Viewing Article

No StarNo StarNo StarNo StarNo Star | Oct 25 2017, 6:30 AM | Print
Configuring Platoatlas on newer OS
APPLICABLE AUDIENCE: PLATO Intranet Applications, United Kingdom and Australasia.

General Information
PlatoAtlas serves pages via Windows and Internet Information Server (IIS) whose security settings, features and defaults can change over time. Use this article to configure Platoatlas manually in most environments.

1) Ensure required IIS features are installed.
Follow this article to ensure IIS has required features:

2) Create an Application Pool

An Application Pool is the host process for one or more Web applications. You can see these host processes running as w3wp.exe in Task Manager.

To create an Application Pool in IIS:

  • Go to the Application Pools section in the Connections Tree
  • Right click and select Add Application Pool
  • Create with the name of your choice (e.g. PlatoAtlas)
  • Choose .NET Framework 4.0 and Integrated Managed Pipeline Mode

Once you've created the Application Pool, select it in the list and click on Advanced Settings.

3)Set the Account Identity

Set the Identity for the Application Pool to LocalSystem or an account with access to the Middle Tier and database. While LocalSystem has good access to local machine resources, the user identity you choose here is passed to your Platoatlas server, which can avoid the need for the DCOMCNFG step below if you specify a user identity with access to the Middle Tier and database.

4) Enable 32-bit

If you are using the wc.dll ISAPI module on a 64 Bit machine, set Enable 32 Bit Applications to True so that the 32 bit wc.dll can work. The Platoatlas .NET Module can run natively in 64 bit mode but we still recommend you run in 32 bit mode.

5) Create a Virtual Directory

  • In the Connections tree, go to YourMachine | WebSites | YourWebSite and click Add Application
  • Enter the name of the virtual directory (e.g. PlatoAtlas) and the path to the Web directory
  • Specify the Application Pool you created in Step 2 above.

6) Set Virtual Directory Authentication

In the Authentication option in the virtual's configuration, enable:

  • Anonymous Authentication
  • Basic Authentication
  • Windows Authentication

7) Enable wc.dll ISAPI

Due to the security settings in IIS, generic ISAPI and CGI extensions (and ASP and ASP.NET even) are not allowed to execute. Without this setting, any access will result in 404.1 errors or offers to sownload wc.dll.

  • Go to the Machine Root in the Connections tree
  • Select ISAPI and CGI Restrictions (IIS Settings)
  • Click and add your mapping to wc.dll in your Web path.
8) Ensure access to temp folder

Make sure that the temp folder configured in the Configuration/WebConnectionConfiguration/TempPath setting in web.config (.NET Handler) or the Path setting in wc.ini (ISAPI) exists and that it has full read and write access for the Application Pool's user account.

This is vitally important in order for IIS and the Application Pool to be able to read and write data in that path. It's also vitally important that your PlatoAtlas Server - potentially running under COM impersonation - has full right rights in this folder as well.

User Account Control Note that UAC can affect access to local folders. We highly recommend that if you use custom accounts for either the Application Pool or COM Impersonation, that you EXPLICITLY add the account to the permissions to avoid problems with the Administrators group under UAC (which effectively leaves you not an administrator).