Configuring databases
Configure databases to hold application or business data that you can access from your message flows.
About this task
Databases that hold application or business data can be read from and written to by nodes within the message flows that you deploy to one or more integration nodes in your domain.
In some situations, and for some applications, you might need to ensure the integrity of the data that you hold in databases across multiple systems and resource managers by coordinating table updates and the writing to one database with the deletion of data in another. To achieve these goals, you must configure your databases, your integration nodes, and your message flows to be globally coordinated.
For more information about the requirement for, and set up of, databases, and the restrictions that apply, see Databases overview.
The process of making databases available has the following phases:
- Optional: Create and configure databases. If your message flows interact with databases, you must create those databases and configure ODBC and JDBC connections for them. Then the integration node can connect to the databases on behalf of the message flows.
- Optional: If your databases contain critical information, coordinate
their updates through a transaction manager.
On distributed systems, a WebSphere® MQ queue manager is the transaction manager that interacts with the resource managers (the database providers), which means that IBM® Integration Bus requires access to WebSphere MQ when processing the messages. On z/OS®, Resource Recovery Service (RRS) provides equivalent coordination. For more information about using WebSphere MQ with IBM Integration Bus, see Installing WebSphere MQ.
To complete these phases: