[Fix Pack 4 or later]

Connection factory considerations for optimized local adapters

This topic reviews considerations for connection factories when using optimized local adapters.

A connection factory must be configured to enable the optimized local adapters on z/OS® for inbound and outbound support, even though it is only used directly for outbound. Multiple connection factories are supported. The connection factory can have any name.

[Fix Pack 4 or later] Each configured connection factory can have different settings associated with it. Configurable settings include connection pool sizes and custom properties.

[Fix Pack 12 or later] The following are settings that can be made on an optimized local adapter managed connection factory. Each of these settings can also be set using an optimized local adapter setter method:

[Fix Pack 12 or later] The IMS OTMA client name, which is automatically generated, is 16 characters and cannot be set with the optimized local adapters resource adapter. For more information about using the optimized local adapters over IMS OTMA, see the topic, Enabling optimized local adapters over OTMA/IMS support.

The connection pool settings for the adapter define the number of logical connections defined in the WebSphere® Application Server connection pool. This is not the same as the number of physical connections between WebSphere Application Server and an external address space. A logical connection is essentially the Java™ EE Connector Architecture (JCA) view of a physical connection, in this case. Logical connections are used by WebSphere applications calling outbound to an external address space.

The connection pool settings for the adapter define the number of logical connections defined in the WebSphere Application Server connection pool. This is not the same as the number of physical connections between WebSphere Application Server and an external address space. A logical connection is essentially the JCA view of a physical connection, in this case.

The balance between physical and logical connections depends on how many concurrent WebSphere application threads should be able to get a connection (logical), and how many requests should be able to be sent or received at any given time to and from an external address space (physical). The maximum number of physical connections can be set to make sure that an external address space does not flood the Application Server with requests, as these are used for both inbound and outbound communication with the external address space. If an external address space attempts to register with WebSphere Application Server and specifies a number of connections that are the maximum physical connections allowed for a server in this node, the register request rejects the register with a reason code that indicates the failure. The register can also fail if the maximum connections for the daemon group are exceeded. Remember that physical connections are requested by the client and are not the same as the logical connections handed out by the JCA adapter. When an outbound request is issued, the JCA logical connection is paired with a physical connection for the duration of the interaction.

After you create and save the connection factories, you can modify the resource references defined in various modules of the application and specify the Java Naming and Directory Interface (JNDI) names of the connection factories wherever appropriate.




Related tasks
Enabling the server environment to use optimized local adapters
Enabling optimized local adapters over OTMA/IMS support


Terms of Use | Feedback

Last updated: Oct 22, 2010 12:21:29 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=compass&product=was-nd-zos&topic=cdat_olacfconsid
File name: cdat_olacfconsid.html