Integrating in TrueSight KMs that are not CMA-Compatible

  • kb1249
  • Oct. 25, 2022
  • 2 min read

How to install and configure the CMA for Legacy KM to integrate in TrueSight KMs that do not support TrueSight CMA.

Best Practice CMA for Legacy KM CMA

Related Topics

Downloads

EMCECSv3-for-MonitoringStudio94-v1.zip

Introduction

The CMA for Legacy KM is a very simple module that can be loaded in a TrueSight CMA policy to preload and configure KMs that have not been designed to support TrueSight CMA (typically custom KMs or older KMs).

A policy for the CMA for Legacy KM allows you to specify configuration variables that are required for the legacy KM to work properly, very much like the Agent Configuration tab. But the CMA for Legacy KM is also capable of setting encrypted credentials that are stored in the PATROL Agent secure store, and execute PSL commands once the configuration variables are set (typically to trigger a discovery).

The KMs below are not compatible with TrueSight CMA:

  • CA ARCserve Backup KM for PATROL (all versions)
  • HP Data Protector KM for PATROL (v1.5.02 and earlier)
  • Symantec Backup Exec KM for PATROL (all versions)
  • Tivoli Workload Scheduler KM for PATROL (all versions)

Procedure

The CMA for Legacy KM is provided for free and “as is”. Sentry Software expresses no warranties of any kind related to this product. In no event shall Sentry Software, nor any of its employees, be held liable for anything arising from the usage of this product.

To integrate in TrueSight KMs that are not CMA-compatible:

  1. Download the CMA for Legacy KM package: cma-for-legacy-km-<version>-thorium.zip.
  2. Log on to TrueSight Operations Management.
  3. Import the CMA for Legacy KM into the Repository.
  4. Add an Infrastructure Policy.
  5. Create a Monitoring Configuration for the CMA for Legacy KM.
  6. Add and configure a PATROL Classic Configuration Path:
    • in the Add to Preloaded KMs field, enter the list of KM or KML files to be preloaded. The list must be comma-delimited. This information will be added to /AgentSetup/preloadedKMs (e.g.: HPO_Load.kml)
    • in the Configuration Path field, enter the PATROL classic configuration path where the variables are to be defined (e.g.: /HPO)
    • enter a unique Internal ID for this configuration (e.g.: HPO)
    • optionally, enter a PSL command to be run when all configuration variables have been set (typically to trigger a discovery, e.g.: set("/HPO_SERVER_ForceDiscovery", true);)
    • create the required PATROL Classic Configuration Variables by providing the Variable name and its Value (e.g.: defaultLogin and root). If the value should be:
      • hidden in the CMA interface, fill in the Value (Hidden) field instead of the Value field (e.g.: the value for defaultPassword)
      • encrypted, select the Encryption Method supported by the KM using the variable (e.g.: the value for defaultPassword for HP Data Protector KM should be in PATROL Agent Default Encryption)
      • if required, enter the PSL command to be executed when the variable is copied. Use %{PATH}, %{NAME} or %{VALUE} to pass the configuration variable path, name or value.
  7. Save and enable the policy to deploy it to the monitored server.
  8. Install the CMA for Legacy KM and the relevant KM that uses these PATROL Classic Configuration Variables on the PATROL Agent where this policy is deployed. Follow the standard KM installation procedure using BMC Installer.
  9. For the preloading process to take effect, restart the PATROL Agent after the initial discovery (after 2 minutes).
Best Practice CMA for Legacy KM CMA