Import MPI (Management Plug-ins)

The boom agent provides the infrastructure to monitor and manage systems. The agent's main responsibilites are the scheduling, thresholding, correlation, suppression and other necessary processing steps as well as the communication with the boom server. The actual monitoring is configured and performed by so called Management PlugIns (MPI). Such MPIs contain the knowledge what needs to be monitored and how to monitor it. Generally an MPI is a combination of binaries/scripts/executables, policies, remote actions and assignment configurations.


  • Import MPI
  • Export MPI


    • Import MPI (Management Plug-ins)


    Import MPI:

    This is an earlier implementation and has been replaced by the new "Show Import MPI View"

    Open the File Menu and select "Import MPI".
    Select MPI's Directory (location of the MPI files) and click "OK" to import the MPI's. You can import Policies, Packages, Assignment Groups, Actions and Node Groups according to your individual requirements.



    Show Import MPI View:

    Policies/Policy Groups, Assignment Groups, Binaries, Actions and Node Groups can be imported according to your individual requirements.

    1. Open the File Menu and select Show Import MPI View.


      2. There are two Import Types available:

      Import MPI

      The Import MPI type expects the following directory structure for loading (same structure as created by the MPI Export utility). If e.g. only Actions have to be imported only the actions directory has to exist.

      import mpifolder

      Import Other

      Import Other allows to import other directory structures e.g. HP Operation Manager configuration files.

      The import of the following HP Operations Manager configuration data is supported:
      Host Groups
      Policy Groups
      Policies (Trap, Message, PerformanceMonitor, SchedulePolicy, LogfileMonitor)
      Instruction Text Interface
      TroubleTicket Flags as CMA

      Additionally this import type asks you for the Import Properties. Select the type of De-Duplication you want to use for the selected policies.

      import mpiother


    2. Use Load Directory to select the directory which should be imported.

    3. The configuration data will be loaded. The Preview window shows all possible conflicts. All green marked elements have no conflict and can be imported.

    4. Select Start Import

      5. import mpiview



      The configuration data can't be imported if there are any conflicts. In this case the conflicting elements in the Preview window are marked red. The user has to decide how to solve the conflict manually. In some cases there are more possibilities to solve the conflict e.g. policy conflict -> rename policy or import policy with a higher version. If all conflicts are solved the import can be started.


    5. Solving import conflicts:

      6. Solving policy import conflicts:

      import_asn


      Rename: Rename the name of the policy
      Increase Version: Increase the version of the policy
      Use XML path:Policy already exists in another policy group on the server. Policy will be moved into the policy group specified in the MPI import.
      Use Server Path:Policy already exists in another policy group on the server. Policy won't be moved to another directory.
      Reset Tree: Reload the previous tree
      Remove: Remove element from import


      Solving assignment group conflicts:

      import_asn


      Rename: Rename the assignment group
      Add Prefix: Add a prefix to the assignment group
      Add Suffix: Add a suffix to the assignment group
      Merge: Merges the element with the existing element
      Reset Tree: Reload the previous tree
      Remove: Remove element from import
      Resolve Links:All links that point to an element (Policy or Package) that is not yet selected for import, are marked with the following icon: import_link The ‘Resolve Link’ method will add all missing elements to the import.



      The following signs are used to show the kind of conflict and conflict solution:

      Common signs:

      green element has no conflict
      grey element already exists on the server and won't be imported

      Policy conflict signs:

      folder Policy alreday exists in the same directory on the server

      folderred Path conflict. Policy already exists in another policy group on the server

      Conflict solution signs:

      newversion Policy has been imported with a higher version

      moved Policy has been moved to a new policy group

      renamed Element has been renamed

      merge Element has been merged with the existing element. This is possible for assignments and actions.

      Informational signs:

      mon_lnk_broken BOOM_Ping msg_lnk_broken BOOM_Messages

      The \policy\assignmentGroups.xml file of the MPI package contains links pointing to non existing physical xml files (policy xml, package xml). The missing xml files exist already on the server hence the links can be imported.

      mon_lnk_broken BOOM_Ping msg_lnk_broken BOOM_Messages

      The \policy\assignmentGroups.xml file of the MPI package contains links pointing to non existing physical xml files (policy xml, package xml). The missing xml files do not exist on the server hence the links cannot be imported.

      lnk_broken Assignment link has been selected for import but the corresponding policy or package has not been selected.

      arrow_left_blue The import does not contain a element which consists on the server.


    6. Checking of the import log file
      Open the import logfile <boom_gui>/<user>_<server>/BoomPolicyConverter_date.log
      Check for hints or warnings to verify the conversion results






    Export MPI (Management Plug-ins)


    Show Export MPI View:

    Policies/Policy Groups, Assignment Groups, Binaries, Actions and Node Groups can be exported according to your individual requirements.

    1. Open the File Menu and select "Show Export MPI View".

    2. The "Export MPI View" opens. Expand/collapse the appropriate section and mark the Policies, Packages, Assignment Groups, Actions and Node Groups you want to export.

    3. Press the ">>" button to put the selected items into the right window for export.

    4. Press the "Export Button" and select the destination directory for saving. The tree structure and all items are exported to xml formatted files.


    export mpi