Explains how to import data to version 5.x.x of the DI Server.
After you have exported your data from the 4.4.x server and into the migration bundle file, import the data in the migration bundle file into the 5.x.x server.
Stop 5.x.x Version of DI Server
Stop the 5.x.x version of the DI Server, as well as the web application server.
Ensure 5.x.x DI Repository Database Is Running
Ensure the database that houses the 5.x.x version of the DI Repository is running. If it is not, start it.
Use Migration Tool to Import Data to 5.x.x Server
Use the Migration Tool to import the migration bundle file to the 5.x.x server. The migration bundle file was generated in the previous step. 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, the path 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 pentaho-di directory that is on the web application server, 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. Complete these steps based on your operating system. The Migration Tool command contains these parameters:
- --import: Indicates this is an import command. This parameter is required if you want to import 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 5.x.x version of the DI Server. This parameter is required.
- --pentaho-war: Indicates the path where 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 command that follows this format in the Command Prompt window. The command should be formatted like this. Command Example:
migrator.bat --import --migration-bundle-file=C:\Users\pentaho\migration.zip --pentaho-solutions-dir=C:\Users\pentaho\server\data-integration-server\pentaho-solutions --pentaho-war=C:\Users\pentaho\server\data-integration-server\tomcat\webapps\di-pentaho
- Linux: Enter a command that follows this format in the Terminal window. The command should be formatted like this. Command Example:
./migrator.sh --import --migration-bundle-file=/Users/mycompany/migration.zip --pentaho-solutions-dir=/Users/mycompany/pentaho/server/data-integration-server/pentaho-solutions --pentaho-war=/Users/mycompany/pentaho/server/data-integration-server/tomcat/webapps/di-pentaho
- The Migrator Tool runs. The progress of the tool is displayed in the Command Prompt or Terminal window.
Review Import Logs
To verify that the import occured properly and that data was imported, do these things.
- Open a Terminal or Command Prompt window and 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 import 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 if you perform decide to migrate the BA Server. We suggest that you name the file something meaningful to you, like migrator_ba_import_09212013.log.
Manually Migrate Additional Data
Manually Migrate JDBC Drivers
|Component||Driver Location in Version 4.4.x||Driver Location in Version 5.x.x|
Manually Adjust Memory Settings
Manually Migrate Additional Configuration Settings
- Back up copies of your 4.4.x and 5.x.x configuration files.
- Use the File Diff tool of your choice to compare the 4.4.x and 5.x.x versions of the configuration file.
- If there are specific customizations that you made in the 4.4.x version of the configuration file that did not migrate, manually make them in the 5.x.x file. Proceed with caution when doing this.
Manually Migrate Other Customizations
- 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 5.x.x versions of these plugins. If you have written a plugin, thoroughly test the plugin to ensure that it works with the 5.x.x version of the system.
- Other web applications: If you have other web applications that have been installed with Pentaho, you must manually update them.