If you are using the file registry in the federation repository
to store passwords, you need to change the passwords in the file registry.
About this task
Complete the following steps to change the WebSphere® Application
Server administrator
password stored in the file registry:Procedure
- Using a command prompt, change to the wp_profile_root/bin directory
for a stand-alone server. Change to the dmgr_profile_root/bin directory
for a clustered environment.
- Issue the wsadmin -conntype NONE command
and press Enter.
- Issue the $AdminTask changeFileRegistryAccountPassword
{-userId <wpsadmin_ID> -password <wpsadmin_new_password>} command
and press Enter.
- Issue the $AdminConfig save command
and press Enter.
- Restart the WebSphere_Portal server for
a stand-alone server. Restart the deployment manager for a clustered
environment. For a clustered environment, the nodeagent and Portal
server do not need to be restarted.
- Complete the following steps to update the RunAsRole,
which changes the stored password:
You can change the
password for the WebSphere Application
Server administrator
user ID using the WebSphere Portal Edit
My Profile portlet, the native utilities for the user repository,
such as the LDAP administration interface or the WebSphere Application
Server Administrative
utilities. Regardless of which option you choose, once you have updated
the password, you must also update the RunAsRole for
the PZNScheduler application.
- For a stand-alone server, log on to the WebSphere Integrated Solutions Console with your new password.
For a clustered environment, log on to the deployment manager with
your new password.
- Go to .
- Locate and click the pznscheduler application.
- Click User RunAs Roles under
Detail Properties.
- Select RuleEventRunAsRole and
then click Remove.
- Enter the fully distinguished name (DN) of the WebSphere Application
Server Administrator
in the username field and the new password
in the password field.
- Select RuleEventRunAsRole, and
then click Apply to apply your changes. Synchronize
the nodes, if you have a clustered environment.
- Click OK, save your changes,
and then restart all of the servers in the environment including the
deployment manager, nodeagent, and Portal server.