The BI Migration Tool (bi-migration-tool.jar) is self-executing and self-contained. You must generate the BI Migration Tool jar file by using the BI Migration Script (migration-tool.sh|cmd). The BI Migration Script is made available after you configure the Oracle Analytics Server domain. This step packages the components of the BI Migration Tool into a single, self-executing jar file, so that it can be easily transported on to an 11g system. To do this, you must have access to a Oracle Analytics Server with a configured domain. You must set up the Oracle Analytics Server domain to provide sufficient infrastructure to run the BI Migration Tool and allow it to repackage itself. The Oracle Analytics Server domain can be empty at this stage.

1. The BI Migration Script (migration-tool.sh|cmd) is available at the following location:
   (UNIX) DOMAIN_HOME/bitools/bin/
2. Run the following command to generate the BI Migration Tool:
   (UNIX) DOMAIN_HOME/bitools/bin/migration-tool.sh package bi-migration-tool.jar
   Where,

   Table 3-6 Command Description

   Option	Description
   DOMAIN_HOME/bitools/bin	Specifies the location of the BI Migration Script.
   package	Specifies the BI Migration Script to perform the packaging operation.
   bi-migration-tool.jar	Specifies the file name of the migration tool jar file where the output is written. In this documentation, the bi-migration-tool.jar file is referred as the "BI Migration Tool" and the migration-tool.sh script is referred as the "BI Migration Script".

3. Copy the BI Migration Tool to the host system from where you want to export data.

The export bundle is a ".jar " file and consists of the metadata information from the 11g Oracle home.

1. Change to the directory where you created the bi-migration-tool.jar file.
2. Run the BI Migration Tool without passing parameters. Enter the following command:
   (UNIX) JDK_HOME/bin/java -jar bi-migration-tool.jar

   Note:

   The JDK version must be JDK 1.8.0_131 or higher. You must verify that a certified JDK already exists on your system by running java -version from the command line.

   This command displays the list of parameters that you can include for the BI Migration Tool to locate various parts of the 11g system.
3. Run the BI Migration Tool with the following parameters this time to create an export bundle.

   Table 3-7 Parameter Description: Creating Export Bundle

   Parameter	Description
   out	Indicates the BI Migration Tool to run in Export mode.
   <oracle 11g home>	Specifies the Oracle home directory. This is typically the directory Oracle_BI inside Middleware home.
   DOMAIN_HOME	Specify the Domain home directory. This is typically the directory user_projects/domains/bi/ inside the Middleware home.
   <output export bundle path>	Specifies the file name of the export bundle where the output is written. The output is not a BAR file. The file name of the export bundle must include the "jar" extension.

   Following is a sample command for creating an export bundle:
   (UNIX) JDK_HOME/bin/java -jar bi-migration-tool.jar out ORACLE_HOME/Oracle_BI1 DOMAIN_HOME/tmp/migration-tool-test/test_export.jar
   Where,

   Table 3-8 Parameter Values: Creating Export Bundle

   Parameter	Description
   ORACLE_HOME/Oracle_BI1	The path where the Oracle home directory is located.
   DOMAIN_HOME	The path where the Domain home directory is located.
   /tmp/migration-tool-test/test_export.jar	The location where the export bundle is created.

   Note:

   Make sure to replace these file paths with the respective paths on your system.
   The following message indicates a successful export:

   Export succeeded

You must import the export bundle using the BI Migration Script (migration-tool.sh|cmd). The BI Migration Script automatically determines the Oracle home and the Domain home directories.

1. Run the BI Migration Script with the following parameters:
   (UNIX) DOMAIN_HOME/bitools/bin/migration-tool.sh in config <export bundle> <service instance name>
   For example,
   DOMAIN_HOME/bitools/bin/migration-tool.sh in config /tmp/migration-tool-test/test_export.jar ssi
   Where,

   Table 3-10 Parameter Values: Importing the export bundle

   Parameter	Description
   in	Indicates the BI Migration Script to import the bundle.
   config	Indicates the BI Migration Script to overwrite the configuration files during the import process.
   /tmp/migration-tool-test/test_export.jar	The path where the export bundle is located.
   ssi	Specifies the name of the service instance.

2. If the migration is successful, you see the output such as the following:

   Import succeeded
   About to close down logging to: DOMAIN_HOME/bilogs/migration/migration-2016-05-05-06-13-05.log
   This is so that the log file can be archived into the diagnostics zip
   Any remaining log entries will go to '/tmp/migration.log', and will not appear in the diagnostics zip
   Migration action succeeded