Sterling Connect:Express considerations

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

Observe the following considerations when you monitor Sterling Connect:Express servers:

• Sterling Connect:Express logs errors differently than other server types supported by IBM Sterling Control Center Monitor. If you want to use the predefined Bad Return Code rule or create a rule to watch for failed Sterling Connect:Express transfers, you need to watch for non-zero return codes in the Server Status and Server Error event types in addition to the Process Step Ended event type.
• For Sterling Connect:Express for UNIX and Sterling Connect:Express for Microsoft Windows, you must specify a monitor rest time that is less than the API timeout for Sterling Connect:Express.
• For Sterling Connect:Express for z/OS users, processes that are held or deferred are not shown in the IBM Sterling Control Center Monitor Queued Activity Monitor.