how mashzone manages the logged user?

Hi,

all the mashzone users are stored in the internal database and get comfortable managed via the mashzone administration gui.

Actually there is no extended monitoring utility to provide session or user information for the mashzone system. What you can do is to activate the JMX Agent for the tomcat server and take a look at the standard catalina mbean to get a more detailed view to active session and server status.

Please visit http://tomcat.apache.org/tomcat-6.0-doc/monitoring.html jmx configuration guide.

Best regards

Thomas

Hi,

I see in \ARIS MashZone\system\tomcat\logs folder a file named MashZone-Session.log.

This file is empty now. How can i made it active? I hope I'll see in sessions logged on Mashzone.

Thanks in advance.

William

Hi William,

your suggestion is right, but at the moment the functionality depends on the mashzone version you are using.

Initially this log was used for development purposes and was also active in the first mashzone 1.0.0., but gets inoperative in following release.

In the the upcoming mashzone release it is going to be active again and the logfile gets automatically filled.

Best regards

Thomas

Thank you Thomas,

Now we use 1.0.1 version. We'll try in other way to obtain session information until the new version.

When will you release the new version? Do you have any idea?

Best regards

William

Hi William,

at the moment, we are working hard on the latest details of the upcoming release.

So it looks already quite good, and i think we will be able to announce it in this quarter yet.

But we still have to pass our qm circles, so i am absolutely not able to provide you a halfway reliable disclosure about the release date.

Best regards

Thomas

Hi Thomas,

we'll wait for the next version.

What kind of DB use Mashzone? I'll want to take just a look in tables, and try to catch the information on sessions and users.

Thanks for infos.

Best regards

Hi William,

it is no secret that mashzone uses an embedded derby database, but it is not in our interest to publish internal information about this database and its schema, completely apart from supporting any request or work against it.

I am sure you can understand our point of view.

Best regards

Thomas