Author |
Message
|
shubha_s |
Posted: Tue Mar 02, 2010 5:04 am Post subject: Http response |
|
|
Acolyte
Joined: 10 Mar 2009 Posts: 57
|
Hi,
I am calling a webservice using HTTP Request nodes. The webservice will give some response, either success or failure..
If the response from webservice is failure then the message goes to the failure terminal of the HttpRequest node and then i have redirected it to a queue..But i want to place a compute node before the MQOutput node n modify the response in case of failure and then put that message to MQOutput queue..
Thanks |
|
Back to top |
|
 |
mqjeff |
Posted: Tue Mar 02, 2010 5:17 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
Yes, you can do that.
 |
|
Back to top |
|
 |
shubha_s |
Posted: Tue Mar 02, 2010 5:43 am Post subject: http response |
|
|
Acolyte
Joined: 10 Mar 2009 Posts: 57
|
mqjeff wrote: |
Yes, you can do that.
 |
But how do i extract the description that http request node failed because of some reason. like <not authorised> or some exact reason..How do i do this?? |
|
Back to top |
|
 |
mqjeff |
Posted: Tue Mar 02, 2010 5:50 am Post subject: Re: http response |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
shubha_s wrote: |
mqjeff wrote: |
Yes, you can do that.
 |
But how do i extract the description that http request node failed because of some reason. like <not authorised> or some exact reason..How do i do this?? |
I'm not at all sure how you would do this.
I would do this by writing ESQL. |
|
Back to top |
|
 |
Guaresnay |
Posted: Tue Mar 02, 2010 7:43 am Post subject: |
|
|
Newbie
Joined: 10 Feb 2010 Posts: 8
|
|
Back to top |
|
 |
Svp |
Posted: Tue Mar 02, 2010 12:33 pm Post subject: But how do i extract the description that http request node |
|
|
Apprentice
Joined: 18 Feb 2010 Posts: 40
|
Hi Shuba,
You can extract the reason for the failure by accesing the Exceptionlist using ESQL.
You can get the Number and Text in the Exceptionlist tree which gives the reason for your failure.
Search for Accessing the ExceptionList tree using ESQL in Infocenter. |
|
Back to top |
|
 |
shubha_s |
Posted: Tue Mar 02, 2010 11:58 pm Post subject: Re:http response |
|
|
Acolyte
Joined: 10 Mar 2009 Posts: 57
|
Svp wrote: |
Hi Shuba,
You can extract the reason for the failure by accesing the Exceptionlist using ESQL.
You can get the Number and Text in the Exceptionlist tree which gives the reason for your failure.
Search for Accessing the ExceptionList tree using ESQL in Infocenter. |
Though i acess the exception list from ESQL, where do i update the values from which the sender will know what the exact error is.
Can any1 throw some light on this?? |
|
Back to top |
|
 |
shubha_s |
Posted: Wed Mar 03, 2010 12:26 am Post subject: Re:http response |
|
|
Acolyte
Joined: 10 Mar 2009 Posts: 57
|
shubha_s wrote: |
Svp wrote: |
Hi Shuba,
You can extract the reason for the failure by accesing the Exceptionlist using ESQL.
You can get the Number and Text in the Exceptionlist tree which gives the reason for your failure.
Search for Accessing the ExceptionList tree using ESQL in Infocenter. |
Though i acess the exception list from ESQL, where do i update the values from which the sender will know what the exact error is.
Can any1 throw some light on this?? |
I am able to access the exception tree but what do I do with the exception message.How do I construct a message and redirec to a queue. |
|
Back to top |
|
 |
Svp |
Posted: Wed Mar 03, 2010 6:17 am Post subject: |
|
|
Apprentice
Joined: 18 Feb 2010 Posts: 40
|
You can have a Failure Terminal--->compute node---> MQ o/p .Get the exception details using the ESQL in compute node and send it to Q. |
|
Back to top |
|
 |
mqjeff |
Posted: Wed Mar 03, 2010 6:47 am Post subject: Re:http response |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
shubha_s wrote: |
How do I construct a message and redirec to a queue. |
As I said you do this with ESQL.
This is *basic* broker skills. If you can't do *this*, then you need to stop asking for help and start doing your own learning. This forum is *not* a training facility nor is it a consulting practice.
It is a learning *resource*, but you must *do* the learning. Read, search, think, try, read again. |
|
Back to top |
|
 |
|