Check JNDI Standard if you want to use the environment naming context ENC. From the File menu, click Save.

4-10 Oracle Fusion Middleware Developers Guide for Oracle Data Integrator dropped the connection to this data server. It contains the code of the On Disconnect command. ■ When an operation is made in ODI Studio or ODI Console that requires a connection to the data server such as View Data or Test Connection, the commands On ConnectDisconnect are also executed if the Client Transaction is selected for this command. To set up On ConnectDisconnect commands:

1. On the On ConnectDisconnect tab of the Data Server editor, click Launch the

Expression Editor in the On Connect section or in the On Disconnect section. 2. In the Expression Editor, enter the SQL command.

3. Click OK. The SQL command is displayed in the Command field.

4. Optionally, select Commit, if you want to commit the connection after executing

the command. Note that if AutoCommit or Client Transaction is selected in the Execute On list, this value will be ignored.

5. Optionally, select Ignore Errors, if you want to ignore the exceptions encountered

during the command execution. Note that if Ignore Errors is not selected, the calling operation will end in error status. A command with Ignore Error selected that fails during a session will appear as a task in a Warning state. 6. From the Log Level list, select the logging level from 1 to 5 of the connect or disconnect command. At execution time, commands can be kept in the session log based on their log level. Default is 3. 7. From the Execute On list, select the transactions on which you want to execute the command. You can select Select All or Unselect All to select or unselect all transactions. 8. From the File menu, click Save. You can now test the connection, see Section 4.2.2.4, Testing a Data Server Connection for more information. Note: You can specify whether or not to show On Connect and Disconnect steps in Operator Navigator. If the user parameter Hide On Connect and Disconnect Steps is set to Yes, On Connect and Disconnect steps are not shown. Note: The Expression Editor displays only the subsitution methods and keywords that are available for the technology of the data server. Note that global variables are only displayed if the connection to the work repository is available. Note: Transactions from 0 to 9 and the Autocommit transaction correspond to connection created by sessions by procedures or knowledge modules. The Client Transaction correspondsto the client components ODI Console and Studio. Setting-up the Topology 4-11

4.2.2.4 Testing a Data Server Connection

It is recommended to test the data server connection before proceeding in the topology definition. To test a connection to a data server:

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

Architecture accordion and then expand the technology containing your data server.

2. Double-click the data server you want to test. The Data Server Editor opens.

3. Click Test Connection.

The Test Connection dialog is displayed.

4. Select the agent that will carry out the test. Local No Agent indicates that the

local station will attempt to connect.

5. Click Detail to obtain the characteristics and capacities of the database and JDBC

driver.

6. Click Test to launch the test.

A window showing connection successful is displayed if the test has worked; if not, an error window appears. Use the detail button in this error window to obtain more information about the cause of the connection failure.

4.2.3 Creating a Physical Schema

An Oracle Data Integrator Physical Schema corresponds to a pair of Schemas: ■ A Data Schema, into which Oracle Data Integrator will look for the source and target data structures for the interfaces. ■ A Work Schema, into which Oracle Data Integrator can create and manipulate temporary work data structures associated to the sources and targets contained in the Data Schema. Frequently used technologies have their physical schema creation methods detailed in the Oracle Fusion Middleware Connectivity and Knowledge Modules Guide for Oracle Data Integrator. Before creating a Physical Schema, note the following: ■ Not all technologies support multiple schemas. In some technologies, you do not specify the work and data schemas since one data server has only one schema. ■ Some technologies do not support the creation of temporary structures. The work schema is useless for these technologies. ■ The user specified in the data server to which the Physical Schema is attached must have appropriate privileges on the schemas attached to this data server. To create a Physical Schema:

1. Select the data server, Right-click and select New Physical Schema. The Physical

Schema Editor appears. 2. If the technology supports multiple schemas: a. Select or type the Data Schema for this Data Integrator physical schema in ... Schema . A list of the schemas appears if the technologies supports schema listing. 4-12 Oracle Fusion Middleware Developers Guide for Oracle Data Integrator b. Select or type the Work Schema for this Data Integrator physical schema in ... Work Schema . A list of the schemas appears if the technologies supports schema listing.

3. Check the Default box if you want this schema to be the default one for this data

server The first physical schema is always the default one.

4. Go to the Context tab.

5. Click Add.

6. Select a Context and an existing Logical Schema for this new Physical Schema. If no Logical Schema for this technology exists yet, you can create it from this Editor. To create a Logical Schema: 1. Select an existing Context in the left column. 2. Type the name of a Logical Schema in the right column. This Logical Schema is automatically created and associated to this physical schema in this context when saving this Editor.

7. From the File menu, click Save.

4.2.4 Creating a Logical Schema

To create a logical schema:

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

accordion. 2. Select the technology you want to attach your logical schema to.

3. Right-click and select New Logical Schema.

4. Fill in the schema name.

5. For each Context in the left column, select an existing Physical Schema in the right column. This Physical Schema is automatically associated to the logical schema in this context. Repeat this operation for all necessary contexts.

6. From the File menu, click Save.

4.2.5 Creating a Physical Agent

To create a Physical Agent: 1. In Topology Navigator right-click the Agents node in the Physical Architecture accordion.

2. Select New Agent.

3. Fill in the following fields: ■ Name : Name of the agent used in the Java graphical interface. ■ Host : Network name or IP address of the machine the agent will been launched on. ■ Port : Listening port used by the agent. By default, this port is the 20910. ■ Web Application Context : Name of the web application corresponding to the Java EE agent deployed on an application server. For standalone agents, this field should be set to oraclediagent.