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 'OpenSearch' Category
Tags: content viewer, Documentum, enterprise content management, offline content
Similar to our recent post and whitepaper on Documentum and SharePoint integration, this post will present similar options for Alfresco users. We recently posted an example of SharePoint and Alfresco integration in our Learning Zone. This post will present a recap of possible solutions to compare and contrast the alternatives.
TSG has recently released a detailed whitepaper on Documentum and SharePoint Search Alternatives. The complete paper is available on our website in the downloads section. This post will share the summary conclusion.
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.
Every couple of months we like to step back and offer a “What’s next” post in regards to our thoughts on what Documentum customers should be considering with their implementations. For this post, we will highlight our thoughts based on a thorough review of EMC World and our client briefing discussions. Continue reading ‘Documentum – Top 12 Tips’
In addition to the enhancements to HPI disscussed last week, we are also enhancing the search capability in HPI for a large Documentum pharmaceutical client. Features will include:
- Lucene Integration: enhanced compatibility of HPI and Lucene through TSG’s OpenContent web services layer
- Save Search: save, recall, run, delete and edit a saved search
- OpenSearch Integration: execute a Lucene search (full text and metadata) and return it in an OpenSearch compliant RSS feed that includes a custom namespace to allow for exporting custom metadata in XML format
- Enhanced Search Controls: new multi-select control that includes a type-ahead feature
- Direct Linking: enable direct linking to content via a URL
- Doc Management: one-click links to view versions from the search results
- Single Sign On: leverage Kerberos to perform automatic application authentication
Core components of these enhancements will be rolled into our HPI 1.4 feature set and will be available later in 2010. For more information and to download HPI or view recorded demos. Please visit http://www.tsgrp.com/ and our Learning Zone.
OpenContent (TSG’s ECM Web Services Layer) and OpenSearch now share more than a similar name. The original OpenSearch 1.0 specification was released in March 2005, and was developed by Amazon. OpenSearch is a collection of technologies that allow publishing of search results in a format suitable for syndication and aggregation. Using OpenSearch standards allow search results to be consumed by a variety of services.
We recently had a client inquire about the ability of OpenContent to run queries that return results in the OpenSearch format. In this particular instance, the client was utilizing Carrot2, a “Search Results Clustering Engine” which allows a variety of search sources be searched from a single portal. Utilizing OpenContent’s REST web services, we were able to create a simple search service that takes in a search phrase, runs the query against a Documentum full-text repository, and returns the results in an OpenSearch compliant feed to be consumed by Carrot2.
Creating an OpenSearch compliant feed also allows us to use the search bar available in modern browsers such as IE8 and Firefox to perform a search of the content repository. This support provides another great way to quickly search for content within the Documentum repository, the same way you might search other search engines like Google, Amazon, Wikipedia, or EBay.
For more information on OpenContent, click here or e-mail us at email@example.com