Initial Setup—First Week
  • 26 Mar 2024
  • 4 Minutes to read
  • Contributors
  • Dark
  • PDF

Initial Setup—First Week

  • Dark
  • PDF

Article summary

This topic is related to the following sections:

About the Initial Setup and First Weeks on a Project

A few tasks are to be completed upon arrival at the new project:

  • The Project Manager or IT Lead meets with the Client IT Lead to determine access for the team to the client legacy systems and SAP. 

  • The Syniti Cloud DevOps team creates a Tenant for the project.

  • The Project Manager determines the scope of the project—Projects, Releases, Milestones, and Objects in scope.

  • The team is assigned Datasets for conversion.

Initial Setup of Supporting Database and Systems for a Working Migrate System

STEP 1 - Configure Working Database Server

  1. Create a named Migrate system account in the working database server. (SQL Server, HANA DB, or Oracle DB)

  2. Connect to the database using the Migrate system account.

  3. Create the MIGRATE Database. (Stores Value Mapping tables XTVALUEMAP and LIST_TARGET_VALUE)

  4. Create the REPORT Database and REPORTL database. (Stores all reports as tables of the data for snapshot)

  5. Create the CONSTRUCT Database. (Stores all Construct Pages as tables and views)


    CONSTRUCT must be a SQL Server database.

  6. Create all working databases for project

    1. SRCxxx database for every Legacy Source system

    2. TGTxxx database for every Target System

    3. One set of working databases for each Subject Area / Environment for DEV, LOAD (Ex: WRKOTC, WRKOTCL)

STEP 2 - Set up Syniti Knowledge Platform Systems

  1. Configure the SKP Connector for the project

  1. Configure the Syniti Replication Hub

  1. Create the Systems

    1. Create the Migration Working Database Server as a System (Click the + icon to create new systems)

      1. Create the Connection

      2. Test the Connection

      3. Scan the Database to pull in the metadata

    2. Create the Construct Database Server as a System (Click the + icon to create new systems)


      If Construct is NOT on the same Migration Working Database Server, then create it as a System. (SQL Server for Construct or sharing with Migration)

      1. Create the Connection

      2. Test the Connection

      3. Scan the Database to pull in the metadata

    3. Create the System Database Servers for all legacy and target systems

      1. Create the Connection for each source using specific Logon IDs

      2. Test the Connection

      3. Scan the Database to pull in the metadata

At this point, the setup of Syniti Migrate is ready for the new project. There is a list of sequenced steps to set up an initial project within the system. These steps are discussed below with links to the sections within this help text to locate the detailed documentation for use.

STEP 3 - Setup of a New Project within Syniti Migrate

In this order, each step builds out the project within Syniti Migrate. The user checks that each step is complete without issues before proceeding to the next step. At any time, if the process fails to work, take images, and contact the Syniti System Support team for instructions for correction. The first six steps of this process are added to a setup wizard - Administer > Setup > Guided Setup.

  1. Setup the Parameters of the project for Syniti Migrate including the internal or external ETL processing (ETL Tool).

  2. Create two Datasource Servers.

    • Create the Migration Working Database server

    • Create the Construct server (even if on the same physical server).


      These database servers are linked to connections within Syniti Knowledge Platform. See STEP 2 - Create the systems above.

  3. Setup the Environments used for DEV and LOAD ETL Processing and Reporting. The Development Area designates where to create reports within the Datasource assigned. Create all Working Database Datasources.

  4. Create the Subject Areas to group together multiple Datasets to migrate data based upon the client's processes. The subject area is linked to the Development Areas.

  5. Assemble the Development Areas to group together a development area, environment, and Working Datasource.

  6. Setup the Imported Working Databases that are created as connections within Syniti Knowledge Platform and used to store the tables, views, functions, and stored procedures for the objects.

  7. Manage the Applications to filter tables required for each of the Datasources that are set as Import All = inactive. It is within this section that a filtered list of tables are stored for the Import Metadata process by table and column.

  8. Create Datasources

    • All System Datasources are set up in this section based upon Application and Instance. They are then linked to the Systems, Connections and Agents stored in the Syniti Data Catalog.

    • REPORT and MIGRATE Datasources are set up as part of the system defaults and must be attached to the Migration Working Database server. Once MIGRATE is modified for the Server information, the system will pull in the Tables and Functions. Refer to Verify Migrate Database Upgrade for more information.

    • Create Datasources for the additional non —DEV environments - REPORTL or REPORTQ as Datasource Type = Report.

    • Create the CONSTRUCT datasource as type = Construct and attach it to the Construct Database Server.

    • All Scanning for Datasources is pulled using the Syniti Data Catalog system to import the metadata.

  1. Create the Snapshot Datasources for all Target and Source Snapshot Datasources are set up and table data is pulled from the System Datasources using the Syniti Replicate system.

  1. Build the Dataset Design—Datasets are added and maintained in this section. All active Data Elements are part of the Mappings.

  1. Create the Project — The Project, Release, Milestones and Deployments are all set up in this section with validity time frames and Development Areas are attached to produce a working migration.

The user is now ready for mapping sessions.


Was this article helpful?


Eddy, a generative AI, facilitating knowledge discovery through conversational intelligence