Repository Logs?

[Former Community Member]

Hi all,

I'm trying to use the recording feature of LCCS. Here are the steps I've been following so far:

1- I registered a repository endpoint with a WebDAV URL which I can map as a network drive in my Windows 7.

2- I created a session with two users.

3- Closed the session with both users.

4- Waited 15 minutes.

But no files were saved on my repository.

Is there a way to see what's going on, like an action log or something?

Thanks in advance.

[DrAlexGor]

1) LCCSREPO.jar doesn't seem to log anything, but since WebDAV works off of apache/httpd then you could look at apache's error logs ( the equivalent /var/log/apache2/error_log). This might say something like "Couldn't PUT your ...............zip file because I didn't have permissions to write to that location". You can also just look through the latest stuff written to your apache logs to see if Adobe servers are even sending you anything ( Windows equivalent to "tail -f /var/log/apache2/error_log" ).

2) Did you look at the debug logger info that Adobe provides *during* a recording session? Using the following in your app:

Just like you, I'm also waiting for Adobe guys to give us some more logging info when something goes wrong on their server.

[Former Community Member]

Now I got it working by setting isRecording = false with a button click.

But as you can imagine, this is not what I'm looking for. The owner shouldn't be forced to click a button before leaving the session.

Any ideas on possible causes of the service not saving the recording after a session ends?

[nzezelj]

Hi barisyesilcicek,

In reference to the button that sets isRecording = false, are you referring to the SDK's recording/playback demo application?  This client application is just a demo made as a reference guide.  Yes, isRecording is set to true to start a recording, and is set to false to stop a recording, but this does not need to happen through button clicks.  It could be made 100% programmatic. 

Furthermore, if the application is being recorded, the LCCS service will stop the recording and publish it to your WebDAV server when the recorded application stops.  So, this should work.  Are you sure your application is being recorded?  And are you sure your application has stopped? 

If you haven't already, I highly recommend you read through our recording documentation at http://learn.adobe.com/wiki/display/lccs/10+Recording+and+Playback.  In particular, section 10.3. could be of interest to you.

Thanks,

Nikola

[Former Community Member]

Hi there,

It does create the recording after the session ends, but the session

doesn't end until 5 minutes after the last client leaves the room (this is

so that we can make sure the room is really out-of-use rather than because

of a reconnect, and avoid startup costs).

You can control recording more granularly from your server by using the

server integration libs to stop the recording.

nigel

[DrAlexGor]

Yup we face the same thing, wait 5 min AND make sure no clients are connected OR click a button to end it.

A much better solution is what Nigel mentioned or a simple JavaScript that catches your user's closing of the browser window, in which case you can send "isRecording=false" and then let the SWF close It'll take some ExternalInterface and JS interaction but shouldn't be too bad ( and of course testing that it works on all the browsers you support )

[Former Community Member]

Thank you all for responses. Howewer, I found the solution in a different way, I set the timeout to 15 seconds from the room console, now it saves the record to my WebDAV after the session ends. Probably I will want to increase this limit though.

P.S. It didn't work until this modification to the room was made (the whole 5 minutes thing).