ActiveTransfer Asset Dependencies

Some assets require other assets. For example, users use assets such as templates and partners, and virtual file systems use assets such as users. For migrated assets to work properly, these required assets must also exist on the target system.

The following table lists all possible dependencies an asset might have, as well as specific instructions for migration where appropriate. The name you use for an asset on the target system must match the name on the source system, with the same capitalization.

Asset

Dependency

ActiveTransfer Server ports

ActiveTransfer Server ports have a dependency on the server instance to which they are configured.

ActiveTransfer Server preferences

ActiveTransfer Server preferences have a dependency on the server instance to which they are configured.

User profiles

User profiles have a dependency on user templates, partners, and tunnels that are defined for a user.

Note:

If Trading Networks is installed, migrate partner profiles defined in Trading Networks separately.

Virtual file system folders

VFS folders have a dependency on users and partners who have been granted access to the folders.

Note:

If Trading Networks is installed, migrate partner profiles defined in Trading Networks separately.

Post-processing events and associated actions

Post-processing events have a dependency on users.

Scheduled events and associated actions

Scheduled events have a dependency on users.

If a dependent asset is not present in the file being imported, or is not present on the target server, ActiveTransfer Server will not import the asset. ActiveTransfer Server logs an error message and continues importing the remaining assets.

If the export file contains the required/dependent assets for any asset, the wm.mft.admin:importData service will ensure that the required assets get migrated first so that no error is thrown.