Warnings

The installer can help migrate an existing sedex Client to a new version, but it does not automatically do everything.

The warnings in this section must be taken seriously so that no messages are lost!

No migration to other hosts

The migration process currently does not support moving a sedex Client from one host to another. Migration is only supported within the file system of a single host.

Business applications and the messaging interface folders

If the messaging interface folders (outbox, inbox, etc.) are under the root folder of the current sedex Client and the sedex Client will be migrated to another root folder, a business application should be prevented from using the interface folders during the migration. Failing to do so will cause an inconsistent state and messages or receipts may be lost.

If a migration changes the paths of the interface folders, business applications must be modified to use the new paths.

Conversion to absolute paths

During an update or migration, most relative paths in the sedex Client’s configuration are automatically converted to absolute paths.

Never start an old sedex Client after the migration

Because the message and receipt states are carried over to the migrated sedex Client, it is very important that the old sedex Client is never started again after a migration has taken place. That would lead to an inconsistent state and messages or receipts could be lost.

sedex Client running as a service

If you are running the sedex Client as a service (Windows service or Linux daemon) using the service wrapper, the existing service must be uninstalled and reinstalled for the new installation. See the relevant steps in Prepare for migration.

Downgrading strongly discouraged

Reverting to an earlier version of the sedex Client is strongly discouraged. A downgrade can result in the loss of messages and receipts. If a problem arises during or with the migrated installation, contact the FSO’s sedex Customer Support.