OWA for SP2013 Part-3 ( Configure Office Web Apps for SharePoint 2013 )

Configure Office Web Apps for SharePoint 2013

Check the following before configuring it

• Install SharePoint 2013.
• Make sure all SharePoint 2013 web applications use claims-based authentication. Office Web Apps rendering and editing won’t work on SharePoint 2013 web applications that use classic mode authentication.
• To enable users to edit (not just read) Office documents in a web browser, you’ll need an editing license. Also, you’ll need to enable editing on the Office Web Apps Server farm.
• If you log on to SharePoint 2013 by using the System Account, you won’t be able to test the connection between SharePoint 2013 and Office Web Apps Server. Log on with a different account to test the connection.
• Low memory conditions can cause Office document previews to fail in Office Web Apps

 Choose one of the following sections depending on whether you want to use HTTP or HTTPS. HTTP is generally recommended only for test environments. In production environments, the more secure HTTPS protocol is the better choice.

In a test environment that uses HTTP

For this configuration, make sure you have set up Office Web Apps Server .Be sure to configure the Office Web Apps Server farm to use an internal URL and HTTP.

For this configuration, make sure you have set up Office Web Apps Server .Be sure to configure the Office Web Apps Server farm to use an internal URL and HTTP.

Step 1: Open an elevated SharePoint 2013 Management Shell

Choose the procedure that corresponds to your server operating system.

In Windows Server 2008 R2
Click Start > All Programs > Microsoft SharePoint 2013 Products.  Right-click SharePoint 2013 Management Shell, and click Run as administrator.

In Windows Server 2012
Press the Windows logo key + Q, or swipe in from the edge of the screen to show the charms, and then click Search to see all the applications that are installed on the computer.
Right-click SharePoint 2013 Management Shell to display the app bar.
In the app bar, click Run as administrator.

Step 2: Create the binding between SharePoint 2013 and Office Web Apps Server

Run the following command, where <WacServerName> is the fully qualified domain name (FQDN) of the URL that you set for the internal URL. This is the point of entry for Office Web Apps Server traffic. For this test environment, you need to specify the –AllowHTTP parameter to allow SharePoint 2013 to receive discovery information from the Office Web Apps Server farm by using HTTP. If you don’t specify –AllowHTTP, SharePoint 2013 will try to use HTTPS to communicate with the Office Web Apps Server farm, and this command won’t work.

New-SPWOPIBinding -ServerName <WacServerName> -AllowHTTP 

After running this command, you should see a list of bindings displayed at the Windows PowerShell command prompt.

Step 3: View the WOPI zones for the SharePoint bindings
Office Web Apps Server uses zones to determine which URL (internal or external) and which protocol (HTTP or HTTPS) to use when it communicates with the host, in this case, SharePoint 2013. By default, SharePoint Server 2013 uses the internal-https zone. Run the following command to see what your current zone is.
Get-SPWOPIZone
The WOPI zone displayed by this command should be internal-http. If it’s displayed correctly, skip to step 5. If it isn’t, see the next step. 

Step 4: Change the WOPI zone to internal-http

If the result from Step 3 was internal-https, run the following command to change the zone to internal-http. You need to make this change because the zone of SharePoint 2013 must match the zone of the Office Web Apps Server farm.

Set-SPWOPIZone -zone "internal-http" Verify that the new zone is internal-http by running Get-SPWOPIZone again. 
Step 5: Change the AllowOAuthOverHttp setting in SHarePoint 2013 to true   To use Office Web Apps with SharePoint 2013 over http in a test environment, you need to set AllowOAuthOverHttp to true. Otherwise OWA won't work. You can check status by running following command. 
( Get-SPSecurityTokenServiceConfig).AllowOAuthOverHttp
If this command returns False, run the following commands to set this to True.

$config = (Get-SPSecurityTokenServiceConfig)

$config.AllowOAuthOverHttp = $true

$config.Update()

Run the following command again to verify that AllowOauthHttp setting is now set to true 
(Get-SPSecurityTokenServiceConfig).AllowOAuthOverHttp   
Step 6: Verify that Office Web Apps is working 
In SharePoint 2013, make sure you are not logged on as system account because you won't be able to edit or view the documents with OWA. Go to a SP2013 document library that contains Office documents and view a word, powerpoint, excel, or OneNote file. The documents should open in a browser that displays the file by using OWA.

In a production environment that uses HTTPS

Before you start the following procedures, make sure that you have set up Office Web Apps Server.

Step 1: Open the SharePoint 2013 Management Shell

Choose the procedure that corresponds to your server operating system.

In Windows Server 2008 R2

1.     Select Start > All Programs > Microsoft SharePoint 2013 Products.

2.     Right-click SharePoint 2013 Management Shell to display the shortcut menu, and click Run as administrator.

In Windows Server 2012

1.     Press the Windows logo key + Q, or swipe in from the edge of the screen to show the charms and then click Search to see all the applications that are installed on the computer.

2.     Right-click SharePoint 2013 Management Shell to display the app bar.

3.     In the app bar, click Run as administrator.

Step 2: Create the binding between SharePoint 2013 and Office Web Apps Server

Run the following command, where <WacServerName> is the fully qualified domain name (FQDN) of the URL that you set for the internal URL. This is the point of entry for Office Web Apps Server traffic.

New-SPWOPIBinding -ServerName <WacServerName>

Step 3: View the WOPI zone of SharePoint 2013

Office Web Apps Server uses zones to determine which URL (internal or external) and which protocol (HTTP or HTTPS) to use when it communicates with the host, which in this case is SharePoint 2013. By default, SharePoint Server 2013 uses the internal-https zone. Verify that this is the current zone by running the following command.

Get-SPWOPIZone     ( Take note of WOPI zone that is displayed )

Step 4: Change the WOPI zone if necessary

Depending on your environment, you might have to change the WOPI zone. If you have a SharePoint farm that's both internal and external, specify external. If you have a SharePoint farm that's internal only, specify internal.

If the results from Step 3 show that internal-https and the SharePoint farm is internal only, you can skip this step. If you have a SharePoint farm that’s internal and external, you need to run the following command to change the zone to external-https.

Set-SPWOPIZone -zone "external-https"

Step 5: Verify that Office Web Apps is working

In SharePoint 2013, make sure you aren’t logged on as System Account because you won’t be able to edit or view the documents with Office Web Apps. Go to a SharePoint 2013 document library that contains Office documents and view a Word, PowerPoint, Excel, or OneNote file. The document should open in a browser that displays the file by using Office Web Apps.