Skip to main content

Install ComposerUI for ASP.NET

Article # 3035603 - Page views: 152


The manual for installing ComposerUI for ASP.NET is outdated. This How-To article contains the updated steps for installing ComposerUI for ASP.NET.



Prequisites Windows Server role.png

The following Windows Server features must be installed:

  • .NET Framework 3.5 Features -> .NET Framework 3.5 (includes .NET 2.0 and 3.0).
  • .NET Framework 4.x Features -> .NET Framework 4.x

The following Windows Server role with features must be installed:

  • Web Server (IIS)
    • Web Server (IIS) -> Web Server -> Application Development -> ASP.NET 4.x
    • Web Server (IIS) -> Web Server -> Authentication -> URL Authorization
    • Web Server (IIS) -> Web Server -> Authentication -> Windows Authentication


01). Run as administrator the installer from ..\KCM\Programs\<version>\Legacy Installers\ITPOnlineASP.NET.exe
02). Click Next.
03). Choose the ComposerUI applications folder location and click Next.
04). Choose the ComposerUI virtual directory name and ComposerUI virtual directory physical path and click Next.
05). Choose the ComposerUI public directory name and ComposerUI public directory physical path and click Next.
06). Click Next to start the installation.
07). Click Finish to close the installer.


Note: The installer from KCM 5.4 and higher is affected by a defect. If you are using KCM 5.4 or higher,  then first follow the instructions from this KB Article (link) before proceeding.

Set file system permissions 

The following file permissions must be set. The default locations for the mentioned locations are:
ComposerUI virtual directory: C:\inetpub\wwwroot\itp
ComposerUI public directory: C:\inetpub\wwwroot\itppublic
ComposerUI applications folder: C:\ITPOnLineApps
ComposerUI log folder: C:\ITPOnLineApps\itplog
ComposerUI sessiondata: C:\ITPOnLineApps\sessiondata

Location Account Permission type
ComposerUI virtual directory Administrators Full Control
  IIS_IUSRS Read & Execute
  IUSR Read & Execute
  NETWORK SERVICE Read & Execute
  Users Read & Execute
ComposerUI public directory Administrators Full Control
  IIS_IUSRS Modify
  IUSR Read & Execute
  Users Read & Execute
ComposerUI applications folder Administrators Full Control
  Users None
ComposerUI log folder Administrators Full Control
  Users None
ComposerUI sessiondata Administrators Full Control
  Users None
Convert virtual directory to an application 

01). Open IIS Manager.
02). Right click the virtual directory and click “Convert to application” .
03). Set the application pool .NET v.4.x Classic.
04). Close the dialog.

ITP - Convert to Application.png

Configure the application pool 

01). Open IIS Manager.
02). Go to application pools.
03). ”Select “.NET v4.x Classic” and click Advanced to open the advanced properties.
04). Under “Process Model” ,change Identity to built-in account: NETWORK SERVICE.
05). Under “Process Model”, change Idle Time-out (minutes) to 0.
06). Close the dialog.
07). Under “Edit Application Pool” click Recycling… (while the application pool .NET v4.5x Classic is still selected).
08). Deselect “Regular time intervals (in minutes):”.
09). Tick “Specific time(s):” and enter a time outside business hours when no users are using ComposerUI for ASP.NET. For example 23:00.
10. Click next and subsequently click finish.

Configure feature delegation 

1). Open IIS Manager.
2). In the Connections panel on the left-hand side, select the element that represents the entire web server.
3). In the middle panel, double click Feature Delegation to open the Feature Delegation configuration page.

Feature Delegation.pngFeature Delegation Configuration.png

Configure ComposerUI 

01). Go to the ComposerUI applications folder (default C:\ITPOnlineApps).
02). Extract the contents of to Newsample (C:\ITPOnlineApps\NewSample)
02). Run Internet Explorer as administrator.
03). Open http://localhost/itp/configure.aspx. If you changed the virtual directory name from itp to something else, then you must replace itp with the different virtual directory name.
Note: This page can only be opened when internet explorer is opened as administrator.
04). Optionally, if KCM is installed on a different machine, change ITP/Server Host to the hostname of the KCM server. Otherwise you can use localhost.
05). Change ITP/Server port to 3003 for instance 1. If you want to use a different KCM instance, then you can use the following formula. 3001 + (2 x instance number).
E.g. for instance 3. 3001 + ( 2 x 3 ) = 3007.
06). Click Submit to save the new settings and click continue.
07). In the application name text box at the bottom of the page enter “NewSample” (without quotes).
08). Click Submit to save the new settings and click continue.
09). Click on the link Deploy located on the right of NewSample.
10). You have finished the post-configuration.

Test the installation 

You can use the following URL for testing the installation.
http ://localhost/itp/app/newsample/modelbegin.aspx?model=<rep uri>

For testing document template Example Letter DKC Blue from project InstallationTest (rep%3A//localhost:2587/documenttemplate/installationtest/example letter dkc blue):
http ://localhost/itp/app/newsample/modelbegin.aspx?model=rep%3A//localhost:2587/documenttemplate/installationtest/example%20letter%20dkc%20blue


Level of Complexity 



Applies to  

Product Version Build Environment Hardware
Kofax Communications Manager All versions      



Article # 3035603
  • Was this article helpful?