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/domain-on-pv/overview.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,15 +10,15 @@ description = "Learn how to create a domain on a persistent volume."
10
10
11
11
### Overview
12
12
13
-
Domain on persistent volume (Domain on PV) is one of the operator's[domain home source type]({{< relref "/managing-domains/choosing-a-model/_index.md" >}}) choices.
14
-
Domain on PV requires that the domain home exists on a persistent volume. The domain home can be created either manually
13
+
Domain on persistent volume (Domain on PV) is an operator [domain home source type]({{< relref "/managing-domains/choosing-a-model/_index.md" >}}),
14
+
which requires that the domain home exists on a persistent volume. The domain home can be created either manually
15
15
or automatically by specifying the section, `domain.spec.configuration.initializeDomainOnPV`, in the domain resource YAML file.
16
16
The initial domain topology and resources are described using [WebLogic Deploy Tooling (WDT) models](#weblogic-deploy-tooling-models).
17
17
18
18
**NOTE**: The `initializeDomainOnPV` section provides a **one time only** domain home initialization.
19
19
The operator creates the domain when the domain resource is first deployed. After the domain is created,
20
20
this section is ignored. Subsequent domain life cycle updates must be controlled by
21
-
the WebLogic Server Administration Console, WebLogic Scripting Tool (WLST), or other mechanisms. See the [High level use case](#high-level-use-case).
21
+
the WebLogic Server Administration Console, the WebLogic Remote Console, WebLogic Scripting Tool (WLST), or other mechanisms. See the [High level use case](#high-level-use-case).
22
22
23
23
The `initializeDomainOnPv` section:
24
24
@@ -33,14 +33,14 @@ The typical Domain on PV use case is for an application life cycle that requires
33
33
For example, you might use frameworks like Meta Data Service (MDS), Oracle Application Development Framework (ADF), or Oracle Service Bus (OSB).
34
34
These frameworks require a running domain and the lifecycle operations are persisted to the file system. Typically,
35
35
after the initial domain is created, you use tools like Fusion Middleware Control, product-specific WLST functions,
36
-
the WebLogic Server Administration Console, the Service Bus Console, or JDeveloper for lifecycle operations. The changes are managed by
36
+
the WebLogic Server Administration Console, the WebLogic Remote Console, the Service Bus Console, or JDeveloper for lifecycle operations. The changes are managed by
37
37
these tools; the data and operations _cannot_ be described using WDT models.
38
38
39
39
### WebLogic Deploy Tooling 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 model files, variable property files, and application archive files.
43
+
They compactly define a WebLogic domain using model files, variable properties files, and application archive files.
44
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" >}})
@@ -54,16 +54,16 @@ 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
56
- Merges your WDT model files.
57
-
- Runs WDT Create Domain tool to create a domain home.
57
+
- Runs the WDT Create Domain Tool to create a domain home.
58
58
59
59
- After the introspector job completes:
60
-
- The operator creates one or more ConfigMap following the pattern `DOMAIN_UID-weblogic-domain-introspect-cm***`.
60
+
- The operator creates one or more ConfigMaps following the pattern `DOMAIN_UID-weblogic-domain-introspect-cm***`.
61
61
- The operator subsequently boots your domain's WebLogic Server pods.
62
62
63
63
### Runtime updates
64
64
65
65
You control runtime updates to the WebLogic domain configuration using tools, such as Fusion Middleware Control, product-specific WLST functions,
66
-
the WebLogic Server Administration Console, the Service Bus Console, the WebLogic Remote Console or the JDeveloper. After the initial domain is created, subsequent updates to the
66
+
the WebLogic Server Administration Console, the WebLogic Remote Console, the Service Bus Console, or JDeveloper. After the initial domain is created, subsequent updates to the
67
67
source of the WDT model files or any referenced macros _will be ignored_.
68
68
69
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
+11-13Lines changed: 11 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,7 +23,7 @@ WebLogic domain.
23
23
24
24
To use this feature, provide the following information:
25
25
26
-
-[WebLogic base image](#weblogic-base-image) - This is the Fusion Middleware Software to be used. For example, WebLogic Server or Fusion Middleware Infrastructure.
26
+
-[WebLogic base image](#weblogic-base-image) - This is the Fusion Middleware Software to be used, for example, WebLogic Server or Fusion Middleware Infrastructure.
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.
@@ -32,13 +32,12 @@ To use this feature, provide the following information:
32
32
-[Domain resource YAML file]({{< relref "/reference/domain-resource.md">}}) - This is for deploying the domain in WebLogic Kubernetes Operator.
33
33
34
34
35
-
- For details about each field,
36
-
- See the `initializeDomainOnPV` section
35
+
For details about each field, see the `initializeDomainOnPV` section
or use the command `kubectl explain domain.spec.configuration.initializeDomainOnPV`
38
+
or use the command `kubectl explain domain.spec.configuration.initializeDomainOnPV`.
40
39
41
-
-For a basic configuration example, see [Basic configuration](#basic-configuration).
40
+
For a basic configuration example, see [Basic configuration](#basic-configuration).
42
41
43
42
#### WebLogic base image
44
43
@@ -67,7 +66,7 @@ Specify an image that describes the domain topology, resources, and applications
67
66
|`domainCreationImages`| WDT domain images. | An array of images. | Y |
68
67
69
68
In this image or images, you must provide the required WDT installer [binaries](https://github.com/oracle/weblogic-deploy-tooling/releases),
70
-
and also the WDT model files, WDT variable files, and WDT archives files. The operator will use them to create the initial domain.
69
+
and also the WDT model files, WDT variables files, and WDT archive files. The operator will use them to create the initial domain.
71
70
72
71
For additional options in `domainCreationImages`, use the following command to obtain the details.
73
72
@@ -84,7 +83,7 @@ The image layout follows this directory structure:
84
83
85
84
You can create your own image using your familiar method or use the [WebLogic Image Tool (WIT)](https://github.com/oracle/weblogic-image-tool).
86
85
87
-
For example, because the file structure is the same as an [Auxiliary Image]({{< relref "/managing-domains/model-in-image/auxiliary-images.md" >}}) that's used in the Model in Image domain home type, you can
86
+
For example, because the file structure is the same as an [Auxiliary Image]({{< relref "/managing-domains/model-in-image/auxiliary-images.md" >}}) that's used in the Model in Image domain home source type, you can
|`domainCreationConfigMap`| Optional WDT models and WDT varaible files in ConfigMap. | ConfigMap name. | N |
112
+
|`domainCreationConfigMap`| Optional WDT models and WDT variables files in ConfigMap. | ConfigMap name. | N |
114
113
115
114
The files inside this ConfigMap must have file extensions, `.yaml`, `.properties`, or `.zip`.
116
115
@@ -188,10 +187,9 @@ spec:
188
187
| `persistentVolumeClaim` | Specification of the persistent volume claim if the operator is creating it. | Specification of the persistent volume claim if you want operator to create it. | N (operator will not create any persistent volume claim) |
189
188
190
189
191
-
Not all the fields in the standard Kubernetes PV and PVC are supported. For the list of supported fields in `persistentVolume` and `persistentVolumeClaim`, see
192
-
- See the `initializeDomainOnPV.peristentVolume` and `initializeDomainOnPV.peristentVolumeClaim` section
190
+
Not all the fields in the standard Kubernetes PV and PVC are supported. For the list of supported fields in `persistentVolume` and `persistentVolumeClaim`, see the `initializeDomainOnPV.peristentVolume` and `initializeDomainOnPV.peristentVolumeClaim` section
193
191
in the domain resource
194
-
[schema](https://github.com/oracle/weblogic-kubernetes-operator/blob/{{< latestMinorVersion >}}/documentation/domains/Domain.md), or use the commands
192
+
[schema](https://github.com/oracle/weblogic-kubernetes-operator/blob/{{< latestMinorVersion >}}/documentation/domains/Domain.md), or use the commands:
@@ -212,7 +210,7 @@ to specify any `persistentVolume` or `persistentVolumeClaim` under the `intiali
212
210
213
211
For JRF-based domains, before proceeding, please be sure to read this document, [JRF domains]({{< relref "/managing-domains/working-with-wdt-models/jrf-domain.md">}}).
214
212
215
-
This is the section describing the WebLogic domain. For example,
213
+
This is the section describing the WebLogic domain. For example:
Copy file name to clipboardExpand all lines: documentation/4.1/content/managing-domains/model-in-image/overview.md
+5-10Lines changed: 5 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,25 +10,21 @@ description = "Introduction to Model in Image, description of its runtime behavi
10
10
11
11
### Introduction
12
12
13
-
Model in Image is an alternative to the operator's Domain in Image and Domain in PV domain types. See [Choose a domain home source type]({{< relref "/managing-domains/choosing-a-model/_index.md" >}}) for a comparison of operator domain types.
14
-
15
-
Unlike Domain in PV and Domain in Image, Model in Image eliminates the need to pre-create your WebLogic domain home prior to deploying your Domain YAML file.
13
+
Model in Image is an alternative to the operator's Domain in Image and Domain on PV domain home source types. For a comparison, see [Choose a domain home source type]({{< relref "/managing-domains/choosing-a-model/_index.md" >}}). Unlike Domain on PV and Domain in Image, Model in Image eliminates the need to pre-create your WebLogic domain home prior to deploying your Domain YAML file.
16
14
17
15
It enables:
18
16
19
17
- Defining a WebLogic domain home configuration using WebLogic Deploy Tooling (WDT) model files and application archives.
20
18
- Embedding these files in a single image that also contains a WebLogic installation,
21
19
and using the WebLogic Image Tool (WIT) to generate this image. Or, alternatively,
22
-
embedding the files in one or more applicationspecific images.
20
+
embedding the files in one or more application-specific images.
23
21
- Optionally, supplying additional model files using a Kubernetes ConfigMap.
24
22
- Supplying Kubernetes Secrets that resolve macro references within the models.
25
23
For example, a secret can be used to supply a database credential.
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
24
+
- Updating WDT model files at runtime. The WDT models are considered the source of truth and match the domain configuration at all times. For example, you can add a data source
27
25
to a running domain. See [Runtime updates](#runtime-updates) for details.
28
26
29
-
This feature is supported for standard WLS domains.
30
-
31
-
For JRF domains, use [Domain on PV]({{< relref "/managing-domains/domain-on-pv/overview.md" >}}).
27
+
This feature is supported for standard WLS domains. For JRF domains, use [Domain on PV]({{< relref "/managing-domains/domain-on-pv/overview.md" >}}).
32
28
33
29
### WebLogic Deploy Tooling models
34
30
@@ -52,8 +48,7 @@ When you deploy a Model in Image domain resource YAML file:
52
48
- Packages the domain home and passes it to the operator.
53
49
54
50
- After the introspector job completes:
55
-
- The operator creates a ConfigMap named `DOMAIN_UID-weblogic-domain-introspect-cm`
56
-
(possibly with some additional maps distinguished by serial names) and puts the packaged domain home in it.
51
+
- The operator creates one or more ConfigMaps following the pattern `DOMAIN_UID-weblogic-domain-introspect-cm***`.
57
52
- The operator subsequently boots your domain's WebLogic Server pods.
58
53
- The pods will obtain their domain home from the ConfigMap.
0 commit comments