1). TIBCO ActiveMatrix Adapter for Database 7.1.0 checks if tibco.sdk.faultTolerance.ems.enabled has been set to "on". If it is "on", TIBCO ActiveMatrix Adapter for Database 7.1.0 will work in Fault Tolerance mode; otherwise, TIBCO ActiveMatrix Adapter for Database 7.1.0 will work in single instance mode.
2). For Fault Tolerance mode, TIBCO ActiveMatrix Adapter for Database 7.1.0 checks if tibco.sdk.faultTolerance.ems.sessionName has been specified. If not, TIBCO ActiveMatrix Adapter for Database 7.1.0 reports an error regarding the missing property; if yes, TIBCO ActiveMatrix Adapter for Database 7.1.0 will check the connectivity for this session.
3). If a session does exist in the .dat file, TIBCO ActiveMatrix Adapter for Database 7.1.0 will use the value of tibco.sdk.faultTolerance.ems.queueName to navigate to token queue. If a session does not exist in the .dat file, TIBCO ActiveMatrix Adapter for Database 7.1.0 will use the following parameters navigate to token queue:
*****************************************
tibco.sdk.faultTolerance.ems.providerUrl
tibco.sdk.faultTolerance.ems.queueName
*****************************************
Example:
*****************************************
tibco.sdk.faultTolerance.ems.providerUrl tcp://localhost:7222
tibco.sdk.faultTolerance.ems.queueName FTQueue
*****************************************
4). From the EMS side, tibco.sdk.faultTolerance.ems.queueName should have prefetch=none set in the configuration file. For example, tibco.sdk.faultTolerance.ems.queueName FTQueue . In queues.conf used by the EMS server, there should be the following content: FTQueue prefetch=none.
5). TIBCO ActiveMatrix Adapter for Database 7.1.0 uses the messages in tibco.sdk.faultTolerance.ems.queueName as a token. That is to say, if tibco.sdk.faultTolerance.ems.queueName has message count as "n", there will be at most "n" TIBCO ActiveMatrix Adapter for Database 7.1.0 instances working in primary mode.