Workspace Send Connector
Workspace Send Connector
The Workspace Send Connector performs the singular task of transporting CData Arc messages across different workspaces.
The Workspace Send Connector ensures that message metadata persists as messages are passed from one workspace to another. Since Arc uses message metadata to track files through the flow, this helps ensure that files are logged, monitored, and processed correctly.
This connector has very simple configuration, as each Workspace Send Connector is paired with exactly one Workspace Receive Connector. Primary configuration is simply a matter of setting the appropriate Workspace and the name of the Workspace Receive Connector within that Workspace.
This section contains all of the configurable connector properties.
Settings related to the basic operation of the connector.
- Connector Id The static name of the connector. All connector-specific files are contained in a folder by the same name within the Data Directory.
- Connector Description An optional field to provide free-form description of the connector and its role in the flow.
Settings related to the Workspace destination where files will end up.
- Workspace Id The Workspace to send messages to.
- Connector Id The name of the Workspace Receive Connector within the target workspace where files should end up.
Settings related to storing copies of processed messages.
- Save to Sent folder Whether a copy of processed files should end up in the Sent folder.
- Send Folder Scheme Sent files are grouped together based on when they are processed (files processed in a similar time period are grouped together). This setting determines how long the grouping period is.
Settings that govern the creation and storage of logs.
- Log Level Specifies the type of information to log in the connector’s
- None - Does not create any logs.
- Error - Creates logs only when the connector encounters an error.
- Warning - Creates logs only when the connector issues a warning.
- Info - Logs general information about the workflow, including any errors and warnings (if applicable).
- Debug - Logs detailed debugging information for both successful and failed workflows.
- Trace - Logs detailed trace information for both successful and failed workflows.
Note: The Debug and Trace levels might log sensitive information, including message contents and SSL certificates. Although connection properties (such as passwords) are masked, you should review logs of this level for sensitive information before sharing them outside of your organization.
- Log Subfolder Scheme Instructs the connector to group files in the
Logsfolder according to the selected interval. For example, the Weekly option instructs the connector to create a new subfolder each week and store all logs for the week in that folder. The blank setting tells the connector to save all logs directly in the
Logsfolder. For connectors that process many transactions, using subfolders can help keep logs organized and improve performance.
- Log Messages A toggle that instructs the connector to save a copy of the most recent message in the
Logsdirectory. Note that the connector only keeps one message per subfolder, and the connector overrides the previously-saved message when it runs again.
Settings related to the automatic processing of files by the connector.
- Send Whether files arriving at the connector will automatically be sent to the external destination.
Settings related to the allocation of resources to the connector.
- Max Workers The maximum number of worker threads that are consumed from the threadpool to process files on this connector. If set, this overrides the default setting on the Profiles page.
- Max Files The maximum number of files that are processed by the connector each time worker threads are assigned to the connector. If set, this overrides the default setting on the Profiles page.
Miscellaneous settings are for specific use cases.
- Other Settings Enables you to configure hidden connector settings in a semicolon-separated list (for example,
setting1=value1;setting2=value2). Normal connector use cases and functionality should not require the use of these settings.