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
(→Interaction Server Cluster deployment) |
|||
| Line 14: | Line 14: | ||
{{NoteFormat|If you use Workspace Web Edition and your load balancer supports web sockets, you must enable this feature in Workspace Web Edition by setting the [[Documentation:HTCC:IWWDep:Application:8.5.2#system.notif.enabled-websocket|system.notif.enabled-websocket]] option to <tt>true</tt>.}}--> | {{NoteFormat|If you use Workspace Web Edition and your load balancer supports web sockets, you must enable this feature in Workspace Web Edition by setting the [[Documentation:HTCC:IWWDep:Application:8.5.2#system.notif.enabled-websocket|system.notif.enabled-websocket]] option to <tt>true</tt>.}}--> | ||
| − | = Interaction Server Cluster deployment= | + | == Interaction Server Cluster deployment== |
{{Chgbar_open}}{{Editgrn_open}}New Page - all new content{{Editgrn_close}}{{Chgbar_close}} | {{Chgbar_open}}{{Editgrn_open}}New Page - all new content{{Editgrn_close}}{{Chgbar_close}} | ||
Revision as of 19:29, December 20, 2016
Load balancing
Web Services supports the following methods for load balancing:
Third-party load balancing
Web Services supports any third-party load balancer that supports sticky sessions. You should configure session affinity (sticky sessions) based on JSESSIONID. Once your load balancer is set up, you can use the following URL for health checks: http://<Web_Services_Host>:<Web_Services_Port>/api/v2/diagnostics/version.
If you're configuring your solution to use Hypertext Transfer Protocol over Secure Socket Layer, you don't need to set up HTTPS between your load balancer and Web Services.
Interaction Server Cluster deployment
Web Services supports Interaction Server Cluster deployment for load balancing. For more information, see the Interaction Server Cluster.
The CloudCluster Application could have one of the following connections:
- Direct connections to Interaction Server Pair
- Connection to an Application Cluster that contains a list of Interaction Server Proxies
The CloudCluster Application cannot support both connection options listed above.
When you configure the connection, the Application Parameters much include the following string:
clusterType=eservices