Workspace 365 uses caching to increase performance and reduce the database server load. This document describes possible caching scenarios and how to set them up.
Installing Workspace 365 on multiple web servers
This document describes required steps for using several web servers for Workspace 365, as in failover or load balancing scenarios.
The term “web farm” refers to the set of web servers servicing one domain, typically under software or hardware load balancer.
The document is focused on the main Workspace 365 application, if you want to use Business Apps Builder on several servers, make the same steps except caching setup.
Machine key changes
When using several Windows machines, it is necessarily to ensure they are using the same cryptographic keys, so session cookie created and encrypted on one server can be successfully decrypted by another.
To do that, first generate new keys using IIS Manager.
- Start IIS Manager on webserver 1 and click on “Machine Key” element in Features view.
- Uncheck “Generate a unique key for each application” checkboxes.
- Click Generate Keys.
- Insert machineKey element into system.web section of Workspace 365 web.config, copying values from the IIS keys generation form:
<machineKey validationKey="D560446BAC289260395B3B0971219158B2CEBFF0B5BD80DACADFD6A7C32AE7C29B70AB02530F9B9A2A652925C50BA96A9487B0EAA4A5D7A8125739864BBB3E43" decryptionKey="24EA2DF472FDB212F6A7D3F98FA2756555A709FFBB72D0E2" validation="SHA1" decryption="Auto" />
MachineKey element should be the same for every web server in a web farm. Note also that validation attribute should be present, despite what older articles on the Internet might state.