Sapience Hardware & Software Requirements PDF

HARDWARE AND SOFTWARE REQUIREMENTS SAPIENCE SERVER AND BUDDY UPDATED: V2.0 FEBRUARY 2020 WELCOME TO SAPIENCE! This document lists the hardware and software requirements for installing Sapience Server v6.5 onwards on customer premises. The suggested server configuration should be considered as the...

HARDWARE AND SOFTWARE REQUIREMENTS SAPIENCE SERVER AND BUDDY UPDATED: V2.0 FEBRUARY 2020 WELCOME TO SAPIENCE! This document lists the hardware and software requirements for installing Sapience Server v6.5 onwards on customer premises. The suggested server configuration should be considered as the minimum requirement. Sapience is a data- intensive application. The exact configuration may require fine-tuning based on the customer-specific environment. The minimum requirements to install Sapience Buddy, for system and mobile, are also provided. SAPIENCE SERVER ASSUMPTION The storage mentioned below is for one year of data collection. If we apply the archival policy described below, the same storage will suffice for up to three years. OutputStaging and InputStaging Databases require additional storage on Database server. For access from outside the organization intranet, the hardware requirements change. Contact Sapience support team for recommendation based on the organization requirement and scenario. Recommended sync frequency: o Lite sync: Every 30 mins o Normal sync: Between 4 – 5 hours o Agent command framework sync: Every 2 hours o Metadata sync frequency: Once daily o Meeting/Outlook Web sync frequency: Every 8 hours Supports ONE Matrix Org for the specified hardware configuration. To increase the number of Matrix Orgs, contact Sapience Support for appropriate recommendations. Sapience recommends a dedicated database server. DNS name available for Sapience application (like..com). Periodic Performance health check of Sapience servers. Continuous monitoring of Sapience servers from the organization’s internal system monitoring tool/application: o All Sapience services o Alert for Server CPU utilization above 70% o Alert for Server Memory utilization above 70% o Alert for hard drive space utilization above 70% Page 1 of 7 ©Sapience Analytics sapienceanalytics.com Confidential SP/ProductDocuments  If Sapience Live or/and Transaction Live is enabled, Sapience recommends additional Application server for every set of 15000 users. Recommended archiving policy: o Daily level data archival after one year o Weekly level data archival after two years o Monthly level data archival after three years Page 2 of 7 ©Sapience Analytics sapienceanalytics.com Confidential SP/ProductDocuments ARCHITECTURE Sapience recommends the following hardware for physical and virtual environments. VCPU can be configured based on the physical hardware requirement. TWO-TIER ARCHITECTURE - HARDWARE In this architecture, the Sapience Application Server and Database Server are hosted on separate hardware. To increase the responsiveness and availability of applications, the Sapience Support team may recommend multiple instances of the servers based on the organization’s requirements and environment. SAPIENCE APPLICATION SERVER Max no. of 15,000 30,000 50,000 users supported: Application 3 6 10 Servers in load- balancing mode (considering Sapience Live and/or Transaction Live) CPU per server Equivalent CPU @ 2.10GHz, Equivalent CPU @ 2.10GHz, Equivalent CPU @ 2.10GHz, 2095 Mhz, 12 Core(s), 24 2095 Mhz, 16 Core(s), 32 2095 Mhz, 16 Core(s), 32 Logical Processor(s) Logical Processor(s) Logical Processor(s) RAM per server 24 GB 32 GB 32 GB 400 GB 400 GB 400 GB Storage per C:\ 150 GB (Operating system) C:\ 150 GB (Operating system) C:\ 150 GB (Operating system) server D:\ 250 GB (Sapience App server) D:\ 250 GB (Sapience App server) D:\ 250 GB (Sapience App server) E:\ 200 GB (Org sync files, scheduled reports, and other data) Shared drive Note: Shared drive across all the application servers Additional Hardware load balancer using round robin technology. requirements The Application Server and Database Server should be connected using high-speed Ethernet (at Network least 1 Gbps), and they should be in a single physical data center. Page 3 of 7 ©Sapience Analytics sapienceanalytics.com Confidential SP/ProductDocuments SAPIENCE DATABASE SERVER Max no. of 15,000 30,000 50,000 users supported: CPU Equivalent CPU @ 2.10GHz, Equivalent CPU @ 2.10GHz, Equivalent CPU @ 2.10GHz, 2095 Mhz, 16 Core(s), 32 2095 Mhz, 24 Core(s), 48 2095 Mhz, 32 Core(s), 64 Logical Processor(s) or higher Logical Processor(s) or higher Logical Processor(s) or higher RAM 64 GB 96 GB 144 GB SSD Disk only SSD Disk only SSD Disk only C:\ 50 GB (Operating system) C:\ 50 GB (Operating system) C:\ 50 GB (Operating system) D:\ 20 GB (SQL server installation) D:\ 20 GB (SQL server installation) D:\ 20 GB (SQL server installation) Storage F:\ 250 GB (Sapience DB MDF files) F:\ 400 GB (Sapience DB MDF files) F:\ 700 GB (Sapience DB MDF files) G:\ 250 GB (Sapience DB LDF files) G:\ 400 GB (Sapience DB LDF files) G:\ 500 GB (Sapience DB LDF files) H:\ 150 GB (Temp DB) H:\ 250 GB (Temp DB) H:\ 500 GB (Temp DB) I:\ 300 GB (Backup files) I:\ 500 GB (Backup files) I:\ 500 GB (Backup files) The Application Server and Database Server should be connected using high speed Ethernet (at Network least 1 Gbps) and should be in a single physical data center. RECOMMENDATIONS FOR SAPIENCE DATABASE SERVER: For two-tier architecture environments, the database should be on SSD disks or a SAN with equivalent I/O performance. High availability of the server is required. For Sapience Database server, the IO STALL should be as recommended by Microsoft. Database file configurations for the TEMPDB database will be based on the customer internal DBA standard. Page 4 of 7 ©Sapience Analytics sapienceanalytics.com Confidential SP/ProductDocuments SOFTWARE AND NETWORK REQUIREMENTS Sapience Application Server Supported OS: Windows Server Operating System (2012 / 2012 R2 / 2016) Recommended: Windows Server 2016 Hardware Requirement: Based on number of users; as recommended by Sapience team Microsoft.Net Framework: 4.7.2 and above Internet Information: 7.0 & above Services (IIS): Recommend 10.0 Microsoft Access Database 2016 (64-bit) Engine: Sapience Database Server Supported SQL Server: Microsoft SQL Server (2012/2012 R2/2014/2016) Network Access to the Sapience Web Client and Server-Sapience Buddy communication (from user devices) is accommodated using default HTTPs protocol while within the organization’s internal network. Access from outside the internal network could be supported through the VPN, or by exposing the server URL. It will depend upon the IT policy. The following ports need to be opened/configured on various systems in Sapience deployment: Client Device: Default/Chosen TCP (HTTPs) Port open for browsing Sapience Application Server: Default/Chosen TCP (HTTPs) Port open for receiving user requests Sapience Database Server: Default/Chosen TCP Port open for server communication Domain Accounts The following two accounts need to be created: Sapience Admin User System admin profile to manage: o Application Server and Database Server (Two-Tier Architecture) System admin permission on SQL Database server is required for: o Fresh install o Upgrade / Hotfix o Database folder Page 5 of 7 ©Sapience Analytics sapienceanalytics.com Confidential SP/ProductDocuments Sapience User This should be a valid domain account with standard user profile. This should be a service account. It should be usable for communication between the IIS and SQL DB server. Should be added to the following groups: o User groups: IIS_WPG, IIS_IUSRS The following local security policies should in place: o Add: Log on as batch job, Log on as service o Deny: Log on locally, Log on through Remote Desktop Services Requires full permission for: o Sapience Database folder in the Database server o Sapience Services Role (SELECT, INSERT, UPDATE, DELETE, EXECUTE ) on 5 Sapience Databases (Registry, TransDB, Trends, SapienceInputStagingDB, SapienceOutputStagingDB) SAPIENCE BUDDY ON PC Supported OS: Windows Windows 7, Windows 8, Windows 8.1 and Windows 10 (32 or 64 Bit) Windows Server 2012, Windows Server 2016 (64 Bit) Mac Version 10.10 "Yosemite," Version 10.11 "El Capitan," Version 10.12 "Sierra", Version 10.13 "High Sierra", Version 10.14 “Mojave”, Version 10.15 "Catalina" Linux RED HAT Enterprise Linux (version 7.3, 7.4, 7.5, 7.6 (64 bit)) Ubuntu Ubuntu Gnome Desktop Manager (version 12.04, 13.10, 14.04, 14.10, 16.04, 17.10, 18.04 with LXDE (32 and 64 bit)) Mint Linux Mint 17, 18 64-bit Cinnamon RAM Minimum 4 GB (recommended 8 GB if the system is running heavy applications like CAD / CAM, or 3D designing, etc.) Platform: For Win OS only: Microsoft.Net Frame 4.5.2 and above with user permissions to the following folders: C:\temp and C:\windows\temp C:\ProgramData\Microsoft\Crypto Prerequisites vcredist_x64, vcredist_x86 (for x86 and x64 VSTOR30, VSTOR40 systems): Page 6 of 7 ©Sapience Analytics sapienceanalytics.com Confidential SP/ProductDocuments Network: User desktop Port 443 open; for the user to browse Sapience server Port 443 open; to receive user requests Connectivity Access to the Sapience Web Client from user desktop using a browser SAPIENCE BUDDY ON MOBILE Android 4.4 (Kitkat) and above from Play Store iOS 8.0 and above from App Store Device-specific settings For Android only: Asus Oppo MI Gionee SamSung S7 / S8 OTHER RECOMMENDATIONS Sapience Staging / UAT Server: o This is required for offline testing and verification of ERP org sync and org structure delta updates, integration with various servers and applications, daily backups, and archival of old data. o The staging server configuration should be a replica of the production environment. o It can also be a VM, with a similar configuration (same number of logical CPUs). o The software configuration will be the same as that of the Sapience Analytics Server (refer to the previous section). o The Production Database backup should be restored on this staging server on a weekly basis. o Sapience server upgrade, Patch testing and other configuration related changes o During UAT test, Sapience recommends connecting a few Sapience Buddy instances to UAT server Data backup policy: o Set up a backup drive to take a temporary backup of Sapience Databases. The backup drive should be at a different physical location. o Sapience supports a full backup, with an overwrite feature, at 8:00 AM and 11:00 PM every day. o The data can also be backed up on a different machine, preferably the staging server. o It is the client’s responsibility to ensure that backups are taken regularly, and available in case any restoration of data becomes necessary. Page 7 of 7 ©Sapience Analytics sapienceanalytics.com Confidential SP/ProductDocuments