Preparing for migration

Task 1: To activate BMC Helix Continuous Optimization

1. Register for BMC Helix Continuous Optimization  and activate the product.
   For more information, see Setting-up-and-going-live.
2. Review the welcome email that includes the login credentials and URLs to use the product.

Task 2: To install and configure the Remote ETL Engine

Install the Remote ETL Engine on the TrueSight Capacity Optimization environment so that it can communicate with the Database server during the migration of the historical data. Install one Remote ETL Engine for each TrueSight Capacity Optimization local or remote ETL Engine. For example, if there are eight local and two remote ETL Engines in TrueSight Capacity Optimization, you need to install ten Remote ETL Engines for BMC Helix Continuous Optimization.

1. In your on-premises environment, prepare a Linux virtual machine for Remote ETL engine installation.
   For more information, see System-requirements-for-the-Remote-ETL-Engine. 
2. Install the Remote ETL Engine.
   For more information, see Installing-the-Remote-ETL-Engine.
3. (Optional ) When migrating from TrueSight Capacity Optimization with Oracle as a database, configure the Oracle client details.
   1. In the Remote ETL Engine installation directory, rename the customenvpre.sh.sample file to customenvpre.sh.
   2. Open the renamed customenvpre.sh file for editing.
   3. In the #ORACLE CLIENT section, search for the following text:
      #ORACLE_HOME="<ORACLE_HOME>"
      #export ORACLE_HOME
      If the statements are preceded by '#' characters, remove them from both to uncomment them and modify the required <ORACLE_HOME> variable. It is the full path of the directory where the Oracle client software is installed; for example, ORACLE_HOME="/opt/oracle/product/12.2.0/client_1"
   4. Restart the scheduler. For more information, see Checking-the-status-of-remote-components.
4. Install Java Development Kit 17.

Task 3: To download the migration toolkit

1. Log in to BMC Helix Continuous Optimization as an administrator and download the migration toolkit.
   The migration-toolkit.tar.gz file is downloaded to your system.

2. Log in to the host computer on which the TrueSight Capacity Optimization Application Server is installed, and create a temporary directory (for example, migrate). Log in as the user that you specified during the Application Server installation (for example: cpit).

   Disk space requirements

   Make sure that the temporary directory on a host computer has a minimum of 20 GB of free space for the migrated data dump. However, the actual space required for the migrated data dump depends on the size of the source environment. To estimate the storage space requirements, see (Optional) Task 4: To estimate the storage space required for migration.

3. Copy the downloaded file to the temporary directory. 
4. Generate the access keys and tenant ID that are required while you run the migration tool on the Application Server. These keys and ID are used to authenticate the Administrator user to connect to BMC Helix Continuous Optimization.
   1. Log in to BMC Helix Portal on which BMC Helix Continuous Optimization is hosted.

   2. Create an access key in BMC Helix Portal. Copy the generated tenant ID, access key, and secret key, and note them down. For details, see Setting up access keys for programmatic access. 

   3. Copy the base URL of BMC Helix Portal and note it down. 

(Optional) Task 4: To estimate the storage space required for migration 

1. On the TrueSight Capacity Optimization Application Server host computer, copy the migration_disk_space_estimation.sh script file to the TrueSight Capacity Optimization installation folder.
2. At the shell prompt, change to the directory where the migration_disk_space_estimation.sh script file is copied.

3. Run the following command to get an estimation of the required disk space:

   bash migration_disk_space_estimation.sh

   An estimation of the total disk space required for migration is displayed. 

(Optional) Task 5: To review the GCP API Extractor configuration

In TrueSight Capacity Optimization, review the Service account key file directory  configuration in GCP API Extractor.  

Make sure that the service account key file is configured to be read from the upload compressed folder option as the folder path option is not supported by the migration toolkit. For details, see Google-Cloud-Platform-GCP-API-Extractor.

Where to go from here

After completing the premigration tasks, you can begin migrating your data.