This chapter describes how to upgrade from Oracle Forms or Reports 11g to Oracle Forms or Reports 12c (12.2.1).
The following topics are covered:
Section 5.1, "Planning an Upgrade to Oracle Forms 12c (12.2.1)"
Section 5.2, "Preparing to Upgrade to Oracle Forms 12c (12.2.1)"
Section 5.4, "Post-Upgrade Steps After Upgrading to Oracle Forms 12c (12.2.1)"
Section 5.5, "Planning an Upgrade to Oracle Reports 12c (12.2.1)"
Section 5.6, "Preparing to Upgrade to Oracle Reports 12c (12.2.1)"
Section 5.8, "Post-Upgrade Steps After Upgrading to Oracle Reports 12c (12.2.1)"
If you are running any of the following software versions, you can use the instructions in this guide to upgrade to Oracle Forms 12c (12.2.1):
Oracle FMW 11g (Release 1) Forms to Oracle Forms 12c (12.2.1).
Oracle FMW 11g (Release 2) Forms to Oracle Forms 12c (12.2.1).
Before you begin to upgrade to Oracle Forms 12c (12.2.1), you must run Forms upgrade extension on the remote Forms nodes to extract Forms configuration residing on the remote nodes.
Note: You are required to perform these steps only if you have any remote Forms nodes, which you may have added using extend domain or expand cluster scenario.
To run Forms upgrade extension on the remote Forms nodes:
Run forms-upgrade-ext.sh (forms-upgrade-ext.bat) script on each remote node and pass it collect option. It will extract and package Forms configuration files on that remote node.
The forms-upgrade-ext.sh is installed in the following directory:
$FORACLE_HOME/forms/plugins/upgrade
Copy the artifacts from all the remote nodes to the Admin Server node.
Run forms-upgrade-ext.sh (forms-upgrade-ext.bat) script on the Admin Server node and pass it apply option. It will extract the Forms configuration from the remote node artifacts and apply it to the Domain.
The process of upgrading to Oracle Forms 12c (12.2.1) includes the following two steps:
Note:
In the 11g, Forms did not require the RCU schema, but starting with 12c all the WLS domains require RCU schema to be setup. Hence, before you perform these steps, ensure that you create a schema (standard schema for 12c components) in RCU before you run the WLS Reconfig wizard.To re-configuring the 11g Domain using the WLS Reconfig wizard:
Run the Reconfig wizard from the following location:
$FORACLE_HOME/oracle_common/common/bin/reconfig.sh
Provide the location of the 11g FMW Domain for upgrade.
Enter the RCU schema information.
Select only the Managed Servers in the wizard.
Don't select the system components option. Those will be automatically configured/upgraded by the Upgrade Assistant.
Leave the default selections on the Node Manager screen. Enter user name and password if needed.
Select JRF-MAN-SVR and FORMS-MAN-SVR server groups for all the Forms managed servers, including the default Forms managed servers WLS_FORMS, WLS_FORMS1, etc. and any other Forms managed servers users that may have been added after the 11g installation.
Click Next until you get to the last screen of the Reconfig wizard.
Run the 12c Upgrade Assistant to complete the upgrade.
To run the Upgrade Assistant:
Run the 12c Upgrade Assistant from the following location:
$FORACLE_HOME/oracle_common/upgrade/bin/ua
Provide the location of the reconfigured 12c domain.
Select the prerequisite check boxes and click Upgrade.
Review the following list of post-upgrade tasks you might have to perform after using the Upgrade Assistant to upgrade to Oracle Forms 12c (12.2.1):
Regenerate the Forms application files: fmx's, mmx's, and plx's to run on Oracle Forms Services 12c (12.2.1).
If you deployed the Oracle Forms Services J2EE custom application ear file (formsapp.ear) file to override the context root or Forms servlet alias, then you should perform similar steps in the 12c (12.2.1) Oracle WebLogic Server domain.
For more information, see "Custom Deployment of Forms Java EE Application" in the Oracle Fusion Middleware Forms Services Deployment Guide.
Manually copy any customizations to the shell scripts in the source Oracle home to the equivalent shell scripts that reside in Oracle Fusion Middleware 12c (12.2.1) Oracle instance directory.
Oracle Fusion Middleware 12c (12.2.1) does not support Java Runtime Environment (JRE) 1.6 or older. If necessary, upgrade your client JRE to 1.7 or 1.8 in order to run Oracle Forms 12c (12.2.1).
If you are running any of the following software versions, you can use the instructions in this guide to upgrade to Oracle Reports 12c (12.2.1):
Oracle FMW 11g (Release 1) Reports to Oracle Reports 12c (12.2.1).
Oracle FMW 11g (Release 2) Reports to Oracle Reports 12c (12.2.1).
Before you begin to upgrade to Oracle Reports 12c (12.2.1), you must run Reports upgrade extension on the remote Reports nodes to extract Reports configuration residing on the remote nodes.
Note: You are required to perform these steps only if you have any remote Reports nodes, which you may have added using extend domain or expand cluster scenario.
To run Reports upgrade extension on the remote Reports nodes:
Run reports-upgrade-ext.sh (reports-upgrade-ext.bat) script on each remote node in extract mode. It will extract and package Reports configuration files on that remote node.
The forms-upgrade-ext.sh is installed in the following directory:
$FORACLE_HOME/reports/plugins/upgrade
Copy the artifacts from all the remote nodes to the Admin Server node.
Run reports-upgrade-ext.sh (reports-upgrade-ext.bat) script on the Admin Server node in apply mode. It will extract the Reports configuration from the remote node artifacts and apply it to the Domain.
Run Upgrade Assistant in readiness mode and ensure that it is working properly.
$ORACLE_HOME/oracle_common/upgrade/bin/ua -readiness
The process of upgrading to Oracle Reports 12c (12.2.1) includes the following two steps:
Note:
In the 11g, Reports did not require the RCU schema, but starting with 12c all the WLS domains require RCU schema to be setup. Hence, before you perform these steps, ensure that you create a schema (standard schema for 12c components) in RCU before you run the WLS Reconfig wizard.To re-configuring the 11g Domain using the WLS Reconfig wizard:
Run the Reconfig wizard from the following location:
$FORACLE_HOME/oracle_common/common/bin/reconfig.sh
Provide the location of the 11g FMW Domain for upgrade.
Enter the RCU schema information.
Select only the Managed Servers in the wizard.
Don't select the system components option. Those will be automatically configured/upgraded by the Upgrade Assistant.
Leave the default selections on the Node Manager screen. Enter user name and password if needed.
Select JRF-MAN-SVR and REPORTS-MAN-SVR server groups for all the Reports managed servers, including the default Reports managed servers WLS_REPORTS, WLS_REPORTS1, etc. and any other Reports managed servers users that may have been added after the 11g installation.
Click Next until you get to the last screen of the Reconfig wizard.
Follow these manual steps to complete the Examine phase.
In the Examine screen for reports, you will see information about components in 11g but missing in 12c, or undeployed reports. Make a note of the component names and types.
Cancel the upgrade at this time, and create component/deploy reports 12c app.
Create reports components in 11g on to 12c using WLST commands: Start node manager, AdminServer.
Use WLST commands to create reports tools, reports servers, reports bridges. Use the same names available in the above step. See Section 2.4.8.1, "Provisioning a Machine" for more information on Provisioning.
Start Reports managed servers. This will cause reports 12c app to be deployed automatically.
Shutdown Nodemanager/Adminserver/Reports managed servers.
Run the 12c Upgrade Assistant to complete the upgrade.
To run the Upgrade Assistant:
Run the 12c Upgrade Assistant from the following location:
$FORACLE_HOME/oracle_common/upgrade/bin/ua
Provide the location of the reconfigured 12c domain.
Select the prerequisite check boxes and click Upgrade.
These steps are only required for Oracle Reports when 11g domains span multiple machines.
Review the following list of post-upgrade tasks you might have to perform after using the Upgrade Assistant to upgrade to Oracle Reports 12c (12.2.1):
For WLS:
Pack/Unpack domain for Remote machines.
Start remote managed servers, so that reports 12c app gets deployed there.
Shutdown remote managed servers.
For Reports:
In AdminServer machine--Extract reports upgraded files meant to be on remote machines.
$ORACLE_HOME/reports/plugins/upgrade/reports-upgrade-ext.sh extractRemote <domainHome> <wlsName> <jarFileName>
Repeat for each reports managed server which is targeted to remote machine.
Copy the respective jars to remote machine where that managed server is targeted.
$ORACLE_HOME/reports/plugins/upgrade/reports-upgrade-ext.sh applyRemote <domainHome> <instanceHome> <wlsName> <jarFileName>
Regenerate the Reports application files: fmx's, mmx's, and plx's to run on Oracle Reports Server 12c (12.2.1).
If you deployed the Oracle Forms Services J2EE custom application ear file (formsapp.ear) file to override the context root or Reports servlet alias, then you should perform similar steps in the 12c (12.2.1) Oracle WebLogic Server domain.
For more information, see "Custom Deployment of Reports Java EE Application" in the Oracle Fusion Middleware Forms Services Deployment Guide.
Manually copy any customizations to the shell scripts in the source Oracle home to the equivalent shell scripts that reside in Oracle Fusion Middleware 12c (12.2.1) Oracle instance directory.
Oracle Fusion Middleware 12c (12.2.1) does not support Java Runtime Environment (JRE) 1.6 or older. If necessary, upgrade your client JRE to 1.7 or 1.8 in order to run Oracle Reports 12c (12.2.1).