Orbit Enterprise Service

The “Enterprise Orbit Service”, short EOS, is a running operating system service and preferably installed and started using an OS administrator account. The used account must have full permission to read and write into the entire Orbit server installation directory. Obviously, read access is required for all resources used by EOS.

A service start, stop and remove are possible from the operating system services management console or as OS administrator by using the Orbit shortcuts within the Orbit installation directory : <Orbit Installation folder>/server/program/bin.

When updating the Orbit Server software or in case of server hardware maintenance it may required to stop and restart the Orbit service. It is obvious that the service needs to be installed before starting and stopped before removing.

When running Orbit in Client/Server setup the EOS service requires file access. The EOS service will read and write all resources and configuration files as requested by Orbit Clients. In this special attention is required regarding file access and permissions for the system user running the service .

When adding resources to EOS, using the EOS console or via Client extensions (e.g. Mobile Mapping runs and projects), the service requires access to the resources. On Windows, mapped network drives are not available to system services, use of (Uniform Naming Convention) is required.

The Orbit toolkit is network-neutral. Connectivity requires an IP-resolve system (such as a DNS). The communication protocol between the Orbit tiers is an Orbit native 'DOX' protocol, requiring only 1 port to be accessible from the outside. Firewalls thus need only to open 1 port to allow remote access to an Orbit server system (in contradiction to standard Java RMI connectivity).

DOX is indeed a proprietary, compressed and binary way to do the communication between Orbit Client and Orbit Server in the most secure, simple and fast way. It has no relation with http or the alikes, but of course runs over tcp/ip.
DOX does not influence any other protocol and cannot be hacked.

By default the EOS service requires TCP port 1100 (DOX for Orbit Desktop Clients - Server) and 1111 (Http (s) for Orbit Web Clients - Server) to operate.

Communication between Client and Server must be available at all times. A client, server or network blocking firewall on these ports will result in run time errors.
The default port configuration can be changed if required. However we do advise to use a reverse proxy instead.

1. Stop EOS service
2. Update Server port configuration :
   <Orbit Installation directory>/server/program/services/
   • DOX : ./dox/service.ini
   • Https(s) : ./http/service.ini
3. Restart EOS service
4. Update Client port configuration :
   • Desktop Clients : <Orbit Installation directory>/client/program/login.ini
   • Web Clients : Change web-address port references, e.g. Publish > Mobile Mapping

It is possible to set the proxy to be used by the EOS service for all outgoing http or https requests.
The default configuration can be changed if required. However we do advise to use the default operating system proxy settings.

EOS service proxy settings are applied on installing the EOS service :
<Orbit Installation directory>/server/program/bin64/ServiceInstall.bat

Set system proxy settings
set JAVA_OPTIONS=...;-Djava.net.useSystemProxies=true

Set other proxy settings
Http requests only :
set JAVA_OPTIONS=...;-Dhttp.proxyHost=0.0.0.0;-Dhttp.proxyPort=0000;-Dhttp.proxyUser=xxx;-Dhttp.proxyPassword=xxx
Http and Https requests :
set JAVA_OPTIONS=...;-Dhttp.proxyHost=0.0.0.0;-Dhttp.proxyPort=0000;-Dhttp.proxyUser=xxx;-Dhttp.proxyPassword=xxx;-Dhttps.proxyHost=0.0.0.0;-Dhttps.proxyPort=0000;-Dhttps.proxyUser=xxx;-Dhttps.proxyPassword=xxx

Orbit desktop client proxy settings are applied on starting the application :
<Orbit Installation directory>/client/program/bin64/OrbitClient.ini

Set other proxy settings
Http and Https requests
... -Xmx0000m -Dhttp.proxyHost=0.0.0.0 -Dhttp.proxyPort=0000 -Dhttps.proxyHost=0.0.0.0 -Dhttps.proxyPort=0000 -splash ...
Make sure to enter the proxy configuration in between the -Xmx and -splash arguments.

As optional server side configuration it is possible to use a dedicated set of configurations for a given service depending the used Orbit desktop client workspace.

All server side service configurations are grouped in the according properties.ini or properties.xml configuration file. It is possible to create a separated “properties_<workspace>” service configuration file for any known Orbit workspace. This duplicated service configuration file makes it possible to set private service configurations for a given workspace.