Overview

Typically when the TIBCO ActiveMatrix BPM user adds a new BPM Node to existing BPM setup, the existing BPM Applications are redistributed to the newly added BPM Node, due to the symmetric nature of BPM Applications. Unfortunately, the Components of the BPM Applications that are in the 'Preparing For Undeploy (PFU)' state are not automatically redistributed.

Note: For the scope of this document, the Components in 'Preparing For Undeploy' state is referred to as 'PFU Components'. For more information on PFU Components and their role in TIBCO ActiveMatrix BPM, please refer to TIBCO ActiveMatrix BPM Product Documentation.

Prior to this release, the only way for BPM users to copy the PFU Components to the new BPM Node(s) was using the NodeUtil tool. The utility supports the exportComponents and importComponents commands with which the PFU Component can be exported from an existing BPM Node and imported into a new BPM Node, respectively. This process is cumbersome and error-prone, as it requires manually executing the utility for every BPM user application that contains PFU Components.

With this enhancement, TIBCO ActiveMatrix now provides a simplified TIBCO ActiveMatrix Administrator CLI-based solution with which all the steps described above can be executed in a single, automated step. The BPM user still have to perform the prerequisite steps of creating the new BPM Node Type and mapping the amx.bpm.app Application to newly created BPM Node. Once the amx.bpm.app Application is successfully distributed to new BPM Node (indicated by the 'In sync' status of the Application in the TIBCO ActiveMatrix Administrator), the user can run the CLI script defined by the exportImport_PfuComponents_build.xml located in the TIBCO ActiveMatrix installation at TIBCO_HOME/administrator/<version>/samples.