Configuring service dependencies in the service profile

You can configure service dependencies in the service profile.

Before you begin

  • You must be a cluster administrator or have the Services Manage permission to configure service dependencies.
  • The service for which you want to configure dependencies must be registered.

About this task

This task uses the terms antecedent and dependent. A service that other services depend on is called an antecedent service. A service that depends on the antecedent service to be running is called the dependent service.

Procedure

Follow these steps to configure dependencies for a service:

  1. Open the Service Profile page.
  2. In the Actions menu of sc:ControlPolicy, select Insert "sc:Dependency".
  3. Configure the following parameters:
    • type: The type parameter can be set to either OnStart or conditional. Only one type of dependency is allowed in the same service definition; either OnStart or conditional, not both.
      • OnStart: When this value is set, the dependent service does not start until the antecedent service is started.
      • conditional: When this value is set, the dependent service is affected by the antecedent service when the antecedent service is in one of the states that are defined for the satisfy and keep parameters.
    • satisfy: Defines a list of states that the antecedent service must be in before the dependent service can start. Separate multiple service states with a comma. The default value is STARTED.
    • keep: Defines a list of states that the antecedent service must be in for the dependent service to keep running. EGO restarts the dependent service if any of the antecedent services are not in the state defined for the keep parameter. Separate multiple service states with a comma. The default value is TENTATIVE, STARTED.
    • autoStart: Defines whether starting a dependent service should automatically trigger its antecedent service to start. The autoStart parameter can be set to either TRUE or FALSE. If autoStart=TRUE, the EGO service controller tries to start the corresponding antecedent service. The default value is TRUE.
    • content: Defines the name of an existing service that is the antecedent service of the dependent service.
  4. Click Save, confirm your changes, and then click Close.

Results

Your service is now updated for dependencies.