EMC Documentum Search Server: The Next Generation for Fulltext Search in the Documentum Platform: EM

I’ll be speaking at EMC World 2010 in Boston (May 10 to 13), delivering the session “Documentum Search Services: Next Generation Search in Documentum Platform”. During my one hour session, I’ll be talking about the upcoming release of Documentum Search Services (DSS), provide some a product overview, comparison to the current FAST Indexing Engine that is embedded with Documentum, and help guide you in planning migrations to DSS.

DSS has been designed to provide ease of deployment, higher scalability and smaller overall footprint. In addition, it has been optimized to provide relief for many of the common performance and quality of search issues that our customers have been struggling with such as underprivileged users, folder descend queries to name a few.

DSS is compatible with 6.5 SP2 or later to make migrations easier. Starting in 6.7, DSS will be the default Search Engine available with the Documentum Product stack.

The upcoming transition to DSS is something that all customers using search today with Documentum will need to make in 2011, but with early planning, the transition can be made easily while providing tremendous improvements for the overall search experience of your end users.

I’d be happy to answer any questions folks may have on this topic before (or after) EMC World. Also, if you have requests for particular topics related to DSS to be addressed, I’ll be happy to try and include them in my talk.

I look forward to seeing all of you in Boston.

-Aamir

Find more posts tagged with

Comments

XdctmX

Is it already released? If not what is the roadmap for it? I don’t see DSS in the download center.

VMware support and Windows 2008 64 bit OS support was what we were waiting for. Glad to know that both will be supported by DSS.

XdctmX

What is the memory requirement for DSS? Is it going to be the same as FAST (min 4 GB!)

ramnreddy

Hi,

Thanks for the information of DSS. I have couple of queries w.r.t DSS.

1.From limited documentation, i understood that DSS can be supported on WINDOWS/LINUX OS only. Is this correct? Will it be supported on Solaris in future release?

2. It would be appreciated if you can share the hardware resource requirements ( memory requirements/no of cores/no of CPUs etc) to set up DSS.

3. Would like to use DSS to index only database metadata but not for full text from documents. Any specific configuration/customization required to divert the DSS for only database metadata indexing ?

4. Will DSS understand normal DQL queries, Is there any specific query language defined as FTDQL defined for FAST ?

If DSS integrated with Webtop, Is it require any code changes at webtop side for simple/advance search components ?

5. Does DSS has the inteligence to convert normal DQL to XQuery and execute queries ?

Appreciate your responses.

Thanks,

Ram Reddy

Singapore

aamir

DSS is not yet released. We have just completed our beta and are preparing for the Controlled Release in June. Our goal is to GA the product in early Q4 after a successful Controlled Program.

aamir

In response to your questions, here is some additional information:

1) DSS will be only support Windows & Linux. The Content Server can still run on any supported operating system including Solaris. We, at present, do not have any plans to support DSS on Solaris. This could change if there is enough demand on other operating systems. We are trying to focus the operating systems to enhance our ability to support 6.5 SP2, 6.5 SP3 & 6.6 versions of the Content Server with the initial DSS release. Limited platforms allows us to reduce the number of platform/version combinations we have to support/test. We also tend to see more demand for Windows/Linux for the search piece of our stack.

2) Formal sizing guides for DSS are not yet available (will be during the Controlled Release). However, we do have some preliminary information that Ed Bueche will be presenting in his Momentum Session on Tuesday, May 11 entitled "Documentum Performance, Scalability & Sizing - Part 2". If you are unable to attend, I would recommend viewing his slides which will also be available.

3) Yes, you can force DSS to only index meta-data by simply marking the various document formats as not indexable in the dm_format object.

4) All current DQL syntax, including the SDC or Search Document Contains, will be supported against DSS. There are no changes required to existing client applications providing that you are not using VQL. DSS does not support VQL since it is proprietary to Verity.

5) Under the covers, DQL is automatically converted to Xquery. You do also have the option to leverage XQuery directly if you wish to use some of the advanced language features of XQuery that are not supported by DQL today.

Mohammad

Hi Amir,

Is DSS based on lucene open source search engine?

Will it be supported on Vmware and what is the recommended memory for it?

Can it be used for enterprise wide search regardless of data sources or is it restricted to Documentum

Warm Regards,

Mohammad Mazhar

XdctmX

The attached documents should answer some of your questions -

As per the attached documents

Is DSS based on lucene open source search engine?

YES

Will it be supported on VMware

VMware is supported

What is the recommended memory for it?

From the previous Post....

2) Formal sizing guides for DSS are not yet available (will be during the Controlled Release). However, we do have some preliminary information that Ed Bueche will be presenting in his Momentum Session on Tuesday, May 11 entitled "Documentum Performance, Scalability & Sizing - Part 2". If you are unable to attend, I would recommend viewing his slides which will also be available.

Gilberto_Lanzer

Hi is there any plans to certified brazilian portuguese?

Thanks

Gilberto

sahil

Aamir,

Is there synonyms/thesaurus support built into DSS. I know lucene supports it and i am hoping the answer would be Yes for DSS as well. If yes, could you provide some documentation that can talk about how easy/hard it is to configure this.

Thanks

Sahil

JorgenWortel

In the presentation I see the quote

Microsoft (FAST) will continue to support EMC Documentumcustomers using Instream4.3.1 through end of 2011

Does this mean FAST will not be supported on 6.5 SP3 after 2011?

XdctmX

2) Formal sizing guides for DSS are not yet available (will be during the Controlled Release). However, we do have some preliminary information that Ed Bueche will be presenting in his Momentum Session on Tuesday, May 11 entitled "Documentum Performance, Scalability & Sizing - Part 2". If you are unable to attend, I would recommend viewing his slides which will also be available.

Can you please share the slides or let me know where I can find them...

Tony_Chu

I have did some research on the Documentum Search service and find out the following :

Documentum DSS is developed base on two technology (at least)

1) Lucene (Open Sources from Apache)

2) Rosette Language Identifier (from Basis Technology Corp.)

Rosette Lanaguage Identifier (RLI) is used for the “language analyzer” which able to identify the Content is what language. However Rosette Language Identifier (RLI) is required License Key to enable particular language. Form out of the box Documentum Search Services have enabled the following language :

Arabic Chinese Czech Dutch

English French German Greek

Hungarian Italian Japanese Korean

Persian Polish Portugese Russian

Spanish Urdu

My Question to DSS is :

If we want to enable the other languages not listed above like "Thai", Will it be able simply to apply the License Key and modify the language-options configuration file ?

Best Regards

Tony Chu

PatriciaA

For those who remember DSS and ESS -- Documentum Search has a new name: Documentum xPlore. EMC is announcing availabililty in November. Don't miss the upcoming webinar: https://community.emc.com/message/510110#510110

aamir

Its not on a committed roadmap yet. xPlore 1.1 (part of the 6.7 release) will add support for Japanese, Korean, Spanish, Italian and French. Our hope is to add Brazilian Portuguese in our next wave of languages (possibly xPlore 1.2).

aamir

[Aamir] No, not yet. We are working on adding Synonym/Thesaurus support in xPlore in xPlore 1.2.

aamir

In the presentation I see the quote

Microsoft (FAST) will continue to support EMC Documentumcustomers using Instream4.3.1 through end of 2011

Does this mean FAST will not be supported on 6.5 SP3 after 2011?

[Aamir] Yes, this is correct. After 12/31/2011, FAST will no longer be supported on any of our product releases. FAST will also not be packaged with the 6.7 Stack.

We encourage everyone to start planning your migrations to xPlore. Additional information on what migration means is available on Powerlink (just search for 'xPlore').

aamir

I have did some research on the Documentum Search service and find out the following :

Documentum DSS is developed base on two technology (at least)

1) Lucene (Open Sources from Apache)

2) Rosette Language Identifier (from Basis Technology Corp.)

Arabic Chinese Czech Dutch

English French German Greek

Hungarian Italian Japanese Korean

Persian Polish Portugese Russian

Spanish Urdu

My Question to DSS is :

If we want to enable the other languages not listed above like "Thai", Will it be able simply to apply the License Key and modify the language-options configuration file ?

[Aamir] xPlore's underlying technology can technically support over 80 languages. However, as part of our xPlore certification effort, we are taking one langauge at a time and creating extensive test suites before claiming support. Just being able to identify and tokenize (and lemmatize) a language doesn't mean that all of the caveats of a language are handled. In addition, our efforts include extensive performance and documentation efforts.

That being said, you do not need an additional license key to enable other langauges. We just cannot guarantee the behavior. I do know that several customers have already tried languages that are not "officially" supported and they have been happy with the results.

I would encourage any customer who needs langauges that are not currently supported, to make sure your account manager, etc is aware of the requirement so that my engineering team can prioritize language certifications appropriately.