The Smart Client connects to the Redbex Application Server using Web Services i.e. using the HTTP protocol. Additionally the Smart Client accesses other HTTP web resources directly i.e. not via the Application Server - see table 1 for a listing of all resources that are connected by the Smart Client directly.
Depending on the network environment in which the Smart Client is installed it might be necessary to configure an HTTP Proxy server to be able to connect all the Web Resources shown in Table 1.
When the Smart Client is started it first checks if there is a specific HTTP proxy server configured in the Smart Client Settings, i.e. if the Smart Client Setting Override system default proxy is set to true. If so the Smart Client will use the HTTP proxy as defined in the Smart Client Settings. If the Smart Client setting Override system default proxy is set to true and the Proxy server is empty the Smart Client will try to connect to the internet without using a proxy server.
If the Smart Client Setting Override system default proxy is not set to true Smart Client will next check if there is an HTTP Proxy configured in the Smart Client Common Settings, i.e. if a Smart CLient Common Settings XML file exists and Smart Client Common Setting HttpProxyOverride is set to true. If so the Smart Client will use the HTTP proxy as defined in the Smart Client Common Settings. If the Smart Client Common setting HttpProxyOverride is set to true and the Smart Client Common Setting HttpProxyServer is empty the Smart Client will try to connect to the internet without using a proxy server.
If neither the Smart Client Settings nor the Smart Client Common Settings define a specific proxy to be used the Smart Client will use the same proxy configuration as defined by the Windows Operating system (Internet Settings).
The HTTP proxy server to be used is evaluated on start up of the Smart Client. Changes to proxy related settings therefore only take effect after a restart of the Smart Client.
The actually used Proxy is logged in the Smart Client log.
Resource |
Description |
Application Server |
Connection to the Redbex Application Server |
Distribution Server |
Connection to the Redbex Distribution Server is needed for downloading and installing updates. |
Google Maps |
When rendering a map view with a Google Maps layer the tiles for the Google Maps layer are loaded directly from Google's servers. |
Bing Maps |
When rendering a map view with a Bing Maps layer the tiles for the Google Maps layer are loaded directly from Microsoft's servers. |
Open Street Maps |
When rendering a map view with an Open Street Maps layer the tiles for the Google Maps layer are loaded directly from OpenStreetMap servers. |
WMS |
When rendering a map view with a WMS layer the tiles for this layer will be directly loaded from the specified WMS. |
WFS |
When rendering a map view with a WFS layer the data for this layer will be directly loaded from the specified WFS. |
RSS Feeds |
Some widgets available for the Start window show RSS feeds. These feeds are loaded directly from the respective source. |
WMS Configuration |
When configuring a WMS layer the Capabilities of the WMS are loaded directly from the given WMS. |
WFS Configuration |
When configuring a WFS layer the Capabilities of the WFS are loaded directly from the given WFS. |
Table 1: HTTP Web Resources used by the Smart Client.