The Control-M plugin connects to BMC Control-M Automation API (REST API). This article provides general troubleshooting steps for users to review the configuration. | |
The Netprobe should be located closely together with the Control-M Automation API server if possible, preferably on the same server or network segment. This can reduce unnecessary latencies between the server communications. Users can check out the documentations from BMC Software, which includes a Command Line Interface (CLI) to try connecting a Control-M instance. |
|
Users should review the Control-M sampler configuration. Each additional dataview means a REST API call, which can accumulate to the overall sampling time. It is suggested to avoid combining many dataviews in a single sampler. If each REST API call takes a few seconds, the Control-M sampler should have less than 10 dataviews. Otherwise, it can exceed the heartbeat interval between the Gateway and Netprobe. It will be useful to enable the "SAMPLING" debug as mentioned in this article. This provides more accurate figures to confirm if certain Control-M sampler takes long time to complete. |
|
Further ReadingUsers can refer to the Control-M Plug-in documentation. |
Comments
0 comments
Please sign in to leave a comment.