May 02, 2007
.NET and Java: Can They Co-exist?Building a fully integrated SOA environmentJonathan Erickson
How one company used cross-platform .NET to solve its .NET/Java EE interoperability challenges
DDJ: With us today is Alex Libis, Information and Data Security Manager of Opal Future Technologies. Alex, can you share with us a brief overview of Opal, particularly in terms of platforms and related issues?
Our primary responsibility was to support eight separate legacy systems, which are running on a variety of systems ranging from Mainframe, UNIX/AIX, AS400 to Microsoft servers, and using various Databse systems including DB2, Informix, SQL400 and SQL server.
To reduce operating costs and eliminate redundant support services, the government tasked us with consolidating the eight pension funds' information management systems -- including customer relationship management, data mining, investments management, help desk, suppliers' management and a few dozen other services -- into unified system services, together with a central pension fund calculation engine and more than 30 terabytes of data.
DDJ: What kind of challenges did you face in implementing the system?
Once we made the decision to go with WebSphere Portal 6, we had less than four months to complete Phase 1, which was to deliver an intranet site that enables pension fund managers to administer the funds using a uniform set of applications.
The main challenge we faced is that several of our support applications are written in .NET, and we have limited access to in-house Java developers. We looked into rewriting the .NET applications in Java, but the process was too time-consuming. It took our Java developers two weeks to rewrite a sample .NET application in Java. At this rate, we figured we'd need about 18 months to integrate our .NET services.
DDJ: How did you tackle these challenges?
For the proof of concept, we chose our largest and most logically complex .NET application. Within three days, our .NET developers integrated the application natively into the Portal and were able to extend WebSphere Portal's role-based personalized interfaces, single sign-on, unified navigation, inter-portlet communications, and other portal services to the .NET applications.
We were very happy with these results, and we purchased Mainsoft's Portal Edition to deploy the remaining .NET applications on the portal.
Today, we have Java developers and .NET developers working side by side in the Portal environment. Both groups can access the same Java classes/JSF objects to deliver Java deployments. Most importantly, Mainsoft's Portal Edition has given us the flexibility to rapidly design and implement the system without worrying about the language in which the components are written.
DDJ: How did it all turn out?
We're well on our way to completing the next phase, which will incorporate 15 additional .NET applications and give accountholders online access to their account information.
DDJ: Is there a web site that you can direct readers to for more information?
|
|
|||||||||||||||||
|
|
|
|