Correcting the subject of the email. Thanks Karthik On 12 September 2012 22:02, Karthik <[email protected]> wrote:
> I have a requirement to integrate 2 or more remedy systems and other > ticketing tools built on different technologies like Java . > > Scenario: Remedy servers A, B, C, D are on different versions of remedy > ranging from 7.1 to 7.6. When incidents are assigned to a particular > assigned group, an incident should be created on a remedy server E on 7.6. > Once a ticket is created on Remedy server E, the integration should be > birectional. i.e. status updates should flow through between the servers. > Similar should happen even when incidents are raised and assigned on > different ticketing tools built on various technologies. > > Assumption: > - Remedy servers are DSO enabled > - Other ticketing tools support web services. i.e. can expse and consume > web services. > > Below are few approaches, i have thought of and need suggestions on these > approaches or please feel free to recommend any other approaches as well: > > 1. Build staging forms on both soure and target systems to handle > transactions. > 2. Data to this staging form can be populated in following different > manners: > > a. Integrate remedy servers using DSO and integrate with other systems > using web services so that same staging form handles the transactions using > same workflows > > - I need to understand if DSO is backward compatible. say for ex: can > we establish DSO between 7.1 and 7.6? > > b. Integrate all the systems(remedy/non remedy) using web services > c. Use an orchestrator tool like BMC Atrium Orchestrator > > Thanks > Karthik > > > > > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
