To design the correspondence interfaces between WebSphere® MQ MQI customers and servers, settle on your correspondence convention, characterize the associations at the two closures of the connection, begin an audience, and characterize channels.
In WebSphere MQ, the consistent correspondence interfaces between items are called channels. The channels used to interface WebSphere MQ MQI customers to servers are called MQI channels. You set up channel definitions at each finish of your connection so your WebSphere MQ application on the WebSphere MQ MQI customer can speak with the line supervisor on the server. For a point by point depiction of how to do this, see User characterized channels.
Before you characterize your MQI channels, you should:
Settle on the type of correspondence you will utilize. See Which correspondence type to utilize.
Characterize the association at each finish of the channel:
To characterize the association, you should:
Design the association.
Record the estimations of the parameters that you requirement for the channel definitions.
Empower the server to identify approaching system demands from your WebSphere MQ MQI customer, by beginning an audience.
Which correspondence type to utilize
Distinctive stages bolster diverse transmission conventions. Your decision of transmission convention relies upon your mix of WebSphere MQ MQI customer and server stages.
There are up to four sorts of transmission convention for MQI channels relying upon your customer and server stages:
When you characterize your MQI channels, each channel definition must determine a transmission convention (transport type) quality. A server isn’t limited to one convention, so extraordinary channel definitions can indicate diverse conventions. For WebSphere MQ MQI customers, it may be valuable to have elective MQI channels utilizing distinctive transmission conventions.
Which correspondence type to utilize
Distinctive stages bolster diverse correspondence conventions. Your decision of transmission convention relies upon your mix of WebSphere MQ MQI customer and server stages.
Arranging an all-encompassing value-based customer
This gathering of points portrays how to design the all-encompassing value-based capacity for every class of exchange administrator.
Characterizing MQI channels
To make another channel, you need to make two channel definitions, one for each finish of the association, utilizing a similar channel name and perfect channel types. For this situation, the channel types are server-association and customer association.
Making server-association and customer association definitions on various stages
You can make each channel definition on the PC to which it applies. There are limitations on how you can make channel definitions on a customer PC.
Making server-association and customer association definitions on the server
You can make the two definitions on the server, at that point make the customer association definition accessible to the customer.
Channel-leave programs for MQI channels
Three kinds of channel exit are accessible to the WebSphere MQ MQI customer condition on UNIX, Linux and Windows frameworks.
Associating a customer to a line sharing gathering
You can associate a customer to a line sharing gathering by making a MQI channel between a customer and a line chief on a server that is an individual from a line sharing gathering.
Arranging a customer utilizing a design record
Arrange your customers utilizing properties in a content record. These qualities can be abrogated by condition factors or in other stage explicit ways.
Utilizing WebSphere MQ condition factors
This segment portrays the earth factors that you can use with WebSphere MQ MQI customer applications.