This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Currenlty I m in a situation where I am suppose to provide an architecture for integrating the more then tow heterogenious system using J2EE technology.All the sub systems are suppose to run on different machines with their own database and web servers. Please suggest any pattern,architecture,protocol for such senario. All responses are appreciated.
What kind of integration are you speaking about? Do the subsystems need to speak to each other? Or do they only need to be integrated into a common user interface?
The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
Joined: Jan 02, 2003
There will be a common interface but the common interface will be using the busines interface of the integrated sub systems in order to get the required information from the sub systems and present it in its own way.This communication will the sort main system using the services provided by the sub systems. Keeping in mind that all sub systems and main system are java based Regards
Some of the common choices are web services (lowest common denominator) or a message-oriented-middleware bus. We have both going on somewhat competitively. WebMethods is a neat integration platform for web services, MQ-Series and MQSI work nicely for messaging. You also have to think about centralized or decentralized models. One group is trying to put WebMethods in front of many services - come to one server and one service organization for everything. Others pop up with their own SOAP servers and 3rd party servers. They are not perfectly interoperable so the client has to know quite a bit about who they're talking to. I talked with one well-known company that had an extremely large centralized hub with a goal of presenting the only public API for hundreds of services all over the planet, real time and batch. That kind of thing takes a huge commitment to reliability, avialability, scalability, performance, manpower and playing well with others. Don't go there without CIO mandates!
A good question is never answered. It is not a bolt to be tightened into place but a seed to be planted and to bear more seed toward the hope of greening the landscape of the idea. John Ciardi