Skip Headers
Oracle® Fusion Middleware Patching Guide
11g Release 1 (11.1.1.7.0)

Part Number E16793-25
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

5 Post-Patching Procedures

This section contains information about manual tasks performed after the Release 11.1.1.7.0 patch installation is complete. Some of the tasks may not apply to your environment as you may not be using the products in question.

NOTE:

The post-patching tasks described in this chapter are not required for all environments or upgrade paths. Consult the Release Starting Point table for your existing environment to determine which tasks apply.

The following topics are covered:

5.1 Post-Patching Tasks If Your Starting Point is Release 11.1.1.2.0

Table 5-1 summarizes the post-patching tasks that may be required depending on your existing Release 11.1.1.2.0 environment. Locate the applicable product area in the table, then refer to the documentation link for instructions.

Table 5-1 Post-Patching Tasks If Your Starting Point is Release 11.1.1.2.0

Product Area Documentation

System and Identity Management Components

Patch any system component(s) associated with a WebLogic Server domain.

Section 5.6.1, "Upgrading System Components"

Oracle Internet Directory, if you plan to add more than one million entries.

Section 5.6.4, "Adding Datafiles to the OLTS_CT_STORE and OLTS_ATTRSTORE Tablespaces for Oracle Internet Directory"

Oracle Configuration Manager for Oracle Identity Management or Oracle Portal, Forms, Reports and Discoverer (Windows operating system only).

Section 5.6.2, "Updating Oracle Configuration Manager"

Oracle Reports and Oracle Portal.

Section 5.6.3, "Resolving JDBC Errors in Oracle Reports and Oracle Portal"

Section 5.8.6, "Updating the Plug-In Configuration When Using a Proxy with WebLogic Server"

Diagnostic Framework

Section 5.6.7, "Configuring Diagnostic Framework Dump Sampling"

Oracle Identity Federation.

Section 5.7.3, "Updating Configuration Properties in Oracle Identity Federation"

Oracle Identity Management listening on dual network addresses.

Section 5.7.4, "Configuring Oracle Identity Management to Listen on Dual Network Addresses"

Oracle WebCenter

 

Patching procedures for either a Release 11.1.1.2.0 or 11.1.1.3.0 installation.

Section 6.4, "Patching an Oracle WebCenter 11.1.1.2.0 or 11.1.1.3.0 Installation"

WebLogic Server Domain

Shared Libraries.

Section 5.8.2, "Updating Fusion Middleware Shared Libraries"

Configurations and Stores.

Section 5.8.3, "Updating Configurations and Stores"

Web Services Atomic Transaction.

Section 5.8.4, "Enabling WS-AtomicTransaction"

Oracle SOA Suite

SOA Schemas and database growth.

Section 5.9.1, "Loading the Oracle SOA Suite Purge Scripts for Database Management"

SOA Composer and BPM Workspace.

Section 5.9.2, "Removing the tmp Folder for SOA Composer, BPM Workspace and B2B"

Oracle SOA soa-infra application.

Section 5.9.5, "Updating the soa-infra Application in Warning State"

Application Policy Store.

Section 5.9.6, "Running bpm-ps6-upgrade.py to Update the Policy Store"

Policy Store and Shared Library.

Section 5.9.7, "Running soa-upgrade.py to Update the Policy Store and Deploy a Shared Library"

BAM-ODI Integration.

Section 5.9.8, "Updating the Oracle Data Integrator Clients if BAM-ODI Integration is Enabled"

Oracle B2B.

Section 5.9.9, "Saving and Restoring XEngine Customizations for Oracle B2B"

User Messaging Service (UMS) Adapter

Section 5.9.11, "Extending the SOA Domain with UMS Adapter Features"

Business Process Management (BPM)

Section 5.9.12, "Extending the SOA Domain with Business Process Management Features"

Oracle Service Bus

Oracle Service Bus.

Section 5.11, "Post-Patching Tasks for Oracle Service Bus"


5.2 Post-Patching Tasks If Your Starting Point is Release 11.1.1.3.0

Table 5-2 summarizes the post-patching tasks that may be required depending on your existing Release 11.1.1.3.0 environment. Locate the applicable product area in the table, then refer to the documentation link for instructions.

Table 5-2 Post-Patching Tasks If Your Starting Point is Release 11.1.1.3.0

Product Area Documentation

System and Identity Management Components

Patch any system component(s) associated with a WebLogic Server domain.

Section 5.6.1, "Upgrading System Components"

Oracle Internet Directory, if you plan to add more than one million entries.

Section 5.6.4, "Adding Datafiles to the OLTS_CT_STORE and OLTS_ATTRSTORE Tablespaces for Oracle Internet Directory"

Oracle Configuration Manager for Oracle Identity Management or Oracle Portal, Forms, Reports and Discoverer (Windows operating system only).

Section 5.6.2, "Updating Oracle Configuration Manager"

Oracle Identity and Access Management Components.

Section 7.2, "Patching Oracle Identity and Access Management 11.1.1.3.0 Components"

Oracle Reports and Oracle Portal.

Section 5.6.3, "Resolving JDBC Errors in Oracle Reports and Oracle Portal"

Section 5.8.6, "Updating the Plug-In Configuration When Using a Proxy with WebLogic Server"

Diagnostic Framework

Section 5.6.7, "Configuring Diagnostic Framework Dump Sampling"

Oracle Identity Federation.

Section 5.7.3, "Updating Configuration Properties in Oracle Identity Federation"

Oracle Internet Directory listening on dual network addresses.

Section 5.7.4, "Configuring Oracle Identity Management to Listen on Dual Network Addresses"

WebLogic Server Domain

Shared Libraries.

Section 5.8.2, "Updating Fusion Middleware Shared Libraries"

Configurations and Stores.

Section 5.8.3, "Updating Configurations and Stores"

Oracle SOA Suite

SOA Schemas and database growth.

Section 5.9.1, "Loading the Oracle SOA Suite Purge Scripts for Database Management"

SOA Composer and BPM Workspace.

Section 5.9.2, "Removing the tmp Folder for SOA Composer, BPM Workspace and B2B"

Oracle SOA soa-infra application.

Section 5.9.5, "Updating the soa-infra Application in Warning State"

Application Policy Store.

Section 5.9.6, "Running bpm-ps6-upgrade.py to Update the Policy Store"

Policy Store and Shared Library.

Section 5.9.7, "Running soa-upgrade.py to Update the Policy Store and Deploy a Shared Library"

BAM-ODI Integration.

Section 5.9.8, "Updating the Oracle Data Integrator Clients if BAM-ODI Integration is Enabled"

Oracle B2B.

Section 5.9.9, "Saving and Restoring XEngine Customizations for Oracle B2B"

User Messaging Service (UMS) Adapter

Section 5.9.11, "Extending the SOA Domain with UMS Adapter Features"

Business Process Management (BPM)

Section 5.9.12, "Extending the SOA Domain with Business Process Management Features"

Oracle WebCenter Content

Oracle WebCenter Content: Imaging.

Section 5.10.1, "Updating Oracle WebCenter Content: Imaging"

Oracle WebCenter Content application adapters.

Section 5.10.2, "Updating Oracle Application Adapters for Oracle WebCenter Content"

Report Library for Records Management in Content Server.

Section 5.10.3, "Configuring the Report Library for Records Management in Content Server"

Oracle Service Bus

Oracle Service Bus.

Section 5.11, "Post-Patching Tasks for Oracle Service Bus"

Oracle Business Intelligence

Oracle Business Intelligence Code Grants.

Section 5.12.1, "Updating Oracle Business Intelligence Code Grants"

Oracle Business Intelligence Catalogs.

Section 5.12.2, "Updating Oracle BI Presentation Catalogs"

Oracle Real-Time Decisions.

Section 5.12.6, "Updating Oracle Real-Time Decisions"

Oracle Data Integrator

Oracle Data Integrator repository objects.

Section 5.13.1, "Finalizing Repository Patching"

Oracle Data Integrator Java EE Agent.

Section 5.13.2, "Reconfiguring the Java EE Agent"

Oracle Data Integrator Standalone Agent.

Section 5.13.3, "Reconfiguring the ODI Standalone Agent"

Oracle Enterprise Manager.

Section 5.13.4, "Reconfiguring Oracle Enterprise Manager Properties"

Oracle Data Integrator Console.

Section 5.13.5, "Reconfiguring the ODI Console"

Oracle Data Integrator odi-sdk-ws Application.

Section 5.13.6, "Adding the Version Number for the odi-sdk-ws Application in config.xml"


5.3 Post-Patching Tasks If Your Starting Point is Release 11.1.1.4.0

Table 5-3 summarizes the post-patching tasks that may be required depending on your existing Release 11.1.1.4.0 environment. Locate the applicable product area in the table, then refer to the documentation link for instructions.

Table 5-3 Post-Patching Tasks If Your Starting Point is Release 11.1.1.4.0

Product Area Documentation

System and Identity Management Components

Patch any system compoment(s) associated with a WebLogic Server domain.

Section 5.6.1, "Upgrading System Components"

Oracle Identity Federation.

Section 5.7.3, "Updating Configuration Properties in Oracle Identity Federation"

Oracle Internet Directory, if you plan to add more than one million entries.

Section 5.6.4, "Adding Datafiles to the OLTS_CT_STORE and OLTS_ATTRSTORE Tablespaces for Oracle Internet Directory"

Oracle Internet Directory listening on dual network addresses.

Section 5.7.4, "Configuring Oracle Identity Management to Listen on Dual Network Addresses"

Oracle Configuration Manager for Oracle Identity Management (Windows operating system only).

Section 5.6.2, "Updating Oracle Configuration Manager"

Oracle Reports and Oracle Portal.

Section 5.6.3, "Resolving JDBC Errors in Oracle Reports and Oracle Portal"

Patch any system using a proxy module in front of WebLogic Server

Section 5.8.6, "Updating the Plug-In Configuration When Using a Proxy with WebLogic Server"

Oracle Platform Security Services (OPSS)

Section 5.6.5, "Generating the BASE64 Encoded Encryption Key for OPSS"

Section 5.6.6, "Enabling Dynamic Audit Metadata Model for OPSS Running in JavaSE Mode"

Diagnostic Framework

Section 5.6.7, "Configuring Diagnostic Framework Dump Sampling"

JRF Template for IBM WebSphere

Section 5.6.8, "Adding Batik Library Jar Files to the JRF Template for IBM WebSphere"

Oracle SOA Suite

SOA Composer and BPM Workspace (this is only applicable if your Release 11.1.1.4.0 software is updated from Release 11.1.1.3.0. If you installed and configured Release 11.1.1.4.0 from scratch then you do not need to perform this task).

Section 5.9.2, "Removing the tmp Folder for SOA Composer, BPM Workspace and B2B"

Oracle BPEL

Section 5.9.4, "Updating MAXRECOVERATTEMPT Attribute to 2"

Oracle SOA soa-infra application.

Section 5.9.5, "Updating the soa-infra Application in Warning State"

Application Policy Store.

Section 5.9.6, "Running bpm-ps6-upgrade.py to Update the Policy Store"

BAM-ODI Integration.

Section 5.9.8, "Updating the Oracle Data Integrator Clients if BAM-ODI Integration is Enabled"

Oracle B2B.

Section 5.9.9, "Saving and Restoring XEngine Customizations for Oracle B2B"

User Messaging Service (UMS) Adapter

Section 5.9.11, "Extending the SOA Domain with UMS Adapter Features"

Business Process Management (BPM)

Section 5.9.12, "Extending the SOA Domain with Business Process Management Features"

Oracle WebCenter Content

Oracle WebCenter Content: Imaging.

Section 5.10.1, "Updating Oracle WebCenter Content: Imaging"

Oracle WebCenter Content application adapters.

Section 5.10.2, "Updating Oracle Application Adapters for Oracle WebCenter Content"

Report Library for Records Management in Content Server.

Section 5.10.3, "Configuring the Report Library for Records Management in Content Server"

Oracle WebCenter Content: Imaging Viewer Cache

Section 5.10.4, "Extending the IPM Domain to Include Viewer Cache"

Oracle Data Integrator

Oracle Data Integrator repository objects.

Section 5.13.6, "Adding the Version Number for the odi-sdk-ws Application in config.xml"


5.4 Post-Patching Tasks If Your Starting Point is Release 11.1.1.5.0

Table 5-4 summarizes the post-patching tasks that may be required depending on your existing Release 11.1.1.5.0 environment. Locate the applicable product area in the table, then refer to the documentation link for instructions.

Table 5-4 Post-Patching Tasks If Your Starting Point is Release 11.1.1.5.0

Product Area Documentation

System and Identity Management Components

Patch any system component(s) associated with a WebLogic Server domain.

Section 5.6.1, "Upgrading System Components"

Oracle Identity Federation.

Section 5.7.3, "Updating Configuration Properties in Oracle Identity Federation"

Oracle Internet Directory, if you plan to add more than one million entries.

Section 5.6.4, "Adding Datafiles to the OLTS_CT_STORE and OLTS_ATTRSTORE Tablespaces for Oracle Internet Directory"

Oracle Internet Directory listening on dual network addresses.

Section 5.7.4, "Configuring Oracle Identity Management to Listen on Dual Network Addresses"

Oracle Configuration Manager for Oracle Identity Management (Windows operating system only).

Section 5.6.2, "Updating Oracle Configuration Manager"

Oracle Reports and Oracle Portal.

Section 5.6.3, "Resolving JDBC Errors in Oracle Reports and Oracle Portal"

Section 5.8.6, "Updating the Plug-In Configuration When Using a Proxy with WebLogic Server"

Oracle Platform Security Services (OPSS)

Section 5.6.5, "Generating the BASE64 Encoded Encryption Key for OPSS"

Section 5.6.6, "Enabling Dynamic Audit Metadata Model for OPSS Running in JavaSE Mode"

Diagnostic Framework

Section 5.6.7, "Configuring Diagnostic Framework Dump Sampling"

JRF Template for IBM WebSphere

Section 5.6.8, "Adding Batik Library Jar Files to the JRF Template for IBM WebSphere"

Oracle SOA Suite

SOA Composer and BPM Workspace .

Section 5.9.2, "Removing the tmp Folder for SOA Composer, BPM Workspace and B2B"

Oracle BPEL

Section 5.9.4, "Updating MAXRECOVERATTEMPT Attribute to 2"

Oracle SOA soa-infra application.

Section 5.9.5, "Updating the soa-infra Application in Warning State"

BAM-ODI Integration.

Section 5.9.8, "Updating the Oracle Data Integrator Clients if BAM-ODI Integration is Enabled"

Oracle B2B.

Section 5.9.9, "Saving and Restoring XEngine Customizations for Oracle B2B"

Oracle JMS Adapter.

Section 5.9.10, "Configuring Oracle JMS Adapter with IBM WebSphere MQ JMS"

User Messaging Service (UMS) Adapter

Section 5.9.11, "Extending the SOA Domain with UMS Adapter Features"

Business Process Management (BPM)

Section 5.9.12, "Extending the SOA Domain with Business Process Management Features"

Oracle WebCenter Content

Oracle WebCenter Content: Imaging.

Section 5.10.1, "Updating Oracle WebCenter Content: Imaging"

Oracle WebCenter Content application adapters.

Section 5.10.2, "Updating Oracle Application Adapters for Oracle WebCenter Content"

Report Library for Records Management in Content Server.

Section 5.10.3, "Configuring the Report Library for Records Management in Content Server"

Oracle WebCenter Content: Imaging Viewer Cache

Section 5.10.4, "Extending the IPM Domain to Include Viewer Cache"

Oracle Service Bus

Oracle Service Bus.

Section 5.11.1, "Updating an Oracle Service Bus Domain After Applying the Latest Patch Set"

Oracle Service Bus IDE.

Section 5.11.2, "Using Oracle Service Bus Release 11.1.1.7.0 with WebLogic Server 10.3.5"

Section 5.11.4, "Performing Additional Post-Update Tasks for Oracle Service Bus IDE"

Oracle Business Intelligence

Oracle Business Intelligence.

Section 5.12.3, "Enabling bicontentserver Features"


5.5 Post-Patching Tasks If Your Starting Point is Release 11.1.1.6.0

Table 5-5 summarizes the post-patching tasks that may be required depending on your existing Release 11.1.1.6.0 environment. Locate the applicable product area in the table, then refer to the documentation link for instructions.

Table 5-5 Post-Patching Tasks If Your Starting Point is Release 11.1.1.6.0

Product Area Documentation

System and Identity Management Components

Patch any system component(s) associated with a WebLogic Server domain.

Section 5.6.1, "Upgrading System Components"

Oracle Identity Federation.

Section 5.7.3, "Updating Configuration Properties in Oracle Identity Federation"

Oracle Platform Security Services (OPSS)

Section 5.6.5, "Generating the BASE64 Encoded Encryption Key for OPSS"

Section 5.6.6, "Enabling Dynamic Audit Metadata Model for OPSS Running in JavaSE Mode"

Diagnostic Framework

Section 5.6.7, "Configuring Diagnostic Framework Dump Sampling"

JRF Template for IBM WebSphere

Section 5.6.8, "Adding Batik Library Jar Files to the JRF Template for IBM WebSphere"

Oracle SOA Suite

Oracle B2B, SOA Composer, BPM Workspace

Section 5.9.2, "Removing the tmp Folder for SOA Composer, BPM Workspace and B2B"

Business Process Execution Language (BPEL) Messaging

Section 5.9.3, "Updating the "BPEL Message Recovery Required" Warning Message Duration"

Oracle BPEL

Section 5.9.4, "Updating MAXRECOVERATTEMPT Attribute to 2"

User Messaging Service (UMS) Adapter

Section 5.9.11, "Extending the SOA Domain with UMS Adapter Features"

Business Process Management (BPM)

Section 5.9.12, "Extending the SOA Domain with Business Process Management Features"

Oracle WebCenter Content

Oracle WebCenter Content: Imaging.

Section 5.10.1, "Updating Oracle WebCenter Content: Imaging"

Oracle WebCenter Content application adapters.

Section 5.10.2, "Updating Oracle Application Adapters for Oracle WebCenter Content"

Report Library for Records Management in Content Server.

Section 5.10.3, "Configuring the Report Library for Records Management in Content Server"

Oracle WebCenter Content: Imaging Viewer Cache

Section 5.10.4, "Extending the IPM Domain to Include Viewer Cache"

Oracle Service Bus

Oracle Service Bus with Oracle WebLogic Server 10.3.6

Section 5.11.3, "Using Oracle Service Bus Release 11.1.1.7.0 with WebLogic Server 10.3.6"

Oracle Business Intelligence

Oracle Business Intelligence Composer

Section 5.12.4, "Enabling Oracle Business Intelligence Composer Features"

Oracle Business Intelligence JBIPS

Section 5.12.5, "Enabling JBIPS Features"


5.6 Post-Patching Tasks for System Components

A system component is a manageable process that is not deployed as a Java application. Instead, a system component is managed by Oracle Process Manager and Notification (OPMN). For more information, see "Understanding Key Oracle Fusion Middleware Concepts" in Oracle Fusion Middleware Administrator's Guide.

Post-patching procedures for the Oracle Identity Management components are described in Section 5.7, "Post-Patching Tasks for Oracle Identity Management Components".

Oracle Fusion Middleware system components include the following:

If you have patched one or more of these components, the tasks in this section should be performed. For more information about system components, refer to "Understanding Key Oracle Fusion Middleware Concepts" in Oracle Fusion Middleware Administrator's Guide.

The following tasks should be performed:

5.6.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 Web Tier 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:

  1. The Administration Server is up and running.

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

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

    On UNIX operating systems:

    cd INSTANCE_HOME/bin
    ./opmnctl start
    

    On Windows operating systems:

    cd INSTANCE_HOME\bin
    opmnctl start
    

NOTE: Be sure to select the procedure that applies to your environment.

To run the script on UNIX operating systems:

cd ORACLE_HOME/opmn/bin
./upgradenonj2eeapp.sh
   -oracleInstance Instance_Home_Location
   -adminHost WebLogic_Server_Host_Name
   -adminPort administration_server_port_number
   -adminUsername administration_server_user
   -adminProtocol ts3

On Windows operating systems:

cd ORACLE_HOME\opmn\bin
upgradenonj2eeapp.bat
   -oracleInstance Instance_Home_Location
   -adminHost WebLogic_Server_Host_Name
   -adminPort administration_server_port_number
   -adminUsername administration_server_user
   -adminProtocol ts3

If the Administration Server has been configured for SSL Only:

cd ORACLE_HOME\opmn\bin
upgradenonj2eeapp.bat
   -oracleInstance Instance_Home_Location
   -adminHost WebLogic_Server_Host_Name
   -adminPort administration_server_port_number
   -adminUsername administration_server_user
   -adminProtocol ts3

If the Administration Server allows access over HTTP:

cd ORACLE_HOME\opmn\bin
upgradenonj2eeapp.bat
   -oracleInstance Instance_Home_Location
   -adminHost WebLogic_Server_Host_Name
   -adminPort administration_server_port_number
   -adminUsername administration_server_user

NOTE: If the Administration Server allows access over HTTP, then you should NOT specify the adminProtocol. It will default to t3 which is the non-secure protocol.

Troubleshooting

If you encounter the Command failed: NonJ2EEManagement Application deployment failed error while running the upgradenonj2eeapp script, perform the following steps to diagnose and correct the problem:

  1. Review the provisioning.log to determine the root cause of the failure. The log file is located in the following directory:

    MW_HOME/instances/myinstance/diagnostics/logs/OPMN/opmn

  2. If the root cause of the failure is a locking issue, continue with the remaining steps.

    If the error was not caused by a locking failure, you may need to simply redeploy and register your instance as described in Step 5.

  3. Login to the Oracle WebLogic Server Administration console:

    http://localhost:7001/console
    

    Navigate to the Change Center and click Release Configuration.

    The lock on the configuration will be removed, but you may also need to deploy re-register your instance.

  4. Restart the upgradenonj2eeapp script as described above and review the provisioning.log.

    If you see: "Failed to unregister instance instance1. It does not exist on the adminserver." contine on to the next step.

  5. Redeploy and register the instance as shown in the following examples. Be sure to use the directory path and instance name for your environment.

    ./opmnctl redeploy -oracleInstance /Middleware/instances/instance1 -adminHost localhost -adminPort 7001 -adminUsername weblogic
    
    Command requires login to weblogic admin server (localhost):
      Username: weblogic
      Password: 
    
    ./opmnctl registerinstance
    Command requires login to weblogic admin server (localhost):
      Username: weblogic
      Password: 
    
  6. Restart the upgradenonj2eeapp script as described above. You should see "Successfully upgraded NonJ2EEManagement.ear and the registeration."

5.6.2 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 in order for the correct version to appear. emCCR is used by Oracle Configuration Manager, which is used to collect client configuration information and upload it to the Oracle repository:

  1. Go to the ORACLE_HOME\ccr\bin directory.

  2. Set the ORACLE_CONFIG_HOME environment variable to the Instance home that contains Oracle Configuration Manager.

    For example, on a Windows operating system:

    set ORACLE_CONFIG_HOME=C:\Oracle\Middleware\Instances\asinst_ocmoc
    

    Below is an example on a UNIX operating system:

    setenv ORACLE_CONFIG_HOME /home/Oracle/Middleware/asinst_ocmoc
    
  3. Run the following emCCR commands:

    emccr collect
    emccr status
    

5.6.3 Resolving JDBC Errors in Oracle Reports and Oracle Portal

If you have Oracle Reports or Oracle Portal 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:

<Date and time> <Warning> <RMI> <BEA-080003>
<RuntimeException thrown by rmi server:
javax.management.remote.rmi.RMIConnectionImpl.invoke
(Ljavax.management.ObjectName;Ljava.lang.String;Ljava.rmi.MarshalledObject;[Ljava.lang.String;Ljavax.security.auth.Subject;)
javax.management.RuntimeErrorException:
oracle.jdbc.driver.T2CConnection.getLibraryVersionNumber()I.javax.management.RuntimeErrorException:
oracle.jdbc.driver.T2CConnection.getLibraryVersionNumber()I
at
oracle.as.jmx.framework.standardmbeans.spi.OracleStandardEmitterMBean.doInvoke(OracleStandardEmitterMBean.java:991)
at
oracle.adf.mbean.share.AdfMBeanInterceptor.internalInvoke(AdfMBeanInterceptor.java:104)
at
oracle.as.jmx.framework.generic.spi.interceptors.AbstractMBeanInterceptor.doInvoke(AbstractMBeanInterceptor.java:252)
....
 
Caused By: java.lang.UnsatisfiedLinkError:
oracle.jdbc.driver.T2CConnection.getLibraryVersionNumber()I
at oracle.jdbc.driver.T2CConnection.getLibraryVersionNumber(Native
        Method)
at oracle.jdbc.driver.T2CConnection$1.run(T2CConnection.java:3537)
at java.security.AccessController.doPrivileged(Native Method)
at oracle.jdbc.driver.T2CConnection.loadNativeLibrary
        (T2CConnection.java:3532)
.... 

You must perform the following in order to avoid these JDBC error messages:

  1. Go to the bin directory inside your DOMAIN_HOME.

  2. Edit the setDomainEnv.sh (on UNIX operating systems) or setDomainEnv.cmd (on Windows operating systems) file and search for EXT_PRE_CLASSPATH.

  3. Change the definition to match the following:

    On UNIX operating systems:

    EXT_PRE_CLASSPATH=$ORACLE_HOME/jdbc/lib/ojdbc6.jar
    export EXT_PRE_CLASSPATH
    

    For example:

    if [ "${EXT_PRE_CLASSPATH}" != "" ] ; then
       if [ "${PRE_CLASSPATH}" != "" ] ; then
          EXT_PRE_CLASSPATH=$ORACLE_HOME/jdbc/lib/ojdbc6.jar // add this line
          export EXT_PRE_CLASSPATH                           // add this line
          PRE_CLASSPATH="${EXT_PRE_CLASSPATH}${CLASSPATHSEP}${PRE_CLASSPATH}"
          export PRE_CLASSPATH
       else
          EXT_PRE_CLASSPATH=$ORACLE_HOME/jdbc/lib/ojdbc6.jar  // add this line
          export EXT_PRE_CLASSPATH                            // add this line
          PRE_CLASSPATH="${EXT_PRE_CLASSPATH}"
          export PRE_CLASSPATH
       fi
    fi
    

    On Windows operating systems:

    if NOT "%EXT_PRE_CLASSPATH%"=="" (
       if NOT "%PRE_CLASSPATH%"=="" (
          set EXT_PRE_CLASSPATH=%ORACLE_HOME%\jdbc\lib\ojdbc6.jar  // add this line
          set PRE_CLASSPATH=%EXT_PRE_CLASSPATH%;%PRE_CLASSPATH%
       ) else (
          set EXT_PRE_CLASSPATH=%ORACLE_HOME%\jdbc\lib\ojdbc6.jar  // add this line
          set PRE_CLASSPATH=%EXT_PRE_CLASSPATH%
       )
    )
    
  4. Restart the Portal Managed Server.

5.6.4 Adding Datafiles to the OLTS_CT_STORE and OLTS_ATTRSTORE Tablespaces for Oracle Internet Directory

If your Oracle Internet Directory schema was created during installation of a version prior to 11g Release 1 (11.1.1.6.0), you must add datafiles to the OLTS_CT_STORE and OLTS_ATTRSTORE tablespaces if you intend to add more than a million entries to Oracle Internet Directory. Perform this step prior to the bulkload or ldapadd operation.

For details, see "Creating Datafiles and Adding Datafiles to a Tablespace" in Oracle Database Administrator's Guide.

5.6.5 Generating the BASE64 Encoded Encryption Key for OPSS

The upgradeOpss() command is used to add a new BASE64 encoded key for each encryption key already in the bootstrap wallet. This key is required when OBI C based code accesses DB credential store. This optional command can be used when starting from version 11.1.1.4.0, 11.1.1.5.0, or 11.1.1.6.0. If this step is not followed, OBI will be unable to access DB-based credential stores in 11.1.1.7.0.

For more information on running OPSS in JSE mode, see "Configuring DB-Based OPSS Security Stores" in Oracle Fusion Middleware Security Guide.

5.6.6 Enabling Dynamic Audit Metadata Model for OPSS Running in JavaSE Mode

To enable the dynamic audit metadata model in audit service for OPSS running in JavaSE mode, the upgradeOpss() command is used to modify jps-config-jse.xml with the additional audit service properties. This optional command can be used when starting from version 11.1.1.4.0, 11.1.1.5.0, or 11.1.1.6.0. If this step is not followed, 11.1.1.7.0 components registered to audit service with the new metadata model will not have audit service in JSE mode.

For more information on running OPSS in JSE mode, see "Configuring Policy and Credential Stores in Java SE Applications" in Oracle Fusion Middleware Security Guide.

5.6.7 Configuring Diagnostic Framework Dump Sampling

In Release 11.1.1.7.0 a new dump sampling feature was added to Diagnostic Framework. To enable this optional feature, the following WLST command should be run while connected to the AdminServer:

wlst.sh <ORACLE_HOME>/common/scripts/wlst/upgradeDFWConfig.py --adminuser <admin user name> --password <admin password> --adminurl <admin url>

5.6.8 Adding Batik Library Jar Files to the JRF Template for IBM WebSphere

This optional post-patching step enables you to provide printer-friendly renderings of certain DVT components such as treemap and sunburst by adding the Batik SVG libraries to the ADF View JRF classpath and the Apache JARs to the application classpath.

For more information, see "updateADFLibrary" in the Oracle Fusion Middleware Administrator's Guide for Oracle Application Development Framework.

5.7 Post-Patching Tasks for Oracle Identity Management Components

This section describes post-patching tasks for products included in Oracle Identity Management: Oracle Internet Directory, Oracle Directory Integration Platform, Oracle Virtual Directory, Oracle Directory Services Manager and Oracle Identity Federation.

5.7.1 Enabling the Evaluate Policies Scheduled Job Run

If you are upgrading Oracle Identity Manager to 11.1.1.7.0 from a previous release, and you use the Evaluate Policies scheduled job, you must enable this job to run after you have patched your existing environment. In Oracle Identity Manager 11.1.1.7.0, the Evaluate Policies scheduled job defaults to disabled, therefore your jobs will not run successfully. In addition, consider setting the frequency to 10 minutes.

To enable the Evaluate Policies Scheduled Job:

  1. Log in to Oracle Identity Administration with the appropriate credentials.

  2. Click the System Management tab and then click Scheduler. Alternatively, you can click the "Search Scheduled Jobs" link on Welcome Screen.

  3. On the left pane, in the search results table, right click on Evaluate Policies and select Enable. You should see a message indicating that the job has been successfully enabled.

  4. Click OK to close the dialog box.

To change the frequency of a scheduled job:

  1. Log in to Oracle Identity Administration with the appropriate credentials.

  2. Click the System Management tab and then click Scheduler. Alternatively, you can click the "Search Scheduled Jobs" link on Welcome Screen.

  3. Click Evaluate Policies in the Job Name column of the search results table.

  4. Navigate to the Job Details page and enter 10 in the -mins field. This will trigger the job to run every 10 minutes.

  5. Note:

    For all the schedule types, if you want the job to be saved and then immediately run, then click Save and Run Now.

    A message confirming that the job has been successfully created and triggered is displayed.

5.7.2 Updating Oracle Identity Management in an Existing ORACLE_IDM_HOME Directory

If you are updating Oracle Identity Management in an already patched ORACLE_IDM_HOME, you will be prompted twice to run oidRoot.sh. Answer 'Yes' twice and the oidRoot.sh will execute as normal. If the root privileges need to be changed then they will be changed.

5.7.3 Updating Configuration Properties in Oracle Identity Federation

Oracle Identity Federation has new features and bug fixes that require new properties to be defined in the Oracle Identity Federation configuration file. If you want to take advantage of the functionality provided by these new properties, you must run one of the following WLST scripts:

  • Run the oif-upgrade-11.1.1.2.0-11.1.1.7.0.py script if:

    • You are updating your software from 11.1.1.2.0 or 11.1.1.3.0 to 11.1.1.7.0

    • You did not previously run the oif-upgrade-11.1.1.2.0-11.1.1.4.0.py script on an existing 11.1.1.4.0 or 11.1.1.5.0 installation.

  • Run the oif-upgrade-11.1.1.4.0-11.1.1.7.0.py script if you are updating your software from 11.1.1.4.0 or 11.1.1.5.0 to 11.1.1.7.0.

  • Run the oif-upgrade-11.1.1.6.0-11.1.1.7.0.py script if you are updating your software from 11.1.1.6.0 to 11.1.1.7.0.

The instructions to run the scripts are shown below:

  1. On Linux operating systems, enter the bash command:

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

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

  4. Run the setOIFEnv script.

    On UNIX operating systems:

    bash
    export DOMAIN_HOME=full_path_to_domain_home_directory
    source ORACLE_HOME/fed/scripts/setOIFEnv.sh
    

    On Microsoft Windows operating systems:

    cd ORACLE_HOME\fed\scripts
    setOIFEnv.cmd
    
  5. Run the oif-upgrade-11.1.1.2.0-11.1.1.7.0.py, oif-upgrade-11.1.1.4.0-11.1.1.7.0.py, or oif-upgrade-11.1.1.6.0-11.1.1.7.0.py script.

    For example, on UNIX operating systems:

    cd ORACLE_HOME/fed/scripts
    java weblogic.WLST oif-upgrade-11.1.1.2.0-11.1.1.7.0.py
    

    On Microsoft Windows operating systems:

    cd ORACLE_HOME\fed\scripts
    java weblogic.WLST oif-upgrade-11.1.1.4.0-11.1.1.7.0.py
    

    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.

5.7.4 Configuring Oracle Identity Management to Listen on Dual Network Addresses

If you are patching Oracle Identity Management to 11g Release 1 (11.1.1.7.0) from a version prior to 11.1.1.6.0, and you are changing your configuration from a machine listening on one network address to a machine listening on dual network addresses, you must do the following after applying the patch:

  1. Stop all servers and instances in your domain.

  2. Reset the value of IPv6 to false in the DOMAIN_HOME/bin/setDomainEnv.sh (on UNIX operating systems) or DOMAIN_HOME\bin\setDomainEnv.bat script (on Windows operating systems).

  3. Restart the servers and instances in your domain.

5.8 Post-Patching Tasks for Your WebLogic Server Domain

Your existing WebLogic Server Domain must be updated by performing the following tasks:

5.8.1 Updating the JDK

You will need to have the latest supported JDK version installed in your patched environment. Consult the System Requirements and Supported Platforms for Oracle Fusion Middleware 11gR1 document at http://www.oracle.com/technetwork/middleware/downloads/fmw-11gr1certmatrix.xls for the latest certified JDK versions for your patch set.

You can access the latest JDK from the Oracle Software Downloads page on the Oracle Technology Network at http://www.oracle.com/technetwork/indexes/downloads/index.html. Follow the installation instructions provided with each download.

5.8.2 Updating Fusion Middleware Shared Libraries

For each WebLogic Server domain, you must run the upgradeJRF() WLST command to update the shared libraries in your domain:

Note:

If you are patching Oracle WebCenter Portal, you do not need to run this command if you follow the directions in Chapter 6, "Patching Oracle WebCenter Portal".

  1. Stop all running instances, Managed Servers, Administration Server, and Node Manager in the domain. See "Starting and Stopping Oracle Fusion Middleware" in Oracle Fusion Middleware Administrator's Guide for more information.

  2. Start WLST.

    On UNIX operating systems:

    cd oracle_common/common/bin
    ./wlst.sh
    

    On Windows operating systems:

    cd oracle_common\common\bin
    wlst.cmd
    
  3. 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')
    

Note:

After you run this command, any custom changes that you have made to your setDomainEnv script will be lost. Oracle recommends that you keep your custom modifications in a separate script that is called by setDomainEnv in order to minimize the disruption that is caused when other domain templates are applied and the setDomainEnv script is regenerated.

If you have set IPv6 to false in your setDomainEnv script, this change will be overwritten when you run the upgradeJRF() command. Make sure you reset IPv6 to false in the setDomainEnv script after you run the upgradeJRF() command.

5.8.3 Updating Configurations and Stores

For each WebLogic Server domain, you must run the upgradeOpss() WLST command to update your configurations and stores from previous releases to Release 11.1.1.7.0 configurations and stores using a system-jazn-data file.

Note:

When running upgradeOpss for 11.1.1.7.0, you may receive a "File Not Found" error message for the audit-store.xml file. This error message can be ignored. The audit-store.xml file is provided after running the upgradeOpss script.

For more information on updating configurations and stores, see "Configuring File-Based Policy and Credential Stores" in the Oracle Fusion Middleware Security Guide.

Note:

If you are patching Oracle WebCenter Portal, you do not need to run this script if you follow the directions in Chapter 6, "Patching Oracle WebCenter Portal".

5.8.4 Enabling WS-AtomicTransaction

WS-AtomicTransaction is a web services feature 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:

  1. Edit the following file.

    On UNIX operating systems:

    DOMAIN_HOME/config/fmwconfig/policy-accessor-config.xml
    

    On Windows operating systems:

    DOMAIN_HOME\config\fmwconfig\policy-accessor-config.xml
    
  2. In the Interceptors section, add the following XML code:

    <interceptor name="ClientWSATInterceptor"
       class="oracle.j2ee.ws.client.transaction.ClientWSATInterceptor"
       category="transaction" />
    <interceptor name="ServerWSATInterceptor"
       class="oracle.j2ee.ws.server.transaction.ServerWSATInterceptor"
       category="transaction" />
    
  3. In the Interceptor Chains section:

    • <interceptor-ref name="ServerWSATInterceptor"/> should be added in the existing entry of SOAPServiceBindingInterceptorChain between the Context and RM interceptors. For example:

      <interceptor-chain name="SOAPServiceBindingInterceptorChain"
                            
      @ class="oracle.integration.platform.common.SOAPBindingInterceptorChain">
               <interceptor-ref name="MTOMInterceptor"/>
               <interceptor-ref name="BindingSecurityInterceptor"/>
               <interceptor-ref name="ServerAddressingInterceptor"/>
               <interceptor-ref name="MEXInterceptor"/>
               <interceptor-ref name="WSRMServerInterceptor"/>
      <interceptor-ref name="ServerWSATInterceptor"/>
               <interceptor-ref name="ContextInterceptor"/>    
               <interceptor-ref name="BindingManagementInterceptor"/>
      </interceptor-chain> 
      
    • <interceptor-ref name="ClientWSATInterceptor"/> should be added in the existing entry of SOAPReferenceBindingInterceptorChain between the Context and RM interceptors. For example:

      <interceptor-chain name="SOAPReferenceBindingInterceptorChain"
                            
      @ class="oracle.integration.platform.common.SOAPBindingInterceptorChain">
               <interceptor-ref name="BindingManagementInterceptor"/>
               <interceptor-ref name="ContextInterceptor"/>
      <interceptor-ref name="ClientWSATInterceptor"/>
               <interceptor-ref name="WSRMClientInterceptor"/>
               <interceptor-ref name="ClientAddressingInterceptor"/>
            
               <interceptor-ref name="BindingSecurityInterceptor"/>
               <interceptor-ref name="MTOMInterceptor"/>
      </interceptor-chain>
      

5.8.5 Optimizing Performance for WebLogic Server Domains on 64-Bit Platforms

If you are upgrading any existing 11g Oracle WebLogic Domain to Release 11.1.1.7.0, it is recommended to make the changes in the setDomainEnv file as described below to optimize performance:

if [ "${JAVA_USE_64BIT}" = "true" ] ; then
        if [ "${JAVA_VENDOR}" = "Oracle" ] ; then
                EXTRA_JAVA_PROPERTIES="-XXcompressedRefs:enable=TRUE
${EXTRA_JAVA_PROPERTIES}"
                export EXTRA_JAVA_PROPERTIES
        fi
fi
if [ "${JAVA_VENDOR}" = "Oracle" ] ; then
        EXTRA_JAVA_PROPERTIES="-XX:+UseLargePagesForHeap
${EXTRA_JAVA_PROPERTIES}"
        export EXTRA_JAVA_PROPERTIES
fi
 
 
EXTRA_JAVA_PROPERTIES="-Djps.auth.debug=false ${EXTRA_JAVA_PROPERTIES}"
export EXTRA_JAVA_PROPERTIES 

The applicable EXTRA_JAVA_PROPERTIES are described in

Table 5-6 Description of Parameters for EXTRA_JAVA_PROPERTIES

Property Description

-XXcompressedRefs

This option governs the use of compressed references, limiting all pointers stored on the heap to 32 bits. Compressed references use fewer Java heap resources and transport less data on the memory bus, thereby improving the performance. This option also frees space on the heap.

-XXcompressedRefs:enable=TRUE is applicable for the JRockit JVM running on a 64-bit operating system.

-XX:+UseLargePagesForHeap

This option enables the use of large pages (if they are available) for the Java heap and code in the JVM. Large pages allow your application to more effectively use the translation look-aside buffer (TLB) in the processor.

This option is applicable for the JRockit JVM.

-Djps.auth.debug

This option is used to make sure JPS debugging is turned off.

This option is applicable for all JVM types.


5.8.6 Updating the Plug-In Configuration When Using a Proxy with WebLogic Server

Due to security changes in WebLogic Server, if you are running a proxy module in front of your WebLogic Server, such as mod_wl_ohs for example, you will need to perform the steps mentioned in the Oracle Fusion Middleware Using Web Server 1.1 Plug-Ins with Oracle WebLogic Server.

In addition, if a load balancer or other software deployed in front of the web server and plug-in is the SSL termination point, and that product sets the WL-Proxy-SSL request header to true or false based on whether or not the client connected to it over SSL, you may to configure the WLProxySSL and WLProxySSLPassThrough parameters as described in "Parameters for Web Server Plug-Ins" in Oracle Fusion Middleware Using Web Server 1.1 Plug-Ins with Oracle WebLogic Server

5.9 Post-Patching Tasks for Oracle SOA Suite

This section contains the following topics for completing your Oracle SOA Suite patch:

Note:

Before you perform any of the tasks in this section, make sure you have completed the tasks in Section 5.8, "Post-Patching Tasks for Your WebLogic Server Domain".

5.9.1 Loading the Oracle SOA Suite Purge Scripts for Database Management

When the amount of data in Oracle Fusion Middleware databases grows very large, maintaining the databases can become difficult and can affect performance. Oracle Fusion Middleware 11g Release 1 (11.1.1.4.0) and later provide a set of tools that can help you purge the Oracle Fusion Middleware of unneeded data.

When a new Oracle Fusion Middleware user installs the latest Oracle SOA Suite schemas using the Repository Creation Utility (RCU), stored procedures required by the Oracle SOA Suite purge scripts are automatically installed in the database.

However, if you are running Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0) or Release 1 (11.1.1.3.0), these stored procedures are not installed automatically. As a result, after you run the Patch Set Assistant to update your Oracle SOA Suite schemas to the latest version, you must manually install the necessary database objects using the following procedure. This procedure is necessary if you want to use the purging capabilities provided by Oracle SOA Suite 11g Release 1 (11.1.1.4.0) or later:

  1. Locate, download, and unpack the latest Oracle Fusion Middleware 11g Repository Creation Utility (RCU) software archive.

    For more information, see "Obtaining RCU" in the Oracle Fusion Middleware Repository Creation Utility User's Guide.

    The directory where you unpack the RCU software is referred to as the RCU_HOME directory.

  2. Using SQLPlus, connect to the database where the Oracle SOA Suite schemas are installed using the database user that owns the SOAINFRA schema.

  3. Run the following script to load the database objects required for purging Oracle SOA Suite data:

    RCU_HOME/rcu/integration/soainfra/sql/soa_purge/soa_purge_scripts.sql
    
  4. Run the following script to load the database objects required for verifying the Oracle SOA Suite data in the database:

    RCU_HOME/rcu/integration/soainfra/sql/verify/soa_verify_scripts.sql
    

