Deploying and Managing SP2013 Apps

25
#spsla @tweetraw Deploying and Managing SP2013 Apps Randy Williams Director of AvePoint Client Services

description

For years, packaging has been an essential best practice to manage the deployment of custom apps across dev, test and production environments. While this principle remains, complexity has grown with the cloud and the latest generation of SharePoint applications. Beyond simple SharePoint solution packages (WSPs)—SharePoint apps have evolved into a conglomeration of code that can be deployed into Windows Azure, SQL Azure, SharePoint Online, not to mention online markets such as SharePoint Store. Join us to gain a solid footing in this new application landscape. Are you prepared to deploy and manage the next generation of custom apps? If not, invest 60 minutes in your career to get up to speed.

Transcript of Deploying and Managing SP2013 Apps

Page 1: Deploying and Managing SP2013 Apps

#spsla @tweetraw

Deploying and Managing SP2013 AppsRandy WilliamsDirector of AvePoint Client Services

Page 2: Deploying and Managing SP2013 Apps

Randy Williams

Director of ACS

@tweetraw [email protected]

Author

Page 3: Deploying and Managing SP2013 Apps

?Why do we need a new app model

Page 4: Deploying and Managing SP2013 Apps

#spsla @tweetraw

Challenges with WSP solutions Full-trust solutions

Performance and stability concerns Incompatible with SPOL

Sandboxed solutions Clunky architecture, too limiting

Requires administrative deployment and support Lifecycle management

Upgrade, decommission Steep learning curve

Page 5: Deploying and Managing SP2013 Apps

#spsla @tweetraw

Benefits of the new app model

• Lower learning curve – re-use your existing web technology background

• SharePoint Store opens up new revenue potentialDevelopers

IT Managers

• Apps decoupled from SharePoint – simplifies upgrades

• Virtually no risk to farm• Corporate catalog facilitates governance

controls

Info Workers

• Based on a proven and familiar app model• Apps can be found in SharePoint Store or a

corporate app catalog• Can provision, upgrade and delete

Page 6: Deploying and Managing SP2013 Apps

“”

A small, easy-to-use, stand-alone productivity app that solves a specific end-user need.

What is a SharePoint 2013 App?

Microsoft - bit.ly/WusHj0

Page 7: Deploying and Managing SP2013 Apps

#spsla @tweetraw

Demo

Built-in AppsA quick look at what’s built in

Page 8: Deploying and Managing SP2013 Apps

#spsla @tweetraw

So - what exactly is an app?

Can contain some declarative SharePoint artifacts External app provides SharePoint UI through IFrame External app uses CSOM or REST (OData) to call back No custom server-side code running on SharePoint WFEs

An application whose interface is surfaced through SharePoint but

code is executed elsewhere

Page 9: Deploying and Managing SP2013 Apps

#spsla @tweetraw

How apps run

SP Farm Other Platform

CSOM/OData

OAuth / S2S

Page 10: Deploying and Managing SP2013 Apps

#spsla @tweetraw

Apps vs solution packagesApps Sandboxed WSP Full trust WSP

Where does server-side code run? Anywhere but farm

Farm (User Code Service) Farm (w3wp.exe)

Scalable Highly Limited Based on farm

Who installs and removes Users Site collection admin Farm admin

Supported in SP2013 Yes Yes Yes

SharePoint Online compatible Yes Yes No

Azure-hosting compatible Yes No No

Requires local farm for development No Yes Yes

Remote deployment and debugging from Visual Studio Yes No No

Package extension and type .app (zip file) .wsp (cab file) .wsp (cab file)

Page 11: Deploying and Managing SP2013 Apps

#spsla @tweetraw

Application lifecycle Apps are designed to be user

provisioned Requires full control permissions

Users find and provision apps from App Catalog or SharePoint Store

App owners can also upgrade and uninstall

Page 12: Deploying and Managing SP2013 Apps

#spsla @tweetraw

Three hosting options

Page 13: Deploying and Managing SP2013 Apps

#spsla @tweetraw

Three hosting options

Page 14: Deploying and Managing SP2013 Apps

#spsla @tweetraw

Three hosting options

Page 15: Deploying and Managing SP2013 Apps

#spsla @tweetraw

Three hosting options

Page 16: Deploying and Managing SP2013 Apps

#spsla @tweetraw

Host web and app web The host web is where app is added, removed, upgraded If app has SharePoint artifacts, a sub-web is created

underneath the host web This sub-web is called the app web App web is only accessible using isolated domain name

https://apps-{GUID}.contosoapps.com/{appName}

Host Web

AppWeb

http://intranet

http://app-af48d482118ab1.contosoapps.com/myapp

Page 17: Deploying and Managing SP2013 Apps

#spsla @tweetraw

App web Provisioned by host web Contains only web-scoped features Initial UI is immersive, full page

Set in appmanifest.xml Custom master page is assigned (app.master) Quick launch and common layout pages are unavailable

Settings.aspx, viewlsts.aspx, etc. Only declarative code allowed within the app web

No DLL

Page 18: Deploying and Managing SP2013 Apps

#spsla @tweetraw

Deploying apps in SharePoint Online Environment is pre-configured to support 2013 apps All hosting options are available

SharePoint-hosted for lightweight, JS-based apps Autohosted for more complex apps

Windows Azure for any server-side custom code (PHP, .NET) SQL Azure for any database requirements

Provider-hosted but provisioning is complex Create App Catalog to host corporate-approved apps SharePoint Store cannot be hidden, but you can prevent

apps from being installed

Page 19: Deploying and Managing SP2013 Apps

#spsla @tweetraw

Deploying apps within SP 2013 farms * Environment is not pre-configured (details covered later) All app hosting types are supported Web application must use claims-based authentication App catalog owners can upload .app packages directly App catalog owners can also approve requested apps SharePoint Store behavior is the same as with SPOL

* On-premises or IAAS-hosted farms

Page 20: Deploying and Managing SP2013 Apps

#spsla @tweetraw

Demo

.app packageLet’s take a look inside

Page 21: Deploying and Managing SP2013 Apps

#spsla @tweetraw

Configure a farm to support 2013 apps Create DNS zone for app domain name (e.g.

contosoapps.com) Create wildcard DNS CNAME entry and point to WFE/load

balancer Obtain a wildcard SSL cert (PowerShell) Create a Subscription Settings service

application and proxy (PowerShell or CA) Create an App Management service

application (PowerShell or CA) Configure app domain URL (e.g.

contosoapps.com) and prefix

For details: http://technet.microsoft.com/en-us/library/fp161236.aspx

Page 22: Deploying and Managing SP2013 Apps

#spsla @tweetraw

Demo Managing apps

Page 23: Deploying and Managing SP2013 Apps

#spsla @[email protected] @tweetraw

Thank you

Page 24: Deploying and Managing SP2013 Apps

Don’t ForgetSharePint!!

Join us at after the closing ceremony at The Daily Pint

for drinks and laughs. A great opportunity to network

with other SharePoint Professionals!

Page 25: Deploying and Managing SP2013 Apps

Atera Prime K2

Axceler KnowledgeLake

CBT Clips KwizCom

Dell QuickStart

Hershey Technologies

Virtualworks

Thank you to all our sponsors! Please visit the booths

outside.

Platinum & Gold Sponsors

SilverSponsors