You're describing the exact scenario for which enterprise messaging was designed. I recently helped a customer build an integration solution between AR System and a couple of external systems. They had already decided on a message queuing system, because they needed something scalable, robust, and decoupled from the applications themselves. The also needed messages to arrive in sequence, with guaranteed delivery. The customer in question had settled on Weblogic MQ, but they could just as easily picked ActiveMQ, WebsphereMQ, SonicMQ, etc.
We had time only for a proof of concept, and there was no way we could even consider building something from scratch, so we decided to go with Java System Solutions' XML Gateway. Full JMS capabilities are now built right into the gateway, so it's just a matter of configuration. Creating the interface forms in Remedy was a piece of cake, of course. And we had the gateway templates ready to run with a modicum of effort. (Side note: Have you noticed development is always significantly faster on the Remedy side? Over the past decade or so I can't tell you how many times I've said, "We're ready to test," and the team on the other end is still firing up Visual Studio or Eclipse or whatever.) The transfer speeds we saw in the POC were phenomenal. We didn't have time to test everything under high load conditions, but I have to think we would have fared pretty well since the solution can be scaled up by adding threads to AR System, XML Gateway, etc. Naturally, all situations are different. If the payload size is very large, the network is already swamped with traffic, or your hardware is underpowered, you'll hit the wall sooner than later. For all the requirements you list below, along with fault tolerance, scalability, flexibility, and ease of use, you can't beat XML Gateway. http://www.javasystemsolutions.com/jss/xmlgateway --Tim (No, I do not work tor Java System Solutions.) ________________________________ From: "HonnourPrahalladachar, PhaniRaja" <[email protected]> To: [email protected] Sent: Thursday, June 18, 2009 10:10:24 AM Subject: [ARSLIST] Integration - Turn Around Time ** Hello List, I’m working on integrating ITSM 7 (ARS 7.1) with other service management applications of multiple organizations located in varied geographies. A middleware will be used to communicate with the end point applications. It will be a one-to-many, bi-directional integration. Main features that are expected in this integration are: 1. message validation 2. message translation 3. guaranteed delivery of the messages 4. sequencing of the messages One of the key requirements is to be able to process every message (or average) within 60 seconds. What has been your experience on time required in processing messages in such integration applications? Is 60 seconds reasonable time for processing messages considering load scenarios where we there may be several hundred messages to be processed for publishing & consuming? Thanks & Regards, Phani Please help Logica to respect the environment by not printing this email / Pour contribuer comme Logica au respect de l'environnement, merci de ne pas imprimer ce mail / Bitte drucken Sie diese Nachricht nicht aus und helfen Sie so Logica dabei die Umwelt zu schuetzen / Por favor ajude a Logica a respeitar o ambiente não imprimindo este correio electrónico. This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you. _Platinum Sponsor: [email protected] ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are"
