URIMAP Config
A URIMAP in CICS maps a URI to a CICS resource, defining how HTTP requests are handled by routing them to the appropriate CICS transactions or programs. For example, the CICS 'WEB OPEN' command opens an HTTP connection. Once the connection is established, the requests can then be managed according to the URIMAP definitions.
To use a URIMAP (User Request Interface Map), create a file with the '.yaml' file extension and name it accordingly, for example "urimap.yaml". Then, open the file and add the following contents:
urimap: <URI ID>: uri: scheme: "http" host: "<server address>" port: "<server port>" path: "</>" securityAttributes: userid: "<name or id of user>" ciphers: "<encryption algorithm>" certificate: "ssl" authenticate: "yes" <URI ID>: uri: scheme: "http" host: "<server address>" port: "<server port>" path: "</>" securityAttributes: userid: "<name or id of user>" ciphers: "<encryption algorithm>" certificate: "ssl" authenticate: "yes"
Assign values to each property.
To make use of this URIMAP configuration, it needs to be loaded through the amt-config.yaml file.
- Open the amt-config.yaml file.
- Find the urimap property and add the filename within quotation marks. For example, urimap: "urimap.yaml"
URIMAP Property Descriptions
Property | Value | Description |
scheme | http, https, ftp | The protocol used to access the resource. |
host | Server Address | The domain name or IP address of the server hosting the resource |
port | Server Port | The network port number used to access the resource. |
path | </path/to/resource> | The path to the specific resource on the server. |
userid | Username or user ID | The username or identifier used for authentication to access the resource. |
ciphers | <security cipher> | The encryption algorithms or ciphers used to secure the connection to the resource. |
certificate | ssl, ... | The digital certificate used to establish the identity of the server and secure the connection. |
authenticate | yes, ... | The authentication method used to verify the identity of the user or client accessing the resource. |
Example file:
urimap: XXYY110A: uri: scheme: "http" host: "amtserver" port: "8080" path: "/path/to/resource" securityAttributes: userid: "johndoe" ciphers: "test" certificate: "ssl" authenticate: "yes" XXYY110B: uri: scheme: "http" host: "amtserver" port: "8080" path: "/path/to/resource" securityAttributes: userid: "johndoe" ciphers: "test" certificate: "ssl" authenticate: "yes"