Patch catalog - Oracle Enterprise Linux Catalog

The Oracle Enterprise Linux Catalog tab defines a number of options including locations (such as location of the source files and the repository) as well as filters and whether local copies of the files are created on the target server or downloaded directly during deployment.

Note

After a catalog option update, ensure you update the patch catalog for the catalog option update to take effect.

The following sections provide more information about the Oracle Enterprise Linux Catalog tab:

Catalog Mode

The Source from Disk Repository (Offline Mode) option is already selected.

Repository Options

Enter the following information:

Field

Description

Payload Source Location (NSH path)

Enter the location of existing metadata and payload files. Metadata files stored in this location are copied to the catalog automatically. Payload files are not copied to the catalog.
To support sourcing of vendor-supplied media, run the BMC_supplied patch downloader utility using the -createRepo option. This option creates the repository with the necessary metadata file. Then identify the source location here.

Repository Location (NSH path)

Enter the NSH path to the location of the patch repository. This location must be on a Linux platform (Red Hat, SUSE or Oracle Enterprise Linux). BMC recommends that this location have ample free space. Repositories typically contain many files, usually totaling gigabytes of data.

Depot Object Options

Enter the following information:

Field

Description

Network URL type for payload deployment

(default) Copy to agent at staging: During the Deploy Job staging phase, the BMC Server Automation Application Server copies patch payloads to a staging directory on the target server.
Agent mounts source for direct use at deployment (no local copy): A Deploy Job instructs the agent on a target server to mount the device specified in the URL and deploy patch payloads directly to the agent. Selecting this option means the Deploy Job does not copy patch payloads to a staging area on the agent, so the job does not create any local copies of the patches on target servers.

Network URL for payload deployment

The value entered here depends on your selection in the Network URL Type for Payload Deployment box.

If you chose Copy to agent at staging, do not enter a value here. The value is autopopulated based on the repository location.
if you chose Agent mounts source for direct use at deployment (no local copy), enter the NFS-accessible path to the location of the payload.

RBAC Policy

Browse to select a predefined ACL Policy. Permissions defined by the ACL Policy are assigned to all Depot Objects created in the catalog.

Filters

Filters limit the amount of information brought into the catalog. Use this procedure to re-create the same filters defined in the configuration file used by the Patch Downloader utility. You can define a filter during catalog creation or later, when editing the catalog.

There is no upper limit to the number of filter combinations you can make but there must be at least one. Only RPMs that match the combinations you define (and their dependent RPMs) are added to the catalog.

To begin, click Add Filter and enter the following information:

Field	Description
OS Flavor	Select the combination operating system and architecture from the list provided.
OS	The operating system, based on your selection in the OS Flavor box, is supplied automatically in a read-only box.
Architecture	The architecture, based on your selected in the OS Flavor box, is supplied automatically in a read-only box.

Patch catalog - Oracle Enterprise Linux Catalog

Catalog Mode

Repository Options

Depot Object Options

Filters

Comments