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: documentation/site/content/managing-domains/model-in-image/overview.md
+13-6Lines changed: 13 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -43,14 +43,21 @@ The WDT model format is fully described in the open source,
43
43
When you deploy a Model in Image domain resource YAML file:
44
44
45
45
- The operator will run a Kubernetes Job called the 'introspector job' that:
46
-
- Merges your WDT models.
47
-
- Runs WDT tooling to generate a domain home.
48
-
- Packages the domain home and passes it to the operator.
46
+
- For an [Auxiliary Image]({{< relref "/managing-domains/model-in-image/auxiliary-images.md" >}}) deployment, an init container is used to copy and set up the WDT installer in the main container, and all the WDT models are also copied to the main container.
47
+
- Sets up the call parameters for WDT to create the domain. The ordering of the models follow the pattern [Model files naming and ordering]({{< relref "/managing-domains/model-in-image/model-files#model-file-naming-and-loading-order" >}}).
48
+
- Runs WDT tooling to generate a domain home using the parameters from the previous step.
49
+
- Encrypts the domain salt key `SerializedSystemIni.dat`.
50
+
- Packages the domain home and passes it to the operator. The packaged domain has two parts. The first part `primordial domain` contains the basic configuration including the encrypted salt key. The second part `domain config` contains the rest of the configuration `config/**/*.xml`. These files are compressed but do not contain any applications, libraries, key stores, and such, because they can be restored from the WDT archives.
49
51
50
52
- After the introspector job completes:
51
-
- The operator creates one or more ConfigMaps following the pattern `DOMAIN_UID-weblogic-domain-introspect-cm***`.
52
-
- The operator subsequently boots your domain's WebLogic Server pods.
53
-
- The pods will obtain their domain home from the ConfigMap.
53
+
- The operator creates one or more ConfigMaps following the pattern `DOMAIN_UID-weblogic-domain-introspect-cm***`. These ConfigMaps contain the packaged domains from the introspector job and other information for starting the domain.
54
+
55
+
- After completion of the introspector job, the operator will start the domain:
56
+
- For an [Auxiliary Image]({{< relref "/managing-domains/model-in-image/auxiliary-images.md" >}}) deployment, an init container is used to copy and set up the WDT installer in the main container, and all the WDT models are also copied to the main container first.
57
+
- Restore the packaged domains in the server pod.
58
+
- Restore applications, libraries, key stores, and such, from the WDT archives.
0 commit comments