nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

Auditing

marco_altieri

Hi,

I'm working with the auditing service in Alfresco 3.4.7 EE.

Unfortunately, as far as I know, starting from the 3.4 the audit database couldn't be a accessed directly and some useful tables like alf_audit_fact are not available anymore.

I'm wondering if someone has already developed something to export the auditing information to a "universe" accessible by a standard business intelligence product (like Business Object).

Regards,
Marco

Find more posts tagged with

Comments

afaust

Hello,

the Audit component was refactored in 3.4 and audit information is now stored in the alf_prop_* tables as far as I know. Accessing the Alfresco DB schema directly is considered bad practice exactly for this reason - the abstraction layer of Alfresco services has remained stable throughout this change.

I am not aware of an export module in the community - depending on the audit application I'd expect that a generic export utility would not be that useful, as audited data might need specific processing if exported to an outside universe.

Regards
Axel

marco_altieri

Hi Axel,

thank you for your reply.

Do you think that ti could be feasible to customise the method:

Map<String, Serializable> audit(
            final AuditApplication application,
            Set<String> disabledPaths,
            final Map<String, Serializable> values)

in AuditComponentImpl to store audit data in an external database (BO universe).

Thank you,
Marco

afaust

Hello,

I wouldn't do that, as this is rather complex and can affect performance significantly if done improperly . It would be best to implement a query action which transfers essential data to your external database in such a scenario.

Regards
Axel