Migrate Performance Center

If you upgrade the Linux OS release, you can use the following procedure to migrate npc to a new host with a new IP address and hostname.
capm360
If you upgrade the Linux OS release, you can use the following procedure to migrate
CA Performance Center
to a new host with a new IP address and hostname.
You must upgrade the existing system to the product version you are migrating to before migrating. This migration procedure copies over
CA Performance Center
and does not require you to install
CA 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
    CA Performance Center
    on the original system as
    sudo user,
    add the command alias on the new system:
    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, 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
    CA Performance Center
    host.
  2. Stop the
    CA 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 -unetqos -p
    password
    > $backupDir/netqosportal.sql
  4. Create a dump of MySQL Event Manager data from the original system:
    /opt/CA/MySql/bin/mysqldump em -unetqos -p
    password
    > $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
    The following path is the default installation directory:
    /opt/CA
  8. Copy the files to the new
    CA 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
    CA 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
If SSL is configured on the source system, reconfigure it on the new system after setup.
Follow these steps:
  1. Log in to the new
    CA 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
    CA 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
      CA 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
      CA 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
      CA 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 -p
    password
    -e 'source /tmp/netqosportal.sql'
    mysql em -unetqos -p
    password
    -e 'source /tmp/em.sql'
  8. Start the
    CA 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
CA Performance Center
hostname is different from the original
CA 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
CA Performance Center
UI.
Follow these steps:
  1. Log in to the
    CA Performance Center
    UI as the Administrator user. Use the new host name:
    http://
    new_PC_host
    :8181
    If you cannot log in, run the following commands to check for database errors:
    mysqlcheck mysql -unetqos -p
    password
    mysqlcheck em -unetqos -p
    password
    mysqlcheck netqosportal -unetqos -p
    password
    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:
    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
    .
    CA 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 sources:
    1. Run the following command to log in to MySQL:
      /opt/CA/MySql/bin/mysql em -unetqos -p
      password
    2. Run the following command:
      UPDATE em.data_sources SET LastEvent = 0, ConsumerID = 0;
    The new Event Manager IP address is pushed to the data sources.
Repair the Database
If you cannot log in to to the
CA Performance Center
UI, check for database errors. If there are errors, stop the
CA Performance Center
services. Repair the database with the appropriate command. Then restart the
CA Performance Center
services.
Follow this procedure:
  1. Stop the
    CA 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 -unetqos -p
    password
    mysqlcheck -r em -unetqos -p
    password
    mysqlcheck -r netqosportal -unetqos -p
    password
  3. tart the
    CA 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
CA 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
    View
    ,
    Repository
    .
  4. In the Folders panel on left, expand
    Public
    ,
    ca
    ,
    Performance Management
    ,
    datasources
    .
  5. Select the
    CA Performance Center
    data source and click
    Edit
    .
  6. Update the data source parameters and click
    Save
    :
    • Schema
      Specify HTTP or HTTPS.
    • Host
      Specify the
      CA Performance Center
      host name. Do not specify the Data Aggregator host name.
    • Port
      Specify the
      CA Performance Center
      port (default: 8181).
    • CA Performance Center
      GUID
      The
      CA 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
      CA Performance Center
      instance. A web service call on
      CA 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
CA Performance Center
netqosportal
tables.
Follow these steps:
  1. Log in to the
    CA 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
    .
    CA Performance Center
    synchronizes with all registered data sources and updates the required contact information.
  4. To verify that the
    CA 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
    CA Performance Center
    host.
Configure Authentication
CA Performance Center
supports external authentication schemes, such as LDAP, SAML 2.0, SSL.
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.