Overview

Update 243 can be configured to use 'either' HTTPS or TCP/IP protocols.

HTTPS

• Is always used where the database is hosted on a remote cloud server
• Can be used on a Local Server if remote access is required by users however requires additional server software.

TCP/IP

• Is recommended for use on a Local Server where no remote access is required by users (eg: Local Area Network only)

HTTPS Deployment:

• The Systems Administrator will generate a configuration file for each database using a special Server Utility. This file will be sent to each user requiring access

• The Configuration file(s) is then simply imported from a Client Configuration utility into a Remote settings screen

TCP/IP Deployment:

• From the Client Configuration utility, each user manually adds a configuration record using the Client Configuration utility into a Local settings screen

The Client Configuration Utility is only used to record details of Update 243 databases. Update 242 databases are accessed as they are at present