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.
Before you begin
To complete a configuration file for an connector, you need to know the following:
- The name of the connector as it is defined in the Add-on's manifest file
- When using the connector with Content Delivery, the name of each Content Delivery environment to be configured, as defined in the cdenvironment variable of each environment
- When using the connector with Content Manager, the item URIs of each stub Folder or stub Category that this connector will make use of for ECL functionality
About this task
After adding a connector to your Tridion Sites implementation, create a JSON configuration file to your needs and upload it to the Add-ons service. The configuration includes settings that are specific to your implementation, such as endpoint URL, username, password, and more.
Refer to the subtopics for a full explanation of the connector configuration file's multi-level structure and for descriptions of the common properties that can be configured for a connector (other properties vary from connector to connector).