How to create a custom Documentum index-agent?
Best Answer
-
We can use REGISTER API command for registering the required user for the required object type on specific events, so that object event for that object type will create queue item for that specific user.
For example, if we register dm_save event for test_user for dm_document, then any new creation of dm_document object will create queue item for test_user automatically.
Here is the syntax for register API: register, session, object-ID, event
session --> Identifies an open repository session
object-ID --> Identifies the object or object type for which you are registering the event.
To identify a particular object, use the object’s object ID or an indirect reference (@object_id).
To identify an object type, use the object ID of the type’s dm_type object. The object type must be SysObject or a SysObject subtype. Sysadmin or Superuser privileges are required to specify an object type.
event --> Defines the event for which you want to receive notification. All the available event details can be found in Documentum CS Admin Guide.Hope this helps:)
HariHari Gadhamsetty
Architect, Consulting Services
OpenText0
Answers
-
Yes, Index Agent approach appears to be helpful for your requirement.
Create new user, register this user to create queue items automatically for doc update/deletion. Then use the same user to query the queue items at regular intervals (may be every 5 mins.) using DFC code, and fetch the required metadata of those documents to store on your additional database.
Hope this helps:)
Hari Gadhamsetty
Architect, Consulting Services
OpenText0 -
We can use REGISTER API command for registering the required user for the required object type on specific events, so that object event for that object type will create queue item for that specific user.
For example, if we register dm_save event for test_user for dm_document, then any new creation of dm_document object will create queue item for test_user automatically.
Here is the syntax for register API: register, session, object-ID, event
session --> Identifies an open repository session
object-ID --> Identifies the object or object type for which you are registering the event.
To identify a particular object, use the object’s object ID or an indirect reference (@object_id).
To identify an object type, use the object ID of the type’s dm_type object. The object type must be SysObject or a SysObject subtype. Sysadmin or Superuser privileges are required to specify an object type.
event --> Defines the event for which you want to receive notification. All the available event details can be found in Documentum CS Admin Guide.Hope this helps:)
HariHari Gadhamsetty
Architect, Consulting Services
OpenText0
Categories
- All Categories
- 107 Developer Announcements
- 53 Articles
- 106 General Questions
- 142 IM Services
- 43 OpenText Hackathon
- 32 Developer Tools
- 20.6K Analytics
- 4.1K AppWorks
- 8.9K Extended ECM
- 898 Cloud Fax and Notifications
- 76 Digital Asset Management
- 9.3K Documentum
- 29 eDOCS
- 118 Exstream
- 39.8K TeamSite
- 1.7K Web Experience Management
- Docker Automation
- LiveSite Content Services (LSCS) REST API
- Single Page Application (SPA) Modules
- TeamSite Add-ons
If you are interested in gaining full access to the content, you can register for a My Support account here.