|
URIMAP resource definitions are used to define how HTTP requests are processed. For any HTTP request for XCICS as an HTTP server, start the URIMAP definition by specifying the components of the expected URL for the Web client's request (scheme, host and path) and other basic information.
The XCICS System Management Guide contains information about URIMAP resource definition attributes that you will use during this process.
| 1. | Identify the URL that you plan to receive as an HTTP request from a Web client. The URL represents a resource that you plan to make available to a Web client through XCICS. |
| 2. | Divide the URL for the HTTP request into its scheme, host and path components. If you want the URIMAP definition to match more than one path, you can use an asterisk as a wildcard character at the end of the path. For example, specifying the path "/xcics/web/cics/*" would make the URIMAP definition match all requests whose path begins with the string "/xcics/web/cics/". If more than one wildcarded URIMAP definition matches an HTTP request, the most specific match is taken. |
| 3. | If a query component is present in the URL, and you want to match the URIMAP definition to that specific query alone, you can include this as part of the PATH specification. A query string can be used after a path that includes an asterisk as a wildcard, but the query string cannot itself include an asterisk as a wildcard. The complete and exact query string must be specified. For a static response with a XCICS document template, a query string can either be used to select the URIMAP definition, or it can be substituted into the document template, but not both. If you do not include a query string in the URIMAP definition, matching takes place only on the path, and any query string that is present in the request is automatically ignored for matching purposes. |
| 4. | Begin a URIMAP definition with a name. |
| 5. | Use the "enabled" attribute to specify whether the URIMAP definition should be in an enabled or disabled state. |
| 6. | Specify a "usage" attribute of "server" (XCICS as an HTTP server). |
| 7. | Specify the "scheme" attribute as the scheme component of the URL for the HTTP request: "http" or "https". |
| 8. | Specify the "tcpipservice" attribute as the name of the TCPIPSERVICE definition that defines the inbound port to which this URIMAP definition relates. If this attribute is not specified, the URIMAP definition applies to a matching HTTP request on any inbound port. |
| 9. | If you need to distinguish between URLs containing different host names, specify the "host" attribute as the host component of the URL for the HTTP request. Do not include a port number. An IPv4 address can be used as a host name, but IPv6 addresses are not supported. If you specify a single asterisk as the host attribute, the URIMAP definition matches any host name on incoming URLs. Use this option if you are not using multiple host names, or if you do not want to distinguish them. |
| 10. | Specify the "path" attribute as the path component of the URL for the HTTP request, including an asterisk as a wildcard character if required. You can either include or omit the delimiter / (forward slash) at the beginning of the path component; if you omit it, XCICS automatically provides it. If a query component is present, and you want to apply the URIMAP definition to that specific query alone, include this as part of the path component (including the question mark at the beginning of the string).
Note: Specifying the path attribute as /* makes the URIMAP definition match all requests directed to the host named in the host attribute, unless more specific URIMAP definitions are also installed, in which case the most specific match is taken. |
| 11. | Now complete your definition: |
|
