--- title: "Environments" slug: "environments" status: "update" updated: 2026-07-14T12:30:00Z published: 2026-07-14T12:30:00Z canonical: "skthelp.syniti.com/environments" stale: true --- > ## Documentation Index > Fetch the complete documentation index at: https://skthelp.syniti.com/llms.txt > Use this file to discover all available pages before exploring further. # Environments This topic relates to the following sections: - [Guided Setup](/v1/docs/guided-setup) - [Parameters](/v1/docs/parameters) - [Servers](/v1/docs/servers) - [Subject Areas](/v1/docs/subject-areas) - [Manage Development Areas](/v1/docs/development-areas) - [Add a Datasource to a Development Area](/v1/docs/maintain-working-datasources) - [Adding & Editing Datasources](/v1/docs/maintain-working-datasources) - [Subsequent Tasks for Environments](/v1/docs/subsequent-tasks-for-environments) - [Working in Multiple Execution Environments](/v1/docs/working-in-multiple-execution-environments) ## About Environments This section allows a project to design, build, execute, and store the data within multiple Environments to prevent loss of work due to a Mock load as example. By designing multiple environments, the developers may continue to work on fixes and changes to a conversion process while the team holds a Mock conversion. Each environment groups together a set of Development Areas and Report Cache database. These environments are then integrated into the Migration Reporting pages and ETL processing pages. Refer to [Working in Multiple Execution Environments](/v1/docs/working-in-multiple-execution-environments) for more information on how to plan for setting up multiple execution environments and how data moves through environments using the same production code in Migrate. Environments work in conjunction with [Working DB Object Promotion](/v1/docs/working-db-object-promotion). The tables, views, rules, and stored procedures of a Development Area like WRKFIN as example may be copied into a newly created Development Area assigned to the Environment using the Working DB Object Promotion process to form a new Development Area like WRKFINL. Environments can be used for projects that require multiple migration servers using the same Migrate Datasource for building and loading data. In a project using multiple environments, it would be as example Development and Load. This page contains the data that pertains to each Environment of the Syniti Migrate Application. Installation of Syniti Migrate provides DEV environment as a default for ETL and Reporting. If the team should require additional environments, they may be added within this page and then linked to a **Report Cache Datasource**. The client may view by Environment the reports stored within [Migration Reports](/v1/docs/migration-reports) or [Deployment Reports](/v1/docs/deployment-reports). > [!NOTE] > Note > > SAP Data Services ETL provides Substitution Parameters to setup for a DEV and LOAD therefore allowing for one set of datastores with multiple configurations to point to each of the databases. Within SAP Data Services pathway - **Tools > Substitution Parameter Configurations** , the team can select the defaulted configuration which changes parameters for the Load vs Dev migration runs. Each user also sets up Configurations within each Datastore to point to the DEV or LOAD configuration and database associated with each. ## Prerequisites REPORT Datasources should be created within Datasources prior to updating the Environments page so they may be attached to the Environment. Refer to section [Catalog > Datasources > Adding & Editing Datasources](/v1/docs/adding-editing-datasources) for more details of building Datasources of type Report. ## Users & Roles for Environments The Admin is responsible for maintenance of the Environments. This section is stored within Administer and only users granted Admin access maintains this process. ## Working in Environments View the following page by navigating to **Administer > Setup > Environments** from Syniti Migrate Homepage or access by using the **Guided Setup**. The system provides one default Environment. The DEV or Development Environment is set to Default active. The **DEVELOPMENT AREAS** button provides access to manage [development areas](/v1/docs/development-areas). ![](https://cdn.document360.io/ca09b4e9-1857-4c63-9f0e-1f25f166f447/Images/Documentation/image (5).png?sv=2026-02-06&spr=https&st=2026-11-17T19%3A14%3A58Z&se=2026-11-17T20%3A14%3A58Z&sr=b&sp=r&sig=uWPv3HAZcOZJ65Vtvww0c9Q1A1zhadC2eh2CZMRWCaE%3D) Environments The Environments grid displays the following fields: | Heading | Description | | --- | --- | | Name | The name of the Environment. (Required) | | Description | The Environment description. | | Report Cache | This field stores the Datasource for the Cached Reports for this Environment. | | Migrate Datasource | The base datasource for Migration. > [!NOTE] > Note > > In a multiple server configuration, the Migrate Datasource for all Environments should point to the MIGRATE datasource of the default Environment (as seen in the image above). | | Active | Toggle switch to make the table Active/Inactive. > [!NOTE] > Note > > Defaults as Active. | | Is Default | Displays the DEV Environment set as the Default. Display only field. | | Color | Color used to visually identify the environment across Migrate pages. | ## Add an Environment Additional Environments may be added by a click on the **Add** ![](https://cdn.document360.io/ca09b4e9-1857-4c63-9f0e-1f25f166f447/Images/Documentation/47993630-023f-4445-9e77-c7eada97df2b.png?sv=2026-02-06&spr=https&st=2026-11-17T19%3A14%3A58Z&se=2026-11-17T20%3A14%3A58Z&sr=b&sp=r&sig=E6wiSTinnPcFWS%2FcvOxc6GLnldm%2FX2rD3oRM4BwFWrM%3D) icon. ![](https://cdn.document360.io/ca09b4e9-1857-4c63-9f0e-1f25f166f447/Images/Documentation/image-A2D1YODW.png?sv=2026-02-06&spr=https&st=2026-11-17T19%3A14%3A58Z&se=2026-11-17T20%3A14%3A58Z&sr=b&sp=r&sig=GFucItWKKRho39z5AjUQBLtLJRoQYQYcYwCQwE5X%2BxY%3D) Environments: Add the Load or Production environment Enter the Environment field values as shown below: | Field Name | Description | | --- | --- | | Environment Name* | The name of the environment. (Required) | | Description | The environment description. | | Report Cache Datasource* | Datasource for the Cached Reports for this environment. (Required) | | Migrate Datasource* | Use the same Migrate datasource that is registered in the Dev environment as the Migrate Datasource for the new environment. Ex: Migrate (Required) > [!NOTE] > Note > > In a multiple server configuration, the Migrate Datasource for all Environments should point to the MIGRATE datasource of the default Environment (as seen in the image above). Registering additional Migrate datasources may lead to inconsistent and unconsolidated data mapping rules during a load cycle. | | Color | Select a unique color from the list or use custom color picker for each environment. | | Is Default | Display switch to show the Default for DEV environment. | | Active | Toggle switch to make the table Active/Inactive. > [!NOTE] > Note > > Defaults as Active. | > [!NOTE] > Note > > Each Report Cache Datasource is created by using the wizard stored within the Environment Edit window. Refer to section [Administer > Setup > Environments > Adding & Editing Report Datasources](/v1/docs/adding-editing-report-datasources) for detailed information on this process. > [!NOTE] > Note > > The MIGRATE Datasource is defaulted as part of the system. To add the same MIGRATE datasource for LOAD environment and others, refer to section [Administer > Setup > Environments > Adding & Editing Migrate Datasources](/v1/docs/adding-editing-migrate-datasources) for detailed information on this process. When finished with edits, click the **Save** ![](https://cdn.document360.io/ca09b4e9-1857-4c63-9f0e-1f25f166f447/Images/Documentation/224d9543-bd89-4779-ac4f-e5962ad7fc6e.png?sv=2026-02-06&spr=https&st=2026-11-17T19%3A14%3A58Z&se=2026-11-17T20%3A14%3A58Z&sr=b&sp=r&sig=%2BqRqffy3uc3mkY6yrOGS9lOfO1wUMJokZHG4AQ7s4N8%3D) icon to complete. ## Edit an Environment To edit an existing Environment, click on the **Edit** ![](https://cdn.document360.io/ca09b4e9-1857-4c63-9f0e-1f25f166f447/Images/Documentation/a9663191-fbe8-443f-ac77-04968dc7816e.png?sv=2026-02-06&spr=https&st=2026-11-17T19%3A14%3A58Z&se=2026-11-17T20%3A14%3A58Z&sr=b&sp=r&sig=9Uf2mNjJETafhawfxmnTGDiEzrf464wRI1OHAOnGAI8%3D) icon to display the Environment details window. ## Delete an Environment To delete an existing Environment, click on the **Delete** ![](https://cdn.document360.io/ca09b4e9-1857-4c63-9f0e-1f25f166f447/Images/Documentation/2ece4e7c-e6f5-4244-b3da-cb1cc6fb4c8f.png?sv=2026-02-06&spr=https&st=2026-11-17T19%3A14%3A58Z&se=2026-11-17T20%3A14%3A58Z&sr=b&sp=r&sig=qW2sdrAJO98ChJff8v%2FIwECW3zFa2cnTFSTAHoVb4BA%3D) icon to display the Environment Details page. Click **OK** to proceed and remove the environment or click on **CANCEL** to exit without changing.