Document Purpose
- Last Updated: August 5, 2025
- 2 minute read
- Progress Connection Manager for ObjectScale
- Documentation
This deployment guide provides instructions on how to configure the Connection Manager to load balance Dell ObjectScale services using application templates. This guide should only be used as a reference for the load balancing configuration of ObjectScale services because each environment is unique and may have different requirements. This guide also outlines the load balancing configuration using custom ObjectScale ports in the application templates, but default ports can also be leveraged based on the environment.
This guide outlines the configuration of Virtual Services (VSs) based on best practices. There are two approaches when publishing Dell ObjectScale through the Connection Manager:
Layer 4: When SSL/TLS offloading is not required, Layer 4 may be used to pass the traffic back to the ObjectScale nodes. Transparency is automatically enabled when using Layer 4. This sends the original source IP address to the Real Servers. For more information, see the Transparency Feature Description. Using Layer 4 has the following requirements:
- The Connection Manager must be set up in a two-arm configuration.
- ObjectScale nodes must use the Connection Manager as the default gateway.
- All connections to the ObjectScale environment must be initiated from a different subnet.
Layer 7: When using SSL/TLS offloading or when the above requirements may not be met, you can leverage Layer 7. Layer 7 by default does not use transparency and therefore the IP address of the Connection Manager is used when accessing the ObjectScale environment. For further details, refer to the Routing Feature Description. The X-Forwarded-For header is leveraged to provide the original source IP address in the ObjectScale logs for troubleshooting purposes. When a secure connection is used, a certificate must be installed on the Connection Manager to decrypt the traffic for the X-Forwarded-For header insertion. This traffic can then be re-encrypted or offloaded depending on the security requirements.
Connection Manager allows for QoS/Rate Limiting to be applied to provide granular controls to the traffic when layer 7 is used. For more information refer the QoS/Rate Limiting section in this document.
Contact Progress Kemp Support for any questions regarding configuration options.