Migrating synthetic configurations

The BMC Transaction Execution Adapter Agent (TEA Agent) installation files include a command-line utility for migrating your scripts and configurations from your existing BMC Transaction Management Application Response Time (BMC TM ART) installation or from your existing BMC TrueSight App Visibility Manager installation (AM Console) installation to App Visibility. The migration is divided into two stages: export from BMC TM ART or AM Console, and import to App Visibility. 

The following topics are included:

• • To export a self-signed certificate for secure BMC TM ART
  • To export from BMC TM ART
  • To export from the AM Console
  • To import configurations and scripts into App Visibility
  • Related topics

To export a self-signed certificate for secure BMC TM ART

If your installation of BMC TM ART is secured using a self-signed certificate, perform the following procedure before starting your export.

1. Open the BMC TM ART client in a browser.
2. From the web browser, export the certificate for BMC TM ART and save it.
3. Open a command prompt and change the directory to the ...\Disk1\files\jre\bin folder.

4. Run the following command:

   keytool -import -alias "<alias name>" -file "<.cer file path>" -keystore "<cacerts path>"

   • <.cer file path> is the full path of the .cer file that you saved.
   • <cacerts path> is the full path to the cacerts file: ...\Disk1\files\jre\lib\security\cacerts

To export from BMC TM ART

1. Run the migration_tool batch file from the ...\Disk1\utility\ConfigurationMigrationTool folder of your TEA Agent installer files.
2. Enter 1 to select export from BMC TM ART.

3. Enter the required parameters for your BMC TM ART connection, or press Enter to accept the default values.

4. Enter the required parameters for your BMC TM ART database, or press Enter to accept the default values.

   The [confluence_table-plus] macro is a standalone macro and it cannot be used inline. Click on this message for details.
   This macro generates standalone content. As a consequence you need to make sure to use a syntax that separates your macro from the content before and after it so that it's on a line by itself. For example in XWiki Syntax 2.0+ this means having 2 newline characters (a.k.a line breaks) separating your macro from the content before and after it.The export starts running. This may take some time. The amount of time depends on the amount of data that you are exporting.
   The migration files are created in the ConfigurationMigrationTool\Migration_output folder.

   Notes

   • BMC TM ART monitor intervals that are defined as less than two minutes are rounded up to two minutes.
   • Of the Essential scripts supplied with BMC TM ART, only the Pinger group of scripts and the URL Checker script are supported in BMC TrueSight. Customized Essential scripts are migrated as well.
   • All of the Monitor settings that are necessary to set up corresponding Execution Plans in TrueSight are migrated.

   Not migrated

    The following are not migrated:

   • Locations that have no assigned Monitors or Projects
   • Projects that have no assigned Monitors
   • Monitors that are not scheduled to run on any Locations

   Character replacement

   The migration utility makes the following character substitutions automatically:

   • In Project Descriptions, all carriage return (CR) characters are replaced with semicolons (;).
   • In Locations and Script names, all non-alphanumeric characters are replaced with underscores(_) as follows:
     • Groups of consecutive non-alphanumeric characters are replaced with a single underscore.
     • If as a result of this character substitution, scripts would have the same name, the TM ART database IDs of the scripts are appended to the script names.
   • Script file names (.ltz files) that are longer than sixty four characters are truncated.

To export from the AM Console

1. Run the migration_tool batch file from the ...\Disk1\utility\ConfigurationMigrationTool folder of your TEA Agent installer files.
2. Enter 2 to select export from AM Console.

3. Enter the required parameters for your AM Console, or press Enter to accept the default values.

   The [confluence_table-plus] macro is a standalone macro and it cannot be used inline. Click on this message for details.
   This macro generates standalone content. As a consequence you need to make sure to use a syntax that separates your macro from the content before and after it so that it's on a line by itself. For example in XWiki Syntax 2.0+ this means having 2 newline characters (a.k.a line breaks) separating your macro from the content before and after it.The export starts running. This may take some time. The amount of time depends on the amount of data that you are exporting.
   The migration files are created in the ConfigurationMigrationTool\Migration_output folder.

To import configurations and scripts into App Visibility

1. Run the migration_tool batch file from the ...\Disk1\utility\ConfigurationMigrationTool folder of your TEA Agent installation files.
2. Enter 3 to select import.

3. Enter the required parameters for your BMC TrueSight Presentation Server connection, or press Enter to accept the default values.

   The [confluence_table-plus] macro is a standalone macro and it cannot be used inline. Click on this message for details.
   This macro generates standalone content. As a consequence you need to make sure to use a syntax that separates your macro from the content before and after it so that it's on a line by itself. For example in XWiki Syntax 2.0+ this means having 2 newline characters (a.k.a line breaks) separating your macro from the content before and after it.All of the configurations and scripts are imported into App Visibility. The files that were created as part of the export process are deleted automatically.

Related topics

Migrating-a-synthetic-TEA-Agent-silently-from-version-2-6-XX

Migrating-a-synthetic-TEA-Agent-from-version-2-6-XX