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
- If you are preparing a clustered Business Process
Choreographer setup, create the cluster.
- If you are using the WebSphere® MQ Java™ Message
Service (JMS) provider, you must create the queue manager and queues: Perform Creating the queue manager and queues for the business process container. If you are using the default
messaging JMS provider do not perform this step.
- Create the database: Perform Creating the database for the business process container.
- If you are using a Network
Deployment environment: Perform Granting permission to the JDBC driver on the deployment manager.
- 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.
- In the administrative console, select the server
where you want to install the business process container. Click .
Where serverName is the name of the application server
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.
- Go to the Business Process Container settings. On the Configuration tab,
under Container Settings, expand Business
process container settings, and click Business process
container.
- 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.
- Start the installation wizard. In the Additional
Properties section, click the link Business process
container installation wizard.
- Select the database configuration (wizard step 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.
- For the Implementation class name use
the default class name that is provided for the JDBC driver implementation.
- 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, you it must be defined in .
- 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.
Draft comment:
This will be required for Cloudscape Derby
- Enter the Data source password for the
data source user name. This is not required for a Cloudscape database.
- 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 Installation wizard
settings page and the product documentation for your database system.
- Click Next to go to the next step in
the installation wizard.
- Select the JMS provider and security (wizard step 2):
- In the drop-down list for JMS provider,
select the messaging service for the business process container to use.
- For default messaging, select Default messaging provider.
- For WebSphere MQ, select WebSphere MQ.
- Use the default value for Queue Manager.
If you are using the default messaging provider, this field is ignored.
- If you are using the WebSphere MQ JMS provider and you
have not defined the WebSphere environment variable ${MQ_INSTALL_ROOT},
make sure that the Classpath points to the WebSphere MQ Java lib directory.
- For the JMS user ID, enter a user ID
that has administration rights for the messaging service. On Linux® and UNIX® systems, use root. On Windows systems,
use the user ID that is used to start WebSphere Process Server.
- For the JMS password, enter the password
for the JMS user ID.
- For the JMS API User ID, enter the user
ID that is to be used when processing asynchronous API calls.
- For the JMS API Password, enter the password
for the JMS API User ID.
- For the Administrator security role mapping,
enter the name of the group, defined in the domain's user registry, that will
map onto the role of Business Process Administrator. On Windows
systems, for example, you can specify the group Administrators.
- For the System monitor security role mapping,
enter the name of the group to map onto the role of Business Process System
Monitor. On Windows systems, for example, you can specify the group
Administrators.
- Click Next to go to the next step in
the installation wizard.
- 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:
- Select Select existing JMS resources.
- Use the Connection Factory drop-down
list to select BPECF.
- Use the Internal Queue drop-down list
to select BPEIntQueue.
- Use the External Request Processing Queue drop-down
list to select BPEApiQueue.
- Use the Hold Queue drop-down list to
select BPEHldQueue.
- Use the Retention Queue drop-down list
to select BPERetQueue.
- To install Business Process Choreographer
Explorer, select the check box; otherwise, clear the check box. If you do not install Business Process Choreographer Explorer now, you
can install it later, as described in Installing and starting Business Process Choreographer Explorer.
- To use the Common Event Infrastructure, select Enable
Common Event Infrastructure logging for all processes running in this container.
- To enable the audit log, select Enable
audit logging for all processes running in this container.
- Click Next to view the summary (wizard step
4).
- 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.
- To make corrections, click Previous.
- To install the business process container and define its resources,
click Finish. The progress is shown
on the Installing page.
- If the installation did not succeed, check for any error messages
that can help you correct the problem, then try again.
- If the installation succeeded, click Save Master Configuration,
then click Save.
- If the application server where you configured Business Process
Choreographer is in a cluster, perform Customizing the business process container resources in a cluster.
- Restart the application server.
- Verify that the business process container has
started successfully: In the administrative console, select verify that the status of the application named BPEContainer_scope is
started, where scope is nodeName_serverName if
you installed the business process container on an application server. If
you installed the business process container on a cluster scope is
the cluster name.
Result
The business process container is configured.What to do next
Continue configuring
in the parent topic at
step
3.