Installing DocuNECT Web v4.5

Installing and Configuring DocuNECT v4.5

This section provides an implementation checklist to help plan your implementation:

1. Select the DocuNECT implementation model by reviewing the DocuNECT Technical Architecture page.

2. Review the Component Compatibility page to ensure that the target environment meets the necessary specifications.

3. The target web server must have the Microsoft .NET Framework (v4.0) installed (if not already present). A link to the foundation classes can be found in the Downloads page.

4. Consult the implementation guides for the ContentConnectors you are going to implement, and for any additional implementation requirements or considerations.

5. Remove all previous versions of the DocuNECT Web product.

6. Log in as the local server administration rights to install the server product.

7. Make sure that the Microsoft Internet Information Server (IIS) is installed and configured on the server. If this steps is perform after installing the Microsoft .NET Framework v4.0, then re-install the framework to make sure the ASP.NET component is properly registered with IIS.

8. If the target server is Microsoft Windows 2008 server then install the IIS 6.0 Management Compatibility component by using the Server Manager. In the Internet Information Services manager, in the ISAPI and CGI Restrictions component allow the restriction for ASP.NET v4.0.

9. The target web server must have the Crystal Reports plug-in. A link to either the 32 or 64 bit plug-in can be found in the Downloads page.

Run the Install for the DocuNECT Web Application

The following points provides a step-by-step guide to installing the Web product:

1. Locate the webhosting.exe file which can be downloaded from the Downloads page. Once located, double-click on the file to initiate the install wizard.

2. Once the install wizard is initiated a welcome screen will be displayed. You will be prompted to enter the name of the system which will be used in the URL.


3. On entering the system name, you will be prompted to enter the IIS web site for the installation and the application pool. It is recommended to create an application pool that is specific to DocuNECT. Note, for Windows 2008 Server make sure the application pool uses ASP.NET v4.0 Classic .NET AppPool.


4. On pressing the Next button, the files for the DocuNECT web will be installed and then another installation wizard will appear that will guide you through the creation/upgrade of the DocuNECT database. You can connect to the database by either using Windows or SQL authentication. This user only used to create/update the database and therefore requires the necessary sysadmin rights to do this.

5. On connecting to the database, you will prompted to either create a new database or upgrade an existing database. Note, the upgrade script built into the web installation will upgrade from any version of 4.x to the latest version.


6. If you select upgrade then the upgrade script will be run on that database. DocuNECT will automatically determine what database version the existing database is on and select the appropriate upgrade for you.

7. On selecting the option to create a new database you will be prompted to select the database name, the SQL collation, and the database owner name. The database name can be any valid SQL server name, but it is recommended to prefix the name with DCN_ to help distinguish the database from other application databases sharing the same server. It is recommended to create a database user called cmsdbadmin to own the different DocuNECT databases. The collation can be left as default unless the DocuNECT database shares the SQL server with another business application that requires a specific collation.


8. A message will confirm that the database has been successfully created.

9. The final task is to confirm the application settings for the web site. This will default to the database owner, but can be changed if necessary. You can also elect to run the DocuNECT using Secure Sockets Layer (SSL). Please note that a SSL certificate will need to be installed on the IIS server in order for this to work correctly.