Set up the WebSphere MQ client

 

When a WebSphere MQ application is run on the WebSphere MQ client, the binding information that it requires to connect to a specific queue manager is defined in a client-connection channel. This information is the name of the MQI channel, the communication type, and the address of the server to be used. You provide this by defining a client-connection channel. The name used must be same as the name used for the server-connection channel defined on the server.

A client-connection channel can be defined in one of the following three ways:

• Define the environment MQSERVER variable on the client. See Defining a client-connection channel using MQSERVER.

• Give the client access to the generated client channel definition table (that is, the amqclchl.tab file). See the chapter about running applications on WebSphere MQ clients in WebSphere MQ Clients.

• If Active Directory support is enabled, the client discovers the client-connection information dynamically from the Active Directory. See WebSphere MQ Intercommunications.

In this example, the MQSERVER environment variable is used to define the client-connection channel. This is the simplest method.

Before starting, confirm that your WebSphere MQ client and server TCP/IP sessions are initialized. To do this, type the following command:

ping server_address

server_address is the TCP/IP hostname, or the network address (in the format n.n.n.n), of the server.

If the ping command fails, check that your TCP/IP software is correctly configured and has been started.

• Defining a client-connection channel using MQSERVER
  

 

Parent topic:

Verifying a WebSphere MQ Client