1. Upgrading Oracle WebCenter
  2. Upgrading Oracle WebCenter from a Previous 12c Release
  3. Upgrading WebCenter Sites from a Previous 12c Release

9 Upgrading WebCenter Sites from a Previous 12c Release

Use this procedure to upgrade WebCenter Sites from 12c (12.2.1.2 or 12.2.1.3) to 12c (12.2.1.4).

Note:

  • Any changes that you have made to the pre-upgrade environment are overwritten during the upgrade process. Oracle recommends that you save your customized files to a shared library location so that you can continue to use them after the upgrade.

  • If the existing Sites environment is configured with NIO-based Shared File System to a database, revert it back to disk storage before starting the upgrade process.

For information about the differences between in-place and out-of-place upgrades, see About In-Place versus Out-of-Place Upgrades in Oracle Fusion Middleware Planning an Upgrade of Oracle Fusion Middleware.

Note:

There are two approaches that you can consider while upgrading depending on your requirement:

  1. You can upgrade the delivery environment and clone it after the upgrade to create development and management environments.

    If you consider this approach, synchronization is required. You must publish the contents from your development and management environments in to the delivery environment before the upgrade. You can then clone your upgraded delivery environment to create development and management environments.

  2. Alternatively, you can upgrade each environment individually.

    If you consider this approach, synchronization is not required.

Follow the steps in the following topics to perform the upgrade:

  • About the WebCenter Sites Upgrade Process from a Previous 12c Release
    Review the flowchart and roadmap for an overview of the upgrade process for WebCenter Sites.
  • Installing the Product Distribution
    Before beginning your upgrade, download the 12c (12.2.1.4.0) Oracle Fusion Middleware Infrastructure and Oracle WebCenter Sites distributions on the target system and install them using Oracle Universal Installer.
  • If you have installed Sites with Insights...
    Oracle WebCenter Sites Insights is deprecated since 12.2.1.1. As a result, the reconfiguration template is not available during upgrade. You must perform the steps mentioned in this topic if your existing deployment contains Sites Insights.
  • Running a Pre-Upgrade Readiness Check
    To identify potential issues with the upgrade, Oracle recommends that you run a readiness check before you start the upgrade process. Be aware that the readiness check may not be able to discover all potential issues with your upgrade. An upgrade may still fail, even if the readiness check reports success.
  • Stopping Servers and Processes
    Before you run the Upgrade Assistant to upgrade your schemas and configurations, you must shut down all of the pre-upgrade processes and servers, including the Administration Server and any managed servers.
  • Before Running the Upgrade Assistant
    Before running the Upgrade Assistant to upgrade your 12.2.1.x domain, complete the tasks listed in this topic.
  • Checklist Before Performing Schema Upgrade
  • Upgrading Product Schemas
    After stopping servers and processes, use the Upgrade Assistant to upgrade supported product schemas to the current release of Oracle Fusion Middleware.
  • About Reconfiguring the Domain
    Run the Reconfiguration Wizard to reconfigure your domain component configurations to 12c (12.2.1.4.0).
  • Upgrading Domain Component Configurations
    After reconfiguring the domain, use the Upgrade Assistant to upgrade the domain component configurations inside the domain to match the updated domain configuration.
  • Starting Servers and Processes
    After a successful upgrade, restart all processes and servers, including the Administration Server and any Managed Servers.
  • Post-Upgrade Validation Tasks
    Oracle has provided validation scripts that you can run on your newly upgraded domain to ensure data integrity after a successful schema and configuration upgrade. You can review the validation summary report for any inconsistencies in data that may have occurred during the schema and configuration upgrade processes.
  • Post-Upgrade Tasks
    The post-upgrade tasks include restoring any custom settings, starting Administration Server and Managed Servers, reconfiguring passwords, and other administrative tasks listed in this topic.
  • Migrating Custom Java Libraries or Static Web Resources
    Perform this optional step only if custom Java libraries or static web resources were added to the web application in your pre-upgrade environment and you want to continue to use them in the upgraded environment.

Parent topic: Upgrading Oracle WebCenter from a Previous 12c Release

About the WebCenter Sites Upgrade Process from a Previous 12c Release

Review the flowchart and roadmap for an overview of the upgrade process for WebCenter Sites.

Figure 9-1 Upgrade Process Flowchart for WebCenter Sites from a Previous 12c Release

Description of Figure 9-1 follows
Description of "Figure 9-1 Upgrade Process Flowchart for WebCenter Sites from a Previous 12c Release"

Table 9-1 provides a roadmap for tasks that you must perform to upgrade WebCenter Sites from a previous 12c release.

Table 9-1 Tasks for Upgrading WebCenter Sites from a Previous 12c Release

Task Description

Required

If you have not done so already, review the introductory topics in this guide and complete the required pre-upgrade tasks.

The pre-upgrade tasks include cloning your production environment, verifying system requirements and certifications, purging unused data, and creating non-SYSDBA user.

For a complete list of pre-upgrade tasks, see Pre-Upgrade Tasks for Oracle WebCenter Components.

Important:

You must back up the WebLogic domain, Sites configuration directory, Sites shared directory, and Sites schema before starting the upgrade process.

Required

Download and install the 12c (12.2.1.4.0) Oracle Fusion Middleware Infrastructure and Oracle WebCenter Sites distributions.

The Infrastructure distribution packs the WebLogic Server and the Java Required Files (JRF) that are required to set up the foundation to install other Fusion Middleware products.

As per the upgrade topology defined in this guide, you must install the Infrastructure in a new Oracle home.

You must install the Oracle WebCenter Sites distribution in the Oracle home that is created when you install the 12.2.1.4.0 Infrastructure. To install the product distributions, follow the procedure described in Installing the Product Distribution.

Required if you have installed WebCenter Sites with Insights

Remove the extension template and install component references to Insights and app server insights_server1 and its dependencies.

Oracle WebCenter Sites Insights is deprecated since 12.2.1.1. As a result, the reconfiguration template is not available during upgrade. You must perform the steps mentioned in the following topic if your existing deployment contains Sites Insights: If you have installed Sites with Insights....

Optional

Run a pre-upgrade readiness check.

See Running a Pre-Upgrade Readiness Check.

Required

Shut down the existing environment (stop all Administration and Managed Servers).

WARNING:

Failure to shut down your servers during an upgrade may lead to data corruption.

See Stopping Servers and Processes.

Required

Complete the required tasks before running the Upgrade Assistant.

The pre-upgrade tasks are a set of tasks that you must complete before starting the upgrade process with the Upgrade Assistant.

These tasks are listed in Before Running the Upgrade Assistant.

Required

Upgrade the product schemas with the Upgrade Assistant.

Upgrade the schemas components that are available for upgrade with the Upgrade Assistant by following the procedure described in Upgrading Product Schemas.

Required

Reconfigure the existing 12c domain.

When you run the Reconfiguration Wizard on your existing domain, it prepares your domain for upgrade by selecting and applying the reconfiguration templates.

Reconfigure the domain by following the procedure described in About Reconfiguring the Domain.

Required

Upgrade the domain configuration.

Upgrade all the configurations contained in your 12.2.1.0 domain with the Upgrade Assistant by following the procedure described in Upgrading Domain Component Configurations.

Required

Complete the post-upgrade validation tasks.

Oracle has provided validation scripts that you can run on your newly upgraded domain to ensure data integrity after a successful schema and configuration upgrade. You can review the validation summary report for any inconsistencies in data that may have occurred during the schema and configuration upgrade processes.

To use the validation script, see Post-Upgrade Validation Tasks.

Required

Complete the other post-upgrade tasks.

Other post-upgrade tasks include restoring any custom settings, starting Administration Server and Managed Servers, reconfiguring passwords, and other administrative tasks listed in Post-Upgrade Tasks.

Required

Restart the servers and processes.

See Starting Servers and Processes.

Parent topic: Upgrading WebCenter Sites from a Previous 12c Release

Installing the Product Distribution

Before beginning your upgrade, download the 12c (12.2.1.4.0) Oracle Fusion Middleware Infrastructure and Oracle WebCenter Sites distributions on the target system and install them using Oracle Universal Installer.

Note:

When Infrastructure is required for the upgrade, you must install the Oracle Fusion Middleware distribution first before you install other Fusion Middleware products.

Ensure that you download and install all the Oracle products that are part of your domain, for example Oracle HTTP Server. You must install the 12.2.1.4.0 binaries into a new Oracle home. It should be on the same host as the existing Oracle home.

