1 / 6

HSJi  Technical Requirements

HSJi  Technical Requirements. Business Non-functional. Performance requirements (user interface search response times, page load times) Basic page load time : < 2 seconds Map listing load time : < 5 seconds Data sizing and growth assumptions – 3 years Database : < 100 MB

flint
Télécharger la présentation

HSJi  Technical Requirements

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. HSJi Technical Requirements

  2. Business Non-functional • Performance requirements (user interface search response times, page load times) • Basic page load time : < 2 seconds • Map listing load time : < 5 seconds • Data sizing and growth assumptions – 3 years • Database : < 100 MB • Files ; < 17 GB • No of users and expected levels of concurrent access for website • Total users : < 1115 (223 orgs) • Concurrent users : < 50 • No of users and expected levels of concurrent access for Drupal CMS • Total users : < 10 • Concurrent users : < 5 • Backup requirements • Database : daily updates available for 1 week • Files : daily updates available for 1 week

  3. Logical • Abacus SSO integration architecture • See attached SSO login flows file • Email alert integration design • Probably utilise existing SMTP relay servers?

  4. HSJi site architecture HSJ Abacus Single-sign-on between HSJ & HSJi See attached file Internet Firewall Salesforce Load Balancer Google Maps API Web server 2 Apache PHP Memcache? Web server 1 Apache PHP Memcache? Ethernet DB Master MySQL Clustered Solr Master Jetty NAS Shared storage Solr Slave Jetty DB Slave MySQL Clustered NAS Shared storage Replicated Replicated Replicated

  5. Physical • Staging Server Details • Drupal SFTP • Name: frln2sadm01 • Directory: /frln2snas01_web_emap_unix • Solr server • Software: • Jetty (8.1.10.v20130312) • Apache Solr (4.4.0) • Name: • 10.102.112.17 (frlbn2sweb33) • Port: 8983 • http://frln2sweb33:8983/solr • Live Server Details • pending Software Technical Stack Name : Drupal Version : 7 Release : 7.23 Name : httpd Version : 2.2.15 Release : 15.el6.centos.1 Name : mysql Version : 5.1.61 Release : 4.el6 Name : php Version : 5.3.3 Release : 14.el6_3 Name : Apache Tomcat Version : 7

  6. Physical • Specs per a VM on staging and production • 2x cores • 4GB memory • Caching architecture • Drupal internal performance settings include: • Page & block caching – saved in database • JS/CSS – files are aggregated & optimised • Possible to turn on caching on load balancer, but not done by default • Error log files • Access : request files from Central IT Web Team • Log rotation : rotated daily, kept for a week • Security • Ports required : 80, 443 • Staging access : Central IT Web Team, Justin Chevallier, Epam • Production access : Central IT Web Team, Justin Chevallier • Monitoring requirements • NAGIOS currently used – covers DB’s, servers, disk usage, CPU, memory, availability • New technologies are being reviewed • DNS requirements • Not sure what this involves. Site URL & DNS, TTL configs? If so TTL usually set to 24 hours, but can be changed in advance.

More Related