Installing and running the event migration utility

Follow the instructions in this topic to download and install the utility.

Minimum requirements

• Java 11. Recommended version openjdk 11.0.7
• BMC Helix Operations Management 
• TrueSight Operations Management

Before you begin

1. On the server where you want to run the migration utility, create the eventmigration directory.
   

   All Cell Knowledge Bases (KBs) that need to be migrated must be present on the server where you run the migration utlity.

2. In the eventmigration directory, perform the following steps:
   1. Download migration utility from the same location from the location shared by BMC Support.

   2. Unzip the event migration utility files, which creates the following folder structure is created:

      

3. Update the conf/migration.properties file with tenant details that you obtained from Preparing-for-event-data-migration.

   Can I configure the maximum event slots to be migrated?

   Yes. However, note that BMC Helix Operations Management supports a maximum 200 event slots per class. 

   For example, the EVENT class has 45 slots in BMC Helix Operations Management. In this case, only 155 slots (200-45) can be configured for this class.

   To configure the maximum number of event slots to be migrated, in the conf/migration.properties file, change the value of the monitor_event.max_slots_no parameter. The default number is 50.

To install and run the event migration utility

1. On the server where you downloaded the migration utility, create the mcell_home\etc directory.
2. Copy the Knowledge Base (KB) files in the mcell_home\etc\<cell_name>\kb directory.
3. In the mcell_home\etc directory, ensure that the Knowledge Base (KB) files are present in the <cell_name>\kb directory.
4. Make sure that you can access the internet from the server where you are running the utility.
5. Open command prompt and navigate to the directory where you downloaded the migration utility jar file.

6. Run the following command:

   java -jar <jar_name>.jar --truesight.mcellhome="<mcell_home dir location>" --truesight.conf="<conf folder location>"   
   

   For example:
   java -jar migratekb-22.4.2.jar --truesight.mcellhome="C:\eventmigration\mcell_home" --truesight.conf="C:\migratekb-utility\target\migratekb-22.4.2-bin\migratekb-22.4.2\conf"

   The command can include the option --server.port=xxxx. The port number defaults to 8080. However, it can be any port if 8080 is already in use.

   The following message appears:
   

   Use: http://localhost:8080 to connect to the GUI.
7. From any browser, go to http://localhost:8080/ to open the migration utility and navigate to the Classes tab.
   
   
   
8. On the BHOM Tenant Details tab, provide the BMC Helix Operations Management tenant details.
   For information about obtaining the tenant details, see Preparing-for-event-data-migration.
   
   
   

9. On the List Event Classes tab, select the classes to migrate.

   Important

   Select the parent of a class that you want to migrate.

   
   
   Event classes can be filtered by status and category. To see the list of available statuses and categories, see Key-considerations-for-migrating-event-data-to-BMC-Helix-Operations-Management.

   Can I migrate the Internal Deprecated class?

   Yes.

   The Internal Deprecated class type is not required in BMC Helix Operations Management. To migrate this class, you must change its class type in the configuration file of the migrate utility. 

   For example, the SIM_RELATIONSHIP_DELETE is an event class of the type Internal Deprecated. To migrate this event class to  BMC Helix Operations Management, change its class type to INTERNAL_THIRD_PARTY by performing the following steps:

   1. Open the <migration_utility_download_directory>conf\classcategory.properties file.
   2. Look for SIM_RELATIONSHIP_DELETE event class.

   3. Change its class type as shown below:
   4. Save the conf\classcategory.properties file.
10. Click Migrate.

Where to go from here

See the migration summary report for the migration status and other details.