Setting up Solaris 10 Proprietary Patch Repository

Solaris 10 CPU (Critical Patch Updates) patches can only be downloaded from Orcale's website, using your subscription account. However, starting 2018 new CPU patches can only be downloaded with an Extended Support subscription contract. Oracle announces in its support portal from time to time (usually quarterly) when a new CPU patch is available for download.

Once you have access to these patches create your Solaris 10 Repository. 

 There are two options to set up a Solaris 10 Repository: 

• Remote Install (NFS): The patches will be located in a specific location/ server on your network. 

• Endpoint Download & Install: Patches will be downloaded to each endpoint.  

Step 1: Define where patches are located

Go to intigua.properties file (full path: /usr/share/tomcat/default/conf/intigua.properties) and create:

pg.repository.local.dir.base

Create a path to your chosen  Storage Location:   

For example for path of : /usr/share/intigua/patch-payload

 pg.repository.local.dir.base = /usr/share/intigua/patch-payload

Step 2: Setup the Solaris 10 Repository

Under your chosen location create a folder called: solaris 

•  When choosing Remote Install (NFS) - Put unzipped CPU only patches in this folder.
• When choosing Endpoint Download & Install: Put the zipped CPU patches in this folder.

Once you are done with the patching procedure for all your endpoints, you can delete the CPU patch (zipped or unzipped) from the repository folder (solaris folder). This is recommended if your you have limited storage capacity. Each CPU patch on average consumes about 2.5 GB disk space. Usually CPU patches are released every quarter, so you have enough time to upload the patches, install them and delete them from the repository once done.

Remote Install (NFS): 

Preconditions: Make sure a minimum storage space of 4 GB is available on the Storage Location (NFS folder).

Mount configuration: 

Storage Location: Any server in the network with a define NFS connection between the Endpoint the Manager. Note the Storage location can be the Manager itself (this option is less recommended).

Go to intigua.properties file (full path: /usr/share/tomcat/default/conf/intigua.properties) 

pg.repository.local.nfs.enabled = true

Tip:  If using the NFS option, make sure the edit /etc/exports file in case your Endpoints are behind a NAT

Set the NFS mount-point parameter to the network location, visible to the endpoints.

pg.repository.local.nfs.mount-point

For example:

pg.repository.local.nfs.mount-point=<IP>:/mnt/

In the Manager server create a NFS mount from the storage location parameter set in step # 1 to the NFS mount point.

For example:

mount -t nfs <IP>:/mnt /usr/share/intigua/patch-payload

Note: The Manager needs to mount to <IP>:/mnt the pg.repository.local.nfs.mount-point parameter should also point to <IP>/mnt, however the patches themselves will appear in the 'solaris' sub-directory if accessed thru the Manager command line.

Endpoint Download & Install

Preconditions: Make sure the configured endpoints have a minimum storage space of 8 GB.

Go to intigua.properties file (full path: /usr/share/tomcat/default/conf/intigua.properties)

Define where in the endpoints to download the Zip file - Minimum storage space required : 2.5 GB 

pg.endpoint.patch.download-location = /export/home/download

Define where in the endpoints to to Unzip the file - Minimum storage space required : 5.5 GB 

pg.endpoint.patch.unzip-location = /export/home/download/unzip

Additional Endpoint configuration: 

If you would like to have a different storage configurations on specific endpoints: 

Create file named: jetpatchcpulocation.sh 

PATCH_DOWNLOAD_LOCATION=abc/def
PATCH_UNZIP_LOCATION=xyz/ghj

In the End Point Placed file under: 

pg.endpoint.patch.cpu-file-location = /export/home