Evaluate Weigh the pros and cons of technologies, products and projects you are considering.

Architectural guidelines to consider when categorizing an enterprise app

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

Standardizing business integration with JBI Integration technologies are expensive and often tie you into a proprietary solution. Additionally, customers often have to rely on more than one vendor to meet their integration needs. Ron Ten-Hove's group at Sun Microsystems was working on a service-oriented integration product when they realized that the industry needed something more than just another integration product: It needed a standard.

The Java Business Integration (JBI) specification aims to eliminate vendor lock-in by providing a standard container in which components from multiple vendors and various integration technologies can interact. In this interview, Ten-Hove, who is specification lead for JBI, takes a closer look at JBI and describes a typical JBI implementation using a purchase order example.

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

You will be able to add details on the next page.

Start the conversation

Send me notifications when other members comment.

Please create a username to comment.