|
Buck: Thanks a lot. It looks like I finally have a solution. The missing piece was the wfrun.jar file. Thanks. Bill Gasparek, Austin/400 (512) 458 3991 x 11 (512) 458 2951 (fax) -----Original Message----- From: Buck Calabro [mailto:Buck.Calabro@commsoft.net] Sent: Wednesday, October 09, 2002 10:26 AM To: web400@midrange.com Subject: RE: [WEB400] WEB Facing deployment to Tomcat >I am using the file system to export my project. >There is nothing in my "/soccer/servlet/com.ibm.as400ad.runtime" >folder except mri.properties. So you should have a directory structure similar to QIBM UserData WebAsAdv default hosts default_host soccer config RecordBeanSource soccer QDDSSRC dspf1... servlets soccer QDDSSRC dspf1... trace web ClientScript images IBM soccer QDDSSRC dspf1... styles In the servlets directory is WFRun.jar This holds the IBM classes for WebFacing. You need to move this into the Tomcat servlet tree. >I don't understand your comment about the PATH statement >or it's length. Sorry. I have never encountered this problem and am only vaguely remembering the details. If I remember correctly, the Java SDK doesn't install properly if the PATH is too long during the install. Or perhaps it's WDT that doesn't install properly. Anyway, my dim recollection is that you need to record the current PATH setting, strip everything out of it that you can, install Java, reboot. Install WDT, reboot. Install SP5, reboot. --buck _______________________________________________ This is the Web Enabling the AS400 / iSeries (WEB400) mailing list To post a message email: WEB400@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/web400 or email: WEB400-request@midrange.com Before posting, please take a moment to review the archives at http://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.