Monitor Server Performance with DX Application Performance Management

You can configure monitoring
NetOps Portal
, the data aggregator, and the data collector for instrumentation in
CA Application Performance Management
(APM).
You can configure monitoring
NetOps Portal
, the data aggregator, and the data collector for instrumentation in
CA Application Performance Management
(APM). APM receives performance metrics about these
DX NetOps Performance Management
components and hosts. During the installation of these components, you can have the installer configure the APM agent. You can also configure the agent for these components post-installation.
After each configuration, ensure that your changes have taken effect by restarting the corresponding services.
Follow these steps:
  1. Log in to the host for the relevant component (
    NetOps Portal
    , the data aggregator, and the data collector
    DX NetOps Performance Management
    ).
  2. Change to the working directory for the component for which you want to configure monitoring by issuing the following command:
    cd
    <installation_directory>
    Example:
    cd /opt/IMDataAggregator
    • installation_directory
      The installation directory of the component.
      Examples:
      /opt/IMDataAggregator
      ,
      /opt/CA/Performance/Center
  3. Run the
    setEMHost.sh
    script.
  4. When prompted, enter the following parameters:
    • CA APM hostname
    • CA APM port
      Default:
      5001
  5. On the
    NetOps Portal
    host, change to the working directory for APM by issuing the following command:
    cd
    <APM_installation_directory>
    Example:
    cd /opt/CA/PerformanceCenter/wily
    • APM_installation_directory
      The installation directory for APM.
      Default:
      /opt/CA/PerformanceCenter/wily
  6. Configure monitoring for
    NetOps Portal
    by completing the following steps:
    1. Configure monitoring for
      NetOps Portal
      services by issuing the following commands:
      ./addWily.sh
      <PC_installation_directory>
      <PC_installation_directory>
      /PC/conf/wrapper-user.conf PC ./addWily.sh
      <PC_installation_directory>
      <PC_installation_directory>
      /sso/conf/wrapper-user.conf sso ./addWily.sh
      <PC_installation_directory>
      <PC_installation_directory>
      /DM/conf/wrapper-user.conf DM ./addWily.sh
      <PC_installation_directory>
      <PC_installation_directory>
      /EM/conf/wrapper-user.conf EM
      • installation_directory
        The installation directory for
        NetOps Portal
        .
        Defaut:
        /opt/CA/PerformanceCenter
    2. Restart the
      NetOps Portal
      services by issuing the following commands:
      • (Red Hat Enterprise Linux (RHEL) 6.x)
        service caperfcenter_console restart service caperfcenter_devicemanager restart service caperfcenter_eventmanager restart service caperfcenter_sso restart
      • (RHEL 7.x, SUSE Linux Enterprise Server (SLES), or Oracle Linux (OL))
        systemctl restart caperfcenter_console systemctl restart caperfcenter_devicemanager systemctl restart caperfcenter_eventmanager systemctl restart caperfcenter_sso
  7. (If you have configured monitoring for the data aggregator) Do the following:
    1. Stop and restart ActiveMQ by issuing the following commands:
      • (RHEL 6.x)
        service activemq stop service activemq start
      • (RHEL 7.x, SLES, or OL)
        systemctl stop activemq systemctl start activemq
    2. Do one of the following steps based on your configuration:
      • Stop the Data Aggregator service by issuing the following command:
        • (RHEL 6.x)
          service dadaemon stop
        • (RHEL 7.x, SLES, or OL)
          systemctl stop dadaemon
      • (Fault-tolerant environment) If the local data aggregator is running, issue one the following commands to shut it down and prevent it from restarting until maintenance is complete:
        • (RHEL 6.x)
          service dadaemon maintenance
        • (RHEL 7.x, SLES, or OL)
          <installation_directory>
          /scripts/dadaemon maintenance
          • installation_directory
            The installation directory of the data aggregator.
            Examples:
            /opt/IMDataAggregator
    3. Do one of the following steps based on your configuration:
      • Start the Data Aggregator service by issuing the following command:
        service dadaemon start
      • (Fault-tolerant environment) Issue one the following commands to enable the fault-tolerant data aggregator so that it can start when necessary:
        • (RHEL 6.x)
          service dadaemon activate
        • (RHEL 7.x, SLES, or OL)
          <installation_directory>
          /scripts/dadaemon activate
  8. If you have configured monitoring for the data collector, stop and restart the Data Collector services by issuing the following commands:
    • (RHEL 6.x)
      service activemq stop service activemq start service dcmd stop service dcmd start
    • (RHEL 7.x, SLES, or OL)
      systemctl stop activemq systemctl start activemq systemctl stop dcmd systemctl start dcmd