Best practice deploying applications on WAS -- JAVA400-L

Subject: Best practice deploying applications on WAS
From: magne@xxxxxxxxx
Date: Thu, 24 May 2007 20:08:35 +0000
List-archive: <http://archive.midrange.com/java400-l>
List-help: <mailto:java400-l-request@midrange.com?subject=help>
List-id: Java Programming on and around the iSeries / AS400 <java400-l.midrange.com>
List-post: <mailto:java400-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/java400-l>, <mailto:java400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/java400-l>, <mailto:java400-l-request@midrange.com?subject=unsubscribe>
Sensitivity: Normal

Hi,
is there a best practice developing applications in WebSphere Development
Studio Client 7.0 and deploying on WAS 6.1?
We are developing a number of WebServices (on top of rpg programs in WDSC).
What's best.....creating a project for each webservice and deploy each project
on the WAS 6.1? Or creating one project containing all the webservices and
deploy as one application on WAS 6.1?
What about performance and resource use (one application versus many
applications)?
An advantage with several applications on WAS is that we can stop/start
applications without disturbing all the other webservices.
Any thoughts about this will be appreciated.

Best regards
Magne

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.