Migrating to version 3.0
Note: The earlier versions of the AlarmPoint sample solution that were delivered prior to this release of BMC AMI Ops Automation allowed you to specify that notifications were directed to either an AlarmPoint ID or a user-specified telephone number. Because notifying a telephone number prevents you from taking advantage of the advanced capabilities in AlarmPoint version 3.0.x, the updated solution supports notifying only an AlarmPoint ID.
To migrate to update the AlarmPoint solution, perform the following steps.
- Install AlarmPoint Standard Infrastructure Edition version 3.0.x or AlarmPoint Professional Infrastructure Edition, version 3.0.x.Ensure that the Java Agent is always running by installing it as a Microsoft Windows service because the BMC AMI OpsA EXECs communicate with this agent.
- Review your automation EXECs and identify where you have customized the QAOALMP1 EXEC (or copied its logic into one of your own EXECs).
- Search for all EXECs that invoke the QAOALMP2 EXEC.
- Review the comments in BBSAMP member QAOALMP4 to understand the revised invocation requirements.
- Convert all of the existing EXECs to match the QAOALMP4 EXEC.
- Be sure to remove the type variable and modify all occurrences of QAOALMP2 to QAOALMP5.
- Update the QAOALMP4 EXEC to specify the IP address or host name of the AlarmPoint version 3.0.x Java Agent.
Test the EXECs with AlarmPoint version 3.0.x and verify that the notifications are correctly generated.
Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*