When you have created a broker database, you must authorize the broker and its execution groups 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 optionally specify a second user ID that the broker uses 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 parameters, and the optional database connection user ID and password with the -u and -p parameters.
If you want to use a different user ID and password for a
particular database, you can set up or change the authorization by
using the mqsisetdbparms command.
If you want to change the service user ID or password, or
the data source password, after you have created the broker, use the mqsichangebroker command; you
cannot change the data source user ID.
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.
The way that you authorize
access depends on the database manager you are using, and the platform
on which you have created the database. The instructions might also
vary from release to release of a single database. Consult your database
administrator, or see the documentation for the appropriate database
when you perform this task.
The following sections provide examples of the steps to complete to provide the required authorization for specific databases:
To authorize access to a DB2® database, you can use either the DB2 Control Center or the DB2 command line:
To authorize access to an Oracle database: