|
Problem(Abstract) |
If you attempt to connect to the deployment manager,
wsadmin.sh script always fails during the first attempt.. The script will
run successfully the second time.
You will see the following errors in the logs:
M2SP:/WebSphere/WS1Cell/DeploymentManager/binÅ date;wsadmin.sh
Fri Aug 20 07:57:23 CEDT 2004
WASX7246E: Cannot establish "SOAP" connection to host "10.192.68.2"
because of an authentication failure. Ensure that u.
Exception message (if any): "ADMN0022E: Access denied for the
getProcessType operation on Server MBean due to insuffici"
WASX7213I: This scripting client is not connected to a server process;
please refer to the log file /WebSphere/WS1Cell/.
WASX7029I: For help, enter: "ÅHelp help"
wsadmin>exit
M2SP:/WebSphere/WS1Cell/DeploymentManager/binÅ date;wsadmin.sh
Fri Aug 20 07:58:14 CEDT 2004
WASX7209I: Connected to process "dmgr" on node WS1 using SOAP connector;
The type of process is: DeploymentManager
WASX7029I: For help, enter: "ÅHelp help"
wsadmin>exit |
|
|
|
Cause |
If you do not include the ID and password as parameters to
the wsadmin.sh command, then you must have the ID and Password in a
properly located soap.client.props file. .
When the first request is sent to DMGR from the executing
wsadmin.sh, DMGR has to validate the ID that submitted the
request and it uses the ID and password from OMVS that
sent the request to DMGR. Once this preliminary check is done, all
future checks against particular roles and actions via node agents or
application servers is done using the data in soap.client.props. |
|
|
Resolving the
problem |
You can resolve the problem by following 1) or 2) below:
- Enter the following command in OMVS: OMVS CU which will change the
user to the WebSphere Application Server admin ID.
- Add the ID and Password to the soap.client.props file
- Execute the wsadmin.sh again
|
|
|
|
|
|
|