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.
Archive for the 'Search' Category
Tags: content viewer, Documentum, enterprise content management, offline content
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 ‘Documentum 6.5 to 6.7 Upgrade Lessons Learned’
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.
We have recently completed a project to create a single search interface to retrieve both Documentum and SharePoint content. This post will present a high-level overview of other SharePoint search interface alternatives and why we chose the integration approach.
EMC World – 2011 – Day Three – ECM Strategy and Roadmap – 2011/2012 – Mark Arbour – Head of Product Management – ECM ApplicationsPublished May 11, 2011 CenterStage , D6.5 , Documentum , MyDocumentum , REST API , Search , Webtop , xCP , xPlore 2 Comments
Attended another roadmap session focused on next 18 months. This post will try to summarize and present TSG thoughts.
The agenda for Momentum, the Documentum portion of EMC World, has recently been posted (http://www.emcworld.com/images/Momentum_2011_Agenda-master4webpage.pdf). For this post, we thought we would highlight things we (TSG) or our typical clients attend. Overall, EMC has divided the sessions into “tracks” focused on Architecture/Best Practices, ECM, Software Developer, Information Governance, Case Management, User Group, Capture and Labs. Continue reading ‘Documentum/Momentum EMC World Prep’