Scenario 2: Deleting data from a defined table in a MicrosoftAX server - 6.1

Talend Components Reference Guide

EnrichVersion
6.1
EnrichProdName
Talend Big Data
Talend Big Data Platform
Talend Data Fabric
Talend Data Integration
Talend Data Management Platform
Talend Data Services Platform
Talend ESB
Talend MDM Platform
Talend Open Studio for Big Data
Talend Open Studio for Data Integration
Talend Open Studio for Data Quality
Talend Open Studio for ESB
Talend Open Studio for MDM
Talend Real-Time Big Data Platform
task
Data Governance
Data Quality and Preparation
Design and Development
EnrichPlatform
Talend Studio

Warning

Before being able to use this component, make sure that you install and launch the MicrosoftAX server correctly.

This Java scenario describes a two-component Job that uses tMSAXOutput to delete from a defined table in a MicrosoftAX server all rows that do not match the data included in a key column.

In this example, the input schema we use is an address column that holds the following data: New York-Midtown Manhattan. We want to delete from the MicrosoftAX server all addresses that are not identical with this one.

Setting up the Job

  1. Drop tFixedFlowInput and tMSAXOutput from the Palette to the design workspace.

  2. Connect the two components together using a Row > Main connection.

Configuring tFixedFlowInput

  1. Double-click tFixedFlowInput to display its Basic settings view and define the component properties.

  2. Set Schema type to Built-in and click the three-dot button next to Edit schema to display a dialog box where you can define the input schema.

  3. Click the plus button and add the input schema columns, address in this example.

  4. Click OK to close the dialog box. The schema column displays automatically in the Values list.

  5. Click in the Value column and enter a value for the input column.

Setting up the connection to the MicrosoftAX server

  1. Double-click tMSAXOutput to open its Basic settings view and define the component properties.

  2. Set Property type to Built-in.

  3. In the Host field, type in the IP address of the MicrosoftAX server.

  4. In the Domain field, type in the domain name on which the MicrosoftAX server is hosted.

  5. Enter your username and password for the server in the corresponding fields.

  6. In the Table Name field, enter the name of the table you want to delete data from, ADDRESS in this example.

Defining the action on data

  1. In the Action on data list, select the action you want to carry on, Delete in this example.

  2. Click Sync columns to retrieve the schema from the preceding component. In this example, we want to retrieve the input column: address.

  3. Click the three-dot button next to Edit Schema to open a dialog box where you can verify the retrieved schema.

  4. In the output schema, select the Key check box next to the column name you want to define as a key column, and then click OK to validate your changes and close the dialog box.

    Note

    When you select Delete as an action on data, you must always define the Reference column as a key column in order for tMSAXOutput to delete rows based on this key column.

  5. In the Additional columns list, click the plus button to add one line and define the parameters the component will use as basis for the delete operation.

  6. Set a name, an operator, a data type, a local expression, a position and a reference column in the corresponding columns for the line you added.

    In this example, we want to delete from the ADDRESS table in the MicrosoftAX server all rows in which the address column is not equal to the address in the key address column and that reads as the following: New York-Midtown Manhattan.

    Note

    When you select Delete as an action on data, you must always set Position to Replace. Otherwise, all settings in the Additional columns will not be taken into account when executing your Job.

Job execution

  • Save your Job and press F6 to execute it.

    tMSAXOutput deletes from the ADDRESS table in the MicrosoftAX server all rows where the address string is not equal to the address in the key column.