General discussion

Locked

Architecture for User behaviour tracking

By okujava ·
Hi!
I have to develope sw components (java) to evalueta sw + user behaviour. we have a "simple" three tier architecture, but the problem is, i should implement an architecture so that the programmer do not need to do anything (!) for me, but I should become all the information I can get. On the following site you can find a brief description of my problem with some explanations. The red boxes are my components, that gather data and evaluate it.
For details, please visit:
http://www.ars-ev.de/problem/problem.html
I would welcome any suggestions!
great thanks!

s.okujava

This conversation is currently closed to new comments.

31 total posts (Page 1 of 4)   01 | 02 | 03 | 04   Next
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Architecture for User behaviour tracking

by okujava In reply to Architecture for User beh ...

Point value changed by question poster.

Collapse -

Architecture for User behaviour tracking

by maxwell edison In reply to Architecture for User beh ...

Session Tracking is a flexible, lightweight mechanism that enables stateful programming on the web. It has a general implementation that serves as a basis for more sophisticated state models, such as persistent user profiles or multi-user sessions. A session is a series of requests from the same user that occur during a time-period. This transaction model for sessions has many benefits over the single-hit model. It can maintain state and user identity across multiple page requests. It can also construct a complex overview of user behavior that goes beyond reporting of user hits.

Session Tracking gives servlets and other server-side applications the ability to keep state about a user as the user moves through the site. Server-side applications can use this facility to create more stateful user experiences and track who's doing what on the site.

Java Web Server maintains user state by creating a Session object for each user on the site. These Session objects are stored and maintained on the server. When a user first makes a request to a site, the user is assigned a new Session object and a unique session ID. The session ID matches the user with the Session object in subsequent requests. The Session object is then passed as part of the request to the servlets that handle the request. Servlets can add information to Session objects or read information from them.

Using Session Tracking from a Servlet:

The following example uses the doGet method from a servlet that prints the number of times users access a particular servlet.

See this link for the example and the entire article explaining the process:

http://mysun-mail.sun.com/system/doc/session_track/SessionTr.html#130

(REMOVE SPACES from the pasted URLs.)

----------

Third party solution - Determine different user group behaviour:

http://www.global-linxs.de/content/pdf/Tracker.pdf

Good luck,

Maxwell

Collapse -

Architecture for User behaviour tracking

by okujava In reply to Architecture for User beh ...

Poster rated this answer

Collapse -

Architecture for User behaviour tracking

by okujava In reply to Architecture for User beh ...

thanks, maxwell edison. has anybody any suggestions to other points?

Collapse -

Architecture for User behaviour tracking

by Joseph Moore In reply to Architecture for User beh ...

Here is another link to a page on Session Tracking with Java:
http://www.apl.jhu.edu/~hall/java/Servlet-Tutorial/Servlet-Tutorial-Session-Tracking.html
(please remove any spaces)

As is this link also:
http://java.sun.com/docs/books/tutorial/servlets/client-state/session-tracking.html
(again, remove any spaces)

And this is a 6 page article with sample HTML script:
http://www.developerfusion.com/show/2076

hope this helps

Collapse -

Architecture for User behaviour tracking

by okujava In reply to Architecture for User beh ...

sorry, session tracking is not new (see above) and not sufficient to solve the problem. sorry

Collapse -

Architecture for User behaviour tracking

by Java Guru In reply to Architecture for User beh ...

I am not completely sure of what you are trying to accomplish. It looks like you are basically trying to implement a system where you can determine the behavior of users on the sytem. Is that right?

User requests can be captured on the web server or the app server. The web server will get you aggregate data, while the app server will enable you to detail all of the requests made by individual users (if session tracking is enabled).

Tracking in the DB tier is possible, but it may not help you. All it will have will be the queries that your app server is generating. If it is a custom written web app, then you should know all of the possible queries that can generated for any particular URL request.

Here is the thing that makes it difficult. VOLUME. Here at TechRepublic, we once hired a company that went through all of our data and categorized users for us. I was not involved in the project, but I did hear some of the discussions involved in it.

One of the things thatwas mentioned was a change to the server request logs to include any user/parameter data that could be of importance. This is HUGE.

In the end, I am not sure it was worth the effort or the $$$ (IMHO).

For the most part, you can get a picture of what your users are doing by generating your own reports on your own request logs. This task is made much easier when related items are grouped by directory.

I am not sure if any of this is in the slightest bit helpful.

Some more information that would be useful in helping your problem would be:
types of user behavior that you anticipate
scale/clicks that are inticipated
more specifics on the architecture (user tier is?)


BTW, I would prever to stay away from RMI. If this is a real-time system for user interraction, then system logs would be much less of an inconvenience for your users (JMS is pretty nifty).

Collapse -

Architecture for User behaviour tracking

by okujava In reply to Architecture for User beh ...

i know about the problem of huge data, but in such a project u can't avoid it. and rmi is already a part of the project. sorry

Collapse -

Architecture for User behaviour tracking

by PENGUINSRULE In reply to Architecture for User beh ...

Well you won't like my answer, but I'm a VMS Bigot and I have to promote the OS. VMS supports Java on the Alpha platform, and it will on Itanium. OpenVMS and SecureVMS are the most secure operating systems in production, and are C2 and B2 compliant respectively. You can literally audit about anything you want to, you can audit particular devices, files, ports, anything - you can find out anything a user is doing with anything. NT/2000 is a *copy* of VMS, but not near as robust or secure at all, and UNIX security - (I'm laughing)..

I did answer your question because VMS will provide a solution to allow you to track everything, and according to DEFCON hacker conventions is not penetrable.

What else could you want?

Collapse -

Architecture for User behaviour tracking

by okujava In reply to Architecture for User beh ...

Sorry, but it's not acceptable for me to let the system run only on one plattform.
I find your answer interesting, but it doesn't suite the question (java technology).

cheers

s.okujava

Back to Web Development Forum
31 total posts (Page 1 of 4)   01 | 02 | 03 | 04   Next

Related Discussions

Related Forums