Propchange: uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/duccbook.html
------------------------------------------------------------------------------
svn:eol-style = native
Added: uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/duccbook.pdf
URL:
http://svn.apache.org/viewvc/uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/duccbook.pdf?rev=1858151&view=auto
==============================================================================
Binary file - no diff available.
Propchange: uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/duccbook.pdf
------------------------------------------------------------------------------
svn:mime-type = application/pdf
Added:
uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/images/BooksCasPerf.png
URL:
http://svn.apache.org/viewvc/uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/images/BooksCasPerf.png?rev=1858151&view=auto
==============================================================================
Binary file - no diff available.
Propchange:
uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/images/BooksCasPerf.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/images/BooksRaw.png
URL:
http://svn.apache.org/viewvc/uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/images/BooksRaw.png?rev=1858151&view=auto
==============================================================================
Binary file - no diff available.
Propchange:
uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/images/BooksRaw.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added:
uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/images/BooksRawPerf.png
URL:
http://svn.apache.org/viewvc/uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/images/BooksRawPerf.png?rev=1858151&view=auto
==============================================================================
Binary file - no diff available.
Propchange:
uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/images/BooksRawPerf.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added: uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/images/Nodepool1.jpg
URL:
http://svn.apache.org/viewvc/uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/images/Nodepool1.jpg?rev=1858151&view=auto
==============================================================================
Binary file - no diff available.
Propchange:
uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/images/Nodepool1.jpg
------------------------------------------------------------------------------
svn:mime-type = image/jpeg
Added: uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/images/Nodepool2.jpg
URL:
http://svn.apache.org/viewvc/uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/images/Nodepool2.jpg?rev=1858151&view=auto
==============================================================================
Binary file - no diff available.
Propchange:
uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/images/Nodepool2.jpg
------------------------------------------------------------------------------
svn:mime-type = image/jpeg
Added: uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/images/Nodepool3.jpg
URL:
http://svn.apache.org/viewvc/uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/images/Nodepool3.jpg?rev=1858151&view=auto
==============================================================================
Binary file - no diff available.
Propchange:
uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/images/Nodepool3.jpg
------------------------------------------------------------------------------
svn:mime-type = image/jpeg
Added: uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/images/ducc-arch.jpg
URL:
http://svn.apache.org/viewvc/uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/images/ducc-arch.jpg?rev=1858151&view=auto
==============================================================================
Binary file - no diff available.
Propchange:
uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/images/ducc-arch.jpg
------------------------------------------------------------------------------
svn:mime-type = image/jpeg
Added:
uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/images/ducc-internals/db-structure.png
URL:
http://svn.apache.org/viewvc/uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/images/ducc-internals/db-structure.png?rev=1858151&view=auto
==============================================================================
Binary file - no diff available.
Propchange:
uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/images/ducc-internals/db-structure.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added:
uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/images/ducc-internals/rm-structure-1.png
URL:
http://svn.apache.org/viewvc/uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/images/ducc-internals/rm-structure-1.png?rev=1858151&view=auto
==============================================================================
Binary file - no diff available.
Propchange:
uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/images/ducc-internals/rm-structure-1.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added:
uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/images/ducc-internals/rm-structure-2.png
URL:
http://svn.apache.org/viewvc/uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/images/ducc-internals/rm-structure-2.png?rev=1858151&view=auto
==============================================================================
Binary file - no diff available.
Propchange:
uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/images/ducc-internals/rm-structure-2.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added:
uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/images/ducc-internals/rm-structure.png
URL:
http://svn.apache.org/viewvc/uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/images/ducc-internals/rm-structure.png?rev=1858151&view=auto
==============================================================================
Binary file - no diff available.
Propchange:
uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/images/ducc-internals/rm-structure.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added:
uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/images/ducc-internals/rm-structure.vsd
URL:
http://svn.apache.org/viewvc/uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/images/ducc-internals/rm-structure.vsd?rev=1858151&view=auto
==============================================================================
Binary file - no diff available.
Propchange:
uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/images/ducc-internals/rm-structure.vsd
------------------------------------------------------------------------------
svn:mime-type = application/msword
Added:
uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/images/ducc-internals/sm-structure.png
URL:
http://svn.apache.org/viewvc/uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/images/ducc-internals/sm-structure.png?rev=1858151&view=auto
==============================================================================
Binary file - no diff available.
Propchange:
uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/images/ducc-internals/sm-structure.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added:
uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/images/ducc-overview/wrapAE.png
URL:
http://svn.apache.org/viewvc/uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/images/ducc-overview/wrapAE.png?rev=1858151&view=auto
==============================================================================
Binary file - no diff available.
Propchange:
uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/images/ducc-overview/wrapAE.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added:
uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/images/ducc-parallel.png
URL:
http://svn.apache.org/viewvc/uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/images/ducc-parallel.png?rev=1858151&view=auto
==============================================================================
Binary file - no diff available.
Propchange:
uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/images/ducc-parallel.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added:
uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/images/ducc-sequential.png
URL:
http://svn.apache.org/viewvc/uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/images/ducc-sequential.png?rev=1858151&view=auto
==============================================================================
Binary file - no diff available.
Propchange:
uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/images/ducc-sequential.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added:
uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/images/ducc-webserver/Job-Details-Files.png
URL:
http://svn.apache.org/viewvc/uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/images/ducc-webserver/Job-Details-Files.png?rev=1858151&view=auto
==============================================================================
Binary file - no diff available.
Propchange:
uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/images/ducc-webserver/Job-Details-Files.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added:
uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/images/ducc-webserver/Job-Details-Performance.png
URL:
http://svn.apache.org/viewvc/uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/images/ducc-webserver/Job-Details-Performance.png?rev=1858151&view=auto
==============================================================================
Binary file - no diff available.
Propchange:
uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/images/ducc-webserver/Job-Details-Performance.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added:
uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/images/ducc-webserver/Job-Details-Processes.png
URL:
http://svn.apache.org/viewvc/uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/images/ducc-webserver/Job-Details-Processes.png?rev=1858151&view=auto
==============================================================================
Binary file - no diff available.
Propchange:
uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/images/ducc-webserver/Job-Details-Processes.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added:
uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/images/ducc-webserver/Job-Details-Specification.png
URL:
http://svn.apache.org/viewvc/uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/images/ducc-webserver/Job-Details-Specification.png?rev=1858151&view=auto
==============================================================================
Binary file - no diff available.
Propchange:
uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/images/ducc-webserver/Job-Details-Specification.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added:
uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/images/ducc-webserver/Job-Details-WorkItems.png
URL:
http://svn.apache.org/viewvc/uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/images/ducc-webserver/Job-Details-WorkItems.png?rev=1858151&view=auto
==============================================================================
Binary file - no diff available.
Propchange:
uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/images/ducc-webserver/Job-Details-WorkItems.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added:
uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/images/ducc-webserver/Jobs.png
URL:
http://svn.apache.org/viewvc/uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/images/ducc-webserver/Jobs.png?rev=1858151&view=auto
==============================================================================
Binary file - no diff available.
Propchange:
uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/images/ducc-webserver/Jobs.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added:
uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/images/ducc-webserver/Preferences.png
URL:
http://svn.apache.org/viewvc/uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/images/ducc-webserver/Preferences.png?rev=1858151&view=auto
==============================================================================
Binary file - no diff available.
Propchange:
uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/images/ducc-webserver/Preferences.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added:
uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/images/ducc-webserver/Reservations.png
URL:
http://svn.apache.org/viewvc/uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/images/ducc-webserver/Reservations.png?rev=1858151&view=auto
==============================================================================
Binary file - no diff available.
Propchange:
uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/images/ducc-webserver/Reservations.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added:
uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/images/ducc-webserver/System-Daemons.png
URL:
http://svn.apache.org/viewvc/uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/images/ducc-webserver/System-Daemons.png?rev=1858151&view=auto
==============================================================================
Binary file - no diff available.
Propchange:
uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/images/ducc-webserver/System-Daemons.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added:
uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/images/ducc-webserver/viz.jpg
URL:
http://svn.apache.org/viewvc/uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/images/ducc-webserver/viz.jpg?rev=1858151&view=auto
==============================================================================
Binary file - no diff available.
Propchange:
uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/images/ducc-webserver/viz.jpg
------------------------------------------------------------------------------
svn:mime-type = image/jpeg
Added:
uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/images/parallel-withzip.jpg
URL:
http://svn.apache.org/viewvc/uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/images/parallel-withzip.jpg?rev=1858151&view=auto
==============================================================================
Binary file - no diff available.
Propchange:
uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/images/parallel-withzip.jpg
------------------------------------------------------------------------------
svn:mime-type = image/jpeg
Added:
uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/images/sequential-withzip.jpg
URL:
http://svn.apache.org/viewvc/uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/images/sequential-withzip.jpg?rev=1858151&view=auto
==============================================================================
Binary file - no diff available.
Propchange:
uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/images/sequential-withzip.jpg
------------------------------------------------------------------------------
svn:mime-type = image/jpeg
Added:
uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/images/uima-as-pipeline.png
URL:
http://svn.apache.org/viewvc/uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/images/uima-as-pipeline.png?rev=1858151&view=auto
==============================================================================
Binary file - no diff available.
Propchange:
uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/images/uima-as-pipeline.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Added:
uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/images/uima-pipeline.jpg
URL:
http://svn.apache.org/viewvc/uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/images/uima-pipeline.jpg?rev=1858151&view=auto
==============================================================================
Binary file - no diff available.
Propchange:
uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/images/uima-pipeline.jpg
------------------------------------------------------------------------------
svn:mime-type = image/jpeg
Added: uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/installation.css
URL:
http://svn.apache.org/viewvc/uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/installation.css?rev=1858151&view=auto
==============================================================================
--- uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/installation.css (added)
+++ uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/installation.css Thu
Apr 25 17:32:43 2019
@@ -0,0 +1,119 @@
+
+/* start css.sty */
+.cmmi-10{font-style: italic;}
+.cmr-17{font-size:170%;}
+.cmr-12{font-size:120%;}
+.cmr-9{font-size:90%;}
+.cmbx-10{ font-weight: bold;}
+.cmtt-10{font-family: monospace;}
+.cmti-10{ font-style: italic;}
+.cmsl-10{font-style: oblique;}
+p.noindent { text-indent: 0em }
+td p.noindent { text-indent: 0em; margin-top:0em; }
+p.nopar { text-indent: 0em; }
+p.indent{ text-indent: 1.5em }
+@media print {div.crosslinks {visibility:hidden;}}
+a img { border-top: 0; border-left: 0; border-right: 0; }
+center { margin-top:1em; margin-bottom:1em; }
+td center { margin-top:0em; margin-bottom:0em; }
+.Canvas { position:relative; }
+img.math{vertical-align:middle;}
+li p.indent { text-indent: 0em }
+li p:first-child{ margin-top:0em; }
+li p:last-child, li div:last-child { margin-bottom:0.5em; }
+li p~ul:last-child, li p~ol:last-child{ margin-bottom:0.5em; }
+.enumerate1 {list-style-type:decimal;}
+.enumerate2 {list-style-type:lower-alpha;}
+.enumerate3 {list-style-type:lower-roman;}
+.enumerate4 {list-style-type:upper-alpha;}
+div.newtheorem { margin-bottom: 2em; margin-top: 2em;}
+.obeylines-h,.obeylines-v {white-space: nowrap; }
+div.obeylines-v p { margin-top:0; margin-bottom:0; }
+.overline{ text-decoration:overline; }
+.overline img{ border-top: 1px solid black; }
+td.displaylines {text-align:center; white-space:nowrap;}
+.centerline {text-align:center;}
+.rightline {text-align:right;}
+div.verbatim {font-family: monospace; white-space: nowrap; text-align:left;
clear:both; }
+.fbox {padding-left:3.0pt; padding-right:3.0pt; text-indent:0pt; border:solid
black 0.4pt; }
+div.fbox {display:table}
+div.center div.fbox {text-align:center; clear:both; padding-left:3.0pt;
padding-right:3.0pt; text-indent:0pt; border:solid black 0.4pt; }
+div.minipage{width:100%;}
+div.center, div.center div.center {text-align: center; margin-left:1em;
margin-right:1em;}
+div.center div {text-align: left;}
+div.flushright, div.flushright div.flushright {text-align: right;}
+div.flushright div {text-align: left;}
+div.flushleft {text-align: left;}
+.underline{ text-decoration:underline; }
+.underline img{ border-bottom: 1px solid black; margin-bottom:1pt; }
+.framebox-c, .framebox-l, .framebox-r { padding-left:3.0pt;
padding-right:3.0pt; text-indent:0pt; border:solid black 0.4pt; }
+.framebox-c {text-align:center;}
+.framebox-l {text-align:left;}
+.framebox-r {text-align:right;}
+span.thank-mark{ vertical-align: super }
+span.footnote-mark sup.textsuperscript, span.footnote-mark a
sup.textsuperscript{ font-size:80%; }
+div.tabular, div.center div.tabular {text-align: center; margin-top:0.5em;
margin-bottom:0.5em; }
+table.tabular td p{margin-top:0em;}
+table.tabular {margin-left: auto; margin-right: auto;}
+td p:first-child{ margin-top:0em; }
+td p:last-child{ margin-bottom:0em; }
+div.td00{ margin-left:0pt; margin-right:0pt; }
+div.td01{ margin-left:0pt; margin-right:5pt; }
+div.td10{ margin-left:5pt; margin-right:0pt; }
+div.td11{ margin-left:5pt; margin-right:5pt; }
+table[rules] {border-left:solid black 0.4pt; border-right:solid black 0.4pt; }
+td.td00{ padding-left:0pt; padding-right:0pt; }
+td.td01{ padding-left:0pt; padding-right:5pt; }
+td.td10{ padding-left:5pt; padding-right:0pt; }
+td.td11{ padding-left:5pt; padding-right:5pt; }
+table[rules] {border-left:solid black 0.4pt; border-right:solid black 0.4pt; }
+.hline hr, .cline hr{ height : 1px; margin:0px; }
+.tabbing-right {text-align:right;}
+span.TEX {letter-spacing: -0.125em; }
+span.TEX span.E{ position:relative;top:0.5ex;left:-0.0417em;}
+a span.TEX span.E {text-decoration: none; }
+span.LATEX span.A{ position:relative; top:-0.5ex; left:-0.4em; font-size:85%;}
+span.LATEX span.TEX{ position:relative; left: -0.4em; }
+div.float, div.figure {margin-left: auto; margin-right: auto;}
+div.float img {text-align:center;}
+div.figure img {text-align:center;}
+.marginpar {width:20%; float:right; text-align:left; margin-left:auto;
margin-top:0.5em; font-size:85%; text-decoration:underline;}
+.marginpar p{margin-top:0.4em; margin-bottom:0.4em;}
+table.equation {width:100%;}
+.equation td{text-align:center; }
+td.equation { margin-top:1em; margin-bottom:1em; }
+td.equation-label { width:5%; text-align:center; }
+td.eqnarray4 { width:5%; white-space: normal; }
+td.eqnarray2 { width:5%; }
+table.eqnarray-star, table.eqnarray {width:100%;}
+div.eqnarray{text-align:center;}
+div.array {text-align:center;}
+div.pmatrix {text-align:center;}
+table.pmatrix {width:100%;}
+span.pmatrix img{vertical-align:middle;}
+div.pmatrix {text-align:center;}
+table.pmatrix {width:100%;}
+span.bar-css {text-decoration:overline;}
+img.cdots{vertical-align:middle;}
+.partToc a, .partToc, .likepartToc a, .likepartToc {line-height: 200%;
font-weight:bold; font-size:110%;}
+.index-item, .index-subitem, .index-subsubitem {display:block}
+div.caption {text-indent:-2em; margin-left:3em; margin-right:1em;
text-align:left;}
+div.caption span.id{font-weight: bold; white-space: nowrap; }
+h1.partHead{text-align: center}
+p.bibitem { text-indent: -2em; margin-left: 2em; margin-top:0.6em;
margin-bottom:0.6em; }
+p.bibitem-p { text-indent: 0em; margin-left: 2em; margin-top:0.6em;
margin-bottom:0.6em; }
+.paragraphHead, .likeparagraphHead { margin-top:2em; font-weight: bold;}
+.subparagraphHead, .likesubparagraphHead { font-weight: bold;}
+.quote {margin-bottom:0.25em; margin-top:0.25em; margin-left:1em;
margin-right:1em; text-align:justify;}
+.verse{white-space:nowrap; margin-left:2em}
+div.maketitle {text-align:center;}
+h2.titleHead{text-align:center;}
+div.maketitle{ margin-bottom: 2em; }
+div.author, div.date {text-align:center;}
+div.thanks{text-align:left; margin-left:10%; font-size:85%; font-style:italic;
}
+div.author{white-space: nowrap;}
+.quotation {margin-bottom:0.25em; margin-top:0.25em; margin-left:1em; }
+.abstract p {margin-left:5%; margin-right:5%;}
+div.abstract {width:100%;}
+/* end css.sty */
+
Propchange: uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/installation.css
------------------------------------------------------------------------------
svn:eol-style = native
Added: uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/installation.html
URL:
http://svn.apache.org/viewvc/uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/installation.html?rev=1858151&view=auto
==============================================================================
--- uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/installation.html
(added)
+++ uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/installation.html Thu
Apr 25 17:32:43 2019
@@ -0,0 +1,818 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
+ "http://www.w3.org/TR/html4/loose.dtd";>
+<html >
+<head><title>DUCC Installation and Verification
+Excerpt From Complete DUCC Documentation</title>
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
+<meta name="generator" content="TeX4ht
(http://www.cse.ohio-state.edu/~gurari/TeX4ht/)">
+<meta name="originator" content="TeX4ht
(http://www.cse.ohio-state.edu/~gurari/TeX4ht/)">
+<!-- html -->
+<meta name="src" content="installation.tex">
+<meta name="date" content="2019-04-02 14:27:00">
+<link rel="stylesheet" type="text/css" href="installation.css">
+</head><body
+>
+<div class="maketitle">
+
+
+
+
+
+<h2 class="titleHead">DUCC Installation and Verification<br />
+Excerpt From Complete DUCC Documentation</h2>
+<div class="author" ><span
+class="cmr-12">Written and maintained by the Apache</span>
+<br /> <span
+class="cmr-12">UIMA</span><sup class="textsuperscript"><span
+class="cmr-9">TM</span></sup><span
+class="cmr-12">Development Community</span></div>
+<br />
+<div class="date" ></div>
+</div>
+<!--l. 18--><p class="noindent" >Copyright <span
+class="cmsy-10">©</span>  2012 The Apache Software Foundation
+<!--l. 20--><p class="noindent" >Copyright <span
+class="cmsy-10">©</span>  2012 International Business Machines
Corporation
+ <!--l. 23--><p class="noindent" ><span class="paragraphHead"><a
+ id="x1-1000"></a><span
+class="cmbx-10">License and Disclaimer</span></span>
+ The ASF licenses this documentation to you under the Apache License,
Version 2.0 (the ”License”); you may not
+ use this documentation except in compliance with the License. You may
obtain a copy of the License
+ at
+ <!--l. 28--><p class="noindent" ><a
+href="http://www.apache.org/licenses/LICENSE-2.0"; class="url" ><span
+class="cmtt-10">http://www.apache.org/licenses/LICENSE-2.0</span></a>
+ <!--l. 30--><p class="noindent" >Unless required by applicable law or
agreed to in writing, this documentation and its contents are distributed under
+ the License on an ”AS IS” BASIS, WITHOUT WARRANTIES OR
CONDITIONS OF ANY KIND, either express
+ or implied. See the License for the specific language governing
permissions and limitations under the
+ License.
+ <!--l. 35--><p class="noindent" ><span class="paragraphHead"><a
+ id="x1-2000"></a><span
+class="cmbx-10">Trademarks</span></span>
+ All terms mentioned in the text that are known to be trademarks or
service marks have been appropriately capitalized.
+ Use of such terms in this book should not be regarded as affecting the
validity of the the trademark or service
+ mark.
+<!--l. 47--><p class="noindent" >Publication date: April 2019
+
+
+<h3 class="sectionHead"><a
+ id="x1-3000"></a>Overview</h3>
+<!--l. 21--><p class="noindent" >DUCC is a multi-user, multi-system
distributed application. For first-time users a staged installation/verification
+methodology is recommended, roughly as follows:
+ <ul class="itemize1">
+ <li class="itemize">Single system installation - single node - all work
runs with the credentials of the installer.
+ </li>
+ <li class="itemize">Optionally add worker nodes to the cluster.
+ </li>
+ <li class="itemize">Enable CGroup containers. CGroups protect DUCC
managed processes running on the same machine from
+ inappropriately stealing memory or CPU resources from each other. CGroups
are also required for DUCC to
+ measure and report performance metrics on managed processes.
+ </li>
+ <li class="itemize">Enable multiple-user support - processes run with the
credentials of the submitting user, while DUCC runs as
+ user <span
+class="cmti-10">ducc</span>. This step requires root authority on one or more
machines.</li></ul>
+<!--l. 39--><p class="noindent" >Nominally user <span
+class="cmti-10">ducc </span>runs the DUCC software. However another user, for
example <span
+class="cmti-10">duccster</span>, could be chosen. In this
+document references to user <span
+class="cmti-10">ducc </span>will mean to the user that you have chosen, be it
<span
+class="cmti-10">ducc </span>or <span
+class="cmti-10">duccster </span>or some other. The
+chosen user is the OS user installing DUCC.
+<!--l. 44--><p class="noindent" >When upgrading from an existing installation
the <span
+class="cmti-10">ducc</span><span
+class="cmti-10">_update </span>script may be used to replace the system files
while leaving the
+site-specific configuration files in place. For more information see <span
+class="cmti-10">“ducc</span><span
+class="cmti-10">_update” </span>in the Administrative Commands section of
+the DuccBook.
+<!--l. 53--><p class="noindent" >Since with this release the persistence data
about completed work is stored in a database, additional upgrade steps are
+required to convert the older file-based data in order to preserve information
about past work. For more information see
+<span
+class="cmti-10">“db</span><span
+class="cmti-10">_create” </span>and <span
+class="cmti-10">“db</span><span
+class="cmti-10">_loader” </span>in the Administrative Commands section
of the DuccBook.
+<!--l. 64--><p class="noindent" >DUCC is distributed as a compressed tar file.
If building from source, this file will be created in your svn trunk/target
+directory. The distribution file is in the form
+
+
+<div class="verbatim" id="verbatim-1">
+   uima-ducc-[version]-bin.tar.gz</div>
+<!--l. 68--><p class="nopar" > where [version] is the DUCC version; for
example, <span
+class="cmti-10">uima-ducc-2.1.0-bin.tar.gz</span>. This document will refer to
the distribution
+file as the “<span
+class="cmmi-10"><</span>distribution.file<span
+class="cmmi-10">></span>”.
+<!--l. 72--><p class="noindent" >
+<h3 class="sectionHead"><a
+ id="x1-4000"></a>Software Prerequisites</h3>
+<a
+ id="x1-4000doc"></a>
+<!--l. 75--><p class="noindent" >Single system installation:
+ <ul class="itemize1">
+ <li class="itemize">Reasonably current Linux. DUCC has been tested on
RHEL 6 & 7, SLES 11 & 12, Ubuntu 14.04 & 16.04 with
+ 64-bit Intel and IBM Power (Big and Little Endian) hardware.
+ <!--l. 81--><p class="noindent" ><span
+class="cmti-10">Note: </span>On some systems the default <span
+class="cmti-10">user limits </span>for max user processes (ulimit -u) and
nfiles (ulimit -n) are
+ defined too low for DUCC. The shell login profile for user <span
+class="cmti-10">ducc </span>should set the soft limit for max user processes
+ to be the same as the hard limit (ulimit -u ‘ulimit -Hu‘),
and the nfiles limit raised above 1024 to at least twice
+ the number of user processes running on the cluster.
+ </li>
+ <li class="itemize">Python 2.x, where ’x’ is 4 or greater.
DUCC has not been tested on Python 3.x.
+ </li>
+ <li class="itemize">Java JDK 7 or 8. DUCC has been tested and run using
IBM and Oracle JDK 1.7 & 1.8. A JDK is required by
+ DUCC’s web server for JSP compilations, for which a JRE is
insufficient.
+ </li>
+ <li class="itemize">Passwordless ssh for the userid running DUCC</li></ul>
+<!--l. 94--><p class="noindent" >Additional requirements for multiple system
installation:
+ <ul class="itemize1">
+ <li class="itemize">All systems must have a shared filesystem
(such as NFS or GPFS) and common user credentials. The
+ $DUCC_HOME directory must be located on a shared filesystem.</li></ul>
+<!--l. 101--><p class="noindent" >Additional requirements for running multiple
user processes with their own credentials.
+ <ul class="itemize1">
+ <li class="itemize">A userid <span
+class="cmti-10">ducc</span>, and group <span
+class="cmti-10">ducc</span>. User <span
+class="cmti-10">ducc </span>must be the only member of group <span
+class="cmti-10">ducc</span>.
+ </li>
+ <li class="itemize">DUCC installed and run with user <span
+class="cmti-10">ducc </span>credentials.
+ <!--l. 107--><p class="noindent" ><span
+class="cmti-10">Note: </span>With these restrictions any userid can be
configured to be the DUCC user and group.
+ </li>
+ <li class="itemize">Root access is required to setuid-root the DUCC
process launcher.</li></ul>
+<!--l. 112--><p class="noindent" >Additional requirements for CGroup
containers:
+
+
+ <ul class="itemize1">
+ <li class="itemize">A userid <span
+class="cmti-10">ducc</span>, and group <span
+class="cmti-10">ducc</span>. User <span
+class="cmti-10">ducc </span>must be the only member of group <span
+class="cmti-10">ducc</span>.
+ </li>
+ <li class="itemize">DUCC installed and run with user <span
+class="cmti-10">ducc </span>credentials.
+ <!--l. 118--><p class="noindent" ><span
+class="cmti-10">Note: </span>With these restrictions any userid can be
configured to be the DUCC user and group.
+ </li>
+ <li class="itemize">Root access is required to configure and enable a
custom cgroup for DUCC.
+ </li>
+ <li class="itemize">A running cgroup subsystem. True by default for newer
OS.
+ </li>
+ <li class="itemize">Create a custom cgroup definition that the DUCC user
can use to run managed applications in. The custom
+ definition to go into /etc/cgconfig.conf is described in <a
+href="#x1-16000doc"><span
+class="cmti-10">CGroups Installation and Configuration</span></a>.
+ </li>
+ <li class="itemize">The cgroup tools package, e.g. libcgroup-tools on
centos and cgroup-tools on ubuntu.
+ </li>
+ <li class="itemize">On some flavors of Linux, the cgroup swap
accounting is not enabled and swap is reported as N/A. To
+ enable swap accounting add swapaccount=1 kernel parameter. More
information on this step is available here:
+ <a
+href="http://unix.stackexchange.com/questions/147158/how-to-enable-swap-accounting-for-memory-cgroup-in-archlinux";
class="url" ><span
+class="cmtt-10">http://unix.stackexchange.com/questions/147158/how-to-enable-swap-accounting-for-memory-cgroup-in-archlinux</span></a>.</li></ul>
+<!--l. 131--><p class="noindent" >In order to build DUCC from source the
following software is also required:
+ <ul class="itemize1">
+ <li class="itemize">A Subversion client, from <a
+href="http://subversion.apache.org/packages.html"; class="url" ><span
+class="cmtt-10">http://subversion.apache.org/packages.html</span></a>. The
svn url is
+ <a
+href="https://svn.apache.org/repos/asf/uima/uima-ducc/trunk"; class="url"
><span
+class="cmtt-10">https://svn.apache.org/repos/asf/uima/uima-ducc/trunk</span></a>.
+ </li>
+ <li class="itemize">Apache Maven, version 3.3.3+, from <a
+href="http://maven.apache.org/index.html"; class="url" ><span
+class="cmtt-10">http://maven.apache.org/index.html</span></a></li></ul>
+<!--l. 138--><p class="noindent" >The DUCC webserver server optionally
supports direct “jconsole” attach to DUCC job processes. To install
this, the
+following is required:
+ <ul class="itemize1">
+ <li class="itemize">Apache Ant, any reasonably current version.</li></ul>
+<!--l. 144--><p class="noindent" >To (optionally) build the documentation, the
following is also required:
+ <ul class="itemize1">
+ <li class="itemize">Latex, including the <span
+class="cmti-10">pdflatex </span>and <span
+class="cmti-10">htlatex </span>packages. A good place to start if you
need to install it is
+ <a
+href="https://www.tug.org/texlive/"; class="url" ><span
+class="cmtt-10">https://www.tug.org/texlive/</span></a>.</li></ul>
+<!--l. 150--><p class="noindent" >More detailed one-time setup instructions
for source-level builds via subversion can be found here:
+<a
+href="http://uima.apache.org/one-time-setup.html#svn-setup"; class="url" ><span
+class="cmtt-10">http://uima.apache.org/one-time-setup.html#svn-setup</span></a>
+<!--l. 153--><p class="noindent" >
+<h3 class="sectionHead"><a
+ id="x1-5000"></a>Building from Source</h3>
+<!--l. 155--><p class="noindent" >To build from source, ensure you have
Subversion and Maven installed. Extract the source from the SVN repository named
+above.
+<!--l. 158--><p class="noindent" >Then from your extract directory into the
root directory (usually current-directory/trunk), and run the command
+
+
+<div class="verbatim" id="verbatim-2">
+    mvn install</div>
+<!--l. 162--><p class="nopar" > or
+
+
+<div class="verbatim" id="verbatim-3">
+    mvn install -Pbuild-duccdocs</div>
+<!--l. 166--><p class="nopar" > if you have LaTeX installed and wish to do the
optional build of documentation. The build-duccdocs profile can also
+activated if the environment valiable BUILD_DUCCDOCS is set true.
+<!--l. 170--><p class="noindent" ><span
+class="cmti-10">Note: LaTeX output is quite verbose and it is suppressed when
run via maven.</span>
+<!--l. 172--><p class="noindent" >An alternative approach for modifying
DUCCDOCS is to use the LaTeX commands manually. Not only is the build much
+faster, it also exposes LaTeX error messages lost by the suppression. To build
duccbook.html manually and leave the output
+in the same directory:
+
+
+<div class="verbatim" id="verbatim-4">
+    cd {path-to-src}/uima-ducc-duccdocs/src/site/tex/duccbook
+ <br />    htlatex duccbook.tex</div>
+<!--l. 178--><p class="nopar" > Use the pdflatex command to build the PDF
version.
+<!--l. 181--><p class="noindent" ><span
+class="cmti-10">Note: The manual command needs to be run twice if
modifications have been made that affect internal book</span>
+<span
+class="cmti-10">references such as the table of contents. Also, temporary
files created by LaTeX will need to be cleaned up</span>
+<span
+class="cmti-10">manually.</span>
+<!--l. 184--><p class="noindent" >If this is your first Maven build it may
take quite a while as Maven downloads all the open-source pre-requisites. (The
+pre-requisites are stored in the Maven repository, usually your $HOME/.m2).
+<!--l. 188--><p class="noindent" >When build is complete, a tarball is placed
in your current-directory/trunk/target directory.
+<!--l. 191--><p class="noindent" >
+<h3 class="sectionHead"><a
+ id="x1-6000"></a>Documentation</h3>
+<!--l. 193--><p class="noindent" >After installation the DUCC documentation is
found (in both PDF and HTML format) in the directory ducc_runtime/docs.
+As well, the DUCC webserver contains a link to the full documentation on each
major page. The API is documented only via
+JavaDoc, distributed in the webserver’s root directory <span
+class="cmtt-10">$DUCC</span><span
+class="cmtt-10">_HOME/webserver/root/doc/api.</span>
+<!--l. 199--><p class="noindent" >If building from source, Maven places the
documentation in
+ <ul class="itemize1">
+ <li class="itemize"><span
+class="cmtt-10">trunk/uima-ducc-duccdocs/target/site </span>(main
documentation), and
+ </li>
+ <li class="itemize"><span
+class="cmtt-10">trunk/target/site/apidocs </span>(API Javadoc)</li></ul>
+<!--l. 205--><p class="noindent" >
+<h3 class="sectionHead"><a
+ id="x1-7000"></a>Single System Installation and Verification</h3>
+<!--l. 207--><p class="noindent" >Any user ID can be used to run a
single-system DUCC, but “ducc” userid is recommended. This user
will employ cgroups as
+well as launching and running processes with the credentials of the submitting
user.
+<!--l. 210--><p class="noindent" >If multiple nodes are going to be added
later, the ducc runtime tree should be installed on a shared filesystem so that
it can
+be mounted on the additional nodes.
+<!--l. 213--><p class="noindent" >Verification submits a very simple UIMA
pipeline for execution under DUCC. Once this is shown to be working, one may
+proceed installing additional features.
+<!--l. 217--><p class="noindent" >
+<h3 class="sectionHead"><a
+ id="x1-8000"></a>Minimal Hardware Requirements for Single System
Installation</h3>
+ <ul class="itemize1">
+ <li class="itemize">One Intel-based or IBM Power-based system (Big or
Little Endian). (More systems may be added later.)
+
+
+ </li>
+ <li class="itemize">8GB of memory. 16GB or more is preferable for
developing and testing applications beyond the non-trivial.
+ </li>
+ <li class="itemize">1GB disk space to hold the DUCC runtime, system logs,
and job logs. More is usually needed for larger
+ installations.</li></ul>
+<!--l. 228--><p class="noindent" >Please note: DUCC is intended for scaling
out memory-intensive UIMA applications over computing clusters consisting of
+multiple nodes with large (16GB-256GB or more) memory. The minimal
requirements are for initial test and evaluation
+purposes, but will not be sufficient to run actual workloads.
+<!--l. 233--><p class="noindent" >
+<h3 class="sectionHead"><a
+ id="x1-9000"></a>Single System Installation</h3>
+<a
+ id="x1-9000doc"></a>
+<!--l. 235--><p class="noindent" >
+ <ol class="enumerate1" >
+ <li
+ class="enumerate" id="x1-9002x1">Expand the distribution file with the
appropriate umask:
+
+
+ <div class="verbatim" id="verbatim-5">
+
(umask 022 && tar -zxf <distribution.file>)</div>
+ <!--l. 239--><p class="nopar" >
+ <!--l. 241--><p class="noindent" >This creates a directory with a name of
the form “apache-uima-ducc-[version]”.
+ <!--l. 243--><p class="noindent" >This directory contains the full DUCC
runtime which you may use “in place” but it is highly recommended
+ that you move it into a standard location on a shared filesystem; for
example, under ducc’s HOME
+ directory:
+
+
+ <div class="verbatim" id="verbatim-6">
+ mv apache-uima-ducc-[version] /home/ducc/ducc_runtime</div>
+ <!--l. 248--><p class="nopar" >
+ <!--l. 250--><p class="noindent" >We refer to this directory, regardless
of its location, as $DUCC_HOME. For simplicity, some of the examples in this
+ document assume it has been moved to /home/ducc/ducc_runtime.
+ </li>
+ <li
+ class="enumerate" id="x1-9004x2">Change directories into the admin
sub-directory of $DUCC_HOME:
+
+
+ <div class="verbatim" id="verbatim-7">
+ cd $DUCC_HOME/admin</div>
+ <!--l. 256--><p class="nopar" >
+ </li>
+ <li
+ class="enumerate" id="x1-9006x3">Run the post-installation script:
+
+
+ <div class="verbatim" id="verbatim-8">
+ ./ducc_post_install</div>
+ <!--l. 261--><p class="nopar" > If this script fails, correct any
problems it identifies and run it again.
+ <!--l. 264--><p class="noindent" >Note that <span
+class="cmti-10">ducc</span><span
+class="cmti-10">_post</span><span
+class="cmti-10">_install </span>initializes various default parameters which
may be changed later by the system
+ administrator. Therefore it usually should be run only during this first
installation step.
+ </li>
+ <li
+ class="enumerate" id="x1-9008x4">If you wish to install jconsole support
from the webserver, make sure Apache Ant is installed, and run
+
+
+ <div class="verbatim" id="verbatim-9">
+ ./sign_jconsole_jar</div>
+ <!--l. 272--><p class="nopar" > This step may be run at any time if you
wish to defer it.
+ </li></ol>
+<!--l. 277--><p class="noindent" >That’s it, DUCC is installed and ready
to run. (If errors were displayed during ducc_post_install they must be
corrected
+before continuing.)
+<!--l. 280--><p class="noindent" >
+<h3 class="sectionHead"><a
+ id="x1-10000"></a>Initial System Verification</h3>
+<!--l. 282--><p class="noindent" >Here we verify the system configuration,
start DUCC, run a test Job, and then shutdown DUCC.
+<!--l. 284--><p class="noindent" >To run the verification, issue these
commands.
+ <ol class="enumerate1" >
+ <li
+ class="enumerate" id="x1-10002x1">cd $DUCC_HOME/admin
+ </li>
+ <li
+ class="enumerate" id="x1-10004x2">./check_ducc
+ <!--l. 289--><p class="noindent" >Examine the output of check_ducc. If
any errors are shown, correct the errors and rerun check_ducc until there
+ are no errors.
+ </li>
+ <li
+ class="enumerate" id="x1-10006x3">Finally, start ducc: ./start_ducc</li></ol>
+<!--l. 294--><p class="noindent" >Start_ducc will first perform a number of
consistency checks. It then starts the ActiveMQ broker, the DUCC control
+processes, and a single DUCC agent on the local node.
+<!--l. 298--><p class="noindent" >You will see some startup messages similar
to the following:
+
+
+<div class="verbatim" id="verbatim-10">
+ENV: Java is configured as: /share/jdk1.7/bin/java
+ <br />ENV: java full version "1.7.0_40-b43"
+ <br />ENV: Threading enabled: True
+ <br />MEM: memory is 15 gB
+ <br />ENV: system is Linux
+ <br />allnodes /home/ducc/ducc_runtime/resources/ducc.nodes
+ <br />Class definition file is ducc.classes
+ <br
/>OK: Class and node definitions validated.
+ <br />OK: Class configuration checked
+ <br />Starting broker on ducchead.biz.org
+ <br />Waiting for broker ..... 0
+ <br />Waiting for broker ..... 1
+ <br
/>ActiveMQ broker is found on configured host and port: ducchead.biz.org:61616
+ <br />Starting 1 agents
+ <br
/>********** Starting agents from file /home/ducc/ducc_runtime/resources/ducc.nodes
+ <br />Starting warm
+ <br />Waiting for Completion
+ <br />ducchead.biz.org Starting rm
+ <br />     PID 14198
+ <br />ducchead.biz.org Starting pm
+ <br />     PID 14223
+ <br />ducchead.biz.org Starting sm
+ <br />     PID 14248
+ <br />ducchead.biz.org Starting or
+ <br />     PID 14275
+ <br />ducchead.biz.org Starting ws
+ <br />     PID 14300
+ <br />ducchead.biz.org
+ <br />    ducc_ling OK
+ <br
/>    DUCC Agent started PID 14325
+ <br />All threads returned</div>
+<!--l. 332--><p class="nopar" >
+<!--l. 334--><p class="noindent" >Now open a browser and go to the DUCC
webserver’s url, http://<span
+class="cmmi-10"><</span>hostname<span
+class="cmmi-10">></span>:42133 where <span
+class="cmmi-10"><</span>hostname<span
+class="cmmi-10">> </span>is the name of the
+host where DUCC is started. Navigate to the Reservations page via the links in
the upper-left corner. You should see the
+DUCC JobDriver reservation in state WaitingForResources. In a few minutes this
should change to Assigned. Now jobs can
+be submitted.
+<!--l. 340--><p class="noindent" >
+<h4 class="subsectionHead"><a
+ id="x1-11000"></a>Submitting a test job</h4>
+<!--l. 341--><p class="noindent" >
+ <ol class="enumerate1" >
+ <li
+ class="enumerate" id="x1-11002x1">$DUCC_HOME/bin/ducc_submit
–specification $DUCC_HOME/examples/simple/1.job</li></ol>
+<!--l. 345--><p class="noindent" >Open the browser in the DUCC jobs page. You
should see the job progress through a series of transitions: Waiting For
+Driver, Waiting For Services, Waiting For Resources, Initializing, and
finally, Running. You’ll see the number of work items
+submitted (15) and the number of work items completed grow from 0 to 15.
Finally, the job will move into Completing and
+then Completed..
+
+
+<!--l. 351--><p class="noindent" >Since this example does not specify a log
directory DUCC will create a log directory in your HOME directory
+under
+
+
+<div class="verbatim" id="verbatim-11">
+$HOME/ducc/logs/job-id</div>
+<!--l. 354--><p class="nopar" >
+<!--l. 356--><p class="noindent" >In this directory, you will find a log for
the sample job’s JobDriver (JD), JobProcess (JP), and a number of other
files
+relating to the job.
+<!--l. 359--><p class="noindent" >This is a good time to explore the DUCC web
pages. Notice that the job id is a link to a set of pages with details about the
+execution of the job.
+<!--l. 362--><p class="noindent" >Notice also, in the upper-right corner is a
link to the full DUCC documentation, the “DuccBook”.
+<!--l. 364--><p class="noindent" >
+<h4 class="subsectionHead"><a
+ id="x1-12000"></a>Registering a test service</h4>
+<!--l. 366--><p class="noindent" >First start an application broker using the
UIMA-AS script included in the DUCC installation, see <span
+class="cmbx-10">??</span>. Then in another shell
+define the broker URL using the name of the host the broker was started on,
and register the service. On your browser select
+the Services page and wait for the service to become Available.
+
+
+<div class="verbatim" id="verbatim-12">
+    export DefaultBrokerURL=tcp://<broker-host-name>:61616
+ <br
/>    $DUCC_HOME/bin/ducc_services --register $DUCC_HOME/examples/simple/1.service
+ <br />    </div>
+<!--l. 374--><p class="nopar" > The service can be tested by sending it CASes
that specify a sleep value.
+
+
+<div class="verbatim" id="verbatim-13">
+    export UIMA_HOME=$DUCC_HOME/apache-uima
+ <br
/>    export UIMA_CLASSPATH=$DUCC_HOME/lib/uima-ducc/examples
+ <br
/>    export UIMA_JVM_OPTS=-DDUCC_HOME=$DUCC_HOME
+ <br
/>    $UIMA_HOME/bin/runRemoteAsyncAE.sh -c $DUCC_HOME/examples/simple/resources/randomsleep/FixedSleepCR.xml -o out $DefaultBrokerURL TopLevelTaeQueue
+ <br />    </div>
+<!--l. 381--><p class="nopar" >
+<!--l. 383--><p class="noindent" >To remove the service use:
+
+
+<div class="verbatim" id="verbatim-14">
+    $DUCC_HOME/bin/ducc_services --unregister <service-id-number>
+ <br />    </div>
+<!--l. 386--><p class="nopar" >
+<!--l. 388--><p class="noindent" >
+<h4 class="subsectionHead"><a
+ id="x1-13000"></a>To stop DUCC</h4>
+
+
+<div class="verbatim" id="verbatim-15">
+      cd $DUCC_HOME/admin
+ <br
/>      ./stop_ducc -a
+ <br />    </div>
+<!--l. 392--><p class="nopar" >
+<!--l. 395--><p class="noindent" >
+<h3 class="sectionHead"><a
+ id="x1-14000"></a>Add additional nodes to the DUCC cluster</h3>
+<!--l. 396--><p class="noindent" >Additional nodes must meet all <span
+class="cmti-10">prerequisites </span>(listed above).
+<!--l. 403--><p class="noindent" >$DUCC_HOME must be on a shared filesystem
and mounted at the same location on all DUCC nodes.
+<!--l. 406--><p class="noindent" >If user’s home directories are on
local filesystems the location for user logfiles should be specified to be on a
shared
+filesystem.
+<!--l. 409--><p class="noindent" >Addional nodes are normally added to a
worker node group. Note that the DUCC head node does not have to be a worker
+node. In addition, the webserver node can be separate from the DUCC head node
(see webserver configuration options in
+ducc.properties).
+<!--l. 414--><p class="noindent" >For worker nodes DUCC needs to know what
node group each machine belongs to, and what nodes need an Agent process to
+be started on.
+<!--l. 417--><p class="noindent" >The configuration shipped with DUCC have all
nodes in the same ”default” node pool. Worker nodes are listed in
the
+file
+
+
+<div class="verbatim" id="verbatim-16">
+$DUCC_HOME/resources/ducc.nodes.</div>
+<!--l. 421--><p class="nopar" >
+<!--l. 423--><p class="noindent" >During initial installation, this file was
initialized with the node DUCC is installed on. Additional nodes may be added
to the
+file using a text editor to increase the size of the DUCC cluster.
+<!--l. 428--><p class="noindent" >
+<h3 class="sectionHead"><a
+ id="x1-15000"></a>Ducc_ling Configuration - Running with credentials of
submitting user</h3>
+<a
+ id="x1-15000doc"></a>
+<!--l. 431--><p class="noindent" >DUCC launches user processes through
ducc_ling, a small native C application. By default the resultant process runs
with
+the credentials of the user ID of the DUCC application. It is possible for
multiple users to submit work to DUCC in this
+configuration, but it requires that the user ID running DUCC has write access
to all directories to which the user process
+outputs data. By configuring the ducc user ID and ducc_ling correctly, work
submitted by all users will run with their own
+credentials.
+<!--l. 439--><p class="noindent" >Before proceeding with this step, please
note:
+ <ul class="itemize1">
+ <li class="itemize">The sequence operations consisting of <span
+class="cmti-10">chown </span>and <span
+class="cmti-10">chmod </span>MUST be performed in the exact order given below.
+ If the <span
+class="cmti-10">chmod </span>operation is performed before the <span
+class="cmti-10">chown </span>operation, Linux will regress the permissions
granted by
+ <span
+class="cmti-10">chmod </span>and ducc_ling will be incorrectly
installed.</li></ul>
+<!--l. 447--><p class="noindent" >ducc_ling is designed to be a setuid-root
program whose function is to run user processes with the identity of the
submitting
+user. This must be installed correctly; incorrect installation can prevent
jobs from running as their submitters, and in the
+worse case, can introduce security problems into the system.
+<!--l. 451--><p class="noindent" >ducc_ling can either be installed on a local
disk on every system in the DUCC cluster, or on a shared-filesystem that does
not
+suppress setuid-root permissions on client nodes. The path to ducc_ling must
be the same on each DUCC node. The default
+path configuration is $DUCC_HOME/admin/$<span
+class="cmsy-10">{</span>os.arch<span
+class="cmsy-10">}</span>/ in order to handle clusters with mixed OS platforms.
+$<span
+class="cmsy-10">{</span>os.arch<span
+class="cmsy-10">} </span>is the architecture specific value of the Java system
property with that name; examples are amd64 and
+ppc64.
+<!--l. 459--><p class="noindent" >The steps are: build ducc_ling for each node
architecture to be added to the cluster, copy ducc_ling to the
+desired location, and then configure ducc_ling to give user ducc the ability
to spawn a process as a different
+user.
+<!--l. 463--><p class="noindent" >In the example below ducc_ling is left under
$DUCC_HOME, where it is built.
+<!--l. 465--><p class="noindent" >As user <span
+class="cmti-10">ducc</span>, build ducc_ling for necessary architectures (this
is done automatically for the DUCC head machine by the
+ducc_post_install script). For each unique OS platform:
+ <ol class="enumerate1" >
+ <li
+ class="enumerate" id="x1-15002x1">cd $DUCC_HOME/admin
+ </li>
+ <li
+ class="enumerate" id="x1-15004x2">./build_duccling</li></ol>
+<!--l. 473--><p class="noindent" >Then, as user <span
+class="cmti-10">root </span>on the shared filesystem, <span
+class="cmti-10">cd </span><span
+class="cmsl-10">$</span><span
+class="cmti-10">DUCC</span><span
+class="cmti-10">_HOME/admin</span>, and for each unique OS architecture:
+ <ol class="enumerate1" >
+ <li
+ class="enumerate" id="x1-15006x1">chown ducc.ducc $<span
+class="cmsy-10">{</span>os.arch<span
+class="cmsy-10">}</span><br
+class="newline" />(set directory ownership to be user ducc, group ducc)
+
+
+ </li>
+ <li
+ class="enumerate" id="x1-15008x2">chmod 700 $<span
+class="cmsy-10">{</span>os.arch<span
+class="cmsy-10">}</span><br
+class="newline" />(only user ducc can read contents of directory)
+ </li>
+ <li
+ class="enumerate" id="x1-15010x3">chown root.ducc $<span
+class="cmsy-10">{</span>os.arch<span
+class="cmsy-10">}</span>/ducc_ling <br
+class="newline" />(make root owner of ducc_ling, and let users in group ducc
access it)
+ </li>
+ <li
+ class="enumerate" id="x1-15012x4">chmod 4750 $<span
+class="cmsy-10">{</span>os.arch<span
+class="cmsy-10">}</span>/ducc_ling <br
+class="newline" />(ducc_ling runs as user root when started by users in group
ducc)</li></ol>
+<!--l. 485--><p class="noindent" >If these steps are correctly performed, ONLY
user <span
+class="cmti-10">ducc </span>may use the ducc_ling program in a privileged way.
ducc_ling
+contains checks to prevent even user <span
+class="cmti-10">root </span>from using it for privileged operations.
+<!--l. 489--><p class="noindent" >If a different location is chosen for
ducc_ling the new path needs to be specified for
ducc.agent.launcher.ducc_spawn_path in
+$DUCC_HOME/resources/site.ducc.properties. For more information see <span
+class="cmti-10">“Properties merging” </span>in the DuccBook.
+<!--l. 499--><p class="noindent" >
+<h3 class="sectionHead"><a
+ id="x1-16000"></a>CGroups Installation and Configuration</h3>
+<a
+ id="x1-16000doc"></a>
+<!--l. 502--><p class="noindent" >
+ <dl class="description"><dt class="description">
+<span
+class="cmbx-10">Note:</span> </dt><dd
+class="description">A key feature of DUCC is to run user processes in CGroups
in order to guarantee each process always has
+ the amount of RAM requested. RAM allocated to the managed process (and
any child processes) that exceed
+ requested DUCC memory size will be forced into swap space. Without
CGroups a process that exceeds its
+ requested memory size by N% is killed (default N=5 in ducc.properties),
and memory use by child processes is
+ ignored.
+ <!--l. 509--><p class="noindent" >DUCC’s CGroup configuration also
allocates CPU resources to managed processes based on relative memory
+ size. A process with 50% of a machine’s RAM will be guaranteed at
least 50% of the machine’s CPU resources
+ as well.</dd></dl>
+<!--l. 514--><p class="noindent" >The steps in this task must be done as user
root and the ducc user.
+<!--l. 516--><p class="noindent" >To install and configure CGroups for DUCC:
+ <ol class="enumerate1" >
+ <li
+ class="enumerate" id="x1-16002x1">Install the appropriate libcgroup package
at level 0.37 or above (see <span
+class="cmti-10">Installation Prerequisites</span>).
+ </li>
+ <li
+ class="enumerate" id="x1-16004x2">For newer OS configure /etc/cgconfig.conf
as follows:
+
+
+ <div class="verbatim" id="verbatim-17">
+
   # Define cgroup for the userid you have opted to install and run DUCC, normally ’ducc’ but in this example ’duccster’, and setup permissions
+  <br />   group duccster {
+  <br />    perm {
+  <br
/>        task {
+  <br
/>           uid = duccster;
+  <br
/>        }
+  <br
/>        admin {
+  <br
/>           uid = duccster;
+  <br
/>        }
+  <br />    }
+  <br />    memory {}
+  <br />    cpu{}
+  <br />    cpuacct{}
+  <br />   }</div>
+ <!--l. 541--><p class="nopar" > For older OS that mount cgroups in
/cgroup, configure /etc/cgconfig.conf as follows:
+
+
+ <div class="verbatim" id="verbatim-18">
+
   # Mount cgroups for older OS (e.g. RHEL v6)
+  <br />   mount {
+  <br
/>      cpuset = /cgroup/cpuset;
+  <br
/>      cpu = /cgroup/cpu;
+  <br
/>      cpuacct = /cgroup/cpuacct;
+  <br
/>      memory = /cgroup/memory;
+  <br
/>      devices = /cgroup/devices;
+  <br
/>      freezer = /cgroup/freezer;
+  <br
/>      net_cls = /cgroup/net_cls;
+  <br
/>      blkio = /cgroup/blkio;
+  <br />   }
+  <br
/>   # Define cgroup for the userid you have opted to install and run DUCC, normally ’ducc’ but in this example ’duccster’, and setup permissions
+  <br />   group duccster {
+  <br />    perm {
+  <br
/>        task {
+  <br
/>           uid = duccster;
+  <br
/>        }
+  <br
/>        admin {
+  <br
/>           uid = duccster;
+  <br
/>        }
+  <br />    }
+  <br />    memory {}
+  <br />    cpu{}
+  <br />    cpuacct{}
+  <br />   }</div>
+ <!--l. 569--><p class="nopar" >
+ </li>
+ <li
+ class="enumerate" id="x1-16006x3">Restart the cgconfig service as per the
specific OS instructions.
+ </li>
+ <li
+ class="enumerate" id="x1-16008x4">Verify the custom cgroup configuration is
active by getting good output from the following 3 commands:
+
+
+ <div class="verbatim" id="verbatim-19">
+
   cgget -g memory:ducc | grep swappiness
+  <br
/>   cgget -g cpu:ducc  | grep cpu.shares
+  <br
/>   cgget -g cpuacct:ducc | grep cpuacct.stat</div>
+ <!--l. 578--><p class="nopar" >
+ </li></ol>
+<!--l. 582--><p class="noindent" ><span
+class="cmti-10">Note: </span>if CGroups is not installed on a machine the DUCC
Agent will detect this and not attempt to use the feature. CGroups
+can also be disabled for all machines or for individual machines. Use <span
+class="cmti-10">ducc.agent.launcher.cgroups.enable </span>and
+<span
+class="cmti-10">ducc.agent.exclusion.file </span>respectively in <span
+class="cmti-10">site.ducc.properties</span>.
+<!--l. 592--><p class="noindent" >
+<h3 class="sectionHead"><a
+ id="x1-17000"></a>Full DUCC Verification</h3>
+<!--l. 594--><p class="noindent" >This is identical to initial verification,
with the one difference that the job “1.job” should be submitted as
any user other
+than ducc. Watch the webserver and check that the job executes under the
correct identity. Once this completes, DUCC is
+installed and verified.
+<!--l. 598--><p class="noindent" >
+<h3 class="sectionHead"><a
+ id="x1-18000"></a>Enable DUCC webserver login</h3>
+<!--l. 600--><p class="noindent" >This step is optional. As shipped, the
webserver is disabled for logins. This can be seen by hovering over the Login
text
+located in the upper right of most webserver pages:
+
+
+<div class="verbatim" id="verbatim-20">
+System is configured to disallow logins</div>
+<!--l. 605--><p class="nopar" >
+<!--l. 607--><p class="noindent" >To enable logins, a Java-based authenticator
must be plugged-in and the login feature must be enabled in the ducc.properties
+file by the DUCC administrator. Also, ducc_ling should be properly deployed
(see Ducc_ling Installation section
+above).
+<!--l. 612--><p class="noindent" >A beta version of a Linux-based
authentication plug-in is shipped with DUCC. It can be found in the source
+tree:
+
+
+<div class="verbatim" id="verbatim-21">
+org.apache.uima.ducc.ws.authentication.LinuxAuthenticationManager</div>
+<!--l. 616--><p class="nopar" >
+<!--l. 618--><p class="noindent" >The Linux-based authentication plug-in will
attempt to validate webserver login requests by appealing to the host OS. The
+user who wishes to login provides a userid and password to the webserver via
https, which in-turn are handed-off to the OS
+for a success/failure reply.
+<!--l. 623--><p class="noindent" >To have the webserver employ the beta
Linux-based authentication plug-in, the DUCC administrator should perform the
+following as user ducc:
+
+
+<div class="verbatim" id="verbatim-22">
+1. edit site.ducc.properties
+ <br
/>2. locate: ducc.ws.login.enabled = false
+ <br
/>3. modify: ducc.ws.login.enabled = true
+ <br />4. add:
+ <br
/>   ducc.authentication.implementer=org.apache.uima.ducc.ws.authentication.LinuxAuthenticationManager
+ <br />5. save</div>
+<!--l. 632--><p class="nopar" >
+<!--l. 634--><p class="noindent" >Note: The beta Linux-based authentication
plug-in has limited testing. In particular, it was tested using:
+
+
+<div class="verbatim" id="verbatim-23">
+Red Hat Enterprise Linux Workstation release 6.4 (Santiago)</div>
+<!--l. 638--><p class="nopar" >
+<!--l. 640--><p class="noindent" >A beta version of a File-based
authentication plug-in is shipped with DUCC. It can be found in the source
+tree:
+
+
+<div class="verbatim" id="verbatim-24">
+org.apache.uima.ducc.ws.authentication.SecureFileAuthenticator.java</div>
+<!--l. 644--><p class="nopar" >
+<!--l. 646--><p class="noindent" >The File-based authentication plug-in will
attempt to validate webserver login requests by checking againist a file that
only
+the user can view, either in the security directory specified in
ducc.properties, else in the user home directory. The user who
+wishes to login provides a userid and password to the webserver via https,
which in-turn are checked against the file-based
+password for a success/failure reply.
+<!--l. 654--><p class="noindent" >Each time a login is attempted by the user,
a new password is generated in the secure file. Thus, each login password is
single
+use.
+<!--l. 657--><p class="noindent" >To have the webserver employ the beta
File-based authentication plug-in, the DUCC administrator should perform the
+following as user ducc:
+
+
+<div class="verbatim" id="verbatim-25">
+1. edit site.ducc.properties
+ <br
/>2. locate: ducc.ws.login.enabled = false
+ <br
/>3. modify: ducc.ws.login.enabled = true
+ <br />4. add:
+ <br
/>   ducc.authentication.implementer=org.apache.uima.ducc.ws.authentication.SecureFileAuthenticator
+ <br />5. save</div>
+<!--l. 666--><p class="nopar" >
+<!--l. 668--><p class="noindent" >Note: The beta File-based authentication
plug-in has limited testing.
+<!--l. 670--><p class="noindent" >Alternatively, you can provide your own
authentication plug-in. To do so:
+
+
+<div class="verbatim" id="verbatim-26">
+1. author a Java class that implements
+ <br
/>   org.apache.uima.ducc.common.authentication.IAuthenticationManager
+ <br
/>2. create a jar file comprising your authentication class
+ <br
/>3. put the jar file in a location accessible by the DUCC webserver, such as
+ <br />    $DUCC_HOME/lib/authentication
+ <br
/>4. put any authentication dependency jar files there as well
+ <br />5. edit ducc.properties
+ <br />6. add the following:
+ <br
/>   ducc.local.jars = authentication/*
+ <br
/>   ducc.authentication.implementer=<your.authenticator.class.Name>
+ <br
/>7. locate: ducc.ws.login.enabled = false
+ <br
/>8. modify: ducc.ws.login.enabled = true
+ <br />9. save</div>
+<!--l. 685--><p class="nopar" >
+<!--l. 687--><p class="noindent" >
+<h3 class="sectionHead"><a
+ id="x1-19000"></a>DUCC webserver user data restricted access</h3>
+<!--l. 689--><p class="noindent" >To configure for user data secure access,
use the following settings (port numbers can be any available, but normally as
+shown below):
+
+
+<div class="verbatim" id="verbatim-27">
+ducc.ws.port = 42133
+ <br />ducc.ws.port.ssl = 42155
+ <br />ducc.ws.login.enabled = true
+ <br />ducc.ws.user.data.access = encrypted</div>
+<!--l. 697--><p class="nopar" >
+<!--l. 699--><p class="noindent" >With these settings, users will be required
to login to the DUCC Web Server to view user data (e.g. user log files). In
+addition, user data will be transported over https only.
+<!--l. 703--><p class="noindent" >There is a list of exempted URIs for which
transport over http is allowed:
+
+
+<div class="verbatim" id="verbatim-28">
+$DUCC_HOME/webserver/etc/http-uri-encryption-exemption.list</div>
+<!--l. 708--><p class="nopar" >
+<!--l. 710--><p class="noindent" >The exemption list allows, for example, the
+
+
+<div class="verbatim" id="verbatim-29">
+ducc_monitor</div>
+<!--l. 713--><p class="nopar" > to fetch status over http:
+
+
+<div class="verbatim" id="verbatim-30">
+ducc-servlet/proxy-job-monitor-report</div>
+<!--l. 718--><p class="nopar" >
+<!--l. 720--><p class="noindent" >
+<h3 class="sectionHead"><a
+ id="x1-20000"></a>DUCC daemons monitoring and notification</h3>
+
+
+<div class="verbatim" id="verbatim-31">
+ <br
/>$DUCC_HOME/bin/ducc_watcher is a Python script that, when run, contacts the
+ <br
/>DUCC Web Server to fetch data and determine the status of the critical head node daemons.
+ <br
/>It can be run as a cron job to detect down daemons and send email notifications
+ <br
/>to a list of receipients specified via command invocation option.
+ <br />
+ <br
/>Use the --help options for details.
+ <br />
+ <br
/>Purpose: send e-mail when a DUCC daemon state changes to not up
+ <br />
+ <br />Files created by script:
+ <br /> - /tmp/<user>/ducc_watcher.state
+ <br
/>   + comprises the last recorded state of DUCC daemons
+ <br />
+ <br /> - /tmp/<user>/ducc_watcher.log
+ <br
/>   + comprises a log produced by the script
+ <br /></div>
+<!--l. 740--><p class="nopar" >
+
+</body></html>
+
+
+
+
Propchange:
uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/installation.html
------------------------------------------------------------------------------
svn:eol-style = native
Added: uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/installation.pdf
URL:
http://svn.apache.org/viewvc/uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/installation.pdf?rev=1858151&view=auto
==============================================================================
Binary file - no diff available.
Propchange: uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/installation.pdf
------------------------------------------------------------------------------
svn:mime-type = application/pdf
Added:
uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/issuesFixed/css/maven-base.css
URL:
http://svn.apache.org/viewvc/uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/issuesFixed/css/maven-base.css?rev=1858151&view=auto
==============================================================================
---
uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/issuesFixed/css/maven-base.css
(added)
+++
uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/issuesFixed/css/maven-base.css
Thu Apr 25 17:32:43 2019
@@ -0,0 +1,155 @@
+body {
+ margin: 0px;
+ padding: 0px;
+}
+img {
+ border:none;
+}
+table {
+ padding:0px;
+ width: 100%;
+ margin-left: -2px;
+ margin-right: -2px;
+}
+acronym {
+ cursor: help;
+ border-bottom: 1px dotted #feb;
+}
+table.bodyTable th, table.bodyTable td {
+ padding: 2px 4px 2px 4px;
+ vertical-align: top;
+}
+div.clear{
+ clear:both;
+ visibility: hidden;
+}
+div.clear hr{
+ display: none;
+}
+#bannerLeft, #bannerRight {
+ font-size: xx-large;
+ font-weight: bold;
+}
+#bannerLeft img, #bannerRight img {
+ margin: 0px;
+}
+.xleft, #bannerLeft img {
+ float:left;
+}
+.xright, #bannerRight {
+ float:right;
+}
+#banner {
+ padding: 0px;
+}
+#banner img {
+ border: none;
+}
+#breadcrumbs {
+ padding: 3px 10px 3px 10px;
+}
+#leftColumn {
+ width: 170px;
+ float:left;
+ overflow: auto;
+}
+#bodyColumn {
+ margin-right: 1.5em;
+ margin-left: 197px;
+}
+#legend {
+ padding: 8px 0 8px 0;
+}
+#navcolumn {
+ padding: 8px 4px 0 8px;
+}
+#navcolumn h5 {
+ margin: 0;
+ padding: 0;
+ font-size: small;
+}
+#navcolumn ul {
+ margin: 0;
+ padding: 0;
+ font-size: small;
+}
+#navcolumn li {
+ list-style-type: none;
+ background-image: none;
+ background-repeat: no-repeat;
+ background-position: 0 0.4em;
+ padding-left: 16px;
+ list-style-position: outside;
+ line-height: 1.2em;
+ font-size: smaller;
+}
+#navcolumn li.expanded {
+ background-image: url(../images/expanded.gif);
+}
+#navcolumn li.collapsed {
+ background-image: url(../images/collapsed.gif);
+}
+#navcolumn li.none {
+ text-indent: -1em;
+ margin-left: 1em;
+}
+#poweredBy {
+ text-align: center;
+}
+#navcolumn img {
+ margin-top: 10px;
+ margin-bottom: 3px;
+}
+#poweredBy img {
+ display:block;
+ margin: 20px 0 20px 17px;
+}
+#search img {
+ margin: 0px;
+ display: block;
+}
+#search #q, #search #btnG {
+ border: 1px solid #999;
+ margin-bottom:10px;
+}
+#search form {
+ margin: 0px;
+}
+#lastPublished {
+ font-size: x-small;
+}
+.navSection {
+ margin-bottom: 2px;
+ padding: 8px;
+}
+.navSectionHead {
+ font-weight: bold;
+ font-size: x-small;
+}
+.section {
+ padding: 4px;
+}
+#footer {
+ padding: 3px 10px 3px 10px;
+ font-size: x-small;
+}
+#breadcrumbs {
+ font-size: x-small;
+ margin: 0pt;
+}
+.source {
+ padding: 12px;
+ margin: 1em 7px 1em 7px;
+}
+.source pre {
+ margin: 0px;
+ padding: 0px;
+}
+#navcolumn img.imageLink, .imageLink {
+ padding-left: 0px;
+ padding-bottom: 0px;
+ padding-top: 0px;
+ padding-right: 2px;
+ border: 0px;
+ margin: 0px;
+}
Propchange:
uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/issuesFixed/css/maven-base.css
------------------------------------------------------------------------------
svn:eol-style = native
Added:
uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/issuesFixed/css/maven-theme.css
URL:
http://svn.apache.org/viewvc/uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/issuesFixed/css/maven-theme.css?rev=1858151&view=auto
==============================================================================
---
uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/issuesFixed/css/maven-theme.css
(added)
+++
uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/issuesFixed/css/maven-theme.css
Thu Apr 25 17:32:43 2019
@@ -0,0 +1,141 @@
+body {
+ padding: 0px 0px 10px 0px;
+}
+body, td, select, input, li{
+ font-family: Verdana, Helvetica, Arial, sans-serif;
+ font-size: 13px;
+}
+code{
+ font-family: Courier, monospace;
+ font-size: 13px;
+}
+a {
+ text-decoration: none;
+}
+a:link {
+ color:#36a;
+}
+a:visited {
+ color:#47a;
+}
+a:active, a:hover {
+ color:#69c;
+}
+#legend li.externalLink {
+ background: url(../images/external.png) left top no-repeat;
+ padding-left: 18px;
+}
+a.externalLink, a.externalLink:link, a.externalLink:visited,
a.externalLink:active, a.externalLink:hover {
+ background: url(../images/external.png) right center no-repeat;
+ padding-right: 18px;
+}
+#legend li.newWindow {
+ background: url(../images/newwindow.png) left top no-repeat;
+ padding-left: 18px;
+}
+a.newWindow, a.newWindow:link, a.newWindow:visited, a.newWindow:active,
a.newWindow:hover {
+ background: url(../images/newwindow.png) right center no-repeat;
+ padding-right: 18px;
+}
+h2 {
+ padding: 4px 4px 4px 6px;
+ border: 1px solid #999;
+ color: #900;
+ background-color: #ddd;
+ font-weight:900;
+ font-size: x-large;
+}
+h3 {
+ padding: 4px 4px 4px 6px;
+ border: 1px solid #aaa;
+ color: #900;
+ background-color: #eee;
+ font-weight: normal;
+ font-size: large;
+}
+h4 {
+ padding: 4px 4px 4px 6px;
+ border: 1px solid #bbb;
+ color: #900;
+ background-color: #fff;
+ font-weight: normal;
+ font-size: large;
+}
+h5 {
+ padding: 4px 4px 4px 6px;
+ color: #900;
+ font-size: normal;
+}
+p {
+ line-height: 1.3em;
+ font-size: small;
+}
+#breadcrumbs {
+ border-top: 1px solid #aaa;
+ border-bottom: 1px solid #aaa;
+ background-color: #ccc;
+}
+#leftColumn {
+ margin: 10px 0 0 5px;
+ border: 1px solid #999;
+ background-color: #eee;
+}
+#navcolumn h5 {
+ font-size: smaller;
+ border-bottom: 1px solid #aaaaaa;
+ padding-top: 2px;
+ color: #000;
+}
+
+table.bodyTable th {
+ color: white;
+ background-color: #bbb;
+ text-align: left;
+ font-weight: bold;
+}
+
+table.bodyTable th, table.bodyTable td {
+ font-size: 1em;
+}
+
+table.bodyTable tr.a {
+ background-color: #ddd;
+}
+
+table.bodyTable tr.b {
+ background-color: #eee;
+}
+
+.source {
+ border: 1px solid #999;
+}
+dl {
+ padding: 4px 4px 4px 6px;
+ border: 1px solid #aaa;
+ background-color: #ffc;
+}
+dt {
+ color: #900;
+}
+#organizationLogo img, #projectLogo img, #projectLogo span{
+ margin: 8px;
+}
+#banner {
+ border-bottom: 1px solid #fff;
+}
+.errormark, .warningmark, .donemark, .infomark {
+ background: url(../images/icon_error_sml.gif) no-repeat;
+}
+
+.warningmark {
+ background-image: url(../images/icon_warning_sml.gif);
+}
+
+.donemark {
+ background-image: url(../images/icon_success_sml.gif);
+}
+
+.infomark {
+ background-image: url(../images/icon_info_sml.gif);
+}
+
Propchange:
uima/site/trunk/uima-website/docs/d/uima-ducc-3.0.0/issuesFixed/css/maven-theme.css
------------------------------------------------------------------------------
svn:eol-style = native
