Greetings, IWS uses Apache but only as the front end to catch the Web
request. The real work is done in the Integrated Application Server which
is a Liberty based container. The Web Services support creates a java
application that is running in the IAS server, that call the back end RPG
or COBOL program. If you need to make changes to the back end program, if
you dont make any changes to the input output parameters, you dont have to
re-deply for that back end change to go in to effect. If you are making
a Parm update, then yea, you need to stop that specific service (not the
entire web server) delete it and redeploy .
Tim
Tim Rowe, timmr@xxxxxxxxxx
Business Architect Application Development & Systems Management for IBM i
IBM i Development Lab, Rochester, MN
(507) 253-6191 (Tie) 553-6191
http://www-03.ibm.com/systems/power/software/i/are/index.html
----- Original message -----
From: Justin Taylor <JUSTIN@xxxxxxxxxxxxx>
Sent by: "WEB400" <web400-bounces@xxxxxxxxxxxx>
To: "Web Enabling the IBM i (AS/400 and iSeries)" <web400@xxxxxxxxxxxx>
Cc:
Subject: Re: [WEB400] Segment webservices
Date: Fri, Feb 3, 2017 1:00 PM
My concerns so far:
1. Finding anything in a 7000 page joblog is a pain.
2. Most often I deploy an update knowing that it will take effect when
Apache is restarted overnight. Sometimes however, it must be in place
now. That means ending the jobs that have the old copy in memory.
Right now, that means every job for that Apache instance.
Tim, if I'm not mistaken IWS won't do file uploads.
--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing
list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: [1]
http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at [2]
http://archive.midrange.com/web400.
References
Visible links
1.
http://lists.midrange.com/mailman/listinfo/web400
2.
http://archive.midrange.com/web400
midrange.com
