Mashing SharePoint Web Services: Example 1

Before publishing the Web Service to Presto we need to gather the following information, assuming we have a SharePoint Site

named JackBe :

• A name to uniquely identify the published Presto Service, eg. SpJackbeLists, signifying Sharepoint Service,Jackbe Site, Lists Web Service.

• The URL for the service WSDL, eg. http://www.mycompany.com/sites/MySite/_vti_bin/Lists.asmx?wsdl. 

• NT Lan Manager (NTLM) Username, password and domain.

Using Presto Service Explorer, we launch the WSDL publishing wizard and enter our details, select NTLM authentication and enter our user credentials. The screenshot below shows an example of the Service details entered in the Service Explorer 

Presto will access the service, read and validate the WSDL and prepare the Service as a Presto Published Service. If successful, the wizard will stop to allow us to configure role based access to the service as a whole and/or to individual operation, as illustrated in the screenshot below:

Having published the service, by default the service will be activated and ready to be invoked, we are now ready to use the service as a Mashable in Wires.

Note that if you try to create a Mashlet directly from the published Web Service using MashletMaker then you will probably find that when you select a Service Operation, GetList for example, MashletMaker will recommend that you virtualize the Operation using Wires becuase the Operation input parameters are complex.

Virtualization is process by which Wires is able to convert complex input parameters into one or more primitive datatype input parameters.