Problem

The unique IDs format has been changed between 3.6.0 SP9 (B2Bi 1.5.0_SP8) and 3.6.0 SP10 (B2Bi 1.5.0_SP9).

So when Integrator 3.6.0 SP10 is removed, the IDs won’t be able to be parsed at runtime (as they are not rolled back to the old format when the SP is uninstalled) : 

ERROR  :20131119:15.42.01.22:procengine(procengine(transadaptenv)):UNIQUE.LIST: the contents of unique ID file "/opt/axway/b2bi/shared/b2bi/data/unique/transferid.unq" is invalid

ERROR  :20131119:15.42.01.22:procengine(procengine(transadaptenv)):failed to create tag 'TransferId' in file '/opt/axway/b2bi/shared/b2bi/data/unique/transferid.unq' for transfer id generation

The IDs are getting changed at first access, so customers might have some unique file IDs with the old format and some with the new one.

The change was to extend the ID name from 10 (in the example from below is <TransferId>) to 40 characters (the padding being done with space characters – ex : TransferId1210000000007200will be changed to TransferId              1210000000007300)

Resolution

-- A tool (attached) has been built by R&D.

-- use it in case you are using unique ids, and if you uninstalled Integrator 3.6.0 SP10.

-- Please find the instructions below :

Unique ID Files Migration

Because unique ID files (usually stored in $CORE_ROOT\data\unique\ known as path in the script command ) are not rolled back automatically when you perform uninstall, special scripts were created for this task.

New files: migrateUnique.bat, migrateUnique.sh, migrateUnique.x4

To run those scripts, make sure you have the Integrator environment set ( . .profile/ for Linux and profile.bat for Windows), Integrator is stopped, and the new scripts are in the same folder (usually in $CORE_ROOT/tool).

Windows

1. path       – performs a recursive downgrade for all files in <path> with “.unq” extension
2.       – performs a recursive upgrade for all files in <path> with “.unq” extension

Linux

First you have to give execute rights to the bash file, chmod 777 migrateUnique.sh

1. path      – performs a recursive downgrade for all files in <path> with “.unq” extension
2. path      – performs a recursive upgrade for all files in <path> with “.unq” extension

Manual migration (for files with a different extension)

r4edi migrateUnique.x4 -d filename – performs a recursive downgrade for <filename>

Example:

Linux:  ./migrateUnique.sh -u /home/xib2mnt4/Axway360_Synch45_SP10/Integrator/

Result: All unique files are updated from old ones to new ones. For example one file that I have ,  emailcorrelation.unq had previously the following content, “EmailMsgId04100100” after the script has been executed looks like: “EmailMsgId                     04100100”

When running with –d option, the downgrade is done from “EmailMsgId                     04100100” to “EmailMsgId04100100”.

Windows: migrateUnique.bat –d C:\Axway\Integrator

In B2Bi, the tool will have to be ran as:

For Linux :

./migrateUnique.sh  -d <$B2Bi_SHARED_DATA/unique path> and <$CORE_DATA/unique/>

./migrateUnique.sh  -d  /home/solution/Axway/Synchrony/Interchange/b2bi/data/unique/

./migrateUnique.sh  -d  /home/solution/Axway/Synchrony/Integrator/data/unique/

For Windows :

>migrateUnique.bat  -d <$B2Bi_SHARED_DATA/unique path> and <$CORE_DATA/unique/>

>migrateUnique.bat  -d  C:/Axway/Synchrony/Interchange/b2bi/data/unique/

>migrateUnique.bat  -d  C:/Axway/Synchrony/Integrator/data/unique/

Notes :

(1) Content length of each of the unique file is reduced back to original length.

(2) The original file(> 50 column length) is still present but the file name is modified and appended with .old extension.