Creating a patch catalog

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.


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.

Before you begin

  • Ensure that security policies on the repository server do not block the download of the catalog.
  • (Red Hat Enterprise Linux, SUSE Linux Enterprise, and Oracle Enterprise Linux) you must pre-install the following packages on the server that hosts the patch repository:


    Tested version






    The versions above were used for testing and validation. Later versions of these packages are known to work but have not been officially qualified with the product.

  • Ensure that the platform on which you plan to store the patch repository is supported by BMC Server Automation.

     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 catalog

    Supported platforms for storing patch repositories


    Any Windows or Linux server

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

    Red Hat Enterprise Linux (RHEL)

    Based on the version of RHEL patching you are performing, the supported patch repository platforms are as follows: 

    For RHEL 6 or earlier: Any RPM-based Linux server

    For RHEL 7: Red Hat Enterprise Linux 6 or Red Hat Enterprise Linux 7

    Oracle Enterprise Linux

    Any RPM-based Linux server
    SUSE Linux

    The repository server can be any Linux server. However some SUSE-specific patches need to be stored only on a SUSE repository.

    BMC strongly recommends that you use a SUSE Linux server for storing the patch repository.


    Any AIX server


    Any Windows or Linux server

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


    Any Windows or Linux server


    Any Windows or Linux server
    Cent OSAny Linux server
    FujitsuAny Windows or Linux server
    HP-UXIf you are using the offline patch downloader you can use any Windows or Linux server to store the patch repository. However, if you are using the VPC method you must store the patch repository only on a HP-UX server.

To create a patch catalog

  1. Right-click a folder in the Depot and select New > Patch catalog > platformName > Catalog.
    For platformName, substitute the platform such as Windows patch catalog, Red Hat patch catalog.
  2. Provide information for the patch catalog as described in the following topics:


    After they are created, all panes in the wizard remain available for edit and review except General and Permissions.

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