To install the 12c (12.2.1.4.0) distributions:
  1. Sign in to the target system.
  2. Download the following from Oracle Technology Network or Oracle Software Delivery Cloud to your target system:
    • Oracle Fusion Middleware Infrastructure (fmw_12.2.1.4.0_infrastructure_generic.jar)
    • Oracle WebCenter Sites (fmw_12.2.1.4.0_wcsites_generic.jar)
  3. Change to the directory where you downloaded the 12c (12.2.1.4.0) product distribution.
  4. Start the installation program for Oracle Fusion Middleware Infrastructure:
    • (UNIX) JDK_HOME/bin/java -jar fmw_12.2.1.4.0_infrastructure.jar
    • (Windows) JDK_HOME\bin\java -jar fmw_12.2.1.4.0_infrastructure.jar
  5. On UNIX operating systems, the Installation Inventory Setup screen appears if this is the first time you are installing an Oracle product on this host.
    Specify the location where you want to create your central inventory. Make sure that the operating system group name selected on this screen has write permissions to the central inventory location, and click Next.

    Note:

    The Installation Inventory Setup screen does not appear on Windows operating systems.
  6. On the Welcome screen, review the information to make sure that you have met all the prerequisites. Click Next.
  7. On the Auto Updates screen, select an option:

    • Skip Auto Updates: If you do not want your system to check for software updates at this time.

    • Select patches from directory: To navigate to a local directory if you downloaded patch files.

    • Search My Oracle Support for Updates: To automatically download software updates if you have a My Oracle Support account. You must enter Oracle Support credentials then click Search. To configure a proxy server for the installer to access My Oracle Support, click Proxy Settings. Click Test Connection to test the connection.

    Click Next.
  8. On the Installation Location screen, specify the location for the Oracle home directory and click Next.
    For more information about Oracle Fusion Middleware directory structure, see Understanding Directories for Installation and Configuration in Oracle Fusion Middleware Planning an Installation of Oracle Fusion Middleware.
  9. On the Installation Type screen, select the following:
    • For Infrastructure, select Fusion Middleware Infrastructure
    • For Oracle WebCenter Sites, select WebCenter Sites

      Note:

      If you have installed Oracle WebCenter Sites with Examples on the source environment, ensure that you select WebCenter Sites with Examples on the target as well.

    Click Next.
  10. The Prerequisite Checks screen analyzes the host computer to ensure that the specific operating system prerequisites have been met.
    To view the list of tasks that are verified, select View Successful Tasks. To view log details, select View Log. If any prerequisite check fails, then an error message appears at the bottom of the screen. Fix the error and click Rerun to try again. To ignore the error or the warning message and continue with the installation, click Skip (not recommended).
  11. On the Installation Summary screen, verify the installation options that you selected.
    If you want to save these options to a response file, click Save Response File and enter the response file location and name. The response file collects and stores all the information that you have entered, and enables you to perform a silent installation (from the command line) at a later time.

    Click Install to begin the installation.

  12. On the Installation Progress screen, when the progress bar displays 100%, click Finish to dismiss the installer, or click Next to see a summary.
  13. The Installation Complete screen displays the Installation Location and the Feature Sets that are installed. Review this information and click Finish to close the installer.
  14. After you have installed Oracle Fusion Middleware Infrastructure, enter the following command to start the installer for your product distribution and repeat the steps above to navigate through the installer screens:
    (UNIX) JDK_HOME/bin/java -jar fmw_12.2.1.4.0_wcsites_generic.jar
    (Windows) JDK_HOME\bin\java -jar fmw_12.2.1.4.0_wcsites_generic.jar

Parent topic: Upgrading WebCenter Sites from a Previous 12c Release

If you have installed Sites with Insights...

Oracle WebCenter Sites Insights is deprecated since 12.2.1.1. As a result, the reconfiguration template is not available during upgrade. You must perform the steps mentioned in this topic if your existing deployment contains Sites Insights.

Note:

Perform this procedure only if you are upgrading from 12.2.1.0 and you have installed Oracle WebCenter Sites with Insights.
Complete the following steps before running the pre-upgrade Readiness Check or before running the Reconfiguration Wizard:
  1. Sign in to the host where you have installed Insights. Take a complete backup of your existing domain.
  2. Remove extension template reference to Insights from the domain-info.xml file.
    1. Change to the following directory:
      (UNIX) EXISTING_ORACLE_HOME/user_projects/domains/DOMAIN_NAME/init-info/domain-info.xml
      (Windows) EXISTING_ORACLE_HOME\user_projects\domains\DOMAIN_NAME\init-info\domain-info.xml
    2. Open the domain-info.xml file for editing.
    3. Remove the <extention-template-ref> with name "Oracle WebCenter Sites - Insights".
    4. Save and close the file.
  3. Remove the install component reference to Insights from the domain-info.xml file.
    1. Change to the following directory:
      (UNIX) EXISTING_ORACLE_HOME/user_projects/domains/DOMAIN_NAME/init-info/domain-info.xml
      (Windows) EXISTING_ORACLE_HOME\user_projects\domains\DOMAIN_NAME\init-info\domain-info.xml
    2. Open the domain-info.xml file for editing.
    3. Remove the <install-comp-ref> with name="oracle.wcsites.insights".
    4. Save and close the file.
  4. Remove app server insights_server1 and its dependencies from the config.xml file.
    1. Change to the following directory:
      (UNIX) EXISTING_ORACLE_HOME/user_projects/domains/DOMAIN_NAME/config/config.xml
      (Windows) EXISTING_ORACLE_HOME\user_projects\domains\DOMAIN_NAME\config\config.xml
    2. Open the config.xml file for editing.
    3. Remove the app server insights_server1 and its dependencies.
    4. Save and close the file.

Parent topic: Upgrading WebCenter Sites from a Previous 12c Release

Running a Pre-Upgrade Readiness Check

To identify potential issues with the upgrade, Oracle recommends that you run a readiness check before you start the upgrade process. Be aware that the readiness check may not be able to discover all potential issues with your upgrade. An upgrade may still fail, even if the readiness check reports success.

Parent topic: Upgrading WebCenter Sites from a Previous 12c Release

About Running a Pre-Upgrade Readiness Check

You can run the Upgrade Assistant in -readiness mode to detect issues before you perform the actual upgrade. You can run the readiness check in GUI mode using the Upgrade Assistant or in silent mode using a response file.

The Upgrade Assistant readiness check performs a read-only, pre-upgrade review of your Fusion Middleware schemas and WebLogic domain configurations that are at a supported starting point. The review is a read-only operation.

The readiness check generates a formatted, time-stamped readiness report so you can address potential issues before you attempt the actual upgrade. If no issues are detected, you can begin the upgrade process. Oracle recommends that you read this report thoroughly before performing an upgrade.

You can run the readiness check while your existing Oracle Fusion Middleware domain is online (while other users are actively using it) or offline.

You can run the readiness check any number of times before performing any actual upgrade. However, do not run the readiness check after an upgrade has been performed, as the report results may differ from the result of pre-upgrade readiness checks.

Note:

To prevent performance from being affected, Oracle recommends that you run the readiness check during off-peak hours.

Parent topic: Running a Pre-Upgrade Readiness Check

Starting the Upgrade Assistant in Readiness Mode

Use the -readiness parameter to start the Upgrade Assistant in readiness mode.

To perform a readiness check on your pre-upgrade environment with the Upgrade Assistant:
  1. Go to the oracle_common/upgrade/bin directory:
    • (UNIX) ORACLE_HOME/oracle_common/upgrade/bin
    • (Windows) ORACLE_HOME\oracle_common\upgrade\bin
  2. Start the Upgrade Assistant.
    • (UNIX) ./ua -readiness
    • (Windows) ua.bat -readiness

    Note:

    If the DISPLAY environment variable is not set up properly to allow for GUI mode, you may encounter the following error:
    Xlib: connection to ":1.0" refused by server
Xlib: No protocol specified

    To resolve this issue, set the DISPLAY environment variable to the system name or IP address of your local workstation, and rerun Upgrade Assistant.

    If you continue to receive these errors after setting DISPLAY, try launching another GUI tool, such as vncconfig. If you see the same errors, your DISPLAY environment variable may still not be set correctly.

    For information about other parameters that you can specify on the command line, see:

Parent topic: Running a Pre-Upgrade Readiness Check

Upgrade Assistant Parameters

When you start the Upgrade Assistant from the command line, you can specify additional parameters.

Table 9-2 Upgrade Assistant Command-Line Parameters

Parameter Required or Optional Description

-readiness

 Required for readiness checks

Note: Readiness checks cannot be performed on standalone installations (those not managed by the WebLogic Server).

Performs the upgrade readiness check without performing an actual upgrade.

Schemas and configurations are checked.

Do not use this parameter if you have specified the -examine parameter.

-threads

Optional

Identifies the number of threads available for concurrent schema upgrades or readiness checks of the schemas.

The value must be a positive integer in the range 1 to 8. The default is 4.

-response

Required for silent upgrades or silent readiness checks

Runs the Upgrade Assistant using inputs saved to a response file generated from the data that is entered when the Upgrade Assistant is run in GUI mode. Using this parameter runs the Upgrade Assistant in silent mode (without displaying Upgrade Assistant screens).

-examine

Optional

Performs the examine phase but does not perform an actual upgrade.

Do not specify this parameter if you have specified the -readiness parameter.

-logLevel attribute

Optional

Sets the logging level, specifying one of the following attributes:

  • TRACE

  • NOTIFICATION

  • WARNING

  • ERROR

  • INCIDENT_ERROR

The default logging level is NOTIFICATION.

Consider setting the -logLevel TRACE attribute to so that more information is logged. This is useful when troubleshooting a failed upgrade. The Upgrade Assistant's log files can become very large if -logLevel TRACE is used.

-logDir location

Optional

Sets the default location of upgrade log files and temporary files. You must specify an existing, writable directory where the Upgrade Assistant creates log files and temporary files.

The default locations are:

(UNIX)

ORACLE_HOME/oracle_common/upgrade/logs
ORACLE_HOME/oracle_common/upgrade/temp

(Windows)

ORACLE_HOME\oracle_common\upgrade\logs
ORACLE_HOME\oracle_common\upgrade\temp

-help

Optional

Displays all of the command-line options.

Performing a Readiness Check with the Upgrade Assistant

Navigate through the screens in the Upgrade Assistant to complete the pre-upgrade readiness check.

