Orbit Enterprise Service

The “Orbit Enterprise Service” runs as an operating system service and is preferably installed and started using an OS administrator account.

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 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.

Using Orbit in Client/Server requires file access for the Orbit Service.

Running Orbit in Client/Server means that file access is done by the Orbit Server. The Server will read all configured resources and provide them to the Clients.
If required the Orbit Server will save the resource as well.

In an Client Server setup special attention is required for data management and storage location.
When configuring resources in the EOS console or by extensions (e.g. Mobile Mapping data) the Service (!) needs to have access to these resources :

• e.g. on Windows it is required to use the UNC syntax (Uniform Naming Convention), when specifying the file path (location).
  Note that a mapped network drive is not visible to a Service and therefore may never be used.
• Be attention to permissions on shared folders. The “Service user” needs permissions as well.

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.

The Orbit Enterprise Service requires TCP ports 1100 (Orbit Desktop Clients - Server) and 1111 (Orbit Web Clients - Server / Publisher) to operate.

• Client-Server : intranet communication only
• Web clients (like Mobile Mapping Publisher) : both internet and intranet communication possible

The Orbit Enterprice Service is default installed on Ports 1100 and 1111, but if required this can be reconfigured :

1. Stop the Orbit Enterprise Service
2. Configure used ports :
   1. Orbit Desktop Clients : <Orbit Installation directory>/server/program/services/dox/service.ini
   2. Orbit Web Clients : <Orbit Installation directory>/server/program/services/http/service.ini
3. Start the Orbit Enterprise Service
4. Change client configuration :
   1. Orbit Desktop Clients : <Orbit Installation directory>/client/program/login.ini
   2. Orbit Web Clients : Change web-address port references
      • Publish > Mobile Mapping

To use an Orbit Client on a workstation it is required that client-server communication via the given port is possible.
If a firewall on Client, Server or Network is blocking, an exception for in and outgoing communication on this port will be required.

It is possible to configure the proxy server to be used by Orbit for all http/https requests.
If you are about to configure a proxy server, we do advise to use the default operating system proxy settings (system settings). A manual configuration of all proxy settings is possible as well.

The proxy configurations are done in the Orbit service installation file and will be applied on installing the 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

The proxy configurations are done in the Orbit client configuration file and will be applied when starting the Orbit Client.
<Orbit Installation directory>/client/program/bin64/OrbitClient.ini
Make sure to enter the proxy configuration in between the -Xmx and -splash arguments.

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 ...