Matt's SharePoint Blog: Office Web Apps Server Preview and SharePoint 2013 Machine Translation Services

I followed the below steps to get Office Web Apps (OWA) and machine translation services working on a Windows Server 2008 R2 server running SharePoint 2013.

You will require a dedicated server to run the Office Web App Server Preview software as it cannot be installed on the same machine as ShasrePoint.

Check Machine Translation service is running on the SharePoint server

Create a Machine Translation Services Service Application in Central Administration if not already present.

Setup server roles on the Office Web Apps Sever

In powershell run as admministrator the below commands, this will install the required roles and services on the server

Run:
Import-Module ServerManager

And then run:
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

Install Office Web Apps on the server

Download OWA from the Microsoft downloads centre,
Copy the disc image file locally to the server.
Run the setup file
You’ll have to import the Office Web Application module into Windows PowerShell for all servers that will run Office Web Apps Server Preview. To do so, open the Windows PowerShell prompt as an administrator, type the below command, and then press ENTER.

Import-Module OfficeWebApps

The Import-Module loads the Office Web Server cmdlets into your instance of Windows PowerShell. To verify that the cmdlets were loaded, type the following command at the PowerShell prompt and then press ENTER:

Get-Command "*Office*"

A list of all cmdlets in the OfficeWebApps module is displayed. To get help with any of the cmdlets, type the following command:

Get-Help cmdletname

Create the Web Apps Server Farm

The code in the following creates a new Office Web Apps Server farm that consists of a single server. The URL you specify for –InternalURL is the name of the server that runs Office Web Apps Server Preview, such as http://servername. The –AllowHttp parameter configures the farm to use HTTP, and the –EditingEnabled parameter enables editing in Office Web Apps Preview when it is used together with SharePoint 2013 Preview.

New-OfficeWebAppsFarm –InternalURL http://owa2013.bramble-cc.local –AllowHttp -EditingEnabled

Verify the Farm Created Successfully

After the farm is created, details about the farm are displayed in the Windows PowerShell prompt. To verify that Office Web Apps Server Preview is installed and configured correctly, use a web browser to access the Office Web Apps Server Preview discovery URL, as shown in the following example. The discovery URL is composed of the value that you assigned to the InternalUrl parameter when you configured your Office Web Apps Server farm, and it is followed by /hosting/discovery.

http://servername/hosting/discovery

If Office Web Apps Server Preview works as expected, you should see a Web app Open Platform Interface (WOPI)-discovery XML file in your web browser. The first few lines of that file should resemble the following example:

<?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&>" />

Run an iisreset /restart /noforce

The above will create a single server Office Web Apps farm, to create a multiple server farm or to add an external address for internet translation then refer to the following article for full instructions - http://technet.microsoft.com/en-us/library/jj219455(v=office.15)

Create the Binding between SharePoint 2013 and Office Web Apps Preview

On the SharePoint 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 Preview traffic. For this test environment, you must specify the –AllowHTTP parameter to allow SharePoint 2013 Preview to receive discovery information from the Office Web Apps Server Preview farm by using HTTP. If you forget to specify –AllowHTTP, SharePoint 2013 Preview will try to use HTTPS to communicate with the Office Web Apps Server Preview farm and this command will fail.

New-SPWOPIBinding -ServerName owa2013.bramble-cc.local -AllowHTTP

Set the Zone

Office Web Apps Server Preview uses the concept of 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 Server 2013. By default, SharePoint Server 2013 Preview uses the Internal HTTPS zone, which won’t work in this scenario because HTTPS is not configured. Therefore, you must run the following command on the SharePoint server to change the zone to Internal HTTP.

Set-SPWopiZone –zone “internal-http”

The above will configure SharePoint 2013 to use translation services over HTTP, to configure HTTPS please refer to the full article below.
http://technet.microsoft.com/en-us/library/ff431687(v=office.15)