There are several administrative tasks that you can perform on WebSphere® Business Monitor outside the WebSphere Business Monitor Administration
extension in the WebSphere Application
Server administrative
console.
Starting and stopping enterprise applications
Follow these steps for starting and stopping one or more of the
installed enterprise applications of WebSphere Business Monitor through
the WebSphere Application
Server administrative
console.
Managing the logging and tracing
Follow these steps to manage the logging and tracing feature in WebSphere Business Monitor using the WebSphere Application
Server administrative
console. Tasks include enabling the logging and tracing for the
application server on which the WebSphere Business Monitor components
are deployed and setting the logging and tracing levels for each of the WebSphere Business Monitor components.
Enabling and disabling the CEI store
The emission of events from the runtime engine to the WebSphere Business Monitor occurs as message transmissions
using the Common Event Infrastructure (CEI).
Changing the data sources names
The data sources names for WebSphere Business Monitor databases
are hardcoded. To change those names, perform the following steps:
Changing DB2 Alphablox data source user name and password
The user name and password of data sources that are created on
the DB2® Alphablox for the Dashboard
Client can be changed using the DB2® Alphablox administrative
console.
Setting the work request queue size
For better performance, you need to set the Work request
queue size value for the DeserializationWorkManager to
correspond with the Event processing batch size system
property of the WebSphere Business Monitor.
Configuring CEI Bus on a remote WebSphere Application Server cell WebSphere Business Monitor performs
its operation by reading the messages that contain the events from the queue
destination named Monitor_Bus_Queue_Destination that gets these events from
the Common Events Infrastructure (CEI) Bus. The events are emitted to the
CEI Bus by the applications that runs on the BPEL engine in WebSphere Process
Server.