sharepoint 2013 hosted-apps (on-premises) - … · optional: create ssl certificate •an optional...
TRANSCRIPT
About Me
Veenus Maximiuk, MCSE – SharePoint, MCSA , MCPD
Managing Architect
© 2013, Information Control Corporation2
spvee.wordpress.com
@SharePointVee
Linkedin.com/in/vmaximiuk
© 2014, Information Control Company3
Agenda
• What are Apps for SharePoint?
• How to Configure SharePoint-hosted Apps
• Fix Error?
• Gotchas and Lessons Learned
What are Apps for SharePoint?
Practically all SharePoint ”artifacts” are Apps now (lists, libraries, web parts, as well as real Apps)
© 2014, Information Control Company6
Apps are stand alone bits of functionality that can be hosted locally, or in the cloud (SharePoint Store)
App URLs and Terminology
http(s)://app-9920e1970da725.YourAppDomain.com/demo/HelloWorld
App Prefix App ID App Domain Host Web App Name
© 2014, Information Control Company8
Host Web
App Web
How to Configure SharePoint-hosted Apps
1. Create Web Application
2. Create Forward Lookup Zone for Apps
3. Map Zone to SharePoint
4. Start Required Services
5. Create Subscription Settings and App Management Service Applications
6. Configure App URLs in SharePoint
7. Configure App Catalog
8. Add App to Catalog and Site
9. Create a Routing Web Application
© 2014, Information Control Company9
© 2014, Information Control Company10
• We know how to do this already
• Let’s move on to the next step
1. Create Web Application
2. Create Forward Lookup Zone for Apps
• If you plan to use apps on an internet-facing website, remember to buy this domain name
• If you only use it internally, remember to add it to either your local intranet or trusted sites
© 2014, Information Control Company11
3. Map Zone to SharePoint
• For multiple servers, point the FQDN to the DNS A Record or IP of the load balanced address
• Test – ex: ping SomeSite.veeapps.local
– Should get a reply back
© 2014, Information Control Company12
Optional: Create SSL Certificate
• An optional step
• Use a wildcard SSL certificate
– Use SSL certificate for each domain or sub-domain
• Since an app has its own unique ID, you’ll need to create one SSL for each app (not ideal)
• Not required to use a SSL certificate if you’re not planning on using SSL in your environment
© 2014, Information Control Company13
4. Start Required Services
© 2014, Information Control Company14
Get-SPServiceInstance | Where {$_.GetType().Name -eq"AppManagementServiceInstance" -or $_.GetType().Name -eq"SPSubscriptionSettingsServiceInstance"} | Start-SPServiceInstance
5.1 Create Subscription Settings Service#Get Managed Account
$managedAccount = Get-SPManagedAccount “<DOMAIN\ManagedAccount>”
#Create Application Pool
$appPoolAccount = New-SPServiceApplicationPool -Name “<SharePoint Application Services>” –Account $managedAccount
**If you want to use an existing service application pool**
$appPoolAccount = Get-SPServiceApplicationPool –Identity “<SharePoint Application Services>”
#Create Subscription Settings Service Application
$appSubscriptionService = New-SPSubscriptionSettingsServiceApplication -Name “Subscription Settings Service” -DatabaseName “<DEMO_Service_SubscriptionSettings>” -ApplicationPool $appPoolAccount
#Create Proxy
New-SPSubscriptionSettingsServiceApplicationProxy -ServiceApplication $appSubscriptionService
© 2014, Information Control Company15
5.2 Create Application Management Service Application
#Get Managed Account
$managedAccount = Get-SPManagedAccount “<DOMAIN\ManagedAccount>”
#Create Application Pool
$appPoolAccount = New-SPServiceApplicationPool -Name “<SharePoint Application Services>” –Account $managedAccount
**If you want to use an existing service application pool**
$appPoolAccount = Get-SPServiceApplicationPool –Identity “<SharePoint Application Services>”
© 2014, Information Control Company16
#Create App Management Service$appManagementService = New-SPAppManagementServiceApplication -Name “<App Management Service>” -ApplicationPool$appPoolAccount -DatabaseName “<DEMO_Service_AppManagement>”
#Create App Management Service ProxyNew-SPAppManagementServiceApplicationProxy -Name “<App Management Service Proxy>” -ServiceApplication$appManagementService
6. Configure App URLs
#Set App Domain
Set-SPAppDomain –AppDomain “veeapps.local”
#Set App Prefix
Set-SPAppSiteSubscriptionName –Name “app” –Confirm:$false
© 2014, Information Control Company17
http(s)://app-9920e1970da725.veeapps.local/demo/HelloWorld
App Prefix App ID App Domain Host Web App Name
Routing Web Application
© 2014, Information Control Company21
No host header
http(s)://app-bcf5d1b0eaa845.veeapps.local/HelloWorld
*.veeapps.local= 192.168.1.7
http(s)://veeintranet.vee.local
http(s)://team.vee.local
App Management
Service Application
NLB192.168.1.7
DNSFarm
9. Create a Routing Web Application
© 2014, Information Control Company22
1. Disable Default Web Site in IIS 2.
Gotchas and Lessons Learned
Apps do not support Kerberos
© 2014, Information Control Company25
If you plan on using FBA, extend the Web App to a different zone
Gotchas and Lessons Learned (cont’d)
• Both Subscription and App Management Services must be in the same proxy group
• Apps do not automatically replicate to variation sites
• AppPool account used for routing Apps must have rights to all content databases
– Use same AppPool for all Web applications
– Use same account for all AppPools
• Backup and restore
– Restore App Management Service
– Restore Content Database(s)
– Manage App Catalog
• Enter a URL for an existing app catalog site
© 2014, Information Control Company26
© 2014, Information Control Company27
• How to setup our environment
• How SharePoint 2013 Apps work
• How to manage apps
• Some gotchas and workarounds
We’ve Learned
References
• Configure an Environment for Apps for SharePoint (SharePoint 2013)
– http://technet.microsoft.com/en-us/library/fp161236(v=office.15).aspx
• How to Configure SharePoint 2013 On-Premises Deployments for Apps
– http://blogs.technet.com/b/mspfe/archive/2013/01/31/configuring-sharepoint-on-premise-deployments-for-apps.aspx
© 2014, Information Control Company28