Prepare to Install Performance Center

To ensure that your npc installation is successful, complete the requirements before you install npc:
To ensure that your
Performance Center
installation is successful, complete the requirements before you install
Performance Center
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
    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
  • 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 the following command to install them.
    yum -y install zip unzip
Set the Limit on the Number of Open Files
Verify that the user account that is installing
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
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
    Performance Center
  2. Edit the following file:
  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
Performance Center
uses multiple ports to communicate with various components, particularly data sources. In addition, some of the products and components that integrate with
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
Performance Center
services to communicate with
Performance Center
  • TCP 3306
    Enables communications to the MySQL database (inbound) from the
    Performance Center
  • TCP/HTTP 8481
    Enables communications between the Device Manager and Console services.
The following communication ports allow users to contact
Performance Center
  • TCP/HTTP 8181
    Enables communications between client computers and the
    Performance Center
    server. Enables console communications with data sources.
  • TCP/HTTP 8381
    Enables communications between client computers and the
    Performance Center
    server. Also enables login using the single sign-on authentication component.
The following communication ports allow other data sources to contact
Performance Center
for eventing and OpenAPI single sign-on:
  • TCP/HTTP 8281
    Enables communications between the Event Manager, which is installed automatically with the
    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
    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,
    Performance Center
    initiates communication and pulls data through this port.
The following diagram illustrates the default port usage:
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
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
Performance Center
host server.
RHEL 7.x System
RHEL 7.x runs NTP with 
. Use the following procedure to verify time synchronization on a RHEL 7.x system. 
Follow these steps:
  1. Open a console and type the following command:
    $ systemctl status chronyd
  2. Verify that the
    daemon is in an active (running) state.
  3. Type the following command to start and enable the
    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
    ntpd on
    $ 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
Performance Center
If you do not have root access to install and run
Performance Center
, configure the sudo user account.
Follow these steps:
  1. Locate the following file on the
    Performance Center
  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)
    • /opt/CA/PerformanceCenter/DM/bin/caperfcenter_devicemanager 
      (for RHEL 7.x)
    • /opt/CA/PerformanceCenter/EM/bin/caperfcenter_eventmanager 
      (for RHEL 7.x)
    • /opt/CA/PerformanceCenter/sso/bin/caperfcenter_sso 
      (for RHEL 7.x)
    • /opt/CA/PerformanceCenter/Tools/bin/
    • /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/
    Separate the permissions with commas and place all permissions on a single line.
    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/,/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/
    • sudouser
      Specify the user who can run the sudo commands.
    With the sudo user configured, add the sudo prefix to all commands to install
    Performance Center
    sudo ./CAPerfCenterSetup.bin
Configure UTF-8 Support
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
Follow these steps:
  1. Do one of the following steps:
    1. Type the following command from a Korn or bash shell:
      export LANG=
       ; export LC_ALL=$LANG
      specifies the language that you want the product to support. The following variables are supported:
      • English:
      • French:
      • Japanese
      • Simplified Chinese:
      • Traditional Chinese:
      For example:
      export LANG=zh_TW.utf8 ; export LC_ALL=$LANG
    2. Type the following command from a Bourne Shell:
       ; export LANG
       ; export LC_ALL
      For example:
      LANG=zh_CN ; export LANG
      LC_ALL=zh_CN ; export LC_ALL
    The language variable is set.