Help - Admin - Installation

Overview

Aspen Workflow is capable of scaling with Microsoft's SQL and IIS BackOffice components.  Server(s) should be installed and configured in accordance with Microsoft recommendations for these products.  It is possible to configure servers as follows:

• One website with one database
• One website with multiple databases
• Multiple websites with one database
• Multiple websites with multiple databases

These installation instructions will assume the first example (one website with one database), and further assume that IIS and SQL will be running on the same NT Server machine.  Installation of Aspen Workflow requires the following steps:

1. Creation of a SQL 2000 database
2. Running the Aspen Workflow SQL installation script
3. Creation of a Website
4. Installing the Aspen Workflow Active Server Components
5. Installing Third Party Server-Side Components
6. Creating an ODBC System DSN

Step 1: Creation of a MSSQL database

After installing SQL 2000, create a database.  It is recommended that the database be named Workflow, to facilitate immediate use of the Crystal Reports that come packaged with Aspen Workflow.  If you will ultimately be running multiple databases, it may make more sense to name the databases according to their role within your organization.  This will mandate that you recompile the prepackaged Crystal reports to point to the correct database.

Step 2: Running the Aspen Workflow SQL Installation Script

An SQL script name WorkflowV3-install.sql exists among the Aspen Workflow installation files.  From the SQL Query Analyzer, open this script and execute it against the newly created database.  This will create the appropriate tables, indices, constraints and stored procedures. 

Step 3: Creation of a Website

From Microsoft Internet Service Manager, create a website for this installation of Aspen Workflow.  For a single website installation, the Aspen Workflow ASP components can be installed in the INETPUB directory.  For multiple website installations, it is recommend that a websites directory be created on a partition separate from the NT installation.  Under the websites directory, create a directory for each virtual website to be created.  Each virtual website can contain an installation of the Aspen Workflow ASP components, and then be further customized.  For an example of the final directory structure, please refer to the Web Site help page.

Note that support of extranets will demand multiple web sites, even if the installation is for just one production database.

Step 4: Installing the Aspen Workflow Active Server Components

The Aspen Workflow installation files should be installed in the workflow directory, resulting in a directory structure as noted in the Web Site help page.

In addition, be sure to register the /common/programs/workflowDocument.wsc component.

Step 5: Installing Third Party Server-Side Components

Additional components are optional, such as:

• Seagate's Crystal Reports 8.0 or Later
• Server Object's ASPMail (for automated emails)
• Server Object's ASPQMail (for automated emails)
• Server Object's ASPHTTP (for automated HTML document generation)
• Software Artisan's SaFileUp (for document imaging)
• Software Artisan's SaAdmin (for NT account integration)
• Adobe's FDF Toolkit (for data-driven PDF document integration)

Step 6: Creating an ODBC System DSN

Two ODBC System Data Source Names (DSN) need to be created as follows:

• workflow: this will be the default connection to the database, and should use SQL authentication.
• workflowSecure:  this will be the secure connection to the database, and will use NT authentication.

You can set up a default database for the System DSN, but Aspen Workflow will redirect the connection to use the database specified in the login.asp page regardless of this setting.

Welcome | Users | Business | Managers | Documents | Lookup | Administrators