This blog is the first post in a series that will consist of multiple short posts that touch on a number of differences between TSG’s HPI solution and the Webtop and D2 interfaces. For the first post, we will discuss searching for content. Users of ECM systems are often willing to put up with some of the more complex functionality (i.e. checkin, checkout, workflows), if they can quickly and accurately locate content. However, if users are unable to easily perform this basic function, you can be sure that they will be quick to loudly voice their concerns and find ways around using the ECM application.
One of the first questions for any Alfresco implementation is: “how will users search and access documents?”. As longtime readers of the TSG blog will know, we typically recommend against the user “I just was a Google Search” approach. Most of our clients want to target certain document types/scenarios and search on key attributes to find content. This post will discuss how TSG’s High Performance Interface (HPI) gives clients an easy way to configure powerful searches against documents that utilize custom types and attributes.
Retrieving data from a Documentum Repository using DQL is a common and robust process with Documentum. With addition of the xPlore search engine, there are some challenges that experienced DQL users may find unique. This post will discuss our experience with DQL and xPlore.
Last week we updated a client’s .NET application to replace Documentum’s defunct PIA (Primary Interop Assembly) API with calls to OpenSearch through HPI. This client’s HPI instance is an offline content viewer portal that utilizes Solr for searching and serving documents. The .NET code change was minimal, simply replacing the PIA calls with OpenSearch calls effectively changing the source of where the application gets its documents from Documentum to Solr. Decoupling the .NET application from the proprietary Documentum API provides greater flexibility in designing, developing, and deploying web applications as well as removing Documentum licensing. After the change to call Opensearch, the application is now shielded from any future upgrades or changes within the Documentum API.
TSG recently assisted a client with upgrading their Documentum 6.5 environment to 6.7. Products included Content Server, xPlore, Business Process Manager (BPM), Content Transformation Services (ADTS, AVTS, MTS), DA, Webtop, Records Manager, Retention Policy Services (RPS), Archive Services for Reports (ASR), and TaskSpace. The client also runs TSG’s High Performance Interface (HPI) and OpenContent products. Continue reading
I was talking to a client last week that was struggling with their Documentum system performance. This client had recently brought in Documentum Consulting, and having been unsuccessful in improving performance, was concerned that there might be nothing left to do. This post will focus on innovative things TSG has done for clients in regards to Documentum performance that are probably outside of the norm of typical database/server tuning particularly focused on Search, Document Retrieval and Inbox viewing.
We’re working with a large Pharmaceutical company to install Documentum xPlore as a replacement for FAST. We’ve just finished the QA environment deployment, and we’re planning for the Production deployment in mid-April. For this post, we are going to discuss the cutover strategy as well as some lessons learned from the project.
Since EMC’s announcement of Documentum D2 late last year, there has been a lot of buzz, and we’ve received a number of inquiries regarding the functionality and underlying technologies of the product. For those who are interested in finding out more information about D2, we would recommend checking out our earlier posts and screen cams that highlight some of the features of the product.
This post summarizes the previous articles that we’ve written in the past few months that give additional information about D2.
When developing a taxonomy for an ECM implementation, the question of how heavily to use folders to classify content always arises. Out-of-the-box implementations of Documentum using WDK applications, like Webtop, typically rely heavily on creating new content in folders, as well as using folder trees to find documents. TSG has had a lot of success with implementing consumer interfaces that utilize folder-less metadata and full-text search to deliver content. Similarly, contributor interfaces can be set up in a way that users can create content and set metadata attributes without the need for manually putting documents into a complex folder structure.
This article will discuss the pros and cons of using folders to classify content in an ECM system. Similar to our previous articles about consumer and contributor functionality, this article will compare the out-of-the-box features with regards to folders that are available in four Documentum user interfaces, Webtop, D2, HPI and xCP.
As we have mentioned on this site multiple times, performance and ease of use in regards to searching is one of the most frequent concerns as it relates to use of Documentum. During our review of D2, we thought it would make an interesting blog post as well as screencam for our Learning Zone to compare searching across the different options (D2, Webtop, HPI and XCP) with Documentum. For our review, we are only presenting configuration only approaches without any customization.