The Update Domain Tool uses a model, the archive, and WLST to update the configuration of an existing WebLogic Server domain, and to deploy applications and resources into the domain in either WLST online or offline mode. The Update Domain Tool will add or re-configure elements from the
topology section of the model, and deploy applications and resources from the
appDeployments sections, as described in the Deploy Applications Tool.
The Update Domain Tool will only add or update elements in the specified model. It will not attempt to remove any missing elements that were present in a previous model.
Running the Update Domain Tool in WLST offline mode is very similar to running the Create Domain Tool; simply provide the domain location and archive file, and separate model and variable files, if needed. For example:
$ weblogic-deploy\bin\updateDomain.cmd -oracle_home c:\wls12213 -domain_type WLS -domain_home domains\DemoDomain -archive_file DemoDomain.zip -model_file DemoDomain.yaml -variable_file DemoDomain.properties
In WLST online mode, simply add the information on how to connect to the WebLogic Server Administration Server, for example:
$ weblogic-deploy\bin\updateDomain.cmd -oracle_home c:\wls12213 -domain_type WLS -domain_home domains\DemoDomain -archive_file DemoDomain.zip -model_file DemoDomain.yaml -variable_file DemoDomain.properties -admin_url t3://127.0.0.1:7001 -admin_user weblogic
As usual, the tool will prompt for the password (it can also be supplied by piping it to standard input of the tool). To bypass the prompt, you can use one of two options. Store the password in an environment variable, and use the variable name with command-line option
-admin_pass_env. Store the password in a file. Provide the file name with command-line option
Unlike the Create Domain Tool, the full domain home directory is specified, rather than the domain’s parent directory, because the domain has already been established.
The Update Domain Tool will not attempt to recreate or add schemas for the RCU database, for domain types that use RCU.
When running the tool in WLST online mode, the update operation may require server restarts or a domain restart to pick up the changes. The update operation can also encounter situations where it cannot complete its operation until the domain is restarted. To communicate these conditions to scripts that may be calling the Update Domain Tool, the shell scripts have two special, non-zero exit codes to communicate these states:
103- The entire domain needs to be restarted.
104- The domain changes have been canceled because the changes in the model requires a domain restart and
When updating shared library online, it is recommended to deploy a new version of the library by updating the version(s) in the MANIFEST.MF file and update the deployment descriptor of any application that wants to upgrade to use the new library, this avoids complicated issues like in-place update of shared library.
In-place update of shared library online is not supported - if you only update the library contents without updating the version(s) of the library in the MANIFEST.MF file. You will get an error from WebLogic Server indicating the library is referenced by applications and cannot be undeployed. You must undeploy all applications referencing the shared library first before proceeding; this is the same behavior when using the WebLogic Server console. Also, a shared library can potentially be referenced by another shared library module which in turns used by other applications, currently there is no capability within WebLogic Server to handle automating undeploy and deploy of an application that uses shared library when the library is updated in-place.
If the model or variables file contains passwords encrypted with the WDT Encryption tool, decrypt the passwords during create with the
-use_encryption flag on the command line to tell the Update Domain Tool that encryption is being used and to prompt for the encryption passphrase. As with the database passwords, the tool can also read the passphrase from standard input (for example,
stdin) to allow the tool to run without any user input. You can bypass the stdin prompt with two other options. Store the passphrase in an environment variable, and use the environment variable name with command-line option
-passphrase_env. Another option is to create a file containing the passphrase value. Pass this filename with the command-line option
The Update Domain Tool supports the use of multiple models, as described in Using multiple models.
||An alternative to entering the admin password at a prompt. The value is an environment variable name that WDT will use to retrieve the password.|
||An alternative to entering the admin password at a prompt. The value is a the name of a file that contains a password string that the tool will read to retrieve the password.|
||The admin server URL for online update.|
||The admin user name for online update.|
||The path to the archive file to use. If the
||Cancel the changes if the update requires domain restart.|
||Discard all existing domain edits before the update.|
||(Required) The location of the existing domain home.|
||The type of domain. (for example,
||The location of the model file. This can also be specified as a comma-separated list of model locations, where each successive model layers on top of the previous ones.|
||Home directory of the Oracle WebLogic installation. Required if the
||An alternative to entering the encryption passphrase at a prompt. The value is an environment variable name that WDT will use to retrieve the passphrase.|
||An alternative to entering the encryption passphrase at a prompt. The value is a the name of a file with a string value which WDT will read to retrieve the passphrase.|
||If present, write restart information to this directory as
||One or more of the passwords in the model or variables file(s) are encrypted and must be decrypted. Java 8 or later required for this feature.|
||The location of the property file containing the values for variables used in the model. This can also be specified as a comma-separated list of property files, where each successive set of properties layers on top of the previous ones.|