Update a Domain Configuration

For information about updating the two domain types, see:

Update a Model in Image Domain

You can use the update mii domain job to deploy or undeploy applications, shared libraries and resources to the new domain using a sample application or user-provided artifacts

When you run the update mii domain job, the primordial domain created using the create mii domain job is used as the base domain, and updates are applied to this domain.

Therefore, if you run the update mii domain job for the first time and deploy an application-A in this job, the resulting primordial domain will have application-A deployed. Then, if you run the update mii domain job for the second time and deploy only application-B in the job, the resulting primordial domain will have only application-B deployed. That is, the state on top of the primordial domain is not stored within the image and this allows you to use the source control system to store WebLogic Deploy Tooling (WDT) model to persist any configuration changes on top of the primordial domain.

To know about the primordial domain, see Mutate the Domain Layer in WebLogic Kubernetes Operator documentation.

You can extend your model Yaml file with new definitions using the update mii domain job. For model Yaml file, see About WebLogic Deploy Tooling.

Tip:

To deploy and undeploy an application, see

Tutorial.

To update the WebLogic domain you can provide a WDT model file, a WDT properties file, or an archive file. The archive file can contain applications, libraries, model file along with other artifacts. For the structure of the archive file, see archive file in WebLogic Deploy Tooling documentation.

When you are updating the domain, if you provide a model through the WDT model field and within the archive, the model specified in the field takes precedence.

You can use one of the following sources to specify the location of the archive zip file, domain model Yaml file, and the variables properties file:

File Upload - Uploads the file from the local system.
Object Storage - Uses the pre-authenticated URL on the Object Storage.
Shared File System - Uses the path of the shared file storage.
The NFS shared file system path is mounted on /u01/shared location on the administration host.

Note:
Ensure that you specify the full path of the location of the zip file on the shared file system.

To update a domain and deploy sample applications, shared libraries, and resources to the domain:

Note:

Every time you update a domain, you have to provide a model containing all the resources (applications, libraries, and so on) you want your domain to have. If your domain currently have application-A installed, and you update your domain with a model with application-B, then the domain will have only application-B. If you want to have both applications, you have to use a model with both application-A and application-B.

If you are running the update domain job for the first time, then to deploy the application, you must manually approve new java.io.File java.lang.String and method java.io.File under jenkins/scriptApproval/. See Approve Scripts to View Parameters.

Sign in to the Jenkins console for your domain. See Access the Jenkins Console.
On the Dashboard page, click update mii domain.
Click Build with Parameters.
From Domain_Name, select the domain that you want to update.
Optional: To update the base image, select the Update_Base_Image check box, and then from Base_Image, select the image that you want to apply to the selected domain.
Select the source of the archive zip file from the Archive_Source list.

Note:
In case of files larger than one MB, use the Object Storage or Shared File System option.
For Archive_File_Location, either browse to select the zip file, specify the http pre-authenticated URL, or specify the path of the zip file on the shared file system.
For the structure of the archive file, see archive file in WebLogic Deploy Tooling documentation.
Select the source of the domain model Yaml file from the Domain_Model_Source list.
If the archive zip file contains the domain model Yaml file, you can skip this step.
For Model_File_Location, either browse to select the Yaml file, specify the http pre-authenticated URL, or specify the path of the Yaml on the shared file system. To deploy the sample application, browse and select Yaml file: deploy_sample_app.yaml or specify the path, /u01/shared/scripts/pipeline/samples/deploy_sample_app.yaml.
See model YAML file in WebLogic Deploy Tooling documentation.
Select the source of the variable properties file from the Variable_Source list.
For Variable_File_Location, either browse to select the file, specify the http pre-authenticated URL, or specify the path of the properties file on the shared file system.
Deselect the Rollback_On_Failure check box if you do not want to rollback to the previous working domain image (optional).
If you deselected this check box, you can rollback to the previous image later from the backup.

Note:
The Rollback_On_Failure check box is selected by default.
Click Build to run the Pipeline job.

You can use the WebLogic Server Administration Console to verify that the domain is updated with all the specified parameters. See Access the WebLogic Console.

Update a Domain on a Persistent Volume

The operator creates the domain on a persistent volume when the domain resource is first deployed. Typically, after the initial domain is created, you use tools such as the following for subsequent domain lifecycle operations:

Fusion Middleware Control Console
WebLogic Server Administration Console
WebLogic Remote Console
Product-specific WLST functions
JDeveloper