XAM (Xerox Attachment Manager) - Documentum

XAM Overview

Xerox Attachment Manager or XAM: is a set of components that enable users associating (attaching) documents in Documentum repository  with unique records in another system (targeted system), by establishing a Documentum relation between the unique identified of the record in the targeted system and the unique identified of the document in Documentum repository, where the relation is going to be stored in Documentum.

XAM Components:

·         XAM WDK Component: which represents the interface required by XAM to browse the repository and locate the required repository

·          XAM Authentication Manager Component: this component is an integration component of the targeted system, which generates a login ticket from the targeted system to Document system based on logged in user in the targeted system.

·         XAM URL Manager Component: responsible for generating URL which contains the encrypted login ticket in addition to the unique identifier of each record from the targeted system

·         XAM Auto-Linking Manager Component: It is a job that sets in the background, which it responsible to attach automatically the newly created documents in Documentum with its corresponding records

XAM Scope:

·         XAM is used to attach documents resides in Documentum to records in the targeted system

·         Users between two systems must by in sync. This can be guaranteed if the targeted system is using LDAP authentication for the users, otherwise the users need to be synced manually.

·         XAM requires access to some required tables in the targeted system using a RDBMS read-only user. The tables would hold information about the record that is going to be associated to the document(s) in Documentum.

·         The records in the targeted systems must have a unique identifier which can be used to establish the relation with the attachments.

·         XAM authentication manager may require access to some libraries in the targeted system in order to establish the login ticket to access Documentum document.

·         Users would be able to open, edit, or delete documents in Documentum as per their assigned privilege in Documentum.

·         The relation between records and documents is many-to-many, which means the same record may associated with more than one attachment (document), and the same document can be attached to different records in the targeted system.

·         If auto-linking between the systems is required, then the document properties must share some information with the record, specially the record unique identifier of the targeted system.

·         Deleting the record in the targeted system requires first to remove the relation with all the attachments manually using XAM interface. Otherwise the system will still assume that the document is still attached to a record in the targeted system.

·         Deleting a document in Documentum, requires to remove manually the relation between that document and its associating records. This needs to be performed by Documentum administrator using special DQL statements that can be provided.

·         Updating the shared properties on the document would not update the record information and vice versa, which means updating the shared properties on the record would not update the shared properties on the document.  This is required only for XAM Auto-Linking Manager Component. However, if the record information is updated in the targeted system. XAM will look for any matching document using the linking criteria and establish a relation between the updated record and the newly matched documents.