Copy Remote Repository

The Remote Repository Copy Functions in Datamaker enable connections between two repositories and make it possible to copy data from one repository to another. An administrator accesses the Remote Copy Functionality from the Project Manager window from any of the following levels:
tdm49
The Remote Repository Copy Functions in Datamaker enable connections between two repositories and make it possible to copy data from one repository to another. An administrator accesses the Remote Copy Functionality from the Project Manager window from any of the following levels:
  • Top level
  • Project level
  • Version level
  • Any level below a version level 
 The versions of the remote repositories must be the same.
You can perform the following actions:
Connect Remote Repository
Select the remote repository for connection:
image2015-12-8 18:11:11.png
Select Remote Projects
Follow these steps:
  • Select remote functionality to display the Remote Projects window:
image2015-12-9 16:36:24.png
  • Select the remote project
  • Select the right remote level for the menu option
  • Click the green arrow
Register Tables
Follow these steps:
  • Select a remote version in the Remote Projects window and click the green arrow.
  • Select a table for copying the remote definition from in the List of registered tables in the selected remote version. If any selected tables are already registered in the current version, a warning appears asking to continue or not. Cancel the operation by selecting No.
Copy Connection Profile
You can copy remote connection profiles to both SQL server and Oracle repositories. If the owner or group of the profile does not exist, the profile is not copied.
Follow these steps:
  1. Verify that the owner or owning group of the connection profile exists in the local repository.
  2. Connect to the repository to which you want to copy connection profiles from a remote repository.
  3. Expand the project tree and right-click the
    Projects
    parent node. Click
    Remote actions from different repository
    , then 
    Copy Profiles
    .
  4. If prompted, connect to the remote repository.
  5. Wait for the copy to finish and review the summary dialog.
Copy Variables
Follow these steps:
  1. Select any project/level to copy remote variables for the selected remote level to the current project level in the Remote Projects window. A list of all the variables available to the remote project level are displayed.
  2. Select the variables to copy to the current project. The top left four buttons provide access to:
    • Check if the variables are used
    • Variables preview value
    • Select and deselect the variables
  3. Select which remote level variable to copy to which current level. By default the equivalent levels are displayed, but you can select all the remote level variables to be copied to the version level, etc.
  4. Select Yes or No to proceed or to cancel copying the variables at this stage. If any variables are already defined in the current project/level, you are asked if you want to overwrite the values. 
Copy Data
Follow these steps:
  1. Select a data group in the current project to be able to copy remote data. Warning is given if a data group is not selected. 
  2. Select a data group to copy the data in Remote Projects window. Click the green arrow. A new window pops up to display the list of the tables that are used in the selected remote data group.
  3. Select the tables from which to copy the data. The system informs the user if the selected tables are already registered in the current version with the same definition. 
  4. Select to copy the variables of the remote data group when the remote data are copied.
Note
: In case one or more remote selected tables are not registered in the current version or their definition is different, warning is given and user is asked to select the tables to register. Select the tables to register/reregister or to proceed with the ones which are already registered with the same definition. 
If yes is selected, used variables in the data pool are copied to their equivalent level. A project level, or version level or data level variable that is used in the data pool is copied to the current project level, the version level or data level respectively. The remote publish level variables are copied to the publish level of the current project.
If any variables are already defined in the current project, the system queries overwriting of the existing variables.
Copy Version
When copying a remote version, all the registered tables of the remote version are registered with the same definition of the new version. The following are also copied:
  • Variables (optional)
  • Data pools
  • Actions
  • Subsets
  • Flowcharts
  • Test Matches, are copied if the publish level of the project of the new version is a Data level.
Otherwise a warning message is given to inform the user of:
  • Default Publish Jobs (optional)
  • Transformation Maps (optional)
In Remote Projects window, select a remote version to copy to the current project and click the green arrow.  
To simplify:
  • Remote Project --> remote-project
  • Current Project --> to-project    
  • Remote Version --> remote-version
  •  New Version --> to-version
Specify the name and the description of the new version that the selected remote version is copied to. Choose to copy project level variables to:
  • The version level 
  • The project level of to-project
Note:
You can also not copy.
Depending on the first publish level and the data level of the remote and the current projects, some of the definitions of the variables with the same name might be lost. In this case, a message is given to indicate the level at which this might occur. 
Subsets, Actions, Flowcharts, and Tags of the remote version are copied to their equivalent level. Select either to copy the remote tags or not.
Case where remote-project has the same levels as to-project 
  • Each level of remote-version is copied to its equivalent level in to-version
  • Variables of remote-levels are copied to its equivalent to-level, considering the first publish level of to-version.
Example
:  If the first publish level of to-version is level 2, then remote-version level 1 variables are copied to level 1 of to-version and all the variables of remote-version of level2 and above will be copied to level 2 of to-version. Hence the variables with the same name in those levels of the remote-version are copied with their definition in the lowest level.
A variable warning is given in this case.
Case where remote-project has fewer levels than to-project
  • Data level of the remote-project is copied to the data level of to-project and the remote levels before the data level are copied to the levels before  the 
    to-project
    data level. Extra missing levels are created by default.
Example:
 If remote-project has 2 levels and to-project has 6 levels, then:
    • Remote-version level 2 which is the data level is copied to level 6 of to-version
    • Remote-version level 1 is copied to level 5 of to-version
    • Extra levels, level 1, level 2, level 3, and level 4 are created by default.
Note:
Generally the variables of each remote level are copied to its equivalent to-level by considering the first publish level of to-project. If necessary a variables Warning is given due to first publish level.
Case where remote-project has more levels than to-project
  • Data level of the remote-version is copied to the data level of to-version. The levels before the data level are then copied respectively until level 1 of to-version is populated.
Example:
 If remote-project has 6 levels and to-project has 2 levels then:
    • Remote-version level 6 which is a data level is copied to level 2 of to-version which is a data level
    • Remote-version level 5 is copied to level 1 of to-version
    • No action is taken for Levels 1, 2, 3 and 4 of remote-version
Note1:
The variables of remote-levels are copied to its equivalent to-level. considering. The first publish is taken into consideration and if necessary a Variables Warning is given due to first publish level.
The missing levels variables are either copied to to-version level or the level one of to-version according to user selection. Subsets, Actions, Tags, Flow Charts of the missing levels are not copied.
Copy Project
When copying a remote project, all the versions and hence the following items for each version are copied: 
Registered tables for each version:
  • Variables (optional)
  • Data pools
  • Actions
  • Subsets
  • Flowcharts
  • Test Matches
  • Default Publish Jobs (optional)
  • Transformation Maps (optional)
The following items are also copied:
  • Project Tags (optional – user is asked)
  • Project security groups (optional - user is asked)
In the Remote Projects window, select a project to copy to the current repository and click on the green arrow.  
Click the double arrow to view project properties. The level details are disabled and cannot be modified. However, the rest of the details can be modified for the new project. All the versions and details of the remote project are copied to the new project in the current repository.
Copy Branches of Project Tree
When copying a branch of the project tree, the following items will be copied for the levels and the data levels of the tree:
  • Variables (optional)
  • Data pools
  • Actions
  • Subsets
  • Flowcharts
  • Test Matches, are copied if the publish level of the current project is a Data level. Otherwise a warning message is given.
  • Default Publish Jobs (optional) 
Follow these steps in Remote Projects window:
  • Select the right level of a remote project (according to the selected level of the current project)
  • Click the green arrow to copy the branch under the selected level of the current project.
Considering that remote project data level are copied to the current project data level, to copy:
(Current project data level – Current project selected level) levels, 
Select the remote level as:
(Remote project data level - remote project selected level) – 1
Example
: If the current project and remote project both have three levels and if the current project selected level is 1, select level 2 of the remote project to copy level 2 and 3 of the remote project under the current level 1.
If the selected level name already exists, the application adds _1 or _2 and so on.
A confirmation to copy the variables is displayed.
If any tables used in a data group are not registered in the current version or their definition is different, a warning is given. The user is also prompted to select the tables to register.
Copy of Generic versions
When copying a project, all the versions and their details including Generic versions are copied.
The following functionalities are
not
applied for Generic versions:
  • Copy a Generic version (Although the Generic version is copied, not all Remote Copy functionality is available)
  • Copy Data belonging to a Generic version, or Copy Data to a data group belonging to a Generic version 
  • Copy a branch of the project tree belonging to a Generic version, or Copy a branch of a project tree to a Generic version 
  • Copy Transformation maps
The rest of the copy remote functionalities which can be applied to an ordinary version can be applied to a Generic version.
Copy of Default Publish Jobs
Default Publish Jobs are copied for the following actions:
  • Copy Projects
  • Copy Versions
  • Copy branches of a project tree
If a default publish job is using 
values for variables from a Data Pool
, the job is copied without the link for the 
values for variables from a Data Pool 
which could be added manually by user.
Also if the default publish job is 
Publish to Data Pool,
 the job is copied as 
Publish to file (CSV)
 instead of publishing to a Data Pool which can be modified manually.