• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Websphere 6 - rapid deployment for EAR files

 
Sean Sullivan
Ranch Hand
Posts: 427
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Websphere Application Server 6.0 has the ability to monitor a local directory and automatically deploy any EAR that you copy there.

IBM calls this "rapid deployment"

http://publib.boulder.ibm.com/infocenter/ws60help/index.jsp?topic=/com.ibm.etools.wrd.freeform.doc/topics/cwrdrapid.html

This feature is similar to the Deployment Scanner feature in JBoss:

http://www.jboss.org/wiki/Wiki.jsp?page=DeploymentScanner
 
Sean Sullivan
Ranch Hand
Posts: 427
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Question:

I am running WAS 6.0 as a Windows service.

I noticed that IBM's Websphere Rapid Deployment tool (wrd.bat) runs as a separate process.

I need to run the Rapid Deployment process as a Windows service.

Is this possible?

My requirements are:

1) I do not want to manually launch wrd.bat
2) wrd.bat should run even if there are no users logged in

Thanks in advance.
[ December 29, 2004: Message edited by: Sean Sullivan ]
 
Sean Sullivan
Ranch Hand
Posts: 427
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I am still searching for an answer.

Is anybody using IBM's new Rapid Deployment feature?
 
Jeanne Boyarsky
author & internet detective
Marshal
Posts: 34870
369
Eclipse IDE Java VI Editor
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Sean,
I haven't used WAS 6 yet, but it sounds like more of a Windows question anyway. Can you set wrd.bat to run as a startup program?

Logicaly, you could run any batch file the same way WAS itself is starting up. I know you don't manually start WAS or require users to be logged in for that.
 
Roland Barcia
author
Ranch Hand
Posts: 181
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Well, WRD is a hot deployment feature, and hot deployment features are to be used for rapid development and testing. I would be careful not to look at this as a production feature. WRD can monitor multiple directories and supports 2 modes, freeform and autoappinstall. In freeform mode, you can throw loose annotated Java classes (such as Servlets or EJB) and it will generated the EAR and deploy it. In autoappinstall mode, you can throw an EAR in the directory and it will deploy it. You can alos enhance the EAR by adding special deployment info and WRD will automatically create JDBC resources needed.

This type of behavior should not be used in a locked down production or late test environments.
 
Sean Sullivan
Ranch Hand
Posts: 427
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Roland,

Thanks for the reply.

I realize that "Rapid Deployment" is not a production feature.

Here's what I am trying to do: I have a build PC (running Windows) that runs an automated build every night at 2 AM. The full build produces 12 EAR files. When the build is finished, I want to automatically deploy the 12 EAR files to Websphere Application Server 6.

I'd like to have the Application Server running on my build PC. I want the Application Server to automatically deploy the new EAR's when they are built at 2AM.

In a perfect world:

1) the build script will copy the 12 EAR files into c:\autodeploy
2) Websphere Application Server 6.0 would monitor c:\autodeploy
and automatically deploy the EAR's

It is too bad that the "rapid deployment" feature is not integrated into the application server. I'm already running Websphere Application Server 6 as a Windows service and it would be nice if I could check a box in the Websphere admin console to enable Rapid Deployment.

FYI: The "Auto Deploy" feature in Sun's Java Application Server 8 is much easier to use.

http://developers.sun.com/prodtech/appserver/reference/techart/deployment.html#4

In Sun's application server, you just login to the admin console and enable "auto deploy" by selecting a check box.

-Sean

Originally posted by Roland Barcia:
Well, WRD is a hot deployment feature, and hot deployment features are to be used for rapid development and testing. I would be careful not to look at this as a production feature. WRD can monitor multiple directories and supports 2 modes, freeform and autoappinstall. In freeform mode, you can throw loose annotated Java classes (such as Servlets or EJB) and it will generated the EAR and deploy it. In autoappinstall mode, you can throw an EAR in the directory and it will deploy it. You can alos enhance the EAR by adding special deployment info and WRD will automatically create JDBC resources needed.

This type of behavior should not be used in a locked down production or late test environments.


[ December 29, 2004: Message edited by: Sean Sullivan ]

[ December 29, 2004: Message edited by: Sean Sullivan ]
[ December 29, 2004: Message edited by: Sean Sullivan ]
 
Sean Sullivan
Ranch Hand
Posts: 427
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Jeanne Boyarsky:
I haven't used WAS 6 yet, but it sounds like more of a Windows question anyway. Can you set wrd.bat to run as a startup program?


The "Startup" solution assumes that a user will login to the PC. I do not want to login to the PC. I want to run Rapid Deployment as a Windows Service.
 
Roland Barcia
author
Ranch Hand
Posts: 181
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I can see how integrating WRD into the App Server would be helpful in certain scenarios. Although WRD supports various flavors of deployment, from a full fledged EAR file to loose annotated classes and therefore requires extra configuration. Some fo those features can be used stand alone such as the annotation builder.

But you can configure a WRD workspace and run WRD as part of your build using the WRD ANT tasks. I believe you can accomplish what you want that way as well.

You can find information Here:

http://publib.boulder.ibm.com/infocenter/ws60help/index.jsp?topic=/com.ibm.etools.j2eeapp.doc/topics/tantautoappinstall.html
 
paul browne
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Another way of doing it is to script the deploy - see the example at
http://www.firstpartners.net/kb/index.php/Websphere#Auto_Deploy_War_or_Ear_to_Websphere
 
Babji Reddy
Ranch Hand
Posts: 106
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello
If the Websphere is in hot deployment mode, then if just modify a JSP and updated in the folders under the EAR folder, will that be automatically picked up or I have to do a full build and drop the complete EAR again?
Thanks
 
Arun kumar
Greenhorn
Posts: 19
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
this may help you in setting up wrd.bat as a windows service.
http://support.microsoft.com/kb/137890
 
SunilRee Gupta
Greenhorn
Posts: 12
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Sean,

you can use the jacl or jython script to deploy your ear files. here you have to use wsadmin.bat utility.

wsadmin.bat -profileName abc -tracefile abc.txt conntype SOAP -f jython.file

IN IBM Info center you can find out how to write wrote JACL or Jython code to install your application.

Hope this will solve your issue

Warm Regards
Sunil Kumar Gupta
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic