Comentários (11)

1 elisabethCesc comentou às Link permanente

Thanks for explanation WebSphere MQ Client Configuration :-)

2 RichardHamilton comentou às Link permanente

Elisabeth, Thanks for your comment! <br /> Regards, R J Hamilton

3 elisabethCesc comentou às Link permanente

Welcome Richard:-)

4 ametinithinkumar comentou às Link permanente

awesome

5 ametinithinkumar comentou às Link permanente

GOOD ONE

6 ray.g comentou às Link permanente

Is there any performance difference connecting to a remote queue manager (and reading queues) using server libs instead of client libs?

7 Gregory(Greg)Bowman comentou às Link permanente

@ray.g Yes, the client connections will typically be slower than a direct connection using bindings mode to connect to a queue manager but the performance difference can vary greatly depending on the amount of "network" that is involved in the client connection. This will hold true even if you are using client connections to connect to a queue manager on the same machine. The best way to determine the amount of performance overhead for your particular environment is to do some testing, but there are some Performance Reports SupportPacs that will give you some general guidelines of what was found in the IBM test labs. Here is a link to a list of those performance reports where you can choose the ones that are most applicable to the version and platforms you are using: http://www-01.ibm.com/support/docview.wss?uid=swg27007150

8 sjoy0703 comentou às Link permanente

What are the different ways of connecting a client program to a MQ server other than using bindings file and client connection/server connection channels. I have seen some client programs making direct connections to the Queue Manager within the code. Which is the better way??

9 Gregory(Greg)Bowman comentou às Link permanente

@sjoy0703 If a program is making a direct connection to the queue manager then it would be considered a "MQ Server program", as described in the article. If the application is running on the same machine as the queue manager, then it is generally better to connect directly to the queue manager, as a MQ Server program, and thus avoid the network and any potential problems in the network. Besides avoiding problems that could occur with network outages, the MQ Server connection is usually going to be noticeably faster too. <br /> Regards, Greg Bowman

10 sjoy0703 comentou às Link permanente

@Greg Thanks! What I had in my mind when I asked this question is I found an XMS client application which makes connection to a remote queue manager in another machine without using bindings or Client/Server Connection channels. <br /> What I understood later is it is using managed connection and invoke Queue Manager connectivity call directly from the client code during runtime and uses .NET configuration file instead of WebSphere MQ client configuration file and environment variables. Of course the managed connection has lot of limitations when compare with the regular client mode connectivity described here.

11 Gregory(Greg)Bowman comentou às Link permanente

@sjoy0703 I am not an expert on XMS by any stretch of imagination, but, like other programming interfaces, it will also allow either bindings (if your queue manager is 7.0.1 or later) or client connections to a queue manager. As you noted, there are limitations on what you can do in XMS compared to a C or JMS WMQ client but I am not familiar enough with it to elaborate much on those limitations. If you do need further help with XMS I am sure the support team at IBM would be happy to help if you open an service request with IBM Support at - https://www.ibm.com/support/servicerequest/help/srHelp.action.