====== Requirements for Orbit Server =====

This page describes the hardware requirements for Orbit's server products, Orbit 3DM Publisher and Orbit 3DM Feature Extraction.

The Orbit Mapping solutions do not require special hardware. \\  
However, make smart choices in relation to the volume of data to be hosted and the expected performance.

===== Operating System =====

Windows or Linux. \\
[[196:technology:platforms:index|]].

===== Computing Power  =====

Depending on expectations, type and volume of used resources (e.g. point cloud, imagery, base maps, … ), number of concurrent users and the data network configuration. \\
Here's a guideline for a single server unit :

  * Operating System: 64bit
  * RAM((Required RAM for Orbit 3DM Publisher using Flash Publication can be calculated at about 7.5 MB per concurrent image request.)): 16 to 32GB
  * CPU: Quad-core or higher



===== 3rd Party Software =====

** Flash for 3DM Publisher and 3DM Feature Extraction ** 

Flash 11.0 or higher is required to load the "EOS Console", the server management tool. \\
The EOS Console can be started via HTTP.

** Database for 3DM Feature Extraction ** 

Client-Server Feature Extraction requires a single central database. \\
Any by Java supported database can be used, see [[196:technology:core:spatial_databases|]]. \\
We advise an opensource and community databases like MySQL or PostgreSQL. 

===== Graphics Card =====

No special requirements.

===== Internet Access =====

Online access to the Orbit License Service is required, see [[196:technology:core:online_license_activation|]].

** Web Client to Server connection for 3DM Publisher **

For data hosting the Server upload and Client download speed needs to be taken into account. \\
Minimum internet (or LAN) data-transfer of 200 Mbps.

Web Client - Server communication requires a single port to operate. The default configuration is set to port 1111. \\ Port 80 or 443 are supported, as well use of a Proxy server.

===== Local Area Network =====

** Desktop Client to Server connection for 3DM Feature Extraction **

It is important to have a fast and solid network connection between the Orbit Desktop Clients, their Orbit Server and the data storage. \\
Minimum data-transfer of 1 Gbps. 

Desktop Client-Server communication requires a single port to operate. The default configuration is set to port 1100. 

===== Network speed =====

This is an informative table to indicate the impact of internet and LAN network speed. 

^  Network speed  ^^^^^ ^  Copy time  ^
|  Unit  |  Gbps((Gigabit per seoncd))  |  Mbps((Megbit per second))  |  Kbps((Kilobits per second))  |  kB((Kilobytes per second))  | |  5MB  |  100MB  |
|  1kb  |  1 *10-6  |  1*10-3  |  1  |  0.125  | |  680 min  |  13 600 min  |
|  100kb  |  0.0008  |  0.8  |  800  |  100  | |  51.2 sec  |  17 min  |
|  1mb  |  0.001  | 1 |  1 000  |  125  | |  41 seconds  |  13 min  |
|  100mb  |  0.1  | 100 |  100 000  |  12 500  | |  0.41 sec  |  8.2 sec  |
|  1gb  |  1  | 1 000 |  1 000 0000  |  125 000  | |  0.041 sec  |  0.82 sec  |

Network speed units are expressed in Bits per second, not in Bytes. In the rightmost column, the equivalent copy time is calculated for e.g. a panorama image file. Note, this is in ideal conditions if the entire network capacity is available.


===== Server Disks & Diskspace =====

No special requirements. \\
An Orbit Server installation is about 500MB, preferably installed on a dedicated partition of 10 to 50 GB. 

===== Storage & File Access =====

An Orbit Server requires file access. \\
Special attention is required to manage and organize the huge volume of mapping resources, see [[196:technology:platforms:specs_desktop|]].


===== Installation Schemes  =====

For 3DM Publisher, we advise a maximum of 50 active concurrent users to one server unit. 

** Single Storage Unit ** 

{{  :196:technology:platforms:publisher_01.png?nolink&800  |}}

** Duplicated Storage Unit **

{{  :196:technology:platforms:publisher_02.png?nolink&800  |}}