[eclipselink-users] Re: What options do I have for configuring auditing

[Reinhard Girstenbrei <reinhard.girstenbrei@xxxxxxxxxx>]

Hi fcalvo@gmailcom,
if you are using Oracle Database Server you could use Fine Grained 
Auditing (FGA).
Using this you do not have to have additional database round trips to 
write the audit entries.
The person executing a statement can be identified with the database 
user name or with the client id (ECID).
Other related topics are proxy authentication and the method 
OracleConnection.setEndToEndMetrics() or when using a JDBC 3.0 compliant 
driver Connection.setClientInfo().
Other database servers might also have an auditing feature that works 
analogous.
Please provide more details if you want a more tailored answer (database 
server, jdbc driver, for both name and version, explain what you want to 
audit).

Best regards,
Reinhard


eclipselink-users-request@xxxxxxxxxxx wrote:
> Send eclipselink-users mailing list submissions to
> 	eclipselink-users@xxxxxxxxxxx
>
> To subscribe or unsubscribe via the World Wide Web, visit
> 	https://dev.eclipse.org/mailman/listinfo/eclipselink-users
> or, via email, send a message with subject or body 'help' to
> 	eclipselink-users-request@xxxxxxxxxxx
>
> You can reach the person managing the list at
> 	eclipselink-users-owner@xxxxxxxxxxx
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of eclipselink-users digest..."
>
>
> Today's Topics:
>
>    1. What options do I have for configuring auditing	of Entities
>       (fcalfo)
>    2. Calculating progress for an entity based on	data from another
>       table (Philipp Kursawe)
>    3. EclipseLink 1.1.2 Released in Galileo (Douglas Clarke)
>    4. RE: EclipseLink 1.1.2 Released in Galileo (Peter Krogh)
>    5. Cascade delete bug (221389) fixed in 2.0 line	but not 1.1
>       line? (Russ Teabeault)
>    6. Re: Cascade delete bug (221389) fixed in 2.0	line but not 1.1
>       line? (Russ Teabeault)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Tue, 23 Jun 2009 14:57:53 -0700 (PDT)
> From: fcalfo <fcalfo@xxxxxxxxx>
> Subject: [eclipselink-users] What options do I have for configuring
> 	auditing	of Entities
> To: eclipselink-users@xxxxxxxxxxx
> Message-ID: <24175205.post@xxxxxxxxxxxxxxx>
> Content-Type: text/plain; charset=us-ascii
>
>
> So it looks like these are the options currently available to support
> auditing of data events on Entities (i.e., I want to insert a row into a
> separate audit table whenever a new Foo is persisted):
>
> 1) Register an Entity method as a DescriptorEvent handler
> 2) Register a separate class as a DescriptorEvent listener
> 3) Add the @PrePersist and @PreUpdate annotations to a method on the Entity
> (or its base class) - but this is probably of limited use since it does not
> provide the DescriptorEvent so a lot of the context will not be available
> for the audit logic
>
> Are there any other options provided by EclipseLink?
>
> Also, there do not seem to be any annotations to directly configure either
> of the first two options, correct?  I'd need to use a @Customizer so I can
> get access to the ClassDescriptor and get its EventManager to add the
> listeners to, correct?
>   

--
Oracle <http://www.oracle.com>
Reinhard Girstenbrei | Senior Principal Technical Support Engineer
Phone: +498914302318 | Mobile: +491775941318
Oracle Oracle Customer Service

ORACLE Deutschland GmbH | Riesstr. 25 | 80992 München

ORACLE Deutschland GmbH, Hauptverwaltung: Riesstraße 25, D-80992 München
Geschäftsführer: Jürgen Kunz, Registergericht: Amtsgericht München, HRB 
82775
Green Oracle <http://www.oracle.com/commitment> 	Oracle is committed to 
developing practices and products that help protect the environment