With respect to the use of WebSphere MQ in CA Gen, WebSphere MQ supports two connections types. The type of connection determines how the MQ client application will connect to a MQ queue manager.
The MQI client connection option makes use of an MQ client/server communications protocol to interact between the client application and the queue manager. This option is used when the client application does not execute on the same machine as that of the MQ queue manager.
The client application communicates to the MQ queue manager across an MQI Channel which must be defined at both the MQ client and server ends of the connection. If the MQI client connection option is utilized, a server connection channel must be added to the queue manager configuration. In addition, the queue manager must have an active listener program for each server connection channel. Defining the channel at the client end varies depending on the type of Gen client. For C language clients, MQ Environment variables are used to define the Channel definition. For Java, the MQ Environment settings are provided using the commcfg.properties file.
Note: For information about these commcfg files, see the Distributed Processing - Overview Guide.
The MQI Server connection is used when the MQ application executes on the same machine as the MQ queue manager. The client application connects to the MQ queue manager using a local queue manager handle.
Note: For more information about how client applications connect to WebSphere MQ queue managers, see IBM WebSphere MQ Clients book.
|
Copyright © 2013 CA.
All rights reserved.
|
|