...
- Microsoft Server Operating System 2016 and above (2019 recommended)
- Processor operating, 4 core 8 thread minimum (8 core 16 thread recommended for 500+JPD, 12 core 24 thread for 1000+JPD)
- Minimum 16 GB of RAM (24 recommended for 500+JPD, 48 for 1000+JPD)
- Available hard disk space as calculated (see section on “estimating hard disk capacity)
- One Thin-Client user license is required for each Rx-Universe session.
- Virus protection software (such as Symantec, AVG, McAfee, etc) with whitelisting of the following folders: RxUniverse and sites.
- Auto logged in user with sufficient permission to run the following application: Digital Processor, Job Tracker, Remote Processor, E-mail Notification, Devices (Serial and TCP/IP)
- Data storage for the application is done with a combination of ISAM files and either Postgres SQL or MSSQL
Network & Communication
- TCP/IP Lan 100/1000(preferred)
- (LAN) Local Static TCP/IP address is required if interfacing the devices (machines) through a TCP/IP connection.
- To enable remote support by Rx-Universe, or outside access via thin-client, a static IP or DNS must be provided, and port# 5640 must be opened on the router and forwarded to the Rx-Universe server
- Port 6523 and Lens Update: http://omics.dnsalias.com inbound and outbound: If the router blocks both incoming and outgoing connections, “port# 6523” must be open for outgoing connections to allow updates of programs, lens data, manufacturer report specifications, Eyefinity translations, etc.
Rx-Suite: http://omics.dyndns.biz:3333 for updates and license, inbound and outbound.
If VisionWeb is used: sftp.visionweb.com port 22, inbound and outbound.
- If Opticom is used: opticomftp.com port 22, inbound and outbound.
- If Eyefinity is used: echannel.eyefinity.com port 20 and 21, inbound and outbound.
- The lab must provide some method to grant access to the server for the RxUniverse support team, TeamViewer is preferred.
...