Copyright © Cloud Software Group, Inc. All Rights Reserved

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

•	Monitoring Tab

•	Advanced Tab

General Tab

General

•	Name — Service name.

•	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. See Configuring Fault Tolerant Process Engines for an in-depth discussion of this topic.

FT Group Settings

Appears only if a TIBCO 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 chapter 15, 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 chapter 15 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.

Monitoring Tab

Rulebases

Click Add to add an existing custom TIBCO Hawk rulebase. The rulebase must have been configured using the TIBCO Hawk Display. See Adding a Rulebase to a Process or Service for more information.

Events

Click Add to create an event. See Adding 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.

•	Reset Failure Count. The value in this field defines how many restarts should be attempted before resetting the error counter to 0.

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.

•	Reset Failure Interval (seconds). The value in this field defines how much time should expire before resetting the error counter to 0.

For example, if you define the following three events and set the Reset Failure Count to 5:

•	Event 1, restart the instance and send an alert on the first failure.

•	Event 2, restart the instance and send an email on the second failure

•	Event 3, restart the instance and execute a command on subsequent failures.

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

Displays if an adapter service is included in the application. Allows you to change TIBCO Adapter SDK properties that were defined in the enterprise archive file.

Runtime Variables

Displays if an adapter service is included in the application. Displays the runtime variables settable for this service. You can change the runtime variable values as required.

TIBCO ActiveMatrix BusinessWorks Checkpoint Data Repository

If you wish to run TIBCO ActiveMatrix 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.

You specify a JDBC Connection resource for the database to be used when you configure your project in TIBCO Designer. The database is then one of the available options on the pop-up menu.

See Configuring Storage for TIBCO ActiveMatrix BusinessWorks Processes for more information.

TIBCO ActiveMatrix BusinessWorks Process Configurations

Allows you to change the process configurations. See Controlling Execution of TIBCO ActiveMatrix BusinessWorks Services for more information.

The Flow Limit parameter always appears in release 5.2 and later and only has meaning when deploying to a TIBCO ActiveMatrix BusinessWorks release 5.2 process engine. If you use Administrator 5.2 or later to deploy to a TIBCO ActiveMatrix BusinessWorks release 5.1.3 process engine, the parameter will display, but have no effect on the process engine.

Copyright © Cloud Software Group, Inc. All Rights Reserved