Unsupported content


This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

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 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.

     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.

    Oops, it seems that you need to place a table or a macro generating a table within the Table Filter macro.

    The table is being loaded. Please wait for a bit ...

    Patch catalogSupported platforms for storing patch repositories

    Windows or Unix

    Note: In BMC Server Automation 8.6 and earlier versions, you can run the Windows offline downloader only on a Windows machine.

    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 RHN (xmlrpc)

    Depending on the version of the Red Hat Enterprise Linux patch catalog that you want to store, use either of the following types of patch repository server:

    • For patch catalogs of RHEL 6 or earlier: Any RPM-based Linux server
    • For patch catalogs of RHEL 7 or later: RHEL 7 is only available via the CDN interface

      Red Hat Enterprise Linux (RHEL) using RHN (xmlrpc) is deprecated from BMC Server Automation 8.9.02 and CDN interface is for for all Red Hat platforms.

    SuSE Linux 12

    SuSE Linux with SMT installed.

    SuSE Linux 9, 10,. 11SuSE Linux with createrepo and python-urlgrabber installed.
    Oracle Enterprise LinuxAny supported RPM-based Linux with createrepo and python-urlgrabber installed

    Windows or Unix

    Note: If you are using Solaris 11 patches, you can only use a Solaris 11 server for storing the patch repository.

    UbuntuWindows or Unix
    DebianWindows or Unix
    Cent OSAny supported RPM-based Linux with createrepo and python-urlgrabber installed

    Fujitsu Solaris

    Windows or Linux

    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:


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.

Was this page helpful? Yes No Submitting... Thank you