TeamSite Search

I understand that Interwoven recommends installing the new TeamSite Search bundled in 6.5 on a separate box. However, I am unable to find any recommendation one way or another. I am trying to discover costs associated with upgrading from 5.5.2 to 6.5. Does anybody know if Search can be installed on the same box (Solaris) without significant resource issues?

Any other advice about the hard costs of upgrading that I might not be considering would be appreciated as well. Thank you

Find more posts tagged with

Comments

NathansDIS

I too am curious about the upgrade path to 6.5. We are using the windows 2000 platform however. I know this has been explored before in other threads, but can someone expand on the need to use a separate server for the Search functionality? Has anyone any experience going from TS 6.1 - TS 6.5 + search? Thanks!

-Nathan
Washington DIS

Adam Stoller

FWIW - we just installed 6.5 *and* search on a Solaris 8 box with about 750 Mb of RAM - and after kicking off the search indexer the backing stores were frozed due to "low free memory" -- so it's not just a CPU issue - there's a memory issue as well.

Granted, 750 Mb of RAM is not a heck of a lot these days (this is a development box not a production box) and Unix and Windows are certainly different beasts - so your mileage will almost definitely vary - but I think it's safe to say that it's "better" / "safer" to install the search component on a separate server (we hope to do this soon)

In the brief amount of time I was able to play with it though, it was nice to be able to see it work without any significant amount of configuration contortions.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

smenon

The baseline indexing that is performed when you add a branch to be indexed for the first time is both CPU and memory intensive. This is because the index agent has to walk the TeamSite Branch and all its files and index not only the metadata but the content as well. This process is fairly CPU intensive especially if you have a large number of files and versions to index. However, once the baseline indexing has been performed, the incremental indexing is quick and you shouldn't see any signifcant load on the server unless you submit hundreds of files at once.

750 MB of RAM is very low if you consider that it has to support both TeamSite and Indexing.

--Sunil Menon
Product Manager
Interwoven, Inc.

rjoseph

Thank you Sunil. So... you are suggesting that Search can be installed on the same production server as TeamSite with little overhead once the initial indexing is complete? Frequent searches against the index and updating the index several dozen times per day should NOT affect performance of TeamSite?

Any other costs...?? I notice that Reporting Center is a separate license key. Is it a separate cost? Is there a need for additional hardware to support it?

Thank you.

-Rob Joseph

smenon

Yes - technically you can.. I would take a hard look at the TeamSite usage scenarios and the existing hardware before going down that path. It is not just a function of the frequency of submits but also the number of files you submit.

ReportCenter is a separate license key and is priced separately. You will need an RDBMS to store the reporting data and to host the Crystal Enterprise Server. Ideally this should be on a different server than the one that TeamSite is running on.

--Sunil Menon
Product Manager
Interwoven, Inc.

Ottawa_IWOV

Incremental indexing...hmmmm
I am doing an incremental update on a branch with TWO files in the STAGING area. I made a change to a file (one line text file) and submitted to STAGING. I couldn't get the file in search results (free-text, current area) for over a minute. That seems slow to me.

Is a Windows 2003 Dual CPU (3GHz a piece) with 2GB RAM hosting the Verity Index and Search services enough?

Is this incremental indexing time normal?

Thanks,

smenon

That doesn't seem normal to me. I would check to see that the branches are configured to be indexed. Also check the iw.tsindex log file in the <search-home>/log directory. You should see something like this

[05 Jan 2005 14:25:07,187] INFO com.interwoven.hunter.index.IncrementalJobProcessor (IncrementalIndexer-0) - IncrementalIndexer-0 starting indexing of branch \\ts65demo\default\main\demo
[05 Jan 2005 14:25:10,406] INFO com.interwoven.hunter.index.IncrementalJobProcessor (IncrementalIndexer-0) - IncrementalIndexer-0 completed indexing of branch \\ts65demo\default\main\demo till edition \\ts65demo\default\main\demo\EDITION\#12
[05 Jan 2005 14:25:10,406] INFO com.interwoven.hunter.index.IncrementalJobProcessor (IncrementalIndexer-0) - Files processed for branch \\ts65demo\default\main\demo is 1
[05 Jan 2005 14:25:10,437] INFO com.interwoven.hunter.index.IndexChangeNotifier (IndexChangeNotifier) - Index change notification sent to ts65demo01.interwoven.com:6720.

If you don't see the incremental index notification, then it means that the index server did not receive the notification to go and process that submit event.

What if you run the CLT - iwndxrefreshbr and force a refresh of the index on that branch? If that works, then it means that for some reason, your index manager is not picking up the event notifications from the TeamSite server.

--Sunil Menon
Product Manager
Interwoven, Inc.

skip11

Hi,

I have installed 6.5 and Search on a Solairis 8 E450 2x400mhz 2gb mem, without significate
performance issues when doing initial indexing or queries against the catalog. Initial indexing
of around 2.5gb of backing store took around 4 hours.

Our new production boxen will have 4x900mhz, and 8gb mem - that should do just fine.

Regards,

R.Barger
Credit Suisse Group
Zurich, Switzerland

Michael

Hi Sunil

You said in your post that ideally Crystal should be hosted on another server. Is it technically possible to have it on on the same server as TeamSite? (not for production use, just evaluation)

Apologies if you had answered this before -- I thought I had read about this a while back but my searches haven't turned anything up. I vaugely remember someone saying that there was some problem with a conflicting dll or some such.

Appeciate any insight you have.

Kind regards
Michael

smenon

Yes - technically it is possible to do this but it is an unsupported configuration. However, as you guessed, there is a conflicting dll (libeay32.dll) that causes issues. Ensure that all versions of libeay32.dll in your system path matches the version that ships with TeamSite and it should work. I want to point out that this configuration is not supported by Business Objects because we are replacing their dll with a different version. Hence, Interwoven cannot support this configuration for TeamSite ReportCenter too because we won't get any support for Business Objects.

thanks

--Sunil Menon
Product Manager
Interwoven, Inc.