Migration and Your Infrastructure

Purpose

This document provides a checklist of the platform and application requirements for a PoC data migration. It also provides a visualization of the infrastructure and mapping file specifications.

Requirements

The following Cognitive Toolkit and OpenText™ Content Server requirements are necessary when migrating from a file share to OpenText™ Content Server.

OpenText™ Content Server Requirements

The requirements for OpenText™ Content Server are the following:

Shinydocs Module installed on all Content Server nodes (ShinydocsService_1.6.x)
Service Account within OpenText™ Directory Services (OTDS) with the following permissions:
- Write
- Read
- Permission to write to Categories and Attributes
Destination folder(s) created
- Destination folder(s) is where data is migrated to
Category created with desired metadata fields

Note: Attributes that the Shinydocs Cognitive Toolkit will fill must not be a required attribute (required=false).

Additional specifications for later stages

The following details will be required for later stages of the migration process:

Username and Password for OTCS that was created in OpenText™ Content Server Requirements
URL of Content Server endpoint (ex. http://acmeServer.com/otcs/cs.exe)
For the Category/Categories the Cognitive Toolkit will provide values for:
- Node ID/Object ID (ex. 596888)
- Exact name of the category/categories
- Exact name of the fields the Cognitive Toolkit will populate

Cognitive Toolkit Requirements

Cognitive Toolkit requires hardware, software, and additional specifications.

Hardware

The following hardware requirements are necessary for a PoC migration:

Windows server 2012R2+, 2016, 2019/Windows 10
4 CPU Cores
16 GB Memory
15 GB Free Disk Space

For migrations of datasets larger than what is common during a PoC, please refer to the Requirement and Recommendations Matrix available within v2.10.0+ Analytics Engine, Visualizer, and Cognitive Toolkit Requirements.

Software

The software requirements are as follows:

.Net 4.7.2 or higher

Additional specifications

Read/Open permission on source data for the service account running the Cognitive Toolkit Executable
Connectivity between: File Share ↔︎ Index Cluster ↔︎ Machine Running Cognitive Toolkit for Migration ↔︎ OTDS ↔︎ OTCS

Mapping of Category/Attributes to Shinydocs Index field names: Mapping should be in JSON format

Business Requirements

Organizations may have additional business requirements to move forward with migration initiatives. It is recommend the following activities are completed with teams whose data is migrating prior to migration:

Redundant, Obsolete, and Trivial (ROT) concepts are shared with team and ROT rules applied to the index
Duplicate data definition is shared with team and tag duplicates tooling run against the index
File structure/taxonomy for content destination is discussed with team

Infrastructure Visualization

The following diagram depicts an infrastructure setup to support a data migration where OpenText™ Content Server is hosted in a cloud environment:

Fig. 1: Data migration from a file share to an instance of OTCS

Mapping File Specifications

By using a mapping file, index values can be used to populate values in OpenText™ Content Server. Shinydocs recommends that the mapping file is in JSON format. For the mapping template and an example of its use, please refer to the appendix items.

Mapping File Template

The following is the mapping template:

JSON

[  {    "comment": [      "The value of the name field should be the category id from Content Server you are trying to map:",      "Under the values section:",      "The left side should be the name of the attribute from Content Server (case sensitive)",      "The right side should be the name of the index field you are trying to map (you can use visualizer to get the exact name)"    ],    "name": 1,    "values": {      "content_server_attribute_name_1": "index_field_name",      "content_server_attribute_name_2": "index_field_name",      "content_server_attribute_name_3": "index_field_name",      "content_server_attribute_name 4": "index_field_name"    }  },  {    "name": 2,    "values": {      "content_server_attribute_name_1": "index_field_name",      "content_server_attribute_name_2": "index_field_name",      "content_server_attribute_name_3": "index_field_name",      "content_server_attribute_name-4": "index_field_name"    }  },  {    "name": 3,    "values": {      "content_server_attribute_name_1": "index_field_name",      "content_server_attribute_name_2": "index_field_name",      "content_server_attribute_name_3": "index_field_name",      "content_server_attribute_name_4": "index_field_name"    }  }]

Mapping File Example

The following is an example of the mapping template file in use:

JSON

[  {    "Example": 5485436,    "values": {      "Classification Code" : "classification",      "Retention Schedule"  : "retention_schedule",      "Original Path" : "path"    }  }