Adapter for Enterprise JavaBeans 6.5 SP3 | webMethods Adapter for Enterprise JavaBeans Documentation | webMethods Adapter for Enterprise JavaBeans Installation and User’s Documentation | Adapter Connections | Configuring Adapter Connections
 
Configuring Adapter Connections
When you configure Adapter for Enterprise Javabeans connections, you specify information that the adapter uses to connect to a supported application server's JNDI server.
You configure Adapter for Enterprise Javabeans connections using Integration Server Administrator.
*To configure an adapter connection
1. In Integration Server Administrator select Adapters > Adapter for EJB.
2. On the Connections screen, click Configure New Connection.
3. On the Connection Types screen, select one of the following adapter connection types:
Connection Type
Description
EJB Non-transactional Connection
Creates a connection that will not be transacted.
EJB Local Connection
Creates a connection that will be employed in non-distributed, local transactions.
EJB XA Connection
Creates a connection that will be employed in distributed, two-phase commit transactions.
4. For more information about the transaction types, see Transaction Management of Adapter for Enterprise Javabeans Connections.
5. In the Adapter for EJB section, provide values for the following parameters:
Parameter
Description/Action
Package
The package in which to create the connection.
You must create the package using Designer before you can specify it using this parameter. For general information about creating packages, see the webMethods Service Development Help for your release.
Note:
Create the connection in a user-defined package rather than in the adapter's package. See Adapter Package Management for other important considerations when creating packages for Adapter for Enterprise Javabeans.
Folder Name
The folder in which to create the connection.
Connection Name
The name you want to give the connection. Connection names cannot have spaces or use special characters reserved by Integration Server or Designer. For more information about the use of special characters in package, folder, and element names, see the webMethods Service Development Help for your release.
6. In the Connection Properties section, provide values for the following parameters:
Parameter
Description/Action
EJB Server Type
Select the name of the application server vendor/version implementation class for the connection.
Note:
WebLogic Server 10.3 supports connections for XA transactions.
XAResource Source
(Used only with connections for XA transactions.) Typically a vendor-specific string that specifies the application server instance you are running against. This parameter is used by the implementation class to obtain the XAResource object from the application server.
Note:
WebLogic 10.3 support XA transactions. The server instance is one of the names shown under the Servers link on the WebLogic administration screen.
Properties File Name
Enter the full path to a text file on a file system accessible to Integration Server that contains the JNDI-specific Java properties. For information about the properties that need to be specified in this file, see JNDI Properties File.
JNDI Username
Optional. If a username and password is required to access the server's JNDI, enter the user name.
Specifying a JNDI username in this parameter overrides the value specified in the standard java.naming.security.principal property if this property is also defined in the JNDI properties file. For more information about security credentials, see JNDI Properties File.
JNDI Password
Optional. If a username and password is required to access the server's JNDI, enter the password.
Specifying a JNDI password in this parameter overrides the value specified in the standard java.naming.security.credentials property if this property is also defined in the JNDI properties file. For more information about security credentials, see JNDI Properties File.
Retype JNDI Password
Required if you entered a JNDI password. Verifies the password entered.
EJB Caching Level
Defines the level of EJB caching the connection uses when configuring adapter services. For more information and EJB caching levels, see EJB Information Caching.
*None. No caching occurs. When configuring the adapter service, the connection will retrieve EJB details directly from the JNDI. This is the default.
*Weak. Information in the cache is retained as long as there are outstanding weak references to the cache.
*Soft.Information in the cache is retained until the JVM would be forced to throw an OutOfMemoryError in response to a memory allocation request. At this point, it frees the memory in the cache.
*Hard. Data is retrieved from the JNDI once and cached until no more connections remain enabled for the connection factory. Subsequent requests for EJB detail are retrieved from the cache.
7. In the Connection Management Properties section, provide values for the following parameters:
Parameter
Description/Action
Enable Connection Pooling
Enables the adapter to use connection pooling. Default: true.
See Connection Pools for more information about connection pooling in the adapter.
If you plan to enable connection pooling in a clustered environment, consider the connection pool size. For details, see Considerations When Configuring Connections with Connection Pooling Enabled.
Minimum Pool Size
The minimum number of connection objects that remain in the connection pool at all times. When the adapter creates the pool, it creates this number of connections. Default: 1.
Maximum Pool Size
The maximum number of connection objects that can exist in the connection pool. When the connection pool has reached its maximum number of connections, the adapter will reuse any inactive connections in the pool or, if all connections are active, it will wait for a connection to become available. Default: 10.
Pool Increment Size
If connection pooling is enabled, this parameter specifies the number of connections by which the pool will be incremented if connections are needed, up to the maximum pool size. Default: 1.
Block Timeout
If connection pooling is enabled, this parameter specifies the number of milliseconds that Integration Server will wait to obtain a connection with the database before it times out and returns an error. Default: 1000.
Expire Timeout
If connection pooling is enabled, this parameter specifies the number of milliseconds that an inactive connection can remain in the pool before it is closed and removed from the pool. For example, to specify 10 seconds, specify 10000. Enter 0 to specify no timeout. Default: 1000.
Note:
The adapter will never violate the Minimum Pool Size parameter. These connections remain in the pool regardless of how long they are inactive.
Startup Retry Count
If connection pooling is enabled, this parameter specifies the number of times that the system should attempt to initialize the connection pool at startup if the initial attempt fails, before issuing an AdapterConnectionException. Default: 0.
Startup Backoff Timeout
If connection pooling is enabled, this parameter specifies the number of seconds to wait between each attempt to initialize the connection pool. Default: 10.
8. Click Save Connection.
The connection you created appears on the adapter's Connections screen and in Designer's Package Navigator.
Be sure to enable the connection before you create adapter services that use it. See Enabling Adapter Connections for instructions.