Optional Windows Server 2003 configuration

Applies to the following products: 
Questionmark Perception
Applies to the following Perception versions: 
Perception 5.2
Perception 5.1

Although your Windows Server 2003 machine will still run Perception Server without doing so, we recommend that in certain environments you may want to perform some additional configuration tasks. These can increase the speed and reliability of your installation however if you have a well specified server they may not be necessary.

What? Why?
Ensure worker processes are recycled This enables you to precisely manage faulty worker processes, ensuring that specified applications in those pools remain healthy, and that system resources can be recovered.
Assign application pools to different processors (only possible with dual processors) This can help to make your Perception Server installation more robust, secure and may also improve performance.

These tasks are described in the following sections.

Configuring IIS to recycle worker processes

If IIS is running in worker process isolation mode, you can configure IIS to periodically restart worker processes in an application pool. This setting enables you to precisely manage faulty worker processes, ensuring that specified applications in those pools remain healthy, and that system resources can be recovered. This functionality is managed from the Recycling tab of an application pools properties page.

By default IIS is configured to recycle processes after they have been inactive for a defined amount of time, measured in minutes. In the example illustrated below, this is 1740 minutes. It is also possible to force an application pool to recycle at specific times. To do so:

    1. Open IIS Manager
    2. Right-click Application Pools and select Properties
    3. The Application Pools Properties dialog is displayed

  1. In the Recycling tab, check the Recycle worker processes (in minutes) box
  2. Check Recycle worker processes at the following times and click Add
  3. In the Select time dialog box, enter a time and click OK

Repeat this procedure if you want to enter any additional application pool recycle times.

Assigning application pools to different processors

When running Windows Server 2003 on a multi processor server, it is possible to set one application pool to use one processor, and the other application pool to use the other processor. This setting can be made by changing the Processor Affinity settings in the Metabase for the second application pool. You must have Administrator rights to perform this function and this only needs to be done on the machine where Enterprise Manager is installed if you have setup Perception in a multi-tiered environment.

To change processor affinity settings:

    1. Locate the \Inetpub\AdminScripts directory. If your operating system is installed on the c:\ drive, this queue can be found in:

C:\Inetpub\AdminScripts

    1. Open a DOS Prompt and run the following command:
>adsutil set w3svc/AppPools/ApplicationPoolName/SMPAffinitized TRUE

(Where ApplicationPoolName is the name of your Application Pool - perception5, for example.)

The response will be:

SMPAffinitized : (BOOLEAN) TRUE
    1. Run the following command:

>adsutil set w3svc/AppPools/ApplicationPoolName/SMPProcessorAffinityMask 0x1

(Where ApplicationPoolName is the name of your Application Pool - perception5, for example.)

The response will be:

SMPProcessorAffinityMask : (INTEGER) 1

Additional information on changing processor affinity settings is available at:

http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/529588d3-71bc-45ea-a84b-267914674709.mspx?mfr=true