This online documentation describes how to use the migration-center software in order to migrate content from a source system into a target system (or into the same system in case of an in-place migration).

Please see the Release Notes for a summary of new and changed features as well as known issues in the migration-center releases.

Also, please make sure that you have read System Requirements before you install and use migration-center in order to achieve the best performance and results for your migration projects.

The supported source and target systems and their versions can be found in our knowledge base article List of supported versions.

The migration-center is a modular system that uses so called adapters in order to connect to the various source and target systems. The adapters to connect to a source system are called scanners and the adapters to connect to a target system are called importers. The capabilities and the configuration parameters of each adapter are described in the corresponding manual.

You can find the explanations of the terms and concepts used in this manual in the Glossary.

And last but not least, Legal Notice contains some important legal information.

Further Resources

For additional tips and tricks, latest blog posts, FAQs, and helpful how-to articles, please visit our user forum.

In case you have technical questions or suggestions for improving migration-center, please send an email to our product support at support@migration-center.com.

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.

migration-center 3.17 Update 4

This release contains the following fixes and updates:

• Updated spring libraries for potential vulnerability CVE-2022-22965 (#61574)

• Fixed error when setting user attributes to "Guest" user using the SharePoint Online Batch Importer (#60948)

Remember to reinstall the CSOM service as well for the SharePoint Online Batch Importer as described here.

AIP - Archival Information Package

AIU - Archival Information Unit

BLOB - Binary large object

DB - Database

CSV - Comma separated values

CLOB - Character large object

DCTM - Documentum

DFC - Documentum Foundation Classes

DMS - Document Management System

DSS - Data Submission Session

GB - Gigabyte

GHz - Gigahertz

IA - InfoArchive

JDBC - Java database connectivity

JRE - Java Runtime Environment

JVM - Java Virtual Machine

KB - Kilobyte

MB - Megabyte

MS - Microsoft

MHz - Megahertz

RAM - Random Access Memory

regex - Regular expression

SIP - Submission Information Package

SPx - Service Pack x

SQL - Structured Query Language

XML - Extensible Markup Language

XSD - File that contains a XML Schema Definition

XSL - File that contains Extensible Stylesheet Language Transformation rules

Here is a list of all the versions supported by migration-center for all of our source and target systems:

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. Please see the for more details.

Database Server

Server Components (Job Server)

Client

Migration Set A migration set comprises a selection of objects (documents, folders) and set of rules for migrating these objects. A migration set represents the work unit of migration-center. Objects can be added or excluded based on various filtering criteria. Individual transformation rules, mapping lists and validations can be defined for a migration set. Transformation rules generate values for attributes, which are in turn validated by validation rules. Objects failing to pass either transformation or validation rules will be reported as errors, requiring the user to review and fix these errors before being allowed to import such objects.

Attribute A piece of metadata belonging to an object (e.g. name, author, creation date, etc.). Can also refer to the attribute’s value, depending on context.

Transformation Rules A set of rules used for editing, transforming and generating attribute values. A set of transformation rules is always unique to a migration set. A single transformation rules is comprised of one or several different steps, where each step calls exactly one transformation function. Transformation rules can be exported/imported to/from files or copied between migration sets containing the same type of objects.

Transformation Function Transformation functions compute attribute values for a transformation rule. Multiple transformation functions can be used in a single transformation rule.

Job Server The migration-center component listening to incoming job requests, and running jobs by executing the code behind the adapters referred by those jobs. Starting a scanner or importer which uses the Documentum adapter will send a request to the Jobserver set for that scanner, and tell that Jobserver to execute the specified job with its parameters and the corresponding adapter code.

Transformation The transformation process transforms a set of objects according to the set of rules to generate or extract.

Validation Validation checks the attribute values resulting from the Transformation step against the definitions of the object types these attributes are associated with. It checks to make sure the values meet basic properties such as data type, length, repeating or mandatory properties of the attributes they are associated with. Only if an object passes validation for every one of its attributes will it be allowed for import. Objects which do not pass validation are not permitted for import since they would fail anyway.

Mapping list A mapping list is a key-value pair used to match a value from the source data (the key) directly to the specified value.

This section provides information about the third party open source libraries used in the migration-center core and its adapters. Provided bellow are the library names, the license under which they are being used and links to the specific version being used.

MC Core

Source Connectors

Target Connectors

Introduction

The present document offers a guideline for sizing and configuring migration-center components in different migration scenarios. Due to the complexity of the migration projects, enterprise environments and applications migration-center interacts with, this guide does not provide exhaustive information, but it offers best practice configurations accumulated in more than 100 migration projects.

The Installation Guide and Database Administrator’s Guide contain a full description of the system requirements and installation steps for all migration-center components and should be consulted first. This document does not substitute the documents mentioned above but completes it with information that might be of importance for getting the best migration-center performance.

Targeted audience

This document is targeted specifically to the technical persons that are responsible with installation and configuration of migration-center components.

Common configurations and common sizing guidelines

This chapter describes the configurations and sizing guidelines that apply to any kind of migration project.

Client

The following hardware and software resources are required by MC client in any of the migration scenarios described in the next chapters.

Server components (Job Server)

Database

The migration-center database stores all information generated during a migration project. This includes job configurations, object metadata, transformation rules, status and history information, etc.

Small projects (up to 500,000 objects)

Sizing and configuration tips

• No special hardware or software requirements

• All MC components can be run on the same machine

Deployment overview

For such a small migration projects, where up to 500,000 objects need to be migrated, there are no special hardware or software requirements. Basically, all three MC components can be run on a single desktop computer or on an adequately sized virtual machine. In this case the machine should have enough physical memory for OS, Oracle server, MC components and other applications that may run on that machine. The recommended processor is a dual or quad core having a clock rate of minimum 2.2 GHz.

Oracle instance

• Standard database installation can be followed (as it is described in “migration-center installation guide”)

• RAM: 4 GB of total memory for the instance.

• Use “Automatic memory management”. This can be chosen when creating the Oracle instance.

Medium migration projects (500,000 – 5 million objects)

Sizing and configuration tips

• Dedicated Oracle Server machine

• Two MC Job Servers for a better scalability

Deployment overview

It is recommended to use a dedicated machine for the Oracle instance needed by MC.

For a better scalability of scanning and importing jobs or when migration timeframe is short, it’s recommended to deploy the Server Components (Job Server) on two machines. In this way you may run multiple scanner and importers in parallel speeding up the entire migration process. The performance of scanners and importers is dependent by the Source and Target System so if one of those systems performs slowly, the migration process can be speeded up by running multiple scanners and importers in parallel. If necessary, the number of deployed Jobservers can be extended.

Oracle instance

• The host should not necessarily be a server machine. A well sized desktop machine would be enough.

• CPU: Quad Core, min. 2.5 GHz

• 8 GB of memory allocated for the instance

• Use “Automatic memory management” in order for the instance to tune its target memory size, redistributing memory as needed between the system global area (SGA) and the instance program global area (instance PGA). If that is not possible, the recommendation is to allocate as much as possible for SGA memory (especially for buffer cache) and keep PGA memory in the range of 200 MB.

• It is very recommended the instance has at least 3 Redo Log files having in total a minimum size of 1 GB. This is important when multiple big transformation and validation jobs are run by MC because those jobs update a big number of database rows that require enough redo log space. You may get the information about existing redo log files by running the query: SELECT * FROM v$log;

Large migration projects (5 million – 15 million objects)

Sizing and configuration tips

• Dedicated Oracle Instance running on a Server machine.

• Three or more MC Job Servers for a better scalability

Deployment overview

It is recommended to use a dedicated Oracle Instance running on server hardware.

For a better scalability of scanning and importing jobs three or more instances of Server Components (Job Server) need to be deployed. The performance of scanners and importers is dependent by the Source and Target System so if one of those systems performs slowly, the migration process can be speeded up by running multiple scanners and importers in parallel. If necessary, the number of deployed Job Servers can be extended.

Oracle instance

• A dedicated server machine is required. It is recommended to use a dedicated Oracle instance for running only Migration Center but no other applications.

• CPU: 4-8 Cores, min. 2.5 GHz

• 16-32 GB of memory allocated for the instance

• Use “Automatic memory management” in order for the instance to tune its target memory size, redistributing memory as needed between the system global area (SGA) and the instance program global area (instance PGA). If that is not possible the recommendation is to allocate as much as possible for SGA memory (especially for buffer cache) and keep PGA memory in the range of 400 MB.

• Make sure that instance has at least 4 Redo Log files having in total a minimum size of 1.5 GB. This is important when multiple big transformation and validation jobs are run by MC because those jobs update a big number of database rows that require enough redo log space. You may get the information about existing redo log files by running the query: SELECT * FROM v$log;

Very large migration projects (more than 15 million objects)

Sizing and configuration tips

• Multiple Dedicated Oracle Instances running on a Server machine or use an instance on a high-performance Oracle cluster

• Four or more Job Servers.

• A file server or a storage server used for temporary storing the content.

Deployment overview

The deployment for the migration of a very large number of objects should be planned carefully. In this case it is recommended to use multiple MC databases. In most cases it is not advised to migrate more than 10 million objects with a single Oracle instance even if the hardware is sized accordingly. There are several reasons for using multiple database instances:

• The data from different sources is not mixed up in a single instance helping the user to handle easier the errors that appear during migration

• The transformations and validations will be better scaled on multiple database instances

• Facilitate the work of multiple migration teams

A dedicated file/storage server should be shared by all Job Servers for storing and accessing the content during migration. This will help the migration in the way that set of objects scanned with any scanner can be imported with any importer.

Oracle instance

• Several dedicated server machines are required. For each machine it is recommended to use a dedicated Oracle instance for running only Migration Center but no other applications.

• CPU: 4-8 Cores, min. 3.0 GHz

• Minimum 16 GB of memory allocated for each instance.

• Use “Automatic memory management” in order for the instance to tune its target memory size, redistributing memory as needed between the system global area (SGA) and the instance program global area (instance PGA). If that is not possible the recommendation is to allocate as much as possible for SGA memory (especially for buffer cache) and keep PGA memory in the range of 600 MB.

• Is recommended that FMEMC_DATA tablespace to be split on multiple physical data files stored on different physical disks in order to maximize the performance for a specific hardware configuration.

• Make sure that instance has at least 5 Redo Log files having in total a minimum size of 2 GB. This is important when multiple big batch jobs (transformations, validations, scanners, importers) jobs are run by MC because those jobs update a big number of database rows in quite a short time and therefore redo log space should be sized accordingly in order to prevent redo log wait events. You may get the information about existing redo log files by running the query: SELECT * FROM v$log;

Introduction

The present document offers a detailed description of migration-center requirements specifically related to the Oracle database management system it uses as the backend.

The Installation Guide contains a full description of the system requirements and installation steps for all migration-center components and should be consulted first. This document does not substitute the Installation Guide, but completes it with information that might be of importance for Oracle database administrators, such as the various packages, privileges and other Oracle specific features required and/or used by migration-center.

Targeted audience

This document is targeted specifically at Oracle database administrators about to deploy migration-center in corporate environments where databases need to adhere to strict internal guidelines and policies, and where the default database installation procedure used by migration-center may need to be reviewed first, or possibly adapted to meet specific requirements before deploying the solution.

The migration-center Database

The migration-center database stores all information generated during a migration project. This includes job configurations, object metadata, transformation rules, status and history information, etc.

Requirements

Hardware Requirements

• 2-4GB of RAM should be assigned to the Oracle database instance (not the entire Oracle server) where the migration-center schema will be deployed. The Oracle specific memory allocation settings can be left at their defaults.

• For storage requirements and sizing of Oracle datafiles see section Oracle Tablespaces below.

• There is no differentiation between physical or virtual hardware in terms of requirements; faster physical hosts may be required to compensate for losses in I/O performance or latency if running the database server on virtual machines.

Software Requirements

• Oracle RDBMS version: 11g R2 - 19c Architecture: both 32bit or 64bit are supported Edition: Standard Edition One, Standard Edition, Enterprise Edition Oracle Express Edition (Oracle XE) is also supported but not recommended in production because of its limitations!

• Ideally a separate Oracle database instance should be designated for use by migration-center alone, rather than an instance shared with other database applications. This would help performance and related troubleshooting if necessary as there wouldn’t be multiple applications and thus multiple potential problem sources to investigate. From a purely technical perspective sharing a database instance with other database applications poses no problems.

• The operating system the Oracle Server is running on is of no relevance to migration-center, as all communication with the database happens at a higher level, independently of the underlying OS or hardware architecture. All operating systems officially supported by the Oracle versions mentioned above are also supported by migration-center.

• Please consult the appropriate Oracle documents for more information on operating systems supported by Oracle databases.

Oracle Schema

The migration-center database schema can be deployed on any Oracle database instance meeting the requirements and setting described in the migration-center Installation Guide

• The schema is named FMEMC. The schema name is fixed cannot be changed; as a consequence it is also not possible to have more than one schema installed on the same database instance.

• The schema is home to all database objects created and used by migration-center, such as tables, stored procedures, Java code, etc. As part of the schema the user FMEMC is created and granted access to all necessary packages, objects and privileges (also see section Oracle Privileges). For storing data and indices two tablespaces are also created for use by FMEMC (also see section Oracle Tablespaces).

Oracle Tablespaces

• The tablespace meant for storing user data is called FMEMC_DATA and will store information such as job configurations, object metadata, transformation rules, status and history information, etc.

• A separate tablespace called FMEMC_INDEX is used for storing indices of indexed fields

Much like the schema name, the tablespace names are fixed and cannot be changed.

Oracle Datafiles

• By default each of the two tablespaces mentioned above store information in 2 data files

• The data files are set to autoextend by default

• The data files can be customized in terms of count, size, storage location, and whether autoextend is allowed or not. With the autoextend option disabled the free space within the data files needs to be monitored and extended accordingly during the migration process to prevent the tables from filling up and stalling the migration process.

The above must be changed in the installation scripts and cannot be set through the regular setup program’s GUI.

• The primary factor for sizing the Oracle data files is the number of objects planned to be migrated using the respective database instance, as well as the number of attributes stored per object, and the length of the respective attribute values; these factors can (and do) of course vary from case to case.

For more comprehensive information on typical migration project sizes (from small to very large) and the requirements in terms of storage space resulting from there, as well as general recommendations for sizing the database in preparation of an upcoming migration project please consult the Sizing Guide.

Oracle Privileges

This chapter details the privileges required by migration-center for accessing the Oracle packages and various functionalities it needs to work properly. By default these privileges are granted to the FMEMC user during installation. After database installation has completed successfully, it is possible to log in with the user FMEMC and connect to the migration-center database in order to start using the solution.

Privileges Required For Installation

The regular installation process using the setup program with GUI requires logging on as SYS. Since this might not be possible in some environments, there is the alternative of customizing the critical part of the setup and having an administrator execute the appropriate scripts.

This would generally involve having an administrator customize and runs the scripts for creating the user FMEMC, tablespaces, data files, etc., and then run the rest of the setup by running the setup program using the previously created user FMEMC for connecting to the database instead of SYS. In this case the below permissions must be granted to user FMEMC in order for the setup program to determine whether migration-center tablespaces and/or data files already exist on the instance where the database is supposed to be installed.

GRANT SELECT ON SYS.DBA_DATA_FILES TO FMEMC;

GRANT SELECT ON SYS.DBA_TABLESPACES TO FMEMC;

Privileges for Various Functionalities

• Encrypting passwords saved by migration-center

• Read current database configuration from view v$instance (host name and database instance name)

• Execute core migration-center job-based functionalities such as transformation, validation, or scheduled migration as native Oracle Jobs

• migration-center Transformation Engine (process migration-center data by applying transformation rules and altering object metadata)

GRANT CONNECT, RESOURCE TO FMEMC;

GRANT CREATE JOB TO FMEMC;

GRANT SELECT ON SYS.V_$INSTANCE TO FMEMC;

GRANT CREATE VIEW TO FMEMC;

GRANT SYS.DBMS_LOCK TO FMEMC;

GRANT SYS.UTL_RAW TO FMEMC;

GRANT SYS.UTL_ENCODE TO FMEMC;

GRANT SYS.DBMS_OBFUSCATION_TOOLKIT;

Privileges for migration-center Scheduler

• Start scheduled migration jobs at the specified time using Oracle’s built-in scheduler GRANT SYS.DBMS_SCHEDULER TO FMEMC;

• Establish network communication from scheduler to Job Server over TCP GRANT SYS.UTL_TCP TO FMEMC;

• Allow the scheduler to send notification emails to configured users about outcome of scheduled migration jobs GRANT SYS.UTL_SMTP TO FMEMC;

Preparing the Database for Setup Using Scripts

As mentioned above, parts of the installation process can be controlled via installation scripts. These can be used for preparing the database manually by an administrator and finally running the regular setup program connected with the migration-center user FMEMC instead of SYS which may not be allowed to be used.

Database scripts

The script files used during setup are located in the Database\util folder of the migration-center installation package. These files can be used to adapt the setup procedure to some degree to specific requirements of the customer’s environment. The individual files and their role in the migration-center database installation process are described in the table below.

Instructions for preparing the database manually and performing the installation

• Decide whether to use a custom or the default location for the data files. Pick create_tablespaces_custom_location.sql or create_tablespaces_default_location.sql accordingly.

• Review/adapt the selected tablespace creation script

• Execute the tablespace creation script

• Review/adapt the user creation script (do not change user name!)

• Execute the user creation script

• Run the migration-center database installation program (Database\InstallDataBase.exe) and proceed as described in the installation guide. Exception to the Installation Guide: log in as the previously created user FMEMC instead of user SYS!

• Verify the database installation log after installation

• Log on to migration-center using the migration-center Client and verify basic functionalities

• Use the drop_fmemc_schema script to drop the entire schema in case of an unsuccessful installation, or if the schema needs to be removed for other reasons. WARNING! This will delete all migration center data from the database instance! Make sure the schema has been backed up before dropping a schema that already contains user data created by migration-center.

migration-center 3.17 Update 3

This release is a collection of cumulative fixes that have been done since version 3.17 Update 2.

Fixes

• Veeva Importer:

  • Importing submission to Veeva RIM with skipUploadContent throws error but import is successful (#60418)

  • Importing submission with skipUploadContent checked does not work (#60306)

  • Uploading/Downloading content to/from FTP Staging Folder does not work with REST calls (#60493)

  • Setting object_type__v attribute throws NullPointerException (#60659)

  • Updating objects throws an error (#60571)

  • The version tree is not correctly scanned when the minor version is greater than 9 (#60957)

  • Submission response is not parsed correctly (#60780)

• Veeva Scanner:

  • Veeva scanner continue working on background after stop (#60805)

• SharePoint Online Scanner:

  • Scanning objects throws an error when parsing the creation date (#60751)

  • An SQL Exception is thrown when the attribute value is greater than the limit (#60208)

  • The build sometimes is compiled for 32 bit platform (#60211)

  • The total number of objects displayed in summary is not correct (#60205)

• D2 Importer:

  • NullPointerException when importing VD relation updates (#60470)

• Dctm Importer (NCC)

  • Updating content on Documnetum NCC with ECS does not work properly (#60795)

migration-center 3.17 Update 2

Features & Enhancements

• Generis Cara Importer:

  • Add support for importing relations (#59664)

  • Add support for setting rendition identifier(#60027)

Known Issues & Limitations

• Generis Cara Importer:

  • When binding relations by version label, no error is thrown when incorrect or missing version label mapping is provided(#60093)

  • Importing a base document and one update (as result of delta scan) results in unpredictable behavior(#60118)

migration-center 3.17 Update 1

Features & Enhancements

• Veeva Importer:

  • Multi-threading for upload content process (#59158)

  • Upload content using File Staging REST API (#59680)

  • Added object type order when importing Veeva Objects (#59085)

  • Updated to use API 21.2 (#59343)

• Veeva Scanner:

  • Multi-threading for download content process (#59158)

  • Retrieving inactive dictionary value from Veeva (#59516)

  • Scan new audit trails in Delta scan (#59641)

  • Download the content from FTP by using REST API (#59160)

  • Updated to use API 21.2 (#59684)

Fixes

• General:

  • Removed SQLJUTL package dependency which caused errors on certain Oracle DBs (#59700)

• SharePoint Online Importer:

  • Removed the need for having minor versions enabled when importing folder updates (#59570)

Known Issues & Limitations

• InfoArchvie Importer:

  • Using Java 8 when generating large PDI files may result in incorrect values in the PDI file (#59214)

• Veeva Importer:

  • objectsOrder feature is ignored if it does not contain all object_name values from the migset (#59981)

  • Setting object_name values that don't exist in Veeva in objectOrder does not throw error (#59980)

migration-center 3.17

Features & Enhancements

• General:

  • Transformation function getDataFromSql can return multiple values (#535420)

• Hyland OnBase Importer

  • Import documents

  • Set custom metadata

  • Import document revisions

  • Delta migration (only for metadata)

• Amazon Comprehend Enrich Scanner

  • Enrich documents metadata based on the content

  • Language detection

  • Extract entities (standard and custom)

  • Support custom classifiers

• Filesystem Scanner:

  • Make versioning case insensitive (#58656)

• Documentum Scanner:

  • Allow more flexible queries for selecting documents to be scanned (#58345)

  • Create counter for already scanned objects in the execution summary (#58907)

  • Export documents with content_location pointing to the path in the storage (#54317)

• Cara Importer:

  • Import audit trails from Documentum as audit trails objects (#58797)

  • Index the imported documents (#59513)

Fixes

• General:

  • Scheduler next run date not calculated correctly (#58845)

• Cara Importer:

  • Fix reporting errors for missing/incorrect system attributes (#58488)

  • Fix nonintuitive error message when required content or rendition attributes are not set (#58608)

• CSV-Excel Scanner:

  • Fix scanning CSV with UTF8 - BOM with first column used as ID (#54010)

• Veeva Importer:

  • Fix max length for system rules (#59046)

  • Attributes mapping does not work properly when the object_type__v is not the same as the object that is imported (#57383)

• Veeva Scanner:

  • Binder relations are scanned even if the child documents are not (#56230)

• SharePoint Online Importer:

  • Temp file is deleted early if HTML error is thrown (#58869)

• OpenText Content Server Importer:

  • Importing compound documents doesn't fail when folder with same name already exists (#52038)

• D2 Importer:

  • Repeating default values are not set correctly (#58692)

Known Issues & Limitations

• Cara Importer:

  • Asynchronous Indexing not setting index on documents (#59574)

• SharePoint Online Scanner:

  • CAML query not working on SPO Scanner (#59597)

migration-center 3.16

Features & Enhancements

• General

  • Add support for Java 11 for all adapters (#53313)

  • Add new transformation function: GetInternalAttributeValue (#57376)

  • Add new transformation function: CalculateNewNumber (#58237)

• Cara Importer (NEW)

  • Add support for checksum verification (#57744)

  • Add support for importing VDs (#57756)

  • Add support for proxy communication (#58057)

  • Add support for uploading content using REST (#58169)

• D2 InPlace Adapter (NEW)

  • D2 Auto-Naming functionality (#57662)

  • D2 Auto-Linking functionality (#57663)

  • D2 Auto-Security functionality (#57664)

  • Validate attributes values based on D2 dictionaries (#57666)

  • Apply D2 rules based on a document’s owner (#57667)

• CSV/Excel Scanner

  • Add support for delta migration on CSV/Excel scanner (#56911)

• D2 Importer

  • Add support for D2 20.4 (#55909)

• Database Scanner

  • Improve performance when scanning data from a single query (#56714)

• Documentum Importer/Scanner

  • Add support for DCTM server 20.4 (#55904)

• Filesystem Scanner

  • Add support for scanning paths provided in a text file (#57073)

  • Specify folders to exclude as relative paths (#57074)

  • Enhance explicit versioning to new versions to existing ones during delta scan(#58563)

• InfoArchive Importer

  • Add support for InfoArchive 20.4 (#55912)

  • Add support for generating huge PDI files (#56912)

• Opentext Content Server Scanner/Importer

  • Add support for OpenText Content Server 20.4 (#55901)

• SharePoint Online Batch Importer

  • Set retention policy labels (#56114)

  • Set sensitivity labels (#57086)

  • Add support for QuickXorHash (needed for files > 15 GB) (#57226)

Fixes

• CSV/Excel Scanner

  • Cells that have nothing but are scanned as null (#57228)

• Documentum Importer

  • Repeating attributes are not rewritten on new versions (#58231)

• Opentext Content Server Importer

  • The job status is not properly set when occurring OutOfMemory error (#57022)

• SharePoint Online Batch Importer

  • MIP Service fails to load DLL (#58038)

• Veeva Scanner

  • The temporary location is not cleared up after the scan run (#57853)

• Veeva Importer

  • Validation errors are not cleared after each validated document (#57206)

  • Submissions cannot be imported when having more than 200 applications (#58062)

Known Issues & Limitations

• Veeva Scanner

  • The binder relations are scanned even if the children documents are not (#56230)

• SharePoint Online Batch Importer

  • When trying to import a broken version tree, the import fails for all documents (even the ones that had a correct version tree) with an error status (#57099)

• Database Scanner

  • The summary is not completely accurate when using a single query (#58228)

• InfoArchive Importer

  • The first version of child doc remains validated when includeChildrenVersions is set to false and includeChildrenOnce is set to true (#57766)

• Veeva Importer

  • Attributes mapping does not work properly when the object_type__v is not the same as the object that is imported (#57383)

• Opentext Content Server Importer

  • NPE when importing documents with no content (#58288)

migration-center 3.15 Update 2

Features & Enhancements

• General

  • Migrate OT shortcuts and URLs to SPO link documents (#55974)

  • New TrackWise Digital importer available (#53977)

  • Improve the performance of the mapping list transformations (#56913)

• SharePoint Online Batch Importer

  • Improve robustness of verification step (#55898)

  • Allow import into multiple sites (#56043)

  • Save imported object URL in object_info1 column (#56113)

• SharePoint Online Scanner

  • App-Only authentication in SPO scanner (#54259)

• Veeva Scanner

  • Automatic resume after daily API limit was exceeded (#56898)

Fixes

• File System Scanner

  • content_location and mc_content_location not updated when using moveFilesToFolder (#56471)

  • Metadata files are not moved when moveFileToFolder is checked (#56488)

• SharePoint Online Classic Importer

  • 'null' added to path when importing to root folder (#56603)

  • Move folder not working in SPO importer (#56703)

• Veeva Importer

  • Document with auto-generated name __v cannot be imported (#56684)

  • Error when importing doc with empty string in attachments and skipUploadToFTP (#56826)

• Veeva Scanner

  • The rendition for already scanned objects is exported to disk in some cases (#56283)

  • Proxy configuration ignored for HTTP requests (#56566)

  • Running scanners in parallel fails with error (#56763)

Known Issues & Limitations

• Veeva Scanner

  • The binder relations are scanned even if the children documents are not (#56230)

• InfoArchive Importer

  • OutOfMemory exception might be thrown by InforArchive importer when generating very large SIP file (#55698)

• SharePoint Online Batch Importer

  • When trying to import a broken version tree, the import fails for all documents (even the ones that had a correct version tree) with an error status (#57099)

• SharePoint On-Prem Importer

  • Moving folders fails with 'File not found' error (#57111)

migration-center 3.15 Update 1

Features & Enhancements

• General

  • Add Veeva Scanner that exports documents and binders from Veeva Vault (#54569)

  • Migrate OpenText shortcuts and URLs to SPO link documents (#55974)

• Documentum Scanner

  • Export all folder paths of all folders where a document is linked (#55486)

• OpenText Scanner

  • Add the URL/path of the original object to the scanned shortcut (#56206)

  • Allow users to configure a list of workspaces/root nodes to be scanned (#55899)

  • Scan URLs as OpenText(object) type so they can be imported to other systems (ex: SharePoint Online) (#56001)

• SharePoint Online Importer

  • Add support for setting sensitivity label for importing documents (#55645)

• Veeva Importer

  • Enable Migration Mode programmatically for the imported objects so Migration Mode is not necessary to be enabled on the vault level (#55493)

Fixes

• Veeva Importer

  • Duplicate values are not supported for object_type__v attribute in RIM Vault (#55664)

Known Issues & Limitations

• Veeva Scanner

  • The renditions for already scanned objects is exported to disk in some cases (#56283)

  • The binder relations are scanned even if the children documents are not (#56230)

• InfoArchive Importer

  • OutOfMemory exception might be thrown by InforArchive importer when generating very large SIP file (#55698)

migration-center 3.15

Features & Enhancements

• CSV - Excel Scanner:

  • Added support for scanning repeating attributes (#54993)

• InfoArchive Importer:

  • Added support for multiple references to the same content (#55529)

• OTCS Scanner:

  • Added support for scanning CAD documents as regular documents (#55900)

• SharePoint Online Batch Importer:

  • Added support for setting approval status on documents (#54990)

  • Added support for setting version numbering (#55505)

  • Added support for setting Lookup field type (#55521)

• Veeva Importer:

  • Added support for delta migration of Veeva objects (#54928)

  • Added support for importing attachments for Veeva Objects (#55535)

• Core Database:

  • Added additional multi-value transformation functions (#55424)

Fixes

• OTCS Importer:

  • Fixed record date not being set in opentext_rm_classification (#55431)

• SharePoint Online Batch Importer:

  • Fixed import failing with invalid XML characters in attributes (#55007)

  • Fixed import failing verification (#55574)

  • Fixed import failing into library with deep path (#55745)

• SharePoint Online Importer:

  • Fixed import failing into site collection URL with spaces (#55571)

  • Fixed not being able to assign AD group (#55796)

  • Fixed error on folder update (#55870)

Known Issues & Limitations

• Alfresco Scanner:

  • Scan doc with versions edited online while autoVersion false, but had autoVersion switched to true afterwards has wrong version content (#55983)

• CSV - Excel Scanner:

  • Content_location is not scanned as multi-value (#55635)

• Veeva Importer:

  • Objects are not rolled back if attachment was set on objects that do not support attachments (#55939)

• Documentum NCC Importer:

  • Delta migration for the multi-page content does not work properly when a new page is added to the primary content (#55739)

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)

migration-center 3.14

Features & Enhancements

• Alfresco Scanner

  • New feature: Scan only last "n" versions (#54289)

  • New feature: Scan multiple sites (#54291)

• D2 Importer

  • Support for D2 20.2

• Documentum Scanner / Importer

  • Support for Documentum Server 20.2

• OpenText Importer

  • Support for OpenText Content Server 20.2

• OpenText Scanner

  • New feature: Scan shortcuts as distinct MC objects (#53710)

  • New feature: Scan any folder subtype objects (#53711)

• SharePoint Online Importer (Classic)

  • New feature: Add user-agent traffic decoration (#52837)

• SharePoint Online Importer (Batch)

  • New feature: Importing role assignments (#54440)

• Tools

  • New tool to export document type definitions from Veeva available (#51539)

Fixes

• OpenText Scanner

  • NPE occurs using excludeFolderPaths (#54326)

  • Wildcards do not work in the root folder (#54329)

  • Set attributes are not scanned if the name is longer than 100 chars (#54589)

• SharePoint Online Importer (Batch)

  • SPO batch importer checks wrong content location (#54568)

  • SPO batch importer throws error when importing large folder hierarchy (#54574)

  • NPE for objects with NULL value in levelInVersionTree in SPO batch importer (#54637)

• SharePoint Importer

  • Wrong max length limit for parentFolder system attribute when importing to SP 2019 (#54592)

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)

• D2 Importer

  • Support for importing to D2 4.1, 4.5, and 4.6 was removed

• OpenText Scanner

  • Using binders in the parameters "scanFolderPaths" and "excludeFolderPaths" is not supported (#54963)

migration-center 3.13 Update 2

Features & Enhancements

• PowerShell tools:

  • Support multiple scan run IDs when creating migration sets (#54263)

• SharePoint Online importer:

  • Support for app-only principal authentication with SharePoint permissions (#54277)

• SharePoint Online Bulk importer:

  • Add mc_content_location in migset rules (#54182)

  • Support for app-only principal authentication with SharePoint permissions (#54277)

• SharePoint Online scanner:

  • Add scanLatestVersionOnly feature (#5615)

  • Add includeFolders and excludeFolders parameters (#53706)

Fixes

• OpenText importer: Wrong values for date attribute during physical objects import (#54255)

• OpenText scanner:

  • NPE occurs using excludeFolderPaths (#54326)

  • Wildcards do not work in the root folder (#54329)

• SharePoint (Online) importer: Automatically added content type not added to cache (#54420)

• SharePoint scanner: Permissions & User fields contain ambiguous username instead of login name (#54240)

migration-center 3.13

Features & Enhancements

• New SharePoint Online Batch Importer (#52665)

• Add “removeDuplicate” transformation function (#53528)

• Add support for Oracle 19c (#52930)

• Add support for Oracle JDK 11 & OpenJDK 11 (#53313)

• Add support for Oracle JDK 13 & OpenJDK 13 (#52492)

• Add support IA 16.7 (#52910)

• Added support for Alfresco 6.2.0 for Alfresco scanner and importer (#54108)

• Alfresco scanner and importer now require java 1.8 or later

• Documentum Scanner

  • Scan complete document audit trail and save it as rendition to the current document version (#52846)

• OpenText Importer

  • Assign objects to Physical Object Box with a dedicate system rule (#52748)

• SharePoint importer

  • Support valid filename characters on SharePoint on-prem (#53304)

• Documentum In-Place

  • Implement move content feature in Documentum In-Place adapter (#53518)

Fixes

• Fix typo in transformation function “ConverDateTimezones” (#53136)

• “GetDateFromString” transformation function returns null in some cases (#53164)

• Job server installation on Linux outdated in Installation Guide (#53714)

• OpenText Importer became laggy during impersonation after a certain number of requests (#53180)

• No error or warning when importing two renditions of the same type with OpenText Importer (#53124)

• The underlying connection was closed: An unexpected error occurred on a send in SharePoint Importer (#53099)

• Could not get SharePoint X-RequestDigest error message when space character in site collection name (#53190)

• SharePoint Importer should log error immediately if required fields are missing (#53844)

• HTTP 503 Server Unavailable Error when downloading large content files with SharePoint Online Scanner (#53673)

• Fix “Member ID is not valid” in OpenText scanner (#53482)

• Fix setting empty Vault Object reference in Veeva importer (#53573)

migration-center 3.12

Features and enhancements

• OTCS Scanner

  • Scanning Project objects as OTCS(container) with metadata (#52932)

  • Save version information as source attributes (#52292)

  • Support wildcards in folder paths (#52360)

  • Show number of warnings in job run report summary (#52845)

  • Scan user field with username instead of user id (#52847)

  • Objects scanned from inside projects now contain full parentFolder path (#52960)

  • Revised OpenText Adapter User Manuals (#52550)

• Veeva Importer

  • Re-authentication mechanism in case of session timeout (#52822)

  • Pause and retry mechanism to handle burst and daily API limits (#52823)

  • Support version binding when importing Veeva Vault binders (#52091)

  • Delta Migration of objects in Veeva Importer (#53037)

• Added support for Alfresco 6.1.1 in Alfresco Importer (#53008)

• Added support for annotations in D2 Importer (#53018)

• Documentum scanner now supports dqlExtendedString returning repeating values (#52587)

• Added Support for SP 2019 in SP Importer (#52870)

• Auto-Classification Module

  • Functionality to split dataset into training and test data (#52660)

  • Removing of library under GPL license (#52853)

  • Classification Process Logging (#52855)

Fixes

• Unresolved document file path in ScanRunExtractor (#52876)

• Filesystem importer writes invalid XML characters to metadata XML file (#52909)

• Missing dependency packages in AC module installer (#52935)

• Error validating classification when subtypes not unique (#52945)

Known Issues

• In Veeva Importer setting Binder version labels as major/minor does not work (#53160)

• In Veeva Importer document updates with empty values for attributes that were not empty does not delete existing value (#53229)

• In OTCS Scanner user fields that were deleted from a category are scanned as IDs (#52982)

migration-center 3.11

Features and enhancements

• New SharePoint Online Scanner (#52409)

• Made OTCS scanner more robust to errors (#52361)

• Imptoved OTCS scanner job run log output (#52365)

• FileSystem Importer now applies XSL transformation on whole unified metadata XML file (#52394)

• Veeva Importer now supports importing Documentum documents as renditions of a specific type to a Veeva Vault document (#52090)

Fixes

• Fixed bug in Filesystem Importer where attributes with no value were not being exported in XML metadata file (#52479)

• Fixed OTCS Scanner not scanning documents under folder inside nested projects (#52809)

• Fixed SPOnline importer bug when importing folders with a “%” in the name (#52857)

• Fixed SPOnline importer not refreshing token when all objects of a large import fail (#52775)

Known Issues

• SharePoint Online Scanner might receive timeout error from SharePoint Online when scanning libraries with more than 5000 documents (#52865)

migration-center 3.10

Features and enhancements

• Added support for Oracle database version 18c (#51451)

• Added support for migrating Veeva Vault Objects (#52136)

• Added support for version 16.x for the OpenText scanner (#50340)

• Added support for D2 versions 16.4 and 16.5 (#50972, #51530)

• Added switch for lifecycle error handling in D2 Importer (#50991)

• Updated the IBM Domino Scanner (#49173)

• Improved database security by changing default password (#51112)

• Improved performance of filesystem importer copy operation (#52320)

• Enhanced the RepeatingToSingleValue function to not throw exception when length exceeds 4000 bytes (#51798)

• Added missing file and folder name checks in the SP and SPO importer user guides (#52076)

• Updated linux Jobserver with new YAJSW wrapper (#52347)

• Box.net Importer, added the following features:

  • Import custom metadata (#50312)

  • Import tags (#50314)

  • Import comments (#50315)

  • Import tasks (#50316)

  • Add collaborators to the imported documents (#50602)

Fixes

• Fixed bug in DCTM adapters when calculating multi page content (#50442)

• Fixed bug in SharePoint scanner when scanning SP 2013+ on Windows Server (#51088)

• Fixed error messages bigger than 2000 characters not being saved in the database (#52357)

• SharePoint Importer, fixed the following bugs:

  • import taking a long time when content_location points to folder (#52115)

  • Importer not starting if adfsBaseURL contains trailing slash (#51941)

  • DEBUG messages getting logged despite log level ERROR in log4j (#52082)

  • Added debug log messages for queue building missing in SP importer (#52084)

  • Exception not caught when reverting import action (#52216)

  • Importer hanging when encountering an exception in RefreshDigest method (#52238)

  • Improved Retry handling (#52270)

  • Error when importing into site with %20 in the name (#52272)

  • autoCreateFolders always enabled (#52305)

  • NullPointerException in file upload when SPOnline throttling occurs (#52325)

migration-center 3.9 – update 3

Features and enhancements

• Some new features and enhancements in Domino Scanner

  • New scanner parameter "excludedAttributeTypes"

  • Default for scanner parameter "exportCompositeItems" now "0"

  • Scanner parameter "selectionFormula" set to be editable by default

  • 64bit support (based on IBM Domino); 32bit support remains unchanged (based on IBM Notes)

• InfoArchive Importer: provide a better way for importing email attachments scanned from IBM Domino

Fixes

• Domino Scanner: Extracted floating point numbers truncated/rounded to integer value

• Domino Scanner: Attributes of type "NumberRange" were not exported

• OpenText CS scanner: some logging improvements

• OpenText CS scanner: Fix scanning subprojects

• Veeva Vault Importer: Fix setting status_v for the root version

• Veeva Vault Importer: Fix importing VD relations that have order_no with decimals.

• Veeva Vault Importer: Fix a null pointer exception when logging some results

• CSV/Excel Scanner: Fix setting the internal processing type of the scanner

• Sharepoint Importer: Fix importing documents having # and % in the name

• Sharepoint Importer: Fix importing folder with two consecutive dots (..) in the name

• Sharepoint Importer: Fix token expiration after 24 hours.

Migration-center 3.9 update 2

Features and enhancements

• Add support for importing attachments to Veeva Vault.

Migration-center 3.9 update 1

Features and enhancements

• Added support for scanning nested compound documents in OTCS Scanner

• Added support for scanning the Nickname attribute for folders and documents in OTCS Scanner

• Added Proxy support for ADFS Authentication in SharePoint Importer

• Added support for filtering Scanners and Importers in MC Client

Fixes

• Fixed OTCS Scanner bug not scanning dates properly sometimes

• Fixed OTCS Scanner "Member Type not valid" error message

• Fixed OTCS Scanner nullPointerException when trying to get the owner name in specific cases

• Fixed OTCS Scanner nullPointerException when trying to scan certain Workspaces

• Fixed SharePoint Importer bug autoCreateFolders not working for values with leading slash

• Fixed SharePoint failing authentication with invalid XML chars in use name or password

migration-center 3.9

Features and enhancements

• Replaced Tanuki service wrapper with YAJSW (#51159)

• Added support for Java 64-bit (#51163)

• Added support for OpenJDK 8 (#51156)

• New CSV / Excel Scanner (#50343)

• Added Content Hash Calculation feature to OTCS scanner (#50736)

• Added support for java web service in OTCS Scanner (#51389)

• Added support for importing RIM submissions to Veeva Vault (#51208)

• Added support for importing Documentum Virtual Documents as Binders in Veeva Vault (#51188)

• Added support for setting references to existing master data objects in Veeva Vault (#51151)

• Added support for ADFS authentication in SPO Importer (#51414)

• Added new Transformation function for time-zone conversions (#51480)

Fixes

• Fixed bug when pulling content for updates with the Database scanner (#51142)

• Fixed error message in OTCS log (#51619)

• Fixed SharePoint Online importer too short path length limitation (#51491)

• Fixed SharePoint not resuming properly after pausing job for long time (#51492)

• Changed behavior of setting the file extension for the SharePoint Importer (#51503)

migration-center 3.8

Features and enhancements

• Documentum Scanner: Added option to scan only the latest version of a VD (#51019)

• OTCS Importer: Added support for importing Virtual Documents as Compound Documents (#51008)

• New transformation functions: GetDataFromSQL() and Length() (#50997, #50999)

• Database Scanner: New Delta migration feature (#50477)

• Documentum Importer: Extended waiting time for operations queue to finish (#50995)

Fixes

• Fixed error in D2 Importer when property pages contained tabs with visibility conditions (#50987)

• Removed unneeded jar file from D2 importer folder (#51073)

migration-center 3.7

Features and enhancements

• The Jobserver now requires Java 8. Java 7 is not anymore supported.

• New Veeva Vault importer

• Extended OpenText importer to import physical items (#50282)

• Changed the way of setting RM Classifications in OpenText importer (#50842).

Fixes

• Delta migration issue after upgrading from 3.2.5 or older (#50571)

Known issues

• Importing not allowed items in the physical item container is permitted (#50978)

• RM classifications for physical objects are not removed during delta (#50979)

• Physical objects properties of type date are not updated during delta migration (#50980)

• Veeva importer may fail to start, if DFC is installed on the same machine (#50981)

• No error reported when setting values to Inactive Fields in Veeva Importer (#50880)

• No error reported when setting values to fields that are not in the Type / Subtype / Classification used in Veeva Importer (#50871)

• No error reported when setting permissions not in the selected lifecycle in Veeva Importer (#50939)

migration-center 3.6

Features and enhancements

• New OpenText In-Place Adapter (#49994)

• Updated Tika library to version 1.17 for Filesystem scanner (#49258)

• OTCS scanner is now able to scan Business Workspaces (#49994)

• SharePoint Importer is now able to change the extension of files (#50142)

• D2 Importer validates the Enabled, Visible and Mandatory conditions in a Property Page (#50235)

• D2 Importer marks documents as Partially Imported when failing to apply a lifecycle action (#50274)

Fixes

• Fixed issue with saving migsets when plsql_optimize_level was set to 3 (#49160)

• Fixed issue with exporting BLOB content from a Firebird database (#49197)

• Fixed error in Documentum In-Place adapter with linking into inexistent folderpath (#49217)

• Fixed nullPointerException in SharePoint Importer when using proxy (#49232)

• Fixed bug in Documentum audit trail rollback scripts (#49943)

• Fixed nullPointerException in Alfresco Importer (#50027)

• Fixed error when scanning documents in “Projects” with OTCS Scanner (#50130)

• Fixed individual version creator not being scanned in OTCS scanner (#50273)

• Fixed missing supported versions for Oracle and DFC in the Installation Guide (#50275)

• Fixed DQL Validation for $repeatingvalue placeholder in D2 Importer (#50278)

Known issues

• D2 Importer does not validate values for Editable ComboBox if they are not in the dictionary (#49115)

• D2 Importer does not validate Enabled and Visibility properties if they have no condition attached to them (#50327)

• Running IA Importer with values “16.x” for the InfoArchiveVersion parameter throws error (#50388)

migration-center 3.5

Features and enhancements

• Alfresco scanner now supports Alfresco 5.2 (#49977)

• Database scanner now supports multi-content Blob/Clob (#49260)

• Added support for scanning and importing xCP comments for folders (#49245)

• Added support for Documentum Content Server 16.4 (#49243)

• Added support for InfoArchive 16.3 (#49244)

• OTCS importer now supports folders of type email_folder types in OpenText Content Server (#49257)

• OTCS scanner now supports scanning documents and emails from Email folders (#49995)

• OTCS scanner now supports OTDS authentication (#50134)

• Added checksum verification feature for OpenText Content Server Importer (#49250)

• Added support for Oracle 12c Release 2 (#49259)

Fixes

• Fixed bug in the Alfresco importer rollback scripts (#49251)

• Fixed delta scan issue when only main object metadata changed (#50052)

• Fixed issue with description length in OTCS importer (#50118)

• Fixed error when setting subterm under non available term in SharePoint Online taxonomies (#49978)

• Fixed job getting stuck when connection to SharePoint server is lost during import (#50026)

• Fixed error when importing filename with apostrophe or plus sign in SharePoint (#49087, #49151)

• Fixed error when importing SharePoint lists with certain settings (#49975)

• Fixed rollback not being performed when a importing certain versions fails in SharePoint (#49974)

• Fixed bug where document gets overwritten when old version moved to folder with a different document of the same name in SharePoint (#4661)

migration-center 3.4

Features and enhancements

• Added comprehensive content hashing with different hashing algorithms and encodings for the following Scanners Documentum, SharePoint, Database and Filesystem (#11636)

• Filesystem Importer: XML Metadata file now contains elements for all null and blank attributes (#11606)

• InfoArchive Importer: migrating Documentum AuditTrails is now supported (#11610)

• InfoArchive Importer: migrating Documentum Virtual Documents with children relations is now supported (#11683)

• OpenText Importer: migrating opentext_email objects is now supported (#11670)

• SharePoint Online Importer: added content integrity checking feature for imported Documents (#8296)

• SharePoint Scanner: scanning entire version trees as a single migration-center object is now supported (#11641)

• New system attributes are now available in transformation rules for all adapters (#11941)

Fixes

• Fixed objects not being scanned when reading permissions failed in Filesystem Scanner (#11779)

• Fixed table key lookup query being case sensitive in OpenText Importer (#11772)

• Fixed length limitation for Table Key Lookup attributes in OpenText Importer (#11777)

• Fixed setting attribute values from a different object to a category that has multiple rows when using multiple threads in OpenText Importer (#11797)

• Improved logging for OpenText Importer (#11781)

• Fixed issue where the initializer thread was still running in the background when a job was being stopped manually (#11739)

• Fixed not being able to delete certain Scheduler runs that took more than 2 seconds to delete (#11889)

migration-center 3.3

Features and enhancements

• Sharepoint Scanner:

  • Added support for SharePoint 2016 (#10999)

  • Added support for CAML queries (#11629)

  • Added support for scanning SharePoint internal attributes (#11653)

• Added support for scanning only current version in eRoom scanner (#11649)

• Filesystem Scanner:

  • mc_content_location and original_location are now available in transformation rules when using moveFilesToFolder (#11474)

  • Added parameter for specifying the date format for extracting extended metadata with unusual format (#11673)

  • Added possibility of scanning permissions (#11720)

  • Upgraded to latest version of Tika Libraries (#11693)

• Added support for InfoArchive 4.1 and 4.2 (#10325)

• Added support for migrating SharePoint folders and List Items into InfoArchive (#11639)

• OpenText importer:

  • now support inheriting folder categories when importing folders (#11674)

  • now support inheriting permissions (#11631)

  • now supports setting null values for popup / dropdown attributes (#11550)

Fixes

• Fixed applyD2RulesByOwner error message when using multiple threads in D2 (#11597)

• Fixed some renditions being scanned twice in Documentum scanner (#11740)

• Fixed wrong file path in log for Filesystem importer (#11469)

• Fixed date values not being properly converted to XML format in some cases for InfoArchive importer (#11672)

• Fixed contentless documents failing when ‘nocontent’ is specified in InfoArchive importer (#11656)

• Fixed missing parent_object_id when scanning delta versions in OTCS Scanner (#11750)

• Fixed importing documents that have date table key lookup attribute failing in OTCS Importer (#11576)

• Fixed error when scanning uncommon managed metadata in SharePoint scanner (#11621)

• Fixed only latest content exported for each version of a document in SharePoint scanner (#11657)

• Fixed exportLocation parameter description when using local path in SharePoint scanner (#11568)

• Fixed error when scanning documents with non-mandatory but empty taxonomy field in SharePoint scanner (#11652)

• Fixed lookup attributes not being scanned at all in SharePoint scanner (#11655)

• Improved OTCS scanner documentation (#11667)

• Corrected version labels in Installation Guide (#11622)

• Fixed Linux Jobserver classpath values (#11690)

migration-center 3.2.9

Features and enhancements

• New Documentum In-Place Adapter (#11490)

• Alfresco Importer now supports Alfresco 5.2 (#10772)

• Documentum Importer - added support for CS 7.3 (#9927)

• D2 Importer

  • Added support for D2 version 4.7 (#10777)

  • Changed D2 DQL and Taxonomy validation to be done by the D2 API (#10317)

  • Added information regarding folder migrating options in the D2 Importer User Guide (#10754)

• InfoArchive Importer

  • Added support for multiple content files per AIU (#8877)

  • Added support for multiple Object Types (#8877)

  • Added support for Custom Attributes inside the eas_sip.xml file (#9405)

  • Added support for calculating the PDI file checksum with SHA-256 and base64 encoding (#11418)

• OTCS Scanner is now able to export rendition types (#11419)

• OTCS Importer now supports Extended Attributes Model (#11424)

• SharePoint Importer now does extra check to avoid overwriting existing content with the same List Item ID when trying to move content to different libraries (#11465)

• Added warning regarding using multiple Jobservers with Sharepoint Importer (#11459)

Fixes

• OpenText Importer: fixed java heap space error when importing large size renditions. (#11426)

• OpenText Importer: fixed the authentication cookie refreshment for impersonated user (#11396)

• OpenText Scanner: fixed out of memory error when scanning objects with size larger than 20MB (#11393)

• OpenText Scanner: fixed out of memory error when scanning objects with size larger than 8GB (#11434)

• Sharepoint Importer: fixed updates to intermediate version being applied to the latest version (#11458)

• Sharepoint Importer: fixed a case that caused the importer to not finish (#10338)

• D2 Importer: Fixed validation for certain DQLs containing placeholders (#10318)

• D2 Importer: Fixed validation of certain taxonomies (#11549)

• Fixed a jar conflict between OpenText Importer and Sharepoint Scanner (#11487)

Known issues

• Multi-threaded import using applyD2RulesByOwner fails for some objects in D2 Importer

• Remaining issues from the main release 3.2 to 3.2.8 Update 2 also apply to release 3.2.8 Update 3 unless noted otherwise.

migration-center 3.2.8 Update 3

Features and enhancements

• Add support for migrating to DCM 6.7 (Documentum Compliance Manager).

Known issues

• Remaining issues from the main release 3.2 to 3.2.8 Update 2 also apply to release 3.2.8 Update 3 unless noted otherwise.

migration-center 3.2.8 Update 2

Features and enhancements

• Added support for xCP comments in Documentum Scanner and Documentum Importer (#10886)

• Added support for “dm_note” objects in Documentum Scanner and Documentum Importer (#10887)

• Added support for multi-page content in Documentum Scanner, Documentum Importer and D2 Importer (#11271)

• Added support for extracting content from BLOB / CLOB column types in the Database Scanner (#10899)

Fixes

• Fixed logging the version of the OpenText Importer in the run log (#11322)

• Fixed setting the version description attribute in OpenText Importer (#11270)

Known issues

• Documentum scanner/importer: The scanned/imported “dm_note” objects are not counted in the job run report (#11391)

• DQLs that have enable(row_based) are not processed correctly in the D2 Importer (#11390)

• Remaining issues from the main release 3.2 to 3.2.8 Update 1 also apply to release 3.2.8 Update 2 unless noted otherwise

migration-center 3.2.8 Update 1

Features and enhancements

• New OpenText scanner: supports scanning documents, compound documents and folders from OpenText repositories version 9.7.1, 10.0 and 10.5. Specific OpenText features are supported like scanning categories, classification, permissions and shortcuts.

Fixes

• Several bug fixes regarding validating DQL queries and Taxonomies when using property pages in D2 Importer.

migration-center 3.2.8

Features and enhancements

• Added support for D2 LSS (Life Sciences Solution) version 4.1 (#9990)

• Added multi-threading capabilities to the D2 importer (#10107)

• Added support for Alfresco version 5.1 (#10354)

• Added support for OpenText Content Server version 16.0 (#9937)

• Added support for SharePoint 2016 (#9925)

• Improved SharePoint Online Importer performance when applying internal attributes and taxonomies (#10314)

• Added support for InfoArchive 4.0 (#9926)

• Added support for Documentum ECS (Elastic Cloud Storage) (#9783)

Fixes

• Alfresco Scanner: fixed scanning duplicates on delta scanning a new version for documents created directly in the Alfresco Share interface (#10013)

• InfoArchvie Importer: fixed nullPointer exception when importing objects without content (#10746)

• Filesystem Importer: fixed logging message when setting owner fails (#10326)

• SharePoint Importer: fixed setting author and editor attributes in a multi-domain environment (#10171)

• SharePoint Scanner: fixed job finishing successfully with incorrect credentials (#9939)

• MC Client: fixed description for RepeatingToSingle transformation function (#10291)

Known Issues

• D2 Importer:

  • importing version updates with CURRENT not set to latest version fails (#10784)

  • the CURRENT label is always set to the latest version when applying Lifecycle (#10686)

  • importing branched versions with multiple and no r_version_label associated fails (#10460)

  • D2 importer does not work with D2 4.5 or 4.1 when Jobserver runs on Java version 1.8 (#10384)

migration-center 3.2.7 Update 4

Features and enhancements

• Improved Sharepoint and Sharepoint Online Importers performance when setting Taxonomies and internal attributes. (#10423)

• Improved Sharepoint Importer Error Reporting in certain cases. (#10299)

Known Issues

• Remaining issues from the main release 3.2 to 3.2.7 Update 3 also apply to release 3.2.7 Update 4 unless noted otherwise

migration-center 3.2.7 Update 3

Features and enhancements

• Documentum Importer can attach now documents to a given lifecycle.

Fixes

• FirstDoc importer: Fix a java.lang.ClassCastException error when importing to FDQM module

• FirstDoc importer: Fix importing versions when there is an attribute count difference in the repeating group between create SDL and document definition SDL.

Known Issues

• Remaining issues from the main release 3.2 to 3.2.7 Update 2 also apply to release 3.2.7 Update 3 unless noted otherwise.

migration-center 3.2.7 Update 2

Features and enhancements

• D2 Importer now supports only D2 version 4.6. The older D2 versions are only supported by the previous versions of migration-center

• OpenText Importer now supports creating OpenText Compound Documents

• OpenText Importer now supports importing renditions

• IBM Domino Scanner:

  • Large attribute values can now be split into chunks of maximum 4000 bytes

  • Added custom attributes: "attachmentItemName" - name of item that an attachments was attached to in the original Domino document, "attachmentName" - name of the attachment in the original document and "$dominoNoteID$" - NoteID of the document in the database that it originates from.

Fixes

• Documentum Scanner: Scanning version trees having versions of multiple object types

• OpenText Importer: Error messages concerting a single attribute do not have the attribute name

• OpenText Importer: Categories not being set if no associations are made for it

• Sharepoint Scanner: Documents with paths longer than 260 characters failed to be scanned

Known Issues

• Running a SP scanner with incorrect credentials on a Sharepoint with anonymous authentication enabled, does not show errors.

• Remaining issues from the main release 3.2 to 3.2.7 Update 1 also apply to release 3.2.7 Update 2 unless noted otherwise.

migration-center 3.2.7 Update 1

Features and enhancements

• Alfrecso scanner now supports scanning version check-in comments

• Alfresco importer now supports importing version check-in comments

• Documentum adapter supports scanning/importing version trees with different object types in them

• InfoArchive importer officially supported on the Linux jobserver

• InfoArchive importer now supports ingestion via InfoArchive Webservices

• OpenText Importer now supports inheriting categories from folders

• OpenText Importer now supports setting values for attributes grouped within a Set attribute

Fixes

• InfoArchive Importer:

  • fixed text inside SIP xml files generated without indent

  • fixed ZIP files not being rolled back when there is not enough memory on disk

• OpenText Importer:

  • fixed impersonate user not working as expected

  • fixed importer not working when DFC not installed

Known Issues

• DocumentumNCC scanner: null pointer exception when scanning documents without content

• InfoArchive importer: SIPs are imported successfully but marked as failed when moveFilesToFolder does not have write permissions

• OpenText Importer: Error messages concerting a single attribute do not have the attribute name

• OpenText Importer: Categories are not set if no associations are made for it

• Sharepoint Scanner: Documents with paths longer than 260 characters fail to be scanned

• Remaining issues from the main release 3.2 to 3.2.7 also apply to release 3.2.7 Update 1 unless noted otherwise.

migration-center 3.2.7

Features and enhancements

• New OpenText importer: supports importing documents and folders to OpenText repositories version 10.0 and 10.5. Specific OpenText features are supported like setting categories, classification, permissions, shortcuts to the imported documents and folders.

• New SharePoint Scanner: supports the scan of SharePoint 2007, 2010 and 2013. Supports scanning documents, folders, listitems, lists and document libraries. Replaces the old scanner which has been retired.

• New SharePoint Importer: supports SharePoint 2010 and 2013 and uses REST API. Support import of documents, folders, listitems, lists and document libraries.

• Retired the previous SharePoint Importer as SharePoint Legacy: new installations will not have it. Updated installations will have it under the name of SharePoint Legacy.

• SharePoint Online Importer supports now documents, folders, listitems, lists and document libraries. Relations can be imported now as attachments for listitems.

• D2 importer supports now creating folders based on the paths provided to documents.

• Alfresco importer supports now the Alfresco 5.0.

• Alfresco scanner and importer: categories and tags are exported and imported using the values displayed in the interface instead of using internal ids.

Fixes

• Alfresco scanner and importer:

  • Fixed a NullPointerException when scanning documents with aspects from Alfresco.

  • Fixed the value of the content location attribute when scanning documents with skipping content.

  • The content location is now available in the attribute “mc_content_location” that is accessible to the transformation engine.

  • Fixed importing a new document version when the first link was modified compared with the previous version.

  • Improve the message description of several errors that may happen when importing updates and versions.

• Documentum scanner:

  • Fixed a query error when scanning a repository having DB2 as database.

  • Fixed scanning version tree having multiple types.

  • Fixed the content location for the documents without format.

• Box importer:

  • Fixed setting “content_created_at” and “content_modified_at” to the imported files.

• Filesystem scanner:

  • Fixed out of memory when scanning more than 1 million of files

  • Fixed the case when scanning multiple folders like: <some folder path>\FName|<some folder path>\FName with Space. In the previous version the second folder was ignored without any error message.

  • Report properly the invalid paths when scanning multiple folders.

  • Fixed a possible performance issue when scanning extended metadata.

• Filesystem importer:

  • Fixed a NullPointerException when setting “modified_date” without setting the “creation_date”

  • Fixed the case when the target file was overwritten by the metadata file when they were having the same name.

• SharePoint Online importer:

  • Fixed updates imported as new versions.

  • Fixed import fails only with major version enabled.

  • Fixed null pointer exception when setting empty “Group or Person” or “Hyperlink” column.

  • Fixed items created for failed jobs are now rolled-back where possible.

  • Fixed running with invalid credentials does not set the error status.

  • Fixed proper log messages are set now for multiple attribute setting errors.

• Eroom scanner

  • The “er:Path” attribute does not contains the file name anymore.

• Database

  • Allow installing migration-center on a non-CDB Oracle 12c instance.

  • Fixed the throwing two errors when upgrading from version 3.2.5 or older. This was the case when filesystem importer was not licensed.

• Client

  • Fixed installing the client on Window 8 and Windows 2012 server. No manual registry configuration is required.