Access Services Introduction & Setup Requirements Kipp Sorensen, Soren Innovations

What we are going to cover 1.Access Services - What and Why? 2.Architecture Overview 3.Planning on-premises deployments

The problem being solved 1.Unknown and uncontrolled data applications 2.Poor end-user applications 3.IT requests to build “minor applications” 4.End-user applications with data access issues and no backups 5.Lack of upgrade path

Why Access Services?

Core Benefits of Access Services 1.SQL Back-end 2.App Experience Simple and clean design Consistent interface and results 3.SharePoint Deployment Web Applications SharePoint SQL Database

SQL Back-end -MS standard for relational databases -Transparent to end user -Common tech and tools for IT support and integrations -Upgrade Path

App Experience Demo

SharePoint Deployment -SharePoint Store & App Catalog for distribution -Multi-user access -Active Directory-based permissions -Simple setup (App Setup) -Available in Office 365 and on-premises Demo

Architecture Overview View and Edit Data Database Design Advanced Reporting & Integration Desktop Access Reports Excel Power View Crystal Reports Custom Websites (.NET, PHP, etc.)

Office 365 versus On-Premises -Already configured and ready -SQL Azure* -Security -Redundancy/Backup -Upfront configurations -Governance -Customer Requirements -Heavy integrations -Security -Cost

On-premise Infrastructure SQL Server 2008 R2 SP1 or 2012 SQL Server 2012 SharePoint 2013

SQL Server 2012 Requirements -Installed elements

SQL Server 2012 Requirements -Advanced Settings -Enabled constrained databases -All Triggers to fire others -Default language to English

SQL Server 2012 Requirements -SQL Authentication Mode -SQL Server & Windows Auth.

SQL Server 2012 Requirements -Client Protocols -Named Pipes: Enabled

SQL Server 2012 Requirements -Service Account & Permissions -Create a domain account that will be used as the Access Services service account (Multiple app pools? This requires unique permissions) -Cannot be the farm account -Grant appropriate access to SQL -Dbcreator -Public -securityadmin

SharePoint App Server Requirements -Install SQL 2012 Feature Pack (what server?) - -Microsoft SQL Server 2012 Local DB (SQLLocalDB.msi) -Microsoft SQL Server 2012 Data-Tier Application Framework (Dacframework.msi) -Microsoft SQL Server 2012 Native Client (sqlncli.msi) -Microsoft SQL Server 2012 Transact-SQL ScriptDom (SQLDOM.MSI) -Microsoft System CLR Types for Microsoft SQL Server 2012 (SQLSysClrTypes.msi)

SharePoint Configurations -Pre-requisites -App Management Services & App Catalog Configured -Subscription Settings Services -DNS configured for Apps Catalog -SSL/Host Headers -Secure Store Service -Generated security key -Site Collection -Permission assigned

SharePoint Configurations -Register the Access Services service account -Create the Access Services service application -Create new application pool and assign the account above -Do you need to reference a different database server? -Remember to start services on Server

SharePoint Configurations -Assign AccessServices account “Full Control” to the App Management Service -Change to Access Service app Pool -Load User Profile = True

Conclusion Access Services can provide value to your organization but identify the use cases Office 365 comes ready with Access Services On-premises environment require additional setup

References - premises.aspx - premises-installation.aspx Hints and Tips - - Whitepaper for install - - SQL 2012 Feature Pack - - Access Service PowerShell Commands - - Account perms in 2013