WebSphere Message Brokers
File: an35001_
Writer: Laura Cowen

Reference topic

This build: July 31, 2007 21:34:33

mqsicreatedb command

Supported platforms

  • Windows

Purpose

The mqsicreatedb command creates a database and makes it accessible to the broker. The command: creates the database, creates an ODBC data source name, and if necessary, depending on the database type, creates and starts a Windows Service. The command creates at most a single instance of the Windows Service for each installation of a major product version. This command supports only the installed DB2 and Derby database engines.

Syntax

Parameters

DatabaseName
(Required) The name of the database you want to create. This must be the first parameter, and is case sensitive. Restrictions might be placed on the permissible length of the database name by the database engine. For restrictions on the character set that can be used, see Characters allowed in commands.
-i ServiceUserID
(Optional, Derby only) The user ID under which the DatabaseInstanceMgr service runs.

This can be specified in any valid username syntax:

  • domain\username
  • \\server\username
  • .\username
  • username

If you use the unqualified form for this user ID (username), the operating system searches for the user ID throughout its domain, starting with the local system. This search might take some time to complete.

The ServiceUserID specified must be a member of the local group mqbrkrs. The ID can be a direct or indirect member of the group. The ServiceUserID must also be authorized to access the home directory (where WebSphere Message Broker is installed).

This parameter is ignored if the database engine specified or defaulted for the command is DB2. A ServiceUserID is required for Derby, but only for the first invocation of this command. Subsequent invocations are associated with the existing Windows DatabaseInstanceMgr service that runs under the ServiceUserID specified on the earlier command

The security requirements for the ServiceUserID are detailed in Security requirements for Windows platforms.

-a ServicePassword
(Optional, Derby only) The password for the ServiceUserID. Specify this only if you specify ServiceUserID.
-w WorkPath
(Optional) The location in which WebSphere Message Broker stores internal data, such as installation logs, component details, and trace output. Do not edit this data unless you are instructed to do so by your IBM Service representative. The shared-classes directory is also located in the work path directory and is used for deployed Java code.
-p PortNumber
(Optional) The TCP/IP port number that this component will use on the local machine. If not specified, the default value 1527 is used.
-e DbType
(Optional) The database engine to be used to create and run the database. Currently supported values are DB2 and Derby. If you do not specify this option, and only one database engine is available, that engine is used. If both are available, the default engine is DB2.
-u DbUserID
(Optional, DB2 only) An additional user name that requires access to the database that is created by this command.

Authorization

The user ID used to invoke this command must have Administrator authority on the local system and be part of the mqbrkrs group.

Examples

The following example sets up a database with the name brokerdb on port 1600:
mqsicreatedb brokerdb -p 1600
The following example sets up a Derby database with the name derbydb, using port number 1527:
mqsicreatedb derbydb -i wbrkuid -a wbrkpw -e Derby -p 1527 
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2007Copyright IBM Corporation 1999, 2007. All Rights Reserved.
This build: July 31, 2007 21:34:33

an35001_ This topic's URL is: