The WebSphere® Application
Server might not start after installation and shutdown because LDAP settings
are not configured correctly or JVM startup arguments are not specified
properly.
Symptoms
The WebSphere Application
Server does not start after installation and shutdown.
Causes
This problem can occur because of several reasons:
- After you enable Global Security, the WebSphere Application
Server might not be able to start
because LDAP repository settings are not configured correctly. This
condition is more likely to happen if you use Standalone as your default
LDAP repository.
- You specified incorrect JVM startup arguments.
Resolving the problem
To resolve the LDAP problem, you must have valid LDAP users
to enable Global Security.
Important: The WebSphere Application
Server User ID (referred to as
the WebSphere Administrative
Login during Content Engine installation)
must reside within the LDAP Base Distinguished Name that you specified
during Content Engine installation.
To modify your LDAP settings:
- Run \IBM\WebSphere\AppServer\profiles\profile\bin\wsadmin
-conntype NONE.
- At the wsadmin> prompt, enter securityoff.
- Enter exit.
- Restart the application server.
- Start the WebSphere Console
and make the necessary changes to the LDAP security settings.
- In the WebSphere Console,
re-enable Global Security.
To correct the JVM startup arguments, modify or remove the
problematic argument values:
- Open the /IBM/WebSphere/AppServer/profiles/<profile>/config/cells/<cell_name>/nodes/<node_name>/servers/<server_name>/servers.xml file.
- Search for "genericJvmArguments".
- Modify or remove the incorrect argument values.
- Save your changes.