Setting up a server to monitor a Sterling B2B Integrator cluster via individual connections

You can monitor a Sterling B2B Integrator clustered instance whether IBM® Sterling Control Center Monitor is individually connected to each node in the Sterling B2B Integrator cluster instance, or connected to the cluster instance through a load balancer. In either case, IBM Sterling Control Center Monitor ensures continuous monitoring of business process activities in case of a node failure and generates events if a cluster node goes down. In addition, you can see the adapter status of all cluster nodes in a single view.

About this task

Note: If nodes are dynamically added or removed from a Sterling B2B Integrator cluster monitored by IBM Sterling Control Center Monitor, IBM Sterling Control Center Monitor will not automatically recognize the change. As a result, any adapters on added nodes will not be monitored until IBM Sterling Control Center Monitor knows about those nodes. For IBM Sterling Control Center Monitor to recognize when a node has been added or removed, you will either have to stop and start IBM Sterling Control Center Monitor or pause and resume monitoring of the node.
To set up IBM Sterling Control Center Monitor to monitor a Sterling B2B Integrator cluster when it is connected to each node individually:

Procedure

  1. On the Sterling B2B Integrator side, create a Web Service called SCCInteropService on one of the nodes in the Sterling B2B Integrator cluster. When you create the web service on one of the cluster nodes, it appears on all other cluster nodes, too. This step ensures that Sterling B2B Integrator and IBM Sterling Control Center Monitor have access to the appropriate process and file transfer data. For detailed instructions, refer to the Sterling B2B Integrator documentation.
  2. On the IBM Sterling Control Center Monitor side, add a server for the Sterling B2B Integrator cluster and for Node Type, select Sterling B2B Integrator Cluster not through a load balancer. Specify the host name and ports for each server, and put them in priority order.