Installing and configuring Workflow Server with a new Db2 database server

Edit online
Draft comment:
This topic only applies to BAW, and is located in the BAW repository. Last updated on 2025-01-20 10:38
Draft comment:
This topic was viewed 2 times since its publication
Workflow Server provides one business process management runtime environment that can support a range of business processes for development, test, staging, or production.

Before you begin

If you are installing from downloaded images from Passport Advantage®, ensure that you downloaded all three required images for Windows. If you are installing from the DVD images, obtain the compressed files from the DVDs. In both cases, extract all of the files from the compressed files to the same location on your hard disk.
Restriction: Use 7zip to extract the files. Disk 2 is too big for the built-in Windows extraction tool.

About this task

Using the typical installation option, you can install Db2 and configure the required databases for IBM® Business Automation Workflow. Select typical installation only if you have administrative privileges (are an Administrator user) and do not have an existing Db2 database server on the system. If you are installing Db2 as a Windows domain user, the domain user name must exist and be added to the local Administrators group before you start the launchpad.

From the product launchpad, the typical installation process installs the software, configures the deployment manager and managed-node profiles, and configures a single-cluster deployment environment that consists of one node and one server. It also installs IBM WebSphere® SDK Java™ Technology Edition 8 (Java 8).

Only one IBM Installation Manager is required to install multiple instances of IBM Business Automation Workflow.

Procedure

  1. Optional: If you are connected to the Internet, the typical installation process automatically upgrades your product to the latest refresh pack and interim fix level. If you want these upgrades to be installed from a local directory instead, or if you want to specify the fix level, you can modify a properties file to direct Installation Manager to the upgrades to install.
    Create the following file:
    • C:/HOMEPATH/bpm_updates.properties
    where
    • The HOMEPATH environment variable points to C:/Users/user_name
    Note: Ensure that you have read/write access to the folders that are specified in the bpm_updates.properties file.
    The file uses three prefixes: ifix, fixpack, and launchpad. Each prefix must be followed by a period. The name after the prefix and the period can be anything you want, which enables you to point to multiple locations for interim fixes, fixpacks, and launchpad upgrades. The locations can be either local directories or URLs. The following code is an example of the prefixes and names in the properties file:
    ifix.1=C:/bpmUpdates
