| Author |
Message
|
| wilsonjohn24 |
 Posted: Thu Aug 07, 2008 11:50 pm Post subject: Soap Input Node in 6.1 ( Soap/MQ support!!!) |
 |
|
Voyager
Joined: 02 Feb 2007
Posts: 93
Location: Scotland
|
Hi,
I have a requirement for SOAP over MQ rather than http. What is the best strategy:
1. Can I do a MQ Port type( or generic JMS Definition) in the WSDL and import this against Soap Input Node - so this will process and parser soap message of MQ using the SOAP parser.
2. Do I reparse the message aftering excepting it of an MQ Input Node as SOAP? ( I cant seem to set the soap parser on the MQ Input Node)
3. As before in 6.0* create a Message set of the WSDL and bind this against MQ Input node?
4. Any other suggestions?
Basically I want to use SOAP/MQ with all the support and utilities which SOAP/Http gets like Specific input nodes + parsers. I cant seem to be able to select the SOAP parser in any other Nodes other than the SOAP ones - which seem geared to http.
Thanks in advance
John |
|
| Back to top |
|
 |
| sridhsri |
| Posted: Fri Aug 08, 2008 5:04 am Post subject: |
|
|
Master
Joined: 19 Jun 2008
Posts: 297
|
| IBM is working on a WSDL definition for SOAP over MQ. I am not aware when that might be released. In the meanwhile, I would recommend using SOAP over JMS where the JMS provider is MQ (that way, you still conform to a standard). To read the messages you could use JMSInput node or MQInput node - both should work. |
|
| Back to top |
|
|
| vaibhav_vy |
| Posted: Sun Aug 10, 2008 9:43 pm Post subject: |
|
|
Apprentice
Joined: 04 Aug 2008
Posts: 28
|
| AFAIK I can use SOAP over JMS using WebServices WBI adapter to put message in MQ queue which will be picked by either MQInput or JMSInput node. But I think you can not use any input node to receive webservices call directly in message flow when you want SOAP over JMS. You can use HttpInput node to receive webservices call using XML over HTTP or you can use SOAPInput node to receive SOAP over HTTP. |
|
| Back to top |
|
|
| mgk |
| Posted: Mon Aug 11, 2008 3:43 am Post subject: |
|
|
Padawan
Joined: 31 Jul 2003
Posts: 1642
|
|
| Back to top |
|
|
| wilsonjohn24 |
| Posted: Thu Aug 14, 2008 10:26 am Post subject: |
|
|
Voyager
Joined: 02 Feb 2007
Posts: 93
Location: Scotland
|
Sorry- for delay in responding, thanks to all for input.
I have read the red paper in the link provided and can see how this could be of use to Broker when calling to Web Service with a port type of MQ/JMS.
But in a scenario where you want Message Broker to Facade a leagcy platform as a SOAP/MQ end point. Very simple if a company has standard of:
- SOAP complicant XML.
- Reliable Message backbone for all communications.
You cant use the SOAP parser - you need to use MQInput + XMLNSC?
Even the scenario in the Red Paper talks about MQ Applications - but Broker can be viewed as an MQ Application yet it cant act as a true consumer of SOAP/MQ or at the very least a compliant one.
Hopefully, I have not seen the woods for the trees  (not the first or last time that will happen) - but this seem a big issue in developing SOA architecture on a Message Bus, forcing the use of a incorrect parser! |
|
| Back to top |
|
|
| wilsonjohn24 |
| Posted: Thu Aug 14, 2008 10:34 am Post subject: My issues....Websphere HTTP Broker???????? |
|
|
Voyager
Joined: 02 Feb 2007
Posts: 93
Location: Scotland
|
My main issue is the speed of development:
HTTP:
SOAP Parser + Soap Mode is really quick just load the WSDL and away you go.
MQ:
Create the Message Set + XMLNS Parser + all the hassel of round tripping as the WSDL changes etc.
In a sentence....
It should be easier to deal with SOAP/MQ Messages than HTTP/SOAP in Websphere Message Broker!!!!!!!! Websphere HTTP Broker????????? |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Aug 14, 2008 1:12 pm Post subject: Re: My issues....Websphere HTTP Broker???????? |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| wilsonjohn24 wrote: |
My main issue is the speed of development:
HTTP:
SOAP Parser + Soap Mode is really quick just load the WSDL and away you go.
MQ:
Create the Message Set + XMLNS Parser + all the hassel of round tripping as the WSDL changes etc.
In a sentence....
It should be easier to deal with SOAP/MQ Messages than HTTP/SOAP in Websphere Message Broker!!!!!!!! Websphere HTTP Broker????????? |
You don't HAVE to use a message set when you use the XMLNS(C) parsers.
The message set is for when you want to create your legacy message and transform SOAP over JMS into a fixed length legacy type message. You will then need the CWF or TDS parsers and your message set definition, and you will need to map the messages.
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| bprasana |
| Posted: Tue May 11, 2010 9:44 pm Post subject: Any Resolution? |
|
|
Disciple
Joined: 18 Apr 2005
Posts: 179
|
Were you able to resolve this issue?
I know its been more than 1.5 years since this question.
But Is there any best approach for this problem now?
Thanks
bprasana |
|
| Back to top |
|
|
|
|
