| Author |
Message
|
| iceage |
 Posted: Tue Sep 05, 2006 9:35 am Post subject: WBIMB V6 implementing Webservice "POC" ideas... |
 |
|
Acolyte
Joined: 12 Apr 2006
Posts: 68
|
I am implementing a webservice in WBIMB V6 for a "POC" project , my requirement is to receive a HTTP request , do some operations and reply back.
My message fllow currently is
Http I/P ---> Series of Compute Nodes ---> Http Reply
I want to generate reply messages that are SOAP wrapped , what are my choices ..
1) Create a SOAP message using ESQL
SET OutputRoot.XMLNSC.{SOAP}:Envelope = ...
2) Make use of MRM message sets ?
3) Any other inbuilt feature that can generate SOAP envelope for me ????
<currenlty HTTPInput/HttpListener generates SOAP fault messages for timeout related failures , that gives me a feeling that SOAP message generation is inbuilt within WBIMB - WHERE/HOW to activate it in other nodes ???? >
Please shed some light on how you normally accomplish this .. ? |
|
| Back to top |
|
 |
| JosephGramig |
| Posted: Tue Sep 05, 2006 10:30 am Post subject: HTTP/SOAP Service |
|
|
Grand Master
Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA
|
There is an example Samples Gallery - Technology samples - Message Brokers - Web Service.
I don't think your systax '{SOAP}' is correct...
You can generate WSDL and thus a message set to be used. You will need a message catagory in the messge set before you generate the WSDL.
_________________
Joseph
Administrator - IBM WebSphere MQ (WMQ) V6.0, IBM WebSphere Message Broker (WMB) V6.1 & V6.0
Solution Designer - WMQ V6.0
Solution Developer - WMB V6.1 & V6.0, WMQ V5.3 |
|
| Back to top |
|
|
| iceage |
| Posted: Tue Sep 05, 2006 11:11 am Post subject: |
|
|
Acolyte
Joined: 12 Apr 2006
Posts: 68
|
Thanks for your reply ..
I wen through those samples and they are using MESSAGE SET , i searched the forum about MESSAGE SET being mandatory for Web Services ( from what i gathered from that discussion it is NO) ..
That being said , i am also personaly reluctant to take the Message Set approach.
I am looking to find out if any inbuilt (PARSER support - if you would) support for SOAP , just like other headers (MQMD , etc .. ) or any other solution ...
I am using {SOAP} syntax , as i have declared SOAP as a CHARACTER datatype. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Sep 05, 2006 11:13 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You should use a real namespace prefix, instead of using an interpolated variable. "Declare SOAP namespace...".
SOAP is supposed to be just pure XML. So you should just be able to build your message entirely by hand using the XMLNSC parser.
There is not a predefined parser for SOAP that is separate from the XMLNSC parser - currently.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| iceage |
| Posted: Tue Sep 05, 2006 11:19 am Post subject: |
|
|
Acolyte
Joined: 12 Apr 2006
Posts: 68
|
Point taken on using NAMESPACE datatype.
In regards to building the SOAP tree in ESQL ( which is what i have now) , what if SOAP format changes ... that means change to the code ?
Wouldnt be nice to have WBIMB generate SOAP headers , as it is in HTTPInput node to choose different SOAP fault format ??? |
|
| Back to top |
|
|
| msukup |
| Posted: Wed Sep 06, 2006 8:16 am Post subject: |
|
|
Acolyte
Joined: 11 Feb 2002
Posts: 56
|
|
| Back to top |
|
|
| iceage |
| Posted: Wed Sep 06, 2006 5:11 pm Post subject: |
|
|
Acolyte
Joined: 12 Apr 2006
Posts: 68
|
| Thanks , that might be a solution .. I shall review that . |
|
| Back to top |
|
|
| mgk |
| Posted: Thu Sep 07, 2006 12:14 am Post subject: |
|
|
Padawan
Joined: 31 Jul 2003
Posts: 1642
|
Hi,
I'm just curious. What is your objection to using the MRM to model the soap envelope, as per the sample?
_________________
MGK
The postings I make on this site are my own and don't necessarily represent IBM's positions, strategies or opinions. |
|
| Back to top |
|
|
| JosephGramig |
| Posted: Thu Sep 07, 2006 12:14 pm Post subject: I got it to work... |
|
|
Grand Master
Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA
|
What I did was:
1) create a Message Set Project
2) create a Message Set (check Use namespaces) and XML wire format
3) Imported the XSDs for the request and response documents
4) Built a Message Definition File w/the IBM supplied SOAP env 1.1
5) Built a Message Def File from the request XSD
6) Built a Message Def File from the response XSD
7) Built a Category File and selected the request (input) response (output)
 Generated the WSDL
9) Built the Message Flow Project (referencing the MSP just created)
10) Built the Message Flow w/ HTTPInput, Compute, HTTPReply
11) on the HTTPInput basic, set the URL selector
12) On the HTTPInput default, set MRM, Message Set (above), Type=Envelope, Format=XML
13) Big hint: Use the code assist in the ESQL! When you reference soapbody and your message, definitions will be added to your code. Don't be suprised by the null1 bla bla stuff. You chan change that...
Good luck
_________________
Joseph
Administrator - IBM WebSphere MQ (WMQ) V6.0, IBM WebSphere Message Broker (WMB) V6.1 & V6.0
Solution Designer - WMQ V6.0
Solution Developer - WMB V6.1 & V6.0, WMQ V5.3 |
|
| Back to top |
|
|
|
|
