Documentation Center

Setting up the Connector for Canto

The setup process for the Tridion Connector for Canto includes adding the connector itself to your Tridion Sites implementation as well as a few additional steps to enable the integration.

Before you begin

Before beginning the connector setup process, be sure you have the following:

  • Access to an Canto cloud instance (version 1 of the REST API is supported)
  • Connector Add-on package has been provided by SDL Customer Support.
  • SDL Tridion Sites 9.5 or later, is installed and fully operational .
  • The .NET Runtime version 3.1 is installed on the host machine of the Content Service and on all Content Manager server machines where the connector will be used. Download the .NET Core Runtime for either Windows or Linux from the following location: https://dotnet.microsoft.com/download/dotnet-core/3.1
  • If using the connector with Content Delivery, the PCA extension (connector-framework-pca-extension) is installed to the Content Service.

About this task

This topic describes the general process for setting up the Connector for Canto. For details on certain individual steps, refer to the linked topics.

Procedure

  1. In the Canto user interface, set up OAuth authorization for Canto.
    1. Log in to your Canto account.
    2. From Settings menu, select the Configurations Options tab.
    3. Select the API menu and create an ApiKey.
    4. Note the client ID and client secret. They will be needed in a subsequent step for configuring the connector.
  2. In each Publication where you want to expose the Canto content in Content Manager, prepare one or more stub Folders as follows:
    1. Under the Building Blocks node, create a new Folder to contain the stub items for the external system.
    2. Click Save, but keep it open for now.
    3. Go to the Info tab and note the value of the Item URI field, such as tcm:1-10-512. You will need to add this information to your connector's configuration.
    4. Click Save and Close.
    Repeat these steps for additional stub Folders, as needed.
  3. Using the Add-ons feature, upload the Connector for Canto's ZIP package.
  4. Create a JSON configuration that includes appropriate settings for this connector and your environment.
    This connector's configuration file defines two connector deployments:
    • CantoDAMConnector — defines the connector for XXX
    • CantoDownloadsConnector — defines the connector for all XXX
    For descriptions of all properties, refer to the related topic on connector configuration properties.
  5. Upload the connector's JSON configuration file to the Add-ons Service.
  6. To complete and verify the connector setup for Content Delivery, do the following:
    1. Restart the Content Service.
      The Content Service should automatically pick up the connector package and configuration from the Add-ons Service and deploy the connector.
    2. Open the GraphQL console at [Content Service URL]/cd/api/graphiql and verify the presence of appropriate GraphQL types for this connector.

Results

After successfully deploying the Connector for Canto to the Content Manager and refreshing a Publication that has been associated with the Connector (using the stubs folder TCM-URI), Canto will appear as a mount point.