This page describe the two-steps procedure to perform a copy of the ECtrans Associations from one ECaccess Gateway to another.
The two-steps are:
- Export and Decryption of the ECtrans Associations from the existing ECaccess Gateway.
- Encryption and Import of the ECtrans Associations into the new ECaccess Gateway.
Because each Gateway has its own private-key for encryption it is required to decrypt and re-encrypt the ECtrans Associations with the relevant private-key.
Before to follow the procedure, please first download the following files and copy them into the mentioned directories:
- upgrade.jar: in both "bin" directories of the existing and new Gateway.
- decrypt.sh: in the "bin" directory of the existing Gateway.
- encrypt.sh: in the "bin" directory of the new Gateway.
Also, on the new ECaccess Gateway, make sure the "gateway/db" directory is original (the one from the distribution) and remove any "private-key.keystore" from the "gateway/conf" directory. This is important to allow a smooth execution of the procedure.
Step 1
Go to the "bin" directory of the existing Gateway and make sure it is not running:
#./gateway stop
Then start the export/decryption of the ECtrans Associations:
#./decrypt.sh
If the script complete successfully, a file named "uncrypted-assoc.sql" is created in the current directory with the ECtrans Associations in clear text.
Just move this file to the "bin" directory of the new Gateway.
Step 2
Go to the "bin" directory of the new Gateway and make sure it is not running:
#./gateway stop
Then start the encryption of the ECtrans Associations:
#./encrypt.sh
If the script complete successfully, a file named "ecaccess.script" is created in the current directory with the encrypted ECtrans Associations.
Copy this file to the "gateway/db" directory:
#cp ./ecaccess.script ../db/.
And start the Gateway:
#./gateway start