Content Central Installation Guide

You will now load the Content Central software on your server(s). When you’ve completed the steps in
this chapter, you will have installed all necessary software components of Content Central and will be
ready to either evaluate the software or begin configuring for production.

Launch the installation program, ContentCentral_Setup.exe. Content Central requires several
supporting packages to be installed prior to installation. Select the Install button to proceed. Be patient as
the installer will load several prerequisites, including a new instance of Microsoft® SQL Server Express
Edition.

You may be provided with an option to install additional packages. Choose the appropriate selections for
your organization.

After the prerequisites have finished installing, the InstallShield Wizard will appear and prepare for
installation.

To begin the installation of Content Central, select the Next button. You will be presented with the
Ademero End-User License Agreement. Select the Next button if you wish to proceed.

You may now choose your Destination Folder for the Content Central software. After choosing the
appropriate location, select the Next button to continue.

You now have the opportunity to go back and make changes if necessary, otherwise select Install.

Be patient as the application is installed.

When the installation is complete you will be presented with a Finish button to exit the InstallShield
Wizard. You can optionally choose to View Release Notes, which will be opened when the wizard closes.

Content Central is now installed.

If you’ve installed Content Central for evaluation purposes, you may login to the Web site immediately and begin using the product with the installed demonstration catalogs and documents.

Launch the Web site by selecting the Content Central shortcut on your desktop. In most cases, the URL is http://localhost/ContentCentral/Login.aspx.

Login with the Username demo and Password demo.

You can proceed directly to the User Guide.

In this chapter, you will create several file folders on your server(s) for system data, incoming content, and documents.

Content Central requires three main folders to be created on your file system: System, Incoming, and Documents. These folders are often found together under a main Content Central folder. For more information, see Section 3.6, “Document Storage Area”.

The System folder and its subfolders need to be created for Content Central processing data. In multiserver environments these will usually be created on the server you’ve designated to house documents and other content.

1. Launch an instance of Windows® Explorer.

Tip – Use the Windows Key-E key combo.

2. Browse to, or create the root folder where you would like to create these System folders, e.g., D:\ContentCentral\System\.

3. Create the following folders inside the System folder:

• CodingQueue: This folder will hold documents captured with a Post-Capture Coding or Versatile Coding QCard™ until they have been fully coded and archived.
• DeletedContent: This folder will contain documents that have been removed from the database either by user action or an enforced retention policy. The XML files produced alongside documents are compliant with the Capture Service and can be used to recapture the document by moving the entire package to an XML-based capture folder.
• Indexes: This folder will contain one subfolder for every Index.
• Unprocessed: This folder will contain any captured documents that are unable to be processed due to one or more problems with the incoming file.
• Reports: This folder will contain any reports generated by the workflow engine.
• Thumbnails: This folder will contain thumbnails when thumbnails have been enabled.

The Incoming folder can contain subfolders for each catalog or document type you create. These subfolders will temporarily hold images and other content to be imported by the Capture Service.

1. Launch an instance of Windows® Explorer or use the existing Explorer window from the previous section.

Tip – Use the Windows Key-E key combo.

2. Browse to, or create the root folder where you would like your incoming images and other content to be routed, e.g., D:\ContentCentral\Incoming\.

The Documents folder will contain a subfolder for each catalog you create. These subfolders will store the documents and other content for your organization.

1. Launch an instance of Windows® Explorer or use the existing Explorer window from the previous section.

Tip – Use the Windows Key-E key combo.

2. Browse to, or create the root folder where you would like your documents and other content to be stored, e.g., D:\ContentCentral\Documents\.

This step permits Content Central to write documents and other content to the data folders.

Perform the appropriate task below for each of the following data folders:

\System\CodingQueue\
\System\DeletedContent\
\System\Indexes\
\System\Unprocessed\
\System\Reports\
\System\Thumbnails\
\Documents\

Windows® XP Professional

Add the ASPNET system account or the impersonation account to each folder and grant Full Control to this account. Inheritance should be enabled.

Windows® Server 2000, Server 2003, Vista

