Red Hat CERTIFICATE SYSTEM 8 - DEPLOYMENT, Install Manual

Page: 121 / 132

Finding the Subsystem Web Services Pages
111
are started before any of the subsystem instances. Likewise, processes with a low number for their
shutdown priority are shut down first, so the subsystem processes are stopped before the processes
they depend on are stopped.
Server Process Name Start Priority Shutdown Priority
Administration Server dirsrv-admin 21 79
Directory Server dirsrv 21 79
Tomcat Server tomcat5 80 20
CA pki-ca 81 19
DRM pki-kra 82 18
OCSP pki-ocsp 83 17
TKS pki-tks 84 16
Apache httpd 85 15
RA 86 14
TPS pki-tps 87 13
Table 9.1. Certificate System Processes and Their chkconfig Start Priority
9.4. Finding the Subsystem Web Services Pages
The CA, RA, DRM, OCSP, TKS, and TPS subsystems have web services pages for agents, as well
as potentially regular users and administrators. These web services can be accessed by opening the
URL to the subsystem host over the subsystem's secure end user's port. For example, for the CA:
https://server.example.com:9444/ca/services
TIP
To get a complete list of all of the interfaces, URLs, and ports for a subsystem, check the
service's status:
service instance-name status
The main web services page for each subsystem has a list of available services pages; these are
summarized in
Table 9.2, “Default Web Services Pages”
. To access any service specifically, access
the appropriate port and append the appropriate directory to the URL. For example, to access the CA's
end entities (regular users) web services:
http s ://server.example.com: 9444/ca/ee/ca/
If DNS is properly configured, then an IPv4 or IPv6 address can be used to connect to the services
pages. For example:
https://1.2.3.4:9444/ca/services
https://[00:00:00:00:123:456:789:00:]:9444/ca/services