Introduction / FirstSpirit Server configuration / Roll-out process for native applications / Updating the native system components

Roll-out process for native applications

Updating the native system components

The directories are synchronised by means of hash values which clearly describe the complete (operating system specific) sub-tree for each client application. This value is cached and saved in a CRC.TXT file, which is located in the respective application directory. This file exists on the client and server.

Server-side changes: Each time a change is made on the server, a new hash value is calculated which enables the client to recognise that a change has been made. The hash value must be removed manually if manual changes are made to the client application files on the server. This can be done by deleting the CRC.TXT file in the operating system-specific client application directory of the server, for example, in Windows operating systems under:
~FirstSpirit5\data\clientapp\jxbrowser4\windows\crc.txt
On establishing a connection with a client computer, the server recognises that the file is missing and automatically calculates a new hash value. This hash value is compared with the files of the workstation computer and then the update is started.

Client-side changes: The native system components are updated in one direction only; from the server to the client computer. This means that the client-side hash value is not recalculated if a manual change is made to the client-side client application files. The next time the client is restarted, the manual changes are therefore retained and are not synchronised with the server-side files (as both hash values are identical).

To reset inadvertent changes to the client-side client application files to the status of the server, firstly, the CRC.TXT file in the operating system specific client application directory of the workstation computer must be deleted, for example, in Windows operating systems under:

C:\Users\<USERNAME>\.firstspirit_5.2R1808\jxbrowser4\crc.txt

On establishing a connection with a server computer, the server now recognises that the file is missing and automatically starts to transfer the file system of the changed client applications from the server to the workstation computer concerned.

© 2005 - 2024 Crownpeak Technology GmbH | All rights reserved. | FirstSpirit 2024.7 | Data privacy