3.1 About the SOA Suite, WebCenter, and Application Developer Installers

The Oracle SOA Suite, Oracle WebCenter, and Oracle Application Developer installers can be used by existing customers to patch an existing Oracle Fusion Middleware installation, or they can be used to install a fresh Oracle Fusion Middleware environment. For these products, you download the same software and run the same installer to perform both functions.

If you are patching an existing environment, use the instructions in this guide.

If you are a new Oracle Fusion Middleware user, refer to the product installation guides for information about installing and configuring a new Oracle Fusion Middleware environment:

If you are running your products in a distributed environment (for example, you have Managed Servers running in multiple domains on multiple systems) this patching procedure must be repeated for each domain on each system. More information about distributed topologies can be found in the Enterprise Deployment Guide for your specific product.

The following provides links to additional information for each of the patching steps.

Back up your Middleware home directory and all sub-directories, along with all of your Domain home and Oracle instance home directories.

If you are patching Oracle WebCenter, there are additional steps that must be followed to ensure that your software is patched correctly. For more information, see Chapter 5, "Patching Oracle WebCenter".

Run the Patch Set Installer to update the software in your Oracle home directory.

If you have multiple Fusion Middleware products installed on your system, you will have multiple Oracle home directories; one for each product.

Each Patch Set Installer can be run against the Oracle home for its own product only; for example, you cannot run the Patch Set Installer for Oracle WebCenter to update the Oracle home for Oracle Identity Management.

3.4.1.1 Back Up Your Middleware Home, Domain Home and Oracle Instances

Before you begin your patch installation, you should back up your Middleware home directory, your Domain home directory, and your Oracle instances. If your patch installation in unexpectedly interrupted, or if you choose to cancel out of the installation before it is complete, you may not be able to install the patch unless you restore your environment to the previous configuration before running the Patch Set Installer again. There is no deinstallation option with the Patch Set Installer.

3.4.1.2 Stop the Servers and Processes

Before you run Patch Set Installer, you should stop all servers and processes.

3.4.1.3 Patch Oracle WebLogic Server

If Oracle WebLogic Server is already installed on your system, make sure you have patched Oracle WebLogic Server to the latest version using the Upgrade installer. The Patch Set Installer requires Oracle WebLogic Server version 10.3.4.

When you apply the Oracle Fusion Middleware 11.1.1.4.0 patch set, both the Omniportlet and WebClipping applications are re-deployed and all configuration data stored within file-based preference stores are lost. Therefore, before running Patch Set Installer, you must save the OmniPortlet and WebClipping configuration and customizations to ensure that customizations are not lost after applying the patch set.

To save and backup your customizations, you must first find the following directories on UNIX operating systems:

path_to_war_directory/WEB-INF/providers/omniPortlet

path_to_war_directory/WEB-INF/providers/webclipping/

On Windows operating systems:

path_to_war_directory\WEB-INF\providers\omniPortlet

path_to_war_directory\WEB-INF\providers\webclipping/

The path_to_war_directory refers to the following path on a UNIX operating system:

Depending on your system environment and product you are updating, you may be prompted to provide the location of a JRE/JDK on your system when you start the installer. When you installed Oracle WebLogic Server, a JRE was installed in the jdk160_21 directory inside the Middleware home; you can use this location to start the installer.

If you do not have Oracle WebLogic Server installed on your system, you can use the JDK in the jdk directory inside the Oracle home.

Make sure you specify the absolute path to your JRE/JDK location; relative paths are not supported.

If you are a new Oracle Fusion Middleware user, your next step is to create and configure a WebLogic domain. Return to your product installation guides for domain configuration and creation information.

3.8 Post-Patching Tasks

This section contains information about manual tasks that must be performed after the patch installation is complete. Some of the tasks may not apply to your environment as you may not be using the products in question. However, if you are, then the manual steps must be performed in order for your domain to work correctly.

3.8.1.1 Upgrading System Components

This step is required for any system component that is associated with a WebLogic domain. In some cases (for example, Oracle WebTier and Oracle Internet Directory), you can choose to create system components that are not associated with any domain; in these cases, you do not have to perform this procedure.

After you have patched your system component software that is associated with a WebLogic domain, you must run the ORACLE_HOME/opmn/bin/upgradenonj2eeapp.sh (on UNIX operating systems) or ORACLE_HOME\opmn\bin\upgradenonj2eeapp.bat (on Windows operating systems) script to update your system components.

Before running this script, make sure:

The Administration Server is up and running.

The ORACLE_HOME environment variable has been set to your product's Oracle home directory.

The OPMN instance in the bin directory in the Instance home is up and running.

The 11g Release 1 (11.1.1.4.0) of Oracle Identity Federation contains several new configuration properties (for example, enabling XML schema validation for federation protocol messages) that were not available in 11g Release 1 (11.1.1.2.0). If you want to take advantage of the functionality provided by these new properties, you must run the oif-upgrade-11.1.1.2.0-11.1.1.4.0.py WLST script as follows:

On Linux operating systems, enter the bash command:

bash

Set the DOMAIN_HOME variable to your Oracle Identity Federation Domain home location.

Set the ORACLE_HOME variable to your Oracle Identity Federation Oracle home location.

You will be prompted for the WebLogic Server Administrator credentials (user name and password) and the location of the Managed Server where Oracle Identity Federation is running. You only need to do this for one Managed Server even if you have multiple Managed Servers in your domain.

3.8.1.3 Updating Oracle Configuration Manager

If you are patching Oracle Identity Manager or Oracle Portal, Forms, Reports and Discoverer, you must run some emCCR commands after applying the latest patch set. emCCR is used by Oracle Configuration Manager, which is used to collect client configuration information and upload it to the Oracle repository:

3.8.1.4 Resolving JDBC Errors in Oracle Reports and Oracle Portal

If you have Oracle Reports or Oracle Portal version 11.1.1.2.0 or 11.1.1.3.0 configured in a domain and you apply the latest patch set, you will see the following error if you try to change the invalidation password:

Error. Check logs for details. [OK].

The following errors are seen in the portal_wls.log and wls_portal.out log files:

Run the upgradeJRF() command on the node or system where the Administration Server is located for each domain you want to update. Your domain location is passed as a parameter:

wlst> upgradeJRF('/DOMAIN_HOME')

3.8.3 Updating Configurations and Stores

For each WebLogic Server domain, you must run the upgradeOpss() WLST command to update your Release 11.1.1.2.0 or 11.1.1.3.0 configurations and stores to Release 11.1.1.4.0 configurations and stores using a system-jazn-data file in Release 11.1.1.4.0.

Note:

Before using this script, make sure that you backup the store to be upgraded. In case of a LDAP store, backup all data under the root node of the store (which is specified as a property of the store in the configuration file). In case of an upgrade failure, restore that node entirely.

3.8.4 Enabling WS-AtomicTransaction

WS-AtomicTransaction is a web services features which was introduced in Oracle Fusion Middleware Release 11.1.1.3.0 release. If you are upgrading a domain which is at the 11.1.1.2.0 release, then you need to perform the following steps to ensure that WS-AtomicTransactions are enabled:

If the name of your SOA Managed Server is not soa_server1, replace soa_server1 with the name of your SOA Managed Server.

Start all the servers.

3.8.5.2 Updating the soa-infra Application in Warning State

If you have a Release 11.1.1.4.0 Oracle SOA Suite domain with only Oracle SOA configured (no Oracle BAM and no Oracle BPM), or only Oracle SOA and Oracle BAM configured (no Oracle BPM), the soa-infra application (The weblogic server EAR file which contains the underlying logic for the SOA Suite infrastructure) will have a deployment status of Warning which will be visible within the WebLogic Server Administration Console. This state will not cause any loss or degradation in service.

If you want to fix this issue, contact Oracle Support.

3.8.5.3 Run soa-upgrade.py to Update the Policy Store and Deploy a Shared Library

Run the soa-upgrade.py WLST script, which does the following:

Adds a new Role Grant and Policy grant within the soa-infra application stripe in the Policy Store.

Deploys the oracle.soa.worklist.webapp shared library to the SOA domain.

The soa-upgrade.py script must be run from the bin directory inside your SOA Oracle home. The syntax for the soa-upgrade.py script is shown below.

Note:

This script must be run as a WLST online script. Make sure the Administration Server and Managed Servers are up and running before running this script.

If you are currently using Oracle BAM and Oracle Data Integrator (ODI) integration, you must re-run an installation script to update your Oracle ODI clients after running the Patch Set Installer to update your software.

The Oracle BAM interface used by ODI has undergone some changes between releases which require an update by all ODI client endpoints. This manual step is only required for domains where a BAM-ODI integration has been configured.

Copy the new version of the ODI configuration files from the SOA_ORACLE_HOME/bam/ODI (on UNIX operating systems) or SOA_ORACLE_HOME\bam\ODI (on Windows operating systems) directory to the ODI_ORACLE_HOME directory as follows.

Note:

If you made any changes to the ODI configuration files before you installed the patch set, then you must make those changes again after you copy the new configuration files from the SOA Oracle home.

On UNIX operating systems:

SOA_ORACLE_HOME/bam/ODI/config/bam_odi.logging.properties to ODI_HOME/lib/bam_odi.logging.properties
SOA_ORACLE_HOME/bam/ODI/config/BAMODIConfig.xml to ODI_HOME/lib/config/BAMODIConfig.xml

On Windows operating systems:

SOA_ORACLE_HOME\bam\ODI\config\bam_odi.logging.properties to ODI_HOME\lib\bam_odi.logging.properties
SOA_ORACLE_HOME\bam\ODI\config\BAMODIConfig.xml to ODI_HOME\lib\config\BAMODIConfig.xml

3.8.5.5 Committing or Reverting Open Edit Sessions in SOA Composer

Before upgrading from a previous release to 11.1.1.4.0, make sure all Edit sessions in SOA Composer are committed or reverted.

SOA Composer provides DT@RT functionality to edit rules dictionaries after deployment. After upgrading to the latest version, all uncommitted sessions in SOA Composer will lost or there can be issues accessing the edit sessions.

3.8.5.6 Saving and Restoring XEngine Customizations for Oracle B2

The procedure in this section is needed only if you use custom XEngine configurations in cases where B2B server is integrated with B2B EDI endpoints.

In such cases, all B2B domains created from the same installation share the a single XEngine configuration stored within the following directory:

On UNIX operating systems:

MW_HOME/SOA_ORACLE_HOME/soa/thirdparty/edifecs/XEngine

On Windows operating systems:

MW_HOME\SOA_ORACLE_HOME\soa\thirdparty\edifecs\XEngine

To preserve your XEngine customizations:

Prior to patching Oracle SOA Suite, back up all contents in the following directory:

3.8.6.1 Updating I/PM in Oracle Enterprise Content Management

After updating your Oracle Enterprise Content Management software to Release 11.1.1.4.0 from 11.1.1.3.0, the manual steps in this section must be performed to target a newly distributed library to the Oracle Imaging and Process Management (Oracle I/PM) deployment. If these steps are not performed, the I/PM Managed Server (default of IPM_server1) will not start.

Start Oracle WebLogic Server and open the Console:

http://administration_server_host:administration_server_port/console

For production systems, go to the "Change Center" portion of the navigation panel on the left and click Lock & Edit.

Targeting the Oracle Application Core Stub file:

In the "Domain Structure" portion of the navigation panel on the left, click Deployments.

Above the "Deployments" table, click the Install button.

In the "Path" field, browse to the directory containing the Oracle Application Core Stub file.

If oracle.soa.workflow.wc.jar is already installed due to Oracle SOA Suite being a part of the domain, you should skip the following Steps a-f. Instead, navigate to oracle.soa.workflow.wc in deployments, then go into its "Targets" tab and target IPM_server1.

In the "Domain Structure" portion of the navigation panel on the left, click Deployments.

Above the "Deployments" table, click the Install button.

In the "Path" field, browse to the directory containing the Oracle SOA Libraries file.

Due to security changes in WebLogic Server, if you were running an SSL-enabled 11g version of Oracle Portal and patched it to Release 11.1.14.0, you will need to perform the steps mentioned in the "Enable the WebLogic Plug-In, and WLProxySSL and WLProxySSLPassThrough Parameters" section of the Oracle Fusion Middleware Administrator's Guide for Oracle Portal before your Oracle Portal instance will be functional again.

