There are many ways to integrate things. All have their price. With web services, the data structures you can send in a single transaction are very limited; you have several layers of infrastructure that must be available; failed transactions are lost; etc. With db link there are potential delays an implications with workflow if you are updating data in remedy through the db.
No one approach is the best approach in every case. You have to look at each case and outline what you intend to accomplish with the integration. Is there a need for real time updates? Is there a need to block a transaction if the integration fails? is there a need for a message queue so that failed operations can be retried? Is there a need to fetch data in real time? What is the expected volume of data? How is the data used in your Remedy applications? How will you handle updates to data? And the list of questions to drive the appropriate solution go on and on. Take a good look at what you are trying to do then make a determination on what type of integration is most appropriate. On Tue, Jul 6, 2010 at 5:08 PM, NNMN <[email protected]> wrote: > Hi ARSers, > > Something which i have been thinking about. I want to know your views on > this. > Let us imagine we have systems, SYS-A(Remedy with its backend) and > SYS-B(another platform app(like java,.NET etc) with its backend). Now if i > want the data from both these systems to flow from each other for certain > interactions, lets say i have the possibility of below methods. > Method-1) I use web-services exposed from both sides to mutually call and > get the input/output approprately and thus i acheive transactions. > Method-2) I expose some relavant schema details as DB links and then i > access them from where ever required (as view forms Remedy). > > Now i want to know about the pros and cons of above methods with respect to > . I always feel that Method 2 is kind of crude way of implementing, but in > a > way i get this feeling from many i talked, that it is an easier and > effortless way to go about it. Still thinking on a long term, reliability, > data-transfer speed etc > factors. > > Cheers, > Naveen > > > ----- > With Warm Regards, > Naveen > -- > View this message in context: > http://old.nabble.com/DB-Links-vs-Webservices-tp29084418p29084418.html > Sent from the ARS (Action Request System) mailing list archive at > Nabble.com. > > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
