Microsoft Content Management Server - SharePoint Connector Integration and Installation

This is Interesting: Free IT Magazines  
Home > Archive > Microsoft Content Management Server > October 2004 > SharePoint Connector Integration and Installation





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author SharePoint Connector Integration and Installation
HaloX

2004-07-15, 7:48 am

First I would like to identify that according to the
matrix provided by Microsoft in the help file provided
with the conntetor instaltion, if I want to use the
placeholder control, SPS must be installed on the same box
as MCMS. Now, I have just reviewed a webcast by Microsoft
given by Martin Harwar regarding custom stylesheets for
the Sharepoint Placeholder control. Near then the end of
the webcast a question was posed: Does MCMS and SPS have
to be on the same machine? His reply was they do NOT have
to be on the same machine. So this leaves me a bit
perplexed. I am currently working with a customer where I
have spec'ed a new MCMS installation with SPS on the same
box because of Microsofts' instruction. I would very much
prefer not to have them on the same box just for isolation
and for scalability. They want to search functionality
which I know is provided theough the SPS searhc web
service so co-existence isn't necessary.

Secondly, can I point the Sharepoint Placeholder control
to a WSS document library instead of the Sharepoint
dcoument library?


Stefan [MSFT]

2004-07-15, 7:48 am

Hi Halo,

CMS and WSS have to be on the same box. Not SPS.
See here for details:
http://download.microsoft.com/downl...6a/MCMS+2002+-+(complete)+FAQ.htm#471BC7E1-1D3B-4540-B6FB-AC10EC620E25

Cheers,
Stefan.

--
This posting is provided "AS IS" with no warranties, and confers no rights.

MCMS FAQ:
http://download.microsoft.com/downl...6a/MCMS+2002+-+(complete)+FAQ.htm
MCMS Blog: http://blogs.msdn.com/stefan_gossner/category/4983.aspx
MCMS Sample Code:
http://www.gotdotnet.com/community/...t+S
erver

MCMS Whitepapers and other docs:
http://blogs.msdn.com/stefan_gossne...2/07/41859.aspx
--------------------------------


"HaloX" <anonymous@discussions.microsoft.com> wrote in message
news:2d64201c46a64$0a652090$a401280a@phx
.gbl...
> First I would like to identify that according to the
> matrix provided by Microsoft in the help file provided
> with the conntetor instaltion, if I want to use the
> placeholder control, SPS must be installed on the same box
> as MCMS. Now, I have just reviewed a webcast by Microsoft
> given by Martin Harwar regarding custom stylesheets for
> the Sharepoint Placeholder control. Near then the end of
> the webcast a question was posed: Does MCMS and SPS have
> to be on the same machine? His reply was they do NOT have
> to be on the same machine. So this leaves me a bit
> perplexed. I am currently working with a customer where I
> have spec'ed a new MCMS installation with SPS on the same
> box because of Microsofts' instruction. I would very much
> prefer not to have them on the same box just for isolation
> and for scalability. They want to search functionality
> which I know is provided theough the SPS searhc web
> service so co-existence isn't necessary.
>
> Secondly, can I point the Sharepoint Placeholder control
> to a WSS document library instead of the Sharepoint
> dcoument library?
>
>



rdcpro

2004-10-06, 5:51 pm

I, too, am very interested in this issue. That article does not actually
state that to use SPS search, it must be on the same box as MCMS.

Is it true that to use the search functionality of the Content Connector on
a production MCMS server (ie: no authoring), I need to install SPS on the
same physical machine? Is there any use for the Content Connector for search
if they do *not* reside together?

Regards,
Mike



"Stefan [MSFT]" wrote:

> Hi Halo,
>
> CMS and WSS have to be on the same box. Not SPS.
> See here for details:
> http://download.microsoft.com/downl...6a/MCMS+2002+-+(complete)+FAQ.htm#471BC7E1-1D3B-4540-B6FB-AC10EC620E25
>
> Cheers,
> Stefan.
>
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> MCMS FAQ:
> http://download.microsoft.com/downl...6a/MCMS+2002+-+(complete)+FAQ.htm
> MCMS Blog: http://blogs.msdn.com/stefan_gossner/category/4983.aspx
> MCMS Sample Code:
> http://www.gotdotnet.com/community/...t+S
erver

> MCMS Whitepapers and other docs:
> http://blogs.msdn.com/stefan_gossne...2/07/41859.aspx
> --------------------------------
>
>
> "HaloX" <anonymous@discussions.microsoft.com> wrote in message
> news:2d64201c46a64$0a652090$a401280a@phx
.gbl...
>
>
>

Stefan [MSFT]

2004-10-07, 2:55 am

Hi Mike,

for Search SPS and MCMS can be on different boxes.
The only benefit of the Connector are then the Search Controls

Cheeers,
Stefan.

--
This posting is provided "AS IS" with no warranties, and confers no rights.

