| Author |
Message
|
| satya2481 |
 Posted: Thu Jan 05, 2012 8:45 pm Post subject: Webservice Issue -- Document Type Invocation |
 |
|
Disciple
Joined: 26 Apr 2007
Posts: 170
Location: Bengaluru
|
Hi,
The flow calls an outbound web service and flow consists of HTTPRequest node which makes the webservice call from broker.
We have the SOAP message sending to webservice and the SOAP Action is also populated in the HTTPRequestHeader as per the WSDL.
But, still web service is responding with below error.
faultstring>SOAPAction '<?>' is of invalid format: SOAPAction should be of the form "rpc/operationName" or "document/operationName"</faultstring>
My httprequest header looks as below.
CREATE LASTCHILD OF OutputRoot NAME 'HTTPRequestHeader';
SET OutputRoot.HTTPRequestHeader.SOAPAction = 'document/http://siebel.com/asi:OppStatusMod';
SET OutputRoot.HTTPRequestHeader.Operation = 'OppStatusMod';
SET OutputRoot.HTTPRequestHeader.Style = 'Document';
Any help and suggestions on the same is really helpful is debugging the issue.
Thanks,
_________________
IBM Certified Solution Developer WebSphere Message Broker V6.0
IBM Certified System Administrator WebSphere MQ V6.0 |
|
| Back to top |
|
 |
| ruchir123 |
| Posted: Thu Jan 05, 2012 11:46 pm Post subject: |
|
|
Acolyte
Joined: 04 Jan 2012
Posts: 58
|
Hi satya,
Your fault code says your SOAP action is not of correct format.
It may be because your SOAP operation is not matching or may be your WSDL is expecting different response.
It will be helpful if you provide more details about your issue.
Exactly at what point you are having this issue and what your flow is.
Thanks  |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Fri Jan 06, 2012 12:28 am Post subject: Re: Webservice Issue -- Document Type Invocation |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| satya2481 wrote: |
Hi,
The flow calls an outbound web service and flow consists of HTTPRequest node which makes the webservice call from broker.
|
Why are you making extra work for yourself using the HTTPRequestNode?
It would be nice for you to explain why you are not using a SOAPRequestNode.
_________________
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 |
|
|
| satya2481 |
| Posted: Fri Jan 06, 2012 1:00 am Post subject: Resolved |
|
|
Disciple
Joined: 26 Apr 2007
Posts: 170
Location: Bengaluru
|
Hi All, thank you very much for a quick response.
The project requirement is to use HTTP nodes only even though WSDL is available.
After putting the SOAPAction value inside double quotes the issue gets resolved 
| Code: |
| SET OutputRoot.HTTPRequestHeader.SOAPAction = '"document/http://siebel.com/asi:OppStatusMod"'; |
Thank You
Satya |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Jan 06, 2012 5:20 am Post subject: Re: Resolved |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| satya2481 wrote: |
| The project requirement is to use HTTP nodes only even though WSDL is available. |
That's not an answer. "We do this because that's what we do" is not a reason, it's blindly following an arbitrary rule.
Why are you not using the WMB features to handle SOAP? Extending the position, you shouldn't use a message set to parse a file but should chop it up longhand in ESQL....
Bear in mind that while you've solved this issue, you'll need to solve the next problem SOAP throws at you. And the next, and the next, and all those solutions are built into the SOAP nodes. And all those solutions you write will result in additional code, and additional gotchas (you're better be sure the rest of your project team knows to put in double quotes & not to take them out). and your management knows about all this additional maintenance effort you're creating.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Fri Jan 06, 2012 5:51 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
I've run into this alot. Stepping into a new assignment, I notice huge amount of mal-thought message flows. When I start probing the legacy resources, the answer I get back is "well, we had this WMB consultant and they didn't like to use Trace nodes. So our management said we were not allowed to use Trace nodes." -- or-- "We were forbidden from applying any service to the toolkit, and we can't figure out why ?wsdl property setting doesn't work" -- or -- "we were told that using bar file overrides were a bad idea, so we have to build bars for each environment."
All of this is the product of people who haven't the time or desire to attend a simple 5 day training class. Hogwash.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Jan 06, 2012 6:10 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| lancelotlinc wrote: |
| I've run into this alot. |
 (and how often do you see that on one of my replies to lancelotlinc??)
Or in the wider context:
"you can't change that system / application, you just have to build round it"
which is a result of someone years ago not having the time or the nerve to speak to those responsible to ask for a change, and it becoming folk knowledge passed down through the elders of the tribe round a campfire built of burning design documents.
The other (less technical) classic is the report from the existing the business users consider critical and which is the one you just can't quite get from your new, shiny system. In the majority of cases investigation indicates that the last person who actually read the report retired years ago and no-one actually knows what it's for.
True war story - part of a mainframe output reduction project (don't laugh!) back in 1980s. Investigating one report which was about half an inch of green music ruled 133 character (younger readers can Google it). Checking the receiving department, I was proudly shown the cabinet in which all of these reports were filed unread, the ring binder in which they were ticked off and the procedures for taking the old ones out & placing them in the warehouse for storage, shuffling the reports into that space so all the new ones were at the top and clearing the reports out of the warehouse once they were 5 years old. I was impressed with the system, and the efficientcy with which it was applied.
"So what's the report for" I asked.
"Oh, I don't know that dear" (the office manager was a lady of a certain age, it was 30 years ago & I was still a dear) "one of the actuaries requested it once but they've never looked at it since."
The actuaries had no idea what it was for either but alarmingly thought "we should keep producing it, perhaps electronically, just in case".
If only trout had been invented back then.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
