Skip to main content
Kofax

Install KCM Core Web Services Interface ASP.NET

Article # 3035091 - Page views: 73

Issue

You want to install the KCM Core Web Services Interface for ASP.NET

 

Solution

The manual misses instructions for installing the KCM Core Web Services interface ASP.NET. This How-To article describes the steps for installing the KCM Core Web Services interface ASP.NET. 

Prerequisites

The following Windows Server features must be installed:

  • 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 (with default options)

 

Installation
  1. Create a folder for hosting the web services interface. For example C:\KCM_Core_WSI
  2. Copy the contents of ..\KCM\Programs\<version>\ITP Server\Apis\Web Services\ to the folder of step 1.
  3. Open IIS Manager.
  4. Fold open Sites.
  5. Right-click Default Web Site -> Add Virtual Directory
  6. Enter the Alias. Alias is the site name. 
      http://localhost/<alias>. 
    Enter the physical path. Physical path is the folder from step 1. E.g.
      C:\KCM_Core_WSI.
    1.png
  7. Click Ok to close the dialog
  8. Right click the new virtual folder and click Convert to Application.
  9. In the 'Add Application' dialog click Select... and select the .NET v4.5 Classic Application pool. Click Ok to close the dialog.
    2.png
Configuration
  1. In the folder of KCM Core WSI, open web.config.
  2. Optionally change ITPServerHost to the hostname of the KCM machine. This is only required if KCM Core WSI is deployed on a different machine than the KCM machine.
  3. Change the key ITPServerPort to the port of the KCM Core instance. To determine the port number, the following formula can be used: 3001 + ( n * 2 ).
    E.g. the port for instance 1 is 3001+(2*1)=3003.
  4. Change executionTimeout to 3600.
    Although not required, it is recommended to uncomment the keys LogFile, MaxLogFileSizeKB, MaxLogCount. This will enable logging. Only the key LogFile must be changed to a location for the log file. It is recommended to configure the logfile in the KCM Core log folder. For example: 

    <add key="LogFile" value="D:\KCM\Work\5.5\Instance_01\core\Log\KCM\WSI\itpserverws.log"/>


    example configuration:
    <?xml version="1.0" encoding="utf-8" ?>
    <configuration>
      <appSettings>
        <add key="ITPServerHost" value="localhost"/>
        <add key="ITPServerPort" value="3003"/>
        <add key="LogFile" value="D:\KCM\Work\5.5\Instance_01\core\Log\KCM\WSI\itpserverws.log"/>
        <add key="MaxLogFileSizeKB" value="1024"/>
        <add key="MaxLogCount" value="10"/>
      </appSettings>
      <system.web>
        <httpRuntime executionTimeout="3600"/>
      </system.web>
    </configuration>
    

NOTE: The identity that runs the .NET v4.5 Classic Application Pool needs write access to the configured log folder.

Testing

The WSDL of the web service can be retrieved from http://<hostname>/<alias>/itpserverwrapped.asmx?wsdl
For example if kcmcore is used as the alias name.
   http://localhost/kcmcore/itpserverwrapped.asmx?wsdl

Further reading

For more information on using the KCM Core WSI, refer to the Core Developer's Guide. The hosted documentation can be accessed via https://docshield.kofax.com/ia-platform.html.

Level of Complexity 

High

 

Applies to  

Product Version Build Environment Hardware
Kofax Communications Manager 5.3 and newer n/a n/a n/a

References

Add any references to other internal or external articles

  • Was this article helpful?