|
On Wednesday 24 September 2003 21:35, Jeff Crosby wrote: > Ha! I figured out my problem and now have iSeries Access for Web up > and running. > > I used port 2016 for Apache and 2018 for Tomcat. In the > "out-of-process" servlet engine connection for Apache I put port 2016 > instead of 2018. > > Doh! Hi Jeff RTFM <g>. Says me who had lots of head scratching getting it to work because I hadn't given the CFGACCWEB2 command enough time to run - it didn't produce any output in the Java shell for several minutes. What's response like from it, after the initial load? Regards, Martin -- martin@xxxxxxxxxx AIM/Gaim: DBG400dotNet http://www.dbg400.net /"\ DBG/400 - DataBase Generation utilities - AS/400 / iSeries Open \ / Source free test environment tools and others (file/spool/misc) X Debian GNU/Linux | ASCII Ribbon Campaign against HTML mail & news / \
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.