Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 8 Setting Deployment Options : Edit Service Configuration Dialog

Edit Service Configuration Dialog
Fields can be edited if this dialog is invoked from the Configuration Builder pane. If invoked from the Deployed Configuration pane, the fields are read only.
The following tabs are available:
General Tab
General
Target Machines
FT Group Settings
Appears only if a TIBCO BusinessWorks process is assigned to additional machines. Note that TIBCO Adapter services cannot be assigned fault tolerant options.
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.
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.
Monitoring Tab
Rulebases
Click Add to add an existing custom TIBCO Hawk rulebase. The rulebase must have been configured using TIBCO Hawk Display. See Adding a Custom Rulebase to a Process or Service for more information.
Events
Click Add to create an event. See To Add an Event to a Service for more information.
Failure Count
When an instance is down unexpectedly, the error count and last failure time are tracked. When the error count is greater or equal to the value set for Reset Failure Count, or if the value set for Reset Failure Interval expires (whichever comes first), the error count is reset to zero.
When an instance is down, the TIBCO Hawk agent will attempt to restart the instance the number of times specified in this field. If the instance restarts after the number of times specified, the event you have defined is triggered.
The event is never triggered if Reset Failure Count is set to 0.
For example, if you define the following three events and set the Reset Failure Count to 5:
On the first failure, the error count is 1, the instance is restarted and an alert is sent.
On the second failure, the error count is 2, the instance is restarted and email is sent.
On third failure, the error count is 3, the instance is restarted and the command you configured is executed.
On fourth failure, the error count is 4, instance is restarted and the command you configured is executed.
On fifth failure, the error count is 5 and then reset to 0. The instance is restarted and the command you configured is executed.
On sixth failure, the error count is 1, the instance is restarted and an alert is sent.
The cycle repeats.
If you do not want to receive alerts frequently, Reset Failure Count should be set with a high value. When error count is reset to 0, the last failure time is reset as well. The Reset Failure Interval takes effect only after the first failure occurs.
Advanced Tab
Click Reset to Defaults to use the defaults defined in the enterprise archive file.
Adapter SDK Properties
It allows you to change TIBCO Adapter SDK properties that were defined in the enterprise archive file.
Runtime Variables
It displays the service settable global variable for this service. You can change the global variable values as required. Be sure to use valid XML characters only.
TIBCO BusinessWorks Checkpoint Data Repository
If you wish to run TIBCO BusinessWorks using multiple engines in fault tolerant mode, you must specify a checkpoint data repository.
For true fault tolerance, you must store the data in a database.
TIBCO BusinessWorks Process Configurations
You can change the process configurations. For more information, see Changing TIBCO BusinessWorks Process Configuration Properties.
The Flow Limit parameter appears in release 5.2 and later and only has meaning when deploying to a TIBCO BusinessWorks release 5.2 or later process engine. If you use Administrator 5.2 or later to deploy to a TIBCO BusinessWorks release 5.1.3 process engine, the parameter will display, but have no effect on the process engine.

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved