6 Upgrading Oracle WebCenter Sites to 12c (12.2.1.1)

You can upgrade your existing Oracle WebCenter Sites 11.1.1.8 and 12.2.1.0 installations to release 12.2.1.1.

Upgrading from 11g to 12c is an out-of-place migration. This includes using the Upgrade Assistant to migrate data tables and platform configuration.

Upgrading from 12.2.1.0 to 12.2.1.1 is an in-place upgrade.

Note:

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

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.
Alternatively, you can upgrade each environments individually.

If you consider this approach, synchronization is not required.

This chapter includes the following topics:

Understanding the WebCenter Sites Upgrade from 11g to 12c
This topic helps you to understand the process flow of the WebCenter Sites upgrade from the 11g to the 12c release using a flowchart.
Upgrading WebCenter Sites from 11g to 12c
The valid 11g starting point for upgrading WebCenter Sites to 12.2.1.1 is WebCenter Sites 11.1.1.8 and above. This is an out-of-place migration.
Understanding the WebCenter Sites Upgrade Process from a Previous 12c Release
This topic helps you to understand the process flow of the WebCenter Sites upgrade from a previous 12c release using a flowchart.
Upgrading WebCenter Sites from a Previous 12c Release
The valid 12c starting point for upgrading WebCenter Sites to 12.2.1.1 is WebCenter Sites 12.2.1.0. This is an in-place upgrade.
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.

6.1 Understanding the WebCenter Sites Upgrade from 11g to 12c

This topic helps you to understand the process flow of the WebCenter Sites upgrade from the 11g to the 12c release using a flowchart.

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

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

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

Table 6-1 Roadmap for WebCenter Sites Upgrade Process from 11g to 12c Release

Step No.	Task	Description
1	Install the 12.2.1.1 Oracle Fusion Middleware Infrastructure.	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. Therefore, follow the procedure described in Installing Fusion Middleware Infrastructure.
2	Install the 12.2.1.1 Oracle WebCenter Sites distribution.	Install Oracle WebCenter Sites distribution as described in Installing WebCenter Sites 12.2.1.1.0 Distribution.
3	Create the required schemas.	If you are upgrading from WebCenter Sites 11g, you must create the required 12c schemas before you begin the upgrade. The schemas required for WebCenter Sites are: Oracle Platform Security Services (OPSS), Audit Services (IAU), and WebCenter Sites. Create the schemas with the Repository Creation Utility (RCU) as described in Creating the Required Schemas before the Upgrade.
4	Configure the WebCenter Sites domain.	Upgrade from 11g to 12c is an out-of-place upgrade. Therefore, configure the 12.2.1.1 WebCenter Sites domain by following the procedure described in Configuring the WebCenter Sites Domain
5	Configure the WebCenter Sites instance.	Configure a WebCenter Sites instance by completing the browser-based WebCenter Sites Configurator by following the procedure described in Configuring WebCenter Sites Instance.
6	Complete the post-configuration tasks.	The post-configuration tasks include configuring the 12.2.1.1 domain with LDAP-based or OAM-based authentication, verifying the directory structure, signing in and accessing the Sites UI, and restarting the managed servers. These tasks are listed in Post-Configuration Tasks.
7	Complete the pre-upgrade tasks.	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.
8	Upgrade the schemas.	Upgrade the schemas components that are available for upgrade with the Upgrade Assistant by following the procedure described in Upgrading the Schemas using the Upgrade Assistant.
9	Upgrade the domain configuration.	Upgrade all the configurations contained in your 11.1.1.8 domain with the Upgrade Assistant by following the procedure described in Upgrading the Configuration using the Upgrade Assistant.
10	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.
11	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.

6.2 Upgrading WebCenter Sites from 11g to 12c

The valid 11g starting point for upgrading WebCenter Sites to 12.2.1.1 is WebCenter Sites 11.1.1.8 and above. This is an out-of-place migration.

Note:

If you are upgrading from 11.1.1.6.x, you must upgrade to release 11.1.1.8 using WebCenter Sites 11g upgrade procedure documented in Fusion Middleware WebCenter Sites Upgrade Guide

To upgrade WebCenter Sites from 11g to 12c, complete the following tasks:

Installing Fusion Middleware Infrastructure
Installing Fusion Middleware Infrastructure creates an Oracle home directory and lays supporting software to install other Fusion Middleware products.
Installing WebCenter Sites 12.2.1.1.0 Distribution
Next, you must then install WebCenter Sites Release 12.2.1.1.0 on the target machine.
Creating the Required Schemas before the Upgrade
If you are upgrading from WebCenter Sites 11g, you must create the required 12c schemas before you begin the upgrade. The schemas required for WebCenter Sites are: Oracle Platform Security Services (OPSS), Audit Services (IAU), and WebCenter Sites.
Configuring the WebCenter Sites Domain
If you are upgrading from WebCenter Sites 11g to 12c, then you must configure the WebCenter Sites domain using the Configuration Wizard.
Configuring WebCenter Sites Instance
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.
Post-Configuration Tasks
After configuring the WebCenter Sites12c, complete the tasks listed in this topic.
Before Running the Upgrade Assistant
Before running the Upgrade Assistant to upgrade your 11.1.1.8.0 domain, complete the tasks listed in this topic.
Upgrading the Schemas using the Upgrade Assistant
You must upgrade the 11g schemas using the Upgrade Assistant.
Upgrading the Configuration using the Upgrade Assistant
You must upgrade the 11g domain configuration using the Upgrade Assistant.
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.

6.2.1 Installing Fusion Middleware Infrastructure

Installing Fusion Middleware Infrastructure creates an Oracle home directory and lays supporting software to install other Fusion Middleware products.

To install Fusion Middleware Infrastructure distribution:

Sign in to the target system where you want to install the 12.2.1.1 product distribution.
Download the Oracle Fusion Middleware Infrastructure distribution (fmw_12.2.1.1.0_infrastructure_generic.jar) from Oracle Technology Network or Oracle Software Delivery Cloud on your target system.
Change to the directory where you downloaded the 12.2.1.1 product distribution.
Start the installation program by entering the following command:
On UNIX operating system:

$JDK_HOME/bin/java [-d64] -jar fmw_12.2.1.1.0_infrastructure_generic.jar

Note:
Use the "-d64" flag only if you are using the HP-UX Itanium system.

On Windows operating system:

%JDK_HOME%\bin\java -jar fmw_12.2.1.1.0_infrastructure_generic.jar
On UNIX operating system, 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:
Installation Inventory Setup screen does not appear on Windows operating system.
On the Welcome screen, review the information to make sure that you have met all the prerequisites and click Next.
On the Auto Updates screen, select Skip Auto Updates and click Next.
- 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.
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 Selecting Directories for Installation and Configuration in Planning an Installation of Oracle Fusion Middleware.
On the Installation Type screen, select Fusion Middleware Infrastructure and click Next.

Note:
The topology in this document does not include server examples. Oracle strongly recommends that you do not install examples into a production environment.
The Prerequisite Checks screen analyzes the host computer to ensure that the specific operating system prerequisites have been met.
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, however this approach is not recommended.
On the Security Updates screen, enter your My Oracle Support account information so you can receive the latest product information and security updates via your My Oracle Support account.
This screen appears the first time you install an Oracle product on a host.

If you do not have an Oracle Support account and you are sure that you want to skip this step, clear the check box and verify your selection in the follow-up dialog box.
On the Installation Summary screen, verify the installation options you selected.
To save these options to a response file, click Save Response File and enter the location and the name of the response file. You can use response files for silent installation. Click Install.
On the Installation Progress screen, click Next when the progress bar displays 100%.
The Installation Complete screen displays the Installation Location and the Feature Sets that are installed. Review this information on this screen and click Finish to close the installer.

6.2.2 Installing WebCenter Sites 12.2.1.1.0 Distribution

Next, you must then install WebCenter Sites Release 12.2.1.1.0 on the target machine.

To install WebCenter Sites:

Sign in to the target system where you want to install the 12.2.1.1 product distribution.
Download the Oracle Fusion Middleware WebCenter Sites distribution (fmw_12.2.1.1.0_wcsites_generic.jar) from Oracle Technology Network or Oracle Software Delivery Cloud on your target system.
Change to the directory where you downloaded the 12.2.1.1 product distribution.
Start the installation program by entering the following command:
On UNIX operating system:

$JDK_HOME/bin/java [-d64] -jar <distribution_file_name>.jar

Note:
Use the "-d64" flag only if you are using the HP-UX Itanium system.

On Windows operating system:

