Creating a patch catalog in offline mode

In an air-gapped environment, in which Internet access is not available to the Application Server, you download the metadata and payload information first to a server outside of the BMC Server Automation environment using a utility provided by BMC. For information about this utility and how to use it to download patches, see Setting up the Offline Patch Downloader utility.

The following procedure assumes that the downloads to the offline repository are done.

Use this procedure to create a patch catalog in Offline mode, using the previously downloaded patches.

StepExample screen

Navigate to the Windows offline downloader utility located in the installer package at the following location: 


Where <installer-path> is the path to the extracted installer package on the Linux payload machine.


Run the offline downloader utility and pass the the location of the the configuration file as a parameter.

sh -configFile <downloaderConfigurationFilePath>

Where <downloaderConfigurationFilePath> is the location of the configuration file used by the Patch Downloader.


Windows patch payload is downloaded to the payload repository location that you defined while creating the configuration file. The patch payload location should contain the following files:

  • hf7b.xml
  • pd5.xml

Important: In this walkthrough we will use the same Linux payload machine to host the repository location. However, if you are in an air-gapped environment, transfer the metadata and payload information, using a removable storage, to the patch repository server within your air-gapped environment.

 If the offline downloader did not execute successfully click here...

If your repository server is a Linux 64-bit machine and you are using BMC Server Automation 8.7, you may encounter the following error, while running the offline downloader.

java: /lib/ bad ELF interpreter: No such file or directory

To resolve this issue, you may perform either of the following:

  • Install the glibc.i686 or glibc.i386 library and re-execute the offline downloader.
  • Download JRE 1.8 on your Linux machine and point to it in the respective offline downloader script file

To troubleshoot other issues with the offline downloader, see Troubleshooting Patch Management issues.


Add the following files to a location in the Depot after each execution of the offline downloader utility. For information about adding files to the depot, see Adding files to the Depot.
  • hf7b.xml
  • pd5.xml

5Perform the following:
  1. In the console Folders view, expand the Depot folder.
  2. Navigate to an existing folder or create a new folder for the patch catalog. The example screenshot on the right uses a folder named Patch Catalog.
  3. Right-click the folder in which you want to store the new catalog and select New > Patch Catalog > Windows Patch Catalog

The New Patch Catalog wizard opens. On the General panel perform the following:

  1. In the Name field, provide a name for the new catalog.
  2. In the Description field, optionally, provide a description of the new catalog.
  3. In the Save in field, verify that the displayed path name is the folder in which you want to save the catalog. If necessary, you can browse to another location.
  4. Click Next.

On the Windows Catalog panel, select Source From Disk Repository (Offline Mode).


In the Repository Options section, provide information in the following required fields:

  • Payload Source Location: Browse to the location where the metadata and payload files are stored. It must be stored on a server, with an RSCD agent installed on it. The following payload files are referred:

    • hf7b.xml
    • pd5.xml
  • Repository Location: Browse to an appropriate location to serve as a patch repository. The repository can reside on any server that has an RSCD agent installed on it.

    BMC Server Automation processes the payload and metadata files from the payload source location and populates the repository location with Windows patches that are used by the catalog.

Note: The payload source location and the repository location can be the same.


In the Repository Options section, browse to and select the metadata and payload files added to the depot location (see this step).

  • Patch Signature File Location (hf7b): Browse to the signature file added to the depot. The file name is hf7b.xml and it contains metadata information.
  • Package Info File Location (pd5): Browse to the information file added to the depot. The file name is pd5.xml and it contains metadata information.
  • OEM Catalog File: Browse to the information file added to the depot. The file name is

Define the types of patches that you want to include in the catalog by selecting the same filters you have entered in the configuration file that contains the XML information used by the Patch Downloader utility.

  1. In the Filters section, click . The Add Windows Filter panel appears.
  2. In the Product drop-down list, select a product, application, or OS for which you want to add patches into the catalog. For example, select the Microsoft Windows Server 2003 product.
  3. Verify that the Language selection is correct for your site.
  4. Repeat the above steps, and select items from the Product drop-down list until your filter list is complete.
  5. Click OK.
  6. The second screenshot on the right, shows a completed Windows Catalog panel for Offline mode with two filter selections.
  7. Click Next.


The Default Notifications panel appears.

  1. Define the type of notifications and under which circumstances (status of the Catalog update job) the notifications are sent.
    Note: If you set up notifications for a particular scheduled job, the default notifications set here will be overridden.
  2. Click Next.
12The Properties panel provides a list of properties automatically assigned to a Catalog Job. For any property that has a check in the Editable column, select the property and click in the Value column.

Click Next.


The Schedules panel allows you to schedule a job to execute immediately, schedule a job at a specific time in the future, schedule a job on a recurring basis, and define notifications that are issued when a job runs.

Select the Execute job now option in the top-left corner of the Schedules panel to execute the catalog update job immediately after the wizard exits.

 If you want to schedule the execution of the catalog update job at a future time, click here ...
  1. Click . The Add New Schedule dialog box appears.
  2. Because we want the Patch Catalog Job to execute once at a particular time in future, we will select the Once option in the Occurrence panel. To select a recurring schedule you can select the appropriate option.
  3. Select the time and date that you want the job to execute.
  4. Select the appropriate time zone you want to follow.
  5. Define a priority for the job execution.
  6. Click the Scheduled Job Notifications tab.
  7. Define the type of notification that the scheduled job should send and under which circumstances (status of the catalog update job) the notifications are sent. This will override the settings defined in the Default Notifications panel.
  8. Click OK.
  9. Continue adding more schedules based on your requirement.

Click Next.


14The Permissions list is an access control list (ACL) granting roles access to any objects created in the system, such as jobs, servers, or depot objects. ACLs control access to all objects, including the sharing of objects between roles.

Using the Permissions panel, you can add individual permissions to an object. You can also set permissions by adding ACL templates or ACL policies. For more information, see Patch catalog - Permissions.

In this walkthrough we are using the default permissions. Click Finish.


The wizard creates the Patch Catalog Job and adds an object for it in the Depot location that you specified on the first wizard panel.

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