TIBCO Scribe® Online Text File As Target
TIBCO Cloud™ Integration - Connect allows you to create a target Connection to one or more text files. Target Connections can be made to text files in Local Directories, and on the following servers: FTP (unencrypted), FTPS (encrypted using SSL), SFTP (SSH File Transfer Protocol), Dropbox, OneDrive, and OneDrive Business. You can then use the Text File as Target Connection to integrate data from a datastore such as Microsoft Dynamics CRM or Salesforce to a text or csv file.
Target connections can also be made to Binary Content and Text Content files. These files are read for validation and the contents are copied to new files in another directory.
Source and target text Connections must be configured separately. See TIBCO Scribe® Online Text File As Source.
Setup Overview
- Install the Text File as Target Connector from the Marketplace. See Marketplace Connectors.
- You have two options when using the Text File as Target Connector.
- Enter the entity and field names when configuring the Connection to generate a text file with a header row automatically when a flow using this Connection is run.
- Create target text files ahead of time to be used as the framework for the inbound data. These can be created manually or by exporting data from an existing database. Tip: The easiest way to create the framework for your Target Connection may be to save a copy of your source data as a text or csv file. Delete any data from the file, but keep the field names in the header row intact.
Text files are the equivalent of tables in a database or entities in TIBCO Cloud™ Integration - Connect. See Source Or Target Text File Requirements.
- On the Text File as Target Connection dialog, configure the tabs in order as they are displayed. See Configuring Text File As Target Connection for configuration steps.
- On the Location tab of the Connection dialog, specify the physical location where the target text files are stored. For any given location, specify the directory that contains the text files. That directory represents the database or container that holds the text files or database tables. There are several location types supported, each with a different set of required parameters. See Target Text Connection — Location Tab for details on each location type.
- If you choose to store text files on your own computer, you must edit the FoldersAccess.txt file. When text files are stored locally, TIBCO Cloud™ Integration - Connect uses the FolderAccess.txt file to maintain the list of directories it is permitted to access when connecting to text files. The TIBCO Cloud™ Integration - Connect Text File as Target Connector is limited to the directories in this list. Add directories to the default list as needed. See Providing Access To Local Text Files.
- Each text file represents an entity or database table. In the Entities tab on the Connection dialog, create a descriptive name for each entity to be accessed by this Connection.
- For each Entity you add, use the right panel of the Entities tab on the Connection dialog to configure associated properties. Properties include: file format information for parsing the text file, associated text file name, and post processing instructions for that file. See Target Text Connection — Entities Tab.
- Within an entity or text file, there are lists of field names and associated data. For each field contained within a text file, use the Fields tab on the Connections dialog to verify or modify the field name, data type, and the width of each field read from the header row in the text file. If the file does not have a header row, and you choose to use an existing text file, field names display as Field 1, Field 2, etc. See Target Text Connection — Fields Tab.
- When the Text Connector as Target is configured, select the Test button to make sure TIBCO Cloud™ Integration - Connect is communicating with the selected text files. See Testing Connections.
Connector Specifications
| Supported | |
|---|---|
|
Agent Types |
|
| Connect on-premise | X |
| Connect cloud | X |
|
Data Replication Apps |
|
| Source | |
| Target | |
|
On Schedule Apps |
|
| Source | X |
| Target | X |
|
On Event Apps |
|
| Source | X |
| Target | X |
|
Flows |
|
| Integration | X |
| Request-Reply | X |
| Message | |
Selecting An Agent Type For Text as Target
Refer to TIBCO Cloud™ Integration - Connect Agents for information on available agent types and how to select the best agent for your app.
Text Connector As An App Target
Consider the following when using the Text Connector as an app target.
Comment Rows
Any row of data that begins with a hash (#) is considered a comment and ignored.
Features Not Supported
The following features are not available for flows that use a Text File as Target Connection:
- Net Change based on Most Recent Record Processed date.
- Reset Metadata — Metadata parameters are contained within the Connection configuration and must be reset there. Resetting metadata is required when fields names have changed in the header row of the source text file. See Resetting Metadata for Text Connections. Note: If you do not have a pre-existing target text file and you reset metadata, any fields you have manually configured are deleted.
- Debugging flows is not available when storing data in FTP locations including FTPS and SFTP.
- Append to existing file is not a valid processing option for Dropbox locations.
TIBCO Cloud™ Integration - Connect API Considerations
The TIBCO Cloud™ Integration - Connect API does not support creating Text File as Target Connections.
License Agreement
The TIBCO End User License Agreement for the Text as a Target Connector describes TIBCO and your legal obligations and requirements. TIBCO suggests that you read the End User License Agreement.
Additional Information
TIBCO Scribe® Online Text File As Source