|
You can start was with this command. Command . . . . . . . . . . . : CALL PGM(QWAS6/QWASSTRSVR) PARM('-profilePat h' '/QIBM/UserData/WebSphere/AppServer/V6/Base/profiles/WAS60SVR' '-server' 'WAS Where WAS60SVR is my instance name and qwas6 is the subsystem . It all depends on your configuration, if the web-app is isolated to and instance you could do it that way. Hope this helps -----Original Message----- From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Michael Soucy Sent: Monday, May 15, 2006 10:47 PM To: Websphere e-list Subject: [WDSCI-L] Stopping/Starting a Web Application in batch Does anyone out there use a change management system to promote changes to your web application? I'm looking for some help in this area. In my shop we are using Softlanding's Turnover to monitor for changes to our Webfaced applications. The process for promoting the changes into production is quite simple except for one problem. I need to find a way to stop and then restart the wefaced application that is running on WAS 6.0 in order for my changes to take effect. The process needs to be able to run in batch so I can re-publish my changes using Turnover. Does anyone out there have any sample CL or QShell script that they would be willing to share that would help me accomplish this? The process need to be able to run in batch in order for this to work. Any help would be greatly appreciated. Sincerely, Michael Soucy michaelsoucy@xxxxxxxxxxx -- This is the Websphere Development Studio Client for iSeries (WDSCI-L) mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/wdsci-l or email: WDSCI-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/wdsci-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.