Orbit desktop Client Installation

One Orbit Client is installed on the same computer as the Orbit Server.
All the Orbit users within the local network can start the Orbit Client via a shortcut that is using a network share to the Orbit Client directory.

This configuration is advised by Orbit and makes it easy to install, maintain and update the Orbit Client Server installation.
Additionally there is no special attention required on data management : “Where will files be stored produced by an Orbit Client?” is no longer an issue.

The disadvantage is that more network traffic is required to start the Orbit Client. The Orbit Client will run on the local computer after transferring Java, Orbit software and configuration from the central Client installation.
However the total start-up data transfer is only 200MB, it can take some time to start the Orbit Client when using a poor network connection (<100Mb).

1. Share the Orbit “client” directory with required permissions. If data will be created in the client directory this should be read and write.
2. Point the client to communicate with the server using the servers' ip address :
   <Orbit installation directory>/client/program/login.ini
   ServerLocation dox://<ipadres>:1100/
3. Check if a firewall on Client or Server isn't preventing communication on port 1100.
   More about the Orbit service and port, see Orbit Enterprise Service.
4. Start the Orbit Client from //<Server IP>/<client share>/program/bin/OrbitClient.exe
   It can be useful to provide a shortcut, do also complete the “Start in:” directory //<Server IP>/<client share>/program/bin/

Instead of one central client on the Orbit server it is possible to start Orbit from a local client copy that will communicate with the Orbit server.

Data, users and all workspaces will be centrally managed but the Orbit Client will run from a local copy.
This Orbit Client Server configuration reduces the network traffic when starting the Orbit Client on a local workstation.
One local client copy can also be used by multiple users e.g. within a 2nd local office network.

The disadvantage is the special attention required when updating Orbit and some additional configurations to manage data produced by an Orbit Client.

1. Start from a well configured Central Client Installation, see above.
   It must be possible to start the central installed Orbit Client on another network computer before installing a local Orbit Client.
2. Copy the “client” directory from the Orbit server installation to the local computer.
3. Start the Orbit Client from the local copy <local copy directory>/client/program/bin/OrbitClient.exe
   It can be useful to provide a shortcut to the local executable on the desktop.
   
   When installing multiple local clients, it is advised to copy the client always to the same location.
   This simplifies the configuration and it will be possible to re-use the same shortcut for all computers.

An Orbit Client can also be configured to use the locally installed Java on your client computer, your own workstation.

Adjust orbitgis.ini (\client\program\bin)
Replace “..\jre\bin\javaw.exe” with your local jre (example “c:/jre6/bin/javaw.exe”), don't forget to use the “ ”