Smart IT test environment


This topic describes the deployment architecture, the hardware and software specifications for all servers used in the test and have details about Subquery algorithm for Restricted User


Smart IT Deployment Architecture

image2020-2-23_23-15-20.png

Specifications for Helix Applications

The following table summarize the hardware and resource allocation of Helix applications used for the benchmark.

Imp Note:

Note: Below configurations should not be considered as the baseline for the High Availability(HA) and resiliency system.
Based on the per-product High-Availability(HA) and resiliency requirement customers can build system accordingly.


Application

#Of Pods

Pod Resource Limit

Helix Single Sign-on (RSSO)

1

CPU Limit - 2, Memory Limit - 4GB

Helix Platform Admin

1

CPU Limit - 4, Memory Limit - 15GB

Helix Platform FTS

1

CPU Limit - 4, Memory Limit - 18GB

Helix Platform user

6

CPU Limit - 2, Memory Limit - 14GB

Helix Smart IT

2

CPU Limit - 4, Memory Limit - 8GB

Helix Virtual Chat Plugin

1

CPU Limit - 2, Memory Limit - 1GB

Helix OpenFire

1

CPU Limit - 1, Memory Limit - 2GB

Helix Digital Workplace

1

CPU Limit - 1.5, Memory Limit - 8GB

Helix Platform Innovation Suite

1

CPU Limit - 750m, Memory Limit - 7GB

The following table summarizes database hardware and resource allocation used for the benchmark.

Database

Specification

VM Used

Number in environment

Operating System Details

Postgres DB server

8 CPUs at 2.20 GHz each, 32GB RAM

Yes

1

CentOS Linux release 7.3.1611 (Core)

MS SQL Database server

2 CPUs at 2.7 GHz each, 24 core each, 320GB RAM

No

1

Microsoft Windows Server 2012 Enterprise with external Hitachi VSP 1000 SAN storage

Other hardware and resource specifications are

Tiers

Specification

VM used

Number in environment

Comments

OpenShift Cluster Master

8 CPUs, 16GB RAM

Yes

1

CentOS Linux release 7.6.1810 (Core)

Helix Platform Admin

4 CPUs, 18GB RAM

Yes

1

CentOS Linux release 7.6.1810 (Core)

Helix Platform FTS

4 CPUs, 24GB RAM

Yes

1

CentOS Linux release 7.6.1810 (Core)

Rest All Helix Applications

(RSSO, Platform User, Smart IT, Virtual Chat Server, Virtual Chat Plugin, Digital Workplace Basic, OpenFire, Innovation Studio)

4 CPUs, 16GB RAM

Yes

14

CentOS Linux release 7.6.1810 (Core)

Client computers (for Micro Focus Silk Performer)

4 CPUs at 2.40 GHz each, 16GB RAM

Yes

3

Microsoft Windows Server 2012 R2 Enterprise

Client computer (end-user timings)

4 CPUs at 3.86 GHz each, 18GB RAM

No

1

Model  - Dell Latitude E5490 Laptop

Note

All virtual machines (VMs) are hosted on VMware ESXi 6.5.0 servers powered by Intel Xeon CPU E5-2697 v2. 

The SQL server machine is configured with 4 separated IO subsystem (Hitachi VSP 1000):

IO Subsystem

Capacity

Partition

Bus Type

Name

Hosting

0

279GB

MBR

RAID

Dell PERC H710 SCSI Disk Device

OS files

1

2TB

MBR

Fibre Channel

Hitachi OPEN-V Multi-Path Disk Device

database data files

2

1.5TB

MBR

Fibre Channel

Hitachi OPEN-V Multi-Path Disk Device

database log files

3

1.5TB

MBR

Fibre Channel

Hitachi OPEN-V Multi-Path Disk Device

database tempdb files

 Software specifications

Tiers

Software Version

Remedy with Smart IT server

Smart IT 20.02

BMC DWP Basic 20.02

Tomcat 8.5.45.0

JDK 11.0.5

Chat server

Openfire 4.2.3

JDK 11.0.5

BMC Remedy Single Sign-On

BMC Remedy Single Sign-On 20.02

Tomcat 9.0.30

JDK 11.0.6

BMC Remedy Mid Tier

BMC Remedy Mid Tier 20.02

Tomcat 8.5.45

JDK 11.0.5

BMC Remedy AR System server

BMC Remedy AR System server 20.02

JDK 11.0.5

BMC Remedy DWP application

BMC Remedy DWP 20.02

Tomcat 8.5.50.0

JDK 11.0.5

BMC Helix Innovation Suite

BMC Helix IS 20.02

JDK 11.0.5

BMC Helix Virtual Chat Plugin

BMC Helix Virtualchat Plugin 20.02

JDK 11.0.5

BMC Helix Virtual Chat Server

BMC Helix Virtualchat Server 20.02

Tomcat 8.5.45.0

JDK 11.0.5

Database server

Microsoft SQL Server 2012

Client computers (Borland Silk Performer)

Silk Performer 20.0

Client computer (end-user timings)

Google Chrome 78

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*