Sterling Connect:Direct for HP NonStop considerations

You need to be aware of considerations for Sterling Connect:Direct for HP NonStop servers when you are integrating them with IBM® Sterling Control Center Monitor.

Observe the following special considerations when managing Sterling Connect:Direct for HP NonStop servers:

• For IBM Sterling Control Center Monitor to manage a Sterling Connect:Direct for HP NonStop server, create three API Managers pointing to the same port in the network map and one adjacent node record that is referenced by all of the API managers on the Sterling Connect:Direct for HP NonStop server. This configuration allows IBM Sterling Control Center Monitor to attempt three simultaneous connections, which may occur if IBM Sterling Control Center Monitor is polling a managed Sterling Connect:Direct for HP NonStop server and performing Guided Node Discovery at the same time. Refer to Defining and Maintaining the Network Map in the IBM Sterling Connect:Direct for HP NonStop Administration Guide.
• A problem in Sterling Connect:Direct for HP NonStop causes events for some Process step end records not to generate. This situation could result in rules not triggering and SLCs generating erroneous events. To address this issue, apply the fix for SR135624.
• Guided Node Discovery requires Sterling Connect:Direct for HP NonStop version 3.4.02 or later.