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 4 Next »

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

  1. Created Kubernetes Cluster.
  2. Downloaded the values.yaml file and set the required properties. To know more about the properties in values.yaml, click here.
  3. Installed Helm CLI 3.1 or above.
  4. Installed Kubernetes Kubectl CLI.
  5. The required user permissions on the Kubernetes Cluster.
  6. Updated environment settings.
    1. Define database configuration.
    2. Define Secrets configuration. To know how to configure Secrets, click here.

    3. Configure logging and monitoring. 

      Adeptia Connect integrates EFK for logging, and Prometheus and Grafana for monitoring purposes. 
      • If you opt for EFK as a logging tool while deploying Adeptia Connect v4.0, the EFK stack is automatically deployed . In case you go for a tool other than EFK, you need to manually install and configure it. Adeptia support team can help you configure the tool. 
      • If you opt for Prometheus & Grafana as monitoring tools while deploying Adeptia Connect v4.0, you need not set up any external tool for monitoring purposes. In case you go for a tool other than Prometheus & Grafana, you need to manually install and configure it. Adeptia support team can help you configure the tool.
    4. Complete Other configurations.

Kubernetes user permissions

  • Administrator rights on the Kubernetes Cluster.

Define database configuration

  1. Enter the values for properties related with database in values.yaml file.
  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.

    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 or CREATE ANY TABLE, CREATE PROCEDURE or CREATE ANY PROCEDURE, and CREATE VIEW or CREATE ANY VIEW 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.

  5. Use SQL authentication mode in case you are using MS SQL server.

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