SOA Integration
In a typical SOA infrastructure, client applications connect to a central integration suite or Enterprise Service Bus (ESB) which then starts the appropriate business process using a form of integration middleware called a protocol adapter. Protocol adapters can be either SOAP/XML based (ie, Web Services) or non-SOAP/XML based (eg, RMI, JDBC, DCOM, .NET Remoting, RMI-IIOP).
Protocol adapters link applications directly to each other or to other forms of middleware such as portals and application servers. They serve a complementary role to full-featured integration suites and ESBs by bridging the gap between various applications and integration middleware (for example, when Web Services interfaces are unavailable or not desired).
J-Integra® Protocol Adapters
We provide four different protocol adapters:
- DCOM Adapter for Java COM Interoperability
- DCOM Adapter for Java Exchange Interoperability
- .NET Remoting Adapter for Java .NET Interoperability
- RMI-IIOP Adapter for Java .NET CORBA Interoperability
Advantages
Customers use J-Integra® protocol adapters for the following reasons:
- Migration - Use as a short-term solution while you migrate to a complete SOA infrastructure.
- Performance - Provides huge advantages over Web Services in both performance and scalability.
- Cost Reduction - Easy to use, accelerates deployment, and provides significant cost savings.