WebSphere Business Integration Monitor is a standalone monitor that allows you to monitor a variety of servers, one of which is InterChange Server. WebSphere Business Integration Monitor is part of the WebSphere Business Integration Modeler & Monitor product. In order for WebSphere Business Integration Monitor to have the capability to monitor flows in InterChange Server, the following requirements must be met:
For WebSphere Business Integration Monitor installation and deployment instructions, refer to the Deployment guide in the WebSphere Business Integration Monitor documentation. For MQ Workflow adapter installation instructions, refer to the Adapter for MQ Workflow User Guide.
This section covers the following topics:
How WebSphere Business Integration Monitor works with InterChange Server
Steps for enabling flow monitoring in the MQWorkflow adapter
Configuring InterChange Server for flow monitoring
Steps for configuring tracing for flow monitoring
WebSphere Business Integration Monitor is able to monitor an InterChange Server system only when that InterChange Server system is configured with flow monitoring. Flow monitoring is a service that provides a view of the event information associated with each flow as it passes through a collaboration in InterChange Server.
WebSphere Business Integration Monitor can monitor an InterChange Server system only when the MQWorkflow adapter is enabled for flow monitoring. Flow monitoring is a service that provides a view of the event information associated with each flow as it passes through a collaboration in InterChange Server.
Perform the following steps to enable the MQWorkflow adapter with flow monitoring.
WebSphere Business Integration Monitor can monitor an InterChange Server system only when that InterChange Server system is first configured with flow monitoring. Flow monitoring is a service that provides a view of the event information associated with each flow as it passes through a collaboration in InterChange Server. The following sections describe how to configure InterChange Server for flow monitoring.
Steps for configuring the InterChange Server database for flow monitoring
Steps for configuring maximum queue depth for flow monitoring
Steps for configuring tracing for flow monitoring
The InterChange Server database can be configured for flow monitoring only after the InterChange Server installation is complete. Two tools allow you to configure the InterChange Server database for flow monitoring: the InterChange Server Configuration Wizard and System Manager.
Perform the following steps to configure the InterChange Server database for flow monitoring, using either of these tools.
InterChange Server Configuration Wizard |
---|
Click Start > Programs > IBM WebSphere InterChange Server > IBM WebSphere InterChange Server > IBM WebSphere InterChange Server Configuration Wizard. The InterChange Server Configuration Wizard opens. |
System Manager |
---|
From the InterChange Server Component Management view of System Monitor, right-click the ICS instance whose database you want to set up with the flow monitoring service, then select Edit Configuration. The upper-right section of System Manager becomes a tool from which you can edit the InterchangeSystem.cfg file. |
Figure 17. Database tab of the InterChange Server Configuration Wizard
Figure 18. Database tab of the Edit Configuration window of System Manager
Table 8. Flow Monitoring configuration information
Configuration information | Description |
---|---|
Host Name | Host name of the machine where the database server resides |
Database | Name of the database you created on your database server |
Schema Name | Name of the database schema where the flow monitoring event tables
reside. If you configure a custom schema name, you must grant
CREATE, DELETE, and INSERT permission to the
login identified by the schema name. For DB2 databases, the schema name
can be arbitrary. For Oracle databases, the schema name is the same as
the user who creates the table. The default schema name is the same as
the login user name.
|
Max connections | Maximum number of simultaneous connections to the database |
Login | Database login name |
Password | Database password |
Port number | Port number of your database server |
Maximum queue depth is a parameter that controls the maximum number of events allowed in the InterChange Server memory before collaborations wait to enqueue additional events. During flow monitoring, many events are recorded for every flow in a traced collaboration. This results in large amounts of database activity, which can degrade performance. To prevent excessive performance degradation, the collaboration flows write monitor events to an in-memory InterChange Server queue, then these flows are transferred to the database. In order to prevent the InterChange Server system from running out of memory, this queue depth can be limited by configuring the maximum queue depth parameter.
Perform the following steps to configure the maximum queue depth from System Manager.
Figure 19. Mics tab of InterChange Server Edit Configuration window
The changes are saved immediately to the InterchangeSystem.cfg file, but do not take effect until the server is restarted.
When you configure flow monitoring for an InterChange Server system, you can set a desired trace level for traced events.
Perform the following steps to set the trace level for flow monitoring.
Table 9. Flow monitoring trace levels
Trace level | Description |
---|---|
0 | No tracing |
1 | At boot-time, display the configuration to the database |
2 | Not used |
3 | Show event enqueue/dequeue in-memory of the server |
4 | Show event data details such as type or sequenceNumber after in-memory queue operation |
5 | Add database writes |