JDBC Support
Note: This facility is only available for online and web services channels only.
By default, the product uses the Universal Connection Pooling (UCP) to manage database connections. It is also possible to use Oracle WebLogic connection pooling through Data Sources for the online transactions (UCP will continued to be used for batch transactions). To use Data Sources the data sources must be created within Oracle WebLogic and then configuration files altered to utilize the Data Source using the following process:
• Create the Data Source in the Oracle WebLogic console using the Services, Data Sources menu item. Repeat for the connection pool for online and connection pool for web services. Specify the following:
Attribute
Comment
Name
Allocate a name for monitoring and management purposes.
JNDI Name
Allocate a name to be used by the connection. This is used as <datasourcename> later. It is recommended that the name be prefixed with jdbc/ to conform to naming standards.
Row Prefetch Enabled
This should be enabled.
Row Prefix Size
Specify a value between 2 - 100.
Default: 48
Stream Chunk Size
This is not used by the product.
Database Type
Specify Oracle.
Database Driver
Specify the database driver to use. Do not use the XA versions of the driver for the product. By default, use the Thin driver for service connections.
Supports Global Transactions
Deselect this option. It does not apply.
One Phase Commit
Ensure this option is selected.
Database Name
Specify the Oracle SID of the database to connect to. This should correspond to DBNAME - Database Name in the ENVIRON.INI.
Host Name
Specify the host allocated to Oracle. This should correspond to DBSERVER - Database Server in the ENVIRON.INI.
Port
Specify the Oracle Listener Port number of the database to connect to. This should correspond to DBPORT - Database Listener Port in the ENVIRON.INI.
Database User Name
Specify the product database user. This should correspond to DBUSER - Online Database User in the ENVIRON.INI.
 
If creating a separate connection pool for Web Services then it is recommended to use XAI_DBUSER - Database User Used for IWS in the ENVIRON.INI to separate traffic in the database.
Password
Specify the password for the user. This should correspond to DBPASS - Online Database User Password in the ENVIRON.INI.
 
If creating a separate connection pool for Web Services then it is recommended to use XAI_DBPASS - Password for Database User for IWS in the ENVIRON.INI to separate traffic in the database.
Initial Capacity
This is the initial size of the connection pool.
Maximum Capacity
This is the maximum size of the connection pool.
Capacity Increment
This is the number of connections that are added to the connection pool when necessary.
Statement Cache Type
This denotes the type of cache to use. Use the LRU setting.
Statement Cache Size
This is the cache size.
• Specify the following values in the ENVIRON.INI using the configureEnv utility. See configureEnv – Set up Environment Settings.
Setting
Recommendation
IWS JDBC DataSource Name
Fully qualified JNDI Name for Web Services Data Source.
Web JDBC DataSource Name
Fully qualified JNDI Name for Web Data Source.
• Execute the initialSetup utility to reflect the change.
• If using native mode, redeploy the product EAR files. See Manual Re-Deployment Process for details.