Configuring a Fault Tolerant Monitoring Service

Procedure

  1. Select Infrastructure > Nodes.
  2. In the Environment drop-down list, select SystemEnvironment.
  3. Create, install, and start a node, say AggregatorNode, on which to replicate the monitoring service.
  4. Add and install instances of the following resource templates on the AggregatorNode you created in the previous step.
    • TIBCO ActiveMatrix Governance JDBC Resource
    • TIBCO ActiveMatrix Governance Hibernate Resource
    • TIBCO ActiveMatrix Governance Teneo Resource
    • TIBCO ActiveMatrix Governance JNDI Connection Resource
    • TIBCO ActiveMatrix Governance JMS ConnectionFactory Resource
    • TIBCO ActiveMatrix Governance JMS Destination Resource
    • TIBCO ActiveMatrix Governance statistics internal JMS Destination Resource
    • TIBCO ActiveMatrix Governance statistics JMS Destination Resource
    • If the notification server is enabled for SSL:
      • TIBCO ActiveMatrix Governance CSP Keystore for EMS Resource
      • TIBCO ActiveMatrix Governance SSL Client for EMS Resource
    • If the database is enabled for SSL:
      • TIBCO ActiveMatrix Governance CSP Keystore for DB Resource
      • TIBCO ActiveMatrix Governance SSL Client for DB Resource
  5. Make sure the JDBC driver feature is provisioned on the AggregatorNode.
  6. Click Applications.
  7. In the Environment drop-down list, select SystemEnvironment.
  8. Expand the System folder.
  9. Click com.tibco.amx.mcr.aggregator .
  10. Click the Distribution tab.
  11. Distribute the following components to the AggregatorNode.
    • Aggregator
    • CLEventParserExtension
    • StandardPeriodicWindowExtension
    • StandardAggregateFunctionsExtension
  12. Click the Properties tab.
  13. Set the allInstancesActive property to true.
  14. Click Save.
  15. Click Deploy.
    The components are deployed to the selected node. The Runtime State changes to Starting and then Running.
  16. Verify that the replicated monitoring service works:
    1. Select Infrastructure > Nodes.
    2. In the Environment drop-down list, select SystemEnvironment.
    3. Click SystemNode and click Stop.
    4. Check the Enterprise Message Service server queue amx.governance.stats for pending messages. For information on how to check Enterprise Message Service server queues, see TIBCO Enterprise Message Service User's Guide. If the monitoring service running on the replica node is processing messages, the pending messages should be should be zero.