In general, the Nexus data import can be run on any system capable of running the EnSight client or simple Python applications. The key requirement is that the system have HTTP access to the system running the Nexus server.
A Nexus server can be run in two different ways:
A local Nexus server runs on the same system as the EnSight client and is not accessible from other systems. It can require a significant amount of disk space and in rare situations RAM. Disk space usage scales with the number of images and geometry objects stored in the database. An example database holding approximately 1000 items, including 10 movies and 4 3D geometry objects may use ~300MB of disk space. When idle, the RAM use is around 50MB, but can increase greatly depending on the complexity of the report operations. 1GB of RAM is suggested for a large server.
A remote Nexus server listens on the network to serve requests from other machines. Remote servers benefit most by running multiple server processes to load-balance many simultaneous requests. They frequently have significantly more RAM and disk space due to the need to hold and serve data from more than one user. The extra data load is often facilitated by employing a (remote or local) PostgreSQL database. Because of this, there are increased options for performance optimization.
Details on these configurations can be found here.
A local server can be turned into a remote server by enabling network connectivity to the machine by an appropriate choice of hostname and port in the Nexus Launcher.
The Nexus server has been tested with the following browsers. The system uses advanced HTML5 elements, so the most recent versions of some of these browsers may be required:
Windows Internet Explorer is no longer supported. Please upgrade to Microsoft Edge.