This chapter contains the following sections:
The first step in the migrating process is to evaluate your current Oracle Fusion Middleware 11g Release 1 (11.1.1.1.0) environment. During the migration process, the topology of the deployment must not change, the port configuration must be retained, and there must be minimal changes in namespaces. All the changes in the namespaces are encapsulated by the properties in the patchMaster.properties file, which is included in the fmw11gR1ps1_patchassist.zip file.
For a list of products included in this patch set, see Section 3.7, "Oracle Fusion Middleware Components Supported by Patch Assistant".
This section discusses the following topics:
This section describes the general and product-specific prerequisites for running Patch Assistant.
This section discuss the following topics:
The following are the general prerequisites for running Patch Assistant:
Ensure that Oracle Fusion Middleware 11g Release 1 (11.1.1.1.0) is installed and configured.
Ensure that you install 11.1.1.2.0 on the same operating system used by the 11.1.1.1.0 installation.
Ensure that the system configuration meets the recommended system configuration described in your product documentation. For more information, see http://www.oracle.com/technology/software/products/ias/files/fusion_certification.html.
Ensure that you have Apache Ant 1.7.0 and Java JDKs (Java SE 6 1.6.0_11 and jrockit_160_05_R27.6.2-20), which are packaged with Oracle WebLogic Server.
Note:
If you are using Oracle Internet Directory, Oracle Virtual Directory, Oracle HTTP Server, or Oracle Web Cache as standalone Oracle Fusion Middleware installations, you must install and configure Apache Ant separately. For more information, see Installing Ant athttp://ant.apache.org/manual/installlist.html and Setting Up the Patch Assistant Environment.Make a detailed note of the topology used for the Oracle Fusion Middleware 11g Release 1 (11.1.1.1.0) installation.
Ensure that you do not change the port configuration and instance names in your existing Oracle Fusion Middleware 11g Release 1 (11.1.1.1.0) installation.
Ensure that the environment variables for tmp and temp directories for Microsoft Windows are set, as described in the Oracle Fusion Middleware Administrator's Guide.
Back up your Oracle software, inventory, schema, and domain before applying this patch set, or before making any other changes to your existing Oracle software. Refer to your product administrator's guide for instructions on backing up your Oracle software and inventory. For more information, see the "Advanced Administration: Backup and Recovery" part in the Oracle Fusion Middleware Administrator's Guide.
On Windows, it is recommended that you edit the patchMaster.properties file in a Notepad. If you are using any other text editor, such as Windows WordPad, then save the file as Text Document. Do not save the file in Rich Text Format.
On Windows, you must delete the service name for Oracle Fusion Middleware 11g Release 1 (11.1.1.1.0) before installing Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0) because both the installations use the same service name. To do so, run the following Ant task on the command line:
ant master-opmn-delete-service
Enter the required information when prompted by the Ant task.
Note:
If you want to abort the migration and revert to the 11.1.1.1.0 deployment, run the followingAnt task on the command line:
ant master-opmn-create-service
Heterogeneous nodes in a Cluster (one in 11.1.1.2.0, other in 11.1.1.2.0) is not supported during the migration process. You must migrate all nodes to 11.1.1.2.0 before environment can be used.
Depending on your Oracle Fusion Middleware component, you may have to meet additional prerequisites as follows:
For Oracle Fusion Middleware Audit Framework, the audit policy is configured for Java components in Oracle Fusion Middleware 11g Release 1 (11.1.1.1.0), you must export the configuration before running Patch Assistant, as follows:
Log in to Oracle Enterprise Manager 11g Fusion Middleware Control.
Expand WebLogic Domain on the left pane, and select your domain.
Your selected domain page is displayed.
From the WebLogic Domain, select Security, and then Audit Policy.
The Audit Policy page is displayed.
Select the Audit Policy, and click Export.
Save the AuditConfiguration file to your machine.
For the Oracle Directory Integration Platform, do the following:
Ensure that your Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0) Oracle Internet Directory is up and running in SSL No-Auth mode.
Extend the Oracle WebLogic domain created during the Oracle Internet Directory 11g Release 1 (11.1.1.2.0) installation, by running the following command:
Windows
config.cmd (Located at: ORACLE_HOME\bin)
UNIX
config.sh (Located at: ORACLE_HOME/bin)
The Oracle Fusion Middleware Configuration Wizard appears. Enter the Oracle Internet Directory 11g Release 1 (11.1.1.2.0) connection details and credentials.
Stop the Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0) domain.
Depending on your installation, complete the following prerequisites:
If your 11.1.1.1.0 configuration has Oracle Internet Directory and Oracle Virtual Directory created with a new Oracle WebLogic domain, then choose the Create a new WebLogic domain option on the Welcome screen of the Oracle Fusion Middleware Configuration Wizard when configuring the 11.1.1.2.0 domain.
During the configuration of 11.1.1.2.0, if you select the Create a new WebLogic domain option, then you must deselect Oracle Internet Directory and Oracle Virtual Directory, and select Oracle Directory Services Manager.
If your Oracle Internet Directory and Oracle Virtual Directory are not registered to any Oracle WebLogic domain in your 11.1.1.1.0 configuration, then 11.1.1.2.0 configuration is not required. You must set the property patchMaster.Oracleinstancenewlist in the patchMaster.properties file to a new directory for the instance. Ensure that you retain the same instance name used in 11.1.1.1.0.
If your 11.1.1.1.0 configuration has Oracle Internet Directory and Oracle Virtual Directory registered to an existing Oracle WebLogic domain, then 11.1.1.2.0 configuration is not required. You must set the property patchMaster.Oracleinstancenewlist in the patchMaster.properties file to a new directory and register the instance with the existing 11.1.1.2.0 WebLogic domain using Ant target. Ensure that you retain the same instance name used in 11.1.1.1.0.
To migrate Oracle WebCenter, you may choose either of these approaches:
Keep two parallel instances of Oracle WebCenter, that is 11.1.1.1.0 as well as 11.1.1.2.0. To do this, you must perform a complete installation of Oracle WebCenter 11.1.1.2.0. You can then migrate your Oracle WebCenter 11.1.1.1.0 data into the new WebCenter instance by using the export and import utilities. This approach enables you to use both instances of Oracle WebCenter, if required. For example, you may run the two instances in parallel to minimize downtime or to ensure that the 11.1.1.2.0 instance is set up to the same level as the 11.1.1.1.0 instance before you switch over to the 11.1.1.2.0 instance completely.
For information about how to install Oracle WebCenter, see the Oracle Fusion Middleware Installation Guide for Oracle WebCenter. For information about export and import utilities, see the "Managing Export, Import, Backup, and Recovery of WebCenter" chapter in the Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.
Migrate the Oracle WebCenter 11.1.1.1.0 repository and mid-tier completely to Oracle WebCenter 11.1.1.2.0. This approach preserves your Oracle WebCenter 11.1.1.1.0 repository data and enables you to reuse the repository.
This guide describes the tasks required to implement this migration approach for Oracle WebCenter.
You can download the fmw11gR1ps1_patchassist.zip, which is included in the Oracle Fusion Middleware 11g Release 1 Patch Set 1 Patch Scripts media. The zip file is available in the same media pack as Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0) on Oracle Technology Network (OTN) at the following URL: http://oracle.com/technology
After downloading this zip file, extract its contents to its own location, in your local machine, where the old and new Oracle Fusion Middleware components are installed. Ensure that the same operating system is used for the 11.1.1.1.0 and 11.1.1.2.0 installations. The zip file includes the following files:
README – Describes the environment.
patchMaster.properties - The user input file.
build.xml – The master build file. Each Oracle Fusion Middleware component has its own build.xml file.
To set up the Patch Assistant environment for Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0), you must set up ANT_HOME, add it to your PATH, set the JAVA_HOME and the permgen size.
For example, on Windows:
set ANT_HOME=MW_HOME\modules\org.apache.ant_1.7.0 set PATH=%PATH%;%ANT_HOME%\bin set JAVA_HOME=MW_HOME\jdk160_14_R27.6.4-18 set ANT_OPTS=-Xmx512M -XX:MaxPermSize=512m
For example, on UNIX:
setenv MW_HOME ##set mw home here## setenv ANT_HOME $MW_HOME/modules/org.apache.ant_1.7.0 setenv PATH $ANT_HOME/bin:$PATH setenv JAVA_HOME $MW_HOME/jdk160_14_R27.6.5-32 setenv ANT_OPTS "-Xmx512M -XX:MaxPermSize=512m"
Before you run Patch Assistant, you must stop the following:
Oracle WebLogic Server
Administration Servers
Managed Servers
Oracle Management Agent
Java EE Applications
High Availability Environments
For more information, see the Starting and Stopping Oracle Fusion Middleware chapter in the Oracle Fusion Middleware Administrator's Guide.
You can use the log file to verify the migration or to detect any errors after running Patch Assistant. Patch Assistant creates a time stamp file in the Patch Assistant home. You can specify the following logging levels:
info (This is the default setting)
error
warning
verbose
debug
Note:
The debug and the verbose options may display sensitive information in the logs, and they are not recommended for typical use.Before you use your log file, you must set the logging properties as follows:
Open the patchMaster.properties file in a text editor, and update the following properties:
# Description: Specifies the directory where the log files go
patchMaster.Logdir=${patchMaster.Dir}
Specifies the default location where the log file is saved.
# Description: Specifies the logging level to be recorded in the log file patchMaster.Loglevel=info
Sets the logging level.
To override the default patchMaster.properties Log level, run the command as shown in the following example:
ant -DpatchMaster.Loglevel=error
Note:
You can override thepatchMaster.properties by setting properties on the command line. If the debug or verbose options are used on the command line, they override the logging level property set in the patchMaster.properties file. For more information, see Section 3.6.1, "Overriding Properties Set in the patchMaster.properties File".