Changes between Version 150 and Version 151 of ippToPsps

Timestamp:

Aug 3, 2011, 3:37:45 PM (15 years ago)

Author:

rhenders

Comment:

--

ippToPsps

@@ -87 +87 @@
 == Running {{{ippToPsps}}} ==
 
-{{{ippToPsps}}} is configured for use entirely by a config file (see above). So, running the software is simply a case of editing a config and passing it as the sole argument to the program, like this:
+{{{ippToPsps}}} is configured for use entirely by a config file (see above). So, running the software is simply a case of editing a config and passing it as an argument to the program, like this:
 
 {{{
@@ -94 +94 @@
 }}}
 
-The {{{./run.sh}}} prefix above is necessary to invoke the correct Java virtual machine, while including the relevant jar files in the CLASSPATH (all included in the {{{trunk/ippToPsps/Jars}}} subdir) 
+The {{{./run.sh}}} prefix above is necessary to invoke the correct Java virtual machine, while including the relevant jar files in the CLASSPATH (all included in the {{{trunk/ippToPsps/Jars}}} subdir)
+
+== Creating and publishing an 'IN' batch ==
+
+The same program is used to create IN batches, but requires one extra argument, like this:
+
+{{{
+./run.sh ipptopsps.py someConfig.xml init
+}}}
+
+This will produce an IN batch, publish it, then stop (the IN-batch MySQL tables will also be updateded in the local scratch database).
 
 == Queuing ==