LogoLogo
24.1
24.1
  • Overview
  • Legal Notice
  • Release Notes
    • Previous versions
  • Glossary
  • Abbreviations
  • Getting Started
  • Supported versions
  • Quick Start Guide
  • Installation Guide
    • System Requirements
    • Prerequisites
    • Install migration-center
    • Install migration-center on AWS
    • Start migration-center
    • Access Network Shares
    • Upgrade migration-center
    • Backup and Restore
    • Java configuration
    • Uninstall migration-center
  • WebClient User Guide
    • TR Function Reference
  • Third Party Open Source Libraries
  • Administration
  • Oracle Database Creation
  • Database Administrator’s Guide
  • Oracle Sizing Guide
  • Time zone handling
  • Documentum security enhancements
  • Common Parameters
  • Scanners
    • Amazon Comprehend Enrich Scanner
    • Alfresco Scanner
    • CSV & Excel Scanner
    • Database Scanner
    • Documentum Scanner
    • Documentum NCC Scanner
    • Domino Scanner
    • Exchange Scanner
    • Filesystem Scanner
    • OpenText Scanner
    • Outlook Scanner
    • SharePoint Scanner
    • SharePoint Online Scanner
    • Veeva Scanner
  • Importers
    • Alfresco Importer
    • AzureBlob Importer
    • Box Importer
    • Cara Importer
    • D2 Importer
    • D2 InPlace Connector
    • Documentum Importer
    • Documentum InPlace Connector
    • Documentum NCC Importer
    • Filesystem Importer
    • Hyland OnBase Importer
    • InfoArchive Importer
    • OpenText Importer
    • OpenText InPlace Connector
    • SharePoint Importer
    • SharePoint Online Importer
    • SharePoint Online Batch Importer
    • TrackWise Importer
    • Veeva Importer
Powered by GitBook
On this page
  • Introduction
  • Supported Versions
  • Features in common with DCTM inPlace
  • Importer Configuration
  • Importer parameters

Was this helpful?

Export as PDF
  1. Importers

D2 InPlace Connector

Was this helpful?

Introduction

The D2 InPlace connector takes the objects processed in migration-center and imports them back in a Documentum or D2 repository. The D2 InPlace connector extends the Documentum InPlace connector and it works together only with Documentum scanner.

The D2 InPlace connector supports a limited amount of D2 features besides the ones already available in the Documentum InPlace connector such as applying auto-security functionality, auto-linking functionality, auto-naming functionality and validating the values against a property page. All these D2 features can be applied based on the owner user or the migration user.

The D2 InPlace currently supports the following D2 versions: 16.5, 16.6, 20.2, 20.4.

Supported Versions

The supported D2 Content Server versions are 20.2, 20.4, including service packs. Any combinations of DFC versions and Content Server versions supported by Opentext Documentum are also supported by migration-center’s D2 InPlace Importer, but it is recommended to use the DFC version matching the version of the Content Server targeted for import. The DFC must be installed and configured on every machine where migration-center Server Components is deployed.

Features in common with DCTM inPlace

The D2 inPlace connector supports all the regular DCTM based features supported by the DCTM inPlace connector. Please refer to the for details.

Importer Configuration

To create a new connector, select "D2InPlace" in the adapter Type drop down of the importer. After this, the list below will be filled with the specific D2InPlace parameters.

The Properties window of an importer can be accessed by double-clicking an importer in the list, by selecting the Properties button from the toolbar or from the context menu.

Importer parameters

The common adaptor parameters are described in .

The configuration parameters available for the Alfresco importer are described below:

  • username* Username for connecting to the target repository. A user account with super user privileges must be used to support the full D2/Documentum functionality offered by migration-center.

  • password* The user’s password.

  • repository* Name of the target repository. The target repository must be accessible from the machine where the selected Job Server is running.

  • moveContentOnly Flag indicating if the metadata will not be updated but only the content should be moved. This will save some processing in case there is no need to update any metadata.

  • autoCreateFolders This option will be used for letting the importer automatically create any missing folders that are part of “dctm_obj_link” or “r_folder_path”. Use this option to have migration-center re-create a folder structure at the target repository during import. If the target repository already has a fixed/predefined folder structure and creating new folders is not desired, deselect this option

  • defaultFolderType The Documentum folder type name used when automatically creating the missing object links. If left empty, dm_folder will be used as default type.

  • moveRenditionContent Flag indicating if renditions will be moved to the new storage. If checked, all renditions and primary content are moved otherwise only the primary content is moved.

  • moveCheckoutContent Flag indicating if checkout documents will be moved to new storage. If not checked, the importer will throw an error if a document is checked out.

  • removeOriginalContent Flag indicating if the content will be removed from the original storage. If checked, the content is removed from the original storage, otherwise the content remains there.

  • moveContentLogFile The file path on the content server where the log related to move content operations will be saved. The folder must exist on the content server. If it does not exist, the log will not be created at all. A value must be set when move content feature is activated by the setting of attribute “a_storage_type”.

  • numberOfThreads The number threads that will be used for importing objects. Maximum allowed is 20.

Parameters marked with an asterisk (*) are mandatory.

applyD2Autonaming Enable or disable D2’s auto-naming rules on import. See for more details.

applyD2Autolinking Enable or disable D2’s auto-linking rules on import. See for more details.

applyD2AutoSecurity Enable or disable D2’s auto-security rules on import. See for more details.

applyD2RulesByOwner Apply D2 rules based on the current document’s owner, rather than the user configured to run the import process. See for more details.

loggingLevel* See .

Documentum inPlace Adapter user guide
Autonaming
Autolinking
Security
Applying D2 rules based on a document’s owner
Common Parameters
Common Parameters