The implementation of an i-Con Integration Framework allows the following:

 

• Manage all integration from a single point
• Logging and automatic problem detection is enabled from a central point
• Notifications of problems via email and sms immediately a problem is detected
• Versioning of all interfaces with roll-back

 

i-Con supports all of the integration patterns, namely:

 

Request / Response

When an application requests a service from another application and waits for a response before processing can continue.

 

Publish and Subscribe

When no requirement for a system to wait for a response before continuing; Publisher is when an event takes place in a system which needs to be made available to other systems, and Subscribe where a system or systems request information to update themselves.

 

SOA (Service Orientated Architecture)

This is a standard way to expose information and functions online, generally implemented as a web service.

 

Normal batch processing

Generating or processing large volumes of transactions to/from flat files or queues

 

i-Con Monitor

This is a separate process that ensures high availability and may be configured to automatically restart in the event of a failure, and also performs the following functions:
• Restart interfaces on same server or Disaster Recovery server in the event of a failure
• Send notifications in the form of sms or email in the event of a failure
• View and manage i-Con events and messages