To configure the interactions OracleAS Adapters for Tuxedo, you must perform the following tasks in the specified order:
This chapter includes the following topics:
The following sections describe how to use Oracle Studio to:
Create JCA Configuration Files for the Tuxedo and Tuxedo Queue Adapters
Create JCA Configuration Files for the Tuxedo Gateway Adapter
Perform the following steps to create a binding file and a WSDL file for the Tuxedo or Tuxedo Queue adapters.
From the Start menu, select Programs, Oracle, and then select Studio.
In the Design perspective, Configuration view, expand the Machine folder.
Expand the machine defined in Configuring OracleAS Adapters for Tuxedo in Oracle Studio.
Expand the Bindings. The binding configurations available on this computer are listed.
Expand the NAV binding. The NAV binding configuration includes branches for data sources and adapters that are located on the computer.
Do one of the following:
For the Tuxedo adapter, expand the Adapters folder and right-click the Tuxedo adapter you defined in Setting up the Tuxedo OracleAS Adapter and select Generate JCA Configuration Files.
For the Tuxedo Queue adapter, expand the Events folder and right-click the Tuxedo Queue you defined in Setting up the Tuxedo Queue OracleAS Adapter on and select Generate JCA Configuration Files.
The JCA Configuration Files dialog box opens.
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.
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 Tuxedo Queue Inbound Interactions.
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 appropriate link the dialog box.
Use these files when working with the BPEL Process Manager or Mediator.
Perform the following steps to create a binding file and a WSDL file for the Tuxedo Gateway adapter.
From the Start menu, select Programs, Oracle, and then select Studio.
In the Design perspective, Configuration view, expand the Machine folder.
Expand the machine defined in Configuring OracleAS Adapters for Tuxedo in Oracle Studio.
Expand the Bindings. The binding configurations available on this computer are listed.
Expand the TGW binding that you created in Setting up the Tuxedo Gateway OracleAS Adapter. The TGW binding configuration includes branches for data sources and adapters that are located on the computer.
Expand the Adapters folder and right-click the Tuxedo Gateway adapter you defined in Setting up the Tuxedo Gateway OracleAS Adapter and select Generate JCA Configuration Files.
The JCA Configuration Files dialog box opens.
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.
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 optional for Inbound interactions.
For more information on the binding file, see Configuring the Binding for Tuxedo Queue Inbound Interactions.
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 link the dialog box.
Use these files when working with the BPEL Process Manager or Mediator.
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.
Note:
TheFunctionName property must have the same value as the corresponding operation.The following is an example of an outbound binding file:
<?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>
Note:
When you work with the Tuxedo Gateway adapter metadata (inbound synchronous), the server must be running.When you work with the Tuxedo Gateway adapter, only one instance can service a Tuxedo Gateway Adapter.
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 a list of these properties, see:
For information on the properties you that must be defined in the binding, see 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.
The following is an example of an inbound binding file for a queue adapter:
<?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=""/>
</activation-spec>
</endpoint-activation>
</adapter-config>
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 |
|
|
Optional. Set to |
|
|
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. |
The Oracle Adapter Framework does not support its own resource manager, therefore the inbound transactional process cannot be supported directly under the Adapter Framework. To configure the transaction gateway process, you must perform the following steps:
Configure the Oracle Gateway inbound process for a specific Tuxedo service as explained in Configuring OracleAS Adapter for Tuxedo. You must select a the Tuxedo Transactional Gateway adapter. For more information, see Setting up the Tuxedo Gateway OracleAS Adapter for more information. The automatically created WSDL contains the com.oracle.adapter.oracle.AttuGWTxnActivationSpec. The properties for this activation spec are not in use and should not be changed.
Next, deploy the created BPEL process. When you deploy a process that includes this activation spec, the Tuxedo Gateway resource adapter that works under the Adapter Framework ignores the activation of the corresponding work thread. As a result, only the BPEL application is activated in the BPEL domain.
You should configure a connection factory that provides connectivity to the transactional gateway adapter. For a list of the properties to configure, see Connection Factory Properties for Synchronous Inbound Processes.
In addition, the resource adapter connection factory contains two properties that enable connectivity from the application server environment to the BPEL domain. These properties are:
bpelDomain: The name of the BPEL domain. The default value is default.
bpelDomainPassword: Password for the BPEL domain. The default value is bpel.
You should not configure the connection factory if the corresponding properties have default values. You can use your existing connection factory or create a new one to edit these properties.