How is Integration between Java and .NET Achieved
Java J2EE applications and .NET applications are equally competitive. Most of the applications currently existing use one of these two technologies. There are situations where your application has to communicate with other applications for achieving a particular functionality.
For example, when you are booking tickets online, the ticket reservation application has to communicate with the payment gateway which in turn communicates with the banks online application for fund transfer. What if your application is developed using .NET and the application you want to connect is developed using Java? How do you achieve interoperability between these two applications and perform the integration? This article will give you an overview on what all different ways are there to perform such integration.
SOA stands for Service Oriented Architecture. Using SOA you can integrate Java and .NET application by following the steps given below:
that both Java and .NET applications are WS-I complaint. Only then web
services can be created
Bridging is yet another alternative for integrating java and .net applications. Assume that your .NET application has to interact with an Enterprise Java Bean (EJB) of a J2EE Application. In that case, you can use bridging. Here is the set of steps involved in bridging:
a client application that will interact with the EJB
Many third-party vendors provide tools to perform integration using bridging. One such most commonly used tool is Ja.NET which belongs to Intrinsync Solutions. When you are using bridging, you need not have to concentrate on the protocols. Tool that provides bridging will do all that you want. You have to concentrate on the normal coding for creating the client application.
This is an interesting option used by Banks and other financial concerns to establish communication between two systems implemented using different technologies. For example BANK A has to send secured data to BANK B wherein BANK As application is built using Java and BANK Bs application is built using .NET. BANK A will convert its data into messages and send it to BANK B using message providers like MQ Series of IBM. Both BANK A and BANK B will have MQ (Message Queue) associated with it. BANK A will put the message in its MQ. Message provider will pick message from BANK As MQ and drop it into BANK Bs MQ. BANK B will fetch the message and interpret it.
Many third party vendors are providing middleware technologies to take care of Java and .NET integration. Few such tools are J-Integra and JNBridgePro.
to our mailing list and receive new articles Note
: We never rent, trade, or sell my email lists to Visit
.NET Programming Tutorial Homepage ______________________________________________________
to our mailing list and receive new articles
: We never rent, trade, or sell my email lists to
Visit .NET Programming Tutorial Homepage
| All about Conceptual Analysis on .NET Remoting | Building desktop applications in .Net | Building Distributed Applications Efficiently Using .Net Remoting | C# (C Sharp) Unified Type System: Reference Types | C# (C Sharp) Unified Type System: Value Types | Data access in .Net | Delegates Vs Interfaces in C# (C Sharp) | How is Integration between Java and .NET Achieved | How is Versioning Achieved in C# (C Sharp) | Implementing Authorization and authentication in ASP.net | Implementing design patterns in .Net | List of Query Keywords in C# (C Sharp) |