Environment Window - General Information
The General Information section in the Environment Window holds the following information:
Note: Always click Save Changes after editing the General Information section.
Environment Name
Mandatory settings.
Populate the following settings:
- TDM Environment Name, when creating a TDM task, select the name of the source and target environments. It is recommended to set the same name in the TDM Environment Name and Fabric Environment Name settings.
- Fabric Environment Name, select the environments deployed to Fabric from the dropdown list.
Environment Additional Information
Optional settings:
- Description.
- Contact person settings.
Environment Type
Mandatory setting.
Set the environment type to one of the following:
Source, this can only be defined as a source environment in a TDM task. For example, in a Production environment a TDM task can extract entities but cannot insert entities.
Target, this environment can only be used as a target environment in a TDM task.
Both, this environment can be used as both a source and target environment in the TDM task. This mode is useful for Data Flux tasks.
Example:
- A tester backs up data in a testing environment before running functional tests by creating and executing an Extract Data Flux task on the testing environment. The testing environment is set as a source environment. During the execution of the Extract task data is saved in the TDM Fabric repository.
- During functional tests the data in the testing environment becomes corrupted and needs to be replaced with the last backed up version created in the testing environment. The tester creates a [Load Data Flux task] and sets the testing environment to be both source and target.
Override Sync Mode
Optional setting.
Override mode can be set if the Environment Type is Source or Both. This setting overrides the default Fabric Sync mode when extracting the selected entities from the source environment and sets another Sync mode which can be overridden on both the [environment and task] levels.
The following values can be set in Override Sync Mode settings:
Do not Sync
Do not sync the entities from the source when running a TDM task with the environment as a source, instead get the entities from Fabric. Note that if the entities do not exist in Fabric, the task's execution will return an error. This mode is needed when access to the source environment is limited by the organization.
Example:
- The Production team allocates a predefined window to extract a subset of entities from Production. Access to Production is restricted apart from to the predefined window.
- An Extract task must be created and run to extract a large subset of entities from Production and to migrate them into Fabric. The Override Sync Mode in the Production TDM environment must be set to Do not Sync to avoid additional access to Production. Other TDM tasks in the Production source environment get data entities from Fabric.
Always Sync
Always sync the entities from the source when running a TDM task with the environment as a source.
Click for more information on [how overriding the sync mode impacts the task execution] process.
Environment Owners
- Admin users can add or remove one or several environment owner users to or from an environment. An environment owner user can be added to several environments.
- An environment owner user can be attached to an environment with tester permissions. For example, a user is attached to ENV1 as the environment owner and attached to ENV2 as a tester.
- The environment owner can edit an environment except for adding or removing environment owner users. Only Admin users can add or remove environment owners.
- The environment owner can create and execute TDM tasks on their environment without limitations, unlike tester users who can define a task on an environment based on their permissions.
Click for more information about environment roles and permissions.
Who is an Environment Owner?
Environment owner users are usually Testing team leaders and are defined under a dedicated group in the LDAP system.
To enable setting authorized users as environment owners in the TDM GUI, the Group Name must be also defined in the TDM GUI configuration file [config.js] in ownersGroupName.
Note that the TDM GUI installation includes an internal LDAP for development. The environment owners Group Name in the internal LDAP is k2venvownerg. Therefore the default value of ownersGroupName in the config.js file is k2venvownerg.
How Do I Add or Remove Environment Owners To or From an Environment?
Click Environment Owners and select a user from the list.
Click Environment Owners again and select another user from the list to set an additional environment owner.
Click the X on an environment owner/s username to remove them from the environment:
Environment Window - General Information
The General Information section in the Environment Window holds the following information:
Note: Always click Save Changes after editing the General Information section.
Environment Name
Mandatory settings.
Populate the following settings:
- TDM Environment Name, when creating a TDM task, select the name of the source and target environments. It is recommended to set the same name in the TDM Environment Name and Fabric Environment Name settings.
- Fabric Environment Name, select the environments deployed to Fabric from the dropdown list.
Environment Additional Information
Optional settings:
- Description.
- Contact person settings.
Environment Type
Mandatory setting.
Set the environment type to one of the following:
Source, this can only be defined as a source environment in a TDM task. For example, in a Production environment a TDM task can extract entities but cannot insert entities.
Target, this environment can only be used as a target environment in a TDM task.
Both, this environment can be used as both a source and target environment in the TDM task. This mode is useful for Data Flux tasks.
Example:
- A tester backs up data in a testing environment before running functional tests by creating and executing an Extract Data Flux task on the testing environment. The testing environment is set as a source environment. During the execution of the Extract task data is saved in the TDM Fabric repository.
- During functional tests the data in the testing environment becomes corrupted and needs to be replaced with the last backed up version created in the testing environment. The tester creates a [Load Data Flux task] and sets the testing environment to be both source and target.
Override Sync Mode
Optional setting.
Override mode can be set if the Environment Type is Source or Both. This setting overrides the default Fabric Sync mode when extracting the selected entities from the source environment and sets another Sync mode which can be overridden on both the [environment and task] levels.
The following values can be set in Override Sync Mode settings:
Do not Sync
Do not sync the entities from the source when running a TDM task with the environment as a source, instead get the entities from Fabric. Note that if the entities do not exist in Fabric, the task's execution will return an error. This mode is needed when access to the source environment is limited by the organization.
Example:
- The Production team allocates a predefined window to extract a subset of entities from Production. Access to Production is restricted apart from to the predefined window.
- An Extract task must be created and run to extract a large subset of entities from Production and to migrate them into Fabric. The Override Sync Mode in the Production TDM environment must be set to Do not Sync to avoid additional access to Production. Other TDM tasks in the Production source environment get data entities from Fabric.
Always Sync
Always sync the entities from the source when running a TDM task with the environment as a source.
Click for more information on [how overriding the sync mode impacts the task execution] process.
Environment Owners
- Admin users can add or remove one or several environment owner users to or from an environment. An environment owner user can be added to several environments.
- An environment owner user can be attached to an environment with tester permissions. For example, a user is attached to ENV1 as the environment owner and attached to ENV2 as a tester.
- The environment owner can edit an environment except for adding or removing environment owner users. Only Admin users can add or remove environment owners.
- The environment owner can create and execute TDM tasks on their environment without limitations, unlike tester users who can define a task on an environment based on their permissions.
Click for more information about environment roles and permissions.
Who is an Environment Owner?
Environment owner users are usually Testing team leaders and are defined under a dedicated group in the LDAP system.
To enable setting authorized users as environment owners in the TDM GUI, the Group Name must be also defined in the TDM GUI configuration file [config.js] in ownersGroupName.
Note that the TDM GUI installation includes an internal LDAP for development. The environment owners Group Name in the internal LDAP is k2venvownerg. Therefore the default value of ownersGroupName in the config.js file is k2venvownerg.
How Do I Add or Remove Environment Owners To or From an Environment?
Click Environment Owners and select a user from the list.
Click Environment Owners again and select another user from the list to set an additional environment owner.
Click the X on an environment owner/s username to remove them from the environment:
