<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns="http://www.w3.org/TR/REC-html40"> <head> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"> <meta name=ProgId content=Word.Document> <meta name=Generator content="Microsoft Word 10"> <meta name=Originator content="Microsoft Word 10"> <link rel=File-List href="cid:filelist.xml@01C4292C.FC81C780">  <style>  </style>  </head> <body lang=EN-US link=blue vlink=purple style='tab-interval:.5in'> <div class=Section1> Tom, I had a similar issue setting up the current release of APLAWS+. My XSL issue was related to missing packages in the ccm.classpath or ccm.webapp files that I created and placed into the /etc/ccm. The xsl files were missing in the /usr/share/ccm/webapps directory. Check your tomcat aplaws log to see what the exact xsl error is then check in the webapps directory to make sure the xsl that failed is actually installed. These files are attached. I did a production install using the quickstart guide found on the APLAWS sourceforge site. Check out the Redhat install guide too:<o:p></o:p> <o:p> </o:p> http://sourceforge.net/project/showfiles.php?group_id=71505&package_id=113522<o:p></o:p> <o:p> </o:p> Here’s my basic install and some gotchas, hope this helps:<o:p></o:p> <o:p> </o:p> My environment:<o:p></o:p> <o:p> </o:p> - Postgres 7.3.4 on Fedora 1.91 – I had to downgrade Postgres 7.4. It appears they have changed the way autocommit works. The driver and database don’t support it, they expect the applications to control commits, so I was getting a transaction error when using the APLAWS+ Postgres driver<o:p></o:p> <o:p> </o:p> - Tomcat 4.1.27 on Windows 2000 will move this to RHEN 3 shortly for dev end staging. There are few gotchas on Windows 2000. Forum is not working for us yet using the “/ccm/portal/forum” relative uri, need to submit a bug. There were some small xsl edits needed, as paths are case sensitive, nothing major yet. Basic install steps follow:<o:p></o:p> <o:p> </o:p> <![if !supportLists]>1) <![endif]>Setup the database and db user using doc. <o:p></o:p> <![if !supportLists]>2) <![endif]>I setup my local environment using the attached setenv script. I did a complete load from command line using:<o:p></o:p> <o:p> </o:p> ccm load-bundle --interactive --name aplaws-plus-complete<o:p></o:p> <o:p> </o:p> <![if !supportLists]>3) <![endif]>Then I initialized Tomcat: <o:p></o:p> <o:p> </o:p> ccm hostinit-bundle --name aplaws-plus-complete --container=tomcat http-port=8080 shutdown-port=8081<o:p></o:p> <o:p> </o:p> There is another gotcha here. The current service install script does not pass JVM memory arguments to the tomcat.exe. This is easy to fix in the script, but to fix after installing the Tomcat service follow these directions:<o:p></o:p> <o:p> </o:p> <![if !supportLists]>a) <![endif]>You can change the parameters in the Windows registry. Path:<o:p></o:p> <o:p> </o:p> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\tomcat-localhost8080\Parameters<o:p></o:p> <o:p> </o:p> b) Change the JVM Option Count value to the new value with the number of parameters it will now have. In my case, I added two parameters –Xms512m and –Xmx512m and it was 11 before so I bumped it to 13.<o:p></o:p> <o:p> </o:p> c) Then I created two more String values. I called the first one I added 'JVM Option Number 12' and the second 'JVM Option Number 13. Then I set the value inside each. The first one I set to '-Xms512m' and the second I set to '-Xmx512m'. Then I restarted Tomcat service and observed when I did big processing the memory limit was now 512 MB, so it worked.<o:p></o:p> <o:p> </o:p> There’s more. I am compiling a step by step journal I will make available after I finish changing the theme and creating my new ccm site. Still figuring that out. Good luck.<o:p></o:p> <o:p> </o:p> --<o:p></o:p> Eric Garza<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> </div> </body> </html>