Readiness checks are performed only on schemas or component configurations that are at a supported upgrade starting point.
To complete the readiness check:
  1. On the Welcome screen, review information about the readiness check. Click Next.
  2. On the Readiness Check Type screen, select the readiness check that you want to perform:
    • Individually Selected Schemas allows you to select individual schemas for review before upgrade. The readiness check reports whether a schema is supported for an upgrade or where an upgrade is needed.

      When you select this option, the screen name changes to Selected Schemas.

    • Domain Based allows the Upgrade Assistant to discover and select all upgrade-eligible schemas or component configurations in the domain specified in the Domain Directory field.

      When you select this option, the screen name changes to Schemas and Configuration.

      Leave the default selection if you want the Upgrade Assistant to check all schemas and component configurations at the same time, or select a specific option:

      • Include checks for all schemas to discover and review all components that have a schema available to upgrade.

      • Include checks for all configurations to review component configurations for a managed WebLogic Server domain.

    Click Next.

  3. If you selected Individually Selected Schemas: On the Available Components screen, select the components that have a schema available to upgrade for which you want to perform a readiness check.
    If you selected Domain Based: On the Component List screen, review the list of components that are present in your domain for which you want to perform a readiness check.
    If you select a component that has dependent components, those components are automatically selected. For example, if you select Oracle Platform Security Services, Oracle Audit Services is automatically selected.

    Depending on the components you select, additional screens may display. For example, you may need to:

    • Specify the domain directory.

    • Specify schema credentials to connect to the selected schema: Database Type, DBA User Name, and DBA Password. Then click Connect.

      Note:

      Oracle database is the default database type. Make sure that you select the correct database type before you continue. If you discover that you selected the wrong database type, do not go back to this screen to change it to the correct type. Instead, close the Upgrade Assistant and restart the readiness check with the correct database type selected to ensure that the correct database type is applied to all schemas.

    • Select the Schema User Name option and specify the Schema Password.

      Note:

      The Upgrade Assistant automatically enables default credentials. If you are unable to connect, make sure that you manually enter the credentials for your schema before you continue.
    Click Next to start the readiness check.
  4. On the Readiness Summary screen, review the summary of the readiness checks that will be performed based on your selections.
    If you want to save your selections to a response file to run the Upgrade Assistant again later in response (or silent) mode, click Save Response File and provide the location and name of the response file. A silent upgrade performs exactly the same function that the Upgrade Assistant performs, but you do not have to manually enter the data again.
    For a detailed report, click View Log.
    Click Next.
  5. On the Readiness Check screen, review the status of the readiness check. The process can take several minutes.
    If you are checking multiple components, the progress of each component displays in its own progress bar in parallel.
    When the readiness check is complete, click Continue.
  6. On the End of Readiness screen, review the results of the readiness check (Readiness Success or Readiness Failure):

    • If the readiness check is successful, click View Readiness Report to review the complete report. Oracle recommends that you review the Readiness Report before you perform the actual upgrade even when the readiness check is successful. Use the Find option to search for a particular word or phrase within the report. The report also indicates where the completed Readiness Check Report file is located.

    • If the readiness check encounters an issue or error, click View Log to review the log file, identify and correct the issues, and then restart the readiness check. The log file is managed by the command-line options you set.

Parent topic: Running a Pre-Upgrade Readiness Check

Understanding the Readiness Report

After performing a readiness check for your domain, review the report to determine whether you need to take any action for a successful upgrade.

The format of the readiness report file is:

readiness<timestamp>.txt

Where, timestamp indicates the date and time of when the readiness check was run.

A readiness report contains the following information:

Table 9-3 Readiness Report Elements

Report Information Description Required Action
Overall Readiness Status: SUCCESS or FAILURE The top of the report indicates whether the readiness check passed or completed with one or more errors. If the report completed with one or more errors, search for FAIL and correct the failing issues before attempting to upgrade. You can re-run the readiness check as many times as necessary before an upgrade.

Timestamp

The date and time that the report was generated.

No action required.

Log file location

/oracle_common/upgrade/logs

The directory location of the generated log file.

No action required.
Domain Directory Displays the domain location No action required.

Readiness report location

/oracle_common/upgrade/logs

The directory location of the generated readiness report.

No action required.

Names of components that were checked

The names and versions of the components included in the check and status.

If your domain includes components that cannot be upgraded to this release, such as SOA Core Extension, do not attempt an upgrade.

Names of schemas that were checked

The names and current versions of the schemas included in the check and status.

Review the version numbers of your schemas. If your domain includes schemas that cannot be upgraded to this release, do not attempt an upgrade.

Individual Object Test Status: FAIL

The readiness check test detected an issue with a specific object.

Do not upgrade until all failed issues have been resolved.

Individual Object Test Status: PASS

The readiness check test detected no issues for the specific object.

If your readiness check report shows only the PASS status, you can upgrade your environment. Note, however, that the Readiness Check cannot detect issues with externals such as hardware or connectivity during an upgrade. You should always monitor the progress of your upgrade.

Completed Readiness Check of <Object> Status: FAILURE The readiness check detected one or more errors that must be resolved for a particular object such as a schema, an index, or datatype. Do not upgrade until all failed issues have been resolved.
Completed Readiness Check of <Object> Status: SUCCESS The readiness check test detected no issues. No action required.

Here is a sample Readiness Report file. Your report may not include all of these checks. 

Upgrade readiness check completed with one or more errors.

This readiness check report was created on Fri Aug 16 13:29:41 PDT 2019
Log file is located at: /oracle/work/middleware_latest/oracle_common/upgrade/logs/ua2019-08-16-13-23-36PM.log
Readiness Check Report File: /oracle/work/middleware_latest/oracle_common/upgrade/logs/readiness2019-08-16-13-29-41PM.txt
Domain Directory: /oracle/work/middleware_1212/user_projects/domains/jrf_domain

Starting readiness check of components.

Oracle Platform Security Services
   Starting readiness check of Oracle Platform Security Services.
     Schema User Name: DEV3_OPSS
     Database Type: Oracle Database
     Database Connect String: 
     VERSION Schema DEV3_OPSS is currently at version 12.1.2.0.0.  Readiness checks will now be performed.
   Starting schema test:  TEST_DATABASE_VERSION  Test that the database server version number is supported for upgrade
     INFO   Database product version: Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production
With the Partitioning, OLAP, Advanced Analytics and Real Application Testing options
   Completed schema test: TEST_DATABASE_VERSION --> Test that the database server version number is supported for upgrade +++ PASS
   Starting schema test:  TEST_REQUIRED_TABLES  Test that the schema contains all the required tables
   Completed schema test: TEST_REQUIRED_TABLES --> Test that the schema contains all the required tables +++ PASS
   Starting schema test:  Test that the schema does not contain any unexpected tables  TEST_UNEXPECTED_TABLES
   Completed schema test: Test that the schema does not contain any unexpected tables --> TEST_UNEXPECTED_TABLES +++ Test that the schema does not contain any unexpected tables
   Starting schema test:  TEST_ENOUGH_TABLESPACE  Test that the schema tablespaces automatically extend if full
   Completed schema test: TEST_ENOUGH_TABLESPACE --> Test that the schema tablespaces automatically extend if full +++ PASS
   Starting schema test:  TEST_USER_TABLESPACE_QUOTA  Test that tablespace quota for this user is sufficient to perform the upgrade
   Completed schema test: TEST_USER_TABLESPACE_QUOTA --> Test that tablespace quota for this user is sufficient to perform the upgrade +++ PASS
   Starting schema test:  TEST_ONLINE_TABLESPACE  Test that schema tablespaces are online
   Completed schema test: TEST_ONLINE_TABLESPACE --> Test that schema tablespaces are online +++ PASS
   Starting permissions test:  TEST_DBA_TABLE_GRANTS  Test that DBA user has privilege to view all user tables
   Completed permissions test: TEST_DBA_TABLE_GRANTS --> Test that DBA user has privilege to view all user tables +++ PASS
   Starting schema test:  SEQUENCE_TEST  Test that the Oracle Platform Security Services schema sequence and its properties are valid
   Completed schema test: SEQUENCE_TEST --> Test that the Oracle Platform Security Services schema sequence and its properties are valid +++ PASS
   Finished readiness check of Oracle Platform Security Services with status: SUCCESS.

Oracle Audit Services
   Starting readiness check of Oracle Audit Services.
     Schema User Name: DEV3_IAU
     Database Type: Oracle Database
     Database Connect String: 
     VERSION Schema DEV3_IAU is currently at version 12.1.2.0.0.  Readiness checks will now be performed.
   Starting schema test:  TEST_DATABASE_VERSION  Test that the database server version number is supported for upgrade
     INFO   Database product version: Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production
