Re: [Wrapper-user] Migration from YAJSW to JSW Method 2

[Leif M. <lei...@ta...>]

David,
I am moving this thread into our support system as you mentioned that it
should be confidential.

Cheers,
Leif


On Thu, Feb 13, 2014 at 12:48 AM, David Brown <da...@da...>wrote:

>  Hello Leif, please find attached a screenshot of our directory structure
> @ tomcat (confidentiality please).
>
> Thanks for the much needed reply.
>
> The dxop.war is mainly our jars and the lib directory is the usual tomcat
> stuff.
>
> There is no catalina.
>
> Not all is clear unless I explain I have a mandate from my boss to explore
> options to resolve our Windows service wrapper issues.
>
> In addition to avoiding YAJSW I am also trying to avoid winrun4j for
> somewhat the same issues: lack of doco and support.
>
> Notwithstanding, I am forced to present both arguments side-by-side.
>
> I understand I can use method 3 but this is similar to winrun4j which
> requires a Java Class that extends an Abstract class whereas JSW requires
> interface implementation.
>
> The ideal presentation would be a nearly config free Windows service
> installation of our app via something like method 2.
>
> If this is not possible then a much more issue free Windows service
> installation using method 3.
>
> To do something similar to method 3 in winrun4j I will have to reread
> everything I have forgotten about Java classloaders.
>
> Please advise, David.
>
>
>
> On 02/11/2014 07:54 PM, Leif Mortenson wrote:
>
>    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.
>>
>
>
>