|
Hello,
I need to configure the server so that that the external party can commence
testing.
I've seen examples where a ScriptAlias is simply added to the server
configuration in order to simply call the test program (change library
lists, etc).
It's also been suggested to use activation groups but that would need a lot
more work to make sure everything is running only in that activation group.
I don't like the fact that the calls to the production program and the test
program would therefore use the same CGI job, if I understand correctly.
I've seen that sometimes there are several CGI jobs running with the same
name instead of one, I don't know how that works.
Is there any reason I shouldn't just duplicate my server instance and use
this only for testing purposes?
Thanks
--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing
list
To post a message email: WEB400@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/web400.
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.