Items 1-7 are required to be installed prior to installing and configuring Tasica Workflow.

Tasica Workflow Deployment Manager

The Deployment Manager will allow you to configure and automatically deploy Tasica Workflow to an IBM WebSphere Application Server. This tool will create the necessary database, directory, and mail resource entries on the application server. Please note that any existing WebSphere Application Server resources generated by the Deployment Manager will be updated or overwritten if the tool is executed multiple times.

To begin the Tasica Workflow Deployment Manager, open the file TasicaConfig.exe in the root directory of the installation. Use the left toolbar to navigate the different configuration pages described below. After the configuration of Tasica Workflow is complete, follow the directions listed under the WebSphere Server Connection and Deploy Tasica Workflow sections to deploy Tasica Workflow to the application server.

Database Settings/Installation

From the Database Settings/Installation page you can enter database connection information, test the database connection, and prepare a specified database for use with Tasica Workflow.

Database Settings

Description

Database Type

There are four supported database types that can be used with Tasica Workflow and WebSphere Application Server.

Note: If Microsoft SQL or Oracle databases are used, then you will need to download the specified JDBC driver before the database preparation can be performed.

Database Host

Enter the database host's URL or IP address.

Database Port

Enter the port used to connect to the database. The default value for each database type is automatically supplied when changing database types.

Database Name

Enter the name of the database to connect to.

Database Login

Enter the database login user name. This user name will require read and write access to the database.

Login Password

Enter the password associated with the user name above.

JDBC Driver

If the chosen database is Microsoft SQL or Oracle then this option will appear. You will need to have already downloaded the appropriate JDBC driver. If the downloaded driver is enclosed in a zip file, it will be necessary to extract the driver jar file. The download links for the appropriate JDBC driver are given above in the Database type section. Click the Browse button and select the driver from the local file system.

Click Test Database Connection to see whether a connection to the database was successfully established and whether it is necessary to install the Tasica Workflow database tables.

Click Update Settings to save the currently entered configuration and driver settings.

Directory Settings

From the Directory Settings page you can enter the connection information needed to connect to an LDAP directory.

Directory Settings

Description

Directory Type

From this drop down you can choose the directory type that will be used with Tasica Workflow. There are five options:

Active Directory

Domino

IBM Directory Server

Novell eDirectory

Other LDAP Directory

LDAP Host

Enter the LDAP host's URL or IP address.

LDAP Port

Enter the port number to connect to the LDAP server. The default setting is 389.

Global Catalog Port

Enter the global catalog port number here. The default value is 3268. This option will only be visible if the Directory Type you chose supports global catalog ports.

LDAP Login

Enter the LDAP login user name.

Login Password

Enter the password associated with the specified user name.

Base DN

Enter the base DN to be used for accessing Tasica Workflow. Any users and groups listed under the Base DN will be able to log in to Tasica Workflow.

User Name Attribute

Enter the attribute used to access the user name. The default value is 'cn'.

Click Test LDAP Connection to see whether a connection to the LDAP server was successfully established.

Click Update Settings to save the currently entered configuration settings.

Directory Configuration

From the Directory Configuration page you will be able to configure additional settings for the LDAP connection.

Directory Configuration Settings

Description

Admin Role

Enter the full distinguished name (DN) of the LDAP group that will be given administrative privileges within Tasica Workflow.

Mail Attribute

Enter the attribute name used within the LDAP server to represent a user's email address. The default value is 'mail'.

Group Mail Attribute

Enter the attribute name used within the LDAP server to represent a group's email address. The default value is 'mail'.

Maximum Search Results

Enter the maximum number of search results that should be returned when using the LDAP browser within Tasica Workflow Designer or Tasica Workflow Server.

Click Update Settings to save the currently entered configuration settings.

Repository Configuration

From the Repository Configuration page you will be able to enter the connection information for an IBM Lotus Quickr repository.

Repository Configuration Settings

Description

Repository Introspection URL

Enter the IBM Lotus Quickr introspection URL.

Repository Login

Enter the repository login user name. This user must have write permissions to the repository in order to publish form files and/or read permissions to the repository in order to display forms from the repository.

Login Password

Enter the password associated with the specified user name.

Click Test Connection to see whether a connection to the repository server was successfully established.

Click Update Settings to save the currently entered configuration settings.

Data Source Configuration

From the Data Source Configuration page you will be able to add external SQL data sources that can be used accessed within workflows and data sets.

Click Add Data Source to create a new data source and show the Add Data Source dialog box. The following fields will be available:

