4 Integrating OracleAS Adapters for CICS

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

  1. Configuring OracleAS Adapters for CICS

  2. Integrating OracleAS Adapters for CICS with WebLogic

  3. Configuring OracleAS Adapter for CICS

Configuring OracleAS Adapter for CICS

This section includes the following topics:

Creating JCA Configuration Files

Perform the following steps to create a binding file and a WSDL file for the CICS adapter or CICS Queue, 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. Do one of the following:

    • For the CICS adapter, expand the Adapters folder and right-click the CICS adapter you defined in Configuring an Oracle Connect Adapter and select Generate JCA Configuration Files.

    • For the CICS Queue adapter, expand the Events folder and right-click the CICS Queue you defined in Configuring the CICS Queue 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. The Connection Factory is mandatory for Outbound interactions and optional for Inbound interactions.

    For information on the binding file, see Configuring the Binding for Outbound Interactions or Configuring the Binding for Inbound Interactions.

  9. Click OK to create the files in the correct location.

    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, click the appropiate link in 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="http://platform.integration.oracle/blocks/adapter/fw/metadata">    <connection-factory UIConnectionName="pcbpel" csfKey="pcbpel" location="eis/legacy/calc"/>        <endpoint-interaction operation="add" portType="calcPortType">        <interaction-spec className="com.attunity.adapter.oracle.AttuInteractionSpec">            <property name="FunctionName" value="add"/>                        <property name="ExecutionTimeout" value="120"/>            </interaction-spec>    </endpoint-interaction>    <endpoint-interaction operation="display" portType="calcPortType">        <interaction-spec className="com.attunity.adapter.oracle.AttuInteractionSpec">            <property name="FunctionName" value="display"/>                        <property name="ExecutionTimeout" value="120"/>            </interaction-spec>    </endpoint-interaction>    <endpoint-interaction operation="div" portType="calcPortType">        <interaction-spec className="com.attunity.adapter.oracle.AttuInteractionSpec">            <property name="FunctionName" value="div"/>                        <property name="ExecutionTimeout" value="120"/>            </interaction-spec>    </endpoint-interaction>    <endpoint-interaction operation="mul" portType="calcPortType">        <interaction-spec className="com.attunity.adapter.oracle.AttuInteractionSpec">            <property name="FunctionName" value="mul"/>                        <property name="ExecutionTimeout" value="120"/>            </interaction-spec>    </endpoint-interaction>    <endpoint-interaction operation="sub" portType="calcPortType">        <interaction-spec className="com.attunity.adapter.oracle.AttuInteractionSpec">            <property name="FunctionName" value="sub"/>                        <property name="ExecutionTimeout" value="120"/>            </interaction-spec>    </endpoint-interaction></adapter-config>

Configuring the Binding for Inbound Interactions

You should not edit the WSDL file generated by Oracle Studio. You may edit the binding file to configure the AttuActivationSpec properties. Most of these properties can also be provided using the Connection Factory. For information on how to configure the Connection Factory, see Configuring the CICS Queue Adapter for Inbound. For information on the properties you that must be defined in the binding, see Table 4-1, "ActivationSpec Properties Defined in the Binding".

The binding file specifies the name of the adapter's connection factory as the value of the adapterInstanceJndi attribute of the <jca:address> element in the <service> section. If a connection factory exists on the application server, its properties are taken. Otherwise, the properties specified by the AttuActivationSpec are used. If a value is specified by both the connection factory and the AttuActivationSpec, the AttuActivationSpec property overrides the value in the connection factory. If you want to use the value specified in the connection factory, you must delete the property from the binding file.

For a description of these properties, see Configuring the CICS Queue Adapter for Inbound

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

<?xml version="1.0" encoding="UTF-8"?>
<adapter-config adapter="Legacy Adapter" name="eventQ1" xmlns="http://platform.integration.oracle/blocks/adapter/fw/metadata">
    <resource-adapter className="com.attunity.adapter.oracle.AttuResourceAdapter"/>  <endpoint-activation operation="eventStream" portType="eventQ1PortType">
<connection-factory UIConnectionName="pcbpel" csfKey="pcbpel" location="eis/legacy/OracleDisam_CDCQueue"/>
        <activation-spec className="com.attunity.adapter.oracle.AttuActivationSpec">
            <property name="MessagesInBatch" value="50"/>
            <property name="WaitTime" value="30"/>
            <property name="EisName" value="eventQ1"/>
            <property name="ServerName" value="localhost"/>
            <property name="PortNumber" value="2551"/>
            <property name="UserName" value=""/>
            <property name="Password" value=""/>
            <property name="Workspace" value="eventQ1"/>
            <property name="RetryInterval" value="15"/>
            <property name="ConnectTimeout" value="0"/>
            <property name="Compression" value="true"/>
            <property name="FirewallProtocol" value=""/>
            <property name="EncryptionProtocol" value=""/>
            <property name="EncryptionKeyName" value=""/>
            <property name="EncryptionKeyValue" value=""/>

The following table describes the properties you must configure in the binding file.

Table 4-1 ActivationSpec Properties Defined in the Binding

Property Description


Optional. The maximum number of events that can be sent by the adapter to the SOA process. The default value is 50.


Optional. Set to true to enable 2PC support. You should set this value to true only if the Oracle adapter is configured for two-phase commit. The default value is false.


Optional. Defines the maximum response time (in seconds) for Oracle Connect to send a response to the CICS queue adapter. The default is set to 30 seconds.


Optional. The amount of time the resource adapter waits if no events are found in the server before issuing the next request. The default is set to 15 seconds.