In the Topology Navigator, go to the Repositories panel. Right-click the Work Repositories node and select New Work Repository. Click Test to verify that the connection is working. Click Next. Click Finish. Click Save in the toolbar. Open the New Gallery

Creating Repositories with Oracle Data Integrator Studio F-9

7. Click Test to verify that the connection is working.

8. Select Work Repository and specify the Work Repository details as follows:

■ Work repository name: The name you gave your Work Repository in the previous step WorkRep1 in the example. You can display the list of Work Repositories available in your Master Repository by clicking on the button to the right of this field.

9. Click OK to validate your entries.

F-10 Oracle Fusion Middleware Installation Guide for Oracle Data Integrator G Customizing the ODI Credential Map Name G-1 G Customizing the ODI Credential Map Name The Oracle Data Integrator Java EE Agent and Oracle Data Integrator Console use a credential map to store usernames and passwords. The default credential map name is oracle.odi.credmap. In rare situations, ODI users may need to change the default to a different credential map name for the ODI Java EE Agent and ODI Console. G.1 What is stored in Credential Store? ODI runtime uses credential store for the ODI Java EE Agent and ODI Console. ■ ODI Java EE Agent boot AppId and Password ■ ODI Console boot AppId and Password In most usage scenarios, ODI uses the credential map name oracle.odi.credmap. In certain environments, however, the credential map name is decided at a global level and all components are required to use that credential map name. For example, an Oracle Fusion Middleware application may use the oracle.apps.security credential map name instead of the standard oracle.odi.credmap. In this case, the credential map name needs to be customized for the environment. G.2 Executing the updateCredMapInEar Script You can modify the credential map name specified in the Oracle Data Integrator templates by running the script updateCredMapInEar.[sh|bat]. If you execute the script with the -EARFILE parameter, you are able to modify a specific ear file and update the default credential map. You must execute this script before creating and deploying ODI Java EE Agent ear and before deploying ODI Console ear to a WebLogic Domain. After executing this script, all generated ODI Java EE Agent ears will carry the changed credential map name. Usage: updateCredMapInEar.sh -MAPNAME=credential_map_name [-EARFILE=ear_file_to_update Where: ■ MAPNAME: User supplied credential map name. ■ EARFILE: This is optional parameter. If specified, the credential map inside the specified ear file will be modified. If not specified, the credential map name in the default templates for ODI Java EE Agent oraclediagent.ear and ODI Console odiconsole.ear will be modified.