When you have created a broker database, you must authorize the owning component to access it. When you invoke the mqsicreatebroker command, you must specify at least one ID for runtime authorization; you can specify a second ID specifically for database connect authorization. If you do not specify the second ID, the component uses its runtime ID (the service user ID) for database access as well.
You specify the service user ID and its password with the -i and -a flags, and the optional database connection ID and password with the -u and -p flags.
The way that you authorize access depends on the database you are using, and the platform on which you have created it.
To authorize access to a DB2 database on Windows:
If you prefer, you can use the command line commands shown below for UNIX platforms (for a broker database); the commands are the same on Windows.
To authorize access to a DB2 database on Linux and UNIX:
db2 connect to broker_db user SysAd_id
db2 grant connect, createtab, bindadd, create_external_routine on database to user mqsiuid
If you need further guidance about any of these tasks, use the online help facility of the DB2 Control Center. Your database administrator might also be able to offer advice and assistance.
To authorize access to an Oracle database:
If you expect to deploy message flows that participate in coordinated transactions to a broker, you must provide additional authorization. This task is described in Configuring databases for coordinated message flows.
For further information, refer to the Oracle documentation, or consult your database administrator.
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
ah14460_ |