After you load the database objects using the provided SQL scripts, refer to "Managing Database Growth" in the Oracle Fusion Middleware Administrator's Guide for Oracle SOA Suite and Oracle Business Process Management Suite for more information.

5.9.2 Removing the tmp Folder for SOA Composer, BPM Workspace and B2B

This manual step must be performed if:

  • You are upgrading from any previous SOA release, the Admin tabs within B2B may not appear after you patch to the latest version.

  • You are upgrading Oracle SOA Composer from Release 11.1.1.2.0 or 11.1.1.3.0; the SOA Composer login screen may appear blank after you patch to the latest version.

  • You are upgrading Oracle BPM Workspace from Release 11.1.1.3.0; the Oracle BPM Workspace application will not start after you patch to the latest version.

To resolve these issues, do the following:

  1. Stop all servers (Administration Server and all Managed Servers).

  2. Remove the tmp directory in DOMAIN_HOME/servers/AdminServer (on UNIX operating systems) or DOMAIN_HOME\servers\AdminServer (on Windows operating systems).

  3. Remove the tmp directory in DOMAIN_HOME/servers/soa_server1 (on UNIX operating systems) or DOMAIN_HOME\servers\soa_server1 (on Windows operating systems).

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

  4. Start all the servers.

5.9.3 Updating the "BPEL Message Recovery Required" Warning Message Duration

