Prerequisites for Invoking Health Check Targets

Following conditions are a prerequisite for invoking Enterprise Deployment Health Check using TIBCO ActiveMatrix Administrator CLI:

  1. A TIBCO_HOME with this release.
  2. An instance of the remote_props.properties file (containing the information for connecting to TIBCO ActiveMatrix Administrator) from CONFIG_HOME/admin/<enterprise-name>/samples, that must be copied over to the TIBCO_HOME from where you intend to run Enterprise Deployment Health Check CLI script. (Note that CONFIG_HOME is the location from where TIBCO ActiveMatrix Administrator is running).
  3. Apache Ant 1.8 or higher needs to be used (You can use Ant available as part of the TIBCO ActiveMatrix installation located in TIBCO_HOME/amx/3.4/bin/ant. If you are using an external Ant, the JRE in use must be 1.7 or higher, that is, the JAVA_HOME must point to Java 7 or higher).
    Remember: When you obtain third party software or services, it is your responsibility to ensure you understand the license terms associated with such third-party software or services and comply with such terms.
  4. The machine from where the Enterprise Deployment Health Check will be executed needs network access to the TIBCO ActiveMatrix Administrator on which the Health Check is being run, that is, you should be able to access the web interface (UI) of TIBCO ActiveMatrix Administrator from this machine.
  5. If a Load Balancer is in use while accessing the web interface (UI) of TIBCO ActiveMatrix Administrator, the Load Balancer URL must be used in the remote_props.properties file for accurate results.
  6. If TIBCO ActiveMatrix Administrator is secured via SSL, you must also copy the necessary certificates to TIBCO_HOME to connect to the TIBCO ActiveMatrix Administrator via SSL.
Note:
  • The user specified in remote_props.properties must be a super user in TIBCO ActiveMatrix Administrator.
  • To make it easier to distinguish the deployments made by business deployments from the deployments done by Enterprise Deployment Health Check, it is recommended that a new “super user” be created and named “edhcuser” for instance, so as to easily identify various log entries pertaining to Enterprise Deployment Health Check.