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/config-overrides.md
+6-2Lines changed: 6 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,25 +24,29 @@ Use configuration overrides (also called _situational configuration_) to customi
24
24
You can use overrides to customize domains as they are moved from QA to production, are deployed to different sites, or are even deployed multiple times at the same site.
25
25
26
26
## How do you specify overrides?
27
+
27
28
* Create a Kubernetes configuration map that contains:
28
-
* Override templates (also known as situational configuration templates).
29
+
* Override templates (also known as situational configuration templates), with names and syntax as described in [Override template names and syntax](#override-template-names-and-syntax).
29
30
* A file named `version.txt` that contains the string `2.0`.
30
31
* Set your domain resource `configOverrides` to the name of this configuration map.
31
32
* Create Kubernetes secrets that contain template macro values.
32
33
* Set your domain `configOverrideSecrets` to reference the aforementioned secrets.
33
34
* Stop all running WebLogic server pods in your domain. (See [Server Lifecycle](server-lifecycle.md).)
34
35
* Start or restart your domain. (See [Server Lifecycle](server-lifecycle.md).)
35
36
36
-
For a detailed walk-through of these steps, [Step-by-step guide](#step-by-step-guide).
37
+
For a detailed walk-through of these steps, see [Step-by-step guide](#step-by-step-guide).
37
38
38
39
## How do overrides work during runtime?
40
+
39
41
* When a domain is first deployed, or is restarted after shutting down all WebLogic server pods, the operator will:
40
42
* Resolve any macros in your override templates.
41
43
* Place expanded override templates in the `optconfig` directory located in each WebLogic domain home directory.
42
44
* When the WebLogic Servers start, they will:
43
45
* Automatically load the override files from the `optconfig` directory.
44
46
* Use the override values in the override files instead of the values specified in their `config.xml` or system resource XML files.
45
47
48
+
For a detailed walk-through of the runtime flow, see [Internal design flow](#internal-design-flow).
0 commit comments