Monitoring a Sterling B2B Integrator server

You can use IBM® Sterling Control Center Monitor to monitor various aspects of a Sterling B2B Integrator server.

Important: Depending on the server IBM Sterling Control Center Monitor is monitoring, you can have functionality limitations in IBM Sterling Control Center Monitor with that server. See the Release notes to see what functionality is available with your server.
You can monitor:
  • Adaptor status
  • Queue depths: Q0 through Q9
  • Business process activity
  • Sterling File Gateway activity
  • File transfers using one or more of the various protocols supported by the Sterling B2B Integrator server
  • Data transfer status
When you are defining Sterling B2B Integrator server properties, consider the following when choosing monitoring options:
  • To monitor business process activities, set Monitor Business Processes to Yes.

    After IBM Sterling Control Center Monitor has connected to the Sterling B2B Integrator server, you can limit the data collected on business processes by IBM Sterling Control Center Monitor. To limit data, click the BP List button on the Settings tab of the Server Properties window.

    On the Business Process Selection dialog, select up to 255 business processes that will not be monitored. In this dialog, you can enter the XPath expression for retrieval of process data for specific business processes.

  • To monitor Sterling File Gateway activity, set Monitor File Gateway to Yes.
  • To monitor file transfers directly that are initiated by business processes and Sterling File Gateway, select one or more of the protocols listed on the Settings tab.

    If no protocols or business processes are selected for monitoring, IBM Sterling Control Center Monitor does not monitor the adaptor status for the Sterling B2B Integrator server, regardless of the value set for Adapter Status Monitor Rest Time.

  • To monitor queue depths, you can specify which queues to monitor at what limit on the Queue Limits tab.
    IBM Sterling Control Center Monitor watches the specified queues and generates events when the specified limit is exceeded and when the queue depth returns to the limit, as shown in the following example:
    CCNS020E Monitored Queue Limit has been exceeded.  Server ID: {0}  Queue: {1}  
Limit: {2}  Depth: {3}
CCNS030I Monitored Queue Limit back in compliance.  Server ID: {0}  Queue: {1}  
Limit: {2}  Depth: {3}