DataSoft Systems Bangladesh Limited

bKash AML360 R2
Deployment process
Version 0.1.0
Revision History

Version Date of Prepared By Reviewed By List of changes from

No Release Previous Version
(dd/mm/yyyy)
0.1.0 12.28.2020 Ahsiqur Rahman Ashiful Islam

List of Approvers

Approved By Role Signature / Date of

Approval
Moniruzzaman Khan

Project Manager

Ashiful Islam
Associate Project Manager
 Table of Content
1 INTRODUCTION ........................................................................................................................................... 4

1.1PROJECT TOP VIEW.......................................................................................................................................... 4

1.2 PROJECT SCOPE, OBJECTIVES AND BRIEF DESCRIPTION ............................................................................. 4
1.3 PROJECT ENVIRONMENT ................................................................................................................................. 4
1.4 TARGET IMPLEMENTATION ENVIRONMENT .................................................................................................. 5
1.5 PROJECT DELIVERABLES ................................................................................................................................ 5
1.6REFERENCE MATERIAL.................................................................................................................................... 5
1.7DEFINITIONS, ACRONYMS, AND TERMINOLOGY ............................................................................................ 5

2 DEPLOYMENT PROCESS ........................................................................................................................... 5

2.1 TERMINOLOGIES: ......................................................................................................................................... 5

2.2 PROCESS FLOW:............................................................................................................................................ 7
2.2.1 STEP 1: RUN THE NGINX, START FRONT-END SERVICE: ........................................................................... 7
2.2.2 STEP 2 -VERIFY THE NGINX AND FRONT-END SERVICE: ............................................................................. 8
2.2.3 STEP 3 - SETUP AUTHORIZATION SERVICE: ................................................................................................ 8
2.2.4 STEP 4 - VERIFY AUTHORIZATION SERVICE:............................................................................................... 9
2.2.5 STEP 5 - SETUP WEB BACKEND SERVICE: ................................................................................................. 11
2.2.6 STEP 6 - VERIFY WEB BACKEND SERVICE STATE ..................................................................................... 12
2.2.7 STEP 7 - SETUP APP BACKEND SERVICE STATE: ....................................................................................... 13
2.2.8 STEP 8 - VERIFY APP BACKEND SERVICE STATE: ..................................................................................... 14
2.2.9 STEP 9 - VERIFY ALL SERVICES STATE: .................................................................................................... 15
2.3 DB RELATED PROCESS: .............................................................................................................................. 16
2.4 ROLLBACK PLAN ......................................................................................................................................... 16
1 Introduction
1.1Project Top View

[Fill up the table here, to provide a top view of the project]

Project Id PRD-DSBL-15101
Project Name bKash AML 360
Client Organization (name & address) BKash
Client Contact (Name &Contact Person,
Address, Phone, Fax)

Project Type [] Development

[ ] Enhancement
[ ] Maintenance/ Support
[ ] Any Other
Application Area Description
(e.g., Industry and functional areas)
Platform/ Technology Description
(Operating system, database, language,
front-end, etc.)
Commercial Terms [] Time & Material
[ ] Turn Key
[ ] Internally sponsored
Total Estimated Size (Unit)
Total Estimated Effort (Unit)
Start Date 25/12/2020
End Date
Total Estimated Calendar Days
Total Budget

1.2 Project Scope, Objectives and Brief Description

[Give a brief description of the project type, project objectives, nature of work, project characteristics,
relationship of this project to other projects and description of the client.]

Provide a reference to the proposal and contract.

Include scope of the project – this includes

 What is included
 What is excluded
 Service levels]

1.3 Project Environment

[Describe the development environment, maintenance environment in terms of hardware
configuration, operating systems and other software systems used to develop and maintain the system]
1.4 Target Implementation Environment
[Describe the environment where the system will be finally installed and operated, in terms of
hardware configuration, operating systems and other software systems being run concurrently]

1.5 Project Deliverables

[Specify the items to be delivered, delivery location, etc. Typical deliverables are Requirements
Analysis document, High-Level Design document, Source-code, User and Operations Manual, etc.]

Sl No Deliverable Media Qty Committed Date

