This post, I would like to discuss about how to install OWAS 2013 (Office Web Apps Server) and configure SharePoint Server 2013 to use it.
What do we get with it?
OWAS 2013 is responsible for the document preview and edit in SharePoint server 2013. Besides SharePoint server, OWAS 2013 can be leveraged by Lync 2013 and Exchange 2013.
About OWAS 2013
OWAS 2013 can’t be installed as a service on SharePoint server. It should be installed as a standalone server. No other server products like SQL, SharePoint, Lync, Exchange, and Office etc. should be installed on the same server that OWAS 2013 is installed on. OWAS 2013 can be installed only on Windows server 2012 and 2008 R2. This can’t be installed on Server 2008 (You need R2).
The following is a snapshot taken from Technet (http://technet.microsoft.com/en-us/library/jj219455(v=office.15).aspx) which depicts the steps involved in setting up OWAS and any host that uses it.
Steps to be done on OWAS server
1) OWAS Download and Install
2) Setup OWAS
Steps to be done on SharePoint server
1) Configure with OWAS
OWAS Download and Install
You can download it from the link below and follow the instructions mentioned there. Installation is pretty simple.
The following PowerShell cmdlets help you create Office Web apps farm once OWAS server is installed.
Use either of the following two cmdlets. Use Https cmdlet if you want that support.
New-OfficeWebAppsFarm –InternalURL "http://spworks01.corp.spworks.net" –AllowHttp –EditingEnabled
http://spworks01.corp.spworks.net - FQDN of server
New-OfficeWebAppsFarm -InternalUrl "https://spworks01.corp.spworks.net" -ExternalUrl "https://spworksowas.spworks.com" -CertificateName "SpWorksOWAS" –EditingEnabled
If Windows PowerShell doesn’t recognize
“New-OfficeWebAppsFarm” cmdlet, you need to import the corresponding module by running the following command.
Import-Module –Name “OfficeWebApps”
Before you proceed to SharePoint server verify that OWAS is working with the following url.
http://servername/hosting/discovery (server name is the “internal url” given when setting up Office Web Apps server). If OWAS is properly configured, you’ll see the following xml.
SharePoint Server configuration with OWAS
Run the SharePoint Management shell as administrator.
Run the following commands.
The following command helps set the WOPI binding with OWAS
New-SPWOPIBinding -ServerName "spworksowas.spworks.com"
Set the SPWOPIZone to internal-http
Set-SPWOPIZone -zone "internal-http"
$config = (Get-SPSecurityTokenServiceConfig)
$config.AllowOAuthOverHttp = $true
Now SharePoint document preview and editing should be working.
Plan Office Web Apps Server
Configure OWAS for SharePoint 2013