With the Partitioning, OLAP, Advanced Analytics and Real Application Testing options
   Completed schema test: TEST_DATABASE_VERSION --> Test that the database server version number is supported for upgrade +++ PASS
   Starting schema test:  TEST_REQUIRED_TABLES  Test that the schema contains all the required tables
   Completed schema test: TEST_REQUIRED_TABLES --> Test that the schema contains all the required tables +++ PASS
   Starting schema test:  TEST_UNEXPECTED_TABLES  Test that the schema does not contain any unexpected tables
   Completed schema test: TEST_UNEXPECTED_TABLES --> Test that the schema does not contain any unexpected tables +++ PASS
   Starting schema test:  TEST_ENOUGH_TABLESPACE  Test that the schema tablespaces automatically extend if full
   Completed schema test: TEST_ENOUGH_TABLESPACE --> Test that the schema tablespaces automatically extend if full +++ PASS
   Starting schema test:  TEST_USER_TABLESPACE_QUOTA  Test that tablespace quota for this user is sufficient to perform the upgrade
   Completed schema test: TEST_USER_TABLESPACE_QUOTA --> Test that tablespace quota for this user is sufficient to perform the upgrade +++ PASS
   Starting schema test:  TEST_ONLINE_TABLESPACE  Test that schema tablespaces are online
   Completed schema test: TEST_ONLINE_TABLESPACE --> Test that schema tablespaces are online +++ PASS
   Starting permissions test:  TEST_DBA_TABLE_GRANTS  Test that DBA user has privilege to view all user tables
   Completed permissions test: TEST_DBA_TABLE_GRANTS --> Test that DBA user has privilege to view all user tables +++ PASS
   Starting schema test:  TEST_MISSING_COLUMNS  Test that tables and views are not missing any required columns
   Completed schema test: TEST_MISSING_COLUMNS --> Test that tables and views are not missing any required columns +++ PASS
   Starting schema test:  TEST_UNEXPECTED_COLUMNS  Test that tables and views do not contain any unexpected columns
   Completed schema test: TEST_UNEXPECTED_COLUMNS --> Test that tables and views do not contain any unexpected columns +++ PASS
   Starting datatype test for table OIDCOMPONENT:  TEST_COLUMN_DATATYPES_V2 --> Test that all table columns have the proper datatypes
   Completed datatype test for table OIDCOMPONENT: TEST_COLUMN_DATATYPES_V2 --> Test that all table columns have the proper datatypes +++ PASS
   Starting datatype test for table IAU_CUSTOM_01:  TEST_COLUMN_DATATYPES_V2 --> Test that all table columns have the proper datatypes
   Completed datatype test for table IAU_CUSTOM_01: TEST_COLUMN_DATATYPES_V2 --> Test that all table columns have the proper datatypes +++ PASS
   Starting datatype test for table IAU_BASE:  TEST_COLUMN_DATATYPES_V2 --> Test that all table columns have the proper datatypes
   Completed datatype test for table IAU_BASE: TEST_COLUMN_DATATYPES_V2 --> Test that all table columns have the proper datatypes +++ PASS
   Starting datatype test for table WS_POLICYATTACHMENT:  TEST_COLUMN_DATATYPES_V2 --> Test that all table columns have the proper datatypes
   Completed datatype test for table WS_POLICYATTACHMENT: TEST_COLUMN_DATATYPES_V2 --> Test that all table columns have the proper datatypes +++ PASS
   Starting datatype test for table OWSM_PM_EJB:  TEST_COLUMN_DATATYPES_V2 --> Test that all table columns have the proper datatypes
   Completed datatype test for table OWSM_PM_EJB: TEST_COLUMN_DATATYPES_V2 --> Test that all table columns have the proper datatypes +++ PASS
   Starting datatype test for table XMLPSERVER:  TEST_COLUMN_DATATYPES_V2 --> Test that all table columns have the proper datatypes
   Completed datatype test for table XMLPSERVER: TEST_COLUMN_DATATYPES_V2 --> Test that all table columns have the proper datatypes +++ PASS
   Starting datatype test for table SOA_HCFP:  TEST_COLUMN_DATATYPES_V2 --> Test that all table columns have the proper datatypes
   Completed datatype test for table SOA_HCFP: TEST_COLUMN_DATATYPES_V2 --> Test that all table columns have the proper datatypes +++ PASS
   Starting schema test:  SEQUENCE_TEST  Test that the audit schema sequence and its properties are valid
   Completed schema test: SEQUENCE_TEST --> Test that the audit schema sequence and its properties are valid +++ PASS
   Starting schema test:  SYNONYMS_TEST  Test that the audit schema required synonyms are present
   Completed schema test: SYNONYMS_TEST --> Test that the audit schema required synonyms are present +++ PASS
   Finished readiness check of Oracle Audit Services with status: FAILURE.

Common Infrastructure Services
   Starting readiness check of Common Infrastructure Services.
     Schema User Name: DEV3_STB
     Database Type: Oracle Database
     Database Connect String: 
   Starting schema test:  TEST_REQUIRED_TABLES  Test that the schema contains all the required tables
   Completed schema test: TEST_REQUIRED_TABLES --> Test that the schema contains all the required tables +++ PASS
   Completed schema test: ALL_TABLES --> TEST_REQUIRED_TABLES +++ Test that the schema contains all the required tables
   Starting schema test:  TEST_UNEXPECTED_TABLES  Test that the schema does not contain any unexpected tables
   Completed schema test: ALL_TABLES --> TEST_UNEXPECTED_TABLES +++ Test that the schema does not contain any unexpected tables
   Starting schema test:  TEST_REQUIRED_VIEWS  Test that the schema contains all the required database views
   Completed schema test: ALL_TABLES --> TEST_REQUIRED_VIEWS +++ Test that the schema contains all the required database views
   Starting schema test:  TEST_MISSING_COLUMNS  Test that tables and views are not missing any required columns
   Completed schema test: ALL_TABLES --> TEST_MISSING_COLUMNS +++ Test that tables and views are not missing any required columns
   Starting schema test:  TEST_DATABASE_VERSION  Test that the database server version number is supported for upgrade
   Starting schema test:  TEST_DATABASE_VERSION  Test that the database server version number is supported for upgrade
     INFO   Database product version: Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production
With the Partitioning, OLAP, Advanced Analytics and Real Application Testing options
   Completed schema test: TEST_DATABASE_VERSION --> Test that the database server version number is supported for upgrade +++ PASS
   Completed schema test: ALL_TABLES --> TEST_DATABASE_VERSION +++ Test that the database server version number is supported for upgrade
   Finished readiness check of Common Infrastructure Services with status: SUCCESS.

Oracle JRF
   Starting readiness check of Oracle JRF.
   Finished readiness check of Oracle JRF with status: SUCCESS.

System Components Infrastructure
   Starting readiness check of System Components Infrastructure.
   Starting config test:  TEST_SOURCE_CONFIG  Checking the source configuration.
     INFO /oracle/work/middleware_1212/user_projects/domains/jrf_domain/opmn/topology.xml was not found. No upgrade is needed.
   Completed config test: TEST_SOURCE_CONFIG --> Checking the source configuration. +++ PASS
   Finished readiness check of System Components Infrastructure with status: ALREADY_UPGRADED.

Common Infrastructure Services
   Starting readiness check of Common Infrastructure Services.
   Starting config test:  CIEConfigPlugin.readiness.test  This tests the readiness of the domain from CIE side.
   Completed config test: CIEConfigPlugin.readiness.test --> This tests the readiness of the domain from CIE side. +++ PASS
   Finished readiness check of Common Infrastructure Services with status: SUCCESS.

Finished readiness check of components.

Parent topic: Running a Pre-Upgrade Readiness Check

Stopping Servers and Processes

Before you run the Upgrade Assistant to upgrade your schemas and configurations, you must shut down all of the pre-upgrade processes and servers, including the Administration Server and any managed servers.

An Oracle Fusion Middleware environment can consist of an Oracle WebLogic Server domain, an Administration Server, multiple managed servers, Java components, system components such as Identity Management components, and a database used as a repository for metadata. The components may be dependent on each other, so they must be stopped in the correct order.

Note:

The procedures in this section describe how to stop the existing, pre-upgrade servers and processes using the WLST command-line utility or a script. You can also use the Oracle Fusion Middleware Control and the Oracle WebLogic Server Administration Console. See Starting and Stopping Administration and Managed Servers and Node Manager.

To stop your pre-upgrade Fusion Middleware environment, navigate to the pre-upgrade domain and follow the steps below:

Step 1: Stop the Managed Servers

To stop a WebLogic Server Managed Server, use the stopManagedWebLogic script:

  • (UNIX) DOMAIN_HOME/bin/stopManagedWebLogic.sh managed_server_name admin_url

  • (Windows) DOMAIN_HOME\bin\stopManagedWebLogic.cmd managed_server_name admin_url

When prompted, enter your user name and password.

Step 2: Stop System Components

To stop system components, such as Oracle HTTP Server, use the stopComponent script:

  • (UNIX) DOMAIN_HOME/bin/stopComponent.sh component_name

  • (Windows) DOMAIN_HOME\bin\stopComponent.cmd component_name

You can stop system components in any order.

Step 3: Stop the Administration Server

When you stop the Administration Server, you also stop the processes running in the Administration Server, including the WebLogic Server Administration Console and Fusion Middleware Control.

To stop the Administration Server, use the stopWebLogic script:

  • (UNIX) DOMAIN_HOME/bin/stopWebLogic.sh

  • (Windows) DOMAIN_HOME\bin\stopWebLogic.cmd

When prompted, enter your user name, password, and the URL of the Administration Server.

Step 4: Stop Node Manager

To stop Node Manager, close the command shell in which it is running.

Alternatively, after setting the nodemanager.properties attribute QuitEnabled to true (the default is false), you can use WLST to connect to Node Manager and shut it down. See stopNodeManager in Oracle Fusion Middleware WLST Command Reference for WebLogic Server.

Parent topic: Upgrading WebCenter Sites from a Previous 12c Release

Before Running the Upgrade Assistant

Before running the Upgrade Assistant to upgrade your 12.2.1.x domain, complete the tasks listed in this topic.

IBM DB2 Database Users Only:

There is no support for DB2 database in 12.2.1.4.0 WCSites release. Customers are advised to use one of the certified databases (Ex: MS-SQLServer or Oracle) with WebCenter Sites. Customers using IBM DB2 will have to move WebCenter Sites schema from DB2 to one of the certified databases using the tools that the latter may provide. This is a prerequisite before upgrading the product schemas.

Parent topic: Upgrading WebCenter Sites from a Previous 12c Release

Checklist Before Performing Schema Upgrade

The upgrade scripts add different tables for various releases. Ensure that you do not add tables with the same name as the tables present in your schema before the upgrade.

For example, if you are upgrading from 12.2.1.2.0 to 12.2.1.3.0, it is acceptable to have the EloquaForms table because it is introduced in 12.2.1.1.0. However, the CECSAudit table is not expected to be in your schema before the upgrade.

List of tables that were added in 12.2.1.1.0:

  • EloquaForm

  • EloquaInstallations

  • EloquaInstances

  • AVISPORTS Sample

  • FileResource

  • FileResource_Dim

  • FileResource_DimP

  • FileResource_Rtgs

List of tables that were added in 12.2.1.3.0:

  • ContentCloud

  • ContentCloudAudit

  • ContentCloudPubTargets

  • ContentCloud_Dim

  • ContentCloud_DimP

  • ContentCloud_Q

  • ContentCloud_Rtgs

  • WCS_ContentCloudSubtype

Oracle recommends that you remove or rename these tables from the Sites schema before you start the Upgrade Assistant.

Note:

This list of tables is applicable only when you are upgrading Oracle WebCenter Sites from 12c (12.2.1.2) or earlier.

Parent topic: Upgrading WebCenter Sites from a Previous 12c Release

Upgrading Product Schemas

