The mqsilist command lists the databases that have been created using the mqsicreatedb command. Only databases created using the mqsicreatedb command can be deleted using the mqsideletedb command.
The Default Configuration wizard and the Prepare Samples wizard use the mqsicreatedb command to create the databases for the broker and the samples, using the default database engine. Therefore, you can list these databases using the mqsilist DatabaseInstanceMgr command.
The mqsisetdbparms command is used to manage the access security for user databases only. It has no effect on Derby databases, which have no access security protection, nor on broker databases in general, which are governed by the access security settings in the broker itself. The rest of this page applies only to the mqsicreatedb, mqsideletedb, and mqsichangedbimgr commands.
If DB2 version 8.1 Fix Pak 7 or later is installed, both DB2 and Derby databases can be created and used. If DB2 Run-time Client Version 8.2 is installed, only Derby databases are supported. If an earlier version of DB2 is installed, only DB2 databases can be created.
The mqsicreatedb command has an option to select the database engine to use (either DB2 or Derby). The default for this option depends on which database engines are installed. If DB2 Run-time Client Version 8.2 is installed, the default is Derby, otherwise the default is DB2.
The databases that are created by mqsicreatedb are managed by a component called the Database Instance manager. This component exists only on Windows. The component stores a list of all the databases created and which database engine is used for each database. Normally there is no process or Windows service required for the Database Instance manager component, and if you start the component it will not be recognized.
The first time a Derby database is created, a Windows service called IBM MQSeries Broker DatabaseInstanceMgr6 is created and started. This service is required in order to access Derby databases. This service can be started or stopped by the mqsistart and mqsistop commands, and automatically starts when Windows is started, if necessary. The service is deleted when the last Derby database is deleted. There is at most one Database Instance manager Windows service, even if you install WebSphere Message Broker Version 6.0 more than once on your Windows computer (multiple installed instances).
The database commands affect all the databases created in any installed instance on your Windows computer, regardless of the instance under which they are created. For example, the mqsilist DatabaseInstanceMgr6 command lists all the databases that have been created using the mqsicreatedb command on this Windows computer. The mqsichangedbimgr command is used to change the user name and password under which the Database Instance manager Windows service is run. This is required only if passwords change or if user names are updated after the initial installation and configuration. For more information, see Using Derby databases on Windows.
The command mqsicreatedb is used to create databases for broker use or for application use. The Prepare Samples wizard and the Default Configuration wizard, for example, use the mqsicreatedb command to create their databases on Windows. Not only is the database itself created (in either DB2 or Derby), but the ODBC data source name (DSN) is also created (with the same name).
Because the data source names and the instance manager component are system wide, you cannot create two databases with the same name, on the same Windows computer, even if they are for brokers on different installed instances of WebSphere Message Broker Version 6.0. The mqsicreatedb command warns you if this is attempted. Any database created using the mqsicreatedb command can be deleted by the mqsideletedb command, even if that database is in use by a broker. See the links to the command descriptions for more information.
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
ah35005_ |