Configuring the business process container using the installation wizard

This describes how to create the necessary resources and then run the business process container installation wizard.

Why and when to perform this task

You must configure the necessary resources and install the business process container application before you can run applications that contain business processes or human tasks.

Steps for this task

  1. If you are preparing a clustered Business Process Choreographer setup:
    1. Create the cluster: Perform Creating a clustered environment.
    2. If you are using the default JMS messaging provider for your cluster:
      1. Make sure that the cluster supports service applications as described in Preparing a server or cluster to support service applications.
      2. Create the database for the message engine's data store. You can either use the same database that is used for the Service Component Architecture (SCA) message engines or a separate database. It is recommended to use one messaging database for all buses that are created by WebSphere Process Server, that is, for the SCA system bus, the SCA application bus, the Common Event Infrastructure bus, and the Business Process Choreographer bus. The database should be accessible to all members of the cluster that hosts the message engine to ensure failover availability of the message engine.
        • If the JMS user is authorized to create tables, the default message engine creates the necessary tables in the database the first time it is accessed.
        • If the JMS user is not authorized to create tables, create the tables before the default messaging provider tries to access the database. You can use the sibDDLGenerator utility that is in the bin subdirectory of your install_root directory to generate a DDL file that can be used to create the tables.
  2. Create the database for Business Process Choreographer: Perform Creating the database for the business process container.
  3. Make sure that the server is started and that you are logged on to the administrative console with a user ID with sufficient administration rights. On Windows® platforms, use the user ID that is used to start WebSphere® Process Server.
  4. In the administrative console, select the server or cluster where you want to install the business process container. Click one of the following:
    • Servers > Application Servers > serverName
    • Servers > Clusters > clusterName

    Where serverName or clusterName is the name of the application server or cluster where you want to install the business process container. In a cluster, you can select any application server, and the business process container is installed simultaneously on all application servers in the cluster.

  5. Go to the Business Process Container settings. On the Configuration tab, under Container Settings, expand Business process container settings, and click Business process container.
  6. Verify that the business process container is not installed. There should be a message indicating that the business process container is not currently installed. If the business process container is already installed, perform Removing the Business Process Choreographer configuration before starting the installation wizard.
  7. Start the installation wizard. In the Additional Properties section, click the link Business process container installation wizard.
  8. Select the database configuration (wizard step 1):
    1. In the JDBC Providers drop-down list, select the entry with the database system, system version and Java™ Database Connectivity (JDBC) driver that you are using. Where possible, the installation wizard offers appropriate default values in the parameter fields. However, with some combinations of browser and platform, no defaults are provided. In this case, you can view the recommended values in Business process container installation wizard settings.
    2. For the Implementation class name use the default class name that is provided for the JDBC driver implementation.
    3. For Classpath enter the location of the Java archive (JAR) or the compressed file that contains the JDBC driver. To use the path variable that is displayed in the text field, it must be defined in Environment > Manage WebSphere Variables.
    4. The Data source user name must be a user ID that has the authority to connect to the database and to modify the data. If the user ID has the authority to create tables and indexes in the database, then the database schema will be updated automatically, when necessary, after applying a service or fix pack. This is not required for a Cloudscape database.
    5. Enter the Data source password for the data source user name. This is not required for a Cloudscape database.
    6. The Custom properties field contains default values for the database that you selected.
      • If you are using a Cloudscape database that is not in the default directory, change the value for the custom property databaseName to specify the fully qualified location of the database.
      • You might need to change or add some other properties. For more information, see the Business process container installation wizard settings page and the product documentation for your database system.
    7. Click Next to go to the next step in the installation wizard.
  9. Select the JMS provider and security (wizard step 2):
    1. For the JMS user ID, the user ID that you enter depends on your messaging system. If you use Websphere default messaging, enter a user ID that has connect, send, receive, and browse rights for the Business Process Choreographer bus, BPC.cellname.Bus, and its destinations. By default, all users that are successfully authenticated with the Websphere Application Server have these permissions. If you use an external JMS provider, such as Websphere MQ, enter a user ID that has connect, send, receive, and browse rights for the queue manger and queues.
    2. For the JMS password, enter the password for the JMS user ID.
    3. For the Webservices Endpoint, enter the Webservice endpoint for the Webservice API.
    4. For the JMS API User ID, enter a user ID from the user registry. This user ID will be used to process asynchronous API calls.
    5. For the JMS API Password, enter the password for the JMS API User ID.
    6. 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.
    7. 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.
    8. Click Next to go to the next step in the installation wizard.
  10. Select the JMS Resources and Business Process Choreographer Explorer (wizard step 3): Either select Create new JMS resources using default values, or perform the following:
    1. Select Select existing JMS resources.
    2. Use the Connection Factory drop-down list to select BPECF.
    3. Use the Internal Queue drop-down list to select BPEIntQueue.
    4. Use the External Request Processing Queue drop-down list to select BPEApiQueue.
    5. Use the Hold Queue drop-down list to select BPEHldQueue.
    6. Use the Retention Queue drop-down list to select BPERetQueue.
  11. Optional: To install Business Process Choreographer Explorer, select the check box; otherwise, clear the check box. You can optionally specify the context root. If you want to have more than one Business Process Choreographer Explorer installed on the same server, at most one of them can use the default context root /bpc.
  12. Optional: To enable the audit log, select Enable audit logging for all processes running in this container.
  13. Optional: To use the Common Event Infrastructure, select Enable Common Event Infrastructure logging for all processes running in this container.
  14. Optional: To install Business Process Choreographer Observer select the check box; otherwise, clear the check box. If you cannot select the check box, make sure that the check box for Enable Common Event Infrastructure logging for all processes running in this container is selected. For JMS User ID, enter a user ID from the user registry that can be used to connect to the CEI bus. For JMS password, enter the associated password.
  15. Click Next to view the summary (wizard step 4).
  16. 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 business process container, but you must create the resources before you activate the business process container. Printing the summary page helps you to create the correct resources.
    1. To make corrections, click Previous.
    2. To install the business process container and define its resources, click Finish. The progress is shown on the Installing page.
  17. If the installation did not succeed, check for any error messages that can help you correct the problem, then try again.
  18. If the installation succeeded, click Save Master Configuration, then click Save.
  19. If you configured Business Process Choreographer in a cluster and you are using the WebSphere MQ JMS provider: Perform Customizing the WebSphere MQ JMS resources in a cluster.
  20. Restart the application server.
  21. Verify that the business process container has started successfully: In the administrative console, select Applications > Enterprise Applications verify that the status of the application named BPEContainer_scope is started. If you installed the business process container on an application server, scope is nodeName_serverName. If you installed the business process container on a cluster scope is the cluster name.

    If you also installed Business Process Choreographer Explorer, you should also see an application running that is named BPCExplorer_scope if it uses the default context root,/bpc or BPCExplorer_scope_contextroot if it does not use the default context root.

    If you installed Business Process Choreographer Observer, you should also see two applications running that are named BPCObserver_scope and BPCECollector_scope

Result

The business process container is configured.

What to do next

Continue configuring in the parent topic at step 2.b.ii.

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