wM8.2.1 migration of trading networks from 6.5

Hi guys,

I am doing a migration from 6.5 to 8.2.1 and I want to preserve the TN data.

So as described on the docs I run the migration tool. This is the log I get;

Deleting unused properties from file config\server.cnf…
File config\server.cnf does not contain any unused properties.
Created backup of file D:\WMFE8\IntegrationServer\config\is_jaas.cnf at D:\WMFE8
\IntegrationServer\migrationbackup\config\is_jaas.cnf.
Deleting unused properties from file config\server.cnf…
File config\server.cnf does not contain any unused properties.
Deleting unused properties from file config\server.cnf…
File config\server.cnf does not contain any unused properties.
Migrating Trading Networks data.
found null last-changed date, using default
found null expire interval, using default
savePassword(nullTestTNConnection,password) - found a NULL pw mgr
The value of the tn.default.idType property is not defined in the database.

An error occurred during the migration. Error message is The value of the tn.default.idType property is not defined in the database.

So does anybody hppens to know where is this field set in the db (tn.default.idType)?

I mean I could change it on the properties but this is the production server so I don’t wan’t to make an outage on this…

Thanks in advance;

What currently you have set in the TN properties file for this:

tn.default.idType = DUNS ??

Do you have this setting in the file or missing? Try to reload WmTN package after the
update…It shouldn’t effect adverse but do this change/reload during some downtime:

HTH,
RMG

Hi rmg,

That’s what I want so set the property like that but I’m affraid that won’t be enough and then I need to add another config property, and more downtime…

Have to check if the reload won’t be a problem!

Thanks for your help!

Yes it won’t hurt anything change…And always do take a backup file before any changes.

But one thing during reload WmTN while business hours it can disturb inflight transactions…So that’s why you need pick some downtime (weekends) and reload the package especially when dealing with production servers.

In any case changes to the properties file need reload or restart TN server.

Ok it worked only with package loading! Thread can be closed.

Cheers,

good deal…Luis