Difference between revisions of "Protege4ClientServer"
(→Installation details) |
(→Linux: (checkpoint save)) |
||
| Line 25: | Line 25: | ||
<li><i>/etc/default/protege</i> which is a properties file that configures the init.d script above. The user will have to modify this file before the server will run correctly. | <li><i>/etc/default/protege</i> which is a properties file that configures the init.d script above. The user will have to modify this file before the server will run correctly. | ||
</ul> | </ul> | ||
| + | When the protege server runs, it will write some system logs to the <i>/var/log/protege</i> directory. | ||
| + | <p/> | ||
An example<i>/etc/default/protege</i> file looks like this: | An example<i>/etc/default/protege</i> file looks like this: | ||
<pre> | <pre> | ||
| Line 38: | Line 40: | ||
PID=/var/log/protege/PID | PID=/var/log/protege/PID | ||
</pre> | </pre> | ||
| − | The HOSTNAME property tells the Protege 4 server | + | The HOSTNAME property tells the Protege 4 server how to advertise itself to the world. On a well-configured desktop or server machine that is not hidden by NAT the given setting will probably usually work. If not an IP address works fine. The sandbox user parameter is important and must be changed. This is a user account on the system that is set aside to run the server. Ideally it would be a user account that has minimal access to the system as a whole excepting write access to the <i>/usr/local/protege/data</i> directory. |
==OS X== | ==OS X== | ||
==Windows== | ==Windows== | ||
Revision as of 13:18, September 14, 2012
Introduction
These are some pages under development to document the Protege 4 Server. We are hoping to release an early alpha soon. <p/>
Videos
Here is the first of several videos that I am going to make to demonstrate server features:
Installation details
The purpose of these pages is to allow people to know what is installed by the server installation and what options the user can change. The installation setup is slightly different depending on whether the operating system in question is Linux, OS X or Windows. The Protege Server should run on other platforms as well though we don't yet support its installation. The key things that need to be figured out for an installation to some other platform is obtaining a version of Java that is at least Java 1.6 and determining how to make the Protege 4 Server start at boot time.
Linux
On a linux system the following files and directories are created:
- /usr/local/protege which contains the core server installation in the subdirectory server, the users data files in the subdirectory data and some command line utilities in the bin subdirectory.
- /etc/init.d/protege which is a script that ensures that the Protege server is started at boot time.
- /etc/default/protege which is a properties file that configures the init.d script above. The user will have to modify this file before the server will run correctly.
When the protege server runs, it will write some system logs to the /var/log/protege directory. <p/> An example/etc/default/protege file looks like this:
# # This file goes into /etc/default/protege and holds the default # settings for the Protege Server. # HOSTNAME=`hostname` PROTEGE_SERVER_PREFIX=/usr/local/protege PROTEGE_SANDBOX_USER=tredmond JAVA_CMD=/usr/local/java/jdk1.7.0_06/bin/java PID=/var/log/protege/PID
The HOSTNAME property tells the Protege 4 server how to advertise itself to the world. On a well-configured desktop or server machine that is not hidden by NAT the given setting will probably usually work. If not an IP address works fine. The sandbox user parameter is important and must be changed. This is a user account on the system that is set aside to run the server. Ideally it would be a user account that has minimal access to the system as a whole excepting write access to the /usr/local/protege/data directory.