%JDK_HOME%\bin\java -jar <distribution_file_name>.jar
On UNIX operating system, 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:
Installation Inventory Setup screen does not appear on Windows operating system.
On the Welcome screen, review the information to make sure that you have met all the prerequisites and click Next.
On the Auto Updates screen, select Skip Auto Updates and click Next.
- 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.
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 Selecting Directories for Installation and Configuration in Planning an Installation of Oracle Fusion Middleware.
On the Installation Type screen, select WebCenter Sites and click Next.
The Prerequisite Checks screen analyzes the host computer to ensure that the specific operating system prerequisites have been met.
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, however this approach is not recommended.
On the Installation Summary screen, verify the installation options you selected.
To save these options to a response file, click Save Response File and enter the location and the name of the response file. You can use response files for silent installation. Click Install.
On the Installation Progress screen, click Next when the progress bar displays 100%.
The Installation Complete screen displays the Installation Location and the Feature Sets that are installed. Review this information on this screen and click Finish to close the installer.

6.2.3 Creating the Required Schemas before the Upgrade

If you are upgrading from WebCenter Sites 11g, you must create the required 12c schemas before you begin the upgrade. The schemas required for WebCenter Sites are: Oracle Platform Security Services (OPSS), Audit Services (IAU), and WebCenter Sites.

Note:

This procedure assumes that you are a SYS or SYSDBA user with full database administrator privileges. If you are a user with limited database privileges, follow the procedure stated in Creating Schemas as a User With Limited Database Privileges. For in-depth information about using RCU, see Creating Schemas with the Repository Creation Utility.

To create the 12c schema:

Change directory to the following:
On UNIX operating system:

$ORACLE_HOME/oracle_common/bin

On Windows operating system:

%ORACLE_HOME%\oracle_common\bin
Run the RCU by entering the following command:
On UNIX operating system:

./rcu

On Windows operating system:

rcu.bat
On the Welcome screen, click Next.
On the Create Repository screen, select Create Repository and then select System Load and Product Load. Click Next.
If you do not have DBA privleges, select Prepare Scripts for System Load.

On the Database Connection Details screen, select the Database Type and enter the following details:

Table 6-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 6-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 6-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.
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 6-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 db2admin.
Password	Enter the password for your database user.

If the prerequisite check is successful, click OK to continue to the next page. If the check fails, review the details you entered and try again.

On the Select Components screen, select Create new prefix and enter the same prefix as the 11g schema.
The custom prefix is used to logically group these schemas together for use in this domain.
Select the following component schemas:
- Oracle Platform Security Services
- Audit Services
- Audit Services Append
- Audit Services Viewer
- WebCenter Sites
- WebCenter Sites—Visitor Services
The Configuration Wizard automatically creates the Common Infrastructure Services schema. This schema is grayed out; you cannot select or deselect it. This schema enables you to retrieve information from RCU during domain configuration.
On the Checking Prerequisites dialog box, verify that the prerequisites checking is successful. Click OK to go to the next page.
On the Schema Passwords screen, specify the passwords for your schema owners.
You must remember the passwords you enter on this screen; you need this information while configuring your product installation. Oracle recommends that you note these values.
On the Map Tablespaces screen, configure the desired tablespace mapping for the schemas you want to create.
When you click Next, a separate dialog window appears asking you to confirm that you want to create these tablespaces. Click OK to proceed and dismiss the dialog window.

A second dialog window appears showing the progress of tablespace creation. After this is complete, click OK to dismiss this window and go to the next screen.

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 RCU. Select the Encrypt Tablespace check box on the Map Tablespaces screen to encrypt all new tablespaces that RCU creates.
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. You can click on the name of a particular log file to view the contents of that file.
Review the information on the Completion Summary screen to verify that the operation is completed successfully. Click Close to complete the schema creation and dismiss RCU.

Which schemas should I create?

Determining Which Schemas to Create

What is system load and product load?

Understanding System Load and Product Load

What are Custom Prefixes?

Understanding Custom Prefixes

Planning Schema Creation:

Planning Your Schema Creation

6.2.4 Configuring the WebCenter Sites Domain

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

To configure the WebCenter Sites domain:

Change directory to the following:
On UNIX operating system:

ORACLE_HOME/oracle_common/common/bin

On Windows operating system:

ORACLE_HOME\oracle_common\common\bin
Start the configuration wizard by entering the following command:
On UNIX operating system:

./config.sh

On Windows operating system:

config.cmd
On the Configuration Type screen, select Create a new domain and click Next .
In the Domain Location field, specify your 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 Understanding Oracle Fusion Middleware.
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.1.0 [wcsites]
- Oracle JRF - 12.2.1.1.0 [oracle_common]
- Oracle Enterprise Manager - 12.2.1.1.0 [em]
- WebLogic Coherence Cluster Extension - 12 2.1.1.0 [wlserver]
Click Next.
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 Understanding Oracle Fusion Middleware.

Click Next.
On the Administrator Account screen, specify the user name and password you provided for the 11.1.1.8.0 WebCenter Sites domain click Next.
These account details are used to boot and connect to the WebCenter Sites domain’s Administrator Server.
On the Domain Mode and JDK screen, select Production and Oracle HotSpot JDK from the Domain Mode and JDK sections respectively and click Next.

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 6-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.

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

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 6-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.

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

For more information, click Help.

Note:
You can also create clusters using Enterprise Manager Fusion Middleware Control.
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.
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.
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.
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.
On the Virtual Targets screen, click Next.
On the Partitions screen, click Next.
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.
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.
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.

Note:

For IBM DB2, WebCenter Sites does not support the default data source created by the Fusion Middleware Configuration Wizard. To create new data source with a driver that DB2 supports:

Add the IBM DB2 Driver JAR files to the class path for the WebCenter Sites domain:
1. Stop the WebLogic Server Administration Server.
2. Copy the db2jcc.jar and db2jcc_license_cu.jar files from DB2 to a location that you can add to the domain class path.
3. Edit DOMAIN_HOME/bin/setDomainEnv.sh and add the following line after # ADD EXTENSIONS TO CLASSPATHS:
  
  PRE_CLASSPATH="path_to_db2jcc.jar:path_to_db2jcc_license_cu.jar:${PRE_CLASSPATH}"
4. Start the Administration Server.
Create a new data source using the preceding DB2 driver.

6.2.5 Configuring WebCenter Sites Instance

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.

6.2.5.1 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.

Before configuring WebCenter Sites, make sure these prerequisite tasks are done:

Grant read, write, and delete permissions for accessing the Oracle Platform Security Services credential store to ORACLE_HOME/wcsites/wcsites_common/lib/sites-security.jar by executing the following script:
- On UNIX operating system:
  
  $DOMAIN_HOME/wcsites/bin/grant-opss-permission.sh
- On Windows operating system:
  
  $DOMAIN_HOME\wcsites\bin\grant-opss-permission.bat
Use the WebLogic Server Administrator user name and password, when prompted by the script.

If a domain home other than the default (ORACLE_HOME/user_projects/domains/domain_name) was specified in the Fusion Middleware Configuration Wizard, make sure grant-opss-permission.sh or grant-opss-permission.bat contains the specified domain name before running it. If necessary, edit the file and update the domain name.
In the WebCenter Sites config directory, modify the files cs-cache.xml, ss-cache.xml, linked-cache.xml, and cas-cache.xml as follows:
1. Locate the following section:
  <cacheManagerPeerProviderFactory class="net.sf.ehcache.distribution.RMICacheManagerPeerProviderFactory" properties="peerDiscovery=automatic, multicastGroupAddress=230.0.0.0, multicastGroupPort=4444, timeToLive=0" />
2. Change the value of the peerDiscovery property to manual.
3. Save and close the file.
4. Start the WebCenter Sites Managed Server.

6.2.5.2 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.

However, if you are upgrading to WebCenter Sites from 11g, then specify the Admin user account same as the 11g Admin user credentials.

Note:

If you are configuring WebCenter Sites over a slow network, increase the setting of the StuckThreadMaxTime property to 1000 seconds per thread before starting the WebCenter Sites Configurator. The default value is 600 seconds.

In certain environments that potentially have network-related issues, the sample sites import process could take more than 600 seconds per thread during the WebCenter Sites configuration setup process. This can cause the import process or install to fail, and multiple exceptions in the log file. Oracle recommends increasing the setting to 1000 seconds to complete a successful installation of the sample sites.

To change the value of StuckThreadMaxTime, in the WebLogic Server Administration Console for the domain, go to Servers -> wcsites_server1 -> Configuration -> Tuning.

To run the browser-based WebCenter Sites Configurator after the corresponding WebLogic domain has been successfully set up:

(Optional) To run the Configurator in silent mode:
1. Edit the DOMAIN_HOME/wcsites/wcsites/config/wcs_properties_bootstrap.ini file, and complete the inline instructions.
2. Start the WebCenter Sites Managed Server.
3. Initiate the WebCenter Sites configuration process with the following command:
  - On UNIX operating systems: xdg-open http://sites-host:sites-port/sites/sitesconfig
  - On Windows operating systems: start http://sites-host:sites-port/sites/sitesconfig
