Scribd
Upload
52 views6 pages

Hardware - Sizing - Indicative Prod

Hardware_Sizing_Indicative prod

Uploaded by

Chong Kum Chun
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as XLSX, PDF, TXT or read online on Scribd
52 views6 pages

Hardware - Sizing - Indicative Prod

Hardware_Sizing_Indicative prod

Uploaded by

Chong Kum Chun
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as XLSX, PDF, TXT or read online on Scribd
You are on page 1/ 6

Assumptions:

* Sizing is provided for KMF,Engagement services & Sync services


* HA is considered ONLY for Production.
* Sizing is estimated for Peak load of 500 requests / sec. + High Availability (only for Production)
* Considered that each Kony instance can handle 35 concurrent requests for KMF, 50 push messages for engagement services
* The Servers need to have internet access or all access required for the respective Kony applications as per the firewall requir
* Capacity planning depends on many parameters like application type, payload, etc. So, its strongly recommended to do pe

Production Application Server - KM


Server Type Specifications
Processor
Memory
Hardware
Network
App Server Drive Configuration
OS Version
Application Server
Software
Java

Backup
DR
Dynatrace monitoring

Production Database Server - KMF, Engagem


Server Type Specifications
Processor
Hardware
Memory
Database
Server Storage (SAN)
Software
Database
Backup
DR
Dynatrace monitoring

Production - Kony Web Server


Server Type Specifications
Processor
Memory
Drive Configuration
Hardware
Physical / VM
Web server Network
Hardware

Web server
Redundant Power

OS Version
Software
Web server
Backup
DR
Dynatrace monitoring
& Sync services

/ sec. + High Availability (only for Production)


35 concurrent requests for KMF, 50 push messages for engagement services per second.
ccess required for the respective Kony applications as per the firewall requirements.
s like application type, payload, etc. So, its strongly recommended to do peak load test before moving to production.

Production Application Server - KMF, Engagement services


Specifications
16 Processors/core per Sever
64 GB per server
2. (1GbE (Client access), 1GbE (Backup))
200 GB
RHEL 6.4 -7.x
WLS 12C, Jboss EAP 6.4/7.0, Tomcat 7.x, WAS 8.5.5.5/8.5.5.10
Oracle/Sun Java Development Kit 1.8 (JDK 1.8.0_11) - 64-bit

Veritas Netbackup version 8.1.2


System capable to perform Disaster Recovery activity within single click solution.
Dynatrace OneAgent license

Production Database Server - KMF, Engagement services


Specifications
4 Processing Units
12 GB
1 TB

MS SQL2019 Enterprise
Veritas Netbackup version 8.1.2
System capable to perform Disaster Recovery activity within single click solution.
Dynatrace OneAgent license

Production - Kony Web Server


Specifications
4 cores
8 GB
60 GB
VM
2 x 1GbE (Client access), 1x1GbE (Backup)
NA

RHEL 7.X
Apache HTTP Server
Veritas Netbackup version 8.1.2
System capable to perform Disaster Recovery activity within single click solution.
Dynatrace OneAgent license
ng to production.

t services
Quantity
Kony Component Instances (JVMs) Servers
KMF Console 1 per Server
KMF Identity 2 per Server

KMF Integration 7 per Server 2

Kony Engagement Services 1 Per Server

2
2
2

Server Quantity

2
2
2

Server Quantity

2
2

2
2
2

You might also like