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

Figure 5-1 Upgrade Process Flowchart for WebCenter Sites from 11g to 12c Release

Description of "Figure 5-1 Upgrade Process Flowchart for WebCenter Sites from 11g to 12c Release"

Table 5-1 provides a roadmap for tasks that you must perform to upgrade WebCenter Sites from 11g to 12c.

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.

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:

     Ensure that you select WebCenter Sites and not WebCenter Sites with Examples.

   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

When upgrading, you must create the required schemas. You can use the Repository Creation Utility (RCU) to create customized schemas or, optionally, you can use the Upgrade Assistant to create schemas using the default schema settings. This procedure describes how to create schemas using the RCU. Information about using the Upgrade Assistant to create schemas is covered in the upgrade procedures.

1. (Optional) If you are upgrading from 12c, and you wish to confirm the schemas which are present in your existing domain, then connect to the database as a user with DBA privileges, and run the following code from SQL*Plus:

   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 ;
   

2. Verify that a certified JDK already exists on your system by running java -version from the command line. For 12c (12.2.1.4.0), the certified JDK is 1.8.0_211 and later.
   Ensure that the JAVA_HOME environment variable is set to the location of the certified JDK. For example:
   • (UNIX) setenv JAVA_HOME=/home/Oracle/Java/jdk1.8.0_211
   • (Windows) set JAVA_HOME=C:\home\Oracle\Java\jdk1.8.0_211
   Add $JAVA_HOME/bin to $PATH.
3. Go to the oracle_common/bin directory:
   • (UNIX) NEW_ORACLE_HOME/oracle_common/bin
   • (Windows) NEW_ORACLE_HOME\oracle_common\bin
4. Start the RCU:
   • (UNIX) ./rcu
   • (Windows) rcu.bat
5. On the Welcome screen, click Next.
6. On the Create Repository screen, select Create Repository and then select System Load and Product Load.
   If you do not have DBA privileges, select Prepare Scripts for System Load. This will generate a SQL script containing all the same SQL statements and blocks that would have been called if the RCU were to execute the actions for the selected components. After the script is generated, a user with the necessary SYS or SYSDBA privileges can execute the script to complete the system load phase.

   Click Next.

7. On the Database Connection Details screen, select the Database Type and enter the connection information for the database that hosts the 12c schemas. See the pertinent table below.

   Table 5-2 Connection Credentials for Oracle Databases and Oracle Databases with Edition-Based Redefinition

   Option	Description and Example
   Host Name	Specify the name of the server where your database is running in the following format: examplehost.exampledomain.com For Oracle RAC databases, specify the VIP name or one of the node names in this field.
   Port	Specify the port number for your database. The default port number for Oracle databases is 1521.
   Service Name	Specify the service name for the database. Typically, the service name is the same as the global database name. For Oracle RAC databases, specify the service name of one of the nodes in this field. For example: examplehost.exampledomain.com
   Username	Enter the user name for your database. The default user name is SYS.
   Password	Enter the password for your database user.
   Role	Select the database user's role from the drop-down list: Normal or SYSDBA

   Table 5-3 Connection Credentials for MySQL Databases

   Option	Description and Example
   Host Name	Specify the host name, IP address, or complete server name in host\server format of the server where your database is running.
   Port	Specify the port number for your database.
   Database Name	Specify the name of your database.
   Username	Specify the name of a user with administrator privileges.
   Password	Enter the password for your database user.

   Table 5-4 Connection Credentials for Microsoft SQL Server Databases

   Option	Description and Example
   Unicode Support	Select Yes or No from the drop-down list.
   Server Name	Specify the host name, IP address, or complete server name in host\server format of the server where your database is running. MSSQL named instances: A named instance is identified by the network name of the computer and the instance name that you specify during installation. The client must specify both the server name and the instance name when connecting.
   Port	Specify the port number for your database.
   Database Name	Specify the name of your database.
   Username	Specify the name of a user with administrator privileges.
   Password	Enter the password for your database user.

   Table 5-5 Connection Credentials for IBM DB2 Databases

   Option	Description and Example
   Server Name	Specify the host name, IP address, or complete server name in host\server format of the server where your database is running.
   Port	Specify the port number for your database.
   Database Name	Specify the name of your database.
   Username	Specify the name of a user with DB Owner privileges. The default user name for IBM DB2 databases is db2inst1.
   Password	Enter the password for your database user.

   If the prerequisite check is successful, click OK to continue to the next screen. If the check fails, review the details you entered and try again.
