Environments

This topic relates to the following sections:

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 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. 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 or Deployment Reports.

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 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.

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 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 Defaults as Active.
Is Default	Displays the DEV Environment set as the Default. Display only field.
Color	Colors assigned by environment.

Add an Environment

Additional Environments may be added by a click on the Add icon.

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 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 for each environment.
Is Default	Display switch to show the Default for DEV environment.
Active	Toggle switch to make the table Active/Inactive. Note Defaults as Active.

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 for detailed information on this process.

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 for detailed information on this process.

When finished with edits, click the Save icon to complete.

Edit an Environment

To edit an existing Environment, click on the Edit icon to display the Environment details window.

Delete an Environment

To delete an existing Environment, click on the Delete icon to display the Environment Details page. Click OK to proceed and remove the environment or click on CANCEL to exit without changing.