Explore topic-wise InterviewSolutions in Current Affairs.

Keystore stores PKI CREDENTIALS that DFC client uses to COMMUNICATE with GLOBAL registery.

Keystore stores PKI credentials that DFC client uses to communicate with global registery.

An AUDIT Trail is the history of INSTANCES of an Audit Event. Each instance of an Audit Event results in the creation of one Audit Trail entry which stores information about the event (such as the time of the event, which objects were involved, who performed the ACTIONS, and which VALUES were affected).

An Audit Trail is the history of instances of an Audit Event. Each instance of an Audit Event results in the creation of one Audit Trail entry which stores information about the event (such as the time of the event, which objects were involved, who performed the actions, and which values were affected).

FLUSH is used to clear the Persistent CACHE and Publish is to publish the DATA Dictionary.

Flush is used to clear the Persistent Cache and Publish is to publish the Data Dictionary.

JBOSS and WEBLOGIC

JBOSS and Weblogic

A quickflow is something that you create on the spot when you want it... SORTA ad-hoc. A FULL workflow is SAVED within the system and has a predefined set of steps. It's GOOD for if you had a process of approvals that you needed to go through to GET a document approved.

A quickflow is something that you create on the spot when you want it... sorta ad-hoc. A full workflow is saved within the system and has a predefined set of steps. It's good for if you had a process of approvals that you needed to go through to get a document approved.

To make your full text index more EFFICIENT, you should AVOID INDEXING nonselective or commonly found words.

To make your full text index more efficient, you should avoid indexing nonselective or commonly found words.

The contents of renditions are stored as dmr_content. The CONTENT of a DELETED DOCUMENT can be retrieved using dmr_content.The actual document or the content is stored as dmr_content and it is linked to dm_document which stores the METADATA.

The contents of renditions are stored as dmr_content. The Content of a deleted document can be retrieved using dmr_content.The actual document or the content is stored as dmr_content and it is linked to dm_document which stores the metadata.

DAB/DAI is an MFC-based application that was USED to configure Documentum artifacts.

Composer is INTENDED to replace DAB/DAI and is built on TOP of the Eclipse INFRASTRUCTURE. This allows us to build new capabilities much easier on top of an industry-standard platform.

DAB/DAI is an MFC-based application that was used to configure Documentum artifacts.

Composer is intended to replace DAB/DAI and is built on top of the Eclipse infrastructure. This allows us to build new capabilities much easier on top of an industry-standard platform.

Verity’s Full TEXT Engine is a powerful search tool embedded within Documentum’s Content SERVER. It enables a user to search both attributes and content stored within the Docbase without leaving the Documentum environment. Using the full-text search a user can PERFORM a comprehensive search of both attributes and content through the execution of a single QUERY.

Going down to the bottom of the picture, task list is created for manual tasks. In this case, performer receives the task in the Inbox. He completes the task through the Task MANAGER interface of the client.

For automatic tasks, the Workflow Engine will invoke the applications directly. Here the applications can talk to the Workflow Engine through server methods and/or DFC.

Verity’s Full Text Engine is a powerful search tool embedded within Documentum’s Content Server. It enables a user to search both attributes and content stored within the Docbase without leaving the Documentum environment. Using the full-text search a user can perform a comprehensive search of both attributes and content through the execution of a single query.

Going down to the bottom of the picture, task list is created for manual tasks. In this case, performer receives the task in the Inbox. He completes the task through the Task Manager interface of the client.

For automatic tasks, the Workflow Engine will invoke the applications directly. Here the applications can talk to the Workflow Engine through server methods and/or DFC.

1)Start with workflow template

• The workflow template OBJECTS: dm_process, a list of dm_activity objects

2)Create workflow instance

• ü Create a dm_workflow object
• ü dm_workflow points to the workflow template dm_process
• ü SAVE dm_workflow
• ü dm_workflow is in DORMANT state

3)Run the workflow

• ü Execute dm_workflow
• ü dm_workflow is in Running state

1)Start with workflow template

2)Create workflow instance

3)Run the workflow

ü Performer tab

• Performer information
• Delegate, REASSIGN, and signoff information

ü PACKAGE tab

• Package information
• Port/link definition

ü Transition tab

• Determine what to do when the TASK is completed
• Transition types:

§ all - all NEXT tasks will be started

§ manual transition - performer chooses the next tasks (forward or reject)

§ auto transition - server PICKS the next tasks based on the condition defined

ü Trigger tab

• Determine when to start this task
• Trigger conditions:

§ all - all previous tasks are done

§ some - certain number of previous tasks are done

§ event - the task will not start until a certain event arrives

Number of times the activity can run

ü Performer tab

ü Package tab

ü Transition tab

§ all - all next tasks will be started

§ manual transition - performer chooses the next tasks (forward or reject)

§ auto transition - server picks the next tasks based on the condition defined

ü Trigger tab

§ all - all previous tasks are done

§ some - certain number of previous tasks are done

§ event - the task will not start until a certain event arrives

Number of times the activity can run

Here we have a closer look at the Workflow functional COMPONENTS. Starting from the top, we have Workflow Manager which is used to create workflow template. Workflow template can also reference alias set and LDAP INTEGRATION in its definition.

Coming to the center of the diagram is the workflow runtime control. In the center is the SERVER Workflow Engine, maintained by Workflow Supervisor. It controls automated aspect of the BUSINESS process

The Workflow Engine references the the routing document (content).

The Workflow Engine also maintains a set of workflow control data. It is used to control the processing of the existing tasks and to determine the next tasks.

Here is the object model in DCTM server.

• Business Process - what is intended to happen
• On the left is the Design Time Definition. Workflow Template is defined by

1. Process Definition - dm_process, representation of what’s intended to happen
2. Activity Definition - dm_activity, representation of what’s intended to achieve at a logical step

• On the right is the Run Time Management

1. Workflow Instance - dm_workflow, controls automated aspect of the business process and record runtime information of workflow
2. Task - record run time information of activity
3. Work Item - dmi_workitem, task allocated to task performers
4. Queue Item - dmi_queue_item, peer item for work item for querying in Inbox
5. Package - dmi_package, references documents and comments routed among task

Here we have a closer look at the Workflow functional components. Starting from the top, we have Workflow Manager which is used to create workflow template. Workflow template can also reference alias set and LDAP integration in its definition.

Coming to the center of the diagram is the workflow runtime control. In the center is the Server Workflow Engine, maintained by Workflow Supervisor. It controls automated aspect of the business process

The Workflow Engine references the the routing document (content).

The Workflow Engine also maintains a set of workflow control data. It is used to control the processing of the existing tasks and to determine the next tasks.

Here is the object model in DCTM server.

The INDEX AGENT is the component that communicates with the CONTENT Server to retrieve content that needs to be indexed. The Index Agent passes indexable content to the Index Server; the Index Server actually builds and maintains the indexes and responds to search REQUESTS.

The Index Agent is the component that communicates with the Content Server to retrieve content that needs to be indexed. The Index Agent passes indexable content to the Index Server; the Index Server actually builds and maintains the indexes and responds to search requests.

There are few search options that can IMPROVE performance.

• EFFICIENT Security CHECKS
• Avoid Unselective QUERIES

There are few search options that can improve performance.

A customized Parallel search specifies a SINGLE filestore as part of the search CRITERIA. You can issue multiple search REQUESTS to the INDIVIDUAL filestores,THUS spawning multiple search requests.

A customized Parallel search specifies a single filestore as part of the search criteria. You can issue multiple search requests to the individual filestores,thus spawning multiple search requests.

A SINGLE filestore can contain APPROXIMATELY 10 million indexable DOCUMENTS.

A single filestore can contain approximately 10 million indexable documents.

To make documents in a filestore available for SEARCHING, you must first create ONE or more COLLECTIONS. A collection is set of PARTITIONS (directories and files) that allow search users to use the Verity search engine to quickly find and display documents MATCHING various search criteria.

To make documents in a filestore available for searching, you must first create one or more collections. A collection is set of partitions (directories and files) that allow search users to use the Verity search engine to quickly find and display documents matching various search criteria.

The Documentum 5 PLATFORM INTRODUCED the Java method server as a means of improving the performance and scalability of the Documentum method architecture.

The method server runs as a PROCESS distinct from the Content Server and is responsible for the invocation of the individual methods. Each method invocation results in a call to the method server which manages the actual execution of the Java-based method IMPLEMENTATION. As the method server is a continuously running process, there is no overhead INVOLVED in loading and tearing-down a Java virtual machine with each invocation. This yields an enormous benefit in overhead.

The Documentum 5 platform introduced the Java method server as a means of improving the performance and scalability of the Documentum method architecture.

The method server runs as a process distinct from the Content Server and is responsible for the invocation of the individual methods. Each method invocation results in a call to the method server which manages the actual execution of the Java-based method implementation. As the method server is a continuously running process, there is no overhead involved in loading and tearing-down a Java virtual machine with each invocation. This yields an enormous benefit in overhead.

GRANT CONFIG AUDIT to USER User_name

Grant Config Audit to User User_name

SELECT group_name from dm_group where any i_supergroups_names='enterprise'

Select group_name from dm_group where any i_supergroups_names='enterprise'

ALTER GROUP group_name DROP (SELECT user_name from dm_user where user_os_name = 'karthik')

ALTER GROUP group_name DROP (select user_name from dm_user where user_os_name = 'karthik')

ALTER GROUP group_name ADD (SELECT user_name from dm_user where user_name = 'karthik')

ALTER GROUP group_name ADD (select user_name from dm_user where user_name = 'karthik')

SELECT user_name, user_os_name, user_state from dm_user where user_state=0 and r_is_group=0 ORDER by user_name

select user_name, user_os_name, user_state from dm_user where user_state=0 and r_is_group=0 order by user_name

GRANT CONFIG AUDIT to USER User_name

Grant Config Audit to User User_name

UPDATE dm_user OBJECTS SET user_state = 1 WHERE user_name = 'username'

UPDATE dm_user OBJECTS SET user_state = 1 WHERE user_name = 'username'

SELECT count (*) from dm_user where last_login_utc_time>DATE (NOW)-90

Note: This QUERY retrieves the use LOGIN information by using their last successful login as REFERENCE

Select count (*) from dm_user where last_login_utc_time>DATE (NOW)-90

Note: This query retrieves the use login information by using their last successful login as reference

SELECT * from dm_user where last_login_utc_time>DATE (NOW)-90

Select * from dm_user where last_login_utc_time>DATE (NOW)-90

Persistent Cache:A cache of Docbase OBJECTS and query results available across client sessions. Persistent caching PRESERVES cached content during SHUTDOWN and startup of DMCL and avoids REPEATEDLY retrieving objects that are accessed infrequently

WebDAV:Web -based Distributed Authoring and Versioning. A set of extensions to the HTTP protocol that allows users to collaboratively edit and MANAGE files on remote Web servers.

Persistent Cache:A cache of Docbase objects and query results available across client sessions. Persistent caching preserves cached content during shutdown and startup of DMCL and avoids repeatedly retrieving objects that are accessed infrequently

WebDAV:Web -based Distributed Authoring and Versioning. A set of extensions to the HTTP protocol that allows users to collaboratively edit and manage files on remote Web servers.

The location in Workflow Manager of ACTIVITY and workflow OBJECTS that are USED to BUILD workflow TEMPLATES.

The location in Workflow Manager of activity and workflow objects that are used to build workflow templates.

This product from Captiva ENABLES users to input information in the form of paper, fax and MICROFICHE and transform it into electronic data, convert it into a usable format, and then store it automatically in the Documentum repository, InputAccel Capture for Documentum gives organization s a better way to coordinate and ensure the integrity of incoming data and HELPS them turn it into business-ready content.

This product from Captiva enables users to input information in the form of paper, fax and microfiche and transform it into electronic data, convert it into a usable format, and then store it automatically in the Documentum repository, InputAccel Capture for Documentum gives organization s a better way to coordinate and ensure the integrity of incoming data and helps them turn it into business-ready content.

An INDEX of words in all DOCUMENTS that Docbase users have ASKED to INCLUDE in the index.

An index of words in all documents that Docbase users have asked to include in the index.

A GROUP of Docbase that have ONE GOVERNING Docbase and other MEMBER Docbase.

A group of Docbase that have one governing Docbase and other member Docbase.

A digital workplace for DISTRIBUTED teams to collaborate on content and processes. This application includes FEATURES like project planning TOOLS, discussion thread, and drag-and-drip file sharing.

A digital workplace for distributed teams to collaborate on content and processes. This application includes features like project planning tools, discussion thread, and drag-and-drip file sharing.

A group whose members are DYNAMICALLY added to or removed from the group by a CLIENT application at runtime. Dynamic groups ALLOW administrators to control permissions and access based on client application and USER LOCATION.

A group whose members are dynamically added to or removed from the group by a client application at runtime. Dynamic groups allow administrators to control permissions and access based on client application and user location.

Documentum CLIENT LIBRARY. It manages the COMMUNICATION between the client and the CONTENT Server.

Documentum Client Library. It manages the communication between the client and the Content Server.

Is an attribute of a Documentum user that determines what he/she can do from a client application. For example, a user with the capability of a Consumer can only search and view CONTENT as needed. A Contributor, on the other HAND, can CRATE content.

Is an attribute of a Documentum user that determines what he/she can do from a client application. For example, a user with the capability of a Consumer can only search and view content as needed. A Contributor, on the other hand, can crate content.

A rule that IDENTIFIES which VERSION of a component to include in your VIRTUAL DOCUMENT.

A rule that identifies which version of a component to include in your virtual document.

If I Import a Document it comes from LOCAL DRIVE and Resides in Repository ( ORACLE STORED the Metadata of the Document ) . If User Checkout the Document it comes from the Repository and then it stores in C:DocumentumCheckout Directory

If I Import a Document it comes from Local Drive and Resides in Repository ( Oracle Stored the Metadata of the Document ) . If User Checkout the Document it comes from the Repository and then it stores in C:DocumentumCheckout Directory

web.xml - A WDK based J2EE Web APPLICATION has a root DIRECTORY which contains a WEB-INF FOLDER. This folder has a web.xml file containing configuration information for the web application. This is mandated by the J2EE Servlet Specification

app.xml - A WDK application is a folder within the main J2EE Web application root directory. If you see your webtop folder, it contains the following four WDK applications. custom, webcomponent,wdk and webtop

Each Application will have its own app.xml. Inheritance is CONTROLLED by the TAG in the app.xml file of the WDK application

The following are the application tags for a standard webtop installation:

•  custom
• webtop
• webcomponent
• wdk

 The ‘wdk’ WDK application does not inherit from any layers as it the core framework. For each WebTop/DA installation, there is one web.xml and four app.xml.

web.xml - A WDK based J2EE Web application has a root directory which contains a WEB-INF folder. This folder has a web.xml file containing configuration information for the web application. This is mandated by the J2EE Servlet Specification

app.xml - A WDK application is a folder within the main J2EE Web application root directory. If you see your webtop folder, it contains the following four WDK applications. custom, webcomponent,wdk and webtop

Each Application will have its own app.xml. Inheritance is controlled by the tag in the app.xml file of the WDK application

The following are the application tags for a standard webtop installation:

 The ‘wdk’ WDK application does not inherit from any layers as it the core framework. For each WebTop/DA installation, there is one web.xml and four app.xml.

Right Click on the CUSTOM FOLDER and CHANGE the Name of the Folder.

Right Click on the Custom Folder and Change the Name of the Folder.

To deploy methods to the METHOD server,we need to simply copy the CLASS files or JAR files to the %DOCUMENTUM% dba java_methods directory on the Content Server. The method server will include them in its classpath.

Jboss is the Java Method Server in D6 .Whenever classes are deployed to the method server, the method server will need to be STOPPED, the TMP folder in %DOCUMENTUM% jboss1.4.2 server DctmServer_MethodServer tmp and START the server. We can find the jboss logs under %DOCUMENTUM% dba jboss1.4.2 DctmServer_MethodServerlog.

To deploy methods to the method server,we need to simply copy the class files or JAR files to the %DOCUMENTUM% dba java_methods directory on the Content Server. The method server will include them in its classpath.

Jboss is the Java Method Server in D6 .Whenever classes are deployed to the method server, the method server will need to be stopped, the tmp folder in %DOCUMENTUM% jboss1.4.2 server DctmServer_MethodServer tmp and start the server. We can find the jboss logs under %DOCUMENTUM% dba jboss1.4.2 DctmServer_MethodServerlog.

Site Caching Services is used to extract content and metadata from the REPOSITORY and deliver it to a file system. The file system can be any file system on any accessible host–it doesn’t have to be a web server.

In addition to moving the actual content, SCS can MOVE the metadata to a target relational database. The database can then be used for personalization.

Site Caching Services is used to PUBLISH content from a Documentum repository to a WEBSITE. 

Site Caching Services is used to extract content and metadata from the repository and deliver it to a file system. The file system can be any file system on any accessible host–it doesn’t have to be a web server.

In addition to moving the actual content, SCS can move the metadata to a target relational database. The database can then be used for personalization.

Site Caching Services is used to publish content from a Documentum repository to a website. 

Each Content Server INSTANCE has a file NAMED server.ini which it reads on start-up. Each Content Server instance also has a server configuration object (of TYPE dm_server_config). Projection TARGETS can be specified in the server.ini file and the server configuration object

Each Content Server instance has a file named server.ini which it reads on start-up. Each Content Server instance also has a server configuration object (of type dm_server_config). Projection targets can be specified in the server.ini file and the server configuration object

SELECT r_folder_path FROM dm_folder WHERE r_object_id in (SELECT i_folder_id FROM dm_document WHERE object_name='object_name')

SELECT r_folder_path FROM dm_folder WHERE r_object_id in (SELECT i_folder_id FROM dm_document WHERE object_name='object_name')

SELECT last_login_utc_time from dm_user where user_name=' NAME of USER'

select last_login_utc_time from dm_user where user_name=' name of user'

If you can live with just CURRENT documents with metadata (no renditions), you can use Composer to migrate CONTENTS and folder structure from ONE REPOSITORY to ANOTHER. There is one Tool Named Buldosar that copy the Metadata and Renditions along with the Document.

If you can live with just CURRENT documents with metadata (no renditions), you can use Composer to migrate contents and folder structure from one repository to another. There is one Tool Named Buldosar that copy the Metadata and Renditions along with the Document.

There are 2 MAJOR OBJECT types that you need to KNOW in

1. dm_relation_type - This DEFINES a relation, MEANS this object type holds the information about the relation like its name, security type, parent type, child type etc.User must have SysAdmin or Super User privileges to create object of this type. All the objects of this type will have r_object_id starting with 38
2. dm_relation - This defines each individual relationship between the objects. Means this type has ID’s of the both parent and child object which makes the relation, the name of the relation etc. All the objects of this type will have r_object_id starting with 37

There are 2 major object types that you need to know in

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.

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.Customized installations might vary. It is important to NOTE that presets are not used to PROVIDE security.

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.

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.Customized installations might vary. It is important to note that presets are not used to provide security.

• Apache Tomcat (SUGGESTED is 5.0.28 and above, works like a charm, our PRODUCTION actually runs Tomcat)
• Websphere 5 (and above)
• Web LOGIC
• JBOSS ( 6.5)

• ORACLE
• DB2
• Sybase
• MSSQL - would you believe MSSQL is the most NUMBER of DB being USED by Documentum