Open navigation

Gespage V8 > V9 Migration

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

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


Contents



ATTENTION ! It is necessary that your server is up to date with the latest version of Gespage v8 (v8.2.7) before carrying out the update steps to version v9.


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

Prior update of the database

It is necessary to update the database schema before installing Gespage v9.

To carry out this update, it is necessary to retrieve the zip Gespage_update_V9.zip as an attachment to this article.

You must copy the recovered zip, then extract it.

After extracting the zip, you must execute the Gespage_update_BDD.exe file.

 


Database backup

You must then 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

You must then uninstall Gespage V8 and Postgres 12.


Installing Gespage v9

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


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. o changes to be made.


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

After updating Gespage, you must connect to the web interface of each MFP in order to update the Sharp OSA links.

Two links need to be updated.

The connection interface address link to include the copier serial number. Example :

    https://Gespage_IP:7181/embedded/sharp/login-n2.xhtml?id=XXXXXXXXXX

The application UI address link to include the copier serial number. Example :

    https://Gespage_IP:7181/embedded/sharp/welcome?id=XXXXXXXXXX


Toshiba

If the initial configuration of your MFPs was not in HTTPS mode (which required the installation of certificates on the MFPs before Gespage v9), you must push the authentication again on each MFP.


Indeed, on version 9 of Gespage, only HTTPS can be used for authentication.



Xerox

No changes to be made.

 

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.