Hello,

Can anyone help me out and confirm whether or not it is possible at this tim
e to use the wsadmin functionality of IBM's websphere ant tasks or even just
 the simple wsadmin.bat to actually install an EAR file to a physically remo
te server?  

It appears that there is a design decision taken in which the temp files for
 the client/server are assumed to be the same and when the server looks for 
a temp file that the client uncompressed or stored on the client's local mac
hine, it's obviously not finding it in it's own server temp dirctory.

Listing the applications or starting/stopping the server works fine but I ge
t error messages about not being able to find temporary files whenever I try
 to do a modifcation via a remote, different physical machine, or a "Java Re
sult 105" error .  

Using WASD 5.1, ANT 1.6.2 on WinXP

I was unable to get ant to call this InstallApplication task from within WAS
D as I got errors regarding IBMJSSEProvider which is apparently resolved by 
using the provided ws_ant.bat file to setup env correctly.

I also tried to use an exec task to launch wsadmin.bat and also recieved sim
ilar warnings about "ear does not exist for installation".    

After setting up a target with wsInstallApp, I get a Java Result 105 Jacl er
ror with an AdminException (presumably about not being able to locate the Ja
cl temp file that is on the client machine instead of the server machine).

Thanks a bunch ahead of time for any help on this!

-- == Damien Joldersma -- djold "at" oah.wa.gov == --
Information Application Specialist
Office of Administrative Hearings
State of Washington

[ Post a follow-up to this message ]

Absolutely, if that machine is in an ND cell.  DMgr takes care of the
transfer.
I do this all the time.  I have one server on my build machine, and use
ws_Ant
and its <wsAdmin> task to install EARs anywhere in the remote cell I want.


If not, I believe you need to transfer the file (typically FTP) then you can
connect to that
remote server and install.

"p00hba" <p00hba.1ecg9r@mail.webservertalk.com> wrote in message
news:p00hba.1ecg9r@mail.webservertalk.com...
>
> Hello,
>
> Can anyone help me out and confirm whether or not it is possible at
> this time to use the wsadmin functionality of IBM's websphere ant tasks
> or even just the simple wsadmin.bat to actually install an EAR file to a
> physically remote server?
>
> It appears that there is a design decision taken in which the temp
> files for the client/server are assumed to be the same and when the
> server looks for a temp file that the client uncompressed or stored on
> the client's local machine, it's obviously not finding it in it's own
> server temp dirctory.
>
> Listing the applications or starting/stopping the server works fine but
> I get error messages about not being able to find temporary files
> whenever I try to do a modifcation via a remote, different physical
> machine, or a "Java Result 105" error .
>
> Using WASD 5.1, ANT 1.6.2 on WinXP
>
> I was unable to get ant to call this InstallApplication task from
> within WASD as I got errors regarding IBMJSSEProvider which is
> apparently resolved by using the provided ws_ant.bat file to setup env
> correctly.
>
> I also tried to use an exec task to launch wsadmin.bat and also
> recieved similar warnings about "ear does not exist for installation".
>
>
> After setting up a target with wsInstallApp, I get a Java Result 105
> Jacl error with an AdminException (presumably about not being able to
> locate the Jacl temp file that is on the client machine instead of the
> server machine).
>
> Thanks a bunch ahead of time for any help on this!
>
> -- == Damien Joldersma -- djold "at" oah.wa.gov == --
> Information Application Specialist
> Office of Administrative Hearings
> State of Washington
>
>
>
> --
> p00hba
> ------------------------------------------------------------------------
> Posted via http://www.webservertalk.com
> ------------------------------------------------------------------------
> View this thread: http://www.webservertalk.com/message437782.html
>

[ Post a follow-up to this message ]