Skip to main content
Version: 4.2.5

iCore web applications hosted in IIS

The iCore AS2 Server application and iCore Invoke are web applications hosted in Microsoft Internet Information Services (IIS). This topic covers some general considerations that may apply for certain versions of IIS.

Considerations regarding IIS 7.0 installation

There are some things you need to consider before installing IIS 7.0. If you intend to use iCore Invoke or iCore AS2 server application with default configurations, you need to also enable the Windows feature HTTP activation (if http binding is used).

IIS 7.0 requirements

  • IIS 6 Management Compatibility
    • IIS 7.0 must have the feature “IIS 6 Management Compatibility” installed.
    • Enable options "IIS Metabase and IIS 6 configuration compatibility".
  • ASP.NET Support - ASP.NET must be installed and activated.

IIS application pool requirement

The application pool that hosts iCore Invoke must have following configuration:

  • .NET framework version - must be set to v.4.0.30319 or later.
  • Enable 32-bit applications.
note

When installing IIS 7.0 on a 64-bit platform, the application pool where the web service is installed must support 32-bit applications. This is done by changing the property Enable 32-bit applications in the advanced settings of the application pool to True.

Post-installation considerations

When creating Nodes in the iCore system from the hosted iCore applications, the permissions of the IIS application pool identity is used to access the Node directory. This means that read/write permissions to the Node directory of the target iCore system must be set up.

If the application pool uses a custom account for the application pool identity, this account must have read and write permission to the Node directory in the iCore system. If using a built-in account, such as “ApplicationPoolIdentity”, these permissions must be assigned to the predefined group “IIS_IUSRS”. The Application pool identity can be found in the advanced settings of the Application Pool.

To add permission to the Node directory, select a Node directory in Windows Explorer and add the “IIS_IUSRS” – group/custom account to the Access Control List (ACL) of the directory:

  1. Open Windows Explorer.
  2. Select the Node directory.
  3. Right-click the directory and select Properties.
  4. Select the Security tab.
  5. Click Edit and then Add.
  6. If you are using the “IIS_IUSRS”, click Locations and make sure that you select your machine. If you are using a custom account, select the location for the account.
  7. In the "Enter the object names to select" box, enter "IIS_IUSRS" or the custom account name.
  8. Click Check Names and click OK.
  9. Assign full access to this user.
Notes
  • For earlier versions of IIS, change the permission to the account that the IIS runs (default: Network service).
  • If you are running Windows 2008 R2 SP1, you must start the scripts from a PowerShell console or PowerShell ISE.
  • If you are running iCore on a x64 OS, you must start the x64 PowerShell console.
  • A bug in Microsoft PowerShell installation prevents users from starting a PowerShell script using File Explorer if the scripts has arguments.
  • To run a script from within the PowerShell console, type: & "<path to .ps1-script>".