Skip to main content
Hitachi Vantara Lumada and Pentaho Documentation

Prepare Environment for DI Migration


Explains how to prepare your enviroment for the migration process.

After you have prepared your migrate plan, prepare your environment. To prepare your environment, do these things.

Install 5.x.x DI Server and Licenses

Complete these steps to install the 5.x.x DI Server and licenses.

Note: If you are going to install the 5.x.x DI Server on the same machine as the 4.4.x one, consider keeping the 4.4.x version of DI Server running as you install the 5.x.x DI server to avoid port conflicts. When you use the Wizard to install the 5.x.x DI Server, it senses what ports are being used used at the time of installation and, if the port is used, it assigns a different port for the newly installed DI Server. If the 5.x.x and 4.4.x DI Servers run on different ports, they can both run at the same time. This is helpful during the Verify Migration step, which occurs later in these instructions, because you will need to run both systems at the same time to verify that content has migrated from the 4.4.x system to the 5.x.x one.
  1. Install the 5.x.x version of the DI Server. See Select DI Installation Options to determine the best installation option.
  2. Ensure that license keys have been installed and modify the startup scripts as needed. To avoid problems with the Migration Tool and to avoid any of your changes being overwritten, the 5.x.x server should be in a "pristine" state; do not configure the system further, just modify the startup scripts and install the license keys.
  3. Make sure that you have an environment variable set for $PENTAHO_INSTALLED_LICENSE_PATH. The variable should be set to the path where your licenses are installed. 
  4. Start the DI Server and Spoon to make sure that the software has installed properly. Do not make any additional changes. If you have problems with starting the DI Server, be sure to fix them before proceeding further.

Download and Install the Migration Tool

The Migration Tool automates the data migration process. The Export Data and Import Data sections provide details on how to use the Migration Tool to perform the migration process.

Note: The installation program for the Migration Tool requires the currently supported version of Oracle Java. We recommend that you download and install the Migration Tool on the same computer where the 5.x.x version of the server is installed because Java will have already been installed on that computer during the installation process.
  1. Download the file from the Customer Support Portal on the computer where the 5.x.x version of the server has been installed.
  2. If you use Windows, open the Command Prompt window. If you use Linux, open the Terminal window.
  3. Install the Migration Tool by doing one of the following.
    1. If you use Windows, enter this command.
    2. If you use Linux, enter this command.
  4. Read the EULA that appears. Select I accept the terms of this license agreement, then click Next.
  5. Indicate where you want the file to be unpacked. It doesn't matter where you download the file. Click the Next button.
  6. The Installation Progress window appears. Progress bars indicate the status of the process. When the process is complete, click Quit to exit.
  7. If the 4.4.x version of the server is installed on another computer, you need to place a copy of the Migration Tool on it also. Because the technology used to package and unzip Migration Tool requires a newer version of Java than the one required by the 4.4.x version of the server, just copy the already unzipped file to that computer. The Migrator Tool however, works with the previous version of Java.

Increase Memory Allocated to the 4.4.x Server

The Migration Tool requires 2 gigabytes of RAM to run. Since the Migration Tool launches a mini-version of the server, the Migration Tool uses the same memory that you have allocated for the server. Since the 4.4.x version of the DI Server had less memory allocated by default, you will need to check the memory settings for the server, then make adjustments if necessary.
  1. Review the instructions in the Changing the Java VM Memory Limits for your operating system and installation type. Then do these things.
    1. Complete the steps for stopping the server.
    2. Ensure that the memory settings for the minimum and maximum Java heap size parameters (-Xms and -Xmx) are both set to at least 2048m or higher. If the parameters are greater than 2048, leave as is, only make changes if the setting is less than 2048. Windows Example:
       export CATALINA_OPTS="-Xms2048m -Xmx2048m -XX:MaxPermSize=256m -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000" 
      Linux Example:
       export JAVA OPTS="-Dpentaho.installed.licenses.file=/opt/pentaho/.installedLicenses.xml -Xms2048m Xmx2048m -XX-MaxPermSize=256m -Dsun.rmi.dyc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000" 
  2. Restart the 4.4.x version of the server and verify that it starts correctly.