1.6Reference Material
[List all documents and other sources of information referenced in this plan. For each referred
material, specify the version no and location. Examples of documents referred to are Contract,
Proposals, Project's Process, Project Kickoff Plan, etc.]

1.7Definitions, Acronyms, and Terminology

[Provide the definitions, acronyms and terminology required for understanding and executing this
plan. If separate project glossary is maintained then refer to that.]

Item Description/ Expansion

2 Deployment process

2.1 Terminologies:

Terminolog Functionality
y
nohup Nohup is short for “No Hangups”.

Nohup is a supplemental command that tells

the Linux system not to stop another
command once it has started.

That means it’ll keep running until it’s

done, even if the user that started it logs
out.
 & If ‘&’ is used at the end of any command,
that moves the command to the
background, freeing up the terminal that
we are working in.
nginx NGINX is open source software for web
serving, reverse proxying, caching, load
balancing, media streaming, and more.

sudo Sudo stands for either “substitute user do”

or “super user do” (depending upon how we
want to look at it).

It is a linux command which allows a user to

run a program as another user (most often
the root user).

netstat netstat (network statistics) is a command-

line tool that displays network connections
(both incoming and outgoing), routing
tables, and a number of network interface
statistics.
2.2 Process Flow:

 Our BkashAml360 solution has 4 major compartments. They are:

1. Frontend Service (Backup approximately 20 minutes and deployment 1 hour)
2. Authorization Service (Backup approximately 20 minutes and deployment 1 hour)
3. Web Backend Service (Backup approximately 20 minutes and deployment 1 hour)
4. App Backend Service (Backup approximately 20 minutes and deployment 1 hour)

 Before starting the deployment, we first back up the DB.

1. Data backup - (approximately 3 hours)
2. Store procedure backup- (approximately 1 hours)

2.2.1 Step 1: Run the NGINX, Start Front-end Service:

NGINX starts the Front-end Service at port: 8001.

Folder Path /usr/share/nginx
IP Address & Port http://103.219.114.181:8001
Commands cd /usr/share/nginx
service nginx restart
2.2.2 Step 2 - Verify the Nginx And Front-end Service:

Check Nginx status in command line. If success appears in command line, then check from web
browser by typing the application url.
Folder Path /usr/share/nginx
Command service nginx status
Front End IP & Port http://103.219.114.181:8001

2.2.3 Step 3 - Setup Authorization Service:

Go to the folder path and run the command. It will run the authorization service in 8003 port.
Folder Path /home/appusr/amlapp/o-auth/
Command nohup java -jar authorization-server-0.0.1.jar & disown
Authorization Service IP & http://103.219.114.181:8003
Port
2.2.4 Step 4 - Verify Authorization Service:

To verify authorization service is running or not, run the command. It will visualize the port number:
8003 is being occupied by authorization service or not.
Folder Path /home/appusr/amlapp/o-auth/
Command netstat -tulpn
Authorization Service IP & http://103.219.114.181:8003
Port
2.2.5 Step 5 - Setup Web Backend Service:

Run the following command in this folder path. It will run the Web Backend Service on port: 8181.
Folder Path /home/appusr/amlapp/web-backend/
Command nohup java -jar bkashWebBackend-0.0.1.jar & disown
Web Backend Service IP & http://103.219.114.181:8181
Port
2.2.6 Step 6 - Verify Web Backend Service State

To Verify the Web Backend service state, we run the command. It will visualize 8181 port is being
occupied by our web backend service or not.
Folder Path /home/appusr/amlapp/web-backend/
Command netstat -tulpn
Web Backend IP & Port http://103.219.114.181:8181
2.2.7 Step 7 - Setup App Backend Service State:

Go to the following folder path and run the command. It will run App Backend Service on port 8004.
Folder Path /home/appusr/amlapp/app-backend/
Command nohup java -jar amlapp-0.0.1.jar &
App Backend Port http://103.219.114.181:8004
2.2.8 Step 8 - Verify App Backend Service State:

To Verify App Backend Service, run the following command on command line. It will visualize 8181
port is occupied by our App Backend service or not.
Folder Path /home/appusr/amlapp/app-backend/
Command netstat -tulpn
App Backend IP & Port http://103.219.114.181:8004
2.2.9 Step 9 - Verify All Services State:

To Verify all services are started, run the following command. It will visualize all the Java
Services we started.
Command ps aux | grep java
2.3 DB related process:
1. R2 related table implementation
2. Store procedure implementation
3. DB optimization query implementation
4. Before going live DB export

2.4 Rollback plan

1. If any inconsistency arises backup db and backup services will be redeployed again.