8. On the Select Components screen, select Select existing prefix and select the prefix that was used to create the existing 11g schemas from the drop-down menu (for example, DEV11G). This prefix is used to logically group schemas together for use in this domain.
   Select the following schemas:

   • Audit Services

   • Audit Services Append

   • Audit Services Viewers

   • WebCenter Sites

   • Metadata Services (_MDS)

   • User Messaging Service (_UMS)

   • WebLogic Server (_WLS)

   Note:

   The Common Infrastructure Services (prefix_STB) and Oracle Platform Security Services (prefix_OPSS) schemas are selected by default if they have not yet been created.

   Make a note of the prefix and schema names for the components you are installing as you will need this information when you configure the installation. Click Next.
9. In the Checking Prerequisites dialog, verify that the prerequisites check is successful, then click OK.
10. On the Schema Passwords screen, specify the passwords for your schema owners.
    Make a note of the passwords you enter on this screen as you will need this information while configuring your product installation.
11. On the Map Tablespaces screen, configure the required tablespace mapping for the schemas you want to create.
    Click Next, then click OK in the confirmation dialog. When the progress dialog shows the tablespace creation is complete, click OK.
    You see the Encrypt Tablespace check box only if you have enabled Transparent Data Encryption (TDE) in the database (Oracle or Oracle EBR) when you start the RCU. Select the Encrypt Tablespace check box on the Map Tablespaces screen to encrypt all new tablespaces that the RCU creates.
12. Verify the information on the Summary screen and click Create to begin schema creation.
    This screen contains information about the log files that were created from this RCU operation. Click on the name of a particular log file to view the contents of that file.
13. Review the information on the Completion Summary screen to verify that the operation is completed successfully. Click Close to complete the schema creation.

If you are upgrading from WebCenter Sites 11g to 12c, then you must configure the WebCenter Sites domain using the Configuration Wizard.

1. Change directory to the following:
   (UNIX) NEW_ORACLE_HOME/oracle_common/common/bin
   (Windows) NEW_ORACLE_HOME\oracle_common\common\bin
2. Start the configuration wizard by entering the following command:
   (UNIX) ./config.sh
   (Windows) config.cmd
3. On the Configuration Type screen, select Create a new domain.
   In the Domain Location field, specify the Domain home directory and click Next.
   Oracle recommends you to select the domain directory location outside the Oracle home directory, which is where the Fusion Middleware products are installed. To learn more about the recommended directory structure, see What Are the Key Oracle Fusion Middleware Directories? in Oracle Fusion Middleware Understanding Oracle Fusion Middleware.
4. On the Templates screen, select Create Domain Using Product Templates:
   Select the following from the Templates Category drop-down list:

   • Oracle WebCenter Sites - 12.2.1.4.0 [wcsites]
   • Oracle JRF - 12.2.1.4.0 [oracle_common]
   • Oracle Enterprise Manager - 12.2.1.4.0 [em]
   • WebLogic Coherence Cluster Extension - 12.2.1.4.0 [wlserver]

   Note:

   The list of Oracle WebCenter Sites templates available in this screen depends on your selection of template while installing the WebCenter Sites binaries. During the 11g to 12c upgrade process, Oracle recommends you to select only Oracle WebCenter Sites (with or without WebCenter Sites – With Examples).

   Click Next.
5. On the Application Location screen, specify the Application Location to store applications associated with your domain by entering the path or by clicking Browse to use the navigation tree. The Application Location is also known as the Application home directory.
   Oracle recommends you to select the application location outside the Oracle home directory, which is where the Fusion Middleware products are installed. To learn more about the recommended directory structure, see What Are the Key Oracle Fusion Middleware Directories? in Oracle Fusion Middleware Understanding Oracle Fusion Middleware.
   Click Next.
6. On the Administrator Account screen, specify the user name and password you provided for the 11.1.1.8 WebCenter Sites domain click Next.
   These account details are used to boot and connect to the WebCenter Sites domain’s Administrator Server.
