Preparing a patch repository

A patch repository is the location where metadata and binaries are stored prior to analysis, packaging, and deployment. Consider the following scenarios before you begin the configuration of the repository.

Scenarios for HP-UX

The following scenarios pertain to the configuration of a repository for the HP-UX platform:

• If patches are downloaded to Repository during analysis — the typical process for HP-UX — follow the instructions in Configuring-the-HP-UX-patch-repository-for-download.
• If the environment is secure, that is, access to the Internet is restricted, patch metadata and binaries must be downloaded to a server with Internet access and then transferred, via removable storage, to the designated patch repository. For more information, see Configuring-repositories-in-a-secure-environment.
• If limited outbound access is a consideration, place the following URL for HP-UX vendor access on an approved list, since Vendor Patch Content will attempt to download patch files from this site: ftp://ftp.itrc.hp.com.

Scenarios for CentOS

The following scenarios pertain to the configuration of a repository for the CentOS platform:

• Patches must always be downloaded for metadata generation.  Follow the instructions in Downloading-CentOS-patch-repositories.
• If limited outbound access is a consideration, ensure that the system that downloads the CentOS patches has access to one or more of the CentOS download locations.
• If the environment is secure, that is, access to the Internet is restricted, consult Configuring-repositories-in-a-secure-environment.