4D v16.3Management of connections by client applications |
||
|
4D v16.3
Management of connections by client applications
Management of connections by client applications
The management of connections by client applications covers the mechanisms by which a merged client application connects to the target server, once it is in its production environment. Starting with 4D v15 R4, these mechanisms have been modified in order to provide more control to the developer and more flexibility in case of connection error. The mechanisms available beginning with 4D v15 R4 described on this page are enabled only when the Use new architecture for application deployments option on the "Compatibility" page of the Database Settings dialog box is checked (see the Compatibility page section). The connection procedure for merged client applications supports cases where the dedicated server is not available. The startup scenario for a 4D client application is the following:
The last used and validated server path is automatically saved in a file named lastServer.xml in the application's user preferences folder. This folder is stored at the following location: userPrefs:=Get 4D folder(Active 4D Folder) Compatibility note: When this compatibility option is not checked (see the Compatibility section), the path is not saved. This mechanism addresses the case where the primary targeted server is temporary unavailable for some reason (maintenance mode for example). When this case occurs for the first time, the server selection dialog box is displayed (if allowed, see below) and the user can manually select an alternate server, whose path is then saved if the connection is successful. Any subsequent unavailability would be handled automatically through the lastServer.xml path information. Notes:
You can choose whether or not to display the standard server selection dialog box on merged client applications when the server cannot be reached. In this case, the configuration depends on the Use new architecture for application deployments compatibility option (see the Compatibility section) as well as the value of the ServerSelectionAllowed XML key on the machine where the application was built. There are three possibilities:
Note: For more information about the ServerSelectionAllowed XML key, refer to its description in the 4D XML Keys BuildApplication manual.
See also
|
PROPERTIES
Product: 4D
HISTORY
Modified: 4D v15 R4 ARTICLE USAGE
4D Design Reference ( 4D v16) |