Vesa Juvonen Principal Consultant Microsoft Services can be individually consumed from any Web Application Allows for a very rich and complex farm structure if required Provide flexibility to utilize services based on application needs ID: 674242
Download Presentation The PPT/PDF document "Services application architecture in SP..." is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.
Slide1
Services application architecture in SP2013
Vesa Juvonen
Principal Consultant
MicrosoftSlide2
Services can be individually consumed from any Web Application
Allows for a very rich (and complex) farm structure if required
Provide flexibility to utilize services based on application needs
Same services architecture as introduced in 2010 Slide3
General architecture identical as in SharePoint 2010
Numerous new enhancements in platform level
New service applications to provide more enhanced functionalities
Office Web Apps is no longer a service applicationSeparated to own product for easier maintenance and operations
Web Analytics is no longer service application
Analyses and reporting process incorporated to search service application
Key changes in service applicationsSlide4
Service Databases
Service
Applications with their own DBs:
App Management Service
Business Data Connectivity
Managed Metadata Service
Search
Secure Store Service
Machine Translation ServiceState ServiceUsage and Health Data CollectionUser ProfileWord Automation ServiceAccess Services App databasesSlide5
Cross farm services in SharePoint 2013
Remote farms don’t need perms to parent
farm DBs*
Any farm can publish SAs
One web application can use both local
and remote SAs
Enables centralized “enterprise” SAs
Support only in specific service applications
Business Data ConnectivityManaged Metadata ServiceSearchSecure Store ServiceMachine Translation ServicesUser ProfileSlide6
Service Applications and WAN environments
Service application
Allowed
for WAN
environments?
Hybrid with Office365
Search
Managed Metadata
Machine Translation Service
Business Data Connectivity
User Profile
Secure Store ServiceSlide7
SharePoint 2010 farms can consume
some services from SharePoint 2013
farms
Other way around is not supportedUseful for upgrade processSupported services are
Search
No FAST consuming from 2010
User Profile
Secure Store
Managed MetadataBCSCross farm services cross major versionsSlide8
Applying software updates in multi-farm environments
Update Service(s) farms always first
Recommended order
Service farm(s)My site farm
Content farms
Connected farms running previous version of the software can consume newer services
Office
Web Apps farm can be updated independently of the SharePoint farms.Slide9
Deploying Service Applications
Deploying service applications by using the Initial Configuration Wizard
Deploying service applications manually or by using Windows PowerShell
Application pool
All service applications are deployed to the same application pool.
You can deploy service applications to dedicated application pools, if desired.
Service accounts
The same account is used for all services. You can edit service accounts later.
You can apply different service accounts to service applications.
Databases
Database names are automatically generated, including GUIDs that are long and difficult to remember.
You can assign database names and implement a naming convention.
Service application settings
Default settings are applied to service applications. You can change these later.
You can implement custom settings when the service application is deployed.
Note. Wizard is not recommended for production usageSlide10
Demo
Walkthrough for administration of service applications in SharePoint 2013Slide11
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.