Creating a patch catalog

Related BMC Communities article

BMC Customers using Automation for Patching use cases depend on OS vendors for Patches and metadata.  To view a document that tracks the service status of the different OS Vendors as known to BMC Support, see the following BMC Communities document:

OS Patching Vendor Health Dashboard

The patch catalog is used to maintain and work with the patch repository through the TrueSight Server Automation Console. For both types of repositories, online and offline, you create a patch catalog through the TrueSight Server Automation Console. Patches are added to the catalog as depot objects according to filters defined for the catalog.

Before you begin

  • Ensure that security policies on the repository server do not block the download of the catalog.

  • Ensure that the platform on which you plan to store the patch repository is supported by TrueSight Server Automation and has an RSCD agent installed on it.

    Click here to expand the supported platform matrix for storing patch repositories...

    Select the type of patch catalog you are creating to filter the supported platforms.


    1Support for this platform is deprecated. For the complete list of deprecated platforms, see Deprecated-and-discontinued-features.

To create a patch catalog

The following topics describe how to create a patch catalog for the various OS platforms:

Important

  • The deploy option for the patch catalog does not involve patch analysis and thus cannot account for dependencies on other patches. This option does not check for payload availability. BMC recommends that the deploy option be used only by advanced users who would want to deploy a patch without performing a patch analysis.
  • The Dependency_List property must not be used to define dependencies for patch catalogs.

 

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