Previous Topic: Add a Service Discovery PolicyNext Topic: Delete Service Discovery Policies


Enable or Disable Service Discovery Policies

You can enable or disable specific Service Discovery policies based on your requirements and control the policy execution schedule.

When you disable a policy, it (disabled policy) does not delete any of the relationships that it has already discovered; this is the default behavior. You can configure this default behavior by configuring the value of the treatDisabledPoliciesAsDeleted parameter. This Service Discovery plugin parameter takes true or false as its value. The default value is false, which implies that the relationships that the policy has already discovered are not deleted when the policy is disabled. The value true implies that all relationships that the policy has already discovered are deleted when the policy is disabled. You can update the value of the parameter in the Service Discovery plugin properties file SOI_HOME\ServiceDiscovery\connectivityContext.xml. Restart Integration Services to make the change effective.

Follow these steps:

  1. Open the Operations Console.
  2. Select Tools, Service Discovery Policies.

    The Service Discovery Policy Editor opens.

  3. Select Dynamic Services, Automatic Relationships, or Unmanaged Relationships (as appropriate) in the Policies tab.

    A list of related policies appears in the Details tab. For example, if you select Dynamic Services, all dynamic service policies are displayed in the Details tab.

  4. Select the appropriate Service Discovery policy that you want to enable or disable in the Details tab.
  5. Click the Enables selected policies icon (plus sign with a tick mark) or Disables selected policies icon (minus sign with a tick mark) to enable or disable the policy.

    The Enabled column displays the updated status. Yes implies that the policy is enabled and No signifies that it is disabled.

Note: By default, the policy is enabled when you create it. However, if require a policy to be disabled from the beginning, disable it after creation, but before saving. This way the policy only starts discovering when you enable it manually later.