Office Web Apps Installation Deployment (i)

From: http://www.cnblogs.com/poissonnotes/p/3238238.html

System requirements for Windows Server 2012,

Note: Servers that install Office Web apps cannot install other apps other than Office Web apps. This includesapplications such as Office,lync, SharePoint, and so on, which are deployed separately.

Installing IIS 7.0

Open Server Manager

Add roles and Features

Open the Add Roles and Features Wizard interface and click Next

Select Role-based or feature-based installation because this is a native-based installation

Click "Next"

On the Server Role list, select Web server

"Next", install.

Note that when you install IIS, you install the "Manage service" under the Web server,

or run the command in the following order:

Run PowerShell as an administrator

View Code

This powershell means enabling related roles and features for Windows, such as ink handwriting services, ASP. NET 4.5,iis Services, etc.

Install Office Web Apps

Download from http://www.microsoft.com/zh-cn/download/confirmation.aspx?id=35489 link
Microsoft Office Web Apps Server

Click Install.

Open the installation file with the following interface:

Agree to the agreement, click "Continue"

Select the installation location and click "Install Now".

When the installation is complete, click "Close"

Install Office Web Apps patch files

Download patch files from http://www.microsoft.com/zh-cn/download/confirmation.aspx?id=38378 for installation

Such as:

Tick the license terms to continue the installation.

Installation complete interface.

Install the Office Web Apps Language Pack

The language pack for Office Web apps allows users to view Office documents as they are available in a SharePoint site when they are open in the web, and if the in-document package contains multiple languages. Language packs can be opened at the following links:

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

It's the installation interface.

Click Accept Agreement to continue. To complete the installation.

Reboot after installation . Otherwise, PowerShell does not recognize the associated cmdlet commands in the next operation.

If you do not want to restart, you can type the following command in PowerShell

Import-module Officewebapps

To load the Office Web Apps Management Command set

Note: If you are installing a language pack for the office Web Apps Farm, isolate the individual servers from the farm separately and then install them individually.

Deployment Office Web Apps

On the Officewebapps server, open PowerShell as an administrator, type the command

New-officewebappsfarm–internalurl "http://OfficeWebApps.veekee.cn" –allowhttp–editingenabled

(where http://OfficeWebApps.veekee.cn OfficeWebApps.veekee.cn is the full computer name of the Officewebapps server.) This name is based on the specific environment.

Enter to determine.

Prompt will appear

Enter "Y" and return.

If successful, the list information will be returned

We can enter the following URL in the server's browser to verify

Http://OfficeWebApps.veekee.cn/hosting/discovery

(where http://OfficeWebApps.veekee.cn OfficeWebApps.veekee.cn is the full computer name of the Officewebapps server.) This name is based on the specific environment)

If the installation is successful, a message will be displayed:

This is where office Web apps deployment succeeds.

In general, Office Web Apps is used in conjunction with other apps, as shown in:

If you develop a system yourself, you can actually invoke Office Web Apps.

Office Web Apps Installation Deployment (II)

SharePoint 2013 calls Office Web Apps

Note: The identity authentication for a SharePoint app that calls Officewebapps must be claims-based authentication (claims-based authentication)

Install SharePoint2013 First, I use the Free Sharepiont Foundation 2013 in this deployment document.

Operating system environment is: windows2012.

1. After installing SharePoint 2013. Run the following PowerShell as an administrator

New-spwopibinding-servername <WacServerName>-allowhttp

Where <WacServerName> is the domain name (FQDN) for office Web Apps, say: OfficeWebApps.veekee.cn.

The PowerShell command above means that the Open Affiliate Program for Office documents in the SharePoint document library is built for office Web Apps.

Successful words will return the following information,

2. Then run the following command:

Get-spwopizone

(Wopi refers to the Web application Open Platform Interface protocol)

The PowerShell command above means to view the communication protocol between this SharePoint server and other servers.

After running, the following information is returned:

Returns INTERNAL-HTTPS, which means that the interface protocol is HTTPS.

In general, using the HTTP protocol on the intranet is sufficient.

So to change to the HTTP protocol, use the following command:

Set-spwopizone-zone "Internal-http"

Again with the Get-spwopizone view, returned is internal-http, the modification succeeds.

3.

Then modify the authentication relationship between SharePoint and Office Web apps. To set the Allowoauthoverhttp property to True.

Use the following command:

(Get-spsecuritytokenserviceconfig). Allowoauthoverhttp

The return is false.

Then you should set this property to true with the following command.

$config = (get-spsecuritytokenserviceconfig) $config. Allowoauthoverhttp = $true $config. Update ()

As shown in the following:

So far, the relationship between Office Web apps and SharePoint2013 has been established. You can create a new SharePoint site to see the effect.

Note: When you create a document, do not use the SYSTEM account, or create an Office document with an error

As shown in the following:

When you create a new document, you'll be presented with a menu that prompts you to create a new Office document.

It also provides a preview of the Office document, as shown in.

Clicking to open the document will provide an effect similar to that of Office desktop, which will let you forget that this is a Web program, as if it were a desktop version of Office.

If you cannot access it, check to see if the client can resolve the OWA address.

Reference Documentation:

Http://technet.microsoft.com/en-us/library/jj219455.aspx

Http://technet.microsoft.com/en-us/library/ff431687.aspx

OWA-related PowerShell commands

Http://technet.microsoft.com/zh-cn/library/jj219457.aspx