In general, the entire environment is built on a Linux-based system.
This can be rolled out / installed in three ways:
- VMWare / HyperV-based, OVA-based, ready-to-use appliance/image (Link).
- On our ready-to-use hardware unit (Link)
- On a third-party-provided server (we prefer HP servers) with a bare-metal installation
- Optional: james-do-it.com as a fully hosted system in the cloud.
Once JAMES services are operational, JAMES needs the following ports:
- 443/tcp HTTPs connection from the client to the JAMES server (this includes the Outlook plugin).
- 443/tcp HTTPs connection from and to the kiosk terminals of JAMES Server
- 443/tcp HTTPs Connection from frontdesk clients/workers to JAMES server
- 389/tcp LDAP (Active Directory) connection for AD-based authentication for JAMES users
- 9100/tcp IPP for any type of printer device for paper or plastic badges from JAMES Server to hardware unit
- 25/tcp SMTP for sending notifications from JAMES Server
- Optional: 123/udp NTP for time synchronisation
- Optional: 161/tcp SNMP for monitoring
Apart from the Outlook plug-in, we only transport HTML/JavaScript content.
These are the requirements for a system that is operated on-premise. The only outgoing communication outside the respective organisation that is needed is the SMTP/e-mail gateway for sending invitations and notifications by e-mail.
Systems that offer an online portal need further configuration and intervention in the environment (DMZ, etc.). This must be clarified separately with a system specialist from metaSEC and the end-user IT department.