| Author |
Message
|
| julio espinoza cancino |
 Posted: Mon Nov 28, 2016 10:24 am Post subject: MQ Client for IBM System I. fix pack 8.0.0.5-WS-MQC-IBM_i |
 |
|
Newbie
Joined: 28 Nov 2016
Posts: 3
|
Hi.
Regarding the mQ client for Iseries, IBM has told me that it is available in fix pack 8.0.0.5-WS-MQC-IBM_i.
I have searched the internet and I can't find any reference to this client nor to their stability or behavior. I can not even find documentation.
The iSeries client is an alternative solution to a retail installation with many transactions per second.
Does anyone have any reference or experience using this client?
Any help will be welcome.
Sincerely |
|
| Back to top |
|
 |
| smdavies99 |
| Posted: Mon Nov 28, 2016 10:53 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
searched the Internet?
Well a search for...........
IBM MQ 8.0.0.5
gives this
http://www-01.ibm.com/support/docview.wss?uid=swg21982686
There is a link to FIX Central where you can find the download of the IBM i 8.0.0.5 client
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| julio espinoza cancino |
| Posted: Mon Nov 28, 2016 11:24 am Post subject: |
|
|
Newbie
Joined: 28 Nov 2016
Posts: 3
|
Thanks for the link, but I'm looking for some kind of information about the experience using these client in a high messaging environment, replacing the servers in Iseries.
Thanks... |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Mon Nov 28, 2016 11:39 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9442
Location: US: west coast, almost. Otherwise, enroute.
|
Google 'MQ client performance' or similar.
Slower performance given increase in network traffic with MQ client.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| julio espinoza cancino |
| Posted: Mon Nov 28, 2016 11:54 am Post subject: |
|
|
Newbie
Joined: 28 Nov 2016
Posts: 3
|
Thank for the help... are there any experience about migrate a high transaction envirnment MQ, using MQ server in Iseries to use MQ client in Iseries, migrating the server to MQ appliance or any other platform?
best reggards
Thanks |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Mon Nov 28, 2016 3:00 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2527
Location: Melbourne, Australia
|
MQ Client requires interactions over TCP/IP for every MQI call. This is not so bad if if the qmgr is local and no n/w links are involved, but the performance is not as good as MQ Server / aka Bindings mode. I suggest that you benchmark performance before moving a high volume environment to MQ Client. The app also needs to properly handle MQ Client severe failures, such as the venerable MQRC_CONNECTION_BROKEN that can occur on any MQI call at any time. You also need to consider if transactionality is required with MQ Client.
_________________
Glenn |
|
| Back to top |
|
|
| RogerLacroix |
| Posted: Mon Nov 28, 2016 4:42 pm Post subject: |
|
|
Jedi Knight
Joined: 15 May 2001
Posts: 3258
Location: London, ON Canada
|
Hello,
This sounds like a manager who wants to save some money but does not have a clue about the cost and work involved in what you ask.
(1) Applications will not require updates if ALL messages are not important, messages can be lost and applications stop working when connectivity is lost to the queue manager.
(2) If messages are critical or important then you better have a truck with lots and lots of money because what you are asking will be VERY expensive.
- All applications will need to be updated to support 2 phase UOW (Unit of Work) or messages can be lost.
- All applications will need re-connection logic added to it, so that dropped connections can be handled.
- There will be a noticeable difference in response speed especially for larger messages
- All of these MQ client applications need to connect somewhere, have you sized out how large of a server will be required to (1) handle the TCP/IP traffic and the MQ workload?
These are just a few things that I can think of off the top of my head.
Regards,
Roger Lacroix
Capitalware Inc.
_________________
Capitalware: Transforming tomorrow into today.
Connected to MQ!
Twitter |
|
| Back to top |
|
|
|
|
