Win a copy of Terraform in Action this week in the Cloud forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Tim Cooke
  • Campbell Ritchie
  • Paul Clapham
  • Ron McLeod
  • Liutauras Vilda
Sheriffs:
  • Jeanne Boyarsky
  • Rob Spoor
  • Bear Bibeault
Saloon Keepers:
  • Jesse Silverman
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
Bartenders:
  • Piet Souris
  • Al Hobbs
  • salvin francis

WebSphere deployment with Ant

 
Ranch Hand
Posts: 109
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Help :roll: ,
I would like to switch from using the WebSphere 4.0 Admin Console to something like Ant for deployment. Does anyone have an example Ant file to get me started. I would appreciate it.
Thanks,
Mike
 
Ranch Hand
Posts: 217
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Basically, you have to use XMLConfig or WSCP for managing your deployment via command line.
You'd read through the WAS HandBook:
http://publib-b.boulder.ibm.com/Redbooks.nsf/RedbookAbstracts/sg246176.html?Open
For Ant integration, you will just need invoke these 2 utilities from Ant.
 
Mike Jones
Ranch Hand
Posts: 109
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Simon,
Thanks for the link. I guess that needs to be a bookmark. I notice there is a deploytool subdirectory with the Websphere 4.0 install, and ejbdeploy.bat. It looks like the Admin Console probably invokes this .bat file. Couldn't you just use this .bat file from the command line?
Thanks,
Mike
 
Ranch Hand
Posts: 124
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I'm not sure if looking to do a build
for AE or AEs. If its AEs I suggest you
take a peak at SG246134 book. In there
you will see a PiggyBank application that
demonstrates command line build. AEs provides
ejbdeploy.bat to generate the stubs for
your ejbs and then SEAppInstall will do
the actual install under WAS AEs 4.0.1. What
it does is extract your EAR file into the
installedApps subdir of WAS AEs 4.0.1.
Hope that helps,
PJ
 
Simon Song
Ranch Hand
Posts: 217
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
EJBDeploy tool is just like EJBC in WLS to generate EJB Container specific supporting codes.
To deploy your app into WAS, you can use SEAppInstall on AEs. Or more powerful tools like XMLConfig/WSCP on AE.
 
Mike Jones
Ranch Hand
Posts: 109
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Simon,
I am using AEs and it looks like the SG246134 redbook is the appropriate reference. Thanks for the info. I'm getting out of the AEs Admin Console business, and moving to the command line. I've been very disappointed with the admin console application hanging up. I continue to get a "HttpTransport X server socket accept failure: socket closed" error, and hope command line deployment options will bypass this. I did a typical install of AEs on Windows 2000 Professional SP 2. Seems like such basics should work out of the box. J2EE is hard enough with the tools working.
Thanks for the help. I really appreciate it.
Mike
 
Simon Song
Ranch Hand
Posts: 217
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Mike,
Have u upgraded to SP2 for AEs V4?
You can obtain latest fix from:
http://www-1.ibm.com/support/manager.wss?rs=0&rt=3&navkey=1ByProduct&nid=4198&go.x=2&go.y=13
 
Ranch Hand
Posts: 58
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hey guys, while using the ejbdeploy tool from Websphere,
1. I notice that sometimes it does not generate the JNDI binding files that it does when using the GUI tool. Can someone let me know how I can get these JNDI binding files without the GUI tool?
2. How come do the websphere tools ignore my security tags in my ejb-jar.xml descriptor?
thank you in advance.
 
Ranch Hand
Posts: 200
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,
As for the ejbdeploy tool - Ant 1.5 provides a task to invoke this. The task is documented under EJB Tasks in the Optional Tasks list at jakarta
Of course you still need the WAS admin tools installed but you don't need the full version of the Websphere Application Server as far as I'm aware.
Cheers,
Steve
 
Steve Granton
Ranch Hand
Posts: 200
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,
Of course, you could always write Ant tasks to do all the other things you need to do on Websphere. :-)
Cheers,
Steve
 
Greenhorn
Posts: 8
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I tried to make a "Deployed...ear" with ant 1.4 and jdk 1.3.1 calling the java task with EJBDeploy class and all was wrong!!
The rmic -iiop in jdk 1.3 has many bugs that are fixed in the 1.4 version.
My project is bound to jdk 1.3 and my workaround is:
1) call java task with EJBDeploy class with codegen parameter; (jdk 1.3 OK)
2) compile generated source code; (jdk 1.3 OK)
3) call java task with rmic's main class and iiop parameter; (jdk 1.4 OK)
4) compile generated sources for stub/skeleton; (jdk 1.3 OK)
That's very unconventional to use different jdk releases for the same project, but jdk 1.4 is used only to generate source code.
Now that seems to work, but I don't know if there will may be problems related to use of jdk 1.4...
Bye!!!
reply
    Bookmark Topic Watch Topic
  • New Topic