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 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.
Patch catalog Supported platforms for storing patch repositories Windows
Windows or Unix
Any AIX server
Note: If you are downloading patches using the SUMA option, ensure that you have the SUMA utility installed on your repository server.
Red Hat Enterprise Linux (RHEL) using the CDN interface
Red Hat Enterprise Linux 6, 7, or 8
SuSE Linux 12
SuSE Linux with SMT installed.
Note:To patch SuSE 12 targets, ensure that the SuSE patch repository server is configured with the Subscription Management Tool (SMT).
The following table lists the versions that are installed with SMT out-of-the-box, as well as the versions on which SMT must be manually installed.
Repository server version SMT installation
SuSE 11 SP3
SuSE 11 SP4
Note: SuSE recommends upgrading SuSE 12 to SuSE 12 SP1 to avoid dependency issues.
Not configured with SMT out of the box. You must manually install and configure SMT (version 11 SP3) on the repository server before you create a SuSE patch catalog. SuSE 12 SP1 or later (recommended) SMT is shipped out-of-the-box with the operating system.
Warning: BMC strongly recommends using Zypper when creating a patching job for a patch catalog that was created using the Subscription Management Tool (SMT). For more information, see Zypper patching tool.
SuSE Linux 11 SuSE Linux with createrepo and python-urlgrabber installed. Oracle Enterprise Linux Any supported RPM-based Linux with createrepo and python-urlgrabber installed Solaris
Windows or Unix
Note: If you are using Solaris 11 patches, you can only use a Solaris 11 server for storing the patch repository.
Ubuntu Unix Debian Windows or Unix Cent OS Any supported RPM-based Linux with createrepo and python-urlgrabber installed Fujitsu Solaris Windows or Linux HP-UX
An HP-UX patch repository must reside either directly on the HP-UX (SWA) Server or in a directory that the SWA Server considers to be a local share.
Note that if you are using an offline downloader, you can run the offline downloader on any Windows or Linux machine, but the HP-UX patch repository must still reside on the HP-UX (SWA) Server.
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 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
- Creating a patch catalog for Red Hat Enterprise Linux
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 TrueSight Server Automation 8.9.01, you must re-update the catalog of RHEL 5 and OEL 5.
The Dependency_List property must not be used to define dependencies for patch catalogs.