Along with event notification and business object request
processing, the JText connector provides the following
capabilities:
- Varied configurations for different business objects; for
example, you can configure different business objects to use
different directories and file extensions, or different data
formats.
- Configuration capabilities for file extensions, directory
location for archive file storage, format type, and file
sequencing.
- Configuration capabilities for dynamically determining the
output filename for each business object, or for returning the full
name of a generated output file.
- Failure recovery.
- Custom data handler capabilities, which means that you can
create your own data handler without recompiling the connector
code. You need only change the configuration properties to use the
new class you have created.
- The ability to exchange data with remote FTP locations as well
as local file system directories.
For more information, see Installing and configuring the JText
adapter, Using JText
connector meta-objects, and the Data Handler
Guide.
While the JText connector enables the transfer of data from a
source application to a destination application like other
adapters, it is unique in the following ways:
- It processes all business objects in the same way. In other
words, because it always writes the business object to a file, it
performs only Create operations (regardless of the
incoming verb).
- It does not interpret the contents of the business objects that
it handles. In other words, it reads each business object as a
potential string or byte array in which key values have no more
significance than other data.
- It uses meta-object values for much of its configuration. For
more information, see Using JText
connector meta-objects.
- It does not have an event table. Instead, it treats the
configured event directory as an event table.
