Office Web Apps is the online companion to Office Word, Excel, PowerPoint, and OneNote applications, and enables users–regardless of their location–to view and edit documents. Office Web Apps give users a browser-based viewing and editing experience providing a representation of an Office document in the browser. When a user selects an Office document that is stored in a SharePoint document library, the document opens directly in the browser. When an Office Web App user selects the Edit in Word, Edit in Excel, Edit in PowerPoint, or the Edit in OneNote button on the toolbar, the document opens immediately in the associated Office client application (if it has been installed on the client computer).

Configuring Office Web Apps for SharePoint 2013 is a fairly simple process. The following post shows how to set up the Office Web Apps Server and configure SharePoint 2013 to use the Office Web Apps Server.

• Windows Server 2012, for our exaample: VNGWIN2012
• Server SharePoint 2013, for our example: VNGO15SQL2

On VNGWIN2012, running the Office Web Apps Server:

1. 1. Open a Windows PowerShell prompt as an administrator:
      Run the following command:
      Add-WindowsFeature Web-Server,Web-Mgmt-Tools,Web-Mgmt-Console,Web-WebServer,Web-Common-Http,Web-Default-Doc,Web-Static-Content,Web-Performance,Web-Stat-Compression,Web-Dyn-Compression,Web-Security,Web-Filtering,Web-Windows-Auth,Web-App-Dev,Web-Net-Ext45,Web-Asp-Net45,Web-ISAPI-Ext,Web-ISAPI-Filter,Web-Includes,InkandHandwritingServices

1. Install Office Web Apps Server software from http://www.microsoft.com/en-us/download/details.aspx?id=35489.
   • • From the root folder of the Office Web Apps files, run Setup.exe:

    

   • • On the Choose a file location page, click Install Now and Close when it’s completed:

    

   • • Open a Windows PowerShell prompt as an administrator and run:
       New-OfficeWebAppsFarm –InternalURL “http://vngwin2012” –AllowHttp -EditingEnabled

    

   • Verify that the Office Web Apps Server farm was created successfully by opening a browser window and going to http://vngwin2012/hosting/discovery

On VNGO15SQL2, the server that runs SharePoint 2013:

1. 1. Open the SharePoint 2013 Management Shell prompt as an administrator:

1. Create the binding between Office Web Apps Server and SharePoint 2013. This sets up communication between the server that runs SharePoint 2013 (VNGO15SQL2) and the server that runs Office Web Apps Server (VNGWIN2012).
   • • Run command:
       New-SPWOPIBinding -ServerName vngwin2012 –AllowHTTP After you run this command, you should see a list of bindings displayed at the Windows PowerShell command prompt:

    

   • • View the WOPI zones for the SharePoint bindings:
       Get-SPWOPIZone

    

   • • Change the WOPI zone to internal-http:
       Set-SPWOPIZone –zone “internal-http”

    

   • • Verify that the new zone is internal-http:
       Get-SPWOPIZone

    

   • • Change the AllowOAuthOverHttp setting in SharePoint 2013 to True:
       (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 the AllowOAuthOverHttp setting is now set to True:
       (Get-SPSecurityTokenServiceConfig).AllowOAuthOverHttp

    

2. Verify that Office Web Apps is working on opening an Office document in a SharePoint 2013 document library.
   • • Go to site http://vngo15sql2, and upload the file “Nokia shares fall.docx” to the document library:

    

   • • Click on “Nokia shares fall” to open the file; it can be viewed using any supported Web browser:

    

   • And can now be edited in Word or via the Edit in Word Web App option: