Below you will find the Gespage v8 > v9 migration procedure.

A FAQ is also available in the FAQ Gespage v8 > v9 migration article.

Contents

• Migration prerequisites
• Gespage server application upgrade procedure
• eTerminal upgrade procedure
• Licence upgrade procedure

ATTENTION! The migration from v8 to v9 is a major update. It must be carried out with the assistance of a technician trained on Gespage.

Migration prerequisites

The following points must be checked prior to the start of the migration:

• It is necessary that your server meets the installation prerequisites for Gespage v9 (see Gespage v9 Prerequisites), especially the hardware requirements.
• It is necessary to verify the compatibility of the MFPs in your fleet with Gespage v9. Indeed, some older MFP ranges are no longer compatible with v9 eTerminals.

Moreover, before starting the migration to Gespage v9, your server must be updated to the latest v8 version (v8.2.7).

Gespage server application upgrade procedure

The update procedure below describes the case of a standard configuration with the PostgreSQL database included as standard in Gespage.

In case of MS-SQL database, please contact Gespage support.

Saving the configuration
 

Before carrying out the update steps, it is necessary to save certain elements.

If the server is virtualized, I invite you to take a snapshot of the VM before carrying out the different steps.

It is possible that some Gespage files were customized when Gespage was first installed. These files should not be impacted by the Gespage update, it is still preferable to back them up beforehand.

Possible custom files are:

• AD synchronization customization script. This script is called LDAPImport.groovy and is located under the directory C:\Program Files\Gespage\GespageCore\server\resources\scripts
• Save the keystore.jks and cacert.jks files in the C:\Program Files\Gespage\GespageCore\server\config directory, these files may contain a certificate for the application's https access.

Performing the update

Database backup

You must save Gespage database

This action is carried out via the Gespage administration page under the Server\System\Backup tab:

The backup file is then available on the server in the folder (default location) : 

    C:\Program Files\Gespage\GespageCore\db\postgresql\save

Uninstalling Gespage v8 and PostgreSQL (Windows)

You must then uninstall Gespage V8 and Postgres 12.

Installing Gespage v9 (Windows)

Then, you must launch the Gespage v9 installer, specifying that this is the installation of a new server:

Installing  Gespage v9 (Linux) 

On Gespage v9, the supported distributions are both Debian and Ubuntu. The minimum versions supported are Debian 11 and Ubuntu 20.04.

If you are using an older distribution version, we recommend installing a new server for the Gespage migration process.

For installing Gespage on Debian, please see the new article : FAQ Install Gespage v9 on Linux

Import database backup

Once the installation is complete, all you have to do is import your backup to the new database via the Gespage administration page in the System\Restoration menu:

Or by selecting a restoration date :

eTerminal upgrade procedure

An eTerminal update procedure may be necessary depending on the eTerminal brand.

For more details on the configuration of each eTerminal on Gespage v9, you can consult the corresponding eTerminal manual.

Brother

After updating Gespage, you must connect to the web interface of each MFP in order to update the connection link to Gespage to include the serial number of the MFP and check that the link is HTTPS:

    https://Gespage_IP:7181/pserver/rs/BSI/start?prod=brother&id=XXXXXXXXXXXXXXX

Canon

Normally no configuration changes are necessary.

However, if authentifcation does not work, you must check that the connection to the Gespage server is HTTPS.

This check is done from the URL http://@IP_COPIEUR:8000/Gespage

Epson

After updating Gespage, you must connect to the web interface or each MFP in order to update the connection link to Gespage to include the serial number of the copier on the URL of the page before connection and check that the link is HTTPS:

    https://Gespage_IP:7181/device/embedded/epson/ISV?id=XXXXXXXXXX

HP

You must push the configuration of each eTerminal from Gespage.

Konica Minolta

No configuration changes are necessary.

Kyocera

You must check that the connection to the Gespage server is HTTPS.

This can be done directly from the copier screen, or via the following URL:

http://IP_COPIEUR:8080/GespageKyocera/jsp/wide/setup.jsp

Lexmark

No configuration changes are necessary.

However, if authentifcation does not work, you must ensure that the port of the Gespage application is HTTPS in the Lexmark applications menu.

Ricoh

Normally no configuration changes are necessary.

However, if authentifcation does not work, you will need to reinstall the Gespage application package to configure it in HTTPS.

If many machines are affected, Gespage support can provide an application update script.

Sharp

No configuration changes are necessary.

Toshiba

You must push the Toshiba eTerminal configuration on each MFP.

Beware, since version 9 of Gespage, o Toshiba eTerminal communication is configured by default in HTTPS.

Xerox

No changes to be made on the Terminal configuration.

Licence upgrade procedure

The Gespage license installed on your v8 server remains valid after the migration to v9.

However, certain cases listed below require a license update:

Web payment

The web payment license has to be reinstalled after migration (new license format).

Xerox

The Xerox eTerminal license has to be reinstalled after migration (new license format).