Replacing analyzer programs with URIMAP definitions
You can replace the request processing functions of your analyzer program with URIMAP resource definitions, which can be changed and controlled by using CICS® system programming commands.
URIMAP definitions can be used to match the URLs of requests and map them to application programs, and specify a converter program, alias transaction, and user ID. If your analyzer program provides extra functions, you can continue to use it instead of a URIMAP definition, or you can combine it with a URIMAP definition.
- You can introduce URIMAP resource definitions progressively for a few requests at a time. Depending on the type of processing carried out by your analyzer program, and the type of application that handles the request, you can choose whether to continue by using the analyzer program in the processing path for each request.
- You might prefer to select and publish new URLs for requests that are handled by URIMAP resource definitions, rather than retaining your existing URLs. When you are ready to discontinue the use of the old processing path for a request, you can set up a URIMAP definition to permanently redirect requests from the old URL to the new URL.
- Ensure that your analyzer program still contains basic handling procedures for unrecognized requests, even if it is no longer involved in the processing path for any requests. The analyzer program is still required on the TCPIPSERVICE definition, and receives requests in situations such as the user incorrectly typing a URL.
Using URIMAP definitions (without an analyzer program) qualifies requests for the direct attach route where CWBA or its transaction is attached directly by the socket listener task to process this request. This option reduces the CPU time that is required to process requests. For more information, see Bypassing the web attach task with the CSOL socket listener task.