Install a Low-Scale System

In a standard large-scale deployment, the Data Aggregator (DA) and Data Collector (DC) components require dedicated nodes. For some smaller deployments of 150,000 polled items or less, these components can run on a shared node.
capm350
HID_DA_DC_shared_host
In a standard large-scale deployment, the Data Aggregator (DA) and Data Collector (DC) components require dedicated nodes. For some smaller deployments of 150,000 polled items or less, these components can run on a shared node.
Do not deploy the DA and DC on a single node in high scale environments.
Limitations
This deployment does not support the following options:
  • Calculated metrics beyond 150,000 metrics per second
  • Fast (1 minute) polling
  • Integration with 
    CA Mediation Manager
     or 
    CA Virtual Network Assurance
  • Multiple DCs
  • Multiple IP domains
  • Multiple tenants
  • Polling beyond 150,000 items
The configuration does not persist through upgrades. After you upgrade the DA, upgrade and configure the DC according to the procedures described here.
Installation
To deploy
CA Performance Management
 with the DA and DC on a single node, complete the following installation steps:
  1. Install the Data Repository
    Because the Data Repository in a low-scale system is deployed on a single node, skip steps that refer to cluster installation.
    See Prepare to Install the Data Repository and Install the Data Repository.
  2. Install the Data Collector on the Data Aggregator host. See the following procedures.
    3
Install the Data Collector
After you install the DA, install and configure the DC on the same host.
Follow these steps:
  1. Log in to the shared host.
  2. Verify that the DA service is running:
    service dadaemon status
    For RHEL 7.x,
    service
    invokes
    systemctl
    . You can use
    systemctl
     instead.
  3. If the service is not running, do one of the following steps:
    • Start the Data Aggregator service:
      service dadaemon start
    •  (Fault tolerant environment) Run 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:
        DA_Install_Directory
        /scripts/dadaemon activate
  4. Verify that the ActiveMQ broker is running:
    service activemq status
    If the service is not running, start the ActiveMQ service:
    service activemq start
  5. Download the DC installer:
    wget -nv http://
    da_host
    :8581/dcm/InstData/Linux/VM/install.bin
  6. Make the install file executable:
    chmod a+x install.bin
  7. Do one of the following steps:
    • Stop the Data Aggregator and ActiveMQ services:
      service dadaemon stop
      service activemq stop
    • (Fault tolerant environment) If the local Data Aggregator is running, run 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:
        DA_Install_Directory/scripts/dadaemon maintenance
  8. Install the DC:
    ./install.bin -i console
  9. Follow the instructions in the console.
    • The installer prompts you for the hostname or IP address of the DA host. Supply the hostname of the shared host.
    The DC is installed and the DC and ActiveMQ services start. After a short time, the DC service fails because the DA service is not running.
  10. Uninstall the Data Aggregator ActiveMQ service:
    /opt/IMDataAggregator/scripts/activemq uninstall
  11. Install the Data Collector ActiveMQ service:
    /opt/IMDataCollector/scripts/activemq install
Reconfigure the Data Collector
After you install the DC on the shared host, reconfigure the DC to use the shared host. On a shared host, the DA and DC use a single ActiveMQ broker.
The procedure includes the following variables:
  • <DAInstallDir>
    The installation directory for the DA
    Default:
    /opt/IMDataAggregator
  • <DCInstallDir>
    The installation directory for the DC
    Default:
    /opt/IMDataCollector
Follow these steps:
  1. Stop the DC and ActiveMQ services:
    service dcmd stop
    service activemq stop
  2. Modify the DA startup script:
    1. Edit the following file:
      DA_Install_Directory
      /scripts/dadaemon
    2. Modify the ACTIVEMQ_HOME variable to point to the DC ActiveMQ broker:
      ACTIVEMQ_HOME="
      <DCInstallDir>
      /broker/apache-activemq-
      version
      " export ACTIVEMQ_HOME
      • version
        Specify the ActiveMQ version. Make sure you enter the correct version. To find the correct version, go to the following location:
        <DCInstallDir>
        /broker
  3. Disable the DA ActiveMQ broker heartbeat:
    1. Create the following file:
      <
      DAInstallDir
      >/apache-karaf-2.4.3/etc/com.ca.im.dm.core.amq.cfg
      Create this file as the user running the Data Aggregator to ensure the correct permissions are set on the new file.
    2. Edit the file and insert the following property configuration:
      jmsbroker-heartbeat-disabled=true
    3. To disable log messages that are related to the DA heartbeat manager, edit the following file:
      <
      DAInstallDir
      >/apache-karaf-2.4.3/etc/org.ops4j.pax.logging.cfg
    4. Insert the following property configuration:
      # Disable ActiveMQ Health Monitoring log messages in shared DA/DC mode
      log4j.logger.com.ca.im.core.jms.heartbeat.JmsHeartbeatManager=OFF
  4. Modify the Apache Karaf JMX management properties:
    1. Edit the following file:
      <DCInstallDir>
      /apache-karaf-2.4.3/etc/org.apache.karaf.management.cfg
    2. Set the following properties:
      rmiRegistryPort = 1199
      rmiServerPort = 44445
  5. (Optional) To support the ability to debug the DA and DC components simultaneously, modify the Karaf debug port:
    1. Edit the following file:
      <
      DCInstallDir
      >/apache-karaf-2.4.3/bin/karaf
    2. Set the following property:
      DEFAULT_JAVA_DEBUG_PORT=5006
  6. Do one of the following steps:
    • Start the Data Aggregator service:
      service dadaemon start
    • (Fault tolerant environment) Run 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:
        DA_Install_Directory
        /scripts/dadaemon activate
  7. Start the DC service:
    service dcmd start
  8. The DA and DC services start on the single host. Complete post installation configuration for your deployment.
Validate the Deployment
To validate the deployment, verify that the required services are functioning as expected.
Follow these steps:
  1. Validate that the DA service is running:
    service dadaemon status
  2. Validate that the DC service is running:
    service dcmd status
  3. Validate that the ActiveMQ Broker is running:
    service activemq status
  4. Validate that the ActiveMQ Broker being run is the Data Collector broker:
    service activemq status
    The returned message must include the following information:
    Status for ActiveMQ: INFO: Loading '
    <
    DCInstallDir
    >
    /broker/apache-activemq-
    version
    /bin/env
    '
     If the message does not show the DC installation directory, repeat the step in the previous procedure to modify the DA startup script.