Content Comparison

Objective

This is designed to prepare the learners in validating a customer onboarding workflow end-to-end by verifying credentials and setting network security settings for virtual machines. Comprehensive step-by-step directions on downloading and installing prerequisite software like CLI for Windows, Chocolatey,the Helm client from the local directory (for example kubectl), etc. It also takes through the important introduction setting up, configuring databases... creating users and database creation.. assignment privileges.... In-order to get prepared ready with YAML files as per the customer standards.

Overview

This document provides step-by-step instructions for the end-to-end validation of the Customer Onboarding Process using AC4.

Prerequisites

1. Obtain bastion access from Connectria.

2. Verify credentials and allow the Adeptia office IP in the VM network security group inbound rules.

3. Download required software from the Google Drive link.

4. Install the CLI for Windows.

Installation Steps

1. Install Choco in PowerShell:

   Code: Set-ExecutionPolicy Bypass -Scope Process -Force; [System.Net.ServicePointManager]::SecurityProtocol = [System.Net.ServicePointManager]::SecurityProtocol -bor 3072; iex ((New-Object System.Net.WebClient).DownloadString('https://community.chocolatey.org/install.ps1'))

2. Create and Configure Database:

   • Create a connection from the workbench.

   • Create the database and users with necessary privileges.

   Code: create user '<<customer_name>>productionuser'@'%' IDENTIFIED BY 'password'; GRANT ALL PRIVILEGES ON <<custome_name>>_backend.* TO '<<customer_name>>productionuser'@'%' WITH GRANT OPTION; GRANT ALL PRIVILEGES ON <<custome_name>>_logs.* TO '<<customer_name>>productionuser'@'%' WITH GRANT OPTION; GRANT SELECT SHOW VIEW ON sic_dev_backend.* TO 'sic_r_user'@'%';

3. Prepare and Install Software:

   • Prepare the YAML file as per client's license and details provided in the email.

   • Add the bastion IP in the AKS cluster network security.

     

   • Install Helm: Code choco install kubernetes-helm

4. Disable SSL Setting from Database Server.

5. Install Adeptia Connect:

   Code: helm install adeptia-connect-nuvem-prod adeptia-connect/adeptia-connect --version 4.3.4 -f nuvem_prod_4_3_04.yaml --timeout 10m --debug -n nuvem-prod

6. Download and Install Nginx:

   • Download Nginx v9.3.32.

     

   • Go to the folder containing tls.key, tls.crt, and star.adeptia.com files and create a secret:

     Code: kubectl create secret tls <<secretname>> --key="tls.key" --cert="tls.crt" --namespace <<namespace>>

   • Update and apply the ingress rules:

     Code: kubectl apply -f ingress.yaml

7. Create EAR Folder and Place EAR File in Shared Path.

8. Deploy Latest License and Restart License Microservice.

9. Provide Ingress IP and Application Domain Name to (Example: Milon) via Ticketing Portal.

Post-Installation Configuration

1. Log in and Perform Initial Setup:

   • Enter the client name and email ID as provided in the client sheet.

   • Enable the following settings:

     • EAR settings

     • SMTP configuration

     • AI MAP

       

     • Adeptia Assistance feature

     • Change logging level to Error for all microservices

     • Enable EAR setting from the application setting (default password: changeit)

       

   • Change environment display name

     

   • Configure mail server parameters:

     Code: emailID: donotreply@adeptia.com Password: refer myglu

     

2. Install EFK Stack:

   • Download EFK.

   • Install EFK:

     Code: helm install efk efk-stack -n logs

3. Install Grafana:

   • Download Grafana.

   • Extract and install Grafana:

     Code: helm install grafana-prometheus kube-prometheus-stack -n monitoring

4. Apply Ingress Rules:

   • Remove s from HTTP and provide the ingress release name in the YAML file.

     

5. Create Namespace for Velero:

   • Create a container in Azure Blob Storage.

     

   • Create credentials-velero.txt:

     Code: AZURE_SUBSCRIPTION_ID= AZURE_TENANT_ID=<<ID>> AZURE_CLIENT_ID=<<ID>> AZURE_CLIENT_SECRET=<<value>> AZURE_RESOURCE_GROUP=<<name>> AZURE_CLOUD_NAME=<<name>>

   • Install Velero:

     Code: velero install --provider azure --plugins velero/velero-plugin-for-microsoft-azure:v1.5.0 --bucket $BLOB_CONTAINER --secret-file <<file path>>/credentials-velero.txt --backup-location-config resourceGroup=$AZURE_BACKUP_RESOURCE_GROUP storageAccount=$AZURE_STORAGE_ACCOUNT_ID subscriptionId=$AZURE_BACKUP_SUBSCRIPTION_ID --use-restic

Adeptia Assistance Configuration

1. Whitelist AKS Cluster Public IP.

2. Update Adeptia Assistant Settings:

   • Navigate to: Setting >> Common >> Adeptia Assistant

     

   • Set the following properties:

     Code: abpm.services.chatbot.adeptiaai.enable = true abpm.services.chatbot.adeptiaai.endpoint = https://ai.adeptia.com/v1.0 abpm.services.chatbot.adeptiaai.oauth.clientid = f3f7e482-0b5a-41f6-aa6b-4b44494be419 abpm.services.chatbot.adeptiaai.oauth.clientsecret = wM48Q~IE-hOKMahzZ7QjoROdOkSumNwQoPOmmaRb abpm.services.chatbot.adeptiaai.oauth.scope = api://f4e48d6e-8d68-460c-9314-d78c0eeafc75/.default abpm.services.chatbot.adeptiaai.oauth.tokenurl = https://login.microsoftonline.com/45549897-61ee-4cfa-b596-04ca9df5c105/oauth2/v2.0/token abpm.services.chatbot.adeptiaai.tagname = ProductDocumentation

Values

​Knowledge base 

3. Enable Adeptia Knowledge Base:

   • Create a database in Milvus with a name starting with an underscore (_) and replacing dashes (-) with underscores (_).

     

4. Create Customer App Registration:

   • Create certification and secrets for Adeptia configuration.

   • Add client ID in the app registration.

   • Add settings in the knowledge base to enable the knowledge base.

     

By following these instructions, you will successfully install and configure the AC4 system, enabling comprehensive customer onboarding and ensuring all necessary features and services are operational.

References: