Java Development Kit
Also known as a JDK. A program-development environment for writing Java applets and applications. It consists of a runtime environment in the operating system layer, as well as the tools and programming that developers need to compile, debug, and run applets and applications that are written in the Java language.
Glossary
Transport Layer Security
Also known as TLS. An industry-standard protocol for secure communications on the Internet. It is the successor of Secure Sockets Layer (SSL) 3.0.
Genesys supports the use of the TLS protocol to secure data exchange between Genesys components.
Glossary
Hypertext Transfer Protocol Over Secure Socket Layer
Also known as https. A secure version of the Hypertext Transfer Protocol, it is the combination of a normal HTTP interaction over an encrypted Secure Sockets Layer (SSL) or Transport Layer Security (TLS) connection.
Glossary
Hypertext Transfer Protocol
Also known as HTTP. The protocol that is used most commonly in the World Wide Web to transfer information from web servers to web browsers.
Glossary
Security and Multi-Tenancy
|
Purpose: To provide background information on Security and Multi-Tenancy in Genesys Web Engagement. |
Security
Genesys Web Engagement supports HTTPS/SSL/TLS to protect data over the web.
- All connections can be secured, including connections from the browser to the Frontend and Backend Servers.
- Applications defined in Configuration Server can have both HTTP and HTTPS connections.
Transport Layer Security (TLS) is supported above Java containers, Jetty and Apache Tomcat.
The user data submitted from the browser tier is always sent through secure connections.
Note: To support secure (TLS) connections to Configuration Server on Windows OS, if you use the JDK 6 64 bit, it is mandatory to do one of the following:
- Update JDK 6 64 bit with Java SE Development Kit 6, Update 38 (JDK 6u38) or older.
- Setup JDK 7.
Multi-Tenancy
To implement Genesys Web Engagement, you should create one application per tenant. This application supports multiple domains and all their associated subdomains. For instance, a genesyslab application supports the genesyslab.com domain and its associated subdomain, docs.genesyslab.com.
As a result, your deployment must respect the following constraints:
- One tenant can contain multiple DSL files, but instrumentation will upload only one of them at a given time; a single DSL file is active for a given page during the customer's visit on your website.
- One Frontend Server node should only belong to one tenant.
- The Frontend load balancer (or Frontend Server) is the single entry point.