3 of 3 people found this helpful
Control-M Automation API 126.96.36.199 on top of Control-M/Enterprise Manager FP 5 - 9.0.00.500 all the way up to latest releases now out of the box supported.
Thanks BMC, for this awesome addition to its Customers which for whatever reason are unable to upgrade their current Control-M EM update Level and need leverage the latest enhancements.
Adriano Gomes thanks so much for pointing this out! I would never have noticed otherwise!
I've been exploring AAPI on 9.0.00.500 and had determined that we should upgrade to 19 asap to get the associated benefits.
The way the API pages are laid out I would never have found this page.
OK, confused now, when I try to install the latest AAPI package I get the message 'Default (Cannot install on installation)'. This is on our EM Server.
PIM PLATFORM PACKAGE-DATE INSTALL-DATE VERSION INSTALL-TYPE COMMENTS
DRNFT.9.0.00 Windows Jun-11-2015 Dec-28-2017 9.0.00.000 INSTALLATION EM
PADEV.9.0.00.400 Windows May-04-2017 Dec-28-2017 9.0.00.400 FIXPACK Control-M Automation API FP 4
DRCBM.9.0.00 Windows Jun-08-2015 Dec-28-2017 9.0.00.000 INSTALLATION BMC Batch Impact Manager
DRFOR.9.0.00 Windows Jun-17-2015 Dec-28-2017 9.0.00.000 INSTALLATION Control-M/Forecast
DRDEV.9.0.00 Windows Jun-13-2017 Dec-29-2017 9.0.00.000 INSTALLATION BMC Control-M Automation API
PANFT.9.0.00.500 Windows Jun-13-2017 Dec-29-2017 9.0.00.500 FIXPACK Control-M/Enterprise Manager FP 5
DRCAG.9.0.00 Windows Jun-17-2015 Dec-13-2018 9.0.00.000 INSTALLATION Control-M Self Service
1 of 1 people found this helpful
Hi Paul Robins
I have not tried Windows Version over 9.00.500 yet. On Windows, it woked over 9.18. I have downloaded from this link on AWS. I worked OK for Linux.
Hope you get this done.
Brilliant. Seems to work for me too. It seems to like MVS jobs even less than the last version :-D
BMC have confirmed the install issue will be fixed in 188.8.131.52
We ran for many months 9.19.100 in a 9.18 environment because we needed features and functionality that was present. We had no issues whatsoever.
I like the new monthly release cycles, and I like the fact it is a separate entity altogether from the EM now. Plus the auto-update of the CLI tools is awesome as well.
As Adriano pointed out, the new monthly releases of Automation API (starting with 184.108.40.206) are a great improvement, not only because you can access to the latest functionalities added to the AAPI without the need to wait several months until the next Control-M/EM fixpack, but also because it works with any EM version 9.0.00.500 and above.
That way, you can have different versions on the EM and the AAPI depending on your requirements, and e.g. be on 9.18.x while having the latest AAPI functionality available with version 220.127.116.11. Then, whenever you upgrade your EM, if the installation detects that the AAPI has an older version that the one included in the EM install package, it will overwrite it; and if it finds a more updated one already installed, it will keep it.
Btw, please take in mind that, as stated in the AAPI 18.104.22.168 documentation, "specific features that require a later version of Control-M are indicated in the current documentation, and the minimum version of Control-M that is compatible with each feature is specified". For example, with AAPI 22.214.171.124 you have the capabilitiy to define file transfer connection profiles for Amazon S3 as code (JSON), but this feature was introduced with MFT 9.0.19. Of course, if you have MFT in an older version, the functionality is not going to work even if it is supported via the AAPI.
Finally, the auto-update of the Automation API CLI tools is just great, and saves a lot of time to avoid the CLI kit upgrade everytime you upgrade the AAPI - and very useful too when you are using the CLI kit to connect to different EM environments with different AAPI versions (it will auto-detect the AAPI version and use the required one on the CLI side).