After stopping servers and processes, use the Upgrade Assistant to upgrade supported product schemas to the current release of Oracle Fusion Middleware.

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.

Parent topic: Upgrading WebCenter Sites from a Previous 12c Release

Starting the Upgrade Assistant

Run the Upgrade Assistant to upgrade product schemas, domain component configurations, or standalone system components to 12c (12.2.1.4.0).

To start the Upgrade Assistant:

Note:

Before you start the Upgrade Assistant, make sure that the JVM character encoding is set to UTF-8 for the platform on which the Upgrade Assistant is running. If the character encoding is not set to UTF-8, then you will not be able to download files containing Unicode characters in their names. This can cause the upgrade to fail.

  1. Go to the oracle_common/upgrade/bin directory:
    • (UNIX) ORACLE_HOME/oracle_common/upgrade/bin
    • (Windows) ORACLE_HOME\oracle_common\upgrade\bin
  2. Start the Upgrade Assistant:
    • (UNIX) ./ua
    • (Windows) ua.bat

For information about other parameters that you can specify on the command line, such as logging parameters, see:

Parent topic: Upgrading Product Schemas

Upgrade Assistant Parameters

When you start the Upgrade Assistant from the command line, you can specify additional parameters.

Table 9-4 Upgrade Assistant Command-Line Parameters

Parameter Required or Optional Description

-readiness

 Required for readiness checks

Note: Readiness checks cannot be performed on standalone installations (those not managed by the WebLogic Server).

Performs the upgrade readiness check without performing an actual upgrade.

Schemas and configurations are checked.

Do not use this parameter if you have specified the -examine parameter.

-threads

Optional

Identifies the number of threads available for concurrent schema upgrades or readiness checks of the schemas.

The value must be a positive integer in the range 1 to 8. The default is 4.

-response

Required for silent upgrades or silent readiness checks

Runs the Upgrade Assistant using inputs saved to a response file generated from the data that is entered when the Upgrade Assistant is run in GUI mode. Using this parameter runs the Upgrade Assistant in silent mode (without displaying Upgrade Assistant screens).

-examine

Optional

Performs the examine phase but does not perform an actual upgrade.

Do not specify this parameter if you have specified the -readiness parameter.

-logLevel attribute

Optional

Sets the logging level, specifying one of the following attributes:

  • TRACE

  • NOTIFICATION

  • WARNING

  • ERROR

  • INCIDENT_ERROR

The default logging level is NOTIFICATION.

Consider setting the -logLevel TRACE attribute to so that more information is logged. This is useful when troubleshooting a failed upgrade. The Upgrade Assistant's log files can become very large if -logLevel TRACE is used.

-logDir location

Optional

Sets the default location of upgrade log files and temporary files. You must specify an existing, writable directory where the Upgrade Assistant creates log files and temporary files.

The default locations are:

(UNIX)

ORACLE_HOME/oracle_common/upgrade/logs
ORACLE_HOME/oracle_common/upgrade/temp

(Windows)

ORACLE_HOME\oracle_common\upgrade\logs
ORACLE_HOME\oracle_common\upgrade\temp

-help

Optional

Displays all of the command-line options.

Upgrading Product Schemas Using the Upgrade Assistant

Navigate through the screens in the Upgrade Assistant to upgrade the product schemas.

To upgrade product schemas with the Upgrade Assistant:
  1. On the Welcome screen, review an introduction to the Upgrade Assistant and information about important pre-upgrade tasks. Click Next.

    Note:

    For more information about any Upgrade Assistant screen, click Help on the screen.
  2. On the Selected Schemas screen, select Individually Selected Schemas or All Schemas Used by a Domain to upgrade the schemas for all the components that WebCenter Sites uses. Click Next.
    The Upgrade Assistant identifies the components that are available for a schema upgrade. The components used by WebCenter Sites are:

    • Oracle Audit Services

    • Oracle Platform Security Services

    • Common Infrastructure Services

    • Oracle WebLogicServer

    • Oracle WebCenter Sites

  3. If you selected Individually Selected Schemas: On the Available Components screen, select Oracle WebCenter Sites and other components, as listed in step 2. Click Next. When you select a component, the schemas and any dependencies are automatically selected.
  4. On the Prerequisites screen, acknowledge that the prerequisites have been met by selecting all the check boxes. Click Next.

    Note:

    The Upgrade Assistant does not verify whether the prerequisites have been met.
  5. On the WebCenter Sites Source Version screen, select 12.2.1.0.0 and Later and click Next. This is the starting point of your upgrade.
  6. On the WebCenter Sites Source Schema screen, select the database type from the Database Type drop-down list.
    Specify the database connect string in the Database Connect String field in the following format:
    • (Oracle Database) host:port/service or host:port:SID or TNS connect string
    • (Microsoft SQL Server) //host:port;DatabaseName=dbname
    • (IBM DB2) //host:port;DatabaseName=dbname
    Specify the user name with DBA privileges in the DBA User Name field. Specify the DBA password in the DBA Password field.
    Specify the user name and password for the schema in the Schema User Name and Schema Password fields, respectively.

    Note:

    For the DB2 database schema upgrade, the Oracle WebCenter Sites component will not be listed if you select All Schemas Used by a Domain in the Selected Schemas screen because WebCenter Sites uses a different driver class from what WebLogic provides. Therefore, you must upgrade Oracle WebCenter Sites schema by selecting Individually Selected Schemas separately from the rest of the components that WebCenter Sites uses.

  7. On the WebCenter Sites Location screen, specify the complete location of the existing Sites home and Sites shared directory, and location of the 12c configuration file: wcs_properties.json.
    Click Next.
  8. On the Examine screen, review the status of the Upgrade Assistant as it examines each schema, verifying that the schema is ready for upgrade. If the status is Examine finished, click Next.
    If the examine phase fails, Oracle recommends that you cancel the upgrade by clicking No in the Examination Failure dialog. Click View Log to see what caused the error and refer to Troubleshooting Your Upgrade in Oracle Fusion Middleware Upgrading with the Upgrade Assistant for information on resolving common upgrade errors.

    Note:

    • If you resolve any issues detected during the examine phase without proceeding with the upgrade, you can start the Upgrade Assistant again without restoring from backup. However, if you proceed by clicking Yes in the Examination Failure dialog box, you need to restore your pre-upgrade environment from backup before starting the Upgrade Assistant again.

    • Canceling the examination process has no effect on the schemas or configuration data; the only consequence is that the information the Upgrade Assistant has collected must be collected again in a future upgrade session.

  9. On the Upgrade Summary screen, review the summary of the schemas that will be upgraded and/or created.
    Verify that the correct Source and Target Versions are listed for each schema you intend to upgrade.
    If you want to save these options to a response file to run the Upgrade Assistant again later in response (or silent) mode, click Save Response File and provide the location and name of the response file. A silent upgrade performs exactly the same function that the Upgrade Assistant performs, but you do not have to manually enter the data again.
    Click Next .
  10. On the Upgrade Progress screen, monitor the status of the upgrade.

    Caution:

    Allow the Upgrade Assistant enough time to perform the upgrade. Do not cancel the upgrade operation unless absolutely necessary. Doing so may result in an unstable environment.
    If any schemas are not upgraded successfully, refer to the Upgrade Assistant log files for more information.

    Note:

    The progress bar on this screen displays the progress of the current upgrade procedure. It does not indicate the time remaining for the upgrade.

    Click Next.

  11. If the upgrade is successful: On the Upgrade Success screen, click Close to complete the upgrade and close the wizard.

    If the upgrade fails: On the Upgrade Failure screen, click View Log to view and troubleshoot the errors. The logs are available at NEW_ORACLE_HOME/oracle_common/upgrade/logs.

    Note:

    If the upgrade fails, you must restore your pre-upgrade environment from backup, fix the issues, then restart the Upgrade Assistant.

Parent topic: Upgrading Product Schemas

Verifying the Schema Upgrade

After completing all the upgrade steps, verify that the upgrade was successful by checking that the schema version in schema_version_registry has been properly updated.

If you are using an Oracle database, connect to the database as a user having Oracle DBA privileges, and run the following from SQL*Plus to get the current version numbers: 

SET LINE 120
COLUMN MRC_NAME FORMAT A14
COLUMN COMP_ID FORMAT A20
COLUMN VERSION FORMAT A12
COLUMN STATUS FORMAT A9
COLUMN UPGRADED FORMAT A8
SELECT MRC_NAME, COMP_ID, OWNER, VERSION, STATUS, UPGRADED FROM SCHEMA_VERSION_REGISTRY ORDER BY MRC_NAME, COMP_ID ;

In the query result:

  • Check that the number in the VERSION column matches the latest version number for that schema. For example, verify that the schema version number is 12.2.1.4.0.

    Note:

    However, that not all schema versions will be updated. Some schemas do not require an upgrade to this release and will retain their pre-upgrade version number.

  • The STATUS field will be either UPGRADING or UPGRADED during the schema patching operation, and will become VALID when the operation is completed.

  • If the status appears as INVALID, the schema update failed. You should examine the logs files to determine the reason for the failure.

  • Synonym objects owned by IAU_APPEND and IAU_VIEWER will appear as INVALID, but that does not indicate a failure.

    They become invalid because the target object changes after the creation of the synonym. The synonyms objects will become valid when they are accessed. You can safely ignore these INVALID objects.

Parent topic: Upgrading Product Schemas

About Reconfiguring the Domain

Run the Reconfiguration Wizard to reconfigure your domain component configurations to 12c (12.2.1.4.0).

Note:

If the source is a clustered environment, run the Reconfiguration Wizard on the primary node only.

When you reconfigure a WebLogic Server domain, the following items are automatically updated, depending on the applications in the domain:

  • WebLogic Server core infrastructure

  • Domain version

Note:

