PK uLoa, mimetypeapplication/epub+zipPK uL 3 OEBPS/GUID-233D0EE0-A77E-4507-B76F-09B80F11BA7A.htmc
The Enterprise Manager Fusion Middleware Control is used to manage the log configuration for the Oracle BI components. You must manually examine the log configuration settings in the 11g system and apply the same settings to your 12c system.
After migrating the 11g configuration to a new 12c environment, you must migrate the scheduler jobs and the job history data from the 11g BIPLATFORM schema to a 12c BIPLATFORM schema. You can connect to 12c BIPLATFROM schema through SQL*PLUS or any other tool and execute the script.
Note:
Oracle does not support the migration of scheduler data from DB2 and SQL Server databases at this point. Migration of scheduler data is only supported by Oracle database.Ensure that you configure the environment as per Oracle recommendations in readiness for the migration.
For a procedure to start and stop Administration server and Managed servers, see Starting and Stopping Administration and Managed Servers and Node Manager and for a procedure to start and stop the BI instance, see Starting and Stopping Components in Administering Oracle Fusion Middleware.
You have the JDK version 1.8.0_77 installed on your system.
You have stopped OBIS1 and OBIPS1.
This appendix provides procedures to handle exceptions during or after migrating from Oracle BI 11g to 12c.
Oracle has introduced many enhancements to existing features in the 12c release for Business Intelligence. Sometimes, these enhancements replace the existing functionality or reimplement it in a different way. Wherever possible, the existing 11g functionality and configuration is migrated to the corresponding 12c system. Although the appearance and behavior of the 12c 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 Oracle BI 11g to the 12c environment. The goal of this process is to not exactly replicate the appearance and behavior of the original 11g system in the 12c environment. Replicating the 11g appearance and behavior is time-consuming and sometimes difficult, if not impossible. For example, the dashboards and prompts are represented differently in 12c and would require significant manual intervention to recreate the 11g appearance. It also undermines the rationale behind moving on to Oracle BI 12c; namely, to take advantage of the enhancements introduced in 12c.
Oracle BI Server: This includes NQSConfig.INI, and opmn.xml environment.
Oracle BI Presentation Services: This includes instanceconfig.xml.
Oracle BI Publisher: This includes scanner.xml, xdo.cfg, xmlp-server-config.xml, datasources.xml, xdodelivery.cfg, cupsprinters.cfg, the Map directory, and the Plugins directory.
The following metadata is migrated:
Content (WebCat), model (RPD), and the authorization policy securing it (Java AuthoriZatioN (JAZN)).
However, OBIS property is migrated.
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 12c 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 12c system with a configured domain. You must set up the 12c domain to provide sufficient infrastructure to run the BI Migration Tool and allow it to repackage itself. The 12c domain can be empty at this stage.
The Fusion Middleware Control is used to manage some of the important configurations for Oracle BI. You must manually examine the configuration of the General, Presentation, Performance, and Mail sections of the Fusion Middleware Control 11g and apply the same settings to the 12c system.
Oracle BI 12c (12.2.1.1) is the latest Business Intelligence release from Oracle. Migrating from Oracle BI 11g to 12c requires careful preparation, planning, and testing. Oracle provides tools and technology to automate much of the migration process. However, the precise strategy that you want to adopt depends on the configuration of the existing 11g system and the required configuration of the 12c system.
This document assumes that you have sufficient knowledge to debug and fix issues encountered in Oracle BI 12c. It also assumes that you have downloaded the Oracle BI 12c software and you have an existing Oracle BI 11g instance installed and running on your system.
Note:
The metadata and configuration migration is an out-of-place process. The migration process does not affect the existing 11g system in the production environment. You can continue to use the existing 11g system until you are ready to roll out the 12c system.To help you develop an effective migration strategy, Oracle recommends that you complete the following steps:
The migration strategy that you ultimately implement can be unique to your particular situation and depends on specific topologies and organizational requirements.
After performing a sample migration and verifying that the data is migrated as expected in to the 12c system, you can proceed to migrate the entire Oracle BI 11g system.
The following flowchart shows the flow of the migration process.
Figure 1-1 BI Migration Process Flow
Table 1-1 provides a high-level summary of the steps you must perform to migrate from Oracle BI 11g to 12c.
Table 1-1 High-level Summary of the Migration Process
Step Number | Step Description | More Information |
---|---|---|
1 | Install and configure Oracle BI 12c software. | For a procedure to install BI 12c, seeInstalling Oracle Business Intelligence in Installing and Configuring Oracle Business Intelligence. For a procedure to configure the 12c domain, see Configuring Oracle Business Intelligence in Installing and Configuring Oracle Business Intelligence. |
2 | Generate the BI Migration Tool (bi-migration-tool.jar) and copy it from the 12c Oracle Home to the 11g system. | None. |
3 | Create an export bundle using the BI Migration Tool on the 11g system. | See Creating the Export Bundle. |
4 | Import the export bundle using the BI Migration Script (migration-tool.sh|cmd). | See Importing with the BI Migration Script (migration-tool.sh|cmd). |
5 | Complete the post-installation steps. | For BI EE, see Post Migration Steps for Oracle BI EE. For BI Publisher, see Post Migration Steps for Oracle BI Publisher. For Essbase, see Post Migration Steps for Essbase. |
This appendix lists the differences in appearance and functionality of the Oracle BI 12c system after migration.
Oracle Business Intelligence Release 12c includes many new and enhanced features. To learn about the features and enhancements, see the "What's New" sections described in those guides.
This topic describes the procedure to remove the BISystemUser policy from the WebLogic Console.
This document describes how to migrate data from Oracle Business Intelligence the 11g environment to the 12c environment.
After completing data migration, manually migrate the configuration settings from the 11g system in to the 12c system and complete the post migration tasks.
See “Understanding Essbase Deployed in BI 12.2.1” in Oracle® Essbase Database Administrator's Guide for the procedure to migrate the following configuration settings from the 11g system in to the 12c system and to complete the post migration tasks:
Oracle Business Intelligence 12c is tightly integrated with the Oracle Fusion Middleware Security architecture and delegates core security functionality to components of that architecture. By default, an Oracle Business Intelligence installation is configured with an authentication provider that uses the Oracle WebLogic Server embedded LDAP server for user and group information. The Oracle Business Intelligence default policy store provider and credential store provider stores credentials, application roles, and application policies in files in the domain. You must manually migrate the Oracle BI WebLogic security configuration from the 11g system to the 12c system.
The 12c configuration might fail with a TRANSFORMBAREEXCEPTION error, if any objects in the catalog are older than Release 11.1.1.7. You can confirm the need to update the catalog items by viewing the metrics in Fusion Middleware Control. In the Catalog folder, find a metric called Reads Needing Upgrade with the description "The number of objects read that required upgrading." If the number is large, then you can resolve this issue by updating objects in the catalog using the Administration page in Presentation Services.
Oracle Fusion Middleware Mapviewer (MapViewer) is a programmable tool for rendering maps using spatial data managed by Oracle Spatial and Graph or Oracle Locator (also referred to as Locator). MapViewer provides tools that hide the complexity of spatial data queries and cartographic rendering, while providing customizable options for more advanced users. These tools can be deployed in a platform-independent manner and are designed to integrate with map-rendering applications. After migrating the data, you must manually modify the 12c MapViewer configuration file to contain the same contents as the 11g file except the Logging section.
Make sure that the XMLP and the BI JavaHost settings match with the settings specified for the configuration of the 11g system.
BISystemUser is not supported in the 12c environment. When the users and policies are migrated from an 11g instance, the JMSResource policy blocks the scheduled jobs. Therefore, you must remove this policy from the JMSResource security configuration. You can manually remove the BISystemUser policy from WebLogic console. Alternatively, you can execute a WLST (Python) script to accomplish this task.
Migrating the metadata and configuration from Oracle Business Intelligence 11g to 12c is an out-of-place process performed by using the BI Migration Tool. This tool creates an Oracle BI 11g metadata archive which contains system security configuration information, the Oracle BI repository, and the Oracle BI Presentation Services Catalog of the 11g system.
This section explains the process to migrate Oracle BI metadata and configurations from an Oracle BI 11g (Release 11.1.1.7 or later) to Oracle BI 12c (Release 12.2.1.1) instance.
Note:
The BI Migration Tool does not preserve any customized features of the 11g system. You must manually copy the customized features of 11g system to the 12c system post migration.After migrating the data, you must manually enable the ClusterEnabled parameter in the ClusterConfig.xml file to turn on the cluster instances on the 12c system.
Most of the security configuration related to application roles, security grants, and application policies are migrated to the Oracle Enterprise Manager Fusion Middleware Control 12c during the migration process. You must examine and manually apply any special Security Provider configuration in the Fusion Middleware Control 12c.
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.
Table 2-4 Parameter Description: 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. This allows you to also migrate the configuration along with the data. |
<export bundle> | The path where the export bundle is located. |
<service instance name> | Specifies the name of the service instance, which is service1. |
Note:
It takes about 10 more minutes for the Application roles and policies to migrate after the migration process is complete.After completing the import process, you must start OBIS1 and OBIPS1 which you stopped before beginning the migration process.