For documentation on the current version, please check Knowledge Base.
Server installation
Java Version
By Default, Orbit places a JRE (Java Runtime Environnement) version in the server folder. Whenever Java is needed by Orbit, a reference is made to this location. We advice to hold on this structure altough one can also use the JRE that already is installed on the Linux OS.
Check for the latest Linux JRE version on the Oracle website :
http://www.oracle.com/technetwork/java/javase/downloads/index.html
There is one JRE version for all Linux distributions. One can choose between a 32 or 64 bit installation and we advice to use the zipped binary distribution. There are multiple Linux distributions and the installers are not properly executed on a minorty of the versions.
Install Orbit as Linux Service
Like on windows, one can install Orbit as a Linux service. We use the “Java Service Wrapper” from Tanuki Software to accomplish this goal.
One can download the necessary files from their site :
http://wrapper.tanukisoftware.com/doc/english/download.jsp
We already selected the necessary files and placed them in the “bin” map of the “server” folder
Use the “service…” scripts for the installation:
- serviceinstall: Install Orbit as service (contains a refence to the “orbitservice” file)
- servicestart: Starts the Orbit service
- servicestop: Stops the Orbit service
- serviceremove: Remove the Orbit service
One must run these script with administrator priviliges.
In linux, a user must run a service (cfr. “system” user in Windows). The user that runs the Orbit service is determined in the “orbitservice” file. Look for the following parameter
RUN_AS_USER=root
By default, the user “root” runs the Orbit service. One can chance this in eg. user “orbit”.
It is recommended to make this user the owner of all the server directories. Following command makes user “orbit” owner of all files and subdirectories in the directory “/home/orbit”
orbit@server:/$ chown -R orbit.orbit /home/orbit
example
Following commands on the console installs and starts the orbitservice. In this exemple, the “server” map is placed in the “/home/orbit” directory.
orbit@server:/$ cd /home/orbit/server/program/bin orbit@server:/home/orbit/server/program/bin$ ./serviceinstall Adding system startup for /etc/init.d/orbitservice ... /etc/rc0.d/K20orbitservice -> ../init.d/orbitservice /etc/rc1.d/K20orbitservice -> ../init.d/orbitservice /etc/rc6.d/K20orbitservice -> ../init.d/orbitservice /etc/rc2.d/S20orbitservice -> ../init.d/orbitservice /etc/rc3.d/S20orbitservice -> ../init.d/orbitservice /etc/rc4.d/S20orbitservice -> ../init.d/orbitservice /etc/rc5.d/S20orbitservice -> ../init.d/orbitservice Service succesfully installed. orbit@server:/home/orbit/server/program/bin$ ./servicestart Starting The Orbit Service... orbit@server:/home/orbit/server/program/bin$ ./orbitservice status The Orbit Service is running (7859).
note: Debian distributions requires the “sudo” prefix. Textual output can differ from the exemple
After executing these commands, an “OrbitService.pid” file will appear in the “bin” folder. This file contains the number of the service.
After starting the service, any client (linux, window, etc…) can connect with the Orbit service via the dox protocol (look for the “login.ini” file in the client part)