ONLINE HELP
 WINDEV, WEBDEV AND WINDEV MOBILE
Help / WEBDEV administrator / WEBDEV Application Server administrator / 08. Appendix 3: Registry
  • Overview
  • Configuration
WINDEV
WindowsLinuxUniversal Windows 10 AppJavaReports and QueriesUser code (UMC)
WEBDEV
WindowsLinuxPHPWEBDEV - Browser code
WINDEV Mobile
AndroidAndroid Widget iPhone/iPadIOS WidgetApple WatchMac CatalystUniversal Windows 10 App
Others
Stored procedures
Overview
When installing a WEBDEV site on a Windows server, the indications regarding the site are automatically inserted into the registry, at the following entry:
HKEY_LOCAL_MACHINE/SOFTWARE/PC SOFT/WEBDEV/29.0/Application/<SiteName>
Where <SiteName> is the name of installed site.
When installing a WEBDEV site on a Linux server, the indications regarding the site are automatically saved to the following configuration file:
/etc/PC SOFT/WEBDEV/29.0/Applications/<SiteName>.conf
Where <SiteName> is the name of installed site. This name complies with the case used for the project name.
When installing a SOAP Webservice on a Windows server, the indications regarding the Webservice are automatically inserted into the registry, at the following entry:
HKEY_LOCAL_MACHINE/SOFTWARE/PC SOFT/WEBDEV/29.0/Webservices/<WebserviceName>
Where <WebserviceName> is the name of installed Webservice.
When installing a SOAP Webservice on a Linux server, the indications regarding the Webservice are automatically saved in the following configuration file:
/etc/PC SOFT/WEBDEV/29.0/Webservices/<WebserviceName>.conf
Where <WebserviceName> is the name of installed Webservice. This name complies with the case used for the project name.
When installing a REST Webservice on a Windows server, the indications regarding the REST Webservice are automatically inserted into the registry, at the following entry:
HKEY_LOCAL_MACHINE/SOFTWARE/PC SOFT/WEBDEV/29.0/RESTWebservices/<RESTWebserviceName>
Where <RESTWebserviceName> is the name of installed REST Webservice.
When installing a REST Webservice on a Linux server, the indications regarding the REST Webservice are automatically saved in the following configuration file:
/etc/PC SOFT/WEBDEV/29.0/RESTWebservices/<RESTWebserviceName>.conf
Where <RESTWebserviceName> is the name of installed REST Webservice. This name complies with the case used for the project name.
Remarks:
  • The different entries in the registry and in the configuration file are given for information only and they allow you to check whether a WEBDEV site is installed properly.
  • These entries are automatically configured when installing a WEBDEV site or a Webservice.
  • Caution: The site or Webservice name is case-sensitive. This parameter must not be modified.
Configuration
The entries in the registry are as follows:
APPLICATIONMULTIPLE Indicates whether the same application can be deployed on several virtual sites.
APPLICATIONNAME Name of application in deployment.
CACHED_SESSIONSNumber of cached sessions for this application.
COOKIE_SESSION_HTTPONLY Enable the option "httponly" for the session cookie of AWP sessions.
ERRORFILEFull name of HTML file that will be used to display the error messages.
GPUHISTOCNXIndicates whether the User Groupware must save the history of connections.
GPUPATHLocation of common data files (HFSQL Classic) of User Groupware (full path).
GPUPATH_RLocation of data files of the User Groupware rights (HFSQL Classic) for the site or Webservice (full path).
HFPATHLocation of data files (HFSQL Classic) of WEBDEV site/Webservice (full path).
HTTPSUsed to specify whether the connection to the site is using an HTTPS connection exclusively.
LOGDIRLocation of WEBDEV site/Webservice access statistics files (full path).
LOCKFORUPDATE Indicates whether the connection to the site or Webservice is blocked for an update.
NOIPCHECK If this key is missing or if it is different from 0, the calling IP address will not be checked: this IP address can change during the session. If this key is found and if it is equal to 0, the IP address of user must not change during the session.
ONERROR_AUTORECONNECT Indicates whether the automatic reconnection is allowed in case of "BAD CONTEXT".
ONERROR_AUTORECONNECTTIME Time (in seconds) before the automatic reconnection in case of "BAD CONTEXT"
MAXCONNECTAPPMaximum number of connections to the site or Webservice (defined in the WEBDEV administrator).
MAXRECONNECTAPPMaximum number of simultaneous accesses to the same site by the same Web user (defined in the WEBDEV administrator).
PROJECTERRORFILE Name of static page defined in the project as template for the error page.
PROJECTPATHPath of site files or Webservice files.
PROJECTNAME Name of site or Webservice (it is the project name if the site was deployed under a different name).
RECONNECTMESSAGE Text of link to display when the user is allowed to reconnect to an application.
SAAS_ADMINISTRATION_URL (SaaS) URL of SaaS management site for the application.
SAAS_WEBSERVICE_URL (SaaS) URL of SaaS webservice that will be used by the application.
SSLADMIN Used to specify whether an https connection is required for the management sites.
TIMEOUT_NORQ Timeout before disconnecting the Web user if no new request is received (defined in the WEBDEV administrator).
TIMEOUT_TASKS Maximum duration for the background tasks and scheduled tasks.
VERSIONSite version.
VIMAGEDIRVirtual directory of site images.
VIRTUALHOSTHost header name of virtual Web site where a site or a Webservice is deployed.
WEBSERVICE_DESCRIPTIONUsed to specify whether the Webservice description is public (1) or not (0).
See also
Minimum version required
  • Version 9
Comments
Click [Add] to post a comment

Last update: 05/26/2022

Send a report | Local help