Resolution:
Description:

============
When running TIBCO BusinessEvents (BE) with OM type as inMemory in Fault Tolerent (FT) mode, the secondary node  fails to become Active on Primary Failure with Engine.FT properties enabled for fault tolerance.

Environment:
==========
TIBCO BusinessEvents 3.0.1 HF2 and above

All OS

Symptoms:
=========
When the primary engine fails, the secondary node fails to become active in Fault Tolerant Mode.

Resolution:
=========

(A) In Designer, for the BE archive that needs to be run in FT:
  A.1). Change the OM from "In memory" to "Cache"
  A.2). Set the Agent Group Name to "FTGroup1" (without the quotes).
  A.3). In the Advanced Settings, for all entities:
      A.3.i). Set the Cache Mode to "memory Only".
      A.3.ii). Uncheck "Suscribe Cluster".
  A.4). Rebuild the EAR.

For each TRA file in the deployment:
  B.1). Remove or comment out all properties whose name start with Engine.FT.
  B.2). Add the following properties:
    Agent.FTGroup1.maxActive=1
    Agent.FTGroup1.priority=10
  The last one (Agent.FTGroup1.priority) can be adjusted separately in each TRA file to obtain the desired behavior (lower number = higher priority).

Running TIBCO Business Events Engine with OM Type as "In Memory" in Fault Tolerant Mode.