fixpack.2=http://test/rep
launchpad.1=C:/launchpad_updates
fixpack.WAS_REP=C:/WAS_updates
fixpack.BPM_REP=C:/BPM_updates
  2. Run Launchpad64.exe, which is in the root directory of the extracted files.
    You can run only one launchpad at a time.
  3. Optional: If you are prompted to update the launchpad, click Update. The updates are installed and your launchpad is restarted automatically.
    If you do not have access to the Internet and want the updates to be installed from a local directory, you can modify a properties file with the appropriate launchpad prefix as described in step 1 to direct Installation Manager to the updates to install.
  4. On the Welcome page, click Typical installation.
  5. Select Install Workflow Server and click Next.
  6. Click Next.
  7. Specify Workflow Server information:
    • Host name: This field shows the name of your machine.
    • Location: Enter the installation location for Workflow Server or click Browse to select the location.
      Notes:
      • The installation location must either be an empty directory or a directory that does not exist and is created during installation.
      • The installation location cannot contain National Language Strings (NLS).
    • Environment Type: Select how the Workflow Server is used. If you have a Workflow Server Production License, set the type to Production. If you have a Workflow Server non-Production License, choose any of the other types.
      • Select Development if the server is to be used in a development capacity.
      • Select Test if the server is to be used as a testing environment, for example, for load testing.
      • Select Staging if the server is to be used as a temporary location to host changes before putting them into production.
      • Select Production if the server is to be used in a production capacity.
    • Name: Specify the name for the Workflow Server environment. This name is used to connect from a Workflow Center to this Workflow Server.
      Restriction: Do not mix production and non-production servers in the same cell.
    • Specify the User name and Password for the cell administrative account. The cell administrator is the primary WebSphere Application Server administrator. A user who is assigned to this role can assign other administrator roles, and is responsible for the administration of the cell and topology. A user who is assigned to this role is not responsible for the administration of the IBM Business Automation Workflow components. Having this role provides access to all interfaces, enabling users to alter or delete all types of available library items and assets, including process applications and toolkits. The user in this role also administers Workflow Servers, Performance Data Warehouses, and internal users and groups. You must be a user assigned to this role to deploy process applications on the Workflow Center server.
    • Specify the User name and Password for the deployment environment account. The deployment environment administrator is the primary IBM Business Automation Workflow administrator. A user who is assigned to this role has administrative access to Workflow Center and Process Admin Console. Having this role provides access to all interfaces, enabling users to alter or delete all types of available library items and assets, including process applications and toolkits. The user in this role also administers Workflow Servers, Performance Data Warehouses, and internal users and groups.
    Select Use this server offline if this Workflow Server will not be connected to a Workflow Center. Offline servers can still be used when deploying snapshots of process applications, but the method for deploying process applications to an offline process server differs from the method for deploying process applications to an online Workflow Server.
    If you did not select Use this server offline, provide the following information for the Workflow Center that this server should connect to:
    • Host name: Enter the host or virtual host that this Workflow Server will use to communicate with Workflow Center. Use a fully qualified host name. In an environment with a load balancer or proxy server between the Workflow Server and the Workflow Center services, make sure that what you designate here matches the URL that is used to access the Workflow Center.
    • Port: Enter the port number of the Workflow Center. In an environment with a load balancer or proxy server between the Workflow Server and the Workflow Center, make sure that what you designate here matches the URL that is used to access the Workflow Center.
    • User name: Enter the name of a Workflow Center user. Workflow Server will connect to Workflow Center as this user.
    • Password: Enter the password for the Workflow Center user.
    You can click Test Connection to check the connection to the Workflow Center. The connection attempt can fail if the user name and password combination is wrong, or if a custom context root has been set for the Workflow Center. If the custom context root has been set, you must use a custom install path instead of typical.
  8. Click Next.
  9. Select No. I need one installed for me. to install Db2.
  10. Specify the User name and Password for the Db2 database.
    Restriction:
    • If you use a Windows domain user ID, include the at sign (@) and the domain name: userID@example.com. Confirm that the domain user ID already exists and was added to the local Administrators group before the launchpad was started.
    • User names must not contain National Language Strings (NLS)
    • User names must be maximum 30 characters long
  11. Click Next to continue.
    Note: If you are using a local properties file, you do not need to provide your IBMid and password.

    A connection to the service repositories is required to download and install fix packs and required interim fixes from the Internet, including fixes for WebSphere Application Server and IBM Business Automation Workflow. You can obtain an IBMid and password by registering at http://www.ibm.com.

    To continue installing without downloading the required fixes, click Cancel or clear the Use your support account to include updates with the installation option on the Installation summary page.

    After successfully installing the product, you can use Installation Manager to install the required fixes.

  12. On the Installation summary page, verify that the installation options and read the license agreements. If you agree to the terms of the license agreements, click I have read and accepted the license agreement and notices.
  13. Click Install Software.

Results

After a successful installation, the Quick Start console starts automatically. If the security certificates failed to import for the connection between Workflow Center and Workflow Server, you must configure the SSL communication manually.

What to do next

If you used the Windows domain user ID to access existing Db2 database and tables, and the profile could not be created, use the following solution:
  1. Follow the steps listed in DB2 log file error: SQL1092N "USERID does not have the authority to perform the requested command or operation.".
  2. Edit the file install_root\logs\config\BPMConfig_timestamp.log. (There should only be one log file with that file name.)
  3. In the log file, search for the line that contains the following string:

    com.ibm.bpm.config.BPMConfig.validateBPMConfigCommand(): ENTRY -create -de

  4. When you have located the string, copy the portion of the string that begins with the -create parameter and paste it to a BPMConfig script invocation in the install_root\bin directory on the Windows command line. For example:

    BPMConfig -create -de C:\Users\jdoe\AppData\Local\Temp\IBM_LaunchPad_BPM_1383510443100\SingleCluster.properties

To learn about security for the environment and applications, see Creating a secure environment.

After the server is started, if you want to use the case management features, see the topic Configuring your system for case management.