4 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 the BI Publisher Configuration
Migrate the customized 11g BI Publisher configuration settings to the 12c environment using the BI Publisher Migration Tool (BIP12CUpgrade.sh).
- 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.
- Configuring Passwords for Oracle BI Publisher Data Sources
The passwords for all data sources in the datasources.xml file are not migrated during the migration. You must manually enter and save the password for each data source using the Administration page in BI Publisher.