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
Merge branch 'pv-domain-simplify-doc-update-withsample-new' of orahub.oci.oraclecorp.com:weblogic-cloud/weblogic-kubernetes-operator into pv-domain-simplify-doc-update-withsample-new
Copy file name to clipboardExpand all lines: documentation/4.1/content/managing-domains/choosing-a-model/_index.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -41,11 +41,11 @@ When using the operator to start WebLogic Server instances from a domain, you ha
41
41
-**[Domain on PV]({{< relref "/samples/domains/domain-home-on-pv/_index.md" >}})**:
42
42
- Set the domain resource `domain.spec.domainHomeSourceType` attribute to `PersistentVolume`.
43
43
- Supply a WebLogic installation in an image and supply a WebLogic configuration as a domain home in a persistent volume.
44
-
- Optionally supply domain resource `domain.spec.configuration.initialDomainOnPV` section to provide information for the Operator to create the initial domain home.
44
+
- Optionally supply the domain resource `domain.spec.configuration.initialDomainOnPV` section to provide information for the Operator to create the initial domain home.
45
45
- Supply WebLogic applications in the persistent volume.
46
-
- Update the WebLogic configuration using WLST, or WebLogic Server Administration Console.
46
+
- Update the WebLogic configuration using WLST, or the WebLogic Server Administration Console.
47
47
- Optionally use [configuration overrides]({{< relref "/managing-domains/configoverrides/_index.md" >}})
48
-
supplied in a Kubernetes ConfigMap. Use this only if WLST, or WebLogic Server Administration Console does not fit your deployment strategy.
48
+
supplied in a Kubernetes ConfigMap. Use this only if WLST, or the WebLogic Server Administration Console does not fit your deployment strategy.
49
49
50
50
Note that you can use different domain home types for different domains; there's no restriction on having domains with different domain home types in the same Kubernetes cluster or namespace.
Copy file name to clipboardExpand all lines: documentation/4.1/content/managing-domains/domain-on-pv/domain-creation-images.md
+8-10Lines changed: 8 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title = "Domain creation images"
3
3
date = 2019-02-23T16:45:16-05:00
4
4
weight = 25
5
5
pre = "<b> </b>"
6
-
description = "Domain creation images supply the WDT artifacts for Domain on PV."
6
+
description = "Domain creation images supply the WDT models for Domain on PV."
7
7
+++
8
8
9
9
{{< table_of_contents >}}
@@ -13,14 +13,14 @@ description = "Domain creation images supply the WDT artifacts for Domain on PV.
13
13
Domain creation images are used for supplying model files, variable files,
14
14
application archive files, and WebLogic Deploy Tooling (WDT) installation files when deploying a domain using
15
15
a Domain on PV model. You will distribute model files, application archives, and the
16
-
WebLogic Deploy Tooling executable using these images. Then, the operator uses WDT and WDT artifacts to
16
+
WebLogic Deploy Tooling executable using these images. Then, the operator uses WDT and WDT models to
17
17
manage the domain.
18
18
19
19
**Note:** These images are _only_ used for creating the domain and will not be used to update the domain.
20
20
21
21
### Configuration
22
22
23
-
You can configure one or more WDT artifacts images in a domain resource.
23
+
You can configure one or more domain creation images in a domain resource.
24
24
25
25
Optionally, you can set the `imagePullPolicy`,
26
26
which defaults to `Always` if the `image` ends in `:latest` and `IfNotPresent`,
@@ -47,12 +47,12 @@ and installation files in the image using the `sourceModelHome` and `sourceWDTIn
47
47
#### Source locations
48
48
49
49
Use the optional attributes `sourceModelHome` and
50
-
`sourceWdtInstallHome` to specify non-default locations of
51
-
WebLogic Deploy Tooling model and installation files in your image(s).
50
+
`sourceWdtInstallHome` to specify non-default locations for the
51
+
WebLogic Deploy Tooling model and installation files in your domain creation image(s).
52
52
Allowed values for `sourceModelHome` and `sourceWdtInstallHome`:
53
53
- Unset - Defaults to `/auxiliary/models` and `/auxiliary/weblogic-deploy`, respectively.
54
-
- Set to a path - Must point to an existing location containing WDT model and installation files, respectively.
55
-
-`None` - Indicates that the image has no WDT models or installation files, respectively.
54
+
- Set to a path - Must point to an existing location containing WDT model and WDT installation files, respectively.
55
+
-`None` - Indicates that the image has no WDT models files and installation files, respectively.
56
56
57
57
If you set the `sourceModelHome` or `sourceWDTInstallHome` to `None` or,
58
58
the source attributes are left unset and there are no files at the default locations,
@@ -69,9 +69,7 @@ For example source locations, see [Configuration example 2](#example-2-source-lo
69
69
#### Multiple images
70
70
71
71
If specifying multiple images with model files in their respective `sourceModelHome`
72
-
directories, then model files are merged.
73
-
The operator will merge the model files from multiple images in the same order in which images appear under `model.auxiliaryImages` or `domain.domainCreationImages`.
74
-
Files from later images take precedence over files from earlier images.
72
+
directories, then model files are merged. Files from later images take precedence over files from earlier images.
75
73
76
74
When specifying multiple images, ensure that only one of the images supplies a WDT installation location using
Copy file name to clipboardExpand all lines: documentation/4.1/content/managing-domains/domain-on-pv/overview.md
+8-9Lines changed: 8 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,8 +23,8 @@ the WebLogic Server Administration Console, WebLogic Scripting Tool (WLST), or o
23
23
The `initializeDomainOnPv` section:
24
24
25
25
- Creates the PersistentVolume (PV) and/or PersistenVolumeClaim (PVC), if needed.
26
-
- Creates the JRF schema, if needed.
27
-
- Creates the WebLogic domain home, based on the provided WDT models on the persistent volume.
26
+
- Creates the RCU schema, if needed.
27
+
- Creates the WebLogic domain homeon the persistent volume based on the provided WDT models.
28
28
29
29
### High level use case
30
30
@@ -40,8 +40,8 @@ these tools; the data and operations _cannot_ be described using WDT models.
40
40
41
41
WDT models are a convenient and simple alternative to WLST
42
42
configuration scripts and templates.
43
-
They compactly define a WebLogic domain using YAML filesand support including
44
-
application archives in a ZIP file. For more information about the model format
43
+
They compactly define a WebLogic domain using model files, variable properties files, and application archives files.
44
+
For more information about the model format
45
45
and its integration,
46
46
see [Usage]({{< relref "/managing-domains/domain-on-pv/usage.md" >}})
47
47
and [Working with WDT Model files]({{< relref "/managing-domains/working-with-wdt-models/model-files.md" >}}).
@@ -53,19 +53,18 @@ The WDT model format is fully described in the open source,
53
53
When you deploy a Domain on PV domain resource YAML file:
54
54
55
55
- The operator will run a Kubernetes Job, called an introspector job, that:
56
-
- Merges your WDT artifacts.
57
-
- Runs WDT tooling to generate a domain home.
56
+
- Merges your WDT model files.
57
+
- Runs WDT Create Domain tool to create a domain home.
58
58
59
59
- After the introspector job completes:
60
-
- The operator creates a ConfigMap named `DOMAIN_UID-weblogic-domain-introspect-cm`
61
-
(possibly with some additional maps distinguished by serial names).
60
+
- The operator creates one or more ConfigMap following the pattern `DOMAIN_UID-weblogic-domain-introspect-cm***`.
62
61
- The operator subsequently boots your domain's WebLogic Server pods.
63
62
64
63
### Runtime updates
65
64
66
65
You control runtime updates to the WebLogic domain configuration using tools, such as Fusion Middleware Control, product-specific WLST functions,
67
66
the WebLogic Server Administration Console, the Service Bus Console, WebLogic Remote Console or JDeveloper. After the initial domain is created, subsequent updates to the
68
-
source of the WDT artifacts or any referenced macros _will be ignored_.
67
+
source of the WDT model files or any referenced macros _will be ignored_.
69
68
70
69
Some changes may require triggering an introspector job. For example:
Copy file name to clipboardExpand all lines: documentation/4.1/content/managing-domains/domain-on-pv/usage.md
+13-13Lines changed: 13 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,8 +27,8 @@ To use this feature, provide the following information:
27
27
-[Volumes and VolumeMounts information](#volumes-and-volumemounts-information) - This follows the standard Kubernetes pod requirements for mounting persistent volumes.
28
28
-[PersistentVolume and PersistentVolumeClaim](#persistent-volume-and-persistent-volume-claim) - This is environment specific and usually requires assistance from your administrator to provide the underlying details, such as `storageClass` or any permissions.
29
29
-[Domain information](#domain-information) - This describes the domain type and whether the operator should create the RCU schema.
30
-
-[Domain WDT artifacts](#domain-creation-wdt-artifacts) - This is where the WDT binaries, WDT model, WDT archive, and WDT variables files reside.
Copy file name to clipboardExpand all lines: documentation/4.1/content/managing-domains/model-in-image/overview.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,7 +23,7 @@ It enables:
23
23
- Optionally, supplying additional model files using a Kubernetes ConfigMap.
24
24
- Supplying Kubernetes Secrets that resolve macro references within the models.
25
25
For example, a secret can be used to supply a database credential.
26
-
- Updating WDT model files and artifacts at runtime. The WDT artifacts are considered the source of truth and matches the domain configuration at all time. For example, you can add a data source
26
+
- Updating WDT model files and artifacts at runtime. The WDT models are considered the source of truth and matches the domain configuration at all time. For example, you can add a data source
27
27
to a running domain. See [Runtime updates](#runtime-updates) for details.
28
28
29
29
This feature is supported for standard WLS domains.
@@ -47,7 +47,7 @@ The WDT model format is fully described in the open source,
47
47
When you deploy a Model in Image domain resource YAML file:
48
48
49
49
- The operator will run a Kubernetes Job called the 'introspector job' that:
50
-
- Merges your WDT artifacts.
50
+
- Merges your WDT models.
51
51
- Runs WDT tooling to generate a domain home.
52
52
- Packages the domain home and passes it to the operator.
Copy file name to clipboardExpand all lines: documentation/4.1/content/managing-domains/model-in-image/usage.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -68,7 +68,7 @@ to:
68
68
must be supplied in the model home because application archives
69
69
are not supported in the [optional WDT model ConfigMap](#optional-wdt-model-configmap).
70
70
71
-
There are multiple methods for supplying Model in Image WDT artifacts:
71
+
There are multiple methods for supplying Model in Image WDT models files, WDT variable files, and WDT archives files:
72
72
73
73
- Use auxiliary images:
74
74
Use [auxiliary images]({{< relref "/managing-domains/model-in-image/auxiliary-images.md" >}})
@@ -87,7 +87,7 @@ There are multiple methods for supplying Model in Image WDT artifacts:
87
87
88
88
Use either of the following methods.
89
89
90
-
-_Manual image creation_ uses Docker commands to layer the WDT artifacts, described in the previous table,
90
+
-_Manual image creation_ uses Docker commands to layer the WDT models files, WDT variable files, and WDT archives files, described in the previous table,
91
91
on top of your base image into a new image.
92
92
- The _WebLogic Image Tool_ (WIT) has built-in options for layering WDT model files,
93
93
WDT binaries, WebLogic Server binaries, and WebLogic Server patches in an image.
@@ -185,7 +185,7 @@ that are copied from [Auxiliary Images]({{<relref "/managing-domains/model-in-im
185
185
186
186
**Notes**:
187
187
188
-
- There are additional attributes that are common to all domain home source types, such as the `image` field. See the Domain Resource [schema](https://github.com/oracle/weblogic-kubernetes-operator/blob/{{< latestMinorVersion >}}/documentation/domains/Domain.md) and [documentation]({{< relref "/managing-domains/domain-resource.md" >}}) for a full list of Domain fields.
188
+
- There are additional attributes that are common to all domain home source types, such as the `image` or `clusters` field. See the Domain Resource [schema](https://github.com/oracle/weblogic-kubernetes-operator/blob/{{< latestMinorVersion >}}/documentation/domains/Domain.md) and [documentation]({{< relref "/managing-domains/domain-resource.md" >}}) for a full list of Domain fields.
189
189
190
190
- For fully specified Model in Image Domain YAML file examples,
191
191
see the [`kubernetes/samples/scripts/create-weblogic-domain/model-in-image/domain-resources`](https://github.com/oracle/weblogic-kubernetes-operator/tree/{{< latestMinorVersion >}}/kubernetes/samples/scripts/create-weblogic-domain/model-in-image/domain-resources) GitHub directory for the [Model in Image sample]({{< relref "/samples/domains/model-in-image/_index.md" >}}).
Copy file name to clipboardExpand all lines: documentation/4.1/content/managing-domains/working-with-wdt-models/model-files.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -69,9 +69,9 @@ For a description of model file macro references to secrets and environment vari
69
69
70
70
- For most models, it's useful to minimize or eliminate the usage of model variable files (also known as property files) and use secrets or environment variables instead.
71
71
72
-
- You can control the order that WDT uses to load your model files, see [WDT artifacts source location and loading order](#wdt-artifacts-source-location-and-loading-order).
72
+
- You can control the order that WDT uses to load your model files, see [WDT models location and loading order](#wdt-models-source-location-and-loading-order).
73
73
74
-
### WDT artifacts source location and loading order
74
+
### WDT models source location and loading order
75
75
76
76
Refer to this section if you need to control the order in which your model files are loaded. The order is important when two or more model files refer to the same configuration, because the last model that's loaded has the highest precedence.
Copy file name to clipboardExpand all lines: documentation/4.1/content/samples/domains/model-in-image/_index.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,7 +18,7 @@ WebLogic Deploy Tooling (WDT) model to specify your WebLogic configuration.
18
18
19
19
WDT models are a convenient and simple alternative to WebLogic Scripting Tool (WLST) configuration scripts and templates. They compactly define a WebLogic domain using model files, variable properties files, and application archives files. The WDT model format is described in the open source, [WebLogic Deploy Tooling](https://oracle.github.io/weblogic-deploy-tooling/) GitHub project, and the required directory structure for a WDT archive is specifically discussed [here](https://oracle.github.io/weblogic-deploy-tooling/concepts/archive/).
20
20
21
-
Furthermore, the Model in Image auxiliary image option lets you supply your WDT model files
21
+
Furthermore, the Model in Image auxiliary image option lets you supply your WDT models files, WDT variable files, and WDT archives files
22
22
in a small separate image separate from your WebLogic image.
23
23
24
24
For more information on Model in Image, see the [Model in Image]({{< relref "/managing-domains/model-in-image/_index.md" >}}) user guide. For a comparison of Model in Image to other domain home source types, see [Choose a domain home source type]({{< relref "/managing-domains/choosing-a-model/_index.md" >}}).
Copy file name to clipboardExpand all lines: documentation/4.1/content/samples/domains/model-in-image/initial.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -87,6 +87,7 @@ Run the following `kubectl` commands to deploy the required secrets:
87
87
Now, you create a Domain YAML file. A Domain is the key resource that tells the operator how to deploy a WebLogic domain.
88
88
89
89
Copy the contents of the [domain resource YAML file](https://raw.githubusercontent.com/oracle/weblogic-kubernetes-operator/{{< latestMinorVersion >}}/kubernetes/samples/scripts/create-weblogic-domain/model-in-image/domain-resources/WLS/mii-initial-d1-WLS-v1.yaml) file to a file called `/tmp/sample/mii-initial-domain.yaml` or similar. Alternatively, you can use the file `/tmp/sample/domain-resources/WLS-AI/mii-initial-d1-WLS-AI-v1.yaml` that is included in the sample source.
90
+
This file contains both the domain resource and the referenced cluster resource definition. See [Domain and Cluster resources]({{< relref "/managing-domains/domain-resource">}}).
90
91
91
92
Click [here](https://raw.githubusercontent.com/oracle/weblogic-kubernetes-operator/{{< latestMinorVersion >}}/kubernetes/samples/scripts/create-weblogic-domain/model-in-image/domain-resources/WLS/mii-initial-d1-WLS-v1.yaml) to view the Domain YAML file.
0 commit comments