Versions Compared

Version Old Version 9 New Version Current
Changes made by

Documentation Reviewer

Kimberly Onnen

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Easy Find and Replace: {"id":"91e7fcd7-f6a2-47a5-b0f4-b52287cde72e","find":"/hamburger menu/i","replace":"menu","search-type":"case-insensitive","replace-title":false}

To find a complete list of system requirements across all the Signature modules, refer to the Signature System Requirements document found on the Product Download page on Signature Resources. https://portal.key2act.com/customer-portal/downloads

Note

If you will be integrating with ServiceChannel and this is a new installation, you will need to install to an HTTPS using port 443. If you currently are installed using port 80, please contact Key2Act WennSoft Support for information on updating to port 443.

Signature Version Compatibility

  • Signature 2015 R2 SP3
  • Signature 2016 R3 SP1
  • Signature 2018 R2
  • Signature 2018 R3

Install the .NET Core Windows Server Hosting bundle

  1. Install the .NET Core Windows Server Hosting bundle on the hosting system. The bundle installs the .NET Core Runtime, .NET Core Library, and the ASP.NET Core Module. The module creates the reverse proxy between IIS and the Kestrel server. If the system doesn't have an Internet connection, obtain and install the Microsoft Visual C++ 2015 Redistributable before installing the .NET Core Windows Server Hosting bundle. Important! If the hosting bundle is installed before IIS, the bundle installation must be repaired. Run the hosting bundle installer again after installing IIS.
  2. Restart the system or execute net stop was /y followed by net start w3svc from a command prompt. Restarting IIS picks up a change to the system PATH made by the installer.

...

If you will be using the Mapping feature, you will also need to obtain a Google or Bing Mapping API key: