I have never used Shareplex but have talked to some people that supported a large DoD agency that used it (I think maybe the project Dylan worked on). It sounded pretty impressive performance wise and they were happy with it. >From what I understand there are a few things to watch out for like doing admin work as LJ has suggested and I think that it takes a while to get it all setup and working as desired.
In regards to DSO, the same large DoD agency (in another area) has (or had) a pretty good size DSO infrastructure to pass requests to the various Remedy systems. One draw back to this is that none of the admin code is synchronized and you would have to run DSO filters/mappings on all forms that you want to replicate/fail over. If you are looking for complete data synchronization I could see how this could be a lot to manage and this would not replicate admin changes. This was all fine for this implementation because they only synchronized data between one form and this also allowed them to keep their own systems customized. I mentioned that they had a DSO infrastructure... They have mostly moved to ARSXML (looks like it now called ARSXLink). This is a better product for their application. I think the performance is better and it is more reliable. It also handles data conflicts better then DSO. I believe that Gidd is a reseller of ARSXML. Here is a link http://www.ntuition.de/index.php?arsxlink_en. HTH, Jason On Wed, May 14, 2008 at 10:01 AM, LJ Longwing <[EMAIL PROTECTED]> wrote: > ** The only caveat that I would put on this is that if you are doing total > db sync then you would need to do development on only one of the servers (or > deploys as it may be) and then restart the other remedy server after the > modifications were made, or run an arsignal. > > ------------------------------ > *From:* Action Request System discussion list(ARSList) [mailto: > [EMAIL PROTECTED] *On Behalf Of *Rick Cook > *Sent:* Wednesday, May 14, 2008 9:49 AM > *To:* arslist@ARSLIST.ORG > *Subject:* Re: synchronization of servers > > ** I don't have any experience with this product, but I will say that by > doing your syncing via DB replication, I think you're on the right track. > It's the fastest way I know of to do what you're doing. > > Rick > > On Wed, May 14, 2008 at 8:43 AM, Zoltán Nemes <[EMAIL PROTECTED]> wrote: > >> ** Dear Listers! >> >> There will be major changes in our Remedy system architecture soon and we >> are trying to be prepared with a concept to support it. >> >> Our company currently uses one production server for ticketing purpose. >> The server is located in Europe. >> According to the new plans, there will be a new production server deployed >> for the USA region. Both these servers has to be real-time synchronized and >> they would have to contain the same case related data, so that they can >> replace each other in case of failures or outages. >> >> The no-brainer solution of course would be DSO. But considering the amount >> of data to be transferred, our belief is that with DSO the overhead on the >> systems will be huge and this leads to intensive network traffic that would >> cause performance problems for us. >> >> We are planning to use a solution based on a database syncronization >> product called Shareplex for Oracle. >> >> Does anyone of you have experience in synchronizing Remedy using this >> product? What are you guys using for syncing your systems? >> >> I would appreciate if you shared your ideas with me. >> >> Thanks, >> Zoltan >> >> __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" >> html___ > > > __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" > html___ > __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" > html___ > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
