HTTP requests are processed by directly attached user transactions
The socket listener task CSOL is optimized to directly attach user transactions for fast arriving HTTP requests. This means the web attach task is bypassed, therefore reducing the CPU time that is required to process each request.
To qualify for optimization, the TCPIPService and URIMAP resource attributes and the request must meet all the criteria, so ensure that your requests are fully configured by selecting all the resource attributes that are marked Required as shown in Table 1.
| TCPIPService | URIMAP | HTTP REQUEST | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ROUTES | PROTOCOL (HTTP) | PROTOCOL (USER) | SSL
|
SSL
|
ANALYZER (NO) | ANALYZER (YES) | USAGE
|
USAGE (CLIENT) | HEADER arrived | HEADER not arrived | URIMAP matched | URIMAP not matched |
| Direct | Required | - | Required | - | Required | - | Required | - | Required | - | Required | - |
| Indirect | - | X | - | X | - | X | - | X | - | X | - | X |
The socket listener task CSOL detects inbound TCP/IP connection requests on all ports that are defined to CICS®, and starts the CICS service that is associated with the port. When the port is intended for CICS web support that uses the protocol of HTTP and SSL support NO or ATTLSAWARE, CSOL looks in the available request data and assesses whether the request can be handled by a directly attached user transaction.
For example, if there is not enough header data already present for CSOL to determine the URI and the USER ID, or if there is no matching URIMAP found or enabled for the request, the request cannot be optimized and CSOL attaches the web attach task to process the request. If the matching URIMAP indicates that the request needs to go through the analyzer program (that is the URM attribute on TCPIPSERVICE), the request cannot be optimized, so CSOL attaches the web attach task to process it.
For the web service requests and atom feeds (that is URIMAP with usage of PIPELINE or ATOM) no analyzer is involved, so these requests would be optimized and be processed by the transactions CPIH or CW2A, providing that no SSL session is used. This mechanism is ready to adopt the direct route and gain performance enhancement, without any changes.
For HTTP server request, if the matching URIMAP indicates that an application-generated response is expected by the client and other criteria are also met, CSOL directly attaches the transaction CWBA that is defined in the URIMAP to process the request. The transaction's task receives the request data from the web client and processes it as usual.