nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Search with WEM 8.5

Dexter_Ellingson

Hello. We are upgrading from VCM/DPM 8.0 to WEM 8.5 and trying to figure out our search approach for preview and delivery sites. We currently use Autonomy IDOL and have a custom indexing process (via a listener) and query process. IDOL is no longer supported with 8.5.

We have looked at the search toolbar and results components but they do not meet all our requirements out of the box. The overrides for these components use classes in the com.vignette.ext.templating.searchcomponent package, but this package is not listed in the public javadoc API.

I am wondering what others have done for search on their preview and delivery sites with WEM 8.5. Have you customized the search components? Used the WEM search API? Used the "solrj" API directly?

Here are a few of our search requirements:

- Index only certain content types for search

- Query for content in a specific channel or any of its subchannels

- Show excerpts of static files in the "summary/description" of search results with the search keyword highlighted

- Configure weighting for content type attributes

Any thoughts are greatly appreciated.

Find more posts tagged with

Comments

Pramod_Kumar_Nookala

Hi Dexter,

The search requirements that you are asking for are doable with WEM 8.5 using the WEM Search API and Solr.

- Index only certain content types for search

This has to be done at the ContentType configuration, you can either enable/disable a CT for Indexing

- Query for content in a specific channel or any of its subchannels

The content that gets indexed will be having the Channel associations information as well, but only the channel/channels it is associated to. If you are expecting the search query to recursively search amongst its subchannels while you are searching for a parent channel associations, that is not supported OOTB. You may have to handle that in your code to recursively go through all subchannels and merge the results.

- Show excerpts of static files in the "summary/description" of search results with the search keyword highlighted

Summary displaying the excerpts of content from StaticFiles and Highlighting is not supported OOTB, but could be done using the Solr features.

- Configure weighting for content type attributes

Could be done with some tuning/settings in the config xml of solr

Thanks,

Pramod.

From: eLink Entry: Discussion Group - Web Experience Management [mailto:v7webcontentmanagement@elinkkc.opentext.com]
Sent: 26 June 2014 19:52
To: eLink Recipient
Subject: Search with WEM 8.5

Search with WEM 8.5

Posted bydexter.ellingson@securian.com (Ellingson, Dexter) On 06/26/2014 10:11 AM

We have looked at the search toolbar and results components but they do not meet all our requirements out of the box. The overrides for these components use classes in thecom.vignette.ext.templating.searchcomponent package, but this package is not listed in the public javadoc API.

I am wondering what others have done for search on their preview and delivery sites with WEM 8.5. Have you customized the search components? Used the WEM search API? Used the "solrj" API directly?

Here are a few of our search requirements:

- Index only certain content types for search

- Query for content in a specific channel or any of its subchannels

- Show excerpts of static files in the "summary/description" of search results with the search keyword highlighted

- Configure weighting for content type attributes

Any thoughts are greatly appreciated.

[To post a comment, use the normal reply function]
Forum:	Discussion Group - Web Experience Management
Content Server:	Knowledge Center

Dexter_Ellingson

Pramod, thank you for your reply. I have a few follow up questions:

1. Are there any customization/configuration points to the indexing process? In addition to indexing only certain content types, we have a requirement to not index content in certain channels.

2. Is it possible to have different search engine installations for the management stage and preview sites and still use the WEM search API? From Content Workspaces, we want all content to be indexed for search, but on preview sites (which use the content on the Management stage), we want only certain content indexed (see my question 1 above). Same restrictions apply for search from delivery sites. I am thinking taking this approach will prevent us from using the OOB indexing process and WEM API for our preview and delivery site search engine installations, but want to confirm.

Pramod_Kumar_Nookala

I am not sure I understand your requirement properly, the content showing up in content workspaces and the content that you can associate/view to/in Site/preview is the same. How would it differ when it comes to the preview. It is only possible to either mark a CT for search or not. At least that is the behavior OOTB.

It is not possible to index content based on association to channels.

Yes, a different search engine can be used between mgmt and delivery sites but OOTB WEM supports only Solr as the search engine on both stages.

You can configure any other search engine as a customsearch engine, but the implementations for indexing and querying have to be written by the user following the API provided for that.

Thanks,

Pramod.

On Jun 26, 2014, at 9:16 PM, "eLink Entry: Discussion Group - Web Experience Management" <v7webcontentmanagement@elinkkc.opentext.com> wrote:

eLink : RE Search with WEM 8.5
RE Search with WEM 8.5 Posted by dexter.ellingson@securian.com (Ellingson, Dexter) On 06/26/2014 11:43 AM

Pramod, thank you for your reply. I have a few follow up questions:1. Are there any customization/configuration points to the indexing process? In addition to indexing only certain content types, we have a requirement to not index content in certain channels.2. Is it possible to have different search engine installations for the management stage and preview sites and still use the WEM search API? From Content Workspaces, we want all content to be indexed for search, but on preview sites (which use the content on the Management stage), we want only certain content indexed (see my question 1 above). Same restrictions apply for search from delivery sites. I am thinking taking this approach will prevent us from using the OOB indexing process and WEM API for our preview and delivery site search engine installations, but want to confirm.
[To post a comment, use the normal reply function]
Topic: Search with WEM 8.5
Forum: Discussion Group - Web Experience Management
Content Server: Knowledge Center