Chad. Thanks for the info. I guess there is nothing I can do about 
capturing the error message using standard Remedy workflow. That's ok 
though. I know that if the escalation fails, the Web Service is down which 
is good enough for me. I am just happy that I managed to get it working!

Many thanks,

Mike.




Hall Chad - chahal <[EMAIL PROTECTED]> 
Sent by: "Action Request System discussion list(ARSList)" 
<arslist@ARSLIST.ORG>
03/01/2007 17:14
Please respond to
arslist@ARSLIST.ORG


To
arslist@ARSLIST.ORG
cc

Subject
Re: Suppressing Web Service errors.






** 
Well, we actually have a separate middleware layer that is almost always 
available. That?s actually the web service that Remedy calls. That 
middleware web service then turns around and calls the appropriate 
external web service and returns any error messages it gets back to 
Remedy. So as long as our middleware web service is running it works fine. 
It took a lot of coordination though to get that middleware web service 
setup to handle all the data that could come through it and make sure, 
based on some of that data, that it gets sent to the correct external web 
service.
 
Our middleware web service uses the Java API to communicate with Remedy.
 
Chad Hall  
(501) 342-2650

From: Action Request System discussion list(ARSList) 
[mailto:[EMAIL PROTECTED] On Behalf Of Michael Worts
Sent: Wednesday, January 03, 2007 10:35 AM
To: arslist@ARSLIST.ORG
Subject: Re: Suppressing Web Service errors.
 
** 
Chad, 

Funny enough, that is exactly what I have developed. I have an escalation 
that tests the web service (every 1 minute) and returns a timestamp. If 
there are any errors, the escalation fails and does not return the 
timestamp. I have not been able to get the web service to return an actual 
error code or message, it just fails and the error appears in the 
escalation log. How have you managed to capture the error? 

As you said, if there is a problem with the web service at least it does 
not stop the user from logging the record. I have another escalation that 
keeps retrying the failed records. 

Many thanks for your response. 

Mike. 

Michael Worts
Remedy Specialist
IGS, Business Consulting Services
ITIL Service Manager Certified
Tel: +44 (0)1962 822273   Mob: +44 (0)7801 755346   Internet: 
[EMAIL PROTECTED] 


Hall Chad - chahal <[EMAIL PROTECTED]> 
Sent by: "Action Request System discussion list(ARSList)" 
<arslist@ARSLIST.ORG> 
03/01/2007 15:02 


Please respond to
arslist@ARSLIST.ORG



To
arslist@ARSLIST.ORG 
cc
 
Subject
Re: Suppressing Web Service errors.
 


 
 




** 
We call our external web services in escalations and have those external 
web services setup to return an error code which we store in a field on 
the Remedy form. We can then use filters on this field to trigger a 
notification or open a ticket if certain known unrecoverable errors occur 
that would need manual intervention. If it?s a recoverable error we simply 
let the escalation retry it during the next cycle. It works pretty well 
and prevents users from ever getting errors that would stop them from 
saving a ticket. 
  
Chad Hall  
(501) 342-2650 
 


From: Action Request System discussion list(ARSList) 
[mailto:[EMAIL PROTECTED] On Behalf Of Michael Worts
Sent: Friday, December 22, 2006 9:24 AM
To: arslist@ARSLIST.ORG
Subject: Fw: Suppressing Web Service errors. 
 
** 
Hi again, 

I am really struggling to find a solution for this one. I have tried 
executing the Web Service form an Escalation and it did suppress the error 
message but only because the escalation failed, which meant I never got my 
failure message. 

Any ideas? Half ideas? 

Mike. 

Michael Worts
Remedy Specialist
IGS, Business Consulting Services
ITIL Service Manager Certified
Tel: +44 (0)1962 822273   Mob: +44 (0)7801 755346   Internet: 
[EMAIL PROTECTED] 
----- Forwarded by Michael Worts/UK/Contr/IBM on 22/12/2006 15:08 ----- 

Michael Worts/UK/Contr/IBM 
21/12/2006 23:28 
 


To
arslist@arslist.org 
cc
 
Subject
Suppressing Web Service errors.

 
 


 
 




Hello everyone, 

I would like the ability to suppress any error messages that are returned 
from my Web Services call. Say for example, if the web service I call is 
unavailable for whatever reason, I do not want the error to appear on the 
screen. I  would prefer to do the error handling through workflow, it is 
much neater. 

Any ideas? 

Many thanks, 

Michael. 

AR 6.3 Patch 11, Oracle 9i, AIX 5.2 __20060125_______________________This 
posting was submitted with HTML in it___ 
*************************************************************************
The information contained in this communication is confidential, is
intended only for the use of the recipient named above, and may be
legally privileged.

If the reader of this message is not the intended recipient, you are 
hereby notified that any dissemination, distribution or copying of this
communication is strictly prohibited.

If you have received this communication in error, please resend this
communication to the sender and delete the original message or any copy
of it from your computer system.

Thank you.
*************************************************************************

__20060125_______________________This posting was submitted with HTML in 
it___ 
__20060125_______________________This posting was submitted with HTML in 
it___
__20060125_______________________This posting was submitted with HTML in 
it___ 

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the 
Answers Are"

Reply via email to