Prepare to Install Performance Center

To ensure that your npc installation is successful, complete the requirements before you install npc:
capm360
HID_Prepare_to_Install_CAPC
To ensure that your
CA Performance Center
installation is successful, complete the requirements before you install
CA Performance Center
:
2
Verify the Prerequisites
  • The software can be installed in any filesystem to which the root user has write access. The default installation directory is /opt/CA/PerformanceCenter. The setup program lets you select another location.
  • Verify that Security Enhanced Linux (SELinux) is disabled on the server where you plan to install
    CA Performance Center
    . By default, some Linux distributions enable this feature, which does not allow the product to function properly.
    For information about configuring an SELinux security policy, see the Red Hat documentation.
  • By default, the MySQL database is installed to /opt/CA/MySql/, but you can select another location during the installation. Verify that the selected filesystem has enough allocated disk space to support a database.
  • To avoid database corruption, exclude the installation directory, and all its subdirectories, from antivirus scans. Prevent scanning by a local instance of an antivirus client and scanning by a remote antivirus instance. Exclude the following directories:
    • /opt/CA/MySql/
    • /opt/CA/MySql/bin
    • /opt/CA/MySql/data
    • /opt/CA/MySql/tmp
    • /opt/CA/PerformanceCenter
  • CA Performance Center
    requires DNS resolution. If DNS is not configured, add system entries to the /etc/hosts file on your server manually.
  • Verify that your /tmp location has at least 4 GB of space available.
  • The installer requires the zip and unzip packages. If these packages are not installed, use one of the following commands to install them:
    yum -y install zip unzip
    SLES:
    zypper install -y zip unzip
  • CA Performance Center
    requires the wget package. If this package is not installed, use one of the following commands to install it:
    yum -y install wget
    SLES:
    zypper install -y wget
  • Perl is required to run some of the available scripts.
Set the Limit on the Number of Open Files
Verify that the user account that is installing
CA Performance Center
has a value of at least 65536 on the number of open files. Set this value permanently.
For systems where a sudo user installs
CA Performance Center
, the installation user might not have the required permissions to complete this procedure. Work with the system administrator to configure the limit.
Follow these steps:
  1. Log in to the
    CA Performance Center
    host.
  2. Edit the following file:
    /etc/security/limits.conf
  3. Add the following lines to the file:
    # Added by Performance Center
    * soft nofile 65536
    # Added by Performance Center
    * hard nofile 65536
  4. Restart the login session.
  5. Verify that the number of open files is set properly:
    ulimit -n
    The command returns the limit that you have specified.
Verify Communication Ports
CA Performance Center
uses multiple ports to communicate with various components, particularly data sources. In addition, some of the products and components that integrate with
CA Performance Center
have specific port requirements. Consult the documentation of each data source for the list of required ports.
For any firewall that protects this server, open the required ports and protocols for the data sources you are deploying. The product documentation for each data source provides a list of required ports and protocols.
Each data source uses unique ports.
The following communication ports allow
CA Performance Center
services to communicate with
CA Performance Center
:
  • TCP 3306
    Enables communications to the MySQL database (inbound) from the
    CA Performance Center
    services.
  • TCP/HTTP 8481
    Enables communications between the Device Manager and Console services.
The following communication ports allow users to contact
CA Performance Center
:
  • TCP/HTTP 8181
    Enables communications between client computers and the
    CA Performance Center
    server. Enables console communications with data sources.
  • TCP/HTTP 8381
    Enables communications between client computers and the
    CA Performance Center
    server. Also enables login using the single sign-on authentication component.
The following communication ports allow other data sources to contact
CA Performance Center
for eventing and OpenAPI single sign-on:
  • TCP/HTTP 8281
    Enables communications between the Event Manager, which is installed automatically with the
    CA Performance Center
    software, and the data sources. The Data Aggregator initiates communication and pushes data through this port.
  • TCP/HTTP 8381
    Enables communication between the Data Aggregator and
    CA Performance Center
    for direct authentication of OpenAPI queries.
The following communication ports must be open on the other data sources:
  • TCP/HTTP 80
    Enables synchronization with CA Network Flow Analysis to retrieve configuration data.
  • TCP/HTTP 8681
    Enables synchronization with CA Network Flow Analysis to retrieve device data.
  • TCP/HTTP 8581
    Enables synchronization with
    CA Performance Management
    . For the Data Aggregator,
    CA Performance Center
    initiates communication and pulls data through this port.
