Starting Test Deployment

Starting Test Deployment

Invoking the Ant target "he" ("health.ent") involves running Test Deployment on each of TIBCO ActiveMatrix Nodes in the Enterprise.

Test Deployments are launched on each Node independent of the other Nodes, and once all Test Deployments are complete, a report is displayed showing the time taken for the deployment on each Node, grouped by the Node's Environment.

Deployment time on each Node varies based on how busy the particular Node is, how busy the Host managing that Node is, as well as how busy the Machine (on which the Node is running) is. If an Environment has many Nodes and if they are going through parallel Test Deployments simultaneously, some of the tasks that are part of the parallel Test Deployment that are sequential in the TIBCO ActiveMatrix Administrator, can skew the Test Deployment timings, but not by a huge margin.

Note: If the Test Deployment invoked as part of Enterprise Deployment Health Check is successful, there is a good chance that your business deployments will complete successfully. However, if the business deployment fails, it may be a result of an error with the business Application configuration itself.