URIMAP definitions are resource definitions that match the URIs
of HTTP or Web service requests, and provide information on how to process
the requests.
URIMAP definitions are used to provide three different Web-related facilities
in CICS®:
- Requests from a Web client, to CICS as an HTTP server. URIMAP definitions
for requests for CICS as an HTTP server have a USAGE attribute of SERVER.
These URIMAP definitions match the URLs of HTTP requests that CICS expects
to receive from a Web client, and they define how CICS should provide a response to each
request. You can use a URIMAP definition to tell CICS to:
- Provide a static response to the HTTP request, using a document
template or z/OS® UNIX System
Services HFS file.
- Provide a dynamic response to the HTTP request, using an application
program.
Planning your CICS Web support architecture for CICS as an HTTP server has
planning information for CICS as an HTTP server, and Resource definition for CICS Web support has
instructions for creating a URIMAP definition for these purposes.
- Requests to a server, from CICS as an HTTP client. URIMAP definitions
for requests from CICS as an HTTP client have a USAGE attribute of CLIENT.
These URIMAP definitions specify URLs that are used when a user application,
acting as a Web client, makes a request through CICS Web support to an HTTP server. Setting
up a URIMAP definition for this purpose means that you can avoid identifying
the URL in your application program. HTTP client requests from a CICS application has
instructions for creating a URIMAP definition for this purpose.
- Web service requests. URIMAP definitions for Web service requests
have a USAGE attribute of PIPELINE. These URIMAP definitions associate a URI
for an inbound Web service request (that is, a request by which a client invokes
a Web service in CICS) with a PIPELINE or WEBSERVICE resource that specifies
the processing to be performed. Web services - start here has
further information about Web services in CICS.
For CICS as
an HTTP server, URIMAP definitions incorporate most of the functions that
were previously provided by the analyzer program associated with the TCPIPSERVICE
definition. An analyzer program may still be involved in the processing path
if required.