WebSphere Message Broker, Version 8.0.0.7 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

Database security

You can access databases from the message flows that you deploy to your brokers, and must therefore consider the steps you might want to take to secure that access.

After you have defined user IDs that you want the broker to use for database access by using the mqsisetdbparms command, you must authorize those IDs so that the broker can access your databases from deployed message flows.

If you have migrated your broker from a previous release, the broker accessed a database for its own use, and you might have defined the user ID and password used to access that database by specifying a database connection user ID and password with the -u and -p parameters on the mqsicreatebroker command. Alternatively, you might have used the broker service user ID and its password (specified with the -i and -a parameters on the same command). When you migrate the broker, these parameters are migrated and stored, and are used by the migrated broker for access to databases that do not have specific ID access defined. On WebSphere® Message Broker Version 8.0, you can use only the mqsisetdbparms command to set or change values for database access by the broker, because the parameters have been deprecated. (The service user ID and password are required on Windows, but are no longer used for database access.)

WebSphere Message Broker does not provide special commands to administer databases. Discuss your database security requirements with the database administrator for the database manager that you are using, or refer to the documentation provided by your database supplier.

For further information about possible security requirements, and examples of setting up security for DB2® and Oracle databases, see Authorizing access to user databases.

Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2016Copyright IBM Corporation 1999, 2016.

        
        Last updated:
        
        Last updated: 2016-05-23 14:47:25


Task topicTask topic | Version 8.0.0.7 | ap11690_