Accelerate Tridion GUI

Introduction

This document describes 4 simple actions that should be taken by every Tridion Infrastructure consultant when installing Tridion on a new environment. These actions will speed up IIS' performance and are valid actions for any other Web Site, not Tridion only.

Prerequisites

Tridion 5.1 SP4, Windows 2003

1. Bind IIS to an IP Address

This is not always possible due to network restrictions, such as network balancing and fail-over requirements, where a server must be available through multiple IP addresses, but will be possible for at least 90% of the deployments.

Open the IIS Manager Console (Administrative Tools -> Internet Information Services (IIS) Manager)

Browse through the left pane to the Tridion Content Manager Web Site (IIS Manager -> <YourServerName> -> Web Sites -> Tridion Content Manager)

Right-click it and select properties from the context menu

In the Web Site Properties dialog, click on the drop-down for "TCP Port:" and select the IP address the server should bind to.

2. Enabling Content Expiration

When enabling content expiration, IIS will add a date to the HTTP Headers telling browsers by when should the content be reloaded from the server, effectively instructing the browser to use its cached version of each object. In other words, IE will use its cache as much as possible and minimize the amount of traffic between the browser and the server.

Browse through the Tridion Content Manager Web Site folders and perform the next step for each of the following folders and subfolders of these:

/Images
/Library (except /Library/ASP and /Library/Commands)
/Resource
/Views/Javascript
/Views/XSL

All other folders should not have content expiration set.

Go to the HTTP headers tab and check "Enable content expiration", and set it to expire after 10 days, as shown in the next figure.

3. Use a custom error page for 401;1 and 401;2 errors

Due to its stateless nature, Tridion will not cache session information on the server-side code, which means that every action the user performs must be preceded by an authentication. In itself, this is not much of an issue, but if your multiply each authentication request by 2Kb (the size of IIS' default error page), you can easily get to a really big number of Kilobytes that are being transferred, literally for nothing.

By defining your own custom error page, you can define a much smaller .html file that will minimize the amount of traffic sent throguh the network.

Go to the Custom Errors tab and select the 401;1`HTTP error. Click Edit

Enter [Tridion Install Dir]\web\blank.htm (or use any other page you created yourself)

Repeat these steps for the 401;2 error.