Adapter Development Kit 6.5 | webMethods Adapter Development Kit Documentation | webMethods Adapter Development Kit Installation and User’s Documentation | Connections | Connection Class Interactions | Enabling Connection Nodes
 
Enabling Connection Nodes
Connection nodes are disabled by default; users must explicitly enable them using the adapter's administrative interface (as described in Configuring and Testing Connection Nodes). If a connection node is enabled when the server shuts down, it will also be enabled at server startup.
The server performs the following actions to enable a connection node:
1. Obtains a connection factory instance.
If the connection manager has already created a connection factory instance (and it is cached for use with this node), that instance is used; otherwise, the manager instantiates a new instance, as shown in step 1 in the following figure.
2. Updates the connection factory instance with the metadata parameter settings using the "set" methods described in webMethods Metadata Parameters.
3. Calls the enableCallBack method to call any adapter specific operations for the enable state change (step 4 in the following figure).
4. Calls the queryTransactionSupportLevel method to get the transaction support capabilities of connections created by this factory (step 5 in the following figure).
Transaction support depends on the capabilities of the adapter resource and the current metadata parameter settings. This method determines whether connections from this node can participate in a transaction that may involve other connections, adapters, or resources. For more information about transaction support, see Specifying Transaction Support in Connections.
5. Initializes the connection pool.
For each connection it will place in the pool (based on the minimum pool size specified when the node was created, as described in Configuring and Testing Connection Nodes), the server calls the createManagedConnectionObject on the connection factory and the initialization methods on the resulting connection object (steps 6 through 9 in the following figure). If connection pooling is disabled, a single connection will be created, initialized, and then destroyed.
6. The server calls the fillResourceAdapterMetadataInfo method on the connection factory to register the types of adapter service templates supported by the connection.
7. Calls the startupCallBack method to perform any adapter specific operations for the startup state change (step 11 in the following figure).
Enabling a connection node