This describes how to use a script to configure Business Process
Choreographer Observer, which allows you to observe the states of running
business processes and human tasks.
Before you begin
- You have configured Business Process Choreographer using the administrative
console or the bpeconfig script.
- You have configured the Business Process Choreographer event collector
but have not yet configured Business Process Choreographer Observer.
- You have enabled the Common Event Infrastructure (CEI) logging for the
container where the business applications run that you want to observe.
- The server must be running.
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 consumer.
On Windows systems,
enter:
setupObserver.bat [-conntype SOAP | RMI | JMS | NONE]
( [-node nodeName] -server serverName ) | ( -cluster clusterName )
[ -remove [-silent]]
On UNIX and Linux systems, enter:
setupObserver.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 Business Process Choreographer event
collector. If you do not specify this option, the default is that the Business
Process Choreographer 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
Working on node 'nodeName', server 'serverName'.
1) Install the Observer application
2) Remove the Observer application and related objects
3) Change configuration settings of an installed Observer
0) Exit Menu
- Select option 1 to install Business Process Choreographer
Observer. You see the JNDI name prompt:
Specify the JNDI name of the database containing the event tables.
Enter '?' to get a list.
Your selection : [jdbc/BPEDB]
- Enter the JNDI name for the data source that is
used by the Business Process Choreographer event collector. 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 are stored. If you leave this field empty or enter a space
character, the default schema is used, which is the schema of the user ID
that is specified in the properties of the data source that you specified
in step 4. All required objects are created and the enterprise application
is installed. Success is indicated by the message:
WebSphere BPC Observer 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 setupObserver.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 you are prompted, enter y to start the application
or n to not start it.
- To activate all settings, restart the server.
Result
Business Process Choreographer Observer
is installed and configured. It can be reached using the URL
http://host:port/bpcobserver/.
Where
host is the name of the host where your application
server is running, and
port is the port number for your
application server (the default is 9080).
What to do next
Continue configuring in the parent topic at step 8.
If you want to, you can use option 3 in the command menu to change configuration
parameters for the Business Process Choreographer Observer, this is described
in support document
7008553.