Skip to Content
Information
Newer version of documentation BMC provides a newer version of the documentation for this version of the product. As a result, BMC no longer accepts comments in this space.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see bao8301.

Migrating to version 3.0

If you are using the EXECs QAOALMP1 and QAOALMP2 and you have upgraded your installation of AlarmPoint Standard or Professional Infrastructure Edition, version 3.0.x, you must perform these migration steps to use the new EXECs, QAOALMP4 and QAOALMP5.

The QAOALMP4 EXEC is a simplified version of the QAOALMP1 EXEC and eliminates the type variable.

In addition, although the QAOALMP2 EXEC communicates directly with the AlarmPoint Server, this option is no longer possible with version 3.0.x. The replacement EXEC, QAOALMP5, communicates with the AlarmPoint Java Agent.

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.

  1. 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.
  2. Review your automation EXECs and identify where you have customized the QAOALMP1 EXEC (or copied its logic into one of your own EXECs).
  3. Search for all EXECs that invoke the QAOALMP2 EXEC.
  4. Review the comments in BBSAMP member QAOALMP4 to understand the revised invocation requirements.
  5. Convert all of the existing EXECs to match the QAOALMP4 EXEC.
  6. Be sure to remove the type variable and modify all occurrences of QAOALMP2 to QAOALMP5.
  7. Update the QAOALMP4 EXEC to specify the IP address or host name of the AlarmPoint version 3.0.x Java Agent.

  8. Test the EXECs with AlarmPoint version 3.0.x and verify that the notifications are correctly generated.

    Warning

    Note

    When you are troubleshooting any notification problems, ensure that you view both the Java Agent logs and the AlarmPoint Server logs for informational and error messages.

Related topic

AlarmPoint-solution

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC AMI Ops Automation 8.3