The bpelRecoveryAlertDurationInDays key limits the BPEL Message Recovery Required inline warning message to be displayed only when recoverable BPEL messages have been created in the last seven days. The default setting of seven days can be changed. You cannot set this property to negative values such as -1 or to 0. In such cases, the key uses its default value (seven days).

To disable the alert message, use the bpelRecoveryStatus key. The duration value is not applicable to the flow trace alert message.

5.9.4 Updating MAXRECOVERATTEMPT Attribute to 2

When upgrading from Oracle SOA Release 11.1.1.4.0, 5.0 or 6.0 to the latest version, you must manually reset the MAXRECOVERATTEMPT attribute (default 0) to a non-zero value to correctly display activity recoverable messages.

Use Oracle Enterprise Manager Fusion Middleware Control to reset this System MBean Browser property:

  1. Access this page through one of the following options:

    From the SOA Infrastructure Menu... From the SOA Folder in the Navigator...
    1. Select SOA Administration > BPEL Properties.

    1. Right-click soa-infra.

    2. Select SOA Administration > BPEL Properties.


    The BPEL Service Engine Properties page is displayed.

  2. Click More BPEL Configuration Properties.

  3. In the Attributes tab, click MAXRECOVERATTEMPT.

  4. In the Value field, enter 2.

  5. Click Apply.

5.9.5 Updating the soa-infra Application in Warning State

If you have a Release 11.1.1.3.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.

Note:

This step is only applicable if your Release 11.1.1.4.0 software is updated from Release 11.1.1.3.0. If Release 11.1.1.4.0 is the only version you have installed and configured, then you do not need to perform this task.

If you want to fix this issue, you must create JMS connection factories and topics as follows:

  1. From the WebLogic Server Administration Console, navigate to Domain Structure>JMS Modules>SOAJMSModule and add the following objects:

    • jms/bpm/PeopleQueryConnectionFactory

    • jms/bpm/CubeCommandXAConnectionFactory

    • jms/bpm/PeopleQueryConnectionFactory

    • jms/bpm/MeasurementTopic

    • jms/bpm/PeopleQueryTopic

  2. Perform any other post-patching procedures required for your starting point and applicable components.

    NOTE: If you want to use the UMS adapter features, then follow the procedures as described in Section 5.9.11, "Extending the SOA Domain with UMS Adapter Features".

  3. Restart the WebLogic Server and Administration Console.

5.9.6 Running bpm-ps6-upgrade.py to Update the Policy Store

To update your policy store to add the new Code Source Permissions, run the bpm-ps6-upgrade.py script from the bin directory inside your SOA Oracle home. You do not need to run this script if you are starting from version 11.1.1.5.0 or 11.1.1.6.0.

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.

On a UNIX operating systems:

cd SOA_ORACLE_HOME/bin
../common/bin/wlst.sh bpm-ps6-upgrade.py

On a Windows operating system:

cd SOA_ORACLE_HOME\bin
..\common\bin\wlst.cmd bpm-ps6-upgrade.py

The command will prompt you for the following items of information:

  • Administrator username for your Oracle BPM domain.

  • Administrator password for your Oracle BPM domain.

  • Host name and Administration Server listen port number where your WebLogic Server/Oracle BPM domain are installed. This should be specified in the following format:

    t3://host:port
    

After the script has completed, stop and restart all the servers as described in "Starting and Stopping Oracle WebLogic Server Instances" in the Oracle Fusion Middleware Administrator's Guide.

5.9.7 Running soa-upgrade.py to Update the Policy Store and Deploy a Shared Library

To update your policy store and deploy shared libraries, 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.

If you are upgrading from Release 11.1.1.4.0 or earlier, make sure the Administration Server is the only server that is up and running before running this script. The other Managed Servers should be shut down.

If you are upgrading from all other previous releases, make sure the Administration Server and all other Managed Servers are up and running before running this script.

On a UNIX operating system:

cd SOA_ORACLE_HOME/bin
../common/bin/wlst.sh soa-upgrade.py --targetList list_of_SOA_servers_or_migratable_targets

On a Windows operating system, run wlst.cmd from the same directory.

cd SOA_ORACLE_HOME\bin
..\common\bin\wlst.cmd soa-upgrade.py --targetList list_of_SOA_servers_or_migratable_targets

The command will prompt you for the following items of information:

  • Administrator username for your Oracle SOA domain.

  • Administrator password for your Oracle SOA domain.

  • Host name and Administration Server listen port number where your WebLogic Server/Oracle SOA domain are installed. This should be specified in the following format:

    t3://host:port
    

After running this command, stop and restart all the servers.

5.9.8 Updating the Oracle Data Integrator Clients if BAM-ODI Integration is Enabled

If you are currently using Oracle BAM and Oracle Data Integrator (ODI) integration, you must re-run an installation script to update your ODI clients after patching 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.

For each such domain, you must run the SOA_ORACLE_HOME/bam/bin/bam_odi_configuration.sh (on UNIX operating systems) or SOA_ORACLE_HOME\bam\bin\bam_odi_configuration.bat (on Microsoft Windows operating systems) script. Use the PATCH command line parameter to copy the Oracle BAM artifacts. For details, see "Using Oracle Data Integrator With Oracle BAM" in Oracle Fusion Middleware Developer's Guide for Oracle SOA Suite.

If ODI and Oracle BAM Server are installed on hosts in different networks, or for any reason you cannot use the script in your environment, you must manually do the following to update your ODI clients:

  1. Using the Middleware home directory under which Oracle BAM is installed, generate a wlfullclient.jar file by using the instructions in "Using the WebLogic JarBuilder Tool" in Oracle Fusion Middleware Programming Stand-alone Clients for Oracle WebLogic Server.

  2. Copy wlfullclient.jar to the ODI_ORACLE_HOME/lib/weblogic (on UNIX operating systems) or ODI_ORACLE_HOME\lib\weblogic (on Windows operating systems) directory.

  3. Copy the following Oracle BAM .jar files to the lib directory in the ODI Oracle home:

    On UNIX operating systems:

    SOA_ORACLE_HOME/bam/modules/oracle.bam_11.1.1/oracle-bam-common.jar
    SOA_ORACLE_HOME/bam/modules/oracle.bam_11.1.1/oracle-bam-etl.jar
    SOA_ORACLE_HOME/bam/modules/oracle.bam_11.1.1/oracle-bam-adc-ejb.jar
    SOA_ORACLE_HOME/bam/modules/oracle.bam.thirdparty_11.1.1/commons-codec-1.3.jar
    SOA_ORACLE_HOME/bam/modules/oracle.bam.thirdparty_11.1.1/xstream-1.3.1.jar
    oracle_common/modules/oracle.odl_11.1.1/ojdl.jar
    oracle_common/modules/oracle.jps_11.1.1/jps-api.jar
    oracle_common/modules/oracle.dms_11.1.1/dms.jar
    oracle_common/modules/org.jaxen_1.1.1.jar
    

    On Windows operating systems:

    SOA_ORACLE_HOME\bam\modules\oracle.bam_11.1.1\oracle-bam-common.jar
    SOA_ORACLE_HOME\bam\modules\oracle.bam_11.1.1\oracle-bam-etl.jar
    SOA_ORACLE_HOME\bam\modules\oracle.bam_11.1.1\oracle-bam-adc-ejb.jar
    SOA_ORACLE_HOME\bam\modules\oracle.bam.thirdparty_11.1.1\commons-codec-1.3.jar
    SOA_ORACLE_HOME\bam\modules\oracle.bam.thirdparty_11.1.1\xstream-1.3.1.jar
    oracle_common\modules\oracle.odl_11.1.1\ojdl.jar
    oracle_common\modules\oracle.jps_11.1.1\jps-api.jar
    oracle_common\modules\oracle.dms_11.1.1\dms.jar
    oracle_common\modules\org.jaxen_1.1.1.jar
    
  4. Copy the following Oracle BAM Knowledge Modules from the SOA_ORACLE_HOME/bam/ODI/knowledge_modules (on UNIX operating systems) or SOA_ORACLE_HOME\bam\ODI\knowledge_modules (on Windows operating systems) directory to the ODI_HOME/lib (on UNIX operating systems) or ODI_HOME\lib (on Windows operating systems) directory:

    KM_CKM Get Oracle BAM Metadata.xml
    KM_IKM SQL to Oracle BAM (delete).xml
    KM_IKM SQL to Oracle BAM (insert).xml
    KM_IKM SQL to Oracle BAM (looksert natural).xml
    KM_IKM SQL to Oracle BAM (looksert surrogate).xml
    KM_IKM SQL to Oracle BAM (update).xml
    KM_IKM SQL to Oracle BAM (upsert).xml
    KM_LKM Get Source Metadata.xml
    KM_LKM Oracle BAM to SQL.xml
    KM_RKM Oracle BAM.xml
    
  5. Backup the following ODI_HOME configuration files.

    On UNIX operating systems:

    ODI_HOME/lib/bam_odi.logging.properties
    ODI_HOME/lib/config/BAMODIConfig.xml
    

    On Windows operating systems:

    ODI_HOME\lib\bam_odi.logging.properties
    ODI_HOME\lib\config/BAMODIConfig.xml
    
  6. 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
    

5.9.9 Saving and Restoring XEngine Customizations for Oracle B2B

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:

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

    MW_HOME/SOA_ORACLE_HOME/soa/thirdparty/edifecs/XEngine
    

    For example, on a UNIX operating system:

    cp -pr SOA_ORACLE_HOME/soa/thirdparty/edifecs/XEngine backup_location
    
  2. Run the Installer to update the software.

  3. Unzip the XEngine ZIP file in the following directory:

    MW_HOME/SOA_ORACLE_HOME/soa/thirdparty/edifecs/XEngine
    

    For example, on a UNIX operating system:

    cd SOA_ORACLE_HOME/soa/thirdparty/edifecs
    gunzip XEngine.tar.gz
    tar -xvf XEngine.tar
    
  4. Restore only the customized configuration files from your backup location.

    For example, if you made changes to the XERegistry.xml file on a UNIX operating system:

    cp backup_location/config/XERegistry.xml 
         SOA_ORACLE_HOME/soa/thirdparty/edifecs/XEngine/config
    

5.9.10 Configuring Oracle JMS Adapter with IBM WebSphere MQ JMS

This step is needed if you are upgrading Oracle SOA Suite from release 11.1.1.2.0 or earlier to the latest release, and you have developed and deployed composites that leverage the Oracle JMS Adapter to access JMS messages that are utilizing IBM WebSphere MQ for message transport/persistence services.

If the Outbound Connection Pool entry created for the JMS Adapter is to be used with Topics, you must use the following additional connection property, which must be added to the end of the connection factory properties for Outbound Connection Pool entry:

ThirdPartyJMSProvider=true

For more information, see "Configuring Oracle JMS Adapter with IBM WebSphere MQ JMS" in Oracle Fusion Middleware User's Guide for Technology Adapters.

5.9.11 Extending the SOA Domain with UMS Adapter Features

This manual step is needed if you are upgrading your Oracle SOA Suite from release 11.1.1.6.0 or earlier to the latest release, and you want to enable the new User Messaging Service (UMS) Adapter features.

  1. Stop all Admin and Managed Servers as described in "Starting and Stopping Oracle WebLogic Server Instances" in the Oracle Fusion Middleware Administrator's Guide.

  2. Launch the Oracle WebLogic Configuration Wizard as described in "Starting the Configuration Wizard in Graphical Mode" in Oracle Fusion Middleware Creating Domains Using the Configuration Wizard.

  3. On the Select Extension Source screen of the Configuration Wizard, select Extend my domain using an existing extension template and specify the following path to the SOA upgrade extension template in the Template location field:

    SOA_HOME/common/templates/applications/oracle.soa_template_111160_111170.jar
    
  4. Continue through the remaining screens to complete the extension.

  5. Restart the Admin and Managed Servers as described in "Starting and Stopping Oracle WebLogic Server Instances" in the Oracle Fusion Middleware Administrator's Guide.

5.9.12 Extending the SOA Domain with Business Process Management Features

This manual step is needed if you are upgrading your Oracle SOA Suite from release 11.1.1.6.0 or earlier to the latest release, and you want to enable the new BPM features such as Case Management and Frevvo Webforms.

  1. Apply the SOA upgrade template as described in Section 5.9.11, "Extending the SOA Domain with UMS Adapter Features". This is a mandatory prerequisite.

  2. Stop all Admin and Managed Servers as described in "Starting and Stopping Oracle WebLogic Server Instances" in the Oracle Fusion Middleware Administrator's Guide.

  3. Launch the Oracle WebLogic Configuration Wizard as described in "Starting the Configuration Wizard in Graphical Mode" in Oracle Fusion Middleware Creating Domains Using the Configuration Wizard.

  4. On the Select Extension Source screen of the Configuration Wizard, select Extend my domain using an existing extension template and specify the following path to the BPM upgrade extension template in the Template location field:

    [SOA_HOME]/common/templates/applications/oracle.bpm_template_111160_111170.jar 
    
  5. Continue through the remaining screens to complete the extension.

  6. Restart the Admin and Managed Servers as described in "Starting and Stopping Oracle WebLogic Server Instances" in the Oracle Fusion Middleware Administrator's Guide.

5.10 Post-Patching Tasks for Oracle WebCenter Content

This section contains the following topics:

5.10.1 Updating Oracle WebCenter Content: Imaging

After updating your Oracle WebCenter Content software to Release 11.1.1.7.0 from any previous version, the manual steps in this section must be performed to target a newly distributed library to the Oracle WebCenter Content: Imaging deployment. If these steps are not performed, the Oracle WebCenter Content: Imaging Managed Server (default of IPM_server1) will not start.

  1. Make sure Oracle WebLogic Server is started, then open the Oracle WebLogic Server Administration Console:

    http://administration_server_host:administration_server_port/console
    
  2. For production systems, go to the "Change Center" portion of the navigation panel on the left and click Lock & Edit.

  3. Targeting the Oracle Application Core Stub file:

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

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

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

      The default location is MW_HOME/oracle_common/atgpf/modules/oracle.applcore.model_11.1.1 (on UNIX operating systems) or MW_HOME\oracle_common\atgpf\modules\oracle.applcore.model_11.1.1 (on Windows operating systems).

    4. Select the oracle.applcore.model.stub.ear file and click Next.

    5. Select Install this deployment as a library and click Next.

    6. Select IPM_server1 as the deployment target and click Next.

    7. Click Finish.

  4. Targeting the Oracle SOA Libraries file for BPM:

    Note:

    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.

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

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

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

      The default location is ECM_ORACLE_HOME/soa/modules/oracle.soa.workflow_11.1.1 (on UNIX operating systems) or ECM_ORACLE_HOME\soa\modules\oracle.soa.workflow_11.1.1 (on Windows operating systems).

    4. Select the oracle.soa.workflow.wc.jar file and click Next.

      A message indicating errors while parsing the deployment will appear in the "Messages" box at the top of the screen. The configuration will treat this as a library deployment. This is expected.

    5. Select IPM_server1 as the deployment target and click Next.

    6. Click Finish.

  5. For production systems, go to the "Change Center" portion of the navigation panel on the left and click Activate Changes.

  6. Any instances of the IPM Managed Server must be restarted for this change to take effect.

  7. Redeploy the imaging.ear file that is installed by the patch set.

    The imaging.ear file is saved by the installer to the following directory:

    ECM_ORACLE_HOME/ipm/lib/imaging.ear
    ECM_ORACLE_HOME\ipm\lib\imaging.ear
    

    To redeploy the EAR file, you can use the command-line, or you can use the Oracle WebLogic Server Administration Console:

    • For information about redeploying an EAR file in from the Administration Console, see "Update (redeploy) an Enterprise application" in the Oracle Fusion Middleware Oracle WebLogic Server Administration Console Online Help.

    • From the command-line, you can use the Oracle WebLogic Server deployer command; for example:

      java weblogic.Deployer -redeploy -name appName
      

      Where appName is the name of the EAR file as defined in the config.xml file.

    • You can also redeploy using the WLST redeploy() command:

      redeploy("appName")
      

      For more information about the redeploy() WLST command, see "redeploy" in Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.

5.10.2 Updating Oracle Application Adapters for Oracle WebCenter Content

The Oracle WebCenter Content application adapters as described in Oracle WebCenter Administrator's Guide for Application Adapters contain manual steps for installing the adapters to their respective ERP system (EBS and PeopleSoft). In order to update to from any previous release to Release 11.1.1.7.0, these adapters must be reinstalled.

To reinstall the EBS adapter:

  1. Follow the instructions in "Compiling Oracle E-Business Suite Forms" in Oracle WebCenter Administrator's Guide for Application Adapters to update the AXF_CUSTOM.PLL module.

  2. If you are configured for SSL, follow the instructions in "Configuring the Integration for SSL" in Oracle WebCenter Administrator's Guide for Application Adapters.

To re-import the PeopleSoft project, follow the instructions (steps 1-6) in "Importing the Oracle PeopleSoft Project" in Oracle WebCenter Administrator's Guide for Application Adapters.

5.10.3 Configuring the Report Library for Records Management in Content Server

If you plan to configure the Records Management feature in Content Server, you need configure the report library for Records Management after creating the domain that includes the WebCenter Content Managed Server, before starting it for the first time. Without this library, you cannot check in any templates to Content Server.

For more information on configuring the report library for Records Management, see "Configuring the Report Library for Records Management in Content Server" in the Oracle WebCenter Content Installation Guide.

5.10.4 Extending the IPM Domain to Include Viewer Cache

If you plan to take advantage of the Viewer Cache feature, or if you were already using it in a previous version of IPM (11.1.1.4.0 or 11.1.1.5.0) that was delivered in a previous patch, then you will need to extend the IPM domain with a new separately packaged Viewer Cache component.

  1. Run the Configuration Wizard:

    cd $ORACLE_HOME/common/bin
    ./config.sh
    
  2. On the Welcome screen, select "Extend an existing WebLogic domain".

  3. On the Select a WebLogic Domain Directory screen, select the domain in which IPM is currently configured. The folder icon of domains in the tree presentation will be designated differently with a small ball on the folder image. By default the domain name provided by the ECM install is base_domain.

  4. On the Select Extension Source screen, select the "Oracle WebCenter Content: Imaging Viewer Cache - 11.1.1.0 [...]".

    Note:

    If you are applying the patch to a system that was upgraded from a previous IPM version (11.1.1.4.0 or 11.1.1.5.0) in which the Viewer Cache was present, you will encounter a dialog titled "Conflict Detected". This message indicates that Component Named "Viewer JMS ConnectionFactory" is already defined. Choose the "Replace existing component" option.

  5. Click Next to move through the remaining configuration screens without making changes. No further changes are required to extend the domain.

  6. On the Configuration Summary screen, click Extend to complete the domain extension.

  7. Restart the Administration Server.

  8. The Viewer Cache remains inactive until it is configured. You must perform the steps described in "Configuring the Imaging Viewer Cache" in Oracle WebCenter Content Installation Guide to fully enable Viewer Cache.

5.11 Post-Patching Tasks for Oracle Service Bus

Follow the instructions in this section to update your Oracle Service Bus Release 11.1.1.2.0 or 11.1.1.3.0 domain configuration information to the latest release, after you have patched your Oracle Service Bus software:

5.11.1 Updating an Oracle Service Bus Domain After Applying the Latest Patch Set

To update your Oracle Service Bus domain configuration information:

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

  2. Under each Oracle Service Bus domain to be updated, 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.

  3. In the command window, switch to the directory in which the update scripts resides:

    OSB_ORACLE_HOME/common/lib/upgrade

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

    (UNIX) java weblogic.WLST ./domainUpgrade.py
    (Windows) java weblogic.WLST domainUpgrade.py
    

5.11.2 Using Oracle Service Bus Release 11.1.1.7.0 with WebLogic Server 10.3.5

Oracle Fusion Middleware 11g Release 1 (11.1.1.7.0) supports both Oracle WebLogic Server release 10.3.5 and 10.3.6. However, if you have already configured Oracle Service Bus with Oracle WebLogic Server 10.3.5 and you want to update Oracle Service Bus with Oracle Service Bus IDE to 11g Release 1 (11.1.1.7.0), then you must also update Oracle WebLogic Server to release 10.3.6. Oracle WebLogic Server 10.3.5 is not supported in an Oracle Service Bus IDE 11g Release 1 (11.1.1.7.0) environment.

If you must update Oracle Service Bus to 11g Release 1 (11.1.1.7.0), and you want to keep your Oracle WebLogic Server release at 10.3.5, then you must disable Oracle Service Bus IDE by manually deleting the following file:

(UNIX) MW_HOME/oepe_11.1.1.8.0/dropins/oracle.osb.ide.lnk
(Windows) MW_HOME\oepe_11.1.1.8.0\dropins\oracle.osb.ide.lnk 

5.11.3 Using Oracle Service Bus Release 11.1.1.7.0 with WebLogic Server 10.3.6

If you installed the latest version of Oracle WebLogic Server (version 10.3.6), and you updated Oracle Service Bus to 11g Release 1 (11.1.1.7.0), then you must install the required patches as described on the "Known Issues for Oracle SOA Products and Oracle AIA Foundation Pack" page on Oracle Technology Network at:

http://www.oracle.com/technetwork/middleware/docs/aiasoarelnotesps6-1866030.html

5.11.4 Performing Additional Post-Update Tasks for Oracle Service Bus IDE

If you are using Oracle Service Bus IDE in your environment, this section describes the required tasks after updating your Oracle Service Bus software to the latest version.

5.11.4.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.6) 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:

  1. Select Oracle WebLogic Server 11g Release 1 (10.3.3), right click and select Delete option.

  2. Uncheck Stop server(s) before deleting and click OK.

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

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

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

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

  4. The Server name is for display purposes in Eclipse.

  5. Click Next.

  6. 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). The default WebLogic home directory is called wlserver_10.3.

    For example, if you are creating a new server in MW_HOME_1, select the MW_HOME_1/wlserver_10.3; or if you are connecting to an existing server domain in MW_HOME_2, select the MW_HOME_2/wlserver_10.3.

    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.

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

  8. Click Next.

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

      For information on creating a new Oracle Service Bus domain, see "Configuring Oracle Service Bus" in the Oracle Fusion Middleware Installation Guide for Oracle Service Bus.

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

  10. Click Next.

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

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

5.12 Post-Patching Tasks for Oracle Business Intelligence

This section contains instructions for post-patching tasks for Oracle Business Intelligence. It contains the following topics:

Note:

Before you continue, make sure you have performed the tasks in Section 5.6, "Post-Patching Tasks for System Components" to update your Oracle Business Intelligence system components.

5.12.1 Updating Oracle Business Intelligence Code Grants

If you are updating to the latest version of Oracle Business Intelligence (BI) from Release 11.1.1.3.0, you must run the bi-upgrade.py script in each Oracle BI domain. This script configures the code grants necessary to ensure that SSL works correctly for Oracle BI, and must be run even if SSL is not used.

To run the script on UNIX operating systems:

cd MW_HOME/oracle_common/common/bin
./wlst.sh BI_ORACLE_HOME/bin/bi-upgrade.py --bioraclehome BI_ORACLE_HOME  --domainhome bi_domain_home

To run the script on Windows operating systems:

cd MW_HOME\oracle_common\common\bin
wlst.cmd BI_ORACLE_HOME\bin\bi-upgrade.py --bioraclehome BI_ORACLE_HOME  --domainhome bi_domain_home

Replace BI_ORACLE_HOME with the full path to your Business Intelligence Oracle home location, and replace bi_domain_home with the full path to your Business Intelligence domain home location.

5.12.2 Updating Oracle BI Presentation Catalogs

When updating your Oracle Business Intelligence (BI) software from Release 11.1.1.3.0, 11.1.1.5.0 or 11.1.1.6.x, you must manually update your Oracle BI Presentation Catalogs. Instructions are provided below:

  1. Stop Oracle BI Presentation Services using Oracle Enterprise Manager.

    For details, see "Using Fusion Middleware Control to Start and Stop Oracle Business Intelligence System Components and Java Components" in Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition.

  2. Back up your Release 11.1.1.3.0, 11.1.1.5.0 or 11.1.1.6.x catalogs by using the 7-Zip utility to create a compressed file for it.

  3. Create a backup copy of the instanceconfig.xml file.

    The instanceconfig.xml file is located in the ORACLE_INSTANCE/config/OracleBIPresentationServicesComponent/coreapplication_obipsn (on UNIX operating systems) or ORACLE_INSTANCE\config\OracleBIPresentationServicesComponent\coreapplication_obipsn (on Windows operating systems) directory.

  4. Change the upgradeAndExit option to true in the instanceconfig.xml file.

    Find the following code:

    <Catalog>
       <UpgradeAndExit>false</UpgradeAndExit>
    </Catalog> 
    

    Change it to the following:

    <Catalog>
       <UpgradeAndExit>true</UpgradeAndExit>
    </Catalog> 
    
  5. Start Oracle BI Presentation Services using the following OPMN command to update the catalogs:

    opmnctl startproc ias-component=coreapplication_obipsn 
    

    For example, on a UNIX operating system:

    cd ORACLE_INSTANCE/bin
    ./opmnctl startproc ias-component=coreapplication_obips1
    

    On a Windows operating system:

    cd ORACLE_INSTANCE\bin
    opmnctl startproc ias-component=coreapplication_obips1
    
  6. After the catalogs are updated, edit the instanceconfig.xml file again and change the upgradeAndExit option back to false.

  7. Restart Oracle BI Presentation Services using Fusion Middleware Control.

5.12.3 Enabling bicontentserver Features

If you are upgrading Oracle Business Intelligence from 11g Release 1 (11.1.1.5.0), you must perform the following if you want to enable the bicontentserver configuration template features:

  1. Make sure all processes in the domain are stopped, including all Oracle instances, the Administration Server, all Managed Servers, and Node Manager.

  2. Start the Configuration Wizard.

    On UNIX operating systems:

    cd WLHOME/common/bin
    where WLHOME is the directory in which WebLogic Server is installed.
    
    ./config.sh
    

    On Windows operating systems:

    cd WLHOME\common\bin
    config.bat
    
  3. On the Welcome screen, select Extend an existing WebLogic domain.

  4. On the Select a WebLogic Domain Directory screen, select the location of your existing Oracle BI domain.

  5. On the Select Extension Source screen, select Extend my domain using an existing extension template and select the following:

    On UNIX operating systems:

    ORACLE_HOME/common/templates/applications/oracle.bicontentserver_template_11.1.1.jar
    

    On Windows operating systems:

    ORACLE_HOME\common\templates\applications\oracle.bicontentserver_template_11.1.1.jar
    
  6. Continue with the remainder of the Configuration Wizard screens to apply this template.

  7. After the template is applied, restart all Oracle Instances, the Administration Server, Managed Servers, and Node Manager.

5.12.4 Enabling Oracle Business Intelligence Composer Features

If you are upgrading Oracle Business Intelligence from 11g Release 1 (11.1.1.x), you must perform the following if you want to enable the Oracle BI Composer or Oracle BI Composer Runtime configuration template features:

  1. Make sure all processes in the domain are stopped, including all Oracle instances, the Administration Server, all Managed Servers, and Node Manager.

  2. Start the Configuration Wizard.

    On UNIX operating systems:

    cd WLHOME/common/bin
    where WLHOME is the directory in which WebLogic Server is installed.
    
    ./config.sh
    

    On Windows operating systems:

    From the Start Menu, launch the Configuration Wizard for WebLogic from the WebLogic Server\Tools\WebLogic Server menu option.

  3. On the Welcome screen, select Extend an existing WebLogic domain.

  4. On the Select a WebLogic Domain Directory screen, select the location of your existing Oracle BI domain.

  5. On the Select Extension Source screen, select Extend my domain using an existing extension template and enter the location of the oracle.bicomposer_template_11.1.1.jar file.

    On Unix operating systems enter a command such as the following:

    ORACLE_HOME/common/templates/applications/oracle.bicomposer_template_11.1.1.jar

  6. Continue with the remainder of the Configuration Wizard screens to apply this template.

  7. After the template is applied, restart all Oracle Instances, the Administration Server, Managed Servers, and Node Manager.

    Note:

    After you perform the steps in this section, you must edit an MBean to enable Oracle BI Composer. For information, see "Manually Enabling BI Composer" in Oracle Fusion Middleware Upgrade Guide for Oracle Business Intelligence.

5.12.5 Enabling JBIPS Features

If you are upgrading Oracle Business Intelligence from 11g Release 1 (11.1.1.x), and you want to enable the Oracle BI JBIPS configuration template features, you must perform the following:

  1. Make sure all processes in the domain are stopped, including all Oracle instances, the Administration Server, all Managed Servers, and Node Manager.

  2. Start the Configuration Wizard.

    On UNIX operating systems:

    cd WLHOME/common/bin
    where WLHOME is the directory in which WebLogic Server is installed.
    
    ./config.sh
    

    On Windows operating systems:

    From the Start Menu launch the Configuration Wizard for WebLogic from the Programs > Oracle WebLogic > WebLogic Server > Tools > Configuration Wizard menu option.

  3. On the Welcome screen, select Extend an existing WebLogic domain.

  4. On the Select a WebLogic Domain Directory screen, select the location of your existing Oracle BI domain.

  5. On the Select Extension Source screen, select Extend my domain automatically to support the following added products and select Oracle JBIPS 11.1.1.7.0.

  6. Continue with the remainder of the Configuration Wizard screens to apply this template.

  7. Review the Configuration Summary screen and verify that the JBIPS Enterprise Web application and the following JBIPS shared libraries are listed:

    • oracle.bi.jbips

    • oracle.bi.jbips.commons

    • oracle.bi.jbips.soap

    NOTE: The JBIPS Web application and JBIPS shared libraries must be deployed to the same target as Analytics web application. The default target is "bi_cluster".

  8. After the template is applied, restart all Oracle Instances, the Administration Server, Managed Servers, and Node Manager.

    You should see "jbips (11.1.1)" Enterprise Application and the JBIPS shared libraries in the list of deployed modules in the Weblogic Administration Console.

5.12.6 Updating Oracle Real-Time Decisions

This section describes how to update Oracle Real-Time Decisions (RTD) to the latest patch set. The following steps are required only if you are patching from 11g Release 1 (11.1.1.3.0); you do not need to perform these steps if you are patching from 11g Release 1 (11.1.1.5.0).

5.12.6.1 Updating the rtd_ils Resource Type Using WLST