This procedure is only needed if you are using OmniPortlet and WebClipping customizations, and they are being used with a file-based preferences store. By default, in Oracle WebCenter and Portal, file-based preferences store is not used. Such stores are only used by default for 11g Portal environments that were upgraded from their 10g versions.

When you apply the Oracle Fusion Middleware 11.1.1.3.0 patch set, both the Omniportlet and WebClipping applications are re-deployed and all customizations and configuration data are lost. Therefore, before running Patch Set Installer, you must save the OmniPortlet and WebClipping configuration and customizations to ensure that customizations are not lost after applying the patch set.

In the Oracle WebCenter domain, restart the Managed Server WC_Portlet.

3.8.9 Adding New OWSM Pre-Defined Policies

Each new patchset of Oracle Web Services Manager (OWSM) can contain new pre-defined web services policies. If your existing domain was created or extended with the Oracle WSM Policy Manager template in the Configuration Wizard, you must do the following to take advantage of these new policies for your domain:

Use connect() to connect to the server running the owsm-pm application.

3.8.10.1 Upgrade Instructions

To upgrade your Release 11.1.1.3.0 domain configuration information:

Make sure you have backed up and shut down all domains to be upgraded.

Under each Oracle Service Bus domain to be upgraded, open a command window and run the DOMAIN_HOME/bin/setDomainEnv.sh (on UNIX operating systems) or DOMAIN_HOME\bin\setDomainEnv.cmd (on Windows operating systems) command.

In the command window, switch to the directory in which the upgrade scripts resides:

OSB_ORACLE_HOME/common/lib/upgrade

On the command line, run the appropriate script for your operating system:

3.8.10.2 Post-Upgrade Tasks

3.8.10.2.1 Deleting Oracle WebLogic Server 11g Release 1 (10.3.3)

You need to create a new Server pointing to Weblogic Server 11g Release 1 (10.3.4) to successfully publish the Oracle Service Bus configuration to the server. In order to do this, you need to delete Oracle WebLogic Server 11g Release 1 (10.3.3).

To delete Oracle WebLogic Server 11g Release 1 (10.3.3), use the following steps:

3.8.10.2.2 Creating Servers

You can deploy (publish) and test your Oracle Service Bus configuration on a running server in Eclipse. When connected to a running server in development, you can also connect to resources in the run-time environment such as JNDI resources and remote EJBs.

If you have an existing Oracle WebLogic Server you want to connect to, the server creation process simply involves you pointing at the existing server domain. If you want to create a new server, the new server wizard lets you create one using the Oracle Fusion Middleware Configuration Wizard.

To Create a Server in Eclipse, use the following steps:

In the Oracle Service Bus perspective, select File > New > Server. The New Server wizard appears.

Select the server type/version you want to create or connect to.

For Server's host name, enter localhost for a local server or enter the name or IP address of the remote system hosting an existing server.

The Server name is for display purposes in Eclipse.

Click Next.

For WebLogic home, click Browse and select the WebLogic_Server_HOME in the Oracle Fusion Middleware installation where the server domain is to reside (or already resides). For example, if you are creating a new server in MW_HOME_1, select the MW_HOME_1/WebLogic_Server_HOME; or if you are connecting to an existing server domain in MW_HOME_2, select the MW_HOME_2/WebLogic_Server_HOME.

Note:

You cannot reference a WebLogic_Server_HOME that is outside of the server's installation MW_HOME, even if the external MW_HOME is the same product version.

The Java home should be populated automatically. If you want to use a different JRE, such as the default Oracle JRockit JRE, click Browse and select the JRE under the same MW_HOME as the server.

Click Next.

Select whether the server is Local or Remote. Remote implies an existing remote server.

If Local, either select an existing server in the Domain Directory field or click the link to create a new domain. After creating a new domain, select it in the Domain Directory field.

Set other options as desired, such as automatic publishing and debug mode.

If Remote, enter the connection settings to an existing remote server.

Click Next.

Move any Oracle Service Bus configuration(s) you want to publish on the server to the Configured pane. You can modify this targeting after you create the server by right-clicking the server and selecting Add and Remove.

Click Finish. The new server appears in the Servers view in Eclipse, where you can start, stop, and publish to the server.

3.9 Starting the Servers and Processes

After you have finished patching your software and performing any necessary post-patching tasks, you are ready to start the servers and processes.