RE: XML iFilter needed for SPS 2003 infopath forms?
- From: Bob C. <BobC@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 28 Apr 2006 14:03:02 -0700
And, the key is at:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SPSSearch\ContentIndexCommon\Filters\Extension\.xml
"Bob C." wrote:
FYI, on SPPS on Windows server 2003, the filter exists (a newer version.
seems) at:
C:\Program Files\SharePoint Portal Server\bin
"allison" wrote:
Finally I can answer Yes! This is a bit long but hopefully will help someone
else.
After getting a confirmation by the SPS product team that the xml iFilter
did in fact need to be installed on the Sharepoint server, I tried again.
Apparently the claim that SP indexes xml files is not quite specific enough.
It must use a default text Filter not a true xml ifilter. I think that was
why I was able to get search results on the text in the InfoPath documents
but not use the properties/attributes from the xml for advanced searching.
Anyway these are the steps I combined from several sources, none of which
was really specific to SPS 2003 so I had worked it out by trial and
error...lots of error and apologize to anyone I may plagiarize here.
Especially rdcpro who worked thru an html custom metadata issue I found here
http://groups.google.com/group/microsoft.public.sharepoint.portalserver/browse_frm/thread/6af5a60950a0d50d/add48c678ff5a3bd?lnk=st&q=Search+on+Numeric+property+on+Sharepoint+2003&rnum=1#add48c678ff5a3bd in an html
Still I have many unanswered questions, have found very little 2003
documentation on crawling Metadata, mapping properties (when, why, and which
way) and am really loved this MSDN Tech article 'Integrating Microsoft
SharePoint Products and Technologies and Microsoft Office InfoPath 2003'
which left me short as a search administrator...'Yes you can do it' but
nothing more.
I believe MS should step up to the plate with a better in-depth
documentation on administering search in 2003 (not customizing with code)
because much of the information in ‘Crawling Custom Metadata with SharePoint
Portal Server’ does not apply but lots of resources still lead to that
document from 2001.
http://www.microsoft.com/sharepoint/server/techinfo/development/metadata.asp
With that rant over here are the steps I finally worked out:
Download the filter (or any xml iFilter should wrk) and verify the pre-reqs.
http://www.microsoft.com/sharepoint/server/techinfo/reskit/XML_Filter.asp
Install the XML content filter for SharePoint Portal Server:
1. Set up SharePoint Portal Server to use the XML content filter for XML
documents.
a. Copy xmlfilter.dll to a directory on a local hard drive.
b. Run regsvr32 xmlfilter.dll.
c. Run RegEdit.exe.
d. Go to
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ContentIndexCommon\Filters\Extention.
e. Delete .xml.
f. Restart the Microsoft Search (MSSearch) service.
2. Go to "Manage Properties of Crawled Content", and delete all the
properties under
urn:schemas.microsoft.com:fulltextqueryinfo:xmlfilter:'schema namespace'
that you are trying to process and also under
urn:schemas-microsoft-com:office:office you need to delete the specific
ows_'InfopathPropertyName' that you want to add to your
Advanced Search.
3. Reset all content indexes.
4. Restart the Microsoft SharePointPS Search service.
5. Initiate a Full Update of all content indexes that contain the
properties. (This rebuilt only one list of properties under
urn:schemas.microsoft.com:fulltextqueryinfo:xmlfilter in my case.)
6. Go to "Manage Properties of Crawled Content", locate the
ows_'InfopathPropertyName' in the
urn:schemas-microsoft-com:office:officenamespace, and check the option,
"Included in the Advanced Search options", which exposes the
meta property to the Sharepoint Search Service. (At this point it still did
not have documents listed under 'Content Using this
Property')
7. Initiate another Full Update of all content indexes. (Now when you should
see documents associated to the ows_ property)
8. After the last update you will be able to select the properties on the
Advanced Search page and find documents using the appropriate
criteria. (Leave the Search by Type' set to Any Type).
--
Allison :)
"Bob C." wrote:
Allison,
Have you got Infopath docs to come up in a search?
Background:
IP2003 sp2, SPPSsp2 on W2003sp1 .
My IP form sets doc lib properties when submitted. Those properties are
defined from the IP Form Options/Form Lib Columns tab. When the form is
published, those cols are added to the form lib All Items view. This all
works fine.
When I review the properties on the
http://portal.me.com/_layouts/1033/Properties.aspx and found that those IP
properties show up under urn:schemas-microsoft-com:office:office, both as
ows_propertyname and ows_xd_someguid_abc1230x...
When I click on any of my custom IP properties in either section to the Edit
Property page, Content Using this Property is blank, even though I have tens
of IP docs using those properties...
Hmmmmm Any thoughs are appreciated.
"allison" wrote:
We are attempting to index infopath forms loaded in a SPS 2003 document
library and search on 2 of the metadata properties. I suspect that I need to
install an xml iFilter on the SQL Server but cannot find a definitive answer.
Everything directs me to the SPS 2001 iFilter at
http://www.microsoft.com/sharepoint/server/techinfo/reskit/XML_Filter.asp .
Is this needed for 2003 or not?
Can anyone answer for sure if Sharepoint 2003 install includes an xml
iFilter and if so then does it also need to be installed on the SQL Server
box? This is on a medium (3 server) farm configuration.
Thanks,
--
Allison
- References:
- RE: XML iFilter needed for SPS 2003 infopath forms?
- From: allison
- RE: XML iFilter needed for SPS 2003 infopath forms?
- From: Bob C.
- RE: XML iFilter needed for SPS 2003 infopath forms?
- Prev by Date: RE: XML iFilter needed for SPS 2003 infopath forms?
- Next by Date: How to disable full-text indexing in SPS 2003 ?
- Previous by thread: RE: XML iFilter needed for SPS 2003 infopath forms?
- Next by thread: How to share aspx files?
- Index(es):
Relevant Pages
|
