Domain on persistent volume (Domain on PV) is an operator domain home source type,
which requires that the domain home exists on a persistent volume. The domain home can be created either manually
or automatically by specifying the section,
domain.spec.configuration.initializeDomainOnPV, in the domain resource YAML file.
The initial domain topology and resources are described using WebLogic Deploy Tooling (WDT) models.
initializeDomainOnPV section provides a one time only domain home initialization.
The operator creates the domain when the domain resource is first deployed. After the domain is created,
this section is ignored. Subsequent domain lifecycle updates must be controlled by
the WebLogic Server Administration Console, the WebLogic Remote Console, WebLogic Scripting Tool (WLST), or other mechanisms. See the High-level use case.
If you are running WebLogic Scripting Tool (WLST) inside a server pod, then please refer to Use kubectl exec in the WLST documentation for very important information related to memory usage.
The typical Domain on PV use case is for an application life cycle that requires persisting changes to the permanent file system.
For example, you might use frameworks like Metadata Services (MDS), Oracle Application Development Framework (ADF), or Oracle Web Services Manager (OWSM). These frameworks require a running domain and the lifecycle operations are persisted to the file system. Typically, after the initial domain is created, you use tools like Fusion Middleware Control, product-specific WLST functions, the WebLogic Server Administration Console, the WebLogic Remote Console, or JDeveloper for lifecycle operations. The changes are managed by these tools; the data and operations cannot be described using WDT models.
WDT models are a convenient and simple alternative to WLST configuration scripts. They compactly define a WebLogic domain using model files, variable properties files, and application archive files. For more information about the model format and its integration, see Usage and Working with WDT Model files. The WDT model format is fully described in the open source, WebLogic Deploy Tooling GitHub project.
When you deploy a Domain on PV domain resource YAML file:
The operator will run a Kubernetes Job, called an introspector job, that:
After the introspector job completes:
You control runtime updates to the WebLogic domain configuration using tools, such as Fusion Middleware Control, product-specific WLST functions, the WebLogic Server Administration Console, the WebLogic Remote Console, or JDeveloper. After the initial domain is created, subsequent updates to the source of the WDT model files or any referenced macros will be ignored.
Some changes may require triggering an introspector job. For example:
After you change the WebLogic domain credential in the WebLogic Server Administration Console, in the domain resource YAML file, you must:
If you change any WebLogic domain topology, such as using the WebLogic Server Administration Console to add clusters or servers, you must:
domain.spec.introspectVersion in the domain resource YAML file.