Using a service auto-discovery policy

Service auto-discovery policies are supplied by Smart Plug-ins (SPIs) to discover services in your managed environment and display them on a service map.

Before you can execute a service auto-discovery policy, you must deploy it to a managed node, either manually or through auto-deployment. See the specific SPI documentation for details on auto-deployment, which varies somewhat from SPI to SPI.

Usually there is no need to modify the SPI auto-discovery policy. However, certain SPIs may require that you configure this policy by adding parameter data such as a user name or password to allow access and discovery of specific applications on a managed node.

Undesired services in the service map that were discovered can be manually removed. These services will not be rediscovered unless a change in the environment is detected. However, you can start commands that force agents to resend service discovery data. When the management server receives the service discovery data, it recreates the service map, including any services that you previously removed. You can also use these commands for troubleshooting if services fail to appear on the management server. You can start these commands on nodes using the following tools:

• ToolsHP OpenView ToolsResend service discovery data (Windows agents)
• ToolsHP OpenView ToolsResend service discovery data (UNIX agents)

To disable automatic service discovery, remove service auto-discovery policies from the Policy Groups that are configured for auto-deployment.

Related Topics:

• Configure deployment for service types
• Node group Deployment properties
• Applying tools to managed nodes, services, and messages
• ovagtrep