Win a copy of Design for the Mind this week in the Design forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Integrating Web Based Enterprise System.

 
Muhammad Sarwar
Greenhorn
Posts: 20
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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.
 
Ilja Preuss
author
Sheriff
Posts: 14112
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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?
 
Muhammad Sarwar
Greenhorn
Posts: 20
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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
 
Lasse Koskela
author
Sheriff
Posts: 11962
5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Have you looked into portal products?
 
Stan James
(instanceof Sidekick)
Ranch Hand
Posts: 8791
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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!
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic