Resource definition for XCICS Web support

You need to create some additional resource definitions for each XCICS Web support task that you want to perform. "Planning the architecture for XCICS as HTTP server " has planning guidance that specifies the resource definitions which you need for each task. The resource definitions that you might need to set up are as follows:

•

Create a TCPIPSERVICE resource definition to define each port that you use to receive inbound HTTP requests for XCICS Web support. This resource definition is the place where you specify the security measures that are applied for each port, along with technical information on the operation of the port. "Creating TCPIPSERVICE resource" tells you how to do this.

•	Optional: Create TRANSACTION resource definitions for any alias transactions that you want to use for inbound HTTP request processing. "Creating TRANSACTION resource definitions" tells you how to do this.

•	Create a URIMAP resource definition to provide processing information for each HTTP request for XCICS as an HTTP server, and for each HTTP request made from XCICS as an HTTP client.

1.	For all HTTP requests to XCICS as an HTTP server, start the definition following the steps in "Starting a URIMAP resource definition for any requests for XCICS as an HTTP server".

2.	For HTTP requests where an application-generated response is provided, follow the steps in "Completing a URIMAP definition for an application response to an HTTP requestfor XCICS as an HTTP server".

1.	For HTTP requests where a static response is provided, follow the steps in "Completing a URIMAP definition for a static response to an HTTP request for XCICS as an HTTP server".

1.	For HTTP requests made from XCICS as an HTTP client, follow the steps in "Creating a URIMAP definition for an HTTP request by XCICS as an HTTP client".

•	If you need to create URIMAP resource definitions for use by XCICS as an HTTP client, follow the steps in "Creating a URIMAP definition for an HTTP request by XCICS as an HTTP client".