Installing PowerSC on Linux systems
You must install a package for each specific function of PowerSC on the Linux® system that is to be monitored.
PowerSC is supported on both Power and Intel systems.
The arch variable in the package name indicates the target
architecture.
Note: For Red Hat Enterprise Linux Server packages, the
el8 variable refers to RHEL8, and el9
refers to RHEL9.
Note: The tar archiving utility is required for the installation.
The following packages are provided:
- powersc-pscxpert-2.2.0.latest
- The PowerSC Compliance package must be installed on Linux systems that require the Security and Compliance Automation feature of PowerSC .
- powersc-uiAgent-2.2.0.latest
- PowerSC GUI Agent package must be installed on Linux systems that will be managed using the PowerSC GUI. The package powersc-pscxpert-2.2.0.latest is required to install powersc-uiAgent-2.2.0.latest.
- powersc-uiServer-2.2.0.latest
- The PowerSC GUI Server package must be installed on the Linux system configured specifically for running the PowerSC GUI Server. You would only install this package if your PowerSC GUI server will reside on a server running a Linux operating system.
- psad-3.0-3.elversion.arch.rpm
- The PowerSC Port Scan Attack Detector (psad) packages
are located in the RPMS/ppc and
RPMS/x86 directories. The psad package must be
installed on Red Hat Enterprise Linux Server 8.3 or later or 9.x systems that require
the psad feature of PowerSC.This package has the following prerequisites:
- sendmail-cf
- mailx
- psad-3.0-3.sles15.arch.rpm
- The PowerSC Port Scan Attack Detector (psad) packages
are located in the RPMS/ppc and
RPMS/x86 directories. The psad package must be
installed on SUSE Linux Enterprise Server 15 and later systems that require the psad
feature of PowerSC.This package has the following prerequisites:
- sendmail-cf
- mailx
- fapolicyd-1.1.7-1.arch.rpm
- The PowerSC File Access Policy Daemon (fapolicyd) packages are located in the RPMS/ppc and RPMS/x86 directories. The fapolicyd package must be installed on SUSE Linux Enterprise Server 15 and later systems that require the fapolicyd feature of PowerSC.
- powersc-xerces-c-3.2.4-4.elversion.arch.rpm, powersc-xerces-c-3.2.4-4.sles15.arch.rpm
- The Xerces packages are located in the RPMS/ppc and
RPMS/x86 directories. Note: Xerces is a prerequisite for the powerscStd.ice package.
- clamav-data-0.103.11-1.elversion.noarch.rpm
- The ClamAV database packages are located in the RPMS directory. They are provided for Red Hat Enterprise Linux Server and SUSE Linux Enterprise Server installations that are not able to download the database due to network connectivity restrictions. SUSE Linux Enterprise Server systems should use the ClamAV el8 packages.
The PowerSC Compliance, PowerSC GUI Server and PowerSC GUI Agent packages are encapsulated in shell archives. The
following describes the naming convention of the shell
archives:
product-version-serverldistro.arch.sh
The following shell archives are available:
- powersc-pscxpert-2.2.0.latest-elversion.arch.sh
- Installs the PowerSC Compliance package on Red Hat Enterprise Linux (RHEL) platforms.
- powersc-pscxpert-2.2.0.latest-sles15.arch.sh
- Installs the PowerSC Compliance package on SUSE Linux Enterprise Server (SLES) platforms.
- powersc-uiAgent-2.2.0.latest-elversion.arch.sh
- Installs the PowerSC GUI Agent package on Red Hat Enterprise Linux (RHEL) platforms.
- powersc-uiAgent-2.2.0.latest-sles15.arch.sh
- Installs the PowerSC GUI Agent package on SUSE Linux Enterprise Server (SLES) platforms.
- powersc-uiServer-2.2.0.latest-elversion.arch.sh
- Installs the PowerSC GUI Server package on Red Hat Enterprise Linux (RHEL) platforms.
- powersc-uiServer-2.2.0.latest-sles15.arch.sh
- Installs the PowerSC GUI Server package on SUSE Linux Enterprise Server (SLES) platforms.
Note: You can use the .sh files to install the
PowerSC components in a new installation or when updating
from a previous version. However, you cannot use the .sh files to overwrite an existing installation
of the same version. If you need to overwrite an existing installation of the same version, first
uninstall the current installation and then reinstall.