Cache
The Image Tool maintains a local file cache store. This store is used to look up where the Java, WebLogic Server installers, and WebLogic Server patches reside in the local file system.
By default, the cache store is located in the user’s $HOME/cache directory. Under this directory, the lookup information is stored in the .metadata file. All automatically downloaded patches also reside in this directory.
You can change the default cache store location by setting the environment variable WLSIMG_CACHEDIR:
You use the cache command to manipulate the local file cache. There are several subcommands for the cache feature.
| Option | Description |
|---|---|
listItems |
List cache contents. |
addInstaller |
Add an installer to the cache. |
addPatch |
Add a patch to the cache. |
addEntry |
Add a cache entry. Use with caution. |
help |
Display help information for the specified command. |
Usage scenarios
-
listItems: Display the contents of the cache. Displays key value pairs of the installers and patches. -
addInstaller: Add an installer to the cache, for example, JDK. -
addPatch: Add a patch to the cache.Note: When adding a patch to the cache store, the
patchIdshould be in the following format:99999999_9.9.9.9.99999The first 8 digits is the patch ID, followed by an underscore, and then the release number to identify the patch between different patch versions.For example, patch
29135930has several different versions in Oracle Support, one for each release or PSU in which the bug is fixed.
| Patch Name | Release |
|---|---|
29135930 |
12.2.1.3.190416 |
29135930 |
12.2.1.3.0 |
29135930 |
12.2.1.3.18106 |
If you downloaded the release version 12.2.1.3.190416 of the patch, then you should use the argument --patchId 29135930_12.2.1.3.190416.
-
addEntry: Consider this an expert mode where you can add key value pairs to the cache without any validation. -
deleteEntry: Delete an entry from the cache for a given key. Note: This command does not delete files from the disk.