Web

The settings relating to the requirements for the web server can be made via this dialog.

The adjustments are adopted during operation and also adjusted in the associated XML configuration so that they are applied again after a system restart

►NOTE◄ If changes are made at this point, the web server is restarted in the background, causing the connection to be lost and then re-established. If the URL or port is changed, it may be necessary to re-enter the URL.

images/download/attachments/167859381/image-2024-1-19_14-31-7-version-1-modificationdate-1705671067269-api-v2.png

#	Description
1	Adapts the configuration of _pro, if necessary on all nodes of a cluster, and maintains it in the associated XML configuration.
2	Determines whether _pro is operated on a separate web server or is stored on the same web server as _data.
3¹	If _pro is operated separately, the individual configuration (pro.xml) must be defined. The directory can be defined by specifying the Pro-Home directory using the variable "${pro.home}". The configuration file used must exist on the file system of the host or all nodes of a cluster and be readable.
4¹	If _pro is operated separately, the server port must be defined. Among other things, this must be different from the _data port.
5¹	If _pro is operated separately, the maximum and minimum number of server threads must be specified.
6	URL path under which the application should be accessible. If _pro is operated separately (2), the context can be set to '/'. If it is not a stand-alone server, a different path (e.g. '/_pro') must be defined, as '/' is already used by _data.
7	Switching the GZIP compression of HTTP responses on or off.
8	Path to call up _data profiles (request)
9	Path to call up _data profiles (trigger)
10 11	Definition of the initial or own HTTP response headers.
12	Add the full list of recommended headers that in most cases result in a Grade A rating. E.g. "Access-Control-Allow-Origin" etc.

1) Only necessary if _pro is operated on a separate web server (2).