Vibe Desktop and Vibe Add-in can cause a large amount of traffic on the Vibe servers. To prevent the Vibe Desktop and the Vibe Add-in synchronization process or the Vibe site from becoming slow, you can distribute Vibe Desktop and Vibe Add-in traffic among dedicated Vibe servers with your load balancer or reverse proxy server.
For example, if you have a Vibe installation with five servers, you could dedicate one server to handle Vibe Desktop traffic, one server to handle Vibe Add-in traffic, and use the remaining three servers to serve the main Vibe Web application. This configuration prevents an unusual spike in Vibe Desktop traffic or Vibe Add-in traffic from impacting the Vibe site.
You can distribute Vibe Desktop traffic and Vibe Add-in traffic differently, depending on whether you want traffic from all applications (not just Vibe Desktop and Vibe Add-in) that are accessing Vibe to be handled in the same way, or whether you want Vibe Desktop traffic and Vibe Add-in traffic to be handled independently from each other and from other applications that are accessing Vibe.
You can configure your load balancer or reverse proxy server to distribute Vibe Desktop synchronization traffic among multiple Vibe servers. Vibe Desktop traffic is independent of traffic from other applications that are accessing Vibe.
NOTE:Your load balancer or reverse proxy server must be able to make routing decisions based on the request headers.
Configure your load balancer or reverse proxy server to use the user agent request header. For Vibe Desktop, the request header begins with NovellVibeDesktop. For example: User-Agent: NovellVibeDesktop/1.0 (Windows NT 6.1; Python/2.7.0; en_US) suds/0.4.
For specific information on how to configure the load balancer or reverse proxy server, see Section 7.5.4, Load Balancer and Reverse Proxy Server Configuration.
You can configure your load balancer or reverse proxy server to distribute Vibe Add-in synchronization traffic among multiple Vibe servers. Vibe Add-in traffic is independent of traffic from other applications that are accessing Vibe.
NOTE:Your load balancer or reverse proxy server must be able to make routing decisions based on the request headers.
Configure your load balancer or reverse proxy server to use the user agent request header. For Vibe Add-in, the request header begins with NovellVibeDesktop. For example: User-Agent: NovellVibeMsoAddin/1.0 (Windows NT 6.1.7601.65536; .NET Framework 4.0.30319.239; en_US)
For specific information on how to configure the load balancer or reverse proxy server, see Section 7.5.4, Load Balancer and Reverse Proxy Server Configuration.
You can configure your load balancer or reverse proxy server to distribute Vibe Desktop and Vibe Add-in synchronization traffic (along with traffic coming from all other applications that use the Vibe Web service interface) among multiple Vibe servers.
Examples of other applications that use the Vibe Web service interface are:
GroupWise client SOAP requests
All other SOAP requests from third-party applications
NOTE:Your load balancer or reverse proxy server must be able to make routing decisions based on the HTTP URL path.
Configure your load balancer or reverse proxy server to send all Vibe Desktop HTTP requests (designated by the following paths /ssf/ws/TeamingServiceV1 and /rest/*) to one pool of Vibe servers.
All other requests are sent to another pool of Vibe servers.
For specific information on how to configure the load balancer or reverse proxy server, see Section 7.5.4, Load Balancer and Reverse Proxy Server Configuration.
For information on how to configure a load balancer for your Vibe site, see any of the following sections, depending on the type of load balancer you want to use:
Configuring Apache as a Load Balancer
in Running Vibe on Multiple Servers
in the Novell Vibe 3.4 Installation Guide.
Configuring Linux Virtual Server as a Load Balancer
in Running Vibe on Multiple Servers
in the Novell Vibe 3.4 Installation Guide.
Configuring IIS to Load Balance in a Clustered Environment
in Configuring Single Sign-On with Internet Information Services for Windows
in the Novell Vibe 3.4 Installation Guide.
For information on how to configure a reverse-proxy server for your Vibe site, see Configuring Single Sign-On with Novell Access Manager
in the Novell Vibe 3.4 Installation Guide.