If you created a plain Atom service or category document
with the root element <app:service> or <app:categories>, set
up a URIMAP resource definition to deliver the document as a static
response through CICS web support.
Procedure
- Complete the steps for planning to deliver a z/OS® UNIX
file as a static response, as described in Providing static HTTP responses with a CICS document template or z/OS UNIX file.
- Complete the steps for setting up a URIMAP definition for
a z/OS UNIX file as a static response,
as described in Specifying common URIMAP attributes for CICS as an HTTP server and Specifying URIMAP attributes for a static response to HTTP requests.
When you are following
these steps, make these choices in the URIMAP definition for your
Atom service or category document:
- Specify the PATH attribute as a suitable URL for the
service or category document, such as /servicedocument.
The path for an Atom service or category document must not begin
with the common part of the path component for any of the Atom feeds
and collections that you serve using the host name that you specified.
- Remember to specify a USAGE attribute of SERVER (CICS
as an HTTP server), not ATOM.
- Specify the MEDIATYPE attribute as application/atomsvc+xml
for an Atom service document, or application/atomcat+xml for
an Atom category document.
- Specify the HFSFILE attribute as the name of the z/OS UNIX file
that contains your service or category document.