See information about the latest product version
Enabling JDBC connections to the databases
Configure connections to a user database through a JDBCProvider configurable service.
You must also set up JDBC connections if your message flows include graphical data maps with one or more database transforms to be run from a Mapping node, or if they include DatabaseRetrieve or DatabaseRoute nodes.
If you configure a JDBC type 4 connection from an application running on a Linux, UNIX, or Windows system, you can configure your broker and queue manager to include interactions with the databases in globally-coordinated transactions. On z/OS®, JDBC connections can be broker-coordinated only.
The information provided in this section is independent of whether your operating systems, brokers, execution groups, queue managers, and databases operate in 32-bit or 64-bit mode, except where stated.
When you write Java classes for a JavaCompute node or a user-defined node, your code must comply with the following restrictions:
- Do not include any code that performs a COMMIT or a ROLLBACK function.
- Do not close the connection to the database. The broker manages all connections, and closes a connection if it is idle for approximately one minute, or if the message flow completes.
To configure JDBC type 4 connections:
- Set up your JDBC provider definition.
- Optional: Set up security.
- Optional: Configure for global-coordination of transactions.
- Optional: If your broker is running on a Windows system, authorize access to JDBCProvider resources.
When you have completed configuration of the databases, add or modify Java code in your JavaCompute or user-defined nodes to access the database that is identified in the JDBCProvider configurable service.