Update the rtd_ils Resource Type Using WLST Perform the following to add

Applying the Latest Oracle Fusion Middleware Patch Set 3-33 4. Check Select Application Stripe to Search, and select obi from its drop down list. 5. Leave the Principal and Permissions blank. 6. Click the Search button next to the Permission field. 7. From the search result, click on the Principal BIAdministrator or the name of your own principle if you are not using BIAdministrator. 8. Click the Edit button. 9. In the Edit Application Grant pane, go to the Permissions section and click the Add button. 10. In the Add Permission dialog, under the Customize section, add the following entries: Permission Class: oracle.security.jps.ResourcePermission Resource Name: resourceType=rtd_ils,resourceName=_all_ Permission Actions: clear_choice_history,clear_statistics,clear_study,clear_ all_operational_data,delete_service,unlock_service,clear_model 11. Click OK in the Add Permission dialog. 12. Click OK button in the Edit Application Grant pane. 3.8.10.3.3 Removing JMS In earlier releases, Oracle RTD relied on JMS for its intra-member cluster communication. In the latest release, JMS is replaced with JRF web services. This is an optional step and no functionality will be affected if you choose not to perform this step. To remove JMS for Oracle RTD: 1. Using a browser, connect to the Administration Server Console: http: admin_server_host : admin_server_port console 2. Click Lock Edit. 3. Under Domain Structure, expand Services Messaging. 4. Click JMS Modules. 5. On JMS Modules table in the right pane, select RTDJMSMODULE. 6. Click the Delete button, then click the Yes button to confirm. 7. On the left pane, click JMS Servers under Services Messaging. 8. On the JMS Servers table on the right pane, select RTDJmsServer. 9. Click the Delete button, then click the Yes button to confirm. 10. Click the Activate Changes button.

3.8.11 Post-Patching Tasks for Oracle Data Integrator

This section contains instructions for post-patching tasks for Oracle Data Integrator. It contains the following topics: ■ Section 3.8.11.1, Finalizing Repository Patching ■ Section 3.8.11.2, Reconfiguring the Java EE Agent ■ Section 3.8.11.3, Reconfiguring the ODI Standalone Agent 3-34 Oracle Fusion Middleware Patching Guide ■ Section 3.8.11.4, Reconfiguring Oracle Enterprise Manager Properties

3.8.11.1 Finalizing Repository Patching

After you have patched the Oracle Data Integrator schemas in your database Chapter 4, Updating Your Schemas with Patch Set Assistant, you must update the following repository objects technologies, profiles, knowledge modules, which are not updated with Patch Set Assistant: ■ Technology Changes – Added: ComplexFile and Groovy – Changed: Oracle Natural keyword join was added Join capability was extended to BOTH Default table name prefixes were added – Changed: Teradata – Changed: PostgreSQL – Changed: Netezza – Changed: OracleBI – Changed: Hypersonic In-Memory Engine – Changed: PostgreSQL supports SQL for retrieving sequences ■ Language Changes: Groovy was added ■ Profile Changes Changes were made to LoadPlan support in the following profiles: – [NG] DESIGNER – [NG] REPOSITORY EXPLORER – [NG] VERSION ADMIN – OPERATOR – SECURITY_ADMIN ■ Knowledge Modules LKM File to Oracle SQLLDR works after removing import javaos from KM step call sqlldr. The old LKM no longer works with an upgraded Jython version. For more information about how to update these repository objects, see Oracle Data Integrator Post-Upgrade Tasks in Oracle Fusion Middleware Upgrade Guide for Oracle Data Integrator.

3.8.11.2 Reconfiguring the Java EE Agent

By default, ODI ships a static Java EE Agent deployment template. To reconfigure the Java EE agent: 1. Make sure the Administrator Server and ODI Managed Servers are up and running. 2. Add the WebLogic Server classes to the CLASSPATH environment variable and the WebLogic_Home serverbin on UNIX operating systems or WebLogic_