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; } } }

Configuring 6.5 Search

Ottawa_IWOV

All-

I did a clean install of TeamSite 6.5 (on server A) and TeamSite Search (on server

When I try and perform Actions > Search, I get the following 'Connection Refused' Java stack errors. So I assume something is wrong with my connection settings.

I looked around on DevNet, and noticed a post regarding the cssdk.cfg file, and updating:

search.server.host:
search.server.port:

Which I did. Reset the servlet engine, and stil I get nothing. Everything also seems fine in search.properties on the search server (atleast to my knowledge).

I basically did a vanilla default install (followed the TeamSite documentation). I am at a loss on this one.

Any guidance on this would be great!

Thanks,

Find more posts tagged with

Comments

Migrateduser

Two things to try:

1. Can you actually access server B from server A directly?

2. If yes, on server B, try issuing the iwndxmgrstatus and the iwsrchmgrping CLTs to actually see if the index and search manager are up. Any interesting messages in the search or index server log?

Regards
--Anirudha

Ottawa_IWOV

Can ping server B from server A no problem.

Here are the resullts from the CLT's:

iwndxmgrstatus
ACTIVE.

iwsrchmgrping
The response time for search server is: 0 ms

Nothing too interesting in the log file. Nothing that looks even remotely like an error ...

Ottawa_IWOV

My Lord, the documentation for Search is horrendous. I mean come on ... I have a couple of questions:

-I assume FieldMapping.xml needs to be set-up before a branch set-up for indexing.
-Can FieldMapping.xml be specific to a certain branch
-Is there a CLT for stop and starting the index and search services. I only see something for bringing them down ...

Thoughts?

reddyl

Stop index and search services using iwndxmgrstop iwsrchmgrstop.

Ottawa_IWOV

How do I re-start them?

skip11

Hi,

/etc/init.d/iw.tsindex start
/etc/init.d/iw.tssearch start

note: always start the index sever first if implementing log rotation which bounces both
services.

Regards,

R.Barger
Credit Suisse Group
Zurich, Switzerland

Edited by skip on 01/06/05 02:25 AM (server time).

bturns

FieldMapping.xml does not need to be set up. There is a default one that is used. If you would like to search custom EA's or Templates then FieldMapping.xml will have to be configured.

I have not seen any documentation that suggests that FieldMapping can be set up on a perbranch basis. It seems to be a system wide configuration. This could get annoying if you've got hundreds of templates and EA's across your enterprise.

kajjubee

I am having the same issue, "connection refused" error in my java stack when i click on search.Did you get it resolved? I have configured Fieldmapping.xml & also branches.cfg. I am able to ping the search server (Machine

from the teamSite server (Machine A). Also I have ensured that the ports of search server & index servers are accessible from my TeamSite server. I do see that the shared file system is growing since. So i am assuming I need to allow the indexing to finish before I search... Any expert comments here? ...

Thanks
K

kajjubee

It works for me now as I modified the cssdk.cfg file with the search server name & port.

cheers!
K

KrisK

I am trying to configure Search on our Solaris server. I want to be able to search our custom Metadata attributes. The admin guide doesn't have much info on this. Anyone has done this before? Do I need a database? During the install, I wasn't prompted for one.

Thanks

Ottawa_IWOV

FieldMapping.xml, look at the example provided in iw-seach-home/etc

KrisK

I configured it. What else do I have to do? When I search for these custom metadata attributes, always I get 0 results. I restarted the index and search.

Thanks

smenon

When did you index the file ? After you configured your FieldMapping.xml do you know if you re-indexed the content? Note : the only way to re-index previously indexed content is to modify and submit - or delete the collection and re-index.

I want to highlight the importance of planning which fields you want to index and make available for search up front before you actually index the content. This will avoid having to re-index your content because you decided to change the fields you want to index.

thanks

--Sunil Menon
Product Manager
Interwoven, Inc.

KrisK

I touched all the files in my workarea and submitted them after I updated the FieldMapping.xml. I also deleted the collection and re-indexed. I am still unable to search onthe custom metadata attributes.

Thanks