When you have created a database, you must authorize the broker to access it. When you run the mqsicreatebroker command, you must specify at least one user ID for runtime authorization (the service user ID); you can specify a second user ID specifically for the broker to use when connecting to databases (the data source user ID). If you do not specify a separate data source user ID for connecting to databases, the broker uses its 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 user ID and password with the -u and -p flags.
To authorize access to a DB2 database using the DB2 Control Center:
If you prefer, you can use the following commands instead of using the DB2 Control Center.
To authorize access to a DB2 database:
db2 connect to broker_db user SysAd_id
db2 grant connect, createtab, bindadd, create_external_routine on database to user mqsiuid
For more information, see the documentation that is supplied with 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 globally coordinated transactions to a broker, you must provide additional authorization. For more information, see Configuring databases for global coordination of transactions.
For further information, refer to the Oracle documentation.