5 Post-Migration Tasks for Oracle BI Publisher

After completing the data migration, you must migrate the BI Publisher configuration, scheduler jobs, and job history. You must also remove the BISystemUser policy from the JMSResource security configuration.

• Migrating Scheduler Jobs and Job History
  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.
• Removing the BISystemUser Policy from the JMSResource Security Configuration
  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 Scheduler Jobs and Job History

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.

The bip_12c_scheduler_migration.sql script requires the user ID, the password, and the connection string for 11g BIPLATFROM schema. The script creates a database link called BIP11g_DBLINK and imports all schedule objects using that link. You must have Database Administrator privileges to run the script.

Note:

You cannot migrate scheduler data from DB2 and SQL Server databases. You can migrate scheduler data only from Oracle databases.

To migrate scheduler jobs and job history:

1. Change to the directory appropriate for your platform:
   (UNIX) NEW_ORACLE_HOME/bi/modules/oracle.bi.publisher/upgradeutil
   (Windows) NEW_ORACLE_HOME\bi\modules\oracle.bi.publisher\upgradeutil
   Replace NEW_ORACLE_HOME with the actual path to the 12c Oracle home you created when you installed the 12c software.
2. Connect to the target 12c BIPLATFORM schema from SQLPLUS or SQL Developer by entering the following command:
   sqlplus userid/password@connectionString -- for 12c RCU Schema
   For example:
   sqlplus username/[e-mail]:1521/pdborcl.yourcompany.com
3. Run the bip_12c_scheduler_migration.sql script, passing the command-line parameters 11g_RCU_SCHEMA, 11G_PASSWORD, 11G_CONNECTION_STRING, and 12C_BIPLATFORM_SCHEMA.
   Usage:

   SQL> @bip_12c_scheduler_migrationg.sql 11g_userid 11g_password 11g_connection_string

   Sample command:

   SQL> bip_12c_scheduler_migration.sql 11g_RCU_USERNAME 11g_PASSSWORD 11G_hostname.yourcompany.com:1521/orcl.yourcompany.com 12C_BIPLATFROM_SCHEMA_NAME
   System output:
   old 1: &&1
   new 1: adc00ccq_biplatform
   old 2: &&2
   new 2: your_password
   old 3: '&&3'
   new 3: 'bipdev4.yourcompany.com:1521/ora11g.yourcompany.com'
   old 4: '&&4'
   new 4: 12C_BIPLATFROM_SCHEMA_NAME
   Database link created.
   9979 rows created.
   9769 rows created.
   9739 rows created.
   4159 rows created.
   6 rows created.
   6 rows created.
   6 rows created.
   Commit complete.
   Database link dropped.
   SQL>

After the import operation completes, the database link is deleted.

Removing the BISystemUser Policy from the JMSResource Security Configuration

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.

• Manually Removing the BISystemUser Policy
  This topic describes the procedure to remove the BISystemUser policy from the WebLogic Console.
• Removing the BISystemUser Policy using a WLST Script
  This topic describes the procedure to remove the BISystemUser policy using a WLST script.

Manually Removing the BISystemUser Policy

This topic describes the procedure to remove the BISystemUser policy from the WebLogic Console.

To manually remove the BISystemUser policy:

1. Sign in to the WebLogic Console.
2. Under Services, click Messaging and then JMSModules, and select BipJmsResource.

   Figure 5-1 JMS Modules

   
   Description of "Figure 5-1 JMS Modules"
3. Under the Security tab, click Policies.
4. Under Policy Conditions, select the User: BISystemUser checkbox and click Remove.

   Figure 5-2 Settings for BipJmsResource

   
   Description of "Figure 5-2 Settings for BipJmsResource"
5. Restart the BI Publisher and check the scheduled jobs.

Removing the BISystemUser Policy using a WLST Script

This topic describes the procedure to remove the BISystemUser policy using a WLST script.

To remove the BISystemUser policy:

1. Copy the BIPRemoveJMSResourcePolicy.py script from the following location:
   (UNIX) NEW_ORACLE_HOME/bi/modules/oracle.bi.publisher
   (Windows) NEW_ORACLE_HOME\bi\modules\oracle.bi.publisher
2. Go to NEW_ORACLE_HOME/server/bin directory.
3. Set the WLS environment. Enter
   source ./setWLSEnv.sh
4. Run the script to remove JMS Resource policy. Enter
   java weblogic.WLST BIPRemoveJMSResourcePolicy.py <WL Admin Username> <WL Admin Password> <Admin Server URL: t3://localhost:port>
5. Sign in to the WebLogic Console and verify whether the policy is removed.