Adapter Development Kit 6.5 | webMethods Adapter Development Kit Documentation | webMethods Adapter Development Kit Installation and User’s Documentation | Design-Time Tasks | Configuring Connection Nodes
 
Configuring Connection Nodes
You create, manage, and enable connection namespace nodes using the adapter's management screen. When you create a connection node, it is disabled by default. You must enable the connection node after you create it.
*To configure a connection node
1. On the Integration Server Administrator > Adapters screen, select your adapter.
An adapter management screen opens, displaying any connection nodes that are currently configured for the adapter. There may be one connection type for each connection factory supported by the adapter.
2. Select Connectionsfrom the navigation area.
3. Click Configure New Connection.
4. On the Connection Types screen, select a connection type.
5. On the Configure Connection Type screen, provide values for the connection's parameters.
a. Complete the Configure Connection Type > adapter_name section as follows:
Field
Description
Package
Select a namespace node package in which to create the connection. For more information about creating packages, see Package Management.
Folder Name
Type the folder name in which to create the connection. If the folder does not already exist in the package, the server creates it.
Connection Name
Type a connection name.
b. Complete the Connection Properties section as appropriate for your adapter resource.
Enter values for the connection's metadata properties. For example, the Sample Adapter displays parameters such as Sample Server Host, Sample Server Port Number, Local Transaction Control, and Timeout.
c. Complete the Connection Management Properties section as follows:
Field
Description
Enable Connection Pooling
Enables or disables the use of connection pooling for the connection. The default value is true (enabled).
Minimum Pool Size
The number of connections to create when the connection is enabled. The default value is 1.
Maximum Pool Size
The maximum number of connections that can exist at one time in the connection pool. The default value is 10.
Pool Increment Size
The number of connections by which the pool will be incremented if connections are needed, up to the maximum pool size. The default value is 1.
Block Timeout
If connection pooling is enabled, this field specifies the number of milliseconds that Integration Server will wait to obtain a connection with the adapter resource before it times out and returns an error.
For example, you have a pool with Maximum Pool Size of 20. If you receive 30 simultaneous requests for a connection, 10 requests will be waiting for a connection from the pool. If you set the Block Timeout to 5000, the 10 requests will wait for a connection for 5 seconds before they time out and return an error. If the services using the connections require 10 seconds to complete and return connections to the pool, the pending requests will fail and return an error message stating that no connections are available.
If you set the Block Timeout value too high, you may encounter problems during error conditions. If a request contains errors that delay the response, other requests will not be sent. This setting should be tuned in conjunction with the Maximum Pool Size to accommodate such bursts in processing. The default value is 1000.
Expire Timeout
If connection pooling is enabled, this field specifies the number of milliseconds that an inactive connection can remain in the pool before it is closed and removed from the pool.
The connection pool will remove inactive connections until the number of connections in the pool is equal to the Minimum Pool Size. The inactivity timer for a connection is reset when the connection is used by the adapter.
If you set the Expire Timeoutvalue too high, you may have a number of unused inactive connections in the pool. This consumes local memory and a connection on your backend resource. This could have an adverse effect if your resource has a limited number of connections.
If you set the Expire Timeoutvalue too low, performance could degrade because of the increased activity of creating and closing connections. This setting should be tuned in conjunction with the Minimum Pool Size to avoid excessive opening/closing of connections during normal processing.
The default value is 1000. Enter -1 to specify no timeout.
Startup Retry Count
The number of times that the system should attempt to initialize the connection pool at startup if the initial attempt fails. The default value is 0 (a single attempt).
Startup Backoff Timeout
The number of seconds that the system should wait between attempts to initialize the connection pool. This field is irrelevant if the value of Startup Retry Count is 0. The default value is 10.
6. Click Test Connection.
The connection is tested based on the settings provided.
7. Click Save Connection.
The connection name is now listed on the adapter's Connections screen and in the Service Browser of Designer.
8. On the adapter's Connections screen, enable the connection node by clicking No in the Enabled column. The Enabled column now shows Yes.
The server initializes a connection pool based on the provided settings. Enabling and disabling a connection node produces entries similar to these in the server log:
2003-08-18 08:21:36 EDT [ART.0118.5505V1] Adapter Runtime (Connection):
Starting connection connections:sampleConnection.
2003-08-18 08:21:36 EDT [ART.0118.5517V1] Adapter Runtime (Connection):
Creating connection manager properties:>>>BasicData:poolable=true,
minimumPoolSize=1,maximumPoolSize=10,poolIncrementSize=1,
blockingTimeout=20000,expireTimeout=20000,selectionSize=1<<<.
2003-08-18 08:21:36 EDT [ADA.0502.0101D] Initializing Sample Connection
2003-08-18 08:21:36 EDT [SCC.0126.0001E] SCC connectionManager Pool Started
2003-08-18 08:24:10 EDT [ART.0118.5510V1] Adapter Runtime (Connection):
Stopping connection connections:sampleConnection.
Note:
If a connection node is enabled when the server shuts down, it will be enabled at server startup.