Using the Solaris download cacher

Use the Solaris download cacher utility to pre-cache Solaris updates to the BigFix server or to a specified target directory before deploying the Fixlets to targeted endpoints.

For more information about the download cacher, see Solaris download cacher tool overview.

To access the tool from the BigFix console, complete the following steps:

From the BigFix Management domain, click Manage Sites > External Sites > Patches for Solaris > Run Solaris Download Cacher Tool - Windows.
Note: The Windows BigFix server and relays must be subscribed to the Patches for Solaris site for the task to be relevant.
Select the appropriate link in the Actions box to start the download.
Enter the necessary information when prompted. Ensure that the credentials to access the Oracle site are correct.
Select the targeted servers or relays, and click OK.

Running the download cacher tool manually

For air-gapped environments, you can run the Solaris download cacher utility manually.

Download the Solaris download cacher tool from the BigFix software website at https://software.bigfix.com/download/bes/util/SolarisDownloadCacher.exe.

Note: Solaris Download cacher (Solaris 11) does not support caching files for Patches.

To run in interactive mode:

SolarisDownloadCacher.exe

To run using a configuration file:

SolarisDownloadCacher.exe --configFile FILE

To run using command line options:

SolarisDownloadCacher.exe <OPTIONS>

Parameters:

--os OS1,OS2,...

Specifies a comma separated list of operating system names, such as 9,10,10x86. Default is all.

--patches ptch1,ptch2,...

Specifies a comma separated list of patch IDs in the format of 123456-78. Default is all.

--downloads FILE

Specifies pairs of patch files (in the format of 123456-78.jar or 10_Recommended.zip) and SHA1s in a file. Each pair is on its own line. The patches and sha1 value should be separated by a space. If a file is specified, the cacher will parse this file for patchIDs instead of parsing a site.

--cluster

Gathers the cluster for specified operating systems, if designated, or all of them if no operating systems are specified.

--superseded

Specifies flag to grab superseded content only.

--maintenance

Gathers from the Patches for Solaris Maintenance site.

--username USER

Specifies the user name to use to access the Oracle website.

--password PASS

Specifies the password to use to access the Oracle website.

--cacheDirectory DIR

Specifies the directory to cache to. Uses the BES cache if undefined.

--noRename

Specifies flag to not rename the files to sha1 values.

--emailServer SERVER

Specifies the SMTP server to use.

--emailUser USER

Specifies the email login to use.

--emailPassword PASS

Specifies the email password to use.

--emailSender ADDR

Specifies the email sender address. Required if emailServer is given.

--emailTo ADDR1,ADDR2,...

Specifies a comma separated list of email addresses. Required if emailServer is given.

--proxy SERVER:PORT

Specifies the proxy server to use.

--proxyUser USER

Specifies the proxy username to use.

--proxyPassword PASS

Specifies the proxy password to use.

--forceDownloads

Specifies the flag to force the cacher to re-download files, even if they already exist.

--autoCacheIncrease

Specifies the flag to automatically increase the cache in the event that the BES cache is filled. Only applies if --cacheDirectory is not specified.

--sites EFXMFILE

Specifies the masthead file. Multiple masthead files may be listed, separated by commas. If given, specified sites will be parsed rather than the default Solaris Fixlet sites.

--configFile FILE

Specifies a cacher configuration file that might contain any of the previous listed options. For example:

--------------------------------------
[Options]
cacheDirectory=C:\cache
proxy=http://someproxyurl:8080
proxyUser=john_doe
proxyPassword=p@ssw0rd
--------------------------------------

Command-line options take precedence if the same option is passed 
in the command line and the config file.

Additionally, the config file used for Download Plug-ins (plugin.ini)
is compatible here.  The [UA] and [Logger] sections from 
plugin.ini may be included in the cacher config file.  For example:

--------------------------------------
[Options]
cacheDirectory=C:\cache

; The following snippet taken from a plugin.ini
[UA]
proxy=http://someproxyurl:8080
proxyUser=john_doe
proxyPassword=p@ssw0rd
--------------------------------------

--logfile FILE

Specifies direct logging to the specified file (as well as STDOUT).

--debug LEVEL

Specifies a debug level (0-5) to determine the verbosity of the output. Default is 0.

--help

Prints the help message.