1 of 1 people found this helpful
First thought is that the last Control-M Reports job type BMC published on the AI Hub does require v9.0.19 or later. This is because the job is using the new AAPI service "reporting status::get" that was introduced in v9.0.19.
If you are using REST calls to create your reports, then it will NOT require you to have the CLI and Node.js installed on your box. That is only required if you are wanting to run jobs that use the CLI.
If you are using the Reports 918, I could not get this to work on a Windows Agent that the CLI could not access the local Environments when using a roaming profile. I worked with BMC support and they opened:
CTM-1457 - In Control-M Application Integrator, when using Run as in Windows, AI doesn't load user's roaming profile correct.
To get around that, we just setup an OS job that has the "ctm reporting report" in the command line.
Then since you are in 188.8.131.52 do note that the Synchronous generation of reports (reporting report::get) via REST will be deprecated in v9.0.20. Before you get to far trying to get the REST calls to work on 9.0.18, might want to wait until you have upgraded your AAPI to v9.0.19 (or above) so that you can use the new reporting commands.
Hope that adds some value in helping to get this work.
We had a version that BMC employee wrote for us that we've been using for over a yr now - currently up to 9.019.100. I did see the new version you mention but haven't looked at it in AI yet to see if there's any gain for us. Our current version broke w/ upgrade to 184.108.40.206 App pack & currently working w/ BMC to resolve.