Specifying URIMAP attributes for a static response to HTTP requests

Some of the attributes specified in a URIMAP apply only when you use a CICS® document templates or a z/OS® UNIX file to provide a static response to HTTP requests.

Before you begin

If you are using path matching, make sure that you specify an asterisk character (*) when you specify the PATH attribute in the URIMAP resource.

About this task

The URIMAP resource has a number of attributes that you specify when you provide a static response to HTTP requests.

The URIMAP resource does not control security for CICS document templates and z/OS UNIX files delivered as static responses. For information about using basic authentication and resource level security to secure these items, see Security for CICS web support.

Procedure

  1. Specify the data content of the static response in the MEDIATYPE attribute.
    For example, specify text/html or text/xml for HTML and XML data content respectively. See IANA media types and character sets for more information about media types.
    This attribute is required, and there is no default value.
    CICS uses the information to create a Content-Type header for the response.
  2. If the MEDIATYPE attribute specifies a text type of data content, specify the following attributes which are required for code page conversion.
    1. Specify the target character set in the CHARACTERSET attribute.
      The target character set is the character set into which CICS converts the static response before sending it to the web client. CICS does not support all the character sets named by IANA. HTML coded character sets lists the IANA character sets that are supported by CICS.
      This information is included in the Content-Type header of the response.
    2. Specify the IBM code page (EBCDIC) in which the static document is encoded in the HOSTCODEPAGE attribute.
    For other types of content, there is no code page conversion.
  3. If you are using a CICS document template to provide the response, specify the name of the document template in the TEMPLATENAME attribute.
    The name you specify is the name of the DOCTEMPLATE resource that defines the attributes of the document template.
    If you want to use path matching, include an asterisk as a wildcard character at the end of the name of the CICS document template. CICS takes the portion of each HTTP request path that is covered by the wildcard character and substitutes it as the last part of the template name.
    URIMAP definition attributes has an example showing how path matching works.

    If a query string is present on the URL, CICS passes the content of the query string into the named CICS document template as a symbol list. CICS passes the content only when the query string has not already been used in the PATH attribute of the URIMAP definition.

  4. If you are using a z/OS UNIX file to form the static response, specify the name of the file in the HFSFILE attribute.

    You can specify the z/OS UNIX file as an absolute (fully qualified) path, or as a path relative to the HOME directory of the CICS region user ID. An absolute path begins with a slash character (/); an relative path does not.

    The CICS region user ID must have permissions to access z/OS UNIX, and the z/OS UNIX directory containing the file, and the file itself. For more information, see Giving CICS regions access to z/OS UNIX System Services and HFS directories .

    If you want to use path matching, include an asterisk as a wildcard character at the end of the path for the z/OS UNIX file. CICS takes the portion of each HTTP request path that is covered by the wildcard character, and substitutes it as the last part of the z/OS UNIX file path. You must explicitly specify at least one level of the directory structure; you cannot use an asterisk on its own in the HFSFILE attribute.

    URIMAP definition attributes has an example showing how path matching works.

    You cannot substitute a query string into a z/OS UNIX file.