Logical Architecture Agents Introduction to the Oracle Data Integrator Topology

4-4 Oracle Fusion Middleware Developers Guide for Oracle Data Integrator It is possible to mix in a single environment standalone and Java EE agents in a distributed environment. Physical and Logical Agents A physical agent corresponds to a single standalone agent or a Java EE agent. A physical agent should have a unique name in the Topology. Similarly to schemas, physical agents having an identical role in different environments can be grouped under the same logical agent. A logical agent is related to physical agents through contexts. When starting an execution, you indicate the logical agent and the context. Oracle Data Integrator will translate this information into a single physical agent that will receive the execution request. Agent URL An agent runs on a host and a port and is identified on this port by an application name. The agent URL also indicates the protocol to use for the agent connection. Possible values for the protocol are http or https. These four components make the agent URL. The agent is reached via this URL. For example: ■ A standalone agent started on port 8080 on the odi_production machine will be reachable at the following URL: http:odi_production:8080oraclediagent. ■ A Java EE agent started as an application called oracledi on port 8000 in a WLS server deployed on the odi_wls host will be reachable at the following URL: http:odi_wls:8000oracledi.

4.1.5 Languages

Languages defines the languages and language elements available when editing expressions at design-time. Languages provided by default in Oracle Data Integrator do not require any user change.

4.1.6 Repositories

The topology contains information about the Oracle Data Integrator repositories. Repository definition, configuration and installation is covered in the Installation and Upgrade Guide for Oracle Data Integrator.

4.2 Setting Up the Topology

The following steps are a guideline to create the topology. You can always modify the topology after an initial setting: 1. Create the contexts corresponding to your different environments. 2. Create the data servers corresponding to the servers used by Oracle Data Integrator. Note: The application name for a standalone agent is always oraclediagent and cannot be changed. Setting-up the Topology 4-5 3. For each data server, create the physical schemas corresponding to the schemas containing data to be integrated with Oracle Data Integrator. 4. Create logical schemas and associate them with physical schemas in the contexts. 5. Create the physical agents corresponding to the standalone or Java EE agents that are installed in your information systems. 6. Create logical agents and associate them with physical agents in the contexts.

4.2.1 Creating a Context

To create a context: 1. In Topology Navigator expand the Contexts accordion.

2. Click New context in the accordion header.

3. Fill in the following fields: ■ Name : Name of the context, as it appears in the Oracle Data Integrator graphical interface. ■ Code : Code of the context, allowing a context to be referenced and identified among the different repositories. ■ Password : Password requested when the user requests switches to this context in a graphical interface. It is recommended to use a password for critical contexts for example, contexts pointing to Production data ■ Check Default if you want this context to be displayed by default in the different lists in Designer Navigator or Operator Navigator.

4. From the File menu, click Save.

4.2.2 Creating a Data Server

A Data Server corresponds for example to a Database, JMS server instance, a scripting engine or a file system accessed with Oracle Data Integrator in the integration flows. Under a data server, subdivisions are created in the form of Physical Schemas.

4.2.2.1 Pre-requisites and Guidelines

It is recommended to follow the guidelines below when creating a data server. Review the Technology Specific Requirements Some technologies require the installation and the configuration of elements such as: ■ Installation of a JDBC Driver. See the Oracle Fusion Middleware Installation Guide for Oracle Data Integrator for more information. ■ Installation of a Client Connector, ■ Data source configuration. Refer to the documentation of the technology you are connecting to through the data server and to the Oracle Fusion Middleware Connectivity and Knowledge Modules Guide for Oracle Data Integrator. The connection information may also change depending on the Note: Frequently used technologies have their data server creation methods detailed in the Oracle Fusion Middleware Connectivity and Knowledge Modules Guide for Oracle Data Integrator. 4-6 Oracle Fusion Middleware Developers Guide for Oracle Data Integrator technology. Refer to the server documentation provided, and contact the server administrator to define the connection methods. Create an Oracle Data Integrator User For each database engine used by Oracle Data Integrator, it is recommended to create a user dedicated for ODI on this data server typically named ODI_TEMP. Grant this user privileges to ■ Createdrop objects and perform data manipulation in his own schema. ■ Manipulate data into objects of the other schemas of this data server according to the operations required for the integration processes. This user should be used as follows: ■ Use this user namepassword in the data server userpassword definition. ■ Use this users schema as your Work Schema for all data schemas on this server.

4.2.2.2 Creating a Data Server

To create a Data Server:

1. In Topology Navigator expand the Technologies node in the Physical Architecture

accordion. 2. Select the technology you want to create a data server for.

3. Right-click and select New Data Server

4. Fill in the following fields in the Definition tab:

■ Name : Name of the Data Server that will appear in Oracle Data Integrator. For naming data servers, it is recommended to use the following naming standard: TECHNOLOGY_NAME_SERVER_NAME. ■ ... Data Server : This is the physical name of the data server used by other data servers to identify it. Enter this name if your data servers can be inter-connected in a native way. This parameter is not mandatory for all technologies. For example, for Oracle, this name corresponds to the name of the instance, used for accessing this data server from another Oracle data server through DBLinks. ■ UserPassword : User name and password for connecting to the data server. This parameter is not mandatory for all technologies, as for example for the File technology. Depending on the technology, this could be a Login, a User, or an account. For some connections using the JNDI protocol, the user name and its associated password can be optional if they have been given in the LDAP directory. 5. Define the connection parameters for the data server: A technology can be accessed directly through JDBC or the JDBC connection to this data server can be served from a JNDI directory. If the technology is accessed through a JNDI directory: 1. Check the JNDI Connection on the Definition tab. 2. Go to the JNDI tab, and fill in the following fields: