Applies to version: 2021.1.x and above; author: Michał Bednarz
The article presents how to expand the WEBCON BPS installation with new application servers to easily support the higher load and increase the availability and reliability of WEBCON BPS applications.
Important: Each subsequent WEBCON BPS application server requires an appropriate license. The WEBCON BPS Search Server component is an exception.
Important: The BPS Search Server role does not support the HA and Failover functions. Ensuring the high availability of this component requires the implementation of a separate SOLR cluster. This configuration is not presented in this article.
Important: Load Balancer must support the Sticky Sessions functionality and the NTLM Proxy functionality (if Windows authentication is used).
WEBCON BPS installation
1. License update
Make sure the licenses for the new application server are available. If no licenses are available, application access errors will appear after expanding the installation.
2. Installation of WEBCON BPS components on a new server
Important: The operation must be performed using the installer with the version compatible with your WEBCON BPS installation.
3. Configuration of BPS Service for Failover
The Failover settings can be configured in the Tools for application management section. After changing the configuration, you must restart BPS Service.
4. Configuration WEBCON BPS for SSL offloading
This operation is described in the SSL Offloading vs WEBCON BPS Portal
5. Network communication between servers in BPS farm
TCP 8002 (WCF Service) should be open on both BPS servers.
TCP 8983 (SOLR) should be open on the BPS server where BPS Search Server is installed.
Important: Communication between BPS servers is required, and there is no need to open ports to a public network.
Load balancing settings and requirements