Catalog groups were a feature of Oracle BI EE that allowed administrators to organize users and application roles for security administration purposes.

In Oracle Analytics Server, catalog groups are obsolete. The catalog groups are migrated by the upgrade process to application roles.

• Migrating the Security Configuration with Oracle WebLogic Server
  Oracle Analytics Server delegates user authentication and the group membership authorization to the external identity providers or the built-in Oracle WebLogic Server embedded LDAP (default authenticator).
• Migrating the Policy and Credential Store Configuration
  Most of the security configuration related to application roles, security grants, and application policies are migrated during the migration process. The default policy store provider and credential store provider stores credentials, application roles, and application policies in files in the domain. You must examine and manually apply any special Security Provider configuration in Oracle Analytics Server.
• Migrating the Oracle Enterprise Manager Fusion Middleware Control Managed Business Intelligence Configurations
  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 of the Oracle Business Intelligence system and apply the same settings to the Oracle Analytics Server system.
• Migrating the Oracle Enterprise Manager Fusion Middleware Control Managed Business Intelligence Log Configuration
  The Oracle 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 Oracle Business Intelligence system and apply the same settings to your Oracle Analytics Server system.
• Migrating the Oracle BI Server Configuration
  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 Oracle Business Intelligence files and manually copy the configuration information to the respective Oracle Analytics Server files.
• Migrating the Oracle BI Presentation Server Configuration
  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. Examine these Oracle Business Intelligence files and manually copy the configuration information to the respective Oracle Analytics Server files.

You must re-configure your data source connections to use the appropriate ODBC drivers. If you are using a data source connection that is already configured to use ODBC drivers in Oracle Business Intelligence, modify the data source configuration's odbc.ini file in Oracle Analytics Server to use the correct ODBC drivers.

1. Open the odbc.ini file located at the following location:
   • (Linux) DOMAIN_HOME/config/fmwconfig/bienv/core/odbc.ini
   • (Windows) Open Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\odbc.ini
   Replace the value of DOMAIN_HOME with the actual path to the Oracle Analytics Server Domain home you created when you installed the Oracle Analytics Server software.
2. Update the ODBC entry to use the appropriate drivers.
3. Update all the existing data source names (DSNs) to the correct ODBC driver version.
4. Save and close the odbc.ini file.

Oracle Analytics Server supports the collection of usage tracking data. When usage tracking is enabled, Oracle Analytics 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 theOracle Analytics Server system, you must enable usage tracking in Oracle Analytics Server Console.

1. On the Oracle Analytics Server Home page, click the Navigator, and select Console.
2. Set the usage tracking parameters. See Set Usage Tracking Parameters.

Make sure that the XMLP and Oracle BI JavaHost settings match with the settings specified for the configuration of the Oracle Business Intelligence system.

1. View the config.xml file on the Oracle Business Intelligence and Oracle Analytics Server.
   The file is present at the following location on the Oracle Business Intelligence:
   • (Linux) BI_DOMAIN_HOME/config/OracleBIJavaHostComponent/coreapplication_obijh1/config.xml
   • (Windows) BI_DOMAIN_HOME\config\OracleBIJavaHostComponent\coreapplication_obijh1\config.xml
   The file is present at the following location on the Oracle Analytics Server:
   • (Linux) NEW_DOMAIN_HOME/config/fmwconfig/biconfig/OBIJH/config.xml
   • (Windows) NEW_DOMAIN_HOME\config\fmwconfig\biconfig\OBIJH\config.xml
2. Verify that the XMLP configuration on both the Oracle Business Intelligence and the Oracle Analytics Server systems is as shown in the following code block:

   <XMLP> 
   <InputStreamLimitInKB>8192</InputStreamLimitInKB> 
   <ReadRequestBeforeProcessing>true</ReadRequestBeforeProcessing>
   </XMLP>

3. Verify that the OBIJH_ARGS="-server -Xmx1024M -Xrs" parameter in the setOBIJHEnv.sh file in Oracle Analytics Server matches with the "start-args" value="-server -Xmx1024M -Xrs parameter in the opmn.xml file in Oracle Business Intelligence.
   The opmn.xml file is located at the following location on the Oracle Business Intelligence system:
   MW_HOME/instances/config/OPMN/opmn/opmn.xml

   <process-type id="OracleBIJavaHostComponent" module-id="CUSTOM"> 
   <module-data> 
   <category id="start-parameters"> 
   <data id="start-executable" value="$ORACLE_HOME/jdk/bin/java"/> 
   <data id="start-args" value="-server -Xmx4096M -Xrs 
   .
   .
   .

   The setOBIJHEnv.sh|.cmd file is located at the following location on the Oracle Analytics Server system:
   • (Linux) DOMAIN_HOME/bi/modules/oracle.bi.cam.obijh/setOBIJHEnv.sh
   • (Windows) DOMAIN_HOME\bi\modules\oracle.bi.cam.obijh\setOBIJHEnv.cmd
   Location of the obijh.properties file:
   • (Linux) [DOMAIN_HOME]/config/fmwconfig/bienv/OBIJH/obijh.properties
   • (Windows) [DOMAIN_HOME]\config\fmwconfig\bienv\OBIJH\obijh.properties

