Add Permissions to the BIAdministrator Principle Using EM The steps in this

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_ Applying the Latest Oracle Fusion Middleware Patch Set 3-35 Home \server\bin on Windows operating systems directory to the PATH environment variable. This can be accomplished by running the setWLSEnv script located in the WebLogic_Home serverbin on UNIX operating systems or WebLogic_ Home \server\bin on Windows operating systems directory. 3. Undeploy the version 11.1.1.3.0 Java EE agent from your domain using the following command: java weblogic.Deployer -url admin_server_url -username admin_server_username -password admin_server_password -targets odi_server_name -name odi_agent_name –undeploy For example: java weblogic.Deployer -url http:examplehost.com:7001 -username exampleuser -password examplepassword -targets odi_server1 -name oraclediagent –undeploy For more information, see Managing Deployed Applications in Oracle Fusion Middleware Deploying Applications to Oracle WebLogic Server. 4. Run the Configuration Wizard. On the Select Domain Source screen, select the Oracle Data Integrator – Agent – 11.1.1.0 template. For more information, see Configure a WebLogic Domain in Oracle Fusion Middleware Installation Guide for Oracle Data Integrator. ODI also enables you to generate a Java EE agent deployment template from ODI Studio. You can customize the Java EE agent with additional data sources and libraries. To do so: 1. Undeploy the version 11.1.1.3.0 Java EE agent from your domain. For more information, see Managing Deployed Applications in Oracle Fusion Middleware Deploying Applications to Oracle WebLogic Server. 2. Using ODI Studio version 11.1.1.5.0 or the command line script to generate equivalent Java EE agent template with required data sources and additional libraries. For more information on data source declaration, deployment and template generation in ODI Studio, see Java EE Agent in the Oracle Fusion Middleware Developers Guide for Oracle Data Integrator. 3. Run the Configuration Wizard. On the Select Domain Source screen, select Oracle Data Integrator – Agent Libraries– 11.1.1.0 to deploy the template. 4. Run the Configuration Wizard a second time, and on the Select Domain Source screen, deploy the generated version 11.1.1.5.0 ODI Java EE agent template to the domain.

3.8.11.3 Reconfiguring the ODI Standalone Agent

To reconfigure the ODI standalone agent: 1. Make sure you have backed up the necessary files and directories as described in Back Up Files for Oracle Data Integrator Java EE Standalone Agent in Section 3.4.4, Back Up Additional Configuration Information. 2. Run the Oracle Data Integrator installer. On the Configure Repositories Install screen, choose Skip Repository Creation. 3. After the installation is complete: