A Sample WSDL and oc4j-ra.xml File

This appendix contains the following sections:

• Sample WSDL File

• Sample oc4j-ra.xml File

Sample WSDL File

A 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.

Figure A-1 shows a sample WSDL file.

Figure A-1 Sample WSDL File

Description of "Figure A-1 Sample WSDL File"

Sample oc4j-ra.xml File

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 the 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 editing the oc4j-ra.xml file and using JDeveloper during design time. For the logical deployment changes to take effect, the OC4J container process must be restarted

You can modify the connection and login properties in the oc4j-ra.xmlfile. A sample oc4j-ra.xml is shown as follows:

<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 might for OracleAS Adapter for Oracle Applications are similar to 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.