General Tab
General
|
•
|
Description — Service description. |
|
•
|
Additional Required Components — Any other components required to run this service. You cannot enable this service unless this field is empty. |
|
•
|
Enable Service — Only enabled services are deployed. Disabling a service, effectively undeploys just that service while letting all other services in the application run as normal. This can be useful, for example when you wish to deploy an application that includes a service for which you don't have the required software. |
Target Machines
|
•
|
Remove from Selected Machines — Click to remove this service configuration from the selected machine(s). |
|
•
|
Add to Additional Machines — Adding services to additional machines is useful for fault tolerance. As a rule, it therefore does not make sense to run the same service on the same machine twice. |
|
•
|
Service Instance — Service instance from the selected machine. The service instance name includes the machine name. |
|
•
|
Software — The software required by this service instance. |
|
•
|
Deployment Status — Deployment status, as shown in the Configuration Builder |
|
•
|
FT Weight — The fault tolerance status and weight of the service instance. Appears only if Run Fault Tolerant is selected. For an in-depth discussion of this topic, see Configuring Fault Tolerant Process Engines. |
FT Group Settings
Appears only if a ActiveMatrix BusinessWorks process is assigned to additional machines. Note that TIBCO Adapter services cannot be assigned fault tolerant options.
|
•
|
Run Fault Tolerant — If selected, the selected service instances will run in fault tolerant mode. |
|
•
|
Heartbeat Interval (ms) — The master engine of a fault-tolerant group broadcasts heartbeat messages to inform the other group members that it is still active. The heartbeat interval determines the time (in milliseconds) between heartbeat messages. In the event if one process engine fails, another engine detects the stop in the master’s heartbeat and resumes operation in place of the other engine. All process starters are restarted on the secondary, and services are restarted to the state of their last checkpoint. |
|
•
|
Activation Interval (ms) — A standard TIBCO Rendezvous fault tolerant parameter, documented in the TIBCO Rendezvous Concepts, Developing Fault Tolerant Programs. |
Secondary process engines track heartbeat messages sent from the master engine. This field specifies the amount of time to expire since the last heartbeat from the master before the secondary restarts the process starters and process engines.
The Heartbeat Interval should be smaller than the Preparation Interval, which should be smaller than the Activation interval. It is recommended that Activation Interval be slightly over 2 heartbeats.
|
•
|
Preparation Interval (ms) — A standard TIBCO Rendezvous fault tolerant parameter, documented in the TIBCO Rendezvous Concepts, Developing Fault Tolerant Programs). |
When a master engine resumes operation, the secondary engine shuts down and returns to standby mode. For some situations, it may be necessary to ensure that the secondary engine has completely shut down before the master engine resumes operation.
This field is used to specify a delay before the master engine restarts. When the time since the last heartbeat from an active member exceeds this value, the ranking inactive member will receive a "hint" so that it can prepare for activation.
The Heartbeat Interval should be smaller than the Preparation Interval, which should be smaller than the Activation interval.