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/2.0/content/userguide/tools/update.md
+16Lines changed: 16 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -30,6 +30,22 @@ When running the tool in WLST online mode, the update operation may require serv
30
30
-`103` - The entire domain needs to be restarted.
31
31
-`104` - The domain changes have been canceled because the changes in the model requires a domain restart and `-cancel_changes_if_restart_required` is specified.
32
32
33
+
### Online update for shared libraries
34
+
35
+
- When updating shared library online, it is recommended to deploy a new version of the library by updating the
36
+
version(s) in the MANIFEST.MF file and update the deployment descriptor of any application that wants to upgrade to
37
+
use the new library, this avoids complicated issues like in-place update of shared
38
+
library.
39
+
40
+
- In-place update of shared library online is not supported - if you only
41
+
update the library contents without updating the version(s) of the library in the MANIFEST.MF file. You will get an error
42
+
from WebLogic Server indicating the library is referenced by applications and cannot be undeployed. You must undeploy
43
+
all applications referencing the shared library first before proceeding; this is the same behavior when using the
44
+
WebLogic Server console. Also, a shared library can potentially be referenced by another
45
+
shared library module which in turns used by other applications, currently there is no capability within
46
+
WebLogic Server to handle automating undeploy and deploy of an application that uses shared library when the library is
47
+
updated in-place.
48
+
33
49
### Using an encrypted model
34
50
35
51
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 `-passphrase_file`.
0 commit comments