×
 
 
  •  
$helper.renderConfluenceMacro('{bmc-global-announcement:$space.key}')

Important

   

This documentation space contains information about PATROL Agents when deployed in a BMC Helix Operations Management environment. If you are a TrueSight Operations Management user, see PATROL Agent 21.02. Open link

BMC PATROL Agent for BMC Helix Operations Management 21.02 ... Administering Loading and monitoring applications Disabling applications

Disabling applications based on application name

The /AgentSetup/disabledKMs configuration variable prevents KMs from being loaded by the Agent regardless of whether a console is a developer console.

Example

If you want to disable everything that begins with NT and CentOS, use NT.* and CentOS.*, not NT*. and CentOS*.

"/AgentSetup/disabledKMs" = {REPLACE="NT.*,CentOS.*,bad_APPL"}

Note

The /AgentSetup/disabledKMs variable does not require a PATROL Agent restart except when it contains regular expressions having special characters such as .* (for example NT.*, CentOS.*).

Format and type of data

item_1,item_2,item_n, KMs

Default value

None

Minimum \ maximum

Not applicable

Dependencies

None

Recommendation

The ALL_COMPUTERS.km and the KM for the current machine type cannot be disabled.

The file names must be on the same line.

Was this page helpful? Yes No Submitting... Thank you
Last modified by Shreya Gurukiran on Mar 30, 2020
disabling

Comments

Log in or register to comment.

Disabling applications
Disabling applications based on architecture
© Copyright 2014 - 2021 BMC Software, Inc.
Legal notices

Powered by Atlassian Confluence and Scroll Viewport

© Copyright 2005-2024 BMC Software, Inc. Use of this site signifies your acceptance of BMC’s Terms of Use . BMC, the BMC logo, and other BMC marks are assets of BMC Software, Inc. These trademarks are registered and may be registered in the U.S. and in other countries.