IBM MQ 7.5 was EOS 30th April 2018.Click EOS notice for more details
Defining the client-connection channel on the server
Having defined the server-connection channel, you now define
the corresponding client-connection channel.
Before you begin
Define the server-connection channel.
Procedure
Define a channel with the same name as the server-connection
channel, but a channel type of client-connection. You
must state the connection name (CONNAME). For TCP/IP, the connection
name is the network address or host name of the server machine. It
is also advisable to specify the queue manager name (QMNAME) to which
you want your IBM®WebSphere® MQ application,
running in the client environment, to connect. By
varying the queue manager name, you can define a set of channels to
connect to different queue managers.
DEFINE CHANNEL(CHAN2) CHLTYPE(CLNTCONN) TRPTYPE(TCP) +
CONNAME(9.20.4.26) QMNAME(QM2) DESCR('Client-connection to Server_2')
Use the following command to allow the inbound connect
access to your queue manager:
SET CHLAUTH(CHAN2) TYPE(ADDRESSMAP) ADDRESS('IP-address') MCAUSER('userid')
Where SET CHLAUTH uses the name of the channel defined in the
previous step.
Where 'IP address' is the IP address
of the client.
Where 'userid' is the ID you want
to provide to the channel for access control to the target queues.
This field is case-sensitive.
You can choose to identify your inbound connection using a
number of different attributes. The example uses IP address. Alternative
attributes include client user ID and SSL or TLS Subject Distinguished
Name. For more information, see Channel authentication records
Results
On platforms other than z/OS®,
this channel definition is stored in a file called the client channel
definition table (CCDT), which is associated with the queue manager.
The client channel definition table can contain more than one client-connection
channel definition. For more information about the client channel
definition table, and for the corresponding information about how
client-connection channel definitions are stored on z/OS, see Client channel definition table.