
CHAPTER 9 TASKBUILDER COMPONENTS 99
to log into the database. e username must have the appropriate rights for all the
tables that the task will access—SELECT rights for tables in source databases, SELECT/
UPDATE/INSERT rights for tables in destination databases (see Appendix B). Tasks
will fail without proper access rights.
Password (Value—Password) – e Password property is used in conjunction with
the User Name property to log into the database. Passwords are case sensitive, and an
incorrect password will cause the task to fail. e password value is displayed in a hid-
den “*****” format and is encrypted for security when stored in the database.
Data
e Data component represents an abstract set of data within the memory of Translator.
e Data component is usually not intended as a task start or endpoint since the data’s
existence in memory is only temporary; it is mainly used as a midpoint between dierent
components going to or from a database or XML le. e Data component is a halfway step
between data formats that don’t have a direct conversion (i.e. Database-to-XML).
Figure 9.2 – Data Component
e Data component has no properties of its own.
XML
e XML component represents a complete XML le in the Translator le system or in
another remotely accessible machine.
Figure 9.3 – XML Component
e XML component has the following properties:
File Name (Value—Filename) – e File Name component allows you to enter a name
for the XML le. You can also use a placeholder for the le name (see the File Name
Placeholders section in this chapter). In tasks where the XML le is the destination of
an action, the XML le with the given le name will be created if it doesn’t already exist,
or updated if it does exist. Tasks that start with an XML component will fail if the given
Kommentare zu diesen Handbüchern