The problem: A business measures model was
imported successfully into WebSphere® Business Monitor administrative
console. Its corresponding Business Process Execution Language (BPEL) .ear
file was successfully installed on the WebSphere Process
Server.
The process instances that belong to this model were created and are running
successfully. The State database tables were created successfully. But no
related data has been created and stored in the State database.
The following steps can help you to investigate and solve this
problem:
- Enable the log details level on the finest level. Refer to Managing the logging and tracing for details on how to
set the log details level.
- Enable the Common Event Infrastructure (CEI) data store. Refer to Enabling and disabling the CEI store for details.
- Create a new process instance in the runtime engine so that new events
will be sent to the Monitor Server.
- Check that the events are generated and sent successfully to the CEI by
logging on to the Common Base Event Viewer application Web page and searching
for the newly created events. Refer to the topic named Viewing monitored
events in WebSphere Process
Server documentation
for details.
- If the events do not exist in the CEI data store, check the BPEL model
deployment on the WebSphere Process
Server.
Refer to the topic named Troubleshooting a failed deployment in WebSphere Process
Server documentation for details
on troubleshooting BPEL deployment.
- If the events exist in the CEI datastore, check that the JMS resources
are created and configured successfully.
- Go to the WebSphere Application
Server administrative
console by selecting .
- Select JMS queue connection factory under the Connection
Factories section, and verify that the JMS queue connection factory
for WebSphere Business Monitor is created with
the name MonitorQueueFactory.
- Select .
- SelectJMS queue under the Destinations section,
and verify that JMS queue is created with the name MonitorQueueDestination.
- Check the trace.log, for exceptions. If there are none, trace the filtering
and correlation trace of the events. If the trace feature is enabled and the
logging level is set to the finest level, you should find that all events
received byWebSphere Business Monitor are in
the trace file. Follow the trace for the first of these events (or any creation
event) to see how it was filtered by each registered process. For each process
registered for the event, a message indicates that the filterAndHandle method
was started and whether the event passed the filter. If the filter was successful,
follow the correlation to see how many instances were returned by the query
for this event entry. If it is a creation event (for example, BPC.BFM.PROCESS.STATUS),
the query should return 0 instances.The creation of a new record for this
process or activity instance should be triggered.