The Quality of Service Requirements

The logical architecture identifies the Java ES components that provide the services described in the use cases, but does not tell you how to install the components on your network. In a typical production solution, quality of service requirements such as response time, service availability, and service reliability are satisfied by installing and configuring multiple instances of the components and distributing the instances among several computer systems. For example, installing two instances of Messaging Server on two different computer systems and configuring them together with load balancing hardware will provide fail-over capability and high availability for your messaging services.

To determine the quality of service requirements for a solution, you analyze your business needs and develop a set of requirements. The quality of service requirements are based on important characteristics of your business needs, such as the number of users that must be supported, the response time that your users must experience, and the amount of down time that is permitted.

The evaluation solution described in this document only needs to support a handful of users, and there is no need for continuous availability or the other features of a production solution. Therefore, the system requirements for the evaluation solution are minimal. These requirements are listed below:

• Load and performance requirements: None

• Availability requirements: None

• Security requirements: LDAP authentication, single sign-on

• Serviceability requirements: None

• Scalability requirements: None