Deprecated Password Option

In previous versions of Message Queue, you could use the —p or —password option to specify a password interactively for the following commands: imqcmd, imqbrokerd, and imdbmgr. Beginning with version 4.0, these options have been deprecated. You must furnish passwords as follows.

1. Set the password property to the desired value in a file used to store only passwords.

   Use the following syntax to specify passwords in the password file.

   PasswordPropertyName=MyPassword

2. Pass the name of the password file using the —passfile option.

A password file can contain one or more of the passwords listed below.

• A keystore password used to open the SSL keystore. Use the imq.keystore.password property to specify this password.

• An LDAP repository password used to connect securely with an LDAP directory if the connection is not anonymous. Use the imq.user_repository.ldap.password property to specify this password.

• A JDBC database password used to connect to a JDBC-compliant database. Use the imq.persist.jdbc.vendorName.password property to specify this password. The vendorName component of the property name is a variable that specifies the database vendor. Choices include hadb, derby, pointbase, oracle, or mysql.

• A password to the imqcmd command (to perform broker administration tasks). Use the imq.imqcmd.password property to specify this password.

In the following example, the password to the JDBC database is set to abracadabra.

imq.persist.jdbc.mysql.password=abracadabra

You can configure the broker to use the password file you create in one of the following ways.

• Set the following properties in the broker's config.properties file.

  imq.passfile.enabled=true

  imq.passfile.dirpath=MyFileDirectory

  imq.passfile.name=MyPassfileName

• Use the —passfile option of the imqbrokerd command.

  imqbrokerd —passfile MyPassfileName