Skip to main content
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.
SettingDescription
Connector IdThe static, unique identifier for the connector.
Connector TypeDisplays the connector name and a description of what it does.
Connector DescriptionAn optional field to provide a free-form description of the connector and its role in the flow.
XSL Template FileThe 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.
SettingDescription
Document FunctionCheck this to allow use of the document() function while processing XSLT.
Embedded ScriptsCheck this to allow use of embedded scripts while processing XSLT.

Advanced Tab

Advanced Settings

SettingDescription
Local File SchemeA 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 DelayThe 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.

Logging

Other Settings

SettingDescription
Processing DelayThe 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

Automation Tab

Automation Settings

Settings related to the automatic processing of files by the connector.
SettingDescription
SendWhether messages arriving at the connector are automatically processed.

Performance

Alerts Tab

SLAs Tab

Macros

Examples

XSLT Operations

In addition to the Operations provided with , connectors can provide operations that extend functionality into Script. These connector operations can be called just like any other Script operation, except for two details:
  1. They must be called through the connector.rsc endpoint.
  2. 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.