Sharepoint2013-office Web App server2013 detailed installation and deployment

Pre-conditions

Office Web App server2013 cannot be installed on the same server as SharePoint server2013, and you will be prompted with the following error if installed on the same server:

Later inquiry information:

According to the official documentation, the requirements for SharePoint 2013 are the same, requiring 8-12GB of memory, which requires the operating system to be Windows Server R2 SP1 or Windows Server 2012, and needs to be installed. Net Framework 4.5 and so on.

According to Microsoft's information such as:

There are two points to note:

Øoffice Web Apps 2013 is a standalone server that is installed independently of SharePoint and no longer needs to be like SharePoint 2010. Needs to be installed with the SharePoint server (to some extent, license costs are saved).

Øoffice Web Apps 2013 not only provides SharePoint with rendering services for Office documents (the document supports a format that does not include PDFs), but also provides document rendering services for Microsoft Exchange Server and Lync Server. You can also provide this service for shared folders and even for third-party applications.

Between the Office Web Apps server and the server that uses its services, it communicates through an entirely new Wopi (Web application Open Platform Interface) interface protocol, and its external channel remains http/ HTTPS protocol. Office Web Apps Server is called the Wopi APP, and using this service is called Wopi Host.

Need

Øpowershell V3 (http://www.microsoft.com/en-us/download/details.aspx?id=29939)

Ø.net Framework4.5

Øwindows Server R2 SP1

Øwindows6.1-kb2592525-x64 (http://www.microsoft.com/zh-cn/download/details.aspx?id=27929)

Office Web App Server 2013 Installation

1th Step: if Windows Server R2 needs to first perform the following

Import-module Servermanager

Add-windowsfeature Web-server,web-webserver,web-common-http,web-static-content,web-app-dev,web-asp-net, Web-net-ext,web-isapi-ext,web-isapi-filter,web-includes,web-security,web-windows-auth,web-filtering, Web-stat-compression,web-dyn-compression,web-mgmt-console,ink-handwriting,ih-ink-support

if it is Windows server2012

Import-module Servermanager

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

And then do the following

Office Web App Server 2013 Configuration

Based on this diagram, the next step is to create a server farm, which is not a SharePoint farm, but an Office Web apps farm-a server farm that can contain multiple Office Web apps servers for different roles. The way to create it is simple, PowerShell:

1th steps:

#加载Office Web Apps Management Command set,

Import-module Officewebapps

2nd steps:

#创建服务器场

New-officewebappsfarm–internalurl http://servername–allowhttp–editingenabled

Description: ServerName server name for the installation of OWA (Office Web App server2013)

3rd steps:

#验证服务器场

Http://servername/hosting/discovery

Description

Office Web Apps Server is running as expected, and you should see the Web application Open Platform Interface (WOPI) discovery XML file in your Web browser. The first few lines of the file should resemble the following example:

Copy

<?xml version= "1.0" encoding= "Utf-8"?>

-<wopi-discovery>

-<net-zone name= "Internal-http" >

-<app name= "Excel" faviconurl= "Http://servername/x/_layouts/images/FavIcon_Excel.ico" checklicense= "true" >

<action name= "View" ext= "ODS" default= "true" urlsrc= "http://servername/x/_layouts/xlviewerinternal.aspx?<ui= Ui_llcc&><rs=dc_llcc&> "/>

<action name= "View" ext= "xls" default= "true" urlsrc= "http://servername/x/_layouts/xlviewerinternal.aspx?<ui= Ui_llcc&><rs=dc_llcc&> "/>

<action name= "View" ext= "XLSB" default= "true" urlsrc= "Http://servername/x/_layouts/xlviewerinternal.aspx?<ui =ui_llcc&><rs=dc_llcc&> "/>

<action name= "View" ext= "xlsm" default= "true" urlsrc= "Http://servername/x/_layouts/xlviewerinternal.aspx?<ui =ui_llcc&><rs=dc_llcc&> "/>

For details, please refer to:

http://technet.microsoft.com/zh-cn/library/jj219455 (v=office.15). aspx

My machine name is: OWA

New-officewebappsfarm–internalurl http://owa–allowhttp–editingenabled

After selecting Y

Explanation: One of the things that needs to be explained is allowhttp: This is whether the configuration allows HTTP access (by default, HTTPS), and the second is editingenabled, which needs to be added if you need to edit the document in a browser (in addition, According to the official documentation, in SharePoint, whether the user can edit the document in the browser, is required to have a separate license configuration, this so-called license concept is similar to Standard CAL, Enterprise CAL concept, Only this can be differentiated from the server level in the past, but at the user level in 2013.

Note: The installation process prompts you for the following error

Only "Add Server Features" is required at this time, such as:

Ø enable the ink support service

After installation, the system will automatically restart the server and then complete the installation.

Ø Enable the Windows authentication service

Open the Web server IIS role that you have added. Add role services, such as:

Did you test the success of the Office Web App? In the browser, enter:

Http://servername/hosting/discovery (servername is the OWA machine name, I am here OWA)

If the following error occurs after installation:

Workaround:

If you install and then remove the components of the. NET Framework 3.5, you may see a "Web service exception" or a "500.21– Internal server Error" message when you run the Officewebapps cmdlet. To resolve this issue, run the following sample command from an elevated command prompt to clean up the settings that prevent Office Web Apps Server from running correctly:

On the command line, enter:

%systemroot%\microsoft.net\framework64\v4.0.30319\aspnet_regiis.exe-iruiisreset/restart/noforce

After running, you can see:

Sharepoint 2013 integrates with Office Web App Server 2013

The integration process is to enable the Office Web Apps Farm to render/edit Office documents in a SharePoint document library.

This configuration is also very simple, open the SharePoint PowerShell script window and execute two sentences:

New-spwopibinding-servername <WacServerName>-allowhttp

Set-spwopizone internal-http

Description

WACSERVERNAME Specifies the name or fully qualified domain name (FQDN) of the WOPI application, such as the server running Office Web apps server.

The first sentence is to establish a relationship between the SharePoint farm and the Office Web Apps Farm, where the allowhttp parameter is the same as the previous concept;

U This example creates bindings for all applications and file extensions supported by the WOPI application on the current SharePoint farm running this cmdlet

New-spwopibinding–servername "Server.corp.Contoso.com" –allowhttp

The Excel,word,ppt assignment can be installed on 3 servers based on the previous diagram, and is associated with the farm, so the following example only enables one of the

U This example associates excel with all actions that Excel performs on the WOPI application on the current SharePoint farm that runs this cmdlet

New-spwopibinding–servername "Server.corp.Contoso.com" –application "Excel"

Ø the second sentence, is to configure the area of the link, the region is divided into internal and external, the Protocol is divided into HTTP and HTTPS, the default is internal + HTTPS, here we use internal-http, in order to configure and before the Office Web When the apps server farm is matched.

My command line here is:

New-spwopibinding–servername "owa.mono.com"-allowhttp set-spwopizone internal-http

Such as:

Done

Office Web App Server 2013 effect test

Upload a Word document under test, as follows:

First, the Office Web Apps feature "System Account" (Administrator) is not available, and if you try to access the site using the system account, and the view browses a document online, an exception occurs, You can see from the log that the server could not find the specific account for the system accounts mapping.