See information about the latest product version
Configuring user databases
Configure databases to hold application or business data that you can access from your message flows.
Databases that hold application or business data are known as user databases, and are read from and written to by nodes within the message flows that you deploy to one or more brokers in your domain.
In some situations, and for some applications, you might need to ensure the integrity of the data that you hold in user 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 brokers, and your message flows to be globally coordinated.
For more information about the requirement for, and set up of, user databases, and the restrictions that apply, see Databases overview.
The process of making databases available has the following phases:
- Optional: Create and configure user databases. If your message flows interact with databases, you must create and configure those databases ready for connection by the broker on behalf of the message flows. For user databases, you can configure ODBC and JDBC connections.
- Optional: If your user databases contain critical information,
coordinate their updates through a transaction manager.
On distributed systems, the WebSphere® MQ queue manager is the transaction manager that interacts with the resource managers (the database providers). On z/OS®, RRS provides equivalent coordination.
To complete these phases: