Use the administrative console to dynamically specify the
monitoring function to publish service component events to the Common Event Infrastructure server.
Before you begin
You must enable the diagnostic trace service, just as you
would with the logger. After you restart your server you would invoke
the events you want to monitor once, because that will cause them
to appear on the list of events available for monitoring.
About this task
This method of selecting events for monitoring is used for
applications that have already been deployed on a process server.
Events that are specified in a .mon file that is deployed with the
application on the process server are monitored by the
Common Event Infrastructure (CEI) database
regardless of any changes you make here. For those events, you can
only specify a greater level of detail to be captured and published
to the CEI database. The output that is published to the CEI database
is very similar to that published by loggers.
Procedure
- From the administrative console, click Troubleshooting
> Logging and tracing.
- Click Change Log Detail levels
- The list of components, packages, and groups displays all
the components that are currently registered on the running server;
only process server events that have been invoked at least once appear
on this list. All process server events that can be logged are listed
under one of the components that start with the name WBILocationMonitor.CEI.
- To make a static change to the configuration, click the Configuration tab.
- To change the configuration dynamically, click the Runtime tab.
- Select an event or group of events to monitor.
- Click the level of detail that you want to capture for
each event.
Note: Only the levels FINE, FINER, and FINEST
are valid for CEI events.
- Click Apply, and then Save.
- Click OK.
- If you made a static change to the configuration, then
you will have to restart the process server for the changes to take
effect.
Results
You can view the monitored event results in the Common Base
Event browser.