[ 
http://jira.dspace.org/jira/browse/DS-321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stuart Lewis reopened DS-321:
-----------------------------

    Documentation Status: In Comments  (was: Complete or Committed)

Hi Jeff,

I've just added a couple of new commands to launcher.xml as I noticed there 
were still some references to 'dsrun org.dspace...' in the docbook.

Hopefully all docbook entries relating to dsrun can be updated now.

Thanks,


Stuart




Macintosh-7:docbook sdl$ grep "dsrun org." *
application.xml:<screen>[dspace]/bin/dsrun org.dspace.browse.IndexBrowse -f -r
application.xml:[dspace]/bin/dsrun org.dspace.browse.ItemCounter
application.xml:[dspace]/bin/dsrun org.dspace.search.DSIndexer</screen>
business.xml:          <para><literal>/dspace/bin/dsrun 
org.dspace.core.ConfigurationManager -property property.name</literal></para>
configure.xml:                                                  <entry>When 
showing the strengths, should they be counted in real time, or fetched from the 
cache. Counts fetched in real time will perform an actual count of the database 
contents every time a page with this feature is requested, which will not 
scale. If you set the property key is set to cache (&quot;true&quot;) you must 
run the following command periodically to update the count: 
<literal>/[dspace]/bin/dsrun org.dspace.browse.ItemCounter</literal>. The 
default is to count in real time (set to &quot;false&quot;).</entry>
configure.xml:                          <screen>[dspace]/bin/dsrun 
org.dspace.administer.MetadataImporter -f [xml file]</screen>
history.xml:                                    <para>DS-319 - Replace 
<literal>/dspace/bin/dsrun org.dspace.browse.ItemCounter</literal> with 
<literal>/dspace/bin/itemcounter</literal></para>
install.xml:0 4 * * * <emphasis> [dspace]</emphasis>/bin/dsrun 
org.dspace.checker.DailyReportEmailer -c
install.xml:                                            
<literal>[dspace]\bin\dsrun org.dspace.administer.CreateAdministrator</literal>
sys_admin.xml:          <para><literal>dsrun 
org.dspace.administer.CommunityFiliator --set --parent=parentID 
--child=childID</literal></para>
sys_admin.xml:                  <para><literal>[dspace]/bin/dsrun 
org.dspace.browse.IndexBrowse -f -r</literal></para>
sys_admin.xml:                  <para><literal>[dspace]/bin/dsrun 
org.dspace.browse.IndexBrowse -i</literal></para>
sys_admin.xml:                  <para><literal>[dspace]/bin/dsrun 
org.dspace.browse.IndexBrowse -r -t -p -v -x -o myfile.sql</literal></para>
update.xml:[dspace]/bin/dsrun org.dspace.administer.MetadataImporter -f


> DSpace command launcher
> -----------------------
>
>                 Key: DS-321
>                 URL: http://jira.dspace.org/jira/browse/DS-321
>             Project: DSpace 1.x
>          Issue Type: New Feature
>          Components: DSpace API
>            Reporter: Stuart Lewis
>            Assignee: Jeffrey Trimble
>            Priority: Minor
>         Attachments: dspace-shell.patch, patch-version2.patch, 
> patch-version3.patch
>
>
> In order to stop the proliferation of [dspace]/bin/scripts, and to maintain 
> parity between windows and unix, I have created a DSpace shell.
> Most scripts can be replaced with:
> [dspace]/bin/dspace {script-name}
> or
> [dspace]\bin\dspace.bat {script-name}
> E.g.
> Instead of running "[dspace]/bin/filter-media -xyz" you can run 
> "[dspace]/bin/dspace filter-media -xyz"
> I've not tested dspace.bat so it may not work.
> The scripts are defined in [dspace]/config/launcher.xml. Running the shell 
> with no parameters will display a list of known commands.
> launcher.xml looks like (just an excerpt):
>     <command>
>         <name>index-update</name>
>         <description>Update the search and browse indexes</description>
>         <step>
>             <class>org.dspace.browse.IndexBrowse</class>
>             <arguments>-i</arguments>
>             <passargs>false</passargs>
>         </step>
>         <step>
>             <class>org.dspace.browse.ItemCounter</class>
>             <passargs>false</passargs>
>         </step>
>         <step>
>             <class>org.dspace.search.DSIndexer</class>
>             <passargs>false</passargs>
>         </step>
>      </command>
>     <command>
>         <name>itemcounter</name>
>         <description>Update the item strength counts in the user 
> interface</description>
>         <step>
>             <class>org.dspace.browse.ItemCounter</class>
>             <passargs>false</passargs>
>         </step>
>     </command>
>     <command>
>         <name>metadata-export</name>
>         <description>Export metadata for batch editing</description>
>         <step>
>             <class>org.dspace.app.bulkedit.MetadataExport</class>
>         </step>
>     </command>
> </commands>
> There can be multiple steps for each command, extra parameters can optionally 
> be inserted using <arguments>-foo bar</arguments> and the arguments passed in 
> by a user can be removed from the command run if <passargs>false</passargs> 
> is inserted for a step.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.dspace.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel

Reply via email to