The following diagram illustrates the default port usage:
For
CA Performance Management
to work properly in a firewall-protected environment, certain ports must be open. Throughout the documentation 8182, 8382, and 61617 appear as suggested port numbers for secured communications. In the instances where these appear, you are free to use any value you want as long as no other processes are using it. For more information about firewall and connectivity considerations, see Review Installation Requirements and Considerations
Performance Management Ports
Performance Management Ports
Verify Time Synchronization
Time synchronization using the Network Time Protocol (NTP) daemon is required for
CA Performance Center
and is recommended for all data source consoles. On Linux servers, the NTP daemon ensures that the clocks on the hosts are synchronized for timing purposes. Verify that the daemon is running on the
CA Performance Center
host server.
SLES System
Use the following procedure to verify time synchronization on an SLES system.
Follow these steps:
  1. Open a console and type the following command:
    $ systemctl status ntpd
  2. Verify that the NTP daemon is in an active (running) state.
  3. Type the following command to start and enable the NTP daemon manually:
    $ systemctl start ntpd
    $ systemctl enable ntpd
    The daemon is started.
RHEL 7.x or OL 7.x System
RHEL 7.x and OL 7.x. run NTP with
chronyd
. Use the following procedure to verify time synchronization on a RHEL 7.x or OL 7.x system.
Follow these steps:
  1. Open a console and type the following command:
    $ systemctl status chronyd
  2. Verify that the
    chrony
    daemon is in an active (running) state.
  3. Type the following command to start and enable the
    chrony
    daemon manually:
    $ systemctl start chronyd
    $ systemctl enable chronyd
    The daemon is started.
RHEL 6.x System
Use the following procedure to verify time synchronization on a RHEL 6.x system.
Follow these steps:
  1. Open a console and type the following command:
    $ chkconfig --list ntpd
    If the NTP daemon is installed, the output resembles the following example:
    ntp 0:off 1:off 2:on 3:on 4:off 5:on 6:off
    The output indicates the runlevels where the daemon runs.
  2. Verify that the current runlevel of the system (usually 3 or 5) has the NTP daemon set to 'on'. If you do not know the current runlevel, type the following commands to find it:
    $ runlevel
    N 3
    If the current runlevel does not have the NTP daemon enabled, enable it by typing the following command:
    $ chkconfig --level
    current_runlevel
    ntpd on
    Example:
    $ chkconfig --level 3 ntpd on
  3. Type the following command to start the NTP daemon manually:
    $ service ntpd start
    The daemon is started.
(Optional) Configure the Sudo User Account for
CA Performance Center
If you do not have root access to install and run
CA Performance Center
, configure the sudo user account.
Follow these steps:
  1. Locate the following file on the
    CA Performance Center
    host:
    /etc/sudoers
  2. Add a command alias with the following permissions to the file:
    • /tmp/CAPerfCenterSetup.bin
    • /etc/init.d/caperfcenter_console
      (for RHEL 6.x)
    • /etc/init.d/caperfcenter_devicemanager
      (for RHEL 6.x)
    • /etc/init.d/caperfcenter_eventmanager
      (for RHEL 6.x)
    • /etc/init.d/caperfcenter_sso
      (for RHEL 6.x)
    • /etc/init.d/mysql
    • /opt/CA/PerformanceCenter/PC/bin/caperfcenter_console
      (for RHEL 7.x, SLES, OL)
    • /opt/CA/PerformanceCenter/DM/bin/caperfcenter_devicemanager
      (for RHEL 7.x, SLES, OL)
    • /opt/CA/PerformanceCenter/EM/bin/caperfcenter_eventmanager
      (for RHEL 7.x, SLES, OL)
    • /opt/CA/PerformanceCenter/sso/bin/caperfcenter_sso
      (for RHEL 7.x, SLES, OL)
    • /opt/CA/PerformanceCenter/Tools/bin/npcshell.sh
    • /opt/CA/PerformanceCenter/SsoConfig
    • /opt/CA/PerformanceCenter/Uninstall_MySql
    • /opt/CA/PerformanceCenter/Uninstall_PerformanceCenter
    • /opt/CA/PerformanceCenter/Uninstall_SSO
    • /sbin/service
    • /opt/CA/MySql/bin/mysql
    • /opt/CA/MySql/bin/mysqldump
    • /opt/CA/PerformanceCenter/sso
    • /opt/CA/PerformanceCenter/PC
    • /opt/CA/PerformanceCenter/PC/webapps/pc/apps
    • /opt/CA/PerformanceCenter/PC/webapps/pc/css/CA-Blue/images
    • /opt/CA/PerformanceCenter/PC/webapps/pc/css/CA-Gray/images
    • /usr/bin/vim
    • /opt/CA/jre/bin/keytool
    • /opt/CA/PerformanceCenter/RemoteEngineer/re.sh
    • /opt/CA/PerformanceCenter/SslConfig
    Separate the permissions with commas and place all permissions on a single line.
    Example:
    Cmnd_Alias CAPERFCENTER = /tmp/CAPerfCenterSetup.bin,/opt/CA/PerformanceCenter/PC/bin/caperfcenter_console,/opt/CA/PerformanceCenter/DM/bin/caperfcenter_devicemanager,/opt/CA/PerformanceCenter/EM/bin/caperfcenter_eventmanager,/opt/CA/PerformanceCenter/sso/bin/caperfcenter_sso,/etc/init.d/mysql,/opt/CA/PerformanceCenter/Tools/bin/npcshell.sh,/opt/CA/PerformanceCenter/SsoConfig,/opt/CA/PerformanceCenter/Uninstall_MySql,/opt/CA/PerformanceCenter/Uninstall_PerformanceCenter,/opt/CA/PerformanceCenter/Uninstall_SSO,/sbin/service,/opt/CA/MySql/bin/mysql,/opt/CA/MySql/bin/mysqldump,/opt/CA/PerformanceCenter/sso,/opt/CA/PerformanceCenter/PC,/opt/CA/PerformanceCenter/PC/webapps/pc/apps,/opt/CA/PerformanceCenter/PC/webapps/pc/css/CA-Blue/images,/opt/CA/PerformanceCenter/PC/webapps/pc/css/CA-Gray/images,/usr/bin/vim,/opt/CA/jre/bin/keytool,/opt/CA/PerformanceCenter/RemoteEngineer/re.sh,/opt/CA/PerformanceCenter/SslConfig
    sudouser
    ALL = CAPERFCENTER
    • sudouser
      Specify the user who can run the sudo commands.
    With the sudo user configured, add the sudo prefix to all commands to install
    CA Performance Center
    .
    Example:
    sudo ./CAPerfCenterSetup.bin
Configure UTF-8 Support
Configure
CA Performance Center
host to support UTF-8 encoding. If UTF-8 encoding is disabled, characters might not display properly during the installation.
The appropriate language packs are also required to support localized deployments.
Some scripts that are used in the installation of selected components are not localized and run in English. For more information, see the
Localization Status Readme
file.
Follow these steps:
  1. Do one of the following steps:
    1. Type the following command from a Korn or bash shell:
      export LANG=
      LANG_value
      ; export LC_ALL=$LANG
      LANG_value
      specifies the language that you want the product to support. The following variables are supported:
      • English:
        en_US.utf8
      • French:
        fr_FR.utf8
      • Japanese
        :
        ja_JP.utf8
      • Simplified Chinese:
        zh_CN.utf8
      • Traditional Chinese:
        zh_TW.utf8
      For example:
      export LANG=zh_TW.utf8 ; export LC_ALL=$LANG
    2. Type the following command from a Bourne Shell:
      LANG=
      LANG_value
      ; export LANG
      LC_ALL=
      LANG_value
      ; export LC_ALL
      For example:
      LANG=zh_CN ; export LANG
      LC_ALL=zh_CN ; export LC_ALL
    The language variable is set.
Install Support for Required and Non-English Fonts
For the installer to run, and for
CA Performance Center
to generate PDF files, follow the standard instructions for installing the necessary fonts on your operating system.
CA Performance Center
and its data sources support multiple languages. The administrator can select a preferred language for each unique product operator. Language packs take advantage of operating system support for localized environments.
Product operators with some language preferences may not be able to view dashboard data in reports by default. To support these language preferences, install the fonts on the
CA Performance Center
host.
Follow these steps:
  1. Log in to the
    CA Performance Center
    host.
  2. Run one of the following commands to install the fonts:
    yum groupinstall fonts
    SLES:
    zypper install dejavu-sans-fonts dejavu-fonts-common arphic-ukai-fonts arphic-uming-fonts ipa-ex-mincho-fonts ipa-mincho-fonts ipa-pmincho-fonts xano-mincho-fonts baekmuk-bitmap-fonts baekmuk-ttf-fonts liberation-fonts
  3. Run the following command to rebuild the font caches:
    fc-cache –v
    SLES:
    fc-cache -fv
  4. Restart
    CA Performance Center
    .