The solution for this problem is to pass the html content wrapped around CDATA tag.Using CDATA as wrapper around the parameter ensures that the html content is just treated as a string and does not get interpretted as markup.CDATA means character data and it can be used like this while passing markup content as parameter
<![CDATA[ your html/xml string parameter]]>.
If the parameter is say.. var x='<div>Here is my content</div>’;
Then the you need to wrap it around with CDATA before passing it to XMLHTTP request like this
SharePoint exposes web services to do data related activities.Recently came across requirement where data need to be uploaded into SharePoint lists from an environment which does not have SharePoint installed.So the object model is not available.Lists.asmx provides all list related activities to add items and read list data.Request and response are exchanged in the form of XMLs.The XMLnode avilable from the response can be used to iterate through list data using .NET classes for XML data processing.
Dataview webpart automatically pulls data from list item and saves the data back to SharePoint list.XSLT is used to format the UI as per requirement.
XSLT can be treated as just like a programming language rather than just data structure or data container like Xml.Data can be processed in the screen and data can be rendered with implementing logic like a scripting language similar to vbscript/php etc.I need to record all these findings with proper sample code and detail description.
Response from Ajax call is received by callback function which processes the data.The response is in the form of XML which can be iterated through to read the list items and individual field values(http://amitkumarmca04.blogspot.com/2008/07/how-access-sharepoint-moss-list-data.html).
Failover/High Availability is a requirement for any SharePoint based application where downtime can affect bussiness.General SharePoint farm setup involves load balanced web front end servers,application servers for central admin,search,excel service etc. and database servers.
Failover/HA can be acheived at DB level by providing clustering or mirroring.Clustering means providing multiple nodes which logically means a single server.Once the pricipal one fails then the other node becomes available.For outer world it is only one server but internally it provides options incase of a failover situation like disk crash etc.
Mirroring is similar concept but in this case the pricipal and the backup server maintain same state of data almost on real time.They share hard drive.There has to be a witness which keeps track if the pricipal server is down for certain period of time and if the dormant one needs to take its place.There are mirroring software which takes care of the whole failover scenario.
FAST ESP has become part Enterprise version of SharePoint 2010.
FAST brings in lot of new features on top of SharePoint Search.It provides previews,thumbnails,deep refinements etc.Setting up FAST search requires setting up two Search Service Applications:Content SSA and Query SSA.These work as interface between SharePoint and FAST.FAST search can be setup in SharePoint in a single server which will implement all the components or on a bigger scale which needs multiple servers dedicated to FAST search components.
FAST search needs one Admin server and one or more non Admin servers for setting up Indexers.The Index can be divided into multiple servers.This is called dividing the index into multiple columns.This makes the index update process faster and also enables to accomodate larger index.
The web crwaler extracts text out of HTML material to prepare the index.There are other components like Query Processor and Query Matching.Setting up FAST search involves deploying a deployment xml which mentions the admin and non admin servers included in the setup.It mentions the index columns.
Query SSA provides interface to the end user search queries and Content SSA provides interface to content sources like SharePoint lists,libs,BDC,Exchange,Web via connectors.
Once FAST search is enabled in SharePoint Farm,then SharePoint search becomes unavailable.
IIS offers different type of authentication mechanisms:anonymous,basic,integrated,forms,digest authentication.
Windows authentication uses either NTLM(NT LAN Manager) or Keberos as the underlying authentication mechanism for propagating user credentitial across the network for accessing resources.
Kerberos is the new technology which is replacing NTLM steadily depending types servers and domains involved.NTLM works across different types of servers like windows,linux etc.It will work in Windows server systems without active directory.
Kerberos offers features like delegation ,greater access to network resources.It provides security token from KDC(key distribution center) and it provides encryption of the password while shared between server and client.If custom service account are used as identity in the application pool hosting the application ,then the account needs to be registered with active directory as ‘Service Principal Names’.Kerberos protocol has been developed by MIT.