Technical Architecture

The iCasework product suite is made up of n-tier / server-centric (browser based, thin-client) components. There are a number of ways we can install iCasework within your organisation, depending on how many servers you have available or how you have your firewalls configured.

We can implement iCasework on one, two or three servers (when using Customer Portal) and an overview of each scenario is listed below.

Servers to be used are the:

• Database server
• External (Public) Application Server using HTTP/HTTPS
• Internal (Intranet) Application Server using HTTP/HTTPS

The diagram below provides an overview of the logical architecture for a standard, three server implementation of iCasework's thin-client applications (Customer Portal, Frontline Portal and Manager/Coordinator Portal).


fig.1
Fig.1 shows Customers connecting to the External Application Server over the Internet, whilst Frontline Staff and Managers will connect to the Internal Application Server.


It is possible to remove the need for the External Application Server in the DMZ, by utilising a Reverse Proxy Server. This would mean that both the Customers, Frontline Staff and Managers would connect to the same Internal Application Server, with Internet access managed via the Reverse Proxy. This option is shown in fig. 2.


fig.2

iCasework can be successfully deployed in a virtualised environment.