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

extended attributes

nirjari

I want to check extended attributes and for that I want to check FieldMapping.xml file.
This file is in the location iwsearch-home\etc\FieldMapping.xml

How can I locate iwsearch-home ? I can find iw-home by iwgethome clt, how to find iwsearch-home ?

I checked root dir, but can not understand which die is iwsearch-home.

Pls provide location for iwsearch-home.

thanks

Find more posts tagged with

Comments

vpatel

I want to check extended attributes and for that I want to check FieldMapping.xml file.
This file is in the location iwsearch-home\etc\FieldMapping.xml

How can I locate iwsearch-home ? I can find iw-home by iwgethome clt, how to find iwsearch-home ?

I checked root dir, but can not understand which die is iwsearch-home.

Pls provide location for iwsearch-home.

thanks

Usually TS Search is installed on a separate box. Look at TS Search server.

nipper

Usually TS Search is installed on a separate box. Look at TS Search server.

Usually ? Not really. It is recommended that search be installed on a different server, but from my experience, that is the exception rather than the rule.

Still you need to ask whoever installed TS and search as to where it is.

vpatel

Usually ? Not really. It is recommended that search be installed on a different server, but from my experience, that is the exception rather than the rule.

Really? Even for production TS?

nipper

Really? Even for production TS?

I have done at least 10 in the past few years, all have search on the same box

Yea, I am a rebel.

jagadesh

The search can be installed in the same server(Teamsite) or in different server. it depends who is carrying installation part.

Try to use the below command
iwsrchgethome

Jamik

I have done at least 10 in the past few years, all have search on the same box

Yea, I am a rebel.

Unless you have a very beefy box, I don't think you'll be able to get away with that with the new version of TeamSite Search.

We use to have Verity K2 as our search product in house and that ran (until last year before we switched to IDOL) on a Windows 2000 server with a very low amount of resources(like 2gb of ram and two processors circa 2002), but it ran very well. When we switched over to IDOL we had to up our Search Environment to 3 servers with a lot more resources for collection storage, plus a fourth that ran the Fetches (even though we didn't change anything except switching over to IDOL from verity).

Now granted the TeamSite Search(IDOL version) is a stripped down version of IDOL, but based on my experience with IDOL I still wouldn't trust it on the TS production box.

nirjari

I think my question is sidelined.

We dont have TS Search installed on dev environment. But we have extended attributes set for DCRs. Where are these EAs set ? If FieldMapping.xml is on TS Search only, then are these EAs set on a diffrent file ? If EAs are set on FieldMapping.xml only then is there a separate location for this file ?

How can the EAs be set , if there is no Search ?

thanks

vpatel

I think my question is sidelined.

We dont have TS Search installed on dev environment. But we have extended attributes set for DCRs. Where are these EAs set ? If FieldMapping.xml is on TS Search only, then are these EAs set on a diffrent file ? If EAs are set on FieldMapping.xml only then is there a separate location for this file ?

How can the EAs be set , if there is no Search ?

thanks

You are completely confusing yourself. EAs are set on a given file itself - you can look at them by looking at File Properties in CC UI. They could be set/manipulated through:

UI (tagging UI)
Using CLTs
Using Java API
Some sort of automated script that uses the CLT / API
By the product itself
etc.

For various types of files within TS, there are various types of EAs that are set by the system. In addition there may be some custom EAs that maybe set based on the requirements. In a nutshell that talks about EAs.

Now the FieldMapping.xml file is configured so that TS Search can pickup these EAs. For example, let's say that you are tagging your DCRs with metadata (which gets stored as EAs). Let's also say that you have hundreds of DCRs relating to automobiles and for each DCR you store the make (i.e. Ford, Nissan, Lexus, GM, Chrysler, Toyota, etc.), model (i.e. F150, Camry, etc.) and year. These metadata (make, model and year) are stored as EAs. Now let's say you want the ability to search for all DCRs that are tagged for Toyota only. In order to have that ability you have to configure FieldMapping.xml file so that it'll "index" and allow you to search on these specific custom EAs that you have set.

Bottom line: EAs are file properties. FieldMapping.xml is NOT required for plain EAs only. However, if you want to configure TS Search to search on specific EAs then you'll configure it in FieldMapping.xml.

I would recommend you read the basic TS Admin guide + TS Search guide. EAs are very trivial part of TS. Perhaps if you don't know what EAs are then you shouldn't be messing around with them -- its very trivial part of the product. Also goofing up on some of the basic EAs could have negative impact that may be difficult and painful to fix especially with your EA knowledge (or lack there of).

HTH!