About the Migration Process

During migration, you migrate your metadata and configuration of the Oracle Business Intelligence components that you have installed on your system. Migration is a two-step process. In the first step, you create an export bundle from a previous release of Oracle Analytics Server or Oracle Business Intelligence release (11.1.1.9.0 or later). In the second step, you import the export bundle in to the latest Oracle Analytics Server system.

Oracle has introduced many enhancements to existing features in Oracle Analytics Server. Sometimes, these enhancements replace the existing functionality or reimplement it in a different way. Wherever possible, the existing prior release functionality and configuration is migrated to the corresponding Oracle Analytics Server system. Although the appearance and behavior of the Oracle Analytics Server system can be different, the end result is expected to be functionally equivalent.

An efficient migration strategy allows you to migrate your metadata and configuration from your Oracle Business Intelligence environment. The goal of this process is to not exactly replicate the appearance and behavior of the original Oracle Business Intelligence system in the latest Oracle Analytics Server environment. Replicating the Oracle Business Intelligence appearance and behavior is time-consuming and sometimes difficult, if not impossible. For example, the dashboards and prompts are represented differently in Oracle Analytics Server and would require significant manual intervention to recreate the Oracle Business Intelligence appearance. It also undermines the rationale behind moving on to Oracle Analytics Server; namely, to take advantage of the enhancements that are introduced in Oracle Analytics Server.

Note:

The export process is read-only. Data, configuration, or existing binaries are not modified or deleted on the source system. During export, the metadata and configuration (specifically the data model and connection pools), the catalog content, and the security store authorization policy are retained. You must reconfigure the following:

The WebLogic authentication configuration
WebLogic doesn't support migration from Oracle Business Intelligence to Oracle Analytics Server. Therefore, you must reconfigure the security realm in Oracle Analytics Server as it's not a part of the Oracle Business Intelligence to Oracle Analytics Server migration. If your users and groups are in an external LDAP, you must configure your Oracle Analytics Server to point to the external LDAP. If your Oracle Business Intelligence users were hosted in the WebLogic LDAP, you can use the WebLogic Server to export users from Oracle Business Intelligence in to Oracle Analytics Server WebLogic LDAP. However, Oracle Analytics Server doesn't support a BI System User. Therefore, you must delete the BI System User after you import it in to the Oracle Analytics Server system.
Mid-tier database content (such as Publisher schedules, the job history of agents, scorecard annotations, and usage tracking tables)
The Agents are migrated from Oracle Business Intelligence to Oracle Analytics Server in a disabled state. You must reenable them after the migration. Reenabling the agents recreates the entries in the scheduler database. However, the Agent history is not migrated from Oracle Business Intelligence to Oracle Analytics Server. You must also reconfigure Usage Tracking.
Application-specific data such as TimesTen aggregates, the global cache, required database schemas, data, outlines, rules, and calculations

The import process is offline. During import, metadata content is deployed to customize the specified service instance and it overwrites the existing configuration settings.

The following components are migrated:

Oracle BI Server: This includes the NQSConfig.INI and the opmn.xml files.
Oracle BI Presentation Services: This includes the instanceconfig.xml file.
Oracle Analytics Publisher: This includes the scanner.xml, xdo.cfg, xmlp-server-config.xml, datasources.xml, xdodelivery.cfg, cupsprinters.cfg files, the Map directory, and the Plugins directory.

The following metadata is migrated:

Content (Oracle BI Presentation Services Catalog), semantic model (the .RPD file), and the authorization policy securing it (Java Authorization (JAZN)).

The following OPMN properties contained in the opmn.xml file are not migrated to Oracle Analytics Server during configuration migration:

obips
obiccs
obijh
obisch

However, the OBIS property is migrated.

Note:

The existing system is left unchanged during and after the migration process is complete.

Table 3-1 provides a high-level summary of the steps that you must perform to migrate from Oracle Business Intelligence or previous release of Oracle Analytics Server to the latest release of Oracle Analytics Server.

Table 3-1 Tasks for Migrating to Oracle Analytics Server

Task Description

Task	Description
Required If you have not done so already, review the introductory topics in this guide and complete the required pre-upgrade tasks.	The pre-upgrade tasks include cloning your production environment, verifying system requirements and certifications, purging unused data, and creating a non-SYSDBA user. For a complete list of pre-upgrade tasks, see Pre-Upgrade Requirements.
Required Review the prerequisites for Oracle Business Intelligence to Oracle Analytics Server migration.	Make sure that you meet the necessary requirements before you migrate your metadata and configuration to Oracle Analytics Server. Additionally, analyze and optimize your Oracle Business Intelligence system by removing redundant content and merging and consolidating similar content. For more information, see Migration Prerequisites.
Required Download and install the Fusion Middleware Infrastructure and Oracle Analytics Server distributions.	The Infrastructure distribution combines the WebLogic Server and the Java Required Files (JRF) that are required to set up the foundation to install other Fusion Middleware products. As per the upgrade topology defined in this guide, you must install the Infrastructure in a new Oracle home. To install the product distributions, follow the procedure that is described in Installing the Product Distributions.
Required Create the required Oracle Analytics Server schemas.	The schemas that you create will vary depending on your existing schema configuration. To create schemas with the Repository Creation Utility (RCU), see Creating the Required Oracle Analytics Server Schemas.
Required Configure the Oracle Analytics Server domain.	To configure the Oracle Analytics Server domain with the Configuration Assistant, see Configuring Oracle Analytics Server Domain with the Configuration Assistant.
Required Stop the servers and processes.	You must stop the Oracle Analytics Server instance, OBIS1, OBIPS1, Administration Server, Managed Servers, and the Node Manager before you start the migration. For the complete procedure, see Stopping Servers and Processes.
Required Use the appropriate migration tool depending on the release of Oracle Business Intelligence or Oracle Analytics Server .	To migrate from Oracle Business Intelligence 11g, you must generate the BI Migration Tool jar file by using the BI Migration Script (migration-tool.sh\|cmd). For the complete procedure, see Generating the BI Migration Tool (bi-migration-tool.jar). To migrate from Oracle Business Intelligence 12c, navigate to (Linux)`12c_DOMAIN_HOME\bitools\bin\` folder or (Windows)`12c_DOMAIN_HOME/bitools/bin/` folder to use the export command specific to the Oracle Business Intelligence release.
Required Create an export bundle.	The export bundle consists of the metadata information from the Oracle Business Intelligence home. To create the export bundle (.jar file) from a 11g system, see Creating the Export Bundle. To create the export bundle (.bar file) from a 12c system, see Export Metadata Using Command Line.
Required Import the export bundle in Oracle Analytics Server.	You must import the export bundle in Oracle Analytics Server. To import the export bundle from a 11g system, use the BI Migration Script (migration-tool.sh\|cmd). The BI Migration Script automatically determines the Oracle home and the Domain home directories. To import the bundle, see Importing with the BI Migration Script (migration-tool.sh\|cmd). To import the export bundle from a 12c system, use the Oracle Analytics Server Console to upload and restore the export bundle. See Import Metadata in Oracle Analytics Server
Required Start the servers and processes.	To start the Oracle Analytics Server, OBIS1, OBIPS1, Administration Server, Managed Servers, and the Node Manager, see Starting Servers and Processes.
Required Complete the post-migration steps.	For Oracle Analytics Server post-migration steps, see Post-Migration Tasks. For Oracle Analytics Publisher post-migration steps, see Post-Migration Tasks for Oracle Analytics Publisher.

Required

If you have not done so already, review the introductory topics in this guide and complete the required pre-upgrade tasks.

The pre-upgrade tasks include cloning your production environment, verifying system requirements and certifications, purging unused data, and creating a non-SYSDBA user.

For a complete list of pre-upgrade tasks, see Pre-Upgrade Requirements.

Required

Review the prerequisites for Oracle Business Intelligence to Oracle Analytics Server migration.

Make sure that you meet the necessary requirements before you migrate your metadata and configuration to Oracle Analytics Server. Additionally, analyze and optimize your Oracle Business Intelligence system by removing redundant content and merging and consolidating similar content. For more information, see Migration Prerequisites.

Required

Download and install the Fusion Middleware Infrastructure and Oracle Analytics Server distributions.

The Infrastructure distribution combines the WebLogic Server and the Java Required Files (JRF) that are required to set up the foundation to install other Fusion Middleware products.

As per the upgrade topology defined in this guide, you must install the Infrastructure in a new Oracle home.

To install the product distributions, follow the procedure that is described in Installing the Product Distributions.

Required

Create the required Oracle Analytics Server schemas.

The schemas that you create will vary depending on your existing schema configuration.

To create schemas with the Repository Creation Utility (RCU), see Creating the Required Oracle Analytics Server Schemas.

Required

Configure the Oracle Analytics Server domain.

To configure the Oracle Analytics Server domain with the Configuration Assistant, see Configuring Oracle Analytics Server Domain with the Configuration Assistant.

Required

Stop the servers and processes.

You must stop the Oracle Analytics Server instance, OBIS1, OBIPS1, Administration Server, Managed Servers, and the Node Manager before you start the migration. For the complete procedure, see Stopping Servers and Processes.

Required

Use the appropriate migration tool depending on the release of Oracle Business Intelligence or Oracle Analytics Server .

To migrate from Oracle Business Intelligence 11g, you must generate the BI Migration Tool jar file by using the BI Migration Script (migration-tool.sh|cmd). For the complete procedure, see Generating the BI Migration Tool (bi-migration-tool.jar).
To migrate from Oracle Business Intelligence 12c, navigate to (Linux)12c_DOMAIN_HOME\bitools\bin\ folder or (Windows)12c_DOMAIN_HOME/bitools/bin/ folder to use the export command specific to the Oracle Business Intelligence release.

Required

Create an export bundle.

The export bundle consists of the metadata information from the Oracle Business Intelligence home.

To create the export bundle (.jar file) from a 11g system, see Creating the Export Bundle.
To create the export bundle (.bar file) from a 12c system, see Export Metadata Using Command Line.

Required

Import the export bundle in Oracle Analytics Server.

You must import the export bundle in Oracle Analytics Server.

To import the export bundle from a 11g system, use the BI Migration Script (migration-tool.sh|cmd). The BI Migration Script automatically determines the Oracle home and the Domain home directories. To import the bundle, see Importing with the BI Migration Script (migration-tool.sh|cmd).
To import the export bundle from a 12c system, use the Oracle Analytics Server Console to upload and restore the export bundle. See Import Metadata in Oracle Analytics Server

Required

Start the servers and processes.

To start the Oracle Analytics Server, OBIS1, OBIPS1, Administration Server, Managed Servers, and the Node Manager, see Starting Servers and Processes.

Required

Complete the post-migration steps.

For Oracle Analytics Server post-migration steps, see Post-Migration Tasks.

For Oracle Analytics Publisher post-migration steps, see Post-Migration Tasks for Oracle Analytics Publisher.