|
From: Barry M. <bm...@gm...> - 2007-06-04 14:35:51
|
This didn't seem to work. I have a wrapper.conf with only #include %WRAPPER_CONF_INCLUDE% and I run the NT Service install bat file as: InstallService.bat .\wrapper.conf set.WRAPPER_CONF_INCLUDE=..\agent\conf\wrapper.conf When I do this, it looks like it is never reading the agent\conf\wrapper.conf file at all since a service called wrapper is installed instead of the name I am giving it in the application conf file. On 6/4/07, Leif Mortenson <le...@ta...> wrote: > > Barry, > > When running wrapper.exe directly you have the choice to specify > > configuration properties on the command line. Is it possible to > > install a windows service using the Install bat file and to specify > > configuration properties to set when it starts? > Anything placed on the command line when the service in installed > will be placed into the registry and used again when the service is > started. > > > > What I would like to do is have a common conf file that is called > > first which would then include another application specific conf file > > that is pointed to by a configuration property specified when the > > wrapper.exe service is called. Is this possible? > Try this. > Start by specifying the following to include your config file from the > primary wrapper.conf: > --- > #include %WRAPPER_CONF_INCLUDE% > --- > > Then put the following on the command line when installing the service: > wrapper.exe -i ..\conf\wrapper.conf set.WRAPPER_CONF_INCLUDE=../myapp.conf > > Cheers, > Leif > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > |