In a secure environment, you must configure the server-to-server
Secure Sockets Layer (SSL) if you want to use events from an IBM® Business
Process Manager or
from IBM Business
Monitor server
in a different cell. The process described here applies to events
that use the Dynamic Event Framework (DEF) in IBM Business
Monitor V8.5.5.
If you are upgrading from an existing Business Monitor topology
and plan to continue to use CEI, which is deprecated, these procedures
would not apply to your environment.
Before you begin
To use the Dynamic Event Framework with
IBM BPM, you
must be using
IBM BPM V8.5.5
or later. The
IBM BPM and
Business Monitor profiles
must be in different cells. The cells must have unique names.
About this task
The following steps are required to make the communication
between the
Business Monitor server
and a remote server work with HTTPS in a multiple-cell environment.
The remote server can be another
Business Monitor server
or a cell on a server that is running
IBM Business
Process Manager.
Procedure
- Import the remote event source server WebSphere® Application
Server root SSL
certificate into Business Monitor:
- In the Business Monitor server WebSphere Application
Server administrative
console, click .
- Enter the Host name, secure SOAP Port of
the event source server or deployment manager profile (the IBM BPM server
or the remote Business Monitor cell),
and Alias, and click Retrieve signer
information.
- Click Apply and save your changes.
- Import the Business Monitor root SSL
certificate into the remote event source server:
- In the WebSphere Application
Server server WebSphere Application
Server administrative
console, click .
- Enter the Host name, secure SOAP Port of
the Business Monitor server
or deployment manager profile, and Alias, and
click Retrieve signer information.
- Click Apply and save your changes.
- To configure the remote data source, open the Dmgr_profile\bin directory
on the remote event source server and run the wbmConfigureQueueBypassDatasource wsadmin
command. Run the command on each IBM Business
Process Manager V8.5.5 cell
that sends events to Business Monitor.
For
information about running the wsadmin tool, see Configuring the environment using wsadmin commands.
The wbmConfigureQueueBypassDatasource command
creates the data source that enables the remote server to send information
to the Business Monitor database.
You must run the command on the remote deployment manager. The wbmConfigureQueueBypassDatasource command
accepts the following parameters: - -monitorCell
cell_name: The name of the cell where Business Monitor is installed or the cell of the remote Business Monitor server if you are configuring communication
between two Business Monitor cells.
- -databaseType: Specify db2, oracle,
or sqlserver.
- -jdbcProvider JDBC_provider_name:
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.
- -driverType: For DB2® and Oracle databases,
specify either 2 or 4. For Oracle databases,
specify 2 for an OCI driver or 4 for a Thin driver. For z/OS®, specify either 2 or 4. This value is not used for SQL Server.
- -databaseName Monitor_database_name:
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:
The host name of the database server.
- -databaseServerPort database_server_port:
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:
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>.
The following example uses Jython to create
a DB2 data source:
AdminTask.wbmConfigureQueueBypassDatasource('[-monitorCell hostNameCell01
-databaseType db2 -jdbcProvider "DB2 Universal JDBC Driver Provider (XA)" -driverType 4
-databaseName MONITOR -databaseServerName hostname.company.com
-databaseServerPort 50000 -user db2user -password db2user_password]')
- Enable event emission.
- Restart both servers or deployment managers and clusters.
- Create an authentication alias for the Business Monitor server
to use to connect to the remote event source server. The
default user name is the same as the primary administrative user name
for the remote event source server. You must create an alias for that
name. In Step 7,
you associate this alias to the remote event source when you run the wbmRegisterDefEventSource() command.
- In the administrative console on the Business Monitor server
where your monitor model is to be deployed, select and
click New.
- Enter a name for the alias, such as RemoteEmitterAlias.
In the User ID and Password fields,
enter the user ID (such as wasadmin) and password
for the primary administrative user on the remote event source server.
- On the Business Monitor server,
register the remote event source in one of the following ways:
- Add remote event sources.
- Open the Dmgr_profile\bin directory
and start a wsadmin session, with Jython script. Run the MBean administrative
task wbmRegisterRemoteEventSources command.
Then, run AdminConfig.save() to save your changes.
This
command creates both the local configuration and the configuration
on the remote system. Supply the following information:
- -hostName: Host name or IP address of the
deployment manager for the remote cell.
- -port: SOAP port number of the deployment
manager for the remote cell.
- -connectionAuthAlias: Authentication alias
for connecting to the deployment manager of the event source cell.
AdminTask.wbmRegisterRemoteEventSources('[-hostName host_name -port port_number -connectionAuthAlias authorization_alias]')
- If you plan to use IBM Process Designer to automatically
generate a monitor model and deploy it for a process application,
see Configuring a target Business Monitor server.
- Check that the remote event source is enabled by completing
the following steps:
- Log in to the WebSphere Integrated System Console.
- Click .
- On the Event Sources panel, verify
that you see an entry for your IBM BPM server. If there is a green
check mark for that server, the server is running.