Applying the Latest Oracle Fusion Middleware Patch Set
9. Select whether the server is Local or Remote. Remote implies an existing remote server
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.
3.9.10.3.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.
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.
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.
Post-Patching Tasks
■ 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 Installation Guide.
■ 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.
3.9.11 Post-Patching Tasks for Oracle Business Intelligence
This section contains instructions for post-patching tasks for Oracle Business Intelligence. It contains the following topics:
■ Section 3.9.11.1, "Updating Oracle Business Intelligence Code Grants"
■ Section 3.9.11.2, "Updating Oracle Business Intelligence Catalogs"
■ Section 3.9.11.3, "Updating Oracle Real-Time Decisions"
■ Section 3.9.11.4, "Upgrading Renamed Views"
3.9.11.1 Updating Oracle Business Intelligence Code Grants
Bug 10349186.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.
Note: Before you continue, make sure you have performed the tasks in Section 3.9.5, "Post-Patching Tasks for System Components" to update your Oracle Business Intelligence system components.
Post-Patching Tasks
3.9.11.2 Updating Oracle Business Intelligence Catalogs
content provided from bug 11678827.When updating your Oracle Business Intelligence (BI) software from Release 11.1.1.3.0 to 11.1.1.6.0, you must manually update your Oracle BI Presentation Catalogs.
Instructions are provided below:
1. Shut down 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 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/coreapp lication_obipsn (on UNIX operating systems) or ORACLE_
INSTANCE\config\OracleBIPresentationServicesComponent\coreapp lication_obipsn (on Windows operating systems) directory.
4. Change the upgradeAndExit option to true in the instanceconfig.xml file.
Find the following code:
<ps:Catalog xmlns:ps="oracle.bi.presentation.services/config/v1.1">
<ps:UpgradeAndExit>false</ps:UpgradeAndExit>
</ps:Catalog>
Change it to the following:
<ps:Catalog xmlns:ps="oracle.bi.presentation.services/config/v1.1">
<ps:UpgradeAndExit>true</ps:UpgradeAndExit>
</ps:Catalog>
5. Start Oracle BI Presentation Services using the following OPMN command the 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.
3.9.11.3 Updating Oracle Real-Time Decisions
content comes from steve brar via email on 4/12/2011. also bug 11056366.
Post-Patching Tasks
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) to 11g Release 1 (11.1.1.5.0) or 11g Release 1 (11.1.1.6.0); you do not need to perform these steps if you are patching from 11g Release 1 (11.1.1.5.0) to 11g Release 1 (11.1.1.6.0).
■ Section 3.9.11.3.1, "Update the rtd_ils Resource Type Using WLST"
■ Section 3.9.11.3.2, "Add Permissions to the BIAdministrator Principle Using EM"
■ Section 3.9.11.3.3, "Removing JMS"
3.9.11.3.1 Update 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")
Post-Patching Tasks
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()
3.9.11.3.2 Add 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, of if you have replaced the BIAdministrator principle included with the product with your own principle:
1. Using a browser, connect to Fusion Middleware Control:
http://admin_server_host:admin_server_port/em
2. In the left tree view, select Weblogic Domain / bifoundation_domain.