JBoss as the method server in 6.5

With Documentum 6.5, JBoss is embedded with Content Server to support the running
of all Content Server Java-based components including:

• Java Method Server
• ACS
• BOCS
• DMS
• IA

Weblogic is no longer embedded in the Content Server.

If you are upgrading from version 5.3.x, 6, or 6 SP1 to version 6.5, the upgrade will
not remove the binaries of the Tomcat and WebLogic application servers. This is
because Tomcat and Weblogic are supported for client and UCF type applications,
while JBoss is used for the Java method server.

Content server 6.5 available

We are finally installing EMC content server 6.5 in a testing environment. I have downloaded installation files and supplemental materials and I’m happy to announce that I’m installing 6.5 for the first time.



Some new features (http://www.emc.com/about/news/press/2008/documentum-delivers-d65.htm ):

Documentum CenterStage Essentials



EMC Documentum CenterStage Essentials is a very easy-to-use collaboration and document management application designed to meet the needs of the modern knowledge worker.

Documentum Media WorkSpace




EMC Documentum Media WorkSpace is the next-generation interactive content launch platform. This highly configurable, intuitive, web-based inteface exposes a set of powerful new features that enable you to fully leverage the value of your rich-media assets.

Documentum Web Publisher Page Builder



EMC Documentum Web Publisher Page Builder enables non-technical business users to employ a highly dynamic, interactive WYSIWYG editor for website creation and content contribution.

XML store integration




The enhanced XML capabilities in Documentum ECM 6.5 are delivered through Documentum XML Store, a new native XML database available within the Documentum platform and related content delivery applications. A market first, EMC provides an integrated, end-to-end solution for creating, managing, accessing, archiving and delivering XML alongside all other types of enterprise content. Documentum's XML capabilities consist of robust management of XML documents and components, high-performance search and query of XML content, dynamic delivery and content transformation applications for content repurposing and personalized publishing as well as solutions for Technical Publications (DITA) and Aerospace and Defense (S1000D).

Default permission set and inheritance of permission

A permission set (also known as an ACL, or access control list), defines the object -level permissions applied to objects to which the permission sets are assigned.

There are three options available for default ACL assignment: type, folder and user. The default setting in affect on content server is permission inherited from user (Picture).

Inherit from user:

This is a default setting on content server and it gives user the ability to grant/revoke permission on individual documents. This leads to creation of unique ACL for every document in the repository.
A user’s default ACL is recorded in the user’s acl _name and acl _domain attributes .

Inherit from type:

number of acls = number of types.

The type of document defines who can access the document. You have to define default ACL for every sysobject object type – not only for your custom types. The reluctance to do that, can result in errors when creating certain objects, for example users:

Error committing changes

[DM_SYSOBJECT_E_TYPE_DEF_ACL]error: “ACL inheritance failed, due to missing ACL in the type ‘dm_cabinet’.

The simplicity of this setting also makes it not very flexible. If you want to aggregate permissions for accounting dept, you would have to create more object types.

Inherit from folder:

This type of permission inheritance is used in most operating systems and requires management of ACLs at the folder level.
A folder or cabinet’ s default ACL is recorded in the object’ s acl _name and acl _domain attributes.

Sysinternal tools all on one place

Microsoft gave us easier access to Sysinternals tools. Anybody who had to look through all the web pages in search of a specific tool would appreciate this.

Link to the sysinternals file share is: http://live.sysinternals.com/ .

If you don’t have any knowledge about sysinternals tools and have Microsoft based environment, you should look into them. You can find all about sysinternals tools on this site: http://technet.microsoft.com/sysinternals .

As per Microsoft:

This is a file share allowing access to all Sysinternals utilities. We have developed this to test an alternate distribution mechanism for our utilities. This will allow you to run these tools from any computer connected to the Internet without having to navigate to a webpage, download and extract the zip file. If you are unfamiliar with Microsoft Windows Sysinternals, it is highly recommended that you visit the website at http://technet.microsoft.com/sysinternals before using these tools. If you have any questions or comments on this file share, please email syssite@microsoft.com

ACS/BOCS error when checking-in content in documentum 5.3 SP5

Error:

Failed to retrieve content from ACS/BOCS server(s). The ACS/BOCS server(s) may be down or your machine may not be able to reach the server(s) due to network connectivity or configuration issues com.documentum.ucf.common.UCFException: All remote hosts failed.

We found out that is not recommendable to install Application Builder application on the content server. We had numerous ACS/BOCS server is missing errors. Once we uninstalled Application Builder application the problem stopped occurring.

"Show all properties" checkbox visible in webtop

Default setting in EMC Documentum 5.3 SP5 WebTop is that you cannot preview custom attributes of a file unless you are administrator.

To present webtop user option to edit custom attributes of a file, you have to make some changes to the webtop-s configuration files:

You have to edit attributes_dm_document_component.xml file. The file is located in:

\webapps\webtop\webcomponent\config\library\attributes\

Portion of XML, that you have to edit is presented here:

<!-- Enable show-all-attributes (for administrators) -->
<filter role='administrator'>
<enableShowAll>true</enableShowAll>
</filter>

Here we have edited portion of XML file. As you can see we deleted administrator and leave blank:

<!-- Enable show-all-attributes (for administrators) -->
<filter role=''>
<enableShowAll>true</enableShowAll>
</filter>

Now we can present custom attributes to the webtop user even if the user has no administrator rights.