URIMAP: related resources

The attributes and values you specify for a URIMAP resource must be consistent with those specified on other resources.

However, CICS® does not check consistency of all related resources when the URIMAP definition is installed, and therefore does not report most inconsistencies at install time. The exception is the check described in Installing URIMAP resource definitions.
  • In URIMAP definitions for CICS as an HTTP server and web services, the TCPIPSERVICE attribute specifies the name of a TCPIPSERVICE resource definition that defines an inbound port to which this URIMAP definition relates. The attribute is optional, and if it is not specified, the URIMAP definition applies to any inbound request on all TCPIPSERVICE definitions. If the TCPIPSERVICE attribute is specified:
    • The selected TCPIPSERVICE resource definition must specify PROTOCOL(HTTP).
    • If SSL(YES) or SSL(CLIENTAUTH) is specified in the TCPIPSERVICE resource definition, the SCHEME attribute of the URIMAP definition must be HTTPS. When a URIMAP definition with HTTPS as the scheme matches a request that a Web client is making, CICS checks that the inbound port used by the request is using SSL. If SSL is not specified for the port, the request is rejected with a 403 (Forbidden) status code.
    You must install the selected TCPIPSERVICE definition before the URIMAP definition can be used.
  • In URIMAP definitions for CICS as an HTTP server where a static response is to be provided, the TEMPLATENAME attribute specifies the 1-48 character name of a CICS document template that will form the static response. The document template must be defined using a DOCTEMPLATE resource definition, and the TEMPLATENAME attribute of that definition specifies the name that is used in the URIMAP definition. The DOCTEMPLATE resource definition must be available before the URIMAP definition can be used.


dfha4_related.html | Timestamp icon Last updated: Monday, 5 June 2017