Explore topic-wise InterviewSolutions in Current Affairs.

• Solaris
• AIX
• HP-UX
• LINUX (Redhat/Fedora - sorry other Linux GUYS, these are the only ones I personally TESTED with)
• WINDOWS 2000+ Server

SOMETIMES you don't WANT user to load the WORD FILE, so you automate the CREATION of PDF or JPEG, and presents it to the user.

sometimes you don't want user to load the Word file, so you automate the creation of PDF or JPEG, and presents it to the user.

an IMAGING software. Full text cannot search WORDS inside images, so you need CAPTIVA to do OCR during SCANNING.

an imaging software. Full text cannot search words inside images, so you need captiva to do OCR during scanning.

creates word per word SEARCH results. Documentum will search EVEN the WORDS INSIDE the MSWORD file.

creates word per word search results. Documentum will search even the words inside the MSWord file.

Sysadmin

• Create, alter, and drop users and groups
• Create, modify, and delete system-level ACLs
• Grant and revoke Create Type, Create CABINET, and Create Group privileges
• Create types, cabinets, and printers
• Manipulate workflows or work ITEMS, regardless of ownership
• Manage any object’s lifecycle
• Set the a_full_text attribute
• The Sysadmin privilege does not override object-level permissions

Super USER

• Perform all the functions of a user with Sysadmin privileges
• Unlock objects in the repository
• Modify or drop another user’s user-defined object type
• Create subtypes that have no supertype
• Register and unregister another user’s tables
• Select from any underlying RDBMS table regardless of WHETHER it is registered or not
• Modify or remove another user’s groups or private ACLs
• Create, modify, or remove system ACLs
• Grant and revoke Superuser and Sysadmin privileges

Sysadmin

Super User

For Content Server:

• Documentum FOUNDATION Classes 6.5 SP1
• EMC CENTERA SDK 3.2
• Red Hat JBOSS ENTERPRISE APPLICATION Platform 4.2.0 CP01

For Content Server:

OS: Windows 2000 SP2

DATABASE: Oracle 10.2.8 , 10.2.9 , 11 G

SQL Server: 2000 SP4

App Server: Tomcat 5, BEA Web Logic 8.1 SP6

Browser: IE , Mozilla , Nescafe , Safari

JRE CLIENT: JRE 1.4.2

Java ( Server): Java 1.4

Portal SOFTWARE: BEA WEBLOGIC Portal 8.1 , IBMWebsphere Portal 5.1

OS: Windows 2000 SP2

Database: Oracle 10.2.8 , 10.2.9 , 11 G

SQL Server: 2000 SP4

App Server: Tomcat 5, BEA Web Logic 8.1 SP6

Browser: IE , Mozilla , Nescafe , Safari

JRE Client: JRE 1.4.2

Java ( Server): Java 1.4

Portal Software: BEA Weblogic Portal 8.1 , IBMWebsphere Portal 5.1

HARD DISK Space: 3.2 GB to Install , 3 GB to RUN

RAM: 4 GB

Hard Disk Space: 3.2 GB to Install , 3 GB to Run

RAM: 4 GB

Hard DISK Space: 4 GB

RAM: 2 GB Ram

Hard Disk Space: 4 GB

RAM: 2 GB Ram

Unified Client Facilities (UCF) is a lightweight client-server application that transfers content between a DFS consumer, a DFS service, and a content repository.

The UCF APIs provide a remote UCF server on the service host with access to the client file system and registry, and provides support for:

• client- orchestrated content transfer in a web application or service chain
• Integration with ACS and BOCS for optimized transfer in DISTRIBUTED architectures
• Transfer of complex content types, such as XML content with file references and Microsoft OFFICE documents with INTERNAL links
• post-transfer actions (which generally MEANS opening the content in a viewer or EDITOR)

Unified Client Facilities (UCF) is a lightweight client-server application that transfers content between a DFS consumer, a DFS service, and a content repository.

The UCF APIs provide a remote UCF server on the service host with access to the client file system and registry, and provides support for:

MTOM is for (LARGE files)

MTOM, an acronym for SOAP Message Transmission Optimization Mechanism, is a W3C recommendation adopted by JAX-WS. Enabling MTOM means that both the request that the SOAP client is SENDING to the server and the returned response GO though MTOM ENCODING and decoding.

MTOM is for (Large files)

MTOM, an acronym for SOAP Message Transmission Optimization Mechanism, is a W3C recommendation adopted by JAX-WS. Enabling MTOM means that both the request that the SOAP client is sending to the server and the returned response go though MTOM encoding and decoding.

Base64 is for Smaller Files around 5kb

Base64 is an established encoding for transfer of opaque data inline within a SOAP message (or more generally within XML). The encoded data is tagged as an element of the xs : BASE 64Binary XML schema data type.

Base64 encoded data is not OPTIMIZED, and in fact is known to expand binary data by a FACTOR of 1.33x original SIZE. This makes base64 inefficient for sending larger data files. As a rule, it is OPTIMAL to use base64 for content smaller than around 5K bytes. For larger content files, it is more optimal to use MTOM.

Base64 is for Smaller Files around 5kb

Base64 is an established encoding for transfer of opaque data inline within a SOAP message (or more generally within XML). The encoded data is tagged as an element of the xs : base 64Binary XML schema data type.

Base64 encoded data is not optimized, and in fact is known to expand binary data by a factor of 1.33x original size. This makes base64 inefficient for sending larger data files. As a rule, it is optimal to use base64 for content smaller than around 5K bytes. For larger content files, it is more optimal to use MTOM.

The dmc_jar OBJECT type is a subtype of dm_document, and it is used for JAR ARCHIVES containing JAVA CODE.

The dmc_jar object type is a subtype of dm_document, and it is used for JAR archives containing Java code.

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.

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.

Even though aspects are not automatically tied to object types sometimes we may have a NEED to do just that (often for convenience).

For example, we may have an existing type called dq_loan_doc and we may want all of its objects (and of its subtypes) to have an aspect dq_web_viewable attached. If an aspect is ASSOCIATED with an object type, the aspect is automatically attached to each new object of the specified object type. Such an aspect is called a DEFAULT aspect for the specified type.

Of COURSE, this aspect can still be attached to objects of other types (SUBJECT to the restrictions mentioned earlier). Default aspects for an object type are recorded in dmi_type_info.default_aspects for the type.

Even though aspects are not automatically tied to object types sometimes we may have a need to do just that (often for convenience).

For example, we may have an existing type called dq_loan_doc and we may want all of its objects (and of its subtypes) to have an aspect dq_web_viewable attached. If an aspect is associated with an object type, the aspect is automatically attached to each new object of the specified object type. Such an aspect is called a default aspect for the specified type.

Of course, this aspect can still be attached to objects of other types (subject to the restrictions mentioned earlier). Default aspects for an object type are recorded in dmi_type_info.default_aspects for the type.

An ASPECT without any PROPERTIES can serve as a flag where the presence of this flag can be CHECKED on objects.

An aspect without any properties can serve as a flag where the presence of this flag can be checked on objects.

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.

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

The Content Server is supported by METHOD SERVERS, which can execute methods. In this context, a method is a piece of CODE that can be scheduled to run as a job or can be invoked from a workflow ACTIVITY or a lifecycle action.

There are TWO kinds of Method Servers:

• Dmbasic Method Server
• Java Method Server

The Content Server is supported by Method Servers, which can execute methods. In this context, a method is a piece of code that can be scheduled to run as a job or can be invoked from a workflow activity or a lifecycle action.

There are two kinds of Method Servers:

The application or the client interacts directly with the web SERVICE USING standards and PROTOCOLS related to web services. However, the web service itself becomes a DFC-based client described in the fundamental pattern earlier. While the communication pattern between the web service and the Content Server instance is the same as that described for a DFC-based client, the pattern between a web service client and the web service is different.

Usually, a DFS client sends a request to the DFS web service and that leads to an interaction with the Content Server instance. The interaction between a DFS web service and its client follows web service standards and a TYPICAL USAGE of these protocols.

The application or the client interacts directly with the web service using standards and protocols related to web services. However, the web service itself becomes a DFC-based client described in the fundamental pattern earlier. While the communication pattern between the web service and the Content Server instance is the same as that described for a DFC-based client, the pattern between a web service client and the web service is different.

Usually, a DFS client sends a request to the DFS web service and that leads to an interaction with the Content Server instance. The interaction between a DFS web service and its client follows web service standards and a typical usage of these protocols.

An alias set is SIMPLY a LIST of aliases (LIKE “reviewer” or “supervisor”) and the values that they RESOLVE to.

• 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

An alias set is simply a list of aliases (like “reviewer” or “supervisor”) and the values that they resolve to.

Aliases is a 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.

In Simple words Aliases are placeholders that can hold any of the following

• A User or a Group Name
• Folder information

Alias is a key value PAIR where key is the alias name and value is the ACTUAL value.

An alias is referenced using one of two formats—%alias_set_name.alias_name or just %alias_name

Aliases is a 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.

In Simple words Aliases are placeholders that can hold any of the following

Alias is a key value pair where key is the alias name and value is the actual value.

An alias is referenced using one of two formats—%alias_set_name.alias_name or just %alias_name

• Consumer
• CONTRIBUTOR
• CO ordinator
• System ADMINISTRATOR