The definitive guide to patterns and strategies that solve the challenging problems with J2EE and .NET integration.

Marina Fisher is a staff engineer at Sun Microsystems Ray Lai is a principal engineer from Sun's Chief Technologist's Office and specializes in financial services and SOA solutions Sonu Sharma is an engagement manager with Client Solutions Organization at Sun Laurence Moroney is the director for technology evangelism for Mainsoft

= 0) {slash = '\\';} else {slash = '/';}openLoc = figLoc.substring(0, figLoc.lastIndexOf(slash) + 1);while (pPage.substring(0,3) == '../') {openLoc = openLoc.substring(0, openLoc.lastIndexOf(slash, openLoc.length - 2)+ 1);pPage = pPage.substring(3, pPage.length + 1);}popUpWin =window.open('','popWin','resizable=1,scrollbars=1,location=0,toolbar=0,width=525,height=394');figDoc = popUpWin.document;zhtm= ' ' + pPage + ' ';zhtm += ' ';zhtm += ' ';zhtm += ' ';zhtm += '' + pPage.substring(pPage.lastIndexOf('/') + 1, pPage.length) + '';zhtm += ' ';figDoc.write(zhtm);figDoc.close();}// modified 3.1.99 RWE v4.1 --> Introduction: Achieving Interoperability Introduction: Achieving Interoperability Business ChallengesIt is a common trait for business to have large and diverse systems and a rare one for them to have unified systems. Be it through acquisitions, mergers, staff and policy turnover, or a hundred other reasons the fact remains--they have systems built in different languages, running on different software platforms, and targeting different hardware. Add on top of this the need for businesses to be increasingly more nimble--fueling a requirement for integrated, interoperating systems that can aggressively respond to business requirements coherently and quickly--and you have a major challenge facing businesses today.A few years ago the typical business data system was a simple, monolithic affair with business assets in a mainframe that were accessible via a tightly coupled user interface. Transfer of assets between domains was usually manual--for example the transfer of an order from a sales-facing system to a realization and delivery system was typically done by an operator keying in details of a printout from one system to the other. The operator herself was the interoperability layer.Over time as systems evolved, technologies evolved to allow networking and to automatically integrate across protocols such as CORBA. These, however, proved to be very difficult and expensive to develop and maintain.Today's landscape sees the data center split into two main deployment types. On one side is the Microsoft stack of products, covering everything except the hardware, from the operating system through the software platform to the application, with the Windows Server family and the .NET framework and runtime. Developers have a host of tools that allow them to develop and target this platform and can receive exceptional time to market and cost of development metrics. On the other side is the open family of Java EE software frameworks, which can run on a variety of hardware platforms and that run applications written with the Java language. With this it has been sh