XSLT Connector

The XSLT connector provides support for Extensible Stylesheet Transformation (XSLT 1.0) transforms.

Key Capabilities

XSLT 1.0 transformation support for converting XML documents based on stylesheet templates
Document function and embedded script support for advanced transformations

Overview

After an XSLT file has been uploaded to the connector, XML files arriving at the connector are automatically converted based on the XSLT definition.

Connector Configuration

This section contains all of the configurable connector properties.

Settings Tab

Connector Settings

Settings related to the core operation of the connector.

Setting	Description
Connector Id	The static, unique identifier for the connector.
Connector Type	Displays the connector name and a description of what it does.
Connector Description	An optional field to provide a free-form description of the connector and its role in the flow.
XSL Template File	The XSLT file that defines the XML transformation to be performed by the connector.

Other Settings

Settings not included in the previous categories. Only visible if you use the .NET edition.

Setting	Description
Document Function	Check this to allow use of the `document()` function while processing XSLT.
Embedded Scripts	Check this to allow use of embedded scripts while processing XSLT.

Advanced Tab

Advanced Settings

Setting	Description
Local File Scheme	A scheme for assigning filenames to messages that are output by the connector. You can use macros in your filenames dynamically to include information such as identifiers and timestamps. For more information, see Macros.
Processing Delay	The amount of time (in seconds) by which the processing of files placed in the Transactions tab is delayed. This is a legacy setting. Best practice is to use a File connector to manage local file systems instead of this setting.

Message

Message settings determine how the connector searches for messages and manages them after processing.

Note: The settings below are deprecated and hidden by default. They appear only on connectors where they were previously enabled or configured to a non-default value. To retain copies of successfully processed files, right-click the connector in the flow, choose Show Success Path, and connect the success path to a File connector.

Setting	Description
Save to Sent Folder (Deprecated)	Copies files processed by the connector to the Sent folder. Disabled by default. Files saved to the Sent folder are not covered by Encryption at Rest.
Sent Folder Scheme (Deprecated)	Groups files in the Sent folder by the selected time interval. Only relevant when Save to Sent Folder is enabled.

Logging

Settings that govern the creation and storage of logs.

Setting	Description
Log Level	The verbosity of logs generated by the connector. When you request support, set this to Debug.
Log Subfolder Scheme	Instructs the connector to group files in the Logs folder according to the selected interval. The Weekly option (which is the default) instructs the connector to create a new subfolder each week and store all logs for the week in that folder. Leaving this setting blank tells the connector to save all logs directly in the Logs folder. For connectors that process many transactions, using subfolders helps keep logs organized and improves performance.
Log Messages	Check this to have the log entry for a processed file include a copy of the file itself. If you disable this, you might not be able to download a copy of the file from the Transactions tab.

Other Settings

Setting	Description
Processing Delay	The amount of time (in seconds) by which the processing of files placed in the Transactions tab is delayed. This is a legacy setting. Best practice is to use a File connector to manage local file systems instead of this setting.

Miscellaneous

Miscellaneous settings are for specific use cases.

Setting	Description
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.

Automation Tab

Automation Settings

Settings related to the automatic processing of files by the connector.

Setting	Description
Send	Whether messages arriving at the connector are automatically processed.

Performance

Settings related to the allocation of resources to the connector.

Setting	Description
Max Workers	The maximum number of worker threads consumed from the threadpool to process files on this connector. If set, this overrides the default setting on the Performance Settings portion of the Advanced Settings page.
Max Files	The maximum number of files sent by each thread assigned to the connector. If set, this overrides the default setting on the Performance Settings portion of the Advanced Settings page.

Alerts Tab

SLAs Tab

Macros

Examples

XSLT Operations

In addition to the Operations provided with Arc, connectors can provide operations that extend functionality into ArcScript. These connector operations can be called just like any other ArcScript operation, except for two details:

They must be called through the connector.rsc endpoint.
They must include an auth token.

For example, calling a connector operation using both of these rules might look something like this:

<arc:set attr="in.myInput" value="myvalue" />
<arc:call op="connector.rsc/opName" authtoken="admin:1j9P8v8b9K0x6g5R5t7k" in="in" out="out">
  <!-- handle output from the op here -->
</arc:call>

The operation specific to the functionality of the XSLT connector is described below.

xsltTranslate

Translates an input XML file according to a configured XSLT connector or a specified XSLT file.

Required Parameters

ConnectorId: The name of the configured XSLT connector to use for translation, OR
TemplateFile: The path to the XSL template to use for translation, OR
Data: The contents of the XSL template to use for translation
File: The input file to translate

Optional Parameters

OutputEncoding: By default, the operation outputs ASCII data. To output base64-encoded binary data instead, set this parameter to base64.
OutputFile: When this is set, output data is not written to the Data output attribute and is instead written to the specified file.

Output Attributes

Data: The output from the translation is passed through this parameter.

Getting Started

Flows

EDI Trading Partner Management Console

Connectors

Mapping

APIs and Automation

How-To Guides

Scripting

Software License and Third-Party Copyrights

Key Capabilities

Overview

Connector Configuration

Settings Tab

Connector Settings

Other Settings

Advanced Tab

Advanced Settings

Message

Logging

Other Settings

Miscellaneous

Automation Tab

Automation Settings

Performance

Alerts Tab

SLAs Tab

Macros

Examples

XSLT Operations

xsltTranslate

Required Parameters

Optional Parameters

Output Attributes

​Key Capabilities

​Overview

​Connector Configuration

​Settings Tab

​Connector Settings

​Other Settings

​Advanced Tab

​Advanced Settings

​Message

​Logging

​Other Settings

​Miscellaneous

​Automation Tab

​Automation Settings

​Performance

​Alerts Tab

​SLAs Tab

​Macros

​Examples

​XSLT Operations

​xsltTranslate

​Required Parameters

​Optional Parameters

​Output Attributes

Key Capabilities

Overview

Connector Configuration

Settings Tab

Connector Settings

Other Settings

Advanced Tab

Advanced Settings

Message

Logging

Other Settings

Miscellaneous

Automation Tab

Automation Settings

Performance

Alerts Tab

SLAs Tab

Macros

Examples

XSLT Operations

xsltTranslate

Required Parameters

Optional Parameters

Output Attributes