Slidy is based on a fully responsive web application. It supports web sockets for optimal web browsing performance and user experience. Slidy has a scalable and redundant technical architecture that allows you to connect to multiple data sources. Unlike other products, Slidy Collector can connect to multiple Genesys statservers; in fact each single metric can point to a different statserver. Slidy Collector allows you to retrieve real time as well as historical data from any SQL Server or Oracle database as well as any WebService to display data from your CRM or other third party data source. Reach out to support@cc-expertise.com to get your personal freel trial licenses.

1. 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

2. Architecture: Stand alone mode
Database Server
(Oracle or SQL Server)
Host1
IIS- SLIDY
Web 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 connectivity
in a single collector mode

3. Architecture: Cluster mode
Host2
HA proxy
Database Server
(DB Cluster preferred)
Host1
IIS- SLIDY
Web 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- SLIDY
Web 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 connectivity
in a cluster mode

4. 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 Genesys
component HA and failover
• SLIDY can connect to multiple Genesys
Statservers
• SLIDY collectors can be fully and
natively controlled by Genesys
management layer
SLIDY Integration with Third party data
sources:
• SLIDY collectors can retrieve data from
any Web Services
• SLIDY collectors can retrieve data from
SQL Server or Oracle Databases
• Single metrics or data arrays are
supported
SLIDY Redundancy:
• SLIDY web application can be load
balanced using any LB (i.e HA proxy.,
Big IP F5, MgInx, etc)
• SLIDY supports true cluster
configuration and failover between
SLIDY collector nodes.
• SLIDY collectors runs in load-balancing
mode by the LB of choice

5. 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 is
distributed among the connected clients
(internet browsers) => limited load on the
SLIDY web application server
• SLIDY web application failover can be managed
through a LB (HA Proxy, Big F5, NGInx, etc)
SQL Server/Oracle
Load 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 by
the Load Balancing (Round Robin) between
multiples Collector instances.
• Each SLIDY Collector can connect to multiple
Genesys Statservers, multiple Webservices
and multiple Databases
SLIDY Database:
• SLIDY database can run on an Oracle or SQL
server cluster or SQL Net flat file on a shared
directory (file server)
• SLIDY Database only stores Wallboard
configuration but no statistical data which is
received 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

6. Architecture across 2 Data Centers
Primary Data Center Backup Data Center

7. 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

8. 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)

9. THANK YOU
support@cc-expertise.com
Harness the power of Smart Visualization