Skip to Content

Global Configuration parameter list

Global configuration parameters provide basic information that is automatically supplied as the default during catalog creation and update as well as during Patching and Remediation Job creation. The following sections describe the configuration parameters and how to configure these parameters:

To have basic information automatically supplied during catalog creation and update as well as Patching and Remediation Job creation, configure global patch configuration parameters.

To configure global patch configuration parameters

  1. From the Configuration menu, select Patch Global Configuration. 
    The Patch Global Configuration dialog box is displayed.
  2. Update the parameters as necessary.
    The parameters are divided into the following tabs:
    • All Operating Systems — Configuration parameters options for a proxy server
    • Platform-specific tabs – For each platform (such as the Windows tab and the Solaris tab) – Parameters that apply only to that specific platform type

    • Shavlik URL Configuration — Configuration for connecting to Shavlik for downloading Microsoft Windows patch related metadata

      The Shavlik metadata download occurs during Live Browse operations of the Hotfixes node in a Server Object, or during a Catalog Update Job run for an online Windows Patch Catalog.  For Offline Windows Patch Catalogs the metadata files must be added as Depot Files, as noted in the Patch-catalog-Windows-Catalog page.

Parameters on the All Operating Systems tab

Platform-specific parameters

Warning

Note

The following table describes parameters that are platform specific. You must enter this information for every platform that you want to patch using TrueSight Server Automation.

NEW IN 20.02.01

Common parameters in the platforms

Options on the yum.conf tab for Red Hat Enterprise Linux, Oracle Enterprise Linux, CentOS, and SUSE Linux Enterprise servers

On the yum.conf tab, perform either of the following actions:

  • Select the Use Default check box if you want to use a yum.conf file with default settings provided with TrueSight Server Automation.

Or

  • Deselect the Use Default check box if you want to use a custom yum.conf file. You can customize the yum.conf file to configure the different patch analysis and deployment parameters. Your desired entries should be added in the text box provided. 

    Click here to see a sample of a yum.conf file.

    Example of a yum.conf file:

    [main]
    debuglevel=4
    logfile=/var/log/yum.log
    pkgpolicy=newest
    distroverpkg=RedHat-release
    tolerant=1
    obsoletes=1
    plugins=0
    gpgcheck=0
    bootloader=1
Warning

Note

The system default /etc/yum.conf file is not used in either case. 

In addition to the options listed in the sample yum.conf above, if you want to avoid the removal of old RPMs during patch analysis when a native yum is used, you can include the installonly_limit option in the yum.conf file. For more information, see the description of this issue in Troubleshooting-Patch-Management-issues.

For more information about all the options that you can include in the yum.conf file, see the yum.conf man page.


You can also customize the yum.conf file when you create a Patching Job. For more information, see Patching-Job-Analysis-Options-for-Red-Hat-Enterprise-Linux-Oracle-Enterprise-Linux-and-SUSE-Linux-Enterprise.

Parameters on the Shavlik URL Configuration tab

The Shavlik URL Configuration tab provides information about the configuration files required by Microsoft Windows.

  • OemCatalogWpd.zip— Required by the Application Server to decrypt metadata files
  • WindowsPatchData.zip — Windows patch analysis and packaging information

The following table lists the fields that are available for configuring the Shavlik files. To edit the details, select the file and click Edit Patch Configuration File.

Where to go from here

Ensure that you have completed all tasks listed in Preparatory-tasks-for-patch-management.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

TrueSight Server Automation 20.02