|
This post discusses the Service Application architecture in SharePoint 2013 and compares the key changes in architecture model with SharePoint 2010. The building model for Service Applications is same as it introduced in SP 2010.Like in SP 2010 service applications can be consumed from within the web application. |
 |
Key changes in Service Applications
- Numerous enhancements in platform level to improve the performance and for making whole model more reliable and more robust
- New Service Applications were introduced to provide more enhanced functionalities. Example Translation service application and application service management
- Office web application is no longer a service application. It is no longer comes with SharePoint and installs as a separate product.
- Web Analytics is no longer a service application – analysis and reporting processes are now incorporated in search service application and it is completely re-done.
The following are the new service applications with their own databases
Cross Farm services in SharePoint 2013
Which of the service applications can share across farms?
Any farm can publish service applications in SP 2010 and is still possible in SP 2013. You can share the service applications across farms as long as parent farm and child farm connectivity exist.
To share service application across farms – Enable publishing within service application in master farm then you can consume using service application proxy within the child farm. The architecture looks as below
The below service applications can only share across farms in SP 2013
- Business Data Connectivity
- Managed Metadata Service
- Search
- Secure Store Service
- SharePoint Translation Services
- User Profile
You can connect to the shared service applications as shown below
Deploying Service Applications
Deploying Service Applications
You can use any one of the below approaches to deploy service applications.
You can deploy service applications using initial sharepoint configuration wizard.
Deploy service applications manually or by using windows power shell.
When you deploy service applications using sharepoint configuration wizard then database names are automatically generated , including GUIDs that are long and difficult to remember. You can assign database names when you deploy using power shell.
Reference: http://technet.microsoft.com/en-us/sharepoint/fp142366
| Share this post : |  |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
