connector-connection-pool defines configuration used to create and manage a pool of connections to a EIS. Pool definition is named, and can be referred to by multiple connector-resource elements (See connector-resource).
Each named pool definition results in a pool instantiated at server start-up. Pool is populated when accessed for the first time. If two or more connector-resource elements point to the same connector-connection-pool element, they are using the same pool of connections, at run time.
There can be more than one pool for one connection-definition in one resource-adapter.
NOTE: some getters/setters use int/boolean. This will be corrected at a future time; these methods cannot use the AppServer template facility, whereby an Attribute value can be of the form attr-name=${ATTR_VALUE}. For an example of where/how this facility is used, see the <http-listener> element, which looks like this:
<http-listener id="http-listener-1" address="0.0.0.0" port="${HTTP_LISTENER_PORT}" acceptor-threads="1" security-enabled="false" default-virtual server="server" server-name="" xpowered-by="true" enabled="true">The 'port' attribute above is set to the value "${HTTP_LISTENER_PORT}", which is a system property. Obviously no method that uses 'boolean' could get or set a String.
|
|
|
|