Installing EAR from remote server

[Adrian]

Hi Guys,

I am trying to remotely install a websphere application as part of an
automated buld script (ant).
I am using WSAD 5.11 and WAS 5.1

I tried running the wsInstallApp task but that was causing errors. I
investigated further and tried to run the installation from the
command line using the wsadmin tool. I log onto the remote WAS server
using SOAP and I can execute commands against the remote server i.e.
list, uninstallApp, stopserver, startserver etc.
However, when I try to run the install command:
(wsadmin>$AdminAppinstall "c:/build/panoramajar/panoramaear.ear"
{-appname Panor
amaEAR -nodeployejb}

I receive the following error:

com.ibm.websphere.management.exception.AdminException
javax.management.MBeanException
com.ibm.websphere.management.exception.AdminException: ADMA0043E:
C:\Documents a
nd Settings\wasadmin\Local Settings\Temp\2\app23320.ear does not exist
for insta
llation.

What seems to happen is:
1) a temp EAR is created i.e. ..\temp\app23320.ear from my EAR
2) The temp EAR is extracted
3) The temp EAR is deleted
4) wsadmin throws error saying it can't find the temp EAR (which it
had just deleted)

I tried running the install command with all sorts of different
options but that seems to make no difference. I also tried using
installInteractive with the same result.

When I deploy the EAR onto the local server it works fine. I tried
running this on different machines and the result is always the same.
It is definitely a problem with my remote deployment.

I've looked around on google and there are a couple other people with
the same problem. However, there are no solutions.

Any guidance would be greatly appreciated.

Thanks,

Adrian

[userwas]

Adrian,

You could try couple of things.

() check the disk space availabilty on the remote machine and also see if there any restrictions on the size & permissions of directories under C:\Documents and Settings\wasadmin\Local Settings\Temp\2\app23320.ear

() also see if the directories are cleaned up after the install.there is a ptf to ensure that clean up is done.

() try establishing SOAP connection with a -conntype none and after the local install do a $AdminConfig save.

() You could do wsadmin>$AdminAppinstall panoramaear.ear
{-appname PanoramaEAR -nodeployejb}

This means that EAR has to be in /WebSphere/AppServer/bin directory i.e where the wsadmin.bat is located.

() where is the ..\temp\app23320.ear being created on the remote machine or local machine ? Is the EAR on the remote machine ?

The above are to only help you isolate the problem.

Hope it helps !

[Klinchin]

I have the same situation with WAS 5.02. The investigation also revealed
that temp EAR is extracted and then deleted right away before the
deployment. Finally I came up with VBS script (I have w2k on both server and
remote computers) that copies EAR to the remote server computer, launches
wsadmin on the remote computer, and then gets back log files. It is wrong
but workable solution so I am still looking for the correct one.

Thank you,
Igor

Post by Adrian
Hi Guys,
I am trying to remotely install a websphere application as part of an
automated buld script (ant).
I am using WSAD 5.11 and WAS 5.1
I tried running the wsInstallApp task but that was causing errors. I
investigated further and tried to run the installation from the
command line using the wsadmin tool. I log onto the remote WAS server
using SOAP and I can execute commands against the remote server i.e.
list, uninstallApp, stopserver, startserver etc.
(wsadmin>$AdminAppinstall "c:/build/panoramajar/panoramaear.ear"
{-appname Panor
amaEAR -nodeployejb}
com.ibm.websphere.management.exception.AdminException
javax.management.MBeanException
C:\Documents a
nd Settings\wasadmin\Local Settings\Temp\2\app23320.ear does not exist
for insta
llation.
1) a temp EAR is created i.e. ..\temp\app23320.ear from my EAR
2) The temp EAR is extracted
3) The temp EAR is deleted
4) wsadmin throws error saying it can't find the temp EAR (which it
had just deleted)
I tried running the install command with all sorts of different
options but that seems to make no difference. I also tried using
installInteractive with the same result.
When I deploy the EAR onto the local server it works fine. I tried
running this on different machines and the result is always the same.
It is definitely a problem with my remote deployment.
I've looked around on google and there are a couple other people with
the same problem. However, there are no solutions.
Any guidance would be greatly appreciated.
Thanks,
Adrian