3 Integrating OracleAS Adapters for CICS with WebLogic

This chapter includes the following topics:

Overview of Integrating OracleAS Adapters for CICS with WebLogic

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 the J2EE specific containers, APIs, and services. WebLogic supports the J2CA 1.5 standard.

J2CA defines standard Java interfaces for simplifying the integration of applications with the EIS. OracleAS Adapter are deployed as a Resource Adapter (RA) 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 (like security and transaction).

Message inflow contracts enable the resource adapter to send asynchronous messages to an application server message endpoints regardless of the messaging style, semantics, or delivering infrastructure. This mechanism enables a wide variety of message providers (like Java Message Service (JMS), or Java API for XML (JAXM)) to be plugged into an application server through the resource adapter.

See Also:

Oracle Application Server Adapter Concepts Guide, Oracle Application Server Containers for J2EE User's Guide, Oracle Application Server Containers for J2EE Services Guide, and Oracle Application Server Containers for J2EE Security Guide.

Configuring the CICS Adapter for Outbound

Deploy the Oracle Connect RAR into the WebLogic server.

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

This table describes the connection factory properties that are relevant for the CICS 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 Oracle Connect server using Oracle Studio.

serverName

Required. Sets the TCP/IP address or host name where the Oracle Connect daemon is running.

workspace

Optional. Specifies the name of an Oracle Connect server workspace to use. The default workspace is Navigator.

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.

fakeXa

Optional. Set to true or false, according to the value of the transaction support property of the corresponding CICS adapter. When set to true, the XA APIs are internally converted to local transaction APIs.

This property is used for outbound interactions only.

Configuring the CICS Queue Adapter for Inbound

Deploy the Oracle Connect RAR into the WebLogic server.

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

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

Table 3-2 Connection Factory Properties for Inbound Interactions

Property Description

eisName

Required. Sets the name of the adapter to use. The adapter is defined in Oracle Connect server using Oracle Studio.

serverName

Required. Sets the TCP/IP address or host name where the Oracle Connect daemon is running.

workspace

Optional. Specifies the name of an Oracle Connect server workspace to use. The default workspace is Navigator.

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.

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.