Using log features

[gvdm]

Hi to all

I have a OpenKM 6.2 Community Edition on my Debian Wheezy VM.
I need to access the log files to read them and to write on them through API. In the reference guide I cannot see any log API.

How should I solve this problem?
Should I develop a module which reads and writes directly on the log files and expose some API from that or should I use the OpenKM's log module (where can I find it?) and build only the APIs for that?

Thanks
Giulio

[jllort]

I do not understand why log api for write. Really all operation done by openkm are automatically write in log. If you make something outside I do not know if has much sense store in openkm log. Really is external operation I will be better store in other place.

About access to log in read mode, actually there's not any method exposed for it. Can be, yes, but sincerally for it I suggest directly make queries to database than use webservices api or similar, will be more fast and flexible than across api.

[gvdm]

I do not understand why log api for write.

I'll edit OpenKM source adding other functions my client asked and I'd like to add the logging functionalities to this custom module. I hoped there would be some API like OKMLog.write() which could help me manage this problem.

About access to log in read mode [...] I suggest directly make queries to database than use webservices api or similar

Could you please tell me where can I find the OpenKM Log DB?

Thank you
Giulio

[pavila]

I can't understand why do you need to write into de OpenKM activity log. Please, can you explain a bit your request?

[jllort]

Log table is OKM_ACTIVITY table under control of ActivityDAO class ( could be exposed under ws easilly, but I do not suggest it ).

If you have extended OpenKM with some general purpose feature, we'll be pleased to add in community trunk. That will give you the security that we will respect the source code in the way while you upgrade application will continue being compatible with your code ( if you've made extension you can be sure about it ). Finally include or not features depends if we consider are general purpose or not. If are so much specific we can not include in trunk branch, but can be share as code example for other community user.

[gvdm]

If you have extended OpenKM with some general purpose feature, we'll be pleased to add in community trunk.

At the moment I'm at a initial phase (I'm determining what I will have to do in the developement phase) so I haven't written anything. In the future I will be happy to share my developement goals with the OpenKM Community

One information: is there any "standard" way to develop an extension for OpenKM or I'll have to build a new module which uses the OpenKM's APIs to interact with it?

[jllort]

Tell me what you want to doing and then I will give orientate you better. Use api ensure can be compatible with any upper OpenKM version because is always maintained. That mean actual patch in your source code will be valid for upper versions and continue working. But depend what you want to build will be better add in core. If it's interesting thing we add in core and maintaining in future. Explain the features and we will suggest you some direction.