Replacing the WebSphere Portal administrator user ID

If you change your security configuration, you may need to replace your old IBM® WebSphere® Portal administrator user ID with a new WebSphere Portal administrator user ID.

About this task

Complete the following steps to replace the WebSphere Portal administrator user ID:
Important cluster note: If you are using IBM Web Content Manager within your clustered environment, you must complete these steps on every node in the cluster. If Web Content Manager is not configured, complete these steps only on the primary node.
Note for z/OS: Before you complete this task, you might want to view and print the appropriate worksheet. See WebSphere Portal Enable for zOS worksheets.

Procedure

  1. Create a user in the Manage Users and Groups portlet to replace the current WebSphere Portal administrative user.
  2. Run the following task to replace the old WebSphere Portal administrative user with the new user:
    • Windows: ConfigEngine.bat wp-change-portal-admin-user -DWasPassword=password -DnewAdminId=newadminid -DnewAdminPw=newpassword -DnewAdminGroupId=newadmingroupid from the wp_profile_root\ConfigEngine directory. The -DnewAdminGroupId parameter is required only if you plan to replace the old administrative group ID.
    • AIX®SolarisLinux: ./ConfigEngine.sh wp-change-portal-admin-user -DWasPassword=password -DnewAdminId=newadminid -DnewAdminPw=newpassword -DnewAdminGroupId=newadmingroupid from the wp_profile_root/ConfigEngine directory. The -DnewAdminGroupId parameter is required only if you plan to replace the old administrative group ID.
    • IBM i: ConfigEngine.sh wp-change-portal-admin-user -DWasPassword=password -DnewAdminId=newadminid -DnewAdminPw=newpassword -DnewAdminGroupId=newadmingroupid from the wp_profile_root/ConfigEngine directory. The -DnewAdminGroupId parameter is required only if you plan to replace the old administrative group ID.
    • z/OS®: Complete the following steps:
      1. Start the WebSphere Portal Customization dialog.
      2. From the Portal configuration panel, select Advanced configuration tasks.
      3. Select Security configuration tasks.
      4. Select Change administrative users.
      5. Select Change WebSphere Portal Server administrative user.
      6. Select Define variables.
      7. Generate the customization jobs.
      8. Follow the Customization dialog instructions for submitting the customization jobs. If the job ends abruptly or is canceled without a failure message, remove all log files from the ConfigEngine/log directory before you rerun the job.
    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.
  3. Verify that the task completed successfully. Stop and restart all servers.
  4. Complete the following steps to change the information stored in the SearchAdminUser alias:
    1. Log in to the WebSphere Integrated Solutions Console.
    2. Click Security > Global security.
    3. Under Authentication, click Java Authentication and Authorization Service > J2C authentication data.
    4. Edit the SearchAdminUser alias.
    5. Update the user ID and/or password to match your WebSphere Portal administrator information.
  5. Clustered environments: Synchronize the nodes.
    1. Log on to the Deployment Manager.
    2. Go to System Administration > Nodes.
    3. Select the nodes to synchronize from the list.
    4. Click Full Resynchronize.

What to do next

Notes:
  • If you use an external security manager such as Tivoli® Access Manager, you must manually remove the old administrator user ID from the external security manager.
  • If you set the default portal administrator user ID to be used as the crawler user ID for Portal Search, you need to adapt that crawler user ID accordingly. For more information see the topic about Managing the content sources of a search collection.