Data Source Configuration Settings

Description

Data Source Name

Enter the JNDI name of the data source. Typically this will be in the format “jdbc/datasource”, without the quotes.

Database Type

Choose the type of database to be used from the drop down menu. There are five options:

DB2

Microsoft SQL

Oracle

AS400

MY SQL

Database Host

Enter the database host's URL or IP address.

Database Port

Enter the port number needed to connect to the database, The default value for each database type is automatically supplied when changing database types.

Database Name

Enter the name of the database that you want to connect to.

Database Login

Enter the database login user name. This user name will require read privileges in order to query the database and write privileges in order to update the database.

Database Password

Enter the password associated with the user name.

JDBC Driver

If the chosen database is Microsoft SQL, Oracle, or MY SQL then this option will appear. You will need to have already downloaded the appropriate JDBC driver. If the downloaded driver is enclosed in a zip file, it will be necessary to extract the driver jar file. The download links for the appropriate JDBC driver are given above in the Database Settings/Intsallation section. Click the Browse button and select the driver from the local file system.

Click Test Connection to see whether a connection to the database was successfully established.

Click Finish to save the data source information and close the window.

Mail Server Configuration

From the Mail Server Configuration page you can edit the settings to connect to an SMTP mail server.

Mail Server Configuration Settings

Description

Mail Source Name

This field cannot be modified.

Mail Source Host

Enter the mail server host's URL or IP address.

Click Update Settings to save the currently entered configuration settings.

System Configuration

From the System Configuration page you can edit general system settings.

System Configuration Settings

Description

Site Title

Enter the title that will be displayed on web browser title bars when accessing the Tasica Workflow web interface.

Notification Sender Address

Enter the sent-by email address to be used for email notifications from Tasica Workflow.

Notification Encoding

From the drop down menu choose the encoding type used to send email notifications. If you wish to enable HTML in emails, select text/html. If you wish emails to be sent in plain text, select or text/plain.

Tasica Workflow Server URL

Enter the URL for the Tasica Workflow Server. This information is required for action item email notifications to be enabled. Any action item links in email notifications will use the specified URL as the base address of the Tasica Workflow application.

Click Update Settings to save the currently entered configuration settings.

Logging Configuration

The Logging Configuration page can be used to modify the system logging settings.

From the drop down menu choose the logging level you wish the log to keep track of. There are four options:

Error – Only basic server start up information and critical errors will be displayed in the Tasica Workflow log files.

Warn – Only basic server start up information, error messages, and unexpected behavior warnings will be displayed in the Tasica Workflow log files.

Info – Displays the same information as the Warn level, as well as connection information when users log in to the Tasica Workflow web interface.

Debug – Displays the same information as the Info level, as well as a large amount of diagnostic information for client activities, workflow activities, and user activities. Not recommended for production environments.

Click Update Settings to save the currently entered configuration settings.

WebShere Server Connection

From the WebSphere Server Connection page you can set up the connection settings used for contacting the WebSphere Application Server.

There are two sections to the WebSphere Server Connection pane: Application Server Settings and Deployment Scope Settings. The Application Server Settings section must be filled out completely before the Deployment Scope Settings section can be properly completed.

Click the Browse button and select the local installation path of the WebSphere Application Server instance you wish to deploy Tasica Workflow on. The selected folder must be the root of an application server installation or the bin directory under the application server's installation path.

Admin User Name

Enter an application server's administrator user name.

Admin Password

Enter the password associated with the specified user name.

The Deployment Scope Settings section allows you to select the scope that the Tasica Workflow Server resources will be created on and the Tasica Workflow Server application will be deployed on.

Deployment Scope Settings

Description

Retrieve Deployment Scopes From Server

Click this button after the Application Server Settings section has been completed. The Node and Server drop down menus will be populated with all available application server scopes.

Node

Choose the application server node you wish to deploy on.

Server

Choose the server name you wish to deploy the Tasica Workflow Server application on.

Context Path

Enter the context path that will be used for the Tasica Workflow Server application.

Deploy Tasica Workflow

The Deploy Tasica Workflow page is used to automatically deploy the Tasica Workflow application on to a WebShpere Application Server. If the process does not complete successfully, an application war file will be created and the manual installation process described under the Integrating Tasica Workflow with WebSphere Application Server section of this document must be followed.

Click Test Configuration to validate the configuration information entered in the previous pages. You will be notified if there are any errors or if any functionality is limited due to specified settings or connectivity issues.

