You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@lenya.apache.org by Amna & Kiran <bo...@yahoo.com> on 2005/05/10 10:44:14 UTC
a plea to qMax
Hi
We know we've been bothering u a lot, but ,can't help it :( Sorry.
But plz guide us as to how to run tht perl code u've provided
on "ContentImportHowTo" in wiki Lenya tutorials.
We are new to perl, have read a couple of tutorials and what we r doing while
compiling it is as follows:
We are providing the following parameters in the code:
............................
....
# defaults
.
.
.
$args{'pub-path'}="C:\ProjectBS\src\apache-lenya-1.2.2-
src\build\lenya\webapp\lenya\pubs\default";
$args{'NODEPATH'}="C:\ProjectBS\src\apache-lenya-1.2.2-
src\build\lenya\webapp\lenya\pubs\default\content\authoring\tutorial";
$args{'FILENAME'}="D:\file.xml";
.................
............
And still we are getting the msg:
"Some required arguments missing (pub-path, NODEPATH, FILENAME)
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org
Re: a plea to qMax _thnx
Posted by Amna & Kiran <bo...@yahoo.com>.
qMax <qmax <at> mediasoft.ru> writes:
> This script is for use under linux,
> It will not work under windows because of pathnames.
> I'll try to modify it a bit, but i could not test it,
> because dont use windows for lenya.
>
Thnx 4 the info.
we posted tht "runs on linux" bit on the "contentImportHowto" wiki page.
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org
Re: a plea to qMax
Posted by qMax <qm...@mediasoft.ru>.
Tuesday, May 10, 2005, 3:44:14 PM, Amna & Kiran wrote:
AK> Hi
AK> We know we've been bothering u a lot, but ,can't help it :( Sorry.
AK> But plz guide us as to how to run tht perl code u've provided
AK> on "ContentImportHowTo" in wiki Lenya tutorials.
AK> We are new to perl, have read a couple of tutorials and what we r doing while
This script is for use under linux,
It will not work under windows because of pathnames.
I'll try to modify it a bit, but i could not test it,
because dont use windows for lenya.
--
qMax
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org
Re: clear down best practice
Posted by Peter Shipley <ps...@nomensa.com>.
Lee Carroll wrote:
> I've added a wiki page with the script
>
> http://wiki.apache.org/lenya/ClearDown
>
> Any problems let me know
Looks, good can't wait to start using it.
Thanks
Pete
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org
Re: clear down best practice
Posted by Lee Carroll <le...@aol.com>.
> I think people are always interested :)
>
> I know I am.
>
I've added a wiki page with the script
http://wiki.apache.org/lenya/ClearDown
Any problems let me know
Lee C
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org
Re: clear down best practice
Posted by Peter Shipley <ps...@nomensa.com>.
Lee Carroll wrote:
> I've not filed an enhancement as it seems that the future lies
elsewhere.
>
> For the present I've written a perl script which clears down back up
> versions and log task history older than a given date.
>
> runs in various modes (report,delete , archive)
>
> if anyone interested I can post on
I think people are always interested :)
I know I am.
Pete
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org
Re: clear down best practice
Posted by Lee Carroll <le...@aol.com>.
>>> You might want to file an enhancement bug, whereas the implementation of
>>> JCR will make this implementation redundant.
I've not filed an enhancement as it seems that the future lies elsewhere.
For the present I've written a perl script which clears down back up
versions and log task history older than a given date.
runs in various modes (report,delete , archive)
if anyone interested I can post on
Lee C
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org
Re: clear down best practice
Posted by "Gregor J. Rothfuss" <gr...@apache.org>.
Peter Shipley wrote:
> Michael Wechner wrote:
>
>> You might want to file an enhancement bug, whereas the implementation of
>> JCR will make this implementation redundant.
>
>
> How will the move to a JCR implementation affect historical changes
> (edits)? It seems to me there might be reason to never delete an
> editorial change .. ever. Would this be catered for ?
the import facilities into JCR would have to take care of this (and will)
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org
Re: clear down best practice
Posted by Peter Shipley <ps...@nomensa.com>.
Michael Wechner wrote:
> You might want to file an enhancement bug, whereas the implementation of
> JCR will make this implementation redundant.
How will the move to a JCR implementation affect historical changes
(edits)? It seems to me there might be reason to never delete an
editorial change .. ever. Would this be catered for ?
>> files in
>> [publication]/logs/tasks
> I think these are the least important and can normally be deleted on
> a regular basis, unless you want to track how people used the system.
These seem best to be categorised in to year/month.
e.g.
[publication]/logs/tasks/year/month/
or even
[publication]/logs/tasks/year/month/day
depending on frequency of usage
as you say, storage is cheap and I for one never like deleting things.
Put them on one side, just in case, but not delete.
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org
Re: clear down best practice
Posted by Lee Carroll <le...@aol.com>.
Thanks Andreas,
your workflow action fits the bill
Lee C
----- Original Message -----
From: "Andreas Hartmann" <an...@apache.org>
To: <us...@lenya.apache.org>
Sent: Wednesday, May 11, 2005 10:40 AM
Subject: Re: clear down best practice
> Lee Carroll wrote:
>> In terms of the workflow history records are their any performance
>> implictions for large and growing xml files?
>
> There will proably be minimal performance issues with very large files,
> but that would only occur if you trigger the workflow automatically
> (I guess no human being will edit and publish a document a couple of
> thousand times). That issue would only affect the overall performance
> if you
>
> - have lots of documents with thousands of states in the history
> - invoke actions which involve workflow operations on a lot of
> these documents
>
> The live performance of the site should not be affected at all.
>
>> If they are performance issues can I get way with removing the all but
>> the latest workflow state?
>
> Yes, that should be no problem since the state machine does not
> consider the history.
>
>> Ideally this would take place at a configurable point in the worklow life
>> cycle. (a house keep job after publication?)
>
> Actually I see no need to have this feature in the Lenya core.
> If you need it in your publication, you could probably implement
> a workflow action and add it to certain transitions of the workflow
> schema:
>
> http://lenya.apache.org/apidocs/1.2/org/apache/lenya/workflow/Action.html
>
> -- Andreas
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
> For additional commands, e-mail: user-help@lenya.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org
Re: clear down best practice
Posted by Andreas Hartmann <an...@apache.org>.
Lee Carroll wrote:
> In terms of the workflow history records are their any performance
> implictions for large and growing xml files?
There will proably be minimal performance issues with very large files,
but that would only occur if you trigger the workflow automatically
(I guess no human being will edit and publish a document a couple of
thousand times). That issue would only affect the overall performance
if you
- have lots of documents with thousands of states in the history
- invoke actions which involve workflow operations on a lot of
these documents
The live performance of the site should not be affected at all.
> If they are performance issues can I get way with removing the all but
> the latest workflow state?
Yes, that should be no problem since the state machine does not
consider the history.
> Ideally this would take place at a configurable point in the worklow
> life cycle. (a house keep job after publication?)
Actually I see no need to have this feature in the Lenya core.
If you need it in your publication, you could probably implement
a workflow action and add it to certain transitions of the workflow schema:
http://lenya.apache.org/apidocs/1.2/org/apache/lenya/workflow/Action.html
-- Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org
Re: clear down best practice
Posted by Lee Carroll <le...@aol.com>.
In terms of the workflow history records are their any performance
implictions for large and growing xml files?
If they are performance issues can I get way with removing the all but the
latest workflow state?
Ideally this would take place at a configurable point in the worklow life
cycle. (a house keep job after publication?)
Lee C
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org
Re: clear down best practice
Posted by Michael Wechner <mi...@wyona.com>.
Lee Carroll wrote:
> workflow history records
> Files in [publication]/content/workflow/history/authoring/
they need to be kept, otherwise your document's workflow will be gone.
>
> lots of backup content files (the guionlydisplays the last 10)
> publication]/rcbak/content/authorig/[a content
> file]/index_en.bak[timestamp]
right, the RCML is listing only 10, whereas IIRC this is configured
within the
Java class (which would actually make sense to put into publication.xconf).
IIRC unfortunately the BAK files of the older versions (>10) are not being
deleted, which probably would make sense to do.
Also it probably would make sense to save only the differences and not
the whole copy.
You might want to file an enhancement bug, whereas the implementation of
JCR will make this implementation redundant.
>
> files in
> [publication]/logs/tasks
I think these are the least important and can normally be deleted on
a regular basis, unless you want to track how people used the system.
>
> I'm not sure if this is exhaustive but they doseem to be growing !
yes, on the other hand harddisks have become cheap ;-)
HTH
Michi
--
Michael Wechner
Wyona Inc. - Open Source Content Management - Apache Lenya
http://www.wyona.com http://lenya.apache.org
michael.wechner@wyona.com michi@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org
Re: clear down best practice
Posted by "Gregor J. Rothfuss" <gr...@apache.org>.
Lee Carroll wrote:
> workflow history records
> Files in [publication]/content/workflow/history/authoring/
>
> lots of backup content files (the guionlydisplays the last 10)
> publication]/rcbak/content/authorig/[a content
> file]/index_en.bak[timestamp]
>
> files in
> [publication]/logs/tasks
>
> I'm not sure if this is exhaustive but they doseem to be growing !
there is currently no feature to expire old revisions, what with disk
space being cheap and all.. enter a feature request in zilla with some
details. i'd think this will become an implementation detail of the
underlying store (JCR) eventually
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org
Re: clear down best practice
Posted by Lee Carroll <le...@aol.com>.
workflow history records
Files in [publication]/content/workflow/history/authoring/
lots of backup content files (the guionlydisplays the last 10)
publication]/rcbak/content/authorig/[a content file]/index_en.bak[timestamp]
files in
[publication]/logs/tasks
I'm not sure if this is exhaustive but they doseem to be growing !
Lee C
----- Original Message -----
From: "Michael Wechner" <mi...@wyona.com>
To: <us...@lenya.apache.org>
Sent: Tuesday, May 10, 2005 3:02 PM
Subject: Re: clear down best practice
> Lee Carroll wrote:
>
>> Hello,
>>
>> I'm begining to notice a build up of workflow and version history in our
>> lenya publications.
>> What is the best approach to deleting /archiving these historical
>> records?
>
>
> which records/files/directories in particular?
>
> Michi
>
> --
> Michael Wechner
> Wyona Inc. - Open Source Content Management - Apache Lenya
> http://www.wyona.com http://lenya.apache.org
> michael.wechner@wyona.com michi@apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
> For additional commands, e-mail: user-help@lenya.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org
Re: clear down best practice
Posted by Michael Wechner <mi...@wyona.com>.
Lee Carroll wrote:
> Hello,
>
> I'm begining to notice a build up of workflow and version history in
> our lenya publications.
> What is the best approach to deleting /archiving these historical
> records?
which records/files/directories in particular?
Michi
--
Michael Wechner
Wyona Inc. - Open Source Content Management - Apache Lenya
http://www.wyona.com http://lenya.apache.org
michael.wechner@wyona.com michi@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org
clear down best practice
Posted by Lee Carroll <le...@aol.com>.
Hello,
I'm begining to notice a build up of workflow and version history in our
lenya publications.
What is the best approach to deleting /archiving these historical records?
Is their a history manager class ?
Are they any other transactional records which grow and grow?
Cheers Lee C
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org
Re: a plea to qMax
Posted by Lee Carroll <le...@aol.com>.
Qmax might be better to comment but the script is expecting two params
passed in on the cmd line. It tests for these and dies if not their.
It looks like you are setting some variables up in the script? This is not
needed just pass the strings in when you execute the script. Looks like qmax
has also wriiten a test switch (-t ) so things can be quite safe
to run as a test use:
lenyaimport.pl -t
"C:\ProjectBS\src\apache-lenya-1.2.2src\build\lenya\webapp\lenya\pubs\default\content\authoring\tutorial"
"D:\file.xml"
to run for real:
lenyaimport.pl
"C:\ProjectBS\src\apache-lenya-1.2.2src\build\lenya\webapp\lenya\pubs\default\content\authoring\tutorial"
"D:\file.xml"
Note i've just copied your filepaths, I guess it won't work if these are
wrong.
----- Original Message -----
From: "Amna & Kiran" <bo...@yahoo.com>
To: <us...@lenya.apache.org>
Sent: Tuesday, May 10, 2005 9:44 AM
Subject: a plea to qMax
> Hi
> We know we've been bothering u a lot, but ,can't help it :( Sorry.
> But plz guide us as to how to run tht perl code u've provided
> on "ContentImportHowTo" in wiki Lenya tutorials.
> We are new to perl, have read a couple of tutorials and what we r doing
> while
> compiling it is as follows:
>
> We are providing the following parameters in the code:
> ............................
> ....
>
> # defaults
> .
> .
> .
> $args{'pub-path'}="C:\ProjectBS\src\apache-lenya-1.2.2-
> src\build\lenya\webapp\lenya\pubs\default";
> $args{'NODEPATH'}="C:\ProjectBS\src\apache-lenya-1.2.2-
> src\build\lenya\webapp\lenya\pubs\default\content\authoring\tutorial";
> $args{'FILENAME'}="D:\file.xml";
> .................
> ............
>
> And still we are getting the msg:
> "Some required arguments missing (pub-path, NODEPATH, FILENAME)
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
> For additional commands, e-mail: user-help@lenya.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org