Changing the WebSphere Application Server Liberty user ID and password
Procedure to modify the WebSphere Application Server Liberty user ID and password.
To modify the WebSphere Application Server
Liberty
user ID and password, you must update the
wauser_variables.xml configuration file. If you
are modifying the password for the primary WebSphere Application Server
Liberty administrator, then you must also update the
useropts file.
- Browse to the wauser_variables.xml
template, which is located in:
- Dynamic Workload Console
- DWC_home
/usr/servers/dwcServer/configDropins/templates
- master domain manager
- TWA_home
/usr/servers/engineServer/configDropins/templates
- Dynamic Workload Console
-
DWC_home\usr\servers\dwcServer\configDropins\templates
- master domain manager
-
TWA_home\usr\servers\engineServer\configDropins\templates
- Copy the wauser_variables.xml template to a temporary directory.
- Edit the file as necessary, specifying the new password.The contents of the wauser_variables.xml file is as follows:
<server description="wauser_var"> <variable name="user.twsuser.id" value="$(wlpUser)"/> <variable name="user.twsuser.password" value="$(wlpPassword)"/> </server>
where:
- user.twsuser.id
- Is the WebSphere Application Server Liberty user ID.
- user.twsuser.password
- Is the new WebSphere Application Server Liberty password.
- Optionally, create a backup copy of the configuration file in a different directory, if the file is already present.
- Copy the wauser_variables.xml file to the
overrides directory. Changes
are effective immediately.
- Dynamic Workload Console
-
DWC_DATA_dir/usr/servers/dwcServer/configDropins/overrides
- master domain manager
-
TWA_DATA_DIR/usr/servers/engineServer/configDropins/overrides
- Dynamic Workload Console
-
DWC_home\usr\servers\dwcServer\configDropins\overrides
- master domain manager
-
TWA_home\usr\servers\engineServer\configDropins\overrides
- Update the USERNAME and
PASSWORD in the
useropts file on the following workstations:
- on every command-line client that points to your workstation.
- on every fault-tolerant agent in your environment that has an HTTP/HTTPS connection defined in localopts that points to your workstation. The HTTP/HTTPS connection is used to submit a predefined job or job stream.
- in the engine connection parameters on every connected Dynamic Workload Console.