Click Deploy Tasica Workflow to automatically deploy the Tasica Workflow Server application and create all necessary resource entries on the specified application server. This button is available when a successful connection to the workflow database, workflow LDAP, and Webshpere Application Server can be established.

The Create Deployable button will only be available if automatic deployment to the WebSphere Application Server is not available. Click this button to create an application war file that is configured with the Tasica Workflow settings entered in the previous pages. The war file will be created in the root of the Tasica Workflow server's installation path with the name in the format “TasicaWorkflow#.war”. Creating a deployable will not overwrite any previously created deployables, since the number portion of the file name will be different.

Prerequisites for Manual Deployment

The connections to the database server and the LDAP server are automatically set up if you use the deployment manager's automatic deployment features. See the Tasica Workflow Deployment Manager section for more information. If you do not use the automatic deployment features, you must set up the following:

Database

LDAP

Database – The WebSphere Application Server requires a connection to the database server.

Deploy and configure the IBM Forms API on WebSphere Application Server. For more information, please refer to the IBM Forms Documentation.

Installing Tasica Workflow

Insert the Tasica Workflow CD and run the installer application.

Accept the license agreements to proceed.

Provide the path to install Tasica Workflow Server in the ‘Install to:’ field.

Optional: To run Tasica Workflow Server as a Windows service, select ‘Run Tasica Workflow as a Windows Service?’ Note that the server will still need to be configured using the server console and any configuration changes will require the service to be restarted. The service will not start until the server has been properly configured.

Optional: To add a shortcut to the server on the desktop, select ‘Add Desktop Shortcut?’.

To integrate Tasica Workflow Server with IBM Forms, select ‘Integrate with IBM Forms?’ If IBM Forms Server and Tasica Workflow Server are to be installed on the same computer, ensure that IBM Forms is installed first.

Click ‘Install’.

Preparing the Database for Tasica Workflow

Tasica Workflow uses a database to hold the application's data. To prepare the database:

Launch TasicaConfig.exe (Windows) or TasicaConfig.sh (Linux, AIX) from the the 'Server' directory of the installation.

Click the Database Settings/Installation option from the left toolbar and fill out the following information:

Database Type: Can be DB2, Microsoft SQL, Oracle, or AS400.

Database Host: The hostname or IP address of the database server.

Database Port: The port to which the database is listening.

Database Name: The name of the database that will host Tasica Workflow data.

Database Login: A database user that has CREATE and MODIFY permissions.

Login Password: The database user’s password.

Click ‘Test Database Connection’ to verify that a connection can be made to the database.

Click ‘Install Tasica Workflow’.

Oracle and MSSQL Users: Tasica Workflow Server does not ship with the JDBC drivers required to connect to a MSSQL or Oracle database.

MSSQL: The file jtds-1.2.2.jar must be placed in /Server/libfd
Download the Jtds-1.2.2.jar here.

Oracle: The file ojdbc5.jar or ojdbc6.jar must be placed in /Server/libfd
The ojdbc5.jar is required for Java 5 runtimes and ojdbc6.jar is required for Java 6 runtimes. These drivers are included with the Oracle installation media, or can be downloaded here.

Preparing Tasica Workflow for connections to other databases (optional)

The following set up is required to access external SQL data sources if you do not use the deployment manager tool's automatic deployment features. See the Tasica Workflow Deployment Manager section for more information. You do not need to follow these instructions if you use the automatic deployment features.
1. Using a zip file viewer, open the file TasicaWorkflowServer.war file located in the Server directory of the installation.
2. Extract WEB-INFf/web.xml.
3. Open the web.xml file and locate the list of <resource-ref> tags.
4. Create a new resource-ref entry with the following structure:
<resource-ref >
<description>SQL DB Connection</description>
<res-ref-name> </res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
<res-sharing-scope>Shareable</res-sharing-scope>
</resource-ref>
5. Locate the <res-ref-name> tag, and add a name for the database connection, prefaced by 'jdbc/'. Example: <res-ref-name>jdbc/mydatasource</res-ref-name>
6. Save the changes.
7. In the application WAR file, replace the WEB-INF/web.xml file with the updated web.xml file.

Integrating Tasica Workflow with WebSphere Application Server

Tasica Workflow integrates with the WebSphere Application Server through the WebSphere Application Server Administration Console. The following process describes how to manually deploy the Tasica Workflow Server application on a WebSphere Application Server instance. See the Tasica Workflow Deployment Manager section for more information. You do not need to follow these instructions if you use the automatic deployment features.
This process will also configure the remaining integration settings with the database, LDAP, and the IBM Forms Server - Webform Server. Integration between Tasica Workflow Designer and the IBM Forms Designer is a separate procedure.

