Services

Services is a standard configuration interface for adding, editing, and removing services. A service is an application that runs continuously. You can customize it by choosing which program to run, any arguments, and any applicable configuration that the service uses to gather additional options and features. You can also use the services section to create primary and backup services and determine the failover state.

For information about interacting with the grid and form, see Standard Configuration Interface in Unified Assurance Concepts. The Services interface has additional controls, described in Grid Details.

This user interface calls REST methods from the api/broker/services endpoints.

The UI path for this interface is Configuration -> Broker Control -> Services.

Grid Details

The interface has the following buttons, in addition to the standard Unified Assurance buttons:

• Start, Stop, and Restart: Select a service, then click one of these to immediately interact with the service.

• Reload Config: Select a running service, then click this to initiate a reread of its configuration and rules files. See Reloading Application Configurations in Unified Assurance Implementation Guide for more information.

• Help: Select a service, then click this to show the documentation for the service.

In the main grid, click the - icon next to a server name to collapse that server's services and hide those entries. Click the + icon next to a server name to expand the services and show those entries.

Form Fields

• Server: The Unified Assurance server that will run the application.

• Package: The package for the application. The documentation for each application lists the correct package to select.

• Name: The name of the service.

• Program: The application that will run. The path to the application is relative to the Unified Assurance installation directory.

• Arguments: The command line options to be pass when running the application. The documentation for each application lists the available arguments.

• Description: The description of what the service does.

• Failover Type: The failover type for the service.

• Primary Service: When Failover Type is set to Redundant/Backup, the service set here will be checked to see if it is running, and if not, the backup is started.

• Decouple - When Failover Type is set to Redundant/Backup, this option appears. A normal primary/backup service pairing is a primary service on the primary server and a backup service on the backup server. This option allows for different combinations of primary/backup service pairings, such as a primary service on the backup server and a backup service on the primary server, or pairing services across servers that are not tied together.

• Cluster ID: When Failover Type is set to Cluster, this is the ID used to identify individual clusters of applications.

• Status: The status of the service.

• Privileged: Whether to run the service as the root user account. Many Unified Assurance applications need this option to be checked for proper functionality. The documentation for each application lists whether this should be checked or unchecked.

• Configuration: Additional settings needed for most applications to function, such as rules files and number of threads. Not every service supports configurations. The documentation for each application lists the supported configuration options.

Best Practice

When setting up redundant services, the failover type for the service on the primary server is set to Primary and the service on the redundant server is set to Redundant/Backup. If the service is part of a cluster, in which multiple services are grouped together to run, then the failover type must be Cluster. If the service is a standalone service, leave as Standalone.