Difference between SSP and SA

Difference between SSP and SA

http://chanakyajayabalan.wordpress.com/2009/12/03/no-more-ssps-in-sharepoint-2010/

About Session

• InProc
• StateServer
• SQLServer
• Custom

 
Following link explain briefly about session
http://www.codeproject.com/KB/aspnet/ExploringSession.aspx

Object model hierarchy in sharepoint

Sharepoint Object Model Hierarchy-1.

Sharepoint Object Model Hierarchy-2

About CLSID

A CLSID is a globally unique identifier that identifies a COM class object.

Following links are realted to this:
1) http://msdn.microsoft.com/en-us/library/ms691424(VS.85).aspx
2) http://www.msdnguide.info/search/node/CLSID

Difference between Biztalk 2006 to Biztalk 2009

http://blogs.digitaldeposit.net/saravana/post/2010/03/04/Reasons-for-moving-from-BizTalk-Server-2006-to-BizTalk-Server-2009-R2.aspx

Installing BizTalk Server 2010 on WindowsServer 2008 R2 and 2008

Following link helps you

http://www.scribd.com/doc/45999258/Installing-BizTalk-Server-2010-on-Windows-Server-2008-R2-and-2008

What Are the BAM WCF and WF Interceptors

Business Activity Monitoring (BAM) is a collection of tools, APIs, and services that allow you to manage aggregations, alerts, and profiles, and to instrument automated processes to send events to monitor relevant business metrics. Together, these provide end-to-end visibility into business processes and enable you to stay abreast of business process status and results.


BAM interceptors extend this same functionality into Windows Workflow Foundation (WF), Windows Communication Foundation (WCF), and other runtime environments. By using a BAM interceptor, you can track your business processes without recompiling your WF or WCF solution—integration is done through a configuration file.

By using the BAM WF or WCF interceptor in your project, you can:

• Use the BAM portal to view information about the business processes running in your WF or WCF application.
  
• Use BAM functionality without adding additional code to your application.
  
• Deploy your solution using familiar BizTalk Server tools and utilities.
  
• Leverage your existing BizTalk Server environment for existing and new WF and WCF applications.

http://msdn.microsoft.com/en-us/library/bb245978(v=bts.70).aspx