Application Server

Application Server is primarily used to provide web container services for other Java ES components. If your solution uses Application Server for web container support, an instance of Application Server must be installed on each computer that runs an instance of a supported components.

For example, if your solution uses Application Server to provide web container support for Communications Express, then every computer with an instance of Communications Express also has an instance of Application Server. Every instance of Communications Express is deployed to the instance of Application Server on the same computer.

The Java ES installer can both install and deploy some components, such as Access Manager. For other components, such as Communications Express, installation is followed by a separate configuration step. For these components, a configuration wizard creates an instance and deploys it. The sections on the individual components explain what is required for each component.

Instances of different components can be deployed to one instance Application Server. For example, if your solution runs Access Manager and Portal Server on one computer, both components can be deployed to the same Application Server instance.

Application Server has no system-level dependencies.

Application Server has several local dependencies. An instance of Application Server always requires a local instance of Message Queue. If your solution uses Web Server to load-balance multiple instances of Application Server, a Web Server instance must be installed locally. And, if your solution uses the High Availability Session Store feature, an instance of this component must be installed locally.

Basic Installation Procedures for Application Server

The basic procedures for installing and configuring Application Server are as follows:

1. Use the Java ES installer to install and configure Application Server on the computer systems specified in your deployment architecture. When you install Application Server, you specify configuration values. In some cases (Access Manager and Portal Server), you also specify configuration values for the supported component, and the supported component is deployed to the Application Server instance. In other cases, you separately run the supported component's configuration wizard to create and deploy an instance.

2. Start and verify all of the Application Server instances.

3. Verify that the supported components are running.

4. If your solution uses load balancing, verify that the load balancing is routing requests among the Application Server instances.

Choosing Configuration Values for Application Server

For each Application Server instance in your solution, you must input values that configure the instance to interoperate with the other components in the solution. For information on choosing configuration values, see Application Server Configuration Information in Sun Java Enterprise System 2005Q4 Installation Reference

Adding Procedures for Application Server to Your Installation Plan

Insert instructions for installing Application Server anywhere some other Java ES component uses Application Server for web container support.

To add installation and configuration instructions for Application Server, do the following:

1. The section on the supported component tells you to add to your installation plan an instruction to run the installer and select both the supported component and Application Server.

2. Add an instruction to also select Message Queue, and if used in your solution, High Availability Session Store, and Web Server.

3. Next, list the configuration values for Application Server.

4. If the supported component is configured and deployed by the installer (Access Manager, and Portal Server), do the following:

   1. Add to your plan the configuration values for the supported component.

   2. Add an instruction to run the installer and supply configuration values for Application Server, Application Server's local dependencies, and the supported component.

   3. Add an instruction to start the Application Server instance. This step also starts the supported component.

   4. As described in the section on the supported component, verify that the supported component is running correctly.

5. If the supported component is not configured and deployed by the installer (Communications ExpressDelegated AdministratorInstant Messaging), do the following:

   1. Add an instruction to run the installer and supply configuration values for Application Server and Application Server's local dependencies.

   2. Add an instruction to list the configuration values for the supported component.

   3. Add an instruction to run the supported component's configuration wizard and supply the configuration values for the supported component.

   4. Add an instruction to start the Application Server instance. This step also starts the supported component.

   5. As described in the section on the supported component, verify that the supported component is running correctly.

6. If the Application Serverinstances are load balanced, add an instruction to verify operation of the load balancer.