WebSphere Message Broker, Version 8.0.0.7
Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS
See information about the latest product version
See information about the latest product version
Authorizing access to JDBC type 4 JDBCProvider resources on Windows
Authorize the broker and queue manager to access shared resources that are associated with the JDBCProvider. This task is required only if you want the database updates to be included in globally coordinated transactions on Windows systems.
Before you start: Set up your JDBC provider definition.
When the queue manager coordinates
transactions, both queue manager and broker access shared memory to
control a connection to the databases with which the message flow
interacts. Therefore, they require the same access control of the
shared memory. One method to achieve this control is to use the same
ID for the broker service ID and the queue manager administrative
ID.
Complete the following steps on the Windows system on which the broker is running:
Next: If you have been following
the instructions in Working with databases, the next task
is Configuring ODBC connections for globally coordinated transactions (optional).