Enter a name for the BPEL process in the Name field. For example,

7-18 Oracle Fusion Middleware Users Guide for Technology Adapters 6. Enter the following information:

a. For Create Connection In, choose Application Resources.

b. In the Connection Name field, specify a unique name for the database

connection. In this example, type DBConnection1. c. From the Connection Type box, select Oracle JDBC. d. In the UserName field, specify the user name to be authorized for access to the database. In this example, type scott. e. In the Role field, enter a role, if applicable. This must be a specific database role, such as SYSDBA, as defined in the database. This field is optional. In this example, leave the Role field blank.

f. In the Password field, specify the password to be associated with the specified

user name. In this example, type tiger.

g. Select Save Password and Deploy Password.

h. From the Driver list, select Thin.

i. In the Host Name field, enter a value to identify the computer running the

Oracle server. Use an IP address or a host name that can be resolved by TCPIP, for example, myserver. The default value is localhost.

j. In the JDBC Port field, enter a value to identify the TCPIP port. The default

is 1521.

k. In the SID field, enter a value for the unique system identifier SID of an

Oracle database instance. The default is XE.

l. Click Test Connection to determine whether the specified information

establishes a connection with the database. A Success message is displayed.

m. Click OK.

The Connection you created is displayed in the Connection field in the Service Name page. Notice that the Java Naming and Directory Interface JNDI name in the JNDI Name field is populated after you have created the database connection. The JNDI name acts as a placeholder for the connection used when your service is deployed to the BPEL server. This enables you to use different databases for development and later production. The value specified in the JNDI name must exist in the Oracle AQ Adapter weblogic-ra.xml file to ensure that the adapter runs in managed mode. A Note: You must connect to the database where Oracle Applications is running.