This chapter contains information about manual tasks performed after the Release 11.1.1.9.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.
If you are patching WebCenter Portal, see Section 6.10, "Post Patching Tasks for Oracle WebCenter Portal".
This chapter includes the following topics:
Section 5.2, "Post-Patching Tasks If Your Starting Point is Release 11.1.1.2"
Section 5.3, "Post-Patching Tasks If Your Starting Point is Release 11.1.1.3"
Section 5.4, "Post-Patching Tasks If Your Starting Point is Release 11.1.1.4"
Section 5.5, "Post-Patching Tasks If Your Starting Point is Release 11.1.1.5"
Section 5.6, "Post-Patching Tasks If Your Starting Point is Release 11.1.1.6"
Section 5.7, "Post-Patching Tasks If Your Starting Point is Release 11.1.1.7"
Section 5.8, "Post-Patching Tasks If Your Starting Point is Release 11.1.1.8"
Most components requires some post-patching configuration tasks. Review the common post-patching tasks in this section to determine if your upgraded environment requires any additional configurations.
To start the WebLogic Administration Server and the Managed Server(s), refer to the following sections:
Note:
You must start the Node Manager, the WebLogic Administration Server, and the Managed Servers with Java Secure Socket Extension (JSSE) enabled, if you have applied the following Oracle WebLogic Server patches to your Middleware home:13964737 (YVDZ)
14174803 (IMWL)
These patches are available from My Oracle Support.
For information on how to start the Node Manager with JSSE enabled, see the "Set the Node Manager Environment Variables" topic in the Administering Node Manager for Oracle WebLogic Server.
After starting Node Manager with JSSE enabled, you must start the Administration Server and Managed Servers with JSSE enabled. For more information, see the "Using the JSSE-Enabled SSL Implementation" topic in Administering Security for Oracle WebLogic Server.
To start the Node Manager, you must run the command startNodeManager.sh (on UNIX) or startNodeManager.cmd (on Windows) from the location $WL_HOME/server/bin.
For more information, see "startNodeManager" in the Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.
To start the WebLogic Administration Server, do the following:
On UNIX:
Run the following commands:
cd MW_HOME/user_projects/domains/domain_name/bin
./startWebLogic.sh
On Windows:
Run the following commands:
cd MW_HOME\user_projects\domains\domain_name\bin
startWebLogic.cmd
To start the Managed Server(s), do the following:
On UNIX:
Move from your present working directory to the MW_HOME/user_projects/domains/domain_name/bin directory by running the following command on the command line:
cd MW_HOME/user_projects/domains/domain_name/bin
Run the following command to start the Managed Servers:
./startManagedWebLogic.sh managed_server_name admin_url admin_username password
where
managed_server_name is the name of the Managed Server
admin_url is URL of the administration console. Specify it in the format http://host:port/console. Specify only if the WebLogic Administration Server is on a different computer.
admin_username is the username of the WebLogic Administration Server.
password is the password of the WebLogic Administration Server.
For example:
./startManagedWebLogic.sh soa_server1 http://host.example.com:7001/console weblogic password123
On Windows:
Move from your present working directory to the MW_HOME\user_projects\domains\domain_name\bin directory by running the following command on the command line:
cd MW_HOME\user_projects\domains\domain_name\bin
Run the following command to start the Managed Servers:
startManagedWebLogic.cmd managed_server_name admin_url admin_username password
where
managed_server_name is the name of the Managed Server.
admin_url is URL of the administration console. Specify it in the format http://host:port/console. Specify only if the WebLogic Administration Server is on a different computer.
admin_username is the username of the WebLogic Administration Server.
password is the password of the WebLogic Administration Server.
For example:
startManagedWebLogic.cmd soa_server1 http://host.example.com:7001/console weblogic password123
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
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
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
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
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
Table 5-6 summarizes the post-patching tasks that may be required depending on your existing Release 11.1.1.7.0 environment. Locate the applicable product area in the table, then refer to the documentation link for instructions.
Table 5-6 Post-Patching Tasks If Your Starting Point is Release 11.1.1.7.0
| Product Area | Documentation |
|---|---|
|
Oracle Directory Integration Platform |
|
|
Oracle Directory Integration Platform (DIP) Support with Oracle Unified Directory (OUD) and Oracle Directory Server Enterprise Edition (ODSEE) |
|
|
Oracle Identity Management Components, if you plan to use Oracle Enterprise Manager to view metrics and configuration settings. |
|
|
Oracle Service Bus |
|
|
Oracle Service Bus Configuration Information |
Section 5.14.1, "Upgrading an Oracle Service Bus Domain After Applying the Latest Patch Set" |
|
Oracle WebCenter Portal |
|
|
Patching procedures for Release 11.1.1.7.0 installation. |
Section 6.3, "Patching an Oracle WebCenter Portal 11.1.1.7.0 Installation" |
|
Oracle WebCenter Content |
|
|
Oracle WebCenter Content application adapters. |
Section 5.13.2, "Upgrading Oracle Application Adapters for Oracle WebCenter Content" |
|
Report Library for Records Management in Content Server. |
Section 5.13.3, "Configuring the Report Library for Records Management in Content Server" |
|
Inbound Refinery (IBR) |
Section 5.13.4, "Using Fusion Middleware Control to Monitor IBR" |
|
WebCenter Content Server |
Section 5.13.5, "Starting Oracle WebCenter Content Server with SOA or BAM" |
|
WebCenter Content System Components |
Section 5.13.6, "Enabling System Components for WebCenter Content" |
Table 5-7 summarizes the post-patching tasks that may be required depending on your existing Release 11.1.1.8.0 environment. Locate the applicable product area in the table, then refer to the documentation link for instructions.
Table 5-7 Post-Patching Tasks If Your Starting Point is Release 11.1.1.8.0
| Product Area | Documentation |
|---|---|
|
Oracle WebCenter Portal |
|
|
Patching procedures for WebCenter Portal |
|
|
Oracle WebCenter Content |
|
|
Oracle WebCenter Content ADF UI. |
Section 5.8.1, "Patching the ADF UI Domain for WebCenter Content" |
The ADF UI for WebCenter Content domain must be patched after upgrading the WebCenter Content domain to 11.1.1.9.0. The p19926432_111190_Generic.zip patch is located in the following directory:
ORACLE_HOME/ucm/Distribution/WccADFUI
The installation package, WccADFUI.zip, is also located in this directory.
For detailed instructions on applying the patch in the ADF UI environment, refer to the README.txt file included in the installation package.
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.10, "Post-Patching Tasks for Oracle Identity Management Components".
Note:
WebCenter Content users may need to perform additional tasks for enabling and disabling system components. See Section 5.13.6, "Enabling System Components for WebCenter Content" for more information.Oracle Fusion Middleware system components include the following:
Products included with Oracle Web Tier, including Oracle HTTP Server and Oracle Web Cache.
Products included with Oracle Identity Management, including Oracle Virtual Directory and Oracle Internet Directory.
Products included with Oracle Portal, Forms, Reports and Discoverer.
Products included with Oracle Business Intelligence, including BI Server, BI Scheduler and BI Presentation Services.
Products included with Oracle Data Integrator.
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:
Section 5.9.3, "Resolving JDBC Errors in Oracle Reports and Oracle Portal"
Section 5.11.6, "Upgrading the Plug-In Configuration When Using a Proxy with WebLogic Server"
Section 5.9.5, "Generating the BASE64 Encoded Encryption Key for OPSS"
Section 5.9.6, "Enabling Dynamic Audit Metadata Model for OPSS Running in JavaSE Mode"
Section 5.9.7, "Configuring Diagnostic Framework Dump Sampling"
Section 5.9.8, "Adding Batik Library Jar Files to the JRF Template for IBM WebSphere"
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 standalone 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 upgrade your system components.
Before running this script, make sure:
The Administration Server is up and running.
The ORACLE_HOME environment variable has been set to your product's Oracle home directory.
The OPMN instance in the bin directory in the Instance home is up and running.
On UNIX operating systems:
cd INSTANCE_HOME/bin
./opmnctl start
On Windows operating systems:
cd INSTANCE_HOME\bin
opmnctl start
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
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
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:
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
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.
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.
Restart the upgradenonj2eeapp script as described above and review the provisioning.log.
If you see: "Failed to unregister instance instance1, does not exist on the adminserver", continue to the next step.
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:
Restart the upgradenonj2eeapp script as described above. You should see "Successfully upgraded NonJ2EEManagement.ear and the registration."
If you are patching 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:
Go to the ORACLE_HOME\ccr\bin directory.
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
Run the following emCCR commands:
emccr collect emccr status
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:
Go to the bin directory inside your DOMAIN_HOME (user_projects by default).
Edit the setDomainEnv.sh (on UNIX operating systems) or setDomainEnv.cmd (on Windows operating systems) file and search for EXT_PRE_CLASSPATH.
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%
)
)
Restart the Portal Managed Server.
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 Data Files and Adding Data Files to a Tablespace" in Oracle Database Administrator's Guide.
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.9.0.
For more information on running OPSS in JSE mode, see "Configuring DB-Based OPSS Security Stores" in Securing Applications with Oracle Platform Security Services.
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.9.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 Securing Applications with Oracle Platform Security Services.
As of 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>
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 "upgradeADFLibrary" in the Administering Oracle ADF Applications.
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.
Note:
If you are upgrading Oracle Identity and Access Management components, such as Oracle Access Manager, Oracle Adaptive Access Manager or Oracle Identity Manager, see "Oracle Fusion Middleware Upgrade Guide for Oracle Identity and Access Management".If you want to use the new DIP features with Oracle Unified Directory (OUD) or Oracle Directory Server Enterprise Edition (ODSEE) after upgrading the Oracle WebLogic Server domain, then you must run the dipConfigurator update (<ORACLE_HOME>/bin) command on the command line and enter the following arguments:
Table 5-8 dipConfigurator Properties
| Properties | Description |
|---|---|
|
|
Oracle WebLogic Server host name where Oracle Directory Integration Platform is deployed. The default host name is |
|
|
Listening port number of the Oracle WebLogic Managed Server where Oracle Directory Integration Platform is deployed. The default port number is |
|
|
Oracle WebLogic Server login user name. |
|
|
Oracle Unified Directory host name. The default host name is |
|
|
Oracle Unified Directory server port number. The default value is |
|
|
Specify |
|
|
The default value is |
|
|
This parameter is used to specify the OUD administration port. The default value in 4444. NOTE: This parameter is only required when the backend is OUD. You do not need this parameter when the backend is ODSEE. |
Note:
You must start Directory Integration Platform before runningdipConfigurator. For information on starting DIP, see "Starting and Stopping Oracle Directory Integration Platform Using WLST" in Oracle Fusion Middleware Administrator's Guide for Oracle Directory Integration Platform
You can view the dipConfig.log file, located at <ORACLE_HOME>/ldap/log/.
Example:
cd $ORACLE_HOME/bin/ $ ./dipConfigurator update Enter WLS Admin Server Host Name [localhost] : machine_name Enter WLS Admin Server Port [7001] : 7001 Enter username to contact WebLogic Server : weblogic Enter password to contact WebLogic Server : Enter backend LDAP Server HostName [localhost] : machine_name Enter backend LDAP Server Port [636] : 1389 Enter if LDAP port is SSL enabled [true] : false Enter username to contact LDAP server : cn=orcladmin Enter password to contact LDAP Server : Enter LDAP Server Admin Port [4444] : 4444
Alternatively, you can use a single command line as shown below:
$ORACLE_HOME/bin/dipConfigurator update -wlshost localhost -wlsport 7001 -wlsuser weblogic -ldaphost localhost -ldapport 1389 -isldapssl false -ldapuser "cn=Directory Manager" -ldapadminport 4444
Once the dipConfigurator update command has been run, you can validate the results of the upgrade by executing the dipStatus command, which is located in the $ORACLE_HOME/bin/ directory. For more information, see "Verifying Oracle Directory Integration Platform" in Oracle Fusion Middleware Administrator's Guide for Oracle Directory Integration Platform.
You can also verify the Oracle Directory Integration Platform (ODIP) upgrade using the Oracle Enterprise Manager Fusion Middleware Control, as follows:
Log in to the Oracle Enterprise Manager Fusion Middleware Control.
In the navigation panel on the left, click or expand Identity and Access and then select the DIP component.
Click the DIP Server menu, point to Administration, and then select Server Properties.
Click Test Connection and verify the instance.
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.9.0.py script if:
You are upgrading your software from 11.1.1.2.0 or 11.1.1.3.0 to 11.1.1.9.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.9.0.py script if you are upgrading your software from 11.1.1.4.0 or 11.1.1.5.0 to 11.1.1.9.0.
Run the oif-upgrade-11.1.1.6.0-11.1.1.9.0.py script if you are upgrading your software from 11.1.1.6.0 to 11.1.1.9.0.
Run the oif-upgrade-11.1.1.7.0-11.1.1.9.0.py script if you are upgrading your software from 11.1.1.7.0 to 11.1.1.9.0.
The instructions to run the scripts are shown below:
On Linux operating systems, enter the bash command:
bash
Set the DOMAIN_HOME variable to your Oracle Identity Federation Domain home location.
Set the ORACLE_HOME variable to your Oracle Identity Federation Oracle home location.
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
Run the oif-upgrade-11.1.1.2.0-11.1.1.9.0.py, oif-upgrade-11.1.1.4.0-11.1.1.9.0.py, oif-upgrade-11.1.1.6.0-11.1.1.9.0.py or oif-upgrade-11.1.1.7.0-11.1.1.9.0.py script.
For example, on UNIX operating systems:
cd ORACLE_HOME/common/bin>wlst.sh $ORACLE_HOME/fed/scripts/oif-upgrade-11.1.1.2.0-11.1.1.9.0.py
On Microsoft Windows operating systems:
cd ORACLE_HOME\common\bin>wlst.cmd $ORACLE_HOME\fed\scripts\oif-upgrade-11.1.1.2.0-11.1.1.9.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.
If you are patching Oracle Identity Management components to 11g Release 1 (11.1.1.9) from a version prior to 11.1.1.6, and you want to use Oracle Enterprise Manager to view configuration settings and metrics for Oracle Virtual Directory, Directory Integration Platform or Oracle Unified Directory, you must do the following after applying the patch:
Navigate to the /lib directory of your WebLogic Server.
For example:
cd $WL_HOME/server/lib
Execute the following:
java -jar wljarbuilder.jar
Navigate to the /jlib directory of your Oracle Home.
For example:
cd $ORACLE_HOME/sysman/jlib
Copy the wlfullclient.jar file to ORACLE_HOME/sysman/jlib.
cp $WL_HOME/server/lib/wlfullclient.jar .
Stop and restart the EMAGENT:
$ORACLE_INSTANCE/bin/opmnctl stopproc ias-component=EMAGENT $ORACLE_INSTANCE/bin/opmnctl startproc ias-component=EMAGENT
Log in to the Oracle Fusion Middleware Control Console and verify that the Configuration Settings page is available for Oracle Virtual Directory or Oracle Internet Directory.
Your existing WebLogic Server Domain must be upgraded by performing the following tasks:
Section 5.11.1, "Upgrading Fusion Middleware Shared Libraries"
Section 5.11.5, "Optimizing Performance for WebLogic Server Domains on 64-Bit Platforms"
Section 5.11.6, "Upgrading the Plug-In Configuration When Using a Proxy with WebLogic Server"
For each WebLogic Server domain, you must run the upgradeJRF() WLST command to upgrade 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".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.
Start WLST.
On UNIX operating systems:
cd oracle_common/common/bin ./wlst.sh
On Windows operating systems:
cd oracle_common\common\bin wlst.cmd
Run the upgradeJRF() command on the node or system where the Administration Server is located for each domain you want to upgrade. 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 yoursetDomainEnv 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.
For each WebLogic Server domain, you must run the upgradeOpss() WLST command to upgrade your configurations and stores from previous releases to Release 11.1.1.9.0 configurations and stores using a system-jazn-data file.
Note:
When runningupgradeOpss for 11.1.1.9.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 upgrading configurations and stores, see "Configuring File-Based Policy and Credential Stores" in the Securing Applications with Oracle Platform Security Services.
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".For each WebLogic Server domain, you must run the upgradeWSM() WLST command to upgrade the Oracle WSM configuration and policies from a previous release (11.1.1.1.0–11.1.1.6.0) to Release 11.1.1.9.0.
The Oracle WSM configuration and policies will be upgraded, such as:
Any predefined policies that have not been customized for your environment are replaced, and any new policies are automatically added. Note, however, that predefined policies that have been customized and user-created custom policies in the repository are not replaced.
WS-Trust configuration, such as DNs and trusted issuers.
Custom roles for secure EJBs.
Note:
This command must be run as a WLST offline command. Therefore, make sure to stop all running instances, Managed Servers, Administration Server, and Node Manager in the domain. See "Starting and Stopping Oracle Fusion Middleware" in the Oracle Fusion Middleware Administrator's Guide for more information.To run the upgradeWSM() WLST command:
Start WLST offline.
On UNIX operating systems:
cd oracle_common/common/bin ./wlst.sh
On Windows operating systems:
cd oracle_common\common\bin wlst.cmd
Run the upgradeWSM() command on the node or system where the Administration Server is located for each domain you want to upgrade. The absolute path to your domain location is passed as a parameter:
wls:/offline> upgradeWSM('/domainPath')
In the following example, the OWSM configuration in a WebLogic Server 11g 11.1.1.5.0 domain is being upgraded to release 11.1.1.9.0.
oracle_common\common\bin > 'Oracle_HOME/user_projects/domains/ps5_domain')
Starting Operation upgradeWSM ...
Upgrading Oracle Web Services Manager configuration started.
Upgrading Oracle Web Services Manager configuration files started.
Upgrading Oracle Web Services Manager configuration files completed.
Migration of custom roles and policies started.
Migration of custom roles and policies completed.
Oracle Web Services Manager successfully upgraded to version 11.1.1.9.0.
Restart the servers and instances in your domain.
For more information on using the upgradeWSM() WLST command, see "Web Services Custom WLST Commands" in the WLST Command Reference for WebLogic Server. For more information about using Oracle WSM, refer to the Administering Web Services.
WS-AtomicTransaction is a Web services feature that was introduced in Oracle Fusion Middleware Release 11.1.1.3.0 release. If you are upgrading a domain that is at the 11.1.1.2.0 release, then you need to perform the following steps to ensure that WS-AtomicTransactions are enabled:
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
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" />
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>
If you are upgrading any existing 11g Oracle WebLogic Domain to Release 11.1.1.9.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-9 Description of Parameters for EXTRA_JAVA_PROPERTIES
| Property | Description |
|---|---|
|
|
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.
|
|
|
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. |
|
|
This option is used to make sure JPS debugging is turned off. This option is applicable for all JVM types. |
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 Using Oracle WebLogic Server Proxy Plug-Ins 12.1.3.
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 Using Oracle WebLogic Server Proxy Plug-Ins 12.1.3.
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.11, "Post-Patching Tasks for Your WebLogic Server Domain".Section 5.12.1, "Loading the Oracle SOA Suite Purge Scripts for Database Management"
Section 5.12.2, "Removing the tmp Folder for SOA Composer, BPM Workspace and B2B"
Section 5.12.5, "Upgrading the soa-infra Application in Warning State"
Section 5.12.6, "Running bpm-ps6-upgrade.py to Upgrade the Policy Store"
Section 5.12.7, "Running soa-upgrade.py to Upgrade the Policy Store and Deploy a Shared Library"
Section 5.12.8, "Upgrading the Oracle Data Integrator Clients if BAM-ODI Integration is Enabled"
Section 5.12.9, "Saving and Restoring XEngine Customizations for Oracle B2B"
Section 5.12.10, "Configuring Oracle JMS Adapter with IBM WebSphere MQ JMS"
Section 5.12.11, "Extending the SOA Domain with UMS Adapter Features"
Section 5.12.12, "Extending the SOA Domain with Business Process Management Features"
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 upgrade 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:
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.
Using SQLPlus, connect to the database where the Oracle SOA Suite schemas are installed using the database user that owns the SOAINFRA schema.
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
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 Administering Oracle SOA Suite and Oracle Business Process Management Suite for more information.
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:
Stop all servers (Administration Server and all Managed Servers).
Remove the tmp directory in DOMAIN_HOME/servers/AdminServer (on UNIX operating systems) or DOMAIN_HOME\servers\AdminServer (on Windows operating systems).
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.
Start all the servers.
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.
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:
Access this page through one of the following options:
| From the SOA Infrastructure Menu... | From the SOA Folder in the Navigator... |
|---|---|
|
|
The BPEL Service Engine Properties page is displayed.
Click More BPEL Configuration Properties.
In the Attributes tab, click MAXRECOVERATTEMPT.
In the Value field, enter 2.
Click Apply.
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 upgraded 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:
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
Complete any additional post-patching tasks.
Restart the WebLogic Server and Administration Console.
To upgrade 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 later.
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.
To upgrade 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 Release 11.1.1.4 or higher, 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.
If you are currently using Oracle BAM and Oracle Data Integrator (ODI) integration, you must re-run an installation script to upgrade your ODI clients after patching your software.
The Oracle BAM interface used by ODI has undergone some changes which require an upgrade 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 Developing SOA Applications with 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 upgrade your ODI clients:
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 Developing Stand-alone Clients for Oracle WebLogic Server.
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.
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
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
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
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
The procedure in this section is needed only if you use custom XEngine configurations in cases where B2B server is integrated with B2B EDI endpoints.
In such cases, all B2B domains created from the same installation share the a single XEngine configuration stored within the following directory:
On UNIX operating systems:
MW_HOME/SOA_ORACLE_HOME/soa/thirdparty/edifecs/XEngine
On Windows operating systems:
MW_HOME\SOA_ORACLE_HOME\soa\thirdparty\edifecs\XEngine
To preserve your XEngine customizations:
Prior to patching Oracle SOA Suite, back up all contents in the following directory:
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
Run the Installer to upgrade the software.
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
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
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 Understanding Technology Adapters.
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.
Stop all Admin and Managed Servers as described in "Starting and Stopping Oracle WebLogic Server Instances" in the Oracle Fusion Middleware Administrator's Guide.
Launch the Oracle WebLogic Configuration Wizard as described in "Starting the Configuration Wizard in Graphical Mode" in Creating WebLogic Domains Using the Configuration Wizard.
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
Continue through the remaining screens to complete the extension.
Restart the Admin and Managed Servers as described in "Starting and Stopping Oracle WebLogic Server Instances" in the Oracle Fusion Middleware Administrator's Guide.
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.
Apply the SOA upgrade template as described in Section 5.12.11, "Extending the SOA Domain with UMS Adapter Features". This is a mandatory prerequisite.
Stop all Admin and Managed Servers as described in "Starting and Stopping Oracle WebLogic Server Instances" in the Oracle Fusion Middleware Administrator's Guide.
Launch the Oracle WebLogic Configuration Wizard as described in "Starting the Configuration Wizard in Graphical Mode" in Creating WebLogic Domains Using the Configuration Wizard.
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_1111xx_1111xx.jar
Continue through the remaining screens to complete the extension.
Restart the Admin and Managed Servers as described in "Starting and Stopping Oracle WebLogic Server Instances" in the Oracle Fusion Middleware Administrator's Guide.
This section contains the following topics:
Section 5.13.1, "Upgrading Oracle WebCenter Content: Imaging"
Section 5.13.2, "Upgrading Oracle Application Adapters for Oracle WebCenter Content"
Section 5.13.3, "Configuring the Report Library for Records Management in Content Server"
Section 5.13.4, "Using Fusion Middleware Control to Monitor IBR"
Section 5.13.5, "Starting Oracle WebCenter Content Server with SOA or BAM"
Section 5.13.6, "Enabling System Components for WebCenter Content"
After upgrading your Oracle WebCenter Content software to Release 11.1.1.9.0 from 11.1.1.3.0 or 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.
Make sure Oracle WebLogic Server is started, then open the Oracle WebLogic Server Administration Console:
http://administration_server_host:administration_server_port/console
For production systems, go to the "Change Center" portion of the navigation panel on the left and click Lock & Edit.
Targeting the Oracle Application Core Stub file:
In the "Domain Structure" portion of the navigation panel on the left, click Deployments.
Above the "Deployments" table, click the Install button.
In the "Path" field, browse to the directory containing the Oracle Application Core Stub file.
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).
Select the oracle.applcore.model.stub.ear file and click Next.
Select Install this deployment as a library and click Next.
Select IPM_server1 as the deployment target and click Next.
Click Finish.
Targeting the Oracle SOA Libraries file for BPM:
Note:
Iforacle.soa.workflow.wc.jar is already installed due to Oracle SOA Suite being a part of the domain, you should skip the following Steps a-f. Instead, navigate to oracle.soa.workflow.wc in deployments, then go into its "Targets" tab and target IPM_server1.In the "Domain Structure" portion of the navigation panel on the left, click Deployments.
Above the "Deployments" table, click the Install button.
In the "Path" field, browse to the directory containing the Oracle SOA Libraries file.
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).
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.
Select IPM_server1 as the deployment target and click Next.
Click Finish.
For production systems, go to the "Change Center" portion of the navigation panel on the left and click Activate Changes.
Any instances of the IPM Managed Server must be restarted for this change to take effect.
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 "Upgrade (redeploy) an Enterprise application" in the 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 WLST Command Reference for WebLogic Server.
The Oracle WebCenter Content application adapters as described in Oracle Fusion Middleware Administering the Application Adapters for Oracle WebCenter contain manual steps for installing the adapters to their respective ERP system (EBS and PeopleSoft). In order to upgrade to from any previous release to Release 11.1.1.9.0, these adapters must be reinstalled.
To reinstall the EBS adapter:
Follow the instructions in "Compiling Oracle E-Business Suite Forms" in Oracle Fusion Middleware Administering the Application Adapters for Oracle WebCenter to upgrade the AXF_CUSTOM.PLL module.
If you are configured for SSL, follow the instructions in "Configuring the Integration for SSL" in Oracle Fusion Middleware Administering the Application Adapters for Oracle WebCenter.
To re-import the PeopleSoft project, follow the instructions (steps 1-6) in "Importing the Oracle PeopleSoft Project" in Oracle Fusion Middleware Administering the Application Adapters for Oracle WebCenter.
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 Fusion Middleware Installing and Configuring Oracle WebCenter Content.
When Inbound Refinery (IBR) has been upgraded to 11.1.1.9.0, the domain must be expanded to use the Oracle Enterprise Manager Plug-in for IBR template with Enterprise Manager Fusion Middleware Control to monitor IBR.
The steps below describe how to expand the domain to include the Oracle Enterprise Manager Plug-in for IBR template.
Navigate to ECM_Home/common/bin/
Execute config.sh
./config.sh
Select Extend an existing Weblogic domain
Select the domain to be extended.
In the next screen, select Oracle Enterprise Manager Plugin for IBR
Click Extend to extend the domain with the IBR template.
When WebCenter Content is integrated with Oracle SOA or Oracle Business Activity Monitoring (BAM), you must start SOA and BAM before starting Oracle WebCenter Content or Oracle Inbound Refinery (IBR).
For more information on launching WebCenter Content server from Fusion Middleware Control, see "Getting Started with Oracle WebCenter Content" in Oracle Fusion Middleware Administering Oracle WebCenter Content.
If you attempt to start the WebCenter Content server or IBR before starting Oracle SOA or BAM servers, then you may see the following error:
oracle.wsm.policymanager.PolicyManagerException: WSM-02120 : Unable to connect to the policy access service.
If you disabled components before the upgrade process, and you did not enable them before the upgrade, then you may experience issues with starting the components after the upgrade. If so, enable the components and retry the upgrade. See Section 3.3.5.1, "Enabling WebCenter Content Components Before Upgrade" for a complete list of components that may be impacted.
For more information, see "Enabling or Disabling a Component Using the Component Manager" in Oracle Fusion Middleware Administering Oracle WebCenter Content.
The instructions in this section describe the tasks that you may need to perform based on your upgrade starting point. Review the upgrade starting point tables to determine which tasks you need to perform after you upgrade your Oracle Service Bus Release domain configuration information to the latest release.
Section 5.14.1, "Upgrading an Oracle Service Bus Domain After Applying the Latest Patch Set"
Section 5.14.2, "Using Oracle Service Bus With WebLogic Server 10.3.5"
Section 5.14.3, "Using Oracle Service Bus With WebLogic Server 10.3.6"
Section 5.14.4, "Performing Additional Post-Upgrade Tasks for Oracle Service Bus IDE"
To upgrade your Oracle Service Bus domain configuration information:
Make sure you have backed up and shut down all domains to be upgraded.
Under each Oracle Service Bus domain to be upgraded, open a command window and run the user_projects/bin/setDomainEnv.sh (on UNIX operating systems) or user_projects\bin\setDomainEnv.cmd (on Windows operating systems) command.
In the command window, switch to the directory in which the upgrade scripts resides:
OSB_ORACLE_HOME/common/lib/upgrade
On the command line, run the appropriate script for your operating system:
(UNIX) java weblogic.WLST ./domainUpgrade.py (Windows) java weblogic.WLST domainUpgrade.py
Oracle Fusion Middleware 11g 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 upgrade Oracle Service Bus with Oracle Service Bus IDE to 11g Release 1 (11.1.1.9.0), then you must also upgrade 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.9.0) environment.
If you must upgrade Oracle Service Bus to 11g Release 1 (11.1.1.9.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.9.0/dropins/oracle.osb.ide.lnk (Windows) MW_HOME\oepe_11.1.1.9.0\dropins\oracle.osb.ide.lnk
If you installed Oracle WebLogic Server version 10.3.6, and you upgraded Oracle Service Bus to 11g Release 1 (11.1.1.9.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
If you are using Oracle Service Bus IDE in your environment, this section describes the required tasks after upgrading your Oracle Service Bus software to the latest version.
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:
Select Oracle WebLogic Server 11g Release 1 (10.3.3), right click and select Delete option.
Uncheck Stop server(s) before deleting and click OK.
You can deploy (publish) and test your Oracle Service Bus configuration on a running server in Eclipse. When connected to a running server in development, you can also connect to resources in the run-time environment such as JNDI resources and remote EJBs.
If you have an existing Oracle WebLogic Server you want to connect to, the server creation process simply involves you pointing at the existing server domain. If you want to create a new server, the new server wizard lets you create one using the Oracle Fusion Middleware Configuration Wizard.
To create a server in Eclipse, use the following steps:
In the Oracle Service Bus perspective, select File > New > Server. The New Server wizard appears.
Select the server type/version you want to create or connect to.
For Server's host name, enter localhost for a local server or enter the name or IP address of the remote system hosting an existing server.
The Server name is for display purposes in Eclipse.
Click Next.
For WebLogic home, click Browse and select the WebLogic_Server_HOME in the Oracle Fusion Middleware installation where the server domain is to reside (or already resides). 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 aWebLogic_Server_HOME that is outside of the server's installation MW_HOME, even if the external MW_HOME is the same product version.The Java home should be populated automatically. If you want to use a different JRE, such as the default Oracle JRockit JRE, click Browse and select the JRE under the same MW_HOME as the server.
Click Next.
Select whether the server is Local or Remote. Remote implies an existing remote server.
If Local, either select an existing server in the Domain Directory field or click the link to create a new domain. After creating a new domain, select it in the Domain Directory field.
Set other options as desired, such as automatic publishing and debug mode.
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.
Click Next.
Move any Oracle Service Bus configuration(s) you want to publish on the server to the Configured pane. You can modify this targeting after you create the server by right-clicking the server and selecting Add and Remove.
Click Finish. The new server appears in the Servers view in Eclipse, where you can start, stop, and publish to the server.
This section contains instructions for post-patching tasks for Oracle Business Intelligence. It contains the following topics:
Section 5.15.1, "Enabling the WebLogic JMS Queue for WebCenter Content Delivery Channel"
Section 5.15.2, "Upgrading Oracle Business Intelligence Code Grants"
Section 5.15.5, "Enabling Oracle Business Intelligence Composer Features"
Section 5.15.6, "Enabling JBIPS Features for the Smartview Client"
Section 5.15.9, "Configuring the Business Intelligence Mobile App Designer Apps Library"
Note:
Before you continue, make sure you have performed the tasks in Section 5.9, "Post-Patching Tasks for System Components" to upgrade your Oracle Business Intelligence system components.You must execute the BIPCreateWCCQueue.py WLST script post upgrade to add the new WebLogic JMS queue for WebCenter Content delivery channel that was added in 11.1.1.9.0.
The script is located in the following directory:
MW_HOME/Oracle_BI1/bifoundation/install/BIPCreateWCCQueue.py
To manually execute the script (if config.sh is not used):
cd <WLS_Home>/common/bin
./wlst.sh BIPCreateWCCQueue.py <WLS_Username> <WLS_Password> t3://<Adminserver_host>:<Adminserver_port>
If you are upgrading 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.
When upgrading 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 upgrade your Oracle BI Presentation Catalogs. Instructions are provided below:
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.
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.
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.
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>
Start Oracle BI Presentation Services using the following OPMN command to upgrade 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
After the catalogs are upgraded, edit the instanceconfig.xml file again and change the upgradeAndExit option back to false.
Restart Oracle BI Presentation Services using Fusion Middleware Control.
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:
Make sure all processes in the domain are stopped, including all Oracle instances, the Administration Server, all Managed Servers, and Node Manager.
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
On the Welcome screen, select Extend an existing WebLogic domain.
On the Select a WebLogic Domain Directory screen, select the location of your existing Oracle BI domain.
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
Continue with the remainder of the Configuration Wizard screens to apply this template.
After the template is applied, restart all Oracle Instances, the Administration Server, Managed Servers, and Node Manager.
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:
Make sure all processes in the domain are stopped, including all Oracle instances, the Administration Server, all Managed Servers, and Node Manager.
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.
On the Welcome screen, select Extend an existing WebLogic domain.
On the Select a WebLogic Domain Directory screen, select the location of your existing Oracle BI domain.
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
Continue with the remainder of the Configuration Wizard screens to apply this template.
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.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 for the Smartview client, you must perform the following:
Make sure all processes in the domain are stopped, including all Oracle instances, the Administration Server, all Managed Servers, and Node Manager.
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.
On the Welcome screen, select Extend an existing WebLogic domain.
On the Select a WebLogic Domain Directory screen, select the location of your existing Oracle BI domain.
On the Select Extension Source screen, select Extend my domain automatically to support the following added products and select Oracle JBIPS.
Continue with the remainder of the Configuration Wizard screens to apply this template.
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".
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.
If you are upgrading Oracle Business Intelligence from 11g Release 1 (11.1.1.x) and your BI installation includes Essbase Studio, then you must manually re-encrypt the Essbase Studio password using the Essbase Studio password encryption utility.
For more information, see "Encrypting the Catalog Password Manually In BI Installations" in the Oracle Essbase Studio User's Guide.
This section describes how to upgrade 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).
Section 5.15.8.1, "Upgrading the rtd_ils Resource Type Using WLST"
Section 5.15.8.2, "Adding Permissions to the BIAdministrator Principle Using EM"
Perform the following to add actions to the rtd_ils resource type:
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.
Launch the WebLogic Scripting Tool (WLST).
On UNIX operating systems:
./wlst.sh
On Windows operating systems:
wlst.cmd
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')
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 ]
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")
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.
Delete the resource type "rtd_ils":
deleteResourceType(appStripe="obi", resourceTypeName="rtd_ils")
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=",")
Disconnect from Oracle WebLogic Server:
disconnect()
Exit from the WebLogic Scripting Tool:
exit()
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:
Start Fusion Middleware Control using the following syntax:
http://admin_server_host:admin_server_port/em
In the left tree view, select Weblogic Domain / bifoundation_domain.
In the content pane, select Security/Application Policies from the drop down "WebLogic Domain".
Check Select Application Stripe to Search, and select "obi" from its drop down list.
Leave the Principal and Permissions blank.
Click the Search button next to the Permission field.
From the search result, click on the Principal "BIAdministrator" (or the name of your own principle if you are not using "BIAdministrator").
Click the Edit button.
In the Edit Application Grant pane, go to the Permissions section and click the Add button.
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
Click OK in the Add Permission dialog.
Click OK in the Edit Application Grant pane.
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:
Using a browser, connect to the Administration Server Console:
http://admin_server_host:admin_server_port/console
Click Lock & Edit.
Under Domain Structure, expand Services > Messaging.
Click JMS Modules.
On JMS Modules table in the right pane, select RTDJMSMODULE.
Click the Delete button, then click the Yes button to confirm.
On the left pane, click JMS Servers (under Services > Messaging).
On the JMS Servers table on the right pane, select RTDJmsServer.
Click the Delete button, then click the Yes button to confirm.
Click the Activate Changes button.
The BI Mobile Apps Library is used to make applications available to your users to run on their mobile devices. You will have to configure this library after an upgrade if you have not previously installed Business Intelligence (BI) Mobile App Designer.
For information about the Apps Library and set up steps, see "About the Apps Library" in the Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Mobile App Designer.
This section contains instructions for post-patching tasks for Oracle Data Integrator. It contains the following topics:
Section 5.16.4, "Reconfiguring Oracle Enterprise Manager Properties"
Section 5.16.6, "Adding the Version Number for the odi-sdk-ws Application in config.xml"
After you have patched the Oracle Data Integrator schemas in your database (Chapter 4, "Upgrading Your Schemas with Patch Set Assistant"), you must upgrade the following repository objects (technologies, profiles, knowledge modules), which are not upgraded 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 upgrade these repository objects, see "Reconfiguring ODI After an Upgrade" in Oracle Fusion Middleware Upgrade Guide for Oracle Data Integrator.
NOTE: If ODI is already deployed in the domain, then there is no need to re-run configuration wizard after upgrading to ODI 11.1.1.9.0.
By default, ODI ships a static Java EE Agent deployment template. To reconfigure the Java EE agent:
Run the Configuration Wizard. On the Select Domain Source screen, select the appropriate Oracle Data Integrator Agent template for your environment.
On UNIX operating systems, check user_projects/bin/setDomainEnv.sh for the following line:
-Dodi.oracle.home=${ODI_ORACLE_HOME}
On Windows operating systems, check user_projects\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.
After the upgrade, make sure the admin server and managed servers are restarted and verify that they are running
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:
Undeploy the previous version Java EE agent from your domain.
For more information, see "Managing Deployed Applications" in Deploying Applications to Oracle WebLogic Server.
Using ODI Studio 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 Developer's Guide for Oracle Data Integrator.
Run the Configuration Wizard. On the Select Domain Source screen, select Oracle Data Integrator – Agent Libraries– 11.1.1.0 to deploy the template.
Run the Configuration Wizard a second time, and on the Select Domain Source screen, deploy the generated version 11.1.1.9.0 ODI Java EE agent template to the domain.
To reconfigure the ODI standalone agent:
Make sure you have backed up the necessary files and directories as described in "Section 3.4.6, "Backing Up Additional Configuration Information".
Run the Oracle Data Integrator installer.
On the Configure Repositories Install screen, choose Skip Repository Creation.
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 Configuring and Starting the Standalone Agent" in Oracle Fusion Middleware Installation Guide for Oracle Data Integrator.
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"
If the domain created in Release 11.1.1.3.0 contains odiconsole components, reconfigure the odiconsole application as follows:
Extend the domain with Oracle Shared SDK Library 11.1.1.0 and target the deployment to odi_server1.
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.
Start the Administration Server and the odi_server1 Managed Server.
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
As of 11g Release 1 (11.1.1.6.0), the odi-sdk-ws application was upgraded 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, 11.1.1.5.0, 11.1.1.7.0 to Release 11.1.1.9.0.
To do this:
Edit the user_projects/config/config.xml (on UNIX operating systems) or user_projects\config\config.xml (on Windows operating systems) file.
Change the following line:
<name>odi-sdk-ws</name>
to add a version number, as shown below:
<name>odi-sdk-ws#11.1.1.9.0.0</name>
Start or restart the Administration Server and Managed Servers in the domain.