<p>If you're upgrading to Exchange 2013, the changes to roles, increased memory, CPU and storagerequirements might leave you reeling. And when you consider the extra server components you need ifyou want to take advantage of every new feature in Exchange 2013, it could be off-putting. To helpease the stress and help you decide if you need it, we'll break down what Office Web Apps Server2013 is.</p><p>Prior to Exchange 2007, if you wanted to view Microsoft Office format attachments from withinOutlook Web Apps (or OutlookWeb Access, as it was known back then), you would need a copy of Office installed on thecomputer that is reading the email. Not only would you need Office installed, but you'd also haveto download a copy of the attachment before you could read it. Exchange 2007 brought the ability toview the attached word document in the Web browser, all of which was rendered on the ExchangeServer on behalf of the end user.</p><p>Oracle Outside In is the underlying technology that supports the WebReady document viewer builtinto Exchange 2007, 2010 and 2013. Oracle Outside In is a third-party tool for Exchange thatrenders Office documents.Understanding the Office Web Apps Server 2013 role</p><p>One of the server products included with Office 2010 was an addition called Office Web AppsServer. Built to compete with Google Apps' online editors, Office Web Apps Server hooked intoSharePoint 2010 and Microsoft's SkyDrive service to allow end users to edit Office documents withina Web browser.</p><p><a href="http://searchexchange.techtarget.com/tip/Does-your-enterprise-need-Office-Web-Apps-Server-2013">Keep reading...</a></p>