|Network interface TCP/IP address||Allows to define the network interface address (network adapter), used for accepting WebServer requests.|
All network interfaces (default) - The WebServer accepts requests through all nework interfaces of the computer. I.e. via all physical network adapters, virtual network adapters (VPN, etc.) and local interface (localhost i.e. 127.0.0.1).
Local network interface (localhost) - The WebServer accepts requests only via local network interface (localhost i.e. 127.0.0.1). In such case the WebServer accepts no requests from network interfaces. The local network interface is accessible only for applications running on the same computer as the WebServer.
Specific network interface - The WebServer accepts requests only from specific network interface (e.g. from particular network card). The networ interface address is entered only in numerical form (e.g. 192.168.1.1), nominal addresses cannot be used. In such case the WebServer will not accept any requests neither from another network interfaces nor local network interface.
This setting especially useful in cases the computer is equipped with multiple network cards while it is necessary to access teh Web only through one of them.
|Port TCP/IP||Number of the TCP/IP port, on which the WebServer accepts requests. Standard value for HTTP is 80 and for HTTPS is 443. |
This configurator sets the initial value of the property Port.
If the port value is already used by another Web server (e.g. by Apache, IIS, etc.), it is necessary to set different value (e.g. 85).
Macro expression can be used for input (it is evaluated while the application is launching).
|WEB server type||The configurator allows to set the WEB server type. WEB server of the "HTTP internal" type is integrated into the PROMOTIC system by default and it is not necessary to configure it. WEB server of the "HTTP(S) service" is included in all recent OS Windows (do not confuse it with IIS, it is not a real independent WEB server) and the PROMOTIC can use it. The configuration may be more difficult (see the puppiled utility PmHttpConfig.exe), but the performance is higher and the secure HTTPS is available.|
http internal (default) - The PROMOTIC system uses own integrated WEB server that is implemented directly over the communication sockets. The most important advantage is the fact that it is not necessary to configure it additionaly in OS Windows.
http service - The PROMOTIC system uses the service that is included in all recent OS Windows as a WEB server (do not confuse it with IIS, it is not a real independent WEB server). The configuration may be more difficult, but the performance is higher and the secure HTTPS is available. The configuration of HTTP service of the OS Windows in order to use it by the PROMOTIC WEB server is done by the PmHttpConfig.exe - configuration of HTTP service for PROMOTIC WEB servers (HTTP or HTTPS) utility.
https service - Based on the HTTP service and therefore similar information is valid as for previous option "http service". The secure HTTPS protocol differs from the unsecure HTTP protocol mainly by, the communication encryption (SSL) and by the fact that the server identity is verified by the certificate (digital signature). This way the possibility of data tapping is eliminated together with the chance of a false server forging. The PmHttpConfig.exe - configuration of HTTP service for PROMOTIC WEB servers (HTTP or HTTPS) is used for configuration including the certificate management.
Caution: For this HTTPS mode it is necessary to have the PmHTTPS licence.
|Worker thread count|
|Default Web file address||If the client enters the address only in the shortened form: //ComputerName, then the request is automatically routed to the specified address. default.htm is entered by default, which means that the request is routed to the address http://ComputerName/default.htm, which is the page containing the list of Web components with references to them. The entered address can even be compound, for example alarms/default.htm - then this request is routed to the "alarms" component. |
Most frequently, the default address leads to the main application workspace (to the PmWorkspace object). The the address entered here can be: workspace/main.htm.
|Default language||Web components display language selection. Web components registered into the PmWebLang object are displayed using the selected language.|
by runtime - According to the language defined in the "Main language of runtime" configurator (using the Pm.RtLang property).
en,de,ru,cs,sk,pl,.. - Specific language selection. Only the languages registred in the "All used languages" configurator can be selected.
|Small timeout (timeout for receiving/sending one part of long request) (s)||When receiving/sending a long request, the request (communication message) is separated to several small parts. The small timeout specifies the maximum allowed time for receiving/sending one part of the long request. The preset value is 10 s.|
|Big timeout (timeout for receiving, processing, sending the whole request) (s)||The big timeout specifies the maximum time for receiving, processing, sending the whole request. It goes about the maximum allowed time from receiving the first part of the request to sending the last part of the request. The preset value is 30 s.|
|Delay between requests or between parts of long request||Enables/disables to insert delays between requests. When receiving a long request consisting of several parts, a delay in inserted between individual parts of the receiving request. When sending a long request consisting of several parts, a delay is inserted between every transmitted part of the request. This means that a short request with a short response (receiving the request in one part, and sending the response in one part) includes one delay, namely after sending (serves for separation of various requests).|
|Delay (ms)||The size of inserted delay in ms. The accuracy is about 10 ms.|
|Strict mode of network users login into the application requiring the use of both name and password||Enables/disables the strict login mode of the network users. The strict mode is recommended, because in this mode the application behavior is simpler and unambiguous. The configurator defines the behavior of the PROMOTIC Web server for network requests without the name and password. Explanation of the differences between the strict and non-strict mode see There are the following rules for PROMOTIC server.|