Re: Installing a web change (was: importing a rpg orsqlrpg)

Joe,

Not to tout my own product, but let me tell you how we do it.  You might be
able to do it manually.

Once a web application is installed, virtually any change can be
"hot-deployed" by just copying in the changed files.  WebSphere will pick
up the changes and automatically restart.  Exceptions are mainly when
creating new EJB's.  New/changed servlets or JSP's are a piece of cake,
even most changes to the web.xml.  IBM has documentation for each type of
change being made what has to be done.

When using TurnOver in WDSC, TurnOver automatically keeps track of all of
the files being changed.  When you tweak something in WebFacing, and
suddenly 100 files were changed, TurnOver knows about every one of them.
You can then just drag n' drop those changes to your TurnOver worklist and
promote them.  The same promotion could include RPG/DSPF/PF/LF, doesn't
have to be just web objects.  This would also allow you to back out the
changes in tandem if necessary.

If you want to, you could even use the WebSphere commands we developed to
stop and start the server or your application as part of the promotion, but
that is usually not necessary.

Anyway, you could do all of the manually.  The hardest part would be
identifying what you changed, especially with WebFacing since so much is
done invisibly.

Hope this helps.

Mark



      To:   "Websphere Development Studio Client for iSeries"
<wdsci-l@xxxxxxxxxxxx>
      cc:
      bcc:
      Subject:    [WDSCI-L] Re: importing a rpg or sqlrpg
"Joe Pluta" <joepluta@xxxxxxxxxxxxxxxxx>
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
03/19/2003 12:15 PM CST
Please respond to Websphere Development Studio Client for iSeries
<font size=-1></font>





















Buck (and/or anybody else with experience on this):

Is it your experience that the sequence of events for tweaking a WebFaced
screen is:

1. Make a tweaks to the WebFaced JSP in WDSC
2. Export the EAR file containing the entire application
3. Stop WebSphere
4. Uninstall the old EAR file
5. Install the newly exported EAR file
6. Restart WebSphere
7. Test the application

I'm not even doing webfacing, just some simple servlets using WDSC, and I'm
finding that most of my time is spent stopping and restarting websphere and
uninstalling/reinstalling the EAR file.  Is this what you're finding?

Joe

_______________________________________________
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.