Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents
minLevel1
maxLevel6
outlinefalse
stylenone
typelist
printabletrue

...

Objective

...

  • Provides step-by-step instructions for the end-to-end validation of the Customer Onboarding Process using AC4.

  • Designed to prepare learners for validating a customer onboarding workflow end-to-end

...

    • Verifying credentials

    • Setting network security settings for virtual machines

...

  • Comprehensive step-by-step directions on

...

  • :

    • Downloading and installing prerequisite software

...

      • CLI for Windows

...

      • Chocolatey

...

      • The Helm client from the local directory (

...

Overview

...

      • e.g., kubectl)

    • Important introduction to setting up and configuring databases

      • Creating users

      • Database creation

      • Assignment of privileges

  • Preparation of YAML files according to customer standards

...

AC Cloud Customer Onboarding Process

Process Step

Actions

Sales/Pre-Sales Transition to Managed Services

  • Sales provides client profile to support and MST (Managed Services Team).

  • MST enters client profile in the "AC Cloud Client Profile".

  • MST submits license request to support as per client profile.

  • Support generates license keys per client profile and sends them to MST.

Submit Infra Resource Ticket to Connectria

  • MST compiles environment request details along with a variable script based on "AC Cloud Client Profile".

  • MST member submits for manager approval.

  • MST manager approves with or without changes.

  • MST submits environment request ticket in TRIA Support system to Connectria as per client profile along with variable script file.

Provision Environment

  • Connectria sets up the Azure resources.

  • Connectria sets up 1st and 2nd part of the monitoring via script.

  • MST verifies environment setup per environment checklist.

  • MST updates "AC Cloud Client Environment Info" sheet to include the new customer environments.

Setup Environment - Bastion Host

  • IInstall Azure Client (Azure CLI).

  • Install Kubernetes Client (kubectl).

  • Install MySQL Client WorkBench.

  • Install Filezilla Client.

  • Set up connection info to the MySQL database through WorkBench.

  • Create databases (Backend Log Quartz).

  • Create users.

  • Assign necessary privileges for the user on the databases.

Setup Environment - Adeptia Connect

  • MST sets up MySQL and databases.

  • MST sets up and configures AC.

  • Install Adeptia Connect.

  • Install Adeptia Connect license.

  • Configure email accounts.

  • Configure performance optimizations.

  • Create customer admin account.

  • Install Ingress.

  • Configure Ingress.

  • Configure EAR (encryption at rest).

  • Bind DNS with Ingress external IP.

  • Test the AC with DNS URL.

  • Conduct functionality testing.

Setup Monitoring

  • Install Prometheus/Grafana.

  • Import Adeptia provided dashboards.

  • Configure Grafana alert threshold.

  • Install EFK (Elasticsearch, Fluentd, Kibana).

  • Configure EFK.

  • Install Lens.

Complete Connectria Monitoring Setup

  • Update the ticket with the AC environment URLs.

  • Connectria sets up the remaining monitoring configuration.

Notify Accounts for Billing

  • MST notifies support of the AC Cloud readiness for the customer.

  • Support notifies accounts of the service readiness for the customer.

Invoice Customer

  • Accounts send an invoice to the customer.

Onboard Client

  • MST sends welcome email with access info and reference links.

  • Sales team and Customer Success connect with the customer to know their training needs.

  • Schedule kick-off call.

  • Conduct kick-off call.

  • Discuss environment access, training, VPN services, project timelines, communication, status update, support channels, etc.

Conduct Training

  • Customer Success schedules the training with the customer.

  • Customer Success conducts the training.

...

Customer Environment Setup

Prerequisites

  1. Obtain bastion access from Connectria.

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

...

  1. Download required software from the Google Drive link.

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

...

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

...

  1. Apply Ingress Rules:

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

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

...

Property name

Description

Default value

abpm.services.chatbot.adeptiaai.enable

Set this property to true/yes to enable the Adeptia Assistant feature.

true

abpm.services.chatbot.adeptiaai.endpoint

The API endpoint to interact with the Adeptia Assistant knowledge base.

https://ai.adeptia.com/v1.0

abpm.services.chatbot.adeptiaai.oauth.clientid

The client identifier provided by the third-party application used for authentication.

f3f7e482-0b5a-41f6-aa6b-4b44494be419

abpm.services.chatbot.adeptiaai.oauth.clientsecret

The client secret provided by the third-party application for authentication.

wM48Q~IE-hOKMahzZ7QjoROdOkSumNwQoPOmmaRb

abpm.services.chatbot.adeptiaai.oauth.scope

The scope of the access request. The application's access token will be limited to the granted scopes.

api://f4e48d6e-8d68-460c-9314-d78c0eeafc75/.default

abpm.services.chatbot.adeptiaai.oauth.tokenurl

The token URL issued by the third-party application for authentication.

https://login.microsoftonline.com/45549897-61ee-4cfa-b596-04ca9df5c105/oauth2/v2.0/token

abpm.services.chatbot.adeptiaai.tagname

The tag name bound to the endpoint. 

ProductDocumentation

​Knowledge base “Note: Check this with Adeptia MST Tesm”

Panel
panelIconIdatlassian-note
panelIcon:note:
bgColor#DEEBFF

------------------------------------

MST (used for maintainence & support)

------------------------------------

client id

c0471393-ccd2-4f2b-86d8-39ae8e54b18f

client secret

Jk~8Q~1bbLGhO0aZQuPyQuJEz5U_7xWQVQaoIaq9

------------------------------------

helpbot (used for Adeptia Connect helpbot)

------------------------------------

client id

f3f7e482-0b5a-41f6-aa6b-4b44494be419

client secret

wM48Q~IE-hOKMahzZ7QjoROdOkSumNwQoPOmmaRb

...