Loopback Modules

In cases where an application or other process resides on the same physical host as an iWatch-monitored database, this traffic will not traverse the network and would therefore not be visible to iWatch under a default implementation. Optional loopback modules address this limitation by permitting the monitoring of TCP/IP traffic within the local host.

Loopback operation is also recommended whenever iWatch data will be used for Audit & Compliance purposes, as this provides the necessary means to monitor local activity even if none is normally present or authorized.

Please refer to the chart below for Loopback Availability by OS:

OS Availability
Solaris 8, 9 Available for all iWatch versions
Solaris 10 Available for Solaris 10 Updates 2, 3, and 4 only. Please note that earlier Update levels of Solaris 10, such as Update 1, are not currently supported. All iWatch Release versions supported.
HP UX Available for PA/RISC systems only; no current support of Itanium. All iWatch versions supported
Windows 2000, 2003, XP Available with iWatch 6.0 Only.
AIX Not Required. AIX offers equivalent native functionality.
Linux (Red Hat, SUSE) Not required. Linux offers equivalent native functionality.