IBM Integration Bus, Version 9.0.0.8 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

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:

If you defined the broker queue manager when you created the broker by running the mqsicreatebroker command, the two components share the same administrative ID, defined as the broker service ID, and you do not have to take further action.
If you specified an existing queue manager when you created the broker, check that its administrative ID is the same ID as the one used for the service ID of the broker. If the ID is not the same, change the queue manager ID to be the same as the broker service ID:
1. Click Start > Run and enter dcomcnfg. The Component Services window opens.
2. In the left pane, expand Component Services > Computers > My Computer and click DCOM Config.
3. In the right pane, right-click the WebSphere® MQ service labeled IBM MQSeries Services, and click Properties.
4. Click the Identity tab.
5. Select This user and enter the user ID and password for the broker service ID to associate that ID with the queue manager.
6. Click OK to confirm the change.

Next: If you have been following the instructions in Working with databases, the next task is Configuring ODBC connections for globally coordinated transactions (optional).

ah61340_.htm |

Last updated Friday, 21 July 2017