Use the installation wizard to install and configure the business process container.
Access the business process container installation wizard by clicking
. This page describes the installation wizard fields, in the order that they display in the wizard.You must create a new data source that is only used by Business Process Choreographer. When you select your JDBC provider, appropriate defaults are inserted in the Implementation class name field.
Type | Value |
---|---|
Mandatory | Yes |
Data type | Drop-down list |
Choices | Create a new XA data source:
|
The Java class name of the Java Database Connectivity (JDBC) driver implementation. Appropriate defaults are inserted in this field after you select your JDBC provider, there is no need to change this value.
Type | Value |
---|---|
Mandatory | Yes |
Data type | String |
Default for Cloudscape 5.1 (Cloudscape JDBC Provider (XA)) | com.ibm.db2j.jdbc.DB2jXADataSource |
Default for DB2 UDB (DB2 Legacy CLI-based Type 2 JDBC Driver (XA)) and for DB2 z/OS (DB2 Legacy CLI-based Type 2 JDBC Driver (XA)) | COM.ibm.db2.jdbc.DB2XADataSource |
Default for DB2 UDB (DB2 Universal JDBC Driver Provider (XA)) and for DB2 z/OS (DB2 Universal JDBC Driver Provider (XA)) | com.ibm.db2.jcc.DB2XADataSource |
Default for Informix (Informix JDBC Driver (XA)) | com.informix.jdbcx.IfxXADataSource |
Default for Oracle 9i and 10g (Oracle JDBC Drivers (XA)) | oracle.jdbc.xa.client.OracleXADataSource |
Default for SQL Server 2000 (DataDirect ConnectJDBC type 4 JDBC driver for MS SQL Server (XA)) | com.ddtek.jdbcx.sqlserver.SQLServerDataSource |
Default for SQL Server 2000 (WebSphere-embedded ConnectJDBC driver for MS SQL Server (XA)) | com.ibm.websphere.jdbcx.sqlserver. SQLServerDataSource |
For more information about properties and settings for the database, refer to Vendor-specific data sources minimum required settings.
The path to the Java archive (JAR) file or zip file that contains the Java Database Connectivity (JDBC) driver. The JDBC driver provides the data source implementation class. If the database is remote, this path indicates where the JDBC driver is installed on the client computer.
Type | Value |
---|---|
Mandatory |
|
Data type | String |
Default for Cloudscape 5.1 | ${CLOUDSCAPE_JDBC_DRIVER_PATH}/db2j.jarThe value for ${CLOUDSCAPE_JDBC_DRIVER_PATH} is predefined and does not need to be set. |
Default for DB2 UDB (DB2 Legacy CLI-based Type 2 JDBC Driver (XA)) and for DB2 z/OS (DB2 Legacy CLI-based Type 2 JDBC Driver (XA)) | ${DB2_JDBC_DRIVER_PATH}/db2java.zipThe value for ${DB2_JDBC_DRIVER_PATH} depends on the DB2 Client installation directory and must be set explicitly in Environment > WebSphere Variables. Typical values are:
|
Default for DB2 UDB (DB2 Universal JDBC Driver Provider (XA) types 2 and 4) and for DB2 z/OS (DB2 Universal JDBC Driver Provider (XA) types 2 and 4) | ${DB2UNIVERSAL_JDBC_DRIVER_PATH}/ db2jcc.jar ${UNIVERSAL_JDBC_DRIVER_PATH}/ db2jcc_license_cu.jar ${DB2UNIVERSAL_JDBC_DRIVER_PATH}/ db2jcc_license_cisuz.jarThe value for ${DB2UNIVERSAL_JDBC_DRIVER_PATH} depends on the installation root directory of the corresponding DB2 Client or DB2 Connect, and must be set in Environment > WebSphere Variables. Typical values for ${DB2UNIVERSAL_JDBC_DRIVER_PATH} are:
|
Default for Informix | ${INFORMIX_JDBC_DRIVER_PATH}/ifxjdbc.jar ${INFORMIX_JDBC_DRIVER_PATH}/ifxjdbcx.jarThe value for ${INFORMIX_JDBC_DRIVER_PATH} depends on the JDBC driver installation directory and must be set in Environment > WebSphere Variables. |
Default for Oracle | ${ORACLE_JDBC_DRIVER_PATH}/ojdbc14.jarThe value for ${ORACLE_JDBC_DRIVER_PATH} depends on the Oracle client installation or JDBC driver installation directory and must be set in Environment > WebSphere Variables. |
Default for SQL Server 2000 (DataDirect ConnectJDBC type 4 JDBC driver for MS SQL Server (XA)) | ${CONNECTJDBC_JDBC_DRIVER_PATH}/sqlserver.jar ${CONNECTJDBC_JDBC_DRIVER_PATH}/base.jar ${CONNECTJDBC_JDBC_DRIVER_PATH}/util.jar ${CONNECTJDBC_JDBC_DRIVER_PATH}/../spy/spy.jarThe value for ${CONNECTJDBC_JDBC_DRIVER_PATH} depends on the installation directory of the DataDirect ConnectJDBC driver, and must be set in Environment > WebSphere Variables. |
Default for SQL Server 2000 (WebSphere embedded ConnectJDBC driver for MS SQL Server (XA)) | ${WAS_LIBS_DIR}/sqlserver.jar ${WAS_LIBS_DIR}/base.jar ${WAS_LIBS_DIR}/util.jar ${WAS_LIBS_DIR}/spy.jar |
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.
Type | Value |
---|---|
Mandatory |
|
Data type | String |
Default | The user ID that is currently logged on to the administrative console. |
The password for the data source user ID.
Type | Value |
---|---|
Mandatory |
|
Data type | String |
Default | None |
Extra parameters that are required by the database system.
Type | Value |
---|---|
Mandatory | Yes |
Data type | String |
Data format | Multiple lines of Property=Value |
Minimum required properties | Refer to Vendor-specific data sources minimum required settings. |
Properties that are not listed in this table | Properties that are optional or that are ignored are not listed in this table. For information about such properties, refer to the documentation for your JDBC provider. |
Required properties | All of the required properties for each JDBC provider are described below. |
Required properties for Cloudscape |
Remember: After running the wizard, make sure that
you create the database in the location specified for databaseName.
|
Required properties for DB2 UDB and DB2 z/OS (DB2 Legacy CLI-based Type 2 JDBC Driver (XA)) |
|
Required properties for DB2 UDB and DB2 z/OS (DB2 Universal JDBC Driver Provider (XA)) |
|
Required properties for Informix |
|
Required properties for Oracle 9i OCI and Oracle 10g OCI |
|
Required properties for Oracle 9i thin and Oracle 10g thin |
|
Required properties for SQL Server 2000 (DataDirect ConnectJDBC type 4 JDBC driver for MS SQL Server (XA) or WebSphere embedded ConnectJDBC driver for MS SQL Server (XA)) |
|
Used to authenticate the connection to the Java Message Service (JMS) provider. 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.
Type | Value |
---|---|
Mandatory | Yes |
Data type | String |
Restrictions | If you use Websphere MQ, the JMS user ID must be less than or equal to 12 characters. For example, the default Windows NT user ID, Administrator, is not valid with WebSphere MQ because the ID contains 13 characters. |
Default | The user ID that you used to log into the administrative console. |
The password for the Java Message Service (JMS) user ID.
Type | Value |
---|---|
Mandatory | If you selected WebSphere JMS Provider; otherwise, this field is disabled. |
Data type | String |
Default | None |
The root context used for the Web service.
Type | Value |
---|---|
Mandatory | Yes |
Data type | String |
Default when configured on a server | /BFMIF_${nodeName}_${serverName} |
Default when configure on a cluster | /BFMIF_${clusterName} |
The user ID that the business process container message-driven bean (MDB) uses when processing asynchronous API calls.
Type | Value |
---|---|
Mandatory | Yes |
Data type | String |
Description | If WebSphere security is enabled, even if you do not use the JMS
API API, you must specify a valid user ID. This ID does not need any special
authorizations. If WebSphere security is enabled and you plan to use the JMS API, this user ID must either be one that is given the appropriate authorities when the process is modeled, or more commonly, it must be a member of a group that was granted the necessary authorities during modeling. The possible staff authorities associated with processes are: Administrator, Reader, and Starter. For activities, a user ID can only perform the sendEvent action if it is a potential owner of the associated receiveEvent. If you want to support all the actions on processes through the JMS API, you can specify a user ID that is a member of the J2EE BPESystemAdministrator role. However, in a production system, the more fine-grained security approach is recommended. |
The password for the JMS API User ID.
Type | Value |
---|---|
Mandatory | If WebSphere security is enabled (even if you do not use the JMS API) |
Data type | String |
The group from the domain user registry that is mapped onto the role of business process administrator.
Type | Value |
---|---|
Mandatory | Yes |
Data type | String |
Default | None |
Restrictions | The group specified must already exist in the domain user registry. The user registry can be the local operating system, Lightweight Directory Access Protocol (LDAP), or custom registry. |
The group from the domain user registry that is mapped onto the role of business process monitor.
Type | Value |
---|---|
Mandatory | Yes |
Data type | String |
Default | None |
Restrictions | The group specified must already exist in the domain user registry. The user registry can be the local operating system, Lightweight Directory Access Protocol (LDAP), or custom registry. |
If this check box is selected, the Business Process Choreographer Explorer is also installed.
Type | Value |
---|---|
Data type | Check box |
Default | selected |
This context root becomes part of the URL for the Business Process Choreographer Explorer.
Type | Value |
---|---|
Data type | String |
Default | /bpc |
Restrictions | If you configure multiple instances of the Business Process Choreographer Explorer, each instance must have a root context that is unique in the WebSphere cell. |
Common Event Infrastructure (CEI) logging can be enabled or disabled.
Type | Value |
---|---|
Data type | Check box |
Default | Not selected |
If this check box is selected, the Business Process Choreographer Observer and event collector are also installed.
Type | Value |
---|---|
Data type | Check box |
Mandatory | No |
Default | Not selected (the Business Process Choreographer Observer will not be installed) |
Dependencies | CEI logging must be enabled before you can select this option. |
The user ID the Business Process Choreographer Observer uses to authenticate against the CEI bus.
Type | Value |
---|---|
Mandatory | If you install the Business Process Choreographer Observer |
Data type | String |
The password for the JMS API User ID.
Type | Value |
---|---|
Mandatory | If you install the Business Process Choreographer Observer |
Data type | String |
Copyright IBM Corporation 2005, 2006.
This information center is powered by Eclipse technology (http://www.eclipse.org)