Before you begin the domain reconfiguration, note the following limitations:

  • The Reconfiguration Wizard does not update any of your own applications that are included in the domain.

  • Transforming a non-dynamic cluster domain to a dynamic cluster domain during the upgrade process is not supported.

    The dynamic cluster feature is available when running the Reconfiguration Wizard, but Oracle only supports upgrading a non-dynamic cluster upgrade and then adding dynamic clusters. You cannot add dynamic cluster during the upgrade process.

  • If the installation that you’re upgrading does not use Oracle Access Management (OAM), then you must edit two files to prevent the Reconfiguration Wizard from attempting to update the nonexistent OAM Infrastructure schema, which causes the upgrade to fail.

    Comment out the lines in your $DOMAIN/init-info/domain-info.xml that are similar to this example: 

    <!--extention-template-ref name="Oracle Identity Navigator" 
  version="11.1.1.3.0" 
  location="/u01/app/oracle/product/fmw/iam111130/common/templates/applications/yourcomany.oinav_11.1.1.3.0_template.jar" 
  symbol=""/-->

<!--install-comp-ref name="oracle.idm.oinav" version="11.1.1.3.0" 
  symbol="yourcompany.idm.oinav_11.1.1.3.0_iam111130_ORACLE_HOME" 
  product_home="/u01/app/oracle/product/fmw/iam111130"/-->

    and similarly comment out the lines in $DOMAIN/config/config.xml that are similar to this example: 

    <!--app-deployment> 
  <name>oinav#11.1.1.3.0</name>
  <target>AdminServer</target>
  <module-type>ear</module-type>

  <source-path>/u01/app/oracle/product/fmw/iam111130/oinav/modules/oinav.ear_11.1.1.3.0/oinav.ear</source-path>
  <deployment-order>500</deployment-order>
  <security-dd-model>DDOnly</security-dd-model>
  <staging-mode>nostage</staging-mode>
</app-deployment-->
Specifically, when you reconfigure a domain, the following occurs:

  • The domain version number in the config.xml file for the domain is updated to the Administration Server's installed WebLogic Server version.

  • Reconfiguration templates for all installed Oracle products are automatically selected and applied to the domain. These templates define any reconfiguration tasks that are required to make the WebLogic domain compatible with the current WebLogic Server version.

  • Start scripts are updated.

    If you want to preserve your modified start scripts, be sure to back them up before starting the Reconfiguration Wizard.

Note:

When the domain reconfiguration process starts, you can’t undo the changes that it makes. Before running the Reconfiguration Wizard, ensure that you have backed up the domain as covered in the pre-upgrade checklist. If an error or other interruption occurs while running the Reconfiguration Wizard, you must restore the domain by copying the files and directories from the backup location to the original domain directory. This is the only way to ensure that the domain has been returned to its original state before reconfiguration.

Follow these instructions to reconfigure the existing domain using the Reconfiguration Wizard. See Reconfiguring WebLogic Domains in Oracle Fusion Middleware Upgrading Oracle WebLogic Server.

Parent topic: Upgrading WebCenter Sites from a Previous 12c Release

Backing Up the Domain

Before running the Reconfiguration Wizard, create a backup copy of the domain directory.

To create a backup of the domain directory:

  1. Copy the source domain to a separate location to preserve the contents.
    (Windows) copy C:\domains\mydomain to C:\domains\mydomain_backup.
    (UNIX) cp mydomain /domains/mydomain_backup
  2. Before updating the domain on each remote Managed Server, create a backup copy of the domain directory on each remote machine.
  3. Verify that the backed up versions of the domain are complete.
If domain reconfiguration fails for any reason, you must copy all files and directories from the backup directory into the original domain directory to ensure that the domain is returned entirely to its original state before reconfiguration.

Parent topic: About Reconfiguring the Domain

Starting the Reconfiguration Wizard

Note:

Shut down the administration server and all collocated managed servers before starting the reconfiguration process. See Stopping Servers and Processes.

To start the Reconfiguration Wizard in graphical mode:

  1. Sign in to the system on which the domain resides.
  2. Open the command shell (on UNIX operating systems) or open a command prompt window (on Windows operating systems).
  3. Edition Based Database Users Only: If your schemas are configured with EBR database, a default edition name must be manually supplied before you run the Reconfiguration Wizard.
    Run the following SQL command to set the default edition:

    ALTER DATABASE DEFAULT EDITION = edition_name;

    where edition_name is the child edition name.

  4. Go to the oracle_common/common/bin directory:
    • (UNIX) NEW_ORACLE_HOME/oracle_common/common/bin
    • (Windows) NEW_ORACLE_HOME\oracle_common\commom\bin
  5. Start the Reconfiguration Wizard with the following logging options:
    • (UNIX) ./reconfig.sh -log=log_file -log_priority=ALL
    • (Windows) reconfig.cmd -log=log_file -log_priority=ALL

    where log_file is the absolute path of the log file you'd like to create for the domain reconfiguration session. This can be helpful if you need to troubleshoot the reconfiguration process.

    The parameter -log_priority=ALL ensures that logs are logged in fine mode.

    Note:

    When you run this command, the following error message might appear to indicate that the default cache directory is not valid:

    *sys-package-mgr*: can't create package cache dir

    You can change the cache directory by setting the environment variable CONFIG_JVM_ARGS. For example:

    CONFIG_JVM_ARGS=-Dpython.cachedir=valid_directory

Parent topic: About Reconfiguring the Domain

Reconfiguring the WebCenter Sites Domain with the Reconfiguration Wizard

Navigate through the screens in the Reconfiguration Wizard to reconfigure your existing domain.

Note:

Reconfiguration templates are automatically selected for every Oracle product that is installed, and are applied to the domain. These templates define any reconfiguration tasks that are required to make the WebLogic domain compatible with the current WebLogic Server version. If you see a template that is reported as missing, verify whether you have installed that respective Oracle product in your domain. For example, if Oracle HTTP Server is part of your existing domain, ensure that you install the 12c (12.2.1.4.0) Oracle HTTP Server product distribution.

Note:

If the source is a clustered environment, run the Reconfiguration Wizard on the primary node only.
To reconfigure the domain with the Reconfiguration Wizard:
  1. On the Select Domain screen, specify the location of the domain you want to upgrade or click Browse to navigate and select the domain directory. Click Next.
  2. On the Reconfiguration Setup Progress screen, view the progress of the setup process. When complete, click Next.
    During this process:

    • The reconfiguration templates for your installed products, including Fusion Middleware products, are automatically applied. This updates various domain configuration files such as config.xml, config-groups.xml, and security.xml (among others).

    • Schemas, scripts, and other such files that support your Fusion Middleware products are updated.

    • The domain upgrade is validated.

  3. On the Domain Mode and JDK screen, select the JDK to use in the domain or click Browse to navigate to the JDK you want to use. The supported JDK version for 12c (12.2.1.4.0) is 1.8.0_211 and later. Click Next.

    Note:

    You cannot change the Domain Mode at this stage.
    For a list of JDKs that are supported for a specific platform, see Oracle Fusion Middleware Supported System Configurations.
  4. On the Database Configuration Type screen, select RCU Data to connect to the Server Table (_STB) schema.
    Enter the database connection details using the RCU service table (_STB) schema credentials and click Get RCU Configuration.
    The Reconfiguration Wizard uses this connection to automatically configure the data sources required for components in your domain.

    Note:

    By default Oracle’s Driver (Thin) for Service connections; Versions: Any is the selected driver. If you specified an instance name in your connection details — instead of the service name — you must select Oracle’s Driver (Thin) for pooled instance connections; Versions: Any If you do not change the driver type, then the connection will fail.

    Note:

    For any existing 12c (12.2.1.3.0) datasource, the reconfiguration will preserve the existing values. For new datasources where the schema was created for 12c (12.2.1.4.0) by the RCU, the default connection data will be retrieved from the _STB schema. If no connection data for a given schema is found in the _STB schema, then the default connection data is used.
    If the check is successful, click Next. If the check fails, reenter the connection details correctly and try again.
  5. On the JDBC Component Schema screen, verify that the DBMS/Service and the Host name is correct for each component schema and click Next.
  6.  For DB2, Populate the DBMS/Service and HostName for the WCSITES Component Schema in the 'Component Datasources' screen for reconfig.
  7. On the JDBC Component Schema Test screen, select all the component schemas and click Test Selected Connections to test the connection for each schema. The result of the test is indicated in the Status column.
    When the check is complete, click Next.
  8. On the Advanced Configuration screen, you can select all categories for which you want to perform advanced configuration. For each category you select, the appropriate configuration screen is displayed to allow you to perform advanced configuration.

    Note:

    The categories that are listed on the Advanced Configuration screen depend on the resources defined in the templates you selected for the domain.
    For this upgrade, select none of the options and click Next.
  9. On the Configuration Summary screen, review the detailed configuration settings of the domain before continuing.
    You can limit the items that are displayed in the right-most panel by selecting a filter option from the View drop-down list.
    To change the configuration, click Back to return to the appropriate screen. To reconfigure the domain, click Reconfig.

    Note:

    The location of the domain does not change when you reconfigure it.
  10. The Reconfiguration Progress screen displays the progress of the reconfiguration process.
    During this process:

    • Domain information is extracted, saved, and updated.

    • Schemas, scripts, and other such files that support your Fusion Middleware products are updated.

    When the progress bar shows 100%, click Next.
  11. The End of Configuration screen indicates whether the reconfiguration process completed successfully or failed. It also displays the location of the domain that was reconfigured as well as the Administration Server URL (including the listen port). If the reconfiguration is successful, it displays Oracle WebLogic Server Reconfiguration Succeeded.
    If the reconfiguration process did not complete successfully, an error message is displayed indicates the reason. Take appropriate action to resolve the issue. If you cannot resolve the issue, contact My Oracle Support.
    Note the Domain Location and the Admin Server URL for further operations.

Parent topic: About Reconfiguring the Domain

Upgrading Domain Component Configurations

