Business process container installation wizard settings

Use the installation wizard to install and configure the business process container.

Access the business process container installation wizard by clicking Servers > Application servers > server_name > Business Process Container Settings > Business process container > Business process container installation wizard. This page describes the installation wizard fields, in the order that they display in the wizard.

Step 1 database configuration:

Step 2 JMS provider and security:

Step 3 Business Process Choreographer Explorer and logging:

Attention: After the container is configured, you can only change the logging options, retry limit, and retention queue message limit. If you want to change any of the other values, you must remove the existing Business Process Choreographer configuration and then create a new one.

JDBC provider

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:
  • Cloudscape 5.1 (Cloudscape JDBC Provider (XA))
  • DB2 UDB 8.1 & 8.2 (DB2 Legacy CLI-based Type 2 JDBC Driver (XA))
  • DB2 UDB 8.1 & 8.2 (DB2 Universal JDBC Driver Provider (XA) type 2)
  • DB2 UDB 8.1 & 8.2 (DB2 Universal JDBC Driver Provider (XA) type 4)
  • DB2 z/OS 7 & 8 (DB2 Legacy CLI-based Type 2 JDBC Driver (XA))
  • DB2 z/OS 7 & 8 (DB2 Universal JDBC Driver Provider (XA) type 2)
  • DB2 z/OS 7 & 8(DB2 Universal JDBC Driver Provider (XA) type 4)
  • Informix 9.4 & 10.0(Informix JDBC Driver (XA))
  • Oracle10g OCI (Oracle JDBC Driver (XA))
  • Oracle 10g thin (Oracle JDBC Driver (XA))
  • Oracle 9i OCI (Oracle JDBC Driver (XA))
  • Oracle 9i thin (Oracle JDBC Driver (XA))
  • SQL Server 2000 (DataDirect ConnectJDBC type 4 JDBC driver for MS SQL Server (XA))
  • SQL Server 2000 (WebSphere embedded ConnectJDBC driver for MS SQL Server (XA))

Implementation class name

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.

Class path (for JDBC provider)

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
For Cloudscape
No, the JDBC driver is already on the WebSphere class path.
For DB2 UDB, DB2 z/OS, Informix, Oracle, SQL Server
Yes
Data type String
Default for Cloudscape 5.1
${CLOUDSCAPE_JDBC_DRIVER_PATH}/db2j.jar
The 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.zip
The 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:
On Windows:
c:\Program Files\IBM\SQLLIB\java
On Linux, AIX and HP-UX:
/home/db2inst1/sqllib/java
On Solaris:
/export/home/db2inst1/sqllib/java
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.jar
The 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:
On Windows:
c:\Program Files\IBM\SQLLIB\java
On Linux, AIX and HP-UX:
/home/db2inst1/sqllib/java
On Solaris:
/export/home/db2inst1/sqllib/java
Default for Informix
${INFORMIX_JDBC_DRIVER_PATH}/ifxjdbc.jar
${INFORMIX_JDBC_DRIVER_PATH}/ifxjdbcx.jar
The 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.jar
The 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.jar
The 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

Data source user name

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
For Cloudscape
No
For DB2 UDB, DB2 z/OS, Informix, Oracle, SQL Server
Yes
Data type String
Default The user ID that is currently logged on to the administrative console.

Data source password

The password for the data source user ID.

Type Value
Mandatory
For Cloudscape
No
For DB2 UDB, DB2 z/OS, Informix, Oracle, SQL Server
Yes
Data type String
Default None

Custom Properties

Extra parameters that are required by the database system.

CAUTION:
It is not recommended that you change any of the optional properties before you have configured and verified that your business process container is working. Making such changes belongs to advanced tuning and troubleshooting, and can cause your system to stop working.
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
databaseName = ${USER_INSTALL_ROOT}/databases/BPEDB
Required string. Defines which database to access. The value must be a fully qualified path.
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))
databaseName=BPEDB
Required string. For DB2 UDB it defines the name of the catalog entry for the database to access. For DB2 z/OS it defines which subsystem contains the database.
Required properties for DB2 UDB and DB2 z/OS (DB2 Universal JDBC Driver Provider (XA))
databaseName=BPEDB
Required string. For DB2 UDB it defines which database to access. For DB2 z/OS it defines which subsystem contains the database.
driverType=2
Required integer. The JDBC connectivity-type of a data source. The only permitted values are 2 or 4.
serverName=hostname
Required string for driver type 4. For the type 2 driver this is ignored. The TCP/IP address or host name for the DRDA server. The default is the name of the current computer.
portNumber=50000
Required integer for driver type 4. For the type 2 driver this is ignored. The TCP/IP port number where the DRDA server resides.
Required properties for Informix
databaseName=BPEDB
Required string. The name of the database.
serverName=""
Required string. The name of the Informix instance (not the name of the computer).
Important: There is no default value for this string. You must set it explicitly.
portNumber=1526
Required integer. The TCP/IP port number of the Informix instance. The value "1526" is the default Informix port on Windows. On UNIX it is "61000".
ifxIFXHOST=hostname
Required string. The name of the server that hosts the Informix database. Specifying Localhost does not work.
informixLockModeWait=60
Required integer. By default, Informix throws an exception when it cannot acquire a lock, rather than waiting for the current owner of the lock to release it. To modify this behavior, set this property to the number of seconds to wait for a lock. The default is 60 seconds. Any negative value means to wait forever.
ifxIFX_XASPEC=y
This string property is required to avoid locking issues when multiple users access the same database. Turn on the ifxIFX_XASPEC property by assigning it the value of Y or y. Turn the property off by assigning it the value of N or n. WebSphere Application Server ignores all other values. Your setting for this property overrides the Informix database system setting.
Required properties for Oracle 9i OCI and Oracle 10g OCI
driverType=oci8
Required string. Defines the type of the JDBC driver.
TNSEntryName=BPEDB
Required string. The entry name that is used in tnsnames.ora to identify the database.
URL=jdbc:oracle:oci8:@BPEDB
Required string. The URL specifies the database from which the data source obtains connections.
Required properties for Oracle 9i thin and Oracle 10g thin
driverType=thin
Required string. Defines the type of the JDBC driver.
databaseName=BPEDB
Required string. Defines which database to access.
serverName=hostname
Required string. The name of the server where the Oracle database resides.
portNumber=1521
Required integer. The TCP/IP port number where the JDBC driver resides.
URL=jdbc:oracle:thin:@hostname:1521:BPEDB
Required string. The URL specifies the database and the database host from which the data source will obtain connections.
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))
serverName=hostname
Required string. The name of the computer that is hosting the Microsoft SQL Server or the TCP/IP address in dotted format.
databaseName=BPEDB
Optional string. The name of the database to access.

JMS user ID

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.

JMS password

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

WebService Endpoint context root

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}

JMS API user ID

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.

JMS API password

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

Administrator security role mapping

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.

System monitor security role mapping

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.

Business Process Choreographer Explorer

If this check box is selected, the Business Process Choreographer Explorer is also installed.

Type Value
Data type Check box
Default selected

Context root

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.

Enable audit logging

Audit logging can be enabled or disabled.

Type Value
Data type Check box
Default Not selected

Enable Common Event Infrastructure logging

Common Event Infrastructure (CEI) logging can be enabled or disabled.

Type Value
Data type Check box
Default Not selected

Business Process Choreographer Observer

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.

JMS user ID (for the observer)

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

JMS password (for the observer)

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)