WebSphere Application Server Ant Tasks
Barry Hawkins <barry@...
2004-09-08 16:21:54 GMT
Good morning. We are experiencing difficulty with trying to get
our application (a WAR file, no EJB involved) to automatically deploy
(a la the Project Automation book by Mike Clark in the Pragmatic
Programmer Starter Kit series) via Ant against WebSphere Application
Server (WAS). I am on the Ant User Mailing List, and I am subscribed
to Barry Searle's list for IBM's Ant/WAS integration. Barry's title is
"Architect, WebSphere Tools for Automated Production Build and
Deployment". The latest message from Mr. Searle on that list seems to
indicate that IBM doesn't intend to work on improving the existing Ant
tasks for WAS:
I believe that AutomatedDeploy is really essentially suited to
Scripting (not Ant)
since it generally involves iterating through list of apps to deploy,
list of servers, list of settings, etc
and Ant is simply not suited to this (it is the wrong tool, "like
trying to use a hammer to put in screws").
Hence I have completely reimplemented my AutomatedDeply, and it is
entirely a JACL script
with a small Ant invocation wrapper that can be used instead of
invoking the script directly.
it only uses WAS wsAdmin, it does not use any other WAS AntTasks.
So, in light of that less-than-exciting news, I turn to this list.
I was hoping to use a vendor-provided Ant task that exposed an
interface that didn't require learning JACL scripting, but they seem to
be looking at it from the other end of the spectrum, with an Ant task
to serve as a means of invoking a JACL script. I know there are a few
seasoned WAS folks on here, as well as some Ant gurus.
Has anyone used the Ant tasks provided in the wsanttasks.jar file
contained in the lib directory of a WebSphere Application Server
installation? I have found that to even get a simple listing of
applications for a server, I have to run Ant via the ws_ant.bat (or
ws_ant.sh when it's on Unix) provided in the bin directory of the WAS
installation. The IBM script goes through an invocation of yet another
script, setupCmdLine.bat/setupCmdLine.sh, invoking a parade of
environment variables between the two before it finally invokes ant and
processes the build.xml file.
The key task I am attempting to use is wsInstallApp, whose taskdef tag
Any advice or insight would be greatly appreciated.
Barry C. Hawkins
All Things Computed