Implementing connectors with Tridion Sites
This section describes how to implement a connector with Tridion Sites. Note that this section applies only to connectors that are based on the Tridion Integration Framework.
- Adding a connector to Tridion Sites
This topic describes the high-level, general process for adding a connector to your environment. The exact process to will vary depending on the specific connector and your planned use cases for it. Always refer to the connector-specific instructions in the reference section of this guide. - Configuring a connector
Connectors require that you provide custom configuration for the connector's Add-ons package in the form of a JSON configuration file, which is true whether you are implementing a prebuilt RWS connector or a custom one you have created. This topic explains the general process for configuring connectors. The exact process needed will depend on the specific connector and your planned use cases for it. - Setting up a multimedia connector in Content Manager
When implementing a multimedia connector, you probably want the external content to be available in Content Manager so that users can access, use and publish the external content along with the published Components. The External Content Library (ECL) feature makes this possible. During connector setup, there are a few tasks that you need to complete in Content Manager to enable this functionality. - Setting up a multichannel delivery connector in Content Manager
When implementing a multichannel delivery connector, there are some tasks that you need to perform in Content Manager to enable this functionality. - Configuring the ping timeout for ECL
ThePingTimeOutSecondssetting in the ExternalContentLibrary.xml file enables you to change the maximum number of seconds that a connector or ECL will wait for a response when pinging each other. For best performance, change the setting only if necessary.