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

To install and run the event migration utility

Ensure that you perform all the actions given the Preparing-for-event-data-migration topic.
On the server where you downloaded the migration utility, create the mcell_home\etc directory.
Copy the Knowledge Base (KB) files in the mcell_home\etc\<cell_name>\kb directory.
In the mcell_home\etc directory, ensure that the Knowledge Base (KB) files are present in the <cell_name>\kb directory.
Make sure that you can access the internet from the server where you are running the utility.
Open command prompt and navigate to the directory where you downloaded the migration utility jar file.
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.
Specify the precedence settings for the policies that you want to migrate.
1. Go to the <migration_utility_home_folder>/conf/migration.properties file.
2. Change the values in the executionOrder column if the precedence is incorrect; otherwise, leave them as is.
  The policy precedence can be between 0 and 9999.
  Important
  - Confirm that the <migration_utility_home_folder>/ExecutionOrderDetails_<cell_name>.csv file is created. If you do see the file, go to the <migration_utility_home_folder>/event_migration.log file to evaluate the cause.
  - If the execution order of the rule is not specified in the <migration_utility_home_folder>/ExecutionOrderDetails_<cell_name>.csv file, or if the file is not generated, the policy precedence number in the kb/policies.baroc file is used to grant policy precedence.
  The following image displays an example <migration_utility_home_folder>/ExecutionOrderDetails_<cell_name>.csv file:
Open the migration utility by navigating to http://localhost:8080/ from any browser.
On the migration utility Home page in your browser, navigate to the Classes tab.
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.
Click Next.
On the List Event classes tab, select the classes to migrate.
If you select a subclass, the event migration utility automatically searches for the parent class. If the parent class was not migrated earlier, it is also migrated with the subclass,

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.
Click Next.
On the Selection Summary tab, review the options that you have selected.
Click Migrate.