Perform the following to add actions to the rtd_ils resource type:

  1. Navigate to the MW_HOME/oracle_common/common/bin (on UNIX operating systems) or MW_HOME\oracle_common\common\bin (on Windows operating systems) directory.

  2. Launch the WebLogic Scripting Tool (WLST).

    On UNIX operating systems:

    ./wlst.sh
    

    On Windows operating systems:

    wlst.cmd
    
  3. Connect to the WebLogic Server using the connect() command:

    connect('adminuser', 'adminuser_password', 't3://admin_server_host:admin_server_port')
    

    Replace adminuser and adminuser_password with the name and password of the Administrator you provided during the Oracle BI installation. Replace admin_server_host and admin_server_port with the host name and port number of the system where Oracle WebLogic Server is running. Below is a sample command:

    connect('exampleuser', 'examplepassword', 't3://examplehost:7001')
    
  4. List all resources of the resource type "rtd_ils" using the following command:

    listResources(appStripe="obi", type="rtd_ils")
    

    This will list all ILS's deployed to the RTD server. For example, if the sample ILS CrossSell was deployed to your RTD server, you would see the following:

    [Name: CrossSell Type: rtd_ils DisplayName: CrossSell Description: CrossSell ]
    
  5. Delete all resources of resource type "rtd_ils" using the following command:

    deleteResource(appStripe="obi", name=resource_name, type="rtd_ils")
    

    For example, the following command would delete the CrossSell resource:

    deleteResource(appStripe="obi", name="CrossSell", type="rtd_ils")
    
  6. Run the listResources() command again to ensure all the resources have been deleted:

    listResources(appStripe="obi", type="rtd_ils")
    

    There should be no resources listed.

  7. Delete the resource type "rtd_ils":

    deleteResourceType(appStripe="obi", resourceTypeName="rtd_ils")
    
  8. Create a resource type "rtd_ils" using the following createResourceType() command:

    createResourceType(appStripe="obi",
    resourceTypeName="rtd_ils",
    displayName="ILS",
    description="Inline Service name",
    matcher="oracle.security.jps.ResourcePermission",
    allowedActions="choice_editor,decision_service:stress,open_service:write,decision_service:normal,open_service:read,deploy_service,download_service,clear_choice_history,clear_statistics,clear_study,clear_all_operational_data,delete_service,unlock_service,clear_model",
    delimiter=",")
    
  9. Disconnect from Oracle WebLogic Server:

    disconnect()
    
  10. Exit from the WebLogic Scripting Tool:

    exit()
    

5.12.6.2 Adding Permissions to the BIAdministrator Principle Using EM

The steps in this section need to be performed if you are using the BIAdministrator principle included with the product, or if you have replaced the BIAdministrator principle included with the product with your own principle:

  1. Start Fusion Middleware Control using the following syntax:

    http://admin_server_host:admin_server_port/em
    
  2. In the left tree view, select Weblogic Domain / bifoundation_domain.

  3. In the content pane, select Security/Application Policies from the drop down "WebLogic Domain".

  4. Check Select Application Stripe to Search, and select "obi" from its drop down list.

  5. Leave the Principal and Permissions blank.

  6. Click the Search button next to the Permission field.

  7. From the search result, click on the Principal "BIAdministrator" (or the name of your own principle if you are not using "BIAdministrator").

  8. Click the Edit button.

  9. In the Edit Application Grant pane, go to the Permissions section and click the Add button.

  10. In the Add Permission dialog, under the Customize section, add the following entries:

    Permission Class: oracle.security.jps.ResourcePermission
    Resource Name: resourceType=rtd_ils,resourceName=_all_
    Permission Actions: clear_choice_history,clear_statistics,clear_study,clear_all_operational_data,delete_service,unlock_service,clear_model
    
  11. Click OK in the Add Permission dialog.

  12. Click OK in the Edit Application Grant pane.

5.12.6.3 Removing JMS

In earlier releases, Oracle RTD relied on JMS for its intra-member cluster communication. In the latest release, JMS is replaced with JRF web services. This is an optional step and no functionality will be affected if you choose not to perform this step.

To remove JMS for Oracle RTD:

  1. Using a browser, connect to the Administration Server Console:

    http://admin_server_host:admin_server_port/console
    
  2. Click Lock & Edit.

  3. Under Domain Structure, expand Services > Messaging.

  4. Click JMS Modules.

  5. On JMS Modules table in the right pane, select RTDJMSMODULE.

  6. Click the Delete button, then click the Yes button to confirm.

  7. On the left pane, click JMS Servers (under Services > Messaging).

  8. On the JMS Servers table on the right pane, select RTDJmsServer.

  9. Click the Delete button, then click the Yes button to confirm.

  10. Click the Activate Changes button.

5.13 Post-Patching Tasks for Oracle Data Integrator

This section contains instructions for post-patching tasks for Oracle Data Integrator. It contains the following topics:

5.13.1 Finalizing Repository Patching

After you have patched the Oracle Data Integrator schemas in your database (Chapter 4, "Updating Your Schemas with Patch Set Assistant"), you must update the following repository objects (technologies, profiles, knowledge modules), which are not updated with Patch Set Assistant:

  • Technology Changes

    • Added: ComplexFile and Groovy

    • Changed: Oracle

      • Natural keyword join was added

      • Join capability was extended to BOTH

      • Default table name prefixes were added

    • Changed: Teradata

    • Changed: PostgreSQL

    • Changed: Netezza

    • Changed: OracleBI

    • Changed: Hypersonic In-Memory Engine

    • Changed: PostgreSQL supports SQL for retrieving sequences

  • Language Changes: Groovy was added

  • Profile Changes

    Changes were made to LoadPlan support in the following profiles:

    • [NG] DESIGNER

    • [NG] REPOSITORY EXPLORER

    • [NG] VERSION ADMIN

    • OPERATOR

    • SECURITY_ADMIN

  • Knowledge Modules

    LKM File to Oracle (SQLLDR) works after removing 'import javaos' from KM step 'call sqlldr'. The old LKM no longer works with an upgraded Jython version.

For more information about how to update these repository objects, see "Oracle Data Integrator Post-Upgrade Tasks" in Oracle Fusion Middleware Upgrade Guide for Oracle Data Integrator.

5.13.2 Reconfiguring the Java EE Agent

By default, ODI ships a static Java EE Agent deployment template. To reconfigure the Java EE agent:

  1. Run the Configuration Wizard. On the Select Domain Source screen, select the Oracle Data Integrator – Agent – 11.1.1.0 template.

    For more information, see "Configure a WebLogic Domain" in Oracle Fusion Middleware Installation Guide for Oracle Data Integrator.

  2. On UNIX operating systems, check DOMAIN_HOME/bin/setDomainEnv.sh for the following line:

    -Dodi.oracle.home=${ODI_ORACLE_HOME}
    

    On Windows operating systems, check DOMAIN_HOME\bin\setDomainEnv.cmd for the following line:

    -Dodi.oracle.home=%ODI_ORACLE_HOME%
    

    On either operating system, if this line is not present, add it to the EXTRA_JAVA_PROPERTIES parameter.

  3. Make sure the Administrator Server and ODI Managed Servers are up and running.

  4. Add the WebLogic Server classes to the CLASSPATH environment variable and the WebLogic_Home/server/bin (on UNIX operating systems) or WebLogic_Home\server\bin (on Windows operating systems) directory to the PATH environment variable.

    This can be accomplished by sourcing the setWLSEnv script located in the WebLogic_Home/server/bin (on UNIX operating systems) or WebLogic_Home\server\bin (on Windows operating systems) directory. For example:

    source setWLSEnv.sh
    
  5. Redeploy the version 11.1.1.3.0 Java EE agent from your domain using the following command:

    java weblogic.Deployer -url admin_server_url -username admin_server_username -password admin_server_password -targets odi_server_name -name odi_agent_name –redeploy
    

    For example:

    java weblogic.Deployer -url t3://examplehost.com:7001 -username exampleuser -password examplepassword -targets odi_server1 -name oraclediagent –redeploy
    

    For more information, see "Managing Deployed Applications" in Oracle Fusion Middleware Deploying Applications to Oracle WebLogic Server.

ODI also enables you to generate a Java EE agent deployment template from ODI Studio. You can customize the Java EE agent with additional data sources and libraries. To do so:

  1. Undeploy the version 11.1.1.3.0 Java EE agent from your domain.

    For more information, see "Managing Deployed Applications" in Oracle Fusion Middleware Deploying Applications to Oracle WebLogic Server.

  2. Using ODI Studio version 11.1.1.7.0 or the command line script to generate equivalent Java EE agent template with required data sources and additional libraries.

    For more information on data source declaration, deployment and template generation in ODI Studio, see "Java EE Agent" in the Oracle Fusion Middleware Developer's Guide for Oracle Data Integrator.

  3. Run the Configuration Wizard. On the Select Domain Source screen, select Oracle Data Integrator – Agent Libraries– 11.1.1.0 to deploy the template.

  4. Run the Configuration Wizard a second time, and on the Select Domain Source screen, deploy the generated version 11.1.1.7.0 ODI Java EE agent template to the domain.

5.13.3 Reconfiguring the ODI Standalone Agent

To reconfigure the ODI standalone agent:

  1. Make sure you have backed up the necessary files and directories as described in "Section 3.4.6, "Backing Up Additional Configuration Information".

  2. Run the Oracle Data Integrator installer.

    On the Configure Repositories Install screen, choose Skip Repository Creation.

  3. After the installation is complete:

    • Restore the ODI_HOME/oracledi/agent/bin/odiparams.sh (on UNIX operating systems) or ODI_HOME\oracledi\agent\bin\odiparams.bat (on Windows operating systems) file.

    • Restore the ODI_HOME/oracledi/agent/drivers (on UNIX operating systems) or ODI_HOME\oracledi\agent\drivers (on Windows operating systems) directory.

For more information, see "Stopping a Standalone Agent" and "Manually Configure the Standalone Agent" in Oracle Fusion Middleware Installation Guide for Oracle Data Integrator.

5.13.4 Reconfiguring Oracle Enterprise Manager Properties

After you have patched Oracle Data Integrator, some of the properties in Oracle Enterprise Manager are lost. To restore these properties, set the following property before starting the Managed Server on which the Oracle Data Integrator Console is deployed:

set JAVA_OPTIONS="-Doracle.odi.repex.view.main.init.skipem=false"

5.13.5 Reconfiguring the ODI Console

If the domain created in Release 11.1.1.3.0 contains odiconsole components, reconfigure the odiconsole application as follows:

  1. Extend the domain with Oracle Shared SDK Library 11.1.1.0 and target the deployment to odi_server1.

  2. Set the CLASSPATH by running the Weblogic_Home/server/bin/setWLSEnv.sh (on UNIX operating systems) or Weblogic_Home\server\bin\setWLSEnv.cmd (on Windows operating systems) script.

  3. Start the Administration Server and the odi_server1 Managed Server.

  4. Redeploy the odiconsole application using the following command:

    java weblogic.Deployer -url administration_server_url -username administration_server_username -password administration_server_password -targets odi_server_name -name odi_console_name –redeploy
    

    For example:

    java weblogic.Deployer -url t3://examplehost.com:7001 -username exampleuser -password examplepassword -targets odi_server1 -name odiconsole –redeploy 
    

5.13.6 Adding the Version Number for the odi-sdk-ws Application in config.xml

As of 11g Release 1 (11.1.1.6.0), the odi-sdk-ws application was updated to introduce a version number. This version number must be added to the config.xml file prior to starting the Administration Server or Managed Servers in the domain for Releases 11.1.1.3.0, 11.1.1.4.0 or 11.1.1.5.0 to Release 11.1.1.7.0.

To do this:

  1. Edit the DOMAIN_HOME/config/config.xml (on UNIX operating systems) or DOMAIN_HOME\config\config.xml (on Windows operating systems) file.

  2. Change the following line:

    <name>odi-sdk-ws</name> 
    

    to add a version number, as shown below:

    <name>odi-sdk-ws#11.1.1.7.0.0</name> 
    
  3. Start or restart the Administration Server and Managed Servers in the domain.