Login to WAS Server Administration Console.

Expand ‘Applications’.

Click ‘New Application’.

In the main window, click ‘New Enterprise Application’.

Browse to find the Tasica Workflow Server war file. It will be titled TasicaWorkflow.war.

Click ‘Next’.

When prompted for how to install the application, click ‘Detailed’.

Click ‘Next’.

Complete the New Application Installation wizard.

Step 1: Select Installation Options

Select ‘Precompile JavaServer Pages files’.

Leave ‘Directory to install application’ empty.

Select ‘Distribute Application’.

Clear ‘Binary configuration’.

Clear ‘Deploy enterprise beans’.

Provide a name for Tasica Workflow in the ‘Application name’ field. This is the name that will appear in the application management sections of WebSphere Application Server.

Select ‘Create MBeans for resources’.

Clear ‘Override class reloading settings for Web and EJB modules’.

Leave ‘Reload interval in seconds’ empty.

Clear ‘Deploy Web services’.

Set ‘Validate Input off/warn/fail’ to ‘warm’.

Clear ‘Process embedded configuration’.

Accept the default values for ‘File Permissions’.

Accept the default value for ‘Application Build ID’.

Clear ‘Allow dispatching includes to remote resources’.

Clear ‘Allow servicing includes from remote resources’.

Accept the default value for ‘Business level application name’.

Accept the default value for ‘Asynchronous Request Dispatch Type’.

Clear ‘Allow EJB reference targets to resolve automatically’.

Click ‘Next’.

Step 2: Map Modules to Servers

In the ‘Clusters and servers’ section, select all the servers on which you want to deploy Tasica Workflow.

For a clustered environment, select the cluster where you want to deploy Tasica Workflow.

Select ‘Tasica Workflow’.

Click ‘Apply’.

Click ‘Next’.

Step 3: Provide JSP reloading options for Web modules

Accept the default ‘JSP reloading options for Web modules’ settings.

Click ‘Next’.

Step 4: Map shared libraries

Accept the default ‘Map shared libraries’ settings.

Click ‘Next’.

Step 5: Map shared library relationships

Accept the default ‘Map shared library relationships’ settings.

Click ‘Next’.

Step 6: Map resource reference to resources
This page contains all the primary settings for integrating Tasica Workflow with the mail server, LDAP, and the database.

In the ‘javax.mail.Session’ section, type ‘mail/fd’ in the ‘Target Resource JNDI Name’ field.

In the ‘javax.naming.directory.DirContext’ section, type‘jndi/fdldap’ in the ‘Target Resource JNDI Name’ field.

In the ‘javax.sql.DataSource’ section, type ‘jdbc/formsdirector’ in the ‘Target Resource JNDI Name’ field.

If you have defined any additional database connections, ensure that the ‘Target Resource JNDI Name’ field matches the value in the ‘Resource Reference’ column for each entry. For more information on defining additional database connections, please refer to the “Preparing Tasica Workflow for connections to other databases” section of this document.

Click ‘Next’.

Step 7: Map virtual hosts for Web modules

Accept the default ‘Map virtual hosts for Web modules’ settings.

Click ‘Next’.

Step 8: Map context roots for Web modules

Provide a context root in the ‘Context Root’ field. This is the path where the application will reside. For example, if the context root is ‘/tasica’, then the full path would be ‘http:///tasica’.

Click ‘Next’.

Step 9: Map environment entries for Web modules

Provide the values for the following environment variables:

Environment Variables

Description

DIRECTORY_MAIL_ATTRIBUTE

The e-mail address attribute for users in the LDAP directory. This is typically ‘mail’.

DIRECTORY_GROUP_MAIL_ATTRIBUTE

The e-mail address attribute for groups in the LDAP directory. This is typically ‘mail’.

DIRECTORY_USERNAME_ATTRIBUTE

The user name attribute for users in the LDAP directory. This is typically ‘cn’ or ‘uid’.

DIRECTORY_MEMBER_ATTRIBUTE

The attribute that identifies users as belonging to a group in the LDAP directory. This is typically ‘member’.

DIRECTLRY_MAX_RESULTS

The maximum number of results that a directory search can return.

LOG4J_DEFAULT_LOGGING_LEVEL

The types of messages written to the Tasica Workflow log files. This is either ‘debug’, ‘info’, ‘warn’ or ‘error’. Note that ‘debug’ is not recommended for production environments.

LOG4J_PROPERTIES_PATH

