Web modules can dispatch requests concurrently on separate threads.
Requests can be dispatched by the server or client.
Before you begin
For additional information about the AsyncRequestDispatcherConfig
and the AsyncRequestDispatcher interfaces, review the com.ibm.websphere.webcontainer.async
package in the application programming interfaces (API) documentation. The
generated API documentation is available in the information center table of
contents from the path Reference > APIs - Application Programming Interfaces.
Review
the asynchronous request dispatcher application (ARD) design considerations
topic before completing the following steps.
About this task
Concurrent dispatching can improve servlet response time. If operations
are dependant on each other, do not enable asynchronous request dispatching,
therefore, select Disabled. Concurrent dispatching might result in errors
when operations are dependant. Select Server side to enable the server to
aggregate requests dispatched concurrently. Select Client side to enable the
client to aggregate requests dispatched concurrently.
Procedure
- Logically separate resource intensive operations.
- Develop servlets that use an asynchronous request dispatcher to
include these operations.
- Enable asynchronous request dispatching on an application server.
- Deploy the application in an application server that has asynchronous
request dispatching enabled.
- Select an aggregation type for the application that needs ARD.
- Optional: Configure the AsyncRequestDispatcherWorkManager
work manager that is used for the request dispatch threads.
- Restart the application server.
What to do next
Restart the modified applications if already installed or start newly
installed applications to enable ARD on each application.