This document's purpose is to describe the complete procedure for a Gespage migration on Windows Servers.
You must first find if you have a standard version or a standalone one. If the folder 'Gespage\GespageCore\server\payaraX' doesn't exists, it means you have the standard version. Some steps will be different depending on that information, please make sure to stick to the steps you should follow when this document indicates differences between thoses two versions.
I. Preparations and update before migrating
1. Check Gespage's version
|You can check your Gespage's version by accessing the admin login page. Your current version is specified at the bottom.|
You'll have to update Gespage on your currently running server to correctly prepare the migration.
Updating resets some things, it is crucial to make some verifications first.
2. Gespage Mobile and how to migrate it
|Updating Gespage resets some of Gespage Mobile's configuration. To make sure you don't forget anything when migrating to the new server, you'll have to check the 'gespage.war' folder.|
If it currently is in 'C:\Program Files\Gespage\GespageCore\server\lib\deploy', then nothing specific has to be done while migrating regarding this file. However, if it's current directory is 'C:\Program Files\Gespage\GespageCore\server\lib\deploy\external', this configuration has to be replicated on the new server (copy/paste the file one level deeper)
3. Get my DB data
For your Gespage re-installation, knowing where your database runs is extremely important. More often than not, it is local to the server.
An installer for PGAdmin is embedded into Gespage's executable. The default installation folder is 'C:\Program Files'. If a folder named 'PostgreSQL' exists, it means your DB is installed locally.
If no folder is found, it probably means it was installed somewhere else, or that it is using a non-default configuration.
You'll have to find your database if you decided not to use the one Gespage could have installed. Getting thoses parameters for the new server will only be possible by you or someone else that knows your company's network architecture.
It is highly recommended to backup your whole Gespage directory or to take a snapshot of yoserver. If the new version happen to be incompatible, you'll have a way to go back to it's old state.
You'll now have to download the correct version of Gespage (the .exe works for both installs and updates).
Updating is mandatory since you'll need a save from the same version to migrate a server and import data from the old to newer server.
Once your original Gespage has been updated, your next steps consists in making a save file that'll contain most of your data.
To do so, head to your old server's Gespage admin web page and go to 'Server > System > Backup/Restore'.
The save can be found at 'C:\Program Files\Gespage\GespageCore\db\postgresql\save'
II. Setting up Gespage on the new server
1. Import your save
To restore a previous DB save, you first need to make sure the save file comes from the same gespage version. Your old server needs to be updated if you used this opportunity to install the last gespage available on your new server.
The save file created during step 1.4, a DB save dump, is to be send on your new server. Once copied, head to gespage's admin page and go to 'Server>System>Backup/Restore' to fully restore your DB.
To make sure everything went smoothly, you can load the Account and Printer pages and confirm you didn't lose any data.
It is strongly advised to keep the same server IP address on your new server. Doing so, you avoid thoses next steps:
(eTerminal manuals can be found at support.gespage.com, each brand has it's own.)
2. Import other data
Then you must copy the following files/folder from the old server to the new one:
4. Advanced Scan (Optionnal)
Among the configuration of the old server which does not rely on the DB, we will also find the temporary directory used by the advanced scan.
On admin page, go to 'Server>Document flow>Scan profiles>Settings'.
If a network folder is specified, and it is still shared on the old server (test done with Windows Explorer), you will need to make sure to recreate a shared folder on the new server.
Moreover, if OCR processing is present, tesseract will also have to be installed on the new server.