This procedure is almost the same as backing up, except the files must be pasted and not copied.
Restoring the OpenERP Server configuration file: Copy openerp-server.conf file from your backup location. Paste it into C:\Program Files (x86)\msf\Unifield\Server to replace it.
Restoring the OpenERP Web configuration file. Copy openerp-web.cfg and openerp-web-oc.cfg files from your backup location. Paste it into C:\Program Files (x86)\msf\Unifield\Web\conf to replace it.
Restart the Openerp services to finalize the replacements.
8.2 Backing up the Local Instance Configuration Files.
This step must be performed each time the super admin password has been modified. It should be the case right after the installation.
Copy the configuration file openerp-server.conf in your backup directory. The file could find it in C:\Program Files (x86)\msf\Unifield\Server
Copy the configuration file openerp-web.cfg and openerp-web-oc.cfg in your backup directory. The file could find it in C:\ProgramFilesx86)\msf\Unifield\Web\conf
Thanks to the synchronization rules, not all the data are synchronized with the synchronization server. This means that the synchronization server is not a backup solution. To avoid data loss because of a crash or any other problems, backups must be created to save 2 kinds of data:
Data not supposed to be synchronized
Data not pushed yet
Backups must not be saved in the local instance’s hard drive as it could be lost if the hard drive crashes or if the machine gets stolen. As for confidentiality issues, if one comes into possession of a backup, she/he would have access to all the information saved into the database backup and would be able to read it. However, she/he will not be able to synchronize data with the synchronization server if she/he does not also possess the synchronization password or if the instance has been invalidated at the synchronization server level. The UniField backup and restore password should be complex and be transmitted only to key staff. There should be a safe place with:
the All-in-one used for the installation
the configuration files after having changed the super admin password (normally done after the installation)
To be able to backup and restore the database, one must possess the UniField backup and restore password. PLEASE NOTE backups are under OCs responsibility according to their respective policies. The Support Team is not responsible for any lost backup. It is strongly recommended to configure the automatic backup in your instance to avoid running manual backups.
Click on Menu Administration 1, Translations 2, Languages 3 Choose the language you would like to activate by clicking on the blue arrow 4
Click Ok 1to validate the activation of this new language.
Installing a new language takes time. The interface won’t be fully translated before the translation process is over. You can check that the language is fully translated in menu Administration 1, Translations 2, Import / Export 3, Translations Requests 4. Only translation requests displayed in this interface can be considered as finished.
Then open UniField’s preferences by clicking at the small cogwheel icon 1 at the top right of the screen.
Select the language you would like to use – in our example “MSF French” 1. Only the active languages are available in this select box.
UniField has only one active language. However, three languages are loaded by default. You can activate another one in the interface. This section describes how to activate and use a different language.
6.2 Automatic Patching of Instances – Silent Upgrade
Silent upgrade is a feature that allows an instance under specific configuration to upgrade automatically when a new patch is avaialbe. There is no human intervention during the upgrade process. Please note that the silent upgrade will be performed only if an automatic synchronization has been configured during the time slot defined in the silent upgrade. General note: the instance upgrade is detected during the initial process of the synchronization (manual or automatic).
Go to Menu Synchronization, Registration, Connection Manager and click on the edit icon of your connection. Edit thefollowing fields:
Silent upgrade 1: tick the box
Upgrade from? 2: Start time of the slot during which the instance will be patched automatically.
Upgrade until? 3: End time of the slot during which the instance will be patched automatically.
Click on Connect 4 – state switches to connected Click on Save 5
When someone synchronizes an instance, he/she may be warned that an update is available. There are two kinds of updates:
Required: The synchronization feature is disabled as long as the update is not applied. Most of the time they are required.
Optional: The synchronization feature remains enabled and the update can be applied right away or later. In any cases, it will be applied when a required update is pushed to the instance.
Before the upgrade it is advise to:
back up the database (will be done anyway by the system befor the upgrade)
inform the users that an update is going to be installed and that they must stop working until further notice
Please keep in mind that we strongly encourage you to make a backup before and after any upgrade . If you don’t do that, it would be harder to recover from a crash during the upgrade. See backup configuration for an automatic backup before patching
When trying a manual synchronisation by pressing the Start All Synchronization in Background button 1 the following message will appear. Click OK 2 Back to the manual synchronization menu Close it.
You will notice the following message displayed on the top-right of your screen.
Click on Menu Synchronization 1, Patch Synchronization 2, Upgrade 3
A pop up window opens. Click on Download 1 Instance restarts when Upgrade is clicked. It would prevent users from going on with their work. As a result, you should warn your colleagues about the unavailability of UniField. Click on Upgrade 2
The instance is restarting to apply the changes.
When it is done you would need to log in again and re-connect back your instance to the SYNC_SERVER (unless you use the auto-connect feature) If you forget to do that, the automatic synchronization won’t be launched. Refer to the Connection manager configuration. Inform the users that they can resume their work
One of the main features of UniField is to deploy upgrades easily. To achieve that, the SYNC_SERVER acts as a patch repository. Every instance that is not up-to-date downloads the patches it needs and applies them locally. This check and the upgrade process are done every time an instance synchronizes.
5.6 Verify the Status of pull and push of Synchronized Entries (only at sync_server instance)
Click on the menu Administration 1, Synchronistaion 2, Monitoring 3, Data Monitor or Message Monitor 4. You will see all the data or messages that have been pushed and pulled between instances via the synchronization server.
Click on a line in this list view to display the instance that pushed the entry to the server and the instances that pulled this entry from the server.
We use cookies to ensure that we give you the best experience on our website. If you continue to use this site we will assume that you are happy with it.
