Configuring the Documentum Connector

The DocumentumConnector.config is the Documentum Connector configuration file where you configure, amongst others, connection details between Documentum and the Content Manager of SDL Tridion.

Procedure

  1. Open the DocumentumConnector.config configuration file, located by default in your SDL Tridion installation \DocumentumConnector directory, in a text editor.
  2. Configure the following settings:
    <DfsUrl>
    The URL of the Documentum Foundation Services (DFS) from which to retrieve renditions. DFS is the programming interface to the Documentum platform.
    <DctmRepositoryName>
    The Documentum repository from which to retrieve objects.
    <DctmLoginName>
    The name with which to retrieve renditions from Documentum.
    <DctmLoginPassword>
    The password to use when retrieving renditions from Documentum. Set isPassword="true" to ensure the element is encrypted when you run the encryption tool.
    <DctmRenditionNameToReturn>
    The default rendition to retrieve during rendering. You can override using Template Building Block parameters and from the Dreamweaver Template.
    <SchemaId>
    The TCM:URI of the Multimedia Schema for Documentum-based documents, for example tcm:1-549-8.
    <RootFolderId>
    The TCM:URI of the Folder is where assets from Documentum are displayed, for example tcm:1-85-2. Specify the TCM:URI of the Folder in the Publication in which this Folder is a local item (where the Folder was created).
    <NotificationWebServiceUrl>
    The URL of the TridionEventService in the Documentum Connector where notifications are sent.
    <NotificationWebServiceUserName>
    The name with which to send notifications to Documentum.
    <NotificationWebServicePassword>
    The password to use when sending notifications to Documentum. Set isPassword="true" to ensure the element is encrypted when you run the encryption tool.
    <CoreServiceUrl>
    The URL to use when communicating with the Content Manager through the Core Service. The Documentum Connector connects to the Core Service via an endpoint. Documentum Connector provides an out-of-the-box endpoint for connecting to the Core Service using the NetTcpBinding binding which uses the net.tcp protocol to communicate with the Core Service:
    <CoreServiceUrl>net.tcp://localhost:2660/CoreService/netTcp_2010</CoreServiceUrl>
    <MmcCreationUserName>
    The user account used by the Documentum Connector Web service to create the Multimedia Component stubs displayed in the Content Manager Explorer for assets from Documentum.
    <TridionAdministratorUser>
    The user account used by the DocumentumConnector.Editor to read the Asset Folder structure and update the cache it has of these in Application Data.
    <CacheExpirationTimeMilliseconds>
    Folder overlay information is cached. The cache is updated periodically by the time specified.
    <BinaryEventSynchronizationTargets>
    The targets from which to retrieve binary events so that implicitly published or removed binaries show up as published and unpublished in the Content Manager Explorer and Documentum is notified of this event. For each SynchronizationTarget specify the following attributes:
    • url—the URL from which to read the binary events. For more information, see Installing the binaryeventsync Web page.
    • targetType—the TCM URI of the Target Type on the url.
    • componentTemplate—the TCM URI of the Component Template to associate with the publish/unpublish action (typically the Default Component Template).
    For example:
    <BinaryEventSynchronizationTargets>
        <SynchronizationTarget targetType="tcm:0-1-65537" url="http://localhost:8090/binaryeventsync.aspx" componentTemplate="tcm:1-24-32"/>
        <SynchronizationTarget targetType="tcm:0-2-65537" url="http://localhost:8080/upload2/binaryeventsync.jsp" componentTemplate="tcm:1-24-32"/>
    </BinaryEventSynchronizationTargets>
  3. Save and close the file.