--- title: "Remote Systems (off line)" canonical: "https://wiki.soft1.eu/space/SS5EN/1236174361/Remote%20Systems%20(off%20line)" format: markdown --- ## Introduction Remote system module can be used in installations at remote areas in order to run basic application functions in the event of interruption of the connection with Application server and central database. Each local installation operates under normal conditions at online mode (connected to the central system). When a communication breakdown occurs between central system and local installation, the local computer automatically tries to connect to a "local backup database" maintained at the branch. When the system operates in off-line mode, users have the possibility to post a limited range type of documents ensuring the smooth operation at the branch. When the connection is restored, the central database is automatically synchronized with data posted in "local backup database" ## Restrictions For the proper operation in offline environment, the data on the branch must be synchronized based on the last synchronization file of the central system. So entries posted into the central system by this time until the breakdown in communication, are not available at the branch. The data synchronized are the necessary to operate the branch in a state of "emergency" and not the full data of the installation. That is, when at Off-line mode there are no customers and items balances , previous documents and can not be printed reports based on transactions. Off-line job is designed to support operations of the branch such as ongoing sales , there are no queues and delays, and can be printed legitimate sales documents. Under no circumstances the full operation of the application can be substituted. Activation process for off-line mode includes a series of configuration steps, which must be executed both on the Application server and the remote workstations (clients). ## Configuration ### Document Series used in off line mode In all document Series (purchases, sales, cash trasnaction) used in any branch, which are available for off line posting of documents, it is necessary to enter the Branch in their data. **Attention:** Remote system function requires that each branch uses distinct document Series. Document Series without branch information in their data, that are used for posting documents in more than one company branches, shall not be available in off line operation. ### Users per Branch For users, you need to define the branch to which they have access. **► Info:** Out of the users defined as branch users, some must be appointed as responsible for synchronization – the selection is performed through the Off line installation parameters. ### Activation Mechanism (performed once only per branch/remote area) In order for the mechanism to be available, you must enter the related operation parameters at each remote area (branch) as follows: 1. Procedure for determining the "local backup database" (auxiliary database type) and the user responsible for synchronization. In System menu select Off line Jobs >  Off line installation parameters. ![image](media://9d735fc2-70d1-4e53-811f-c7453587e622)     2. On the screen displayed, select the user responsible for the synchronization between the auxiliary database type and central database, selecting anyone of the company users. Then, define the auxiliary database type. ![image](media://a2780afe-f673-428d-937c-1d0f668a265d)     3. On the next screen define the name of the server, on which the auxiliary database is to be created, as well as the user name and password for the server ![image](media://e13f345f-4d23-4be5-af5f-8c286c536740)     4. Complete the process entering the name and collation of the auxiliary database. ![image](media://d1ee4646-8eb2-4f3c-b883-f4b7b4b2d246) **► Info:** The above process is executed once in each local installation. As soon as configuration completes, parameter is activated on the first login screen of the application. **► Info: **The user defined as responsible for synchronization must  have access to the specific company and the specific branch. ### Local database synchronization Before cretaing the local backup database you need to create the file which will be used to synchronize it.  In System menu select off line Jobs > Create file for local synchronization. On the screen displayed, enter the name and location of the file to be generated. **Attention: **the path defined for file saving must be accessible, under the same name, by the Application server too.If you do not select a storage path, the file is saved on the terminal on which application server is installed. ![image](media://908c3c3b-5642-402b-b65d-2f33fee87c8b) ► **Info**: The user that creates the synchronization file must be the administrator. ► **Info:** The file created must contain all configuration data, the master files, and the print reports necessary for executing functions in off line status. ► **Info: **Upon completion of the process, you shall notice that .xco files includes now data that concern the off line process and the auxiliary database data. ► **Info: **Synchronization file generation is performed through the server. ### Create local database Login to the system as the user defined as responsible for the synchronization of the local installation. In System menu select: Off line jobs > Create local installation in order to create the database. ![image](media://c3c167b7-e183-4463-b42f-54dc772cf06f) **Synchronization methods** - **From the central database:** if the file generated was stored in the folder containing SOFT1 files (application server) then update (download) of the file from the central installation shall be performed automatically. - **From data file: **select the file generated that is stored locally on your computer. ## Local database operation. ### Off line operation Branch users login and work online. If, for any reason, connection to the application server is interrupted, a message is displayed on the client so that the user can select either offline system operation, or to exit the application. ![image](media://ffccecae-3135-4b80-9a09-cb94f4029e3d) If the user  selects , the client connects automatically to the local database. ►** Info:** The status bar of the application, displays the offline status of the workstation. The user can post certain type of entries throughout the period that the workstation is in OffLine status. ### Central database synchronization When connection to the application server is restored,a message is displayed automatically: If the user selects , the application displays a new message requesting confirmation in order to update the central database with the entries made while the client was in Off line operation status. If you select [Yes], a new information message is displayed, and pressing [Yes] to it launches the process for the synchronization of the two databases –local and central. ![image](media://8b42037b-300e-4e36-b8d0-fe5b978f13ce) ![image](media://908c3c3b-5642-402b-b65d-2f33fee87c8b) ►** Info: **The status bar shows the central database update progress. ►** Info:** It is not recommended to exist the application during synchronization. If the user exit the application during synchronization, the application shall display the relevant message: ### Local database synchronization During client login, the local database is updated automatically with the changes performed online (there is no need to generate a file from the central installation). However, if the user wishes to synchronize local installation, he may select Off line jobs > Synchronize local database available through system settings. **► Info: **Local database synchronization using the central installation is performed automatically, without requirement to generate a synchronization file. Synchronization is performed every 5 hours. **► Info:** Changes are performed according to the configuration of offupd.ini file. **► Info: **File offupd.ini must be stored on each client. **► Info: **If you wish to modify file offupd.ini, then you must save it with the name offupdcustom.ini **Outprocess in Offline mode** To connect the application in offline mode suffices to add parameter FORCEOFFLINE = 1 in section [APPLICATION] of xco. Alternatively it may be added to the command line the parameter / FORCEOFFLINE: 1. Attention: if you set at xco the parameter  FORCEOFFLINE = 1, then the application considers that it is always in offline mode ( regardless if you have selected not to operate offline during the login process. ## Important comments ► The installation can operate in OffLine mode for up to 3 days without any certification request by the License Manager. A necessary precondition is to perform at least one connection to the Online database. ► Special attention must be paid to the codification of customers /items /suppliers (master files), if there is possibility of generation thereof in offline operation. Example of the code format of customer file: First digit indicates connection status. Thus, when the user is Online in standalone or client environment, value 0 is set. For Offline status value 1 is set. The parameter-type code format must include the following: 1 to 1 with formula:  IF(CONNECTIONSTATUS=4,1,0) ## Automations The offline process can be automated with the parameters: - HASOFFLINERECORDS=0,1,2   //Update central database with offline entries (Message: "There are entries in the local database which have not been transferred to the central. Sync now?" (0: Question,  1: option [Yes] is selected,  2: option [No] is selected) - OFFLINECONNECT=0,1          //switch to offline mode without questions (1: connect, otherwise question) - ONLINECONNECT=0,1           //switch to online mode without questions (1: connect, otherwise question) - ONLINEUPDATE=0,1,2           //Regard to the message "This operation will update the central database with the entries posted in the local installation." (0: Question,  1: option [Yes] is selected,  2: option [No] is selected) These parameters are added to the OFFLINE section of the xco. file eg. [OFFLINE] TYPE=MSSQL SERVER=SOFT1 DATABASE=SOFT1_onoff USER=sa PASSWORD=#Xcx`D@h@GK@ LANGID=1 SYNCUSER=60 HASOFFLINERECORDS=1 OFFLINECONNECT=1 ONLINECONNECT=1