To configure WebCenter Sites over a web server, increase the web server timeout value to 300 sec before starting the WebCenter Sites configuration.

(Optional) Set the values of the following properties as appropriate for your environment, using the Property Management Tool in the Admin interface. Set these properties for a cluster that uses the NIO database-based file system. If you would like files stored in locations other than the default (individual folders under DOMAIN_HOME/wcsites/wcsites/config), specify the locations as property values because they cannot be changed once WebCenter Sites is up and running.

Properties	Description
`xcelerate.transformpath`	Directory where Microsoft Word files are stored before WebCenter Sites transforms those files into assets.
`cs.pgcachefolder`	Deprecated. Only set if instructed to do so by Oracle Support.
`cs.xmlfolder`	Working directory for HTML rendering.
`cs.pgexportfolder`	Base export directory for the HTML files that are created when assets are published with the Export to Disk delivery type.
`vis.path`	Directory where WebCenter Sites is installed. You must include the trailing slash.
`mwb.path`	Directory where WebCenter Sites is installed. You must include the trailing slash.
`contentserver.installation.folder`	Directory where WebCenter Sites is installed. You must include the trailing slash. Applies to installations in which Satellite Server and WebCenter Sites are running in the same web application and must therefore share the user's session. Specifying this enables Satellite Server to access WebCenter Sites resources.
`cs.csdtfolder`	Directory where WebCenter Sites Developer Tools imports are stored.

For more information on the preceding properties, see Property Files Reference for Oracle WebCenter Sites.

Start the Managed Server for the WebCenter Sites primary cluster node.
In a web browser, access this URL: http://sites-host:sites-port/sites/sitesconfigsetup.
On the WebCenter Sites Configurator screen, click Begin.
On the Database Parameters screen, specify the JNDI Datasource name for the WebCenter Sites database repository This must be the repository you created using the Repository Creation Utility while setting up the WebLogic domain.
On the Web Application Parameters screen, select Yes if you are installing over a secure connection, leave all the parameters at their default (prepopulated) values, and click Next.
On the CAS Deployment Information screen, leave all parameters at their default (prepopulated) values and click Next. If using a cluster and a front-end web server for load balancing, adjust these values as appropriate for your environment.
On the WebCenter Sites Administrator Accounts screen, specify the credentials you want, and then click Next.
(Optional) If you chose the WebCenter Sites with Examples installation option when installing WebCenter Sites, the Sample Sites screen appears. On this screen, select the desired sample sites and click Next.
On the Configuration Summary screen, click Test and verify that all tests are successful. Then click Start and wait for the configuration process to complete.
Restart the Managed Server for the WebCenter Sites application.
Verify that WebCenter Sites is up and running by accessing the following URL in a web browser and logging in: http://sites-host:sites-port/sites.

Note:

The default location for cas.log is DOMAIN_HOME/servers/wcsites_server1/logs/.

To get XMLPost and Bulkloader up and running, set the following directories in the CLASSPATH environment variable:

ORACLE_HOME\wcsites\webcentersites\sites-home\lib\*
ORACLE_HOME\oracle_common\modules\clients\*

For information about how to configure additional cluster nodes, see Setting Up a Cluster.

For information about how to configure an external LDAP authentication provider, see Switching to Authentication Against an LDAP Directory.

For information about how to configure Oracle Access Manager integration, see Switching to Authentication Against Oracle Access Manager.

For information about how to use the WebCenter Sites Configuration Import/Export Utility, see Using the Property Management Tool in Property Files Reference for Oracle WebCenter Sites.

6.2.6 Post-Configuration Tasks

After configuring the WebCenter Sites12c, complete the tasks listed in this topic.

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.1 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.
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.
Sign in to the Sites UI using your Administrator credentials.
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 configure WebCenter Sites for authentication against Oracle Access Manager. This is a recommended solution for production environments.

6.2.6.1 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.

Before you change your authentication provider, install and configure WebCenter Sites.

To switch WebCenter Sites to authentication against an external LDAP directory:

(Optional) If your LDAP directory is case-sensitive, set the ldap.caseAware property in the DOMAIN_HOME/wcsites/wcsites/config/wcs_properties.json file to true.
Access the LDAP Configurator at http://sites-host:sites-port/sites-context/ldapconfig, follow the instructions on the screen, and enter the values for your environment.
For LDAP rollback, restart the WebCenter Sites Managed Server, and go to the same LDAP Configurator URL.

Now there is only manual LDAP integration. Nothing is written to your LDAP Server, only an LDIF file is created under the DOMAIN_HOME/wcsites/wcsites/config/ldap folder. The peopleparent, groupparent, username, and other fields are not prepopulated, as in the previous release.

Modify the LDIF file located in DOMAIN_HOME/wcsites/wcsites/config/ with values appropriate for your environment.

Because the fields are not prepopulated, follow this example for ORACLEDIR :

ldap server type -- ORACLEDIR
ldap DSN -- dc=oracle,dc=com
ldap host -- localhost
ldap port -- 389
ldap username -- cn=orcladmin
ldap password -- password
ldap peopleParent -- cn=Users,dc=oracle,dc=com
ldap groupparent -- cn=Groups,dc=oracle,dc=com

If the LDAP server you are using is case sensitive, edit the property file DOMAIN_HOME/wcsites/wcsites/config/wcs_properties.json, and change the ldap.caseAware property value to true.

By default the value of ldap.caseAware is set to false. Log in will fail if you are using a case-sensitive LDAP server and this property is set to false.

Note:
During the integration of Sites with LDAP, if the users data in LDAP is separated by a comma the data does not get fetched. for example: test,user. To retrieve the data, you need to change the syntax in the dir.ini file located at ..sites/install directory from "syntax.escape=\\ to syntax.escape=\#".
If you choose Oracle Virtual Directory as your LDAP authentication provider, WebCenter Sites generates an LDIF file, which you can import to your Oracle Internet Directory server and then create an adaptar in Oracle Virtual Directory to connect to the Oracle Internet Directory server.

You cannot import an LDIF file directly to an Oracle Virtual Directory LDAP server because it does not have a storage of its own.
Import the LDIF file into the external LDAP authentication provider.
Restart the WebLogic Managed Server running this WebCenter Sites instance.

6.2.6.2 Switching to Authentication Against Oracle Access Manager

You can configure WebCenter Sites for authentication against Oracle Access Manager. This is a recommended solution for production environments.

WebCenter Sites integration is supported for Oracle Access Manager 11.1.2.2.0 and 11.1.2.3.0.

To switch WebCenter Sites to authentication against Oracle Access Manager:

Deploy the oamlogin.war and oamtoken.war application files located under ORACLE_HOME/wcsites/webcentersites/sites-home on the WebLogic domain containing the target WebCenter Sites instance.
Create the following property file: DOMAIN_HOME/wcsites/wcsites/config/wemsites_settings.properties.

Populate the wemsites_settings.properties file as follows.

Elements	Properties
`oamredirect`	`http://oam_server_host:oam_port/oam/server/auth_cred_submit`
`oamlogout`	`oamlogout=http://oam_server_host:oam_port/oam/server/logout`
`forgotpassword`	`helpdesk-email-address`

Set following properties in DOMAIN_HOME/wcsites/wcsites/config/SSOConfig.xml.

Elements	Properties
`serviceUrl`	`http://{ohs_server_host}:{ohs_port}/{sites_context_root}/REST`
`ticketUrl`	`http://{oamtoken_server_host}:{`oamtoken_port}/oamtoken
`signoutURL`	`http://{oam_server_host}:{oam_port}/oam/server/logout?end_url={end_url}` Use this URL when invoking WebCenter Sites logout. It includes the encoded URL where the browser will return after all logout processing has been completed by Oracle Access Manager.
`end_url`	For test (staging) environments: `http%3A%2F%2F{ohs_server_host}%3A{ohs_port}%2F{sites_context_root}%2Fwem%2Ffatwire%2Fwem%2FWelcome` For production (delivery) environments: `http%3A%2F%2F{ohs_server_host}%3A{ohs_port}%2F{sites_context_root}%2FXcelerate%2FLoginPage.html`
`dbUsername`	Name of the WebCenter Sites general Administrator user account.
`dbPassword`	Password for the WebCenter Sites general Administrator user account.
`trustConfigured`	Indicates to WebCenter Sites whether a trust relationship has been established between the WebCenter Sites Managed Server and the Oracle HTTP Server WebGate in Oracle Access Management. A trust relationship between the two eliminates the need to include an identity assertion in every request. Set to `true` if a trust relationship exists; otherwise, set to `false`.

