StartServer, StopServer, StartNode, StopNode,
StartManager, StopManager, AddNode, and other administrative commands do
not work properly |
|
Problem(Abstract) |
Why are all of the administrative command scripts in the
$WAS_HOME/bin directory on a single machine working only for a
specific node? |
|
|
|
Resolving the
problem |
Is the WAS_USER_SCRIPT defined for the command
prompt or terminal that you see in the issue?
- To check this in Windows®, issue the following command:
echo %WAS_USER_SCRIPT%
This command should not return anything if this variable is not set.
- To check this in Unix®, issue the following command:
$WAS_USER_SCRIPT
This command should not return anything if this variable is not set.
If WAS_USER_SCRIPT is defined to be a specific path, remove that defined
parameter and try to rerun the questionable scripts.
- On Windows systems, use the following command:
set WAS_USER_SCRIPT=
- In Unix systems, use the following command:
export WAS_USER_SCRIPT=""
If WAS_USER_SCRIPT is not defined, run one of the administrative commands
without any parameters to see if the help menu is returned. If no menu is
returned, the Java™ environment is not initialized properly and the JDK™
cannot be found. Check the setupCmdLine file to verify that the Java
location, JAVA_HOME is correct. If the menu is correctly returned,
make sure the parameters are set correctly.
If these steps do not resolve the problem. call IBM support at
1-800-IBM-SERV. Have the following information ready for the IBM
representative to analyze:
- Pipe the information (produced from trying to run the
commands) to a file
- The steps required to reproduce the problem
|
|
|
|
|
Cross Reference information |
Segment |
Product |
Component |
Platform |
Version |
Edition |
Application Servers |
Runtimes for Java Technology |
Java SDK |
|
|
|
|
|
|