7. On the Domain Mode and JDK screen, select Production and Oracle HotSpot JDK from the Domain Mode and JDK sections respectively and click Next.
8. On the Database Configuration Type screen, specify details about the database and database schema.
   Select RCU Data. This option instructs the Configuration Wizard to connect to the database and Service Table (STB) schema to automatically retrieve schema information for schemas needed to configure the domain.
   If you select Manual Configuration on this screen, you must manually fill in parameters for your schema on the JDBC Component Schema screen.
   Specify the connection details in the following fields:

   Note:

   Make sure that the 11g schema and the 12c schema collocate on the same database.

   Table 5-6 Field Descriptions for the Database Configuration Type Screen

   Field	Description
   DBMS/Service	Enter the database DBMS name, or service name if you selected a service type driver. Example: orcl.exampledomain.com
   Host Name	Enter the name of the server hosting the database. Example: examplehost.exampledomain.com
   Port	Enter the port number on which the database listens. Example: 1521
   Schema Owner and Schema Password	Enter the username and password for connecting to the database's Service Table schema that you specified when you created the schemas using the RCU. The default username is prefix_STB, where prefix is the custom prefix that you defined in RCU.

   Click Get RCU Configuration.
   The following output in the Connection Result Log indicates that the operation succeeded. Click OK to go to the next screen.

   Connecting to the database server...OK
   Retrieving schema data from database server...OK
   Binding local schema components with retrieved data...OK
   
   Successfully Done.

9. On the JDBC Component Schema screen, verify or specify the details about the database schemas.
   Verify that the values are correct for all schemas. If you selected RCU Data on the Database Configuration Type screen, the schema table should already be populated appropriately.
   Click Next.
10. The JDBC Component Schema Test screen is used to test the data source connections.
    A green check mark in the Status column indicates a successful test. If you encounter any issues, see the error message in the Connection Result Log section of the screen, fix the problem, then try to test the connection again by clicking Test Selected Connections.
    By default, the schema password for each schema component is the password you specified while creating your schemas. If you want different passwords for different schema components, manually edit them on the previous screen (JDBC Component Schema) by entering the password you want in the Schema Password column, against each row. After specifying the passwords, select the check box corresponding to the schemas that you changed the password in and test the connection again.
    Click Next.
11. The Advanced Configuration screen is used to complete the domain configuration. Select the options for which you want to perform advanced configuration and click Next:

    Table 5-7 Advanced Configuration Screen Options

    Option	Description
    Administration Server	Required to properly configure the listen address of the Administration Server.
    Node Manager	Required to configure Node Manager.
    Topology	Required to configure the WebCenter Sites Managed Server.

12. On the Administration Server screen, specify a server name in the ServerName field.
    Select the IP address of the host from the Listen Address drop-down list where you want the Administration Server to reside. Do not select All Local Addresses.
    You can retain the default value in the Listen Port field or specify a number between 1 and 65535. The custom value must be different from SSL listen port and coherence port.
    Do not specify any Server Groups for the Administration Server.
    Click Next.
13. On the Node Manager screen, select the type of Node Manager you want to configure, along with the Node Manager credentials.
    For the Node Manager Type, select Per Domain Default Location.
    Specify the user name and the password in the Node Manager Credentials field.
14. On the Managed Servers screen, you can Add, Clone, or Delete the Managed Servers and also assign a server group (if available) to a Managed Server.
    1. In the Listen Address drop-down list, select the IP address of the host you want the Managed Server to reside on. You can also specify the system name or DNS name that maps to a single IP address. Do not select All Local Addresses.
    2. Click Enable SSL to enable security.
    The Configuration Wizard automatically populated the default Server Groups for each Managed Server added by default. If you add additional servers, select WCSITES-MGD-SERVER from the Server Groups drop-down list.
    Server Groups target Fusion Middleware applications and services to one or more servers by mapping defined application service groups to each defined server group. A given application service group can be mapped to multiple server groups if needed. Any application services that map to a given server group are automatically targeted to all servers that are assigned to that group.
    Click Help to learn more about adding, cloning, or deleting a Managed Server.
    When finished, click Next.
15. On the Clusters screen, click Add to create a new cluster.
    A cluster is a group of WebLogic Server instances that work together to provide scalability and high-availability for applications. By creating clusters, you can group Managed Servers such that they operate as a single unit for hosting applications and resources.
    Specify a name for your cluster in the Cluster Name field., such as wcs_cluster_1. Leave the Cluster Address field blank.
    Repeat and add one more cluster, namely, wcs_cluster_2, and click Next.
    Be sure to assign the clusters to the WCSITES-MGD-SERVER server group.
    For more information about this screen, click Help.

    Note:

    You can also create clusters using Enterprise Manager Fusion Middleware Control.
