tLDAPOutput
definition. Then it passes on the field list to the next component via a Row > Main link.
tLDAPOutput Standard properties
These properties are used to configure tLDAPOutput running in the Standard Job framework.
The Standard
tLDAPOutput component belongs to the Databases family.
The component in this framework is available in all Talend
products.
Basic settings
Property type |
Either Built-in or |
 |
Built-in: No property data stored |
 |
Repository: Select the repository |
|
Click this icon to open a database connection wizard and store the For more information about setting up and storing database |
Use an existing connection |
Select this check box and in the Component List click the relevant connection component to Note that when a Job contains the parent Job and the child Job, |
Host |
LDAP Directory server IP address. |
Port |
Listening port number of server. |
Base DN |
Path to user’s authorized tree leaf. |
Protocol |
Select the protocol type on the list. LDAP : no encryption is used
LDAPS: secured LDAP. When this
TLS: certificate is used When this |
User and Password |
Fill in the User and Password as required by the Note that the login must match the LDAP syntax requirement to be To enter the password, click the […] button next to the |
Multi valued field separator |
Type in the value separator in multi-value fields. |
Alias dereferencing |
Select the option on the list. Never improves search performance if you are sure
Always: Always dereference
Never: Never dereferences
Searching:Dereferences aliases only
Finding: Dereferences aliases only |
Referral handling |
Select the option on the list:
Ignore: does not handle request
Follow:does handle request |
Insert mode |
Select the editing mode on the list:
Add: add a value in a multi-value Insert: insert new data,
Update: updates the existing
Delete: remove the selected data Insert or update: Insert a new record. If Warning:
When Update is selected, you |
DN Column Name |
Select in the list the type of the LDAP input entity used. |
Schema and Edit |
A schema is a row description. It defines the number of fields |
 |
Built-In: You create and store the schema locally for this component |
 |
Repository: You have already created the schema and stored it in the When the schema to be reused has default values that are You can find more details about how to |
 |
Click Edit
|
Die on error |
This check box is selected by default. Clear the check box to skip |
Advanced settings
Use Attribute Options (for update mode) |
Select this check box to choose the desired attribute (including |
tStatCatcher Statistics |
Select this check box to gather the job processing metadata at a |
Global Variables
Global Variables |
NB_LINE: the number of rows processed. This is an After
NB_LINE_REJECTED: the number of rows rejected. This is an
ERROR_MESSAGE: the error message generated by the A Flow variable functions during the execution of a component while an After variable To fill up a field or expression with a variable, press Ctrl + For further information about variables, see |
Usage
Usage rule |
This component covers all possible LDAP queries. Note: Press Ctrl + Space bar to |
Editing data in a LDAP directory
All of the database output components have the Parallelize option in their Advanced
settings tab. This option allows you to improve data processing
performances by handling several data flows simultaneously. For more information, see
Talend Studio User Guide.
The following scenario describes a Job that reads an LDAP directory, updates
the email of a selected entry and displays the output before writing the LDAP directory. To
keep it simple, no alias dereferencing nor referral handling is performed. This scenario is
based on Displaying LDAP directory’s filtered content. The result returned was a single entry, related to an organisational person, whom email
is to be updated.
The output shows the following fields: dn, uid and mail as defined in the Job.
Dropping the components
-
Drop the tLDAPInput, tLDAPOutput, tMap and tLogRow components
from the Palette to the design
workspace. -
Link tLDAPInput to tMap using the Row >
Main connection. -
Link tMap to tLogRow using the Row >
Main connection. -
Link tLogRow to tLDAPOutput using the Row >
Main connection.
Configuring the components
-
In the tLDAPInput
Component view, set the connection details
to the LDAP directory server as well as the filter as described in Displaying LDAP directory’s filtered content.Change the schema to make it simpler, by removing the unused fields:
dc, ou,
objectclass. -
Then open the mapper to set the edit to be carried out.
Drag & drop the uid column from the input table to the output as no
change is required on this column. -
In the Expression field of the
dn column (output), fill in with the exact
expression expected by the LDAP server to reach the target tree leaf and
allow directory writing only if you haven’t set it already in
the Base DN field of the tLDAPOutput component. -
In this use case, the GetResultName
global variable is used to retrieve this path automatically. Press Ctrl+Space bar to access the variable list and
selecttLDAPInput_1_RESULT_NAME
. -
In the mail column’s expression field, type in the
new email that will overwrite the current data in the LDAP directory. In
this example, we change to
Pierre.Dupont@talend.com.Click OK to validate the changes. -
Then select the tLDAPOutput component to
set the directory writing properties. - Set the Port and Host details manually if they aren’t stored in the Repository.
-
In Base DN field, set the highest tree
leaf you have the rights to access. If you have not set previously the exact
and full path of the target DN you want to access, then fill in it here. In
this use case, the full DN is provided by the dn output
from the tMap component, therefore only the
highest accessible leaf is given:
o=directoryRoot. -
Select the relevant protocol to be used: LDAP for this example.
Fill in the User and Password as expected by the LDAP
directory.Fill in Multi-valued field separator with
a comma as some fields may hold more than one value, separated by a comma. -
Use the default setting of Alias
Dereferencing and Referral
Handling fields, respectively Always and Ignore.The Insert mode for this use case is
Update (the email address).The schema was provided by the previous component through the propagation
operation. -
In the Advanced settings view, select the
Use Attribute Options (for update mode)
check box to show the Attribute Options
table.Select the attribute mail under the
Attribute Name part and the choose
Replace under the Option part.
Executing the Job
- Press Ctrl+S to save the Job.
-
Press F6 to run the Job.