sharepoint 2013 work management service deep dive
DESCRIPTION
Where do you keep track of all your tasks? Outlook? SharePoint? Maybe Project Server? Storing them across multiple applications is a pure Information Worker challenge. SharePoint 2013 has the new Work Management Service Application to solve these issues. It aggregates tasks across SharePoint, Exchange, Project Server and there's even a story for TFS. There's not that much documentation out there on how to configure it, how to maintain and work with it. In this session I will walk through the architecture and setup, and go over how it operates and what you need to know to keep it alive. I will demonstrate the features and discuss all of the technical aspects.TRANSCRIPT
SharePoint 2013 Work Management Service Deep DiveRadi AtanassovSharePoint MCM & MVPOneBit Software
SharePoint MCSM
SharePoint Server MVP
OneBit Software
Web Platform User Group
C:\Users\Radi>whoami
What is the Work Management Service Application for?
What is the architecture and how does it work
High-Trust / S2S Authentication Provisioning & Configuration Demo
Agenda
Get an understanding of what the Work Management Service Application does and how it operates internally
Learn how to configure an environment for task synchronisation
Demonstrate enough resources to get you going
Show you something not shown at #SPC12
Session Goals
Aggregates “tasks” between SharePoint, Exchange and Project Server
Solves the problem of disconnected “task” lists in multiple places & across applications
What is the Work Management Service App all about?
Productivity Benefits One location to manage tasks
Synced with Outlook (Exchange)
Nice views and timeline
Task Search Grouped by Project
My Tasks
Very quick demo
Task Storage
My Sites
SharePoint Task Lists
Project Server2013
Exchange Server2013
Personal Site
Work Management Service Architecture
List on Personal Site
Project Server DB
SP Content DBSP Web App
Change Log
Work Management
Service
Write personal tasks
Read personal tasks
Refresh request
Change tasks in
to
list
Call as Proj server user mapped to SP User
Call as SP UserGet Tasks via OM
1 2
3
45
6
7
My Tasks
* Taken from the Ignite training material, credits to Vesa Juvonen and Chris Gideon
Supported Tasks• The following Content Types:
• TasksWithTimelineAndHierarchy-171 (SP2013 Task)• Task-107 (SP2010 Task)• GanttTasks-150 (SP2010 Task)
Note: The Task content type should be marked as the Default Content Type for your custom list in order for the tasks to be aggregated by the service.
WMA gets Task List locations from Search (by default cached for 3 hours per user)
Ignores if outside of the farm Lack of frequent crawling can delay
discovery Locations are cached and used in the next
refresh Event handlers create hints
$w=Get-SPWeb “http://mysites/my/personal/radi” $w.Properties["wmahint"]
Dependency on Search
Relies on Timer Job “Work Management synchronize with Exchange” Performs “work” every 1 minute No guarantee that you will see an update, cache is per user
SharePoint calls Exchange One-way trust needed
Required S2S authentication and people hate configuring this
Sync with Exchange
Requires “opting-in”…
Gotcha!
Opt-in from any Task List and PWA
What gets synced?Outlook Property
MY TASKS property
SharePoint property
Project property Notes
Subject Title Title Name
Due Date Due Date Due Date Finish Date
Body Description Description n/a
Status Completed Checkbox
n/a n/a This works in parallel with % Complete property
Folder name Group name List name Project name
Start Date n/a Start Date Start Date
Importance Pinned Date n/a n/a
Total Work Total Work n/a Total Work
Actual Work Actual Work n/a Actual Work
% Complete % complete % complete % complete This works in parallel with the Status property. Set to 100 when task is marked as complete. Set to 0, when unmarked.
SharePoint, Project and Exchange are providers
Caching and refreshing is per provider Technically, you can create your own
providers Not documented. Not supported. See Adis Jugo’s blog in the references using Microsoft.Office.Server.WorkManagement; using Microsoft.Office.Server.WorkManagement.ProviderOM; using Microsoft.Office.Server.WorkManagement.Providers;
Based on a provider model
What is Server-to-Server (S2S) authentication? Also called “High Trust” A configuration of trust between an
application and SharePoint Designed to facilitate on-premises
authentication Example: SharePoint, Workflow and
Exchange communicate with each other over S2S
No need for ACS in on-premises deployments
S2S requires certificates
1
2
43
SharePoint Web Server
User
App
S2S STS
SSL Cert Public/Private key pair (.pfx)
Work Management Service ApplicationConfiguration
Configuration - prerequisites Exchange Server 2013 SharePoint 2013 with:
User Profile Service Application – with a profile Work Management Service Application Claims Web Application with SSL Installed Exchange Web Services API on SP servers Search (to aggregate SP tasks) Project Server (for aggregation of Project tasks)
Cross-farm is not supported
Configuration – user interfaces My Site Host over SSL
https://va-dev-01:3000
A SharePoint Project Site https://va-dev-01
Project Web App https://va-dev-01/PWA
Outlook Web App https://va-exc-01/owa
Configuration – User Profiles You just need profiles in there for
S2S, but you need My Sites for the “My Tasks” list
Can use the new (old) AD Import You must give access to the My Site
Host web application pool service account
Configuration – WM Service Application Central Administration
No interface for settings!!
PowerShell New-SPWorkManagementServiceApplication New-SPWorkManagementServiceApplicationProxy Set-SPWorkManagementServiceApplication Set-SPWorkManagementServiceApplicationProxy
Configuration - Creating a new service application
$appPool = Get-SPServiceApplicationPool "SharePoint Services”
$wmsa = New-SPWorkManagementServiceApplication –Name "Work Management Service Application" –ApplicationPool $appPool–Proxy
$wmsaProxy = New-SPWorkManagementServiceApplicationProxy -Name "Work Management Service Application Proxy" -ServiceApplication $serviceApp
Modifying settings - Set-SPWorkManagementServiceApplication
• NumberOfUsersPerEwsSyncBatch - the maximum number of users per Timer job interval. (default 100)
• NumberOfUsersEwsSyncWillProcessAtOnce - the maximum number of users at one time. (default 10)
• NumberOfSubscriptionSyncsPerEwsSyncRun - the minimum amount of time (in minutes) between calls for a new tenant to synchronize Exchange Web Services tasks. (default is 30 minutes)
• MinimumTimeBetweenSearchQueries - the minimum amount of time (in hours) between calls to search for a given user. This parameter is used to discover new providers not yet known to have tasks for this user. (default is 3 hours)
• MinimumTimeBetweenProviderRefreshes - the minimum amount of time (in minutes) between refreshes for a provider for a given user. (default is 5 minutes)
• MinimumTimeBetweenEwsSyncSubscriptionSearches - the minimum amount of time (in minutes) to find new tenants that want to synchronize Exchange Web Services tasks.
Configuration – Exchange Web Services API
Download EWSManagedAPI.msi from the Microsoft Download Center http://www.microsoft.com/en-us/download/details.aspx?id=35371
Run: msiexec /i EwsManagedApi.msi
addlocal="ExchangeWebServicesApi_Feature,ExchangeWebServicesApi_Gac“
Do an IISReset…
Configuration – Exchange Server 2013 server to trust the SharePoint 2013 server To establish OAuth trust and service permission
on Exchange, run: Configure-EnterprisePartnerApplication.ps1 -
ApplicationType Sharepoint -AuthMetadataUrl https://<SP_FQDN>/_layouts/15/metadata/json/1
Located in “C:\Program Files\Microsoft\Exchange Server\V15\Scripts”
Make sure certificates are trusted
WMA service account needs access to UPA My Site Host web application pool service
account needs access to UPA and the content databases
(GrantAccessToProcessIdentity)
Permission Checklist
Provision PWA sites after configuring WMA
Or add the WM service account to the Project Server databases’ PSDataAccess role.
Project Server Dependency
Work Management Service Configuration
DEMO
Key takeaways Work Management Service
configuration has a few steps but is not that hard
Not enough documentation out there ULS Logs is the key tool for
troubleshooting S2S is pretty awesome…
Resources Configure Exchange task synchronization in
SharePoint Server 2013 - http://technet.microsoft.com/en-us/library/jj554516.aspx
Configure server-to-server authentication between SharePoint 2013 and Exchange Server 2013 - http://technet.microsoft.com/en-us/library/jj655399.aspx
How to: Create high-trust apps for SharePoint 2013 using the server-to-server protocol (advanced topic) - http://msdn.microsoft.com/en-us/library/fp179901.aspx
The best resource out there: My Tasks Aggregation in SharePoint Server and Exchange Task Integration – Whitepaper by Marc Boyer
http://www.microsoft.com/en-us/download/details.aspx?id=38799
Resources #2
Adis Jugo’s Bloghttp://blog.sharedove.com/adisjugo/index.php/2014/02/18/webinar-work-management-service-materials-and-answers/ Has a great task provider code sample!
Resources #3
Time for questions Please fill in your feedback forms
Thank you !!!!!!!!! You are AWESOME!
Contact me to solve your S2S problems [email protected] @RadiAtanassov Facebook: Radi Atanassov LinkedIn: http://au.linkedin.com/in/sharepointradi Blog: www.sharepoint.bg/radi Company: www.onebitsoftware.net
© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, 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.
The end.