Set up the resources and environment that the broker needs to connect to broker and user databases with ODBC.
The broker uses Open Database Connectivity (ODBC) to connect to databases. You must define ODBC data source names (DSNs) for the broker database on each computer that hosts a broker. You must also define ODBC DSNs for any user databases that are accessed by message flows that are deployed to the broker. At any one time, multiple connections can use the same DSN definition.
On z/OS® systems, see Data sources on z/OS for information about enabling connections
to databases. You do not have to follow the tasks described in this
section.
On Linux® on POWER™ and Linux on System z®, DB2® is the only supported database
manager; the broker and message flows connect to
the databases directly using the DB2 supplied
driver and do not use a driver manager. The DB2 alias
is used as the DSN.
Set the ODBCINI environment variable to point to the .ini file that contains the DSN that is defined for the broker to connect to the broker database; the file is odbc.ini on all platforms except HP-UX on Itanium where it is odbc64.ini. If you define 64-bit DSNs in odbc64.ini on 64-bit platforms, you must also set ODBCINI64 to point to odbc64.ini.
For more information about the 32-bit and 64-bit considerations, see Broker database connections and User database connections.
When you have defined the appropriate DSNs, you must also configure the environment so that the broker can access the correct database libraries; Setting your environment to support access to databases describes this task.
To enable connections on distributed systems: