So I'm not clear what the Windows best practice is for per-installation
files for an OS service. Is it to have a user for that service?
Fuseki may be running standalong (a sort of user install) or as a
service (something like service.bat from Tomcat) or as a WAR file in a
(user|service) install.
* User/standalone uses the current directory.
* Service/standalone should use the same as tomcat/service
* tomcat/user should use the users AppData data ?
Tomcat8 docs puts the Tomcat files at c:\tomcat8 but presumable that is
not good practice.
I have come across Windows systems that use "c:/usr/..." just to copy
their Unix version.
C:\Programs and Files\Fuseki is OK for FUSEKI_HOME but not FUSEKI_BASE (??).
Andy
On 13/01/15 18:50, John A. Fereira wrote:
The windows configuration for tomcat is essentially the same as for unix except that
there is a catalina.bat startup script that reads (if it exists) a setenv.bat file in
the tomcat "bin" directory. Of course, you have to use the windows syntax for
setting the environment variable in the setenv.bat file. Here is what mine looks like:
set JAVA_HOME=/usr/local/jdk1.7.0_51
set JAVA_OPTS="-Xmx1024M"
set FUSEKI_HOME=/usr/local/src/jena-fuseki2
-----Original Message-To d----
From: Rob Vesse [mailto:[email protected]]
Sent: Tuesday, January 13, 2015 11:39 AM
To: [email protected]
Subject: Re: Fuseki with a web.xml
Andy
On Windows you'd typically take one of several approaches:
- Have an environment variable (FUSEKI_HOME) that points to the configuration
controlled by the user
- Install to a users AppData folder (for per-user installations) - C:\Users and
Documents\Username\AppData\Local\Fuseki\Config\
- Install to program files (for system installations) - C:\Programs and
Files\Fuseki\Config\
Or possibly a hybrid of 2 and 3 if you install the executables to the system
but each user has their own configuration
Rob
On 13/01/2015 15:57, "Andy Seaborne" <[email protected]> wrote:
Excellent - that's exactly what's needed. It's not something to change
while the server running.
I don't think there is any solution to the "don't control tomcat
installation" problem except a well-known location like /etc/fuseki.
If you don't have access to the tomcat installation, you're unlike to
have access to /etc/defaults or anywhere else in system space.
The choice of /etc/fuseki is fairly arbitrarily modelled on /etc/httpd
/etc/apache2. Some system might prefer /var/lib/fuseki. The default
could be path to find the first existing place on the path.
The place can have symbolic links - important for controlled the disk
location of databases (SSD are good!).
And what should it be for MSWindows? (I'm not a windows server/services
user).
Andy
On 12/01/15 12:21, John A. Fereira wrote:
The startup script for Tomcat (catatalina.sh or catalina.bat) will
check for the existence of a setenv.sh or setenv.bat file in the
$TOMCAT_HOME/bin directory and "source" it if it exists. That's
usually where I put any environment variables that I want to set that
are needed by a web app. It's a good place to add variables used by
the JVM (e.g. for explicitly setting min/max memory or garbage
collection) as well.
-----Original Message-----
From: Andy Seaborne [mailto:[email protected]]
Sent: Monday, January 12, 2015 6:27 AM
To: [email protected]
Subject: Re: Fuseki with a web.xml
On 11/01/15 12:35, Trevor Donaldson wrote:
I did see that /etc/fuseki error when I dropped the war file in
tomcat. I want sure how to change fuseki_base? Any I dead how to get
the war to work in tomcat?
FUSEKI_BASE is an environment variable and can be set in whatever way
you prefer for environment variables. Usually, before invoking Tomcat
... which is tricky when it's a service).
And, in fact, -DFUSEKI_HOME also works 'cos I got bored by the fact
that Java does not have System.setenv.
/etc/fuseki can be a symbolic link.
Andy
On Jan 11, 2015 5:10 AM, "Andy Seaborne" <[email protected]> wrote:
Thanks the links worked. I have the war. The question I have is can
I
overwrite the shiro.ini file? I see the war but everything is
already packaged.
Just to follow up on this point.
The server builds its work area the first time - you can edit these
files. They don't get overwritten next time.
In the WAR version, run once, and shiro.ini file will be in
$FUSEKI_BASE/shiro.ini which is /etc/fuseki/shiro.ini by default.
Andy
