Overview

After you have prepared your environment, export data from the old version of the server.

Stop Old Version of the Server

Stop the old version of the DI Server, as well as the web application server.

Use Migration Tool to Export Data From Old Version of the Server

Use the Migration Tool to export transformation, job, schedule, system configuration, user, role, and shareable object, such as partitions, slave servers, and cluster information from the old server. The Prepare Upgrade Plan step outlines what the Migration Tool exports. Exported data is saved in a migration bundle file. A log file that contains additional details about the extraction process is also stored in the migration bundle file. After you complete the tasks in this section, you will import this migration bundle file. Instructions for that appear in the next section of this documentation.

To use the Migration Tool to import data, complete these steps.

If you have not done so already, identify the paths to the pentaho-solutions directory, where the DI Server is deployed, as well as paths to additional servlets or jar files that you want to export.

Open a Terminal or Command Prompt window, then navigate to the directory where the Migration Tool is installed.

Issue a command in the Terminal or Command Prompt windows that indicates the action you want the Migration Tool to perform, as well as the locations to the pentaho-solutions directory, the DI Server is deployed, and optionally any additional servlets and jar files that you want to migrate. Also indicate where you want the Migration Tool to place the migration bundle file. The Migration Tool command contains these parameters:

--export: Indicates this is an export command. This parameter is required if you want to export a migration bundle file.

--migration-bundle-file: Specifies the directory where you want the migration file to be stored. This parameter is optional. If you do not supply it, the migration bundle file is stored in the same directory where the Migration Tool is installed.

--pentaho-solutions-dir: Indicates the path to the pentaho-solutions directory for the old version of the DI Server. This parameter is required.

--pentaho-war: Indicates the path to place where the old version of the DI Server is deployed. This parameter is required.

--extra-paths: Indicates the files in your classpath that are needed to run the DI Server. Files in the classpath include JDBC drivers, the servlet.api file, and any relevant configuration folders. Whether you include this parameter depends on the platform on which your DI Server is deployed. If your DI Server is deployed on Tomcat, do NOT include the extra-paths parameter because the classpaths are sensed by the Migration Tool when you run it. If your DI Server is deployed on another web application server, use the extra-paths parameter to the files indicated in your classpath.

Windows: Enter a migration command that follows this format in the Command Prompt window that uses the parameters described at the beginning of this step. The command should be formatted like this example.Command Example:

Linux: Enter a command that follows this format in the Terminal window that uses the parameters described at the beginning of this step. The command should be formatted like this example.Command Example:

The Migrator Tool runs. The progress of the tool is displayed in the Command Prompt or Terminal window.

Verify Export Process

To verify that the migration bundle has been created properly and that data was extracted, do these things.

Open a Terminal or Command Prompt window and navigate to the directory where the migration bundle file is stored.

Verify that the bundle exists and that the file size is not zero.

Navigate to the directory where the Migration Tool was installed. The migrator.log file should appear. The migrator.log file contains a log of the export process.

Open the migrator.log file and note any failures or errors. If any failures or errors exist, you might need to migrate that data manually.

Close the file, then rename the migrator.log file to something else. It is very important that you do this. If you do not rename the file, the migrator.log file will be overwritten when you perform the tasks in the Import Data to New Server step. We suggest that you name the file something meaningful to you, like migrator_di_export_09212013.log.

Manually Adjust Memory Settings

If your memory settings for the DI Server is greater than the default, you will need to adjust it. For information on how to adjust memory settings, see the Changing the Java VM Memory Limits section.

Manually Migrate Additional Configuration Settings

Configuration settings are migrated by the Migration Tool as indicated in the What Is Migrated subsection in Prepare DI Migration Plan. If there are additional customizations that you want to migrate, complete these steps.

Back up copies of your old and new configuration files.

Use the File Diff tool of your choice to compare the old and new versions of the configuration file.

If there are specific customizations that you made in the old version of the configuration file that did not migrate, manually make them in the new file. Proceed with caution when doing this.

Manually Migrate Other Customizations

Because of the nature of the software, many customizations can be made. The following presents examples of other customizations you might have made to the old system that would need to be migrated to the new one.

Custom scheduler: If you are using a different implementation of user settings or a scheduler that you have written or have customized, you will need to migrate those manually.

Community plugins: If available, you will need to install new versions of these plugins. If you have written a plugin, thoroughly test the plugin to ensure that it works with the new version of the system.

Other web applications: If you have other web applications that have been installed with Pentaho, you must manually update them.