Now that you have used enable-secure-admin, try a simple test from the remote
Windows system, something like
asadmin uptime
which is a simpler operation and should help verify whether the remote
asadmin client is communicating correctly with the server.
If that works, but the remote deployment command still does not, look in the
server's server.log file (normally in domains/domain1/logs/server.log) to see
if there are any errors logged there from your failed deployment.
If "asadmin uptime" does not work then there is something else wrong,
probably with the communication. At that point you could define the
environment variable
AS_DEBUG=true
and then try the asadmin command again. You should see detailed logging as
the client attempts to exchange messages with the server.
- Tim
--
[Message sent by forum member 'tjquinn']
View Post: http://forums.java.net/node/806284