3 Integrating OracleAS Adapters for Tuxedo with WebLogic

This section includes the following topics:

Overview of Integrating OracleAS Adapters for Tuxedo
Configuring the Tuxedo Adapter for Outbound
Configuring the Tuxedo Queue Inbound Adapter
Configuring the Tuxedo Gateway Synchronous Inbound Adapter

Overview of Integrating OracleAS Adapters for Tuxedo

Oracle Application Server provides a complete Java 2 Enterprise Edition (J2EE) environment that executes on the Java virtual machine (JVM) of the standard Java Development Kit (JDK). WebLogic is J2EE certified and provides all J2EE specific containers, APIs, and services. WebLogic supports the J2CA 1.5 standards.

J2CA defines standard Java interfaces for simplifying the integration of applications with the EIS. OracleAS Adapters are deployed as resource adapters within the WebLogic container.

The contract between the WebLogic client application and the resource adapter is defined by the common client interface (CCI). The contract between the WebLogic container and the resource adapter is defined by the service provider interface (SPI). The SPI API addresses the connection management, transaction management and the security management.

Connection management enables application components to connect to an EIS and leverage any connection pooling provided by the application server.

Transaction management enables an application server to use a transaction manager to manage transactions across multiple resource managers.

Lifecycle management contracts enable an application server to initialize a resource adapter instance during the deployment of the adapter or application server startup. In addition, it enables the application server to notify the resource adapter instance during server shutdown or undeployment of the adapter.

The lifecycle contract provides the mechanism for the application server to manage the lifecycle of the resource adapter instance.

Work management contracts enable the resource adapter to perform its logic by using threads dispatched by an application server, rather than creating threads on its own. The handshake is done through a Work instance submission. This makes the application server threads management more efficient, providing better control over their execution contexts (such as security and transaction).

Message inflow, which refers to inbound communications from an EIS to the application server. For more information, see Configuring the Tuxedo Queue Inbound Adapter.

Configuring the Tuxedo Adapter for Outbound

Deploy the Oracle Connect RAR into the WebLogic server.

You may create the appropriate connection factories for each Tuxedo Adapter.

This table describes the connection factory properties that are relevant for the Tuxedo Adapter. Do not change the values of any of the other properties.

Table 3-1 Connection Factory Properties for Outbound Interactions

Property	Description
`eisName`	Required. Sets the name of the adapter to use. The adapter is defined in the Oracle Connect server using Oracle Studio, as described in Setting up the Tuxedo OracleAS Adapter.
`serverName`	Required. Enter the name of the server with the TCP/IP address or host name where the Oracle Connect daemon is running. For more information, see Advanced Tuning of the Daemon for details about the daemon.
`workspace`	Optional. Specifies the name of an Oracle Connect server workspace to use. The default workspace is `Navigator`. For more information, see Workspaces for details about workspaces.
`portNumber`	Optional. Specifies the TCP/IP port where the Oracle Connect daemon is running on the server. The default port is `2551`.
`userName`	Optional. Specifies a user who can access the Oracle Connect server. The user is defined in the Oracle Connect daemon configuration. For more informatin, see Daemon Security and Workspace Security for details about users allowed to access an Oracle Connect server
`password`	Optional. Specifies a valid password for the user.
`firewallProtocol`	Optional. Specifies the firewall protocol used: either `none` or `fixedNat` (the Nat protocol using a fixed address for the daemon). The default is set to `none`.
`connectTimeout`	Optional. Specifies the connection timeout in seconds. The default is 0, indicating that there is no connection timeout.
`encryptionProtocol`	Optional. Specifies the name of encryption protocol to use. The default is set to `RC4`. If the value of the property is not defined, the RC4 protocol is used.
`encryptionKeyName`	Optional. Specifies the name of the symmetric encryption key to use.
`encryptionKeyValue`	Optional. Specifies the value of the symmetric encryption key to use.
`fakeXa`	For outbound interactions only. When set to `true`, the XA APIs are internally converted to local transaction APIs. The default is set to `false`.
`useNamespace`	Optional. Set to `true` or `false`. When set to `true`, the metadata record schema uses namespaces.
`exposeEventStreamMetadata`	Optional. When set to `true`, standard XSD schema is used for the Tuxedo/Q adapter inbound events metadata. When `false`, the native schema is used.

Configuring the Tuxedo Queue Inbound Adapter

Deploy the Oracle Connect RAR into the WebLogic server.

You may create the appropriate connection factories for each Tuxedo Queue Adapter.

This table describes the connection factory properties that are relevant for the Tuxedo Queue Adapter. Do not change the values of any of the other properties.

Table 3-2 Connection Factory Properties for Queue Inbound Processes

