Repairing the WebSphere Application Server Network Deployment registry after switching to LDAP

If you have switched from an internal registry to a Lightweight Directory Access Protocol (LDAP) user registry without using the documented procedure, "Switching to an LDAP user registry," you might be unable to stop IBM® WebSphere® Application Server processes.

Symptoms

You can not stop WebSphere Application Server Network Deployment when using either the MetadataServer.sh stop command or the stopServer.sh command.

Environment

Optional. Describe any environmental details that are not already in the title or short description.

Resolving the problem

Repair the WebSphere Application Server registry:
  1. Kill the WebSphere Application Server processes.
  2. Use sudo vi to edit the following settings in the file, /opt/IBM/WebSphere/AppServer/profiles/InfoSphere/config/cells/hostNameNode01Cell/security.xml:
    1. Change the first instance of enabled="true" to "false"
    2. Change the first instance of appEnabled="true" to "false"
  3. Start WebSphere Application Server.
  4. Log into the WebSphere Application Server administrative console by using wasadmin.
    Note: Because of your modifications to security.xml in step 2, the console does not prompt you for a password.
  5. In Security > Global Security, click Configure and enter the following information:
    1. Set Primary administrator user name to wasadmin.
    2. Select Server identity that is stored in the repository and set the user ID to wasadmin and type the password.
  6. Click Apply and then OK. This returns you to the Global Security page.
  7. Select the check boxes: Enable administrative security and Enable application security
  8. Clear the Java 2 security check box.
  9. Click Apply. A message appears on the top of the form. Click the Save link inside the message.
  10. Log out of the WebSphere Application Server administrative console.
  11. Test that you can now stop WebSphere Application Server smoothly:
    1. Stop WebSphere Application Server.
      Note: WebSphere Application Server should be able to stop without errors, but you must still do the following steps to ensure the that the problem is fixed.
    2. Start WebSphere Application Server.
    3. Stop WebSphere Application Server. It should be able to stop without errors.