WebSphere Message Brokers
File: an09155_
Writer: Bill Oppenheimer

Reference topic

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

mqsisetdbparms command

Supported platforms

  • Windows
  • Linux and UNIX systems
  • z/OS. Run this command by customizing and submitting BIPSDBP.

Purpose

Use the mqsisetdbparms command to associate a specific user ID and password with each data source name (DSN) used in the following nodes:
  • Compute
  • Database
  • Filter
  • DataInsert
  • DataDelete
  • DataUpdate
  • Mapping
  • Warehouse
If the same DSN is used in multiple nodes (referring to the same database instance), the same user ID and password combination is used.

The user ID and password pair is created in the DSN folder under the broker's registry folder.

This command does not run if the broker is running. You must stop the broker before you run this command.

Note: The mqsisetdbparms command does not apply to the broker databases. Therefore you cannot use this command to override the broker data source name.

The mqsisetdbparms command allows you to create, alter, or delete the user ID and password pairs.

Syntax

Create

Alter

Delete

Parameters

BrokerName
(Required) The name of the broker for which settings are to be created, altered, or deleted.
-n DataSourceName
(Required) The data source for which the user ID and password pair are to be modified.
-u DataSourceUserId
(Required for Create; Optional for Alter) The user ID to be associated with this data source.
-p DataSourcePassword
(Required for Create and Alter) The password to be associated with this data source.

Windows platform

Linux platform

UNIX platform

For compatibility with existing systems, you can still specify <password>. However, if you do not specify a password with this parameter when you run the command you are prompted to enter a password during its invocation, and to enter the password a second time to verify that you have entered it correctly.

-d
(Required for Delete) Delete the user ID and password pair for this data source from the registry.

Authorization

On Windows systems the user ID used to invoke this command must have Administrator authority on the local system.

On UNIX systems, the user ID used to invoke this command must be a member of the mqbrkrs group.

On z/OS, the user ID used to invoke this command must be a member of a group which has READ and WRITE access to the component directory.

Note: Ensure that the registry is appropriately secured to prevent unauthorized access. mqsisetdbparms is not required for correct operation of the broker. However, if the broker administrator does not assign specific user IDs and passwords to specific data sources, the broker user ID (and password, on Windows and UNIX systems) is used. The password is not stored in clear text in the file system.

Examples

The following examples show the usage of the command without the additional Universal Record Identifier (URI):
mqsisetdbparms WBRK_BROKER -n MQBroker1 -u MQUserId -p password
mqsisetdbparms WBRK_BROKER -n MQBroker1 -d

The following examples show the use of the command when the URI for a JMS or JNDI resource name is substituted for the DataSourceName associated with the -n flag.

For a JMS resource the prefix is "jms::" and for JNDI the prefix is "jndi::".

On UNIX systems, if the parameter string includes a back slash "\" character, you must escape from this character by using a second back slash character "\\" when entering the mqsisetdbparms command.

For example, to specify a user ID of myuserid and password secret for JMS topic connection factory tcf1 in broker MyBroker1, use the following syntax:
mqsisetdbparms MyBroker1 -n jms::tcf1 -u myuserid -p secret
Similarly to specify the same security for a JNDI initial context com.sun.jndi.fscontext.RefFSContextFactory, enter the following command:
mqsisetdbparms MyBroker1 -n jndi::com.sun.jndi.fscontext.RefFSContextFactory 
     -u myuserid -p secret

The preceding examples describe how to configure security for JMS and JNDI resources for all JMS Nodes using those resources in a broker.

To increase the degree of control you have in the security of JMS nodes, you can associate a resource with an account name. The account name itself comprises the message flow name concatenated with the node label by means of the underscore character "_", that is:
            <Message Flow Name>_<Node label>
For example, where the message flow name is MyJMSFlow1 and you require a specific user and password for JMSInput node MyJMSInput1, the resulting account name is:
             MyJMSFlow1_MyJMSInput1
You can then use the account name string in the DataSource option of the mqsisetdbparms command. You do this by prefixing the account name with the resource type, and concatenating the account name with an @ character followed by the resource name itself, as follows:
            <resource type><account name>@<resource name>
Therefore, assuming a JMS resource name of tcf1, used by JMSInput node MyJMSInput1 in message flow MyJMSFlow1, the following DataSourceName is used:
            jms::MyJMSFlow1_MyJMSInput1@tcf1
Specifying a user ID of myuserid, a password of secret, a broker name of MyBroker1, and the DataSourceName name created from the account name, as described above, use the following syntax:
mqsisetdbparms MyBroker1 -n jms::MyJMSFlow1_MyJMSInput1@tcf1
                 -u myuserid -p secret
Notices | Trademarks | Downloads | Library | Support | Feedback

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

an09155_ This topic's URL is: