Deploying to WebSphere

ChuckM

We are looking to migrate to websphere and use OpenDeploy as our deployment tool. Until now we have only used OD for web content (no apps). Could anyone share their success or failure using OD and WebSphere?

Thanks.

rwinterpacht

We're a Websphere shop here at Household, and have been using OD with TeamSite to deploy source code as well as business-managed content. So, we have a projects branch for all the developers, with a 'proj' for developers to deploy (via workflow) to our testing regions. Then they copy editions to a shared workarea 'proj_release', submit and cut an edition, and our infrastructure team will deploy out to production. (They usually run a preview, let developers review the log files, then run the deployment.)
Since most of our projects are on WAS 3.5, we can pick and choose files to deploy, which seems to be working just fine.
But we are now in the process of migrating to WAS 4.0, and using WSAD instead of VAJ, and the deployment completely changes. Basically, all deployments now consist of an EAR file which needs to be packaged up, deployed, then exploded on the target server(s.)
Because TeamSite has limited capabilities for files (like downloading entire directory structures,) developers will typically deploy jar files, property files, and jsps. This makes up contents on the app server. They have the ability to restart the app to pick up changed files.

Hope this helps,
Raf Winterpacht