Modifying Connection and Definition Files

This appendix covers the following topics:

WSDL Definition File
Configuring Connection Information
oc4j-ra.xml File

WSDL Definition File

Web Service Definition Language (WSDL) is generated by the JDeveloper BPEL Designer during design time. The WSDL file generated by the Adapter Wizard is the adapter service definition. In addition, it specifies various operations exposed by the service. The operations are based on user input to the Adapter Wizard. An operation either retrieves or inserts data to Oracle Applications and is represented by a JCA activation or interaction spec.

Example of a WSDL File

the picture is described in the document text

Configuring Connection Information

OracleAS Adapter for Oracle Applications is deployed as J2CA 1.5 resource adapters within the same OC4J container as BPEL Process Manager during installation.

Although OracleAS Adapter for Oracle Applications is physically deployed as J2CA 1.5 resource adapters, the logical deployment of the Adapter involves creating the connection entries for the J2CA 1.0 resource adapter by modifying the oc4j-ra.xml file, then using JDeveloper at design time. This connection information is for tying up the database connection information provided when you create a partner link or service and is used by iAS at run-time in the background.

In addition to editing the oc4j-ra.xml file manually, you can use Enterprise Manager to modify the connection configuration so that the proper information is inserted into oc4j-ra.xml automatically.

Note: The following example of connection configuration for OracleAS Adapter for Oracle Applications can be used with the Oracle Applications adapter tutorials packaged with the product. For the logical deployment changes to take effect, the OC4J container process must be restarted.

To configure the connection information:

Log into Enterprise manager at the URL for your web server host machine:
```
http://servername:port/em
```
Note: The default port number is 8888. The default login user ID and password are oc4jadmin and welcome1 respectively.
Create a connection pool and a data source:
1. Click Home, then Administration.
2. Click the Go To Task icon for Services/JDBC Resources.
3. Under Connection Pools, click the Create button.
4. Accept the defaults, and click Continue.
5. Enter the following values (leave defaults for the rest):
  Field Value
  
  Name appsSample_pool
  JDBC URL The URL for your database. For example:
  jdbc:oracle:thin:@host:1521:SID
  Username apps
  
  Password apps
6. Click Finish, then click the Test Connection icon for your new connection pool.
7. On the page that appears, click Test.
  
  Back on the main page, a successful connection message is displayed. If you see an error message, check the URL and credentials to ensure you've entered the right information.
8. Click Finish.
9. Under Data Sources, click Create.
10. Accept the defaults and click Continue.
11. Enter the following values (leave defaults for the rest):
  
  Field Value
  
  Name appsDemoDS
  
  JNDI Location jdbc/appsSampleDataSource
  
  Connection Pool appsSample_pool
12. Click Finish.
Create an Oracle Applications adapter connection:
1. At the top of the page, click the OC4J:home breadcrumb link, then the Applications link.
2. In the tree of applications, click the default link.
3. Under Modules, click the AppsAdapter link, then the Connection Factories link.
4. Under Connection Factories, click Create.
  
  Note: Use the Create button near the top of the screen, not the one in the Shared Connection Pools section.
5. Accept all the defaults and click Continue.
6. For JNDI Location, enter eis/Apps/appsSample.
7. Under Configuration Properties, for xADataSourceName, enter jdbc/appsSampleDataSource. Keep the default entries for all of the other fields.
8. Click Finish.

Field	Value
Name	appsSample_pool
JDBC URL	The URL for your database. For example: jdbc:oracle:thin:@host:1521:SID
Username	apps
Password	apps

Field	Value
Name	appsDemoDS
JNDI Location	jdbc/appsSampleDataSource
Connection Pool	appsSample_pool

oc4j-ra.xml File

You can modify the connection and login properties in the oc4j-ra.xml file directly. Following is an example of oc4j-ra.xml:

<connector-factory location="eis/Apps/apps1" connector-name="Oracle Applications Adapter">
        <config-property name="connectionString" value="jdbc:oracle:thin:@localhost:1215:orcl"/>
        <config-property name="userName" value="oraapps"/>
        <config-property name="password" value="oraapps"/>
        <config-property name="usesExternalConnectionPooling" value="false"/>
        <config-property name="dataSourceName" value=""/>
        <config-property name="usesExternalTransactionController" value="false"/>
</connector-factory>

For a Middle Tier installation, refer to the oc4j-ra.xml file at the following location:

$ORACLE_HOME\j2ee\OC4J_BPEL\application-deployments\default\AppsAdapter

For a BPEL Process Manager with standalone OC4J installation, refer to the oc4j-ra.xml file at the following location:

$ORACLE_HOME\integration\orabpel\system\appserver\oc4j\j2ee\home\application-deployments\default\AppsAdapter

Note: The run-time errors that can occur for OracleAS Adapter for Oracle Applications are similar to those for OracleAS Adapter for Databases. Refer to the "Troubleshooting the OracleAS Adapter for Databases" section in Oracle BPEL Process Manager Developer's Guide for information about handling error messages.