Adeptia Connect can be installed on Microsoft Windows and Linux operating system. You can download separate installers of the product for Windows and Linux from Adeptia website.

See the deployment architecture to learn how to install Adeptia Connect in a clustered and non-clustered environment. You may want to verify if you meet the system requirements before you begin to install the product using this installation guide.

Prerequisites for installation

Before you begin to install, you need to make sure that you meet the following prerequisites for seamless deployment of Adeptia Connect within your production and the non-production environment.

The following instructions are laid out to help you ensure that all the prerequisites have been met. Note that these instructions are applicable in case of installing Adeptia Connect on any of the two operating systems, Windows and Linux.

Set up two databases to host Adeptia backend and log database.
The database must be accessible through TCP/IP. The port must be fixed and opened.

Ensure that you have below database permissions for Adeptia backend and log database.

Database	Ensure that you have permission to
MySQL	SELECT, CREATE, DROP, INDEX, ALTER, INSERT, UPDATE, DELETE, REFERENCES, CREATE ROUTINE, ALTER ROUTINE, and EXECUTE for MySQL database.
Oracle	CREATE SESSION, CREATE TABLE, CREATE ANY TABLE, ALTER ANY TABLE, DROP ANY TABLE, DELETE ANY TABLE, SELECT ANY TABLE, UPDATE ANY TABLE, INSERT ANY TABLE, CREATE ANY INDEX, ALTER ANY INDEX, DROP ANY INDEX,CREATE PROCEDURE, CREATE ANY PROCEDURE, ALTER ANY PROCEDURE, DROP ANY PROCEDURE, and EXECUTE ANY PROCEDURE for Oracle database.
MS SQL server	CREATE TABLE, ADD COLUMN, CREATE INDEX, DROP COLUMN, DROP INDEX, DROP TABLE, CREATE PROCEDURE, ALTER PROCEDURE, EXECUTE, and DROP PROCEDURE for SQL Server database.

Use SQL authentication mode in case you are using MS SQL server.
Administrator rights on the server where Adeptia application will be installed.
These below points are applicable only for clustering environment:
- Connect Server nodes must have read/write access to shared drive without login credentials.
- Port 1098 and 21000 to be opened in all Connect Server nodes for communication among them.
Setup and configure an internal and external load balancer as per the deployment diagram.
- The security certificate to be installed on the internal and external load balancer can be either CA-signed or self-signed, however, we recommend a CA-signed certificate.
- Both load balancer should support SSL and SSL must be terminated at load balancer.
HTTP/HTTPS port (80/443) to be opened for an inbound request to the DMZ from the external environment.
In case, you are using default application ports then open the ports for HTTP/HTTPS (8088/8843).
HTTP/HTTPS port (80/443) to be opened for the inbound request to the private network from the DMZ.
In case, you are using default application ports then open the ports for HTTP/HTTPS (8080/8443).
Ensure that the port mentioned in the step 9 and 10 are whitelisted. If they are not whitelisted then Microsoft Windows firewall from all instances must be turned OFF.
One email account with SMTP address details (for example, username, account name, password, SMTP address, SMTP port, and SSL information) used for sending notifications from the Adeptia application.
Whitelist https://connect.adeptia.com in the firewall for incoming and outgoing traffic for using business applications such as Quickbooks, Salesforce, or any other.
Maintain a replica of the database and shared drives you are using. This is necessary if you are setting a disaster recovery environment.

Next step

System requirements

You may be interested in...

What's new

Best practices

Training guides

Frequently asked questions

Adeptia Connect APIs

Adeptia security report

Browser not supported