Installing MDID2

From Mdidwiki

Jump to: navigation, search

This article describes the installation process of MDID2. If you already have MDID2 installed and want to upgrade to the latest version, check the upgrade instructions.

Contents

Prerequisites

Due to difficulties with running MDID on Linux distributions using mono, and little demand for mono support, we currently only recommend and support installing MDID on a Windows server.

Installation

  • Download and extract software package in desired location, e.g. c:\mdid2 (Windows) or /usr/local/mdid2 (Linux)
  • Create a directory that will hold image content (the account running the web application must have write permission on this directory), e.g. c:\mdid2\images (Windows) or /usr/share/mdid2/images (Linux)


Website setup

Note: These steps only work if MDID2 is the only web application running on the server. If MDID2 should be an additional web application, create a new web site instead of using the Default Web Site and check for the appropriate parameters for the aspnet_regiis tool.

  • Run Start->Programs->Administrative Tools->Computer Management
  • Select Services and Applications->Internet Information Services->Web Sites
  • Open Properties for Default Web Site
  • Select Home Directory and set Local Path to the extracted wwwroot directory
  • Open a command prompt and install the ASP.NET client scripts by running
    c:\windows\Microsoft.NET\Framework\v1.1.4322\aspnet_regiis -c

On Windows 2003, ASP.NET has to be enabled as well:

  • Run Start->Programs->Administrative Tools->Computer Management
  • Select Services and Applications->Internet Information Services->Web Service Extensions
  • Select ASP.NET v1.1.4322 and click Allow


Database setup

MySQL

  • Create a new MySQL database with desired name by running
    mysqladmin -u root create mdid2
    or if you have setup a root account password, run
    mysqladmin -u root -p create mdid2
  • Log into MySQL by running
    mysql -u root
    or if you have setup a root account password, run
    mysql -u root -p
  • Create a new user account and set the password by submitting these commands:
    grant all privileges on mdid2.* to mdid2@localhost;
    set password for mdid2@localhost=old_password("password");
    flush privileges;

Important: You may need to configure MySQL to use UTF8 to ensure that Unicode characters are handled correctly. To do this, edit your my.ini configuration file to contain this line in the server section: 

[mysqld]
default-character-set=utf8

Microsoft SQL Server 2000

  • Run Start->Programs->Microsoft SQL Server->Enterprise Manager
  • Select local server->Databases
  • Create a new database (Action->New Database) with desired name (e.g. mdid2) and in desired location
  • Select Security->Logins
  • Create new login (Action->New Login) with desired login name and password (SQL Server Authentication is recommended)
  • On the Database Access tab for the account, select the newly created database and check the db_owner box under Database roles


Note: Be sure to have the full-text service (shows as "Microsoft Search" in the SQL Service Manager) running. Not having the service running when you open up the web browser to setup the MDID database tables can stop the install script midway through. This can result in an error like "Cannot retrieve database version [2]". MDID will not run on MSDE due to this dependency upon the full-text search service.

Configuration

Rename the the config.xml.release file that came with the software package to config.xml and set these entries:

  • <content><resourcepath> to the image content directory
  • <content><downloads> to the included downloads directory
  • <content><templates> to the included templates directory
  • <database><servertype> must be MYSQL for MySQL or MSSQL for Microsoft SQL Server.
  • <database><connection> must be updated with the chosen username and password
  • <smtp><server> must be the domain name or IP address of an accessible SMTP server
  • <smtp><sender> must be a valid email address, which will be used as the sender address for automatically generated emails
  • <database><upgradeable> must be true to run the installation and set the MSSQL password, it should be set to false once the installation is complete.

Starting with release 0.8, an alternative full-text index can be configured.

Building the software

  • Start the build process by running 
    nant go
    in the mdid2 directory.

Database initialization

  • Open a web browser and point it to the application that is now setup
  • Populate the database by logging in using "admin" as both the username and password
  • Remember to change the password for the admin account using My MDID->Options

Configuration

Enabling ImageViewer 1 Support

These steps are only required if you want to enable support for ImageViewer 1 in addition to ImageViewer 2 support.

  • Edit the machine.config file for the ASP.NET 1.1 framework, located at c:\winnt\Microsoft.NET\Framework\v1.1.4322\config\machine.config
  • Find the line
    <add verb="*" path="*.asp" type="System.Web.HttpForbiddenHandler"/>
  • Replace that line with
    <add verb="*" path="*.asp" type="System.Web.UI.PageHandlerFactory"/>
  • Run Start->Programs->Administrative Tools->Computer Management
  • Select Services and Applications->Internet Information Services
  • Open Properties for Default Web Site (or the web site you set up)
  • Select Home Directory and click the Configuration button
  • Under App Mappings, find the entry for the .aspx extension and note the Executable Path
  • Find the entry for the .asp extension, click edit and enter the Executable Path that was listed for the .aspx extension
  • Download the ImageViewer 1 files and extract all files into the wwwroot\imgview directory of your MDID2 installation.
  • You can also place the ImageViewer1.zip file in the mdid2\wwwroot\downloads directory and uncomment the corresponding entry in downloads.xml to make it available on the Downloads page of your installation.

Enabling External Authentication Support

  • Modify the config.xml file in your MDID2 installation directory
  • In the <authentication> section, rename the opening and closing tags for <method.example> tag to <method>
  • Change the method tag to represent the authentication type you want to use:
    • for LDAP: <method>Orciid.Core.LdapUserAuthentication</method>
    • for POP3: <method>Orciid.Core.Pop3UserAuthentication</method>
    • for IMAP: <method>Orciid.Core.ImapUserAuthentication</method>
  • If using LDAP, specify the correct information for the <server> and <querypath> settings. If you have been using MDID1 with LDAP authentication, you can look up these settings in the config.asp file of your MDID1 installation.
  • If using IMAP or POP3, specify the server, port, and email domain name in the <imap> or <pop3> section.
  • The <autocreateuser> setting specifies if users who have an LDAP account, but no MDID2 account, can log in and have an MDID2 account automatically created for them. If this setting is true and you are using LDAP, you also need to specify the names of the respective LDAP properties in the <ldap><fields> section. Those LDAP values will be used in the newly created MDID2 account.
  • Save the config.xml file. No restart of MDID2 should be required to activate the new settings.

Enabling/Disabling verbose error messages

Exceptions may occur at any time. Depending on a setting in the web.config file in the wwwroot directory of your MDID2 installation, these exceptions may be shown to the end user. To change the behaviour, modify the <customErrors> settings in the web.config file.

Visual Studio project files

See the visualstudio.txt file included with the package for instructions on how to compile, debug, and run MDID within Visual Studio 2003.

Retrieved from "http://mdid.org/mdidwiki/index.php?title=Installing_MDID2"
Personal tools