What is Office Web Apps Server?
Office Web Apps Server is an Office server product that provides
browser-based file viewing and editing services for Office files. Office
Web Apps Server works with products and services that support WOPI,
the Web app Open Platform Interface protocol. These products, known as
hosts, include SharePoint 2013, Lync Server 2013, and Exchange Server
2013.
An Office Web Apps Server farm can provide Office services to multiple
on-premises hosts, and you can scale out the farm from one server to
multiple servers as your organization’s needs grow. Although Office Web
Apps Server requires dedicated servers that run no other server
applications, you can install Office Web Apps Server on virtual machine
instances
It is easier to deploy and manage Office Web Apps within your
organization now that it is a stand-alone product. If you deploy
SharePoint 2013, for example, you no longer have to optimize the
SharePoint infrastructure to support Office Web Apps, which in
earlier versions was tightly integrated with SharePoint Server 2010.
You can also apply updates to the Office Web Apps Server farm
separately and at a different frequency than you update SharePoint
2013, Exchange Server 2013, or Lync Server 2013. Having a stand-
alone Office Web Apps Server farm also means that users can view
or edit Office files that are stored outside SharePoint 2013, such as
those in shared folders or other websites. This functionality is
provided by a feature known as Online Viewers.
How Office Web Apps Server works
A key part of the new integration model is a new public
WOPI API that Office Web Apps Server uses to
communicate with hosts. Office Web Apps Server
fetches and manipulates files using the WOPI API. We
often refer to Office Web Apps Server as a WOPI App.
Hosts must recognize WOPI requests from WOPI apps.
Here’s an example of the data flow between the browser,
SharePoint Server 2013, and Office Web Apps Server.
Office Web Apps Server usage scenarios
How WOPI works:
1.The user wants to view or open a document that is stored on a host that runs Exchange Server 2013,
SharePoint 2013, or Lync Server 2013
2.The host directs the browser to a special page that contains an IFRAME that connects to a page on
Office Web Apps Server.
3.The page initiates a request to Office Web Apps Server. The request includes the file name, access
token, and the URL of the file location on the host
4.5.Office Web Apps Server responds to the request by getting the document from the host and then
rendering the document in the IFRAME. The user can then view or edit the document in the web
browser.