Start the application debugging profile manager by typing its URL in your Web browser. The URL that you enter will depend upon how CICS® Web support is configured. Your system administrator will tell you the URL to use for your system. CICS displays the "List all profiles" page.
For example, if your Web browser connects directly to CICS, and your system is configured to use the sample analyzer program DFHWBADX, the URL is
http://mvs_address:port/CICS/CWBA/dfhdpwb
If URIMAP definitions are being used to manage requests, the
URL is as defined in the URIMAP definition that references program DFHDPWB.
To provide access to the Web interface, you can use either an analyzer program, or URIMAP definitions, as part of your CICS Web support architecture. The CICS Internet Guide explains the architecture elements that are used to give Web clients access to CICS applications.
Only one URL is required. The user accesses different pages by selecting interface elements on the pages that the program provides, beginning with the "List all profiles" page.
If the sample analyzer program DFHWBADX, or an analyzer program with similar function, is used to handle requests for the application debugging profile manager, the path component of the URL gives CICS the information it needs to run the program. The path /CICS/CWBA/dfhdpwb tells the analyzer that:
If URIMAP definitions are used to handle requests for the application debugging profile manager, you need to set up two URIMAP definitions:
The second URIMAP definition is required because when a graphic is wanted, the HTML pages for the Web interface use the tag img src=, so that the Web browser makes a request for the graphic and then displays what it receives. The img src= tag specifies the name of the graphics program, and the Web browser makes the request using the path component of the URL that was originally used to start the Web interface, followed by the name of the graphics program. A URIMAP definition is needed to map this new request to the graphics program.
The following sample URIMAP definitions could be used to provide access to DFHDPWB and DFHADWB1:
For DFHDPWB:
URIMAP: ADPM - URIMAP name
GROUP: MYGROUP - any suitable
USAGE: SERVER - For inbound requests
SCHEME: HTTP - Or use HTTPS for SSL
HOST: * - * matches any host name
PATH: /cicsapps/adpm/* - Any path can be used, with final asterisk
TCPIPSERVICE: - If blank, applies to all ports
ANALYZER: NO - Means do not run analyzer
CONVERTER: CICS - Means no converter used
TRANSACTION: CWBA - Default transaction ID
PROGRAM: DFHDPWB - App debugging profile manager
For DFHADWB1:
URIMAP: ADWB1
GROUP: MYGROUP
USAGE: SERVER
SCHEME: HTTP
HOST: *
PATH: /cicsapps/adpm/dfhadwb1
[Same path as for DFHDPWB, but with dfhadwb1 appended]
TCPIPSERVICE:
ANALYZER: NO
CONVERTER: CICS
TRANSACTION: CWBA
PROGRAM: DFHADWB1 - Graphics program
When URIMAP definitions are used, the path specified in the URL does not need to have any relationship to the resource; the linkage between the path and the resource is made by the URIMAP definition. For the URIMAP that points to DFHDPWB, you could specify a path that includes a page element, such as /cicsapps/adpm/start.html. The name of the page element does not matter. Note that if you do this, when the Web browser makes a request for DFHADWB1, it omits the page element and appends dfhadwb1 in its place. If the path in the first of the sample URIMAP definitions was /cicsapps/adpm/start.html, the path in the second sample URIMAP definition would still be /cicsapps/adpm/dfhadwb1.
The CICS Internet Guide explains how to set up URIMAP definitions.