[daisy] Re: Upgrade from 1.5 to 2.0: wrapper issues withlogkit.xml

[Andreas Deininger]

2007/4/6, Robert Kindl <rob at exec.cz>:
> > > IMHO config files for wrapper are little bit broken (including .bat
> files)
> > Could you comment some more on the problems with the bat files?
>
> daisy-startup.bat is calling DaisyRepo.bat and DaisyWiku.bat which got
> renamed.
> Then it's calling ..\..\resources\sleep.bat and
> ..\..\resources\T4ePortPing.exe which doesn't make it in final release at
> all ;-)

I think is is a misunderstanding:
When upgrading from a daisy instance that was got using the
windows-installer, one should not rename c:\Program Files\Daisy-1.5.1
(or whatever the main directory was named), but the directory
c:\Program Files\Daisy-1.5.1\daisyhome. The new DAISY_HOME directory
could then be somenthing like c:\Program Files\Daisy-1.5.1\daisyhome2
(or so). This way, the port ping utilities and everything else are
still in place and functional. I just tried an upgrade from an 1.5.1
instance in that way and the wrapper scripts were working flawflessy
after the upgrade, without any manual intervention. Despite of that
fact, I would like to see the wrapper scripts and config file
distributed with Daisy 2.0 used for starting up daisy as service.

> Main problem with daisy-repository-server-service.bat and
> daisy-repository-server-service.bat
> is that it doesn't find wrapper conf files (it's looking for them in same
> directory as wrapper.exe).

That's correct. These files are templates only, to be copied in the
service directories of the daisy wiki and daisy data wiki dirs (to be
created when updating. We really should add a README.txt (or as
already proposed a DO_NOT_USE_THESE_SCRIPTS.txt) file with the daisy
2.0.1 release.

> Simillary install/uninstall batches also doesn't works ...

For the same reason as described above.

> > It would be helpful if you can provide the fixed versions (e.g. by
> > submitting them to jira: http://issues.cocoondev.org).

Once we added section "using the wrapper scripts" to the upgrade
instructions, everything should be fine.

Regards
Andreas

> Unfortunately I don't really fix them as finally I decide to rather run
> wrapper directly from command line.
>
> > > I changed following three lines in daisy-repository-server-service.conf
> and
> > > wrapper goes fine (obviously with correctly setup environment):
> > >
> > > set.default.DAISY_DATADIR=
>
> This allows for "default" value to be se in environment (while original
> set.DAISY_DATADIR= simply destroys this value).
>
> > > wrapper.java.command=%JAVA_HOME%/bin/java.exe
> > Yep, I stumbled accross that one too.
>
> I have seen this new JIRA issue, thanks :-)
>
> > > wrapper.app.parameter.8="file:/%DAISY_DATADIR%/conf/myconfig.xml"
> > AFAICS the difference is the extra slash after file: ? I didn't notice
> > any problem with this, but if it doesn't do any harm we could add it.
>
> Without slash it gives me following message:
> Unable to convert the supplied path
> [file:D:\Daisy\RepoData/conf/myconfig.xml] to a url.
>
> Rob