1) Workflow - dm_process
A manual activity is performed by a person or multiple people. An automatic activity is performed by a script or program. A workflow is an automatic process that assigns specific tasks to specific users, in sequence, in order to carry out organizational procedures.
Participants in a workflow have the option to mark themselves as unavailable for workflow tasks. When the workflow runs, if the user selected as the performer is unavailable, the workflow engine attempts to give the work item to the user’s delegated user
To start a workflow, you choose the workflow template that specifies the sequence of tasks you want performed. The users in a workflow are called the workflow’s performers.
2) Lifecycle - dm_policy
A document lifecycle is a sequence of states a file goes through between its creation and expiration.
3) About Repository
A repository is a virtual storehouse for the content you work on and share with other employees. In addition to content, a repository also stores other items, such as workflows (the automated sequences for routing files), permission sets, and user profiles. Object in the Repository is Stored in the Object type dm_document. The content in a repository is managed by the Documentum Content Server.
4) A Permission set determines who can access a particular item in a repository. Each item in the repository has an associated permission set, determining who can access the item and what actions each user with access can perform.
5) Seven Access Level in the Permission Sets are
ü None: No access to the item.
ü Browse: Users can view the item’s properties (but not its content).
ü Read: Users can view the item’s content.
ü Relate: Users can annotate the item.
ü Version: Users can modify and check in new versions of the item.
ü Write: Users can modify and check in the item as the same version.
ü Delete: Users can delete items.
6) A rendition is an alternate copy of a file or an additional file that can be included with an object.
7) Object Types
| ACS Config | dm_acs_config |
| Activity | dm_activity |
| Document | dm_Document |
| Jar | dmc_jar |
| Java | dm_java |
| Job | dm_job |
| LDAP Configuration | dm_ldap_config |
| Method | dm_method |
| Note | dm_note |
| Policy | dm_policy |
| Sysobject | dm_sysobject |
8) A transformation is the automated rendering of a file from one look or format to another. Transformations let you automatically transform the look and format of an existing file in order to create a new rendition for the object or a new object that is related to the original object. Transformation functionality is available only on repositories that are configured with Media Transformation Services, Document Transformation Services, or both.
9) Replicas allow users of different repositories to share documents over great distances.
10) A form is an XML-based file that provides fields for you to enter and retrieve data.
11) Collaborative Services support and improve the way groups work together around content (documents, rich media assets, etc.) and processes (lifecycles, workflows).
12) Three States of the Workflow
ü Running
ü Paused
ü Terminated
13) Three Stages in LifeCycle
ü Start
ü WIP(Work in Progress)
ü Staging
ü Approved
14) To assign a lifecycle to an object, you must have at least Write permission on the object.
15) Access Levels for the Users (Basic)
| Access level | What it allows |
| None | No access is permitted to the item. |
| Browse | Users can view the item’s properties but not the item’s content. |
| Read | Users can view both the properties and content of the item. |
| Relate | Users can do the above plus they can add annotations to the item. |
| Version | Users can do the above plus they can modify the item’s content and they can check in a new version of the item (with a new version number). Users cannot overwrite an existing version or edit the item’s properties. |
| Write | Users can do the above plus they can edit item properties and check in the item as the same version. |
| Delete | Users can do all the above, and they can delete items. |
16) Access Levels for the Users (Extended)
| Extended permission | What it allows |
| Execute Procedure | Super users can change the owner of an item and can use Execute Procedure to run external procedures on certain item types. |
| Change Location | Users with Change Location permissions can move an item in the repository. |
| | Users with |
| Change Permission | Users with Change Permissions can modify the basic permissions of an item. |
| Change Ownership | Users with Change Ownership permissions can change the owner of the item. |
| Delete Object | Users with the Delete Object extended permission have the right only to delete the object. |
17) The Content Server adds these default aliases to a permission set:
ü dm_owner: Represents the owner of the permission set.
ü dm_world: Represents all repository users.
18) You must have sysadmin or superuser privileges to create users.
19) A global user is a repository user who is found in all members of a repository federation and whose attribute values are the same in all of the repositories. Global users are managed through the governing repository.
20) A role is a type of group that contains a set of users or other groups that are assigned a particular role within a client application domain.
21) Work queues hold tasks that are to be performed by available users who are assigned to the queue.
22) Web Publisher is a browser-based application that simplifies and automates the creation of content for web sites.
23) Digital Asset Manager (DAM) is a WebTop-based application that provides powerful media management capabilities such as on-demand file transformation, thumbnail viewing, and storyboard support. It extends Documentum’s powerful content management functionality to rich media, enabling content management capabilities for images, audio, and video.
24) Documentum Client for Outlook (DCO) is a WebTop-based application that provides end users with the ability to drag and drop electronic mail and attachments from Microsoft Outlook into a Documentum repository.
25) Documentum Compliance Manager (DCM) integrates with WebTop to help manage large volumes of documents that must comply with regulatory and quality standards.
26) Connection brokers, formerly called Docbroker, provide repository connection information to client applications.
27) The default connection broker port is 1489.
28) Documentum Site Caching Services (SCS) publishes documents from a Documentum repository directly to a web site.
29) dm_document - dm document is a subtype of dm_sysobject
30) I_chronicle_id - i_chronicle_id field specify parent of the whole tree.
31) what is the difference between workflow and lifecycle?
Lifecycle is just set of states which a document has to pass through in a Documentum system
Workflow is the actual business process which is applied on an object in a certain state
32) Dm_method - dm_method is a type where you mention which type of method to be run -Java, Dmbasic Documentum jobs call these dm_method objects to execute their process. Dm_method is where you define what a job should do
33) Will i_chronicle_id change when the document passes through lifecycle?
It does not change during life cycle
34) How will you deploy a workflow process?
Workflow is not deployed, but attached to a lifecycle state
35) What are the Attributes of the ACL object?
ü object_name: The name of the ACL. This must be unique for all ALCs with the same owner_name.
ü owner_name: The owner of the ACL. System ACLs are owned by the docbase owner, while User ACLs are owned by normal docbase users.
ü r_accessor_name: A repeating attribute that lists all of the users and groups that have access.
ü r_accessor_permit: A repeating attribute that lists the level of access for each user and group defined in the accessor_name attribute.
ü r_accessor_xpermit: A repeating attribute that specifies the extended permissions for each user and group defined in the accessor_name attribute. Extended permissions are only available in Documentum 4i and later servers.
36) Can you create a relation between objects in different docbases?
No, you can’t create relationships to objects in another docbase using dm_relations. There is another relationship type called dm_reference that can relate objects in different docbases. However dm_reference is not intended to be used for creating user-defined relationships, but is used for system-defined relationships like links to remote objects and virtual documents with remote children.
37) Alias sets are lists of alias names paired with the values they will resolve to.
38) Alias set can be created using DAB
39) Can I have a mix of real users and aliases as accessors in my ACL template?
No, you can’t. All accessor names are converted to alias names when an ACL template is saved.
40) What happens if I delete a document with a relation to another doc? Does the relation get deleted then or via dmclean?
The server will destroy the relationship object (dm_relation) immediately if either the parent or child is deleted. Dm_relation is a persistent type so it does not descend from dm_sysobject and therefore has no i_is_deleted flag. A dm_relation_type object will not be deleted when the last dm_relation referencing it is deleted.
41) A method is an object in the docbase that lets you launch a program on the server without being logged into the server. There are two main reasons to use server-side methods: to allow normal users to execute a command that only a superuser can execute, and to off load processor-intensive tasks from the client to the server.The best way to create a method is using a script or procedure.
42) Transactional Content Management (TCM) is an overall term for describing the management of content received or generated as part of a process.
43) EMC Documentum TaskSpace provides a user interface optimized for task processing and document retrieval, delivers an end to end solution for managing high volume TCM applications. TaskSpace also provides the ability to configure, design, and layout user interfaces in addition to core content management functionality.
44) TaskSpace:
ü Provides a streamlined, scalable user interface built for task processing and document retrieval.
ü Offers integrated document viewing with annotations.
ü Enables the management of work queues.
ü Works in conjunction with Forms Builder to allow application designers to quickly and easily create tailored applications.
ü Serves as an alternative to Webtop for process oriented applications.
45) Forms Builder is an interactive tool used to create and modify form based templates and store them in a repository. Forms Builder enables users to design user interface templates for searching, viewing documents and folders, process initiation, task lists, and tasks as well as basic forms within the Documentum Process Suite and functions as the layout tool for TaskSpace.
46) Process Builder allows for the creation of process templates. A process template captures the definition of a business process, enabling users to repeatedly perform the process.
47) EMC Documentum Composer provides a development platform for assembling, configuring, and deploying EMC Documentum applications.
48) Four Layers in Documentum
1. Repository Layer – Database, File System, Distributed Repository
2. Content Service Layer – Core services and Extended Services
3. Component and Development Layer – DFC, BOF, WDK, Portlets, Standard Based API
4. Application Layer – Web-based, Desktop, Portal and Enterprise Applications.
49) Business Object Framework(BOF) is a structured environment for developing content Applications
50) Users Basic privileges are not Hierarchical
1. None
2. Create Type
3. Create Cabinet
4. Create Group
5. Sysadmin
6. Superuser
51) A DocApp is a package of Repository Objects and itself a Repository Object.
52) A Workflow template consists of activities linked together via flows.
53) A Flow describes the movement of information from one activity to another.
54) The global registry is a central repository that serves several purposes:
ü Deploys service-based business objects (SBOs)
ü Stores network location objects
ü Stores application presets, unless another repository is configured in app.xml
ü Stores persistent user preferences, unless another repository is configured in app.xml
55) Application Connectors provide users with the ability to access a repository directly from content authoring applications. For example, a user writing a document with Microsoft Word can check the document into the repository from within Word.
56) The Emc Documentum dump and load utility let you copy a full or partial repository, including content from one Machine to another.
57) You can also do the following with dump and load utilities:
ü Copy a repository
ü Move a repository from one location to another
ü Archive a repository
ü Duplicate or move a partial repository
ü Work on cross-platforms
ü Work on cross-databases
ü Enable dump with/without content
58) Prerequisites to run dump
1. Run the Consistency Checker job and remove all inconsistencies reported.
2. Run the dmclean job.
3. Check in all the checked-out documents.
4. Clean unwanted document versions or renditions.
5. Clean old log files by the dm_LogPurge job.
6. Ensure that there is enough disk space to accommodate the dump file.
59) Sample script to dump the whole repository
create,c,dm_dump_record set,c,l,flle_name c:\Temp\dumpfile.dmp set,c,l, dump_operation
full_docbase_dump set,c,l,include content T save,c,l getmessage,c
60) Few Points about Dumps
ü There is no size limit on the dump file from Documetum unless the 0/S has a limit on it.
ü The target repository can have a different ID, name, or owner unless there is a need to preserve r_object_ids.
ü You cannot load a partial dump file.
ü You can query the r_end_time attribute of dm_dump_record or dm_load_record. If it has a valid date arid time then your dump or load was successful
61) The end goal of our workflow is to ensure that a document gets the appropriate reviews so that it can be made active to end users
62) Workflow can be created and managed by Workflow Manager and Business Process Manager.
63) Groups are used for object permissions; roles are used for application or function permissions.
64) A document is said to be a virtual document, if the value “r_is_virtual_doc” attribute is set to “1.
65) There are two types of business objects
1. Type-Based Objects (TBOs)
2. Service Based Objects (SBOs).
66) Type-based business objects (TBOs) are the most common types of business objects. They correspond to custom object types in the Docbase and used to apply custom business logic to those object types. You create a TBO by extending a DFC object such as DFDocument.
67) A service-based business object (SBOs) doesn't map to a particular object type in the Docbase.Instead, it provides general purpose functions for your application to use. Service-based objects can be used across docbases, even accessing multiple docbases at once.
68) Steps to create TBO
1. Create a new directory called 'boftest'. You will use use this directory to build, compile, and test this BOF proof-of-concept.
2. Create the TBO interface,
3. Create the TBO behavior,
4. Create the client
5. Compile the code
6. Jar up the BOF classes
7. Add the BOF entry to dbor.properties
8. Test the BOF using the client
69) About SBO
ü SBO’s are part of Documentum Business Object framework
ü SBO’s are not associated with any repositories
ü SBO’s are not associated with any Documentum object types.
ü SBO information is stored in repositories designated as Global Registry.
ü SBO’s are stored in /System/Modules/SBO/
ü Each folder in /System/Modules/SBO/ corresponds to a individual SBO
70) Data Dictionary storage is inside the Docbase. Data Dictionary can support multiple locales. Default set of Data Dictionary is enabled once Content Server is installed.
71) Annotation - Quickly add comments, markups and stamps to any document.
72) Steps to Implement SBO
1. Create a interface that extends IDfService define your business method
2. Create the implementation class implement write your business logic, This class should extend DfService and implement the interface defined in Step 1
3. Create a jar file for the created Interface and another jar for the implementation class then create Jar Definitions
4. Create a SBO Module and Deploy your Documentum Archive using Documentum Composer (Application builder for older versions)
73) Tools for Building Documentum Workflow Manager
ü Workflow Manager
ü Process Builder
74) Difference between a workflow and a distribution list
You can pass documents using a distribution list. A distribution list can send a document to a selected list of users either one after another (serial) or all at once (broadcast).
However, a workflow can contain both serial and broadcast flows. A workflow can pass documents conditionally which is not possible in a distribution list.
75) Basic process of building a workflow
1. Log on the Workflow Manager.
2. Drag and drop the activity from template to the drawing panel
3. Connect the activities using the flow tool
4. Set the parameters in Activity Inspector and Flow Inspector
5. Save, validate and install the workflow template
76) Audit trail is a built-in functionality of the Documentum Content Server. Administrators (users with Configure Audit privilege) can turn on/turn off this functionality. This functionality can record events Which are occurring while users are managing content
77) Object Types in Documentum
ü r_object_id - A Unique ID of an object.
ü i_vstamp - This property is basically used for versioning,
ü i_is_replica - This property of object that indicates whether that object is replica of an object in a remote repository
ü dm_sysobject - Most of the commonly used object types are extended from this object type.
ü dm_acl -This object type plays a very vital role in implementing security to the Documentum Server
ü dm_user -This stores all the information about user in a Documentum repository
ü dm_group -This object stores information about a specific group, which includes r_object_id of all the member users, groups.
ü dm_document- represents a real document in Repository
ü dm_folder - Folders are basically used to organize contents.
ü dm_cabinet -Cabinet is a special type of folders and its used to organize sys object in a Repository.
78) Sample Hierarchy of Object Types
79) Tools to create Custom Object types
ü Developer Studio
ü App Builder
ü Custom DQL scripts
80) A DocApp is nothing but a packaging unit for Documentum objects. A DocApp works as a deployable packaging unit to move objects across Docbases.
81) Using Documentum Application Builder you can create and package all your objects within a DocApp
82) Where to set Set dfc.Properties - web-inf\classes
83) Docbase = repository = where documents are stored along with metadata. Docbroker = something that a client uses to locate the repositories.
84) Using Documentum Administrator you can:
ü Monitor Docbase system and resource usage
ü Configure a Docbase
ü Create Docbase users and groups
ü Change the attributes of existing Docbase users and groups
ü Create or modify Docbase object types
ü Create or maintain Access Control Lists (ACL’s).
85) Jobs typically run at predetermined intervals. The jobs that exist in all repositories have default Schedules when they are created. Most jobs pass standard arguments to the method executed by the job.The arguments are set on the Method tab for each job, and can be modified in most cases.
86) Documentum Compliance Manager- Automates processes for collecting, sharing, approving and Using content in order to meet stringent quality goals and compliance requirements
87) New in Documentum 6.5
ü Presets
ü ECIS
ü Support Word 2007
ü Room Invites
ü Calendars
ü Discussions
88) Task Space is new Documentum 6 product for Transactional Content Management. Task Space is Specifically designed for users who have to perform a large number of tasks, and who have to find Documents and folders in very large repositories.
89) Documentum 6 includes the following enhancements in WebTop
ü Improved item selection lets you select items by clicking them, not by selecting checkboxes.
ü Right-click menus provide streamlined access to performing actions
ü Multi-object property editing lets you edit or assign properties, permissions and lifecycles to Multiple objects at once.
ü Lifecycle state displayed in list view
ü Resizable columns
90) Search functionality now includes the following in Documentum 6:
ü Savings the results for others to use
ü Real-time query monitoring (with ECI WebTop Extended Search option
ü Ability to perform a combined database search on properties and full-text search on strings
ü Conditional value assistance
ü User interface enhancements
91) What’s the Super type of dm_cabinet? - dm_folder
92) Content management is the organizing, categorizing, and structuring of information resources (text,Images, documents, etc.) So that they can be stored, published, and edited with ease and flexibility.
93) Documentum Layered Technical Architecture (bottom-up)
ü Repository Infrastructure (database, index…)
ü Repository Services
ü Security
ü Compliance
ü Content Services
ü Process Services
ü Client Infrastructure Layer
94) Tools, Programming Interfaces, and Configuration Interfaces across all but the Infrastructure Layer
95) D6.5 adds XML Store on the Infrastructure Layer (formerly X-Hive)
Allows for rapid XQuery against the XML in the system
96) SOA is a focus on where they are trying to move Documentum from client-server, New Paradigm
1. Easy to do from scratch, hard to transition
2. Started with 5.x with Business Office Framework
3. DFS in D6
97) Services (first 6 are in D6):
ü Schema: Data Dictionary
ü Object: Create, Update, Delete, Copy Move, Validate…etc.
ü Version: checkin, checkout, cancelCheckout, etc.
ü Query: DQL (supports paging)
ü Search: support mulltiple repositories, can tie into ECIS
ü Workflow: startProcess, getProcessInfo, etc.
ü Access Control
ü Lifecycle
ü Virtual Documents
ü Query Store: Saved searches
ü Task Management
ü Analytics
ü Content Delivery
ü Profile (CTS)
ü Transformation
ü Policy: apply, remove, getAppliedPolicies, etc. (Retention Policy Services)
ü Electronic Signature: add, verify
ü ERP Integration: execute Action, executeAgent, etc.
ü Formal Record
98) Post D6.5
ü More services
ü Services governing strict process (ensure services ineroperability)
ü Support WS Standards
ü REST support: Define resource model and URI (complimentary to the current SOAP-based services)
ü Next generation of clients will use SOA
99) Three types of services in the Intelligent Information Infrastructure: Content, Archive, and XML
100) May preclude DFC from the application layer in the future.
101) As last year, Aspects are presented as the way to slim the system object, and thus everything we throw into Documentum
102) Operation Customization D6.5 (already in there, just not documented)
ü Able to modify the behavior of action on the server-side without modifying the application
ü Import, Export, Checkout, Check-in, Cancel Checkout, Delete, Copy, Move, Validate, Transform
ü Defines steps for each operation
ü Allows operation cutomization based on Type, Format, or Repository
ü Includes modifying existing operations and creating new operations
ü Register Operation populators
ü Can add new steps and replace existing actions
ü Using BOF 2
103) BOF 3 in post D6.5
ü BOF versioning, allows different versions of BOF objects to co-exist
ü Will add notion of bundling of business objects, tracking those dependencies
ü Tighter integration with Composer (I hope so because it is miserable now)
ü Simplified customization model
104) Lightweight sysobject
ü Current sysobject 3K+ per instance (I always thought it was 2K)
ü Light ones allow multiple instances to share the same set of policies and metadata
ü One instance of Parent object and one smaller child object for each individual object
ü Changing the Parent impacts all children
ü Make use of Documentum as a Archive repository much more realistic
ü Will complement existing object model
ü Object look and behave like normal sysobject
ü Objects can be change to heavyweight sysobject from lightweight sysobject if needed so shared values on Parent can be changed without impacting the other children.
ü 30x footprint reduction seen in database, depends on number of parents to children
105) Batching
ü Allows the grouping of multiple operations into one set of SQL statements to the database
ü IDfBatchManager interface allows you to open and then close a batch. normal DFC in the middle
ü Helps with mass import, reduces round-trips to database
106) Scoping
ü Server performs checks during every operation (does this folder exist)
ü Allows for suspension of checks when performing a batch operaion
ü Default Scopes: Operation, Transaction, Batch
ü When combined with Batching, getting 3x+ performance improvement
107) Partitioning - Allows items to be placed in logical partition to manage items and to store.
108) JBoss as application server in D6.5, option or replacement? Need to ask Product Manager
109) Indexing Architecture in D7
ü Lucene (Had been D6.5, very sad)
ü support for XQuery
110) Basic privilege for User
a) None-0
b) Crete type - 1
c) Create Cabinet-2
d) Create Group – 4
e) sysadmin – 8
f) superuser- 16
111) Extended Privilege for user
a) None – 0
b) Config Audit – 8
c) Purge Audit- 16
d) View Audit-32
112) Object Type
ü LifeCycle - dm_policy
ü Workflow - dm_process
ü DocApps - dm_application
113) Difference Between Workflow and Lifecycle
Workflow is what people do and a Lifecycle is what happens to a Document
114) Enterprise Content Services (ECS)
ECS which includes all services that operate within the DFS Framework , share a common Set of Technologies built around JAX-WS , including a service context, use of the context registry and agent DFS runtime services and common runtime classes
115) Benefits of UCF
ü Can be deployed through an applet in n-tier configurations, which enables direct content transfer between the machine where the browser is located and a Content Server.
ü Support for ACS and BOCS
ü Provides support for transferring documents consisting of multiple files, such as XML documents with file references, and for creating and updating virtual documents.
ü Provides facilities for opening downloaded content in an editor or viewer.
116) Documentum allows creation of new object types, which are called custom types. A custom type can be created using Documentum Application Builder (DAB), using Documentum Administrator (DA), or using DQL/API scripts. DAB is the most commonly used application for creating custom types since it fully supports the data dictionary and it has a Graphical User Interface (GUI) specifically designed for creating and managing custom types.
Creating a custom type is a privileged operation and only the users with following privileges can do so:
ü Create Type
ü Sysadmin
ü Superuser
117) The data dictionary consists of a set of types whose objects store information about types, such as constraints for properties, default lifecycle, default property values, value assistance, mapping info, and localized text. Since the data dictionary is stored in the repository, it is available to all client applications.
118) Changing the Repository Owner Password in Documentum
a) Stop the Repository
b) Go to $DM_HOME/dba/config/
c) Create a copy of the file with name dbpasswd.txt
d) In the DB change the password of Repository Owner
e) Edit the dbpasswd.txt( The file backed up in Step 3) and replace the new password as plain text
f) Save dbpasswd.txt
g) Go to $DM_HOME/bin run the following
h) dm_encrypt_password -docbase
i) Restart the Repository
119) Documentum Object Hierarchy Diagram
120) i_vstamp - This property is basically used for versioning, each time you save changes to the object the value of this property increases by 1 and this also helps to check the concurrent modification of object.
121) i_is_replica - This property of object that indicates whether that object is replica of an object in a remote repository
122) Documentum Object support 2 types of Attributes
1. Single Value Attributes - Single Value properties are properties that can hold a single value at a time For Eg: object_name One object will have only a single name
2. Repeated Attributes - Repeated Attributes are properties that can hold multiple values. For Eg: Keywords A object can have multiple keywords attached to it
123) Cabinets - A Cabinet object is the highest level of Organization visible to the users in a Repository. Means Cabinets can exist only in the top level in the Repository. Cabinet object extends from Folder. But Any object that extends from dm_sysobject (ie means any object that can be saved in a repository) are stored in Cabinets. A Cabinet cannot be placed inside another cabinet or a folder and you need super user privileges to create or remove a Cabinet.
124) Folders - The Folders are means of organizing objects that can be saved (Any object that extends from dm_sysobject other than dm_cabinet) and it is used with combination of a Cabinet. In other words a Folder cannot exist without a Cabinet. All objects that are saved in a repository must be saved either in a folder, which is inside a cabinet, or it can be saved directly in a cabinet. Folder extends from dm_sysobject and the internal name of folder is dm_folder and r_object_id of a dm_folder starts with “0b”.
125) Documentum Composer, a new application for packaging and deploying Documentum artifacts. It is meant to replace Documentum Application Builder and Documentum Application Installer with a single application for developing, building, and deploying Documentum projects into a repository.
126)The ServiceFactory is used to construct service instance. As parameters, the ServiceFactory requires the class name of the service to create, the URL to the service WSDL, and a populated ServiceContext.
127) The ServiceContext object provides stateful information such as repository credentials to a service instance. Once created, ServiceContext instances can be optionally registered with the Context Registry Service which allows them to be shared among multiple service instances
128) A ServiceContext instance must be associated with at least one RepositoryIdentity instance.A RepositoryIdentity instance stores a repository name and its login credentials for the service
129) How will you differentiate repeating fields and single value fields - Repeating fields have multiple values and single fields have only one value
130) what about security in Documentum - Security in documentum is enforced by permission levels, ACLs and groups/roles
131) How to create Users?
There are two ways to create users in Documentum
a) Using DQL
create dm_cabinet object set object_name = '%USERNAME%'
create dm_user object set user_name = '%USER DISPLAY NAME%,
set default_folder = '/%USERNAME%',
set user_os_name = '%USERNAME%',
set user_privileges = %PRIVILEGES%',
set user_address = '%USER EMAIL%
b) Using the IAPI:
create,c,dm_user
set,c,l,user_name
set,c,l,user_os_name
set,c,l,user_address
save,c,l
132) what is the difference between super user and administrator
A superuser is a user with higher permission levels than other users. An administrator also have high level of permissions but he will be able to do the administrative tasks such as configuring the docbase, scheduling the jobs, managing the sessions etc.
133) What is dfc & dmcl, differenctiate both?
DFC is DCTM foundation class framework which is a set of Java classes to interact with DCTM server. DMCL is the inherent language understood by the server.
134) Differences between iAPI and DQL
iAPI is a set of commands that are given to the server. DQL is the DCTM query language to query the docbase like a database.
135) Under what scenarios will you use iAPI ?
ü iAPI is used to create objects, check-in and checkout, DQL cannot be used for that purpose.
ü iAPI is basically used when no other client is available with server
ü iAPI is also used to cross check the operations performed by the user code.
136) What is a Permission Template?
A Permisssion template is an ACL which assigns a set of permissions to a set of users.
137) What is docapp and Documentum Application Installer?
A docapp is a documentum application which can be installed by documetum app installer. A Docapp can contain a set of custom objects, attributes, lifecycles and customized forms that can manipulate the docbase.
138) Component and Container - Component Contain more than one Container . Container can found inside the Component
139) App.xml file - This is the XML File that contains startup page or Startup Component
140) What is the recommended method for migrating Web Content Management (WCM) Page Builder templates, blueprints, managed links, and associated content from a production environment to a testing environment?
a. archive and install a DocApp
b. perform a repository-to-repository copy operation through WebPublisher
c. execute cabinet dump and load
d. use a deep export/import through WebPublisher
Answer: a
141) IDQL supports query execution while IAPI supports direct invocation of the API functions.
142) Workflows typically represent business processes and model event-oriented applications. Workflows can be defined for documents, folders (representing the contained documents), and virtual documents.
143) Lifecycles define business rules that can be applied to different types of documents.
144) Content Server is the foundation of the Documentum platform and provides the following standard services:
ü Content management services
ü Process management services
ü Security services
ü Distributed services
145) What is required for using Business Object Framework 2 (BOF 2)?
a. a dfc.properties file on all client machines such as application servers
b. a DBOR.properties and a dfc.properties file on all client machines such as application servers and a global registry repository
c. a DBOR.properties file on all client machines and a global registry repository
d. a global registry repository and a dfc.properties file on all client machines
Answer: d
146) Which file replaces the pre-D6 dmcl.ini?
a. dfc.properties
b. docbroker.ini
c. java.ini
d. dbor.properties
Answer: a
147) Certain operations on an object mark it as immutable, which means that object properties cannot be changed. An object is marked immutable by setting r_ immutable_ flag to true.
148) Object Type - An object type is a template for creating objects. In other words, an object is an instance of its type.
149) Content Server uses UTF-8 encoding of Unicode. The Unicode standard provides a unique number to represent every character in every language. UTF-8 is a way of representing these numbers in binary form. Unicode enables Content Server to store metadata using characters from different languages and to manage multilingual content.
150) Custom Objects can be created using DA
151) what format that object are stored in the repository? - MSW8
152) Add on Services in Documentum Content Server
Trusted Content Services (TCS) provides additional security features such as digital shredding of content files, strong electronic signatures, content encryption, and enhanced ACLs.
Content Services for EMC Centera (CSEC) adds support for Centera storage for guaranteed retention and immutability. Centera storage is suitable for storing large amounts of infrequently changing data that needs to be retained for a specific period.
Content Storage Services (CSS) enables the use of content storage and migration policies, which automate the assignment of content to various storage areas. CSS can be used for optimizing the use of storage infrastructure in the enterprise. CSS also provides features for content compression and de-duplication.
Retention Policy Services (RPS) enables use of policies to manage the lifecycle of the objects stored in the repository. A retention policy defines the phases through which such an object passes and how it is finally disposed off or archived.
153) Can we change the name of custom folder? If yes, where we have to change?
Right click->Properties .In the name textbox, type the new name and save
154) What is the use of components in documentum?
Components are visual elements in wdk applications (like Menubar, Breadcum,etc.,)
155) Would you install Content Server, Database, Application server on one machine? - YES
156) Aspects provide an alternative to placing attributes on a standard object type.
157) A registered table is a table from the underlying database that has been registered with the repository. This registration allows the table to be specified in a DQL query, either by itself or in conjunction with a type. A registered table can be used in place of an object type in most DQL queries and its columns can be used as properties in a DQL query.
158) How are these content files associated with a SysObject? In other words, how does Content Server know what metadata is associated with a content file? How does it know that one content file is a rendition of another one?
Content Server manages content files using content objects, which (indirectly) point to the physical locations of content files and associate them with SysObjects.
159) Explain different ways new object types and attributes can be created
From DA create type by specifying or not specifying supertype and by using DAB
160) List as many native Documentum types as you can
ü dm_document
ü dm_folder
ü dm_cabinet
ü dm_sysobject
ü dm_user
ü dm_store
ü dm_process
ü dm_job
ü dm_method
ü dm_relation
ü dmr_content
161) How are these content files associated with a SysObject? In other words, how does Content Server know what metadata is associated with a content file? How does it know that one content file is a rendition of another one?
Content Server manages content files using content objects, which (indirectly) point to the physical locations of content files and associate them with SysObjects.
162) List as many native Documentum attributes as you can
ü r_object_id
ü title
ü subject
ü object_name
ü owner_name
ü r_object_type
ü r_creation_date
ü r_modify_date
ü a_content_type
ü log_entry
ü acl_domain
ü acl_name
163) Every content file in the repository has an associated content object, which stores information about the location of the file and identifies the SysObjects associated with it. A content object is an object of type dmr_content.
164) Documentum Client-Server Application Communication
a. The Content Server projects to the connection broker
b. The client connects to the connection broker to retrieve connection information for the Content Server
c. The client establishes a connection and issues API commands to the Content Server via the DFC
d. The Content Server processes the client APIs and retrieves the requested information from the repository
e. The Content Server sends the information back to the client using APIs via the DFC
165) Presets and its Order - A preset determines the selections or actions available in particular situations. Creating a preset offers a way to reduce screen options to those options that are relevant to the user’s task in the particular situation. A preset comprises one or more rules. Each rule determines the selections or actions available within a specific functional area. For example, a rule can determine available lifecycles, available actions, or available auto complete text. Presets allow user to configure menu /format/type /lifecycle/workflow selection for different users, groups, roles or location. The item or set of items is called the preset’s scope. Creating a preset offers a way to reduce screen options to those options that are relevant to the user’s task in the particular situation.
The default order of precedence for applying presets is as follows: a preset for a location takes first precedence; then a preset for a user; then a preset for a role; then a preset for an object type. Presets can be disabled by adding the elements
166) Difference between 5.3,6.0, 6.5
ü DQL calls triggers an onSave() call on the object
ü Java 1.5 (and beyond) is supported, this was a big win form my point of view.
ü DFS - EMC created web services to access Documentum objects.
ü The UI had some major changes for DA / Webtop, many actions were moved to a new and really snazzy looking "right click menu"
ü On a more technical side the dmcl.ini file is now deprecated, DFC code running on a client box now utilizes the dfc.properties file
ü EMC released Composer, which is an Eclipse port that works really well with Documentum.
ü tomcat , 6.0 – Weblogic , 6.5 – Jboss
167) A federation is a set of two or more repositories bound together to facilitate the management of a multi-repository distributed configuration.
168) To deploy methods to the method server, simply copy the class files or JAR files to the%DOCUMENTUM%\dba\java_methods directory on the Content Server.
169) How to hide a version label radio button for a particular Object type"?
Easiest way is to modify the jsp that correspond to the checkin component.
170) Where we use Presets?
ü Restricting the actions for users/roles/locations
ü Default values of attributes
ü Restrictions of format / type selections in preset
ü Columns for listing pages
ü Navigation customizations
171) MTOM to transfer a BinaryContent representation and BASE_64 to transfer DataHandlerContent and we use this in DFS
172) EMC Documentum’s workflow model allows an authorized user to easily develop process and event-oriented applications for document management. The model supports both production and ad hoc workflows. An authorized user can define workflows for individual documents, folders containing a group of documents, and virtual documents. A workflow’s definition can include simple or complex task sequences (including those with dependencies). Users with appropriate permissions can modify in-progress workflows. Workflow and event notifications are automatically issued through standard electronic mail systems while documents remain under secure server control. Workflow definitions are stored in the repository, allowing an authorized user to start multiple workflows based on one workflow definition.
173) Workflow Model
a) We have Workflow Manager to create the Workflow definition which is called workflow template.
b) At runtime we create a workflow instance which refers to the workflow template.
c) The server workflow engine controls the flow logic according to the workflow definition in the workflow template.
d) User performs on the tasks through the client application. Or the task itself be performed by some applications.
174) REGISTER Statement
ü Registers an RDBMS table so that eContent Server can recognize the sql table
ü Allows access to data in an existing RDBMS table that may be created to support additional application data part of another application owned by someone else
ü Does not verify that the table or its columns exist
ü All columns in a table need not be registered
ü Creates a dm_registered object in the System cabinet which provides a description of the table and user access to it
175) Steps to create Register Table
Register a RDBMS table by register keyword
REGISTER TABLE [owner_name.]table_name (column_def {,column_def})[[WITH] KEY (column_list)]
[SYNONYM [FOR] ‘table_identification’]
Eg: REGISTER TABLE johndoe.”remote1 (“columnA” int)
176) An implicit association is created by putting the form control inside the label element, while an explicit association is created by giving the label element a for attribute with the same value as the form control’s id attribute.
177) Alias - Reusability and portability. Alias sets are stored as dm_alias_set objects in Documentum. They can make already powerful Documentum features like Workflow, Lifecycles, and Access Control Lists even more powerful by allowing critical attribute values to be resolved dynamically.
Alias sets remove the need to hard-code the names of users, groups, locations, and permission sets throughout your application and instead provide a means for setting these values dynamically as your personnel changes and your business processes evolve.
178) Alias Sets are the Collection of Aliases (Which has alias names and its values)
ü Resolve a Sysobject’s owner name and/or ACL dynamically
ü Resolve Workflow task performers dynamically
ü Specify the Docbase location(s) for linking objects dynamically
ü Take advantage of a rich scheme for resolving aliases in different circumstances
179) An alias is referenced using one of two formats—%alias_set_name.alias_name or just %alias_name
180) Aspects - Aspects extend behavior and attributes for objects. An object type defines the properties and behavior of all objects of that type (and of its subtypes, via inheritance). In contrast, aspects enable us to attach additional behavior and attributes to an object, regardless of its type.Even though aspects can be attached regardless of the type of object, aspects cannot be attached to arbitrary types of objects.
Aspects can be attached under the following restrictions on types
ü An aspect can be attached to any sysobject.
ü An aspect can be attached to any object of null type (type with no supertype), once the type has been altered to allow aspects.
ü It is also possible to attach multiple aspects to one object but one aspect cannot be attached multiple times to the same object.
ü If an aspect's name contains a dot, such as jumbo.loan, it cannot have any properties.
181) base 64 is used for encoding and decoding during the import operation and export operation of files
182) The Business Object Framework (BOF) is a set of functionality included starting with DFC 5.1 that provides ability to hook into any of the methods in the standard DFC object interfaces.
Docbasic code which runs either as part of a Method configured in the docbase or as part of the lifecycle scripts. Since dmbasic talks directly to the DMCL API, it does not go through DFC and therefore does not get the benefit of the BOF layer.
183) Deploying BOF - In DFC 5.3, Documentum has introduced a new way of managing BOF code that is far superior to the DBOR. BOF code is now stored in the repository and dynamically loaded by DFC as needed by application code running against that docbase. SBOs can be hosted in a single “global” repository, providing the same functionality to multiple docbases. TBOs can now be hosted and configured in only the docbase that uses them, allowing for different TBO registrations to be set up for different docbases
With 5.3, Documentum has introduced the concept of a “module”, which is a unit of executable code that is stored in the docbase. Service Based and Type Based Objects are one kind of module. To support this new module framework, a few new object types have been introduced: dmc_jar, dmc_module, and dmc_java_library.
dmc_jar - The dmc_jar object type is a subtype of dm_document, and it is used for JAR archives containing Java code. This might include a JAR containing your TBO implementation class(es), or perhaps your SBO interface class(es), types of modules in DFC 5.3. Methods can now be implemented by repository-based module code. Documentum’s new (limited) support for aspects is also implemented using repository-based module code.
184) Type Based Objects(TBO)
public class BfExampleOneTbo extends DfDocument implements IDfBusinessObject, IDfDynamicInheritance
{
protected IDfId doCheckout(String versionLabel, String compoundArchValue, String specialAppValue,
Object[] extendedArgs) throws DfException
{
185) Service Based Objects(SBO)
public interface IBfLogService extends IDfService {
/** Logs a warning message indicating that the given document has been checked out, as well as some information about the lock owner.
public void logCheckout(String docbase, IDfDocument document) throws DfException;
}
//Implementation
public class BfLogService extends DfService implements IBfLogService
{
public void logCheckout(String docbase, IDfDocument document) throws DfException
{
//Implement SBO in TBO
protected IDfId doCheckout(String versionLabel, String compoundArchValue, String specialAppValue,
Object[] extendedArgs) throws DfException {
// Let the superclass perform the actual checkout.
IDfId newId = super.doCheckout(versionLabel, compoundArchValue, specialAppValue, extendedArgs);
// Get a session; it will be released automatically.
IDfSession session = getSession();
// Instantiate the SBO.
IDfSessionManager sessMgr = session.getSessionManager();
IDfClient client = session.getClient();
IBfLogService logService = (IBfLogService) client.newService(IBfLogService.class.getName(), sessMgr);
// Call the SBO method.
logService.logCheckout(session.getDocbaseName(), this);
----------------- Print Out Taken -------------------------------------------------------------------------------
186) Alias Example - Imagine a company with a simple review process for their documents: before a document is released, it must be reviewed by the author’s manager. Using Alias Sets, each author can have his or her own unique alias that relates the word “manager” to a user in the docbase. This allows a single workflow to be used by every author in the docbase. The workflow is designed to route the document to the “manager” alias, which will be resolved differently at run time for each author. Instead of requiring a different workflow for each author, a single workflow can be used with Alias Sets
Although this review process seems simple, without Alias Sets, it would be difficult to implement since the manager’s name would have to be hard-coded as the reviewer, requiring a different workflow for each author.
187) Difference between Client Capability and Privileges?
Client Capability is used by a client program (Intranet Client, Desktop Client or your own app etc) to determine what levels of functionality (dialog boxes for example) are presented to the user. It is separate from the user's privileges, which are used by the server to determine what the user is actually allowed to do.
5 comments:
Thank you for posting.
you are a documentum guru .... thanks a lot....
Excellent guide
Very helpful article
Very well done! Thanks a lot!!
Post a Comment