Copyright © 2020 fme AG. All Rights Reserved.

fme AG believes the information in this publication is accurate as of its publication date. The information is subject to change without notice.

THE INFORMATION IN THIS PUBLICATION IS PROVIDED "AS IS." FME AG MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Use, copying, and distribution of any fme AG software described in this publication requires an applicable software license.

All trademarks used herein are the property of their respective owners.

A content migration with migration-center always involves a source system, a target system, and of course the migration-center itself.

This section provides information about the requirements for using migration-center in a content migration project.

For best results and performance it is recommended that every component will be installed on a different system. Hence, the system requirements for each component are listed separately.

The required capacities depend on the number of documents to be processed. The values given below are minimal requirements for a system processing about 1.000.000 documents.

Database Server

Server Components (Job Server)

Client

migration-center 3.14 Update 1

Features & Enhancements

• Veeva Importer

  • New feature: Import documents using existing content from FTP server (#55303)

  • New feature: Add support for importing relations (#54991)

• SharePoint Online Importer (Batch)

  • New feature: Allow assignment of any valid SP user (#55219)

  • Support for OneDrive (#54262)

• Filesystem Scanner

  • New feature: Perform transformation of source object XML files before processing (#54776)

Fixes

• SharePoint Online Importer (Batch)

  • Update objects not marked as processed/imported (#55058)

• Veeva Importer

  • Import version tree with renditions fails (#55396)

• SharePoint Importer

  • Folder and document get created although a column cannot be set (#55001)

  • SPO importer fails setting lookup column with a NULL value (#55140)

  • CSOM Processor fails with 401 Unauthorized error if a job ran longer than 24 hours (#55323)

• Opentext Scanner

  • Keywords system rule is limited to 255 characters for Physical Objects migset (#55341)

Known Issues & Limitations

• General / logging

  • The installer does not update the location of the Job Server's log files. So if you do not want to use the default location for log files, which is <Job Server Home>/logs, you need to manually update the log file location in the <Job Server Home>/lib/mc-core/logback.xml configuration file (#54732)