Add the Network Service system account or the impersonation account to each folder and grant Full Control to this account. Inheritance should be enabled.

The following adjustments can improve system performance and response.

The ASP.NET State Service improves performance by maintaining session data between the server and client(s). To enable it, access the Services dialog on the machine you’ve designated for the Web site. Locate the service named, ASP.NET State Service, and set the Startup Type to Automatic. If the service is not currently running, start the service. You may now exit the Services dialog.

Access the Internet Information Services dialog on the same machine. This can be found from within the Administrative Tools section of the Control Panel or inside the Management dialog of My Computer (right-click, Manage). Expand the computer-name node to reveal the Web Sites node. Continue expanding until you locate the ContentCentral node. Access the properties of Content Central (right-click, properties) and select the ASP.NET tab. Select the Edit Configuration button. When the ASP.NET Configuration Settings dialog appears, select the State Management tab. Choose the StateServer option from the Session state mode drop down list.

If you would like to also enable ASP.NET Impersonation (the next optimization), remain in this dialog and skip to the next section. Otherwise, select the OK button to save the ASP.NET configuration settings. Select the OK button to save the changes to the Content Central Web site. You may now exit the Internet Information Services dialog.

When users make requests to Content Central, Internet Information Services will use an ASP.NET process identity to access resources such as the SQL Server. Perform the following if you would like to define a different Windows® account for these operations.

Note:  When operating Content Central in a multi-server environment, impersonation is mandatory.

Within the Application tab of the ASP.NET Configuration Settings dialog for the Content Central virtual directory, add a check to the Local impersonation checkbox and provide a pre-defined user account for impersonation. Select the OK button to save the ASP.NET configuration settings. Select the OK button to save the changes to the Content Central Web site. You may now exit the Internet Information Services dialog.

Once impersonation has been enabled, the account used must be allowed permissions to read and write within a few of the previously-defined data folder(s) (See Section 3, “Adding Proper Security Credentials to Data Folders”). The account will also need read and write access to the database in SQL (described later).

The Configuration Manager is responsible for defining the SQL database, linking each server in a multiserver environment, enabling Active Directory integration, and managing licensing.

IMPORTANT:  Because the Configuration Manager stores the OCR license, it must be installed on the server containing the Capture Service.

Begin by launching the application using the desktop shortcut labeled Configuration Manager.

Select the Server Name of your installed SQL Server. If your SQL Server is installed on a non-standard port, you may enter the port number in the Port Number field. Choose the correct Version of SQL Server you have installed.

The Database Name field defaults to Content Central, but you may change it if you desire.

• SQL Admin Login: Choose the method of authentication for accessing SQL with Admin rights. This security level is necessary to create the Content Central database.
• SQL User Login: Choose the method of authentication you would like Content Central to access SQL with during production. When using SQL Authentication, the username and password provided will be created, i.e., the user does not need to exist in SQL. When using Windows Authentication you will need to access the database and provide db_datareader/db_datawriter access to the system account being impersonated through ASP.NET. This will either be the ASPNET or Network Service account when Local Impersonation is disabled (default) or the system account provided when enabling impersonation as described in Section 4.2, “ASP.NET Impersonation”.

Complete the SQL Settings configuration by selecting each of the three buttons at the bottom of the SQL Settings tab. The Create/Edit Database button will create the database for Content Central, and the Test User Login button will create the user when using SQL Authentication.

Proceed to the System Folders tab.

Browse to the appropriate folders created in Section 2.1, “System Folder and Subfolders”.

Content Central can be integrated with Microsoft® Windows® Active Directory so that users can be added to the system easily. Active Directory users will use their existing Windows® account name and password
to login to Content Central.

Select the Add button to add an Active Directory domain to Content Central. To enable this domain, select the Enable Active Directory Authentication checkbox, enter the Fully Qualified Domain Name, and
provide an Active Directory User name and Password. Select the Test Login button to verify Content Central can access the Active Directory server.

You should have received both a user license and OCR license from Ademero. Select the Enter License Key button to enter the User License key and the Import OCR License button to load the OCR License file. You may select the OK button when you’ve completed this step to save your changes.

