Setting up the patch catalogs
A patch catalog provides a place to store metadata about patches. Patch catalogs store vendor patch metadata, and are the source of information used for analysis, downloading patch payloads, and deployment.
Patch catalogs can be designed for specific needs. For example, a patch catalog can used for a particular operating system, such as Microsoft Windows 2008 or 2012. With well designed patch catalogs, it is easier to select the patches that should be used when evaluating the patch configuration of a particular server.
The following topics describe how to set up patch catalogs in your environment, to support patch management.
- Creating a patch catalog
- Downloading patch payloads to the catalog
- Modifying and updating patch catalogs
- Organizing patch catalog content using smart groups
- Deploying directly from the patch catalog (AIX only)
See the section about Patch Repository Sizing in the TrueSight Server Automation Sizing Guide available from the BMC Communities for the latest sizing and scalability recommendations.
Because the files in a Patch Catalog use a file location type of AGENT_MOUNT or NSH_COPY_AT_STAGING they are not part of File Server cleanup, even if the File Server is the storage location for the patches.