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.
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.
This topic includes the following sections:
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:
(Linux only) Ensure that you have performed the corresponding prerequisite steps if you are creating a patch catalog for any of the following Linux operating systems:
Ensure that the platform on which you plan to store the patch repository is supported by BMC Server Automation.
Provide information for the patch catalog as described in the following topics:
Note
After they are created, all panes in the wizard remain available for edit and review except General and Permissions.
Patch catalog - Windows Catalog
Note: You can also display the IAVA ID for a Windows bulletin in the patch analysis results.