Changes between Version 169 and Version 170 of ippToPsps
- Timestamp:
- Oct 5, 2011, 3:14:48 PM (15 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
ippToPsps
v169 v170 85 85 {{{ippToPsps}}} contains numerous separate programs that work together to process and load IPP data (in the form of batches) to the datastore, monitor the progress of those batches and then perform the necessary cleanup of the various temporary files once those batches are safely merged into the PSPS database. 86 86 87 == Setting up a loading machine == 88 89 Although this can be changed in the config file, {{{ippToPsps}}} uses a 'scratch' MySQL database on {{{localhost}}} while processing. So, to run {{{ippToPsps}}} a local MySQL server should be up-and-running, with a database created as the {{{ipp}}} user for use by {{{ippToPsps}}}. The default name for this is {{{ipptopsps_scratch}}}. 87 == Loading == 88 89 90 === Setting up a loading machine === 91 92 Although this can be changed in the config file, {{{ippToPsps}}} uses a 'scratch' MySQL database on {{{localhost}}} while processing. So, to to any loading, a local MySQL server should be up-and-running, with a database created as the {{{ipp}}} user for use by {{{ippToPsps}}}. The default name for this is {{{ipptopsps_scratch}}}. 90 93 91 94 Because {{{ippToPsps}}} uses this local database as a scratch database, there are large number of inserts and deletions, meaning large log files. For this reason, it is important to configure MySQL to store its data on a local partition, and not {{{/var}}} as is the default. For example, on {{{ipp005}}}: … … 113 116 }}} 114 117 115 == Loading == 118 At the time of writing, scratch databases are set up on the following IPP hosts: 119 120 {{{ 121 ipp005 122 ipp006 123 ipp007 124 ipp033 125 ipp034 126 }}} 127 128 {{{ipp005}}} in fact has ''three'' scratch databases, so three clients can potentially be run on this machine. This is because {{{ipp005}}} is where the DVO databases are currently stored, so clients running on the same machine have a much higher throughput. 129 130 === Running === 116 131 117 132 Loading data means running the {{{load.py}}} program while passing it the relevant configuration 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:
