Installation of the 3Diax platform is usually pain free for clients. Following are the required steps for IT administrators during such an installation. Details are listed below the summary:

#	Step	Local	Managed	Cloud
1	Provision hardware	x
2	Install Ubuntu 16.04 LTS	x
3	Open port 443 to incoming traffic	x
4	Create DNS entries to point to provisioned hardware	x
5	Create SSL certificate for DNS entries	x	x
6	Copy SSL certificate and key to the server	x	x
7	Install 3DIAX license file	x
8	Run installation script from Authentise	x
9	Install Authentise Echo	x	x	x
10	Modify Echo configuration file	x	x
11	Create a 3DIAX user	x	x	x
12	Configure Echo to traverse proxies	x	x	x
13	Configure Echo printers	x	x	x

1. Provision Hardware.

The exact hardware specifications you'll need will depend on your use case and the expected load on the system. Please consult with your Authentise sales associate to determine reasonable allocation of CPU, RAM and network-attached disk space

2. Install Ubuntu 16.04 LTS

Ubuntu 16.04 is the latest long-term supported release of Ubuntu, and it is the operating system used for Authentise 3DIAX. Authentise recommends using the "server" distribution of Ubuntu.

3. Open port 443 to incoming traffic

3DIAX performs all communication over SSL and requires port 443 to be opened on any firewalls that control access to the server so that web browsers on the same network can reach the service. Optionally some portions of the UI can be run without SSL over port 80, but it is not recommended

4. Create DNS entries to point to provisioned hardware

3DIAX is a constellation of microservices that communicate with each other via DNS entries. The TLD pattern you use is up to your organization, but the system will need DNS entries for the following:

'users.authentise.<TLD>',

'app.authentise.<TLD>',

'callback.authentise.<TLD>',

'data.authentise.<TLD>',

'erp.authentise.<TLD>',

'estimates.authentise.<TLD>',

'events.authentise.<TLD>',

'gigan.authentise.<TLD>',

'installers.authentise.<TLD>',

'integrations.authentise.<TLD>',

'metrics.authentise.<TLD>',

'models.authentise.<TLD>',

'packing.authentise.<TLD>',

'payment.authentise.<TLD>',

'print.authentise.<TLD>',

'quickslice.authentise.<TLD>',

'quoting.authentise.<TLD>',

'rapidfab.authentise.<TLD>',

'status.authentise.<TLD>',

'syphon.authentise.<TLD>',

'tetra.authentise.<TLD>',

'vision.authentise.<TLD>',

'widget.authentise.<TLD>',

'woodhouse.authentise.<TLD>'

5. Create SSL Certificate

If your organization uses their own Certificate Authority you will need to follow your internal process to get SSL certificates created for the domains in step 4. The certificate should use SAN to provide the various DNS names.

6. Copy SSL certificate and key to the server

The bundled certificate chain and key should be located at /etc/authentise/wildcard.authentise.pem and /etc/authentise/wildcard.authentise.key.pem and should be in the PEM file format

7. Install 3DIAX license file

Authentise will supply you with a license file that you should copy to the server at /root/authentise.license

8. Run Installation Script from Authentise

Authentise will supply you with a script that you should run as root on the server. This script will read the license file and begin the process of downloading and installing the docker image files that are used to run the application. It will also ingest the SSL certificate and key to use with its internal web server

9. Install Authentise Echo

Echo needs to be installed on a windows 10 computer on the same intranet as the printers it will be communicating with. Echo installs as a service that runs in the background as soon as the machine starts up. The service will bind to port 11003 on the loopback IP address (127.0.0.1). It uses this port to communicate with the local configuration utility. Unless your firewall rules are especially draconian you should not need to make any firewall rule changes for this installation. You will need Administrator access to install the software.

10. Modify Echo configuration file

Echo by default is configured to talk to Authentise's multi-tennant cloud. If you are using a local deployment or a managed cloud deployment for 3DIAX you will need to modify the Echo configuration file to communicate with your install of 3DIAX.

11. Create a 3DIAX user

Echo needs the credentials for a 3DIAX user to use when sending data about printers. You must use the Echo configuration utility to provide credentials to Echo. Echo will then create a derivative key from those credentials to use for uploading data.

12. Configure Echo to traverse proxies

If your network requires HTTPS proxies to reach either your local install of 3DIAX or the cloud version of 3DIAX you will need to use the Echo configuration utility to configure communication with those proxies, including their IP address and credentials, if any

13. Configure printers

Once Echo is installed and configured to traverse your network proxies you will need to configure your different printers. This can be done from any web browser and will require the IP address, printer type and printer serial number for any printers you want Echo to communicate with. The IP address should be the address to reach the printer from the computer where Echo is installed. It does not have to be a publicly addressable IP address

Support from Client IT Staff