I would like to categorize an existing enterprise insurance agency application built on J2EE, running on WebSphere 5.1. Are there any architectural guidelines I need to consider?
I would like to know details regarding the architecture to adopt considering the following:
1. The services that need to be identified.
2. The communication between this services.
3. Will the signature of each service be unique?
4. What will be the communication channel between the various services?
5. Is there an industry standard to adopt?
6. Is there an industry suggested practice for error handling in services?
Could you please provide information on these topics.
The scope of this question is a bit large for this type of forum, but I'll give it a quick pass.
1. Factor the application into business functions. A service should reflect a business task.
2. For communication within a J2EE application, I recommend communicating using RMI. But all services should also be exposed as Web services to enable integration with other applications. Web services communicate using SOAP.
3. Each Web service should have a unique signature.
4. SOAP over HTTP or HTTP/S
5. SOAP/WSDL/UDDI and WS-I Basic Profile
6. I'm not aware of any defined industry best practices for error handling beyond what's defined in the WS-I Basic Profile.
Dig Deeper on Topics Archive
Related Q&A from Anne Thomas Manes
Anne Thomas Manes explains the differences between open source clients and open source implementations. Continue Reading
Anne Thomas Manes discusses the best way to go about creating an enterprise data dictionary and why the systems works well. Continue Reading
Anne Thomas Manes explains the difference between 'hard' real time and 'live' real time systems. Continue Reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.