After migrating the data, you must manually enable the ClusterEnabled parameter in the ClusterConfig.xml file to turn on the cluster instances on the Oracle Analytics Server.

1. Open the ClusterConfig.xml file for editing, located at the following location:
   • (Linux) DOMAIN_HOME/config/fmwconfig/biconfig/core
   • (Windows) DOMAIN_HOME\config\fmwconfig\biconfig\core
2. Locate the following:

   <ClusterEnabled>false</ClusterEnabled> 

   Change it to the following:

   <ClusterEnabled>true</ClusterEnabled> 

3. Save and close the file.

The compatibility framework allows the Oracle Analytics Server to add new features that are not compatible with the Oracle Business Intelligence releases while providing a flexible framework that enables Oracle Analytics Server to operate in a compatibility mode. 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 Analytics Server system to be compatible with the earlier release. Add the COMPATIBLE_RELEASE parameter to the NQSConfig.INI file to ensure that the migrated Oracle Analytics Server environment behaves as closely as possible to Oracle Business Intelligence environment.

Oracle recommends you to configure OBIEE Compatibility Release using the Oracle Analytics Server Console. See Performance and Compatibility Options.

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.

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 theOracle Analytics Server MapViewer configuration file to contain the same contents as the Oracle Business Intelligence file except the Logging section.

