This content has been marked as final. Show 5 replies
application name is not one of the parameters for the AnalyticsUtil methods. It is determined based one the Webcenter Application name of the deployment.
Also, I don't realy like the idea of having to set this distinction in the method calls that register the event. For pageviews, this is no problem, since I have to add that manually to my application anyway, but it would mean I have to implement the registration of all OOTB events (like login, document download etc) manually as well.
So far, I have come up with a workaround to split the data:
I register a custom event when the login page is viewed and when the user is logged in (you need to be authenticated for all pages, except the loginpage), where I register the department with the sessionid.
Then, on a batch basis, I schedule a database job, the moves all FACTs to the "dummy" application that belongs to the selected department (based on the department registered/sessionid combination registered by the custom event).
I am now implementing this to test this workaround, but I am hoping for a cleaner way to fix this, without having to manipulate the analytics data directly in the database.