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:
The patch catalog is used to maintain and work with the patch repository through the BMC Server Automation Console. For both types of repositories, online and offline, you create a patch catalog through the BMC 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 BMC Server Automation and has an RSCD agent installed on it.
To create a patch catalog
The following topics describe how to create a patch catalog for the various OS platforms:
- Creating a patch catalog for RHEL 7
- Creating a patch catalog for RHEL 6
- Creating a patch catalog for Microsoft Windows
- Creating a patch catalog for Oracle Enterprise Linux
- Creating a patch catalog for SuSE Linux
- Creating a patch catalog for Debian or Ubuntu
- Creating a patch catalog for Solaris
- Creating a patch catalog for AIX
Note
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.
If you are upgrading from earlier versions to BMC Server Automation 8.9.01, you must re-update the catalog of RHEL 5 and OEL 5.
Comments