The procedures outlined in the following sections describe the high-level process of upgrading a basic WebCenter domain to 12c (12.2.1.1). Most upgrades follow these general procedures, but the actual upgrade procedures you will perform depend on which components are being upgraded. There may be additional pre- or post- upgrade procedures associated with your components. Therefore, you will need to locate the upgrade procedures for each component in your pre-upgrade environment to complete the domain upgrade.
For example, if your Oracle WebCenter domain includes Oracle WebCenter Content and WebCenter Portal, you would need to follow the procedures described in Upgrading Oracle WebCenter Content to 12c and Upgrading Oracle WebCenter Portal 11g Installations.
Table 3-1 Standard Upgrade Procedures
Step | Task |
---|---|
1 | Installing the Required Oracle Fusion Middleware Distributions for WebCenter |
2 | Creating Schemas for WebCenter 12c |
3 |
Running a Pre-Upgrade Readiness Check Optional Oracle strongly recommends that you run the pre-upgrade readiness check before starting the upgrade process. |
4 |
|
5 |
Reconfiguring the WebCenter Domain with the Reconfiguration Wizard |
6 |
Upgrading the Component Configuration with the Upgrade Assistant |
7 |
-readiness
mode to identify potential upgrade issues before you perform an actual upgrade.Before you can perform and upgrade to WebCenter 12c, you must install - but do not configure - the following Fusion Middleware distributions in your existing 11g domain:
Distribution | Installation Guide |
---|---|
Oracle Fusion Middleware Infrastructure |
Installing and Configuring the Oracle Fusion Middleware Infrastructure |
Oracle WebCenter Content (if you are upgrading Content or Enterprise Capture) |
Installing and Configuring Oracle WebCenter Content |
Oracle WebCenter Portal (if you are upgrading Portal) |
|
Oracle SOA Suite and Business Process Management |
WebCenter Content Imaging Upgrades Only: You must install Oracle SOA Suite 12c before upgrading Oracle WebCenter Content Imaging. If the 12c SOA binaries are not present, the upgrade will fail. Installing and Configuring Oracle SOA Suite and Business Process Management |
Review the 12c schema requirements before you can upgrade Oracle WebCenter:
Service Table (_STB)
Oracle Fusion Middleware 12c introduces a new required schema called Service Table (_STB). This schema is automatically created when you run the Repository Creation Utility (RCU) and must be created before you can upgrade your existing 11g deployment. For more information, see Understanding the Service Table Schema.
Oracle Platform Security Services (_OPSS)
WebCenter does not use the _OPSS schema directly, but requires that the OPSS schema be upgraded as part of the upgrade process. If you do not have an Oracle Platform Security Services (_OPSS) schema in your 11g environment, you must create one for 12c.
Audit Schemas (OPSS_AUDIT_VIEWER)
If you used an XML-based OPSS_AUDIT schema in 11g, then you will need to create a new 12c OPSS_AUDIT_VIEWER schema or the domain reconfiguration will fail.
To create the new schemas, you will use the Oracle Repository Creation Utility (RCU).
The Upgrade Assistant can be run in -readiness
mode to identify potential upgrade issues before you perform an actual upgrade.
The readiness check is a read-only operation that scans your existing domain or database schemas and produces a text file with the results of the scan. If your pre-upgrade environment has issues, you can correct those issues and then rerun the readiness check before you upgrade.
ORACLE_HOME/oracle_common/upgrade/logs
Note:
You can run the readiness check while the system is online. Depending on the comprehensiveness of the checks, the readiness checks can take more time to complete. Oracle recommends that you run the Readiness Check during slower usage periods to prevent performance degradation.-readiness
mode:
Go to the bin
directory:
On UNIX operating systems:
ORACLE_HOME
/oracle_common/upgrade/bin
On Windows operating systems:
ORACLE_HOME
\oracle_common\upgrade\bin
Enter the following command to start the Upgrade Assistant.
On UNIX operating systems:
./ua -readiness
On Windows operating systems:
ua.bat -readiness
You can also launch the Upgrade Assistant with logging parameters as shown in the UNIX example below:
./ua [-logLevel <log_level] [-logDir <log_directory>
]
TRACE
NOTIFICATION
WARNING
ERROR
INCIDENT_ERROR
NOTIFICATION
.When troubleshooting, consider setting the -logLevel
to TRACE
so that more information will be logged. If additional information is not needed, change the logLevel as the Upgrade Assistant's log files can become very large when -logLevel TRACE
is used.
Note:
If you have not created the Service Table schema, you might encounter the error messageUPGAST-00328 : The schema version registry table does not exist on this database. If that happens it is necessary to create the service table schema in order to run Upgrade Assistant.
If this occurs, you will need to create the required 12c schemas with the Repository Creation Utility (RCU).
Table 3-2 Upgrade Assistant Screens: Readiness Check
Screen | When Screen Appears | Description |
---|---|---|
Welcome |
Always. |
This screen provides an overview of the readiness check. |
Readiness Check Type:
|
Always. |
Readiness checks are only performed on schemas or component configurations that are at a supported upgrade starting point. There are two options to choose from. These options are described below:
|
Available Components |
When Individually Selected Schemas option is selected. |
This screen lists the available components for which the schemas will be selected. If you select something here, readiness check will be performed on that component's schema. |
All Schemas Component List |
Any time a schema readiness check is done. |
This screen is shown any time a schema readiness check is done. This could be when you select Individually Selected Schemas or Domain Based with the Include checks for all schemas option. |
Schema Credentials |
Always. |
Use this screen to enter information required to connect to the selected schema and the database that hosts the schema. If the schema that is to be upgraded was created by RCU in a prior Fusion Middleware release then you will see a drop-down menu listing the possible schema names. DBA User Name: Oracle recommends that you run the Upgrade Assistant as FMW and not SYSDBA. If you have not yet created the FMW user, see Creating a Non-SYSDBA User to Run Upgrade Assistant |
Readiness Summary |
Always. |
This screen provides a high-level overview of the readiness checks to be performed based on your selections. Click Save Response File if you plan to run the Upgrade Assistant again in |
Readiness Check |
Always. |
This screen displays the current status of the readiness check. Depending on what you have selected to check, the process can take several minutes. For a detailed report, click View Readiness Report. This button appears only after all the readiness checks are complete. Caution: To prevent performance degradation, consider running the readiness check during off-peak hours. |
Readiness Success |
If the readiness check completes successfully. |
You can now review the complete report. If the readiness check encounters an issue or error, review the log file to identify the issues, correct the issues, and then restart the readiness check. By default, the Readiness Check Report file is located in the following Oracle 12c directory:
|
The Upgrade Assistant allows you to upgrade individually selected schemas or all schemas associated with a domain. The option you select determines which Upgrade Assistant screens you will use.
To launch the Upgrade Assistant:
Screen | Description |
---|---|
Upgrade Options |
When upgrading schemas, you can select Individually Selected Schemas or All Schemas Used by a Domain. Select Individually Selected Schemas only when the domain uses schemas that cannot be upgraded to this version of Fusion Middleware or schemas that you do not want to upgrade at this time. |
Component List |
UA automatically detects the products installed in the domain directory. The Component List varies depending on what you currently have deployed in your domain. |
Prerequisites |
You must read and select each option before you continue. Note that Upgrade Assistant does not validate that they prerequisites have been met. |
Schema Credentials |
Provide the connection details for the schema. Be sure to use the correct schema prefix for the schemas you are upgrading. |
Examine |
The Examine phase scans the component versions to determine if an upgrade is needed. |
Upgrade Summary |
Review the summary and then click Upgrade to begin the actual upgrade process. |
Upgrade Progress |
Monitor the upgrade progress from this screen. |
End of Upgrade |
This screen returns the upgrade status: Success or Failure. Review the log report if the upgrade fails for any reason. |
Note:
Do not start the domain reconfiguration process until you have created all of the required schemas. See Creating Schemas for WebCenter 12c
Start the Reconfiguration Wizard in graphical mode by doing the following:
Reconfiguration Screens:
Screen | Description | Screen |
---|---|---|
Select Domain |
Provide the location of the domain to be reconfigured. |
|
Reconfiguration Setup Progress |
During the reconfiguration setup process, the WebLogic Server core infrastructure is reconfigured for 12c, templates are applied, and views are created and validated. |
|
Domain Mode and JDK |
The JDK and other information can be provided on this screen (if not auto-populated with the JDK you want to use). |
|
Database Configuration Type |
Use this screen to provide the 11g database details for the prefix_MDS schema, 12c database details to load the new prefix_STB schema, and to ensure prefix_OCS and prefix_MDS schemas are pointing to the 11g environment. |
|
JDBC Component Schema |
Once you provide the correct STB schema credentials and 11g schema owners, the information should auto-populate. Individual schema passwords must be updated in the auto-populated screen. |
|
JDBC Component Schema Test |
The Reconfiguration Wizard uses the information you provide to conduct a test connection. |
|
Node Manager |
Even though there was no node manager configuration in 11g, it must be configured for 12c. Provide the required details as shown below: |
|
Reconfiguration Progress |
Monitor the progress and status of the domain reconfiguration. |
Note:
Do not perform this step if you are upgrading Oracle WebCenter Content as the necessary configuration changes are performed automatically at server startup (post upgrade) without user intervention.If you already upgraded schemas, you will run the Upgrade Assistant again to upgrade the component configurations. Navigate to the 12c Upgrade Assistant.
On UNIX operating systems:
./ua
On Windows operating systems:
ua.bat
Provide the required information in each of the Upgrade Assistant screens. The screens you see will vary depending on the upgrade options you select.
Screen | Description |
---|---|
All Configurations |
Use this screen to provide the location of the 11g domain so that the Upgrade Assistant can update the location of WebCenter binaries in the 11g domain. This enables the Administration server to pick up the 12c binaries when it is started. Provide the location of the 11g domain. |
Component List |
The Upgrade Assistant scans the domain and identifies the components that will be upgraded. |
Examine |
Reviews the components in the domain and determines if an upgrade is necessary. |
Upgrade Summary |
Review the information and click Upgrade. |
Upgrade Success |
The 11g domain configurations are now upgraded for 12c. |
You may have to perform additional configuration tasks after an upgrade depending on which components are in your deployment.
Note:
You may have additional post-upgrade tasks if your deployment contains the following:
You can start and stop the Oracle WebLogic Server Administration Server using the WLST command line or a script. When you start or stop the Administration Server, you also start or stop the processes running in the Administration Server, including the WebLogic Server Administration Console and Fusion Middleware Control.
For example, to start an Administration Server, use the following script:
DOMAIN_HOME/bin/startWebLogic.sh
To stop an Administration Server, use the following script:
DOMAIN_HOME/bin/stopWebLogic.sh username password [admin_url]
You can start Node Manager using the WLST command line or a script.
To start Node Manager, use the following script:
(UNIX) DOMAIN_HOME/bin/startNodeManager.sh (Windows) DOMAIN_HOME\bin\startNodeManager.cmd
To stop Node Manager, close the command shell in which it is running.
To start or stop a WebLogic Server Managed Server using Fusion Middleware Control:
From the navigation pane, expand the domain.
Select the Managed Server.
From the WebLogic Server menu, choose Control, then Start Up or Shut Down.
Alternatively, you can right-click the server, then choose Control, then Start Up or Shut Down.
You can use a script or WLST to start and stop a WebLogic Server Managed Server.
For example, to start a WebLogic Server Managed Server, use the following script:
(UNIX) DOMAIN_HOME/bin/startManagedWebLogic.sh managed_server_name admin_url (Windows) DOMAIN_HOME\bin\startManagedWebLogic.cmd managed_server_name admin_url
When prompted, enter your user name and password.
To stop a WebLogic Server Managed Server, use the following script:
(UNIX) DOMAIN_HOME/bin/stopManagedWebLogic.sh managed_server_name admin_url username password (Windows) DOMAIN_HOME\bin\stopManagedWebLogic.cmd managed_server_name admin_url username password
Once all of the servers have been successfully started and stopped, open your component applications and make sure that everything is working as expected. Use your component-specific Administration and Developers guides to help you navigate the new features of your upgraded environment.