This describes how to use a script to configure the event collector
and database tables that are necessary for the Business Process Choreographer
Observer.
Before you begin
- A database is available.
- The CLASSPATH environment variable contains the JDBC driver for your database.
- You have to create an XA data source manually using the application server's
administrative console. The data source must point to the database.
Steps for this task
- Change to the Business Process Choreographer subdirectory where
the configuration scripts are located.
On Windows
® systems, enter:
cd install_root\ProcessChoreographer\config
On UNIX
® and Linux
® systems,
enter:
cd install_root/ProcessChoreographer/config
- Start the script to set up the event collector.
On Windows systems,
enter:
setupEventCollector.bat [-conntype SOAP | RMI | JMS | NONE]
( [-node nodeName] -server serverName ) | ( -cluster clusterName )
[ -remove [-silent]]
On UNIX and Linux systems, enter:
setupEventCollector.sh [-conntype SOAP | RMI | JMS | NONE]
( [-node nodeName] -server serverName ) | ( -cluster clusterName )
[ -remove [-silent]]
Where:
- conntype SOAP | RMI | JMS | NONE
- The connection mode that wsadmin tool uses.
- node nodeName
- The name of the node. This parameter is optional. The default value is
the local node.
- server serverName
- The name of the server. If you do not specify the option -conntype
none, this parameter is optional.
- cluster clusterName
- clusterName If you do not specify the option -conntype
none, this parameter is optional.
- remove
- Specify this option to remove the event collector. If you do not specify
this option, the default is that the event collector will be configured.
- silent
- This option can only be used with the remove option.
It causes the script to not output any prompts. This parameter is optional.
Note: In
a standalone server environment:
- Include the -conntype NONE option only if the application
server is not running.
- If the server is running and global security is enabled, include the -user and -password options.
- If you are not configuring the default profile, add the -profileName option.
You see the Commands Menu:Commands Menu
1) Prepare a database for the Event Collector
2) Install the Event Collector application
3) Remove the Event Collector application and related objects
4) Change configuration settings of an installed Event Collector
0) Exit Commands Menu
Note: If you started the script in local
mode, that is, with the -conntype none parameter and without
specifying a server or cluster, only menu items 0 and 1 are displayed.
- Select option 1 to prepare a database for the event collector.
- When you see the commands menu:
Select the type of your DBMS :
'd' ... DB2
'c' ... Cloudscape
'7' ... DB2 V7 on z/OS
'8' ... DB2 V8 on z/OS
'o' ... Oracle
'x' ... Exit
Your selection : [c]
You see the Commands Menu:
- Select your database type.
- For DB2, enter d.
- For Cloudscape, enter c.
- For DB2 V7 on z/OS, enter 7.
- For DB2 V8 on z/OS, enter 8.
- For Oracle, enter o.
- Enter the database settings.
- For DB2, enter the following:
- Either the database name, or an alias, for example BPEDB.
- The user ID and password to connect to the database, for example, db2admin.
- The password for user ID.
- The database schema to be used for the database objects. If you specify
a schema that does not exist, it is created. If you enter a space character
or leave the field empty, the schema of the user ID specified in a. is used.
- For Cloudscape, enter the following:
- The fully qualified path to the database, for example, d:\w\p\profiles\Srv01\databases\BPEDB.
- The database schema to be used for the database objects. If you specify
a schema that does not exist, it is created. If you enter a space character
or leave the field empty, the default schema is used (normally APP)
.
- If you are prompted to stop the server, do so, then press c to
continue.
- For Oracle, enter the following:
- The database name, for example, BPEDB.
- The host name where the database resides, for example, localhost.
- The port number where the Oracle listener is listening, for example, 1521.
- The user ID to connect to the database, for example, system.
- The password for the user ID.
After checking the connection, the database is prepared.
- Check for any errors. If any errors occur, check the
log file setupEventCollector.log that is located in the logs subdirectory
of the profile directory. For example, on Windows, if your profile is named myServer and
your profiles are stored in install_root\profiles,
the log file is located in install_root\profiles\myServer\logs.
- Install the event collector application. When you see
the Commands Menu:
Commands Menu
1) Prepare a database for the Event Collector
2) Install the Event Collector application
3) Remove the Event Collector application and related objects
4) Change configuration settings of an installed Event Collector
0) Exit Commands Menu
Select option 2 to install
the Business Process Choreographer event collector application. You
see the JNDI name prompt:Specify the JNDI name of the database where the WebSphere BPC Event
Collector should store the collected events.
Enter '?' to get a list.
Your selection : [jdbc/BPEDB]
- Enter the JNDI name that is used to connect to the database. You can also enter ? to get a list of all registered
data sources.
- Enter the name of the schema for the database tables in which the
collected events will be stored. To use the schema specified in the data source
definition, enter a space character or leave the field empty.
- Enter the JMS user ID to authenticate with the Common Event Infrastructure
(CEI) bus. If the CEI bus has security disabled, you can leave this empty.
If you specify a user ID, also enter a password at the next prompt. All required objects are created and the enterprise application
is installed. Success is indicated by the message:
WebSphere Business Process Choreographer Event Collector
installed successfully!
- If there were no error messages, enter y to save
the configuration. Otherwise, enter n to discard the changes
and keep your original configuration. If there were errors, check
the log file named setupEventCollector.log, which is located
in the logs directory of the profile, for example, on
Windows, if your profile is named myServer and your profiles
are stored in install_root\profiles, the
log file is located in install_root\profiles\myServer\logs.
- If CEI logging is not enabled on the server, you see the following:
Checking if CEI event logging is enabled ...
Warning: The Business process container of server_name has CEI event
logging disabled.
To allow the Event Collector to work correctly, CEI event logging is required.
Do you want to enable the CEI event logging on server_name? (y/n)
To
enable CEI logging, enter y, otherwise enter n.
- If you are prompted to start the application, enter y to
start the application or n to not start it.
- To activate all settings, restart the server.
Result
The Business Process Choreographer event collector is
installed and configured.
What to do next
Configure the Business Process
Choreographer Observer with step 2. If you want to, you can use option 4 in the command menu to change configuration
parameters for the event collector, this is described in support document
7008553.