|
This topic tells you how to create a URIMAP definition which specifies the components of the URI for an HTTP client request (scheme, host and path), and an SSL client certificate to be used with the request, if required. A URIMAP definition can be named on the WEB OPEN command, to provide a scheme and host name and a default path for the connection. It can also be named on a WEB SEND command, to provide a path for the relevant request. Alternatively, you can use the WEB EXTRACT URIMAP command to extract information from the URIMAP definition and use it directly in the application program that makes the HTTP client request.
| 1. | Identify the URL that you plan to use for the HTTP client request . The URL represents a resource that you plan to access on a server. |
| 2. | Identify whether a client certificate might be required for the request, and obtain a suitable certificate label. If the scheme used for the request is HTTPS (HTTP with SSL), the server might request a SSL client certificate. If this happens, XCICS supplies the certificate label that is specified in the URIMAP definition. |
| 3. | Divide the URL for the request into its scheme, host and path components. |
| 4. | Begin a URIMAP definition with a name, with the "define urimap" statement in the XCICS configuration file. |
| 5. | Use the "enabled" attribute to specify whether the URIMAP definition should be installed in an enabled or disabled state. |
| 6. | Specify a "usage" attribute of "client" (XCICS as an HTTP client). |
| 7. | Specify the "scheme" attribute as the scheme component of the URL for the request. HTTP (without SSL) or HTTPS (with SSL) can be used. Do not include the delimiters :// following the scheme component. |
| 8. | Specify the "host" attribute as the host component of the URL for the request. Include the port number (prefixed by a colon) if it has been specified explicitly in the URL. |
| 9. | Specify the "path" attribute as the path component of the URL for the request. A wildcard (asterisk) cannot be used in a URIMAP definition for XCICS as an HTTP client. |
| 10. | Optional: If SSL is being used, specify the CERTIFICATE attribute as the label of the certificate that is to be used as the SSL client certificate for this request. |
| 11. | Optional: If SSL or TLS is being used, specify the CIPHERS attribute as the cipher code that is to be used for this request. |
|
