Planning the architecture for XCICS as HTTP server

The XCICS Web support architecture for XCICS as an HTTP server varies depending on the tasks you want it to perform. Some configurable components of XCICS Web Support are required for all tasks, such as the TCPIPSERVICE definitions for the ports that receive inbound requests. Other configurable components are only required for specific tasks.

•	You can serve dynamic, application-generated responses to HTTP requests, using a specially designed Web-aware XCICS application program. "Providing dynamic HTTP responses with Web-aware application programs" tells you how to do this.

•	You can serve static responses to HTTP requests, using documents or files that are available to XCICS. "Providing static HTTP responses with a XCICS document template or flat file" tells you how to do this.

•	You can enable a Web client using HTTP to access an existing COMMAREA application in XCICS. "Giving Web clients access to COMMAREA applications" tells you how to do this.

•	You can receive non-HTTP requests from a client and provide an application-generated response. "XCICS Web support and non-HTTP requests" tells you how to do this.