After reconfiguring the domain, use the Upgrade Assistant to upgrade the domain component configurations inside the domain to match the updated domain configuration.

Parent topic: Upgrading WebCenter Sites from a Previous 12c Release

Starting the Upgrade Assistant

Run the Upgrade Assistant to upgrade product schemas, domain component configurations, or standalone system components to 12c (12.2.1.4.0).

To start the Upgrade Assistant:

Note:

Before you start the Upgrade Assistant, make sure that the JVM character encoding is set to UTF-8 for the platform on which the Upgrade Assistant is running. If the character encoding is not set to UTF-8, then you will not be able to download files containing Unicode characters in their names. This can cause the upgrade to fail.

  1. Go to the oracle_common/upgrade/bin directory:
    • (UNIX) ORACLE_HOME/oracle_common/upgrade/bin
    • (Windows) ORACLE_HOME\oracle_common\upgrade\bin
  2. Start the Upgrade Assistant:
    • (UNIX) ./ua
    • (Windows) ua.bat

For information about other parameters that you can specify on the command line, such as logging parameters, see:

Parent topic: Upgrading Domain Component Configurations

Upgrade Assistant Parameters

When you start the Upgrade Assistant from the command line, you can specify additional parameters.

Table 9-5 Upgrade Assistant Command-Line Parameters

Parameter Required or Optional Description

-readiness

 Required for readiness checks

Note: Readiness checks cannot be performed on standalone installations (those not managed by the WebLogic Server).

Performs the upgrade readiness check without performing an actual upgrade.

Schemas and configurations are checked.

Do not use this parameter if you have specified the -examine parameter.

-threads

Optional

Identifies the number of threads available for concurrent schema upgrades or readiness checks of the schemas.

The value must be a positive integer in the range 1 to 8. The default is 4.

-response

Required for silent upgrades or silent readiness checks

Runs the Upgrade Assistant using inputs saved to a response file generated from the data that is entered when the Upgrade Assistant is run in GUI mode. Using this parameter runs the Upgrade Assistant in silent mode (without displaying Upgrade Assistant screens).

-examine

Optional

Performs the examine phase but does not perform an actual upgrade.

Do not specify this parameter if you have specified the -readiness parameter.

-logLevel attribute

Optional

Sets the logging level, specifying one of the following attributes:

  • TRACE

  • NOTIFICATION

  • WARNING

  • ERROR

  • INCIDENT_ERROR

The default logging level is NOTIFICATION.

Consider setting the -logLevel TRACE attribute to so that more information is logged. This is useful when troubleshooting a failed upgrade. The Upgrade Assistant's log files can become very large if -logLevel TRACE is used.

-logDir location

Optional

Sets the default location of upgrade log files and temporary files. You must specify an existing, writable directory where the Upgrade Assistant creates log files and temporary files.

The default locations are:

(UNIX)

ORACLE_HOME/oracle_common/upgrade/logs
ORACLE_HOME/oracle_common/upgrade/temp

(Windows)

ORACLE_HOME\oracle_common\upgrade\logs
ORACLE_HOME\oracle_common\upgrade\temp

-help

Optional

Displays all of the command-line options.

Upgrading WebCenter Sites Domain Components Using the Upgrade Assistant

Navigate through the screens in the Upgrade Assistant to upgrade component configurations in the WebLogic domain.

When performing a reduced downtime upgrade for WebCenter Sites, you must run the Upgrade Assistant a second time to upgrade the component configurations. This step is not needed for the other WebCenter components.

To upgrade domain component configurations with the Upgrade Assistant:
  1. On the Welcome screen, review an introduction to the Upgrade Assistant and information about important pre-upgrade tasks. Click Next.

    Note:

    For more information about any Upgrade Assistant screen, click Help on the screen.
  2. On the next screen:

    • Select All Configurations Used By a Domain. The screen name changes to WebLogic Components.

    • In the Domain Directory field, enter the WebLogic domain directory path.

    Click Next.

  3. On the Component List screen, verify that the list includes all the components for which you want to upgrade configurations and click Next.
    If you do not see the components you want to upgrade, click Back to go to the previous screen and specify a different domain.
  4. On the Prerequisites screen, acknowledge that the prerequisites have been met by selecting all the check boxes. Click Next.

    Note:

    The Upgrade Assistant does not verify whether the prerequisites have been met.
  5. On the WebCenter Sites Source Version screen, select 12.2.1.0.0 or Later and click Next. This is the starting point of your upgrade.
  6. (Clustered environment) If the Source environment is a Clustered environment, use the pack/unpack utility to apply the changes to other cluster members in the domain.
    In Primary node, go to path of target environment and execute PACK command:
    $ORACLE_HOME/oracle_common/common/bin
    In Secondary cluster member nodes, go to target environment and execute UNPACK command:
    $ORACLE_HOME/oracle_common/common/bin
    1. On each of the Secondary cluster member nodes, replace the Sites config folder with the one from the Primary node by copying the $DOMAIN_HOME/wcsites/wcsites/config/ to each of the nodes from the Primary node.
    2. On each of the Secondary cluster member nodes, update the following files located at DOMAIN_HOME/wcsites/wcsites/config/:
      • host properties:

        In this file, replace IP-Address details of Primary node with Secondary node details

      • jbossTicketCacheReplicationConfig.xml:

        Update the bind_addr property with a valid host or IP address of Primary node with Secondary node details for this Secondary cluster node

        Note:

        Oracle recommends changing the multicastGroupPort value to a unique value greater than 2048. Ensure that the multicast port used in jbossTicketCacheReplicationConfig.xml is the same on each node in the cluster but is different on other clusters running on the same network.
      • cas-cache.xml:

        If you are using IPv6 addressing, set multicastGroupAddress value to a valid IPv6 multicast address. This value must be the same for each node in the cluster. For example: [ff0x:0:0:0:0:0:0:301].

        Set the timeToLive parameter to a value appropriate for your environment (typically 1). The timeToLive field must be changed from the default value of 0 if the cluster members are not all collocated on the same machine. This field must be set based on the distribution of your clustered machines, as shown in the following table:

        Table 9-6 Description of the different values of the timeToLive field

        timeToLive Value Description

        1

        Multicast packets restricted to the same subnet.

        32

        Multicast packets restricted to the same site.

        64

        Multicast packets restricted to the same geographical region.

        128

        Multicast packets restricted to the same continent.

        256

        No restriction.

        Repeat this step for cs-cache.xml, linked-cache.xml, and ss-cache.xml files.

        Note:

        For all these 4-xml files(cas-cache.xml, cs-cache.xml, linked-cache.xml, and ss-cache.xml) the values of “multicastGroupAddress”, “timeToLive”, “multicastGroupPort” should be appropriate as per the Primary node
    3. On each of the Secondary cluster member node go to path EXISTING_DOMAIN_HOME/bin and modify setStartupEnv.sh file
      • Ensure –Dsites.node=<Secondary cluster node name>. If this parameter is not present then add this parameter
      • Ensure –Dsites.config=<Folder Path containing wcs_properties.json file>

      Note:

      The wcs_properties.json file is shared among Primary and Secondary cluster member nodes, so the location path of this file should be the same for Primary and Secondary cluster member nodes.
  7. On the Examine screen, review the status of the Upgrade Assistant as it examines each component, verifying that the component configuration is ready for upgrade. If the status is Examine finished, click Next.
    If the examine phase fails, Oracle recommends that you cancel the upgrade by clicking No in the Examination Failure dialog. Click View Log to see what caused the error and refer to Troubleshooting Your Upgrade in Oracle Fusion Middleware Upgrading with the Upgrade Assistant for information on resolving common upgrade errors.

    Note:

    • If you resolve any issues detected during the examine phase without proceeding with the upgrade, you can start the Upgrade Assistant again without restoring from backup. However, if you proceed by clicking Yes in the Examination Failure dialog box, you need to restore your pre-upgrade environment from backup before starting the Upgrade Assistant again.

    • Canceling the examination process has no effect on the configuration data; the only consequence is that the information the Upgrade Assistant has collected must be collected again in a future upgrade session.

  8. On the Upgrade Summary screen, review the summary of the options you have selected for component configuration upgrade.
    The response file collects and stores all the information that you have entered, and enables you to perform a silent upgrade at a later time. The silent upgrade performs exactly the same function that the Upgrade Assistant performs, but you do not have to manually enter the data again. If you want to save these options to a response file, click Save Response File and provide the location and name of the response file.
    Click Upgrade to start the upgrade process.
  9. On the Upgrade Progress screen, monitor the status of the upgrade.

    Caution:

    Allow the Upgrade Assistant enough time to perform the upgrade. Do not cancel the upgrade operation unless absolutely necessary. Doing so may result in an unstable environment.
    If any components are not upgraded successfully, refer to the Upgrade Assistant log files for more information.

    Note:

    The progress bar on this screen displays the progress of the current upgrade procedure. It does not indicate the time remaining for the upgrade.

    Click Next.

  10. If the configuration upgrade is successful, summary files are generated at the following location:
    NEW_ORACLE_HOME/oracle_common/upgrade/logs/
    If the source is a clustered environment, the summary details are generated for each cluster as follows:
    NEW_ORACLE_HOME/oracle_common/upgrade/logs/
    If the schema upgrade fails, you can review the logs for possible errors. The log file is generated at the following location:
    NEW_ORACLE_HOME/oracle_common/upgrade/logs
    Click Close to close the Upgrade Assistant.

Parent topic: Upgrading Domain Component Configurations

Verifying the Domain-Specific-Component Configurations Upgrade

To verify that the domain-specific-component configurations upgrade was successful, sign in to the Administration console and the Oracle Enterprise Manager Fusion Middleware Control and verify that the version numbers for each component is 12.2.1.4.0.

To sign in to the Administration Console, go to: http://administration_server_host:administration_server_port/console

