Recently in Analytics Category

I mentioned the ALI Interoperability Matrix (login required) in the Publisher 6.5 post, and realized that I don't always go to the official site to check compatible versions of the Aqualogic stack; instead I just use a locally saved copy because it's quicker to pull up. 

Obviously, the locally saved snapshot can get out of date over time, but it's nice to have when you need it in a pinch (having been on sites that don't allow you to connect to their network).

If you want an Excel copy of the matrix, you can download it here.  Keep in mind it's only current as of the end of August 2008, but for prior versions of the portal, the information should be pretty static. For the latest version, visit one.bea.com (while it lasts).

In Analytics, there aren't many options to filter the reports well - some reports allow filtering on a user property, some on an auth source, and some on communities.

It's the latter one that I found myself needing when I wanted to create Community Analytics Reports, filtered on a certain set of communities (we're using lots of Experience Definitions, so since that wasn't an option to filter on, I figured I'd create an Analytics Report that just filtered on all communities within each Experience Definition).

Problem is, Analytics 2.1 has a bug that prevents you from browsing and selecting multiple communities in a folder. So when trying to configure a Community Traffic Report and using the Browse button here:

... you just got this when navigating to a folder with a bunch of communities in it:

The standard BEA (Oracle?) party line is that this bug is fixed in Analytics 2.5 (which I'm sure it is), and to just search for communities here.  But unfortunately 2.5 only works with the 6.5 portal, and many of you aren't ready to make that move (drop us a line when you are!).

Fortunately, there's a (relatively) easy fix after the jump!