The Problem

Developer wants to build an application on top of Documentum Content Repository to create/update/read/act on content stored in Documentum Repository. They have two available options. They can either connect to Documentum Content Server as Named User or Gateway User. Diagram below explains Named user and Gateway User mechanisms.

In the named user access, the application connects to Documentum as a user it is performing action as, where as in Gateway user access, application connects to Documentum as a application user that performs actions on behalf of the users that is interacting with the application.

Solution

The decision on which mechanism to use should be based on the actions that are being performed by the application for the users and not on easy of development.

If the actions that are performed by the application are related to active content, where the content is updated, versioned, modified, different policy applied, audited, etc then use “Named User” access.

If the actions that are performed by the application are related to inactive or fixed content, where the content is being stored in the Documentum repository as record or archived content then find out if you know who if the application knows the user on whose behalf it is performing action.

If one would use “Gateway User” for active content, then

• One would have to keep track of checkout-owner, date, etc outside Documentum repository, which is not a good idea.
• One would not be able to take advantage of Documentum auditing capabilities, subscriptions, etc.

Typical Scenarios

1. Most interactive applications/solutions should use named users access to Documentum.
2. Some examples of applications where Gateway user access is appropriate are
   • Documents scanned into Documentum Repository as records, typically by a scanner operator, who is not the real owner of the content.
   • Content created into Documentum repository from various types of devices including medical devices, where the content created is fixed content and will not be altered.
   • Content stored in Documentum repository as final record for archival purposes.

About DFE

This article is provided by the Designed for EMC team.

You can discuss this article on the EDN Forums by clicking here.