my guess is that they would own a lot more proprietary in-house written code after completing that conversion, and managers are usually more "buy" than "build" these days...
----- Original Message -----
From: "T.Rob" <t.rob-CkT6zf+urXSzW/GOMZKyElesiRL1/***@public.gmane.org>
To: MQSERIES-0lvw86wZMd9k/bWDasg6f+***@public.gmane.org
Sent: Friday, November 1, 2013 10:57:50 PM
Subject: Re: Web Services better than MQ?
I think he did admit exactly that. He advised considering...
* Transactionality
* Governance
* Statefulness
* A requirement for transformation
...then said that converting between such unlike things is not simply
messaging-to-messaging. His parting shot wasn't to prefer WMQ over CICS but
specifically said to keep WMQ *and* CICS for the uses where they are
appropriate.
Sure, there's insufficient information to answer Mike's question but I can't
fault Pete for responding provisionally that "it's bigger than a breadbox."
That someone would even phrase this as "Are web services under CICS a better
messaging platform than MQ and MQ Broker?" suggests someone involved sees an
equivalency that doesn't exist, or if it exists does so on the most
superficial level. Pete asks essentially the same question you did...
"better for what, exactly?"
Did I miss something slanted toward Avada's product in all of that?
-- T.Rob
-----Original Message-----
Of Bob Juch
Sent: Friday, November 01, 2013 18:34 PM
Subject: Re: Web Services better than MQ?
Peter,
You have a vested interest in seeing MQ thrive but I hope you can admit
it's not the best solution in all situations. I've seen the "when the
only tool you have is a hammer all problems look like nails"
mindset result in some terrible solutions.
There's not enough information at this point to answer Mike's question.
Bob Juch
Juch Services LLC
Post by Peter DLet me just answer with Omg.
I was with one of the very very first web services organizations back
in 1998 (yeah it's that old). So I love certain aspects of web services.
Post by Peter DFirst, web services are not transactional unless you code like a freak
to make them that way - rollbacks, apps that don't respond, assured
delivery, etc. It's not just CICS it's the endpoints of the services
too!
Post by Peter DSecond it's hard to determine the validity of the service at all unless
you have a great repository where you can validate the biz and tech usage
as well as the destinations and consumers before and after you implement
them.
Post by Peter DHow do you deal with state vs non state (asynchronous) transactions?
Then they're saying broker? Omg-2.
What are they going to use to transform all of the transactions? How is
that transformation engine going to integrate and communicate with the
underlying delivery layer?
Post by Peter DI think someone in your management structure read some Info-Week or CIO
Today article and has no idea of the ramifications and years that a
migration like that would take; never mind at the end if it leaving some
very essential delivery and acknowledgment issues unresolved.
Post by Peter DI cannot disclose but a very large P&C insurance company started down
the webm services path to replace MQ - 3 years later guess what they're
now growing in their environment? Yup - MQ gets another shot at the
title. This is just like saying get rid of CICS -- ok and the
alternative is? ...
Post by Peter DTo IBM - if you fix your license structure and stop being greedy this
kind if stuff wouldn't happen anyway. We all know it comes down to corp $
and cents (not sense).
Post by Peter D/Pete
Post by Ward, Mike SAre web services under CICS a better messaging platform than MQ and MQ
Broker? We are MQ V7.1, Broker V8 and CICS 4.2. All of our touch points
use MQ and broker for messaging. There seems to be an ripple going
through our department to get rid of MQ and Broker and use CICS Web
Services. Are CICS Web services better suited for serving messaging data
to our touch points? Any opinions welcome.
Post by Peter DPost by Ward, Mike S==========================
This email, and any files transmitted with it, is confidential and
intended solely for the use of the individual or entity to which it is
addressed. If you have received this email in error, please notify the
system manager. This message contains confidential information and is
intended only for the individual named. If you are not the named
addressee, you should not disseminate, distribute or copy this e-mail.
Please notify the sender immediately by e-mail if you have received this
message by mistake and delete this e-mail from your system. If you are
not the intended recipient, you are notified that disclosing, copying,
distributing or taking any action in reliance on the contents of this
information is strictly prohibited.
Post by Peter DPost by Ward, Mike Sthe message body (not the subject), write: SIGNOFF MQSERIES
Instructions for managing your mailing list subscription are provided
in the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html
the message body (not the subject), write: SIGNOFF MQSERIES
Instructions for managing your mailing list subscription are provided
in the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html
message body (not the subject), write: SIGNOFF MQSERIES Instructions for
managing your mailing list subscription are provided in the Listserv
General Users Guide available at http://www.lsoft.com
Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html
To unsubscribe, write to LISTSERV-0lvw86wZMd9k/bWDasg6f+***@public.gmane.org and,
in the message body (not the subject), write: SIGNOFF MQSERIES
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html
To unsubscribe, write to LISTSERV-0lvw86wZMd9k/bWDasg6f+***@public.gmane.org and,
in the message body (not the subject), write: SIGNOFF MQSERIES
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html