Property	Description
`eisName`	Required. Sets the name of the adapter to use. The adapter is defined in the Oracle Connect server using Oracle Studio, as described in Setting up the Tuxedo Queue OracleAS Adapter.
`messagesInBatch`	Specifies the maximum number of messages that can be moved to an endpoint in batch. The default is set to `50`.
`support2PC`	Enables global transaction support, where applicable. The default is set to `False`. Do not set to `true`.
`waitTime`	Defines the maximum response time (in seconds) for Oracle Connect to send a response to the Tuxedo queue adapter. The default is set to 30 seconds.
`retryInterval`	Defines the sleep time after any detected problem before restarting inbound activity. The default is set to 15 seconds.
`serverName`	Required. Sets the TCP/IP address or host name where the Oracle Connect daemon is running. For more information, see Advanced Tuning of the Daemon for details about the daemon.
`workspace`	Optional. Specifies the name of an Oracle Connect server workspace to use. The default workspace is `Navigator`. For more information, see Workspaces for details about workspaces.
`portNumber`	Optional. Specifies the TCP/IP port where the Oracle Connect daemon is running on the server. The default port is `2551`.
`userName`	Optional. Specifies a user who can access the Oracle Connect server. The user is defined in the Oracle Connect daemon configuration. For more information, see Daemon Security and Workspace Security for details about users allowed to access an Oracle Connect server
`password`	Optional. Specifies a valid password for the user.
`firewallProtocol`	Optional. Specifies the firewall protocol used: either `none` or `fixedNat` (the Nat protocol using a fixed address for the daemon). The default is set to `none`.
`connectTimeout`	Optional. Specifies the connection timeout in seconds. The default is 0, indicating that there is no connection timeout.
`encryptionProtocol`	Optional. Specifies the name of encryption protocol to use. The default is set to `null`. The RC4 protocol is supported.
`encryptionKeyName`	Optional. Specifies the name of the symmetric encryption key to use.
`encryptionKeyValue`	Optional. Specifies the value of the symmetric encryption key to use.
`connectionFactory`	This property is used only for the BPEL or ESB environment. It specifies the c`onnectionFactory` class instance that contains the adapter connection properties. If any connection property is defined on both the activationSpec and the connectionFactory, the activationSpec value is used.

Configuring the Tuxedo Gateway Synchronous Inbound Adapter

Deploy the Oracle Connect RAR into the WebLogic server.

You may create the appropriate connection factories for each CICS Queue Adapter.

This table describes the connection factory properties that are relevant for theTuxedo Gateway Adapter. Do not change the values of any of the other properties.

Table 3-3 Connection Factory Properties for Synchronous Inbound Processes

Property	Description
`eisName`	Required. Sets the name of the adapter to use. The adapter is defined in the Oracle Connect server using Oracle Studio, as described in Setting up the Tuxedo Gateway OracleAS Adapter.
serviceName	Required. Sets the name of the Tuxedo service. The service is defined as an interaction in the Oracle Connect Server using Oracle Studio.
`waitTime`	Defines the maximum response time (in seconds) for Oracle Connect to send a response to the Tuxedo gateway adapter. The default is set to 30 seconds.
`retryInterval`	Defines the sleep time after any detected problem before restarting inbound activity. The default is set to 15 seconds.
endpointTimeout	Defines the timeout for endpoint thread activation (in seconds). The default is `600` seconds.
`serverName`	Required. Sets the TCP/IP address or host name where the Oracle Connect daemon is running. For more information, see Advanced Tuning of the Daemon for details about the daemon.
`portNumber`	Optional. Specifies the TCP/IP port where the Oracle Connect daemon is running on the server. The default port is `2551`.
`userName`	Optional. Specifies a user who can access the Oracle Connect server. The user is defined in the Oracle Connect daemon configuration. Form more informaion, see Daemon Security and Workspace Security for details about users allowed to access an Oracle Connect server
`password`	Optional. Specifies a valid password for the user.
`firewallProtocol`	Optional. Specifies the firewall protocol used: either `none` or `fixedNat` (the Nat protocol using a fixed address for the daemon). The default is set to `none`.
`connectTimeout`	Optional. Specifies the connection timeout in seconds. The default is 0, indicating that there is no connection timeout.
`encryptionProtocol`	Optional. Specifies the name of encryption protocol to use. The default is set to `null`. The RC4 protocol is supported.
`encryptionKeyName`	Optional. Specifies the name of the symmetric encryption key to use.
`encryptionKeyValue`	Optional. Specifies the value of the symmetric encryption key to use.
`connectionFactory`	This property is used only for the BPEL or ESB environment. It specifies the `connectionFactory` class instance that contains the adapter connection properties. If any connection property is defined on both the activationSpec and the connectionFactory, the activationSpec value is used.

High Availability

The Oracle legacy adapters for OracleAS support High Availability using OracleAS clusters with active-active and active-passive topologies.

In an active-active topology Oracle Application Server provides an active-active redundant model for all its components with OracleAS Clusters. In an OracleAS

Cluster, two or more Oracle Application Server instances are configured to serve the same application workload. These instances can reside on the same computer or on different computers. The active instances may be front-ended by an external load balancer, which can redirect requests to any of the active instances, or by some other application-level configuration, such as address lists, to distribute the requests.

In an active-passive topology Oracle Application Server supports Active-passive model using OracleAS Cold Failover Clusters. In this case two or more application server instances are configured to serve the same application workload, but only one is active at any time.

Note: The Tuxedo Gateway adapter cannot work with OracleAS cluster and therefore does not support High Availability topology.