Jump to: navigation, search

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

A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

(Interaction Server Cluster deployment)
(Interaction Server Cluster deployment)
Line 24: Line 24:
 
* Direct connections to Interaction Server Pair
 
* Direct connections to Interaction Server Pair
 
* Connection to an Application Cluster that contains a list of Interaction Server Proxies
 
* Connection to an Application Cluster that contains a list of Interaction Server Proxies
 +
  
 
The CloudCluster Application cannot support both connection options listed above.
 
The CloudCluster Application cannot support both connection options listed above.
  
When you configure the connection, the Application Parameters field must include the following string:
+
When you configure the connection, the '''Application Parameters''' field must include the following string:
  
 
<source lang="text">clusterType=eservices</source>
 
<source lang="text">clusterType=eservices</source>
 +
 +
[[File:LoadBalanceApplicationParamaters.png|Image of Application Parameter field]]
 +
 +
  
 
[[Category:V:HTCC:8.5.2DRAFT]]
 
[[Category:V:HTCC:8.5.2DRAFT]]

Revision as of 20:20, 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.

Important
Web Services and Applications does not currently support web sockets.


Interaction Server Cluster deployment

New Page - all new content

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 field must include the following string:

clusterType=eservices

Image of Application Parameter field

Comments or questions about this documentation? Contact us for support!