ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » HTTP Input Node - Best Practices

Post new topic  Reply to topic
 HTTP Input Node - Best Practices « View previous topic :: View next topic » 
Author Message
wilsonjohn24
PostPosted: Thu Dec 27, 2007 3:54 am    Post subject: HTTP Input Node - Best Practices Reply with quote

Voyager

Joined: 02 Feb 2007
Posts: 93
Location: Scotland

Hi,

The HTTPInput node has 3 out terminals. Failure/Catch/Out.

Is it ok practice not to wire up the Catch/Failure nodes to any error handling routine as this node "automatically generates" soap fault responses?


thanks for your views in advance


John
Back to top
View user's profile Send private message
wilsonjohn24
PostPosted: Fri Jan 04, 2008 11:51 am    Post subject: Reply with quote

Voyager

Joined: 02 Feb 2007
Posts: 93
Location: Scotland

Hi,

Was hoping that someone has an view on this or what have they done on past flowss?

Here was my view......

I do not see any reason to attach anything to the catch or error terminals- unless you want to override the error handling. But on the whole the default behaviour of the HTTP Input node is excellant - it handles responses to timeouts and errors by packaging them into SOAP fault xml and sending it back to the http client.

My view is dont try to recode anything that IBM provides out of the box........Without a dam good reason
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Sat Jan 05, 2008 9:07 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

The HTTPInput node doesn't know about SOAP faults, I think.

I think you'll find that it's the IA90 nodes that know about SOAP faults.

Or the SOAP nodes in v6.1.

The same reasons one might hook up catch/failure terminals on an MQInput node apply to an HTTPInput node - specialized processing, error logging, etc.

I might tend to do the same thing with both - hook up catch to perform error logging and then rethrow the original exception.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
wilsonjohn24
PostPosted: Mon Jan 07, 2008 10:55 am    Post subject: Reply with quote

Voyager

Joined: 02 Feb 2007
Posts: 93
Location: Scotland

Thanks for that jefflowrey

What I was meaning that you can set a property of the HttpInput node to automatically return exceptions as soap 1.1/soap 1.2/http formats.

I think you have answered by question ( at least gave more confidence).. I just wanted to ensure that their would be no major gotchas associated with not wiring these terminals up.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » HTTP Input Node - Best Practices
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.