Replace the WAS administrator user ID
If you change security configuration, you may need to replace old IBM WebSphere Application Server administrator user ID with a new WAS administrator user ID.
To replace the WAS administrator user ID:
If you use an external security manager such as TivoliAccess Manager, manually remove the old administrator user ID from the external security manager.
- Create a new user in the Manage Users and Groups portlet to replace the current WAS administrative user.
- Run the following task to replace the old WAS administrative user with the new user:
Windows™: ConfigEngine.bat wp-change-was-admin-user -DWasPassword=foo -DnewAdminId=newadminid -DnewAdminPw=newpassword -DnewAdminGroupId=newadmingroupid from the WP_PROFILE/ConfigEngine. The -DnewAdminGroupID parameter is required only if you plan to replace the old administrative group ID.
UNIX™: ./ConfigEngine.sh wp-change-was-admin-user -DWasPassword=foo -DnewAdminId=newadminid -DnewAdminPw=newpassword -DnewAdminGroupId=newadmingroupid from the WP_PROFILE/ConfigEngine. The -DnewAdminGroupID parameter is required only if you plan to replace the old administrative group ID.
i: ConfigEngine.sh wp-change-was-admin-user -DWasPassword=foo -DnewAdminId=newadminid -DnewAdminPw=newpassword -DnewAdminGroupId=newadmingroupid from the WP_PROFILE/ConfigEngine. The -DnewAdminGroupID parameter is required only if you plan to replace the old administrative group ID.Additional parameter for stopped servers: This task verifies the user against a running server instance. If the server is stopped, add the -Dskip.ldap.validation=true parameter to the task to skip the validation.
- Verify that the task completed successfully. In a clustered environment, restart the dmgr, the node agent(s), and WebSphere_Portal servers. In a standalone environment, restart the server1 and WebSphere_Portal servers.
Parent
Update user ID and passwords