Service Applications in sharepoint 2010

TechNet defines Service applications as “a resource that can be shared across sites within a farm or, in some cases, across multiple farms.” Previously resources were shared between sites using the Shared Service Provider (SSP) model. The SSP model worked fairly well with simple deployments but little information was available for complicated distributed deployments which led to a lot of frustration. In addition, one of the big complaints was that the SSP was only available for MOSS versions and was not available for WSS. The Service Applications framework has been built directly into Foundation services which makes it available to all flavors of SharePoint.

A Modular Approach
SharePoint Server 2010 ships with services for all of the main MS Office apps, Search, User Profiles, Managed Meta-Data, Performance Point, and BCS. Not only can you define which applications are configured, but you can manage the associations so that the applications can be exposed to specific SharePoint web applications. Since it is possible to deploy the same service multiple times you can support different configurations and authentication models to support more complex deployments. In addition there are situations where you can use FAST search on some applications and regular Search on others in the same farm. There are an unlimited number of deployment possibilities.

Since the framework is open this provides real opportunities to the ISVs in areas like vertical applications in just about every area. Some of the ECM and BPM vendors have been heavily integrated with SharePoint for years so I think this can only make their offerings that much more powerful.

Another advantage to the modular approach is that it is possible to for both Microsoft and the ISVs to provide new services or service versions outside of the typical long release cycle. I’m hopeful that this will enable some of the currently evolving technologies and features to catch up.

Creating Custom List Page and Redrirecting after Update

Creating Custom List Page and Redrirecting after Update
One of my clients required a custom edit form for their editing screen where it would show certain fields and then redirect to a new page after the OK button was clicked. I had done this before at another client except i’d never found a way to actually redirect the page after the save. Here is an article on how to do that to.

1. In Sharepoint Designer take your EditForm.aspx and copy it.
2. Rename it
3. Open this new form and click on the PlaceHolderMain (leave your ListFormWebPart on the page)
4. In the ListFormWebPart scroll down the properties in the xml which describes the webpart and change to false. For some reason the form will not work unless you leave the original on the page.
4. Click on Insert->Sharepoint Controls->Custom List Form
5. Choose the appropriate List and select Edit Form
6. Sharepoint generates the form for you.

To customize the save button, find the following control on the page Sharepoint:SaveButton

1. Delete the SaveButton
2. Add

input type="button" value="Save" name="btnSave" onclick="javascript: {ddwrt:GenFireServerEvent('__commit;__redirect={}')}"

instead
3. This button allows the form to be saved and redirects to back to that page. See this article for more info

Hope it helps!

UPDATE:

If you wish to update after redirecting this is how i did it:

add in

ParameterBinding Name=”Source” Location=”QueryString(Source)”

to your paramterbindings list then add

xsl:param name=”Source”>0 /xsl:param>
xsl:variable name=”RedirectLoc”> xsl:value-of select=”$Source”/> /xsl:variable>

to your stylesheet

then the button should be:

input type=”button” value=”Save” name=”btnTopSave” onclick=”javascript: {ddwrt:GenFireServerEvent(concat(‘__commit;__redirect={‘,$RedirectLoc,’}'))}”/>