db-derby-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From j..@apache.org
Subject svn commit: rev 36674 - in incubator/derby/site/trunk/src/documentation/content/xdocs: . manuals manuals/admin manuals/develop manuals/getstart manuals/reference manuals/tuning
Date Fri, 20 Aug 2004 22:29:28 GMT
Author: jta
Date: Fri Aug 20 15:29:26 2004
New Revision: 36674

Added:
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt02.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt03.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt04.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt05.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt06.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt07.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt08.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt09.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt10.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt11.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt12.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt13.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt14.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt15.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt16.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt17.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt18.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt19.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt20.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt21.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt22.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt23.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt24.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt25.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt26.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt27.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt28.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt29.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt30.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt31.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt32.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt33.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt34.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt35.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt36.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt37.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt38.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt39.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt40.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt41.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt42.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt43.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt44.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt45.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt46.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt47.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt48.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt49.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt50.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt51.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt52.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt53.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt54.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt55.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt56.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt58.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt59.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt60.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt61.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt62.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt64.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt65.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop02.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop03.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop04.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop05.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop06.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop07.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop08.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop09.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop10.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop100.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop101.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop102.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop103.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop104.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop105.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop106.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop107.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop108.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop109.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop11.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop110.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop111.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop112.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop113.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop114.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop115.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop116.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop117.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop118.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop119.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop12.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop120.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop121.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop122.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop123.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop124.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop125.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop126.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop127.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop128.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop129.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop13.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop130.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop131.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop132.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop133.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop134.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop135.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop136.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop137.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop138.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop139.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop14.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop140.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop141.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop142.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop143.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop144.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop145.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop146.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop147.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop148.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop149.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop15.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop150.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop151.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop152.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop153.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop154.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop156.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop157.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop16.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop17.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop18.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop19.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop20.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop21.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop22.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop23.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop24.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop25.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop26.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop27.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop28.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop29.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop30.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop31.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop32.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop33.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop34.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop35.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop36.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop37.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop38.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop39.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop40.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop41.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop42.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop43.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop44.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop45.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop46.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop47.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop48.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop49.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop50.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop51.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop52.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop53.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop54.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop55.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop56.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop57.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop58.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop59.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop60.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop61.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop62.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop63.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop64.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop65.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop66.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop67.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop68.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop69.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop70.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop71.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop72.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop73.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop74.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop75.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop76.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop77.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop78.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop79.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop80.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop81.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop82.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop83.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop84.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop85.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop86.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop87.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop88.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop89.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop90.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop91.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop92.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop93.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop94.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop95.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop96.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop97.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop98.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop99.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/getstart/
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/getstart/gspr.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/getstart/gspr02.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/getstart/gspr03.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/getstart/gspr04.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/getstart/gspr05.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/getstart/gspr06.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/getstart/gspr08.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/getstart/gspr11.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/getstart/gspr16.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/getstart/gspr21.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/getstart/gspr22.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/getstart/gspr23.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/getstart/gspr24.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/getstart/gspr25.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/getstart/gspr26.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/getstart/gspr27.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/getstart/gspr28.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/getstart/gspr29.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/getstart/gspr30.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/getstart/gspr31.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/getstart/gspr32.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/getstart/gspr33.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/getstart/gspr34.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/getstart/gspr35.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/getstart/gspr36.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/getstart/gspr39.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/getstart/gspr40.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/getstart/index.xml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/index.xml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj02.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj03.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj04.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj05.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj06.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj07.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj08.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj09.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj10.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj100.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj101.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj102.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj103.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj104.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj105.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj106.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj107.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj108.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj109.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj11.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj110.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj111.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj112.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj113.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj114.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj115.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj116.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj117.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj118.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj119.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj12.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj120.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj121.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj122.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj123.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj124.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj125.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj126.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj127.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj128.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj129.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj13.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj130.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj131.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj132.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj133.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj134.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj135.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj136.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj137.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj138.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj139.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj14.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj140.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj141.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj142.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj143.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj144.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj145.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj146.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj147.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj148.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj149.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj15.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj150.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj151.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj152.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj153.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj154.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj155.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj156.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj157.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj158.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj159.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj16.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj160.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj161.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj162.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj163.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj164.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj165.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj166.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj167.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj168.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj169.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj17.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj170.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj171.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj172.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj173.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj174.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj175.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj176.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj177.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj178.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj179.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj18.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj180.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj181.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj182.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj183.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj184.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj185.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj186.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj187.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj188.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj189.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj19.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj190.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj191.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj192.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj193.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj194.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj195.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj196.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj197.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj198.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj199.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj20.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj200.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj201.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj202.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj203.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj204.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj205.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj206.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj207.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj208.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj209.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj21.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj210.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj211.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj212.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj213.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj214.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj215.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj216.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj217.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj218.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj219.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj22.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj220.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj221.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj222.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj223.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj224.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj225.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj226.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj227.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj228.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj229.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj23.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj230.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj231.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj232.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj233.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj234.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj235.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj236.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj237.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj238.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj239.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj24.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj240.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj241.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj242.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj243.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj244.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj245.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj246.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj247.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj248.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj249.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj25.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj250.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj251.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj252.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj253.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj254.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj255.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj256.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj257.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj258.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj259.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj26.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj260.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj261.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj262.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj263.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj264.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj265.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj266.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj267.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj268.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj269.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj27.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj270.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj271.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj272.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj274.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj275.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj28.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj29.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj30.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj31.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj32.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj33.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj34.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj35.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj36.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj37.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj38.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj39.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj40.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj41.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj42.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj43.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj44.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj45.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj46.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj47.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj48.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj49.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj50.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj51.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj52.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj53.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj54.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj55.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj56.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj57.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj58.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj59.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj60.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj61.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj62.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj63.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj64.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj65.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj66.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj67.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj68.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj69.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj70.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj71.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj72.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj73.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj74.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj75.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj76.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj77.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj78.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj79.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj80.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj81.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj82.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj83.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj84.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj85.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj86.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj87.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj88.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj89.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj90.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj91.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj92.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj93.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj94.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj95.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj96.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj97.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj98.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/reference/sqlj99.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf02.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf03.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf04.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf05.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf06.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf07.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf08.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf09.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf10.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf100.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf101.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf102.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf103.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf104.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf105.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf106.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf107.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf108.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf109.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf11.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf110.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf111.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf112.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf113.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf114.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf115.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf116.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf117.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf118.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf12.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf120.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf121.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf13.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf14.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf15.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf16.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf17.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf18.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf19.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf20.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf21.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf22.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf23.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf24.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf25.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf26.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf27.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf28.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf29.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf30.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf31.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf32.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf33.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf34.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf35.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf36.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf37.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf38.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf39.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf40.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf41.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf42.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf43.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf44.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf45.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf46.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf47.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf48.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf49.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf50.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf51.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf52.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf53.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf54.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf55.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf56.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf57.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf58.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf59.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf60.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf61.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf62.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf63.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf64.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf65.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf66.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf67.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf68.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf69.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf70.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf71.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf72.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf73.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf74.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf75.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf76.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf77.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf78.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf79.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf80.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf81.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf82.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf83.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf84.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf85.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf86.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf87.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf88.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf89.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf90.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf91.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf92.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf93.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf94.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf95.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf96.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf97.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf98.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/tuning/perf99.ihtml
   incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/unupdate_name.sh   (contents, props changed)
Modified:
   incubator/derby/site/trunk/src/documentation/content/xdocs/site.xml
   incubator/derby/site/trunk/src/documentation/content/xdocs/tabs.xml
Log:
Added 5 Derby Manuals to the repository

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,28 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Server and Administration Guide</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Fri, 16 Jul 2004 10:56:44">
+<META HTTP-EQUIV="review" CONTENT="Sat, 16 Jul 2005 10:56:44">
+<META HTTP-EQUIV="expires" CONTENT="Sun, 16 Jul 2006 10:56:44">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+<H1>Server and Administration Guide</H1>
+<BR>
+<P><B>First Edition (August 2004)</B>
+
+<P><B>(C) Copyright International Business Machines Corporation 1997, 2004. All rights reserved.</B> <BR>U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
+<P>
+<P><HR>[ <A HREF="hubprnt02.html">Next Page</A><br><A HREF="hubprnt02.html#ToC">Table of Contents</A><br><A HREF="hubprnt65.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt02.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt02.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,113 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Contents</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Fri, 16 Jul 2004 10:56:44">
+<META HTTP-EQUIV="review" CONTENT="Sat, 16 Jul 2005 10:56:44">
+<META HTTP-EQUIV="expires" CONTENT="Sun, 16 Jul 2006 10:56:44">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<BR>
+<HR><H1><A NAME="ToC">Contents</A></H1>
+<P><A  HREF="hubprnt03.html#HDRSII-PREFACE-30074">About this guide</A><BR>
+<MENU>
+<LI><A  HREF="hubprnt04.html#HDRSII-PREFACE-11181">Purpose of this guide</A>
+<LI><A  HREF="hubprnt05.html#HDRSII-PREFACE-22460">Audience</A>
+<LI><A  HREF="hubprnt06.html#HDRSII-PREFACE-23947">How This Document Is Organized</A>
+</MENU>
+<P><B><A  HREF="hubprnt07.html#HDRPARTONE1008131">Derby Server Guide</A></B><BR>
+<MENU>
+<LI><A  HREF="hubprnt08.html#HDRSII-OVERVIEW-11108">Using Derby in a Multi-User Environment</A>
+<MENU>
+<LI><A  HREF="hubprnt09.html#HDRSII-OVERVIEW-17524">Derby in a Server Framework</A>
+<LI><A  HREF="hubprnt10.html#HDRSII-OVERVIEW-38650">About this guide and the Network Server documentation</A>
+</MENU>
+<LI><A  HREF="hubprnt11.html#HDRSII-APPS-59125">Using the Network Server with preexisting Derby applications</A>
+<MENU>
+<LI><A  HREF="hubprnt12.html#HDRSII-APPS-THENETWORKSERVERANDJVMS">The Network Server and JVMs</A>
+<LI><A  HREF="hubprnt13.html#HDRSII-APPS-CHANGINGYOURCLASSPATH">Changing your classpath</A>
+<LI><A  HREF="hubprnt14.html#HDRCBDJHHFD">Starting the Network Server</A>
+<LI><A  HREF="hubprnt15.html#HDRSII-CONFIG-SYSTEMINFORMATION">System information</A>
+<LI><A  HREF="hubprnt16.html#HDRAPPS810777">Accessing the Network Server using the DB2 Universal Driver</A>
+<LI><A  HREF="hubprnt17.html#HDRNSDATASOURCES">Accessing the Network Server using a DataSource</A>
+<LI><A  HREF="hubprnt18.html#HDRSII-APPS-USINGTHEDERBYTOOLSWITHTHENE">Using the Derby tools with the Network Server</A>
+<LI><A  HREF="hubprnt19.html#HDRSII-APPS-">Differences between running Derby in embedded mode and using the Network Server</A>
+<LI><A  HREF="hubprnt20.html#HDRSII-APPS-SETTINGPORTNUMBERS">Setting port numbers</A>
+</MENU>
+<LI><A  HREF="hubprnt21.html#HDRSII-CONFIG-86869">Managing the Derby Network Server</A>
+<MENU>
+<LI><A  HREF="hubprnt22.html#HDRSII-CONFIG-OVERVIEW">Overview</A>
+<LI><A  HREF="hubprnt23.html#HDRSII-CONFIG-SETTINGNETWROKSERVERPROPERTIES">Setting Network Server Properties</A>
+<LI><A  HREF="hubprnt24.html#HDRSII-CONFIG-VERIFYINGSTARTUP">Verifying Startup</A>
+<LI><A  HREF="hubprnt25.html#HDRSII-CONFIG-SHUTTINGDOWNTHENETWORKSERVER">Shutting Down the Network Server</A>
+</MENU>
+<LI><A  HREF="hubprnt26.html#HDRSII-SERVLET-98430">Managing the Derby Network Server Remotely</A>
+<MENU>
+<LI><A  HREF="hubprnt27.html#HDRSERVLET810957">Servlet Interface</A>
+</MENU>
+<LI><A  HREF="hubprnt28.html#HDRSII-ADV-27203">Derby Network Server Advanced Topics</A>
+<MENU>
+<LI><A  HREF="hubprnt29.html#HDRSII-NET-SERV-SECURITY">Network Server Security</A>
+<LI><A  HREF="hubprnt30.html#HDRSII-NET-SERV-RUN">Running the Network Server Under the Security Manager</A>
+<LI><A  HREF="hubprnt31.html#HDRSII-ADV-CONFIGURINGTHENETWORKSERVER">Configuring the network server</A>
+<LI><A  HREF="hubprnt32.html#HDRSII-ADV-LOGFILE">Log File</A>
+<LI><A  HREF="hubprnt33.html#HDRSII-ADV-TRACEFACILITY">Trace Facility</A>
+</MENU>
+<LI><A  HREF="hubprnt34.html#HDRSII-SAMPLE-PROGRAMS">Derby Network Server Sample Programs</A>
+<MENU>
+<LI><A  HREF="hubprnt35.html#HDRSII-OVERVIEW-NSSAMPLE">The NsSample sample program</A>
+<LI><A  HREF="hubprnt36.html#HDRSII-OVERVIEW-NET-SERV-SAMPLE">Network Server sample programs for embedded and client connections</A>
+</MENU></MENU>
+<P><B><A  HREF="hubprnt37.html#HDRPARTTWO1008128">Derby Administration Guide</A></B><BR>
+<MENU>
+<LI><A  HREF="hubprnt38.html#HDRSII-CONSIST-54401">Checking Database Consistency</A>
+<MENU>
+<LI><A  HREF="hubprnt39.html#HDRSII-CONSIST-30301">The SYSCS_CHECK_TABLE function</A>
+<LI><A  HREF="hubprnt40.html#HDRSII-CONSIST-38781">Sample Error Messages</A>
+<LI><A  HREF="hubprnt41.html#HDRSII-CONSIST-24642">Sample Queries</A>
+</MENU>
+<LI><A  HREF="hubprnt42.html#HDRSII-BUBBKUP-98797">Backing Up and Restoring Databases</A>
+<MENU>
+<LI><A  HREF="hubprnt43.html#Header_98">Backing Up a Database</A>
+<LI><A  HREF="hubprnt44.html#HDRSII-BUBBKUP-44223">Restoring a Database from a Backup Copy</A>
+<LI><A  HREF="hubprnt45.html#Header_106">Creating a Database From a Backup Copy</A>
+<LI><A  HREF="hubprnt46.html#HDRROLLFORWARD">Roll-forward Recovery</A>
+</MENU>
+<LI><A  HREF="hubprnt47.html#Header_109">Restoring a Database from a Backup Copy Using OS Commands</A>
+<MENU>
+<LI><A  HREF="hubprnt48.html#HDRSII-BUBBKUP-26328">Restoring a Database Using OS Commands when the Log File Is Not in the Default Location</A>
+<LI><A  HREF="hubprnt49.html#HDRSII-BUBBKUP-66644">Failure Recovery</A>
+<LI><A  HREF="hubprnt50.html#HDRSII-BUBBKUP-43568">Backup History</A>
+</MENU>
+<LI><A  HREF="hubprnt51.html#HDRSII-LOG-98797">Logging on a Separate Device</A>
+<MENU>
+<LI><A  HREF="hubprnt52.html#HDRLOG800206">Using the logDevice Property</A>
+<LI><A  HREF="hubprnt53.html#HDRLOG800241">Example of Creating a Log in a Non-Default Location</A>
+<LI><A  HREF="hubprnt54.html#HDRLOG800279">Example of Moving a Log Manually</A>
+<LI><A  HREF="hubprnt55.html#HDRLOG800315">Issues for Logging in a Non-Default Location</A>
+</MENU>
+<LI><A  HREF="hubprnt56.html#HDRSII-LOCKVTI-42553">Getting Locking Information</A>
+<LI><A  HREF="hubprnt59.html#HDRSII-SPACE-73511">Identifying and Reclaiming Unused Space</A>
+<MENU>
+<LI><A  HREF="hubprnt60.html#HDRSII-SPACE-21579">Overview</A>
+<LI><A  HREF="hubprnt61.html#HDRSII-SPACE-78375">Identifying Unused Space in a Table or Index</A>
+<LI><A  HREF="hubprnt62.html#HDRSII-SPACE-44643">Reclaiming Unused Space</A>
+</MENU>
+<P><A  HREF="hubprnt64.html#HDRTRADEM">Trademarks</A><BR>
+<P><A  HREF="hubprnt65.html#HDRINDEX_START">Index</A><BR>
+<P>
+<P>
+<P><HR>[ <A HREF="hubprnt.html">Previous Page</A><br><A HREF="hubprnt03.html">Next Page</A><br><A HREF="#ToC">Table of Contents</A><br><A HREF="hubprnt65.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt03.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt03.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,29 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>About this guide</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Fri, 16 Jul 2004 10:56:44">
+<META HTTP-EQUIV="review" CONTENT="Sat, 16 Jul 2005 10:56:44">
+<META HTTP-EQUIV="expires" CONTENT="Sun, 16 Jul 2006 10:56:44">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<HR><H1 NAME="HDRSII-PREFACE-30074">About this guide</H1>
+<UL>
+<LI><A HREF="hubprnt04.html#HDRSII-PREFACE-11181">"Purpose of this guide"</A>
+</LI><LI><A HREF="hubprnt05.html#HDRSII-PREFACE-22460">"Audience"</A>
+</LI><LI><A HREF="hubprnt06.html#HDRSII-PREFACE-23947">"How This Document Is Organized"</A>
+</LI></UL>
+<P><HR>[ <A HREF="hubprnt02.html">Previous Page</A><br><A HREF="hubprnt04.html">Next Page</A><br><A HREF="hubprnt02.html#ToC">Table of Contents</A><br><A HREF="hubprnt65.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt04.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt04.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,33 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Purpose of this guide</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Fri, 16 Jul 2004 10:56:44">
+<META HTTP-EQUIV="review" CONTENT="Sat, 16 Jul 2005 10:56:44">
+<META HTTP-EQUIV="expires" CONTENT="Sun, 16 Jul 2006 10:56:44">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<HR><H1 NAME="HDRSII-PREFACE-11181">Purpose of this guide</H1>
+<P>This guide explains how to use Derby in a multiple-client
+environment. It also provides information that a server administrator
+might need to keep Derby running with high performance and reliability in
+a server framework or a multiple-client application server. (When
+running in embedded mode, Derby databases typically do not need any
+administration.)
+<P>To connect multiple clients with Derby, you can embed Derby in a
+server framework of your own choosing, or you can use the Derby Network
+Server. This manual describes these options.
+<P><HR>[ <A HREF="hubprnt03.html">Previous Page</A><br><A HREF="hubprnt05.html">Next Page</A><br><A HREF="hubprnt02.html#ToC">Table of Contents</A><br><A HREF="hubprnt65.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt05.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt05.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,27 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Audience</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Fri, 16 Jul 2004 10:56:44">
+<META HTTP-EQUIV="review" CONTENT="Sat, 16 Jul 2005 10:56:44">
+<META HTTP-EQUIV="expires" CONTENT="Sun, 16 Jul 2006 10:56:44">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<HR><H1 NAME="HDRSII-PREFACE-22460">Audience</H1>
+<P>This book contains two parts. The first part is for developers of
+client/server and multiple-client applications. The second part is for
+administrators.
+<P><HR>[ <A HREF="hubprnt04.html">Previous Page</A><br><A HREF="hubprnt06.html">Next Page</A><br><A HREF="hubprnt02.html#ToC">Table of Contents</A><br><A HREF="hubprnt65.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt06.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt06.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,57 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>How This Document Is Organized</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Fri, 16 Jul 2004 10:56:44">
+<META HTTP-EQUIV="review" CONTENT="Sat, 16 Jul 2005 10:56:44">
+<META HTTP-EQUIV="expires" CONTENT="Sun, 16 Jul 2006 10:56:44">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<HR><H1 NAME="HDRSII-PREFACE-23947">How This Document Is Organized</H1>
+<P>This document includes the following chapters:
+<P>Part One: (Derby Server Guide):
+<UL>
+<LI><I><A HREF="hubprnt08.html#HDRSII-OVERVIEW-11108">"Using Derby in a Multi-User Environment"</A></I> 
+<P>Describes the different options for embedding Derby in a server
+framework; explains the Network Server option.
+</LI><LI><I><A HREF="hubprnt11.html#HDRSII-APPS-59125">"Using the Network Server with preexisting Derby applications"</A></I> 
+<P>Describes how to change existing Derby applications to work with the
+Network Server.
+</LI><LI><I><A HREF="hubprnt21.html#HDRSII-CONFIG-86869">"Managing the Derby Network Server"</A></I> 
+<P>Describes how to manage the Network Server using shell scripts, the command
+line, or the Network Server API.
+</LI><LI><I><A HREF="hubprnt26.html#HDRSII-SERVLET-98430">"Managing the Derby Network Server Remotely"</A></I> 
+<P>Describes how to manage the Network Server using the servlet
+interface.
+</LI><LI><I><A HREF="hubprnt28.html#HDRSII-ADV-27203">"Derby Network Server Advanced Topics"</A></I> 
+<P>Describes advanced topics for Derby Network Server users.
+</LI></UL>
+<P>Part Two (Derby Administration Guide):
+<UL>
+<LI><I><A HREF="hubprnt38.html#HDRSII-CONSIST-54401">"Checking Database Consistency"</A></I> 
+<P>Shows how to check the consistency of Derby databases.
+</LI><LI><I><A HREF="hubprnt42.html#HDRSII-BUBBKUP-98797">"Backing Up and Restoring Databases"</A></I> 
+<P>Shows how to back up a database while it is online.
+</LI><LI><I><A HREF="hubprnt51.html#HDRSII-LOG-98797">"Logging on a Separate Device"</A></I> 
+<P>Shows how to put a database's log on a separate device, which is
+helpful for the performance of large databases.
+</LI><LI><I><A HREF="hubprnt56.html#HDRSII-LOCKVTI-42553">"Getting Locking Information"</A></I> 
+<P>Shows how to get detailed information about locking status.
+</LI><LI><I><A HREF="hubprnt59.html#HDRSII-SPACE-73511">"Identifying and Reclaiming Unused Space"</A></I> 
+<P>Shows how to identify and reclaim unused space in tables and related
+indexes.
+</LI></UL>
+<P><HR>[ <A HREF="hubprnt05.html">Previous Page</A><br><A HREF="hubprnt07.html">Next Page</A><br><A HREF="hubprnt02.html#ToC">Table of Contents</A><br><A HREF="hubprnt65.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt07.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt07.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,33 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Derby Server Guide</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Fri, 16 Jul 2004 10:56:44">
+<META HTTP-EQUIV="review" CONTENT="Sat, 16 Jul 2005 10:56:44">
+<META HTTP-EQUIV="expires" CONTENT="Sun, 16 Jul 2006 10:56:44">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<HR><H1 NAME="HDRPARTONE1008131">Derby Server Guide</H1>
+<P>This part of the guide is divided into the following sections:
+<UL>
+<LI><A HREF="hubprnt08.html#HDRSII-OVERVIEW-11108">Using Derby in a Multi-User Environment</A>
+</LI><LI><A HREF="hubprnt11.html#HDRSII-APPS-59125">Using the Network Server with preexisting Derby applications</A>
+</LI><LI><A HREF="hubprnt21.html#HDRSII-CONFIG-86869">Managing the Derby Network Server</A>
+</LI><LI><A HREF="hubprnt26.html#HDRSII-SERVLET-98430">Managing the Derby Network Server Remotely</A>
+</LI><LI><A HREF="hubprnt28.html#HDRSII-ADV-27203">Derby Network Server Advanced Topics</A>
+</LI><LI><A HREF="hubprnt34.html#HDRSII-SAMPLE-PROGRAMS">Derby Network Server Sample Programs</A>
+</LI></UL>
+<P><HR>[ <A HREF="hubprnt06.html">Previous Page</A><br><A HREF="hubprnt08.html">Next Page</A><br><A HREF="hubprnt02.html#ToC">Table of Contents</A><br><A HREF="hubprnt65.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt08.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt08.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,29 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Using Derby in a Multi-User Environment</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Fri, 16 Jul 2004 10:56:44">
+<META HTTP-EQUIV="review" CONTENT="Sat, 16 Jul 2005 10:56:44">
+<META HTTP-EQUIV="expires" CONTENT="Sun, 16 Jul 2006 10:56:44">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<HR><H1 NAME="HDRSII-OVERVIEW-11108">Using Derby in a Multi-User Environment</H1>
+<P>This chapter contains the following sections:
+<UL>
+<LI><A HREF="hubprnt09.html#HDRSII-OVERVIEW-17524">Derby in a Server Framework</A>
+</LI><LI><A HREF="hubprnt10.html#HDRSII-OVERVIEW-38650">About this guide and the Network Server documentation</A>
+</LI></UL>
+<P><HR>[ <A HREF="hubprnt07.html">Previous Page</A><br><A HREF="hubprnt09.html">Next Page</A><br><A HREF="hubprnt02.html#ToC">Table of Contents</A><br><A HREF="hubprnt65.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt09.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt09.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,213 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Derby in a Server Framework</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="Table-level locking, table-level, Locking, Row-level locking, row-level, Isolation levels, from single application running in embedded mode, Multiple connections, and JDBC, Multi-threading">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Fri, 16 Jul 2004 10:56:44">
+<META HTTP-EQUIV="review" CONTENT="Sat, 16 Jul 2005 10:56:44">
+<META HTTP-EQUIV="expires" CONTENT="Sun, 16 Jul 2006 10:56:44">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-OVERVIEW-17524">Derby in a Server Framework</H1>
+<P>In a sense, Derby is always an embedded product. You can embed
+it in an application where users access the database from a single JVM or in a
+server framework-an application that allows users from different JVMs to
+connect to Derby simultaneously. When Derby is embedded in an
+application, the local JDBC driver calls the local Derby database.
+When Derby is embedded in a server framework, the server framework's
+connectivity software provides data to multiple client JDBC applications over
+a network or the Internet.
+<P>For local or remote multi-user (multiple users accessing from different
+JVMs) connectivity, use the Derby Network Server. If you require
+features other than those included in Network Server, you can embed the basic
+Derby product in another server framework.
+<P><H1><A NAME="HDROVERVIEW825125">Connectivity Configurations</A></H1>
+<P>There are many ways you can embed Derby in a server framework:
+<UL>
+<LI><I>Use the Network Server.</I> 
+<P>The easiest way to provide connectivity to multiple users accessing
+Derby databases from different JVMs. The Derby Network Server
+provides this kind of connectivity to Derby databases within a single
+system or over a network.
+</LI><LI><I>Purchase another server framework.</I> 
+<P>You can use Derby within many server frameworks, such as the
+IBM<SUP>(R)</SUP> WebSphere Application Server.
+</LI><LI><I>Write your own framework.</I>
+</LI></UL>
+<P>Derby's flexibility allows other configurations as well.
+For example, rather than embedding Derby in a server that communicates
+with a client using JDBC, you can embed Derby within a servlet in a Web
+server that communicates with a browser using HTTP.
+<P><H1><A NAME="HDRSII-OVERVIEW-33597">Multiple-client features available in Derby</A></H1>
+<P>The basic Derby product contains some features that are useful for
+developing multi-user applications. These features include:
+<UL>
+<LI>Row-Level Locking </LI>
+<LI>Multiple Concurrency Levels</LI>
+<LI>Multi-Connection and Multi-Threading</LI>
+<LI>Administrative Tools</LI>
+</UL>
+<P><H1><A NAME="HDRSII-OVERVIEW-28261">Row-Level Locking</A></H1>
+<P>
+<A NAME="IDX174"></A>
+<A NAME="IDX175"></A>
+To support multi-user access, Derby utilizes row-level locking.
+Derby can be configured to use table-level locking In environments with
+few concurrent transactions (for example: a read-only database) .
+Table-level locking is preferable if there are few or no writes to the server,
+while row-level locking is essential for good performance if many clients
+write to the server concurrently. The Derby optimizer tunes lock
+choice for queries automatically.
+<A NAME="IDX176"></A>
+<A NAME="IDX177"></A>
+<P><H1><A NAME="HDRSII-OVERVIEW-16172">Multiple Concurrency Levels</A></H1>
+<P>
+<A NAME="IDX178"></A>
+Derby supports <TT>SERIALIZABLE</TT> (RR), <TT>REPEATABLE READ</TT>
+(RS), <TT>READ COMMITTED</TT> (CS), and <TT>READ UNCOMMITTED</TT> (UR)
+isolation levels. <TT>CS</TT> (the default isolation level) provides
+the best balance between concurrency and consistency in multiple-client
+environments. <TT>RS</TT> provides less consistency than
+<TT>RR</TT> but allows more concurrency. <TT>RR</TT> provides
+greatest consistency. <TT>UR</TT> provides maximum concurrency, if
+uncommitted values are allowed in the query. It is typically used if
+approximate results are acceptable. See &quot;Types and Scope of Locks
+in Derby Systems&quot; in the <CITE>Derby Developer's
+Guide</CITE> for more information.
+<P><H1><A NAME="HDRSII-OVERVIEW-65220">Multi-Connection and Multi-Threading</A></H1>
+<P>
+<A NAME="IDX179"></A>
+<A NAME="IDX180"></A>
+Derby allows multiple simultaneous connections to a database, even in
+embedded mode. Derby is also fully multi-threaded, and you can
+have multiple threads active at the same time. However, JDBC semantics
+impose some limitations on multi-threading. See the <CITE>Derby
+Developer's Guide</CITE> for more information.
+<P><H1><A NAME="HDRSII-OVERVIEW-83312">Administrative Tools</A></H1>
+<P>Derby provides some tools and features to assist database
+administrators. These tools are:
+<UL>
+<LI>Consistency checker
+</LI><LI>On-line backup
+</LI><LI>The ability to put a database's log on a separate device
+</LI></UL>
+<P>These tools and features are discussed in part two of this book. See
+the chapters in that section for more information.
+<P><H1><A NAME="HDROVERVIEW825266">The Derby Network Server</A></H1>
+<P>The Derby Network Server provides multi-user connectivity to
+Derby databases within a single system or over a network. The
+Network Server receives and replies to queries from clients using standard
+Distributed Relational Database Architecture (DRDA) protocol. One method
+databases may be accessed through the Derby Network Server is by using 
+the IBM JDBC driver, the DB2 JDBC Universal Driver.   This driver is available
+for free download from <a href=" http://www.ibm.com/developerworks/cloudscape">IBM developerWorks</a>.  Other clients could
+be written to access the database through the Derby Network Server, 
+however none are included with Derby at this time. 
+<P>The network server is a solution for multiple JVMs connecting to the
+database, unlike the embedded scenario where one JVM is all that runs as part
+of the system. When Derby is embedded in a single-JVM application,
+the embedded JDBC driver calls the local Derby. When Derby is
+embedded in a server framework, the server framework's connectivity
+software provides data to multiple client JDBC applications over a network or
+the Internet.
+<P>To run the Derby Network Server, you will need to install the
+following files:
+<P>On the server side (included with Derby): 
+<UL>
+<LI><I>derby.jar</I>
+</LI><LI><I>derbynet.jar</I>
+</LI></UL>
+<P>On the client side (not included with Derby, but may be downloaded
+for no charge from <a href="http://www.ibm.com/developerworks/cloudscape">IBM developerWorks</a>).
+<UL>
+<LI><I>db2jcc.jar</I>
+</LI><LI><I>db2jcc_license_c.jar</I>
+</LI></UL>
+<P>There are several ways to manage the Derby Network Server:
+<UL>
+<LI>through the command line
+</LI><LI>using <I>.bat</I> and <I>.ksh</I> scripts
+</LI><LI>through the servlet interface
+</LI><LI>with your own Java program (written using the Network Server API)
+</LI><LI>by setting Network Server properties
+</LI></UL>
+<P><A HREF="hubprnt11.html#HDRSII-APPS-59125">Using the Network Server with preexisting Derby applications</A> explains how to change existing Java applications that
+currently run against Derby in embedded mode to run against the
+Derby Network Server.
+<P><A HREF="hubprnt21.html#HDRSII-CONFIG-86869">"Managing the Derby Network Server"</A> explains how to manage the Network Server via the command line,
+including starting and stopping it.
+<P><A HREF="hubprnt26.html#HDRSII-SERVLET-98430">"Managing the Derby Network Server Remotely"</A> explains how to use the servlet interface to manage the Network
+Server.
+<P><A HREF="hubprnt28.html#HDRSII-ADV-27203">"Derby Network Server Advanced Topics"</A> contains advanced topics for Derby Network Server
+users.
+<P>Because of the differences in JDBC drivers that are used, you might
+encounter differences in functionality when running Derby in the Network
+Server framework rather than running it embedded in a user application.
+Refer to <A HREF="hubprnt11.html#HDRSII-APPS-59125">Using the Network Server with preexisting Derby applications</A> here for a complete list of the differences between embedded
+and Network Server configurations.
+<P><H1><A NAME="HDROVERVIEW825149">Embedding Servers</A></H1>
+<P>Since Derby is written in Java, you have great flexibility in
+configuring your deployment. For example, you can run Derby, the
+JDBC server framework, and another application in the same JVM as a single
+process.
+<P><H1><A NAME="HDREMBEDDEDSERVER">How to Start an Embedded Server From an Application</A></H1>
+<P>In one thread, the embedding application boots the local JDBC driver for
+its own access.
+<PRE>/* loading the client driver boots the client driver only*/
+Class.forName("org.apache.derby.jdbc.EmbeddedDriver").newInstance();
+Connection conn = DriverManager.getConnection(
+    "jdbc:derby:sample");
+ 
+ 
+</PRE>
+<P>In another thread, the same application boots the server framework to allow
+remote access. Booting the server framework from within the application
+allows both the server and the application to run in the same JVM.
+<P><H1><A NAME="HDREMBEDDEDSERVEREX">Embedded Server Example</A></H1>
+<P>Network Server can be started in another thread automatically when
+Derby boots by setting the
+<I>derby.drda.startNetworkServer</I> property (see <A HREF="hubprnt23.html#HDRSII-CONFIG-SETTINGNETWROKSERVERPROPERTIES">Setting Network Server Properties</A>) or it can be started
+using a program:
+<PRE>import org.apache.derby.drda.NetworkServerControl;
+import java.net.InetAddress;
+NetworkServerControl server = new NetworkServerControl
+	(InetAddress.getByName("localhost"),1527);
+server.start(null);
+</PRE>
+<P>The program starting Network Server can access the database with either the
+embedded driver or the IBM JDBC Universal Driver. The server
+framework's attempt to boot the local JDBC driver is ignored because it
+has already been booted within the application's JVM. The server
+framework simply accesses the instance of Derby already booted.
+There is no conflict between the application and the server framework.
+<P>The remote client can then connect via the client driver:
+<P>
+<PRE>String nsURL="jdbc:derby:net://localhost:1527/
+sample:retrieveMessagesFromServerOnGetMessage=true;";&nbsp;
+java.util.Properties props = new java.util.Properties();
+props.put("user","usr");
+props.put("password","pwd");
+ 
+Class.forName("com.ibm.db2.jcc.DB2Driver").newInstance();
+Connection conn = DriverManager.getConnection(nsURL, props);
+ 
+/*interact with Derby*/
+Statement s = conn.createStatement();
+ 
+ResultSet rs = s.executeQuery(
+"SELECT * FROM HotelBookings");
+</PRE>
+<P><HR>[ <A HREF="hubprnt08.html">Previous Page</A><br><A HREF="hubprnt10.html">Next Page</A><br><A HREF="hubprnt02.html#ToC">Table of Contents</A><br><A HREF="hubprnt65.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt10.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt10.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,32 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>About this guide and the Network Server documentation</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Fri, 16 Jul 2004 10:56:44">
+<META HTTP-EQUIV="review" CONTENT="Sat, 16 Jul 2005 10:56:44">
+<META HTTP-EQUIV="expires" CONTENT="Sun, 16 Jul 2006 10:56:44">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-OVERVIEW-38650">About this guide and the Network Server documentation</H1>
+<P>This guide assumes you are familiar with Derby features,
+administration, and tuning. Before reading this guide, you should first
+learn the basic Derby product by reading the <CITE>Derby
+Developer's Guide</CITE>. Also, since multi-user environments
+typically have performance and tuning issues, you should read <CITE>Tuning
+Derby</CITE>.
+<P>For additional information about the IBM DB2 JDBC Universal Driver, refer
+to the DB2 UDB documentation.
+<P><HR>[ <A HREF="hubprnt09.html">Previous Page</A><br><A HREF="hubprnt11.html">Next Page</A><br><A HREF="hubprnt02.html#ToC">Table of Contents</A><br><A HREF="hubprnt65.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt11.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt11.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,36 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Using the Network Server with preexisting Derby applications</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Fri, 16 Jul 2004 10:56:44">
+<META HTTP-EQUIV="review" CONTENT="Sat, 16 Jul 2005 10:56:44">
+<META HTTP-EQUIV="expires" CONTENT="Sun, 16 Jul 2006 10:56:44">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<HR><H1 NAME="HDRSII-APPS-59125">Using the Network Server with preexisting Derby applications</H1>
+<P>You must make certain changes to Java applications that currently run
+against Derby in embedded mode, for them to work with the Derby
+Network Server. The following topics discuss these changes:
+<UL>
+<LI><I><A HREF="hubprnt12.html#HDRSII-APPS-THENETWORKSERVERANDJVMS">The Network Server and JVMs</A></I>
+</LI><LI><I><A HREF="hubprnt13.html#HDRSII-APPS-CHANGINGYOURCLASSPATH">Changing your classpath</A></I>
+</LI><LI><I><A HREF="hubprnt14.html#HDRCBDJHHFD">Starting the Network Server</A></I>
+</LI><LI><I><A HREF="hubprnt16.html#HDRAPPS810777">Accessing the Network Server using the DB2 Universal Driver</A></I>
+</LI><LI><I><A HREF="hubprnt18.html#HDRSII-APPS-USINGTHEDERBYTOOLSWITHTHENE">Using the Derby tools with the Network Server</A></I>
+</LI><LI><I><A HREF="hubprnt19.html#HDRSII-APPS-">Differences between running Derby in embedded mode and using the Network Server</A></I>
+</LI><LI><I><A HREF="hubprnt20.html#HDRSII-APPS-SETTINGPORTNUMBERS">Setting port numbers</A></I>
+</LI></UL>
+<P><HR>[ <A HREF="hubprnt10.html">Previous Page</A><br><A HREF="hubprnt12.html">Next Page</A><br><A HREF="hubprnt02.html#ToC">Table of Contents</A><br><A HREF="hubprnt65.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt12.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt12.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,26 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>The Network Server and JVMs</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Fri, 16 Jul 2004 10:56:44">
+<META HTTP-EQUIV="review" CONTENT="Sat, 16 Jul 2005 10:56:44">
+<META HTTP-EQUIV="expires" CONTENT="Sun, 16 Jul 2006 10:56:44">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-APPS-THENETWORKSERVERANDJVMS">The Network Server and JVMs</H1>
+<P>The Derby Network Server is compatible with Java<SUP>(TM)</SUP> 2 Platform,
+Standard Edition, v 1.3.1 (J2SE) and above.
+<P><HR>[ <A HREF="hubprnt11.html">Previous Page</A><br><A HREF="hubprnt13.html">Next Page</A><br><A HREF="hubprnt02.html#ToC">Table of Contents</A><br><A HREF="hubprnt65.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt13.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt13.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,65 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Changing your classpath</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="derbynet.jar, derby.jar, db2jcc.jar, db2jcc_license_c.jar">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Fri, 16 Jul 2004 10:56:44">
+<META HTTP-EQUIV="review" CONTENT="Sat, 16 Jul 2005 10:56:44">
+<META HTTP-EQUIV="expires" CONTENT="Sun, 16 Jul 2006 10:56:44">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-APPS-CHANGINGYOURCLASSPATH">Changing your classpath</H1>
+<P>The following jar files must be in your server classpath to use the Network
+Server and Universal Driver:
+<UL>
+<LI>
+<A NAME="IDX181"></A>
+<I>derbynet.jar<TT></TT></I> 
+<P>The Network Server jar file that contains the Network Server code.
+The jar file is only necessary for the process that starts the Network Server
+in addition to the standard Derby jar files.
+</LI><LI>
+<A NAME="IDX182"></A>
+<I>derby.jar</I>
+<P>This file must be in your classpath to use any of the Derby Network
+Server functions.
+</LI><LI>
+<A NAME="IDX183"></A>
+<I><I>db2jcc.jar</I> </I> 
+<P>This jar file must be in your classpath to use the DB2 JDBC Universal
+Driver. The jar file is the client communication layer necessary for
+client side communication with the Network Server using the DB2 JDBC Universal
+Driver. The <I>db2jcc.jar</I> file needs to be in the client
+side classpath to use the DB2 JDBC Universal Driver to access
+Derby.
+</LI><LI>
+<A NAME="IDX184"></A>
+<I><I>db2jcc_license_c.jar</I> </I> 
+<P>This is the license jar file, and it must be in your client machine's
+classpath to use the DB2 JDBC Universal Driver.
+</LI></UL>
+<P>Derby provides script files for setting the class path to work with
+the Network Server. The scripts are located in
+$DERBY_INSTALL\frameworks\NetworkServer\bin.
+<UL>
+<LI><I>setNetworkClientCP.bat </I>(Windows)
+</LI><LI><I>setNetworkClientCP.ksh </I>(UNIX)
+</LI><LI><I>setNetworkServerCP.bat </I>(Windows)
+</LI><LI><I>setNetworkServerCP.ksh </I>(UNIX)
+</LI></UL>
+<P>See Chapter <A HREF="hubprnt21.html#HDRSII-CONFIG-86869">Managing the Derby Network Server</A> and <CITE>Getting Started with Derby</CITE> for more
+information on setting class path.
+<P><HR>[ <A HREF="hubprnt12.html">Previous Page</A><br><A HREF="hubprnt14.html">Next Page</A><br><A HREF="hubprnt02.html#ToC">Table of Contents</A><br><A HREF="hubprnt65.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt14.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt14.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,106 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Starting the Network Server</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="from scripts, Starting Network Server, starting, Network Server, starting from a command line, starting from the API">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Fri, 16 Jul 2004 10:56:44">
+<META HTTP-EQUIV="review" CONTENT="Sat, 16 Jul 2005 10:56:44">
+<META HTTP-EQUIV="expires" CONTENT="Sun, 16 Jul 2006 10:56:44">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRCBDJHHFD">Starting the Network Server</H1>
+<A NAME="IDX185"></A>
+<A NAME="IDX186"></A>
+<P>The <I>startNetworkServer.bat </I>(Windows) and
+<I>startNetworkServer.ksh </I>(UNIX) scripts start the
+server. These scripts are located in the
+$DERBY_INSTALL/frameworks/NetworkServer/bin directory, where
+$DERBY_INSTALL is the Derby root installation
+directory.
+<P>You can only run NetworkServerControl commands from the host that started
+the Network Server.
+<P>The Network Server itself resides in the
+<I>$DERBY_INSTALL/lib</I>.
+<P>For example, if you have installed Derby in the default directory on
+the C drive (in Windows) and you have set up your classpath correctly, type
+the following command:
+<PRE><B><I>$DERBY_INSTALL</I>\frameworks\NetworkServer\bin\startNetworkserver.bat</B>
+</PRE>
+<P>where <I>$DERBY_INSTALL</I> is the directory where you
+installed Derby.
+<DL><DT><B>Note:</B></DT><DD>The default system directory is the directory in which Derby was
+started. (See the <CITE>Derby Developer's Guide</CITE> for
+more information about the system directory.)
+</DD></DL>
+<P>You can set
+<I><I>$DERBY_INSTALL</I>\frameworks\NetworkServer\bin</I>
+in your path to shorten the command.
+<P>By default Network Server will only listen to requests on the loopback
+address so will only accept connections from the localhost.
+<P><H1><A NAME="HDRSII-CONFIG-ALTERINGTHESTARTNETWORKSERVERSCR">Altering the startNetworkServer script</A></H1>
+<P>You can modify the <I>startNetworkServer</I> script to do any of the
+following:
+<UL>
+<LI>Specify a port number other than the default(1527).
+<P>Add <TT>-p &lt;<I>portnumber</I>></TT> after the <TT>start</TT>
+command: 
+<PRE><B>java org.apache.derby.drda.NetworkServerControl start -p <I>1368</I></B>
+</PRE>
+</LI><LI>Specify a specific interface (host name or IP address) to listen on other
+than the default (localhost).
+<P>Add <TT>-h</TT> to the command:
+<PRE><B>java org.apache.derby.drda.NetworkServerControl start -h myhost -p <I>1368</I></B>
+</PRE>
+<P>This will enable connections from other hosts. You can specify a
+host name, ip address or 0.0.0.0 to listen on all
+interfaces. You should run under the Java security manager and enable
+user authentication before using this option.
+</LI></UL>
+<P><H1><A NAME="HDRCONFIG814934">Starting the Network Server without the script</A></H1>
+<A NAME="IDX187"></A>
+<P>If you don't want to use one of the scripts provided, you can start
+the Network Server on the command line. The syntax for the command
+looks like this:
+<PRE><B>java org.apache.derby.drda.NetworkServerControl start [-h &lt;<I>host</I>>] [-p &lt;<I>portNumber</I>>]</B>
+</PRE>
+<P><H1><A NAME="HDRCONFIG814963">Starting the Network Server from a Java application</A></H1>
+<A NAME="IDX188"></A>
+<P>There are two ways of starting the network server from a Java
+application.
+<UL>
+<LI>You can include the following line in the
+<TT>derby.properties</TT> file: 
+<PRE>derby.drda.startNetworkServer=true
+</PRE>This starts the server on the default port, 1527, listening on
+<TT>localhost</TT> (all interfaces). You may specify a different port
+or a specific interface in the <TT>derby.properties</TT>
+file. For example:
+<PRE>derby.drda.portNumber=1110
+derby.drda.host=myhost
+</PRE>You can also specify the <TT>startNetworkServer</TT> and
+<TT>portNumber</TT> properties using a Java command:
+<PRE>java -Dderby.drda.startNetworkServer=true&nbsp;
+	-Dderby.drda.portNumber=1110
+	-Dderby.drda.host=myhost yourApp
+</PRE>
+</LI><LI>You can use the <TT>NetworkServerControl</TT> API to start the Network
+Server from a separate thread within a Java application: 
+<PRE>NetworkServerControl server = new NetworkServerControl(null);
+server.start (null);
+</PRE>The <TT>NetworkServerControl.start</TT> method does not return
+until the server is shut down, so you should run it in its own thread.
+</LI></UL>
+<P><HR>[ <A HREF="hubprnt13.html">Previous Page</A><br><A HREF="hubprnt15.html">Next Page</A><br><A HREF="hubprnt02.html#ToC">Table of Contents</A><br><A HREF="hubprnt65.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt15.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt15.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,95 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>System information</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Fri, 16 Jul 2004 10:56:44">
+<META HTTP-EQUIV="review" CONTENT="Sat, 16 Jul 2005 10:56:44">
+<META HTTP-EQUIV="expires" CONTENT="Sun, 16 Jul 2006 10:56:44">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-CONFIG-SYSTEMINFORMATION">System information</H1>
+<P>You can get information about the Network Server such as version and
+current property values, Java information, and Derby database server
+information, using the <I>sysinfo </I>tool.
+<TT><I>Sysinfo</I></TT> is available from scripts, the command line, the
+NetworkServerControl API, or through the servlet interface.
+<P>The following scripts are located in the
+$DERBY_INSTALL/frameworks/NetworkServer/bin directory, and will
+return an error if the Derby Network Server is not started.
+<P>To run <I>sysinfo</I> from the scripts provided, in Windows, use:
+<PRE>sysinfo.bat [-h &lt;<I>host</I>>][-p &lt;<I>portnumber</I>>]&nbsp;
+</PRE>
+<P>and for Unix, use:
+<PRE>sysinfo.ksh [-h &lt;<I>host</I>>] [&lt;-p <I>portnumber</I>>]&nbsp;
+</PRE>
+<P><H1><A NAME="HDRCONFIG815768">Using the command line</A></H1>
+<P>To run <I>sysinfo</I> from the command line, use the following command
+while the Network Server is running:
+<PRE><B>java org.apache.derby.drda.NetworkServerControl sysinfo [-h &lt;<I>host</I>>][-p &lt;<I>portnumber</I>>]&nbsp;</B>
+</PRE>
+<P><H1><A NAME="HDRCONFIG815853">Using the API</A></H1>
+<P>The <I>sysinfo</I> method produces the same information as the
+<TT><I>sysinfo</I></TT> command. The signature for this method is
+<PRE><B>String getSysinfo();</B>
+</PRE>
+<P>For example:
+<PRE>NetworkServerControl serverControl = new NetworkServerControl();
+String myinfo = serverControl.getSysinfo();
+</PRE>
+<P>returns information about the Network server running on the current machine
+on port 1527.
+<P><H1><A NAME="HDRAPPSRUNTIMEINFO">runtimeinfo</A></H1>
+<P>Use the <I>runtimeinfo</I> command to get runtime information about the
+Network Server. This command will provide information about memory
+usage and current sessions, including the user, database, and prepared
+statement information.
+<P><B>Using the command line:</B>
+<P>To run <I>runtimeinfo</I> from the command line, enter:
+<PRE>java org.apache.derby.drda.NetworkServerControl runtimeinfo [-h &lt;host>]
+[&lt;-p portnumber>]&nbsp;
+</PRE>
+<P><B>Using the API:</B>
+<P>The <I>getRuntimeInfo</I> method returns the same information as the
+<I>runtimeinfo</I> command. The signature for the
+<I>getRuntimeInfo</I> method is:
+<PRE><B>String getRuntimeInfo()</B>
+</PRE>
+<P>For example:
+<PRE>NetworkServerControl serverControl = new NetworkServerControl();
+String myinfo = serverControl.getRuntimeInfo();&nbsp;
+</PRE>
+<P><H1><A NAME="HDRCONFIG815822">getCurrent Properties</A></H1>
+<P>There is an additional Java method you can use to get information about the
+Network Server - the <I>getCurrent Properties</I> method.
+<P>The <I>getCurrentProperties</I> method returns a Properties object with
+the value of all the NetServer properties as they are currently set.
+<P>The signature of this method is:
+<PRE><B>Properties getCurrentProperties();</B>
+</PRE>
+<P>For example:
+<PRE>NetworkServerControl server = new NetworkServerControl();
+Properties p = server.getCurrentProperties();
+p.list(System.out);
+System.out.println(p.getProperty("derby.drda.host"));
+</PRE>
+<P>As shown above, you can get the current properties and then work with
+individual properties if needed using various API's on
+<I>Properties</I> class. You can also print all the properties on
+<TT>System.out</TT> using the <TT>Properties.list()</TT>
+method.
+<P>See <A HREF="hubprnt26.html#HDRSII-SERVLET-98430">"Managing the Derby Network Server Remotely"</A> for information on getting system information using the servlet
+interface.
+<P><HR>[ <A HREF="hubprnt14.html">Previous Page</A><br><A HREF="hubprnt16.html">Next Page</A><br><A HREF="hubprnt02.html#ToC">Table of Contents</A><br><A HREF="hubprnt65.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt16.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt16.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,141 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Accessing the Network Server using the DB2 Universal Driver</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Fri, 16 Jul 2004 10:56:44">
+<META HTTP-EQUIV="review" CONTENT="Sat, 16 Jul 2005 10:56:44">
+<META HTTP-EQUIV="expires" CONTENT="Sun, 16 Jul 2006 10:56:44">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRAPPS810777">Accessing the Network Server using the DB2 Universal Driver</H1>
+<P>When connecting to the Network Server, your application needs to load a
+driver and connection URL specific to the Network Server. In addition,
+you specify a user name and password. If you have not set up
+authentication, you can use any value for the user name and password.
+The driver you need to access the network server is:
+<PRE>com.ibm.db2.jcc.DB2Driver
+</PRE>
+<P>The URL needed to access the network server is:
+<PRE>jdbc:derby:net://&lt;<I>server</I>>[:&lt;<I>port</I>>]/
+&lt;<I>databaseName</I>>[;&lt;Derby URL attribute>=&lt;value> [;...]]
+[:&lt;Universal Driver attribute>=&lt;value>; [...;]]
+</PRE>
+<P>The syntax for connection to the Network Server differs slightly from the
+syntax used to connect to Derby running in embedded mode. After
+the database name and attributes you can include attributes for the DB2 JDBC
+Driver. You must include a semicolon after the last Universal Driver
+attribute.
+<UL>
+<LI><I>server</I> 
+<P>The name of the machine where the server is running. It can be the
+name of the machine (for example, <I>buffy</I>) or the address, for
+example, <I>158.58.62.225</I>.
+<DL><DT><B>Note:</B></DT><DD>Unless the Network Server was started with the <TT>-h</TT> option or the
+<I>derby.drda.host</I> property set, this value should
+be <TT>localhost</TT>.
+</DD></DL>
+</LI><LI><I>port</I> 
+<P>The port the server is listening to. The default is 1527.
+</LI><LI><I>database name</I> 
+<P>The name of the database you are connecting to. The database name
+can be at most 18 characters long. You must use double quotes (&quot;)
+to include path information in the database name. Alternately, you can
+specify path information by setting the property
+<I>derby.system.home</I> in either the
+<TT><I>derby.properties</I></TT> file or in the Java
+environment when starting the Network Server. See the <CITE>
+Derby Developer's Guide</CITE> for more information about defining the
+system home.
+</LI><LI><I>derby URL attribute=value</I> 
+<P>Optional database connection URL attributes supported by Derby.
+See the <CITE>Derby Developer's Guide</CITE> for more
+information.
+</LI><LI><I>Universal Driver Attribute=value</I> 
+<P>Optional database connection URL attributes supported by the DB2 Universal
+JDBC Driver.
+<P>The DB2 JDBC Universal Driver requires that you set the Universal Driver
+user and password attributes to non-null values.
+<P>Here's a list of the DB2 Universal JDBC Driver attributes available to
+you when running the Network Server:
+<UL>
+<LI><I>user </I> 
+<P>User name (required by the Universal JDBC Driver).
+</LI><LI><I>password</I> 
+<P>User password (required by the Universal JDBC Driver).
+</LI><LI><I>portNumber</I> 
+<P>The TCP/IP port number where the Network Server listens for connection
+requests to this data source. The default is 1527.
+</LI><LI><I>retrieveMessagesFromServerOnGetMessage</I> 
+<P>Displays error messages from the server.
+</LI><LI><I>readOnly</I> 
+<P>Creates a read-only connection. The default is false.
+</LI><LI><I>logWriter</I>
+<P>A character output stream. All logging and tracing messages print to
+the <TT>logWriter</TT> property.
+</LI><LI><I>traceLevel</I>
+<P>Specifies the granularity of logging messages to the <TT>logWriter</TT>
+property.
+</LI><LI><I>traceFile</I>
+<P>Provides an explicit file location for the trace output.
+</LI><LI><I>securityMechanism</I>
+<P>Indicates what type of security mechanism is used.
+</LI><LI><I>deferPrepares</I>
+<P>Controls when prepared statements are physically prepared in the database
+server. The default value is <TT>true</TT>.
+</LI></UL>
+</LI></UL>
+<P><H1><A NAME="HDRAPPS810699">Examples</A></H1>
+<P><B>Example 1</B>
+<P>The following example connects to the default server name
+<I>localhost</I> on the default port, <I>1527</I>, and to the database
+<I>sample</I>. It specifies the URL attributes <I>user,
+password,</I> and <I>retrieveMessagesFromServerOnGetMessage</I>.
+You must set the Universal Driver Attributes user name and password.
+<PRE>jdbc:derby:net://localhost:1527/sample:user=judy;password=no12see;
+retrieveMessagesFromServerOnGetMessage=true;
+</PRE>
+<P><B>Example 2</B>
+<P>The following example specifies both Derby and Universal Driver
+Attributes: 
+<PRE>jdbc:derby:net://localhost:1527/sample;create=true:user=judy;
+password=no12see;retrieveMessagesFromServerOnGetMessage=true;
+</PRE>
+<P><B>Example 3</B>
+<P>This example connects to the default server name <I>localhost</I> on
+the default port, <I>1527</I>, and includes the path in the database name
+portion of the URL. The database name must be delimited by double
+quotes and you cannot specify Derby attributes on the URL.
+<PRE>jdbc:derby:net://localhost:1527/"c:/my-db-dir/my-db-name":user=judy;
+password=no12see;retrieveMessagesFromServerOnGetMessage=true;
+</PRE>
+<P><B>Example 4</B>
+<P>The following is a sample program fragment that connects to the Network
+Server using the Universal Driver:
+<PRE>String databaseURL = "jdbc:derby:net://localhost:1527/sample";
+<B>// Load IBM JDBC Universal Driver class</B>
+Class.forName("com.ibm.db2.jcc.DB2Driver");
+<B>// Set user and password properties</B>
+Properties properties = new Properties();
+properties.put("user", "APP");
+properties.put("password", "APP");
+properties.put("retreiveMessagesFromServerOnGetMessage", "true");
+<B>// Get a connection</B>
+Connection conn = DriverManager.getConnection(databaseURL, properties);&nbsp;
+</PRE>
+<P><B>Universal Driver System information</B>
+<P>The Derby Network Server is compatible with the DB2 JDBC Universal
+Driver release 1.2 and higher.
+<P><HR>[ <A HREF="hubprnt15.html">Previous Page</A><br><A HREF="hubprnt17.html">Next Page</A><br><A HREF="hubprnt02.html#ToC">Table of Contents</A><br><A HREF="hubprnt65.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt17.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt17.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,64 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Accessing the Network Server using a DataSource</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Fri, 16 Jul 2004 10:56:44">
+<META HTTP-EQUIV="review" CONTENT="Sat, 16 Jul 2005 10:56:44">
+<META HTTP-EQUIV="expires" CONTENT="Sun, 16 Jul 2006 10:56:44">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRNSDATASOURCES">Accessing the Network Server using a DataSource</H1>
+<P>The DB2 Universal Driver DataSources
+<TT>com.ibm.db2.jcc.DB2SimpleDataSource</TT> and
+<TT>com.ibm.db2.jcc.DB2ConnectionPoolDataSource</TT>
+are supported with Network Server. See the DB2 Universal Driver
+Documentation for details.
+<P><H1><A NAME="HDRNSDATASOURCEXMP">Example</A></H1>
+<P>The following example uses
+<TT>com.ibm.db2.jcc.DB2SimpleDataSource</TT> to
+access the Network Server:
+<PRE>public static javax.sql.DataSource getDS(String database, String user, String
+password) throws SQLException
+{
+com.ibm.db2.jcc.DB2SimpleDataSource ds = new com.ibm.db2.jcc.DB2SimpleDataSource();
+ 
+// DatabaseName can include Derby URL Attributes
+ds.setDatabaseName(database);
+ 
+if (user != null)
+   ds.setUser(user);
+if (password != null)
+   ds.setPassword(password);
+ 
+// The host on which network server is running
+ds.setServerName("localhost");
+ 
+// port on which Network Server is listening
+ds.setPortNumber(1527);
+ 
+// Driver type must be 4 to access Network Server
+ds.setDriverType(4);
+ 
+return ds;
+}
+ 
+</PRE>
+<P>The program then can connect:
+<PRE>javax.sql.DataSource ds = getDS("mydb;create=true", null, null);
+// Note:  user and password are required on connection
+Connection conn = ds.getConnection("usr2", "pass2");
+</PRE>
+<P><HR>[ <A HREF="hubprnt16.html">Previous Page</A><br><A HREF="hubprnt18.html">Next Page</A><br><A HREF="hubprnt02.html#ToC">Table of Contents</A><br><A HREF="hubprnt65.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt18.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt18.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,61 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Using the Derby tools with the Network Server</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="using with Network Server, ij, ij and, Network Server, dblook, dblook and">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Fri, 16 Jul 2004 10:56:44">
+<META HTTP-EQUIV="review" CONTENT="Sat, 16 Jul 2005 10:56:44">
+<META HTTP-EQUIV="expires" CONTENT="Sun, 16 Jul 2006 10:56:44">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-APPS-USINGTHEDERBYTOOLSWITHTHENE">Using the Derby tools with the Network Server</H1>
+<P>The Derby tools <TT>ij</TT> and <TT>dblook</TT> work in embedded
+mode and client/server mode.
+<P><H1><A NAME="HDRAPPS811302">ij</A></H1>
+<A NAME="IDX189"></A>
+<A NAME="IDX190"></A>
+<P>To use ij with the Universal Driver, specify the following driver:
+<P><I>com.ibm.db2.jcc.DB2Driver </I>
+<P>This can be done using a script:
+<UL>
+<LI>Directory:
+<I>$DERBY_INSTALL\frameworks\NetworkServer\bin\</I> (Windows)
+</LI><LI>Script: <I>ij.bat</I> (Windows)
+</LI><LI>Script: <I>ij.ksh</I> (Unix)
+</LI></UL>
+<P>on the command line:
+<PRE>java -Dij.driver='com.ibm.db2.jcc.DB2Driver' org.apache.derby.tools.ij&nbsp;
+</PRE>
+<P>or by using the DRIVER command:
+<PRE>ij> DRIVER 'com.ibm.db2.jcc.DB2Driver';&nbsp;
+</PRE>
+<P>Connection is done by specifying the URL:
+<PRE>ij> CONNECT 'jdbc:derby:net://localhost:1527/sample'
+	USER 'judy' PASSWORD 'no12see';
+</PRE>
+<P>See <A HREF="hubprnt16.html#HDRAPPS810777">Accessing the Network Server using the DB2 Universal Driver</A> for additional URL examples.
+<P>The Universal Driver requires a user and password.
+<P><H1><A NAME="HDRAPPS811345">dblook</A></H1>
+<A NAME="IDX191"></A>
+<A NAME="IDX192"></A>
+<P>To use <TT>dblook</TT> with the Universal Driver, make sure the Network
+Server is running (see <A HREF="hubprnt14.html#HDRCBDJHHFD">Starting the Network Server</A>), and then include the necessary Derby and Universal
+Driver connection attributes as part of the database URL. For
+example:
+<PRE>java org.apache.derby.tools.dblook -d
+	'jdbc:derby:net://localhost:1527/sample:user=judy;password=no12see;'
+</PRE>
+<P><HR>[ <A HREF="hubprnt17.html">Previous Page</A><br><A HREF="hubprnt19.html">Next Page</A><br><A HREF="hubprnt02.html#ToC">Table of Contents</A><br><A HREF="hubprnt65.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt19.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt19.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,172 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Differences between running Derby in embedded mode and using the Network Server</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="Derby features unsupported in, Network Server, and Network Server, XA, error messages and, and the Network Server, Error messages, User authentication, user authentication and, com.ibm.db2.jcc.DB2BaseDataSource. CLEAR_TEXT_ PASSWORD_SECURITY, supported by Network Server, Security properties, supported security properties, com.ibm.db2.jcc.DB2BaseDataSource. USER_ONLY_SECURITY, com.ibm.db2.jcc.DB2BaseDataSource. ENCRYPTED_USER_AND_ PASSWORD_SECURITY, using with Network Server, Encrypted UserID and password, IBM Java Cryptography Extension (JCE), ibmjceprovider.jar, ibmjcefw.jar, ibmpkderby.jar, ibmpkcs11.jar">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Fri, 16 Jul 2004 10:56:44">
+<META HTTP-EQUIV="review" CONTENT="Sat, 16 Jul 2005 10:56:44">
+<META HTTP-EQUIV="expires" CONTENT="Sun, 16 Jul 2006 10:56:44">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-APPS-">Differences between running Derby in embedded mode and using the Network Server</H1>
+<P><H1><A NAME="HDRAPPS811581">Features not supported</A></H1>
+<A NAME="IDX193"></A>
+<P><H1><A NAME="HDRAPPS811478">XA</A></H1>
+<A NAME="IDX194"></A>
+<P>XA is not supported.
+<P><H1><A NAME="HDRAPPS-ISOLATION-LEV">Isolation level</A></H1>
+<P>When you use the Derby Network Server, the
+<I>java.sql.Connection.setTransactionIsolation()</I>
+method behaves somewhat differently than when Derby runs in embedded
+mode:
+<OL TYPE=1>
+<LI><I>setTransactionIsolation()</I> does not commit the
+transaction.
+</LI><LI>The new isolation level is applied only to statements created after
+<I>setTransactionIsolation()</I> is called. Statements created with
+the previous isolation level will continue to be executed with the isolation
+level that was set when they were created.
+</LI></OL>
+<P><H1><A NAME="HDRAPPS811974">Error messages</A></H1>
+<A NAME="IDX195"></A>
+<A NAME="IDX196"></A>
+<P>The Network Server reports only the first error/warning if multiple errors
+or warnings occur for a given statement. For example:
+<PRE>ij> create table ai (x int, y int generated always as identity
+	(increment by 200000000));
+ij> insert into ai (x) values (1),(2),(3),(4),(5),(6),(7),
+(8),(9),(10),(11),(12),(13),(14),(15),(16),(17),(18),(19);
+</PRE>
+<P>The Network Server generates the following error with the exception message
+appended to error:
+<PRE>ERROR 42Z24: Overflow occurred in identity for column 'Y' in table 'A I':
+SQLSTATE: 22003: The resulting value is outside the range&nbsp;
+for the data type INTEGER.
+</PRE>
+<P>Using the Derby embedded driver, you would see the following two SQL
+exceptions: :
+<PRE>ERROR 42Z24: Overflow occurred in identity for column 'Y' in table 'AI'.&nbsp;
+ 
+</PRE>
+<PRE>ERROR 22003: The resulting value is outside the range for the data type INTEGER.
+</PRE>
+<P>This is because the Universal Driver reports only one SQLException or one
+<I>SQLWarning </I>per statement.
+<P>By default, the Universal Driver will not return message text. Use
+the <TT>retrieveMessagesFromServerOnGetMessage</TT> attribute to see message
+text. For example, if
+<TT>retrieveMessagesFromServerOnGetMessage=false</TT>:
+<PRE>ij> select * from akdfj;
+ERROR 42X05: DB2 SQL error: SQLCODE: -1, SQLSTATE: 42X05, SQLERRMC: AKDFJ 42X05
+</PRE>
+<P>If <TT>retrieveMessagesFromServerOnGetMessage=true</TT>:
+<PRE>ij> select * from akdfj;
+ERROR 42X05: Table 'AKDFJ' does not exist.
+</PRE>
+<P><H1><A NAME="HDRSII-APPS-49914">User authentication</A></H1>
+<A NAME="IDX197"></A>
+<A NAME="IDX198"></A>
+<P>As when running Derby in embedded mode, you can enable or disable
+server-side user authentication when using the Derby Network
+Server. However, the default security mechanism
+(<TT>CLEAR_TEXT_PASSWORD</TT>) requires that you supply both the user name
+and password.
+<P>
+<A NAME="IDX199"></A>
+In addition to the default user name and password security mechanism,
+<I>com.ibm.db2.jcc.DB2BaseDataSource.CLEAR_TEXT_PASSWORD_SECURITY,
+</I> Derby Network Server supports the following security properties
+<A NAME="IDX200"></A>
+<A NAME="IDX201"></A>
+:
+<UL>
+<LI><I>
+<A NAME="IDX202"></A>
+UserID 
+(</I><TT><I>com.ibm.db2.jcc.DB2BaseDataSource.USER_ONLY_SECURITY)</I></TT>
+<P>
+<P>When using this mechanism, only the user property needs to be
+specified.
+</LI><LI><I>
+<A NAME="IDX203"></A>
+Encrypted UserID and encrypted password 
+(com.ibm.db2.jcc.DB2BaseDataSource.ENCRYPTED_USER
+AND_PASSWORD_SECURITY)</I> 
+<P>When using this mechanism, both password and user are encrypted.
+</LI></UL>
+<P>The user's name specified upon connection is the default schema for
+the connection, if a schema with that name exists. See the &quot;User
+Names and Schemas&quot; section in the <CITE>
+Derby Developer's Guide</CITE>.
+<P>If you specify any other security mechanism, you will receive an
+exception.
+<P>To change the default, you can specify another security mechanism as a
+property or on the URL (using the securityMechanism attribute) when making the
+connection.
+<P><H1><A NAME="HDRAPPS811631">Network Server user authentication when user authentication is on in Derby</A></H1>
+<P>When user authentication is enabled in Derby, you have the option of
+using the default security mechanism, user name and password, or of specifying
+that the security mechanism be encrypted user and password.
+<P><H1><A NAME="HDRAPPS811656">Network Server user authentication when user authentication is off in Derby</A></H1>
+<P>When user authentication is turned off in Derby, you can use any of
+the security mechanism options.
+<P>A user and password need to be provided for all security mechanisms except
+<I>USER_ONLY_SECURITY</I>. However, because user authentication is
+disabled in the Derby server, the user name and password you supply does
+not have to be one recognized as valid by Derby.
+<P><H1><A NAME="HDRAPPS811695">Encrypted user ID and password</A></H1>
+<A NAME="IDX204"></A>
+<P>
+<A NAME="IDX205"></A>
+To use encrypted user id and password, you need to have IBM JCE (Java
+Cryptography Extension) 1.2.1 or later. You can use it
+with any versions of IBM or Sun's Java<SUP>(TM)</SUP> 2 Platform, Standard Edition,
+v 1.2 (J2SE).
+<P>IBM JDK 1.4 or later comes with IBM JCE, so there's no separate
+IBM JCE installation needed. For earlier versions of IBM JDK or other
+JDK's:
+<OL TYPE=1>
+<LI>Copy the IBM JCE jar files to the <I>jre/lib/ext</I> directory of the
+IBM SDK's installation home. The jar files include: 
+<A NAME="IDX206"></A>
+<TT><I>ibmjceprovider.jar</I></TT>, <TT><I>
+<A NAME="IDX207"></A>
+ibmjcefw.jar</I></TT>, 
+<A NAME="IDX208"></A>
+<TT><I>ibmpkderby.jar</I></TT>, and 
+<A NAME="IDX209"></A>
+<TT><I>ibmpkcs11.jar</I></TT>.
+</LI><LI>Modify the <I>java.security</I> file under
+<TT><I>jre/lib/security</I></TT>, in the list of providers (and
+preference order) section, change it to be: 
+<PRE>security.provider.1=sun.security.provider.Sun
+security.provider.2=com.ibm.crypto.provider.IBMJCE
+</PRE>
+<P>Note that you need both lines (if you are installing the IBM JCE on a Dun
+JDK) and that order is important.
+</LI><LI>During JDBC connection using JCC, specify <I>9</I> as
+<TT><I>securityMechanism</I></TT> in the connection property to use
+encrypted user id and password. 
+<P>If an encrypted database is booted in the Network Server, users can connect
+to the database without giving the <I>bootPassword</I>. The first
+connection to the database must provide the <I>bootPassword</I> , but all
+subsequent connections do not need to supply the
+<I>bootPassword</I>. To remove access from the encrypted database,
+use the <I>dbshutdown</I> option to shutdown the database.
+<P>The Network Server uses IBM JCE 1.2.1 to do the encryption,
+as does the IBM DB2 JDBC Universal Driver.
+</LI></OL>
+<P><HR>[ <A HREF="hubprnt18.html">Previous Page</A><br><A HREF="hubprnt20.html">Next Page</A><br><A HREF="hubprnt02.html#ToC">Table of Contents</A><br><A HREF="hubprnt65.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt20.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt20.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,38 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Setting port numbers</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="setting port numbers for, Network Server, Network Server and, Port numbers">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Fri, 16 Jul 2004 10:56:44">
+<META HTTP-EQUIV="review" CONTENT="Sat, 16 Jul 2005 10:56:44">
+<META HTTP-EQUIV="expires" CONTENT="Sun, 16 Jul 2006 10:56:44">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-APPS-SETTINGPORTNUMBERS">Setting port numbers</H1>
+<A NAME="IDX210"></A>
+<A NAME="IDX211"></A>
+<P>By default, Derby using the Network Server listens on TCP/IP port
+number 1527. If you want to use a different port number, you can
+specify it on the command line when starting the Network Server. For
+example:
+<PRE><B>java org.apache.derby.drda.NetworkServerControl start -p 1088</B>
+</PRE>
+<P>It is better, however, to specify these changes in the
+<I>startNetworkServer.bat</I> or
+<I>startNetworkServer.ksh</I> scripts or by setting the
+<TT>derby.drda.portNumber</TT> property in
+<TT>derby.properties</TT>. See <A HREF="hubprnt14.html#HDRCBDJHHFD">Starting the Network Server</A> for more information.
+<P><HR>[ <A HREF="hubprnt19.html">Previous Page</A><br><A HREF="hubprnt21.html">Next Page</A><br><A HREF="hubprnt02.html#ToC">Table of Contents</A><br><A HREF="hubprnt65.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt21.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt21.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,33 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Managing the Derby Network Server</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Fri, 16 Jul 2004 10:56:44">
+<META HTTP-EQUIV="review" CONTENT="Sat, 16 Jul 2005 10:56:44">
+<META HTTP-EQUIV="expires" CONTENT="Sun, 16 Jul 2006 10:56:44">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<HR><H1 NAME="HDRSII-CONFIG-86869">Managing the Derby Network Server</H1>
+<P>This chapter explains how to manage the Network Server.
+<UL>
+<LI><A HREF="hubprnt22.html#HDRSII-CONFIG-OVERVIEW">Overview</A>
+</LI><LI><A HREF="hubprnt23.html#HDRSII-CONFIG-SETTINGNETWROKSERVERPROPERTIES">Setting Network Server Properties</A>
+</LI><LI><A HREF="hubprnt14.html#HDRCBDJHHFD">Starting the Network Server</A>
+</LI><LI><A HREF="hubprnt24.html#HDRSII-CONFIG-VERIFYINGSTARTUP">Verifying Startup</A>
+</LI><LI><A HREF="hubprnt25.html#HDRSII-CONFIG-SHUTTINGDOWNTHENETWORKSERVER">Shutting Down the Network Server</A>
+</LI><LI><A HREF="hubprnt15.html#HDRSII-CONFIG-SYSTEMINFORMATION">System information</A>
+</LI></UL>
+<P><HR>[ <A HREF="hubprnt20.html">Previous Page</A><br><A HREF="hubprnt22.html">Next Page</A><br><A HREF="hubprnt02.html#ToC">Table of Contents</A><br><A HREF="hubprnt65.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt22.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt22.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,94 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Overview</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="compatibility with Network Server, JVMs, and JVM compatibility, Network Server, for Network Server, Class path, class path and, NetworkServerControl class, NetworkServerControl class and, NetworkServerControl API">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Fri, 16 Jul 2004 10:56:44">
+<META HTTP-EQUIV="review" CONTENT="Sat, 16 Jul 2005 10:56:44">
+<META HTTP-EQUIV="expires" CONTENT="Sun, 16 Jul 2006 10:56:44">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-CONFIG-OVERVIEW">Overview</H1>
+<P>The Derby Network Server can run as a stand-alone server, with
+Derby as an embedded part of the application. It can also be
+managed remotely from a Web server through a servlet interface. This
+chapter explains how to manage the Network Server using shell scripts, the
+command line, or the Network Server API. See <A HREF="hubprnt26.html#HDRSII-SERVLET-98430">"Managing the Derby Network Server Remotely"</A> for information about starting and shutting down the Network
+Server using the servlet interface.
+<P>You start the Derby Network Server using the command line or using the
+Derby Server API. (Derby provides scripts for you to use to
+start the server from the command line.) Before starting the server,
+you will probably set certain Derby and Network Server properties.
+<P><H1><A NAME="HDRCONFIG813340">The Network Server and JVMs</A></H1>
+<A NAME="IDX212"></A>
+<A NAME="IDX213"></A>
+<P>The Derby Network Server is compatible with <B>Java<SUP>(TM)</SUP> 2 Platform,
+Standard Edition, v 1.3.1 (J2SE)</B> and above.
+<P><H1><A NAME="HDRCONFIG813498">Setting the Class Path</A></H1>
+<A NAME="IDX214"></A>
+<A NAME="IDX215"></A>
+<P>Before starting the server, be sure the jar files for the Network Server
+and Derby libraries are in your class path. For instance, if you
+have installed Derby under <I>C:\derby</I>, add
+<I>C:\derby\lib\derby.jar</I> and
+<I>C:\derby\lib\derbynet.jar</I> to the class path.
+Also add the libraries for any Java classes used in your databases.
+<P>Derby provides script files for setting the class path, located in
+<I>$DERBY_INSTALL\frameworks\NetworkServer\bin</I>.
+<UL>
+<LI><I>setNetworkClientCP.bat </I>(Windows)
+</LI><LI><I>setNetworkClientCP.ksh </I>(UNIX)
+</LI><LI><I>setNetworkServerCP.bat </I>(Windows)
+</LI><LI><I>setNetworkServerCP.ksh </I>(UNIX)
+</LI></UL>
+<P>See <CITE>Getting Started with Derby</CITE> for more information on
+setting class path.
+<P><H1><A NAME="HDRCONFIG813694">Using the NetworkServerControl API</A></H1>
+<A NAME="IDX216"></A>
+<A NAME="IDX217"></A>
+<P>If you are using the API, you need to create a instance of the
+<I>NetworkServerControl</I> class first.
+<P>There are two constructor methods for the <I>NetworkServerControl</I>
+class: 
+<UL>
+<LI><I>NetworkServerControl()</I>
+<P>Creates an instance which listens on the port set by the
+<I>derby.drda.portNumberProperty</I> or the default
+port (1527) if the property is not set. It will also listen on the host
+set by the <I>derby.drda.host</I> property or the
+loopback address if the property is not set. The default constructor
+disallows remote connections. It is equivalent to calling
+<TT>NetworkServerControl(InetAddress.getByName("localhost"),1527)</TT>
+if no properties are set.
+</LI><LI><I>NetworkServerControl(InetAddress address, int portNumber)</I> 
+<P>Creates an instance which listens on the specified <I>portNumber</I> on
+the specified address. The <I>InetAddress</I> will be passed to
+<I>ServerSocket</I>. NULL is an invalid address value. The
+following examples show how you might allow Network Server to accept
+connections from other hosts:
+<PRE>//accepts connections from other hosts on an IPv4 system
+NetworkServerControl serverControl = nwe NetworkServerControl
+		(InetAddress.getByName("0.0.0.0"),1527)&nbsp;
+</PRE>
+<PRE>//accepts connections from other hosts on an IPV6 system
+NetworkServerControl serverControl = nwe NetworkServerControl
+		(InetAddress.getByName("::"),1527)&nbsp;
+</PRE>
+<DL><DT><B>Note:</B></DT><DD>Before enabling connections from other systems, ensure that you are running
+under security manager.
+</DD></DL>
+</LI></UL>
+<P><HR>[ <A HREF="hubprnt21.html">Previous Page</A><br><A HREF="hubprnt23.html">Next Page</A><br><A HREF="hubprnt02.html#ToC">Table of Contents</A><br><A HREF="hubprnt65.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt23.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt23.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,212 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Setting Network Server Properties</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="properties, Network Server, Properties, derby.drda.startNetworkServer, derby.drda.portNumber, derby.drda.traceDirectory, derby.drda.host, derby.drda.logConnections, derby.drda.minThreads, derby.drda.maxThreads, derby.drda.timeslice">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Fri, 16 Jul 2004 10:56:44">
+<META HTTP-EQUIV="review" CONTENT="Sat, 16 Jul 2005 10:56:44">
+<META HTTP-EQUIV="expires" CONTENT="Sun, 16 Jul 2006 10:56:44">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-CONFIG-SETTINGNETWROKSERVERPROPERTIES">Setting Network Server Properties</H1>
+<A NAME="IDX218"></A>
+<A NAME="IDX219"></A>
+<P>You can specify Network Server properties on the command line, in the
+<I>.bat</I> or <I>.ksh</I> file (loading the properties
+by executing 'java -D'), or in the
+<TT><I>derby.properties </I></TT>file. Properties in
+the command line or <I>.bat </I>or <I>.ksh</I> file take
+precedence over properties in the
+<TT><I>derby.properties</I></TT> file. Arguments
+given to commands on the command line take precedence over properties
+values.
+<P>The following properties can be specified:
+<UL>
+<LI><A HREF="#SPTSII-CONFIG-STARTNETWORKSERVER">derby.drda.startNetworkServer</A>
+</LI><LI><A HREF="#SPTSII-CONFIG-PORTNUMBER">derby.drda.portNumber</A>
+</LI><LI><A HREF="#HDRSII-CONFIG-DB2JDRDATRACEDIRECTORY">derby.drda.traceDirectory</A>
+</LI><LI><A HREF="#HDRSII-CONFIG-">derby.drda.traceAll</A>
+</LI><LI><A HREF="#HDRSII-CONFIG-DB2JDRDALOGCONNECTIONS">derby.drda.logConnections</A>
+</LI><LI><A HREF="#SPTDRDAHOST">derby.drda.host</A>
+</LI><LI><A HREF="#SPTDRDAMINTHREADS">derby.drda.minThreads</A>
+</LI><LI><A HREF="#SPTDRDAMAXTHREADS">derby.drda.maxThreads</A>
+</LI><LI><A HREF="#SPTDRDATIMESLICE">derby.drda.timeslice</A>
+</LI></UL>
+<A NAME="SPTSII-CONFIG-STARTNETWORKSERVER"></A>
+<P>
+<H1><A NAME="HDRSII-CONFIG-STARTNETWORKSERVER">derby.drda.startNetworkServer</A></H1>
+<A NAME="IDX220"></A>
+<P>Use the <I>derby.drda.startNetworkServer</I>
+property to simplify embedding the Network Server in your application.
+When you set <I>derby.drda.startNetworkServer</I>, the
+Network Server will automatically start when you start Derby. Only
+one Network Server can be started in a JVM.
+<P><STRONG>Syntax</STRONG>
+<PRE>&lt;derby.drda.startNetworkServer=[true<br>false]&gt;
+</PRE>
+<P><STRONG>Default</STRONG>
+<P>false
+<P><STRONG>Example</STRONG>
+<PRE><B>derby.drda.startNetworkServer=true</B>
+</PRE>
+<P><STRONG>Static or Dynamic</STRONG>
+<P>Static. You must shut down the Network Server and restart Derby
+for this change to take effect.
+<A NAME="SPTSII-CONFIG-PORTNUMBER"></A>
+<P>
+<H1><A NAME="HDRSII-CONFIG-PORTNUMBER">derby.drda.portNumber</A></H1>
+<A NAME="IDX221"></A>
+<P>Indicates the port number to use. 
+<A NAME="IDX222"></A>
+<P><STRONG>Syntax</STRONG>
+<PRE>&lt;derby.drda.portNumber=<I>portnumber</I>&gt;;
+</PRE>
+<P><STRONG>Default</STRONG>
+<P>If no port number is specified, 1527 is the default.
+<P><STRONG>Example</STRONG>
+<PRE><B>derby.drda.portNumber=1110</B>
+</PRE>
+<P><STRONG>Static or Dynamic</STRONG>
+<P>Static. You must restart the Network Server for changes to take
+effect.
+<A NAME="SPTDRDAHOST"></A>
+<P>
+<H1><A NAME="HDRDRDAHOST">derby.drda.host</A></H1>
+<A NAME="IDX223"></A>
+<P>Indicates that Network Server listen on a specific network
+interface. This allows multiple instances of Network Server to run on a
+single machine each using its own unique host:port combination.
+The host needs to be set to enable remote connections. By default, the
+Network Server will only listen on the loopback address. If the
+property is set to 0.0.0.0, Network Server will listen on
+all interfaces. Ensure that you are running under the security manager
+and that you have user authorization enabled before enabling remote
+connections with this property.
+<P><STRONG>Syntax</STRONG>
+<PRE>&lt;derby.drda.host=<I>hostname</I>&gt;;
+</PRE>
+<P><STRONG>Default</STRONG>
+<P>If no host is specified, the Network Server listens on the loopback address
+of the current machine (localhost).
+<P><STRONG>Example</STRONG>
+<PRE><B>derby.drda.host=myhost</B>
+</PRE>
+<P><STRONG>Static or Dynamic</STRONG>
+<P>Static. You must restart the Network Server for changes to take
+effect.
+<P>
+<H1><A NAME="HDRSII-CONFIG-DB2JDRDATRACEDIRECTORY">derby.drda.traceDirectory</A></H1>
+<P>Indicates the location for tracing files.
+<P><STRONG>Syntax</STRONG>
+<PRE>&lt;derby.drda.traceDirectory=<I>tracefiledirectory</I>&gt;;
+</PRE>
+<P><STRONG>Default</STRONG>
+<P>If the <I>derby.system.home</I> property has been
+set, it is the default. Otherwise, the default is the current
+directory.
+<P><STRONG>Example</STRONG>
+<PRE><B>derby.drda.traceDirectory=c:/Derby/trace</B>
+</PRE>
+<P><STRONG>Static or Dynamic</STRONG>
+<P>Dynamic. System values can be changed using commands or the servlet
+interface after the Network Server has been started.
+<P>
+<H1><A NAME="HDRSII-CONFIG-">derby.drda.traceAll</A></H1>
+<P>Turns tracing on for all sessions.
+<P><STRONG>Syntax</STRONG>
+<PRE>&lt;derby.drda.traceAll=[true|false]&gt;;
+</PRE>
+<P><STRONG>Default</STRONG>
+<P>False.
+<P><STRONG>Example</STRONG>
+<PRE><B>derby.drda.traceAll=true</B>
+</PRE>
+<P><STRONG>Static or Dynamic</STRONG>
+<P>
+<A NAME="IDX224"></A>
+Dynamic. System values can be changed using commands or the servlet
+interface after the Network Server has been started.
+<P>
+<H1><A NAME="HDRSII-CONFIG-DB2JDRDALOGCONNECTIONS">derby.drda.logConnections</A></H1>
+<P>Indicates whether to log connections and disconnections.
+<P><STRONG>Syntax</STRONG>
+<PRE>&lt;derby.drda.logConnections=[true|false]&gt;t;
+</PRE>
+<P><STRONG>Default</STRONG>
+<P>False.
+<P><STRONG>Example</STRONG>
+<P><B>derby.drda.logConnections=true</B>
+<P><STRONG>Static or Dynamic</STRONG>
+<P>Dynamic. System values can be changed using commands or the servlet
+interface after the Network Server has been started.
+<A NAME="SPTDRDAMINTHREADS"></A>
+<P>
+<H1><A NAME="HDRDRDAMINTHREADS">derby.drda.minThreads</A></H1>
+<A NAME="IDX225"></A>
+<P>Use the <I>derby.drda.minThreads</I> property to set
+a minimum number of connection threads that Network Server will
+allocate. By default, connection threads are allocated as
+needed.
+<P><STRONG>Syntax</STRONG>
+<PRE>&lt;derby.drda.minThreads=<I>numthreads</I>&gt;;
+</PRE>
+<P><STRONG>Default</STRONG>
+<P>1
+<P><STRONG>Example</STRONG>
+<PRE><B>derby.drda.minThreads=10</B>
+</PRE>
+<P><STRONG>Static or Dynamic</STRONG>
+<P>Static.
+<A NAME="SPTDRDAMAXTHREADS"></A>
+<P>
+<H1><A NAME="HDRDRDAMAXTHREADS">derby.drda.maxThreads</A></H1>
+<A NAME="IDX226"></A>
+<P>Use the <I>derby.drda.maxThreads</I> property to set
+a maximum number of connection threads that Network Server will
+allocate. If all of the connection threads are currently being used and
+the Network Server has already allocated the maximum amount of threads, then
+threads will be shared using the
+<I>derby.drda.timeslice</I> property to determine when
+sessions will be swapped.
+<P><STRONG>Syntax</STRONG>
+<PRE>&lt;derby.drda.maxThreads=<I>numthreads</I>&gt;;
+</PRE>
+<P><STRONG>Default</STRONG>
+<P>1
+<P><STRONG>Example</STRONG>
+<PRE><B>derby.drda.maxThreads=50</B>
+</PRE>
+<P><STRONG>Static or Dynamic</STRONG>
+<P>Static.
+<A NAME="SPTDRDATIMESLICE"></A>
+<P>
+<H1><A NAME="HDRDRDATIMESLICE">derby.drda.timeslice</A></H1>
+<A NAME="IDX227"></A>
+<P>Use the <I>derby.drda.timeslice</I> to set the
+number of milliseconds each connection will use before yielding to another
+connection. This property is only relevant if the
+<I>derby.drda.maxThreads</I> property is set.
+<P><STRONG>Syntax</STRONG>
+<PRE>&lt;derby.drda.timeslice=<I>milliseconds</I>&gt;;
+</PRE>
+<P><STRONG>Default</STRONG>
+<P>1
+<P><STRONG>Example</STRONG>
+<PRE><B>derby.drda.timeslice=2000</B>
+</PRE>
+<P><STRONG>Static or Dynamic</STRONG>
+<P>Static.
+<P><HR>[ <A HREF="hubprnt22.html">Previous Page</A><br><A HREF="hubprnt24.html">Next Page</A><br><A HREF="hubprnt02.html#ToC">Table of Contents</A><br><A HREF="hubprnt65.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt24.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt24.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,61 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Verifying Startup</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="verifying startup, Network Server">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Fri, 16 Jul 2004 10:56:44">
+<META HTTP-EQUIV="review" CONTENT="Sat, 16 Jul 2005 10:56:44">
+<META HTTP-EQUIV="expires" CONTENT="Sun, 16 Jul 2006 10:56:44">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-CONFIG-VERIFYINGSTARTUP">Verifying Startup</H1>
+<A NAME="IDX228"></A>
+<P>Derby provides the ability to ping the server.
+<P>You can use the scripts <TT><I>NetworkServerControl.bat</I>
+</TT>or <TT><I>NetworkServerControl.ksh</I></TT>, with the
+<TT><I>ping</I></TT> command. For example:
+<PRE><B>NetworkServerControl ping [-h &lt;<I>host</I>&gt;;]&nbsp;
+[-p &lt;<I>portnumber</I>&gt;]
+</PRE>
+<P>You can also use the NetworkServerControl command:
+<PRE><B>&lt;java org.apache.derby.drda.NetworkServerControl ping [-h &lt;<I>host</I>&gt;]&nbsp;
+[-p &lt;<I>portnumber</I>&gt;]&nbsp;
+</PRE>
+<P><B>Verifying startup using the API</B>
+<P>You can use the NetworkServerControl API to verify startup from within a
+Java application:
+<PRE><B>ping();&nbsp;</B>
+</PRE>
+<P>The following example uses a method to verify startup. It will try
+to verify for the specified number of seconds:
+<PRE>private static boolean isServerStarted(NetworkServerControl server, int ntries)
+	{
+		for (int i = 1; i &lt;= ntries; i ++)
+		{
+			try {
+				Thread.sleep(500);
+				server.ping();
+				return true;
+			}
+			catch (Exception e) {
+				if (i == ntries)
+					return false;
+			}
+		}
+		return false;
+	}
+</PRE>
+<P><HR>[ <A HREF="hubprnt23.html">Previous Page</A><br><A HREF="hubprnt25.html">Next Page</A><br><A HREF="hubprnt02.html#ToC">Table of Contents</A><br><A HREF="hubprnt65.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt25.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt25.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,61 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Shutting Down the Network Server</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="from scripts, Shutting down Network Server, shutting down, Network Server, from the command line, from the API">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Fri, 16 Jul 2004 10:56:44">
+<META HTTP-EQUIV="review" CONTENT="Sat, 16 Jul 2005 10:56:44">
+<META HTTP-EQUIV="expires" CONTENT="Sun, 16 Jul 2006 10:56:44">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-CONFIG-SHUTTINGDOWNTHENETWORKSERVER">Shutting Down the Network Server</H1>
+<A NAME="IDX229"></A>
+<A NAME="IDX230"></A>
+<P>Derby databases shut down normally when the Network Server is shut
+down, as long as user authentication is not enabled If user authentication is
+enabled, you must explicitly shut down the databases, specifying a
+valid Derby user name and password. Shut down the databases before
+shutting down the Network Server. The databases are shut down either by
+an applicationDerby server or when itself is shut down.
+<P>To shut down the Network Server from the scripts provided for Windows,
+use:
+<PRE><B>stopNetworkServer.bat [-h <I>&lt;host></I>] [-p <I>&lt;portnumber></I>]&nbsp;</B>
+</PRE>
+<P>and for Unix, use:
+<PRE><B>stopNetworkServer.ksh [-h <I>&lt;host></I>] [-p <I>&lt;portnumber></I>]&nbsp;</B>
+</PRE>
+<P>These scripts are located in the
+<I>$DERBY_INSTALL/frameworks/NetworkServer/bin</I>
+directory.
+<P><H1><A NAME="HDRCONFIG815333">Shutting Down from the Command Line</A></H1>
+<A NAME="IDX231"></A>
+<P>From the command line, shut down the Network Server with the following
+command:
+<PRE><B>java org.apache.derby.drda.NetworkServerControl
+	shutdown [-h <I>&lt;host></I>][-p <I>&lt;portnumber></I>]&nbsp;</B>
+</PRE>
+<P><H1><A NAME="HDRCONFIG815357">Shutting Down Using the API</A></H1>
+<A NAME="IDX232"></A>
+<P>You can use the NetworkServerControl API to shut down the Network Server
+from within a Java application, using the following syntax:
+<PRE>shutdown();
+</PRE>
+<P>For example, the following command shuts down the Network Server running on
+the current machine using port 1527.
+<PRE>NetworkServerControl server = new NetworkServerControl();
+server.shutdown();
+</PRE>
+<P><HR>[ <A HREF="hubprnt24.html">Previous Page</A><br><A HREF="hubprnt26.html">Next Page</A><br><A HREF="hubprnt02.html#ToC">Table of Contents</A><br><A HREF="hubprnt65.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt26.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt26.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,24 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Managing the Derby Network Server Remotely</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Fri, 16 Jul 2004 10:56:44">
+<META HTTP-EQUIV="review" CONTENT="Sat, 16 Jul 2005 10:56:44">
+<META HTTP-EQUIV="expires" CONTENT="Sun, 16 Jul 2006 10:56:44">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<HR><H1 NAME="HDRSII-SERVLET-98430">Managing the Derby Network Server Remotely</H1>
+<P><HR>[ <A HREF="hubprnt25.html">Previous Page</A><br><A HREF="hubprnt27.html">Next Page</A><br><A HREF="hubprnt02.html#ToC">Table of Contents</A><br><A HREF="hubprnt65.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt27.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt27.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,125 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Servlet Interface</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="from the servlet interface, Starting Network Server, using servlet interface, Shutting down Network Server">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Fri, 16 Jul 2004 10:56:44">
+<META HTTP-EQUIV="review" CONTENT="Sat, 16 Jul 2005 10:56:44">
+<META HTTP-EQUIV="expires" CONTENT="Sun, 16 Jul 2006 10:56:44">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSERVLET810957">Servlet Interface</H1>
+<P>The servlet interface can be used to start the network server
+remotely. To use the servlet interface, the servlet must be registered
+with a web server and <I>derby.system.home</I> must be
+known to the web server.
+<P>A Web application archive (WAR) file, <I>derby.war</I>, for
+the Derby Network Server is available in
+<I>$DERBY_INSTALL/frameworks/NetworkServer/war.</I>
+This WAR registers the Network Server's servlet at the relative path
+<I>/derbynet</I>. Please see the documentation for your Application
+Server for instructions on how to install it.
+<P>For example, if <I>derby.war</I> is installed in Websphere
+Application Server with a context root of <I>cns</I>, then the URL of the
+server is:
+<PRE>http://server[:port]/cns/derbynet
+</PRE>
+<DL><DT><B>Note:</B></DT><DD>A servlet engine is not part of the Network Server.
+</DD></DL>
+<P>The servlet takes the following optional configuration parameters:
+<UL>
+<LI><I>portNumber</I> 
+<P>specifies the port number to be used by the network server.
+</LI><LI><I>startNetworkServerOnInit</I>
+<P>specifies that the network server is to be started when the servlet is
+initialized.
+</LI><LI><I>tracingDirectory</I> 
+<P>specifies the location for trace files. If the tracing directory is
+not specified, the traces are placed in
+<I>derby.system.home</I>.
+</LI></UL>
+<P>The servlet displays the following pages:
+<P><H1><A NAME="HDRSERVLET810694">Start-up page</A></H1>
+<A NAME="IDX233"></A>
+<P>Use the Start-up page to start the server.
+<P>You can choose the following options from the startup page:
+<UL>
+<LI>turn logging on when the server is started.
+</LI><LI>turn tracing on for all sessions when the server is started.
+</LI><LI>start the server.
+</LI></UL>
+<P><H1><A NAME="HDRSERVLET810717">Running page</A></H1>
+<A NAME="IDX234"></A>
+<P>If the network server is running (whether it was started by initializing
+the servlet or in some other manner), the running page is displayed.
+The running page indicates whether logging is on or off, whether tracing is on
+or off, and if tracing is on, indicates for which session.
+<P>You can use the running page to stop the server and turn logging and
+tracing on or off, boot or shut down databases. The following options
+are available from the running page:
+<UL>
+<LI>start or stop logging.
+</LI><LI>start or stop tracing all sessions.
+</LI><LI>specify session to trace. (If you choose this option, the Trace
+session page is displayed.)
+</LI><LI>change tracing directory (If you choose this option, the Trace directory
+page is displayed.)
+</LI><LI>specify threading parameters for network server. (If you choose
+this option, the Thread parameters page is displayed.)
+</LI><LI>stop the application server.
+</LI></UL>
+<P><H1><A NAME="HDRSERVLET810796">Trace session page</A></H1>
+<P>If on the running page you choose to specify a session to trace, this page
+is displayed. You must enter the Session ID.
+<P>You are given the option to turn tracing on or off or return to the
+previous menu. When you push the Trace On/Off button, information
+indicating the current tracing state is displayed.
+<P><H1><A NAME="HDRSERVLET810822">Trace directory page</A></H1>
+<P>This page is displayed if the you choose to change the tracing directory on
+the Running page. You must enter the Trace Directory.
+<P>You are given the option to set a tracing directory or return to the
+previous menu. Additional information is displayed indicating the
+current tracing directory when you push the Set Directory button.
+<P><H1><A NAME="HDRSERVLET810850">Test Connection</A></H1>
+<P>This page is displayed if the test connection button is pressed.
+<P>Enter the following applicable information:
+<UL>
+<LI>Database Directory (optional). 
+<P>Specify database to test connection to or leave blank to test connecting to
+network server.
+</LI><LI>UserID (required if user authentication is enabled)
+</LI><LI>Password (required if user authentication is enabled)
+</LI></UL>
+<P>You are given the option to test the connection or return to the previous
+Menu.
+<P>Information about the success or failure of the connection test will be
+displayed when the test connection button is pushed.
+<P><H1><A NAME="HDRSERVLET810910">Set Network Server Parameters</A></H1>
+<P>The first page is displayed if the thread parameter button is
+pressed. This page sets the new parameters. Enter the following
+applicable information:
+<UL>
+<LI>New maximum number of threads
+</LI><LI>New thread time slice
+</LI></UL>
+<DL><DT><B>Note:</B></DT><DD>If the either the maximum or time slice parameters are left blank, that value
+is left unchanged from the current setting.
+</DD></DL>
+<P>You are given the option of setting the parameters or returning to the
+previous menu.
+<P>The updated values for the maximum and the time slice are displayed when
+Set Network Server Parameters is pressed.
+<P><HR>[ <A HREF="hubprnt26.html">Previous Page</A><br><A HREF="hubprnt28.html">Next Page</A><br><A HREF="hubprnt02.html#ToC">Table of Contents</A><br><A HREF="hubprnt65.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt28.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt28.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,33 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Derby Network Server Advanced Topics</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Fri, 16 Jul 2004 10:56:44">
+<META HTTP-EQUIV="review" CONTENT="Sat, 16 Jul 2005 10:56:44">
+<META HTTP-EQUIV="expires" CONTENT="Sun, 16 Jul 2006 10:56:44">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<HR><H1 NAME="HDRSII-ADV-27203">Derby Network Server Advanced Topics</H1>
+<P>This chapter discusses the following advanced topics for users of the
+Derby Network Server:
+<UL>
+<LI><A HREF="hubprnt29.html#HDRSII-NET-SERV-SECURITY">Network Server Security</A>
+</LI><LI><A HREF="hubprnt30.html#HDRSII-NET-SERV-RUN">Running the Network Server Under the Security Manager</A>
+</LI><LI><A HREF="hubprnt31.html#HDRSII-ADV-CONFIGURINGTHENETWORKSERVER">Configuring the network server</A>
+</LI><LI><A HREF="hubprnt32.html#HDRSII-ADV-LOGFILE">Log File</A>
+</LI><LI><A HREF="hubprnt33.html#HDRSII-ADV-TRACEFACILITY">Trace Facility</A>
+</LI></UL>
+<P><HR>[ <A HREF="hubprnt27.html">Previous Page</A><br><A HREF="hubprnt29.html">Next Page</A><br><A HREF="hubprnt02.html#ToC">Table of Contents</A><br><A HREF="hubprnt65.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt29.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt29.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,66 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Network Server Security</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="Network Server Security, and security changes, Network Server">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Fri, 16 Jul 2004 10:56:44">
+<META HTTP-EQUIV="review" CONTENT="Sat, 16 Jul 2005 10:56:44">
+<META HTTP-EQUIV="expires" CONTENT="Sun, 16 Jul 2006 10:56:44">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-NET-SERV-SECURITY">Network Server Security</H1>
+<P>
+<A NAME="IDX235"></A>
+<A NAME="IDX236"></A>
+By default, the Derby Network Server will only listen on the
+<TT><I>localhost</I></TT>. Clients must use the
+<TT><I>localhost</I></TT> host name to connect. By default,
+clients cannot access the Network Server from another host. To enable
+connections from other hosts, you can set the
+<TT><I>derby.drda.host</I></TT> property, or you can
+start the Network Server with the <TT><I>-h</I></TT> option in the
+<TT><I>java
+org.apache.derby.drda.NetworkServerControl
+start</I></TT> command.
+<P>In the following example the server will only listen on
+<TT><I>localhost</I></TT> and clients cannot access the server from
+another host.
+<PRE><B>java org.apache.derby.drda.NetworkServerControl start</B>
+</PRE>
+<P>In the following example, the server runs on host machine
+<TT><I>myserver.mydomain.com</I></TT> and also listens for
+clients from other hosts. Clients should specify the server in the URL
+or DataSource as
+<TT><I>myserver.mydomain.com</I></TT>:
+<PRE><B>java org.apache.derby.drda.NetworkServerControl start -h myserver.mydomain.com</B>
+</PRE>
+<P>To start the Network Server so that it will listen on all interfaces, start
+with an IP address of <TT><I>0.0.0.0</I></TT>, as
+follows: 
+<PRE><B>java org.apache.derby.drda.NetworkServerControl start -h 0.0.0.0</B>
+</PRE>
+<P>A server started with the
+<TT><I>0.0.0.0</I></TT> option will listen to
+client requests that originate from both <TT><I>localhost</I></TT> and
+other machines on the network.
+<P>In addition, administrative commands (for example:
+<TT><I>org.apache.derby.drda.NetworkServerControl
+shutdown</I></TT>) can only execute on the host where the server was
+started even if the server was started with the <TT><I>-h</I></TT>
+option.
+<P>
+<P>
+<P><HR>[ <A HREF="hubprnt28.html">Previous Page</A><br><A HREF="hubprnt30.html">Next Page</A><br><A HREF="hubprnt02.html#ToC">Table of Contents</A><br><A HREF="hubprnt65.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt30.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt30.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,81 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Running the Network Server Under the Security Manager</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="running under security manager, Network Server">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Fri, 16 Jul 2004 10:56:44">
+<META HTTP-EQUIV="review" CONTENT="Sat, 16 Jul 2005 10:56:44">
+<META HTTP-EQUIV="expires" CONTENT="Sun, 16 Jul 2006 10:56:44">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-NET-SERV-RUN">Running the Network Server Under the Security Manager</H1>
+<A NAME="IDX237"></A>
+<P>
+<P>You should run the Network Server under the Java security manager.
+An example security policy file appears below. Please fine tune this
+policy to suit your needs. Keep in mind that opening up the server to
+all clients without limiting access via the policy listed below is a severe
+security risk.
+<PRE><B>//Recommended set of permissions to start and use the network server,
+//assuming the 'd:/derby/lib' directory has been secured.&nbsp;
+//Fine tune based on your environment settings
+grant codeBase "file:d:/derby/lib/-" {
+permission java.io.FilePermission "${derby.system.home}${/}-",&nbsp;
+	"read, write, delete";
+permission java.io.FilePermission "${user.dir}${/}-", "read, write, delete";
+permission java.util.PropertyPermission "derby.*", "read";
+permission java.util.PropertyPermission "user.dir", "read";
+permission java.lang.RuntimePermission "createClassLoader";
+permission java.net.SocketPermission "myclientmachine.mydomain.com", "accept";
+};
+&nbsp;
+//Required set of permissions to stop the network server, assuming you have
+// secured the 'd:/derby/lib' directory
+//Remember to fine tune this as per your environment.
+grant codeBase "file:d:/derby/lib/-"  {
+//Following is required when server is started with "-h localhost"&nbsp;
+//or without the -h option
+permission java.net.SocketPermission "localhost", "accept, connect, resolve";&nbsp;
+permission java.net.SocketPermission "127.0.0.1", "accept, connect, resolve";
+//The following is only required if the server is started with the -h &lt;host&gt;&nbsp;
+//option (else shutdown access will be denied).
+permission java.net.SocketPermission "&lt;host&gt;:*", "accept, connect, resolve";
+};</B>
+</PRE>
+<P>The following example shows how to start the network server in the default
+security manager (listening to clients from <TT><I>localhost</I></TT>
+only, which is the default behavior if the <TT><I>-h</I></TT> option is
+not used to start the server), assuming the policy file exists in
+<I>d:/nwsvr.policy</I>:
+<PRE><B>java -Djava.security.manager -Djava.security.policy=d:/nwsvr.policy
+org.apache.derby.drda.NetworkServerControl start&nbsp;</B>
+</PRE>
+<P>You can also achieve the same behavior with the following example, which
+makes explicit use of the <TT><I>-h</I></TT> option when starting the
+server:
+<PRE><B>java -Djava.security.manager -Djava.security.policy=d:/nwsvr.policy
+org.apache.derby.drda.NetworkServerControl start -h localhost</B>
+</PRE>
+<P>The following example shows how to start the network server (assuming you
+start the server on the host machine
+<TT><I>myserver.mydomain.com</I></TT>) in the default
+security manager (listening to client requests originating from other machines
+only). This example also assumes that the policy file exists in
+<I>d:/nwsvr.policy</I>:
+<PRE><B>java -Djava.security.manager -Djava.security.policy=d:/nwsvr.policy
+org.apache.derby.drda.NetworkServerControl start -h myserver.mydomain.com</B>
+</PRE>
+<P><HR>[ <A HREF="hubprnt29.html">Previous Page</A><br><A HREF="hubprnt31.html">Next Page</A><br><A HREF="hubprnt02.html#ToC">Table of Contents</A><br><A HREF="hubprnt65.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt31.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt31.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,67 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Configuring the network server</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="derby.drda.minthreads">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Fri, 16 Jul 2004 10:56:44">
+<META HTTP-EQUIV="review" CONTENT="Sat, 16 Jul 2005 10:56:44">
+<META HTTP-EQUIV="expires" CONTENT="Sun, 16 Jul 2006 10:56:44">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-ADV-CONFIGURINGTHENETWORKSERVER">Configuring the network server</H1>
+<P>The network server can be configured to use a specific number of threads to
+handle connections.
+<P>
+<A NAME="IDX238"></A>
+The minimum number of threads is the number of threads that are started when
+the network server is booted. This is specified as a property,
+<I>derby.drda.minThreads = &lt;min&gt;</I>.
+<P>The maximum number of threads is the maximum number of threads that will be
+used for connections. If more connections are active than are threads
+available, connections must wait until the next thread becomes
+available. Threads can become available after a specified time.
+The time is checked only when the thread has finished processing a
+communication.
+<P>You can change the maximum number of threads by using the following
+command:
+<PRE>java org.apache.derby.drda.NetworkServerControl maxthreads &lt;<I>max</I>&gt; [-h &lt;<I>host</I>&gt;]&nbsp;
+[-p &lt;<I>portnumber</I>&gt;]&nbsp;
+</PRE>
+<P>You can also set the <TT>derby.drda.maxThreads</TT>
+property to assign this value.
+<P>A &lt;max&gt; value of 0 means that there is no maximum and a new thread
+will be generated for a connection if there are no current threads
+available. This is the default.
+<P>&lt;max&gt; and &lt;min&gt; are stored as integers so the theoretical
+maximum is 2147483647 (maximum integer). The practical maximum is
+determined by the machine configuration.
+<P>To change the time that a connection thread should work on one
+session's request to see whether there are waiting sessions, use the
+following command:
+<PRE>java org.apache.derby.drda.NetworkServerControl timeslice &lt;<I>milliseconds</I>&gt; [-h &lt;<I>host</I>&gt;]&nbsp;
+[-p &lt;<I>portnumber</I>&gt;]&nbsp;
+</PRE>
+<P>You can also set the <TT>derby.drda.timeSlice</TT>
+property to set this value.
+<P>A value of 0 milliseconds indicates that the thread will not give up
+working on the session until the session ends.
+<P>A value of -1 milliseconds indicates to use the default. The default
+value is 0.
+<P>The maximum number of milliseconds that can be specified is 2147483647
+(maximum integer).
+<P>The Network Server configuration can also be changed using the servlet
+interface.
+<P><HR>[ <A HREF="hubprnt30.html">Previous Page</A><br><A HREF="hubprnt32.html">Next Page</A><br><A HREF="hubprnt02.html#ToC">Table of Contents</A><br><A HREF="hubprnt65.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt32.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt32.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,51 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Log File</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="derby.infolog.append, derby.drda.logConnections, and the Network Server, derby.log">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Fri, 16 Jul 2004 10:56:44">
+<META HTTP-EQUIV="review" CONTENT="Sat, 16 Jul 2005 10:56:44">
+<META HTTP-EQUIV="expires" CONTENT="Sun, 16 Jul 2006 10:56:44">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-ADV-LOGFILE">Log File</H1>
+<P>
+<A NAME="IDX239"></A>
+<A NAME="IDX240"></A>
+<A NAME="IDX241"></A>
+The Network Server uses the Derby <I>derby.log</I> file
+for logging problems it encounters. It also logs connections and
+disconnections when the property
+<TT><I>derby.drda.logConnections</I></TT> is set to
+true. The <TT><I>derby.log </I></TT>file is created
+when the Derby server is booted. The network server records the
+time and version. If a log file exists, it is overwritten, unless the
+property <TT><I>derby.infolog.append</I></TT> is set
+to true. See the <CITE>Derby Developer's Guide</CITE> for
+more information about <TT><I>derby.log</I></TT>.
+<P>You can also turn on connection and disconnection logging using the
+following command, (or through the servlet interface):
+<PRE><B>java org.apache.derby.drda.NetworkServerControl logconnections on&nbsp;
+[-h &lt;host&gt;] [-p &lt;portnumber&gt;]&nbsp;</B>
+</PRE>
+<P>Turn connection logging off with the following command, (or through the
+servlet interface):
+<PRE><B>java org.apache.derby.drda.NetworkServerControl logconnections off&nbsp;
+[-h &lt;host&gt;][-p &lt;portnumber&gt;]&nbsp;</B>
+</PRE>
+<P>See the DB2 UDB documentation for information about the Universal
+Driver's error reporting.
+<P><HR>[ <A HREF="hubprnt31.html">Previous Page</A><br><A HREF="hubprnt33.html">Next Page</A><br><A HREF="hubprnt02.html#ToC">Table of Contents</A><br><A HREF="hubprnt65.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt33.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt33.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,61 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Trace Facility</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="trace facility, Network Server, for the Network Server, Trace facility">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Fri, 16 Jul 2004 10:56:44">
+<META HTTP-EQUIV="review" CONTENT="Sat, 16 Jul 2005 10:56:44">
+<META HTTP-EQUIV="expires" CONTENT="Sun, 16 Jul 2006 10:56:44">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-ADV-TRACEFACILITY">Trace Facility</H1>
+<A NAME="IDX242"></A>
+<A NAME="IDX243"></A>
+<P>You will use the trace facility only if you are working with technical
+support and they require the additional information provided in this
+file.
+<P>See <A HREF="hubprnt26.html#HDRSII-SERVLET-98430">Managing the Derby Network Server Remotely</A> for information about managing the trace facility using the
+servlet interface.
+<P><H1><A NAME="HDRADV804410">Turning On the Trace Facility</A></H1>
+<P>Turn on tracing for all sessions by specifying the property:
+<P><I>derby.drda.traceAll=true </I>
+<P>While the network server is running, you can use the following command to
+turn on the trace facility:
+<PRE><B>java org.apache.derby.drda.NetworkServerControl trace on [&lt;<I>connection number</I>&gt;]&nbsp;
+[-h &lt;<I>host</I>&gt;][-p &lt;<I>portnumber</I>&gt;]&nbsp;</B>
+</PRE>
+<P>If the &lt;<I>connection number</I>&gt; is specified tracing is turned
+on only for that connection.
+<P>Specify the location of the tracing files by specifying the property:
+<P><I>derby.drda.traceDirectory=&lt;directory for tracing
+files&gt; </I>
+<DL><DT><B>Note:</B></DT><DD>Specify the directory where the tracing files will reside. The file
+name itself is defined by the system.
+</DD></DL>
+<P>If the trace directory is not specified, the traces are placed in
+<I>derby.system.home</I>.
+<P>While the network server is running, using the following command to set the
+trace directory:
+<PRE><B>java org.apache.derby.drda.NetworkServerControl traceDirectory&nbsp;
+&lt;<I>directory for tracing files</I>&gt;[-h &lt;<I>host</I>&gt;] [-p &lt;<I>portnumber</I>&gt;] &nbsp;</B>
+</PRE>
+<P><H1><A NAME="HDRADV804451">Turning Off the Trace Facility</A></H1>
+<P>Tracing can be turned off with the following command:
+<PRE><B>java org.apache.derby.drda.NetworkServerControl trace off [&lt;<I>connection number</I>&gt;]&nbsp;
+[-h &lt;<I>host</I>&gt;] [-p &lt;<I>portnumber</I>&gt;]&nbsp;</B>
+</PRE>
+<P>The tracing files are named <I>Server.trace</I>
+<P><HR>[ <A HREF="hubprnt32.html">Previous Page</A><br><A HREF="hubprnt34.html">Next Page</A><br><A HREF="hubprnt02.html#ToC">Table of Contents</A><br><A HREF="hubprnt65.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt34.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt34.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,33 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Derby Network Server Sample Programs</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="Sample programs for Network Server">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Fri, 16 Jul 2004 10:56:44">
+<META HTTP-EQUIV="review" CONTENT="Sat, 16 Jul 2005 10:56:44">
+<META HTTP-EQUIV="expires" CONTENT="Sun, 16 Jul 2006 10:56:44">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<HR><H1 NAME="HDRSII-SAMPLE-PROGRAMS">Derby Network Server Sample Programs</H1>
+<A NAME="IDX244"></A>
+<P>
+<P>This chapter describes the following Derby Network Server sample
+programs for Network Server users:
+<UL>
+<LI><A HREF="hubprnt35.html#HDRSII-OVERVIEW-NSSAMPLE">The NsSample sample program</A>
+</LI><LI><A HREF="hubprnt36.html#HDRSII-OVERVIEW-NET-SERV-SAMPLE">Network Server sample programs for embedded and client connections</A>
+</LI></UL>
+<P><HR>[ <A HREF="hubprnt33.html">Previous Page</A><br><A HREF="hubprnt35.html">Next Page</A><br><A HREF="hubprnt02.html#ToC">Table of Contents</A><br><A HREF="hubprnt65.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt35.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt35.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,187 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>The NsSample sample program</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="NsSample sample program, Network Server">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Fri, 16 Jul 2004 10:56:44">
+<META HTTP-EQUIV="review" CONTENT="Sat, 16 Jul 2005 10:56:44">
+<META HTTP-EQUIV="expires" CONTENT="Sun, 16 Jul 2006 10:56:44">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-OVERVIEW-NSSAMPLE">The NsSample sample program</H1>
+<A NAME="IDX245"></A>
+<P>
+<P>The <I>NsSample</I> program is a simple JDBC application that interacts
+with the Network Server.
+<P>This topic includes the following sections:
+<UL>
+<LI><A HREF="#HDROVERVIEW-NS-DEMO">Overview of the NsSample sample program</A>
+</LI><LI><A HREF="#HDROVERVIEW-NS-RUN-DEMO">Running the NsSample sample program</A>
+</LI></UL>
+<P><H1><A NAME="HDROVERVIEW-NS-DEMO">Overview of the NsSample sample program</A></H1>
+<P>The <I>NsSample</I> program performs the following tasks:
+<UL>
+<LI>starts the Network Server.
+</LI><LI>checks that the Network Server is running.
+</LI><LI>loads the DB2 JDBC Universal driver.
+</LI><LI>creates the <I>NsSampledb</I> database if not already created.
+</LI><LI>checks to see if the schema is already created, and if not, creates the
+schema which includes the SAMPLETBL table and corresponding indexes.
+</LI><LI>connects to the database.
+</LI><LI>loads the schema by inserting data.
+</LI><LI>starts client threads to perform database related operations.
+</LI><LI>has each of the clients perform DML operations (select, insert, delete,
+update) using JDBC calls. For example, one client thread establishes an
+embedded connection to perform database operations, while another client
+thread establishes a client connection to the Network Server to perform
+database operations.
+</LI><LI>waits for the client threads to finish the tasks.
+</LI><LI>shuts down the Network Server at the end of the demonstration.
+</LI></UL>
+<P>The following files should be installed in the
+<TT>%DERBY_INSTALL%\demo\programs\nserverdemo\</TT> directory in order
+to run the sample program:
+<UL>
+<LI><I>NsSample.java</I>
+<P>This is the entry point into the sample program. The program starts
+up two client threads. The first client establishes an embedded
+connection to perform database operations, while the second client establishes
+a client connection to the Network Server to perform database
+operations.
+<P>You can change the following constants to modify the sample program:
+<UL>
+<LI>NUM_ROWS - The number of rows that must be initially loaded into the
+schema.
+</LI><LI>ITERATIONS - The number of iterations for which each client thread does
+database related work.
+</LI><LI>NUM_CLIENT_THREADS - The number of clients that you want to run the
+program against.
+</LI><LI>NETWORKSERVER_PORT - The port on which the network server is
+running.
+</LI></UL>
+</LI><LI><I>NsSampleClientThread.java</I>
+<P>This file contains two Java classes: 
+<UL>
+<LI>The NsSampleClientThread class extends Thread and instantiates a
+NsSampleWork instance.
+</LI><LI>The NsSampleWork class contains everything required to perform DML
+operations using JDBC calls. The <I>doWork</I> method in the
+NsSampleWork class represents all the work done as part of this sample
+program.
+</LI></UL>
+</LI><LI><I>NetworkServerUtil.java</I> 
+<P>This file contains helper methods to start the Network Server and to
+shutdown the server.
+</LI><LI>Compiled class files:
+<UL>
+<LI><I>NsSample.class</I>
+</LI><LI><I>NsSampleClientThread.class</I>
+</LI><LI><I>NsSampleWork.class</I>
+</LI><LI><I>NetworkServerUtil.class</I>
+</LI></UL>
+</LI></UL>
+<P><H1><A NAME="HDROVERVIEW-NS-RUN-DEMO">Running the NsSample sample program</A></H1>
+<P>To run the <I>NsSample</I> program: 
+<OL TYPE=1>
+<LI>Open a command prompt and change directories to the
+<I>%DERBY_INSTALL%\demo\programs\</I> directory, where
+<I>%DERBY_INSTALL%</I> is the directory where you installed
+Derby.
+</LI><LI>Set the CLASSPATH to the current directory (&quot;.&quot;) and also
+include the following jar files in order to use the Network Server and the DB2
+JDBC Universal Driver. 
+<UL>
+<LI><I>derbynet.jar</I>
+<P>The Network Server jar file. It must be in your CLASSPATH to use any
+of the Network Server functions.
+</LI><LI><I>db2jcc.jar</I> 
+<P>This jar file must be in your CLASSPATH to use the DB2 JDBC Universal
+Driver.
+</LI><LI><I>db2jcc_license_c.jar</I> 
+<P>This jar file is the license file for the Universal Driver.
+</LI><LI><I>derby.jar</I>
+<P>The Derby database engine jar file.
+</LI></UL>
+</LI><LI>
+<P>Test the CLASSPATH settings by running the following Java command:
+<PRE> java org.apache.derby.tools.sysinfo
+</PRE>
+<P>This command will show the Derby jar files that are in the CLASSPATH
+as well as the DB2 JDBC Universal Driver along with their respective
+versions.
+</LI><LI>
+<P>After you have set up your environment correctly, execute the application
+from the same directory:
+<PRE>java  nserverdemo.NsSample
+ 
+</PRE>
+</LI></OL>
+<P>You should receive output similar to the following if the program runs
+successfully:
+<PRE>Derby Network Server created
+Server is ready to accept connections on port 1621.
+Connection number: 1.
+[NsSample] Derby Network Server started.
+[NsSample] Sample Derby Network Server program demo starting.
+Please wait .....................
+Connection number: 2.
+[NsSampleWork] Begin creating table - SAMPLETBL and necessary indexes.
+[NsSampleClientThread] Thread id - 1; started.
+[NsSampleWork] Thread id - 1; requests database connection,&nbsp;
+	dbUrl =jdbc:derby:NSSampledb;
+[NsSampleClientThread] Thread id - 2; started.
+[NsSampleWork] Thread id - 2; requests database connection,&nbsp;
+	dbUrl =jdbc:derby:net://localhost:1621/
+	NSSampledb;create=true:retrieveMessagesFromServerOnGetMessage=true;
+	deferPrepares=true;
+Connection number: 3.
+[NsSampleWork] Thread id - 1 selected 1 row [313,Derby36   ,1.7686243E23,9620]
+[NsSampleWork] Thread id - 1 selected 1 row [313,Derby36   ,1.7686243E23,9620]
+[NsSampleWork] Thread id - 1; deleted 1 row with t_key = 9620
+[NsSampleWork] Thread id - 1 selected 1 row [700,Derby34   ,8.7620301E9,9547]
+[NsSampleWork] Thread id - 1 selected 1 row [700,Derby34   ,8.7620301E9,9547]
+[NsSampleWork] Thread id - 2 selected 1 row [700,Derby34   ,8.7620301E9,9547]
+[NsSampleWork] Thread id - 2 selected 1 row [700,Derby34   ,8.7620301E9,9547]
+[NsSampleWork] Thread id - 1; inserted 1 row.
+[NsSampleWork] Thread id - 1 selected 1 row [52,Derby34   ,8.7620301E9,9547]
+[NsSampleWork] Thread id - 2; updated 1 row with t_key = 9547
+[NsSampleWork] Thread id - 1; deleted 1 row with t_key = 9547
+[NsSampleWork] Thread id - 2 selected 1 row [617,Derby31   ,773.83636,9321]
+[NsSampleWork] Thread id - 2 selected 1 row [617,Derby31   ,773.83636,9321]
+[NsSampleWork] Thread id - 2 selected 1 row [617,Derby31   ,773.83636,9321]
+[NsSampleWork] Thread id - 2 selected 1 row [617,Derby31   ,773.83636,9321]
+[NsSampleWork] Thread id - 1; inserted 1 row.
+[NsSampleWork] Thread id - 2; deleted 1 row with t_key = 9321
+[NsSampleWork] Thread id - 1; deleted 1 row with t_key = 8707
+[NsSampleWork] Thread id - 1; closed connection to the database.
+[NsSampleClientThread] Thread id - 1; finished all tasks.
+[NsSampleWork] Thread id - 2; deleted 1 row with t_key = 8490
+[NsSampleWork] Thread id - 2; closed connection to the database.
+[NsSampleClientThread] Thread id - 2; finished all tasks.
+[NsSample] Shutting down network server.
+Connection number: 4.
+Shutdown successful.
+ 
+</PRE>
+<P>Running the <I>NsSample</I> program will also create the following new
+directories and files:
+<UL>
+<LI><I>NSSampledb</I>
+<P>This directory makes up the <I>NSSampledb</I> database.
+</LI><LI><I>derby.log</I>
+<P>This log file contains Derby progress and error messages.
+</LI></UL>
+<P><HR>[ <A HREF="hubprnt34.html">Previous Page</A><br><A HREF="hubprnt36.html">Next Page</A><br><A HREF="hubprnt02.html#ToC">Table of Contents</A><br><A HREF="hubprnt65.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt36.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt36.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,184 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Network Server sample programs for embedded and client connections</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="sample programs for embedded and client connections, Network Server, SimpleNetworkServerSample program, SimpleNetworkClientSample program">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Fri, 16 Jul 2004 10:56:44">
+<META HTTP-EQUIV="review" CONTENT="Sat, 16 Jul 2005 10:56:44">
+<META HTTP-EQUIV="expires" CONTENT="Sun, 16 Jul 2006 10:56:44">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-OVERVIEW-NET-SERV-SAMPLE">Network Server sample programs for embedded and client connections</H1>
+<A NAME="IDX246"></A>
+<P>
+<P>This Derby Network Server sample program demonstrates how to obtain an
+embedded connection and client connections to the same database using the
+Network Server. This program shows how to use either the DriverManager
+or a DataSource to obtain client connections.
+<P>For a database to be consistent, only one JVM can access it at a
+time. The embedded driver is loaded when the Network Server is
+started. The JVM that starts the Network Server can get an embedded
+connection to the same database that the Network Server is accessing to serve
+clients from other JVMs. This solution allows you to take advantage of
+the performance benefits of the embedded driver while also allowing client
+connections from other JVMs to connect to the same database.
+<P>This topic contains the following sections:
+<UL>
+<LI><A HREF="#HDRSII-OVERVIEW-SERV-SAMP-PRGM">The SimpleNetworkServerSample Program</A>
+</LI><LI><A HREF="#HDRSII-OVERVIEW-RUN-SERV-PRGM">Running the SimpleNetworkServerSample Program</A>
+</LI><LI><A HREF="#HDRSII-OVERVIEW-CLIENT-CONNECT">Connecting a Client to the Network Server with the SimpleNetworkClientSample program</A>
+</LI><LI><A HREF="#HDRSII-OVERVIEW-CLIENT-RUN">Running the SimpleNetworkClientSample Program</A>
+</LI></UL>
+<P><H1><A NAME="HDRSII-OVERVIEW-SERV-SAMP-PRGM">The SimpleNetworkServerSample Program</A></H1>
+<A NAME="IDX247"></A>
+<P>
+<P>The <I>SimpleNetworkServerSample</I> program starts the Derby
+Network Server as well as the embedded driver and waits for clients to
+connect. The program performs the following tasks.
+<UL>
+<LI>starts the Derby Network Server using a property and also loads the
+embedded driver
+</LI><LI>checks if the Network Server is up and running
+</LI><LI>creates the database <I>NSSimpleDB</I> if it is not already created
+</LI><LI>obtains an embedded database connection
+</LI><LI>tests the database connection by executing a sample query.
+</LI><LI>allows client connections to connect to the server until you decide to
+stop the server and exit the program
+</LI><LI>closes the connection
+</LI><LI>shuts down the Network Server before exiting the program.
+</LI></UL>
+<P>To run the sample program, the following files should be installed in the
+<TT>%DERBY_INSTALL%\demo\programs\nserverdemo\</TT> directory:
+<UL>
+<LI>The source file: <I>SimpleNetworkServerSample.java</I>
+</LI><LI>The compiled class file:
+<I>SimpleNetworkServerSample.class</I>
+</LI></UL>
+<P><H1><A NAME="HDRSII-OVERVIEW-RUN-SERV-PRGM">Running the SimpleNetworkServerSample Program</A></H1>
+<P>To run the Derby Network Server sample program:
+<OL TYPE=1>
+<LI>Open a command prompt and change directories to the
+<TT>%DERBY_INSTALL%\demo\programs\nserverdemo</TT> directory, where
+<TT>%DERBY_INSTALL%</TT> is the directory where you installed
+Derby.
+</LI><LI>Set the CLASSPATH to include the following jar files in order to run this
+program:
+<UL>
+<LI>the current directory (&quot;.&quot;)
+</LI><LI><I>derbynet.jar</I> 
+<P>The Network Server jar file. It must be in your CLASSPATH because we
+start the Network Server in this program.
+</LI><LI><I>derby.jar</I> 
+<P>The database engine jar file.
+</LI></UL>
+</LI><LI>Test the CLASSPATH settings by running the following Java command: 
+<PRE>java org.apache.derby.tools.sysinfo
+</PRE>
+<P>This command will show the Derby jar files that are in the
+CLASSPATH.
+</LI><LI>Once you have set up your environment correctly, execute the application
+from the same directory: 
+<PRE>java SimpleNetworkServerSample
+</PRE>
+</LI></OL>
+<P>You should receive output similar to the following if the program runs
+successfully:
+<PRE>Starting Network Server
+Testing if Network Server is up and running!
+Derby Network Server now running
+Got an embedded connection.
+Testing embedded connection by executing a sample query
+number of rows in sys.systables = 16
+While my app is busy with embedded work, ij might connect like this:
+ 
+        $ java -Dij.user=me -Dij.password=pw -Dij.protocol=
+			jdbc:derby:net:\\localhost:1527\ org.apache.derby.tools.ij
+        ij&gt; connect 'NSSimpleDB:retrieveMessagesFromServerOnGetMessage=true;';
+Watch that punctuation.  Put a ':' before the jcc
+attributes and a ';' after each one (even the last).
+ 
+ 
+Clients can continue to connect:
+Press [Enter] to stop Server
+</PRE>
+<P>Running the <I>SimpleNetworkServerSample</I> program will also create
+the following new directories and files: 
+<UL>
+<LI><I>NSSimpleDB</I>
+<P>This directory makes up the <I>NSSimpleDB</I> database.
+</LI><LI><I>derby.log</I> 
+<P>This log file contains Derby progress and error messages.
+</LI></UL>
+<P><H1><A NAME="HDRSII-OVERVIEW-CLIENT-CONNECT">Connecting a Client to the Network Server with the SimpleNetworkClientSample program</A></H1>
+<A NAME="IDX248"></A>
+<P>
+<P>The <I>SimpleNetworkClientSample</I> program is a client program that
+interacts with the Derby Network Server from another JVM. The
+program performs the following tasks.
+<UL>
+<LI>loads the DB2 Universal JDBC Driver
+</LI><LI>obtains a client connection using the DriverManager
+</LI><LI>obtains a client connection using a DataSource
+</LI><LI>tests the database connections by executing a sample query
+</LI><LI>closes the connections and then exits the program.
+</LI></UL>
+<P>The following files should be installed in the
+<TT>%DERBY_INSTALL%\demo\programs\nserverdemo\</TT> directory in order
+to run the sample program:
+<UL>
+<LI>The source file: <I>SimpleNetworkClientSample.java</I>
+</LI><LI>The compiled class file:
+<I>SimpleNetworkClientSample.class</I>
+</LI></UL>
+<P><H1><A NAME="HDRSII-OVERVIEW-CLIENT-RUN">Running the SimpleNetworkClientSample Program</A></H1>
+<P>To connect to the Network Server that has been started as part of the
+SimpleNetworkServerSample program:
+<OL TYPE=1>
+<LI>Open a command prompt and change directories to the
+<TT>%DERBY_INSTALL%\demo\programs\nserverdemo</TT> directory, where
+<TT>%DERBY_INSTALL%</TT> is the directory where you installed
+Derby.
+</LI><LI>Network Server clients need only the following jar files in the CLASSPATH
+to connect to the Network Server. Set the CLASSPATH to include the
+following jar files:
+<UL>
+<LI>the current directory (&quot;.&quot;)
+</LI><LI><I>db2jcc.jar</I> 
+<P>This jar file must be in your CLASSPATH to use the DB2 JDBC Universal
+Driver.
+</LI><LI><I>db2jcc_license_c.jar</I>
+<P>This jar file is the license file for the Universal Driver for
+Derby.
+</LI></UL>
+</LI><LI>Once you have set up your environment correctly, execute the application
+from the same directory:
+<PRE>java SimpleNetworkClientSample
+</PRE>
+</LI></OL>
+<P>You should receive output similar to the following if the program runs
+successfully:
+<PRE>Starting Sample client program
+Got a client connection via the DriverManager.
+connection from datasource; getDriverName =&nbsp;
+	IBM DB2 JDBC Universal Driver Architecture
+Got a client connection via a DataSource.
+Testing the connection obtained via DriverManager by executing a sample query
+number of rows in sys.systables = 16
+Testing the connection obtained via a DataSource by executing a sample query
+number of rows in sys.systables = 16
+Goodbye!
+</PRE>
+<P><HR>[ <A HREF="hubprnt35.html">Previous Page</A><br><A HREF="hubprnt37.html">Next Page</A><br><A HREF="hubprnt02.html#ToC">Table of Contents</A><br><A HREF="hubprnt65.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt37.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt37.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,32 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Derby Administration Guide</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Fri, 16 Jul 2004 10:56:44">
+<META HTTP-EQUIV="review" CONTENT="Sat, 16 Jul 2005 10:56:44">
+<META HTTP-EQUIV="expires" CONTENT="Sun, 16 Jul 2006 10:56:44">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<HR><H1 NAME="HDRPARTTWO1008128">Derby Administration Guide</H1>
+<P>This part of the guide is divided into the following sections:
+<UL>
+<LI><A HREF="hubprnt38.html#HDRSII-CONSIST-54401">Checking Database Consistency</A>
+</LI><LI><A HREF="hubprnt42.html#HDRSII-BUBBKUP-98797">Backing Up and Restoring Databases</A>
+</LI><LI><A HREF="hubprnt51.html#HDRSII-LOG-98797">Logging on a Separate Device</A>
+</LI><LI><A HREF="hubprnt56.html#HDRSII-LOCKVTI-42553">Getting Locking Information</A>
+</LI><LI><A HREF="hubprnt59.html#HDRSII-SPACE-73511">Identifying and Reclaiming Unused Space</A>
+</LI></UL>
+<P><HR>[ <A HREF="hubprnt36.html">Previous Page</A><br><A HREF="hubprnt38.html">Next Page</A><br><A HREF="hubprnt02.html#ToC">Table of Contents</A><br><A HREF="hubprnt65.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt38.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt38.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,39 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Checking Database Consistency</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="checking database, Consistency">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Fri, 16 Jul 2004 10:56:44">
+<META HTTP-EQUIV="review" CONTENT="Sat, 16 Jul 2005 10:56:44">
+<META HTTP-EQUIV="expires" CONTENT="Sun, 16 Jul 2006 10:56:44">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<HR><H1 NAME="HDRSII-CONSIST-54401">Checking Database Consistency</H1>
+<P>
+<A NAME="IDX249"></A>
+Derby is a robust product containing many safeguards to ensure that the
+database remains consistent.
+<P>If, however, you have experienced hardware or operating system failure and
+you want to verify that the database is still consistent, Derby provides
+a way to do this. Check consistency only if there are indications that
+such a check is needed, because a consistency check can take a long time on a
+large database.
+<UL>
+<LI><A HREF="hubprnt39.html#HDRSII-CONSIST-30301">The SYSCS_CHECK_TABLE function</A>
+</LI><LI><A HREF="hubprnt40.html#HDRSII-CONSIST-38781">Sample Error Messages</A>
+</LI><LI><A HREF="hubprnt41.html#HDRSII-CONSIST-24642">Sample Queries</A>
+</LI></UL>
+<P><HR>[ <A HREF="hubprnt37.html">Previous Page</A><br><A HREF="hubprnt39.html">Next Page</A><br><A HREF="hubprnt02.html#ToC">Table of Contents</A><br><A HREF="hubprnt65.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt39.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt39.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,62 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>The SYSCS_CHECK_TABLE function</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="org.apache.derby.database. ConsistencyChecker.checkTable">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Fri, 16 Jul 2004 10:56:44">
+<META HTTP-EQUIV="review" CONTENT="Sat, 16 Jul 2005 10:56:44">
+<META HTTP-EQUIV="expires" CONTENT="Sun, 16 Jul 2006 10:56:44">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-CONSIST-30301">The SYSCS_CHECK_TABLE function</H1>
+<P>
+<A NAME="IDX250"></A>
+The <I>SYSCS_UTIL.SYSCS_CHECK_TABLE()</I> checks the consistency of
+a Derby table. You run this function in an SQL statement, as
+follows:
+<PRE>VALUES SYSCS_UTIL.SYSCS_CHECK_TABLE(
+    SchemaName, TableName)
+</PRE>
+<P><I>SYSCS_CHECK_TABLE</I> returns a smallint. If the table is
+consistent (or if <TT><I>SYSCS_CHECK_TABLE</I></TT> is run on a view),
+<TT><I>SYSCS_CHECK_TABLE </I></TT> returns a non-zero value.
+Otherwise, <TT><I>SYSCS_CHECK_TABLE</I></TT> throws an exception on the
+first inconsistency it finds.
+<P><I>SYSCS_UTIL.SYSCS_CHECK_TABLE</I> verifies the
+following:
+<UL>
+<LI>Base tables are internally consistent.
+</LI><LI>Base tables and all associated indexes contain the same number of
+rows.
+</LI><LI>The values and row locations in each index match those of the base
+table.
+</LI><LI>All BTREE indexes are internally consistent.
+</LI></UL>
+<DL><DT><B>Note:</B></DT><DD>Both <I>SchemaName</I> and <I>TableName</I> must be any expression
+that evaluates to a string data type. If you created a schema or table
+name as a non-delimited identifier, you must present their names in all upper
+case. For example:
+</DD></DL>
+<PRE><B>VALUES SYSCS_UTIL.SYSCS_CHECK_TABLE('APP', 'CITIES')</B>
+</PRE>
+<P>For a consistent table, the following result is displayed:
+<PRE>1
+-----
+1
+ 
+1 row selected
+</PRE>
+<P><HR>[ <A HREF="hubprnt38.html">Previous Page</A><br><A HREF="hubprnt40.html">Next Page</A><br><A HREF="hubprnt02.html#ToC">Table of Contents</A><br><A HREF="hubprnt65.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt40.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt40.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,45 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Sample Error Messages</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Fri, 16 Jul 2004 10:56:44">
+<META HTTP-EQUIV="review" CONTENT="Sat, 16 Jul 2005 10:56:44">
+<META HTTP-EQUIV="expires" CONTENT="Sun, 16 Jul 2006 10:56:44">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-CONSIST-38781">Sample Error Messages</H1>
+<P>This section provides examples of error messages that
+<I>SYSCS_UTIL.SYSCS_CHECK_TABLE() </I> can return.
+<P>The row counts of the base table and an index differ:
+<PRE>ERROR X0Y55: The number of rows in the base table does not match&nbsp;
+the number of rows in at least 1 of the indexes on the table. Index&nbsp;
+'T1_I' on table 'APP.T1' has 4 rows, but the base table has 5 rows.&nbsp;
+The suggested corrective action is to recreate the index.
+</PRE>
+<P>The index refers to a row that does not exist in the base table:
+<PRE>ERROR X0X62: Inconsistency found between table 'APP.T1' and index
+'T1_I'. Error when trying to retrieve row location '(1,6)' from the&nbsp;
+table. The full index key,including the row location, is '{ 1, (1,6) }'.
+The suggested corrective action is to recreate the index.
+</PRE>
+<P>A key column value differs between the base table and the index:
+<PRE>ERROR X0X61: The values for column 'C10' in index 'T1_C10' and&nbsp;
+table 'APP.T1' do not match for row location (1,7). The value in the&nbsp;
+index is '2 2   ', while the value in the base table is 'NULL'. The full
+index key, including the row location, is '{ 2 2       , (1,7) }'. The&nbsp;
+suggested corrective action is to recreate the index.
+</PRE>
+<P><HR>[ <A HREF="hubprnt39.html">Previous Page</A><br><A HREF="hubprnt41.html">Next Page</A><br><A HREF="hubprnt02.html#ToC">Table of Contents</A><br><A HREF="hubprnt65.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt41.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt41.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,43 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Sample Queries</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Fri, 16 Jul 2004 10:56:44">
+<META HTTP-EQUIV="review" CONTENT="Sat, 16 Jul 2005 10:56:44">
+<META HTTP-EQUIV="expires" CONTENT="Sun, 16 Jul 2006 10:56:44">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-CONSIST-24642">Sample Queries</H1>
+<P>This section provides examples that illustrate using
+<I>SYSCS_UTIL.SYSCS_CHECK_TABLE() </I> in queries.
+<P>Check the consistency of a single table:
+<PRE><B>VALUES SYSCS_UTIL.SYSCS_CHECK_TABLE('APP', 'FLIGHTS')</B>
+</PRE>
+<P>Check the consistency of all of the tables in a schema, stopping at the
+first failure:
+<PRE><B>SELECT tablename, SYSCS_UTIL.SYSCS_CHECK_TABLE(
+    'SAMP', tablename)
+FROM sys.sysschemas s, sys.systables t
+WHERE s.schemaname = 'SAMP' AND s.schemaid = t.schemaid</B>
+</PRE>
+<P>Check the consistency of an entire database, stopping at the first
+failure:
+<PRE><B>SELECT schemaname, tablename,
+SYSCS_UTIL.SYSCS_CHECK_TABLE(schemaname, tablename)
+FROM sys.sysschemas s, sys.systables t
+WHERE s.schemaid = t.schemaid</B>
+</PRE>
+<P><HR>[ <A HREF="hubprnt40.html">Previous Page</A><br><A HREF="hubprnt42.html">Next Page</A><br><A HREF="hubprnt02.html#ToC">Table of Contents</A><br><A HREF="hubprnt65.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt42.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt42.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,30 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Backing Up and Restoring Databases</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="Backing up databases">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Fri, 16 Jul 2004 10:56:44">
+<META HTTP-EQUIV="review" CONTENT="Sat, 16 Jul 2005 10:56:44">
+<META HTTP-EQUIV="expires" CONTENT="Sun, 16 Jul 2006 10:56:44">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<HR><H1 NAME="HDRSII-BUBBKUP-98797">Backing Up and Restoring Databases</H1>
+<P>
+<A NAME="IDX251"></A>
+Derby provides a way to back up a database while it is on-line.
+While the backup is in progress, update operations are temporarily blocked but
+read operations can still proceed.
+<P><HR>[ <A HREF="hubprnt41.html">Previous Page</A><br><A HREF="hubprnt43.html">Next Page</A><br><A HREF="hubprnt02.html#ToC">Table of Contents</A><br><A HREF="hubprnt65.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt43.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt43.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,184 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Backing Up a Database</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="Backup procedure, SYSCS_UTIL.SYSCS_BACKUP_DATABASE() system procedure, SYSCS_UTIL.SYSCS_FREEZE_DATABASE system procedure, SYSCS_UTIL.SYSCS_UNFREEZE_DATABASE system procedure, backing up, Encrypted databases, of encrypted databases, Backup">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Fri, 16 Jul 2004 10:56:44">
+<META HTTP-EQUIV="review" CONTENT="Sat, 16 Jul 2005 10:56:44">
+<META HTTP-EQUIV="expires" CONTENT="Sun, 16 Jul 2006 10:56:44">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="Header_98">Backing Up a Database</H1>
+<UL>
+<LI><A HREF="#HDRSII-BUBBKUP-12677">Offline Backups</A>
+</LI><LI><A HREF="#HDRSII-BUBBKUP-63476">On-line Backups</A>
+</LI><LI><A HREF="#HDRSII-BUBBKUP-67525">When the Log is in a non-Default Location</A>
+</LI><LI><A HREF="#HDRSII-BUBBKUP-21105">Backing Up Encrypted Databases</A>
+</LI><LI><A HREF="hubprnt49.html#HDRSII-BUBBKUP-66644">Failure Recovery</A>
+</LI><LI><A HREF="hubprnt46.html#HDRROLLFORWARD">Roll-forward Recovery</A>
+</LI></UL>
+<P><H1><A NAME="HDRSII-BUBBKUP-12677">Offline Backups</A></H1>
+<P>To perform an offline backup of a database, simply use operating system
+commands to copy the database directory. The database must be shut down
+prior to performing an offline backup.
+<P>For example, on Windows NT, the following operating system command would
+back up a (closed) database named <I>sample</I> located in
+d:\mydatabases by copying it to the directory
+d:\mybackups\2004-06-01:
+<PRE><B>xcopy d:\mydatabases\sample d:\mybackups\2004-06-01\sample /s /i</B>
+</PRE>
+<P>(If you are not using Windows NT, substitute the appropriate operating
+system command for copying a directory and all contents to a new
+location.)
+<DL><DT><B>Note:</B></DT><DD>On Windows NT, do not attempt to update a database while it is being backed
+up in this way. Attempting to update a database during an off-line
+backup will generate a <I>java.io.IOException</I>.
+Using on-line backups prevent this from occurring.
+</DD></DL>
+<P>For large systems, shutting down the database might not be
+convenient. To back up a database without having to take it off line,
+system administrators should use on-line backups, described next.
+<P><H1><A NAME="HDRSII-BUBBKUP-63476">On-line Backups</A></H1>
+<P>Use online backups to back up a database while it is booted. During
+the interval the backup is running, the database can be read, but writes to
+the database are blocked.
+<P>There are two ways to perform on-line backups:
+<UL>
+<LI><A HREF="#HDRSII-BUBBKUP-94347">Using the backup procedure</A>
+</LI><LI><A HREF="#HDRSII-BUBBKUP-75469">Using Operating System Commands with the freeze and unfreeze system procedures</A>
+</LI></UL>
+<P><H1><A NAME="HDRSII-BUBBKUP-94347">Using the backup procedure</A></H1>
+<P>The <I>SYSCS_UTIL.SYSCS_BACKUP_DATABASE()</I> procedure locks
+the database and performs the copy operation.
+<P>
+<A NAME="IDX252"></A>
+<A NAME="IDX253"></A>
+<P>The <TT><I>SYSCS_UTIL.SYSCS_BACKUP_DATABASE()</I></TT>
+procedure takes a string argument representing the location in which to back
+up the database. Typically you provide the full path to the backup
+directory. (Relative paths are interpreted as relative to the current
+directory, not to the
+<TT><I>derby.system.home</I></TT> directory.)
+<P>For example, to specify a backup location of c:/mybackups/2004-06-01
+for the currently-open database, you would use the following statement:
+<PRE><B>CALL SYSCS_UTIL.SYSCS_BACKUP_DATABASE('c:/mybackups/2004-06-01')</B>
+</PRE>
+<DL><DT><B>Note:</B></DT><DD>Use forward slashes as the path separator in SQL commands.
+</DD></DL>
+<P>The <I>SYSCS_UTIL.SYSCS_BACKUP_DATABASE()</I> procedure puts the
+database into a state in which it can be safely copied, then copies the entire
+original database directory (including data files, on-line transaction log
+files, and jar files) to the specified backup directory. Files not
+within the original database directory (for example,
+<I>derby.properties</I>) are <I>not</I> copied.
+<P>Here is an example, which backs up a database to a directory with a name
+that reflects the current date:
+<PRE>public static void backUpDatabase(Connection conn)throws SQLException
+{
+String backupdirectory ="c:/mybackups/"+JCalendar.getToday();
+CallableStatement cs = conn.prepareCall("CALL SYSCS_UTIL.SYSCS_BACKUP_DATABASE(?)");&nbsp;
+cs.setString(1, backupdirectory);
+cs.execute();&nbsp;
+cs.close();
+System.out.println("backed up database to "+backupdirectory);
+}
+</PRE>
+<P>For a database backed up on 2004-06-01, the above commands copy the current
+database to a directory of the same name in
+<I>c:/mybackups/2004-06-01</I>.
+<P>Uncommitted transactions do not appear in the backed-up database.
+<DL><DT><B>Note:</B></DT><DD>Do not back up different databases with the same name to the same backup
+directory. If a database of the same name already exists in the backup
+directory, it is assumed to be an older version and is overwritten.
+</DD></DL>
+<DL><DT><B>Note:</B></DT><DD>If you are doing this through the Network Server, refer to the workaround in <A HREF="hubprnt19.html#HDRSII-APPS-">Differences between running Derby in embedded mode and using the Network Server</A>.
+</DD></DL>
+<P><H1><A NAME="HDRSII-BUBBKUP-75469">Using Operating System Commands with the freeze and unfreeze system procedures</A></H1>
+<P>Typically, this procedure is used to speed up the copy operation involved
+in the on-line backup. In this scenario, Derby does not perform
+the copy operation for you. You use the
+<I>SYSCS_UTIL.SYSCS_FREEZE_DATABASE()</I> procedure to lock the
+database, and then explicitly copy the database directory using operating
+system commands.
+<P>For example, because the UNIX<SUP></SUP> <I>tar</I> command uses
+operating system file-copying routines and Derby uses the IBM Application
+Developer Kit file-copying routines, tar might provide faster backups than the
+<I>SYSCS_UTIL.SYSCS_BACKUP_DATABASE</I> procedure.
+<P>
+<A NAME="IDX254"></A>
+<A NAME="IDX255"></A>
+To use operating system commands for on-line database backups, call the
+<I>SYSCS_UTIL.SYSCS_FREEZE_DATABASE()</I> system procedure.
+The <I>SYSCS_UTIL.SYSCS_FREEZE_DATABASE()</I> system procedure puts
+the database into a state in which it can be safely copied. Once the
+copy is complete, use the <I>SYSCS_UTIL.SYSCS_FREEZE_DATABASE()</I>
+system procedure to continue working with the database. Only after
+<I>SYSCS_UTIL.SYSCS_FREEZE_DATABASE()</I> has been specified can
+transactions once again write to the database. Read operations can
+proceed while the database is &quot;frozen&quot;.
+<DL><DT><B>Note:</B></DT><DD>To ensure a consistent backup of the database, Derby might block
+applications that attempt to write to a 'frozen' database until the
+back up is completed and the
+<I>SYSCS_UTIL.SYSCS_UNFREEZE_DATABASE()</I>system procedure is
+called.
+</DD></DL>
+<P>The following example demonstrates using <I>freeze</I> and
+<I>unfreeze</I> surrounding an operating system copy command:
+<PRE>String backupdirectory = "c:/mybackups/" + JCalendar.getToday();
+Statement s = conn.createStatement();
+s.executeUpdate(
+    "CALL SYSCS_UTIL.SYSCS_FREEZE_DATABASE();
+<B>//copy the database directory during this interval</B>
+s.executeUpdate(
+    "CALL SYSCS_UTIL.SYSCS_UNFREEZE_DATABASE();
+s.close();
+</PRE>
+<DL><DT><B>Note:</B></DT><DD>If you are doing this through the Network Server, refer to the workaround in <A HREF="hubprnt19.html#HDRSII-APPS-">Differences between running Derby in embedded mode and using the Network Server</A>.
+</DD></DL>
+<P><H1><A NAME="HDRSII-BUBBKUP-67525">When the Log is in a non-Default Location</A></H1>
+<DL><DT><B>Note:</B></DT><DD>Read <A HREF="hubprnt51.html#HDRSII-LOG-98797">Logging on a Separate Device</A> to find out about the default location of the database
+log.
+</DD></DL>
+<P>If you put the database log in a non-default location prior to backing up
+the database, note the following:
+<UL>
+<LI>If backing up the database using an operating system command, you must
+explicitly copy the log file as well. 
+<PRE>xcopy d:\mydatabases\sample c:\mybackups\2004-06-01\sample /s /i
+xcopy h:\janet\tourslog\log c:\mybackups\2004-06-01\sample\log /s /i
+</PRE>
+</LI></UL>
+<DL><DT><B>Note:</B></DT><DD>If you are not using Windows NT, substitute the appropriate operating system
+command for copying a directory and all contents to a new location.
+</DD></DL>
+<UL>
+<LI>Edit the <I>logDevice </I>entry in
+<I>service.properties</I> of the database backup so that it points
+to the correct location for the log. In the above example, the log was
+moved to the default location for a log, so you could remove the logDevice
+entry entirely, or leave the logDevice entry as is and wait until the database
+is restored to edit the entry.
+</LI></UL>
+<P>See <A HREF="hubprnt51.html#HDRSII-LOG-98797">"Logging on a Separate Device"</A> for information about putting the log in a non-default
+location.
+<P><H1><A NAME="HDRSII-BUBBKUP-21105">Backing Up Encrypted Databases</A></H1>
+<P>
+<A NAME="IDX256"></A>
+<A NAME="IDX257"></A>
+When you back up an encrypted database, both the backup and the log files
+remain encrypted. To restore an encrypted database, you must know the
+boot password.
+<P><HR>[ <A HREF="hubprnt42.html">Previous Page</A><br><A HREF="hubprnt44.html">Next Page</A><br><A HREF="hubprnt02.html#ToC">Table of Contents</A><br><A HREF="hubprnt65.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt44.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt44.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,37 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Restoring a Database from a Backup Copy</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Fri, 16 Jul 2004 10:56:44">
+<META HTTP-EQUIV="review" CONTENT="Sat, 16 Jul 2005 10:56:44">
+<META HTTP-EQUIV="expires" CONTENT="Sun, 16 Jul 2006 10:56:44">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-BUBBKUP-44223">Restoring a Database from a Backup Copy</H1>
+<P>You can specify the <I>restoreFrom=Path</I> attribute in the boot time
+connection URL to restore a database using a full backup from the specified
+location. If a database with the same name exists in
+the <I>derby.system.home</I> location, the whole
+database is deleted, copied from the backup location, and then
+restarted.
+<P>The log files are copied to the same location they were in when the backup
+was taken. The<I>logDevice</I> attribute can be used in conjunction
+with <I>restoreFrom=Path</I> to store logs in a different location.
+For Example, to restore the <I>toursDB</I> database using a backup copy in
+<I>c:\mybackups\sample</I>, the connection URL should be:
+<PRE>jdbc:derby:toursDB;createFrom=c:\mybackups\sample
+</PRE>
+<P><HR>[ <A HREF="hubprnt43.html">Previous Page</A><br><A HREF="hubprnt45.html">Next Page</A><br><A HREF="hubprnt02.html#ToC">Table of Contents</A><br><A HREF="hubprnt65.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt45.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt45.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,43 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Creating a Database From a Backup Copy</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="Creating a Database From a Backup Copy">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Fri, 16 Jul 2004 10:56:44">
+<META HTTP-EQUIV="review" CONTENT="Sat, 16 Jul 2005 10:56:44">
+<META HTTP-EQUIV="expires" CONTENT="Sun, 16 Jul 2006 10:56:44">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="Header_106">Creating a Database From a Backup Copy</H1>
+<P>
+<A NAME="IDX258"></A>
+You can specify the <I>createFrom=Path</I> attribute in the boot time
+connection URL to create a database using a full backup at a specified
+location. If there is a database with the same name in
+derby.system.home, an error will occur and the existing
+database will be left intact. If there is not an existing database with
+the same name in the current <I>derby.system.home</I>
+location, the whole database is copied from the backup location to the
+<I>derby.system.home</I> location and started.
+<P>The Log files are copied to the default location. The logDevice
+attribute can be used in conjunction with <I>createFrom=Path</I> to store
+logs in a different location. With <I>createFrom=Path</I> you do
+not need to copy the individual log files to the log directory.
+<P>For example, to create the <I>toursDB</I> database using a backup copy
+in <I>c:\mybackups\sample</I>, the connection URL should be: 
+<PRE>jdbc:derby.sample;createFrom=c:\mybackups\sample
+</PRE>
+<P><HR>[ <A HREF="hubprnt44.html">Previous Page</A><br><A HREF="hubprnt46.html">Next Page</A><br><A HREF="hubprnt02.html#ToC">Table of Contents</A><br><A HREF="hubprnt65.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt46.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt46.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,138 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Roll-forward Recovery</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="Roll-forward Recovery, Backing Up, Online Archived Logs, Enabling, Disabling, Protecting Log Files">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Fri, 16 Jul 2004 10:56:44">
+<META HTTP-EQUIV="review" CONTENT="Sat, 16 Jul 2005 10:56:44">
+<META HTTP-EQUIV="expires" CONTENT="Sun, 16 Jul 2006 10:56:44">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRROLLFORWARD">Roll-forward Recovery</H1>
+<P>
+<A NAME="IDX259"></A>
+Derby supports roll-forward recovery to restore a damaged database to the
+most recent state before a failure occurred. Derby restores a
+database from full backup and replays all the transactions after the
+backup. All the log files after a backup are required to replay the
+transactions after the backup. By default, the database keeps only logs
+that are required for crash-recovery. For roll-forward recovery to be
+successful, all log files should be archived after a backup. Log files
+can be archived using the backup function calls that enable log
+archiving.
+<P>In roll-forward recovery the log archival mode ensures that all old log
+files are available. The log files are available only from the time
+that the log archival mode is enabled.
+<P>Derby uses the following information to restore the database:
+<UL>
+<LI>The backup copy of the database
+</LI><LI>The set of archived logs
+</LI><LI>The current online active log
+</LI></UL>
+<P>You cannot use roll-forward recovery to restore individual tables.
+Roll-forward recovery recovers the entire database.
+<P>To restore a database using roll-forward recovery, you must already have a
+backup copy of the database, all the archived logs since then, and the active
+log files. All the log files should be in the database log
+directory.
+<P>There are two types of log files in Derby: active logs and
+online archived logs.
+<P><B>Active Logs:</B>
+<P>Active logs are used during crash recovery to prevent a failure from
+leaving a database in an inconsistent state. Roll-forward recovery can
+also use the active logs to recover to the end of the log files. Active
+logs are located in the database log path directory.
+<P><B>Online Archived Logs</B>
+<A NAME="IDX260"></A>
+<P>Log files that are stored for roll-forward recovery use when they are no
+longer needed for crash recovery. Online Archived logs are also kept in
+the database log path directory.
+<P><B>Enabling Log Archival Mode</B>
+<A NAME="IDX261"></A>
+<P>Online archive logs are available only if the database is enabled for log
+archival mode. You can use the following system procedure:
+<PRE>SYSCS_UTIL.SYSCS_BACKUP_DATABASE_AND_ENABLE_LOG_ARCHIVE_MODE
+(IN BACKUPDIR VARCHAR(32672), IN SMALLINT DELETE_ARCHIVED_LOG_FILES)
+</PRE>
+<P>The input parameters for the above calls are the location where the backup
+should be stored and to indicate to the database whether or not to keep online
+archived logs for the backup. Existing online archived log files before
+this backup will be deleted if the input parameter value for
+<I>deleteOnlineArchivedLogFiles</I> is non-zero. The log files are
+deleted only after a successful backup.
+<DL><DT><B>Note:</B></DT><DD>Make sure to store the backup database in a safe place when you choose the
+log file removal option.
+</DD></DL>
+<P><B>Disabling Log Archival Mode:</B>
+<A NAME="IDX262"></A>
+<P>Once you enable log archival mode, the database will always have the log
+archival mode enabled even if it is subsequently booted or backed up.
+The only way to disable the log archive mode is to call:
+<P><I>SYSCS_UTIL.SYSCS_DISABLE_LOG_ARCHIVE_MODE(IN SMALLINT
+DELETE_ARCHIVED_LOG_FILES )</I>
+<P>This system procedure disables the log archive mode and deletes any
+existing online archived log files if the input parameter
+<I>DELETE_ARCHIVED_LOG_FILES </I>is non-zero.
+<P><B>Performing Roll-Forward Recovery:</B>
+<P>By using the full backup copy , archived logs and active logs, the database
+can be restored to its most recent state by performing roll-forward
+recovery. Roll-forward recovery can be performed by specifying a
+connection URL attribute <I>rollForwardRecoveryFrom=&lt;BackupPath&gt;</I>
+at boot time. This brings the database to most recent state using full
+backup copy , archived logs and active logs. All the log files should
+be in the database log path directory.
+<P>In the following example a database named 'wombat' is backed up
+to d:/database directory with log archive mode enabled and restored
+using roll-forward recovery after a media failure:
+<P><B>Backing Up a Database:</B>
+<P>
+<PRE>connect 'jdbc:derby:wombat;create=true';
+ 
+create table t1(a int not null primary key);
+------------------DML/DDL Operations
+CALL SYSCS_UTIL.SYSCS_BACKUP_DATABASE_AND_ENABLE_LOG_ARCHIVE_MODE
+('d:/backup', 0);
+insert into t1 values(19);
+create table t2(a int);
+-----------------DML/DDL Operations
+-----------------Database Crashed (Media Corruption on data disks)
+</PRE>
+<P><B>Restoring a Database Using Roll-Forward Recovery:</B>
+<P>
+<PRE>connect 'jdbc:derby:wombat;rollForwardRecoveryFrom=d:/backup/wombat';
+select * from t1;
+---------------DML/DDL Operations
+</PRE>
+<P>The following attribute can be specified in the JDBC boot time connection
+URL:
+<P><I>rollForwardRecoveryFrom=&lt;Path&gt;</I>
+<P>For more information see the rollForwardRecoveryFrom=&lt;Path&gt; section
+in the Derby Reference Manual.
+<P>After a database is restored from full backup, transactions from the online
+archived logs and active logs are replayed.
+<P><H1><A NAME="Header_108">Protecting Log Files</A></H1>
+<P>
+<A NAME="IDX263"></A>
+The roll-forward recovery mechanism only helps to restore a database to the
+most recent point of time if the log files are available. It is very
+important to make sure that log data is not damaged due to a disk
+crash. You should use some form of disk fault tolerance method.
+Generally, this is accomplished through the use of a disk array. A disk
+array consists of a collection of disk drives that appear as a single large
+disk drive to an application. Disk arrays involve disk striping, which
+is the distribution of a file across multiple disks, the mirroring of disks,
+and data parity checks.
+<P><HR>[ <A HREF="hubprnt45.html">Previous Page</A><br><A HREF="hubprnt47.html">Next Page</A><br><A HREF="hubprnt02.html#ToC">Table of Contents</A><br><A HREF="hubprnt65.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt47.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt47.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,45 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Restoring a Database from a Backup Copy Using OS Commands</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="Restoring a database, restoring from, Backup">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Fri, 16 Jul 2004 10:56:44">
+<META HTTP-EQUIV="review" CONTENT="Sat, 16 Jul 2005 10:56:44">
+<META HTTP-EQUIV="expires" CONTENT="Sun, 16 Jul 2006 10:56:44">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<HR><H1 NAME="Header_109">Restoring a Database from a Backup Copy Using OS Commands</H1>
+<P>
+<A NAME="IDX264"></A>
+<A NAME="IDX265"></A>
+When you restore a database, the log file must be in the default
+location.
+<P>Do not provide a <I>logDevice</I> entry in the
+<I>service.properties</I> file that specifies the location to which
+the database is being restored.
+<P>Before you copy a backed-up database to its new location, ensure that a
+database of the same name does not exist.
+<P>To restore a database from a backup copy, copy the backup database to the
+location where you want to restore the database, and start the
+database. After you restore the database, check the consistency of the
+database as described in <A HREF="hubprnt38.html#HDRSII-CONSIST-54401">"Checking Database Consistency"</A>.
+<P>For example, to use Windows NT operating system commands to restore the
+<I>sample</I> database to the directory d:\mydatabases:
+<PRE>rmdir  d:\mydatabases\sample /s
+ 
+xcopy c:\mybackups\2004-06-01\sample d:\mydatabases\sample /s /i
+</PRE>
+<P><HR>[ <A HREF="hubprnt46.html">Previous Page</A><br><A HREF="hubprnt48.html">Next Page</A><br><A HREF="hubprnt02.html#ToC">Table of Contents</A><br><A HREF="hubprnt65.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt48.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt48.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,50 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Restoring a Database Using OS Commands when the Log File Is Not in the Default Location</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Fri, 16 Jul 2004 10:56:44">
+<META HTTP-EQUIV="review" CONTENT="Sat, 16 Jul 2005 10:56:44">
+<META HTTP-EQUIV="expires" CONTENT="Sun, 16 Jul 2006 10:56:44">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-BUBBKUP-26328">Restoring a Database Using OS Commands when the Log File Is Not in the Default Location</H1>
+<P><B>If You Used the Built-In Backup Command:</B>
+<P>When you back up a database whose log file is not in the default location,
+Derby puts the log file in the default location. When you restore
+the database from this backup copy, you must move the log file if you want to
+put it in a non-default location. Follow the instructions in <A HREF="hubprnt51.html#HDRSII-LOG-98797">"Logging on a Separate Device"</A> for moving a log file.
+<P><B>If You Used Operating System Commands:</B>
+<P>After you restore the database, you must move the log file to the original
+location. If the database log is not in the default location, or if a
+<I>logDevice</I> entry is specified in the
+<I>service.properties</I> file that specifies the location to which
+the database is being restored, ensure that the <I>logDevice</I> entry and
+the new log location correspond. Copy the database to the new location
+and connect to the database.
+<P>To correspond the <I>logDevice</I> entry to the log file location, use
+one of the following methods:
+<UL>
+<LI>Move the log to the location that is indicated by the <I>logDevice</I>
+entry.
+</LI><LI>Change the <I>logDevice</I> entry in the
+<I>service.properties</I> file to correspond to the log
+location.
+</LI><LI>Change both the new log location and the <I>logDevice</I> entry to
+represent the same location.
+</LI><LI>Move the log to the default location and delete the <I>logDevice</I>
+entry in the <I>service.properties</I> file.
+</LI></UL>
+<P><HR>[ <A HREF="hubprnt47.html">Previous Page</A><br><A HREF="hubprnt49.html">Next Page</A><br><A HREF="hubprnt02.html#ToC">Table of Contents</A><br><A HREF="hubprnt65.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt49.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt49.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,32 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Failure Recovery</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="failure of, Backup">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Fri, 16 Jul 2004 10:56:44">
+<META HTTP-EQUIV="review" CONTENT="Sat, 16 Jul 2005 10:56:44">
+<META HTTP-EQUIV="expires" CONTENT="Sun, 16 Jul 2006 10:56:44">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-BUBBKUP-66644">Failure Recovery</H1>
+<P>
+<A NAME="IDX266"></A>
+If the backup process does not complete, the new copy of the database is
+unusable. Derby does not perform automatic cleanup if a backup
+process fails.
+<P>If the backup process fails or an error occurs, the original database is
+usable after it is recovered, but the backup copy is unusable.
+<P><HR>[ <A HREF="hubprnt48.html">Previous Page</A><br><A HREF="hubprnt50.html">Next Page</A><br><A HREF="hubprnt02.html#ToC">Table of Contents</A><br><A HREF="hubprnt65.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt50.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt50.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,41 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Backup History</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="BACKUP.HISTORY file">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Fri, 16 Jul 2004 10:56:44">
+<META HTTP-EQUIV="review" CONTENT="Sat, 16 Jul 2005 10:56:44">
+<META HTTP-EQUIV="expires" CONTENT="Sun, 16 Jul 2006 10:56:44">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-BUBBKUP-43568">Backup History</H1>
+<P>
+<A NAME="IDX267"></A>
+Backup history is recorded in an ASCII file (BACKUP.HISTORY) in the
+database directory of the original database. This file stores the time
+and location of the backup process. If the file does not exist, it is
+created during the backup. If it does exist, new information is
+appended to it. The following example shows the backup history that is
+written to a file:
+<PRE>Thu Sep 09 09:18:35 PDT 1999:Backup started for database located at
+D:\mydatabases\toursDB
+Thu Sep 09 09:18:44 PDT 1999:copied database directory from
+D:\mydatabases\toursDB to C:\mybackups\1999-01-01\toursDB
+Thu Sep 09 09:18:44 PDT 1999:copied log directory from
+D:\mydatabases\toursDB\log to C:\mybackups\1999-01-01\toursDB\log
+Thu Sep 09 09:18:44 PDT 1999:Backup completed, log instant at (10,15855)
+</PRE>
+<P><HR>[ <A HREF="hubprnt49.html">Previous Page</A><br><A HREF="hubprnt51.html">Next Page</A><br><A HREF="hubprnt02.html#ToC">Table of Contents</A><br><A HREF="hubprnt65.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt51.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt51.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,41 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Logging on a Separate Device</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="Logging transactions, putting on separate device, Transaction log, default location for, Log">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Fri, 16 Jul 2004 10:56:44">
+<META HTTP-EQUIV="review" CONTENT="Sat, 16 Jul 2005 10:56:44">
+<META HTTP-EQUIV="expires" CONTENT="Sun, 16 Jul 2006 10:56:44">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<HR><H1 NAME="HDRSII-LOG-98797">Logging on a Separate Device</H1>
+<P>System administrators can improve the performance for update-intensive,
+large databases by putting a database's log on a separate device, which
+reduces I/O contention.
+<P>
+<A NAME="IDX268"></A>
+<A NAME="IDX269"></A>
+<A NAME="IDX270"></A>
+By default, the transaction log is in the <I>log</I> subdirectory of the
+database directory. If you want to store this <I>log</I>
+subdirectory in another location, do either of the following:
+<UL>
+<LI>Specify the non-default location using the <I>logDevice</I> attribute
+on the database connection URL when you create the database.
+</LI><LI>If the database is already created, move the log manually and update the
+<I>service.properties</I> file.
+</LI></UL>
+<P><HR>[ <A HREF="hubprnt50.html">Previous Page</A><br><A HREF="hubprnt52.html">Next Page</A><br><A HREF="hubprnt02.html#ToC">Table of Contents</A><br><A HREF="hubprnt65.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt52.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt52.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,44 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Using the logDevice Property</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="logDevice, setting logDevice in, service.properties file">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Fri, 16 Jul 2004 10:56:44">
+<META HTTP-EQUIV="review" CONTENT="Sat, 16 Jul 2005 10:56:44">
+<META HTTP-EQUIV="expires" CONTENT="Sun, 16 Jul 2006 10:56:44">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRLOG800206">Using the logDevice Property</H1>
+<A NAME="IDX271"></A>
+<P>To specify a non-default location for the log directory, set the
+<I>logDevice</I> attribute on the database connection URL when you create
+the database. (This attribute is meaningful only when you are creating
+a database.) You can specify <TT><I>logDevice</I></TT> as either
+an absolute path or a path relative to the directory where the JVM is being
+executed.
+<P>
+<A NAME="IDX272"></A>
+Setting <I>logDevice</I> on the database connection URL adds an entry to
+the <I>service.properties</I> file. If you ever move the log
+manually, alter the entry in <I>service.properties.</I> If
+you move the log back to the default location, remove the <TT><I>logDevice
+</I></TT>entry from <I>service.properties</I>.
+<P>To check the log location for an existing database, you can retrieve the
+logDevice attribute as a database property. Issue the following
+statement:
+<PRE><B>VALUES SYSCS_UTIL.SYSCS_GET_DATABASE_PROPERTY('logDevice')</B>
+</PRE>
+<P><HR>[ <A HREF="hubprnt51.html">Previous Page</A><br><A HREF="hubprnt53.html">Next Page</A><br><A HREF="hubprnt02.html#ToC">Table of Contents</A><br><A HREF="hubprnt65.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt53.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt53.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,30 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Example of Creating a Log in a Non-Default Location</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Fri, 16 Jul 2004 10:56:44">
+<META HTTP-EQUIV="review" CONTENT="Sat, 16 Jul 2005 10:56:44">
+<META HTTP-EQUIV="expires" CONTENT="Sun, 16 Jul 2006 10:56:44">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRLOG800241">Example of Creating a Log in a Non-Default Location</H1>
+<P>The following database connection URL creates a database in the directory
+d:/mydatabases, but puts the database log directory in
+h:/janets/tourslog:
+<PRE>jdbc:derby:d:/mydatabases/toursDB;
+    create=true;logDevice=h:/janets/tourslog
+</PRE>
+<P><HR>[ <A HREF="hubprnt52.html">Previous Page</A><br><A HREF="hubprnt54.html">Next Page</A><br><A HREF="hubprnt02.html#ToC">Table of Contents</A><br><A HREF="hubprnt65.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt54.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt54.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,46 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Example of Moving a Log Manually</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Fri, 16 Jul 2004 10:56:44">
+<META HTTP-EQUIV="review" CONTENT="Sat, 16 Jul 2005 10:56:44">
+<META HTTP-EQUIV="expires" CONTENT="Sun, 16 Jul 2006 10:56:44">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRLOG800279">Example of Moving a Log Manually</H1>
+<P>If you later want to move the log to g:/bigdisk/tourslog, move the
+log with operating system commands:
+<PRE><B>move h:\janets\tourslog\log\*.* g:\bigdisk\tourslog\log</B>
+</PRE>
+<P>and alter the <I>logDevice </I>entry in
+<I>service.properties</I> to read as follows:
+<PRE>logDevice=g:/bigdisk/toursLog
+</PRE>
+<DL><DT><B>Note:</B></DT><DD>You can use either a single forward slash or double back slashes for a path
+separator.
+</DD></DL>
+<P>If you later want to move the log back to its default location (in this
+case, d:\mydatabases\toursDB\log), move the log manually as
+follows:
+<PRE><B>move g:\bigdisk\tourslog\log\*.* d:\mydatabases\toursDB\log</B>
+</PRE>
+<P>and delete the <I>logDevice </I>entry from
+<I>service.properties.</I>
+<DL><DT><B>Note:</B></DT><DD>This example uses commands specific to the Windows NT operating
+system. Use commands appropriate to your operating system to copy a
+directory and all contents to a new location.
+</DD></DL>
+<P><HR>[ <A HREF="hubprnt53.html">Previous Page</A><br><A HREF="hubprnt55.html">Next Page</A><br><A HREF="hubprnt02.html#ToC">Table of Contents</A><br><A HREF="hubprnt65.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt55.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt55.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,26 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Issues for Logging in a Non-Default Location</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Fri, 16 Jul 2004 10:56:44">
+<META HTTP-EQUIV="review" CONTENT="Sat, 16 Jul 2005 10:56:44">
+<META HTTP-EQUIV="expires" CONTENT="Sun, 16 Jul 2006 10:56:44">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRLOG800315">Issues for Logging in a Non-Default Location</H1>
+<P>When the log is not in the default location, backing up and restoring a
+database can require extra steps. See <A HREF="hubprnt42.html#HDRSII-BUBBKUP-98797">"Backing Up and Restoring Databases"</A> for details.
+<P><HR>[ <A HREF="hubprnt54.html">Previous Page</A><br><A HREF="hubprnt56.html">Next Page</A><br><A HREF="hubprnt02.html#ToC">Table of Contents</A><br><A HREF="hubprnt65.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt56.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt56.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,96 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Getting Locking Information</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="monitoring, Locks, tools to help minimize, Deadlock">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Fri, 16 Jul 2004 10:56:44">
+<META HTTP-EQUIV="review" CONTENT="Sat, 16 Jul 2005 10:56:44">
+<META HTTP-EQUIV="expires" CONTENT="Sun, 16 Jul 2006 10:56:44">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<HR><H1 NAME="HDRSII-LOCKVTI-42553">Getting Locking Information</H1>
+<P>
+<A NAME="IDX273"></A>
+<A NAME="IDX274"></A>
+Derby provides a tool to monitor and display locking information.
+This tool can help you create applications that minimize deadlock.
+It can also help you locate the cause of deadlock when it does occur.
+<P>To diagnose locking problems, perform the following action:
+<UL>
+<LI>constantly monitor locking traffic by logging all deadlocks (using the
+<I>derby.locks.monitor</I> property)
+</LI></UL>
+
+<P><H1 NAME="HDRSII-LOCKVTI-83889">Lock Monitoring</H1>
+<P>
+<A NAME="IDX282"></A>
+The <I>derby.stream.error.logSeverityLevel</I>
+property determines the level of error you are informed about. By
+default,
+<TT><I>derby.stream.error.logSeverityLevel
+</I></TT>is set at 40000. If
+<TT><I>derby.stream.error.logSeverityLevel</I></TT>
+is set to display transaction-level errors (that is, if it is set to a value
+less than 40000), deadlock errors are logged to the
+<I>derby.log</I> file. If it is set to a value of 40000
+or higher, deadlock errors are not logged to the
+<I>derby.log</I> file.
+<P>
+<A NAME="IDX283"></A>
+The <I>derby.locks.monitor</I> property ensures that
+deadlock errors are logged regardless of the value of
+<TT><I>derby.stream.error.logSeverityLevel</I></TT>.
+When <TT><I>derby.locks.monitor</I></TT> is set to
+<I>true</I>, all locks involved in deadlocks are written to
+<I>derby.log</I> along with a unique number identifying the
+lock.
+<P>
+<A NAME="IDX284"></A>
+To see a thread's stack trace when a lock is requested, set
+<I>derby.locks.deadlockTrace</I> to true. This
+property is ignored if
+<TT><I>derby.locks.monitor</I></TT> is set to
+<I>false</I>.
+<DL><DT><B>Note:</B></DT><DD>Use <I>derby.locks.deadlockTrace</I> with care.
+Setting this property can alter the timing of the application, severely affect
+performance, and produce a very large <I>derby.log</I>
+file.
+</DD></DL>
+<P>For information on how to set properties, see <CITE>Tuning 
+Derby</CITE>. For specific information about the properties
+mentioned in this section, see the properties chapter in that book.
+<P>Here is an example of a victim's error message when Derby aborts a
+transaction because of a deadlock:
+<PRE>--SQLException Caught--
+ 
+SQLState: 40001 =
+Error Code: 30000&nbsp;
+Message: A lock could not be obtained due to a deadlock,
+cycle of locks and waiters is: Lock : ROW, DEPARTMENT, (1,14)
+Waiting XID : {752, X} , APP, update department set location='Boise'
+	where deptno='E21'
+Granted XID : {758, X} Lock : ROW, EMPLOYEE, (2,8)
+Waiting XID : {758, U} , APP, update employee set bonus=150 where salary=23840
+Granted XID : {752, X} The selected victim is XID : 752
+</PRE>
+<DL><DT><B>Note:</B></DT><DD>You can use the <I>derby.locks.waitTimeout</I> and
+<I>derby.locks.deadlockTimeout</I> properties to
+configure how long Derby waits for a lock to be released, or when to
+begin deadlock checking. For more information on these properties, see
+the chapter that discusses controlling Derby application behavior, in the
+<I>Derby Developer's Guide</I>.
+</DD></DL>
+<P><HR>[ <A HREF="hubprnt55.html">Previous Page</A><br><A HREF="hubprnt59.html">Next Page</A><br><A HREF="hubprnt02.html#ToC">Table of Contents</A><br><A HREF="hubprnt65.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt58.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt58.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,83 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Lock Monitoring</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="derby.stream.error.logSeverityLevel, derby.locks.monitor, derby.locks.deadlockTrace">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Fri, 16 Jul 2004 10:56:44">
+<META HTTP-EQUIV="review" CONTENT="Sat, 16 Jul 2005 10:56:44">
+<META HTTP-EQUIV="expires" CONTENT="Sun, 16 Jul 2006 10:56:44">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-LOCKVTI-83889">Lock Monitoring</H1>
+<P>
+<A NAME="IDX282"></A>
+The <I>derby.stream.error.logSeverityLevel</I>
+property determines the level of error you are informed about. By
+default,
+<TT><I>derby.stream.error.logSeverityLevel
+</I></TT>is set at 40000. If
+<TT><I>derby.stream.error.logSeverityLevel</I></TT>
+is set to display transaction-level errors (that is, if it is set to a value
+less than 40000), deadlock errors are logged to the
+<I>derby.log</I> file. If it is set to a value of 40000
+or higher, deadlock errors are not logged to the
+<I>derby.log</I> file.
+<P>
+<A NAME="IDX283"></A>
+The <I>derby.locks.monitor</I> property ensures that
+deadlock errors are logged regardless of the value of
+<TT><I>derby.stream.error.logSeverityLevel</I></TT>.
+When <TT><I>derby.locks.monitor</I></TT> is set to
+<I>true</I>, all locks involved in deadlocks are written to
+<I>derby.log</I> along with a unique number identifying the
+lock.
+<P>
+<A NAME="IDX284"></A>
+To see a thread's stack trace when a lock is requested, set
+<I>derby.locks.deadlockTrace</I> to true. This
+property is ignored if
+<TT><I>derby.locks.monitor</I></TT> is set to
+<I>false</I>.
+<DL><DT><B>Note:</B></DT><DD>Use <I>derby.locks.deadlockTrace</I> with care.
+Setting this property can alter the timing of the application, severely affect
+performance, and produce a very large <I>derby.log</I>
+file.
+</DD></DL>
+<P>For information on how to set properties, see <CITE>Tuning 
+Derby</CITE>. For specific information about the properties
+mentioned in this section, see the properties chapter in that book.
+<P>Here is an example of a victim's error message when Derby aborts a
+transaction because of a deadlock:
+<PRE>--SQLException Caught--
+ 
+SQLState: 40001 =
+Error Code: 30000&nbsp;
+Message: A lock could not be obtained due to a deadlock,
+cycle of locks and waiters is: Lock : ROW, DEPARTMENT, (1,14)
+Waiting XID : {752, X} , APP, update department set location='Boise'
+	where deptno='E21'
+Granted XID : {758, X} Lock : ROW, EMPLOYEE, (2,8)
+Waiting XID : {758, U} , APP, update employee set bonus=150 where salary=23840
+Granted XID : {752, X} The selected victim is XID : 752
+</PRE>
+<DL><DT><B>Note:</B></DT><DD>You can use the <I>derby.locks.waitTimeout</I> and
+<I>derby.locks.deadlockTimeout</I> properties to
+configure how long Derby waits for a lock to be released, or when to
+begin deadlock checking. For more information on these properties, see
+the chapter that discusses controlling Derby application behavior, in the
+<I>Derby Developer's Guide</I>.
+</DD></DL>
+<P><HR>[ <A HREF="hubprnt56.html">Previous Page</A><br><A HREF="hubprnt59.html">Next Page</A><br><A HREF="hubprnt02.html#ToC">Table of Contents</A><br><A HREF="hubprnt65.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt59.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt59.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,31 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Identifying and Reclaiming Unused Space</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="reclaiming, Space">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Fri, 16 Jul 2004 10:56:44">
+<META HTTP-EQUIV="review" CONTENT="Sat, 16 Jul 2005 10:56:44">
+<META HTTP-EQUIV="expires" CONTENT="Sun, 16 Jul 2006 10:56:44">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<HR><H1 NAME="HDRSII-SPACE-73511">Identifying and Reclaiming Unused Space</H1>
+<A NAME="IDX285"></A>
+<UL>
+<LI><A HREF="hubprnt60.html#HDRSII-SPACE-21579">Overview</A>
+</LI><LI><A HREF="hubprnt61.html#HDRSII-SPACE-78375">Identifying Unused Space in a Table or Index</A>
+</LI><LI><A HREF="hubprnt62.html#HDRSII-SPACE-44643">Reclaiming Unused Space</A>
+</LI></UL>
+<P><HR>[ <A HREF="hubprnt58.html">Previous Page</A><br><A HREF="hubprnt60.html">Next Page</A><br><A HREF="hubprnt02.html#ToC">Table of Contents</A><br><A HREF="hubprnt65.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt60.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt60.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,35 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Overview</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Fri, 16 Jul 2004 10:56:44">
+<META HTTP-EQUIV="review" CONTENT="Sat, 16 Jul 2005 10:56:44">
+<META HTTP-EQUIV="expires" CONTENT="Sun, 16 Jul 2006 10:56:44">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-SPACE-21579">Overview</H1>
+<P>A Derby table or index (sometimes called a conglomerate) can contain
+unused space after large amounts of data have been deleted or updated.
+This happens because, by default, Derby does not return unused space to
+the operating system. Once a page has been allocated to a table or
+index, Derby does not automatically return the page to the operating
+system until the table or index is dropped, even if the space is no longer
+needed. However, Derby does provide a way to:
+<UL>
+<LI>identify unused space in tables and associated indexes
+</LI><LI>reclaim unused space in tables and associated indexes
+</LI></UL>
+<P><HR>[ <A HREF="hubprnt59.html">Previous Page</A><br><A HREF="hubprnt61.html">Next Page</A><br><A HREF="hubprnt02.html#ToC">Table of Contents</A><br><A HREF="hubprnt65.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt61.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt61.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,104 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Identifying Unused Space in a Table or Index</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="org.apache.derby.diag.SpaceTableVTI">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Fri, 16 Jul 2004 10:56:44">
+<META HTTP-EQUIV="review" CONTENT="Sat, 16 Jul 2005 10:56:44">
+<META HTTP-EQUIV="expires" CONTENT="Sun, 16 Jul 2006 10:56:44">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-SPACE-78375">Identifying Unused Space in a Table or Index</H1>
+<P><H1><A NAME="HDRSPACE801513">Getting an Estimate of Reclaimable Space</A></H1>
+<P>
+<A NAME="IDX286"></A>
+Use the SpaceTable VTI
+(<I>org.apache.derby.diag.SpaceTable</I>, aliased
+as <I>SpaceTable</I>) to get an estimate of the amount of space that can
+be reclaimed in a table.
+<P>The VTI takes a table name as an argument (or the schema name and the table
+name) and returns a conservative estimate of the space that can be reclaimed
+by compressing the table and its indexes.
+<P>For example, to get space information on a table named
+<I>FlightAvailability</I>, issue the following query:
+<PRE><B>SELECT *
+FROM NEW SpaceTable('FLIGHTAVAILABILITY') AS EQ</B>
+</PRE>
+<DL><DT><B>Note:</B></DT><DD>The table name must evaluate to a string. For table names created as
+non-delimited identifiers (non-case-sensitive), specify the table name in
+uppercase letters.
+</DD></DL>
+<P>You might wish to see only the estimate of the space that could be
+reclaimed by compressing the tables and its indexes. That is the most
+important information returned by the VTI:
+<PRE><B>SELECT CONGLOMERATENAME, ESTIMSPACESAVING&nbsp;
+FROM NEW SpaceTable('FLIGHTAVAILABILITY') AS EQ</B>
+</PRE>
+<P>For <I>FlightAvailability,</I> which has two indexes, the output would
+look something like this if the table has some space that could be
+reclaimed:
+<PRE>CONGLOMERATENAME                    |ESTIMSPACESAVING
+------------------------------------------------------------
+FLIGHTAVAILABILITY                  |12288
+846c00a0-00de-a111-40de-000a0a410d00|8192
+ace4c0a3-00de-a111-40de-000a0a410d00|4096
+</PRE>
+<P>The VTI also has a constructor that takes the schema name followed by the
+table name. To see unused information about all tables in all schemas,
+use the following query:
+<PRE><B>SELECT * FROM SYS.SYSSCHEMAS s, SYS.SYSTABLES t,
+   NEW SpaceTable(SCHEMANAME,TABLENAME) AS EQ
+WHERE s.SCHEMAID = t.SCHEMAID
+AND t.TABLENAME=EQ.CONGLOMERATENAME
+AND ISINDEX=false</B>
+</PRE>
+<P><H1><A NAME="HDRSPACE801545">About the Page Usage Information</A></H1>
+<P>The VTI also displays some information about page usage which is less
+immediately helpful than the estimate of space that could be reclaimed.
+In looking at the page usage information, for those who want to know, it helps
+to understand how Derby assigns space to a table or index. When it
+first creates the conglomerate (table or index), Derby
+<I>pre-allocates</I> a number of pages for the conglomerate (usually one,
+but the number is configurable). Derby then<I> allocates</I>
+pages to the conglomerate, always one page at a time. Allocated pages
+might contain rows, they might not. At some point Derby might flag
+some of those pages as inefficient users of space. Those pages are
+called <I>unfilled</I> pages in the VTI. When all the rows are
+deleted from a page, Derby de-allocates the page and makes it a <I>free
+</I>page. If the page is needed later, Derby can re-allocate the
+page. Derby bases its conservative estimate of the amount of space
+that could be reclaimed on the number of free pages. When you actually
+compress the table and indexes as described in <A HREF="hubprnt62.html#HDRSII-SPACE-44643">Reclaiming Unused Space</A>, Derby might also be able to reclaim space from
+unfilled pages, but this space is not included in the VTI's
+estimate. Derby is not able to reclaim space from pre-allocated
+pages that have not yet been allocated.
+<P>For example, to see only the page usage information for a table, you could
+issue the following command:
+<PRE><B>SELECT NUMALLOCATEDPAGES, NUMFREEPAGES,
+    NUMUNFILLEDPAGES, ISINDEX&nbsp;
+FROM NEW SpaceTable('FLIGHTAVAILABILITY') AS EQ</B>
+</PRE>
+<P>The following example output shows that the table has four allocated pages
+in total (three allocated and one allocated unfilled) and 1 free
+(de-allocated) pages. Its associated indexes (in the second two rows)
+also show some free pages.
+<PRE>NUMALLOCATEDPAGES   |NUMFREEPAGES        |NUMUNFILLEDPAGES    |ISINDEX
+--------------------------------------------------------------------
+1                   |3                   |1                   |false
+2                   |2                   |1                   |true
+2                   |1                   |1                   |true
+</PRE>
+<P><HR>[ <A HREF="hubprnt60.html">Previous Page</A><br><A HREF="hubprnt62.html">Next Page</A><br><A HREF="hubprnt02.html#ToC">Table of Contents</A><br><A HREF="hubprnt65.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt62.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt62.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,52 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Reclaiming Unused Space</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="Compressing tables and indexes">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Fri, 16 Jul 2004 10:56:44">
+<META HTTP-EQUIV="review" CONTENT="Sat, 16 Jul 2005 10:56:44">
+<META HTTP-EQUIV="expires" CONTENT="Sun, 16 Jul 2006 10:56:44">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-SPACE-44643">Reclaiming Unused Space</H1>
+<A NAME="IDX287"></A>
+<P>After you determine that a table and its indexes have a significant amount
+of unused space, use the <TT>SYSCS_UTIL.SYSCS_COMPRESS_TABLE</TT>
+procedure to reclaim that space.
+<P>Reclaiming space returns it to the operating system. For example,
+after you have identified that the <I>FlightAvailability</I> table and its
+related indexes have a significant amount of unused space, you could reclaim
+that space with the following command:
+<PRE><B>call SYSCS_UTIL.SYSCS_COMPRESS_TABLE('APP', 'FLIGHTAVAILABILITY', 0);</B>
+</PRE>
+<P>By default, the <TT>SYSCS_UTIL.SYSCS_COMPRESS_TABLE</TT> procedure
+instructs Derby to compress the table and its related indexes
+concurrently, which can use a lot of temporary disk space and memory.
+<P>The third parameter of the
+<TT>SYSCS_UTIL.SYSCS_COMPRESS_TABLE()</TT> procedure determines
+whether the operation runs in sequential or non-sequential mode. If you
+specify <TT>0</TT> for the third argument in the procedure, the operation
+runs in non-sequential mode. To force the operation to run in
+sequential mode, specify a non-zero smallint argument for the third
+argument. In sequential mode,Derby compresses the table and
+indexes sequentially, one at a time. Sequential compression uses less
+memory and disk space but is slower. The following example shows how to
+force the operation to run in sequential mode:
+<PRE><B>call SYSCS_UTIL.SYSCS_COMPRESS_TABLE('APP', 'FLIGHTAVAILABILITY', 1);</B>
+</PRE>
+<P>For more information about this command, see the <CITE>Derby
+Reference Manual</CITE>.
+<P><HR>[ <A HREF="hubprnt61.html">Previous Page</A><br><A HREF="hubprnt64.html">Next Page</A><br><A HREF="hubprnt02.html#ToC">Table of Contents</A><br><A HREF="hubprnt65.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt64.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt64.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,50 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Trademarks</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Fri, 16 Jul 2004 10:56:44">
+<META HTTP-EQUIV="review" CONTENT="Sat, 16 Jul 2005 10:56:44">
+<META HTTP-EQUIV="expires" CONTENT="Sun, 16 Jul 2006 10:56:44">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<HR><H1 NAME="HDRTRADEM">Trademarks</H1>
+<P>The following terms are trademarks of International Business Machines
+Corporation in the United States, other countries, or both, and have been used
+in at least one of the documents in the DB2 UDB documentation library.
+<BR>
+<TABLE >
+<TR>
+<TD ALIGN="LEFT" VALIGN="TOP" WIDTH="50%">
+Cloudscape<BR>
+DB2<BR>
+DB2 Universal Database<BR>
+</TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH="50%">
+DRDA<BR>
+IBM<BR>
+WebSphere<BR>
+</TD></TR></TABLE>
+<P>The following terms are trademarks or registered trademarks of other
+companies and have been used in at least one of the documents in the IBM
+Cloudscape documentation library:
+<P>Microsoft, Windows, Windows NT, and the Windows logo are trademarks of
+Microsoft Corporation in the United States, other countries, or both.
+<P>Java and all Java-based trademarks are trademarks of Sun Microsystems,
+Inc. in the United States, other countries, or both.
+<P>UNIX is a registered trademark of The Open Group in the United States and
+other countries.
+<P>Other company, product, or service names may be trademarks or service marks
+of others.
+<P><HR>[ <A HREF="hubprnt62.html">Previous Page</A><br><A HREF="hubprnt65.html">Next Page</A><br><A HREF="hubprnt02.html#ToC">Table of Contents</A><br><A HREF="hubprnt65.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt65.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/admin/hubprnt65.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,513 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Index</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Fri, 16 Jul 2004 10:56:44">
+<META HTTP-EQUIV="review" CONTENT="Sat, 16 Jul 2005 10:56:44">
+<META HTTP-EQUIV="expires" CONTENT="Sun, 16 Jul 2006 10:56:44">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P>
+<HR><H1 NAME="HDRINDEX_START">Index</H1>
+<strong><a href="#IDX0_42">B</a></strong>
+<ul class="indexlist">
+<li>Backing Up
+<ul class="indexlist">
+<li>Roll-forward Recovery
+<A HREF="hubprnt46.html#IDX259">(259)</A>
+</li>
+</ul>
+</li>
+<li>Backing up databases
+<A HREF="hubprnt42.html#IDX251">(251)</A>
+</li>
+<li>Backup
+<ul class="indexlist">
+<li>failure of
+<A HREF="hubprnt49.html#IDX266">(266)</A>
+</li>
+<li>of encrypted databases
+<A HREF="hubprnt43.html#IDX257">(257)</A>
+</li>
+<li>restoring from
+<A HREF="hubprnt47.html#IDX265">(265)</A>
+</li>
+</ul>
+</li>
+<li>BACKUP.HISTORY file
+<A HREF="hubprnt50.html#IDX267">(267)</A>
+</li>
+<li>Backup procedure
+<A HREF="hubprnt43.html#IDX252">(252)</A>
+</li>
+</ul>
+<strong><a href="#IDX0_43">C</a></strong>
+<ul class="indexlist">
+<li>Class path
+<ul class="indexlist">
+<li>for Network Server
+<A HREF="hubprnt22.html#IDX214">(214)</A>
+</li>
+</ul>
+</li>
+<li>derby.drda.host
+<A HREF="hubprnt23.html#IDX223">(223)</A>
+</li>
+<li>derby.drda.logConnections
+<A HREF="hubprnt23.html#IDX224">(224)</A>, <A HREF="hubprnt32.html#IDX240">(240)</A>
+</li>
+<li>derby.drda.maxThreads
+<A HREF="hubprnt23.html#IDX226">(226)</A>
+</li>
+<li>derby.drda.minthreads
+<A HREF="hubprnt31.html#IDX238">(238)</A>
+</li>
+<li>derby.drda.minThreads
+<A HREF="hubprnt23.html#IDX225">(225)</A>
+</li>
+<li>derby.drda.portNumber
+<A HREF="hubprnt23.html#IDX221">(221)</A>
+</li>
+<li>derby.drda.startNetworkServer
+<A HREF="hubprnt23.html#IDX220">(220)</A>
+</li>
+<li>derby.drda.timeslice
+<A HREF="hubprnt23.html#IDX227">(227)</A>
+</li>
+<li>derby.drda.traceDirectory
+<A HREF="hubprnt23.html#IDX222">(222)</A>
+</li>
+<li>derby.infolog.append
+<A HREF="hubprnt32.html#IDX239">(239)</A>
+</li>
+<li>derby.locks.deadlockTrace
+<A HREF="hubprnt58.html#IDX284">(284)</A>
+</li>
+<li>derby.locks.monitor
+<A HREF="hubprnt58.html#IDX283">(283)</A>
+</li>
+<li>derby.log
+<ul class="indexlist">
+<li>and the Network Server
+<A HREF="hubprnt32.html#IDX241">(241)</A>
+</li>
+</ul>
+</li>
+<li>derby.stream.error.logSeverityLevel
+<A HREF="hubprnt58.html#IDX282">(282)</A>
+</li>
+<li>com.ibm.db2.jcc.DB2BaseDataSource. CLEAR_TEXT_ PASSWORD_SECURITY
+<A HREF="hubprnt19.html#IDX199">(199)</A>
+</li>
+<li>com.ibm.db2.jcc.DB2BaseDataSource. ENCRYPTED_USER_AND_ PASSWORD_SECURITY
+<A HREF="hubprnt19.html#IDX203">(203)</A>
+</li>
+<li>com.ibm.db2.jcc.DB2BaseDataSource. USER_ONLY_SECURITY
+<A HREF="hubprnt19.html#IDX202">(202)</A>
+</li>
+<li>org.apache.derby.database. ConsistencyChecker.checkTable
+<A HREF="hubprnt39.html#IDX250">(250)</A>
+</li>
+<li>org.apache.derby.diag.SpaceTableVTI
+<A HREF="hubprnt61.html#IDX286">(286)</A>
+</li>
+<li>Compressing tables and indexes
+<A HREF="hubprnt62.html#IDX287">(287)</A>
+</li>
+<li>Consistency
+<ul class="indexlist">
+<li>checking database
+<A HREF="hubprnt38.html#IDX249">(249)</A>
+</li>
+</ul>
+</li>
+<li>Creating a Database From a Backup Copy
+<A HREF="hubprnt45.html#IDX258">(258)</A>
+</li>
+<li>derby.jar
+<A HREF="hubprnt13.html#IDX182">(182)</A>
+</li>
+<li>dblook
+<ul class="indexlist">
+<li>using with Network Server
+<A HREF="hubprnt18.html#IDX191">(191)</A>
+</li>
+</ul>
+</li>
+<li>derbynet.jar
+<A HREF="hubprnt13.html#IDX181">(181)</A>
+</li>
+</ul>
+<strong><a href="#IDX0_44">D</a></strong>
+<ul class="indexlist">
+<li>db2jcc.jar
+<A HREF="hubprnt13.html#IDX183">(183)</A>
+</li>
+<li>db2jcc_license_c.jar
+<A HREF="hubprnt13.html#IDX184">(184)</A>
+</li>
+<li>Deadlock
+<ul class="indexlist">
+<li>tools to help minimize
+<A HREF="hubprnt56.html#IDX274">(274)</A>
+</li>
+</ul>
+</li>
+</ul>
+<strong><a href="#IDX0_45">E</a></strong>
+<ul class="indexlist">
+<li>Encrypted databases
+<ul class="indexlist">
+<li>backing up
+<A HREF="hubprnt43.html#IDX256">(256)</A>
+</li>
+</ul>
+</li>
+<li>Encrypted UserID and password
+<ul class="indexlist">
+<li>using with Network Server
+<A HREF="hubprnt19.html#IDX204">(204)</A>
+</li>
+</ul>
+</li>
+<li>Error messages
+<ul class="indexlist">
+<li>and the Network Server
+<A HREF="hubprnt19.html#IDX196">(196)</A>
+</li>
+</ul>
+</li>
+</ul>
+<strong><a href="#IDX0_49">I</a></strong>
+<ul class="indexlist">
+<li>IBM Java Cryptography Extension (JCE)
+<A HREF="hubprnt19.html#IDX205">(205)</A>
+</li>
+<li>ibmjcefw.jar
+<A HREF="hubprnt19.html#IDX207">(207)</A>
+</li>
+<li>ibmjceprovider.jar
+<A HREF="hubprnt19.html#IDX206">(206)</A>
+</li>
+<li>ibmpkderby.jar
+<A HREF="hubprnt19.html#IDX208">(208)</A>
+</li>
+<li>ibmpkcs11.jar
+<A HREF="hubprnt19.html#IDX209">(209)</A>
+</li>
+<li>ij
+<ul class="indexlist">
+<li>using with Network Server
+<A HREF="hubprnt18.html#IDX189">(189)</A>
+</li>
+</ul>
+</li>
+<li>Isolation levels
+<A HREF="hubprnt09.html#IDX178">(178)</A>
+</li>
+</ul>
+<strong><a href="#IDX0_4A">J</a></strong>
+<ul class="indexlist">
+<li>JVMs
+<ul class="indexlist">
+<li>compatibility with Network Server
+<A HREF="hubprnt22.html#IDX212">(212)</A>
+</li>
+</ul>
+</li>
+</ul>
+<strong><a href="#IDX0_4C">L</a></strong>
+<ul class="indexlist">
+<li>Locking
+<ul class="indexlist">
+<li>row-level
+<A HREF="hubprnt09.html#IDX177">(177)</A>
+</li>
+<li>table-level
+<A HREF="hubprnt09.html#IDX175">(175)</A>
+</li>
+</ul>
+</li>
+<li>Locks
+<ul class="indexlist">
+<li>monitoring
+<A HREF="hubprnt56.html#IDX273">(273)</A>
+</li>
+</ul>
+</li>
+<li>Log
+<ul class="indexlist">
+<li>default location for
+<A HREF="hubprnt51.html#IDX270">(270)</A>
+</li>
+</ul>
+</li>
+<li>logDevice
+<A HREF="hubprnt52.html#IDX271">(271)</A>
+</li>
+<li>Logging transactions
+<A HREF="hubprnt51.html#IDX268">(268)</A>
+</li>
+</ul>
+<strong><a href="#IDX0_4D">M</a></strong>
+<ul class="indexlist">
+<li>Multi-threading
+<ul class="indexlist">
+<li>and JDBC
+<A HREF="hubprnt09.html#IDX180">(180)</A>
+</li>
+</ul>
+</li>
+<li>Multiple connections
+<ul class="indexlist">
+<li>from single application running in embedded mode
+<A HREF="hubprnt09.html#IDX179">(179)</A>
+</li>
+</ul>
+</li>
+</ul>
+<strong><a href="#IDX0_4E">N</a></strong>
+<ul class="indexlist">
+<li>Network Server
+<ul class="indexlist">
+<li>and JVM compatibility
+<A HREF="hubprnt22.html#IDX213">(213)</A>
+</li>
+<li>and security changes
+<A HREF="hubprnt29.html#IDX236">(236)</A>
+</li>
+<li>class path and
+<A HREF="hubprnt22.html#IDX215">(215)</A>
+</li>
+<li>Derby features unsupported in
+<A HREF="hubprnt19.html#IDX193">(193)</A>
+</li>
+<li>dblook and
+<A HREF="hubprnt18.html#IDX192">(192)</A>
+</li>
+<li>error messages and
+<A HREF="hubprnt19.html#IDX195">(195)</A>
+</li>
+<li>ij and
+<A HREF="hubprnt18.html#IDX190">(190)</A>
+</li>
+<li>NsSample sample program
+<A HREF="hubprnt35.html#IDX245">(245)</A>
+</li>
+<li>properties
+<A HREF="hubprnt23.html#IDX218">(218)</A>
+</li>
+<li>running under security manager
+<A HREF="hubprnt30.html#IDX237">(237)</A>
+</li>
+<li>sample programs for embedded and client connections
+<A HREF="hubprnt36.html#IDX246">(246)</A>
+</li>
+<li>setting port numbers for
+<A HREF="hubprnt20.html#IDX210">(210)</A>
+</li>
+<li>shutting down
+<A HREF="hubprnt25.html#IDX230">(230)</A>
+</li>
+<li>starting
+<A HREF="hubprnt14.html#IDX186">(186)</A>
+</li>
+<li>starting from a command line
+<A HREF="hubprnt14.html#IDX187">(187)</A>
+</li>
+<li>starting from the API
+<A HREF="hubprnt14.html#IDX188">(188)</A>
+</li>
+<li>supported security properties
+<A HREF="hubprnt19.html#IDX201">(201)</A>
+</li>
+<li>trace facility
+<A HREF="hubprnt33.html#IDX242">(242)</A>
+</li>
+<li>user authentication and
+<A HREF="hubprnt19.html#IDX198">(198)</A>
+</li>
+<li>verifying startup
+<A HREF="hubprnt24.html#IDX228">(228)</A>
+</li>
+</ul>
+</li>
+<li>Network Server Security
+<A HREF="hubprnt29.html#IDX235">(235)</A>
+</li>
+<li>NetworkServerControl API
+<ul class="indexlist">
+<li>NetworkServerControl class and
+<A HREF="hubprnt22.html#IDX217">(217)</A>
+</li>
+</ul>
+</li>
+<li>NetworkServerControl class
+<A HREF="hubprnt22.html#IDX216">(216)</A>
+</li>
+</ul>
+<strong><a href="#IDX0_4F">O</a></strong>
+<ul class="indexlist">
+<li>Online Archived Logs
+<A HREF="hubprnt46.html#IDX260">(260)</A>
+<ul class="indexlist">
+<li>Disabling
+<A HREF="hubprnt46.html#IDX262">(262)</A>
+</li>
+<li>Enabling
+<A HREF="hubprnt46.html#IDX261">(261)</A>
+</li>
+</ul>
+</li>
+</ul>
+<strong><a href="#IDX0_50">P</a></strong>
+<ul class="indexlist">
+<li>Port numbers
+<ul class="indexlist">
+<li>Network Server and
+<A HREF="hubprnt20.html#IDX211">(211)</A>
+</li>
+</ul>
+</li>
+<li>Properties
+<ul class="indexlist">
+<li>Network Server
+<A HREF="hubprnt23.html#IDX219">(219)</A>
+</li>
+</ul>
+</li>
+<li>Protecting Log Files
+<A HREF="hubprnt46.html#IDX263">(263)</A>
+</li>
+</ul>
+<strong><a href="#IDX0_52">R</a></strong>
+<ul class="indexlist">
+<li>Restoring a database
+<A HREF="hubprnt47.html#IDX264">(264)</A>
+</li>
+<li>Row-level locking
+<A HREF="hubprnt09.html#IDX176">(176)</A>
+</li>
+</ul>
+<strong><a href="#IDX0_53">S</a></strong>
+<ul class="indexlist">
+<li>Sample programs for Network Server
+<A HREF="hubprnt34.html#IDX244">(244)</A>
+</li>
+<li>Security properties
+<ul class="indexlist">
+<li>supported by Network Server
+<A HREF="hubprnt19.html#IDX200">(200)</A>
+</li>
+</ul>
+</li>
+<li>service.properties file
+<ul class="indexlist">
+<li>setting logDevice in
+<A HREF="hubprnt52.html#IDX272">(272)</A>
+</li>
+</ul>
+</li>
+<li>Shutting down Network Server
+<ul class="indexlist">
+<li>from scripts
+<A HREF="hubprnt25.html#IDX229">(229)</A>
+</li>
+<li>from the API
+<A HREF="hubprnt25.html#IDX232">(232)</A>
+</li>
+<li>from the command line
+<A HREF="hubprnt25.html#IDX231">(231)</A>
+</li>
+<li>using servlet interface
+<A HREF="hubprnt27.html#IDX234">(234)</A>
+</li>
+</ul>
+</li>
+<li>SimpleNetworkClientSample program
+<A HREF="hubprnt36.html#IDX248">(248)</A>
+</li>
+<li>SimpleNetworkServerSample program
+<A HREF="hubprnt36.html#IDX247">(247)</A>
+</li>
+<li>Space
+<ul class="indexlist">
+<li>reclaiming
+<A HREF="hubprnt59.html#IDX285">(285)</A>
+</li>
+</ul>
+</li>
+<li>Starting Network Server
+<ul class="indexlist">
+<li>from scripts
+<A HREF="hubprnt14.html#IDX185">(185)</A>
+</li>
+<li>from the servlet interface
+<A HREF="hubprnt27.html#IDX233">(233)</A>
+</li>
+</ul>
+</li>
+<li>SYSCS_UTIL.SYSCS_BACKUP_DATABASE() system procedure
+<A HREF="hubprnt43.html#IDX253">(253)</A>
+</li>
+<li>SYSCS_UTIL.SYSCS_FREEZE_DATABASE system procedure
+<A HREF="hubprnt43.html#IDX254">(254)</A>
+</li>
+<li>SYSCS_UTIL.SYSCS_UNFREEZE_DATABASE system procedure
+<A HREF="hubprnt43.html#IDX255">(255)</A>
+</li>
+</ul>
+<strong><a href="#IDX0_54">T</a></strong>
+<ul class="indexlist">
+<li>Table-level locking
+<A HREF="hubprnt09.html#IDX174">(174)</A>
+</li>
+<li>Trace facility
+<ul class="indexlist">
+<li>for the Network Server
+<A HREF="hubprnt33.html#IDX243">(243)</A>
+</li>
+</ul>
+</li>
+<li>Transaction log
+<ul class="indexlist">
+<li>putting on separate device
+<A HREF="hubprnt51.html#IDX269">(269)</A>
+</li>
+</ul>
+</li>
+</ul>
+<strong><a href="#IDX0_55">U</a></strong>
+<ul class="indexlist">
+<li>User authentication
+<ul class="indexlist">
+<li>and Network Server
+<A HREF="hubprnt19.html#IDX197">(197)</A>
+</li>
+</ul>
+</li>
+</ul>
+<strong><a href="#IDX0_58">X</a></strong>
+<ul class="indexlist">
+<li>XA
+<ul class="indexlist">
+<li>and Network Server
+<A HREF="hubprnt19.html#IDX194">(194)</A>
+</li>
+</ul>
+</li>
+</ul>
+<P><HR>[ <A HREF="hubprnt64.html">Previous Page</A><br><A HREF="hubprnt02.html#ToC">Table of Contents</A><br><A HREF="#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,27 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Developer's Guide</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+<H1>Developer's Guide</H1>
+<BR>
+<P><B>First Edition (August 2004)</B>
+<P><B>(C) Copyright International Business Machines Corporation 1997, 2004. All rights reserved.</B> <BR>U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
+<P>
+<P><HR>[ <A HREF="develop02.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop02.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop02.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,249 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Contents</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+<H1>Developer's Guide</H1>
+<BR>
+<HR><H1><A NAME="ToC">Contents</H1>
+<P><A HREF="develop03.html#HDRSII-DGPREF-29520">About This Document</A><BR>
+<MENU>
+<LI><A HREF="develop04.html#HDRSII-DGPREF-11181">Purpose of This Document</A>
+<LI><A HREF="develop05.html#HDRSII-DGPREF-24290">Audience</A>
+<LI><A HREF="develop06.html#HDRSII-DGPREF-23947">How This Document Is Organized</A>
+</MENU>
+<P><A HREF="develop07.html#HDRSII-DEVELOP-19524">JDBC Applications and Derby Basics</A><BR>
+<MENU>
+<LI><A HREF="develop08.html#HDRSII-DEVELOP-14839">Application Development Overview</A>
+<LI><A HREF="develop09.html#HDRSII-DEVELOP-39409">Derby Embedded Basics</A>
+<MENU>
+<LI><A HREF="develop10.html#HDRSII-DEVELOP-40653">Derby JDBC Driver</A>
+<LI><A HREF="develop11.html#HDRSII-DEVELOP-17453">Derby JDBC Database Connection URL</A>
+<LI><A HREF="develop12.html#HDRSII-DEVELOP-27610">Derby System</A>
+<LI><A HREF="develop13.html#HDRSII-DEVELOP-21955">A Derby Database</A>
+<LI><A HREF="develop14.html#HDRSII-DEVELOP-34964">Connecting to Databases</A>
+<LI><A HREF="develop15.html#HDRSII-DEVELOP-51654">Working with the Database Connection URL Attributes</A>
+</MENU></MENU>
+<P><A HREF="develop16.html#HDRSII-START-19524">After Installing</A><BR>
+<MENU>
+<LI><A HREF="develop17.html#HDRSII-START-16043">The Installation Directory</A>
+<MENU>
+<LI><A HREF="develop18.html#HDRSTART813142">Batch Files and Shell Scripts</A>
+</MENU>
+<LI><A HREF="develop19.html#HDRSII-START-18978">Derby and JVMs</A>
+<LI><A HREF="develop20.html#HDRSII-START-98282">Derby Libraries and Class Path</A>
+<LI><A HREF="develop21.html#HDRSII-START-41260">UNIX-Specific Issues</A>
+<MENU>
+<LI><A HREF="develop22.html#HDRSII-START-39409">Configuring File Descriptors</A>
+<LI><A HREF="develop23.html#HDRSTART813545">Scripts</A>
+</MENU></MENU>
+<P><A HREF="develop24.html#HDRSII-DEVELOP-25174">Derby Embedded Basics</A><BR>
+<MENU>
+<LI><A HREF="develop25.html#HDRSII-DEVELOP-40170">Embedded Derby JDBC Driver</A>
+<LI><A HREF="develop26.html#HDRSII-DEVELOP-38881">Embedded Derby JDBC Database Connection URL</A>
+<LI><A HREF="develop27.html#HDRSII-DEVELOP-10252">Getting a Nested Connection</A>
+<LI><A HREF="develop28.html#HDRSII-DEVELOP-38381">Starting Derby as an Embedded Database</A>
+</MENU>
+<P><A HREF="develop29.html#HDRSII-DEPLOY-32171">Deploying Derby Applications</A><BR>
+<MENU>
+<LI><A HREF="develop30.html#HDRSII-DEPLOY-38918">Deployment Issues</A>
+<MENU>
+<LI><A HREF="develop31.html#HDRDEPLOY855368">Embedded Deployment Application Overview</A>
+<LI><A HREF="develop32.html#HDRSII-DEPLOY-37603">Deployment Cheat Sheets</A>
+</MENU>
+<LI><A HREF="develop33.html#HDRSII-DEPLOY-15325">Creating Derby Databases for Read-Only Use</A>
+<MENU>
+<LI><A HREF="develop34.html#HDRSII-DEPLOY-26887">Creating and Preparing the Database for Read-Only Use</A>
+<LI><A HREF="develop35.html#HDRSII-DEPLOY-19136">Deploying the Database on the Read-Only Media</A>
+<LI><A HREF="develop36.html#HDRSII-DEPLOY-33704">Transferring Read-Only Databases to Archive (Jar or Zip) Files</A>
+<LI><A HREF="develop37.html#HDRSII-DEPLOY-11201">Accessing a Read-Only Database in a Zip/Jar</A>
+<LI><A HREF="develop38.html#HDRSII-DEPLOY-39856">Accessing Databases-in-a-Jar in the Class Path</A>
+<LI><A HREF="develop39.html#HDRSII-DEPLOY-82529">Databases on Read-Only Media and DatabaseMetaData</A>
+</MENU>
+<LI><A HREF="develop40.html#HDRSII-DEPLOY-30736">Loading Classes from a Database</A>
+<MENU>
+<LI><A HREF="develop41.html#HDRDEPLOY856753">Class Loading Overview</A>
+<LI><A HREF="develop42.html#HDRSII-DEPLOY-15818">Create Jar Files for Your Application</A>
+<LI><A HREF="develop43.html#HDRSII-DEPLOY-23812">Add the jar file or files to the database</A>
+<LI><A HREF="develop44.html#HDRSII-DEPLOY-21645">Enable database class loading with a property</A>
+<LI><A HREF="develop45.html#HDRSII-DEPLOY-12748">Code your applications the way you normally would</A>
+<LI><A HREF="develop46.html#HDRSII-DEPLOY-17604">Dynamic Changes to Jar Files or Database Jar Class Path</A>
+</MENU></MENU>
+<P><A HREF="develop47.html#Header_87">Derby server-side programming</A><BR>
+<MENU>
+<LI><A HREF="develop48.html#HDRSII-SPECIAL-42117">Programming Database-Side JDBC Procedures</A>
+<MENU>
+<LI><A HREF="develop49.html#HDRSII-SPECIAL-27988">Overview</A>
+<LI><A HREF="develop50.html#HDRSII-SPECIAL-29620">Database-Side JDBC Procedures and Nested Connections</A>
+<LI><A HREF="develop51.html#HDRSII-SPECIAL-16181">Database-Side JDBC Procedures Using Non-Nested Connections</A>
+<LI><A HREF="develop52.html#HDRSII-SPECIAL-41728">Database-Side JDBC Procedures and SQLExceptions</A>
+<LI><A HREF="develop53.html#HDRSII-SPECIAL-45786">User-Defined SQLExceptions</A>
+</MENU>
+<LI><A HREF="develop54.html#HDRSII-SPECIAL-27163">Programming Trigger Actions</A>
+<MENU>
+<LI><A HREF="develop55.html#HDRSII-SPECIAL-53165">Trigger Action Overview</A>
+<LI><A HREF="develop56.html#HDRSII-SPECIAL-76763">Performing Referential Actions</A>
+<LI><A HREF="develop57.html#HDRSII-SPECIAL-67260">Accessing Before and After Rows</A>
+<LI><A HREF="develop58.html#HDRSII-SPECIAL-13670">Examples</A>
+<LI><A HREF="develop59.html#HDRSII-SPECIAL-49460">Triggers and Exceptions</A>
+</MENU></MENU>
+<P><A HREF="develop60.html#HDRSII-CONCEPTS-19524">Controlling Derby Application Behavior</A><BR>
+<MENU>
+<LI><A HREF="develop61.html#HDRSII-CONCEPTS-38375">The JDBC Connection and Transaction Model</A>
+<MENU>
+<LI><A HREF="develop62.html#HDRSII-CONCEPTS-36881">Connections</A>
+<LI><A HREF="develop63.html#HDRSII-CONCEPTS-19173">Transactions</A>
+</MENU>
+<LI><A HREF="develop64.html#HDRSII-CONCEPTS-41275">SQL and JDBC ResultSet/Cursor Mechanisms</A>
+<MENU>
+<LI><A HREF="develop65.html#HDRSII-CONCEPTS-88082">Simple Non-Updatable ResultSets</A>
+<LI><A HREF="develop66.html#HDRSII-CONCEPTS-28351">Updatable Cursors</A>
+<LI><A HREF="develop67.html#HDRSII-CONCEPTS-23987">ResultSets and Auto-Commit</A>
+<LI><A HREF="develop68.html#HDRSII-CONCEPTS-22641">Scrolling Insensitive ResultSets</A>
+<LI><A HREF="develop69.html#HDRSII-CONCEPTS-HOLDABLECURSORS">Holdable Cursors</A>
+</MENU>
+<LI><A HREF="develop70.html#HDRSII-CONCEPTS-30291">Locking, Concurrency, and Isolation</A>
+<MENU>
+<LI><A HREF="develop71.html#HDRSII-CONCEPTS-15366">Isolation Levels and Concurrency</A>
+<LI><A HREF="develop72.html#HDRSII-CONCEPTS-22300">Configuring Isolation Levels</A>
+<LI><A HREF="develop73.html#HDRSII-CONCEPTS-23810">Lock Granularity</A>
+<LI><A HREF="develop74.html#HDRSII-CONCEPTS-36402">Types and Scope of Locks in Derby Systems</A>
+<LI><A HREF="develop75.html#HDRSII-CONCEPTS-28436">Deadlocks</A>
+</MENU>
+<LI><A HREF="develop76.html#HDRSII-CONCEPTS-34828">Working with Multiple Connections to a Single Database</A>
+<MENU>
+<LI><A HREF="develop77.html#HDRSII-CONCEPTS-35713">Deployment Options and Threading and Connection Modes</A>
+<LI><A HREF="develop78.html#HDRSII-CONCEPTS-10914">Multi-User Database Access</A>
+<LI><A HREF="develop79.html#HDRSII-CONCEPTS-24019">Multiple Connections from a Single Application</A>
+</MENU>
+<LI><A HREF="develop80.html#HDRSII-CONCEPTS-23499">Working with Multiple Threads Sharing a Single Connection</A>
+<MENU>
+<LI><A HREF="develop81.html#HDRSII-CONCEPTS-89498">Pitfalls of Sharing a Connection Among Threads</A>
+<LI><A HREF="develop82.html#HDRSII-CONCEPTS-65864">Multi-thread programming tips</A>
+<LI><A HREF="develop83.html#HDRSII-CONCEPTS-91600">Threads Sharing a Statement: A Case Study</A>
+</MENU>
+<LI><A HREF="develop84.html#HDRSII-DEVELOP-22619">Working with Database Threads in an Embedded Environment</A>
+<LI><A HREF="develop85.html#HDRSII-CONCEPTS-24927">Working with Derby SQLExceptions in an Application</A>
+<MENU>
+<LI><A HREF="develop86.html#HDRCONCEPTS844813">Information Provided in SQLExceptions</A>
+</MENU></MENU>
+<P><A HREF="develop87.html#HDRSII-RESMAN-19524">Using Derby as a J2EE Resource Manager</A><BR>
+<MENU>
+<LI><A HREF="develop88.html#HDRSII-RESMAN-79556">The Classes Pertaining to Resource Managers</A>
+<LI><A HREF="develop89.html#HDRSII-RESMAN-78715">How to Use Them</A>
+<MENU>
+<LI><A HREF="develop90.html#HDRSII-RESMAN-89722">Getting a DataSource</A>
+<LI><A HREF="develop91.html#HDRSII-RESMAN-92946">Shutting Down or Creating a Database</A>
+</MENU></MENU>
+<P><A HREF="develop92.html#Header_161">Derby and Security</A><BR>
+<MENU>
+<LI><A HREF="develop93.html#HDRSII-CSECUR-33663">Security Overview</A>
+<MENU>
+<LI><A HREF="develop94.html#HDRCSECUR862382">Features</A>
+<LI><A HREF="develop95.html#HDRSII-CSECUR-12392">Configuring Security for Your Environment</A>
+</MENU>
+<LI><A HREF="develop96.html#HDRSII-CSECUR-42374">Working with User Authentication</A>
+<MENU>
+<LI><A HREF="develop97.html#HDRSII-CSECUR-30032">Overview</A>
+<LI><A HREF="develop98.html#HDRSII-CSECUR-36127">Enabling User Authentication</A>
+<LI><A HREF="develop99.html#HDRSII-CSECUR-37817">Defining Users</A>
+<LI><A HREF="develop100.html#HDRSII-CSECUR-38522">External Directory Service</A>
+<LI><A HREF="develop101.html#HDRSII-CSECUR-21547">Built-in Derby Users</A>
+<LI><A HREF="develop102.html#HDRSII-CSECUR-32557">Properties Summary</A>
+<LI><A HREF="develop103.html#HDRSII-CSECUR-79358">Programming Applications for Derby User Authentication</A>
+</MENU>
+<LI><A HREF="develop104.html#HDRSII-CSECUR-37241">Users and Authorization Identifiers</A>
+<MENU>
+<LI><A HREF="develop105.html#HDRSII-CSECUR-24458">Authorization Identifiers, User Authentication, and User Authorization</A>
+<LI><A HREF="develop106.html#HDRCSECUR865580">User Names and Schemas</A>
+<LI><A HREF="develop107.html#HDRCSECUR865622">Exceptions</A>
+</MENU>
+<LI><A HREF="develop108.html#HDRSII-CSECUR-36595">User Authorization</A>
+<MENU>
+<LI><A HREF="develop109.html#HDRCSECUR866060">Setting User Authorization</A>
+<LI><A HREF="develop110.html#HDRCSECUR866190">About Read-Only and Full Access</A>
+<LI><A HREF="develop111.html#HDRSII-CSECUR-79131">Examples</A>
+</MENU>
+<LI><A HREF="develop112.html#HDRSII-CSECUR-24366">Encrypting Databases on Disk</A>
+<MENU>
+<LI><A HREF="develop113.html#HDRSII-CSECUR-99212">Overview</A>
+<LI><A HREF="develop114.html#HDRSII-CSECUR-96815">Requirements for Derby Encryption</A>
+<LI><A HREF="develop115.html#HDRSII-CSECUR-97760">Working with Encryption</A>
+</MENU>
+<LI><A HREF="develop116.html#HDRSII-CSECUR-90988">Signed Jar Files</A>
+<LI><A HREF="develop117.html#HDRSII-CSECUR-10983">Notes on the Derby Security Features</A>
+<LI><A HREF="develop118.html#HDRSII-CSECUR-51876">User Authentication and Authorization Examples</A>
+<MENU>
+<LI><A HREF="develop119.html#HDRSII-CSECUR-18108">Client/Server Environment</A>
+<LI><A HREF="develop120.html#HDRSII-CSECUR-13713">Single-User, Embedded Environment</A>
+</MENU>
+<LI><A HREF="develop121.html#HDRBABEJDFJ">Running Derby under a security manager</A>
+<MENU>
+<LI><A HREF="develop122.html#HDRBABEJGJD">Granting Permissions to Derby</A>
+<LI><A HREF="develop123.html#HDRCSECUR871387">Examples of Java 2 Security Policy Files for embedded Derby</A>
+</MENU></MENU>
+<P><A HREF="develop124.html#HDRSII-ADVJDBC-35053">Developing Tools and Using Derby with an IDE</A><BR>
+<MENU>
+<LI><A HREF="develop125.html#HDRSII-ADVJDBC-41138">Offering Connection Choices to the User</A>
+<MENU>
+<LI><A HREF="develop126.html#HDRADVJDBC814034">The DriverPropertyInfo Array</A>
+</MENU>
+<LI><A HREF="develop127.html#HDRSII-ADVJDBC-32436">Using Derby with IDEs</A>
+<MENU>
+<LI><A HREF="develop128.html#HDRSII-ADVJDBC-18939">IDEs and Multiple JVMs</A>
+</MENU></MENU>
+<P><A HREF="develop129.html#HDRSII-TRICKS-32436">SQL Tips</A><BR>
+<MENU>
+<LI><A HREF="develop130.html#HDRSII-TRICKS-19707">Retrieving the Database Connection URL</A>
+<LI><A HREF="develop131.html#HDRSII-TRICKS-39584">Supplying a Parameter Only Once</A>
+<LI><A HREF="develop132.html#HDRSII-TRICKS-21248">Defining an Identity Column</A>
+<LI><A HREF="develop133.html#HDRSII-TRICKS-23426">Using Third-Party Tools</A>
+<LI><A HREF="develop134.html#HDRSII-TRICKS-13019">Tricks of the VALUES Clause</A>
+<MENU>
+<LI><A HREF="develop135.html#HDRTRICKS807337">Multiple Rows</A>
+<LI><A HREF="develop136.html#HDRTRICKS807365">Mapping Column Values to Return Values</A>
+<LI><A HREF="develop137.html#HDRTRICKS807400">Creating Empty Queries</A>
+</MENU></MENU>
+<P><A HREF="develop138.html#HDRSII-I18N-10613">Localizing Derby</A><BR>
+<MENU>
+<LI><A HREF="develop139.html#HDRSII-I18N-71274">SQL Parser Support for Unicode</A>
+</MENU>
+<P><A HREF="develop140.html#HDRSTNDRDS806118">Derby and Standards</A><BR>
+<MENU>
+<LI><A HREF="develop141.html#HDRSTNDRDS806055">SQL99</A>
+<MENU>
+<LI><A HREF="develop142.html#HDRSTNDRDS805644">Dynamic SQL</A>
+<LI><A HREF="develop143.html#HDRSTNDRDS805664">Cursors</A>
+<LI><A HREF="develop144.html#HDRSTNDRDS805690">Information Schema</A>
+<LI><A HREF="develop145.html#HDRSTNDRDS805716">Transactions</A>
+<LI><A HREF="develop146.html#HDRSTNDRDS805742">Stored routines and PSM</A>
+<LI><A HREF="develop147.html#HDRSTNDRDS805768">Calling functions and procedures</A>
+<LI><A HREF="develop148.html#HDRSTNDRDS805841">Unique constraints and nulls</A>
+<LI><A HREF="develop149.html#HDRSTNDRDS805893">NOT NULL characteristic</A>
+<LI><A HREF="develop150.html#HDRSTNDRDS805921">Fewer reserved keywords</A>
+<LI><A HREF="develop151.html#HDRSTNDRDS805949">DECIMAL max precision</A>
+<LI><A HREF="develop152.html#HDRSTNDRDS805975">CLOB, and BLOB</A>
+<LI><A HREF="develop153.html#HDRSTNDRDS806001">Expressions on LONGs</A>
+<LI><A HREF="develop154.html#HDRSTNDRDS806027">ALTER TABLE</A>
+</MENU></MENU>
+<P><A HREF="develop156.html#HDRTRADEM">Trademarks</A>
+<P><A HREF="develop157.html#HDRINDEX_START">Index</A><BR>
+<P>
+<P>
+<P><HR>[ <A HREF="develop.html">Previous Page</A><br><A HREF="develop03.html">Next Page</A><br><A HREF="#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop03.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop03.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,32 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>About This Document</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<HR><H1 NAME="HDRSII-DGPREF-29520">About This Document</H1>
+<UL>
+<LI><A HREF="develop04.html#HDRSII-DGPREF-11181">"Purpose of This Document"</A>
+</LI><LI><A HREF="develop05.html#HDRSII-DGPREF-24290">"Audience"</A>
+</LI><LI><A HREF="develop06.html#HDRSII-DGPREF-23947">"How This Document Is Organized"</A>
+</LI></UL>
+<P>For general information about the Derby documentation, such as a
+complete list of books, conventions, and further reading, see <CITE>Getting
+Started with Derby</CITE>.
+<P><HR>[ <A HREF="develop02.html">Previous Page</A><br><A HREF="develop04.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop04.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop04.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,28 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Purpose of This Document</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<HR><H1 NAME="HDRSII-DGPREF-11181">Purpose of This Document</H1>
+<P>This book explains how to use the core Derby technology and is for
+developers building Derby applications. It describes basic
+Derby concepts, such as how you create and access Derby databases
+through JDBC procedures and how you can deploy Derby applications.
+<P><HR>[ <A HREF="develop03.html">Previous Page</A><br><A HREF="develop05.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop05.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop05.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,28 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Audience</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<HR><H1 NAME="HDRSII-DGPREF-24290">Audience</H1>
+<P>This book is intended for software developers who already know some SQL and
+Java. Derby users who are not familiar with the SQL standard or
+the Java programming language will benefit from consulting books on those
+subjects.
+<P><HR>[ <A HREF="develop04.html">Previous Page</A><br><A HREF="develop06.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop06.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop06.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,47 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>How This Document Is Organized</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<HR><H1 NAME="HDRSII-DGPREF-23947">How This Document Is Organized</H1>
+<P>This document includes the following chapters:
+<UL>
+<LI><A HREF="develop07.html#HDRSII-DEVELOP-19524">"JDBC Applications and Derby Basics"</A> 
+<P>Basic details for using Derby, including loading the JDBC driver,
+specifying a database URL, and starting Derby.
+</LI><LI><A HREF="develop16.html#HDRSII-START-19524">"After Installing"</A> 
+<P>Explains the installation layout.
+</LI><LI><A HREF="develop29.html#HDRSII-DEPLOY-32171">"Deploying Derby Applications"</A> 
+<P>An overview of different deployment scenarios, and tips for getting the
+details right when deploying applications.
+</LI><LI><A HREF="develop60.html#HDRSII-CONCEPTS-19524">"Controlling Derby Application Behavior"</A> 
+<P>JDBC, cursors, locking and isolation levels, and multiple
+connections.
+</LI><LI><A HREF="develop87.html#HDRSII-RESMAN-19524">"Using Derby as a J2EE Resource Manager"</A> 
+<P>Information for programmers developing back-end components in a J2EE
+system.
+</LI><LI><A HREF="develop124.html#HDRSII-ADVJDBC-35053">"Developing Tools and Using Derby with an IDE"</A> 
+<P>Tips for tool designers.
+</LI><LI><A HREF="develop129.html#HDRSII-TRICKS-32436">"SQL Tips"</A> 
+<P>Insiders' tricks of the trade for using SQL.
+</LI><LI><A HREF="develop138.html#HDRSII-I18N-10613">Localizing Derby</A> 
+<P>An overview of database localization.
+</LI></UL>
+<P><HR>[ <A HREF="develop05.html">Previous Page</A><br><A HREF="develop07.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop07.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop07.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,27 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>JDBC Applications and Derby Basics</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<HR><H1 NAME="HDRSII-DEVELOP-19524">JDBC Applications and Derby Basics</H1>
+<P>This chapter describes the core Derby functionality. In
+addition, it details the most basic Derby deployment, Derby embedded
+in a Java application.
+<P><HR>[ <A HREF="develop06.html">Previous Page</A><br><A HREF="develop08.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop08.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop08.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,62 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Application Development Overview</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="tutorial for, JDBC">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<HR><H1 NAME="HDRSII-DEVELOP-14839">Application Development Overview</H1>
+<P>Derby application developers use JDBC, the application programming
+interface that makes it possible to access relational databases from Java
+programs. The JDBC API is part of the Java<SUP>(TM)</SUP>2 Platform, Standard
+Edition and is not specific to Derby. It consists of the
+<I>java.sql</I> and <I>javax.sql</I> packages, which is
+a set of classes and interfaces that make it possible to access databases
+(from a number of different vendors, not just Derby) from a Java
+application.
+<P>
+<A NAME="IDX502"></A>
+To develop Derby applications successfully, you will need to learn
+JDBC. This chapter does not teach you how to program with the JDBC
+API.
+<P>This chapter covers the details of application programming that are
+specific to Derby applications. For example, all JDBC applications
+typically start their DBMS's JDBC driver and use a connection URL to
+connect to a database. This chapter gives you the details of how to
+start Derby's JDBC driver and how to work with Derby's
+connection URL to accomplish various tasks. It also covers essential
+Derby concepts such as the Derby system.
+<P>You will find reference information about the particulars of
+Derby's implementation of JDBC in the <CITE>Derby Reference
+Manual</CITE>.
+<P>Derby application developers will need to learn SQL.
+<I>SQL</I> is the standard query language used with relational databases
+and is not tied to a particular programming language. No matter how a
+particular RDBMS has been implemented, the user can design databases and
+insert, modify, and retrieve data using the standard SQL statements and
+well-defined data types. SQL-92 is the version of SQL standardized by
+ANSI and ISO in 1992; Derby supports entry-level SQL-92 as well as
+some higher-level features. Entry-level SQL-92 is a subset of full
+SQL-92 specified by ANSI and ISO that is supported by nearly all major DBMSs
+today. This chapter does not teach you SQL. You will find
+reference information about the particulars of Derby's implementation
+of SQL in the <CITE>Derby Reference Manual</CITE>.
+<P>Derby implements JDBC that allows Derby to serve a resource
+manager in a J2EE compliant system.
+<P><HR>[ <A HREF="develop07.html">Previous Page</A><br><A HREF="develop09.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop09.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop09.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,26 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Derby Embedded Basics</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<HR><H1 NAME="HDRSII-DEVELOP-39409">Derby Embedded Basics</H1>
+<P>This section discusses the basics of the Derby
+database.
+<P><HR>[ <A HREF="develop08.html">Previous Page</A><br><A HREF="develop10.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop10.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop10.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,42 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Derby JDBC Driver</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="description, JDBC driver">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-DEVELOP-40653">Derby JDBC Driver</H1>
+<A NAME="IDX503"></A>
+<P>Derby consists of both the database engine and an embedded JDBC
+driver. Applications use JDBC to interact with a database.
+Applications must load the driver in order to work with the database.
+<P>In an embedded environment, loading the driver also starts
+Derby.
+<P>In a Java application, you typically load the driver with the static
+<I>Class.forName</I> method or with the
+<TT><I>jdbc.drivers</I></TT> system property. For
+example:
+<PRE>Class.forName("org.apache.derby.jdbc.EmbeddedDriver");
+ 
+</PRE>
+<P>For detailed information about loading the Derby JDBC driver, see
+<I>&quot;java.sql.Driver&quot; </I> in the <CITE>Derby
+Reference Manual</CITE><CITE>.</CITE> See also javadoc for
+org.apache.derby.util.DriverUtil.
+<P><HR>[ <A HREF="develop09.html">Previous Page</A><br><A HREF="develop11.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop100.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop100.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,351 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>External Directory Service</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="used to provide user authentication, External directory services, use of external directory service for, User authentication, LDAP directory services, required for LDAP user authorization, jndid, ldap.jar, required for LDAP user authentication, providerutil.jar, setting, JNDI properties for user authorization, providing your own, User authorization">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-CSECUR-38522">External Directory Service</H1>
+<A NAME="IDX735"></A>
+<A NAME="IDX736"></A>
+<P>A directory service stores names and attributes of those names. A
+typical use for a directory service is to store user names and passwords for a
+computer system. Derby uses the Java naming and directory
+interface (JNDI) to interact with external directory services that can provide
+authentication of users' names and passwords.
+<P>Derby can use the following services:
+<UL>
+<LI><A HREF="#HDRSII-CSECUR-41285">LDAP Directory Service</A>
+</LI><LI><A HREF="#HDRSII-CSECUR-21561">User-Defined Class</A>
+</LI></UL>
+<P><H1><A NAME="HDRSII-CSECUR-41285">LDAP Directory Service</H1>
+<A NAME="IDX737"></A>
+<P>You can allow Derby to authenticate users against an existing LDAP
+directory service within your enterprise. LDAP (lightweight directory
+access protocol) provides an open directory access protocol running over
+TCP/IP. An LDAP directory service can quickly authenticate a user's
+name and password.
+<P>To use an LDAP directory service, set
+<I>derby.authentication.provider</I> to
+<I>LDAP</I>.
+<P>Examples of LDAP service providers are:
+<UL>
+<LI>Netscape Directory Server 
+<P>Netscape Directory Server is an LDAP directory server. In addition,
+the Netscape Directory Synchronization Service synchronizes entries in a
+Windows NT directory with the entries in Netscape's Directory
+Server. It allows you to use the Windows NT directory as a repository
+for Derby users.
+</LI><LI>UMich slapd (freeware for the UNIX platform from the University of
+Michigan)
+</LI><LI>AE SLAPD for Windows NT, from AEInc
+</LI></UL>
+<P><H1><A NAME="HDRSII-CSECUR-74608">Libraries for LDAP User Authentication</H1>
+<P>To use an LDAP directory service with Derby, you need the following
+libraries in your class path:
+<UL>
+<LI><I>
+<A NAME="IDX738"></A>
+jndi.jar</I> 
+<P>JNDI classes
+</LI><LI><I>
+<A NAME="IDX739"></A>
+ldap.jar</I> 
+<P>LDAP provider from Sun
+</LI><LI><I>
+<A NAME="IDX740"></A>
+providerutil.jar</I> 
+<P>JNDI classes for a provider
+</LI></UL>
+<P>Derby does not provide these libraries; they are available from
+Sun on the JNDI page at Use the 1.1.x versions of these
+libraries, not the 1.2.x versions. You might need to do
+two separate downloads to obtain all the required libraries.
+<P><H1><A NAME="HDRCSECUR863446">Setting Up Derby to Use Your LDAP Directory Service</H1>
+<P>When specifying LDAP as your authentication service, you must specify the
+location of the server and its port number.
+<UL>
+<LI><I>derby.authentication.server</I> 
+<P>Set the property <I>derby.authentication.server</I>
+to the location and port number of the LDAP server. For example: 
+<PRE>derby.authentication.server=godfrey:389
+</PRE>
+</LI></UL>
+<P><H1><A NAME="HDRCSECUR876908">Guest Access to Search for DNs</H1>
+<P>In an LDAP system, users are hierarchically organized in the directory as a
+set of entries. An <I>entry</I> is a set of name-attribute pairs
+identified by a unique name, called a DN (distinguished name). An entry
+is unambiguously identified by a DN, which is the concatenation of selected
+attributes from each entry in the tree along a path leading from the root down
+to the named entry, ordered from right to left. For example, a DN for a
+user might look like this:
+<PRE>cn=mary,ou=People,o=FlyTours.com
+ 
+uid=mary,ou=People,o=FlyTours.com
+</PRE>
+<P>The allowable entries for the name are defined by the entry's
+<I>objectClass</I>.
+<P>An LDAP client can bind to the directory (successfully log in) if it
+provides a user ID and password. The user ID must be a DN, the fully
+qualified list of names and attributes. This means that the user must
+provide a very long name.
+<P>Typically, the user knows only a simple user name (e.g., the
+first part of the DN above, <I>WilliamS</I>). With Derby, you
+do not need the full DN, because an LDAP client (Derby) can go to the
+directory first as a guest or even an anonymous user, search for the full DN,
+then rebind to the directory using the full DN (and thus authenticate the
+user).
+<P>Derby typically initiates a search for a full DN before binding to the
+directory using the full DN for user authentication. Derby does
+not initiate a search in the following cases:
+<UL>
+<LI>You have set
+<I>derby.authentication.ldap.searchFilter</I> to
+<I>derby.user</I>.
+</LI><LI>A user DN has been cached locally for the specific user with the
+<I>derby.user.UserName</I> property.
+</LI></UL>
+<P>For more information, see
+<I>derby.authentication.ldap.searchFilter</I> in
+<CITE>Tuning Derby</CITE>.
+<P>Some systems permit anonymous searches; other require a user DN and
+password. You can specify a user's DN and password for the search
+with the properties listed below. In addition, you can limit the scope
+of the search by specifying a filter (definition of the object class for the
+user) and a base (directory from which to begin the search) with the
+properties listed below.
+<UL>
+<LI><I>derby.authentication.ldap.searchAuthDN
+(optional)</I> 
+<P>Specifies the DN with which to bind (authenticate) to the server when
+searching for user DNs. This parameter is optional if anonymous access
+is supported by your server. If specified, this value must be a DN
+recognized by the directory service, and it must also have the authority to
+search for the entries.
+<P>If not set, it defaults to an anonymous search using the root DN specified
+by the
+<I>derby.authentication.ldap.searchBase</I>
+property. For example:
+<PRE>uid=guest,o=FlyTours.com
+</PRE>
+</LI><LI><I>derby.authentication.ldap.searchAuthPW
+(optional)</I> 
+<P>Specifies the password to use for the guest user configured above to bind
+to the directory service when looking up the DN. If not set, it
+defaults to an anonymous search using the root DN specified by the
+<I>derby.authentication.ldap.searchBase</I>
+property.
+<PRE>myPassword
+</PRE>
+</LI><LI><I>derby.authentication.ldap.searchBase
+(optional)</I> 
+<P>Specifies the root DN of the point in your hierarchy from which to begin a
+guest search for the user's DN. For example:
+<PRE>ou=people,o=FlyTours.com
+</PRE>
+<P>When using Netscape Directory Server, set this property to the root DN, the
+special entry to which access control does not apply (optional).
+</LI></UL>
+<P>To narrow the search, you can specify a user's
+<I>objectClass</I>.
+<UL>
+<LI><I>derby.authentication.ldap.searchFilter
+(optional)</I> 
+<P>Set
+<I>derby.authentication.ldap.searchFilter</I> to
+a logical expression that specifies what constitutes a user for your LDAP
+directory service. The default value of this property is
+<TT><I>objectClass=inetOrgPerson</I></TT>. For example:
+<PRE>objectClass=person
+</PRE>
+</LI></UL>
+<P><H1><A NAME="HDRCSECUR863546">Performance Issues</H1>
+<P>For performance reasons, the LDAP directory server should be in the same
+LAN as Derby. Derby does not cache the user's credential
+information locally and thus must connect to the directory server every time a
+user connects.
+<P>Connection requests that provide the full DN are faster than those that
+must search for the full DN.
+<P><H1><A NAME="HDRCSECUR863611">Windows NT Users	</H1>
+<P>Netscape provides LDAP functionality for Windows NT systems with its
+Netscape Directory Synchronization service, which synchronizes the Windows NT
+users with the Netscape Directory Server. SSL is recommended in this
+configuration.
+<P><H1><A NAME="HDRCSECUR863676">Restrictions</H1>
+<P>Derby does not support LDAP groups.
+<P><H1><A NAME="HDRCSECUR864242">JNDI-Specific Properties for External Directory Services</H1>
+<A NAME="IDX741"></A>
+<P>Derby allows you to set a few advanced JNDI properties, which you can
+set in any of the supported ways of setting Derby properties.
+Typically you would set these at the same level (database or system) for which
+you configured the external authentication service.
+<P>The list of supported properties can be found in Appendix A: JNDI
+Context Environment in the Java Naming and Direction API at
+<VAR>http://java.sun.com/products/jndi/reference/api/index.html</VAR>.
+The external directory service must support the property.
+<P>Each JNDI provider has its set of properties that you can set within the
+Derby system.
+<P>For example, you can set the property
+<I>java.naming.security.authentication</I> to allow
+user credentials to be encrypted on the network if the provider supports
+it. You can also specify that SSL be used with LDAP (LDAPS).
+<P><H1><A NAME="HDRSII-CSECUR-21561">User-Defined Class</H1>
+<A NAME="IDX742"></A>
+<P>Set <I>derby.authentication.provider</I> to the full
+name of a class that implements the public interface
+<I>org.apache.derby.authentication.UserAuthenticator</I>.
+<P>By writing your own class that fulfills some minimal requirements, you can
+hook Derby up to an <I>external authentication service</I> other than
+LDAP. To do so, specify an external authentication service
+by setting the property
+<TT><I>derby.authentication.provider</I></TT> to a
+class name that you want Derby to load at startup.
+<P>The class that provides the external authentication service must implement
+the public interface
+<I>org.apache.derby.authentication</I>.<I>UserAuthenticator</I>
+and throw exceptions of the type
+<I>java.sql.SQLException</I> where appropriate.
+<P>Using a user-defined class makes Derby adaptable to various naming and
+directory services.
+<P>A very simple example of a class that implements the interface
+follows.
+<PRE>import org.apache.derby.authentication.UserAuthenticator;
+import java.io.FileInputStream;
+import java.util.Properties;
+import java.sql.SQLException;
+<B>/**
+  * A simple example of a specialized Authentication scheme.
+  * The system property 'derby.connection.requireAuthentication'
+  * must be set
+  * to true and 'derby.connection.specificAuthentication' must
+  * contain the full class name of the overriden authentication
+  * scheme,  i.e., the name of this class.
+  *
+  * @see org.apache.derby.authentication.UserAuthenticator&nbsp;
+  */</B>
+ 
+public class MyAuthenticationSchemeImpl implements
+UserAuthenticator {
+    private static final String USERS_CONFIG_FILE = "myUsers.cfg";
+    private static Properties usersConfig;
+ 
+   <B> // Constructor
+    // We get passed some Users properties if the&nbsp;
+    //authentication service could not set them as&nbsp;
+    //part of System properties.
+    //</B>
+    public MyAuthenticationSchemeImpl() {
+    }
+<B>    /* static block where we load the users definition from a
+users configuration file.*/</B>
+ 
+    static {
+<B>       /* load users config file as Java properties
+        File must be in the same directory where
+        Derby  gets started.
+       (otherwise full path must be specified) */</B>
+       FileInputStream in = null;
+       usersConfig = new Properties();
+       try {
+           in = new FileInputStream(USERS_CONFIG_FILE);
+           usersConfig.load(in);
+           in.close();
+       } catch (java.io.IOException ie) {
+           // No Config file. Raise error message
+           System.err.println(
+             "WARNING: Error during Users Config file
+retrieval");
+           System.err.println("Exception: " + ie);
+       }
+    }
+<B>    /**
+     * Authenticate the passed-in user's credentials.
+     * A more complex class could make calls
+     * to any external users directory.
+     *
+     * @param userName               The user's name
+     * @param userPassword           The user's password&nbsp;
+     * @param databaseName           The database&nbsp;
+     * @param infoAdditional jdbc connection info.
+     * @exception SQLException on failure
+     */</B>
+    public boolean authenticateUser(String userName,
+     String userPassword,
+     String databaseName,
+     Properties info)
+       throws SQLException&nbsp;
+    {
+ <B>      /* Specific Authentication scheme logic.
+        If user has been authenticated, then simply return.
+        If user name and/or password are invalid,&nbsp;
+        then raise the appropriate exception.
+&nbsp;
+       This example allows only users defined in the
+       users config properties object.
+ 
+       Check if the passed-in user has been defined for the system.
+       We expect to find and match the property corresponding to
+       the credentials passed in. */</B>
+       if (userName == null)
+          <B> // We do not tolerate 'guest' user for now.
+       </B>    return false;
+<B>       //
+       // Check if user exists in our users config (file)
+       // properties set.
+       // If we did not find the user in the users config set, then
+       // try to find if the user is defined as a System property.
+       //</B>
+       String actualUserPassword;
+       actualUserPassword = usersConfig.getProperty(userName);
+       if (actualUserPassword == null)
+           actualUserPassword = System.getProperty(userName);
+       if (actualUserPassword == null)
+            <B>// no such passed-in user found</B>
+            return false;
+            <B>// check if the password matches</B>
+       if (!actualUserPassword.equals(userPassword))
+       return false;
+       <B>// Now, check if the user is a valid user of the database</B>
+       if (databaseName != null)
+       {
+             <B>/* if database users restriction lists present, then check&nbsp;
+            if there is one for this database and if so,&nbsp;
+            check if the user is a valid one of that database.
+            For this example, the only user we authorize in database
+            DarkSide is user 'DarthVader'. This is the only database
+            users restriction list we have for this example.
+            We authorize any valid (login) user to access the
+            OTHER databases in the system.
+            Note that database users ACLs could be set in the same
+            properties file or a separate one and implemented as you
+            wish. */</B>
+            <B>//</B>
+           if (databaseName.equals("DarkSide")) {
+              <B>// check if user is a valid one.</B>
+              if (!userName.equals("DarthVader"))
+                  <B>// This user is not a valid one of the passed-in</B>
+                  return false;
+           }
+       }
+       <B>// The user is a valid one in this database</B>
+       return true;
+    }
+}
+</PRE>
+<P><HR>[ <A HREF="develop99.html">Previous Page</A><br><A HREF="develop101.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop101.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop101.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,80 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Built-in Derby Users</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="Derby's built-in repository, Users, Passwords">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-CSECUR-21547">Built-in Derby Users</H1>
+<A NAME="IDX743"></A>
+<P>Derby provides a simple, built-in repository of user names and
+passwords.
+<P>To use the built-in repository, set
+<I>derby.authentication.provider</I> to
+<I>BUILTIN</I>. Using built-in users is an alternative to using an
+external directory service such as LDAP.
+<PRE>derby.authentication.provider=BUILTIN
+</PRE>
+<P>You can create user names and passwords for Derby users by specifying
+them with the <I>derby.user.UserName</I>
+property.
+<DL><DT><B>Note:</B></DT><DD>These user names are case-sensitive for user authorization. User names
+are <I>SQL92Identifiers</I>. Delimited identifiers are
+allowed: 
+<PRE>derby.user."FRed"=java
+</PRE>
+</DD></DL>
+<P>For more information on user names and <I>SQL92Identifiers</I>, see <A HREF="develop104.html#HDRSII-CSECUR-37241">Users and Authorization Identifiers</A>.
+<DL><DT><B>Note:</B></DT><DD>For passwords, it is a good idea not to use words that would be easily
+guessed, such as a login name or simple words or numbers. A password
+should be a mix of numbers and upper- and lowercase letters.
+<A NAME="IDX744"></A>
+</DD></DL>
+<P><H1><A NAME="HDRCSECUR864642">Database-Level Properties</H1>
+<P>When you create users with database-level properties, those users are
+available to the specified database only.
+<P>You set the property once for each user. To delete a user, set that
+user's password to null.
+<PRE><B><B>-- adding the user sa with password 'derbyE'</B>
+CALL SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY(
+    'derby.user.sa', 'derbypass')
+<B>-- adding the user mary with password 'little7xylamb'</B>
+CALL SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY(
+    'derby.user.mary', 'little7xylamb')
+<B>-- removing mary by setting password to null</B>
+CALL SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY(
+    'derby.user.mary', null)</B>
+</PRE>
+<P><H1><A NAME="HDRCSECUR864692">System-Level Properties</H1>
+<P>When you create users with system-level properties, those users are
+available to all databases in the system.
+<P>You set the value of this system-wide property once for each user, so you
+can set it several times. To delete a user, remove that user from the
+file.
+<P>You can define this property in the usual ways--typically in the
+<I>derby.properties</I> file. For more information
+about setting properties, see <CITE>Tuning Derby</CITE>.
+<P>Here is a sample excerpt from the <I>derby.properties</I>
+file:
+<PRE><B># Users definition
+#</B>
+derby.user.sa=derbypass
+derby.user.mary=little7xylamb
+</PRE>
+<P><HR>[ <A HREF="develop100.html">Previous Page</A><br><A HREF="develop102.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop102.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop102.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,58 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Properties Summary</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-CSECUR-32557">Properties Summary</H1>
+<P><A HREF="#TBLSII-CSECUR-27690">Table 9</A> summarizes the various properties related to user
+authentication.
+<BR>
+<P><B><A NAME="TBLSII-CSECUR-27690">Table 9. User Authentication Properties</A></B><BR>
+<TABLE WIDTH="100%" BORDER>
+<TR>
+<TH ALIGN="LEFT" VALIGN="BOTTOM" ID="WQ38" WIDTH="54%">Property Name
+</TH><TH ALIGN="LEFT" VALIGN="BOTTOM" ID="WQ39" WIDTH="46%">Use
+</TH></TR><TR>
+<TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ38" WIDTH="54%"><I>derby.connection.requireAuthentication</I>
+</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ39" WIDTH="46%">Turns on user authentication.
+</TD></TR><TR>
+<TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ38" WIDTH="54%"><I>derby.authentication.provider</I>
+</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ39" WIDTH="46%">Specifies the kind of user authentication to use.
+</TD></TR><TR>
+<TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ38" WIDTH="54%"><I>derby.authentication.server</I>
+</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ39" WIDTH="46%">For LDAP user authentication, specifies the location of the
+server.
+</TD></TR><TR>
+<TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ38" WIDTH="54%"><I>derby.authentication.ldap.searchAuthDN,
+derby.authentication.ldap.searchAuthPW,
+derby.authentication.ldap.searchFilter,
+</I>and<TT><I> derby.authentication.
+ldap.searchBase</I></TT>
+</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ39" WIDTH="46%">Configures the way DN searches are performed.
+</TD></TR><TR>
+<TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ38" WIDTH="54%"><I>derby.user.UserName</I>
+</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ39" WIDTH="46%">Creates a user name and password for Derby's built-in user
+repository.
+</TD></TR><TR>
+<TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ38" WIDTH="54%"><I>javax.naming.*</I>
+</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ39" WIDTH="46%">JNDI properties
+</TD></TR></TABLE>
+<P>
+<P><HR>[ <A HREF="develop101.html">Previous Page</A><br><A HREF="develop103.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop103.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop103.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,68 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Programming Applications for Derby User Authentication</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="programming applications for, User authentication, providing, User names, Passwords, no encryption of">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-CSECUR-79358">Programming Applications for Derby User Authentication</H1>
+<A NAME="IDX745"></A>
+<UL>
+<LI><A HREF="#HDRSII-CSECUR-12766">Programming the Application to Provide the User and Password</A>
+</LI><LI><A HREF="#HDRSII-CSECUR-30551">Login Failure Exceptions</A>
+</LI><LI><A HREF="develop105.html#HDRSII-CSECUR-24458">Authorization Identifiers, User Authentication, and User Authorization</A>
+</LI></UL>
+<P><H1><A NAME="HDRSII-CSECUR-12766">Programming the Application to Provide the User and Password</H1>
+<A NAME="IDX746"></A>
+<A NAME="IDX747"></A>
+<P>In the <I>DriverManager.getConnection</I> call, an application
+can provide the user name and password:
+<UL>
+<LI>separately as arguments to the following signature of the method:
+<I>getConnection(String url, String user, String password)</I> 
+<PRE>Connection conn = DriverManager.getConnection(
+    "jdbc:derby:myDB", "mary", "little7xylamb");
+</PRE>
+</LI><LI>as attributes to the database connection URL 
+<PRE>Connection conn = DriverManager.getConnection(
+    "jdbc:derby:myDB;user=mary;password=little7xylamb");
+</PRE>
+</LI><LI>by setting the user and password properties in a Properties object as with
+other connection URL attributes 
+<PRE>Properties p = new Properties();
+p.put("user", "mary");
+p.put("password", "little7xylamb");
+Connection conn = DriverManager.getConnection(
+    "jdbc:derby:myDB", p);
+</PRE>
+</LI></UL>
+<DL><DT><B>Note:</B></DT><DD>The password is not encrypted. When you are using Derby in the
+context of a server framework, the framework should be responsible for
+encrypting the password across the network. If your framework does not
+encrypt the password, consider using SSL.
+<A NAME="IDX748"></A>
+</DD></DL>
+<P>For information about the treatment of user names within the Derby
+system, see <A HREF="develop104.html#HDRSII-CSECUR-37241">Users and Authorization Identifiers</A>.
+<P><H1><A NAME="HDRSII-CSECUR-30551">Login Failure Exceptions</H1>
+<P>If user authentication is turned on and a valid user name and password are
+not provided, <I>SQLException</I> 08004 is raised.
+<PRE>ERROR 08004: Connection refused : Invalid authentication.
+</PRE>
+<P><HR>[ <A HREF="develop102.html">Previous Page</A><br><A HREF="develop104.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop104.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop104.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,43 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Users and Authorization Identifiers</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="Authorization identifiers">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<HR><H1 NAME="HDRSII-CSECUR-37241">Users and Authorization Identifiers</H1>
+<A NAME="IDX749"></A>
+<P>User names within the Derby system are known as <I>authorization
+identifiers</I>. The authorization identifier is a string that
+represents the name of the user, if one was provided in the connection
+request. For example, the built-in function CURRENT_USER returns the
+authorization identifier for the current user.
+<P>Once the authorization identifier is passed to the Derby system, it
+becomes an <I>SQL92Identifier</I>.
+<TT><I>SQL92Identifiers</I></TT>--the kind of identifiers that
+represent database objects such as tables and columns--are
+case-insensitive (they are converted to all caps) unless delimited with double
+quotes, are limited to 128 characters, and have other limitations.
+<P>User names must be valid authorization identifiers even if user
+authentication is turned off, and even if all users are allowed access to all
+databases.
+<P>For more information about <I>SQL92Identifiers</I>, see
+<I>&quot;SQL92Identifier&quot; </I> in the <CITE>Derby Reference
+Manual</CITE>.
+<P><HR>[ <A HREF="develop103.html">Previous Page</A><br><A HREF="develop105.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop105.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop105.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,77 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Authorization Identifiers, User Authentication, and User Authorization</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="and schemas, Users, and users, Schemas">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-CSECUR-24458">Authorization Identifiers, User Authentication, and User Authorization</H1>
+<A NAME="IDX750"></A>
+<A NAME="IDX751"></A>
+<P>When working with both user authentication and user authorization, you need
+to understand how user names are treated by each system. If an external
+authentication system is used, the conversion of the user's name to an
+authorization identifier does not happen until <I>after</I> authentication
+has occurred but <I>before</I> user authorization (see <A HREF="develop108.html#HDRSII-CSECUR-36595">User Authorization</A>). Imagine, for example, a user named Fred.
+<UL>
+<LI>Within the user authentication system, Fred is known as
+<I>FRed</I>. Your external user authorization service is
+case-sensitive, so Fred must always type his name that way. 
+<PRE>Connection conn = DriverManager.getConnection(
+    "jdbc:derby:myDB", "FRed", "flintstone");
+</PRE>
+</LI><LI>Within the Derby user authorization system, Fred becomes a
+case-insensitive authorization identifier. Fred is known as
+<I>FRED</I>.
+</LI><LI>When specifying which users are authorized to access the accounting
+database, you must list Fred's authorization identifier, <I>FRED</I>
+(which you can type as <I>FRED</I>, <I>FREd</I>, or <I>fred</I>,
+since the system automatically converts it to all-uppercase). 
+<PRE><B>derby.fullAccessUsers=sa,FRED,mary</B>
+</PRE>
+</LI></UL>
+<P>Let's take a second example, where Fred has a slightly different name
+within the user authentication system.
+<UL>
+<LI>Within the user authentication system, Fred is known as
+<I>Fred!</I>. You must now put double quotes around the name,
+because it is not a valid <TT><I>SQL92Identifier</I></TT>.
+(Derby knows to remove the double quotes when passing the name to the
+external authentication system.) 
+<PRE>Connection conn = DriverManager.getConnection(
+    "jdbc:derby:myDB", "\"Fred!\"", "flintstone");
+</PRE>
+</LI><LI>Within the Derby user authorization system, <I>Fred</I> becomes a
+case-sensitive authorization identifier. Fred is known as
+<I>Fred!</I>.
+</LI><LI>When specifying which users are authorized to access the accounting
+database, you must list Fred's authorization identifier,
+<I>&quot;Fred!&quot;</I> (which you must always delimit with double
+quotation marks). 
+<PRE>derby.fullAccessUsers=sa,"Fred!",manager
+</PRE>
+</LI></UL>
+<P>As shown in the first example, your external authentication system may be
+case-sensitive, whereas the authorization identifier within Derby may not
+be. If your authentication system allows two distinct users whose names
+differ by case, delimit all user names within the connection request to make
+all user names case-sensitive within the Derby system. In
+addition, you must also delimit user names that do not conform to
+<I>SQL92Identifier</I> rules with double quotes.
+<P><HR>[ <A HREF="develop104.html">Previous Page</A><br><A HREF="develop106.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop106.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop106.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,27 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>User Names and Schemas</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRCSECUR865580">User Names and Schemas</H1>
+<P>User names can affect a user's default schema. For information
+about user names and schemas, see &quot;SET SCHEMA statement&quot; in the
+<CITE>Derby Reference Manual</CITE><CITE>.</CITE>
+<P><HR>[ <A HREF="develop105.html">Previous Page</A><br><A HREF="develop107.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop107.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop107.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,27 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Exceptions</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRCSECUR865622">Exceptions</H1>
+<P>Specifying an invalid authorization identifier in a database user
+authorization property raises an exception. Specifying an invalid
+authorization identifier in a connection request raises an exception.
+<P><HR>[ <A HREF="develop106.html">Previous Page</A><br><A HREF="develop108.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop108.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop108.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,33 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>User Authorization</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="User authorization, Authorization">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<HR><H1 NAME="HDRSII-CSECUR-36595">User Authorization</H1>
+<A NAME="IDX752"></A>
+<A NAME="IDX753"></A>
+<P>Derby provides user authorization, which is a means of granting users
+permission to access a database (or system). Derby allows you to
+distinguish between full (read-write) access and read-only access.
+(Derby Version 10 does not support the SQL GRANT and REVOKE
+features, which allow you to set permissions to specific database objects or
+specific SQL actions.)
+<P><HR>[ <A HREF="develop107.html">Previous Page</A><br><A HREF="develop109.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop109.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop109.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,100 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Setting User Authorization</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="for databases, User authorization, controlling access to, Databases, full (read-write) versus read-only, Access, UserUtility, com.ibm.derby.database.UserUtility">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRCSECUR866060">Setting User Authorization</H1>
+<P><H1><A NAME="HDRCSECUR865783">Database or System Access</H1>
+<A NAME="IDX754"></A>
+<P>Typically, you configure user authorization for a particular
+database. However, Derby also allows you to configure user
+authorization for the system, which is useful during development and for
+specifying a secure default access for all databases in the system.
+<P>To control access to a particular database, set database-level properties
+that specify which users have full (read-write) access to the database and
+which users have read-only access to the database. Users not specified
+by either property inherit the default access for the database (none,
+read-only, or full read-write access). When not explicitly set, the
+default access for a database is full (read-write) access.
+<P><H1><A NAME="HDRCSECUR865818">Setting the Default Access Mode</H1>
+<A NAME="IDX755"></A>
+<P>To specify the default access mode for the database, use the
+<I>derby.database.defaultConnectionMode</I>
+property. You can set the property to the following values:
+<UL>
+<LI><I>noAccess</I>
+</LI><LI><I>readOnlyAccess</I>
+</LI><LI><I>fullAccess</I> (the default)
+</LI></UL>
+<P>Derby validates the authorization configuration properties when users
+set them. It raises an exception if a user attempts to set the
+properties to invalid values (see <A HREF="#HDRSII-CSECUR-37978">Exceptions</A>).
+<P><H1><A NAME="HDRCSECUR865880">Setting the Access Mode for Particular Users</H1>
+<A NAME="IDX756"></A>
+<P>To specify which particular users have full (read-write) access to a
+database, use the <I>derby.database.fullAccessUsers</I>
+property. For example:
+<PRE>CALL SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY(
+    'derby.database.fullAccessUsers', 'sa,mary')
+</PRE>
+<P>To specify which particular users have read-only access to a database, use
+the <I>derby.database.readOnlyAccessUsers</I>
+property. For example:
+<PRE>CALL SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY(
+    'derby.database.readOnlyAccessUsers', 'guest,"Fred!"')
+</PRE>
+<P>For these properties, you specify users as a comma-separated list (no
+spaces between the comma and the next user).
+<P>For users not specified with either property the access is specified by the
+<I>derby.database.defaultConnectionMode</I>
+property.
+<DL><DT><B>Note:</B></DT><DD>It is possible to configure a database so that it cannot be changed (or even
+accessed) using the
+<I>derby.database.defaultConnectionMode</I>
+property. If you set this property to <TT><I>noAccess</I></TT> or
+<TT><I>readOnlyAccess</I></TT>, be sure to allow at least one user full
+access.
+</DD></DL>
+<DL><DT><B>Note:</B></DT><DD>Derby provides a utility to make it easier to create and maintain the
+lists of read-only and full-access users. This utility is
+<I>org.apache.derby.database.UserUtility</I>.
+The following example shows how to use the utility to add a full access
+user:
+<PRE>CALL org.apache.derby.database.UserUtility.add("mary",
+		UserUtility.FULL_ACCESS_PERMISSION);
+</PRE>
+<A NAME="IDX757"></A>
+<A NAME="IDX758"></A>
+</DD></DL>
+<P>See the Javadoc for the utility or <A HREF="develop111.html#HDRSII-CSECUR-79131">Examples</A> for more details.
+<P><H1><A NAME="HDRCSECUR865935">Notes on User Authorization</H1>
+<P>All the authorization properties are set for a connection when it is
+created. Changing any of the authorization properties does not affect
+existing connections. However, all future connections are affected by
+the change.
+<P>For more information about authorization identifiers, see <A HREF="develop104.html#HDRSII-CSECUR-37241">Users and Authorization Identifiers</A>.
+<P><H1><A NAME="HDRSII-CSECUR-37978">Exceptions</H1>
+<P>If a user is not authorized to connect to the database specified in the
+connection request, <I>SQLException</I> 04501 is raised.
+<P>If a user with <I>readOnlyAccess</I> attempts to write to a database,
+<I>SQLException</I> 08004 <TT><I>- connection refused</I></TT> is
+raised.
+<P><HR>[ <A HREF="develop108.html">Previous Page</A><br><A HREF="develop110.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop11.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop11.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,53 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Derby JDBC Database Connection URL</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="description, Database connection URL, features common to embedded and client/server versions">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-DEVELOP-17453">Derby JDBC Database Connection URL</H1>
+<A NAME="IDX504"></A>
+<P>A Java application using the JDBC API establishes a connection to a
+database by obtaining a <I>Connection</I> object. The standard way
+to obtain a <TT><I>Connection</I></TT> object is to call the method
+<TT><I>DriverManager.getConnection</I></TT>, which takes a String
+containing a connection URL (uniform resource locator). A JDBC
+connection URL provides a way of identifying a database. It also allows
+you to perform a number of high-level tasks, such as creating a database or
+shutting down the system.
+<P>An application in an embedded environment uses a different connection URL
+from that used by applications using the Derby Network Server in a
+client/server environment. See the <CITE>Derby Server and
+Administration Guide</CITE> for more information on the Network Server.
+<P>However, all versions of the connection URL (which you can use for tasks
+besides connecting to a database) have common features:
+<A NAME="IDX505"></A>
+<UL>
+<LI>you can specify the name of the database you want to connect to
+</LI><LI>you can specify a number of attributes and values that allow you to
+accomplish tasks. For more information about what you can specify with
+the Derby connection URL, see &quot;Examples&quot;. For detailed
+reference about attributes and values, as well as syntax of the database
+connection URL, see the &quot;Derby Database Connection URL Syntax&quot; in
+the <CITE>Derby Reference Manual</CITE>.
+</LI></UL>
+<P>An example use of the connection URL:
+<PRE>Connection conn=DriverManager.getConnection("jdbc:derby:sample");
+</PRE>
+<P><HR>[ <A HREF="develop10.html">Previous Page</A><br><A HREF="develop12.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop110.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop110.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,68 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>About Read-Only and Full Access</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="Permissions, definition, Read-only access, Full access">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRCSECUR866190">About Read-Only and Full Access</H1>
+<A NAME="IDX759"></A>
+<A NAME="IDX760"></A>
+<A NAME="IDX761"></A>
+<P><A HREF="#TBLSII-CSECUR-20486">Table 10</A> shows which actions read-only and full-access users are
+permitted to perform on regular or source databases and on target databases
+.
+<BR>
+<P><B><A NAME="TBLSII-CSECUR-20486">Table 10. Permissions for Read-Only and Full-Access Users</A></B><BR>
+<TABLE WIDTH="100%" BORDER>
+<TR>
+<TH ALIGN="LEFT" VALIGN="BOTTOM" ID="WQ42" WIDTH="39%">Action
+</TH><TH ALIGN="LEFT" VALIGN="BOTTOM" ID="WQ43" WIDTH="22%">Read-Only Users
+</TH><TH ALIGN="LEFT" VALIGN="BOTTOM" ID="WQ44" WIDTH="38%">Full-Access Users
+</TH></TR><TR>
+<TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ42" WIDTH="39%">Executing SELECT statements
+</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ43" WIDTH="22%">X
+</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ44" WIDTH="38%">X
+</TD></TR><TR>
+<TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ42" WIDTH="39%">Reading database properties
+</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ43" WIDTH="22%">X
+</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ44" WIDTH="38%">X
+</TD></TR><TR>
+<TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ42" WIDTH="39%">Loading database classes from jar files
+</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ43" WIDTH="22%">X
+</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ44" WIDTH="38%">X
+</TD></TR><TR>
+<TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ42" WIDTH="39%">Executing INSERT, UPDATE, or DELETE statements
+</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ43" WIDTH="22%">
+<BR></TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ44" WIDTH="38%">X
+</TD></TR><TR>
+<TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ42" WIDTH="39%">Executing DDL statements
+</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ43" WIDTH="22%">
+<BR></TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ44" WIDTH="38%">X
+</TD></TR><TR>
+<TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ42" WIDTH="39%">Adding or replacing jar files
+</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ43" WIDTH="22%">
+<BR></TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ44" WIDTH="38%">X
+</TD></TR><TR>
+<TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ42" WIDTH="39%">Setting database properties
+</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ43" WIDTH="22%">
+<BR></TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ44" WIDTH="38%">X
+</TD></TR></TABLE>
+<P>
+<P><HR>[ <A HREF="develop109.html">Previous Page</A><br><A HREF="develop111.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop111.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop111.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,56 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Examples</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-CSECUR-79131">Examples</H1>
+<P>This example shows the property settings to configure a database to
+support:
+<UL>
+<LI>full access for a single user named &quot;sa&quot;
+</LI><LI>read-only access for anyone else who connects to the database 
+<PRE><B>CALL SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY(
+    'derby.database.defaultConnectionMode',
+    'readOnlyAccess')</B>
+<B>CALL SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY(
+    'derby.database.fullAccessUsers', 'sa')</B>
+</PRE>
+</LI></UL>
+<P>The following example shows the settings to configure a database to
+support:
+<UL>
+<LI>full access for a single user named &quot;Fred!&quot; (case-sensitive) with
+full (read-write) access
+</LI><LI>Read-only access for mary and guest
+</LI><LI>No access for other users
+</LI></UL>
+<P>The example also demonstrates the use of delimited identifiers for user
+names.
+<PRE><B>CALL SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY(
+    'derby.database.defaultConnectionMode',
+    'noAccess')
+ 
+CALL SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY(
+    'derby.database.fullAccessUsers', '"Fred!"')
+ 
+CALL SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY(
+    'derby.database.readOnlyAccessUsers', 'mary,guest')</B>
+</PRE>
+<P><HR>[ <A HREF="develop110.html">Previous Page</A><br><A HREF="develop112.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop112.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop112.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,32 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Encrypting Databases on Disk</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="Database encryption, encrypting, Databases">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<HR><H1 NAME="HDRSII-CSECUR-24366">Encrypting Databases on Disk</H1>
+<A NAME="IDX762"></A>
+<A NAME="IDX763"></A>
+<UL>
+<LI><A HREF="develop113.html#HDRSII-CSECUR-99212">Overview</A>
+</LI><LI><A HREF="develop114.html#HDRSII-CSECUR-96815">Requirements for Derby Encryption</A>
+</LI><LI><A HREF="develop115.html#HDRSII-CSECUR-97760">Working with Encryption</A>
+</LI></UL>
+<P><HR>[ <A HREF="develop111.html">Previous Page</A><br><A HREF="develop113.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop113.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop113.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,41 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Overview</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-CSECUR-99212">Overview</H1>
+<P>Derby provides a way for you to encrypt your data on disk.
+<P>Typically, database systems encrypt and decrypt data in transport over the
+network, using industry-standard systems. This system works well for
+client/server databases; the server is assumed to be in a trusted, safe
+environment, managed by a system administrator. In addition, the
+recipient of the data is trusted and should be capable of protecting the
+data. The only risk comes when transporting data over the wire, and
+data encryption happens during network transport only.
+<P>However, Derby databases are platform-independent files that are
+designed to be easily shared in a number of ways, including transport over the
+Internet. Recipients of the data might not know how, or might not have
+the means, to properly protect the data.
+<P>This data encryption feature provides the ability to store user data in an
+encrypted form. The user who boots the database must provide a boot
+password.
+<DL><DT><B>Note:</B></DT><DD>Jar files stored in the database are not encrypted.
+</DD></DL>
+<P><HR>[ <A HREF="develop112.html">Previous Page</A><br><A HREF="develop114.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop114.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop114.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,50 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Requirements for Derby Encryption</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="providers, Encryption, Data encryption">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-CSECUR-96815">Requirements for Derby Encryption</H1>
+<P>Derby supports disk encryption, but you must supply the
+following:
+<UL>
+<LI>An implementation of the Java Cryptographic Extension (JCE) package
+version 1.2.1 or higher. 
+<P>Derby does not support earlier, non-exportable, versions of JCE (such
+as JCE 1.2). More information on JCE 1.2.1,
+including a product download, can be found at:
+<VAR>http://java.sun.com/products/jce/index.html</VAR>.
+<P>Any attempt to create or access an encrypted database without the libraries
+for an implementation of JCE of the proper version, or without Java<SUP>(TM)</SUP> 2
+Platform, Standard Edition, v 1.2 (J2SE) or higher, raises an
+exception; you will not be able to create or boot the database.
+<DL><DT><B>Note:</B></DT><DD>The JCE installation documentation describes configuring (registering) the
+JCE software. You do not need to do this; Derby registers JCE
+dynamically.
+</DD></DL>
+</LI><LI>the encryption provider 
+<P>
+<A NAME="IDX764"></A>
+<A NAME="IDX765"></A>
+An encryption provider implements the Java cryptography concepts. The
+JRE for J2SE 1.4 or J2EE 1.4 includes JCE and one or more
+default encryption providers.
+</LI></UL>
+<P><HR>[ <A HREF="develop113.html">Previous Page</A><br><A HREF="develop115.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop115.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop115.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,178 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Working with Encryption</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="creating, Encrypted databases, configuring, Data encryption, Encryption, Encryption providers, Encryption algorithms, booting">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-CSECUR-97760">Working with Encryption</H1>
+<UL>
+<LI><A HREF="#HDRSII-CSECUR-88690">Encrypting Databases on Creation</A>
+</LI><LI><A HREF="#HDRSII-CSECUR-60146">Booting an Encrypted Database</A>
+</LI><LI><A HREF="#HDRSII-CSECUR-55054">Changing the Boot Password</A>
+</LI></UL>
+<P><H1><A NAME="HDRSII-CSECUR-88690">Encrypting Databases on Creation</H1>
+<A NAME="IDX766"></A>
+<A NAME="IDX767"></A>
+<A NAME="IDX768"></A>
+<P>Derby allows you to configure a database for encryption when you
+create it. To do so, you specify <I>dataEncryption=true</I> on the
+connection URL.
+<P>The Java Runtime Environment (JRE) determines the default encryption
+provider, as follows:
+<UL>
+<LI>For J2SE/J2EE 1.4 or higher, the JRE's provider is the
+default.
+</LI><LI>For an IBM Corp J2SE/J2EE 1.3 JRE, the default provider is
+<I>com.ibm.crypto.provider</I>.
+</LI><LI>For a Sun Microsystem J2SE/J2EE 1.3 JRE, the default provider is
+<I>com.sun.crypto.provider.SunJCE</I>.
+</LI><LI>For any other J2SE/J2EE 1.3 JRE, a provider must be
+specified.
+</LI></UL>
+<P>You have the option of specifying an alternate encryption provider;
+see <A HREF="#HDRSII-CSECUR-31493">Specifying an Alternate Encryption Provider</A>. The default encryption algorithm is DES, but you
+have the option of specifying an alternate algorithm; see <A HREF="#HDRSII-CSECUR-67151">Specifying an Alternate Encryption Algorithm</A>.
+<P><H1><A NAME="HDRCSECUR866716">Creating the Boot Password</H1>
+<P>When you encrypt a database you must also specify a boot password, which is
+an alpha-numeric string used to generate the encryption key. The length
+of the encryption key depends on the algorithm used:
+<UL>
+<LI>DES (the default) (56 bits)
+</LI><LI>DESede (168 bits)
+</LI><LI>all other algorithms (128 bits)
+</LI></UL>
+<DL><DT><B>Note:</B></DT><DD>The boot password should have at least as many characters as number of bytes
+in the encryption key (56 bits=8 bytes, 168 bits=24 bytes, 128 bits=16
+bytes). The minimum number of characters for the boot password allowed
+by Derby is eight.
+</DD></DL>
+<P>It is a good idea not to use words that would be easily guessed, such as a
+login name or simple words or numbers. A <I>bootPassword</I>, like
+any password, should be a mix of numbers and upper- and lowercase
+letters.
+<P>You turn on and configure encryption and specify the corresponding boot
+password on the connection URL for a database when you create it:
+<PRE>jdbc:derby:encryptionDB1;create=true;dataEncryption=true;
+    bootPassword=clo760uds2caPe
+</PRE>
+<DL><DT><B>Note:</B></DT><DD>If you lose the <I>bootPassword</I> and the database is not currently
+booted, you will not be able to connect to the database anymore. (If
+you know the current <I>bootPassword</I>, you can change it. See <A HREF="#HDRSII-CSECUR-55054">Changing the Boot Password</A>.)
+</DD></DL>
+<P><H1><A NAME="HDRSII-CSECUR-31493">Specifying an Alternate Encryption Provider</H1>
+<A NAME="IDX769"></A>
+<P>You can specify an alternate provider when you create the database with the
+<TT><I>encryptionProvider=providerName</I></TT> attribute.
+<P>You must specify the full package and class name of the provider, and you
+must also add the libraries to the application's class path.
+<PRE><B>-- using the the provider library jce_jdk13-10b4.zip|
+-- available from www.bouncycastle.org</B>
+jdbc:derby:encryptedDB3;create=true;dataEncryption=true;
+bootPassword=clo760uds2caPe;
+encryptionProvider=org.bouncycastle.jce.provider.BouncyCastleProvider;
+encryptionAlgorithm=DES/CBC/NoPadding
+ 
+<B>-- using a provider
+-- available from
+-- http://jcewww.iaik.tu-graz.ac.at/download.html</B>
+jdbc:derby:encryptedDB3;create=true;dataEncryption=true;
+bootPassword=clo760uds2caPe;
+encryptionProvider=iaik.security.provider.IAIK;encryptionAlgorithm=
+DES/CBC/NoPadding
+</PRE>
+<P><H1><A NAME="HDRSII-CSECUR-67151">Specifying an Alternate Encryption Algorithm</H1>
+<A NAME="IDX770"></A>
+<P>Derby supports the following encryption algorithms:
+<UL>
+<LI>DES (the default)
+</LI><LI>DESede (also known as triple DES)
+</LI><LI>Any encryption algorithm that fulfills the following requirements: 
+<UL>
+<LI>it is symmetric
+</LI><LI>it is a block cipher, with a block size of 8 bytes
+</LI><LI>it uses the <I>NoPadding</I> padding scheme
+</LI><LI>its secret key can be represented as an arbitrary byte array
+</LI><LI>it requires exactly one initialization parameter, an initialization vector
+of type <I>javax.crypto.spec.IvParameterSpec</I>
+</LI><LI>it can use <I>javax.crypto.spec.SecretKeySpec</I>
+to represent its key
+</LI></UL> 
+<P>For example, the algorithm <I>Blowfish</I> implemented in the Sun JCE
+package fulfills these requirements.
+</LI></UL>
+<P>By Java convention, an encryption algorithm is specified like this:
+<PRE><B><I>algorithmName</I>/<I>feedbackMode</I>/<I>padding</I></B>
+</PRE>
+<P>The only feedback modes allowed are:
+<UL>
+<LI>CBC
+</LI><LI>CFB
+</LI><LI>ECB
+</LI><LI>OCB
+</LI></UL>
+<P>By default, Derby uses the DES algorithm of
+<I>DES/CBC/NoPadding</I>.
+<P>Specify an alternate encryption algorithm when you create a database with
+the <I>encryptionAlgorithm=algorithm</I> attribute. If the
+algorithm you specify is not supported by the provider you have specified,
+Derby throws an exception.
+<P><H1><A NAME="HDRSII-CSECUR-60146">Booting an Encrypted Database</H1>
+<A NAME="IDX771"></A>
+<P>Once you have created an encrypted database, you must supply the boot
+password to reboot it. Encrypted databases cannot be booted
+automatically along with all other system databases on system startup (see
+<I>&quot;derby.system.bootAll&quot; </I> in <CITE>Tuning
+Derby</CITE>). Instead, you boot encrypted databases when you
+first connect to them.
+<P>For example, to access an encrypted database called <I>wombat,</I>
+created with the boot password clo760uds2caPe<I>,</I> you would use the
+following connection URL:
+<PRE>jdbc:derby:wombat;bootPassword=clo760uds2caPe
+</PRE>
+<P>Once the database is booted, all connections can access the database
+without the boot password. Only a connection that boots the database
+requires the key.
+<P>For example, the following connections would boot the database and thus
+require the boot password:
+<UL>
+<LI>the first connection to the database in the JVM session
+</LI><LI>the first connection to the database after the database has been
+explicitly shut down
+</LI><LI>the first connection to the database after the system has been shut down
+and then rebooted
+</LI></UL>
+<DL><DT><B>Note:</B></DT><DD>The boot password is not meant to prevent unauthorized connections to the
+database once it has been booted. To protect a database once it has
+been booted, turn on user authentication (see <A HREF="develop96.html#HDRSII-CSECUR-42374">Working with User Authentication</A>).
+</DD></DL>
+<P><H1><A NAME="HDRSII-CSECUR-55054">Changing the Boot Password</H1>
+<P>You can change the boot password for the current database.
+<PRE><B>CALL SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY(
+    'bootPasword', '<I>oldbpw</I> , <I>newbpw</I>');</B>
+</PRE>
+<P>where <I>oldbpw</I> is the current boot password and <I>newbpw</I>
+is the new boot password. This call commits immediately; it is not
+transactional.
+<DL><DT><B>Note:</B></DT><DD><TT><I>PropertyInfo.getDatabaseProperty("bootPassword")</I></TT>,
+or <TT>VALUES
+SYSCS_UTIL.SYSCS_GET_DATABASE_PROPERTY('bootPassword')</TT>,
+will not return the boot password.
+</DD></DL>
+<P><HR>[ <A HREF="develop114.html">Previous Page</A><br><A HREF="develop116.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop116.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop116.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,64 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Signed Jar Files</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="loading signed, Jar files, Signed jar files">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<HR><H1 NAME="HDRSII-CSECUR-90988">Signed Jar Files</H1>
+<A NAME="IDX772"></A>
+<A NAME="IDX773"></A>
+<P>In a Java 2 environment, Derby can detect digital signatures on jar
+files. When attempting to load a class from a signed jar file stored in
+the database, Derby will verify the validity of the signature.
+<DL><DT><B>Note:</B></DT><DD>The Derby class loader only validates the integrity of the signed jar
+file and that the certificate has not expired. Derby cannot
+ascertain whether the validity/identity of declared signer is correct.
+To validate identity, use a Security Manager (i.e., an
+implementation of <I>java.lang.SecurityManager</I>).
+</DD></DL>
+<P>When loading classes from an application jar file in a Java 2 environment,
+Derby behaves as follows:
+<UL>
+<LI><I>If the class is signed, Derby will:</I> 
+<UL>
+<LI>verify that the jar was signed using a X.509 certificate
+(i.e., can be represented by the class
+<I>java.security.cert.X509Certificate</I>). If
+not, throw an exception.
+</LI><LI>verify that the digital signature matches the contents of the file.
+If not, throw an exception.
+</LI><LI>check that the set of signing certificates are all valid for the current
+date and time. If any certificate has expired or is not yet valid,
+throw an exception.
+</LI><LI>pass the array of certificates to the <I>setSigners()</I> method of
+<TT><I>java.lang.ClassLoader</I></TT>. This allows
+security managers to obtain the list of signers for a class (using
+<TT><I>java.lang.Class.getSigners</I></TT>) and
+then validate the identity of the signers using the services of a Public Key
+Infrastructure (PKI).
+</LI></UL>
+</LI></UL>
+<DL><DT><B>Note:</B></DT><DD>Derby does not provide a security manager.
+</DD></DL>
+<P>For more information about signed jar files, see the Java 2 specifications
+at <VAR>http://java.sun.com</VAR>.
+<P>For more information about Java 2 security, go to
+<VAR>http://java.sun.com/security/</VAR>.
+<P><HR>[ <A HREF="develop115.html">Previous Page</A><br><A HREF="develop117.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop117.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop117.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,46 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Notes on the Derby Security Features</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="limitations of, Security features">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<HR><H1 NAME="HDRSII-CSECUR-10983">Notes on the Derby Security Features</H1>
+<A NAME="IDX774"></A>
+<P>Because Derby does not support traditional grant and revoke features,
+the security model has some basic limitations. For both embedded and
+client/server systems, it assumes that users are trusted. You must
+trust your full-access users not to perform undesirable actions. You
+lock out non full-access users with database properties, which are stored in
+the database (and in an encrypted database these properties are also
+encrypted). Note, however, for a distributed/embedded system that a
+sophisticated user with the database encryption key might be able to
+physically change those properties in the database files.
+<P>In addition, in the Derby system, it is not necessary to have a
+specific connection (or permission to access a particular database) to shut
+down the system. Any authenticated user can shut down the
+system.
+<P>Other security holes to think about are:
+<UL>
+<LI>JVM subversion, running the application under a home-grown JVM.
+</LI><LI>trolling for objects
+</LI><LI>class substitution, locating a class that has access to sensitive data and
+replacing it with one that passes on information
+</LI></UL>
+<P><HR>[ <A HREF="develop116.html">Previous Page</A><br><A HREF="develop118.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop118.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop118.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,29 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>User Authentication and Authorization Examples</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<HR><H1 NAME="HDRSII-CSECUR-51876">User Authentication and Authorization Examples</H1>
+<UL>
+<LI><A HREF="develop119.html#HDRSII-CSECUR-18108">Client/Server Environment</A>
+</LI><LI><A HREF="develop120.html#HDRSII-CSECUR-13713">Single-User, Embedded Environment</A>
+</LI><LI><A HREF="develop120.html#HDRSII-CSECUR-26537">Extended Example</A>
+</LI></UL>
+<P><HR>[ <A HREF="develop117.html">Previous Page</A><br><A HREF="develop119.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop119.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop119.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,73 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Client/Server Environment</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-CSECUR-18108">Client/Server Environment</H1>
+<P>In this example, Derby is running in a user-designed application
+server. Derby provides the user authentication, not the
+application server. The server is running in a secure environment, the
+application server encrypts the passwords, and a database administrator is
+available. The administrator configures security using system-level
+properties in the <I>derby.properties</I> file and has
+protected this file with operating system tools. Derby connects to
+an existing LDAP directory service within the enterprise to authenticate
+users.
+<P>The default access mode for all databases is set to <I>fullAccess</I>
+(the default).
+<P>The <I>derby.properties</I> file for the server includes
+the following entries:
+<PRE><B># turn on user authentication</B>
+derby.connection.requireAuthentication=true
+<B># set the authentication provider to an external LDAP server</B>
+derby.authentication.provider=LDAP
+<B># the host name and port number of the LDAP server</B>
+derby.authentication.server=godfrey:389
+<B># the search base for user names</B>
+derby.authentication.ldap.searchBase=o=oakland.mycompany.com
+<B># explicitly show the access mode for databases (this is default)</B>
+derby.database.defaultAccessMode=fullAccess
+</PRE>
+<P>With these settings, all users must be authenticated by the LDAP server in
+order to access any Derby databases.
+<P>The database administrator has determined that one database,
+<I>accountingDB</I>, has additional security needs. Within a
+connection to that database, the database administrator uses database-wide
+properties (which override properties set in the
+<I>derby.properties</I> file) to limit access to this
+database. Only the users <I>prez</I>, <I>cfo</I>, and
+<I>numberCruncher</I> have full (read-write) access to this database, and
+only <I>clerk1</I> and <I>clerk2</I> have read-only access to this
+database. No other users can access the database.
+<PRE><B>CALL SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY(
+    'derby.database.defaultAccessMode', 'noAccess')
+ 
+CALL SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY(
+    'derby.database.fullAccessUsers',
+    'prez,cfo,numberCruncher')
+ 
+CALL SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY(
+    'derby.database.readAccessUsers', 'clerk1,clerk2')</B>
+</PRE>
+<P>The database administrator then requires all current users to disconnect
+and re-connect. These property changes do not go into effect for
+current connections. The database administrator can force current users
+to reconnect by shutting down the database
+<P><HR>[ <A HREF="develop118.html">Previous Page</A><br><A HREF="develop120.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop12.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop12.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,262 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Derby System</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="Derby system, System directory, description, System, derby.properties file, defined for system in derby.properties, Properties, Error log, derby.log, prohibition of, Multiple JVMs accessing, single system, of databases in system, Automatic booting, Restarting Derby within same JVM, specifying, used to define system directory, derby.system.home, default, creating and naming directory for">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-DEVELOP-27610">Derby System</H1>
+<A NAME="IDX506"></A>
+<A NAME="IDX507"></A>
+<A NAME="IDX508"></A>
+<P>A Derby database exists within a <I>system</I>.
+<P>A Derby system is a single instance of the Derby database engine
+and the environment in which it runs. It consists of a system
+directory, zero or more databases, and a system-wide configuration. The
+system directory contains any persistent system-wide configuration parameters,
+or properties, specific to that system in a properties file called <A HREF="#HDRSII-DEVELOP-39943">derby.properties</A>. This file is not automatically created; you
+must create it yourself.
+<A NAME="IDX509"></A>
+<A NAME="IDX510"></A>
+<P>The Derby system is not persistent; you must specify the location
+of the system directory at every startup.
+<P>However, the system - as well as its directory, which you name - is an
+essential part of a running database or databases. Understanding the
+Derby system is essential to successful development and deployment of
+Derby applications.
+<P><B><A NAME="FIGSII-DEVELOP-17155">Figure 1. Derby databases live in a system, which includes system-wide properties, an error log, and one or more databases.</A></B><BR>
+<BR><IMG SRC="images/system.gif" ALT="Derby databases live in a system, which includes system-wide properties, an error log, and one or more databases."><BR>
+<P>The system directory can also contain an error log file called
+<I>derby.log </I>(see <A HREF="#HDRSII-DEVELOP-25889">The Error Log</A>).
+<A NAME="IDX511"></A>
+<A NAME="IDX512"></A>
+<P>Each database within that system is contained in a subdirectory, which has
+the same name as the database (see <A HREF="develop13.html#HDRSII-DEVELOP-21955">A Derby Database</A>).
+<P>You can use a property (see <I>&quot;derby.service&quot; </I>
+in <CITE>Tuning Derby</CITE>) to include databases in other directories
+or in subdirectories of the system directory in the current system when you
+start it up.
+<P>In addition, if you connect to a database outside the current system, it
+automatically becomes part of the current system.
+<P><H1><A NAME="HDRSII-DEVELOP-96597">One Derby per Java Virtual Machine</H1>
+<A NAME="IDX513"></A>
+<P>You could potentially have two instances of a Derby system (JVM)
+running on the same machine at the same time. Each instance must run in
+a different JVM. Two separate instances of Derby must not access
+the same database. For example, in an embedded environment, an
+application that accesses Derby databases starts up the local JDBC
+driver, which starts up an instance of Derby. If you start another
+application, such as ij, and connect to the same database, severe database
+corruption can result. See <A HREF="#HDRSII-DEVELOP-20458">Double-Booting System Behavior</A>.
+<P><H1><A NAME="HDRSII-DEVELOP-27715">Booting</H1>
+<A NAME="IDX514"></A>
+<P>The default configuration for Derby is to <I>boot</I> (or start) a
+database when an application first makes a connection to it. When
+Derby boots a database, it checks to see if recovery needs to be run on
+the database, so in some unusual cases booting can take some time.
+<P>You can also configure your system to automatically boot all databases in
+the system when it starts up; see
+<I>derby.system.bootAll</I> in the Tuning 
+Derby manual. Because of the time needed to boot a database, the
+number of databases in the system directory affects startup performance if you
+use that configuration.
+<P>Once a database has been booted within a Derby system, it remains
+active until the Derby system has been shut down or until you shut down
+the database individually.
+<P>When Derby boots a database, it prints a message in the error
+log:
+<PRE>2004-06-10 03:54:06.196 GMT: Booting Derby version
+- 10.0.0.1 alpha - (29612): instance c013800d-00fd-0cb0-e736-ffffd1025a25 on
+database directory sample
+</PRE>
+<P>The number of databases running in a Derby system is limited only by
+the amount of memory available in the JVM.
+<P><H1><A NAME="HDRSII-DEVELOP-20349">Shutting Down the System</H1>
+<P>In an embedded environment, when an application shuts down, it should first
+shut down Derby.
+<P>If the application that started the embedded Derby quits but leaves
+the JVM running, Derby continues to run and is available for database
+connections.
+<P>In an embedded system, the application shuts down the Derby system by
+issuing the following JDBC call:
+<PRE>DriverManager.getConnection("jdbc:derby:cs;shutdown=true");
+</PRE>
+<P>Shutdown commands always raise <I>SQLExceptions</I>.
+<P>When a Derby system shuts down, a message goes to the error log:
+<PRE>Sat Jan 10 14:31:54 PDT 2004:
+Shutting down instance 80000001-00d0-8bdf-d115-000a0a0b2d00
+</PRE>
+<P>
+<A NAME="IDX515"></A>
+Typically, an application using an embedded Derby engine shuts down
+Derby just before shutting itself down. However, an application
+can shut down Derby and later restart it in the same JVM session.
+To restart Derby successfully, the JVM needs to unload
+<I>org.apache.derby.jdbc.EmbeddedDriver</I>, so
+that it can reload it when it restarts Derby. (Loading the local
+driver starts Derby.)
+<P>You cannot explicitly request that the JVM unload a class, but you can
+ensure that the <I>EmbeddedDriver</I> class is unloaded by using a
+<TT><I>System.gc()</I></TT> to force it to garbage collect
+classes that are no longer needed. Running with
+<TT><I>-nogc</I></TT> or <TT><I>-noclassgc</I></TT> definitely
+<I>prevents</I> the class from being unloaded and makes you unable to
+restart Derby in the same JVM.
+<P>It is also possible to shut down a single database instead of the entire
+Derby system. See <A HREF="develop15.html#HDRSII-DEVELOP-40464">Shutting Down Derby or an Individual Database</A>. You can reboot a database in the same Derby
+session after shutting it down.
+<P><H1><A NAME="HDRSII-DEVELOP-13018">Defining the System Directory</H1>
+<A NAME="IDX516"></A>
+<P>
+<A NAME="IDX517"></A>
+You define the system directory when Derby starts up by specifying a Java
+<I>system property</I> called
+<TT><I>derby.system.home</I></TT>. If you do
+not specify the system directory when starting up Derby, the current
+directory becomes the system directory.
+<P>It is recommended 
+that you always explicitly specify the system directory when
+starting up Derby.
+<P>Derby uses the <I>derby.system.home</I>
+property to determine which directory is its system directory - and thus what
+databases are in its system, where to create new databases, and what
+configuration parameters to use. See <CITE>Tuning Derby</CITE>
+for more information on setting this property.
+<P>If you specify a system directory at startup that does not exist,
+Derby creates this new directory - and thus a new system with no
+databases--automatically.
+<A NAME="IDX518"></A>
+<P><H1><A NAME="HDRSII-DEVELOP-25889">The Error Log</H1>
+<A NAME="IDX519"></A>
+<P>Once you create or connect to a database within a system, Derby begins
+outputting information and error messages, if any. Typically,
+Derby writes this information to a log called
+<I>derby.log</I> in the system directory, although you can
+also have Derby send messages to a stream, using a property. By
+default, Derby overwrites <I>derby.log</I> when you start
+the system. You can configure Derby to append to the log with the
+<TT><I>derby.infolog.append</I></TT> property.
+For information on setting this and other properties, see <CITE>Tuning 
+Derby</CITE>.
+<P><H1><A NAME="HDRSII-DEVELOP-39943">derby.properties</H1>
+<A NAME="IDX520"></A>
+<P>The text file <I>derby.properties</I> contains the
+definition of properties, or configuration parameters valid for the entire
+system. This file is not automatically created; if you wish to set
+Derby properties with this file, you need to create it yourself.
+The file should be in the format created by the
+<TT><I>java.util.Properties.save</I></TT>
+method. For more information about properties and the
+derby.properties file, see <CITE>Tuning 
+Derby</CITE>.
+<P><H1><A NAME="HDRSII-DEVELOP-20458">Double-Booting System Behavior</H1>
+<P>Derby attempts to prevent two instances of Derby from booting the
+same database by using a file called <I>db.lck</I> inside the
+database directory (see &quot;The Database Directory&quot;).
+<P>On all platforms running with a JDK of 1.4 or higher, Derby can
+successfully prevent a second instance of Derby from booting the database
+and thus prevents corruption.
+<P>On some platforms running with a JDK lower than 1.4, Derby may
+prevent a second instance of Derby from booting the database (previous to
+JDK 1.4 the ability to do this was OS dependent).
+<P>If this is the case, you will see an <I>SQLException</I> like the
+following:
+<PRE>ERROR XJ040: Failed to start database 'sample', see the next exception for details.
+ERROR XSDB6: Another instance of Derby might have already booted
+the databaseC:\databases\sample.&nbsp;
+ 
+</PRE>
+<P>The error is also written to the error log.
+<P>If you are running a JVM prior to 1.4, Derby issues a warning
+message on some platforms if an instance of Derby attempts to boot a
+database that already has a running instance of Derby attached to
+it. However, it does not prevent the second instance from booting, and
+thus potentially corrupting, the database. (You can change this
+behavior with the property
+<TT><I>derby.database.forceDatabaseLock</I></TT>.)
+<P>If a warning message has been issued, corruption might already have
+occurred. Corruption can occur even if one of the two booting systems
+has &quot;readonly&quot; access to the database.
+<P>The warning message looks like this:
+<PRE>WARNING: Derby&nbsp;
+(instance 80000000-00d2-3265-de92-000a0a0a0200) is
+attempting to boot the database /export/home/sky/wombat
+even though Derby
+(instance 80000000-00d2-3265-8abf-000a0a0a0200) might still be active.
+Only one instance of Derby
+should boot a database at a time. Severe and non-recoverable corruption can
+result and might have already occurred.
+</PRE>
+<P>The warning is also written to the error log.
+<P>If you see this warning, you should close the connection and exit the JVM,
+minimizing the risk of a corruption. Close all instances of Derby,
+then restart one instance of Derby and shut down the database properly so
+that the <I>db.lck</I> file can be removed. The warning
+message continues to appear until a proper shutdown of the Derby system
+can delete the <I>db.lck</I> file.
+<P>When developing applications, you might want to configure Derby to
+append to the log. Doing so will help you detect when you have
+inadvertently started more than one instance of Derby in the same
+system. For example, when the
+<I>derby.infolog.append</I> property is set to true for
+a system, booting two instances of Derby in the same system produces the
+following in the log:
+<PRE>Sat Aug 14 09:42:51 PDT 2004:
+Booting Derby version - 10.0.0.1 alpha - (29612):&nbsp;
+ 
+instance 80000000-00d2-1c87-7586-000a0a0b1300 on database at
+directory C:\tutorial_system\sample
+------------------------------------------------------------
+Sat Aug 14 09:42:59 PDT 2004:
+Booting Derby version - 10.0.0.1 alpha - (29612):
+instance 80000000-00d2-1c87-9143-000a0a0b1300 on database at
+directory C:\tutorial_system\HelloWorldDB
+</PRE>
+<P>Derby allows you to boot databases that are not in the system
+directory. While this might seem more convenient, check that you do not
+boot the same database with two JVMs. If you need to access a single
+database from more than one JVM, you will need to put a server solution in
+place. You can allow multiple JVMs that need to access that database to
+connect to the server. Derby includes the Network Server as a
+server solution. See the <CITE>Derby Server and Administration
+Guide</CITE> for more information on the Network Server.
+<P><H1><A NAME="HDRSII-DEVELOP-19297">Recommended Practices</H1>
+<A NAME="IDX521"></A>
+<P>When developing Derby applications, create a single directory to hold
+your database or databases. Give this directory a unique name, to help
+you remember that:
+<UL>
+<LI>All databases exist within a system.
+</LI><LI>System-wide properties affect the entire system, and persistent
+system-wide properties live in the system directory.
+</LI><LI>You can boot all the databases in the system, and the boot-up times of all
+databases affect the performance of the system.
+</LI><LI>You can preboot databases only if they are within the system.
+(Databases do not necessarily have to live inside the system
+<I>directory</I>, but keeping your databases there is the recommended
+practice.)
+</LI><LI>Once you connect to a database, it is part of the current system and thus
+inherits all system-wide properties.
+</LI><LI>Only one instance of Derby can run in a JVM at a single time, and
+only one instance of Derby should boot a database at one time.
+Keeping databases in the system directory makes it less likely that you would
+use more than one instance of Derby.
+</LI><LI>The error log is located inside the system directory.
+</LI></UL>
+<P><HR>[ <A HREF="develop11.html">Previous Page</A><br><A HREF="develop13.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop120.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop120.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,188 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Single-User, Embedded Environment</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-CSECUR-13713">Single-User, Embedded Environment</H1>
+<P>In this example, Derby is embedded in a single-user application that
+is deployed in a number of different and potentially insecure ways. For
+that reason, the application developer has decided to encrypt the database and
+to turn on user authentication using Derby's built-in user
+authentication, which will not require connections to an LDAP server.
+The end-user must know the <I>bootPassword</I> to boot the database and
+the user name and password to connect to the database. Even if the
+database ended up in an e-mail, only the intended recipient would be able to
+access data in the database. The application developer has decided not
+to use any user authorization features, since each database will accept only a
+single user. In that situation, the default full-access connection mode
+is acceptable.
+<P>When creating the database, the application developer encrypts the database
+by using the following connection URL:
+<PRE><B>jdbc:derby:wombat;create=true;dataEncryption=true;
+    bootPassword=sxy90W348HHn</B>
+</PRE>
+<P>Before deploying the database, the application developer turns on user
+authentication, sets the authentication provider to BUILTIN, creates a single
+user and password, and disallows system-wide properties to protect the
+database-wide security property settings:
+<PRE><B>SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY(
+    'derby.connection.requireAuthentication', 'true')
+ 
+SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY(
+    'derby.authentication.provider', 'BUILTIN')
+ 
+SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY(
+    'derby.user.enduser', 'red29PlaNe')
+ 
+CALL SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY(
+    'derby.database.propertiesOnly', true')</B>
+</PRE>
+<P>When the user connects (and boots) the database, the user has to provide
+the <I>bootPassword</I>, the user name, and the password. The
+following example shows how to provide those in a connection URL, although the
+application programmer would probably provide GUI windows to allow the end
+user to type those in:
+<PRE><B>jdbc:derby:wombat;bootPassword=sxy90W348HHn;
+    user=enduser;password=red29PlaNe</B>
+</PRE>
+<P><H1><A NAME="HDRSII-CSECUR-26537">Extended Example</H1>
+<P>The following two examples from the <I>sample</I> database show how to
+turn on and turn off user authentication using Derby's built-in user
+authentication and user authorization.
+<PRE>/**&nbsp;
+	  * Turn on built-in user authentication and user authorization.&nbsp;
+	  *&nbsp;
+	  * @param conn a connection to the database.
+	  */
+ 
+	public static void turnOnBuiltInUsers(Connection conn) throws SQLException {&nbsp;
+		System.out.println("Turning on authentication.");&nbsp;
+		Statement s = conn.createStatement();&nbsp;
+ 
+ 
+		// Setting and Confirming requireAuthentication&nbsp;
+		s.executeUpdate("CALL SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY(" +&nbsp;
+			"'derby.connection.requireAuthentication', 'true')");
+		ResultSet rs = s.executeQuery(&nbsp;
+			"VALUES SYSCS_UTIL.SYSCS_GET_DATABASE_PROPERTY(" +&nbsp;
+			"'derby.connection.requireAuthentication')");&nbsp;
+		rs.next();&nbsp;
+		System.out.println(rs.getString(1));&nbsp;
+		// Setting authentication scheme to Derby&nbsp;
+		s.executeUpdate("CALL SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY(" +&nbsp;
+			"'derby.authentication.provider', 'BUILTIN')");&nbsp;
+ 
+		// Creating some sample users&nbsp;
+		s.executeUpdate("CALL SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY(" +&nbsp;
+			"'derby.user.sa', 'ajaxj3x9')");&nbsp;
+		s.executeUpdate("CALL SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY(" +&nbsp;
+			"'derby.user.guest', 'java5w6x')");&nbsp;
+		s.executeUpdate("CALL SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY(" +&nbsp;
+			"'derby.user.mary', 'little7xylamb')");&nbsp;
+ 
+		// Setting default connection mode to no access&nbsp;
+		// (user authorization)&nbsp;
+		s.executeUpdate("CALL SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY(" +&nbsp;
+			"'derby.database.defaultConnectionMode', 'noAccess')");&nbsp;
+		// Confirming default connection mode&nbsp;
+		rs = s.executeQuery (
+			"VALUES SYSCS_UTIL.SYSCS_GET_DATABASE_PROPERTY(" +&nbsp;
+			"'derby.database.defaultConnectionMode')");&nbsp;
+		rs.next();&nbsp;
+		System.out.println(rs.getString(1));&nbsp;
+ 
+		// Defining read-write users&nbsp;
+		s.executeUpdate("CALL SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY(" +&nbsp;
+			"'derby.database.fullAccessUsers', 'sa,mary')");&nbsp;
+ 
+		// Defining read-only users&nbsp;
+		s.executeUpdate("CALL SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY(" +&nbsp;
+			"'derby.database.readOnlyAccessUsers', 'guest')");&nbsp;
+ 
+		// Confirming full-access users&nbsp;
+		rs = s.executeQuery(
+			"VALUES SYSCS_UTIL.SYSCS_GET_DATABASE_PROPERTY(" +&nbsp;
+			"'derby.database.fullAccessUsers')");&nbsp;
+		rs.next();&nbsp;
+		System.out.println(rs.getString(1));&nbsp;
+ 
+		// Confirming read-only users&nbsp;
+		rs = s.executeQuery(
+			"VALUES SYSCS_UTIL.SYSCS_GET_DATABASE_PROPERTY(" +&nbsp;
+			"'derby.database.readOnlyAccessUsers')");&nbsp;
+		rs.next();&nbsp;
+		System.out.println(rs.getString(1));&nbsp;
+ 
+		//we would set the following property to TRUE only&nbsp;
+		//when we were ready to deploy.&nbsp;
+		s.executeUpdate("CALL SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY(" +&nbsp;
+			"'derby.database.propertiesOnly', 'false')");&nbsp;
+		s.close();&nbsp;
+	}&nbsp;
+</PRE>
+<PRE>/**&nbsp;
+	  * Turn off built-in user authentication and user authorization.&nbsp;
+	  *&nbsp;
+	  * @param conn a connection to the database.
+	  */
+ 
+	public static void turnOffBuiltInUsers(Connection conn) throws SQLException {&nbsp;
+		Statement s = conn.createStatement();&nbsp;
+		System.out.println("Turning off authentication.");&nbsp;
+ 
+		s.executeUpdate("CALL SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY(" +&nbsp;
+			"'derby.connection.requireAuthentication', 'false')");&nbsp;
+		s.executeUpdate("CALL SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY(" +&nbsp;
+			"'derby.authentication.provider', null)");&nbsp;
+		s.executeUpdate("CALL SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY(" +&nbsp;
+			"'derby.user.sa', null)");&nbsp;
+		s.executeUpdate("CALL SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY(" +&nbsp;
+			"'derby.user.guest', null)");&nbsp;
+		s.executeUpdate("CALL SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY(" +&nbsp;
+			"'derby.user.mary', null)");&nbsp;
+		s.executeUpdate("CALL SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY(" +&nbsp;
+			"'derby.database.defaultConnectionMode', 'fullAccess')");&nbsp;
+		s.executeUpdate("CALL SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY(" +&nbsp;
+			"'derby.database.fullAccessUsers', null)");&nbsp;
+		s.executeUpdate("CALL SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY(" +&nbsp;
+			"'derby.database.readOnlyAccessUsers', null)");&nbsp;
+		s.executeUpdate("CALL SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY(" +&nbsp;
+			"'derby.database.propertiesOnly', 'false')");&nbsp;
+ 
+		// Confirming requireAuthentication&nbsp;
+		ResultSet rs = s.executeQuery(
+			"VALUES SYSCS_UTIL.SYSCS_GET_DATABASE_PROPERTY(" +&nbsp;
+			"'derby.connection.requireAuthentication')");&nbsp;
+		rs.next();&nbsp;
+		System.out.println(rs.getString(1));&nbsp;
+ 
+		// Confirming default connection mode&nbsp;
+		rs = s.executeQuery(
+			"VALUES SYSCS_UTIL.SYSCS_GET_DATABASE_PROPERTY(" +&nbsp;
+			"'derby.database.defaultConnectionMode')");&nbsp;
+		rs.next();&nbsp;
+		System.out.println(rs.getString(1));&nbsp;
+		System.out.println("Turned off all the user-related properties.");&nbsp;
+		s.close();&nbsp;
+	}
+}
+ 
+</PRE>
+<P><HR>[ <A HREF="develop119.html">Previous Page</A><br><A HREF="develop121.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop121.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop121.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,40 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Running Derby under a security manager</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="and Derby permissions, Policy files, Java 2 Security Manager">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<HR><H1 NAME="HDRBABEJDFJ">Running Derby under a security manager</H1>
+<A NAME="IDX775"></A>
+<P>
+<A NAME="IDX776"></A>
+When running within an application or application server with a Java 2
+Security Manager enabled, Derby must be granted certain permissions to
+execute and access database files. Those permissions are described in
+&quot;<A HREF="develop122.html#HDRBABEJGJD">Granting Permissions to Derby</A>&quot;, below.
+<P>For more information about permissions and examples of creating permission
+objects and granting permissions, see the Security Architecture specification
+at
+<VAR>http://java.sun.com/j2se/1.4.2/docs/guide/security/PolicyFiles.html</VAR>.
+<UL>
+<LI><A HREF="develop122.html#HDRBABEJGJD">Granting Permissions to Derby</A>
+</LI><LI><A HREF="develop123.html#HDRCSECUR871387">Examples of Java 2 Security Policy Files for embedded Derby</A>
+</LI></UL>
+<P><HR>[ <A HREF="develop120.html">Previous Page</A><br><A HREF="develop122.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop122.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop122.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,79 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Granting Permissions to Derby</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="granting to Derby, Permissions, mandatory, database access, optional">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRBABEJGJD">Granting Permissions to Derby</H1>
+<A NAME="IDX777"></A>
+<P>The following section discusses which permissions should be granted to
+Derby (the code base <I>derby.jar</I>).
+<P>See Default Policy Implementation and Policy File Syntax at
+<VAR>http://java.sun.com/j2se/1.4.2/docs/guide/security/PolicyFiles.html</VAR>
+for more information about creating policy files.
+<P><H1><A NAME="HDRCSECUR871035">Mandatory Permissions</H1>
+<A NAME="IDX778"></A>
+<P><H1><A NAME="HDRCSECUR871065">permission java.lang.RuntimePermission &quot;createClassLoader&quot;</H1>
+<P>Mandatory. It allows Derby to execute SQL queries and supports
+loading class files from jar files stored in the database.
+<P><H1><A NAME="HDRCSECUR871126">permission java.util.PropertyPermission &quot;derby.*&quot;, read</H1>
+<P>Allows Derby to read individual Derby properties set in the
+JVM's system set. If the action is denied, properties in the
+JVM's system set are ignored.
+<P><H1><A NAME="HDRCSECUR871172">Database Access Permissions</H1>
+<A NAME="IDX779"></A>
+<P><H1><A NAME="HDRCSECUR871193">permission java.io.FilePermission &quot;directory${/}/-&quot;, &quot;read,write,delete&quot;</H1>
+<P>Allows Derby to manage files within the database that maps to the
+directory specified. For read-only databases, only the &quot;read&quot;
+action needs to be granted.
+<P><H1><A NAME="HDRCSECUR871230">Optional Permissions</H1>
+<A NAME="IDX780"></A>
+<P><H1><A NAME="HDRCSECUR871260">permission java.io.FilePermission &quot;${derby.system.home}&quot;, &quot;read,write&quot;</H1>
+<P>Allows Derby to determine the system directory when set by
+d<I>b2j.system.home </I>and create it if needed. If
+the system directory already exists then only the &quot;read&quot; permission
+needs to be granted.
+<P><H1><A NAME="HDRCSECUR871279">permission java.util.PropertyPermission &quot;user.dir&quot;, &quot;read&quot;</H1>
+<P>Permits access to the system directory value if
+<I>derby.system.home </I>is not set or no permission
+has been granted to read the <TT><I>derby.system.home
+</I></TT>property.
+<P><H1><A NAME="HDRCSECUR871300">permission java.io.FilePermission &quot;${derby.system.home}${/}derby.properties&quot;, &quot;read&quot;</H1>
+<P>Allows Derby to read the system properties file from the system
+directory.
+<P><H1><A NAME="HDRCSECUR871315">permission java.io.FilePermission &quot;${derby.system.home}${/}derby.log&quot;, &quot;read,write,delete&quot;</H1>
+<P>or
+<P><H1><A NAME="HDRCSECUR871330">permission java.io.FilePermission &quot;${user.dir}${/}derby.log&quot;, &quot;read,write,delete&quot;</H1>
+<P>Only one of these permissions is needed. Permits the application to
+read, write, and delete to the Derby log file, unless the log has been
+re-directed. (See the <I>derby.stream.error
+</I>properties in <CITE>Tuning Derby</CITE> for more
+information.) If one of the requested valid actions is denied, the
+Derby log will be
+<TT><I>java.lang.System.err</I></TT>.
+<P><H1><A NAME="HDRCSECUR871353">Combining Permissions</H1>
+<P>You might grant one <I>FilePermission</I> that encompasses several, or
+all, of the permissions described below, instead of separately granting a
+number of the more specific permissions.
+<P>For example:
+<P><H1><A NAME="HDRCSECUR871372">permission java.io.FilePermission &quot;${derby.system.home}/-&quot;, &quot;read,write,delete&quot;</H1>
+<P>Allows the Derby engine complete access to the system directory and
+any databases contained in the system directory.
+<P><HR>[ <A HREF="develop121.html">Previous Page</A><br><A HREF="develop123.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop123.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop123.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,79 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Examples of Java 2 Security Policy Files for embedded Derby</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="examples, Policy files">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRCSECUR871387">Examples of Java 2 Security Policy Files for embedded Derby</H1>
+<A NAME="IDX781"></A>
+<P><H1><A NAME="HDRCSECUR871406">Example 1</H1>
+<PRE><B>/* Grants permission to run Derby and access all      */
+/* databases under the Derby system home              */
+/* when it is specified by the system property             */
+/* derby.system.home                                        */
+ 
+/* Note derby.system.home must be an absolute pathname */</B>
+ 
+grant codeBase "file://f:/derby/lib/derby.jar" {
+ 
+  permission java.lang.RuntimePermission "createClassLoader";
+  permission java.util.PropertyPermission "derby.*", "read";
+ 
+  permission java.io.FilePermission "${derby.system.home}${/}
+-", "read,write,delete";
+};
+</PRE>
+<P><H1><A NAME="HDRCSECUR871422">Example 2</H1>
+<PRE><B>/* Grants permission to run Derby and access all      */
+/* databases under the Derby system home              */
+/* when it defaults to the current directory               */</B>
+ 
+ 
+grant codeBase "file://f:/derby/lib/derby.jar" {
+  permission java.lang.RuntimePermission "createClassLoader";
+  permission java.util.PropertyPermission "derby.*", "read";
+&nbsp;
+  permission java.util.PropertyPermission "user.dir", "read";
+  permission java.io.FilePermission "${user.dir}${/}-",
+ "read,write,delete";
+ 
+};
+</PRE>
+<P><H1><A NAME="HDRCSECUR871439">Example 3</H1>
+<PRE><B>/* Grants permission to run Derby and access a single */
+/* database (salesdb) under the Derby system home     */
+ 
+/* Note derby.system.home must be an absolute pathname */</B>
+ 
+grant codeBase "file://f:/derby/lib/derby.jar" {
+ 
+  permission java.lang.RuntimePermission "createClassLoader";
+  permission java.util.PropertyPermission "derby.*", "read";
+ 
+  permission java.io.FilePermission "${derby.system.home}${/}*",&nbsp;
+"read,write,delete";
+  permission java.io.FilePermission "${derby.system.home}${/}
+salesdb${/}
+-", "read,write,delete";
+ 
+ 
+};&nbsp;
+</PRE>
+<P><HR>[ <A HREF="develop122.html">Previous Page</A><br><A HREF="develop124.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop124.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop124.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,30 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Developing Tools and Using Derby with an IDE</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<HR><H1 NAME="HDRSII-ADVJDBC-35053">Developing Tools and Using Derby with an IDE</H1>
+<P>Applications such as database tools are designed to work with databases
+whose schemas and contents are unknown in advance. This chapter
+discusses a few topics useful for such applications.
+<UL>
+<LI><A HREF="develop125.html#HDRSII-ADVJDBC-41138">Offering Connection Choices to the User</A>
+</LI></UL>
+<P><HR>[ <A HREF="develop123.html">Previous Page</A><br><A HREF="develop125.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop125.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop125.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,67 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Offering Connection Choices to the User</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="java.sql.Driver.getPropertyInfo, list of provided by databaseName attribute, Available databases">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<HR><H1 NAME="HDRSII-ADVJDBC-41138">Offering Connection Choices to the User</H1>
+<P>
+<A NAME="IDX782"></A>
+JDBC's <I>java.sql.Driver.getPropertyInfo</I>
+method allows a generic GUI tool to determine the properties for which it
+should prompt a user in order to get enough information to connect to a
+database. Depending on the values the user has supplied so far,
+additional values might become necessary. It might be necessary to
+iterate though several calls to <TT><I>getPropertyInfo</I></TT>.
+If no more properties are necessary, the call returns an array of zero
+length.
+<P>In a Derby system, do not use the method against an instance of
+<I>org.apache.derby.jdbc.EmbeddedDriver</I>.
+Instead, request the JDBC driver from the driver manager:
+<PRE>java.sql.DriverManager.getDriver(
+    "jdbc:derby:").getPropertyInfo(<I>URL</I>, <I>Prop</I>)
+</PRE>
+<P>
+<A NAME="IDX783"></A>
+In a Derby system, the properties returned in the
+<I>DriverPropertyInfo</I> object are connection URL attributes, including
+a list of booted databases in a system (the <TT><I>databaseName</I></TT>
+attribute).
+<P>Databases in a system are not automatically booted until you connect with
+them. You can configure your system to retain the former behavior, in
+which case the steps described in this section will continue to work.
+See <I>&quot;derby.system.bootAll&quot; </I> in
+<CITE>Tuning Derby</CITE>.
+<P><I>getPropertyInfo</I> requires a connection URL and a
+<TT><I>Properties</I></TT> object as parameters. Typically, what
+you pass are values that you will use in a future call to
+<TT><I>java.sql.DriverManager.getConnection</I></TT>
+when you actually connect to the database. For information about
+setting attributes in calls to
+<TT><I>java.sql.DriverManager.getConnection</I></TT>,
+see <A HREF="develop14.html#HDRSII-DEVELOP-22102">Examples</A>.
+<P>A call to <I>getPropertyInfo</I> with parameters that contain
+sufficient information to connect successfully returns an array of zero
+length. (Receiving this zero-length array does not <I>guarantee</I>
+that the <TT><I>getConnection</I></TT> call will succeed, because
+something else could go wrong.)
+<P>Repeat calls to <I>getPropertyInfo</I> until it returns a zero-length
+array or none of the properties remaining are desired.
+<P><HR>[ <A HREF="develop124.html">Previous Page</A><br><A HREF="develop126.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop126.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop126.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,71 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>The DriverPropertyInfo Array</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="DriverPropertyInfo Array, using, getPropertyInfo">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRADVJDBC814034">The DriverPropertyInfo Array</H1>
+<A NAME="IDX784"></A>
+<P>When a non-zero-length array is returned by <I>getPropertyInfo</I>,
+each element is a <TT><I>DriverPropertyInfo</I></TT> object representing
+a connection URL attribute that has not already been specified. Only
+those that make sense in the current context are returned.
+<P>This <I>DriverPropertyInfo</I> object contains:
+<UL>
+<LI><I>name of the attribute</I>
+</LI><LI><I>description</I>
+</LI><LI><I>current value</I> 
+<P>If an attribute has a default value, this is set in the value field of
+<I>DriverPropertyInfo</I>, even if the attribute has not been set in the
+connection URL or the <TT><I>Properties</I></TT> object. If the
+attribute does not have a default value and it is not set in the URL or the
+<TT><I>Properties</I></TT> object, its value will be null.
+</LI><LI><I>list of choices</I>
+</LI><LI><I>whether required for a connection request</I>
+</LI></UL>
+<P>Several fields in a <I>DriverPropertyInfo</I> object are allowed to be
+null.
+<P><H1><A NAME="HDRADVJDBC813965">Example</H1>
+<A NAME="IDX785"></A>
+<P>Here is some example code:
+<PRE>import java.sql.*;
+import java.util.Properties;
+<B>// start with the least amount of information
+// to see the full list of choices
+// we could also enter with a URL and Properties
+// provided by a user.</B>
+String url = "jdbc:derby:";
+Properties info = new Properties();
+Driver cDriver = DriverManager.getDriver(url);
+for (;;)
+        {
+        DriverPropertyInfo[] attributes = cDriver.getPropertyInfo(
+            url, info);
+        <B> // zero length means a connection attempt can be made</B>
+        if (attributes.length == 0)
+        break;
+<B>        // insert code here to process the array, e.g.,
+        // display all options in a GUI and allow the user to
+        // pick and then set the attributes in info or URL.</B>
+        }
+<B>// try the connection</B>
+Connection conn = DriverManager.getConnection(url, info);
+</PRE>
+<P><HR>[ <A HREF="develop125.html">Previous Page</A><br><A HREF="develop127.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop127.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop127.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,42 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Using Derby with IDEs</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="using Derby with, IDEs, and need to use server framework">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<HR><H1 NAME="HDRSII-ADVJDBC-32436">Using Derby with IDEs</H1>
+<A NAME="IDX786"></A>
+<A NAME="IDX787"></A>
+<P>When you use an integrated development environment (IDE) to develop an
+embedded Derby application, you might need to run Derby within a
+server framework. This is because an IDE might try connecting to the
+database from two different JVMs, whereas only a single JVM instance should
+connect to a Derby database at one time, as described in <A HREF="develop12.html#HDRSII-DEVELOP-96597">One Derby per Java Virtual Machine</A> (multiple connections from the same JVM are allowed).
+<P>An &quot;embedded Derby application&quot; is one which runs in the same
+JVM as the application. Such an application uses the embedded
+Derby driver
+(<I>org.apache.derby.jdbc.EmbeddedDriver</I>;
+see <A HREF="develop25.html#HDRSII-DEVELOP-40170">Embedded Derby JDBC Driver</A>) and connection URL
+(<TT><I>jdbc:derby:databaseName</I></TT>; see <A HREF="develop26.html#HDRSII-DEVELOP-38881">Embedded Derby JDBC Database Connection URL</A>). If you use
+this driver name or connection URL from the IDE, when the IDE tries to open a
+second connection to the same database with the embedded Derby, the
+attempt fails. Two JVMs cannot connect to the same database in embedded
+mode. This situation is described in more detail in <A HREF="develop128.html#HDRSII-ADVJDBC-18939">IDEs and Multiple JVMs</A>.
+<P><HR>[ <A HREF="develop126.html">Previous Page</A><br><A HREF="develop128.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop128.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop128.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,51 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>IDEs and Multiple JVMs</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-ADVJDBC-18939">IDEs and Multiple JVMs</H1>
+<P>When you use an integrated development environment (IDE) to build a Java
+application, you can launch the application from within the IDE at any point
+in the development process. Typically, the IDE launches a JVM dedicated
+to the application. When the application completes, the JVM
+exits. Any database connections established by the application are
+closed.
+<P>During the development of a database application, most IDEs allow you to
+test individual database connections and queries without running the entire
+application. When you test an individual database connection or query
+(which requires a database connection), the IDE might launch a JVM that runs
+in a specialized testing environment. In this case, when a test
+completes, the JVM remains active and available for further testing, and the
+database connection established during the test remains open.
+<P>Because of the behaviors of the IDE described above, if you use the
+embedded Derby JDBC driver, you may encounter errors connecting in the
+following situations:
+<UL>
+<LI>You test an individual query or database connection and then try to run an
+application that uses the same database as the tested feature. 
+<P>The database connection established by testing the connection or query
+stays open, and prevents the application from establishing a connection to the
+same database.
+</LI><LI>You run an application, and before it completes (for example, while it
+waits for user input), you attempt to run a second application or to test a
+connection or query that uses the same database as the first
+application.
+</LI></UL>
+<P><HR>[ <A HREF="develop127.html">Previous Page</A><br><A HREF="develop129.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop129.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop129.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,33 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>SQL Tips</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<HR><H1 NAME="HDRSII-TRICKS-32436">SQL Tips</H1>
+<P>This section provides some examples of interesting SQL features (it also
+includes one or two non-SQL tips):
+<UL>
+<LI><A HREF="develop130.html#HDRSII-TRICKS-19707">Retrieving the Database Connection URL</A>
+</LI><LI><A HREF="develop131.html#HDRSII-TRICKS-39584">Supplying a Parameter Only Once</A>
+</LI><LI><A HREF="develop132.html#HDRSII-TRICKS-21248">Defining an Identity Column</A>
+</LI><LI><A HREF="develop133.html#HDRSII-TRICKS-23426">Using Third-Party Tools</A>
+</LI><LI><A HREF="develop134.html#HDRSII-TRICKS-13019">Tricks of the VALUES Clause</A>
+</LI></UL>
+<P><HR>[ <A HREF="develop128.html">Previous Page</A><br><A HREF="develop130.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop13.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop13.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,218 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>A Derby Database</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="description of in Derby system, Databases, function, log directory, seg0 directory, service.properties file, tmp directory, jar directory, Size limitations of Derby objects and databases, maximum number allowed per database, Tables, size limitations, maximum number allowed per table, Indexes, Columns, Rows, dropping, Dropping databases, Backing up databases, backing up, Shutting down a single database, Recovery, description, Start-up, Shutdown, Database pages, configuring, in current version, Limitations, limitations of, not supported for CLOB, BLOB, and LONG VARCHAR data types">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-DEVELOP-21955">A Derby Database</H1>
+<A NAME="IDX522"></A>
+<P>A Derby database contains dictionary objects such as tables, columns,
+indexes, and jar files. A Derby database can also store its own
+configuration information.
+<P><H1><A NAME="HDRSII-DEVELOP-40724">The Database Directory</H1>
+<P>A Derby database is stored in files that live in a directory of the
+same name as the database. Database directories typically live in
+<I>system</I> directories.
+<P>A database directory contains the following, as shown in <A HREF="#FIGSII-DEVELOP-31476">Figure 2</A>:
+<UL>
+<LI><I>log</I> directory
+<A NAME="IDX523"></A>
+<P>Contains files that make up the database transaction log, used internally
+for data recovery (not the same thing as the error log).
+</LI><LI><I>seg0</I> directory
+<A NAME="IDX524"></A>
+<P>Contains one file for each user table, system table, and index (known as
+conglomerates).
+</LI><LI><I>service.properties</I> file
+<A NAME="IDX525"></A>
+<P>A text file with internal configuration information.
+</LI><LI><I>tmp</I> directory 
+<A NAME="IDX526"></A>
+<P>(might not exist.) A temporary directory used by Derby for
+large sorts and deferred updates and deletes. Sorts are used by a
+variety of SQL statements. For databases on read-only media, you might
+need to set a property to change the location of this directory. See
+&quot;Creating Derby Databases for Read-Only Use&quot;.
+</LI><LI><I>jar</I> directory 
+<A NAME="IDX527"></A>
+<P>(might not exist.) A directory in which jar files are stored when
+you use database class loading.
+</LI></UL>
+<P><A NAME="SPTSII-DEVELOP-ACCESSINGAREADONLYDATABASEINAZIP"></A>Read-only database directories can be archived (and compressed,
+if desired) into jar or zip files. For more information, see <A HREF="develop37.html#HDRSII-DEPLOY-11201">Accessing a Read-Only Database in a Zip/Jar</A>.
+<P><B><A NAME="FIGSII-DEVELOP-31476">Figure 2. Derby database directories contain files and directories used by the software.</A></B><BR>
+<BR><IMG SRC="images/dbcont.gif" ALT="A Derby database directory containing files and directories."><BR>
+<P>
+<A NAME="IDX528"></A>
+Derby imposes relatively few limitations on the number and size of
+databases and database objects. The following table shows some size
+limitations of Derby databases and database objects:
+<BR>
+<P><B><A NAME="TBLSII-DEVELOP-85623">Table 1. </A></B><BR>
+<TABLE WIDTH="100%">
+<A NAME="IDX529"></A>
+<A NAME="IDX530"></A>
+<A NAME="IDX531"></A>
+<A NAME="IDX532"></A>
+<A NAME="IDX533"></A>
+<A NAME="IDX534"></A>Size Limits to Derby Database Objects
+<TR>
+<TH ALIGN="LEFT" VALIGN="BOTTOM" ID="WQ2" WIDTH="40%">Type of Object
+</TH><TH ALIGN="LEFT" VALIGN="BOTTOM" ID="WQ3" WIDTH="60%">Limit
+</TH></TR><TR>
+<TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ2" WIDTH="40%">tables per database
+</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ3" WIDTH="60%"><I>java.lang.Long.MAX_VALUE</I> 
+<P>Some operating systems impose a limit to the number of files allowed in a
+single directory.
+</TD></TR><TR>
+<TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ2" WIDTH="40%">indexes per table
+</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ3" WIDTH="60%">32,767 or storage
+</TD></TR><TR>
+<TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ2" WIDTH="40%">columns per table
+</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ3" WIDTH="60%">1,012
+</TD></TR><TR>
+<TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ2" WIDTH="40%">number of columns on an index key
+</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ3" WIDTH="60%">16
+</TD></TR><TR>
+<TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ2" WIDTH="40%">rows per table
+</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ3" WIDTH="60%">no limit
+</TD></TR><TR>
+<TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ2" WIDTH="40%">size of table
+</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ3" WIDTH="60%">no limit Some operating systems impose a limit on the size of a single
+file.
+</TD></TR><TR>
+<TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ2" WIDTH="40%">size of row
+</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ3" WIDTH="60%">no limit--rows can span pages. Rows cannot span tables so some
+operating systems impose a limit on the size of a single file, and therefore
+limit the size of a table and size of a row in that table.
+</TD></TR></TABLE>
+<P>For a complete list of restrictions on Derby databases and database
+objects, see the <I>Derby Reference Manual</I>.
+<P><H1><A NAME="HDRSII-DEVELOP-42173">Creating, Dropping, and Backing Up Databases</H1>
+<P>You create new databases and access existing ones by specifying attributes
+to the Derby connection URL (see <A HREF="develop14.html#HDRSII-DEVELOP-22102">Examples</A>).
+<P>
+<A NAME="IDX535"></A>
+<A NAME="IDX536"></A>
+There is no drop database command. To drop a database, delete the
+database directory with operating system commands. The database must
+not be booted when you remove a database. You can get a list of booted
+databases with <I>getPropertyInfo</I> (see <A HREF="develop125.html#HDRSII-ADVJDBC-41138">Offering Connection Choices to the User</A>).
+<P>
+<A NAME="IDX537"></A>
+<A NAME="IDX538"></A>
+To back up a database, you can use the online backup utility. For
+information on this utility, see the <CITE>Derby Server and
+Administration Guide</CITE>.
+<P>You can also use <I>roll-forward recovery</I> to recover a damaged
+database. Derby accomplishes roll-forward recovery by using a full
+backup copy of the database, archived logs, and active logs from the most
+recent time before a failure. For more information on roll-forward
+recovery see the <CITE>Derby Server and Administration
+Guide</CITE>.
+<P><H1><A NAME="HDRDEVELOP845973">Single Database Shutdown</H1>
+<A NAME="IDX539"></A>
+<P>An application can shut down a single database within a Derby system
+and leave the rest of the system running. See &quot;Shutting Down
+Derby or an Individual Database&quot;.
+<P><H1><A NAME="HDRSII-DEVELOP-18166">Storage and Recovery</H1>
+<A NAME="IDX540"></A>
+<P>A Derby database provides persistent storage and recovery.
+Derby ensures that all committed transactions are durable, even if the
+system fails, through the use of a database transaction log. Whereas
+inserts, updates, and deletes may be cached before being written to disk, log
+entries tracking all those changes are never cached but always forced to disk
+when a transaction commits. If the system or operating system fails
+unexpectedly, when Derby next starts up it can use the log to perform
+recovery, recovering the &quot;lost&quot; transactions from the log and rolling
+back uncommitted transactions. <I>Recovery</I> ensures that all
+committed transactions at the time the system failed are applied to the
+database, and all transactions that were active are rolled back. Thus
+the databases are left in a consistent, valid state.
+<P>In normal operation, Derby keeps the log small through periodic
+checkpoints. Checkpointing marks the portions of the log that are no
+longer useful, writes changed pages to disk, then truncates the log.
+<P>Derby checkpoints the log file as it fills. It also checkpoints
+the log when a shutdown command is issued. Shutting down the JVM in
+which Derby is running without issuing the proper shutdown command is
+equivalent to a system failure from Derby's point of view.
+<P>
+<A NAME="IDX541"></A>
+<A NAME="IDX542"></A>
+<A NAME="IDX543"></A>
+Booting a database means that Derby checks to see if recovery needs to be
+run on a database. Recovery can be costly, so using the proper shutdown
+command improves connection or startup performance.
+<P><H1><A NAME="HDRSII-DEVELOP-84026">Log on Separate Device</H1>
+<P>You can put a database's log on a separate device when you create
+it. For more information, see the <CITE>Derby Server and
+Administration Guide</CITE>.
+<P><H1><A NAME="HDRSII-DEVELOP-25820">Database Pages</H1>
+<A NAME="IDX544"></A>
+<P>Derby tables and indexes, known as conglomerates, consist of two or
+more pages. A page is a unit of storage whose size is configurable on a
+system-wide, database-wide, or conglomerate-specific basis. By default,
+a conglomerate grows one page at a time until eight pages of user data (or
+nine pages of total disk use, which includes one page of internal information)
+have been allocated. (You can configure this behavior; see
+<I>&quot;derby.storage.initialPages&quot; </I> in
+<CITE>Tuning Derby</CITE>.) After that, it grows eight pages at
+a time.
+<P>The size of a row or column is not limited by the page size. Rows or
+columns that are longer than the table's page size are automatically
+wrapped to overflow pages.
+<P><H1><A NAME="HDRDEVELOP846110">Database-Wide Properties</H1>
+<A NAME="IDX545"></A>
+<P>You can set many Derby properties as database-level properties.
+When set in this way, they are stored in the database and &quot;travel&quot;
+with the database unless overridden by a system property. For more
+information, see &quot;Database-Wide Properties&quot; in <CITE>Tuning 
+Derby</CITE>.
+<DL><DT><B>Note:</B></DT><DD>It is recommended 
+that you work with database-level properties wherever
+possible.
+</DD></DL>
+<P><H1><A NAME="HDRSII-DEVELOP-30653">Database Limitations</H1>
+<A NAME="IDX546"></A>
+<P>Derby databases have these limitations:
+<UL>
+<LI><I>Indexes are not supported for columns defined on CLOB, BLOB, and LONG
+VARCHAR data types.
+<A NAME="IDX547"></A>
+<A NAME="IDX548"></A>
+</I> 
+<P>If the length of the key columns in an index is larger than half the page
+size of the index, creating an index on those key columns for the table
+fails. For existing indexes, an insert of new rows for which the key
+columns are larger than half of the index page size causes the insert to
+fail.
+<P>It is generally not recommended to create indexes on long columns.
+It is best to create indexes on small columns that provide a quick look-up to
+larger, unwieldy data in the row. You might not see performance
+improvements if you index long columns. For information about indexes,
+see <CITE>Tuning Derby</CITE>.
+</LI><LI><I>The system shuts down if the database log cannot allocate more disk
+space.</I> 
+<P>A &quot;LogFull&quot; error or some sort of <TT><I>IOException</I></TT>
+will occur in the <I>derby.log </I> if the system runs out of
+space. If the system has no more disk space to append to the
+<I>derby.log</I>, you might not see the error messages.
+</LI></UL>
+<P><HR>[ <A HREF="develop12.html">Previous Page</A><br><A HREF="develop14.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop130.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop130.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,33 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Retrieving the Database Connection URL</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="retrieving from database, Database connection URL">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<HR><H1 NAME="HDRSII-TRICKS-19707">Retrieving the Database Connection URL</H1>
+<A NAME="IDX788"></A>
+<P>Derby does not have a built-in function that returns the name of the
+database. However, you can use <I>DatabaseMetaData</I> to return
+the connection URL of any local <TT><I>Connection</I></TT>.
+<PRE><B>/* in java */</B>
+String myURL = conn.getMetaData().getURL();
+ 
+</PRE>
+<P><HR>[ <A HREF="develop129.html">Previous Page</A><br><A HREF="develop131.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop131.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop131.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,42 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Supplying a Parameter Only Once</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="Using a supplied parameter multiple times in a query, power of, VALUES clause">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<HR><H1 NAME="HDRSII-TRICKS-39584">Supplying a Parameter Only Once</H1>
+<A NAME="IDX789"></A>
+<A NAME="IDX790"></A>
+<P>If you want to supply a parameter value once and use it multiple times
+within a query, put it in the FROM clause with an appropriate CAST:
+<PRE>SELECT  phonebook.*&nbsp;
+	FROM phonebook, (VALUES (CAST(? AS INT), CAST(? AS VARCHAR(255))))&nbsp;
+						AS Choice(choice, search_string)
+	WHERE search_string = (case when choice = 1 then firstnme&nbsp;
+                 when choice=2 then lastname&nbsp;
+						when choice=3 then phonenumber end);
+</PRE>
+<P>This query selects what the second parameter will be compared to based on
+the value in the first parameter. Putting the parameters in the FROM
+clause means that they need to be applied only once to the query, and you can
+give them names so that you can refer to them elsewhere in the query.
+In the example above, the first parameter is given the name <I>choice</I>,
+and the second parameter is given the name <I>search_string</I>.
+<P><HR>[ <A HREF="develop130.html">Previous Page</A><br><A HREF="develop132.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop132.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop132.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,45 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Defining an Identity Column</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="defining, Identity column, definition">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<HR><H1 NAME="HDRSII-TRICKS-21248">Defining an Identity Column</H1>
+<A NAME="IDX791"></A>
+<A NAME="IDX792"></A>
+<P>An identity column is a column that stores numbers that increment by one
+with each insertion. Identity columns are sometimes called
+autoincrement columns. Derby provides autoincrement as a built-in
+feature; see CREATE TABLE statement in the <CITE>Derby Reference
+Manual</CITE>.
+<P>Below is an example that shows how to use an identity column to create the
+MAP_ID column of the MAPS table in the <I>toursDB database</I>.
+<PRE>CREATE TABLE MAPS
+(
+MAP_ID INTEGER NOT NULL GENERATED ALWAYS AS IDENTITY (START WITH 1, INCREMENT BY 1),
+MAP_NAME VARCHAR(24) NOT NULL,
+REGION VARCHAR(26),
+AREA DECIMAL(8,4) NOT NULL,
+PHOTO_FORMAT VARCHAR(26) NOT NULL,
+PICTURE BLOB(102400),
+UNIQUE (MAP_ID, MAP_NAME)
+)
+</PRE>
+<P><HR>[ <A HREF="develop131.html">Previous Page</A><br><A HREF="develop133.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop133.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop133.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,27 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Using Third-Party Tools</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<HR><H1 NAME="HDRSII-TRICKS-23426">Using Third-Party Tools</H1>
+<P>You can hook into any JDBC tool with just our JDBC Driver class name
+(<I>org.apache.derby.jdbc.EmbeddedDriver</I>)
+and Derby's JDBC connection URL.
+<P><HR>[ <A HREF="develop132.html">Previous Page</A><br><A HREF="develop134.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop134.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop134.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,26 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Tricks of the VALUES Clause</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="power of, VALUES clause">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<HR><H1 NAME="HDRSII-TRICKS-13019">Tricks of the VALUES Clause</H1>
+<A NAME="IDX793"></A>
+<P><HR>[ <A HREF="develop133.html">Previous Page</A><br><A HREF="develop135.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop135.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop135.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,44 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Multiple Rows</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="Multiple rows VALUES clause">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRTRICKS807337">Multiple Rows</H1>
+<A NAME="IDX794"></A>
+<P>Derby supports the complete SQL-92 VALUES clause; this is very
+handy in several cases. The first useful case is that it can be used to
+insert multiple rows:
+<PRE><B>INSERT INTO OneColumnTable VALUES 1,2,3,4,5,6,7,8
+ 
+INSERT INTO TwoColumnTable VALUES
+    (1, 'first row'),
+    (2, 'second row'),
+    (3, 'third row')</B>
+</PRE>
+<P>Dynamic parameters reduce the number of times execute requests are sent
+across:
+<PRE><B><B>-- send 5 rows at a time:</B>
+PREPARE p1 AS 'INSERT INTO ThreeColumnTable VALUES&nbsp;
+(?,?,?), (?,?,?), (?,?,?), (?,?,?), (?,?,?)
+EXECUTE p1 USING 'VALUES (''1st'',1,1,''2nd'',2,2''3rd'',
+3,3,''4th'',4,4,''5th'',5,5)'</B>
+</PRE>
+<P><HR>[ <A HREF="develop134.html">Previous Page</A><br><A HREF="develop136.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop136.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop136.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,40 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Mapping Column Values to Return Values</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="Mapping column values to return values">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRTRICKS807365">Mapping Column Values to Return Values</H1>
+<A NAME="IDX795"></A>
+<P>Multiple-row VALUES tables are useful in mapping column values to desired
+return values in queries:
+<PRE><B><B>-- get the names of all departments in Ohio</B>
+SELECT DeptName
+FROM Depts,
+(VALUES (1, 'Shoe'),
+    (2, 'Laces'),
+    (4, 'Polish'))
+AS DeptMap(DeptCode,DeptDesc)
+WHERE Depts.DeptCode = DeptMap.DeptCode
+AND Depts.DeptLocn LIKE '%Ohio%'</B>
+</PRE>
+<P>You might also find it useful to store values used often for mapping in a
+persistent table and then using that table in the query.
+<P><HR>[ <A HREF="develop135.html">Previous Page</A><br><A HREF="develop137.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop137.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop137.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,36 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Creating Empty Queries</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="Creating empty queries">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRTRICKS807400">Creating Empty Queries</H1>
+<A NAME="IDX796"></A>
+<P>Developers using Derby in existing applications might need to create
+&quot;empty&quot; queries with the right result shape for filling in bits of
+functionality Derby does not supply. Empty queries of the right
+size and shape can be formed off a single values table and a &quot;WHERE
+FALSE&quot; condition:
+<PRE><B>SELECT *
+FROM (VALUES ('',1,&quot;TRUE&quot;)) AS ProcedureInfo(ProcedureName,NumParameters,&nbsp;
+ProcedureValid)
+WHERE 1=0</B>
+</PRE>
+<P><HR>[ <A HREF="develop136.html">Previous Page</A><br><A HREF="develop138.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop138.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop138.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,43 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Localizing Derby</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="Localization, Internationalization, definition, Locales">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P>
+<HR><H1 NAME="HDRSII-I18N-10613">Localizing Derby</H1>
+<A NAME="IDX797"></A>
+<A NAME="IDX798"></A>
+<P>
+<A NAME="IDX799"></A>
+Derby offers support for locales. The word <I>locale</I> in
+the Java platform refers to an instance of a class that identifies a
+particular combination of language and region. If a Java class varies
+its behavior according to <I>locale</I>, it is said to be
+locale-sensitive. Derby provides some support for locales for
+databases and other components such as the tools and the installer.
+<P>It also provides a feature to support databases in many different
+languages, a feature which is independent of a particular territory.
+See <A HREF="develop139.html#HDRSII-I18N-71274">SQL Parser Support for Unicode</A>.
+<P>When you create or upgrade a database, you can use the territory attribute
+to associate a non-default territory with the database. For information
+about how to use the territory attribute, see the <CITE>Derby
+Reference Manual</CITE>.
+<P><HR>[ <A HREF="develop137.html">Previous Page</A><br><A HREF="develop139.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop139.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop139.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,30 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>SQL Parser Support for Unicode</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="Unicode support">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<HR><H1 NAME="HDRSII-I18N-71274">SQL Parser Support for Unicode</H1>
+<A NAME="IDX800"></A>
+<P>To support users in many different languages, Derby's SQL parser
+understands all Unicode characters and allows any Unicode character or number
+to be used in an identifier. Derby does not attempt to ensure that
+the characters in identifiers are valid in the database's locale.
+<P><HR>[ <A HREF="develop138.html">Previous Page</A><br><A HREF="develop140.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop14.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop14.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,217 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Connecting to Databases</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="connecting, Databases, connecting to within system, connecting to outside system, convention for specifying connection path when outside system, directory subsubprotocol, accessing databases from, Class path, Connecting to databases not directly in the system directory">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-DEVELOP-34964">Connecting to Databases</H1>
+<P>You connect to a database using a form of the Derby connection URL as
+an argument to the <I>DriverManager.getConnection</I> call (see <A HREF="develop11.html#HDRSII-DEVELOP-17453">Derby JDBC Database Connection URL</A>). You specify a path to the database within this
+connection URL.
+<P><H1><A NAME="HDRSII-DEVELOP-19619">Standard Connections--Connecting to Databases in the File System</H1>
+<A NAME="IDX549"></A>
+<P><H1><A NAME="HDRDEVELOP846369">Within the System</H1>
+<A NAME="IDX550"></A>
+<P>The standard way to access databases is in the file system by specifying
+the path to the database, either absolute or relative to the system
+directory. In a client/server environment, this path is always on the
+<I>server</I> machine.
+<P>By default, you can connect to databases within the current system
+directory (see <A HREF="develop12.html#HDRSII-DEVELOP-13018">Defining the System Directory</A>). To connect to databases within the current system,
+just specify the database name on the connection URL. For example, if
+your system directory contains a database called <I>myDB</I>, you can
+connect to that database with the following connection URL:
+<PRE>jdbc:derby:myDB
+</PRE>
+<P>The full call within a Java program would be:
+<PRE>Connection conn =DriverManager.getConnection("jdbc:derby:myDB");
+</PRE>
+<P><H1><A NAME="HDRDEVELOP846402">Outside the System Directory</H1>
+<A NAME="IDX551"></A>
+<P>You can also connect to databases in other directories (including
+subdirectories of the system directory) by specifying a relative or absolute
+path name to identify the database. The way you specify an absolute
+path is defined by the host operating system (see
+<CITE>java.io.File.isAbsolute</CITE>). You must
+specify a path for a database in a directory other than the system directory
+even if you have defined the <TT><I>derby.service</I></TT>
+property to have Derby boot the database automatically (see
+<I>&quot;derby.service&quot;</I> in <CITE>Tuning 
+Derby</CITE>).
+<P>Using the connection URL as described here, you can connect to databases in
+more than one directory at a time.
+<P>Two examples:
+<PRE>jdbc:derby:../otherDirectory/myDB
+ 
+jdbc:derby:c:/otherDirectory/myDB
+</PRE>
+<DL><DT><B>Note:</B></DT><DD>Once connected to, such a database becomes a part of the Derby system,
+even though it is not in the system directory. This means that it takes
+on the system-wide properties of the system and that no other instance of
+Derby should access that database, among other things. It is
+recommended that you connect to databases only in the system directory.
+See <A HREF="develop12.html#HDRSII-DEVELOP-19297">Recommended Practices</A> for suggestions about working with a Derby
+system.
+</DD></DL>
+<P><H1><A NAME="HDRSII-DEVELOP-40350">Conventions for Specifying the Database Path</H1>
+<A NAME="IDX552"></A>
+<P>When accessing databases from the file system (instead of from class path
+or a jar file), any path that is not absolute is interpreted as relative to
+the system directory.
+<P>The path must do one of the following:
+<UL>
+<LI>refer to a previously created Derby database
+</LI><LI>specify the <I>create=true</I> attribute
+</LI></UL>
+<P>The path separator in the connection URL is / (forward slash), as in the
+standard <I>file:// </I>URL protocol.
+<P>You can specify only databases that are local to the machine on which the
+JVM is running. NFS file systems on UNIX and remote shared files on
+Windows (//<I>machine/directory</I>) are not guaranteed to work.
+Using <I>derby.system.home</I> and forward slashes is
+recommended practice for platform independent applications.
+<P>If two different database name values, relative or absolute, refer to the
+same actual directory, they are considered equivalent. This means that
+connections to a database through its absolute path and its relative path are
+connections to the same database. Within Derby, the name of the
+database is defined by the canonical path of its directory from
+<CITE>java.io.File.getCanonicalPath</CITE>.
+<P>Derby automatically creates any intermediate directory that does not
+already exist when creating a new database. If it cannot create the
+intermediate directory, the database creation fails.
+<P>
+<A NAME="IDX553"></A>
+If the path to the database is ambiguous, i.e., potentially the
+same as that to a database that is available on the class path (see
+&quot;Special Database Access&quot;), use the <I>directory:</I>
+subsubprotocol to specify the one in the file system. For
+example:
+<PRE>jdbc:derby:directory:myDB
+</PRE>
+<P><H1><A NAME="HDRSII-DEVELOP-19700">Special Database Access</H1>
+<P>You can also access databases from the class path or from a jar file (in
+the class path or not) as read-only databases.
+<P><H1><A NAME="HDRSII-DEVELOP-91854">From the Class Path</H1>
+<A NAME="IDX554"></A>
+<P>In most cases, you access databases from the file system as described
+above. However, it is also possible to access databases from the class
+path. The databases can be archived into a jar or zip file or left as
+is.
+<P>All such databases are read-only.
+<P>To access an unarchived database from the class path, specify the name of
+the database relative to the directory in the class path. You can use
+the class path subprotocol if such a database is ambiguous within the
+directory system. See <A HREF="develop26.html#HDRSII-DEVELOP-38881">Embedded Derby JDBC Database Connection URL</A> for more information.
+<P>For example, for a database called <I>sample</I> in
+<I>C:\derby\demo\databases</I>, you can put the
+<I>C:\derby\demo\databases</I> directory in the class path and
+access <I>sample</I> like this:
+<PRE>jdbc:derby:/sample
+ 
+</PRE>
+<P>The forward slash is required before <I>sample</I> to indicate that it
+is relative to <I>C:\derby\demo\databases</I> directory.
+<P>If only <I>C:\derby</I> were in the class path, you could
+access <I>sample</I> (read-only) like this:
+<PRE>jdbc:derby:/demo/databases/sample
+ 
+</PRE>
+<P><H1><A NAME="HDRSII-DEVELOP-24155">From a Jar or Zip File</H1>
+<P>It is possible to access databases from a jar file. The jar file can
+be, but does not have to be, on the class path.
+<DL><DT><B>Note:</B></DT><DD>All such databases are read-only.
+</DD></DL>
+<P>For example, suppose you have archived the database <I>jarDB1</I> into
+a file called <I>jar1.jar</I>. This archive is in the class
+path before you start up Derby. You can access <I>jarDB1</I>
+with the following connection URL
+<PRE>jdbc:derby:/jarDB1
+</PRE>
+<P>To access a database in a jar file that is not on the class path, use the
+jar subprotocol.
+<P>For example, suppose you have archived the database <I>jarDB2</I> into
+a file called <I>jar2.jar</I>. This archive is not in the
+class path. You can access <I>jarDB2</I> by specifying the path to
+the jar file along with the jar subsubprotocol, like this:
+<PRE>jdbc:derby:jar:(c:/derby/lib/jar2.jar)jarDB2
+ 
+</PRE>
+<P>For complete instructions and examples of accessing databases in jar files,
+see <A HREF="develop37.html#HDRSII-DEPLOY-11201">Accessing a Read-Only Database in a Zip/Jar</A>.
+<P><H1><A NAME="HDRSII-DEVELOP-22102">Examples</H1>
+<P>
+<A NAME="IDX555"></A>
+<P>The examples in this section use the syntax of the connection URL for use
+in an embedded environment. This information also applies to the client
+connection URL in a client/server environment. For reference
+information about client connection URLs, see
+<I>&quot;java.sql.Connection&quot;</I> in the <CITE>
+Derby Reference Manual</CITE>.
+<UL>
+<LI><I>jdbc:derby:db1</I> 
+<P>Open a connection to the database <I>db1</I>. <I>db1</I> is
+a directory located in the system directory.
+</LI><LI><I>jdbc:derby:london/sales</I> 
+<P>Open a connection to the database <I>london/sales</I>.
+<I>london</I> is a subdirectory of the system directory, and
+<I>sales</I> is a subdirectory of the directory <I>london</I>.
+</LI><LI><I>jdbc:derby:/reference/phrases/french</I> 
+<P>Open a connection to the database
+<I>/reference/phrases/french</I>. 
+<P>On a UNIX system, this would be the path of the directory. On a
+Windows system, the path would be <I>C:\reference\phrases\french</I>
+if the current drive were <I>C. </I>If a jar file storing databases
+were in the user's class path, this could also be a path within the jar
+file.
+</LI><LI><I>jdbc:derby:a:/demo/sample</I> 
+<P>Open a connection to the database stored in the directory
+<I>\demo\sample</I> on drive <I>A</I> (usually the floppy drive) on a
+Windows system.
+</LI><LI><I>jdbc:derby:c:/databases/salesdb 
+<BR>
+jdbc:derby:salesdb</I> 
+<P>These two connection URLs connect to the same database, <I>salesdb</I>,
+on a Windows platform if the system directory of the Derby system is
+<I>C:\databases</I>.
+</LI><LI><I>jdbc:derby:support/bugsdb;create=true</I> 
+<P>Create the database <I>support/bugsdb</I> in the system directory,
+automatically creating the intermediate directory <I>support</I> if it
+does not exist.
+</LI><LI><I>jdbc:derby:sample;shutdown=true</I> 
+<P>Shut down the <I>sample</I> database.
+</LI><LI><I>jdbc:derby:/myDB</I> 
+<P>Access <I>myDB</I> (which is directly in a directory in the class path)
+as a read-only database.
+</LI><LI><I>jdbc:derby:classpath:/myDB</I> 
+<P>Access <I>myDB</I> (which is directly in a directory in the class path)
+as a read-only database. The reason for using the subsubprotocol is
+that it might have the same path as a database in the directory
+structure.
+</LI><LI><I>jdbc:derby:jar:(C:/dbs.jar)products/boiledfood</I>
+<P>
+<P>Access the read-only database <I>boiledfood</I> in the
+<I>products</I> directory from the jar file
+<I>C:/dbs.jar</I>.
+</LI><LI><I>jdbc:derby:directory:myDB</I> 
+<P>Access <I>myDB</I>, which is in the system directory. The reason
+for using the <TT><I>directory:</I></TT> subsubprotocol is that it
+might happen to have the same path as a database in the class path.
+</LI></UL>
+<P><HR>[ <A HREF="develop13.html">Previous Page</A><br><A HREF="develop15.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop140.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop140.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,32 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Derby and Standards</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="and Derby, SQL99 standards">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<HR><H1 NAME="HDRSTNDRDS806118">Derby and Standards</H1>
+<A NAME="IDX801"></A>
+<P>Derby adheres to SQL99 standards wherever possible. Below you
+will find a guide to those features currently in Derby that are not
+standard; these features are currently being evaluated and might be
+removed in future releases.
+<P>This section describes those parts of Derby that are non-standard or
+not typical for a database system:
+<P><HR>[ <A HREF="develop139.html">Previous Page</A><br><A HREF="develop141.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop141.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop141.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,24 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>SQL99</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<HR><H1 NAME="HDRSTNDRDS806055">SQL99</H1>
+<P><HR>[ <A HREF="develop140.html">Previous Page</A><br><A HREF="develop142.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop142.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop142.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,26 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Dynamic SQL</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSTNDRDS805644">Dynamic SQL</H1>
+<P>Derby uses JDBC's Prepared Statement, and does not provide SQL
+commands for dynamic SQL.
+<P><HR>[ <A HREF="develop141.html">Previous Page</A><br><A HREF="develop143.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop143.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop143.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,28 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Cursors</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSTNDRDS805664">Cursors</H1>
+<P>Derby uses JDBC's Result Sets, and does not provide SQL for
+manipulating cursors except for positioned update and delete.
+Derby's scrolling insensitive cursors are provided through JDBC, not
+through SQL commands.
+<P><HR>[ <A HREF="develop142.html">Previous Page</A><br><A HREF="develop144.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop144.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop144.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,26 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Information Schema</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSTNDRDS805690">Information Schema</H1>
+<P>Derby uses its own system catalog and JDBC's DatabaseMetadata,
+and does not provide the standard Information Schema views.
+<P><HR>[ <A HREF="develop143.html">Previous Page</A><br><A HREF="develop145.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop145.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop145.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,26 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Transactions</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSTNDRDS805716">Transactions</H1>
+<P>Derby uses JDBC's Connection, and provides only the SQL command
+SET TRANSACTION ISOLATION for transactions.
+<P><HR>[ <A HREF="develop144.html">Previous Page</A><br><A HREF="develop146.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop146.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop146.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,27 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Stored routines and PSM</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSTNDRDS805742">Stored routines and PSM</H1>
+<P>Derby supports external procedures using the Java programming
+language. Procedures are managed using the CREATE PROCEDURE and DROP
+PROCEDURE statements.
+<P><HR>[ <A HREF="develop145.html">Previous Page</A><br><A HREF="develop147.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop147.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop147.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,26 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Calling functions and procedures</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSTNDRDS805768">Calling functions and procedures</H1>
+<P>Derby supports the CALL (procedure) statement for calling external
+procedures declared by the CREATE PROCEDURE statement.
+<P><HR>[ <A HREF="develop146.html">Previous Page</A><br><A HREF="develop148.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop148.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop148.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,27 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Unique constraints and nulls</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSTNDRDS805841">Unique constraints and nulls</H1>
+<P>The SQL standard defines that unique constraints on nullable columns allow
+any number of nulls; Derby does not permit unique constraints on
+nullable columns.
+<P><HR>[ <A HREF="develop147.html">Previous Page</A><br><A HREF="develop149.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop149.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop149.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,28 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>NOT NULL characteristic</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSTNDRDS805893">NOT NULL characteristic</H1>
+<P>The SQL standard says NOT NULL is a constraint, and can be named and viewed
+in the information schema as such. Derby does not provide naming
+for NOT NULL, nor does it present it as a constraint in the information
+schema, only as a characteristic of the column.
+<P><HR>[ <A HREF="develop148.html">Previous Page</A><br><A HREF="develop150.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop15.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop15.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,168 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Working with the Database Connection URL Attributes</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="Attributes to database connection URL, setting, use of in database connection URL, Database name attribute, accessing, Read-only databases, part of database connection URL syntax, Subsubprotocol, Shutting down a single database, using database connection URL attribute, Shutting down Derby, shutting down individually, Databases, Creating a database, creating, providing a name and password for in connection, Users, encrypting upon creation, booting, Encrypted databases, Attributes (URL), setting as properties, specifying with Properties object">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-DEVELOP-51654">Working with the Database Connection URL Attributes</H1>
+<A NAME="IDX556"></A>
+<P>
+<A NAME="IDX557"></A>
+You specify attributes on the Derby connection URL (see <A HREF="develop11.html#HDRSII-DEVELOP-17453">Derby JDBC Database Connection URL</A>). The examples in this section use the syntax of the
+connection URL for use in an embedded environment. You can also specify
+these same attributes and values on the client connection URL if you are using
+Derby as a database server. For more information, see the <CITE>
+Derby Server and Administration Guide</CITE>.
+<P>You can also set these attributes by passing a <I>Properties</I> object
+along with a connection URL to
+<TT><I>DriverManager.getConnection</I></TT> when obtaining a
+connection; see &quot;Specifying Attributes in a Properties
+Object&quot;.
+<P>All attributes are optional. For detailed information about the
+connection URL syntax and attributes, see &quot;Derby Database Connection
+URL Syntax&quot;in the <CITE>Derby Reference Manual</CITE>.
+<P>You can specify the following attributes:
+<UL>
+<LI><I>bootPassword=key</I>
+</LI><LI><I>create=true</I>
+</LI><LI><I>databaseName=nameofDatabase</I>
+</LI><LI><I>dataEncryption=true</I>
+</LI><LI><I>encryptionProvider=providerName</I>
+</LI><LI><I>encryptionAlgorithm=algorithm</I>
+</LI><LI><I>territory=ll_CC</I>
+</LI><LI><I>logDevice=logDirectoryPath</I>
+</LI><LI><I>createFrom=BackupPath</I>
+</LI><LI><I>restoreFrom=BackupPath</I>
+</LI><LI><I>rollForwardrecoveryFrom=BackupPath</I>
+</LI><LI><I>password=userPassword</I>
+</LI><LI><I>shutdown=true</I>
+</LI><LI><I>user=userName</I>
+</LI></UL>
+<P><H1><A NAME="HDRDEVELOP847152">Using the databaseName Attribute</H1>
+<A NAME="IDX558"></A>
+<PRE>jdbc:derby:;databaseName=<I>databaseName</I>
+ 
+</PRE>
+<P>
+<A NAME="IDX559"></A>
+<A NAME="IDX560"></A>
+You can access read-only databases in jar or zip files by specifying jar as
+the subsubprotocol, like this:
+<PRE>jdbc:derby:jar:(<I>pathToArchive</I>)<I>databasePathWithinArchive</I>
+ 
+</PRE>
+<P>Or, if the jar or zip file has been included in the class path, like
+this:
+<PRE>jdbc:derby:/<I>databasePathWithinArchive</I>
+ 
+</PRE>
+<P><H1><A NAME="HDRSII-DEVELOP-40464">Shutting Down Derby or an Individual Database</H1>
+<A NAME="IDX561"></A>
+<A NAME="IDX562"></A>
+<A NAME="IDX563"></A>
+<P>Applications in an embedded environment shut down the Derby system by
+specifying the <I>shutdown=true</I> attribute in the connection
+URL. To shut down the system, you do not specify a database name, and
+you must not specify any other attribute.
+<PRE>jdbc:derby:;shutdown=true
+ 
+</PRE>
+<P>A successful shutdown always results in an <I>SQLException</I> to
+indicate that Derby has shut down and that there is no other
+exception.
+<P>You can also shut down an individual database if you specify the
+<I>databaseName</I>. You can shut down the database of the current
+connection if you specify the default connection instead of a database
+name<I> </I>(within an SQL statement).
+<PRE><B><B>// shutting down a database from your application</B>
+DriverManager.getConnection(
+    "jdbc:derby:sample;shutdown=true");</B>
+ 
+</PRE>
+<P><H1><A NAME="HDRSII-DEVELOP-39090">Creating and Accessing a Database</H1>
+<A NAME="IDX564"></A>
+<A NAME="IDX565"></A>
+<P>You create a database by supplying a new database name in the connection
+URL and specifying <I>create=true</I>. Derby creates a new
+database inside a new subdirectory in the system directory. This system
+directory has the same name as the new database. If you specify a
+partial path, it is relative to the system directory. You can also
+specify an absolute path.
+<PRE>jdbc:derby:<I>databaseName</I>;create=true
+ 
+</PRE>
+<P>For more details about <I>create=true</I>, see
+<I>&quot;create=true&quot;</I> in the <CITE>Derby Reference
+Manual</CITE>.
+<P><H1><A NAME="HDRSII-DEVELOP-12233">Providing a User Name and Password</H1>
+<A NAME="IDX566"></A>
+<P>When user authentication is enabled, an application must provide a user
+name and password. One way to do this is to use connection URL
+attributes (see <I>user=userName</I> and
+<I>password=userPassword</I>).
+<PRE>jdbc:derby:sample;user=jill;password=toFetchAPail
+</PRE>
+<P>For more information, see <A HREF="develop96.html#HDRSII-CSECUR-42374">Working with User Authentication</A>.
+<P><H1><A NAME="HDRSII-DEVELOP-14496">Encrypting a Database When You Create It</H1>
+<A NAME="IDX567"></A>
+<P>If your environment is configured properly, you can create your database as
+an encrypted database (one in which the database is encrypted on disk).
+To do this, you use the <I>dataEncryption=true</I> attribute to turn on
+encryption and the <TT><I>bootPassword=key</I></TT> attribute to specify
+a key for the encryption. You can also specify an encryption provider
+and encryption algorithm other than the defaults with the
+<TT><I>encryptionProvider=providerName</I></TT> and
+<TT><I>encryptionAlgorithm=algorithm </I></TT>attributes For more
+information about data encryption, see <A HREF="develop112.html#HDRSII-CSECUR-24366">Encrypting Databases on Disk</A>.
+<PRE>jdbc:derby:encryptedDB;create=true;dataEncryption=true;
+bootPassword=DBpassword
+ 
+</PRE>
+<P><H1><A NAME="HDRSII-DEVELOP-40140">Booting an Encrypted Database</H1>
+<A NAME="IDX568"></A>
+<P>You must specify the encryption key with the <I>bootPassword=key</I>
+attribute for an encrypted database when you boot it (which is the first time
+you connect to it within a JVM session or after shutting it down within the
+same JVM session). For more information about data encryption, see <A HREF="develop112.html#HDRSII-CSECUR-24366">Encrypting Databases on Disk</A>.
+<PRE>jdbc:derby:encryptedDB;bootPassword=DBpassword
+ 
+</PRE>
+<P><H1><A NAME="HDRSII-DEVELOP-36289">Specifying Attributes in a Properties Object</H1>
+<A NAME="IDX569"></A>
+<A NAME="IDX570"></A>
+<P>Instead of specifying attributes on the connection URL, you can specify
+attributes as properties in a <I>Properties</I> object that you pass as a
+second argument to the
+<TT><I>DriverManager.getConnection</I></TT> method. For
+example, to set the user name and password:
+<PRE>Class.forName("org.apache.derby.jdbc.EmbeddedDriver");
+ 
+Properties p = new Properties();
+ 
+p.put("user", "sa");
+ 
+p.put("password", "manager");
+ 
+ 
+Connection conn = DriverManager.getConnection(
+ 
+    "jdbc:derby:mynewDB", p);
+</PRE>
+<P><HR>[ <A HREF="develop14.html">Previous Page</A><br><A HREF="develop16.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop150.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop150.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,26 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Fewer reserved keywords</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSTNDRDS805921">Fewer reserved keywords</H1>
+<P>Derby has converted several keywords<B> </B>to be
+non-reserved.
+<P><HR>[ <A HREF="develop149.html">Previous Page</A><br><A HREF="develop151.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop151.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop151.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,27 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>DECIMAL max precision</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSTNDRDS805949">DECIMAL max precision</H1>
+<P>For Derby, the maximum precision for DECIMAL columns is 31
+digits. SQL99 does not require a specific maximum precision for
+decimals, but most products have a maximum precision of 15-32 digits.
+<P><HR>[ <A HREF="develop150.html">Previous Page</A><br><A HREF="develop152.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop152.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop152.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,25 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>CLOB, and BLOB</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSTNDRDS805975">CLOB, and BLOB</H1>
+<P>Derby supports the standard CLOB and BLOB data types.
+<P><HR>[ <A HREF="develop151.html">Previous Page</A><br><A HREF="develop153.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop153.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop153.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,39 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Expressions on LONGs</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSTNDRDS806001">Expressions on LONGs</H1>
+<P>Derby permits expressions on LONG VARCHAR; however LONG VARCHAR
+data types are not allowed in:
+<UL>
+<LI>GROUP BY clauses
+</LI><LI>ORDER BY clauses
+</LI><LI>JOIN operations
+</LI><LI>PRIMARY KEY constraints
+</LI><LI>Foreign KEY constraints
+</LI><LI>UNIQUE key constraints
+</LI><LI>MIN aggregate function
+</LI><LI>MAX aggregate function
+</LI><LI>[NOT] IN predicate
+</LI><LI>UNION operator
+</LI></UL>
+<P>SQL99 also places some restrictions on expressions on LONG types.
+<P><HR>[ <A HREF="develop152.html">Previous Page</A><br><A HREF="develop154.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop154.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop154.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,26 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>ALTER TABLE</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSTNDRDS806027">ALTER TABLE</H1>
+<P>Slightly different ALTER TABLE syntax for altering column defaults.
+SQL99 uses DROP and SET, we use DEFAULT.
+<P><HR>[ <A HREF="develop153.html">Previous Page</A><br><A HREF="develop156.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop156.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop156.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,50 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Trademarks</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<HR><H1 NAME="HDRTRADEM">Trademarks</H1>
+<P>The following terms are trademarks of International Business Machines
+Corporation in the United States, other countries, or both, and have been used
+in at least one of the documents in the DB2 UDB documentation library.
+<BR>
+<TABLE >
+<TR>
+<TD ALIGN="LEFT" VALIGN="TOP" WIDTH="50%">
+Cloudscape<BR>
+DB2<BR>
+DB2 Universal Database<BR>
+</TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH="50%">
+DRDA<BR>
+IBM<BR>
+WebSphere<BR>
+</TD></TR></TABLE>
+<P>The following terms are trademarks or registered trademarks of other
+companies and have been used in at least one of the documents in the IBM
+Cloudscape documentation library:
+<P>Microsoft, Windows, Windows NT, and the Windows logo are trademarks of
+Microsoft Corporation in the United States, other countries, or both.
+<P>Java and all Java-based trademarks are trademarks of Sun Microsystems,
+Inc. in the United States, other countries, or both.
+<P>UNIX is a registered trademark of The Open Group in the United States and
+other countries.
+<P>Other company, product, or service names may be trademarks or service marks
+of others.
+<P><HR>[ <A HREF="develop154.html">Previous Page</A><br><A HREF="develop157.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop157.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop157.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,1360 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Index</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P>
+<BR>
+<HR><H1 NAME="HDRINDEX_START">Index</H1>
+<strong><a href="#IDX0_41">A</a></strong>
+<ul class="indexlist">
+<li>Access
+<ul class="indexlist">
+<li>full (read-write) versus read-only
+<A HREF="develop109.html#IDX756">(756)</A>
+</li>
+</ul>
+</li>
+<li>Accessing read-only databases from class path
+<A HREF="develop38.html#IDX612">(612)</A>
+</li>
+<li>APIs for public classes and interfaces
+<A HREF="develop17.html#IDX574">(574)</A>
+</li>
+<li>Archiving read-only databases
+<A HREF="develop36.html#IDX606">(606)</A>, <A HREF="develop36.html#IDX610">(610)</A>
+</li>
+<li>Attributes (URL), setting as properties
+<A HREF="develop15.html#IDX569">(569)</A>
+</li>
+<li>Attributes to database connection URL
+<A HREF="develop15.html#IDX556">(556)</A>
+<ul class="indexlist">
+<li>setting
+<A HREF="develop15.html#IDX557">(557)</A>
+</li>
+<li>specifying with Properties object
+<A HREF="develop15.html#IDX570">(570)</A>
+</li>
+</ul>
+</li>
+<li>Authentication
+<A HREF="develop96.html#IDX731">(731)</A>
+<ul class="indexlist">
+<li>definition
+<A HREF="develop94.html#IDX725">(725)</A>
+</li>
+</ul>
+</li>
+<li>Authentication provider
+<ul class="indexlist">
+<li>specifying
+<A HREF="develop99.html#IDX734">(734)</A>
+</li>
+</ul>
+</li>
+<li>Authorization
+<A HREF="develop108.html#IDX753">(753)</A>
+</li>
+<li>Authorization identifiers
+<A HREF="develop104.html#IDX749">(749)</A>
+</li>
+<li>Auto-commit
+<ul class="indexlist">
+<li>and transactions
+<A HREF="develop63.html#IDX653">(653)</A>
+</li>
+<li>turning off
+<A HREF="develop63.html#IDX656">(656)</A>
+</li>
+<li>turning off with JDBC
+<A HREF="develop63.html#IDX655">(655)</A>
+</li>
+<li>using
+<A HREF="develop63.html#IDX654">(654)</A>
+</li>
+</ul>
+</li>
+<li>Autocommit
+<ul class="indexlist">
+<li>holdable cursors and
+<A HREF="develop69.html#IDX672">(672)</A>
+</li>
+</ul>
+</li>
+<li>Automatic booting
+<ul class="indexlist">
+<li>of databases in system
+<A HREF="develop12.html#IDX514">(514)</A>
+</li>
+</ul>
+</li>
+<li>Available databases
+<ul class="indexlist">
+<li>list of provided by databaseName attribute
+<A HREF="develop125.html#IDX783">(783)</A>
+</li>
+</ul>
+</li>
+</ul>
+<strong><a href="#IDX0_42">B</a></strong>
+<ul class="indexlist">
+<li>Backing up databases
+<A HREF="develop13.html#IDX537">(537)</A>
+</li>
+<li>Batch files
+<A HREF="develop18.html#IDX576">(576)</A>
+</li>
+</ul>
+<strong><a href="#IDX0_43">C</a></strong>
+<ul class="indexlist">
+<li>Class path
+<ul class="indexlist">
+<li>accessing databases from
+<A HREF="develop14.html#IDX554">(554)</A>
+</li>
+</ul>
+</li>
+<li>Classes
+<ul class="indexlist">
+<li>storing in database
+<A HREF="develop40.html#IDX617">(617)</A>
+</li>
+</ul>
+</li>
+<li>classpath subsubprotocol
+<A HREF="develop26.html#IDX585">(585)</A>
+</li>
+<li>DERBY_INSTALL environment variable
+<A HREF="develop17.html#IDX572">(572)</A>
+</li>
+<li>derby.log
+<A HREF="develop12.html#IDX512">(512)</A>
+</li>
+<li>derby.properties file
+<A HREF="develop12.html#IDX509">(509)</A>, <A HREF="develop12.html#IDX520">(520)</A>
+</li>
+<li>Derby system
+<A HREF="develop12.html#IDX506">(506)</A>
+</li>
+<li>derby.system.home
+<ul class="indexlist">
+<li>used to define system directory
+<A HREF="develop12.html#IDX517">(517)</A>
+</li>
+</ul>
+</li>
+<li>Columns
+<ul class="indexlist">
+<li>maximum number allowed per table
+<A HREF="develop13.html#IDX532">(532)</A>
+</li>
+</ul>
+</li>
+<li>com.ibm.derby.database.UserUtility
+<A HREF="develop109.html#IDX758">(758)</A>
+</li>
+<li>org.apache.derby.jdbc.EmbeddedConnectionPoolDataSource
+<A HREF="develop88.html#IDX721">(721)</A>
+</li>
+<li>org.apache.derby.jdbc.EmbeddedDataSource
+<A HREF="develop88.html#IDX720">(720)</A>
+</li>
+<li>org.apache.derby.jdbc.EmbeddedXADataSource
+<A HREF="develop88.html#IDX722">(722)</A>
+</li>
+<li>Concurrency
+<A HREF="develop70.html#IDX676">(676)</A>
+</li>
+<li>Connecting to a database
+<A HREF="develop28.html#IDX595">(595)</A>
+</li>
+<li>Connecting to databases
+<ul class="indexlist">
+<li>in embedded mode
+<A HREF="develop28.html#IDX594">(594)</A>
+</li>
+<li>when path is ambiguous because of databases in class path
+<A HREF="develop38.html#IDX615">(615)</A>
+</li>
+<li>when path is ambiguous with databases in file system
+<A HREF="develop38.html#IDX614">(614)</A>
+</li>
+</ul>
+</li>
+<li>Connecting to databases not directly in the system directory
+<A HREF="develop14.html#IDX555">(555)</A>
+</li>
+<li>Connecting to multiple databases
+<A HREF="develop62.html#IDX648">(648)</A>
+</li>
+<li>Connections
+<ul class="indexlist">
+<li>getting
+<A HREF="develop62.html#IDX647">(647)</A>
+</li>
+</ul>
+</li>
+<li>Creating a database
+<ul class="indexlist">
+<li>using database connection URL attribute
+<A HREF="develop15.html#IDX564">(564)</A>
+</li>
+</ul>
+</li>
+<li>Creating empty queries
+<A HREF="develop137.html#IDX796">(796)</A>
+</li>
+<li>derby.jar
+<A HREF="develop32.html#IDX600">(600)</A>
+</li>
+<li>Cursors
+<ul class="indexlist">
+<li>accessing system-generated names
+<A HREF="develop66.html#IDX665">(665)</A>
+</li>
+<li>all result sets as
+<A HREF="develop62.html#IDX650">(650)</A>
+</li>
+<li>holdable
+<A HREF="develop69.html#IDX670">(670)</A>
+</li>
+<li>naming
+<A HREF="develop66.html#IDX663">(663)</A>, <A HREF="develop66.html#IDX664">(664)</A>
+</li>
+<li>requirements for being updatable
+<A HREF="develop66.html#IDX661">(661)</A>
+</li>
+<li>scrolling insensitive
+<A HREF="develop68.html#IDX669">(669)</A>
+</li>
+<li>updatable
+<A HREF="develop66.html#IDX662">(662)</A>
+</li>
+<li>working with
+<A HREF="develop64.html#IDX659">(659)</A>
+</li>
+</ul>
+</li>
+</ul>
+<strong><a href="#IDX0_44">D</a></strong>
+<ul class="indexlist">
+<li>Data encryption
+<ul class="indexlist">
+<li>configuring
+<A HREF="develop115.html#IDX767">(767)</A>
+</li>
+<li>providers
+<A HREF="develop114.html#IDX765">(765)</A>
+</li>
+</ul>
+</li>
+<li>Database class loading
+<A HREF="develop40.html#IDX616">(616)</A>
+</li>
+<li>Database connection URL
+<ul class="indexlist">
+<li>description
+<A HREF="develop11.html#IDX504">(504)</A>
+</li>
+<li>features common to embedded and client/server versions
+<A HREF="develop11.html#IDX505">(505)</A>
+</li>
+<li>retrieving from database
+<A HREF="develop130.html#IDX788">(788)</A>
+</li>
+<li>syntax
+<A HREF="develop26.html#IDX581">(581)</A>
+</li>
+<li>using
+<A HREF="develop26.html#IDX587">(587)</A>
+</li>
+</ul>
+</li>
+<li>Database encryption
+<A HREF="develop112.html#IDX762">(762)</A>
+</li>
+<li>Database name attribute
+<ul class="indexlist">
+<li>use of in database connection URL
+<A HREF="develop15.html#IDX558">(558)</A>
+</li>
+</ul>
+</li>
+<li>Database pages
+<ul class="indexlist">
+<li>description
+<A HREF="develop13.html#IDX544">(544)</A>
+</li>
+</ul>
+</li>
+<li>Database-side JDBC procedures
+<A HREF="develop48.html#IDX622">(622)</A>
+<ul class="indexlist">
+<li>and SQLExceptions
+<A HREF="develop52.html#IDX632">(632)</A>
+</li>
+<li>definition
+<A HREF="develop49.html#IDX624">(624)</A>
+</li>
+<li>example of connecting to different database
+<A HREF="develop51.html#IDX630">(630)</A>
+</li>
+<li>using nested connections
+<A HREF="develop50.html#IDX625">(625)</A>
+</li>
+<li>using non-nested connections
+<A HREF="develop51.html#IDX629">(629)</A>
+</li>
+</ul>
+</li>
+<li>Database-side procedures
+<ul class="indexlist">
+<li>definition
+<A HREF="develop49.html#IDX623">(623)</A>
+</li>
+</ul>
+</li>
+<li>Databases
+<ul class="indexlist">
+<li>backing up
+<A HREF="develop13.html#IDX538">(538)</A>
+</li>
+<li>configuring
+<A HREF="develop13.html#IDX545">(545)</A>
+</li>
+<li>connecting
+<A HREF="develop14.html#IDX549">(549)</A>
+</li>
+<li>connecting to outside system
+<A HREF="develop14.html#IDX551">(551)</A>
+</li>
+<li>connecting to within system
+<A HREF="develop14.html#IDX550">(550)</A>
+</li>
+<li>controlling access to
+<A HREF="develop109.html#IDX755">(755)</A>
+</li>
+<li>convention for specifying connection path when outside system
+<A HREF="develop14.html#IDX552">(552)</A>
+</li>
+<li>creating
+<A HREF="develop15.html#IDX565">(565)</A>
+</li>
+<li>description of in Derby system
+<A HREF="develop13.html#IDX522">(522)</A>
+</li>
+<li>dropping
+<A HREF="develop13.html#IDX535">(535)</A>
+</li>
+<li>encrypting
+<A HREF="develop112.html#IDX763">(763)</A>
+</li>
+<li>encrypting upon creation
+<A HREF="develop15.html#IDX567">(567)</A>
+</li>
+<li>shutting down individually
+<A HREF="develop15.html#IDX563">(563)</A>
+</li>
+</ul>
+</li>
+<li>Deadlock detection
+<A HREF="develop75.html#IDX701">(701)</A>
+</li>
+<li>Deadlocks
+<ul class="indexlist">
+<li>description
+<A HREF="develop75.html#IDX700">(700)</A>
+</li>
+<li>detecting
+<A HREF="develop75.html#IDX702">(702)</A>
+</li>
+<li>programming an application to handle
+<A HREF="develop75.html#IDX703">(703)</A>
+</li>
+</ul>
+</li>
+<li>Deployment modes
+<ul class="indexlist">
+<li>threading/connection modes and
+<A HREF="develop77.html#IDX705">(705)</A>
+</li>
+</ul>
+</li>
+<li>directory subsubprotocol
+<A HREF="develop14.html#IDX553">(553)</A>, <A HREF="develop26.html#IDX584">(584)</A>
+</li>
+<li>Dirty reads
+<ul class="indexlist">
+<li>definition
+<A HREF="develop71.html#IDX682">(682)</A>
+</li>
+</ul>
+</li>
+<li>Disk encryption
+<A HREF="develop94.html#IDX727">(727)</A>
+</li>
+<li>DriverPropertyInfo Array
+<A HREF="develop126.html#IDX784">(784)</A>
+</li>
+<li>Dropping databases
+<A HREF="develop13.html#IDX536">(536)</A>
+</li>
+</ul>
+<strong><a href="#IDX0_45">E</a></strong>
+<ul class="indexlist">
+<li>Embedded applications
+<ul class="indexlist">
+<li>deploying
+<A HREF="develop31.html#IDX597">(597)</A>
+</li>
+</ul>
+</li>
+<li>Embedded environments
+<A HREF="develop31.html#IDX596">(596)</A>, <A HREF="develop32.html#IDX601">(601)</A>
+<ul class="indexlist">
+<li>Derby as single-user database
+<A HREF="develop31.html#IDX598">(598)</A>
+</li>
+<li>how applications interact with Derby in
+<A HREF="develop31.html#IDX599">(599)</A>
+</li>
+<li>how to deploy Derby
+<A HREF="develop32.html#IDX602">(602)</A>
+</li>
+</ul>
+</li>
+<li>Encrypted databases
+<ul class="indexlist">
+<li>booting
+<A HREF="develop15.html#IDX568">(568)</A>, <A HREF="develop115.html#IDX771">(771)</A>
+</li>
+<li>creating
+<A HREF="develop115.html#IDX766">(766)</A>
+</li>
+</ul>
+</li>
+<li>Encrypting databases
+<A HREF="develop94.html#IDX728">(728)</A>
+</li>
+<li>Encryption
+<ul class="indexlist">
+<li>configuring
+<A HREF="develop115.html#IDX768">(768)</A>
+</li>
+<li>providers
+<A HREF="develop114.html#IDX764">(764)</A>
+</li>
+</ul>
+</li>
+<li>Encryption algorithms
+<ul class="indexlist">
+<li>configuring
+<A HREF="develop115.html#IDX770">(770)</A>
+</li>
+</ul>
+</li>
+<li>Encryption providers
+<ul class="indexlist">
+<li>configuring
+<A HREF="develop115.html#IDX769">(769)</A>
+</li>
+</ul>
+</li>
+<li>Error log
+<A HREF="develop12.html#IDX511">(511)</A>
+<ul class="indexlist">
+<li>description
+<A HREF="develop12.html#IDX519">(519)</A>
+</li>
+</ul>
+</li>
+<li>Exclusive locks
+<ul class="indexlist">
+<li>definition
+<A HREF="develop74.html#IDX696">(696)</A>
+</li>
+</ul>
+</li>
+<li>Explicit close of JDBC objects
+<A HREF="develop63.html#IDX657">(657)</A>
+</li>
+<li>External directory services
+<ul class="indexlist">
+<li>used to provide user authentication
+<A HREF="develop100.html#IDX735">(735)</A>
+</li>
+</ul>
+</li>
+</ul>
+<strong><a href="#IDX0_46">F</a></strong>
+<ul class="indexlist">
+<li>File descriptors
+<ul class="indexlist">
+<li>configuring to run Derby
+<A HREF="develop22.html#IDX578">(578)</A>
+</li>
+</ul>
+</li>
+<li>Full access
+<ul class="indexlist">
+<li>definition
+<A HREF="develop110.html#IDX761">(761)</A>
+</li>
+</ul>
+</li>
+</ul>
+<strong><a href="#IDX0_47">G</a></strong>
+<ul class="indexlist">
+<li>getPropertyInfo
+<ul class="indexlist">
+<li>using
+<A HREF="develop126.html#IDX785">(785)</A>
+</li>
+</ul>
+</li>
+<li>Getting a nested connection
+<ul class="indexlist">
+<li>using database connection URL attribute
+<A HREF="develop27.html#IDX589">(589)</A>
+</li>
+</ul>
+</li>
+</ul>
+<strong><a href="#IDX0_48">H</a></strong>
+<ul class="indexlist">
+<li>Holdable cursors and autocommit
+<A HREF="develop69.html#IDX671">(671)</A>
+</li>
+</ul>
+<strong><a href="#IDX0_49">I</a></strong>
+<ul class="indexlist">
+<li>Identity column
+<ul class="indexlist">
+<li>defining
+<A HREF="develop132.html#IDX791">(791)</A>
+</li>
+<li>definition
+<A HREF="develop132.html#IDX792">(792)</A>
+</li>
+</ul>
+</li>
+<li>IDEs
+<ul class="indexlist">
+<li>and need to use server framework
+<A HREF="develop127.html#IDX787">(787)</A>
+</li>
+<li>using Derby with
+<A HREF="develop127.html#IDX786">(786)</A>
+</li>
+</ul>
+</li>
+<li>Indexes
+<ul class="indexlist">
+<li>limitations of
+<A HREF="develop13.html#IDX547">(547)</A>
+</li>
+<li>maximum number allowed per table
+<A HREF="develop13.html#IDX531">(531)</A>
+</li>
+<li>not supported for CLOB, BLOB, and LONG VARCHAR data types
+<A HREF="develop13.html#IDX548">(548)</A>
+</li>
+</ul>
+</li>
+<li>Installation directory
+<ul class="indexlist">
+<li>layout of
+<A HREF="develop17.html#IDX571">(571)</A>
+</li>
+</ul>
+</li>
+<li>Internationalization
+<A HREF="develop138.html#IDX798">(798)</A>
+</li>
+<li>interrupt calls
+<ul class="indexlist">
+<li>caught by Derby
+<A HREF="develop84.html#IDX714">(714)</A>
+</li>
+</ul>
+</li>
+<li>IOExceptions
+<ul class="indexlist">
+<li>indicating need to relax file descriptors limit
+<A HREF="develop22.html#IDX579">(579)</A>
+</li>
+</ul>
+</li>
+<li>Isolation levels
+<A HREF="develop70.html#IDX674">(674)</A>
+<ul class="indexlist">
+<li>configuring
+<A HREF="develop72.html#IDX689">(689)</A>
+</li>
+</ul>
+</li>
+</ul>
+<strong><a href="#IDX0_4A">J</a></strong>
+<ul class="indexlist">
+<li>jar directory
+<ul class="indexlist">
+<li>function
+<A HREF="develop13.html#IDX527">(527)</A>
+</li>
+</ul>
+</li>
+<li>jar files
+<ul class="indexlist">
+<li>databases in
+<A HREF="develop36.html#IDX609">(609)</A>
+</li>
+<li>installing, removing, and replacing
+<A HREF="develop43.html#IDX621">(621)</A>
+</li>
+<li>loading signed
+<A HREF="develop41.html#IDX620">(620)</A>, <A HREF="develop116.html#IDX772">(772)</A>
+</li>
+<li>storing in database
+<A HREF="develop40.html#IDX618">(618)</A>
+</li>
+</ul>
+</li>
+<li>Jar files
+</li>
+<li>jar subsubprotocol
+<A HREF="develop26.html#IDX586">(586)</A>
+</li>
+<li>Java 2 Security Manager
+<A HREF="develop121.html#IDX776">(776)</A>
+</li>
+<li>java.sql.Connection.TRANSACTION_READ_COMMITTED
+<A HREF="develop71.html#IDX678">(678)</A>, <A HREF="develop71.html#IDX679">(679)</A>
+</li>
+<li>java.sql.Connection.TRANSACTION_READ_UNCOMMITTED
+<A HREF="develop71.html#IDX677">(677)</A>
+</li>
+<li>java.sql.Connection.TRANSACTION_SERIALIZABLE
+<A HREF="develop71.html#IDX680">(680)</A>
+</li>
+<li>java.sql.Driver.getPropertyInfo
+<A HREF="develop125.html#IDX782">(782)</A>
+</li>
+<li>JDBC
+<ul class="indexlist">
+<li>tutorial for
+<A HREF="develop08.html#IDX502">(502)</A>
+</li>
+</ul>
+</li>
+<li>JDBC Connections
+<A HREF="develop61.html#IDX644">(644)</A>
+<ul class="indexlist">
+<li>definition
+<A HREF="develop62.html#IDX646">(646)</A>
+</li>
+</ul>
+</li>
+<li>JDBC driver
+<ul class="indexlist">
+<li>description
+<A HREF="develop10.html#IDX503">(503)</A>
+</li>
+</ul>
+</li>
+<li>JDBC driver (embedded)
+<A HREF="develop25.html#IDX580">(580)</A>
+<ul class="indexlist">
+<li>starting
+<A HREF="develop28.html#IDX592">(592)</A>
+</li>
+</ul>
+</li>
+<li>JDBC Statement
+<ul class="indexlist">
+<li>definition
+<A HREF="develop62.html#IDX649">(649)</A>
+</li>
+</ul>
+</li>
+<li>JNDI properties for user authorization
+<ul class="indexlist">
+<li>setting
+<A HREF="develop100.html#IDX741">(741)</A>
+</li>
+</ul>
+</li>
+<li>jndid
+<ul class="indexlist">
+<li>required for LDAP user authorization
+<A HREF="develop100.html#IDX738">(738)</A>
+</li>
+</ul>
+</li>
+<li>JVMs (Java Virtual Machines)
+<ul class="indexlist">
+<li>verified for Derby
+<A HREF="develop19.html#IDX577">(577)</A>
+</li>
+</ul>
+</li>
+</ul>
+<strong><a href="#IDX0_4C">L</a></strong>
+<ul class="indexlist">
+<li>LDAP directory services
+<ul class="indexlist">
+<li>used to provide user authentication
+<A HREF="develop100.html#IDX737">(737)</A>
+</li>
+</ul>
+</li>
+<li>ldap.jar
+<ul class="indexlist">
+<li>required for LDAP user authorization
+<A HREF="develop100.html#IDX739">(739)</A>
+</li>
+</ul>
+</li>
+<li>Limitations
+<ul class="indexlist">
+<li>in current version
+<A HREF="develop13.html#IDX546">(546)</A>
+</li>
+</ul>
+</li>
+<li>Locales
+<ul class="indexlist">
+<li>definition
+<A HREF="develop138.html#IDX799">(799)</A>
+</li>
+</ul>
+</li>
+<li>Localization
+<A HREF="develop138.html#IDX797">(797)</A>
+</li>
+<li>Lock granularity
+<A HREF="develop73.html#IDX690">(690)</A>
+</li>
+<li>Locking
+<A HREF="develop70.html#IDX675">(675)</A>
+<ul class="indexlist">
+<li>row-level
+<A HREF="develop73.html#IDX692">(692)</A>
+</li>
+<li>table-level
+<A HREF="develop73.html#IDX691">(691)</A>
+</li>
+</ul>
+</li>
+<li>Locks
+<ul class="indexlist">
+<li>exclusive
+<A HREF="develop74.html#IDX693">(693)</A>
+</li>
+<li>scope of
+<A HREF="develop74.html#IDX699">(699)</A>
+</li>
+<li>shared
+<A HREF="develop74.html#IDX694">(694)</A>
+</li>
+<li>update
+<A HREF="develop74.html#IDX695">(695)</A>
+</li>
+</ul>
+</li>
+<li>log directory
+<ul class="indexlist">
+<li>function
+<A HREF="develop13.html#IDX523">(523)</A>
+</li>
+</ul>
+</li>
+<li>Logic
+<ul class="indexlist">
+<li>storing in database
+<A HREF="develop40.html#IDX619">(619)</A>
+</li>
+</ul>
+</li>
+</ul>
+<strong><a href="#IDX0_4D">M</a></strong>
+<ul class="indexlist">
+<li>Mapping column values to return values
+<A HREF="develop136.html#IDX795">(795)</A>
+</li>
+<li>Multi-threaded applications
+<A HREF="develop77.html#IDX706">(706)</A>
+</li>
+<li>Multi-user database access
+<ul class="indexlist">
+<li>programming for
+<A HREF="develop78.html#IDX709">(709)</A>
+</li>
+</ul>
+</li>
+<li>Multiple connections
+<ul class="indexlist">
+<li>from multiple applications connecting to server
+<A HREF="develop77.html#IDX708">(708)</A>
+</li>
+<li>from single application running in embedded mode
+<A HREF="develop77.html#IDX707">(707)</A>
+</li>
+<li>in single application
+<A HREF="develop76.html#IDX704">(704)</A>
+</li>
+</ul>
+</li>
+<li>Multiple JVMs accessing
+<ul class="indexlist">
+<li>prohibition of
+<A HREF="develop12.html#IDX513">(513)</A>
+</li>
+</ul>
+</li>
+<li>Multiple rows VALUES clause
+<A HREF="develop135.html#IDX794">(794)</A>
+</li>
+<li>Multiple threads sharing single connection
+<A HREF="develop80.html#IDX710">(710)</A>
+</li>
+</ul>
+<strong><a href="#IDX0_4E">N</a></strong>
+<ul class="indexlist">
+<li>Nested connections
+<ul class="indexlist">
+<li>definition
+<A HREF="develop62.html#IDX651">(651)</A>
+</li>
+<li>getting
+<A HREF="develop27.html#IDX588">(588)</A>, <A HREF="develop27.html#IDX590">(590)</A>, <A HREF="develop50.html#IDX626">(626)</A>, <A HREF="develop50.html#IDX627">(627)</A>
+</li>
+<li>limitations of
+<A HREF="develop50.html#IDX628">(628)</A>
+</li>
+</ul>
+</li>
+<li>Non-repeatable reads
+<ul class="indexlist">
+<li>definition
+<A HREF="develop71.html#IDX683">(683)</A>
+</li>
+</ul>
+</li>
+</ul>
+<strong><a href="#IDX0_50">P</a></strong>
+<ul class="indexlist">
+<li>Passwords
+<A HREF="develop101.html#IDX744">(744)</A>
+<ul class="indexlist">
+<li>no encryption of
+<A HREF="develop103.html#IDX748">(748)</A>
+</li>
+<li>providing
+<A HREF="develop103.html#IDX747">(747)</A>
+</li>
+</ul>
+</li>
+<li>Permissions
+<A HREF="develop110.html#IDX759">(759)</A>
+<ul class="indexlist">
+<li>database access
+<A HREF="develop122.html#IDX779">(779)</A>
+</li>
+<li>granting to Derby
+<A HREF="develop122.html#IDX777">(777)</A>
+</li>
+<li>mandatory
+<A HREF="develop122.html#IDX778">(778)</A>
+</li>
+<li>optional
+<A HREF="develop122.html#IDX780">(780)</A>
+</li>
+</ul>
+</li>
+<li>Phantom reads
+<ul class="indexlist">
+<li>definition
+<A HREF="develop71.html#IDX684">(684)</A>
+</li>
+</ul>
+</li>
+<li>Policy files
+<ul class="indexlist">
+<li>and Derby permissions
+<A HREF="develop121.html#IDX775">(775)</A>
+</li>
+<li>examples
+<A HREF="develop123.html#IDX781">(781)</A>
+</li>
+</ul>
+</li>
+<li>Processing SQLExceptions
+<A HREF="develop86.html#IDX717">(717)</A>
+</li>
+<li>Properties
+<ul class="indexlist">
+<li>defined for system in derby.properties
+<A HREF="develop12.html#IDX510">(510)</A>
+</li>
+</ul>
+</li>
+<li>providerutil.jar
+<ul class="indexlist">
+<li>required for LDAP user authentication
+<A HREF="develop100.html#IDX740">(740)</A>
+</li>
+</ul>
+</li>
+</ul>
+<strong><a href="#IDX0_52">R</a></strong>
+<ul class="indexlist">
+<li>Read-only access
+<ul class="indexlist">
+<li>definition
+<A HREF="develop110.html#IDX760">(760)</A>
+</li>
+</ul>
+</li>
+<li>Read-only databases
+<ul class="indexlist">
+<li>accessing
+<A HREF="develop15.html#IDX559">(559)</A>
+</li>
+<li>accessing in zip/jar files
+<A HREF="develop37.html#IDX611">(611)</A>
+</li>
+<li>archiving to jar or zip files
+<A HREF="develop36.html#IDX607">(607)</A>
+</li>
+<li>creating
+<A HREF="develop34.html#IDX604">(604)</A>
+</li>
+<li>deploying
+<A HREF="develop35.html#IDX605">(605)</A>
+</li>
+<li>putting in class path
+<A HREF="develop38.html#IDX613">(613)</A>
+</li>
+<li>working with
+<A HREF="develop33.html#IDX603">(603)</A>
+</li>
+</ul>
+</li>
+<li>Recovery
+<A HREF="develop13.html#IDX540">(540)</A>, <A HREF="develop13.html#IDX543">(543)</A>
+</li>
+<li>Referential actions
+<ul class="indexlist">
+<li>and triggers
+<A HREF="develop56.html#IDX637">(637)</A>
+</li>
+</ul>
+</li>
+<li>Referential integrity
+<ul class="indexlist">
+<li>via triggers
+<A HREF="develop56.html#IDX639">(639)</A>
+</li>
+</ul>
+</li>
+<li>Resource manager
+<ul class="indexlist">
+<li>Derby as in J2EE system
+<A HREF="develop87.html#IDX719">(719)</A>
+</li>
+</ul>
+</li>
+<li>Restarting Derby within same JVM
+<A HREF="develop12.html#IDX515">(515)</A>
+</li>
+<li>ResultSets
+<ul class="indexlist">
+<li>behavior of with auto-commit
+<A HREF="develop67.html#IDX666">(666)</A>
+</li>
+<li>scrolling insensitive (JDBC 2.0)
+<A HREF="develop68.html#IDX668">(668)</A>
+</li>
+<li>working with
+<A HREF="develop64.html#IDX660">(660)</A>
+</li>
+</ul>
+</li>
+<li>Rollback
+<ul class="indexlist">
+<li>implicit versus explicit
+<A HREF="develop63.html#IDX658">(658)</A>
+</li>
+</ul>
+</li>
+<li>Rows
+<ul class="indexlist">
+<li>maximum number allowed per table
+<A HREF="develop13.html#IDX533">(533)</A>
+</li>
+<li>size limitations
+<A HREF="develop13.html#IDX534">(534)</A>
+</li>
+</ul>
+</li>
+</ul>
+<strong><a href="#IDX0_53">S</a></strong>
+<ul class="indexlist">
+<li>Sample applications and databases
+<ul class="indexlist">
+<li>description
+<A HREF="develop17.html#IDX573">(573)</A>
+</li>
+</ul>
+</li>
+<li>Schemas
+<ul class="indexlist">
+<li>and users
+<A HREF="develop105.html#IDX751">(751)</A>
+</li>
+</ul>
+</li>
+<li>Scrolling insensitive cursors
+<A HREF="develop68.html#IDX667">(667)</A>
+</li>
+<li>Security
+<ul class="indexlist">
+<li>configuring
+<A HREF="develop95.html#IDX729">(729)</A>
+</li>
+</ul>
+</li>
+<li>Security features
+<A HREF="develop93.html#IDX723">(723)</A>
+<ul class="indexlist">
+<li>limitations of
+<A HREF="develop117.html#IDX774">(774)</A>
+</li>
+</ul>
+</li>
+<li>seg0 directory
+<A HREF="develop13.html#IDX524">(524)</A>
+</li>
+<li>service.properties file
+<A HREF="develop13.html#IDX525">(525)</A>
+</li>
+<li>Shared locks
+<ul class="indexlist">
+<li>definition
+<A HREF="develop74.html#IDX697">(697)</A>
+</li>
+</ul>
+</li>
+<li>Shell scripts
+<A HREF="develop18.html#IDX575">(575)</A>
+</li>
+<li>Shutdown
+<ul class="indexlist">
+<li>description
+<A HREF="develop13.html#IDX542">(542)</A>
+</li>
+</ul>
+</li>
+<li>Shutting down a single database
+<A HREF="develop13.html#IDX539">(539)</A>, <A HREF="develop15.html#IDX561">(561)</A>
+</li>
+<li>Shutting down Derby
+<ul class="indexlist">
+<li>using database connection URL attribute
+<A HREF="develop15.html#IDX562">(562)</A>
+</li>
+</ul>
+</li>
+<li>Signed jar files
+<A HREF="develop116.html#IDX773">(773)</A>
+</li>
+<li>single system
+<ul class="indexlist">
+<li>prohibition of
+<A HREF="develop12.html#IDX513">(513)</A>
+</li>
+</ul>
+</li>
+<li>Size limitations of Derby objects and databases
+<A HREF="develop13.html#IDX528">(528)</A>
+</li>
+<li>SQL99 standards
+<ul class="indexlist">
+<li>and Derby
+<A HREF="develop140.html#IDX801">(801)</A>
+</li>
+</ul>
+</li>
+<li>SQLExceptions
+<ul class="indexlist">
+<li>chaining of
+<A HREF="develop86.html#IDX716">(716)</A>
+</li>
+<li>importance of not catching within database-side procedures
+<A HREF="develop52.html#IDX631">(631)</A>
+</li>
+<li>user-defined (38001-38999)
+<A HREF="develop53.html#IDX633">(633)</A>
+</li>
+<li>working with
+<A HREF="develop85.html#IDX715">(715)</A>
+</li>
+</ul>
+</li>
+<li>SQLWarnings
+<A HREF="develop86.html#IDX718">(718)</A>
+</li>
+<li>Start-up
+<ul class="indexlist">
+<li>description
+<A HREF="develop13.html#IDX541">(541)</A>
+</li>
+</ul>
+</li>
+<li>Starting Derby
+<A HREF="develop28.html#IDX593">(593)</A>
+<ul class="indexlist">
+<li>embedded mode
+<A HREF="develop28.html#IDX591">(591)</A>
+</li>
+</ul>
+</li>
+<li>Statements shared by threads
+<ul class="indexlist">
+<li>dangers of
+<A HREF="develop83.html#IDX711">(711)</A>
+</li>
+</ul>
+</li>
+<li>Subprotocol
+<ul class="indexlist">
+<li>part of database connection URL syntax
+<A HREF="develop26.html#IDX582">(582)</A>
+</li>
+</ul>
+</li>
+<li>Subsubprotocol
+<ul class="indexlist">
+<li>part of database connection URL syntax
+<A HREF="develop15.html#IDX560">(560)</A>, <A HREF="develop26.html#IDX583">(583)</A>
+</li>
+</ul>
+</li>
+<li>System
+<ul class="indexlist">
+<li>description
+<A HREF="develop12.html#IDX508">(508)</A>
+</li>
+</ul>
+</li>
+<li>System directory
+<A HREF="develop12.html#IDX507">(507)</A>
+<ul class="indexlist">
+<li>creating and naming directory for
+<A HREF="develop12.html#IDX521">(521)</A>
+</li>
+<li>default
+<A HREF="develop12.html#IDX518">(518)</A>
+</li>
+<li>specifying
+<A HREF="develop12.html#IDX516">(516)</A>
+</li>
+</ul>
+</li>
+</ul>
+<strong><a href="#IDX0_54">T</a></strong>
+<ul class="indexlist">
+<li>Tables
+<ul class="indexlist">
+<li>maximum number allowed per database
+<A HREF="develop13.html#IDX529">(529)</A>
+</li>
+<li>size limitations
+<A HREF="develop13.html#IDX530">(530)</A>
+</li>
+</ul>
+</li>
+<li>Threads
+<ul class="indexlist">
+<li>notifying
+<A HREF="develop84.html#IDX713">(713)</A>
+</li>
+<li>sleep and interrupt calls
+<A HREF="develop84.html#IDX712">(712)</A>
+</li>
+</ul>
+</li>
+<li>tmp directory
+<ul class="indexlist">
+<li>function
+<A HREF="develop13.html#IDX526">(526)</A>
+</li>
+</ul>
+</li>
+<li>Transaction anomalies in generic database systems
+<ul class="indexlist">
+<li>description
+<A HREF="develop71.html#IDX681">(681)</A>
+</li>
+</ul>
+</li>
+<li>Transaction isolation levels
+<A HREF="develop70.html#IDX673">(673)</A>
+</li>
+<li>TRANSACTION_READ_COMMITTED isolation level
+<A HREF="develop71.html#IDX687">(687)</A>
+</li>
+<li>TRANSACTION_READ_UNCOMMITTED isolation level
+<A HREF="develop71.html#IDX688">(688)</A>
+</li>
+<li>TRANSACTION_REPEATABLE_READ isolation level
+<A HREF="develop71.html#IDX686">(686)</A>
+</li>
+<li>TRANSACTION_SERIALIZABLE isolation level
+<A HREF="develop71.html#IDX685">(685)</A>
+</li>
+<li>Transactions
+<A HREF="develop61.html#IDX645">(645)</A>
+<ul class="indexlist">
+<li>definition
+<A HREF="develop63.html#IDX652">(652)</A>
+</li>
+</ul>
+</li>
+<li>Triggers
+<ul class="indexlist">
+<li>accessing before and after rows
+<A HREF="develop57.html#IDX640">(640)</A>
+</li>
+<li>and exceptions
+<A HREF="develop59.html#IDX642">(642)</A>
+</li>
+<li>automatic rollback of trigger actions
+<A HREF="develop59.html#IDX643">(643)</A>
+</li>
+<li>example of trigger actions
+<A HREF="develop58.html#IDX641">(641)</A>
+</li>
+<li>limitations of trigger actions
+<A HREF="develop55.html#IDX636">(636)</A>
+</li>
+<li>programming trigger actions
+<A HREF="develop54.html#IDX634">(634)</A>
+</li>
+<li>use of SQL and Java in trigger actions
+<A HREF="develop55.html#IDX635">(635)</A>
+</li>
+<li>use of to perform referential actions
+<A HREF="develop56.html#IDX638">(638)</A>
+</li>
+</ul>
+</li>
+</ul>
+<strong><a href="#IDX0_55">U</a></strong>
+<ul class="indexlist">
+<li>Unicode support
+<A HREF="develop139.html#IDX800">(800)</A>
+</li>
+<li>Update locks
+<A HREF="develop74.html#IDX698">(698)</A>
+</li>
+<li>User authentication
+<A HREF="develop96.html#IDX730">(730)</A>
+<ul class="indexlist">
+<li>definition
+<A HREF="develop94.html#IDX724">(724)</A>
+</li>
+<li>enabling
+<A HREF="develop98.html#IDX732">(732)</A>
+</li>
+<li>programming applications for
+<A HREF="develop103.html#IDX745">(745)</A>
+</li>
+<li>use of external directory service for
+<A HREF="develop100.html#IDX736">(736)</A>
+</li>
+</ul>
+</li>
+<li>User authorization
+<A HREF="develop108.html#IDX752">(752)</A>
+<ul class="indexlist">
+<li>definition
+<A HREF="develop94.html#IDX726">(726)</A>
+</li>
+<li>for databases
+<A HREF="develop109.html#IDX754">(754)</A>
+</li>
+<li>providing your own
+<A HREF="develop100.html#IDX742">(742)</A>
+</li>
+</ul>
+</li>
+<li>User names
+<ul class="indexlist">
+<li>providing
+<A HREF="develop103.html#IDX746">(746)</A>
+</li>
+</ul>
+</li>
+<li>Users
+<ul class="indexlist">
+<li>and schemas
+<A HREF="develop105.html#IDX750">(750)</A>
+</li>
+<li>Derby's built-in repository
+<A HREF="develop101.html#IDX743">(743)</A>
+</li>
+<li>defining for a system
+<A HREF="develop99.html#IDX733">(733)</A>
+</li>
+<li>providing a name and password for in connection
+<A HREF="develop15.html#IDX566">(566)</A>
+</li>
+</ul>
+</li>
+<li>UserUtility
+<A HREF="develop109.html#IDX757">(757)</A>
+</li>
+<li>Using a supplied parameter multiple times in a query
+<A HREF="develop131.html#IDX789">(789)</A>
+</li>
+</ul>
+<strong><a href="#IDX0_56">V</a></strong>
+<ul class="indexlist">
+<li>VALUES clause
+<ul class="indexlist">
+<li>power of
+<A HREF="develop131.html#IDX790">(790)</A>, <A HREF="develop134.html#IDX793">(793)</A>
+</li>
+</ul>
+</li>
+</ul>
+<strong><a href="#IDX0_5A">Z</a></strong>
+<ul class="indexlist">
+<li>Zip files
+<ul class="indexlist">
+<li>databases in
+<A HREF="develop36.html#IDX608">(608)</A>
+</li>
+</ul>
+</li>
+</ul>
+<P><HR>[ <A HREF="develop156.html">Previous Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop16.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop16.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,33 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>After Installing</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<HR><H1 NAME="HDRSII-START-19524">After Installing</H1>
+<P>This chapter provides reference information about the installation
+directory, JVMs, class path, upgrades, and platform-specific issues.
+<P>Review the <TT>install.html</TT> file that is installed with
+Derby for information on installing the Derby development
+environment. See the Release Notes for information on platform support,
+changes that may affect your existing applications, defect information, and
+recent documentation updates. See <CITE>Getting Started with 
+Derby</CITE> for basic product descriptions, information on getting
+started, and directions for setting the path and the classpath.
+<P><HR>[ <A HREF="develop15.html">Previous Page</A><br><A HREF="develop17.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop17.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop17.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,69 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>The Installation Directory</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="layout of, Installation directory, DERBY_INSTALL environment variable, description, Sample applications and databases, APIs for public classes and interfaces">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<HR><H1 NAME="HDRSII-START-16043">The Installation Directory</H1>
+<A NAME="IDX571"></A>
+<P>The installation program installs the Derby software in a directory of
+your choice. See the<TT> install.html</TT> file for
+information on how to install Derby.
+<P>
+<A NAME="IDX572"></A>
+The installer automatically creates setup scripts that include an environment
+variable called DERBY_INSTALL. The installer's value is set to
+the Derby base directory.
+<PRE>C:&gt;echo %DERBY_INSTALL%
+C:\derby_install_directory
+</PRE>
+<P>If you want to set your own environment, <CITE>Getting Started with 
+Derby</CITE> instructs you on setting its value to the directory in which
+you installed the Derby software.
+<P>The installer for Derby installs all the files you need, including the
+documentation set, some example applications, and a sample database.
+<P>Details about the installation:
+<UL>
+<LI><I>index.html </I>in the top-level directory is the top page
+for the on-line documentation.
+</LI><LI><I>release_notes.html</I>, in the top-level Derby base
+directory, contains important last-minute information. <I>Read it
+first</I>.
+</LI><LI><I>
+<A NAME="IDX573"></A>
+/demo</I> contains some sample applications, useful scripts, and prebuilt
+databases. 
+<UL>
+<LI><I>/databases</I> includes prebuilt sample databases.
+</LI><LI><I>/programs</I> includes sample applications.
+</LI></UL>
+</LI><LI><I>/doc</I> contains the on-line documentation (including this
+document).
+</LI><LI><I>/frameworks</I> contains utilities and scripts for running
+Derby.
+</LI><LI><I>
+<A NAME="IDX574"></A>
+/javadoc</I> contains the documented APIs for the public classes and
+interfaces. Typically, you use the JDBC interface to interact with
+Derby; however, you can use some of these additional classes in
+certain situations.
+</LI><LI><I>/lib</I> contains the Derby libraries.
+</LI></UL>
+<P><HR>[ <A HREF="develop16.html">Previous Page</A><br><A HREF="develop18.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop18.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop18.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,33 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Batch Files and Shell Scripts</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="Shell scripts, Batch files">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSTART813142">Batch Files and Shell Scripts</H1>
+<A NAME="IDX575"></A>
+<A NAME="IDX576"></A>
+<P>The <I>/frameworks/embedded/bin</I> directory contains scripts for
+running some of the Derby tools and utilities. To customize your
+environment, put the directory first in your path.
+<P>These scripts serve as examples to help you get started with these tools
+and utilities on any platform. However, they can require modification
+in order to run properly on certain platforms.
+<P><HR>[ <A HREF="develop17.html">Previous Page</A><br><A HREF="develop19.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop19.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop19.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,29 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Derby and JVMs</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="verified for Derby, JVMs (Java Virtual Machines)">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<HR><H1 NAME="HDRSII-START-18978">Derby and JVMs</H1>
+<P>
+<A NAME="IDX577"></A>
+Derby is a database engine written completely in Java; it will run
+in any JVM, version 1.3 or higher. 
+<P><HR>[ <A HREF="develop18.html">Previous Page</A><br><A HREF="develop20.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop20.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop20.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,29 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Derby Libraries and Class Path</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<HR><H1 NAME="HDRSII-START-98282">Derby Libraries and Class Path</H1>
+<P>Derby libraries are located in the /<I>lib</I> subdirectory of the
+Derby base directory. You must set the class path on your
+development machine to include the appropriate libraries.
+<P><CITE>Getting Started with Derby</CITE><CITE> </CITE>explains how to
+set the class path in a development environment.
+<P><HR>[ <A HREF="develop19.html">Previous Page</A><br><A HREF="develop21.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop21.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop21.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,24 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>UNIX-Specific Issues</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<HR><H1 NAME="HDRSII-START-41260">UNIX-Specific Issues</H1>
+<P><HR>[ <A HREF="develop20.html">Previous Page</A><br><A HREF="develop22.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop22.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop22.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,34 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Configuring File Descriptors</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="configuring to run Derby, File descriptors, indicating need to relax file descriptors limit, IOExceptions">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-START-39409">Configuring File Descriptors</H1>
+<A NAME="IDX578"></A>
+<A NAME="IDX579"></A>
+<P>Derby databases create one file per table or index. Some
+operating systems limit the number of files an application can open at one
+time. If the default is a low number, such as 64, you might run into
+unexpected <I>IOExceptions</I> (wrapped in
+<TT><I>SQLExceptions</I></TT>). If your operating system lets you
+configure the number of file descriptors, set this number to a higher
+value.
+<P><HR>[ <A HREF="develop21.html">Previous Page</A><br><A HREF="develop23.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop23.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop23.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,31 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Scripts</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSTART813545">Scripts</H1>
+<P>Your installation contains executable script files that simplify invoking
+the Derby tools. On UNIX systems, these files might need to have
+their default protections set to include execute privilege. A typical
+way to do this is with the command <I>chmod +x
+*.ksh</I>.
+<P>Consult the documentation for your operating system for system-specific
+details.
+<P><HR>[ <A HREF="develop22.html">Previous Page</A><br><A HREF="develop24.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop24.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop24.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,28 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Derby Embedded Basics</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<HR><H1 NAME="HDRSII-DEVELOP-25174">Derby Embedded Basics</H1>
+<P>This section explains how to use and configure Derby in an embedded
+environment. Included in the installation is a sample application
+program, <I>/demo/programs/simple</I>, which illustrates how to run
+Derby embedded in the calling program.
+<P><HR>[ <A HREF="develop23.html">Previous Page</A><br><A HREF="develop25.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop25.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop25.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,35 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Embedded Derby JDBC Driver</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="JDBC driver (embedded)">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<HR><H1 NAME="HDRSII-DEVELOP-40170">Embedded Derby JDBC Driver</H1>
+<A NAME="IDX580"></A>
+<P>The Derby driver class name for the embedded environment is
+<I>org.apache.derby.jdbc.EmbeddedDriver</I>.
+In a Java application, you typically load the driver with the static
+<TT><I>Class.forName</I></TT> method or with the
+<TT><I>jdbc.drivers</I></TT> system property. For more
+information, see &quot;Starting Derby as an Embedded Database&quot;.
+<P>For detailed information about loading the Derby JDBC driver, see
+<I>&quot;java.sql.Driver&quot;</I> in the <CITE>Derby
+Reference Manual</CITE><CITE>.</CITE>
+<P><HR>[ <A HREF="develop24.html">Previous Page</A><br><A HREF="develop26.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop26.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop26.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,73 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Embedded Derby JDBC Database Connection URL</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="syntax, Database connection URL, part of database connection URL syntax, Subprotocol, Subsubprotocol, directory subsubprotocol, classpath subsubprotocol, jar subsubprotocol, using">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<HR><H1 NAME="HDRSII-DEVELOP-38881">Embedded Derby JDBC Database Connection URL</H1>
+<A NAME="IDX581"></A>
+<P>The standard Derby JDBC connection URL, which you can use for tasks
+besides connecting to a database, is
+<PRE>jdbc:derby:[subsubprotocol:][<I>databaseName</I>][;<I>attribute</I>=<I>value</I>]*
+</PRE>
+<P>
+<A NAME="IDX582"></A>
+<I>derby</I> is always the <I>subprotocol</I> for connecting to a
+Derby database.
+<P><I>
+<A NAME="IDX583"></A>
+Subsubprotocol</I>, which is not typically specified, determines how
+Derby looks for a database: in a directory, in a class path, or in
+a jar file. Subsubprotocol is one of the following:
+<UL>
+<LI><I>
+<A NAME="IDX584"></A>
+directory</I> The default. Specify this explicitly only to
+distinguish a database that might be ambiguous with one on the class
+path.
+</LI><LI><I>
+<A NAME="IDX585"></A>
+classpath</I> Databases are treated as read-only databases, and all
+<I>databaseNames</I> must begin with at least a slash, because you specify
+them &quot;relative&quot; to the class path directory.
+</LI><LI><I>
+<A NAME="IDX586"></A>
+jar</I> Databases are treated as read-only databases.
+<I>DatabaseNames</I> might require a leading slash, because you specify
+them &quot;relative&quot; to the jar file.
+</LI></UL>
+<P><I>jar</I> requires an additional element immediately before the
+database name:
+<PRE>(<I>pathToArchive</I>)
+</PRE>
+<P><I>pathToArchive</I> is the path to the jar or zip file that holds the
+database.
+<P>For examples of using this syntax, see <A HREF="develop37.html#HDRSII-DEPLOY-11201">Accessing a Read-Only Database in a Zip/Jar</A>.
+<P>You typically pass the connection URL as an argument to the JDBC
+<I>DriverManager.getConnection</I> method call. For
+example:
+<PRE>DriverManager.getConnection("jdbc:derby:sample");
+<A NAME="IDX587"></A>
+</PRE>
+<P>You can specify attributes and attribute values to a connection URL.
+For more information about what you can specify with the Derby connection
+URL, see <A HREF="develop14.html#HDRSII-DEVELOP-22102">Examples</A>. For detailed reference about attributes and values,
+see the <CITE>Derby Reference Manual</CITE>.
+<P><HR>[ <A HREF="develop25.html">Previous Page</A><br><A HREF="develop27.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop27.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop27.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,40 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Getting a Nested Connection</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="getting, Nested connections, using database connection URL attribute, Getting a nested connection">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<HR><H1 NAME="HDRSII-DEVELOP-10252">Getting a Nested Connection</H1>
+<A NAME="IDX588"></A>
+<A NAME="IDX589"></A>
+<A NAME="IDX590"></A>
+<P>When you are executing a method within SQL, that method might need to reuse
+the current connection to the database in order to execute more SQL
+statements. Such a connection is called a<I> nested
+connection</I>. The way for a method to get a nested connection is to
+issue a connection request using the connection URL.
+<PRE>jdbc:default:connection
+</PRE>
+<P>URL attributes are not supported as part of this connection URL. Any
+URL attributes specified in a Properties object, user name, or password that
+are passed to a
+<I>java.sql.DriverManager.getConnection()</I> call
+will be ignored.
+<P><HR>[ <A HREF="develop26.html">Previous Page</A><br><A HREF="develop28.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop28.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop28.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,60 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Starting Derby as an Embedded Database</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="embedded mode, Starting Derby, starting, JDBC driver (embedded), in embedded mode, Connecting to databases, Connecting to a database">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<HR><H1 NAME="HDRSII-DEVELOP-38381">Starting Derby as an Embedded Database</H1>
+<A NAME="IDX591"></A>
+<A NAME="IDX592"></A>
+<P>To start Derby, you start the Derby JDBC driver. Starting
+the Derby driver starts up the complete Derby system within the
+current JVM.
+<P>For example, when using the JBDC driver manager directly within Java code,
+you typically start a JDBC driver in one of two ways:
+<UL>
+<LI>Specify the <I>jdbc.drivers</I> system property, which allows
+users to customize the JDBC drivers used by their applications. For
+example: 
+<PRE>java -Djdbc.drivers=org.apache.derby.jdbc.EmbeddedDriver <I>applicationClass
+<A NAME="IDX593"></A>
+</I></PRE>
+</LI></UL>
+<UL>
+<LI>Load the class directly from Java code using the static method
+<I>Class.forName</I>. For example: 
+<PRE>Class.forName("org.apache.derby.jdbc.EmbeddedDriver");&nbsp;
+ 
+</PRE>
+</LI></UL>
+<P>For more details, see <I>&quot;java.sql.Driver&quot;</I> in
+the <CITE>Derby Reference Manual</CITE><CITE>.</CITE>
+<P><A NAME="SPTSII-DEVELOP-15566"></A>
+<A NAME="IDX594"></A>
+Once the Derby JDBC driver class has been loaded, you can connect to any
+Derby database by passing the embedded connection URL with the
+appropriate attributes to the <I>DriverManager.getConnection</I>
+method.
+<P>
+<A NAME="IDX595"></A>
+For example:
+<PRE>Connection conn = DriverManager.getConnection("jdbc:derby:sample");
+</PRE>
+<P><HR>[ <A HREF="develop27.html">Previous Page</A><br><A HREF="develop29.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop29.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop29.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,35 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Deploying Derby Applications</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<HR><H1 NAME="HDRSII-DEPLOY-32171">Deploying Derby Applications</H1>
+<P>Typically, once you have developed a Derby application and database,
+you package up the application, the Derby libraries, and the database in
+some means for distribution to your users. This process is called
+<I>deployment</I>.
+<P>This chapter discusses issues for deploying Derby applications and
+databases.
+<UL>
+<LI><A HREF="develop30.html#HDRSII-DEPLOY-38918">Deployment Issues</A>
+</LI><LI><A HREF="develop33.html#HDRSII-DEPLOY-15325">Creating Derby Databases for Read-Only Use</A>
+</LI><LI><A HREF="develop40.html#HDRSII-DEPLOY-30736">Loading Classes from a Database</A>
+</LI></UL>
+<P><HR>[ <A HREF="develop28.html">Previous Page</A><br><A HREF="develop30.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop30.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop30.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,29 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Deployment Issues</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<HR><H1 NAME="HDRSII-DEPLOY-38918">Deployment Issues</H1>
+<P>This section discusses deployment options and details.
+<UL>
+<LI><A HREF="develop31.html#HDRDEPLOY855368">Embedded Deployment Application Overview</A>
+</LI><LI><A HREF="develop32.html#HDRSII-DEPLOY-37603">Deployment Cheat Sheets</A>
+</LI></UL>
+<P><HR>[ <A HREF="develop29.html">Previous Page</A><br><A HREF="develop31.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop31.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop31.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,58 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Embedded Deployment Application Overview</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="Embedded environments, deploying, Embedded applications, Derby as single-user database, how applications interact with Derby in">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRDEPLOY855368">Embedded Deployment Application Overview</H1>
+<A NAME="IDX596"></A>
+<A NAME="IDX597"></A>
+<P>In an embedded environment, Derby runs in the same JVM as the
+application. The application can be a single-user application or a
+multi-user application server. In the latter case, Derby runs
+embedded in the user-provided server framework, and any client applications
+use user-provided connectivity or allow the application server to handle all
+database interaction.
+<P><B><A NAME="FIGSII-DEPLOY-31527">Figure 3. Derby embedded in a single-user Java application</A></B><BR>
+<BR><IMG SRC="images/embed.gif" ALT="Derby in a single-user application scenario."><BR>
+<P><B><A NAME="FIGSII-DEPLOY-29107">Figure 4. Derby embedded in a multi-user Java application server</A></B><BR>
+<BR><IMG SRC="images/itserv.gif" ALT="Derby in a multi-user application scenario."><BR>
+<P>
+<A NAME="IDX598"></A>
+When a Derby database is embedded in a Java application, the database is
+dedicated to that single application. If you deploy more than one copy
+of the application, <I>each application has its own copy of the database and
+Derby software</I>. A Derby server framework can work in
+multi-threaded, multi-connection mode and can even connect to more than one
+database at a time. A server framework, such as the Derby Network
+Server, can be used to manage multiple connections and handle network
+capabilities. Some server framework solutions, such as WebSphere
+Application Server, provide additional features such as web services and
+connection pooling. However, only one server framework at a time can
+operate against a Derby database.
+<P>The Derby application accesses an embedded Derby database through
+the JDBC API. To connect, an application makes a call to the local
+Derby JDBC driver. Accessing the JDBC driver automatically starts
+the embedded Derby software. The calling application is
+responsible for shutting down the embedded Derby database
+software. 
+<A NAME="IDX599"></A>
+<P>
+<P><HR>[ <A HREF="develop30.html">Previous Page</A><br><A HREF="develop32.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop32.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop32.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,61 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Deployment Cheat Sheets</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="derby.jar, Embedded environments, how to deploy Derby">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-DEPLOY-37603">Deployment Cheat Sheets</H1>
+<P><H1><A NAME="HDRDEPLOY855655">Deploying Derby in an Embedded Environment</H1>
+<P>
+<A NAME="IDX600"></A>
+You can &quot;embed&quot; Derby in any Java application (single- or
+multi-user) by deploying the following package:
+<A NAME="IDX601"></A>
+<UL>
+<LI>
+<A NAME="IDX602"></A>
+the Derby library (<I>derby.jar</I>)
+</LI><LI>the application's libraries 
+<P>You have the option of storing these libraries in the database. (See
+<A HREF="develop40.html#HDRSII-DEPLOY-30736">Loading Classes from a Database</A>.)
+</LI><LI>the database or databases used by the application, in the context of their
+system directory (see <A HREF="#HDRSII-DEPLOY-18639">Embedded Systems and Properties</A>) 
+<P><B><A NAME="FIGSII-DEPLOY-21165">Figure 5. Deploying an application, embedded Derby software, and the database. Storing the application in the database and setting properties as database-wide properties simplify deployment.</A></B><BR>
+<BR><IMG SRC="images/edeploy.gif" ALT="Graphic 1; A slightly more complicated deployment with the application and properties outside of the database. Graphic 2; A simplified deployment with application and properties stored in the database."><BR>
+</LI></UL>
+<P><H1><A NAME="HDRSII-DEPLOY-18639">Embedded Systems and Properties</H1>
+<UL>
+<LI>Are any system-wide properties being set that could be set as
+database-wide properties? Database-wide properties are stored in the database
+and are simpler for deployment. System-wide parameters might be easier
+for development.
+</LI><LI>Are any properties being set in the
+<I>derby.properties</I> file? Database-wide properties are
+stored in the database and are simpler for deployment. Some properties
+can only be set on a system-wide basis. If so, deploy the entire system
+directory along with the properties file. Deploy only those databases
+that you wish to include. Setting properties programmatically can
+simplify this step-- you will not have to worry about deploying the
+system directory/properties file.
+</LI></UL>
+<P>Before deploying your application, read <A HREF="develop12.html#HDRSII-DEVELOP-19297">Recommended Practices</A>.
+<P>Extra steps are required for deploying an application and an embedded
+database on read-only media. See <A HREF="develop33.html#HDRSII-DEPLOY-15325">Creating Derby Databases for Read-Only Use</A>.
+<P><HR>[ <A HREF="develop31.html">Previous Page</A><br><A HREF="develop33.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop33.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop33.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,38 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Creating Derby Databases for Read-Only Use</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="working with, Read-only databases">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<HR><H1 NAME="HDRSII-DEPLOY-15325">Creating Derby Databases for Read-Only Use</H1>
+<A NAME="IDX603"></A>
+<P>You can create Derby databases for use on read-only media such as
+CD-ROMs. Derby databases in zip or jar files are also read-only
+databases. Typically, read-only databases are deployed with an
+application in an embedded environment.
+<UL>
+<LI><A HREF="develop34.html#HDRSII-DEPLOY-26887">Creating and Preparing the Database for Read-Only Use</A>
+</LI><LI><A HREF="develop35.html#HDRSII-DEPLOY-19136">Deploying the Database on the Read-Only Media</A>
+</LI><LI><A HREF="develop36.html#HDRSII-DEPLOY-33704">Transferring Read-Only Databases to Archive (Jar or Zip) Files</A>
+</LI><LI><A HREF="develop37.html#HDRSII-DEPLOY-11201">Accessing a Read-Only Database in a Zip/Jar</A>
+</LI><LI><A HREF="develop38.html#HDRSII-DEPLOY-39856">Accessing Databases-in-a-Jar in the Class Path</A>
+</LI><LI><A HREF="develop39.html#HDRSII-DEPLOY-82529">Databases on Read-Only Media and DatabaseMetaData</A>
+</LI></UL>
+<P><HR>[ <A HREF="develop32.html">Previous Page</A><br><A HREF="develop34.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop34.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop34.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,58 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Creating and Preparing the Database for Read-Only Use</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="creating, Read-only databases">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-DEPLOY-26887">Creating and Preparing the Database for Read-Only Use</H1>
+<A NAME="IDX604"></A>
+<P>To create databases for use on read-only media:
+<OL TYPE=1>
+<LI>Create and populate the database on read-write media.
+</LI><LI>Commit all transactions and shut down Derby in the prescribed manner
+(see <A HREF="develop15.html#HDRSII-DEVELOP-40464">Shutting Down Derby or an Individual Database</A>). 
+<P>If you do not shut down Derby in the prescribed manner, Derby
+will need to perform recovery the next time the system boots.
+Derby cannot perform recovery on read-only media.
+</LI><LI>Delete the <I>tmp</I> directory if one was created within your
+database directory. If you include this directory, Derby will
+attempt to delete it and will return errors when attempting to boot a database
+on read-only media.
+</LI><LI>For the read-only database, set the property
+<I>derby.storage.tempDirectory</I> to a writable
+location. Derby needs to write to temporary files for large sorts
+required by such SQL statements as ORDER BY, UNION, DISTINCT, and GROUP
+BY. For more information about this property, see
+<TT><I>&quot;derby.storage.tempDirectory&quot;</I></TT>
+in <CITE>Tuning Derby</CITE>. For example: 
+<PRE>derby.storage.tempDirectory=c:/temp/mytemp
+</PRE> 
+<P>Be sure to set this property such that it is deployed with the
+database. For more information, see <A HREF="develop32.html#HDRSII-DEPLOY-18639">Embedded Systems and Properties</A>.
+</LI><LI>Configure the database to send error messages to a writable file or to an
+output stream. For information, see the
+<I>derby.stream.xxx</I> properties in <CITE>Tuning 
+Derby</CITE>. 
+<PRE>derby.stream.error.file=c:/temp/mylog.LOG
+</PRE> 
+<P>Be sure to set this property such that it is deployed with the
+database. For more information, see <A HREF="develop32.html#HDRSII-DEPLOY-18639">Embedded Systems and Properties</A>.
+</LI></OL>
+<P><HR>[ <A HREF="develop33.html">Previous Page</A><br><A HREF="develop35.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop35.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop35.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,34 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Deploying the Database on the Read-Only Media</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="deploying, Read-only databases">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-DEPLOY-19136">Deploying the Database on the Read-Only Media</H1>
+<A NAME="IDX605"></A>
+<OL TYPE=1>
+<LI>Move the database directory to the read-only media, including the
+necessary subdirectory directories (<I>log</I> and <I>seg0</I>) and
+the file <TT><I>service.properties</I></TT>.
+</LI><LI>Use the database as usual, with the following exception: 
+<P>You will not be able to insert or update any data in the database or create
+or drop dictionary objects.
+</LI></OL>
+<P><HR>[ <A HREF="develop34.html">Previous Page</A><br><A HREF="develop36.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop36.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop36.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,75 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Transferring Read-Only Databases to Archive (Jar or Zip) Files</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="Archiving read-only databases, archiving to jar or zip files, Read-only databases, databases in, Zip files, Jar files">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-DEPLOY-33704">Transferring Read-Only Databases to Archive (Jar or Zip) Files</H1>
+<A NAME="IDX606"></A>
+<A NAME="IDX607"></A>
+<A NAME="IDX608"></A>
+<A NAME="IDX609"></A>
+<P>Once a database has been created in Derby, it can be stored in a jar
+or zip file and continue to be accessed by Derby in read-only
+mode. This allows a read-only database to be distributed as a single
+file instead of as multiple files within a directory and to be
+compressed. In fact, a jar or zip file can contain any number of
+Derby databases and can also contain other information not related to
+Derby, such as application data or code.
+<P>You cannot store the <I>derby.properties</I> file in a jar
+or zip file.
+<P>To create a jar or zip file containing one or more Derby
+databases:
+<OL TYPE=1>
+<LI>Follow the instructions for creating a database for use on read-only
+media. See <A HREF="develop34.html#HDRSII-DEPLOY-26887">Creating and Preparing the Database for Read-Only Use</A>.
+</LI><LI>From the directory that contains the database folder, archive the database
+directory and its contents. For example, for the database<I>
+sales</I> that lives in the system directory<I> C:\london</I>,
+issue the command from <I>london</I>. Do not issue the command from
+inside the database directory itself. 
+<P>For example, archive the database folder and its contents using the JAR
+program from the JDK. You can use any zip or jar tool to generate the
+archive. 
+<P>
+<A NAME="IDX610"></A>
+This command archives the database directory <I>sales</I> and its contents
+into a compressed jar file called <I>dbs.jar</I>. 
+<PRE>cd C:\london
+jar cMf C:\dbs.jar sales
+</PRE> 
+<P>You can add multiple databases with jar. For example, this command
+puts the <I>sales</I> databases and the <I>boiledfood</I> database (in
+the subdirectory products) into the archive. 
+<PRE>cd C:\london
+jar cMf C:\dbs.jar sales products\boiledfood
+</PRE> 
+<P>The relative paths of the database in the jar need not match their original
+relative paths. You can do this by allowing your archive tool to change
+the path, or by moving the original databases before archiving them. 
+<P>The archive can be compressed or uncompressed, or individual databases can
+be uncompressed or compressed if your archive tool allows it.
+Compressed databases take up a smaller amount of space on disk, depending on
+the data loaded, but are slower to access. 
+<P>Once the database is archived into the jar or zip file, it has no
+relationship to the original database. The original database can
+continue to be modified if desired.
+</LI></OL>
+<P><HR>[ <A HREF="develop35.html">Previous Page</A><br><A HREF="develop37.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop37.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop37.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,48 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Accessing a Read-Only Database in a Zip/Jar</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="accessing in zip/jar files, Read-only databases">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-DEPLOY-11201">Accessing a Read-Only Database in a Zip/Jar</H1>
+<A NAME="IDX611"></A>
+<P>To access a database in a zip/jar, you specify jar in the
+subsubprotocol:
+<PRE>jdbc:derby:jar:(<I>pathToArchive</I>)<I>databasePathWithinArchive</I>
+</PRE>
+<P>The <I>pathToArchive</I> is the absolute path to the archive
+file. The <I>databasePathWithinArchive</I> is the relative path to
+the database within the archive. For example:
+<PRE>jdbc:derby:jar:(C:/dbs.jar)products/boiledfood
+jdbc:derby:jar:(C:/dbs.jar)sales
+</PRE>
+<P>If you have trouble finding a database within an archive, check the
+contents of the archive using your archive tool. The
+<I>databasePathWithinArchive</I> must match the one in the archive.
+You might find that the path in the archive has a leading slash, and thus the
+URL would be:
+<PRE>jdbc:derby:jar:(C:/dbs.jar)/products/boiledfood
+</PRE>
+<P>Databases in a jar or zip file are always opened read-only and there is
+currently no support to allow updates of any type.
+<P>Databases in a jar or zip file are not booted automatically when Derby
+is started, unless they are explicitly listed as
+<I>derby.service</I> properties.
+<P><HR>[ <A HREF="develop36.html">Previous Page</A><br><A HREF="develop38.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop38.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop38.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,74 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Accessing Databases-in-a-Jar in the Class Path</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="Accessing read-only databases from class path, putting in class path, Read-only databases, when path is ambiguous with databases in file system, Connecting to databases, when path is ambiguous because of databases in class path">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-DEPLOY-39856">Accessing Databases-in-a-Jar in the Class Path</H1>
+<A NAME="IDX612"></A>
+<A NAME="IDX613"></A>
+<P>Once an archive containing one or more Derby databases has been
+created it can be placed in the class path. This allows access to a
+database from within an application without the application's knowing the
+path of the archive. When jar or zip files are part of the class path,
+you do not have to specify the jar subsubprotocol to connect to them.
+<P>To access a database in a zip or jar file in the class path:
+<OL TYPE=1>
+<LI>Set the class path to include the jar or zip file before starting up
+Derby: 
+<PRE>CLASSPATH="C:\dbs.jar;%CLASSPATH%"
+</PRE>
+</LI><LI>Connect to a database within the jar or zip file with one of the following
+connection URLs: 
+<PRE>jdbc:derby:/<I>databasePathWithinArchive</I>
+</PRE> 
+<P>(standard syntax) 
+<PRE>jdbc:derby:classpath:/<I>databasePathWithinArchive</I>
+</PRE> 
+<P>(syntax with subsubprotocol)
+</LI></OL>
+<P>For example:
+<PRE>jdbc:derby:/products/boiledfood
+jdbc:derby:classpath:/products/boiledfood
+</PRE>
+<P><H1><A NAME="HDRSII-DEPLOY-18716">When Path Is Ambiguous with Databases in File System</H1>
+<A NAME="IDX614"></A>
+<P>Use the basic connection URL syntax only if the database path specified
+does not also point to a Derby database in the file system. If
+this is the case, the connection attempt might fail or connect to the wrong
+database. Use the form of the syntax with the subsubprotocol to
+distinguish between the databases.
+<P>For example:
+<PRE>jdbc:derby:classpath:/products/boiledfood
+</PRE>
+<P><H1><A NAME="HDRDEPLOY856333">When Path Is Ambiguous Because of Databases in Class Path</H1>
+<A NAME="IDX615"></A>
+<P>To connect to a database in the file system when the connection URL that
+you would use would be ambiguous with a database in the class path, use the
+following form of the connection URL:
+<PRE>jdbc:derby:directory:<I>databasePathInFileSystem</I>
+</PRE>
+<P>For example,
+<PRE>jdbc:derby:directory:/products/boiledfood
+</PRE>
+<P>Apart from the connection URL, databases in archives in the class path
+behave just like databases in archives accessed through the file
+system. However, databases in archives are read-only.
+<P><HR>[ <A HREF="develop37.html">Previous Page</A><br><A HREF="develop39.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop39.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop39.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,26 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Databases on Read-Only Media and DatabaseMetaData</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-DEPLOY-82529">Databases on Read-Only Media and DatabaseMetaData</H1>
+<P>Databases on read-only media return true for
+<I>DatabaseMetaData.isReadOnly</I>.
+<P><HR>[ <A HREF="develop38.html">Previous Page</A><br><A HREF="develop40.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop40.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop40.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,38 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Loading Classes from a Database</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="Database class loading, storing in database, Classes, Jar files, Logic">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<HR><H1 NAME="HDRSII-DEPLOY-30736">Loading Classes from a Database</H1>
+<A NAME="IDX616"></A>
+<A NAME="IDX617"></A>
+<A NAME="IDX618"></A>
+<A NAME="IDX619"></A>
+<P>You can store application logic in a database and then load classes from
+the database. Application logic, which can be used by both Derby
+(for database-side methods and stored objects) and your application, includes
+Java class files and other resources. Storing application code
+simplifies application deployment, since it reduces the potential for problems
+with a user's class path.
+<P>In an embedded environment, when application logic is stored in the
+database, both the user application and Derby can access classes loaded
+by the Derby class loader from stored jar files.
+<P><HR>[ <A HREF="develop39.html">Previous Page</A><br><A HREF="develop41.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop41.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop41.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,44 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Class Loading Overview</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="loading signed, Jar files">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRDEPLOY856753">Class Loading Overview</H1>
+<P>You store application classes and resources by storing one or more jar
+files in the database. Then your application can access classes loaded
+by Derby from the jar file and does not need to be coded in a particular
+way. The only difference is the way in which you invoke the
+application.
+<P>Here are the basic steps:
+<OL TYPE=1>
+<LI><A HREF="develop42.html#HDRSII-DEPLOY-15818">Create Jar Files for Your Application</A>
+</LI><LI><A HREF="develop43.html#HDRSII-DEPLOY-23812">Add the jar file or files to the database</A>
+</LI><LI><A HREF="develop44.html#HDRSII-DEPLOY-21645">Enable database class loading with a property</A>
+</LI><LI><A HREF="develop45.html#HDRSII-DEPLOY-12748">Code your applications the way you normally would</A>
+</LI></OL>
+<DL><DT><B>Note:</B></DT><DD>If you are interested in making changes to jar files stored in the database
+or changing the database jar &quot;class path&quot; of your application without
+having to re-boot, read <A HREF="develop46.html#HDRSII-DEPLOY-17604">Dynamic Changes to Jar Files or Database Jar Class Path</A>.
+</DD></DL>
+<P><H1><A NAME="HDRSII-DEPLOY-92419">Signed Jar Files</H1>
+<A NAME="IDX620"></A>
+<P>For information about how Derby handles signed jar files, see <A HREF="develop116.html#HDRSII-CSECUR-90988">Signed Jar Files</A>
+<P><HR>[ <A HREF="develop40.html">Previous Page</A><br><A HREF="develop42.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop42.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop42.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,60 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Create Jar Files for Your Application</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-DEPLOY-15818">Create Jar Files for Your Application</H1>
+<P>Include any Java classes in a jar file intended for Derby class
+loading except:
+<UL>
+<LI>the standard Java packages (<I>java.*</I>,
+<TT><I>javax.*</I></TT>) 
+<P>Derby does not prevent you from storing such a jar file in the
+database, but these classes <I>are never loaded</I> from the jar
+file.
+</LI><LI>those supplied with your Java environment (for example,
+<I>sun.*</I>)
+</LI></UL>
+<P>A running Derby system can load classes from any number of jar files
+from any number of schemas and databases.
+<P>Create jar files intended for Derby database class loading the same
+way you create a jar file for inclusion in a user's class path. For
+example, consider an application targeted at travel agencies:
+<PRE><B>jar cf travelagent.jar travelagent/*.class.</B>
+</PRE>
+<P>Various IDEs have tools to generate a list of contents for a jar file based
+on your application. If your application requires classes from other
+jar files, you have a choice:
+<UL>
+<LI><I>Extract the required third-party classes from their jar file and
+include only those in your jar file.</I> 
+<P>Best if you need only a small subset of the classes in the third-party jar
+file.
+</LI><LI><I>Store the third-party jar file in the database.</I> 
+<P>Best if you need most or all of the classes in the third-party jar file,
+since your application and third-party logic can be upgraded
+separately.
+</LI><LI><I>Deploy the third-party jar file in the user's class
+path.</I> 
+<P>Best if the classes are often already installed on a user's machine
+(for example, Objectspace's JGL classes).
+</LI></UL>
+<P>Include the class files and resources needed for your application.
+<P><HR>[ <A HREF="develop41.html">Previous Page</A><br><A HREF="develop43.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop43.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop43.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,58 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Add the jar file or files to the database</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="installing, removing, and replacing, jar files">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-DEPLOY-23812">Add the jar file or files to the database</H1>
+<A NAME="IDX621"></A>
+<P>
+<P>Use a set of procedures to install, replace, and remove jar files in a
+database. When you install a jar file in a database, you give it a
+Derby jar name, which is an <TT><I>SQL92Identifier</I></TT>.
+<DL><DT><B>Note:</B></DT><DD>Once a jar file has been installed, you cannot modify any of the individual
+classes or resources within the jar file. Instead, you must replace the
+entire jar file.
+</DD></DL>
+<P><H1><A NAME="HDRDEPLOY856948">Examples</H1>
+<P>See the <CITE>Derby Tools and Utilities Guide</CITE> for reference
+information about the utility and complete syntax.
+<P><H1><A NAME="HDRDEPLOY856845">Installing Jar Files</H1>
+<PRE><B><B>-- SQL  statement</B>
+CALL sqlj.install_jar(
+    'tours.jar', 'APP.Sample1', 0)
+ 
+<B>-- SQL  statement
+-- using a quoted identifier for the&nbsp;
+-- Derby  jar name</B>
+CALL sqlj.install_jar(
+    'tours.jar', 'APP."Sample2"', 0)</B>
+</PRE>
+<P><H1><A NAME="HDRDEPLOY856880">Removing Jar Files</H1>
+<PRE><B><B>-- SQL  statement</B>
+CALL sqlj.remove_jar(
+    'APP.Sample1', 0)</B>
+</PRE>
+<P><H1><A NAME="HDRDEPLOY856912">Replacing Jar Files</H1>
+<PRE><B><B>-- SQL  statement</B>
+CALL sqlj.replace_jar(
+    'c:\myjarfiles\newtours.jar', 'APP.Sample1')</B>
+</PRE>
+<P><HR>[ <A HREF="develop42.html">Previous Page</A><br><A HREF="develop44.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop44.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop44.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,52 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Enable database class loading with a property</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-DEPLOY-21645">Enable database class loading with a property</H1>
+<P>Once you have added one or more jar files to a database, you must set the
+database jar &quot;class path&quot; by including the jar file or files in the
+<I>derby.database.classpath</I> property to enable
+Derby to load classes from the jar files. This property, which
+behaves like a class path, specifies the jar files to be searched for classes
+and resources and the order in which they are searched. If Derby
+does not find a needed class stored in the database, it can retrieve the class
+from the user's class path. (Derby first looks in the
+user's class path before looking in the database.)
+<UL>
+<LI>Separate jar files with a colon (:).
+</LI><LI>Use two-part names for the jar files (schema name and jar name).
+Set the property as a database-level property for the database. The
+<I>first time</I> you set the property, you must reboot to load the
+classes.
+</LI></UL>
+<P>Example:
+<PRE><B>CALL SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY(
+    'derby.database.classpath',
+    'APP.ToursLogic:APP.ACCOUNTINGLOGIC')</B>
+</PRE>
+<P>See <I>&quot;derby.database.classpath&quot;</I> in
+<CITE>Tuning Derby</CITE> for more information about the
+property.
+<DL><DT><B>Note:</B></DT><DD>Derby's class loader looks first in the user's class path for
+any needed classes, and then in the database. To ensure class loading
+with the database class loader, remove classes from the class path.
+</DD></DL>
+<P><HR>[ <A HREF="develop43.html">Previous Page</A><br><A HREF="develop45.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop45.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop45.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,41 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Code your applications the way you normally would</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-DEPLOY-12748">Code your applications the way you normally would</H1>
+<P>In your applications, you cause classes to be loaded the way you normally
+would:
+<UL>
+<LI>indirectly referencing them in the code
+</LI><LI>directly using <I>java.lang.Class.forName</I>
+</LI></UL>
+<P>In your applications, you load resources the way you normally would, using
+the standard
+<I>java.lang.Class.getResourceAsStream</I>, a
+mechanism that allows an application to access resources defined in the class
+path without knowing where or how they are stored.
+<P>You do not need to make any changes to the way code interacts with
+Derby and its JDBC driver. An application can safely attempt to
+boot Derby, even though it is already running, without any errors.
+Applications connect to Derby in the usual manner.
+<DL><DT><B>Note:</B></DT><DD>The method <I>getResource</I> is not supported.
+</DD></DL>
+<P><HR>[ <A HREF="develop44.html">Previous Page</A><br><A HREF="develop46.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop46.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop46.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,61 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Dynamic Changes to Jar Files or Database Jar Class Path</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-DEPLOY-17604">Dynamic Changes to Jar Files or Database Jar Class Path</H1>
+<P>When you store jar files in a single database and make those jar files
+available to that database, it is possible to make changes to jar files or to
+change the database jar &quot;class path&quot; dynamically (without having to
+reboot).
+<P>That is, when you install or replace a jar file within an SQL statement or
+change the database jar &quot;class path&quot; (the
+<I>derby.database.classpath</I>
+property<TT><I>),</I></TT> Derby is able to load the new classes
+right away without your having to reboot.
+<P><H1><A NAME="HDRDEPLOY857611">Requirements</H1>
+<P>Certain conditions must be met for this to be true:
+<UL>
+<LI>You <I>originally configured</I> database-level class loading for the
+database correctly. Turning on the database-level class loading
+property requires setting the
+<TT><I>derby.database.classpath</I></TT> property
+with valid two-part names, then rebooting.
+</LI><LI>If changes to the <I>derby.database.classpath</I>
+property are needed to reflect new jar files, you change the property to a
+valid value.
+</LI></UL>
+<P>If these requirements are not met, you will have to reboot to see the
+changes.
+<P><H1><A NAME="HDRDEPLOY857648">Notes</H1>
+<P>When you are changing the
+<I>derby.database.classpath</I> property, all classes
+loaded from database jar files are reloaded, even for a jar file that has not
+changed.
+<P>Remember that the user's class path is searched first.
+<P>Any existing prepared statements will use the previously loaded classes
+unless they require class loading, in which case they will fail with a
+<I>ClassNotFound</I> error.
+<P>Cached objects do not match objects created with newly loaded
+classes. For example, an in-memory <I>Customer</I> object will not
+match a new <TT><I>Customer</I></TT> object if the
+<TT><I>Customer</I></TT> class has been reloaded, and it will raise a
+<TT><I>ClassCastException.</I></TT>
+<P><HR>[ <A HREF="develop45.html">Previous Page</A><br><A HREF="develop47.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop47.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop47.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,30 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Derby server-side programming</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<HR><H1 NAME="Header_87">Derby server-side programming</H1>
+<P>This chapter discusses special programming for Derby features such as
+database-side JDBC procedures and triggers.
+<UL>
+<LI><A HREF="develop48.html#HDRSII-SPECIAL-42117">Programming Database-Side JDBC Procedures</A>
+</LI><LI><A HREF="develop54.html#HDRSII-SPECIAL-27163">Programming Trigger Actions</A>
+</LI></UL>
+<P><HR>[ <A HREF="develop46.html">Previous Page</A><br><A HREF="develop48.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop48.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop48.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,35 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Programming Database-Side JDBC Procedures</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="Database-side JDBC procedures">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<HR><H1 NAME="HDRSII-SPECIAL-42117">Programming Database-Side JDBC Procedures</H1>
+<A NAME="IDX622"></A>
+<UL>
+<LI><A HREF="develop49.html#HDRSII-SPECIAL-27988">Overview</A>
+</LI><LI><A HREF="develop50.html#HDRSII-SPECIAL-29620">Database-Side JDBC Procedures and Nested Connections</A>
+</LI><LI><A HREF="develop50.html#HDRSII-SPECIAL-28907">Requirements for Database-Side JDBC Procedures Using Nested Connections</A>
+</LI><LI><A HREF="develop50.html#HDRSII-SPECIAL-29620">Database-Side JDBC Procedures and Nested Connections</A>
+</LI><LI><A HREF="develop51.html#HDRSII-SPECIAL-16181">Database-Side JDBC Procedures Using Non-Nested Connections</A>
+</LI><LI><A HREF="develop52.html#HDRSII-SPECIAL-41728">Database-Side JDBC Procedures and SQLExceptions</A>
+</LI><LI><A HREF="develop53.html#HDRSII-SPECIAL-45786">User-Defined SQLExceptions</A>
+</LI></UL>
+<P><HR>[ <A HREF="develop47.html">Previous Page</A><br><A HREF="develop49.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop49.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop49.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,36 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Overview</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="definition, Database-side procedures, Database-side JDBC procedures">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-SPECIAL-27988">Overview</H1>
+<P>
+<A NAME="IDX623"></A>
+<A NAME="IDX624"></A>
+Methods invoked within an application are called application-side
+methods. Methods invoked within Derby are called database-side
+procedures.
+<P>An application-side method can be exactly the same as a database-side
+procedure. The only difference is where you invoke them. You
+write the method only once. Where you invoke the method--within
+the application or within an SQL statement--determines whether it is an
+&quot;application-side&quot; or a &quot;database-side&quot; method.
+<P><HR>[ <A HREF="develop48.html">Previous Page</A><br><A HREF="develop50.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop50.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop50.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,75 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Database-Side JDBC Procedures and Nested Connections</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="using nested connections, Database-side JDBC procedures, getting, Nested connections, limitations of">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-SPECIAL-29620">Database-Side JDBC Procedures and Nested Connections</H1>
+<A NAME="IDX625"></A>
+<P>
+<A NAME="IDX626"></A>
+Most database-side JDBC Procedures need to share the same transaction space as
+the statements that called them for the following reasons:
+<UL>
+<LI>to avoid blocking and deadlocks
+</LI><LI>to ensure that any updates done from within the method are atomic with the
+outer transaction
+</LI></UL>
+<P>In order to use the same transaction, the procedure must use the same
+connection as the parent SQL statement in which the method was
+executed. Connections re-used in this way are called <I>nested
+connections</I>.
+<P>
+<A NAME="IDX627"></A>
+Use the connection URL <I>jdbc:default:connection</I> to
+re-use the current <TT><I>Connection</I></TT>
+<P>The Database Connection URL jdbc:default:connection allows a
+Java method to get the <I>Connection</I> of the SQL statement that called
+it. This is the standard (SQL standard, Part 13 SQL Routines and Java)
+mechanism to obtain the nested connection object. The method would get
+a <TT><I>Connection</I></TT> like this:
+<PRE>Connection conn = DriverManager.getConnection(
+    "jdbc:default:connection");
+</PRE>
+<P>Loading a JDBC driver in a database-side routine is not required.
+<P><H1><A NAME="HDRSII-SPECIAL-28907">Requirements for Database-Side JDBC Procedures Using Nested Connections</H1>
+<A NAME="IDX628"></A>
+<P>In order to preserve transactional atomicity, database-side JDBC procedures
+that use nested connections:
+<UL>
+<LI>cannot issue a commit or rollback, unless called within a CALL or VALUES
+statement. 
+<P>Commits are permitted when the procedure is called within a CALL or VALUES
+statement.
+</LI><LI>cannot change connection attributes such as auto-commit.
+</LI><LI>cannot modify the data in a table used by the parent statement that called
+the procedure, using INSERT, UPDATE, or DELETE. For example, if a
+SELECT statement using the <I>T</I> table calls the
+<TT><I>changeTables</I></TT> procedure,
+<TT><I>changeTables</I></TT> cannot modify data in the <TT><I>T</I>
+table.</TT>
+</LI><LI>cannot drop a table used by the statement that called the
+procedure.
+</LI><LI>cannot be in a class whose static initializer executes DDL
+statements.
+</LI></UL>
+<P>In addition, the Connection object that represents the nested connection
+always has its auto-commit mode set to false.
+<P><HR>[ <A HREF="develop49.html">Previous Page</A><br><A HREF="develop51.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop51.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop51.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,51 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Database-Side JDBC Procedures Using Non-Nested Connections</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="using non-nested connections, Database-side JDBC procedures, example of connecting to different database">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-SPECIAL-16181">Database-Side JDBC Procedures Using Non-Nested Connections</H1>
+<A NAME="IDX629"></A>
+<P>A database-side JDBC procedure can create a new connection instead of using
+a nested connection. Statements executed in the procedure will be part
+of a different transaction, and so can issue commits and rollbacks.
+<P>Such procedures can connect to a database different from the one to which
+the parent SQL statement that called it is connected. The procedure
+does not use the same transaction or <I>Connection</I>. It
+establishes a new <TT><I>Connection</I></TT> and transaction.
+<DL><DT><B>Note:</B></DT><DD>If database-side JDBC procedures do not use nested connections, this means
+that they are operating outside of the normal DBMS transaction control, so it
+is not good practice to use them indiscriminately.
+</DD></DL>
+<P><H1><A NAME="HDRSPECIAL847513">Invoking a Procedure Using the CALL Command</H1>
+<A NAME="IDX630"></A>
+<P>If a procedure does not return a value, Derby can execute the
+procedure using the SQL CALL command. You can invoke the procedure in
+an SQL statement such as the following:
+<PRE><B>CALL MYPROC()</B>
+</PRE>
+<DL><DT><B>Note:</B></DT><DD>You cannot roll back this statement, because commits occur within the
+procedure itself. Procedures that use nested connections, on the other
+hand, are not permitted to commit or roll back and can therefore be rolled
+back after the calling statement.
+</DD></DL>
+<P>You can also use the CALL command to execute a procedure that does return a
+value, but you will not be able to access the value.
+<P><HR>[ <A HREF="develop50.html">Previous Page</A><br><A HREF="develop52.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop52.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop52.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,78 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Database-Side JDBC Procedures and SQLExceptions</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="importance of not catching within database-side procedures, SQLExceptions, and SQLExceptions, Database-side JDBC procedures">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-SPECIAL-41728">Database-Side JDBC Procedures and SQLExceptions</H1>
+<A NAME="IDX631"></A>
+<A NAME="IDX632"></A>
+<P>It is possible to code database-side procedures, like application-side
+methods, to catch <I>SQLExceptions</I>.
+<TT><I>SQLExceptions</I></TT> that are caught within a procedure are
+hidden from the calling application code. When such
+<TT><I>SQLExceptions</I></TT> are of transaction severity (such as
+deadlocks), this &quot;hiding&quot; of the exception causes unexpected
+problems.
+<P>This is because errors of transaction severity roll back work already done
+by a transaction (not just the piece executed by the called method) and
+silently begin a new transaction. When the method execution is
+complete, Derby detects that the outer statement was invalidated by a
+deadlock and rolls back any work done<I> in the new transaction</I> as
+well. This is the expected behavior, because all the statements in
+between explicit commits should be treated atomically; the new
+transaction implicitly begun by Derby's rollback was not intended by
+the application designer.
+<P>However, this is not the same behavior that would happen if the method were
+invoked in the application. In that situation, Derby would roll
+back the work done by the transaction and silently begin a new
+transaction. Work in the new transaction would not be rolled back when
+the method returned. However, coding the application in that way means
+that the transaction did not end where you expected it to and is probably a
+programming mistake. Coding in this manner is not recommended.
+<P>A method that catches a deadlock exception and then continues is probably
+making a mistake. Errors of transaction severity should be caught not
+by nested code, but only by the outermost application code. That is the
+only way to ensure that transactions begin and end where you expect them
+to.
+<P>Not all database vendors handle nested deadlocks the same way. For
+this and other reasons, it is not possible to write portable SQL-invoking
+methods. However, it is possible to write SQL-invoking methods that
+behave identically <I>regardless of whether you invoke them in the
+application or as a procedure in the database</I>.
+<P>In order to ensure identical application- and database-side handling of
+nested errors, code try-catch blocks to check for the severity of exceptions
+as follows:
+<PRE>try {
+    preparedStatement.execute();
+} catch (SQLException se ) {
+        String SQLState = se.getSQLState();
+    if ( SQLState.equals( "23505" ) )&nbsp;
+        { correctDuplicateKey(); }
+    else if ( SQLState.equals( "22003" ) ) {&nbsp;
+        correctArithmeticOverflow(); }
+    else { throw se; }
+}
+</PRE>
+<P>Of course, users also have the choice of not wrapping SQL statements in
+try-catch blocks within methods. In that case, <I>SQLExceptions</I>
+are caught higher up in their applications, which is the desired
+behavior.
+<P><HR>[ <A HREF="develop51.html">Previous Page</A><br><A HREF="develop53.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop53.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop53.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,35 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>User-Defined SQLExceptions</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="user-defined (38001-38999), SQLExceptions">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-SPECIAL-45786">User-Defined SQLExceptions</H1>
+<A NAME="IDX633"></A>
+<P>When the execution of a database-side method raises an error, Derby
+wraps that exception in an <I>SQLException</I> with an
+<TT><I>SQLState</I></TT> of 38000. You can avoid having
+Derby wrap the exception if:
+<UL>
+<LI>the exception is an <I>SQLException</I>
+</LI><LI>the range of the <I>SQLState</I> is 38001-38999
+</LI></UL>
+<P>(This conforms to the SQL99 standard.)
+<P><HR>[ <A HREF="develop52.html">Previous Page</A><br><A HREF="develop54.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop54.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop54.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,45 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Programming Trigger Actions</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="programming trigger actions, Triggers">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<HR><H1 NAME="HDRSII-SPECIAL-27163">Programming Trigger Actions</H1>
+<A NAME="IDX634"></A>
+<P>Derby allows you to create triggers. When you create a trigger,
+you define an action or set of actions that are executed when a database event
+occurs on a specified table. A <I>database event</I> is a delete,
+insert, or update operation. For example, if you define a trigger for a
+delete on a particular table, the trigger action is executed whenever someone
+deletes a row or rows from the table.
+<P>The <TT>CREATE TRIGGER</TT> statement in the <CITE>Derby
+Reference Manual</CITE> goes into detail of the complete <TT>CREATE
+TRIGGER</TT> syntax. This section provides information on defining the
+trigger action itself, which is only one aspect of creating triggers.
+<P>This section refers to the <TT>CREATE TRIGGER</TT> statement as the
+<I>trigger actions</I>.
+<UL>
+<LI><A HREF="develop55.html#HDRSII-SPECIAL-53165">Trigger Action Overview</A>
+</LI><LI><A HREF="develop56.html#HDRSII-SPECIAL-76763">Performing Referential Actions</A>
+</LI><LI><A HREF="develop57.html#HDRSII-SPECIAL-67260">Accessing Before and After Rows</A>
+</LI><LI><A HREF="develop58.html#HDRSII-SPECIAL-13670">Examples</A>
+</LI><LI><A HREF="develop59.html#HDRSII-SPECIAL-49460">Triggers and Exceptions</A>
+</LI></UL>
+<P><HR>[ <A HREF="develop53.html">Previous Page</A><br><A HREF="develop55.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop55.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop55.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,38 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Trigger Action Overview</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="use of SQL and Java in trigger actions, Triggers, limitations of trigger actions">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-SPECIAL-53165">Trigger Action Overview</H1>
+<A NAME="IDX635"></A>
+<P><A NAME="SPTSII-SPECIAL-55377"></A>
+<A NAME="IDX636"></A>
+A trigger action is a simple SQL statement. For example:
+<PRE><B>CREATE TRIGGER . .&nbsp;.
+DELETE FROM flightavailability&nbsp;
+	WHERE flight_id IN (SELECT flight_id FROM flightavailability&nbsp;
+		WHERE YEAR(flight_date) &lt; 2004);)&nbsp;
+</B></PRE>
+<P>A trigger action does have some limitations, though; for example, it
+cannot contain dynamic parameters or alter the table on which the trigger is
+defined. See &quot;TriggerAction&quot; in the <CITE>Derby
+Reference Manual</CITE> for details.
+<P><HR>[ <A HREF="develop54.html">Previous Page</A><br><A HREF="develop56.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop56.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop56.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,33 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Performing Referential Actions</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="and triggers, Referential actions, use of to perform referential actions, Triggers, via triggers, Referential integrity">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-SPECIAL-76763">Performing Referential Actions</H1>
+<A NAME="IDX637"></A>
+<A NAME="IDX638"></A>
+<A NAME="IDX639"></A>
+<P>Derby provides referential actions. Examples in this section
+are included to illustrate how to write triggers. You can choose to use
+standard SQL referential integrity to obtain this functionality, rather than
+writing triggers. See the <CITE>Derby Reference Manual</CITE>
+for more information on referential integrity.
+<P><HR>[ <A HREF="develop55.html">Previous Page</A><br><A HREF="develop57.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop57.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop57.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,39 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Accessing Before and After Rows</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="accessing before and after rows, Triggers">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-SPECIAL-67260">Accessing Before and After Rows</H1>
+<A NAME="IDX640"></A>
+<P>Many trigger actions need to access the values of the rows being
+changed. Such trigger actions need to know one or both of the
+following:
+<UL>
+<LI>the &quot;before&quot; values of the rows being changed (their values before
+the database event that caused the trigger to fire)
+</LI><LI>the &quot;after&quot; values of the rows being changed (the values to which
+the database event is setting them)
+</LI></UL>
+<P>Derby provides transition variables and transition tables for a
+trigger action to access these values. See&quot;Referencing Old and New
+Values: The Referencing Clause&quot; in the <CITE>Derby Reference
+Manual</CITE>.
+<P><HR>[ <A HREF="develop56.html">Previous Page</A><br><A HREF="develop58.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop58.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop58.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,41 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Examples</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="example of trigger actions, Triggers">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-SPECIAL-13670">Examples</H1>
+<A NAME="IDX641"></A>
+<P>The following trigger action copies a row from the <I>flights</I> table
+into the <I>flight_history</I> table whenever any row gets inserted into
+<I>flights</I> and adds the comment &quot;inserted from trig1&quot; in the
+<I>status</I> column of the<I>flight_history</I> table.
+<PRE><B>CREATE TRIGGER trig1&nbsp;
+AFTER UPDATE ON flights&nbsp;
+REFERENCING OLD AS UPDATEDROW&nbsp;
+FOR EACH ROW MODE DB2SQL&nbsp;
+INSERT INTO flights_history&nbsp;
+VALUES (UPDATEDROW.FLIGHT_ID, UPDATEDROW.SEGMENT_NUMBER,
+UPDATEDROW.ORIG_AIRPORT, UPDATEDROW.DEPART_TIME,
+UPDATED ROW.DEST_AIRPORT, UPDATEDROW.ARRIVE_TIME,
+UPDATEDROW.MEAL, UPDATEDROW.FLYING_TIME, UPDATEDROW.MILES,
+UPDATEDROW.AIRCRAFT,'INSERTED FROM trig1');</B>
+</PRE>
+<P><HR>[ <A HREF="develop57.html">Previous Page</A><br><A HREF="develop59.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop59.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop59.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,58 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Triggers and Exceptions</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="and exceptions, Triggers, automatic rollback of trigger actions">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-SPECIAL-49460">Triggers and Exceptions</H1>
+<A NAME="IDX642"></A>
+<UL>
+<LI><A HREF="#HDRSII-SPECIAL-67198">Exceptions in Triggers Actions</A>
+</LI><LI><A HREF="#HDRSII-SPECIAL-93497">Aborting Statements and Transactions</A>
+</LI></UL>
+<P><H1><A NAME="HDRSII-SPECIAL-67198">Exceptions in Triggers Actions</H1>
+<A NAME="IDX643"></A>
+<P>Exceptions raised by triggers have a statement severity; they roll
+back the statement that caused the trigger to fire.
+<P>This rule applies to nested triggers (triggers that are fired by other
+triggers). If a trigger action raises an exception (and it is not
+caught), the transaction on the current connection is rolled back to the point
+before the triggering event. For example, suppose Trigger A causes
+Trigger B to fire. If Trigger B throws an exception, the current
+connection is rolled back to the point before to the statement in Trigger A
+that caused Trigger B to fire. Trigger A is then free to catch the
+exception thrown by Trigger B and continue with its work. If Trigger A
+does not throw an exception, the statement that caused Trigger A, as well as
+any work done in Trigger A, continues until the transaction in the current
+connection is either committed or rolled back. However, if Trigger A
+does not catch the exception from Trigger B, it is as if Trigger A had thrown
+the exception. In that case, the statement that caused Trigger A to
+fire is rolled back, along with any work done by both of the triggers.
+<P><H1><A NAME="HDRSII-SPECIAL-93497">Aborting Statements and Transactions</H1>
+<P>You might want a trigger action to be able to abort the triggering
+statement or even the entire transaction. Triggers that use the current
+connection are not permitted to commit or roll back the connection, so how do
+you do that? The answer is: have the trigger throw an exception, which
+is by default a statement-level exception (which rolls back the
+statement). The application-side code that contains the statement that
+caused the trigger to fire can then roll back the entire connection if
+desired. Programming triggers in this respect is no different from
+programming any database-side JDBC method.
+<P><HR>[ <A HREF="develop58.html">Previous Page</A><br><A HREF="develop60.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop60.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop60.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,33 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Controlling Derby Application Behavior</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<HR><H1 NAME="HDRSII-CONCEPTS-19524">Controlling Derby Application Behavior</H1>
+<P>This chapter looks at some advanced Derby concepts:
+<UL>
+<LI><A HREF="develop61.html#HDRSII-CONCEPTS-38375">The JDBC Connection and Transaction Model</A>
+</LI><LI><A HREF="develop64.html#HDRSII-CONCEPTS-41275">SQL and JDBC ResultSet/Cursor Mechanisms</A>
+</LI><LI><A HREF="develop70.html#HDRSII-CONCEPTS-30291">Locking, Concurrency, and Isolation</A>
+</LI><LI><A HREF="develop76.html#HDRSII-CONCEPTS-34828">Working with Multiple Connections to a Single Database</A>
+</LI><LI><A HREF="develop80.html#HDRSII-CONCEPTS-23499">Working with Multiple Threads Sharing a Single Connection</A>
+</LI><LI><A HREF="develop85.html#HDRSII-CONCEPTS-24927">Working with Derby SQLExceptions in an Application</A>
+</LI></UL>
+<P><HR>[ <A HREF="develop59.html">Previous Page</A><br><A HREF="develop61.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop61.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop61.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,37 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>The JDBC Connection and Transaction Model</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="JDBC Connections, Transactions">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<HR><H1 NAME="HDRSII-CONCEPTS-38375">The JDBC Connection and Transaction Model</H1>
+<A NAME="IDX644"></A>
+<A NAME="IDX645"></A>
+<P>Session and transaction capabilities for SQL are handled through JDBC
+procedures, not by SQL commands.
+<P>JDBC defines a system session and transaction model for database
+access. A <I>session</I> is the duration of one connection to the
+database and is handled by a JDBC <TT><I>Connection</I></TT>
+object. This section includes the following topics:
+<UL>
+<LI><A HREF="develop62.html#HDRSII-CONCEPTS-36881">Connections</A>
+</LI><LI><A HREF="develop63.html#HDRSII-CONCEPTS-19173">Transactions</A>
+</LI></UL>
+<P><HR>[ <A HREF="develop60.html">Previous Page</A><br><A HREF="develop62.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop62.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop62.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,96 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Connections</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="definition, JDBC Connections, getting, Connections, Connecting to multiple databases, JDBC Statement, all result sets as, Cursors, Nested connections">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-CONCEPTS-36881">Connections</H1>
+<P>
+<A NAME="IDX646"></A>
+A <I>Connection</I> object represents a connection with a database.
+Within the scope of one <TT><I>Connection</I></TT>, you access only a
+single Derby database. (Database-side JDBC procedures can allow
+you to access more than one database in some circumstances.) Depending
+on your Derby product license, a single application might allow one or
+more <TT><I>Connections</I></TT> to Derby, either to a single
+database or to many different databases, provided that all the databases are
+within the same system (see <A HREF="develop12.html#HDRSII-DEVELOP-27610">Derby System</A>).
+<P>
+<A NAME="IDX647"></A>
+With DriverManager, you use the connection URL as an argument to get the
+<TT><I>getConnection</I></TT> method to specify which database to
+connect to and other details (see <A HREF="develop11.html#HDRSII-DEVELOP-17453">Derby JDBC Database Connection URL</A>).
+<P>
+<A NAME="IDX648"></A>
+The following example shows an application establishing three separate
+connections to two different databases in the current system.
+<PRE>Connection conn = DriverManager.getConnection(
+    "jdbc:derby:sample");
+System.out.println("Connected to database sample");
+conn.setAutoCommit(false);
+Connection conn2 = DriverManager.getConnection(
+    "jdbc:derby:newDB;create=true");
+System.out.println("Created AND connected to newDB");
+conn2.setAutoCommit(false);
+Connection conn3 = DriverManager.getConnection(
+    "jdbc:derby:newDB");
+System.out.println("Got second connection to newDB");
+conn3.setAutoCommit(false);
+</PRE>
+<P>A <I>Connection</I> object has no association with any specific
+thread; during its lifetime, any number of threads might have access to
+it, as controlled by the application.
+<P><H1><A NAME="HDRCONCEPTS838179">Statements</H1>
+<A NAME="IDX649"></A>
+<P>To execute SQL statements against a database, an application uses
+<I>Statements</I> (<TT><I>java.sql.Statement</I></TT>)
+and <I>PreparedStatements</I>
+(<TT><I>java.sql.PreparedStatement</I></TT>), or
+<I>CallableStatements</I>
+(<TT><I>java.sql.CallableStatement</I></TT>) for stored
+procedures. Because <I>PreparedStatement</I> extends
+<I>Statement</I> and <I>CallableStatement</I> extends<I>
+PreparedStatement</I>, this section refers to both as
+<I>Statements</I>. <I>Statements</I> are obtained from and are
+associated with a particular <I>Connection</I>.
+<P><H1><A NAME="HDRCONCEPTS838315">ResultSets and Cursors</H1>
+<A NAME="IDX650"></A>
+<P>Executing a <I>Statement</I> that returns values gives a
+<TT><I>ResultSet</I></TT>
+(<TT><I>java.sql.ResultSet</I></TT>), allowing the
+application to obtain the results of the statement. Only one
+<TT><I>ResultSet</I></TT> can be open for a particular
+<TT><I>Statement</I></TT> at any time, as per the JDBC
+specification.
+<P>Thus, executing a <I>Statement</I> automatically closes any open
+<TT><I>ResultSet</I></TT> generated by an earlier execution of that
+<TT><I>Statement</I></TT>.
+<P>For this reason, you must use a different <I>Statement</I> to update a
+cursor (a named <TT><I>ResultSet</I></TT>) from the one used to generate
+the cursor.
+<P>The names of open cursors must be unique within a
+<I>Connection</I>. For more information about how to use cursors
+and <TT><I>ResultSets</I></TT>, see <A HREF="develop64.html#HDRSII-CONCEPTS-41275">SQL and JDBC ResultSet/Cursor Mechanisms</A>.
+<P><H1><A NAME="HDRSII-CONCEPTS-26633">Nested Connections</H1>
+<A NAME="IDX651"></A>
+<P>SQL statements can include routine invocations. If these routines
+interact with the database, they must use a <I>Connection</I>.
+<P>For more information, see <A HREF="develop48.html#HDRSII-SPECIAL-42117">Programming Database-Side JDBC Procedures</A>.
+<P><HR>[ <A HREF="develop61.html">Previous Page</A><br><A HREF="develop63.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop63.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop63.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,173 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Transactions</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="definition, Transactions, and transactions, Auto-commit, using, turning off with JDBC, turning off, Explicit close of JDBC objects, implicit versus explicit, Rollback">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-CONCEPTS-19173">Transactions</H1>
+<A NAME="IDX652"></A>
+<P>A <I>transaction</I> is a set of one or more SQL statements that make
+up a logical unit of work that you can either commit or roll back and that
+will be recovered in the event of a system failure. All the statements
+in the transaction are <I>atomic</I>. A transaction is associated
+with a single <TT><I>Connection</I></TT> object (and database). A
+transaction cannot span <I>Connections</I> (or databases).
+<P>Derby permits schema and data manipulation statements (DML) to be
+intermixed within a single transaction. If you create a table in one
+transaction, you can also insert into it in that same transaction. A
+schema manipulation statement (DDL) is not automatically committed when it is
+performed, but participates in the transaction within which it is
+issued. Because DDL requires exclusive locks on system tables, keep
+transactions that involve DDL short.
+<P><H1><A NAME="HDRCONCEPTS838850">Transactions When Auto-Commit Is Disabled</H1>
+<A NAME="IDX653"></A>
+<P>When auto-commit is disabled (see <A HREF="#HDRSII-CONCEPTS-29416">Using Auto-Commit</A>), you use a <I>Connection</I> object's
+<TT><I>commit</I></TT> and <TT><I>rollback</I></TT> methods to
+commit or roll back a transaction. The <TT><I>commit</I></TT>
+method makes permanent the changes resulting from the transaction and releases
+locks. The <TT><I>rollback</I></TT> method undoes all the changes
+resulting from the transaction and releases locks. A transaction
+encompasses all the SQL statements executed against a single
+<TT><I>Connection</I></TT> object since the last
+<TT><I>commit</I></TT> or <TT><I>rollback</I></TT>.
+<P>You do not need to explicitly begin a transaction. You implicitly
+end one transaction and begin a new one after disabling auto-commit, changing
+the isolation level, or after calling <TT><I>commit</I></TT> or
+<TT><I>rollback</I></TT>.
+<P>Committing a transaction also closes all <TT><I>ResultSet</I></TT>
+objects excluding the <TT><I>ResultSet</I></TT> objects associated with
+cursors with holdability <TT>true</TT>. The default holdability of
+the cursors is <TT>true</TT> and <TT><I>ResultSet</I></TT> objects
+associated with them need to be closed explicitly. A commit will not
+close such <TT><I>ResultSet</I></TT> objects. (See <A HREF="develop69.html#HDRSII-CONCEPTS-HOLDABLECURSORS">Holdable Cursors</A> for more information.) It also releases any database
+locks currently held by the <TT><I>Connection</I></TT>, whether or not
+these objects were created in different threads.
+<P><H1><A NAME="HDRSII-CONCEPTS-29416">Using Auto-Commit</H1>
+<A NAME="IDX654"></A>
+<P>A new connection to a Derby database is in auto-commit mode by
+default, as specified by the JDBC standard. Auto-commit mode means that
+when a statement is completed, the method <I>commit</I> is called on that
+statement automatically. Auto-commit in effect makes every SQL
+statement a transaction. The commit occurs when the statement completes
+or the next statement is executed, whichever comes first. In the case
+of a statement returning a <TT><I>ResultSet</I></TT>, the statement
+completes when the last row of the <TT><I>ResultSet</I></TT> has been
+retrieved or the <TT><I>ResultSet</I></TT> has been closed
+explicitly.
+<P>Some applications might prefer to work with Derby in auto-commit
+mode; some might prefer to work with auto-commit turned off. You
+should be aware of the implications of using either model.
+<P>You should be aware of the following when you use auto-commit:
+<UL>
+<LI><I>Cursors</I> 
+<P>You cannot use auto-commit if you do any positioned updates or deletes
+(that is, an update or delete statement with a &quot;WHERE CURRENT OF&quot;
+clause) on cursors which have the <I>close cursors on commit</I> option
+set.
+<P>Auto-commit automatically closes cursors, which are explicitly opened with
+the <I>close on commit</I> option, when you do any in-place updates or
+deletes. For more information about cursors, see <A HREF="develop64.html#HDRSII-CONCEPTS-41275">SQL and JDBC ResultSet/Cursor Mechanisms</A>.
+<P>A cursor declared to be held across commit can execute updates and issue
+multiple commits before closing the cursor, but the cursor must be
+repositioned before any statement following the commit. If this is
+attempted with auto-commit on, an error is generated.
+</LI><LI><I>Database-side JDBC Procedures (procedures using nested
+connections)</I> 
+<P>You cannot execute procedures within SQL statements if those procedures
+perform a commit or rollback on the current connection. Since in the
+auto-commit mode all SQL statements are implicitly committed, Derby turns
+off auto-commit during execution of database-side procedures and turns it back
+on when the method completes.
+<P>Procedures that use nested connections are not permitted to turn
+auto-commit on or off or to commit or roll back.
+</LI><LI><I>Table-level locking and the SERIALIZABLE isolation level</I> 
+<P>When an application uses table-level locking and the SERIALIZABLE isolation
+level, all statements that access tables hold at least shared table
+locks. Shared locks prevent other transactions that update data from
+accessing the table. A transaction holds a lock on a table until the
+transaction commits. <I>So even a SELECT statement holds a shared
+lock on a table until its connection commits and a new transaction
+begins. </I>
+<BR>
+<P><B><A NAME="Table_2">Table 2. Summary of Application Behavior with Auto-Commit On or Off</A></B><BR>
+<TABLE  BORDER>
+<TR>
+<TH ALIGN="LEFT" VALIGN="BOTTOM" ID="WQ6" WIDTH="48%">Topic
+</TH><TH ALIGN="LEFT" VALIGN="BOTTOM" ID="WQ7" WIDTH="25%">Auto-Commit On
+</TH><TH ALIGN="LEFT" VALIGN="BOTTOM" ID="WQ8" WIDTH="26%">Auto-Commit Off
+</TH></TR><TR>
+<TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ6" WIDTH="48%">Transactions
+</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ7" WIDTH="25%">Each statement is a separate transaction.
+</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ8" WIDTH="26%">Commit() or rollback() begins a transaction.
+</TD></TR><TR>
+<TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ6" WIDTH="48%">Database-side JDBC procedures (routines using nested connections)
+</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ7" WIDTH="25%">Auto-commit is turned off.
+</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ8" WIDTH="26%">Works (no explicit commits or rollbacks are allowed).
+</TD></TR><TR>
+<TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ6" WIDTH="48%">Updatable cursors
+</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ7" WIDTH="25%">Does not work.
+</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ8" WIDTH="26%">Works.
+</TD></TR><TR>
+<TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ6" WIDTH="48%">Multiple connections accessing the same data
+</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ7" WIDTH="25%">Works.
+</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ8" WIDTH="26%">Works. Lower concurrency when applications use SERIALIZABLE
+isolation mode and table-level locking.
+</TD></TR></TABLE>
+</LI></UL>
+<P><H1><A NAME="HDRCONCEPTS839040">Turning Off Auto-Commit</H1>
+<A NAME="IDX655"></A>
+<A NAME="IDX656"></A>
+<PRE>You can disable auto-commit with the <I>Connection</I> class's
+<I>setAutoCommit</I> method.
+</PRE>
+<PRE><B>//using the JDBC setAutoCommit method</B>
+conn.setAutoCommit(false);
+</PRE>
+<P><H1><A NAME="HDRCONCEPTS839085">Explicitly Closing Statements, <I>ResultSets</I>, and <I>Connections</I></H1>
+<A NAME="IDX657"></A>
+<P>You should explicitly close <I>Statements</I>,
+<TT><I>ResultSets,</I></TT> and <TT><I>Connections</I></TT> when
+you no longer need them. Connections to Derby are resources
+external to an application, and the garbage collector will not close them
+automatically.
+<P>For example, close a <I>Statement</I> object using its
+<TT><I>close</I></TT> method; close a
+<TT><I>Connection</I></TT> object using its <TT><I>close</I></TT>
+method. If auto-commit is disabled, active transactions need to be
+explicitly committed or rolled back before closing the connection
+<P><H1><A NAME="HDRSII-CONCEPTS-14433">Statement Versus Transaction Runtime Rollback</H1>
+<A NAME="IDX658"></A>
+<P>When an SQL statement generates an exception, this exception results in a
+<I>runtime rollback</I>. A runtime rollback is a system-generated
+rollback of a statement or transaction by Derby, as opposed to an
+explicit <TT><I>rollback</I></TT> call from your application.
+<P>Extremely severe exceptions, such as disk-full errors, shut down the
+system, and the transaction is rolled back when the database is next
+booted. Severe exceptions, such as deadlock, cause transaction
+rollback; Derby rolls back all changes since the beginning of the
+transaction and implicitly begins a new transaction. Less severe
+exceptions, such as syntax errors, result in statement rollback;
+Derby rolls back only changes made by the statement that caused the
+error. The application developer can insert code to explicitly roll
+back the entire transaction if desired.
+<P>Derby supports partial rollback through the use of savepoints.
+See the <CITE>Derby Reference Manual</CITE> for more
+information.
+<P><HR>[ <A HREF="develop62.html">Previous Page</A><br><A HREF="develop64.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop64.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop64.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,41 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>SQL and JDBC ResultSet/Cursor Mechanisms</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="working with, Cursors, ResultSets">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<HR><H1 NAME="HDRSII-CONCEPTS-41275">SQL and JDBC ResultSet/Cursor Mechanisms</H1>
+<A NAME="IDX659"></A>
+<A NAME="IDX660"></A>
+<P>A cursor provides you with the ability to step through and process the rows
+in a <I>ResultSet</I> one by one. A
+<TT><I>java.sql.ResultSet</I></TT> object constitutes a
+cursor. You do not need to use a language construct, such as
+SQL-92's DECLARE CURSOR, to work with cursors in a Java
+application. In Derby, any SELECT statement generates a
+cursor.
+<UL>
+<LI><A HREF="develop65.html#HDRSII-CONCEPTS-88082">Simple Non-Updatable ResultSets</A>
+</LI><LI><A HREF="develop66.html#HDRSII-CONCEPTS-28351">Updatable Cursors</A>
+</LI><LI><A HREF="develop67.html#HDRSII-CONCEPTS-23987">ResultSets and Auto-Commit</A>
+</LI><LI><A HREF="develop68.html#HDRSII-CONCEPTS-22641">Scrolling Insensitive ResultSets</A>
+</LI><LI><A HREF="develop69.html#HDRSII-CONCEPTS-HOLDABLECURSORS">Holdable Cursors</A>
+</LI></UL>
+<P><HR>[ <A HREF="develop63.html">Previous Page</A><br><A HREF="develop65.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop65.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop65.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,62 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Simple Non-Updatable ResultSets</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-CONCEPTS-88082">Simple Non-Updatable ResultSets</H1>
+<P>Here is an excerpt from a sample JDBC application that generates a
+<I>ResultSet</I> with a simple SELECT statement and then processes the
+rows.
+<PRE>Connection conn = DriverManager.getConnection(
+    "jdbc:derby:sample");
+Statement s = conn.createStatement();
+s.execute("set schema 'SAMP'");
+<B>//note that autocommit is on--it is on by default in JDBC</B>
+ResultSet rs = s.executeQuery(
+    "SELECT empno, firstnme, lastname, salary, bonus, comm "
+				 + 12 "FROM samp.employee");
+<B>/** a standard JDBC ResultSet. It maintains a&nbsp;
+  *  cursor that points to the current row of data. The cursor&nbsp;
+  *  moves down one row each time the method next() is called.
+  *  You can scroll one way only--forward--with the next()
+  *  method. When auto-commit is on, after you reach the&nbsp;
+  *  last row the statement is considered completed
+  *  and the transaction is committed.
+  */</B>
+System.out.println( "last name" + "," + "first name" + ": earnings");
+<B>/* here we are scrolling through the result set&nbsp;
+with the next() method.*/</B>
+while (rs.next()) {
+<B>    // processing the rows</B>
+    String firstnme = rs.getString("FIRSTNME");
+    String lastName = rs.getString("LASTNAME");
+    BigDecimal salary = rs.getBigDecimal("SALARY");
+    BigDecimal bonus = rs.getBigDecimal("BONUS");
+    BigDecimal comm = rs.getBigDecimal("COMM");&nbsp;
+    System.out.println( lastName + ", " + firstnme + ": "&nbsp;
+                       + (salary.add(bonus.add(comm))));
+}
+rs.close();
+<B>// once we've iterated through the last row,
+// the transaction commits automatically and releases
+//shared locks</B>
+s.close();
+</PRE>
+<P><HR>[ <A HREF="develop64.html">Previous Page</A><br><A HREF="develop66.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop66.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop66.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,117 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Updatable Cursors</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="requirements for being updatable, Cursors, updatable, naming, accessing system-generated names">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-CONCEPTS-28351">Updatable Cursors</H1>
+<P>Cursors are read-only by default. For a cursor to be updatable, you
+must specify SELECT . . . FOR UPDATE. Use FOR
+UPDATE only when you will be modifying rows to avoid excessive locking of
+tables.
+<UL>
+<LI><A HREF="#HDRSII-CONCEPTS-30811">Requirements for Updatable Cursors</A>
+</LI><LI><A HREF="#HDRSII-CONCEPTS-41704">Naming or Accessing the Name of a Cursor</A>
+</LI><LI><A HREF="#HDRSII-CONCEPTS-38274">Extended Updatable Cursor Example</A>
+</LI></UL>
+<P><H1><A NAME="HDRSII-CONCEPTS-30811">Requirements for Updatable Cursors</H1>
+<A NAME="IDX661"></A>
+<A NAME="IDX662"></A>
+<P>Only specific SELECT statements--simple accesses of a single
+table--allow you to update or delete rows as you step through
+them.
+<P>For more information, see &quot;SELECT statement&quot; and &quot;FOR UPDATE
+clause&quot; in the <CITE>Derby Reference Manual</CITE>.
+<P><H1><A NAME="HDRSII-CONCEPTS-41704">Naming or Accessing the Name of a Cursor</H1>
+<A NAME="IDX663"></A>
+<P>
+<A NAME="IDX664"></A>
+There is no SQL language command to <I>assign</I> a name to a
+cursor. You can use the JDBC <TT><I>setCursorName</I></TT> method
+to assign a name to a <TT><I>ResultSet</I></TT> that allows positioned
+updates and deletes. You assign a name to a
+<TT><I>ResultSet</I></TT> with the <TT><I>setCursorName</I></TT>
+method of the <TT><I>Statement</I></TT> interface. You assign the
+name to a cursor before executing the <TT><I>Statement</I></TT> that
+will generate it.
+<PRE>Statement s3 = conn.createStatement();
+<B>// name the statement so we can reference the result set
+// it generates</B>
+s3.setCursorName("UPDATABLESTATEMENT");
+<B>// we will be able to use the following statement later
+//to access the current row of the cursor</B>
+PreparedStatement ps2 = conn.prepareStatement(
+     "UPDATE FlightBookings SET number_seats = ? " +
+        "WHERE CURRENT OF UPDATABLESTATEMENT");
+</PRE>
+<P>
+<A NAME="IDX665"></A>
+More typically, you do not assign a name to the cursor, but let the system
+generate one for you automatically. You can determine the
+system-generated cursor name of a <I>ResultSet</I> generated by a SELECT
+statement using the <TT><I>ResultSet</I></TT> class's
+<TT><I>getCursorName</I></TT> method.
+<PRE>PreparedStatement ps2 = conn.prepareStatement(
+    "UPDATE employee SET bonus = ? WHERE CURRENT OF "+
+        Updatable.getCursorName());
+</PRE>
+<P><H1><A NAME="HDRSII-CONCEPTS-38274">Extended Updatable Cursor Example</H1>
+<PRE>String URL = "jdbc:derby:sample";
+<B>// autocommit must be turned off for updatable cursors</B>
+conn.setAutoCommit(false);
+Statement s3 = conn.createStatement();
+<B>// name the statement so we can reference the result set
+// it generates</B>
+s3.setCursorName("UPDATABLESTATEMENT");
+<B>// Updatable statements have some requirements</B>
+<B>// for example, select must be on a single table</B>
+ResultSet Updatable = s3.executeQuery(
+    "SELECT firstnme, lastname, workdept, bonus" +
+    "FROM employee FOR UPDATE of bonus");
+<B>// we need a separate statement to do the</B>
+<B>// update PreparedStatement</B>
+PreparedStatement ps2 = conn.prepareStatement("UPDATE employee " +
+<B>// we could use the cursor name known by the system,</B>
+<B>// as the following line shows</B>
+<B>//"SET bonus = ? WHERE CURRENT OF " + Updatable.getCursorName());</B>
+<B>// but we already know the cursor name</B>
+"SET bonus = ? WHERE CURRENT OF UPDATABLESTATEMENT");&nbsp;
+String theDept="E21";
+while (Updatable.next()) {
+    String firstnme = Updatable.getString("FIRSTNME");
+    String lastName = Updatable.getString("LASTNAME");
+    String workDept = Updatable.getString("WORKDEPT");
+    BigDecimal bonus = Updatable.getBigDecimal("BONUS");
+    if (workDept.equals(theDept)) {
+    <B>// if the current row meets our criteria,
+    // update the updatable column in the row</B>
+        ps2.setBigDecimal(1, bonus.add(new BigDecimal(250)));
+        ps2.executeUpdate();
+        System.out.println("Updating bonus in employee" +
+        " table for employee " + firstnme +
+        ", department " + theDept );
+    }&nbsp;
+    }
+Updatable.close();
+s3.close();
+ps2.close();
+conn.commit();
+</PRE>
+<P><HR>[ <A HREF="develop65.html">Previous Page</A><br><A HREF="develop67.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop67.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop67.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,28 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>ResultSets and Auto-Commit</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="behavior of with auto-commit, ResultSets">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-CONCEPTS-23987">ResultSets and Auto-Commit</H1>
+<A NAME="IDX666"></A>
+<P>Except for the result sets associated with holdable cursors (see <A HREF="develop69.html#HDRSII-CONCEPTS-HOLDABLECURSORS">Holdable Cursors</A> for more information), issuing a commit will cause all
+result sets on your connection to be closed.
+<P><HR>[ <A HREF="develop66.html">Previous Page</A><br><A HREF="develop68.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop68.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop68.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,71 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Scrolling Insensitive ResultSets</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="Scrolling insensitive cursors, scrolling insensitive (JDBC 2.0), ResultSets, scrolling insensitive, Cursors">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-CONCEPTS-22641">Scrolling Insensitive ResultSets</H1>
+<A NAME="IDX667"></A>
+<A NAME="IDX668"></A>
+<A NAME="IDX669"></A>
+<P>JDBC 2.0 adds a new kind of <TT><I>ResultSet</I></TT>, one
+that allows you to scroll in either direction or to move the cursor to a
+particular row. Derby implements scrolling insensitive
+<TT><I>ResultSets</I></TT>. When you use a scroll insensitive
+<TT><I>ResultSets</I></TT> cursor to facilitate the insensitive
+scrolling action, Derby materializes in memory all rows from the first
+one in the result set up to the one with the biggest row number.
+<PRE><B></B><B>//autocommit does not have to be off because even if&nbsp;
+//we accidentally scroll past the last row, the implicit commit
+//on the the statement will not close the result set because result sets
+//are held over commit by default</B>
+conn.setAutoCommit(false);
+Statement s4 = conn.createStatement(
+ResultSet.TYPE_SCROLL_INSENSITIVE, ResultSet.CONCUR_READ_ONLY);
+s4.execute("set schema 'SAMP'");
+ResultSet scroller=s4.executeQuery(
+    "SELECT sales_person, region, sales FROM sales " +
+    "WHERE sales &gt; 8 ORDER BY sales DESC");
+if (scroller.first())
+    System.out.println("The sales rep who sold the highest number
+				of sales is " +
+           scroller.getString("SALES_PERSON"));
+else
+    System.out.println("There are no rows.");
+scroller.beforeFirst();
+scroller.afterLast();
+scroller.absolute(3);
+if (!scroller.isAfterLast())&nbsp;
+    System.out.println("The employee with the third highest number
+				of sales is " +
+           scroller.getString("SALES_PERSON") + ", with " +
+           scroller.getInt("SALES") + " sales");
+if (scroller.isLast())
+    System.out.println("There are only three rows.");
+if (scroller.last())
+    System.out.println("The least highest number
+				of sales of the top three sales is: " +
+           scroller.getInt("SALES"));
+scroller.close();
+s4.close();
+conn.close();
+System.out.println("Closed connection");
+</PRE>
+<P><HR>[ <A HREF="develop67.html">Previous Page</A><br><A HREF="develop69.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop69.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop69.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,96 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Holdable Cursors</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="holdable, Cursors, Holdable cursors and autocommit, holdable cursors and, Autocommit">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-CONCEPTS-HOLDABLECURSORS">Holdable Cursors</H1>
+<A NAME="IDX670"></A>
+<DL><DT><B>Note:</B></DT><DD>Non-holdable cursors are only available in Java<SUP>(TM)</SUP> 2 Platform, Standard
+Edition, v 1.4 (J2SE) environments.
+</DD></DL>
+<P>The holdable cursor feature permits an application to keep cursors open
+after implicit or explicit commits. By default, the cursors are held
+open after a commit. Starting with Java<SUP>(TM)</SUP> 2 Platform, Standard
+Edition, v 1.4 (J2SE), cursors can be created with close when a commit
+occurs option. Such cursors will be automatically closed when a commit
+happens. Cursors are automatically closed when a transaction aborts,
+whether or not they have been specified to be held open.
+<DL><DT><B>Note:</B></DT><DD>Holdable cursors do not work with XA transactions, in Derby Version 10, therefore cursors should be opened with holdability false when working
+with XA transactions.
+</DD></DL>
+<P>To specify whether a cursor should be held open after a commit takes place,
+supply one of the following <I>ResultSet</I> parameters to the
+<TT><I>Connection</I></TT> method <TT><I>createStatement</I></TT>,
+<TT><I>prepareStatement</I></TT>, or
+<TT><I>prepareCall</I></TT>:
+<UL>
+<LI><I>CLOSE_CURSORS_AT_COMMIT</I> 
+<P>Cursors are closed when an implicit or explicit commit is performed.
+</LI><LI><I>HOLD_CURSORS_OVER_COMMIT</I> 
+<P>Cursors are held open when a commit is performed, implicitly or
+explicitly. This is the default behavior.
+</LI></UL>
+<P>The method <I>Statement.getResultSetHoldability()</I> indicates
+whether a cursor generated by the Statement object stays open or closes, upon
+commit. See the <CITE>Derby Reference Manual</CITE> for more
+information.
+<P>When an implicit or explicit commit occurs, <I>ResultSets</I> that hold
+cursors open behave as follows:
+<UL>
+<LI>Open <I>ResultSets</I> remain open. The cursor is positioned
+before the next logical row of the result set.
+</LI><LI>When the session is terminated, the <I>ResultSet</I> is closed and
+destroyed.
+</LI><LI>All locks are released, except locks protecting the current cursor
+position of open cursors specified to stay open after commits.
+</LI><LI>Immediately following a commit, the only valid operations that can be
+performed on the <I>ResultSet</I> are: 
+<UL>
+<LI>positioning the <I>ResultSet</I> to the next valid row in the result
+with <TT><I>ResultSet.next()</I></TT>.
+</LI><LI>closing the <I>ResultSet</I> with
+<TT><I>ResultSet.close()</I></TT>.
+</LI></UL>
+</LI></UL>
+<P>When a rollback occurs either explicitly or implicitly, the following
+behavior applies:
+<UL>
+<LI>All open <I>ResultSets</I> are closed.
+</LI><LI>All locks acquired during the unit of work are released.
+</LI></UL>
+<P><H1><A NAME="HDRCONCEPTS840995">Holdable Cursors and Autocommit</H1>
+<A NAME="IDX671"></A>
+<A NAME="IDX672"></A>
+<P>When autocommit is on, positioned updates and deletes are not supported for
+<I>ResultSet </I>objects that hold cursors open. If you attempt an
+update or delete, an exception is thrown.
+<P><H1><A NAME="HDRCONCEPTS841119">Non-Holdable Cursor Example</H1>
+<P>The following example uses <I>Connection.createStatement</I> to
+return a <TT><I>ResultSet</I></TT> that will close after a commit is
+performed:
+<PRE>Connection conn = ds.getConnection(user, passwd);
+Statement stmt =
+conn.createStatement(ResultSet.TYPE_SCROLL_INSENSITIVE,
+                  ResultSet.CONCUR_READ_ONLY,
+                  ResultSet.CLOSE_CURSORS_AT_COMMIT);
+ 
+</PRE>
+<P><HR>[ <A HREF="develop68.html">Previous Page</A><br><A HREF="develop70.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop70.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop70.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,40 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Locking, Concurrency, and Isolation</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="Transaction isolation levels, Isolation levels, Locking, Concurrency">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<HR><H1 NAME="HDRSII-CONCEPTS-30291">Locking, Concurrency, and Isolation</H1>
+<A NAME="IDX673"></A>
+<A NAME="IDX674"></A>
+<A NAME="IDX675"></A>
+<A NAME="IDX676"></A>
+<P>This section discusses topics pertinent to multi-user systems, in which
+concurrency is important. Derby is configured by default to work
+well for multi-user systems. For single-user systems, you might want to
+tune your system so that it uses fewer resources; see <A HREF="develop73.html#HDRSII-CONCEPTS-23810">Lock Granularity</A>.
+<UL>
+<LI><A HREF="develop71.html#HDRSII-CONCEPTS-15366">Isolation Levels and Concurrency</A>
+</LI><LI><A HREF="develop72.html#HDRSII-CONCEPTS-22300">Configuring Isolation Levels</A>
+</LI><LI><A HREF="develop73.html#HDRSII-CONCEPTS-23810">Lock Granularity</A>
+</LI><LI><A HREF="develop74.html#HDRSII-CONCEPTS-36402">Types and Scope of Locks in Derby Systems</A>
+</LI><LI><A HREF="develop75.html#HDRSII-CONCEPTS-28436">Deadlocks</A>
+</LI></UL>
+<P><HR>[ <A HREF="develop69.html">Previous Page</A><br><A HREF="develop71.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop71.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop71.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,205 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Isolation Levels and Concurrency</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="java.sql.Connection.TRANSACTION_READ_UNCOMMITTED, java.sql.Connection.TRANSACTION_READ_COMMITTED, java.sql.Connection.TRANSACTION_SERIALIZABLE, description, Transaction anomalies in generic database systems, definition, Dirty reads, Non-repeatable reads, Phantom reads, TRANSACTION_SERIALIZABLE isolation level, TRANSACTION_REPEATABLE_READ isolation level, TRANSACTION_READ_COMMITTED isolation level, TRANSACTION_READ_UNCOMMITTED isolation level">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-CONCEPTS-15366">Isolation Levels and Concurrency</H1>
+<P>Derby provides four transaction isolation levels. Setting the
+transaction isolation level for a connection allows a user to specify how
+severely the user's transaction should be isolated from other
+transactions. For example, it allows you to specify whether transaction
+A is allowed to make changes to data that have been viewed by transaction B
+before transaction B has committed.
+<P>A connection determines its own isolation level, so JDBC provides an
+application with a way to specify a level of transaction isolation. It
+specifies four levels of transaction isolation. The higher the
+transaction isolation, the more care is taken to avoid conflicts;
+avoiding conflicts sometimes means locking out transactions. Lower
+isolation levels thus allow greater concurrency.
+<P>Inserts, updates, and deletes always behave the same no matter what the
+isolation level is. Only the behavior of select statements
+varies.
+<P>To set isolation levels you can use the JDBC
+<I>Connection.setIsolationLevel</I> method or the SQL SET ISOLATION
+statement. The names of the isolation levels are different, depending
+on whether you use a JDBC method or SQL statement. <A HREF="#TBLSII-CONCEPTS-ISO_LEVEL">Table 3</A> shows the equivalent names for isolation levels whether they
+are set through the JDBC method or an SQL statement.
+<BR>
+<P><B><A NAME="TBLSII-CONCEPTS-ISO_LEVEL">Table 3. Mapping of JDBC transaction isolation levels to Derby isolation levels</A></B><BR>
+<TABLE WIDTH="100%" BORDER>
+<TR>
+<TH ALIGN="LEFT" VALIGN="TOP" ID="WQ11" WIDTH="58%">Isolation levels for JDBC
+</TH><TH ALIGN="LEFT" VALIGN="TOP" ID="WQ12" WIDTH="42%">Isolation levels for SQL
+</TH></TR><TR>
+<TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ11" WIDTH="58%">Connection.TRANSACTION_READ_ UNCOMMITTED (ANSI level 0)
+<A NAME="IDX677"></A>
+</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ12" WIDTH="42%">UR, DIRTY READ, READ UNCOMMITTED
+</TD></TR><TR>
+<TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ11" WIDTH="58%">Connection.TRANSACTION_READ_COMMITTED (ANSI level 1) 
+<A NAME="IDX678"></A>
+</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ12" WIDTH="42%">CS, CURSOR STABILITY, READ COMMITTED
+</TD></TR><TR>
+<TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ11" WIDTH="58%">Connection.TRANSACTION_REPEATABLE_READ (ANSI level 2) 
+<A NAME="IDX679"></A>
+</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ12" WIDTH="42%">RS
+</TD></TR><TR>
+<TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ11" WIDTH="58%">Connection.TRANSACTION_SERIALIZABLE (ANSI level 3) 
+<A NAME="IDX680"></A>
+</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ12" WIDTH="42%">RR, REPEATABLE READ, SERIALIZABLE
+</TD></TR></TABLE>
+<P>
+<A NAME="IDX681"></A>
+These levels allow you to avoid particular kinds of transaction anomalies,
+which are described in <A HREF="#TBLSII-CONCEPTS-17741">Table 4</A>.
+<BR>
+<P><B><A NAME="TBLSII-CONCEPTS-17741">Table 4. Transaction Anomalies</A></B><BR>
+<TABLE WIDTH="100%" BORDER>
+<TR>
+<TH ALIGN="LEFT" VALIGN="BOTTOM" ID="WQ14" WIDTH="49%">Anomaly
+</TH><TH ALIGN="LEFT" VALIGN="BOTTOM" ID="WQ15" WIDTH="52%">Example
+</TH></TR><TR>
+<TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ14" WIDTH="49%">Dirty Reads
+<A NAME="IDX682"></A>
+<P>
+<P>A dirty read happens when a transaction reads data that is being modified
+by another transaction that has not yet committed.
+</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ15" WIDTH="52%">Transaction A begins. 
+<PRE>UPDATE employee SET salary = 31650
+WHERE empno = '000090'
+</PRE> Transaction B begins. 
+<PRE>SELECT * FROM employee
+</PRE> (Transaction B sees data updated by transaction A. Those updates
+have not yet been committed.)
+</TD></TR><TR>
+<TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ14" WIDTH="49%">Non-Repeatable Reads
+<A NAME="IDX683"></A>
+<P>
+<P>Non-repeatable reads happen when a query returns data that would be
+different if the query were repeated within the same transaction.
+Non-repeatable reads can occur when other transactions are modifying data that
+a transaction is reading.
+</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ15" WIDTH="52%">Transaction A begins. 
+<PRE>SELECT * FROM employee
+WHERE empno = '000090'&nbsp;
+</PRE> Transaction B begins. 
+<PRE>UPDATE employee SET salary = 30100
+WHERE empno = '000090'
+</PRE> (Transaction B updates rows viewed by transaction A before transaction
+A commits.) If Transaction A issues the same SELECT statement, the
+results will be different.
+</TD></TR><TR>
+<TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ14" WIDTH="49%">Phantom Reads
+<A NAME="IDX684"></A>
+<P>
+<P>Records that appear in a set being read by another transaction.
+Phantom reads can occur when other transactions insert rows that would satisfy
+the WHERE clause of another transaction's statement.
+</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ15" WIDTH="52%">Transaction A begins. 
+<PRE>SELECT * FROM employee
+ WHERE salary &gt; 30000&nbsp;
+</PRE> Transaction B begins. 
+<PRE>INSERT INTO employee
+(empno, firstnme, midinit,
+lastname, job,
+salary) VALUES ('000350', 'NICK',
+'A','GREEN','LEGAL COUNSEL',35000)
+</PRE> Transaction B inserts a row that would satisfy the query in Transaction
+A if it were issued again.
+</TD></TR></TABLE>
+<P>The transaction isolation level is a way of specifying whether these
+transaction anomalies are allowed. The transaction isolation level thus
+affects the quantity of data locked by a particular transaction. In
+addition, a DBMS's locking schema might also affect whether these
+anomalies are allowed. A DBMS can lock either the entire table or only
+specific rows in order to prevent transaction anomalies.
+<P><A HREF="#TBLSII-CONCEPTS-28076">Table 5</A> shows which anomalies are possible under the various locking
+schemas and isolation levels.
+<BR>
+<P><B><A NAME="TBLSII-CONCEPTS-28076">Table 5. When Transaction Anomalies Are Possible</A></B><BR>
+<TABLE WIDTH="100%" BORDER>
+<TR>
+<TH ALIGN="LEFT" VALIGN="BOTTOM" ID="WQ18" WIDTH="57%">Isolation Level
+</TH><TH ALIGN="LEFT" VALIGN="BOTTOM" ID="WQ19" WIDTH="21%">Table-Level Locking
+</TH><TH ALIGN="LEFT" VALIGN="BOTTOM" ID="WQ20" WIDTH="22%">Row-Level Locking
+</TH></TR><TR>
+<TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ18" WIDTH="57%">TRANSACTION_READ_UNCOMMITTED
+</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ19" WIDTH="21%">Dirty reads, nonrepeatable reads, and phantom reads possible
+</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ20" WIDTH="22%">Dirty reads, nonrepeatable reads, and phantom reads possible
+</TD></TR><TR>
+<TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ18" WIDTH="57%">TRANSACTION_READ_COMMITTED
+</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ19" WIDTH="21%">Nonrepeatable reads and phantom reads possible
+</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ20" WIDTH="22%">Nonrepeatable reads and phantom reads possible
+</TD></TR><TR>
+<TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ18" WIDTH="57%">TRANSACTION_REPEATABLE_READ
+</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ19" WIDTH="21%">Phantom reads not possible because entire table is locked
+</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ20" WIDTH="22%">Phantom reads possible
+</TD></TR><TR>
+<TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ18" WIDTH="57%">TRANSACTION_SERIALIZABLE
+</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ19" WIDTH="21%">None
+</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ20" WIDTH="22%">None
+</TD></TR></TABLE>
+<P>The following <I>java.sql.Connection</I> isolation levels
+are supported:
+<UL>
+<LI>
+<A NAME="IDX685"></A>
+<TT>TRANSACTION_SERIALIZABLE</TT>
+<P><TT>RR</TT>, <TT>SERIALIZABLE</TT>, or <TT>REPEATABLE READ</TT> from
+SQL.
+<P><I>TRANSACTION_SERIALIZABLE</I> means that Derby treats the
+transactions as if they occurred serially (one after the other) instead of
+concurrently. Derby issues locks to prevent all the transaction
+anomalies listed in <A HREF="#TBLSII-CONCEPTS-17741">Table 4</A> from occurring. The type of lock it issues is sometimes
+called a <I>range lock</I>. For more information about range locks,
+see <A HREF="develop74.html#HDRCONCEPTS842524">Scope of Locks</A>.
+</LI><LI>
+<A NAME="IDX686"></A>
+<TT>TRANSACTION_REPEATABLE_READ</TT> 
+<P><TT>RS</TT> from SQL.
+<P><I>TRANSACTION_REPEATABLE_READ</I> means that Derby issues locks
+to prevent only dirty reads and non-repeatable reads, but not phantoms.
+It does not issue range locks for selects.
+</LI><LI>
+<A NAME="IDX687"></A>
+<TT>TRANSACTION_READ_COMMITTED</TT> 
+<P><TT>CS</TT> or <TT>CURSOR STABILITY</TT> from SQL.
+<P><I>TRANSACTION_READ_COMMITTED</I> means that Derby issues locks to
+prevent only dirty reads, not all the transaction anomalies listed in <A HREF="#TBLSII-CONCEPTS-17741">Table 4</A>.
+<P><I>TRANSACTION_READ_COMMITTED</I> is the default isolation level for
+transactions.
+</LI><LI>
+<A NAME="IDX688"></A>
+<TT>TRANSACTION_READ_UNCOMMITTED</TT> 
+<P><TT>UR</TT>, <TT>DIRTY READ</TT>, or <TT>READ UNCOMMITTED</TT> from
+SQL.
+<P>For a SELECT INTO, FETCH with a read-only cursor, full select used in an
+INSERT, full select/subquery in an UPDATE/DELETE, or scalar full select
+(wherever used), READ UNCOMMITTED allows:
+<UL>
+<LI>Any row that is read during the unit of work to be changed by other
+application processes.
+</LI><LI>Any row that was changed by another application process to be read even if
+the change has not been committed by the application process.
+</LI></UL>
+<P>For other operations, the rules that apply to READ COMMITTED also apply to
+READ UNCOMMITTED.
+</LI></UL>
+<P><HR>[ <A HREF="develop70.html">Previous Page</A><br><A HREF="develop72.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop72.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop72.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,48 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Configuring Isolation Levels</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="configuring, Isolation levels">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-CONCEPTS-22300">Configuring Isolation Levels</H1>
+<A NAME="IDX689"></A>
+<P>If a connection does not specify its isolation level, it inherits the
+default isolation level for the Derby system, The default value is
+<TT>CS</TT>. When set to <TT>CS</TT>, the connection inherits the
+TRANSACTION_READ_COMMITTED isolation level. When set to <TT>RR</TT>,
+the connection inherits the TRANSACTION_SERIALIZABLE isolation level, when set
+to <TT>RS</TT>, the connection inherits the TRANSACTION_REPEATABLE_READ
+isolation level, and when set to <TT>UR</TT>, the connection inherits the
+TRANSACTION_READ_UNCOMMITTED isolation level.
+<P>To override the inherited default, use the methods of
+<I>java.sql.Connection</I>.
+<P>In addition, a connection can change the isolation level of the transaction
+within an SQL statement. For more information, see &quot;SET ISOLATION
+statement&quot; in the <CITE>Derby Reference Manual</CITE>. You
+can use the WITH clause to change the isolation level for the current
+statement only, not the transaction. For information about the&quot;WITH
+clause,&quot; see the &quot;SELECT statement&quot;in the <CITE>Derby
+Reference Manual</CITE>.
+<P>In all cases except when you change the isolation level using the WITH
+clause, changing the isolation level commits the current transaction.
+<DL><DT><B>Note:</B></DT><DD>For information about how to choose a particular isolation level, see
+<CITE>Tuning Derby</CITE>.
+</DD></DL>
+<P><HR>[ <A HREF="develop71.html">Previous Page</A><br><A HREF="develop73.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop73.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop73.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,49 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Lock Granularity</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="Lock granularity, table-level, Locking, row-level">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-CONCEPTS-23810">Lock Granularity</H1>
+<A NAME="IDX690"></A>
+<A NAME="IDX691"></A>
+<A NAME="IDX692"></A>
+<P><A NAME="SPTSII-CONCEPTS-18383"></A>Derby can be configured
+for <I>table-level</I> locking. With table-level locking, when a
+transaction locks data in order to prevent any transaction anomalies, it
+always locks the entire table, not just those rows being accessed.
+<P>By default, Derby is configured for row-level locking.
+Row-level locking uses more memory but allows greater concurrency, which works
+better in multi-user systems. Table-level locking works best with
+single-user applications or read-only applications.
+<P>You typically set lock granularity for the entire Derby system, not
+for a particular application. However, at runtime, Derby may
+escalate the lock granularity for a particular transaction from row-level
+locking to table-level locking for performance reasons. You have some
+control over the threshold at which this occurs. For information on
+turning off row-level locking, see
+<I>&quot;derby.storage.rowLocking&quot; </I> in
+<CITE>Tuning Derby</CITE>. For more information about automatic
+lock escalation, see &quot;About the System's Selection of Lock
+Granularity&quot; and &quot;Transaction-Based Lock Escalation&quot; in
+<CITE>Tuning Derby</CITE><CITE>. </CITE>For more information on
+tuning your Derby system, see &quot;Tuning Databases and
+Applications&quot;.
+<P><HR>[ <A HREF="develop72.html">Previous Page</A><br><A HREF="develop74.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop74.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop74.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,196 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Types and Scope of Locks in Derby Systems</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="exclusive, Locks, shared, update, definition, Exclusive locks, Shared locks, Update locks, scope of">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-CONCEPTS-36402">Types and Scope of Locks in Derby Systems</H1>
+<A NAME="IDX693"></A>
+<A NAME="IDX694"></A>
+<A NAME="IDX695"></A>
+<P><H1><A NAME="HDRCONCEPTS842279">Exclusive Locks</H1>
+<P>
+<A NAME="IDX696"></A>
+<A NAME="IDX697"></A>
+When a statement modifies data, its transaction holds an <I>exclusive</I>
+lock on data that prevents other transactions from accessing the data.
+This lock remains in place until the transaction holding the lock issues a
+commit or rollback. Table-level locking lowers concurrency in a
+multi-user system.
+<P><H1><A NAME="HDRCONCEPTS842304">Shared Locks</H1>
+<P>When a statement reads data without making any modifications, its
+transaction obtains a <I>shared lock</I> on the data. Another
+transaction that tries to read the same data is permitted to read, but a
+transaction that tries to update the data will be prevented from doing so
+until the shared lock is released. How long this shared lock is held
+depends on the isolation level of the transaction holding the lock.
+Transactions using the TRANSACTION_READ_COMMITTED isolation level release the
+lock when the transaction steps through to the next row. Transactions
+using the TRANSACTION_SERIALIZABLE or TRANSACTION_REPEATABLE_READ isolation
+level hold the lock until the transaction is committed, so even a SELECT can
+prevent updates if a commit is never issued. Transactions using the
+TRANSACTION_READ_UNCOMMITTED isolation level do not request any locks.
+<P><H1><A NAME="HDRCONCEPTS842385">Update Locks</H1>
+<P>
+<A NAME="IDX698"></A>
+When a user-defined update cursor (created with the FOR UPDATE clause) reads
+data, its transaction obtains an <I>update </I>lock on the data. If
+the user-defined update cursor updates the data, the update lock is converted
+to an exclusive lock. If the cursor does not update the row, when the
+transaction steps through to the next row, transactions using the
+TRANSACTION_READ_COMMITTED isolation level release the lock, and transactions
+using the TRANSACTION_SERIALIZABLE or TRANSACTION_REPEATABLE_READ isolation
+level downgrade it to a shared lock until the transaction is committed.
+(For update locks, the TRANSACTION_READ_UNCOMMITTED isolation level acts the
+same way as TRANSACTION_READ_COMMITTED.)
+<P>Update locks help minimize deadlocks.
+<P><H1><A NAME="HDRCONCEPTS842462">Lock Compatibility</H1>
+<P><A HREF="#TBLSII-CONCEPTS-LOCK_MTRX">Table 6</A> lists compatibility between lock types.
+<CITE>+</CITE> means compatible, <CITE>-</CITE> means incompatible.
+<BR>
+<P><B><A NAME="TBLSII-CONCEPTS-LOCK_MTRX">Table 6. Lock Compatibility Matrix</A></B><BR>
+<TABLE WIDTH="100%" BORDER>
+<TR>
+<TD ALIGN="LEFT" VALIGN="TOP" WIDTH="29%">
+<BR></TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH="24%">Shared
+</TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH="24%">Update
+</TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH="24%">Exclusive
+</TD></TR><TR>
+<TD ALIGN="LEFT" VALIGN="TOP" WIDTH="29%">Shared
+</TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH="24%">
+<P>+
+<BR></TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH="24%">
+<P>-
+<BR></TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH="24%">
+<P>-
+<BR></TD></TR><TR>
+<TD ALIGN="LEFT" VALIGN="TOP" WIDTH="29%">Update
+</TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH="24%">
+<P>+
+<BR></TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH="24%">
+<P>-
+<BR></TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH="24%">
+<P>-
+<BR></TD></TR><TR>
+<TD ALIGN="LEFT" VALIGN="TOP" WIDTH="29%">Exclusive
+</TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH="24%">
+<P>-
+<BR></TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH="24%">
+<P>-
+<BR></TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH="24%">
+<P>-
+<BR></TD></TR></TABLE>
+<P><H1><A NAME="HDRCONCEPTS842524">Scope of Locks</H1>
+<A NAME="IDX699"></A>
+<P>The amount of data locked by a statement can vary.
+<UL>
+<LI><I>table locks</I> 
+<P>A statement can lock the <I>entire table</I>.
+<P>Table-level locking systems always lock entire tables.
+<P>Row-level locking systems can lock entire tables if the WHERE clause of a
+statement cannot use an index. For example, UPDATES that cannot use an
+index lock the entire table.
+<P>Row-level locking systems can lock entire tables if a high number of
+single-row locks would be less efficient than a single table-level
+lock. Choosing table-level locking instead of row-level locking for
+performance reasons is called <I>lock escalation</I>. (For more
+information about this topic, see &quot;About the System's Selection of
+Lock Granularity&quot; and &quot;Transaction-Based Lock Escalation&quot; in
+<CITE>Tuning Derby</CITE>.)
+</LI><LI><I>single-row locks</I> 
+<P>A statement can lock only <I>a single row</I> at a time.
+<P>This section applies only to row-level locking systems.
+<P>For TRANSACTION_READ_COMMITTED or TRANSACTION_REPEATABLE_READ isolation,
+Derby treats rows as cursors for SELECT statements. It locks rows
+only as the application steps through the rows in the result. The
+current row is locked. The row lock is released when the application
+goes to the next row. (For TRANSACTION_SERIALIZABLE isolation, however,
+Derby locks the whole set before the application begins stepping
+through.) For TRANSACTION_READ_UNCOMMITTED, no row locks are
+requested.
+<P>Derby locks single rows for INSERT statements, holding each row until
+the transaction is committed. (If there is an index associated with the
+table, the previous key is also locked.)
+</LI><LI><I>range locks</I> 
+<P>A statement can lock <I>a range of rows</I> (range lock).
+<P>This section applies only to row-level locking systems.
+<P>For <I>any</I> isolation level, Derby locks <I>all the rows in
+the result</I> plus an entire range of rows for updates or deletes.
+<P>For the TRANSACTION_SERIALIZABLE isolation level, Derby locks all the
+rows in the result plus an entire range of rows in the table for SELECTs to
+prevent nonrepeatable reads and phantoms.
+<P>For example, if a SELECT statement specifies rows in the
+<I>Employee</I> table where the <I>salary</I> is BETWEEN two values,
+the system can lock more than just the actual rows it returns in the
+result. It also must lock the entire <I>range</I> of rows between
+those two values to prevent another transaction from inserting, deleting, or
+updating a row within that range.
+<P>An index must be available for a range lock. If one is not
+available, Derby locks the entire table.
+<BR>
+<P><B><A NAME="TBLSII-CONCEPTS-15873">Table 7. Possible Types and Scopes of Locking</A></B><BR>
+<TABLE  BORDER>
+<TR>
+<TH ALIGN="LEFT" VALIGN="BOTTOM" ID="WQ28" WIDTH="30%">Transaction Isolation Level
+</TH><TH ALIGN="LEFT" VALIGN="BOTTOM" ID="WQ29" WIDTH="25%">Table-Level Locking
+</TH><TH ALIGN="LEFT" VALIGN="BOTTOM" ID="WQ30" WIDTH="45%">Row-Level Locking
+</TH></TR><TR>
+<TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ28" WIDTH="30%">Connection. TRANSACTION_ READ_UNCOMMITED (SQL: UR)
+</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ29" WIDTH="25%">For SELECT statements, table-level locking is never requested using this
+isolation level. For other statements, same as for TRANSACTION_ READ_
+COMMITTED.
+</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ30" WIDTH="45%">SELECT statements get no locks. For other statements, same as for
+TRANSACTION_ READ_COMMITTED.
+</TD></TR><TR>
+<TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ28" WIDTH="30%">Connection. TRANSACTION_ READ_COMMITTED (SQL: CS)
+</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ29" WIDTH="25%">SELECT statements get a shared lock on the entire table. The locks
+are released when the user closes the <I>ResultSet</I>. Other
+statements get exclusive locks on the entire table, which are released when
+the transaction commits.
+</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ30" WIDTH="45%">SELECTs lock and release single rows as the user steps through the
+<I>ResultSet</I>. UPDATEs and DELETEs get exclusive locks on a
+range of rows. INSERT statements get exclusive locks on single rows
+(and sometimes on the preceding rows).
+</TD></TR><TR>
+<TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ28" WIDTH="30%">Connection. TRANSACTION_ REPEATABLE_READ (SQL: RS)
+</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ29" WIDTH="25%">Same as for TRANSACTION_ SERIALIZABLE
+</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ30" WIDTH="45%">SELECT statements get shared locks on the rows that satisfy the WHERE
+clause (but do not prevent inserts into this range). UPDATEs and
+DELETEs get exclusive locks on a range of rows. INSERT statements get
+exclusive locks on single rows (and sometimes on the preceding rows).
+</TD></TR><TR>
+<TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ28" WIDTH="30%">Connection. TRANSACTION_ SERIALIZABLE (SQL: RR)
+</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ29" WIDTH="25%">SELECT statements get a shared lock on the entire table. Other
+statements get exclusive locks on the entire table, which are released when
+the transaction commits.
+</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ30" WIDTH="45%">SELECT statements get shared locks on a range of rows. UPDATE and
+DELETE statements get exclusive locks on a range of rows. INSERT
+statements get exclusive locks on single rows (and sometimes on the preceding
+rows).
+</TD></TR></TABLE>
+</LI></UL>
+<P><H1><A NAME="HDRCONCEPTS842613">Notes on Locking</H1>
+<P>In addition to the locks already described, foreign key lookups require
+briefly held shared locks on the referenced table (row or table, depending on
+the configuration).
+<P>The table and examples in this section do not take performance-based lock
+escalation into account. Remember that the system can choose
+table-level locking for performance reasons.
+<P><HR>[ <A HREF="develop73.html">Previous Page</A><br><A HREF="develop75.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop75.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop75.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,180 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Deadlocks</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="description, Deadlocks, Deadlock detection, detecting, programming an application to handle">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-CONCEPTS-28436">Deadlocks</H1>
+<A NAME="IDX700"></A>
+<P>In a database, a deadlock is a situation in which two or more transactions
+are waiting for one another to give up locks.
+<P>For example, Transaction A might hold a lock on some rows in the
+<I>Accounts</I> table and needs to update some rows in the
+<I>Orders</I> table to finish. Transaction B holds locks on those
+very rows in the <I>Orders</I> table but needs to update the rows in the
+<I>Accounts</I> table held by Transaction A. Transaction A cannot
+complete its transaction because of the lock on <I>Orders</I>.
+Transaction B cannot complete its transaction because of the lock on
+<I>Accounts</I>. All activity comes to a halt and remains at a
+standstill forever unless the DBMS detects the deadlock and aborts one of the
+transactions.
+<P><B><A NAME="Figure_6">Figure 6. A deadlock.</A></B><BR>
+<BR><IMG SRC="images/dead.gif" ALT="This figure depicts a deadlock, where two transactions are waiting for one another to give up locks."><BR>
+<P><H1><A NAME="HDRSII-CONCEPTS-53677">Avoiding Deadlocks</H1>
+<P>Using both row-level locking and the TRANSACTION_READ_COMMITTED isolation
+level makes it likely that you will avoid deadlocks (both settings are
+Derby defaults). However, deadlocks are still possible.
+Derby application developers can avoid deadlocks by using consistent
+application logic; for example, transactions that access
+<I>Accounts</I> and <I>Orders</I> should always access the tables in
+the same order. That way, in the scenario described above, Transaction
+B simply waits for transaction A to release the lock on <I>Orders</I>
+before it begins. When transaction A releases the lock on
+<I>Orders</I>, Transaction B can proceed freely.
+<P>Another tool available to you is the LOCK TABLE statement. A
+transaction can attempt to lock a table in exclusive mode when it starts to
+prevent other transactions from getting shared locks on a table. For
+more information, see &quot;LOCK TABLE statement&quot; in the <CITE>
+Derby Reference Manual</CITE>.
+<P><H1><A NAME="HDRSII-CONCEPTS-95005">Deadlock Detection</H1>
+<A NAME="IDX701"></A>
+<P>When a transaction waits more than a specific amount of time to obtain a
+lock (called the deadlock timeout), Derby can detect whether the
+transaction is involved in a deadlock. When Derby analyzes such a
+situation for deadlocks it tries to determine how many transactions are
+involved in the deadlock (two or more). Usually aborting one
+transaction breaks the deadlock. Derby must pick one transaction
+as the victim and abort that transaction; it picks the transaction that
+holds the fewest number of locks as the victim, on the assumption that
+transaction has performed the least amount of work. (This may not be
+the case, however; the transaction might have recently been escalated
+from row-level locking to table locking and thus hold a small number of locks
+even though it has done the most work.)
+<P>When Derby aborts the victim transaction, it receives a deadlock error
+(an <I>SQLException</I> with an <TT><I>SQLState</I></TT> of
+40001). The error message gives you the transaction IDs, the
+statements, and the status of locks involved in a deadlock situation.
+<PRE>ERROR 40001: A lock could not be obtained due to a deadlock,
+cycle of locks &amp; waiters is:
+Lock : ROW, DEPARTMENT, (1,14)
+Waiting XID : {752, X} , APP, update department set location='Boise'
+	where deptno='E21'
+Granted XID : {758, X} Lock : ROW, EMPLOYEE, (2,8)
+Waiting XID : {758, U} , APP, update employee set bonus=150 where salary=23840
+Granted XID : {752, X} The selected victim is XID : 752
+</PRE>
+<P>For information on configuring when deadlock checking occurs, see <A HREF="#HDRSII-CONCEPTS-16400">Configuring Deadlock Detection and Lock Wait Timeouts</A>.
+<DL><DT><B>Note:</B></DT><DD>Deadlocks are detected only within a single database. Deadlocks across
+multiple databases are not detected. Non-database deadlocks caused by
+Java synchronization primitives are not detected by Derby.
+</DD></DL>
+<P><H1><A NAME="HDRSII-CONCEPTS-89097">Lock Wait Timeouts</H1>
+<P>Even if a transaction is not involved in a deadlock, it might have to wait
+a considerable amount of time to obtain a lock because of a long-running
+transaction or transactions holding locks on the tables it needs. In
+such a situation, you might not want a transaction to wait
+indefinitely. Instead, you might want the waiting transaction to abort,
+or <I>time out</I>, after a reasonable amount of time, called a <I>lock
+wait timeout</I>. (For information about configuring the lock wait
+timeout, see <A HREF="#HDRSII-CONCEPTS-16400">Configuring Deadlock Detection and Lock Wait Timeouts</A>.)
+<P><H1><A NAME="HDRSII-CONCEPTS-16400">Configuring Deadlock Detection and Lock Wait Timeouts</H1>
+<P>You configure the amount of time a transaction waits before Derby does
+any deadlock checking with the
+<I>derby.locks.deadlockTimeout</I> property. You
+configure the amount of time a transaction waits before timing out with the
+<TT><I>derby.locks.waitTimeout</I></TT>
+property. When configuring your database or system, you should consider
+these properties together. For example, in order for any deadlock
+checking to occur, the
+<TT><I>derby.locks.deadlockTimeout</I></TT> property
+must be set to a value lower than the
+<TT><I>derby.locks.waitTimeout</I></TT>
+property. If it is set to a value equal to or higher than the
+<TT><I>derby.locks.waitTimeout</I></TT>, the
+transaction times out before Derby does any deadlock checking.
+<P>
+<A NAME="IDX702"></A>
+By default, <I>derby.locks.waitTimeout</I> is set to 60
+seconds. -1 is the equivalent of no wait timeout. This means
+that transactions never time out, although Derby can choose a transaction
+as a deadlock victim.
+<P><B><A NAME="FIGSII-CONCEPTS-27089">Figure 7. One possible configuration: deadlock checking occurs when a transaction has waited 30 seconds; no lock wait timeouts occur.</A></B><BR>
+<BR><IMG SRC="images/lockwa3.gif" ALT="This illustration depicts one possible configuration: deadlock checking occurs when a transaction has waited 30 seconds; no lock wait timeouts occur."><BR>
+<P><B><A NAME="FIGSII-CONCEPTS-91443">Figure 8. Another typical configuration: deadlock checking occurs after a transaction has waited 60 seconds for a lock; after 90 seconds, the transaction times out and is rolled back.</A></B><BR>
+<BR><IMG SRC="images/lockwa1.gif" ALT="This illustration depicts another typical configuration: deadlock checking occurs after a transaction has waited 60 seconds for a lock; after 90 seconds, the transaction times out and is rolled back."><BR>
+<P><B><A NAME="FIGSII-CONCEPTS-14875">Figure 9. A configuration in which no deadlock checking occurs: transactions time out after they have waited 50 seconds. No deadlock checking occurs.</A></B><BR>
+<BR><IMG SRC="images/lockwa2.gif" ALT="This illustration depicts a configuration in which no deadlock checking occurs: transactions time out after they have waited 50 seconds. No deadlock checking occurs."><BR>
+<P><H1><A NAME="HDRSII-CONCEPTS-50894">Debugging Deadlocks</H1>
+<P>If deadlocks occur frequently in your multi-user system with a particular
+application, you might need to do some debugging. Derby provides a
+class to help you in this situation,
+<I>org.apache.derby.diag.LockTable</I>. You
+can also set the property
+<I>derby.locks.deadlockTrace</I> to dump additional
+information to the derby.log file about any deadlocks that occur
+on your system. See the Tuning Guide for more information on this
+property. For information, see the <CITE>Derby Server and
+Administration Guide</CITE>.
+<P><H1><A NAME="HDRSII-CONCEPTS-32861">Programming Applications to Handle Deadlocks</H1>
+<A NAME="IDX703"></A>
+<P>When you configure your system for deadlock and lockwait timeouts and an
+application could be chosen as a victim when the transaction times out, you
+should program your application to handle this. To do this, test for
+<I>SQLExceptions</I> with <TT><I>SQLStates</I></TT> of 40001
+(deadlock timeout) or 40XL1 or 40XL2 (lockwait timeout).
+<P>In the case of a deadlock you might want to re-try the transaction that was
+chosen as a victim. In the case of a lock wait timeout, you probably do
+not want to do this right away.
+<P>The following code is one example of how to handle a deadlock
+timeout.
+<PRE><B>/// if this code might encounter a deadlock,&nbsp;
+// put the whole thing in a try/catch block
+// then try again if the deadlock victim exception&nbsp;
+// was thrown</B>
+try {
+    s6.executeUpdate(
+         "UPDATE employee " +&nbsp;
+         "SET bonus = 625 " + 91&nbsp;
+         "WHERE empno='000150'");&nbsp;
+    s6.executeUpdate("UPDATE project " +&nbsp;
+         "SET respemp = '000150' " +&nbsp;
+         "WHERE projno='IF1000'");&nbsp;
+}&nbsp;
+<B>// note: do not catch such exceptions in database-side methods;&nbsp;
+// catch such exceptions only at the outermost level of&nbsp;
+// application code.&nbsp;
+// See <A HREF="develop52.html#HDRSII-SPECIAL-41728">Database-Side JDBC Procedures and SQLExceptions</A>. </B>&nbsp;
+catch (SQLException se) {&nbsp;
+    if (se.getSQLState().equals("40001")) {&nbsp;
+        <B>// it was chosen as a victim of a deadlock.&nbsp;
+        // try again at least once at this point.</B>&nbsp;
+        System.out.println( "Will try the transaction again.");&nbsp;
+        s6.executeUpdate("UPDATE employee " +&nbsp;
+        "SET bonus = 625 " +&nbsp;
+        "WHERE empno='000150'");&nbsp;
+        s6.executeUpdate("UPDATE project " +&nbsp;
+        "SET respemp = 000150 " +&nbsp;
+        "WHERE projno='IF1000'");&nbsp;
+    }&nbsp;
+    else throw se;&nbsp;
+}
+ 
+</PRE>
+<P><HR>[ <A HREF="develop74.html">Previous Page</A><br><A HREF="develop76.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop76.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop76.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,31 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Working with Multiple Connections to a Single Database</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="in single application, Multiple connections">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<HR><H1 NAME="HDRSII-CONCEPTS-34828">Working with Multiple Connections to a Single Database</H1>
+<A NAME="IDX704"></A>
+<UL>
+<LI><A HREF="develop77.html#HDRSII-CONCEPTS-35713">Deployment Options and Threading and Connection Modes</A>
+</LI><LI><A HREF="develop78.html#HDRSII-CONCEPTS-10914">Multi-User Database Access</A>
+</LI><LI><A HREF="develop79.html#HDRSII-CONCEPTS-24019">Multiple Connections from a Single Application</A>
+</LI></UL>
+<P><HR>[ <A HREF="develop75.html">Previous Page</A><br><A HREF="develop77.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop77.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop77.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,87 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Deployment Options and Threading and Connection Modes</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="threading/connection modes and, Deployment modes, Multi-threaded applications, from single application running in embedded mode, Multiple connections, from multiple applications connecting to server">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-CONCEPTS-35713">Deployment Options and Threading and Connection Modes</H1>
+<A NAME="IDX705"></A>
+<P>A database can be available to multiple connections in the following
+situations:
+<UL>
+<LI>Multiple applications access a single database (possible only when
+Derby is running inside a server framework).
+</LI><LI>A single application has more than one <I>Connection</I> to the same
+database. 
+<P>The way you deploy Derby affects the ways applications can use
+multi-threading and connections, as shown in <A HREF="#TBLSII-CONCEPTS-40343">Table 8</A>.
+<BR>
+<P><B><A NAME="TBLSII-CONCEPTS-40343">Table 8. Threading and Connection Modes</A></B><BR>
+<TABLE  BORDER>
+<TR>
+<TH ALIGN="LEFT" VALIGN="BOTTOM" ID="WQ33" WIDTH="36%">Connection mode
+</TH><TH ALIGN="LEFT" VALIGN="BOTTOM" ID="WQ34" WIDTH="37%">Embedded
+</TH><TH ALIGN="LEFT" VALIGN="BOTTOM" ID="WQ35" WIDTH="27%">Server
+</TH></TR><TR>
+<TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ33" WIDTH="36%">
+<P><I>Multi-Threaded</I>
+<P>From an application, using a <I>single</I>
+<TT><I>Connection</I></TT> to a Derby database and issuing requests
+against that connection in multiple threads.
+<A NAME="IDX706"></A>
+<BR></TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ34" WIDTH="37%">Supply a single <I>Connection</I> object to separate threads.
+Derby ensures that only one operation is applied at a time for
+consistency. Server frameworks automatically manage multi-threaded
+operations. For more information, see <A HREF="develop63.html#HDRSII-CONCEPTS-19173">Transactions</A>.
+</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ35" WIDTH="27%">Server frameworks can automatically multi-thread operations.
+Remote client applications can multi-thread if desired.
+</TD></TR><TR>
+<TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ33" WIDTH="36%">
+<P><I>Multi-Connection</I>
+<P>From an application, using multiple connections to a Derby database
+and issuing requests against those connections on multiple threads.
+<P>
+<A NAME="IDX707"></A>
+<A NAME="IDX708"></A>
+(You must have a multi-user license to have more than one connection to
+Derby.)
+<BR></TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ34" WIDTH="37%">Create individual connections within a single application and use the
+appropriate connection for each JDBC request. The connections can all
+be to the same database, or can be to different databases in the same
+Derby system.
+</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ35" WIDTH="27%">Remote client applications can establish the multiple connections
+desired.
+</TD></TR><TR>
+<TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ33" WIDTH="36%">
+<P><I>Multi-User</I>
+<P>Multiple applications (or JVMs) accessing the same Derby
+database. Each user application has its own connection or connections
+to the database.
+<BR></TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ34" WIDTH="37%">Not possible. Only one application can access a database at a
+time, and only one application can access a specific system at a time.
+When using a pre-1.4 JVM, Derby might not prevent multiple
+applications from concurrently accessing the same Derby system, but do
+not allow this because such access can corrupt the databases involved.
+</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ35" WIDTH="27%">Only one server should access a database at a time. Multiple
+remote client applications can access the same server, and thus can access the
+same database at the same time through that server.
+</TD></TR></TABLE>
+</LI></UL>
+<P><HR>[ <A HREF="develop76.html">Previous Page</A><br><A HREF="develop78.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop78.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop78.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,35 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Multi-User Database Access</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="programming for, Multi-user database access">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-CONCEPTS-10914">Multi-User Database Access</H1>
+<A NAME="IDX709"></A>
+<P>Multi-user database access is possible if Derby is running inside a
+server framework.
+<P>If more than one client application tries to modify the same data, the
+connection that gets the table first gets the lock on the data (either
+specific rows or the entire table). The second connection has to wait
+until the first connection commits or rolls back the transaction in order to
+access the data. If two connections are only querying and not modifying
+data, they can both access the same data at the same time because they can
+each get a shared lock. For more information, see <A HREF="develop70.html#HDRSII-CONCEPTS-30291">Locking, Concurrency, and Isolation</A>.
+<P><HR>[ <A HREF="develop77.html">Previous Page</A><br><A HREF="develop79.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop79.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop79.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,43 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Multiple Connections from a Single Application</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-CONCEPTS-24019">Multiple Connections from a Single Application</H1>
+<P>A single application can work with multiple <I>Connections</I> to the
+same database and assign them to different threads. The application
+programmer can avoid concurrency and deadlock problems in several ways:
+<UL>
+<LI>Use the <I>TRANSACTION_READ_COMMITTED</I> isolation level and turn on
+row-level locking (the defaults).
+</LI><LI>Beware of deadlocks caused by using more than one <I>Connection</I> in
+a single thread (the most obvious case). For example, if the thread
+tries to update the same table from two different
+<TT><I>Connections</I></TT>, a deadlock can occur.
+</LI><LI>Assign <I>Connections</I> to threads that handle discrete
+tasks. For example, do not have two threads update the
+<I>Hotels</I> table. Have one thread update the <I>Hotels</I>
+table and a different one update the <I>Groups</I> table.
+</LI><LI>If threads access the same tables, commit transactions often.
+</LI><LI>Multi-threaded Java applications have the ability to self-deadlock without
+even accessing a database, so beware of that too.
+</LI><LI>Use nested connections to share the same lock space.
+</LI></UL>
+<P><HR>[ <A HREF="develop78.html">Previous Page</A><br><A HREF="develop80.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop80.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop80.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,33 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Working with Multiple Threads Sharing a Single Connection</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="Multiple threads sharing single connection">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<HR><H1 NAME="HDRSII-CONCEPTS-23499">Working with Multiple Threads Sharing a Single Connection</H1>
+<A NAME="IDX710"></A>
+<P>JDBC allows you to share a single <I>Connection</I> among multiple
+threads.
+<UL>
+<LI><A HREF="develop81.html#HDRSII-CONCEPTS-89498">Pitfalls of Sharing a Connection Among Threads</A>
+</LI><LI><A HREF="develop82.html#HDRSII-CONCEPTS-65864">Multi-thread programming tips</A>
+</LI><LI><A HREF="develop83.html#HDRSII-CONCEPTS-91600">Threads Sharing a Statement: A Case Study</A>
+</LI></UL>
+<P><HR>[ <A HREF="develop79.html">Previous Page</A><br><A HREF="develop81.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop81.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop81.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,74 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Pitfalls of Sharing a Connection Among Threads</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-CONCEPTS-89498">Pitfalls of Sharing a Connection Among Threads</H1>
+<P>Here is a review of the potential pitfalls of sharing a single
+<I>Connection</I> among multiple threads:
+<UL>
+<LI>Committing or rolling back a transaction closes all open
+<I>ResultSet</I> objects and currently executing <I>Statements</I>,
+unless you are using held cursors.
+<P>If one thread commits, it closes the <I>Statements</I> and
+<I>ResultSets</I> of all other threads using the same connection.
+</LI><LI>Executing a <I>Statement</I> automatically closes any existing open
+<I>ResultSet</I> generated by an earlier execution of that
+<I>Statement</I>.
+<P>If threads share <I>Statements</I>, one thread could close
+another's <I>ResultSet.</I>
+</LI></UL>
+<P>In many cases, it is easier to assign each thread to a distinct
+<I>Connection</I>. If thread <I>A</I> does database work that
+is not transactionally related to thread <I>B</I>, assign them to
+different <I>Connections</I>. For example, if thread <I>A</I>
+is associated with a user input window that allows users to delete hotels and
+thread <I>B</I> is associated with a user window that allows users to view
+city information, assign those threads to different
+<I>Connections</I>. That way, when thread <I>A</I> commits, it
+does not affect any <I>ResultSets</I> or <I>Statements</I> of thread
+B.
+<P>Another strategy is to have one thread do queries and another thread do
+updates. Queries hold shared locks until the transaction commits in
+SERIALIZABLE isolation mode; use READ_COMMITTED instead.
+<P>Yet another strategy is to have only one thread do database access.
+Have other threads get information from the database access thread.
+<P>Multiple threads are permitted to share a <I>Connection</I>,
+<I>Statement</I>, or <I>ResultSet</I>. However, the application
+programmer must ensure that one thread does not affect the behavior of the
+others.<TABLE BORDER WIDTH="100%"><TR><TH ALIGN="LEFT">Recommended Practices</TH><TR><TD>
+<P>Here are some tips for avoiding unexpected behavior:
+<UL>
+<LI>Avoid sharing <I>Statements</I> (and their
+<TT><I>ResultSets</I></TT>) among threads.
+</LI><LI>Each time a thread executes a<I> Statement</I>, it should process the
+results before relinquishing the <TT><I>Connection</I></TT>.
+</LI><LI>Each time a thread accesses the <I>Connection</I>, it should
+consistently commit or not, depending on application protocol.
+</LI><LI>Have one thread be the &quot;managing&quot; database <I>Connection</I>
+thread that should handle the higher-level tasks, such as establishing the
+<TT><I>Connection</I></TT>, committing, rolling back, changing
+<TT><I>Connection</I></TT> properties such as auto-commit, closing the
+<TT><I>Connection</I></TT>, shutting down the database (in an embedded
+environment), and so on.
+</LI><LI>Close <I>ResultSets</I> and <TT><I>Statements</I></TT> that are
+no longer needed in order to release resources.
+</LI></UL></TD></TR></TABLE>
+<P><HR>[ <A HREF="develop80.html">Previous Page</A><br><A HREF="develop82.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop82.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop82.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,38 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Multi-thread programming tips</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-CONCEPTS-65864">Multi-thread programming tips</H1>
+<P>Some programmers might share a <I>Connection</I> among multiple threads
+because they have experienced poor concurrency using separate
+transactions. Here are some tips for increasing concurrency:
+<UL>
+<LI>Use row-level locking.
+</LI><LI>Use the <I>TRANSACTION_READ_COMMITTED</I> isolation level.
+</LI><LI>Avoid queries that cannot use indexes; they require locking of all
+the rows in the table (if only very briefly) and might block an update.
+</LI></UL>
+<P>In addition, some programmers might share a statement among multiple
+threads to avoid the overhead of each thread's having its own.
+Using the single statement cache, threads can share the same statement from
+<I>different connections</I>. For more information, see &quot;Tuning
+Databases and Applications&quot; in <CITE>Tuning Derby</CITE>.
+<P><HR>[ <A HREF="develop81.html">Previous Page</A><br><A HREF="develop83.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop83.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop83.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,56 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Threads Sharing a Statement: A Case Study</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="dangers of, Statements shared by threads">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-CONCEPTS-91600">Threads Sharing a Statement: A Case Study</H1>
+<A NAME="IDX711"></A>
+<P>This example shows what can happen if two threads try to share a
+single<I> Statement</I>.
+<PRE>PreparedStatement ps = conn.prepareStatement(
+    "UPDATE account SET balance =  balance + ? WHERE id = ?");
+<B>/* now assume two threads T1,T2 are given this
+java.sql.PreparedStatement object </B>and that the following events
+happen in the order shown (pseudojava code)*/
+T1 - ps.setBigDecimal(1, 100.00);
+T1 - ps.setLong(2, 1234);
+T2 -  ps.setBigDecimal(1, -500.00);
+<B>// *** At this point the prepared statement has the parameters
+// -500.00 and 1234
+// T1 thinks it is adding 100.00 to account 1234 but actually
+// it is subtracting 500.00</B>
+T1 - ps.executeUpdate();
+T2 - ps.setLong(2, 5678);
+<B>// T2 executes the correct update</B>
+ T2 - ps.executeUpdate();
+<B>/* Also, the auto-commit mode of the connection can lead
+to some strange behavior.*/</B>
+</PRE>
+<P>If it is absolutely necessary, the application can get around this problem
+with Java synchronization.
+<P>If the threads each obtain their own <I>PreparedStatement</I> (with
+identical text), their <TT><I>setXXX</I></TT> calls do not interfere
+with each other. Moreover, Derby is able to share the same
+compiled query plan between the two statements; it needs to maintain only
+separate state information. However, there is the potential for
+confusion in regard to the timing of the <I>commit</I>, since a single
+<I>commit</I> commits all the statements in a transaction.
+<P><HR>[ <A HREF="develop82.html">Previous Page</A><br><A HREF="develop84.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop84.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop84.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,38 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Working with Database Threads in an Embedded Environment</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="sleep and interrupt calls, Threads, notifying, caught by Derby, interrupt calls">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<HR><H1 NAME="HDRSII-DEVELOP-22619">Working with Database Threads in an Embedded Environment</H1>
+<P>Do not use <TT><I>interrupt</I></TT> calls to notify threads that are
+accessing a database, because Derby will catch the
+<TT><I>interrupt</I></TT> call and close the connection to the
+database. Use <TT><I>wait</I></TT> and
+<TT><I>notify</I></TT> calls instead.
+<A NAME="IDX712"></A>
+<A NAME="IDX713"></A>
+<A NAME="IDX714"></A>
+<P>This will not happen in a client/server environment, but if you want your
+application to work in either environment it is good practice to follow this
+rule.
+<P>There are special considerations when working with more than one database
+thread in an application. See <A HREF="develop76.html#HDRSII-CONCEPTS-34828">Working with Multiple Connections to a Single Database</A> and <A HREF="develop80.html#HDRSII-CONCEPTS-23499">Working with Multiple Threads Sharing a Single Connection</A>.
+<P><HR>[ <A HREF="develop83.html">Previous Page</A><br><A HREF="develop85.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop85.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop85.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,30 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Working with Derby SQLExceptions in an Application</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="working with, SQLExceptions">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<HR><H1 NAME="HDRSII-CONCEPTS-24927">Working with Derby SQLExceptions in an Application</H1>
+<A NAME="IDX715"></A>
+<P>JDBC generates exceptions of the type
+<I>java.sql.SQLException</I>. To see the exceptions
+generated by Derby, retrieve and process the
+<TT><I>SQLExceptions</I></TT> in a catch block.
+<P><HR>[ <A HREF="develop84.html">Previous Page</A><br><A HREF="develop86.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop86.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop86.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,73 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Information Provided in SQLExceptions</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="chaining of, SQLExceptions, Processing SQLExceptions, SQLWarnings">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRCONCEPTS844813">Information Provided in SQLExceptions</H1>
+<P>Derby provides the message, <I>SQLState</I> values, and error
+codes. Use the <TT><I>getSQLState</I></TT> and
+<TT><I>getMessage</I></TT> methods to view the
+<TT><I>SQLState</I></TT> and error messages. Use
+<TT><I>getErrorCode</I></TT> to see the error code. The error
+code defines the severity of the error and is not unique to each
+exception. The severity levels are described
+in<TT><I>org.apache.derby.types.ExceptionSeverity</I></TT>.
+<P>
+<A NAME="IDX716"></A>
+In addition, a single error can generate more than one
+<I>SQLException</I>. Use a loop and the
+<TT><I>getNextException</I></TT> method to process all
+<TT><I>SQLExceptions</I></TT> in the chain. In many cases, the
+second exception in the chain is the pertinent one.
+<P>
+<A NAME="IDX717"></A>
+The following is an example:
+<PRE>catch (Throwable e) {
+    System.out.println("exception thrown:");
+    errorPrint(e);
+}
+static void errorPrint(Throwable e) {
+    if (e instanceof SQLException)&nbsp;
+        SQLExceptionPrint((SQLException)e);
+    else
+        System.out.println("A non-SQL error: " + e.toString());
+}
+static void SQLExceptionPrint(SQLException sqle) {
+    while (sqle != null) {
+        System.out.println("\n---SQLException Caught---\n");
+        System.out.println("SQLState:   " + (sqle).getSQLState());
+        System.out.println("Severity: " + (sqle).getErrorCode());
+        System.out.println("Message:  " + (sqle).getMessage());&nbsp;
+        sqle.printStackTrace();&nbsp;
+        sqle = sqle.getNextException();
+    }
+}
+</PRE>
+<P>See also &quot;Derby Exception Messages and SQL States&quot;, in the
+<CITE>Derby Reference Manual</CITE>.
+<P>
+<A NAME="IDX718"></A>
+Applications should also check for and process
+<I>java.sql.SQLWarnings</I>, which are processed in a
+similar way. Derby issues an <TT><I>SQLWarning</I></TT> if
+the <TT><I>create=true</I></TT> attribute is specified and the database
+already exists.<TT><B></B></TT>
+<P><HR>[ <A HREF="develop85.html">Previous Page</A><br><A HREF="develop87.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop87.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop87.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,60 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Using Derby as a J2EE Resource Manager</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="Derby as in J2EE system, Resource manager">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<HR><H1 NAME="HDRSII-RESMAN-19524">Using Derby as a J2EE Resource Manager</H1>
+<P>J2EE, or the Java 2 Platform, Enterprise Edition, is a standard for
+development of enterprise applications; one example is Enterprise Java
+Beans (EJBs) with distributed capabilities.
+<P>
+<A NAME="IDX719"></A>
+Derby is a J2EE-conformant component in a distributed J2EE system.
+As such, it is one part of a larger system that includes, among other things,
+a JNDI server, a connection pool module, a transaction manager, a resource
+manager, and user applications. Derby also supports the JTA API,
+which is not a current J2EE requirement, but this functionality provides
+another piece of the same system. Within this system, Derby can
+serve as the resource manager.
+<P>For more information on J2EE and how to work in this environment, see the
+J2EE specification available at
+<VAR>http://java.sun.com/j2ee/docs.html</VAR>.
+<DL><DT><B>Note:</B></DT><DD>This chapter does not show you how to use Derby as a Resource
+Manager. Instead, it provides details specific to Derby that are
+not covered in the specification. This information is useful to
+programmers developing other modules in a distributed J2EE system, not to
+end-user application developers.
+</DD></DL>
+<P>In order to qualify as a resource manager in a J2EE system, J2EE requires
+these basic areas of support. These three areas of support involve
+implementation of APIS and are described in &quot;J2EE Compliance: Java
+Transaction API and javax.sql Extensions&quot; in the <CITE>
+Derby Reference Manual</CITE>.
+<P>This chapter describes the Derby classes that implement the APIs and
+provides some implementation-specific details.
+<DL><DT><B>Note:</B></DT><DD>All of the classes described in this chapter require a Java<SUP>(TM)</SUP> 2 Platform,
+Standard Edition, v 1.2 (J2SE) or higher environment.
+</DD></DL>
+<UL>
+<LI><A HREF="develop88.html#HDRSII-RESMAN-79556">The Classes Pertaining to Resource Managers</A>
+</LI><LI><A HREF="develop89.html#HDRSII-RESMAN-78715">How to Use Them</A>
+</LI></UL>
+<P><HR>[ <A HREF="develop86.html">Previous Page</A><br><A HREF="develop88.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop88.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop88.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,45 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>The Classes Pertaining to Resource Managers</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="org.apache.derby.jdbc.EmbeddedDataSource, org.apache.derby.jdbc.EmbeddedConnectionPoolDataSource, org.apache.derby.jdbc.EmbeddedXADataSource">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<HR><H1 NAME="HDRSII-RESMAN-79556">The Classes Pertaining to Resource Managers</H1>
+<P>See the javadoc for each class for more information.
+<UL>
+<LI><I>org.apache.derby.jdbc.EmbeddedDataSource</I><I>
+<A NAME="IDX720"></A>
+</I> 
+<P>Implements <I>javax.sql.DataSource</I> interface, which a
+JNDI server can reference. Typically this is the object that you work
+with as a <TT><I>DataSource</I></TT>.
+</LI><LI><I>org.apache.derby.jdbc.EmbeddedConnectionPoolDataSource</I>
+<A NAME="IDX721"></A>
+<P>
+<P>Implements
+<I>javax.sql.ConnectionPoolDataSource</I>. A factory
+for <TT><I>PooledConnection</I></TT> objects.
+</LI><LI><I>org.apache.derby.jdbc.EmbeddedXADataSource</I><I>
+<A NAME="IDX722"></A>
+</I> 
+<P>Derby's implementation of a
+<I>javax.sql.XADataSource</I>.
+</LI></UL>
+<P><HR>[ <A HREF="develop87.html">Previous Page</A><br><A HREF="develop89.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop89.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop89.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,28 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>How to Use Them</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<HR><H1 NAME="HDRSII-RESMAN-78715">How to Use Them</H1>
+<UL>
+<LI><A HREF="develop90.html#HDRSII-RESMAN-89722">Getting a DataSource</A>
+</LI><LI><A HREF="develop91.html#HDRSII-RESMAN-92946">Shutting Down or Creating a Database</A>
+</LI></UL>
+<P><HR>[ <A HREF="develop88.html">Previous Page</A><br><A HREF="develop90.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop90.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop90.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,72 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Getting a DataSource</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-RESMAN-89722">Getting a DataSource</H1>
+<P>Normally, you can simply work with the interfaces for
+<I>javax.sql.DataSource</I>,
+<TT><I>javax.sql.ConnectionPoolDataSource</I></TT>, and
+<TT><I>javax.sql.XADataSource</I></TT>, as shown in the
+following examples.
+<PRE>import org.apache.derby.jdbc.EmbeddedConnectionPoolDataSource;
+import org.apache.derby.jdbc.EmbeddedDataSource;
+import org.apache.derby.jdbc.EmbeddedXADataSource;&nbsp;
+ 
+javax.sql.ConnectionPoolDataSource cpds = new DerbyConnectionPoolDataSource();&nbsp;
+javax.sql.DataSource ds = new DerbyDataSource();&nbsp;
+javax.sql.XADataSource xads = new DerbyXADataSource();
+</PRE>
+<P>Derby provides six properties for a <I>DataSource</I>.
+These properties are in
+<I>org.apache.derby.jdbc.EmbeddedDataSource</I>.
+They are:
+<UL>
+<LI><I>DatabaseName</I> 
+<P>This mandatory property must be set. It identifies which database to
+access. If a database named wombat located at /local1/db/wombat is to
+be accessed, then one should call
+<I>setDatabaseName</I>(&quot;/local1/db/wombat&quot;) on the data source
+object.
+</LI><LI><I>CreateDatabase</I> 
+<P>Optional. Sets a property to create a database the next time the
+<I>XADataSource.getXAConection()</I> method is called. The
+string <I>createString</I> is always &quot;create&quot; (or possibly
+null). (Use the method <TT><I>setDatabaseName()</I></TT> to
+define the name of the database.)
+</LI><LI><I>ShutdownDatabase</I> 
+<P>Optional. Sets a property to shut down a database. The string
+<I>shutDownString</I> is always &quot;shutdown&quot; (or possibly
+null). Shuts down the database the next time
+<TT><I>XADataSource.getXAConnection().getConnection()</I></TT>
+method is called.
+</LI><LI><I>DataSourceName</I> 
+<P>Optional. Name for ConnectionPooledDataSource or
+XADataSource. Not used by the data source object. Used for
+informational purpose only.
+</LI><LI><I>Description</I> 
+<P>Optional. Description of the data source. Not used by the
+data source object. Used for informational purpose only.
+</LI><LI><I>connectionAttributes</I> 
+<P>Optional. Connection attributes specific to Derby. See
+the <CITE>Derby Reference Manual</CITE> for a more information about
+the attributes.
+</LI></UL>
+<P><HR>[ <A HREF="develop89.html">Previous Page</A><br><A HREF="develop91.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop91.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop91.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,49 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Shutting Down or Creating a Database</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-RESMAN-92946">Shutting Down or Creating a Database</H1>
+<P>If you need to shut down or create a database, it is easiest just to work
+with the Derby-specific implementations of interfaces, as shown in the
+following examples.
+<PRE>javax.sql.XADataSource xads = makeXADataSource(mydb, true);
+ 
+ 
+<B>// example of setting property directory using&nbsp;</B>
+// <B>Derby 's </B>XADataSource object
+import org.apache.derby.jdbc.EmbeddedXADataSource;
+import javax.sql.XADataSource;
+<B>// dbname is the database name
+// if create is true, create the database if not already created</B>
+XADataSource makeXADataSource (String dbname, boolean create)&nbsp;
+{
+    DerbyXADataSource xads = new DerbyXADataSource();
+<B>    // use Derby 's setDatabaseName call</B>
+    xads.setDatabaseName(dbname);
+    if (create)
+        xads.setCreateDatabase("create");
+    return xads;
+}
+</PRE>
+<P>Setting the property does not create or shut down the database. The
+database is not actually created or shut down until the next connection
+request.
+<P><HR>[ <A HREF="develop90.html">Previous Page</A><br><A HREF="develop92.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop92.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop92.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,35 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Derby and Security</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<HR><H1 NAME="Header_161">Derby and Security</H1>
+<UL>
+<LI><A HREF="develop93.html#HDRSII-CSECUR-33663">Security Overview</A>
+</LI><LI><A HREF="develop96.html#HDRSII-CSECUR-42374">Working with User Authentication</A>
+</LI><LI><A HREF="develop104.html#HDRSII-CSECUR-37241">Users and Authorization Identifiers</A>
+</LI><LI><A HREF="develop108.html#HDRSII-CSECUR-36595">User Authorization</A>
+</LI><LI><A HREF="develop112.html#HDRSII-CSECUR-24366">Encrypting Databases on Disk</A>
+</LI><LI><A HREF="develop116.html#HDRSII-CSECUR-90988">Signed Jar Files</A>
+</LI><LI><A HREF="develop117.html#HDRSII-CSECUR-10983">Notes on the Derby Security Features</A>
+</LI><LI><A HREF="develop118.html#HDRSII-CSECUR-51876">User Authentication and Authorization Examples</A>
+</LI><LI><A HREF="develop121.html#HDRBABEJDFJ">Running Derby under a security manager</A>
+</LI></UL>
+<P><HR>[ <A HREF="develop91.html">Previous Page</A><br><A HREF="develop93.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop93.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop93.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,26 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Security Overview</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="Security features">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<HR><H1 NAME="HDRSII-CSECUR-33663">Security Overview</H1>
+<A NAME="IDX723"></A>
+<P><HR>[ <A HREF="develop92.html">Previous Page</A><br><A HREF="develop94.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop94.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop94.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,54 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Features</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="definition, User authentication, Authentication, User authorization, Disk encryption, Encrypting databases">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRCSECUR862382">Features</H1>
+<P>Derby can be deployed in a number of ways and in a number of different
+environments. The security needs of the Derby system are also
+diverse. Derby supplies or supports the following optional
+security mechanisms:
+<UL>
+<LI><I>User authentication
+<A NAME="IDX724"></A>
+<A NAME="IDX725"></A>
+</I> 
+<P>Derby verifies user names and passwords before permitting them access
+to the Derby system. See <A HREF="develop96.html#HDRSII-CSECUR-42374">Working with User Authentication</A>.
+</LI><LI><I>User authorization
+<A NAME="IDX726"></A>
+</I> 
+<P>A means of granting specific users permission to read a database or to
+write to a database. See <A HREF="develop108.html#HDRSII-CSECUR-36595">User Authorization</A>.
+</LI><LI><I>Disk encryption
+<A NAME="IDX727"></A>
+<A NAME="IDX728"></A>
+</I> 
+<P>A means of encrypting Derby data stored on disk. See <A HREF="develop112.html#HDRSII-CSECUR-24366">Encrypting Databases on Disk</A>.
+</LI><LI><I>Validation of Certificate for Signed Jar Files</I> 
+<P>In a Java 2 environment, Derby validates certificates for classes
+loaded from signed jar files. See <A HREF="develop116.html#HDRSII-CSECUR-90988">Signed Jar Files</A>. 
+<P><B><A NAME="Figure_10">Figure 10. Some of the Derby security mechanisms at work in a client/server environment</A></B><BR>
+<BR><IMG SRC="images/security.gif" ALT="Some of the Derby security mechanisms at work in a client/server environment."><BR>
+<P><B><A NAME="Figure_11">Figure 11. Another Derby security mechanism, disk encryption, protects data when the recipient might not know how to protect data. It is useful for databases deployed in an embedded environment.</A></B><BR>
+<BR><IMG SRC="images/security2.gif" ALT="The disk encryption security mechanism."><BR>
+</LI></UL>
+<P><HR>[ <A HREF="develop93.html">Previous Page</A><br><A HREF="develop95.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop95.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop95.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,102 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Configuring Security for Your Environment</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="configuring, Security">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-CSECUR-12392">Configuring Security for Your Environment</H1>
+<A NAME="IDX729"></A>
+<P>In most cases, you enable Derby's security features through the
+use of properties. It is important to understand the best way of
+setting properties for your environment.
+<UL>
+<LI><A HREF="#HDRSII-CSECUR-82556">Configuring Security in a Client/Server Environment</A>
+</LI><LI><A HREF="#HDRSII-CSECUR-81850">Configuring Security in an Embedded Environment</A>
+</LI></UL>
+<P><H1><A NAME="HDRSII-CSECUR-82556">Configuring Security in a Client/Server Environment</H1>
+<P>This discussion assumes a system with multiple databases and some
+administrative resources. For systems that have a single database and
+for which there are no administrative resources, follow the instructions in <A HREF="#HDRSII-CSECUR-81850">Configuring Security in an Embedded Environment</A>.
+<OL TYPE=1>
+<LI>Configure security features as system properties. 
+<P>See &quot;System-Wide Properties&quot; in <CITE>Tuning 
+Derby</CITE>.
+<P>Provide administrative-level protection for the
+<I>derby.properties</I> file and Derby databases.
+For example, you can protect these files and directories with operating system
+permissions and firewalls.
+</LI><LI>Turn on user authentication for your system. 
+<P>All users must provide valid user IDs and passwords to access the
+Derby system. See <A HREF="develop96.html#HDRSII-CSECUR-42374">Working with User Authentication</A> for information.
+<P>If you are using Derby's built-in users, configure users for the
+system in the <I>derby.properties</I> file. Provide the
+protection for this file.
+</LI><LI>Configure user authorization for sensitive databases in your
+system. 
+<P>Only designated users will be able to access sensitive databases.
+You typically configure user authorization with database-level
+properties. See <A HREF="develop108.html#HDRSII-CSECUR-36595">User Authorization</A> for information. It is also possible to
+configure user authorization with system-level properties. This is
+useful when you are developing systems or when all databases have the same
+level of sensitivity.
+</LI></OL>
+<P><H1><A NAME="HDRSII-CSECUR-81850">Configuring Security in an Embedded Environment</H1>
+<P>In an embedded environment, typically there is only one database per system
+and there are no administrative resources to protect databases.
+<OL TYPE=1>
+<LI>Encrypt the database when you create it.
+</LI><LI>Configure all security features as database-level properties. 
+<P>When you do this, these properties are stored in the database (which is
+encrypted). See &quot;Database-Wide Properties&quot; in <CITE>Tuning 
+Derby</CITE>.
+</LI><LI>Turn on protection for database-level properties so that they cannot be
+overridden by system properties. 
+<P>Do this by setting the
+<I>derby.database.propertiesOnly</I> property to
+true.
+</LI><LI>To prevent unauthorized users from accessing databases once they are
+booted, turn on user authentication for the database and configure user
+authorization for the database. 
+<P>See <A HREF="develop96.html#HDRSII-CSECUR-42374">Working with User Authentication</A> for information. 
+<P>See <A HREF="develop108.html#HDRSII-CSECUR-36595">User Authorization</A> for information.
+</LI><LI>If you are using Derby's built-in users, configure each user as a
+database-level property so that user names and passwords can be
+encrypted.
+</LI></OL><TABLE BORDER WIDTH="100%"><TR><TH ALIGN="LEFT">Caveat for Configuring Security</TH><TR><TD>
+<P>Derby does not come with a built-in superuser. For that reason,
+be careful when configuring Derby for user authentication and user
+authorization.
+<OL TYPE=1>
+<LI>When first working with security, work with system-level properties only
+so that you can easily override them if you make a mistake.
+</LI><LI>Be sure to create at least one valid user, and grant that user full
+(read-write) access. For example, you might always want to create a
+user called <I>sa</I> with the password <I>derby</I> while you
+are developing.
+</LI><LI>Test the authentication system while it is still configured at the system
+level. Be absolutely certain that you have configured the system
+correctly before setting the properties as database-level properties.
+</LI><LI>Before disabling system-level properties (by setting
+<I>derby.database.propertiesOnly</I> to true), test
+that at least one database-level read-write user (such as <I>sa</I>) is
+valid. If you do not have at least one valid user that the system can
+authenticate, you will not be able to access your database.
+</LI></OL></TD></TR></TABLE>
+<P><HR>[ <A HREF="develop94.html">Previous Page</A><br><A HREF="develop96.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop96.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop96.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,34 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Working with User Authentication</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="User authentication, Authentication">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<HR><H1 NAME="HDRSII-CSECUR-42374">Working with User Authentication</H1>
+<A NAME="IDX730"></A>
+<A NAME="IDX731"></A>
+<UL>
+<LI><A HREF="develop97.html#HDRSII-CSECUR-30032">Overview</A>
+</LI><LI><A HREF="develop98.html#HDRSII-CSECUR-36127">Enabling User Authentication</A>
+</LI><LI><A HREF="develop99.html#HDRSII-CSECUR-37817">Defining Users</A>
+</LI><LI><A HREF="develop102.html#HDRSII-CSECUR-32557">Properties Summary</A>
+</LI><LI><A HREF="develop103.html#HDRSII-CSECUR-79358">Programming Applications for Derby User Authentication</A>
+</LI></UL>
+<P><HR>[ <A HREF="develop95.html">Previous Page</A><br><A HREF="develop97.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop97.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop97.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,56 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Overview</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-CSECUR-30032">Overview</H1>
+<P>Derby provides support for user authentication. <I>User
+authentication</I> means that Derby authenticates a user's name and
+password before allowing that user access to the system.
+<P>When user authentication is enabled (which it is not by default), the user
+requesting a connection must provide a valid name and password, which
+Derby verifies against the repository of users defined for the
+system. Once Derby authenticates the user, it grants the user
+access to the Derby system but not necessarily access to the database
+made in the connection request. In the Derby system, access to a
+database is determined by <I>user authorization</I>. For
+information, see <A HREF="develop108.html#HDRSII-CSECUR-36595">User Authorization</A>.
+<P>Derby allows you to provide a repository of users in a number of
+different ways. For example, you can hook Derby up to an external
+directory service elsewhere in your enterprise, create your own, use
+Derby's simple mechanism for creating a built-in repository of
+users.
+<P>You can define a repository of users for a particular database or for an
+entire system, depending on whether you use system-wide or database-wide
+properties. See <A HREF="develop95.html#HDRSII-CSECUR-12392">Configuring Security for Your Environment</A> for more information.
+<P>When Derby user authentication is enabled and Derby uses an
+external directory service, the architecture looks something like that shown
+in the Figure below:
+<P><B><A NAME="FIGSII-CSECUR-32704">Figure 12. Derby user authentication using an external service. The application can be a single-user application with an embedded Derby engine or a multi-user application server.</A></B><BR>
+<BR><IMG SRC="images/authentic.gif" ALT="Derby user authentication using an external service."><BR>
+<P>Derby always runs embedded in another Java application, whether that
+application is a single-user application or a multiple-user application server
+or connectivity framework. A database can be accessed by only one JVM
+at a time, so it is possible to deploy a system in which the application in
+which Derby is embedded, not Derby, handles the user authentication
+by connecting to an external directory service.
+<P><B><A NAME="Figure_13">Figure 13. The application provides the user authentication using an external service. The application can be a single-user application with an embedded Derby engine or a multi-user application server.</A></B><BR>
+<BR><IMG SRC="images/appauth.gif" ALT="The application user authentication as an external service."><BR>
+<P><HR>[ <A HREF="develop96.html">Previous Page</A><br><A HREF="develop98.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop98.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop98.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,40 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Enabling User Authentication</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="enabling, User authentication">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-CSECUR-36127">Enabling User Authentication</H1>
+<A NAME="IDX732"></A>
+<P>To enable user authentication, set the
+<I>derby.connection.requireAuthentication</I> property
+to true. Otherwise, Derby does not require a user name and
+password. You can set this property as a system-wide property or as a
+database-wide property.
+<P>For a multi-user product, you would typically set it for the system in the
+<I>derby.properties</I> file for your server, since it is in a
+trusted environment.
+<DL><DT><B>Note:</B></DT><DD>If you start a Derby system with user authentication enabled but without
+defining at least one user, you will not be able to shut down the system
+gracefully. When Derby is running in a connectivity server and
+user authentication is turned on, stopping the server requires a user name and
+password. You will need to alter shutdown scripts accordingly.
+</DD></DL>
+<P><HR>[ <A HREF="develop97.html">Previous Page</A><br><A HREF="develop99.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop99.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/develop/develop99.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,46 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Defining Users</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META NAME="KEYWORDS" CONTENT="defining for a system, Users, specifying, Authentication provider">
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Thu, 15 Jul 2004 13:54:02">
+<META HTTP-EQUIV="review" CONTENT="Fri, 15 Jul 2005 13:54:02">
+<META HTTP-EQUIV="expires" CONTENT="Sat, 15 Jul 2006 13:54:02">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<P><H1 NAME="HDRSII-CSECUR-37817">Defining Users</H1>
+<A NAME="IDX733"></A>
+<A NAME="IDX734"></A>
+<P>Derby provides several ways to define the repository of users and
+passwords. To specify which of these services to use with your
+Derby system, set the property
+<I>derby.authentication.provider</I> to the appropriate
+value as discussed in the appropriate section listed below.
+<P>Setting the property as a system-wide property creates system-wide
+users. Setting the property as a database-wide property creates users
+for a single database only.
+<UL>
+<LI><A HREF="develop100.html#HDRSII-CSECUR-38522">External Directory Service</A>: <A HREF="develop100.html#HDRSII-CSECUR-41285">LDAP Directory Service</A>. This includes Windows NT domain
+user authentication through the Netscape NT Synchronization Service.
+</LI><LI><A HREF="develop100.html#HDRSII-CSECUR-21561">User-Defined Class</A>
+</LI><LI><A HREF="develop101.html#HDRSII-CSECUR-21547">Built-in Derby Users</A>
+</LI></UL>
+<DL><DT><B>Note:</B></DT><DD>Shutting down the Derby system (for example, using the
+<I>shutdown=true</I> form of the connection URL without specifying a
+particular database) when user authentication is turned on requires that you
+define at least one user as a system-wide user.
+</DD></DL>
+<P><HR>[ <A HREF="develop98.html">Previous Page</A><br><A HREF="develop100.html">Next Page</A><br><A HREF="develop02.html#ToC">Table of Contents</A><br><A HREF="develop157.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/getstart/gspr.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/getstart/gspr.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,26 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Getting Started with Derby</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Wed, 14 Jul 2004 10:49:01">
+<META HTTP-EQUIV="review" CONTENT="Thu, 14 Jul 2005 10:49:01">
+<META HTTP-EQUIV="expires" CONTENT="Fri, 14 Jul 2006 10:49:01">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+<H1>Getting Started with Derby</H1>
+<BR>
+<P><B>First Edition (August 2004)</B>
+<P><B>(C) Copyright International Business Machines Corporation 1997, 2004. All rights reserved.</B> <BR>U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
+<P>
+<P><HR>[ <A HREF="gspr02.html">Next Page</A><br><A HREF="gspr02.html#ToC">Table of Contents</A><br><A HREF="gspr40.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/getstart/gspr02.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/getstart/gspr02.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,66 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Contents</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Wed, 14 Jul 2004 10:49:01">
+<META HTTP-EQUIV="review" CONTENT="Thu, 14 Jul 2005 10:49:01">
+<META HTTP-EQUIV="expires" CONTENT="Fri, 14 Jul 2006 10:49:01">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+<H1>Getting Started with Derby</H1>
+<BR>
+<HR><H1><A NAME="ToC">Contents</A></H1>
+<P><A HREF="gspr03.html#HDRSII-GSINTRO-19524">Introducing Derby</A><BR>
+<MENU>
+<LI><A HREF="gspr04.html#HDRSII-GSINTRO-35889">Deployment options</A>
+<LI><A HREF="gspr05.html#HDRSII-GSINTRO-SYSTEMREQUIREMENTS">System requirements</A>
+</MENU>
+<P><A HREF="gspr06.html#HDRSII-GS-19524">Installing and working with Derby</A><BR>
+<MENU>
+<LI><A HREF="gspr08.html#HDRSII-GS-INSTALLINGDB2CSCAPE">Installing Derby</A>
+<LI><A HREF="gspr11.html#HDRSII-GS-SETUPJAVAENVIR">Setting up your Java environment</A>
+<LI><A HREF="gspr16.html#HDRSII-GS-36360">Set the DERBY_INSTALL environment variable</A>
+<MENU>
+<LI><A HREF="gspr16.html#HDRSII-GS-26250">Set the class path</A>
+</MENU></MENU>
+<P><A HREF="gspr21.html#HDRSII-GSQUICK-19524">Quick start for experienced JDBC users</A><BR>
+<MENU>
+<LI><A HREF="gspr22.html#HDRSII-GSQUICK-70629">Environment quick start</A>
+<MENU>
+<LI><A HREF="gspr23.html#HDRSII-GSQUICK-35643">Embedded environment</A>
+<LI><A HREF="gspr24.html#HDRSII-GSQUICK-13780">Client/server environment</A>
+</MENU>
+<LI><A HREF="gspr25.html#HDRSII-GSQUICK-67441">Libraries and class path</A>
+<LI><A HREF="gspr26.html#HDRSII-GSQUICK-35368">Driver</A>
+<LI><A HREF="gspr27.html#HDRSII-GSQUICK-30197">Database connection URL</A>
+</MENU>
+<P><A HREF="gspr28.html#HDRSII-DOCS-14707">The Derby documents</A><BR>
+<MENU>
+<LI><A HREF="gspr29.html#HDRSII-DOCS-17307">The library</A>
+</MENU>
+<P><A HREF="gspr30.html#HDRSII-DOCS-37966">Documentation conventions</A><BR>
+<MENU>
+<LI><A HREF="gspr31.html#HDRSII-DOCS-99397">Terminology</A>
+<LI><A HREF="gspr32.html#HDRSII-DOCS-10012">Syntax</A>
+<LI><A HREF="gspr33.html#HDRSII-DOCS-18277">Typography</A>
+</MENU>
+<P><A HREF="gspr34.html#HDRSII-GSLIBS-19524">Appendix A. Derby Libraries: Complete Reference</A><BR>
+<MENU>
+<LI><A HREF="gspr35.html#HDRSII-GSLIBS-46043">Libraries Provided by Derby</A>
+<LI><A HREF="gspr36.html#HDRSII-GSLIBS-56653">Libraries Not Provided by Derby</A>
+</MENU>
+<P><A HREF="gspr39.html#HDRTRADEM">Trademarks</A>
+<P><A HREF="gspr40.html#HDRINDEX_START">Index</A><BR>
+<P>
+<P><HR>[ <A HREF="gspr.html">Previous Page</A><br><A HREF="gspr03.html">Next Page</A><br><A HREF="#ToC">Table of Contents</A><br><A HREF="gspr40.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/getstart/gspr03.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/getstart/gspr03.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,30 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Introducing Derby</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Wed, 14 Jul 2004 10:49:01">
+<META HTTP-EQUIV="review" CONTENT="Thu, 14 Jul 2005 10:49:01">
+<META HTTP-EQUIV="expires" CONTENT="Fri, 14 Jul 2006 10:49:01">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<HR><H1 NAME="HDRSII-GSINTRO-19524">Introducing Derby</H1>
+<P>Welcome to Derby! Derby is a Java- and SQL-based relational
+database management system (RDBMS). This chapter describes the
+Derby products. 
+<UL>
+<LI><A HREF="gspr04.html#HDRSII-GSINTRO-35889">Deployment options</A>
+</LI><LI><A HREF="gspr05.html#HDRSII-GSINTRO-SYSTEMREQUIREMENTS">System requirements</A>
+</LI></UL>
+<P><HR>[ <A HREF="gspr02.html">Previous Page</A><br><A HREF="gspr04.html">Next Page</A><br><A HREF="gspr02.html#ToC">Table of Contents</A><br><A HREF="gspr40.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/getstart/gspr04.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/getstart/gspr04.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,32 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Deployment options</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Wed, 14 Jul 2004 10:49:01">
+<META HTTP-EQUIV="review" CONTENT="Thu, 14 Jul 2005 10:49:01">
+<META HTTP-EQUIV="expires" CONTENT="Fri, 14 Jul 2006 10:49:01">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+<H1 NAME="HDRSII-GSINTRO-35889">Deployment options</H1>
+<P>Derby can be deployed in a number of different ways: 
+<UL>
+<LI>Embedded in a single-user Java application. Derby can be
+practically invisible to the user, since it requires no administration and
+runs in the same Java virtual machine (JVM) as the application.
+</LI><LI>Embedded in a multi-user application such as a Web server, an application
+server, or a shared development environment.
+</LI><LI>Embedded in a server framework. You can use either the Network
+Server or a server of your own choice.
+</LI></UL>
+<P><HR>[ <A HREF="gspr03.html">Previous Page</A><br><A HREF="gspr05.html">Next Page</A><br><A HREF="gspr02.html#ToC">Table of Contents</A><br><A HREF="gspr40.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/getstart/gspr05.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/getstart/gspr05.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,25 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>System requirements</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Wed, 14 Jul 2004 10:49:01">
+<META HTTP-EQUIV="review" CONTENT="Thu, 14 Jul 2005 10:49:01">
+<META HTTP-EQUIV="expires" CONTENT="Fri, 14 Jul 2006 10:49:01">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<HR><H1 NAME="HDRSII-GSINTRO-SYSTEMREQUIREMENTS">System requirements</H1>
+<P>Derby is a database engine written completely in Java; it will
+run in any certified Java Virtual Machine (JVM).
+<P><HR>[ <A HREF="gspr04.html">Previous Page</A><br><A HREF="gspr06.html">Next Page</A><br><A HREF="gspr02.html#ToC">Table of Contents</A><br><A HREF="gspr40.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/getstart/gspr06.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/getstart/gspr06.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,28 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Installing and working with Derby</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Wed, 14 Jul 2004 10:49:01">
+<META HTTP-EQUIV="review" CONTENT="Thu, 14 Jul 2005 10:49:01">
+<META HTTP-EQUIV="expires" CONTENT="Fri, 14 Jul 2006 10:49:01">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<HR><H1 NAME="HDRSII-GS-19524">Installing and working with Derby</H1>
+<P><A NAME="SPTSII-GS-29008"></A>If you are new to Derby and
+JDBC programming, the following topics will help you begin using the
+product. If you are already an experienced JDBC programmer, see <A HREF="gspr21.html#HDRSII-GSQUICK-19524">"Quick start for experienced JDBC users"</A>.
+<P><A HREF="gspr08.html#HDRSII-GS-INSTALLINGDB2CSCAPE">Installing Derby</A>
+<P><A HREF="gspr11.html#HDRSII-GS-SETUPJAVAENVIR">Setting up your Java environment</A>
+<P><HR>[ <A HREF="gspr05.html">Previous Page</A><br><A HREF="gspr08.html">Next Page</A><br><A HREF="gspr02.html#ToC">Table of Contents</A><br><A HREF="gspr40.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/getstart/gspr08.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/getstart/gspr08.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,32 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
+<HTML><HEAD>
+<TITLE>Installing Derby</TITLE>
+<!-- Begin Header Records  ========================================== -->
+
+<!-- (C) Copyright IBM Corporation 1997, 2004                              -->
+<!-- All rights reserved. Licensed Materials Property of IBM          -->
+<!-- US Government Users Restricted Rights -                          -->
+<!-- Use, duplication or disclosure restricted by                     -->
+<!-- GSA ADP Schedule Contract with IBM Corp.                         -->
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
+<META HTTP-EQUIV="updated" CONTENT="Wed, 14 Jul 2004 10:49:01">
+<META HTTP-EQUIV="review" CONTENT="Thu, 14 Jul 2005 10:49:01">
+<META HTTP-EQUIV="expires" CONTENT="Fri, 14 Jul 2006 10:49:01">
+</HEAD><BODY>
+<!-- End Header Records  ============================================ -->
+<A NAME="Top_Of_Page"></A>
+
+<HR><H1 NAME="HDRSII-GS-INSTALLINGDB2CSCAPE">Installing Derby</H1>
+<P>These instructions assume you downloaded the zip or tar archive from the
+Derby web site.
+<p>Extract the file.
+The contents of the distribution will be extracted into a subdirectory named
+apache-derby-10.0 and it will contain two subdirectories:
+<ul>
+   <li> The lib subdirectory contains the Derby jar files.</li>
+   <li> The javadoc subdirectory contains the api documentation that was
+        generated from source code comments.</li>
+</ul>
+<P><HR>[ <A HREF="gspr06.html">Previous Page</A><br><A HREF="gspr11.html">Next Page</A><br><A HREF="gspr02.html#ToC">Table of Contents</A><br><A HREF="gspr40.html#HDRINDEX_START">Index</A> ] 
+<A NAME="Bot_Of_Page"></A>
+</BODY></HTML>

Added: incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/getstart/gspr11.ihtml
==============================================================================
--- (empty file)
+++ incubator/derby/site/trunk/src/documentation/content/xdocs/manuals/getstart/gspr11.ihtml	Fri Aug 20 15:29:26 2004
@@ -0,0 +1,48 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN"