ETL Version Selection

About ETL Versions

ETL Versions provide multiple Milestone versions of ETL packages that are operating against the same target objects so that the user may continue to make changes to the DEV Milestone version of DEV environment for a future mock while running a different Milestone Version of a different environment that is locked in place. The version is combined with use of Reporting Environments to separate the ETL Job Tasks by Milestone. If changes are made to add new rules, or remove tasks within the DEV Milestone, the other Milestones are not affected. It is only when the DEV Milestone is copied to one of the other Milestones that the ETL Rules will all be the same.

The benefit of ETL Version Selection is that once a Milestone has completed, the list of Job Tasks run with durations, counts of records, and timing is available for review. This data is all stored in a Migration table identified by the Version ID. Also, the user may continue to run the ETL Job list against the DEV Milestone during a Milestone (for example, Mock1 and Integration Test) and test changes without affecting the work of the Milestone. This process allows for segregation of the information for the Developer.

Refer to Working in Multiple Execution Environments for more information on how to plan for setting up multiple execution environments (created as Milestone versions) and how data moves through environments using the same production code in Migrate.

Prerequisites to using ETL Versions

Project Setup at Milestone level

Within the Project Setup of the Release, each Milestone is required to select a Reporting Environment. As the image below shows, each Milestone is assigned to an Environment (Reporting Environment). In this project, there are two Reporting Environments DEV and LOAD. Refer to section Administer > Setup > Environments for details of the setup and use of Environments.

Promote Object Data from DEV Environment to LOAD Environment

The Dataset tables and views must be copied into the other Environments in order for the process to work successfully. Refer to section Migrate > Working DB Object Promotion for details of the database copy process.

Setting the Version for an ETL Job

The Version info appears on the ETL Job Tasks page as a header. It shows the current milestone version and the active environment. The DEV-DEV version is the base version used for development in the DEV environment. The user should setup a Milestone named for this DEV version so that they can develop and run the ETL in that version during a Milestone. Each Milestone other than the DEV Milestone should be assigned to the LOAD Environment. In this way, the Milestone ETL Job and updates will be separate from the Development ETL Job and updates.

The DEV version is the default version where all work is completed. Copies of the remaining Milestones may be initiated through the Version Selection window. At this point the user may select another version by clicking the Version list, or they may create a new version (by copying from the DEV version to a new Milestone version.

The Version list on this dialog box will contain an option for DEV, and items for all of the Release's Milestones.

If a Version has not yet been created for the selected Milestone, the user will need to create a copy before they're able to switch to view the version.

The copy feature of this process will complete the following:

• If any component of DEV package is created, the entire DEV package will now be created.

• If a Version has already been created for the selected Milestone, the user will be able to Switch to the Version, or re-copy from Dev (which will overwrite).

  

  

To Select the version - Click on the Switch To This Version button

To Copy and Renew - Click on the Copy DEV to Mock1 button to initiate the copy process. The copy process allows you to select the required ETL types to copy to the next Environment. This process keeps the version tasks aligned.

The result will display the new version selected for the ETL Job Tasks as shown below:

When Job Tasks are viewed for the Source Transform, the Milestone name is added to each of the tasks and the Target and Datasource values reflect the Milestone's Reporting Environment working datasource (in this case, WRKFOO2BARL for INT1).

ETL Version Selection within Data Mapping Details

Within the Target Source Mapping details, each ETL Task setup for the field mapping will provide the version copies. Select a field mapping and then click on the ETL Tasks button to view ETL Tasks built for each Milestone. These all are built from the Copy feature from DEV to the Milestone.

As shown below, this Rule is part of a migration that currently has a DEV and Integration Test Version. Both versions of the same rule are displayed one additional version is created for the object.

ETL Version Selection as Part of the ETL Job List

Access Migrate > ETL Jobs and the version as part of the list of jobs running in ETL.