Configuring the human task container, using the installation wizard

Use this task to configure the human task container.

Before you begin

Before configuring the human task container, perform Configuring the business process container using the installation wizard.

Why and when to perform this task

If you have run the bpeconfig.jacl script, the human task container is already configured. The following steps describe how to configure the human task container using the installation wizard.

Steps for this task

  1. In the administrative console, click Servers > Application servers > Server_Name. Then in the Container Settings section, click Human task container settings > Human task container > Human task container installation wizard (in the Additional Properties section). Where possible, the installation wizard offers appropriate default values in the parameter fields, you can view the recommended values on the Human task container installation wizard settings.
  2. Verify that the human task container is not configured. There should be a message indicating that the Human Task Manager is not currently installed. If the human task container is already configured, remove the configuration before you start the installation wizard. For details about how to remove the configuration, see Removing the Business Process Choreographer configuration.
  3. Select the JMS provider and security settings (step 1):
    1. In the drop-down list for JMS provider, select the messaging service that is used by the business process container.
      • For default messaging, select Default messaging provider.
      • For WebSphere MQ, select WebSphere MQ.
    2. Use the default value for Queue Manager (BPC_nodeName_serverName). If you are using the default messaging provider, this field is ignored.
    3. If you are using external messaging (WebSphere MQ JMS provider) and you have not defined the WebSphere environment variable ${MQ_INSTALL_ROOT}, make sure that Classpath points to the WebSphere MQ Java lib directory.
    4. For the JMS user ID, enter a user ID that has administration rights for the messaging service. This user ID will be used to connect to the JMS queue manager. On Linux® and UNIX® systems, use root. On Windows® systems, use the user ID that is used to start WebSphere Process Server.
    5. For the JMS password, enter the password for the JMS user ID.
    6. For Escalation user ID, enter the user ID that will be used by the human task container to perform scheduled actions, for example triggering escalations to verify the expected task state, timed task deletion, and task expiration.
    7. For Escalation password, enter the password for the escalation user ID.
    8. For the Administrator security role mapping, enter the name of the group, defined in the user registry, that will map onto the role of Business Process Administrator. On Windows systems, for example, you can specify the group Administrators.
    9. For the System monitor security role mapping, enter the name of the group in the user registry to map onto the role of Business Process System Monitor. On Windows systems, for example, you can specify the group Administrators.
    10. Click Next to go to the next step in the installation wizard.
  4. Select the JMS Resources (step 2): If you are not reusing an existing JMS connection factory and queues, which is normally the case, select Create new JMS resources using default values. Otherwise, perform the following:
    1. Select Select existing JMS resources.
    2. Use the Connection Factory drop-down list to select the connection factory you want to use.
    3. Use the default Hold Queue value HTMHldQueue.
    4. Use the default Retention Queue value.
  5. Optional: Select Mail session to create the default mail session resource with cell scope, named mail/HTMNotification_nodeName_serverName.
    Attention: If this is not set, no escalation mails are sent.
  6. Optional: To use the Common Event Infrastructure, select Enable Common Event Infrastructure logging .
  7. Optional: To enable the audit log, select Enable audit logging for all human tasks .
  8. Click Next to view the Summary (step 3).
  9. Check that the information on the summary page is correct. The summary includes reminders of which external resources are necessary. If you have not already created them, you can continue configuring the human task container, but you must create the resources before you activate the human task container. Printing the summary page helps you to create the correct resources.
    1. To make corrections, click Previous.
    2. To install the human task container and define its resources, click Finish. The progress is shown on the Installing page.
    3. Verify that no error messages are displayed.
  10. If you selected the Mail session option in step 5, you must set the mail transport host:
    1. Click Resources > Mail Providers.
    2. Select the cell scope: Built-in Mail Provider.
    3. Under Mail sessions, click HTMMailSession_nodeName_serverName and set the Mail transport host.
    4. If the mail transport host is secured, also set Mail transport user ID and Mail transport password.
    5. Click OK.
  11. Click Save Master Configuration, then click Save.
  12. Restart the application server.
  13. If the container did not install successfully, check for any error messages that can help you correct the problem, then repeat this task.

    Check the administrative console or the SystemOut.log file for the application server. On a cluster, check the log for all application servers in the cluster.

Result

The human task container is configured.

What to do next

Continue configuring in the parent topic at step 3.

Terms of use |

Last updated: Tue Feb 21 17:31:26 2006

(c) Copyright IBM Corporation 2005.
This information center is powered by Eclipse technology (http://www.eclipse.org)