Processing HTTP Requests in AS Java 
All HTTP requests go to the Internet Communication Manager (ICM). If the ICM decides that the request has to be processed in AS Java, the Java handler forwards the request across a Fast Channel Architecture (FCA) connection (based on memory pipes) to the relevant server process in AS Java, as follows: The ICM puts the request in the HTTP request queue, which is processed by the HTTP worker threads of the Java server process. As soon as an HTTP worker thread is free, it takes a request from the queue and processes it. It also forwards the request to the relevant containers. If necessary, the worker thread then updates the status of the session.
Prerequisites
The Java Server process must have status RUNNING. Then the HTTP service and the Web applications are running in AS Java, and the server process participates in AS Java load balancing.
Caution
If AS Java does not yet have this status, the ICM will not forward the request to AS Java. The client then gets an error message.
Process
The following graphic describes the entire process, from the sending of a HTTP request from a Web client, to receipt of the response by the client. It focuses on how the request is processed in the AS Java.
HTTP Requests in AS Java
Processing involves the following steps:
HTTP worker threads wait for new requests in the HTTP request queue. If a request is in the queue, a free worker thread starts processing it.
The HTTP worker thread reads the request data from the FCA connection (based on memory pipes and MPI buffer).
The HTTP worker thread forwards the request to the associated container of the Java server process: Web container, EJB container, persistence layer, and so on.
The response is written to the FCA connection.
If the status of the session changes, the session table is updated in the shared memory (Web and EJB session).
Once the HTTP has been processed, the HTTP worker thread frees up the FCA connection and waits for new requests.