You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: site/cache.md
+26-24Lines changed: 26 additions & 24 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,28 +1,30 @@
1
1
# Cache
2
2
3
-
The Image Tool maintains a local file cache store, this store is used to look up where the Java,
4
-
WebLogic installers, and WebLogic patches reside in the local file system.
5
-
6
-
By default, it is stored in the user's ```$HOME/cache``` directory. Under this directory, the lookup information is
7
-
stored in the file ```.metadata```. All automatically downloaded patches also reside in this directory.
8
-
9
-
This default cache store location can be changed by setting the environment variable WLSIMG_CACHEDIR
3
+
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.
10
4
11
-
The `cache` command can be used to manipulate the local file cache. There are several subcommands of the cache feature:
5
+
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.
12
6
7
+
You can change the default cache store location by setting the environment variable `WLSIMG_CACHEDIR`:
8
+
9
+
```bash
10
+
export WLSIMG_CACHEDIR="/path/to/cachedir"
13
11
```
14
-
Usage: imagetool cache [COMMAND]
15
-
List and set cache options
16
12
17
-
Commands:
13
+
You use the `cache` command to manipulate the local file cache. There are several subcommands for the cache feature.
18
14
19
-
listItems List cache contents
20
-
addInstaller Add cache entry for wls, fmw, jdk or wdt installer
21
-
addPatch Add cache entry for wls|fmw patch or psu
22
-
addEntry Command to add a cache entry. Use caution
23
-
deleteEntry Command to delete a cache entry
24
-
help Displays help information about the specified command
25
15
```
16
+
Usage: imagetool cache [OPTIONS]
17
+
List and set cache options
18
+
```
19
+
20
+
| Option | Description |
21
+
| --- | --- |
22
+
|`listItems`| List cache contents. |
23
+
|`addInstaller`| Add cache entry for `wls`, `fmw`, `jdk`, or `wdt` installer. |
24
+
|`addPatch`| Add cache entry for `wls` or `fmw` patch, or `psu`. |
25
+
|`addEntry`| Add a cache entry. Use with caution. |
26
+
|`help`| Display help information for the specified command.|
Note: When adding a patch to the cache store. The patchId should be in the following format: 99999999_9.9.9.9.99999 The first 8 digits is the patch id, followed by an underscore and then release number. This is needed if you want to distinguish a patch that has different versions of the patch.
53
+
**Note**: When adding a patch to the cache store, the `patchId` should be in the following format: `99999999_9.9.9.9.99999` The first 8 digits is the patch ID, followed by an underscore, and then the release number. This is needed if you want to distinguish a patch that has different patch versions.
52
54
53
-
For example, patch 29135930 has several different versions from Oracle support, one for each release where the bug is fixed.
55
+
For example, patch `29135930` has several different versions in Oracle Support, one for each release in which the bug is fixed.
54
56
55
57
| Patch Name | Release |
56
58
| ---------|---------|
57
-
| 29135930 | 12.2.1.3.190416|
58
-
| 29135930 | 12.2.1.3.0 |
59
-
| 29135930 | 12.2.1.3.18106 |
59
+
| `29135930` | `12.2.1.3.190416`|
60
+
| `29135930` | `12.2.1.3.0` |
61
+
| `29135930` | `12.2.1.3.18106` |
60
62
61
-
If you have downloaded the release version ```12.2.1.3.190416``` of the patch, then you should use the argument as ```--patchId 29135930_12.2.1.3.190416```
63
+
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```.
62
64
63
65
- `addEntry`: Consider this an expert mode where you can add key value pairs to the cache without any validation.
The Image Tool creates a temporary directory, prefixed by ```wlsimgbuilder_temp```,
4
+
every time it runs. Under normal circumstances, this directory will be deleted. However,
5
+
if the process is aborted or the tool is unable to remove the directory, you can delete it manually.
6
+
7
+
By default, the temporary directory is created under the user's home directory. If you do not want it created under the home directory, set the environment variable:
8
+
9
+
```bash
10
+
export WLSIMG_BLDDIR="/path/to/dir"
11
+
```
12
+
13
+
14
+
If you see dangling images after the build, use the following command to remove them:
5. Occasionally, a WebLogic Server patch will require patching the OPatch binaries before applying them. We recommend downloading the latest OPatch patch and setting up the cache.
49
+
50
+
For example, if the latest OPatch patch is `28186730`, `13.9.4.0.0`. After downloading it from Oracle Support, you can use this command to set up the cache:
# Create an image with a WebLogic domain using the WebLogic Deploy Tool
2
+
3
+
The Image Tool lets you create a customized WebLogic domain in the image using the [WebLogic Deploy Tool](https://github.com/oracle/weblogic-deploy-tooling).
4
+
5
+
## Steps
6
+
7
+
1. Create the image, as directed in the [Quick Start](quickstart.md) guide.
8
+
9
+
2. Download the [WebLogic Deploy Tool](https://github.com/oracle/weblogic-deploy-tooling/releases), and then add it to the cache store:
The Image Tool supports creating Linux-based WebLogic Docker images, applying WebLogic patches, and creating WebLogic domains. It can be used with or without Internet access.
4
+
5
+
In this use case, the Image Tool will:
6
+
7
+
1. Start with a base-level operating system image (`oraclelinux:7-slim`).
8
+
2. Update the image with the necessary packages for installing WebLogic Server.
9
+
3. Install Java and WebLogic Server.
10
+
11
+
## Steps
12
+
13
+
1. Download these Java and WebLogic installers from the [Oracle Software Delivery Cloud](https://edelivery.oracle.com)
14
+
and save them in a directory of your choice, for example, `/home/acmeuser/wls-installers`:
15
+
16
+
`fmw_12.2.1.3.0_wls_Disk1_1of1.zip`\
17
+
`jdk-8u202-linux-x64.tar.gz`
18
+
19
+
20
+
2. Use the [Cache Tool](cache.md) to add the installers:
**Note**: The value of the version must be a valid WebLogic Server version number. This version number is used to verify and find the correct patch file to download from Oracle Support. The format of the version is a 5 digits tuple, separated by period. For example, ```12.2.1.3.0``````12.1.3.0.0```
31
+
32
+
3. Create the image using the [Create Tool](create-image.md) commands. For example:
0 commit comments