Deploy Office WEB APPS Server and configure its integration with SharePoint 2013

Office Web Apps Server is a new Office server product that provides browser-based versions of Word, PowerPoint, Excel, and OneNote. A single office Web Apps server farm can support users who access Office files through SharePoint 2013, Lync Server 2013, Exchange Server 2013, shared Folders, and Web sites. Office Web Apps Server applies to products and services that support the WOPI (WEB application Open Platform Interface protocol). These products, called hosts, include SharePoint 2013, Lync Server 2013, and Exchange Server 2013. The Office Web Apps Server farm can provide office services to multiple on-premises hosts, and you can extend the farm from one server to multiple servers as your organization needs to grow. Office Web Apps 2013 is a standalone product that deploys SharePoint 2013, and you don't need to optimize your SharePoint infrastructure to support Office Web Apps as ever.

When used with SharePoint server 20,131, Office Web apps Server provides an updated version of Word Web App, Excel Web App, PowerPoint Web App, and OneNote We b App. Users can view Office documents in a SharePoint library by using a supported Web browser on a computer and many mobile devices, such as Windows Phone, IPhone, IPad, and Windows 8 tablet, and in some cases can edit those documents 。 Among the many new features in Office Web Apps, the improved touch support and editing capabilities enable users of IPad and Windows 8 tablets to edit and view Office documents directly from their devices. Www.it165.net

My experimental environment is as follows:
Contoso-sp13.contoso.com (SharePoint 2013; Os:windows Server 2012)
Contoso-owa.contoso.com (offie Web Apps Server 2013; Os:windows Server 2012)
Note: Office Web Apps Server is now a standalone product, so it cannot be installed on the same server as SharePoint server and needs to be installed separately. You can also have multiple office Web APPS servers that make up a single server farm, and my lab environment has only one OWA server.

First step: Prepare the server to run Office Web Apps server
Step two: Office Web Apps server farm
Step Three: Configure SharePoint 2013 to use Office Web Apps

The first step. Prepare the server to run Office Web Apps server

1. Open the Windows PowerShell prompt as an administrator, and then run the following sample command to install the required roles and services.
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

The Windows Server R2 and Windows Server 2012 prerequisites differ, and you can refer to: http://technet.microsoft.com/zh-cn/library/jj219455.aspx


2. Download and install Office Web Apps Server 2012
Download link:http://www.microsoft.com/en-us/download/details.aspx?id=35489

3. Install the language pack for Office Web Apps Server, download the link:

http://www.microsoft.com/zh-cn/download/details.aspx?id=35490

Step Two: Deploy  office Web Apps server  server farm
 
1.  Create Office Web Apps server farm
in Office Web apps S erver, open PowerShell, enter
Import-module officewebapps
 
new-officewebappsfarm – internalurl  "http://ServerName"  –allowhttp-editingenabled
 
My OWA server has a record ' Owa.contoso.com ' points to it, so my command line is
 
 
New-officewebappsfarm–internalurl "http://owa.contoso.com"  –allowhttp-editingenabled
 
 
 

 
2.  Verify that Office Web Apps was created successfully Server farm
Open the following link in the browser
http://servername/hosting/discovery
 
If Office Web Apps server is running as expected, you should The Web browser sees the Web application Open Platform Interface (WOPI) discovery XML file. As follows:
 

Step Three: Configure SharePoint 2013 to use Office Web Apps

For detailed documentation, refer to: http://technet.microsoft.com/zh-cn/library/ff431687.aspx

Here I use the test environment in HTTP to configure SharePoint 2013 to use Office Web Apps Server

1. Create a binding between SharePoint 2013 and Office Web Apps Server
Open the SharePoint Management Shell and enter

New-spwopibinding-servername <WacServerName>-allowhttp

2. View the WOPI zone for SharePoint bindings

Get-spwopizone

If the result obtained by performing step 3 is Internal-https, run the following command to change the zone to Internal-http. You must make this change because the zone for SharePoint 2013 must match the region of the Office Web Apps server farm.

Set-spwopizone–zone "Internal-http"

Confirm that the new zone is internal-http by running the following command:

Get-spwopizone

3. Change the Allowoauthoverhttp setting in SharePoint 2013 to True

To use SharePoint 2013 with Office Web Apps in a test environment with HTTP, you must set Allowoauthoverhttp to True. Otherwise, Office Web Apps will not work. You can check the current status by running the following example:

(Get-spsecuritytokenserviceconfig). Allowoauthoverhttp

If this command returns FALSE, run the following command to set it 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

Now we can easily open and edit an Office document in a SharePoint document library.



You can also create Office documents directly on a Web page

The test is over here and hopefully this article will help you!

Deploy Office WEB APPS Server and configure its integration with SharePoint 2013