Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

Before you start deploying, you may want to see if you’re meeting all the prerequisites for deployment. Ensure that you have:

  1. Kubernetes Cluster available with given system requirements.
  2. Database available with given system requirements.
  3. Installed Helm CLI 3.1 or above.
  4. Installed Kubernetes Kubectl CLI.
  5. Administrator rights on the Kubernetes cluster level. 
  6. In case you're using any external vault for Kubernetes Secrets make sure it is able to connect with the Kubernetes Cluster. Define Secrets configuration. To know how to configure Secrets, click here.
  7. Updated environment settings.
    1. Define database configuration.
    2. Configure logging and monitoring
    3. Ensure that you have set othe.

Define database configuration

  1. Enter the values for the following properties related with database in values.yaml file. (contact Ravi)







  2. Set up two databases to host Adeptia backend and log database.
  3. The database must be accessible through TCP/IP. The port must be fixed and opened.
  4. Ensure that you have below database permissions for Adeptia backend and log database. (contact Abhishek or Ajay)

    Database

    Ensure that you have permission to

    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.

  5. Use SQL Authentication mode only.

Other configurations

  1. 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.

  2. 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.

  3. 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).
  4. 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).
  5. Ensure that the port mentioned in the point 13 and 14 are whitelisted. If they are not whitelisted then Microsoft Windows firewall from all instances must be turned OFF. 
  6. 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.
  7. Whitelist https://connect.adeptia.com in the firewall for incoming and outgoing traffic for using business applications such as QuickBooks, Salesforce, or any other. 
  8. Maintain a replica of the database and shared drives you are using. This is necessary if you are setting a disaster recovery environment.
  9. Antivirus application should be configured to whitelist Adeptia Connect binaries.
  • No labels