Content Comparison

...

Download Prerequisites:
- Download required software from Google Drive (ACExpress pre-required software).
Install Software:
- Install all required software on the Bastion.
Install CLI for Windows:
- Open PowerShell and run the following command to install Chocolatey:
  Code Block
  bash
  Copy 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'))

Info

Note: To deploy from your laptop, you must have administrative rights to install the Command Line Interface (CLI), Helm, and Chocolatey (choco).

Typically, the MST team will configure these tools and provide remote access for login and deployment. In this scenario, you will not need to configure the CLI, Helm, and Chocolatey yourself.

...

3. Database Configuration

Database Setup:
- Create the connection from the workbench.
- Verify the DB user provided by Connectria.
- Create the database and users. Example command:
  Copy code
  create user '<<customer_name>>productionuser'@'%' IDENTIFIED BY 'password'; GRANT ALL PRIVILEGES ON <<customer_name>>_backend.* TO '<<customer_name>>productionuser'@'%' WITH GRANT OPTION;

For Example:

acsSittrainingbackend and acsSittraininglogs are the two databases created.
acsSituser is the user created with full privileges over these two databases, and they can grant these privileges to others.

Expand

title	For details click Here

Using MySQL Workbench to create two databases and a user, along with granting that user privileges to the databases. Here's the breakdown:

Database Creation:
- acsSittrainingbackend: A database named acsSittrainingbackend is being created.
- acsSittraininglogs: Another database named acsSittraininglogs is being created.
User Creation:
- A user named acsSituser is being created with the password 'password'. The SQL command for this is:
  Code Block
  create user 'acsSituser'@'%' IDENTIFIED BY 'password';
The @'%' part indicates that this user can connect from any host (% is a wildcard for any IP).
Granting Privileges:
- The user acsSituser is being granted all privileges on the acsSittrainingbackend and acsSittraininglogs databases with the GRANT OPTION. This means the user can perform any action on these databases and also grant the same privileges to other users. The commands used are:
  Code Block
  GRANT ALL PRIVILEGES ON acsSittrainingbackend.* TO 'acsSituser'@'%' WITH GRANT OPTION; GRANT ALL PRIVILEGES ON acsSittraininglogs.* TO 'acsSituser'@'%' WITH GRANT OPTION;
- These commands provide the user acsSituser full control over both databases, including the ability to read, write, update, delete data, and manage the structure.

...

4. YAML and Cluster Setup

Prepare YAML Configuration:
- Prepare the YAML file as per the client’s license and details provided via email.
- How to access YAML file - Currently the YAML file is taken from product team and placed at shared location as shown in image below

Info
Note: Create a copy of ACExpress folder with other name and then edit the YAML files to input details

...

Update YAML File by changing the Env screat to update database and AIMap Backend update

Image Added

Update backend and log details and set static, migration cleanup job to “True”

...

AKS Cluster Setup:
- Add the Bastion IP in the AKS cluster network security settings.

...

5. Helm and Adeptia Connect Installation

Install Helm:
- Install Helm in the Bastion:
  Copy code
  choco install kubernetes-helm
Disable SSL Setting:
- Disable the SSL setting from the database server.

...

Install Adeptia Connect:
- Install Adeptia Connect using Helm (Follow Adeptia documentation) :
  Copy code
  helm install <<release name>> <<adeptia connect helmcharts path>>/ --timeout 10m --debug -n <<namespace>>

...

6. NGINX and Ingress Setup

Install NGINX:
- Download NGINX v9.3.32 and apply the ingress rules:
  Copy code
  kubectl apply -f ingress.yaml

...

7. EAR Setup and License Deployment

Once a secret is created, update the ingress.yaml file to apply the ingress rules.

...

Create EAR Folder:
- Create an EAR folder in the shared path and place the EAR file.

...

Deploy the Latest License:
- Deploy the latest license provided by the support team and restart the license microservice. (Shared Drive)

...

8. Environment Configuration

Configure Client Environment:
- Log in to the environment and configure the following:
  - EAR Settings
  - SMTP Configuration
  - AI MAP Settings
  - Logging Level (Set to Error)
  - Application Password: Default password is changeit.

...

Info

EmailID : donotreply@adeptia.com

Password: (refer) myglu

...

9. Monitoring and Backup Setup

Install EFK:
- Download and install the EFK stack:
  Copy code
  helm install efk efk-stack/ -n logs
- After EFK installation is completed create the secret and apply the ingress rule

...

Install Grafana:
- Download and install Grafana using Helm:
- Extract the zip file and run the below command from the following folder
  Copy code
  helm install grafana-prometheus kube-prometheus-stack -n monitoring

...

Once grafana is installed create the secret and apply the ingress rule
Apply the ingress yaml file with below changes
Remove the s from the HTTP and provide the ingress release name

...

10. Velero Backup Configuration

Velero Backup Configuration:
- Create a namespace velero and a container in Azure Blob Storage.

...

Install Velero using the command:
Copy 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
Create credentials-velero.txt using below lines: (Note: you can get the details from MST Team)

...

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

Use the below command to install the velero

Code Block

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

OR