|
Problem(Abstract) |
Security settings that are not valid within IBM®
WebSphere® Application Server can prevent the Deployment Manager,
NodeAgent, or Application Server from starting. In this case, the
administrative console also won't start. |
|
|
|
Cause |
The WebSphere Deployment Manager, NodeAgent, or
Application Server might fail to start if:
- The security settings are set improperly within Application
Server
- Changes occur within the operating system or LDAP server configuration
that cause the security settings to become invalid within Application
Server.
|
|
|
Resolving the
problem |
Use the wsadmin batch / script to disable security when
the Deployment Manager, NodeAgent, or Application Server does not start
because of security settings that are not valid within WebSphere.
When WebSphere Deployment Manager is installed
This procedure assumes that there is at least one federated
Application Server, which is the typical case when the Deployment Manager
is installed.
- Ensure that no Java™ processes related to Application Server are
running.
- Disable security for WebSphere:
- cd $WAS_HOME/bin for the Deployment Manager.
- Issue the wsadmin -conntype NONE command. (Issue
./wsadmin.sh -conntype NONE for UNIX®. ) Wait until wsadmin
responds.
- Issue the securityoff command (no space between security
and off).
- Issue the exit command.
- Restart WebSphere. (Start Deployment Manager first, then NodeAgent;
you do not need to restart servers at this point.)
- Log on to the ND administrative console.
- Make the required security setting changes.
- Click Apply, then click Save, then click OK to save the master
configuration and synchronize the change to all nodes.
- Log out of the administrative console.
- Stop Deployment Manager and the NodeAgent.
- Start Deployment Manager, the NodeAgent, (in that order) and then
start any Application Servers.
When a stand-alone Application Server is installed
This procedure assumes that the application server is Base, meaning that
it is NOT federated within a Deployment Manager cell.
- Ensure that no Java processes related to Application Server are
running.
- Disable security for Application Server.
- cd $WAS_HOME/bin for the Application Server.
- Issue the wsadmin -conntype NONE command. (Issue
./wsadmin.sh conntype NONE for UNIX®. ) Wait until wsadmin
responds.
- Issue the securityoff command (no space between security
and off).
- Issue the exit command.
- Restart the Application Server.
- Log on to the administrative console.
- Make the required security setting changes.
- Click Apply, then click Save, then click OK to save the master
configuration.
- Log out of the administrative console.
- Stop the Application Server.
- Start the Application Server.
|
|
|
|
|
Cross Reference information |
Segment |
Product |
Component |
Platform |
Version |
Edition |
Application Servers |
Runtimes for Java Technology |
Java SDK |
|
|
|
Historical Number |
90600
000
672 |
|
Product
Alias/Synonym |
WAS |
|
|
|
|