After migrating the Oracle BI EE metadata, manually migrate the configuration settings for catalog groups and other components such as security for WebLogic and Enterprise Manager, BI Server, and BI Presentation Services.
Catalog groups are a feature of Oracle BI EE that allows administrators to organize users and application roles for security administration purposes.
In Oracle BI Release 12c (12.2.1.1 and higher), catalog groups are deprecated. The catalog groups are migrated by the upgrade process to Application roles.
After migrating the data, manually migrate the configuration information from the 11g system to the 12c system, which includes WebLogic security, Enterprise Manager security, the managed BI configurations, BI logs, BI Server, and BI Presentation Server configuration settings.
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.
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.
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.
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.
Various files for the BI Server contain configuration information: odbc.ini and tnsnames.ora. The odbc.ini file contains non-Oracle data source (DSN) connection information. The tnsnames.ora file contains network service names mapped to connect descriptors for the local naming method, or net service names mapped to listener protocol addresses. You must examine these 11g files and manually copy the configuration information to the respective 12c files.
The Oracle BI Presentation Services process hosts most of the business logic of the Web server and provides the framework and interface for the presentation of business intelligence data to web clients. The userpref_currencies.xml file defines the currency options that are displayed in the Currency box of the Preferences tab of the My Account dialog. The bridgeconfig.properties file contains the Presentation Services Plug-in information. You must examine these 11g files and manually copy the configuration information to the respective 12c files.
You must configure the database to use the appropriate DataDirect drivers. If you are using a database that is already configured to use the DataDirect drivers, modify the database configuration's odbc.ini file to use the correct DataDirect drivers.
The Oracle BI Server supports the collection of usage tracking data. When usage tracking is enabled, the BI Server collects usage tracking data for each query. The statistics are then written to a usage tracking log file or are inserted directly in to a database table. After you complete migrating and configuring the 12c system, you must enable usage tracking in the NQSConfig.INI file.
Note:
Ensure that the queries of the BI Server are being tracked in the table by view data.After configuring the 12c system, you must configure the SQL Server settings in the odbc.ini file.
After migrating the data, you must add roles and permissions for BI Administrator, BI Author, and BI Consumer groups.
You must configure the MySQL database to use the DataDirect driver. If you are using a database that is already configured to use the DataDirect drivers, modify the database configuration's odbc.ini file to use the correct DataDirect drivers.
Make sure that the XMLP and the BI JavaHost settings match with the settings specified for the configuration of the 11g system.
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.
Hardware acceleration affects the autocompletion of features such as dashboard prompts, trellis charts and microcharts, Summary Advisor functionality, and aggregate persistence for the TimesTen In-Memory database. Therefore, you must manually enable the bi:hw-acceleration flag in the 12c bi-config.xml file post migration. You must also enable the bi:compat-mode-11g flag, so that the state of the 11g system is preserved at run time.
The compatibility framework allows the BI Server to add new features or bug fixes in Oracle BI 12c (12.2.1.1 and later) that are not compatible with the Oracle BI 11g releases while providing a flexible framework that enables the BI Server to operate in a compatibility mode with the earlier major release. Individual features and bug fixes can be enabled or disabled independently using compatibility flags. Alternatively, you can set all the compatibility flags to the default values using a single COMPATIBLE_RELEASE flag for the Oracle BI system to be compatible with the earlier release, which is 11.1.1.9. Add the COMPATIBLE_RELEASE parameter to the NQSConfig.INI file to ensure that the migrated 12c environment behaves as closely as possible to Oracle Business Intelligence 11g Release 1 (11.1.1.9) environment.
Note:
If the COMPATIBLE_RELEASE parameter is not set, then the system defaults to the behavior of the current release, such as 12.2.1.2.The framework does not distinguish individual bundle patches (only the first four digits of the version number are significant for determining compatibility).
When applying new features, enhancements, or bug fixes that are not inherently backward-compatible, ensure that you specify a compatibility flag using the guidelines described in this topic.
Note:
The NQSConfig.INI file does not contain the COMPATIBLE_RELEASE parameter by default. The global bi:compat-mode-11g is the default flag and it applies to all Oracle BI EE components. When the bi:compat-mode-11g element in the bi-config.xml file is set totrue
, the BI Server compatibility framework behaves as if the COMPATIBLE_RELEASE were set to 11.1.1.9 and it disables any features or bug fixes that would cause major compatibility issues during migration from 11g to 12c. However, if you explicitly edit the NQSConfig.INI file to set the COMPATIBLE_RELEASE parameter or any other compatibility flag, then the setting in the NQSConfig.INI file takes precedence over the global bi:compat-mode-11g flag specified in the bi-config.xml file.In addition to setting the general COMPATIBLE_RELEASE parameter, you can set compatibility flags for specific features or bug fixes, which begin with the prefix "OBIS_". Instructions to set these specific compatibility flags are provided by the support team to solve certain issues on a need basis. For example,
[ COMPATIBILITY ] COMPATIBLE_RELEASE=11.1.1.9; OBIS_ENABLE_DIMENSIONALITY=0;
Setting the COMPATIBLE_RELEASE parameter or specific compatibility flags in the NQSConfig.INI file applies the changes to the entire system. You can also set the COMPATIBLE_RELEASE parameter or the specific feature flag as a session variable or an environment variable so that the compatibility mode is set to specific reports or dashboards. You can do this by adding a query prefix to an analysis request. The following is an example of a variable setting:
set variable COMPATIBLE_RELEASE='11.1.1.9':
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.
To avoid authentication issues post migration, you must uncheck the Required for Authentication option in the DYNAMIC_OLAP_LOGIN initialization block.
Note:
Follow this procedure only if you are migrating from Oracle BI Release 11.1.1.7 to 12c.