Monitoring Connect:Direct servers

For best performance, NodeService threads for Connect:Direct servers establish connections to their respective monitored servers once, and do not disconnect those connections after each poll unless an error occurs. When monitoring more than a few thousand Connect:Direct servers though it would be possible for IBM® Sterling Control Center Monitor to attempt to exceed the number of socket connections allowed by the server’s operating system the EP runs on.

In IBM Sterling Control Center Monitor v6.1.2.1 the engine property NON_PERSISTENT_CD_CONNECTION was introduced to avoid exceeding allowed socket connections. By setting this property to true (default=false), Connect:Direct NodeServices will disconnect after each poll cycle and re-establish the connection to their Connect:Direct server at the beginning of each poll cycle.

Unless exceeding the number of socket connections is a problem for one, or more, of your EPs, you should not change the default setting for NON_PERSISTENT_CD_CONNECTION from false to true.