Introduction: Application servers
An application server is a JVM that is running user applications. The application server collaborates with the Web server to return a dynamic, customized response to a client request. Application code, including...
...runs in an application server.
Conforming to the J2EE component architecture...
You can define multiple application servers, each running its own JVM.
Additional configuration options include...
- Configure transport chains to provide networking services to functions such as...
- Plug into an application server to define a hook point that runs when the server starts and shuts down.
- Define command-line information that passes to a server when it starts or initializes.
- Tuning application servers
- Enhance the performance of the application server JVM.
- Use an Object Request Broker for RMI/IIOP communication.
The product supports asynchronous messaging based on the Java Message Service (JMS) of a JMS provider that conforms to the JMS specification version 1.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 application servers.
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.
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 TasksCreating generic servers
Programming to use JMS and messaging directly
Administering application servers
Configuring transport chains
Tuning application servers
Manage Object Request Brokers
WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.
IBM is a trademark of the IBM Corporation in the United States, other countries, or both.