Skip Headers
Oracle® Application Server Adapters for IMS/DB User's Guide
11g Release 1 (11.1.1)

Part Number E16087-01
Go to Documentation Home
Go to Book List
Book List
Go to Table of Contents
Go to Index
Go to Feedback page
Contact Us

Go to previous page
Go to next page
View PDF

4 Integrating OracleAS Adapters for IMS/DB

To configure interactions for the OracleAS Adapter for IMS/DB, you must perform the following tasks in the specified order:

  1. Configuring the OracleAS Adapter for IMS/DB

  2. Integrating OracleAS Adapter for IMS/DB with WebLogic

  3. Configuring OracleAS Adapter for IMS/DB

See Also:

Oracle Application Server Adapter Concepts Guide.

Configuring OracleAS Adapter for IMS/DB

This chapter includes the following topics:

Creating JCA Configuration Files

Perform the following steps to create a binding file and a WSDL file for the adapter, using Oracle Studio:

  1. From the Start menu, select Programs, Oracle, and then select Studio.

  2. In the Design perspective, Configuration view, expand the Machine folder.

  3. Expand the machine defined in Setting Up the IBM z/OS Platform in Oracle Studio.

  4. Expand the Bindings. The binding configurations available on this computer are listed.

  5. Expand the NAV binding. The NAV binding configuration includes branches for data sources and adapters that are located on the computer.

  6. Expand the Adapters folder and right-click the database adapter you defined in Setting Up an Oracle Connect Adapter and select Generate JCA Configuration Files.

    The JCA Configuration Files dialog box opens.

  7. In the Save to field, type the path to the location where you want to save the files, or select Browse to browse to a location.

  8. In the JNDI Location field, change the default value for the WebLogic Connection Factory JNDI location, if necessary.

    You should ensure that a connection factory exists on the WebLogic server. For more information on the binding file, see Configuring the Binding for Outbound Interactions.

  9. Click OK to create the files in the correct location and close the dialog box.

    The View Genereated Content dialog box opens. It provides links to the binding file (*.jca) and the WSDL file that are created. If you want to view or edit the files or edit the files, click the appropriate link the dialog box.

    Use these files when working with the BPEL Process Manager or Mediator.

Configuring the Binding for Outbound Interactions

You should not edit the WSDL file generated by Oracle Studio. You may edit the binding file to configure the ExecutionTimeout property in the AttuInteractionSpec.


The FunctionName property must have the same value as the corresponding operation.

The following is an example of a binding file for outbound applications:

<?xml version="1.0" encoding="UTF-8"?>
<adapter-config adapter="Legacy Adapter" name="calc" xmlns="">
    <connection-factory UIConnectionName="pcbpel" csfKey="pcbpel" location="eis/legacy/calc"/>
    <endpoint-interaction operation="add" portType="calcPortType">
        <interaction-spec className="">
            <property name="FunctionName" value="add"/>
            <property name="ExecutionTimeout" value="120"/>
    <endpoint-interaction operation="display" portType="calcPortType">
        <interaction-spec className="">
            <property name="FunctionName" value="display"/>
            <property name="ExecutionTimeout" value="120"/>
    <endpoint-interaction operation="div" portType="calcPortType">
        <interaction-spec className="">
            <property name="FunctionName" value="div"/>
            <property name="ExecutionTimeout" value="120"/>
    <endpoint-interaction operation="mul" portType="calcPortType">
        <interaction-spec className="">
            <property name="FunctionName" value="mul"/>
            <property name="ExecutionTimeout" value="120"/>
    <endpoint-interaction operation="sub" portType="calcPortType">
        <interaction-spec className="">
            <property name="FunctionName" value="sub"/>
            <property name="ExecutionTimeout" value="120"/>