![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
• After you have deployed the process engines, it is most efficient to select all process engines by selecting the check boxes, and then choosing Start. After the primary and secondary engines have communicated, the master will display as Running and all other engines as Standby. If you start only the primary, it will first go to Standby mode as it checks the status of the other engines. It then changes to Running.
1. In TIBCO Administrator, click Application Management.
4. Click the General tab.
5. Select Run Fault Tolerant. Change other options as required. See FT Group Settings for field descriptions.
6. Click Save.To run TIBCO BusinessWorks using multiple engines in fault tolerant mode, you must specify a checkpoint data repository. See Failover and Checkpoint Data for more information.
1. In TIBCO Administrator, click Application Management.
4. Click the Advanced tab.
6. Click Save.If you use a database to store process engine information, a service is reinstantiated to the state of its last checkpoint. In the event of a failure, any processing done after a checkpoint is lost when the process instance is restarted by another engine. See TIBCO BusinessWorks Palette Reference for more information about Checkpoint activities. See Configuring Storage for TIBCO BusinessWorks Processes for more information about configuring process engine storage.
Figure 48 Fault-tolerant failoverThe expected deployment is for master and secondary engines to reside on separate machines. You can have multiple secondary engines, if desired, and you can specify a weight for each engine. The weight determines the type of relationship between the fault-tolerant engines. See Peer or Master and Secondary Relationships for more information about relationships between fault-tolerant engines.A master and its secondary engines is known as a fault-tolerant group. The group can be configured with several advanced configuration options, such as the heartbeat interval and the weight of each group member. See TIBCO BusinessWorks Palette Reference for a complete description of configuration options for fault tolerance.Because fault-tolerant engines are expected to be on separate machines, you should specify to use a database for storage for each process engine. By this you can specify the same JDBC Connection resource for the master and secondary engines, and therefore all engines can share the information stored for process instance checkpoints. See , Configuring Storage for TIBCO BusinessWorks Processes.See FT Group Settings for field descriptions.For information about which process engine starts and what state it starts in, see TIBCO BusinessWorks Process Design Guide.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |