Logo 
Search:

Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

What is "service virtualization" as used in the MSDN WSS custom web services white paper?

  Asked By: Marilyn    Date: May 18    Category: Sharepoint    Views: 1116

In
msdn.microsoft.com/.../odc_sp2
003_
ta/html/odc_writingcustomwebservicesforsppt.asp, "Writing Custom Web
Services for SharePoint Products and Technologies", this white paper
uses
the term "service virtualization" in several places:

1. Modify the .disco and .wsdl files to support service virtualization.

2. To modify the Service1disco.aspx file and the Service1wsdl.aspx file
to
support service virtualization.

3. This Web service uses service virtualization to determine the site
context, and then uploads the document to the Shared Documents document
library folder.


The term doesn't appear anywhere else on the Internet (except for a few
SOA
references), no where in MSDN and no where in the WSS SDK.


What exactly are the authors
refering to when they usee the term "service virtualization"?

Share: 

 

8 Answers Found

 
Answer #1    Answered By: Faith Delgado     Answered On: May 18

I presume that they mean that the service  can be discovered externally.
However, I'm not familiar with the term  either.

I do have a contention with their supposition that the Web Service must
be running on a different port. I would swear that I've created custom
SharePoint Web services  that run on the same port (80) but under a
different host header.

If I'm wrong (and I could be here), any idea why the need for a unique
port when a unique host header or a unique IP address (post SP2 of
course) should suffice?

 
Answer #2    Answered By: Amrita Durgude     Answered On: May 18

... Anyways Service Virtualization meaning to be able to call
from any Sharepoint web  url (kinda like all the _layouts pages)

 
Answer #3    Answered By: Maricela Conway     Answered On: May 18

one of the SharePoint PMs, responded personally (see below).

 
Answer #4    Answered By: Vinay Thakur     Answered On: May 18

I've created custom  SharePoint web  Services that run on the same
port (80) but under a different host header.

I generally agree with your comment. I've always thought of using
different ports vs. host headers as somewhat interchangeable. ...i.e.
whatever it takes to get IIS to map an incoming request to a virtual
directory (IIS web site). 85%certainty.

 
Answer #5    Answered By: Shameka Rich     Answered On: May 18

I think that I understand and that is more or less what I meant by the
"service can be discovered externally".

But just to be sure, by adding the appropriate information to the .disco
and .wsdl files, the Web service  can be deployed to just one of the Web
front ends and the other Web servers in the sharepoint  farm will
discover and use it. Is that correct?

I always thought that you had to deploy a custom  Web Service equally to
all Web servers in the farm. So, this is good news. The remaining
question is: What is the appropriate information to put into the .disco
and .wsdl files?

 
Answer #6    Answered By: Royce Orr     Answered On: May 18

Checkout

msdn.microsoft.com/.../odc_sp2003_
ta/html/odc_writingcustomwebservicesforsppt.asp for the details. ...and it
just occured to me how the wp solution works.

In the section of the wp, "To create and edit a .disco file  and a wsdl",
they have you turn the .disco and .wsdl into ASP.NET pages ...and hence,
turn them into "dynamic" disco and wsdl  files.

Checkout the white  paper.

 
Answer #7    Answered By: Laura Walker     Answered On: May 18

"I always thought that you
had to deploy a custom  Web service  equally to all web  servers in the farm.
So, this is good news": (short answer: The physical files  need to be
deployed to all the servers in the farm though (manually))

-----

nope this does not relate to files being automatically deployed to all the
servers in the form but just like how the layouts page (are deployed to all
the servers in the fram and can be called from any site URL

for ex: one page at can be called from :

http://localhost/1033/_layouts/settings.aspx;

http://localhost/sites/site1/1033/_layouts/settings.aspx;

http://localhost/sites/sites1/web1/1033/_layouts/settings.aspx;

similarly for your web service you should be able add reference from any of
the site locations. (and use the Context.GetSite() calls in your code to
find out which site were you called from)

The physical files need to be deployed to all the servers in the farm though
(manually)

 
Answer #8    Answered By: Nina Banks     Answered On: May 18

Read several of the messages below for the answer to my original posting.

 




Tagged: