Introduction: Application servers

 

+

Search Tips   |   Advanced Search

 

An appserver is a JVM that is running user applications. The appserver collaborates with the Web server to return a dynamic, customized response to a client request. Application code, including...

...runs in an appserver.

Conforming to the J2EE component architecture, servlets and JSP files run in a Web container, and enterprise beans run in an EJB container.

You can define multiple appservers, each running its own JVM.

  1. Configure transport chains to provide networking services to such functions as the service integration bus component of...

  2. Add an interface to an appserver to define a hook point that runs when the server starts and shuts down.

  3. Define command-line information that passes to a server when it starts or initializes.

  4. Tuning appservers

  5. Enhance the performance of the appserver JVM.

  6. Use an ORB for RMI/IIOP communication.

 

Asynchronous messaging

WAS supports asynchronous messaging based on the JMS of a JMS provider that conforms to the JMS specification v1.1.

The JMS functions of the default message service in WAS are served by one or more messaging engines (in a service integration bus) that runs within appservers.

In a deployment manager cell, there can be WAS v5 nodes. If a v5 node is configured to use V5 default messaging (the v5 embedded messaging), there can be at most one JMS server on that node.

 

Generic Servers

A generic server is a server that is managed in the WebSphere administrative domain, although it is not a server that is supplied by the WAS product. The generic server can be any server or process that is necessary to support the Application Server environment.

 

Related concepts

Introduction: Application servers

 

Related tasks

Creating generic servers
Programming to use JMS and messaging directly
Administering appservers
Configure transport chains
Creating custom services
Tuning appservers
Manage Object Request Brokers