Extractions of a job
Admin | 
application database > ETL > Jobs > Extractions link
Note: if the job is locked, the extractions window will be read only
Purpose of the page¶
This window allows you to detect and define certain necessary information to include the execution of the active extraction tasks belonging to the defined job routines.
IMPORTANT: the window does not allow new records to be inserted manually. To register and edit the extraction tasks, you must run the Update extractions utility present in the window’s actions menu. The utility will automatically insert as many records as there are active extraction tasks for that routine, for every routine of the active job. However, you can delete records if, for that particular job, you do not want to run certain extraction tasks that are active by default in the job routine, and have been automatically inserted into the window by the Update extractions utility.
Attributes tab
Note: in the job execution step, you can define or edit the attributes set in this window only in relation to that specific execution.
| Field | Description |
|---|---|
| Sorting | indicates the order of the routine within the job. Note: the values of the Sorting field are unique and different from 0. |
| ETL domain | indicates the ETL domain to which the extraction task belongs |
| Routine | indicates the routine to which the extraction task belongs. |
| Extraction task description | - indicates the description of the extraction task. |
| Data Source | - indicates the data source defined for the extraction task. |
| Data source type | allows you to select the input type from those configured in the extraction task’s data source. |
| Extraction type | allows you to select the extraction type from among the following: - Application server: loading is carried out either from queries or from files present on directories visible by the application server indicated in the Permitted dictionaries; - Client: loading is carried out via the uploading of files by the client; - Endpoint/Tagetik Data Loader: loading is carried out using an Endpoint that also allows you to use the Tagetik Data Loader. Note: If the type of external source from which to extract the data is a database, the Application server and Client options will be the same and tell the system that the query must be run on the database configured in the data source. |
| Endpoint/Tagetik Data Loader | allows you to select an endpoint that will be used if the Extraction type is Endpoint/Tagetik Data Loader; |
| Directory | allows you to define a directory that will be used if the Data source type is from file and the Extraction type is not Client; |
| File names | allows you to list the names of the files, separated by a comma (comma separated). which will be used when the Data source type is from file and the Extraction type is not from Client. Note: If it is necessary to indicate several files of the same type, just separate the various names by a semicolon. In addition to indicating several files, you can also use the wildcard “*” to extract only files that respect the indicated filter. When the input File names includes a wildcard (*), the file name must be enclosed in square brackets [ ]. For example, you can write: - [*.fbk] to indicate all files that end with the extension “.fbk”; - [name*] to indicate all files that start with “name”; - [name*.fbk] to indicate all files that start with “name” and end with the extension ".fbk"; - [name{PARAM_AZIENDA}*] to indicate all files that start with “name” + entity parameter value. The file name can also be defined using SQL strings by utilising the parameters defined in the ETL syntax If no file name is specified, the system will extract the data of all files of the type related to the value of the Data source type field that exist in the specified directory. |
| File management type | Only for loaded files whoseData source type is from file and Extraction type is not from Client. Allows you to select from the following options: - None: no action will be run on the file - Delete: the file will be deleted if loading is completed successfully - Archive: the file will be moved to an “archive” file if loading is completed successfully. |
| File ID | Only for loaded files whoseData source type is from file and Extraction type is from Client. This indicates the ID of the file to be loaded via upload, to classify the extraction tasks with the same data source (in order to limit the number of uploads of files containing data to extract). Note: if the same File ID is attributed to two or more tasks, the system will load a single file, thus preventing it from requesting the uploading of superfluous files that have already been loaded. |