erwin Data Transformation 9.2.6 - User Guide

Operation “GET”

Operation “GET”

When the field “Operation” is set to “GET”, then the Operation Parameter section shows options for the file adapter execution. The first option is related to the protocol (NFS or FTP)

NFS Protocol

If the protocol is set to NFS, then the Operation Parameter section shows the following parameters:

•Type (CSV, Sheet, XML, MS Project, DM) – file type the adapter will manage

•Target (remote) Directory that will be used at adapter execution time to get files from; this may be anywhere in the Windows network file system, provided that it is accessible and readable by the Windows user (“local system account”) performing batch operations.

•Filters – used to include more than one file in the adapter operation (using “*” as a wildcard for the beginning, in the middle, or at the end of file name). If filter is set as a single “*”, then the entire folder content will be used by the adapter during execution.

FTP Protocol

If the protocol is set as FTP then the Operation Parameter section shows the following parameters:

•Type (CSV, Sheet, XML, MS Project, DM) – type of file the adapter will manage

•FTP Server Directory that will be used at adapter execution time; this may be anywhere in the network file system, provided that it is accessible and readable by the adapter specified in the FTP account (see below)

•Filters – used to include more than one file in the adapter operation (using “*” as a wildcard for the beginning, in the middle, or at the end of file name). If filter is set as a single “*”, then the entire folder content will be used by the adapter during execution.

Moreover, the user has to define the Connection and Proxy sections with the parameters needed to access the FTP server.

All the parameters in the Connection section are mandatory, including the FTP account to be used to access the specified directory; if a proxy is used then the user must complete the Proxy section parameters.

Operation “PUT”

Operation “PUT”

When the field “Operation” is set to “PUT”, then the Operation Parameter section shows options for the file adapter execution. The first option is related to the protocol (NFS or FTP)

NFS Protocol

If the protocol is set to NFS, then the Operation Parameter section shows the following parameters:

•Target (remote) Directory that will be used at adapter execution time, to drop files coming out from workflows using it as operation target; this may be anywhere in the Windows network file system, provided that it is accessible and writable by the Windows user (“local system account”) performing batch operations.

FTP Protocol

If the protocol is set to FTP, then the Operation Parameter section shows the following parameters:

•FTP Server Directory that will be used at adapter execution time, to drop files coming out from workflows using it as operation target, provided that it is accessible and writable by the adapter specified FTP account (see below)

Moreover, the user has to define the Connection and Proxy sections with the parameters needed to access the FTP server.

All the parameters in the Connection section are mandatory, including the FTP account to be used to access the specified directory; only if you have a proxy you must complete the Proxy section parameters.

To save the new File Adapter just created, press the  button.  The adapter will be saved and added to the File Adapter List at the top of the window.

To cancel the adapter data just entered and to reset the window, press the  button.

To delete an existing adapter, just select it and press the  button. It will be permanently removed from the File Adapter List (all the items linked to the file adapter are removed: job, workflow using it as source).

The  button closes the window.

Transformation Library Configuration

Transformation Library Configuration

In the Transformation Library there are some pre-built parsers (based onto XSLT) to apply transformations to the data managed through the workflow (see after):

•Data cleanse (like Data Type Check,Not Allowed Text Check)

•Data format (like Format Date - Format Number - Capital/Small letter - Suffix/Prefix - Replace Text)

•Data structure change (like Combine Field - Split Field - Add Fixed value field)

•Data filter (like Fixed values, Interval Value)

•Data Derivation (like Sum values in rows/columns, counting values in rows/columns, Match keys and pick values)

These kinds of XSLT files can’t be modified or deleted by the user.

The top field of the window shows the contents of the XSLT library, with a short description and the relative XSL file.

Selecting an activity from the list automatically completes the Library Parameters fields with the parameters of the library.

Optionally, it’s also possible here to define custom XSLT library elements to be used in the workflow configuration for input or output data formatting (see later). The custom parsers must have been developed in advance, with a proper XML/XSLT editor.

To add a new custom XSLT to the library, press the  button; once the name and description are provided, the browse button pops up a new window allowing the user to select an .XSLT file from the file system. The selected file will be copied into the subfolder “library\Custom Transformation” of your DT data installation folder.

A custom transformation could be alternatively defined as:

•CC compliant – output is XML, compliant with the CC internal XML schema

•CC uncompliant – output is XML, with a different schema, or HTML, or TXT, or MS Excel

•CM compliant – output is XML, compliant with CM operation schema (only to be used to load in CM models multiple intersection object type at once)

It’s possible to have a preview of the CC internal Schema / CM operation Schema pressing the  button, with the appropriate dropdown type selection:

The  button saves the XSL library once created or modified by the user.

The  button deletes the XSL library that user selected from the list.

The  button resets all the fields just edited by the user.

The  button closes the window.

Configurations

Configurations