|
Problem(Abstract) |
Environment:
Node A - Dmgr/Base - Linux® - 5.1.1.4
Node B - Base (Only Scripting options selected)- Windows® XP - 5.1.1.4
Wsadmin client was executed on Node B to connect to the remote deployment
manger on Node A to update an EAR file.
Recreate Scenarios:
Installed Base IBM® WebSphere® Application Server with custom options -
only selected package on Node B during the install.
Administration
Scripting Administration
Running the wsadmin client scripting tool to connect to the remote
deployment manager to deploy an EAR file, failed to find the class
(BindingChoices) and client received the following exception at command
prompt.
C:\WAS_51\WebSphere\AppServer\bin>wsadmin -conntype SOAP -host
waslinux21 -port 8879 -user ldap -password xxxxxxxx
WASX7209I: Connected to process "dmgr" on node waslinux21Manager using
SOAP connector; The type of process is: DeploymentManager
WASX7029I: For help, enter: "$Help help"
wsadmin>$AdminApp install c:/tmp/ear/HelloWord.ear {-update -appname
HelloWord}
WASX7015E: Exception running command: "$AdminApp install
c:/tmp/ear/HelloWord.ear {-update -appname HelloWord}"; exception in
formation: com.ibm.websphere.management.exception.ConnectorException
org.apache.soap.SOAPException: [SOAPException:
faultCode=SOAP-ENV:Client;
msg=com.ibm.ws.webservices.deploy.BindingChoices; t
argetException=java.lang.IllegalArgumentException:
com.ibm.ws.webservices.deploy.BindingChoices] |
|
|
|
Cause |
Wsadmin client scripting package does not install the
webservices.jar on Node B which is causing the failure. |
|
|
Resolving the
problem |
Analysis shows that this class exists in webservices.jar
and this JAR file is not installed when installing the scripting package.
Workaround:
1. Copy the webservices.jar from (Node A) standard WAS_HOME/lib to
scripting install root on Node B.
2. Run the wsadmin client on Node B again to deploy the EAR. |
|
|