Hi Vikrant, We work for a number of different clients and by using AO we just want to generalize this process. We will publish AO Legacy web services and then client can consume it easily. Also suppose if next client comes and they use any tool other than remedy, in that case also we can make use of same web services.That's why our management wants us to proceed with the AO option and we have done almost everything other than taking care of error handler process. I am not able to design a process which comes handy in case our AO is down.All modifications will be lost on even 1 side which we want to store in a temporary table and then resend them again with the help of an escalation.
Regards, Vivek --- On Sun, 2/3/13, Kulkarni, Vikrant <vkulka...@columnit.com> wrote: From: Kulkarni, Vikrant <vkulka...@columnit.com> Subject: Re: Issues with Remedy Ebonding- Consuming AO process through Filter To: arslist@ARSLIST.ORG Date: Sunday, February 3, 2013, 5:39 PM Why not use the DSO process for this? Vikrant Sent from my Xperia™ smartphone Vivek Garg <vivek_ussd...@yahoo.com> wrote: Hi, We are trying to achieve remedy ebonding i.e. bidirectional incidents sync between 2 remedy systems. We have created an AO(Atrium Ochestrator) process which we are trying to consume through set fields action in a filter. Now we want the update/modifications to happen first on remedy 1 and then our filter should call AO process to make the same changes on 2nd remedy.If there is some issue with the AO like CDP is down or for any reason my AO process failed, then we do not want to loose changes made on remedy 1, we want to store these changes in a temporary table and with the help of an esclation we want to resend these changes again through our AO process once it's up. Basically what I want to know is that how should I design such a workflow which ensures that AO process must be called after changes successfully gets stored on Remedy 1. Please suggest some approach to implement this. Thanks , VIvek _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
