Installing and configuring Office Web Apps – Part 2

This post is part of a series.

Installing and configuring Office Web Apps – Part 1 – About Office Web Apps installatino and service application proxy group configuration

Installing and configuring Office Web Apps – Part 2 – This article

Exploring Office Web Apps

I have deployed Office Web Apps into my test farm. I use two web applications, letitknow and letitknowext with two different proxy groups as following:

Proxy groups and web apps
Proxy groups and web apps

My External Web application

On the external web application I am interested in two site collection features:

  • Office Web Apps
  • Open Documents in Client Applications by Default
Office Web Apps feature
Office Web Apps feature

This means the scope for these are the site collection. Good to know.

Office Web Apps feature

Activating or deactivating the Office Web Apps feature affects the Menu of a document.

Office Web Apps feature activated
Office Web Apps feature activated
Office Web Apps feature deactivated
Office Web Apps feature deactivated

Open Documents in Client Applications by Default feature

At first strangely, activating or deactivating the Office Web Apps feature does not have any effect on the behaviour when you click on the document name. It can be activated, deactivated the document always opens in the browser (the right kind of document of course, meaning excel powerpoint, word) if a user clicks on the name, and mind you users like to do that. I was a bit puzzled for a minute, then realised that there is another new feature there, among the site collection features, the Open Documents in Client Applications by Default. This controls what happens on a click. In disabled state, the documents open in the browser, when enabled a client application is used by default.

Document library settings

Additionally to the default open site collection feature, in a document library Advanced Settings page there is an option called Opening Documents in the Browser. The possible values are Open in the client application, Open in the browser, Use the server default (Open in the client application). The last one is the default, and the other two basically overrides the feature settings on the site collection. This gives us a bit more flexibility.

Document library default open behaviour in advanced settings
Document library default open behaviour in advanced settings

With this and the feature, there are 6 possible settings variation.

Open in the client application Open in the browser Use server default
Open in client application feature activated Client Browser Client
Open in client application feature deactivated Client Browser Browser

Cache and cache database

As I went to Central Admin site > Application management > View all site collections and selected the letitknowEXT webapp I found a new site collection, Office_Viewing_Service_Cache.

OWA cache site collection
OWA cache site collection

First of all, it uses the one and only same content database of this web app. After that I opened this, only managed to do it using the my farm administrator user (from the screenshot you can tell, my setup user can open this too).

I found 3 document libraries, and the one with the name cache was most interesting with 5 items.

OWA cache site all site content
OWA cache site all site content

In the cache folder I found files related to document rendering separated in folders according to which day I opened the files first in the browser. Then I uploaded a new document, opened in browser then confirmed, that cache library got a new folder with one item in there. The cache is used by the Word Viewing service and the PowerPoint Service application.

Cache document library
Cache document library

The cache is scoped on web application level, if I create new site collections and all use OWA, every site collection will use only this one as cache.

I used powershell to retrieve current cache settings and used the GUI also to double check.

In Central administration I went to Application management > Site Collection Quotas and Locks, then selected the letitknowEXT web application and the Office_Viewing_Service_Cache site collection.

Cache site collection limit in CA
Cache site collection limit in CA

The default limit is 100 GB.

The same limit in Powershell:

$cacheEXT = Get-SPOfficeWebAppsCache | Where-Object {$_.url -eq “http://letitknowext/sites/Of

fice_Viewing_Service_Cache”}

$cacheEXT.quota

Get-SPOfficeWebAppsCache
Get-SPOfficeWebAppsCache

To change the limit I used the Set-SPOfficeWebAppsCache commandlet.

Set-SPOfficeWebAppsCache
Set-SPOfficeWebAppsCache

The same on the GUI.

Changed cache site collection quota in CA
Changed cache site collection quota in CA

Finally, I wanted to move this cache into another content database, which means a site collection move between content databases, with the help of the Move-SPSite commandlet.

$cacheDB = New-SPContentDatabase -WebApplication “http://letitknowext” -Name “Cache”

$cacheEXT = Get-SPOfficeWebAppsCache | Where-Object {$_.url -eq “http://letitknowext/sites/Of

fice_Viewing_Service_Cache”}

Move-SPSite -DestinationDatabase cache -Identity $cacheEXT

Move Office Web Apps cache to another content database
Move Office Web Apps cache to another content database

In central admin my content databases on my external web application looked like this, with OWA cache in a new content database.

Move Office Web Apps cache content database in CA
Office Web Apps cache content database in CA
Advertisements

1 thought on “Installing and configuring Office Web Apps – Part 2”

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s