====== Requirements for Orbit Server ===== This page describes the hardware requirements for Orbit's server products, Orbit 3DM Publisher and Orbit 3DM Feature Extraction. * Requirements of the Orbit 3D Mapping Viewer and Plugins, see [[209:technology:platforms:specs_webclient|]]. * Requirements of the Orbit Desktop, see [[209:technology:platforms:specs_desktop|]]. ===== Smart Choices ===== There is are no special hardware requirements for Orbit Mapping solutions. However, make smart choices in relation to * the number of concurrent users * the volume of data to be hosted * the expected performance ===== Operating System ===== [[209:technology:platforms:index|]]. === Orbit 3DM Publisher === Windows Server or Linux on both virtual machine or physical hardware. === Orbit 3DM Feature Extraction === Windows Server only, both virtual machine or physical hardware. ===== Computing Power ===== Depending your expectations, here's a guideline for a single server unit : * Operating System: 64bit * RAM: 16 to 32GB * CPU: Quad-core or higher ===== 3rd Party Software ===== === Orbit 3DM Feature Extraction === For 3DM Feature Extraction only, not applicable for 3DM Publisher. * Adobe Flash \\ Flash 11.0 or higher is required to load the "EOS Console", the server management tool. \\ * Database \\ Client-Server Feature Extraction requires a single central database. \\ Any by Java supported database can be used, see [[209:technology:core:spatial_databases|]]. \\ We advise an opensource and community databases like MySQL or PostgreSQL. ===== Graphics Card ===== No requirements, the Orbit server doesn't use GPU processing. ===== Server Disks & Disk-space ===== No special requirements. \\ An Orbit Server installation is about 500MB, preferably installed on a dedicated partition. Reserve 10 to 50 GB free disk-space. ===== Storage & File Access ===== The Orbit Service requires resource access. \\ Data can be stored on local or network-attached physical storage drives or in the cloud. Orbit provides cloud storage drivers for Microsoft Azure and Amazon S3 blob storage accounts. \\ To support other cloud storage providers, please contact orbit.support@bentley.com. Special attention is required to manage and organize the huge volume of mapping resources, see [[209:technology:platforms:specs_desktop|]]. ===== Network ===== === Orbit 3DM Publisher === For 3DM Publisher only, Web Client to Server connection. For data hosting the Server upload and Client download speed needs to be taken into account. * Minimum server upload speed of 200 Mbps. * Minimum client download speed of 20 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. === Orbit 3DM Feature Extraction === For 3DM Feature Extraction only, Desktop Client to Server connection. 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 | Mbps | Kbps | kB/s | | 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 full resolution panorama image file. Note, this is in ideal conditions if the entire network capacity is available. ===== Internet Access ===== Online access to the Orbit License Service is required, see [[209:technology:core:online_license_activation|]]. ===== Web Server ===== The Orbit Server includes a Web Server supporting Http (Https) and Ws (Wss) communication. \\ For direct Server-WebClient communication, there is no need to install additional services like Microsoft's Internet Information Service, Apache or others. === Https/Wss === Additional configurations and conditions must be met to setup secured communication. A Java KeyStore file derived from Authorization Certificate is required. Certificate submitting and KeyStore file creation must be completed by the company's IT team or hosting partner prior to re-configuring the Orbit Web Server from Http into Https. More information, see * [[https://en.wikipedia.org/wiki/Keystore|Wikipedia Java Keystore]]. * [[209:server:eos:service|]]. === Proxy === Use of proxy is supported, not mandatory. Ensure correct transfer of all Http/Https and Ws/Wss communication! \\ Depending your corporate IT procedures use of port forwarding or (reverse) proxy may be advised or required. However direct communication with the Orbit Service will always be fastest. \\ Setup and management of firewall, port forwarding or proxy server and server domain name belong to the responsibility of the company's IT team or hosting partner. More information, see * [[http://en.wikipedia.org/wiki/Port_forwarding|Wikipedia Port Forwarding]] * [[http://en.wikipedia.org/wiki/Proxy_server|Proxy Server]] === Domain Name === We highly recommend the use of a domain name to refer to the Orbit server. \\ More information, see [[http://simple.wikipedia.org/wiki/Domain_Name_System|Wikipedia Domain Name System]]. ===== Installation Schemes ===== For 3DM Publisher, we advise a maximum of 100 active concurrent users to one server unit. ** Single Storage Unit ** {{ :209:technology:platforms:publisher_01.png?nolink&800 |}} ** Duplicated Storage Units ** {{ :209:technology:platforms:publisher_02.png?nolink&800 |}}