Pre-requisites and Guidelines Creating a Data Server

Setting-up the Topology 4-7 If the technology is connected through JDBC: 1. Un-check the JNDI Connection box. 2. Go to the JDBC tab, and fill in the following fields: You can get a list of pre-defined JDBC drivers and URLs by clicking Display available drivers or Display URL sample.

6. From the File menu, click Save to validate the creation of the data server.

4.2.2.3 Creating a Data Server Advanced Settings

The following actions are optional: ■ Adding Connection Properties ■ Defining Data Sources ■ Setting Up On ConnectDisconnect Commands Adding Connection Properties These properties are passed when creating the connection, in order to provide optional configuration parameters. Each property is a key, value pair. Field Description JNDI authentication ■ None : Anonymous access to the naming or directory service ■ Simple : Authenticated access, non-encrypted ■ CRAM-MD5 : Authenticated access, encrypted MD5 ■ other value : authenticated access, encrypted according to other value JNDI UserPassword Userpassword connecting to the JNDI directory JNDI Protocol Protocol used for the connection Note that only the most common protocols are listed here. This is not an exhaustive list. ■ LDAP : Access to an LDAP directory ■ SMQP : Access to a SwiftMQ MOM directory ■ other value : access following the sub-protocol other value JNDI Driver The driver allowing the JNDI connection Example Sun LDAP directory: com.sun.jndi.ldap.LdapCtxFactory JNDI URL The URL allowing the JNDI connection For example: ldap:suse70:389o=linuxfocus.org JNDI Resource The directory element containing the connection parameters For example: cn=sampledb Field Description JDBC Driver Name of the JDBC driver used for connecting to the data server JDBC URL URL allowing you to connect to the data server. 4-8 Oracle Fusion Middleware Developers Guide for Oracle Data Integrator ■ For JDBC: These properties depend on the driver used. Please see the driver documentation for a list of available properties. It is possible in JDBC to specify here the user and password for the connection, instead of specifying there in the Definition tab. ■ For JNDI: These properties depend on the resource used. To add a connection property to a data server:

1. On the Properties tab click Add a Property.

2. Specify a Key identifying this property. This key is case-sensitive. 3. Specify a value for the property.

4. From the File menu, click Save.

Defining Data Sources On the Data Sources tab you can define JDBC data sources that will be used by Oracle Data Integrator Java EE Agents deployed on application servers to connect to this data server. Note that data sources are not applicable for standalone agents. Defining data sources is not mandatory, but allows the Java EE agent to benefit from the data sources and connection pooling features available on the application server. Connection pooling allows reusing connections across several sessions. If a data source is not declared for a given data server in a Java EE agent, this Java EE agent always connects the data server using direct JDBC connection, that is without using any of the application server data sources. Before defining the data sources in Oracle Data Integrator, please note the following: ■ Datasources for WebLogic Server should be created with the Statement Cache Size parameter set to 0 in the Connection Pool configuration. Statement caching has a minor impact on data integration performances, and may lead to unexpected results such as data truncation with some JDBC drivers. Note that this concerns only data connections to the source and target data servers, not the repository connections. ■ If using Connection Pooling with datasources, it is recommended to avoid ALTER SESSION statements in procedures and Knowledge Modules. If a connection requires ALTER SESSION statements, it is recommended to disable connection pooling in the related datasources. To define JDBC data sources for a data server:

1. On the DataSources tab of the Data Server editor click Add a DataSource

2. Select a physical Agent in the Agent field.

3. Enter the data source name in the JNDI Name field.

Note that this name must match the name of the data source in your application server.

4. Check JNDI Standard if you want to use the environment naming context ENC.

When JNDI Standard is checked, Oracle Data Integrator automatically prefixes the data source name with the string java:compenv to identify it in the application server’s JNDI directory. Note that the JNDI Standard is not supported by Oracle WebLogic Server and for global data sources.

5. From the File menu, click Save.