Migration > Migrating Electronic Signature

Migrating from Electronic Signature 2.8.0 SP1 to Electronic Signature 2.9

Introduction

This topic explains how to migrate from Electronic Signature 2.8.0 SP1 to Electronic Signature 2.9.

Migration procedure

Stop Electronic Signature.
Back up the existing installation folder.
Back up the database.
Enter one of the following commands to run Axway Installer in Update mode:
GUI mode
- UNIX: update.sh
- Windows: In the Windows Start menu, select Programs > Axway Software > Axway Synchrony [version] > Update
Console mode
- UNIX: update.sh --mode console
- Windows: update64.exe or update32.bat --mode console
In the Updates management screen, select the Electronic Signature product to update and click on the Add Updates button.
The Open dialog is displayed.
Select the downloaded upgrade pack and click Open.
The selected update is added to the list in green.
- To modify an update, click the name. The update changes to blue.
- To remove the update, click Remove.
- To get information on the update, click Info.
Click Next and review the upgrade pack you want to install and then click Update to begin installing.
Review and click OK to exit the installer.
Update the properties in the configuration.properties file (as described below).
Update the config script located in <ES 290 directory>\ElectronicSignature\bin\ (as described below in "Updating the config script").
If the reject or signature exit is activated, update the configuration.properties file to reference the new fex-es-exit-sample.jar delivered in <ES 290 directory>\ElectronicSignature\devKit\exit\.
At the end of the update, restore the following files (from your backup) to the 2.9.0 installation:
<backup directory>\ElectronicSignature\apps\ui\config.cfg to <ES 290 directory>\ElectronicSignature\apps\ui\
Restart Electronic Signature. It has now been updated to 2.9.

Note

If the product was installed with the option "Generate scripts only" instead of "Generate and lauch scripts" then the upgrade pack will not update the database. The migration script will be copied in <ES 290 directory>\ElectronicSignature\database\[oracle or mysql]\scripts\1\table_migrate_2.9.0.sql and it will have to be executed manually.

Updating the configuration.properties file

This section describes some new properties in the Electronic Signature configuration.properties file. After migrating you should check, and if necessary update, the following properties.

ebics.signatureList

# List of allowed Signature protocols separated by comma.

# Supported Signature protocols are:

A005:CERTIFICATE,A006:CERTIFICATE,A005:KEYPAIR,A006:KEYPAIR,A004:KEYPAIR ebics.signatureList=A005:CERTIFICATE

sentinel.trackedObjectName

# Sentinel object to be tracked

sentinel.trackedObjectName=XFBTransfer

sentinel.trackedObjectVersion

# Sentinel object to be tracked

sentinel.trackedObjectVersion=3.9

Updating the config script

Windows:

In the config.bat file add the following line under the TRACKINGOBJECT declaration:

set TRACKINGOBJECTVERSION=3.9

UNIX:

In the config file add the following line under the TRACKINGOBJECT declaration:

TRACKINGOBJECTVERSION=3.9