Red Hat CERTIFICATE SYSTEM 7.3 - ADMINISTRATION, Administration Manual

Page: 97 / 554

Using Java Servlets
75
SELINUXTYPE=targeted
###########################################
NOTE
All of the instances run in un-confined mode with no security-enhanced policies in effect
for the server.
3.8. Using Java Servlets
Each subsystem Java
™
servlet supports a parameter called
xml
, which can have a value of either
true
or
false
. This parameter sets what kind of data the servlet returns; by default all of the
subsystem interfaces, like the agent services page or the end-entities page, returns data in HTML.
Setting the
xml
with a value of
true
returns XML data. This XML information is useful for writing
scripts that interact with the server.
The
xml
parameter is appended to the end of the interface link. For example, the server returns an
HTML page when the following link is accessed:
https://server.example.com:9443/ca/ee/ca/displayBySerial?op=displayBySerial&serialNumber=0x1
Appending
xml=true
to the end of the link returns the same page in XML:
https://server.example.com:9443/ca/ee/ca/displayBySerial?
op=displayBySerial&serialNumber=0x1
&xml=true
3.9. Logs
This section explains how to use the Console to configure logs maintained by the Certificate System
instance and how to view log contents.
This section contains the following subsections:
•
Section 3.9.1, “About Logs”
•
Section 3.9.2, “Services That Are Logged”
•
Section 3.9.3, “Log Levels (Message Categories)”
•
Section 3.9.4, “Buffered Versus Unbuffered Logging”
•
Section 3.9.5, “Log File Rotation”
•
Section 3.9.6, “Configuring Logs in the Console”
•
Section 3.9.7, “Configuring Logs in the CS.cfg File”
•
Section 3.9.8, “Configuring TPS Logs”
•
Section 3.9.9, “Monitoring Logs”
•
Section 3.9.10, “Signing Log Files”