I agree if you are going to use WS I would use some kind enterprise bus. I had a custom app that used See Beyond I think it was called and it worked wonders. You can send the info to the Enterprise Bus in real time and then the Enterprise Bus can sent it whenever, queue it up for nightly push, real time etc..... Also what we did with the See Beyond was added workflow that would push back a success when modified so you would know it went through and if it did not the Enterprise Bus could keep trying to send it till it got a success.
On Thu, Jul 15, 2010 at 3:17 PM, Guillaume Rheault <[email protected]>wrote: > ** > What I would ask the customer is whether some kind of "retry" mechanism > is needed, in case there is some kind of data error, or even worse a network > problem. > So... you may need a enterprise bus to queue the web service messages to > perform the retry, or some custom .net or java code (i.e. a web service in > between the Remedy ITSM services) to handle error and retries > > Guillaume > > > ------------------------------ > *From:* Action Request System discussion list(ARSList) [ > [email protected]] on behalf of Danny Kellett [ > [email protected]] > *Sent:* Tuesday, June 15, 2010 9:14 AM > *To:* [email protected] > *Subject:* Web Services with ITSM > > ** > > Hi all, > > > > I have a customer who wishes to use Web Services as their > main communication between two ITSM systems for incident problem and change. > I know this is possible but I was wondering if any of you have had any > experiences with this with regards to good or bad really. Also they have > specified communication over SSL. > > > > Thanks for your time, > > > > Kind regards > > Danny > > > _attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_ > _attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_ -- Kevin Begosh _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
