A MQe queue manager needs an application to create the required environment before the queue manager is loaded. This means the application that starts the queue manager needs to have access to certain information before it can load the queue manager. For instance, if you are setting the packet size for the communications adapter in Java™, the required Java property needs to be set before loading the queue manager. Two pieces of information that are required by the application are the location of the MQe Registry and the location of the queue store. The registry (not to be confused with the Windows® Registry) is where the definition of all the objects belonging to the queue manager are held, for instance queues and connection definitions. This allows a queue manager to create the correct objects when it is loaded. The queue store is the location where the queues are located, and allows a queue manager to hold messages on local queues that persist between a queue manager being stopped and started.
You can configure the MQe environment using the API, utilities shipped with MQe, or management tools such as MQe_Explorer. These methods can capture the environment parameters in an initialization file, but this is optional. See Queue manager operations for more information on queue managers. See Configuring MQe objects for more information on configuration.
You can configure a queue manager with MQ bridge capabilities. This is called a gateway and, in Java, it exchanges messages with MQ host and distributed products. The C code base uses a device queue manager only.