erwin Data Transformation 9.2.5 - User Guide

Web Service POST

Web Service POST

Choose the Web Service POST  Adapter in the “Choose Adapter” drop-down list (only the Web Service “POST” Adapters will be available in the list)

As a result of this choice, data coming from the source adapter will be transformed as defined in “Transformation” step and sent to the Web Service, as defined in its configuration.

Evolve Site Import

Evolve Site Import

In order to copy Evolve sites from model to model, you should consider that:

•A target site has to be created before executing the operation

•Only the following components are copied from source model to target model: Menu, Index Pages, Object Pages, Diagram Popouts, Diagram Designer Layouts

•If you want to manage Diagram Designer Layouts you should enable target model with Diagram Designer

•If any objects is already defined in the target site it will be overwritten

•It is recommended that all the pages linked to source Evolve site, should not be associated to other Evolve sites

The following instructions have to be followed in order to copy an Evolve Site. It is recommended to back up your target model before the operation, as a bad configuration may result in a loss of information.

          1. Create a new workflow configuration on your target model configuration

          2. Select as source EA Adapter and select the export adapter related to your source model

          3. Select CW Site as object type and filter only Name and Description properties

          4. Add a second source EA Adapter and select the export adapter related to your source model: select CW View as object type and filter the following properties/associations:

a. Name

b. App Type

c. Business Description

d. Category

e. Description

f. Display Name

g. Hash Code

h. Root Object Type

i. CW Site (belongs to (index))

j. CW Site (belongs to (single))

k. CW Site (belongs to (diagram pop out))

          5. (Optionally, only if you want to copy Diagram Designer Layouts) Add a third source EA Adapter, select the export adapter related to your source model and filter the following properties:

a. Name

b. Automatic Diagram

c. Category

d. Description

e. Enabled Version

f. Root Object Type

          6. Add a Fixed Value Manager transformation on the following columns:

*: use semicolon in value cell as specified

          7. Add a Replace Text transformation on the following columns:

          8. Choose the operation Evolve Site Import that will automatically map all needed fields

Email Configurations

Email Configurations

The email notification allows the user to be easily aware of what’s going on with DT operations, particularly for the owners of model information managed by the tool.

Notification email for the workflow operation results can be configured with a custom setting for recipients, CC recipients, email subject and message text.

The workflow output, in HTML format, will be attached to email. If it is not needed – for example, the workflow is configured to produce a file that will be also attached to email – the option “Attach workflow output file” should be deselected:

another option is provided to send email always (per default), only with data, or only on errors:

Some parameters can be used in subject or message text:

•<%SYSDATE%>,<%SYSDATE_EUR%>,<%SYSDATE_USA%>,<%SYSDATE_UTC%>: replaced at execution time with date time, using requested format.

•<%OPERATION_FOLDER%>: replaced at execution time workflow operation folder path.

•<%WORKFLOW_FOLDER%>: replaced at execution time workflow folder path.

The email can contain links to specified URL: just use “Add URL” button to have a sample link text and replace your own site address and name:

The resulting email looks like this:

It is possible to use the option “Single email for record” to send a notification for each input dataset record.

Users may put parameters in the email configuration using column name to give specific information regarding the recipient: to be recognized by DT as a parameter, a column name must be enclosed between a prefix “<%” and a suffix “%>”.

For instance if the first dataset of a workflow has a column named “1 AM email”, containing the application manager email related to the column “1 Application name”, a proper email recipient could be configured in the email as <%1 AM email %> and the subject of the message could be:

“Application <%1 Application name%> has been updated in EA model”

This setting, when the “Single email for record” option is selected, produces a single notification per source dataset record, replacing parameters with their value as read from the input.

Workflow Test

Workflow Test

Once configured, the workflow can be tested using the button “Test”, even if is not yet active.

When tested, a progress bar will make the user aware of the major workflow steps:

1. Adapter execution

2. Source data normalization – to provide transformation input data

3. Transformation execution

4. Workflow output normalization – to provide data for operation

As soon as the step is performed and corresponding data is produced, a specific button makes it available to the user.

Once data for operation have been produced, user may choose to actually execute operation or not, after checking the operation data.

The user is then informed about the result of the operation execution, if requested.