Table-based bus configuration across multiple cells

To enable IBM® Business Monitor to bypass the JMS queue and use the table-based method to receive events from a remote event service, you must create a data source in the remote cell. As part of the instructions in "Configuring IBM Business Monitor to receive events from IBM Business Process Manager V8.5.0 and earlier," run the wbmConfigureQueueBypassDatasource command on the remote deployment manager to create the data source.

Purpose

Important: This command applies only to remote CEI servers.

The wbmConfigureQueueBypassDatasource command creates the data source that enables the remote CEI server to send information to the IBM Business Monitor database. You must run the command on the remote deployment manager.

The data source name is Monitor_<cell_name>__Routing_Database, where <cell_name> is the name of the cell where IBM Business Monitor is installed

For full instructions for setting up table-based event delivery, see Configuring Business Monitor to receive events from IBM BPM V8.5.0 and earlier. Running the wbmConfigureQueueBypassDatasource is the final step. After you run the command and save the configuration changes, you must restart the remote deployment manager or stand-alone server.

Example

The following example uses Jython to create a DB2® data source.
AdminTask.wbmConfigureQueueBypassDatasource('[-monitorCell moncell3 -databaseType db2 -jdbcProvider myProvider -driverType 4 -databaseName MONDB -databaseServerName dbsrv3 -databaseServerPort 50000 -authAlias monDatabaseAlias]')
A sample Jython script named configureQueueBypass.py is provided. The script shows how to pass parameters to the wbmConfigureQueueBypassDatasource command. If the remote CEI event service is running on Process Server 8.0, the script is already installed in <WebSphere_Process_Server_root>/util/WBM. Otherwise, you can copy the script from the app_server_root/scripts.wbm/crossCell directory on the IBM Business Monitor server to the remote deployment manager or stand-alone server.
Before running the script, open the script file in an editor. Find the section that begins with this comment:
# Set the values for the parameters
Replace the sample values with the values for your system. Be sure to remove the comment marker on one of the securityParm = lines.
Run the script using the wsadmin command as follows:
  • Windows profile_root\bin\wsadmin.bat -lang jython -f "<path_to_script>/configureQueueBypass.py"
  • Linux Unix profile_root/bin/wsadmin.sh -lang jython -f "<path_to_script>/configureQueueBypass.py"

Parameters

The wbmConfigureQueueBypassDatasource command accepts the parameters listed in the following table.
Parameter and Value Required? Description Comments
-monitorCell cell_name Required The name of the cell where IBM Business Monitor is installed.

In multiple-cell configurations, use the name of the Business Monitor cell where the monitor model that consumes the events is installed.

The cell name is used in the name of the data source, allowing the remote CEI event service to route events to multiple IBM Business Monitor cells.
-databaseType db2 | oracle | sqlserver Required The type of database. Specify db2, oracle, or sqlserver.
-jdbcProvider JDBC_provider_name Required The name of an existing JDBC provider that supports the database type. The JDBC provider must be defined at the cell scope, which means that the resource is available to any node or server within the cell. You can use the administrative console to get a list of JDBC providers. Click Resources > JDBC > JDBC providers.

For DB2 for z/OS®, it is recommended to use an XA provider if the database is remote from the CEI server, and a non-XA provider if the database is located with the CEI server.

If no jdbcProvider definition exists on the remote WebSphere® Application Server or Process Server, you must create the required jdbcProvider definition.
  1. In the administrative console of your IBM Business Monitor server, select Resources > JDBC > JDBC Providers > MonitorDBProvider to view the definition.
  2. In the administrative console of the remote server, select Resources > JDBC > JDBC Providers. Select the cell scope from the Scope list and click New. Specify the same values as in the definition of the MonitorDBProvider on your IBM Business Monitor server.
-driverType 2 | 4 Required The driver type for the database. For DB2 and Oracle databases, specify either 2 or 4. For Oracle databases, a value of 2 corresponds to the OCI driver and a value of 4 corresponds to the Thin driver.

For SQL Server, specify either 2 or 4. The value is ignored.

-databaseName Monitor_database_name Required The name of the MONITOR database. For DB2 for z/OS databases, this value is the database subsystem name. For other versions of DB2 and for SQL Server, this value is the database name. For Oracle databases, this value is the Oracle system ID.
-databaseServerName database_server_name Required The host name of the database server.  
-databaseServerPort database_server_port Required The port number for the database server. For DB2 databases, the default value is 50000. For Oracle databases, the default value is 1521. For SQL Server databases, the default value is 1433.
-authAlias database_authentication_alias | -user user_name -password password Required if security is enabled Specify either an existing authentication alias for the database, or the user name and password for the database. If a database user name and a password are provided instead of an authentication alias, an authentication alias is created. The authentication alias is named MonitorRoutingDatabaseAlias_ <Monitor_cell_name>