16. On the Assign Servers to Clusters screen, assign Managed Servers to the new cluster.
    1. In the Clusters pane, select the cluster to which you want to assign the Managed Servers. For example, wcs_cluster_1.
    2. In the Servers pane, assign a server to a cluster by doing one of the following:

       • Single-click a server from the Servers pane and click the right-arrow button (>) to move it under the selected cluster.

       • Double-click a server from the Servers pane to move it under the selected cluster.

    3. Repeat this procedure to assign all the Servers to the Clusters.

    Note:

    Only Managed Servers are displayed under the Server pane. The Administration Server is not listed because you cannot assign it to a cluster.
    Click Next.
17. The Coherence Clusters screen is displayed only if you have included Coherence during the Infrastructure installation.
    Specify a name for the Coherence Cluster in the Cluster Name field. You can also retain the default name.
    Leave the default port number 0 as the Cluster Listen Port and click Next. After configuration, the Coherence cluster is automatically added to the domain.
18. On the Machines screen, create new machines in the domain. A machine is required so that you can use the Node Manager to start and stop servers.
    Select the Machine tab (for Windows) or the UNIX Machine tab (for UNIX), then click Add to create a new machine.
    Specify a name for the machine in the Name field. For example, wcs_machine_1.
    In the Node Manager Listen Address field, select the IP address of the machine in which you have configured the Managed Servers.
    You must select a specific interface and not localhost. This allows Coherence cluster addresses to be dynamically calculated.

    Note:

    If you are extending an existing domain, you can assign servers to any existing machine. It is not necessary to create a new machine unless your situation requires it.
    Click Next.
19. On the Assign Servers to Machines screen, assign the Administration Server and Managed Servers to the new machine you created on the Machines screen.
    1. In the Machines pane, select the machine to which you want to assign the Administration Server and the Managed Servers. For example, wcs_machine_1.
    2. In the Servers pane, assign each server to a machine by doing one of the following:

       • Single-click a server from the Servers pane and click the right-arrow button (>) to move it under the selected machine.

       • Double-click a server from the Servers pane to move it under the selected machine.

    3. Repeat this procedure to assign all the Servers to the Machine.
    Click Next.
20. On the Virtual Targets screen, click Next.
21. On the Partitions screen, click Next.
22. The Configuration Summary screen has detailed configuration information for the domain you are about to create.
    Review each item on the screen and verify that the information is correct and click Create to create the domain.
    You can limit the items that are displayed in the summary pane by selecting a filter option from the View drop-down list.
    To make any changes, go back to a screen by clicking Back or by selecting the screen in the navigation pane. Domain creation does not start until you click Create.
23. The Configuration Progress screen displays the progress of the domain creation process.
    If the domain creation is successful, click Next.
    If the domain creation fails, review the errors and try again. If you cannot troubleshoot the errors, contact My Oracle Support for further assistance.
24. The End of Configuration screen displays the domain location and the Admin Server URL for the domain you created.
    Note the values for further operations.

After you configure the Oracle WebCenter Sites domain, you can configure a WebCenter Sites instance by completing the browser-based WebCenter SitesConfigurator. WebCenter Sites runtime consists of WebCenter Sites and CAS web applications (WAR files) and the following components shared across cluster members: a config directory, a data directory, and a database instance.

The following topics describe how to configure WebCenter Sites:

• Prerequisites for Configuring WebCenter Sites Instance
  Several prerequisite tasks must be done before you use the WebCenter Sites Configurator. These tasks include granting permissions for OPSS access, modifying cache files, and setting property values for your environment.
• Configuring WebCenter Sites with the Configurator
  The WebCenter Sites Configurator populates the database with tables and data necessary for WebCenter Sites to function. The Configurator also creates the necessary user accounts and sets the required permissions on the database objects.

After configuring the WebCenter Sites 12c, complete the tasks listed in this topic.

1. If the existing Sites 11.1.1.8 environment is configured with LDAP-based or OAM-based authentication, configure the same for your 12.2.1.4.0 environment as well.

   To switch to LDAP-based authentication, see Switching to Authentication Against an LDAP Directory.
   To switch to LDAP-based authentication, see Switching to Authentication Against Oracle Access Manager.

