|
Component family
|
Talend
MDM
|
|
|
Function
|
tMDMTriggerOutput receives an XML
flow (Document type) from its
preceding component.
Note
This component works alongside the new trigger service and
process plug-in in MDM version 5.0 and higher. The MDM Jobs,
triggers and processes developed in previous MDM versions remain
supported. However, we recommend using this component when
designing new MDM Jobs.
|
|
Purpose
|
This component receives an XML flow to set the MDM message so that
MDM retrieves this message at runtime. With this component, you do
not need to configure your Job any more in order to communicate the
data changes from MDM to your Job.
|
|
Basic settings
|
Property Type
|
Either Built-in or Repository.
Since version 5.6, both the Built-In mode and the Repository mode are
available in any of the Talend solutions.
|
|
|
|
Built-in: No property data stored
centrally.
tMDMTriggerOutput is expected to
use this option in order to apply the default read-only schema.
MDM_message is the only column
of this schema.
|
|
|
|
Repository: Select the repository
file where properties are stored. The fields that follow are
completed automatically using the fetched data.
As tMDMTriggerOutput provides a
fixed read-only schema, you are expected to use the Built-in option.
|
|
|
Schema and Edit
Schema
|
A schema is a row description, it defines the number of fields that will be processed
and passed on to the next component. The schema is either built-in
or remote in the Repository.
Since version 5.6, both the Built-In mode and the Repository mode are
available in any of the Talend solutions.
Click Edit schema to make changes to the schema. If the
current schema is of the Repository type, three options are
available:
-
View schema: choose this option to view the
schema only.
-
Change to built-in property: choose this option
to change the schema to Built-in for local
changes.
-
Update repository connection: choose this option to change
the schema stored in the repository and decide whether to propagate the changes to
all the Jobs upon completion. If you just want to propagate the changes to the
current Job, you can select No upon completion and
choose this schema metadata again in the [Repository
Content] window.
|
|
|
|
Built-in: The schema will be
created and stored for this component only. Related Topic: see
Talend Studio User
Guide.
This is the default option for tMDMTriggerOutput. With this option, the read-only
schema is used to deal with the XML-format MDM message.
|
|
|
|
Repository: The schema already
exists and is stored in the repository. You can reuse it in various
projects and jobs. Related Topic: see Talend Studio User Guide.
As tMDMTriggerOutput provides a
fixed read-only schema, you are expected to use the Built-in option.
|
|
Advanced settings
|
tStatCatcher Statistics
|
Select this check box to gather the processing metadata at the Job
level as well as at each component level.
|
|
Global Variables
|
ERROR_MESSAGE: the error message generated by the
component when an error occurs. This is an After variable and it returns a string. This
variable functions only if the Die on error check box is
cleared, if the component has this check box.
A Flow variable functions during the execution of a component while an After variable
functions after the execution of the component.
To fill up a field or expression with a variable, press Ctrl +
Space to access the variable list and choose the variable to use from it.
For further information about variables, see Talend Studio
User Guide.
|
|
Usage
|
Use this component as an end component. It needs an input
flow.
To send message to MDM, you need to deploy the Job using this
component on your MDM server and generate the corresponding trigger
and process to invoke this Job in MDM.
For further information about how to deploy a Job onto MDM server
and how to generate a trigger or a process, see
Talend Studio User Guide.
|
|
Limitation
|
During the deployment of this
component on the MDM server, you need to select the Hosted (Zip) type as the format of the
deployed Job. If you deploy it in the Distributed
(War) type, the relative Job cannot be invoked. For
further information about the available types, see
Talend Studio User Guide. |
