System information

After installing the JDK, run /usr/sbin/alternatives --config javac as root to insure that
a JDK is available.
Solaris 9 systems do not require downloading and installing a JDK; however, it may be required to
download and install the Sun JDK 5.0 package in order to obtain a compatible Sun JRE 5.0 package.
5.4. TPS Subsystem Considerations
•
TPS subsystems installed on a Red Hat Enterprise Linux system require a local installation of the
Apache 2.0.x web server. If the installation is made on a newly-installed Red Hat Enterprise Linux
AS or ES system, rather than an upgraded system, and Everything was selected during the
Anaconda installation process, an Apache server should already be present.
When installing the TPS subsystem on Solaris 9, a specially-configured Apache server is included
as part of the Certificate System 7.2 packages.
•
The TPS subsystem cannot be cloned.
5.5. Directory Server Information
All subsystems require access to Red Hat Directory Server 7.1 on either the local machine (if it is also
a 32-bit Red Hat Enterprise Linux platform) or a remote machine (acceptable platforms are 32-bit Red
Hat Enterprise Linux 4, 32-bit Solaris 9 for SPARC, or 64-bit Solaris 9 for SPARC).
5.6. Source RPMs
Since Red Hat Certificate System 7.2 is not an open-source product, source RPMs are only available
for third-party packages.
NOTE
Several of these third-party packages may issue warnings when they are installed be-
cause they may contain the UID or GUID of their original packager.
5.7. New File Locations and Subsystem URIs
The subsystem files in Certificate System 7.2 are in different locations than in Certificate System 7.1.
The old and new locations are listed in Table 3, “Certificate System 7.1 and 7.2 File Locations”. These
are explained in more detail in chapter 3, "Administrative Basics," in the Certificate System Adminis-
trator's Guide.
File 7.1 Location 7.2 Location
Subsystem start and stop
scripts
/opt/redhat-cs/cert-in-
stance_ID
/etc/init.d/instance_ID
Release Notes
10