Figure 7illustrates the case of a Clientaccessing services from an aggregating Serverthat does not support Auditing.


Figure 7– Aggregation with a non-auditing Server

In this case, each of the Serversreceives requests and creates their own audit log entry for them, with the exception of Server“B”, which does not support Auditing. In this case, Server“B” passes the audit id it receives from its Client“A” to the next Server. This creates the required audit chain. Server“B” is not listed as supporting Auditing. In a case where a Serverdoes not support writing audit entries, the entire system may be considered as not supporting Auditing.

In the case of an aggregating Serverthat does not support Auditing, the Serverwould still be required to subscribe for Audit Eventsfrom the Serversit is aggregating. In this manner, Server“B” would be able to provide all of the Audit Eventsto Client“A”, including the event generated by Server“C” and Server“D”, even though it did not generate an Auditevent.