Add Ability to Invoke Automation Script During Admin Mode Processing

Maximo has always had limited Admin Mode support when dealing with clusters. IBM Support even recommends to shut down all JVMs but one. In 7.6.1.1 this was enhanced a step further where Maximo can even stop and start the other JVMs inside of WebSphere automatically during the admin mode processing.

It's currently impossible to invoke a script during admin mode to do any processing that a customer might require for an admin mode related change. This is particularly important in SaaS scenarios where customers are empowered to perform their own DB Configs whom might not inform their provider that they're going to be performing these maintenance events, but applies to on-premises customers as well.

This request allows a customer to have an automation script invoked during the admin mode process to do any additional processing required, such as to ensure downtime is properly reflected in the external monitoring systems or to provide notifications in alternate systems (such as sending to a Slack channel for example).

It would be ideal, but not required for this enhancement, to be able to prevent the application from entering admin mode from this script by throwing an error. For example, if this script is supposed to validate that a change record exists for this system during this maintenance window, it would be beneficial to prevent admin mode if a change does not actually exist. Similarly if this is required to push downtime to a monitoring system, it would be beneficial that if it failed the script could throw an error and the processing failed.