The path to the LOG4J properties file to use to format Tasica Workflow’s log files. Leave this entry blank to use the default log formatting.

USER_ID

How users are identified in Tasica Workflow. This is either ‘dn’ or ‘email’. If ‘dn’ is specified, users are identified by their distinguished name from LDAP. If ‘email’ is specified, users are identified by their e-mail address from LDAP.

NOTIFICATION_FROM

The e-mail address used for sending system messages such as routed form notifications.

NOTIFICATION_ENCODING

The e-mail encoding. Options are either ‘text/html’ or ‘text/plain’.

SITE_TITLE

The title displayed on a user’s browser when accessing the Tasica Workflow web interface.

ADMIN_ROLE

The distinguished name of the LDAP group given administration rights for the Tasica Workflow Server.

DATABASE_JNDI_NAME

The name of the Tasica Workflow database. This should remain ‘jdbc/formsdirector’.

Order of Installation

You must install items 1 and 2 prior to installing and configuring Tasica Portlet Pack.

Prerequisites

There are no prerequisites for this integration.

Pre-Installation Configuration for Tasica Portlet Pack

You must specify a Tasica Workflow server for the portlet pack before users will have access to the portlets.

To set or change the Tasica Workflow Server used by the portlet pack:

Open the Tasica Workflow Portlets Pack application WAR file using a zip file viewer. By default, this file is named TasicaPortletPack.war.

Extract WEB-INF/web.xml.

Open the web.xml file and navigate to the list of tags.

Locate the tag that corresponds to FD_SERVER_ADDRESS_KEY.

Enter the location of the Tasica Workflow server between the and tags. The location must be in the following format:

scheme://fd_server:port/context_path

The currently supported schemes are http and https. The port section is optional and if omitted will default to use port 80 on http or 433 on https. Additionally, if there is no context_path for Tasica Workflow, ensure that there is only one slash (/) at the end of the address.

Save the changes made and replace the WEB-INF/web.xml file in application WAR file with the updated web.xml file.

Pre-Installation Configuration for Single-Sign-On Lockout

Each Tasica Workflow portlet needs to authenticate with the Tasica Workflow server. Certain LDAP servers can be configured to flag a user account as compromised if it receives a number of consecutive failed attempts. This can be problematic if a user enters the wrong credentials and the portal page has many portlets all attempting to authenticate. By default, Tasica Workflow portlets only try to authenticate once. After a failed attempt, the user must reenter their credentials before authentication is attempted again. In most cases there is no reason to modify this behavior. To modify this follow the above procedure and change the value of FD_SSO_LOCKOUT from “true” to “false”.

To set or change the single-sign-on lockout settings:

Open the Tasica Workflow Portlets Pack application WAR file using a zip file viewer. By default, this file is named TasicaPortletPack.war.

Extract WEB-INF/web.xml.

Open the web.xml file and navigate to the list of tags.

Locate the tag that corresponds to FD_SSO_LOCKOUT.

Enter “true” or “false” between the and tags. Entering “true” will enable single-sign-on lockout.

Save the changes made and replace the WEB-INF/web.xml file in application WAR file with the updated web.xml file.

Installing Tasica Portlet Pack

Login to WebSphere Portal Server.

Select the ‘Administration > Portlet Management > Web Modules’ page.

Click ‘Install’.

Browse to find the Tasica Portlet Pack war file. It will be titled TasicaPortletPack.war.

Configuring Tasica Portlet Pack

When a user accesses a Tasica Portlet for the first time, they are required to enter their user name and password. This only occurs once per user and they only have to do this for one portlet. For example, if the user accesses the Tasks Portlet first, they will enter their user name and password to continue. If they then access the Action Items Portlet, they will not be required to enter any credentials.

Click the ‘Update your user name and password’ link.

Enter your Tasica Workflow user name in the field provided.

Enter your Tasica Workflow password in the field provided.

Click ‘Update Settings’.

TASICA WORKFLOW DESIGNER AND TASICA REPORT DESIGNER INTEGRATION

Background

The Tasica Workflow Designer integration consists of installing the Workflow Designer on top of a IBM Forms Designer installation. Tasica Reports Designer will install at the same time as Tasica Workflow Designer.

Integration Components

Tasica Workflow Designer will integrate with the following component:

IBM Forms Designer

Order of Installation

The order of installation for the solution is as follows:

IBM Forms Designer

Tasica Workflow Designer

Tasica Reports Designer

Item 1 is required to be installed prior to installing and configuring Tasica Workflow Designer.