|
You can use XCICS Web support to process inbound TCP/IP client requests which are not in the HTTP format. This facility is primarily intended to provide support for requests from user-written clients that use nonstandard request formats. The processing that takes place for requests, and the response that is provided, are defined by the user. No specific support is provided for any formally defined protocols which are used for client-server communication.
XCICS Web support only handles non-HTTP messages when XCICS is the server. Non-HTTP requests cannot be made by XCICS as a client. Client requests made through XCICS Web support use the HTTP protocol.
When XCICS Web support facilities are used for handling non-HTTP requests:
| • | You can use TCPIPSERVICE resource definitions to control the ports on which requests are received. |
| • | You can use an analyzer program to assemble and parse requests, specify code page conversion, and determine subsequent request processing. You can code the analyzer program to parse requests in accordance with any request format that you have defined, but note that this XCICS facility does not provide specific support for any particular protocol for which a formal definition exists. |
| • | You can use either Web-aware application programs, or non-Web-aware applications with a converter program, to provide responses to requests. Requests and responses can be handled using certain elements of the EXEC XCICS WEB programming interface, or passed between XCICS applications in a COMMAREA. |
Some XCICS Web support facilities are not available for non-HTTP requests:
| • | Some of the facilities that help you interpret HTTP requests and construct the responses are not available. For example, message headers cannot be accessed separately. |
| • | Persistent connections are not supported. |
| • | URIMAP definitions are not used for non-HTTP requests. |
|
