Setting up a JDBC provider for type 4 connections

Use a JDBC Providers policy to configure a JDBC provider service.

Before you begin

See the following information: Creating an integration node.
Create the database by following the database documentation.

About this task

When you include a DatabaseRetrieve, DatabaseRoute, JavaCompute, Mapping, or Java™ user-defined node in a message flow, and interact with a database in that node, the integration server must establish a connection with the database to fulfill the operations that are performed by the node. You must define a JDBC Providers policy to provide the integration server with the information that it needs to complete the connection.

Important: When naming your JDBC Providers policy, consider the following requirements:

If you want to use your JDBC Providers policy with a JavaCompute node, or with a Java user-defined node, the name of your policy must match the datasourceName parameter in the getJDBCType4Connection(), provided that the policy is in the default policy project. If the policy is not in the default policy project, you must specify the policy and policy project name in the format {policyProjectName}:PolicyName.
If you want to use your JDBC Providers policy with a Mapping node, the name of your policy must match the database name that is used by the database transforms in your Graphical Data Map. For each database transform, the database name is determined by the database definition (.dbm file) in the Data Design project that was used to create the map. The JDBC Providers policy must be deployed in the default policy project; for more information, see Configuring a default policy project.
If you want to use your JDBC Providers policy with a DatabaseRetrieve node, or with a DatabaseRoute node, the name of your policy must match the value of the Data source name property of the node. The JDBC Providers policy must be deployed in the default policy project; for more information, see Configuring a default policy project.

A JDBC Providers policy supports connections to one database only; you must create a policy for each database that your nodes or Java applications connect to.

To set up a JDBC provider for type 4 connections, complete the following steps.

Procedure

Identify the type of database for which you require a JDBC Providers policy.

Supported JDBC drivers and databases are shown in IBM App Connect Enterprise system requirements; support for globally coordinated (XA) transactions is restricted on some platforms and for some databases.
Use the Policy editor in the IBM App Connect Enterprise Toolkit to create a JDBC Providers policy and choose the template for your chosen database type (see Creating policies with the IBM App Connect Enterprise Toolkit).
The template provides some default values, but you must change some of them to create a viable definition.
For example, the Database name property is mandatory, but is initially empty (see JDBC Providers policy (JDBCProviders)).
The following values and order of preference are used by the integration server to substitute the user ID and password in the pattern:
1. First, on all platforms: The user ID and password that you have set for the specific database, by using the mqsisetdbparms and specifying the database in the -n parameter.
2. Second, on all platforms: The user ID and password that you have set for all other databases, by using the mqsisetdbparms and specifying jdbc::JDBC in the -n parameter.
3. Third, the values are platform-specific:
  1. On Windows: The integration node service ID and password that you specified on the mqsicreatebroker command.
  2. On Linux® and UNIX: The user ID mqsiUser and password ******** (these values are fixed).
When you have created your JDBC Providers policy, you must deploy it to any integration server where you will deploy the message flows that will use this policy. You can deploy the policy project directly to an integration server.

What to do next

If required, set up security for the JDBC connection, set up the environment to include the JDBC Providers policy in globally coordinated transactions, or both.