Authorizing access to JDBC type 4 JDBCProvider resources on Windows
Authorize the integration node 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 begin
About this task
On distributed systems, a WebSphere® MQ queue manager provides the coordinated transaction support, which means that IBM® Integration Bus must have access to WebSphere MQ when it is processing the messages in the flow. For more information about using WebSphere MQ with IBM Integration Bus, see Installing WebSphere MQ.
When the queue manager coordinates transactions, both queue manager and integration node 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 integration node service ID and the queue manager administrative ID.
If you specified an existing queue manager when you created the integration node, check that its administrative ID is the same ID as the one used for the service ID of the integration node. If the ID is not the same, change the queue manager ID to be the same as the integration node service ID.
Complete the following steps on the Windows system on which the integration node is running:
Procedure
- Click and enter dcomcnfg. The Component Services window opens.
- In the left pane, expand and click DCOM Config.
- In the right pane, right-click the WebSphere MQ service labeled IBM MQSeries Services, and click Properties.
- Click the Identity tab.
- Select This user and enter the user ID and password for the integration node service ID to associate that ID with the queue manager.
- Click OK to confirm the change.