Oracle Apps Adapter 6.0 | webMethods Oracle Applications Adapter Documentation | webMethods Oracle Applications Adapter Installation and User’s Documentation | Adapter Connections | Configuring Adapter Connections
 
Configuring Adapter Connections
When you configure Oracle Apps Adapter connections, you create a new connection and specify information that Integration Server uses to connect and log into an Oracle Applications server.
You configure Oracle Apps Adapter connections using Integration Server Administrator.
Note:
If you are using predefined transaction services, they use a specific preconfigured connection. You only need to edit the connection and specify the database connection information specific to your system. See Editing Adapter Connections for instructions. For more information about using connections with predefined transaction services, see the webMethods Oracle Applications Predefined Transaction Services Installation and User's Guide for the version of Oracle Applications with which you are using the adapter.
*To configure a connection
1. In the Adapters menu in the Integration Server Administrator navigation area, click Oracle Apps Adapter.
2. On the Connections screen, click Configure New Connection.
3. On the Connection Types screen, click Oracle Apps Adapter Connection to display the Configure Connection Type screen.
4. In the Oracle Apps Adapter section, provide values for the following fields.
Parameter
Description/Action
Package
The package in which to configure the connection.
You must create the package using Designer before you can specify it for this parameter. For general information about creating packages, see the webMethods Service Development Help for your release.
Note:
Configure the connection in a user-defined package rather than in the adapter's package. See Oracle Apps Adapter Package Management for other important considerations when creating packages for use with Oracle Apps Adapter.
Folder Name
The folder in which to configure 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.
5. In the Connection Properties section, provide values for the following fields:
Parameter
Description/Action
Oracle Apps Release version
The version of the Oracle Applications server to which you are connecting.
Database Server Host
The host name of the Oracle Applications database to which you are connecting.
Database Port Number
The port number of the Oracle Applications database.
Database Name
The name of the Oracle Applications database.
Database User Name
The user name that Integration Server must use to log into the Oracle Applications database. APPS is the only user name Oracle Apps Adapter supports.
Database Password
The password that Integration Server must user to log into the Oracle Applications database.
Retype Database Password
Confirms the password you specified in Database Password.
Local/XA Transaction Control
The type of transaction support that the connection provides. Select the following transaction type:
LOCAL_TRANSACTION: The connection does not automatically commit transactions. You can manually define the transactions, or the Integration Server transaction manager will manage it for you. See Built-In Transaction Management Services for instructions on managing transactions manually.
DataSource Class Name
The name of the JDBC driver's DataSource class name. Only the Oracle Thin JDBC Driver is supported:
oracle.jdbc.pool.OracleDataSource
Network protocol
A standard Oracle Applications DataSource property to indicate the name of the network protocol that the connection will use when connecting to the database.
Leave this parameter blank.
Other properties
Enables you to provide additional JDBC driver DataSource properties for the Oracle Thin JDBC Driver. The following property is supported:
driverType=thin
6. In the Connection Management Properties section, provide values for the following fields:
Parameter
Description/Action
Enable Connection Pooling
Enables the connection to use connection pooling.
See Connection Pools for more information about connection pooling.
Note:
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
If connection pooling is enabled, this field specifies the number of connections to create when the connection is enabled. The adapter will keep open the number of connections you configure here regardless of whether these connections become idle.
Maximum Pool Size
If connection pooling is enabled, this field specifies the maximum number of connections that can exist at one time in the connection pool.
Pool Increment Size
If connection pooling is enabled, this field specifies the number of connections by which the pool will be incremented if connections are needed, up to the maximum pool size.
Block Timeout (msec)
If connection pooling is enabled, this field 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.
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 might encounter problems during error conditions. If a request contains errors that delay the response, other requests will not be sent. Tune this setting in conjunction with the Maximum Pool Size to accommodate such bursts in processing.
Expire Timeout (msec)
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 Timeout value too high, you might 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 Timeout value 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.
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 is 0.
Startup Backoff Timeout (sec)
The number of seconds that the system should wait between attempts to initialize the connection pool.
7. Click Save Connection.
By default, when you configure a connection, it is not enabled. For information about enabling connections, see Enabling Adapter Connections.