Thanks, Paul. You inspired me to give it a go again.
Actually, there was one path that I hadn't tried--I was trying to be too fancy. So, I tried the simplest path: c:\temp\wided6_english.fos. For the life of me, I can't figure out how to get the Windows blank space in the path to be read correctly (%20 didn't work).
I also turned logging on, so I got a better error message telling me that it couldn't find the stylesheet. I also used the "stylesheet" param, instead of "fosi" (which I didn't see listed in the PE programmer's guide).
--Alex
In Reply to alex sato:
Hi,
So, I was able to modify the sample script (e3script.bat, e3samples.jar, e3client.jar) to publish to the PE Server using the default stylesheet, but when I try and use our custom FOSI, the server returns the 500 error. I've tried to use all sorts of paths--to no avail
Thanks!
Alex
==============================================================
Here's my text file with the parameters that the e3script.bat file reads:
# Setup our policies (see the javadoc for more information).
setpolicy DELETE_PARTIAL_FILES_POLICY false
setpolicy LOG_THREAD_PREFIX_POLICY true
setpolicy LOG_TIME_DATE_PREFIX_POLICY true
e3 <u>http://Config8518VM0:8080/e3/servlet/e3</u>
basedir .
java com.arbortext.e3.E3AppTest
convert PDF_FORMAT
convert_set FOSI_PARAMETER Wide_D6_English.fos
convert_set INPUT_FORMAT_PARAMETER XML_FORMAT
convert_set OUTPUT_FORMAT_PARAMETER PDF_FORMAT
post <u>\\Plefilesvr01\techpubs\DropOff\AlexSato\temp\build-test\src\deployment_guide.xml</u> <u>\\Plefilesvr01\techpubs\DropOff\AlexSato\temp\build-test\output\deployment_guide.pdf</u>
