KM Search iView Question

[Former Member]

Hello all,

I've been having a look at the KM Search iView.

I created an iView of type com.sap.km.cm.basicsearch, had a look and it's all fine. I created a Search Options Set based on the basic UISearch search options set, limited it to search over only one index and removed the option for the user to see the 'Advanced Search' options. The problem with this iView type is that the results are displayed in the same window and not in a popup.

In this thread /community [original link is broken]=19072 John says to "create from com.sap.portal.navigation.toolarea.default and hide the collaboration links on property editor". I did that, hid all of the options that I didn't want the user to see; leaving only the search function.

And finaly to my problem. From this iView that I've created I can't see how to set the Search Options Set to the one that I created, which searches only the single index.

Using com.sap.portal.navigation.toolarea.default to give me a search function that opens the results in a popup can I set the Search Options Set (and of course, if so then how)?

Thanks in advance and regards,

Patrick.

[Former Member · Accepted solution]

Hi Patrick,

1)

Your iview will have the following parameters

"Search Component Set" , "Search Options Set" and "Search Result LayoutSet" - Give your own created component and the option set values here.

2)

There is a property of iview which enables you to select display it in a new window or in the same window.

"Launch in a New Window"

3)

If you are using the default toolarea search function then in the toolarea iview there are two parameters

1)KM Search Advanced Parameters

2)KM Search Parameters

- add the following parameters to both the existing parameter values "&SearchPluginName=<SearchOptionSetName>&SearchComponentName=<SearchComponentSetname>&rndLayoutSet=<CustomLayoutSet>"

[Former Member · Accepted solution]

Hi Prakash, thanks for the response.

It's your number 3) that interests me here.

I saw those parameters earlier and at a guess I tried to add "&SearchOptionsSet=<SearchOptionsSetName>" to them but it didn't work.

I see that you named the parameter "&SearchPluginName=<SearchOptionSetName>". I gave it a try and it didn't work for me. Perhaps the parameter name should be different? I'm using EP6 on NW04 SP11.

Thanks so far,

Patrick.

[Former Member · Accepted solution]

Hi again Prakash, I've done a little more research here.

I found the same info that you gave me here, http://help.sap.com/saphelp_nw04/helpdata/en/54/9d953fc405330ee10000000a114084/frameset.htm it's a good resource and explains a lot.

When I 'Preview' my search iView with the parameter "SearchPluginName=<SearchOptionsSetName>" like you gave me, it works. It only returns documents indexed by the index in my SearchOptionsSet.

However, when I add this search iView to a page and use it, it returns all documents indexed by all indexes, so does not use the SearchOptionsSet that I've declared in the "SearchPluginName=" parameter.

Do you have any idea why this would be?

Regards,

Patrick.

[Former Member · Accepted solution]

Hi,

I am also using the them in the same way.Below is what i am giving for the parameter "query" for my custom search UI in the tool area

For advanced search

StartPage=SearchPage&ConfigFileName=Navigation.xml&layoutSetMode=exclusive&ResourceListType=com.sapportals.wcm.SearchResultList&SearchType=quick&Advanced=true&SearchPluginName=MyCommonUISearch&SearchCompsName=MyCommonUISearchComponents&rndLayoutSet=MyCommonSearchResultLayoutSet&QueryString=

For Basic search

StartPage=SearchPage&ConfigFileName=Navigation.xml&layoutSetMode=exclusive&ResourceListType=com.sapportals.wcm.SearchResultList&SearchType=quick&SearchPluginName=MyCommonUISearch&SearchCompsName=MyCommonUISearchComponents&rndLayoutSet=MyCommonSearchResultLayoutSet&QueryString=

Regards

Prakash

[Former Member · Accepted solution]

Hi Patrick,

I dont have any idea. I will check and let you know.

Regards

Prakash

[Former Member · Accepted solution]

:oops:

It was a local cache problem.

I emptied the cache and now it works as it should.

Thanks for all of your help Prakash.

Regards,

Patrick.