Download as pptx, pdf, or txt
Download as pptx, pdf, or txt
You are on page 1of 19

Click to edit Master

subtitle style

06 | Deploying Apps

Chris Johnson | SharePoint Guru


Christopher Harrison | Microsoft Certified Trainer
Module Overview

App Management Architecture


Understanding App Packages
Publishing Apps
• Installing, Updating, and Uninstalling Apps
Lesson 1: App Management Architecture

Service Applications for App Management


• Publishing Locations
Service Applications for App Management

• The App Management Service


– Create by using Central Administration or PowerShell
• The Site Subscription Settings Service
– Create by using PowerShell
$ApplicationPool = New-SPServiceApplicationPool -Name "Site
Subscription Settings Pool" -Account CONTOSO\Administrator
$SiteSubService = New-
SPSubscriptionSettingsServiceApplication
-Name "Subscription Settings Service"
-Databasename "SubscriptionSettingsServiceDatabase"
-applicationpool $applicationPool
$AppProxy = New-
SPSubscriptionSettingsServiceApplicationProxy
-ServiceApplication $SiteSubService
Publishing Locations

• App Packages are published in:


– The Office Store
• For global access
– An App Catalog
• For access from the same web application
Lesson 2: Understanding App Packages

App Package Format


Packages for Remote Hosted Apps
• Demonstration: Exploring an App Package
App Package Format

• AppManifest.xml
– Required for all apps
• AppIcon.png
– Recommended for all apps
• App Web Solution
– Required for SharePoint hosted apps
– Optional for remote hosted apps
• Host Web Features
– Optional for all apps
Packages for Remote Hosted Apps
SharePoint Autohosted App Provider Hosted
Hosted App Package App Package
Package
• App Manifest
• App Manifest
• App Manifest • App Icon
• App Icon
• App Icon • Web Deploy
• Solution Package
Package: • Remote
• Web Pages Web
• Scripts • Data Tier
• SharePoint Application
Items Package
• Database
Lesson 3: Publishing Apps

The Publishing Wizard


Publishing to the Office Store
• Publishing to an App Catalog
The Publishing Wizard
Publishing to the Office Store
• The Office Store is a global catalog of apps for SharePoint, Office, and Azure
• A Dashboard Seller Account is required
• Upload you apps and provide:
– A title
– A version number
– A description
– A category
– A logo
– Screenshots

• Microsoft tests and approves the quality of all apps


Publishing to an App Catalog

• You can use an App Catalog to publish an app to the users of a


single tenancy or web application
• Use Central Administration to create a new App Catalog site
• Upload app package files to the app catalog and complete the
metadata to publish apps
DEMO
Publishing an App
Lesson 4: Installing, Updating, and Uninstalling Apps

App Installation
Updating an App
• Uninstalling Apps
App Installation

• Installation procedures
• Installation permissions
• Agreement to Permission Requests
• Installation with PowerShell
$web = "http://intranet.contoso.com/"
$apppackage = "C:\Apps\MyApp.app"
$appsource =
([microsoft.sharepoint.administration.spappsource]
::CorporateCatalog)
$spapp = Import-SPAppPackage –Path $apppackge –Site $web
–Source $appsource –Confirm: $false
Install-SPApp –Web $web –Identity $spapp –Confirm: $false
Updating an App

• Upgrades are based on the version number in the app manifest


– Upgrades are voluntary
• Upgrades are simplified because SharePoint hosted apps and
autohosted apps are self-contained
• For provider hosted apps ensure that the remote web supports
both old and new versions
Uninstalling Apps

• When you remove an app the app web is deleted


• Shortcuts and the app identifier are deleted so permission no
longer apply
• Remote webs are not deleted

$web = "http://intranet.contoso.com/"
$appname = "Contoso Ledgers App"
$appInstance = Get-SPAppInstance –Web $web |
Where-Object {$_.Title –eq $appname}
Uninstall-SPAppInstance –Identity $appInstance –Con
$false
DEMO
Upgrading an App
©2013 Microsoft Corporation. All rights reserved. Microsoft, Windows, Office, Azure, System Center, Dynamics 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.

You might also like