slidy architecture
TRANSCRIPT
THE New generation Wallboard solution for Contact Centers
Harness the power of Smart Visualization
Innovative multimedia wallboard displaying Genesys statistics and metrics from any third party data sources
ARCHITECTURE OVERVIEW
Architecture: Stand alone mode
Database Server(Oracle or SQL Server)
Host1
IIS- SLIDYWeb application
Collector Service
Genesys Solution Control
Server
SLIDY
Genesys StatServer (Pri/Bak)
Genesys Components
Internet browser
Genesys Config Server
SIP Server/TServer
Genesys LCA
Genesys CS Proxy (Pri)
Note: This diagram focuses only on Genesys component connectivityin a single collector mode
Architecture: Cluster mode
Host2
HA proxy
Database Server(DB Cluster preferred)
Host1
IIS- SLIDYWeb application
Collector Service1 (primary)
Genesys Solution Control
Server
SLIDY
Genesys StatServer (Pri/Bak)
Genesys Components
Internet browser
Collector Service4 (primary)
Genesys Config Server
SIP Server/TServer
Load Balancer(i.e. HA proxy, Big IP F5)
IIS- SLIDYWeb application
Genesys StatServer (Pri/Bak)
Genesys LCAGenesys LCA
Genesys CS Proxy (Pri)
Genesys CS Proxy (Bak)
Collector Service2 (primary)
Collector Service3 (primary)
Note: This diagram focuses only on Genesys component connectivityin a cluster mode
IIS Web
Architecture: Redundancy
Load Balancer / Reverse proxy
IIS (Web server1)
SLIDY Web App
IIS (Web server2)
SLIDY Web App
SLIDY Collector 1
Genesys StatServer1
Genesys StatServer2
Web Service1
Web Service2
Database1
Database2
SLIDY Collector 2 SLIDY Collector 3
User Internet browser User Internet browser User Internet browser User Internet browser
Failover - Stickiness
Load Balancing
Genesys StatServerN Web ServiceN DatabaseN
Data Sources
Slidy configuration DB SQL Server/Oracle
Load Balancer / Reverse proxy
Cluster
Web Services
SLIDY components
Genesys components
DB data sources
SLIDY Integration with Genesys:
• SLIDY collectors support Genesyscomponent HA and failover
• SLIDY can connect to multiple GenesysStatservers
• SLIDY collectors can be fully andnatively controlled by Genesysmanagement layer
SLIDY Integration with Third party datasources:
• SLIDY collectors can retrieve data fromany Web Services
• SLIDY collectors can retrieve data fromSQL Server or Oracle Databases
• Single metrics or data arrays aresupported
SLIDY Redundancy:
• SLIDY web application can be loadbalanced using any LB (i.e HA proxy.,Big IP F5, MgInx, etc)
• SLIDY supports true clusterconfiguration and failover betweenSLIDY collector nodes.
• SLIDY collectors runs in load-balancingmode by the LB of choice
Architecture: Scalability
Load Balancer/ Reverse proxy
IIS (Web server1)
SLIDY Web App
IIS (Web server2)
SLIDY Web App
SLIDY Web Application Scalability:
• SLIDY architecture advantage: the load isdistributed among the connected clients(internet browsers) => limited load on theSLIDY web application server
• SLIDY web application failover can be managedthrough a LB (HA Proxy, Big F5, NGInx, etc)
SQL Server/OracleLoad balancer Load balancer
SLIDY Collector 1
Genesys StatServer1
Genesys StatServer2
Web Service1
Web Service2
Database1
Database2
SLIDY Collector 2 SLIDY Collector 3
SLIDY Metric Collector Scalability:
• The SLIDY collector upscaling is supported bythe Load Balancing (Round Robin) betweenmultiples Collector instances.
• Each SLIDY Collector can connect to multipleGenesys Statservers, multiple Webservicesand multiple Databases
SLIDY Database:
• SLIDY database can run on an Oracle or SQLserver cluster or SQL Net flat file on a shareddirectory (file server)
• SLIDY Database only stores Wallboardconfiguration but no statistical data which isreceived and displayed in REAL-TIME
User Internet browser User Internet browser User Internet browser User Internet browser Load Sharing
Load Balancing
Genesys StatServerN Web ServiceN DatabaseN
Data Sources
Architecture across 2 Data Centers
Primary Data Center Backup Data Center
DR scenario: • The primary Data Center is down or controlled switchover between two data centers.
Actions to switchover between Data Centers• A standby SLIDY solution is available and running on Data Center2• All wallboard configuration is available on the SLIDY database on DC1 (primary) is replicated and available on DC2
(backup).• The Genesys Statservers on both DCs are expected to be configured with the same statistics.• As soon as Agents login to SIP Server on DC2, StatServer on DC2 starts collecting metrics.• SLIDY users get access to all existing configuration and statistics are immediately collected by DC2 StatServer.
How does SLIDY adjust to the change of statservers when switching to DC2 knowing that metrics are associated to a specific statserver application?• SLIDY collector copes automatically with a StatServer pair configured in HA mode (warm standby) on one Data Center.• When switching to a second data center, SLIDY collector keeps in its configuration a mapping between each statserver on
DC1 to the statserver on DC2 and replaces automatically the reference to the statservers in each metric definition by the alternative one.
• This ensures full transparency and availability of all statistics on the DC2 without any manual intervention or configuration.
DR and switchover between Data Centers
The Challenge: Web based applications like SLIDY are required to push data to clients as fast as possible, whenever it is necessary without waiting for client requests. For the purpose of efficiency and performance a two way (client/server) communication mechanism is required to implement “real-time web” functionality.
The Answer: SLIDY has built-in capabilities to push content to the connected clients as it happens, in real-time and supports WebSockets, which is a HTML5 API that enables bi-directional communication between the browser and the server. Websockets is supported by all modern internet browsers and is an enabler for real-time web applications.
SLIDY uses SignalR which takes advantage of WebSockets under the covers when it's available, and gracefully fallback to other techniques like server events, http long-polling and other technologies to mimic bi-directional communication (collectively known as "comet") when it isn’t supported (i.e on older browsers).
HTML5 Web Sockets can provide a 500:1 or (depending on the size of the HTTP headers) even a 1000:1 reduction in unnecessary HTTP header traffic and 3:1 reduction in latency.
• Genesys Web Services and Applications does not currently support WebSockets. • SLIDY does support Web Sockets!
Real-time web application
"Reducing kilobytes of data to 2 bytes…and reducing latency from 150ms to 50ms is far more than marginal. In fact, these two factors alone are enough to make Web Sockets seriously interesting to Google.“
Ian Hickson (Google's HTML5 specification lead)