2. Verify the directory structure. You must have Oracle Home (containing product binaries), Sites Home (domain and config data), and Sites Shared directories created after you configure WebCenter Sites.
3. Sign in to the Sites UI using your Administrator credentials.
4. Restart Managed Servers and access WebCenter Sites.

• Switching to Authentication Against an LDAP Directory
  This topic describes how to switch WebCenter Sites to authentication against an external LDAP authentication provider directory. This is a recommended solution for production environments if integration with Oracle Access Management is not viable.
• Switching to Authentication Against Oracle Access Manager
  You can configureWebCenter Sites for authentication against Oracle Access Manager. This solution is recommended for production environments.

Before running the Upgrade Assistant to upgrade from 11.1.1.8, complete the tasks listed in this topic.

1. If your existing Sites 11.1.1.8 environment is a clustered configuration, you can either upgrade the primary node to 12.2.1.4.0 and reconfigure the cluster setup on target, or you can upgrade all cluster members.
   To upgrade all cluster members, register the cluster nodes by completing the following steps:
   1. Sign in to Sites Admin Server URL.
   2. Go to Admin and click Cluster Node Management under System Tools.
   3. Configure node names for each cluster as per the source environment.
      The nodes configured in this step are eventually mapped to the corresponding 11.1.1.8 nodes during the upgrade process.
2. Shut down the source (11.1.1.8) and the target (12.2.1.4.0) Admin Server and Managed Server instances.
3. If the source (11.1.1.8) and target (12.2.1.4.0) are on different physical machines, then Oracle recommends that you migrate the following source install directories on to the target machine before starting the upgrade process.
   Migrating the source install directories on to the target machine helps to reduce the process time during upgrade.
   • Sites 11.1.1.8.0 Sites Install/Home
   • Sites 11.1.1.8.0 Sites Shared
   • Sites 11.1.1.8.0 web apps path of deployed Sites war
4. If your existing Sites 11.1.1.8 environment is a clustered environment, migrate the nodes from source machine to target machine.
   You can migrate the source instance directories in any order. Following is a sample example:
   If the source environment is a two-node cluster setup, create two directories with name which you gave while registering the nodes during Cluster Node Management. For example, if node names given while registering the nodes are NodeA and NodeB, then create two directories: NodeA and NodeB on target machine.
   Copy the source data on the target machine in the following format:

   NodeA (Primary node)
   		Sites-install/Home
   		Sites-Shared
   		Location of deployed sites war
   NodeB (Secondary node)
   		Sites-install/Home
   		Location of deployed sites war

   Note:

   You don’t need to copy Sites-Shared per node.
5.  Ensure that the source schema (11g) and target schema (12c) collocate on the same database server.

   Oracle
   <Single DB Instance>
   11g schema
   12c schema

   MS SQL Server
   <Single DB Instance>
   11g schema
   12c schema

6. If you are an Oracle user, you must create a Non-SYSDBA user for performing the upgrade. To create a Non-SYSDBA user, see Creating a Non-SYSDBA User to Run the Upgrade Assistant.
7. Ensure that the 12.2.1.4.0 target schema tablespace size has enough capacity to complete the successful data migration from the 11g source schema. The default target schema size is set to 5 GB by the RCU. You can adjust the tablespace size according to the size of the source schema.
8. Typically, Sites uses the time zone setting of the WebLogic JVM. However, if you want to use a different time zone, ensure that you change it immediately after you install Sites, that is, before you create any data in the target (12.2.1.4.0) environment.

• Creating a Non-SYSDBA User to Run the Upgrade Assistant
  Oracle recommends that you create a non-SYSDBA user called FMW to run the Upgrade Assistant. This user has the privileges required to modify schemas, but does not have full administrator privileges.
• Copying 11.1.1.8 Schema from a DB2 Source to a New Target Database
  You must import the Sites 11.1.1.8 schema from source DB2 database to target database (where 12.2.1.4.0 Sites schema is setup) before upgrading the schemas.

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.

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.

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.

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/EXISTING_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.

• Starting Servers and Processes
  After a successful upgrade, restart all processes and servers, including the Administration Server and any Managed Servers.
• If the Existing Instance is a Delivery Instance...
  If you are upgrading from 11g to the latest 12c release, and if your existing instance is a delivery instance, then you must manually reassign Apps for the User Published Sites.

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.