Hi Naveen,

Run "[dspace]/bin/dspace" from the command line and it will give you a 
list of all available options. There's also detailed documentation on 
the new "dspace" command at:

https://wiki.duraspace.org/display/DSDOC4x/Command+Line+Operations

In that documentation, you'll see that normal "stat-*" commands can now 
simply be run as:

[dspace]/bin/dspace stat-*

There are a variety of other commands that also can be run from this 
"dspace" script (see the docs). In most scenarios you no longer need to 
directly call *dsrun*. But, there is still a "[dspace]/bin/dspace dsrun" 
command just in case you ever need to directly call a java class.

- Tim

On 9/24/2014 9:35 AM, Naveen Srinivasan wrote:
> Hi Tim,
>
> Thanks . Please confirm the below thing,
>
> You have mentioned that , *the older "dsrun" command is now replaced
> with: **[dspace]/bin/dspace dsrun [command]*
> *
> *
> Still do we need to use dsrun ,prefixed with dspace as " dspace
> dsrun[command] " or its just " dspace [command] "  because I am not able
> to find the dsrun file anywhere in the directory.Is that understood
> internally by the system?
>
> Can i get updated stat-* files  ? Command in the stat-* files**
> is***dsrun org.dspace.app.statistics.CreateStatReport -r stat-initial .*
> *
> *
> I believe i need to update the commands in the stat-* files as* dspace
> dsrun [command] . *Is that right?
>
> Regards,
> Naveen
> Illinois Institute of Technology
> Graduate (MCS)
> Mob : (312) 774-1687
>
> On Tue, Sep 23, 2014 at 9:56 AM, Tim Donohue <[email protected]
> <mailto:[email protected]>> wrote:
>
>     Hi Naveen,
>
>     In more recent versions of DSpace (including DSpace 3.x), these
>     older stat-* commands have been replaced by a single "dspace"
>     commandline script ([dspace]/bin/dspace).
>
>     So, the commands should now be:
>
>     [dspace]/bin/dspace stat-general
>     [dspace]/bin/dspace stat-monthly
>     [dspace]/bin/dspace stat-report-general
>     [dspace]/bin/dspace stat-report-monthly
>
>     Additionally, the older "dsrun" command is now replaced with:
>
>     [dspace]/bin/dspace dsrun [command]
>
>     So, you will need to update your cron jobs to use this new syntax.
>
>     - Tim
>
>
>     On 9/23/2014 9:40 AM, Naveen Srinivasan wrote:
>
>         Hello Everyone ,
>
>         In the Repository ,When I click the Administrative section
>         -->Statistics
>         page ,i am getting the message *as " There are currently no reports
>         available for this service. Please check back later."
>         *
>
>         I came to know that I need to setup the cron jobs to run this
>         ,For the
>         cron job to run we need files such as dsrun ,stat-* files in the
>         bin folder.
>
>         I am using Dspace *3.1 * version (Linux environment). I am not
>         able to
>         find dsrun and stat-* files in the bin directory .
>
>         Cron job:
>
>         0 1 * * * [dspace]/bin/stat-general
>         0 1 * * * [dspace]/bin/stat-monthly
>         0 2 * * * [dspace]/bin/stat-report-__general
>         0 2 * * * [dspace]/bin/stat-report-__monthly
>
>         As I am not able to find the dsrun and stat * files in version 3.1 ,
>         Please let me know whether the dsrun is supported in the version
>         3.1 and
>         above,if yes whats the procedure to run the statistics file.
>         Thanks in
>         advance.
>
>
>         Note : I got the dsrun and stat files from lower version bin
>         folder ,but
>         its not successful.
>
>         Regards,
>         Naveen
>         Illinois Institute of Technology
>         Graduate (MCS)
>         Mob : (312) 774-1687 <tel:%28312%29%20774-1687>
>
>
>         
> ------------------------------__------------------------------__------------------
>         Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
>         Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS
>         Reports
>         Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
>         Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
>         
> http://pubads.g.doubleclick.__net/gampad/clk?id=154622311&__iu=/4140/ostg.clktrk
>         
> <http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk>
>
>
>
>         _________________________________________________
>         DSpace-tech mailing list
>         [email protected].__net
>         <mailto:[email protected]>
>         https://lists.sourceforge.net/__lists/listinfo/dspace-tech
>         <https://lists.sourceforge.net/lists/listinfo/dspace-tech>
>         List Etiquette:
>         https://wiki.duraspace.org/__display/DSPACE/Mailing+List+__Etiquette
>         <https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette>
>
>

------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette

Reply via email to