Smarts Server Manager (ESM): How to migrate application process templates and host configuration from Smarts Server Manager/ESM 9.x to version 9.3 and later
search cancel

Smarts Server Manager (ESM): How to migrate application process templates and host configuration from Smarts Server Manager/ESM 9.x to version 9.3 and later

book

Article ID: 331737

calendar_today

Updated On:

Products

VMware Smart Assurance

Environment

VMware Smart Assurance - SMARTS

Resolution

This article explains how to automatically migrate application process templates and host configuration from Smarts Server Manager/ESM 9.x to Smarts Server Manager 9.3 and later environments using an adapter ASL script. This is a new functionality introduced in Smarts Server Manager 9.3.



Smarts Server Manager 9.3 (formerly known as ESM) offers a migration adapter script that supports the migration from Smarts Server Manager/ESM 9.x to ESM 9.3 of application process templates and processes that were manually configured on hosts. This functionality enables you to:

  • Retrieve the application process templates from the Smarts Server Manager/ESM 9.x environment, convert the templates to XML, and import the information as user-defined templates into a single XML file.
  • Retrieve processes or host applications that were manually configured on hosts from Smarts Server Manager/ESM 9.x, and transfer the applications to a discovered host (the applications are not saved to an XML file).
The migration adapter script used to perform the migration is called dump-process-monitoring-configuration-file.asl. The procedure to use this ASL script to migrate from Smarts Server Manager/ESM 9.x to 9.3 or later is as follows:
  1. Start the old Smarts Server Manager/ESM 9.x Domain Manager.
  2. In your new Smarts Server Manager 9.3 installation, execute the following sm_adapter command from the <BASEDIR>/smarts/bin directory (as one line):

sm_adapter -b <broker:port> -s <old_esm_domain_manager> -Dfilename=<BASEDIR>/smarts/local/conf/esm/ProcessMonitoringConfig.txt <BASEDIR>/smarts/rules/sp/dump-process-monitoring-configuration-file.asl

Where the following is true in the above command:

<broker:port>: The location of the broker (and port number used) where the old Smarts Server Manager/ESM Domain Manager is registered.

<old_esm_domain_manager>: The name of the old Smarts Server Manager/ESM Domain Manager.

<BASEDIR>:  The directory where the new Smarts Server Manager 9.3 is installed.

  1. After the transfer has executed successfully, start the new (9.3) Server Manager by specifying the --clean-topology and --ignore-restore-errors options. To do this, run the following sm_server command from the <BASEDIR>/smarts/bin directory:

sm_server -n <9.3_server_manager_name> -c esm --output --daemon --clean-topology --ignore-restore-errors

  1. With the completion of the preceding steps, the contents of the adapter ProcessMonitoringConfig.txt file is automatically loaded and processed. Also, the --clean-topology option of the sm_server command imports the customized Polling and Threshold settings from the old repository file into the new topology.