MCMS FAQ:
http://download.microsoft.com/downl...6a/MCMS+2002+-+(complete)+FAQ.htm
MCMS Blog: http://blogs.msdn.com/stefan_gossner/category/4983.aspx
MCMS Sample Code:
http://www.gotdotnet.com/community/...t+S
erver

MCMS Whitepapers and other docs:
http://blogs.msdn.com/stefan_gossne...2/07/41859.aspx
--------------------------------


"rdcpro" <rdcpro@discussions.microsoft.com> wrote in message
news:9ED513EB-393D-435F-B336-9C3F47A18A42@microsoft.com...
> I, too, am very interested in this issue. That article does not actually
> state that to use SPS search, it must be on the same box as MCMS.
>
> Is it true that to use the search functionality of the Content Connector

on
> a production MCMS server (ie: no authoring), I need to install SPS on the
> same physical machine? Is there any use for the Content Connector for

search[vbcol=seagreen]
> if they do *not* reside together?
>
> Regards,
> Mike
>
>
>
> "Stefan [MSFT]" wrote:
>
http://download.microsoft.com/downl...6a/MCMS+2002+-+(complete)+FAQ.htm#471BC7E1-1D3B-4540-B6FB-AC10EC620E25[vbcol=seagreen]
rights.[vbcol=seagreen]
http://download.microsoft.com/downl...6a/MCMS+2002+-+(complete)+FAQ.htm[vbcol=seagreen]
http://www.gotdotnet.com/community/...t+S
erver
[vbcol=seagreen]


AC

2004-10-07, 11:20 am

Mike-

You have other options. I didn't use the component that came with the
connector for a few reasons:
> you can't customize the output
> you can't search on specific source groups


Those were the two main reasons... I wanted more customization. So I build
my own utilizing the search.asmx web service (the same *i think* the search
component that comes with the connector uses). Read more about it via the
link below... also links to other people's implementations of the same.
While I wrote it for an ASP.NET app, it works perfectly for a MCMS site as
well.

Using SharePoint search in an ASP.NET application with noise filtering
http://andrewconnell.com/blog/archi.../07/15/406.aspx

-AC

"rdcpro" <rdcpro@discussions.microsoft.com> wrote in message
news:9ED513EB-393D-435F-B336-9C3F47A18A42@microsoft.com...[vbcol=seagreen]
> I, too, am very interested in this issue. That article does not actually
> state that to use SPS search, it must be on the same box as MCMS.
>
> Is it true that to use the search functionality of the Content Connector
> on
> a production MCMS server (ie: no authoring), I need to install SPS on the
> same physical machine? Is there any use for the Content Connector for
> search
> if they do *not* reside together?
>
> Regards,
> Mike
>
>
>
> "Stefan [MSFT]" wrote:
>


rdcpro

2004-10-07, 8:46 pm

Very nice and concise outline--thanks Angus!

I'm thinking the same approach would work for the major search engines as
well. I've got a short list of user agents from major crawlers...

We have lots of aggregating/rollup content in a right side column, in
addition to our navigation. Up till now we've been using Site Server for
searching. We built a search stager and produce a "searchable content" meta
tag...it will be very nice to get rid of that stuff!

Regards,
Mike

"Angus Logan [MVP]" wrote:

> From the MCMS 2002 Connector for SharePoint Technologies documentation see
> /Planning, Architecture & technology overview
> /Plannign for deployment
> /computer configuration
>
> (or if it comes through the picture below)
>
>
> You can also manually code your own sharepoint search; see my brain dump of
> how I did it with a few links to other articles:
> http://msmvps.com/anguslogan/archiv...0/03/14833.aspx
>
> --
> ________________________________________

>
> Angus Logan (MCAD/MCDBA/MCP/MVP for MCMS)
> Product Specialist
> Microsoft Application Solutions
> Data#3 Limited
> E angus_logan@data3.com.au
> BLOG www.anguslogan.com
> ________________________________________

>
> "rdcpro" <rdcpro@discussions.microsoft.com> wrote in message
> news:9ED513EB-393D-435F-B336-9C3F47A18A42@microsoft.com...
> on
> search
> http://download.microsoft.com/downl...6a/MCMS+2002+-+(complete)+FAQ.htm#471BC7E1-1D3B-4540-B6FB-AC10EC620E25
> rights.
> http://download.microsoft.com/downl...6a/MCMS+2002+-+(complete)+FAQ.htm
> http://www.gotdotnet.com/community/...t+S
erver

>
>
>

rdcpro

2004-10-07, 8:46 pm

Thanks Stefan.

While we'll be deploying this inside the firewall for the authoring server,
we're not quite ready to integrate our internal portal, so my main focus for
this project is replacing Site Server's search engine with the SPS search
engine and in our DMZ as well.

One followup--does the SearchSearchMetaTagGenerator control only emit the
meta tags when SPS is crawling, or does it emit the metatags for any user
agent? Is this configurable through a property? IOW, something like:

<cmssps:SearchSearchMetaTagGenerator id="SearchMetaTagGenerator1"
runat="server" user-agents="googlebot, msnbot, ms search">


Thanks again,
Mike

"Stefan [MSFT]" wrote:

> Hi Mike,
>
> for Search SPS and MCMS can be on different boxes.
> The only benefit of the Connector are then the Search Controls
>
> Cheeers,
> Stefan.
>
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> MCMS FAQ:
> http://download.microsoft.com/downl...6a/MCMS+2002+-+(complete)+FAQ.htm
> MCMS Blog: http://blogs.msdn.com/stefan_gossner/category/4983.aspx
> MCMS Sample Code:
> http://www.gotdotnet.com/community/...t+S
erver

> MCMS Whitepapers and other docs:
> http://blogs.msdn.com/stefan_gossne...2/07/41859.aspx
> --------------------------------
>
>
> "rdcpro" <rdcpro@discussions.microsoft.com> wrote in message
> news:9ED513EB-393D-435F-B336-9C3F47A18A42@microsoft.com...
> on
> search
> http://download.microsoft.com/downl...6a/MCMS+2002+-+(complete)+FAQ.htm#471BC7E1-1D3B-4540-B6FB-AC10EC620E25
> rights.
> http://download.microsoft.com/downl...6a/MCMS+2002+-+(complete)+FAQ.htm
> http://www.gotdotnet.com/community/...t+S
erver

>
>
>

rdcpro

2004-10-07, 8:46 pm

Thanks Andrew--I actually found your article earlier yesterday, and was
coming to the same conclusions. We already implement noise filtering (using
Site Server for searching), and that's a feature I wanted to keep, and in
fact expand upon. Very useful info. Thanks.

Regards,
Mike


"AC" wrote:

> Mike-
>
> You have other options. I didn't use the component that came with the
> connector for a few reasons:
>
> Those were the two main reasons... I wanted more customization. So I build
> my own utilizing the search.asmx web service (the same *i think* the search
> component that comes with the connector uses). Read more about it via the
> link below... also links to other people's implementations of the same.
> While I wrote it for an ASP.NET app, it works perfectly for a MCMS site as
> well.
>
> Using SharePoint search in an ASP.NET application with noise filtering
> http://andrewconnell.com/blog/archi.../07/15/406.aspx
>
> -AC
>
> "rdcpro" <rdcpro@discussions.microsoft.com> wrote in message
> news:9ED513EB-393D-435F-B336-9C3F47A18A42@microsoft.com...
>
>
>

Stefan [MSFT]

2004-10-08, 7:47 am

Hi Mike,

this control emits the content for every user agent.

Cheers,
Stefan.

--
This posting is provided "AS IS" with no warranties, and confers no rights.

MCMS FAQ:
http://download.microsoft.com/downl...6a/MCMS+2002+-+(complete)+FAQ.htm
MCMS Blog: http://blogs.msdn.com/stefan_gossner/category/4983.aspx
MCMS Sample Code:
http://www.gotdotnet.com/community/...t+S
erver

MCMS Whitepapers and other docs:
http://blogs.msdn.com/stefan_gossne...2/07/41859.aspx
--------------------------------


"rdcpro" <rdcpro@discussions.microsoft.com> wrote in message
news:0E8B8179-F670-4CD0-81F5-02ED28D68028@microsoft.com...
> Thanks Stefan.
>
> While we'll be deploying this inside the firewall for the authoring

server,
> we're not quite ready to integrate our internal portal, so my main focus

for[vbcol=seagreen]
> this project is replacing Site Server's search engine with the SPS search
> engine and in our DMZ as well.
>
> One followup--does the SearchSearchMetaTagGenerator control only emit the
> meta tags when SPS is crawling, or does it emit the metatags for any user
> agent? Is this configurable through a property? IOW, something like:
>
> <cmssps:SearchSearchMetaTagGenerator id="SearchMetaTagGenerator1"
> runat="server" user-agents="googlebot, msnbot, ms search">
>
>
> Thanks again,
> Mike
>
> "Stefan [MSFT]" wrote:
>
rights.[vbcol=seagreen]
http://download.microsoft.com/downl...6a/MCMS+2002+-+(complete)+FAQ.htm[vbcol=seagreen]
http://www.gotdotnet.com/community/...t+S
erver
[vbcol=seagreen]
actually[vbcol=seagreen]
Connector[vbcol=seagreen]
the[vbcol=seagreen]
http://download.microsoft.com/downl...6a/MCMS+2002+-+(complete)+FAQ.htm#471BC7E1-1D3B-4540-B6FB-AC10EC620E25[vbcol=seagreen]
http://download.microsoft.com/downl...6a/MCMS+2002+-+(complete)+FAQ.htm[vbcol=seagreen]
http://www.gotdotnet.com/community/...t+S
erver
[vbcol=seagreen]


Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com