1. Go to the Oracle Analytics Server Fusion Middleware MapViewer Administration Console (http://AnalyticsServer_host:port/mapviewer).
2. Create a copy of the default Oracle Analytics Server MapViewer configuration file.
3. Overwrite the contents in the copy of the Oracle Analytics Server MapViewer configuration file with the content from the mapViewerConfig.xml file from the Oracle Business Intelligence MapViewer install.
4. Replace the logging section of the MapViewer configuration file copy with the settings from the default Oracle Analytics Server MapViewer configuration file.
5. Update the logging settings log levels of the MapViewer configuration file as needed for Oracle Analytics Server.
6. Click Save on theOracle Analytics Server MapViewer Administration Console and then click Restart.

To avoid authentication issues post-migration, you must review and update initialization blocks that the Required for Authentication option enabled.

1. Open the repository (semantic model) in offline mode.
   1. Change to the following directory on Oracle Analytics Server:
      (Linux) DOMAIN_HOME/bitools/bin/
      (Windows) DOMAIN_HOME\bitools\bin\
      Replace the value of DOMAIN_HOME with the actual Domain home on your Oracle Analytics Server.
   2. Run the following command:
      sh data-model-cmd.sh downloadrpd –u uname –p pwd –o downloaded.rpd –w rpd_password
      Where,

      -o is the output repository (semantic model)
      -w rpd_password  is the repository (semantic model) password, say Admin123

   3. Open the downloaded repository (semantic model) offline in Model Administration Tool, which you installed with the client installer.
2. Complete the following steps:
   1. From the Manage menu in Model Administration Tool, select Variables.
   2. In the Variable Manager dialog, from the Action menu, select Session, then Initialization Blocks.
   3. In the Variable Initialization Block dialog, review the initialization blocks with Required for Authentication configured.
   4. Locate DYNAMIC_OLAP_LOGIN, open the DYNAMIC_OLAP_LOGIN properties, and uncheck the Required for Authentication checkbox.
   5. Click Apply and save the repository (semantic model).
3. Open the repository (semantic model) in online mode using the uploadrpd command.
   DOMAIN_HOME/bitools/bin/data-model-cmd.sh uploadrpd –u uname –p pwd –i downloaded.rpd –w rpd_password

You must manually copy the following configuration files after the migration: writebacktemplate.xml, userpref_currencies.xml, and bicustom.ear.

1. Change to the following directory:
   • (Linux) DOMAIN_HOME/bi/bifoundation/web/msgdb/messages
   • (Windows) DOMAIN_HOME\bi\bifoundation\web\msgdb\messages
2. Copy the writebacktemplate.xml file to the Oracle Analytics Server instance.
3. Change to the following directory:
   • (Linux) APPLICATION_HOME/bi/bidata/components/OBIPS/
   • (Windows) APPLICATION_HOME\bi\bidata\components\OBIPS\
4. Copy the bicustom.ear file to the Oracle Analytics Server instance.
5. Change to the following directory:
   • (Linux) DOMAIN_HOME/config/fmwconfig/biconfig/OBIPS
   • (Windows) DOMAIN_HOME\config\fmwconfig\biconfig\OBIPS
6. Copy the userpref_currencies.xml file to the Oracle Analytics Server instance.
7. Open the userpref_currencies.xml file for editing and add the following lines:

   <Config>
   <UserCurrencyPreferences currencyTagMappingType="static">
     <UserCurrencyPreference sessionVarValue="gc1" displayText="Global Currency 1" currencyTag="int:USD" />
     <UserCurrencyPreference sessionVarValue="gc2" displayText="Global Currency 2" currencyTag="int:euro-l" />
     <UserCurrencyPreference sessionVarValue="gc3" displayText="Global Currency 3" currencyTag="loc:ja-JP" />
     <UserCurrencyPreference sessionVarValue="orgc" displayText="Org Currency" currencyTag="loc:en-BZ" />
     <UserCurrencyPreference sessionVarValue="lc1" displayTag="int:DEM" currencyTag="int:DEM" />
   </UserCurrencyPreferences>
   </Config>

   Save and close the file.
8. Change to the following directory:
   • (Linux) DOMAIN_HOME/config/fmwconfig/biconfig/OBIPS
   • (Windows) DOMAIN_HOME\config\fmwconfig\biconfig\OBIPS
9. Open the instanceconfig.xml file for editing and add the following line:

   <UserprefCurrenciesConfigFile>DOMAIN_HOME/config/fmwconfig/biconfig/OBIPS/userpref_currencies.xml</UserprefCurrenciesConfigFile>

   Save and close the file.
10. Restart the services.

In an analysis, content developers can control the text that is displayed when the results of the analysis return no data. Content developers can accept the default message, or they can customize the text of the message, including by inserting HTML formatting codes in the message.

If content developers customized the message and included HTML codes in Oracle Business Intelligence, then the message is displayed with the codes showing as readable text in Oracle Analytics Server, rather than performing their functions to format the message. To work around this issue, open the Analysis Properties dialog for each analysis whose custom message includes HTML codes and select the Contains HTML/JavaScript/CSS Markup option.

Use System Settings in Oracle Analytics Server Console to enable Allow HTML/JavaScript/CSS Content if you want the Contains HTML/JavaScript/CSS Markup option displayed in various dialogs and editors where you can apply formatting.

Review the structure of the Catalog after migration.

1. Open the instanceconfig.xml file for editing from the following location:
   • (Linux) DOMAIN_HOME/config/fmwconfig/biconfig/OBIPS
   • (Windows) DOMAIN_HOME\config\fmwconfig\biconfig\OBIPS
2. Add the following elements within the <Catalog></Catalog> nodes:
   • To remove all empty folders: <CleanEmptyFolderInHome>true</CleanEmptyFolderInHome>
   • To relocate existing folders to their new locations: <CoalesceHomeDirectoryFolders>true</CoalesceHomeDirectoryFolders>
3. Save and close the file.

When you restore content from a snapshot or migrate content from a different environment, delivery schedules defined for agents, analyses, and dashboards in the snapshot aren’t restored or activated right away. When you’re ready to restore deliveries on your system, you can decide whether to enable or disable delivery schedules on your system. This is useful as you might not want to immediately start delivering content.

1. In the Oracle Analytics Home page, click the Navigator, and then click Console.
2. Click Monitor Deliveries.
3. To restore deliveries, click the Action menu for the page and select Restore Deliveries.
4. Select whether to restore and activate deliveries or restore deliveries only. Select one of the following:

   • Maintain Delivery Schedule Status

     All delivery schedules maintain their status (enabled or disabled).

     • Existing delivery schedules remain unchanged.
     • New delivery schedules created during the restore process inherit the schedule status that’s defined in the corresponding agent, analysis or dashboard.

     For example, this option is useful when you restore deliveries in a production environment where you want deliveries to be active immediately.

   • Disable Delivery Schedules for New Deliveries

     Delivery schedules that are created during the restore process for agents, analyses, and dashboards are disabled. Existing delivery schedules remain unchanged.

     For example, this option is useful when you restore deliveries in a test environment where you don’t need to activate deliveries immediately.

   • Disable All Delivery Schedules And Delete All History (Not recommended)

     All delivery schedules are disabled during the restore process and any delivery history is deleted.

     • Existing delivery schedules are disabled.
     • New delivery schedules created for agents, analyses, and dashboards during the restore process are disabled.
     • Historical delivery details no longer available.

     This option is not recommended. If you do select this option, you must manually enable delivery schedules for all agents, analyses, and dashboards.

5. Click Restore.
6. To activate a delivery, click the Action menu for the delivery, and select Enable.

   To activate multiple deliveries at once, select Shift + click or Ctrl + click to select all the deliveries you want to activate, then right-click and select Enable.

   If necessary, click Edit to redefine the delivery schedule.

• Migrating Scheduler Jobs and Job History
  After migrating the Oracle Business Intelligence configuration to a new Oracle Analytics Server environment, you must migrate the scheduler jobs and the job history data from the Oracle Business Intelligence BIPLATFORM schema to a BIPLATFORM schema. You can connect to BIPLATFROM schema through SQL*PLUS or any other tool and run the script.
• Removing the BISystemUser Policy from the JMSResource Security Configuration
  BISystemUser is not supported in the Oracle Analytics Server environment. When the users and policies are migrated from an Oracle Business Intelligence 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 run a WLST (Python) script to accomplish this task.