To sign in to Oracle Enterprise Manager Fusion Middleware Control Console, go to: http://administration_server_host:administration_server_port/em

Note:

After upgrade, make sure you run the administration tools from the new 12c (12.2.1.4.0) Oracle home directory and not from the previous Oracle home directory.

During the upgrade process, some OWSM documents, including policy sets and predefined documents such as policies and assertion templates, may need to be upgraded. If a policy set or a predefined document is upgraded, its version number is incremented by 1.

If you created the FMW user to run the Upgrade Assistant, ensure that you delete the account after verifying your upgrade was successful.

Parent topic: Upgrading Domain Component Configurations

Starting Servers and Processes

After a successful upgrade, restart all processes and servers, including the Administration Server and any Managed Servers.

The components may be dependent on each other so they must be started in the correct order.

Note:

The procedures in this section describe how to start servers and process using the WLST command line or a script. You can also use the Oracle Fusion Middleware Control and the Oracle WebLogic Server Administration Console. See Starting and Stopping Administration and Managed Servers and Node Manager in Administering Oracle Fusion Middleware.

To start your Fusion Middleware environment, follow the steps below:

Step 1: Start the Administration Server

When you start the Administration Server, you also start the processes running in the Administration Server, including the WebLogic Server Administration Console and Fusion Middleware Control.

To start the Administration Server, use the startWebLogic script:

  • (UNIX) DOMAIN_HOME/bin/startWebLogic.sh

  • (Windows) DOMAIN_HOME\bin\startWebLogic.cmd

When prompted, enter your user name, password, and the URL of the Administration Server.

Step 2: Start Node Manager

To start Node Manager, use the startNodeManager script:

  • (UNIX) DOMAIN_HOME/bin/startNodeManager.sh

  • (Windows) DOMAIN_HOME\bin\startNodeManager.cmd

Step 3: Start the Managed Servers

To start a WebLogic Server Managed Server, use the startManagedWebLogic 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.

Note:

The startup of a Managed Server will typically start the applications that are deployed to it. Therefore, it should not be necessary to manually start applications after the Managed Server startup.

Step 4: Start System Components

To start system components, such as Oracle HTTP Server, use the startComponent script:

  • (UNIX) DOMAIN_HOME/bin/startComponent.sh component_name

  • (Windows) DOMAIN_HOME\bin\startComponent.cmd component_name

You can start system components in any order.

Parent topic: Upgrading WebCenter Sites from a Previous 12c Release

Post-Upgrade Validation Tasks

Oracle has provided validation scripts that you can run on your newly upgraded domain to ensure data integrity after a successful schema and configuration upgrade. You can review the validation summary report for any inconsistencies in data that may have occurred during the schema and configuration upgrade processes.

To run the validation script:
  1. The validation script is available at the following locations in the new Oracle Home:
    (UNIX) Oracle_Home/wcsites/plugins/upgrade/
    (UNIX) ./validation.sh
    (Windows) Oracle_Home\wcsites\plugins\upgrade\
    (Windows) validation.bat
  2. When the validation check is complete, validation summary report: Validation.txt is generated. Save it at any location on your system.
  3. Review the validation summary report to check if there is any inconsistency in the data between your existing domain and the newly configured 12.2.1.4.0 domain.

Parent topic: Upgrading WebCenter Sites from a Previous 12c Release

Post-Upgrade Tasks

The post-upgrade tasks include restoring any custom settings, starting Administration Server and Managed Servers, reconfiguring passwords, and other administrative tasks listed in this topic.

After upgrading to WebCenter Sites 12.2.1.4.0:
  1. Re-enable Lucene search indexes.
    Follow these steps after the upgrade process to re-enable Lucene search indexes to perform search operations in Contributor UI. Indexes need to be recreated as the Lucene version is now upgraded:
    1. Set the ORACLE_HOME environment variable to the directory where you have installed Oracle WebCenter Sites.
    2. Stop all servers and components including the Admin Server and all managed servers.
    3. Create a complete backup of the existing <DOMAIN_HOME/wcsites/wcsites/lucene> folder. The /lucene folder is located in the WebCenter Sites /shared folder.
    4. Set the following environment variables using a terminal window:
      • JAVA_HOME to the latest supported JDK version (currently JDK 1.8.0_211)
      • LUCENEPATH to the existing <DOMAIN_HOME/wcsites/wcsites/lucene> as shown in the following example:

        export LUCENEPATH=/scratch/Sites12.2.1.4.0/DOMAIN_HOME/wcsites/wcsites/lucene>

    5. Download the Lucene jar files (JARS).
    6. Navigate to the folder where the Lucene JARs were downloaded and execute the following two commands:

      Note:

      Make sure that there are no exceptions (errors) when executing these commands which migrate the indices from Lucene version 4.4 to 6.6 version.
      On Linux operating systems:
      find $LUCENEPATH -mindepth 1 -type d -exec java
        -cp lucene-core-5.5.5.jar:lucene-backward-codecs-5.5.5.jar
        org.apache.lucene.index.IndexUpgrader {} \;
      find $LUCENEPATH -mindepth 1 -type d -exec java
        -cp lucene-core-6.6.0.jar:lucene-backward-codecs-6.6.0.jar
        org.apache.lucene.index.IndexUpgrader {} \;
      On Windows operating systems (substitute your actual directory paths):
      c:\LuceneJars>java -cp
      lucene-core-5.5.5.jar;lucene-backward-codecs-5.5.5.jar org.apache.lucene.index.IndexUpgrader
      <Path of \lucene folder present in Sites \shared folder>\<Flex or Basic Asset type
      Name (such as Flex_C11)>
      c:\LuceneJars>java -cp
      lucene-core-6.6.0.jar;lucene-backward-codecs-6.6.0.jar org.apache.lucene.index.IndexUpgrader
      Path of \lucene folder present in Sites \shared folder>\<Flex or Basic Asset type
      Name (such as Flex_C11)>
  2. Restore or re-deploy the custom settings from your existing environment to your 12.2.1.4.0 environment.
    These include custom changes made to Java libraries, static web resources, or element changes.
    To restore changes made to the Java libraries or static web pages, see Migrating Custom Java Libraries or Static Web Resources.
  3. Start Administration Server and Managed Servers. See Starting Servers and Processes.

    Note:

    Before you start the Administration Server and Managed Servers, clear the cached images and files in the browser.

  4. Reconfigure passwords for the publishing process.
    1. Sign in to the Administration Server URL as the Administrator.
    2. Go to Admin menu and click Destinations under Publishing.
    3. Update the publishing destination URL, Port, Username, and Password.
  5. If external WebRoots are configured, update WebRoots from Sites Admin user interface.
  6. If your source was a clustered environment, copy the config directory xml file settings from your source environment on which you run the Upgrade Assistant, to all other nodes on your upgraded environment.
    These include the following:
    • cs-cache.xml
    • cas-cache.xml
    • ss-cache.xml
    • linked-cache.xml
    • MobilityServices.xml
    • Custom/RestResources.xml
    • wcs_properties_bootstrap.ini
  7. (Applicable only if you are using SQL server) Fusion Middleware Infrastructure Release 12c requires the SQL Server database to be configured in a case sensitive mode. As a result, ics:sql jsp tag provided by WebCenter Sites require the table value to be in the same case as stated in the database.
    Following is the syntax of the ics:sql statement:
    <ics:sql
      sql="sql commands"
      listname="list name"
      table="name of table"
      [limit="max number of results"]/>

    You must provide the name of the table in the same case as specified in the SQL Server database.

  8. The following properties are reset to the application Admin user account values provided during Sites Configuration Setup process:
    • xcelerate.batchuser and password
    • cs.emailpassword
    You must update these properties with their appropriate values using the Property Management Tool.
  9. After WCC integration, reset the wcc.server.password in WCC Configuration to view all the mapped rules.
  10. If the instance is delivery and has any of the Sample Sites published, then you must republish the Sample Sites to the delivery instance from upgraded development instance.
  11. (If you are upgrading from a previous 12c release only and if Sites is installed with RSS and Site Capture on same domain)
    1. If you are upgrading Sites with RSS and Site Capture to 12c (12.2.1.4.0) from 12.2.1.0 or a later release, you must create a new domain and install RSS and Site Capture again.
    2. If you are not installing Site Capture on the same port, perform the following:

      1. Change the Site Capture port in the FW_View and FW_Application tables for Site Capture in Sites

      2. Change the port number in the valid.urls property

      3. Change the port number in other properties under the SiteCapture category

    3. After installing RSS, change the RSS port in the SystemSatellite table, unless RSS is installed on same port.

Parent topic: Upgrading WebCenter Sites from a Previous 12c Release

Migrating Custom Java Libraries or Static Web Resources

Perform this optional step only if custom Java libraries or static web resources were added to the web application in your pre-upgrade environment and you want to continue to use them in the upgraded environment.

If the web application includes custom Java libraries (jar files) or custom static web resources, such as css, js, or images, then you will have to manually migrate them to the upgraded environment after the upgrade. If you do not migrate these resources, you will not be able to access the functionality in the upgraded environment.

The WebCenter Sites web application is shipped as a WAR file. The web application is deployed during Config Wizard process initially and can be redeployed multiple times during the application lifecycle. Oracle recommends that you do not include any implementation-specific customizations to the Sites WAR file as the changes will be overwritten during the upgrade process.

When extending the WebLogic Server Shared Libraries framework, Sites provides extend.sites.webapp-lib.war as a shared library. This file is located in NEW_ORACLE_HOME/wcsites/webcentersites/sites-home/ directory. Any implementation-specific customizations, such as static web resources or JAVA libraries, can be included in this WAR file. This shared library gets deployed during application lifecycle and shares the same context root as sites (/sites/). The contents of this shared library will not be overwritten during patching process.

Additionally, if the Sites UI has been customized, the code changes must also be migrated to the upgraded environment.

Parent topic: Upgrading WebCenter Sites from a Previous 12c Release