erwin DT - User Guide
Getting Started
Getting Started
Tool Overview
Tool Overview
DT is aimed at configuring multiple, dynamic data flows, and managing those flows without relying on programming resources, with an easy to use interface to organize them in logically consistent job sequences, to be run on schedule/on demand:
Extract and transform raw data from third party tools in order to create and update data into erwin CW Exchange repository or into erwin EA Agile workspaces
Extract data from erwin CW Exchange repository or from erwin EA Agile workspaces in order to update third party tools.
Configure operation to run on a schedule: after the initial configuration and test, the data flows can run automatically with no need for the user to intervene.
From now on, “model” refers to data logically organized either into CW Exchange repository or into erwin EA Agile workspaces.
DT can therefore be classified as a tool that enables users to:
Maintain model data aligned with external sources
oGet raw data from external data source via adapters
oTransform data using XLST Transformation library
oMap data to the model objects and load into the model
Export and publish model data
oUnload data from the model, using custom filters
oTransform data using XLST Transformation library
oUpload external databases, post data to cloud systems or send files to external folder data to destination
Manage operations
oBack up data
oSchedule the data flows to be executed
oReview audit logs
oConfigure email notification alerts
DT offers a number of ready-to-use standard adapters that cover a wide number of integration needs. This enables the application of a standard approach to integration requirements.
To ensure safe data operations, all updating activities are performed using standard APIs, and are preceded by data mapping and consistency checks. A user operation log, e-mail notification, scheduled operation log and system log are also provided (sever errors are notified via e-mail to system administrator).
DT stores all the necessary settings (environment parameters, access control and profiling, job scheduling, workflows, adapter parameters and rules for file handling) in an embedded database (users do not need to interact with this database directly, a tool administrator may do).
User may interact with the tool during workflow testing activities, checking data previews and if necessary, discarding the updates.
Licensing
Licensing
If no valid license is found on the system, the user is required to provide a license key when DT starts.
For offline licensing, a request code must be generated. This window should not be closed until the product activation is complete, as a new request would otherwise need to be generated.
This code should be sent to erwin support, who will in turn provide an activation code specific to the request. This code should be used to activate the product. The activation code used must be specific to the request code provided to support; generating a new request code would necessitate a new activation code.