External applications are used as Workflow Actions in Workflow Rules. An external application can be started in response to one or more Workflow Triggers meeting their conditions.

Select the Add button to add an external application to Content Central. Provide a descriptive Name to help identify the application later.

An application can be bound to a catalog or document type by selecting the appropriate item(s) from the Visibility drop-down list. To make an application available globally, select All Catalogs.

Choose the location of the application by selecting the Browse button to locate the executable.

An optional list of Arguments may be provided. The following list identifies the variables that may be used in the argument list. All variables are case sensitive.

$object – Returns  the  file  path  when  return  object  is  an  item  of  content  orcoding-queue content. Returns a number when return object is an integer.

$clickid – Returns a unique id associated with a user click from a menu. This variable is valid only when an external application is activated from a custom menu item.

$docfolder – Returns the folder path when return object is an item of content or coding-queue content.

$docfilename – Returns the file name when return object is an item of content or coding-queue content.

$docid – Returns the internal identifier for the item of content or coding-queue content.

$catalog – Returns the catalog for the item of content or coding-queue content.

$doctype – Returns the document type for the item of content or coding-queue content.

$field: – Returns the value of an index field from an item of content or coding queue content. Enter the field name inside the square brackets.

$packetname – The name of the packet template

$packetfieldname – The name of the key field of the packet template

$packetfieldvalue – The value of the key field of the packet

$packetstatus – One of the following indicators for the packet

Packet is complete.
Packet is incomplete. The following document types are missing:
doctype1, doctype2…doctypeN.

$actinguserusername – The username of the user causing the action

$actinguserfirstname – The first name of the user causing the action

$actinguserlastname – The last name of the user causing the action

$actinguseremailaddress – The e-mail address of the user causing the action

$apname – Returns the name of the approval process when the return object is an item of content and the workflow trigger is of type: Approval Processes: Movement on Process.

$apaction – One of the following approval-process actions when the workflow trigger is of type: Approval Process: Movement on Process

Assigned to Process
Approved
Rejected
Process Completed
Rejected from Process
Removed from Process

$apdate – Returns the date of the approval-process event when the return object is an item of content and the workflow trigger is of type: Approval Processes: Movement on Process.

$aptime – Returns the time of the approval-process event when the return object is an item of content and the workflow trigger is of type: Approval Processes: Movement on Process.

$appriority – Returns the current priority of the approval-process event when the return object is an item of content and the workflow trigger is of type:  Approval Processes: Movement on Process.

$apnote – Returns the note of the approval-process event when the return object is an item of content and the workflow trigger is of type: Approval Processes: Movement on Process.

$apassignerusername – Returns the username of the user who began the approval process when the return object is an item of content and the workflow trigger is of type: Approval Processes: Movement on Process.

$apassignerfirstname – Returns the first name of the user who began the approval process when the return object is an item of content and the workflow trigger is of type: Approval Processes: Movement on Process.

$apassignerlastname – Returns the last name of the user who began the approval process when the return object is an item of content and the workflow trigger is of type: Approval Processes: Movement on Process.

$apassigneremailaddress – Returns the e-mail address of the user who began the approval process when the return object is an item of content and the workflow trigger is of type: Approval Processes: Movement on Process.

Some applications require argument data to be enclosed in single or double quotes. Example: -argument “$object”. Likewise, it may be necessary to escape double quotes (“) existing within the data that a variable represents, such as when a user enters double quotes in an approval-process note. In these cases you can Use Escape Character for Double-Quotes. The character used depends on the application. Batch files in Windows® use an additional double-quote to escape a double-quote. Example: “This is a “”quoted”” line.” Other applications may use a backslash character. Example: “This is a \”quoted\” line.”

Select the Delete button to remove one or more applications from the list.

The Export Data area allows you to specify files on the server that will be used to export document information in Content Central using workflow rules.

Select the Add button to add a new file. Provide a Name that will be used to reference this file in the Web application. Select the Browse button to select an existing file on the server or specify a new one. This file can be a CSV or TXT file.

WARNING:  New information will be appended to the selected file. Do not choose an existing file that contains important information.