Where Remote Manager is not used through the native network and operates behind a proxy server/load balancer, the (external) access to it is happening by means of URLs. Such access is configurable via properties following the pattern transport.host and transport.port. The following table illustrates the required setup for external access via HTTPS, HTTP and WSS URLs, and can be used as a reference model if other transport must be setup.
For communication via HTTPS and WSS URLs, the Load Balancer must perform SSL offload as Remote Manager supports only plain HTTP and WS communication. The properties for enablement of SSL offload are also provided in the table below.
Property | Value | Description |
|---|---|---|
| <host-name/ip> | hostname / public IP address of Remote Manager (i.e. of proxy server / Load Balancer) |
| 443 | port for HTTPS URLs |
| <host-name/ip> | hostname / public IP address of Remote Manager (i.e. of proxy server / Load Balancer) |
| 443 | port for HTTP URLs |
| <host-name/ip> | hostname / public IP address of Remote Manager (i.e. of proxy server / Load Balancer) |
| 443 | port for WSS URLs |
| true | The default value is false, and must be set to true, if RM is behind a Load Balancer and SSL is offloaded |
| true | The default value is false, and must be set to true, if RM is behind a Load Balancer and SSL is offloaded |
The same properties and the respective URLs can be also used for agents and external applications, e.g. download URLs.