Configuring Common Event Infrastructure (deprecated)

In IBM® Business Process Manager Advanced V8.5.6, the Common Event Infrastructure (CEI) is not enabled by default. You must, therefore, set up CEI in the IBM BPM cell so that you can send events to CEI if you are using it.

Before you begin

Before you complete this task, make sure that you verify the following information:

The value that you use for -datasourceJndiName (for example, jdbc/SharedDb) is accessible from the cluster scope.
The value that you use for -datasourceAuthAlias (for example, BPM_DB_ALIAS) exists and has the authority to access the database.
The values that you use for -jmsAuthAlias -user and -password (for example, celladmin/celladmin) correspond to a valid user.

About this task

You run a series of wsadmin commands to enable CEI.

Procedure

Navigate to the following directory: DMGR_PROFILE/bin/wsadmin
Configure CEI by entering the wbmDeployCEIEventService command:
```
AdminTask.wbmDeployCEIEventService('[-busMember [-cluster clusterName -datasourceJndiName jndiName -datasourceAuthAlias authAlias -databaseSchema schemaName -createTables true] -eventService [-cluster clusterName] -jmsAuthAlias [ -user userName -password userPassword]]')
```
Where:

-busMember -cluster clusterName

is the name of the BPM messaging engine cluster or the single cluster name if a single cluster was created.

-busMember -datasourceJndiName value

is an existing value (for example, jdbc/SharedDb)

-busMember -datasourceAuthAlias value

is an existing value (for example, BPM_DB_ALIAS)

-eventServices -cluster clusterName

is the name of the BPM support cluster or the single cluster name if a single cluster was created.

-jmsAuthAlias -user userName

is an existing name and is a member of the Administrator group. It must be the same on both the Process Server deployment manager and on the IBM Business Monitor deployment manager in a cross-cell configuration.

-jmsAuthAlias -password userPassword

is an existing password and is a member of the Administrator group. It must be the same on both the Process Server deployment manager and on the IBM Business Monitor deployment manager in a cross-cell configuration.
An example of the wbmDeployCEIEventService command follows:
```
AdminTask.wbmDeployCEIEventService('[-busMember [-cluster MECluster -datasourceJndiName jdbc/SharedDb -datasourceAuthAlias BPM_DB_ALIAS -databaseSchema CEIME -createTables true] -eventService [-cluster SupCluster] -jmsAuthAlias [ -user celladmin -password celladmin]]')
```
Save the configuration changes by entering the following command:
```
AdminConfig.save()
```
Verify that the command you entered in step 2 was successful by completing the following steps:
1. Restart the deployment manager and the clusters.
2. Check to make sure that the CEI bus was created.
3. Check to make sure that the messaging engine at the CEI bus can be started.

Enable Business Process Choreographer to emit CEI events:

DMGR_PROFILE/bin/wsadmin -connType NONE -f WAS_home\ProcessChoreographer\admin\setStateObserver.py -cluster clusterName -enable CEI

Where:

-cluster clusterName: is the name of the cluster where Business Process Choreographer is configured

An example of enabling Business Process Choreographer follows:

DMGR_PROFILE/bin/wsadmin -connType NONE -f P:\bpm8500\ProcessChoreographer\admin\setStateObserver.py -cluster AppCluster -enable CEI

Optional: If you are migrating to IBM BPM V8.5.6 from an earlier version, or if CEI and Business Process Choreographer are deployed on different clusters, configure the CEI emitter factory:
```
DMGR_PROFILE/bin/wsadmin -f WAS_home\util\migration\scripts\setCEIDestination.py -a applicationClusterName -s supportClusterName -no-sync
```
Where:

-a applicationClusterName

is the name of the application cluster

-s supportClusterName

is the name of the support cluster

–no-sync

is an optional parameter that specifies whether to synchronize the changes to all nodes. By default, no-sync is false, which means that the node synchronize command is called immediately after the change. If no-sync is true, the node synchronize command is not called automatically and you must synchronize the nodes later so that the changes take effect.

An example of configuring the CEI emitter factory follows:
```
DMGR_PROFILE/bin/wsadmin -f P:\bpm8500\util\migration\scripts\setCEIDestination.py -a AppCluster -s SupportCluster 
```
Verify that the command you entered in step 5 was successful by completing the following steps from the administrative console:
1. Click Servers > Clusters > WebSphere application server clusters > cluster_name > Business Process Choreographer > Business Flow Manager.
2. Make sure that Enable Common Event Infrastructure logging is enabled.
3. Click Servers > Clusters > WebSphere application server clusters > cluster_name > Business Process Choreographer > Human Task Manager.
4. Make sure that Enable Common Event Infrastructure logging is enabled.
5. Click Service Integration > Common Event Infrastructure, and then click Event emitter factories > Default Common Event Infrastructure emitter > Event service transmission.
6. Make sure that the event service JNDI name is set to the cluster_name you provided (for example, SupCluster).