How is Integration between Java and .NET AchievedJava 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 bank’s 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: • Ensure
that both Java and .NET applications are WS-I complaint. Only then web
services can be created Bridging: 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: • Create
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 Solution’s.
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. Messaging: 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 A’s
application is built using Java and BANK B’s 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 A’s
MQ and drop it into BANK B’s MQ. BANK B will fetch the message and
interpret it. Middleware
Technology: Many third
party vendors are providing middleware technologies to take care of Java
and .NET integration. Few such tools are J-Integra and JNBridgePro.
_______________________________________________________________________
FREE
Subscription
Subscribe
to our mailing list and receive new articles Note
: We never rent, trade, or sell my email lists to Visit
.NET Programming Tutorial Homepage ______________________________________________________ |