Copy the obAccsessClient.xml and cwallet.sso files from your Oracle Access Manager instance into the DOMAIN_HOME/wcsites/wcsites/config/oblix/lib/ directory on the target WebCenter Sites instance.
Edit the oamtoken.xml file in the sites-config directory by setting the compatibility mode and oblix path. The compatibility mode should be set to 11G and the oblix path to the sites-config folder under which you have the oblix/lib folder.

In the Oracle Access Manager configuration for WebCenter Sites, update the protected, public, and excluded resources for as follows:

###########################
protected_uris
###########################
/oamlogin/test
/sites/Xcelerate/LoginPage.html
/sites/Satellite/.../*
/sites/faces/jspx/.../*
/sites/wem/fatwire/.../*
/sites/ContentServer/.../*
/sites/wem/fatwire/wem/Welcome
/console

###########################
Exclusion Scheme        OraDefaultExclusionAuthNScheme
/sites/REST
/index.html
/oamlogin/oamsso/.../*
/sites/wem/fatwire/home
/sites/**

For more information, see Updating the Protected, Public, and Excluded Resources for an Enterprise Deployment.

To integrate the OAMSDK Client with Weblogic Server as the oamtoken.war application, edit the jps-config.xml file for the WebCenter Sites domain. By default, the WebLogic domain runs with this file, which is part of the WebLogic Server 12 c startup script:

-Doracle.security.jps.config=ORACLE_HOME/user_projects/domains/DOMAIN_NAME/config/fmwconfig/jps-config.xml
1. Add a service instance, as the following example shows, next to existing service instances in the existing jsp-config.xml file:
  <serviceInstance name="credstore.oamtoken" provider="credstoressp" location="./oamtoken">
  
  <description>File Based Credential Store Service Instance</description>
  
  <property name="location" value="./oamtoken"/>
  
  </serviceInstance>
  
  location is the path to the directory that contains the cwallet.sso file. The preceding example sets this path with reference to the current jsp-config.xml file. Make sure the omtoken folder is created with respect to the current directory and the cwallet.sso file is placed there. The location value can also be an absolute path to where the cwallet.sso file is placed
2. Add <serviceInstanceRef ref="credstore.oamtoken"/> under <jpsContext name="default">.
3. Add following <jpsContext> element under <jpsContexts default="default">:
  <jpsContext name="OAMASDK">
  
  <serviceInstanceRef ref="credstore.oamtoken"/>
  
  </jpsContext>
Add permissions so that code in oamtoken.war can be used.
The WebGate instance created in Oracle Access Manager is accessed by the client. You need to add the credential to the WebCenter Sites domain so that the security restriction can be taken care of.
1. Launch the WebLogic Scripting Tool with the wlst.sh script:
  cd ORACLE_HOME/oracle_common/common/bin/./wlst.sh
2. Connect to the Administration Server for the WebCenter Sites domain:
  connect('user-name','password','sites-host:admin-port')
3. Grant the permissions:
  grantPermission(codeBaseURL="file:/scratch/idc/newoam/rend/Oracle_Home/user_projects/domains/renddomain/servers/wcsites_server1/tmp/_WL_user/oamtoken/-", permClass="oracle.security.jps.service.credstore.CredentialAccessPermission",permTarget="context=SYSTEM,mapName=OAMAgent,keyName=*",permActions="*")
  
  The preceding path is basically the path where WebLogic Server has deployed the oamtoken.war application.
4. Restart the target WebCenter Sites Managed Server.
(Optional) If trust between WebCenter Sites and Oracle Access Manager has not been established, modify the configuration of the WebCenter Sites web tier as follows:
1. Log in to the Oracle Access Manager Console.
2. In the WebGate authorization policy (under the protected resource policy), go to the Responses tab.
3. Enable (select) the Identity Assertion check box.
4. Click Apply to save your changes.

(Optional) If WebCenterSites is deployed on a cluster is using OAM Integration. Following steps are required to be replicated on oamticketcache cache.

In the config directory, we have cas-cache.xml where oamticketcache is configured by default.

Uncomment the commented section in the cache named oamticketcache the section appear as:

<cacheEventListenerFactory
class="net.sf.ehcache.distribution.RMICacheReplicatorFactory"  
properties="replicateAsynchronously=true, replicatePuts=true,
replicateUpdates=true,
        replicateUpdatesViaCopy=false, replicateRemovals=true"/>
<bootstrapCacheLoaderFactory 
class="net.sf.ehcache.distribution.RMIBootstrapCacheLoaderFactory"
                properties="bootstrapAsynchronously=false,
                        maximumChunkSizeBytes=5000000"
                propertySeparator="," />

Change the cacheManagerPeerProviderFactory as follows, make sure port is unique.

<cacheManagerPeerProviderFactory
class="net.sf.ehcache.distribution.RMICacheManagerPeerProviderFactory"
        properties="peerDiscovery=automatic,
multicastGroupAddress=230.0.0.8,
                multicastGroupPort=40002, timeToLive=1" />

The port should be different for cacheManagerPeerProviderFactory and cacheManagerPeerListenerFactory as specified in the earlier steps.
All the cluster nodes should have same port for both the properties.

Restart the WebLogic Managed Server hosting this WebCenter Sites instance.

6.2.6.2.1 Integrating Site-Capture with Oracle Access Manager

To ingrate Site-Capite with OAM perform the following steps:

Configure the Protected Resource Policy:
1. Click Application Domains and click Open.
2. Click Search>WCSitesWebGate, and Authentication Policies tab.
3. Click Protected Resource Policy.
  For Authentication Scheme, select LDAPWemScheme. Make sure that the authentication scheme is created previously .
4. Click Responses tab.
5. Select Identity Assertion option.
6. When an Authentication policy is accepted, it creates the responses. The responses are required by the WebCenter Sites HTTP filter to recognize LDAP attributes and provide information about the authenticated user. To create responses perform the following steps:
1. Click Add .
2. In the Name field, enter enter FATGATE_CSTIMEOUT.
3. For Type, select Header.
4. Enter 30 as Header Value.
To add Resources:
1. Click Application Domains.
2. Click Open.
3. Click Search.
4. Select WCSitesWebGate>Resources>Search and Create.
5. For Type, enter HTTP Host.
6. For Host Identifier enter WCSitesWebGate.
7. For Resource URL, enter /__admin/** .
8. For Protection Level, set it as Protected.
9. For Authentication Policy and Authorization Policy, select Protected Resource Policy.

6.2.7 Before Running the Upgrade Assistant

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

Before running the Upgrade Assistant:

If your existing Sites 11.1.1.8 environment is a clustered configuration, you can either upgrade the primary node to 12.2.1.1 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.
Shut down the source (11.1.1.8) and the target (12.2.1.1) Admin Server and Managed Server instances.
If the source (11.1.1.8) and target (12.2.1.1) 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
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.

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

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

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 Upgrade Assistant.
If you are a DB2 user, consider the following before starting the upgrade:
- Import the Sites 11.1.1.8.0 schema from source database to target database (where 12.2.1.1.0 Sites schema is setup) before initiating schema upgrade. For a detailed procedure, see Copying 11.1.1.8 Schema from a DB2 Source to a New Target Database.
- Import the DB2 database on the same machine to make sure that your existing Sites 11.1.1.8.0 runtime is not affected during upgrade process.
- Because the source schema and target schema reside on single DB instance, specify the target database instance details along with the schema details during the schema upgrade process.
Ensure that the 12.2.1.1 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.

Creating a Non-SYSDBA User to Run Upgrade Assistant
Oracle recommends that you create a non-SYSDBA user called FMW to run the Upgrade Assistant. The FMW 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.1 Sites schema is setup) before upgrading the schemas..

6.2.7.1 Creating a Non-SYSDBA User to Run Upgrade Assistant

Oracle recommends that you create a non-SYSDBA user called FMW to run the Upgrade Assistant. The FMW user has the privileges required to modify schemas, but does not have full administrator privileges.

SYSDBA is an administrative privilege, required to perform high-level administrative operations such as creating, starting up, shutting down, backing up, or recovering the database. The SYSDBA system privilege is for a fully empowered database administrator. When you connect with the SYSDBA privilege, you connect with a default schema and not with the schema that is generally associated with your user name. For SYSDBA, this schema is SYS. Access to a default schema can be a very powerful privilege. For example, when you connect as user SYS, you have unlimited privileges on data dictionary tables. Therefore, Oracle recommends that you create a Non-SYSDBA user to upgrade the schemas. The privileges listed in this topic must be granted before starting the Upgrade Assistant.

Note:

The v$xatrans$ table does not exist by default. You must run the XAVIEW.SQL script to create this table before creating the user. Moreover, grant on v$xatrans$ table is required only for Oracle Identity Manager. If you do not require Oracle Identity Manager for configuration or if you do not have the v$xatrans$ table, then remove the following line from the script:

   grant select on v$xatrans$ to FMW with grant option;

In the example below, welcome1 is the password. Make sure that you specify your actual password when granting privileges.

create user FMW identified by welcome1;
grant dba to FMW;
grant execute on DBMS_LOB to FMW with grant option;
grant execute on DBMS_OUTPUT to FMW with grant option;
grant execute on DBMS_STATS to FMW with grant option;
grant execute on sys.dbms_aqadm to FMW with grant option;
grant execute on sys.dbms_aqin to FMW with grant option;
grant execute on sys.dbms_aqjms to FMW with grant option;
grant execute on sys.dbms_aq to FMW with grant option;
grant execute on utl_file to FMW with grant option;
grant execute on dbms_lock to FMW with grant option;
grant select on sys.V_$INSTANCE to FMW with grant option;
grant select on sys.GV_$INSTANCE to FMW with grant option;
grant select on sys.V_$SESSION to FMW with grant option;
grant select on sys.GV_$SESSION to FMW with grant option;
grant select on dba_scheduler_jobs to FMW with grant option;
grant select on dba_scheduler_job_run_details to FMW with grant option;
grant select on dba_scheduler_running_jobs to FMW with grant option;
grant select on dba_aq_agents to FMW with grant option;
grant execute on sys.DBMS_SHARED_POOL to FMW with grant option;
grant select on dba_2pc_pending to FMW with grant option;
grant select on dba_pending_transactions to FMW with grant option;
grant execute on DBMS_FLASHBACK to FMW with grant option;
grant execute on dbms_crypto to FMW with grant option;
grant execute on DBMS_REPUTIL to FMW with grant option;
grant execute on dbms_job to FMW with grant option;
grant select on pending_trans$ to FMW with grant option;
grant select on dba_scheduler_job_classes to fmw with grant option;
grant select on SYS.DBA_DATA_FILES to FMW with grant option;
grant select on SYS.V_$ASM_DISKGROUP to FMW with grant option;
grant select on v$xatrans$ to FMW with grant option;
grant execute on sys.dbms_system to FMW with grant option;
grant execute on DBMS_SCHEDULER to FMW with grant option;
grant select on dba_data_files to FMW with grant option;
grant execute on UTL_RAW to FMW with grant option;
grant execute on DBMS_XMLDOM to FMW with grant option;
grant execute on DBMS_APPLICATION_INFO to FMW with grant option;
grant execute on DBMS_UTILITY to FMW with grant option;
grant execute on DBMS_SESSION to FMW with grant option;
grant execute on DBMS_METADATA to FMW with grant option;
grant execute on DBMS_XMLGEN to FMW with grant option;
grant execute on DBMS_DATAPUMP to FMW with grant option;
grant execute on DBMS_MVIEW to FMW with grant option;
grant select on ALL_ENCRYPTED_COLUMNS to FMW with grant option;
grant select on dba_queue_subscribers to FMW with grant option; 
grant execute on SYS.DBMS_ASSERT to FMW with grant option;

Note:

Oracle Database 11.2.0.3 Database Users ONLY: You must apply Oracle Patch 13036331 before you begin the upgrade. Go to My Oracle Support to download the patch.

If you do not apply this patch, then you will have to grant additional privileges for some schemas.

6.2.7.2 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.1 Sites schema is setup) before upgrading the schemas..

Consider the following criteria to make sure that the import operation is successful:

Ensure the user performing the database import has the required privileges on the target database.
Set the APPLHEAPSZ of the target database to an appropriate value depending on your schema size.

To copy the Sites 11.1.1.8 schema from source database to target database:

Enter the following command from the location where you created the database directories:

$ db2move <old_db> COPY -sn <schemaname> -co TARGET_DB <targetDB> user <username> using <password>

Table 6-8 DatabaseMovement Command Parameters

Parameter	Description
db2move	Database movement tool command. It is used to move the tables within the DB2 database from the source system to the target system.
old_db	Specify the name of the database existing on the source system.
COPY	Indicates the database movement tool to perform a copy operation.
schemaname	Specify the schema name for the database existing on the source system.
targetDB	Specify the name of the target database.
username	Specify the user name.
password	Specify the password.

For example:

$ db2move dot8db COPY -sn dot8schema -co TARGET_DB 12cdb user dot8user using test1234

Verify that the copy operation is successful by performing the following steps:
1. Sign in to the DB2 console.
2. Connect to the new (target) database.
3. List and query the tables to make sure that data is copied properly.
Grant the necessary privileges for the DB_SITE (RCU 12c Sites user) before upgrading.

6.2.8 Upgrading the Schemas using the Upgrade Assistant

You must upgrade the 11g schemas using the Upgrade Assistant.

To upgrade the 11g schemas:

Run the Upgrade Assistant from the 12.2.1.1 Oracle home by entering the following command:
On UNIX operating system:

$Oracle_Home/oracle_common/upgrade/bin/ua

On Windows operating system:

%Oracle_Home%\oracle_common\upgrade\bin\ua.bat
The Welcome screen provides an overview of the Upgrade Assistant and some information about important pre-upgrade tasks. Click Next.
For more information about using the Upgrade Assistant, click Help on the Upgrade Assistant screen.
On the Selected Schemas screen, select Individually Selected Schemas and click Next.
The Upgrade Assistant identifies the components that are available for a schema upgrade thus allowing you to select the schemas you want to include in the upgrade.
The Available Components screen provides a list of installed Oracle Fusion Middleware components that have schemas that can be upgraded.
When you select a component, the schemas and any dependencies are automatically selected.

Select Oracle WebCenter Sites and click Next.
On the Prerequisites screen, acknowledge that the prerequisites have been met by checking all the check boxes. Click Next.

Note:
The Upgrade Assistant does not verify whether the prerequisites have been met.
On the WebCenter Sites Source Version screen, select 11.1.1.8.0 and click Next. This is the starting point of your upgrade.
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.
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: host_name:port/service_name.

Specify the user name with DBA privileges in the DBA User Name field. For example, sys as SYSDBA. 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.

If you are using Oracle database:
1. Enter the details of the 12c Schema for "WCSITES Schema" page.
2. Select the Schema user name from the drop-down list.
3. Enter password and proceed
4. Enter the details of the Sites 11.1.1.8.0 schema for "WCSITES_SOURCE Schema" page.
5. Update Schema user name and password for the Schema having 11.1.1.8.0 tables.
If you are using SQL Server:
1. Enter the details of the 12c Schema for "WCSITES Schema" page.
2. Select the Schema user name in the drop-down list. Only the RCU created WebCenter Sites Schemas will be listed in the drop-down list.
3. Enter password and proceed.
4. Enter the details of the Sites 11.1.1.8.0 schema for "WCSITES_SOURCE Schema" page. You need to provide a dba user and the Sites User.
5. Enter the default prefix being used for the Schemas in Sites 11.1.1.8.0 in the "WCSITES SourceSchema prefix" page. For example, use "dbo" if that is the prefix.
The Examine screen displays the status of the Upgrade Assistant as it examines each component, verifying that the component is ready for upgrade. If the status is “Examine finished.”, click Upgrade.
If the examine phase fails, Oracle recommends that you cancel the upgrade by clicking No on the Examination Failure dialog box. Click View Log to see what caused the error and refer to Troubleshooting Your Upgrade 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 on 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.
On the Upgrade Summary screen, review the summary of the options you have selected by expanding the tree.
Review the Source Version and the Target Version to make sure that both the versions are correct before proceeding with the upgrade.

The response file collects and stores all the information that you have entered through the Upgrade Assistant's graphical user interface , and enables you to perform a silent upgrade at a later time. The silent upgrade performs exactly the same function that the Upgrade Assistant wizard 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 and provide the location and name of the response file.

Click Upgrade to start the upgrade process.
The Upgrade Progress screen shows the status of the upgrade process and the projected Target Version of the component after a successful upgrade. Click Next.

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.
If the schema upgrade is successful, a summary file is generated at the following location:
$ORACLE_HOME/oracle_common/upgrade/logs/wcsites_upgrade/schema/Source Version/Database Type/summary.txt

Where, Source Version is 11.1.1.8.0 in this case and Database Type is the database which you are using.

If the schema upgrade fails, you can review the logs for possible errors. The log file is generated at the following location:

$ORACLE_HOME/oracle_common/upgrade/logs

Click Close to close the Upgrade Assistant.

6.2.9 Upgrading the Configuration using the Upgrade Assistant

You must upgrade the 11g domain configuration using the Upgrade Assistant.

Note:

Readiness Check for the Configuration upgrade is not available for 11g starting point.

To upgrade the 11g domain:

Run the Upgrade Assistant from the 12.2.1.1 Oracle home by entering the following command:
On UNIX operating system:

$Oracle_Home/oracle_common/upgrade/bin/ua

On Windows operating system:

%Oracle_Home%\oracle_common\upgrade\bin\ua.bat
The Welcome screen provides an overview of the Upgrade Assistant and some information about important pre-upgrade tasks. Click Next.
For more information about using the Upgrade Assistant, click Help on the Upgrade Assistant screen.
On the All Configurations screen, select All Configurations Used by a Domain and specify the 11.1.1.8 domain location in the Domain Directory field by entering it directly or by clicking Browse to use a navigation tree to select a valid domain directory. Click Next.
On the Component List screen, verify that all the components you want to upgrade within a domain are listed 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.
On the Prerequisites screen, acknowledge that the prerequisites have been met by checking all the check boxes. Click Next.

Note:
The Upgrade Assistant does not verify whether the prerequisites have been met.
On the WebCenter Sites Source Version screen, select 11.1.1.8.0 and click Next. This is the starting point of your upgrade.
The WebCenter Sites Source Details screen is displayed if your source is a single-server environment.
On the WebCenter Sites Source Cluster Details screen, specify the complete path of the 11.1.1.8.0 Sites Install Directory and 11.1.1.8.0 Sites webApp location and click Upgrade.

You can also click Browse to select a particular directory using the navigation tree.
The WebCenter Sites Source Details screen is displayed if your source is a clustered environment.
Specify the Sites Install and Sites webApp directory for each node in the Sites Install and Sites webApp columns respectively.

You can also click Browse to select a particular directory using the navigation tree.

After specifying the 11.1.1.8.0 directories, click Upgrade.

Note:
The node names listed in the Upgrade Assistant are the names that you provided while registering the nodes in Cluster Node Management screen.
The Examine screen displays the status of the Upgrade Assistant as it examines each component, verifying that the component is ready for upgrade. If the status is “Examine finished.”, click Upgrade.
If the examine phase fails, Oracle recommends that you cancel the upgrade by clicking No on the Examination Failure dialog box. Click View Log to see what caused the error and refer to Troubleshooting Your Upgrade 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 on 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.
On the Upgrade Summary screen, review the summary of the options you have selected by expanding the tree.
Review the Source Version and the Target Version to make sure that both the versions are correct before proceeding with the upgrade.

The response file collects and stores all the information that you have entered through the Upgrade Assistant's graphical user interface , and enables you to perform a silent upgrade at a later time. The silent upgrade performs exactly the same function that the Upgrade Assistant wizard 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 and provide the location and name of the response file.

Click Upgrade to start the upgrade process.
The Upgrade Progress screen shows the status of the upgrade process and the projected Target Version of the component after a successful upgrade. Click Next.

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.
If the configuration upgrade is successful, summary files are generated at the following location:
$ORACLE_HOME/oracle_common/upgrade/logs/wcsites_upgrade/config/Source Version/

Where, Source Version is 11.1.1.8.0 in this case.

If the source (11.1.1.8.0) is a clustered environment, the summary details are generated for each cluster as follows:

$ORACLE_HOME/oracle_common/upgrade/logs/wcsites_upgrade/config/Source Version/$nodename
If the source (11.1.1.8.0) is a single-server environment, the following three summary files are generated:
- PropertyMigration_Summary.txt for Property Migration Summary
- HomeMigration_Summary.txt for Site Home Migration Summary
- SharedMigration_Summary.txt for Sites Shared Migration Summary
If the schema upgrade fails, you can review the logs for possible errors. The log file is generated at the following location:

$ORACLE_HOME/oracle_common/upgrade/logs

Click Close to close the Upgrade Assistant.

6.2.10 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:

The validation script is available at the following location:
$Oracle_Home/wcsites/plugins/upgrade/

On UNIX operating system, run the validation script by entering the following command:

./validation.sh

On Windows operating system, run the validation script by entering the following command:

validation.bat
When the validation check is complete, validation summary report: Validation.txt is generated. Save it at any location on your system.
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.1 domain.

Note:
If your source (11.1.1.8) environment is using Patch 12 or above, comparison report for web.xml displays Eloqua integration filters as product customizations. You can ignore this because the filters are available on the target (12.2.1.1) environment. You can also ignore the differences displayed for inipath parameter value under the context-parameter.

6.2.11 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.1:

Restore or re-deploy the custom settings from your existing environment to your 12.2.1.1 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.

Note:
WebCenter Sites 12c uses ODL logging framework and any custom Log4j log levels set on 11g environment are not migrated to ODL logging. You can reset these levels after the upgrade.
Start Administration Server and Managed Servers.
Reconfigure passwords for the publishing process.
1. Sign in to the Admin 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.
If you are upgrading from 11g deployment, assign the users to the Sites Apps.
1. Sign in to the AdminSite as an Administrator.
2. Go to WEB Admin under AdminSite.
  Click Apps. Then click Manage App under Admin App.
  
  Click Assign to Sites. Click Select Sites and then click Continue.
  
  Select Advanced User role and save the change.
3. Go to WEB Admin under AdminSite.
  Click Apps. Then click Manage App under Admin App.
  
  Click Assign to Sites. Click Select Sites and then click Continue.
  
  Select Sites User role and save the change.
4. Repeat this procedure to add other Apps to the users and to assign roles to that user.
If external WebRoots are configured, update WebRoots from Sites Admin user interface.
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-cahe.xml
- cas-cache.xml
- ss-cache.xml
- linked-cache.xml
- MobilityServices.xml
- Custom/RestResources.xml
- wcs_properties_bootstrap.ini
  
  Note:
  Lucene search indexes are re-enabled during the upgrade process. Search results in Contributor UI will likely be delayed until the indexes are completely rebuilt post upgrade process.
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.
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.
After WCC integration, reset the wcc.server.password in WCC Configuration to view all the mapped rules.

6.3 Understanding the WebCenter Sites Upgrade Process from a Previous 12c Release

This topic helps you to understand the process flow of the WebCenter Sites upgrade from a previous 12c release using a flowchart.

Figure 6-2 Flowchart for WebCenter Sites Upgrade Process from a Previous 12c Release

Description of "Figure 6-2 Flowchart for WebCenter Sites Upgrade Process from a Previous 12c Release"

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

Table 6-9 Roadmap for WebCenter Sites Upgrade Process from a Previous 12c Release

Step No.	Task	Description
1	Install the 12.2.1.1 Oracle Fusion Middleware Infrastructure.	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. Therefore, follow the procedure described in Installing Fusion Middleware Infrastructure.
2	Install the 12.2.1.1 Oracle WebCenter Sites distribution.	Install Oracle WebCenter Sites distribution as described in Installing WebCenter Sites 12.2.1.1.0 Distribution.
3	Shut down the Administration Server and the Managed Servers.	Before starting the upgrade process, shut down the Administration Server and the Managed Servers by following the procedure described in Shutting Down the Administration Server and the Managed Servers.
4	Back up your 12.2.1.0 environment.	It is important to back up your existing environment before the upgrade because the domain configurations are upgraded in-place. The back-up allows you to restore your pre-upgrade environment in case the upgrade fails or if the upgrade results are unsatisfactory. For a list of backup items, see Backing up the 12.2.1.0 Environment.
5	Reconfigure the 12.2.1.0 domain.	When you run the Reconfiguration Wizard on your existing domain, it prepares your domain for upgrade by selecting and applying the recongifuration templates. Reconfigure the domain by following the procedure described in Reconfiguring the WebCenter Sites Domain with the Reconfiguration Wizard.
6	Complete the pre-upgrade tasks.	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.
7	Upgrade the schemas.	Upgrade the schemas components that are available for upgrade with the Upgrade Assistant by following the procedure described in Upgrading the Schemas using the Upgrade Assistant.
8	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 the Configuration using the Upgrade Assistant.
9	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.
10	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.

6.4 Upgrading WebCenter Sites from a Previous 12c Release

The valid 12c starting point for upgrading WebCenter Sites to 12.2.1.1 is WebCenter Sites 12.2.1.0. This is an in-place upgrade.

Note:

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.

To upgrade WebCenter Sites 12.2.1.1 from a previous 12c release, complete the following tasks:

Installing Fusion Middleware Infrastructure
Installing Fusion Middleware Infrastructure creates an Oracle home directory and lays supporting software to install other Fusion Middleware products.
Installing WebCenter Sites 12.2.1.1.0 Distribution
Next, you must then install WebCenter Sites Release 12.2.1.1.0 on the target machine.
Shutting Down the Administration Server and the Managed Servers
You must shut down the Administration Server and the Managed Servers on your 12.2.1 system.
Backing up the 12.2.1.0 Environment
You must back up the WebLogic domain, Sites configuration directory, Sites shared directory, and Sites schema before starting the upgrade process.
Reconfiguring the WebCenter Sites Domain with the Reconfiguration Wizard
You must first reconfigure your 12.2.1.0 Sites domain using the Reconfiguration Wizard before running the Upgrade Assistant.
Before Running the Upgrade Assistant
Before running the Upgrade Assistant to upgrade your 12.2.1.0 domain, complete the tasks listed in this topic.
Upgrading the Schemas using the Upgrade Assistant
You must upgrade the 12.2.1.0 schemas using the Upgrade Assistant.
Upgrading the Configuration using the Upgrade Assistant
You must upgrade the 12.1.1.0.0 domain configuration using the Upgrade Assistant.
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.

6.4.1 Installing Fusion Middleware Infrastructure

Installing Fusion Middleware Infrastructure creates an Oracle home directory and lays supporting software to install other Fusion Middleware products.

To install Fusion Middleware Infrastructure distribution:

Sign in to the target system where you want to install the 12.2.1.1 product distribution.
Download the Oracle Fusion Middleware Infrastructure distribution (fmw_12.2.1.1.0_infrastructure_generic.jar) from Oracle Technology Network or Oracle Software Delivery Cloud on your target system.
Change to the directory where you downloaded the 12.2.1.1 product distribution.
Start the installation program by entering the following command:
On UNIX operating system:

$JDK_HOME/bin/java [-d64] -jar fmw_12.2.1.1.0_infrastructure_generic.jar

Note:
Use the "-d64" flag only if you are using the HP-UX Itanium system.

On Windows operating system:

%JDK_HOME%\bin\java -jar fmw_12.2.1.1.0_infrastructure_generic.jar
On UNIX operating system, 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:
Installation Inventory Setup screen does not appear on Windows operating system.
On the Welcome screen, review the information to make sure that you have met all the prerequisites and click Next.
On the Auto Updates screen, select Skip Auto Updates and click Next.
- 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.
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 Selecting Directories for Installation and Configuration in Planning an Installation of Oracle Fusion Middleware.
On the Installation Type screen, select Fusion Middleware Infrastructure and click Next.

Note:
The topology in this document does not include server examples. Oracle strongly recommends that you do not install examples into a production environment.
The Prerequisite Checks screen analyzes the host computer to ensure that the specific operating system prerequisites have been met.
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, however this approach is not recommended.
On the Security Updates screen, enter your My Oracle Support account information so you can receive the latest product information and security updates via your My Oracle Support account.
This screen appears the first time you install an Oracle product on a host.

If you do not have an Oracle Support account and you are sure that you want to skip this step, clear the check box and verify your selection in the follow-up dialog box.
On the Installation Summary screen, verify the installation options you selected.
To save these options to a response file, click Save Response File and enter the location and the name of the response file. You can use response files for silent installation. Click Install.
On the Installation Progress screen, click Next when the progress bar displays 100%.
The Installation Complete screen displays the Installation Location and the Feature Sets that are installed. Review this information on this screen and click Finish to close the installer.

6.4.2 Installing WebCenter Sites 12.2.1.1.0 Distribution

Next, you must then install WebCenter Sites Release 12.2.1.1.0 on the target machine.

To install WebCenter Sites:

Sign in to the target system where you want to install the 12.2.1.1 product distribution.
Download the Oracle Fusion Middleware WebCenter Sites distribution (fmw_12.2.1.1.0_wcsites_generic.jar) from Oracle Technology Network or Oracle Software Delivery Cloud on your target system.
Change to the directory where you downloaded the 12.2.1.1 product distribution.
Start the installation program by entering the following command:
On UNIX operating system:

$JDK_HOME/bin/java [-d64] -jar <distribution_file_name>.jar

Note:
Use the "-d64" flag only if you are using the HP-UX Itanium system.

On Windows operating system:

%JDK_HOME%\bin\java -jar <distribution_file_name>.jar
On UNIX operating system, 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:
Installation Inventory Setup screen does not appear on Windows operating system.
On the Welcome screen, review the information to make sure that you have met all the prerequisites and click Next.
On the Auto Updates screen, select Skip Auto Updates and click Next.
- 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.
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 Selecting Directories for Installation and Configuration in Planning an Installation of Oracle Fusion Middleware.
On the Installation Type screen, select WebCenter Sites and click Next.
The Prerequisite Checks screen analyzes the host computer to ensure that the specific operating system prerequisites have been met.
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, however this approach is not recommended.
On the Installation Summary screen, verify the installation options you selected.
To save these options to a response file, click Save Response File and enter the location and the name of the response file. You can use response files for silent installation. Click Install.
On the Installation Progress screen, click Next when the progress bar displays 100%.
The Installation Complete screen displays the Installation Location and the Feature Sets that are installed. Review this information on this screen and click Finish to close the installer.

6.4.3 Shutting Down the Administration Server and the Managed Servers

You must shut down the Administration Server and the Managed Servers on your 12.2.1 system.

To shut down the server instances:

Enter the following command to stop the Administration Server:
On UNIX operating system:

$DOMAIN_HOME/bin/stopWebLogic.sh username password [admin_url]

On Windows operating system:

$DOMAIN_HOME\bin\stopWebLogic.cmd username password [admin_url]
Enter the following command to stop the Managed Server:
On UNIX operating system:

$DOMAIN_HOME/bin/stopManagedWebLogic.sh managed_server_name admin_url

On Windows operating system:

$DOMAIN_HOME\bin\stopManagedWebLogic.cmd managed_server_name admin_url

When prompted, specify your user name and password.

6.4.4 Backing up the 12.2.1.0 Environment

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

6.4.5 Reconfiguring the WebCenter Sites Domain with the Reconfiguration Wizard

You must first reconfigure your 12.2.1.0 Sites domain using the Reconfiguration Wizard before running the Upgrade Assistant.

Note:

If the source is a clustered environment, run the Reconfiguration Wizard on the primary node only. Use the pack/unpack utility to apply the changes to other cluster members in the domain.

To reconfigure the domain:

Run the Reconfiguration Wizard by entering the following command:
On UNIX operating system:

$ORACLE_HOME/oracle_common/common/bin/reconfig.sh

On Windows operating system:

%ORACLE_HOME%\oracle_common\common\bin\reconfig.cmd

Note:
When you run the reconfig.cmd or reconfig.sh command, you can get the following error message 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 including the -Dpython.cachedir=valid_directory parameter in the command.

Oracle recommends that you specify the "log" option while starting the Reconfiguration Wizard as shown in the following example:

./reconfig.sh -log=/$ORACLE_HOME/logs/reconfig.log -log_priority=ALL

You can set the log_priority as per your requirements.
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.
The Reconfiguration Setup Progress screen shows 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.
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. 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.
On the Database Configuration Type screen, select RCU Data .
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.

If the check is successful, click Next. If the check fails, reenter the connection details correctly and try again.
On the JDBC Component Schema screen, verify that the DBMS/Service and the Host name is correct for each component schema and click Next.
For DB2, Populate the DBMS/Service and HostName for the WCSITES Component Schema in the 'Component Datasources' screen for reconfig.
On the JDBC Component Schema Test screen, select all the component schemas and click Test Selected Connections to test the connection for each schema.
When the check is complete, click Next.
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.
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.
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.
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 to indicate 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.

6.4.6 Before Running the Upgrade Assistant

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

Before running the Upgrade Assistant:

If the source is a clustered environment, pack the domain from primary node and unpack it on the secondary cluster members.
Replace the Sites config folder on the second node with the one from the primary node.

Update the following xml files located at $DOMAIN_HOME/wcsires/config/:

jbossTicketCacheReplicationConfig.xml:
Update the bind_addr property with a valid host or IP address for this cluster node.

Note:
Oracle recommends changing the multicastGroupPort value to a unique value greater than 2048. Ensure that the multicast port used injbossTicketCacheReplicationConfig.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 6-10 timeToLive Value Descriptions

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.

Grant permissions for the new Sites security jar by entering the following command:
$DOMAIN_HOME/wcsites/bin/grant-opss-permission
Restore your custom settings to the xml configuration files. For DB2:
1. Add the db2jcc.jar and db2jcc_license_cu.jar files back to the domain classpath.
2. Edit the setDomainEnv.sh file present at the following location using a text editor:
  $Domain_Home/bin
  
  Find the following text:
  
  # ADD EXTENSIONS TO CLASSPATHS
  
  Add the following line after # ADD EXTENSIONS TO CLASSPATHS:
  
  PRE_CLASSPATH="path_to_db2jcc.jar:path_to_db2jcc_license_cu.jar:${PRE_CLASSPATH}
Save the setDomainEnv.sh file.
Restore any customization performed to xml configuration files post reconfiguration process.

6.4.7 Upgrading the Schemas using the Upgrade Assistant

You must upgrade the 12.2.1.0 schemas using the Upgrade Assistant.

To upgrade the 12.2.1.0 schemas:

Run the Upgrade Assistant from the 12.2.1.1 Oracle home by entering the following command:
On UNIX operating system:

$Oracle_Home/oracle_common/upgrade/bin/ua

On Windows operating system:

%Oracle_Home%\oracle_common\upgrade\bin\ua.bat
The Welcome screen provides an overview of the Upgrade Assistant and some information about important pre-upgrade tasks. Click Next.
For more information about using the Upgrade Assistant, click Help on the Upgrade Assistant screen.
On the Selected Schemas screen, select Individually Selected Schemas and click Next.
The Upgrade Assistant identifies the components that are available for a schema upgrade thus allowing you to select the schemas you want to include in the upgrade.
The Available Components screen provides a list of installed Oracle Fusion Middleware components that have schemas that can be upgraded.
When you select a component, the schemas and any dependencies are automatically selected.

Select Oracle WebCenter Sites and click Next.
On the Prerequisites screen, acknowledge that the prerequisites have been met by checking all the check boxes. Click Next.

Note:
The Upgrade Assistant does not verify whether the prerequisites have been met.
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.
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.
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: host_name:port/service_name.

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.
The Examine screen displays the status of the Upgrade Assistant as it examines each component, verifying that the component is ready for upgrade. If the status is “Examine finished.”, click Upgrade.
If the examine phase fails, Oracle recommends that you cancel the upgrade by clicking No on the Examination Failure dialog box. Click View Log to see what caused the error and refer to Troubleshooting Your Upgrade 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 on 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.
On the Upgrade Summary screen, review the summary of the options you have selected by expanding the tree.
Review the Source Version and the Target Version to make sure that both the versions are correct before proceeding with the upgrade.

The response file collects and stores all the information that you have entered through the Upgrade Assistant's graphical user interface , and enables you to perform a silent upgrade at a later time. The silent upgrade performs exactly the same function that the Upgrade Assistant wizard 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 and provide the location and name of the response file.

Click Upgrade to start the upgrade process.
The Upgrade Progress screen shows the status of the upgrade process and the projected Target Version of the component after a successful upgrade. Click Next.

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.
If the schema upgrade is successful, a summary file is generated at the following location:
$ORACLE_HOME/oracle_common/upgrade/logs/wcsites_upgrade/schema/Source Version/Database Type/summary.txt

Where, Source Version is 12.2.1.1 in this case and Database Type is the database which you are using.

If the schema upgrade fails, you can review the logs for possible errors. The log file is generated at the following location:

$ORACLE_HOME/oracle_common/upgrade/logs

Click Close to close the Upgrade Assistant.

6.4.8 Upgrading the Configuration using the Upgrade Assistant

You must upgrade the 12.1.1.0.0 domain configuration using the Upgrade Assistant.

To upgrade the 12.2.1.1.0 domain:

Run the Upgrade Assistant from the 12.2.1.1 Oracle home by entering the following command:
On UNIX operating system:

$Oracle_Home/oracle_common/upgrade/bin/ua

On Windows operating system:

%Oracle_Home%\oracle_common\upgrade\bin\ua.bat
The Welcome screen provides an overview of the Upgrade Assistant and some information about important pre-upgrade tasks. Click Next.
For more information about using the Upgrade Assistant, click Help on the Upgrade Assistant screen.
On the All Configurations screen, select All Configurations Used by a Domain and specify the 12.2.1.0 domain location in the Domain Directory field by entering it directly or by clicking Browse to use a navigation tree to select a valid domain directory. Click Next.
On the Component List screen, verify that all the components you want to upgrade within a domain are listed 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.
On the Prerequisites screen, acknowledge that the prerequisites have been met by checking all the check boxes. Click Next.

Note:
The Upgrade Assistant does not verify whether the prerequisites have been met.
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.
The WebCenter Sites Source Details screen is displayed if your source is a single-server environment.
On the WebCenter Sites Source Cluster Details screen, specify the complete path of the 12.2.1.1.0 Sites Install Directory and 12.2.1.1.0 Sites webApp location and click Upgrade.

You can also click Browse to select a particular directory using the navigation tree.
The WebCenter Sites Source Details screen is displayed if your source is a clustered environment.
Specify the 12.2.1.1.0 Sites Install and 12.2.1.1.0 Sites webApp directory for each node in the Sites Install and Sites webApp columns respectively.

You can also click Browse to select a particular directory using the navigation tree.

After specifying the 12.2.1.1.0 directories, click Upgrade.

Note:
The node names listed in the Upgrade Assistant are the names that you provided while registering the nodes in Cluster Node Management screen.
The Examine screen displays the status of the Upgrade Assistant as it examines each component, verifying that the component is ready for upgrade. If the status is “Examine finished.”, click Upgrade.
If the examine phase fails, Oracle recommends that you cancel the upgrade by clicking No on the Examination Failure dialog box. Click View Log to see what caused the error and refer to Troubleshooting Your Upgrade 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 on 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.
On the Upgrade Summary screen, review the summary of the options you have selected by expanding the tree.
Review the Source Version and the Target Version to make sure that both the versions are correct before proceeding with the upgrade.

The response file collects and stores all the information that you have entered through the Upgrade Assistant's graphical user interface , and enables you to perform a silent upgrade at a later time. The silent upgrade performs exactly the same function that the Upgrade Assistant wizard 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 and provide the location and name of the response file.

Click Upgrade to start the upgrade process.
The Upgrade Progress screen shows the status of the upgrade process and the projected Target Version of the component after a successful upgrade. Click Next.

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.
If the configuration upgrade is successful, summary files are generated at the following location:
$ORACLE_HOME/oracle_common/upgrade/logs/wcsites_upgrade/config/Source Version/

Where, Source Version is 12.2.1.1.0 in this case.

If the source (12.2.1.1.0) is a clustered environment, the summary details are generated for each cluster as follows:

$ORACLE_HOME/oracle_common/upgrade/logs/wcsites_upgrade/config/Source Version/$nodename
If the source (12.2.1.1.0) is a single-server environment, the following three summary files are generated:
- PropertyMigration_Summary.txt for Property Migration Summary
- HomeMigration_Summary.txt for Site Home Migration Summary
- SharedMigration_Summary.txt for Sites Shared Migration Summary
If the schema upgrade fails, you can review the logs for possible errors. The log file is generated at the following location:

$ORACLE_HOME/oracle_common/upgrade/logs

Click Close to close the Upgrade Assistant.

6.4.9 Post-Upgrade Validation Tasks

To run the validation script:

The validation script is available at the following location:
$Oracle_Home/wcsites/plugins/upgrade/

On UNIX operating system, run the validation script by entering the following command:

./validation.sh

On Windows operating system, run the validation script by entering the following command:

validation.bat
When the validation check is complete, validation summary report: Validation.txt is generated. Save it at any location on your system.
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.1 domain.

Note:
If your source (11.1.1.8) environment is using Patch 12 or above, comparison report for web.xml displays Eloqua integration filters as product customizations. You can ignore this because the filters are available on the target (12.2.1.1) environment. You can also ignore the differences displayed for inipath parameter value under the context-parameter.

6.4.10 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.1:

Restore or re-deploy the custom settings from your existing environment to your 12.2.1.1 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.

Note:
WebCenter Sites 12c uses ODL logging framework and any custom Log4j log levels set on 11g environment are not migrated to ODL logging. You can reset these levels after the upgrade.
Start Administration Server and Managed Servers.
Reconfigure passwords for the publishing process.
1. Sign in to the Admin 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.
If you are upgrading from 11g deployment, assign the users to the Sites Apps.
1. Sign in to the AdminSite as an Administrator.
2. Go to WEB Admin under AdminSite.
  Click Apps. Then click Manage App under Admin App.
  
  Click Assign to Sites. Click Select Sites and then click Continue.
  
  Select Advanced User role and save the change.
3. Go to WEB Admin under AdminSite.
  Click Apps. Then click Manage App under Admin App.
  
  Click Assign to Sites. Click Select Sites and then click Continue.
  
  Select Sites User role and save the change.
4. Repeat this procedure to add other Apps to the users and to assign roles to that user.
If external WebRoots are configured, update WebRoots from Sites Admin user interface.
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-cahe.xml
- cas-cache.xml
- ss-cache.xml
- linked-cache.xml
- MobilityServices.xml
- Custom/RestResources.xml
- wcs_properties_bootstrap.ini
  
  Note:
  Lucene search indexes are re-enabled during the upgrade process. Search results in Contributor UI will likely be delayed until the indexes are completely rebuilt post upgrade process.
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.
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.
After WCC integration, reset the wcc.server.password in WCC Configuration to view all the mapped rules.

6.5 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 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.