Articles (filtered by 'Installation')

Filter by subject:

Running i-lign In-house

If your company decides to host i-lign inhouse, you may find the following articles useful. They describe the process for installation by the i-lign team, and for self-installation, as well as the technical requirements.

System Requirements

The system requirements for servers are only applicable if you are hosting the i-lign server yourself. Please see our Knowledge Base article on Running i-lign In-house for more details.

For externally hosted deployments, only the client requirements apply.

Single Sign On example using IIS

This article describes one way you can connect IIS to Tomcat on Windows and delegate Single Sign On authentication to IIS.


This example assumes you already have the following:

Restoring Databases

Restoring a previously hosted database.

Single Sign On architecture

It is possible to integrate i-lign into your authentication infrastructure by delegating the authentication to a native web server or reverse proxy installed on the same server as i-lign.

Our standard approach is for the front end web server or proxy to communicate to the Tomcat application server via the AJP binary protocol. There are AJP modules available for web servers like IIS and Apache.

This approach allows you to pick and configure an integration method that suits your network.

Installing another instance

When installing another i-lign instance on an existing i-lign server, the process is the same but you will need to take note of the following points:


The following series of articles provides information about installing a production and test instance of i-lign on Windows, and installing databases.