Hi All,
Microsoft has wiped out SSP and launched new concept Service Applications in SharePoint 2010. SSP was the most interesting and powerful concept of Microsoft Office SharePoint Server (MOSS) 2007. I am thrilled about this new feature because of its flexibility.
So what is SSP?
This is a collection of application servers that provide shared services out to any portals or sites that need them. These services include:
• Search
• Index
• Audience compilation
• User profiles database
• My Sites
• Business Data Catalogue
• Excel Services
Problem with SSP concepts:
When we create SSP, it automatically creates with all the above mentioned services which could share between many web applications. Think a scenario where web application A uses search service with same configuration with others web applications but profile/BDC configuration is totally different with others.
In the above mentioned scenario single SSP will fail to fulfil the needs. What will we do to overcome this situation?
Yes, the only option is to create new SSP and make necessary changes to the profile/BDC configuration. But in that case two SSPs need to create which are totally independent with each other’s and both SSP consist the common services apart from profile/BDC.
SSP sharing over cross farm is very difficult.
What is Service Applications?
Service applications are services that are shared across sites within a farm (for example, Search and Excel Calculation Services). Some service applications can be shared across multiple farms. Every service is working independently and at least one service is associated with Service Applications.
• Attach those services with web applications which are needed rather than entire set like SSP.
• Share services across multiple web applications within same farm
• Deploy at Application Server
• Some services can be share across multiple server farms
• Third party companies can develop services and add to the platform
Service Applications Advantage
Key advantage of the new architecture is the flexibility and addresses many of the scalability negotiation inbuilt in the SSP model.
SSP model enforce web application to use a bunch of services irrespective of utilization but in new model web application can consume individual service and any number of services or combination can be associated as per the needs.
Now services can have its own database and also deploy in a dedicated server. Service Applications are managed through Central Administration. Neither separate web application is required nor is Content Database required.
New model also allows you to deploy multiple instance of the same Service Application in a farm. Service application can be published to other farms easily.
Ref Sites:
MSDN Blog | Andrew Connell Blog | Harbar.net Articles
Microsoft has wiped out SSP and launched new concept Service Applications in SharePoint 2010. SSP was the most interesting and powerful concept of Microsoft Office SharePoint Server (MOSS) 2007. I am thrilled about this new feature because of its flexibility.
So what is SSP?
This is a collection of application servers that provide shared services out to any portals or sites that need them. These services include:
• Search
• Index
• Audience compilation
• User profiles database
• My Sites
• Business Data Catalogue
• Excel Services
Problem with SSP concepts:
When we create SSP, it automatically creates with all the above mentioned services which could share between many web applications. Think a scenario where web application A uses search service with same configuration with others web applications but profile/BDC configuration is totally different with others.
In the above mentioned scenario single SSP will fail to fulfil the needs. What will we do to overcome this situation?
Yes, the only option is to create new SSP and make necessary changes to the profile/BDC configuration. But in that case two SSPs need to create which are totally independent with each other’s and both SSP consist the common services apart from profile/BDC.
SSP sharing over cross farm is very difficult.
What is Service Applications?
Service applications are services that are shared across sites within a farm (for example, Search and Excel Calculation Services). Some service applications can be shared across multiple farms. Every service is working independently and at least one service is associated with Service Applications.
• Attach those services with web applications which are needed rather than entire set like SSP.
• Share services across multiple web applications within same farm
• Deploy at Application Server
• Some services can be share across multiple server farms
• Third party companies can develop services and add to the platform
Service Applications Advantage
Key advantage of the new architecture is the flexibility and addresses many of the scalability negotiation inbuilt in the SSP model.
SSP model enforce web application to use a bunch of services irrespective of utilization but in new model web application can consume individual service and any number of services or combination can be associated as per the needs.
Now services can have its own database and also deploy in a dedicated server. Service Applications are managed through Central Administration. Neither separate web application is required nor is Content Database required.
New model also allows you to deploy multiple instance of the same Service Application in a farm. Service application can be published to other farms easily.
Ref Sites:
MSDN Blog | Andrew Connell Blog | Harbar.net Articles
I get it clear idea about server point application review is very helpful to improve my web hosting knowledge.Above all the points are explained very clearly.hosting server
ReplyDelete