| So did one of our customers. We won't mention them by name here but this is their story. NOTE: Amdocs, Siebel and Tibco are registered trademarks of those software application vendors. For many years leading up to 2003, the firm had attempted to integrate their CRM system (Siebel) with Amdocs, their core business application. The business case for the proposed interoperability was attractive, with real time transactions eliminating a cumbersome manual work-around currently being performed by staff. By April 2003 the substantial integration efforts had been marginally successful, with a number of simpler transactions in prototype operation. However, the effort and elapsed time required to thread together the remaining (more complex) transactions was looking prohibitive. To move things forward, a conceptual solution was put forward: utilize the firm's Tibco service bus infrastructure to process the requests from Siebel, perform the necessary business processing and make the necessary invocations within Amdocs. A sound concept - the final piece of the puzzle being to tie the Tibco integration workflow into Amdocs. That's where the integration project stalled. That's usually our call to arms. How did me make it work? Simple. Working with the integration team, our man on the ground spotted that the Amdocs exhibits an industry standard CORBA interface - albeit an extremely complex one. Not fazed, a standard Industry BabelTube (SOAP2CORBA) neatly bridged the interoperability gap between the service bus and the CORBA interface, as depicted in the diagram below. |