|
From: Leif M. <lei...@ta...> - 2014-02-12 02:01:54
|
David, The Wrapper also places no restrictions on the directory structure of the application. The integration methods are of course based off of the default to make it easier for most users. With the Wrapper, the main thing is that the working directory is always forced to the location of the Wrapper binary. This is done for application stability as everything will work reliably regardless of how the application is started. There is a way to adjust this after the Wrapper's configuration is loaded but before the JVM is launched. (wrapper.working.dir). There are also some configurable paths at the top of the shell and batch scripts that tell the script where the wrapper binary and then its relative wrapper configuration file are located. Please explain your directory structure and what you would like to do and we will try to help out. Cheers, Leif On Wed, Feb 12, 2014 at 6:25 AM, David Brown <da...@da...> wrote: > Hello, after reading enough of the doco: Method 2 - WrapperStartStopApp > Integration (Windows/Tomcat) I realized that our current tomcat deploy > is radically non-standard and the instructions given at: > > wrapper.tanukisoftware.com/doc/english/integrate-start-stop-win.html > > Will need to be somewhat modified to work with our tomcat (1.7). > > Currently, we are using YAJSW 10.1 and is the target for using JSW. > > YAJSW does not require a strict Tomcat directory structure. > > My question is there an integration method or some way of modifying a > JSW integration method that will successfully install our application > running under Tomcat as a Windows7 service? > > Please advise, David. > |