Tyrell Perera wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Samisa Abeysinghe wrote:
Chathura C. Ekanayake wrote:
Registry already supports some activity logs based on the resource,
action, user, etc.
We are also planning to implement notification/eventing system for
registry, which triggers registered listeners on certain events.
Different event listeners can register for events (e.g. mail, IM). May
be we can implement a report generator also as a listener, which
aggregates events and generates reports on that data.
But I am not aware of the exact details Mashup server is expecting
from the reports. If they can give detailed list of information
expected from the reports we can figure out which reports can be
generated from the registry. There may be actions/data that is outside
the registry context, which cannot be captured in registry reports.
+1 for evaluating if it can be done at registry level.
Given the way mashup uses registry, my understanding is that, mashup
should be able to piggyback on registry. We should try and minimize
functionality duplication.
Agreed. We can implement the 'Reporting Engine' and the associated API
inside the Registry, along with some default reports.
For instance, in the case of mooshup.com, it would be useful to have
reports on;
- User Activity for a given period
- New User registrations for a given period
- Resources (Mashups) in the server for a given user
- User Login and Access reports
- Number of edits on resources (Mashups) by user(s)
Most above events can be captured by registry. Some of them are already
supported in registry activity logs.
One exception is the user login reports which depends on the realm used
in the mashup server.
If it uses the RegistryRealm, we can capture those events as well. As
now user manager code is also in registry svn we might be able to give
such reporting functionality directly in the default realm level. I will
investigate more into details of this.
Thanks,
Chathura
The list can go on, so we need to decide on a few, really useful reports
to give an administrator by default. When we need customized domain
specific reporting, we will include them in the Mashup distro as .jrxml
files. We can use the infrastructure provided by the registry to compile
them at runtime.
Since some things like Activity reporting is already present in the
registry, we can just leverage the export facility of Jasper Reports to
allow these reports in PDF and spreadsheet formats.
Tyrell
- --
Tyrell Perera
Senior Software Engineer; WSO2, Inc.; http://www.wso2.com/
email: [EMAIL PROTECTED]; cell: +94 77 302 2505
"Oxygenating the Web Service Platform."
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFH6RaAehFdPcgGx7oRAsi2AJ9jdJmbt+sl6JtCw7PJuBMzdvqQJACeOGoe
8uSfzwz+uVBLVg3XESRPBEo=
=k/xO
-----END PGP SIGNATURE-----
_______________________________________________
Mashup-dev mailing list
[email protected]
http://www.wso2.org/cgi-bin/mailman/listinfo/mashup-dev
_______________________________________________
Mashup-dev mailing list
[email protected]
http://www.wso2.org/cgi-bin/mailman/listinfo/mashup-dev
