Queue manager parameters

List of the parameter names that can be passed to the queue manager and the registry.

The following lists the parameter names that you can pass to the queue manager and the registry:
Queue manager Parameters
MQeQueueManager.Name(ascii)
This is the name of the queue manager being started.
Registry Parameters
MQeRegistry.LocalRegType(ascii)
This is the type of registry being opened. MQe currently supports:
file registry
Set this parameter to com.ibm.mqe.registry.MQeFileSession.
private registry
Set this parameter to com.ibm.mqe.registry.MQePrivateSession.
You also need a private registry for some security features.
MQeRegistry.DirName(ascii)
This is the name of the directory holding the registry files. You must pass this parameter for a file registry.
MQeRegistry.PIN(ascii)
You need this PIN for a private registry.
Note: For security reasons, MQe deletes the PIN and KeyRingPassword, if supplied, from the startup parameters as soon as the queue manager is activated.
MQeRegistry.CAIPAddrPort(ascii)
You need this address and port number of a mini-certificate server for auto-registration, so that the queue manager can obtain its credentials from the mini-certificate server.
MQeRegistry.CertReqPIN(ascii)
This is the certificate request number allocated by the mini-certificate administrator to allow the registry to obtain its credentials. You need this for auto-registration, so that the queue manager can obtain its credentials from the mini-certificate server.
MQeRegistry.Separator(ascii)
This is used to specify a non-default separator. A separator is the character used between the the components of an entry name, for example <QueueManager><Separator><Queue>. Although this parameter is specified as a string, it must contain a single character. If it contains more than one, only the first character is used. Use the same separator for each registry opened and do not change it once a registry is in use. If you do not specify this parameter, the separator defaults to "+".
MQeRegistry.RegistryAdapter(ascii)
This is the class, or an alias that resolves to a class, of the adapter that the registry uses to store its data. You must include this class if you want the registry to use an adapter other than the default MQeDiskFieldsAdapter. You can use any valid storage adapter class.
You always need the first two parameters. The last two are for auto-registration of the registry if it wishes to obtain credentials from the mini-certificate server.
MQeRegistry.RegistryAdapter (ascii)
The class, (or an alias that resolves to a class), of the adapter that the registry uses to store its data. This value should be included if you want the registry to use an adapter other than the default MQeDiskFieldsAdapter. Any valid adapter class can be used.
A queue manager can run:
  • As a client
  • As server
  • In a servlet

The following sections describe the example client, servers and servlet that are provided in the examples.queuemanager package.refer extensively to the example code to illustrate how to start queue managers. All queue managers are constructed from the same base MQe components, with some additions that give each its unique properties. MQe provides an example class, MQeQueueManagerUtils, that encapsulates many of the common functions.

All the examples require parameters at startup. These parameters are stored in standard ini files. The ini files are read and the data is converted into an MQeFields object. The loadConfigFile() method in the MQeQueueManagerUtils class performs this function.


Terms of use | WebSphere software

(c) Copyright IBM Corporation 2004, 2005. All rights reserved.