Skip to content
CA Performance Management - 3.6
Documentation powered by DocOps

Migrate Performance Center

Last update April 16, 2019

If you upgrade the Linux OS release, you can use the following procedure to migrate Performance Center to a new host with a new IP address and hostname.

Note: You must upgrade the existing system to the product version you are migrating to before migrating. This migration procedure copies over Performance Center and does not require you to install Performance Center on the new host.

Prepare for the Migration

Follow these steps:

  1. Verify that the new host meets the system requirements. For more information, see Review Installation Requirements and Considerations and the CA Performance Management Sizing Tool
  2. Prepare the new host. For more information, see Prepare to Install CA Performance Management.

  3. If you installed Performance Center on the original system as sudo user, add the command alias on the new system:
    1. Locate the following file on the 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, or OL)
      • /opt/CA/PerformanceCenter/DM/bin/caperfcenter_devicemanager (for RHEL 7.x, SLES, or OL)
      • /opt/CA/PerformanceCenter/EM/bin/caperfcenter_eventmanager (for RHEL 7.x, SLES, or OL)
      • /opt/CA/PerformanceCenter/sso/bin/caperfcenter_sso (for RHEL 7.x, SLES, or 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/DM/repository

      • /opt/CA/PerformanceCenter/NotificationScripts

      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/DM/repository, /opt/CA/PerformanceCenter/NotificationScripts

      caadmin ALL = CAPERFCENTER

  4. Verify that the new host has network access from the original host.

Copy the Files from the Existing System

Follow these steps:

  1. Log in to the original Performance Center host.
  2. Stop the Performance Center services on the original system:

    service caperfcenter_console stop

    service caperfcenter_devicemanager stop

    service caperfcenter_eventmanager stop

    service caperfcenter_sso stop

  3. Create a dump of the MySQL netqosportal database from the original system:

    /opt/CA/MySql/bin/mysqldump --routines netqosportal > $backupDir/netqosportal.sql

  4. Create a dump of MySQL Event Manager data from the original system:

    /opt/CA/MySql/bin/mysqldump em > $backupDir/em.sql

  5. Copy the database backups:

    scp $backupDir/netqosportal.sql <new_PC_host>:/tmp/netqosportal.sql

    scp $backupDir/em.sql <new_PC_host>:/tmp/em.sql

  6. Stop the mysql service on the original system:

    service mysql stop

  7. Package the files in the installation directory:

    cd /opt

    tar czf PC.tgz ./CA

    Note: The following path is the default installation directory: /opt/CA

  8. Copy the files to the new Performance Center host:

    scp /opt/PC.tgz <new_PC_host>:/opt

  9. Copy the registry file that stores the installation and version information: 

    scp /var/.com.zerog.registry.xml <new_PC_host>:/var

  10. If you are migrating to a RHEL 6.x system, copy the Performance Center service startup scripts:

    scp /etc/init.d/caperfcenter_console <new_PC_host>:/etc/init.d/caperfcenter_console

    scp /etc/init.d/caperfcenter_devicemanager <new_PC_host>:/etc/init.d/caperfcenter_devicemanager

    scp /etc/init.d/caperfcenter_eventmanager <new_PC_host>:/etc/init.d/caperfcenter_eventmanager

    scp /etc/init.d/caperfcenter_sso <new_PC_host>:/etc/init.d/caperfcenter_sso

  11. Copy the MySQL startup script:

    scp /etc/init.d/mysql <new_PC_host>:/etc/init.d/mysql

  12. Copy the MySQL configuration file:

    scp /etc/my.cnf <new_PC_host>:/etc/

Configure the New System

Follow these steps:

  1. Log in to the new Performance Center host.

  2. Change the directory:

    cd /opt

  3. Extract PC.tgz file:

    tar -xvf PC.tgz

  4. Verify that the paths in /etc/profile point /opt/CA to the root where Performance Center is installed. Verify the following PATHs:

    PATH="${PATH}:/opt/CA/jre/bin"
    export PATH
    PATH="${PATH}:/opt/CA/MySql/bin"
    export PATH
    PATH="${PATH}:/opt/CA/PerformanceCenter/Tools/bin"
    export PATH

  5. Do one of the following steps:

    • If you are migrating to a RHEL 6.x system, add the following services to add runlevel information for the Performance Center system services:

      chkconfig --add mysql
      chkconfig --add caperfcenter_console
      chkconfig --add caperfcenter_devicemanager
      chkconfig --add caperfcenter_eventmanager
      chkconfig --add caperfcenter_sso

    • If you are migrating to a RHEL 7.x, SLES, or OL system, add the following services to add runlevel information for the Performance Center system services:

      chkconfig --add mysql
      /opt/CA/PerformanceCenter/PC/bin/caperfcenter_console install
      /opt/CA/PerformanceCenter/DM/bin/caperfcenter_devicemanager install
      /opt/CA/PerformanceCenter/EM/bin/caperfcenter_eventmanager install
      /opt/CA/PerformanceCenter/sso/bin/caperfcenter_sso install

  6. Configure MySQL in the /etc/group and /etc/passwd files:

    1. Add the following command to /etc/group:

      mysql:x:27:

    2. Add the following command to /etc/passwd file:

      mysql:x:27:27:MySQL Server:/var/lib/mysql:/bin/bash

    3. To ensure that the edits take effect, log out from the new Performance Center host, and log in again.
    4. Start the mysql service on the new system:

      service mysql start

  7. Restore the databases:

    cd /opt/CA/MySql/bin

    mysql netqosportal -unetqos -ppassword -e 'source /tmp/netqosportal.sql'

    mysql em -unetqos -ppassword -e 'source /tmp/em.sql'

  8. Start the Performance Center services on the new system as follows:

    1. Start the SSO service:

      service caperfcenter_sso start

    2. Wait one minute, then start the Event Manager and Device Manager:

      service caperfcenter_eventmanager start

      service caperfcenter_devicemanager start

    3. Wait one minute, then start the console service:

      service caperfcenter_console start

Update the Event Manager Data Source

If the new Performance Center hostname is different from the original Performance Center host, update the Event Manager data source. You must run a full Event Manager data source sync after you update the host name in the Performance Center UI.

Follow these steps:

  1. Log in to the Performance Center UI as the Administrator user. Use the new host name:
    http://new_PC_host:8181

    Note: If you cannot log in, run the following commands to check for database errors:

    mysqlcheck mysql

    mysqlcheck em

    mysqlcheck netqosportal

    If you see missing functions or corrupt table issues, see the following procedure for repairing the database.

  2. Hover over Administration, and click Data Sources: Data Sources.
  3. Select the Event Manager data source, and click Edit.
  4. Edit the Host Name and Display Name fields:

    Note: If SSL is configured, specify HTTPS for the communication protocol.

  5. To validate communication, click Test.
  6. Click Save.
  7. Select the Event Manager data source, and click Resync.
  8. Select Perform a Full Resynchronization, and click Resync.
    Performance Center resynchronizes with the Event Manager data source.
  9. After the Event Manager has completed a full resynchronization, re-register the Event Manager with the Data Aggregator:

    Find the data source ID of the DA, by logging into MySql and running the following query:

    /opt/CA/MySql/bin/mysql netqosportal

    SELECT SourceID as DASOURCEID FROM netqosportal.data_sources2 WHERE sourcetype = 262144;

    Take the returned ID for DASOURCEID and put it at the end of the following query, in place of DASOURCEID:
    For example, if it returns an ID of 6, replace DASOURCEID with 6:

    UPDATE em.data_sources SET LastEvent = 0, ConsumerID = 0 WHERE sourceid = DASOURCEID;

    The new Event Manager IP address is pushed to the Data Aggregator.

Repair the Database

If you cannot log in to to the Performance Center UI, check for database errors. If there are errors, stop the Performance Center services. Repair the database with the appropriate command. Then restart the Performance Center services.

Follow this procedure:

  1. Stop the Performance Center services:

    service caperfcenter_console stop

    service caperfcenter_devicemanager stop

    service caperfcenter_eventmanager stop

    service caperfcenter_sso stop

  2. Repair the database with the appropriate command:

    mysqlcheck -r mysql

    mysqlcheck -r em

    mysqlcheck -r netqosportal

  3. Start the Performance Center services on the new system as follows:

    1. Start the SSO service:

      service caperfcenter_sso start

    2. Wait one minute, then start the event manager and Device Manager:

      service caperfcenter_eventmanager start

      service caperfcenter_devicemanager start

    3. Wait one minute, then start the console service:

      service caperfcenter_console start

Configure the Data Source Connector for a Report

If you have the Unified Dashboards and Reporting for Infrastructure Management solution set up, and the new Performance Center hostname has changed, reconfigure the data source connector for the reports.

Follow these steps:

  1. Ensure that the CA Business Intelligence data source is installed.
  2. Open the CA Business Intelligence JasperReports login page in a browser. Log in to the CA Business Intelligence JasperReports Server as a user with an Administration role for the Public organization.
  3. Select ViewRepository.
  4. In the Folders panel on left, expand Public, ca, Performance Managementdatasources.
  5. Select the Performance Center data source and click Edit.
  6. Update the data source parameters and click Save:
    • Schema
      Specify HTTP or HTTPS.
    • Host
      Specify the Performance Center host name. Do not specify the Data Aggregator host name.
    • Port
      Specify the Performance Center port (default: 8181).
    • Performance Center GUID
      The Performance Center GUID (unique) is used when the password for the CA Business Intelligence web user is not available. This information passes to the Data Aggregator to ensure that the request is going to the correct Performance Center instance. A web service call on Performance Center retrieves this information.
      GUID Endpoint URL: http://hostname:8181/pc/center/webservice/datasources/performanceCenterGUID
  7. Click Save to apply the changes.

Verify the Migration

You must run Resync All to update the IP addresses for the Performance Center netqosportal tables.

Follow these steps:

  1. Log in to the Performance Center UI as the Administrator user. Use the new host name:
    http://new_PC_host:8181

  2. Hover over Administration, and click Data Sources: Data Sources.
  3. Click Resync All.
    Performance Center synchronizes with all registered data sources and updates the required contact information.
  4. To verify that the Performance Center host name is correct on the Data Aggregator, use the following REST call: 
    http://<DA_host>:8581/rest/dataaggregator
    The value for NpcHostName is the IP address of the new Performance Center host.

Configure Authentication

Performance Center supports external authentication schemes, such as LDAP, SAML 2.0, SSL.

  • For LDAP, no additional configuration is required with a Performance Center migration.
  • For SAML 2.0, reconfigure SAML 2.0 on the new system. For more information, see Set Up SAML 2.0 Support.
  • For SSL, set up new SSL certificates with the new hostname and alias. For more information, see Set Up SSL Certificates.

Note: If you have overridden the NPC hostname that Data Aggregator contacts, update Web Service Host in SSO Config. For more information, see Update Performance Center Website Settings.

Was this helpful?

Please log in to post comments.