24051827 3145740 24084594 24117747 24117748 24117749 24117750 24117751 24117752 24117753 24117754 24117755 24117756 24117757 24117758 11 2013-12-04 09:21:43.933 2013-12-04 10:56:57.167 24051828 24051829 24051833 24051834 24051836 24051837 24051839 24051842 24051844 24051846 18580035 8355883 8355883 3145740 18645542 19137221 19137222 5 2012-03-05 15:47:44.387 2012-03-27 11:03:28.320 19038275 19038298 19038300 19038302 18251845 17236193 8355883 17236193 3145740 18284613 3 2011-07-25 16:06:45.533 2011-07-25 16:43:49.810 18251850 18251853 19041365 8355883 8355883 3145740 19074051 2 2012-11-29 08:17:40.267 2012-11-29 08:17:59.683 19041366 3114599 8355883 8355883 3145740 3180066 10461293 10461294 10461295 10461296 10461297 10461298 10461299 10461300 10461301 10461302 10461303 10461304 10461305 10461306 3277230 3604491 3604494 3604495 3604499 3604500 3604502 3604504 3604583 3604629 3604630 3604648 3604697 3604698 3604699 4849678 5734410 34 2008-04-09 12:55:07.147 2009-09-24 14:59:26.387 3637532 3637554 3637590 3637591 3637592 3637593 3637594 3637595 3637596 3637597 3637598 3637599 3637600 3637858 3638026 5374732 5832826 5832916 5832919 6259008 7176199 8913088 8913091 8913093 8913118 9372015 9372262 10354804 10354807 10354810 10355548 10355551 10356300 19040151 8355883 8355883 3145740 19072868 2 2012-07-18 09:21:48.597 2012-07-18 09:26:08.850 19040165 19041368 8355883 8355883 3145740 19074054 19533446 19533447 19533448 11 2012-11-29 08:19:23.410 2013-01-08 14:00:32.057 19041370 19041372 19041543 19041545 19041547 19041548 19041550 19041551 19041552 19041589 19040153 8355883 8355883 3145740 19072869 2 2012-07-18 09:22:12.510 2012-07-18 09:26:37.663 19040166 19040155 8355883 8355883 3145740 19072870 2 2012-07-18 09:22:30.357 2012-07-18 09:27:04.180 19040167 3637534 8355883 8355883 3145740 3670289 18350272 3604578 3604579 3604589 5734402 31 2008-04-22 12:26:44.157 2011-08-03 14:50:14.523 3637536 3637538 3637540 3637541 3637543 3637545 3637547 3637548 3637550 3637561 3637563 3637565 3637571 3637573 3637575 3637577 3637579 3637581 3637586 3637737 3932172 5374029 5374030 6259028 6259147 7176224 9372164 9797783 9797784 10356263 18251898 3735591 9928714 19040157 8355883 8355883 3145740 19072871 2 2012-07-18 09:22:47.887 2012-07-18 09:27:39.447 19040168 19040159 8355883 8355883 3145740 19072872 2 2012-07-18 09:23:07.043 2012-07-18 09:28:05.443 19040169 25919541 25919539 8355883 25919539 3145740 25952309 9 2014-05-20 05:54:13.407 2014-05-20 10:54:56.077 25919543 25919545 25919547 25919549 25919551 25919553 25919555 25919556 19040161 8355883 8355883 3145740 19072873 3 2012-07-18 09:23:25.270 2012-07-18 09:33:50.693 19040170 19040174 8913090 8355883 8355883 3145740 8945851 13 2009-01-26 16:30:22.427 2009-09-24 14:32:26.397 8913092 8913094 8913096 8913116 9371778 9371780 9371806 9371808 9371810 9371895 9371899 10356272 9076752 28213255 8355883 8355883 3145740 28246023 7 2015-08-26 12:01:56.270 2015-08-28 15:58:46.773 28213258 28213291 28213293 28213296 28377089 28377091 25919539 8355883 25919541 8355883 3145740 25952307 26018343 1 2014-05-20 05:32:00.260 2014-05-20 05:32:00.260 3113965 8355883 8355883 3145740 3179450 15696758 15696759 15696760 15696761 15696762 15696763 15696764 15696765 15696766 15696767 42 2008-03-17 13:05:41.323 2010-12-17 07:24:41.037 3113966 3113968 3113970 3113972 3113974 3113976 3113980 3113982 3113983 3113985 3113987 3113989 3113999 3114001 3114003 3114004 3114016 3114018 3114020 3114023 3114025 3114027 3114029 3114031 3114033 3114035 3114037 3114038 3114040 3114042 3114044 3114046 3114048 3114050 3114052 3932230 3932232 3932234 3932235 3932237 15630529 3309644 3309645 3309646 3309647 4063240 4063241 5439489 4063242 8355883 814 2162995 3113965 3114599 3637286 3637534 3637859 3638030 5832828 5832918 5832921 6259010 6259430 7176201 7766027 8355849 8913090 8913120 9372328 9798110 9798359 9798378 9798398 9798677 10354800 10354826 10354882 10356280 10356284 10356302 10356471 10356476 10911981 10912225 10912300 11239606 11240274 11240296 11797064 12484688 13926566 15204448 15204478 15630363 15630373 15630488 15630643 15631042 15631339 15631413 15631441 15631445 16416807 16417009 16777373 16777460 17236193 18252222 18252474 18580035 19039049 19039359 19039402 19040044 19040151 19040153 19040155 19040157 19040159 19040161 19040970 19040991 19041349 19041365 19041368 19041520 24052291 25919539 27067271 28213255 3145740 8388650 28278789 28278790 28278791 28278792 28278793 28278794 28278795 28278796 28278797 28278798 28278799 28278800 28278801 28278802 28278803 28278804 28278805 28278806 28278807 28278808 28278809 28278810 28278811 28278812 28278813 28278814 28278815 28278816 28278817 28278818 28278819 28278820 28278821 28278822 28278823 28278824 28278825 28278826 28278827 28278828 28278829 28278830 28278831 28278832 28278833 28278834 28278835 28278836 28278837 28278838 28278839 28278840 28278841 28278842 28278843 28278844 28278845 28278846 28278847 28278848 28278849 28278850 28278851 28278852 28278853 28278854 28278855 28278856 28278857 28278858 28278859 28278860 28278861 28278862 28278863 28278864 28278865 28278866 28278867 28278868 28278869 28278870 28278871 28278872 28278873 28278874 28278875 28278876 28278877 28278878 28278879 28278880 28278881 28278882 28278883 28278884 28278885 28278886 28278887 28278888 28278889 28278890 28278891 28278892 28278893 28278894 28278895 28278896 28278897 28278898 28278899 28278900 28278901 28278902 28278903 28278904 28278905 28278906 28278907 28278908 28278909 28278910 28278911 28278912 28278913 28278914 28278915 28278916 28278917 28278918 28278919 28278920 28278921 28278922 28278923 28278924 28278925 28278926 28278927 28278928 28278929 28278930 28278931 28278932 28278933 28278934 28278935 28278936 28278937 28278938 28278939 28278940 28278941 28278942 28278943 28278944 28278945 28278946 28278947 28278948 28278949 28278950 28278951 28278952 28278953 28278954 28278955 28278956 28278957 28278958 28278959 28278960 28278961 28278962 28278963 28278964 28278965 28278966 28278967 28278968 28278969 28278970 28278971 28278972 28278973 28278974 28278975 28278976 28278977 28278978 28278979 28278980 28278981 28278982 28278983 28278984 28278985 28278986 28278987 28278988 28278989 28278990 28278991 28278992 28278993 28278994 28278995 28278996 28278997 238 2009-01-06 09:56:05.890 2015-08-26 12:03:05.403 8355887 8355888 8356022 8356024 8356025 8356027 8356028 8356030 8356032 8356034 8356035 8356036 8356037 8356048 8356049 9371670 9798339 9798340 9798342 9798343 9798344 9798346 9798350 9798352 9798354 9798355 9798357 9798361 9798362 9798365 9798367 9798369 9798371 9798374 9798376 9798396 9798640 9798644 9798660 9798661 9798665 9798667 9798675 10354783 10354789 10354791 10354793 10354795 10354797 10354798 10354814 10354816 10354817 10354820 10354821 10354822 10354824 10354829 10354831 10354833 10354835 10354880 10354895 10354900 10355704 10355888 10355892 10356235 10356266 10356268 10356270 10356275 10356278 10356282 10356287 10356292 10356294 10356297 10356299 10356467 10356469 10356472 10356474 10911971 10911973 10911974 10911976 10911979 10912223 10912298 10912299 10912302 10912303 11239604 11240294 11240322 11240342 11796611 11796612 11797062 12484686 13926630 13926710 14516249 14516250 15204426 15630370 15630371 15630374 15630486 15630533 15630639 15630641 15630652 15630653 15630660 15630662 15630674 15630675 15630677 15630679 15630681 15630683 15630685 15630688 15630690 15630692 15630694 15630696 15630698 15630700 15630701 15630702 15630704 15630705 15630706 15630708 15630710 15630712 15630713 15630715 15630716 15630717 15630719 15630721 15630723 15630725 15630726 15630728 15630730 15630732 15630733 15630735 15630737 15630739 15630741 15630742 15630744 15630745 15630746 15630747 15630748 15630749 15630750 15630751 15630915 15630917 15630919 15630942 15631040 15631243 15631274 15631290 15631292 15631294 15631296 15631298 15631306 15631307 15631309 15631311 15631411 15631439 15631443 16416804 16416805 16416974 16416976 16416978 16777371 16777436 16777438 16777440 16777442 16777444 16777446 16777448 16777450 16777452 16777454 16777456 16777458 17858672 18251934 18252472 18252589 18252590 18580033 19038477 19039048 19039399 19040042 19040143 19040145 19040147 19040149 19040163 19040172 19040173 19040176 19040177 19041146 19041161 19041164 19041166 19041169 19041170 19041347 19041363 19041518 21365730 24052289 25919536 27067266 27067267 27067269 28213257 3735561 3735563 3735570 9798677 8355883 8355883 3145740 9831416 9901210 2 2009-05-26 14:40:54.140 2009-05-26 14:42:26.207 9798679 24052291 8355883 8355883 3145740 24085051 3 2014-01-08 10:06:03.217 2014-01-08 10:08:12.920 24052292 24052293 24018989 24018990 16220240 15631042 8355883 15631042 3145740 16253006 4 2011-03-03 09:19:09.790 2011-03-03 11:16:02.953 16220242 16220244 16220246 10912227 10912225 8355883 10912225 3145740 10944982 15706807 15706808 15706809 15706810 15706811 15706812 15706813 15706814 15706815 15706816 15706817 15706818 15706819 25 2009-12-23 08:33:45.977 2011-01-10 11:02:05.533 10912229 10912231 10912233 10912235 10912237 10912239 10912241 10912242 13926603 13926605 13926607 13926609 13926612 13926614 13926615 13926617 13926619 13926620 13926621 13926623 13926632 13926648 15630868 15630870 14123034 8913120 8355883 8355883 3145740 8945880 3 2009-01-28 08:09:41.793 2009-09-24 14:19:48.627 8913122 10356264 9798684 5832921 8355883 5832921 3145740 9831423 2 2009-05-27 09:19:26.627 2009-05-27 09:20:02.723 9798685 16220251 15631042 8355883 15631042 3145740 16253017 1 2011-03-07 15:41:35.863 2011-03-07 15:41:35.863 19041349 8355883 8355883 3145740 19074035 19530013 19530014 19530015 19530016 19530017 19530018 19530019 19530020 19530021 1 2012-11-28 09:38:28.127 2012-11-28 09:38:28.127 10912225 8355883 10912227 8355883 3145740 10944980 11013008 11013009 1 2009-12-23 08:30:26.117 2009-12-23 08:30:26.117 9372328 8355883 8355883 3145740 9405061 13 2009-03-19 14:46:17.863 2009-09-24 14:43:13.717 9372330 9372332 9372334 9372336 9372439 9372443 9372445 9372462 9372465 9372466 9372468 10356289 15204478 8355883 8355883 3145740 15237242 15712007 15712008 15712009 15712010 15712011 23 2010-11-08 11:50:34.297 2011-02-08 11:47:45.040 15204482 15204505 15204507 15204509 15204510 15204512 15204515 15204517 15631249 15631251 15631252 15631255 15631288 15631299 15631303 15631318 15631320 15631322 15631324 15631325 15631327 15631422 8355849 8355883 8355883 3145740 8388617 21434738 9 2008-12-29 11:40:49.410 2013-08-03 11:27:03.317 8355851 9798662 9798669 9798671 9798673 9798678 21365731 21365733 23167213 18252474 8355883 18252474 3145740 23199974 23691572 10 2013-10-30 14:35:52.330 2013-11-13 11:16:04.560 23167215 23167216 23167217 23167227 23167229 23625755 23625757 23625759 23625794 12484688 8355883 8355883 3145740 12550223 14024802 14024803 14024804 14024805 14024806 14024807 14024808 14024809 14024810 14024811 14024812 13 2010-05-25 11:18:33.507 2010-07-14 12:20:03.517 12484690 12484692 12484694 12484699 12484700 12484702 13140023 13926482 13926484 13926486 13926488 13926490 15630643 8355883 8355883 3145740 15663401 15697387 1 2011-01-04 10:00:02.023 2011-01-04 10:00:02.023 13926566 8355883 8355883 3145740 13959328 14352389 35 2010-07-27 11:54:54.630 2010-09-07 17:03:39.380 13926568 13926570 13926571 13926572 13926573 13926574 13926576 13926577 13926579 13926580 13926628 13926641 13926643 13926644 13926646 13926649 13926650 13926651 13926652 13926654 13926669 13926671 13926673 13926674 13926676 13926678 13926712 13926714 13926718 13926719 13926720 13926722 14188670 14811144 14123028 16416971 5832921 8355883 5832921 3145740 16449731 16515800 2 2011-03-31 19:57:30.943 2011-03-31 20:01:09.287 16416972 16547861 18252474 8355883 23167213 8355883 3145740 18285229 5 2011-10-20 09:56:04.947 2013-10-30 14:36:14.470 18252485 23167210 23167211 23167214 18186357 18186358 18186359 18186360 18186361 18186362 18186363 18186408 18186409 3637556 10356302 8355883 10356302 3145740 3670311 3604584 3604585 3604586 3604587 3604588 3604595 3604644 3604645 4620319 4849707 5734408 14 2008-04-23 13:29:35.487 2009-09-24 15:01:32.700 3637559 3637582 3637584 3637588 3637736 3637848 3637850 3637852 3637853 3637855 3932174 4456591 10356296 3735582 3735583 3735584 3735585 11240349 11240296 8355883 11240296 11240404 3145740 11273087 29 2010-03-09 19:14:14.123 2010-03-10 11:41:40.383 11240350 11240351 11240353 11240354 11240356 11240358 11240371 11240373 11240375 11240378 11240380 11240382 11240384 11240386 11240387 11240389 11240390 11240391 11240392 11240393 11240394 11240395 11240396 11240397 11240398 11240399 11240401 11240403 16416942 16416807 8355883 16416807 3145740 16449703 5 2011-03-29 10:13:19.987 2011-03-29 10:52:03.083 16416944 16416946 16416948 16416950 16416809 16416807 8355883 16416807 3145740 16449576 6 2011-03-15 10:36:22.017 2011-03-15 11:59:39.333 16416811 16416813 16416815 16416817 16416818 16416807 8355883 16416809 16416942 18251940 8355883 3145740 16449574 18350703 18350704 18350705 4 2011-03-15 10:34:53.783 2011-08-04 15:13:35.520 16416940 18251935 18251936 19040970 8355883 8355883 3145740 19073662 19165651 19165652 7 2012-09-26 07:14:38.057 2012-09-26 08:04:20.647 19040972 19040973 19040975 19040977 19040979 19040981 19169535 5832828 8355883 8355883 3145740 5865590 10460883 10460884 10460885 10460886 10460887 4 2008-07-21 11:06:21.957 2009-09-24 14:42:42.513 5832835 5832836 5832838 5832839 10356288 16416786 15631042 8355883 15631042 3145740 16449553 7 2011-03-14 14:48:54.827 2011-03-14 17:30:04.347 16416788 16416789 16416791 16416793 16416794 16416796 17236193 8355883 18251845 19041602 8355883 3145740 17268956 19533631 19533632 19533633 19533634 19533635 19533636 19533637 19533638 19533639 19533640 19533641 26771466 46 2011-06-06 21:36:16.963 2013-01-10 13:09:34.660 17236194 17236196 17236198 17236200 17236201 17236203 17236205 17465347 17465349 17465353 17465355 17465357 17858731 17858733 17858734 17858736 17858738 17858740 17858744 17858746 17858748 17858749 18251841 18251843 18251846 18251848 18251851 18251866 18251868 18251870 18251872 18251874 18251876 18251878 18251880 18251881 18251882 18251884 18251900 19041165 19041167 19041206 19041208 19041209 19041600 18186264 18186265 18186266 18186267 18186268 18186269 18186270 18186271 18186272 18186273 18186274 18186275 18186276 18186277 11240274 8355883 8355883 3145740 11273014 11340879 11340880 11340881 11340882 8 2010-03-05 11:53:11.113 2010-03-05 12:23:36.647 11240276 11240278 11240280 11240282 11240284 11240286 11240288 7176201 8355883 8355883 3145740 7208966 10460982 10460983 6 2008-10-29 10:39:30.207 2009-09-24 14:45:44.550 9372341 9372342 9372343 9372345 10356293 19039049 8355883 8355883 3145740 19071809 19166764 19166765 19166766 19166767 19166768 19166769 19166770 19166771 19166772 19166773 19166774 19166775 6 2012-06-04 17:50:29.237 2012-10-31 13:12:54.377 19039052 19039054 19039055 19041098 19041100 11240296 8355883 11240349 11796703 8355883 3145740 11273036 11863382 11863383 28 2010-03-08 16:45:32.780 2010-04-14 13:27:41.690 11240303 11240304 11240306 11240308 11240309 11240311 11240313 11240315 11240316 11240317 11240319 11240320 11240323 11240324 11240326 11240328 11240330 11240331 11240344 11240345 11240347 11796699 11796701 11796705 11796706 11796708 11796799 19040991 8355883 8355883 3145740 19073683 19168547 19168548 19168549 19168550 19168551 19168552 19168553 19168554 19168555 19168556 19168557 19168558 19168559 19168560 19168561 19168562 19168563 19168564 19168565 19168566 19168567 19168568 19168569 19168570 19168571 19168572 19168573 19168574 19168575 19168576 19168577 19168578 19168579 19168580 19168581 19168582 19168583 19168584 19168585 19168586 19168587 19168588 19168589 19168590 19168591 19168592 19168593 19168594 19168595 19168596 19168597 19168598 19168599 19168600 19168601 34 2012-09-26 11:09:35.667 2012-11-15 12:58:23.647 19040992 19040993 19040994 19040996 19040997 19041001 19041002 19041162 19041172 19041174 19041175 19041177 19041178 19041179 19041180 19041181 19041182 19041183 19041185 19041187 19041189 19041190 19041192 19041194 19041196 19041198 19041200 19041201 19041202 19041204 19041225 19041226 19041228 18580092 19041520 8355883 19041520 3145740 18645599 19533120 19533121 18 2012-03-07 14:57:05.953 2012-12-30 11:48:39.190 18580094 18580096 18580100 18580103 18580105 18580107 18580108 18580110 18580112 18580114 18580116 18580118 18580120 18580122 18580123 18580125 19041521 18841764 18841767 10911981 8355883 10356237 8355883 3145740 10944744 16 2009-11-05 10:52:22.817 2009-12-30 11:59:17.807 10911983 10911987 10911988 10911990 10911991 10911993 10911995 10911997 10911999 10912001 10912002 10912004 10912006 10912008 10912254 16416865 15631042 8355883 15631042 3145740 16449628 2 2011-03-21 10:00:53.793 2011-03-21 10:19:37.463 16416867 19040089 19040044 8355883 19040044 3145740 19072807 19156712 19156713 2 2012-07-15 08:18:15.653 2012-07-15 08:19:07.170 19040090 7766027 8355883 8355883 3145740 7798793 14024906 14024907 8 2008-11-12 08:47:47.573 2010-07-28 08:05:14.757 7766029 7766031 7766033 7766034 7766042 10354786 13926590 10355550 9798398 8355883 9798398 3145740 10388278 10460505 10460506 5 2009-07-23 10:06:25.403 2009-09-24 14:34:13.447 10355555 10355557 10355559 10356273 9798359 8355883 8355883 3145740 9831110 1 2009-05-08 11:58:14.617 2009-05-08 11:58:14.617 16777460 8355883 8355883 3145740 16810221 16879380 16879381 16879382 16879383 16879384 16879385 16879386 16879387 1 2011-05-23 16:13:52.997 2011-05-23 16:13:52.997 15204448 8355883 8355883 3145740 15237213 2 2010-11-02 09:21:37.147 2010-11-02 09:22:03.103 15204449 6259010 8355883 8355883 3145740 6226231 10 2008-08-27 13:39:41.480 2009-09-24 14:43:55.347 6259012 6259014 6259035 7176207 7176209 7176214 7176216 8060942 10356290 9798378 8355883 8355883 9798385 9798386 3145740 9831128 9961505 10256387 17 2009-05-09 15:33:01.367 2009-05-27 12:46:56.967 9798380 9798382 9798384 9798388 9798390 9798403 9798405 9798407 9798410 9798416 9798686 9798688 9798692 9798694 9798696 10354695 27066970 23167205 23167205 3145740 27099731 27138185 27138186 3 2015-04-15 09:51:04.943 2015-04-15 09:54:12.063 27066972 27066973 27263016 27263017 19040054 19040044 8355883 19040044 3145740 19072772 19156590 1 2012-07-14 14:54:08.180 2012-07-14 14:54:08.180 10356476 8355883 8355883 3145740 10389188 11338164 11141121 44 2009-10-08 12:07:56.397 2010-01-22 15:47:49.153 10356479 10911919 10911921 10911923 10911925 10911927 10911928 10911930 10911932 10911933 10911935 10911937 10911939 10911940 10911942 10911946 10911949 10911952 10911954 10911956 10911958 10911960 10911961 10911963 10911964 10911966 10911968 10911970 10912150 10912160 10912161 10912163 10912165 10912173 10912177 11239521 11239523 11239524 11239525 11239527 11239529 11239531 11239533 11403272 11403273 11403306 11403310 11403338 11403342 11403343 11403357 11403358 11403359 11403365 11763713 11763732 11763740 18251940 16416807 8355883 16416807 3145740 18284704 1 2011-08-04 15:38:48.243 2011-08-04 15:38:48.243 5832918 8355883 8355883 3145740 5865679 2 2008-08-04 13:40:51.173 2009-09-24 14:39:51.913 10356285 19040050 19040044 8355883 19040044 3145740 19072769 1 2012-07-14 14:50:26.363 2012-07-14 14:50:26.363 5832921 8355883 9798447 9798684 15630941 16416971 8355883 3145740 5865681 16515795 16515796 16515797 16515798 16515799 21 2008-08-04 13:42:13.733 2011-03-31 19:55:11.330 6259221 6259268 6259412 7372808 7372809 7766101 7766103 8060940 9371740 9371758 9371858 9371860 9372016 9798445 9798682 15630934 15630936 15630938 15630939 16416969 19040044 8355883 19040050 19040054 19040089 8355883 3145740 19072763 21435477 21435478 21435479 21435480 21435481 21435482 33 2012-07-13 10:43:52.837 2013-08-15 08:20:15.347 19040046 19040048 19040052 19040055 19040057 19040059 19040060 19040061 19040063 19040065 19040067 19040068 19040069 19040071 19040072 19040074 19040076 19040078 19040080 19040082 19040084 19040085 19040087 19040092 19040093 21365519 21365521 21365683 21365685 21365686 21365687 21365994 19169491 19169492 10356471 8355883 8355883 3145740 10389183 11141122 40 2009-10-08 12:05:43.910 2009-12-08 16:21:20.753 10356473 10911760 10911762 10911895 10911896 10911898 10911899 10911901 10911906 10911907 10911908 10911909 10911910 10911912 10911914 10911916 10911917 10911943 10911944 10912010 10912012 10912014 10912016 10912018 10912019 10912022 10912049 10912051 10912052 10912086 10912099 10912101 10912102 10912104 10912113 10912155 10912167 10912168 10912175 3638030 8355883 8355883 3145740 3670777 15707913 15707914 15707915 15707916 15707917 15707918 15707919 15707920 15707921 15707922 15707923 15707924 15707925 15707926 15707927 15707928 15707929 15707930 15707931 15707932 15707933 3604675 3604676 3604696 4096010 4849756 40 2008-05-12 09:51:47.077 2011-01-18 21:33:44.513 3638031 3638034 3638036 3638073 3638074 3638112 3932176 3932178 3932184 3932219 3932227 3932228 4456525 4456526 4915278 5275677 5373956 5374051 5374060 5374062 5374068 5374115 5374253 5374354 5374431 5374432 5374433 5374680 5374682 5374684 5374688 5374709 5374714 5374716 5374721 5374723 5374730 5832868 6258995 6258997 10356295 15630943 4063234 4063235 4063236 5439492 5439500 5439501 5439502 5439503 3637286 8355883 8355883 3145740 3670051 10460487 10460488 10460489 10460490 10460491 10460492 10460493 10460494 10460495 10460496 10460497 10460498 10460499 10460500 10460501 10460502 10460503 10460504 3604492 3604493 3604496 3604497 3604498 3604501 3604503 3604505 3604512 3604605 68 2008-04-14 16:11:58.510 2009-09-24 14:31:39.633 3637288 3637289 3637290 3637291 3637292 3637293 3637294 3637296 3637297 3637298 3637299 3637300 3637301 3637302 3637304 3637306 3637307 3637308 3637309 3637310 3637311 3637313 3637314 3637315 3637317 3637318 3637323 3637332 3637333 3637335 3637475 3637477 3637479 3637530 3637602 3637604 3637605 3637606 3637607 3637609 3637610 3637613 3637645 3637660 3637661 3637662 3637685 3637687 3637730 3637731 3637733 3637735 3638111 5374070 5374073 5374075 5374520 5374526 5374527 7372857 7372862 7372865 7372870 10354806 10354809 10354812 10356271 3735555 3735556 3735557 3735558 3735559 3735560 3735562 3735564 3735565 3735566 27067271 8355883 8355883 3145740 27100025 27143383 27143384 27143385 5 2015-06-09 11:38:01.650 2015-06-10 14:05:44.280 27067273 27067275 27067277 27067284 19041602 17236193 8355883 17236193 3145740 19074283 1 2013-01-10 13:21:43.920 2013-01-10 13:21:43.920 15630363 8355883 17858588 8355883 3145740 15663129 6 2010-11-30 22:31:25.733 2010-12-01 06:38:43.263 15630364 15630365 15630366 15630368 15630375 11796703 11240296 8355883 11240296 3145740 11829460 11863045 11863046 11863047 11863048 11863049 11863050 11863051 11863052 11863053 11863054 11863055 1 2010-04-13 09:03:08.517 2010-04-13 09:03:08.517 15630373 8355883 8355883 3145740 15663138 1 2010-11-30 22:49:22.087 2010-11-30 22:49:22.087 21365729 3145740 21398443 28083296 28083297 28083298 28083299 28083300 28083301 28083302 28083303 28083304 28083305 28083306 28083307 28083308 28083309 28083310 28083311 28083312 28083313 28083314 28083315 28083316 28083317 28083318 28083319 29655066 83 2013-08-03 11:21:10.280 2015-08-21 16:30:52.903 25067522 25395487 25395489 27557970 27557972 27557974 27557976 27557978 27557980 27557982 27557984 27557986 27557988 27557990 27557992 27557994 27557996 27557998 27557999 27558013 27558032 27558035 27558037 27558040 27558042 27558044 27558089 27558091 27558092 27558094 27558097 27558099 27558100 27558101 27558103 27558105 27558107 27558108 27558110 27558112 27558115 27558117 27558119 27558121 27558123 27558125 27558127 27558129 27558130 27558138 27558140 27558142 27558144 27558146 27558161 27558163 27558165 27558169 27558171 27558173 27558175 27558176 27558178 27558180 27558182 27558184 27558186 27558188 27558190 27558192 27558194 27558196 27558198 27558200 27558202 27558204 27558206 27558208 27558219 27558229 28016661 28016663 9798398 8355883 10355550 8355883 3145740 9831148 10460601 10256388 5 2009-05-11 10:01:43.157 2009-09-24 14:35:18.690 9798400 9798516 9798517 10356277 15631042 8355883 15631044 16220240 16220251 16416786 16416865 17858701 8355883 3145740 15663795 17957933 17957934 17957935 17957936 17957937 17957938 6 2011-01-23 23:16:28.733 2011-06-23 11:41:10.920 16220238 16220249 16416784 16416863 17858699 3145740 3114598 8355883 3211565 3211566 3211567 3211568 3211569 3211570 3211571 3211572 3211573 3211574 3211575 3211576 3211577 3211578 4882516 4882520 4882521 19300620 2008-04-09 12:55:07.143 2009-09-24 14:17:05.313 global 15631044 15631042 8355883 15631042 3145740 15663797 16285946 16285947 8 2011-01-23 23:21:42.587 2011-03-03 08:57:29.177 15631046 15631048 15631050 15631053 15631055 15631056 16220237 9798110 8355883 8355883 3145740 9830865 2 2009-05-01 14:58:13.070 2009-05-29 15:03:55.927 10354784 19039359 8355883 8355883 3145740 19072100 19145833 19145834 19145835 19145836 19 2012-06-25 13:36:31.327 2012-06-26 08:05:53.093 19039360 19039362 19039364 19039366 19039368 19039369 19039371 19039374 19039379 19039380 19039382 19039383 19039385 19039386 19039388 19039396 19039397 19039400 19169471 814 8355883 8355883 3145740 811 10455646 10455647 10455648 10455649 10455650 10455651 10455652 10455653 10455654 10455655 10455656 10455657 10455658 10455659 10455660 10455661 10455662 10455663 10455664 10455665 10455666 34 2007-02-07 14:07:35.807 2009-06-04 12:45:16.043 815 816 817 818 819 820 821 822 823 824 825 826 828 834 835 852 853 854 1040 1041 1042 589828 589829 589830 589831 589832 589833 589834 5374694 5374696 5374698 10354896 10354901 557058 19039402 8355883 8355883 3145740 19072142 14 2012-06-26 10:17:36.350 2012-06-26 13:17:55.650 19039404 19039405 19039406 19039408 19039410 19039412 19039414 19039416 19039418 19039419 19039421 19039422 19039423 10912300 8355883 8355883 3145740 10945055 11013740 11013741 11013742 11013743 11013744 11013745 11013746 11013747 11013748 11013749 11013750 11013751 11013752 11013753 11013754 11013755 11013756 11013757 11013758 11013759 11013760 11013761 11013762 11013763 11013764 11013765 11013766 11013767 11013768 11013769 11013770 11013771 11013772 11013773 11013774 11013775 11013776 11013777 1 2010-01-05 08:32:12.603 2010-01-05 08:32:12.603 17858701 15631042 8355883 15631042 3145740 17891454 1 2011-06-23 11:42:42.387 2011-06-23 11:42:42.387 11797066 11797064 8355883 11797064 3145740 11829819 3 2010-04-27 15:13:02.987 2010-04-28 11:59:48.923 11797067 11797114 11763741 19041520 8355883 18580092 8355883 3145740 19074203 19533122 2 2012-12-30 11:48:04.033 2012-12-30 11:49:24.833 19041522 11797064 8355883 11797066 17858720 8355883 3145740 11829817 17957940 17957941 2 2010-04-27 14:44:20.247 2011-06-24 10:28:41.410 17858718 16777373 8355883 8355883 3145740 16810135 16876374 1 2011-05-09 13:08:18.217 2011-05-09 13:08:18.217 17858720 11797064 8355883 11797064 3145740 17891472 1 2011-06-24 10:38:10.997 2011-06-24 10:38:10.997 9798447 5832921 8355883 5832921 3145740 9831198 8 2009-05-12 17:00:48.963 2009-09-04 15:46:37.813 10354711 10354738 10354861 10354863 10356107 10356109 10356111 10356302 8355883 3637556 5374734 8355883 3145740 10389018 15709264 15709265 2 2009-09-24 15:00:46.927 2011-01-31 21:46:28.770 15631242 3244068 SPEPRJ false custom ]]> 15631413 8355883 15631415 8355883 3145740 15664164 15712000 1 2011-02-07 08:51:30.257 2011-02-07 08:51:30.257 3244067 4]]> 3244066 theme.key ]]> 15631415 15631413 8355883 15631413 3145740 15664166 1 2011-02-07 10:22:29.400 2011-02-07 10:22:29.400 10354884 10354882 8355883 10354882 3145740 10387648 5 2009-06-04 09:34:49.790 2009-06-04 12:46:47.277 10354885 10354887 10354892 10354902 10485828 10485829 10485830 10485831 10485832 10485833 10485834 10485835 10485836 10485837 10485838 10485839 10485840 10485841 10485842 10485843 10485844 10485845 10485846 10485847 10485848 10485849 10485850 10354882 8355883 10354884 8355883 3145740 10387646 19533123 19533124 2 2009-06-04 09:33:08.477 2012-12-30 11:51:19.413 19041523 6259430 8355883 8355883 3145740 6226632 15712644 15712645 15712646 15712647 15712648 9961511 20 2008-10-21 10:34:48.373 2011-02-10 13:49:53.400 6259432 6259434 6259436 6259438 6259440 6259442 6259444 6259446 6259448 6259450 6259451 6586370 6586371 6586374 8355842 8355844 9798641 15631437 15631482 6717441 6717442 18252222 8355883 8355883 3145740 18284982 2 2011-09-13 13:58:01.047 2011-09-13 13:59:51.173 18252224 2162995 8355883 8355883 3145740 2195759 19138240 19138241 19138242 19138243 19138244 19138245 19138246 19138247 19138248 3277006 4849755 53 2007-12-03 13:18:03.697 2012-04-13 16:28:00.083 2162996 2162997 2162998 2162999 2163000 2163001 2163002 2163003 2163004 2163005 2163006 2163007 2163020 2163021 2163022 2163023 2163024 2163025 2163026 2163027 2163038 2163039 2163043 2163044 2163048 2163049 2163050 2163052 2163067 2163104 2785288 2785291 2785292 2785294 3112964 3112990 3112992 3112994 3112996 3113538 3114053 4456450 4456452 4456454 7176232 8355852 15630526 18579511 18579513 18579514 19038344 19038479 2326545 2326546 2326547 2326557 2326555 2326556 4587521 19040241 3145740 19072947 19159442 1 2012-07-24 17:24:07.230 2012-07-24 17:24:07.230 15630941 5832921 8355883 5832921 3145740 15663695 1 2011-01-18 21:23:19.297 2011-01-18 21:23:19.297 15631445 8355883 8355883 3145740 15664196 16285789 16285790 16285791 16285792 16285793 19 2011-02-09 09:50:05.230 2011-02-22 19:09:59.103 15631498 15631500 15631502 15990819 15990821 15990823 15990825 15990827 15990828 15990830 15990853 15990855 15990857 15990859 15990861 15990863 16220193 16220195 16417009 8355883 8355883 3145740 16449769 1 2011-04-04 10:39:07.340 2011-04-04 10:39:07.340 23167205 27066970 3145740 23199966 27138183 29 2013-10-30 14:29:58.263 2015-04-15 09:51:32.573 23167207 24051764 24051765 24051767 24051769 24051771 24051773 24051775 24051777 24051778 24051780 24051873 24052036 24052258 24052260 24052261 24052262 24052264 24052266 26640386 26640388 27066961 27066963 27066964 27066965 27066967 27066968 27066971 27263014 27263015 15631441 8355883 8355883 3145740 15664192 19137804 19137805 19137806 19137807 17 2011-02-09 06:25:02.520 2012-04-10 11:10:09.393 15631496 15631667 15631681 15631683 15990786 15990788 15990790 15990803 15990805 15990809 15990811 15990832 15990847 15990851 19038429 19038431 10356280 8355883 8355883 3145740 10388997 10460693 10460694 10460695 10460696 1 2009-09-24 14:36:14.363 2009-09-24 14:36:14.363 3637859 8355883 8355883 3145740 3670609 3604649 3604650 3604651 3604674 3 2008-05-06 16:38:16.753 2009-09-24 14:44:18.787 3637861 10356291 10356284 8355883 8355883 3145740 10389000 10460789 1 2009-09-24 14:38:07.757 2009-09-24 14:38:07.757 15630488 8355883 8355883 3145740 15663251 19532312 19532313 19532314 19532315 19532316 19532317 19532318 19532319 19532320 19532321 19532322 19532323 19532324 19532325 19532326 19532327 19532328 19532329 19532330 19532331 19532332 19532333 19532334 19532335 19532336 19532337 19532338 19532339 19532340 19532341 19532342 19532343 19532344 19532345 19532346 19532347 19532348 19532349 19532350 19532351 19532352 19532353 19532354 19532355 19532356 19532357 19532358 19532359 19532360 19532361 19532362 19532363 19532364 19532365 19532366 19532367 19532368 19532369 19532370 19532371 19532372 19532373 19532374 19532375 19532376 19532377 19532378 19532379 19532380 19532381 19532382 19532383 19532384 19532385 19532386 19532387 19532388 19532389 19532390 19532391 19532392 19532393 19532394 19532395 19532396 19532397 19532398 19532399 19532400 19532401 19532402 19532403 19532404 19532405 19532406 19532407 19532408 19532409 19532410 19532411 19532412 19532413 19532414 19532415 19532416 19532417 19532418 19532419 19532420 19532421 19532422 19532423 19532424 19532425 19532426 19532427 19532428 19532429 19532430 19532431 19532432 19532433 19532434 19532435 19532436 19532437 19532438 19532439 19532440 19532441 19532442 19532443 19532444 48 2010-12-15 13:35:53.173 2012-12-15 08:12:36.767 15630490 15630492 15630494 15630495 15630497 15630501 15630504 15630508 15630509 15630510 15630512 15630528 15630531 19038478 19038481 19038483 19038485 19041147 19041149 19041151 19041153 19041155 19041157 19041159 19041383 19041385 19041387 19041389 19041391 19041392 19041394 19041396 19041411 19041413 19041415 19041417 19041418 19041420 19041422 19041424 19041426 19041428 19041430 19041432 19041442 19041444 19041446 15728670 15728671 19169334 19169335 19169336 19169337 19169338 19169339 19169342 19169551 19169552 19169553 19169554 19169555 19169556 19169557 19169559 19169560 19169563 19169590 19169591 19169592 19169561 19169562 19169558 19169340 19169341 5374734 10356302 8355883 10356302 3145740 5407464 3 2008-07-08 15:13:10.307 2009-09-24 15:01:46.997 5374736 10356298 27066777 3145740 27099540 2 2015-03-05 13:19:01.760 2015-03-05 13:31:06.850 27066782 10354826 8355883 8355883 3145740 10387592 10454642 10454643 10454644 1 2009-06-01 10:05:31.383 2009-06-01 10:05:31.383 10356237 10911981 8355883 10911981 3145740 10388955 5 2009-09-18 12:04:09.600 2009-11-05 10:53:10.617 10356239 10356241 10356261 10911977 15631339 8355883 8355883 15631352 3145740 15664089 15711688 15711689 15711690 15711691 4 2011-02-03 13:59:06.237 2011-02-03 20:48:24.360 15631341 15631348 15631351 15728735 15728736 10354800 8355883 8355883 3145740 10387566 10454078 10454079 10454080 6 2009-05-29 15:27:30.707 2009-05-29 15:36:18.530 10354801 10354803 10354805 10354808 10354811 11239606 8355883 8355883 3145740 11272371 11338397 11338398 11338399 11338400 11338401 11338402 11338403 11338404 11338405 11338406 11338407 11338408 11338409 7 2010-01-29 15:27:06.493 2010-01-29 18:21:04.977 11239608 11239610 11239612 11239614 11239615 11239617 17858588 15630363 8355883 15630363 3145740 17891355 17957514 17957515 17957516 17957517 17957518 17957519 17957520 17957521 17957522 17957523 17957524 17957525 17957526 17957527 17957528 17957529 17957530 17957531 17957532 17957533 17957534 17957535 17957536 17957537 17957538 17957539 17957540 17957541 17957542 17957543 17957544 17957545 17957546 17957547 17957548 17957549 17957550 17957551 17957552 17957553 17957554 17957555 17957556 17957557 17957558 17957559 17957560 17957561 17957562 17957563 17957564 17957565 1 2011-06-14 09:06:37.993 2011-06-14 09:06:37.993 17957532 17858588 2011-06-14 09:06:38.100 2011-06-14 09:06:38.100 17957533 17858588 2011-06-14 09:06:38.100 2011-06-14 09:06:38.100 11240375 11273113 9 2010-03-09 19:14:14.123 2010-03-10 11:18:59.553 11240349 17957534 17858588 2011-06-14 09:06:38.100 2011-06-14 09:06:38.100 11240378 11273116 10 2010-03-09 19:14:14.123 2010-03-10 11:23:48.057 11240349 17957535 17858588 2011-06-14 09:06:38.100 2011-06-14 09:06:38.100 17957536 17858588 2011-06-14 09:06:38.100 2011-06-14 09:06:38.100 17957537 17858588 2011-06-14 09:06:38.100 2011-06-14 09:06:38.100 11240371 11273109 7 2010-03-09 19:14:14.123 2010-03-09 19:20:09.693 11240349 17957538 17858588 2011-06-14 09:06:38.100 2011-06-14 09:06:38.100 17957539 17858588 2011-06-14 09:06:38.100 2011-06-14 09:06:38.100 11240373 11273111 8 2010-03-09 19:14:14.123 2010-03-10 11:18:21.433 11240349 17957524 17858588 2011-06-14 09:06:38.100 2011-06-14 09:06:38.100 17957525 17858588 2011-06-14 09:06:38.100 2011-06-14 09:06:38.100 10912177 10944934 35 2009-10-08 12:07:56.397 2009-12-08 16:11:34.363 10356476 17957526 17858588 2011-06-14 09:06:38.100 2011-06-14 09:06:38.100 17957527 17858588 2011-06-14 09:06:38.100 2011-06-14 09:06:38.100 10912175 10944932 39 2009-10-08 12:05:43.910 2009-12-03 17:03:30.863 10356471 17957528 17858588 2011-06-14 09:06:38.100 2011-06-14 09:06:38.100 17957529 17858588 2011-06-14 09:06:38.100 2011-06-14 09:06:38.100 10912173 10944930 34 2009-10-08 12:07:56.397 2009-12-03 10:23:42.520 10356476 17957530 17858588 2011-06-14 09:06:38.100 2011-06-14 09:06:38.100 17957531 17858588 2011-06-14 09:06:38.100 2011-06-14 09:06:38.100 17957549 17858588 2011-06-14 09:06:38.100 2011-06-14 09:06:38.100 11240391 11273129 18 2010-03-09 19:14:14.123 2010-03-10 11:33:56.140 11240349 17957548 17858588 2011-06-14 09:06:38.100 2011-06-14 09:06:38.100 11240392 11273130 19 2010-03-09 19:14:14.123 2010-03-10 11:34:31.030 11240349 17957551 17858588 2011-06-14 09:06:38.100 2011-06-14 09:06:38.100 11240393 11273131 20 2010-03-09 19:14:14.123 2010-03-10 11:35:03.223 11240349 17957550 17858588 2011-06-14 09:06:38.100 2011-06-14 09:06:38.100 11240394 11273132 21 2010-03-09 19:14:14.123 2010-03-10 11:35:44.437 11240349 17957553 17858588 2011-06-14 09:06:38.100 2011-06-14 09:06:38.100 11240387 11273125 15 2010-03-09 19:14:14.123 2010-03-10 11:31:47.970 11240349 17957552 17858588 2011-06-14 09:06:38.100 2011-06-14 09:06:38.100 17957555 17858588 2011-06-14 09:06:38.103 2011-06-14 09:06:38.103 11240389 11273127 16 2010-03-09 19:14:14.123 2010-03-10 11:32:45.693 11240349 17957554 17858588 2011-06-14 09:06:38.100 2011-06-14 09:06:38.100 11240390 11273128 17 2010-03-09 19:14:14.123 2010-03-10 11:33:42.540 11240349 17957541 17858588 2011-06-14 09:06:38.100 2011-06-14 09:06:38.100 17957540 17858588 2011-06-14 09:06:38.100 2011-06-14 09:06:38.100 11240384 11273122 13 2010-03-09 19:14:14.123 2010-03-10 11:28:21.623 11240349 17957543 17858588 2011-06-14 09:06:38.100 2011-06-14 09:06:38.100 17957542 17858588 2011-06-14 09:06:38.100 2011-06-14 09:06:38.100 11240386 11273124 14 2010-03-09 19:14:14.123 2010-03-10 11:29:34.520 11240349 17957545 17858588 2011-06-14 09:06:38.100 2011-06-14 09:06:38.100 17957544 17858588 2011-06-14 09:06:38.100 2011-06-14 09:06:38.100 11240380 11273118 11 2010-03-09 19:14:14.123 2010-03-10 11:25:58.977 11240349 17957547 17858588 2011-06-14 09:06:38.100 2011-06-14 09:06:38.100 17957546 17858588 2011-06-14 09:06:38.100 2011-06-14 09:06:38.100 11240382 11273120 12 2010-03-09 19:14:14.123 2010-03-10 11:27:38.847 11240349 18284704 18251940 15696765 3113965 2010-12-17 07:24:41.110 2010-12-17 07:24:41.110 15696764 3113965 2010-12-17 07:24:41.110 2010-12-17 07:24:41.110 15696767 3113965 2010-12-17 07:24:41.110 2010-12-17 07:24:41.110 15696766 3113965 2010-12-17 07:24:41.110 2010-12-17 07:24:41.110 11240403 11273141 28 2010-03-09 19:14:14.123 2010-03-10 11:40:33.840 11240349 15696761 3113965 2010-12-17 07:24:41.110 2010-12-17 07:24:41.110 15696760 3113965 2010-12-17 07:24:41.110 2010-12-17 07:24:41.110 11240401 11273139 27 2010-03-09 19:14:14.123 2010-03-10 11:39:30.083 11240349 26771466 1 17236193 2014-07-22 14:27:15.020 2014-07-22 14:27:15.020 15696763 3113965 2010-12-17 07:24:41.110 2010-12-17 07:24:41.110 15696762 3113965 2010-12-17 07:24:41.110 2010-12-17 07:24:41.110 11240399 11273137 26 2010-03-09 19:14:14.123 2010-03-10 11:39:10.557 11240349 11240398 11273136 25 2010-03-09 19:14:14.123 2010-03-10 11:38:48.893 11240349 11240397 11273135 24 2010-03-09 19:14:14.123 2010-03-10 11:37:22.260 11240349 15696759 3113965 2010-12-17 07:24:41.110 2010-12-17 07:24:41.110 11240396 11273134 23 2010-03-09 19:14:14.123 2010-03-10 11:36:58.153 11240349 15696758 3113965 2010-12-17 07:24:41.110 2010-12-17 07:24:41.110 11240395 11273133 22 2010-03-09 19:14:14.123 2010-03-10 11:36:12.250 11240349 17957519 17858588 2011-06-14 09:06:38.100 2011-06-14 09:06:38.100 10912231 10944986 2 2009-12-23 08:33:45.977 2009-12-23 08:36:16.590 10912227 17957518 17858588 2011-06-14 09:06:38.100 2011-06-14 09:06:38.100 17957517 17858588 2011-06-14 09:06:38.100 2011-06-14 09:06:38.100 10912233 10944988 3 2009-12-23 08:33:45.977 2009-12-23 08:50:30.087 10912227 17957516 17858588 2011-06-14 09:06:38.100 2011-06-14 09:06:38.100 17957523 17858588 2011-06-14 09:06:38.100 2011-06-14 09:06:38.100 19038483 19071249 16 2010-12-15 13:35:53.173 2012-04-13 16:43:54.027 15630488 17957522 17858588 2011-06-14 09:06:38.100 2011-06-14 09:06:38.100 17957521 17858588 2011-06-14 09:06:38.100 2011-06-14 09:06:38.100 19038485 19071251 17 2010-12-15 13:35:53.173 2012-04-13 16:47:07.110 15630488 10912229 10944984 1 2009-12-23 08:33:45.977 2009-12-23 08:33:45.977 10912227 14188670 14221436 33 2010-07-27 11:54:54.630 2010-08-04 15:38:32.723 13926566 17957520 17858588 2011-06-14 09:06:38.100 2011-06-14 09:06:38.100 19038479 19071245 52 2007-12-03 13:18:03.697 2012-04-02 10:20:30.487 2162995 10912223 10944978 89 2009-01-06 09:56:05.890 2009-11-05 10:51:20.920 8355883 19038481 19071247 15 2010-12-15 13:35:53.173 2012-04-13 16:17:21.707 15630488 17957515 17858588 2011-06-14 09:06:38.100 2011-06-14 09:06:38.100 17957514 17858588 2011-06-14 09:06:38.100 2011-06-14 09:06:38.100 19038477 19071243 209 2009-01-06 09:56:05.890 2012-03-05 15:29:29.637 8355883 19038478 19071244 14 2010-12-15 13:35:53.173 2010-12-17 07:24:41.303 15630488 11240308 11273047 4 2010-03-08 16:45:32.780 2010-03-08 17:17:52.670 11240296 11240309 11273048 5 2010-03-08 16:45:32.780 2010-03-08 17:19:12.423 11240296 6586370 6619138 12 2008-10-21 10:34:48.373 2008-10-21 11:48:40.217 6259430 11240311 11273050 6 2010-03-08 16:45:32.780 2010-03-08 17:27:14.070 11240296 3309644 3113965 2008-03-19 16:09:27.213 2008-03-19 16:09:27.213 1779 1 3309645 3113965 2008-03-19 16:11:27.143 2008-03-19 16:11:27.143 4341 1 11240313 11273052 7 2010-03-08 16:45:32.780 2010-03-08 17:28:01.417 11240296 6586374 6619142 14 2008-10-21 10:34:48.373 2008-10-21 14:32:55.237 6259430 6586371 6619139 13 2008-10-21 10:34:48.373 2008-10-21 14:28:31.497 6259430 11240304 11273043 2 2010-03-08 16:45:32.780 2010-03-08 16:56:04.980 11240296 10912113 10944873 35 2009-10-08 12:05:43.910 2009-11-18 11:23:28.090 10356471 11240303 11273042 1 2010-03-08 16:45:32.780 2010-03-08 16:45:32.780 11240296 11240306 11273045 3 2010-03-08 16:45:32.780 2010-03-08 16:56:30.627 11240296 11240323 11273062 13 2010-03-08 16:45:32.780 2010-03-08 17:41:37.203 11240296 11240324 11273063 14 2010-03-08 16:45:32.780 2010-03-08 18:16:26.300 11240296 11240326 11273065 15 2010-03-08 16:45:32.780 2010-03-08 18:17:27.127 11240296 11240328 11273067 16 2010-03-08 16:45:32.780 2010-03-08 18:31:58.313 11240296 11240330 11273069 17 2010-03-08 16:45:32.780 2010-03-08 18:34:53.487 11240296 3309647 3113965 2008-03-19 16:24:20.443 2008-03-19 16:24:20.443 1107 1 11240315 11273054 8 2010-03-08 16:45:32.780 2010-03-08 17:29:17.693 11240296 3309646 3113965 2008-03-19 16:22:08.703 2008-03-19 16:22:08.703 3097 1 11240316 11273055 9 2010-03-08 16:45:32.780 2010-03-08 17:32:58.423 11240296 11240317 11273056 10 2010-03-08 16:45:32.780 2010-03-08 17:34:01.560 11240296 11240319 11273058 11 2010-03-08 16:45:32.780 2010-03-08 17:36:01.577 11240296 11240320 11273059 12 2010-03-08 16:45:32.780 2010-03-08 17:40:41.080 11240296 11240322 11273061 96 2009-01-06 09:56:05.890 2010-03-08 16:27:08.297 8355883 11240342 11273081 97 2009-01-06 09:56:05.890 2010-03-08 18:15:57.947 8355883 10912150 10944908 29 2009-10-08 12:07:56.397 2009-11-05 10:03:24.223 10356476 15709264 10356302 2011-01-31 21:46:29.073 2011-01-31 21:46:29.073 15709265 10356302 2011-01-31 21:46:29.073 2011-01-31 21:46:29.073 5374680 5407411 25 2008-05-12 09:51:47.077 2008-06-24 15:32:13.677 3638030 11240345 11273084 20 2010-03-08 16:45:32.780 2010-03-09 19:11:02.910 11240296 17957564 17858588 2011-06-14 09:06:38.103 2011-06-14 09:06:38.103 11240344 11273083 19 2010-03-08 16:45:32.780 2010-03-08 18:54:34.080 11240296 17957565 17858588 2011-06-14 09:06:38.103 2011-06-14 09:06:38.103 5374682 5407413 26 2008-05-12 09:51:47.077 2008-06-30 10:28:00.813 3638030 9831416 9798677 17957562 17858588 2011-06-14 09:06:38.103 2011-06-14 09:06:38.103 17957563 17858588 2011-06-14 09:06:38.103 2011-06-14 09:06:38.103 17957560 17858588 2011-06-14 09:06:38.103 2011-06-14 09:06:38.103 17957561 17858588 2011-06-14 09:06:38.103 2011-06-14 09:06:38.103 11240331 11273070 18 2010-03-08 16:45:32.780 2010-03-08 18:50:57.113 11240296 17957558 17858588 2011-06-14 09:06:38.103 2011-06-14 09:06:38.103 17957559 17858588 2011-06-14 09:06:38.103 2011-06-14 09:06:38.103 3113538 3179038 40 2007-12-03 13:18:03.697 2008-01-07 10:33:59.000 2162995 17957556 17858588 2011-06-14 09:06:38.103 2011-06-14 09:06:38.103 9831423 9798684 17957557 17858588 2011-06-14 09:06:38.103 2011-06-14 09:06:38.103 10912163 10944921 32 2009-10-08 12:07:56.397 2009-12-02 16:27:06.113 10356476 11240358 11273096 6 2010-03-09 19:14:14.123 2010-03-09 19:18:08.883 11240349 5374694 5407425 29 2007-02-07 14:07:35.807 2007-03-19 10:33:38.097 814 10912165 10944923 33 2009-10-08 12:07:56.397 2009-12-03 09:53:44.550 10356476 11240356 11273094 5 2010-03-09 19:14:14.123 2010-03-09 19:16:28.800 11240349 5374696 5407427 30 2007-02-07 14:07:35.807 2008-07-01 15:17:12.797 814 10912167 10944925 37 2009-10-08 12:05:43.910 2009-12-01 13:15:49.210 10356471 10912168 10944926 38 2009-10-08 12:05:43.910 2009-12-03 17:02:39.213 10356471 5374698 5407429 31 2007-02-07 14:07:35.807 2008-07-01 15:20:53.330 814 5374684 5407415 27 2008-05-12 09:51:47.077 2008-06-30 10:30:51.650 3638030 10912155 10944913 36 2009-10-08 12:05:43.910 2009-11-19 16:41:57.270 10356471 11240350 11273088 1 2010-03-09 19:14:14.123 2010-03-09 19:14:14.123 11240349 11240347 11273085 21 2010-03-08 16:45:32.780 2010-03-09 19:11:13.690 11240296 5374688 5407419 28 2008-05-12 09:51:47.077 2008-06-30 11:12:41.087 3638030 11240353 11273091 3 2010-03-09 19:14:14.123 2010-03-09 19:15:12.183 11240349 11240354 11273092 4 2010-03-09 19:14:14.123 2010-03-09 19:15:48.423 11240349 10912160 10944918 30 2009-10-08 12:07:56.397 2009-12-01 10:47:56.730 10356476 11240351 11273089 2 2010-03-09 19:14:14.123 2010-03-09 19:14:42.820 11240349 10912161 10944919 31 2009-10-08 12:07:56.397 2009-12-02 16:26:21.167 10356476 10912049 10944808 27 2009-10-08 12:05:43.910 2009-11-09 12:11:23.623 10356471 9831198 9798447 5832826 5865588 17 2008-04-09 12:55:07.147 2008-07-08 13:57:32.783 3114599 10912051 10944810 28 2009-10-08 12:05:43.910 2009-11-11 10:18:07.540 10356471 10912052 10944811 29 2009-10-08 12:05:43.910 2009-11-11 10:21:39.907 10356471 2785294 2818060 34 2007-12-03 13:18:03.697 2008-01-02 10:48:20.650 2162995 11796799 11829556 27 2010-03-08 16:45:32.780 2010-04-13 09:08:53.203 11240296 2785291 2818057 32 2007-12-03 13:18:03.697 2008-01-02 10:03:41.677 2162995 2785292 2818058 33 2007-12-03 13:18:03.697 2008-01-02 10:16:06.733 2162995 5832839 5865601 2 2008-07-21 11:06:21.957 2008-07-23 09:37:20.097 5832828 5832835 5865597 1 2008-07-21 11:06:21.957 2008-07-21 11:06:21.957 5832828 5832836 5865598 1 2008-07-21 11:06:21.957 2008-07-21 11:06:21.957 5832828 5832838 5865600 2 2008-07-21 11:06:21.957 2008-07-23 09:37:20.097 5832828 2785288 2818055 31 2007-12-03 13:18:03.697 2007-12-21 14:14:04.080 2162995 11240282 11273022 4 2010-03-05 11:53:11.113 2010-03-05 12:08:19.193 11240274 11240280 11273020 3 2010-03-05 11:53:11.113 2010-03-05 12:04:25.907 11240274 10460982 7176201 2009-09-24 14:45:44.577 2009-09-24 14:45:44.577 11240278 11273018 2 2010-03-05 11:53:11.113 2010-03-05 12:01:50.370 11240274 10460983 7176201 2009-09-24 14:45:44.577 2009-09-24 14:45:44.577 10912086 10944846 30 2009-10-08 12:05:43.910 2009-11-11 10:22:38.997 10356471 11240276 11273016 1 2010-03-05 11:53:11.113 2010-03-05 11:53:11.113 11240274 11240288 11273028 7 2010-03-05 11:53:11.113 2010-03-05 12:21:37.783 11240274 11240286 11273026 6 2010-03-05 11:53:11.113 2010-03-05 12:18:44.443 11240274 11240284 11273024 5 2010-03-05 11:53:11.113 2010-03-05 12:11:09.200 11240274 10912104 10944864 34 2009-10-08 12:05:43.910 2009-11-18 11:21:03.660 10356471 11240294 11273034 95 2009-01-06 09:56:05.890 2010-01-29 15:25:34.123 8355883 10912099 10944859 31 2009-10-08 12:05:43.910 2009-11-13 13:01:36.950 10356471 10912102 10944862 33 2009-10-08 12:05:43.910 2009-11-18 11:20:13.000 10356471 5832868 5865629 35 2008-05-12 09:51:47.077 2008-07-08 11:54:57.200 3638030 10912101 10944861 32 2009-10-08 12:05:43.910 2009-11-18 11:13:13.127 10356471 10911979 10944742 88 2009-01-06 09:56:05.890 2009-11-05 10:49:56.300 8355883 10911983 10944746 1 2009-11-05 10:52:22.817 2009-11-05 10:52:22.817 10911981 10911990 10944752 4 2009-11-05 10:52:22.817 2009-11-05 11:09:31.217 10911981 10911987 10944749 2 2009-11-05 10:52:22.817 2009-11-05 11:01:53.470 10911981 10911988 10944750 3 2009-11-05 10:52:22.817 2009-11-05 11:09:12.703 10911981 10911993 10944755 6 2009-11-05 10:52:22.817 2009-11-05 11:23:40.310 10911981 16253006 16220240 5374520 5407255 57 2008-04-14 16:11:58.510 2008-06-17 10:48:20.320 3637286 10911991 10944753 5 2009-11-05 10:52:22.817 2009-11-05 11:23:20.960 10911981 19137807 15631441 2012-04-10 11:10:09.417 2012-04-10 11:10:09.417 19137806 15631441 2012-04-10 11:10:09.417 2012-04-10 11:10:09.417 5374526 5407261 58 2008-04-14 16:11:58.510 2008-06-25 16:48:32.277 3637286 16253017 16220251 10911997 10944759 8 2009-11-05 10:52:22.817 2009-11-05 11:33:37.087 10911981 19137805 15631441 2012-04-10 11:10:09.417 2012-04-10 11:10:09.417 19137804 15631441 2012-04-10 11:10:09.417 2012-04-10 11:10:09.417 10911995 10944757 7 2009-11-05 10:52:22.817 2009-11-05 11:27:03.527 10911981 10912002 10944764 11 2009-11-05 10:52:22.817 2009-11-05 12:35:37.530 10911981 10912001 10944763 10 2009-11-05 10:52:22.817 2009-11-05 12:34:02.793 10911981 5374527 5407262 59 2008-04-14 16:11:58.510 2008-06-25 17:09:27.883 3637286 10911999 10944761 9 2009-11-05 10:52:22.817 2009-11-05 12:26:36.417 10911981 10912006 10944768 13 2009-11-05 10:52:22.817 2009-11-05 12:58:40.597 10911981 19071809 19039049 10912004 10944766 12 2009-11-05 10:52:22.817 2009-11-05 12:36:12.290 10911981 10912010 10944772 20 2009-10-08 12:05:43.910 2009-11-04 17:24:10.447 10356471 10912008 10944770 14 2009-11-05 10:52:22.817 2009-11-05 13:05:02.213 10911981 10356479 10389191 1 2009-10-08 12:07:56.397 2009-10-08 12:07:56.397 10356476 10912012 10944774 21 2009-10-08 12:05:43.910 2009-11-05 14:50:26.057 10356471 10912014 10944776 22 2009-10-08 12:05:43.910 2009-11-05 14:53:12.830 10356471 10912016 10944778 23 2009-10-08 12:05:43.910 2009-11-05 15:02:08.470 10356471 10912018 10944780 24 2009-10-08 12:05:43.910 2009-11-05 15:03:30.140 10356471 21434738 8355849 2013-08-03 11:27:03.337 2013-08-03 11:27:03.337 10912019 10944781 25 2009-10-08 12:05:43.910 2009-11-05 15:13:38.923 10356471 5832916 5865677 18 2008-04-09 12:55:07.147 2008-07-21 11:01:30.987 3114599 2195759 "Downloads">"2.1 Releases">"2.1.1" # I then clicked on alfresco-enterprise-tomcat-2.1.1.zip to download the zip file. # Went to [http://customers.alfresco.com] (I was still logged in) # Went to "Company Home">"Downloads">"2.1 Releases">"2.1.1">"License Files" # I went ahead and downloaded all the "*.lic" files, but I think I only need enterprise-network-customer-unlimited.lic" # Logged out of Alfresco. # Since I suspect I will need a JDBC driver for SQLServer, I downloaded the jTDS-1.2.2 driver from the jtds web site (just Google jtds and go to the download section of the top google return). # I closed the Firefox browser. # I extracted the jtds-1.2.2.jar file from the jtds download # I downloaded and installed the JRockit 6 R27.4 JDK Microsoft Windows (x86 - 32 bit) from BEA's web site {note} After installing JRockit, make sure you set the JAVA_HOME environment variable to point to the installation of JRockit. For example, I went to the desktop, right clicked on the computer, did Properties, then clicked on the Advanced tab, then click on the environment variables button and then created a new system variable named JAVA_HOME and set to c:\bin\Java\jrockit-R27.4.0-jdk1.6.0_02 {note} # I ran the installer, changed the "Program Files" to "bin" in the installation directory for both the JDK and the JRE. I also chose to install the JRE as public. # Using Firefox, I downloaded the PHP 5.2.5 Windows Installer from php.net and installed it. Although I installed it, I did not integrate it with a web server as I want Alfresco to take port 80. I probably did not need to install PHP, but I thought I would anyway. (again, I changed install path from "Program Files" to "bin" # I also downloaded and installed OpenOffice and ran it once so I could get through the initial startup # I setup a Alfresco database on the server Solstice and granted the LAGOON\DB_Collaboration account to be the db_owner of the Alfresco database. # I unzipped the alfresco tomcat zip file to an alfresco directory in c:\bin # I then went to the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions directory for the customization of the server. ## I edited the custom-repository.properties file ### Changed the dir.root and dir.indexes to look like: {noformat} dir.root=//tornado.shore.mbari.org/Alfresco/alf_data dir.indexes=d:/alf_data/lucene-indexes {noformat} ### Commented out the db.* lines for the HSQL Connection (db.driver and db.url) ### Uncommented the db.* lines for MSSQL and changed to use the jTDS driver. They should look like: {noformat} db.driver=net.sourceforge.jtds.jdbc.Driver db.url=jdbc:jtds:sqlserver://solstice.shore.mbari.org/Alfresco;domain=SHORE;user=DB_Collaboration;password=XXXXXXXXX {noformat} ### I also added the following section to override the mail server settings {noformat} # Mail server configuration mail.host=mail.mbari.org mail.port=25 mail.username= mail.password= {noformat} ## Edited the custom-hibernate-dialect.properties file ### Commented out the HSQL Dialect ### Uncommented the MSSQL Dialect # I then installed the jtds-1.2.2.jar in the c:\bin\alfresco\tomcat\common\lib so that it will be on the classpath when Alfresco is started # Now this is not necessarily fun, but in order to really get it configured the way we want it, you need to pull the original .war file out, edit some stuff inside and re-create the .war. {note} This should all be done before starting Alfresco for the first time. {note} # Copy the c:\Alfresco\tomcat\webapps\alfresco.war file to your home directory. # Make a second copy so that you will always the original (I copied to alfresco.war.orig and moved it somewhere else. It is important to move it and have only the alfresco.war file in the directory because when you un-jar it, all the files go right where alfresco.war is.) # From a command line, un-jar the war file using: {noformat} jar -xvf alfresco.war {noformat} # This unpacks a lot of files and after it completes, move (or delete) the alfresco.war file from the directory. This needs to be done so it does not end up in the new .war file. # I wanted to change the "Company Home" that seems to be everywhere to something that says MBARI. ## Edited ./WEB-INF/classes/alfresco/messages/webclient.properties and changed company_home from 'Company Home' to 'MBARI' ## Edited ./WEB-INF/classes/alfresco/messages/webclient_en_US.properties and changed company_home from 'Company Home' to 'MBARI' ## I edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces.properties and changed the first two lines to read {noformat} spaces.company_home.name=MBARI spaces.company_home.description=The root space for MBARI {noformat} ## Edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces_en_US.properties and made the same changes as the previous step {tip} This took a bit to find all these, and to be honest, I am not sure which one actually made the change on the GUI, but I suspect it was the _en_US ones. {tip} # When users are imported via LDAP, user spaces get created automatically. In order to put them where I wanted them to go (instead of right in the Company Home), I edited the ./WEB-INF/classes/alfresco/authentication-services-context.xml file. In the file there is a bean with an name of personalHomeFolderProvider. There is a property name 'path' and I added {noformat} /${spaces.user_homes.childname} {noformat} to the end to try to get them to create the user spaces there instead of in the Company Home. The final bean XML looks like: {noformat} /${spaces.company_home.childname}/${spaces.user_homes.childname} ${spaces.store} false All All {noformat} # I wanted to change the logo that is used. I attached the replacement logo [CLT:here|^AlfrescoLogo32.png]. Copy this to ./images/logo and overwrite the one that is there. # In order to setup SSL for the application (will do that later), edit ./WEB-INF/web.xml and add the following {noformat} Login Pages /* CONFIDENTIAL {noformat} right before the ending tag at the bottom of the file. # Now in order to change the default behavior so that all content is versioned from the start, I edited the .\WEB-INF\classes\alfresco\model\contentModel.xml and searched for the content type definition block. {noformat} Content cm:cmobject true d:content false true false true {noformat} and added the following block right before the ending tag: {noformat} cm:versionable {noformat} so the final block looks like: {noformat} Content cm:cmobject true d:content false true false true cm:versionable {noformat} # Lastly, I wanted to redirect the log files to a separate disk. This is done because in the Windows hardening process, most of the disk space ends up on drive D: where alfresco does not live. The log files quickly fill up the small C: drive. To to this, I edited the .\WEB-INF\classes\log4j.properties and changed the log file appender location to point to a directory that was created on the D: drive called D:/alf_logs. # That takes care of all the changes to the WAR file. We can now put it back into .war form. # While you are in the directory you expanded the war file in, run ## jar cvfm alfresco.war META-INF\MANIFEST.MF . # You should now have an alfresco.war file in the directory. Move that back to the alfresco install and overwrite the existing one. # Most users like the details view, so I set the default to that by editing c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions\web-client-config-custom.xml and added: {noformat} details 20
20
20 {noformat} right before the closing tag. # Now in order to use MBARI accounts, NTLM authentication was turned on and then chained with the native Alfresco accounts so that we could have non-MBARI accounts on the Alfresco server. ## In order to enable NTLM and native Alfresco authentication, I had to edit two files. For simplicity I have just attached them here and they can be downloaded and installed in the extensions directory. ### The first file is the [CLT:ntlm-authentication-context.xml|^ntlm-authentication-context.xml] file. This configures and enables NTLM authentication. ### The next file was the [CLT:chaining-authentication-context.xml|^chaining-authentication-context.xml] file which enabled Alfresco authentication and chained it together with the NTLM authentication from the previous file. # Then in order to setup CIFS on the server, I edited the file-servers-custom.xml file to look like the attached [CLT:file-servers-custom.xml|^file-servers-custom.xml] file. # In order to grant certain accounts admin privs, I created a new custom-authority-services-context.xml in the same directory as the ldap-authentication-context.xml file and added {noformat} kgomes admin administrator {noformat} # In order for Alfresco to handle all port 80 traffic, I changed Tomcat so that it takes port 80 and SSL goes over port 443. So I edited the c:\Alfresco\tomcat\conf\server.xml file and changed the 8080 port to 80 and the 8443 port to 443 (the 443 change is done in two places). # Now I needed to setup the SSL for the web traffic. Cathy Sewell was instrumental in getting this working. She ordered a new certificate specifically for alfresco and put it in the c:\local\cert folder. Here are the instructions for what she did to get the certficate installed. {noformat} SSL certificate for server Alfresco - 1/2/08 C:\bin\Java\jrockit-R27.1.0-jre1.6.0_02\bin>keytool -genkey -alias tomcat -keyalg RSA -keystore tomcat.keystore What is your first and last name? [alfresco.mbari.org]: What is the name of your organizational unit? [IS]: What is the name of your organization? [MBARI]: What is the name of your City or Locality? [Moss Landing]: What is the name of your State or Province? [CD]: CA What is the two-letter country code for this unit? [US]: Is CN=alfresco.mbari.org, OU=IS, O=MBARI, L=Moss Landing, ST=CA, C=US correct? [no]: y Enter key password for (RETURN if same as keystore password): C:\bin\Java\jrockit-R27.4.0-jre1.6.0_02\bin>keytool -certreq -keyalg RSA -alias tomcat -file certreq.csr -keystore tomcat.keystore Enter keystore password: Generated certificate request file, certreq.csr, was submitted to SSL provider. Certificate provider sent certificate file (alfresco.mbari.org.crt), along with gd_bundle.crt, gd_cross_intermediate.crt, and gd_intermediate.crt. Additionally, I downloaded valicert_class2_root.cer from their website. These files were stored in c:\local\cert. The following commands were used to add them to the tomcat keystore: C:\bin\Java\jrockit-R27.4.0-jre1.6.0_02\bin>keytool -import -alias root -keystore tomcat.keystore -trustcacerts -file c:\local\cert\valicert_class2_root.cer Enter keystore password: Certificate already exists in system-wide CA keystore under alias Do you still want to add it to your own keystore? [no]: y Certificate was added to keystore C:\bin\Java\jrockit-R27.4.0-jre1.6.0_02\bin>keytool -import -alias cross -keystore tomcat.keystore -trustcacerts -file c:\local\cert\gd_cross_intermediate.crt Enter keystore password: Certificate was added to keystore C:\bin\Java\jrockit-R27.4.0-jre1.6.0_02\bin>keytool -import -alias intermed -keystore tomcat.keystore -trustcacerts -file c:\local\cert\gd_intermediate.crt Enter keystore password: Certificate was added to keystore C:\bin\Java\jrockit-R27.4.0-jre1.6.0_02\bin>keytool -import -alias tomcat -keystore tomcat.keystore -trustcacerts -file c:\local\cert\alfresco.mbari.org.crt Enter keystore password: Certificate reply was installed in keystore {noformat} # I edited the c:\bin\alfresco\tomcat\conf\server.xml file and uncommented the SSL section and edited to look like that shown below. {noformat} {noformat} # Since I was in the server.xml file, I went ahead and changed it so that the default webapp was alfresco so that you would get alfresco anytime you went to the base URL. I did this by adding: {noformat} {noformat} as the last line of the tag section (right before the closing tag). {note} You will also notice the Valve tag that I had to add to turn off proxy cache disabling so that IE clients would work correctly over SSL. Gotta love M$. {note} # I copied the enterprise-network-unlimited.lic file into the c:\Alfresco\tomcat\shared\classes\alfresco\extensions\license directory # Just to keep things clean, I edited the c:\bin\alfresco\alfresco.bat file and put 'rem' in front of the second JAVA_OPTS set as I am using Java 6. # Now after you run it for the first time and the database structure gets created, you can't restart it because you get: {noformat} java.sql.SQLException: Column names in each table must be unique. Column name 'ID_' in table 'JBPM_ACTION' is specified more than once. {noformat} Sigh, so in order to keep Alfresco from hurting itself, I had to turn off the schema updates. This is done by editing the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions\custom-repository.properties and adding the following: {noformat} db.schema.update=false {noformat} and then restarting alfresco. # To install Alfresco as a Windows Service use a command prompt and enter the following: {noformat} cd c:\bin\alfresco\tomcat\bin service.bat install alfresco tomcat5.exe //US//alfresco --DisplayName "Alfresco Server" tomcat5.exe //US//alfresco --JvmMs=512 --JvmMx=1024 --JvmSs=64 tomcat5.exe //US//alfresco --JavaHome=c:/bin/Java/jrockit-R27.4.0-jdk1.6.0_02 tomcat5.exe //US//alfresco --Environment ALF_HOME=c:/bin/alfresco/ tomcat5.exe //US//alfresco --Environment PATH=c:/bin/alfresco/bin;%PATH% tomcat5.exe //US//alfresco --StartPath c:/bin/alfresco --Startup auto {noformat} {note:title=JRockit Dump Size} As Alfresco was running, we noticed JRockit was occasionally creating these HUGE dump files that would fill up the hard drive. I turned this "feature" off by running tomcat5w.exe and in the popup GUI, I added a Java command line option: -XXdumpSize:none to turn off the dump files. {note} # To uninstall the service, at a later time, do the following: {noformat} cd c:\bin\alfresco\tomcat\bin service.bat uninstall alfresco {noformat} # To edit your service settings at any time: {noformat} cd c:\alfresco\tomcat\bin tomcat5w.exe //ES//alfresco {noformat} {warning} These next couple of steps had to be taken to install a patch from Alfresco for an issue with bulk uploads I was having. Essentially when file and path structures get really long and nasty, Alfresco was throwing an error and bailing out. This patch (two Java classes) fixed that issue. {warning} # Next, I downloaded the attached [CLT:JAR|^act2139.jar] file and copied it to the c:\bin\alfresco\tomcat\webapps\alfresco\WEB-INF\classes directory. # I shutdown Alfresco and then unjarred the file to install the new classes. They are: ## org/alfresco/filesys/smb/server/SMBSrvPacket.class ## org/alfresco/filesys/util/DataBuffer.class # I would assume since they do not overwrite anything, that this location is further up in the class loader and so it will load these new classes first. # I deleted the act2139.jar file and the META-INF directory that the unjarring process created. # In order to install certain modules (like the email listener), I had to get the Alfresco Module Manager from the customers.alfresco.com download site. I downloaded the alfresco-mmt-2.1.1.jar file locally so I could use it to install modules. # I then downloaded the email listener module from [http://forge.alfresco.com/projects/email-listener/]. It came as a zip file, so I unzipped it and it created a folder with the appropriate emailListener.amp in it. # Make another backup copy of the alfresco.war file and put somewhere in case you want to roll this back. # Open a command prompt windows and cd to the location where the Alfresco Module Manager jar is. # Run the following: {noformat} java -jar alfresco-mmt-2.1.1.jar path_to_emailListener.amp path_to_alfresco.war {noformat} So for me this looked like: {noformat} java -jar alfresco-mmt-2.1.1.jar .\email-listener_2.1RC2\emailListener.amp c:\bin\alfresco\tomcat\webapps\alfresco.war {noformat} # You should be able to verify the install by running: {noformat} java -jar alfresco-mmt-2.1.1.jar list c:\bin\alfresco\tomcat\webapps\alfresco.war {noformat} and you should see something like: {noformat} Module 'emailListener' installed in 'c:\bin\alfresco\tomcat\webapps\alfresco.war' - Title: EmailListener - Version: 2.1 - Install Date: Fri Dec 07 08:43:10 PST 2007 - Desription: EmailListener Module {noformat} # Finally, to start the service, just go into your Windows Service control panel and locate the service that is now named 'Alfresco Server'. You can start and stop Alfresco from this control panel. {note:title=Database Migrations} For the alfresco.mbari.org installation, we moved the back end database a couple of times for performance and management reasons. The first move was to backup the database from solstice.shore.mbari.org to the SQL 2005 server called capricorn. We did this because 2005 was the officially supported DB and we were experiencing some strange issues. It ran fine on capricorn for a long while, but for licensing reasons, we wanted to consolidate the DB onto a newer SQL Server 2008 machine called equinox.shore.mbari.org. In order to point Alfresco at a different database, I edited the custom-repository.properties file located in the {noformat}c:\bin\alfresco\tomcat\shared\classes\alfresco\extension{noformat} directory. Here is what the final result looked like with the previous two configurations commented out. {noformat} # # SQLServer connection (requires jtds-1.2.jar or equivalent - http://jtds.sourceforge.net/) # db.driver=net.sourceforge.jtds.jdbc.Driver # DB on Solstice #db.url=jdbc:jtds:sqlserver://solstice.shore.mbari.org/Alfresco;domain=SHORE;user=DB_Collaboration;password=xxxxxx # DB on capricorn #db.url=jdbc:jtds:sqlserver://capricorn.shore.mbari.org/Alfresco;domain=SHORE;user=DB_Collaboration;password=xxxxxx # DB on equinox db.url=jdbc:jtds:sqlserver://equinox.shore.mbari.org/Alfresco;domain=SHORE;user=DB_Collaboration;password=xxxxxx {noformat} I also downloaded the most recent jtds driver (1.2.5) and installed it in the c:\bin\alfresco\tomcat\common\lib directory and removed the old version. {note} h1. Content Migration Now, in order to migrate content from old alfresco and normal file structures, I did the following: h3. For content already in alfresco: # Navigate to the space whose contents you want to migrate. For example, let's say I want to migrate the stuff from my personal space. I would navigate (using the WebUI) to the /MBARI/User Homes/kgomes space. You should see the contents of the kgomes folder from this view. # Click on 'More actions->View Details'. # On the right hand side, click on 'Export'. # For package name, I usually enter the space name followed by '_export', but it doesn't really matter. # Click on the link that says 'Click here to select the destination' and select somewhere that you will be able to download the .acp file from. # Select 'Current Space'. # Select 'Include Children'. # Uncheck 'Include this space' unless you have content (documents) in this specific folder (anything other than folders) that you want to migrate. This is a bit tricky, but there are two ways to do this. If you want to have the top level folder created, use the 'Include this space' and that will create the top level folder. Otherwise, if will expand into the folder in which you import the .acp file into. This is important in cases where the folder has already been created for you (like with user homes) and you have to migrate content into that folder. If you have the option to create the top level directory, by all means do so. # Uncheck 'Export in background' so you can force it to happen and you know when it is complete.]]> 2162995 10912022 10944784 26 2009-10-08 12:05:43.910 2009-11-06 20:19:49.103 10356471 5832919 5865680 19 2008-04-09 12:55:07.147 2008-08-04 13:32:09.017 3114599 18284613 18251845 10356472 10389184 82 2009-01-06 09:56:05.890 2009-10-08 11:59:53.967 8355883 10356474 10389186 83 2009-01-06 09:56:05.890 2009-10-08 12:06:04.700 8355883 10356473 10389185 1 2009-10-08 12:05:43.910 2009-10-08 12:05:43.910 10356471 10356467 10389179 80 2009-01-06 09:56:05.890 2009-09-24 14:59:12.273 8355883 10356469 10389181 81 2009-01-06 09:56:05.890 2009-10-08 11:58:39.810 8355883 3604651 1 3637859 2008-05-07 07:49:15.067 2008-05-07 07:49:15.067 10911943 10944706 18 2009-10-08 12:05:43.910 2009-11-04 14:42:42.947 10356471 19168587 19040991 2012-11-15 12:58:23.697 2012-11-15 12:58:23.697 3604650 1 3637859 2008-05-06 16:49:15.017 2008-05-06 16:49:15.017 10911944 10944707 19 2009-10-08 12:05:43.910 2009-11-04 17:23:41.940 10356471 19168586 19040991 2012-11-15 12:58:23.697 2012-11-15 12:58:23.697 19168585 19040991 2012-11-15 12:58:23.697 2012-11-15 12:58:23.697 19168584 19040991 2012-11-15 12:58:23.697 2012-11-15 12:58:23.697 10911946 10944709 16 2009-10-08 12:07:56.397 2009-11-04 17:13:22.063 10356476 19168583 19040991 2012-11-15 12:58:23.697 2012-11-15 12:58:23.697 10911939 10944702 13 2009-10-08 12:07:56.397 2009-11-04 16:58:33.633 10356476 19168582 19040991 2012-11-15 12:58:23.697 2012-11-15 12:58:23.697 10911940 10944703 14 2009-10-08 12:07:56.397 2009-11-04 16:59:58.967 10356476 19168581 19040991 2012-11-15 12:58:23.697 2012-11-15 12:58:23.697 19168580 19040991 2012-11-15 12:58:23.697 2012-11-15 12:58:23.697 10911942 10944705 15 2009-10-08 12:07:56.397 2009-11-04 17:02:25.100 10356476 19530021 19041349 2012-11-28 09:38:28.173 2012-11-28 09:38:28.173 19168595 19040991 2012-11-15 12:58:23.697 2012-11-15 12:58:23.697 10911935 10944698 11 2009-10-08 12:07:56.397 2009-11-04 16:46:52.290 10356476 19530020 19041349 2012-11-28 09:38:28.173 2012-11-28 09:38:28.173 19168594 19040991 2012-11-15 12:58:23.697 2012-11-15 12:58:23.697 19168593 19040991 2012-11-15 12:58:23.697 2012-11-15 12:58:23.697 10911937 10944700 12 2009-10-08 12:07:56.397 2009-11-04 16:52:55.347 10356476 19168592 19040991 2012-11-15 12:58:23.697 2012-11-15 12:58:23.697 19168591 19040991 2012-11-15 12:58:23.697 2012-11-15 12:58:23.697 19168590 19040991 2012-11-15 12:58:23.697 2012-11-15 12:58:23.697 10911932 10944695 9 2009-10-08 12:07:56.397 2009-11-04 16:41:03.390 10356476 19168589 19040991 2012-11-15 12:58:23.697 2012-11-15 12:58:23.697 10911933 10944696 10 2009-10-08 12:07:56.397 2009-11-04 16:46:23.313 10356476 19168588 19040991 2012-11-15 12:58:23.697 2012-11-15 12:58:23.697 19168570 19040991 2012-11-15 12:58:23.697 2012-11-15 12:58:23.697 10911928 10944691 7 2009-10-08 12:07:56.397 2009-11-04 16:34:45.810 10356476 19530013 19041349 2012-11-28 09:38:28.173 2012-11-28 09:38:28.173 19168571 19040991 2012-11-15 12:58:23.697 2012-11-15 12:58:23.697 10911927 10944690 6 2009-10-08 12:07:56.397 2009-11-04 16:30:54.550 10356476 19530014 19041349 2012-11-28 09:38:28.173 2012-11-28 09:38:28.173 19168568 19040991 2012-11-15 12:58:23.697 2012-11-15 12:58:23.697 10911930 10944693 8 2009-10-08 12:07:56.397 2009-11-04 16:35:26.563 10356476 19530015 19041349 2012-11-28 09:38:28.173 2012-11-28 09:38:28.173 19168569 19040991 2012-11-15 12:58:23.697 2012-11-15 12:58:23.697 19530016 19041349 2012-11-28 09:38:28.173 2012-11-28 09:38:28.173 10460887 5832828 2009-09-24 14:42:42.547 2009-09-24 14:42:42.547 19168566 19040991 2012-11-15 12:58:23.697 2012-11-15 12:58:23.697 19530017 19041349 2012-11-28 09:38:28.173 2012-11-28 09:38:28.173 10460886 5832828 2009-09-24 14:42:42.547 2009-09-24 14:42:42.547 19168567 19040991 2012-11-15 12:58:23.697 2012-11-15 12:58:23.697 10911923 10944686 4 2009-10-08 12:07:56.397 2009-11-04 16:11:47.860 10356476 19530018 19041349 2012-11-28 09:38:28.173 2012-11-28 09:38:28.173 10460885 5832828 2009-09-24 14:42:42.547 2009-09-24 14:42:42.547 19168564 19040991 2012-11-15 12:58:23.697 2012-11-15 12:58:23.697 19530019 19041349 2012-11-28 09:38:28.173 2012-11-28 09:38:28.173 10460884 5832828 2009-09-24 14:42:42.547 2009-09-24 14:42:42.547 19168565 19040991 2012-11-15 12:58:23.697 2012-11-15 12:58:23.697 10911925 10944688 5 2009-10-08 12:07:56.397 2009-11-04 16:18:14.563 10356476 19168578 19040991 2012-11-15 12:58:23.697 2012-11-15 12:58:23.697 19168579 19040991 2012-11-15 12:58:23.697 2012-11-15 12:58:23.697 10911919 10944682 2 2009-10-08 12:07:56.397 2009-10-09 15:48:07.807 10356476 3604644 1 3637556 2008-05-06 16:21:15.023 2008-05-06 16:21:15.023 19168576 19040991 2012-11-15 12:58:23.697 2012-11-15 12:58:23.697 3604645 1 3637556 2008-05-06 16:22:15.023 2008-05-06 16:22:15.023 19168577 19040991 2012-11-15 12:58:23.697 2012-11-15 12:58:23.697 10911921 10944684 3 2009-10-08 12:07:56.397 2009-11-04 16:09:06.320 10356476 10911916 10944679 16 2009-10-08 12:05:43.910 2009-11-04 14:40:26.080 10356471 19168574 19040991 2012-11-15 12:58:23.697 2012-11-15 12:58:23.697 19168575 19040991 2012-11-15 12:58:23.697 2012-11-15 12:58:23.697 18284982 18252222 3604648 2 3114599 2008-05-06 16:32:15.040 2008-05-21 15:16:15.027 19168572 19040991 2012-11-15 12:58:23.697 2012-11-15 12:58:23.697 3604649 1 3637859 2008-05-06 16:39:15.027 2008-05-06 16:39:15.027 10911917 10944680 17 2009-10-08 12:05:43.910 2009-11-04 14:41:39.557 10356471 19168573 19040991 2012-11-15 12:58:23.697 2012-11-15 12:58:23.697 10911977 10944740 4 2009-09-18 12:04:09.600 2009-09-24 13:57:16.317 10356237 11796708 11829465 26 2010-03-08 16:45:32.780 2010-04-13 09:04:26.440 11240296 10911976 10944739 87 2009-01-06 09:56:05.890 2009-11-05 10:48:23.250 8355883 10911973 10944736 85 2009-01-06 09:56:05.890 2009-11-05 10:46:37.580 8355883 10911974 10944737 86 2009-01-06 09:56:05.890 2009-11-05 10:47:52.233 8355883 10911971 10944734 84 2009-01-06 09:56:05.890 2009-10-08 12:07:11.377 8355883 11796699 11829457 22 2010-03-08 16:45:32.780 2010-03-09 19:13:19.260 11240296 25067522 25100290 1 2013-08-03 11:21:10.280 2013-08-03 11:21:10.280 21365729 10911970 10944733 28 2009-10-08 12:07:56.397 2009-11-05 09:57:16.300 10356476 11796701 11829459 23 2010-03-08 16:45:32.780 2010-04-13 09:01:48.703 11240296 10460883 5832828 2009-09-24 14:42:42.547 2009-09-24 14:42:42.547 10911968 10944731 27 2009-10-08 12:07:56.397 2009-11-05 09:56:14.607 10356476 3604697 1 3114599 2008-05-16 13:51:15.047 2008-05-16 13:51:15.047 3604696 6 3638030 2008-05-16 13:50:15.037 2008-05-27 13:51:15.130 10911966 10944729 26 2009-10-08 12:07:56.397 2009-11-05 09:53:50.563 10356476 11796705 11829462 24 2010-03-08 16:45:32.780 2010-04-13 09:02:59.080 11240296 10911963 10944726 24 2009-10-08 12:07:56.397 2009-11-05 09:47:32.837 10356476 11796706 11829463 25 2010-03-08 16:45:32.780 2010-04-13 09:04:07.120 11240296 10911964 10944727 25 2009-10-08 12:07:56.397 2009-11-05 09:52:40.383 10356476 19168600 19040991 2012-11-15 12:58:23.697 2012-11-15 12:58:23.697 19168601 19040991 2012-11-15 12:58:23.697 2012-11-15 12:58:23.697 10911961 10944724 23 2009-10-08 12:07:56.397 2009-11-05 09:32:31.090 10356476 10911960 10944723 22 2009-10-08 12:07:56.397 2009-11-05 09:26:20.073 10356476 19168596 19040991 2012-11-15 12:58:23.697 2012-11-15 12:58:23.697 10911958 10944721 21 2009-10-08 12:07:56.397 2009-11-05 09:15:09.887 10356476 19168597 19040991 2012-11-15 12:58:23.697 2012-11-15 12:58:23.697 19168598 19040991 2012-11-15 12:58:23.697 2012-11-15 12:58:23.697 10911956 10944719 20 2009-10-08 12:07:56.397 2009-11-05 09:02:32.487 10356476 19168599 19040991 2012-11-15 12:58:23.697 2012-11-15 12:58:23.697 3604676 15 3638030 2008-05-12 09:53:15.037 2008-05-29 12:27:15.057 10911954 10944717 19 2009-10-08 12:07:56.397 2009-11-05 09:00:59.763 10356476 3604674 3 3637859 2008-05-08 09:46:15.043 2008-06-02 16:46:15.043 10911952 10944715 18 2009-10-08 12:07:56.397 2009-11-05 06:36:37.677 10356476 3604675 1 3638030 2008-05-12 09:52:15.013 2008-05-12 09:52:15.013 10911949 10944712 17 2009-10-08 12:07:56.397 2009-11-04 20:51:48.367 10356476 9831110 9798359 11796611 11829370 98 2009-01-06 09:56:05.890 2010-03-09 19:10:18.280 8355883 11796612 11829371 99 2009-01-06 09:56:05.890 2010-04-01 11:36:57.373 8355883 19038275 19071043 1 2012-03-05 15:47:44.387 2012-03-05 15:47:44.387 18580035 3604698 2 3114599 2008-05-16 13:52:15.017 2008-05-16 13:55:15.027 3604699 3 3114599 2008-05-16 13:52:15.027 2008-05-16 13:55:15.030 9831128 9798378 28083319 21365729 2015-08-21 16:30:52.957 2015-08-21 16:30:52.957 28083318 21365729 2015-08-21 16:30:52.957 2015-08-21 16:30:52.957 28083317 21365729 2015-08-21 16:30:52.957 2015-08-21 16:30:52.957 28083316 21365729 2015-08-21 16:30:52.957 2015-08-21 16:30:52.957 10911909 10944672 12 2009-10-08 12:05:43.910 2009-11-04 14:32:07.973 10356471 19168549 19040991 2012-11-15 12:58:23.697 2012-11-15 12:58:23.697 10911910 10944673 13 2009-10-08 12:05:43.910 2009-11-04 14:32:27.133 10356471 19168548 19040991 2012-11-15 12:58:23.693 2012-11-15 12:58:23.693 10911907 10944670 10 2009-10-08 12:05:43.910 2009-11-04 14:30:28.247 10356471 19168551 19040991 2012-11-15 12:58:23.697 2012-11-15 12:58:23.697 10911908 10944671 11 2009-10-08 12:05:43.910 2009-11-04 14:31:35.090 10356471 19168550 19040991 2012-11-15 12:58:23.697 2012-11-15 12:58:23.697 19168553 19040991 2012-11-15 12:58:23.697 2012-11-15 12:58:23.697 10911914 10944677 15 2009-10-08 12:05:43.910 2009-11-04 14:39:00.790 10356471 19038298 19071065 2 2012-03-05 15:47:44.387 2012-03-19 16:16:51.230 18580035 19168552 19040991 2012-11-15 12:58:23.697 2012-11-15 12:58:23.697 4096010 4 3638030 2008-05-27 13:51:15.080 2008-05-29 12:27:15.047 19168555 19040991 2012-11-15 12:58:23.697 2012-11-15 12:58:23.697 10911912 10944675 14 2009-10-08 12:05:43.910 2009-11-04 14:33:10.283 10356471 19168554 19040991 2012-11-15 12:58:23.697 2012-11-15 12:58:23.697 9831148 9798398 10911901 10944664 8 2009-10-08 12:05:43.910 2009-11-04 13:37:52.610 10356471 19168557 19040991 2012-11-15 12:58:23.697 2012-11-15 12:58:23.697 19168556 19040991 2012-11-15 12:58:23.697 2012-11-15 12:58:23.697 10911899 10944662 7 2009-10-08 12:05:43.910 2009-11-04 13:37:33.787 10356471 19168559 19040991 2012-11-15 12:58:23.697 2012-11-15 12:58:23.697 19168558 19040991 2012-11-15 12:58:23.697 2012-11-15 12:58:23.697 19168561 19040991 2012-11-15 12:58:23.697 2012-11-15 12:58:23.697 19168560 19040991 2012-11-15 12:58:23.697 2012-11-15 12:58:23.697 10911906 10944669 9 2009-10-08 12:05:43.910 2009-11-04 13:38:58.847 10356471 19168563 19040991 2012-11-15 12:58:23.697 2012-11-15 12:58:23.697 19168562 19040991 2012-11-15 12:58:23.697 2012-11-15 12:58:23.697 10460789 10356284 2009-09-24 14:38:07.780 2009-09-24 14:38:07.780 10911898 10944661 6 2009-10-08 12:05:43.910 2009-11-04 13:36:07.810 10356471 10911896 10944659 5 2009-10-08 12:05:43.910 2009-11-04 13:35:05.040 10356471 10911895 10944658 4 2009-10-08 12:05:43.910 2009-10-18 09:13:24.453 10356471 19038302 19071069 4 2012-03-05 15:47:44.387 2012-03-27 11:00:20.153 18580035 19038300 19071067 3 2012-03-05 15:47:44.387 2012-03-27 10:54:47.433 18580035 19168547 19040991 2012-11-15 12:58:23.693 2012-11-15 12:58:23.693 10356300 10389016 33 2008-04-09 12:55:07.147 2009-07-23 10:07:42.123 3114599 10356299 10389015 79 2009-01-06 09:56:05.890 2009-09-24 14:49:18.377 8355883 5374721 5407452 32 2008-05-12 09:51:47.077 2008-07-07 13:26:28.490 3638030 5374716 5407447 31 2008-05-12 09:51:47.077 2008-07-07 13:15:06.270 3638030 5374730 5407460 34 2008-05-12 09:51:47.077 2008-07-08 09:24:37.793 3638030 5374723 5407454 33 2008-05-12 09:51:47.077 2008-07-08 09:18:19.743 3638030 19038344 19071110 51 2007-12-03 13:18:03.697 2012-01-17 10:23:16.260 2162995 5374714 5407445 30 2008-05-12 09:51:47.077 2008-07-02 17:26:39.513 3638030 5374709 5407440 29 2008-05-12 09:51:47.077 2008-07-01 11:00:26.150 3638030 3604512 1 3637286 2008-04-15 15:19:15.017 2008-04-15 15:19:15.017 10356270 10388988 71 2009-01-06 09:56:05.890 2009-09-24 14:27:43.107 8355883 28083305 21365729 2015-08-21 16:30:52.957 2015-08-21 16:30:52.957 28083304 21365729 2015-08-21 16:30:52.957 2015-08-21 16:30:52.957 10356268 10388986 70 2009-01-06 09:56:05.890 2009-09-24 14:23:44.427 8355883 28083307 21365729 2015-08-21 16:30:52.957 2015-08-21 16:30:52.957 28083306 21365729 2015-08-21 16:30:52.957 2015-08-21 16:30:52.957 28083301 21365729 2015-08-21 16:30:52.957 2015-08-21 16:30:52.957 10356273 10388991 4 2009-07-23 10:06:25.403 2009-07-23 10:36:36.977 10355550 28083300 21365729 2015-08-21 16:30:52.957 2015-08-21 16:30:52.957 10356272 10388990 12 2009-01-26 16:30:22.427 2009-02-25 10:55:03.967 8913090 28083303 21365729 2015-08-21 16:30:52.957 2015-08-21 16:30:52.957 10356271 10388989 67 2008-04-14 16:11:58.510 2009-05-29 15:36:18.537 3637286 28083302 21365729 2015-08-21 16:30:52.957 2015-08-21 16:30:52.957 10356278 10388996 73 2009-01-06 09:56:05.890 2009-09-24 14:33:52.213 8355883 28083313 21365729 2015-08-21 16:30:52.957 2015-08-21 16:30:52.957 28083312 21365729 2015-08-21 16:30:52.957 2015-08-21 16:30:52.957 10356277 10388995 4 2009-05-11 10:01:43.157 2009-05-13 14:48:55.267 9798398 28083315 21365729 2015-08-21 16:30:52.957 2015-08-21 16:30:52.957 10356275 10388993 72 2009-01-06 09:56:05.890 2009-09-24 14:30:12.127 8355883 28083314 21365729 2015-08-21 16:30:52.957 2015-08-21 16:30:52.957 10356282 10388999 74 2009-01-06 09:56:05.890 2009-09-24 14:35:52.870 8355883 28083309 21365729 2015-08-21 16:30:52.957 2015-08-21 16:30:52.957 28083308 21365729 2015-08-21 16:30:52.957 2015-08-21 16:30:52.957 28083311 21365729 2015-08-21 16:30:52.957 2015-08-21 16:30:52.957 28083310 21365729 2015-08-21 16:30:52.957 2015-08-21 16:30:52.957 10356285 10389001 1 2008-08-04 13:40:51.173 2008-08-04 13:40:51.173 5832918 5374736 5407466 1 2008-07-08 15:13:10.307 2008-07-08 15:13:10.307 5374734 10356289 10389005 12 2009-03-19 14:46:17.863 2009-04-02 12:27:04.917 9372328 10356290 10389006 9 2008-08-27 13:39:41.480 2008-12-08 09:28:00.473 6259010 5374732 5407462 16 2008-04-09 12:55:07.147 2008-05-12 09:35:51.557 3114599 10356287 10389003 75 2009-01-06 09:56:05.890 2009-09-24 14:37:45.667 8355883 10356288 10389004 3 2008-07-21 11:06:21.957 2008-07-23 12:13:44.340 5832828 10356293 10389009 5 2008-10-29 10:39:30.207 2009-03-23 15:15:07.533 7176201 28083296 21365729 2015-08-21 16:30:52.957 2015-08-21 16:30:52.957 10356294 10389010 77 2009-01-06 09:56:05.890 2009-09-24 14:45:24.370 8355883 28083297 21365729 2015-08-21 16:30:52.957 2015-08-21 16:30:52.957 28083298 21365729 2015-08-21 16:30:52.957 2015-08-21 16:30:52.957 10356291 10389007 2 2008-05-06 16:38:16.753 2008-05-06 16:48:51.923 3637859 10356292 10389008 76 2009-01-06 09:56:05.890 2009-09-24 14:40:35.757 8355883 28083299 21365729 2015-08-21 16:30:52.957 2015-08-21 16:30:52.957 10356297 10389013 78 2009-01-06 09:56:05.890 2009-09-24 14:47:31.383 8355883 10945055 10912300 10356298 10389014 2 2008-07-08 15:13:10.307 2008-07-09 14:49:59.030 5374734 10356295 10389011 38 2008-05-12 09:51:47.077 2008-08-25 14:52:16.770 3638030 10356296 10389012 13 2008-04-23 13:29:35.487 2008-06-02 17:49:36.343 3637556 10356239 10388957 1 2009-09-18 12:04:09.600 2009-09-18 12:04:09.600 10356237 4063241 3113965 2008-05-28 09:24:34.093 2008-06-11 14:03:14.950 3155 2 4063240 3113965 2008-05-28 09:24:21.777 2008-05-28 09:24:21.777 19719 1 10356241 10388959 2 2009-09-18 12:04:09.600 2009-09-18 12:15:43.333 10356237 3604595 1 3637556 2008-04-24 10:24:15.027 2008-04-24 10:24:15.027 4063242 3113965 2008-05-28 10:12:44.120 2008-05-28 10:12:44.120 12158 1 10356235 10388954 68 2009-01-06 09:56:05.890 2009-08-11 16:06:45.513 8355883 3604586 1 3637556 2008-04-23 14:04:15.020 2008-04-23 14:04:15.020 4063235 3638030 2008-05-22 14:50:08.423 2008-05-22 14:50:08.423 3505352 1 3604587 16 3637556 2008-04-23 14:07:15.023 2008-06-02 17:50:15.033 4063234 3638030 2008-05-22 14:30:38.700 2008-05-22 14:30:38.700 176399 1 3604588 11 3637556 2008-04-23 14:15:15.023 2008-06-03 07:36:15.070 3604589 10 3637534 2008-04-23 14:37:15.017 2008-05-21 15:07:15.053 4063236 3638030 2008-05-22 14:50:59.487 2008-05-22 14:50:59.487 815660 1 3604583 3 3114599 2008-04-23 13:27:15.073 2008-04-24 09:08:15.030 3604585 1 3637556 2008-04-23 13:32:15.023 2008-04-23 13:32:15.023 3604584 1 3637556 2008-04-23 13:30:15.020 2008-04-23 13:30:15.020 3604579 21 3637534 2008-04-22 12:30:15.020 2008-05-21 15:14:15.030 3604578 1 3637534 2008-04-22 12:27:15.027 2008-04-22 12:27:15.027 10356263 10388981 29 2008-04-22 12:26:44.157 2009-04-22 13:52:59.907 3637534 10460694 10356280 2009-09-24 14:36:14.407 2009-09-24 14:36:14.407 10356264 10388982 2 2009-01-28 08:09:41.793 2009-01-28 09:15:38.767 8913120 10460695 10356280 2009-09-24 14:36:14.407 2009-09-24 14:36:14.407 10356266 10388984 69 2009-01-06 09:56:05.890 2009-09-18 12:03:45.353 8355883 10460693 10356280 2009-09-24 14:36:14.407 2009-09-24 14:36:14.407 10460696 10356280 2009-09-24 14:36:14.407 2009-09-24 14:36:14.407 10356261 10388979 3 2009-09-18 12:04:09.600 2009-09-18 12:21:39.477 10356237 3604630 2 3114599 2008-04-28 10:27:15.057 2008-05-21 15:14:15.027 5734410 1 3114599 2008-06-23 12:17:15.070 2008-06-23 12:17:15.070 3604629 3 3114599 2008-04-28 09:50:15.037 2008-05-21 15:07:15.077 24117747 24051827 2013-12-04 10:56:57.197 2013-12-04 10:56:57.197 19038429 19071195 15 2011-02-09 06:25:02.520 2011-02-18 15:31:59.417 15631441 24084594 24051827 10911762 10944529 3 2009-10-08 12:05:43.910 2009-10-18 08:23:52.183 10356471 19038431 19071197 16 2011-02-09 06:25:02.520 2012-04-10 11:03:05.653 15631441 10911760 10944527 2 2009-10-08 12:05:43.910 2009-10-08 12:06:04.740 10356471 5734402 1 3637534 2008-06-13 20:28:15.117 2008-06-13 20:28:15.117 5734408 1 3637556 2008-06-22 07:56:15.080 2008-06-22 07:56:15.080 3604605 1 3637286 2008-04-24 11:47:15.023 2008-04-24 11:47:15.023 3113989 3179474 12 2008-03-17 13:05:41.323 2008-03-17 14:39:12.890 3113965 3113987 3179472 11 2008-03-17 13:05:41.323 2008-03-17 14:33:09.440 3113965 15663138 SendBinaryFile" from the Motocross menu and select the file to send (remember to use a temporary file name) - issue Motocross "Send Break" command to end the transfer (CTRL-C may also work) It is preferred to DISABLE line feeds when using Motocross; transfers work correctly and disabling prevents double prompts. Not all versions of Motocross include the required "Transfer>SendBinaryFile" menu item. Version 2.32 has it. Motocross does not support Y-Modem transfer. - It is possible to upload OASIS.CFG at the OASIS prompt or at the PicoDOS prompt. The following notes apply: Uploading using Hyperterm works OK from OASIS> prompt if the "Send Line ends with Line Feeds" is ENABLED. You may later want to disable it to prevent double OASIS prompts. Uploading using Hyperterm works OK from PicoDOS C:\> prompt if the "Send Line ends with Line Feeds" is DISABLED. It will work OK if ENABLED, but will cause double OASIS prompts. It is possible to upload using Hyperterm from the PicoDOS prompt with a 'yr' command. See note above on using reset pico via radio console. ###################### Summary ########################### - use dumb editors - check line ends (using a hex editor) before sending - use Motocross + capture from OASIS prompt - DISABLE "send line ends with line feeds" if using Motocross - ENABLE "send line feeds with line ends" if using HyperTerm - transfer to a temp file name - check line ends (type test) after sending ########################################################### {noformat}]]> 15630373 10460601 9798398 2009-09-24 14:35:18.727 2009-09-24 14:35:18.727 3113982 3179467 8 2008-03-17 13:05:41.323 2008-03-17 13:50:35.573 3113965 3113980 3179465 7 2008-03-17 13:05:41.323 2008-03-17 13:39:08.700 3113965 3113985 3179470 10 2008-03-17 13:05:41.323 2008-03-17 14:32:14.017 3113965 15663129 prompt or in picodos... 4) Craig etal suggest going from picodos with a yr command, but I don't like to because if you forget your connected via radio you may be SOL for 30 minutes because you'll probably kill the radio driver and have to wait for 32 minutes for the hardware to rest(I have not tested that, Im trying at my desk right now...). 5) I prefer to use "capture" command and motocross but you need a version that has the "Transfer>SendBinaryFile" menu item. (eg. v2.32 has it, an older version that Paul found out at sea did not) 6) If you must, you can use hyperterm with the capture command and "Transfer>SendTextFile" but you ***ABSOLUTELY MUST FIRST SET "Send line ends with line feeds" PRIOR TO TRANSMITTING THE FILE*** My tests show that using capture at the oasis prompt with this setting off, causes hyperterm to strip the lf in your cfg file. Then the file on the controller appears as all on one line when typed back. 7) Motocross "send binary file" works from either the picodos or OASIS> capture command (as long as you obey rule #1) In all cases, its "Comm Settings > "Send LF after CR" was un-checked. 8a) Hyperterm works ok from OASIS> prompt IF the "Send Line ends with Line Feeds" is TRUE. (but you may later want to reset it to false so you don't get "Double OASIS> prompts" 8b) Hyperterm works ok from picodos C:\> prompt IF the "Send Line ends with Line Feeds" is FALSE. (also will work ok if TRUE but then you get the double prompt symptom. *************************** THE BOTTOM LINE(S) ***************************** USE dumb editors, check line endings with XVI32 to verify Rule#1 and xfer to a temp file (Rule#2) using MOTOCROSS !!!! (Or only if brave or hardwired to console port, you can use yr from picodos) **************************************************************************** If your forced to deal with an oasis.cfg file that may not have correct line endings even though it looks ok in notepad.... and you have no hex editor to verify... (eg. When you upload the file per recommendations above, it still is all on one line) It seems in my quick testing that you can use notepad to add extra lines at every line and then re-upload...(you will have line endings in hex editor of 0D 0D 0A which still seems to be ok with OASIS>) Curious if anyone else has experiences that differ from above, it would be great to nail this down and cookbook it along with how to recover if you do screw things up...... -Rich If you mistakenly issue the "reset pico" command while connected to the radio port, you will loose contact... The only ways to get it back are to: 1)Bounce the power 2)Wait ~32 minutes for the hardware reset (plus the wait for the radio wakeup procedure) Fortunately in the next release of code (still in testing), Bob added a warning message with a Y/N to remind you your on the radio... (Thanks Bob!) And please correct my last.... re: picodos using yr (ymodem receive...) is from hyperterm (motocross doesn't support ymodem file xfers....) -Rich {noformat} And from Paul: {noformat} Another follow up to this thread... sorry for the overkill. We successfully transferred a new oasis.cfg file to 2010M1 via radio link on Tuesday afternoon. The file was edited with a hex editor to include the correct 0D 0A line terminators. There were places where there were two in a row (0D 0A 0D 0A) but in no cases were there multiple 0Ds before a single 0A as I've run across in some other oasis.cfg files that are floating around (0D 0D 0A). Once the file was edited and double checked, we transferred it according to Rich's procedure in #6 below and detailed here: -Establish link with mooring -At oasis prompt, type "capture [filename] " -Go to HyperTerm properties, 'settings' tab, click 'ascii setup' button, check 'Send line ends with line feeds' button -Go to HyperTerm Transfer menu, and select 'Send Text File...' -Select file to send and wait for file transfer -At oasis prompt, type "^D" to close capture on oasis -Go back to HyperTerm properties and uncheck 'Send line ends with line feeds' -Check file on can to make sure it looks right (at oasis prompt, type "type [filename]") -If all looks correct, rename files (oasis.cfg to [oasis.bk?] and [filename] to oasis.cfg) and reset mooring. -Sacrifice a small animal (or vegetable for the vegetarians) to the mooring gods And finally... -Blame Rich if it doesn't work for you Just wanted to document the successful file transfer over the radio. The mooring came back immediately, and everything appears to be working well. Paul P.s. In #1 below, Rich says that he strongly recommends checking the file in a hex editor. I think this should be an absolute requirement. {noformat} From Paul again: {noformat} A couple of notes regarding the oasis.cfg file issue from Wednesday's deployment: First off, we were NOT able to modify the config file with the new pCO2 constants before it was deployed... Attempts to transfer the new file to the controller on the buoy did not appear to work, and looked (for about ten minutes there) like it corrupted the entire oasis directory. Due to past issues of corrupting the oasis controller with bad oasis.cfg files, and the above scare that the oasis directory was destroyed while on the way out to deploy the buoy, I was unwilling to continue attempting to get a file across to the controller. So unfortunately the constants are not correct for the pCO2 that is on the buoy. Secondly, the config file needs to be in its deployment form at the time the oasis can is closed!! Because there are some idiosyncrasies with this file transfer, having it on the bench gives plenty of time to recover if there is an issue. As of a week before deployment, the entire systems should ideally be hands off, and this definitely needs to be the case for all software/firmware on the can. Further bench testing (Thanks Rich!!) has shown that we may have nailed down the problem with the file transfer, but until additional testing shows that we can reliably do this over the radio on the buoy, no changes should be made after the can is closed. Some pCO2 specific thoughts: I know it's been this way for a long time (forever?), but why are the pCO2 constants contained in the oasis.cfg file? This is the only instrument-specific information contained in the oasis.cfg file (other than driver info); what would we need to do to bring them out? Ideally we would have them on shore for post processing, but if they need to absolutely be on the buoy, can they be in a separate file (pCO2.cfg maybe)? Maybe have a line in the oasis.cfg that would point to the pCO2 config file? With this information no longer in the oasis.cfg file, there is not the same danger of hanging the entire buoy if the file becomes corrupt in the transfer. It will also allow us to change the pCO2 constants if the instrument ever needs to be swapped in the field. I'm sure this has been considered before... I've either forgotten the answer, or wasn't in on the discussion. Apologies if I'm digging up old info. Thanks, Paul {noformat} And from Bob: {noformat} On another note, if we can *ever* get up to speed with the most current checked-in code, (that is, if we can switch to the new radios and wire protocol), it's worth noting that this new code also has some line editing features. They've turned out to be extremely useful for the respirometers, which are based on Oasis and where the line editor commands originated. Allows you to add, delete, and comment-out lines in OASIS.CFG in situ, which greatly reduces the need for transferring files. -Bob {noformat}]]> 15630363 3113983 3179468 9 2008-03-17 13:05:41.323 2008-03-17 14:17:00.600 3113965 3113974 3179459 5 2008-03-17 13:05:41.323 2008-03-17 13:21:39.227 3113965 3113972 3179457 4 2008-03-17 13:05:41.323 2008-03-17 13:18:23.847 3113965 28213258 28246026 1 2015-08-26 12:01:56.270 2015-08-26 12:01:56.270 28213255 28213257 28246025 237 2009-01-06 09:56:05.890 2015-06-09 11:26:30.600 8355883 3113976 3179461 6 2008-03-17 13:05:41.323 2008-03-17 13:24:03.127 3113965 3113966 3179451 1 2008-03-17 13:05:41.323 2008-03-17 13:05:41.323 3113965 3113970 3179455 3 2008-03-17 13:05:41.323 2008-03-17 13:13:19.373 3113965 3113968 3179453 2 2008-03-17 13:05:41.323 2008-03-17 13:06:18.293 3113965 5865590 5832828 10455652 814 2009-06-04 12:45:16.087 2009-06-04 12:45:16.087 3114020 3179504 19 2008-03-17 13:05:41.323 2008-03-19 15:03:56.117 3113965 10455653 814 2009-06-04 12:45:16.087 2009-06-04 12:45:16.087 10455654 814 2009-06-04 12:45:16.087 2009-06-04 12:45:16.087 10455655 814 2009-06-04 12:45:16.087 2009-06-04 12:45:16.087 3114023 3179506 20 2008-03-17 13:05:41.323 2008-03-19 15:13:57.957 3113965 10455656 814 2009-06-04 12:45:16.087 2009-06-04 12:45:16.087 10455657 814 2009-06-04 12:45:16.087 2009-06-04 12:45:16.087 3114025 3179508 21 2008-03-17 13:05:41.323 2008-03-19 15:20:29.210 3113965 10455658 814 2009-06-04 12:45:16.087 2009-06-04 12:45:16.087 10455659 814 2009-06-04 12:45:16.087 2009-06-04 12:45:16.087 10455660 814 2009-06-04 12:45:16.087 2009-06-04 12:45:16.087 10455661 814 2009-06-04 12:45:16.087 2009-06-04 12:45:16.087 10455662 814 2009-06-04 12:45:16.087 2009-06-04 12:45:16.087 10455663 814 2009-06-04 12:45:16.087 2009-06-04 12:45:16.087 10455664 814 2009-06-04 12:45:16.087 2009-06-04 12:45:16.087 3114016 3179500 17 2008-03-17 13:05:41.323 2008-03-18 15:17:55.367 3113965 10455665 814 2009-06-04 12:45:16.087 2009-06-04 12:45:16.087 10455666 814 2009-06-04 12:45:16.087 2009-06-04 12:45:16.087 3114018 3179502 18 2008-03-17 13:05:41.323 2008-03-19 15:02:32.297 3113965 3114004 3179489 16 2008-03-17 13:05:41.323 2008-03-18 15:00:57.410 3113965 24117755 24051827 2013-12-04 10:56:57.197 2013-12-04 10:56:57.197 3114003 3179488 15 2008-03-17 13:05:41.323 2008-03-18 14:52:31.687 3113965 24117754 24051827 2013-12-04 10:56:57.197 2013-12-04 10:56:57.197 24117753 24051827 2013-12-04 10:56:57.197 2013-12-04 10:56:57.197 24117752 24051827 2013-12-04 10:56:57.197 2013-12-04 10:56:57.197 24117751 24051827 2013-12-04 10:56:57.197 2013-12-04 10:56:57.197 24117750 24051827 2013-12-04 10:56:57.197 2013-12-04 10:56:57.197 24117749 24051827 2013-12-04 10:56:57.197 2013-12-04 10:56:57.197 24117748 24051827 2013-12-04 10:56:57.197 2013-12-04 10:56:57.197 10455647 814 2009-06-04 12:45:16.087 2009-06-04 12:45:16.087 10455646 814 2009-06-04 12:45:16.087 2009-06-04 12:45:16.087 10455649 814 2009-06-04 12:45:16.087 2009-06-04 12:45:16.087 3113999 3179484 13 2008-03-17 13:05:41.323 2008-03-17 14:46:10.790 3113965 24117758 24051827 2013-12-04 10:56:57.197 2013-12-04 10:56:57.197 10455648 814 2009-06-04 12:45:16.087 2009-06-04 12:45:16.087 24117757 24051827 2013-12-04 10:56:57.197 2013-12-04 10:56:57.197 10455651 814 2009-06-04 12:45:16.087 2009-06-04 12:45:16.087 3114001 3179486 14 2008-03-17 13:05:41.323 2008-03-18 14:40:04.290 3113965 24117756 24051827 2013-12-04 10:56:57.197 2013-12-04 10:56:57.197 10455650 814 2009-06-04 12:45:16.087 2009-06-04 12:45:16.087 3114053 3179536 41 2007-12-03 13:18:03.697 2008-02-12 08:22:35.703 2162995 3114052 3179535 35 2008-03-17 13:05:41.323 2008-03-19 16:57:55.087 3113965 3114050 3179533 34 2008-03-17 13:05:41.323 2008-03-19 16:54:28.077 3113965 3114048 3179531 33 2008-03-17 13:05:41.323 2008-03-19 16:50:32.287 3113965 28213296 28246065 4 2015-08-26 12:01:56.270 2015-08-28 10:13:25.597 28213255 28213293 28246062 3 2015-08-26 12:01:56.270 2015-08-28 10:04:20.937 28213255 3114046 3179529 32 2008-03-17 13:05:41.323 2008-03-19 16:43:35.753 3113965 28213291 28246060 2 2015-08-26 12:01:56.270 2015-08-26 12:06:20.900 28213255 3114044 3179527 31 2008-03-17 13:05:41.323 2008-03-19 16:31:09.423 3113965 3114042 3179525 30 2008-03-17 13:05:41.323 2008-03-19 16:27:31.670 3113965 3114040 3179523 29 2008-03-17 13:05:41.323 2008-03-19 16:25:17.743 3113965 3114038 3179521 28 2008-03-17 13:05:41.323 2008-03-19 16:23:54.463 3113965 3114037 3179520 27 2008-03-17 13:05:41.323 2008-03-19 16:22:35.447 3113965 10256388 10223630 10223629 10223628 9798398 10256387 10223619 10223620 10223621 10223622 10223623 10223624 10223625 10223626 10223627 9798378 3114035 3179518 26 2008-03-17 13:05:41.323 2008-03-19 16:18:24.537 3113965 16416978 16449738 189 2009-01-06 09:56:05.890 2011-03-31 20:10:09.893 8355883 3114033 3179516 25 2008-03-17 13:05:41.323 2008-03-19 16:12:30.957 3113965 16416976 16449736 188 2009-01-06 09:56:05.890 2011-03-31 20:07:17.647 8355883 3114031 3179514 24 2008-03-17 13:05:41.323 2008-03-19 16:08:46.017 3113965 16416974 16449734 187 2009-01-06 09:56:05.890 2011-03-15 10:33:49.377 8355883 3114029 3179512 23 2008-03-17 13:05:41.323 2008-03-19 15:39:36.597 3113965 16416972 16449732 1 2011-03-31 19:57:30.943 2011-03-31 19:57:30.943 16416971 26018343 25919539 2014-05-20 05:32:00.340 2014-05-20 05:32:00.340 3114027 3179510 22 2008-03-17 13:05:41.323 2008-03-19 15:24:44.797 3113965 16416969 16449729 20 2008-08-04 13:42:13.733 2011-01-18 21:18:09.177 5832921 16416948 16449709 3 2011-03-29 10:13:19.987 2011-03-29 10:34:07.087 16416942 9797784 9830553 28 2008-04-22 12:26:44.157 2009-04-22 13:52:37.627 3637534 9797783 9830552 27 2008-04-22 12:26:44.157 2009-03-09 16:58:40.237 3637534 16416950 16449711 4 2011-03-29 10:13:19.987 2011-03-29 10:47:29.583 16416942 4587521 2162995 2008-05-28 21:29:45.220 2008-05-28 21:29:45.220 12158 1 16416944 16449705 1 2011-03-29 10:13:19.987 2011-03-29 10:13:19.987 16416942 16416946 16449707 2 2011-03-29 10:13:19.987 2011-03-29 10:19:55.193 16416942 16416940 16449701 1 2011-03-15 10:34:53.783 2011-03-15 10:34:53.783 16416807 16416796 16449563 6 2011-03-14 14:48:54.827 2011-03-14 16:00:46.310 16416786 15663251 Backup ...' # \[kgomes\] Accepted the defaults # \[kgomes\] Under options, I selected 'Verify after backup' # \[kgomes\] Under General, I selected 'Disk' as the destination, then clicked on 'Add...' # \[kgomes\] I added the file name '2012_12_12_2.1.1' to the default path as the file name to save it to # \[kgomes\] I then took about 15 minutes and stated it was completed successfully. # \[kgomes\] I then mapped the equinox 'backup' folder on foghorn and could then see the backup of the SQL database. # \[kgomes\] I copied the backup to the backup file to the D:\MSSQL 10.MSSQL\MSSQL\BACKUP directory so I could use it to restore the database on foghorn # \[kgomes\] On foghorn I started up SQL Server Management Studio again # \[kgomes\] I right-clicked on the "Databases" icon and select "Restore Database..." # \[kgomes\] I entered 'Alfresco' as the "To database" name to restore to # \[kgomes\] I selected 'From Device', then clicked on the "..." button. # \[kgomes\] I left the default media of "file" and then clicked "Add..." # \[kgomes\] Then I had to select "All Files" from the "Files of Type" because I forgot to add the .bak extension when I backed it up. # \[kgomes\] Then selected OK, then OK again. # \[kgomes\] I put a check mark next to the new device entry. # \[kgomes\] I looked under "Options" and selected "Overwrite the existing database" even though I don't think it is needed in this case. # \[kgomes\] Then I clicked OK to fire it off. # \[kgomes\] After this, Neil and I noticed that the schema being used on the tables was 'LAGOON\DB_Collaboration'. Neil wanted to change that to 'dbo'. He made the change and we may have to edit the JTDS driver URL to use that schema specifically (if it works at all). # \[kgomes\] I then logged into alfresco.mbari.org and copied the 'lucence-indexes' directory on the D:\alf_data to the 2012_12_12_2.1.1 directory on atlas\Alfresco so that we had a backup of the indexes. # \[kgomes\] I copied the database backup from equinox to the same share so we had all three: content store, database backup and lucene-indexes all in one spot. # \[kgomes\] I downloaded version 2.1.7.1, 3.4.10, 3.4.11 and 4.1.1.3 and put them in the /tmp directory on alfresco5-test.mbari.org and on alfresco5.mbari.org # \[kgomes\] I put a README.txt file in this same directory to explain all this. # \[TRIBLOOM\] Step 1 - Alfesco 2.1.7.1 \-Unzip alfresco-enterprise-tomcat-2.1.7.1.zip \-Create directory /opt/alfresco-enterprise-2.1.7.1 \-Create symbolic link from /opt/alfresco to /opt/alfresco-enterprise-2.1.7.1 \-Modify /opt/alfresco/tomcat/shared/classes/alfresco/extension/custom-repository.properties for SQL Server DB \-Use alf2_1_7@foghorn.shore.mbari.org for the DB and a new/blank content store and indexes \-Modify /opt/alfresco/tomcat/shared/classes/alfresco/extension/custom-hibernate-dialect.properties for SQL Server DB \-Create /etc/init.d/alfresco from https://wiki.alfresco.com/wiki/Installing_Alfresco_2.1_on_Ubuntu_7.10 (modify for AlfrescoSvc user, remove iptables, redirection, and open office, and change log location) \-Adjust permissions/ownership as necessary \-Adjust access to the firewall as necessary \-Verify "stock" Alfresco is working (use a web browser on port 8080) # \[TRIBLOOM\] Step 2 - "Upgrade" Alfresco 2.1.1 content/DB to Alfresco 2.1.7.1 \-Delete the alf_bootstrap_lock table \-Delete all JBPM_\* tables from the DB (this will destroy any in process workflows) \-Redirect Alfresco to the old DB (Alfresco@foghorn.shore.mbari.org) and content store using /opt/alfresco/tomcat/shared/classes/alfresco/extension/custom-repository.properties \-Set index.recovery.mode=FULL to rebuild indexes (note this process took about 9 hours) # \[TRIBLOOM\] Step 3 - Alfresco 2.2.8 \-Run the linux installer ./AlfrescoEnterprise-2.2.8-Linux-x86-Install     -Use /opt/alfresco-enterprise-2.2.8 for the target directory \-Remove the old sym link /opt/aflresco rm /opt/alfresco \-relink /opt/alfresco to 2.2.8 ln \-s /opt/alfresco-enterprise-2.2.8 /opt/alfresco \-Modify /opt/alfresco/tomcat/shared/classes/alfresco/extension/custom-repository.properties for SQL Server DB \-Use alf2_2_8@foghorn.shore.mbari.org for the DB and a new/blank content store and indexes \-Modify /opt/alfresco/tomcat/shared/classes/alfresco/extension/custom-hibernate-dialect.properties for SQL Server DB # \[TRIBLOOM\] Step 4 - "Upgrade" Alfresco 2.1.1 content/DB to Alfresco 2.1.7.1 \-Delete the duplicate archive nodes using this script: /*****\* Script for removing duplicate archive nodes  \******/ delete   FROM \[Alfresco\].\[dbo\].\[alf_node_status\]   where node_id in (   select A.id from (     SELECT       count(n.id) as num, n.id     FROM       alfresco.dbo.alf_node n       JOIN alfresco.dbo.alf_node_status nstat ON (nstat.node_id = n.id)       JOIN alfresco.dbo.alf_store s ON (s.protocol = nstat.protocol AND s.identifier = nstat.identifier)     group by n.id) A     where A.num > 1   ) and protocol='archive' \-Redirect Alfresco to the old DB (Alfresco@foghorn.shore.mbari.org) and content store using /opt/alfresco/tomcat/shared/classes/alfresco/extension/custom-repository.properties {panel} {column} {section}]]> 15630488 15728671 15630488 2010-12-15 13:45:00.497 2010-12-15 13:45:00.497 133 1 15728670 15728670 15630488 2010-12-15 13:45:00.497 2012-11-12 16:37:22.790 11562 19 16416805 16449572 186 2009-01-06 09:56:05.890 2011-03-15 10:33:29.780 8355883 7766101 7798865 6 2008-08-04 13:42:13.733 2008-11-05 14:50:35.657 5832921 16416804 16449571 185 2009-01-06 09:56:05.890 2011-02-09 09:49:00.147 8355883 7766103 7798867 7 2008-08-04 13:42:13.733 2008-11-14 15:29:46.160 5832921 10460495 3637286 2009-09-24 14:31:39.667 2009-09-24 14:31:39.667 17236196 17268959 2 2011-06-06 21:36:16.963 2011-06-06 21:37:10.420 17236193 10460494 3637286 2009-09-24 14:31:39.667 2009-09-24 14:31:39.667 10460493 3637286 2009-09-24 14:31:39.667 2009-09-24 14:31:39.667 17236198 17268961 3 2011-06-06 21:36:16.963 2011-06-06 21:37:59.130 17236193 10460492 3637286 2009-09-24 14:31:39.667 2009-09-24 14:31:39.667 10460499 3637286 2009-09-24 14:31:39.667 2009-09-24 14:31:39.667 17236200 17268963 4 2011-06-06 21:36:16.963 2011-06-06 21:51:30.613 17236193 10460498 3637286 2009-09-24 14:31:39.667 2009-09-24 14:31:39.667 17236201 17268964 5 2011-06-06 21:36:16.963 2011-06-06 21:55:14.507 17236193 10460497 3637286 2009-09-24 14:31:39.667 2009-09-24 14:31:39.667 10460496 3637286 2009-09-24 14:31:39.667 2009-09-24 14:31:39.667 16416784 16449551 3 2011-01-23 23:16:28.733 2011-03-07 15:33:46.597 15631042 16416789 16449556 2 2011-03-14 14:48:54.827 2011-03-14 15:04:02.273 16416786 10460487 3637286 2009-09-24 14:31:39.667 2009-09-24 14:31:39.667 16416788 16449555 1 2011-03-14 14:48:54.827 2011-03-14 14:48:54.827 16416786 16416793 16449560 4 2011-03-14 14:48:54.827 2011-03-14 15:57:44.077 16416786 10460491 3637286 2009-09-24 14:31:39.667 2009-09-24 14:31:39.667 16416794 16449561 5 2011-03-14 14:48:54.827 2011-03-14 15:59:13.503 16416786 10460490 3637286 2009-09-24 14:31:39.667 2009-09-24 14:31:39.667 16416791 16449558 3 2011-03-14 14:48:54.827 2011-03-14 15:05:57.713 16416786 10460489 3637286 2009-09-24 14:31:39.667 2009-09-24 14:31:39.667 17236194 17268957 1 2011-06-06 21:36:16.963 2011-06-06 21:36:16.963 17236193 10460488 3637286 2009-09-24 14:31:39.667 2009-09-24 14:31:39.667 5865681 5832921 10460500 3637286 2009-09-24 14:31:39.667 2009-09-24 14:31:39.667 10460501 3637286 2009-09-24 14:31:39.667 2009-09-24 14:31:39.667 5865679 5832918 10460502 3637286 2009-09-24 14:31:39.667 2009-09-24 14:31:39.667 10460503 3637286 2009-09-24 14:31:39.667 2009-09-24 14:31:39.667 10460504 3637286 2009-09-24 14:31:39.667 2009-09-24 14:31:39.667 10460505 10355550 2009-09-24 14:32:50.773 2009-09-24 14:32:50.773 10460506 10355550 2009-09-24 14:32:50.773 2009-09-24 14:32:50.773 7766034 7798800 4 2008-11-12 08:47:47.573 2008-11-12 09:49:42.033 7766027 7766033 7798799 3 2008-11-12 08:47:47.573 2008-11-12 09:40:30.477 7766027 7766031 7798797 2 2008-11-12 08:47:47.573 2008-11-12 09:18:02.197 7766027 16416863 16449626 4 2011-01-23 23:16:28.733 2011-03-14 14:47:54.913 15631042 7766029 7798795 1 2008-11-12 08:47:47.573 2008-11-12 08:47:47.573 7766027 15728736 15631339 2011-02-03 18:11:21.613 2011-02-03 18:11:21.613 2937460 1 15728735 15631339 2011-02-03 14:01:12.363 2011-02-03 14:01:12.363 534513 1 7766042 7798808 5 2008-11-12 08:47:47.573 2008-11-12 09:50:03.183 7766027 16416867 16449630 1 2011-03-21 10:00:53.793 2011-03-21 10:00:53.793 16416865 16416815 16449582 3 2011-03-15 10:36:22.017 2011-03-15 11:44:51.073 16416809 16416817 16449584 4 2011-03-15 10:36:22.017 2011-03-15 11:57:10.037 16416809 16416818 16449585 5 2011-03-15 10:36:22.017 2011-03-15 11:59:05.560 16416809 16416811 16449578 1 2011-03-15 10:36:22.017 2011-03-15 10:36:22.017 16416809 16416813 16449580 2 2011-03-15 10:36:22.017 2011-03-15 11:35:07.367 16416809 8060942 8093710 8 2008-08-27 13:39:41.480 2008-10-29 17:34:09.087 6259010 8060940 8093708 8 2008-08-04 13:42:13.733 2008-11-17 08:21:07.133 5832921 2326557 2162995 2007-12-06 10:29:33.930 2007-12-06 10:29:33.930 3002 1 2326547 2326556 2162995 2007-12-21 14:08:06.407 2007-12-21 14:08:06.407 2588 1 2326555 2162995 2007-12-21 14:08:06.390 2007-12-21 14:08:06.390 1783 1 2326547 2162995 2007-12-06 10:29:33.930 2007-12-21 14:08:06.410 2988 2 2326546 2162995 2007-12-06 09:22:22.510 2007-12-06 09:22:22.510 3772 1 2326545 2162995 2007-12-03 13:30:50.737 2007-12-03 13:30:50.737 5163 1 19138244 2162995 2012-04-13 16:28:00.157 2012-04-13 16:28:00.157 19138245 2162995 2012-04-13 16:28:00.157 2012-04-13 16:28:00.157 19138246 2162995 2012-04-13 16:28:00.157 2012-04-13 16:28:00.157 19138247 2162995 2012-04-13 16:28:00.157 2012-04-13 16:28:00.157 19138248 2162995 2012-04-13 16:28:00.157 2012-04-13 16:28:00.157 15663401 15630643 19138241 2162995 2012-04-13 16:28:00.157 2012-04-13 16:28:00.157 19138240 2162995 2012-04-13 16:28:00.157 2012-04-13 16:28:00.157 19138243 2162995 2012-04-13 16:28:00.157 2012-04-13 16:28:00.157 19138242 2162995 2012-04-13 16:28:00.157 2012-04-13 16:28:00.157 11240404 11240349 11273142 1 2010-03-10 11:54:56.970 2010-03-10 11:54:56.970 19072142 19039402 25952307 25919539 25952309 25919541 16547861 16416971 2011-03-31 19:59:29.750 2011-03-31 19:59:29.750 52736 1 17236203 17268966 6 2011-06-06 21:36:16.963 2011-06-06 21:55:37.323 17236193 17236205 17268968 7 2011-06-06 21:36:16.963 2011-06-06 21:58:44.050 17236193 18186409 18252474 2011-11-02 13:50:50.727 2011-11-02 13:50:50.727 121856 1 18186408 18252474 2011-11-02 13:50:13.393 2011-11-02 13:50:13.393 31462 1 17465355 17498123 11 2011-06-06 21:36:16.963 2011-06-07 09:25:02.517 17236193 17465357 17498125 12 2011-06-06 21:36:16.963 2011-06-07 09:33:11.810 17236193 26640386 26673154 20 2013-10-30 14:29:58.263 2014-01-05 20:38:17.763 23167205 26640388 26673156 21 2013-10-30 14:29:58.263 2014-07-01 17:09:36.237 23167205 18645542 18580035 18186363 18252474 2011-10-20 10:06:58.753 2011-10-20 10:06:58.753 347480 1 18186362 18252474 2011-10-20 10:04:58.293 2011-10-20 10:04:58.293 110808 1 14123028 13926566 2010-07-27 11:54:55.030 2010-07-27 11:54:55.030 20239 1 18186359 18252474 2011-10-20 10:01:00.370 2011-10-20 10:01:00.370 23302 1 18186358 18252474 2011-10-20 10:01:00.347 2011-10-20 10:01:00.347 361305 1 18186361 18252474 2011-10-20 10:04:58.287 2011-10-20 10:04:58.287 72188 1 18186360 18252474 2011-10-20 10:01:00.373 2011-10-20 10:01:00.373 78469 1 21398443 4.4: [https://confluence.atlassian.com/display/JIRA044/Migrating+JIRA+to+Another+Server] ## The JIRA configuration tool: [https://confluence.atlassian.com/display/JIRA044/Using+the+JIRA+Configuration+Tool] h5. Steps # (/) Create new VM named bugs.mbari.org in the DMZ # (/) Have Neil create database Jira_Temp on solstice2.shore.mbari.org # (/) Have Neil create database Jira on solstice2.shore.mbari.org # (/) Have Pat install Java 7 on bugs.shore.mbari.org # (/) Have Pete plumb holes through firewall so processes on bugs.mbari.org can get to Solstice2 # (/) Have Pat create DB_Collaboration account on bugs so it can run JIRA under that account and it can connect to solstice2 using that NT Domain account. # (/) Upgrade license on Atlassian site # (/) Log into bugs.shore.mbari.org # (/) Download 3.13.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 4.4.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 5.2.11 standalone Linux 64 bit tar.gz (not sure this version is necessary, but at least I have it) # (/) Unzip and untar the file to /opt # (/) Download latest JIRA (6.4.7 as of this writing). # (/) Unzip and untar it to /opt # Performed Test Upgrade ## (/) In order to export the current stuff in JIRA, I had to shut off access so people could not change the data while I was backing it up. ## (/) I ssh'd to oceana.mbari.org as root and edited the /opt/jira/conf/server.xml file and commented out the Connector section that had the port of 8010 to shut it off from the normal serving route. ## (/) I uncommented the 8082 port connector and the 8443 port connector so that I could still get to the server. ## (/) I stopped and started the JIRA server and in the log file I got a "keystore was tampered with..." which is not surprising. ## (/) I could then browser over to http://oceana.mbari.org:8082/jira ## (/) Then through the Administration console, I did an XML backup ## (/) I then created a tar of all the attachments in the /data/jira_3_12/attachments directory ## (/) I moved both the XML and tar files to the /root/jira-upgrade directory ## (/) I then reversed the changes to the server.xml file and shut down JIRA ## (/) I left it down during the next steps in case it went so well, I could just point people to the new server (yeah, right). ## (/) I then browsed to the crowd server on oceana and add a new application using: ### URL: http://bugs.mbari.org/jira3135 ### IP: 134.89.2.29 ### Name: JIRA3135 ### Password: (ask Kevin) :) ## (/) On bugs, I made a copy of the JIRA 3.13.5 download in the /opt directory and unzipped and untarred it. ## (/) In order to configure the crowd connection I did the following: ### (/) I scp'd the /opt/crowd/client/crowd-integration-client-1.6.jar file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I removed the existing 1.6.1 crowd client jar from the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I scp'd the /opt/crowd/client/conf/crowd.properties file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I scp'd the /opt/crowd/client/conf/crowd-ehcache.xml file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I edited the crowd.properties file on bugs to look like: {noformat} application.name JIRA3135 application.password (ask Kevin) application.login.url http://oceana.mbari.org:8095/crowd/console/ crowd.server.url http://oceana.mbari.org:8095/crowd/services/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 0 session.lastvalidation session.lastvalidation {noformat} ### (/) I edited the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/osuser.xml file to comment out the current authentication mechanism and then uncomment the crowd one. ## (/) I then edited the /opt/atlassian-jira-standalone-3.13.5/conf/server/xml file and configured the database connection to the Jira_Temp database on Solstice2. I looked like this: {noformat} {noformat} ## (/) Edit the /opt/atlassian/jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/entityengine.xml and changed it from 'hsql' to 'mssql' and delete the line with "PUBLIC" in it per the instructions in the comments in that file. ## (/) I edited the /etc/httpd/conf/httpd.conf file and created a proxy pass at the bottom of the file to point a normal URL to the default port 8080 for JIRA: {noformat} # Proxy Pass for JIRA ProxyPass http://bugs.mbari.org:8080 ProxyPassReverse http://bugs.mbari.org:8080 {noformat} ## (/) I restarted Apache ## (/) I scp'd the jtds driver from oceana to the /opt/atlassian-jira-standalone-3.13.5/common/lib directory (you could down from the internet) ## (/) I then went to the /opt/atlassian-jira-standalone-3.13.5/ directory and ran './bin/startup.sh'. From the log file, I could tell things were hanging. After some troubleshooting I am wondering if the local firewall is preventing the application to get access to the database on solstice2. I can telnet to port 1433, but I can't browse to the base http://bugs.mbari.org from anywhere but the local web browser. I have submitted a ticket. ## (/) I restarted the old JIRA with my hopes dashed :(. ## (/) Pat disabled the firewall on bugs.mbari.org but it still hung trying to connect to solstice2.shore.mbari.org. That is really, really perplexing. Neil mentioned that solstice2 is using Kerberos and solstice is not. Checking with the JTDS docs, version 1.3.1 of the driver added kerberos support, so I downloaded that driver and added the 'userKerberos=true' property to the URL in the server.xml file and restarted. Got an error about no credentials, so added user and password properties to the URL. Nope, no luck. Never did figure this one out, but I had Pat pull the VM inside the firewall and after some thrash it worked. Well, it sort of worked ... sigh. It turns out I had downloaded the standard version instead of the enterprise version. I need to redo this work ... grrr. ## (/) I deleted all the tables in the Jira_Temp database and removed the /data/jira3135/indexes directory (and recreated). ## (/) I downloaded the enterprise version of the 3.13.5 server. I made a copy in the /opt directory and unzipped and untarred the file. ## (/) I went back to crowd and edited the application to change the properties to: ### URL: http://bugs.shore.mbari.org:8080 ### IP: 134.89.12.31 ### Name: jira3135 ### Password: (ask Kevin) :) ## (/) I then repeated the steps above to get the server up and running with the following differences: ### The server name is now bugs.shore.mbari.org ### The paths given above are a little different in that they no longer say "standard" but say "enterprise" ### I deleted the proxy pass as it seemed to have issues before and this is only temporary anyway. ## (/) I then browsed to http://bugs.shore.mbari.org:8080 ## (/) It took me to the start up page and at the top was the option to 'import your existing data'. Seemed too good not to try. I clicked on the link. It asked me for the backup file location and the location where the indexes would be stored. ## (/) I copied the XML zip file and the attachments tar file to the /data/original directory. ## (/) I created the /data/jira3135/indexes and used those directories ... it fired off the import and I waited. ## (/) I tailed the log file to watch the import. Holy crap, it worked!!! I could log in and everything! I copied the results from the log file here for posterity sake: {noformat} 2015-07-22 20:55:45,156 http-8080-Processor22 INFO [jira.action.admin.DataImport] Running data import 2015-07-22 20:55:45,179 http-8080-Processor22 INFO [jira.action.admin.DataImport] Importing data.. 2015-07-22 20:55:45,186 http-8080-Processor22 INFO [jira.action.admin.DataImport] Start parsing XML with SAX Parser 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] XML successfully parsed 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] Removing all entries from the database. 2015-07-22 20:56:24,593 http-8080-Processor22 INFO [jira.action.admin.DataImport] All entries removed. 2015-07-22 20:56:24,594 http-8080-Processor22 INFO [jira.action.admin.DataImport] Started storing 410414 Generic Values 2015-07-22 21:01:51,967 http-8080-Processor22 INFO [jira.action.admin.DataImport] Finished storing Generic Values 2015-07-22 21:01:52,329 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:52,361 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:54,683 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLink' to module 'jira.user.format:profile-link-user-format'. 2015-07-22 21:01:54,724 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullName' to module 'jira.user.format:full-name-user-format'. 2015-07-22 21:01:54,773 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkSearcher' to module 'jira.user.format:profile-link-searcher-user-format'. 2015-07-22 21:01:54,784 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkExternal' to module 'jira.user.format:profile-link-external-user-format'. 2015-07-22 21:01:54,795 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkActionHeader' to module 'jira.user.format:profile-link-action-header-user-format'. 2015-07-22 21:01:54,807 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullProfile' to module 'jira.user.format:full-profile-user-format'. 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/comments 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/issues 2015-07-22 21:01:55,641 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/plugins 2015-07-22 21:01:55,867 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:01:55,871 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/issues does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:55,873 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/comments does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,033 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,257 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,889 http-8080-Processor22 ERROR [atlassian.jira.upgrade.ConsistencyCheckImpl] Attachments are turned on, but attachment path [/data/jira_3_12/attachments] invalid - disabling attachments 2015-07-22 21:02:13,904 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Detected that an upgrade is needed; existing data at build 299 2015-07-22 21:02:13,907 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Doing Upgrade... 2015-07-22 21:02:13,915 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value' succeeded 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 317 2015-07-22 21:02:13,944 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite filters - make each filter a favourite of its owner. 2015-07-22 21:02:17,822 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build319] Could not find author 'fpy' for filter with id '10040' 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite filters - make each filter a favourite of its owner.' succeeded 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 319 2015-07-22 21:02:17,995 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise Share Permissions. Move old shares to new shares. 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise Share Permissions. Move old shares to new shares.' succeeded 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 321 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Migrating the old JIRA UI colors to the new JIRA 3.13 colors 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build322] Custom color detected for jira.lf.menu.bgcolour : #336699 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Migrating the old JIRA UI colors to the new JIRA 3.13 colors' succeeded 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 322 2015-07-22 21:02:18,025 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite dashboards - make each dashboard a favourite of its owner. 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'cmcgann' for dashboard with id '10030' 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'fpy' for dashboard with id '10060' 2015-07-22 21:02:18,423 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'kanna' for dashboard with id '10040' 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite dashboards - make each dashboard a favourite of its owner.' succeeded 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 325 2015-07-22 21:02:18,625 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Reindexing all data in JIRA to include Favourites. 2015-07-22 21:02:18,648 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All starting... 2015-07-22 21:02:18,650 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 0% complete. Current index: Issue 2015-07-22 21:02:18,654 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:02:18,809 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 1% complete. Current index: Issue 2015-07-22 21:02:18,855 indexerPool-2-thread-10 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 2% complete. Current index: Issue 2015-07-22 21:02:18,899 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 3% complete. Current index: Issue 2015-07-22 21:02:18,945 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 4% complete. Current index: Issue 2015-07-22 21:02:19,012 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 5% complete. Current index: Issue . . . 2015-07-22 21:02:26,164 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 95% complete. Current index: Issue 2015-07-22 21:02:26,232 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 96% complete. Current index: Issue 2015-07-22 21:02:26,316 indexerPool-2-thread-9 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 97% complete. Current index: Issue 2015-07-22 21:02:26,771 indexerPool-2-thread-3 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: Issue 2015-07-22 21:02:27,261 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 8607ms. Indexer: DefaultIndexManager: paths: [/data/jira3135/indexes/issues, /data/jira3135/indexes/comments] 2015-07-22 21:02:27,263 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: SearchRequest 2015-07-22 21:02:27,268 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,293 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: SearchRequest 2015-07-22 21:02:27,308 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: PortalPage 2015-07-22 21:02:27,312 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,377 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: PortalPage 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 115ms. Indexer: SharedEntityIndexManager: paths: [/data/jira3135/indexes/entities/portalpage, /data/jira3135/indexes/entities/searchrequest] 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All complete. Total time: 8722ms. 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Reindexing all data in JIRA to include Favourites.' succeeded 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 326 2015-07-22 21:02:27,397 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade succeeded! Setting data build number to 360 2015-07-22 21:02:27,469 JiraQuartzScheduler_Worker-0 WARN [service.services.export.ExportService] Backup directory /data/jira_3_12/backup does not exist {noformat} {warning:title=Paths} It appears that the upgraded JIRA will still look for the attachments and the backup locations in the original places. So I created /data/jira_3_12/backup and untarred the original attachments to /data/jira_3_12 and then everything worked (including attachements) in the new JIRA. {warning} ## (/) I then used the upgraded JIRA to generate a new XML backup and stored it in /data/original/3.13.5 along with another tar of the files in /data/jira_3_12/attachments. ## (/) I then shutdown the JIRA server. *I should be ready to move on to version 4 upgrade WHEW* ## So, before moving on, I decided that it would be a really good idea to spin up a new Crowd instance to get rid of the :8443 in the URL and to move off of RedHat per IS requests. I have a ticket in for a new VM and a new database to try to get this going. I am waiting on that before moving on. ## (/) Pat created the VM and Neil created the database. ## (/) I logged into auth.mbari.org (name of the VM) and downloaded crowd which I unzipped to the /opt directory ## (/) I then created a /data/crowd directory and gave my account permissions on it and then edited the /opt/atlassian..../crowd-webapp/WEB-INF/classes/crowd-init.properties file to set that as the crowd home directory. ## (/) The instructions say to download the JDBC driver, but they already have JTDS 1.2.7 in the download so I did not do anything. ## (/) You have to manually connect up CrowdID to a database as they setup wizard does not currently do this. ### (/) They say to download the driver, but again 1.2.7 was there so I did nothing. ### (/) I edited the /opt/atlassian.../apache-tomcat/conf/Catalina/localhost/openidserver.xml to look like: {noformat} {noformat} ### (/) I edited the /opt/atlassian.../build.properties files to look like: {noformat} # Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See https://confluence.atlassian.com/display/CROWD/Connecting+Crowd+to+a+Database hibernate.dialect=org.hibernate.dialect.SQLServerDialect # The Hibernate transaction factory to use. See https://confluence.atlassian.com/display/CROWD/Configuring+Crowd hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory # The http port you wish to run crowd from, ie: http://localhost:8095/crowd crowd.tomcat.connector.port=8095 # Tomcat requires a unique port for shutdown crowd.tomcat.shutdown.port=8020 # Crowd context root crowd.url=http://localhost:8095/crowd # Demo context root demo.url=http://localhost:8095/demo # OpenID server context root openidserver.url=http://localhost:8095/openidserver {noformat} ### (/) I then ran the build.sh script in the root of /opt/atlassian... ## (/) I fired up crowd using the /opt/atlassian.../start_crowd.sh script ## (/) I then went to http://auth.mbari.org:8095/crowd to kick off the start up wizard ## (/) I grabbed a new eval license from my account on atlassian and pasted into the license page. ## (/) I selected "New install" on the next page. ## (/) I configured the JDBC connection using this connection URL with user DB_Collaboration {noformat} jdbc:jtds:sqlserver://dione.mbari.org:51001/Crowd;domain=SHORE;useNTLMv2=TRUE {noformat} ## (/) I left the "Options" as they came up {warning:title=Paths} Not sure if this is a problem, but because I started the set up using auth.mbari.org, it set the Base URL to http://auth.mbari.org:8095/crowd instead of localhost. Hope that is not a problem. We will see. {warning} ## (/) I configured the email connection using the settings from [here|https://wind.shore.mbari.org/is/howto/email/mbarimail/imap] and I used my network login (probably shouldn't be doing that ... not sure where it stores my password, but I am assuming in the DB). ## (/) For the local admin account, I created a user named 'crowdadm' so it would not clash with my LDAP account. See Kevin Gomes for password information. ## (/) I checked the OpenID server as an integrated application ## (/) It then took me to the login page and I logged in using the newly minted admin account. Seemed all is well so far. ## (/) I visited the openidserver URL as well and that seemed OK. ## (/) I decided to wait on configuring the MBARI LDAP directory until I got everything with SSL working. ## (/) Now the next step was to follow the directions to configure Crowd to run over SSL found [here|https://confluence.atlassian.com/display/CROWD/Configuring+Crowd+to+Work+with+SSL] ## (/) I shutdown crowd. Note that the stop script does not shutdown things correctly and I noticed the crowd app running as root. That should not be if I started as kgomes. Not sure what is up with that. ## (/) Now Joe had already configured SSL once, so I used his connector configuration in the server.xml file and so the final file looked like: {noformat} {noformat} ## (/) I then edited the /data/crowd/crowd.properties to look like: {noformat} #Sat Aug 01 09:05:15 PDT 2015 session.lastvalidation=session.lastvalidation session.tokenkey=session.tokenkey crowd.server.url=https\://localhost\:8443/crowd/services/ application.name=crowd http.timeout=30000 session.isauthenticated=session.isauthenticated application.login.url=https\://localhost\:8443/crowd/console/ session.validationinterval=0 application.password=Y1Xp3OorCmsOP4eruL1dmH {noformat} One thing to note here is that based on a comment from the SSL configuration page at atlassian (Steve's comment), you are supposed to leave all the host names the same. For example, if the file says localhost, leave it localhost. So this created a bit of a problem based on the fact that I had left the base URL pointing to auth.mbari.org in the wizard steps above. That step wrote auth.mbari.org to the /data/crowd/crowd.properties. All the other files reference localhost, so to be consistent, I changed auth.mbari.org to localhost in the /data/crowd/crowd.properties file. We will see if this works. ## (/) Per the instructions on the atlassian page (referenced above), I also edited the build.properties file and the /client/conf/crowd.properties files before I restarted and used the SSL URLs ## build.properties: {noformat} # Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See https://confluence.atlassian.com/display/CROWD/Connecting+Crowd+to+a+Database hibernate.dialect=org.hibernate.dialect.SQLServerDialect # The Hibernate transaction factory to use. See https://confluence.atlassian.com/display/CROWD/Configuring+Crowd hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory # The http port you wish to run crowd from, ie: http://localhost:8095/crowd crowd.tomcat.connector.port=8095 # Tomcat requires a unique port for shutdown crowd.tomcat.shutdown.port=8020 # Crowd context root crowd.url=https://localhost:8443/crowd # Demo context root demo.url=https://localhost:8443/demo # OpenID server context root openidserver.url=https://localhost:8443/openidserver {noformat} ## crowd.properties (client) {noformat} application.name crowd application.password password application.login.url https://localhost:8443/crowd/console/ crowd.server.url https://localhost:8443/crowd/services/ crowd.base.url https://localhost:8443/crowd/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 2 session.lastvalidation session.lastvalidation {noformat} ## (/) Although not stated, I am assuming you would need to run the build.sh script to push the build.properties changes to their proper places, so I did that. Note that before doing that, I know that it will clobber the server.xml changes I made, so I made a copy of that file and diff'd them after and then rolled the previous changes to the new server.xml file. Actually, amazingly enough, it seems to have done the connector entry correctly so I left it after running the build.sh script. ## (/) Crossed my fingers and then restarted crowd. I tailed the catalina.out file and did not see any stack traces so that is a good sign! ## (/) I visited https://auth.mbari.org:8443/crowd first. It could not find that page, but I suspect that is because I am browsing from the outside, so I tried just https://auth.mbari.org/crowd and got a service unavailable. I am suspecting that this is a combination of firewall and proxy pass and I will send this info to Joe. From what I can see on the crowd side, it seems like the server started cleanly, we just can't get to it. I tried to reach it from a browser on the machine itself too (through VNC) with the same service not available. ## (/) Here are the notes from Joe after he fixed it! Wooohooo! {noformat} Hey Kevin, Thanks for starting clean! I had to make a few adjustments. 1-I modified the server.xml file in /opt/atlassian-crowd-2.8.3/apache-tomcat/conf/server.xml so there are two connectors per the instructions on the Atlassian site. I have backed up this good server.xml file in /etc/temp/ if you want to browse it to see what I did. Of note is that I removed all the jargon referencing the types of ciphers available to simplify things for now. 2-I modified /data/crowd/crowd.properties to have crowd.server.url=https\://localhost\:8443/crowd/services/ application.login.url=https\://localhost\:8443/crowd/console/ But that would cause my login to error with an error saying it was unable to reach the authentication server. I scratched my head for a bit. When I revert the values to just using non-SSL and try to log in, I just get an "invalid login" (I don't know the crowdadm password). So I worked under the assumption that if I can configure SSL to get an "invalid login" when logging in then it would work when provided real credentials. So, I then changed /data/crowd/crowd.proprties to: crowd.server.url=https\://auth.mbari.org\:8443/crowd/services/ application.login.url=https\://auth.mbari.org\:8443/crowd/console/ And now when I try to log in with SSL it says "invalid login". Strange because all the other values I can find only show "localhost" .. in any case... Can you try to log in now? {noformat} ## (/) Next I moved on to configuring the connection to MBARI's LDAP server to enable our logins through Crowd and CrowdID ## (/) I clicked on "Add Directory" in crowd. ## (/) I selected "Connector" then clicked Next ## (/) I put ldap.shore.mbari.org as the name of the server ## (/) I selected "Use memberOf for group memberships" ## (/) I used "OU=AllUsers,DC=shore,DC=mbari,DC=org" for the Base DN ## (/) I used "CN=LDAPbind,OU=Special,OU=AllUsers,DC=shore,DC=mbari,DC=org" for the Username (talk to Pat Allen for password) ## (/) I tested the connection (button click) and it passed. ## (/) I de-selected all the capabilities of the connector as it is a ready only connector and then saved it. It synchronized correctly! ## (/) At first, I could not login using my MBARI credentials, but after going to the "crowd" application in crowd (logged in as the local admin), I had to add the LDAP directory and configure it to "Allow all to authenticate", then I was able to login. After this, the last step was to get this to run as a different user and lock down various directories. I went through the entire directory structure /opt/atlassian... and set up so that root owned all read-only locations and DB_Collaboration (account set up by IS) owned the other stuff. I also gave full ownership to the /data/crowd directory to DB_Collaboration so it could write there. Pat set up a script to start on boot and after a little tweaking, it now starts on boot. {warning:title=CrowdID log file} One thing that came up here was that when the crowdID application ran, it tried to write a log file to the location where the process was launched from (which is /opt/atlassian...). This is a bad thing and I figured out that I could change that location by changing the file /opt/atlassian-crowd-2.8.3/crowd-openidserver-webapp/WEB-INF/classes/log4j.properties and hardcoding the /data/crowd/logs/atlassian-crowd-openid-server.log and then restarted the application. {warning} ## (/) Another note is the when an application tried to use the OpenID application, it would get redirected to localhost. I changed the /opt/atlassian.../crowd-openidserver-webapp/WEB-INF/classes/crowd.properties file to look like: {noformat} #Sat Aug 01 10:03:18 PDT 2015 session.lastvalidation=session.lastvalidation session.tokenkey=session.tokenkey crowd.server.url=http\://localhost\:8095/crowd/services/ application.name=crowd-openid-server #application.login.url.template=http\://localhost\:8095/openidserver?returnToUrl\=${RETURN_TO_URL} application.login.url.template=https\://auth.mbari.org/openidserver?returnToUrl\=${RETURN_TO_URL} session.isauthenticated=session.isauthenticated #application.base.url=http\://localhost\:8095/openidserver application.base.url=https\://auth.mbari.org/openidserver #application.login.url=http\://localhost\:8095/openidserver application.login.url=https\://auth.mbari.org/openidserver session.validationinterval=0 application.password=password {noformat} and that seems to have fixed it. # (/) It is finally time to move on to the version 4 upgrade ... holy crap. I first went to the *new* crowd install (auth.mbari.org) and logged in as the crowdadm. # (/) I clicked on Applications, then on Add Application # (/) I selected JIRA from the Application type drop-down # (/) I entered jira445 as the username. Ask Kevin about the password. # (/) I used http://bugs.shore.mbari.org:8081 as the URL # (/) I used 134.89.12.31 as the IP address. # (/) I selected only the MBARI LDAP directory. # (/) Then I selected "Allow all users to authenticate" # (/) Then I clicked on "Add Application" # (/) I VNC'd into bugs.mbari.org. As it turns out, for Linux, there is an installer program to download. I downloaded the .bin for 64 bit Linux installer and moved it to the jira-upgrade directory. # (/) I chmod'd the file to make it executable and ran it. It gave me a warning about not being root, but I went ahead with it. # (/) It asked for the JIRA home and data directory, which I specified as /opt/jira4 and /data/jira445. # (/) For the ports, I specified 8180 and 8105 (HTTP and control respectively). It then extracted all the files and launched JIRA. It said if finished, so I opened a local browser to http://localhost:8180 which kicked off the start up wizard. # (/) I specified the external database using: ## solstice2.shore.mbari.org (server) ## 1433 (port) ## jira4 (database) ## DB_Collaboration (username) ## (password ask Kevin) ## dbo (schema) # But all this failed as it seems to just want to try and use the SQL server authentication instead of domain. I will have to do it manually. # (/) I stopped the server using the bin/stop-jira.sh script. # (/) I created and edited /data/jira445/dbconfig.xml and made it look like the following: {noformat} ?xml version="1.0" encoding="UTF-8"?> defaultDS default mssql jiraschema jdbc:jtds:sqlserver://solstice2.shore.mbari.org:1433/Jira4;domain=SHORE;useNTLMv2=true net.sourceforge.jtds.jdbc.Driver DB_Collaboration (ask Kevin) 15 {noformat} # (/) I then started it again using bin/start-jira.sh and tailed the catalina.out file. Got a bunch of errors related to the schema 'jiraschema', I edited the file and changed the schema to 'dbo' and restarted. That seemed to do it. There was one stack trace for some iCal plugin, but looks OK other than that. # I browsed back to localhost:8180 and the wizard moved to step 2. There was an option to import existing data bit without the crowd connection, I thought I should set it up manually, connect to crowd, then import. I generated an evaluation license, called the app "MBARI JIRA4" and change the server in the url to bugs.shore.mbari.org # For the admin, I created an account called 'jiraadm' (ask Kevin for password). # Since this is a temporary system, I left the email system disabled. # I logged in as jiraadm, went to Administration, then Users, then clicked on Add Directory and chose Atlassian Crowd. Note that I had to set the server URL to http://auth.mbari.org:8095/crowd or I would have had to configure all this SSL crap that I did not want to do for this temporary install. # It tested successfully, I clicked Save and it went through a 13 second sync, whew! # I then went to System->Import and Export->Restore System # I copied the jira-upgrade-3.13.5.zip file from the previous version export into /data/jira445/import and then entered that file name along with the new evaluation license again. # I worked through progress bar after I clicked on Restore (it took a really long time). # I then stopped, restarted and tailed the log file. # I am thinking now I should have put the attachments in the import attachments directory, but I am hoping I can just copy them to the data/attachments directory. # UG! I got some error during the import. The exception read: "JIRA is unable to migrat the User Directory configuration because external users exist but the osuser.xml file is not available". It then gave me a link to a doc that talked about making the old user files available before the upgrade ... crap. So I needed to copy the osuser.xml and crowd.properties file from atlassian-jira/WEB-INF/classes directory on the old install to the same directory on the new install ... sigh. This means I am going to blow away everything and start over. # I shutdown jira4 # I dropped all things in the database and deleted all content in the /data/jira445 directory (except for the dbconfig.xml file). # I also removed the temp, logs (actually you have to leave the directory, just clear the files) and the work/Catalina/localhost directories from the jira installation. # I then copied the osuser.xml and the crowd.properties files from the 3.13.5 install to the 4 install. # I edited the crowd.properties file in hopes that I could point it to the new crowd install on auth.mbari.org and it would work, but we will see. # I then started jira and tailed the log file. # All looked OK (other than iCal plugin stack trace again), so I went to localhost:8180 and got step 2 of the wizard. I used the same info as before. # I logged in as the local admin account and it looks like the system picked up the crowd connection, but lets see what server it used! Hey it used the one I edited into the file! Sweet ... now let's see if the import works. # I copied the 3.13.5 zip file to the import directory again and this time, I untarred the attachments into the import/attachments directory. # I kicked off the restore as before and it worked through it fine. # Shutdown and restarted system, tailing the log file and then went to localhost:8180 # I can see issues (before logging in) and it all looks good!! The attachments did not move over from the import directory, so I copied the tar file from /data/jira445/import to /data/jira445/data and then untarred it there, then removed the tar file and the import zip file from the import directory. # Now I will try to login using my MBARI account and OMG it actually worked!!! (it even gave my kgomes account Admin privs) # I then performed an export and copied those file to the /data/backups/4.4.5 directory (also created a TAR of the attachments and put there too). # Now on to version 5! # OK, so something strange is happening. After the imports, the server ID goes back to the one that is on our current production server, which must mean it is using our current license key (which does not match the server ID, BTW). Oh well, I will press on! # I created a /data/jira5211 directory as well as a /opt/jira5 directory. Knowing what I know now and reading through the install instructions, it appears that I need to create a dbconfig.xml file manually, so I did that using: {noformat} defaultDS default mssql dbo jdbc:jtds:sqlserver://solstice2.shore.mbari.org:1433/Jira5;domain=SHORE;useNTLMv2=true net.sourceforge.jtds.jdbc.Driver DB_Collaboration (ask Kevin) 20 20 30000 20 true 300 select 1 60000 300000 true false {noformat} # I then changed the mode to executable on the installer download and ran that. # I had to choose a "custom install" this time through, but the properties were similar after that (ports I used were 8280 and 8205) # I then browsed to localhost:8280 # I dropped me to a wizard where I define the title as "MBARI JIRA5", and changed host to bugs.shore.mbari.org (from localhost) # This license was a little different in that is just asked for my Atlassian username and password and fetched a new license for me. # For the admin account, I used the same 'jiraadm' account # Left email notification disabled. # I created a new application in crowd for JIRA 5 and used same account info as for 4. # In JIRA, I went to Administration->Users->User Directories and then added a directory as I had done before. # All went well and the sync happened. # I then went to Administration->System->Import and Export->Restore System # I copied the backup of 4.4.5 to the /data/jira5211/import directory and then specified that file name. I did not specify a license as it seems to use the old one and it said so in the text below the box. # Clicked on restore and while it was restoring, I untarred the attachments to the /data/jira5211/data directory # After the restore, I shutdown and restarted JIRA tailing the log file. # Browsed to localhost:8280 and ... success! I see issues before logging in and ... my MBARI login worked, I was admin and all is good!!!! # As with previous version, I ran a backup of the DB and attachments and placed in /data/backups/5.2.11 # I poked around a little and there seems to be an issue in the comments that they are still referencing oceana??? I will have to look into this. # I then re-did the process once again for version 6.4.9. I will only put notes about things that are dramatically different below: ## It looks like the dbconfig.xml file is the same as it is for version 5, so I just copied and edited to point to Jira6 DB. ## I used ports 8380 and 8305 {warning:title=Collation} The DB needs to be using a specific collation that it's not, I will have to correct that on the production run {warning} ## It gave me a choice on "how I wanted to use JIRA" and I chose the default (top) one which was just JIRA. ## Something did not go well on the restore (got to 90%) from backup up and the server seems to have crashed, but it looks like it tried to restart? ## I forced a stop and start and tailed the log file. Could it be related to the collation issue? Upon restart it re-ran the indexing. Looks like it worked OK, let me login with my MBARI account. ## Interesting, the comments pointing to oceana seems to have fixed itself in the step of the upgrade. ## Another interesting note, when I went to the Admin->System->General configuration, it had the base URL as oceana, that would explain it. So I edited that to bugs.shore.mbari.org (it also made me change the Mode to private, which makes sense since authentication is external). ## I went back to the 3, 4, and 5 install and changed the base URL there too. That fixed that issue. # I then sent an email to all hands giving the URLs for folks to look at. # While folks were looking over the upgrade instances, I went ahead and created the cloud instance at Atlassian so I could test upload the JIRA backup from 6.4.9 {warning:title=Disable Remote Crowd Directory} As a part of the test import, I discovered that you have to disable the remote crowd directory through User Management->User Directories *before* you do the backup/export. {warning} # You basically do a backup of the system, tar up the attachments and then push those files to the cloud instance through WebDAV. Then you choose those files to do a 'JIRA Import'. The attachments did not work and I had to leave those de-selected and then submitted a ticket for that to be done. # It did seem to import all the users from our LDAP system, so I had to go through and 'Deactivate' all the users that I did not think would login. The billing adjusts fine to that, so that seems tractable. I am still working on seeing how users login to their imported accounts and if you can link BitBucket accounts to JIRA. h3. The Production (Final) Migration The day is finally here, the production JIRA migration. Here are the steps I took: # Logged into oceana as root # Edited the /opt/jira/conf/server.xml and commented out the Connector section that had the port of 8010 to shut it off from the normal serving route # I uncommented the 8082 port connector and the 8443 port connector so that I could still get to the server. # I stopped and started the JIRA server and in the log file I got a "keystore was tampered with..." which is not surprising. # I could then browser over to http://oceana.mbari.org:8082/jira # Then through the Administration console, I did an XML backup (file named final-jira-migration-backup-2015-08-21) and selected the zip option ## I had to create a /tmp/jira-backup directory and give DB_Collaboration:coladm ownership for the backup to happen ... sigh # I created the directory /root/jira-upgrade/final-2015-08-21 and moved the backup from /tmp/jira-backup to that location # I then shut down JIRA (hopefully for the LAST time!!!) # I logged out of oceana # I logged into bugs.shore.mbari.org as me # Due to a patch and reboot, all the JIRA servers were down, which was fine. # I cd'd to /opt/atlassian-jira-enterprise-3.13.5-standalone # I wanted to clean things up so I cd'd to logs and removed all the log files # I then wanted to remove the deployed web application so I could start clean so I changed to ../work and deleted the entire Catalina directory # Using Aqua Data Studio, I deleted all the tables in the Jira_Temp database on solstice2 # Back on bugs, I scp'd the backup zip file and the attachments file to the /data/backups/3.12/final-upgrade-2015-08-21 directory # I cd'd to the /data/jira3135 directory and deleted the attachments and indexes directories and then created empty directories for those again. # Since the first import will look for attachments in /data/jira_3_12, I cd'd to that directory and deleted the attachments directory there. # I then copied the attachments tar I scp'd over and untarred it in that location. # I then started up JIRA (version 3.13.5) using /opt/atlassian-jira-enterprise-3.13.5-standalone/bin/startup.sh # I tailed the log file and it looked like a clean startup. # I browsed over to http://bugs.shore.mbari.org:8080 and got the start up page. # I clicked on the "Import existing data" link and specified the /data/backups/3.12/final-upgrade-2015-08-21/final-jira-migration-backup-2015-08-21.zip as the backup file and /data/jira3135/indexes as the index location # I tailed the log file during the import process and everything looked great ... YEEEEEEEEEEESSSSSSSSSSSSSS!!!!!! # OK, so far so good. Attachments were there and everything. # I then went to the administration panel and performed another backup to XML using the file nanme final-jira-migration-3135-backup-2015-08-21 and selected the zip option. # It created the zip file in the JIRA tomcat bin directory! So I moved it to /data/backups/3.13.15/final-upgrade-2015-08-21 # I created a tar of the attachments (which was in the /data/jira_3_12 directory) and moved it to /data/backups/3.13.15/final-upgrade-2015-08-21 also # I then shutdown the 3.13.5 JIRA instance for the LAST (hopefully) time!! # I fired up Aqua Data Studio again and deleted all the stuff in the Jira4 database on solstice 2 # I then cd'd to /opt/jira4/logs and cleaned out any log files # I cd'd to /opt/jira4/work and removed the .pid file and the Catalina directory # I cd'd to the /opt/jira4 directory and removed the temp directory too. # I then cd'd to the /data/jira445 directory and removed everything but the dbconfig.xml file # I then started JIRA 4 and tailed the log file # It created all the tables in the DB as well as all the directories fine. # I copied the /data/backups/3.13.5/final-upgrade-2015-08-21/final-jira-migration-3135-backup-2015-08-21.zip to the /data/jira445/import directory # I copied the /data/backups/3.13.5/final-upgrade-2015-08-21/final-jira-migration-3135-attachments.tar to the /data/jira445/data directory # I untarred it there and it put all the attachments in the attachments directory. # I then removed the tar file. # I then went to the http://bugs.shore.mbari.org:8180 url in my browser # I clicked on the "Import your existing data" link # I entered /data/jira445/import/final-jira-migration-3135-backup-2015-08-21.zip in the File name box and then clicked import. # It bounced back because of eval license was needed, so I clicked on the generate eval license and agreed to the terms, Yes to install license and then clicked import. # I tailed the log file and everything worked!!!! Attachments too!!!! # I logged in and went to the admin panel. # I went to the Import and Export and clicked on Backup System tab on the left. # I entered the file name final-migration-445-2015-08-21 and clicked Backup # This created the backup located here: /data/jira445/export/final-migration-445-2015-08-21.zip # I then shutdown the JIRA4 for the (hopefully) LAST TIME!!!! # I created the /data/backups/4.4.5/final-upgrade-2015-08-21 directory # I then moved the /data/jira445/export/final-migration-445-2015-08-21.zip to the /data/backups/4.4.5/final-upgrade-2015-08-21 directory # I cd'd to the /data/jira445/data directory and tarred up the attachements directory to the final-migration-445-attachments-2015-08-21.tar file # I then moved that file to the /data/backups/4.4.5/final-upgrade-2015-08-21 directory # I cd'd to the /opt/jira5/logs directory and removed all the log files # I cd'd to the /opt/jira5/work directory and removed the Catalina directory and the pid file # I cd'd to the /data/jira5211 directory and I removed all the directories except for the dbconfig.xml file # I used Aqua data studio to delete all the tables in the Jira5 database (this took a couple of rounds of delete due to key constraints) # I then started JIRA 5 using /opt/jira5/bin/start-jira.sh and the DB tables and /data/jira5211 directories were all created OK # I copied the /data/backups/4.4.5/final-upgrade-2015-08-21/final-migration-445-attachments-2015-08-21.tar to the /data/jira5211/data directory # I then untarred the file there which put all the attachments in the attachments folder. # I then copied the /data/backups/4.5.5/final-upgrade-2015-08-21/final-migration-445-2015-08-21.zip to the /data/jira5211/import directory # I tailed the /opt/jira5/log/catalina.out file and opened http://bugs.shore.mbari.org:8280 in my browser # I clicked on the "import data" link # I put /data/jira5211/import/final-migration-445-2015-08-21.zip in the file name field and then clicked on Generate an evaluation key # I filled out everything and it put the license key in and then I clicked on "import" # Everything seemed to go smoothly, so I logged in and then created a backup by going to Administration->System->Import and Export. # I input the file name final-upgrade-5211-2015-08-21 which created the /data/jira5211/export/final-upgrade-5211-2015-08-21.zip file # I shutdown JIRA 5 for (hopefully!) the LAST TIME !!! # I tarred up that /data/jira5211/data/attachments directory and moved it to /data/backups/5.2.11/final-upgrade-5211-2015-08-21/final-upgrade-5211-attachments-2015-08-21.tar # I moved the backup that was in the /data/jira5211/export directory to the /data/backups/5.2.11/final-upgrade-5211-2015-08-21 directory # Using Aqua data studio, I deleted everything in the Jira6 database (took a couple rounds due to keys) # I cd'd to /opt/jira6/logs and removed all the log files # I cd'd to /opt/jira6/work and deleted everything there # I cd'd to /data/jira649 and removed everything but the dbconfig.xml file # I then cd'd to /opt/jira6/bin and started jira using jira-start.sh # I tailed to log file to make sure it all started up OK. # After successful start up, I copied the /data/backups/5.2.11/final-upgrade-5211-2015-08-21/final-upgrade-5211-2015-08-21.zip file to the /data/jira649/import directory # I copied the /data/backups/5.2.11/final-upgrade-5211-2015-08-21/final-upgrade-5211-attachments-2015-08-21.tar to the /data/jira649/data directory and untarred it which put all the attachments in the attachments directory. # I then went to http://bugs.shore.mbari.org:8380 to kick off the set up # I tailed the log file in the terminal to make sure all was OK # I clicked on "import your data" link # I put /data/jira649/import/final-upgrade-5211-2015-08-21.zip in the file name box and clicked on Generate evaluation license, followed the instructions and then clicked on Import # Everything seems to have worked (including attachments)!!! # I went to User Management->User Directories and I moved the JIRA internal directory up in the order of directories and disabled the Remote Crowd Directory # I then did an export using System->Backup System and used the file name final-upgrade-6211-2015-08-21 # I then shutdown the JIRA 6 for (hopefully!!!) the LAST TIME !!!! # I cd'd to the /data/jira629/data directory and created the final-upgrade-629-attachments-2015-08-21.tar file of the attachments directory # I cd'd to the /data/backup/6.4.9/ directory and created the final-upgrade-649-2015-08-21 directory. # I cd'd to that directory and moved the backup file and the attachment tar to that directory. # I then opened a terminal on my local machine and SCP'd those backup files locally. # I then mounted the WebDAV directory on my local machine using finder an connecting using https://mbari1.atlassian.net/webdav/ # I then copied the backup files I scp'd to may local machine to the remote WebDAV directory. # I logged in to our cloud system and went to Administration->System # I clicked on JIRA Import on the left hand side # I only selected the XML backup zip to import as Atlassian has to do the attachments. # I gave me the option of updating URLs that were in issues, I selected the ones point to oceana and continued. # It warned me that everything would be replaced. I left the email enabled and continued. # It looks like it did a purge first, then the import. # It failed and I updated my support ticket to have them look at it # They uploaded and re-indexed and it wiped out all accounts, so I logged in as admin/admin and it put me through a setup routine # I changed that admin password, but it looks like it is a limited 'admin'. I am wondering if the account needs to have site admin because I can't get into any of the user management stuff. # That was it, Atlassian made the admin account a part of the site-admins group and I am golden. # I went through and de-activately almost all the accounts except for the ones I knew about and reset all their password to a default that I will email them directly so they can login and change it. # I added the MBARI Logo # I enabled Gravatar images WHEW, TIME FOR A BEER! ]]> 21365729 14123034 10912227 2010-07-28 11:37:38.583 2010-07-28 11:37:38.583 20145 1 18186357 18252474 2011-10-20 09:57:37.453 2011-10-20 09:57:37.453 4240434 1 19072100 127.0.0.1 8443 8443 {noformat} Add SSL section: {noformat} 8443 /usr/local/keystore/keystore Refer to jetty.xml to see password Refer to jetty.xml to see password {noformat} h3. Start Bamboo using jetty.xml Edit the file /opt/Bamboo/conf/wrapper.conf {noformat}sudo chmod a+w /opt/Bamboo/conf/wrapper.conf{noformat} # Comment out the following lines: #* {noformat}#wrapper.app.parameter.2=8085 #wrapper.app.parameter.3=../webapp #wrapper.app.parameter.4=/{noformat} # Add the following line: {noformat}wrapper.app.parameter.2=webapp/WEB-INF/classes/jetty.xml{noformat} h3. Configure Crowd It's way easier to configure now. Follow the instructions at https://confluence.atlassian.com/display/BAMBOO/Integrating+Bamboo+with+Crowd ]]> 19039359 17465349 17498117 9 2011-06-06 21:36:16.963 2011-06-07 09:03:37.540 17236193 17465347 17498115 8 2011-06-06 21:36:16.963 2011-06-06 22:01:55.330 17236193 17465353 17498121 10 2011-06-06 21:36:16.963 2011-06-07 09:05:30.667 17236193 18186265 17236193 2011-07-25 12:38:08.257 2011-07-25 12:38:08.257 133 1 18186264 18186264 17236193 2011-07-25 12:38:08.257 2011-07-28 15:17:08.720 18808 14 18186269 17236193 2011-07-25 12:38:08.257 2011-07-25 13:58:43.763 7678 5 18186264 18186268 17236193 2011-07-25 12:38:08.257 2011-07-25 13:57:51.757 7115 4 18186264 18186267 17236193 2011-07-25 12:38:08.257 2011-07-25 13:55:02.227 6790 3 18186264 18186266 17236193 2011-07-25 12:38:08.257 2011-07-25 12:45:56.790 4609 2 18186264 13140023 13172790 7 2010-05-25 11:18:33.507 2010-05-25 14:36:46.650 12484688 11829460 " ## \# Set the RTC, only if a battery has been installed on the Beagleboard# # set the battery backed RTC, "hwclock \-w" ## \# Build the McStar Natively# # Enter "shutdown now". # Power off Beagleboard # Remove Ethernet Dongle from the Beagleboard {warning:title=Copy McStar app from host to harddrive}{warning} # Attach a freshly EXT3 formatted USB drive to the host # Enter "cp \-R \~/McStar/app /media/sda1/." # Unmount USB drive # Remove the USB host from the host and connect it to the Beagleboard # Power up the Beagleboard # Enter "root" at the Linux prompt # Enter "cd /media/sda1/app/src" # Enter "touch Makefile \*.h \*.cpp" # Enter "make clean" # Enter "make" ## \# Test the McStar App for 10 minutes, writing a new file every minute # Enter "mkdir /media/sda1/data" # Enter "cd /media/sda1/app/scripts" # Enter "./test_mcstar.sh" \\ \\ ---- h3. Notes on Beagel Board and SD Card Copy h1. Copy Linux filesystem on bootable SD card This tutorial is part of our Tutorials section. It shows how to flash an image onto an SD/SDHC card. This guide assumes that the card is correctly partitioned, as described in the Create a bootable SD/SDHC card in Ubuntu tutorial. h4. Steps in this tutorial # Mount the SD/SDHC card (if not already mounted) # Write bootloader if necessary # Write Linux kernel image # Write Linux root file system # Unmount h1. Quick Solution: Copy an already existing card If you have already one working SD image and an (absolutely similar) formatted second card, you can just copy them. WARNING Please be aware that the filesystem names (/dev/sdb1, etc.) can differ from system to system, make sure to select the right one. Copy one SD card to another: sudo dd if=/dev/sdb of=/dev/sdcThe safer alternative: Copy the SD card to harddisk and then onto another sudo dd if=/dev/sdb of=~/sd-card-copy.binNow back on the second SD card: sudo dd if=~/sd-card-copy.bin of=/dev/sdb h1. Mount SD/SDHC card Check where linux mounted the card. One way is to check this via mount . Call mount to see where the card has been mounted. Two partitions should have been mounted, one named '/media/BOOT' and the other one '/media/LINUX'. Note the device name, e.g. '/dev/sdb'. mountIf the card has not been mounted, you have two choices: h3. Automatic _Just unplug and re-plug the cardreader. It will be detected and mounted automatically._ h3. Manually If the check with mount didn't work out, use dmesg: dmesg \| tailWatch out for a line like this: [sdc] Attached SCSI removable diskWhere *sdc* could also be sdc or sdd. If it was sdb, the device name of the memory card is */dev/sdc*. sudo mkdir \-p /media/BOOT sudo mount /dev/sdc1 /media/BOOT sudo mkdir \-p /media/LINUX sudo mount /dev/sdc2 /media/LINUX h1. Copy files on the BOOT partition (MLO, u-boot.bin and uImage) _Please note that the bootloader files don't have to be rewritten every time. This applies especially when a new custom Linux system is created with_ BitBake and OpenEmbedded_. However if you work close to the hardware, e.g. on drivers, this is different.\_ h4. Overo Download MLO and uBoot from this link (commands for shell below): * PIXHAWK OpenEmbedded Images Download (OpenCV and libdc1394 ready) *IMPORTANT: Copy MLO FIRST\!*. The commands below download the two files and copy them in the right order on the boot partition. _You may have to adjust the filenames for future revisions._ cd $HOME wget [http://pixhawk.ethz.ch/wiki/_media/symlink/images/overo/mlo-overo] wget [http://pixhawk.ethz.ch/wiki/_media/symlink/images/overo/u-boot.bin-overoAnd] now copy the two files onto the boot partition (*MLO first* because of a bug in the X-loader which causes problems if MLO is not the first file written onto the boot partition). cp MLO-overo\* /media/BOOT/MLO cp u-boot.bin-overo\* /media/BOOT/u-boot.bin The Linux kernel (*uImage*) resides also on the *BOOT* partition of the SD-card. If you compile a new version of the kernel you have to copy the new *uImage* on the BOOT partition. See the instructions below. h4. BeagleBoard Download MLO and uBoot from this link (commands for shell below): * [http://www.angstrom-distribution.org/demo/beagleboard/] * Only for PIXHAWK Team (_will be made public in october_) *IMPORTANT: Copy MLO FIRST\!*. The commands below download the two files and copy them in the right order on the boot partition. _You may have to adjust the filenames for future revisions._ cd $HOME wget [http://www.angstrom-distribution.org/demo/beagleboard/MLO] wget [http://www.angstrom-distribution.org/demo/beagleboard/u-boot.binAnd] now copy the two files onto the boot partition (*MLO first* because of a bug in the X-loader which causes problems if MLO is not the first file written onto the boot partition). cp MLO /media/BOOT/MLO cp u-boot.bin /media/BOOT/u-boot.bin The Linux kernel (*uImage*) resides also on the *BOOT* partition of the SD-card. If you compile a new version of the kernel you have to copy the new *uImage* on the BOOT partition. See the instructions below. h1. Copy Linux _The next step is to copy the Linux kernel and the Linux root filesystem on the BOOT and LINUX partitions. You can use_ *{_}precompiled binaries{_}* _for both or_ *{_}compile an OpenEmbedded image yourself{_}{*}_. Instructions for both options are provided below._ h2. Copy the precompiled Ã…ngström Image The precompiled Ã…ngström image consists (besided MLO and u-boot.bin from the bootloader section) of two files: The Linux kernel image (uImage) and the root file system. h3. Copy uImage Download and copy the kernel image into the root directory of the boot partition. h4. Gumstix Overo cd $HOME wget [http://pixhawk.ethz.ch/wiki/_media/symlink/images/overo/uimage.bin-overo] cp uimage.bin-overo\* /media/BOOT/uImage h4. BeagleBoard cd $HOME wget [http://www.angstrom-distribution.org/demo/beagleboard/uImage] cp uImage /media/BOOT/uImage h3. Copy the Linux root file system The file is named *rootfs.tar.bz2 for the Beagle link and omap3-desktop-image-overo\-*.tar.bz2 for the Overo link below. Check the main folder for the current name. * Gumstix Overo: PIXHAWK OpenEmbedded Images Download (OpenCV and libdc1394 ready) * BeagleBoard: [http://www.angstrom-distribution.org/demo/beagleboard/] Download the files to a temporary directory, e.g. the Desktop or your user folder. The next step is to extract these files into the LINUX partition (NOT the boot partition). This can only be done by using Linux. If you're using Windows or MacOS, read this. h4. Gumstix Overo If you have downloaded the console image: wget [http://pixhawk.ethz.ch/wiki/_media/symlink/images/overo/pixhawk-console-image-overo.tar.bz2] sudo tar xjf pixhawk-console-image-overo-*.tar.bz2 \-C /media/LINUXOr the desktop image: wget [http://pixhawk.ethz.ch/wiki/_media/symlink/images/overo/pixhawk-desktop-image-overo.tar.bz2] sudo tar xjf pixhawk-desktop-image-overo\-*.tar.bz2* *{-}C /media/LINUXpossibly, "pixhawk-desktop-image-overo{-}*.tar.bz2" has to be changed into "pixhawk-console-image-overo.tar.bz2" (just adept file name) h4. BeagleBoard sudo tar xjf \*rootfs.tar.bz2 \-C /media/LINUX h2. Copy custom OpenEmbedded Linux Image h3. Linux Kernel Image and u-boot bootloader Copy the kernel image and u-boot. h4. Gumstix Overo sudo cp $OE_HOME/tmp/deploy/glibc/images/overo/uImage-overo.bin /media/BOOT/uImage cp $OE_HOME/tmp/deploy/glibc/images/overo/u-boot-overo.bin /media/BOOT/u-boot.bin h4. BeagleBoard sudo cp $OE_HOME/tmp/deploy/glibc/images/beagleboard/uImage-beagleboard.bin /media/BOOT/uImage cp $OE_HOME/tmp/deploy/glibc/images/beagleboard/u-boot-beagleboard.bin /media/BOOT/u-boot.bin h3. Linux root filesystem After the kernel, the root filesystem has to be copied as well. If you are overwriting an existing installation and you don't need a 100% clean system, you can just delete all files. The command below will delete all files in /media/LINUX except the lost+found directory of the EXT3 file system. sudo rm \-rf /media/LINUX/\* && sudo mkdir /media/LINUX/lost+foundHowever if you want a really clean disk, you should format it, but this will take considerably longer. sudo mkfs.ext3 \-L LINUX /dev/sdc2And now copy the new files. h4. Gumstix Overo The console image: sudo tar xjf $OE_HOME/tmp/deploy/glibc/images/overo/omap3-console-image-overo.tar.bz2 \-C /media/LINUXThe pixhawk console image: sudo tar xjf $OE_HOME/tmp/deploy/glibc/images/overo/pixhawk-console-image-overo.tar.bz2 \-C /media/LINUXOr the desktop image: sudo tar xjf $OE_HOME/tmp/deploy/glibc/images/overo/omap3-desktop-image-overo.tar.bz2 \-C /media/LINUX h4. BeagleBoard The console image: sudo tar xjf $OE_HOME/tmp/deploy/glibc/images/beagleboard/omap3-console-image-beagleboard.tar.bz2 \-C /media/LINUXOr the desktop image: sudo tar xjf $OE_HOME/tmp/deploy/glibc/images/beagleboard/omap3-desktop-image-overo.beagleboard.bz2 \-C /media/LINUX h1. Unmount the SD/SDHC card Now unmount the drive either manually (by clicking the unmount icon on the desktop) or by shell command: sync sudo umount /media/BOOT sudo umount /media/LINUX sudo rm \-r /media/BOOT sudo rm \-r /media/LINUX h1. Copy bytewise from one SDHC card to another If you have modified your installation and want to clone the content of the SD card, you can do this with dd. Make sure to plug in the source card first, then the destination card. Check the file names with: dmesg \| tailAnd unmount the card (with the GUI or with umount /dev/sdb). Then use dd to copy the first gigabyte from one card to the other (including partition table, etc.): sudo dd if=/dev/sdb of=/dev/sdc bs=1073741824]]> 11796703 18645599 characters. Then control goes into a forever loop, reading those dm items, formatting them for output via serial port, and then sleeping for .9 seconds. Some points to note.... # depth items is produced from pressure and ships lat, using standard algorithms by another navproc task (depthCalcTask()).  # Rov Lat/Lon is likewise produced by  the navproc rovPositionTask() from winfrog serial data. The specific datamanger item names consumed are defined in dvecsIntfc.h.{color:#ff0000}*\**{color}{color:#ff0000}\***NOTE THIS NEEDS TO BE RESOLVED FOR MIGRATION TO Rachel Carson... Vorne did not exist on Pt.Lobos/Ventana and the items names are different \! \*\*{color}{color:#ff0000}*\**{color} # The vorneTask() uses the old VT102 ascii terminal command syntax to position the cursor.  \[1,1H is the string command to move the cursor to row1,column1. Then (0x0B) is used to move relative for text appearing on line, 2,3 and 4. # If any garbage exists/gets written to character cells not normally written to during operation (ie in positions beyond end of line, it will remain there. The vorneTask makes an attempt to clear all character position by writing to all lines/cells on startup, but not after that. # The vorne display has significant lag in the time it takes to render the screen.... the serial write is practically immediate; the internal rendering of all the character positions takes perhaps a half-a-second or more.  \\]]> 18580092 18186270 17236193 2011-07-25 12:38:08.257 2011-07-25 15:53:35.503 15191 6 18186264 18186271 17236193 2011-07-25 12:38:08.257 2011-07-25 16:24:05.447 16846 7 18186264 18186272 17236193 2011-07-25 12:38:08.257 2011-07-25 16:28:51.843 17271 8 18186264 18186273 17236193 2011-07-25 12:38:08.257 2011-07-25 16:29:03.580 17271 9 18186264 18186274 17236193 2011-07-25 12:38:08.257 2011-07-25 16:37:17.233 17326 10 18186264 18186275 17236193 2011-07-25 12:38:08.257 2011-07-25 16:39:04.393 17430 11 18186264 18186276 17236193 2011-07-25 12:38:08.257 2011-07-28 15:02:38.557 18065 12 18186264 18186277 17236193 2011-07-25 12:38:08.257 2011-07-28 15:05:51.547 18405 13 18186264 24051833 24084600 3 2013-12-04 09:21:43.933 2013-12-04 09:22:21.847 24051827 24051834 24084601 4 2013-12-04 09:21:43.933 2013-12-04 09:29:19.620 24051827 24051828 24084595 1 2013-12-04 09:21:43.933 2013-12-04 09:21:43.933 24051827 24051829 24084596 2 2013-12-04 09:21:43.933 2013-12-04 09:22:09.320 24051827 17891355 17858588 19041366 19074052 1 2012-11-29 08:17:40.267 2012-11-29 08:17:40.267 19041365 19041363 19074049 229 2009-01-06 09:56:05.890 2012-11-28 09:28:34.070 8355883 19041370 19074056 1 2012-11-29 08:19:23.410 2012-11-29 08:19:23.410 19041368 19041372 19074058 2 2012-11-29 08:19:23.410 2012-11-29 08:25:54.113 19041368 24051844 24084611 9 2013-12-04 09:21:43.933 2013-12-04 10:07:25.007 24051827 24051846 24084613 10 2013-12-04 09:21:43.933 2013-12-04 10:56:40.127 24051827 24051839 24084606 7 2013-12-04 09:21:43.933 2013-12-04 09:31:35.203 24051827 24051842 24084609 8 2013-12-04 09:21:43.933 2013-12-04 09:40:01.580 24051827 24051836 24084603 5 2013-12-04 09:21:43.933 2013-12-04 09:30:17.567 24051827 19041385 19074071 26 2010-12-15 13:35:53.173 2012-12-10 12:36:46.513 15630488 8355888 8388655 2 2009-01-06 09:56:05.890 2009-01-06 14:11:54.517 8355883 19041383 19074069 25 2010-12-15 13:35:53.173 2012-11-12 16:36:29.247 15630488 24051837 24084604 6 2013-12-04 09:21:43.933 2013-12-04 09:31:19.727 24051827 8355887 8388654 1 2009-01-06 09:56:05.890 2009-01-06 09:56:05.890 8355883 11338164 10356476 2010-01-22 15:47:49.167 2010-01-22 15:47:49.167 19041347 19074033 228 2009-01-06 09:56:05.890 2012-11-13 10:37:47.017 8355883 24051873 24084640 12 2013-10-30 14:29:58.263 2013-12-02 08:05:15.867 23167205 9372330 9405063 1 2009-03-19 14:46:17.863 2009-03-19 14:46:17.863 9372328 15663695 15630941 9372336 9405069 4 2009-03-19 14:46:17.863 2009-03-19 15:02:49.923 9372328 9372334 9405067 3 2009-03-19 14:46:17.863 2009-03-19 14:53:27.403 9372328 15630641 15663400 113 2009-01-06 09:56:05.890 2011-01-04 09:26:55.370 8355883 9372332 9405065 2 2009-03-19 14:46:17.863 2009-03-19 14:46:59.403 9372328 15630639 15663398 112 2009-01-06 09:56:05.890 2010-12-17 07:28:02.807 8355883 8355844 8388612 16 2008-10-21 10:34:48.373 2008-12-29 10:52:19.067 6259430 9372345 9405078 4 2008-10-29 10:39:30.207 2009-03-23 14:41:30.300 7176201 8355842 8388610 15 2008-10-21 10:34:48.373 2008-10-21 14:34:39.003 6259430 9372343 9405076 3 2008-10-29 10:39:30.207 2009-03-23 14:40:55.953 7176201 9372341 9405074 1 2008-10-29 10:39:30.207 2008-10-29 10:39:30.207 7176201 9372342 9405075 2 2008-10-29 10:39:30.207 2009-03-23 14:40:37.613 7176201 15630653 15663411 115 2009-01-06 09:56:05.890 2011-01-04 10:35:09.423 8355883 15630652 15663410 114 2009-01-06 09:56:05.890 2011-01-04 09:59:53.397 8355883 15630662 15663420 117 2009-01-06 09:56:05.890 2011-01-04 11:44:04.477 8355883 15630660 15663418 116 2009-01-06 09:56:05.890 2011-01-04 10:44:02.150 8355883 7208966   Debian 4.0, Base Mem=512M, Dynamic sizeable harddisk 8.0 GB host key is right ctrl\\ h1. Editors h3.  TextPad [http://textpad.com /]; TextPad has about 80% to 90% of what slickedit has and you can have it today. \\ To register your copy of TextPad: 1. Select all the lines including "BEGIN LICENSE" and "END LICENSE",     and copy them to the clipboard using Ctrl+C. 2. Start TextPad, and choose the "Enter License Code" command from the     Help menu. 3. Paste the license information into the dialog box, using Ctrl+V. 4. Click OK. If you have purchased a multiple user site license, you must repeat this step on each client PC, but it is not necessary to do it for each user name on a PC. Please e-mail sales@textpad.com, if you have any difficulties. If you do not already have a copy of Textpad 4.5 you can download this from . BEGIN LICENSE Monteray Bay Aquarium Research Institute Site License 01 0005 RS2D-XDNU-GUA4-CZCZ 411aedde 61b2d8be 2a3ea037 54a6535c d80ec02a b3c15935 1509f1d0 08ce95b0 1894c13a 1e29cf6a 24734d92 719e8b90 cd840c5a 87d40e02 5ec866c3 5040e210 30cf0e05 3f14a534 835694bb aee4bdb2 4b63c5d8 61226c94 1eb4a1a2 757fb2b1 END LICENSE]]> 7176201 17891454 17858701 6259451 6226653 11 2008-10-21 10:34:48.373 2008-10-21 11:47:29.440 6259430 15630674 15663431 118 2009-01-06 09:56:05.890 2011-01-04 11:56:57.907 8355883 15630675 15663432 119 2009-01-06 09:56:05.890 2011-01-04 13:50:59.860 8355883 15630677 15663434 120 2009-01-06 09:56:05.890 2011-01-04 13:51:58.223 8355883 9405061 9372328 15630679 15663436 121 2009-01-06 09:56:05.890 2011-01-04 14:06:22.317 8355883 15630681 15663438 122 2009-01-06 09:56:05.890 2011-01-04 14:08:16.923 8355883 15630683 15663440 123 2009-01-06 09:56:05.890 2011-01-04 14:14:39.097 8355883 6259438 6226640 4 2008-10-21 10:34:48.373 2008-10-21 11:17:22.477 6259430 15630685 15663442 124 2009-01-06 09:56:05.890 2011-01-04 14:21:25.907 8355883 6259436 6226638 3 2008-10-21 10:34:48.373 2008-10-21 11:15:42.773 6259430 6259442 6226644 6 2008-10-21 10:34:48.373 2008-10-21 11:25:40.797 6259430 15630688 15663445 125 2009-01-06 09:56:05.890 2011-01-04 14:22:35.890 8355883 6259440 6226642 5 2008-10-21 10:34:48.373 2008-10-21 11:21:38.227 6259430 15630690 15663447 126 2009-01-06 09:56:05.890 2011-01-04 14:34:00.310 8355883 6259446 6226648 8 2008-10-21 10:34:48.373 2008-10-21 11:31:39.330 6259430 15630692 15663449 127 2009-01-06 09:56:05.890 2011-01-04 14:36:57.500 8355883 6259444 6226646 7 2008-10-21 10:34:48.373 2008-10-21 11:29:42.110 6259430 15630694 15663451 128 2009-01-06 09:56:05.890 2011-01-04 14:40:06.397 8355883 8355852 8388620 46 2007-12-03 13:18:03.697 2008-10-30 14:40:16.987 2162995 6259450 6226652 10 2008-10-21 10:34:48.373 2008-10-21 11:46:08.577 6259430 15630696 15663453 129 2009-01-06 09:56:05.890 2011-01-04 14:41:36.920 8355883 8355851 8388619 1 2008-12-29 11:40:49.410 2008-12-29 11:40:49.410 8355849 6259448 6226650 9 2008-10-21 10:34:48.373 2008-10-21 11:45:24.377 6259430 15630698 15663455 130 2009-01-06 09:56:05.890 2011-01-04 14:46:15.183 8355883 15630713 15663470 140 2009-01-06 09:56:05.890 2011-01-04 15:12:45.727 8355883 8356030 8388791 8 2009-01-06 09:56:05.890 2009-01-10 23:39:14.003 8355883 8356028 8388789 7 2009-01-06 09:56:05.890 2009-01-10 23:38:30.677 8355883 15630712 15663469 139 2009-01-06 09:56:05.890 2011-01-04 15:10:31.853 8355883 8356027 8388788 6 2009-01-06 09:56:05.890 2009-01-10 23:37:01.537 8355883 8356034 8388795 10 2009-01-06 09:56:05.890 2009-01-11 09:13:32.620 8355883 15630710 15663467 138 2009-01-06 09:56:05.890 2011-01-04 15:08:39.807 8355883 8356032 8388793 9 2009-01-06 09:56:05.890 2009-01-11 09:02:24.983 8355883 15630708 15663465 137 2009-01-06 09:56:05.890 2011-01-04 15:02:04.967 8355883 15630705 15663462 135 2009-01-06 09:56:05.890 2011-01-04 15:01:01.450 8355883 15630706 15663463 136 2009-01-06 09:56:05.890 2011-01-04 15:01:41.253 8355883 8356037 8388798 13 2009-01-06 09:56:05.890 2009-01-11 09:16:55.067 8355883 8356036 8388797 12 2009-01-06 09:56:05.890 2009-01-11 09:16:33.790 8355883 15630704 15663461 134 2009-01-06 09:56:05.890 2011-01-04 14:56:58.643 8355883 8356035 8388796 11 2009-01-06 09:56:05.890 2009-01-11 09:16:10.970 8355883 15630701 15663458 132 2009-01-06 09:56:05.890 2011-01-04 14:55:53.327 8355883 15630702 15663459 133 2009-01-06 09:56:05.890 2011-01-04 14:56:22.787 8355883 15630700 15663457 131 2009-01-06 09:56:05.890 2011-01-04 14:51:32.953 8355883 15630730 15663487 150 2009-01-06 09:56:05.890 2011-01-04 15:36:32.493 8355883 15630728 15663485 149 2009-01-06 09:56:05.890 2011-01-04 15:33:20.987 8355883 9372164 9404905 26 2008-04-22 12:26:44.157 2008-10-30 12:54:22.550 3637534 15630726 15663483 148 2009-01-06 09:56:05.890 2011-01-04 15:32:26.117 8355883 15630725 15663482 147 2009-01-06 09:56:05.890 2011-01-04 15:31:25.800 8355883 15630723 15663480 146 2009-01-06 09:56:05.890 2011-01-04 15:29:02.943 8355883 15630721 15663478 145 2009-01-06 09:56:05.890 2011-01-04 15:22:06.010 8355883 8356022 8388783 3 2009-01-06 09:56:05.890 2009-01-06 14:55:15.297 8355883 17891472 17858720 15630719 15663476 144 2009-01-06 09:56:05.890 2011-01-04 15:20:08.817 8355883 8356025 8388786 5 2009-01-06 09:56:05.890 2009-01-10 23:36:15.167 8355883 15630717 15663474 143 2009-01-06 09:56:05.890 2011-01-04 15:19:40.380 8355883 15630716 15663473 142 2009-01-06 09:56:05.890 2011-01-04 15:18:47.567 8355883 15630715 15663472 141 2009-01-06 09:56:05.890 2011-01-04 15:13:25.897 8355883 8356024 8388785 4 2009-01-06 09:56:05.890 2009-01-10 22:33:58.317 8355883 15630744 15663501 158 2009-01-06 09:56:05.890 2011-01-04 17:00:54.597 8355883 15630745 15663502 159 2009-01-06 09:56:05.890 2011-01-04 17:02:05.877 8355883 15630746 15663503 160 2009-01-06 09:56:05.890 2011-01-04 17:02:34.333 8355883 15630739 15663496 155 2009-01-06 09:56:05.890 2011-01-04 16:46:34.040 8355883 15630741 15663498 156 2009-01-06 09:56:05.890 2011-01-04 16:48:23.373 8355883 15630742 15663499 157 2009-01-06 09:56:05.890 2011-01-04 17:00:24.003 8355883 15630735 15663492 153 2009-01-06 09:56:05.890 2011-01-04 15:46:02.600 8355883 15630737 15663494 154 2009-01-06 09:56:05.890 2011-01-04 16:44:35.277 8355883 15630732 15663489 151 2009-01-06 09:56:05.890 2011-01-04 15:39:21.300 8355883 15630733 15663490 152 2009-01-06 09:56:05.890 2011-01-04 15:41:42.147 8355883 3114598 3145740 3180065 2 2008-04-09 12:55:07.140 2009-09-24 14:17:05.293 10356262 8290318 21561411 8356048 8388807 14 2009-01-06 09:56:05.890 2009-01-11 09:17:40.733 8355883 8356049 8388808 15 2009-01-06 09:56:05.890 2009-01-12 10:02:39.260 8355883 15630751 15663508 165 2009-01-06 09:56:05.890 2011-01-04 17:08:02.073 8355883 15630748 15663505 162 2009-01-06 09:56:05.890 2011-01-04 17:03:46.793 8355883 15630747 15663504 161 2009-01-06 09:56:05.890 2011-01-04 17:03:10.683 8355883 15630750 15663507 164 2009-01-06 09:56:05.890 2011-01-04 17:05:19.463 8355883 15630749 15663506 163 2009-01-06 09:56:05.890 2011-01-04 17:04:12.177 8355883 10355557 10388285 2 2009-07-23 10:06:25.403 2009-07-23 10:21:48.443 10355550 10355555 10388283 1 2009-07-23 10:06:25.403 2009-07-23 10:06:25.403 10355550 19041432 19074118 44 2010-12-15 13:35:53.173 2012-12-12 15:59:47.137 15630488 19041430 19074116 43 2010-12-15 13:35:53.173 2012-12-12 15:31:17.543 15630488 10355559 10388287 3 2009-07-23 10:06:25.403 2009-07-23 10:33:37.483 10355550 19041428 19074114 42 2010-12-15 13:35:53.173 2012-12-12 15:07:16.417 15630488 24051764 24084532 2 2013-10-30 14:29:58.263 2013-10-30 14:31:09.597 23167205 19041426 19074112 41 2010-12-15 13:35:53.173 2012-12-12 14:50:06.183 15630488 19041424 19074110 40 2010-12-15 13:35:53.173 2012-12-12 14:38:47.263 15630488 24051765 24084533 3 2013-10-30 14:29:58.263 2013-12-01 21:01:16.210 23167205 10355548 10388276 31 2008-04-09 12:55:07.147 2009-05-29 15:36:18.517 3114599 15663795 15631042 19041422 19074108 39 2010-12-15 13:35:53.173 2012-12-12 14:37:49.050 15630488 24051767 24084535 4 2013-10-30 14:29:58.263 2013-12-01 21:03:20.967 23167205 15663797 15631044 10355551 10388279 32 2008-04-09 12:55:07.147 2009-07-23 10:01:10.093 3114599 19041420 19074106 38 2010-12-15 13:35:53.173 2012-12-12 14:26:41.153 15630488 24051769 24084537 5 2013-10-30 14:29:58.263 2013-12-01 21:06:42.723 23167205 24051771 24084539 6 2013-10-30 14:29:58.263 2013-12-01 21:08:19.573 23167205 24051773 24084541 7 2013-10-30 14:29:58.263 2013-12-01 21:12:35.380 23167205 19041446 19074132 47 2010-12-15 13:35:53.173 2012-12-13 08:06:45.403 15630488 24051775 24084543 8 2013-10-30 14:29:58.263 2013-12-01 21:16:25.347 23167205 19041444 19074130 46 2010-12-15 13:35:53.173 2012-12-12 17:32:07.223 15630488 24051777 24084545 9 2013-10-30 14:29:58.263 2013-12-01 21:19:11.277 23167205 24051778 24084546 10 2013-10-30 14:29:58.263 2013-12-02 08:00:12.980 23167205 19041442 19074128 45 2010-12-15 13:35:53.173 2012-12-12 16:20:47.047 15630488 16777456 16810217 201 2009-01-06 09:56:05.890 2011-05-23 15:46:46.827 8355883 24051780 24084548 11 2013-10-30 14:29:58.263 2013-12-02 08:01:11.777 23167205 16777458 16810219 202 2009-01-06 09:56:05.890 2011-05-23 15:51:32.477 8355883 16777452 16810213 199 2009-01-06 09:56:05.890 2011-05-23 15:45:15.530 8355883 16777454 16810215 200 2009-01-06 09:56:05.890 2011-05-23 15:45:58.773 8355883 19041396 19074082 32 2010-12-15 13:35:53.173 2012-12-10 15:41:49.710 15630488 19041391 19074077 29 2010-12-15 13:35:53.173 2012-12-10 14:24:44.033 15630488 19041392 19074078 30 2010-12-15 13:35:53.173 2012-12-10 15:28:09.787 15630488 19041394 19074080 31 2010-12-15 13:35:53.173 2012-12-10 15:34:34.630 15630488 19041387 19074073 27 2010-12-15 13:35:53.173 2012-12-10 12:56:45.090 15630488 19041389 19074075 28 2010-12-15 13:35:53.173 2012-12-10 12:59:10.537 15630488 19041415 19074101 35 2010-12-15 13:35:53.173 2012-12-12 14:22:18.097 15630488 19041418 19074104 37 2010-12-15 13:35:53.173 2012-12-12 14:26:18.270 15630488 19041417 19074103 36 2010-12-15 13:35:53.173 2012-12-12 14:23:39.487 15630488 19041411 19074097 33 2010-12-15 13:35:53.173 2012-12-10 15:53:44.217 15630488 19041413 19074099 34 2010-12-15 13:35:53.173 2012-12-12 14:18:21.250 15630488 9372262 9404998 27 2008-04-09 12:55:07.147 2009-03-03 16:31:41.660 3114599 28246023 2.7.4 -> 3.5.17 -> 5.0.3 -> latest (5.8 at time of writing this) h5. Steps # I.S. created a new VM named pompeii.shore.mbari.org that I will use to do all the stepwise upgrades # Java 1.6.0_36 was installed, so I asked for an update to the latest 1.8 version # I.S. created four databases for the upgrade path. # Per the installation instructions, for each of these databases, I performed the following using Aqua Data Studio {noformat} ALTER DATABASE COLLATE SQL_Latin1_General_CP1_CS_AS {noformat} # Per the installation instructions, for each database, I ran: {noformat} ALTER DATABASE SET READ_COMMITTED_SNAPSHOT ON WITH ROLLBACK IMMEDIATE; {noformat} # I VNC'd into pompeii.shore.mbari.org and fired up Firefox. # I downloaded the .tar.gz versions of the standalone for all the versions listed above. # I went to the Confluence Administration panel and went to Backup and Restore # I selected both the Backup check boxes and clicked "Backup" # The backup completed and I downloaded the 1.3 GB file. # I then SCP'd that file to pompeii in case I can do a local restore which will be much faster. (/home/kgomes/confluence_upgrade) ]]> 28213255 10389188 10356476 3179450 'Downloads'>'2.1 Releases'>'2.1.1' # I changed to the 'Details View', made 40 items visible, and then downloaded 'alfresco-enterprise-tomcat-2.1.1.zip' file. # I then unzipped the downloaded file to c:\bin which created an alfresco-enterprise-tomcat-2.1.1 folder in c:\bin. # I renamed the alfresco-enterprise-tomcat-2.1.1 folder to simply alfresco. # I then went back to the web browser and went to 'Company Home'>'Downloads'>'2.1 Releases'>'2.1.1'>'License Files' # I am not sure if I can do this with our agreement, but I downloaded the 'enterprise-network-customer-unlimited.lic' file. {note} I did get approval from Joe Van De Graaff at Alfresco to use the license for a test installation to get us through this issue. {note} # I logged out of the Alfresco customer web site. # I Googled on jTDS to find the jTDS JDBC driver and downloaded the jtds-1.2.2-dist.zip file from the website. # Using Windows Explorer, I could just open the jTDS zip file and copy the jtds-1.2.2.jar file. # I then pasted it in the directory c:\bin\alfresco\tomcat\common\lib directory. # I created a c:\data\alf_data directory where the alfresco data will be stored. This is different from the production installation in that the content is stored on a network appliance (\\tornado.shore.mbari.org\alfresco). # I installed a copy of SQL Server 2005 locally to use for the database to back the Alfresco test install. {note} In order to do this without warnings, I had to go back and install IIS through the Add/Remove Programs Control Panel. {note} ## I used the Local System account to run services and only used Windows Authentication logins ## I installed all the service packs and the SQL Server Management Studio product to admin DBs. # In SQL Server, I added the SHORE\DB_Collaboration accounts to the logins. # I created a new database named alfresco-test and made SHORE\DB_Collaboration the owner. # I then went to the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions directory for the customization of the server. ## I edited the custom-repository.properties file ### Changed the dir.root and dir.indexes to look like: {noformat} dir.root=c:/data/alf_data dir.indexes=c:/data/alf_data/lucene-indexes {noformat} ### Commented out the db.* lines for the HSQL Connection (db.driver and db.url) ### Uncommented the db.* lines for MSSQL and changed to use the jTDS driver. They should look like (except the password should be the right one): {noformat} db.driver=net.sourceforge.jtds.jdbc.Driver db.url=jdbc:jtds:sqlserver://localhost/alfresco-test;domain=SHORE;user=DB_Collaboration;password=XXXXXXXXX {noformat} ### I also added the following section to override the mail server settings {noformat} # Mail server configuration mail.host=mail.mbari.org mail.port=25 mail.username= mail.password= {noformat} ## Edited the custom-hibernate-dialect.properties file ### Commented out the HSQL Dialect ### Uncommented the MSSQL Dialect # Now this is not necessarily fun, but in order to really get it configured the way we want it, you need to pull the original .war file out, edit some stuff inside and re-create the .war. {note} This should all be done before starting Alfresco for the first time. {note} # Copy the c:\bin\alfresco\tomcat\webapps\alfresco.war file to your home directory. # Make a second copy so that you will always the original (I copied to alfresco.war.orig and moved it somewhere else. It is important to move it and have only the alfresco.war file in the directory because when you un-jar it, all the files go right where alfresco.war is.) # From a command line, un-jar the war file using: {noformat} jar -xvf alfresco.war {noformat} # This unpacks a lot of files and after it completes, move (or delete) the alfresco.war file from the directory. This needs to be done so it does not end up in the new .war file. # I wanted to change the "Company Home" that seems to be everywhere to something that says MBARI. ## Edited ./WEB-INF/classes/alfresco/messages/webclient.properties and changed company_home from 'Company Home' to 'MBARI Test' ## Edited ./WEB-INF/classes/alfresco/messages/webclient_en_US.properties and changed company_home from 'Company Home' to 'MBARI Test' ## I edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces.properties and changed the first two lines to read {noformat} spaces.company_home.name=MBARI Test spaces.company_home.description=The root of MBARIs Test Alfresco Server {noformat} ## Edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces_en_US.properties and made the same changes as the previous step {tip} This took a bit to find all these, and to be honest, I am not sure which one actually made the change on the GUI, but I suspect it was the _en_US ones. {tip} # When users are imported via LDAP, user spaces get created automatically. In order to put them where I wanted them to go (instead of right in the Company Home), I edited the ./WEB-INF/classes/alfresco/authentication-services-context.xml file. In the file there is a bean with an name of personalHomeFolderProvider. There is a property name 'path' and I added {noformat} /${spaces.user_homes.childname} {noformat} to the end to try to get them to create the user spaces there instead of in the Company Home. The final bean XML looks like: {noformat} /${spaces.company_home.childname}/${spaces.user_homes.childname} ${spaces.store} false All All {noformat} # I wanted to change the logo that is used. I attached the replacement [Alfresco Logo|CLT:Installation Notes^AlfrescoLogo32.png]. Copy this to ./images/logo and overwrite the one that is there. {warning} Note that I did NOT setup SSL for this installation so if I will need to come back and do that if I want truly parallel systems {warning} # Now in order to change the default behavior so that all content is versioned from the start, I edited the .\WEB-INF\classes\alfresco\model\contentModel.xml and searched for the content type definition block. {noformat} Content cm:cmobject true d:content false true false true {noformat} and added the following block right before the ending tag: {noformat} cm:versionable {noformat} so the final block looks like: {noformat} Content cm:cmobject true d:content false true false true cm:versionable {noformat} # That takes care of all the changes to the WAR file. We can now put it back into .war form. # While you are in the directory you expanded the war file in, run ## jar cvfm alfresco.war META-INF\MANIFEST.MF . # You should now have an alfresco.war file in the directory. Move that back to the alfresco install and overwrite the existing one. # Most users like the details view, so I set the default to that by editing c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions\web-client-config-custom.xml and added: {noformat} details 20
20
20 {noformat} right before the closing tag. # Now in order to use MBARI accounts, NTLM authentication was turned on and then chained with the native Alfresco accounts so that we could have non-MBARI accounts on the Alfresco server. ## For simplicity sake, I have attached the files and you can simply download and install them in the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions directory. {note} Before doing these next steps, rename the file-servers-custom.xml file to file-servers-custom.xml.orig so you will have a backup of the original {note} ### First install the [CLT:NTLM Configuration XML File|^ntlm-authentication-context.xml] ### Next install the [CLT:Authentication Chaining Configuration File|^chaining-authentication-context.xml] ### Next install the [CLT:CIFS configuration|^file-servers-custom.xml] file and over-write the existing one. ### Now in order to setup a job that imports users and groups once a day, download and install the [CLT:LDAP configuration|^ldap-synchronisation-context.xml] file. ### The ldap sych XML file simply contains all the configuration information with properties to hold the actual values for your installation. To define these properties, I installed the following [CLT:properties file|^ldap-synchronisation.properties]. If you are setting up your own installation, you will change these properties for your install. {warning} In the CIFS configuration file, make sure you change the tag to reflect a unique name on the network. {warning} ### Next install the [CLT:customized authority configuration|^custom-authority-services-context.xml] file (this gives administrative privs to certain accounts). {warning} Note that I did NOT change the server to take over port 80 traffic as the SQL Server install seemed to want IIS which is currently using port 80 {warning} # Now in order for the alfresco web application to be the default, I edit the c:\bin\alfresco\tomcat\conf\server.xml file and added: {noformat} {noformat} as the last line of the tag section (right before the closing tag). {note} You will also notice the Valve tag that I had to add to turn off proxy cache disabling so that IE clients would work correctly over SSL. Gotta love M$. {note} # Just to keep things clean, I edited the c:\bin\alfresco\alfresco.bat file and put 'rem' in front of the second JAVA_OPTS set as I am using Java 6. # You are now actually ready to start alfresco for the first time! Open a command window and cd over the to c:\bin\alfresco directory and then type: {noformat} alf_start.bat {noformat} # After a long time (took several minutes on a regular PC), look at the alfresco.log file in the c:\bin\alfresco directory and see if it looks like everything started OK, you can also check the database to see if the tables have been created in the alfresco-test database. You should also be able to go to http://alfresco-test.shore.mbari.org:8080 and see the alfresco web application. # Now from the command window where you ran alf_start.bat, run alf_stop.bat to shut the server down. Check the alfresco.log file to see if anything weird happened. If not, try restarting it with alf_start.bat again and look at the alfresco.log file. Sometimes, you can't restart it because you get: {noformat} java.sql.SQLException: Column names in each table must be unique. Column name 'ID_' in table 'JBPM_ACTION' is specified more than once. {noformat} Sigh, so in order to keep Alfresco from hurting itself, you might have to turn off the schema updates. This is done by editing the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions\custom-repository.properties and adding the following: {noformat} db.schema.update=false {noformat} and then restarting alfresco. # To install Alfresco as a Windows Service use a command prompt and enter the following: {noformat} cd c:\bin\alfresco\tomcat\bin service.bat install alfresco tomcat5.exe //US//alfresco --DisplayName "Alfresco Server" tomcat5.exe //US//alfresco --JvmMs=512 --JvmMx=1024 --JvmSs=64 tomcat5.exe //US//alfresco --JavaHome=c:/bin/Java/jrockit-R27.4.0-jdk1.6.0_02 tomcat5.exe //US//alfresco --Environment ALF_HOME=c:/bin/alfresco/ tomcat5.exe //US//alfresco --Environment PATH=c:/bin/alfresco/bin;%PATH% tomcat5.exe //US//alfresco --StartPath c:/bin/alfresco --Startup auto {noformat} # To uninstall the service, at a later time, do the following: {noformat} cd c:\bin\alfresco\tomcat\bin service.bat uninstall alfresco {noformat} # To edit your service settings at any time: {noformat} cd c:\alfresco\tomcat\bin tomcat5w.exe //ES//alfresco {noformat} {warning} These next couple of steps had to be taken to install a patch from Alfresco for an issue with bulk uploads I was having. Essentially when file and path structures get really long and nasty, Alfresco was throwing an error and bailing out. This patch (two Java classes) fixed that issue. {warning} # Next, I downloaded the attached [CLT:JAR|^act2139.jar] file and copied it to the c:\bin\alfresco\tomcat\webapps\alfresco\WEB-INF\classes directory. # I shutdown Alfresco and then unjarred the file to install the new classes. They are: ## org/alfresco/filesys/smb/server/SMBSrvPacket.class ## org/alfresco/filesys/util/DataBuffer.class # I would assume since they do not overwrite anything, that this location is further up in the class loader and so it will load these new classes first. # I deleted the act2139.jar file and the META-INF directory that the unjarring process created. # I did not do this, but you can verify this took, I run alfresco with the {noformat} CATALINA_OPTS="-verbose:class" {noformat} and verifyied that you can find some line, some where, that shows: {noformat} [Loaded org.alfresco.filesys.smb.server.SMBSrvPacket from file:/opt/alfresco211/tomcat/webapps/alfresco/WEB-INF/classes/org/alfresco/filesys/smb/server/SMBSrvPacket.class] {noformat} and NOT: {noformat} Loaded org.alfresco.filesys.smb.server.SMBSrvPacket from file:/opt/alfresco211/tomcat/webapps/alfresco/WEB-INF/lib/alfresco-repository.jar] {noformat} ]]> 3113965 15630370 15663136 107 2009-01-06 09:56:05.890 2010-10-21 23:41:22.207 8355883 15630368 15663134 4 2010-11-30 22:31:25.733 2010-11-30 22:32:59.753 15630363 15630365 15663131 2 2010-11-30 22:31:25.733 2010-11-30 22:31:49.487 15630363 15630366 15663132 3 2010-11-30 22:31:25.733 2010-11-30 22:32:24.443 15630363 15630364 15663130 1 2010-11-30 22:31:25.733 2010-11-30 22:31:25.733 15630363 19041600 19074281 45 2011-06-06 21:36:16.963 2012-11-13 14:39:51.500 17236193 15630375 15663140 5 2010-11-30 22:31:25.733 2010-11-30 22:34:29.400 15630363 15630374 15663139 109 2009-01-06 09:56:05.890 2010-11-30 22:48:56.557 8355883 15630371 15663137 108 2009-01-06 09:56:05.890 2010-11-30 22:37:00.277 8355883 16777436 16810197 191 2009-01-06 09:56:05.890 2011-05-09 13:07:33.020 8355883 16777438 16810199 192 2009-01-06 09:56:05.890 2011-05-23 15:15:24.587 8355883 16777440 16810201 193 2009-01-06 09:56:05.890 2011-05-23 15:32:17.097 8355883 16777442 16810203 194 2009-01-06 09:56:05.890 2011-05-23 15:33:37.400 8355883 16777444 16810205 195 2009-01-06 09:56:05.890 2011-05-23 15:36:53.763 8355883 19041589 19074271 10 2012-11-29 08:19:23.410 2013-01-04 11:47:55.150 19041368 16777446 16810207 196 2009-01-06 09:56:05.890 2011-05-23 15:38:55.800 8355883 6259268 6226478 2 2008-08-04 13:42:13.733 2008-09-25 13:55:40.070 5832921 16777448 16810209 197 2009-01-06 09:56:05.890 2011-05-23 15:41:27.497 8355883 16777450 16810211 198 2009-01-06 09:56:05.890 2011-05-23 15:44:04.523 8355883 2163067 2195831 29 2007-12-03 13:18:03.697 2007-12-07 08:45:30.763 2162995 6259221 6226432 1 2008-08-04 13:42:13.733 2008-08-04 13:42:13.733 5832921 19041552 19074235 9 2012-11-29 08:19:23.410 2013-01-04 11:46:58.077 19041368 19041551 19074234 8 2012-11-29 08:19:23.410 2013-01-04 11:46:43.097 19041368 2163052 2195816 28 2007-12-03 13:18:03.697 2007-12-06 16:30:40.510 2162995 19041548 19074231 6 2012-11-29 08:19:23.410 2013-01-04 11:43:00.987 19041368 19041547 19074230 5 2012-11-29 08:19:23.410 2013-01-04 11:22:07.857 19041368 19041550 19074233 7 2012-11-29 08:19:23.410 2013-01-04 11:43:27.693 19041368 811 ... internal dav:http://seaspray.shore.mbari.org:8082/archiva/repository/internal/ snapshots dav:http://seaspray.shore.mbari.org:8082/archiva/repository/snapshots/ internal Archiva Managed Internal Repository http://seaspray.shore.mbari.org:8082/archiva/repository/internal/ true false snapshots Archiva Managed Snapshot Repository http://seaspray.shore.mbari.org:8082/archiva/repository/snapshots/ false true ... {code} h2. {anchor:M2} +Using the external MBARI repository from a [Maven 2|http://maven.apache.org/] project+ h3. Referencing the Repository To include the MBARI repository in your Maven build, edit your _pom.xml_ to include the MBARI repository location: {code:xml} ... mbari MBARI Repository http://oceana.shore.mbari.org/maven2 ... ... {code} h3. Including a Dependency from the Repository Once the MBARI repository is included in you build, you can browse the repository to see what projects are available (just go to [http://oceana.shore.mbari.org/maven2]). If you find a dependency you need you can reference it in your _pom.xml_. Here's an example... {code:xml} ... ... qt4j qt4j 0.5 ... ... {code} h3. Putting a Dependency into the Repository The easiest way to put a dependency into the repository is to setup a Maven build file (i.e. _pom.xml_). In _pom.xml_ add the following _distributionManagement_ information: {code:xml} 4.0.0 qt4j qt4j jar 1.0-SNAPSHOT QT4J ... mbari-repository MBARI Repository scp://oceana.shore.mbari.org/var/www/html/maven2 {code} Executing _mvn deploy_ will put your build jar at http://oceana.shore.mbari.org/maven2////-.jar. In the example here it would put it into [http://oceana.shore.mbari.org/maven2/qt4j/qt4j/1.0-SNAPSHOT/] h3. Publishing Maven generated web sites Maven can generate a web site for a default web site for you. You can view samples of the currently published projects at [http://oceana.shore.mbari.org/projects]. It's not very interesting, however, it is a very simple way to publish the javadoc, sources and auto-generated reports. To do so modify your _pom.xml_: {code:xml} ... org.apache.maven.plugins maven-jxr-plugin org.apache.maven.plugins maven-pmd-plugin 1.5 org.apache.maven.plugins maven-checkstyle-plugin ... oceana.shore.mbari.org scp://oceana.shore.mbari.org/var/www/html/projects/${project.name} {code} Then run _mvn javadoc:javadoc site:site site:deploy_. This will build the javadocs, create a site with some useful reports, then publish the site (using scp) to oceana in the correct location. h3. Project Specific Maven Repositories Some projects may need to be configured differently for different deployment locations. For example, [VARS|VARS:Home] is configured differently for each ship and shore. These specific configurations are stored in Maven repositories in [http://oceana.shore.mbari.org/maven2-prj]. Each directory listed there is a different repository. Here's an example of how to include the projects configured for [Eye-in-the-sea|EITS:Home]. {code:xml} mbari-eits MBARI-EITS Repository http://oceana.shore.mbari.org/maven2-prj/eits {code} h2. {anchor:M3} +Using the external MBARI repository from an [Ant|http://ant.apache.org] project using Maven+ Maven repositories can be used from Ant build scripts using [Maven's antlib|http://maven.apache.org/ant-tasks.html]. To do this you must have both Maven and Ant installed. h3. Bootstrapping antlib To bootstrap antlib into your projects (so users can build without having to install antlib) modify your _build.xml_ file like so: {code:xml} ... Finding dependencies of ${pom.artifactId}-${version} ... {code} h2. {anchor:M4} +Using the external MBARI repository from an [Ant|http://ant.apache.org] project using Ivy+ Maven repositories can be used from Ant build scripts using [Ivy|http://incubator.apache.org/ivy/]. h3. Referencing the repository In the directory containing the ant build file, _build.xml_, create a file called _ivyconf.xml_. _ivyconf.xml_ tells Ivy where to look for dependencies. The contents of the file will look something like: {code:xml} {code} h3. Including a Dependency from the Repository In the directory containing _build.xml_, create a file called _ivy.xml_. _ivy.xml_ tells Ivy what dependencies to include in your build. Here's an example of it's contents: {code:xml} {code} h3. Using Ivy from Ant The code below will fetch Ivy for you. SO you do not need install any additional software in order to get you build to work. In your ant build file include the following: {code:xml} ... {code} Calling _ant ivy.install_ will fetch all the dependencies from the web and put them into the _lib_ directory of your project. ]]> 814 11829817 11797064 2163104 2195867 30 2007-12-03 13:18:03.697 2007-12-11 14:58:59.627 2162995 19041545 19074228 4 2012-11-29 08:19:23.410 2013-01-04 11:17:41.417 19041368 19041543 19074226 3 2012-11-29 08:19:23.410 2012-11-29 08:38:08.987 19041368 10389183 10356471 11829819 11797066 19041522 19074205 1 2012-12-30 11:48:04.033 2012-12-30 11:48:04.033 19041520 19041521 19074204 17 2012-03-07 14:57:05.953 2012-12-30 11:48:39.080 18580092 19041518 19074202 230 2009-01-06 09:56:05.890 2012-11-29 08:14:48.900 8355883 16777371 16810134 190 2009-01-06 09:56:05.890 2011-03-31 20:12:23.067 8355883 19041523 19074206 1 2009-06-04 09:33:08.477 2009-06-04 09:33:08.477 10354882 6259412 6226613 3 2008-08-04 13:42:13.733 2008-10-01 13:43:48.200 5832921 9901210 9798677 2009-05-26 14:42:26.223 2009-05-26 14:42:26.223 2163007 2195771 12 2007-12-03 13:18:03.697 2007-12-04 16:02:26.983 2162995 2163005 2195769 10 2007-12-03 13:18:03.697 2007-12-04 14:10:13.540 2162995 2163006 2195770 11 2007-12-03 13:18:03.697 2007-12-04 15:51:43.120 2162995 2163003 2195767 8 2007-12-03 13:18:03.697 2007-12-04 13:31:01.190 2162995 2163004 2195768 9 2007-12-03 13:18:03.697 2007-12-04 14:08:57.437 2162995 2163002 2195766 7 2007-12-03 13:18:03.697 2007-12-04 12:13:25.663 2162995 2163001 2195765 6 2007-12-03 13:18:03.697 2007-12-03 14:26:47.450 2162995 6259434 6226636 2 2008-10-21 10:34:48.373 2008-10-21 11:05:13.230 6259430 2163000 2195764 5 2007-12-03 13:18:03.697 2007-12-03 14:22:03.877 2162995 2162999 2195763 4 2007-12-03 13:18:03.697 2007-12-03 14:09:48.777 2162995 6259432 6226634 1 2008-10-21 10:34:48.373 2008-10-21 10:34:48.373 6259430 2162998 2195762 3 2007-12-03 13:18:03.697 2007-12-03 13:43:10.547 2162995 2162997 2195761 2 2007-12-03 13:18:03.697 2007-12-03 13:25:06.853 2162995 2162996 2195760 1 2007-12-03 13:18:03.697 2007-12-03 13:18:03.697 2162995 8945851 8913090 21435478 19040044 2013-08-15 08:20:15.410 2013-08-15 08:20:15.410 2163048 2195812 25 2007-12-03 13:18:03.697 2007-12-06 14:38:42.970 2162995 21435479 19040044 2013-08-15 08:20:15.410 2013-08-15 08:20:15.410 15630504 15663267 7 2010-12-15 13:35:53.173 2010-12-15 13:52:03.230 15630488 2163049 2195813 26 2007-12-03 13:18:03.697 2007-12-06 15:27:02.247 2162995 2163050 2195814 27 2007-12-03 13:18:03.697 2007-12-06 15:57:53.997 2162995 21435477 19040044 2013-08-15 08:20:15.410 2013-08-15 08:20:15.410 2163043 2195807 23 2007-12-03 13:18:03.697 2007-12-06 13:51:42.413 2162995 21435482 19040044 2013-08-15 08:20:15.413 2013-08-15 08:20:15.413 15630501 15663264 6 2010-12-15 13:35:53.173 2010-12-15 13:47:50.967 15630488 2163044 2195808 24 2007-12-03 13:18:03.697 2007-12-06 14:09:04.000 2162995 21435480 19040044 2013-08-15 08:20:15.410 2013-08-15 08:20:15.410 21435481 19040044 2013-08-15 08:20:15.410 2013-08-15 08:20:15.410 2163039 2195803 22 2007-12-03 13:18:03.697 2007-12-06 13:48:14.497 2162995 9372445 9405176 7 2009-03-19 14:46:17.863 2009-04-01 13:32:20.457 9372328 15630497 15663260 5 2010-12-15 13:35:53.173 2010-12-15 13:45:00.507 15630488 9372443 9405174 6 2009-03-19 14:46:17.863 2009-04-01 13:28:36.617 9372328 15630495 15663258 4 2010-12-15 13:35:53.173 2010-12-15 13:42:38.370 15630488 15630494 15663257 3 2010-12-15 13:35:53.173 2010-12-15 13:39:12.920 15630488 15630492 15663255 2 2010-12-15 13:35:53.173 2010-12-15 13:37:09.900 15630488 2163038 2195802 21 2007-12-03 13:18:03.697 2007-12-06 12:39:49.500 2162995 15630490 15663253 1 2010-12-15 13:35:53.173 2010-12-15 13:35:53.173 15630488 2163027 2195791 20 2007-12-03 13:18:03.697 2007-12-06 10:51:06.383 2162995 15630486 15663249 110 2009-01-06 09:56:05.890 2010-12-01 06:37:48.570 8355883 9372439 9405170 5 2009-03-19 14:46:17.863 2009-03-19 15:04:13.237 9372328 2163024 2195788 17 2007-12-03 13:18:03.697 2007-12-06 10:27:08.240 2162995 2163023 2195787 16 2007-12-03 13:18:03.697 2007-12-06 10:03:57.290 2162995 2163026 2195790 19 2007-12-03 13:18:03.697 2007-12-06 10:49:54.287 2162995 2163025 2195789 18 2007-12-03 13:18:03.697 2007-12-06 10:42:38.973 2162995 2163020 2195784 13 2007-12-03 13:18:03.697 2007-12-04 16:05:57.560 2162995 15664089 15631339 2163022 2195786 15 2007-12-03 13:18:03.697 2007-12-06 09:58:55.067 2162995 2163021 2195785 14 2007-12-03 13:18:03.697 2007-12-06 09:22:08.990 2162995 15630531 15663294 13 2010-12-15 13:35:53.173 2010-12-17 07:24:07.183 15630488 15630533 15663296 111 2009-01-06 09:56:05.890 2010-12-15 13:29:18.997 8355883 16515795 5832921 2011-03-31 19:55:13.607 2011-03-31 19:55:13.607 15630526 15663289 47 2007-12-03 13:18:03.697 2010-12-17 07:24:06.483 2162995 24052036 24084797 13 2013-10-30 14:29:58.263 2013-12-05 16:58:33.003 23167205 15630528 15663291 12 2010-12-15 13:35:53.173 2010-12-15 15:18:54.863 15630488 10389018 10356302 15630529 15663292 41 2008-03-17 13:05:41.323 2010-12-17 07:24:40.993 3113965 9372468 9405198 11 2009-03-19 14:46:17.863 2009-04-02 11:34:31.560 9372328 15630508 15663271 8 2010-12-15 13:35:53.173 2010-12-15 13:55:53.093 15630488 15630509 15663272 9 2010-12-15 13:35:53.173 2010-12-15 14:32:16.420 15630488 10388997 10356280 9372466 9405196 10 2009-03-19 14:46:17.863 2009-04-02 11:34:06.973 9372328 15630510 15663273 10 2010-12-15 13:35:53.173 2010-12-15 14:44:12.457 15630488 9372465 9405195 9 2009-03-19 14:46:17.863 2009-04-02 11:14:46.407 9372328 15630512 15663275 11 2010-12-15 13:35:53.173 2010-12-15 14:44:25.297 15630488 10389000 10356284 9372462 9405192 8 2009-03-19 14:46:17.863 2009-04-01 14:17:01.947 9372328 15631352 15631339 15664102 1 2011-02-03 20:49:50.960 2011-02-03 20:49:50.960 16515800 16416971 2011-03-31 20:01:09.663 2011-03-31 20:01:09.663 16515796 5832921 2011-03-31 19:55:13.607 2011-03-31 19:55:13.607 16515797 5832921 2011-03-31 19:55:13.607 2011-03-31 19:55:13.607 16515798 5832921 2011-03-31 19:55:13.607 2011-03-31 19:55:13.607 16515799 5832921 2011-03-31 19:55:13.607 2011-03-31 19:55:13.607 8945880 8913120 10944982 10912227 10944980 10912225 3604499 1 3114599 2008-04-14 17:20:15.040 2008-04-14 17:20:15.040 3604498 8 3637286 2008-04-14 17:20:15.017 2008-04-25 00:36:15.030 3604501 61 3637286 2008-04-14 17:22:15.027 2008-06-03 08:59:15.017 3604500 1 3114599 2008-04-14 17:22:15.017 2008-04-14 17:22:15.017 3604503 1 3637286 2008-04-14 17:25:15.027 2008-04-14 17:25:15.027 3604502 17 3114599 2008-04-14 17:23:15.023 2008-05-12 09:36:15.033 3604505 2 3637286 2008-04-15 06:46:15.047 2008-04-15 06:48:15.030 15664196 127.0.0.1 8443 8443 {noformat} {note} # I restarted Bamboo to verify that the SSL connection works. # I then shutdown the Bamboo installation and followed the instructions [here|http://confluence.atlassian.com/display/CROWD/Integrating+Crowd+with+Atlassian+Bamboo] to integrate it with Crowd. Below are the specific things I had to do for our installation ## In order to keep the default groups of bamboo-admin and bamboo-users out of our LDAP, I created those two groups in the MBARI Crowd directory and then created a bambooadmin account that belongs to both. That meets the requirements of Bamboo and does not force our I.S. group to have to have bamboo-admin and bamboo-user groups in our LDAP. ## The rest of the configuration was pretty straightforward except for the fact that Crowd is now using SSL and the connection between build-server and crowd was over SSL. This caused much grief as the connection was not trusted so I finally found some instructions on how to get around that [here|http://blogs.sun.com/andreas/entry/no_more_unable_to_find]. After I ran the program attached and installed the keystore in the java jre/lib/security directory, all was well and I could authenticate into Bamboo using MBARI's LDAP and MBARI Crowd directory. # The last step was to get all this running as a different user. ## I shutdown bamboo. ## I then did a 'chown -R root:root /opt/Bamboo' to make sure that the default ownership of all the files was root ## I did a 'chown -R DB_Collaboration:DB_Collaboration /data/Bamboo' to make sure the DB_Collaboration account owned all the bamboo data. ## I then went in to the /opt/Bamboo directory and gave ownership of the following files and directories to DB_Collaboration. ### atlassian-bamboo.log ### logs ### /opt/Bamboo (so the bamboo.pid file can be created) ## I then created the /etc/init.d/bamboo script: {noformat} #!/bin/sh # Startup script for bamboo # # chkconfig: 2345 99 01 # description: Atlassian Bamboo # pidfile: /var/run/bamboo.pid . /etc/rc.d/init.d/functions BAMBOO_HOME=/data/Bamboo BAMBOO_INSTALL=/opt/Bamboo BAMBOO_USER=DB_Collaboration export BAMBOO_HOME NAME=bamboo BPID=${BAMBOO_INSTALL}/bamboo.pid PID=/var/run/${NAME}.pid cd ${BAMBOO_INSTALL} if [ _$1 = _condrestart ]; then su - ${BAMBOO_USER} -c " cd ${BAMBOO_INSTALL} && ${BAMBOO_INSTALL}/bamboo.sh stop && ${BAMBOO_INSTALL}/bamboo.sh start " else su - ${BAMBOO_USER} -c " cd ${BAMBOO_INSTALL} && ${BAMBOO_INSTALL}/bamboo.sh $@ " fi RC=$? if [ -f $BPID ]; then cp -- $BPID $PID touch /var/lock/subsys/${NAME} else rm -- $PID /var/lock/subsys/${NAME} 2>/dev/null fi exit $RC {noformat} # I made it executable by all and changed the ownership to root:root # I then ran the following to configure it to start: {noformat} sudo /sbin/chkconfig --add bamboo sudo /sbin/chkconfig bamboo on sudo /sbin/service bamboo start {noformat} # I then downloaded the selenium rc server jar file, put it in the /opt/selenium directory and created the following script and put it in /etc/init.d/selenium {noformat} #!/bin/sh # chkconfig: 2345 99 01 # description: Selenium RC Service Agent . /etc/rc.d/init.d/functions scriptFile=$(readlink -fn $(type -p $0)) scriptDir=$(dirname $scriptFile) # This is the directory where selenium is installed applDir=/opt/selenium-rc # The service names serviceName=SeleniumRC serviceNameLo=SeleniumRC # The group that will be used to run the service serviceUser=DB_Collaboration serviceGroup=DB_Collaboration # This is the process id file pidFile=/opt/selenium-rc/selenium.pid # This is the log file where messages will be written serviceLogFile=/opt/selenium-rc/log/selenium.log # The java command to run javaCommand=java # The arguments to pass to the java command javaArgs="-jar selenium-server-standalone-2.0b2.jar" # The full java command line javaCommandLine="$javaCommand $javaArgs" javaCommandLineKeyword=selenium-server-standalone # The time to wait for the graceful shutdown to work before sending SIGKILL maxShutdownTime=15 # This is a function to create a file and make it writable by the process group function makeFileWritable { local filename="$1" touch $filename || return 1 chgrp $serviceGroup $filename || return 1 chmod g+w $filename || return 1 return 0; } # This function checks if the process with the pid that is passed in is running function checkProcessIsRunning { local pid="$1" if [ -z "$pid" -o "$pid" == " " ]; then return 1; fi if [ ! -e /proc/$pid ]; then return 1; fi return 0; } # This function checks to see if the process id is the one that we started function checkProcessIsOurService { local pid="$1" if [ "$(ps -p $pid --no-headers -o comm)" != "$javaCommand" ]; then return 1; fi grep -q "$javaCommandLineKeyword" /proc/$pid/cmdline if [ $? -ne 0 ]; then return 1; fi return 0; } # This actually starts the service running function startServiceProcess { cd $applDir || return 1 rm -f $pidFile makeFileWritable $pidFile || return 1 makeFileWritable $serviceLogFile || return 1 cmd="nohup $javaCommandLine >>$serviceLogFile 2>&1 & echo \$! >$pidFile" sudo -u $serviceUser $SHELL -c "$cmd" || return 1 # $SHELL -c "$cmd" || return 1 sleep 0.1 pid="$(<$pidFile)" if checkProcessIsRunning $pid; then :; else echo "$serviceName service started, log file $serviceLogFile." return 1 fi return 0; } # This function stops the process function stopServiceProcess { kill $pid || return 1 for ((i=0; i 15631445 3604504 1 3114599 2008-04-14 17:25:15.027 2008-04-14 17:25:15.027 16285793 15631445 2011-02-22 19:09:59.210 2011-02-22 19:09:59.210 3604491 81 3114599 2008-04-14 16:11:15.030 2008-06-03 08:59:15.013 16285792 15631445 2011-02-22 19:09:59.210 2011-02-22 19:09:59.210 3604493 74 3637286 2008-04-14 16:26:15.017 2008-05-15 14:42:15.017 3604492 1 3637286 2008-04-14 16:12:15.027 2008-04-14 16:12:15.027 16285789 15631445 2011-02-22 19:09:59.210 2011-02-22 19:09:59.210 3604495 11 3114599 2008-04-14 17:19:15.030 2008-06-03 08:41:15.080 3604494 5 3114599 2008-04-14 17:19:15.023 2008-04-24 16:32:15.013 16285791 15631445 2011-02-22 19:09:59.210 2011-02-22 19:09:59.210 3604497 2 3637286 2008-04-14 17:20:15.017 2008-04-14 17:24:15.027 16285790 15631445 2011-02-22 19:09:59.210 2011-02-22 19:09:59.210 3604496 1 3637286 2008-04-14 17:19:15.033 2008-04-14 17:19:15.033 10356109 10388835 6 2009-05-12 17:00:48.963 2009-09-04 14:49:11.703 9798447 15697387 15630643 2011-01-04 10:00:02.133 2011-01-04 10:00:02.133 10356107 10388833 5 2009-05-12 17:00:48.963 2009-06-02 11:04:13.257 9798447 9830865 9798110 10356111 10388837 7 2009-05-12 17:00:48.963 2009-09-04 15:45:33.687 9798447 14516250 14549017 105 2009-01-06 09:56:05.890 2010-08-25 11:07:30.237 8355883 14516249 14549016 104 2009-01-06 09:56:05.890 2010-08-04 15:04:17.227 8355883 23167214 23199975 4 2011-10-20 09:56:04.947 2013-10-30 14:33:30.220 18252474 12484690 12550225 1 2010-05-25 11:18:33.507 2010-05-25 11:18:33.507 12484688 23167211 23199972 3 2011-10-20 09:56:04.947 2013-10-30 14:33:05.243 18252474 12484686 12550222 101 2009-01-06 09:56:05.890 2010-04-27 14:42:40.460 8355883 23167217 23199978 3 2013-10-30 14:35:52.330 2013-10-30 14:37:27.750 23167213 23167216 23199977 2 2013-10-30 14:35:52.330 2013-10-30 14:37:13.837 23167213 23167215 23199976 1 2013-10-30 14:35:52.330 2013-10-30 14:35:52.330 23167213 12484694 12550229 3 2010-05-25 11:18:33.507 2010-05-25 11:53:31.610 12484688 12484692 12550227 2 2010-05-25 11:18:33.507 2010-05-25 11:21:15.200 12484688 23167229 23199990 5 2013-10-30 14:35:52.330 2013-10-31 06:45:10.967 23167213 23167227 23199988 4 2013-10-30 14:35:52.330 2013-10-30 14:38:02.930 23167213 12484702 12550237 6 2010-05-25 11:18:33.507 2010-05-25 14:26:12.030 12484688 12484700 12550235 5 2010-05-25 11:18:33.507 2010-05-25 14:22:41.517 12484688 12484699 12550234 4 2010-05-25 11:18:33.507 2010-05-25 12:29:24.697 12484688 16879380 16777460 2011-05-23 16:13:53.380 2011-05-23 16:13:53.380 16879381 16777460 2011-05-23 16:13:53.380 2011-05-23 16:13:53.380 16879382 16777460 2011-05-23 16:13:53.380 2011-05-23 16:13:53.380 16879383 16777460 2011-05-23 16:13:53.380 2011-05-23 16:13:53.380 16879384 16777460 2011-05-23 16:13:53.383 2011-05-23 16:13:53.383 16879385 16777460 2011-05-23 16:13:53.383 2011-05-23 16:13:53.383 16879386 16777460 2011-05-23 16:13:53.383 2011-05-23 16:13:53.383 18252472 18285228 205 2009-01-06 09:56:05.890 2011-08-04 15:12:57.303 8355883 16879387 16777460 2011-05-23 16:13:53.383 2011-05-23 16:13:53.383 4620319 1 3637556 2008-06-02 17:48:15.027 2008-06-02 17:48:15.027 15664192 tag on port 8085 so that the straight http port was closed. # I.S. then opened up port 8443 to the world h5. OpenID # I enabled CrowdID on this server as well. # Mike Godin found some redirects were not happening correctly: {noformat} I'm wondering if maybe it's a hostname issue. The redirections I see are: #1 from login page, GET https://crowd.mbari.org:8443/openidserver/server.openid?openid.assoc_handle= #2 redirected GET to https://crowd.mbari.org:8443/openidserver/secure/interaction/allowauthentication!default.action #3 redirected GET to https://localhost:8443/openidserver !!!! It should have redirected to https://crowd.mbari.org:8443/openidserver Weird thing is that the redirection in step 2 is correct. But for some reason crowd.mbari.org forgets it's host name in step 3. I guess this is why things work when a user is already logged into crowd, because only steps #1 and #2 need to occur. {noformat} On the web I found this: {noformat} I found out the solution ! In crowd-openidserver-webapp\WEB-INF\classes\crowd.properties the following values are set: application.login.url http://localhost:8095/openidserver crowd.server.url http://localhost:8095/crowd/services/ After changing "localhost" to the the correct hostname/ip-address, the redirect is working as expected. {noformat} I also made this change and I am waiting to hear from Mike G. I also changed the 'localhost' to 'crowd.mbari.org' in the /data/crowd.properties file to make sure redirects happen OK there too. ]]> 15631441 15664164 15631413 18252485 18285238 1 2011-10-20 09:56:04.947 2011-10-20 09:56:04.947 18252474 15664166 15631415 18285229 18252474 17957941 11797064 2011-06-24 10:28:41.503 2011-06-24 10:28:41.503 17957940 11797064 2011-06-24 10:28:41.503 2011-06-24 10:28:41.503 3277006 5 2162995 2008-03-21 14:54:15.037 2008-03-21 14:55:15.027 3638074 3670819 5 2008-05-12 09:51:47.077 2008-05-12 13:42:45.180 3638030 3638073 3670818 4 2008-05-12 09:51:47.077 2008-05-12 10:11:02.807 3638030 15712648 6259430 2011-02-10 13:49:53.487 2011-02-10 13:49:53.487 15712644 6259430 2011-02-10 13:49:53.487 2011-02-10 13:49:53.487 15712645 6259430 2011-02-10 13:49:53.487 2011-02-10 13:49:53.487 15712646 6259430 2011-02-10 13:49:53.487 2011-02-10 13:49:53.487 15712647 6259430 2011-02-10 13:49:53.487 2011-02-10 13:49:53.487 19040981 19073673 6 2012-09-26 07:14:38.057 2012-09-26 07:56:48.573 19040970 19040979 19073671 5 2012-09-26 07:14:38.057 2012-09-26 07:54:30.497 19040970 19040977 19073669 4 2012-09-26 07:14:38.057 2012-09-26 07:49:55.660 19040970 19040975 19073667 3 2012-09-26 07:14:38.057 2012-09-26 07:37:32.077 19040970 19040973 19073665 2 2012-09-26 07:14:38.057 2012-09-26 07:36:59.073 19040970 3638111 3670850 53 2008-04-14 16:11:58.510 2008-04-24 16:32:36.650 3637286 3638112 3670851 6 2008-05-12 09:51:47.077 2008-05-13 09:44:29.057 3638030 19040972 19073664 1 2012-09-26 07:14:38.057 2012-09-26 07:14:38.057 19040970 19041002 19073694 7 2012-09-26 11:09:35.667 2012-09-26 11:56:44.473 19040991 19041001 19073693 6 2012-09-26 11:09:35.667 2012-09-26 11:37:52.747 19040991 23691572 23167213 2013-11-13 11:16:04.827 2013-11-13 11:16:04.827 19040997 19073689 5 2012-09-26 11:09:35.667 2012-09-26 11:37:38.957 19040991 19040996 19073688 4 2012-09-26 11:09:35.667 2012-09-26 11:30:47.970 19040991 19040994 19073686 3 2012-09-26 11:09:35.667 2012-09-26 11:21:19.410 19040991 19040993 19073685 2 2012-09-26 11:09:35.667 2012-09-26 11:10:11.460 19040991 19040992 19073684 1 2012-09-26 11:09:35.667 2012-09-26 11:09:35.667 19040991 3638026 3670773 15 2008-04-09 12:55:07.147 2008-05-06 16:33:40.977 3114599 14811144 14843912 34 2010-07-27 11:54:54.630 2010-08-16 11:31:13.000 13926566 27263015 23167205 2015-04-15 09:34:03.140 2015-04-15 09:34:03.140 66300 1 27263014 23167205 2015-04-15 09:33:49.270 2015-04-15 09:33:49.270 172586 1 27263017 27066970 2015-04-15 09:53:11.577 2015-04-15 09:53:11.577 66300 1 27263016 27066970 2015-04-15 09:52:42.660 2015-04-15 09:52:42.660 172586 1 18579511 18645042 48 2007-12-03 13:18:03.697 2010-12-17 07:24:06.650 2162995 18579514 18645045 50 2007-12-03 13:18:03.697 2012-01-17 10:22:10.943 2162995 18579513 18645044 49 2007-12-03 13:18:03.697 2012-01-17 10:15:08.093 2162995 17957936 15631042 2011-06-23 11:41:11.003 2011-06-23 11:41:11.003 17957937 15631042 2011-06-23 11:41:11.003 2011-06-23 11:41:11.003 17957938 15631042 2011-06-23 11:41:11.003 2011-06-23 11:41:11.003 17957933 15631042 2011-06-23 11:41:11.003 2011-06-23 11:41:11.003 17957934 15631042 2011-06-23 11:41:11.003 2011-06-23 11:41:11.003 3638036 3670783 3 2008-05-12 09:51:47.077 2008-05-12 09:59:32.907 3638030 17957935 15631042 2011-06-23 11:41:11.003 2011-06-23 11:41:11.003 3638034 3670781 2 2008-05-12 09:51:47.077 2008-05-12 09:52:21.333 3638030 3638031 3670778 1 2008-05-12 09:51:47.077 2008-05-12 09:51:47.077 3638030 19041098 19073789 4 2012-06-04 17:50:29.237 2012-06-04 17:59:20.207 19039049 10944744 10911981 19041100 19073791 5 2012-06-04 17:50:29.237 2012-10-31 13:00:56.600 19039049 10355888 10388614 66 2009-01-06 09:56:05.890 2009-08-05 09:50:37.347 8355883 10355892 10388618 67 2009-01-06 09:56:05.890 2009-08-11 16:04:03.963 8355883 11338409 11239606 2010-01-29 18:21:04.990 2010-01-29 18:21:04.990 11338408 11239606 2010-01-29 18:21:04.990 2010-01-29 18:21:04.990 19145836 19039359 2012-06-26 08:05:53.610 2012-06-26 08:05:53.610 11338405 11239606 2010-01-29 18:21:04.990 2010-01-29 18:21:04.990 11338404 11239606 2010-01-29 18:21:04.990 2010-01-29 18:21:04.990 11338407 11239606 2010-01-29 18:21:04.990 2010-01-29 18:21:04.990 16285947 15631044 2011-03-03 08:57:29.283 2011-03-03 08:57:29.283 11338406 11239606 2010-01-29 18:21:04.990 2010-01-29 18:21:04.990 16285946 15631044 2011-03-03 08:57:29.283 2011-03-03 08:57:29.283 589831 622599 25 2007-02-07 14:07:35.807 2007-03-19 10:27:51.533 814 589832 622600 26 2007-02-07 14:07:35.807 2007-03-19 10:29:21.700 814 19137221 18580035 2012-03-27 11:03:28.337 2012-03-27 11:03:28.337 589833 622601 27 2007-02-07 14:07:35.807 2007-03-19 10:31:01.480 814 19137222 18580035 2012-03-27 11:03:28.337 2012-03-27 11:03:28.337 589834 622602 28 2007-02-07 14:07:35.807 2007-03-19 10:31:58.887 814 19145833 19039359 2012-06-26 08:05:53.610 2012-06-26 08:05:53.610 589828 622596 22 2007-02-07 14:07:35.807 2007-03-01 13:53:31.383 814 589829 622597 23 2007-02-07 14:07:35.807 2007-03-19 10:21:51.243 814 19145835 19039359 2012-06-26 08:05:53.610 2012-06-26 08:05:53.610 589830 622598 24 2007-02-07 14:07:35.807 2007-03-19 10:22:28.480 814 19145834 19039359 2012-06-26 08:05:53.610 2012-06-26 08:05:53.610 11338400 11239606 2010-01-29 18:21:04.987 2010-01-29 18:21:04.987 11338401 11239606 2010-01-29 18:21:04.987 2010-01-29 18:21:04.987 11338402 11239606 2010-01-29 18:21:04.990 2010-01-29 18:21:04.990 11338403 11239606 2010-01-29 18:21:04.990 2010-01-29 18:21:04.990 11338397 11239606 2010-01-29 18:21:04.987 2010-01-29 18:21:04.987 11338398 11239606 2010-01-29 18:21:04.987 2010-01-29 18:21:04.987 11338399 11239606 2010-01-29 18:21:04.987 2010-01-29 18:21:04.987 19041226 19073916 32 2012-09-26 11:09:35.667 2012-11-15 12:46:49.540 19040991 19041225 19073915 31 2012-09-26 11:09:35.667 2012-11-13 12:34:32.797 19040991 10355704 10388432 65 2009-01-06 09:56:05.890 2009-06-04 12:44:12.833 8355883 19041209 19073900 44 2011-06-06 21:36:16.963 2012-11-13 14:39:30.247 17236193 19041208 19073899 43 2011-06-06 21:36:16.963 2012-11-13 14:36:32.147 17236193 19041206 19073897 42 2011-06-06 21:36:16.963 2012-11-13 10:36:14.717 17236193 19041204 19073895 30 2012-09-26 11:09:35.667 2012-11-13 12:33:17.187 19040991 19041201 19073892 28 2012-09-26 11:09:35.667 2012-11-13 12:31:41.557 19040991 19041202 19073893 29 2012-09-26 11:09:35.667 2012-11-13 12:32:50.543 19040991 19041200 19073891 27 2012-09-26 11:09:35.667 2012-11-13 12:15:31.153 19040991 19041198 19073889 26 2012-09-26 11:09:35.667 2012-11-13 12:11:57.653 19040991 19041196 19073887 25 2012-09-26 11:09:35.667 2012-11-13 12:08:27.077 19040991 10485849 10354884 2009-06-04 09:35:21.117 2009-06-04 12:00:32.670 28733 21 10485828 23167210 23199971 2 2011-10-20 09:56:04.947 2011-10-20 10:17:26.533 18252474 10485848 10354884 2009-06-04 09:35:21.117 2009-06-04 10:44:57.833 25692 20 10485828 10485847 10354884 2009-06-04 09:35:21.117 2009-06-04 10:44:42.780 25694 19 10485828 23167207 23199968 1 2013-10-30 14:29:58.263 2013-10-30 14:29:58.263 23167205 10485846 10354884 2009-06-04 09:35:21.117 2009-06-04 10:44:05.387 25799 18 10485828 3637848 3670598 6 2008-04-23 13:29:35.487 2008-04-28 08:06:10.050 3637556 3637850 3670599 7 2008-04-23 13:29:35.487 2008-05-06 16:22:32.147 3637556 10485850 10354884 2009-06-04 09:35:21.117 2009-06-04 13:02:43.307 29035 22 10485828 10485841 10354884 2009-06-04 09:35:21.117 2009-06-04 10:31:05.700 19314 13 10485828 10485840 10354884 2009-06-04 09:35:21.117 2009-06-04 10:28:55.383 18432 12 10485828 10485839 10354884 2009-06-04 09:35:21.117 2009-06-04 10:23:55.247 16806 11 10485828 10485838 10354884 2009-06-04 09:35:21.117 2009-06-04 10:13:25.797 17026 10 10485828 10485845 10354884 2009-06-04 09:35:21.117 2009-06-04 10:42:50.330 26234 17 10485828 10485844 10354884 2009-06-04 09:35:21.117 2009-06-04 10:40:49.663 23863 16 10485828 10485843 10354884 2009-06-04 09:35:21.117 2009-06-04 10:40:28.740 23863 15 10485828 10485842 10354884 2009-06-04 09:35:21.117 2009-06-04 10:39:30.973 23873 14 10485828 10485832 10354884 2009-06-04 09:35:21.117 2009-06-04 09:41:05.623 5204 4 10485828 10485833 10354884 2009-06-04 09:35:21.117 2009-06-04 09:52:06.797 8185 5 10485828 3637861 3670611 1 2008-05-06 16:38:16.753 2008-05-06 16:38:16.753 3637859 10485830 10354884 2009-06-04 09:35:21.117 2009-06-04 09:37:17.107 2101 2 10485828 10485831 10354884 2009-06-04 09:35:21.117 2009-06-04 09:39:33.017 3727 3 10485828 10485836 10354884 2009-06-04 09:35:21.117 2009-06-04 10:04:20.343 15358 8 10485828 10485837 10354884 2009-06-04 09:35:21.117 2009-06-04 10:07:16.997 16488 9 10485828 10485834 10354884 2009-06-04 09:35:21.117 2009-06-04 09:55:38.060 10916 6 10485828 10485835 10354884 2009-06-04 09:35:21.117 2009-06-04 09:58:25.670 13426 7 10485828 3637852 3670601 8 2008-04-23 13:29:35.487 2008-05-06 16:23:13.487 3637556 3637853 3670602 9 2008-04-23 13:29:35.487 2008-05-06 16:28:39.630 3637556 10485828 10354884 2009-06-04 09:35:21.117 2009-06-04 13:02:52.690 29035 23 3637855 3670604 10 2008-04-23 13:29:35.487 2008-05-06 16:30:04.470 3637556 10485829 10354884 2009-06-04 09:35:21.117 2009-06-04 09:35:21.117 133 1 10485828 19041228 19073918 33 2012-09-26 11:09:35.667 2012-11-15 12:47:16.373 19040991 3277230 2 3114599 2008-04-10 13:52:15.073 2008-04-10 13:52:15.073 3637858 3670607 14 2008-04-09 12:55:07.147 2008-04-24 10:41:45.970 3114599 19041157 19073848 23 2010-12-15 13:35:53.173 2012-11-12 16:12:13.243 15630488 19041155 19073846 22 2010-12-15 13:35:53.173 2012-11-12 16:00:47.867 15630488 19041162 19073853 8 2012-09-26 11:09:35.667 2012-09-26 11:57:00.097 19040991 19041161 19073852 223 2009-01-06 09:56:05.890 2012-11-12 15:04:00.640 8355883 19041159 19073850 24 2010-12-15 13:35:53.173 2012-11-12 16:18:05.103 15630488 19041149 19073840 19 2010-12-15 13:35:53.173 2012-11-12 15:04:00.847 15630488 19041147 19073838 18 2010-12-15 13:35:53.173 2012-04-13 16:49:01.930 15630488 24085051 24052291 19041153 19073844 21 2010-12-15 13:35:53.173 2012-11-12 15:53:02.977 15630488 19159442 19040241 2012-07-24 17:24:07.287 2012-07-24 17:24:07.287 19041151 19073842 20 2010-12-15 13:35:53.173 2012-11-12 15:07:25.157 15630488 4882520 3145740 2008-06-03 12:50:03.990 2008-06-03 12:50:03.990 18841767 18580092 2012-03-07 16:19:42.870 2012-03-07 16:19:42.870 499091 1 19041146 19073837 222 2009-01-06 09:56:05.890 2012-07-18 09:38:27.100 8355883 4882521 3145740 2008-06-03 12:50:03.990 2008-06-03 12:50:03.990 27066782 27099545 1 2015-03-05 13:19:01.760 2015-03-05 13:19:01.760 27066777 18841764 18580092 2012-03-07 15:02:30.060 2012-03-07 15:02:30.060 18780 1 19041187 19073878 20 2012-09-26 11:09:35.667 2012-11-13 11:56:38.907 19040991 19041190 19073881 22 2012-09-26 11:09:35.667 2012-11-13 12:04:21.993 19040991 19041189 19073880 21 2012-09-26 11:09:35.667 2012-11-13 11:57:24.590 19040991 19041192 19073883 23 2012-09-26 11:09:35.667 2012-11-13 12:04:50.440 19040991 19041194 19073885 24 2012-09-26 11:09:35.667 2012-11-13 12:06:31.833 19040991 19041180 19073871 15 2012-09-26 11:09:35.667 2012-11-13 10:46:14.780 19040991 19041179 19073870 14 2012-09-26 11:09:35.667 2012-11-13 10:45:40.210 19040991 19041182 19073873 17 2012-09-26 11:09:35.667 2012-11-13 10:47:12.157 19040991 19041181 19073872 16 2012-09-26 11:09:35.667 2012-11-13 10:46:45.480 19040991 19041183 19073874 18 2012-09-26 11:09:35.667 2012-11-13 10:47:27.323 19040991 4882516 3145740 2008-06-03 12:49:12.807 2008-06-03 12:49:12.807 9076752 8913090 2009-01-28 13:40:35.263 2009-01-28 13:42:07.263 390136 1 19041185 19073876 19 2012-09-26 11:09:35.667 2012-11-13 10:47:52.363 19040991 19041172 19073863 9 2012-09-26 11:09:35.667 2012-11-13 10:34:11.733 19040991 18252590 18285341 207 2009-01-06 09:56:05.890 2011-11-11 08:18:12.220 8355883 18252589 18285340 206 2009-01-06 09:56:05.890 2011-10-20 09:55:42.620 8355883 19041174 19073865 10 2012-09-26 11:09:35.667 2012-11-13 10:39:20.200 19040991 19041175 19073866 11 2012-09-26 11:09:35.667 2012-11-13 10:42:03.333 19040991 19041177 19073868 12 2012-09-26 11:09:35.667 2012-11-13 10:42:23.893 19040991 19041178 19073869 13 2012-09-26 11:09:35.667 2012-11-13 10:45:20.370 19040991 19041164 19073855 224 2009-01-06 09:56:05.890 2012-11-13 10:34:11.597 8355883 19041165 19073856 40 2011-06-06 21:36:16.963 2011-08-03 15:49:32.800 17236193 9798386 9798378 9831136 9899682 9899683 1 2009-05-10 15:42:33.313 2009-05-10 15:42:33.313 19041166 19073857 225 2009-01-06 09:56:05.890 2012-11-13 10:35:41.680 8355883 9798385 9798378 9831135 1 2009-05-10 15:37:29.630 2009-05-10 15:37:29.630 19041167 19073858 41 2011-06-06 21:36:16.963 2012-11-13 10:36:06.283 17236193 19041169 19073860 226 2009-01-06 09:56:05.890 2012-11-13 10:36:14.613 8355883 19041170 19073861 227 2009-01-06 09:56:05.890 2012-11-13 10:37:04.780 8355883 13926609 13959371 12 2009-12-23 08:33:45.977 2010-07-28 10:38:40.040 10912227 1040 1037 19 2007-02-07 14:07:35.807 2007-02-09 15:30:14.377 814 18251850 18284618 1 2011-07-25 16:06:45.533 2011-07-25 16:06:45.533 18251845 1041 1038 20 2007-02-07 14:07:35.807 2007-03-01 13:30:40.393 814 13926607 13959369 11 2009-12-23 08:33:45.977 2010-07-28 10:37:33.617 10912227 1042 1039 21 2007-02-07 14:07:35.807 2007-03-01 13:39:30.470 814 18251848 18284616 26 2011-06-06 21:36:16.963 2011-07-25 16:08:40.230 17236193 13926605 13959367 10 2009-12-23 08:33:45.977 2010-07-28 10:21:58.163 10912227 18251846 18284614 25 2011-06-06 21:36:16.963 2011-07-25 16:04:53.173 17236193 13926603 13959365 9 2009-12-23 08:33:45.977 2009-12-23 09:39:09.417 10912227 18251843 18284611 24 2011-06-06 21:36:16.963 2011-07-25 12:38:08.270 17236193 13926617 13959379 16 2009-12-23 08:33:45.977 2010-07-28 11:27:21.357 10912227 18251841 18284609 23 2011-06-06 21:36:16.963 2011-06-28 14:42:16.300 17236193 18580033 18645540 208 2009-01-06 09:56:05.890 2011-11-11 08:18:46.830 8355883 13926615 13959377 15 2009-12-23 08:33:45.977 2010-07-28 11:27:02.877 10912227 3637530 3670285 34 2008-04-14 16:11:58.510 2008-04-22 08:41:22.477 3637286 4849756 2 3638030 2008-06-05 10:27:15.047 2008-06-05 10:27:15.047 13926614 13959376 14 2009-12-23 08:33:45.977 2010-07-28 11:16:07.947 10912227 4849755 1 2162995 2008-06-05 10:06:15.150 2008-06-05 10:06:15.150 13926612 13959374 13 2009-12-23 08:33:45.977 2010-07-28 10:46:28.150 10912227 21365994 21398699 32 2012-07-13 10:43:52.837 2013-07-30 08:21:35.863 19040044 3637532 3670287 1 2008-04-09 12:55:07.147 2008-04-09 12:55:07.147 3114599 13926623 13959385 20 2009-12-23 08:33:45.977 2010-07-28 11:44:21.480 10912227 3637538 3670293 2 2008-04-22 12:26:44.157 2008-04-22 12:29:27.280 3637534 13926621 13959383 19 2009-12-23 08:33:45.977 2010-07-28 11:41:54.270 10912227 13926620 13959382 18 2009-12-23 08:33:45.977 2010-07-28 11:38:20.243 10912227 3637536 3670291 1 2008-04-22 12:26:44.157 2008-04-22 12:26:44.157 3637534 13926619 13959381 17 2009-12-23 08:33:45.977 2010-07-28 11:37:10.617 10912227 3637541 3670296 4 2008-04-22 12:26:44.157 2008-04-22 16:17:00.840 3637534 13926632 13959394 21 2009-12-23 08:33:45.977 2010-07-28 11:47:57.690 10912227 3637540 3670295 3 2008-04-22 12:26:44.157 2008-04-22 16:08:45.100 3637534 13926630 13959392 102 2009-01-06 09:56:05.890 2010-05-25 11:17:56.773 8355883 3637545 3670300 6 2008-04-22 12:26:44.157 2008-04-22 16:20:45.263 3637534 3637543 3670298 5 2008-04-22 12:26:44.157 2008-04-22 16:17:38.697 3637534 13926628 13959390 11 2010-07-27 11:54:54.630 2010-07-27 14:05:37.750 13926566 13926576 13959338 7 2010-07-27 11:54:54.630 2010-07-27 12:40:14.107 13926566 18251880 18284648 35 2011-06-06 21:36:16.963 2011-07-31 09:00:12.257 17236193 13926577 13959339 8 2010-07-27 11:54:54.630 2010-07-27 12:41:03.220 13926566 18251881 18284649 36 2011-06-06 21:36:16.963 2011-07-31 09:01:39.727 17236193 18251882 18284650 37 2011-06-06 21:36:16.963 2011-07-31 09:04:33.373 17236193 13926571 13959333 3 2010-07-27 11:54:54.630 2010-07-27 12:26:15.397 13926566 13926572 13959334 4 2010-07-27 11:54:54.630 2010-07-27 12:36:07.233 13926566 18251876 18284644 33 2011-06-06 21:36:16.963 2011-07-31 08:50:51.067 17236193 13926573 13959335 5 2010-07-27 11:54:54.630 2010-07-27 12:37:39.160 13926566 13926574 13959336 6 2010-07-27 11:54:54.630 2010-07-27 12:39:23.793 13926566 18251878 18284646 34 2011-06-06 21:36:16.963 2011-07-31 08:57:44.667 17236193 18251872 18284640 31 2011-06-06 21:36:16.963 2011-07-31 08:25:55.283 17236193 18251874 18284642 32 2011-06-06 21:36:16.963 2011-07-31 08:34:05.917 17236193 13926579 13959341 9 2010-07-27 11:54:54.630 2010-07-27 12:41:13.780 13926566 13926580 13959342 10 2010-07-27 11:54:54.630 2010-07-27 12:47:07.370 13926566 18251868 18284636 29 2011-06-06 21:36:16.963 2011-07-31 07:10:03.370 17236193 18251870 18284638 30 2011-06-06 21:36:16.963 2011-07-31 08:01:55.000 17236193 18251866 18284634 28 2011-06-06 21:36:16.963 2011-07-25 16:11:14.623 17236193 13926590 13959352 7 2008-11-12 08:47:47.573 2009-05-29 15:04:23.740 7766027 19073662 aistrack@mbari.org # AUV -> auvtrack@mbari.org # Drifter -> driftertrack@mbari.org # Glider -> glidertrack@mbari.org # Mooring -> mooringtrack@mbari.org # Ship -> ship track@mbari.org Then you just need to put the proper information into the *subject* of the message and leave the body blank: _platformName_*,*_timestamp_*,*_longitude_*,*_latitude Where: # _platformName_ is the name you would like to use for your platform *NOTE IT MUST BE 9 CHARACTERS OR LESS* # _timestamp_ is the time of the location fix in decimal epoch seconds # _longitude_ is, well, the longitude # _latitude_ is, well, the latitude h5. Java Publisher To be documented ... h5. Python Publisher To be documented ...]]> 19040970 11863382 11240296 2010-04-14 13:27:41.810 2010-04-14 13:27:41.810 11863383 11240296 2010-04-14 13:27:41.810 2010-04-14 13:27:41.810 18251851 18284619 27 2011-06-06 21:36:16.963 2011-07-25 16:09:37.613 17236193 18251853 18284621 2 2011-07-25 16:06:45.533 2011-07-25 16:10:02.933 18251845 3637586 3670341 19 2008-04-22 12:26:44.157 2008-04-23 16:31:51.773 3637534 3637584 3670339 3 2008-04-23 13:29:35.487 2008-04-24 09:09:31.207 3637556 3637582 3670337 2 2008-04-23 13:29:35.487 2008-04-23 14:06:55.130 3637556 3637581 3670336 18 2008-04-22 12:26:44.157 2008-04-23 16:27:23.120 3637534 3637579 3670334 17 2008-04-22 12:26:44.157 2008-04-23 16:26:35.503 3637534 3637594 3670349 7 2008-04-09 12:55:07.147 2008-04-24 10:39:33.377 3114599 3637593 3670348 6 2008-04-09 12:55:07.147 2008-04-24 10:38:58.580 3114599 3637592 3670347 5 2008-04-09 12:55:07.147 2008-04-24 10:38:44.030 3114599 3637591 3670346 4 2008-04-09 12:55:07.147 2008-04-24 10:38:30.123 3114599 3637590 3670345 3 2008-04-09 12:55:07.147 2008-04-23 13:27:44.343 3114599 3637588 3670343 4 2008-04-23 13:29:35.487 2008-04-24 09:29:54.050 3637556 3637602 3670357 35 2008-04-14 16:11:58.510 2008-04-22 11:29:42.113 3637286 3637599 3670354 12 2008-04-09 12:55:07.147 2008-04-24 10:41:14.623 3114599 3637600 3670355 13 2008-04-09 12:55:07.147 2008-04-24 10:41:35.393 3114599 3637597 3670352 10 2008-04-09 12:55:07.147 2008-04-24 10:40:28.140 3114599 3637598 3670353 11 2008-04-09 12:55:07.147 2008-04-24 10:40:51.300 3114599 3637595 3670350 8 2008-04-09 12:55:07.147 2008-04-24 10:39:52.697 3114599 3637596 3670351 9 2008-04-09 12:55:07.147 2008-04-24 10:40:09.683 3114599 3637609 3670364 40 2008-04-14 16:11:58.510 2008-04-24 10:48:41.947 3637286 3637610 3670365 41 2008-04-14 16:11:58.510 2008-04-24 10:49:55.047 3637286 11340882 11240274 2010-03-05 12:23:36.710 2010-03-05 12:23:36.710 3637607 3670362 39 2008-04-14 16:11:58.510 2008-04-24 10:48:29.863 3637286 11340881 11240274 2010-03-05 12:23:36.710 2010-03-05 12:23:36.710 4849707 1 3637556 2008-06-03 14:08:15.020 2008-06-03 14:08:15.020 11340880 11240274 2010-03-05 12:23:36.710 2010-03-05 12:23:36.710 3637605 3670360 37 2008-04-14 16:11:58.510 2008-04-24 10:47:52.923 3637286 13926570 13959332 2 2010-07-27 11:54:54.630 2010-07-27 12:17:42.180 13926566 11340879 11240274 2010-03-05 12:23:36.710 2010-03-05 12:23:36.710 27100025 27067271 3637606 3670361 38 2008-04-14 16:11:58.510 2008-04-24 10:48:07.410 3637286 13926568 13959330 1 2010-07-27 11:54:54.630 2010-07-27 11:54:54.630 13926566 3637604 3670359 36 2008-04-14 16:11:58.510 2008-04-24 10:46:24.407 3637286 3637554 3670309 2 2008-04-09 12:55:07.147 2008-04-22 12:26:00.650 3114599 3637548 3670303 8 2008-04-22 12:26:44.157 2008-04-22 16:48:36.050 3637534 3637547 3670302 7 2008-04-22 12:26:44.157 2008-04-22 16:24:29.763 3637534 3637550 3670305 9 2008-04-22 12:26:44.157 2008-04-22 16:49:06.947 3637534 3637559 3670314 1 2008-04-23 13:29:35.487 2008-04-23 13:29:35.487 3637556 3637561 3670316 10 2008-04-22 12:26:44.157 2008-04-22 16:50:34.067 3637534 3637563 3670318 11 2008-04-22 12:26:44.157 2008-04-23 14:47:23.520 3637534 3637565 3670320 12 2008-04-22 12:26:44.157 2008-04-23 14:56:56.853 3637534 3637575 3670330 15 2008-04-22 12:26:44.157 2008-04-23 16:24:17.427 3637534 3637577 3670332 16 2008-04-22 12:26:44.157 2008-04-23 16:25:39.503 3637534 3637571 3670326 13 2008-04-22 12:26:44.157 2008-04-23 15:03:22.013 3637534 3637573 3670328 14 2008-04-22 12:26:44.157 2008-04-23 16:05:48.423 3637534 13926490 13959254 12 2010-05-25 11:18:33.507 2010-07-14 12:12:19.660 12484688 7372809 7405577 5 2008-08-04 13:42:13.733 2008-11-05 14:49:49.300 5832921 15631683 15664422 4 2011-02-09 06:25:02.520 2011-02-16 05:47:31.520 15631441 7372808 7405576 4 2008-08-04 13:42:13.733 2008-10-21 08:16:32.567 5832921 13926488 13959252 11 2010-05-25 11:18:33.507 2010-07-14 12:10:26.627 12484688 13959328 13926566 13926486 13959250 10 2010-05-25 11:18:33.507 2010-07-14 10:28:53.980 12484688 13926484 13959248 9 2010-05-25 11:18:33.507 2010-07-14 10:26:23.393 12484688 3637645 3670400 43 2008-04-14 16:11:58.510 2008-04-24 10:58:18.110 3637286 13926482 13959246 8 2010-05-25 11:18:33.507 2010-06-01 09:37:47.283 12484688 15631681 15664420 3 2011-02-09 06:25:02.520 2011-02-15 10:09:49.617 15631441 3932235 3965002 39 2008-03-17 13:05:41.323 2008-05-28 10:28:12.867 3113965 3932237 3965004 40 2008-03-17 13:05:41.323 2008-05-28 10:28:36.983 3113965 15631667 15664406 2 2011-02-09 06:25:02.520 2011-02-10 15:28:23.727 15631441 3637662 3670417 46 2008-04-14 16:11:58.510 2008-04-24 11:43:47.117 3637286 3637661 3670416 45 2008-04-14 16:11:58.510 2008-04-24 11:43:33.793 3637286 3637660 3670415 44 2008-04-14 16:11:58.510 2008-04-24 11:31:35.540 3637286 3932219 3964986 10 2008-05-12 09:51:47.077 2008-05-22 15:35:23.377 3638030 3932230 3964997 36 2008-03-17 13:05:41.323 2008-03-19 17:06:26.423 3113965 3637613 3670368 42 2008-04-14 16:11:58.510 2008-04-24 10:50:05.770 3637286 3932228 3964995 12 2008-05-12 09:51:47.077 2008-05-28 08:17:46.287 3638030 3932227 3964994 11 2008-05-12 09:51:47.077 2008-05-27 14:07:19.437 3638030 3932234 3965001 38 2008-03-17 13:05:41.323 2008-05-28 10:19:08.717 3113965 3932232 3964999 37 2008-03-17 13:05:41.323 2008-05-28 09:27:39.447 3113965 7372870 7405638 63 2008-04-14 16:11:58.510 2008-11-09 13:32:34.153 3637286 18251900 18284668 39 2011-06-06 21:36:16.963 2011-07-31 09:18:32.257 17236193 18580094 18645601 1 2012-03-07 14:57:05.953 2012-03-07 14:57:05.953 18580092 18580096 18645603 2 2012-03-07 14:57:05.953 2012-03-07 15:05:12.263 18580092 7372862 7405630 61 2008-04-14 16:11:58.510 2008-11-09 13:32:00.333 3637286 18580100 18645607 3 2012-03-07 14:57:05.953 2012-03-07 15:37:57.477 18580092 7372865 7405633 62 2008-04-14 16:11:58.510 2008-11-09 13:32:17.017 3637286 18580103 18645610 4 2012-03-07 14:57:05.953 2012-03-07 16:16:05.880 18580092 18580105 18645612 5 2012-03-07 14:57:05.953 2012-03-07 16:18:32.647 18580092 3932176 3964943 7 2008-05-12 09:51:47.077 2008-05-16 09:13:16.977 3638030 3637737 3670490 20 2008-04-22 12:26:44.157 2008-04-24 10:20:19.467 3637534 3637736 3670489 5 2008-04-23 13:29:35.487 2008-04-24 10:25:08.127 3637556 3637735 3670488 52 2008-04-14 16:11:58.510 2008-04-24 16:30:40.337 3637286 3932178 3964945 8 2008-05-12 09:51:47.077 2008-05-22 08:33:40.270 3638030 18251884 18284652 38 2011-06-06 21:36:16.963 2011-07-31 09:16:02.747 17236193 7372857 7405625 60 2008-04-14 16:11:58.510 2008-06-25 17:09:38.503 3637286 3637733 3670486 51 2008-04-14 16:11:58.510 2008-04-24 16:29:56.977 3637286 3932172 3964939 21 2008-04-22 12:26:44.157 2008-04-28 09:51:37.400 3637534 3637731 3670484 50 2008-04-14 16:11:58.510 2008-04-24 16:29:04.123 3637286 3932174 3964941 11 2008-04-23 13:29:35.487 2008-05-06 16:32:10.097 3637556 3637730 3670483 49 2008-04-14 16:11:58.510 2008-04-24 15:53:17.323 3637286 3932184 3964951 9 2008-05-12 09:51:47.077 2008-05-22 09:16:44.287 3638030 19073683 19040991 18251898 18284666 30 2008-04-22 12:26:44.157 2009-09-24 14:18:06.017 3637534 27066968 27099730 27 2013-10-30 14:29:58.263 2015-04-15 09:35:07.803 23167205 3637687 3670442 48 2008-04-14 16:11:58.510 2008-04-24 15:51:10.243 3637286 27066967 27099729 26 2013-10-30 14:29:58.263 2015-04-15 09:31:17.907 23167205 18580125 18645632 16 2012-03-07 14:57:05.953 2012-03-07 17:16:32.707 18580092 18251934 18284698 204 2009-01-06 09:56:05.890 2011-06-21 17:27:48.170 8355883 18580123 18645630 15 2012-03-07 14:57:05.953 2012-03-07 17:15:33.297 18580092 27066964 27099726 24 2013-10-30 14:29:58.263 2015-04-15 09:28:18.767 23167205 18251936 18284700 3 2011-03-15 10:34:53.783 2011-08-04 15:12:57.423 16416807 27066963 27099725 23 2013-10-30 14:29:58.263 2015-04-15 09:18:38.673 23167205 18251935 18284699 2 2011-03-15 10:34:53.783 2011-03-29 10:06:55.503 16416807 3637685 3670440 47 2008-04-14 16:11:58.510 2008-04-24 11:44:37.933 3637286 27066965 27099727 25 2013-10-30 14:29:58.263 2015-04-15 09:28:53.400 23167205 15712007 15204478 2011-02-08 11:47:45.163 2011-02-08 11:47:45.163 27066961 27099723 22 2013-10-30 14:29:58.263 2014-07-01 17:37:00.067 23167205 15712009 15204478 2011-02-08 11:47:45.163 2011-02-08 11:47:45.163 15712008 15204478 2011-02-08 11:47:45.163 2011-02-08 11:47:45.163 15712011 15204478 2011-02-08 11:47:45.163 2011-02-08 11:47:45.163 15712010 15204478 2011-02-08 11:47:45.163 2011-02-08 11:47:45.163 18580110 18645617 8 2012-03-07 14:57:05.953 2012-03-07 16:29:47.360 18580092 18580107 18645614 6 2012-03-07 14:57:05.953 2012-03-07 16:25:53.020 18580092 18580108 18645615 7 2012-03-07 14:57:05.953 2012-03-07 16:28:41.333 18580092 15712000 15631413 2011-02-07 08:51:30.330 2011-02-07 08:51:30.330 18580114 18645621 10 2012-03-07 14:57:05.953 2012-03-07 16:51:12.207 18580092 18580112 18645619 9 2012-03-07 14:57:05.953 2012-03-07 16:46:32.607 18580092 18580118 18645625 12 2012-03-07 14:57:05.953 2012-03-07 17:07:37.333 18580092 18580116 18645623 11 2012-03-07 14:57:05.953 2012-03-07 17:04:43.127 18580092 27066971 27099732 28 2013-10-30 14:29:58.263 2015-04-15 09:50:55.187 23167205 18580122 18645629 14 2012-03-07 14:57:05.953 2012-03-07 17:14:48.187 18580092 27066972 27099733 1 2015-04-15 09:51:04.943 2015-04-15 09:51:04.943 27066970 27066973 27099734 2 2015-04-15 09:51:04.943 2015-04-15 09:51:42.060 27066970 18580120 18645627 13 2012-03-07 14:57:05.953 2012-03-07 17:08:38.300 18580092 10388278 @kahuna.shore.mbari.org/svn/repos/MBARItracking/trunk MBARItracking {noformat} where is your account name on kahuna. This package has be checked out to the following accounts on pismo.shore.mbari.org into the \~/dev directory (the password is the same for all these accounts - ask Mike McCann or Pat Allen for it): * m1track * m2track * shiptrack * aistrack * auvtrack  Please refer to the README files in the package for further details on the implementation.  For example here is the current version of the README file in the scripts directory: {noformat} scripts folder of the MBARItracking project =========================================== $Id: README 5246 2009-07-08 18:14:29Z mccann $ The scripts here populate the MBARItracking database with position data. The various scripts are implemented in various ways from various accounts as indicated below: Script Account Implementation ------ ------- -------------- grabShipPosition.py shiptrack Connect to socket, parse $GPRMC, insert to DB, write to log file shipWatchdog.py shiptrack Check log file like: 0,10,20,30,40,50 * * * * /shipWatchdog.py grabAISposition.py aistrack Connect to socket, parse AIS, insert to DB, write to log file aisWatchdog.py aistrack Check log file like: 0,10,20,30,40,50 * * * * /aisWatchdog.py grabOasisTrackers.pl m1track Symlinked by grabM{1,2}tracker.pl, in .forward file, parse MIME m2track messages from email sent from Iridium modems, insert to DB. {noformat} To monitor the successful operation of this system open this link in Google Earth: [http://elvis.shore.mbari.org/tracking/viewTracking.kml|Should launch GoogleEarth on your system] (This link is on our public web site on the "Today in the Bay" web page: [http://www.mbari.org/cruises/all/plot/all700.html|http://www.mbari.org/cruises/all/plot/all700.html ]). If you can see data for the last hour then the real-time feeds and database are operating. \-\- Mike McCann 23 July 2009]]> 10355550 27067266 27100020 234 2009-01-06 09:56:05.890 2014-05-20 05:30:45.827 8355883 4456525 4489288 13 2008-05-12 09:51:47.077 2008-05-28 08:18:22.087 3638030 4456526 4489289 13 2008-05-12 09:51:47.077 2008-05-28 08:18:22.087 3638030 27067267 27100021 235 2009-01-06 09:56:05.890 2015-06-09 11:22:28.377 8355883 27067269 27100023 236 2009-01-06 09:56:05.890 2015-06-09 11:23:29.643 8355883 3637288 3670053 1 2008-04-14 16:11:58.510 2008-04-14 16:11:58.510 3637286 3637289 3670054 2 2008-04-14 16:11:58.510 2008-04-14 16:25:59.583 3637286 27067273 27100027 1 2015-06-09 11:38:01.650 2015-06-09 11:38:01.650 27067271 3637290 3670055 3 2008-04-14 16:11:58.510 2008-04-14 16:26:28.953 3637286 23625759 23658526 8 2013-10-30 14:35:52.330 2013-11-06 07:41:05.233 23167213 23625755 23658522 6 2013-10-30 14:35:52.330 2013-10-31 06:47:14.167 23167213 23625757 23658524 7 2013-10-30 14:35:52.330 2013-11-06 07:38:17.150 23167213 5439502 3638030 2008-06-16 17:12:42.437 2008-06-16 17:12:42.437 27473 1 5439503 3638030 2008-06-16 17:14:45.697 2008-06-16 17:14:45.697 25887 1 27067277 27100031 3 2015-06-09 11:38:01.650 2015-06-09 13:38:00.767 27067271 5439489 3113965 2008-05-28 09:24:34.093 2008-05-28 09:24:34.093 3154 1 4063241 9961505 1 9798378 2009-05-10 09:00:15.080 2009-05-10 09:00:15.080 27067275 27100029 2 2015-06-09 11:38:01.650 2015-06-09 13:36:08.007 27067271 5439492 3638030 2008-06-11 16:16:01.800 2008-06-11 16:16:01.800 125952 1 9961511 1 6259430 2009-05-12 12:58:15.067 2009-05-12 12:58:15.067 27067284 27100038 4 2015-06-09 11:38:01.650 2015-06-09 13:42:54.457 27067271 5439501 3638030 2008-06-16 17:05:30.913 2008-06-16 17:05:30.913 31466 1 5439500 3638030 2008-06-16 17:02:54.973 2008-06-16 17:02:54.973 81155 1 15631482 15664228 19 2008-10-21 10:34:48.373 2011-02-09 06:18:10.220 6259430 11013008 10912225 2009-12-23 08:30:26.173 2009-12-23 08:30:26.173 11013009 10912225 2009-12-23 08:30:26.173 2009-12-23 08:30:26.173 11863053 11796703 2010-04-13 09:03:08.660 2010-04-13 09:03:08.660 11863052 11796703 2010-04-13 09:03:08.660 2010-04-13 09:03:08.660 3637323 3670086 27 2008-04-14 16:11:58.510 2008-04-14 17:15:08.490 3637286 11863055 11796703 2010-04-13 09:03:08.660 2010-04-13 09:03:08.660 11863054 11796703 2010-04-13 09:03:08.660 2010-04-13 09:03:08.660 15631496 15664239 1 2011-02-09 06:25:02.520 2011-02-09 06:25:02.520 15631441 11863049 11796703 2010-04-13 09:03:08.660 2010-04-13 09:03:08.660 11863048 11796703 2010-04-13 09:03:08.660 2010-04-13 09:03:08.660 3637335 3670096 30 2008-04-14 16:11:58.510 2008-04-15 15:07:46.207 3637286 15631498 15664241 1 2011-02-09 09:50:05.230 2011-02-09 09:50:05.230 15631445 11863051 11796703 2010-04-13 09:03:08.660 2010-04-13 09:03:08.660 11863050 11796703 2010-04-13 09:03:08.660 2010-04-13 09:03:08.660 11863045 11796703 2010-04-13 09:03:08.660 2010-04-13 09:03:08.660 3637332 3670094 28 2008-04-14 16:11:58.510 2008-04-14 17:24:58.687 3637286 11863047 11796703 2010-04-13 09:03:08.660 2010-04-13 09:03:08.660 3180066 3114599 11863046 11796703 2010-04-13 09:03:08.660 2010-04-13 09:03:08.660 3637333 3670095 29 2008-04-14 16:11:58.510 2008-04-15 15:06:47.483 3637286 3637313 3670078 22 2008-04-14 16:11:58.510 2008-04-14 17:09:54.547 3637286 3637314 3670079 23 2008-04-14 16:11:58.510 2008-04-14 17:11:56.347 3637286 3637311 3670076 21 2008-04-14 16:11:58.510 2008-04-14 17:09:02.413 3637286 3637309 3670074 19 2008-04-14 16:11:58.510 2008-04-14 17:06:29.640 3637286 15631502 15664245 3 2011-02-09 09:50:05.230 2011-02-10 16:19:15.360 15631445 3637310 3670075 20 2008-04-14 16:11:58.510 2008-04-14 17:06:44.640 3637286 3637307 3670072 17 2008-04-14 16:11:58.510 2008-04-14 17:05:51.003 3637286 15631500 15664243 2 2011-02-09 09:50:05.230 2011-02-10 16:12:53.160 15631445 3637308 3670073 18 2008-04-14 16:11:58.510 2008-04-14 17:06:14.273 3637286 27099731 ** response ** 0 * Channel 1 Power Control = 0 (Off) ** $1PC0 ** Response: ** 0 * Channel 1 Power Control = 1 (On) ** $1PC1 ** Response: ** 1 * Channel 1 Power Read ** $1PR ** Response: ** 1 * Read Block ** $1RB read temperature sensor block (4 channels) ** $5RB read pH sensor block (Seabird 18s) ** Response: ** \*+02712.00 ** \*+00200.00 ** \*+00125.76 ** \*+00347.95 * Read Data ** $1RD read tDGH channel 1 (temperature ch 1) ** $2RD read tDGH channel 2 (temperature ch 2) ** $3RD read tDGH channel 3 (temperature ch 3) ** $4RD read tDGH channel 4 (temperature ch 4) ** $5RD read tDGH channel 5 (pH sensor ch 1) ** $6RD read tDGH channel 6 (pH sensor ch 2) ** $7RD read tDGH channel 7 (pH sensor ch 3) ** $8RD read tDGH channel 8 (pH sensor ch 4) ** $9RD read tDGH channel 9 (pH sensor ch 5)]]> 27066970 3637317 3670082 25 2008-04-14 16:11:58.510 2008-04-14 17:13:29.827 3637286 3637318 3670083 26 2008-04-14 16:11:58.510 2008-04-14 17:14:34.733 3637286 3637315 3670080 24 2008-04-14 16:11:58.510 2008-04-14 17:12:44.177 3637286 3637298 3670063 10 2008-04-14 16:11:58.510 2008-04-14 17:00:05.487 3637286 3637297 3670062 9 2008-04-14 16:11:58.510 2008-04-14 16:59:47.403 3637286 3637296 3670061 8 2008-04-14 16:11:58.510 2008-04-14 16:54:12.217 3637286 4456452 4489220 43 2007-12-03 13:18:03.697 2008-05-28 21:27:07.703 2162995 3637294 3670059 7 2008-04-14 16:11:58.510 2008-04-14 16:27:19.463 3637286 23625794 23658561 9 2013-10-30 14:35:52.330 2013-11-06 07:47:39.900 23167213 3637293 3670058 6 2008-04-14 16:11:58.510 2008-04-14 16:27:05.377 3637286 4456454 4489222 44 2007-12-03 13:18:03.697 2008-05-28 21:29:07.137 2162995 3637292 3670057 5 2008-04-14 16:11:58.510 2008-04-14 16:26:53.427 3637286 3637291 3670056 4 2008-04-14 16:11:58.510 2008-04-14 16:26:39.977 3637286 3637306 3670071 16 2008-04-14 16:11:58.510 2008-04-14 17:02:52.320 3637286 4456450 4489218 42 2007-12-03 13:18:03.697 2008-03-19 17:06:32.780 2162995 3637304 3670069 15 2008-04-14 16:11:58.510 2008-04-14 17:02:01.310 3637286 3637302 3670067 14 2008-04-14 16:11:58.510 2008-04-14 17:01:46.340 3637286 3637301 3670066 13 2008-04-14 16:11:58.510 2008-04-14 17:01:16.400 3637286 3637300 3670065 12 2008-04-14 16:11:58.510 2008-04-14 17:00:43.083 3637286 3637299 3670064 11 2008-04-14 16:11:58.510 2008-04-14 17:00:25.923 3637286 15631411 15664162 182 2009-01-06 09:56:05.890 2011-02-03 09:23:04.703 8355883 18252224 18284984 1 2011-09-13 13:58:01.047 2011-09-13 13:58:01.047 18252222 15631422 15664173 22 2010-11-08 11:50:34.297 2011-02-03 12:50:56.173 15204478 15631443 15664194 184 2009-01-06 09:56:05.890 2011-02-09 06:18:51.750 8355883 19074035 19041349 19166768 19039049 2012-10-31 13:12:54.390 2012-10-31 13:12:54.390 15631437 15664188 18 2008-10-21 10:34:48.373 2009-05-21 11:27:14.453 6259430 13926722 13959484 32 2010-07-27 11:54:54.630 2010-08-04 15:37:15.067 13926566 19166769 19039049 2012-10-31 13:12:54.390 2012-10-31 13:12:54.390 13926719 13959481 30 2010-07-27 11:54:54.630 2010-08-04 15:35:44.643 13926566 19166770 19039049 2012-10-31 13:12:54.393 2012-10-31 13:12:54.393 13926720 13959482 31 2010-07-27 11:54:54.630 2010-08-04 15:36:13.817 13926566 19166771 19039049 2012-10-31 13:12:54.393 2012-10-31 13:12:54.393 19166764 19039049 2012-10-31 13:12:54.390 2012-10-31 13:12:54.390 13926718 13959480 29 2010-07-27 11:54:54.630 2010-08-04 15:14:09.960 13926566 19166765 19039049 2012-10-31 13:12:54.390 2012-10-31 13:12:54.390 19166766 19039049 2012-10-31 13:12:54.390 2012-10-31 13:12:54.390 19166767 19039049 2012-10-31 13:12:54.390 2012-10-31 13:12:54.390 15631439 15664190 183 2009-01-06 09:56:05.890 2011-02-07 08:50:08.007 8355883 13926714 13959476 28 2010-07-27 11:54:54.630 2010-08-04 15:08:15.480 13926566 13926712 13959474 27 2010-07-27 11:54:54.630 2010-07-30 12:53:36.847 13926566 13926710 13959472 103 2009-01-06 09:56:05.890 2010-07-28 12:36:31.773 8355883 11763732 10356476 2010-01-22 15:42:25.650 2010-03-29 11:03:52.047 19792 12 11403272 3637479 3670234 33 2008-04-14 16:11:58.510 2008-04-22 08:40:36.330 3637286 15631351 15664101 3 2011-02-03 13:59:06.237 2011-02-03 18:11:49.277 15631339 4456591 4489350 12 2008-04-23 13:29:35.487 2008-05-21 15:15:14.527 3637556 15631348 15664098 2 2011-02-03 13:59:06.237 2011-02-03 14:00:17.747 15631339 3637475 3670229 31 2008-04-14 16:11:58.510 2008-04-15 15:14:24.487 3637286 3637477 3670232 32 2008-04-14 16:11:58.510 2008-04-22 08:32:48.503 3637286 11763741 11797066 2010-04-27 15:14:24.887 2010-04-27 15:14:24.887 1982844 1 11763740 10356476 2010-01-22 15:42:25.650 2010-04-19 16:34:42.980 20379 13 11403272 15631341 15664091 1 2011-02-03 13:59:06.237 2011-02-03 13:59:06.237 15631339 19166775 19039049 2012-10-31 13:12:54.393 2012-10-31 13:12:54.393 13926676 13959438 25 2010-07-27 11:54:54.630 2010-07-30 08:36:35.620 13926566 19166774 19039049 2012-10-31 13:12:54.393 2012-10-31 13:12:54.393 19166773 19039049 2012-10-31 13:12:54.393 2012-10-31 13:12:54.393 13926678 13959440 26 2010-07-27 11:54:54.630 2010-07-30 09:55:57.693 13926566 19166772 19039049 2012-10-31 13:12:54.393 2012-10-31 13:12:54.393 11763713 10356476 2010-01-22 15:42:25.650 2010-03-16 09:06:57.113 19884 11 11403272 13926669 13959431 21 2010-07-27 11:54:54.630 2010-07-28 15:50:01.750 13926566 13926671 13959433 22 2010-07-27 11:54:54.630 2010-07-30 08:15:00.773 13926566 13926674 13959436 24 2010-07-27 11:54:54.630 2010-07-30 08:35:55.923 13926566 13926673 13959435 23 2010-07-27 11:54:54.630 2010-07-30 08:34:29.843 13926566 13926654 13959416 20 2010-07-27 11:54:54.630 2010-07-28 15:45:13.607 13926566 13926651 13959413 18 2010-07-27 11:54:54.630 2010-07-28 15:42:32.893 13926566 13926652 13959414 19 2010-07-27 11:54:54.630 2010-07-28 15:42:43.397 13926566 13926646 13959408 15 2010-07-27 11:54:54.630 2010-07-28 15:06:23.083 13926566 13926644 13959406 14 2010-07-27 11:54:54.630 2010-07-28 15:05:54.467 13926566 13926643 13959405 13 2010-07-27 11:54:54.630 2010-07-28 14:41:18.817 13926566 13926650 13959412 17 2010-07-27 11:54:54.630 2010-07-28 15:38:38.793 13926566 13926649 13959411 16 2010-07-27 11:54:54.630 2010-07-28 15:25:31.487 13926566 13926648 13959410 22 2009-12-23 08:33:45.977 2010-07-28 13:45:02.597 10912227 13926641 13959403 12 2010-07-27 11:54:54.630 2010-07-28 12:35:36.840 13926566 15631327 15664077 21 2010-11-08 11:50:34.297 2011-02-03 12:50:28.847 15204478 9371740 9404496 9 2008-08-04 13:42:13.733 2008-12-05 15:46:50.013 5832921 15204505 15237269 2 2010-11-08 11:50:34.297 2010-11-08 14:24:09.363 15204478 15631324 15664074 19 2010-11-08 11:50:34.297 2011-02-03 12:44:29.427 15204478 15711688 15631339 2011-02-03 20:48:25.010 2011-02-03 20:48:25.010 19040143 19072861 213 2009-01-06 09:56:05.890 2012-07-13 10:35:50.237 8355883 15711689 15631339 2011-02-03 20:48:25.010 2011-02-03 20:48:25.010 15711690 15631339 2011-02-03 20:48:25.010 2011-02-03 20:48:25.010 15631325 15664075 20 2010-11-08 11:50:34.297 2011-02-03 12:48:11.907 15204478 19040145 19072863 214 2009-01-06 09:56:05.890 2012-07-18 08:53:19.213 8355883 15711691 15631339 2011-02-03 20:48:25.010 2011-02-03 20:48:25.010 19040147 19072865 215 2009-01-06 09:56:05.890 2012-07-18 08:59:53.880 8355883 19040149 19072867 216 2009-01-06 09:56:05.890 2012-07-18 09:10:18.320 8355883 15631311 15664061 181 2009-01-06 09:56:05.890 2011-02-03 09:22:03.493 8355883 5407464 5374734 15631307 15664057 179 2009-01-06 09:56:05.890 2011-02-03 09:20:17.647 8355883 15204515 15237279 7 2010-11-08 11:50:34.297 2010-11-11 08:51:09.087 15204478 15631309 15664059 180 2009-01-06 09:56:05.890 2011-02-03 09:21:02.247 8355883 15204517 15237281 8 2010-11-08 11:50:34.297 2010-11-11 11:19:02.857 15204478 15204512 15237276 6 2010-11-08 11:50:34.297 2010-11-11 08:46:23.567 15204478 19040163 19072875 217 2009-01-06 09:56:05.890 2012-07-18 09:21:08.407 8355883 15631320 15664070 17 2010-11-08 11:50:34.297 2011-02-03 12:29:11.727 15204478 16449731 16416971 19040165 19072877 1 2012-07-18 09:21:48.597 2012-07-18 09:21:48.597 19040151 15631322 15664072 18 2010-11-08 11:50:34.297 2011-02-03 12:41:59.263 15204478 19040166 19072878 1 2012-07-18 09:22:12.510 2012-07-18 09:22:12.510 19040153 19040167 19072879 1 2012-07-18 09:22:30.357 2012-07-18 09:22:30.357 19040155 15204507 15237271 3 2010-11-08 11:50:34.297 2010-11-11 08:06:14.453 15204478 19040168 19072880 1 2012-07-18 09:22:47.887 2012-07-18 09:22:47.887 19040157 15204510 15237274 5 2010-11-08 11:50:34.297 2010-11-11 08:45:45.037 15204478 19040169 19072881 1 2012-07-18 09:23:07.043 2012-07-18 09:23:07.043 19040159 15631318 15664068 16 2010-11-08 11:50:34.297 2011-02-03 09:00:15.897 15204478 15204509 15237273 4 2010-11-08 11:50:34.297 2010-11-11 08:42:25.010 15204478 19040170 19072882 1 2012-07-18 09:23:25.270 2012-07-18 09:23:25.270 19040161 15631298 15664048 177 2009-01-06 09:56:05.890 2011-02-03 08:56:14.957 8355883 15631296 15664046 176 2009-01-06 09:56:05.890 2011-02-03 08:54:41.447 8355883 15631294 15664044 175 2009-01-06 09:56:05.890 2011-02-03 08:53:18.337 8355883 24052292 24085052 1 2014-01-08 10:06:03.217 2014-01-08 10:06:03.217 24052291 24052293 24085053 2 2014-01-08 10:06:03.217 2014-01-08 10:07:07.000 24052291 15631292 15664042 174 2009-01-06 09:56:05.890 2011-02-03 08:52:16.263 8355883 15631306 15664056 178 2009-01-06 09:56:05.890 2011-02-03 08:57:57.690 8355883 24052289 24085049 232 2009-01-06 09:56:05.890 2013-08-03 11:21:43.117 8355883 15631303 15664053 15 2010-11-08 11:50:34.297 2011-02-03 08:58:49.547 15204478 15631299 15664049 14 2010-11-08 11:50:34.297 2011-02-03 08:58:49.520 15204478 15204482 15237246 1 2010-11-08 11:50:34.297 2010-11-08 11:50:34.297 15204478 15631290 15664040 173 2009-01-06 09:56:05.890 2011-02-01 18:02:11.537 8355883 15631288 15664038 13 2010-11-08 11:50:34.297 2011-02-01 14:45:45.727 15204478 16449769 16417009 24052261 24085021 16 2013-10-30 14:29:58.263 2014-01-05 19:56:31.587 23167205 24052262 24085022 17 2013-10-30 14:29:58.263 2014-01-05 19:57:20.060 23167205 24052260 24085020 15 2013-10-30 14:29:58.263 2014-01-05 19:53:36.137 23167205 24052266 24085026 19 2013-10-30 14:29:58.263 2014-01-05 20:36:28.597 23167205 24052264 24085024 18 2013-10-30 14:29:58.263 2014-01-05 19:58:22.027 23167205 24052258 24085018 14 2013-10-30 14:29:58.263 2013-12-22 07:20:41.787 23167205 15631274 15664024 172 2009-01-06 09:56:05.890 2011-01-31 21:48:59.813 8355883 15631243 15663994 171 2009-01-06 09:56:05.890 2011-01-23 23:15:37.677 8355883 15631249 15663999 9 2010-11-08 11:50:34.297 2010-11-11 11:28:58.863 15204478 15631251 15664001 10 2010-11-08 11:50:34.297 2011-02-01 13:42:03.950 15204478 15631252 15664002 11 2010-11-08 11:50:34.297 2011-02-01 13:49:32.323 15204478 15631255 15664005 12 2010-11-08 11:50:34.297 2011-02-01 13:56:23.330 15204478 9371670 9404435 16 2009-01-06 09:56:05.890 2009-01-12 10:02:52.183 8355883 19074051 19041365 3211577 3145740 2008-04-09 12:55:07.147 2008-04-09 12:55:07.147 19040177 19072889 221 2009-01-06 09:56:05.890 2012-07-18 09:38:08.367 8355883 6259147 6226365 24 2008-04-22 12:26:44.157 2008-08-28 15:58:12.350 3637534 3211578 3145740 2008-04-09 12:55:07.147 2008-04-09 12:55:07.147 19040176 19072888 220 2009-01-06 09:56:05.890 2012-07-18 09:33:33.857 8355883 19074054 19041368 19040174 19072886 2 2012-07-18 09:23:25.270 2012-07-18 09:28:37.823 19040161 3211573 3145740 2008-04-09 12:55:07.147 2008-04-09 12:55:07.147 19040173 19072885 219 2009-01-06 09:56:05.890 2012-07-18 09:32:49.823 8355883 3211574 3145740 2008-04-09 12:55:07.147 2008-04-09 12:55:07.147 19040172 19072884 218 2009-01-06 09:56:05.890 2012-07-18 09:25:25.300 8355883 3211575 3145740 2008-04-09 12:55:07.147 2008-04-09 12:55:07.147 3211576 3145740 2008-04-09 12:55:07.147 2008-04-09 12:55:07.147 17268956 17236193 15631242 15663993 1 2009-09-24 15:00:46.927 2009-09-24 15:00:46.927 10356302 16449703 16416942 19074283 19041602 5275677 5308445 15 2008-05-12 09:51:47.077 2008-06-09 16:50:50.507 3638030 16449628 16416865 3211567 3145740 2008-04-09 12:55:07.147 2008-04-09 12:55:07.147 8388617 8355849 9371860 9404610 12 2008-08-04 13:42:13.733 2009-02-24 11:26:03.860 5832921 3211568 3145740 2008-04-09 12:55:07.147 2008-04-09 12:55:07.147 3211565 3145740 2008-04-09 12:55:07.147 2008-04-09 12:55:07.147 3211566 3145740 2008-04-09 12:55:07.147 2008-04-09 12:55:07.147 3211571 3145740 2008-04-09 12:55:07.147 2008-04-09 12:55:07.147 3211572 3145740 2008-04-09 12:55:07.147 2008-04-09 12:55:07.147 19040042 19072761 212 2009-01-06 09:56:05.890 2012-06-25 17:07:48.347 8355883 3211569 3145740 2008-04-09 12:55:07.147 2008-04-09 12:55:07.147 3211570 3145740 2008-04-09 12:55:07.147 2008-04-09 12:55:07.147 11273087 Accessories  --> Communications  --> Hyperterm  --> McStar USBser 115200 ** 115200, 8n1, no flow, COM5 * Step 4 - remove magnet from McSTAR 'white spot' ** If no activity, hit ENTER a couple of times and put magnet on white spot and remove. ** Should see a boot screen, do not hit a key to stop autoboot \\ h4. McSTAR Functional Test    * Step 1 - in Hyperterm, after McSTAR has booted, login with by entering 'root' ** JFFS2 message is harmless, but if login not seen due to JFFS2 message, hit ENTER a couple of times. * Step 2 - cd /media/sda1 (USB harddisk connected to McStar) ** List (ls) should show app dir * Step 3 - 'cd /media/sda1/app/scripts' * Step 4 - type 'date', then type 'date \-s "Tue Mar 09 10:54:30 PST 2010"' * Step 4 - start the McSTAR app './run_mcstar.sh' ** Allow it to run until the first recording message comes out.   Say stuff, whistle, whisper, etc. every 10 seconds or so (data blocks vary from 2 to 20 minutes; typically 5 minutes). ** After the first recording data message, hit Ctrl-c (terminate McSTAR data collection). ** "Writing a new audio file D000000..."  h4. Verification * Step 1 - after terminating run_mcstar.sh   In Hyperterm, change directories to the data directory. ** cd /media/sda1/data ** cd to the latest directory, then cd to R00000 * Find the file and transfer ** In Hyperterm, Transfer  \--> Receive File, use Zmodem (no crash recovery). Close ** In hyperterm, tell McSTAR to transfer the file you recorded * sz D00000 * On the HP Netbook, start Audacity On Windows * Project  \--> Import Raw Data ** Accept the defaults, and change 44100 to 48000 On a Mac * File  --> Import  --> Raw Data... * select file * open file and accept default settings except Sample Rate - change from default value of 44100 Hz to 48000 Hz (sampling rate of McSTAR). \\]]> 11240349 9371858 9404608 11 2008-08-04 13:42:13.733 2009-02-19 16:56:40.237 5832921 11273036 100db S/N ## bypass switching power supply noise ## shielding # Add external 'status good' indicator # Improve deployment reliability ## reduce size and weight # Change Connectors ## Paul Coenen's recommendations]]> 11240296 8388650 8355883 27143384 27067271 2015-06-10 14:05:44.377 2015-06-10 14:05:44.377 27143385 27067271 2015-06-10 14:05:44.377 2015-06-10 14:05:44.377 27143383 27067271 2015-06-10 14:05:44.377 2015-06-10 14:05:44.377 19040087 19072805 23 2012-07-13 10:43:52.837 2012-07-15 08:13:59.100 19040044 6258997 6226218 37 2008-05-12 09:51:47.077 2008-08-25 14:04:42.923 3638030 6258995 6226216 36 2008-05-12 09:51:47.077 2008-07-25 13:06:51.027 3638030 19040090 19072808 1 2012-07-15 08:18:15.653 2012-07-15 08:18:15.653 19040089 19040084 19072802 21 2012-07-13 10:43:52.837 2012-07-14 21:09:55.653 19040044 19040085 19072803 22 2012-07-13 10:43:52.837 2012-07-14 21:18:55.893 19040044 9371808 9404558 8 2009-01-26 16:30:22.427 2009-02-20 19:27:04.703 8913090 19040080 19072798 19 2012-07-13 10:43:52.837 2012-07-14 21:01:28.957 19040044 9371810 9404560 9 2009-01-26 16:30:22.427 2009-02-20 21:04:58.980 8913090 19040082 19072800 20 2012-07-13 10:43:52.837 2012-07-14 21:08:01.967 19040044 19040076 19072794 17 2012-07-13 10:43:52.837 2012-07-14 20:53:31.513 19040044 9371806 9404556 7 2009-01-26 16:30:22.427 2009-02-20 16:16:40.207 8913090 19040078 19072796 18 2012-07-13 10:43:52.837 2012-07-14 20:56:56.490 19040044 6259014 6226235 2 2008-08-27 13:39:41.480 2008-08-27 13:41:13.377 6259010 6259012 6226233 1 2008-08-27 13:39:41.480 2008-08-27 13:39:41.480 6259010 15204449 15237214 1 2010-11-02 09:21:37.147 2010-11-02 09:21:37.147 15204448 11273014 11240274 16449553 16416786 19040092 19072810 24 2012-07-13 10:43:52.837 2012-07-15 08:17:27.860 19040044 6259008 6226229 20 2008-04-09 12:55:07.147 2008-08-04 13:42:04.500 3114599 19040093 19072811 25 2012-07-13 10:43:52.837 2012-07-15 08:20:48.423 19040044 19040057 19072775 5 2012-07-13 10:43:52.837 2012-07-14 14:54:30.647 19040044 6259028 6226248 23 2008-04-22 12:26:44.157 2008-06-13 20:38:44.573 3637534 19040055 19072773 4 2012-07-13 10:43:52.837 2012-07-14 14:53:48.387 19040044 9371780 9404535 6 2009-01-26 16:30:22.427 2009-02-20 13:56:18.057 8913090 19040052 19072771 3 2012-07-13 10:43:52.837 2012-07-14 10:09:05.017 19040044 9371778 9404533 5 2009-01-26 16:30:22.427 2009-01-28 08:06:30.677 8913090 19040048 19072767 2 2012-07-13 10:43:52.837 2012-07-14 07:45:09.087 19040044 19040046 19072765 1 2012-07-13 10:43:52.837 2012-07-13 10:43:52.837 19040044 16449576 16416809 19040074 19072792 16 2012-07-13 10:43:52.837 2012-07-14 19:21:40.800 19040044 19074203 19041520 19040072 19072790 15 2012-07-13 10:43:52.837 2012-07-14 19:21:24.587 19040044 19040071 19072789 14 2012-07-13 10:43:52.837 2012-07-14 18:31:01.503 19040044 19040069 19072787 13 2012-07-13 10:43:52.837 2012-07-14 18:30:03.850 19040044 16449574 16416807 19040068 19072786 12 2012-07-13 10:43:52.837 2012-07-14 18:29:34.347 19040044 19040067 19072785 11 2012-07-13 10:43:52.837 2012-07-14 18:28:30.170 19040044 6259035 6226255 3 2008-08-27 13:39:41.480 2008-08-27 13:44:29.137 6259010 19040065 19072783 10 2012-07-13 10:43:52.837 2012-07-14 18:27:20.717 19040044 19040063 19072781 9 2012-07-13 10:43:52.837 2012-07-14 18:25:51.227 19040044 15204426 15237193 106 2009-01-06 09:56:05.890 2010-08-25 11:07:54.247 8355883 9371758 9404513 10 2008-08-04 13:42:13.733 2009-02-19 11:44:00.507 5832921 19040061 19072779 8 2012-07-13 10:43:52.837 2012-07-14 15:06:08.040 19040044 19040060 19072778 7 2012-07-13 10:43:52.837 2012-07-14 15:03:49.317 19040044 19040059 19072777 6 2012-07-13 10:43:52.837 2012-07-14 15:03:10.840 19040044 15631055 15663808 5 2011-01-23 23:21:42.587 2011-01-24 10:34:18.550 15631044 15631056 15663809 6 2011-01-23 23:21:42.587 2011-01-24 10:39:53.960 15631044 15631053 15663806 4 2011-01-23 23:21:42.587 2011-01-23 23:29:52.723 15631044 21365683 21398399 28 2012-07-13 10:43:52.837 2013-07-17 13:29:45.663 19040044 10354738 10387505 2 2009-05-12 17:00:48.963 2009-05-28 08:09:30.957 9798447 19532442 15630488 2012-12-15 08:12:36.897 2012-12-15 08:12:36.897 19532443 15630488 2012-12-15 08:12:36.897 2012-12-15 08:12:36.897 21365685 21398401 29 2012-07-13 10:43:52.837 2013-07-30 08:19:56.580 19040044 19532440 15630488 2012-12-15 08:12:36.897 2012-12-15 08:12:36.897 21365686 21398402 30 2012-07-13 10:43:52.837 2013-07-30 08:20:50.227 19040044 19532441 15630488 2012-12-15 08:12:36.897 2012-12-15 08:12:36.897 21365687 21398403 31 2012-07-13 10:43:52.837 2013-07-30 08:21:23.383 19040044 19532438 15630488 2012-12-15 08:12:36.897 2012-12-15 08:12:36.897 19532439 15630488 2012-12-15 08:12:36.897 2012-12-15 08:12:36.897 19532436 15630488 2012-12-15 08:12:36.897 2012-12-15 08:12:36.897 19532437 15630488 2012-12-15 08:12:36.897 2012-12-15 08:12:36.897 11403273 10356476 2010-01-22 15:42:25.650 2010-01-22 15:42:25.650 20102 1 11403272 11403272 10356476 2010-01-22 15:42:25.650 2010-04-27 06:36:20.487 20239 14 19532444 15630488 2012-12-15 08:12:36.897 2012-12-15 08:12:36.897 10354783 10387550 44 2009-01-06 09:56:05.890 2009-05-26 14:27:45.427 8355883 19532425 15630488 2012-12-15 08:12:36.897 2012-12-15 08:12:36.897 21365733 21398447 8 2008-12-29 11:40:49.410 2013-08-03 11:23:27.270 8355849 10354784 10387551 1 2009-05-01 14:58:13.070 2009-05-29 15:03:55.850 9798110 19532424 15630488 2012-12-15 08:12:36.897 2012-12-15 08:12:36.897 11403310 10356476 2010-01-22 15:42:25.650 2010-01-28 16:17:39.783 19894 3 11403272 19532427 15630488 2012-12-15 08:12:36.897 2012-12-15 08:12:36.897 10354786 10387553 6 2008-11-12 08:47:47.573 2009-05-29 15:04:23.697 7766027 21365731 21398445 7 2008-12-29 11:40:49.410 2009-05-26 14:41:53.467 8355849 19532426 15630488 2012-12-15 08:12:36.897 2012-12-15 08:12:36.897 19532421 15630488 2012-12-15 08:12:36.897 2012-12-15 08:12:36.897 19532420 15630488 2012-12-15 08:12:36.897 2012-12-15 08:12:36.897 19532423 15630488 2012-12-15 08:12:36.897 2012-12-15 08:12:36.897 19532422 15630488 2012-12-15 08:12:36.897 2012-12-15 08:12:36.897 10354791 10387558 46 2009-01-06 09:56:05.890 2009-05-29 15:06:53.487 8355883 19532433 15630488 2012-12-15 08:12:36.897 2012-12-15 08:12:36.897 19532432 15630488 2012-12-15 08:12:36.897 2012-12-15 08:12:36.897 10354793 10387560 47 2009-01-06 09:56:05.890 2009-05-29 15:08:24.583 8355883 19532435 15630488 2012-12-15 08:12:36.897 2012-12-15 08:12:36.897 19532434 15630488 2012-12-15 08:12:36.897 2012-12-15 08:12:36.897 21365730 21398444 231 2009-01-06 09:56:05.890 2012-12-30 11:47:36.873 8355883 19532429 15630488 2012-12-15 08:12:36.897 2012-12-15 08:12:36.897 19532428 15630488 2012-12-15 08:12:36.897 2012-12-15 08:12:36.897 10354789 10387556 45 2009-01-06 09:56:05.890 2009-05-29 15:03:17.410 8355883 19532431 15630488 2012-12-15 08:12:36.897 2012-12-15 08:12:36.897 19532430 15630488 2012-12-15 08:12:36.897 2012-12-15 08:12:36.897 15631040 15663793 170 2009-01-06 09:56:05.890 2011-01-18 21:25:33.517 8355883 19532408 15630488 2012-12-15 08:12:36.897 2012-12-15 08:12:36.897 19532409 15630488 2012-12-15 08:12:36.897 2012-12-15 08:12:36.897 19532410 15630488 2012-12-15 08:12:36.897 2012-12-15 08:12:36.897 19532411 15630488 2012-12-15 08:12:36.897 2012-12-15 08:12:36.897 19532404 15630488 2012-12-15 08:12:36.897 2012-12-15 08:12:36.897 19532405 15630488 2012-12-15 08:12:36.897 2012-12-15 08:12:36.897 19532406 15630488 2012-12-15 08:12:36.897 2012-12-15 08:12:36.897 19532407 15630488 2012-12-15 08:12:36.897 2012-12-15 08:12:36.897 15631048 15663801 2 2011-01-23 23:21:42.587 2011-01-23 23:25:32.277 15631044 19532416 15630488 2012-12-15 08:12:36.897 2012-12-15 08:12:36.897 19532417 15630488 2012-12-15 08:12:36.897 2012-12-15 08:12:36.897 15631050 15663803 3 2011-01-23 23:21:42.587 2011-01-23 23:26:32.150 15631044 19532418 15630488 2012-12-15 08:12:36.897 2012-12-15 08:12:36.897 19532419 15630488 2012-12-15 08:12:36.897 2012-12-15 08:12:36.897 7798793 {noformat} Lastly, I edited the /opt/jboss/server/default/deploy/jbossweb-tomcat55.sar/META-INF/jboss-service.xml and changed the following line: {noformat} false {noformat} to: {noformat} true {noformat} Then I restarted JBoss.]]> 7766027 19532412 15630488 2012-12-15 08:12:36.897 2012-12-15 08:12:36.897 19532413 15630488 2012-12-15 08:12:36.897 2012-12-15 08:12:36.897 15631046 15663799 1 2011-01-23 23:21:42.587 2011-01-23 23:21:42.587 15631044 19532414 15630488 2012-12-15 08:12:36.897 2012-12-15 08:12:36.897 11403306 10356476 2010-01-22 15:42:25.650 2010-01-22 15:50:26.567 19806 2 11403272 19532415 15630488 2012-12-15 08:12:36.897 2012-12-15 08:12:36.897 3670609 3637859 834 831 14 2007-02-07 14:07:35.807 2007-02-07 15:08:24.863 814 557058 814 2007-03-19 10:22:54.960 2007-03-19 10:22:54.960 337281 1 11403342 10356476 2010-01-22 15:42:25.650 2010-02-16 08:51:39.013 19924 5 11403272 828 825 13 2007-02-07 14:07:35.807 2007-02-07 14:42:21.253 814 11403343 10356476 2010-01-22 15:42:25.650 2010-02-23 09:35:45.277 20058 6 11403272 11403357 10356476 2010-01-22 15:42:25.650 2010-02-24 11:23:01.033 20138 7 11403272 835 832 15 2007-02-07 14:07:35.807 2007-02-07 15:31:43.083 814 10354695 10387463 16 2009-05-09 15:33:01.367 2009-05-27 10:00:26.200 9798378 815 812 1 2007-02-07 14:07:35.807 2007-02-07 14:07:35.807 814 816 813 2 2007-02-07 14:07:35.807 2007-02-07 14:13:28.843 814 817 814 3 2007-02-07 14:07:35.807 2007-02-07 14:14:59.057 814 818 815 4 2007-02-07 14:07:35.807 2007-02-07 14:16:23.030 814 823 820 9 2007-02-07 14:07:35.807 2007-02-07 14:30:20.150 814 11403338 10356476 2010-01-22 15:42:25.650 2010-02-02 09:17:12.507 19849 4 11403272 824 821 10 2007-02-07 14:07:35.807 2007-02-07 14:31:06.087 814 825 822 11 2007-02-07 14:07:35.807 2007-02-07 14:32:10.607 814 826 823 12 2007-02-07 14:07:35.807 2007-02-07 14:37:54.213 814 819 816 5 2007-02-07 14:07:35.807 2007-02-07 14:16:38.383 814 820 817 6 2007-02-07 14:07:35.807 2007-02-07 14:24:06.557 814 821 818 7 2007-02-07 14:07:35.807 2007-02-07 14:24:39.457 814 822 819 8 2007-02-07 14:07:35.807 2007-02-07 14:25:23.417 814 9371895 9404644 10 2009-01-26 16:30:22.427 2009-02-20 21:32:41.397 8913090 11403365 10356476 2010-01-22 15:42:25.650 2010-03-09 09:36:49.607 19600 10 11403272 9371899 9404648 11 2009-01-26 16:30:22.427 2009-02-25 10:32:58.023 8913090 11403359 10356476 2010-01-22 15:42:25.650 2010-03-05 16:35:16.307 19676 9 11403272 11403358 10356476 2010-01-22 15:42:25.650 2010-03-04 13:30:44.710 20004 8 11403272 853 850 17 2007-02-07 14:07:35.807 2007-02-09 15:27:25.867 814 854 851 18 2007-02-07 14:07:35.807 2007-02-09 15:29:28.547 814 10354711 10387479 1 2009-05-12 17:00:48.963 2009-05-12 17:00:48.963 9798447 852 849 16 2007-02-07 14:07:35.807 2007-02-08 10:40:07.840 814 15630938 15663692 18 2008-08-04 13:42:13.733 2011-01-18 21:13:18.377 5832921 15707918 3638030 2011-01-18 21:33:44.943 2011-01-18 21:33:44.943 19532338 15630488 2012-12-15 08:12:36.893 2012-12-15 08:12:36.893 15707919 3638030 2011-01-18 21:33:44.943 2011-01-18 21:33:44.943 19532339 15630488 2012-12-15 08:12:36.893 2012-12-15 08:12:36.893 15630936 15663690 17 2008-08-04 13:42:13.733 2011-01-18 20:52:37.380 5832921 15707916 3638030 2011-01-18 21:33:44.943 2011-01-18 21:33:44.943 19532336 15630488 2012-12-15 08:12:36.893 2012-12-15 08:12:36.893 15707917 3638030 2011-01-18 21:33:44.943 2011-01-18 21:33:44.943 10354887 10387651 2 2009-06-04 09:34:49.790 2009-06-04 09:35:21.127 10354884 19532337 15630488 2012-12-15 08:12:36.893 2012-12-15 08:12:36.893 15630934 15663688 16 2008-08-04 13:42:13.733 2009-09-24 14:41:31.317 5832921 15707922 3638030 2011-01-18 21:33:44.943 2011-01-18 21:33:44.943 19532334 15630488 2012-12-15 08:12:36.893 2012-12-15 08:12:36.893 6226231 BOOT PICO * CF2> BOOT APP for deployment * RMC message for A or V (Tracking or DR - tells wether GPS is tracking) \\ * First Tasks * 1) Add to Prompt GPS OK, RGPS Age OK, AGC OK, Platform Track OK (ask once every 4sec to avoid swamping the Seatel) * 2) Create NMEA style string on Spare2 hooked to 24 port terminal server for continuous stream of updates to be displayed by a GUI * 3) Implement 'Hunting Algorithm' if pointing command is sent N times (config parm). * \\ \\ \\ \\ Seatel SEA TEL MODEl TAC-92 USER INTERFACE DESCRIPTI0N VERSION 1.61 1.0 COMMAND SUMMARY | CONTROL CODES: | FUNCTION | | | 6 | Azimuth CW one step (system step reselution) | | 4 | Azimuth CCW one step | | 8 | Elevation up one step | | 2 | Elevation DOWN one step | | Aaaaa{} | Move AZ to aaa.a deg , true or magnetic | | Baaaa{} | Set ships heading to aaa.a degrees | | C | Step Track ON | | D | Step Track and Tracking OFF | | cnnnn{} | Set MHz/CHA tuning to nnnn MHz | | dnnnn{} | Set KHz/CHB tuning to nnnn KHz | | Eeeee{} | Move EL to ee.e or eee.e degrees | | F | Toggle auto unwrap ON/OFF | | gnnn {} | Set polang position to nnn | | Jrrrr{} | Move azimuth to ship relative position | | Nnnn{ } | Set number of signal strength updates (1-255) | | Onnn{ } | Output data to EME equipment | | R | start spiral search fot satellite | | S | Advance AGC input selectien (Ext, ChA, ChB, IF) | | Taaaa{} | Move to satellite at aaa.a degrees | | U | Force cable unwrap | | W | Write parameters to NV RAM | | Xnnn{} | Set azimuth step track size to nnn steps (1-255) | | Ynnn{} | Set elevation step track size to nnn steps (0-255) | | Z | Toggle C/Ku step size selection | | esc | Cancel pending numeric command | | $mmmmm{} | NMEA Latitude / Longitude input (GPGLL format) | | MONITOR CODES | FUNCTION | TAC RESPONSE | | H | Relative Az,Ship Heading | RrrrrHaaaa,CR,LF,> | | M | Tracking Parameters | Xnnn Ynnn Nnnn cc,CR,LF,> | | P | Az/EL Position | EeeeeAaaaa,CR,LF,> | | s | TaC Status | Snn,CR,LF1> | | V | Software Version | TAC-92 VER N,NN,CR,LF, > | | q | Tuning >Frequencies , Input | Qnnnn nnnn s,CR,LF,> | | u | Polang position | Gnnn ,CR,LF,> | | % | Signal Strength | Lnnnn,CR,LF,> | | & | Error Status | &nnn ,CR,LF,> | | ABBREVIATIONS: | | eeee = | Elevation angle oooo to 0900 nominal 0000 to 3599 range | | aaaa = | True/Magnetic Azimuth 0000 to 3599 range | | rrrr = | Relative azimuth 0950 to 6250 1ange | | nnnn = | A5CII decimal number 0000-9999 | | nnn = | ASCII decima\[ number 0 to 255 | | nn = | System Status twO bitmaped ASCII characters | | cc = | C /Ku tracking parameter bank selection | | s = | AGC receiver selection 0,l,2,3 | | {} = | Carriage return | April 30, 1996 Doc No. 112862-D \\ \\]]> 6259010 15707923 3638030 2011-01-18 21:33:44.943 2011-01-18 21:33:44.943 10354885 10387649 1 2009-06-04 09:34:49.790 2009-06-04 09:34:49.790 10354884 19532335 15630488 2012-12-15 08:12:36.893 2012-12-15 08:12:36.893 15707920 3638030 2011-01-18 21:33:44.943 2011-01-18 21:33:44.943 19532332 15630488 2012-12-15 08:12:36.893 2012-12-15 08:12:36.893 15707921 3638030 2011-01-18 21:33:44.943 2011-01-18 21:33:44.943 19532333 15630488 2012-12-15 08:12:36.893 2012-12-15 08:12:36.893 19532330 15630488 2012-12-15 08:12:36.893 2012-12-15 08:12:36.893 19532331 15630488 2012-12-15 08:12:36.893 2012-12-15 08:12:36.893 10354880 10387644 62 2009-01-06 09:56:05.890 2009-06-01 10:23:40.323 8355883 19532328 15630488 2012-12-15 08:12:36.893 2012-12-15 08:12:36.893 19532329 15630488 2012-12-15 08:12:36.893 2012-12-15 08:12:36.893 15707914 3638030 2011-01-18 21:33:44.943 2011-01-18 21:33:44.943 19532326 15630488 2012-12-15 08:12:36.893 2012-12-15 08:12:36.893 15707915 3638030 2011-01-18 21:33:44.943 2011-01-18 21:33:44.943 19532327 15630488 2012-12-15 08:12:36.893 2012-12-15 08:12:36.893 19532324 15630488 2012-12-15 08:12:36.893 2012-12-15 08:12:36.893 15707913 3638030 2011-01-18 21:33:44.943 2011-01-18 21:33:44.943 19532325 15630488 2012-12-15 08:12:36.893 2012-12-15 08:12:36.893 19532323 15630488 2012-12-15 08:12:36.893 2012-12-15 08:12:36.893 19532322 15630488 2012-12-15 08:12:36.893 2012-12-15 08:12:36.893 19532321 15630488 2012-12-15 08:12:36.893 2012-12-15 08:12:36.893 19532320 15630488 2012-12-15 08:12:36.893 2012-12-15 08:12:36.893 19532319 15630488 2012-12-15 08:12:36.893 2012-12-15 08:12:36.893 19532318 15630488 2012-12-15 08:12:36.893 2012-12-15 08:12:36.893 19532317 15630488 2012-12-15 08:12:36.893 2012-12-15 08:12:36.893 19532316 15630488 2012-12-15 08:12:36.893 2012-12-15 08:12:36.893 19532315 15630488 2012-12-15 08:12:36.893 2012-12-15 08:12:36.893 19532314 15630488 2012-12-15 08:12:36.893 2012-12-15 08:12:36.893 15630943 15663697 39 2008-05-12 09:51:47.077 2009-09-24 14:47:51.397 3638030 10354863 10387627 4 2009-05-12 17:00:48.963 2009-06-02 11:01:13.190 9798447 19532313 15630488 2012-12-15 08:12:36.893 2012-12-15 08:12:36.893 19532312 15630488 2012-12-15 08:12:36.893 2012-12-15 08:12:36.893 10354861 10387625 3 2009-05-12 17:00:48.963 2009-05-28 13:58:59.787 9798447 15630942 15663696 169 2009-01-06 09:56:05.890 2011-01-13 15:12:08.953 8355883 15630939 15663693 19 2008-08-04 13:42:13.733 2011-01-18 21:16:58.353 5832921 15630919 15663674 168 2009-01-06 09:56:05.890 2011-01-13 15:11:07.097 8355883 15707933 3638030 2011-01-18 21:33:44.943 2011-01-18 21:33:44.943 15707932 3638030 2011-01-18 21:33:44.943 2011-01-18 21:33:44.943 15630915 15663670 166 2009-01-06 09:56:05.890 2011-01-05 09:03:50.450 8355883 10354900 10387664 64 2009-01-06 09:56:05.890 2009-06-04 12:42:08.390 8355883 15630917 15663672 167 2009-01-06 09:56:05.890 2011-01-13 15:01:24.147 8355883 10354901 10387665 33 2007-02-07 14:07:35.807 2009-06-04 12:42:52.817 814 10354902 10387666 4 2009-06-04 09:34:49.790 2009-06-04 12:19:15.143 10354884 10354895 10387659 63 2009-01-06 09:56:05.890 2009-06-04 09:32:11.277 8355883 15707925 3638030 2011-01-18 21:33:44.943 2011-01-18 21:33:44.943 15707924 3638030 2011-01-18 21:33:44.943 2011-01-18 21:33:44.943 10354896 10387660 32 2007-02-07 14:07:35.807 2009-06-04 12:42:52.780 814 15707927 3638030 2011-01-18 21:33:44.943 2011-01-18 21:33:44.943 15707926 3638030 2011-01-18 21:33:44.943 2011-01-18 21:33:44.943 15707929 3638030 2011-01-18 21:33:44.943 2011-01-18 21:33:44.943 15707928 3638030 2011-01-18 21:33:44.943 2011-01-18 21:33:44.943 10354892 10387656 3 2009-06-04 09:34:49.790 2009-06-04 10:12:26.887 10354884 15707931 3638030 2011-01-18 21:33:44.943 2011-01-18 21:33:44.943 15707930 3638030 2011-01-18 21:33:44.943 2011-01-18 21:33:44.943 15630870 15663624 24 2009-12-23 08:33:45.977 2011-01-10 11:00:16.380 10912227 10354822 10387588 56 2009-01-06 09:56:05.890 2009-06-01 08:36:07.817 8355883 19532398 15630488 2012-12-15 08:12:36.897 2012-12-15 08:12:36.897 10354821 10387587 55 2009-01-06 09:56:05.890 2009-06-01 08:36:04.807 8355883 19532399 15630488 2012-12-15 08:12:36.897 2012-12-15 08:12:36.897 15630868 15663622 23 2009-12-23 08:33:45.977 2010-07-28 15:37:17.033 10912227 10354820 10387586 54 2009-01-06 09:56:05.890 2009-05-29 15:44:39.910 8355883 19532396 15630488 2012-12-15 08:12:36.897 2012-12-15 08:12:36.897 19532397 15630488 2012-12-15 08:12:36.897 2012-12-15 08:12:36.897 10388955 10356237 19532402 15630488 2012-12-15 08:12:36.897 2012-12-15 08:12:36.897 19532403 15630488 2012-12-15 08:12:36.897 2012-12-15 08:12:36.897 10354824 10387590 57 2009-01-06 09:56:05.890 2009-06-01 08:36:52.067 8355883 19532400 15630488 2012-12-15 08:12:36.897 2012-12-15 08:12:36.897 19532401 15630488 2012-12-15 08:12:36.897 2012-12-15 08:12:36.897 10354814 10387580 51 2009-01-06 09:56:05.890 2009-05-29 15:27:15.323 8355883 19532390 15630488 2012-12-15 08:12:36.897 2012-12-15 08:12:36.897 19532391 15630488 2012-12-15 08:12:36.897 2012-12-15 08:12:36.897 10354812 10387578 66 2008-04-14 16:11:58.510 2009-05-29 15:31:35.280 3637286 19532388 15630488 2012-12-15 08:12:36.897 2012-12-15 08:12:36.897 19532389 15630488 2012-12-15 08:12:36.897 2012-12-15 08:12:36.897 10354811 10387577 5 2009-05-29 15:27:30.707 2009-05-29 15:31:35.273 10354800 19532394 15630488 2012-12-15 08:12:36.897 2012-12-15 08:12:36.897 10354817 10387583 53 2009-01-06 09:56:05.890 2009-05-29 15:41:41.293 8355883 19532395 15630488 2012-12-15 08:12:36.897 2012-12-15 08:12:36.897 10354816 10387582 52 2009-01-06 09:56:05.890 2009-05-29 15:38:08.437 8355883 19532392 15630488 2012-12-15 08:12:36.897 2012-12-15 08:12:36.897 19532393 15630488 2012-12-15 08:12:36.897 2012-12-15 08:12:36.897 19532383 15630488 2012-12-15 08:12:36.897 2012-12-15 08:12:36.897 10354805 10387571 3 2009-05-29 15:27:30.707 2009-05-29 15:30:24.470 10354800 10354806 10387572 64 2008-04-14 16:11:58.510 2008-11-09 13:32:57.627 3637286 19532382 15630488 2012-12-15 08:12:36.897 2012-12-15 08:12:36.897 19532381 15630488 2012-12-15 08:12:36.897 2012-12-15 08:12:36.897 10354803 10387569 2 2009-05-29 15:27:30.707 2009-05-29 15:28:17.307 10354800 10354804 10387570 28 2008-04-09 12:55:07.147 2009-03-17 13:51:32.387 3114599 19532380 15630488 2012-12-15 08:12:36.897 2012-12-15 08:12:36.897 10354809 10387575 65 2008-04-14 16:11:58.510 2009-05-29 15:31:00.633 3637286 19532387 15630488 2012-12-15 08:12:36.897 2012-12-15 08:12:36.897 10354810 10387576 30 2008-04-09 12:55:07.147 2009-05-29 15:31:35.260 3114599 19532386 15630488 2012-12-15 08:12:36.897 2012-12-15 08:12:36.897 10354807 10387573 29 2008-04-09 12:55:07.147 2009-05-29 15:31:00.597 3114599 19532385 15630488 2012-12-15 08:12:36.897 2012-12-15 08:12:36.897 19532384 15630488 2012-12-15 08:12:36.897 2012-12-15 08:12:36.897 10354808 10387574 4 2009-05-29 15:27:30.707 2009-05-29 15:31:00.627 10354800 10354797 10387564 49 2009-01-06 09:56:05.890 2009-05-29 15:18:33.547 8355883 19532375 15630488 2012-12-15 08:12:36.897 2012-12-15 08:12:36.897 10354798 10387565 50 2009-01-06 09:56:05.890 2009-05-29 15:19:46.707 8355883 19532374 15630488 2012-12-15 08:12:36.897 2012-12-15 08:12:36.897 10354795 10387562 48 2009-01-06 09:56:05.890 2009-05-29 15:15:01.620 8355883 19532373 15630488 2012-12-15 08:12:36.897 2012-12-15 08:12:36.897 19532372 15630488 2012-12-15 08:12:36.897 2012-12-15 08:12:36.897 19532379 15630488 2012-12-15 08:12:36.897 2012-12-15 08:12:36.897 10354801 10387567 1 2009-05-29 15:27:30.707 2009-05-29 15:27:30.707 10354800 19532378 15630488 2012-12-15 08:12:36.897 2012-12-15 08:12:36.897 19532377 15630488 2012-12-15 08:12:36.897 2012-12-15 08:12:36.897 16876374 16777373 2011-05-09 13:08:18.657 2011-05-09 13:08:18.657 19532376 15630488 2012-12-15 08:12:36.897 2012-12-15 08:12:36.897 19532364 15630488 2012-12-15 08:12:36.893 2012-12-15 08:12:36.893 19532365 15630488 2012-12-15 08:12:36.893 2012-12-15 08:12:36.893 19532366 15630488 2012-12-15 08:12:36.893 2012-12-15 08:12:36.893 19532367 15630488 2012-12-15 08:12:36.897 2012-12-15 08:12:36.897 19532368 15630488 2012-12-15 08:12:36.897 2012-12-15 08:12:36.897 19532369 15630488 2012-12-15 08:12:36.897 2012-12-15 08:12:36.897 19532370 15630488 2012-12-15 08:12:36.897 2012-12-15 08:12:36.897 19532371 15630488 2012-12-15 08:12:36.897 2012-12-15 08:12:36.897 9372015 9404763 26 2008-04-09 12:55:07.147 2009-01-28 08:08:31.203 3114599 19532356 15630488 2012-12-15 08:12:36.893 2012-12-15 08:12:36.893 9372016 9404764 13 2008-08-04 13:42:13.733 2009-02-24 11:28:30.630 5832921 19532357 15630488 2012-12-15 08:12:36.893 2012-12-15 08:12:36.893 19532358 15630488 2012-12-15 08:12:36.893 2012-12-15 08:12:36.893 19532359 15630488 2012-12-15 08:12:36.893 2012-12-15 08:12:36.893 19532360 15630488 2012-12-15 08:12:36.893 2012-12-15 08:12:36.893 19532361 15630488 2012-12-15 08:12:36.893 2012-12-15 08:12:36.893 19532362 15630488 2012-12-15 08:12:36.893 2012-12-15 08:12:36.893 19532363 15630488 2012-12-15 08:12:36.893 2012-12-15 08:12:36.893 10354835 10387601 61 2009-01-06 09:56:05.890 2009-06-01 10:13:15.903 8355883 19532349 15630488 2012-12-15 08:12:36.893 2012-12-15 08:12:36.893 21365521 21398243 27 2012-07-13 10:43:52.837 2013-07-17 13:28:44.473 19040044 19532348 15630488 2012-12-15 08:12:36.893 2012-12-15 08:12:36.893 19532351 15630488 2012-12-15 08:12:36.893 2012-12-15 08:12:36.893 21365519 21398241 26 2012-07-13 10:43:52.837 2012-07-15 08:32:24.567 19040044 3670777 D0 52.08 52.08 \+0 \+0.00 D0->D1 104.17 104.17 \+0 \+0.00 D1->D2 156.25 156.25 \+0 \+0.00 D2->D3 208.33 208.33 \+0 \+0.00 D3->D4 260.42 260.42 \+0 \+0.00 D4->D5 312.50 312.50 \+0 \+0.00 D5->D6 364.58 364.58 \+0 \+0.00 D6->D7 416.67 416.67 \+0 \+0.00 D7->stopbit 468.75 468.75 \+0 \+0.00 end of stopb 520.83 520.83 \+0 \+0.00 \*/ UBR00=0xC0; UBR10=0x00; UMCTL0=0x00; /\* uart0 3686400Hz 19200bps \*/ UBR01=0xC0; UBR11=0x00; UMCTL1=0x00; /\* uart1 3686400Hz 19200bps \*/ h4. The simplest way to use the USART in UART mode is this: interrupt is not enabled, the software checks if it can output the next byte (UTXIFG = 1), and if a new character has been received (URXIFG = 1). \\ h4. Modbus Register Map * REG_INPUT_START         512         // input registers start at 512 * REG_INPUT_NREGS         8           // 8x16 bit registers * REG_SOLENOIDS_A        0            // Holding registers start at 0 (16 coils for each A and B) * REG_SOLENOIDS_B        1   * REG_HOLDING_START    0           // to match WAGO * REG_HOLDING_NREGS   40         // 40 is more than actual (2) * REG_COILS_START         0           // read individual coils (was 1000) * REG_COILS_SIZE           32          // 32 coils * REG_DISC_START          0           // discrete (was 1000) * REG_DISC_SIZE             32          // 32 coils \\ h3. ---- MODBUS * Commands ** Read Input Register (0x04) ** Read Holding Registers (0x03) ** Write Single Register (0x06) ** Write Multiple Registers (0x10) ** Read/Write Multiple Registers (0x17) ** Read Coils (0x01) ** Write Single Coil (0x05) ** Write Multiple Coils (0x0F) ** Read Discrete Inputs (0x02) ** Report Slave ID (0x11)   * Address * Slave ID  * Berlios ModBus Stack ** The modbus stack is config'd in {color:#0000ff}mbconfig.h{color} which is located in vpc\modbus\include \\ \\ ---- h3. Debugging MSP430 h4. Starting gdbproxy The next step is starting gdbproxy, which is responsible for the communication between GDB and the FET: msp430-gdbproxy \--port=2000 msp430 If your FET is properly connected to the parallel port, you should see a message like the following: info: msp430: Target device is a 'MSP430F12x' (type 11) notice: msp430-gdbproxy: waiting on TCP port 2000 h4. Using Insight (Windows) After you have started Insight (c:\msp430\bin\msp430-gdb.exe), click on "File->Open" and select the elf-file (e.g. "test.elf") you want to debug. Now click on "Run->Connect to target" and enter the following settings: Target: "Remote/TCP" Hostname: "localhost" Port: "2000" Set breakpoint at 'main': yes Set breakpoint at 'exit': yes Attach to target: yes Download Program: yes Command after attaching: "monitor erase all" Run Method: Continue from last Stop When you click on "Ok" Insight should tell you that the connection was successful, and gdbproxy should say "notice: msp430-gdbproxy: connected". To start the debugging click on "Run" or simply press "r". If everything worked correctly you should now see the sourcecode of your program with the first line of main() marked green. The red point is the breakpoint that has been set by Insight automatically. You can set or remove breakpoints by clicking on the '-' in front of the line. Now you can 'c'ontinue the execution to the next breakpoint, 's'tep through the code, or step a single assembler instruction... but be careful with "finish": Insight sometimes seems to lock up with this command. So if you want to finish a function, I recommend setting a breakpoint to the end of the function and using "continue". \\ h2. Installing the Compiler Tool Chain To obtain and install the compiler: # Go to the MSPGCC download page and obtain the latest MSPGCC installation. I used the 'mspgcc-20040723.exe' download which installed everything I needed for a Win32 setup. \\ # This step need only be performed if you wish to use the graphical version of GDB. The latest MSPGCC download only includes the command line GDB debugger. I prefer to use the graphical version called Insight. A slightly older prebuilt version of Insight can be used. Install this older version of insight into a different directory to that chosen for the latest MSPGCC installation as you don't want to overwrite the files obtained in step 1. \\ You should now have two installations. The latest version of MSPGCC installed during step 1, and a slightly older version of Insight from step 2. Both versions of the GDB debugger are called msp430-gdb.exe so one needs to be renamed. Locate the older version msp430-gdb.exe from the files installed during this step and rename it msp430-insight.exe. \\ # Ensure the BIN directory from the files installed during step 1 and the BIN directory from the files installed during step 2 are included in your PATH environment variable. \\ \\ # The MSPGCC download includes a program called msp430-gdbproxy.exe. This intercepts the GDB TCP commands and redirects them to the parallel port. Start msp430-gdbproxy (a shortcut to this will have been placed on the start menu when MSPGCC was installed). By default msp430-gdbproxy uses port 3333 - do not change this. \\ # Program the flash as per the instruction in the section above. The flash can be programmed from within GDB but it is much faster to do it separately and beforehand. \\ # Start the debugger using the command ... msp430-insight a.out... the commands in the gdb.ini file will do the rest. If you prefer to use the command line debugger simply replace msp430-insight with msp430-gdb. \\ # Insight will start at and the program will stop at the breakpoint in main() as shown below. \\ MSP430 Clocking \\ MSP430 Basic Clock Module * Clock Signals: ** *ACLK*: Auxiliary clock. The signal is sourced from LFXT1CLK with a divider of 1, 2, 4, or 8. (The calibration program for the serial link sets the divider to 4, but after the calibration it can be changed to any other values.) ACLK can be used as the clock signal for Timer A and Timer B. ** *MCLK*: Master clock. The signal can be sourced from LFXT1CLK, XT2CLK (if available), or DCOCLK with a divider of 1, 2, 4, or 8. MCLK is used by the CPU and system. ** *SMCLK*: Sub-main clock. The signal is sourced from either XT2CLK (if available), or DCOCLK with a divider of 1, 2, 4, or 8. SMCLK can be used as the clock signal for Timer A and Timer B. * MSP430 Clocking pictorial: *   * \\ !MSP430_clocking2.JPG!                  !MSP430_BCSCTL1.JPG! !MSP430_BCSCTL2.JPG!\\ \\]]> 3638030 19532350 15630488 2012-12-15 08:12:36.893 2012-12-15 08:12:36.893 19532353 15630488 2012-12-15 08:12:36.893 2012-12-15 08:12:36.893 19532352 15630488 2012-12-15 08:12:36.893 2012-12-15 08:12:36.893 19532355 15630488 2012-12-15 08:12:36.893 2012-12-15 08:12:36.893 19532354 15630488 2012-12-15 08:12:36.893 2012-12-15 08:12:36.893 19532341 15630488 2012-12-15 08:12:36.893 2012-12-15 08:12:36.893 19532340 15630488 2012-12-15 08:12:36.893 2012-12-15 08:12:36.893 10354829 10387595 58 2009-01-06 09:56:05.890 2009-06-01 10:04:09.903 8355883 19532343 15630488 2012-12-15 08:12:36.893 2012-12-15 08:12:36.893 19532342 15630488 2012-12-15 08:12:36.893 2012-12-15 08:12:36.893 10354831 10387597 59 2009-01-06 09:56:05.890 2009-06-01 10:06:59.183 8355883 19532345 15630488 2012-12-15 08:12:36.893 2012-12-15 08:12:36.893 19532344 15630488 2012-12-15 08:12:36.893 2012-12-15 08:12:36.893 10354833 10387599 60 2009-01-06 09:56:05.890 2009-06-01 10:08:30.833 8355883 19532347 15630488 2012-12-15 08:12:36.893 2012-12-15 08:12:36.893 19532346 15630488 2012-12-15 08:12:36.893 2012-12-15 08:12:36.893 11013768 10912300 2010-01-05 08:32:12.670 2010-01-05 08:32:12.670 11013769 10912300 2010-01-05 08:32:12.670 2010-01-05 08:32:12.670 11013770 10912300 2010-01-05 08:32:12.670 2010-01-05 08:32:12.670 11013771 10912300 2010-01-05 08:32:12.670 2010-01-05 08:32:12.670 11013764 10912300 2010-01-05 08:32:12.670 2010-01-05 08:32:12.670 6226632 Backup Database... ## Select Database-complete ## Click on Add... under Destination ## I typed in a file location of \\tempest\tempbox\kgomes\backups\crowd\db_backup as the file to backup to. ## I then created a new tar.gz file for the /opt/atlassian-crowd-1.5.1 installation and put in the same backup location on tempest. ## I then created a new tar.gz file for the crowd home directory /data/crowd and put in same tempest location # I copied the jtds-1.2.jar from /opt/atlassian-crowd-1.5.1/crowd-webapp/WEB-INF/lib to the same directory in the new installation # I then edited the /opt/atlassian-crowd-1.6/crowd-webapp/WEB-INF/classes/crowd-init.properties and pointed the crowd home directory to /data/crowd # I then copied the updated crowd client jar (/opt/atlassian-crowd-1.6/client/crowd-integrations-client-1.6.jar) to /opt/confluence/confluence/WEB-INF/lib and to /opt/jira/atlassian-jira/WEB-INF/lib (I removed the old ones too IMPORTANT!) # I downloaded the recommended crowd-ehcache.xml file from the instructions listed above and copied to the /opt/confluence/confluence/WEB-INF/classes and /opt/jira/atlassian-jira/WEB-INF/classes directories # Lastly I changed the /opt/crowd symbolic link to point to the new crowd installation, shut down confluence, jira, and crowd and restarted crowd. # After the successful start up of the three applications, I put all the backup files in Alfresco [here|https://alfresco.mbari.org/alfresco/webdav/Engineering/Tools/Collaboration%20Tools/Atlassian%20Crowd/Backups/2008_12_29]]]> 6259430 11013765 10912300 2010-01-05 08:32:12.670 2010-01-05 08:32:12.670 11013766 10912300 2010-01-05 08:32:12.670 2010-01-05 08:32:12.670 11013767 10912300 2010-01-05 08:32:12.670 2010-01-05 08:32:12.670 11013776 10912300 2010-01-05 08:32:12.670 2010-01-05 08:32:12.670 11013777 10912300 2010-01-05 08:32:12.670 2010-01-05 08:32:12.670 11013772 10912300 2010-01-05 08:32:12.670 2010-01-05 08:32:12.670 11013773 10912300 2010-01-05 08:32:12.670 2010-01-05 08:32:12.670 11013774 10912300 2010-01-05 08:32:12.670 2010-01-05 08:32:12.670 11013775 10912300 2010-01-05 08:32:12.670 2010-01-05 08:32:12.670 11013753 10912300 2010-01-05 08:32:12.670 2010-01-05 08:32:12.670 11013752 10912300 2010-01-05 08:32:12.670 2010-01-05 08:32:12.670 11013755 10912300 2010-01-05 08:32:12.670 2010-01-05 08:32:12.670 11013754 10912300 2010-01-05 08:32:12.670 2010-01-05 08:32:12.670 8913088 8945849 22 2008-04-09 12:55:07.147 2008-10-29 10:37:48.387 3114599 11013749 10912300 2010-01-05 08:32:12.670 2010-01-05 08:32:12.670 11013748 10912300 2010-01-05 08:32:12.670 2010-01-05 08:32:12.670 11013751 10912300 2010-01-05 08:32:12.670 2010-01-05 08:32:12.670 11013750 10912300 2010-01-05 08:32:12.670 2010-01-05 08:32:12.670 8913092 8945853 1 2009-01-26 16:30:22.427 2009-01-26 16:30:22.427 8913090 11013761 10912300 2010-01-05 08:32:12.670 2010-01-05 08:32:12.670 8913091 8945852 23 2008-04-09 12:55:07.147 2009-01-26 16:28:16.417 3114599 11013760 10912300 2010-01-05 08:32:12.670 2010-01-05 08:32:12.670 8913094 8945855 2 2009-01-26 16:30:22.427 2009-01-26 16:31:19.627 8913090 11013763 10912300 2010-01-05 08:32:12.670 2010-01-05 08:32:12.670 8913093 8945854 24 2008-04-09 12:55:07.147 2009-01-26 16:31:19.610 3114599 11013762 10912300 2010-01-05 08:32:12.670 2010-01-05 08:32:12.670 8913096 8945857 3 2009-01-26 16:30:22.427 2009-01-26 16:31:30.273 8913090 11013757 10912300 2010-01-05 08:32:12.670 2010-01-05 08:32:12.670 11013756 10912300 2010-01-05 08:32:12.670 2010-01-05 08:32:12.670 11013759 10912300 2010-01-05 08:32:12.670 2010-01-05 08:32:12.670 11013758 10912300 2010-01-05 08:32:12.670 2010-01-05 08:32:12.670 16220244 16253010 2 2011-03-03 09:19:09.790 2011-03-03 11:10:36.920 16220240 16220246 16253012 3 2011-03-03 09:19:09.790 2011-03-03 11:11:45.117 16220240 16220249 16253015 2 2011-01-23 23:16:28.733 2011-03-03 08:57:56.990 15631042 16220237 16253003 7 2011-01-23 23:21:42.587 2011-01-24 10:40:38.770 15631044 16220238 16253004 1 2011-01-23 23:16:28.733 2011-01-23 23:16:28.733 15631042 16220242 16253008 1 2011-03-03 09:19:09.790 2011-03-03 09:19:09.790 16220240 8913118 8945878 25 2008-04-09 12:55:07.147 2009-01-26 16:31:30.260 3114599 8913116 8945876 4 2009-01-26 16:30:22.427 2009-01-26 16:38:03.427 8913090 8913122 8945882 1 2009-01-28 08:09:41.793 2009-01-28 08:09:41.793 8913120 9928714 3637534 2009-04-22 13:41:17.090 2009-04-22 13:41:17.090 24576 1 3670311 3637556 28016663 28049431 82 2013-08-03 11:21:10.280 2015-08-21 16:29:01.307 21365729 28016661 28049429 81 2013-08-03 11:21:10.280 2015-08-06 14:58:58.090 21365729 16220195 16252962 18 2011-02-09 09:50:05.230 2011-02-22 19:08:26.180 15631445 3670289 3637534 16220193 16252960 17 2011-02-09 09:50:05.230 2011-02-19 12:55:51.930 15631445 19533123 10354882 2012-12-30 11:51:19.450 2012-12-30 11:51:19.450 19533122 19041520 2012-12-30 11:49:24.857 2012-12-30 11:49:24.857 19533121 18580092 2012-12-30 11:48:39.243 2012-12-30 11:48:39.243 19533120 18580092 2012-12-30 11:48:39.243 2012-12-30 11:48:39.243 19533124 10354882 2012-12-30 11:51:19.450 2012-12-30 11:51:19.450 16810135 16777373 9798350 9831102 23 2009-01-06 09:56:05.890 2009-05-08 09:31:37.207 8355883 9798352 9831104 24 2009-01-06 09:56:05.890 2009-05-08 09:46:27.177 8355883 9798354 9831106 25 2009-01-06 09:56:05.890 2009-05-08 09:56:51.103 8355883 9798355 9831107 26 2009-01-06 09:56:05.890 2009-05-08 09:58:23.067 8355883 9798357 9831109 27 2009-01-06 09:56:05.890 2009-05-08 09:59:16.037 8355883 9798362 9831113 29 2009-01-06 09:56:05.890 2009-05-08 12:05:07.253 8355883 9798361 9831112 28 2009-01-06 09:56:05.890 2009-05-08 11:57:45.107 8355883 9798365 9831116 30 2009-01-06 09:56:05.890 2009-05-08 12:09:30.453 8355883 9798367 9831118 31 2009-01-06 09:56:05.890 2009-05-09 14:54:13.033 8355883 9798369 9831120 32 2009-01-06 09:56:05.890 2009-05-09 14:55:00.090 8355883 9798371 9831122 33 2009-01-06 09:56:05.890 2009-05-09 14:55:40.820 8355883 9798374 9831124 34 2009-01-06 09:56:05.890 2009-05-09 14:59:59.820 8355883 9798376 9831126 35 2009-01-06 09:56:05.890 2009-05-09 15:07:28.913 8355883 16810221 16777460 11013743 10912300 2010-01-05 08:32:12.670 2010-01-05 08:32:12.670 11013742 10912300 2010-01-05 08:32:12.670 2010-01-05 08:32:12.670 11013741 10912300 2010-01-05 08:32:12.670 2010-01-05 08:32:12.670 11013740 10912300 2010-01-05 08:32:12.670 2010-01-05 08:32:12.670 11013747 10912300 2010-01-05 08:32:12.670 2010-01-05 08:32:12.670 11013746 10912300 2010-01-05 08:32:12.670 2010-01-05 08:32:12.670 11013745 10912300 2010-01-05 08:32:12.670 2010-01-05 08:32:12.670 11013744 10912300 2010-01-05 08:32:12.670 2010-01-05 08:32:12.670 9798342 9831094 19 2009-01-06 09:56:05.890 2009-05-08 09:21:21.780 8355883 9798339 9831091 17 2009-01-06 09:56:05.890 2009-02-18 11:48:14.667 8355883 19072763 19040044 9798340 9831092 18 2009-01-06 09:56:05.890 2009-05-08 09:20:53.600 8355883 19072769 19040050 9798346 9831098 22 2009-01-06 09:56:05.890 2009-05-08 09:28:19.733 8355883 9798343 9831095 20 2009-01-06 09:56:05.890 2009-05-08 09:25:16.797 8355883 9798344 9831096 21 2009-01-06 09:56:05.890 2009-05-08 09:26:17.597 8355883 19039419 19072159 10 2012-06-26 10:17:36.350 2012-06-26 11:40:52.857 19039402 19039421 19072161 11 2012-06-26 10:17:36.350 2012-06-26 11:41:07.123 19039402 19039422 19072162 12 2012-06-26 10:17:36.350 2012-06-26 11:47:13.487 19039402 19039423 19072163 13 2012-06-26 10:17:36.350 2012-06-26 11:50:13.903 19039402 19039412 19072152 6 2012-06-26 10:17:36.350 2012-06-26 11:13:55.133 19039402 19039414 19072154 7 2012-06-26 10:17:36.350 2012-06-26 11:17:02.373 19039402 6717442 6259430 2008-10-21 14:36:07.163 2008-10-21 14:36:07.163 159767 1 19039416 19072156 8 2012-06-26 10:17:36.350 2012-06-26 11:27:44.767 19039402 6717441 6259430 2008-10-21 14:32:11.293 2008-10-21 14:32:11.293 149587 1 15990786 16023554 5 2011-02-09 06:25:02.520 2011-02-16 05:55:00.250 15631441 19039418 19072158 9 2012-06-26 10:17:36.350 2012-06-26 11:38:29.113 19039402 19039404 19072144 1 2012-06-26 10:17:36.350 2012-06-26 10:17:36.350 19039402 15990790 16023558 7 2011-02-09 06:25:02.520 2011-02-16 06:10:26.480 15631441 19039406 19072146 3 2012-06-26 10:17:36.350 2012-06-26 10:49:34.017 19039402 15990788 16023556 6 2011-02-09 06:25:02.520 2011-02-16 06:01:09.523 15631441 9798416 9831167 10 2009-05-09 15:33:01.367 2009-05-11 13:43:06.760 9798378 19039405 19072145 2 2012-06-26 10:17:36.350 2012-06-26 10:47:33.860 19039402 19039408 19072148 4 2012-06-26 10:17:36.350 2012-06-26 10:50:06.977 19039402 19039410 19072150 5 2012-06-26 10:17:36.350 2012-06-26 11:12:45.567 19039402 19072772 19040054 9798407 9831157 8 2009-05-09 15:33:01.367 2009-05-11 13:26:33.267 9798378 9798410 9831160 9 2009-05-09 15:33:01.367 2009-05-11 13:33:25.330 9798378 11272371 Serial Port->usbserial-A9006R0V. I set the communication settings to 115200, No flow control. Then I opened up a connection by selecting Connection->Open Connection. Nothing seems to happen, but if you then plug the 5V power adapter into the board, you should see the boot sequence start. It takes quite a bit of time for the Angstrom kernel to start up (like several minutes). Eventually, the login prompt will come up and you can login as root (no password). After I logged in a played around for a bit, I issued the shutdown command and then powered off the board and unplugged it from my mac. I connected the LCD screen via the video instructions on http://www.gumstix.com and added the two wireless antennas. I then plugged the Chestnut back into my Mac, established a connection through MacWise and then powered up. When I saw the "Hit any key to stop autoboot:" message, I hit the space bar.]]> 11239606 9798403 9831153 6 2009-05-09 15:33:01.367 2009-05-10 16:14:45.557 9798378 9798405 9831155 7 2009-05-09 15:33:01.367 2009-05-11 13:15:58.140 9798378 9798400 9831150 1 2009-05-11 10:01:43.157 2009-05-11 10:01:43.157 9798398 15990803 16023570 8 2011-02-09 06:25:02.520 2011-02-16 06:16:51.300 15631441 15990805 16023572 9 2011-02-09 06:25:02.520 2011-02-16 10:38:33.113 15631441 9798396 9831146 36 2009-01-06 09:56:05.890 2009-05-09 15:11:25.603 8355883 15990809 16023576 10 2011-02-09 06:25:02.520 2011-02-16 10:40:25.277 15631441 15990811 16023578 11 2011-02-09 06:25:02.520 2011-02-16 11:32:04.687 15631441 9798388 9831138 4 2009-05-09 15:33:01.367 2009-05-09 15:53:02.327 9798378 9798390 9831140 5 2009-05-09 15:33:01.367 2009-05-10 16:08:07.273 9798378 19072807 19040089 9798384 9831134 3 2009-05-09 15:33:01.367 2009-05-09 15:44:03.093 9798378 15990819 16023586 4 2011-02-09 09:50:05.230 2011-02-10 16:39:19.837 15631445 15990821 16023588 5 2011-02-09 09:50:05.230 2011-02-17 13:37:44.350 15631445 9798380 9831130 1 2009-05-09 15:33:01.367 2009-05-09 15:33:01.367 9798378 15990823 16023590 6 2011-02-09 09:50:05.230 2011-02-17 13:49:22.980 15631445 9798382 9831132 2 2009-05-09 15:33:01.367 2009-05-09 15:37:25.340 9798378 15990825 16023592 7 2011-02-09 09:50:05.230 2011-02-17 13:51:19.883 15631445 14024808 12484688 2010-07-14 12:20:03.537 2010-07-14 12:20:03.537 14024809 12484688 2010-07-14 12:20:03.537 2010-07-14 12:20:03.537 19039368 19072109 5 2012-06-25 13:36:31.327 2012-06-25 13:41:14.857 19039359 14024810 12484688 2010-07-14 12:20:03.537 2010-07-14 12:20:03.537 29655066 1 21365729 2017-01-25 07:42:15.033 2017-01-25 07:42:15.033 19039369 19072110 6 2012-06-25 13:36:31.327 2012-06-25 13:43:23.307 19039359 14024811 12484688 2010-07-14 12:20:03.537 2010-07-14 12:20:03.537 15990832 16023599 12 2011-02-09 06:25:02.520 2011-02-16 11:57:24.703 15631441 14024804 12484688 2010-07-14 12:20:03.537 2010-07-14 12:20:03.537 14024805 12484688 2010-07-14 12:20:03.537 2010-07-14 12:20:03.537 3670051 3637286 19039364 19072105 3 2012-06-25 13:36:31.327 2012-06-25 13:37:45.657 19039359 15990830 16023597 10 2011-02-09 09:50:05.230 2011-02-17 14:15:48.457 15631445 14024806 12484688 2010-07-14 12:20:03.537 2010-07-14 12:20:03.537 15990827 16023594 8 2011-02-09 09:50:05.230 2011-02-17 14:02:27.547 15631445 14024807 12484688 2010-07-14 12:20:03.537 2010-07-14 12:20:03.537 19039366 19072107 4 2012-06-25 13:36:31.327 2012-06-25 13:40:10.233 19039359 15990828 16023595 9 2011-02-09 09:50:05.230 2011-02-17 14:14:52.033 15631445 19039360 19072101 1 2012-06-25 13:36:31.327 2012-06-25 13:36:31.327 19039359 19039362 19072103 2 2012-06-25 13:36:31.327 2012-06-25 13:37:01.320 19039359 14024812 12484688 2010-07-14 12:20:03.537 2010-07-14 12:20:03.537 23199974 23167213 15990847 16023614 13 2011-02-09 06:25:02.520 2011-02-17 18:02:00.057 15631441 15990857 16023624 13 2011-02-09 09:50:05.230 2011-02-19 10:34:53.243 15631445 14024803 12484688 2010-07-14 12:20:03.537 2010-07-14 12:20:03.537 14024802 12484688 2010-07-14 12:20:03.537 2010-07-14 12:20:03.537 15990855 16023622 12 2011-02-09 09:50:05.230 2011-02-19 10:26:14.827 15631445 15990853 16023620 11 2011-02-09 09:50:05.230 2011-02-17 14:19:39.547 15631445 15990851 16023618 14 2011-02-09 06:25:02.520 2011-02-18 12:04:47.557 15631441 15990863 16023630 16 2011-02-09 09:50:05.230 2011-02-19 12:49:28.017 15631445 19039399 19072139 211 2009-01-06 09:56:05.890 2012-06-04 17:48:15.827 8355883 19039400 19072140 18 2012-06-25 13:36:31.327 2012-06-25 17:04:17.520 19039359 19039397 19072137 17 2012-06-25 13:36:31.327 2012-06-25 17:00:49.330 19039359 15990859 16023626 14 2011-02-09 09:50:05.230 2011-02-19 10:47:09.087 15631445 15990861 16023628 15 2011-02-09 09:50:05.230 2011-02-19 12:01:46.240 15631445 19039396 19072136 16 2012-06-25 13:36:31.327 2012-06-25 16:07:49.153 19039359 19300620 3145740 2012-06-18 17:34:30.537 2012-06-18 17:34:30.537 19039388 19072129 15 2012-06-25 13:36:31.327 2012-06-25 15:35:40.187 19039359 19039386 19072127 14 2012-06-25 13:36:31.327 2012-06-25 15:35:29.137 19039359 19039385 19072126 13 2012-06-25 13:36:31.327 2012-06-25 14:59:15.540 19039359 19039383 19072124 12 2012-06-25 13:36:31.327 2012-06-25 14:58:38.150 19039359 19039382 19072123 11 2012-06-25 13:36:31.327 2012-06-25 14:50:31.427 19039359 23199966 tags ** 1 do not suppress * setecho=0 suppress echoed characters ** 1 do not suppress * setprompt=0 suppress 'S>' ** 1 do not suppress * setbaud=115200 ** 9600, 38400, 115200 * setsampleperiod=1 ** n seconds between scans when running continuously. Each sample is comprised of an average of 8 scans. * Operational commands ** ts returns a measurement in one of the above formats. ** tsc continuously samples and returns the measurement in one of the above formats. The update rate is 1Hz which is an average of 16 samples. Return to interactive mode via the ESC key. ** gethd ** getcd ** getec ** getsd ** getcc * Electrical ** Voltage input 11VDC - 18VDC ** Current consumption 82mA at 12VDC h3. DGH D5451 Module setup * Setup the D5451 to 115200 baud, procedure: ** Wire the default pin on the D5451 to Ground, set terminal to 300 baud (8N1) with serial port connected and 12v supplied (47mA) ** $1WE (echo \*) ** $1SU3108E1C2 (echo \*) ** change terminal settings to 115200, then disconnect the Default pin from ground (leave floating) ** $1RS should return \*3108E1C2 ** $1RD will take a sample, returns \*-99999.99 with input floating (no thermistor) h3. Serial Protocol * Power All (0=off, 1=on) ** $1PA0 ** response ** 0 * Channel 1 Power Control = 0 (Off) ** $1PC0 ** Response: ** 0 * Channel 1 Power Control = 1 (On) ** $1PC1 ** Response: ** 1 * Channel 1 Power Read ** $1PR ** Response: ** 1 * Read Block ** $1RB read temperature sensor block (4 channels) ** $5RB read pH sensor block (Seabird 18s) ** Response: ** \*+02712.00 ** \*+00200.00 ** \*+00125.76 ** \*+00347.95 * Read Data ** $1RD read tDGH channel 1 (temperature ch 1) ** $2RD read tDGH channel 2 (temperature ch 2) ** $3RD read tDGH channel 3 (temperature ch 3) ** $4RD read tDGH channel 4 (temperature ch 4) ** $5RD read tDGH channel 5 (pH sensor ch 1) ** $6RD read tDGH channel 6 (pH sensor ch 2) ** $7RD read tDGH channel 7 (pH sensor ch 3) ** $8RD read tDGH channel 8 (pH sensor ch 4) ** $9RD read tDGH channel 9 (pH sensor ch 5)]]> 23167205 19039380 19072121 10 2012-06-25 13:36:31.327 2012-06-25 14:48:11.537 19039359 19039379 19072120 9 2012-06-25 13:36:31.327 2012-06-25 13:53:38.627 19039359 19072868 19040151 19072869 19040153 9798445 9831196 14 2008-08-04 13:42:13.733 2009-03-03 16:31:41.703 5832921 19072870 19040155 19072871 19040157 19039374 19072115 8 2012-06-25 13:36:31.327 2012-06-25 13:48:28.360 19039359 19072872 19040159 19072873 19040161 19039371 19072112 7 2012-06-25 13:36:31.327 2012-06-25 13:43:35.860 19039359 18350272 3637534 2011-08-03 14:50:14.663 2011-08-03 14:50:14.663 19072947 19040241 9798516 9831262 2 2009-05-11 10:01:43.157 2009-05-11 12:05:46.863 9798398 9798517 9831263 3 2009-05-11 10:01:43.157 2009-05-13 14:48:32.710 9798398 10454080 10354800 2009-05-29 15:36:18.537 2009-05-29 15:36:18.537 10454078 10354800 2009-05-29 15:36:18.537 2009-05-29 15:36:18.537 10454079 10354800 2009-05-29 15:36:18.537 2009-05-29 15:36:18.537 14024907 7766027 2010-07-28 08:05:15.007 2010-07-28 08:05:15.007 14024906 7766027 2010-07-28 08:05:15.007 2010-07-28 08:05:15.007 15706816 10912227 2011-01-10 11:02:05.843 2011-01-10 11:02:05.843 27558101 27590866 34 2013-08-03 11:21:10.280 2015-08-01 08:49:05.663 21365729 15706817 10912227 2011-01-10 11:02:05.843 2011-01-10 11:02:05.843 15706818 10912227 2011-01-10 11:02:05.843 2011-01-10 11:02:05.843 27558099 27590864 32 2013-08-03 11:21:10.280 2015-08-01 08:45:31.467 21365729 15706819 10912227 2011-01-10 11:02:05.843 2011-01-10 11:02:05.843 9798644 9831384 38 2009-01-06 09:56:05.890 2009-05-21 11:25:18.790 8355883 27558100 27590865 33 2013-08-03 11:21:10.280 2015-08-01 08:48:17.173 21365729 15706812 10912227 2011-01-10 11:02:05.843 2011-01-10 11:02:05.843 5374051 5406806 17 2008-05-12 09:51:47.077 2008-06-11 14:46:30.897 3638030 27558105 27590870 36 2013-08-03 11:21:10.280 2015-08-01 08:53:21.703 21365729 15706813 10912227 2011-01-10 11:02:05.843 2011-01-10 11:02:05.843 19165652 19040970 2012-09-26 08:04:20.663 2012-09-26 08:04:20.663 15706814 10912227 2011-01-10 11:02:05.843 2011-01-10 11:02:05.843 25919555 25952323 7 2014-05-20 05:54:13.407 2014-05-20 09:15:20.377 25919541 27558103 27590868 35 2013-08-03 11:21:10.280 2015-08-01 08:49:47.577 21365729 15706815 10912227 2011-01-10 11:02:05.843 2011-01-10 11:02:05.843 25919556 25952324 8 2014-05-20 05:54:13.407 2014-05-20 09:22:02.887 25919541 15706808 10912227 2011-01-10 11:02:05.843 2011-01-10 11:02:05.843 25919553 25952321 6 2014-05-20 05:54:13.407 2014-05-20 09:14:40.113 25919541 15706809 10912227 2011-01-10 11:02:05.843 2011-01-10 11:02:05.843 27558094 27590859 30 2013-08-03 11:21:10.280 2015-08-01 08:28:12.117 21365729 15706810 10912227 2011-01-10 11:02:05.843 2011-01-10 11:02:05.843 25919551 25952319 5 2014-05-20 05:54:13.407 2014-05-20 08:46:56.610 25919541 27558091 27590856 28 2013-08-03 11:21:10.280 2015-08-01 08:19:41.960 21365729 15706811 10912227 2011-01-10 11:02:05.843 2011-01-10 11:02:05.843 27558092 27590857 29 2013-08-03 11:21:10.280 2015-08-01 08:27:34.927 21365729 25919549 25952317 4 2014-05-20 05:54:13.407 2014-05-20 08:38:53.227 25919541 27558097 27590862 31 2013-08-03 11:21:10.280 2015-08-01 08:43:11.530 21365729 9798641 9831381 17 2008-10-21 10:34:48.373 2009-05-21 11:27:14.383 6259430 25919547 25952315 3 2014-05-20 05:54:13.407 2014-05-20 06:33:26.970 25919541 15706807 10912227 2011-01-10 11:02:05.843 2011-01-10 11:02:05.843 9798640 9831380 37 2009-01-06 09:56:05.890 2009-05-11 09:46:33.083 8355883 9798662 9831401 2 2008-12-29 11:40:49.410 2009-05-26 13:49:48.137 8355849 19169335 15630488 2010-12-15 13:45:00.497 2012-04-13 16:20:06.460 2220 3 15728670 25919545 25952313 2 2014-05-20 05:54:13.407 2014-05-20 06:08:15.300 25919541 9798661 9831400 40 2009-01-06 09:56:05.890 2009-05-26 13:32:02.333 8355883 27558117 27590882 42 2013-08-03 11:21:10.280 2015-08-01 09:20:36.907 21365729 19169334 15630488 2010-12-15 13:45:00.497 2010-12-15 13:47:22.643 2194 2 15728670 9798660 9831399 39 2009-01-06 09:56:05.890 2009-05-21 11:28:27.773 8355883 19169337 15630488 2010-12-15 13:45:00.497 2012-04-13 16:34:59.317 4781 5 15728670 25919543 25952311 1 2014-05-20 05:54:13.407 2014-05-20 05:54:13.407 25919541 27558115 27590880 41 2013-08-03 11:21:10.280 2015-08-01 09:15:05.583 21365729 19169336 15630488 2010-12-15 13:45:00.497 2012-04-13 16:27:11.243 3623 4 15728670 19169339 15630488 2010-12-15 13:45:00.497 2012-04-13 16:42:24.813 6167 7 15728670 9798665 9831404 41 2009-01-06 09:56:05.890 2009-05-26 13:32:43.487 8355883 27558121 27590886 44 2013-08-03 11:21:10.280 2015-08-01 09:34:23.313 21365729 19169338 15630488 2010-12-15 13:45:00.497 2012-04-13 16:35:16.010 5209 6 15728670 19169341 15630488 2012-04-13 16:47:07.090 2012-04-13 16:47:07.090 133 1 19169340 27558119 27590884 43 2013-08-03 11:21:10.280 2015-08-01 09:29:39.017 21365729 19169340 15630488 2012-04-13 16:47:07.090 2012-12-10 15:28:58.837 6944 8 27558110 27590875 39 2013-08-03 11:21:10.280 2015-08-01 09:05:44.577 21365729 25919536 25952304 233 2009-01-06 09:56:05.890 2014-01-08 09:57:26.837 8355883 27558108 27590873 38 2013-08-03 11:21:10.280 2015-08-01 09:04:58.187 21365729 27558107 27590872 37 2013-08-03 11:21:10.280 2015-08-01 09:02:45.530 21365729 5374030 5406789 22 2008-04-22 12:26:44.157 2008-05-21 15:13:26.050 3637534 27558112 27590877 40 2013-08-03 11:21:10.280 2015-08-01 09:07:03.490 21365729 5374029 5406788 22 2008-04-22 12:26:44.157 2008-05-21 15:13:26.050 3637534 9798675 9831414 43 2009-01-06 09:56:05.890 2009-05-26 13:52:15.937 8355883 10387566 10354800 9798678 9831417 6 2008-12-29 11:40:49.410 2009-05-26 14:22:14.333 8355849 9798679 9831418 1 2009-05-26 14:40:54.140 2009-05-26 14:40:54.140 9798677 9798682 9831421 15 2008-08-04 13:42:13.733 2009-05-12 16:47:32.530 5832921 9798667 9831406 42 2009-01-06 09:56:05.890 2009-05-26 13:51:24.380 8355883 9798669 9831408 3 2008-12-29 11:40:49.410 2009-05-26 13:49:48.193 8355849 9798671 9831410 4 2008-12-29 11:40:49.410 2009-05-26 13:59:25.497 8355849 9798673 9831412 5 2008-12-29 11:40:49.410 2009-05-26 14:07:26.357 8355849 9798692 9831431 13 2009-05-09 15:33:01.367 2009-05-27 09:36:01.923 9798378 9798694 9831433 14 2009-05-09 15:33:01.367 2009-05-27 09:51:23.403 9798378 19156713 19040089 2012-07-15 08:19:07.197 2012-07-15 08:19:07.197 12550223 12484688 19156712 19040089 2012-07-15 08:19:07.197 2012-07-15 08:19:07.197 9798696 9831435 15 2009-05-09 15:33:01.367 2009-05-27 09:55:09.597 9798378 27558089 27590854 27 2013-08-03 11:21:10.280 2015-07-23 22:42:34.573 21365729 9798686 9831425 11 2009-05-09 15:33:01.367 2009-05-11 13:52:05.857 9798378 19165651 19040970 2012-09-26 08:04:20.663 2012-09-26 08:04:20.663 9798685 9831424 1 2009-05-27 09:19:26.627 2009-05-27 09:19:26.627 9798684 9798688 9831427 12 2009-05-09 15:33:01.367 2009-05-27 09:22:08.420 9798378 27558042 27590807 25 2013-08-03 11:21:10.280 2015-07-23 21:02:40.953 21365729 27558040 27590805 24 2013-08-03 11:21:10.280 2015-07-23 17:21:01.993 21365729 27558037 27590802 23 2013-08-03 11:21:10.280 2015-07-23 17:19:01.580 21365729 27558035 27590800 22 2013-08-03 11:21:10.280 2015-07-23 17:10:35.927 21365729 27558032 27590797 21 2013-08-03 11:21:10.280 2015-07-23 09:49:27.177 21365729 27558044 27590809 26 2013-08-03 11:21:10.280 2015-07-23 21:21:41.540 21365729 5373956 5406724 16 2008-05-12 09:51:47.077 2008-06-11 10:51:06.203 3638030 27557999 27590765 19 2013-08-03 11:21:10.280 2015-07-22 21:19:39.207 21365729 11141121 11108357 11108356 11108371 11108358 11108353 11108355 11108354 11108360 11108359 10356476 27557996 27590762 17 2013-08-03 11:21:10.280 2015-07-22 21:05:45.457 21365729 11141122 11108369 11108367 11108362 11108370 11108368 11108361 11108365 11108364 11108366 11108363 10356471 19169342 15630488 2010-12-15 13:45:00.497 2012-04-13 16:43:09.263 6172 8 15728670 27557998 27590764 18 2013-08-03 11:21:10.280 2015-07-22 21:13:17.143 21365729 27558013 27590779 20 2013-08-03 11:21:10.280 2015-07-22 21:20:49.787 21365729 19039055 19071814 3 2012-06-04 17:50:29.237 2012-06-04 17:58:58.020 19039049 7176216 7208981 7 2008-08-27 13:39:41.480 2008-10-29 17:31:32.180 6259010 7176214 7208979 6 2008-08-27 13:39:41.480 2008-10-29 15:48:58.153 6259010 27557970 27590736 4 2013-08-03 11:21:10.280 2014-03-20 12:24:05.053 21365729 19039052 19071811 1 2012-06-04 17:50:29.237 2012-06-04 17:50:29.237 19039049 19039054 19071813 2 2012-06-04 17:50:29.237 2012-06-04 17:54:24.660 19039049 27557974 27590740 6 2013-08-03 11:21:10.280 2015-07-21 12:26:59.723 21365729 7176209 7208974 5 2008-08-27 13:39:41.480 2008-10-29 14:28:25.240 6259010 27557972 27590738 5 2013-08-03 11:21:10.280 2015-07-21 12:22:39.203 21365729 7176207 7208972 4 2008-08-27 13:39:41.480 2008-09-02 16:06:41.187 6259010 27557978 27590744 8 2013-08-03 11:21:10.280 2015-07-21 17:48:02.170 21365729 27557976 27590742 7 2013-08-03 11:21:10.280 2015-07-21 17:45:42.147 21365729 27557982 27590748 10 2013-08-03 11:21:10.280 2015-07-22 10:02:32.397 21365729 27557980 27590746 9 2013-08-03 11:21:10.280 2015-07-21 17:52:49.427 21365729 7176232 7208994 45 2007-12-03 13:18:03.697 2008-05-28 21:30:51.333 2162995 27557986 27590752 12 2013-08-03 11:21:10.280 2015-07-22 17:07:31.510 21365729 27557984 27590750 11 2013-08-03 11:21:10.280 2015-07-22 17:04:49.537 21365729 27557990 27590756 14 2013-08-03 11:21:10.280 2015-07-22 20:49:31.967 21365729 7176224 7208986 25 2008-04-22 12:26:44.157 2008-09-10 10:32:04.250 3637534 27557988 27590754 13 2013-08-03 11:21:10.280 2015-07-22 20:32:20.617 21365729 27557994 27590760 16 2013-08-03 11:21:10.280 2015-07-22 21:04:47.800 21365729 27557992 27590758 15 2013-08-03 11:21:10.280 2015-07-22 20:55:18.257 21365729 19533631 17236193 2013-01-10 13:09:34.740 2013-01-10 13:09:34.740 19533635 17236193 2013-01-10 13:09:34.740 2013-01-10 13:09:34.740 19533634 17236193 2013-01-10 13:09:34.740 2013-01-10 13:09:34.740 19533633 17236193 2013-01-10 13:09:34.740 2013-01-10 13:09:34.740 19533632 17236193 2013-01-10 13:09:34.740 2013-01-10 13:09:34.740 19533638 17236193 2013-01-10 13:09:34.740 2013-01-10 13:09:34.740 7176199 7208964 21 2008-04-09 12:55:07.147 2008-08-27 13:36:39.827 3114599 19533639 17236193 2013-01-10 13:09:34.740 2013-01-10 13:09:34.740 19533636 17236193 2013-01-10 13:09:34.740 2013-01-10 13:09:34.740 19533637 17236193 2013-01-10 13:09:34.740 2013-01-10 13:09:34.740 19156590 19040054 2012-07-14 14:54:08.217 2012-07-14 14:54:08.217 19533640 17236193 2013-01-10 13:09:34.740 2013-01-10 13:09:34.740 19533641 17236193 2013-01-10 13:09:34.740 2013-01-10 13:09:34.740 19039048 19071807 210 2009-01-06 09:56:05.890 2012-04-13 16:17:21.537 8355883 10387592 10354826 5374115 5406865 21 2008-05-12 09:51:47.077 2008-06-17 10:02:00.960 3638030 27099540 27066777 15237242 Add/Remove Software) # In the Search tab, enter erlang and select the 14B version of erlang. It will then install a bunch of dependencies (which is a good thing). # Go to the rabbitmq download page and grab the [RHEL version of the RPM|http://www.rabbitmq.com/releases/rabbitmq-server/v2.3.1/rabbitmq-server-2.3.1-1.noarch.rpm] # Use RPM or yum localinstall to install the rabbitmq RPM. # Once it is installed, it can be started using: {noformat} /sbin/service rabbitmq-server start {noformat} # It can be setup to start as a service by using: {noformat} chkconfig rabbitmq-server on {noformat} h5. Management Plugins # If you want the web management console, download the .ez files from the [plugins page|http://www.rabbitmq.com/plugins.html] and install them in the /usr/lib/rabbitmq/lib/rabbitmq_server-2.3.1/plugins and restart the server. {note:Plugins are picky} I found that while the core Rabbit server was somewhat immune to the version of Erlang, the plugins were not. {note} h5. LDAP Authentication # I was able to configure the RabbitMQ server to use our internal LDAP system in a chained configuration with the internal RabbitMQ authentication system. This allows you to use your MBARI logins on the RabbitMQ server. {note:title=One VERY icky caveat} Due to the way we have our Active Directory configured on site, the user DN's are in the form of *Lastname, Firstname*. While it works, that makes users have to login with a username like {noformat} Gomes\\, Kevin {noformat} It is ugly and hopefully we can address this in our Active Directory in the future. That said, the LDAP integration works well. {note} # Download the [ldap-auth plugin|http://www.rabbitmq.com/releases/plugins/v2.3.1/rabbitmq-auth-backend-ldap-2.3.1.ez] and put in the /usr/lib/rabbitmq/lib/rabbitmq_server-2.3.1/plugins directory. # Create (or add configuration) the /etc/rabbitmq/rabbitmq.config file with the following: {noformat} [ {rabbit, [ {auth_backends, [rabbit_auth_backend_ldap, rabbit_auth_backend_internal]} ] }, {rabbit_auth_backend_ldap, [ {servers, ["ldap.shore.mbari.org"]}, {user_dn_pattern, ["CN=${username},OU=Users,OU=AllUsers,DC=shore,DC=mbari,DC=org"]} ] } ]. {noformat} # Restart the server # With the LDAP authentication working, you can now control access permissions on resources (vhosts, exchanges, bindings, queues). See the following for more details: ## [RabbitMQ LDAP Authentication README|http://hg.rabbitmq.com/rabbitmq-auth-backend-ldap/file/default/README] ## [RabbitMQ LDAP Authorization README|http://hg.rabbitmq.com/rabbitmq-auth-backend-ldap/file/default/README-authorisation]]]> 15204478 3112964 3178500 35 2007-12-03 13:18:03.697 2008-01-02 12:56:37.217 2162995 24018989 24052291 2014-01-08 10:07:06.987 2014-01-08 10:08:02.713 1929 2 5374075 5406829 56 2008-04-14 16:11:58.510 2008-06-17 10:47:17.900 3637286 19169471 19039359 2012-06-25 14:57:03.640 2012-06-25 14:57:03.640 231618 1 19169492 19040044 2012-07-13 10:44:47.273 2012-07-13 10:44:47.273 313061 1 5374062 5406817 19 2008-05-12 09:51:47.077 2008-06-16 17:06:46.910 3638030 19169491 19040044 2012-07-13 10:44:27.880 2012-07-13 10:44:27.880 379624 1 5374060 5406815 18 2008-05-12 09:51:47.077 2008-06-16 12:53:33.973 3638030 3112990 3178524 36 2007-12-03 13:18:03.697 2008-01-04 12:40:37.740 2162995 15237213 15204448 3112992 3178526 37 2007-12-03 13:18:03.697 2008-01-07 10:01:36.663 2162995 3112994 3178528 38 2007-12-03 13:18:03.697 2008-01-07 10:02:54.213 2162995 5374070 5406825 54 2008-04-14 16:11:58.510 2008-05-15 14:41:29.600 3637286 3112996 3178530 39 2007-12-03 13:18:03.697 2008-01-07 10:32:49.453 2162995 10387648 10354884 5374068 5406823 20 2008-05-12 09:51:47.077 2008-06-16 17:15:04.843 3638030 5374073 5406827 55 2008-04-14 16:11:58.510 2008-06-17 10:40:54.787 3637286 10387646 10354882 24018990 24052291 2014-01-08 10:07:06.987 2014-01-08 10:07:06.987 133 1 24018989 28278838 8355883 2015-08-26 12:03:05.510 2015-08-26 12:03:05.510 17858740 17891489 18 2011-06-06 21:36:16.963 2011-06-28 13:25:52.493 17236193 28278839 8355883 2015-08-26 12:03:05.510 2015-08-26 12:03:05.510 19169592 15630488 2012-04-13 16:47:07.090 2012-12-10 14:18:06.387 6970 7 19169340 18350704 16416807 2011-08-04 15:13:35.533 2011-08-04 15:13:35.533 28278836 8355883 2015-08-26 12:03:05.510 2015-08-26 12:03:05.510 19169591 15630488 2012-04-13 16:47:07.090 2012-12-10 14:01:35.113 6377 6 19169340 18350705 16416807 2011-08-04 15:13:35.533 2011-08-04 15:13:35.533 28278837 8355883 2015-08-26 12:03:05.510 2015-08-26 12:03:05.510 19169590 15630488 2012-04-13 16:47:07.090 2012-11-12 16:13:11.887 4962 5 19169340 28278842 8355883 2015-08-26 12:03:05.510 2015-08-26 12:03:05.510 17858744 17891493 19 2011-06-06 21:36:16.963 2011-06-28 13:53:03.683 17236193 18350703 16416807 2011-08-04 15:13:35.533 2011-08-04 15:13:35.533 28278843 8355883 2015-08-26 12:03:05.510 2015-08-26 12:03:05.510 28278840 8355883 2015-08-26 12:03:05.510 2015-08-26 12:03:05.510 17858746 17891495 20 2011-06-06 21:36:16.963 2011-06-28 14:05:23.047 17236193 28278841 8355883 2015-08-26 12:03:05.510 2015-08-26 12:03:05.510 17858731 17891480 13 2011-06-06 21:36:16.963 2011-06-07 09:36:58.453 17236193 28278846 8355883 2015-08-26 12:03:05.510 2015-08-26 12:03:05.510 28278847 8355883 2015-08-26 12:03:05.510 2015-08-26 12:03:05.510 17858733 17891482 14 2011-06-06 21:36:16.963 2011-06-28 12:52:04.673 17236193 28278844 8355883 2015-08-26 12:03:05.510 2015-08-26 12:03:05.510 17858734 17891483 15 2011-06-06 21:36:16.963 2011-06-28 12:58:39.483 17236193 28278845 8355883 2015-08-26 12:03:05.510 2015-08-26 12:03:05.510 28278850 8355883 2015-08-26 12:03:05.510 2015-08-26 12:03:05.510 17858736 17891485 16 2011-06-06 21:36:16.963 2011-06-28 12:58:48.037 17236193 28278851 8355883 2015-08-26 12:03:05.510 2015-08-26 12:03:05.510 28278848 8355883 2015-08-26 12:03:05.510 2015-08-26 12:03:05.510 17858738 17891487 17 2011-06-06 21:36:16.963 2011-06-28 13:10:45.530 17236193 28278849 8355883 2015-08-26 12:03:05.510 2015-08-26 12:03:05.510 28278855 8355883 2015-08-26 12:03:05.510 2015-08-26 12:03:05.510 10912298 10945053 90 2009-01-06 09:56:05.890 2009-12-23 08:24:14.497 8355883 28278854 8355883 2015-08-26 12:03:05.510 2015-08-26 12:03:05.510 28278853 8355883 2015-08-26 12:03:05.510 2015-08-26 12:03:05.510 28278852 8355883 2015-08-26 12:03:05.510 2015-08-26 12:03:05.510 28278859 8355883 2015-08-26 12:03:05.510 2015-08-26 12:03:05.510 28278858 8355883 2015-08-26 12:03:05.510 2015-08-26 12:03:05.510 28278857 8355883 2015-08-26 12:03:05.510 2015-08-26 12:03:05.510 28278856 8355883 2015-08-26 12:03:05.510 2015-08-26 12:03:05.510 17858748 17891497 21 2011-06-06 21:36:16.963 2011-06-28 14:15:27.383 17236193 28278863 8355883 2015-08-26 12:03:05.513 2015-08-26 12:03:05.513 28278862 8355883 2015-08-26 12:03:05.510 2015-08-26 12:03:05.510 28278861 8355883 2015-08-26 12:03:05.510 2015-08-26 12:03:05.510 17858749 17891498 22 2011-06-06 21:36:16.963 2011-06-28 14:40:31.407 17236193 28278860 8355883 2015-08-26 12:03:05.510 2015-08-26 12:03:05.510 28278867 8355883 2015-08-26 12:03:05.513 2015-08-26 12:03:05.513 28278866 8355883 2015-08-26 12:03:05.513 2015-08-26 12:03:05.513 28278865 8355883 2015-08-26 12:03:05.513 2015-08-26 12:03:05.513 28278864 8355883 2015-08-26 12:03:05.513 2015-08-26 12:03:05.513 28278868 8355883 2015-08-26 12:03:05.513 2015-08-26 12:03:05.513 19169559 15630488 2010-12-15 13:45:00.497 2012-11-12 15:31:35.857 11449 16 15728670 28278869 8355883 2015-08-26 12:03:05.513 2015-08-26 12:03:05.513 19169558 15630488 2012-04-13 16:47:07.090 2012-04-13 16:48:22.470 1240 2 19169340 28278870 8355883 2015-08-26 12:03:05.513 2015-08-26 12:03:05.513 19169561 15630488 2012-04-13 16:47:07.090 2012-11-12 15:47:07.687 3132 3 19169340 28278871 8355883 2015-08-26 12:03:05.513 2015-08-26 12:03:05.513 19169560 15630488 2010-12-15 13:45:00.497 2012-11-12 15:48:00.583 11451 17 15728670 28278872 8355883 2015-08-26 12:03:05.513 2015-08-26 12:03:05.513 19169563 15630488 2010-12-15 13:45:00.497 2012-11-12 15:48:03.553 11451 18 15728670 28278873 8355883 2015-08-26 12:03:05.513 2015-08-26 12:03:05.513 19169562 15630488 2012-04-13 16:47:07.090 2012-11-12 15:49:38.407 4922 4 19169340 28278874 8355883 2015-08-26 12:03:05.513 2015-08-26 12:03:05.513 28278875 8355883 2015-08-26 12:03:05.513 2015-08-26 12:03:05.513 10454644 10354826 2009-06-01 10:05:31.443 2009-06-01 10:05:31.443 10912239 10944994 6 2009-12-23 08:33:45.977 2009-12-23 08:59:13.287 10912227 28278876 8355883 2015-08-26 12:03:05.513 2015-08-26 12:03:05.513 19169551 15630488 2010-12-15 13:45:00.497 2012-04-13 17:20:00.533 6273 9 15728670 28278877 8355883 2015-08-26 12:03:05.513 2015-08-26 12:03:05.513 10912241 10944996 7 2009-12-23 08:33:45.977 2009-12-23 09:19:16.380 10912227 28278878 8355883 2015-08-26 12:03:05.513 2015-08-26 12:03:05.513 19169553 15630488 2010-12-15 13:45:00.497 2012-11-12 15:24:14.270 11946 11 15728670 10912242 10944997 8 2009-12-23 08:33:45.977 2009-12-23 09:27:47.663 10912227 28278879 8355883 2015-08-26 12:03:05.513 2015-08-26 12:03:05.513 19169552 15630488 2010-12-15 13:45:00.497 2012-11-12 15:20:47.830 12009 10 15728670 10912235 10944990 4 2009-12-23 08:33:45.977 2009-12-23 08:53:31.400 10912227 28278880 8355883 2015-08-26 12:03:05.513 2015-08-26 12:03:05.513 19169555 15630488 2010-12-15 13:45:00.497 2012-11-12 15:24:27.377 11946 13 15728670 28278881 8355883 2015-08-26 12:03:05.513 2015-08-26 12:03:05.513 19169554 15630488 2010-12-15 13:45:00.497 2012-11-12 15:24:14.377 11946 12 15728670 10912237 10944992 5 2009-12-23 08:33:45.977 2009-12-23 08:57:06.097 10912227 28278882 8355883 2015-08-26 12:03:05.513 2015-08-26 12:03:05.513 19169557 15630488 2010-12-15 13:45:00.497 2012-11-12 15:28:46.940 11970 15 15728670 28278883 8355883 2015-08-26 12:03:05.513 2015-08-26 12:03:05.513 5374253 5406996 22 2008-05-12 09:51:47.077 2008-06-17 14:41:50.373 3638030 19169556 15630488 2010-12-15 13:45:00.497 2012-11-12 15:26:15.677 11831 14 15728670 28278885 8355883 2015-08-26 12:03:05.513 2015-08-26 12:03:05.513 28278884 8355883 2015-08-26 12:03:05.513 2015-08-26 12:03:05.513 28278887 8355883 2015-08-26 12:03:05.513 2015-08-26 12:03:05.513 28278886 8355883 2015-08-26 12:03:05.513 2015-08-26 12:03:05.513 28278889 8355883 2015-08-26 12:03:05.513 2015-08-26 12:03:05.513 28278888 8355883 2015-08-26 12:03:05.513 2015-08-26 12:03:05.513 28278891 8355883 2015-08-26 12:03:05.513 2015-08-26 12:03:05.513 28377089 28409857 5 2015-08-26 12:01:56.270 2015-08-28 10:23:46.927 28213255 28278890 8355883 2015-08-26 12:03:05.513 2015-08-26 12:03:05.513 28278893 8355883 2015-08-26 12:03:05.513 2015-08-26 12:03:05.513 19169535 19040970 2012-09-26 07:37:14.783 2012-09-26 07:37:14.783 514818 1 28377091 28409859 6 2015-08-26 12:01:56.270 2015-08-28 14:02:47.030 28213255 28278892 8355883 2015-08-26 12:03:05.513 2015-08-26 12:03:05.513 28278895 8355883 2015-08-26 12:03:05.513 2015-08-26 12:03:05.513 28278894 8355883 2015-08-26 12:03:05.513 2015-08-26 12:03:05.513 28278897 8355883 2015-08-26 12:03:05.513 2015-08-26 12:03:05.513 28278896 8355883 2015-08-26 12:03:05.513 2015-08-26 12:03:05.513 10912254 10945009 15 2009-11-05 10:52:22.817 2009-11-05 13:10:28.297 10911981 28278899 8355883 2015-08-26 12:03:05.513 2015-08-26 12:03:05.513 28278898 8355883 2015-08-26 12:03:05.513 2015-08-26 12:03:05.513 17858672 17891429 203 2009-01-06 09:56:05.890 2011-05-23 16:12:04.443 8355883 11797067 11829820 1 2010-04-27 15:13:02.987 2010-04-27 15:13:02.987 11797066 11239524 11272291 38 2009-10-08 12:07:56.397 2010-01-22 09:53:05.803 10356476 28278795 8355883 2015-08-26 12:03:05.507 2015-08-26 12:03:05.507 11239523 11272290 37 2009-10-08 12:07:56.397 2010-01-22 09:21:36.950 10356476 28278794 8355883 2015-08-26 12:03:05.507 2015-08-26 12:03:05.507 28278793 8355883 2015-08-26 12:03:05.507 2015-08-26 12:03:05.507 11239525 11272292 39 2009-10-08 12:07:56.397 2010-01-22 09:53:44.407 10356476 28278792 8355883 2015-08-26 12:03:05.507 2015-08-26 12:03:05.507 28278791 8355883 2015-08-26 12:03:05.507 2015-08-26 12:03:05.507 11239527 11272294 40 2009-10-08 12:07:56.397 2010-01-22 09:54:37.037 10356476 28278790 8355883 2015-08-26 12:03:05.507 2015-08-26 12:03:05.507 28278789 8355883 2015-08-26 12:03:05.507 2015-08-26 12:03:05.507 11239529 11272296 41 2009-10-08 12:07:56.397 2010-01-22 15:41:56.967 10356476 28278803 8355883 2015-08-26 12:03:05.507 2015-08-26 12:03:05.507 28278802 8355883 2015-08-26 12:03:05.507 2015-08-26 12:03:05.507 28278801 8355883 2015-08-26 12:03:05.507 2015-08-26 12:03:05.507 28278800 8355883 2015-08-26 12:03:05.507 2015-08-26 12:03:05.507 28278799 8355883 2015-08-26 12:03:05.507 2015-08-26 12:03:05.507 28278798 8355883 2015-08-26 12:03:05.507 2015-08-26 12:03:05.507 28278797 8355883 2015-08-26 12:03:05.507 2015-08-26 12:03:05.507 11239521 11272288 36 2009-10-08 12:07:56.397 2009-12-09 09:12:49.277 10356476 28278796 8355883 2015-08-26 12:03:05.507 2015-08-26 12:03:05.507 28278808 8355883 2015-08-26 12:03:05.510 2015-08-26 12:03:05.510 28278809 8355883 2015-08-26 12:03:05.510 2015-08-26 12:03:05.510 28278810 8355883 2015-08-26 12:03:05.510 2015-08-26 12:03:05.510 28278811 8355883 2015-08-26 12:03:05.510 2015-08-26 12:03:05.510 28278804 8355883 2015-08-26 12:03:05.507 2015-08-26 12:03:05.507 28278805 8355883 2015-08-26 12:03:05.507 2015-08-26 12:03:05.507 28278806 8355883 2015-08-26 12:03:05.507 2015-08-26 12:03:05.507 28278807 8355883 2015-08-26 12:03:05.510 2015-08-26 12:03:05.510 28278816 8355883 2015-08-26 12:03:05.510 2015-08-26 12:03:05.510 10912299 10945054 91 2009-01-06 09:56:05.890 2010-01-05 08:31:00.607 8355883 28278817 8355883 2015-08-26 12:03:05.510 2015-08-26 12:03:05.510 19533448 19041368 2013-01-08 14:00:32.103 2013-01-08 14:00:32.103 28278818 8355883 2015-08-26 12:03:05.510 2015-08-26 12:03:05.510 28278819 8355883 2015-08-26 12:03:05.510 2015-08-26 12:03:05.510 10912302 10945057 92 2009-01-06 09:56:05.890 2010-01-05 08:31:19.613 8355883 28278812 8355883 2015-08-26 12:03:05.510 2015-08-26 12:03:05.510 10912303 10945058 93 2009-01-06 09:56:05.890 2010-01-05 08:36:19.543 8355883 28278813 8355883 2015-08-26 12:03:05.510 2015-08-26 12:03:05.510 28278814 8355883 2015-08-26 12:03:05.510 2015-08-26 12:03:05.510 19533447 19041368 2013-01-08 14:00:32.103 2013-01-08 14:00:32.103 17858699 17891452 5 2011-01-23 23:16:28.733 2011-03-21 09:32:18.007 15631042 28278815 8355883 2015-08-26 12:03:05.510 2015-08-26 12:03:05.510 19533446 19041368 2013-01-08 14:00:32.103 2013-01-08 14:00:32.103 28278825 8355883 2015-08-26 12:03:05.510 2015-08-26 12:03:05.510 28278824 8355883 2015-08-26 12:03:05.510 2015-08-26 12:03:05.510 28278827 8355883 2015-08-26 12:03:05.510 2015-08-26 12:03:05.510 28278826 8355883 2015-08-26 12:03:05.510 2015-08-26 12:03:05.510 28278821 8355883 2015-08-26 12:03:05.510 2015-08-26 12:03:05.510 11797062 11829815 100 2009-01-06 09:56:05.890 2010-04-01 11:38:30.423 8355883 28278820 8355883 2015-08-26 12:03:05.510 2015-08-26 12:03:05.510 28278823 8355883 2015-08-26 12:03:05.510 2015-08-26 12:03:05.510 28278822 8355883 2015-08-26 12:03:05.510 2015-08-26 12:03:05.510 10461295 3114599 2009-09-24 14:59:26.423 2009-09-24 14:59:26.423 28278833 8355883 2015-08-26 12:03:05.510 2015-08-26 12:03:05.510 10461294 3114599 2009-09-24 14:59:26.423 2009-09-24 14:59:26.423 28278832 8355883 2015-08-26 12:03:05.510 2015-08-26 12:03:05.510 10461293 3114599 2009-09-24 14:59:26.423 2009-09-24 14:59:26.423 28278835 8355883 2015-08-26 12:03:05.510 2015-08-26 12:03:05.510 28278834 8355883 2015-08-26 12:03:05.510 2015-08-26 12:03:05.510 28278829 8355883 2015-08-26 12:03:05.510 2015-08-26 12:03:05.510 10461299 3114599 2009-09-24 14:59:26.423 2009-09-24 14:59:26.423 17858718 17891470 1 2010-04-27 14:44:20.247 2010-04-27 14:44:20.247 11797064 28278828 8355883 2015-08-26 12:03:05.510 2015-08-26 12:03:05.510 10461298 3114599 2009-09-24 14:59:26.423 2009-09-24 14:59:26.423 28278831 8355883 2015-08-26 12:03:05.510 2015-08-26 12:03:05.510 10461297 3114599 2009-09-24 14:59:26.423 2009-09-24 14:59:26.423 28278830 8355883 2015-08-26 12:03:05.510 2015-08-26 12:03:05.510 10461296 3114599 2009-09-24 14:59:26.423 2009-09-24 14:59:26.423 28278975 8355883 2015-08-26 12:03:05.517 2015-08-26 12:03:05.517 28278974 8355883 2015-08-26 12:03:05.517 2015-08-26 12:03:05.517 28278973 8355883 2015-08-26 12:03:05.517 2015-08-26 12:03:05.517 28278972 8355883 2015-08-26 12:03:05.517 2015-08-26 12:03:05.517 28278979 8355883 2015-08-26 12:03:05.517 2015-08-26 12:03:05.517 28278978 8355883 2015-08-26 12:03:05.517 2015-08-26 12:03:05.517 28278977 8355883 2015-08-26 12:03:05.517 2015-08-26 12:03:05.517 28278976 8355883 2015-08-26 12:03:05.517 2015-08-26 12:03:05.517 10461305 3114599 2009-09-24 14:59:26.423 2009-09-24 14:59:26.423 28278967 8355883 2015-08-26 12:03:05.517 2015-08-26 12:03:05.517 10461304 3114599 2009-09-24 14:59:26.423 2009-09-24 14:59:26.423 28278966 8355883 2015-08-26 12:03:05.517 2015-08-26 12:03:05.517 28278965 8355883 2015-08-26 12:03:05.517 2015-08-26 12:03:05.517 10461306 3114599 2009-09-24 14:59:26.423 2009-09-24 14:59:26.423 28278964 8355883 2015-08-26 12:03:05.517 2015-08-26 12:03:05.517 10461301 3114599 2009-09-24 14:59:26.423 2009-09-24 14:59:26.423 28278971 8355883 2015-08-26 12:03:05.517 2015-08-26 12:03:05.517 10461300 3114599 2009-09-24 14:59:26.423 2009-09-24 14:59:26.423 28278970 8355883 2015-08-26 12:03:05.517 2015-08-26 12:03:05.517 10461303 3114599 2009-09-24 14:59:26.423 2009-09-24 14:59:26.423 28278969 8355883 2015-08-26 12:03:05.517 2015-08-26 12:03:05.517 10461302 3114599 2009-09-24 14:59:26.423 2009-09-24 14:59:26.423 28278968 8355883 2015-08-26 12:03:05.517 2015-08-26 12:03:05.517 28278990 8355883 2015-08-26 12:03:05.517 2015-08-26 12:03:05.517 28278991 8355883 2015-08-26 12:03:05.517 2015-08-26 12:03:05.517 5374433 5407169 24 2008-05-12 09:51:47.077 2008-06-19 15:09:09.907 3638030 27558219 27590983 79 2013-08-03 11:21:10.280 2015-08-05 13:19:52.467 21365729 28278988 8355883 2015-08-26 12:03:05.517 2015-08-26 12:03:05.517 5374432 5407168 24 2008-05-12 09:51:47.077 2008-06-19 15:09:09.907 3638030 28278989 8355883 2015-08-26 12:03:05.517 2015-08-26 12:03:05.517 5374431 5407167 24 2008-05-12 09:51:47.077 2008-06-19 15:09:09.907 3638030 28278994 8355883 2015-08-26 12:03:05.520 2015-08-26 12:03:05.520 3735591 3637534 2008-05-02 15:24:01.517 2008-05-02 15:24:01.517 1179179 1 28278995 8355883 2015-08-26 12:03:05.520 2015-08-26 12:03:05.520 28278992 8355883 2015-08-26 12:03:05.520 2015-08-26 12:03:05.520 28278993 8355883 2015-08-26 12:03:05.520 2015-08-26 12:03:05.520 28278982 8355883 2015-08-26 12:03:05.517 2015-08-26 12:03:05.517 28278983 8355883 2015-08-26 12:03:05.517 2015-08-26 12:03:05.517 28278980 8355883 2015-08-26 12:03:05.517 2015-08-26 12:03:05.517 28278981 8355883 2015-08-26 12:03:05.517 2015-08-26 12:03:05.517 27558229 27590992 80 2013-08-03 11:21:10.280 2015-08-06 12:47:21.933 21365729 3735582 3637556 2008-04-23 13:30:16.107 2008-04-23 13:30:16.107 3480935 1 28278986 8355883 2015-08-26 12:03:05.517 2015-08-26 12:03:05.517 3735583 3637556 2008-04-23 13:30:41.907 2008-04-23 13:30:41.907 2396959 1 28278987 8355883 2015-08-26 12:03:05.517 2015-08-26 12:03:05.517 3735584 3637556 2008-04-23 13:31:37.950 2008-04-23 13:31:37.950 7467922 1 28278984 8355883 2015-08-26 12:03:05.517 2015-08-26 12:03:05.517 3735585 3637556 2008-04-24 09:09:00.793 2008-04-24 09:09:00.793 19978 1 28278985 8355883 2015-08-26 12:03:05.517 2015-08-26 12:03:05.517 27558206 27590970 77 2013-08-03 11:21:10.280 2015-08-05 13:02:37.987 21365729 27558204 27590968 76 2013-08-03 11:21:10.280 2015-08-05 12:40:37.943 21365729 27138183 23167205 2015-04-15 09:51:32.653 2015-04-15 09:51:32.653 11239533 11272300 43 2009-10-08 12:07:56.397 2010-01-22 15:45:03.957 10356476 27138185 27066970 2015-04-15 09:54:12.197 2015-04-15 09:54:12.197 27138186 27066970 2015-04-15 09:54:12.197 2015-04-15 09:54:12.197 11239531 11272298 42 2009-10-08 12:07:56.397 2010-01-22 15:43:59.937 10356476 27558208 27590972 78 2013-08-03 11:21:10.280 2015-08-05 13:10:33.600 21365729 28278997 8355883 2015-08-26 12:03:05.520 2015-08-26 12:03:05.520 28278996 8355883 2015-08-26 12:03:05.520 2015-08-26 12:03:05.520 3735570 8355883 2008-04-22 08:37:50.737 2009-05-29 15:31:00.757 35840 1 11797114 11829864 2 2010-04-27 15:13:02.987 2010-04-27 15:15:08.180 11797066 3735566 3637286 2008-04-14 17:08:37.783 2008-04-14 17:08:37.783 4372022 1 3735564 3637286 2008-04-14 16:54:43.247 2008-04-14 16:54:43.247 36864 1 27558190 27590954 69 2013-08-03 11:21:10.280 2015-08-05 11:23:01.430 21365729 3735565 3637286 2008-04-14 16:57:31.460 2008-04-14 17:00:25.957 33148 1 3735562 3637286 2008-04-14 16:53:29.230 2008-04-14 16:53:29.230 43008 1 27558188 27590952 68 2013-08-03 11:21:10.280 2015-08-05 11:21:48.400 21365729 3735563 8355883 2008-04-14 16:53:56.180 2009-05-29 15:31:35.367 43520 1 4915278 4948041 14 2008-05-12 09:51:47.077 2008-06-02 13:01:04.423 3638030 3735560 3637286 2008-04-14 16:22:55.970 2008-04-14 16:22:55.970 19968 1 27558194 27590958 71 2013-08-03 11:21:10.280 2015-08-05 11:41:23.240 21365729 3735561 8355883 2008-04-14 16:23:27.157 2009-05-29 15:36:18.603 495616 1 3735558 3637286 2008-04-14 16:22:17.877 2008-04-14 16:22:17.877 125761 1 27558192 27590956 70 2013-08-03 11:21:10.280 2015-08-05 11:27:16.167 21365729 3735559 3637286 2008-04-14 16:22:35.127 2008-04-14 16:22:35.127 40448 1 3735556 3637286 2008-04-14 16:21:29.900 2008-04-14 16:21:29.900 50176 1 27558198 27590962 73 2013-08-03 11:21:10.280 2015-08-05 12:04:29.993 21365729 3735557 3637286 2008-04-14 16:21:50.890 2008-04-14 16:21:50.890 85504 1 14352389 1 13926566 2010-08-17 09:29:15.080 2010-08-17 09:29:15.080 27558196 27590960 72 2013-08-03 11:21:10.280 2015-08-05 12:03:23.817 21365729 3735555 3637286 2008-04-14 16:21:05.847 2008-04-14 16:21:05.847 263346 1 27558202 27590966 75 2013-08-03 11:21:10.280 2015-08-05 12:34:34.943 21365729 27558200 27590964 74 2013-08-03 11:21:10.280 2015-08-05 12:13:05.807 21365729 28278915 8355883 2015-08-26 12:03:05.513 2015-08-26 12:03:05.513 27558175 27590939 61 2013-08-03 11:21:10.280 2015-08-05 09:57:05.110 21365729 28278914 8355883 2015-08-26 12:03:05.513 2015-08-26 12:03:05.513 27558176 27590940 62 2013-08-03 11:21:10.280 2015-08-05 10:03:18.927 21365729 28278913 8355883 2015-08-26 12:03:05.513 2015-08-26 12:03:05.513 28278912 8355883 2015-08-26 12:03:05.513 2015-08-26 12:03:05.513 27558178 27590942 63 2013-08-03 11:21:10.280 2015-08-05 10:04:15.697 21365729 28278911 8355883 2015-08-26 12:03:05.513 2015-08-26 12:03:05.513 27558171 27590935 59 2013-08-03 11:21:10.280 2015-08-05 09:15:01.847 21365729 28278910 8355883 2015-08-26 12:03:05.513 2015-08-26 12:03:05.513 5374354 5407092 23 2008-05-12 09:51:47.077 2008-06-18 08:19:33.837 3638030 28278909 8355883 2015-08-26 12:03:05.513 2015-08-26 12:03:05.513 27558173 27590937 60 2013-08-03 11:21:10.280 2015-08-05 09:23:31.230 21365729 28278908 8355883 2015-08-26 12:03:05.513 2015-08-26 12:03:05.513 28278907 8355883 2015-08-26 12:03:05.513 2015-08-26 12:03:05.513 28278906 8355883 2015-08-26 12:03:05.513 2015-08-26 12:03:05.513 27558184 27590948 66 2013-08-03 11:21:10.280 2015-08-05 11:08:23.077 21365729 28278905 8355883 2015-08-26 12:03:05.513 2015-08-26 12:03:05.513 28278904 8355883 2015-08-26 12:03:05.513 2015-08-26 12:03:05.513 27558186 27590950 67 2013-08-03 11:21:10.280 2015-08-05 11:16:41.323 21365729 28278903 8355883 2015-08-26 12:03:05.513 2015-08-26 12:03:05.513 28278902 8355883 2015-08-26 12:03:05.513 2015-08-26 12:03:05.513 27558180 27590944 64 2013-08-03 11:21:10.280 2015-08-05 10:37:54.537 21365729 28278901 8355883 2015-08-26 12:03:05.513 2015-08-26 12:03:05.513 4849678 7 3114599 2008-06-03 13:08:15.110 2008-06-05 10:27:15.040 28278900 8355883 2015-08-26 12:03:05.513 2015-08-26 12:03:05.513 27558182 27590946 65 2013-08-03 11:21:10.280 2015-08-05 11:01:08.430 21365729 28278930 8355883 2015-08-26 12:03:05.517 2015-08-26 12:03:05.517 28278931 8355883 2015-08-26 12:03:05.517 2015-08-26 12:03:05.517 28278928 8355883 2015-08-26 12:03:05.517 2015-08-26 12:03:05.517 28278929 8355883 2015-08-26 12:03:05.517 2015-08-26 12:03:05.517 27558161 27590925 55 2013-08-03 11:21:10.280 2015-08-03 14:33:27.087 21365729 28278926 8355883 2015-08-26 12:03:05.517 2015-08-26 12:03:05.517 28278927 8355883 2015-08-26 12:03:05.517 2015-08-26 12:03:05.517 28278924 8355883 2015-08-26 12:03:05.517 2015-08-26 12:03:05.517 10454643 10354826 2009-06-01 10:05:31.443 2009-06-01 10:05:31.443 28278925 8355883 2015-08-26 12:03:05.517 2015-08-26 12:03:05.517 10454642 10354826 2009-06-01 10:05:31.443 2009-06-01 10:05:31.443 28278922 8355883 2015-08-26 12:03:05.517 2015-08-26 12:03:05.517 28278923 8355883 2015-08-26 12:03:05.517 2015-08-26 12:03:05.517 28278920 8355883 2015-08-26 12:03:05.517 2015-08-26 12:03:05.517 28278921 8355883 2015-08-26 12:03:05.517 2015-08-26 12:03:05.517 27558169 27590933 58 2013-08-03 11:21:10.280 2015-08-04 17:26:13.313 21365729 28278918 8355883 2015-08-26 12:03:05.513 2015-08-26 12:03:05.513 28278919 8355883 2015-08-26 12:03:05.517 2015-08-26 12:03:05.517 27558163 27590927 56 2013-08-03 11:21:10.280 2015-08-04 12:59:10.070 21365729 28278916 8355883 2015-08-26 12:03:05.513 2015-08-26 12:03:05.513 28278917 8355883 2015-08-26 12:03:05.513 2015-08-26 12:03:05.513 27558165 27590929 57 2013-08-03 11:21:10.280 2015-08-04 13:15:38.113 21365729 28278945 8355883 2015-08-26 12:03:05.517 2015-08-26 12:03:05.517 28278944 8355883 2015-08-26 12:03:05.517 2015-08-26 12:03:05.517 27558146 27590911 54 2013-08-03 11:21:10.280 2015-08-03 12:25:43.660 21365729 28278947 8355883 2015-08-26 12:03:05.517 2015-08-26 12:03:05.517 28278946 8355883 2015-08-26 12:03:05.517 2015-08-26 12:03:05.517 27558144 27590909 53 2013-08-03 11:21:10.280 2015-08-03 12:19:32.767 21365729 28278941 8355883 2015-08-26 12:03:05.517 2015-08-26 12:03:05.517 28278940 8355883 2015-08-26 12:03:05.517 2015-08-26 12:03:05.517 27558142 27590907 52 2013-08-03 11:21:10.280 2015-08-03 11:49:18.560 21365729 28278943 8355883 2015-08-26 12:03:05.517 2015-08-26 12:03:05.517 28278942 8355883 2015-08-26 12:03:05.517 2015-08-26 12:03:05.517 27558140 27590905 51 2013-08-03 11:21:10.280 2015-08-03 11:39:41.823 21365729 28278937 8355883 2015-08-26 12:03:05.517 2015-08-26 12:03:05.517 28278936 8355883 2015-08-26 12:03:05.517 2015-08-26 12:03:05.517 28278939 8355883 2015-08-26 12:03:05.517 2015-08-26 12:03:05.517 11239604 11272369 94 2009-01-06 09:56:05.890 2010-01-05 08:37:11.277 8355883 28278938 8355883 2015-08-26 12:03:05.517 2015-08-26 12:03:05.517 28278933 8355883 2015-08-26 12:03:05.517 2015-08-26 12:03:05.517 11239610 11272375 2 2010-01-29 15:27:06.493 2010-01-29 17:46:52.150 11239606 28278932 8355883 2015-08-26 12:03:05.517 2015-08-26 12:03:05.517 28278935 8355883 2015-08-26 12:03:05.517 2015-08-26 12:03:05.517 11239608 11272373 1 2010-01-29 15:27:06.493 2010-01-29 15:27:06.493 11239606 28278934 8355883 2015-08-26 12:03:05.517 2015-08-26 12:03:05.517 28278960 8355883 2015-08-26 12:03:05.517 2015-08-26 12:03:05.517 27558130 27590895 49 2013-08-03 11:21:10.280 2015-08-01 10:09:25.653 21365729 28278961 8355883 2015-08-26 12:03:05.517 2015-08-26 12:03:05.517 27558129 27590894 48 2013-08-03 11:21:10.280 2015-08-01 09:55:20.093 21365729 11239614 11272379 4 2010-01-29 15:27:06.493 2010-01-29 18:03:57.840 11239606 28278962 8355883 2015-08-26 12:03:05.517 2015-08-26 12:03:05.517 28278963 8355883 2015-08-26 12:03:05.517 2015-08-26 12:03:05.517 27558127 27590892 47 2013-08-03 11:21:10.280 2015-08-01 09:41:16.120 21365729 11239612 11272377 3 2010-01-29 15:27:06.493 2010-01-29 18:00:34.820 11239606 28278956 8355883 2015-08-26 12:03:05.517 2015-08-26 12:03:05.517 11239617 11272382 6 2010-01-29 15:27:06.493 2010-01-29 18:15:42.887 11239606 28278957 8355883 2015-08-26 12:03:05.517 2015-08-26 12:03:05.517 25395489 25428257 3 2013-08-03 11:21:10.280 2014-03-20 11:50:31.907 21365729 27558125 27590890 46 2013-08-03 11:21:10.280 2015-08-01 09:39:26.290 21365729 28278958 8355883 2015-08-26 12:03:05.517 2015-08-26 12:03:05.517 11239615 11272380 5 2010-01-29 15:27:06.493 2010-01-29 18:13:59.163 11239606 28278959 8355883 2015-08-26 12:03:05.517 2015-08-26 12:03:05.517 25395487 25428255 2 2013-08-03 11:21:10.280 2014-02-12 12:38:17.170 21365729 27558123 27590888 45 2013-08-03 11:21:10.280 2015-08-01 09:36:29.783 21365729 28278952 8355883 2015-08-26 12:03:05.517 2015-08-26 12:03:05.517 27558138 27590903 50 2013-08-03 11:21:10.280 2015-08-01 10:15:29.797 21365729 28278953 8355883 2015-08-26 12:03:05.517 2015-08-26 12:03:05.517 28278954 8355883 2015-08-26 12:03:05.517 2015-08-26 12:03:05.517 28278955 8355883 2015-08-26 12:03:05.517 2015-08-26 12:03:05.517 28278948 8355883 2015-08-26 12:03:05.517 2015-08-26 12:03:05.517 28278949 8355883 2015-08-26 12:03:05.517 2015-08-26 12:03:05.517 28278950 8355883 2015-08-26 12:03:05.517 2015-08-26 12:03:05.517 28278951 8355883 2015-08-26 12:03:05.517 2015-08-26 12:03:05.517 18284700 18251936 18284699 18251935 18284698 18251934 9831380 9798640 9831381 Backup Database... ## Select Database-complete ## Click on Add... under Destination ## I typed in a file location of \\tempest\tempbox\kgomes\backups\crowd\db_backup as the file to backup to. ## I then created a new tar.gz file for the /opt/atlassian-crowd-1.5.1 installation and put in the same backup location on tempest. ## I then created a new tar.gz file for the crowd home directory /data/crowd and put in same tempest location # I copied the jtds-1.2.jar from /opt/atlassian-crowd-1.5.1/crowd-webapp/WEB-INF/lib to the same directory in the new installation # I then edited the /opt/atlassian-crowd-1.6/crowd-webapp/WEB-INF/classes/crowd-init.properties and pointed the crowd home directory to /data/crowd # I then copied the updated crowd client jar (/opt/atlassian-crowd-1.6/client/crowd-integrations-client-1.6.jar) to /opt/confluence/confluence/WEB-INF/lib and to /opt/jira/atlassian-jira/WEB-INF/lib (I removed the old ones too IMPORTANT!) # I downloaded the recommended crowd-ehcache.xml file from the instructions listed above and copied to the /opt/confluence/confluence/WEB-INF/classes and /opt/jira/atlassian-jira/WEB-INF/classes directories # Lastly I changed the /opt/crowd symbolic link to point to the new crowd installation, shut down confluence, jira, and crowd and restarted crowd. # After the successful start up of the three applications, I put all the backup files in Alfresco [here|https://alfresco.mbari.org/alfresco/webdav/Engineering/Tools/Collaboration%20Tools/Atlassian%20Crowd/Backups/2008_12_29]]]> 9798641 9831384 9798644 2195867 "Downloads">"2.1 Releases">"2.1.1" # I then clicked on alfresco-enterprise-tomcat-2.1.1.zip to download the zip file. # Went to [http://customers.alfresco.com] (I was still logged in) # Went to "Company Home">"Downloads">"2.1 Releases">"2.1.1">"License Files" # I went ahead and downloaded all the "*.lic" files, but I think I only need enterprise-network-customer-unlimited.lic" # Logged out of Alfresco. # Since I suspect I will need a JDBC driver for SQLServer, I downloaded the jTDS-1.2.2 driver from the jtds web site (just Google jtds and go to the download section of the top google return). # I closed the Firefox browser. # I extracted the jtds-1.2.2.jar file from the jtds download # I downloaded and installed the JRockit 6 R27.4 JDK Microsoft Windows (x86 - 32 bit) from BEA's web site {note} After installing JRockit, make sure you set the JAVA_HOME environment variable to point to the installation of JRockit. For example, I went to the desktop, right clicked on the computer, did Properties, then clicked on the Advanced tab, then click on the environment variables button and then created a new system variable named JAVA_HOME and set to c:\bin\Java\jrockit-R27.4.0-jdk1.6.0_02 {note} # I ran the installer, changed the "Program Files" to "bin" in the installation directory for both the JDK and the JRE. I also chose to install the JRE as public. # Using Firefox, I downloaded the PHP 5.2.5 Windows Installer from php.net and installed it. Although I installed it, I did not integrate it with a web server as I want Alfresco to take port 80. I probably did not need to install PHP, but I thought I would anyway. (again, I changed install path from "Program Files" to "bin" # I also downloaded and installed OpenOffice and ran it once so I could get through the initial startup # I setup a Alfresco database on the server Solstice and granted the LAGOON\DB_Collaboration account to be the db_owner of the Alfresco database. # I unzipped the alfresco tomcat zip file to an alfresco directory in c:\bin # I then went to the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions directory for the customization of the server. ## I edited the custom-repository.properties file ### Changed the dir.root and dir.indexes to look like: {noformat} dir.root=//tornado.shore.mbari.org/Alfresco/alf_data dir.indexes=d:/alf_data/lucene-indexes {noformat} ### Commented out the db.* lines for the HSQL Connection (db.driver and db.url) ### Uncommented the db.* lines for MSSQL and changed to use the jTDS driver. They should look like: {noformat} db.driver=net.sourceforge.jtds.jdbc.Driver db.url=jdbc:jtds:sqlserver://solstice.shore.mbari.org/Alfresco;domain=SHORE;user=DB_Collaboration;password=XXXXXXXXX {noformat} ### I also added the following section to override the mail server settings {noformat} # Mail server configuration mail.host=mail.mbari.org mail.port=25 mail.username= mail.password= {noformat} ## Edited the custom-hibernate-dialect.properties file ### Commented out the HSQL Dialect ### Uncommented the MSSQL Dialect # I then installed the jtds-1.2.2.jar in the c:\bin\alfresco\tomcat\common\lib so that it will be on the classpath when Alfresco is started # Now this is not necessarily fun, but in order to really get it configured the way we want it, you need to pull the original .war file out, edit some stuff inside and re-create the .war. {note} This should all be done before starting Alfresco for the first time. {note} # Copy the c:\Alfresco\tomcat\webapps\alfresco.war file to your home directory. # Make a second copy so that you will always the original (I copied to alfresco.war.orig and moved it somewhere else. It is important to move it and have only the alfresco.war file in the directory because when you un-jar it, all the files go right where alfresco.war is.) # From a command line, un-jar the war file using: {noformat} jar -xvf alfresco.war {noformat} # This unpacks a lot of files and after it completes, move (or delete) the alfresco.war file from the directory. This needs to be done so it does not end up in the new .war file. # I wanted to change the "Company Home" that seems to be everywhere to something that says MBARI. ## Edited ./WEB-INF/classes/alfresco/messages/webclient.properties and changed company_home from 'Company Home' to 'MBARI' ## Edited ./WEB-INF/classes/alfresco/messages/webclient_en_US.properties and changed company_home from 'Company Home' to 'MBARI' ## I edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces.properties and changed the first two lines to read {noformat} spaces.company_home.name=MBARI spaces.company_home.description=The root space for MBARI {noformat} ## Edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces_en_US.properties and made the same changes as the previous step {tip} This took a bit to find all these, and to be honest, I am not sure which one actually made the change on the GUI, but I suspect it was the _en_US ones. {tip} # When users are imported via LDAP, user spaces get created automatically. In order to put them where I wanted them to go (instead of right in the Company Home), I edited the ./WEB-INF/classes/alfresco/authentication-services-context.xml file. In the file there is a bean with an name of personalHomeFolderProvider. There is a property name 'path' and I added {noformat} /${spaces.user_homes.childname} {noformat} to the end to try to get them to create the user spaces there instead of in the Company Home. The final bean XML looks like: {noformat} /${spaces.company_home.childname}/${spaces.user_homes.childname} ${spaces.store} false All All {noformat} # I wanted to change the logo that is used. I attached the replacement logo [here|^AlfrescoLogo32.png]. Copy this to ./images/logo and overwrite the one that is there. # In order to setup SSL for the application (will do that later), edit ./WEB-INF/web.xml and add the following {noformat} Login Pages /* CONFIDENTIAL {noformat} right before the ending tag at the bottom of the file. # Now in order to change the default behavior so that all content is versioned from the start, I edited the .\WEB-INF\classes\alfresco\model\contentModel.xml and searched for the content type definition block. {noformat} Content cm:cmobject true d:content false true false true {noformat} and added the following block right before the ending tag: {noformat} cm:versionable {noformat} so the final block looks like: {noformat} Content cm:cmobject true d:content false true false true cm:versionable {noformat} # That takes care of all the changes to the WAR file. We can now put it back into .war form. # While you are in the directory you expanded the war file in, run ## jar cvfm alfresco.war META-INF\MANIFEST.MF . # You should now have an alfresco.war file in the directory. Move that back to the alfresco install and overwrite the existing one. # Most users like the details view, so I set the default to that by editing c:\Alfresco\tomcat\shared\classes\alfresco\extensions/web-client-config-custom.xml and added: {noformat} details 20
20
20 {noformat} right before the closing tag. # Now in order to use MBARI accounts, I needed to configure LDAP. # I downloade this [ldap-authentication-context.xml|^ldap-authentication-context.xml] file and put it in the c:\Alfresco\tomcat\shared\classes\alfresco\extensions folder. # We wanted to be able to make sure we could have collaborator accounts that were not MBARI LDAP accounts so that we could have Alfresco users that had not permissions at all on the MBARI network. In order to do this, I used the Alfresco native user service and chained the authentication together with the MBARI LDAP. In order to do this, I downloaded this [chaining-authentication-context.xml|^chaining-authentication-context.xml] file and installed in c:\Alfresco\tomcat\shared\classes\alfresco\extensions. # In order to grant certain accounts admin privs, I created a new custom-authority-services-context.xml in the same directory as the ldap-authentication-context.xml file and added {noformat} kgomes admin administrator {noformat} # In order for Alfresco to handle all port 80 traffic, I changed Tomcat so that it takes port 80 and SSL goes over port 443. So I edited the c:\Alfresco\tomcat\conf\server.xml file and changed the 8080 port to 80 and the 8443 port to 443 (the 443 change is done in two places). # I copied the enterprise-network-unlimited.lic file into the c:\Alfresco\tomcat\shared\classes\alfresco\extensions\license directory # Just to keep things clean, I edited the c:\bin\alfresco\alfresco.bat file and put 'rem' in front of the second JAVA_OPTS set as I am using Java 6. # Now after you run it for the first time and the database structure gets created, you can't restart it because you get: {noformat} java.sql.SQLException: Column names in each table must be unique. Column name 'ID_' in table 'JBPM_ACTION' is specified more than once. {noformat} Sigh, so in order to keep Alfresco from hurting itself, I had to turn off the schema updates. This is done by editing the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions\custom-repository.properties and adding the following: {noformat} db.schema.update=false {noformat} and then restarting alfresco. # To install Alfresco as a Windows Service use a command prompt and enter the following: {noformat} cd c:\bin\alfresco\tomcat\bin service.bat install alfresco tomcat5.exe //US//alfresco --DisplayName "Alfresco Server" tomcat5.exe //US//alfresco --JvmMs=512 --JvmMx=1024 --JvmSs=64 tomcat5.exe //US//alfresco --JavaHome=c:/bin/Java/jrockit-R27.4.0-jdk1.6.0_02 tomcat5.exe //US//alfresco --Environment ALF_HOME=c:/bin/alfresco/ tomcat5.exe //US//alfresco --Environment PATH=c:/bin/alfresco/bin;%PATH% tomcat5.exe //US//alfresco --StartPath c:/bin/alfresco --Startup auto {noformat} # To uninstall the service, at a later time, do the following: {noformat} cd c:\bin\alfresco\tomcat\bin service.bat uninstall alfresco {noformat} # To edit your service settings at any time: {noformat} cd c:\alfresco\tomcat\bin tomcat5w.exe //ES//alfresco {noformat} # In order to install certain modules (like the email listener), I had to get the Alfresco Module Manager from the customers.alfresco.com download site. I downloaded the alfresco-mmt-2.1.1.jar file locally so I could use it to install modules. # I then downloaded the email listener module from [http://forge.alfresco.com/projects/email-listener/]. It came as a zip file, so I unzipped it and it created a folder with the appropriate emailListener.amp in it. # Make another backup copy of the alfresco.war file and put somewhere in case you want to roll this back. # Open a command prompt windows and cd to the location where the Alfresco Module Manager jar is. # Run the following: {noformat} java -jar alfresco-mmt-2.1.1.jar path_to_emailListener.amp path_to_alfresco.war {noformat} So for me this looked like: {noformat} java -jar alfresco-mmt-2.1.1.jar .\email-listener_2.1RC2\emailListener.amp c:\bin\alfresco\tomcat\webapps\alfresco.war {noformat} # You should be able to verify the install by running: {noformat} java -jar alfresco-mmt-2.1.1.jar list c:\bin\alfresco\tomcat\webapps\alfresco.war {noformat} and you should see something like: {noformat} Module 'emailListener' installed in 'c:\bin\alfresco\tomcat\webapps\alfresco.war' - Title: EmailListener - Version: 2.1 - Install Date: Fri Dec 07 08:43:10 PST 2007 - Desription: EmailListener Module {noformat} # To configure the security for this installation of Alfresco, it was a multi-step process. ## The first step was to enable LDAP as the mechanism used for authentication. To do this I: ### Edited the c:\bin\alfresco\tomcat\shared\classes\alfresco\extension\ldap-authentication.properties to make it look like: {noformat} # # This properties file brings together the common options for LDAP authentication rather than editing the bean definitions # # How to map the user id entered by the user to taht passed through to LDAP # - simple # - this must be a DN and would be something like # CN=%s,DC=company,DC=com # - digest # - usually pass through what is entered # %s ldap.authentication.userNameFormat=%s@shore.mbari.org # The LDAP context factory to use ldap.authentication.java.naming.factory.initial=com.sun.jndi.ldap.LdapCtxFactory # The URL to connect to the LDAP server ldap.authentication.java.naming.provider.url=ldap://ldap.shore.mbari.org:389 # The authentication mechanism to use ldap.authentication.java.naming.security.authentication=simple # The default principal to use (only used for LDAP sync) ldap.authentication.java.naming.security.principal=LDAPbind@shore.mbari.org # The password for the default principal (only used for LDAP sync) ldap.authentication.java.naming.security.credentials=XXXXXX {noformat} You will need to actually put in the password for the account that has read privs on the LDAP service. ### I then renamed the file c:\bin\alfresco\tomcat\shared\classes\alfresco\extension\ldap-authentication.xml.sample to c:\bin\alfresco\tomcat\shared\classes\alfresco\extension\ldap-authentication.xml and restarted Alfresco # Finally, to start the service, just go into your Windows Service control panel and locate the service that is now named 'Alfresco Server'. You can start and stop Alfresco from this control panel. ]]> 2163104 9831414 9798675 9831412 9798673 9831417 9798678 9831418 9798679 9831421 9798682 9831425 9798686 9831424 9798685 9831401 9798662 9831400 9798661 9831399 9798660 9831406 9798667 9831404 9798665 9831410 9798671 9831408 9798669 2195784 "Downloads">"2.1 Releases">"2.1.1" * I then clicked on AlfrescoEnterprise-2.1.1-Setup.exe to download the installation executable. I also downloaded AlfrescoWCMEnterprise-2.1.1-Setup.exe in case I needed it later. * Went to [http://customers.alfresco.com] (I was still logged in) * Went to "Company Home">"Downloads">"2.1 Releases">"2.1.1">"License Files" * I went ahead and downloaded all the "*.lic" files, but I think I only need enterprise-network-customer-unlimited.lic" * Logged out of Alfresco. * Since I suspect I will need a JDBC driver for SQLServer, I downloaded the jTDS-1.2.2 driver from the jtds web site (just Google jtds and go to the download section of the top google return). * I closed the Firefox browser. * I extracted the jtds-1.2.2.jar file from the jtds download * I downloaded and installed the JRockit 6 R27.4 JDK Microsoft Windows (x86 - 32 bit) from BEA's web site * I ran the installer, changed the "Program Files" to "bin" in the installation directory for both the JDK and the JRE. I also chose to install the JRE as public. * Using Firefox, I downloaded the PHP 5.2.5 Windows Installer from php.net and installed it. Although I installed it, I did not integrate it with a web server as I want Alfresco to take port 80. I probably did not need to install PHP, but I thought I would anyway. (again, I changed install path from "Program Files" to "bin" * I setup a Alfresco database on the server Solstice and granted the LAGOON\DB_Collaboration account to be the db_owner of the Alfresco database. * I then executed the .exe on the alfresco server to install Alfresco * I left the installation directory as c:\Alfresco * It did not find the JDK I installed so it asked to download and install one, but I said no. * I did select the option to download and install the OpenOffice.org component. * After the installation was complete, I left the check box for "Run Configuration Wizard" checked to see if the configuration wizard was worth much. * The Wizard: ** I chose the MS SQL Database Type ** For the content location, I input "\\tornado.shore.mbari.org\alfresco\alf_data". ** For the indicies, I input "c:\alfresco\alf_data\lucene-indexes" ** I left the OpenOffice install location as "C:\Alfresco\openoffice" ** Thus completes the Wizard. * To make sure the Wizard was wise, I looked at all the configuration files that were in c:\Alfresco\tomcat\shared\classes\alfresco\extensions because this is where all the customization for a particular installation goes. * In the custom-hibernate-dialect.properties file, everything looked fine. * In the custom-repository.properties, it was not. ** The database URL was :jdbc:jtds:sqlserver://localhost/alfresco but this is not correct, we want to point it to Solstice so I changed it to: {noformat} db.url=jdbc:jtds:sqlserver://solstice.shore.mbari.org/Alfresco;domain=SHORE;user=DB_Collaboration;password=XXXXX {noformat} ** I then installed the jtds-1.2.2.jar in the c:\alfresco\tomcat\common\lib so that it will be on the classpath when Alfresco is started ** I also added the following section to override the mail server settings {noformat} # Mail server configuration mail.host=mail.mbari.org mail.port=25 mail.username= mail.password= {noformat} ]]> 2163020 9831196 9798445 2195786 "Downloads">"2.1 Releases">"2.1.1" # I then clicked on AlfrescoEnterprise-2.1.1-Setup.exe to download the installation executable. I also downloaded AlfrescoWCMEnterprise-2.1.1-Setup.exe in case I needed it later. # Went to [http://customers.alfresco.com] (I was still logged in) # Went to "Company Home">"Downloads">"2.1 Releases">"2.1.1">"License Files" # I went ahead and downloaded all the "*.lic" files, but I think I only need enterprise-network-customer-unlimited.lic" # Logged out of Alfresco. # Since I suspect I will need a JDBC driver for SQLServer, I downloaded the jTDS-1.2.2 driver from the jtds web site (just Google jtds and go to the download section of the top google return). # I closed the Firefox browser. # I extracted the jtds-1.2.2.jar file from the jtds download # I downloaded and installed the JRockit 6 R27.4 JDK Microsoft Windows (x86 - 32 bit) from BEA's web site # I ran the installer, changed the "Program Files" to "bin" in the installation directory for both the JDK and the JRE. I also chose to install the JRE as public. # Using Firefox, I downloaded the PHP 5.2.5 Windows Installer from php.net and installed it. Although I installed it, I did not integrate it with a web server as I want Alfresco to take port 80. I probably did not need to install PHP, but I thought I would anyway. (again, I changed install path from "Program Files" to "bin" # I setup a Alfresco database on the server Solstice and granted the LAGOON\DB_Collaboration account to be the db_owner of the Alfresco database. # I then executed the .exe on the alfresco server to install Alfresco # I left the installation directory as c:\Alfresco # It did not find the JDK I installed so it asked to download and install one, but I said no. # I did select the option to download and install the OpenOffice.org component. # After the installation was complete, I left the check box for "Run Configuration Wizard" checked to see if the configuration wizard was worth much. # The Wizard: ## I chose the MS SQL Database Type ## For the content location, I input "\\tornado.shore.mbari.org\alfresco\alf_data". ## For the indicies, I input "c:\alfresco\alf_data\lucene-indexes" ## I left the OpenOffice install location as "C:\Alfresco\openoffice" ## Thus completes the Wizard. # To make sure the Wizard was wise, I looked at all the configuration files that were in c:\Alfresco\tomcat\shared\classes\alfresco\extensions because this is where all the customization for a particular installation goes. # In the custom-hibernate-dialect.properties file, everything looked fine. # In the custom-repository.properties, it was not. ## The database URL was :jdbc:jtds:sqlserver://localhost/alfresco but this is not correct, we want to point it to Solstice so I changed it to: {noformat} db.url=jdbc:jtds:sqlserver://solstice.shore.mbari.org/Alfresco;domain=SHORE;user=DB_Collaboration;password=XXXXX {noformat} ## I then installed the jtds-1.2.2.jar in the c:\alfresco\tomcat\common\lib so that it will be on the classpath when Alfresco is started ## I also added the following section to override the mail server settings {noformat} # Mail server configuration mail.host=mail.mbari.org mail.port=25 mail.username= mail.password= {noformat} # Now this is not necessarily fun, but in order to really get it configured the way we want it, you need to pull the original .war file out, edit some stuff inside and re-create the .war. {note} This should all be done before starting Alfresco for the first time. {note} # Copy the c:\Alfresco\tomcat\webapps\alfresco.war file to your home directory. # Make a second copy so that you will always the original (I copied to alfresco.war.orig and moved it somewhere else. It is important to move it and have only the alfresco.war file in the directory because when you un-jar it, all the files go right where alfresco.war is.) # From a command line, un-jar the war file using: {noformat} jar -xvf alfresco.war {noformat} # This unpacks a lot of files and after it completes, move (or delete) the alfresco.war file from the directory. This needs to be done so it does not end up in the new .war file. # I wanted to change the "Company Home" that seems to be everywhere to something that says MBARI. ## Edited ./WEB-INF/classes/alfresco/messages/webclient.properties and changed company_home from 'Company Home' to 'MBARI' ## Edited ./WEB-INF/classes/alfresco/messages/webclient_en_US.properties and changed company_home from 'Company Home' to 'MBARI' ## I edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces.properties and changed the first two lines to read {noformat} spaces.company_home.name=MBARI spaces.company_home.description=The root space for MBARI {noformat} ## Edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces_en_US.properties and made the same changes as the previous step {tip} This took a bit to find all these, and to be honest, I am not sure which one actually made the change on the GUI, but I suspect it was the _en_US ones. {tip} # When users are imported via LDAP, user spaces get created automatically. In order to put them where I wanted them to go (instead of right in the Company Home), I edited the ./WEB-INF/classes/alfresco/authentication-services-context.xml file. In the file there is a bean with an name of personalHomeFolderProvider. There is a property name 'path' and I added {noformat} /${spaces.user_homes.childname} {noformat} to the end to try to get them to create the user spaces there instead of in the Company Home. The final bean XML looks like: {noformat} /${spaces.company_home.childname}/${spaces.user_homes.childname} ${spaces.store} false All All {noformat} # I wanted to change the logo that is used. I attached the replacement logo [here|^AlfrescoLogo32.png]. Copy this to ./images/logo and overwrite the one that is there. # In order to setup SSL for the application (will do that later), edit ./WEB-INF/web.xml and add the following {noformat} Login Pages /* CONFIDENTIAL {noformat} right before the ending tag at the bottom of the file. # Now in order to change the default behavior so that all content is versioned from the start, I edited the .\WEB-INF\classes\alfresco\model\contentModel.xml and searched for the content type definition block. {noformat} Content cm:cmobject true d:content false true false true {noformat} and added the following block right before the ending tag: {noformat} cm:versionable {noformat} so the final block looks like: {noformat} Content cm:cmobject true d:content false true false true cm:versionable {noformat} # That takes care of all the changes to the WAR file. We can now put it back into .war form. # While you are in the directory you expanded the war file in, run ## jar cvfm alfresco.war META-INF\MANIFEST.MF . # You should now have an alfresco.war file in the directory. Move that back to the alfresco install and overwrite the existing one. # Most users like the details view, so I set the default to that by editing c:\Alfresco\tomcat\shared\classes\alfresco\extensions/web-client-config-custom.xml and added: {noformat} details 20
20
20 {noformat} right before the closing tag. ]]> 2163022 2195785 "Downloads">"2.1 Releases">"2.1.1" # I then clicked on AlfrescoEnterprise-2.1.1-Setup.exe to download the installation executable. I also downloaded AlfrescoWCMEnterprise-2.1.1-Setup.exe in case I needed it later. # Went to [http://customers.alfresco.com] (I was still logged in) # Went to "Company Home">"Downloads">"2.1 Releases">"2.1.1">"License Files" # I went ahead and downloaded all the "*.lic" files, but I think I only need enterprise-network-customer-unlimited.lic" # Logged out of Alfresco. # Since I suspect I will need a JDBC driver for SQLServer, I downloaded the jTDS-1.2.2 driver from the jtds web site (just Google jtds and go to the download section of the top google return). # I closed the Firefox browser. # I extracted the jtds-1.2.2.jar file from the jtds download # I downloaded and installed the JRockit 6 R27.4 JDK Microsoft Windows (x86 - 32 bit) from BEA's web site # I ran the installer, changed the "Program Files" to "bin" in the installation directory for both the JDK and the JRE. I also chose to install the JRE as public. # Using Firefox, I downloaded the PHP 5.2.5 Windows Installer from php.net and installed it. Although I installed it, I did not integrate it with a web server as I want Alfresco to take port 80. I probably did not need to install PHP, but I thought I would anyway. (again, I changed install path from "Program Files" to "bin" # I setup a Alfresco database on the server Solstice and granted the LAGOON\DB_Collaboration account to be the db_owner of the Alfresco database. # I then executed the .exe on the alfresco server to install Alfresco # I left the installation directory as c:\Alfresco # It did not find the JDK I installed so it asked to download and install one, but I said no. # I did select the option to download and install the OpenOffice.org component. # After the installation was complete, I left the check box for "Run Configuration Wizard" checked to see if the configuration wizard was worth much. # The Wizard: ## I chose the MS SQL Database Type ## For the content location, I input "\\tornado.shore.mbari.org\alfresco\alf_data". ## For the indicies, I input "c:\alfresco\alf_data\lucene-indexes" ## I left the OpenOffice install location as "C:\Alfresco\openoffice" ## Thus completes the Wizard. # To make sure the Wizard was wise, I looked at all the configuration files that were in c:\Alfresco\tomcat\shared\classes\alfresco\extensions because this is where all the customization for a particular installation goes. # In the custom-hibernate-dialect.properties file, everything looked fine. # In the custom-repository.properties, it was not. ## The database URL was :jdbc:jtds:sqlserver://localhost/alfresco but this is not correct, we want to point it to Solstice so I changed it to: {noformat} db.url=jdbc:jtds:sqlserver://solstice.shore.mbari.org/Alfresco;domain=SHORE;user=DB_Collaboration;password=XXXXX {noformat} ## I then installed the jtds-1.2.2.jar in the c:\alfresco\tomcat\common\lib so that it will be on the classpath when Alfresco is started ## I also added the following section to override the mail server settings {noformat} # Mail server configuration mail.host=mail.mbari.org mail.port=25 mail.username= mail.password= {noformat} # Now this is not necessarily fun, but in order to really get it configured the way we want it, you need to pull the original .war file out, edit some stuff inside and re-create the .war. {note} This should all be done before starting Alfresco for the first time. {note} # Copy the c:\Alfresco\tomcat\webapps\alfresco.war file to your home directory. # Make a second copy so that you will always the original (I copied to alfresco.war.orig and moved it somewhere else. It is important to move it and have only the alfresco.war file in the directory because when you un-jar it, all the files go right where alfresco.war is.) # From a command line, un-jar the war file using: {noformat} jar -xvf alfresco.war {noformat} # This unpacks a lot of files and after it completes, move (or delete) the alfresco.war file from the directory. This needs to be done so it does not end up in the new .war file. # I wanted to change the "Company Home" that seems to be everywhere to something that says MBARI. ## Edited ./WEB-INF/classes/alfresco/messages/webclient.properties and changed company_home from 'Company Home' to 'MBARI' ## Edited ./WEB-INF/classes/alfresco/messages/webclient_en_US.properties and changed company_home from 'Company Home' to 'MBARI' ## I edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces.properties and changed the first two lines to read {noformat} spaces.company_home.name=MBARI spaces.company_home.description=The root space for MBARI {noformat} ## Edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces_en_US.properties and made the same changes as the previous step {tip} This took a bit to find all these, and to be honest, I am not sure which one actually made the change on the GUI, but I suspect it was the _en_US ones. {tip} # When users are imported via LDAP, user spaces get created automatically. In order to put them where I wanted them to go (instead of right in the Company Home), I edited the ./WEB-INF/classes/alfresco/authentication-services-context.xml file. In the file there is a bean with an name of personalHomeFolderProvider. There is a property name 'path' and I added {noformat} /${spaces.user_homes.childname} {noformat} to the end to try to get them to create the user spaces there instead of in the Company Home. The final bean XML looks like: {noformat} /${spaces.company_home.childname}/${spaces.user_homes.childname} ${spaces.store} false All All {noformat} # I wanted to change the logo that is used. I attached the replacement logo [here|^AlfrescoLogo32.png]. Copy this to ./images/logo and overwrite the one that is there. # In order to setup SSL for the application (will do that later), edit ./WEB-INF/web.xml and add the following {noformat} Login Pages /* CONFIDENTIAL {noformat} ]]> 2163021 2195788 "Downloads">"2.1 Releases">"2.1.1" # I then clicked on AlfrescoEnterprise-2.1.1-Setup.exe to download the installation executable. I also downloaded AlfrescoWCMEnterprise-2.1.1-Setup.exe in case I needed it later. # Went to [http://customers.alfresco.com] (I was still logged in) # Went to "Company Home">"Downloads">"2.1 Releases">"2.1.1">"License Files" # I went ahead and downloaded all the "*.lic" files, but I think I only need enterprise-network-customer-unlimited.lic" # Logged out of Alfresco. # Since I suspect I will need a JDBC driver for SQLServer, I downloaded the jTDS-1.2.2 driver from the jtds web site (just Google jtds and go to the download section of the top google return). # I closed the Firefox browser. # I extracted the jtds-1.2.2.jar file from the jtds download # I downloaded and installed the JRockit 6 R27.4 JDK Microsoft Windows (x86 - 32 bit) from BEA's web site # I ran the installer, changed the "Program Files" to "bin" in the installation directory for both the JDK and the JRE. I also chose to install the JRE as public. # Using Firefox, I downloaded the PHP 5.2.5 Windows Installer from php.net and installed it. Although I installed it, I did not integrate it with a web server as I want Alfresco to take port 80. I probably did not need to install PHP, but I thought I would anyway. (again, I changed install path from "Program Files" to "bin" # I setup a Alfresco database on the server Solstice and granted the LAGOON\DB_Collaboration account to be the db_owner of the Alfresco database. # I then executed the .exe on the alfresco server to install Alfresco # I left the installation directory as c:\Alfresco # It did not find the JDK I installed so it asked to download and install one, but I said no. # I did select the option to download and install the OpenOffice.org component. # After the installation was complete, I left the check box for "Run Configuration Wizard" checked to see if the configuration wizard was worth much. # The Wizard: ## I chose the MS SQL Database Type ## For the content location, I input "\\tornado.shore.mbari.org\alfresco\alf_data". ## For the indicies, I input "c:\alfresco\alf_data\lucene-indexes" ## I left the OpenOffice install location as "C:\Alfresco\openoffice" ## Thus completes the Wizard. # To make sure the Wizard was wise, I looked at all the configuration files that were in c:\Alfresco\tomcat\shared\classes\alfresco\extensions because this is where all the customization for a particular installation goes. # In the custom-hibernate-dialect.properties file, everything looked fine. # In the custom-repository.properties, it was not. ## The database URL was :jdbc:jtds:sqlserver://localhost/alfresco but this is not correct, we want to point it to Solstice so I changed it to: {noformat} db.url=jdbc:jtds:sqlserver://solstice.shore.mbari.org/Alfresco;domain=SHORE;user=DB_Collaboration;password=XXXXX {noformat} ## I then installed the jtds-1.2.2.jar in the c:\alfresco\tomcat\common\lib so that it will be on the classpath when Alfresco is started ## I also added the following section to override the mail server settings {noformat} # Mail server configuration mail.host=mail.mbari.org mail.port=25 mail.username= mail.password= {noformat} # Now this is not necessarily fun, but in order to really get it configured the way we want it, you need to pull the original .war file out, edit some stuff inside and re-create the .war. {note} This should all be done before starting Alfresco for the first time. {note} # Copy the c:\Alfresco\tomcat\webapps\alfresco.war file to your home directory. # Make a second copy so that you will always the original (I copied to alfresco.war.orig and moved it somewhere else. It is important to move it and have only the alfresco.war file in the directory because when you un-jar it, all the files go right where alfresco.war is.) # From a command line, un-jar the war file using: {noformat} jar -xvf alfresco.war {noformat} # This unpacks a lot of files and after it completes, move (or delete) the alfresco.war file from the directory. This needs to be done so it does not end up in the new .war file. # I wanted to change the "Company Home" that seems to be everywhere to something that says MBARI. ## Edited ./WEB-INF/classes/alfresco/messages/webclient.properties and changed company_home from 'Company Home' to 'MBARI' ## Edited ./WEB-INF/classes/alfresco/messages/webclient_en_US.properties and changed company_home from 'Company Home' to 'MBARI' ## I edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces.properties and changed the first two lines to read {noformat} spaces.company_home.name=MBARI spaces.company_home.description=The root space for MBARI {noformat} ## Edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces_en_US.properties and made the same changes as the previous step {tip} This took a bit to find all these, and to be honest, I am not sure which one actually made the change on the GUI, but I suspect it was the _en_US ones. {tip} # When users are imported via LDAP, user spaces get created automatically. In order to put them where I wanted them to go (instead of right in the Company Home), I edited the ./WEB-INF/classes/alfresco/authentication-services-context.xml file. In the file there is a bean with an name of personalHomeFolderProvider. There is a property name 'path' and I added {noformat} /${spaces.user_homes.childname} {noformat} to the end to try to get them to create the user spaces there instead of in the Company Home. The final bean XML looks like: {noformat} /${spaces.company_home.childname}/${spaces.user_homes.childname} ${spaces.store} false All All {noformat} # I wanted to change the logo that is used. I attached the replacement logo [here|^AlfrescoLogo32.png]. Copy this to ./images/logo and overwrite the one that is there. # In order to setup SSL for the application (will do that later), edit ./WEB-INF/web.xml and add the following {noformat} Login Pages /* CONFIDENTIAL {noformat} right before the ending tag at the bottom of the file. # Now in order to change the default behavior so that all content is versioned from the start, I edited the .\WEB-INF\classes\alfresco\model\contentModel.xml and searched for the content type definition block. {noformat} Content cm:cmobject true d:content false true false true {noformat} and added the following block right before the ending tag: {noformat} cm:versionable {noformat} so the final block looks like: {noformat} Content cm:cmobject true d:content false true false true cm:versionable {noformat} # That takes care of all the changes to the WAR file. We can now put it back into .war form. # While you are in the directory you expanded the war file in, run ## jar cvfm alfresco.war META-INF\MANIFEST.MF . # You should now have an alfresco.war file in the directory. Move that back to the alfresco install and overwrite the existing one. # Most users like the details view, so I set the default to that by editing c:\Alfresco\tomcat\shared\classes\alfresco\extensions/web-client-config-custom.xml and added: {noformat} details 20
20
20 {noformat} right before the closing tag. # Now in order to use MBARI accounts, I needed to configure LDAP. {tip} In the older version of Alfresco, I actually used NTLM to manage logins, but currently 2.0's NTLM for ActiveDirectory is broken. The supposedly have fixed it in the Enterprise version, but it has not made it to the Community edition yet. That is OK, as I will just use LDAP to authenticate. {tip} ## I cd'd to the /opt/alfresco-2.0/tomcat/shared/classes/alfresco/extensions directory ## I then copied the ldap-authentication-context.xml.sample to ldap-authentication-context.xml and edited to match our ActiveDirectory setup. I have attached the file to this WIKI pages instead of detailing out all the changes. The file is [here|^ldap-authentication-context.xml] ## We wanted to be able to make sure we could have collaborator accounts that were not MBARI LDAP accounts so that we could have Alfresco users that had not permissions at all on the MBARI network. In order to do this, I used the Alfresco native user service and chained the authentication together with the MBARI LDAP. In order to do this, I copied the chaining-authentication-context.xml.sample to chaining-authentication-context.xml. I then edited the file to make the appropriate changes (I have also attached the changed config file [here|^chaining-authentication-context.xml] for downloading): ### The first change was to the first bean declaration's id from *authenticationServiceImpl* to *authenticationService*. ### In the same bean declaration, I changed the first authentication services reference from *authenticationServiceImplJAAS* to *authenticationServiceImplLDAP* ### I then changed the JAAS bean declaration to point to the ldap declaration by changing the bean id from *authenticationServiceImplJAAS* to *authenticationServiceImplLDAP* ### There are two properties in this bean and I had to change them to point to the LDAP configuration (these changes actually reference the services defined in the ldap-authentication-context.xml configuration file). #### Change the authenticationDao property's value from *authenticationDaoJAAS* to *authenticationDaoLDAP* #### Change the authenticationComponent property from *authenticationComponentImplJAAS* to *authenticationComponentImplLDAP* ## In order to grant certain accounts admin privs, I created a new custom-authority-services-context.xml in the same directory as the ldap-authentication-context.xml file and added {noformat} kgomes admin administrator {noformat} ## In the same directory, I edited the file-servers-custom.xml file and added a new config section {noformat} blizzard.shore.mbari.org shore {noformat} ]]> 2163024 18284609 18251841 2195787 "Downloads">"2.1 Releases">"2.1.1" # I then clicked on AlfrescoEnterprise-2.1.1-Setup.exe to download the installation executable. I also downloaded AlfrescoWCMEnterprise-2.1.1-Setup.exe in case I needed it later. # Went to [http://customers.alfresco.com] (I was still logged in) # Went to "Company Home">"Downloads">"2.1 Releases">"2.1.1">"License Files" # I went ahead and downloaded all the "*.lic" files, but I think I only need enterprise-network-customer-unlimited.lic" # Logged out of Alfresco. # Since I suspect I will need a JDBC driver for SQLServer, I downloaded the jTDS-1.2.2 driver from the jtds web site (just Google jtds and go to the download section of the top google return). # I closed the Firefox browser. # I extracted the jtds-1.2.2.jar file from the jtds download # I downloaded and installed the JRockit 6 R27.4 JDK Microsoft Windows (x86 - 32 bit) from BEA's web site # I ran the installer, changed the "Program Files" to "bin" in the installation directory for both the JDK and the JRE. I also chose to install the JRE as public. # Using Firefox, I downloaded the PHP 5.2.5 Windows Installer from php.net and installed it. Although I installed it, I did not integrate it with a web server as I want Alfresco to take port 80. I probably did not need to install PHP, but I thought I would anyway. (again, I changed install path from "Program Files" to "bin" # I setup a Alfresco database on the server Solstice and granted the LAGOON\DB_Collaboration account to be the db_owner of the Alfresco database. # I then executed the .exe on the alfresco server to install Alfresco # I left the installation directory as c:\Alfresco # It did not find the JDK I installed so it asked to download and install one, but I said no. # I did select the option to download and install the OpenOffice.org component. # After the installation was complete, I left the check box for "Run Configuration Wizard" checked to see if the configuration wizard was worth much. # The Wizard: ## I chose the MS SQL Database Type ## For the content location, I input "\\tornado.shore.mbari.org\alfresco\alf_data". ## For the indicies, I input "c:\alfresco\alf_data\lucene-indexes" ## I left the OpenOffice install location as "C:\Alfresco\openoffice" ## Thus completes the Wizard. # To make sure the Wizard was wise, I looked at all the configuration files that were in c:\Alfresco\tomcat\shared\classes\alfresco\extensions because this is where all the customization for a particular installation goes. # In the custom-hibernate-dialect.properties file, everything looked fine. # In the custom-repository.properties, it was not. ## The database URL was :jdbc:jtds:sqlserver://localhost/alfresco but this is not correct, we want to point it to Solstice so I changed it to: {noformat} db.url=jdbc:jtds:sqlserver://solstice.shore.mbari.org/Alfresco;domain=SHORE;user=DB_Collaboration;password=XXXXX {noformat} ## I then installed the jtds-1.2.2.jar in the c:\alfresco\tomcat\common\lib so that it will be on the classpath when Alfresco is started ## I also added the following section to override the mail server settings {noformat} # Mail server configuration mail.host=mail.mbari.org mail.port=25 mail.username= mail.password= {noformat} # Now this is not necessarily fun, but in order to really get it configured the way we want it, you need to pull the original .war file out, edit some stuff inside and re-create the .war. {note} This should all be done before starting Alfresco for the first time. {note} # Copy the c:\Alfresco\tomcat\webapps\alfresco.war file to your home directory. # Make a second copy so that you will always the original (I copied to alfresco.war.orig and moved it somewhere else. It is important to move it and have only the alfresco.war file in the directory because when you un-jar it, all the files go right where alfresco.war is.) # From a command line, un-jar the war file using: {noformat} jar -xvf alfresco.war {noformat} # This unpacks a lot of files and after it completes, move (or delete) the alfresco.war file from the directory. This needs to be done so it does not end up in the new .war file. # I wanted to change the "Company Home" that seems to be everywhere to something that says MBARI. ## Edited ./WEB-INF/classes/alfresco/messages/webclient.properties and changed company_home from 'Company Home' to 'MBARI' ## Edited ./WEB-INF/classes/alfresco/messages/webclient_en_US.properties and changed company_home from 'Company Home' to 'MBARI' ## I edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces.properties and changed the first two lines to read {noformat} spaces.company_home.name=MBARI spaces.company_home.description=The root space for MBARI {noformat} ## Edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces_en_US.properties and made the same changes as the previous step {tip} This took a bit to find all these, and to be honest, I am not sure which one actually made the change on the GUI, but I suspect it was the _en_US ones. {tip} # When users are imported via LDAP, user spaces get created automatically. In order to put them where I wanted them to go (instead of right in the Company Home), I edited the ./WEB-INF/classes/alfresco/authentication-services-context.xml file. In the file there is a bean with an name of personalHomeFolderProvider. There is a property name 'path' and I added {noformat} /${spaces.user_homes.childname} {noformat} to the end to try to get them to create the user spaces there instead of in the Company Home. The final bean XML looks like: {noformat} /${spaces.company_home.childname}/${spaces.user_homes.childname} ${spaces.store} false All All {noformat} # I wanted to change the logo that is used. I attached the replacement logo [here|^AlfrescoLogo32.png]. Copy this to ./images/logo and overwrite the one that is there. # In order to setup SSL for the application (will do that later), edit ./WEB-INF/web.xml and add the following {noformat} Login Pages /* CONFIDENTIAL {noformat} right before the ending tag at the bottom of the file. # Now in order to change the default behavior so that all content is versioned from the start, I edited the .\WEB-INF\classes\alfresco\model\contentModel.xml and searched for the content type definition block. {noformat} Content cm:cmobject true d:content false true false true {noformat} and added the following block right before the ending tag: {noformat} cm:versionable {noformat} so the final block looks like: {noformat} Content cm:cmobject true d:content false true false true cm:versionable {noformat} # That takes care of all the changes to the WAR file. We can now put it back into .war form. # While you are in the directory you expanded the war file in, run ## jar cvfm alfresco.war META-INF\MANIFEST.MF . # You should now have an alfresco.war file in the directory. Move that back to the alfresco install and overwrite the existing one. # Most users like the details view, so I set the default to that by editing c:\Alfresco\tomcat\shared\classes\alfresco\extensions/web-client-config-custom.xml and added: {noformat} details 20
20
20 {noformat} right before the closing tag. # Now, in order to get it hooked up to our LDAP system, I edited the c:\Alfresco\tomcat\shared\classes\alfresco\extensions\ldap-authentication.properties and made it look like the following: {noformat} {noformat}]]> 2163023 2195790 "Downloads">"2.1 Releases">"2.1.1" # I then clicked on AlfrescoEnterprise-2.1.1-Setup.exe to download the installation executable. I also downloaded AlfrescoWCMEnterprise-2.1.1-Setup.exe in case I needed it later. # Went to [http://customers.alfresco.com] (I was still logged in) # Went to "Company Home">"Downloads">"2.1 Releases">"2.1.1">"License Files" # I went ahead and downloaded all the "*.lic" files, but I think I only need enterprise-network-customer-unlimited.lic" # Logged out of Alfresco. # Since I suspect I will need a JDBC driver for SQLServer, I downloaded the jTDS-1.2.2 driver from the jtds web site (just Google jtds and go to the download section of the top google return). # I closed the Firefox browser. # I extracted the jtds-1.2.2.jar file from the jtds download # I downloaded and installed the JRockit 6 R27.4 JDK Microsoft Windows (x86 - 32 bit) from BEA's web site # I ran the installer, changed the "Program Files" to "bin" in the installation directory for both the JDK and the JRE. I also chose to install the JRE as public. # Using Firefox, I downloaded the PHP 5.2.5 Windows Installer from php.net and installed it. Although I installed it, I did not integrate it with a web server as I want Alfresco to take port 80. I probably did not need to install PHP, but I thought I would anyway. (again, I changed install path from "Program Files" to "bin" # I setup a Alfresco database on the server Solstice and granted the LAGOON\DB_Collaboration account to be the db_owner of the Alfresco database. # I then executed the .exe on the alfresco server to install Alfresco # I left the installation directory as c:\Alfresco # It did not find the JDK I installed so it asked to download and install one, but I said no. # I did select the option to download and install the OpenOffice.org component. # After the installation was complete, I left the check box for "Run Configuration Wizard" checked to see if the configuration wizard was worth much. # The Wizard: ## I chose the MS SQL Database Type ## For the content location, I input "\\tornado.shore.mbari.org\alfresco\alf_data". ## For the indicies, I input "c:\alfresco\alf_data\lucene-indexes" ## I left the OpenOffice install location as "C:\Alfresco\openoffice" ## Thus completes the Wizard. # To make sure the Wizard was wise, I looked at all the configuration files that were in c:\Alfresco\tomcat\shared\classes\alfresco\extensions because this is where all the customization for a particular installation goes. # In the custom-hibernate-dialect.properties file, everything looked fine. # In the custom-repository.properties, it was not. ## The database URL was :jdbc:jtds:sqlserver://localhost/alfresco but this is not correct, we want to point it to Solstice so I changed it to: {noformat} db.url=jdbc:jtds:sqlserver://solstice.shore.mbari.org/Alfresco;domain=SHORE;user=DB_Collaboration;password=XXXXX {noformat} ## I then installed the jtds-1.2.2.jar in the c:\alfresco\tomcat\common\lib so that it will be on the classpath when Alfresco is started ## I also added the following section to override the mail server settings {noformat} # Mail server configuration mail.host=mail.mbari.org mail.port=25 mail.username= mail.password= {noformat} # Now this is not necessarily fun, but in order to really get it configured the way we want it, you need to pull the original .war file out, edit some stuff inside and re-create the .war. {note} This should all be done before starting Alfresco for the first time. {note} # Copy the c:\Alfresco\tomcat\webapps\alfresco.war file to your home directory. # Make a second copy so that you will always the original (I copied to alfresco.war.orig and moved it somewhere else. It is important to move it and have only the alfresco.war file in the directory because when you un-jar it, all the files go right where alfresco.war is.) # From a command line, un-jar the war file using: {noformat} jar -xvf alfresco.war {noformat} # This unpacks a lot of files and after it completes, move (or delete) the alfresco.war file from the directory. This needs to be done so it does not end up in the new .war file. # I wanted to change the "Company Home" that seems to be everywhere to something that says MBARI. ## Edited ./WEB-INF/classes/alfresco/messages/webclient.properties and changed company_home from 'Company Home' to 'MBARI' ## Edited ./WEB-INF/classes/alfresco/messages/webclient_en_US.properties and changed company_home from 'Company Home' to 'MBARI' ## I edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces.properties and changed the first two lines to read {noformat} spaces.company_home.name=MBARI spaces.company_home.description=The root space for MBARI {noformat} ## Edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces_en_US.properties and made the same changes as the previous step {tip} This took a bit to find all these, and to be honest, I am not sure which one actually made the change on the GUI, but I suspect it was the _en_US ones. {tip} # When users are imported via LDAP, user spaces get created automatically. In order to put them where I wanted them to go (instead of right in the Company Home), I edited the ./WEB-INF/classes/alfresco/authentication-services-context.xml file. In the file there is a bean with an name of personalHomeFolderProvider. There is a property name 'path' and I added {noformat} /${spaces.user_homes.childname} {noformat} to the end to try to get them to create the user spaces there instead of in the Company Home. The final bean XML looks like: {noformat} /${spaces.company_home.childname}/${spaces.user_homes.childname} ${spaces.store} false All All {noformat} # I wanted to change the logo that is used. I attached the replacement logo [here|^AlfrescoLogo32.png]. Copy this to ./images/logo and overwrite the one that is there. # In order to setup SSL for the application (will do that later), edit ./WEB-INF/web.xml and add the following {noformat} Login Pages /* CONFIDENTIAL {noformat} right before the ending tag at the bottom of the file. # Now in order to change the default behavior so that all content is versioned from the start, I edited the .\WEB-INF\classes\alfresco\model\contentModel.xml and searched for the content type definition block. {noformat} Content cm:cmobject true d:content false true false true {noformat} and added the following block right before the ending tag: {noformat} cm:versionable {noformat} so the final block looks like: {noformat} Content cm:cmobject true d:content false true false true cm:versionable {noformat} # That takes care of all the changes to the WAR file. We can now put it back into .war form. # While you are in the directory you expanded the war file in, run ## jar cvfm alfresco.war META-INF\MANIFEST.MF . # You should now have an alfresco.war file in the directory. Move that back to the alfresco install and overwrite the existing one. # Most users like the details view, so I set the default to that by editing c:\Alfresco\tomcat\shared\classes\alfresco\extensions/web-client-config-custom.xml and added: {noformat} details 20
20
20 {noformat} right before the closing tag. # Now in order to use MBARI accounts, I needed to configure LDAP. # I downloade this [ldap-authentication-context.xml|^ldap-authentication-context.xml] file and put it in the c:\Alfresco\tomcat\shared\classes\alfresco\extensions folder. # We wanted to be able to make sure we could have collaborator accounts that were not MBARI LDAP accounts so that we could have Alfresco users that had not permissions at all on the MBARI network. In order to do this, I used the Alfresco native user service and chained the authentication together with the MBARI LDAP. In order to do this, I downloaded this [chaining-authentication-context.xml|^chaining-authentication-context.xml] file and installed in c:\Alfresco\tomcat\shared\classes\alfresco\extensions. # In order to grant certain accounts admin privs, I created a new custom-authority-services-context.xml in the same directory as the ldap-authentication-context.xml file and added {noformat} kgomes admin administrator {noformat} # In order for Alfresco to handle all port 80 traffic, I changed Tomcat so that it takes port 80 and SSL goes over port 443. So I edited the c:\Alfresco\tomcat\conf\server.xml file and changed the 8080 port to 80 and the 8443 port to 443.]]> 2163026 2195789 "Downloads">"2.1 Releases">"2.1.1" # I then clicked on AlfrescoEnterprise-2.1.1-Setup.exe to download the installation executable. I also downloaded AlfrescoWCMEnterprise-2.1.1-Setup.exe in case I needed it later. # Went to [http://customers.alfresco.com] (I was still logged in) # Went to "Company Home">"Downloads">"2.1 Releases">"2.1.1">"License Files" # I went ahead and downloaded all the "*.lic" files, but I think I only need enterprise-network-customer-unlimited.lic" # Logged out of Alfresco. # Since I suspect I will need a JDBC driver for SQLServer, I downloaded the jTDS-1.2.2 driver from the jtds web site (just Google jtds and go to the download section of the top google return). # I closed the Firefox browser. # I extracted the jtds-1.2.2.jar file from the jtds download # I downloaded and installed the JRockit 6 R27.4 JDK Microsoft Windows (x86 - 32 bit) from BEA's web site # I ran the installer, changed the "Program Files" to "bin" in the installation directory for both the JDK and the JRE. I also chose to install the JRE as public. # Using Firefox, I downloaded the PHP 5.2.5 Windows Installer from php.net and installed it. Although I installed it, I did not integrate it with a web server as I want Alfresco to take port 80. I probably did not need to install PHP, but I thought I would anyway. (again, I changed install path from "Program Files" to "bin" # I setup a Alfresco database on the server Solstice and granted the LAGOON\DB_Collaboration account to be the db_owner of the Alfresco database. # I then executed the .exe on the alfresco server to install Alfresco # I left the installation directory as c:\Alfresco # It did not find the JDK I installed so it asked to download and install one, but I said no. # I did select the option to download and install the OpenOffice.org component. # After the installation was complete, I left the check box for "Run Configuration Wizard" checked to see if the configuration wizard was worth much. # The Wizard: ## I chose the MS SQL Database Type ## For the content location, I input "\\tornado.shore.mbari.org\alfresco\alf_data". ## For the indicies, I input "c:\alfresco\alf_data\lucene-indexes" ## I left the OpenOffice install location as "C:\Alfresco\openoffice" ## Thus completes the Wizard. # To make sure the Wizard was wise, I looked at all the configuration files that were in c:\Alfresco\tomcat\shared\classes\alfresco\extensions because this is where all the customization for a particular installation goes. # In the custom-hibernate-dialect.properties file, everything looked fine. # In the custom-repository.properties, it was not. ## The database URL was :jdbc:jtds:sqlserver://localhost/alfresco but this is not correct, we want to point it to Solstice so I changed it to: {noformat} db.url=jdbc:jtds:sqlserver://solstice.shore.mbari.org/Alfresco;domain=SHORE;user=DB_Collaboration;password=XXXXX {noformat} ## I then installed the jtds-1.2.2.jar in the c:\alfresco\tomcat\common\lib so that it will be on the classpath when Alfresco is started ## I also added the following section to override the mail server settings {noformat} # Mail server configuration mail.host=mail.mbari.org mail.port=25 mail.username= mail.password= {noformat} # Now this is not necessarily fun, but in order to really get it configured the way we want it, you need to pull the original .war file out, edit some stuff inside and re-create the .war. {note} This should all be done before starting Alfresco for the first time. {note} # Copy the c:\Alfresco\tomcat\webapps\alfresco.war file to your home directory. # Make a second copy so that you will always the original (I copied to alfresco.war.orig and moved it somewhere else. It is important to move it and have only the alfresco.war file in the directory because when you un-jar it, all the files go right where alfresco.war is.) # From a command line, un-jar the war file using: {noformat} jar -xvf alfresco.war {noformat} # This unpacks a lot of files and after it completes, move (or delete) the alfresco.war file from the directory. This needs to be done so it does not end up in the new .war file. # I wanted to change the "Company Home" that seems to be everywhere to something that says MBARI. ## Edited ./WEB-INF/classes/alfresco/messages/webclient.properties and changed company_home from 'Company Home' to 'MBARI' ## Edited ./WEB-INF/classes/alfresco/messages/webclient_en_US.properties and changed company_home from 'Company Home' to 'MBARI' ## I edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces.properties and changed the first two lines to read {noformat} spaces.company_home.name=MBARI spaces.company_home.description=The root space for MBARI {noformat} ## Edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces_en_US.properties and made the same changes as the previous step {tip} This took a bit to find all these, and to be honest, I am not sure which one actually made the change on the GUI, but I suspect it was the _en_US ones. {tip} # When users are imported via LDAP, user spaces get created automatically. In order to put them where I wanted them to go (instead of right in the Company Home), I edited the ./WEB-INF/classes/alfresco/authentication-services-context.xml file. In the file there is a bean with an name of personalHomeFolderProvider. There is a property name 'path' and I added {noformat} /${spaces.user_homes.childname} {noformat} to the end to try to get them to create the user spaces there instead of in the Company Home. The final bean XML looks like: {noformat} /${spaces.company_home.childname}/${spaces.user_homes.childname} ${spaces.store} false All All {noformat} # I wanted to change the logo that is used. I attached the replacement logo [here|^AlfrescoLogo32.png]. Copy this to ./images/logo and overwrite the one that is there. # In order to setup SSL for the application (will do that later), edit ./WEB-INF/web.xml and add the following {noformat} Login Pages /* CONFIDENTIAL {noformat} right before the ending tag at the bottom of the file. # Now in order to change the default behavior so that all content is versioned from the start, I edited the .\WEB-INF\classes\alfresco\model\contentModel.xml and searched for the content type definition block. {noformat} Content cm:cmobject true d:content false true false true {noformat} and added the following block right before the ending tag: {noformat} cm:versionable {noformat} so the final block looks like: {noformat} Content cm:cmobject true d:content false true false true cm:versionable {noformat} # That takes care of all the changes to the WAR file. We can now put it back into .war form. # While you are in the directory you expanded the war file in, run ## jar cvfm alfresco.war META-INF\MANIFEST.MF . # You should now have an alfresco.war file in the directory. Move that back to the alfresco install and overwrite the existing one. # Most users like the details view, so I set the default to that by editing c:\Alfresco\tomcat\shared\classes\alfresco\extensions/web-client-config-custom.xml and added: {noformat} details 20
20
20 {noformat} right before the closing tag. # Now in order to use MBARI accounts, I needed to configure LDAP. # I downloade this [ldap-authentication-context.xml|^ldap-authentication-context.xml] file and put it in the c:\Alfresco\tomcat\shared\classes\alfresco\extensions folder. # We wanted to be able to make sure we could have collaborator accounts that were not MBARI LDAP accounts so that we could have Alfresco users that had not permissions at all on the MBARI network. In order to do this, I used the Alfresco native user service and chained the authentication together with the MBARI LDAP. In order to do this, I downloaded this [chaining-authentication-context.xml|^chaining-authentication-context.xml] file and installed in c:\Alfresco\tomcat\shared\classes\alfresco\extensions. # In order to grant certain accounts admin privs, I created a new custom-authority-services-context.xml in the same directory as the ldap-authentication-context.xml file and added {noformat} kgomes admin administrator {noformat} ]]> 2163025 2195791 "Downloads">"2.1 Releases">"2.1.1" # I then clicked on AlfrescoEnterprise-2.1.1-Setup.exe to download the installation executable. I also downloaded AlfrescoWCMEnterprise-2.1.1-Setup.exe in case I needed it later. # Went to [http://customers.alfresco.com] (I was still logged in) # Went to "Company Home">"Downloads">"2.1 Releases">"2.1.1">"License Files" # I went ahead and downloaded all the "*.lic" files, but I think I only need enterprise-network-customer-unlimited.lic" # Logged out of Alfresco. # Since I suspect I will need a JDBC driver for SQLServer, I downloaded the jTDS-1.2.2 driver from the jtds web site (just Google jtds and go to the download section of the top google return). # I closed the Firefox browser. # I extracted the jtds-1.2.2.jar file from the jtds download # I downloaded and installed the JRockit 6 R27.4 JDK Microsoft Windows (x86 - 32 bit) from BEA's web site # I ran the installer, changed the "Program Files" to "bin" in the installation directory for both the JDK and the JRE. I also chose to install the JRE as public. # Using Firefox, I downloaded the PHP 5.2.5 Windows Installer from php.net and installed it. Although I installed it, I did not integrate it with a web server as I want Alfresco to take port 80. I probably did not need to install PHP, but I thought I would anyway. (again, I changed install path from "Program Files" to "bin" # I setup a Alfresco database on the server Solstice and granted the LAGOON\DB_Collaboration account to be the db_owner of the Alfresco database. # I then executed the .exe on the alfresco server to install Alfresco # I left the installation directory as c:\Alfresco # It did not find the JDK I installed so it asked to download and install one, but I said no. # I did select the option to download and install the OpenOffice.org component. # After the installation was complete, I left the check box for "Run Configuration Wizard" checked to see if the configuration wizard was worth much. # The Wizard: ## I chose the MS SQL Database Type ## For the content location, I input "\\tornado.shore.mbari.org\alfresco\alf_data". ## For the indicies, I input "c:\alfresco\alf_data\lucene-indexes" ## I left the OpenOffice install location as "C:\Alfresco\openoffice" ## Thus completes the Wizard. # To make sure the Wizard was wise, I looked at all the configuration files that were in c:\Alfresco\tomcat\shared\classes\alfresco\extensions because this is where all the customization for a particular installation goes. # In the custom-hibernate-dialect.properties file, everything looked fine. # In the custom-repository.properties, it was not. ## The database URL was :jdbc:jtds:sqlserver://localhost/alfresco but this is not correct, we want to point it to Solstice so I changed it to: {noformat} db.url=jdbc:jtds:sqlserver://solstice.shore.mbari.org/Alfresco;domain=SHORE;user=DB_Collaboration;password=XXXXX {noformat} ## I then installed the jtds-1.2.2.jar in the c:\alfresco\tomcat\common\lib so that it will be on the classpath when Alfresco is started ## I also added the following section to override the mail server settings {noformat} # Mail server configuration mail.host=mail.mbari.org mail.port=25 mail.username= mail.password= {noformat} # Now this is not necessarily fun, but in order to really get it configured the way we want it, you need to pull the original .war file out, edit some stuff inside and re-create the .war. {note} This should all be done before starting Alfresco for the first time. {note} # Copy the c:\Alfresco\tomcat\webapps\alfresco.war file to your home directory. # Make a second copy so that you will always the original (I copied to alfresco.war.orig and moved it somewhere else. It is important to move it and have only the alfresco.war file in the directory because when you un-jar it, all the files go right where alfresco.war is.) # From a command line, un-jar the war file using: {noformat} jar -xvf alfresco.war {noformat} # This unpacks a lot of files and after it completes, move (or delete) the alfresco.war file from the directory. This needs to be done so it does not end up in the new .war file. # I wanted to change the "Company Home" that seems to be everywhere to something that says MBARI. ## Edited ./WEB-INF/classes/alfresco/messages/webclient.properties and changed company_home from 'Company Home' to 'MBARI' ## Edited ./WEB-INF/classes/alfresco/messages/webclient_en_US.properties and changed company_home from 'Company Home' to 'MBARI' ## I edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces.properties and changed the first two lines to read {noformat} spaces.company_home.name=MBARI spaces.company_home.description=The root space for MBARI {noformat} ## Edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces_en_US.properties and made the same changes as the previous step {tip} This took a bit to find all these, and to be honest, I am not sure which one actually made the change on the GUI, but I suspect it was the _en_US ones. {tip} # When users are imported via LDAP, user spaces get created automatically. In order to put them where I wanted them to go (instead of right in the Company Home), I edited the ./WEB-INF/classes/alfresco/authentication-services-context.xml file. In the file there is a bean with an name of personalHomeFolderProvider. There is a property name 'path' and I added {noformat} /${spaces.user_homes.childname} {noformat} to the end to try to get them to create the user spaces there instead of in the Company Home. The final bean XML looks like: {noformat} /${spaces.company_home.childname}/${spaces.user_homes.childname} ${spaces.store} false All All {noformat} # I wanted to change the logo that is used. I attached the replacement logo [here|^AlfrescoLogo32.png]. Copy this to ./images/logo and overwrite the one that is there. # In order to setup SSL for the application (will do that later), edit ./WEB-INF/web.xml and add the following {noformat} Login Pages /* CONFIDENTIAL {noformat} right before the ending tag at the bottom of the file. # Now in order to change the default behavior so that all content is versioned from the start, I edited the .\WEB-INF\classes\alfresco\model\contentModel.xml and searched for the content type definition block. {noformat} Content cm:cmobject true d:content false true false true {noformat} and added the following block right before the ending tag: {noformat} cm:versionable {noformat} so the final block looks like: {noformat} Content cm:cmobject true d:content false true false true cm:versionable {noformat} # That takes care of all the changes to the WAR file. We can now put it back into .war form. # While you are in the directory you expanded the war file in, run ## jar cvfm alfresco.war META-INF\MANIFEST.MF . # You should now have an alfresco.war file in the directory. Move that back to the alfresco install and overwrite the existing one. # Most users like the details view, so I set the default to that by editing c:\Alfresco\tomcat\shared\classes\alfresco\extensions/web-client-config-custom.xml and added: {noformat} details 20
20
20 {noformat} right before the closing tag. # Now in order to use MBARI accounts, I needed to configure LDAP. # I downloade this [ldap-authentication-context.xml|^ldap-authentication-context.xml] file and put it in the c:\Alfresco\tomcat\shared\classes\alfresco\extensions folder. # We wanted to be able to make sure we could have collaborator accounts that were not MBARI LDAP accounts so that we could have Alfresco users that had not permissions at all on the MBARI network. In order to do this, I used the Alfresco native user service and chained the authentication together with the MBARI LDAP. In order to do this, I downloaded this [chaining-authentication-context.xml|^chaining-authentication-context.xml] file and installed in c:\Alfresco\tomcat\shared\classes\alfresco\extensions. # In order to grant certain accounts admin privs, I created a new custom-authority-services-context.xml in the same directory as the ldap-authentication-context.xml file and added {noformat} kgomes admin administrator {noformat} # In order for Alfresco to handle all port 80 traffic, I changed Tomcat so that it takes port 80 and SSL goes over port 443. So I edited the c:\Alfresco\tomcat\conf\server.xml file and changed the 8080 port to 80 and the 8443 port to 443 (the 443 change is done in two places).]]> 2163027 21398699 21365994 2195802 "Downloads">"2.1 Releases">"2.1.1" # I then clicked on AlfrescoEnterprise-2.1.1-Setup.exe to download the installation executable. I also downloaded AlfrescoWCMEnterprise-2.1.1-Setup.exe in case I needed it later. # Went to [http://customers.alfresco.com] (I was still logged in) # Went to "Company Home">"Downloads">"2.1 Releases">"2.1.1">"License Files" # I went ahead and downloaded all the "*.lic" files, but I think I only need enterprise-network-customer-unlimited.lic" # Logged out of Alfresco. # Since I suspect I will need a JDBC driver for SQLServer, I downloaded the jTDS-1.2.2 driver from the jtds web site (just Google jtds and go to the download section of the top google return). # I closed the Firefox browser. # I extracted the jtds-1.2.2.jar file from the jtds download # I downloaded and installed the JRockit 6 R27.4 JDK Microsoft Windows (x86 - 32 bit) from BEA's web site # I ran the installer, changed the "Program Files" to "bin" in the installation directory for both the JDK and the JRE. I also chose to install the JRE as public. # Using Firefox, I downloaded the PHP 5.2.5 Windows Installer from php.net and installed it. Although I installed it, I did not integrate it with a web server as I want Alfresco to take port 80. I probably did not need to install PHP, but I thought I would anyway. (again, I changed install path from "Program Files" to "bin" # I setup a Alfresco database on the server Solstice and granted the LAGOON\DB_Collaboration account to be the db_owner of the Alfresco database. # I then executed the .exe on the alfresco server to install Alfresco # I left the installation directory as c:\Alfresco # It did not find the JDK I installed so it asked to download and install one, but I said no. # I did select the option to download and install the OpenOffice.org component. # After the installation was complete, I left the check box for "Run Configuration Wizard" checked to see if the configuration wizard was worth much. # The Wizard: ## I chose the MS SQL Database Type ## For the content location, I input "\\tornado.shore.mbari.org\alfresco\alf_data". ## For the indicies, I input "c:\alfresco\alf_data\lucene-indexes" ## I left the OpenOffice install location as "C:\Alfresco\openoffice" ## Thus completes the Wizard. # To make sure the Wizard was wise, I looked at all the configuration files that were in c:\Alfresco\tomcat\shared\classes\alfresco\extensions because this is where all the customization for a particular installation goes. # In the custom-hibernate-dialect.properties file, everything looked fine. # In the custom-repository.properties, it was not. ## The database URL was :jdbc:jtds:sqlserver://localhost/alfresco but this is not correct, we want to point it to Solstice so I changed it to: {noformat} db.url=jdbc:jtds:sqlserver://solstice.shore.mbari.org/Alfresco;domain=SHORE;user=DB_Collaboration;password=XXXXX {noformat} ## I then installed the jtds-1.2.2.jar in the c:\alfresco\tomcat\common\lib so that it will be on the classpath when Alfresco is started ## I also added the following section to override the mail server settings {noformat} # Mail server configuration mail.host=mail.mbari.org mail.port=25 mail.username= mail.password= {noformat} # Now this is not necessarily fun, but in order to really get it configured the way we want it, you need to pull the original .war file out, edit some stuff inside and re-create the .war. {note} This should all be done before starting Alfresco for the first time. {note} # Copy the c:\Alfresco\tomcat\webapps\alfresco.war file to your home directory. # Make a second copy so that you will always the original (I copied to alfresco.war.orig and moved it somewhere else. It is important to move it and have only the alfresco.war file in the directory because when you un-jar it, all the files go right where alfresco.war is.) # From a command line, un-jar the war file using: {noformat} jar -xvf alfresco.war {noformat} # This unpacks a lot of files and after it completes, move (or delete) the alfresco.war file from the directory. This needs to be done so it does not end up in the new .war file. # I wanted to change the "Company Home" that seems to be everywhere to something that says MBARI. ## Edited ./WEB-INF/classes/alfresco/messages/webclient.properties and changed company_home from 'Company Home' to 'MBARI' ## Edited ./WEB-INF/classes/alfresco/messages/webclient_en_US.properties and changed company_home from 'Company Home' to 'MBARI' ## I edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces.properties and changed the first two lines to read {noformat} spaces.company_home.name=MBARI spaces.company_home.description=The root space for MBARI {noformat} ## Edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces_en_US.properties and made the same changes as the previous step {tip} This took a bit to find all these, and to be honest, I am not sure which one actually made the change on the GUI, but I suspect it was the _en_US ones. {tip} # When users are imported via LDAP, user spaces get created automatically. In order to put them where I wanted them to go (instead of right in the Company Home), I edited the ./WEB-INF/classes/alfresco/authentication-services-context.xml file. In the file there is a bean with an name of personalHomeFolderProvider. There is a property name 'path' and I added {noformat} /${spaces.user_homes.childname} {noformat} to the end to try to get them to create the user spaces there instead of in the Company Home. The final bean XML looks like: {noformat} /${spaces.company_home.childname}/${spaces.user_homes.childname} ${spaces.store} false All All {noformat} # I wanted to change the logo that is used. I attached the replacement logo [here|^AlfrescoLogo32.png]. Copy this to ./images/logo and overwrite the one that is there. # In order to setup SSL for the application (will do that later), edit ./WEB-INF/web.xml and add the following {noformat} Login Pages /* CONFIDENTIAL {noformat} right before the ending tag at the bottom of the file. # Now in order to change the default behavior so that all content is versioned from the start, I edited the .\WEB-INF\classes\alfresco\model\contentModel.xml and searched for the content type definition block. {noformat} Content cm:cmobject true d:content false true false true {noformat} and added the following block right before the ending tag: {noformat} cm:versionable {noformat} so the final block looks like: {noformat} Content cm:cmobject true d:content false true false true cm:versionable {noformat} # That takes care of all the changes to the WAR file. We can now put it back into .war form. # While you are in the directory you expanded the war file in, run ## jar cvfm alfresco.war META-INF\MANIFEST.MF . # You should now have an alfresco.war file in the directory. Move that back to the alfresco install and overwrite the existing one. # Most users like the details view, so I set the default to that by editing c:\Alfresco\tomcat\shared\classes\alfresco\extensions/web-client-config-custom.xml and added: {noformat} details 20
20
20 {noformat} right before the closing tag. # Now in order to use MBARI accounts, I needed to configure LDAP. # I downloade this [ldap-authentication-context.xml|^ldap-authentication-context.xml] file and put it in the c:\Alfresco\tomcat\shared\classes\alfresco\extensions folder. # We wanted to be able to make sure we could have collaborator accounts that were not MBARI LDAP accounts so that we could have Alfresco users that had not permissions at all on the MBARI network. In order to do this, I used the Alfresco native user service and chained the authentication together with the MBARI LDAP. In order to do this, I downloaded this [chaining-authentication-context.xml|^chaining-authentication-context.xml] file and installed in c:\Alfresco\tomcat\shared\classes\alfresco\extensions. # In order to grant certain accounts admin privs, I created a new custom-authority-services-context.xml in the same directory as the ldap-authentication-context.xml file and added {noformat} kgomes admin administrator {noformat} # In order for Alfresco to handle all port 80 traffic, I changed Tomcat so that it takes port 80 and SSL goes over port 443. So I edited the c:\Alfresco\tomcat\conf\server.xml file and changed the 8080 port to 80 and the 8443 port to 443 (the 443 change is done in two places). # I copied the enterprise-network-unlimited.lic file into the c:\Alfresco\tomcat\shared\classes\alfresco\extensions\license directory]]> 2163038 2195803 "Downloads">"2.1 Releases">"2.1.1" # I then clicked on alfresco-enterprise-tomcat-2.1.1.zip to download the zip file. # Went to [http://customers.alfresco.com] (I was still logged in) # Went to "Company Home">"Downloads">"2.1 Releases">"2.1.1">"License Files" # I went ahead and downloaded all the "*.lic" files, but I think I only need enterprise-network-customer-unlimited.lic" # Logged out of Alfresco. # Since I suspect I will need a JDBC driver for SQLServer, I downloaded the jTDS-1.2.2 driver from the jtds web site (just Google jtds and go to the download section of the top google return). # I closed the Firefox browser. # I extracted the jtds-1.2.2.jar file from the jtds download # I downloaded and installed the JRockit 6 R27.4 JDK Microsoft Windows (x86 - 32 bit) from BEA's web site # I also downloaded and installed OpenOffice. # I ran the installer, changed the "Program Files" to "bin" in the installation directory for both the JDK and the JRE. I also chose to install the JRE as public. # Using Firefox, I downloaded the PHP 5.2.5 Windows Installer from php.net and installed it. Although I installed it, I did not integrate it with a web server as I want Alfresco to take port 80. I probably did not need to install PHP, but I thought I would anyway. (again, I changed install path from "Program Files" to "bin" # I setup a Alfresco database on the server Solstice and granted the LAGOON\DB_Collaboration account to be the db_owner of the Alfresco database. # I then executed the .exe on the alfresco server to install Alfresco # I left the installation directory as c:\Alfresco # It did not find the JDK I installed so it asked to download and install one, but I said no. # I did select the option to download and install the OpenOffice.org component. # After the installation was complete, I left the check box for "Run Configuration Wizard" checked to see if the configuration wizard was worth much. # The Wizard: ## I chose the MS SQL Database Type ## For the content location, I input "\\tornado.shore.mbari.org\alfresco\alf_data". ## For the indicies, I input "c:\alfresco\alf_data\lucene-indexes" ## I left the OpenOffice install location as "C:\Alfresco\openoffice" ## Thus completes the Wizard. # To make sure the Wizard was wise, I looked at all the configuration files that were in c:\Alfresco\tomcat\shared\classes\alfresco\extensions because this is where all the customization for a particular installation goes. # In the custom-hibernate-dialect.properties file, everything looked fine. # In the custom-repository.properties, it was not. ## The database URL was :jdbc:jtds:sqlserver://localhost/alfresco but this is not correct, we want to point it to Solstice so I changed it to: {noformat} db.url=jdbc:jtds:sqlserver://solstice.shore.mbari.org/Alfresco;domain=SHORE;user=DB_Collaboration;password=XXXXX {noformat} ## I then installed the jtds-1.2.2.jar in the c:\alfresco\tomcat\common\lib so that it will be on the classpath when Alfresco is started ## I also added the following section to override the mail server settings {noformat} # Mail server configuration mail.host=mail.mbari.org mail.port=25 mail.username= mail.password= {noformat} # Now this is not necessarily fun, but in order to really get it configured the way we want it, you need to pull the original .war file out, edit some stuff inside and re-create the .war. {note} This should all be done before starting Alfresco for the first time. {note} # Copy the c:\Alfresco\tomcat\webapps\alfresco.war file to your home directory. # Make a second copy so that you will always the original (I copied to alfresco.war.orig and moved it somewhere else. It is important to move it and have only the alfresco.war file in the directory because when you un-jar it, all the files go right where alfresco.war is.) # From a command line, un-jar the war file using: {noformat} jar -xvf alfresco.war {noformat} # This unpacks a lot of files and after it completes, move (or delete) the alfresco.war file from the directory. This needs to be done so it does not end up in the new .war file. # I wanted to change the "Company Home" that seems to be everywhere to something that says MBARI. ## Edited ./WEB-INF/classes/alfresco/messages/webclient.properties and changed company_home from 'Company Home' to 'MBARI' ## Edited ./WEB-INF/classes/alfresco/messages/webclient_en_US.properties and changed company_home from 'Company Home' to 'MBARI' ## I edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces.properties and changed the first two lines to read {noformat} spaces.company_home.name=MBARI spaces.company_home.description=The root space for MBARI {noformat} ## Edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces_en_US.properties and made the same changes as the previous step {tip} This took a bit to find all these, and to be honest, I am not sure which one actually made the change on the GUI, but I suspect it was the _en_US ones. {tip} # When users are imported via LDAP, user spaces get created automatically. In order to put them where I wanted them to go (instead of right in the Company Home), I edited the ./WEB-INF/classes/alfresco/authentication-services-context.xml file. In the file there is a bean with an name of personalHomeFolderProvider. There is a property name 'path' and I added {noformat} /${spaces.user_homes.childname} {noformat} to the end to try to get them to create the user spaces there instead of in the Company Home. The final bean XML looks like: {noformat} /${spaces.company_home.childname}/${spaces.user_homes.childname} ${spaces.store} false All All {noformat} # I wanted to change the logo that is used. I attached the replacement logo [here|^AlfrescoLogo32.png]. Copy this to ./images/logo and overwrite the one that is there. # In order to setup SSL for the application (will do that later), edit ./WEB-INF/web.xml and add the following {noformat} Login Pages /* CONFIDENTIAL {noformat} right before the ending tag at the bottom of the file. # Now in order to change the default behavior so that all content is versioned from the start, I edited the .\WEB-INF\classes\alfresco\model\contentModel.xml and searched for the content type definition block. {noformat} Content cm:cmobject true d:content false true false true {noformat} and added the following block right before the ending tag: {noformat} cm:versionable {noformat} so the final block looks like: {noformat} Content cm:cmobject true d:content false true false true cm:versionable {noformat} # That takes care of all the changes to the WAR file. We can now put it back into .war form. # While you are in the directory you expanded the war file in, run ## jar cvfm alfresco.war META-INF\MANIFEST.MF . # You should now have an alfresco.war file in the directory. Move that back to the alfresco install and overwrite the existing one. # Most users like the details view, so I set the default to that by editing c:\Alfresco\tomcat\shared\classes\alfresco\extensions/web-client-config-custom.xml and added: {noformat} details 20
20
20 {noformat} right before the closing tag. # Now in order to use MBARI accounts, I needed to configure LDAP. # I downloade this [ldap-authentication-context.xml|^ldap-authentication-context.xml] file and put it in the c:\Alfresco\tomcat\shared\classes\alfresco\extensions folder. # We wanted to be able to make sure we could have collaborator accounts that were not MBARI LDAP accounts so that we could have Alfresco users that had not permissions at all on the MBARI network. In order to do this, I used the Alfresco native user service and chained the authentication together with the MBARI LDAP. In order to do this, I downloaded this [chaining-authentication-context.xml|^chaining-authentication-context.xml] file and installed in c:\Alfresco\tomcat\shared\classes\alfresco\extensions. # In order to grant certain accounts admin privs, I created a new custom-authority-services-context.xml in the same directory as the ldap-authentication-context.xml file and added {noformat} kgomes admin administrator {noformat} # In order for Alfresco to handle all port 80 traffic, I changed Tomcat so that it takes port 80 and SSL goes over port 443. So I edited the c:\Alfresco\tomcat\conf\server.xml file and changed the 8080 port to 80 and the 8443 port to 443 (the 443 change is done in two places). # I copied the enterprise-network-unlimited.lic file into the c:\Alfresco\tomcat\shared\classes\alfresco\extensions\license directory]]> 2163039 2195807 "Downloads">"2.1 Releases">"2.1.1" # I then clicked on alfresco-enterprise-tomcat-2.1.1.zip to download the zip file. # Went to [http://customers.alfresco.com] (I was still logged in) # Went to "Company Home">"Downloads">"2.1 Releases">"2.1.1">"License Files" # I went ahead and downloaded all the "*.lic" files, but I think I only need enterprise-network-customer-unlimited.lic" # Logged out of Alfresco. # Since I suspect I will need a JDBC driver for SQLServer, I downloaded the jTDS-1.2.2 driver from the jtds web site (just Google jtds and go to the download section of the top google return). # I closed the Firefox browser. # I extracted the jtds-1.2.2.jar file from the jtds download # I downloaded and installed the JRockit 6 R27.4 JDK Microsoft Windows (x86 - 32 bit) from BEA's web site {note} After installing JRockit, make sure you set the JAVA_HOME environment variable to point to the installation of JRockit. For example, I went to the desktop, right clicked on the computer, did Properties, then clicked on the Advanced tab, then click on the environment variables button and then created a new system variable named JAVA_HOME and set to c:\bin\Java\jrockit-R27.4.0-jdk1.6.0_02 {note} # I also downloaded and installed OpenOffice. # I ran the installer, changed the "Program Files" to "bin" in the installation directory for both the JDK and the JRE. I also chose to install the JRE as public. # Using Firefox, I downloaded the PHP 5.2.5 Windows Installer from php.net and installed it. Although I installed it, I did not integrate it with a web server as I want Alfresco to take port 80. I probably did not need to install PHP, but I thought I would anyway. (again, I changed install path from "Program Files" to "bin" # I setup a Alfresco database on the server Solstice and granted the LAGOON\DB_Collaboration account to be the db_owner of the Alfresco database. # I then executed the .exe on the alfresco server to install Alfresco # I left the installation directory as c:\Alfresco # It did not find the JDK I installed so it asked to download and install one, but I said no. # I did select the option to download and install the OpenOffice.org component. # After the installation was complete, I left the check box for "Run Configuration Wizard" checked to see if the configuration wizard was worth much. # The Wizard: ## I chose the MS SQL Database Type ## For the content location, I input "\\tornado.shore.mbari.org\alfresco\alf_data". ## For the indicies, I input "c:\alfresco\alf_data\lucene-indexes" ## I left the OpenOffice install location as "C:\Alfresco\openoffice" ## Thus completes the Wizard. # To make sure the Wizard was wise, I looked at all the configuration files that were in c:\Alfresco\tomcat\shared\classes\alfresco\extensions because this is where all the customization for a particular installation goes. # In the custom-hibernate-dialect.properties file, everything looked fine. # In the custom-repository.properties, it was not. ## The database URL was :jdbc:jtds:sqlserver://localhost/alfresco but this is not correct, we want to point it to Solstice so I changed it to: {noformat} db.url=jdbc:jtds:sqlserver://solstice.shore.mbari.org/Alfresco;domain=SHORE;user=DB_Collaboration;password=XXXXX {noformat} ## I then installed the jtds-1.2.2.jar in the c:\alfresco\tomcat\common\lib so that it will be on the classpath when Alfresco is started ## I also added the following section to override the mail server settings {noformat} # Mail server configuration mail.host=mail.mbari.org mail.port=25 mail.username= mail.password= {noformat} # Now this is not necessarily fun, but in order to really get it configured the way we want it, you need to pull the original .war file out, edit some stuff inside and re-create the .war. {note} This should all be done before starting Alfresco for the first time. {note} # Copy the c:\Alfresco\tomcat\webapps\alfresco.war file to your home directory. # Make a second copy so that you will always the original (I copied to alfresco.war.orig and moved it somewhere else. It is important to move it and have only the alfresco.war file in the directory because when you un-jar it, all the files go right where alfresco.war is.) # From a command line, un-jar the war file using: {noformat} jar -xvf alfresco.war {noformat} # This unpacks a lot of files and after it completes, move (or delete) the alfresco.war file from the directory. This needs to be done so it does not end up in the new .war file. # I wanted to change the "Company Home" that seems to be everywhere to something that says MBARI. ## Edited ./WEB-INF/classes/alfresco/messages/webclient.properties and changed company_home from 'Company Home' to 'MBARI' ## Edited ./WEB-INF/classes/alfresco/messages/webclient_en_US.properties and changed company_home from 'Company Home' to 'MBARI' ## I edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces.properties and changed the first two lines to read {noformat} spaces.company_home.name=MBARI spaces.company_home.description=The root space for MBARI {noformat} ## Edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces_en_US.properties and made the same changes as the previous step {tip} This took a bit to find all these, and to be honest, I am not sure which one actually made the change on the GUI, but I suspect it was the _en_US ones. {tip} # When users are imported via LDAP, user spaces get created automatically. In order to put them where I wanted them to go (instead of right in the Company Home), I edited the ./WEB-INF/classes/alfresco/authentication-services-context.xml file. In the file there is a bean with an name of personalHomeFolderProvider. There is a property name 'path' and I added {noformat} /${spaces.user_homes.childname} {noformat} to the end to try to get them to create the user spaces there instead of in the Company Home. The final bean XML looks like: {noformat} /${spaces.company_home.childname}/${spaces.user_homes.childname} ${spaces.store} false All All {noformat} # I wanted to change the logo that is used. I attached the replacement logo [here|^AlfrescoLogo32.png]. Copy this to ./images/logo and overwrite the one that is there. # In order to setup SSL for the application (will do that later), edit ./WEB-INF/web.xml and add the following {noformat} Login Pages /* CONFIDENTIAL {noformat} right before the ending tag at the bottom of the file. # Now in order to change the default behavior so that all content is versioned from the start, I edited the .\WEB-INF\classes\alfresco\model\contentModel.xml and searched for the content type definition block. {noformat} Content cm:cmobject true d:content false true false true {noformat} and added the following block right before the ending tag: {noformat} cm:versionable {noformat} so the final block looks like: {noformat} Content cm:cmobject true d:content false true false true cm:versionable {noformat} # That takes care of all the changes to the WAR file. We can now put it back into .war form. # While you are in the directory you expanded the war file in, run ## jar cvfm alfresco.war META-INF\MANIFEST.MF . # You should now have an alfresco.war file in the directory. Move that back to the alfresco install and overwrite the existing one. # Most users like the details view, so I set the default to that by editing c:\Alfresco\tomcat\shared\classes\alfresco\extensions/web-client-config-custom.xml and added: {noformat} details 20
20
20 {noformat} right before the closing tag. # Now in order to use MBARI accounts, I needed to configure LDAP. # I downloade this [ldap-authentication-context.xml|^ldap-authentication-context.xml] file and put it in the c:\Alfresco\tomcat\shared\classes\alfresco\extensions folder. # We wanted to be able to make sure we could have collaborator accounts that were not MBARI LDAP accounts so that we could have Alfresco users that had not permissions at all on the MBARI network. In order to do this, I used the Alfresco native user service and chained the authentication together with the MBARI LDAP. In order to do this, I downloaded this [chaining-authentication-context.xml|^chaining-authentication-context.xml] file and installed in c:\Alfresco\tomcat\shared\classes\alfresco\extensions. # In order to grant certain accounts admin privs, I created a new custom-authority-services-context.xml in the same directory as the ldap-authentication-context.xml file and added {noformat} kgomes admin administrator {noformat} # In order for Alfresco to handle all port 80 traffic, I changed Tomcat so that it takes port 80 and SSL goes over port 443. So I edited the c:\Alfresco\tomcat\conf\server.xml file and changed the 8080 port to 80 and the 8443 port to 443 (the 443 change is done in two places). # I copied the enterprise-network-unlimited.lic file into the c:\Alfresco\tomcat\shared\classes\alfresco\extensions\license directory]]> 2163043 16252962 127.0.0.1 8443 8443 {noformat} {note} # I restarted Bamboo to verify that the SSL connection works. # I then shutdown the Bamboo installation and followed the instructions [here|http://confluence.atlassian.com/display/CROWD/Integrating+Crowd+with+Atlassian+Bamboo] to integrate it with Crowd. Below are the specific things I had to do for our installation ## In order to keep the default groups of bamboo-admin and bamboo-users out of our LDAP, I created those two groups in the MBARI Crowd directory and then created a bambooadmin account that belongs to both. That meets the requirements of Bamboo and does not force our I.S. group to have to have bamboo-admin and bamboo-user groups in our LDAP. ## The rest of the configuration was pretty straightforward except for the fact that Crowd is now using SSL and the connection between build-server and crowd was over SSL. This caused much grief as the connection was not trusted so I finally found some instructions on how to get around that [here|http://blogs.sun.com/andreas/entry/no_more_unable_to_find]. After I ran the program attached and installed the keystore in the java jre/lib/security directory, all was well and I could authenticate into Bamboo using MBARI's LDAP and MBARI Crowd directory. # The last step was to get all this running as a different user. ## I shutdown bamboo. ## I then did a 'chown -R root:root /opt/Bamboo' to make sure that the default ownership of all the files was root ## I did a 'chown -R DB_Collaboration:DB_Collaboration /data/Bamboo' to make sure the DB_Collaboration account owned all the bamboo data. ## I then went in to the /opt/Bamboo directory and gave ownership of the following files and directories to DB_Collaboration. ### atlassian-bamboo.log ### logs ### /opt/Bamboo (so the bamboo.pid file can be created) ## I then created the /etc/init.d/bamboo script: {noformat} #!/bin/sh # Startup script for bamboo # # chkconfig: 2345 99 01 # description: Atlassian Bamboo # pidfile: /var/run/bamboo.pid . /etc/rc.d/init.d/functions BAMBOO_HOME=/data/Bamboo BAMBOO_INSTALL=/opt/Bamboo BAMBOO_USER=DB_Collaboration export BAMBOO_HOME NAME=bamboo BPID=${BAMBOO_INSTALL}/bamboo.pid PID=/var/run/${NAME}.pid cd ${BAMBOO_INSTALL} if [ _$1 = _condrestart ]; then su - ${BAMBOO_USER} -c " cd ${BAMBOO_INSTALL} && ${BAMBOO_INSTALL}/bamboo.sh stop && ${BAMBOO_INSTALL}/bamboo.sh start " else su - ${BAMBOO_USER} -c " cd ${BAMBOO_INSTALL} && ${BAMBOO_INSTALL}/bamboo.sh $@ " fi RC=$? if [ -f $BPID ]; then cp -- $BPID $PID touch /var/lock/subsys/${NAME} else rm -- $PID /var/lock/subsys/${NAME} 2>/dev/null fi exit $RC {noformat} # I made it executable by all and changed the ownership to root:root # I then ran the following to configure it to start: {noformat} sudo /sbin/chkconfig --add bamboo sudo /sbin/chkconfig bamboo on sudo /sbin/service bamboo start {noformat} # I then downloaded the selenium rc server jar file, put it in the /opt/selenium directory and created the following script and put it in /etc/init.d/selenium {noformat} #!/bin/sh # chkconfig: 2345 99 01 # description: Selenium RC Service Agent . /etc/rc.d/init.d/functions scriptFile=$(readlink -fn $(type -p $0)) scriptDir=$(dirname $scriptFile) # This is the directory where selenium is installed applDir=/opt/selenium-rc # The service names serviceName=SeleniumRC serviceNameLo=SeleniumRC # The group that will be used to run the service serviceUser=DB_Collaboration serviceGroup=DB_Collaboration # This is the process id file pidFile=/opt/selenium-rc/selenium.pid # This is the log file where messages will be written serviceLogFile=/opt/selenium-rc/log/selenium.log # The java command to run javaCommand=java # The arguments to pass to the java command javaArgs="-jar selenium-server-standalone-2.0b2.jar" # The full java command line javaCommandLine="$javaCommand $javaArgs" javaCommandLineKeyword=selenium-server-standalone # The time to wait for the graceful shutdown to work before sending SIGKILL maxShutdownTime=15 # This is a function to create a file and make it writable by the process group function makeFileWritable { local filename="$1" touch $filename || return 1 chgrp $serviceGroup $filename || return 1 chmod g+w $filename || return 1 return 0; } # This function checks if the process with the pid that is passed in is running function checkProcessIsRunning { local pid="$1" if [ -z "$pid" -o "$pid" == " " ]; then return 1; fi if [ ! -e /proc/$pid ]; then return 1; fi return 0; } # This function checks to see if the process id is the one that we started function checkProcessIsOurService { local pid="$1" if [ "$(ps -p $pid --no-headers -o comm)" != "$javaCommand" ]; then return 1; fi grep -q "$javaCommandLineKeyword" /proc/$pid/cmdline if [ $? -ne 0 ]; then return 1; fi return 0; } # This actually starts the service running function startServiceProcess { cd $applDir || return 1 rm -f $pidFile makeFileWritable $pidFile || return 1 makeFileWritable $serviceLogFile || return 1 cmd="nohup $javaCommandLine >>$serviceLogFile 2>&1 & echo \$! >$pidFile" sudo -u $serviceUser $SHELL -c "$cmd" || return 1 # $SHELL -c "$cmd" || return 1 sleep 0.1 pid="$(<$pidFile)" if checkProcessIsRunning $pid; then :; else echo "$serviceName service started, log file $serviceLogFile." return 1 fi return 0; } # This function stops the process function stopServiceProcess { kill $pid || return 1 for ((i=0; i 16220195 2195808 "Downloads">"2.1 Releases">"2.1.1" # I then clicked on alfresco-enterprise-tomcat-2.1.1.zip to download the zip file. # Went to [http://customers.alfresco.com] (I was still logged in) # Went to "Company Home">"Downloads">"2.1 Releases">"2.1.1">"License Files" # I went ahead and downloaded all the "*.lic" files, but I think I only need enterprise-network-customer-unlimited.lic" # Logged out of Alfresco. # Since I suspect I will need a JDBC driver for SQLServer, I downloaded the jTDS-1.2.2 driver from the jtds web site (just Google jtds and go to the download section of the top google return). # I closed the Firefox browser. # I extracted the jtds-1.2.2.jar file from the jtds download # I downloaded and installed the JRockit 6 R27.4 JDK Microsoft Windows (x86 - 32 bit) from BEA's web site {note} After installing JRockit, make sure you set the JAVA_HOME environment variable to point to the installation of JRockit. For example, I went to the desktop, right clicked on the computer, did Properties, then clicked on the Advanced tab, then click on the environment variables button and then created a new system variable named JAVA_HOME and set to c:\bin\Java\jrockit-R27.4.0-jdk1.6.0_02 {note} # I ran the installer, changed the "Program Files" to "bin" in the installation directory for both the JDK and the JRE. I also chose to install the JRE as public. # Using Firefox, I downloaded the PHP 5.2.5 Windows Installer from php.net and installed it. Although I installed it, I did not integrate it with a web server as I want Alfresco to take port 80. I probably did not need to install PHP, but I thought I would anyway. (again, I changed install path from "Program Files" to "bin" # I also downloaded and installed OpenOffice and ran it once so I could get through the initial startup # I setup a Alfresco database on the server Solstice and granted the LAGOON\DB_Collaboration account to be the db_owner of the Alfresco database. # I unzipped the alfresco tomcat zip file to an alfresco directory in c:\bin # I then went to the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions directory for the customization of the server. ## I edited the custom-repository.properties file ### Changed the dir.root and dir.indexes to look like: {noformat} dir.root=//tornado.shore.mbari.org/Alfresco/alf_data dir.indexes=d:/alf_data/lucene-indexes {noformat} ### Commented out the db.* lines for the HSQL Connection (db.driver and db.url) ### Uncommented the db.* lines for MSSQL and changed to use the jTDS driver. They should look like: {noformat} db.driver=net.sourceforge.jtds.jdbc.Driver db.url=jdbc:jtds:sqlserver://solstice.shore.mbari.org/Alfresco;domain=SHORE;user=DB_Collaboration;password=XXXXXXXXX {noformat} ## Edited the custom-hibernate-dialect.properties file ### Commented out the HSQL Dialect ### Uncommented the MSSQL Dialect -- Needs updating -- # In the custom-hibernate-dialect.properties file, everything looked fine. # In the custom-repository.properties, it was not. ## The database URL was :jdbc:jtds:sqlserver://localhost/alfresco but this is not correct, we want to point it to Solstice so I changed it to: {noformat} db.url=jdbc:jtds:sqlserver://solstice.shore.mbari.org/Alfresco;domain=SHORE;user=DB_Collaboration;password=XXXXX {noformat} ## I then installed the jtds-1.2.2.jar in the c:\alfresco\tomcat\common\lib so that it will be on the classpath when Alfresco is started ## I also added the following section to override the mail server settings {noformat} # Mail server configuration mail.host=mail.mbari.org mail.port=25 mail.username= mail.password= {noformat} # Now this is not necessarily fun, but in order to really get it configured the way we want it, you need to pull the original .war file out, edit some stuff inside and re-create the .war. {note} This should all be done before starting Alfresco for the first time. {note} # Copy the c:\Alfresco\tomcat\webapps\alfresco.war file to your home directory. # Make a second copy so that you will always the original (I copied to alfresco.war.orig and moved it somewhere else. It is important to move it and have only the alfresco.war file in the directory because when you un-jar it, all the files go right where alfresco.war is.) # From a command line, un-jar the war file using: {noformat} jar -xvf alfresco.war {noformat} # This unpacks a lot of files and after it completes, move (or delete) the alfresco.war file from the directory. This needs to be done so it does not end up in the new .war file. # I wanted to change the "Company Home" that seems to be everywhere to something that says MBARI. ## Edited ./WEB-INF/classes/alfresco/messages/webclient.properties and changed company_home from 'Company Home' to 'MBARI' ## Edited ./WEB-INF/classes/alfresco/messages/webclient_en_US.properties and changed company_home from 'Company Home' to 'MBARI' ## I edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces.properties and changed the first two lines to read {noformat} spaces.company_home.name=MBARI spaces.company_home.description=The root space for MBARI {noformat} ## Edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces_en_US.properties and made the same changes as the previous step {tip} This took a bit to find all these, and to be honest, I am not sure which one actually made the change on the GUI, but I suspect it was the _en_US ones. {tip} # When users are imported via LDAP, user spaces get created automatically. In order to put them where I wanted them to go (instead of right in the Company Home), I edited the ./WEB-INF/classes/alfresco/authentication-services-context.xml file. In the file there is a bean with an name of personalHomeFolderProvider. There is a property name 'path' and I added {noformat} /${spaces.user_homes.childname} {noformat} to the end to try to get them to create the user spaces there instead of in the Company Home. The final bean XML looks like: {noformat} /${spaces.company_home.childname}/${spaces.user_homes.childname} ${spaces.store} false All All {noformat} # I wanted to change the logo that is used. I attached the replacement logo [here|^AlfrescoLogo32.png]. Copy this to ./images/logo and overwrite the one that is there. # In order to setup SSL for the application (will do that later), edit ./WEB-INF/web.xml and add the following {noformat} Login Pages /* CONFIDENTIAL {noformat} right before the ending tag at the bottom of the file. # Now in order to change the default behavior so that all content is versioned from the start, I edited the .\WEB-INF\classes\alfresco\model\contentModel.xml and searched for the content type definition block. {noformat} Content cm:cmobject true d:content false true false true {noformat} and added the following block right before the ending tag: {noformat} cm:versionable {noformat} so the final block looks like: {noformat} Content cm:cmobject true d:content false true false true cm:versionable {noformat} # That takes care of all the changes to the WAR file. We can now put it back into .war form. # While you are in the directory you expanded the war file in, run ## jar cvfm alfresco.war META-INF\MANIFEST.MF . # You should now have an alfresco.war file in the directory. Move that back to the alfresco install and overwrite the existing one. # Most users like the details view, so I set the default to that by editing c:\Alfresco\tomcat\shared\classes\alfresco\extensions/web-client-config-custom.xml and added: {noformat} details 20
20
20 {noformat} right before the closing tag. # Now in order to use MBARI accounts, I needed to configure LDAP. # I downloade this [ldap-authentication-context.xml|^ldap-authentication-context.xml] file and put it in the c:\Alfresco\tomcat\shared\classes\alfresco\extensions folder. # We wanted to be able to make sure we could have collaborator accounts that were not MBARI LDAP accounts so that we could have Alfresco users that had not permissions at all on the MBARI network. In order to do this, I used the Alfresco native user service and chained the authentication together with the MBARI LDAP. In order to do this, I downloaded this [chaining-authentication-context.xml|^chaining-authentication-context.xml] file and installed in c:\Alfresco\tomcat\shared\classes\alfresco\extensions. # In order to grant certain accounts admin privs, I created a new custom-authority-services-context.xml in the same directory as the ldap-authentication-context.xml file and added {noformat} kgomes admin administrator {noformat} # In order for Alfresco to handle all port 80 traffic, I changed Tomcat so that it takes port 80 and SSL goes over port 443. So I edited the c:\Alfresco\tomcat\conf\server.xml file and changed the 8080 port to 80 and the 8443 port to 443 (the 443 change is done in two places). # I copied the enterprise-network-unlimited.lic file into the c:\Alfresco\tomcat\shared\classes\alfresco\extensions\license directory]]> 2163044 16252960 127.0.0.1 8443 8443 {noformat} {note} # I restarted Bamboo to verify that the SSL connection works. # I then shutdown the Bamboo installation and followed the instructions [here|http://confluence.atlassian.com/display/CROWD/Integrating+Crowd+with+Atlassian+Bamboo] to integrate it with Crowd. Below are the specific things I had to do for our installation ## In order to keep the default groups of bamboo-admin and bamboo-users out of our LDAP, I created those two groups in the MBARI Crowd directory and then created a bambooadmin account that belongs to both. That meets the requirements of Bamboo and does not force our I.S. group to have to have bamboo-admin and bamboo-user groups in our LDAP. ## The rest of the configuration was pretty straightforward except for the fact that Crowd is now using SSL and the connection between build-server and crowd was over SSL. This caused much grief as the connection was not trusted so I finally found some instructions on how to get around that [here|http://blogs.sun.com/andreas/entry/no_more_unable_to_find]. After I ran the program attached and installed the keystore in the java jre/lib/security directory, all was well and I could authenticate into Bamboo using MBARI's LDAP and MBARI Crowd directory. # The last step was to get all this running as a different user. ## I shutdown bamboo. ## I then did a 'chown -R root:root /opt/Bamboo' to make sure that the default ownership of all the files was root ## I did a 'chown -R DB_Collaboration:DB_Collaboration /data/Bamboo' to make sure the DB_Collaboration account owned all the bamboo data. ## I then went in to the /opt/Bamboo directory and gave ownership of the following files and directories to DB_Collaboration. ### atlassian-bamboo.log ### logs ### /opt/Bamboo (so the bamboo.pid file can be created) ## I then created the /etc/init.d/bamboo script: {noformat} #!/bin/sh # Startup script for bamboo # # chkconfig: 2345 99 01 # description: Atlassian Bamboo # pidfile: /var/run/bamboo.pid . /etc/rc.d/init.d/functions BAMBOO_HOME=/data/Bamboo BAMBOO_INSTALL=/opt/Bamboo BAMBOO_USER=DB_Collaboration export BAMBOO_HOME NAME=bamboo BPID=${BAMBOO_INSTALL}/bamboo.pid PID=/var/run/${NAME}.pid cd ${BAMBOO_INSTALL} if [ _$1 = _condrestart ]; then su - ${BAMBOO_USER} -c " cd ${BAMBOO_INSTALL} && ${BAMBOO_INSTALL}/bamboo.sh stop && ${BAMBOO_INSTALL}/bamboo.sh start " else su - ${BAMBOO_USER} -c " cd ${BAMBOO_INSTALL} && ${BAMBOO_INSTALL}/bamboo.sh $@ " fi RC=$? if [ -f $BPID ]; then cp -- $BPID $PID touch /var/lock/subsys/${NAME} else rm -- $PID /var/lock/subsys/${NAME} 2>/dev/null fi exit $RC {noformat} # I made it executable by all and changed the ownership to root:root # I then ran the following to configure it to start: {noformat} sudo /sbin/chkconfig --add bamboo sudo /sbin/chkconfig bamboo on sudo /sbin/service bamboo start {noformat}]]> 16220193 2195814 "Downloads">"2.1 Releases">"2.1.1" # I then clicked on alfresco-enterprise-tomcat-2.1.1.zip to download the zip file. # Went to [http://customers.alfresco.com] (I was still logged in) # Went to "Company Home">"Downloads">"2.1 Releases">"2.1.1">"License Files" # I went ahead and downloaded all the "*.lic" files, but I think I only need enterprise-network-customer-unlimited.lic" # Logged out of Alfresco. # Since I suspect I will need a JDBC driver for SQLServer, I downloaded the jTDS-1.2.2 driver from the jtds web site (just Google jtds and go to the download section of the top google return). # I closed the Firefox browser. # I extracted the jtds-1.2.2.jar file from the jtds download # I downloaded and installed the JRockit 6 R27.4 JDK Microsoft Windows (x86 - 32 bit) from BEA's web site {note} After installing JRockit, make sure you set the JAVA_HOME environment variable to point to the installation of JRockit. For example, I went to the desktop, right clicked on the computer, did Properties, then clicked on the Advanced tab, then click on the environment variables button and then created a new system variable named JAVA_HOME and set to c:\bin\Java\jrockit-R27.4.0-jdk1.6.0_02 {note} # I ran the installer, changed the "Program Files" to "bin" in the installation directory for both the JDK and the JRE. I also chose to install the JRE as public. # Using Firefox, I downloaded the PHP 5.2.5 Windows Installer from php.net and installed it. Although I installed it, I did not integrate it with a web server as I want Alfresco to take port 80. I probably did not need to install PHP, but I thought I would anyway. (again, I changed install path from "Program Files" to "bin" # I also downloaded and installed OpenOffice and ran it once so I could get through the initial startup # I setup a Alfresco database on the server Solstice and granted the LAGOON\DB_Collaboration account to be the db_owner of the Alfresco database. # I unzipped the alfresco tomcat zip file to an alfresco directory in c:\bin # I then went to the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions directory for the customization of the server. ## I edited the custom-repository.properties file ### Changed the dir.root and dir.indexes to look like: {noformat} dir.root=//tornado.shore.mbari.org/Alfresco/alf_data dir.indexes=d:/alf_data/lucene-indexes {noformat} ### Commented out the db.* lines for the HSQL Connection (db.driver and db.url) ### Uncommented the db.* lines for MSSQL and changed to use the jTDS driver. They should look like: {noformat} db.driver=net.sourceforge.jtds.jdbc.Driver db.url=jdbc:jtds:sqlserver://solstice.shore.mbari.org/Alfresco;domain=SHORE;user=DB_Collaboration;password=XXXXXXXXX {noformat} ### I also added the following section to override the mail server settings {noformat} # Mail server configuration mail.host=mail.mbari.org mail.port=25 mail.username= mail.password= {noformat} ## Edited the custom-hibernate-dialect.properties file ### Commented out the HSQL Dialect ### Uncommented the MSSQL Dialect # I then installed the jtds-1.2.2.jar in the c:\bin\alfresco\tomcat\common\lib so that it will be on the classpath when Alfresco is started # Now this is not necessarily fun, but in order to really get it configured the way we want it, you need to pull the original .war file out, edit some stuff inside and re-create the .war. {note} This should all be done before starting Alfresco for the first time. {note} # Copy the c:\Alfresco\tomcat\webapps\alfresco.war file to your home directory. # Make a second copy so that you will always the original (I copied to alfresco.war.orig and moved it somewhere else. It is important to move it and have only the alfresco.war file in the directory because when you un-jar it, all the files go right where alfresco.war is.) # From a command line, un-jar the war file using: {noformat} jar -xvf alfresco.war {noformat} # This unpacks a lot of files and after it completes, move (or delete) the alfresco.war file from the directory. This needs to be done so it does not end up in the new .war file. # I wanted to change the "Company Home" that seems to be everywhere to something that says MBARI. ## Edited ./WEB-INF/classes/alfresco/messages/webclient.properties and changed company_home from 'Company Home' to 'MBARI' ## Edited ./WEB-INF/classes/alfresco/messages/webclient_en_US.properties and changed company_home from 'Company Home' to 'MBARI' ## I edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces.properties and changed the first two lines to read {noformat} spaces.company_home.name=MBARI spaces.company_home.description=The root space for MBARI {noformat} ## Edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces_en_US.properties and made the same changes as the previous step {tip} This took a bit to find all these, and to be honest, I am not sure which one actually made the change on the GUI, but I suspect it was the _en_US ones. {tip} # When users are imported via LDAP, user spaces get created automatically. In order to put them where I wanted them to go (instead of right in the Company Home), I edited the ./WEB-INF/classes/alfresco/authentication-services-context.xml file. In the file there is a bean with an name of personalHomeFolderProvider. There is a property name 'path' and I added {noformat} /${spaces.user_homes.childname} {noformat} to the end to try to get them to create the user spaces there instead of in the Company Home. The final bean XML looks like: {noformat} /${spaces.company_home.childname}/${spaces.user_homes.childname} ${spaces.store} false All All {noformat} # I wanted to change the logo that is used. I attached the replacement logo [here|^AlfrescoLogo32.png]. Copy this to ./images/logo and overwrite the one that is there. # In order to setup SSL for the application (will do that later), edit ./WEB-INF/web.xml and add the following {noformat} Login Pages /* CONFIDENTIAL {noformat} right before the ending tag at the bottom of the file. # Now in order to change the default behavior so that all content is versioned from the start, I edited the .\WEB-INF\classes\alfresco\model\contentModel.xml and searched for the content type definition block. {noformat} Content cm:cmobject true d:content false true false true {noformat} and added the following block right before the ending tag: {noformat} cm:versionable {noformat} so the final block looks like: {noformat} Content cm:cmobject true d:content false true false true cm:versionable {noformat} # That takes care of all the changes to the WAR file. We can now put it back into .war form. # While you are in the directory you expanded the war file in, run ## jar cvfm alfresco.war META-INF\MANIFEST.MF . # You should now have an alfresco.war file in the directory. Move that back to the alfresco install and overwrite the existing one. # Most users like the details view, so I set the default to that by editing c:\Alfresco\tomcat\shared\classes\alfresco\extensions/web-client-config-custom.xml and added: {noformat} details 20
20
20 {noformat} right before the closing tag. # Now in order to use MBARI accounts, I needed to configure LDAP. # I downloade this [ldap-authentication-context.xml|^ldap-authentication-context.xml] file and put it in the c:\Alfresco\tomcat\shared\classes\alfresco\extensions folder. # We wanted to be able to make sure we could have collaborator accounts that were not MBARI LDAP accounts so that we could have Alfresco users that had not permissions at all on the MBARI network. In order to do this, I used the Alfresco native user service and chained the authentication together with the MBARI LDAP. In order to do this, I downloaded this [chaining-authentication-context.xml|^chaining-authentication-context.xml] file and installed in c:\Alfresco\tomcat\shared\classes\alfresco\extensions. # In order to grant certain accounts admin privs, I created a new custom-authority-services-context.xml in the same directory as the ldap-authentication-context.xml file and added {noformat} kgomes admin administrator {noformat} # In order for Alfresco to handle all port 80 traffic, I changed Tomcat so that it takes port 80 and SSL goes over port 443. So I edited the c:\Alfresco\tomcat\conf\server.xml file and changed the 8080 port to 80 and the 8443 port to 443 (the 443 change is done in two places). # I copied the enterprise-network-unlimited.lic file into the c:\Alfresco\tomcat\shared\classes\alfresco\extensions\license directory # Just to keep things clean, I edited the c:\bin\alfresco\alfresco.bat file and put 'rem' in front of the second JAVA_OPTS set as I am using Java 6. # Now after you run it for the first time and the database structure gets created, you can't restart it because you get: {noformat} java.sql.SQLException: Column names in each table must be unique. Column name 'ID_' in table 'JBPM_ACTION' is specified more than once. {noformat} Sigh, so in order to keep Alfresco from hurting itself, I had to turn off the schema updates. This is done by editing the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions\custom-repository.properties and adding the following: {noformat} db.schema.update=false {noformat} and then restarting alfresco. ]]> 2163050 19071814 19039055 2195813 "Downloads">"2.1 Releases">"2.1.1" # I then clicked on alfresco-enterprise-tomcat-2.1.1.zip to download the zip file. # Went to [http://customers.alfresco.com] (I was still logged in) # Went to "Company Home">"Downloads">"2.1 Releases">"2.1.1">"License Files" # I went ahead and downloaded all the "*.lic" files, but I think I only need enterprise-network-customer-unlimited.lic" # Logged out of Alfresco. # Since I suspect I will need a JDBC driver for SQLServer, I downloaded the jTDS-1.2.2 driver from the jtds web site (just Google jtds and go to the download section of the top google return). # I closed the Firefox browser. # I extracted the jtds-1.2.2.jar file from the jtds download # I downloaded and installed the JRockit 6 R27.4 JDK Microsoft Windows (x86 - 32 bit) from BEA's web site {note} After installing JRockit, make sure you set the JAVA_HOME environment variable to point to the installation of JRockit. For example, I went to the desktop, right clicked on the computer, did Properties, then clicked on the Advanced tab, then click on the environment variables button and then created a new system variable named JAVA_HOME and set to c:\bin\Java\jrockit-R27.4.0-jdk1.6.0_02 {note} # I ran the installer, changed the "Program Files" to "bin" in the installation directory for both the JDK and the JRE. I also chose to install the JRE as public. # Using Firefox, I downloaded the PHP 5.2.5 Windows Installer from php.net and installed it. Although I installed it, I did not integrate it with a web server as I want Alfresco to take port 80. I probably did not need to install PHP, but I thought I would anyway. (again, I changed install path from "Program Files" to "bin" # I also downloaded and installed OpenOffice and ran it once so I could get through the initial startup # I setup a Alfresco database on the server Solstice and granted the LAGOON\DB_Collaboration account to be the db_owner of the Alfresco database. # I unzipped the alfresco tomcat zip file to an alfresco directory in c:\bin # I then went to the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions directory for the customization of the server. ## I edited the custom-repository.properties file ### Changed the dir.root and dir.indexes to look like: {noformat} dir.root=//tornado.shore.mbari.org/Alfresco/alf_data dir.indexes=d:/alf_data/lucene-indexes {noformat} ### Commented out the db.* lines for the HSQL Connection (db.driver and db.url) ### Uncommented the db.* lines for MSSQL and changed to use the jTDS driver. They should look like: {noformat} db.driver=net.sourceforge.jtds.jdbc.Driver db.url=jdbc:jtds:sqlserver://solstice.shore.mbari.org/Alfresco;domain=SHORE;user=DB_Collaboration;password=XXXXXXXXX {noformat} ### I also added the following section to override the mail server settings {noformat} # Mail server configuration mail.host=mail.mbari.org mail.port=25 mail.username= mail.password= {noformat} ## Edited the custom-hibernate-dialect.properties file ### Commented out the HSQL Dialect ### Uncommented the MSSQL Dialect # I then installed the jtds-1.2.2.jar in the c:\bin\alfresco\tomcat\common\lib so that it will be on the classpath when Alfresco is started # Now this is not necessarily fun, but in order to really get it configured the way we want it, you need to pull the original .war file out, edit some stuff inside and re-create the .war. {note} This should all be done before starting Alfresco for the first time. {note} # Copy the c:\Alfresco\tomcat\webapps\alfresco.war file to your home directory. # Make a second copy so that you will always the original (I copied to alfresco.war.orig and moved it somewhere else. It is important to move it and have only the alfresco.war file in the directory because when you un-jar it, all the files go right where alfresco.war is.) # From a command line, un-jar the war file using: {noformat} jar -xvf alfresco.war {noformat} # This unpacks a lot of files and after it completes, move (or delete) the alfresco.war file from the directory. This needs to be done so it does not end up in the new .war file. # I wanted to change the "Company Home" that seems to be everywhere to something that says MBARI. ## Edited ./WEB-INF/classes/alfresco/messages/webclient.properties and changed company_home from 'Company Home' to 'MBARI' ## Edited ./WEB-INF/classes/alfresco/messages/webclient_en_US.properties and changed company_home from 'Company Home' to 'MBARI' ## I edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces.properties and changed the first two lines to read {noformat} spaces.company_home.name=MBARI spaces.company_home.description=The root space for MBARI {noformat} ## Edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces_en_US.properties and made the same changes as the previous step {tip} This took a bit to find all these, and to be honest, I am not sure which one actually made the change on the GUI, but I suspect it was the _en_US ones. {tip} # When users are imported via LDAP, user spaces get created automatically. In order to put them where I wanted them to go (instead of right in the Company Home), I edited the ./WEB-INF/classes/alfresco/authentication-services-context.xml file. In the file there is a bean with an name of personalHomeFolderProvider. There is a property name 'path' and I added {noformat} /${spaces.user_homes.childname} {noformat} to the end to try to get them to create the user spaces there instead of in the Company Home. The final bean XML looks like: {noformat} /${spaces.company_home.childname}/${spaces.user_homes.childname} ${spaces.store} false All All {noformat} # I wanted to change the logo that is used. I attached the replacement logo [here|^AlfrescoLogo32.png]. Copy this to ./images/logo and overwrite the one that is there. # In order to setup SSL for the application (will do that later), edit ./WEB-INF/web.xml and add the following {noformat} Login Pages /* CONFIDENTIAL {noformat} right before the ending tag at the bottom of the file. # Now in order to change the default behavior so that all content is versioned from the start, I edited the .\WEB-INF\classes\alfresco\model\contentModel.xml and searched for the content type definition block. {noformat} Content cm:cmobject true d:content false true false true {noformat} and added the following block right before the ending tag: {noformat} cm:versionable {noformat} so the final block looks like: {noformat} Content cm:cmobject true d:content false true false true cm:versionable {noformat} # That takes care of all the changes to the WAR file. We can now put it back into .war form. # While you are in the directory you expanded the war file in, run ## jar cvfm alfresco.war META-INF\MANIFEST.MF . # You should now have an alfresco.war file in the directory. Move that back to the alfresco install and overwrite the existing one. # Most users like the details view, so I set the default to that by editing c:\Alfresco\tomcat\shared\classes\alfresco\extensions/web-client-config-custom.xml and added: {noformat} details 20
20
20 {noformat} right before the closing tag. # Now in order to use MBARI accounts, I needed to configure LDAP. # I downloade this [ldap-authentication-context.xml|^ldap-authentication-context.xml] file and put it in the c:\Alfresco\tomcat\shared\classes\alfresco\extensions folder. # We wanted to be able to make sure we could have collaborator accounts that were not MBARI LDAP accounts so that we could have Alfresco users that had not permissions at all on the MBARI network. In order to do this, I used the Alfresco native user service and chained the authentication together with the MBARI LDAP. In order to do this, I downloaded this [chaining-authentication-context.xml|^chaining-authentication-context.xml] file and installed in c:\Alfresco\tomcat\shared\classes\alfresco\extensions. # In order to grant certain accounts admin privs, I created a new custom-authority-services-context.xml in the same directory as the ldap-authentication-context.xml file and added {noformat} kgomes admin administrator {noformat} # In order for Alfresco to handle all port 80 traffic, I changed Tomcat so that it takes port 80 and SSL goes over port 443. So I edited the c:\Alfresco\tomcat\conf\server.xml file and changed the 8080 port to 80 and the 8443 port to 443 (the 443 change is done in two places). # I copied the enterprise-network-unlimited.lic file into the c:\Alfresco\tomcat\shared\classes\alfresco\extensions\license directory # Just to keep things clean, I edited the c:\bin\alfresco\alfresco.bat file and put 'rem' in front of the second JAVA_OPTS set as I am using Java 6. ]]> 2163049 19071813 19039054 2195812 "Downloads">"2.1 Releases">"2.1.1" # I then clicked on alfresco-enterprise-tomcat-2.1.1.zip to download the zip file. # Went to [http://customers.alfresco.com] (I was still logged in) # Went to "Company Home">"Downloads">"2.1 Releases">"2.1.1">"License Files" # I went ahead and downloaded all the "*.lic" files, but I think I only need enterprise-network-customer-unlimited.lic" # Logged out of Alfresco. # Since I suspect I will need a JDBC driver for SQLServer, I downloaded the jTDS-1.2.2 driver from the jtds web site (just Google jtds and go to the download section of the top google return). # I closed the Firefox browser. # I extracted the jtds-1.2.2.jar file from the jtds download # I downloaded and installed the JRockit 6 R27.4 JDK Microsoft Windows (x86 - 32 bit) from BEA's web site {note} After installing JRockit, make sure you set the JAVA_HOME environment variable to point to the installation of JRockit. For example, I went to the desktop, right clicked on the computer, did Properties, then clicked on the Advanced tab, then click on the environment variables button and then created a new system variable named JAVA_HOME and set to c:\bin\Java\jrockit-R27.4.0-jdk1.6.0_02 {note} # I ran the installer, changed the "Program Files" to "bin" in the installation directory for both the JDK and the JRE. I also chose to install the JRE as public. # Using Firefox, I downloaded the PHP 5.2.5 Windows Installer from php.net and installed it. Although I installed it, I did not integrate it with a web server as I want Alfresco to take port 80. I probably did not need to install PHP, but I thought I would anyway. (again, I changed install path from "Program Files" to "bin" # I also downloaded and installed OpenOffice and ran it once so I could get through the initial startup # I setup a Alfresco database on the server Solstice and granted the LAGOON\DB_Collaboration account to be the db_owner of the Alfresco database. # I unzipped the alfresco tomcat zip file to an alfresco directory in c:\bin # I then went to the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions directory for the customization of the server. ## I edited the custom-repository.properties file ### Changed the dir.root and dir.indexes to look like: {noformat} dir.root=//tornado.shore.mbari.org/Alfresco/alf_data dir.indexes=d:/alf_data/lucene-indexes {noformat} ### Commented out the db.* lines for the HSQL Connection (db.driver and db.url) ### Uncommented the db.* lines for MSSQL and changed to use the jTDS driver. They should look like: {noformat} db.driver=net.sourceforge.jtds.jdbc.Driver db.url=jdbc:jtds:sqlserver://solstice.shore.mbari.org/Alfresco;domain=SHORE;user=DB_Collaboration;password=XXXXXXXXX {noformat} ### I also added the following section to override the mail server settings {noformat} # Mail server configuration mail.host=mail.mbari.org mail.port=25 mail.username= mail.password= {noformat} ## Edited the custom-hibernate-dialect.properties file ### Commented out the HSQL Dialect ### Uncommented the MSSQL Dialect # I then installed the jtds-1.2.2.jar in the c:\bin\alfresco\tomcat\common\lib so that it will be on the classpath when Alfresco is started # Now this is not necessarily fun, but in order to really get it configured the way we want it, you need to pull the original .war file out, edit some stuff inside and re-create the .war. {note} This should all be done before starting Alfresco for the first time. {note} # Copy the c:\Alfresco\tomcat\webapps\alfresco.war file to your home directory. # Make a second copy so that you will always the original (I copied to alfresco.war.orig and moved it somewhere else. It is important to move it and have only the alfresco.war file in the directory because when you un-jar it, all the files go right where alfresco.war is.) # From a command line, un-jar the war file using: {noformat} jar -xvf alfresco.war {noformat} # This unpacks a lot of files and after it completes, move (or delete) the alfresco.war file from the directory. This needs to be done so it does not end up in the new .war file. # I wanted to change the "Company Home" that seems to be everywhere to something that says MBARI. ## Edited ./WEB-INF/classes/alfresco/messages/webclient.properties and changed company_home from 'Company Home' to 'MBARI' ## Edited ./WEB-INF/classes/alfresco/messages/webclient_en_US.properties and changed company_home from 'Company Home' to 'MBARI' ## I edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces.properties and changed the first two lines to read {noformat} spaces.company_home.name=MBARI spaces.company_home.description=The root space for MBARI {noformat} ## Edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces_en_US.properties and made the same changes as the previous step {tip} This took a bit to find all these, and to be honest, I am not sure which one actually made the change on the GUI, but I suspect it was the _en_US ones. {tip} # When users are imported via LDAP, user spaces get created automatically. In order to put them where I wanted them to go (instead of right in the Company Home), I edited the ./WEB-INF/classes/alfresco/authentication-services-context.xml file. In the file there is a bean with an name of personalHomeFolderProvider. There is a property name 'path' and I added {noformat} /${spaces.user_homes.childname} {noformat} to the end to try to get them to create the user spaces there instead of in the Company Home. The final bean XML looks like: {noformat} /${spaces.company_home.childname}/${spaces.user_homes.childname} ${spaces.store} false All All {noformat} # I wanted to change the logo that is used. I attached the replacement logo [here|^AlfrescoLogo32.png]. Copy this to ./images/logo and overwrite the one that is there. # In order to setup SSL for the application (will do that later), edit ./WEB-INF/web.xml and add the following {noformat} Login Pages /* CONFIDENTIAL {noformat} right before the ending tag at the bottom of the file. # Now in order to change the default behavior so that all content is versioned from the start, I edited the .\WEB-INF\classes\alfresco\model\contentModel.xml and searched for the content type definition block. {noformat} Content cm:cmobject true d:content false true false true {noformat} and added the following block right before the ending tag: {noformat} cm:versionable {noformat} so the final block looks like: {noformat} Content cm:cmobject true d:content false true false true cm:versionable {noformat} # That takes care of all the changes to the WAR file. We can now put it back into .war form. # While you are in the directory you expanded the war file in, run ## jar cvfm alfresco.war META-INF\MANIFEST.MF . # You should now have an alfresco.war file in the directory. Move that back to the alfresco install and overwrite the existing one. # Most users like the details view, so I set the default to that by editing c:\Alfresco\tomcat\shared\classes\alfresco\extensions/web-client-config-custom.xml and added: {noformat} details 20
20
20 {noformat} right before the closing tag. # Now in order to use MBARI accounts, I needed to configure LDAP. # I downloade this [ldap-authentication-context.xml|^ldap-authentication-context.xml] file and put it in the c:\Alfresco\tomcat\shared\classes\alfresco\extensions folder. # We wanted to be able to make sure we could have collaborator accounts that were not MBARI LDAP accounts so that we could have Alfresco users that had not permissions at all on the MBARI network. In order to do this, I used the Alfresco native user service and chained the authentication together with the MBARI LDAP. In order to do this, I downloaded this [chaining-authentication-context.xml|^chaining-authentication-context.xml] file and installed in c:\Alfresco\tomcat\shared\classes\alfresco\extensions. # In order to grant certain accounts admin privs, I created a new custom-authority-services-context.xml in the same directory as the ldap-authentication-context.xml file and added {noformat} kgomes admin administrator {noformat} # In order for Alfresco to handle all port 80 traffic, I changed Tomcat so that it takes port 80 and SSL goes over port 443. So I edited the c:\Alfresco\tomcat\conf\server.xml file and changed the 8080 port to 80 and the 8443 port to 443 (the 443 change is done in two places). # I copied the enterprise-network-unlimited.lic file into the c:\Alfresco\tomcat\shared\classes\alfresco\extensions\license directory]]> 2163048 19071811 19039052 14221436 14188670 2195816 "Downloads">"2.1 Releases">"2.1.1" # I then clicked on alfresco-enterprise-tomcat-2.1.1.zip to download the zip file. # Went to [http://customers.alfresco.com] (I was still logged in) # Went to "Company Home">"Downloads">"2.1 Releases">"2.1.1">"License Files" # I went ahead and downloaded all the "*.lic" files, but I think I only need enterprise-network-customer-unlimited.lic" # Logged out of Alfresco. # Since I suspect I will need a JDBC driver for SQLServer, I downloaded the jTDS-1.2.2 driver from the jtds web site (just Google jtds and go to the download section of the top google return). # I closed the Firefox browser. # I extracted the jtds-1.2.2.jar file from the jtds download # I downloaded and installed the JRockit 6 R27.4 JDK Microsoft Windows (x86 - 32 bit) from BEA's web site {note} After installing JRockit, make sure you set the JAVA_HOME environment variable to point to the installation of JRockit. For example, I went to the desktop, right clicked on the computer, did Properties, then clicked on the Advanced tab, then click on the environment variables button and then created a new system variable named JAVA_HOME and set to c:\bin\Java\jrockit-R27.4.0-jdk1.6.0_02 {note} # I ran the installer, changed the "Program Files" to "bin" in the installation directory for both the JDK and the JRE. I also chose to install the JRE as public. # Using Firefox, I downloaded the PHP 5.2.5 Windows Installer from php.net and installed it. Although I installed it, I did not integrate it with a web server as I want Alfresco to take port 80. I probably did not need to install PHP, but I thought I would anyway. (again, I changed install path from "Program Files" to "bin" # I also downloaded and installed OpenOffice and ran it once so I could get through the initial startup # I setup a Alfresco database on the server Solstice and granted the LAGOON\DB_Collaboration account to be the db_owner of the Alfresco database. # I unzipped the alfresco tomcat zip file to an alfresco directory in c:\bin # I then went to the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions directory for the customization of the server. ## I edited the custom-repository.properties file ### Changed the dir.root and dir.indexes to look like: {noformat} dir.root=//tornado.shore.mbari.org/Alfresco/alf_data dir.indexes=d:/alf_data/lucene-indexes {noformat} ### Commented out the db.* lines for the HSQL Connection (db.driver and db.url) ### Uncommented the db.* lines for MSSQL and changed to use the jTDS driver. They should look like: {noformat} db.driver=net.sourceforge.jtds.jdbc.Driver db.url=jdbc:jtds:sqlserver://solstice.shore.mbari.org/Alfresco;domain=SHORE;user=DB_Collaboration;password=XXXXXXXXX {noformat} ### I also added the following section to override the mail server settings {noformat} # Mail server configuration mail.host=mail.mbari.org mail.port=25 mail.username= mail.password= {noformat} ## Edited the custom-hibernate-dialect.properties file ### Commented out the HSQL Dialect ### Uncommented the MSSQL Dialect # I then installed the jtds-1.2.2.jar in the c:\bin\alfresco\tomcat\common\lib so that it will be on the classpath when Alfresco is started # Now this is not necessarily fun, but in order to really get it configured the way we want it, you need to pull the original .war file out, edit some stuff inside and re-create the .war. {note} This should all be done before starting Alfresco for the first time. {note} # Copy the c:\Alfresco\tomcat\webapps\alfresco.war file to your home directory. # Make a second copy so that you will always the original (I copied to alfresco.war.orig and moved it somewhere else. It is important to move it and have only the alfresco.war file in the directory because when you un-jar it, all the files go right where alfresco.war is.) # From a command line, un-jar the war file using: {noformat} jar -xvf alfresco.war {noformat} # This unpacks a lot of files and after it completes, move (or delete) the alfresco.war file from the directory. This needs to be done so it does not end up in the new .war file. # I wanted to change the "Company Home" that seems to be everywhere to something that says MBARI. ## Edited ./WEB-INF/classes/alfresco/messages/webclient.properties and changed company_home from 'Company Home' to 'MBARI' ## Edited ./WEB-INF/classes/alfresco/messages/webclient_en_US.properties and changed company_home from 'Company Home' to 'MBARI' ## I edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces.properties and changed the first two lines to read {noformat} spaces.company_home.name=MBARI spaces.company_home.description=The root space for MBARI {noformat} ## Edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces_en_US.properties and made the same changes as the previous step {tip} This took a bit to find all these, and to be honest, I am not sure which one actually made the change on the GUI, but I suspect it was the _en_US ones. {tip} # When users are imported via LDAP, user spaces get created automatically. In order to put them where I wanted them to go (instead of right in the Company Home), I edited the ./WEB-INF/classes/alfresco/authentication-services-context.xml file. In the file there is a bean with an name of personalHomeFolderProvider. There is a property name 'path' and I added {noformat} /${spaces.user_homes.childname} {noformat} to the end to try to get them to create the user spaces there instead of in the Company Home. The final bean XML looks like: {noformat} /${spaces.company_home.childname}/${spaces.user_homes.childname} ${spaces.store} false All All {noformat} # I wanted to change the logo that is used. I attached the replacement logo [here|^AlfrescoLogo32.png]. Copy this to ./images/logo and overwrite the one that is there. # In order to setup SSL for the application (will do that later), edit ./WEB-INF/web.xml and add the following {noformat} Login Pages /* CONFIDENTIAL {noformat} right before the ending tag at the bottom of the file. # Now in order to change the default behavior so that all content is versioned from the start, I edited the .\WEB-INF\classes\alfresco\model\contentModel.xml and searched for the content type definition block. {noformat} Content cm:cmobject true d:content false true false true {noformat} and added the following block right before the ending tag: {noformat} cm:versionable {noformat} so the final block looks like: {noformat} Content cm:cmobject true d:content false true false true cm:versionable {noformat} # That takes care of all the changes to the WAR file. We can now put it back into .war form. # While you are in the directory you expanded the war file in, run ## jar cvfm alfresco.war META-INF\MANIFEST.MF . # You should now have an alfresco.war file in the directory. Move that back to the alfresco install and overwrite the existing one. # Most users like the details view, so I set the default to that by editing c:\Alfresco\tomcat\shared\classes\alfresco\extensions/web-client-config-custom.xml and added: {noformat} details 20
20
20 {noformat} right before the closing tag. # Now in order to use MBARI accounts, I needed to configure LDAP. # I downloade this [ldap-authentication-context.xml|^ldap-authentication-context.xml] file and put it in the c:\Alfresco\tomcat\shared\classes\alfresco\extensions folder. # We wanted to be able to make sure we could have collaborator accounts that were not MBARI LDAP accounts so that we could have Alfresco users that had not permissions at all on the MBARI network. In order to do this, I used the Alfresco native user service and chained the authentication together with the MBARI LDAP. In order to do this, I downloaded this [chaining-authentication-context.xml|^chaining-authentication-context.xml] file and installed in c:\Alfresco\tomcat\shared\classes\alfresco\extensions. # In order to grant certain accounts admin privs, I created a new custom-authority-services-context.xml in the same directory as the ldap-authentication-context.xml file and added {noformat} kgomes admin administrator {noformat} # In order for Alfresco to handle all port 80 traffic, I changed Tomcat so that it takes port 80 and SSL goes over port 443. So I edited the c:\Alfresco\tomcat\conf\server.xml file and changed the 8080 port to 80 and the 8443 port to 443 (the 443 change is done in two places). # I copied the enterprise-network-unlimited.lic file into the c:\Alfresco\tomcat\shared\classes\alfresco\extensions\license directory # Just to keep things clean, I edited the c:\bin\alfresco\alfresco.bat file and put 'rem' in front of the second JAVA_OPTS set as I am using Java 6. # Now after you run it for the first time and the database structure gets created, you can't restart it because you get: {noformat} java.sql.SQLException: Column names in each table must be unique. Column name 'ID_' in table 'JBPM_ACTION' is specified more than once. {noformat} Sigh, so in order to keep Alfresco from hurting itself, I had to turn off the schema updates. This is done by editing the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions\custom-repository.properties and adding the following: {noformat} db.schema.update=false {noformat} and then restarting alfresco. # To install Alfresco as a Windows Service use a command prompt and enter the following: {noformat} cd c:\bin\alfresco\tomcat\bin service.bat install alfresco tomcat5.exe //US//alfresco --DisplayName "Alfresco Server" tomcat5.exe //US//alfresco --JvmMs=512 --JvmMx=1024 --JvmSs=64 tomcat5.exe //US//alfresco --JavaHome=c:/bin/Java/jrockit-R27.4.0-jdk1.6.0_02 tomcat5.exe //US//alfresco --Environment ALF_HOME=c:/bin/alfresco/ tomcat5.exe //US//alfresco --Environment PATH=c:/bin/alfresco/bin;%PATH% tomcat5.exe //US//alfresco --StartPath c:/bin/alfresco --Startup auto {noformat} # To uninstall the service, at a later time, do the following: {noformat} cd c:\bin\alfresco\tomcat\bin service.bat uninstall alfresco {noformat} # To edit your service settings at any time: {noformat} cd c:\alfresco\tomcat\bin tomcat5w.exe //ES//alfresco {noformat} # Finally, to start the service, just go into your Windows Service control panel and locate the service that is now named 'Alfresco Server'. You can start and stop Alfresco from this control panel. ]]> 2163052 24084797 24052036 2195831 "Downloads">"2.1 Releases">"2.1.1" # I then clicked on alfresco-enterprise-tomcat-2.1.1.zip to download the zip file. # Went to [http://customers.alfresco.com] (I was still logged in) # Went to "Company Home">"Downloads">"2.1 Releases">"2.1.1">"License Files" # I went ahead and downloaded all the "*.lic" files, but I think I only need enterprise-network-customer-unlimited.lic" # Logged out of Alfresco. # Since I suspect I will need a JDBC driver for SQLServer, I downloaded the jTDS-1.2.2 driver from the jtds web site (just Google jtds and go to the download section of the top google return). # I closed the Firefox browser. # I extracted the jtds-1.2.2.jar file from the jtds download # I downloaded and installed the JRockit 6 R27.4 JDK Microsoft Windows (x86 - 32 bit) from BEA's web site {note} After installing JRockit, make sure you set the JAVA_HOME environment variable to point to the installation of JRockit. For example, I went to the desktop, right clicked on the computer, did Properties, then clicked on the Advanced tab, then click on the environment variables button and then created a new system variable named JAVA_HOME and set to c:\bin\Java\jrockit-R27.4.0-jdk1.6.0_02 {note} # I ran the installer, changed the "Program Files" to "bin" in the installation directory for both the JDK and the JRE. I also chose to install the JRE as public. # Using Firefox, I downloaded the PHP 5.2.5 Windows Installer from php.net and installed it. Although I installed it, I did not integrate it with a web server as I want Alfresco to take port 80. I probably did not need to install PHP, but I thought I would anyway. (again, I changed install path from "Program Files" to "bin" # I also downloaded and installed OpenOffice and ran it once so I could get through the initial startup # I setup a Alfresco database on the server Solstice and granted the LAGOON\DB_Collaboration account to be the db_owner of the Alfresco database. # I unzipped the alfresco tomcat zip file to an alfresco directory in c:\bin # I then went to the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions directory for the customization of the server. ## I edited the custom-repository.properties file ### Changed the dir.root and dir.indexes to look like: {noformat} dir.root=//tornado.shore.mbari.org/Alfresco/alf_data dir.indexes=d:/alf_data/lucene-indexes {noformat} ### Commented out the db.* lines for the HSQL Connection (db.driver and db.url) ### Uncommented the db.* lines for MSSQL and changed to use the jTDS driver. They should look like: {noformat} db.driver=net.sourceforge.jtds.jdbc.Driver db.url=jdbc:jtds:sqlserver://solstice.shore.mbari.org/Alfresco;domain=SHORE;user=DB_Collaboration;password=XXXXXXXXX {noformat} ### I also added the following section to override the mail server settings {noformat} # Mail server configuration mail.host=mail.mbari.org mail.port=25 mail.username= mail.password= {noformat} ## Edited the custom-hibernate-dialect.properties file ### Commented out the HSQL Dialect ### Uncommented the MSSQL Dialect # I then installed the jtds-1.2.2.jar in the c:\bin\alfresco\tomcat\common\lib so that it will be on the classpath when Alfresco is started # Now this is not necessarily fun, but in order to really get it configured the way we want it, you need to pull the original .war file out, edit some stuff inside and re-create the .war. {note} This should all be done before starting Alfresco for the first time. {note} # Copy the c:\Alfresco\tomcat\webapps\alfresco.war file to your home directory. # Make a second copy so that you will always the original (I copied to alfresco.war.orig and moved it somewhere else. It is important to move it and have only the alfresco.war file in the directory because when you un-jar it, all the files go right where alfresco.war is.) # From a command line, un-jar the war file using: {noformat} jar -xvf alfresco.war {noformat} # This unpacks a lot of files and after it completes, move (or delete) the alfresco.war file from the directory. This needs to be done so it does not end up in the new .war file. # I wanted to change the "Company Home" that seems to be everywhere to something that says MBARI. ## Edited ./WEB-INF/classes/alfresco/messages/webclient.properties and changed company_home from 'Company Home' to 'MBARI' ## Edited ./WEB-INF/classes/alfresco/messages/webclient_en_US.properties and changed company_home from 'Company Home' to 'MBARI' ## I edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces.properties and changed the first two lines to read {noformat} spaces.company_home.name=MBARI spaces.company_home.description=The root space for MBARI {noformat} ## Edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces_en_US.properties and made the same changes as the previous step {tip} This took a bit to find all these, and to be honest, I am not sure which one actually made the change on the GUI, but I suspect it was the _en_US ones. {tip} # When users are imported via LDAP, user spaces get created automatically. In order to put them where I wanted them to go (instead of right in the Company Home), I edited the ./WEB-INF/classes/alfresco/authentication-services-context.xml file. In the file there is a bean with an name of personalHomeFolderProvider. There is a property name 'path' and I added {noformat} /${spaces.user_homes.childname} {noformat} to the end to try to get them to create the user spaces there instead of in the Company Home. The final bean XML looks like: {noformat} /${spaces.company_home.childname}/${spaces.user_homes.childname} ${spaces.store} false All All {noformat} # I wanted to change the logo that is used. I attached the replacement logo [here|^AlfrescoLogo32.png]. Copy this to ./images/logo and overwrite the one that is there. # In order to setup SSL for the application (will do that later), edit ./WEB-INF/web.xml and add the following {noformat} Login Pages /* CONFIDENTIAL {noformat} right before the ending tag at the bottom of the file. # Now in order to change the default behavior so that all content is versioned from the start, I edited the .\WEB-INF\classes\alfresco\model\contentModel.xml and searched for the content type definition block. {noformat} Content cm:cmobject true d:content false true false true {noformat} and added the following block right before the ending tag: {noformat} cm:versionable {noformat} so the final block looks like: {noformat} Content cm:cmobject true d:content false true false true cm:versionable {noformat} # That takes care of all the changes to the WAR file. We can now put it back into .war form. # While you are in the directory you expanded the war file in, run ## jar cvfm alfresco.war META-INF\MANIFEST.MF . # You should now have an alfresco.war file in the directory. Move that back to the alfresco install and overwrite the existing one. # Most users like the details view, so I set the default to that by editing c:\Alfresco\tomcat\shared\classes\alfresco\extensions/web-client-config-custom.xml and added: {noformat} details 20
20
20 {noformat} right before the closing tag. # Now in order to use MBARI accounts, I needed to configure LDAP. # I downloade this [ldap-authentication-context.xml|^ldap-authentication-context.xml] file and put it in the c:\Alfresco\tomcat\shared\classes\alfresco\extensions folder. # We wanted to be able to make sure we could have collaborator accounts that were not MBARI LDAP accounts so that we could have Alfresco users that had not permissions at all on the MBARI network. In order to do this, I used the Alfresco native user service and chained the authentication together with the MBARI LDAP. In order to do this, I downloaded this [chaining-authentication-context.xml|^chaining-authentication-context.xml] file and installed in c:\Alfresco\tomcat\shared\classes\alfresco\extensions. # In order to grant certain accounts admin privs, I created a new custom-authority-services-context.xml in the same directory as the ldap-authentication-context.xml file and added {noformat} kgomes admin administrator {noformat} # In order for Alfresco to handle all port 80 traffic, I changed Tomcat so that it takes port 80 and SSL goes over port 443. So I edited the c:\Alfresco\tomcat\conf\server.xml file and changed the 8080 port to 80 and the 8443 port to 443 (the 443 change is done in two places). # I copied the enterprise-network-unlimited.lic file into the c:\Alfresco\tomcat\shared\classes\alfresco\extensions\license directory # Just to keep things clean, I edited the c:\bin\alfresco\alfresco.bat file and put 'rem' in front of the second JAVA_OPTS set as I am using Java 6. # Now after you run it for the first time and the database structure gets created, you can't restart it because you get: {noformat} java.sql.SQLException: Column names in each table must be unique. Column name 'ID_' in table 'JBPM_ACTION' is specified more than once. {noformat} Sigh, so in order to keep Alfresco from hurting itself, I had to turn off the schema updates. This is done by editing the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions\custom-repository.properties and adding the following: {noformat} db.schema.update=false {noformat} and then restarting alfresco. # To install Alfresco as a Windows Service use a command prompt and enter the following: {noformat} cd c:\bin\alfresco\tomcat\bin service.bat install alfresco tomcat5.exe //US//alfresco --DisplayName "Alfresco Server" tomcat5.exe //US//alfresco --JvmMs=512 --JvmMx=1024 --JvmSs=64 tomcat5.exe //US//alfresco --JavaHome=c:/bin/Java/jrockit-R27.4.0-jdk1.6.0_02 tomcat5.exe //US//alfresco --Environment ALF_HOME=c:/bin/alfresco/ tomcat5.exe //US//alfresco --Environment PATH=c:/bin/alfresco/bin;%PATH% tomcat5.exe //US//alfresco --StartPath c:/bin/alfresco --Startup auto {noformat} # To uninstall the service, at a later time, do the following: {noformat} cd c:\bin\alfresco\tomcat\bin service.bat uninstall alfresco {noformat} # To edit your service settings at any time: {noformat} cd c:\alfresco\tomcat\bin tomcat5w.exe //ES//alfresco {noformat} # In order to install certain modules (like the email listener), I had to get the Alfresco Module Manager from the customers.alfresco.com download site. I downloaded the alfresco-mmt-2.1.1.jar file locally so I could use it to install modules. # I then downloaded the email listener module from [http://forge.alfresco.com/projects/email-listener/]. It came as a zip file, so I unzipped it and it created a folder with the appropriate emailListener.amp in it. # Make another backup copy of the alfresco.war file and put somewhere in case you want to roll this back. # Open a command prompt windows and cd to the location where the Alfresco Module Manager jar is. # Run the following: {noformat} java -jar alfresco-mmt-2.1.1.jar path_to_emailListener.amp path_to_alfresco.war {noformat} So for me this looked like: {noformat} java -jar alfresco-mmt-2.1.1.jar .\email-listener_2.1RC2\emailListener.amp c:\bin\alfresco\tomcat\webapps\alfresco.war {noformat} # You should be able to verify the install by running: {noformat} java -jar alfresco-mmt-2.1.1.jar list c:\bin\alfresco\tomcat\webapps\alfresco.war {noformat} and you should see something like: {noformat} Module 'emailListener' installed in 'c:\bin\alfresco\tomcat\webapps\alfresco.war' - Title: EmailListener - Version: 2.1 - Install Date: Fri Dec 07 08:43:10 PST 2007 - Desription: EmailListener Module {noformat} # Finally, to start the service, just go into your Windows Service control panel and locate the service that is now named 'Alfresco Server'. You can start and stop Alfresco from this control panel. ]]> 2163067 9831262 9798516 18284666 18251898 9831263 9798517 16253010 16220244 18284668 18251900 16253008 16220242 16253003 16220237 16253004 16220238 18284646 18251878 18284644 18251876 16253015 16220249 18284650 18251882 18284649 18251881 18284648 18251880 16253012 16220246 19071807 19039048 18284652 18251884 18284634 18251866 2195762 "Downloads"->"1.4 Releases"->"1.4.5 Release" * I then clicked on alfresco-enterprise-tomcat-1.4.5.zip to download the installation zip file. * I also downloaded alfresco-enterprise-sdk-1.4.5.tar.gz, alfresco-enterprise-sdk-1.4.5.zip, alfresco-web-service-client-1.4.5.tar.gz, alfresco-web-service-client-1.4.5.zip so that I would have them handy for later.]]> 2162998 2195761 2162997 18284636 18251868 2195760 2162996 18284638 18251870 18284640 18251872 18284642 18251874 2195769 "Downloads">"2.1 Releases">"2.1.1" * I then clicked on AlfrescoEnterprise-2.1.1-Setup.exe to download the installation executable. I also downloaded AlfrescoWCMEnterprise-2.1.1-Setup.exe in case I needed it later. * Went to [http://customers.alfresco.com] (I was still logged in) * Went to "Company Home">"Downloads">"2.1 Releases">"2.1.1">"License Files" * I went ahead and downloaded all the "*.lic" files, but I think I only need enterprise-network-customer-unlimited.lic" * Logged out of Alfresco. * Since I suspect I will need a JDBC driver for SQLServer, I downloaded the jTDS-1.2.2 driver from the jtds web site (just Google jtds and go to the download section of the top google return). * I closed the Firefox browser. * I extracted the jtds-1.2.2.jar file from the jtds download * I downloaded and installed the JRockit 6 R27.4 JDK Microsoft Windows (x86 - 32 bit) from BEA's web site * I ran the installer, changed the "Program Files" to "bin" in the installation directory for both the JDK and the JRE. I also chose to install the JRE as public. * Using Firefox, I downloaded the PHP 5.2.5 Windows Installer from php.net and installed it. Although I installed it, I did not integrate it with a web server as I want Alfresco to take port 80. I probably did not need to install PHP, but I thought I would anyway. (again, I changed install path from "Program Files" to "bin"]]> 2163005 2195770 "Downloads">"2.1 Releases">"2.1.1" * I then clicked on AlfrescoEnterprise-2.1.1-Setup.exe to download the installation executable. I also downloaded AlfrescoWCMEnterprise-2.1.1-Setup.exe in case I needed it later. * Went to [http://customers.alfresco.com] (I was still logged in) * Went to "Company Home">"Downloads">"2.1 Releases">"2.1.1">"License Files" * I went ahead and downloaded all the "*.lic" files, but I think I only need enterprise-network-customer-unlimited.lic" * Logged out of Alfresco. * Since I suspect I will need a JDBC driver for SQLServer, I downloaded the jTDS-1.2.2 driver from the jtds web site (just Google jtds and go to the download section of the top google return). * I closed the Firefox browser. * I extracted the jtds-1.2.2.jar file from the jtds download * I downloaded and installed the JRockit 6 R27.4 JDK Microsoft Windows (x86 - 32 bit) from BEA's web site * I ran the installer, changed the "Program Files" to "bin" in the installation directory for both the JDK and the JRE. I also chose to install the JRE as public. * Using Firefox, I downloaded the PHP 5.2.5 Windows Installer from php.net and installed it. Although I installed it, I did not integrate it with a web server as I want Alfresco to take port 80. I probably did not need to install PHP, but I thought I would anyway. (again, I changed install path from "Program Files" to "bin" * I setup a Alfresco database on the server Solstice and granted the LAGOON\DB_Collaboration account to be the db_owner of the Alfresco database. * I then executed the .exe on the alfresco server to install Alfresco * I left the installation directory as c:\Alfresco * It did not find the JDK I installed so it asked to download and install one, but I said no. * I did select the option to download and install the OpenOffice.org component. * After the installation was complete, I left the check box for "Run Configuration Wizard" checked to see if the configuration wizard was worth much. * The Wizard: ** I chose the MS SQL Database Type ** For the content location, I input "\\tornado.shore.mbari.org\alfresco\alf_data". ** For the indicies, I input "c:\alfresco\alf_data\lucene-indexes" ** I left the OpenOffice install location as "C:\Alfresco\openoffice" ** Thus completes the Wizard. * To make sure the Wizard was wise, I looked at all the configuration files that were in c:\Alfresco\tomcat\shared\classes\alfresco\extensions because this is where all the customization for a particular installation goes. * In the custom-hibernate-dialect.properties file, everything looked fine. * In the custom-repository.properties, it was not. ** The database URL was :jdbc:jtds:sqlserver://localhost/alfresco but this is not correct, we want to point it to Solstice so I changed it to: {noformat} db.url=jdbc:jtds:sqlserver://solstice.shore.mbari.org/Alfresco;domain=SHORE;user=DB_Collaboration;password=XXXXX {noformat}]]> 2163006 18284611 18251843 2195767 "Downloads">"2.1 Releases">"2.1.1" * I then clicked on AlfrescoEnterprise-2.1.1-Setup.exe to download the installation executable. I also downloaded AlfrescoWCMEnterprise-2.1.1-Setup.exe in case I needed it later. * Went to [http://customers.alfresco.com] (I was still logged in) * Went to "Company Home">"Downloads">"2.1 Releases">"2.1.1">"License Files" * I went ahead and downloaded all the "*.lic" files, but I think I only need enterprise-network-customer-unlimited.lic" * Logged out of Alfresco. * Since I suspect I will need a JDBC driver for SQLServer, I downloaded the jTDS-1.2.2 driver from the jtds web site (just Google jtds and go to the download section of the top google return). * I closed the Firefox browser. * I extracted the jtds-1.2.2.jar file from the jtds download * I downloaded and installed the JRockit 6 R27.4 JDK Microsoft Windows (x86 - 32 bit) from BEA's web site ]]> 2163003 18284614 18251846 2195768 "Downloads">"2.1 Releases">"2.1.1" * I then clicked on AlfrescoEnterprise-2.1.1-Setup.exe to download the installation executable. I also downloaded AlfrescoWCMEnterprise-2.1.1-Setup.exe in case I needed it later. * Went to [http://customers.alfresco.com] (I was still logged in) * Went to "Company Home">"Downloads">"2.1 Releases">"2.1.1">"License Files" * I went ahead and downloaded all the "*.lic" files, but I think I only need enterprise-network-customer-unlimited.lic" * Logged out of Alfresco. * Since I suspect I will need a JDBC driver for SQLServer, I downloaded the jTDS-1.2.2 driver from the jtds web site (just Google jtds and go to the download section of the top google return). * I closed the Firefox browser. * I extracted the jtds-1.2.2.jar file from the jtds download * I downloaded and installed the JRockit 6 R27.4 JDK Microsoft Windows (x86 - 32 bit) from BEA's web site * I ran the installer, changed the "Program Files" to "bin" in the installation directory for both the JDK and the JRE. I also chose to install the JRE as public. * Using Firefox, I downloaded the PHP 5.2.5 Windows Installer from php.net and installed it. Although I installed it, I did not integrate it with a web server as I want Alfresco to take port 80. I probably did not need to install PHP, but I thought I would anyway.]]> 2163004 2195765 "Downloads">"2.1 Releases">"2.1.1" * I then clicked on AlfrescoEnterprise-2.1.1-Setup.exe to download the installation executable. I also downloaded AlfrescoWCMEnterprise-2.1.1-Setup.exe in case I needed it later. * Went to [http://customers.alfresco.com] (I was still logged in) * Went to "Company Home">"Downloads">"2.1 Releases">"2.1.1">"License Files" * I went ahead and downloaded all the "*.lic" files, but I think I only need enterprise-network-customer-unlimited.lic" * Logged out of Alfresco. * Since I suspect I will need a JDBC driver for SQLServer, I downloaded the jTDS-1.2.2 driver from the jtds web site (just Google jtds and go to the download section of the top google return). * I closed the Firefox browser. * I extracted the jtds-1.2.2.jar file from the jtds download ]]> 2163001 18284616 18251848 2195766 "Downloads">"2.1 Releases">"2.1.1" * I then clicked on AlfrescoEnterprise-2.1.1-Setup.exe to download the installation executable. I also downloaded AlfrescoWCMEnterprise-2.1.1-Setup.exe in case I needed it later. * Went to [http://customers.alfresco.com] (I was still logged in) * Went to "Company Home">"Downloads">"2.1 Releases">"2.1.1">"License Files" * I went ahead and downloaded all the "*.lic" files, but I think I only need enterprise-network-customer-unlimited.lic" * Logged out of Alfresco. * Since I suspect I will need a JDBC driver for SQLServer, I downloaded the jTDS-1.2.2 driver from the jtds web site (just Google jtds and go to the download section of the top google return). * I closed the Firefox browser. * I extracted the jtds-1.2.2.jar file from the jtds download * I downloaded and installed the JRockit 6 R27.4 JDK Microsoft Windows (Intel EM64T & AMD64 - 64 bit) from BEA's web site ]]> 2163002 2195763 "Downloads">"2.1 Releases">"2.1.1" * I then clicked on AlfrescoEnterprise-2.1.1-Setup.exe to download the installation executable. I also downloaded AlfrescoWCMEnterprise-2.1.1-Setup.exe in case I needed it later. * Went to [http://customers.alfresco.com] (I was still logged in) * Went to "Company Home">"Downloads">"2.1 Releases">"2.1.1">"License Files" * I went ahead and downloaded all the "*.lic" files, but I think I only need enterprise-network-customer-unlimited.lic"]]> 2162999 18284618 18251850 2195764 "Downloads">"2.1 Releases">"2.1.1" * I then clicked on AlfrescoEnterprise-2.1.1-Setup.exe to download the installation executable. I also downloaded AlfrescoWCMEnterprise-2.1.1-Setup.exe in case I needed it later. * Went to [http://customers.alfresco.com] (I was still logged in) * Went to "Company Home">"Downloads">"2.1 Releases">"2.1.1">"License Files" * I went ahead and downloaded all the "*.lic" files, but I think I only need enterprise-network-customer-unlimited.lic" * Logged out of Alfresco. * Since I suspect I will need a JDBC driver for SQLServer, I downloaded the jTDS-1.2.2 driver from the jtds web site (just Google jtds and go to the download section of the top google return). * I closed the Firefox browser.]]> 2163000 18284619 18251851 18284621 18251853 2195771 "Downloads">"2.1 Releases">"2.1.1" * I then clicked on AlfrescoEnterprise-2.1.1-Setup.exe to download the installation executable. I also downloaded AlfrescoWCMEnterprise-2.1.1-Setup.exe in case I needed it later. * Went to [http://customers.alfresco.com] (I was still logged in) * Went to "Company Home">"Downloads">"2.1 Releases">"2.1.1">"License Files" * I went ahead and downloaded all the "*.lic" files, but I think I only need enterprise-network-customer-unlimited.lic" * Logged out of Alfresco. * Since I suspect I will need a JDBC driver for SQLServer, I downloaded the jTDS-1.2.2 driver from the jtds web site (just Google jtds and go to the download section of the top google return). * I closed the Firefox browser. * I extracted the jtds-1.2.2.jar file from the jtds download * I downloaded and installed the JRockit 6 R27.4 JDK Microsoft Windows (x86 - 32 bit) from BEA's web site * I ran the installer, changed the "Program Files" to "bin" in the installation directory for both the JDK and the JRE. I also chose to install the JRE as public. * Using Firefox, I downloaded the PHP 5.2.5 Windows Installer from php.net and installed it. Although I installed it, I did not integrate it with a web server as I want Alfresco to take port 80. I probably did not need to install PHP, but I thought I would anyway. (again, I changed install path from "Program Files" to "bin" * I setup a Alfresco database on the server Solstice and granted the LAGOON\DB_Collaboration account to be the db_owner of the Alfresco database. * I then executed the .exe on the alfresco server to install Alfresco * I left the installation directory as c:\Alfresco * It did not find the JDK I installed so it asked to download and install one, but I said no. * I did select the option to download and install the OpenOffice.org component. * After the installation was complete, I left the check box for "Run Configuration Wizard" checked to see if the configuration wizard was worth much. * The Wizard: ** I chose the MS SQL Database Type ** For the content location, I input "\\tornado.shore.mbari.org\alfresco\alf_data". ** For the indicies, I input "c:\alfresco\alf_data\lucene-indexes" ** I left the OpenOffice install location as "C:\Alfresco\openoffice" ** Thus completes the Wizard. * To make sure the Wizard was wise, I looked at all the configuration files that were in c:\Alfresco\tomcat\shared\classes\alfresco\extensions because this is where all the customization for a particular installation goes. * In the custom-hibernate-dialect.properties file, everything looked fine. * In the custom-repository.properties, it was not. ** The database URL was :jdbc:jtds:sqlserver://localhost/alfresco but this is not correct, we want to point it to Solstice so I changed it to: {noformat} db.url=jdbc:jtds:sqlserver://solstice.shore.mbari.org/Alfresco;domain=SHORE;user=DB_Collaboration;password=XXXXX {noformat} * I then installed the jtds-1.2.2.jar in the c:\alfresco\tomcat\common\lib so that it will be on the classpath when Alfresco is started ]]> 2163007 24084640 24051873 24084613 24051846 24084611 24051844 18284984 18252224 9831095 9798343 9831096 9798344 9831098 9798346 9831091 9798339 9831092 9798340 9831094 9798342 9831104 9798352 9831106 9798354 9831102 9798350 9831109 9798357 9831107 9798355 9831113 9798362 9831112 9798361 9831118 9798367 9831116 9798365 9831122 9798371 9831120 9798369 9831126 9798376 9831124 9798374 9831130 9798380 9831134 9798384 9831132 9798382 9831138 9798388 9831135 9798385 9831136 9798386 9831140 9798390 9831146 9798396 9831150 9798400 9831153 9798403 9831155 9798405 9831157 9798407 9831160 9798410 9831167 9798416 24084539 24051771 24084541 24051773 24084543 24051775 24084545 24051777 24084546 24051778 24084532 24051764 24084533 24051765 24084535 24051767 24084537 24051769 10945054 10912299 10945053 10912298 10945058 10912303 10945057 10912302 24084548 24051780 24084609 24051842 24084603 24051836 24084604 24051837 24084606 24051839 24084600 24051833 24084601 24051834 24084595 24051828 24084596 24051829 13172790 13140023 15663134 prompt or in picodos... 4) Craig etal suggest going from picodos with a yr command, but I don't like to because if you forget your connected via radio you may be SOL for 30 minutes because you'll probably kill the radio driver and have to wait for 32 minutes for the hardware to rest(I have not tested that, Im trying at my desk right now...). 5) I prefer to use "capture" command and motocross but you need a version that has the "Transfer>SendBinaryFile" menu item. (eg. v2.32 has it, an older version that Paul found out at sea did not) 6) If you must, you can use hyperterm with the capture command and "Transfer>SendTextFile" but you ***ABSOLUTELY MUST FIRST SET "Send line ends with line feeds" PRIOR TO TRANSMITTING THE FILE*** My tests show that using capture at the oasis prompt with this setting off, causes hyperterm to strip the lf in your cfg file. Then the file on the controller appears as all on one line when typed back. 7) Motocross "send binary file" works from either the picodos or OASIS> capture command (as long as you obey rule #1) In all cases, its "Comm Settings > "Send LF after CR" was un-checked. 8a) Hyperterm works ok from OASIS> prompt IF the "Send Line ends with Line Feeds" is TRUE. (but you may later want to reset it to false so you don't get "Double OASIS> prompts" 8b) Hyperterm works ok from picodos C:\> prompt IF the "Send Line ends with Line Feeds" is FALSE. (also will work ok if TRUE but then you get the double prompt symptom. *************************** THE BOTTOM LINE(S) ***************************** USE dumb editors, check line endings with XVI32 to verify Rule#1 and xfer to a temp file (Rule#2) using MOTOCROSS !!!! (Or only if brave or hardwired to console port, you can use yr from picodos) **************************************************************************** If your forced to deal with an oasis.cfg file that may not have correct line endings even though it looks ok in notepad.... and you have no hex editor to verify... (eg. When you upload the file per recommendations above, it still is all on one line) It seems in my quick testing that you can use notepad to add extra lines at every line and then re-upload...(you will have line endings in hex editor of 0D 0D 0A which still seems to be ok with OASIS>) Curious if anyone else has experiences that differ from above, it would be great to nail this down and cookbook it along with how to recover if you do screw things up...... -Rich If you mistakenly issue the "reset pico" command while connected to the radio port, you will loose contact... The only ways to get it back are to: 1)Bounce the power 2)Wait ~32 minutes for the hardware reset (plus the wait for the radio wakeup procedure) Fortunately in the next release of code (still in testing), Bob added a warning message with a Y/N to remind you your on the radio... (Thanks Bob!) And please correct my last.... re: picodos using yr (ymodem receive...) is from hyperterm (motocross doesn't support ymodem file xfers....) -Rich {noformat} And from Paul: {noformat} Another follow up to this thread... sorry for the overkill. We successfully transferred a new oasis.cfg file to 2010M1 via radio link on Tuesday afternoon. The file was edited with a hex editor to include the correct 0D 0A line terminators. There were places where there were two in a row (0D 0A 0D 0A) but in no cases were there multiple 0Ds before a single 0A as I've run across in some other oasis.cfg files that are floating around (0D 0D 0A). Once the file was edited and double checked, we transferred it according to Rich's procedure in #6 below and detailed here: -Establish link with mooring -At oasis prompt, type "capture [filename] " -Go to HyperTerm properties, 'settings' tab, click 'ascii setup' button, check 'Send line ends with line feeds' button -Go to HyperTerm Transfer menu, and select 'Send Text File...' -Select file to send and wait for file transfer -At oasis prompt, type "^D" to close capture on oasis -Go back to HyperTerm properties and uncheck 'Send line ends with line feeds' -Check file on can to make sure it looks right (at oasis prompt, type "type [filename]") -If all looks correct, rename files (oasis.cfg to [oasis.bk?] and [filename] to oasis.cfg) and reset mooring. -Sacrifice a small animal (or vegetable for the vegetarians) to the mooring gods And finally... -Blame Rich if it doesn't work for you Just wanted to document the successful file transfer over the radio. The mooring came back immediately, and everything appears to be working well. Paul P.s. In #1 below, Rich says that he strongly recommends checking the file in a hex editor. I think this should be an absolute requirement. {noformat}]]> 15630368 15663132 prompt or in picodos... 4) Craig etal suggest going from picodos with a yr command, but I don't like to because if you forget your connected via radio you may be SOL for 30 minutes because you'll probably kill the radio driver and have to wait for 32 minutes for the hardware to rest(I have not tested that, Im trying at my desk right now...). 5) I prefer to use "capture" command and motocross but you need a version that has the "Transfer>SendBinaryFile" menu item. (eg. v2.32 has it, an older version that Paul found out at sea did not) 6) If you must, you can use hyperterm with the capture command and "Transfer>SendTextFile" but you ***ABSOLUTELY MUST FIRST SET "Send line ends with line feeds" PRIOR TO TRANSMITTING THE FILE*** My tests show that using capture at the oasis prompt with this setting off, causes hyperterm to strip the lf in your cfg file. Then the file on the controller appears as all on one line when typed back. 7) Motocross "send binary file" works from either the picodos or OASIS> capture command (as long as you obey rule #1) In all cases, its "Comm Settings > "Send LF after CR" was un-checked. 8a) Hyperterm works ok from OASIS> prompt IF the "Send Line ends with Line Feeds" is TRUE. (but you may later want to reset it to false so you don't get "Double OASIS> prompts" 8b) Hyperterm works ok from picodos C:\> prompt IF the "Send Line ends with Line Feeds" is FALSE. (also will work ok if TRUE but then you get the double prompt symptom. *************************** THE BOTTOM LINE(S) ***************************** USE dumb editors, check line endings with XVI32 to verify Rule#1 and xfer to a temp file (Rule#2) using MOTOCROSS !!!! (Or only if brave or hardwired to console port, you can use yr from picodos) **************************************************************************** If your forced to deal with an oasis.cfg file that may not have correct line endings even though it looks ok in notepad.... and you have no hex editor to verify... (eg. When you upload the file per recommendations above, it still is all on one line) It seems in my quick testing that you can use notepad to add extra lines at every line and then re-upload...(you will have line endings in hex editor of 0D 0D 0A which still seems to be ok with OASIS>) Curious if anyone else has experiences that differ from above, it would be great to nail this down and cookbook it along with how to recover if you do screw things up...... -Rich If you mistakenly issue the "reset pico" command while connected to the radio port, you will loose contact... The only ways to get it back are to: 1)Bounce the power 2)Wait ~32 minutes for the hardware reset (plus the wait for the radio wakeup procedure) Fortunately in the next release of code (still in testing), Bob added a warning message with a Y/N to remind you your on the radio... (Thanks Bob!) And please correct my last.... re: picodos using yr (ymodem receive...) is from hyperterm (motocross doesn't support ymodem file xfers....) -Rich {noformat}]]> 15630366 15663131 prompt or in picodos... 4) Craig etal suggest going from picodos with a yr command, but I don't like to because if you forget your connected via radio you may be SOL for 30 minutes because you'll probably kill the radio driver and have to wait for 32 minutes for the hardware to rest(I have not tested that, Im trying at my desk right now...). 5) I prefer to use "capture" command and motocross but you need a version that has the "Transfer>SendBinaryFile" menu item. (eg. v2.32 has it, an older version that Paul found out at sea did not) 6) If you must, you can use hyperterm with the capture command and "Transfer>SendTextFile" but you ***ABSOLUTELY MUST FIRST SET "Send line ends with line feeds" PRIOR TO TRANSMITTING THE FILE*** My tests show that using capture at the oasis prompt with this setting off, causes hyperterm to strip the lf in your cfg file. Then the file on the controller appears as all on one line when typed back. 7) Motocross "send binary file" works from either the picodos or OASIS> capture command (as long as you obey rule #1) In all cases, its "Comm Settings > "Send LF after CR" was un-checked. 8a) Hyperterm works ok from OASIS> prompt IF the "Send Line ends with Line Feeds" is TRUE. (but you may later want to reset it to false so you don't get "Double OASIS> prompts" 8b) Hyperterm works ok from picodos C:\> prompt IF the "Send Line ends with Line Feeds" is FALSE. (also will work ok if TRUE but then you get the double prompt symptom. *************************** THE BOTTOM LINE(S) ***************************** USE dumb editors, check line endings with XVI32 to verify Rule#1 and xfer to a temp file (Rule#2) using MOTOCROSS !!!! (Or only if brave or hardwired to console port, you can use yr from picodos) **************************************************************************** If your forced to deal with an oasis.cfg file that may not have correct line endings even though it looks ok in notepad.... and you have no hex editor to verify... (eg. When you upload the file per recommendations above, it still is all on one line) It seems in my quick testing that you can use notepad to add extra lines at every line and then re-upload...(you will have line endings in hex editor of 0D 0D 0A which still seems to be ok with OASIS>) Curious if anyone else has experiences that differ from above, it would be great to nail this down and cookbook it along with how to recover if you do screw things up...... -Rich {noformat}]]> 15630365 15663137 15630371 15663136 15630370 9404560 9371810 15663130 prompt or in picodos... 4) Craig etal suggest going from picodos with a yr command, but I don't like to because if you forget your connected via radio you may be SOL for 30 minutes because you'll probably kill the radio driver and have to wait for 32 minutes for the hardware to rest(I have not tested that, Im trying at my desk right now...). 5) I prefer to use "capture" command and motocross but you need a version that has the "Transfer>SendBinaryFile" menu item. (eg. v2.32 has it, an older version that Paul found out at sea did not) 6) If you must, you can use hyperterm with the capture command and "Transfer>SendTextFile" but you ***ABSOLUTELY MUST FIRST SET "Send line ends with line feeds" PRIOR TO TRANSMITTING THE FILE*** My tests show that using capture at the oasis prompt with this setting off, causes hyperterm to strip the lf in your cfg file. Then the file on the controller appears as all on one line when typed back. 7) Motocross "send binary file" works from either the picodos or OASIS> capture command (as long as you obey rule #1) In all cases, its "Comm Settings > "Send LF after CR" was un-checked. 8a) Hyperterm works ok from OASIS> prompt IF the "Send Line ends with Line Feeds" is TRUE. (but you may later want to reset it to false so you don't get "Double OASIS> prompts" 8b) Hyperterm works ok from picodos C:\> prompt IF the "Send Line ends with Line Feeds" is FALSE. (also will work ok if TRUE but then you get the double prompt symptom. *************************** THE BOTTOM LINE(S) ***************************** USE dumb editors, check line endings with XVI32 to verify Rule#1 and xfer to a temp file (Rule#2) using MOTOCROSS !!!! (Or only if brave or hardwired to console port, you can use yr from picodos) **************************************************************************** If your forced to deal with an oasis.cfg file that may not have correct line endings even though it looks ok in notepad.... and you have no hex editor to verify... (eg. When you upload the file per recommendations above, it still is all on one line) It seems in my quick testing that you can use notepad to add extra lines at every line and then re-upload...(you will have line endings in hex editor of 0D 0D 0A which still seems to be ok with OASIS>) Curious if anyone else has experiences that differ from above, it would be great to nail this down and cookbook it along with how to recover if you do screw things up...... -Rich ]]> 15630364 9404556 9371806 9404558 9371808 5865600 5832838 5865601 5832839 5865597 5832835 5865598 5832836 11829556 11796799 5865588 5832826 15663139 15630374 15663140 prompt or in picodos... 4) Craig etal suggest going from picodos with a yr command, but I don't like to because if you forget your connected via radio you may be SOL for 30 minutes because you'll probably kill the radio driver and have to wait for 32 minutes for the hardware to rest(I have not tested that, Im trying at my desk right now...). 5) I prefer to use "capture" command and motocross but you need a version that has the "Transfer>SendBinaryFile" menu item. (eg. v2.32 has it, an older version that Paul found out at sea did not) 6) If you must, you can use hyperterm with the capture command and "Transfer>SendTextFile" but you ***ABSOLUTELY MUST FIRST SET "Send line ends with line feeds" PRIOR TO TRANSMITTING THE FILE*** My tests show that using capture at the oasis prompt with this setting off, causes hyperterm to strip the lf in your cfg file. Then the file on the controller appears as all on one line when typed back. 7) Motocross "send binary file" works from either the picodos or OASIS> capture command (as long as you obey rule #1) In all cases, its "Comm Settings > "Send LF after CR" was un-checked. 8a) Hyperterm works ok from OASIS> prompt IF the "Send Line ends with Line Feeds" is TRUE. (but you may later want to reset it to false so you don't get "Double OASIS> prompts" 8b) Hyperterm works ok from picodos C:\> prompt IF the "Send Line ends with Line Feeds" is FALSE. (also will work ok if TRUE but then you get the double prompt symptom. *************************** THE BOTTOM LINE(S) ***************************** USE dumb editors, check line endings with XVI32 to verify Rule#1 and xfer to a temp file (Rule#2) using MOTOCROSS !!!! (Or only if brave or hardwired to console port, you can use yr from picodos) **************************************************************************** If your forced to deal with an oasis.cfg file that may not have correct line endings even though it looks ok in notepad.... and you have no hex editor to verify... (eg. When you upload the file per recommendations above, it still is all on one line) It seems in my quick testing that you can use notepad to add extra lines at every line and then re-upload...(you will have line endings in hex editor of 0D 0D 0A which still seems to be ok with OASIS>) Curious if anyone else has experiences that differ from above, it would be great to nail this down and cookbook it along with how to recover if you do screw things up...... -Rich If you mistakenly issue the "reset pico" command while connected to the radio port, you will loose contact... The only ways to get it back are to: 1)Bounce the power 2)Wait ~32 minutes for the hardware reset (plus the wait for the radio wakeup procedure) Fortunately in the next release of code (still in testing), Bob added a warning message with a Y/N to remind you your on the radio... (Thanks Bob!) And please correct my last.... re: picodos using yr (ymodem receive...) is from hyperterm (motocross doesn't support ymodem file xfers....) -Rich {noformat} And from Paul: {noformat} Another follow up to this thread... sorry for the overkill. We successfully transferred a new oasis.cfg file to 2010M1 via radio link on Tuesday afternoon. The file was edited with a hex editor to include the correct 0D 0A line terminators. There were places where there were two in a row (0D 0A 0D 0A) but in no cases were there multiple 0Ds before a single 0A as I've run across in some other oasis.cfg files that are floating around (0D 0D 0A). Once the file was edited and double checked, we transferred it according to Rich's procedure in #6 below and detailed here: -Establish link with mooring -At oasis prompt, type "capture [filename] " -Go to HyperTerm properties, 'settings' tab, click 'ascii setup' button, check 'Send line ends with line feeds' button -Go to HyperTerm Transfer menu, and select 'Send Text File...' -Select file to send and wait for file transfer -At oasis prompt, type "^D" to close capture on oasis -Go back to HyperTerm properties and uncheck 'Send line ends with line feeds' -Check file on can to make sure it looks right (at oasis prompt, type "type [filename]") -If all looks correct, rename files (oasis.cfg to [oasis.bk?] and [filename] to oasis.cfg) and reset mooring. -Sacrifice a small animal (or vegetable for the vegetarians) to the mooring gods And finally... -Blame Rich if it doesn't work for you Just wanted to document the successful file transfer over the radio. The mooring came back immediately, and everything appears to be working well. Paul P.s. In #1 below, Rich says that he strongly recommends checking the file in a hex editor. I think this should be an absolute requirement. {noformat} And from Bob: {noformat} On another note, if we can *ever* get up to speed with the most current checked-in code, (that is, if we can switch to the new radios and wire protocol), it's worth noting that this new code also has some line editing features. They've turned out to be extremely useful for the respirometers, which are based on Oasis and where the line editor commands originated. Allows you to add, delete, and comment-out lines in OASIS.CFG in situ, which greatly reduces the need for transferring files. -Bob {noformat}]]> 15630375 9404610 9371860 9404608 9371858 14843912 14811144 9404644 9371895 9404648 9371899 15663253 15630490 15663257 15630494 15663258 15630495 15663255 15630492 15663260 15630497 15663264 15630501 15663249 15630486 9404435 9371670 15663289 "Downloads">"2.1 Releases">"2.1.1" # I then clicked on alfresco-enterprise-tomcat-2.1.1.zip to download the zip file. # Went to [http://customers.alfresco.com] (I was still logged in) # Went to "Company Home">"Downloads">"2.1 Releases">"2.1.1">"License Files" # I went ahead and downloaded all the "*.lic" files, but I think I only need enterprise-network-customer-unlimited.lic" # Logged out of Alfresco. # Since I suspect I will need a JDBC driver for SQLServer, I downloaded the jTDS-1.2.2 driver from the jtds web site (just Google jtds and go to the download section of the top google return). # I closed the Firefox browser. # I extracted the jtds-1.2.2.jar file from the jtds download # I downloaded and installed the JRockit 6 R27.4 JDK Microsoft Windows (x86 - 32 bit) from BEA's web site {note} After installing JRockit, make sure you set the JAVA_HOME environment variable to point to the installation of JRockit. For example, I went to the desktop, right clicked on the computer, did Properties, then clicked on the Advanced tab, then click on the environment variables button and then created a new system variable named JAVA_HOME and set to c:\bin\Java\jrockit-R27.4.0-jdk1.6.0_02 {note} # I ran the installer, changed the "Program Files" to "bin" in the installation directory for both the JDK and the JRE. I also chose to install the JRE as public. # Using Firefox, I downloaded the PHP 5.2.5 Windows Installer from php.net and installed it. Although I installed it, I did not integrate it with a web server as I want Alfresco to take port 80. I probably did not need to install PHP, but I thought I would anyway. (again, I changed install path from "Program Files" to "bin" # I also downloaded and installed OpenOffice and ran it once so I could get through the initial startup # I setup a Alfresco database on the server Solstice and granted the LAGOON\DB_Collaboration account to be the db_owner of the Alfresco database. # I unzipped the alfresco tomcat zip file to an alfresco directory in c:\bin # I then went to the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions directory for the customization of the server. ## I edited the custom-repository.properties file ### Changed the dir.root and dir.indexes to look like: {noformat} dir.root=//tornado.shore.mbari.org/Alfresco/alf_data dir.indexes=d:/alf_data/lucene-indexes {noformat} ### Commented out the db.* lines for the HSQL Connection (db.driver and db.url) ### Uncommented the db.* lines for MSSQL and changed to use the jTDS driver. They should look like: {noformat} db.driver=net.sourceforge.jtds.jdbc.Driver db.url=jdbc:jtds:sqlserver://solstice.shore.mbari.org/Alfresco;domain=SHORE;user=DB_Collaboration;password=XXXXXXXXX {noformat} ### I also added the following section to override the mail server settings {noformat} # Mail server configuration mail.host=mail.mbari.org mail.port=25 mail.username= mail.password= {noformat} ## Edited the custom-hibernate-dialect.properties file ### Commented out the HSQL Dialect ### Uncommented the MSSQL Dialect # I then installed the jtds-1.2.2.jar in the c:\bin\alfresco\tomcat\common\lib so that it will be on the classpath when Alfresco is started # Now this is not necessarily fun, but in order to really get it configured the way we want it, you need to pull the original .war file out, edit some stuff inside and re-create the .war. {note} This should all be done before starting Alfresco for the first time. {note} # Copy the c:\Alfresco\tomcat\webapps\alfresco.war file to your home directory. # Make a second copy so that you will always the original (I copied to alfresco.war.orig and moved it somewhere else. It is important to move it and have only the alfresco.war file in the directory because when you un-jar it, all the files go right where alfresco.war is.) # From a command line, un-jar the war file using: {noformat} jar -xvf alfresco.war {noformat} # This unpacks a lot of files and after it completes, move (or delete) the alfresco.war file from the directory. This needs to be done so it does not end up in the new .war file. # I wanted to change the "Company Home" that seems to be everywhere to something that says MBARI. ## Edited ./WEB-INF/classes/alfresco/messages/webclient.properties and changed company_home from 'Company Home' to 'MBARI' ## Edited ./WEB-INF/classes/alfresco/messages/webclient_en_US.properties and changed company_home from 'Company Home' to 'MBARI' ## I edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces.properties and changed the first two lines to read {noformat} spaces.company_home.name=MBARI spaces.company_home.description=The root space for MBARI {noformat} ## Edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces_en_US.properties and made the same changes as the previous step {tip} This took a bit to find all these, and to be honest, I am not sure which one actually made the change on the GUI, but I suspect it was the _en_US ones. {tip} # When users are imported via LDAP, user spaces get created automatically. In order to put them where I wanted them to go (instead of right in the Company Home), I edited the ./WEB-INF/classes/alfresco/authentication-services-context.xml file. In the file there is a bean with an name of personalHomeFolderProvider. There is a property name 'path' and I added {noformat} /${spaces.user_homes.childname} {noformat} to the end to try to get them to create the user spaces there instead of in the Company Home. The final bean XML looks like: {noformat} /${spaces.company_home.childname}/${spaces.user_homes.childname} ${spaces.store} false All All {noformat} # I wanted to change the logo that is used. I attached the replacement logo [here|^AlfrescoLogo32.png]. Copy this to ./images/logo and overwrite the one that is there. # In order to setup SSL for the application (will do that later), edit ./WEB-INF/web.xml and add the following {noformat} Login Pages /* CONFIDENTIAL {noformat} right before the ending tag at the bottom of the file. # Now in order to change the default behavior so that all content is versioned from the start, I edited the .\WEB-INF\classes\alfresco\model\contentModel.xml and searched for the content type definition block. {noformat} Content cm:cmobject true d:content false true false true {noformat} and added the following block right before the ending tag: {noformat} cm:versionable {noformat} so the final block looks like: {noformat} Content cm:cmobject true d:content false true false true cm:versionable {noformat} # Lastly, I wanted to redirect the log files to a separate disk. This is done because in the Windows hardening process, most of the disk space ends up on drive D: where alfresco does not live. The log files quickly fill up the small C: drive. To to this, I edited the .\WEB-INF\classes\log4j.properties and changed the log file appender location to point to a directory that was created on the D: drive called D:/alf_logs. # That takes care of all the changes to the WAR file. We can now put it back into .war form. # While you are in the directory you expanded the war file in, run ## jar cvfm alfresco.war META-INF\MANIFEST.MF . # You should now have an alfresco.war file in the directory. Move that back to the alfresco install and overwrite the existing one. # Most users like the details view, so I set the default to that by editing c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions\web-client-config-custom.xml and added: {noformat} details 20
20
20 {noformat} right before the closing tag. # Now in order to use MBARI accounts, NTLM authentication was turned on and then chained with the native Alfresco accounts so that we could have non-MBARI accounts on the Alfresco server. ## In order to enable NTLM and native Alfresco authentication, I had to edit two files. For simplicity I have just attached them here and they can be downloaded and installed in the extensions directory. ### The first file is the [ntlm-authentication-context.xml|^ntlm-authentication-context.xml] file. This configures and enables NTLM authentication. ### The next file was the [chaining-authentication-context.xml|^chaining-authentication-context.xml] file which enabled Alfresco authentication and chained it together with the NTLM authentication from the previous file. # Then in order to setup CIFS on the server, I edited the file-servers-custom.xml file to look like the attached [file-servers-custom.xml|^file-servers-custom.xml] file. # In order to grant certain accounts admin privs, I created a new custom-authority-services-context.xml in the same directory as the ldap-authentication-context.xml file and added {noformat} kgomes admin administrator {noformat} # In order for Alfresco to handle all port 80 traffic, I changed Tomcat so that it takes port 80 and SSL goes over port 443. So I edited the c:\Alfresco\tomcat\conf\server.xml file and changed the 8080 port to 80 and the 8443 port to 443 (the 443 change is done in two places). # Now I needed to setup the SSL for the web traffic. Cathy Sewell was instrumental in getting this working. She ordered a new certificate specifically for alfresco and put it in the c:\local\cert folder. Here are the instructions for what she did to get the certficate installed. {noformat} SSL certificate for server Alfresco - 1/2/08 C:\bin\Java\jrockit-R27.1.0-jre1.6.0_02\bin>keytool -genkey -alias tomcat -keyalg RSA -keystore tomcat.keystore What is your first and last name? [alfresco.mbari.org]: What is the name of your organizational unit? [IS]: What is the name of your organization? [MBARI]: What is the name of your City or Locality? [Moss Landing]: What is the name of your State or Province? [CD]: CA What is the two-letter country code for this unit? [US]: Is CN=alfresco.mbari.org, OU=IS, O=MBARI, L=Moss Landing, ST=CA, C=US correct? [no]: y Enter key password for (RETURN if same as keystore password): C:\bin\Java\jrockit-R27.4.0-jre1.6.0_02\bin>keytool -certreq -keyalg RSA -alias tomcat -file certreq.csr -keystore tomcat.keystore Enter keystore password: Generated certificate request file, certreq.csr, was submitted to SSL provider. Certificate provider sent certificate file (alfresco.mbari.org.crt), along with gd_bundle.crt, gd_cross_intermediate.crt, and gd_intermediate.crt. Additionally, I downloaded valicert_class2_root.cer from their website. These files were stored in c:\local\cert. The following commands were used to add them to the tomcat keystore: C:\bin\Java\jrockit-R27.4.0-jre1.6.0_02\bin>keytool -import -alias root -keystore tomcat.keystore -trustcacerts -file c:\local\cert\valicert_class2_root.cer Enter keystore password: Certificate already exists in system-wide CA keystore under alias Do you still want to add it to your own keystore? [no]: y Certificate was added to keystore C:\bin\Java\jrockit-R27.4.0-jre1.6.0_02\bin>keytool -import -alias cross -keystore tomcat.keystore -trustcacerts -file c:\local\cert\gd_cross_intermediate.crt Enter keystore password: Certificate was added to keystore C:\bin\Java\jrockit-R27.4.0-jre1.6.0_02\bin>keytool -import -alias intermed -keystore tomcat.keystore -trustcacerts -file c:\local\cert\gd_intermediate.crt Enter keystore password: Certificate was added to keystore C:\bin\Java\jrockit-R27.4.0-jre1.6.0_02\bin>keytool -import -alias tomcat -keystore tomcat.keystore -trustcacerts -file c:\local\cert\alfresco.mbari.org.crt Enter keystore password: Certificate reply was installed in keystore {noformat} # I edited the c:\bin\alfresco\tomcat\conf\server.xml file and uncommented the SSL section and edited to look like that shown below. {noformat} {noformat} # Since I was in the server.xml file, I went ahead and changed it so that the default webapp was alfresco so that you would get alfresco anytime you went to the base URL. I did this by adding: {noformat} {noformat} as the last line of the tag section (right before the closing tag). {note} You will also notice the Valve tag that I had to add to turn off proxy cache disabling so that IE clients would work correctly over SSL. Gotta love M$. {note} # I copied the enterprise-network-unlimited.lic file into the c:\Alfresco\tomcat\shared\classes\alfresco\extensions\license directory # Just to keep things clean, I edited the c:\bin\alfresco\alfresco.bat file and put 'rem' in front of the second JAVA_OPTS set as I am using Java 6. # Now after you run it for the first time and the database structure gets created, you can't restart it because you get: {noformat} java.sql.SQLException: Column names in each table must be unique. Column name 'ID_' in table 'JBPM_ACTION' is specified more than once. {noformat} Sigh, so in order to keep Alfresco from hurting itself, I had to turn off the schema updates. This is done by editing the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions\custom-repository.properties and adding the following: {noformat} db.schema.update=false {noformat} and then restarting alfresco. # To install Alfresco as a Windows Service use a command prompt and enter the following: {noformat} cd c:\bin\alfresco\tomcat\bin service.bat install alfresco tomcat5.exe //US//alfresco --DisplayName "Alfresco Server" tomcat5.exe //US//alfresco --JvmMs=512 --JvmMx=1024 --JvmSs=64 tomcat5.exe //US//alfresco --JavaHome=c:/bin/Java/jrockit-R27.4.0-jdk1.6.0_02 tomcat5.exe //US//alfresco --Environment ALF_HOME=c:/bin/alfresco/ tomcat5.exe //US//alfresco --Environment PATH=c:/bin/alfresco/bin;%PATH% tomcat5.exe //US//alfresco --StartPath c:/bin/alfresco --Startup auto {noformat} # To uninstall the service, at a later time, do the following: {noformat} cd c:\bin\alfresco\tomcat\bin service.bat uninstall alfresco {noformat} # To edit your service settings at any time: {noformat} cd c:\alfresco\tomcat\bin tomcat5w.exe //ES//alfresco {noformat} {warning} These next couple of steps had to be taken to install a patch from Alfresco for an issue with bulk uploads I was having. Essentially when file and path structures get really long and nasty, Alfresco was throwing an error and bailing out. This patch (two Java classes) fixed that issue. {warning} # Next, I downloaded the attached [JAR|^act2139.jar] file and copied it to the c:\bin\alfresco\tomcat\webapps\alfresco\WEB-INF\classes directory. # I shutdown Alfresco and then unjarred the file to install the new classes. They are: ## org/alfresco/filesys/smb/server/SMBSrvPacket.class ## org/alfresco/filesys/util/DataBuffer.class # I would assume since they do not overwrite anything, that this location is further up in the class loader and so it will load these new classes first. # I deleted the act2139.jar file and the META-INF directory that the unjarring process created. # In order to install certain modules (like the email listener), I had to get the Alfresco Module Manager from the customers.alfresco.com download site. I downloaded the alfresco-mmt-2.1.1.jar file locally so I could use it to install modules. # I then downloaded the email listener module from [http://forge.alfresco.com/projects/email-listener/]. It came as a zip file, so I unzipped it and it created a folder with the appropriate emailListener.amp in it. # Make another backup copy of the alfresco.war file and put somewhere in case you want to roll this back. # Open a command prompt windows and cd to the location where the Alfresco Module Manager jar is. # Run the following: {noformat} java -jar alfresco-mmt-2.1.1.jar path_to_emailListener.amp path_to_alfresco.war {noformat} So for me this looked like: {noformat} java -jar alfresco-mmt-2.1.1.jar .\email-listener_2.1RC2\emailListener.amp c:\bin\alfresco\tomcat\webapps\alfresco.war {noformat} # You should be able to verify the install by running: {noformat} java -jar alfresco-mmt-2.1.1.jar list c:\bin\alfresco\tomcat\webapps\alfresco.war {noformat} and you should see something like: {noformat} Module 'emailListener' installed in 'c:\bin\alfresco\tomcat\webapps\alfresco.war' - Title: EmailListener - Version: 2.1 - Install Date: Fri Dec 07 08:43:10 PST 2007 - Desription: EmailListener Module {noformat} # Finally, to start the service, just go into your Windows Service control panel and locate the service that is now named 'Alfresco Server'. You can start and stop Alfresco from this control panel. h1. Content Migration Now, in order to migrate content from old alfresco and normal file structures, I did the following: h3. For content already in alfresco: # Navigate to the space whose contents you want to migrate. For example, let's say I want to migrate the stuff from my personal space. I would navigate (using the WebUI) to the /MBARI/User Homes/kgomes space. You should see the contents of the kgomes folder from this view. # Click on 'More actions->View Details'. # On the right hand side, click on 'Export'. # For package name, I usually enter the space name followed by '_export', but it doesn't really matter. # Click on the link that says 'Click here to select the destination' and select somewhere that you will be able to download the .acp file from. # Select 'Current Space'. # Select 'Include Children'. # Uncheck 'Include this space' unless you have content (documents) in this specific folder (anything other than folders) that you want to migrate. This is a bit tricky, but there are two ways to do this. If you want to have the top level folder created, use the 'Include this space' and that will create the top level folder. Otherwise, if will expand into the folder in which you import the .acp file into. This is important in cases where the folder has already been created for you (like with user homes) and you have to migrate content into that folder. If you have the option to create the top level directory, by all means do so. # Uncheck 'Export in background' so you can force it to happen and you know when it is complete.]]> 15630526 15663291 15630528 15663292 'Downloads'>'2.1 Releases'>'2.1.1' # I changed to the 'Details View', made 40 items visible, and then downloaded 'alfresco-enterprise-tomcat-2.1.1.zip' file. # I then unzipped the downloaded file to c:\bin which created an alfresco-enterprise-tomcat-2.1.1 folder in c:\bin. # I renamed the alfresco-enterprise-tomcat-2.1.1 folder to simply alfresco. # I then went back to the web browser and went to 'Company Home'>'Downloads'>'2.1 Releases'>'2.1.1'>'License Files' # I am not sure if I can do this with our agreement, but I downloaded the 'enterprise-network-customer-unlimited.lic' file. {note} I did get approval from Joe Van De Graaff at Alfresco to use the license for a test installation to get us through this issue. {note} # I logged out of the Alfresco customer web site. # I Googled on jTDS to find the jTDS JDBC driver and downloaded the jtds-1.2.2-dist.zip file from the website. # Using Windows Explorer, I could just open the jTDS zip file and copy the jtds-1.2.2.jar file. # I then pasted it in the directory c:\bin\alfresco\tomcat\common\lib directory. # I created a c:\data\alf_data directory where the alfresco data will be stored. This is different from the production installation in that the content is stored on a network appliance (\\tornado.shore.mbari.org\alfresco). # I installed a copy of SQL Server 2005 locally to use for the database to back the Alfresco test install. {note} In order to do this without warnings, I had to go back and install IIS through the Add/Remove Programs Control Panel. {note} ## I used the Local System account to run services and only used Windows Authentication logins ## I installed all the service packs and the SQL Server Management Studio product to admin DBs. # In SQL Server, I added the SHORE\DB_Collaboration accounts to the logins. # I created a new database named alfresco-test and made SHORE\DB_Collaboration the owner. # I then went to the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions directory for the customization of the server. ## I edited the custom-repository.properties file ### Changed the dir.root and dir.indexes to look like: {noformat} dir.root=c:/data/alf_data dir.indexes=c:/data/alf_data/lucene-indexes {noformat} ### Commented out the db.* lines for the HSQL Connection (db.driver and db.url) ### Uncommented the db.* lines for MSSQL and changed to use the jTDS driver. They should look like (except the password should be the right one): {noformat} db.driver=net.sourceforge.jtds.jdbc.Driver db.url=jdbc:jtds:sqlserver://localhost/alfresco-test;domain=SHORE;user=DB_Collaboration;password=XXXXXXXXX {noformat} ### I also added the following section to override the mail server settings {noformat} # Mail server configuration mail.host=mail.mbari.org mail.port=25 mail.username= mail.password= {noformat} ## Edited the custom-hibernate-dialect.properties file ### Commented out the HSQL Dialect ### Uncommented the MSSQL Dialect # Now this is not necessarily fun, but in order to really get it configured the way we want it, you need to pull the original .war file out, edit some stuff inside and re-create the .war. {note} This should all be done before starting Alfresco for the first time. {note} # Copy the c:\bin\alfresco\tomcat\webapps\alfresco.war file to your home directory. # Make a second copy so that you will always the original (I copied to alfresco.war.orig and moved it somewhere else. It is important to move it and have only the alfresco.war file in the directory because when you un-jar it, all the files go right where alfresco.war is.) # From a command line, un-jar the war file using: {noformat} jar -xvf alfresco.war {noformat} # This unpacks a lot of files and after it completes, move (or delete) the alfresco.war file from the directory. This needs to be done so it does not end up in the new .war file. # I wanted to change the "Company Home" that seems to be everywhere to something that says MBARI. ## Edited ./WEB-INF/classes/alfresco/messages/webclient.properties and changed company_home from 'Company Home' to 'MBARI Test' ## Edited ./WEB-INF/classes/alfresco/messages/webclient_en_US.properties and changed company_home from 'Company Home' to 'MBARI Test' ## I edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces.properties and changed the first two lines to read {noformat} spaces.company_home.name=MBARI Test spaces.company_home.description=The root of MBARIs Test Alfresco Server {noformat} ## Edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces_en_US.properties and made the same changes as the previous step {tip} This took a bit to find all these, and to be honest, I am not sure which one actually made the change on the GUI, but I suspect it was the _en_US ones. {tip} # When users are imported via LDAP, user spaces get created automatically. In order to put them where I wanted them to go (instead of right in the Company Home), I edited the ./WEB-INF/classes/alfresco/authentication-services-context.xml file. In the file there is a bean with an name of personalHomeFolderProvider. There is a property name 'path' and I added {noformat} /${spaces.user_homes.childname} {noformat} to the end to try to get them to create the user spaces there instead of in the Company Home. The final bean XML looks like: {noformat} /${spaces.company_home.childname}/${spaces.user_homes.childname} ${spaces.store} false All All {noformat} # I wanted to change the logo that is used. I attached the replacement [Alfresco Logo|CLT:Installation Notes^AlfrescoLogo32.png]. Copy this to ./images/logo and overwrite the one that is there. {warning} Note that I did NOT setup SSL for this installation so if I will need to come back and do that if I want truly parallel systems {warning} # Now in order to change the default behavior so that all content is versioned from the start, I edited the .\WEB-INF\classes\alfresco\model\contentModel.xml and searched for the content type definition block. {noformat} Content cm:cmobject true d:content false true false true {noformat} and added the following block right before the ending tag: {noformat} cm:versionable {noformat} so the final block looks like: {noformat} Content cm:cmobject true d:content false true false true cm:versionable {noformat} # That takes care of all the changes to the WAR file. We can now put it back into .war form. # While you are in the directory you expanded the war file in, run ## jar cvfm alfresco.war META-INF\MANIFEST.MF . # You should now have an alfresco.war file in the directory. Move that back to the alfresco install and overwrite the existing one. # Most users like the details view, so I set the default to that by editing c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions\web-client-config-custom.xml and added: {noformat} details 20
20
20 {noformat} right before the closing tag. # Now in order to use MBARI accounts, NTLM authentication was turned on and then chained with the native Alfresco accounts so that we could have non-MBARI accounts on the Alfresco server. ## For simplicity sake, I have attached the files and you can simply download and install them in the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions directory. {note} Before doing these next steps, rename the file-servers-custom.xml file to file-servers-custom.xml.orig so you will have a backup of the original {note} ### First install the [NTLM Configuration XML File|^ntlm-authentication-context.xml] ### Next install the [Authentication Chaining Configuration File|^chaining-authentication-context.xml] ### Next install the [CIFS configuration|^file-servers-custom.xml] file and over-write the existing one. ### Now in order to setup a job that imports users and groups once a day, download and install the [LDAP configuration|^ldap-synchronisation-context.xml] file. ### The ldap sych XML file simply contains all the configuration information with properties to hold the actual values for your installation. To define these properties, I installed the following [properties file|^ldap-synchronisation.properties]. If you are setting up your own installation, you will change these properties for your install. {warning} In the CIFS configuration file, make sure you change the tag to reflect a unique name on the network. {warning} ### Next install the [customized authority configuration|^custom-authority-services-context.xml] file (this gives administrative privs to certain accounts). {warning} Note that I did NOT change the server to take over port 80 traffic as the SQL Server install seemed to want IIS which is currently using port 80 {warning} # Now in order for the alfresco web application to be the default, I edit the c:\bin\alfresco\tomcat\conf\server.xml file and added: {noformat} {noformat} as the last line of the tag section (right before the closing tag). {note} You will also notice the Valve tag that I had to add to turn off proxy cache disabling so that IE clients would work correctly over SSL. Gotta love M$. {note} # Just to keep things clean, I edited the c:\bin\alfresco\alfresco.bat file and put 'rem' in front of the second JAVA_OPTS set as I am using Java 6. # You are now actually ready to start alfresco for the first time! Open a command window and cd over the to c:\bin\alfresco directory and then type: {noformat} alf_start.bat {noformat} # After a long time (took several minutes on a regular PC), look at the alfresco.log file in the c:\bin\alfresco directory and see if it looks like everything started OK, you can also check the database to see if the tables have been created in the alfresco-test database. You should also be able to go to http://alfresco-test.shore.mbari.org:8080 and see the alfresco web application. # Now from the command window where you ran alf_start.bat, run alf_stop.bat to shut the server down. Check the alfresco.log file to see if anything weird happened. If not, try restarting it with alf_start.bat again and look at the alfresco.log file. Sometimes, you can't restart it because you get: {noformat} java.sql.SQLException: Column names in each table must be unique. Column name 'ID_' in table 'JBPM_ACTION' is specified more than once. {noformat} Sigh, so in order to keep Alfresco from hurting itself, you might have to turn off the schema updates. This is done by editing the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions\custom-repository.properties and adding the following: {noformat} db.schema.update=false {noformat} and then restarting alfresco. # To install Alfresco as a Windows Service use a command prompt and enter the following: {noformat} cd c:\bin\alfresco\tomcat\bin service.bat install alfresco tomcat5.exe //US//alfresco --DisplayName "Alfresco Server" tomcat5.exe //US//alfresco --JvmMs=512 --JvmMx=1024 --JvmSs=64 tomcat5.exe //US//alfresco --JavaHome=c:/bin/Java/jrockit-R27.4.0-jdk1.6.0_02 tomcat5.exe //US//alfresco --Environment ALF_HOME=c:/bin/alfresco/ tomcat5.exe //US//alfresco --Environment PATH=c:/bin/alfresco/bin;%PATH% tomcat5.exe //US//alfresco --StartPath c:/bin/alfresco --Startup auto {noformat} # To uninstall the service, at a later time, do the following: {noformat} cd c:\bin\alfresco\tomcat\bin service.bat uninstall alfresco {noformat} # To edit your service settings at any time: {noformat} cd c:\alfresco\tomcat\bin tomcat5w.exe //ES//alfresco {noformat} {warning} These next couple of steps had to be taken to install a patch from Alfresco for an issue with bulk uploads I was having. Essentially when file and path structures get really long and nasty, Alfresco was throwing an error and bailing out. This patch (two Java classes) fixed that issue. {warning} # Next, I downloaded the attached [JAR|^act2139.jar] file and copied it to the c:\bin\alfresco\tomcat\webapps\alfresco\WEB-INF\classes directory. # I shutdown Alfresco and then unjarred the file to install the new classes. They are: ## org/alfresco/filesys/smb/server/SMBSrvPacket.class ## org/alfresco/filesys/util/DataBuffer.class # I would assume since they do not overwrite anything, that this location is further up in the class loader and so it will load these new classes first. # I deleted the act2139.jar file and the META-INF directory that the unjarring process created. # I did not do this, but you can verify this took, I run alfresco with the {noformat} CATALINA_OPTS="-verbose:class" {noformat} and verifyied that you can find some line, some where, that shows: {noformat} [Loaded org.alfresco.filesys.smb.server.SMBSrvPacket from file:/opt/alfresco211/tomcat/webapps/alfresco/WEB-INF/classes/org/alfresco/filesys/smb/server/SMBSrvPacket.class] {noformat} and NOT: {noformat} Loaded org.alfresco.filesys.smb.server.SMBSrvPacket from file:/opt/alfresco211/tomcat/webapps/alfresco/WEB-INF/lib/alfresco-repository.jar] {noformat} ]]> 15630529 5865680 5832919 15663294 15630531 5865677 5832916 15663296 15630533 15663267 15630504 15663272 15630509 15663271 15630508 15663273 15630510 15663275 15630512 21398241 21365519 9404496 9371740 3178528 "Downloads">"2.1 Releases">"2.1.1" # I then clicked on alfresco-enterprise-tomcat-2.1.1.zip to download the zip file. # Went to [http://customers.alfresco.com] (I was still logged in) # Went to "Company Home">"Downloads">"2.1 Releases">"2.1.1">"License Files" # I went ahead and downloaded all the "*.lic" files, but I think I only need enterprise-network-customer-unlimited.lic" # Logged out of Alfresco. # Since I suspect I will need a JDBC driver for SQLServer, I downloaded the jTDS-1.2.2 driver from the jtds web site (just Google jtds and go to the download section of the top google return). # I closed the Firefox browser. # I extracted the jtds-1.2.2.jar file from the jtds download # I downloaded and installed the JRockit 6 R27.4 JDK Microsoft Windows (x86 - 32 bit) from BEA's web site {note} After installing JRockit, make sure you set the JAVA_HOME environment variable to point to the installation of JRockit. For example, I went to the desktop, right clicked on the computer, did Properties, then clicked on the Advanced tab, then click on the environment variables button and then created a new system variable named JAVA_HOME and set to c:\bin\Java\jrockit-R27.4.0-jdk1.6.0_02 {note} # I ran the installer, changed the "Program Files" to "bin" in the installation directory for both the JDK and the JRE. I also chose to install the JRE as public. # Using Firefox, I downloaded the PHP 5.2.5 Windows Installer from php.net and installed it. Although I installed it, I did not integrate it with a web server as I want Alfresco to take port 80. I probably did not need to install PHP, but I thought I would anyway. (again, I changed install path from "Program Files" to "bin" # I also downloaded and installed OpenOffice and ran it once so I could get through the initial startup # I setup a Alfresco database on the server Solstice and granted the LAGOON\DB_Collaboration account to be the db_owner of the Alfresco database. # I unzipped the alfresco tomcat zip file to an alfresco directory in c:\bin # I then went to the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions directory for the customization of the server. ## I edited the custom-repository.properties file ### Changed the dir.root and dir.indexes to look like: {noformat} dir.root=//tornado.shore.mbari.org/Alfresco/alf_data dir.indexes=d:/alf_data/lucene-indexes {noformat} ### Commented out the db.* lines for the HSQL Connection (db.driver and db.url) ### Uncommented the db.* lines for MSSQL and changed to use the jTDS driver. They should look like: {noformat} db.driver=net.sourceforge.jtds.jdbc.Driver db.url=jdbc:jtds:sqlserver://solstice.shore.mbari.org/Alfresco;domain=SHORE;user=DB_Collaboration;password=XXXXXXXXX {noformat} ### I also added the following section to override the mail server settings {noformat} # Mail server configuration mail.host=mail.mbari.org mail.port=25 mail.username= mail.password= {noformat} ## Edited the custom-hibernate-dialect.properties file ### Commented out the HSQL Dialect ### Uncommented the MSSQL Dialect # I then installed the jtds-1.2.2.jar in the c:\bin\alfresco\tomcat\common\lib so that it will be on the classpath when Alfresco is started # Now this is not necessarily fun, but in order to really get it configured the way we want it, you need to pull the original .war file out, edit some stuff inside and re-create the .war. {note} This should all be done before starting Alfresco for the first time. {note} # Copy the c:\Alfresco\tomcat\webapps\alfresco.war file to your home directory. # Make a second copy so that you will always the original (I copied to alfresco.war.orig and moved it somewhere else. It is important to move it and have only the alfresco.war file in the directory because when you un-jar it, all the files go right where alfresco.war is.) # From a command line, un-jar the war file using: {noformat} jar -xvf alfresco.war {noformat} # This unpacks a lot of files and after it completes, move (or delete) the alfresco.war file from the directory. This needs to be done so it does not end up in the new .war file. # I wanted to change the "Company Home" that seems to be everywhere to something that says MBARI. ## Edited ./WEB-INF/classes/alfresco/messages/webclient.properties and changed company_home from 'Company Home' to 'MBARI' ## Edited ./WEB-INF/classes/alfresco/messages/webclient_en_US.properties and changed company_home from 'Company Home' to 'MBARI' ## I edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces.properties and changed the first two lines to read {noformat} spaces.company_home.name=MBARI spaces.company_home.description=The root space for MBARI {noformat} ## Edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces_en_US.properties and made the same changes as the previous step {tip} This took a bit to find all these, and to be honest, I am not sure which one actually made the change on the GUI, but I suspect it was the _en_US ones. {tip} # When users are imported via LDAP, user spaces get created automatically. In order to put them where I wanted them to go (instead of right in the Company Home), I edited the ./WEB-INF/classes/alfresco/authentication-services-context.xml file. In the file there is a bean with an name of personalHomeFolderProvider. There is a property name 'path' and I added {noformat} /${spaces.user_homes.childname} {noformat} to the end to try to get them to create the user spaces there instead of in the Company Home. The final bean XML looks like: {noformat} /${spaces.company_home.childname}/${spaces.user_homes.childname} ${spaces.store} false All All {noformat} # I wanted to change the logo that is used. I attached the replacement logo [here|^AlfrescoLogo32.png]. Copy this to ./images/logo and overwrite the one that is there. # In order to setup SSL for the application (will do that later), edit ./WEB-INF/web.xml and add the following {noformat} Login Pages /* CONFIDENTIAL {noformat} right before the ending tag at the bottom of the file. # Now in order to change the default behavior so that all content is versioned from the start, I edited the .\WEB-INF\classes\alfresco\model\contentModel.xml and searched for the content type definition block. {noformat} Content cm:cmobject true d:content false true false true {noformat} and added the following block right before the ending tag: {noformat} cm:versionable {noformat} so the final block looks like: {noformat} Content cm:cmobject true d:content false true false true cm:versionable {noformat} # That takes care of all the changes to the WAR file. We can now put it back into .war form. # While you are in the directory you expanded the war file in, run ## jar cvfm alfresco.war META-INF\MANIFEST.MF . # You should now have an alfresco.war file in the directory. Move that back to the alfresco install and overwrite the existing one. # Most users like the details view, so I set the default to that by editing c:\Alfresco\tomcat\shared\classes\alfresco\extensions/web-client-config-custom.xml and added: {noformat} details 20
20
20 {noformat} right before the closing tag. # Now in order to use MBARI accounts, NTLM authentication was turned on and then chained with the native Alfresco accounts so that we could have non-MBARI accounts on the Alfresco server. ## In order to enable NTLM and native Alfresco authentication, I had to edit two files. For simplicity I have just attached them here and they can be downloaded and installed in the extensions directory. ### The first file is the [ntlm-authentication-context.xml|^ntlm-authentication-context.xml] file. This configures and enables NTLM authentication. ### The next file was the [chaining-authentication-context.xml|^chaining-authentication-context.xml] file which enabled Alfresco authentication and chained it together with the NTLM authentication from the previous file. # Then in order to setup CIFS on the server, I edited the file-servers-custom.xml file to look like the attached [file-servers-custom.xml|^file-servers-custom.xml] file. # In order to grant certain accounts admin privs, I created a new custom-authority-services-context.xml in the same directory as the ldap-authentication-context.xml file and added {noformat} kgomes admin administrator {noformat} # In order for Alfresco to handle all port 80 traffic, I changed Tomcat so that it takes port 80 and SSL goes over port 443. So I edited the c:\Alfresco\tomcat\conf\server.xml file and changed the 8080 port to 80 and the 8443 port to 443 (the 443 change is done in two places). # Now I needed to setup the SSL for the web traffic. Cathy Sewell was instrumental in getting this working. She ordered a new certificate specifically for alfresco and put it in the c:\local\cert folder. Here are the instructions for what she did to get the certficate installed. {noformat} SSL certificate for server Alfresco - 1/2/08 C:\bin\Java\jrockit-R27.1.0-jre1.6.0_02\bin>keytool -genkey -alias tomcat -keyalg RSA -keystore tomcat.keystore What is your first and last name? [alfresco.mbari.org]: What is the name of your organizational unit? [IS]: What is the name of your organization? [MBARI]: What is the name of your City or Locality? [Moss Landing]: What is the name of your State or Province? [CD]: CA What is the two-letter country code for this unit? [US]: Is CN=alfresco.mbari.org, OU=IS, O=MBARI, L=Moss Landing, ST=CA, C=US correct? [no]: y Enter key password for (RETURN if same as keystore password): C:\bin\Java\jrockit-R27.4.0-jre1.6.0_02\bin>keytool -certreq -keyalg RSA -alias tomcat -file certreq.csr -keystore tomcat.keystore Enter keystore password: Generated certificate request file, certreq.csr, was submitted to SSL provider. Certificate provider sent certificate file (alfresco.mbari.org.crt), along with gd_bundle.crt, gd_cross_intermediate.crt, and gd_intermediate.crt. Additionally, I downloaded valicert_class2_root.cer from their website. These files were stored in c:\local\cert. The following commands were used to add them to the tomcat keystore: C:\bin\Java\jrockit-R27.4.0-jre1.6.0_02\bin>keytool -import -alias root -keystore tomcat.keystore -trustcacerts -file c:\local\cert\valicert_class2_root.cer Enter keystore password: Certificate already exists in system-wide CA keystore under alias Do you still want to add it to your own keystore? [no]: y Certificate was added to keystore C:\bin\Java\jrockit-R27.4.0-jre1.6.0_02\bin>keytool -import -alias cross -keystore tomcat.keystore -trustcacerts -file c:\local\cert\gd_cross_intermediate.crt Enter keystore password: Certificate was added to keystore C:\bin\Java\jrockit-R27.4.0-jre1.6.0_02\bin>keytool -import -alias intermed -keystore tomcat.keystore -trustcacerts -file c:\local\cert\gd_intermediate.crt Enter keystore password: Certificate was added to keystore C:\bin\Java\jrockit-R27.4.0-jre1.6.0_02\bin>keytool -import -alias tomcat -keystore tomcat.keystore -trustcacerts -file c:\local\cert\alfresco.mbari.org.crt Enter keystore password: Certificate reply was installed in keystore Adjustment of the server.xml file was left to Kevin. {noformat} #I edited the c:\bin\alfresco\tomcat\conf\server.xml file and uncommented the SSL section and edited to look like that shown below. {noformat} {noformat} # Since I was in the server.xml file, I went ahead and changed it so that the default webapp was alfresco so that you would get alfresco anytime you went to the base URL. I did this by adding: {noformat} {noformat} as the last line of the tag section (right before the closing tag). {note} You will also notice the Valve tag that I had to add to turn off proxy cache disabling so that IE clients would work correctly over SSL. Gotta love M$. {note} # I copied the enterprise-network-unlimited.lic file into the c:\Alfresco\tomcat\shared\classes\alfresco\extensions\license directory # Just to keep things clean, I edited the c:\bin\alfresco\alfresco.bat file and put 'rem' in front of the second JAVA_OPTS set as I am using Java 6. # Now after you run it for the first time and the database structure gets created, you can't restart it because you get: {noformat} java.sql.SQLException: Column names in each table must be unique. Column name 'ID_' in table 'JBPM_ACTION' is specified more than once. {noformat} Sigh, so in order to keep Alfresco from hurting itself, I had to turn off the schema updates. This is done by editing the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions\custom-repository.properties and adding the following: {noformat} db.schema.update=false {noformat} and then restarting alfresco. # To install Alfresco as a Windows Service use a command prompt and enter the following: {noformat} cd c:\bin\alfresco\tomcat\bin service.bat install alfresco tomcat5.exe //US//alfresco --DisplayName "Alfresco Server" tomcat5.exe //US//alfresco --JvmMs=512 --JvmMx=1024 --JvmSs=64 tomcat5.exe //US//alfresco --JavaHome=c:/bin/Java/jrockit-R27.4.0-jdk1.6.0_02 tomcat5.exe //US//alfresco --Environment ALF_HOME=c:/bin/alfresco/ tomcat5.exe //US//alfresco --Environment PATH=c:/bin/alfresco/bin;%PATH% tomcat5.exe //US//alfresco --StartPath c:/bin/alfresco --Startup auto {noformat} # To uninstall the service, at a later time, do the following: {noformat} cd c:\bin\alfresco\tomcat\bin service.bat uninstall alfresco {noformat} # To edit your service settings at any time: {noformat} cd c:\alfresco\tomcat\bin tomcat5w.exe //ES//alfresco {noformat} # In order to install certain modules (like the email listener), I had to get the Alfresco Module Manager from the customers.alfresco.com download site. I downloaded the alfresco-mmt-2.1.1.jar file locally so I could use it to install modules. # I then downloaded the email listener module from [http://forge.alfresco.com/projects/email-listener/]. It came as a zip file, so I unzipped it and it created a folder with the appropriate emailListener.amp in it. # Make another backup copy of the alfresco.war file and put somewhere in case you want to roll this back. # Open a command prompt windows and cd to the location where the Alfresco Module Manager jar is. # Run the following: {noformat} java -jar alfresco-mmt-2.1.1.jar path_to_emailListener.amp path_to_alfresco.war {noformat} So for me this looked like: {noformat} java -jar alfresco-mmt-2.1.1.jar .\email-listener_2.1RC2\emailListener.amp c:\bin\alfresco\tomcat\webapps\alfresco.war {noformat} # You should be able to verify the install by running: {noformat} java -jar alfresco-mmt-2.1.1.jar list c:\bin\alfresco\tomcat\webapps\alfresco.war {noformat} and you should see something like: {noformat} Module 'emailListener' installed in 'c:\bin\alfresco\tomcat\webapps\alfresco.war' - Title: EmailListener - Version: 2.1 - Install Date: Fri Dec 07 08:43:10 PST 2007 - Desription: EmailListener Module {noformat} # Finally, to start the service, just go into your Windows Service control panel and locate the service that is now named 'Alfresco Server'. You can start and stop Alfresco from this control panel. ]]> 3112994 3178530 "Downloads">"2.1 Releases">"2.1.1" # I then clicked on alfresco-enterprise-tomcat-2.1.1.zip to download the zip file. # Went to [http://customers.alfresco.com] (I was still logged in) # Went to "Company Home">"Downloads">"2.1 Releases">"2.1.1">"License Files" # I went ahead and downloaded all the "*.lic" files, but I think I only need enterprise-network-customer-unlimited.lic" # Logged out of Alfresco. # Since I suspect I will need a JDBC driver for SQLServer, I downloaded the jTDS-1.2.2 driver from the jtds web site (just Google jtds and go to the download section of the top google return). # I closed the Firefox browser. # I extracted the jtds-1.2.2.jar file from the jtds download # I downloaded and installed the JRockit 6 R27.4 JDK Microsoft Windows (x86 - 32 bit) from BEA's web site {note} After installing JRockit, make sure you set the JAVA_HOME environment variable to point to the installation of JRockit. For example, I went to the desktop, right clicked on the computer, did Properties, then clicked on the Advanced tab, then click on the environment variables button and then created a new system variable named JAVA_HOME and set to c:\bin\Java\jrockit-R27.4.0-jdk1.6.0_02 {note} # I ran the installer, changed the "Program Files" to "bin" in the installation directory for both the JDK and the JRE. I also chose to install the JRE as public. # Using Firefox, I downloaded the PHP 5.2.5 Windows Installer from php.net and installed it. Although I installed it, I did not integrate it with a web server as I want Alfresco to take port 80. I probably did not need to install PHP, but I thought I would anyway. (again, I changed install path from "Program Files" to "bin" # I also downloaded and installed OpenOffice and ran it once so I could get through the initial startup # I setup a Alfresco database on the server Solstice and granted the LAGOON\DB_Collaboration account to be the db_owner of the Alfresco database. # I unzipped the alfresco tomcat zip file to an alfresco directory in c:\bin # I then went to the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions directory for the customization of the server. ## I edited the custom-repository.properties file ### Changed the dir.root and dir.indexes to look like: {noformat} dir.root=//tornado.shore.mbari.org/Alfresco/alf_data dir.indexes=d:/alf_data/lucene-indexes {noformat} ### Commented out the db.* lines for the HSQL Connection (db.driver and db.url) ### Uncommented the db.* lines for MSSQL and changed to use the jTDS driver. They should look like: {noformat} db.driver=net.sourceforge.jtds.jdbc.Driver db.url=jdbc:jtds:sqlserver://solstice.shore.mbari.org/Alfresco;domain=SHORE;user=DB_Collaboration;password=XXXXXXXXX {noformat} ### I also added the following section to override the mail server settings {noformat} # Mail server configuration mail.host=mail.mbari.org mail.port=25 mail.username= mail.password= {noformat} ## Edited the custom-hibernate-dialect.properties file ### Commented out the HSQL Dialect ### Uncommented the MSSQL Dialect # I then installed the jtds-1.2.2.jar in the c:\bin\alfresco\tomcat\common\lib so that it will be on the classpath when Alfresco is started # Now this is not necessarily fun, but in order to really get it configured the way we want it, you need to pull the original .war file out, edit some stuff inside and re-create the .war. {note} This should all be done before starting Alfresco for the first time. {note} # Copy the c:\Alfresco\tomcat\webapps\alfresco.war file to your home directory. # Make a second copy so that you will always the original (I copied to alfresco.war.orig and moved it somewhere else. It is important to move it and have only the alfresco.war file in the directory because when you un-jar it, all the files go right where alfresco.war is.) # From a command line, un-jar the war file using: {noformat} jar -xvf alfresco.war {noformat} # This unpacks a lot of files and after it completes, move (or delete) the alfresco.war file from the directory. This needs to be done so it does not end up in the new .war file. # I wanted to change the "Company Home" that seems to be everywhere to something that says MBARI. ## Edited ./WEB-INF/classes/alfresco/messages/webclient.properties and changed company_home from 'Company Home' to 'MBARI' ## Edited ./WEB-INF/classes/alfresco/messages/webclient_en_US.properties and changed company_home from 'Company Home' to 'MBARI' ## I edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces.properties and changed the first two lines to read {noformat} spaces.company_home.name=MBARI spaces.company_home.description=The root space for MBARI {noformat} ## Edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces_en_US.properties and made the same changes as the previous step {tip} This took a bit to find all these, and to be honest, I am not sure which one actually made the change on the GUI, but I suspect it was the _en_US ones. {tip} # When users are imported via LDAP, user spaces get created automatically. In order to put them where I wanted them to go (instead of right in the Company Home), I edited the ./WEB-INF/classes/alfresco/authentication-services-context.xml file. In the file there is a bean with an name of personalHomeFolderProvider. There is a property name 'path' and I added {noformat} /${spaces.user_homes.childname} {noformat} to the end to try to get them to create the user spaces there instead of in the Company Home. The final bean XML looks like: {noformat} /${spaces.company_home.childname}/${spaces.user_homes.childname} ${spaces.store} false All All {noformat} # I wanted to change the logo that is used. I attached the replacement logo [here|^AlfrescoLogo32.png]. Copy this to ./images/logo and overwrite the one that is there. # In order to setup SSL for the application (will do that later), edit ./WEB-INF/web.xml and add the following {noformat} Login Pages /* CONFIDENTIAL {noformat} right before the ending tag at the bottom of the file. # Now in order to change the default behavior so that all content is versioned from the start, I edited the .\WEB-INF\classes\alfresco\model\contentModel.xml and searched for the content type definition block. {noformat} Content cm:cmobject true d:content false true false true {noformat} and added the following block right before the ending tag: {noformat} cm:versionable {noformat} so the final block looks like: {noformat} Content cm:cmobject true d:content false true false true cm:versionable {noformat} # That takes care of all the changes to the WAR file. We can now put it back into .war form. # While you are in the directory you expanded the war file in, run ## jar cvfm alfresco.war META-INF\MANIFEST.MF . # You should now have an alfresco.war file in the directory. Move that back to the alfresco install and overwrite the existing one. # Most users like the details view, so I set the default to that by editing c:\Alfresco\tomcat\shared\classes\alfresco\extensions/web-client-config-custom.xml and added: {noformat} details 20
20
20 {noformat} right before the closing tag. # Now in order to use MBARI accounts, NTLM authentication was turned on and then chained with the native Alfresco accounts so that we could have non-MBARI accounts on the Alfresco server. ## In order to enable NTLM and native Alfresco authentication, I had to edit two files. For simplicity I have just attached them here and they can be downloaded and installed in the extensions directory. ### The first file is the [ntlm-authentication-context.xml|^ntlm-authentication-context.xml] file. This configures and enables NTLM authentication. ### The next file was the [chaining-authentication-context.xml|^chaining-authentication-context.xml] file which enabled Alfresco authentication and chained it together with the NTLM authentication from the previous file. # Then in order to setup CIFS on the server, I edited the file-servers-custom.xml file to look like the attached [file-servers-custom.xml|^file-servers-custom.xml] file. # In order to grant certain accounts admin privs, I created a new custom-authority-services-context.xml in the same directory as the ldap-authentication-context.xml file and added {noformat} kgomes admin administrator {noformat} # In order for Alfresco to handle all port 80 traffic, I changed Tomcat so that it takes port 80 and SSL goes over port 443. So I edited the c:\Alfresco\tomcat\conf\server.xml file and changed the 8080 port to 80 and the 8443 port to 443 (the 443 change is done in two places). # Now I needed to setup the SSL for the web traffic. Cathy Sewell was instrumental in getting this working. She ordered a new certificate specifically for alfresco and put it in the c:\local\cert folder. Here are the instructions for what she did to get the certficate installed. {noformat} SSL certificate for server Alfresco - 1/2/08 C:\bin\Java\jrockit-R27.1.0-jre1.6.0_02\bin>keytool -genkey -alias tomcat -keyalg RSA -keystore tomcat.keystore What is your first and last name? [alfresco.mbari.org]: What is the name of your organizational unit? [IS]: What is the name of your organization? [MBARI]: What is the name of your City or Locality? [Moss Landing]: What is the name of your State or Province? [CD]: CA What is the two-letter country code for this unit? [US]: Is CN=alfresco.mbari.org, OU=IS, O=MBARI, L=Moss Landing, ST=CA, C=US correct? [no]: y Enter key password for (RETURN if same as keystore password): C:\bin\Java\jrockit-R27.4.0-jre1.6.0_02\bin>keytool -certreq -keyalg RSA -alias tomcat -file certreq.csr -keystore tomcat.keystore Enter keystore password: Generated certificate request file, certreq.csr, was submitted to SSL provider. Certificate provider sent certificate file (alfresco.mbari.org.crt), along with gd_bundle.crt, gd_cross_intermediate.crt, and gd_intermediate.crt. Additionally, I downloaded valicert_class2_root.cer from their website. These files were stored in c:\local\cert. The following commands were used to add them to the tomcat keystore: C:\bin\Java\jrockit-R27.4.0-jre1.6.0_02\bin>keytool -import -alias root -keystore tomcat.keystore -trustcacerts -file c:\local\cert\valicert_class2_root.cer Enter keystore password: Certificate already exists in system-wide CA keystore under alias Do you still want to add it to your own keystore? [no]: y Certificate was added to keystore C:\bin\Java\jrockit-R27.4.0-jre1.6.0_02\bin>keytool -import -alias cross -keystore tomcat.keystore -trustcacerts -file c:\local\cert\gd_cross_intermediate.crt Enter keystore password: Certificate was added to keystore C:\bin\Java\jrockit-R27.4.0-jre1.6.0_02\bin>keytool -import -alias intermed -keystore tomcat.keystore -trustcacerts -file c:\local\cert\gd_intermediate.crt Enter keystore password: Certificate was added to keystore C:\bin\Java\jrockit-R27.4.0-jre1.6.0_02\bin>keytool -import -alias tomcat -keystore tomcat.keystore -trustcacerts -file c:\local\cert\alfresco.mbari.org.crt Enter keystore password: Certificate reply was installed in keystore Adjustment of the server.xml file was left to Kevin. {noformat} #I edited the c:\bin\alfresco\tomcat\conf\server.xml file and uncommented the SSL section and edited to look like that shown below. {noformat} {noformat} # Since I was in the server.xml file, I went ahead and changed it so that the default webapp was alfresco so that you would get alfresco anytime you went to the base URL. I did this by adding: {noformat} {noformat} as the last line of the tag section (right before the closing tag). {note} You will also notice the Valve tag that I had to add to turn off proxy cache disabling so that IE clients would work correctly over SSL. Gotta love M$. {note} # I copied the enterprise-network-unlimited.lic file into the c:\Alfresco\tomcat\shared\classes\alfresco\extensions\license directory # Just to keep things clean, I edited the c:\bin\alfresco\alfresco.bat file and put 'rem' in front of the second JAVA_OPTS set as I am using Java 6. # Now after you run it for the first time and the database structure gets created, you can't restart it because you get: {noformat} java.sql.SQLException: Column names in each table must be unique. Column name 'ID_' in table 'JBPM_ACTION' is specified more than once. {noformat} Sigh, so in order to keep Alfresco from hurting itself, I had to turn off the schema updates. This is done by editing the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions\custom-repository.properties and adding the following: {noformat} db.schema.update=false {noformat} and then restarting alfresco. # To install Alfresco as a Windows Service use a command prompt and enter the following: {noformat} cd c:\bin\alfresco\tomcat\bin service.bat install alfresco tomcat5.exe //US//alfresco --DisplayName "Alfresco Server" tomcat5.exe //US//alfresco --JvmMs=512 --JvmMx=1024 --JvmSs=64 tomcat5.exe //US//alfresco --JavaHome=c:/bin/Java/jrockit-R27.4.0-jdk1.6.0_02 tomcat5.exe //US//alfresco --Environment ALF_HOME=c:/bin/alfresco/ tomcat5.exe //US//alfresco --Environment PATH=c:/bin/alfresco/bin;%PATH% tomcat5.exe //US//alfresco --StartPath c:/bin/alfresco --Startup auto {noformat} # To uninstall the service, at a later time, do the following: {noformat} cd c:\bin\alfresco\tomcat\bin service.bat uninstall alfresco {noformat} # To edit your service settings at any time: {noformat} cd c:\alfresco\tomcat\bin tomcat5w.exe //ES//alfresco {noformat} # In order to install certain modules (like the email listener), I had to get the Alfresco Module Manager from the customers.alfresco.com download site. I downloaded the alfresco-mmt-2.1.1.jar file locally so I could use it to install modules. # I then downloaded the email listener module from [http://forge.alfresco.com/projects/email-listener/]. It came as a zip file, so I unzipped it and it created a folder with the appropriate emailListener.amp in it. # Make another backup copy of the alfresco.war file and put somewhere in case you want to roll this back. # Open a command prompt windows and cd to the location where the Alfresco Module Manager jar is. # Run the following: {noformat} java -jar alfresco-mmt-2.1.1.jar path_to_emailListener.amp path_to_alfresco.war {noformat} So for me this looked like: {noformat} java -jar alfresco-mmt-2.1.1.jar .\email-listener_2.1RC2\emailListener.amp c:\bin\alfresco\tomcat\webapps\alfresco.war {noformat} # You should be able to verify the install by running: {noformat} java -jar alfresco-mmt-2.1.1.jar list c:\bin\alfresco\tomcat\webapps\alfresco.war {noformat} and you should see something like: {noformat} Module 'emailListener' installed in 'c:\bin\alfresco\tomcat\webapps\alfresco.war' - Title: EmailListener - Version: 2.1 - Install Date: Fri Dec 07 08:43:10 PST 2007 - Desription: EmailListener Module {noformat} # Finally, to start the service, just go into your Windows Service control panel and locate the service that is now named 'Alfresco Server'. You can start and stop Alfresco from this control panel. h1. Content Migration Now, in order to migrate content from old alfresco and normal file structures, I did the following: h3. For content already in alfresco: # Navigate to the space whose contents you want to migrate. For example, let's say I want to migrate the stuff from my personal space. I would navigate (using the WebUI) to the /MBARI/User Homes/kgomes space. You should see the contents of the kgomes folder from this view. # Click on 'More actions->View Details'. # On the right hand side, click on 'Export'. # For package name, I usually enter the space name followed by '_export', but it doesn't really matter. # Click on the link that says 'Click here to select the destination' and select somewhere that you will be able to download the .acp file from. # Select 'Current Space'. # Select 'Include Children'. # Uncheck 'Include this space' unless you have content (documents) in this specific folder (anything other than folders) that you want to migrate. This is a bit tricky, but there are two ways to do this. If you want to have the top level folder created, use the 'Include this space' and that will create the top level folder. Otherwise, if will expand into the folder in which you import the .acp file into. # Uncheck 'Export in background' so you can force it to happen and you know when it is complete.]]> 3112996 3178524 "Downloads">"2.1 Releases">"2.1.1" # I then clicked on alfresco-enterprise-tomcat-2.1.1.zip to download the zip file. # Went to [http://customers.alfresco.com] (I was still logged in) # Went to "Company Home">"Downloads">"2.1 Releases">"2.1.1">"License Files" # I went ahead and downloaded all the "*.lic" files, but I think I only need enterprise-network-customer-unlimited.lic" # Logged out of Alfresco. # Since I suspect I will need a JDBC driver for SQLServer, I downloaded the jTDS-1.2.2 driver from the jtds web site (just Google jtds and go to the download section of the top google return). # I closed the Firefox browser. # I extracted the jtds-1.2.2.jar file from the jtds download # I downloaded and installed the JRockit 6 R27.4 JDK Microsoft Windows (x86 - 32 bit) from BEA's web site {note} After installing JRockit, make sure you set the JAVA_HOME environment variable to point to the installation of JRockit. For example, I went to the desktop, right clicked on the computer, did Properties, then clicked on the Advanced tab, then click on the environment variables button and then created a new system variable named JAVA_HOME and set to c:\bin\Java\jrockit-R27.4.0-jdk1.6.0_02 {note} # I ran the installer, changed the "Program Files" to "bin" in the installation directory for both the JDK and the JRE. I also chose to install the JRE as public. # Using Firefox, I downloaded the PHP 5.2.5 Windows Installer from php.net and installed it. Although I installed it, I did not integrate it with a web server as I want Alfresco to take port 80. I probably did not need to install PHP, but I thought I would anyway. (again, I changed install path from "Program Files" to "bin" # I also downloaded and installed OpenOffice and ran it once so I could get through the initial startup # I setup a Alfresco database on the server Solstice and granted the LAGOON\DB_Collaboration account to be the db_owner of the Alfresco database. # I unzipped the alfresco tomcat zip file to an alfresco directory in c:\bin # I then went to the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions directory for the customization of the server. ## I edited the custom-repository.properties file ### Changed the dir.root and dir.indexes to look like: {noformat} dir.root=//tornado.shore.mbari.org/Alfresco/alf_data dir.indexes=d:/alf_data/lucene-indexes {noformat} ### Commented out the db.* lines for the HSQL Connection (db.driver and db.url) ### Uncommented the db.* lines for MSSQL and changed to use the jTDS driver. They should look like: {noformat} db.driver=net.sourceforge.jtds.jdbc.Driver db.url=jdbc:jtds:sqlserver://solstice.shore.mbari.org/Alfresco;domain=SHORE;user=DB_Collaboration;password=XXXXXXXXX {noformat} ### I also added the following section to override the mail server settings {noformat} # Mail server configuration mail.host=mail.mbari.org mail.port=25 mail.username= mail.password= {noformat} ## Edited the custom-hibernate-dialect.properties file ### Commented out the HSQL Dialect ### Uncommented the MSSQL Dialect # I then installed the jtds-1.2.2.jar in the c:\bin\alfresco\tomcat\common\lib so that it will be on the classpath when Alfresco is started # Now this is not necessarily fun, but in order to really get it configured the way we want it, you need to pull the original .war file out, edit some stuff inside and re-create the .war. {note} This should all be done before starting Alfresco for the first time. {note} # Copy the c:\Alfresco\tomcat\webapps\alfresco.war file to your home directory. # Make a second copy so that you will always the original (I copied to alfresco.war.orig and moved it somewhere else. It is important to move it and have only the alfresco.war file in the directory because when you un-jar it, all the files go right where alfresco.war is.) # From a command line, un-jar the war file using: {noformat} jar -xvf alfresco.war {noformat} # This unpacks a lot of files and after it completes, move (or delete) the alfresco.war file from the directory. This needs to be done so it does not end up in the new .war file. # I wanted to change the "Company Home" that seems to be everywhere to something that says MBARI. ## Edited ./WEB-INF/classes/alfresco/messages/webclient.properties and changed company_home from 'Company Home' to 'MBARI' ## Edited ./WEB-INF/classes/alfresco/messages/webclient_en_US.properties and changed company_home from 'Company Home' to 'MBARI' ## I edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces.properties and changed the first two lines to read {noformat} spaces.company_home.name=MBARI spaces.company_home.description=The root space for MBARI {noformat} ## Edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces_en_US.properties and made the same changes as the previous step {tip} This took a bit to find all these, and to be honest, I am not sure which one actually made the change on the GUI, but I suspect it was the _en_US ones. {tip} # When users are imported via LDAP, user spaces get created automatically. In order to put them where I wanted them to go (instead of right in the Company Home), I edited the ./WEB-INF/classes/alfresco/authentication-services-context.xml file. In the file there is a bean with an name of personalHomeFolderProvider. There is a property name 'path' and I added {noformat} /${spaces.user_homes.childname} {noformat} to the end to try to get them to create the user spaces there instead of in the Company Home. The final bean XML looks like: {noformat} /${spaces.company_home.childname}/${spaces.user_homes.childname} ${spaces.store} false All All {noformat} # I wanted to change the logo that is used. I attached the replacement logo [here|^AlfrescoLogo32.png]. Copy this to ./images/logo and overwrite the one that is there. # In order to setup SSL for the application (will do that later), edit ./WEB-INF/web.xml and add the following {noformat} Login Pages /* CONFIDENTIAL {noformat} right before the ending tag at the bottom of the file. # Now in order to change the default behavior so that all content is versioned from the start, I edited the .\WEB-INF\classes\alfresco\model\contentModel.xml and searched for the content type definition block. {noformat} Content cm:cmobject true d:content false true false true {noformat} and added the following block right before the ending tag: {noformat} cm:versionable {noformat} so the final block looks like: {noformat} Content cm:cmobject true d:content false true false true cm:versionable {noformat} # That takes care of all the changes to the WAR file. We can now put it back into .war form. # While you are in the directory you expanded the war file in, run ## jar cvfm alfresco.war META-INF\MANIFEST.MF . # You should now have an alfresco.war file in the directory. Move that back to the alfresco install and overwrite the existing one. # Most users like the details view, so I set the default to that by editing c:\Alfresco\tomcat\shared\classes\alfresco\extensions/web-client-config-custom.xml and added: {noformat} details 20
20
20 {noformat} right before the closing tag. # Now in order to use MBARI accounts, NTLM authentication was turned on and then chained with the native Alfresco accounts so that we could have non-MBARI accounts on the Alfresco server. ## In order to enable NTLM and native Alfresco authentication, I had to edit two files. For simplicity I have just attached them here and they can be downloaded and installed in the extensions directory. ### The first file is the [ntlm-authentication-context.xml|^ntlm-authentication-context.xml] file. This configures and enables NTLM authentication. ### The next file was the [chaining-authentication-context.xml|^chaining-authentication-context.xml] file which enabled Alfresco authentication and chained it together with the NTLM authentication from the previous file. # Then in order to setup CIFS on the server, I edited the file-servers-custom.xml file to look like the attached [file-servers-custom.xml|^file-servers-custom.xml] file. # In order to grant certain accounts admin privs, I created a new custom-authority-services-context.xml in the same directory as the ldap-authentication-context.xml file and added {noformat} kgomes admin administrator {noformat} # In order for Alfresco to handle all port 80 traffic, I changed Tomcat so that it takes port 80 and SSL goes over port 443. So I edited the c:\Alfresco\tomcat\conf\server.xml file and changed the 8080 port to 80 and the 8443 port to 443 (the 443 change is done in two places). # Now I needed to setup the SSL for the web traffic. Cathy Sewell was instrumental in getting this working. She ordered a new certificate specifically for alfresco and put it in the c:\local\cert folder. I edited the c:\bin\alfresco\tomcat\conf\server.xml file and uncommented the SSL section and edited to look like that shown below. {noformat} {noformat} # Since I was in the server.xml file, I went ahead and changed it so that the default webapp was alfresco so that you would get alfresco anytime you went to the base URL. I did this by adding: {noformat} {noformat} as the last line of the tag section (right before the closing tag). {note} You will also notice the Valve tag that I had to add to turn off proxy cache disabling so that IE clients would work correctly over SSL. Gotta love M$. {note} # I copied the enterprise-network-unlimited.lic file into the c:\Alfresco\tomcat\shared\classes\alfresco\extensions\license directory # Just to keep things clean, I edited the c:\bin\alfresco\alfresco.bat file and put 'rem' in front of the second JAVA_OPTS set as I am using Java 6. # Now after you run it for the first time and the database structure gets created, you can't restart it because you get: {noformat} java.sql.SQLException: Column names in each table must be unique. Column name 'ID_' in table 'JBPM_ACTION' is specified more than once. {noformat} Sigh, so in order to keep Alfresco from hurting itself, I had to turn off the schema updates. This is done by editing the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions\custom-repository.properties and adding the following: {noformat} db.schema.update=false {noformat} and then restarting alfresco. # To install Alfresco as a Windows Service use a command prompt and enter the following: {noformat} cd c:\bin\alfresco\tomcat\bin service.bat install alfresco tomcat5.exe //US//alfresco --DisplayName "Alfresco Server" tomcat5.exe //US//alfresco --JvmMs=512 --JvmMx=1024 --JvmSs=64 tomcat5.exe //US//alfresco --JavaHome=c:/bin/Java/jrockit-R27.4.0-jdk1.6.0_02 tomcat5.exe //US//alfresco --Environment ALF_HOME=c:/bin/alfresco/ tomcat5.exe //US//alfresco --Environment PATH=c:/bin/alfresco/bin;%PATH% tomcat5.exe //US//alfresco --StartPath c:/bin/alfresco --Startup auto {noformat} # To uninstall the service, at a later time, do the following: {noformat} cd c:\bin\alfresco\tomcat\bin service.bat uninstall alfresco {noformat} # To edit your service settings at any time: {noformat} cd c:\alfresco\tomcat\bin tomcat5w.exe //ES//alfresco {noformat} # In order to install certain modules (like the email listener), I had to get the Alfresco Module Manager from the customers.alfresco.com download site. I downloaded the alfresco-mmt-2.1.1.jar file locally so I could use it to install modules. # I then downloaded the email listener module from [http://forge.alfresco.com/projects/email-listener/]. It came as a zip file, so I unzipped it and it created a folder with the appropriate emailListener.amp in it. # Make another backup copy of the alfresco.war file and put somewhere in case you want to roll this back. # Open a command prompt windows and cd to the location where the Alfresco Module Manager jar is. # Run the following: {noformat} java -jar alfresco-mmt-2.1.1.jar path_to_emailListener.amp path_to_alfresco.war {noformat} So for me this looked like: {noformat} java -jar alfresco-mmt-2.1.1.jar .\email-listener_2.1RC2\emailListener.amp c:\bin\alfresco\tomcat\webapps\alfresco.war {noformat} # You should be able to verify the install by running: {noformat} java -jar alfresco-mmt-2.1.1.jar list c:\bin\alfresco\tomcat\webapps\alfresco.war {noformat} and you should see something like: {noformat} Module 'emailListener' installed in 'c:\bin\alfresco\tomcat\webapps\alfresco.war' - Title: EmailListener - Version: 2.1 - Install Date: Fri Dec 07 08:43:10 PST 2007 - Desription: EmailListener Module {noformat} # Finally, to start the service, just go into your Windows Service control panel and locate the service that is now named 'Alfresco Server'. You can start and stop Alfresco from this control panel. ]]> 3112990 3178526 "Downloads">"2.1 Releases">"2.1.1" # I then clicked on alfresco-enterprise-tomcat-2.1.1.zip to download the zip file. # Went to [http://customers.alfresco.com] (I was still logged in) # Went to "Company Home">"Downloads">"2.1 Releases">"2.1.1">"License Files" # I went ahead and downloaded all the "*.lic" files, but I think I only need enterprise-network-customer-unlimited.lic" # Logged out of Alfresco. # Since I suspect I will need a JDBC driver for SQLServer, I downloaded the jTDS-1.2.2 driver from the jtds web site (just Google jtds and go to the download section of the top google return). # I closed the Firefox browser. # I extracted the jtds-1.2.2.jar file from the jtds download # I downloaded and installed the JRockit 6 R27.4 JDK Microsoft Windows (x86 - 32 bit) from BEA's web site {note} After installing JRockit, make sure you set the JAVA_HOME environment variable to point to the installation of JRockit. For example, I went to the desktop, right clicked on the computer, did Properties, then clicked on the Advanced tab, then click on the environment variables button and then created a new system variable named JAVA_HOME and set to c:\bin\Java\jrockit-R27.4.0-jdk1.6.0_02 {note} # I ran the installer, changed the "Program Files" to "bin" in the installation directory for both the JDK and the JRE. I also chose to install the JRE as public. # Using Firefox, I downloaded the PHP 5.2.5 Windows Installer from php.net and installed it. Although I installed it, I did not integrate it with a web server as I want Alfresco to take port 80. I probably did not need to install PHP, but I thought I would anyway. (again, I changed install path from "Program Files" to "bin" # I also downloaded and installed OpenOffice and ran it once so I could get through the initial startup # I setup a Alfresco database on the server Solstice and granted the LAGOON\DB_Collaboration account to be the db_owner of the Alfresco database. # I unzipped the alfresco tomcat zip file to an alfresco directory in c:\bin # I then went to the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions directory for the customization of the server. ## I edited the custom-repository.properties file ### Changed the dir.root and dir.indexes to look like: {noformat} dir.root=//tornado.shore.mbari.org/Alfresco/alf_data dir.indexes=d:/alf_data/lucene-indexes {noformat} ### Commented out the db.* lines for the HSQL Connection (db.driver and db.url) ### Uncommented the db.* lines for MSSQL and changed to use the jTDS driver. They should look like: {noformat} db.driver=net.sourceforge.jtds.jdbc.Driver db.url=jdbc:jtds:sqlserver://solstice.shore.mbari.org/Alfresco;domain=SHORE;user=DB_Collaboration;password=XXXXXXXXX {noformat} ### I also added the following section to override the mail server settings {noformat} # Mail server configuration mail.host=mail.mbari.org mail.port=25 mail.username= mail.password= {noformat} ## Edited the custom-hibernate-dialect.properties file ### Commented out the HSQL Dialect ### Uncommented the MSSQL Dialect # I then installed the jtds-1.2.2.jar in the c:\bin\alfresco\tomcat\common\lib so that it will be on the classpath when Alfresco is started # Now this is not necessarily fun, but in order to really get it configured the way we want it, you need to pull the original .war file out, edit some stuff inside and re-create the .war. {note} This should all be done before starting Alfresco for the first time. {note} # Copy the c:\Alfresco\tomcat\webapps\alfresco.war file to your home directory. # Make a second copy so that you will always the original (I copied to alfresco.war.orig and moved it somewhere else. It is important to move it and have only the alfresco.war file in the directory because when you un-jar it, all the files go right where alfresco.war is.) # From a command line, un-jar the war file using: {noformat} jar -xvf alfresco.war {noformat} # This unpacks a lot of files and after it completes, move (or delete) the alfresco.war file from the directory. This needs to be done so it does not end up in the new .war file. # I wanted to change the "Company Home" that seems to be everywhere to something that says MBARI. ## Edited ./WEB-INF/classes/alfresco/messages/webclient.properties and changed company_home from 'Company Home' to 'MBARI' ## Edited ./WEB-INF/classes/alfresco/messages/webclient_en_US.properties and changed company_home from 'Company Home' to 'MBARI' ## I edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces.properties and changed the first two lines to read {noformat} spaces.company_home.name=MBARI spaces.company_home.description=The root space for MBARI {noformat} ## Edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces_en_US.properties and made the same changes as the previous step {tip} This took a bit to find all these, and to be honest, I am not sure which one actually made the change on the GUI, but I suspect it was the _en_US ones. {tip} # When users are imported via LDAP, user spaces get created automatically. In order to put them where I wanted them to go (instead of right in the Company Home), I edited the ./WEB-INF/classes/alfresco/authentication-services-context.xml file. In the file there is a bean with an name of personalHomeFolderProvider. There is a property name 'path' and I added {noformat} /${spaces.user_homes.childname} {noformat} to the end to try to get them to create the user spaces there instead of in the Company Home. The final bean XML looks like: {noformat} /${spaces.company_home.childname}/${spaces.user_homes.childname} ${spaces.store} false All All {noformat} # I wanted to change the logo that is used. I attached the replacement logo [here|^AlfrescoLogo32.png]. Copy this to ./images/logo and overwrite the one that is there. # In order to setup SSL for the application (will do that later), edit ./WEB-INF/web.xml and add the following {noformat} Login Pages /* CONFIDENTIAL {noformat} right before the ending tag at the bottom of the file. # Now in order to change the default behavior so that all content is versioned from the start, I edited the .\WEB-INF\classes\alfresco\model\contentModel.xml and searched for the content type definition block. {noformat} Content cm:cmobject true d:content false true false true {noformat} and added the following block right before the ending tag: {noformat} cm:versionable {noformat} so the final block looks like: {noformat} Content cm:cmobject true d:content false true false true cm:versionable {noformat} # That takes care of all the changes to the WAR file. We can now put it back into .war form. # While you are in the directory you expanded the war file in, run ## jar cvfm alfresco.war META-INF\MANIFEST.MF . # You should now have an alfresco.war file in the directory. Move that back to the alfresco install and overwrite the existing one. # Most users like the details view, so I set the default to that by editing c:\Alfresco\tomcat\shared\classes\alfresco\extensions/web-client-config-custom.xml and added: {noformat} details 20
20
20 {noformat} right before the closing tag. # Now in order to use MBARI accounts, NTLM authentication was turned on and then chained with the native Alfresco accounts so that we could have non-MBARI accounts on the Alfresco server. ## In order to enable NTLM and native Alfresco authentication, I had to edit two files. For simplicity I have just attached them here and they can be downloaded and installed in the extensions directory. ### The first file is the [ntlm-authentication-context.xml|^ntlm-authentication-context.xml] file. This configures and enables NTLM authentication. ### The next file was the [chaining-authentication-context.xml|^chaining-authentication-context.xml] file which enabled Alfresco authentication and chained it together with the NTLM authentication from the previous file. # Then in order to setup CIFS on the server, I edited the file-servers-custom.xml file to look like the attached [file-servers-custom.xml|^file-servers-custom.xml] file. # In order to grant certain accounts admin privs, I created a new custom-authority-services-context.xml in the same directory as the ldap-authentication-context.xml file and added {noformat} kgomes admin administrator {noformat} # In order for Alfresco to handle all port 80 traffic, I changed Tomcat so that it takes port 80 and SSL goes over port 443. So I edited the c:\Alfresco\tomcat\conf\server.xml file and changed the 8080 port to 80 and the 8443 port to 443 (the 443 change is done in two places). # Now I needed to setup the SSL for the web traffic. Cathy Sewell was instrumental in getting this working. She ordered a new certificate specifically for alfresco and put it in the c:\local\cert folder. Here are the instructions for what she did to get the certficate installed. {noformat} SSL certificate for server Alfresco - 1/2/08 C:\bin\Java\jrockit-R27.1.0-jre1.6.0_02\bin>keytool -genkey -alias tomcat -keyalg RSA -keystore tomcat.keystore What is your first and last name? [alfresco.mbari.org]: What is the name of your organizational unit? [IS]: What is the name of your organization? [MBARI]: What is the name of your City or Locality? [Moss Landing]: What is the name of your State or Province? [CD]: CA What is the two-letter country code for this unit? [US]: Is CN=alfresco.mbari.org, OU=IS, O=MBARI, L=Moss Landing, ST=CA, C=US correct? [no]: y Enter key password for (RETURN if same as keystore password): C:\bin\Java\jrockit-R27.4.0-jre1.6.0_02\bin>keytool -certreq -keyalg RSA -alias tomcat -file certreq.csr -keystore tomcat.keystore Enter keystore password: Generated certificate request file, certreq.csr, was submitted to SSL provider. Certificate provider sent certificate file (alfresco.mbari.org.crt), along with gd_bundle.crt, gd_cross_intermediate.crt, and gd_intermediate.crt. Additionally, I downloaded valicert_class2_root.cer from their website. These files were stored in c:\local\cert. The following commands were used to add them to the tomcat keystore: C:\bin\Java\jrockit-R27.4.0-jre1.6.0_02\bin>keytool -import -alias root -keystore tomcat.keystore -trustcacerts -file c:\local\cert\valicert_class2_root.cer Enter keystore password: Certificate already exists in system-wide CA keystore under alias Do you still want to add it to your own keystore? [no]: y Certificate was added to keystore C:\bin\Java\jrockit-R27.4.0-jre1.6.0_02\bin>keytool -import -alias cross -keystore tomcat.keystore -trustcacerts -file c:\local\cert\gd_cross_intermediate.crt Enter keystore password: Certificate was added to keystore C:\bin\Java\jrockit-R27.4.0-jre1.6.0_02\bin>keytool -import -alias intermed -keystore tomcat.keystore -trustcacerts -file c:\local\cert\gd_intermediate.crt Enter keystore password: Certificate was added to keystore C:\bin\Java\jrockit-R27.4.0-jre1.6.0_02\bin>keytool -import -alias tomcat -keystore tomcat.keystore -trustcacerts -file c:\local\cert\alfresco.mbari.org.crt Enter keystore password: Certificate reply was installed in keystore Adjustment of the server.xml file was left to Kevin. {noformat} #I edited the c:\bin\alfresco\tomcat\conf\server.xml file and uncommented the SSL section and edited to look like that shown below. {noformat} {noformat} # Since I was in the server.xml file, I went ahead and changed it so that the default webapp was alfresco so that you would get alfresco anytime you went to the base URL. I did this by adding: {noformat} {noformat} as the last line of the tag section (right before the closing tag). {note} You will also notice the Valve tag that I had to add to turn off proxy cache disabling so that IE clients would work correctly over SSL. Gotta love M$. {note} # I copied the enterprise-network-unlimited.lic file into the c:\Alfresco\tomcat\shared\classes\alfresco\extensions\license directory # Just to keep things clean, I edited the c:\bin\alfresco\alfresco.bat file and put 'rem' in front of the second JAVA_OPTS set as I am using Java 6. # Now after you run it for the first time and the database structure gets created, you can't restart it because you get: {noformat} java.sql.SQLException: Column names in each table must be unique. Column name 'ID_' in table 'JBPM_ACTION' is specified more than once. {noformat} Sigh, so in order to keep Alfresco from hurting itself, I had to turn off the schema updates. This is done by editing the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions\custom-repository.properties and adding the following: {noformat} db.schema.update=false {noformat} and then restarting alfresco. # To install Alfresco as a Windows Service use a command prompt and enter the following: {noformat} cd c:\bin\alfresco\tomcat\bin service.bat install alfresco tomcat5.exe //US//alfresco --DisplayName "Alfresco Server" tomcat5.exe //US//alfresco --JvmMs=512 --JvmMx=1024 --JvmSs=64 tomcat5.exe //US//alfresco --JavaHome=c:/bin/Java/jrockit-R27.4.0-jdk1.6.0_02 tomcat5.exe //US//alfresco --Environment ALF_HOME=c:/bin/alfresco/ tomcat5.exe //US//alfresco --Environment PATH=c:/bin/alfresco/bin;%PATH% tomcat5.exe //US//alfresco --StartPath c:/bin/alfresco --Startup auto {noformat} # To uninstall the service, at a later time, do the following: {noformat} cd c:\bin\alfresco\tomcat\bin service.bat uninstall alfresco {noformat} # To edit your service settings at any time: {noformat} cd c:\alfresco\tomcat\bin tomcat5w.exe //ES//alfresco {noformat} # In order to install certain modules (like the email listener), I had to get the Alfresco Module Manager from the customers.alfresco.com download site. I downloaded the alfresco-mmt-2.1.1.jar file locally so I could use it to install modules. # I then downloaded the email listener module from [http://forge.alfresco.com/projects/email-listener/]. It came as a zip file, so I unzipped it and it created a folder with the appropriate emailListener.amp in it. # Make another backup copy of the alfresco.war file and put somewhere in case you want to roll this back. # Open a command prompt windows and cd to the location where the Alfresco Module Manager jar is. # Run the following: {noformat} java -jar alfresco-mmt-2.1.1.jar path_to_emailListener.amp path_to_alfresco.war {noformat} So for me this looked like: {noformat} java -jar alfresco-mmt-2.1.1.jar .\email-listener_2.1RC2\emailListener.amp c:\bin\alfresco\tomcat\webapps\alfresco.war {noformat} # You should be able to verify the install by running: {noformat} java -jar alfresco-mmt-2.1.1.jar list c:\bin\alfresco\tomcat\webapps\alfresco.war {noformat} and you should see something like: {noformat} Module 'emailListener' installed in 'c:\bin\alfresco\tomcat\webapps\alfresco.war' - Title: EmailListener - Version: 2.1 - Install Date: Fri Dec 07 08:43:10 PST 2007 - Desription: EmailListener Module {noformat} # Finally, to start the service, just go into your Windows Service control panel and locate the service that is now named 'Alfresco Server'. You can start and stop Alfresco from this control panel. ]]> 3112992 3178500 "Downloads">"2.1 Releases">"2.1.1" # I then clicked on alfresco-enterprise-tomcat-2.1.1.zip to download the zip file. # Went to [http://customers.alfresco.com] (I was still logged in) # Went to "Company Home">"Downloads">"2.1 Releases">"2.1.1">"License Files" # I went ahead and downloaded all the "*.lic" files, but I think I only need enterprise-network-customer-unlimited.lic" # Logged out of Alfresco. # Since I suspect I will need a JDBC driver for SQLServer, I downloaded the jTDS-1.2.2 driver from the jtds web site (just Google jtds and go to the download section of the top google return). # I closed the Firefox browser. # I extracted the jtds-1.2.2.jar file from the jtds download # I downloaded and installed the JRockit 6 R27.4 JDK Microsoft Windows (x86 - 32 bit) from BEA's web site {note} After installing JRockit, make sure you set the JAVA_HOME environment variable to point to the installation of JRockit. For example, I went to the desktop, right clicked on the computer, did Properties, then clicked on the Advanced tab, then click on the environment variables button and then created a new system variable named JAVA_HOME and set to c:\bin\Java\jrockit-R27.4.0-jdk1.6.0_02 {note} # I ran the installer, changed the "Program Files" to "bin" in the installation directory for both the JDK and the JRE. I also chose to install the JRE as public. # Using Firefox, I downloaded the PHP 5.2.5 Windows Installer from php.net and installed it. Although I installed it, I did not integrate it with a web server as I want Alfresco to take port 80. I probably did not need to install PHP, but I thought I would anyway. (again, I changed install path from "Program Files" to "bin" # I also downloaded and installed OpenOffice and ran it once so I could get through the initial startup # I setup a Alfresco database on the server Solstice and granted the LAGOON\DB_Collaboration account to be the db_owner of the Alfresco database. # I unzipped the alfresco tomcat zip file to an alfresco directory in c:\bin # I then went to the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions directory for the customization of the server. ## I edited the custom-repository.properties file ### Changed the dir.root and dir.indexes to look like: {noformat} dir.root=//tornado.shore.mbari.org/Alfresco/alf_data dir.indexes=d:/alf_data/lucene-indexes {noformat} ### Commented out the db.* lines for the HSQL Connection (db.driver and db.url) ### Uncommented the db.* lines for MSSQL and changed to use the jTDS driver. They should look like: {noformat} db.driver=net.sourceforge.jtds.jdbc.Driver db.url=jdbc:jtds:sqlserver://solstice.shore.mbari.org/Alfresco;domain=SHORE;user=DB_Collaboration;password=XXXXXXXXX {noformat} ### I also added the following section to override the mail server settings {noformat} # Mail server configuration mail.host=mail.mbari.org mail.port=25 mail.username= mail.password= {noformat} ## Edited the custom-hibernate-dialect.properties file ### Commented out the HSQL Dialect ### Uncommented the MSSQL Dialect # I then installed the jtds-1.2.2.jar in the c:\bin\alfresco\tomcat\common\lib so that it will be on the classpath when Alfresco is started # Now this is not necessarily fun, but in order to really get it configured the way we want it, you need to pull the original .war file out, edit some stuff inside and re-create the .war. {note} This should all be done before starting Alfresco for the first time. {note} # Copy the c:\Alfresco\tomcat\webapps\alfresco.war file to your home directory. # Make a second copy so that you will always the original (I copied to alfresco.war.orig and moved it somewhere else. It is important to move it and have only the alfresco.war file in the directory because when you un-jar it, all the files go right where alfresco.war is.) # From a command line, un-jar the war file using: {noformat} jar -xvf alfresco.war {noformat} # This unpacks a lot of files and after it completes, move (or delete) the alfresco.war file from the directory. This needs to be done so it does not end up in the new .war file. # I wanted to change the "Company Home" that seems to be everywhere to something that says MBARI. ## Edited ./WEB-INF/classes/alfresco/messages/webclient.properties and changed company_home from 'Company Home' to 'MBARI' ## Edited ./WEB-INF/classes/alfresco/messages/webclient_en_US.properties and changed company_home from 'Company Home' to 'MBARI' ## I edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces.properties and changed the first two lines to read {noformat} spaces.company_home.name=MBARI spaces.company_home.description=The root space for MBARI {noformat} ## Edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces_en_US.properties and made the same changes as the previous step {tip} This took a bit to find all these, and to be honest, I am not sure which one actually made the change on the GUI, but I suspect it was the _en_US ones. {tip} # When users are imported via LDAP, user spaces get created automatically. In order to put them where I wanted them to go (instead of right in the Company Home), I edited the ./WEB-INF/classes/alfresco/authentication-services-context.xml file. In the file there is a bean with an name of personalHomeFolderProvider. There is a property name 'path' and I added {noformat} /${spaces.user_homes.childname} {noformat} to the end to try to get them to create the user spaces there instead of in the Company Home. The final bean XML looks like: {noformat} /${spaces.company_home.childname}/${spaces.user_homes.childname} ${spaces.store} false All All {noformat} # I wanted to change the logo that is used. I attached the replacement logo [here|^AlfrescoLogo32.png]. Copy this to ./images/logo and overwrite the one that is there. # In order to setup SSL for the application (will do that later), edit ./WEB-INF/web.xml and add the following {noformat} Login Pages /* CONFIDENTIAL {noformat} right before the ending tag at the bottom of the file. # Now in order to change the default behavior so that all content is versioned from the start, I edited the .\WEB-INF\classes\alfresco\model\contentModel.xml and searched for the content type definition block. {noformat} Content cm:cmobject true d:content false true false true {noformat} and added the following block right before the ending tag: {noformat} cm:versionable {noformat} so the final block looks like: {noformat} Content cm:cmobject true d:content false true false true cm:versionable {noformat} # That takes care of all the changes to the WAR file. We can now put it back into .war form. # While you are in the directory you expanded the war file in, run ## jar cvfm alfresco.war META-INF\MANIFEST.MF . # You should now have an alfresco.war file in the directory. Move that back to the alfresco install and overwrite the existing one. # Most users like the details view, so I set the default to that by editing c:\Alfresco\tomcat\shared\classes\alfresco\extensions/web-client-config-custom.xml and added: {noformat} details 20
20
20 {noformat} right before the closing tag. # Now in order to use MBARI accounts, NTLM authentication was turned on and then chained with the native Alfresco accounts so that we could have non-MBARI accounts on the Alfresco server. ## In order to enable NTLM and native Alfresco authentication, I had to edit two files. For simplicity I have just attached them here and they can be downloaded and installed in the extensions directory. ### The first file is the [ntlm-authentication-context.xml|^ntlm-authentication-context.xml] file. This configures and enables NTLM authentication. ### The next file was the [chaining-authentication-context.xml|^chaining-authentication-context.xml] file which enabled Alfresco authentication and chained it together with the NTLM authentication from the previous file. # Then in order to setup CIFS on the server, I edited the file-servers-custom.xml file to look like the attached [file-servers-custom.xml|^file-servers-custom.xml] file. # In order to grant certain accounts admin privs, I created a new custom-authority-services-context.xml in the same directory as the ldap-authentication-context.xml file and added {noformat} kgomes admin administrator {noformat} # In order for Alfresco to handle all port 80 traffic, I changed Tomcat so that it takes port 80 and SSL goes over port 443. So I edited the c:\Alfresco\tomcat\conf\server.xml file and changed the 8080 port to 80 and the 8443 port to 443 (the 443 change is done in two places). # Now I needed to setup the SSL for the web traffic. Cathy Sewell was instrumental in getting this working. She ordered a new certificate specifically for alfresco and put it in the c:\local\cert folder. I edited the c:\bin\alfresco\tomcat\conf\server.xml file and uncommented the SSL section and edited to look like that shown below. {noformat} {noformat} # Since I was in the server.xml file, I went ahead and changed it so that the default webapp was alfresco so that you would get alfresco anytime you went to the base URL. I did this by adding: {noformat} {noformat} as the last line of the tag section (right before the closing tag). # I copied the enterprise-network-unlimited.lic file into the c:\Alfresco\tomcat\shared\classes\alfresco\extensions\license directory # Just to keep things clean, I edited the c:\bin\alfresco\alfresco.bat file and put 'rem' in front of the second JAVA_OPTS set as I am using Java 6. # Now after you run it for the first time and the database structure gets created, you can't restart it because you get: {noformat} java.sql.SQLException: Column names in each table must be unique. Column name 'ID_' in table 'JBPM_ACTION' is specified more than once. {noformat} Sigh, so in order to keep Alfresco from hurting itself, I had to turn off the schema updates. This is done by editing the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions\custom-repository.properties and adding the following: {noformat} db.schema.update=false {noformat} and then restarting alfresco. # To install Alfresco as a Windows Service use a command prompt and enter the following: {noformat} cd c:\bin\alfresco\tomcat\bin service.bat install alfresco tomcat5.exe //US//alfresco --DisplayName "Alfresco Server" tomcat5.exe //US//alfresco --JvmMs=512 --JvmMx=1024 --JvmSs=64 tomcat5.exe //US//alfresco --JavaHome=c:/bin/Java/jrockit-R27.4.0-jdk1.6.0_02 tomcat5.exe //US//alfresco --Environment ALF_HOME=c:/bin/alfresco/ tomcat5.exe //US//alfresco --Environment PATH=c:/bin/alfresco/bin;%PATH% tomcat5.exe //US//alfresco --StartPath c:/bin/alfresco --Startup auto {noformat} # To uninstall the service, at a later time, do the following: {noformat} cd c:\bin\alfresco\tomcat\bin service.bat uninstall alfresco {noformat} # To edit your service settings at any time: {noformat} cd c:\alfresco\tomcat\bin tomcat5w.exe //ES//alfresco {noformat} # In order to install certain modules (like the email listener), I had to get the Alfresco Module Manager from the customers.alfresco.com download site. I downloaded the alfresco-mmt-2.1.1.jar file locally so I could use it to install modules. # I then downloaded the email listener module from [http://forge.alfresco.com/projects/email-listener/]. It came as a zip file, so I unzipped it and it created a folder with the appropriate emailListener.amp in it. # Make another backup copy of the alfresco.war file and put somewhere in case you want to roll this back. # Open a command prompt windows and cd to the location where the Alfresco Module Manager jar is. # Run the following: {noformat} java -jar alfresco-mmt-2.1.1.jar path_to_emailListener.amp path_to_alfresco.war {noformat} So for me this looked like: {noformat} java -jar alfresco-mmt-2.1.1.jar .\email-listener_2.1RC2\emailListener.amp c:\bin\alfresco\tomcat\webapps\alfresco.war {noformat} # You should be able to verify the install by running: {noformat} java -jar alfresco-mmt-2.1.1.jar list c:\bin\alfresco\tomcat\webapps\alfresco.war {noformat} and you should see something like: {noformat} Module 'emailListener' installed in 'c:\bin\alfresco\tomcat\webapps\alfresco.war' - Title: EmailListener - Version: 2.1 - Install Date: Fri Dec 07 08:43:10 PST 2007 - Desription: EmailListener Module {noformat} # Finally, to start the service, just go into your Windows Service control panel and locate the service that is now named 'Alfresco Server'. You can start and stop Alfresco from this control panel. ]]> 3112964 9404513 9371758 25428255 25395487 25428257 4.4: [https://confluence.atlassian.com/display/JIRA044/Migrating+JIRA+to+Another+Server] h5. Steps # (/) Create new VM named bugs.mbari.org in the DMZ # (/) Have Neil create database JIRA_Temp on solstice2.shore.mbari.org # (/) Have Neil create database JIRA on solstice2.shore.mbari.org # (/) Have Pat install Java 7 on bugs.shore.mbari.org # (/) Have Pete plumb holes through firewall so processes on bugs.mbari.org can get to Solstice2 # (/) Have Pat create DB_Collaboration account on bugs so it can run JIRA under that account and it can connect to solstice2 using that NT Domain account. # (/) Upgrade license on Atlassian site # Run a test upgrade: ## Upgrade from 3.12.1 -> 4.4.5 (this will actually be what they call a 'migration') ### From the Administrator's page in JIRA, perform a 'Backup Data to XML'. ### Login in to oceana.mbari.org as root ### Create a tar.gz of the JIRA home directory on ocean.mbari.org which is located at /data/jira_3_12 ## Upgrade from 4.4.5 -> 6.2 (latest): # Run the production upgrade: ]]> 25395489 5865629 D0 52.08 52.08 \+0 \+0.00 D0->D1 104.17 104.17 \+0 \+0.00 D1->D2 156.25 156.25 \+0 \+0.00 D2->D3 208.33 208.33 \+0 \+0.00 D3->D4 260.42 260.42 \+0 \+0.00 D4->D5 312.50 312.50 \+0 \+0.00 D5->D6 364.58 364.58 \+0 \+0.00 D6->D7 416.67 416.67 \+0 \+0.00 D7->stopbit 468.75 468.75 \+0 \+0.00 end of stopb 520.83 520.83 \+0 \+0.00 \*/ UBR00=0xC0; UBR10=0x00; UMCTL0=0x00; /\* uart0 3686400Hz 19200bps \*/ UBR01=0xC0; UBR11=0x00; UMCTL1=0x00; /\* uart1 3686400Hz 19200bps \*/ h4. The simplest way to use the USART in UART mode is this: interrupt is not enabled, the software checks if it can output the next byte (UTXIFG = 1), and if a new character has been received (URXIFG = 1). \\ h4. Modbus Register Map * REG_INPUT_START         512         // input registers start at 512 * REG_INPUT_NREGS         8           // 8x16 bit registers * REG_SOLENOIDS_A        0            // Holding registers start at 0 (16 coils for each A and B) * REG_SOLENOIDS_B        1   * REG_HOLDING_START    0           // to match WAGO * REG_HOLDING_NREGS   40         // 40 is more than actual (2) * REG_COILS_START         0           // read individual coils (was 1000) * REG_COILS_SIZE           32          // 32 coils * REG_DISC_START          0           // discrete (was 1000) * REG_DISC_SIZE             32          // 32 coils \\ h3. ---- MODBUS * Commands ** Read Input Register (0x04) ** Read Holding Registers (0x03) ** Write Single Register (0x06) ** Write Multiple Registers (0x10) ** Read/Write Multiple Registers (0x17) ** Read Coils (0x01) ** Write Single Coil (0x05) ** Write Multiple Coils (0x0F) ** Read Discrete Inputs (0x02) ** Report Slave ID (0x11)   * Address * Slave ID  * Berlios ModBus Stack ** The modbus stack is config'd in {color:#0000ff}mbconfig.h{color} which is located in vpc\modbus\include \\ \\ ---- h3. Debugging MSP430 h4. Starting gdbproxy The next step is starting gdbproxy, which is responsible for the communication between GDB and the FET: msp430-gdbproxy \--port=2000 msp430 If your FET is properly connected to the parallel port, you should see a message like the following: info: msp430: Target device is a 'MSP430F12x' (type 11) notice: msp430-gdbproxy: waiting on TCP port 2000 h4. Using Insight (Windows) After you have started Insight (c:\msp430\bin\msp430-gdb.exe), click on "File->Open" and select the elf-file (e.g. "test.elf") you want to debug. Now click on "Run->Connect to target" and enter the following settings: Target: "Remote/TCP" Hostname: "localhost" Port: "2000" Set breakpoint at 'main': yes Set breakpoint at 'exit': yes Attach to target: yes Download Program: yes Command after attaching: "monitor erase all" Run Method: Continue from last Stop When you click on "Ok" Insight should tell you that the connection was successful, and gdbproxy should say "notice: msp430-gdbproxy: connected". To start the debugging click on "Run" or simply press "r". If everything worked correctly you should now see the sourcecode of your program with the first line of main() marked green. The red point is the breakpoint that has been set by Insight automatically. You can set or remove breakpoints by clicking on the '-' in front of the line. Now you can 'c'ontinue the execution to the next breakpoint, 's'tep through the code, or step a single assembler instruction... but be careful with "finish": Insight sometimes seems to lock up with this command. So if you want to finish a function, I recommend setting a breakpoint to the end of the function and using "continue". \\ h2. Installing the Compiler Tool Chain To obtain and install the compiler: # Go to the MSPGCC download page and obtain the latest MSPGCC installation. I used the 'mspgcc-20040723.exe' download which installed everything I needed for a Win32 setup. \\ # This step need only be performed if you wish to use the graphical version of GDB. The latest MSPGCC download only includes the command line GDB debugger. I prefer to use the graphical version called Insight. A slightly older prebuilt version of Insight can be used. Install this older version of insight into a different directory to that chosen for the latest MSPGCC installation as you don't want to overwrite the files obtained in step 1. \\ You should now have two installations. The latest version of MSPGCC installed during step 1, and a slightly older version of Insight from step 2. Both versions of the GDB debugger are called msp430-gdb.exe so one needs to be renamed. Locate the older version msp430-gdb.exe from the files installed during this step and rename it msp430-insight.exe. \\ # Ensure the BIN directory from the files installed during step 1 and the BIN directory from the files installed during step 2 are included in your PATH environment variable. \\ \\ # The MSPGCC download includes a program called msp430-gdbproxy.exe. This intercepts the GDB TCP commands and redirects them to the parallel port. Start msp430-gdbproxy (a shortcut to this will have been placed on the start menu when MSPGCC was installed). By default msp430-gdbproxy uses port 3333 - do not change this. \\ # Program the flash as per the instruction in the section above. The flash can be programmed from within GDB but it is much faster to do it separately and beforehand. \\ # Start the debugger using the command ... msp430-insight a.out... the commands in the gdb.ini file will do the rest. If you prefer to use the command line debugger simply replace msp430-insight with msp430-gdb. \\ # Insight will start at and the program will stop at the breakpoint in main() as shown below. \\ MSP430 Clocking \\ MSP430 Basic Clock Module * Clock Signals: ** *ACLK*: Auxiliary clock. The signal is sourced from LFXT1CLK with a divider of 1, 2, 4, or 8. (The calibration program for the serial link sets the divider to 4, but after the calibration it can be changed to any other values.) ACLK can be used as the clock signal for Timer A and Timer B. ** *MCLK*: Master clock. The signal can be sourced from LFXT1CLK, XT2CLK (if available), or DCOCLK with a divider of 1, 2, 4, or 8. MCLK is used by the CPU and system. ** *SMCLK*: Sub-main clock. The signal is sourced from either XT2CLK (if available), or DCOCLK with a divider of 1, 2, 4, or 8. SMCLK can be used as the clock signal for Timer A and Timer B. * MSP430 Clocking pictorial: *   * \\ !MSP430_clocking2.JPG!                  !MSP430_BCSCTL1.JPG! !MSP430_BCSCTL2.JPG!\\ \\]]> 5832868 9404533 9371778 21398243 21365521 9404535 9371780 15663410 15630652 15663398 15630639 25952324 25919556 15663400 15630641 25952323 25919555 15663420 15630662 15663411 15630653 15663418 15630660 19072156 19039416 15663440 15630683 19072158 19039418 15663442 15630685 25952304 25919536 15663436 15630679 19072159 19039419 19072162 19039422 11829371 11796612 15663438 15630681 19072161 19039421 11829370 11796611 15663431 15630674 19072148 19039408 15663432 15630675 19072150 19039410 15663434 15630677 19072152 19039412 19072154 19039414 19072139 19039399 25952315 25919547 15663455 15630698 19072140 127.0.0.1 8443 8443 {noformat} Add SSL section: {noformat} 8443 /usr/local/keystore/keystore Refer to jetty.xml to see password Refer to jetty.xml to see password {noformat} h3. Start Bamboo using jetty.xml Edit the file /opt/Bamboo/conf/wrapper.conf {noformat}sudo chmod a+w /opt/Bamboo/conf/wrapper.conf{noformat} # Comment out the following lines: #* {noformat}#wrapper.app.parameter.2=8085 #wrapper.app.parameter.3=../webapp #wrapper.app.parameter.4=/{noformat} # Add the following line: {noformat}wrapper.app.parameter.2=webapp/WEB-INF/classes/jetty.xml{noformat} h3. Configure Crowd It's way easier to configure now. Follow the instructions at https://confluence.atlassian.com/display/BAMBOO/Integrating+Bamboo+with+Crowd ]]> 19039400 15663458 15630701 25952317 25919549 15663457 15630700 25952319 25919551 15663451 15630694 19072144 19039404 19072145 19039405 25952321 25919553 15663453 15630696 19072146 19039406 15663447 15630690 15663449 15630692 25952311 25919543 19072136 127.0.0.1 8443 8443 {noformat} Add SSL section: {noformat} 8443 /usr/local/keystore/keystore Refer to jetty.xml to see password Refer to jetty.xml to see password {noformat} h3. Start Bamboo using jetty.xml Edit the file /opt/Bamboo/conf/wrapper.conf {noformat}sudo chmod a+w /opt/Bamboo/conf/wrapper.conf{noformat} # Comment out the following lines: #* {noformat}#wrapper.app.parameter.2=8085 #wrapper.app.parameter.3=../webapp #wrapper.app.parameter.4=/{noformat} # Add the following line: {noformat}wrapper.app.parameter.2=webapp/WEB-INF/classes/jetty.xml{noformat} ]]> 19039396 19072137 127.0.0.1 8443 8443 {noformat} Add SSL section: {noformat} 8443 /usr/local/keystore/keystore Refer to jetty.xml to see password Refer to jetty.xml to see password {noformat} h3. Start Bamboo using jetty.xml Edit the file /opt/Bamboo/conf/wrapper.conf {noformat}sudo chmod a+w /opt/Bamboo/conf/wrapper.conf{noformat} # Comment out the following lines: #* {noformat}#wrapper.app.parameter.2=8085 #wrapper.app.parameter.3=../webapp #wrapper.app.parameter.4=/{noformat} # Add the following line: {noformat}wrapper.app.parameter.2=webapp/WEB-INF/classes/jetty.xml{noformat} h3. Configure Crowd It's way easier to configure now. Follow the instructions at https://confluence.atlassian.com/display/BAMBOO/Integrating+Bamboo+with+Crowd ]]> 19039397 25952313 25919545 15663445 15630688 15663473 15630716 15663474 15630717 15663472 15630715 15663469 15630712 15663470 15630713 15663467 15630710 15663465 15630708 15663463 15630706 15663461 15630704 15663462 15630705 15663459 15630702 15663490 15630733 15663489 15630732 15663487 15630730 15663485 15630728 9404905 9372164 15663483 15630726 15663482 15630725 15663480 15630723 19072163 19039423 15663478 15630721 21398402 21365686 21398401 21365685 15663476 15630719 21398399 21365683 15663492 15630735 15663494 15630737 15663496 15630739 15663498 15630741 15663499 15630742 15663502 15630745 15663501 15630744 15663504 15630747 15663503 15630746 21398403 21365687 15663506 15630749 15663505 15630748 15663507 15630750 15663508 15630751 18645540 18580033 19072121 19039380 9831435 9798696 21398447 21365733 19072120 19039379 21398445 21365731 21398444 21365730 19072115 19039374 19072129 127.0.0.1 8443 8443 {noformat} Add SSL section: {noformat} 8443 /usr/local/keystore/keystore Refer to jetty.xml to see password Refer to jetty.xml to see password {noformat}]]> 19039388 19072127 127.0.0.1 8443 8443 {noformat} Add SSL section: {noformat} 8443 /usr/local/keystore/keystore Refer to jetty.xml to see password Refer to jetty.xml to see password {noformat]]> 19039386 9831427 9798688 9831433 9798694 19072126 19039385 19072123 19039382 9831431 9798692 19072124 19039383 19072105 19039364 19072103 19039362 19072101 19039360 19072112 19039371 19072110 19039369 19072109 19039368 19072107 19039366 18645619 \[1,1H is the string command to move the cursor to row1,column1. Then (0x0B) is used to move relative for text appearing on line, 2,3 and 4.  Note that if any garbage exists/gets written to character cells not normally written to during operation (ie in positions beyond end of line, it will remain there. The vorneTask makes an attempt to clear all character position by writing to all lines/cells on startup.   \\ \\]]> 18580112 18645621 characters. Then control goes into a forever loop, reading those dm items, formatting them for output via serial port, and then sleeping for .9 seconds. Some points to note.... depth items is produced from pressure and ships lat, using standard algorithms by another navproc task (depthCalcTask()).  Rov Lat/Lon is likewise produced by  the navproc rovPositionTask() from winfrog serial data. The specific datamanger item names consumed are defined in dvecsIntfc.h. {color:#ff0000}*\**{color}{color:#ff0000}*\**NOTE THIS NEEDS TO BE RESOLVED FOR MIGRATION TO Rachel Carson... Vorne did not exist on Pt.Lobos/Ventana and the items names are different \! **{color}{color:#ff0000}*\**{color} The vorneTask() uses the old VT102 ascii terminal command syntax to position the cursor.  \[1,1H is the string command to move the cursor to row1,column1. Then (0x0B) is used to move relative for text appearing on line, 2,3 and 4.  Note that if any garbage exists/gets written to character cells not normally written to during operation (ie in positions beyond end of line, it will remain there. The vorneTask makes an attempt to clear all character position by writing to all lines/cells on startup.   \\ \\]]> 18580114 9404764 9372016 9404763 9372015 18645623 characters. Then control goes into a forever loop, reading those dm items, formatting them for output via serial port, and then sleeping for .9 seconds. Some points to note.... # depth items is produced from pressure and ships lat, using standard algorithms by another navproc task (depthCalcTask()).  # Rov Lat/Lon is likewise produced by  the navproc rovPositionTask() from winfrog serial data. The specific datamanger item names consumed are defined in dvecsIntfc.h.{color:#ff0000}*\**{color}{color:#ff0000}\***NOTE THIS NEEDS TO BE RESOLVED FOR MIGRATION TO Rachel Carson... Vorne did not exist on Pt.Lobos/Ventana and the items names are different \! \*\*{color}{color:#ff0000}*\**{color} # The vorneTask() uses the old VT102 ascii terminal command syntax to position the cursor.  \[1,1H is the string command to move the cursor to row1,column1. Then (0x0B) is used to move relative for text appearing on line, 2,3 and 4. # If any garbage exists/gets written to character cells not normally written to during operation (ie in positions beyond end of line, it will remain there. The vorneTask makes an attempt to clear all character position by writing to all lines/cells on startup, but not after that. # The vorne display has significant lag in the time it takes to render the screen.... the serial write is practically immediate; the internal rendering of all the character positions takes perhaps a half-a-second or more.  \\]]> 18580116 18645625 characters. Then control goes into a forever loop, reading those dm items, formatting them for output via serial port, and then sleeping for .9 seconds. Some points to note.... # depth items is produced from pressure and ships lat, using standard algorithms by another navproc task (depthCalcTask()).  # Rov Lat/Lon is likewise produced by  the navproc rovPositionTask() from winfrog serial data. The specific datamanger item names consumed are defined in dvecsIntfc.h.{color:#ff0000}*\**{color}{color:#ff0000}\***NOTE THIS NEEDS TO BE RESOLVED FOR MIGRATION TO Rachel Carson... Vorne did not exist on Pt.Lobos/Ventana and the items names are different \! \*\*{color}{color:#ff0000}*\**{color} # The vorneTask() uses the old VT102 ascii terminal command syntax to position the cursor.  \[1,1H is the string command to move the cursor to row1,column1. Then (0x0B) is used to move relative for text appearing on line, 2,3 and 4. # If any garbage exists/gets written to character cells not normally written to during operation (ie in positions beyond end of line, it will remain there. The vorneTask makes an attempt to clear all character position by writing to all lines/cells on startup, but not after that. # The vorne display has significant lag in the time it takes to render the screen.... the serial write is practically immediate; the internal rendering of all the character positions takes perhaps a half-a-second or more.  \\]]> 18580118 18645627 characters. Then control goes into a forever loop, reading those dm items, formatting them for output via serial port, and then sleeping for .9 seconds. Some points to note.... # depth items is produced from pressure and ships lat, using standard algorithms by another navproc task (depthCalcTask()).  # Rov Lat/Lon is likewise produced by  the navproc rovPositionTask() from winfrog serial data. The specific datamanger item names consumed are defined in dvecsIntfc.h.{color:#ff0000}*\**{color}{color:#ff0000}\***NOTE THIS NEEDS TO BE RESOLVED FOR MIGRATION TO Rachel Carson... Vorne did not exist on Pt.Lobos/Ventana and the items names are different \! \*\*{color}{color:#ff0000}*\**{color} # The vorneTask() uses the old VT102 ascii terminal command syntax to position the cursor.  \[1,1H is the string command to move the cursor to row1,column1. Then (0x0B) is used to move relative for text appearing on line, 2,3 and 4. # If any garbage exists/gets written to character cells not normally written to during operation (ie in positions beyond end of line, it will remain there. The vorneTask makes an attempt to clear all character position by writing to all lines/cells on startup, but not after that. # The vorne display has significant lag in the time it takes to render the screen.... the serial write is practically immediate; the internal rendering of all the character positions takes perhaps a half-a-second or more.  \\]]> 18580120 18645629 characters. Then control goes into a forever loop, reading those dm items, formatting them for output via serial port, and then sleeping for .9 seconds. Some points to note.... # depth items is produced from pressure and ships lat, using standard algorithms by another navproc task (depthCalcTask()).  # Rov Lat/Lon is likewise produced by  the navproc rovPositionTask() from winfrog serial data. The specific datamanger item names consumed are defined in dvecsIntfc.h.{color:#ff0000}*\**{color}{color:#ff0000}\***NOTE THIS NEEDS TO BE RESOLVED FOR MIGRATION TO Rachel Carson... Vorne did not exist on Pt.Lobos/Ventana and the items names are different \! \*\*{color}{color:#ff0000}*\**{color} # The vorneTask() uses the old VT102 ascii terminal command syntax to position the cursor.  \[1,1H is the string command to move the cursor to row1,column1. Then (0x0B) is used to move relative for text appearing on line, 2,3 and 4. # If any garbage exists/gets written to character cells not normally written to during operation (ie in positions beyond end of line, it will remain there. The vorneTask makes an attempt to clear all character position by writing to all lines/cells on startup, but not after that. # The vorne display has significant lag in the time it takes to render the screen.... the serial write is practically immediate; the internal rendering of all the character positions takes perhaps a half-a-second or more.  \\]]> 18580122 18645630 characters. Then control goes into a forever loop, reading those dm items, formatting them for output via serial port, and then sleeping for .9 seconds. Some points to note.... # depth items is produced from pressure and ships lat, using standard algorithms by another navproc task (depthCalcTask()).  # Rov Lat/Lon is likewise produced by  the navproc rovPositionTask() from winfrog serial data. The specific datamanger item names consumed are defined in dvecsIntfc.h.{color:#ff0000}*\**{color}{color:#ff0000}\***NOTE THIS NEEDS TO BE RESOLVED FOR MIGRATION TO Rachel Carson... Vorne did not exist on Pt.Lobos/Ventana and the items names are different \! \*\*{color}{color:#ff0000}*\**{color} # The vorneTask() uses the old VT102 ascii terminal command syntax to position the cursor.  \[1,1H is the string command to move the cursor to row1,column1. Then (0x0B) is used to move relative for text appearing on line, 2,3 and 4. # If any garbage exists/gets written to character cells not normally written to during operation (ie in positions beyond end of line, it will remain there. The vorneTask makes an attempt to clear all character position by writing to all lines/cells on startup, but not after that. # The vorne display has significant lag in the time it takes to render the screen.... the serial write is practically immediate; the internal rendering of all the character positions takes perhaps a half-a-second or more.  \\]]> 18580123 18645632 characters. Then control goes into a forever loop, reading those dm items, formatting them for output via serial port, and then sleeping for .9 seconds. Some points to note.... # depth items is produced from pressure and ships lat, using standard algorithms by another navproc task (depthCalcTask()).  # Rov Lat/Lon is likewise produced by  the navproc rovPositionTask() from winfrog serial data. The specific datamanger item names consumed are defined in dvecsIntfc.h.{color:#ff0000}*\**{color}{color:#ff0000}\***NOTE THIS NEEDS TO BE RESOLVED FOR MIGRATION TO Rachel Carson... Vorne did not exist on Pt.Lobos/Ventana and the items names are different \! \*\*{color}{color:#ff0000}*\**{color} # The vorneTask() uses the old VT102 ascii terminal command syntax to position the cursor.  \[1,1H is the string command to move the cursor to row1,column1. Then (0x0B) is used to move relative for text appearing on line, 2,3 and 4. # If any garbage exists/gets written to character cells not normally written to during operation (ie in positions beyond end of line, it will remain there. The vorneTask makes an attempt to clear all character position by writing to all lines/cells on startup, but not after that. # The vorne display has significant lag in the time it takes to render the screen.... the serial write is practically immediate; the internal rendering of all the character positions takes perhaps a half-a-second or more.  \\]]> 18580125 18645603 18580096 18645607 \[1,1H is the string to move the cursor to row1,column1. Then VT is used to move relative for text on line, 2,3 and 4.  Note that if any garbage exists/gets written to character cells not normally written to during operation (ie in positions beyond end of line, it will remain there. The vorneTask makes an attempt to clear all character position by writing to all lines/cells on startup.   \\ \\]]> 18580100 18645610 \[1,1H is the string command to move the cursor to row1,column1. Then (0x0B) is used to move relative for text appearing on line, 2,3 and 4.  Note that if any garbage exists/gets written to character cells not normally written to during operation (ie in positions beyond end of line, it will remain there. The vorneTask makes an attempt to clear all character position by writing to all lines/cells on startup.   \\ \\]]> 18580103 18645612 \[1,1H is the string command to move the cursor to row1,column1. Then (0x0B) is used to move relative for text appearing on line, 2,3 and 4.  Note that if any garbage exists/gets written to character cells not normally written to during operation (ie in positions beyond end of line, it will remain there. The vorneTask makes an attempt to clear all character position by writing to all lines/cells on startup.   \\ \\]]> 18580105 18645614 \[1,1H is the string command to move the cursor to row1,column1. Then (0x0B) is used to move relative for text appearing on line, 2,3 and 4.  Note that if any garbage exists/gets written to character cells not normally written to during operation (ie in positions beyond end of line, it will remain there. The vorneTask makes an attempt to clear all character position by writing to all lines/cells on startup.   \\ \\]]> 18580107 18645615 \[1,1H is the string command to move the cursor to row1,column1. Then (0x0B) is used to move relative for text appearing on line, 2,3 and 4.  Note that if any garbage exists/gets written to character cells not normally written to during operation (ie in positions beyond end of line, it will remain there. The vorneTask makes an attempt to clear all character position by writing to all lines/cells on startup.   \\ \\]]> 18580108 18645617 \[1,1H is the string command to move the cursor to row1,column1. Then (0x0B) is used to move relative for text appearing on line, 2,3 and 4.  Note that if any garbage exists/gets written to character cells not normally written to during operation (ie in positions beyond end of line, it will remain there. The vorneTask makes an attempt to clear all character position by writing to all lines/cells on startup.   \\ \\]]> 18580110 11829463 " ## \# Set the RTC, only if a battery has been installed on the Beagleboard# # set the battery backed RTC, "hwclock \-w" ## \# Build the McStar Natively# # Enter "shutdown now". # Power off Beagleboard # Remove Ethernet Dongle from the Beagleboard {warning:title=Copy McStar app from host to harddrive}{warning} # Attach a freshly EXT3 formatted USB drive to the host # Enter "cp \-R \~/McStar/app /media/sda1/." # Unmount USB drive # Remove the USB host from the host and connect it to the Beagleboard # Power up the Beagleboard # Enter "root" at the Linux prompt # Enter "cd /media/sda1/app/src" # Enter "touch Makefile \*.h \*.cpp" # Enter "make clean" # Enter "make" ## \# Test the McStar App for 10 minutes, writing a new file every minute # Enter "mkdir /media/sda1/data" # Enter "cd /media/sda1/app/scripts" # Enter "./test_mcstar.sh" \\ \\ ---- h3. Notes on Beagel Board and SD Card Copy h1. Copy Linux filesystem on bootable SD card This tutorial is part of our Tutorials section. It shows how to flash an image onto an SD/SDHC card. This guide assumes that the card is correctly partitioned, as described in the Create a bootable SD/SDHC card in Ubuntu tutorial. h4. Steps in this tutorial # Mount the SD/SDHC card (if not already mounted) # Write bootloader if necessary # Write Linux kernel image # Write Linux root file system # Unmount h1. Quick Solution: Copy an already existing card If you have already one working SD image and an (absolutely similar) formatted second card, you can just copy them. WARNING Please be aware that the filesystem names (/dev/sdb1, etc.) can differ from system to system, make sure to select the right one. Copy one SD card to another: sudo dd if=/dev/sdb of=/dev/sdcThe safer alternative: Copy the SD card to harddisk and then onto another sudo dd if=/dev/sdb of=~/sd-card-copy.binNow back on the second SD card: sudo dd if=~/sd-card-copy.bin of=/dev/sdb h1. Mount SD/SDHC card Check where linux mounted the card. One way is to check this via mount . Call mount to see where the card has been mounted. Two partitions should have been mounted, one named '/media/BOOT' and the other one '/media/LINUX'. Note the device name, e.g. '/dev/sdb'. mountIf the card has not been mounted, you have two choices: h3. Automatic _Just unplug and re-plug the cardreader. It will be detected and mounted automatically._ h3. Manually If the check with mount didn't work out, use dmesg: dmesg \| tailWatch out for a line like this: [sdc] Attached SCSI removable diskWhere *sdc* could also be sdc or sdd. If it was sdb, the device name of the memory card is */dev/sdc*. sudo mkdir \-p /media/BOOT sudo mount /dev/sdc1 /media/BOOT sudo mkdir \-p /media/LINUX sudo mount /dev/sdc2 /media/LINUX h1. Copy files on the BOOT partition (MLO, u-boot.bin and uImage) _Please note that the bootloader files don't have to be rewritten every time. This applies especially when a new custom Linux system is created with_ BitBake and OpenEmbedded_. However if you work close to the hardware, e.g. on drivers, this is different.\_ h4. Overo Download MLO and uBoot from this link (commands for shell below): * PIXHAWK OpenEmbedded Images Download (OpenCV and libdc1394 ready) *IMPORTANT: Copy MLO FIRST\!*. The commands below download the two files and copy them in the right order on the boot partition. _You may have to adjust the filenames for future revisions._ cd $HOME wget [http://pixhawk.ethz.ch/wiki/_media/symlink/images/overo/mlo-overo] wget [http://pixhawk.ethz.ch/wiki/_media/symlink/images/overo/u-boot.bin-overoAnd] now copy the two files onto the boot partition (*MLO first* because of a bug in the X-loader which causes problems if MLO is not the first file written onto the boot partition). cp MLO-overo\* /media/BOOT/MLO cp u-boot.bin-overo\* /media/BOOT/u-boot.bin The Linux kernel (*uImage*) resides also on the *BOOT* partition of the SD-card. If you compile a new version of the kernel you have to copy the new *uImage* on the BOOT partition. See the instructions below. h4. BeagleBoard Download MLO and uBoot from this link (commands for shell below): * [http://www.angstrom-distribution.org/demo/beagleboard/] * Only for PIXHAWK Team (_will be made public in october_) *IMPORTANT: Copy MLO FIRST\!*. The commands below download the two files and copy them in the right order on the boot partition. _You may have to adjust the filenames for future revisions._ cd $HOME wget [http://www.angstrom-distribution.org/demo/beagleboard/MLO] wget [http://www.angstrom-distribution.org/demo/beagleboard/u-boot.binAnd] now copy the two files onto the boot partition (*MLO first* because of a bug in the X-loader which causes problems if MLO is not the first file written onto the boot partition). cp MLO /media/BOOT/MLO cp u-boot.bin /media/BOOT/u-boot.bin The Linux kernel (*uImage*) resides also on the *BOOT* partition of the SD-card. If you compile a new version of the kernel you have to copy the new *uImage* on the BOOT partition. See the instructions below. h1. Copy Linux _The next step is to copy the Linux kernel and the Linux root filesystem on the BOOT and LINUX partitions. You can use_ *{_}precompiled binaries{_}* _for both or_ *{_}compile an OpenEmbedded image yourself{_}{*}_. Instructions for both options are provided below._ h2. Copy the precompiled Ã…ngström Image The precompiled Ã…ngström image consists (besided MLO and u-boot.bin from the bootloader section) of two files: The Linux kernel image (uImage) and the root file system. h3. Copy uImage Download and copy the kernel image into the root directory of the boot partition. h4. Gumstix Overo cd $HOME wget [http://pixhawk.ethz.ch/wiki/_media/symlink/images/overo/uimage.bin-overo] cp uimage.bin-overo\* /media/BOOT/uImage h4. BeagleBoard cd $HOME wget [http://www.angstrom-distribution.org/demo/beagleboard/uImage] cp uImage /media/BOOT/uImage h3. Copy the Linux root file system The file is named *rootfs.tar.bz2 for the Beagle link and omap3-desktop-image-overo\-*.tar.bz2 for the Overo link below. Check the main folder for the current name. * Gumstix Overo: PIXHAWK OpenEmbedded Images Download (OpenCV and libdc1394 ready) * BeagleBoard: [http://www.angstrom-distribution.org/demo/beagleboard/] Download the files to a temporary directory, e.g. the Desktop or your user folder. The next step is to extract these files into the LINUX partition (NOT the boot partition). This can only be done by using Linux. If you're using Windows or MacOS, read this. h4. Gumstix Overo If you have downloaded the console image: wget [http://pixhawk.ethz.ch/wiki/_media/symlink/images/overo/pixhawk-console-image-overo.tar.bz2] sudo tar xjf pixhawk-console-image-overo-*.tar.bz2 \-C /media/LINUXOr the desktop image: wget [http://pixhawk.ethz.ch/wiki/_media/symlink/images/overo/pixhawk-desktop-image-overo.tar.bz2] sudo tar xjf pixhawk-desktop-image-overo\-*.tar.bz2* *{-}C /media/LINUXpossibly, "pixhawk-desktop-image-overo{-}*.tar.bz2" has to be changed into "pixhawk-console-image-overo.tar.bz2" (just adept file name) h4. BeagleBoard sudo tar xjf \*rootfs.tar.bz2 \-C /media/LINUX h2. Copy custom OpenEmbedded Linux Image h3. Linux Kernel Image and u-boot bootloader Copy the kernel image and u-boot. h4. Gumstix Overo sudo cp $OE_HOME/tmp/deploy/glibc/images/overo/uImage-overo.bin /media/BOOT/uImage cp $OE_HOME/tmp/deploy/glibc/images/overo/u-boot-overo.bin /media/BOOT/u-boot.bin h4. BeagleBoard sudo cp $OE_HOME/tmp/deploy/glibc/images/beagleboard/uImage-beagleboard.bin /media/BOOT/uImage cp $OE_HOME/tmp/deploy/glibc/images/beagleboard/u-boot-beagleboard.bin /media/BOOT/u-boot.bin h3. Linux root filesystem After the kernel, the root filesystem has to be copied as well. If you are overwriting an existing installation and you don't need a 100% clean system, you can just delete all files. The command below will delete all files in /media/LINUX except the lost+found directory of the EXT3 file system. sudo rm \-rf /media/LINUX/\* && sudo mkdir /media/LINUX/lost+foundHowever if you want a really clean disk, you should format it, but this will take considerably longer. sudo mkfs.ext3 \-L LINUX /dev/sdc2And now copy the new files. h4. Gumstix Overo The console image: sudo tar xjf $OE_HOME/tmp/deploy/glibc/images/overo/omap3-console-image-overo.tar.bz2 \-C /media/LINUXThe pixhawk console image: sudo tar xjf $OE_HOME/tmp/deploy/glibc/images/overo/pixhawk-console-image-overo.tar.bz2 \-C /media/LINUXOr the desktop image: sudo tar xjf $OE_HOME/tmp/deploy/glibc/images/overo/omap3-desktop-image-overo.tar.bz2 \-C /media/LINUX h4. BeagleBoard The console image: sudo tar xjf $OE_HOME/tmp/deploy/glibc/images/beagleboard/omap3-console-image-beagleboard.tar.bz2 \-C /media/LINUXOr the desktop image: sudo tar xjf $OE_HOME/tmp/deploy/glibc/images/beagleboard/omap3-desktop-image-overo.beagleboard.bz2 \-C /media/LINUX h1. Unmount the SD/SDHC card Now unmount the drive either manually (by clicking the unmount icon on the desktop) or by shell command: sync sudo umount /media/BOOT sudo umount /media/LINUX sudo rm \-r /media/BOOT sudo rm \-r /media/LINUX h1. Copy bytewise from one SDHC card to another If you have modified your installation and want to clone the content of the SD card, you can do this with dd. Make sure to plug in the source card first, then the destination card. Check the file names with: dmesg \| tailAnd unmount the card (with the GUI or with umount /dev/sdb). Then use dd to copy the first gigabyte from one card to the other (including partition table, etc.): sudo dd if=/dev/sdb of=/dev/sdc bs=1073741824]]> 11796706 11829465 11796708 11829459 " ## \# Set the RTC, only if a battery has been installed on the Beagleboard# # set the battery backed RTC, "hwclock \-w" ## \# Build the McStar Natively# # Enter "shutdown now". # Power off Beagleboard # Remove Ethernet Dongle from the Beagleboard {warning:title=Copy McStar app from host to harddrive}{warning} # Attach a freshly EXT3 formatted USB drive to the host # Enter "cp \-R \~/McStar/app /media/sda1/." # Unmount USB drive # Remove the USB host from the host and connect it to the Beagleboard # Power up the Beagleboard # Enter "root" at the Linux prompt # Enter "cd /media/sda1/app/src" # Enter "touch Makefile \*.h \*.cpp" # Enter "make clean" # Enter "make" ## \# Test the McStar App for 10 minutes, writing a new file every minute # Enter "mkdir /media/sda1/data" # Enter "cd /media/sda1/app/scripts" # Enter "./test_mcstar.sh" \\ \\ ---- h3. Notes on Beagel Board and SD Card Copy h1. Copy Linux filesystem on bootable SD card This tutorial is part of our Tutorials section. It shows how to flash an image onto an SD/SDHC card. This guide assumes that the card is correctly partitioned, as described in the Create a bootable SD/SDHC card in Ubuntu tutorial. h4. Steps in this tutorial # Mount the SD/SDHC card (if not already mounted) # Write bootloader if necessary # Write Linux kernel image # Write Linux root file system # Unmount h1. Quick Solution: Copy an already existing card If you have already one working SD image and an (absolutely similar) formatted second card, you can just copy them. WARNING Please be aware that the filesystem names (/dev/sdb1, etc.) can differ from system to system, make sure to select the right one. Copy one SD card to another: sudo dd if=/dev/sdb of=/dev/sdcThe safer alternative: Copy the SD card to harddisk and then onto another sudo dd if=/dev/sdb of=~/sd-card-copy.binNow back on the second SD card: sudo dd if=~/sd-card-copy.bin of=/dev/sdb h1. Mount SD/SDHC card Check where linux mounted the card. One way is to check this via mount . Call mount to see where the card has been mounted. Two partitions should have been mounted, one named '/media/BOOT' and the other one '/media/LINUX'. Note the device name, e.g. '/dev/sdb'. mountIf the card has not been mounted, you have two choices: h3. Automatic _Just unplug and re-plug the cardreader. It will be detected and mounted automatically._ h3. Manually If the check with mount didn't work out, use dmesg: dmesg \| tailWatch out for a line like this: [sdc] Attached SCSI removable diskWhere *sdc* could also be sdc or sdd. If it was sdb, the device name of the memory card is */dev/sdc*. sudo mkdir \-p /media/BOOT sudo mount /dev/sdc1 /media/BOOT sudo mkdir \-p /media/LINUX sudo mount /dev/sdc2 /media/LINUX h1. Copy files on the BOOT partition (MLO, u-boot.bin and uImage) _Please note that the bootloader files don't have to be rewritten every time. This applies especially when a new custom Linux system is created with_ BitBake and OpenEmbedded_. However if you work close to the hardware, e.g. on drivers, this is different.\_ h4. Overo Download MLO and uBoot from this link (commands for shell below): * PIXHAWK OpenEmbedded Images Download (OpenCV and libdc1394 ready) *IMPORTANT: Copy MLO FIRST\!*. The commands below download the two files and copy them in the right order on the boot partition. _You may have to adjust the filenames for future revisions._ cd $HOME wget [http://pixhawk.ethz.ch/wiki/_media/symlink/images/overo/mlo-overo] wget [http://pixhawk.ethz.ch/wiki/_media/symlink/images/overo/u-boot.bin-overoAnd] now copy the two files onto the boot partition (*MLO first* because of a bug in the X-loader which causes problems if MLO is not the first file written onto the boot partition). cp MLO-overo\* /media/BOOT/MLO cp u-boot.bin-overo\* /media/BOOT/u-boot.bin The Linux kernel (*uImage*) resides also on the *BOOT* partition of the SD-card. If you compile a new version of the kernel you have to copy the new *uImage* on the BOOT partition. See the instructions below. h4. BeagleBoard Download MLO and uBoot from this link (commands for shell below): * [http://www.angstrom-distribution.org/demo/beagleboard/] * Only for PIXHAWK Team (_will be made public in october_) *IMPORTANT: Copy MLO FIRST\!*. The commands below download the two files and copy them in the right order on the boot partition. _You may have to adjust the filenames for future revisions._ cd $HOME wget [http://www.angstrom-distribution.org/demo/beagleboard/MLO] wget [http://www.angstrom-distribution.org/demo/beagleboard/u-boot.binAnd] now copy the two files onto the boot partition (*MLO first* because of a bug in the X-loader which causes problems if MLO is not the first file written onto the boot partition). cp MLO /media/BOOT/MLO cp u-boot.bin /media/BOOT/u-boot.bin The Linux kernel (*uImage*) resides also on the *BOOT* partition of the SD-card. If you compile a new version of the kernel you have to copy the new *uImage* on the BOOT partition. See the instructions below. h1. Copy Linux _The next step is to copy the Linux kernel and the Linux root filesystem on the BOOT and LINUX partitions. You can use_ *{_}precompiled binaries{_}* _for both or_ *{_}compile an OpenEmbedded image yourself{_}{*}_. Instructions for both options are provided below._ h2. Copy the precompiled Ã…ngström Image The precompiled Ã…ngström image consists (besided MLO and u-boot.bin from the bootloader section) of two files: The Linux kernel image (uImage) and the root file system. h3. Copy uImage Download and copy the kernel image into the root directory of the boot partition. h4. Gumstix Overo cd $HOME wget [http://pixhawk.ethz.ch/wiki/_media/symlink/images/overo/uimage.bin-overo] cp uimage.bin-overo\* /media/BOOT/uImage h4. BeagleBoard cd $HOME wget [http://www.angstrom-distribution.org/demo/beagleboard/uImage] cp uImage /media/BOOT/uImage h3. Copy the Linux root file system The file is named *rootfs.tar.bz2 for the Beagle link and omap3-desktop-image-overo\-*.tar.bz2 for the Overo link below. Check the main folder for the current name. * Gumstix Overo: PIXHAWK OpenEmbedded Images Download (OpenCV and libdc1394 ready) * BeagleBoard: [http://www.angstrom-distribution.org/demo/beagleboard/] Download the files to a temporary directory, e.g. the Desktop or your user folder. The next step is to extract these files into the LINUX partition (NOT the boot partition). This can only be done by using Linux. If you're using Windows or MacOS, read this. h4. Gumstix Overo If you have downloaded the console image: wget [http://pixhawk.ethz.ch/wiki/_media/symlink/images/overo/pixhawk-console-image-overo.tar.bz2] sudo tar xjf pixhawk-console-image-overo-*.tar.bz2 \-C /media/LINUXOr the desktop image: wget [http://pixhawk.ethz.ch/wiki/_media/symlink/images/overo/pixhawk-desktop-image-overo.tar.bz2] sudo tar xjf pixhawk-desktop-image-overo\-*.tar.bz2* *{-}C /media/LINUXpossibly, "pixhawk-desktop-image-overo{-}*.tar.bz2" has to be changed into "pixhawk-console-image-overo.tar.bz2" (just adept file name) h4. BeagleBoard sudo tar xjf \*rootfs.tar.bz2 \-C /media/LINUX h2. Copy custom OpenEmbedded Linux Image h3. Linux Kernel Image and u-boot bootloader Copy the kernel image and u-boot. h4. Gumstix Overo sudo cp $OE_HOME/tmp/deploy/glibc/images/overo/uImage-overo.bin /media/BOOT/uImage cp $OE_HOME/tmp/deploy/glibc/images/overo/u-boot-overo.bin /media/BOOT/u-boot.bin h4. BeagleBoard sudo cp $OE_HOME/tmp/deploy/glibc/images/beagleboard/uImage-beagleboard.bin /media/BOOT/uImage cp $OE_HOME/tmp/deploy/glibc/images/beagleboard/u-boot-beagleboard.bin /media/BOOT/u-boot.bin h3. Linux root filesystem After the kernel, the root filesystem has to be copied as well. If you are overwriting an existing installation and you don't need a 100% clean system, you can just delete all files. The command below will delete all files in /media/LINUX except the lost+found directory of the EXT3 file system. sudo rm \-rf /media/LINUX/\* && sudo mkdir /media/LINUX/lost+foundHowever if you want a really clean disk, you should format it, but this will take considerably longer. sudo mkfs.ext3 \-L LINUX /dev/sdc2And now copy the new files. h4. Gumstix Overo The console image: sudo tar xjf $OE_HOME/tmp/deploy/glibc/images/overo/omap3-console-image-overo.tar.bz2 \-C /media/LINUXThe pixhawk console image: sudo tar xjf $OE_HOME/tmp/deploy/glibc/images/overo/pixhawk-console-image-overo.tar.bz2 \-C /media/LINUXOr the desktop image: sudo tar xjf $OE_HOME/tmp/deploy/glibc/images/overo/omap3-desktop-image-overo.tar.bz2 \-C /media/LINUX h4. BeagleBoard The console image: sudo tar xjf $OE_HOME/tmp/deploy/glibc/images/beagleboard/omap3-console-image-beagleboard.tar.bz2 \-C /media/LINUXOr the desktop image: sudo tar xjf $OE_HOME/tmp/deploy/glibc/images/beagleboard/omap3-desktop-image-overo.beagleboard.bz2 \-C /media/LINUX h1. Unmount the SD/SDHC card Now unmount the drive either manually (by clicking the unmount icon on the desktop) or by shell command: sync sudo umount /media/BOOT sudo umount /media/LINUX sudo rm \-r /media/BOOT sudo rm \-r /media/LINUX h1. Copy bytewise from one SDHC card to another If you have modified your installation and want to clone the content of the SD card, you can do this with dd. Make sure to plug in the source card first, then the destination card. Check the file names with: dmesg \| tailAnd unmount the card (with the GUI or with umount /dev/sdb). Then use dd to copy the first gigabyte from one card to the other (including partition table, etc.): sudo dd if=/dev/sdb of=/dev/sdc bs=1073741824]]> 11796701 11829462 " ## \# Set the RTC, only if a battery has been installed on the Beagleboard# # set the battery backed RTC, "hwclock \-w" ## \# Build the McStar Natively# # Enter "shutdown now". # Power off Beagleboard # Remove Ethernet Dongle from the Beagleboard {warning:title=Copy McStar app from host to harddrive}{warning} # Attach a freshly EXT3 formatted USB drive to the host # Enter "cp \-R \~/McStar/app /media/sda1/." # Unmount USB drive # Remove the USB host from the host and connect it to the Beagleboard # Power up the Beagleboard # Enter "root" at the Linux prompt # Enter "cd /media/sda1/app/src" # Enter "touch Makefile \*.h \*.cpp" # Enter "make clean" # Enter "make" ## \# Test the McStar App for 10 minutes, writing a new file every minute # Enter "mkdir /media/sda1/data" # Enter "cd /media/sda1/app/scripts" # Enter "./test_mcstar.sh" \\ \\ ---- h3. Notes on Beagel Board and SD Card Copy h1. Copy Linux filesystem on bootable SD card This tutorial is part of our Tutorials section. It shows how to flash an image onto an SD/SDHC card. This guide assumes that the card is correctly partitioned, as described in the Create a bootable SD/SDHC card in Ubuntu tutorial. h4. Steps in this tutorial # Mount the SD/SDHC card (if not already mounted) # Write bootloader if necessary # Write Linux kernel image # Write Linux root file system # Unmount h1. Quick Solution: Copy an already existing card If you have already one working SD image and an (absolutely similar) formatted second card, you can just copy them. WARNING Please be aware that the filesystem names (/dev/sdb1, etc.) can differ from system to system, make sure to select the right one. Copy one SD card to another: sudo dd if=/dev/sdb of=/dev/sdcThe safer alternative: Copy the SD card to harddisk and then onto another sudo dd if=/dev/sdb of=~/sd-card-copy.binNow back on the second SD card: sudo dd if=~/sd-card-copy.bin of=/dev/sdb h1. Mount SD/SDHC card Check where linux mounted the card. One way is to check this via mount . Call mount to see where the card has been mounted. Two partitions should have been mounted, one named '/media/BOOT' and the other one '/media/LINUX'. Note the device name, e.g. '/dev/sdb'. mountIf the card has not been mounted, you have two choices: h3. Automatic _Just unplug and re-plug the cardreader. It will be detected and mounted automatically._ h3. Manually If the check with mount didn't work out, use dmesg: dmesg \| tailWatch out for a line like this: [sdc] Attached SCSI removable diskWhere *sdc* could also be sdc or sdd. If it was sdb, the device name of the memory card is */dev/sdc*. sudo mkdir \-p /media/BOOT sudo mount /dev/sdc1 /media/BOOT sudo mkdir \-p /media/LINUX sudo mount /dev/sdc2 /media/LINUX h1. Copy files on the BOOT partition (MLO, u-boot.bin and uImage) _Please note that the bootloader files don't have to be rewritten every time. This applies especially when a new custom Linux system is created with_ BitBake and OpenEmbedded_. However if you work close to the hardware, e.g. on drivers, this is different.\_ h4. Overo Download MLO and uBoot from this link (commands for shell below): * PIXHAWK OpenEmbedded Images Download (OpenCV and libdc1394 ready) *IMPORTANT: Copy MLO FIRST\!*. The commands below download the two files and copy them in the right order on the boot partition. _You may have to adjust the filenames for future revisions._ cd $HOME wget [http://pixhawk.ethz.ch/wiki/_media/symlink/images/overo/mlo-overo] wget [http://pixhawk.ethz.ch/wiki/_media/symlink/images/overo/u-boot.bin-overoAnd] now copy the two files onto the boot partition (*MLO first* because of a bug in the X-loader which causes problems if MLO is not the first file written onto the boot partition). cp MLO-overo\* /media/BOOT/MLO cp u-boot.bin-overo\* /media/BOOT/u-boot.bin The Linux kernel (*uImage*) resides also on the *BOOT* partition of the SD-card. If you compile a new version of the kernel you have to copy the new *uImage* on the BOOT partition. See the instructions below. h4. BeagleBoard Download MLO and uBoot from this link (commands for shell below): * [http://www.angstrom-distribution.org/demo/beagleboard/] * Only for PIXHAWK Team (_will be made public in october_) *IMPORTANT: Copy MLO FIRST\!*. The commands below download the two files and copy them in the right order on the boot partition. _You may have to adjust the filenames for future revisions._ cd $HOME wget [http://www.angstrom-distribution.org/demo/beagleboard/MLO] wget [http://www.angstrom-distribution.org/demo/beagleboard/u-boot.binAnd] now copy the two files onto the boot partition (*MLO first* because of a bug in the X-loader which causes problems if MLO is not the first file written onto the boot partition). cp MLO /media/BOOT/MLO cp u-boot.bin /media/BOOT/u-boot.bin The Linux kernel (*uImage*) resides also on the *BOOT* partition of the SD-card. If you compile a new version of the kernel you have to copy the new *uImage* on the BOOT partition. See the instructions below. h1. Copy Linux _The next step is to copy the Linux kernel and the Linux root filesystem on the BOOT and LINUX partitions. You can use_ *{_}precompiled binaries{_}* _for both or_ *{_}compile an OpenEmbedded image yourself{_}{*}_. Instructions for both options are provided below._ h2. Copy the precompiled Ã…ngström Image The precompiled Ã…ngström image consists (besided MLO and u-boot.bin from the bootloader section) of two files: The Linux kernel image (uImage) and the root file system. h3. Copy uImage Download and copy the kernel image into the root directory of the boot partition. h4. Gumstix Overo cd $HOME wget [http://pixhawk.ethz.ch/wiki/_media/symlink/images/overo/uimage.bin-overo] cp uimage.bin-overo\* /media/BOOT/uImage h4. BeagleBoard cd $HOME wget [http://www.angstrom-distribution.org/demo/beagleboard/uImage] cp uImage /media/BOOT/uImage h3. Copy the Linux root file system The file is named *rootfs.tar.bz2 for the Beagle link and omap3-desktop-image-overo\-*.tar.bz2 for the Overo link below. Check the main folder for the current name. * Gumstix Overo: PIXHAWK OpenEmbedded Images Download (OpenCV and libdc1394 ready) * BeagleBoard: [http://www.angstrom-distribution.org/demo/beagleboard/] Download the files to a temporary directory, e.g. the Desktop or your user folder. The next step is to extract these files into the LINUX partition (NOT the boot partition). This can only be done by using Linux. If you're using Windows or MacOS, read this. h4. Gumstix Overo If you have downloaded the console image: wget [http://pixhawk.ethz.ch/wiki/_media/symlink/images/overo/pixhawk-console-image-overo.tar.bz2] sudo tar xjf pixhawk-console-image-overo-*.tar.bz2 \-C /media/LINUXOr the desktop image: wget [http://pixhawk.ethz.ch/wiki/_media/symlink/images/overo/pixhawk-desktop-image-overo.tar.bz2] sudo tar xjf pixhawk-desktop-image-overo\-*.tar.bz2* *{-}C /media/LINUXpossibly, "pixhawk-desktop-image-overo{-}*.tar.bz2" has to be changed into "pixhawk-console-image-overo.tar.bz2" (just adept file name) h4. BeagleBoard sudo tar xjf \*rootfs.tar.bz2 \-C /media/LINUX h2. Copy custom OpenEmbedded Linux Image h3. Linux Kernel Image and u-boot bootloader Copy the kernel image and u-boot. h4. Gumstix Overo sudo cp $OE_HOME/tmp/deploy/glibc/images/overo/uImage-overo.bin /media/BOOT/uImage cp $OE_HOME/tmp/deploy/glibc/images/overo/u-boot-overo.bin /media/BOOT/u-boot.bin h4. BeagleBoard sudo cp $OE_HOME/tmp/deploy/glibc/images/beagleboard/uImage-beagleboard.bin /media/BOOT/uImage cp $OE_HOME/tmp/deploy/glibc/images/beagleboard/u-boot-beagleboard.bin /media/BOOT/u-boot.bin h3. Linux root filesystem After the kernel, the root filesystem has to be copied as well. If you are overwriting an existing installation and you don't need a 100% clean system, you can just delete all files. The command below will delete all files in /media/LINUX except the lost+found directory of the EXT3 file system. sudo rm \-rf /media/LINUX/\* && sudo mkdir /media/LINUX/lost+foundHowever if you want a really clean disk, you should format it, but this will take considerably longer. sudo mkfs.ext3 \-L LINUX /dev/sdc2And now copy the new files. h4. Gumstix Overo The console image: sudo tar xjf $OE_HOME/tmp/deploy/glibc/images/overo/omap3-console-image-overo.tar.bz2 \-C /media/LINUXThe pixhawk console image: sudo tar xjf $OE_HOME/tmp/deploy/glibc/images/overo/pixhawk-console-image-overo.tar.bz2 \-C /media/LINUXOr the desktop image: sudo tar xjf $OE_HOME/tmp/deploy/glibc/images/overo/omap3-desktop-image-overo.tar.bz2 \-C /media/LINUX h4. BeagleBoard The console image: sudo tar xjf $OE_HOME/tmp/deploy/glibc/images/beagleboard/omap3-console-image-beagleboard.tar.bz2 \-C /media/LINUXOr the desktop image: sudo tar xjf $OE_HOME/tmp/deploy/glibc/images/beagleboard/omap3-desktop-image-overo.beagleboard.bz2 \-C /media/LINUX h1. Unmount the SD/SDHC card Now unmount the drive either manually (by clicking the unmount icon on the desktop) or by shell command: sync sudo umount /media/BOOT sudo umount /media/LINUX sudo rm \-r /media/BOOT sudo rm \-r /media/LINUX h1. Copy bytewise from one SDHC card to another If you have modified your installation and want to clone the content of the SD card, you can do this with dd. Make sure to plug in the source card first, then the destination card. Check the file names with: dmesg \| tailAnd unmount the card (with the GUI or with umount /dev/sdb). Then use dd to copy the first gigabyte from one card to the other (including partition table, etc.): sudo dd if=/dev/sdb of=/dev/sdc bs=1073741824]]> 11796705 18645601 18580094 11829457 " ## \# Set the RTC, only if a battery has been installed on the Beagleboard# # set the battery backed RTC, "hwclock \-w" ## \# Build the McStar Natively# # Enter "shutdown now". # Power off Beagleboard # Remove Ethernet Dongle from the Beagleboard {warning:title=Copy McStar app from host to harddrive}{warning} # Attach a freshly EXT3 formatted USB drive to the host # Enter "cp \-R \~/McStar/app /media/sda1/." # Unmount USB drive # Remove the USB host from the host and connect it to the Beagleboard # Power up the Beagleboard # Enter "root" at the Linux prompt # Enter "cd /media/sda1/app/src" # Enter "touch Makefile \*.h \*.cpp" # Enter "make clean" # Enter "make" ## \# Test the McStar App for 10 minutes, writing a new file every minute # Enter "mkdir /media/sda1/data" # Enter "cd /media/sda1/app/scripts" # Enter "./test_mcstar.sh" \\ \\ ---- h3. Notes on Beagel Board and SD Card Copy h1. Copy Linux filesystem on bootable SD card This tutorial is part of our Tutorials section. It shows how to flash an image onto an SD/SDHC card. This guide assumes that the card is correctly partitioned, as described in the Create a bootable SD/SDHC card in Ubuntu tutorial. h4. Steps in this tutorial # Mount the SD/SDHC card (if not already mounted) # Write bootloader if necessary # Write Linux kernel image # Write Linux root file system # Unmount h1. Quick Solution: Copy an already existing card If you have already one working SD image and an (absolutely similar) formatted second card, you can just copy them. WARNING Please be aware that the filesystem names (/dev/sdb1, etc.) can differ from system to system, make sure to select the right one. Copy one SD card to another: sudo dd if=/dev/sdb of=/dev/sdcThe safer alternative: Copy the SD card to harddisk and then onto another sudo dd if=/dev/sdb of=~/sd-card-copy.binNow back on the second SD card: sudo dd if=~/sd-card-copy.bin of=/dev/sdb h1. Mount SD/SDHC card Check where linux mounted the card. One way is to check this via mount . Call mount to see where the card has been mounted. Two partitions should have been mounted, one named '/media/BOOT' and the other one '/media/LINUX'. Note the device name, e.g. '/dev/sdb'. mountIf the card has not been mounted, you have two choices: h3. Automatic _Just unplug and re-plug the cardreader. It will be detected and mounted automatically._ h3. Manually If the check with mount didn't work out, use dmesg: dmesg \| tailWatch out for a line like this: [sdc] Attached SCSI removable diskWhere *sdc* could also be sdc or sdd. If it was sdb, the device name of the memory card is */dev/sdc*. sudo mkdir \-p /media/BOOT sudo mount /dev/sdc1 /media/BOOT sudo mkdir \-p /media/LINUX sudo mount /dev/sdc2 /media/LINUX h1. Copy files on the BOOT partition (MLO, u-boot.bin and uImage) _Please note that the bootloader files don't have to be rewritten every time. This applies especially when a new custom Linux system is created with_ BitBake and OpenEmbedded_. However if you work close to the hardware, e.g. on drivers, this is different.\_ h4. Overo Download MLO and uBoot from this link (commands for shell below): * PIXHAWK OpenEmbedded Images Download (OpenCV and libdc1394 ready) *IMPORTANT: Copy MLO FIRST\!*. The commands below download the two files and copy them in the right order on the boot partition. _You may have to adjust the filenames for future revisions._ cd $HOME wget [http://pixhawk.ethz.ch/wiki/_media/symlink/images/overo/mlo-overo] wget [http://pixhawk.ethz.ch/wiki/_media/symlink/images/overo/u-boot.bin-overoAnd] now copy the two files onto the boot partition (*MLO first* because of a bug in the X-loader which causes problems if MLO is not the first file written onto the boot partition). cp MLO-overo\* /media/BOOT/MLO cp u-boot.bin-overo\* /media/BOOT/u-boot.bin The Linux kernel (*uImage*) resides also on the *BOOT* partition of the SD-card. If you compile a new version of the kernel you have to copy the new *uImage* on the BOOT partition. See the instructions below. h4. BeagleBoard Download MLO and uBoot from this link (commands for shell below): * [http://www.angstrom-distribution.org/demo/beagleboard/] * Only for PIXHAWK Team (_will be made public in october_) *IMPORTANT: Copy MLO FIRST\!*. The commands below download the two files and copy them in the right order on the boot partition. _You may have to adjust the filenames for future revisions._ cd $HOME wget [http://www.angstrom-distribution.org/demo/beagleboard/MLO] wget [http://www.angstrom-distribution.org/demo/beagleboard/u-boot.binAnd] now copy the two files onto the boot partition (*MLO first* because of a bug in the X-loader which causes problems if MLO is not the first file written onto the boot partition). cp MLO /media/BOOT/MLO cp u-boot.bin /media/BOOT/u-boot.bin The Linux kernel (*uImage*) resides also on the *BOOT* partition of the SD-card. If you compile a new version of the kernel you have to copy the new *uImage* on the BOOT partition. See the instructions below. h1. Copy Linux _The next step is to copy the Linux kernel and the Linux root filesystem on the BOOT and LINUX partitions. You can use_ *{_}precompiled binaries{_}* _for both or_ *{_}compile an OpenEmbedded image yourself{_}{*}_. Instructions for both options are provided below._ h2. Copy the precompiled Ã…ngström Image The precompiled Ã…ngström image consists (besided MLO and u-boot.bin from the bootloader section) of two files: The Linux kernel image (uImage) and the root file system. h3. Copy uImage Download and copy the kernel image into the root directory of the boot partition. h4. Gumstix Overo cd $HOME wget [http://pixhawk.ethz.ch/wiki/_media/symlink/images/overo/uimage.bin-overo] cp uimage.bin-overo\* /media/BOOT/uImage h4. BeagleBoard cd $HOME wget [http://www.angstrom-distribution.org/demo/beagleboard/uImage] cp uImage /media/BOOT/uImage h3. Copy the Linux root file system The file is named *rootfs.tar.bz2 for the Beagle link and omap3-desktop-image-overo\-*.tar.bz2 for the Overo link below. Check the main folder for the current name. * Gumstix Overo: PIXHAWK OpenEmbedded Images Download (OpenCV and libdc1394 ready) * BeagleBoard: [http://www.angstrom-distribution.org/demo/beagleboard/] Download the files to a temporary directory, e.g. the Desktop or your user folder. The next step is to extract these files into the LINUX partition (NOT the boot partition). This can only be done by using Linux. If you're using Windows or MacOS, read this. h4. Gumstix Overo If you have downloaded the console image: wget [http://pixhawk.ethz.ch/wiki/_media/symlink/images/overo/pixhawk-console-image-overo.tar.bz2] sudo tar xjf pixhawk-console-image-overo-*.tar.bz2 \-C /media/LINUXOr the desktop image: wget [http://pixhawk.ethz.ch/wiki/_media/symlink/images/overo/pixhawk-desktop-image-overo.tar.bz2] sudo tar xjf pixhawk-desktop-image-overo\-*.tar.bz2* *{-}C /media/LINUXpossibly, "pixhawk-desktop-image-overo{-}*.tar.bz2" has to be changed into "pixhawk-console-image-overo.tar.bz2" (just adept file name) h4. BeagleBoard sudo tar xjf \*rootfs.tar.bz2 \-C /media/LINUX h2. Copy custom OpenEmbedded Linux Image h3. Linux Kernel Image and u-boot bootloader Copy the kernel image and u-boot. h4. Gumstix Overo sudo cp $OE_HOME/tmp/deploy/glibc/images/overo/uImage-overo.bin /media/BOOT/uImage cp $OE_HOME/tmp/deploy/glibc/images/overo/u-boot-overo.bin /media/BOOT/u-boot.bin h4. BeagleBoard sudo cp $OE_HOME/tmp/deploy/glibc/images/beagleboard/uImage-beagleboard.bin /media/BOOT/uImage cp $OE_HOME/tmp/deploy/glibc/images/beagleboard/u-boot-beagleboard.bin /media/BOOT/u-boot.bin h3. Linux root filesystem After the kernel, the root filesystem has to be copied as well. If you are overwriting an existing installation and you don't need a 100% clean system, you can just delete all files. The command below will delete all files in /media/LINUX except the lost+found directory of the EXT3 file system. sudo rm \-rf /media/LINUX/\* && sudo mkdir /media/LINUX/lost+foundHowever if you want a really clean disk, you should format it, but this will take considerably longer. sudo mkfs.ext3 \-L LINUX /dev/sdc2And now copy the new files. h4. Gumstix Overo The console image: sudo tar xjf $OE_HOME/tmp/deploy/glibc/images/overo/omap3-console-image-overo.tar.bz2 \-C /media/LINUXThe pixhawk console image: sudo tar xjf $OE_HOME/tmp/deploy/glibc/images/overo/pixhawk-console-image-overo.tar.bz2 \-C /media/LINUXOr the desktop image: sudo tar xjf $OE_HOME/tmp/deploy/glibc/images/overo/omap3-desktop-image-overo.tar.bz2 \-C /media/LINUX h4. BeagleBoard The console image: sudo tar xjf $OE_HOME/tmp/deploy/glibc/images/beagleboard/omap3-console-image-beagleboard.tar.bz2 \-C /media/LINUXOr the desktop image: sudo tar xjf $OE_HOME/tmp/deploy/glibc/images/beagleboard/omap3-desktop-image-overo.beagleboard.bz2 \-C /media/LINUX h1. Unmount the SD/SDHC card Now unmount the drive either manually (by clicking the unmount icon on the desktop) or by shell command: sync sudo umount /media/BOOT sudo umount /media/LINUX sudo rm \-r /media/BOOT sudo rm \-r /media/LINUX h1. Copy bytewise from one SDHC card to another If you have modified your installation and want to clone the content of the SD card, you can do this with dd. Make sure to plug in the source card first, then the destination card. Check the file names with: dmesg \| tailAnd unmount the card (with the GUI or with umount /dev/sdb). Then use dd to copy the first gigabyte from one card to the other (including partition table, etc.): sudo dd if=/dev/sdb of=/dev/sdc bs=1073741824]]> 11796699 9405170 9372439 9405176 9372445 9405174 9372443 15663690 15630936 15663688 15630934 15663693 15630939 15663692 15630938 15663697 D0 52.08 52.08 \+0 \+0.00 D0->D1 104.17 104.17 \+0 \+0.00 D1->D2 156.25 156.25 \+0 \+0.00 D2->D3 208.33 208.33 \+0 \+0.00 D3->D4 260.42 260.42 \+0 \+0.00 D4->D5 312.50 312.50 \+0 \+0.00 D5->D6 364.58 364.58 \+0 \+0.00 D6->D7 416.67 416.67 \+0 \+0.00 D7->stopbit 468.75 468.75 \+0 \+0.00 end of stopb 520.83 520.83 \+0 \+0.00 \*/ UBR00=0xC0; UBR10=0x00; UMCTL0=0x00; /\* uart0 3686400Hz 19200bps \*/ UBR01=0xC0; UBR11=0x00; UMCTL1=0x00; /\* uart1 3686400Hz 19200bps \*/ h4. The simplest way to use the USART in UART mode is this: interrupt is not enabled, the software checks if it can output the next byte (UTXIFG = 1), and if a new character has been received (URXIFG = 1). \\ h4. Modbus Register Map * REG_INPUT_START         512         // input registers start at 512 * REG_INPUT_NREGS         8           // 8x16 bit registers * REG_SOLENOIDS_A        0            // Holding registers start at 0 (16 coils for each A and B) * REG_SOLENOIDS_B        1   * REG_HOLDING_START    0           // to match WAGO * REG_HOLDING_NREGS   40         // 40 is more than actual (2) * REG_COILS_START         0           // read individual coils (was 1000) * REG_COILS_SIZE           32          // 32 coils * REG_DISC_START          0           // discrete (was 1000) * REG_DISC_SIZE             32          // 32 coils \\ h3. ---- MODBUS * Commands ** Read Input Register (0x04) ** Read Holding Registers (0x03) ** Write Single Register (0x06) ** Write Multiple Registers (0x10) ** Read/Write Multiple Registers (0x17) ** Read Coils (0x01) ** Write Single Coil (0x05) ** Write Multiple Coils (0x0F) ** Read Discrete Inputs (0x02) ** Report Slave ID (0x11)   * Address * Slave ID  * Berlios ModBus Stack ** The modbus stack is config'd in {color:#0000ff}mbconfig.h{color} which is located in vpc\modbus\include \\ \\ ---- h3. Debugging MSP430 h4. Starting gdbproxy The next step is starting gdbproxy, which is responsible for the communication between GDB and the FET: msp430-gdbproxy \--port=2000 msp430 If your FET is properly connected to the parallel port, you should see a message like the following: info: msp430: Target device is a 'MSP430F12x' (type 11) notice: msp430-gdbproxy: waiting on TCP port 2000 h4. Using Insight (Windows) After you have started Insight (c:\msp430\bin\msp430-gdb.exe), click on "File->Open" and select the elf-file (e.g. "test.elf") you want to debug. Now click on "Run->Connect to target" and enter the following settings: Target: "Remote/TCP" Hostname: "localhost" Port: "2000" Set breakpoint at 'main': yes Set breakpoint at 'exit': yes Attach to target: yes Download Program: yes Command after attaching: "monitor erase all" Run Method: Continue from last Stop When you click on "Ok" Insight should tell you that the connection was successful, and gdbproxy should say "notice: msp430-gdbproxy: connected". To start the debugging click on "Run" or simply press "r". If everything worked correctly you should now see the sourcecode of your program with the first line of main() marked green. The red point is the breakpoint that has been set by Insight automatically. You can set or remove breakpoints by clicking on the '-' in front of the line. Now you can 'c'ontinue the execution to the next breakpoint, 's'tep through the code, or step a single assembler instruction... but be careful with "finish": Insight sometimes seems to lock up with this command. So if you want to finish a function, I recommend setting a breakpoint to the end of the function and using "continue". \\ h2. Installing the Compiler Tool Chain To obtain and install the compiler: # Go to the MSPGCC download page and obtain the latest MSPGCC installation. I used the 'mspgcc-20040723.exe' download which installed everything I needed for a Win32 setup. \\ # This step need only be performed if you wish to use the graphical version of GDB. The latest MSPGCC download only includes the command line GDB debugger. I prefer to use the graphical version called Insight. A slightly older prebuilt version of Insight can be used. Install this older version of insight into a different directory to that chosen for the latest MSPGCC installation as you don't want to overwrite the files obtained in step 1. \\ You should now have two installations. The latest version of MSPGCC installed during step 1, and a slightly older version of Insight from step 2. Both versions of the GDB debugger are called msp430-gdb.exe so one needs to be renamed. Locate the older version msp430-gdb.exe from the files installed during this step and rename it msp430-insight.exe. \\ # Ensure the BIN directory from the files installed during step 1 and the BIN directory from the files installed during step 2 are included in your PATH environment variable. \\ \\ # The MSPGCC download includes a program called msp430-gdbproxy.exe. This intercepts the GDB TCP commands and redirects them to the parallel port. Start msp430-gdbproxy (a shortcut to this will have been placed on the start menu when MSPGCC was installed). By default msp430-gdbproxy uses port 3333 - do not change this. \\ # Program the flash as per the instruction in the section above. The flash can be programmed from within GDB but it is much faster to do it separately and beforehand. \\ # Start the debugger using the command ... msp430-insight a.out... the commands in the gdb.ini file will do the rest. If you prefer to use the command line debugger simply replace msp430-insight with msp430-gdb. \\ # Insight will start at and the program will stop at the breakpoint in main() as shown below. \\ MSP430 Clocking \\ MSP430 Basic Clock Module * Clock Signals: ** *ACLK*: Auxiliary clock. The signal is sourced from LFXT1CLK with a divider of 1, 2, 4, or 8. (The calibration program for the serial link sets the divider to 4, but after the calibration it can be changed to any other values.) ACLK can be used as the clock signal for Timer A and Timer B. ** *MCLK*: Master clock. The signal can be sourced from LFXT1CLK, XT2CLK (if available), or DCOCLK with a divider of 1, 2, 4, or 8. MCLK is used by the CPU and system. ** *SMCLK*: Sub-main clock. The signal is sourced from either XT2CLK (if available), or DCOCLK with a divider of 1, 2, 4, or 8. SMCLK can be used as the clock signal for Timer A and Timer B. * MSP430 Clocking pictorial: *   * \\ !MSP430_clocking2.JPG!                  !MSP430_BCSCTL1.JPG! !MSP430_BCSCTL2.JPG!\\ \\]]> 15630943 15663696 15630942 15663672 15630917 7208994 "Downloads">"2.1 Releases">"2.1.1" # I then clicked on alfresco-enterprise-tomcat-2.1.1.zip to download the zip file. # Went to [http://customers.alfresco.com] (I was still logged in) # Went to "Company Home">"Downloads">"2.1 Releases">"2.1.1">"License Files" # I went ahead and downloaded all the "*.lic" files, but I think I only need enterprise-network-customer-unlimited.lic" # Logged out of Alfresco. # Since I suspect I will need a JDBC driver for SQLServer, I downloaded the jTDS-1.2.2 driver from the jtds web site (just Google jtds and go to the download section of the top google return). # I closed the Firefox browser. # I extracted the jtds-1.2.2.jar file from the jtds download # I downloaded and installed the JRockit 6 R27.4 JDK Microsoft Windows (x86 - 32 bit) from BEA's web site {note} After installing JRockit, make sure you set the JAVA_HOME environment variable to point to the installation of JRockit. For example, I went to the desktop, right clicked on the computer, did Properties, then clicked on the Advanced tab, then click on the environment variables button and then created a new system variable named JAVA_HOME and set to c:\bin\Java\jrockit-R27.4.0-jdk1.6.0_02 {note} # I ran the installer, changed the "Program Files" to "bin" in the installation directory for both the JDK and the JRE. I also chose to install the JRE as public. # Using Firefox, I downloaded the PHP 5.2.5 Windows Installer from php.net and installed it. Although I installed it, I did not integrate it with a web server as I want Alfresco to take port 80. I probably did not need to install PHP, but I thought I would anyway. (again, I changed install path from "Program Files" to "bin" # I also downloaded and installed OpenOffice and ran it once so I could get through the initial startup # I setup a Alfresco database on the server Solstice and granted the LAGOON\DB_Collaboration account to be the db_owner of the Alfresco database. # I unzipped the alfresco tomcat zip file to an alfresco directory in c:\bin # I then went to the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions directory for the customization of the server. ## I edited the custom-repository.properties file ### Changed the dir.root and dir.indexes to look like: {noformat} dir.root=//tornado.shore.mbari.org/Alfresco/alf_data dir.indexes=d:/alf_data/lucene-indexes {noformat} ### Commented out the db.* lines for the HSQL Connection (db.driver and db.url) ### Uncommented the db.* lines for MSSQL and changed to use the jTDS driver. They should look like: {noformat} db.driver=net.sourceforge.jtds.jdbc.Driver db.url=jdbc:jtds:sqlserver://solstice.shore.mbari.org/Alfresco;domain=SHORE;user=DB_Collaboration;password=XXXXXXXXX {noformat} ### I also added the following section to override the mail server settings {noformat} # Mail server configuration mail.host=mail.mbari.org mail.port=25 mail.username= mail.password= {noformat} ## Edited the custom-hibernate-dialect.properties file ### Commented out the HSQL Dialect ### Uncommented the MSSQL Dialect # I then installed the jtds-1.2.2.jar in the c:\bin\alfresco\tomcat\common\lib so that it will be on the classpath when Alfresco is started # Now this is not necessarily fun, but in order to really get it configured the way we want it, you need to pull the original .war file out, edit some stuff inside and re-create the .war. {note} This should all be done before starting Alfresco for the first time. {note} # Copy the c:\Alfresco\tomcat\webapps\alfresco.war file to your home directory. # Make a second copy so that you will always the original (I copied to alfresco.war.orig and moved it somewhere else. It is important to move it and have only the alfresco.war file in the directory because when you un-jar it, all the files go right where alfresco.war is.) # From a command line, un-jar the war file using: {noformat} jar -xvf alfresco.war {noformat} # This unpacks a lot of files and after it completes, move (or delete) the alfresco.war file from the directory. This needs to be done so it does not end up in the new .war file. # I wanted to change the "Company Home" that seems to be everywhere to something that says MBARI. ## Edited ./WEB-INF/classes/alfresco/messages/webclient.properties and changed company_home from 'Company Home' to 'MBARI' ## Edited ./WEB-INF/classes/alfresco/messages/webclient_en_US.properties and changed company_home from 'Company Home' to 'MBARI' ## I edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces.properties and changed the first two lines to read {noformat} spaces.company_home.name=MBARI spaces.company_home.description=The root space for MBARI {noformat} ## Edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces_en_US.properties and made the same changes as the previous step {tip} This took a bit to find all these, and to be honest, I am not sure which one actually made the change on the GUI, but I suspect it was the _en_US ones. {tip} # When users are imported via LDAP, user spaces get created automatically. In order to put them where I wanted them to go (instead of right in the Company Home), I edited the ./WEB-INF/classes/alfresco/authentication-services-context.xml file. In the file there is a bean with an name of personalHomeFolderProvider. There is a property name 'path' and I added {noformat} /${spaces.user_homes.childname} {noformat} to the end to try to get them to create the user spaces there instead of in the Company Home. The final bean XML looks like: {noformat} /${spaces.company_home.childname}/${spaces.user_homes.childname} ${spaces.store} false All All {noformat} # I wanted to change the logo that is used. I attached the replacement logo [here|^AlfrescoLogo32.png]. Copy this to ./images/logo and overwrite the one that is there. # In order to setup SSL for the application (will do that later), edit ./WEB-INF/web.xml and add the following {noformat} Login Pages /* CONFIDENTIAL {noformat} right before the ending tag at the bottom of the file. # Now in order to change the default behavior so that all content is versioned from the start, I edited the .\WEB-INF\classes\alfresco\model\contentModel.xml and searched for the content type definition block. {noformat} Content cm:cmobject true d:content false true false true {noformat} and added the following block right before the ending tag: {noformat} cm:versionable {noformat} so the final block looks like: {noformat} Content cm:cmobject true d:content false true false true cm:versionable {noformat} # That takes care of all the changes to the WAR file. We can now put it back into .war form. # While you are in the directory you expanded the war file in, run ## jar cvfm alfresco.war META-INF\MANIFEST.MF . # You should now have an alfresco.war file in the directory. Move that back to the alfresco install and overwrite the existing one. # Most users like the details view, so I set the default to that by editing c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions\web-client-config-custom.xml and added: {noformat} details 20
20
20 {noformat} right before the closing tag. # Now in order to use MBARI accounts, NTLM authentication was turned on and then chained with the native Alfresco accounts so that we could have non-MBARI accounts on the Alfresco server. ## In order to enable NTLM and native Alfresco authentication, I had to edit two files. For simplicity I have just attached them here and they can be downloaded and installed in the extensions directory. ### The first file is the [ntlm-authentication-context.xml|^ntlm-authentication-context.xml] file. This configures and enables NTLM authentication. ### The next file was the [chaining-authentication-context.xml|^chaining-authentication-context.xml] file which enabled Alfresco authentication and chained it together with the NTLM authentication from the previous file. # Then in order to setup CIFS on the server, I edited the file-servers-custom.xml file to look like the attached [file-servers-custom.xml|^file-servers-custom.xml] file. # In order to grant certain accounts admin privs, I created a new custom-authority-services-context.xml in the same directory as the ldap-authentication-context.xml file and added {noformat} kgomes admin administrator {noformat} # In order for Alfresco to handle all port 80 traffic, I changed Tomcat so that it takes port 80 and SSL goes over port 443. So I edited the c:\Alfresco\tomcat\conf\server.xml file and changed the 8080 port to 80 and the 8443 port to 443 (the 443 change is done in two places). # Now I needed to setup the SSL for the web traffic. Cathy Sewell was instrumental in getting this working. She ordered a new certificate specifically for alfresco and put it in the c:\local\cert folder. Here are the instructions for what she did to get the certficate installed. {noformat} SSL certificate for server Alfresco - 1/2/08 C:\bin\Java\jrockit-R27.1.0-jre1.6.0_02\bin>keytool -genkey -alias tomcat -keyalg RSA -keystore tomcat.keystore What is your first and last name? [alfresco.mbari.org]: What is the name of your organizational unit? [IS]: What is the name of your organization? [MBARI]: What is the name of your City or Locality? [Moss Landing]: What is the name of your State or Province? [CD]: CA What is the two-letter country code for this unit? [US]: Is CN=alfresco.mbari.org, OU=IS, O=MBARI, L=Moss Landing, ST=CA, C=US correct? [no]: y Enter key password for (RETURN if same as keystore password): C:\bin\Java\jrockit-R27.4.0-jre1.6.0_02\bin>keytool -certreq -keyalg RSA -alias tomcat -file certreq.csr -keystore tomcat.keystore Enter keystore password: Generated certificate request file, certreq.csr, was submitted to SSL provider. Certificate provider sent certificate file (alfresco.mbari.org.crt), along with gd_bundle.crt, gd_cross_intermediate.crt, and gd_intermediate.crt. Additionally, I downloaded valicert_class2_root.cer from their website. These files were stored in c:\local\cert. The following commands were used to add them to the tomcat keystore: C:\bin\Java\jrockit-R27.4.0-jre1.6.0_02\bin>keytool -import -alias root -keystore tomcat.keystore -trustcacerts -file c:\local\cert\valicert_class2_root.cer Enter keystore password: Certificate already exists in system-wide CA keystore under alias Do you still want to add it to your own keystore? [no]: y Certificate was added to keystore C:\bin\Java\jrockit-R27.4.0-jre1.6.0_02\bin>keytool -import -alias cross -keystore tomcat.keystore -trustcacerts -file c:\local\cert\gd_cross_intermediate.crt Enter keystore password: Certificate was added to keystore C:\bin\Java\jrockit-R27.4.0-jre1.6.0_02\bin>keytool -import -alias intermed -keystore tomcat.keystore -trustcacerts -file c:\local\cert\gd_intermediate.crt Enter keystore password: Certificate was added to keystore C:\bin\Java\jrockit-R27.4.0-jre1.6.0_02\bin>keytool -import -alias tomcat -keystore tomcat.keystore -trustcacerts -file c:\local\cert\alfresco.mbari.org.crt Enter keystore password: Certificate reply was installed in keystore {noformat} # I edited the c:\bin\alfresco\tomcat\conf\server.xml file and uncommented the SSL section and edited to look like that shown below. {noformat} {noformat} # Since I was in the server.xml file, I went ahead and changed it so that the default webapp was alfresco so that you would get alfresco anytime you went to the base URL. I did this by adding: {noformat} {noformat} as the last line of the tag section (right before the closing tag). {note} You will also notice the Valve tag that I had to add to turn off proxy cache disabling so that IE clients would work correctly over SSL. Gotta love M$. {note} # I copied the enterprise-network-unlimited.lic file into the c:\Alfresco\tomcat\shared\classes\alfresco\extensions\license directory # Just to keep things clean, I edited the c:\bin\alfresco\alfresco.bat file and put 'rem' in front of the second JAVA_OPTS set as I am using Java 6. # Now after you run it for the first time and the database structure gets created, you can't restart it because you get: {noformat} java.sql.SQLException: Column names in each table must be unique. Column name 'ID_' in table 'JBPM_ACTION' is specified more than once. {noformat} Sigh, so in order to keep Alfresco from hurting itself, I had to turn off the schema updates. This is done by editing the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions\custom-repository.properties and adding the following: {noformat} db.schema.update=false {noformat} and then restarting alfresco. # To install Alfresco as a Windows Service use a command prompt and enter the following: {noformat} cd c:\bin\alfresco\tomcat\bin service.bat install alfresco tomcat5.exe //US//alfresco --DisplayName "Alfresco Server" tomcat5.exe //US//alfresco --JvmMs=512 --JvmMx=1024 --JvmSs=64 tomcat5.exe //US//alfresco --JavaHome=c:/bin/Java/jrockit-R27.4.0-jdk1.6.0_02 tomcat5.exe //US//alfresco --Environment ALF_HOME=c:/bin/alfresco/ tomcat5.exe //US//alfresco --Environment PATH=c:/bin/alfresco/bin;%PATH% tomcat5.exe //US//alfresco --StartPath c:/bin/alfresco --Startup auto {noformat} # To uninstall the service, at a later time, do the following: {noformat} cd c:\bin\alfresco\tomcat\bin service.bat uninstall alfresco {noformat} # To edit your service settings at any time: {noformat} cd c:\alfresco\tomcat\bin tomcat5w.exe //ES//alfresco {noformat} {warning} These next couple of steps had to be taken to install a patch from Alfresco for an issue with bulk uploads I was having. Essentially when file and path structures get really long and nasty, Alfresco was throwing an error and bailing out. This patch (two Java classes) fixed that issue. {warning} # Next, I downloaded the attached [JAR|^act2139.jar] file and copied it to the c:\bin\alfresco\tomcat\webapps\alfresco\WEB-INF\classes directory. # I shutdown Alfresco and then unjarred the file to install the new classes. They are: ## org/alfresco/filesys/smb/server/SMBSrvPacket.class ## org/alfresco/filesys/util/DataBuffer.class # I would assume since they do not overwrite anything, that this location is further up in the class loader and so it will load these new classes first. # I deleted the act2139.jar file and the META-INF directory that the unjarring process created. # In order to install certain modules (like the email listener), I had to get the Alfresco Module Manager from the customers.alfresco.com download site. I downloaded the alfresco-mmt-2.1.1.jar file locally so I could use it to install modules. # I then downloaded the email listener module from [http://forge.alfresco.com/projects/email-listener/]. It came as a zip file, so I unzipped it and it created a folder with the appropriate emailListener.amp in it. # Make another backup copy of the alfresco.war file and put somewhere in case you want to roll this back. # Open a command prompt windows and cd to the location where the Alfresco Module Manager jar is. # Run the following: {noformat} java -jar alfresco-mmt-2.1.1.jar path_to_emailListener.amp path_to_alfresco.war {noformat} So for me this looked like: {noformat} java -jar alfresco-mmt-2.1.1.jar .\email-listener_2.1RC2\emailListener.amp c:\bin\alfresco\tomcat\webapps\alfresco.war {noformat} # You should be able to verify the install by running: {noformat} java -jar alfresco-mmt-2.1.1.jar list c:\bin\alfresco\tomcat\webapps\alfresco.war {noformat} and you should see something like: {noformat} Module 'emailListener' installed in 'c:\bin\alfresco\tomcat\webapps\alfresco.war' - Title: EmailListener - Version: 2.1 - Install Date: Fri Dec 07 08:43:10 PST 2007 - Desription: EmailListener Module {noformat} # Finally, to start the service, just go into your Windows Service control panel and locate the service that is now named 'Alfresco Server'. You can start and stop Alfresco from this control panel. h1. Content Migration Now, in order to migrate content from old alfresco and normal file structures, I did the following: h3. For content already in alfresco: # Navigate to the space whose contents you want to migrate. For example, let's say I want to migrate the stuff from my personal space. I would navigate (using the WebUI) to the /MBARI/User Homes/kgomes space. You should see the contents of the kgomes folder from this view. # Click on 'More actions->View Details'. # On the right hand side, click on 'Export'. # For package name, I usually enter the space name followed by '_export', but it doesn't really matter. # Click on the link that says 'Click here to select the destination' and select somewhere that you will be able to download the .acp file from. # Select 'Current Space'. # Select 'Include Children'. # Uncheck 'Include this space' unless you have content (documents) in this specific folder (anything other than folders) that you want to migrate. This is a bit tricky, but there are two ways to do this. If you want to have the top level folder created, use the 'Include this space' and that will create the top level folder. Otherwise, if will expand into the folder in which you import the .acp file into. This is important in cases where the folder has already been created for you (like with user homes) and you have to migrate content into that folder. If you have the option to create the top level directory, by all means do so. # Uncheck 'Export in background' so you can force it to happen and you know when it is complete.]]> 7176232 15663674 15630919 15663670 15630915 7208986 7176224 7208981 BOOT PICO CF2> BOOT APP for deployment RMC message for A or V (Tracking or DR - tells wether GPS is tracking) \\ First Tasks 1) Add to Prompt GPS OK, RGPS Age OK, AGC OK, Platform Track OK (ask once every 4sec to avoid swamping the Seatel) 2) Create NMEA style string on Spare2 hooked to 24 port terminal server for continuous stream of updates to be displayed by a GUI \\ \\ \\ \\ Seatel SEA TEL MODEl TAC-92 USER INTERFACE DESCRIPTI0N VERSION 1.61 1.0 COMMAND SUMMARY | CONTROL CODES: | FUNCTION | | | 6 |Azimuth CW one step (system step reselution) | | 4 |Azimuth CCW one step | | 8 |Elevation up one step | | 2 |Elevation DOWN one step | | Aaaaa{} |Move AZ to aaa.a deg , true or magnetic | | Baaaa{} |Set ships heading to aaa.a degrees | | c |Step Track ON | | D |Step Track and Tracking OFF | | cnnnn{} |Set MHz/CHA tuning to nnnn MHz | | dnnnn{} |Set KHz/CHB tuning to nnnn KKz > | | Eeeee{} |Move EL to ee.e or eee.e degrees | | F |Toggle aUto unwrap ON/OFF | | gnnn {} |Set polang position to nnn | | Jrrrr{} |Move azimuth to ship relative position | | Nnnn{ } |Set number of signal strength updAtes (1-255) | | Onnn{ } |Output data to EME equipment | | R |start spiral search fot satellite | | s |Advance AGC input selectien (Ext, ChA, ChB, IF) | | Taaaa{} |Move to satellite at aaa.a degrees | | U |Force cable unwrap | | W |Write parameterS to NV RAM | | Xnnn{} |Set azimuth step track si2e to nnn steps (1-255) | | Ynnn{} |Set elevation step track size to nnn steps (0-255) | | Z |Toggle C/Ku step size selection | | esc |Cancel pending numeric command | | $mmmmm{} |NMEA Latitude / Longitude input (GPGLL format) | | MONITOR CODES | FUNCTION | TAC RESPONSE | | H | Relative Az,Ship Heading | RrrrrHaaaa,CR,LF,> | | M | Tracking Parameters | Xnnn Ynnn Nnnn cc,CR,LF,> | | P | Az/EL Position | EeeeeAaaaa,CR,LF,> | | s | TaC Status | Snn,CR,LF1> | | V | Software Version | TAC-92 VER N,NN,CR,LF, > | | q | Tuning >Frequencies , Input | Qnnnn nnnn s,CR,LF,> | | u | Polang position | Gnnn ,CR,LF,> | | % | Signal Strength | Lnnnn,CR,LF,> | | & | Error Status | &nnn ,CR,LF,> | | ABBREVIATIONS: | | eeee = | Elevation angle oooo to 0900 nominal 0000 to 3599 range | | aaaa = | True/Magnetic Azimuth 0000 to 3599 range | | rrrr = | Relative azimuth 0950 to 6250 1ange | | nnnn = | A5CII decimal number 0000-9999 | | nnn = | ASCII decima\[ number 0 to 255 | | nn = | System Status twO bitmaped ASCII characters | | cc = | C /Ku tracking parameter bank selection | | s = | AGC receiver selection 0,l,2,3 | | {} = | Carriage return | April 30, 1996 Doc No. 112862-D \\ \\]]> 7176216 7208979 BOOT PICO CF2> BOOT APP for deployment RMC message for A or V (Tracking or DR - tells wether GPS is tracking)\\ First Tasks 1) Add to Prompt GPS OK, RGPS Age OK, AGC OK, Platform Track OK (ask once every 4sec to avoid swamping the Seatel) 2) Create NMEA style string on Spare2 hooked to 24 port terminal server for continuous stream of updates to be displayed by a GUI\\]]> 7176214 7208974 BOOT PICO CF2> BOOT APP for deployment]]> 7176209 7208972 7176207 7208964 7176199 17891452 17858699 9405067 9372334 9405069 9372336 9405074 . BEGIN LICENSE Monteray Bay Aquarium Research Institute Site License 01 0005 RS2D-XDNU-GUA4-CZCZ 411aedde 61b2d8be 2a3ea037 54a6535c d80ec02a b3c15935 1509f1d0 08ce95b0 1894c13a 1e29cf6a 24734d92 719e8b90 cd840c5a 87d40e02 5ec866c3 5040e210 30cf0e05 3f14a534 835694bb aee4bdb2 4b63c5d8 61226c94 1eb4a1a2 757fb2b1 END LICENSE]]> 9372341 9405063 9372330 9405065 9372332 15663624 15630870 15663622 15630868 9405075 . BEGIN LICENSE Monteray Bay Aquarium Research Institute Site License 01 0005 RS2D-XDNU-GUA4-CZCZ 411aedde 61b2d8be 2a3ea037 54a6535c d80ec02a b3c15935 1509f1d0 08ce95b0 1894c13a 1e29cf6a 24734d92 719e8b90 cd840c5a 87d40e02 5ec866c3 5040e210 30cf0e05 3f14a534 835694bb aee4bdb2 4b63c5d8 61226c94 1eb4a1a2 757fb2b1 END LICENSE]]> 9372342 9405076 . BEGIN LICENSE Monteray Bay Aquarium Research Institute Site License 01 0005 RS2D-XDNU-GUA4-CZCZ 411aedde 61b2d8be 2a3ea037 54a6535c d80ec02a b3c15935 1509f1d0 08ce95b0 1894c13a 1e29cf6a 24734d92 719e8b90 cd840c5a 87d40e02 5ec866c3 5040e210 30cf0e05 3f14a534 835694bb aee4bdb2 4b63c5d8 61226c94 1eb4a1a2 757fb2b1 END LICENSE]]> 9372343 17891429 17858672 9405078 . BEGIN LICENSE Monteray Bay Aquarium Research Institute Site License 01 0005 RS2D-XDNU-GUA4-CZCZ 411aedde 61b2d8be 2a3ea037 54a6535c d80ec02a b3c15935 1509f1d0 08ce95b0 1894c13a 1e29cf6a 24734d92 719e8b90 cd840c5a 87d40e02 5ec866c3 5040e210 30cf0e05 3f14a534 835694bb aee4bdb2 4b63c5d8 61226c94 1eb4a1a2 757fb2b1 END LICENSE]]> 9372345 17891482 17858733 17891480 17858731 17891489 17858740 17891487 17858738 17891485 17858736 17891483 17858734 17891470 17858718 3179038 "Downloads">"2.1 Releases">"2.1.1" # I then clicked on alfresco-enterprise-tomcat-2.1.1.zip to download the zip file. # Went to [http://customers.alfresco.com] (I was still logged in) # Went to "Company Home">"Downloads">"2.1 Releases">"2.1.1">"License Files" # I went ahead and downloaded all the "*.lic" files, but I think I only need enterprise-network-customer-unlimited.lic" # Logged out of Alfresco. # Since I suspect I will need a JDBC driver for SQLServer, I downloaded the jTDS-1.2.2 driver from the jtds web site (just Google jtds and go to the download section of the top google return). # I closed the Firefox browser. # I extracted the jtds-1.2.2.jar file from the jtds download # I downloaded and installed the JRockit 6 R27.4 JDK Microsoft Windows (x86 - 32 bit) from BEA's web site {note} After installing JRockit, make sure you set the JAVA_HOME environment variable to point to the installation of JRockit. For example, I went to the desktop, right clicked on the computer, did Properties, then clicked on the Advanced tab, then click on the environment variables button and then created a new system variable named JAVA_HOME and set to c:\bin\Java\jrockit-R27.4.0-jdk1.6.0_02 {note} # I ran the installer, changed the "Program Files" to "bin" in the installation directory for both the JDK and the JRE. I also chose to install the JRE as public. # Using Firefox, I downloaded the PHP 5.2.5 Windows Installer from php.net and installed it. Although I installed it, I did not integrate it with a web server as I want Alfresco to take port 80. I probably did not need to install PHP, but I thought I would anyway. (again, I changed install path from "Program Files" to "bin" # I also downloaded and installed OpenOffice and ran it once so I could get through the initial startup # I setup a Alfresco database on the server Solstice and granted the LAGOON\DB_Collaboration account to be the db_owner of the Alfresco database. # I unzipped the alfresco tomcat zip file to an alfresco directory in c:\bin # I then went to the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions directory for the customization of the server. ## I edited the custom-repository.properties file ### Changed the dir.root and dir.indexes to look like: {noformat} dir.root=//tornado.shore.mbari.org/Alfresco/alf_data dir.indexes=d:/alf_data/lucene-indexes {noformat} ### Commented out the db.* lines for the HSQL Connection (db.driver and db.url) ### Uncommented the db.* lines for MSSQL and changed to use the jTDS driver. They should look like: {noformat} db.driver=net.sourceforge.jtds.jdbc.Driver db.url=jdbc:jtds:sqlserver://solstice.shore.mbari.org/Alfresco;domain=SHORE;user=DB_Collaboration;password=XXXXXXXXX {noformat} ### I also added the following section to override the mail server settings {noformat} # Mail server configuration mail.host=mail.mbari.org mail.port=25 mail.username= mail.password= {noformat} ## Edited the custom-hibernate-dialect.properties file ### Commented out the HSQL Dialect ### Uncommented the MSSQL Dialect # I then installed the jtds-1.2.2.jar in the c:\bin\alfresco\tomcat\common\lib so that it will be on the classpath when Alfresco is started # Now this is not necessarily fun, but in order to really get it configured the way we want it, you need to pull the original .war file out, edit some stuff inside and re-create the .war. {note} This should all be done before starting Alfresco for the first time. {note} # Copy the c:\Alfresco\tomcat\webapps\alfresco.war file to your home directory. # Make a second copy so that you will always the original (I copied to alfresco.war.orig and moved it somewhere else. It is important to move it and have only the alfresco.war file in the directory because when you un-jar it, all the files go right where alfresco.war is.) # From a command line, un-jar the war file using: {noformat} jar -xvf alfresco.war {noformat} # This unpacks a lot of files and after it completes, move (or delete) the alfresco.war file from the directory. This needs to be done so it does not end up in the new .war file. # I wanted to change the "Company Home" that seems to be everywhere to something that says MBARI. ## Edited ./WEB-INF/classes/alfresco/messages/webclient.properties and changed company_home from 'Company Home' to 'MBARI' ## Edited ./WEB-INF/classes/alfresco/messages/webclient_en_US.properties and changed company_home from 'Company Home' to 'MBARI' ## I edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces.properties and changed the first two lines to read {noformat} spaces.company_home.name=MBARI spaces.company_home.description=The root space for MBARI {noformat} ## Edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces_en_US.properties and made the same changes as the previous step {tip} This took a bit to find all these, and to be honest, I am not sure which one actually made the change on the GUI, but I suspect it was the _en_US ones. {tip} # When users are imported via LDAP, user spaces get created automatically. In order to put them where I wanted them to go (instead of right in the Company Home), I edited the ./WEB-INF/classes/alfresco/authentication-services-context.xml file. In the file there is a bean with an name of personalHomeFolderProvider. There is a property name 'path' and I added {noformat} /${spaces.user_homes.childname} {noformat} to the end to try to get them to create the user spaces there instead of in the Company Home. The final bean XML looks like: {noformat} /${spaces.company_home.childname}/${spaces.user_homes.childname} ${spaces.store} false All All {noformat} # I wanted to change the logo that is used. I attached the replacement logo [here|^AlfrescoLogo32.png]. Copy this to ./images/logo and overwrite the one that is there. # In order to setup SSL for the application (will do that later), edit ./WEB-INF/web.xml and add the following {noformat} Login Pages /* CONFIDENTIAL {noformat} right before the ending tag at the bottom of the file. # Now in order to change the default behavior so that all content is versioned from the start, I edited the .\WEB-INF\classes\alfresco\model\contentModel.xml and searched for the content type definition block. {noformat} Content cm:cmobject true d:content false true false true {noformat} and added the following block right before the ending tag: {noformat} cm:versionable {noformat} so the final block looks like: {noformat} Content cm:cmobject true d:content false true false true cm:versionable {noformat} # That takes care of all the changes to the WAR file. We can now put it back into .war form. # While you are in the directory you expanded the war file in, run ## jar cvfm alfresco.war META-INF\MANIFEST.MF . # You should now have an alfresco.war file in the directory. Move that back to the alfresco install and overwrite the existing one. # Most users like the details view, so I set the default to that by editing c:\Alfresco\tomcat\shared\classes\alfresco\extensions/web-client-config-custom.xml and added: {noformat} details 20
20
20 {noformat} right before the closing tag. # Now in order to use MBARI accounts, NTLM authentication was turned on and then chained with the native Alfresco accounts so that we could have non-MBARI accounts on the Alfresco server. ## In order to enable NTLM and native Alfresco authentication, I had to edit two files. For simplicity I have just attached them here and they can be downloaded and installed in the extensions directory. ### The first file is the [ntlm-authentication-context.xml|^ntlm-authentication-context.xml] file. This configures and enables NTLM authentication. ### The next file was the [chaining-authentication-context.xml|^chaining-authentication-context.xml] file which enabled Alfresco authentication and chained it together with the NTLM authentication from the previous file. # Then in order to setup CIFS on the server, I edited the file-servers-custom.xml file to look like the attached [file-servers-custom.xml|^file-servers-custom.xml] file. # In order to grant certain accounts admin privs, I created a new custom-authority-services-context.xml in the same directory as the ldap-authentication-context.xml file and added {noformat} kgomes admin administrator {noformat} # In order for Alfresco to handle all port 80 traffic, I changed Tomcat so that it takes port 80 and SSL goes over port 443. So I edited the c:\Alfresco\tomcat\conf\server.xml file and changed the 8080 port to 80 and the 8443 port to 443 (the 443 change is done in two places). # Now I needed to setup the SSL for the web traffic. Cathy Sewell was instrumental in getting this working. She ordered a new certificate specifically for alfresco and put it in the c:\local\cert folder. Here are the instructions for what she did to get the certficate installed. {noformat} SSL certificate for server Alfresco - 1/2/08 C:\bin\Java\jrockit-R27.1.0-jre1.6.0_02\bin>keytool -genkey -alias tomcat -keyalg RSA -keystore tomcat.keystore What is your first and last name? [alfresco.mbari.org]: What is the name of your organizational unit? [IS]: What is the name of your organization? [MBARI]: What is the name of your City or Locality? [Moss Landing]: What is the name of your State or Province? [CD]: CA What is the two-letter country code for this unit? [US]: Is CN=alfresco.mbari.org, OU=IS, O=MBARI, L=Moss Landing, ST=CA, C=US correct? [no]: y Enter key password for (RETURN if same as keystore password): C:\bin\Java\jrockit-R27.4.0-jre1.6.0_02\bin>keytool -certreq -keyalg RSA -alias tomcat -file certreq.csr -keystore tomcat.keystore Enter keystore password: Generated certificate request file, certreq.csr, was submitted to SSL provider. Certificate provider sent certificate file (alfresco.mbari.org.crt), along with gd_bundle.crt, gd_cross_intermediate.crt, and gd_intermediate.crt. Additionally, I downloaded valicert_class2_root.cer from their website. These files were stored in c:\local\cert. The following commands were used to add them to the tomcat keystore: C:\bin\Java\jrockit-R27.4.0-jre1.6.0_02\bin>keytool -import -alias root -keystore tomcat.keystore -trustcacerts -file c:\local\cert\valicert_class2_root.cer Enter keystore password: Certificate already exists in system-wide CA keystore under alias Do you still want to add it to your own keystore? [no]: y Certificate was added to keystore C:\bin\Java\jrockit-R27.4.0-jre1.6.0_02\bin>keytool -import -alias cross -keystore tomcat.keystore -trustcacerts -file c:\local\cert\gd_cross_intermediate.crt Enter keystore password: Certificate was added to keystore C:\bin\Java\jrockit-R27.4.0-jre1.6.0_02\bin>keytool -import -alias intermed -keystore tomcat.keystore -trustcacerts -file c:\local\cert\gd_intermediate.crt Enter keystore password: Certificate was added to keystore C:\bin\Java\jrockit-R27.4.0-jre1.6.0_02\bin>keytool -import -alias tomcat -keystore tomcat.keystore -trustcacerts -file c:\local\cert\alfresco.mbari.org.crt Enter keystore password: Certificate reply was installed in keystore Adjustment of the server.xml file was left to Kevin. {noformat} #I edited the c:\bin\alfresco\tomcat\conf\server.xml file and uncommented the SSL section and edited to look like that shown below. {noformat} {noformat} # Since I was in the server.xml file, I went ahead and changed it so that the default webapp was alfresco so that you would get alfresco anytime you went to the base URL. I did this by adding: {noformat} {noformat} as the last line of the tag section (right before the closing tag). {note} You will also notice the Valve tag that I had to add to turn off proxy cache disabling so that IE clients would work correctly over SSL. Gotta love M$. {note} # I copied the enterprise-network-unlimited.lic file into the c:\Alfresco\tomcat\shared\classes\alfresco\extensions\license directory # Just to keep things clean, I edited the c:\bin\alfresco\alfresco.bat file and put 'rem' in front of the second JAVA_OPTS set as I am using Java 6. # Now after you run it for the first time and the database structure gets created, you can't restart it because you get: {noformat} java.sql.SQLException: Column names in each table must be unique. Column name 'ID_' in table 'JBPM_ACTION' is specified more than once. {noformat} Sigh, so in order to keep Alfresco from hurting itself, I had to turn off the schema updates. This is done by editing the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions\custom-repository.properties and adding the following: {noformat} db.schema.update=false {noformat} and then restarting alfresco. # To install Alfresco as a Windows Service use a command prompt and enter the following: {noformat} cd c:\bin\alfresco\tomcat\bin service.bat install alfresco tomcat5.exe //US//alfresco --DisplayName "Alfresco Server" tomcat5.exe //US//alfresco --JvmMs=512 --JvmMx=1024 --JvmSs=64 tomcat5.exe //US//alfresco --JavaHome=c:/bin/Java/jrockit-R27.4.0-jdk1.6.0_02 tomcat5.exe //US//alfresco --Environment ALF_HOME=c:/bin/alfresco/ tomcat5.exe //US//alfresco --Environment PATH=c:/bin/alfresco/bin;%PATH% tomcat5.exe //US//alfresco --StartPath c:/bin/alfresco --Startup auto {noformat} # To uninstall the service, at a later time, do the following: {noformat} cd c:\bin\alfresco\tomcat\bin service.bat uninstall alfresco {noformat} # To edit your service settings at any time: {noformat} cd c:\alfresco\tomcat\bin tomcat5w.exe //ES//alfresco {noformat} # In order to install certain modules (like the email listener), I had to get the Alfresco Module Manager from the customers.alfresco.com download site. I downloaded the alfresco-mmt-2.1.1.jar file locally so I could use it to install modules. # I then downloaded the email listener module from [http://forge.alfresco.com/projects/email-listener/]. It came as a zip file, so I unzipped it and it created a folder with the appropriate emailListener.amp in it. # Make another backup copy of the alfresco.war file and put somewhere in case you want to roll this back. # Open a command prompt windows and cd to the location where the Alfresco Module Manager jar is. # Run the following: {noformat} java -jar alfresco-mmt-2.1.1.jar path_to_emailListener.amp path_to_alfresco.war {noformat} So for me this looked like: {noformat} java -jar alfresco-mmt-2.1.1.jar .\email-listener_2.1RC2\emailListener.amp c:\bin\alfresco\tomcat\webapps\alfresco.war {noformat} # You should be able to verify the install by running: {noformat} java -jar alfresco-mmt-2.1.1.jar list c:\bin\alfresco\tomcat\webapps\alfresco.war {noformat} and you should see something like: {noformat} Module 'emailListener' installed in 'c:\bin\alfresco\tomcat\webapps\alfresco.war' - Title: EmailListener - Version: 2.1 - Install Date: Fri Dec 07 08:43:10 PST 2007 - Desription: EmailListener Module {noformat} # Finally, to start the service, just go into your Windows Service control panel and locate the service that is now named 'Alfresco Server'. You can start and stop Alfresco from this control panel. h1. Content Migration Now, in order to migrate content from old alfresco and normal file structures, I did the following: h3. For content already in alfresco: # Navigate to the space whose contents you want to migrate. For example, let's say I want to migrate the stuff from my personal space. I would navigate (using the WebUI) to the /MBARI/User Homes/kgomes space. You should see the contents of the kgomes folder from this view. # Click on 'More actions->View Details'. # On the right hand side, click on 'Export'. # For package name, I usually enter the space name followed by '_export', but it doesn't really matter. # Click on the link that says 'Click here to select the destination' and select somewhere that you will be able to download the .acp file from. # Select 'Current Space'. # Select 'Include Children'. # Uncheck 'Include this space' unless you have content (documents) in this specific folder (anything other than folders) that you want to migrate. This is a bit tricky, but there are two ways to do this. If you want to have the top level folder created, use the 'Include this space' and that will create the top level folder. Otherwise, if will expand into the folder in which you import the .acp file into. This is important in cases where the folder has already been created for you (like with user homes) and you have to migrate content into that folder. If you have the option to create the top level directory, by all means do so. # Uncheck 'Export in background' so you can force it to happen and you know when it is complete.]]> 3113538 9404998 9372262 17891495 17858746 17891498 17858749 16023554 15990786 17891497 17858748 17891493 17858744 15663808 15631055 15663809 15631056 15663803 15631050 15663806 15631053 15663799 15631046 15663801 15631048 15663793 15631040 6619138 6586370 28246026 2.7.4 -> 3.5.17 -> 5.0.3 -> latest (5.8 at time of writing this) h5. Steps # I.S. created a new VM named pompeii.shore.mbari.org that I will use to do all the stepwise upgrades # Java 1.6.0_36 was installed ]]> 28213258 28246025 28213257 10389191 10356479 15663994 15631243 15663993 15631242 3179451 3113966 3179453 3113968 15664002 Add/Remove Software) # In the Search tab, enter erlang and select the default erlang and install it. # Once it finishes, search for rabbitmq-server and install that. ]]> 15631252 3179455 3113970 15664001 Add/Remove Software) # Make sure under the Browse->Development tab/section that the Development Libraries and Development Tools are installed. # Make sure that a real Java SDK is installed (1.5+) before continuing (see java.com) # Click on the Search tab and enter 'openssl' then hit return. Make sure the openssl and openssl-devel are installed and if not, check the packages and click on 'Apply' (some dependencies may be installed as well). # In order to use the odbc functions for erlang (not necessarily need for us, but whatever), the odbc packages needed to be installed. In the Package Manager, I made sure the following were installed: ## unixODBC (both the i386 and the x86_64) ## unixODBC-devel (both the i386 and the x86_64) # I also needed to install the ncurses devel libraries with the package manager as well as the wxWidgets library. So using package manager, I installed (for i386 and x86_64 and then a bunch of dependencies were added): ## ncurses-devel ## wxGTK ## wxGTK-devel ## wxGTK-gl # Now for the current production release in the EPEL for rabbitmq (which is 2.1.0), we needed Erlang R13 (not 14 or 12). So this means I needed to build it. I went to erlang.org and downloaded the R13B04 tar.gz file and unpacked on my Desktop. # I opened a command terminal and ran: {noformat} cd ~/Desktop gunzip otp_src_R13B04.tar.gz tar -xvf otp_src_R13B04.tar cd otp_src_R13B04 ./configure --with-ssl --with-odbc make make install {noformat} # After installing Erlang 13B04, I went to rabbitmq.com and downloaded the 2.1.1 noarch rpm version of the rabbit mq server and ran the following in a terminal window: {noformat} yum localinstall rabbitmq-server-2.1.1-1.noarch.rpm {noformat} {note:title=digital key} I had to import rabbitmq's signing public key by running: wget http:://www.rabbitmq.com/rabbitmq-signing-key-public.asc then running gpg --import rabbitmq-signing-key-public.asc {note}]]> 15631251 3179457 3113972 15663999 Add/Remove Software) # Make sure under the Browse->Development tab/section that the Development Libraries and Development Tools are installed. # Make sure that a real Java SDK is installed (1.5+) before continuing (see java.com) # Click on the Search tab and enter 'openssl' then hit return. Make sure the openssl and openssl-devel are installed and if not, check the packages and click on 'Apply' (some dependencies may be installed as well). # In order to use the odbc functions for erlang (not necessarily need for us, but whatever), the odbc packages needed to be installed. In the Package Manager, I made sure the following were installed: ## unixODBC (both the i386 and the x86_64) ## unixODBC-devel (both the i386 and the x86_64) # I also needed to install the ncurses devel libraries with the package manager as well as the wxWidgets library. So using package manager, I installed (for i386 and x86_64 and then a bunch of dependencies were added): ## ncurses-devel ## wxGTK ## wxGTK-devel ## wxGTK-gl # Now for the current production release in the EPEL for rabbitmq (which is 2.1.0), we needed Erlang R13 (not 14 or 12). So this means I needed to build it. I went to erlang.org and downloaded the R13B04 tar.gz file and unpacked on my Desktop. # I opened a command terminal and ran: {noformat} cd ~/Desktop gunzip otp_src_R13B04.tar.gz tar -xvf otp_src_R13B04.tar cd otp_src_R13B04 ./configure --with-ssl --with-odbc make make install {noformat} # After installing Erlang 13B04, I went to rabbitmq.com and downloaded the 2.1.1 noarch rpm version of the rabbit mq server and ran the following in a terminal window: {noformat} yum localinstall rabbitmq-server-2.1.1-1.noarch.rpm {noformat}]]> 15631249 851 ... mbari MBARI Repository http://oceana.shore.mbari.org/maven2 ... ... {code} h3. Including a Dependency from the Repository Once the MBARI repository is included in you build, you can browse the repository to see what projects are available (just go to [http://oceana.shore.mbari.org/maven2]). If you find a dependency you need you can reference it in your _pom.xml_. Here's an example... {code:xml} ... ... qt4j qt4j 0.5 ... ... {code} h3. Putting a Dependency into the Repository The easiest way to put a dependency into the repository is to setup a Maven build file (i.e. _pom.xml_). In _pom.xml_ add the following _distributionManagement_ information: {code:xml} 4.0.0 qt4j qt4j jar 1.0-SNAPSHOT QT4J ... mbari-repository MBARI Repository scp://oceana.shore.mbari.org/var/www/html/maven2 {code} Executing _mvn deploy_ will put your build jar at http://oceana.shore.mbari.org/maven2////-.jar. In the example here it would put it into [http://oceana.shore.mbari.org/maven2/qt4j/qt4j/1.0-SNAPSHOT/] h3. Publishing Maven generated web sites Maven can generate a web site for a default web site for you. You can view samples of the currently published projects at [http://oceana.shore.mbari.org/projects]. It's not very interesting, however, it is a very simple way to publish the javadoc, sources and auto-generated reports. To do so modify your _pom.xml_: {code:xml} ... org.apache.maven.plugins maven-jxr-plugin org.apache.maven.plugins maven-pmd-plugin 1.5 org.apache.maven.plugins maven-checkstyle-plugin ... oceana.shore.mbari.org scp://oceana.shore.mbari.org/var/www/html/projects/${project.name} {code} Then run _mvn javadoc:javadoc site:site site:deploy_. This will build the javadocs, create a site with some useful reports, then publish the site (using scp) to oceana in the correct location. h2. Using the MBARI repository from an [Ant|http://ant.apache.org] project Maven repositories can be used from Ant build scripts using [Ivy|http://incubator.apache.org/ivy/]. h3. Referencing the repository In the directory containing the ant build file, _build.xml_, create a file called _ivyconf.xml_. _ivyconf.xml_ tells Ivy where to look for dependencies. The contents of the file will look something like: {code:xml} {code} h3. Including a Dependency from the Repository In the directory containing _build.xml_, create a file called _ivy.xml_. _ivy.xml_ tells Ivy what dependencies to include in your build. Here's an example of it's contents: {code:xml} {code} h3. Using Ivy from Ant The code below will fetch Ivy for you. SO you do not need install any additional software in order to get you build to work. In your ant build file include the following: {code:xml} ... {code} Calling _ant ivy.install_ will fetch all the dependencies from the web and put them into the _lib_ directory of your project. ]]> 854 28246065 2.7.4 -> 3.5.17 -> 5.0.3 -> latest (5.8 at time of writing this) h5. Steps # I.S. created a new VM named pompeii.shore.mbari.org that I will use to do all the stepwise upgrades # Java 1.6.0_36 was installed, so I asked for an update to the latest 1.8 version # I.S. created four databases for the upgrade path. # Per the installation instructions, for each of these databases, I performed the following using Aqua Data Studio {noformat} ALTER DATABASE COLLATE SQL_Latin1_General_CP1_CS_AS {noformat} # Per the installation instructions, for each database, I ran: {noformat} ALTER DATABASE SET READ_COMMITTED_SNAPSHOT ON WITH ROLLBACK IMMEDIATE; {noformat} # I VNC'd into pompeii.shore.mbari.org and fired up Firefox. # I downloaded the .tar.gz versions of the standalone for all the versions listed above. ]]> 28213296 28246062 2.7.4 -> 3.5.17 -> 5.0.3 -> latest (5.8 at time of writing this) h5. Steps # I.S. created a new VM named pompeii.shore.mbari.org that I will use to do all the stepwise upgrades # Java 1.6.0_36 was installed, so I asked for an update to the latest 1.8 version # I.S. created four databases for the upgrade path. # Per the installation instructions, for each of these databases, I performed the following using Aqua Data Studio {noformat} ALTER DATABASE COLLATE SQL_Latin1_General_CP1_CS_AS {noformat} # Per the installation instructions, for each database, I ran: {noformat} ALTER DATABASE SET READ_COMMITTED_SNAPSHOT ON WITH ROLLBACK IMMEDIATE; {noformat} ]]> 28213293 28246060 2.7.4 -> 3.5.17 -> 5.0.3 -> latest (5.8 at time of writing this) h5. Steps # I.S. created a new VM named pompeii.shore.mbari.org that I will use to do all the stepwise upgrades # Java 1.6.0_36 was installed, so I asked for an update to the latest 1.8 version ]]> 28213291 11829864 11797114 850 ... mbari MBARI Repository http://oceana.shore.mbari.org/maven2 ... ... {code} h3. Including a Dependency from the Repository Once the MBARI repository is included in you build, you can browse the repository to see what projects are available (just go to [http://oceana.shore.mbari.org/maven2]). If you find a dependency you need you can reference it in your _pom.xml_. Here's an example... {code:xml} ... ... qt4j qt4j 1.0-SNAPSHOT ... ... {code} h3. Putting a Dependency into the Repository The easiest way to put a dependency into the repository is to setup a Maven build file (i.e. _pom.xml_). In _pom.xml_ add the following _distributionManagement_ information: {code:xml} 4.0.0 qt4j qt4j jar 1.0-SNAPSHOT QT4J ... mbari-repository MBARI Repository scp://oceana.shore.mbari.org/var/www/html/maven2 {code} Executing _mvn deploy_ will put your build jar at http://oceana.shore.mbari.org/maven2////-.jar. In the example here it would put it into [http://oceana.shore.mbari.org/maven2/qt4j/qt4j/1.0-SNAPSHOT/] h3. Publishing Maven generated web sites Maven can generate a web site for a default web site for you. It's not very interesting, however, it is a very simple way to publish the javadocs and sources. To do so modify your _pom.xml_: {code:xml} ... org.apache.maven.plugins maven-jxr-plugin org.apache.maven.plugins maven-pmd-plugin 1.5 org.apache.maven.plugins maven-checkstyle-plugin ... oceana.shore.mbari.org scp://oceana.shore.mbari.org/var/www/html/projects/${project.name} {code} Then run _mvn javadoc:javadoc site:site site:deploy_. This will build the javadocs, create a site with some useful reports, then publish the site (using scp) to oceana in the correct location. h2. Using the MBARI repository from an [Ant|http://ant.apache.org] project Maven repositories can be used from Ant build scripts using [Ivy|http://incubator.apache.org/ivy/]. h3. Referencing the repository In the directory containing the ant build file, _build.xml_, create a file called _ivyconf.xml_. _ivyconf.xml_ tells Ivy where to look for dependencies. The contents of the file will look something like: {code:xml} {code} h3. Including a Dependency from the Repository In the directory containing _build.xml_, create a file called _ivy.xml_. _ivy.xml_ tells Ivy what dependencies to include in your build. Here's an example of it's contents: {code:xml} {code} h3. Using Ivy from Ant The code below will fetch Ivy for you. SO you do not need install any additional software in order to get you build to work. In your ant build file include the following: {code:xml} ... {code} Calling _ant ivy.install_ will fetch all the dependencies from the web and put them into the _lib_ directory of your project. ]]> 853 849 ... mbari MBARI Repository http://oceana.shore.mbari.org/maven2 ... ... {code} h3. Including a Dependency from the Repository Once the MBARI repository is included in you build, you can browse the repository to see what projects are available (just go to [http://oceana.shore.mbari.org/maven2]). If you find a dependency you need you can reference it in your _pom.xml_. Here's an example... {code:xml} ... ... qt4j qt4j 1.0-SNAPSHOT ... ... {code} h3. Putting a Dependency into the Repository The easiest way to put a dependency into the repository is to setup a Maven build file (i.e. _pom.xml_). In _pom.xml_ add the following _distributionManagement_ information: {code:xml} 4.0.0 qt4j qt4j jar 1.0-SNAPSHOT QT4J ... mbari-repository MBARI Repository scp://oceana.shore.mbari.org/var/www/html/maven2 {code} Executing _mvn deploy_ will put your build jar at http://oceana.shore.mbari.org/maven2////-.jar. In the example here it would put it into [http://oceana.shore.mbari.org/maven2/qt4j/qt4j/1.0-SNAPSHOT/] h2. Using the MBARI repository from an [Ant|http://ant.apache.org] project Maven repositories can be used from Ant build scripts using [Ivy|http://incubator.apache.org/ivy/]. h3. Referencing the repository In the directory containing the ant build file, _build.xml_, create a file called _ivyconf.xml_. _ivyconf.xml_ tells Ivy where to look for dependencies. The contents of the file will look something like: {code:xml} {code} h3. Including a Dependency from the Repository In the directory containing _build.xml_, create a file called _ivy.xml_. _ivy.xml_ tells Ivy what dependencies to include in your build. Here's an example of it's contents: {code:xml} {code} h3. Using Ivy from Ant The code below will fetch Ivy for you. SO you do not need install any additional software in order to get you build to work. In your ant build file include the following: {code:xml} ... {code} Calling _ant ivy.install_ will fetch all the dependencies from the web and put them into the _lib_ directory of your project. ]]> 852 821 ... mbari MBARI Repository http://oceana.shore.mbari.org/maven2 ... ... {code} h3. Including a Dependency from the Repository Once the MBARI repository is included in you build, you can browse the repository to see what projects are available (just go to [http://oceana.shore.mbari.org/maven2]). {code:xml} ... ... qt4j qt4j 1.0-SNAPSHOT ... ... {code} h2. Using the MBARI repository from an [Ant|http://ant.apache.org] project Maven repositories can be used from Ant build scripts using [Ivy|http://incubator.apache.org/ivy/]. h3. Referencing the repository In the directory containing the ant build file, _build.xml_, create a file called _ivyconf.xml_. _ivyconf.xml_ tells Ivy where to look for dependencies. The contents of the file will look something like: {code:xml} {code} h3. Including a Dependency from the Repository In the directory containing _build.xml_, create a file called _ivy.xml_. _ivy.xml_ tells Ivy what dependencies to include in your build. Here's an example of it's contents: {code:xml} {code}]]> 824 822 ... mbari MBARI Repository http://oceana.shore.mbari.org/maven2 ... ... {code} h3. Including a Dependency from the Repository Once the MBARI repository is included in you build, you can browse the repository to see what projects are available (just go to [http://oceana.shore.mbari.org/maven2]). {code:xml} ... ... qt4j qt4j 1.0-SNAPSHOT ... ... {code} h2. Using the MBARI repository from an [Ant|http://ant.apache.org] project Maven repositories can be used from Ant build scripts using [Ivy|http://incubator.apache.org/ivy/]. h3. Referencing the repository In the directory containing the ant build file, _build.xml_, create a file called _ivyconf.xml_. _ivyconf.xml_ tells Ivy where to look for dependencies. The contents of the file will look something like: {code:xml} {code} h3. Including a Dependency from the Repository In the directory containing _build.xml_, create a file called _ivy.xml_. _ivy.xml_ tells Ivy what dependencies to include in your build. Here's an example of it's contents: {code:xml} {code}]]> 825 819 ... mbari MBARI Repository http://oceana.shore.mbari.org/maven2 ... ... {code} h3. Including a Dependency from the Repository Once the MBARI repository is included in you build, you can browse the repository to see what projects are available (just go to [http://oceana.shore.mbari.org/maven2]). {code:xml} ... ... qt4j qt4j 1.0-SNAPSHOT ... ... {code} h2. Using the MBARI repository from an [Ant|http://ant.apache.org] project Maven repositories can be used from Ant build scripts using [Ivy|http://incubator.apache.org/ivy/]. h3. Referencing the repository In the directory containing the ant build file, _build.xml_, create a file called ivyconf.xml. The contents of the file will look something like: {code:xml} {code}]]> 822 820 ... mbari MBARI Repository http://oceana.shore.mbari.org/maven2 ... ... {code} h3. Including a Dependency from the Repository Once the MBARI repository is included in you build, you can browse the repository to see what projects are available (just go to [http://oceana.shore.mbari.org/maven2]). {code:xml} ... ... qt4j qt4j 1.0-SNAPSHOT ... ... {code} h2. Using the MBARI repository from an [Ant|http://ant.apache.org] project Maven repositories can be used from Ant build scripts using [Ivy|http://incubator.apache.org/ivy/]. h3. Referencing the repository In the directory containing the ant build file, _build.xml_, create a file called _ivyconf.xml_. _ivyconf.xml_ tells Ivy where to look for dependencies. The contents of the file will look something like: {code:xml} {code} h3. Including a Dependency from the Repository In the directory containing _build.xml_, create a file called _ivy.xml_. _ivy.xml_ tells Ivy what dependencies to include. Here's an example of it's contents: {code:xml} {code}]]> 823 825 ... mbari MBARI Repository http://oceana.shore.mbari.org/maven2 ... ... {code} h3. Including a Dependency from the Repository Once the MBARI repository is included in you build, you can browse the repository to see what projects are available (just go to [http://oceana.shore.mbari.org/maven2]). {code:xml} ... ... qt4j qt4j 1.0-SNAPSHOT ... ... {code} h2. Using the MBARI repository from an [Ant|http://ant.apache.org] project Maven repositories can be used from Ant build scripts using [Ivy|http://incubator.apache.org/ivy/]. h3. Referencing the repository In the directory containing the ant build file, _build.xml_, create a file called _ivyconf.xml_. _ivyconf.xml_ tells Ivy where to look for dependencies. The contents of the file will look something like: {code:xml} {code} h3. Including a Dependency from the Repository In the directory containing _build.xml_, create a file called _ivy.xml_. _ivy.xml_ tells Ivy what dependencies to include in your build. Here's an example of it's contents: {code:xml} {code} h3. Using Ivy from Ant In your ant build file include the following: {code:xml} ... {code} Calling _ant ivy.install_ will fetch all the dependencies from the web and put them into the _lib_ directory of your project. ]]> 828 823 ... mbari MBARI Repository http://oceana.shore.mbari.org/maven2 ... ... {code} h3. Including a Dependency from the Repository Once the MBARI repository is included in you build, you can browse the repository to see what projects are available (just go to [http://oceana.shore.mbari.org/maven2]). {code:xml} ... ... qt4j qt4j 1.0-SNAPSHOT ... ... {code} h2. Using the MBARI repository from an [Ant|http://ant.apache.org] project Maven repositories can be used from Ant build scripts using [Ivy|http://incubator.apache.org/ivy/]. h3. Referencing the repository In the directory containing the ant build file, _build.xml_, create a file called _ivyconf.xml_. _ivyconf.xml_ tells Ivy where to look for dependencies. The contents of the file will look something like: {code:xml} {code} h3. Including a Dependency from the Repository In the directory containing _build.xml_, create a file called _ivy.xml_. _ivy.xml_ tells Ivy what dependencies to include in your build. Here's an example of it's contents: {code:xml} {code} h3. Using Ivy from Ant In your ant build file include the following: {code:xml} ... Calling _ant ivy.install_ will fetch all the dependencies from the web and put them into the _lib_ directory of your project. {code} ]]> 826 3179504 'Downloads'>'2.1 Releases'>'2.1.1' # I changed to the 'Details View', made 40 items visible, and then downloaded 'alfresco-enterprise-tomcat-2.1.1.zip' file. # I then unzipped the downloaded file to c:\bin which created an alfresco-enterprise-tomcat-2.1.1 folder in c:\bin. # I renamed the alfresco-enterprise-tomcat-2.1.1 folder to simply alfresco. # I then went back to the web browser and went to 'Company Home'>'Downloads'>'2.1 Releases'>'2.1.1'>'License Files' # I am not sure if I can do this with our agreement, but I downloaded the 'enterprise-network-customer-unlimited.lic' file. {note} I did get approval from Joe Van De Graaff at Alfresco to use the license for a test installation to get us through this issue. {note} # I logged out of the Alfresco customer web site. # I Googled on jTDS to find the jTDS JDBC driver and downloaded the jtds-1.2.2-dist.zip file from the website. # Using Windows Explorer, I could just open the jTDS zip file and copy the jtds-1.2.2.jar file. # I then pasted it in the directory c:\bin\alfresco\tomcat\common\lib directory. # I created a c:\data\alf_data directory where the alfresco data will be stored. This is different from the production installation in that the content is stored on a network appliance (\\tornado.shore.mbari.org\alfresco). # I installed a copy of SQL Server 2005 locally to use for the database to back the Alfresco test install. {note} In order to do this without warnings, I had to go back and install IIS through the Add/Remove Programs Control Panel. {note} ## I used the Local System account to run services and only used Windows Authentication logins ## I installed all the service packs and the SQL Server Management Studio product to admin DBs. # In SQL Server, I added the SHORE\DB_Collaboration accounts to the logins. # I created a new database named alfresco-test and made SHORE\DB_Collaboration the owner. # I then went to the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions directory for the customization of the server. ## I edited the custom-repository.properties file ### Changed the dir.root and dir.indexes to look like: {noformat} dir.root=c:/data/alf_data dir.indexes=c:/data/alf_data/lucene-indexes {noformat} ### Commented out the db.* lines for the HSQL Connection (db.driver and db.url) ### Uncommented the db.* lines for MSSQL and changed to use the jTDS driver. They should look like: {noformat} db.driver=net.sourceforge.jtds.jdbc.Driver db.url=jdbc:jtds:sqlserver://localhost/alfresco-test;domain=SHORE;user=DB_Collaboration;password=XXXXXXXXX {noformat} ### I also added the following section to override the mail server settings {noformat} # Mail server configuration mail.host=mail.mbari.org mail.port=25 mail.username= mail.password= {noformat}]]> 3114020 3179506 'Downloads'>'2.1 Releases'>'2.1.1' # I changed to the 'Details View', made 40 items visible, and then downloaded 'alfresco-enterprise-tomcat-2.1.1.zip' file. # I then unzipped the downloaded file to c:\bin which created an alfresco-enterprise-tomcat-2.1.1 folder in c:\bin. # I renamed the alfresco-enterprise-tomcat-2.1.1 folder to simply alfresco. # I then went back to the web browser and went to 'Company Home'>'Downloads'>'2.1 Releases'>'2.1.1'>'License Files' # I am not sure if I can do this with our agreement, but I downloaded the 'enterprise-network-customer-unlimited.lic' file. {note} I did get approval from Joe Van De Graaff at Alfresco to use the license for a test installation to get us through this issue. {note} # I logged out of the Alfresco customer web site. # I Googled on jTDS to find the jTDS JDBC driver and downloaded the jtds-1.2.2-dist.zip file from the website. # Using Windows Explorer, I could just open the jTDS zip file and copy the jtds-1.2.2.jar file. # I then pasted it in the directory c:\bin\alfresco\tomcat\common\lib directory. # I created a c:\data\alf_data directory where the alfresco data will be stored. This is different from the production installation in that the content is stored on a network appliance (\\tornado.shore.mbari.org\alfresco). # I installed a copy of SQL Server 2005 locally to use for the database to back the Alfresco test install. {note} In order to do this without warnings, I had to go back and install IIS through the Add/Remove Programs Control Panel. {note} ## I used the Local System account to run services and only used Windows Authentication logins ## I installed all the service packs and the SQL Server Management Studio product to admin DBs. # In SQL Server, I added the SHORE\DB_Collaboration accounts to the logins. # I created a new database named alfresco-test and made SHORE\DB_Collaboration the owner. # I then went to the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions directory for the customization of the server. ## I edited the custom-repository.properties file ### Changed the dir.root and dir.indexes to look like: {noformat} dir.root=c:/data/alf_data dir.indexes=c:/data/alf_data/lucene-indexes {noformat} ### Commented out the db.* lines for the HSQL Connection (db.driver and db.url) ### Uncommented the db.* lines for MSSQL and changed to use the jTDS driver. They should look like (except the password should be the right one): {noformat} db.driver=net.sourceforge.jtds.jdbc.Driver db.url=jdbc:jtds:sqlserver://localhost/alfresco-test;domain=SHORE;user=DB_Collaboration;password=XXXXXXXXX {noformat} ### I also added the following section to override the mail server settings {noformat} # Mail server configuration mail.host=mail.mbari.org mail.port=25 mail.username= mail.password= {noformat} ## Edited the custom-hibernate-dialect.properties file ### Commented out the HSQL Dialect ### Uncommented the MSSQL Dialect # Now this is not necessarily fun, but in order to really get it configured the way we want it, you need to pull the original .war file out, edit some stuff inside and re-create the .war. {note} This should all be done before starting Alfresco for the first time. {note} # Copy the c:\bin\alfresco\tomcat\webapps\alfresco.war file to your home directory. # Make a second copy so that you will always the original (I copied to alfresco.war.orig and moved it somewhere else. It is important to move it and have only the alfresco.war file in the directory because when you un-jar it, all the files go right where alfresco.war is.) # From a command line, un-jar the war file using: {noformat} jar -xvf alfresco.war {noformat} # This unpacks a lot of files and after it completes, move (or delete) the alfresco.war file from the directory. This needs to be done so it does not end up in the new .war file. # I wanted to change the "Company Home" that seems to be everywhere to something that says MBARI. ## Edited ./WEB-INF/classes/alfresco/messages/webclient.properties and changed company_home from 'Company Home' to 'MBARI' ## Edited ./WEB-INF/classes/alfresco/messages/webclient_en_US.properties and changed company_home from 'Company Home' to 'MBARI' ## I edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces.properties and changed the first two lines to read {noformat} spaces.company_home.name=MBARI spaces.company_home.description=The root space for MBARI {noformat} ## Edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces_en_US.properties and made the same changes as the previous step {tip} This took a bit to find all these, and to be honest, I am not sure which one actually made the change on the GUI, but I suspect it was the _en_US ones. {tip} # When users are imported via LDAP, user spaces get created automatically. In order to put them where I wanted them to go (instead of right in the Company Home), I edited the ./WEB-INF/classes/alfresco/authentication-services-context.xml file. In the file there is a bean with an name of personalHomeFolderProvider. There is a property name 'path' and I added {noformat} /${spaces.user_homes.childname} {noformat} to the end to try to get them to create the user spaces there instead of in the Company Home. The final bean XML looks like: {noformat} /${spaces.company_home.childname}/${spaces.user_homes.childname} ${spaces.store} false All All {noformat} # I wanted to change the logo that is used. I attached the replacement logo [here|^AlfrescoLogo32.png]. Copy this to ./images/logo and overwrite the one that is there. # In order to setup SSL for the application (will do that later), edit ./WEB-INF/web.xml and add the following {noformat} Login Pages /* CONFIDENTIAL {noformat} right before the ending tag at the bottom of the file. # Now in order to change the default behavior so that all content is versioned from the start, I edited the .\WEB-INF\classes\alfresco\model\contentModel.xml and searched for the content type definition block. {noformat} Content cm:cmobject true d:content false true false true {noformat} and added the following block right before the ending tag: {noformat} cm:versionable {noformat} so the final block looks like: {noformat} Content cm:cmobject true d:content false true false true cm:versionable {noformat} # That takes care of all the changes to the WAR file. We can now put it back into .war form. # While you are in the directory you expanded the war file in, run ## jar cvfm alfresco.war META-INF\MANIFEST.MF .]]> 3114023 3179500 'Downloads'>'2.1 Releases'>'2.1.1' # I changed to the 'Details View', made 40 items visible, and then downloaded 'alfresco-enterprise-tomcat-2.1.1.zip' file. # I then unzipped the downloaded file to c:\bin which created an alfresco-enterprise-tomcat-2.1.1 folder in c:\bin. # I then went back to the web browser and went to 'Company Home'>'Downloads'>'2.1 Releases'>'2.1.1'>'License Files' # I am not sure if I can do this with our agreement, but I downloaded the 'enterprise-network-customer-unlimited.lic' file. {note} I did get approval from Joe Van De Graaff at Alfresco to use the license for a test installation to get us through this issue. {note} # I logged out of the Alfresco customer web site. # I Googled on jTDS to find the jTDS JDBC driver and downloaded the jtds-1.2.2-dist.zip file from the website. # Using Windows Explorer, I could just open the jTDS zip file and copy the jtds-1.2.2.jar file. # I then pasted it in the directory c:\bin\alfresco-enterprise-tomcat-2.1.1\tomcat\common\lib directory. # I created a c:\data\alf_data directory where the alfresco data will be stored. This is different from the production installation in that the content is stored on a network appliance (\\tornado.shore.mbari.org\alfresco). # I installed a copy of SQL Server 2005 locally to use for the database to back the Alfresco test install. {note} In order to do this without warnings, I had to go back and install IIS through the Add/Remove Programs Control Panel {note} ## I used the Local System account to run services and only used Windows Authentication logins]]> 3114016 831 ... mbari MBARI Repository http://oceana.shore.mbari.org/maven2 ... ... {code} h3. Including a Dependency from the Repository Once the MBARI repository is included in you build, you can browse the repository to see what projects are available (just go to [http://oceana.shore.mbari.org/maven2]). {code:xml} ... ... qt4j qt4j 1.0-SNAPSHOT ... ... {code} h3. Putting a Dependency into the Repository The easiest way to put a dependency into the repository is to setup a Maven build file (i.e. _pom.xml_). In _pom.xml_ add the following _distributionManagement_ information: {code:xml} 4.0.0 qt4j qt4j jar 1.0-SNAPSHOT QT4J ... mbari-repository MBARI Repository scp://oceana.shore.mbari.org/var/www/html/maven2 {code} Executing _mvn deploy_ will put your build jar at http://oceana.shore.mbari.org/maven2////-.jar. In the example here it would put it into [http://oceana.shore.mbari.org/maven2/qt4j/qt4j/1.0-SNAPSHOT/] h2. Using the MBARI repository from an [Ant|http://ant.apache.org] project Maven repositories can be used from Ant build scripts using [Ivy|http://incubator.apache.org/ivy/]. h3. Referencing the repository In the directory containing the ant build file, _build.xml_, create a file called _ivyconf.xml_. _ivyconf.xml_ tells Ivy where to look for dependencies. The contents of the file will look something like: {code:xml} {code} h3. Including a Dependency from the Repository In the directory containing _build.xml_, create a file called _ivy.xml_. _ivy.xml_ tells Ivy what dependencies to include in your build. Here's an example of it's contents: {code:xml} {code} h3. Using Ivy from Ant In your ant build file include the following: {code:xml} ... {code} Calling _ant ivy.install_ will fetch all the dependencies from the web and put them into the _lib_ directory of your project. ]]> 834 3179502 'Downloads'>'2.1 Releases'>'2.1.1' # I changed to the 'Details View', made 40 items visible, and then downloaded 'alfresco-enterprise-tomcat-2.1.1.zip' file. # I then unzipped the downloaded file to c:\bin which created an alfresco-enterprise-tomcat-2.1.1 folder in c:\bin. # I renamed the alfresco-enterprise-tomcat-2.1.1 folder to simply alfresco. # I then went back to the web browser and went to 'Company Home'>'Downloads'>'2.1 Releases'>'2.1.1'>'License Files' # I am not sure if I can do this with our agreement, but I downloaded the 'enterprise-network-customer-unlimited.lic' file. {note} I did get approval from Joe Van De Graaff at Alfresco to use the license for a test installation to get us through this issue. {note} # I logged out of the Alfresco customer web site. # I Googled on jTDS to find the jTDS JDBC driver and downloaded the jtds-1.2.2-dist.zip file from the website. # Using Windows Explorer, I could just open the jTDS zip file and copy the jtds-1.2.2.jar file. # I then pasted it in the directory c:\bin\alfresco\tomcat\common\lib directory. # I created a c:\data\alf_data directory where the alfresco data will be stored. This is different from the production installation in that the content is stored on a network appliance (\\tornado.shore.mbari.org\alfresco). # I installed a copy of SQL Server 2005 locally to use for the database to back the Alfresco test install. {note} In order to do this without warnings, I had to go back and install IIS through the Add/Remove Programs Control Panel. {note} ** I used the Local System account to run services and only used Windows Authentication logins ** I installed all the service packs and the SQL Server Management Studio product to admin DBs. # In SQL Server, I added the SHORE\DB_Collaboration accounts to the logins. # I created a new database named alfresco-test and made SHORE\DB_Collaboration the owner. # I then went to the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions directory for the customization of the server. ## I edited the custom-repository.properties file ### Changed the dir.root and dir.indexes to look like: {noformat} dir.root=c:/data/alf_data dir.indexes=c:/data/alf_data/lucene-indexes {noformat} ### Commented out the db.* lines for the HSQL Connection (db.driver and db.url) ### Uncommented the db.* lines for MSSQL and changed to use the jTDS driver. They should look like: {noformat} db.driver=net.sourceforge.jtds.jdbc.Driver db.url=jdbc:jtds:sqlserver://localhost/alfresco-test;domain=SHORE;user=DB_Collaboration;password=XXXXXXXXX {noformat} ### I also added the following section to override the mail server settings {noformat} # Mail server configuration mail.host=mail.mbari.org mail.port=25 mail.username= mail.password= {noformat}]]> 3114018 832 ... mbari MBARI Repository http://oceana.shore.mbari.org/maven2 ... ... {code} h3. Including a Dependency from the Repository Once the MBARI repository is included in you build, you can browse the repository to see what projects are available (just go to [http://oceana.shore.mbari.org/maven2]). {code:xml} ... ... qt4j qt4j 1.0-SNAPSHOT ... ... {code} h3. Putting a Dependency into the Repository The easiest way to put a dependency into the repository is to setup a Maven build file (i.e. _pom.xml_). In _pom.xml_ add the following _distributionManagement_ information: {code:xml} 4.0.0 qt4j qt4j jar 1.0-SNAPSHOT QT4J ... mbari-repository MBARI Repository scp://oceana.shore.mbari.org/var/www/html/maven2 {code} Executing _mvn deploy_ will put your build jar at http://oceana.shore.mbari.org/maven2////-.jar. In the example here it would put it into [http://oceana.shore.mbari.org/maven2/qt4j/qt4j/1.0-SNAPSHOT/] h2. Using the MBARI repository from an [Ant|http://ant.apache.org] project Maven repositories can be used from Ant build scripts using [Ivy|http://incubator.apache.org/ivy/]. h3. Referencing the repository In the directory containing the ant build file, _build.xml_, create a file called _ivyconf.xml_. _ivyconf.xml_ tells Ivy where to look for dependencies. The contents of the file will look something like: {code:xml} {code} h3. Including a Dependency from the Repository In the directory containing _build.xml_, create a file called _ivy.xml_. _ivy.xml_ tells Ivy what dependencies to include in your build. Here's an example of it's contents: {code:xml} {code} h3. Using Ivy from Ant The code below will fetch Ivy for you. SO you do not need install any additional software in order to get you build to work. In your ant build file include the following: {code:xml} ... {code} Calling _ant ivy.install_ will fetch all the dependencies from the web and put them into the _lib_ directory of your project. ]]> 835 3179512 'Downloads'>'2.1 Releases'>'2.1.1' # I changed to the 'Details View', made 40 items visible, and then downloaded 'alfresco-enterprise-tomcat-2.1.1.zip' file. # I then unzipped the downloaded file to c:\bin which created an alfresco-enterprise-tomcat-2.1.1 folder in c:\bin. # I renamed the alfresco-enterprise-tomcat-2.1.1 folder to simply alfresco. # I then went back to the web browser and went to 'Company Home'>'Downloads'>'2.1 Releases'>'2.1.1'>'License Files' # I am not sure if I can do this with our agreement, but I downloaded the 'enterprise-network-customer-unlimited.lic' file. {note} I did get approval from Joe Van De Graaff at Alfresco to use the license for a test installation to get us through this issue. {note} # I logged out of the Alfresco customer web site. # I Googled on jTDS to find the jTDS JDBC driver and downloaded the jtds-1.2.2-dist.zip file from the website. # Using Windows Explorer, I could just open the jTDS zip file and copy the jtds-1.2.2.jar file. # I then pasted it in the directory c:\bin\alfresco\tomcat\common\lib directory. # I created a c:\data\alf_data directory where the alfresco data will be stored. This is different from the production installation in that the content is stored on a network appliance (\\tornado.shore.mbari.org\alfresco). # I installed a copy of SQL Server 2005 locally to use for the database to back the Alfresco test install. {note} In order to do this without warnings, I had to go back and install IIS through the Add/Remove Programs Control Panel. {note} ## I used the Local System account to run services and only used Windows Authentication logins ## I installed all the service packs and the SQL Server Management Studio product to admin DBs. # In SQL Server, I added the SHORE\DB_Collaboration accounts to the logins. # I created a new database named alfresco-test and made SHORE\DB_Collaboration the owner. # I then went to the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions directory for the customization of the server. ## I edited the custom-repository.properties file ### Changed the dir.root and dir.indexes to look like: {noformat} dir.root=c:/data/alf_data dir.indexes=c:/data/alf_data/lucene-indexes {noformat} ### Commented out the db.* lines for the HSQL Connection (db.driver and db.url) ### Uncommented the db.* lines for MSSQL and changed to use the jTDS driver. They should look like (except the password should be the right one): {noformat} db.driver=net.sourceforge.jtds.jdbc.Driver db.url=jdbc:jtds:sqlserver://localhost/alfresco-test;domain=SHORE;user=DB_Collaboration;password=XXXXXXXXX {noformat} ### I also added the following section to override the mail server settings {noformat} # Mail server configuration mail.host=mail.mbari.org mail.port=25 mail.username= mail.password= {noformat} ## Edited the custom-hibernate-dialect.properties file ### Commented out the HSQL Dialect ### Uncommented the MSSQL Dialect # Now this is not necessarily fun, but in order to really get it configured the way we want it, you need to pull the original .war file out, edit some stuff inside and re-create the .war. {note} This should all be done before starting Alfresco for the first time. {note} # Copy the c:\bin\alfresco\tomcat\webapps\alfresco.war file to your home directory. # Make a second copy so that you will always the original (I copied to alfresco.war.orig and moved it somewhere else. It is important to move it and have only the alfresco.war file in the directory because when you un-jar it, all the files go right where alfresco.war is.) # From a command line, un-jar the war file using: {noformat} jar -xvf alfresco.war {noformat} # This unpacks a lot of files and after it completes, move (or delete) the alfresco.war file from the directory. This needs to be done so it does not end up in the new .war file. # I wanted to change the "Company Home" that seems to be everywhere to something that says MBARI. ## Edited ./WEB-INF/classes/alfresco/messages/webclient.properties and changed company_home from 'Company Home' to 'MBARI Test' ## Edited ./WEB-INF/classes/alfresco/messages/webclient_en_US.properties and changed company_home from 'Company Home' to 'MBARI Test' ## I edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces.properties and changed the first two lines to read {noformat} spaces.company_home.name=MBARI Test spaces.company_home.description=The root of MBARIs Test Alfresco Server {noformat} ## Edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces_en_US.properties and made the same changes as the previous step {tip} This took a bit to find all these, and to be honest, I am not sure which one actually made the change on the GUI, but I suspect it was the _en_US ones. {tip} # When users are imported via LDAP, user spaces get created automatically. In order to put them where I wanted them to go (instead of right in the Company Home), I edited the ./WEB-INF/classes/alfresco/authentication-services-context.xml file. In the file there is a bean with an name of personalHomeFolderProvider. There is a property name 'path' and I added {noformat} /${spaces.user_homes.childname} {noformat} to the end to try to get them to create the user spaces there instead of in the Company Home. The final bean XML looks like: {noformat} /${spaces.company_home.childname}/${spaces.user_homes.childname} ${spaces.store} false All All {noformat} # I wanted to change the logo that is used. I attached the replacement [Alfresco Logo|CLT:Installation Notes^AlfrescoLogo32.png]. Copy this to ./images/logo and overwrite the one that is there. {warning} Note that I did NOT setup SSL for this installation so if I will need to come back and do that if I want truly parallel systems {warning} # Now in order to change the default behavior so that all content is versioned from the start, I edited the .\WEB-INF\classes\alfresco\model\contentModel.xml and searched for the content type definition block. {noformat} Content cm:cmobject true d:content false true false true {noformat} and added the following block right before the ending tag: {noformat} cm:versionable {noformat} so the final block looks like: {noformat} Content cm:cmobject true d:content false true false true cm:versionable {noformat} # That takes care of all the changes to the WAR file. We can now put it back into .war form. # While you are in the directory you expanded the war file in, run ## jar cvfm alfresco.war META-INF\MANIFEST.MF . # You should now have an alfresco.war file in the directory. Move that back to the alfresco install and overwrite the existing one. # Most users like the details view, so I set the default to that by editing c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions\web-client-config-custom.xml and added: {noformat} details 20
20
20 {noformat} right before the closing tag. ]]> 3114029 3179514 'Downloads'>'2.1 Releases'>'2.1.1' # I changed to the 'Details View', made 40 items visible, and then downloaded 'alfresco-enterprise-tomcat-2.1.1.zip' file. # I then unzipped the downloaded file to c:\bin which created an alfresco-enterprise-tomcat-2.1.1 folder in c:\bin. # I renamed the alfresco-enterprise-tomcat-2.1.1 folder to simply alfresco. # I then went back to the web browser and went to 'Company Home'>'Downloads'>'2.1 Releases'>'2.1.1'>'License Files' # I am not sure if I can do this with our agreement, but I downloaded the 'enterprise-network-customer-unlimited.lic' file. {note} I did get approval from Joe Van De Graaff at Alfresco to use the license for a test installation to get us through this issue. {note} # I logged out of the Alfresco customer web site. # I Googled on jTDS to find the jTDS JDBC driver and downloaded the jtds-1.2.2-dist.zip file from the website. # Using Windows Explorer, I could just open the jTDS zip file and copy the jtds-1.2.2.jar file. # I then pasted it in the directory c:\bin\alfresco\tomcat\common\lib directory. # I created a c:\data\alf_data directory where the alfresco data will be stored. This is different from the production installation in that the content is stored on a network appliance (\\tornado.shore.mbari.org\alfresco). # I installed a copy of SQL Server 2005 locally to use for the database to back the Alfresco test install. {note} In order to do this without warnings, I had to go back and install IIS through the Add/Remove Programs Control Panel. {note} ## I used the Local System account to run services and only used Windows Authentication logins ## I installed all the service packs and the SQL Server Management Studio product to admin DBs. # In SQL Server, I added the SHORE\DB_Collaboration accounts to the logins. # I created a new database named alfresco-test and made SHORE\DB_Collaboration the owner. # I then went to the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions directory for the customization of the server. ## I edited the custom-repository.properties file ### Changed the dir.root and dir.indexes to look like: {noformat} dir.root=c:/data/alf_data dir.indexes=c:/data/alf_data/lucene-indexes {noformat} ### Commented out the db.* lines for the HSQL Connection (db.driver and db.url) ### Uncommented the db.* lines for MSSQL and changed to use the jTDS driver. They should look like (except the password should be the right one): {noformat} db.driver=net.sourceforge.jtds.jdbc.Driver db.url=jdbc:jtds:sqlserver://localhost/alfresco-test;domain=SHORE;user=DB_Collaboration;password=XXXXXXXXX {noformat} ### I also added the following section to override the mail server settings {noformat} # Mail server configuration mail.host=mail.mbari.org mail.port=25 mail.username= mail.password= {noformat} ## Edited the custom-hibernate-dialect.properties file ### Commented out the HSQL Dialect ### Uncommented the MSSQL Dialect # Now this is not necessarily fun, but in order to really get it configured the way we want it, you need to pull the original .war file out, edit some stuff inside and re-create the .war. {note} This should all be done before starting Alfresco for the first time. {note} # Copy the c:\bin\alfresco\tomcat\webapps\alfresco.war file to your home directory. # Make a second copy so that you will always the original (I copied to alfresco.war.orig and moved it somewhere else. It is important to move it and have only the alfresco.war file in the directory because when you un-jar it, all the files go right where alfresco.war is.) # From a command line, un-jar the war file using: {noformat} jar -xvf alfresco.war {noformat} # This unpacks a lot of files and after it completes, move (or delete) the alfresco.war file from the directory. This needs to be done so it does not end up in the new .war file. # I wanted to change the "Company Home" that seems to be everywhere to something that says MBARI. ## Edited ./WEB-INF/classes/alfresco/messages/webclient.properties and changed company_home from 'Company Home' to 'MBARI Test' ## Edited ./WEB-INF/classes/alfresco/messages/webclient_en_US.properties and changed company_home from 'Company Home' to 'MBARI Test' ## I edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces.properties and changed the first two lines to read {noformat} spaces.company_home.name=MBARI Test spaces.company_home.description=The root of MBARIs Test Alfresco Server {noformat} ## Edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces_en_US.properties and made the same changes as the previous step {tip} This took a bit to find all these, and to be honest, I am not sure which one actually made the change on the GUI, but I suspect it was the _en_US ones. {tip} # When users are imported via LDAP, user spaces get created automatically. In order to put them where I wanted them to go (instead of right in the Company Home), I edited the ./WEB-INF/classes/alfresco/authentication-services-context.xml file. In the file there is a bean with an name of personalHomeFolderProvider. There is a property name 'path' and I added {noformat} /${spaces.user_homes.childname} {noformat} to the end to try to get them to create the user spaces there instead of in the Company Home. The final bean XML looks like: {noformat} /${spaces.company_home.childname}/${spaces.user_homes.childname} ${spaces.store} false All All {noformat} # I wanted to change the logo that is used. I attached the replacement [Alfresco Logo|CLT:Installation Notes^AlfrescoLogo32.png]. Copy this to ./images/logo and overwrite the one that is there. {warning} Note that I did NOT setup SSL for this installation so if I will need to come back and do that if I want truly parallel systems {warning} # Now in order to change the default behavior so that all content is versioned from the start, I edited the .\WEB-INF\classes\alfresco\model\contentModel.xml and searched for the content type definition block. {noformat} Content cm:cmobject true d:content false true false true {noformat} and added the following block right before the ending tag: {noformat} cm:versionable {noformat} so the final block looks like: {noformat} Content cm:cmobject true d:content false true false true cm:versionable {noformat} # That takes care of all the changes to the WAR file. We can now put it back into .war form. # While you are in the directory you expanded the war file in, run ## jar cvfm alfresco.war META-INF\MANIFEST.MF . # You should now have an alfresco.war file in the directory. Move that back to the alfresco install and overwrite the existing one. # Most users like the details view, so I set the default to that by editing c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions\web-client-config-custom.xml and added: {noformat} details 20
20
20 {noformat} right before the closing tag. # Now in order to use MBARI accounts, NTLM authentication was turned on and then chained with the native Alfresco accounts so that we could have non-MBARI accounts on the Alfresco server. ## For simplicity sake, I have attached the files and you can simply download and install them in the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions directory. ### First install the ## In order to enable NTLM and native Alfresco authentication, I had to edit two files. For simplicity I have just attached them here and they can be downloaded and installed in the extensions directory. ### The first file is the [ntlm-authentication-context.xml|^ntlm-authentication-context.xml] file. This configures and enables NTLM authentication. ### The next file was the [chaining-authentication-context.xml|^chaining-authentication-context.xml] file which enabled Alfresco authentication and chained it together with the NTLM authentication from the previous file. # Then in order to setup CIFS on the server, I edited the file-servers-custom.xml file to look like the attached [file-servers-custom.xml|^file-servers-custom.xml] file. # In order to grant certain accounts admin privs, I created a new custom-authority-services-context.xml in the same directory as the ldap-authentication-context.xml file and added {noformat} kgomes admin administrator {noformat} # In order for Alfresco to handle all port 80 traffic, I changed Tomcat so that it takes port 80 and SSL goes over port 443. So I edited the c:\Alfresco\tomcat\conf\server.xml file and changed the 8080 port to 80 and the 8443 port to 443 (the 443 change is done in two places).]]> 3114031 3179508 'Downloads'>'2.1 Releases'>'2.1.1' # I changed to the 'Details View', made 40 items visible, and then downloaded 'alfresco-enterprise-tomcat-2.1.1.zip' file. # I then unzipped the downloaded file to c:\bin which created an alfresco-enterprise-tomcat-2.1.1 folder in c:\bin. # I renamed the alfresco-enterprise-tomcat-2.1.1 folder to simply alfresco. # I then went back to the web browser and went to 'Company Home'>'Downloads'>'2.1 Releases'>'2.1.1'>'License Files' # I am not sure if I can do this with our agreement, but I downloaded the 'enterprise-network-customer-unlimited.lic' file. {note} I did get approval from Joe Van De Graaff at Alfresco to use the license for a test installation to get us through this issue. {note} # I logged out of the Alfresco customer web site. # I Googled on jTDS to find the jTDS JDBC driver and downloaded the jtds-1.2.2-dist.zip file from the website. # Using Windows Explorer, I could just open the jTDS zip file and copy the jtds-1.2.2.jar file. # I then pasted it in the directory c:\bin\alfresco\tomcat\common\lib directory. # I created a c:\data\alf_data directory where the alfresco data will be stored. This is different from the production installation in that the content is stored on a network appliance (\\tornado.shore.mbari.org\alfresco). # I installed a copy of SQL Server 2005 locally to use for the database to back the Alfresco test install. {note} In order to do this without warnings, I had to go back and install IIS through the Add/Remove Programs Control Panel. {note} ## I used the Local System account to run services and only used Windows Authentication logins ## I installed all the service packs and the SQL Server Management Studio product to admin DBs. # In SQL Server, I added the SHORE\DB_Collaboration accounts to the logins. # I created a new database named alfresco-test and made SHORE\DB_Collaboration the owner. # I then went to the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions directory for the customization of the server. ## I edited the custom-repository.properties file ### Changed the dir.root and dir.indexes to look like: {noformat} dir.root=c:/data/alf_data dir.indexes=c:/data/alf_data/lucene-indexes {noformat} ### Commented out the db.* lines for the HSQL Connection (db.driver and db.url) ### Uncommented the db.* lines for MSSQL and changed to use the jTDS driver. They should look like (except the password should be the right one): {noformat} db.driver=net.sourceforge.jtds.jdbc.Driver db.url=jdbc:jtds:sqlserver://localhost/alfresco-test;domain=SHORE;user=DB_Collaboration;password=XXXXXXXXX {noformat} ### I also added the following section to override the mail server settings {noformat} # Mail server configuration mail.host=mail.mbari.org mail.port=25 mail.username= mail.password= {noformat} ## Edited the custom-hibernate-dialect.properties file ### Commented out the HSQL Dialect ### Uncommented the MSSQL Dialect # Now this is not necessarily fun, but in order to really get it configured the way we want it, you need to pull the original .war file out, edit some stuff inside and re-create the .war. {note} This should all be done before starting Alfresco for the first time. {note} # Copy the c:\bin\alfresco\tomcat\webapps\alfresco.war file to your home directory. # Make a second copy so that you will always the original (I copied to alfresco.war.orig and moved it somewhere else. It is important to move it and have only the alfresco.war file in the directory because when you un-jar it, all the files go right where alfresco.war is.) # From a command line, un-jar the war file using: {noformat} jar -xvf alfresco.war {noformat} # This unpacks a lot of files and after it completes, move (or delete) the alfresco.war file from the directory. This needs to be done so it does not end up in the new .war file. # I wanted to change the "Company Home" that seems to be everywhere to something that says MBARI. ## Edited ./WEB-INF/classes/alfresco/messages/webclient.properties and changed company_home from 'Company Home' to 'MBARI Test' ## Edited ./WEB-INF/classes/alfresco/messages/webclient_en_US.properties and changed company_home from 'Company Home' to 'MBARI Test' ## I edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces.properties and changed the first two lines to read {noformat} spaces.company_home.name=MBARI Test spaces.company_home.description=The root of MBARIs Test Alfresco Server {noformat} ## Edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces_en_US.properties and made the same changes as the previous step {tip} This took a bit to find all these, and to be honest, I am not sure which one actually made the change on the GUI, but I suspect it was the _en_US ones. {tip} # When users are imported via LDAP, user spaces get created automatically. In order to put them where I wanted them to go (instead of right in the Company Home), I edited the ./WEB-INF/classes/alfresco/authentication-services-context.xml file. In the file there is a bean with an name of personalHomeFolderProvider. There is a property name 'path' and I added {noformat} /${spaces.user_homes.childname} {noformat} to the end to try to get them to create the user spaces there instead of in the Company Home. The final bean XML looks like: {noformat} /${spaces.company_home.childname}/${spaces.user_homes.childname} ${spaces.store} false All All {noformat} # I wanted to change the logo that is used. I attached the replacement logo [here|^AlfrescoLogo32.png]. Copy this to ./images/logo and overwrite the one that is there. # In order to setup SSL for the application (will do that later), edit ./WEB-INF/web.xml and add the following {noformat} Login Pages /* CONFIDENTIAL {noformat} right before the ending tag at the bottom of the file. # Now in order to change the default behavior so that all content is versioned from the start, I edited the .\WEB-INF\classes\alfresco\model\contentModel.xml and searched for the content type definition block. {noformat} Content cm:cmobject true d:content false true false true {noformat} and added the following block right before the ending tag: {noformat} cm:versionable {noformat} so the final block looks like: {noformat} Content cm:cmobject true d:content false true false true cm:versionable {noformat} # That takes care of all the changes to the WAR file. We can now put it back into .war form. # While you are in the directory you expanded the war file in, run ## jar cvfm alfresco.war META-INF\MANIFEST.MF .]]> 3114025 3179510 'Downloads'>'2.1 Releases'>'2.1.1' # I changed to the 'Details View', made 40 items visible, and then downloaded 'alfresco-enterprise-tomcat-2.1.1.zip' file. # I then unzipped the downloaded file to c:\bin which created an alfresco-enterprise-tomcat-2.1.1 folder in c:\bin. # I renamed the alfresco-enterprise-tomcat-2.1.1 folder to simply alfresco. # I then went back to the web browser and went to 'Company Home'>'Downloads'>'2.1 Releases'>'2.1.1'>'License Files' # I am not sure if I can do this with our agreement, but I downloaded the 'enterprise-network-customer-unlimited.lic' file. {note} I did get approval from Joe Van De Graaff at Alfresco to use the license for a test installation to get us through this issue. {note} # I logged out of the Alfresco customer web site. # I Googled on jTDS to find the jTDS JDBC driver and downloaded the jtds-1.2.2-dist.zip file from the website. # Using Windows Explorer, I could just open the jTDS zip file and copy the jtds-1.2.2.jar file. # I then pasted it in the directory c:\bin\alfresco\tomcat\common\lib directory. # I created a c:\data\alf_data directory where the alfresco data will be stored. This is different from the production installation in that the content is stored on a network appliance (\\tornado.shore.mbari.org\alfresco). # I installed a copy of SQL Server 2005 locally to use for the database to back the Alfresco test install. {note} In order to do this without warnings, I had to go back and install IIS through the Add/Remove Programs Control Panel. {note} ## I used the Local System account to run services and only used Windows Authentication logins ## I installed all the service packs and the SQL Server Management Studio product to admin DBs. # In SQL Server, I added the SHORE\DB_Collaboration accounts to the logins. # I created a new database named alfresco-test and made SHORE\DB_Collaboration the owner. # I then went to the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions directory for the customization of the server. ## I edited the custom-repository.properties file ### Changed the dir.root and dir.indexes to look like: {noformat} dir.root=c:/data/alf_data dir.indexes=c:/data/alf_data/lucene-indexes {noformat} ### Commented out the db.* lines for the HSQL Connection (db.driver and db.url) ### Uncommented the db.* lines for MSSQL and changed to use the jTDS driver. They should look like (except the password should be the right one): {noformat} db.driver=net.sourceforge.jtds.jdbc.Driver db.url=jdbc:jtds:sqlserver://localhost/alfresco-test;domain=SHORE;user=DB_Collaboration;password=XXXXXXXXX {noformat} ### I also added the following section to override the mail server settings {noformat} # Mail server configuration mail.host=mail.mbari.org mail.port=25 mail.username= mail.password= {noformat} ## Edited the custom-hibernate-dialect.properties file ### Commented out the HSQL Dialect ### Uncommented the MSSQL Dialect # Now this is not necessarily fun, but in order to really get it configured the way we want it, you need to pull the original .war file out, edit some stuff inside and re-create the .war. {note} This should all be done before starting Alfresco for the first time. {note} # Copy the c:\bin\alfresco\tomcat\webapps\alfresco.war file to your home directory. # Make a second copy so that you will always the original (I copied to alfresco.war.orig and moved it somewhere else. It is important to move it and have only the alfresco.war file in the directory because when you un-jar it, all the files go right where alfresco.war is.) # From a command line, un-jar the war file using: {noformat} jar -xvf alfresco.war {noformat} # This unpacks a lot of files and after it completes, move (or delete) the alfresco.war file from the directory. This needs to be done so it does not end up in the new .war file. # I wanted to change the "Company Home" that seems to be everywhere to something that says MBARI. ## Edited ./WEB-INF/classes/alfresco/messages/webclient.properties and changed company_home from 'Company Home' to 'MBARI Test' ## Edited ./WEB-INF/classes/alfresco/messages/webclient_en_US.properties and changed company_home from 'Company Home' to 'MBARI Test' ## I edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces.properties and changed the first two lines to read {noformat} spaces.company_home.name=MBARI Test spaces.company_home.description=The root of MBARIs Test Alfresco Server {noformat} ## Edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces_en_US.properties and made the same changes as the previous step {tip} This took a bit to find all these, and to be honest, I am not sure which one actually made the change on the GUI, but I suspect it was the _en_US ones. {tip} # When users are imported via LDAP, user spaces get created automatically. In order to put them where I wanted them to go (instead of right in the Company Home), I edited the ./WEB-INF/classes/alfresco/authentication-services-context.xml file. In the file there is a bean with an name of personalHomeFolderProvider. There is a property name 'path' and I added {noformat} /${spaces.user_homes.childname} {noformat} to the end to try to get them to create the user spaces there instead of in the Company Home. The final bean XML looks like: {noformat} /${spaces.company_home.childname}/${spaces.user_homes.childname} ${spaces.store} false All All {noformat} # I wanted to change the logo that is used. I attached the replacement [Alfresco Logo|CLT:Installation Notes^AlfrescoLogo32.png]. Copy this to ./images/logo and overwrite the one that is there. # In order to setup SSL for the application (will do that later), edit ./WEB-INF/web.xml and add the following {noformat} Login Pages /* CONFIDENTIAL {noformat} right before the ending tag at the bottom of the file. # Now in order to change the default behavior so that all content is versioned from the start, I edited the .\WEB-INF\classes\alfresco\model\contentModel.xml and searched for the content type definition block. {noformat} Content cm:cmobject true d:content false true false true {noformat} and added the following block right before the ending tag: {noformat} cm:versionable {noformat} so the final block looks like: {noformat} Content cm:cmobject true d:content false true false true cm:versionable {noformat} # That takes care of all the changes to the WAR file. We can now put it back into .war form. # While you are in the directory you expanded the war file in, run ## jar cvfm alfresco.war META-INF\MANIFEST.MF .]]> 3114027 3179520 'Downloads'>'2.1 Releases'>'2.1.1' # I changed to the 'Details View', made 40 items visible, and then downloaded 'alfresco-enterprise-tomcat-2.1.1.zip' file. # I then unzipped the downloaded file to c:\bin which created an alfresco-enterprise-tomcat-2.1.1 folder in c:\bin. # I renamed the alfresco-enterprise-tomcat-2.1.1 folder to simply alfresco. # I then went back to the web browser and went to 'Company Home'>'Downloads'>'2.1 Releases'>'2.1.1'>'License Files' # I am not sure if I can do this with our agreement, but I downloaded the 'enterprise-network-customer-unlimited.lic' file. {note} I did get approval from Joe Van De Graaff at Alfresco to use the license for a test installation to get us through this issue. {note} # I logged out of the Alfresco customer web site. # I Googled on jTDS to find the jTDS JDBC driver and downloaded the jtds-1.2.2-dist.zip file from the website. # Using Windows Explorer, I could just open the jTDS zip file and copy the jtds-1.2.2.jar file. # I then pasted it in the directory c:\bin\alfresco\tomcat\common\lib directory. # I created a c:\data\alf_data directory where the alfresco data will be stored. This is different from the production installation in that the content is stored on a network appliance (\\tornado.shore.mbari.org\alfresco). # I installed a copy of SQL Server 2005 locally to use for the database to back the Alfresco test install. {note} In order to do this without warnings, I had to go back and install IIS through the Add/Remove Programs Control Panel. {note} ## I used the Local System account to run services and only used Windows Authentication logins ## I installed all the service packs and the SQL Server Management Studio product to admin DBs. # In SQL Server, I added the SHORE\DB_Collaboration accounts to the logins. # I created a new database named alfresco-test and made SHORE\DB_Collaboration the owner. # I then went to the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions directory for the customization of the server. ## I edited the custom-repository.properties file ### Changed the dir.root and dir.indexes to look like: {noformat} dir.root=c:/data/alf_data dir.indexes=c:/data/alf_data/lucene-indexes {noformat} ### Commented out the db.* lines for the HSQL Connection (db.driver and db.url) ### Uncommented the db.* lines for MSSQL and changed to use the jTDS driver. They should look like (except the password should be the right one): {noformat} db.driver=net.sourceforge.jtds.jdbc.Driver db.url=jdbc:jtds:sqlserver://localhost/alfresco-test;domain=SHORE;user=DB_Collaboration;password=XXXXXXXXX {noformat} ### I also added the following section to override the mail server settings {noformat} # Mail server configuration mail.host=mail.mbari.org mail.port=25 mail.username= mail.password= {noformat} ## Edited the custom-hibernate-dialect.properties file ### Commented out the HSQL Dialect ### Uncommented the MSSQL Dialect # Now this is not necessarily fun, but in order to really get it configured the way we want it, you need to pull the original .war file out, edit some stuff inside and re-create the .war. {note} This should all be done before starting Alfresco for the first time. {note} # Copy the c:\bin\alfresco\tomcat\webapps\alfresco.war file to your home directory. # Make a second copy so that you will always the original (I copied to alfresco.war.orig and moved it somewhere else. It is important to move it and have only the alfresco.war file in the directory because when you un-jar it, all the files go right where alfresco.war is.) # From a command line, un-jar the war file using: {noformat} jar -xvf alfresco.war {noformat} # This unpacks a lot of files and after it completes, move (or delete) the alfresco.war file from the directory. This needs to be done so it does not end up in the new .war file. # I wanted to change the "Company Home" that seems to be everywhere to something that says MBARI. ## Edited ./WEB-INF/classes/alfresco/messages/webclient.properties and changed company_home from 'Company Home' to 'MBARI Test' ## Edited ./WEB-INF/classes/alfresco/messages/webclient_en_US.properties and changed company_home from 'Company Home' to 'MBARI Test' ## I edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces.properties and changed the first two lines to read {noformat} spaces.company_home.name=MBARI Test spaces.company_home.description=The root of MBARIs Test Alfresco Server {noformat} ## Edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces_en_US.properties and made the same changes as the previous step {tip} This took a bit to find all these, and to be honest, I am not sure which one actually made the change on the GUI, but I suspect it was the _en_US ones. {tip} # When users are imported via LDAP, user spaces get created automatically. In order to put them where I wanted them to go (instead of right in the Company Home), I edited the ./WEB-INF/classes/alfresco/authentication-services-context.xml file. In the file there is a bean with an name of personalHomeFolderProvider. There is a property name 'path' and I added {noformat} /${spaces.user_homes.childname} {noformat} to the end to try to get them to create the user spaces there instead of in the Company Home. The final bean XML looks like: {noformat} /${spaces.company_home.childname}/${spaces.user_homes.childname} ${spaces.store} false All All {noformat} # I wanted to change the logo that is used. I attached the replacement [Alfresco Logo|CLT:Installation Notes^AlfrescoLogo32.png]. Copy this to ./images/logo and overwrite the one that is there. {warning} Note that I did NOT setup SSL for this installation so if I will need to come back and do that if I want truly parallel systems {warning} # Now in order to change the default behavior so that all content is versioned from the start, I edited the .\WEB-INF\classes\alfresco\model\contentModel.xml and searched for the content type definition block. {noformat} Content cm:cmobject true d:content false true false true {noformat} and added the following block right before the ending tag: {noformat} cm:versionable {noformat} so the final block looks like: {noformat} Content cm:cmobject true d:content false true false true cm:versionable {noformat} # That takes care of all the changes to the WAR file. We can now put it back into .war form. # While you are in the directory you expanded the war file in, run ## jar cvfm alfresco.war META-INF\MANIFEST.MF . # You should now have an alfresco.war file in the directory. Move that back to the alfresco install and overwrite the existing one. # Most users like the details view, so I set the default to that by editing c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions\web-client-config-custom.xml and added: {noformat} details 20
20
20 {noformat} right before the closing tag. # Now in order to use MBARI accounts, NTLM authentication was turned on and then chained with the native Alfresco accounts so that we could have non-MBARI accounts on the Alfresco server. ## For simplicity sake, I have attached the files and you can simply download and install them in the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions directory. {note} Before doing these next steps, rename the file-servers-custom.xml file to file-servers-custom.xml.orig so you will have a backup of the original {note} ### First install the [NTLM Configuration XML File|^ntlm-authentication-context.xml] ### Next install the [Authentication Chaining Configuration File|^chaining-authentication-context.xml] ### Next install the [CIFS configuration|^file-servers-custom.xml] file and over-write the existing one. {warning} Make sure you change the tag to reflect a unique name on the network. {warning} # Then in order to setup CIFS on the server, I edited the file-servers-custom.xml file to look like the attached [file-servers-custom.xml|^file-servers-custom.xml] file. # In order to grant certain accounts admin privs, I created a new custom-authority-services-context.xml in the same directory as the ldap-authentication-context.xml file and added {noformat} kgomes admin administrator {noformat} # In order for Alfresco to handle all port 80 traffic, I changed Tomcat so that it takes port 80 and SSL goes over port 443. So I edited the c:\Alfresco\tomcat\conf\server.xml file and changed the 8080 port to 80 and the 8443 port to 443 (the 443 change is done in two places).]]> 3114037 814 ... mbari MBARI Repository http://oceana.shore.mbari.org/maven2 ... ... {code} h3. Including a Dependency from the Repository Once the MBARI repository is included in you build, you can browse the repository to see what projects are available (just go to [http://oceana.shore.mbari.org/maven2]). {code:xml} ... ... qt4j qt4j 1.0-SNAPSHOT ... ... {code} h2. Including ]]> 817 813 ... mbari MBARI Repository http://oceana.shore.mbari.org/maven2 ... ... {code} h3. Including a Dependency from the Repository {code:xml} ... ... qt4j qt4j 1.0-SNAPSHOT ... ... {code} h2. Including ]]> 816 812 ... mbari MBARI Repository http://oceana.shore.mbari.org/maven2 ... ... {code}]]> 815 3179521 'Downloads'>'2.1 Releases'>'2.1.1' # I changed to the 'Details View', made 40 items visible, and then downloaded 'alfresco-enterprise-tomcat-2.1.1.zip' file. # I then unzipped the downloaded file to c:\bin which created an alfresco-enterprise-tomcat-2.1.1 folder in c:\bin. # I renamed the alfresco-enterprise-tomcat-2.1.1 folder to simply alfresco. # I then went back to the web browser and went to 'Company Home'>'Downloads'>'2.1 Releases'>'2.1.1'>'License Files' # I am not sure if I can do this with our agreement, but I downloaded the 'enterprise-network-customer-unlimited.lic' file. {note} I did get approval from Joe Van De Graaff at Alfresco to use the license for a test installation to get us through this issue. {note} # I logged out of the Alfresco customer web site. # I Googled on jTDS to find the jTDS JDBC driver and downloaded the jtds-1.2.2-dist.zip file from the website. # Using Windows Explorer, I could just open the jTDS zip file and copy the jtds-1.2.2.jar file. # I then pasted it in the directory c:\bin\alfresco\tomcat\common\lib directory. # I created a c:\data\alf_data directory where the alfresco data will be stored. This is different from the production installation in that the content is stored on a network appliance (\\tornado.shore.mbari.org\alfresco). # I installed a copy of SQL Server 2005 locally to use for the database to back the Alfresco test install. {note} In order to do this without warnings, I had to go back and install IIS through the Add/Remove Programs Control Panel. {note} ## I used the Local System account to run services and only used Windows Authentication logins ## I installed all the service packs and the SQL Server Management Studio product to admin DBs. # In SQL Server, I added the SHORE\DB_Collaboration accounts to the logins. # I created a new database named alfresco-test and made SHORE\DB_Collaboration the owner. # I then went to the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions directory for the customization of the server. ## I edited the custom-repository.properties file ### Changed the dir.root and dir.indexes to look like: {noformat} dir.root=c:/data/alf_data dir.indexes=c:/data/alf_data/lucene-indexes {noformat} ### Commented out the db.* lines for the HSQL Connection (db.driver and db.url) ### Uncommented the db.* lines for MSSQL and changed to use the jTDS driver. They should look like (except the password should be the right one): {noformat} db.driver=net.sourceforge.jtds.jdbc.Driver db.url=jdbc:jtds:sqlserver://localhost/alfresco-test;domain=SHORE;user=DB_Collaboration;password=XXXXXXXXX {noformat} ### I also added the following section to override the mail server settings {noformat} # Mail server configuration mail.host=mail.mbari.org mail.port=25 mail.username= mail.password= {noformat} ## Edited the custom-hibernate-dialect.properties file ### Commented out the HSQL Dialect ### Uncommented the MSSQL Dialect # Now this is not necessarily fun, but in order to really get it configured the way we want it, you need to pull the original .war file out, edit some stuff inside and re-create the .war. {note} This should all be done before starting Alfresco for the first time. {note} # Copy the c:\bin\alfresco\tomcat\webapps\alfresco.war file to your home directory. # Make a second copy so that you will always the original (I copied to alfresco.war.orig and moved it somewhere else. It is important to move it and have only the alfresco.war file in the directory because when you un-jar it, all the files go right where alfresco.war is.) # From a command line, un-jar the war file using: {noformat} jar -xvf alfresco.war {noformat} # This unpacks a lot of files and after it completes, move (or delete) the alfresco.war file from the directory. This needs to be done so it does not end up in the new .war file. # I wanted to change the "Company Home" that seems to be everywhere to something that says MBARI. ## Edited ./WEB-INF/classes/alfresco/messages/webclient.properties and changed company_home from 'Company Home' to 'MBARI Test' ## Edited ./WEB-INF/classes/alfresco/messages/webclient_en_US.properties and changed company_home from 'Company Home' to 'MBARI Test' ## I edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces.properties and changed the first two lines to read {noformat} spaces.company_home.name=MBARI Test spaces.company_home.description=The root of MBARIs Test Alfresco Server {noformat} ## Edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces_en_US.properties and made the same changes as the previous step {tip} This took a bit to find all these, and to be honest, I am not sure which one actually made the change on the GUI, but I suspect it was the _en_US ones. {tip} # When users are imported via LDAP, user spaces get created automatically. In order to put them where I wanted them to go (instead of right in the Company Home), I edited the ./WEB-INF/classes/alfresco/authentication-services-context.xml file. In the file there is a bean with an name of personalHomeFolderProvider. There is a property name 'path' and I added {noformat} /${spaces.user_homes.childname} {noformat} to the end to try to get them to create the user spaces there instead of in the Company Home. The final bean XML looks like: {noformat} /${spaces.company_home.childname}/${spaces.user_homes.childname} ${spaces.store} false All All {noformat} # I wanted to change the logo that is used. I attached the replacement [Alfresco Logo|CLT:Installation Notes^AlfrescoLogo32.png]. Copy this to ./images/logo and overwrite the one that is there. {warning} Note that I did NOT setup SSL for this installation so if I will need to come back and do that if I want truly parallel systems {warning} # Now in order to change the default behavior so that all content is versioned from the start, I edited the .\WEB-INF\classes\alfresco\model\contentModel.xml and searched for the content type definition block. {noformat} Content cm:cmobject true d:content false true false true {noformat} and added the following block right before the ending tag: {noformat} cm:versionable {noformat} so the final block looks like: {noformat} Content cm:cmobject true d:content false true false true cm:versionable {noformat} # That takes care of all the changes to the WAR file. We can now put it back into .war form. # While you are in the directory you expanded the war file in, run ## jar cvfm alfresco.war META-INF\MANIFEST.MF . # You should now have an alfresco.war file in the directory. Move that back to the alfresco install and overwrite the existing one. # Most users like the details view, so I set the default to that by editing c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions\web-client-config-custom.xml and added: {noformat} details 20
20
20 {noformat} right before the closing tag. # Now in order to use MBARI accounts, NTLM authentication was turned on and then chained with the native Alfresco accounts so that we could have non-MBARI accounts on the Alfresco server. ## For simplicity sake, I have attached the files and you can simply download and install them in the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions directory. {note} Before doing these next steps, rename the file-servers-custom.xml file to file-servers-custom.xml.orig so you will have a backup of the original {note} ### First install the [NTLM Configuration XML File|^ntlm-authentication-context.xml] ### Next install the [Authentication Chaining Configuration File|^chaining-authentication-context.xml] ### Next install the [CIFS configuration|^file-servers-custom.xml] file and over-write the existing one. {warning} In the CIFS configuration file, make sure you change the tag to reflect a unique name on the network. {warning} ### Next install the file. # In order to grant certain accounts admin privs, I created a new custom-authority-services-context.xml in the same directory as the ldap-authentication-context.xml file and added {noformat} kgomes admin administrator {noformat} # In order for Alfresco to handle all port 80 traffic, I changed Tomcat so that it takes port 80 and SSL goes over port 443. So I edited the c:\Alfresco\tomcat\conf\server.xml file and changed the 8080 port to 80 and the 8443 port to 443 (the 443 change is done in two places).]]> 3114038 3179516 'Downloads'>'2.1 Releases'>'2.1.1' # I changed to the 'Details View', made 40 items visible, and then downloaded 'alfresco-enterprise-tomcat-2.1.1.zip' file. # I then unzipped the downloaded file to c:\bin which created an alfresco-enterprise-tomcat-2.1.1 folder in c:\bin. # I renamed the alfresco-enterprise-tomcat-2.1.1 folder to simply alfresco. # I then went back to the web browser and went to 'Company Home'>'Downloads'>'2.1 Releases'>'2.1.1'>'License Files' # I am not sure if I can do this with our agreement, but I downloaded the 'enterprise-network-customer-unlimited.lic' file. {note} I did get approval from Joe Van De Graaff at Alfresco to use the license for a test installation to get us through this issue. {note} # I logged out of the Alfresco customer web site. # I Googled on jTDS to find the jTDS JDBC driver and downloaded the jtds-1.2.2-dist.zip file from the website. # Using Windows Explorer, I could just open the jTDS zip file and copy the jtds-1.2.2.jar file. # I then pasted it in the directory c:\bin\alfresco\tomcat\common\lib directory. # I created a c:\data\alf_data directory where the alfresco data will be stored. This is different from the production installation in that the content is stored on a network appliance (\\tornado.shore.mbari.org\alfresco). # I installed a copy of SQL Server 2005 locally to use for the database to back the Alfresco test install. {note} In order to do this without warnings, I had to go back and install IIS through the Add/Remove Programs Control Panel. {note} ## I used the Local System account to run services and only used Windows Authentication logins ## I installed all the service packs and the SQL Server Management Studio product to admin DBs. # In SQL Server, I added the SHORE\DB_Collaboration accounts to the logins. # I created a new database named alfresco-test and made SHORE\DB_Collaboration the owner. # I then went to the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions directory for the customization of the server. ## I edited the custom-repository.properties file ### Changed the dir.root and dir.indexes to look like: {noformat} dir.root=c:/data/alf_data dir.indexes=c:/data/alf_data/lucene-indexes {noformat} ### Commented out the db.* lines for the HSQL Connection (db.driver and db.url) ### Uncommented the db.* lines for MSSQL and changed to use the jTDS driver. They should look like (except the password should be the right one): {noformat} db.driver=net.sourceforge.jtds.jdbc.Driver db.url=jdbc:jtds:sqlserver://localhost/alfresco-test;domain=SHORE;user=DB_Collaboration;password=XXXXXXXXX {noformat} ### I also added the following section to override the mail server settings {noformat} # Mail server configuration mail.host=mail.mbari.org mail.port=25 mail.username= mail.password= {noformat} ## Edited the custom-hibernate-dialect.properties file ### Commented out the HSQL Dialect ### Uncommented the MSSQL Dialect # Now this is not necessarily fun, but in order to really get it configured the way we want it, you need to pull the original .war file out, edit some stuff inside and re-create the .war. {note} This should all be done before starting Alfresco for the first time. {note} # Copy the c:\bin\alfresco\tomcat\webapps\alfresco.war file to your home directory. # Make a second copy so that you will always the original (I copied to alfresco.war.orig and moved it somewhere else. It is important to move it and have only the alfresco.war file in the directory because when you un-jar it, all the files go right where alfresco.war is.) # From a command line, un-jar the war file using: {noformat} jar -xvf alfresco.war {noformat} # This unpacks a lot of files and after it completes, move (or delete) the alfresco.war file from the directory. This needs to be done so it does not end up in the new .war file. # I wanted to change the "Company Home" that seems to be everywhere to something that says MBARI. ## Edited ./WEB-INF/classes/alfresco/messages/webclient.properties and changed company_home from 'Company Home' to 'MBARI Test' ## Edited ./WEB-INF/classes/alfresco/messages/webclient_en_US.properties and changed company_home from 'Company Home' to 'MBARI Test' ## I edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces.properties and changed the first two lines to read {noformat} spaces.company_home.name=MBARI Test spaces.company_home.description=The root of MBARIs Test Alfresco Server {noformat} ## Edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces_en_US.properties and made the same changes as the previous step {tip} This took a bit to find all these, and to be honest, I am not sure which one actually made the change on the GUI, but I suspect it was the _en_US ones. {tip} # When users are imported via LDAP, user spaces get created automatically. In order to put them where I wanted them to go (instead of right in the Company Home), I edited the ./WEB-INF/classes/alfresco/authentication-services-context.xml file. In the file there is a bean with an name of personalHomeFolderProvider. There is a property name 'path' and I added {noformat} /${spaces.user_homes.childname} {noformat} to the end to try to get them to create the user spaces there instead of in the Company Home. The final bean XML looks like: {noformat} /${spaces.company_home.childname}/${spaces.user_homes.childname} ${spaces.store} false All All {noformat} # I wanted to change the logo that is used. I attached the replacement [Alfresco Logo|CLT:Installation Notes^AlfrescoLogo32.png]. Copy this to ./images/logo and overwrite the one that is there. {warning} Note that I did NOT setup SSL for this installation so if I will need to come back and do that if I want truly parallel systems {warning} # Now in order to change the default behavior so that all content is versioned from the start, I edited the .\WEB-INF\classes\alfresco\model\contentModel.xml and searched for the content type definition block. {noformat} Content cm:cmobject true d:content false true false true {noformat} and added the following block right before the ending tag: {noformat} cm:versionable {noformat} so the final block looks like: {noformat} Content cm:cmobject true d:content false true false true cm:versionable {noformat} # That takes care of all the changes to the WAR file. We can now put it back into .war form. # While you are in the directory you expanded the war file in, run ## jar cvfm alfresco.war META-INF\MANIFEST.MF . # You should now have an alfresco.war file in the directory. Move that back to the alfresco install and overwrite the existing one. # Most users like the details view, so I set the default to that by editing c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions\web-client-config-custom.xml and added: {noformat} details 20
20
20 {noformat} right before the closing tag. # Now in order to use MBARI accounts, NTLM authentication was turned on and then chained with the native Alfresco accounts so that we could have non-MBARI accounts on the Alfresco server. ## For simplicity sake, I have attached the files and you can simply download and install them in the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions directory. ### First install the [NTLM Configuration XML File|^ntlm-authentication-context.xml] ### Next install the [Authentication Chaining Configuration File|^chaining-authentication-context.xml] # Then in order to setup CIFS on the server, I edited the file-servers-custom.xml file to look like the attached [file-servers-custom.xml|^file-servers-custom.xml] file. # In order to grant certain accounts admin privs, I created a new custom-authority-services-context.xml in the same directory as the ldap-authentication-context.xml file and added {noformat} kgomes admin administrator {noformat} # In order for Alfresco to handle all port 80 traffic, I changed Tomcat so that it takes port 80 and SSL goes over port 443. So I edited the c:\Alfresco\tomcat\conf\server.xml file and changed the 8080 port to 80 and the 8443 port to 443 (the 443 change is done in two places).]]> 3114033 818 ... mbari MBARI Repository http://oceana.shore.mbari.org/maven2 ... ... {code} h3. Including a Dependency from the Repository Once the MBARI repository is included in you build, you can browse the repository to see what projects are available (just go to [http://oceana.shore.mbari.org/maven2]). {code:xml} ... ... qt4j qt4j 1.0-SNAPSHOT ... ... {code} h2. Using the MBARI repository from an [Ant|http://ant.apache.org] project Maven repositories can be used from Ant build scripts using [Ivy|http://incubator.apache.org/ivy/]. h3. Referencing the repository In the directory containing the ant build file, _build.xml_, create a file called ivyconf.xml. The contents of the file will look something like: {code:xml} {code}]]> 821 817 ... mbari MBARI Repository http://oceana.shore.mbari.org/maven2 ... ... {code} h3. Including a Dependency from the Repository Once the MBARI repository is included in you build, you can browse the repository to see what projects are available (just go to [http://oceana.shore.mbari.org/maven2]). {code:xml} ... ... qt4j qt4j 1.0-SNAPSHOT ... ... {code} h2. Using the MBARI repository from an [Ant|http://ant.apache.org] project Maven repositories can be used from Ant build scripts using [Ivy|http://incubator.apache.org/ivy/]. h3. Referencing the repository In the directory containing the ant build file, _build.xml_, create a file called ivyconf.xml. The contents of the file will look something like: {code:xml} {code}]]> 820 3179518 'Downloads'>'2.1 Releases'>'2.1.1' # I changed to the 'Details View', made 40 items visible, and then downloaded 'alfresco-enterprise-tomcat-2.1.1.zip' file. # I then unzipped the downloaded file to c:\bin which created an alfresco-enterprise-tomcat-2.1.1 folder in c:\bin. # I renamed the alfresco-enterprise-tomcat-2.1.1 folder to simply alfresco. # I then went back to the web browser and went to 'Company Home'>'Downloads'>'2.1 Releases'>'2.1.1'>'License Files' # I am not sure if I can do this with our agreement, but I downloaded the 'enterprise-network-customer-unlimited.lic' file. {note} I did get approval from Joe Van De Graaff at Alfresco to use the license for a test installation to get us through this issue. {note} # I logged out of the Alfresco customer web site. # I Googled on jTDS to find the jTDS JDBC driver and downloaded the jtds-1.2.2-dist.zip file from the website. # Using Windows Explorer, I could just open the jTDS zip file and copy the jtds-1.2.2.jar file. # I then pasted it in the directory c:\bin\alfresco\tomcat\common\lib directory. # I created a c:\data\alf_data directory where the alfresco data will be stored. This is different from the production installation in that the content is stored on a network appliance (\\tornado.shore.mbari.org\alfresco). # I installed a copy of SQL Server 2005 locally to use for the database to back the Alfresco test install. {note} In order to do this without warnings, I had to go back and install IIS through the Add/Remove Programs Control Panel. {note} ## I used the Local System account to run services and only used Windows Authentication logins ## I installed all the service packs and the SQL Server Management Studio product to admin DBs. # In SQL Server, I added the SHORE\DB_Collaboration accounts to the logins. # I created a new database named alfresco-test and made SHORE\DB_Collaboration the owner. # I then went to the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions directory for the customization of the server. ## I edited the custom-repository.properties file ### Changed the dir.root and dir.indexes to look like: {noformat} dir.root=c:/data/alf_data dir.indexes=c:/data/alf_data/lucene-indexes {noformat} ### Commented out the db.* lines for the HSQL Connection (db.driver and db.url) ### Uncommented the db.* lines for MSSQL and changed to use the jTDS driver. They should look like (except the password should be the right one): {noformat} db.driver=net.sourceforge.jtds.jdbc.Driver db.url=jdbc:jtds:sqlserver://localhost/alfresco-test;domain=SHORE;user=DB_Collaboration;password=XXXXXXXXX {noformat} ### I also added the following section to override the mail server settings {noformat} # Mail server configuration mail.host=mail.mbari.org mail.port=25 mail.username= mail.password= {noformat} ## Edited the custom-hibernate-dialect.properties file ### Commented out the HSQL Dialect ### Uncommented the MSSQL Dialect # Now this is not necessarily fun, but in order to really get it configured the way we want it, you need to pull the original .war file out, edit some stuff inside and re-create the .war. {note} This should all be done before starting Alfresco for the first time. {note} # Copy the c:\bin\alfresco\tomcat\webapps\alfresco.war file to your home directory. # Make a second copy so that you will always the original (I copied to alfresco.war.orig and moved it somewhere else. It is important to move it and have only the alfresco.war file in the directory because when you un-jar it, all the files go right where alfresco.war is.) # From a command line, un-jar the war file using: {noformat} jar -xvf alfresco.war {noformat} # This unpacks a lot of files and after it completes, move (or delete) the alfresco.war file from the directory. This needs to be done so it does not end up in the new .war file. # I wanted to change the "Company Home" that seems to be everywhere to something that says MBARI. ## Edited ./WEB-INF/classes/alfresco/messages/webclient.properties and changed company_home from 'Company Home' to 'MBARI Test' ## Edited ./WEB-INF/classes/alfresco/messages/webclient_en_US.properties and changed company_home from 'Company Home' to 'MBARI Test' ## I edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces.properties and changed the first two lines to read {noformat} spaces.company_home.name=MBARI Test spaces.company_home.description=The root of MBARIs Test Alfresco Server {noformat} ## Edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces_en_US.properties and made the same changes as the previous step {tip} This took a bit to find all these, and to be honest, I am not sure which one actually made the change on the GUI, but I suspect it was the _en_US ones. {tip} # When users are imported via LDAP, user spaces get created automatically. In order to put them where I wanted them to go (instead of right in the Company Home), I edited the ./WEB-INF/classes/alfresco/authentication-services-context.xml file. In the file there is a bean with an name of personalHomeFolderProvider. There is a property name 'path' and I added {noformat} /${spaces.user_homes.childname} {noformat} to the end to try to get them to create the user spaces there instead of in the Company Home. The final bean XML looks like: {noformat} /${spaces.company_home.childname}/${spaces.user_homes.childname} ${spaces.store} false All All {noformat} # I wanted to change the logo that is used. I attached the replacement [Alfresco Logo|CLT:Installation Notes^AlfrescoLogo32.png]. Copy this to ./images/logo and overwrite the one that is there. {warning} Note that I did NOT setup SSL for this installation so if I will need to come back and do that if I want truly parallel systems {warning} # Now in order to change the default behavior so that all content is versioned from the start, I edited the .\WEB-INF\classes\alfresco\model\contentModel.xml and searched for the content type definition block. {noformat} Content cm:cmobject true d:content false true false true {noformat} and added the following block right before the ending tag: {noformat} cm:versionable {noformat} so the final block looks like: {noformat} Content cm:cmobject true d:content false true false true cm:versionable {noformat} # That takes care of all the changes to the WAR file. We can now put it back into .war form. # While you are in the directory you expanded the war file in, run ## jar cvfm alfresco.war META-INF\MANIFEST.MF . # You should now have an alfresco.war file in the directory. Move that back to the alfresco install and overwrite the existing one. # Most users like the details view, so I set the default to that by editing c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions\web-client-config-custom.xml and added: {noformat} details 20
20
20 {noformat} right before the closing tag. # Now in order to use MBARI accounts, NTLM authentication was turned on and then chained with the native Alfresco accounts so that we could have non-MBARI accounts on the Alfresco server. ## For simplicity sake, I have attached the files and you can simply download and install them in the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions directory. {note} Before doing these next steps, rename the file-servers-custom.xml file to file-servers-custom.xml.orig so you will have a backup of the original {note} ### First install the [NTLM Configuration XML File|^ntlm-authentication-context.xml] ### Next install the [Authentication Chaining Configuration File|^chaining-authentication-context.xml] ### Next install the file and over-write the existing one. {warning} Make sure you change the tag to reflect a unique name on the network. {warning} # Then in order to setup CIFS on the server, I edited the file-servers-custom.xml file to look like the attached [file-servers-custom.xml|^file-servers-custom.xml] file. # In order to grant certain accounts admin privs, I created a new custom-authority-services-context.xml in the same directory as the ldap-authentication-context.xml file and added {noformat} kgomes admin administrator {noformat} # In order for Alfresco to handle all port 80 traffic, I changed Tomcat so that it takes port 80 and SSL goes over port 443. So I edited the c:\Alfresco\tomcat\conf\server.xml file and changed the 8080 port to 80 and the 8443 port to 443 (the 443 change is done in two places).]]> 3114035 816 ... mbari MBARI Repository http://oceana.shore.mbari.org/maven2 ... ... {code} h3. Including a Dependency from the Repository Once the MBARI repository is included in you build, you can browse the repository to see what projects are available (just go to [http://oceana.shore.mbari.org/maven2]). {code:xml} ... ... qt4j qt4j 1.0-SNAPSHOT ... ... {code} h2. Using the MBARI repository from an [Ant|http://ant.apache.org] project ]]> 819 815 ... mbari MBARI Repository http://oceana.shore.mbari.org/maven2 ... ... {code} h3. Including a Dependency from the Repository Once the MBARI repository is included in you build, you can browse the repository to see what projects are available (just go to [http://oceana.shore.mbari.org/maven2]). {code:xml} ... ... qt4j qt4j 1.0-SNAPSHOT ... ... {code} h2. Using the MBARI repository from an [Ant|http://ant.apache.org] project ]]> 818 3179465 'Downloads'>'2.1 Releases'>'2.1.1' # I changed to the 'Details View', made 40 items visible, and then downloaded 'alfresco-enterprise-tomcat-2.1.1.zip' file. # I then unzipped the downloaded file to c:\bin which created an alfresco-enterprise-tomcat-2.1.1 folder in c:\bin.]]> 3113980 11829815 11797062 3179461 'Downloads'>'2.1 Releases'>'2.1.1' # I changed to the 'Details View', made 40 items visible, and then downloaded 'alfresco-enterprise-tomcat-2.1.1.zip' file.]]> 3113976 3179459 'Downloads'>'2.1 Releases'>'2.1.1']]> 3113974 10389181 10356469 3179474 'Downloads'>'2.1 Releases'>'2.1.1' # I changed to the 'Details View', made 40 items visible, and then downloaded 'alfresco-enterprise-tomcat-2.1.1.zip' file. # I then unzipped the downloaded file to c:\bin which created an alfresco-enterprise-tomcat-2.1.1 folder in c:\bin. # I then went back to the web browser and went to 'Company Home'>'Downloads'>'2.1 Releases'>'2.1.1'>'License Files' # I am not sure if I can do this with our agreement, but I downloaded the 'enterprise-network-customer-unlimited.lic' file. {note} I did get approval from Joe Van De Graaff at Alfresco to use the license for a test installation to get us through this issue. {note} # I logged out of the Alfresco customer web site. # I Googled on jTDS to find the jTDS JDBC driver and downloaded the jtds-1.2.2-dist.zip file from the website. # Using Windows Explorer, I could just open the jTDS zip file and copy the jtds-1.2.2.jar file. # I then pasted it in the directory c:\bin\alfresco-enterprise-tomcat-2.1.1\tomcat\common\lib directory.]]> 3113989 10389179 10356467 3179472 'Downloads'>'2.1 Releases'>'2.1.1' # I changed to the 'Details View', made 40 items visible, and then downloaded 'alfresco-enterprise-tomcat-2.1.1.zip' file. # I then unzipped the downloaded file to c:\bin which created an alfresco-enterprise-tomcat-2.1.1 folder in c:\bin. # I then went back to the web browser and went to 'Company Home'>'Downloads'>'2.1 Releases'>'2.1.1'>'License Files' # I am not sure if I can do this with our agreement, but I downloaded the 'enterprise-network-customer-unlimited.lic' file. {note} I did get approval from Joe Van De Graaff at Alfresco to use the license for a test installation to get us through this issue. {note}]]> 3113987 10389185 10356473 10389186 10356474 3179470 'Downloads'>'2.1 Releases'>'2.1.1' # I changed to the 'Details View', made 40 items visible, and then downloaded 'alfresco-enterprise-tomcat-2.1.1.zip' file. # I then unzipped the downloaded file to c:\bin which created an alfresco-enterprise-tomcat-2.1.1 folder in c:\bin. # I then went back to the web browser and went to 'Company Home'>'Downloads'>'2.1 Releases'>'2.1.1'>'License Files' # I am not sure if I can do this with our agreement, but I downloaded the 'enterprise-network-customer-unlimited.lic' file.]]> 3113985 3179467 'Downloads'>'2.1 Releases'>'2.1.1' # I changed to the 'Details View', made 40 items visible, and then downloaded 'alfresco-enterprise-tomcat-2.1.1.zip' file. # I then unzipped the downloaded file to c:\bin which created an alfresco-enterprise-tomcat-2.1.1 folder in c:\bin. # I then went back to the web browser and went to 'Company Home'>'Downloads'>'2.1 Releases'>'2.1.1'>'License Files' # I am not sure if I can do this with our agreement, but I downloaded the 'enterprise-network-customer-unlimited.lic' file.]]> 3113982 11829820 11797067 10389184 10356472 3179468 3113983 3179489 'Downloads'>'2.1 Releases'>'2.1.1' # I changed to the 'Details View', made 40 items visible, and then downloaded 'alfresco-enterprise-tomcat-2.1.1.zip' file. # I then unzipped the downloaded file to c:\bin which created an alfresco-enterprise-tomcat-2.1.1 folder in c:\bin. # I then went back to the web browser and went to 'Company Home'>'Downloads'>'2.1 Releases'>'2.1.1'>'License Files' # I am not sure if I can do this with our agreement, but I downloaded the 'enterprise-network-customer-unlimited.lic' file. {note} I did get approval from Joe Van De Graaff at Alfresco to use the license for a test installation to get us through this issue. {note} # I logged out of the Alfresco customer web site. # I Googled on jTDS to find the jTDS JDBC driver and downloaded the jtds-1.2.2-dist.zip file from the website. # Using Windows Explorer, I could just open the jTDS zip file and copy the jtds-1.2.2.jar file. # I then pasted it in the directory c:\bin\alfresco-enterprise-tomcat-2.1.1\tomcat\common\lib directory. # I created a c:\data\alf_data directory where the alfresco data will be stored. This is different from the production installation in that the content is stored on a network appliance (\\tornado.shore.mbari.org\alfresco). # I installed a copy of SQL Server 2005 locally to use for the database to back the Alfresco test install. {note} In order to do this without warnings, I had to go back and install IIS through the Add/Remove Programs Control Panel {note} ## I used the Local System account to run services and used my NT account password for the sa account on the SQL Server]]> 3114004 3179488 'Downloads'>'2.1 Releases'>'2.1.1' # I changed to the 'Details View', made 40 items visible, and then downloaded 'alfresco-enterprise-tomcat-2.1.1.zip' file. # I then unzipped the downloaded file to c:\bin which created an alfresco-enterprise-tomcat-2.1.1 folder in c:\bin. # I then went back to the web browser and went to 'Company Home'>'Downloads'>'2.1 Releases'>'2.1.1'>'License Files' # I am not sure if I can do this with our agreement, but I downloaded the 'enterprise-network-customer-unlimited.lic' file. {note} I did get approval from Joe Van De Graaff at Alfresco to use the license for a test installation to get us through this issue. {note} # I logged out of the Alfresco customer web site. # I Googled on jTDS to find the jTDS JDBC driver and downloaded the jtds-1.2.2-dist.zip file from the website. # Using Windows Explorer, I could just open the jTDS zip file and copy the jtds-1.2.2.jar file. # I then pasted it in the directory c:\bin\alfresco-enterprise-tomcat-2.1.1\tomcat\common\lib directory. # I created a c:\data\alf_data directory where the alfresco data will be stored. This is different from the production installation in that the content is stored on a network appliance (\\tornado.shore.mbari.org\alfresco). # I installed a copy of SQL Server 2005 locally to use for the database to back the Alfresco test install. {note} In order to do this without warnings, I had to go back and install IIS through the Add/Remove Programs Control Panel {note}]]> 3114003 3179486 'Downloads'>'2.1 Releases'>'2.1.1' # I changed to the 'Details View', made 40 items visible, and then downloaded 'alfresco-enterprise-tomcat-2.1.1.zip' file. # I then unzipped the downloaded file to c:\bin which created an alfresco-enterprise-tomcat-2.1.1 folder in c:\bin. # I then went back to the web browser and went to 'Company Home'>'Downloads'>'2.1 Releases'>'2.1.1'>'License Files' # I am not sure if I can do this with our agreement, but I downloaded the 'enterprise-network-customer-unlimited.lic' file. {note} I did get approval from Joe Van De Graaff at Alfresco to use the license for a test installation to get us through this issue. {note} # I logged out of the Alfresco customer web site. # I Googled on jTDS to find the jTDS JDBC driver and downloaded the jtds-1.2.2-dist.zip file from the website. # Using Windows Explorer, I could just open the jTDS zip file and copy the jtds-1.2.2.jar file. # I then pasted it in the directory c:\bin\alfresco-enterprise-tomcat-2.1.1\tomcat\common\lib directory. # I created a c:\data\alf_data directory where the alfresco data will be stored. This is different from the production installation in that the content is stored on a network appliance (\\tornado.shore.mbari.org\alfresco). # I installed a copy of SQL Server 2005 locally to use for the database to back the Alfresco test install.]]> 3114001 3179484 'Downloads'>'2.1 Releases'>'2.1.1' # I changed to the 'Details View', made 40 items visible, and then downloaded 'alfresco-enterprise-tomcat-2.1.1.zip' file. # I then unzipped the downloaded file to c:\bin which created an alfresco-enterprise-tomcat-2.1.1 folder in c:\bin. # I then went back to the web browser and went to 'Company Home'>'Downloads'>'2.1 Releases'>'2.1.1'>'License Files' # I am not sure if I can do this with our agreement, but I downloaded the 'enterprise-network-customer-unlimited.lic' file. {note} I did get approval from Joe Van De Graaff at Alfresco to use the license for a test installation to get us through this issue. {note} # I logged out of the Alfresco customer web site. # I Googled on jTDS to find the jTDS JDBC driver and downloaded the jtds-1.2.2-dist.zip file from the website. # Using Windows Explorer, I could just open the jTDS zip file and copy the jtds-1.2.2.jar file. # I then pasted it in the directory c:\bin\alfresco-enterprise-tomcat-2.1.1\tomcat\common\lib directory. # I created a c:\data\alf_data directory where the alfresco data will be stored. This is different from the production installation in that the content is stored on a network appliance (\\tornado.shore.mbari.org\alfresco).]]> 3113999 15664102 15631352 15664101 15631351 8945857 8913096 8945855 8913094 8945854 8913093 8945853 8913092 8945852 8913091 8945849 8913088 15664075 Add/Remove Software) # In the Search tab, enter erlang and select the 14B version of erlang. It will then install a bunch of dependencies (which is a good thing). # Go to the rabbitmq download page and grab the [RHEL version of the RPM|http://www.rabbitmq.com/releases/rabbitmq-server/v2.3.1/rabbitmq-server-2.3.1-1.noarch.rpm] # Use RPM or yum localinstall to install the rabbitmq RPM. # Once it is installed, it can be started using: {noformat} /sbin/service rabbitmq-server start {noformat} # It can be setup to start as a service by using: {noformat} chkconfig rabbitmq-server on {noformat} h5. Management Plugins # If you want the web management console, download the .ez files from the [plugins page|http://www.rabbitmq.com/plugins.html] and install them in the /usr/lib/rabbitmq/lib/rabbitmq_server-2.3.1/plugins and restart the server. {note:Plugins are picky} I found that while the core Rabbit server was somewhat immune to the version of Erlang, the plugins were not. {note} h5. LDAP Authentication # I was able to configure the RabbitMQ server to use our internal LDAP system in a chained configuration with the internal RabbitMQ authentication system. This allows you to use your MBARI logins on the RabbitMQ server. {note:title=One VERY icky caveat} Due to the way we have our Active Directory configured on site, the user DN's are in the form of *Lastname, Firstname*. While it works, that makes users have to login with a username like {noformat} Gomes\\, Kevin {noformat} It is ugly and hopefully we can address this in our Active Directory in the future. That said, the LDAP integration works well. {note} # Download the [ldap-auth plugin|http://www.rabbitmq.com/releases/plugins/v2.3.1/rabbitmq-auth-backend-ldap-2.3.1.ez] and put in the /usr/lib/rabbitmq/lib/rabbitmq_server-2.1.1/plugins directory. # Create (or add configuration) the /etc/rabbitmq/rabbitmq.config file with the following: {noformat} [ {rabbit, [ {auth_backends, [rabbit_auth_backend_ldap, rabbit_auth_backend_internal]} ] }, {rabbit_auth_backend_ldap, [ {servers, ["ldap.shore.mbari.org"]}, {user_dn_pattern, ["CN=${username},OU=Users,OU=AllUsers,DC=shore,DC=mbari,DC=org"]} ] } ]. {noformat} # Restart the server # With the LDAP authentication working, you can now control access permissions on resources (vhosts, exchanges, bindings, queues). See the following for more details: ## [RabbitMQ LDAP Authentication README|http://hg.rabbitmq.com/rabbitmq-auth-backend-ldap/file/default/README] ## [RabbitMQ LDAP Authorization README|http://hg.rabbitmq.com/rabbitmq-auth-backend-ldap/file/default/README-authorisation]]]> 15631325 15664077 Add/Remove Software) # In the Search tab, enter erlang and select the 14B version of erlang. It will then install a bunch of dependencies (which is a good thing). # Go to the rabbitmq download page and grab the [RHEL version of the RPM|http://www.rabbitmq.com/releases/rabbitmq-server/v2.3.1/rabbitmq-server-2.3.1-1.noarch.rpm] # Use RPM or yum localinstall to install the rabbitmq RPM. # Once it is installed, it can be started using: {noformat} /sbin/service rabbitmq-server start {noformat} # It can be setup to start as a service by using: {noformat} chkconfig rabbitmq-server on {noformat} h5. Management Plugins # If you want the web management console, download the .ez files from the [plugins page|http://www.rabbitmq.com/plugins.html] and install them in the /usr/lib/rabbitmq/lib/rabbitmq_server-2.3.1/plugins and restart the server. {note:Plugins are picky} I found that while the core Rabbit server was somewhat immune to the version of Erlang, the plugins were not. {note} h5. LDAP Authentication # I was able to configure the RabbitMQ server to use our internal LDAP system in a chained configuration with the internal RabbitMQ authentication system. This allows you to use your MBARI logins on the RabbitMQ server. {note:title=One VERY icky caveat} Due to the way we have our Active Directory configured on site, the user DN's are in the form of *Lastname, Firstname*. While it works, that makes users have to login with a username like {noformat} Gomes\\, Kevin {noformat} It is ugly and hopefully we can address this in our Active Directory in the future. That said, the LDAP integration works well. {note} # Download the [ldap-auth plugin|http://www.rabbitmq.com/releases/plugins/v2.3.1/rabbitmq-auth-backend-ldap-2.3.1.ez] and put in the /usr/lib/rabbitmq/lib/rabbitmq_server-3.2.1/plugins directory. # Create (or add configuration) the /etc/rabbitmq/rabbitmq.config file with the following: {noformat} [ {rabbit, [ {auth_backends, [rabbit_auth_backend_ldap, rabbit_auth_backend_internal]} ] }, {rabbit_auth_backend_ldap, [ {servers, ["ldap.shore.mbari.org"]}, {user_dn_pattern, ["CN=${username},OU=Users,OU=AllUsers,DC=shore,DC=mbari,DC=org"]} ] } ]. {noformat} # Restart the server # With the LDAP authentication working, you can now control access permissions on resources (vhosts, exchanges, bindings, queues). See the following for more details: ## [RabbitMQ LDAP Authentication README|http://hg.rabbitmq.com/rabbitmq-auth-backend-ldap/file/default/README] ## [RabbitMQ LDAP Authorization README|http://hg.rabbitmq.com/rabbitmq-auth-backend-ldap/file/default/README-authorisation]]]> 15631327 15664068 Add/Remove Software) # In the Search tab, enter erlang and select the 14B version of erlang. It will then install a bunch of dependencies (which is a good thing). # Go to the rabbitmq download page and grab the [RHEL version of the RPM|http://www.rabbitmq.com/releases/rabbitmq-server/v2.3.0/rabbitmq-server-2.3.0-1.noarch.rpm] # Use RPM or yum localinstall to install the rabbitmq RPM. # Once it is installed, it can be started using: {noformat} /sbin/service rabbitmq-server start {noformat} # It can be setup to start as a service by using: {noformat} chkconfig rabbitmq-server on {noformat} # If you want the web management console, download the .ez files from the [plugins page|http://www.rabbitmq.com/plugins.html] and install them in the /usr/lib/rabbitmq/lib/rabbitmq_server-2.3.0/plugins and restart the server. {note:Plugins are picky} I found that while the core Rabbit server was somewhat immune to the version of Erlang, the plugins were not. {note}]]> 15631318 15664070 Add/Remove Software) # In the Search tab, enter erlang and select the 14B version of erlang. It will then install a bunch of dependencies (which is a good thing). # Go to the rabbitmq download page and grab the [RHEL version of the RPM|http://www.rabbitmq.com/releases/rabbitmq-server/v2.3.1/rabbitmq-server-2.3.1-1.noarch.rpm] # Use RPM or yum localinstall to install the rabbitmq RPM. # Once it is installed, it can be started using: {noformat} /sbin/service rabbitmq-server start {noformat} # It can be setup to start as a service by using: {noformat} chkconfig rabbitmq-server on {noformat} h5. Management Plugins # If you want the web management console, download the .ez files from the [plugins page|http://www.rabbitmq.com/plugins.html] and install them in the /usr/lib/rabbitmq/lib/rabbitmq_server-2.3.1/plugins and restart the server. {note:Plugins are picky} I found that while the core Rabbit server was somewhat immune to the version of Erlang, the plugins were not. {note} h5. LDAP Authentication # I was able to configure the RabbitMQ server to use our internal LDAP system in a chained configuration with the internal RabbitMQ authentication system. This allows you to use your MBARI logins on the RabbitMQ server. {note:title=One VERY icky caveat} Due to the way we have our Active Directory configured on site, the user DN's are in the form of *Lastname, Firstname*. While it works, that makes users have to login with a username like *Gomes\\, Kevin*. It is ugly and hopefully we can address this in Active Directory in the future. {note} # Download the [ldap-auth plugin|http://www.rabbitmq.com/releases/plugins/v2.3.1/rabbitmq-auth-backend-ldap-2.3.1.ez]]]> 15631320 15664072 Add/Remove Software) # In the Search tab, enter erlang and select the 14B version of erlang. It will then install a bunch of dependencies (which is a good thing). # Go to the rabbitmq download page and grab the [RHEL version of the RPM|http://www.rabbitmq.com/releases/rabbitmq-server/v2.3.1/rabbitmq-server-2.3.1-1.noarch.rpm] # Use RPM or yum localinstall to install the rabbitmq RPM. # Once it is installed, it can be started using: {noformat} /sbin/service rabbitmq-server start {noformat} # It can be setup to start as a service by using: {noformat} chkconfig rabbitmq-server on {noformat} h5. Management Plugins # If you want the web management console, download the .ez files from the [plugins page|http://www.rabbitmq.com/plugins.html] and install them in the /usr/lib/rabbitmq/lib/rabbitmq_server-2.3.1/plugins and restart the server. {note:Plugins are picky} I found that while the core Rabbit server was somewhat immune to the version of Erlang, the plugins were not. {note} h5. LDAP Authentication # I was able to configure the RabbitMQ server to use our internal LDAP system in a chained configuration with the internal RabbitMQ authentication system. This allows you to use your MBARI logins on the RabbitMQ server. {note:title=One VERY icky caveat} Due to the way we have our Active Directory configured on site, the user DN's are in the form of *Lastname, Firstname*. While it works, that makes users have to login with a username like *Gomes\\, Kevin*. It is ugly and hopefully we can address this in Active Directory in the future. {note} # Download the [ldap-auth plugin|http://www.rabbitmq.com/releases/plugins/v2.3.1/rabbitmq-auth-backend-ldap-2.3.1.ez] and put in the /usr/lib/rabbitmq/lib/rabbitmq_server-2.1.1/plugins directory. # Create (or add configuration) the /etc/rabbitmq/rabbitmq.config file with the following: {noformat} [ {rabbit, [ {auth_backends, [rabbit_auth_backend_ldap, rabbit_auth_backend_internal]} ] }, {rabbit_auth_backend_ldap, [ {servers, ["ldap.shore.mbari.org"]}, {user_dn_pattern, ["CN=${username},OU=Users,OU=AllUsers,DC=shore,DC=mbari,DC=org"]} ] } ]. {noformat}]]> 15631322 15664074 Add/Remove Software) # In the Search tab, enter erlang and select the 14B version of erlang. It will then install a bunch of dependencies (which is a good thing). # Go to the rabbitmq download page and grab the [RHEL version of the RPM|http://www.rabbitmq.com/releases/rabbitmq-server/v2.3.1/rabbitmq-server-2.3.1-1.noarch.rpm] # Use RPM or yum localinstall to install the rabbitmq RPM. # Once it is installed, it can be started using: {noformat} /sbin/service rabbitmq-server start {noformat} # It can be setup to start as a service by using: {noformat} chkconfig rabbitmq-server on {noformat} h5. Management Plugins # If you want the web management console, download the .ez files from the [plugins page|http://www.rabbitmq.com/plugins.html] and install them in the /usr/lib/rabbitmq/lib/rabbitmq_server-2.3.1/plugins and restart the server. {note:Plugins are picky} I found that while the core Rabbit server was somewhat immune to the version of Erlang, the plugins were not. {note} h5. LDAP Authentication # I was able to configure the RabbitMQ server to use our internal LDAP system in a chained configuration with the internal RabbitMQ authentication system. This allows you to use your MBARI logins on the RabbitMQ server. {note:title=One VERY icky caveat} Due to the way we have our Active Directory configured on site, the user DN's are in the form of *Lastname, Firstname*. While it works, that makes users have to login with a username like *Gomes\\, Kevin*. It is ugly and hopefully we can address this in Active Directory in the future. {note} # Download the [ldap-auth plugin|http://www.rabbitmq.com/releases/plugins/v2.3.1/rabbitmq-auth-backend-ldap-2.3.1.ez] and put in the /usr/lib/rabbitmq/lib/rabbitmq_server-2.1.1/plugins directory. # Create (or add configuration) the /etc/rabbitmq/rabbitmq.config file with the following: {noformat} [ {rabbit, [ {auth_backends, [rabbit_auth_backend_ldap, rabbit_auth_backend_internal]} ] }, {rabbit_auth_backend_ldap, [ {servers, ["ldap.shore.mbari.org"]}, {user_dn_pattern, ["CN=${username},OU=Users,OU=AllUsers,DC=shore,DC=mbari,DC=org"]} ] } ]. {noformat} # Restart the server # With the LDAP authentication working, you can now control access permissions on resources (vhosts, exchanges, bindings, queues). See the following for more details: ## [RabbitMQ LDAP Authentication README|http://hg.rabbitmq.com/rabbitmq-auth-backend-ldap/file/default/README] ## [RabbitMQ LDAP Authorization README|http://hg.rabbitmq.com/rabbitmq-auth-backend-ldap/file/default/README-authorisation]]]> 15631324 15664091 15631341 15664098 15631348 15664049 Add/Remove Software) # In the Search tab, enter erlang and select the 14B version of erlang. It will then install a bunch of dependencies (which is a good thing). # Go to the rabbitmq download page and grab the [RHEL version of the RPM|http://www.rabbitmq.com/releases/rabbitmq-server/v2.3.0/rabbitmq-server-2.3.0-1.noarch.rpm] # Use RPM or yum localinstall to install the rabbitmq RPM. # Once it is installed, it can be started using: {noformat} /sbin/service rabbitmq-server start {noformat} # It can be setup to start as a service by using: {noformat} chkconfig rabbitmq-server on {noformat} # If you want the web management console, download the .ez files from the [plugins page|http://www.rabbitmq.com/plugins.html] and install them in the /usr/lib/rabbitmq/lib/rabbitmq_server-2.3.0/plugins and restart the server. {note:Plugins are picky} I found that while the core Rabbit server was somewhat immune to the version of Erlang, the plugins were not. {note}]]> 15631299 15664048 15631298 15664046 15631296 15664044 15631294 10389012 10356296 15664042 15631292 10389011 D0 52.08 52.08 \+0 \+0.00 D0->D1 104.17 104.17 \+0 \+0.00 D1->D2 156.25 156.25 \+0 \+0.00 D2->D3 208.33 208.33 \+0 \+0.00 D3->D4 260.42 260.42 \+0 \+0.00 D4->D5 312.50 312.50 \+0 \+0.00 D5->D6 364.58 364.58 \+0 \+0.00 D6->D7 416.67 416.67 \+0 \+0.00 D7->stopbit 468.75 468.75 \+0 \+0.00 end of stopb 520.83 520.83 \+0 \+0.00 \*/ UBR00=0xC0; UBR10=0x00; UMCTL0=0x00; /\* uart0 3686400Hz 19200bps \*/ UBR01=0xC0; UBR11=0x00; UMCTL1=0x00; /\* uart1 3686400Hz 19200bps \*/ h4. The simplest way to use the USART in UART mode is this: interrupt is not enabled, the software checks if it can output the next byte (UTXIFG = 1), and if a new character has been received (URXIFG = 1). \\ h4. Modbus Register Map * REG_INPUT_START         512         // input registers start at 512 * REG_INPUT_NREGS         8           // 8x16 bit registers * REG_SOLENOIDS_A        0            // Holding registers start at 0 (16 coils for each A and B) * REG_SOLENOIDS_B        1   * REG_HOLDING_START    0           // to match WAGO * REG_HOLDING_NREGS   40         // 40 is more than actual (2) * REG_COILS_START         0           // read individual coils (was 1000) * REG_COILS_SIZE           32          // 32 coils * REG_DISC_START          0           // discrete (was 1000) * REG_DISC_SIZE             32          // 32 coils \\ h3. ---- MODBUS * Commands ** Read Input Register (0x04) ** Read Holding Registers (0x03) ** Write Single Register (0x06) ** Write Multiple Registers (0x10) ** Read/Write Multiple Registers (0x17) ** Read Coils (0x01) ** Write Single Coil (0x05) ** Write Multiple Coils (0x0F) ** Read Discrete Inputs (0x02) ** Report Slave ID (0x11)   * Address * Slave ID  * Berlios ModBus Stack ** The modbus stack is config'd in {color:#0000ff}mbconfig.h{color} which is located in vpc\modbus\include \\ \\ ---- h3. Debugging MSP430 h4. Starting gdbproxy The next step is starting gdbproxy, which is responsible for the communication between GDB and the FET: msp430-gdbproxy \--port=2000 msp430 If your FET is properly connected to the parallel port, you should see a message like the following: info: msp430: Target device is a 'MSP430F12x' (type 11) notice: msp430-gdbproxy: waiting on TCP port 2000 h4. Using Insight (Windows) After you have started Insight (c:\msp430\bin\msp430-gdb.exe), click on "File->Open" and select the elf-file (e.g. "test.elf") you want to debug. Now click on "Run->Connect to target" and enter the following settings: Target: "Remote/TCP" Hostname: "localhost" Port: "2000" Set breakpoint at 'main': yes Set breakpoint at 'exit': yes Attach to target: yes Download Program: yes Command after attaching: "monitor erase all" Run Method: Continue from last Stop When you click on "Ok" Insight should tell you that the connection was successful, and gdbproxy should say "notice: msp430-gdbproxy: connected". To start the debugging click on "Run" or simply press "r". If everything worked correctly you should now see the sourcecode of your program with the first line of main() marked green. The red point is the breakpoint that has been set by Insight automatically. You can set or remove breakpoints by clicking on the '-' in front of the line. Now you can 'c'ontinue the execution to the next breakpoint, 's'tep through the code, or step a single assembler instruction... but be careful with "finish": Insight sometimes seems to lock up with this command. So if you want to finish a function, I recommend setting a breakpoint to the end of the function and using "continue". \\ h2. Installing the Compiler Tool Chain To obtain and install the compiler: # Go to the MSPGCC download page and obtain the latest MSPGCC installation. I used the 'mspgcc-20040723.exe' download which installed everything I needed for a Win32 setup. \\ # This step need only be performed if you wish to use the graphical version of GDB. The latest MSPGCC download only includes the command line GDB debugger. I prefer to use the graphical version called Insight. A slightly older prebuilt version of Insight can be used. Install this older version of insight into a different directory to that chosen for the latest MSPGCC installation as you don't want to overwrite the files obtained in step 1. \\ You should now have two installations. The latest version of MSPGCC installed during step 1, and a slightly older version of Insight from step 2. Both versions of the GDB debugger are called msp430-gdb.exe so one needs to be renamed. Locate the older version msp430-gdb.exe from the files installed during this step and rename it msp430-insight.exe. \\ # Ensure the BIN directory from the files installed during step 1 and the BIN directory from the files installed during step 2 are included in your PATH environment variable. \\ \\ # The MSPGCC download includes a program called msp430-gdbproxy.exe. This intercepts the GDB TCP commands and redirects them to the parallel port. Start msp430-gdbproxy (a shortcut to this will have been placed on the start menu when MSPGCC was installed). By default msp430-gdbproxy uses port 3333 - do not change this. \\ # Program the flash as per the instruction in the section above. The flash can be programmed from within GDB but it is much faster to do it separately and beforehand. \\ # Start the debugger using the command ... msp430-insight a.out... the commands in the gdb.ini file will do the rest. If you prefer to use the command line debugger simply replace msp430-insight with msp430-gdb. \\ # Insight will start at and the program will stop at the breakpoint in main() as shown below. \\ MSP430 Clocking \\ MSP430 Basic Clock Module * Clock Signals: ** *ACLK*: Auxiliary clock. The signal is sourced from LFXT1CLK with a divider of 1, 2, 4, or 8. (The calibration program for the serial link sets the divider to 4, but after the calibration it can be changed to any other values.) ACLK can be used as the clock signal for Timer A and Timer B. ** *MCLK*: Master clock. The signal can be sourced from LFXT1CLK, XT2CLK (if available), or DCOCLK with a divider of 1, 2, 4, or 8. MCLK is used by the CPU and system. ** *SMCLK*: Sub-main clock. The signal is sourced from either XT2CLK (if available), or DCOCLK with a divider of 1, 2, 4, or 8. SMCLK can be used as the clock signal for Timer A and Timer B. * MSP430 Clocking pictorial: *   * \\ !MSP430_clocking2.JPG!                  !MSP430_BCSCTL1.JPG! !MSP430_BCSCTL2.JPG!\\ \\]]> 10356295 10389014 10356298 15664040 15631290 10389013 10356297 10389016 10356300 15664038 Add/Remove Software) # In the Search tab, enter erlang and select the default erlang and install it. # Once it finishes, search for rabbitmq-server and install that. {note} wget ... sudo gpg --import ....asc sudo yum localinstall rabb....rpm {note} {noformat} Start the Server The server is not started as a daemon by default when the RabbitMQ server package is installed. To start the daemon by default when the system boots, as an administrator run chkconfig rabbitmq-server on. As an administrator, start and stop the server as usual using /sbin/service rabbitmq-server stop/start/etc. Note: The server is set up to run as system user rabbitmq. If you change the location of the Mnesia database or the logs, you must ensure the files are owned by this user (and also update the environment variables). {noformat} # Had to build plugins from source for version reasons # sudo yum install mercurial # sudo yum install git # sudo yum install pyhton-simplejson # cd to a location and type 'hg clone -r rabbitmq_v2_1_1 http://hg.rabbitmq.com/rabbitmq-public-umbrella # cd rabbitmq-public-umbrella # make co ]]> 15631288 10389015 10356299 10389003 10356287 10389004 10356288 10389005 10356289 10389006 BOOT PICO * CF2> BOOT APP for deployment * RMC message for A or V (Tracking or DR - tells wether GPS is tracking) \\ * First Tasks * 1) Add to Prompt GPS OK, RGPS Age OK, AGC OK, Platform Track OK (ask once every 4sec to avoid swamping the Seatel) * 2) Create NMEA style string on Spare2 hooked to 24 port terminal server for continuous stream of updates to be displayed by a GUI * 3) Implement 'Hunting Algorithm' if pointing command is sent N times (config parm). * \\ \\ \\ \\ Seatel SEA TEL MODEl TAC-92 USER INTERFACE DESCRIPTI0N VERSION 1.61 1.0 COMMAND SUMMARY | CONTROL CODES: | FUNCTION | | | 6 | Azimuth CW one step (system step reselution) | | 4 | Azimuth CCW one step | | 8 | Elevation up one step | | 2 | Elevation DOWN one step | | Aaaaa{} | Move AZ to aaa.a deg , true or magnetic | | Baaaa{} | Set ships heading to aaa.a degrees | | C | Step Track ON | | D | Step Track and Tracking OFF | | cnnnn{} | Set MHz/CHA tuning to nnnn MHz | | dnnnn{} | Set KHz/CHB tuning to nnnn KHz | | Eeeee{} | Move EL to ee.e or eee.e degrees | | F | Toggle auto unwrap ON/OFF | | gnnn {} | Set polang position to nnn | | Jrrrr{} | Move azimuth to ship relative position | | Nnnn{ } | Set number of signal strength updates (1-255) | | Onnn{ } | Output data to EME equipment | | R | start spiral search fot satellite | | S | Advance AGC input selectien (Ext, ChA, ChB, IF) | | Taaaa{} | Move to satellite at aaa.a degrees | | U | Force cable unwrap | | W | Write parameters to NV RAM | | Xnnn{} | Set azimuth step track size to nnn steps (1-255) | | Ynnn{} | Set elevation step track size to nnn steps (0-255) | | Z | Toggle C/Ku step size selection | | esc | Cancel pending numeric command | | $mmmmm{} | NMEA Latitude / Longitude input (GPGLL format) | | MONITOR CODES | FUNCTION | TAC RESPONSE | | H | Relative Az,Ship Heading | RrrrrHaaaa,CR,LF,> | | M | Tracking Parameters | Xnnn Ynnn Nnnn cc,CR,LF,> | | P | Az/EL Position | EeeeeAaaaa,CR,LF,> | | s | TaC Status | Snn,CR,LF1> | | V | Software Version | TAC-92 VER N,NN,CR,LF, > | | q | Tuning >Frequencies , Input | Qnnnn nnnn s,CR,LF,> | | u | Polang position | Gnnn ,CR,LF,> | | % | Signal Strength | Lnnnn,CR,LF,> | | & | Error Status | &nnn ,CR,LF,> | | ABBREVIATIONS: | | eeee = | Elevation angle oooo to 0900 nominal 0000 to 3599 range | | aaaa = | True/Magnetic Azimuth 0000 to 3599 range | | rrrr = | Relative azimuth 0950 to 6250 1ange | | nnnn = | A5CII decimal number 0000-9999 | | nnn = | ASCII decima\[ number 0 to 255 | | nn = | System Status twO bitmaped ASCII characters | | cc = | C /Ku tracking parameter bank selection | | s = | AGC receiver selection 0,l,2,3 | | {} = | Carriage return | April 30, 1996 Doc No. 112862-D \\ \\]]> 10356290 10389007 10356291 15664061 15631311 10389008 10356292 10389009   Debian 4.0, Base Mem=512M, Dynamic sizeable harddisk 8.0 GB host key is right ctrl\\ h1. Editors h3.  TextPad [http://textpad.com /]; TextPad has about 80% to 90% of what slickedit has and you can have it today. \\ To register your copy of TextPad: 1. Select all the lines including "BEGIN LICENSE" and "END LICENSE",     and copy them to the clipboard using Ctrl+C. 2. Start TextPad, and choose the "Enter License Code" command from the     Help menu. 3. Paste the license information into the dialog box, using Ctrl+V. 4. Click OK. If you have purchased a multiple user site license, you must repeat this step on each client PC, but it is not necessary to do it for each user name on a PC. Please e-mail sales@textpad.com, if you have any difficulties. If you do not already have a copy of Textpad 4.5 you can download this from . BEGIN LICENSE Monteray Bay Aquarium Research Institute Site License 01 0005 RS2D-XDNU-GUA4-CZCZ 411aedde 61b2d8be 2a3ea037 54a6535c d80ec02a b3c15935 1509f1d0 08ce95b0 1894c13a 1e29cf6a 24734d92 719e8b90 cd840c5a 87d40e02 5ec866c3 5040e210 30cf0e05 3f14a534 835694bb aee4bdb2 4b63c5d8 61226c94 1eb4a1a2 757fb2b1 END LICENSE]]> 10356293 15664059 15631309 10389010 10356294 10388995 10356277 15664057 15631307 10388996 10356278 15664056 15631306 10388999 10356282 15664053 Add/Remove Software) # In the Search tab, enter erlang and select the 14B version of erlang. It will then install a bunch of dependencies (which is a good thing). # Go to the rabbitmq download page and grab the [RHEL version of the RPM|http://www.rabbitmq.com/releases/rabbitmq-server/v2.3.0/rabbitmq-server-2.3.0-1.noarch.rpm] # Use RPM or yum localinstall to install the rabbitmq RPM. # Once it is installed, it can be started using: {noformat} /sbin/service rabbitmq-server start {noformat} # It can be setup to start as a service by using: {noformat} chkconfig rabbitmq-server on {noformat} # If you want the web management console, download the .ez files from the [plugins page|http://www.rabbitmq.com/plugins.html] and install them in the /usr/lib/rabbitmq/lib/rabbitmq_server-2.3.0/plugins and restart the server. {note:Plugins are picky} I found that while the core Rabbit server was somewhat immune to the version of Erlang, the plugins were not. {note}]]> 15631303 10389001 10356285 18645044 "Downloads">"2.1 Releases">"2.1.1" # I then clicked on alfresco-enterprise-tomcat-2.1.1.zip to download the zip file. # Went to [http://customers.alfresco.com] (I was still logged in) # Went to "Company Home">"Downloads">"2.1 Releases">"2.1.1">"License Files" # I went ahead and downloaded all the "*.lic" files, but I think I only need enterprise-network-customer-unlimited.lic" # Logged out of Alfresco. # Since I suspect I will need a JDBC driver for SQLServer, I downloaded the jTDS-1.2.2 driver from the jtds web site (just Google jtds and go to the download section of the top google return). # I closed the Firefox browser. # I extracted the jtds-1.2.2.jar file from the jtds download # I downloaded and installed the JRockit 6 R27.4 JDK Microsoft Windows (x86 - 32 bit) from BEA's web site {note} After installing JRockit, make sure you set the JAVA_HOME environment variable to point to the installation of JRockit. For example, I went to the desktop, right clicked on the computer, did Properties, then clicked on the Advanced tab, then click on the environment variables button and then created a new system variable named JAVA_HOME and set to c:\bin\Java\jrockit-R27.4.0-jdk1.6.0_02 {note} # I ran the installer, changed the "Program Files" to "bin" in the installation directory for both the JDK and the JRE. I also chose to install the JRE as public. # Using Firefox, I downloaded the PHP 5.2.5 Windows Installer from php.net and installed it. Although I installed it, I did not integrate it with a web server as I want Alfresco to take port 80. I probably did not need to install PHP, but I thought I would anyway. (again, I changed install path from "Program Files" to "bin" # I also downloaded and installed OpenOffice and ran it once so I could get through the initial startup # I setup a Alfresco database on the server Solstice and granted the LAGOON\DB_Collaboration account to be the db_owner of the Alfresco database. # I unzipped the alfresco tomcat zip file to an alfresco directory in c:\bin # I then went to the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions directory for the customization of the server. ## I edited the custom-repository.properties file ### Changed the dir.root and dir.indexes to look like: {noformat} dir.root=//tornado.shore.mbari.org/Alfresco/alf_data dir.indexes=d:/alf_data/lucene-indexes {noformat} ### Commented out the db.* lines for the HSQL Connection (db.driver and db.url) ### Uncommented the db.* lines for MSSQL and changed to use the jTDS driver. They should look like: {noformat} db.driver=net.sourceforge.jtds.jdbc.Driver db.url=jdbc:jtds:sqlserver://solstice.shore.mbari.org/Alfresco;domain=SHORE;user=DB_Collaboration;password=XXXXXXXXX {noformat} ### I also added the following section to override the mail server settings {noformat} # Mail server configuration mail.host=mail.mbari.org mail.port=25 mail.username= mail.password= {noformat} ## Edited the custom-hibernate-dialect.properties file ### Commented out the HSQL Dialect ### Uncommented the MSSQL Dialect # I then installed the jtds-1.2.2.jar in the c:\bin\alfresco\tomcat\common\lib so that it will be on the classpath when Alfresco is started # Now this is not necessarily fun, but in order to really get it configured the way we want it, you need to pull the original .war file out, edit some stuff inside and re-create the .war. {note} This should all be done before starting Alfresco for the first time. {note} # Copy the c:\Alfresco\tomcat\webapps\alfresco.war file to your home directory. # Make a second copy so that you will always the original (I copied to alfresco.war.orig and moved it somewhere else. It is important to move it and have only the alfresco.war file in the directory because when you un-jar it, all the files go right where alfresco.war is.) # From a command line, un-jar the war file using: {noformat} jar -xvf alfresco.war {noformat} # This unpacks a lot of files and after it completes, move (or delete) the alfresco.war file from the directory. This needs to be done so it does not end up in the new .war file. # I wanted to change the "Company Home" that seems to be everywhere to something that says MBARI. ## Edited ./WEB-INF/classes/alfresco/messages/webclient.properties and changed company_home from 'Company Home' to 'MBARI' ## Edited ./WEB-INF/classes/alfresco/messages/webclient_en_US.properties and changed company_home from 'Company Home' to 'MBARI' ## I edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces.properties and changed the first two lines to read {noformat} spaces.company_home.name=MBARI spaces.company_home.description=The root space for MBARI {noformat} ## Edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces_en_US.properties and made the same changes as the previous step {tip} This took a bit to find all these, and to be honest, I am not sure which one actually made the change on the GUI, but I suspect it was the _en_US ones. {tip} # When users are imported via LDAP, user spaces get created automatically. In order to put them where I wanted them to go (instead of right in the Company Home), I edited the ./WEB-INF/classes/alfresco/authentication-services-context.xml file. In the file there is a bean with an name of personalHomeFolderProvider. There is a property name 'path' and I added {noformat} /${spaces.user_homes.childname} {noformat} to the end to try to get them to create the user spaces there instead of in the Company Home. The final bean XML looks like: {noformat} /${spaces.company_home.childname}/${spaces.user_homes.childname} ${spaces.store} false All All {noformat} # I wanted to change the logo that is used. I attached the replacement logo [CLT:here|^AlfrescoLogo32.png]. Copy this to ./images/logo and overwrite the one that is there. # In order to setup SSL for the application (will do that later), edit ./WEB-INF/web.xml and add the following {noformat} Login Pages /* CONFIDENTIAL {noformat} right before the ending tag at the bottom of the file. # Now in order to change the default behavior so that all content is versioned from the start, I edited the .\WEB-INF\classes\alfresco\model\contentModel.xml and searched for the content type definition block. {noformat} Content cm:cmobject true d:content false true false true {noformat} and added the following block right before the ending tag: {noformat} cm:versionable {noformat} so the final block looks like: {noformat} Content cm:cmobject true d:content false true false true cm:versionable {noformat} # Lastly, I wanted to redirect the log files to a separate disk. This is done because in the Windows hardening process, most of the disk space ends up on drive D: where alfresco does not live. The log files quickly fill up the small C: drive. To to this, I edited the .\WEB-INF\classes\log4j.properties and changed the log file appender location to point to a directory that was created on the D: drive called D:/alf_logs. # That takes care of all the changes to the WAR file. We can now put it back into .war form. # While you are in the directory you expanded the war file in, run ## jar cvfm alfresco.war META-INF\MANIFEST.MF . # You should now have an alfresco.war file in the directory. Move that back to the alfresco install and overwrite the existing one. # Most users like the details view, so I set the default to that by editing c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions\web-client-config-custom.xml and added: {noformat} details 20
20
20 {noformat} right before the closing tag. # Now in order to use MBARI accounts, NTLM authentication was turned on and then chained with the native Alfresco accounts so that we could have non-MBARI accounts on the Alfresco server. ## In order to enable NTLM and native Alfresco authentication, I had to edit two files. For simplicity I have just attached them here and they can be downloaded and installed in the extensions directory. ### The first file is the [CLT:ntlm-authentication-context.xml|^ntlm-authentication-context.xml] file. This configures and enables NTLM authentication. ### The next file was the [CLT:chaining-authentication-context.xml|^chaining-authentication-context.xml] file which enabled Alfresco authentication and chained it together with the NTLM authentication from the previous file. # Then in order to setup CIFS on the server, I edited the file-servers-custom.xml file to look like the attached [CLT:file-servers-custom.xml|^file-servers-custom.xml] file. # In order to grant certain accounts admin privs, I created a new custom-authority-services-context.xml in the same directory as the ldap-authentication-context.xml file and added {noformat} kgomes admin administrator {noformat} # In order for Alfresco to handle all port 80 traffic, I changed Tomcat so that it takes port 80 and SSL goes over port 443. So I edited the c:\Alfresco\tomcat\conf\server.xml file and changed the 8080 port to 80 and the 8443 port to 443 (the 443 change is done in two places). # Now I needed to setup the SSL for the web traffic. Cathy Sewell was instrumental in getting this working. She ordered a new certificate specifically for alfresco and put it in the c:\local\cert folder. Here are the instructions for what she did to get the certficate installed. {noformat} SSL certificate for server Alfresco - 1/2/08 C:\bin\Java\jrockit-R27.1.0-jre1.6.0_02\bin>keytool -genkey -alias tomcat -keyalg RSA -keystore tomcat.keystore What is your first and last name? [alfresco.mbari.org]: What is the name of your organizational unit? [IS]: What is the name of your organization? [MBARI]: What is the name of your City or Locality? [Moss Landing]: What is the name of your State or Province? [CD]: CA What is the two-letter country code for this unit? [US]: Is CN=alfresco.mbari.org, OU=IS, O=MBARI, L=Moss Landing, ST=CA, C=US correct? [no]: y Enter key password for (RETURN if same as keystore password): C:\bin\Java\jrockit-R27.4.0-jre1.6.0_02\bin>keytool -certreq -keyalg RSA -alias tomcat -file certreq.csr -keystore tomcat.keystore Enter keystore password: Generated certificate request file, certreq.csr, was submitted to SSL provider. Certificate provider sent certificate file (alfresco.mbari.org.crt), along with gd_bundle.crt, gd_cross_intermediate.crt, and gd_intermediate.crt. Additionally, I downloaded valicert_class2_root.cer from their website. These files were stored in c:\local\cert. The following commands were used to add them to the tomcat keystore: C:\bin\Java\jrockit-R27.4.0-jre1.6.0_02\bin>keytool -import -alias root -keystore tomcat.keystore -trustcacerts -file c:\local\cert\valicert_class2_root.cer Enter keystore password: Certificate already exists in system-wide CA keystore under alias Do you still want to add it to your own keystore? [no]: y Certificate was added to keystore C:\bin\Java\jrockit-R27.4.0-jre1.6.0_02\bin>keytool -import -alias cross -keystore tomcat.keystore -trustcacerts -file c:\local\cert\gd_cross_intermediate.crt Enter keystore password: Certificate was added to keystore C:\bin\Java\jrockit-R27.4.0-jre1.6.0_02\bin>keytool -import -alias intermed -keystore tomcat.keystore -trustcacerts -file c:\local\cert\gd_intermediate.crt Enter keystore password: Certificate was added to keystore C:\bin\Java\jrockit-R27.4.0-jre1.6.0_02\bin>keytool -import -alias tomcat -keystore tomcat.keystore -trustcacerts -file c:\local\cert\alfresco.mbari.org.crt Enter keystore password: Certificate reply was installed in keystore {noformat} # I edited the c:\bin\alfresco\tomcat\conf\server.xml file and uncommented the SSL section and edited to look like that shown below. {noformat} {noformat} # Since I was in the server.xml file, I went ahead and changed it so that the default webapp was alfresco so that you would get alfresco anytime you went to the base URL. I did this by adding: {noformat} {noformat} as the last line of the tag section (right before the closing tag). {note} You will also notice the Valve tag that I had to add to turn off proxy cache disabling so that IE clients would work correctly over SSL. Gotta love M$. {note} # I copied the enterprise-network-unlimited.lic file into the c:\Alfresco\tomcat\shared\classes\alfresco\extensions\license directory # Just to keep things clean, I edited the c:\bin\alfresco\alfresco.bat file and put 'rem' in front of the second JAVA_OPTS set as I am using Java 6. # Now after you run it for the first time and the database structure gets created, you can't restart it because you get: {noformat} java.sql.SQLException: Column names in each table must be unique. Column name 'ID_' in table 'JBPM_ACTION' is specified more than once. {noformat} Sigh, so in order to keep Alfresco from hurting itself, I had to turn off the schema updates. This is done by editing the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions\custom-repository.properties and adding the following: {noformat} db.schema.update=false {noformat} and then restarting alfresco. # To install Alfresco as a Windows Service use a command prompt and enter the following: {noformat} cd c:\bin\alfresco\tomcat\bin service.bat install alfresco tomcat5.exe //US//alfresco --DisplayName "Alfresco Server" tomcat5.exe //US//alfresco --JvmMs=512 --JvmMx=1024 --JvmSs=64 tomcat5.exe //US//alfresco --JavaHome=c:/bin/Java/jrockit-R27.4.0-jdk1.6.0_02 tomcat5.exe //US//alfresco --Environment ALF_HOME=c:/bin/alfresco/ tomcat5.exe //US//alfresco --Environment PATH=c:/bin/alfresco/bin;%PATH% tomcat5.exe //US//alfresco --StartPath c:/bin/alfresco --Startup auto {noformat} # To uninstall the service, at a later time, do the following: {noformat} cd c:\bin\alfresco\tomcat\bin service.bat uninstall alfresco {noformat} # To edit your service settings at any time: {noformat} cd c:\alfresco\tomcat\bin tomcat5w.exe //ES//alfresco {noformat} {warning} These next couple of steps had to be taken to install a patch from Alfresco for an issue with bulk uploads I was having. Essentially when file and path structures get really long and nasty, Alfresco was throwing an error and bailing out. This patch (two Java classes) fixed that issue. {warning} # Next, I downloaded the attached [CLT:JAR|^act2139.jar] file and copied it to the c:\bin\alfresco\tomcat\webapps\alfresco\WEB-INF\classes directory. # I shutdown Alfresco and then unjarred the file to install the new classes. They are: ## org/alfresco/filesys/smb/server/SMBSrvPacket.class ## org/alfresco/filesys/util/DataBuffer.class # I would assume since they do not overwrite anything, that this location is further up in the class loader and so it will load these new classes first. # I deleted the act2139.jar file and the META-INF directory that the unjarring process created. # In order to install certain modules (like the email listener), I had to get the Alfresco Module Manager from the customers.alfresco.com download site. I downloaded the alfresco-mmt-2.1.1.jar file locally so I could use it to install modules. # I then downloaded the email listener module from [http://forge.alfresco.com/projects/email-listener/]. It came as a zip file, so I unzipped it and it created a folder with the appropriate emailListener.amp in it. # Make another backup copy of the alfresco.war file and put somewhere in case you want to roll this back. # Open a command prompt windows and cd to the location where the Alfresco Module Manager jar is. # Run the following: {noformat} java -jar alfresco-mmt-2.1.1.jar path_to_emailListener.amp path_to_alfresco.war {noformat} So for me this looked like: {noformat} java -jar alfresco-mmt-2.1.1.jar .\email-listener_2.1RC2\emailListener.amp c:\bin\alfresco\tomcat\webapps\alfresco.war {noformat} # You should be able to verify the install by running: {noformat} java -jar alfresco-mmt-2.1.1.jar list c:\bin\alfresco\tomcat\webapps\alfresco.war {noformat} and you should see something like: {noformat} Module 'emailListener' installed in 'c:\bin\alfresco\tomcat\webapps\alfresco.war' - Title: EmailListener - Version: 2.1 - Install Date: Fri Dec 07 08:43:10 PST 2007 - Desription: EmailListener Module {noformat} # Finally, to start the service, just go into your Windows Service control panel and locate the service that is now named 'Alfresco Server'. You can start and stop Alfresco from this control panel. {note:title=Database Migrations} For the alfresco.mbari.org installation, we moved the back end database a couple of times for performance and management reasons. The first move was to backup the database from solstice.shore.mbari.org to the SQL 2005 server called capricorn. We did this because 2005 was the officially supported DB and we were experiencing some strange issues. It ran fine on capricorn for a long while, but for licensing reasons, we wanted to consolidate the DB onto a newer SQL Server 2008 machine called equinox.shore.mbari.org. {note} h1. Content Migration Now, in order to migrate content from old alfresco and normal file structures, I did the following: h3. For content already in alfresco: # Navigate to the space whose contents you want to migrate. For example, let's say I want to migrate the stuff from my personal space. I would navigate (using the WebUI) to the /MBARI/User Homes/kgomes space. You should see the contents of the kgomes folder from this view. # Click on 'More actions->View Details'. # On the right hand side, click on 'Export'. # For package name, I usually enter the space name followed by '_export', but it doesn't really matter. # Click on the link that says 'Click here to select the destination' and select somewhere that you will be able to download the .acp file from. # Select 'Current Space'. # Select 'Include Children'. # Uncheck 'Include this space' unless you have content (documents) in this specific folder (anything other than folders) that you want to migrate. This is a bit tricky, but there are two ways to do this. If you want to have the top level folder created, use the 'Include this space' and that will create the top level folder. Otherwise, if will expand into the folder in which you import the .acp file into. This is important in cases where the folder has already been created for you (like with user homes) and you have to migrate content into that folder. If you have the option to create the top level directory, by all means do so. # Uncheck 'Export in background' so you can force it to happen and you know when it is complete.]]> 18579513 18645045 "Downloads">"2.1 Releases">"2.1.1" # I then clicked on alfresco-enterprise-tomcat-2.1.1.zip to download the zip file. # Went to [http://customers.alfresco.com] (I was still logged in) # Went to "Company Home">"Downloads">"2.1 Releases">"2.1.1">"License Files" # I went ahead and downloaded all the "*.lic" files, but I think I only need enterprise-network-customer-unlimited.lic" # Logged out of Alfresco. # Since I suspect I will need a JDBC driver for SQLServer, I downloaded the jTDS-1.2.2 driver from the jtds web site (just Google jtds and go to the download section of the top google return). # I closed the Firefox browser. # I extracted the jtds-1.2.2.jar file from the jtds download # I downloaded and installed the JRockit 6 R27.4 JDK Microsoft Windows (x86 - 32 bit) from BEA's web site {note} After installing JRockit, make sure you set the JAVA_HOME environment variable to point to the installation of JRockit. For example, I went to the desktop, right clicked on the computer, did Properties, then clicked on the Advanced tab, then click on the environment variables button and then created a new system variable named JAVA_HOME and set to c:\bin\Java\jrockit-R27.4.0-jdk1.6.0_02 {note} # I ran the installer, changed the "Program Files" to "bin" in the installation directory for both the JDK and the JRE. I also chose to install the JRE as public. # Using Firefox, I downloaded the PHP 5.2.5 Windows Installer from php.net and installed it. Although I installed it, I did not integrate it with a web server as I want Alfresco to take port 80. I probably did not need to install PHP, but I thought I would anyway. (again, I changed install path from "Program Files" to "bin" # I also downloaded and installed OpenOffice and ran it once so I could get through the initial startup # I setup a Alfresco database on the server Solstice and granted the LAGOON\DB_Collaboration account to be the db_owner of the Alfresco database. # I unzipped the alfresco tomcat zip file to an alfresco directory in c:\bin # I then went to the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions directory for the customization of the server. ## I edited the custom-repository.properties file ### Changed the dir.root and dir.indexes to look like: {noformat} dir.root=//tornado.shore.mbari.org/Alfresco/alf_data dir.indexes=d:/alf_data/lucene-indexes {noformat} ### Commented out the db.* lines for the HSQL Connection (db.driver and db.url) ### Uncommented the db.* lines for MSSQL and changed to use the jTDS driver. They should look like: {noformat} db.driver=net.sourceforge.jtds.jdbc.Driver db.url=jdbc:jtds:sqlserver://solstice.shore.mbari.org/Alfresco;domain=SHORE;user=DB_Collaboration;password=XXXXXXXXX {noformat} ### I also added the following section to override the mail server settings {noformat} # Mail server configuration mail.host=mail.mbari.org mail.port=25 mail.username= mail.password= {noformat} ## Edited the custom-hibernate-dialect.properties file ### Commented out the HSQL Dialect ### Uncommented the MSSQL Dialect # I then installed the jtds-1.2.2.jar in the c:\bin\alfresco\tomcat\common\lib so that it will be on the classpath when Alfresco is started # Now this is not necessarily fun, but in order to really get it configured the way we want it, you need to pull the original .war file out, edit some stuff inside and re-create the .war. {note} This should all be done before starting Alfresco for the first time. {note} # Copy the c:\Alfresco\tomcat\webapps\alfresco.war file to your home directory. # Make a second copy so that you will always the original (I copied to alfresco.war.orig and moved it somewhere else. It is important to move it and have only the alfresco.war file in the directory because when you un-jar it, all the files go right where alfresco.war is.) # From a command line, un-jar the war file using: {noformat} jar -xvf alfresco.war {noformat} # This unpacks a lot of files and after it completes, move (or delete) the alfresco.war file from the directory. This needs to be done so it does not end up in the new .war file. # I wanted to change the "Company Home" that seems to be everywhere to something that says MBARI. ## Edited ./WEB-INF/classes/alfresco/messages/webclient.properties and changed company_home from 'Company Home' to 'MBARI' ## Edited ./WEB-INF/classes/alfresco/messages/webclient_en_US.properties and changed company_home from 'Company Home' to 'MBARI' ## I edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces.properties and changed the first two lines to read {noformat} spaces.company_home.name=MBARI spaces.company_home.description=The root space for MBARI {noformat} ## Edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces_en_US.properties and made the same changes as the previous step {tip} This took a bit to find all these, and to be honest, I am not sure which one actually made the change on the GUI, but I suspect it was the _en_US ones. {tip} # When users are imported via LDAP, user spaces get created automatically. In order to put them where I wanted them to go (instead of right in the Company Home), I edited the ./WEB-INF/classes/alfresco/authentication-services-context.xml file. In the file there is a bean with an name of personalHomeFolderProvider. There is a property name 'path' and I added {noformat} /${spaces.user_homes.childname} {noformat} to the end to try to get them to create the user spaces there instead of in the Company Home. The final bean XML looks like: {noformat} /${spaces.company_home.childname}/${spaces.user_homes.childname} ${spaces.store} false All All {noformat} # I wanted to change the logo that is used. I attached the replacement logo [CLT:here|^AlfrescoLogo32.png]. Copy this to ./images/logo and overwrite the one that is there. # In order to setup SSL for the application (will do that later), edit ./WEB-INF/web.xml and add the following {noformat} Login Pages /* CONFIDENTIAL {noformat} right before the ending tag at the bottom of the file. # Now in order to change the default behavior so that all content is versioned from the start, I edited the .\WEB-INF\classes\alfresco\model\contentModel.xml and searched for the content type definition block. {noformat} Content cm:cmobject true d:content false true false true {noformat} and added the following block right before the ending tag: {noformat} cm:versionable {noformat} so the final block looks like: {noformat} Content cm:cmobject true d:content false true false true cm:versionable {noformat} # Lastly, I wanted to redirect the log files to a separate disk. This is done because in the Windows hardening process, most of the disk space ends up on drive D: where alfresco does not live. The log files quickly fill up the small C: drive. To to this, I edited the .\WEB-INF\classes\log4j.properties and changed the log file appender location to point to a directory that was created on the D: drive called D:/alf_logs. # That takes care of all the changes to the WAR file. We can now put it back into .war form. # While you are in the directory you expanded the war file in, run ## jar cvfm alfresco.war META-INF\MANIFEST.MF . # You should now have an alfresco.war file in the directory. Move that back to the alfresco install and overwrite the existing one. # Most users like the details view, so I set the default to that by editing c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions\web-client-config-custom.xml and added: {noformat} details 20
20
20 {noformat} right before the closing tag. # Now in order to use MBARI accounts, NTLM authentication was turned on and then chained with the native Alfresco accounts so that we could have non-MBARI accounts on the Alfresco server. ## In order to enable NTLM and native Alfresco authentication, I had to edit two files. For simplicity I have just attached them here and they can be downloaded and installed in the extensions directory. ### The first file is the [CLT:ntlm-authentication-context.xml|^ntlm-authentication-context.xml] file. This configures and enables NTLM authentication. ### The next file was the [CLT:chaining-authentication-context.xml|^chaining-authentication-context.xml] file which enabled Alfresco authentication and chained it together with the NTLM authentication from the previous file. # Then in order to setup CIFS on the server, I edited the file-servers-custom.xml file to look like the attached [CLT:file-servers-custom.xml|^file-servers-custom.xml] file. # In order to grant certain accounts admin privs, I created a new custom-authority-services-context.xml in the same directory as the ldap-authentication-context.xml file and added {noformat} kgomes admin administrator {noformat} # In order for Alfresco to handle all port 80 traffic, I changed Tomcat so that it takes port 80 and SSL goes over port 443. So I edited the c:\Alfresco\tomcat\conf\server.xml file and changed the 8080 port to 80 and the 8443 port to 443 (the 443 change is done in two places). # Now I needed to setup the SSL for the web traffic. Cathy Sewell was instrumental in getting this working. She ordered a new certificate specifically for alfresco and put it in the c:\local\cert folder. Here are the instructions for what she did to get the certficate installed. {noformat} SSL certificate for server Alfresco - 1/2/08 C:\bin\Java\jrockit-R27.1.0-jre1.6.0_02\bin>keytool -genkey -alias tomcat -keyalg RSA -keystore tomcat.keystore What is your first and last name? [alfresco.mbari.org]: What is the name of your organizational unit? [IS]: What is the name of your organization? [MBARI]: What is the name of your City or Locality? [Moss Landing]: What is the name of your State or Province? [CD]: CA What is the two-letter country code for this unit? [US]: Is CN=alfresco.mbari.org, OU=IS, O=MBARI, L=Moss Landing, ST=CA, C=US correct? [no]: y Enter key password for (RETURN if same as keystore password): C:\bin\Java\jrockit-R27.4.0-jre1.6.0_02\bin>keytool -certreq -keyalg RSA -alias tomcat -file certreq.csr -keystore tomcat.keystore Enter keystore password: Generated certificate request file, certreq.csr, was submitted to SSL provider. Certificate provider sent certificate file (alfresco.mbari.org.crt), along with gd_bundle.crt, gd_cross_intermediate.crt, and gd_intermediate.crt. Additionally, I downloaded valicert_class2_root.cer from their website. These files were stored in c:\local\cert. The following commands were used to add them to the tomcat keystore: C:\bin\Java\jrockit-R27.4.0-jre1.6.0_02\bin>keytool -import -alias root -keystore tomcat.keystore -trustcacerts -file c:\local\cert\valicert_class2_root.cer Enter keystore password: Certificate already exists in system-wide CA keystore under alias Do you still want to add it to your own keystore? [no]: y Certificate was added to keystore C:\bin\Java\jrockit-R27.4.0-jre1.6.0_02\bin>keytool -import -alias cross -keystore tomcat.keystore -trustcacerts -file c:\local\cert\gd_cross_intermediate.crt Enter keystore password: Certificate was added to keystore C:\bin\Java\jrockit-R27.4.0-jre1.6.0_02\bin>keytool -import -alias intermed -keystore tomcat.keystore -trustcacerts -file c:\local\cert\gd_intermediate.crt Enter keystore password: Certificate was added to keystore C:\bin\Java\jrockit-R27.4.0-jre1.6.0_02\bin>keytool -import -alias tomcat -keystore tomcat.keystore -trustcacerts -file c:\local\cert\alfresco.mbari.org.crt Enter keystore password: Certificate reply was installed in keystore {noformat} # I edited the c:\bin\alfresco\tomcat\conf\server.xml file and uncommented the SSL section and edited to look like that shown below. {noformat} {noformat} # Since I was in the server.xml file, I went ahead and changed it so that the default webapp was alfresco so that you would get alfresco anytime you went to the base URL. I did this by adding: {noformat} {noformat} as the last line of the tag section (right before the closing tag). {note} You will also notice the Valve tag that I had to add to turn off proxy cache disabling so that IE clients would work correctly over SSL. Gotta love M$. {note} # I copied the enterprise-network-unlimited.lic file into the c:\Alfresco\tomcat\shared\classes\alfresco\extensions\license directory # Just to keep things clean, I edited the c:\bin\alfresco\alfresco.bat file and put 'rem' in front of the second JAVA_OPTS set as I am using Java 6. # Now after you run it for the first time and the database structure gets created, you can't restart it because you get: {noformat} java.sql.SQLException: Column names in each table must be unique. Column name 'ID_' in table 'JBPM_ACTION' is specified more than once. {noformat} Sigh, so in order to keep Alfresco from hurting itself, I had to turn off the schema updates. This is done by editing the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions\custom-repository.properties and adding the following: {noformat} db.schema.update=false {noformat} and then restarting alfresco. # To install Alfresco as a Windows Service use a command prompt and enter the following: {noformat} cd c:\bin\alfresco\tomcat\bin service.bat install alfresco tomcat5.exe //US//alfresco --DisplayName "Alfresco Server" tomcat5.exe //US//alfresco --JvmMs=512 --JvmMx=1024 --JvmSs=64 tomcat5.exe //US//alfresco --JavaHome=c:/bin/Java/jrockit-R27.4.0-jdk1.6.0_02 tomcat5.exe //US//alfresco --Environment ALF_HOME=c:/bin/alfresco/ tomcat5.exe //US//alfresco --Environment PATH=c:/bin/alfresco/bin;%PATH% tomcat5.exe //US//alfresco --StartPath c:/bin/alfresco --Startup auto {noformat} # To uninstall the service, at a later time, do the following: {noformat} cd c:\bin\alfresco\tomcat\bin service.bat uninstall alfresco {noformat} # To edit your service settings at any time: {noformat} cd c:\alfresco\tomcat\bin tomcat5w.exe //ES//alfresco {noformat} {warning} These next couple of steps had to be taken to install a patch from Alfresco for an issue with bulk uploads I was having. Essentially when file and path structures get really long and nasty, Alfresco was throwing an error and bailing out. This patch (two Java classes) fixed that issue. {warning} # Next, I downloaded the attached [CLT:JAR|^act2139.jar] file and copied it to the c:\bin\alfresco\tomcat\webapps\alfresco\WEB-INF\classes directory. # I shutdown Alfresco and then unjarred the file to install the new classes. They are: ## org/alfresco/filesys/smb/server/SMBSrvPacket.class ## org/alfresco/filesys/util/DataBuffer.class # I would assume since they do not overwrite anything, that this location is further up in the class loader and so it will load these new classes first. # I deleted the act2139.jar file and the META-INF directory that the unjarring process created. # In order to install certain modules (like the email listener), I had to get the Alfresco Module Manager from the customers.alfresco.com download site. I downloaded the alfresco-mmt-2.1.1.jar file locally so I could use it to install modules. # I then downloaded the email listener module from [http://forge.alfresco.com/projects/email-listener/]. It came as a zip file, so I unzipped it and it created a folder with the appropriate emailListener.amp in it. # Make another backup copy of the alfresco.war file and put somewhere in case you want to roll this back. # Open a command prompt windows and cd to the location where the Alfresco Module Manager jar is. # Run the following: {noformat} java -jar alfresco-mmt-2.1.1.jar path_to_emailListener.amp path_to_alfresco.war {noformat} So for me this looked like: {noformat} java -jar alfresco-mmt-2.1.1.jar .\email-listener_2.1RC2\emailListener.amp c:\bin\alfresco\tomcat\webapps\alfresco.war {noformat} # You should be able to verify the install by running: {noformat} java -jar alfresco-mmt-2.1.1.jar list c:\bin\alfresco\tomcat\webapps\alfresco.war {noformat} and you should see something like: {noformat} Module 'emailListener' installed in 'c:\bin\alfresco\tomcat\webapps\alfresco.war' - Title: EmailListener - Version: 2.1 - Install Date: Fri Dec 07 08:43:10 PST 2007 - Desription: EmailListener Module {noformat} # Finally, to start the service, just go into your Windows Service control panel and locate the service that is now named 'Alfresco Server'. You can start and stop Alfresco from this control panel. {note:title=Database Migrations} For the alfresco.mbari.org installation, we moved the back end database a couple of times for performance and management reasons. The first move was to backup the database from solstice.shore.mbari.org to the SQL 2005 server called capricorn. We did this because 2005 was the officially supported DB and we were experiencing some strange issues. It ran fine on capricorn for a long while, but for licensing reasons, we wanted to consolidate the DB onto a newer SQL Server 2008 machine called equinox.shore.mbari.org. In order to point Alfresco at a different database, I edited the custom-repository.properties file located in the {noformat}c:\bin\alfresco\tomcat\shared\classes\alfresco\extension{noformat} directory. Here is what the final result looked like with the previous two configurations commented out. I also downloaded the most recent jtds driver (1.2.5) and installed it in the c:\bin\alfresco\tomcat\common\lib directory and removed the old version. {note} h1. Content Migration Now, in order to migrate content from old alfresco and normal file structures, I did the following: h3. For content already in alfresco: # Navigate to the space whose contents you want to migrate. For example, let's say I want to migrate the stuff from my personal space. I would navigate (using the WebUI) to the /MBARI/User Homes/kgomes space. You should see the contents of the kgomes folder from this view. # Click on 'More actions->View Details'. # On the right hand side, click on 'Export'. # For package name, I usually enter the space name followed by '_export', but it doesn't really matter. # Click on the link that says 'Click here to select the destination' and select somewhere that you will be able to download the .acp file from. # Select 'Current Space'. # Select 'Include Children'. # Uncheck 'Include this space' unless you have content (documents) in this specific folder (anything other than folders) that you want to migrate. This is a bit tricky, but there are two ways to do this. If you want to have the top level folder created, use the 'Include this space' and that will create the top level folder. Otherwise, if will expand into the folder in which you import the .acp file into. This is important in cases where the folder has already been created for you (like with user homes) and you have to migrate content into that folder. If you have the option to create the top level directory, by all means do so. # Uncheck 'Export in background' so you can force it to happen and you know when it is complete.]]> 18579514 15664005 Add/Remove Software) # In the Search tab, enter erlang and select the default erlang and install it. # Once it finishes, search for rabbitmq-server and install that. {noformat} Start the Server The server is not started as a daemon by default when the RabbitMQ server package is installed. To start the daemon by default when the system boots, as an administrator run chkconfig rabbitmq-server on. As an administrator, start and stop the server as usual using /sbin/service rabbitmq-server stop/start/etc. Note: The server is set up to run as system user rabbitmq. If you change the location of the Mnesia database or the logs, you must ensure the files are owned by this user (and also update the environment variables). {noformat}]]> 15631255 18645042 "Downloads">"2.1 Releases">"2.1.1" # I then clicked on alfresco-enterprise-tomcat-2.1.1.zip to download the zip file. # Went to [http://customers.alfresco.com] (I was still logged in) # Went to "Company Home">"Downloads">"2.1 Releases">"2.1.1">"License Files" # I went ahead and downloaded all the "*.lic" files, but I think I only need enterprise-network-customer-unlimited.lic" # Logged out of Alfresco. # Since I suspect I will need a JDBC driver for SQLServer, I downloaded the jTDS-1.2.2 driver from the jtds web site (just Google jtds and go to the download section of the top google return). # I closed the Firefox browser. # I extracted the jtds-1.2.2.jar file from the jtds download # I downloaded and installed the JRockit 6 R27.4 JDK Microsoft Windows (x86 - 32 bit) from BEA's web site {note} After installing JRockit, make sure you set the JAVA_HOME environment variable to point to the installation of JRockit. For example, I went to the desktop, right clicked on the computer, did Properties, then clicked on the Advanced tab, then click on the environment variables button and then created a new system variable named JAVA_HOME and set to c:\bin\Java\jrockit-R27.4.0-jdk1.6.0_02 {note} # I ran the installer, changed the "Program Files" to "bin" in the installation directory for both the JDK and the JRE. I also chose to install the JRE as public. # Using Firefox, I downloaded the PHP 5.2.5 Windows Installer from php.net and installed it. Although I installed it, I did not integrate it with a web server as I want Alfresco to take port 80. I probably did not need to install PHP, but I thought I would anyway. (again, I changed install path from "Program Files" to "bin" # I also downloaded and installed OpenOffice and ran it once so I could get through the initial startup # I setup a Alfresco database on the server Solstice and granted the LAGOON\DB_Collaboration account to be the db_owner of the Alfresco database. # I unzipped the alfresco tomcat zip file to an alfresco directory in c:\bin # I then went to the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions directory for the customization of the server. ## I edited the custom-repository.properties file ### Changed the dir.root and dir.indexes to look like: {noformat} dir.root=//tornado.shore.mbari.org/Alfresco/alf_data dir.indexes=d:/alf_data/lucene-indexes {noformat} ### Commented out the db.* lines for the HSQL Connection (db.driver and db.url) ### Uncommented the db.* lines for MSSQL and changed to use the jTDS driver. They should look like: {noformat} db.driver=net.sourceforge.jtds.jdbc.Driver db.url=jdbc:jtds:sqlserver://solstice.shore.mbari.org/Alfresco;domain=SHORE;user=DB_Collaboration;password=XXXXXXXXX {noformat} ### I also added the following section to override the mail server settings {noformat} # Mail server configuration mail.host=mail.mbari.org mail.port=25 mail.username= mail.password= {noformat} ## Edited the custom-hibernate-dialect.properties file ### Commented out the HSQL Dialect ### Uncommented the MSSQL Dialect # I then installed the jtds-1.2.2.jar in the c:\bin\alfresco\tomcat\common\lib so that it will be on the classpath when Alfresco is started # Now this is not necessarily fun, but in order to really get it configured the way we want it, you need to pull the original .war file out, edit some stuff inside and re-create the .war. {note} This should all be done before starting Alfresco for the first time. {note} # Copy the c:\Alfresco\tomcat\webapps\alfresco.war file to your home directory. # Make a second copy so that you will always the original (I copied to alfresco.war.orig and moved it somewhere else. It is important to move it and have only the alfresco.war file in the directory because when you un-jar it, all the files go right where alfresco.war is.) # From a command line, un-jar the war file using: {noformat} jar -xvf alfresco.war {noformat} # This unpacks a lot of files and after it completes, move (or delete) the alfresco.war file from the directory. This needs to be done so it does not end up in the new .war file. # I wanted to change the "Company Home" that seems to be everywhere to something that says MBARI. ## Edited ./WEB-INF/classes/alfresco/messages/webclient.properties and changed company_home from 'Company Home' to 'MBARI' ## Edited ./WEB-INF/classes/alfresco/messages/webclient_en_US.properties and changed company_home from 'Company Home' to 'MBARI' ## I edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces.properties and changed the first two lines to read {noformat} spaces.company_home.name=MBARI spaces.company_home.description=The root space for MBARI {noformat} ## Edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces_en_US.properties and made the same changes as the previous step {tip} This took a bit to find all these, and to be honest, I am not sure which one actually made the change on the GUI, but I suspect it was the _en_US ones. {tip} # When users are imported via LDAP, user spaces get created automatically. In order to put them where I wanted them to go (instead of right in the Company Home), I edited the ./WEB-INF/classes/alfresco/authentication-services-context.xml file. In the file there is a bean with an name of personalHomeFolderProvider. There is a property name 'path' and I added {noformat} /${spaces.user_homes.childname} {noformat} to the end to try to get them to create the user spaces there instead of in the Company Home. The final bean XML looks like: {noformat} /${spaces.company_home.childname}/${spaces.user_homes.childname} ${spaces.store} false All All {noformat} # I wanted to change the logo that is used. I attached the replacement logo [CLT:here|^AlfrescoLogo32.png]. Copy this to ./images/logo and overwrite the one that is there. # In order to setup SSL for the application (will do that later), edit ./WEB-INF/web.xml and add the following {noformat} Login Pages /* CONFIDENTIAL {noformat} right before the ending tag at the bottom of the file. # Now in order to change the default behavior so that all content is versioned from the start, I edited the .\WEB-INF\classes\alfresco\model\contentModel.xml and searched for the content type definition block. {noformat} Content cm:cmobject true d:content false true false true {noformat} and added the following block right before the ending tag: {noformat} cm:versionable {noformat} so the final block looks like: {noformat} Content cm:cmobject true d:content false true false true cm:versionable {noformat} # Lastly, I wanted to redirect the log files to a separate disk. This is done because in the Windows hardening process, most of the disk space ends up on drive D: where alfresco does not live. The log files quickly fill up the small C: drive. To to this, I edited the .\WEB-INF\classes\log4j.properties and changed the log file appender location to point to a directory that was created on the D: drive called D:/alf_logs. # That takes care of all the changes to the WAR file. We can now put it back into .war form. # While you are in the directory you expanded the war file in, run ## jar cvfm alfresco.war META-INF\MANIFEST.MF . # You should now have an alfresco.war file in the directory. Move that back to the alfresco install and overwrite the existing one. # Most users like the details view, so I set the default to that by editing c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions\web-client-config-custom.xml and added: {noformat} details 20
20
20 {noformat} right before the closing tag. # Now in order to use MBARI accounts, NTLM authentication was turned on and then chained with the native Alfresco accounts so that we could have non-MBARI accounts on the Alfresco server. ## In order to enable NTLM and native Alfresco authentication, I had to edit two files. For simplicity I have just attached them here and they can be downloaded and installed in the extensions directory. ### The first file is the [CLT:ntlm-authentication-context.xml|^ntlm-authentication-context.xml] file. This configures and enables NTLM authentication. ### The next file was the [CLT:chaining-authentication-context.xml|^chaining-authentication-context.xml] file which enabled Alfresco authentication and chained it together with the NTLM authentication from the previous file. # Then in order to setup CIFS on the server, I edited the file-servers-custom.xml file to look like the attached [CLT:file-servers-custom.xml|^file-servers-custom.xml] file. # In order to grant certain accounts admin privs, I created a new custom-authority-services-context.xml in the same directory as the ldap-authentication-context.xml file and added {noformat} kgomes admin administrator {noformat} # In order for Alfresco to handle all port 80 traffic, I changed Tomcat so that it takes port 80 and SSL goes over port 443. So I edited the c:\Alfresco\tomcat\conf\server.xml file and changed the 8080 port to 80 and the 8443 port to 443 (the 443 change is done in two places). # Now I needed to setup the SSL for the web traffic. Cathy Sewell was instrumental in getting this working. She ordered a new certificate specifically for alfresco and put it in the c:\local\cert folder. Here are the instructions for what she did to get the certficate installed. {noformat} SSL certificate for server Alfresco - 1/2/08 C:\bin\Java\jrockit-R27.1.0-jre1.6.0_02\bin>keytool -genkey -alias tomcat -keyalg RSA -keystore tomcat.keystore What is your first and last name? [alfresco.mbari.org]: What is the name of your organizational unit? [IS]: What is the name of your organization? [MBARI]: What is the name of your City or Locality? [Moss Landing]: What is the name of your State or Province? [CD]: CA What is the two-letter country code for this unit? [US]: Is CN=alfresco.mbari.org, OU=IS, O=MBARI, L=Moss Landing, ST=CA, C=US correct? [no]: y Enter key password for (RETURN if same as keystore password): C:\bin\Java\jrockit-R27.4.0-jre1.6.0_02\bin>keytool -certreq -keyalg RSA -alias tomcat -file certreq.csr -keystore tomcat.keystore Enter keystore password: Generated certificate request file, certreq.csr, was submitted to SSL provider. Certificate provider sent certificate file (alfresco.mbari.org.crt), along with gd_bundle.crt, gd_cross_intermediate.crt, and gd_intermediate.crt. Additionally, I downloaded valicert_class2_root.cer from their website. These files were stored in c:\local\cert. The following commands were used to add them to the tomcat keystore: C:\bin\Java\jrockit-R27.4.0-jre1.6.0_02\bin>keytool -import -alias root -keystore tomcat.keystore -trustcacerts -file c:\local\cert\valicert_class2_root.cer Enter keystore password: Certificate already exists in system-wide CA keystore under alias Do you still want to add it to your own keystore? [no]: y Certificate was added to keystore C:\bin\Java\jrockit-R27.4.0-jre1.6.0_02\bin>keytool -import -alias cross -keystore tomcat.keystore -trustcacerts -file c:\local\cert\gd_cross_intermediate.crt Enter keystore password: Certificate was added to keystore C:\bin\Java\jrockit-R27.4.0-jre1.6.0_02\bin>keytool -import -alias intermed -keystore tomcat.keystore -trustcacerts -file c:\local\cert\gd_intermediate.crt Enter keystore password: Certificate was added to keystore C:\bin\Java\jrockit-R27.4.0-jre1.6.0_02\bin>keytool -import -alias tomcat -keystore tomcat.keystore -trustcacerts -file c:\local\cert\alfresco.mbari.org.crt Enter keystore password: Certificate reply was installed in keystore {noformat} # I edited the c:\bin\alfresco\tomcat\conf\server.xml file and uncommented the SSL section and edited to look like that shown below. {noformat} {noformat} # Since I was in the server.xml file, I went ahead and changed it so that the default webapp was alfresco so that you would get alfresco anytime you went to the base URL. I did this by adding: {noformat} {noformat} as the last line of the tag section (right before the closing tag). {note} You will also notice the Valve tag that I had to add to turn off proxy cache disabling so that IE clients would work correctly over SSL. Gotta love M$. {note} # I copied the enterprise-network-unlimited.lic file into the c:\Alfresco\tomcat\shared\classes\alfresco\extensions\license directory # Just to keep things clean, I edited the c:\bin\alfresco\alfresco.bat file and put 'rem' in front of the second JAVA_OPTS set as I am using Java 6. # Now after you run it for the first time and the database structure gets created, you can't restart it because you get: {noformat} java.sql.SQLException: Column names in each table must be unique. Column name 'ID_' in table 'JBPM_ACTION' is specified more than once. {noformat} Sigh, so in order to keep Alfresco from hurting itself, I had to turn off the schema updates. This is done by editing the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions\custom-repository.properties and adding the following: {noformat} db.schema.update=false {noformat} and then restarting alfresco. # To install Alfresco as a Windows Service use a command prompt and enter the following: {noformat} cd c:\bin\alfresco\tomcat\bin service.bat install alfresco tomcat5.exe //US//alfresco --DisplayName "Alfresco Server" tomcat5.exe //US//alfresco --JvmMs=512 --JvmMx=1024 --JvmSs=64 tomcat5.exe //US//alfresco --JavaHome=c:/bin/Java/jrockit-R27.4.0-jdk1.6.0_02 tomcat5.exe //US//alfresco --Environment ALF_HOME=c:/bin/alfresco/ tomcat5.exe //US//alfresco --Environment PATH=c:/bin/alfresco/bin;%PATH% tomcat5.exe //US//alfresco --StartPath c:/bin/alfresco --Startup auto {noformat} # To uninstall the service, at a later time, do the following: {noformat} cd c:\bin\alfresco\tomcat\bin service.bat uninstall alfresco {noformat} # To edit your service settings at any time: {noformat} cd c:\alfresco\tomcat\bin tomcat5w.exe //ES//alfresco {noformat} {warning} These next couple of steps had to be taken to install a patch from Alfresco for an issue with bulk uploads I was having. Essentially when file and path structures get really long and nasty, Alfresco was throwing an error and bailing out. This patch (two Java classes) fixed that issue. {warning} # Next, I downloaded the attached [CLT:JAR|^act2139.jar] file and copied it to the c:\bin\alfresco\tomcat\webapps\alfresco\WEB-INF\classes directory. # I shutdown Alfresco and then unjarred the file to install the new classes. They are: ## org/alfresco/filesys/smb/server/SMBSrvPacket.class ## org/alfresco/filesys/util/DataBuffer.class # I would assume since they do not overwrite anything, that this location is further up in the class loader and so it will load these new classes first. # I deleted the act2139.jar file and the META-INF directory that the unjarring process created. # In order to install certain modules (like the email listener), I had to get the Alfresco Module Manager from the customers.alfresco.com download site. I downloaded the alfresco-mmt-2.1.1.jar file locally so I could use it to install modules. # I then downloaded the email listener module from [http://forge.alfresco.com/projects/email-listener/]. It came as a zip file, so I unzipped it and it created a folder with the appropriate emailListener.amp in it. # Make another backup copy of the alfresco.war file and put somewhere in case you want to roll this back. # Open a command prompt windows and cd to the location where the Alfresco Module Manager jar is. # Run the following: {noformat} java -jar alfresco-mmt-2.1.1.jar path_to_emailListener.amp path_to_alfresco.war {noformat} So for me this looked like: {noformat} java -jar alfresco-mmt-2.1.1.jar .\email-listener_2.1RC2\emailListener.amp c:\bin\alfresco\tomcat\webapps\alfresco.war {noformat} # You should be able to verify the install by running: {noformat} java -jar alfresco-mmt-2.1.1.jar list c:\bin\alfresco\tomcat\webapps\alfresco.war {noformat} and you should see something like: {noformat} Module 'emailListener' installed in 'c:\bin\alfresco\tomcat\webapps\alfresco.war' - Title: EmailListener - Version: 2.1 - Install Date: Fri Dec 07 08:43:10 PST 2007 - Desription: EmailListener Module {noformat} # Finally, to start the service, just go into your Windows Service control panel and locate the service that is now named 'Alfresco Server'. You can start and stop Alfresco from this control panel. h1. Content Migration Now, in order to migrate content from old alfresco and normal file structures, I did the following: h3. For content already in alfresco: # Navigate to the space whose contents you want to migrate. For example, let's say I want to migrate the stuff from my personal space. I would navigate (using the WebUI) to the /MBARI/User Homes/kgomes space. You should see the contents of the kgomes folder from this view. # Click on 'More actions->View Details'. # On the right hand side, click on 'Export'. # For package name, I usually enter the space name followed by '_export', but it doesn't really matter. # Click on the link that says 'Click here to select the destination' and select somewhere that you will be able to download the .acp file from. # Select 'Current Space'. # Select 'Include Children'. # Uncheck 'Include this space' unless you have content (documents) in this specific folder (anything other than folders) that you want to migrate. This is a bit tricky, but there are two ways to do this. If you want to have the top level folder created, use the 'Include this space' and that will create the top level folder. Otherwise, if will expand into the folder in which you import the .acp file into. This is important in cases where the folder has already been created for you (like with user homes) and you have to migrate content into that folder. If you have the option to create the top level directory, by all means do so. # Uncheck 'Export in background' so you can force it to happen and you know when it is complete.]]> 18579511 9405192 9372462 8945876 8913116 9405198 9372468 15664024 15631274 9405195 9372465 8945878 8913118 9405196 9372466 8945882 8913122 10944986 10912231 10944984 10912229 10944990 10912235 10944988 10912233 10944994 10912239 10944992 10912237 10944978 10912223 2818055 "Downloads">"2.1 Releases">"2.1.1" # I then clicked on alfresco-enterprise-tomcat-2.1.1.zip to download the zip file. # Went to [http://customers.alfresco.com] (I was still logged in) # Went to "Company Home">"Downloads">"2.1 Releases">"2.1.1">"License Files" # I went ahead and downloaded all the "*.lic" files, but I think I only need enterprise-network-customer-unlimited.lic" # Logged out of Alfresco. # Since I suspect I will need a JDBC driver for SQLServer, I downloaded the jTDS-1.2.2 driver from the jtds web site (just Google jtds and go to the download section of the top google return). # I closed the Firefox browser. # I extracted the jtds-1.2.2.jar file from the jtds download # I downloaded and installed the JRockit 6 R27.4 JDK Microsoft Windows (x86 - 32 bit) from BEA's web site {note} After installing JRockit, make sure you set the JAVA_HOME environment variable to point to the installation of JRockit. For example, I went to the desktop, right clicked on the computer, did Properties, then clicked on the Advanced tab, then click on the environment variables button and then created a new system variable named JAVA_HOME and set to c:\bin\Java\jrockit-R27.4.0-jdk1.6.0_02 {note} # I ran the installer, changed the "Program Files" to "bin" in the installation directory for both the JDK and the JRE. I also chose to install the JRE as public. # Using Firefox, I downloaded the PHP 5.2.5 Windows Installer from php.net and installed it. Although I installed it, I did not integrate it with a web server as I want Alfresco to take port 80. I probably did not need to install PHP, but I thought I would anyway. (again, I changed install path from "Program Files" to "bin" # I also downloaded and installed OpenOffice and ran it once so I could get through the initial startup # I setup a Alfresco database on the server Solstice and granted the LAGOON\DB_Collaboration account to be the db_owner of the Alfresco database. # I unzipped the alfresco tomcat zip file to an alfresco directory in c:\bin # I then went to the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions directory for the customization of the server. ## I edited the custom-repository.properties file ### Changed the dir.root and dir.indexes to look like: {noformat} dir.root=//tornado.shore.mbari.org/Alfresco/alf_data dir.indexes=d:/alf_data/lucene-indexes {noformat} ### Commented out the db.* lines for the HSQL Connection (db.driver and db.url) ### Uncommented the db.* lines for MSSQL and changed to use the jTDS driver. They should look like: {noformat} db.driver=net.sourceforge.jtds.jdbc.Driver db.url=jdbc:jtds:sqlserver://solstice.shore.mbari.org/Alfresco;domain=SHORE;user=DB_Collaboration;password=XXXXXXXXX {noformat} ### I also added the following section to override the mail server settings {noformat} # Mail server configuration mail.host=mail.mbari.org mail.port=25 mail.username= mail.password= {noformat} ## Edited the custom-hibernate-dialect.properties file ### Commented out the HSQL Dialect ### Uncommented the MSSQL Dialect # I then installed the jtds-1.2.2.jar in the c:\bin\alfresco\tomcat\common\lib so that it will be on the classpath when Alfresco is started # Now this is not necessarily fun, but in order to really get it configured the way we want it, you need to pull the original .war file out, edit some stuff inside and re-create the .war. {note} This should all be done before starting Alfresco for the first time. {note} # Copy the c:\Alfresco\tomcat\webapps\alfresco.war file to your home directory. # Make a second copy so that you will always the original (I copied to alfresco.war.orig and moved it somewhere else. It is important to move it and have only the alfresco.war file in the directory because when you un-jar it, all the files go right where alfresco.war is.) # From a command line, un-jar the war file using: {noformat} jar -xvf alfresco.war {noformat} # This unpacks a lot of files and after it completes, move (or delete) the alfresco.war file from the directory. This needs to be done so it does not end up in the new .war file. # I wanted to change the "Company Home" that seems to be everywhere to something that says MBARI. ## Edited ./WEB-INF/classes/alfresco/messages/webclient.properties and changed company_home from 'Company Home' to 'MBARI' ## Edited ./WEB-INF/classes/alfresco/messages/webclient_en_US.properties and changed company_home from 'Company Home' to 'MBARI' ## I edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces.properties and changed the first two lines to read {noformat} spaces.company_home.name=MBARI spaces.company_home.description=The root space for MBARI {noformat} ## Edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces_en_US.properties and made the same changes as the previous step {tip} This took a bit to find all these, and to be honest, I am not sure which one actually made the change on the GUI, but I suspect it was the _en_US ones. {tip} # When users are imported via LDAP, user spaces get created automatically. In order to put them where I wanted them to go (instead of right in the Company Home), I edited the ./WEB-INF/classes/alfresco/authentication-services-context.xml file. In the file there is a bean with an name of personalHomeFolderProvider. There is a property name 'path' and I added {noformat} /${spaces.user_homes.childname} {noformat} to the end to try to get them to create the user spaces there instead of in the Company Home. The final bean XML looks like: {noformat} /${spaces.company_home.childname}/${spaces.user_homes.childname} ${spaces.store} false All All {noformat} # I wanted to change the logo that is used. I attached the replacement logo [here|^AlfrescoLogo32.png]. Copy this to ./images/logo and overwrite the one that is there. # In order to setup SSL for the application (will do that later), edit ./WEB-INF/web.xml and add the following {noformat} Login Pages /* CONFIDENTIAL {noformat} right before the ending tag at the bottom of the file. # Now in order to change the default behavior so that all content is versioned from the start, I edited the .\WEB-INF\classes\alfresco\model\contentModel.xml and searched for the content type definition block. {noformat} Content cm:cmobject true d:content false true false true {noformat} and added the following block right before the ending tag: {noformat} cm:versionable {noformat} so the final block looks like: {noformat} Content cm:cmobject true d:content false true false true cm:versionable {noformat} # That takes care of all the changes to the WAR file. We can now put it back into .war form. # While you are in the directory you expanded the war file in, run ## jar cvfm alfresco.war META-INF\MANIFEST.MF . # You should now have an alfresco.war file in the directory. Move that back to the alfresco install and overwrite the existing one. # Most users like the details view, so I set the default to that by editing c:\Alfresco\tomcat\shared\classes\alfresco\extensions/web-client-config-custom.xml and added: {noformat} details 20
20
20 {noformat} right before the closing tag. # Now in order to use MBARI accounts, NTLM authentication was turned on and then chained with the native Alfresco accounts so that we could have non-MBARI accounts on the Alfresco server. ## In order to enable NTLM and native Alfresco authentication, I had to edit two files. For simplicity I have just attached them here and they can be downloaded and installed in the extensions directory. ### The first file is the [ntlm-authentication-context.xml|^ntlm-authentication-context.xml] file. This configures and enables NTLM authentication. ### The next file was the [chaining-authentication-context.xml|^chaining-authentication-context.xml] file which enabled Alfresco authentication and chained it together with the NTLM authentication from the previous file. # Then in order to setup CIFS on the server, I edited the file-servers-custom.xml file to look like the attached [file-servers-custom.xml|^file-servers-custom.xml] file. # In order to grant certain accounts admin privs, I created a new custom-authority-services-context.xml in the same directory as the ldap-authentication-context.xml file and added {noformat} kgomes admin administrator {noformat} # In order for Alfresco to handle all port 80 traffic, I changed Tomcat so that it takes port 80 and SSL goes over port 443. So I edited the c:\Alfresco\tomcat\conf\server.xml file and changed the 8080 port to 80 and the 8443 port to 443 (the 443 change is done in two places). # I copied the enterprise-network-unlimited.lic file into the c:\Alfresco\tomcat\shared\classes\alfresco\extensions\license directory # Just to keep things clean, I edited the c:\bin\alfresco\alfresco.bat file and put 'rem' in front of the second JAVA_OPTS set as I am using Java 6. # Now after you run it for the first time and the database structure gets created, you can't restart it because you get: {noformat} java.sql.SQLException: Column names in each table must be unique. Column name 'ID_' in table 'JBPM_ACTION' is specified more than once. {noformat} Sigh, so in order to keep Alfresco from hurting itself, I had to turn off the schema updates. This is done by editing the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions\custom-repository.properties and adding the following: {noformat} db.schema.update=false {noformat} and then restarting alfresco. # To install Alfresco as a Windows Service use a command prompt and enter the following: {noformat} cd c:\bin\alfresco\tomcat\bin service.bat install alfresco tomcat5.exe //US//alfresco --DisplayName "Alfresco Server" tomcat5.exe //US//alfresco --JvmMs=512 --JvmMx=1024 --JvmSs=64 tomcat5.exe //US//alfresco --JavaHome=c:/bin/Java/jrockit-R27.4.0-jdk1.6.0_02 tomcat5.exe //US//alfresco --Environment ALF_HOME=c:/bin/alfresco/ tomcat5.exe //US//alfresco --Environment PATH=c:/bin/alfresco/bin;%PATH% tomcat5.exe //US//alfresco --StartPath c:/bin/alfresco --Startup auto {noformat} # To uninstall the service, at a later time, do the following: {noformat} cd c:\bin\alfresco\tomcat\bin service.bat uninstall alfresco {noformat} # To edit your service settings at any time: {noformat} cd c:\alfresco\tomcat\bin tomcat5w.exe //ES//alfresco {noformat} # In order to install certain modules (like the email listener), I had to get the Alfresco Module Manager from the customers.alfresco.com download site. I downloaded the alfresco-mmt-2.1.1.jar file locally so I could use it to install modules. # I then downloaded the email listener module from [http://forge.alfresco.com/projects/email-listener/]. It came as a zip file, so I unzipped it and it created a folder with the appropriate emailListener.amp in it. # Make another backup copy of the alfresco.war file and put somewhere in case you want to roll this back. # Open a command prompt windows and cd to the location where the Alfresco Module Manager jar is. # Run the following: {noformat} java -jar alfresco-mmt-2.1.1.jar path_to_emailListener.amp path_to_alfresco.war {noformat} So for me this looked like: {noformat} java -jar alfresco-mmt-2.1.1.jar .\email-listener_2.1RC2\emailListener.amp c:\bin\alfresco\tomcat\webapps\alfresco.war {noformat} # You should be able to verify the install by running: {noformat} java -jar alfresco-mmt-2.1.1.jar list c:\bin\alfresco\tomcat\webapps\alfresco.war {noformat} and you should see something like: {noformat} Module 'emailListener' installed in 'c:\bin\alfresco\tomcat\webapps\alfresco.war' - Title: EmailListener - Version: 2.1 - Install Date: Fri Dec 07 08:43:10 PST 2007 - Desription: EmailListener Module {noformat} # Finally, to start the service, just go into your Windows Service control panel and locate the service that is now named 'Alfresco Server'. You can start and stop Alfresco from this control panel. ]]> 2785288 15664243 15631500 2818058 "Downloads">"2.1 Releases">"2.1.1" # I then clicked on alfresco-enterprise-tomcat-2.1.1.zip to download the zip file. # Went to [http://customers.alfresco.com] (I was still logged in) # Went to "Company Home">"Downloads">"2.1 Releases">"2.1.1">"License Files" # I went ahead and downloaded all the "*.lic" files, but I think I only need enterprise-network-customer-unlimited.lic" # Logged out of Alfresco. # Since I suspect I will need a JDBC driver for SQLServer, I downloaded the jTDS-1.2.2 driver from the jtds web site (just Google jtds and go to the download section of the top google return). # I closed the Firefox browser. # I extracted the jtds-1.2.2.jar file from the jtds download # I downloaded and installed the JRockit 6 R27.4 JDK Microsoft Windows (x86 - 32 bit) from BEA's web site {note} After installing JRockit, make sure you set the JAVA_HOME environment variable to point to the installation of JRockit. For example, I went to the desktop, right clicked on the computer, did Properties, then clicked on the Advanced tab, then click on the environment variables button and then created a new system variable named JAVA_HOME and set to c:\bin\Java\jrockit-R27.4.0-jdk1.6.0_02 {note} # I ran the installer, changed the "Program Files" to "bin" in the installation directory for both the JDK and the JRE. I also chose to install the JRE as public. # Using Firefox, I downloaded the PHP 5.2.5 Windows Installer from php.net and installed it. Although I installed it, I did not integrate it with a web server as I want Alfresco to take port 80. I probably did not need to install PHP, but I thought I would anyway. (again, I changed install path from "Program Files" to "bin" # I also downloaded and installed OpenOffice and ran it once so I could get through the initial startup # I setup a Alfresco database on the server Solstice and granted the LAGOON\DB_Collaboration account to be the db_owner of the Alfresco database. # I unzipped the alfresco tomcat zip file to an alfresco directory in c:\bin # I then went to the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions directory for the customization of the server. ## I edited the custom-repository.properties file ### Changed the dir.root and dir.indexes to look like: {noformat} dir.root=//tornado.shore.mbari.org/Alfresco/alf_data dir.indexes=d:/alf_data/lucene-indexes {noformat} ### Commented out the db.* lines for the HSQL Connection (db.driver and db.url) ### Uncommented the db.* lines for MSSQL and changed to use the jTDS driver. They should look like: {noformat} db.driver=net.sourceforge.jtds.jdbc.Driver db.url=jdbc:jtds:sqlserver://solstice.shore.mbari.org/Alfresco;domain=SHORE;user=DB_Collaboration;password=XXXXXXXXX {noformat} ### I also added the following section to override the mail server settings {noformat} # Mail server configuration mail.host=mail.mbari.org mail.port=25 mail.username= mail.password= {noformat} ## Edited the custom-hibernate-dialect.properties file ### Commented out the HSQL Dialect ### Uncommented the MSSQL Dialect # I then installed the jtds-1.2.2.jar in the c:\bin\alfresco\tomcat\common\lib so that it will be on the classpath when Alfresco is started # Now this is not necessarily fun, but in order to really get it configured the way we want it, you need to pull the original .war file out, edit some stuff inside and re-create the .war. {note} This should all be done before starting Alfresco for the first time. {note} # Copy the c:\Alfresco\tomcat\webapps\alfresco.war file to your home directory. # Make a second copy so that you will always the original (I copied to alfresco.war.orig and moved it somewhere else. It is important to move it and have only the alfresco.war file in the directory because when you un-jar it, all the files go right where alfresco.war is.) # From a command line, un-jar the war file using: {noformat} jar -xvf alfresco.war {noformat} # This unpacks a lot of files and after it completes, move (or delete) the alfresco.war file from the directory. This needs to be done so it does not end up in the new .war file. # I wanted to change the "Company Home" that seems to be everywhere to something that says MBARI. ## Edited ./WEB-INF/classes/alfresco/messages/webclient.properties and changed company_home from 'Company Home' to 'MBARI' ## Edited ./WEB-INF/classes/alfresco/messages/webclient_en_US.properties and changed company_home from 'Company Home' to 'MBARI' ## I edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces.properties and changed the first two lines to read {noformat} spaces.company_home.name=MBARI spaces.company_home.description=The root space for MBARI {noformat} ## Edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces_en_US.properties and made the same changes as the previous step {tip} This took a bit to find all these, and to be honest, I am not sure which one actually made the change on the GUI, but I suspect it was the _en_US ones. {tip} # When users are imported via LDAP, user spaces get created automatically. In order to put them where I wanted them to go (instead of right in the Company Home), I edited the ./WEB-INF/classes/alfresco/authentication-services-context.xml file. In the file there is a bean with an name of personalHomeFolderProvider. There is a property name 'path' and I added {noformat} /${spaces.user_homes.childname} {noformat} to the end to try to get them to create the user spaces there instead of in the Company Home. The final bean XML looks like: {noformat} /${spaces.company_home.childname}/${spaces.user_homes.childname} ${spaces.store} false All All {noformat} # I wanted to change the logo that is used. I attached the replacement logo [here|^AlfrescoLogo32.png]. Copy this to ./images/logo and overwrite the one that is there. # In order to setup SSL for the application (will do that later), edit ./WEB-INF/web.xml and add the following {noformat} Login Pages /* CONFIDENTIAL {noformat} right before the ending tag at the bottom of the file. # Now in order to change the default behavior so that all content is versioned from the start, I edited the .\WEB-INF\classes\alfresco\model\contentModel.xml and searched for the content type definition block. {noformat} Content cm:cmobject true d:content false true false true {noformat} and added the following block right before the ending tag: {noformat} cm:versionable {noformat} so the final block looks like: {noformat} Content cm:cmobject true d:content false true false true cm:versionable {noformat} # That takes care of all the changes to the WAR file. We can now put it back into .war form. # While you are in the directory you expanded the war file in, run ## jar cvfm alfresco.war META-INF\MANIFEST.MF . # You should now have an alfresco.war file in the directory. Move that back to the alfresco install and overwrite the existing one. # Most users like the details view, so I set the default to that by editing c:\Alfresco\tomcat\shared\classes\alfresco\extensions/web-client-config-custom.xml and added: {noformat} details 20
20
20 {noformat} right before the closing tag. # Now in order to use MBARI accounts, NTLM authentication was turned on and then chained with the native Alfresco accounts so that we could have non-MBARI accounts on the Alfresco server. ## In order to enable NTLM and native Alfresco authentication, I had to edit two files. For simplicity I have just attached them here and they can be downloaded and installed in the extensions directory. ### The first file is the [ntlm-authentication-context.xml|^ntlm-authentication-context.xml] file. This configures and enables NTLM authentication. ### The next file was the [chaining-authentication-context.xml|^chaining-authentication-context.xml] file which enabled Alfresco authentication and chained it together with the NTLM authentication from the previous file. # Then in order to setup CIFS on the server, I edited the file-servers-custom.xml file to look like the attached [file-servers-custom.xml|^file-servers-custom.xml] file. # In order to grant certain accounts admin privs, I created a new custom-authority-services-context.xml in the same directory as the ldap-authentication-context.xml file and added {noformat} kgomes admin administrator {noformat} # In order for Alfresco to handle all port 80 traffic, I changed Tomcat so that it takes port 80 and SSL goes over port 443. So I edited the c:\Alfresco\tomcat\conf\server.xml file and changed the 8080 port to 80 and the 8443 port to 443 (the 443 change is done in two places). # I copied the enterprise-network-unlimited.lic file into the c:\Alfresco\tomcat\shared\classes\alfresco\extensions\license directory # Just to keep things clean, I edited the c:\bin\alfresco\alfresco.bat file and put 'rem' in front of the second JAVA_OPTS set as I am using Java 6. # Now after you run it for the first time and the database structure gets created, you can't restart it because you get: {noformat} java.sql.SQLException: Column names in each table must be unique. Column name 'ID_' in table 'JBPM_ACTION' is specified more than once. {noformat} Sigh, so in order to keep Alfresco from hurting itself, I had to turn off the schema updates. This is done by editing the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions\custom-repository.properties and adding the following: {noformat} db.schema.update=false {noformat} and then restarting alfresco. # Now I needed to setup the SSL for the web traffic. Cathy Sewell was instrumental in getting this working. She ordered a new certificate specifically for alfresco and put it in the c:\local\cert folder. I edited the c:\bin\alfresco\tomcat\conf\server.xml file and uncommented the SSL section and edited to look like that shown below. {noformat} {noformat} # To install Alfresco as a Windows Service use a command prompt and enter the following: {noformat} cd c:\bin\alfresco\tomcat\bin service.bat install alfresco tomcat5.exe //US//alfresco --DisplayName "Alfresco Server" tomcat5.exe //US//alfresco --JvmMs=512 --JvmMx=1024 --JvmSs=64 tomcat5.exe //US//alfresco --JavaHome=c:/bin/Java/jrockit-R27.4.0-jdk1.6.0_02 tomcat5.exe //US//alfresco --Environment ALF_HOME=c:/bin/alfresco/ tomcat5.exe //US//alfresco --Environment PATH=c:/bin/alfresco/bin;%PATH% tomcat5.exe //US//alfresco --StartPath c:/bin/alfresco --Startup auto {noformat} # To uninstall the service, at a later time, do the following: {noformat} cd c:\bin\alfresco\tomcat\bin service.bat uninstall alfresco {noformat} # To edit your service settings at any time: {noformat} cd c:\alfresco\tomcat\bin tomcat5w.exe //ES//alfresco {noformat} # In order to install certain modules (like the email listener), I had to get the Alfresco Module Manager from the customers.alfresco.com download site. I downloaded the alfresco-mmt-2.1.1.jar file locally so I could use it to install modules. # I then downloaded the email listener module from [http://forge.alfresco.com/projects/email-listener/]. It came as a zip file, so I unzipped it and it created a folder with the appropriate emailListener.amp in it. # Make another backup copy of the alfresco.war file and put somewhere in case you want to roll this back. # Open a command prompt windows and cd to the location where the Alfresco Module Manager jar is. # Run the following: {noformat} java -jar alfresco-mmt-2.1.1.jar path_to_emailListener.amp path_to_alfresco.war {noformat} So for me this looked like: {noformat} java -jar alfresco-mmt-2.1.1.jar .\email-listener_2.1RC2\emailListener.amp c:\bin\alfresco\tomcat\webapps\alfresco.war {noformat} # You should be able to verify the install by running: {noformat} java -jar alfresco-mmt-2.1.1.jar list c:\bin\alfresco\tomcat\webapps\alfresco.war {noformat} and you should see something like: {noformat} Module 'emailListener' installed in 'c:\bin\alfresco\tomcat\webapps\alfresco.war' - Title: EmailListener - Version: 2.1 - Install Date: Fri Dec 07 08:43:10 PST 2007 - Desription: EmailListener Module {noformat} # Finally, to start the service, just go into your Windows Service control panel and locate the service that is now named 'Alfresco Server'. You can start and stop Alfresco from this control panel. ]]> 2785292 2818057 "Downloads">"2.1 Releases">"2.1.1" # I then clicked on alfresco-enterprise-tomcat-2.1.1.zip to download the zip file. # Went to [http://customers.alfresco.com] (I was still logged in) # Went to "Company Home">"Downloads">"2.1 Releases">"2.1.1">"License Files" # I went ahead and downloaded all the "*.lic" files, but I think I only need enterprise-network-customer-unlimited.lic" # Logged out of Alfresco. # Since I suspect I will need a JDBC driver for SQLServer, I downloaded the jTDS-1.2.2 driver from the jtds web site (just Google jtds and go to the download section of the top google return). # I closed the Firefox browser. # I extracted the jtds-1.2.2.jar file from the jtds download # I downloaded and installed the JRockit 6 R27.4 JDK Microsoft Windows (x86 - 32 bit) from BEA's web site {note} After installing JRockit, make sure you set the JAVA_HOME environment variable to point to the installation of JRockit. For example, I went to the desktop, right clicked on the computer, did Properties, then clicked on the Advanced tab, then click on the environment variables button and then created a new system variable named JAVA_HOME and set to c:\bin\Java\jrockit-R27.4.0-jdk1.6.0_02 {note} # I ran the installer, changed the "Program Files" to "bin" in the installation directory for both the JDK and the JRE. I also chose to install the JRE as public. # Using Firefox, I downloaded the PHP 5.2.5 Windows Installer from php.net and installed it. Although I installed it, I did not integrate it with a web server as I want Alfresco to take port 80. I probably did not need to install PHP, but I thought I would anyway. (again, I changed install path from "Program Files" to "bin" # I also downloaded and installed OpenOffice and ran it once so I could get through the initial startup # I setup a Alfresco database on the server Solstice and granted the LAGOON\DB_Collaboration account to be the db_owner of the Alfresco database. # I unzipped the alfresco tomcat zip file to an alfresco directory in c:\bin # I then went to the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions directory for the customization of the server. ## I edited the custom-repository.properties file ### Changed the dir.root and dir.indexes to look like: {noformat} dir.root=//tornado.shore.mbari.org/Alfresco/alf_data dir.indexes=d:/alf_data/lucene-indexes {noformat} ### Commented out the db.* lines for the HSQL Connection (db.driver and db.url) ### Uncommented the db.* lines for MSSQL and changed to use the jTDS driver. They should look like: {noformat} db.driver=net.sourceforge.jtds.jdbc.Driver db.url=jdbc:jtds:sqlserver://solstice.shore.mbari.org/Alfresco;domain=SHORE;user=DB_Collaboration;password=XXXXXXXXX {noformat} ### I also added the following section to override the mail server settings {noformat} # Mail server configuration mail.host=mail.mbari.org mail.port=25 mail.username= mail.password= {noformat} ## Edited the custom-hibernate-dialect.properties file ### Commented out the HSQL Dialect ### Uncommented the MSSQL Dialect # I then installed the jtds-1.2.2.jar in the c:\bin\alfresco\tomcat\common\lib so that it will be on the classpath when Alfresco is started # Now this is not necessarily fun, but in order to really get it configured the way we want it, you need to pull the original .war file out, edit some stuff inside and re-create the .war. {note} This should all be done before starting Alfresco for the first time. {note} # Copy the c:\Alfresco\tomcat\webapps\alfresco.war file to your home directory. # Make a second copy so that you will always the original (I copied to alfresco.war.orig and moved it somewhere else. It is important to move it and have only the alfresco.war file in the directory because when you un-jar it, all the files go right where alfresco.war is.) # From a command line, un-jar the war file using: {noformat} jar -xvf alfresco.war {noformat} # This unpacks a lot of files and after it completes, move (or delete) the alfresco.war file from the directory. This needs to be done so it does not end up in the new .war file. # I wanted to change the "Company Home" that seems to be everywhere to something that says MBARI. ## Edited ./WEB-INF/classes/alfresco/messages/webclient.properties and changed company_home from 'Company Home' to 'MBARI' ## Edited ./WEB-INF/classes/alfresco/messages/webclient_en_US.properties and changed company_home from 'Company Home' to 'MBARI' ## I edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces.properties and changed the first two lines to read {noformat} spaces.company_home.name=MBARI spaces.company_home.description=The root space for MBARI {noformat} ## Edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces_en_US.properties and made the same changes as the previous step {tip} This took a bit to find all these, and to be honest, I am not sure which one actually made the change on the GUI, but I suspect it was the _en_US ones. {tip} # When users are imported via LDAP, user spaces get created automatically. In order to put them where I wanted them to go (instead of right in the Company Home), I edited the ./WEB-INF/classes/alfresco/authentication-services-context.xml file. In the file there is a bean with an name of personalHomeFolderProvider. There is a property name 'path' and I added {noformat} /${spaces.user_homes.childname} {noformat} to the end to try to get them to create the user spaces there instead of in the Company Home. The final bean XML looks like: {noformat} /${spaces.company_home.childname}/${spaces.user_homes.childname} ${spaces.store} false All All {noformat} # I wanted to change the logo that is used. I attached the replacement logo [here|^AlfrescoLogo32.png]. Copy this to ./images/logo and overwrite the one that is there. # In order to setup SSL for the application (will do that later), edit ./WEB-INF/web.xml and add the following {noformat} Login Pages /* CONFIDENTIAL {noformat} right before the ending tag at the bottom of the file. # Now in order to change the default behavior so that all content is versioned from the start, I edited the .\WEB-INF\classes\alfresco\model\contentModel.xml and searched for the content type definition block. {noformat} Content cm:cmobject true d:content false true false true {noformat} and added the following block right before the ending tag: {noformat} cm:versionable {noformat} so the final block looks like: {noformat} Content cm:cmobject true d:content false true false true cm:versionable {noformat} # That takes care of all the changes to the WAR file. We can now put it back into .war form. # While you are in the directory you expanded the war file in, run ## jar cvfm alfresco.war META-INF\MANIFEST.MF . # You should now have an alfresco.war file in the directory. Move that back to the alfresco install and overwrite the existing one. # Most users like the details view, so I set the default to that by editing c:\Alfresco\tomcat\shared\classes\alfresco\extensions/web-client-config-custom.xml and added: {noformat} details 20
20
20 {noformat} right before the closing tag. # Now in order to use MBARI accounts, NTLM authentication was turned on and then chained with the native Alfresco accounts so that we could have non-MBARI accounts on the Alfresco server. ## In order to enable NTLM and native Alfresco authentication, I had to edit two files. For simplicity I have just attached them here and they can be downloaded and installed in the extensions directory. ### The first file is the [ntlm-authentication-context.xml|^ntlm-authentication-context.xml] file. This configures and enables NTLM authentication. ### The next file was the [chaining-authentication-context.xml|^chaining-authentication-context.xml] file which enabled Alfresco authentication and chained it together with the NTLM authentication from the previous file. # Then in order to setup CIFS on the server, I edited the file-servers-custom.xml file to look like the attached [file-servers-custom.xml|^file-servers-custom.xml] file. # In order to grant certain accounts admin privs, I created a new custom-authority-services-context.xml in the same directory as the ldap-authentication-context.xml file and added {noformat} kgomes admin administrator {noformat} # In order for Alfresco to handle all port 80 traffic, I changed Tomcat so that it takes port 80 and SSL goes over port 443. So I edited the c:\Alfresco\tomcat\conf\server.xml file and changed the 8080 port to 80 and the 8443 port to 443 (the 443 change is done in two places). # I copied the enterprise-network-unlimited.lic file into the c:\Alfresco\tomcat\shared\classes\alfresco\extensions\license directory # Just to keep things clean, I edited the c:\bin\alfresco\alfresco.bat file and put 'rem' in front of the second JAVA_OPTS set as I am using Java 6. # Now after you run it for the first time and the database structure gets created, you can't restart it because you get: {noformat} java.sql.SQLException: Column names in each table must be unique. Column name 'ID_' in table 'JBPM_ACTION' is specified more than once. {noformat} Sigh, so in order to keep Alfresco from hurting itself, I had to turn off the schema updates. This is done by editing the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions\custom-repository.properties and adding the following: {noformat} db.schema.update=false {noformat} and then restarting alfresco. # Now I needed to setup the SSL for the web traffic. Cathy Sewell was instrumental in getting this working. She ordered a new certificate specifically for alfresco and put it in the c:\local\cert folder. I edited the c:\bin\alfresco\tomcat\conf\server.xml file and uncommented the SSL section and edited to look like that shown below. {noformat} {noformat} # To install Alfresco as a Windows Service use a command prompt and enter the following: {noformat} cd c:\bin\alfresco\tomcat\bin service.bat install alfresco tomcat5.exe //US//alfresco --DisplayName "Alfresco Server" tomcat5.exe //US//alfresco --JvmMs=512 --JvmMx=1024 --JvmSs=64 tomcat5.exe //US//alfresco --JavaHome=c:/bin/Java/jrockit-R27.4.0-jdk1.6.0_02 tomcat5.exe //US//alfresco --Environment ALF_HOME=c:/bin/alfresco/ tomcat5.exe //US//alfresco --Environment PATH=c:/bin/alfresco/bin;%PATH% tomcat5.exe //US//alfresco --StartPath c:/bin/alfresco --Startup auto {noformat} # To uninstall the service, at a later time, do the following: {noformat} cd c:\bin\alfresco\tomcat\bin service.bat uninstall alfresco {noformat} # To edit your service settings at any time: {noformat} cd c:\alfresco\tomcat\bin tomcat5w.exe //ES//alfresco {noformat} # In order to install certain modules (like the email listener), I had to get the Alfresco Module Manager from the customers.alfresco.com download site. I downloaded the alfresco-mmt-2.1.1.jar file locally so I could use it to install modules. # I then downloaded the email listener module from [http://forge.alfresco.com/projects/email-listener/]. It came as a zip file, so I unzipped it and it created a folder with the appropriate emailListener.amp in it. # Make another backup copy of the alfresco.war file and put somewhere in case you want to roll this back. # Open a command prompt windows and cd to the location where the Alfresco Module Manager jar is. # Run the following: {noformat} java -jar alfresco-mmt-2.1.1.jar path_to_emailListener.amp path_to_alfresco.war {noformat} So for me this looked like: {noformat} java -jar alfresco-mmt-2.1.1.jar .\email-listener_2.1RC2\emailListener.amp c:\bin\alfresco\tomcat\webapps\alfresco.war {noformat} # You should be able to verify the install by running: {noformat} java -jar alfresco-mmt-2.1.1.jar list c:\bin\alfresco\tomcat\webapps\alfresco.war {noformat} and you should see something like: {noformat} Module 'emailListener' installed in 'c:\bin\alfresco\tomcat\webapps\alfresco.war' - Title: EmailListener - Version: 2.1 - Install Date: Fri Dec 07 08:43:10 PST 2007 - Desription: EmailListener Module {noformat} # Finally, to start the service, just go into your Windows Service control panel and locate the service that is now named 'Alfresco Server'. You can start and stop Alfresco from this control panel. ]]> 2785291 15664245 15631502 2818060 "Downloads">"2.1 Releases">"2.1.1" # I then clicked on alfresco-enterprise-tomcat-2.1.1.zip to download the zip file. # Went to [http://customers.alfresco.com] (I was still logged in) # Went to "Company Home">"Downloads">"2.1 Releases">"2.1.1">"License Files" # I went ahead and downloaded all the "*.lic" files, but I think I only need enterprise-network-customer-unlimited.lic" # Logged out of Alfresco. # Since I suspect I will need a JDBC driver for SQLServer, I downloaded the jTDS-1.2.2 driver from the jtds web site (just Google jtds and go to the download section of the top google return). # I closed the Firefox browser. # I extracted the jtds-1.2.2.jar file from the jtds download # I downloaded and installed the JRockit 6 R27.4 JDK Microsoft Windows (x86 - 32 bit) from BEA's web site {note} After installing JRockit, make sure you set the JAVA_HOME environment variable to point to the installation of JRockit. For example, I went to the desktop, right clicked on the computer, did Properties, then clicked on the Advanced tab, then click on the environment variables button and then created a new system variable named JAVA_HOME and set to c:\bin\Java\jrockit-R27.4.0-jdk1.6.0_02 {note} # I ran the installer, changed the "Program Files" to "bin" in the installation directory for both the JDK and the JRE. I also chose to install the JRE as public. # Using Firefox, I downloaded the PHP 5.2.5 Windows Installer from php.net and installed it. Although I installed it, I did not integrate it with a web server as I want Alfresco to take port 80. I probably did not need to install PHP, but I thought I would anyway. (again, I changed install path from "Program Files" to "bin" # I also downloaded and installed OpenOffice and ran it once so I could get through the initial startup # I setup a Alfresco database on the server Solstice and granted the LAGOON\DB_Collaboration account to be the db_owner of the Alfresco database. # I unzipped the alfresco tomcat zip file to an alfresco directory in c:\bin # I then went to the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions directory for the customization of the server. ## I edited the custom-repository.properties file ### Changed the dir.root and dir.indexes to look like: {noformat} dir.root=//tornado.shore.mbari.org/Alfresco/alf_data dir.indexes=d:/alf_data/lucene-indexes {noformat} ### Commented out the db.* lines for the HSQL Connection (db.driver and db.url) ### Uncommented the db.* lines for MSSQL and changed to use the jTDS driver. They should look like: {noformat} db.driver=net.sourceforge.jtds.jdbc.Driver db.url=jdbc:jtds:sqlserver://solstice.shore.mbari.org/Alfresco;domain=SHORE;user=DB_Collaboration;password=XXXXXXXXX {noformat} ### I also added the following section to override the mail server settings {noformat} # Mail server configuration mail.host=mail.mbari.org mail.port=25 mail.username= mail.password= {noformat} ## Edited the custom-hibernate-dialect.properties file ### Commented out the HSQL Dialect ### Uncommented the MSSQL Dialect # I then installed the jtds-1.2.2.jar in the c:\bin\alfresco\tomcat\common\lib so that it will be on the classpath when Alfresco is started # Now this is not necessarily fun, but in order to really get it configured the way we want it, you need to pull the original .war file out, edit some stuff inside and re-create the .war. {note} This should all be done before starting Alfresco for the first time. {note} # Copy the c:\Alfresco\tomcat\webapps\alfresco.war file to your home directory. # Make a second copy so that you will always the original (I copied to alfresco.war.orig and moved it somewhere else. It is important to move it and have only the alfresco.war file in the directory because when you un-jar it, all the files go right where alfresco.war is.) # From a command line, un-jar the war file using: {noformat} jar -xvf alfresco.war {noformat} # This unpacks a lot of files and after it completes, move (or delete) the alfresco.war file from the directory. This needs to be done so it does not end up in the new .war file. # I wanted to change the "Company Home" that seems to be everywhere to something that says MBARI. ## Edited ./WEB-INF/classes/alfresco/messages/webclient.properties and changed company_home from 'Company Home' to 'MBARI' ## Edited ./WEB-INF/classes/alfresco/messages/webclient_en_US.properties and changed company_home from 'Company Home' to 'MBARI' ## I edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces.properties and changed the first two lines to read {noformat} spaces.company_home.name=MBARI spaces.company_home.description=The root space for MBARI {noformat} ## Edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces_en_US.properties and made the same changes as the previous step {tip} This took a bit to find all these, and to be honest, I am not sure which one actually made the change on the GUI, but I suspect it was the _en_US ones. {tip} # When users are imported via LDAP, user spaces get created automatically. In order to put them where I wanted them to go (instead of right in the Company Home), I edited the ./WEB-INF/classes/alfresco/authentication-services-context.xml file. In the file there is a bean with an name of personalHomeFolderProvider. There is a property name 'path' and I added {noformat} /${spaces.user_homes.childname} {noformat} to the end to try to get them to create the user spaces there instead of in the Company Home. The final bean XML looks like: {noformat} /${spaces.company_home.childname}/${spaces.user_homes.childname} ${spaces.store} false All All {noformat} # I wanted to change the logo that is used. I attached the replacement logo [here|^AlfrescoLogo32.png]. Copy this to ./images/logo and overwrite the one that is there. # In order to setup SSL for the application (will do that later), edit ./WEB-INF/web.xml and add the following {noformat} Login Pages /* CONFIDENTIAL {noformat} right before the ending tag at the bottom of the file. # Now in order to change the default behavior so that all content is versioned from the start, I edited the .\WEB-INF\classes\alfresco\model\contentModel.xml and searched for the content type definition block. {noformat} Content cm:cmobject true d:content false true false true {noformat} and added the following block right before the ending tag: {noformat} cm:versionable {noformat} so the final block looks like: {noformat} Content cm:cmobject true d:content false true false true cm:versionable {noformat} # That takes care of all the changes to the WAR file. We can now put it back into .war form. # While you are in the directory you expanded the war file in, run ## jar cvfm alfresco.war META-INF\MANIFEST.MF . # You should now have an alfresco.war file in the directory. Move that back to the alfresco install and overwrite the existing one. # Most users like the details view, so I set the default to that by editing c:\Alfresco\tomcat\shared\classes\alfresco\extensions/web-client-config-custom.xml and added: {noformat} details 20
20
20 {noformat} right before the closing tag. # Now in order to use MBARI accounts, NTLM authentication was turned on and then chained with the native Alfresco accounts so that we could have non-MBARI accounts on the Alfresco server. ## In order to enable NTLM and native Alfresco authentication, I had to edit two files. For simplicity I have just attached them here and they can be downloaded and installed in the extensions directory. ### The first file is the [ntlm-authentication-context.xml|^ntlm-authentication-context.xml] file. This configures and enables NTLM authentication. ### The next file was the [chaining-authentication-context.xml|^chaining-authentication-context.xml] file which enabled Alfresco authentication and chained it together with the NTLM authentication from the previous file. # Then in order to setup CIFS on the server, I edited the file-servers-custom.xml file to look like the attached [file-servers-custom.xml|^file-servers-custom.xml] file. # In order to grant certain accounts admin privs, I created a new custom-authority-services-context.xml in the same directory as the ldap-authentication-context.xml file and added {noformat} kgomes admin administrator {noformat} # In order for Alfresco to handle all port 80 traffic, I changed Tomcat so that it takes port 80 and SSL goes over port 443. So I edited the c:\Alfresco\tomcat\conf\server.xml file and changed the 8080 port to 80 and the 8443 port to 443 (the 443 change is done in two places). # I copied the enterprise-network-unlimited.lic file into the c:\Alfresco\tomcat\shared\classes\alfresco\extensions\license directory # Just to keep things clean, I edited the c:\bin\alfresco\alfresco.bat file and put 'rem' in front of the second JAVA_OPTS set as I am using Java 6. # Now after you run it for the first time and the database structure gets created, you can't restart it because you get: {noformat} java.sql.SQLException: Column names in each table must be unique. Column name 'ID_' in table 'JBPM_ACTION' is specified more than once. {noformat} Sigh, so in order to keep Alfresco from hurting itself, I had to turn off the schema updates. This is done by editing the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions\custom-repository.properties and adding the following: {noformat} db.schema.update=false {noformat} and then restarting alfresco. # Now I needed to setup the SSL for the web traffic. Cathy Sewell was instrumental in getting this working. She ordered a new certificate specifically for alfresco and put it in the c:\local\cert folder. I edited the c:\bin\alfresco\tomcat\conf\server.xml file and uncommented the SSL section and edited to look like that shown below. {noformat} {noformat} # To install Alfresco as a Windows Service use a command prompt and enter the following: {noformat} cd c:\bin\alfresco\tomcat\bin service.bat install alfresco tomcat5.exe //US//alfresco --DisplayName "Alfresco Server" tomcat5.exe //US//alfresco --JvmMs=512 --JvmMx=1024 --JvmSs=64 tomcat5.exe //US//alfresco --JavaHome=c:/bin/Java/jrockit-R27.4.0-jdk1.6.0_02 tomcat5.exe //US//alfresco --Environment ALF_HOME=c:/bin/alfresco/ tomcat5.exe //US//alfresco --Environment PATH=c:/bin/alfresco/bin;%PATH% tomcat5.exe //US//alfresco --StartPath c:/bin/alfresco --Startup auto {noformat} # To uninstall the service, at a later time, do the following: {noformat} cd c:\bin\alfresco\tomcat\bin service.bat uninstall alfresco {noformat} # To edit your service settings at any time: {noformat} cd c:\alfresco\tomcat\bin tomcat5w.exe //ES//alfresco {noformat} # In order to install certain modules (like the email listener), I had to get the Alfresco Module Manager from the customers.alfresco.com download site. I downloaded the alfresco-mmt-2.1.1.jar file locally so I could use it to install modules. # I then downloaded the email listener module from [http://forge.alfresco.com/projects/email-listener/]. It came as a zip file, so I unzipped it and it created a folder with the appropriate emailListener.amp in it. # Make another backup copy of the alfresco.war file and put somewhere in case you want to roll this back. # Open a command prompt windows and cd to the location where the Alfresco Module Manager jar is. # Run the following: {noformat} java -jar alfresco-mmt-2.1.1.jar path_to_emailListener.amp path_to_alfresco.war {noformat} So for me this looked like: {noformat} java -jar alfresco-mmt-2.1.1.jar .\email-listener_2.1RC2\emailListener.amp c:\bin\alfresco\tomcat\webapps\alfresco.war {noformat} # You should be able to verify the install by running: {noformat} java -jar alfresco-mmt-2.1.1.jar list c:\bin\alfresco\tomcat\webapps\alfresco.war {noformat} and you should see something like: {noformat} Module 'emailListener' installed in 'c:\bin\alfresco\tomcat\webapps\alfresco.war' - Title: EmailListener - Version: 2.1 - Install Date: Fri Dec 07 08:43:10 PST 2007 - Desription: EmailListener Module {noformat} # Finally, to start the service, just go into your Windows Service control panel and locate the service that is now named 'Alfresco Server'. You can start and stop Alfresco from this control panel. ]]> 2785294 10944996 10912241 10944997 10912242 15664228 Backup Database... ## Select Database-complete ## Click on Add... under Destination ## I typed in a file location of \\tempest\tempbox\kgomes\backups\crowd\db_backup as the file to backup to. ## I then created a new tar.gz file for the /opt/atlassian-crowd-1.5.1 installation and put in the same backup location on tempest. ## I then created a new tar.gz file for the crowd home directory /data/crowd and put in same tempest location # I copied the jtds-1.2.jar from /opt/atlassian-crowd-1.5.1/crowd-webapp/WEB-INF/lib to the same directory in the new installation # I then edited the /opt/atlassian-crowd-1.6/crowd-webapp/WEB-INF/classes/crowd-init.properties and pointed the crowd home directory to /data/crowd # I then copied the updated crowd client jar (/opt/atlassian-crowd-1.6/client/crowd-integrations-client-1.6.jar) to /opt/confluence/confluence/WEB-INF/lib and to /opt/jira/atlassian-jira/WEB-INF/lib (I removed the old ones too IMPORTANT!) # I downloaded the recommended crowd-ehcache.xml file from the instructions listed above and copied to the /opt/confluence/confluence/WEB-INF/classes and /opt/jira/atlassian-jira/WEB-INF/classes directories # Lastly I changed the /opt/crowd symbolic link to point to the new crowd installation, shut down confluence, jira, and crowd and restarted crowd. # After the successful start up of the three applications, I put all the backup files in Alfresco [here|https://alfresco.mbari.org/alfresco/webdav/Engineering/Tools/Collaboration%20Tools/Atlassian%20Crowd/Backups/2008_12_29]]]> 15631482 15664239 15631496 15664241 15631498 10945009 10912254 10944921 $5000 Unit Cost | $30,000 | $ | | 5020-000 | Books/Subscriptions | $1,850 | $ | | 5060-000 | Dues, Membership, Licenses | $5,720 | $ | | 5130-000 | Outside Srvc - General | $7,500 | $ | | 5150-000 | Outside Srvc - Maint Contracts | $25,050 | $ | | 5300-000 | Supplies - Computer (Hardware) | $11,875 | $ | | 5310-000 | Supplies - Computer (Software) | $10,180 | $ | | 5320-000 | Supplies - Engineering Lab | $17,850 | $ | | 5330-000 | Supplies - Non-Capitalized Equipment | $13,100 | $ | | *Total* | | $123,125 | $ | {panel} {column} {section} ]]> 10912163 10944919 $5000 Unit Cost | $30,000 | $ | | 5020-000 | Books/Subscriptions | $1,850 | $ | | 5060-000 | Dues, Membership, Licenses | $5,720 | $ | | 5130-000 | Outside Srvc - General | $7,500 | $ | | 5150-000 | Outside Srvc - Maint Contracts | $25,050 | $ | | 5300-000 | Supplies - Computer (Hardware) | $11,875 | $ | | 5310-000 | Supplies - Computer (Software) | $10,180 | $ | | 5320-000 | Supplies - Engineering Lab | $17,850 | $ | | 5330-000 | Supplies - Non-Capitalized Equipment | $13,100 | $ | | *Total* | | $123,125 | $ | {panel} {column} {section} ]]> 10912161 10944918 $5000 Unit Cost | $30,000 | $ | | 5020-000 | Books/Subscriptions | $1,850 | $ | | 5060-000 | Dues, Membership, Licenses | $5,720 | $ | | 5130-000 | Outside Srvc - General | $7,500 | $ | | 5150-000 | Outside Srvc - Maint Contracts | $25,050 | $ | | 5300-000 | Supplies - Computer (Hardware) | $11,875 | $ | | 5310-000 | Supplies - Computer (Software) | $10,180 | $ | | 5320-000 | Supplies - Engineering Lab | $17,850 | $ | | 5330-000 | Supplies - Non-Capitalized Equipment | $13,100 | $ | | *Total* | | $123,125 | $ | {panel} {column} {section} ]]> 10912160 10944930 $5000 Unit Cost | $30,000 | $ | | 5020-000 | Books/Subscriptions | $1,850 | $ | | 5060-000 | Dues, Membership, Licenses | $5,720 | $ | | 5130-000 | Outside Srvc - General | $7,500 | $ | | 5150-000 | Outside Srvc - Maint Contracts | $25,050 | $ | | 5300-000 | Supplies - Computer (Hardware) | $11,875 | $ | | 5310-000 | Supplies - Computer (Software) | $10,180 | $ | | 5320-000 | Supplies - Engineering Lab | $17,850 | $ | | 5330-000 | Supplies - Non-Capitalized Equipment | $13,100 | $ | | *Total* | | $123,125 | $ | {panel} {column} {section} ]]> 10912173 1039 ... mbari MBARI Repository http://oceana.shore.mbari.org/maven2 ... ... {code} h3. Including a Dependency from the Repository Once the MBARI repository is included in you build, you can browse the repository to see what projects are available (just go to [http://oceana.shore.mbari.org/maven2]). If you find a dependency you need you can reference it in your _pom.xml_. Here's an example... {code:xml} ... ... qt4j qt4j 0.5 ... ... {code} h3. Putting a Dependency into the Repository The easiest way to put a dependency into the repository is to setup a Maven build file (i.e. _pom.xml_). In _pom.xml_ add the following _distributionManagement_ information: {code:xml} 4.0.0 qt4j qt4j jar 1.0-SNAPSHOT QT4J ... mbari-repository MBARI Repository scp://oceana.shore.mbari.org/var/www/html/maven2 {code} Executing _mvn deploy_ will put your build jar at http://oceana.shore.mbari.org/maven2////-.jar. In the example here it would put it into [http://oceana.shore.mbari.org/maven2/qt4j/qt4j/1.0-SNAPSHOT/] h3. Publishing Maven generated web sites Maven can generate a web site for a default web site for you. You can view samples of the currently published projects at [http://oceana.shore.mbari.org/projects]. It's not very interesting, however, it is a very simple way to publish the javadoc, sources and auto-generated reports. To do so modify your _pom.xml_: {code:xml} ... org.apache.maven.plugins maven-jxr-plugin org.apache.maven.plugins maven-pmd-plugin 1.5 org.apache.maven.plugins maven-checkstyle-plugin ... oceana.shore.mbari.org scp://oceana.shore.mbari.org/var/www/html/projects/${project.name} {code} Then run _mvn javadoc:javadoc site:site site:deploy_. This will build the javadocs, create a site with some useful reports, then publish the site (using scp) to oceana in the correct location. h3. Project Specific Maven Repositories Some projects may need to be configured differently for different deployment locations. For example, [VARS|VARS:Home] is configured differently for each ship and shore. These specific configurations are stored in Maven repositories in [http://oceana.shore.mbari.org/maven2-prj]. Each directory listed there is a different repository. Here's an example of how to include the projects configured for [Eye-in-the-sea|EITS:Home]. {code:xml} mbari-eits MBARI-EITS Repository http://oceana.shore.mbari.org/maven2-prj/eits {code} h2. Using the MBARI repository from an [Ant|http://ant.apache.org] project using Maven Maven repositories can be used from Ant build scripts using [Maven's antlib|http://maven.apache.org/ant-tasks.html]. To do this you must have both Maven and Ant installed. h3. Bootstrapping antlib To boostrap antlib into your projects (so users can build without having to install antlib) modify your _build.xml_ file like so: {code:xml} ... {code} h2. Using the MBARI repository from an [Ant|http://ant.apache.org] project using Ivy Maven repositories can be used from Ant build scripts using [Ivy|http://incubator.apache.org/ivy/]. h3. Referencing the repository In the directory containing the ant build file, _build.xml_, create a file called _ivyconf.xml_. _ivyconf.xml_ tells Ivy where to look for dependencies. The contents of the file will look something like: {code:xml} {code} h3. Including a Dependency from the Repository In the directory containing _build.xml_, create a file called _ivy.xml_. _ivy.xml_ tells Ivy what dependencies to include in your build. Here's an example of it's contents: {code:xml} {code} h3. Using Ivy from Ant The code below will fetch Ivy for you. SO you do not need install any additional software in order to get you build to work. In your ant build file include the following: {code:xml} ... {code} Calling _ant ivy.install_ will fetch all the dependencies from the web and put them into the _lib_ directory of your project. ]]> 1042 10944925 10912167 1038 ... mbari MBARI Repository http://oceana.shore.mbari.org/maven2 ... ... {code} h3. Including a Dependency from the Repository Once the MBARI repository is included in you build, you can browse the repository to see what projects are available (just go to [http://oceana.shore.mbari.org/maven2]). If you find a dependency you need you can reference it in your _pom.xml_. Here's an example... {code:xml} ... ... qt4j qt4j 0.5 ... ... {code} h3. Putting a Dependency into the Repository The easiest way to put a dependency into the repository is to setup a Maven build file (i.e. _pom.xml_). In _pom.xml_ add the following _distributionManagement_ information: {code:xml} 4.0.0 qt4j qt4j jar 1.0-SNAPSHOT QT4J ... mbari-repository MBARI Repository scp://oceana.shore.mbari.org/var/www/html/maven2 {code} Executing _mvn deploy_ will put your build jar at http://oceana.shore.mbari.org/maven2////-.jar. In the example here it would put it into [http://oceana.shore.mbari.org/maven2/qt4j/qt4j/1.0-SNAPSHOT/] h3. Publishing Maven generated web sites Maven can generate a web site for a default web site for you. You can view samples of the currently published projects at [http://oceana.shore.mbari.org/projects]. It's not very interesting, however, it is a very simple way to publish the javadoc, sources and auto-generated reports. To do so modify your _pom.xml_: {code:xml} ... org.apache.maven.plugins maven-jxr-plugin org.apache.maven.plugins maven-pmd-plugin 1.5 org.apache.maven.plugins maven-checkstyle-plugin ... oceana.shore.mbari.org scp://oceana.shore.mbari.org/var/www/html/projects/${project.name} {code} Then run _mvn javadoc:javadoc site:site site:deploy_. This will build the javadocs, create a site with some useful reports, then publish the site (using scp) to oceana in the correct location. h3. Project Specific Maven Repositories Some projects may need to be configured differently for different deployment locations. For example, [VARS|VARS:Home] is configured differently for each ship and shore. These specific configurations are stored in Maven repositories in [http://oceana.shore.mbari.org/maven2-prj]. Each directory listed there is a different repository. Here's an example of how to include the projects configured for [Eye-in-the-sea|EITS:Home]. {code:xml} mbari-eits MBARI-EITS Repository http://oceana.shore.mbari.org/maven2-prj/eits {code} h2. Using the MBARI repository from an [Ant|http://ant.apache.org] project Maven repositories can be used from Ant build scripts using [Ivy|http://incubator.apache.org/ivy/]. h3. Referencing the repository In the directory containing the ant build file, _build.xml_, create a file called _ivyconf.xml_. _ivyconf.xml_ tells Ivy where to look for dependencies. The contents of the file will look something like: {code:xml} {code} h3. Including a Dependency from the Repository In the directory containing _build.xml_, create a file called _ivy.xml_. _ivy.xml_ tells Ivy what dependencies to include in your build. Here's an example of it's contents: {code:xml} {code} h3. Using Ivy from Ant The code below will fetch Ivy for you. SO you do not need install any additional software in order to get you build to work. In your ant build file include the following: {code:xml} ... {code} Calling _ant ivy.install_ will fetch all the dependencies from the web and put them into the _lib_ directory of your project. ]]> 1041 15664162 15631411 10944926 10912168 1037 ... mbari MBARI Repository http://oceana.shore.mbari.org/maven2 ... ... {code} h3. Including a Dependency from the Repository Once the MBARI repository is included in you build, you can browse the repository to see what projects are available (just go to [http://oceana.shore.mbari.org/maven2]). If you find a dependency you need you can reference it in your _pom.xml_. Here's an example... {code:xml} ... ... qt4j qt4j 0.5 ... ... {code} h3. Putting a Dependency into the Repository The easiest way to put a dependency into the repository is to setup a Maven build file (i.e. _pom.xml_). In _pom.xml_ add the following _distributionManagement_ information: {code:xml} 4.0.0 qt4j qt4j jar 1.0-SNAPSHOT QT4J ... mbari-repository MBARI Repository scp://oceana.shore.mbari.org/var/www/html/maven2 {code} Executing _mvn deploy_ will put your build jar at http://oceana.shore.mbari.org/maven2////-.jar. In the example here it would put it into [http://oceana.shore.mbari.org/maven2/qt4j/qt4j/1.0-SNAPSHOT/] h3. Publishing Maven generated web sites Maven can generate a web site for a default web site for you. You can view samples of the currently published projects at [http://oceana.shore.mbari.org/projects]. It's not very interesting, however, it is a very simple way to publish the javadoc, sources and auto-generated reports. To do so modify your _pom.xml_: {code:xml} ... org.apache.maven.plugins maven-jxr-plugin org.apache.maven.plugins maven-pmd-plugin 1.5 org.apache.maven.plugins maven-checkstyle-plugin ... oceana.shore.mbari.org scp://oceana.shore.mbari.org/var/www/html/projects/${project.name} {code} Then run _mvn javadoc:javadoc site:site site:deploy_. This will build the javadocs, create a site with some useful reports, then publish the site (using scp) to oceana in the correct location. h2. Using the MBARI repository from an [Ant|http://ant.apache.org] project Maven repositories can be used from Ant build scripts using [Ivy|http://incubator.apache.org/ivy/]. h3. Referencing the repository In the directory containing the ant build file, _build.xml_, create a file called _ivyconf.xml_. _ivyconf.xml_ tells Ivy where to look for dependencies. The contents of the file will look something like: {code:xml} {code} h3. Including a Dependency from the Repository In the directory containing _build.xml_, create a file called _ivy.xml_. _ivy.xml_ tells Ivy what dependencies to include in your build. Here's an example of it's contents: {code:xml} {code} h3. Using Ivy from Ant The code below will fetch Ivy for you. SO you do not need install any additional software in order to get you build to work. In your ant build file include the following: {code:xml} ... {code} Calling _ant ivy.install_ will fetch all the dependencies from the web and put them into the _lib_ directory of your project. ]]> 1040 10944923 $5000 Unit Cost | $30,000 | $ | | 5020-000 | Books/Subscriptions | $1,850 | $ | | 5060-000 | Dues, Membership, Licenses | $5,720 | $ | | 5130-000 | Outside Srvc - General | $7,500 | $ | | 5150-000 | Outside Srvc - Maint Contracts | $25,050 | $ | | 5300-000 | Supplies - Computer (Hardware) | $11,875 | $ | | 5310-000 | Supplies - Computer (Software) | $10,180 | $ | | 5320-000 | Supplies - Engineering Lab | $17,850 | $ | | 5330-000 | Supplies - Non-Capitalized Equipment | $13,100 | $ | | *Total* | | $123,125 | $ | {panel} {column} {section} ]]> 10912165 10944913 10912155 10944908 $5000 Unit Cost | $30,000 | $ | | 5020-000 | Books/Subscriptions | $1,850 | $ | | 5060-000 | Dues, Membership, Licenses | $5,720 | $ | | 5130-000 | Outside Srvc - General | $7,500 | $ | | 5150-000 | Outside Srvc - Maint Contracts | $25,050 | $ | | 5300-000 | Supplies - Computer (Hardware) | $11,875 | $ | | 5310-000 | Supplies - Computer (Software) | $10,180 | $ | | 5320-000 | Supplies - Engineering Lab | $17,850 | $ | | 5330-000 | Supplies - Non-Capitalized Equipment | $13,100 | $ | | *Total* | | $123,125 | $ | {panel} {column} {section} ]]> 10912150 18285238 18252485 15664188 Backup Database... ## Select Database-complete ## Click on Add... under Destination ## I typed in a file location of \\tempest\tempbox\kgomes\backups\crowd\db_backup as the file to backup to. ## I then created a new tar.gz file for the /opt/atlassian-crowd-1.5.1 installation and put in the same backup location on tempest. ## I then created a new tar.gz file for the crowd home directory /data/crowd and put in same tempest location # I copied the jtds-1.2.jar from /opt/atlassian-crowd-1.5.1/crowd-webapp/WEB-INF/lib to the same directory in the new installation # I then edited the /opt/atlassian-crowd-1.6/crowd-webapp/WEB-INF/classes/crowd-init.properties and pointed the crowd home directory to /data/crowd # I then copied the updated crowd client jar (/opt/atlassian-crowd-1.6/client/crowd-integrations-client-1.6.jar) to /opt/confluence/confluence/WEB-INF/lib and to /opt/jira/atlassian-jira/WEB-INF/lib (I removed the old ones too IMPORTANT!) # I downloaded the recommended crowd-ehcache.xml file from the instructions listed above and copied to the /opt/confluence/confluence/WEB-INF/classes and /opt/jira/atlassian-jira/WEB-INF/classes directories # Lastly I changed the /opt/crowd symbolic link to point to the new crowd installation, shut down confluence, jira, and crowd and restarted crowd. # After the successful start up of the three applications, I put all the backup files in Alfresco [here|https://alfresco.mbari.org/alfresco/webdav/Engineering/Tools/Collaboration%20Tools/Atlassian%20Crowd/Backups/2008_12_29]]]> 15631437 15664190 15631439 15664194 15631443 10944932 10912175 10944934 $5000 Unit Cost | $30,000 | $ | | 5020-000 | Books/Subscriptions | $1,850 | $ | | 5060-000 | Dues, Membership, Licenses | $5,720 | $ | | 5130-000 | Outside Srvc - General | $7,500 | $ | | 5150-000 | Outside Srvc - Maint Contracts | $25,050 | $ | | 5300-000 | Supplies - Computer (Hardware) | $11,875 | $ | | 5310-000 | Supplies - Computer (Software) | $10,180 | $ | | 5320-000 | Supplies - Engineering Lab | $17,850 | $ | | 5330-000 | Supplies - Non-Capitalized Equipment | $13,100 | $ | | *Total* | | $123,125 | $ | {panel}{column}{section}]]> 10912177 15664173 Add/Remove Software) # In the Search tab, enter erlang and select the 14B version of erlang. It will then install a bunch of dependencies (which is a good thing). # Go to the rabbitmq download page and grab the [RHEL version of the RPM|http://www.rabbitmq.com/releases/rabbitmq-server/v2.3.1/rabbitmq-server-2.3.1-1.noarch.rpm] # Use RPM or yum localinstall to install the rabbitmq RPM. # Once it is installed, it can be started using: {noformat} /sbin/service rabbitmq-server start {noformat} # It can be setup to start as a service by using: {noformat} chkconfig rabbitmq-server on {noformat} h5. Management Plugins # If you want the web management console, download the .ez files from the [plugins page|http://www.rabbitmq.com/plugins.html] and install them in the /usr/lib/rabbitmq/lib/rabbitmq_server-2.3.1/plugins and restart the server. {note:Plugins are picky} I found that while the core Rabbit server was somewhat immune to the version of Erlang, the plugins were not. {note} h5. LDAP Authentication # I was able to configure the RabbitMQ server to use our internal LDAP system in a chained configuration with the internal RabbitMQ authentication system. This allows you to use your MBARI logins on the RabbitMQ server. {note:title=One VERY icky caveat} Due to the way we have our Active Directory configured on site, the user DN's are in the form of *Lastname, Firstname*. While it works, that makes users have to login with a username like {noformat} Gomes\\, Kevin {noformat} It is ugly and hopefully we can address this in our Active Directory in the future. That said, the LDAP integration works well. {note} # Download the [ldap-auth plugin|http://www.rabbitmq.com/releases/plugins/v2.3.1/rabbitmq-auth-backend-ldap-2.3.1.ez] and put in the /usr/lib/rabbitmq/lib/rabbitmq_server-2.3.1/plugins directory. # Create (or add configuration) the /etc/rabbitmq/rabbitmq.config file with the following: {noformat} [ {rabbit, [ {auth_backends, [rabbit_auth_backend_ldap, rabbit_auth_backend_internal]} ] }, {rabbit_auth_backend_ldap, [ {servers, ["ldap.shore.mbari.org"]}, {user_dn_pattern, ["CN=${username},OU=Users,OU=AllUsers,DC=shore,DC=mbari,DC=org"]} ] } ]. {noformat} # Restart the server # With the LDAP authentication working, you can now control access permissions on resources (vhosts, exchanges, bindings, queues). See the following for more details: ## [RabbitMQ LDAP Authentication README|http://hg.rabbitmq.com/rabbitmq-auth-backend-ldap/file/default/README] ## [RabbitMQ LDAP Authorization README|http://hg.rabbitmq.com/rabbitmq-auth-backend-ldap/file/default/README-authorisation]]]> 15631422 18285228 18252472 10944862 10912102 19071245 "Downloads">"2.1 Releases">"2.1.1" # I then clicked on alfresco-enterprise-tomcat-2.1.1.zip to download the zip file. # Went to [http://customers.alfresco.com] (I was still logged in) # Went to "Company Home">"Downloads">"2.1 Releases">"2.1.1">"License Files" # I went ahead and downloaded all the "*.lic" files, but I think I only need enterprise-network-customer-unlimited.lic" # Logged out of Alfresco. # Since I suspect I will need a JDBC driver for SQLServer, I downloaded the jTDS-1.2.2 driver from the jtds web site (just Google jtds and go to the download section of the top google return). # I closed the Firefox browser. # I extracted the jtds-1.2.2.jar file from the jtds download # I downloaded and installed the JRockit 6 R27.4 JDK Microsoft Windows (x86 - 32 bit) from BEA's web site {note} After installing JRockit, make sure you set the JAVA_HOME environment variable to point to the installation of JRockit. For example, I went to the desktop, right clicked on the computer, did Properties, then clicked on the Advanced tab, then click on the environment variables button and then created a new system variable named JAVA_HOME and set to c:\bin\Java\jrockit-R27.4.0-jdk1.6.0_02 {note} # I ran the installer, changed the "Program Files" to "bin" in the installation directory for both the JDK and the JRE. I also chose to install the JRE as public. # Using Firefox, I downloaded the PHP 5.2.5 Windows Installer from php.net and installed it. Although I installed it, I did not integrate it with a web server as I want Alfresco to take port 80. I probably did not need to install PHP, but I thought I would anyway. (again, I changed install path from "Program Files" to "bin" # I also downloaded and installed OpenOffice and ran it once so I could get through the initial startup # I setup a Alfresco database on the server Solstice and granted the LAGOON\DB_Collaboration account to be the db_owner of the Alfresco database. # I unzipped the alfresco tomcat zip file to an alfresco directory in c:\bin # I then went to the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions directory for the customization of the server. ## I edited the custom-repository.properties file ### Changed the dir.root and dir.indexes to look like: {noformat} dir.root=//tornado.shore.mbari.org/Alfresco/alf_data dir.indexes=d:/alf_data/lucene-indexes {noformat} ### Commented out the db.* lines for the HSQL Connection (db.driver and db.url) ### Uncommented the db.* lines for MSSQL and changed to use the jTDS driver. They should look like: {noformat} db.driver=net.sourceforge.jtds.jdbc.Driver db.url=jdbc:jtds:sqlserver://solstice.shore.mbari.org/Alfresco;domain=SHORE;user=DB_Collaboration;password=XXXXXXXXX {noformat} ### I also added the following section to override the mail server settings {noformat} # Mail server configuration mail.host=mail.mbari.org mail.port=25 mail.username= mail.password= {noformat} ## Edited the custom-hibernate-dialect.properties file ### Commented out the HSQL Dialect ### Uncommented the MSSQL Dialect # I then installed the jtds-1.2.2.jar in the c:\bin\alfresco\tomcat\common\lib so that it will be on the classpath when Alfresco is started # Now this is not necessarily fun, but in order to really get it configured the way we want it, you need to pull the original .war file out, edit some stuff inside and re-create the .war. {note} This should all be done before starting Alfresco for the first time. {note} # Copy the c:\Alfresco\tomcat\webapps\alfresco.war file to your home directory. # Make a second copy so that you will always the original (I copied to alfresco.war.orig and moved it somewhere else. It is important to move it and have only the alfresco.war file in the directory because when you un-jar it, all the files go right where alfresco.war is.) # From a command line, un-jar the war file using: {noformat} jar -xvf alfresco.war {noformat} # This unpacks a lot of files and after it completes, move (or delete) the alfresco.war file from the directory. This needs to be done so it does not end up in the new .war file. # I wanted to change the "Company Home" that seems to be everywhere to something that says MBARI. ## Edited ./WEB-INF/classes/alfresco/messages/webclient.properties and changed company_home from 'Company Home' to 'MBARI' ## Edited ./WEB-INF/classes/alfresco/messages/webclient_en_US.properties and changed company_home from 'Company Home' to 'MBARI' ## I edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces.properties and changed the first two lines to read {noformat} spaces.company_home.name=MBARI spaces.company_home.description=The root space for MBARI {noformat} ## Edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces_en_US.properties and made the same changes as the previous step {tip} This took a bit to find all these, and to be honest, I am not sure which one actually made the change on the GUI, but I suspect it was the _en_US ones. {tip} # When users are imported via LDAP, user spaces get created automatically. In order to put them where I wanted them to go (instead of right in the Company Home), I edited the ./WEB-INF/classes/alfresco/authentication-services-context.xml file. In the file there is a bean with an name of personalHomeFolderProvider. There is a property name 'path' and I added {noformat} /${spaces.user_homes.childname} {noformat} to the end to try to get them to create the user spaces there instead of in the Company Home. The final bean XML looks like: {noformat} /${spaces.company_home.childname}/${spaces.user_homes.childname} ${spaces.store} false All All {noformat} # I wanted to change the logo that is used. I attached the replacement logo [CLT:here|^AlfrescoLogo32.png]. Copy this to ./images/logo and overwrite the one that is there. # In order to setup SSL for the application (will do that later), edit ./WEB-INF/web.xml and add the following {noformat} Login Pages /* CONFIDENTIAL {noformat} right before the ending tag at the bottom of the file. # Now in order to change the default behavior so that all content is versioned from the start, I edited the .\WEB-INF\classes\alfresco\model\contentModel.xml and searched for the content type definition block. {noformat} Content cm:cmobject true d:content false true false true {noformat} and added the following block right before the ending tag: {noformat} cm:versionable {noformat} so the final block looks like: {noformat} Content cm:cmobject true d:content false true false true cm:versionable {noformat} # Lastly, I wanted to redirect the log files to a separate disk. This is done because in the Windows hardening process, most of the disk space ends up on drive D: where alfresco does not live. The log files quickly fill up the small C: drive. To to this, I edited the .\WEB-INF\classes\log4j.properties and changed the log file appender location to point to a directory that was created on the D: drive called D:/alf_logs. # That takes care of all the changes to the WAR file. We can now put it back into .war form. # While you are in the directory you expanded the war file in, run ## jar cvfm alfresco.war META-INF\MANIFEST.MF . # You should now have an alfresco.war file in the directory. Move that back to the alfresco install and overwrite the existing one. # Most users like the details view, so I set the default to that by editing c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions\web-client-config-custom.xml and added: {noformat} details 20
20
20 {noformat} right before the closing tag. # Now in order to use MBARI accounts, NTLM authentication was turned on and then chained with the native Alfresco accounts so that we could have non-MBARI accounts on the Alfresco server. ## In order to enable NTLM and native Alfresco authentication, I had to edit two files. For simplicity I have just attached them here and they can be downloaded and installed in the extensions directory. ### The first file is the [CLT:ntlm-authentication-context.xml|^ntlm-authentication-context.xml] file. This configures and enables NTLM authentication. ### The next file was the [CLT:chaining-authentication-context.xml|^chaining-authentication-context.xml] file which enabled Alfresco authentication and chained it together with the NTLM authentication from the previous file. # Then in order to setup CIFS on the server, I edited the file-servers-custom.xml file to look like the attached [CLT:file-servers-custom.xml|^file-servers-custom.xml] file. # In order to grant certain accounts admin privs, I created a new custom-authority-services-context.xml in the same directory as the ldap-authentication-context.xml file and added {noformat} kgomes admin administrator {noformat} # In order for Alfresco to handle all port 80 traffic, I changed Tomcat so that it takes port 80 and SSL goes over port 443. So I edited the c:\Alfresco\tomcat\conf\server.xml file and changed the 8080 port to 80 and the 8443 port to 443 (the 443 change is done in two places). # Now I needed to setup the SSL for the web traffic. Cathy Sewell was instrumental in getting this working. She ordered a new certificate specifically for alfresco and put it in the c:\local\cert folder. Here are the instructions for what she did to get the certficate installed. {noformat} SSL certificate for server Alfresco - 1/2/08 C:\bin\Java\jrockit-R27.1.0-jre1.6.0_02\bin>keytool -genkey -alias tomcat -keyalg RSA -keystore tomcat.keystore What is your first and last name? [alfresco.mbari.org]: What is the name of your organizational unit? [IS]: What is the name of your organization? [MBARI]: What is the name of your City or Locality? [Moss Landing]: What is the name of your State or Province? [CD]: CA What is the two-letter country code for this unit? [US]: Is CN=alfresco.mbari.org, OU=IS, O=MBARI, L=Moss Landing, ST=CA, C=US correct? [no]: y Enter key password for (RETURN if same as keystore password): C:\bin\Java\jrockit-R27.4.0-jre1.6.0_02\bin>keytool -certreq -keyalg RSA -alias tomcat -file certreq.csr -keystore tomcat.keystore Enter keystore password: Generated certificate request file, certreq.csr, was submitted to SSL provider. Certificate provider sent certificate file (alfresco.mbari.org.crt), along with gd_bundle.crt, gd_cross_intermediate.crt, and gd_intermediate.crt. Additionally, I downloaded valicert_class2_root.cer from their website. These files were stored in c:\local\cert. The following commands were used to add them to the tomcat keystore: C:\bin\Java\jrockit-R27.4.0-jre1.6.0_02\bin>keytool -import -alias root -keystore tomcat.keystore -trustcacerts -file c:\local\cert\valicert_class2_root.cer Enter keystore password: Certificate already exists in system-wide CA keystore under alias Do you still want to add it to your own keystore? [no]: y Certificate was added to keystore C:\bin\Java\jrockit-R27.4.0-jre1.6.0_02\bin>keytool -import -alias cross -keystore tomcat.keystore -trustcacerts -file c:\local\cert\gd_cross_intermediate.crt Enter keystore password: Certificate was added to keystore C:\bin\Java\jrockit-R27.4.0-jre1.6.0_02\bin>keytool -import -alias intermed -keystore tomcat.keystore -trustcacerts -file c:\local\cert\gd_intermediate.crt Enter keystore password: Certificate was added to keystore C:\bin\Java\jrockit-R27.4.0-jre1.6.0_02\bin>keytool -import -alias tomcat -keystore tomcat.keystore -trustcacerts -file c:\local\cert\alfresco.mbari.org.crt Enter keystore password: Certificate reply was installed in keystore {noformat} # I edited the c:\bin\alfresco\tomcat\conf\server.xml file and uncommented the SSL section and edited to look like that shown below. {noformat} {noformat} # Since I was in the server.xml file, I went ahead and changed it so that the default webapp was alfresco so that you would get alfresco anytime you went to the base URL. I did this by adding: {noformat} {noformat} as the last line of the tag section (right before the closing tag). {note} You will also notice the Valve tag that I had to add to turn off proxy cache disabling so that IE clients would work correctly over SSL. Gotta love M$. {note} # I copied the enterprise-network-unlimited.lic file into the c:\Alfresco\tomcat\shared\classes\alfresco\extensions\license directory # Just to keep things clean, I edited the c:\bin\alfresco\alfresco.bat file and put 'rem' in front of the second JAVA_OPTS set as I am using Java 6. # Now after you run it for the first time and the database structure gets created, you can't restart it because you get: {noformat} java.sql.SQLException: Column names in each table must be unique. Column name 'ID_' in table 'JBPM_ACTION' is specified more than once. {noformat} Sigh, so in order to keep Alfresco from hurting itself, I had to turn off the schema updates. This is done by editing the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions\custom-repository.properties and adding the following: {noformat} db.schema.update=false {noformat} and then restarting alfresco. # To install Alfresco as a Windows Service use a command prompt and enter the following: {noformat} cd c:\bin\alfresco\tomcat\bin service.bat install alfresco tomcat5.exe //US//alfresco --DisplayName "Alfresco Server" tomcat5.exe //US//alfresco --JvmMs=512 --JvmMx=1024 --JvmSs=64 tomcat5.exe //US//alfresco --JavaHome=c:/bin/Java/jrockit-R27.4.0-jdk1.6.0_02 tomcat5.exe //US//alfresco --Environment ALF_HOME=c:/bin/alfresco/ tomcat5.exe //US//alfresco --Environment PATH=c:/bin/alfresco/bin;%PATH% tomcat5.exe //US//alfresco --StartPath c:/bin/alfresco --Startup auto {noformat} {note:title=JRockit Dump Size} As Alfresco was running, we noticed JRockit was occasionally creating these HUGE dump files that would fill up the hard drive. I turned this "feature" off by running tomcat5w.exe and in the popup GUI, I added a Java command line option: -XXdumpSize:none to turn off the dump files. {note} # To uninstall the service, at a later time, do the following: {noformat} cd c:\bin\alfresco\tomcat\bin service.bat uninstall alfresco {noformat} # To edit your service settings at any time: {noformat} cd c:\alfresco\tomcat\bin tomcat5w.exe //ES//alfresco {noformat} {warning} These next couple of steps had to be taken to install a patch from Alfresco for an issue with bulk uploads I was having. Essentially when file and path structures get really long and nasty, Alfresco was throwing an error and bailing out. This patch (two Java classes) fixed that issue. {warning} # Next, I downloaded the attached [CLT:JAR|^act2139.jar] file and copied it to the c:\bin\alfresco\tomcat\webapps\alfresco\WEB-INF\classes directory. # I shutdown Alfresco and then unjarred the file to install the new classes. They are: ## org/alfresco/filesys/smb/server/SMBSrvPacket.class ## org/alfresco/filesys/util/DataBuffer.class # I would assume since they do not overwrite anything, that this location is further up in the class loader and so it will load these new classes first. # I deleted the act2139.jar file and the META-INF directory that the unjarring process created. # In order to install certain modules (like the email listener), I had to get the Alfresco Module Manager from the customers.alfresco.com download site. I downloaded the alfresco-mmt-2.1.1.jar file locally so I could use it to install modules. # I then downloaded the email listener module from [http://forge.alfresco.com/projects/email-listener/]. It came as a zip file, so I unzipped it and it created a folder with the appropriate emailListener.amp in it. # Make another backup copy of the alfresco.war file and put somewhere in case you want to roll this back. # Open a command prompt windows and cd to the location where the Alfresco Module Manager jar is. # Run the following: {noformat} java -jar alfresco-mmt-2.1.1.jar path_to_emailListener.amp path_to_alfresco.war {noformat} So for me this looked like: {noformat} java -jar alfresco-mmt-2.1.1.jar .\email-listener_2.1RC2\emailListener.amp c:\bin\alfresco\tomcat\webapps\alfresco.war {noformat} # You should be able to verify the install by running: {noformat} java -jar alfresco-mmt-2.1.1.jar list c:\bin\alfresco\tomcat\webapps\alfresco.war {noformat} and you should see something like: {noformat} Module 'emailListener' installed in 'c:\bin\alfresco\tomcat\webapps\alfresco.war' - Title: EmailListener - Version: 2.1 - Install Date: Fri Dec 07 08:43:10 PST 2007 - Desription: EmailListener Module {noformat} # Finally, to start the service, just go into your Windows Service control panel and locate the service that is now named 'Alfresco Server'. You can start and stop Alfresco from this control panel. {note:title=Database Migrations} For the alfresco.mbari.org installation, we moved the back end database a couple of times for performance and management reasons. The first move was to backup the database from solstice.shore.mbari.org to the SQL 2005 server called capricorn. We did this because 2005 was the officially supported DB and we were experiencing some strange issues. It ran fine on capricorn for a long while, but for licensing reasons, we wanted to consolidate the DB onto a newer SQL Server 2008 machine called equinox.shore.mbari.org. In order to point Alfresco at a different database, I edited the custom-repository.properties file located in the {noformat}c:\bin\alfresco\tomcat\shared\classes\alfresco\extension{noformat} directory. Here is what the final result looked like with the previous two configurations commented out. {noformat} # # SQLServer connection (requires jtds-1.2.jar or equivalent - http://jtds.sourceforge.net/) # db.driver=net.sourceforge.jtds.jdbc.Driver # DB on Solstice #db.url=jdbc:jtds:sqlserver://solstice.shore.mbari.org/Alfresco;domain=SHORE;user=DB_Collaboration;password=T00l%W#Use # DB on capricorn #db.url=jdbc:jtds:sqlserver://capricorn.shore.mbari.org/Alfresco;domain=SHORE;user=DB_Collaboration;password=T00l%W#Use # DB on equinox db.url=jdbc:jtds:sqlserver://equinox.shore.mbari.org/Alfresco;domain=SHORE;user=DB_Collaboration;password=T00l%W#Use {noformat} I also downloaded the most recent jtds driver (1.2.5) and installed it in the c:\bin\alfresco\tomcat\common\lib directory and removed the old version. {note} h1. Content Migration Now, in order to migrate content from old alfresco and normal file structures, I did the following: h3. For content already in alfresco: # Navigate to the space whose contents you want to migrate. For example, let's say I want to migrate the stuff from my personal space. I would navigate (using the WebUI) to the /MBARI/User Homes/kgomes space. You should see the contents of the kgomes folder from this view. # Click on 'More actions->View Details'. # On the right hand side, click on 'Export'. # For package name, I usually enter the space name followed by '_export', but it doesn't really matter. # Click on the link that says 'Click here to select the destination' and select somewhere that you will be able to download the .acp file from. # Select 'Current Space'. # Select 'Include Children'. # Uncheck 'Include this space' unless you have content (documents) in this specific folder (anything other than folders) that you want to migrate. This is a bit tricky, but there are two ways to do this. If you want to have the top level folder created, use the 'Include this space' and that will create the top level folder. Otherwise, if will expand into the folder in which you import the .acp file into. This is important in cases where the folder has already been created for you (like with user homes) and you have to migrate content into that folder. If you have the option to create the top level directory, by all means do so. # Uncheck 'Export in background' so you can force it to happen and you know when it is complete.]]> 19038479 10944861 10912101 19071244 19038478 19071243 19038477 10944859 10912099 19071249 19038483 10944864 10912104 19071247 19038481 3179536 "Downloads">"2.1 Releases">"2.1.1" # I then clicked on alfresco-enterprise-tomcat-2.1.1.zip to download the zip file. # Went to [http://customers.alfresco.com] (I was still logged in) # Went to "Company Home">"Downloads">"2.1 Releases">"2.1.1">"License Files" # I went ahead and downloaded all the "*.lic" files, but I think I only need enterprise-network-customer-unlimited.lic" # Logged out of Alfresco. # Since I suspect I will need a JDBC driver for SQLServer, I downloaded the jTDS-1.2.2 driver from the jtds web site (just Google jtds and go to the download section of the top google return). # I closed the Firefox browser. # I extracted the jtds-1.2.2.jar file from the jtds download # I downloaded and installed the JRockit 6 R27.4 JDK Microsoft Windows (x86 - 32 bit) from BEA's web site {note} After installing JRockit, make sure you set the JAVA_HOME environment variable to point to the installation of JRockit. For example, I went to the desktop, right clicked on the computer, did Properties, then clicked on the Advanced tab, then click on the environment variables button and then created a new system variable named JAVA_HOME and set to c:\bin\Java\jrockit-R27.4.0-jdk1.6.0_02 {note} # I ran the installer, changed the "Program Files" to "bin" in the installation directory for both the JDK and the JRE. I also chose to install the JRE as public. # Using Firefox, I downloaded the PHP 5.2.5 Windows Installer from php.net and installed it. Although I installed it, I did not integrate it with a web server as I want Alfresco to take port 80. I probably did not need to install PHP, but I thought I would anyway. (again, I changed install path from "Program Files" to "bin" # I also downloaded and installed OpenOffice and ran it once so I could get through the initial startup # I setup a Alfresco database on the server Solstice and granted the LAGOON\DB_Collaboration account to be the db_owner of the Alfresco database. # I unzipped the alfresco tomcat zip file to an alfresco directory in c:\bin # I then went to the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions directory for the customization of the server. ## I edited the custom-repository.properties file ### Changed the dir.root and dir.indexes to look like: {noformat} dir.root=//tornado.shore.mbari.org/Alfresco/alf_data dir.indexes=d:/alf_data/lucene-indexes {noformat} ### Commented out the db.* lines for the HSQL Connection (db.driver and db.url) ### Uncommented the db.* lines for MSSQL and changed to use the jTDS driver. They should look like: {noformat} db.driver=net.sourceforge.jtds.jdbc.Driver db.url=jdbc:jtds:sqlserver://solstice.shore.mbari.org/Alfresco;domain=SHORE;user=DB_Collaboration;password=XXXXXXXXX {noformat} ### I also added the following section to override the mail server settings {noformat} # Mail server configuration mail.host=mail.mbari.org mail.port=25 mail.username= mail.password= {noformat} ## Edited the custom-hibernate-dialect.properties file ### Commented out the HSQL Dialect ### Uncommented the MSSQL Dialect # I then installed the jtds-1.2.2.jar in the c:\bin\alfresco\tomcat\common\lib so that it will be on the classpath when Alfresco is started # Now this is not necessarily fun, but in order to really get it configured the way we want it, you need to pull the original .war file out, edit some stuff inside and re-create the .war. {note} This should all be done before starting Alfresco for the first time. {note} # Copy the c:\Alfresco\tomcat\webapps\alfresco.war file to your home directory. # Make a second copy so that you will always the original (I copied to alfresco.war.orig and moved it somewhere else. It is important to move it and have only the alfresco.war file in the directory because when you un-jar it, all the files go right where alfresco.war is.) # From a command line, un-jar the war file using: {noformat} jar -xvf alfresco.war {noformat} # This unpacks a lot of files and after it completes, move (or delete) the alfresco.war file from the directory. This needs to be done so it does not end up in the new .war file. # I wanted to change the "Company Home" that seems to be everywhere to something that says MBARI. ## Edited ./WEB-INF/classes/alfresco/messages/webclient.properties and changed company_home from 'Company Home' to 'MBARI' ## Edited ./WEB-INF/classes/alfresco/messages/webclient_en_US.properties and changed company_home from 'Company Home' to 'MBARI' ## I edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces.properties and changed the first two lines to read {noformat} spaces.company_home.name=MBARI spaces.company_home.description=The root space for MBARI {noformat} ## Edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces_en_US.properties and made the same changes as the previous step {tip} This took a bit to find all these, and to be honest, I am not sure which one actually made the change on the GUI, but I suspect it was the _en_US ones. {tip} # When users are imported via LDAP, user spaces get created automatically. In order to put them where I wanted them to go (instead of right in the Company Home), I edited the ./WEB-INF/classes/alfresco/authentication-services-context.xml file. In the file there is a bean with an name of personalHomeFolderProvider. There is a property name 'path' and I added {noformat} /${spaces.user_homes.childname} {noformat} to the end to try to get them to create the user spaces there instead of in the Company Home. The final bean XML looks like: {noformat} /${spaces.company_home.childname}/${spaces.user_homes.childname} ${spaces.store} false All All {noformat} # I wanted to change the logo that is used. I attached the replacement logo [here|^AlfrescoLogo32.png]. Copy this to ./images/logo and overwrite the one that is there. # In order to setup SSL for the application (will do that later), edit ./WEB-INF/web.xml and add the following {noformat} Login Pages /* CONFIDENTIAL {noformat} right before the ending tag at the bottom of the file. # Now in order to change the default behavior so that all content is versioned from the start, I edited the .\WEB-INF\classes\alfresco\model\contentModel.xml and searched for the content type definition block. {noformat} Content cm:cmobject true d:content false true false true {noformat} and added the following block right before the ending tag: {noformat} cm:versionable {noformat} so the final block looks like: {noformat} Content cm:cmobject true d:content false true false true cm:versionable {noformat} # That takes care of all the changes to the WAR file. We can now put it back into .war form. # While you are in the directory you expanded the war file in, run ## jar cvfm alfresco.war META-INF\MANIFEST.MF . # You should now have an alfresco.war file in the directory. Move that back to the alfresco install and overwrite the existing one. # Most users like the details view, so I set the default to that by editing c:\Alfresco\tomcat\shared\classes\alfresco\extensions/web-client-config-custom.xml and added: {noformat} details 20
20
20 {noformat} right before the closing tag. # Now in order to use MBARI accounts, NTLM authentication was turned on and then chained with the native Alfresco accounts so that we could have non-MBARI accounts on the Alfresco server. ## In order to enable NTLM and native Alfresco authentication, I had to edit two files. For simplicity I have just attached them here and they can be downloaded and installed in the extensions directory. ### The first file is the [ntlm-authentication-context.xml|^ntlm-authentication-context.xml] file. This configures and enables NTLM authentication. ### The next file was the [chaining-authentication-context.xml|^chaining-authentication-context.xml] file which enabled Alfresco authentication and chained it together with the NTLM authentication from the previous file. # Then in order to setup CIFS on the server, I edited the file-servers-custom.xml file to look like the attached [file-servers-custom.xml|^file-servers-custom.xml] file. # In order to grant certain accounts admin privs, I created a new custom-authority-services-context.xml in the same directory as the ldap-authentication-context.xml file and added {noformat} kgomes admin administrator {noformat} # In order for Alfresco to handle all port 80 traffic, I changed Tomcat so that it takes port 80 and SSL goes over port 443. So I edited the c:\Alfresco\tomcat\conf\server.xml file and changed the 8080 port to 80 and the 8443 port to 443 (the 443 change is done in two places). # Now I needed to setup the SSL for the web traffic. Cathy Sewell was instrumental in getting this working. She ordered a new certificate specifically for alfresco and put it in the c:\local\cert folder. Here are the instructions for what she did to get the certficate installed. {noformat} SSL certificate for server Alfresco - 1/2/08 C:\bin\Java\jrockit-R27.1.0-jre1.6.0_02\bin>keytool -genkey -alias tomcat -keyalg RSA -keystore tomcat.keystore What is your first and last name? [alfresco.mbari.org]: What is the name of your organizational unit? [IS]: What is the name of your organization? [MBARI]: What is the name of your City or Locality? [Moss Landing]: What is the name of your State or Province? [CD]: CA What is the two-letter country code for this unit? [US]: Is CN=alfresco.mbari.org, OU=IS, O=MBARI, L=Moss Landing, ST=CA, C=US correct? [no]: y Enter key password for (RETURN if same as keystore password): C:\bin\Java\jrockit-R27.4.0-jre1.6.0_02\bin>keytool -certreq -keyalg RSA -alias tomcat -file certreq.csr -keystore tomcat.keystore Enter keystore password: Generated certificate request file, certreq.csr, was submitted to SSL provider. Certificate provider sent certificate file (alfresco.mbari.org.crt), along with gd_bundle.crt, gd_cross_intermediate.crt, and gd_intermediate.crt. Additionally, I downloaded valicert_class2_root.cer from their website. These files were stored in c:\local\cert. The following commands were used to add them to the tomcat keystore: C:\bin\Java\jrockit-R27.4.0-jre1.6.0_02\bin>keytool -import -alias root -keystore tomcat.keystore -trustcacerts -file c:\local\cert\valicert_class2_root.cer Enter keystore password: Certificate already exists in system-wide CA keystore under alias Do you still want to add it to your own keystore? [no]: y Certificate was added to keystore C:\bin\Java\jrockit-R27.4.0-jre1.6.0_02\bin>keytool -import -alias cross -keystore tomcat.keystore -trustcacerts -file c:\local\cert\gd_cross_intermediate.crt Enter keystore password: Certificate was added to keystore C:\bin\Java\jrockit-R27.4.0-jre1.6.0_02\bin>keytool -import -alias intermed -keystore tomcat.keystore -trustcacerts -file c:\local\cert\gd_intermediate.crt Enter keystore password: Certificate was added to keystore C:\bin\Java\jrockit-R27.4.0-jre1.6.0_02\bin>keytool -import -alias tomcat -keystore tomcat.keystore -trustcacerts -file c:\local\cert\alfresco.mbari.org.crt Enter keystore password: Certificate reply was installed in keystore {noformat} # I edited the c:\bin\alfresco\tomcat\conf\server.xml file and uncommented the SSL section and edited to look like that shown below. {noformat} {noformat} # Since I was in the server.xml file, I went ahead and changed it so that the default webapp was alfresco so that you would get alfresco anytime you went to the base URL. I did this by adding: {noformat} {noformat} as the last line of the tag section (right before the closing tag). {note} You will also notice the Valve tag that I had to add to turn off proxy cache disabling so that IE clients would work correctly over SSL. Gotta love M$. {note} # I copied the enterprise-network-unlimited.lic file into the c:\Alfresco\tomcat\shared\classes\alfresco\extensions\license directory # Just to keep things clean, I edited the c:\bin\alfresco\alfresco.bat file and put 'rem' in front of the second JAVA_OPTS set as I am using Java 6. # Now after you run it for the first time and the database structure gets created, you can't restart it because you get: {noformat} java.sql.SQLException: Column names in each table must be unique. Column name 'ID_' in table 'JBPM_ACTION' is specified more than once. {noformat} Sigh, so in order to keep Alfresco from hurting itself, I had to turn off the schema updates. This is done by editing the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions\custom-repository.properties and adding the following: {noformat} db.schema.update=false {noformat} and then restarting alfresco. # To install Alfresco as a Windows Service use a command prompt and enter the following: {noformat} cd c:\bin\alfresco\tomcat\bin service.bat install alfresco tomcat5.exe //US//alfresco --DisplayName "Alfresco Server" tomcat5.exe //US//alfresco --JvmMs=512 --JvmMx=1024 --JvmSs=64 tomcat5.exe //US//alfresco --JavaHome=c:/bin/Java/jrockit-R27.4.0-jdk1.6.0_02 tomcat5.exe //US//alfresco --Environment ALF_HOME=c:/bin/alfresco/ tomcat5.exe //US//alfresco --Environment PATH=c:/bin/alfresco/bin;%PATH% tomcat5.exe //US//alfresco --StartPath c:/bin/alfresco --Startup auto {noformat} # To uninstall the service, at a later time, do the following: {noformat} cd c:\bin\alfresco\tomcat\bin service.bat uninstall alfresco {noformat} # To edit your service settings at any time: {noformat} cd c:\alfresco\tomcat\bin tomcat5w.exe //ES//alfresco {noformat} # In order to install certain modules (like the email listener), I had to get the Alfresco Module Manager from the customers.alfresco.com download site. I downloaded the alfresco-mmt-2.1.1.jar file locally so I could use it to install modules. # I then downloaded the email listener module from [http://forge.alfresco.com/projects/email-listener/]. It came as a zip file, so I unzipped it and it created a folder with the appropriate emailListener.amp in it. # Make another backup copy of the alfresco.war file and put somewhere in case you want to roll this back. # Open a command prompt windows and cd to the location where the Alfresco Module Manager jar is. # Run the following: {noformat} java -jar alfresco-mmt-2.1.1.jar path_to_emailListener.amp path_to_alfresco.war {noformat} So for me this looked like: {noformat} java -jar alfresco-mmt-2.1.1.jar .\email-listener_2.1RC2\emailListener.amp c:\bin\alfresco\tomcat\webapps\alfresco.war {noformat} # You should be able to verify the install by running: {noformat} java -jar alfresco-mmt-2.1.1.jar list c:\bin\alfresco\tomcat\webapps\alfresco.war {noformat} and you should see something like: {noformat} Module 'emailListener' installed in 'c:\bin\alfresco\tomcat\webapps\alfresco.war' - Title: EmailListener - Version: 2.1 - Install Date: Fri Dec 07 08:43:10 PST 2007 - Desription: EmailListener Module {noformat} # Finally, to start the service, just go into your Windows Service control panel and locate the service that is now named 'Alfresco Server'. You can start and stop Alfresco from this control panel. h1. Content Migration Now, in order to migrate content from old alfresco and normal file structures, I did the following: h3. For content already in alfresco: # Navigate to the space whose contents you want to migrate. For example, let's say I want to migrate the stuff from my personal space. I would navigate (using the WebUI) to the /MBARI/User Homes/kgomes space. You should see the contents of the kgomes folder from this view. # Click on 'More actions->View Details'. # On the right hand side, click on 'Export'. # For package name, I usually enter the space name followed by '_export', but it doesn't really matter. # Click on the link that says 'Click here to select the destination' and select somewhere that you will be able to download the .acp file from. # Select 'Current Space'. # Select 'Include Children'. # Uncheck 'Include this space' unless you have content (documents) in this specific folder (anything other than folders) that you want to migrate. This is a bit tricky, but there are two ways to do this. If you want to have the top level folder created, use the 'Include this space' and that will create the top level folder. Otherwise, if will expand into the folder in which you import the .acp file into. This is important in cases where the folder has already been created for you (like with user homes) and you have to migrate content into that folder. If you have the option to create the top level directory, by all means do so. # Uncheck 'Export in background' so you can force it to happen and you know when it is complete.]]> 3114053 10944846 10912086 3179535 'Downloads'>'2.1 Releases'>'2.1.1' # I changed to the 'Details View', made 40 items visible, and then downloaded 'alfresco-enterprise-tomcat-2.1.1.zip' file. # I then unzipped the downloaded file to c:\bin which created an alfresco-enterprise-tomcat-2.1.1 folder in c:\bin. # I renamed the alfresco-enterprise-tomcat-2.1.1 folder to simply alfresco. # I then went back to the web browser and went to 'Company Home'>'Downloads'>'2.1 Releases'>'2.1.1'>'License Files' # I am not sure if I can do this with our agreement, but I downloaded the 'enterprise-network-customer-unlimited.lic' file. {note} I did get approval from Joe Van De Graaff at Alfresco to use the license for a test installation to get us through this issue. {note} # I logged out of the Alfresco customer web site. # I Googled on jTDS to find the jTDS JDBC driver and downloaded the jtds-1.2.2-dist.zip file from the website. # Using Windows Explorer, I could just open the jTDS zip file and copy the jtds-1.2.2.jar file. # I then pasted it in the directory c:\bin\alfresco\tomcat\common\lib directory. # I created a c:\data\alf_data directory where the alfresco data will be stored. This is different from the production installation in that the content is stored on a network appliance (\\tornado.shore.mbari.org\alfresco). # I installed a copy of SQL Server 2005 locally to use for the database to back the Alfresco test install. {note} In order to do this without warnings, I had to go back and install IIS through the Add/Remove Programs Control Panel. {note} ## I used the Local System account to run services and only used Windows Authentication logins ## I installed all the service packs and the SQL Server Management Studio product to admin DBs. # In SQL Server, I added the SHORE\DB_Collaboration accounts to the logins. # I created a new database named alfresco-test and made SHORE\DB_Collaboration the owner. # I then went to the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions directory for the customization of the server. ## I edited the custom-repository.properties file ### Changed the dir.root and dir.indexes to look like: {noformat} dir.root=c:/data/alf_data dir.indexes=c:/data/alf_data/lucene-indexes {noformat} ### Commented out the db.* lines for the HSQL Connection (db.driver and db.url) ### Uncommented the db.* lines for MSSQL and changed to use the jTDS driver. They should look like (except the password should be the right one): {noformat} db.driver=net.sourceforge.jtds.jdbc.Driver db.url=jdbc:jtds:sqlserver://localhost/alfresco-test;domain=SHORE;user=DB_Collaboration;password=XXXXXXXXX {noformat} ### I also added the following section to override the mail server settings {noformat} # Mail server configuration mail.host=mail.mbari.org mail.port=25 mail.username= mail.password= {noformat} ## Edited the custom-hibernate-dialect.properties file ### Commented out the HSQL Dialect ### Uncommented the MSSQL Dialect # Now this is not necessarily fun, but in order to really get it configured the way we want it, you need to pull the original .war file out, edit some stuff inside and re-create the .war. {note} This should all be done before starting Alfresco for the first time. {note} # Copy the c:\bin\alfresco\tomcat\webapps\alfresco.war file to your home directory. # Make a second copy so that you will always the original (I copied to alfresco.war.orig and moved it somewhere else. It is important to move it and have only the alfresco.war file in the directory because when you un-jar it, all the files go right where alfresco.war is.) # From a command line, un-jar the war file using: {noformat} jar -xvf alfresco.war {noformat} # This unpacks a lot of files and after it completes, move (or delete) the alfresco.war file from the directory. This needs to be done so it does not end up in the new .war file. # I wanted to change the "Company Home" that seems to be everywhere to something that says MBARI. ## Edited ./WEB-INF/classes/alfresco/messages/webclient.properties and changed company_home from 'Company Home' to 'MBARI Test' ## Edited ./WEB-INF/classes/alfresco/messages/webclient_en_US.properties and changed company_home from 'Company Home' to 'MBARI Test' ## I edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces.properties and changed the first two lines to read {noformat} spaces.company_home.name=MBARI Test spaces.company_home.description=The root of MBARIs Test Alfresco Server {noformat} ## Edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces_en_US.properties and made the same changes as the previous step {tip} This took a bit to find all these, and to be honest, I am not sure which one actually made the change on the GUI, but I suspect it was the _en_US ones. {tip} # When users are imported via LDAP, user spaces get created automatically. In order to put them where I wanted them to go (instead of right in the Company Home), I edited the ./WEB-INF/classes/alfresco/authentication-services-context.xml file. In the file there is a bean with an name of personalHomeFolderProvider. There is a property name 'path' and I added {noformat} /${spaces.user_homes.childname} {noformat} to the end to try to get them to create the user spaces there instead of in the Company Home. The final bean XML looks like: {noformat} /${spaces.company_home.childname}/${spaces.user_homes.childname} ${spaces.store} false All All {noformat} # I wanted to change the logo that is used. I attached the replacement [Alfresco Logo|CLT:Installation Notes^AlfrescoLogo32.png]. Copy this to ./images/logo and overwrite the one that is there. {warning} Note that I did NOT setup SSL for this installation so if I will need to come back and do that if I want truly parallel systems {warning} # Now in order to change the default behavior so that all content is versioned from the start, I edited the .\WEB-INF\classes\alfresco\model\contentModel.xml and searched for the content type definition block. {noformat} Content cm:cmobject true d:content false true false true {noformat} and added the following block right before the ending tag: {noformat} cm:versionable {noformat} so the final block looks like: {noformat} Content cm:cmobject true d:content false true false true cm:versionable {noformat} # That takes care of all the changes to the WAR file. We can now put it back into .war form. # While you are in the directory you expanded the war file in, run ## jar cvfm alfresco.war META-INF\MANIFEST.MF . # You should now have an alfresco.war file in the directory. Move that back to the alfresco install and overwrite the existing one. # Most users like the details view, so I set the default to that by editing c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions\web-client-config-custom.xml and added: {noformat} details 20
20
20 {noformat} right before the closing tag. # Now in order to use MBARI accounts, NTLM authentication was turned on and then chained with the native Alfresco accounts so that we could have non-MBARI accounts on the Alfresco server. ## For simplicity sake, I have attached the files and you can simply download and install them in the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions directory. {note} Before doing these next steps, rename the file-servers-custom.xml file to file-servers-custom.xml.orig so you will have a backup of the original {note} ### First install the [NTLM Configuration XML File|^ntlm-authentication-context.xml] ### Next install the [Authentication Chaining Configuration File|^chaining-authentication-context.xml] ### Next install the [CIFS configuration|^file-servers-custom.xml] file and over-write the existing one. {warning} In the CIFS configuration file, make sure you change the tag to reflect a unique name on the network. {warning} ### Next install the [customized authority configuration|^custom-authority-services-context.xml] file (this gives administrative privs to certain accounts). {warning} Note that I did NOT change the server to take over port 80 traffic as the SQL Server install seemed to want IIS which is currently using port 80 {warning} # Now in order for the alfresco web application to be the default, I edit the c:\bin\alfresco\tomcat\conf\server.xml file and added: {noformat} {noformat} as the last line of the tag section (right before the closing tag). {note} You will also notice the Valve tag that I had to add to turn off proxy cache disabling so that IE clients would work correctly over SSL. Gotta love M$. {note} # Just to keep things clean, I edited the c:\bin\alfresco\alfresco.bat file and put 'rem' in front of the second JAVA_OPTS set as I am using Java 6. # You are now actually ready to start alfresco for the first time! Open a command window and cd over the to c:\bin\alfresco directory and then type: {noformat} alf_start.bat {noformat} # After a long time (took several minutes on a regular PC), look at the alfresco.log file in the c:\bin\alfresco directory and see if it looks like everything started OK, you can also check the database to see if the tables have been created in the alfresco-test database. You should also be able to go to http://alfresco-test.shore.mbari.org:8080 and see the alfresco web application. # Now from the command window where you ran alf_start.bat, run alf_stop.bat to shut the server down. Check the alfresco.log file to see if anything weird happened. If not, try restarting it with alf_start.bat again and look at the alfresco.log file. Sometimes, you can't restart it because you get: {noformat} java.sql.SQLException: Column names in each table must be unique. Column name 'ID_' in table 'JBPM_ACTION' is specified more than once. {noformat} Sigh, so in order to keep Alfresco from hurting itself, you might have to turn off the schema updates. This is done by editing the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions\custom-repository.properties and adding the following: {noformat} db.schema.update=false {noformat} and then restarting alfresco.]]> 3114052 3179531 'Downloads'>'2.1 Releases'>'2.1.1' # I changed to the 'Details View', made 40 items visible, and then downloaded 'alfresco-enterprise-tomcat-2.1.1.zip' file. # I then unzipped the downloaded file to c:\bin which created an alfresco-enterprise-tomcat-2.1.1 folder in c:\bin. # I renamed the alfresco-enterprise-tomcat-2.1.1 folder to simply alfresco. # I then went back to the web browser and went to 'Company Home'>'Downloads'>'2.1 Releases'>'2.1.1'>'License Files' # I am not sure if I can do this with our agreement, but I downloaded the 'enterprise-network-customer-unlimited.lic' file. {note} I did get approval from Joe Van De Graaff at Alfresco to use the license for a test installation to get us through this issue. {note} # I logged out of the Alfresco customer web site. # I Googled on jTDS to find the jTDS JDBC driver and downloaded the jtds-1.2.2-dist.zip file from the website. # Using Windows Explorer, I could just open the jTDS zip file and copy the jtds-1.2.2.jar file. # I then pasted it in the directory c:\bin\alfresco\tomcat\common\lib directory. # I created a c:\data\alf_data directory where the alfresco data will be stored. This is different from the production installation in that the content is stored on a network appliance (\\tornado.shore.mbari.org\alfresco). # I installed a copy of SQL Server 2005 locally to use for the database to back the Alfresco test install. {note} In order to do this without warnings, I had to go back and install IIS through the Add/Remove Programs Control Panel. {note} ## I used the Local System account to run services and only used Windows Authentication logins ## I installed all the service packs and the SQL Server Management Studio product to admin DBs. # In SQL Server, I added the SHORE\DB_Collaboration accounts to the logins. # I created a new database named alfresco-test and made SHORE\DB_Collaboration the owner. # I then went to the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions directory for the customization of the server. ## I edited the custom-repository.properties file ### Changed the dir.root and dir.indexes to look like: {noformat} dir.root=c:/data/alf_data dir.indexes=c:/data/alf_data/lucene-indexes {noformat} ### Commented out the db.* lines for the HSQL Connection (db.driver and db.url) ### Uncommented the db.* lines for MSSQL and changed to use the jTDS driver. They should look like (except the password should be the right one): {noformat} db.driver=net.sourceforge.jtds.jdbc.Driver db.url=jdbc:jtds:sqlserver://localhost/alfresco-test;domain=SHORE;user=DB_Collaboration;password=XXXXXXXXX {noformat} ### I also added the following section to override the mail server settings {noformat} # Mail server configuration mail.host=mail.mbari.org mail.port=25 mail.username= mail.password= {noformat} ## Edited the custom-hibernate-dialect.properties file ### Commented out the HSQL Dialect ### Uncommented the MSSQL Dialect # Now this is not necessarily fun, but in order to really get it configured the way we want it, you need to pull the original .war file out, edit some stuff inside and re-create the .war. {note} This should all be done before starting Alfresco for the first time. {note} # Copy the c:\bin\alfresco\tomcat\webapps\alfresco.war file to your home directory. # Make a second copy so that you will always the original (I copied to alfresco.war.orig and moved it somewhere else. It is important to move it and have only the alfresco.war file in the directory because when you un-jar it, all the files go right where alfresco.war is.) # From a command line, un-jar the war file using: {noformat} jar -xvf alfresco.war {noformat} # This unpacks a lot of files and after it completes, move (or delete) the alfresco.war file from the directory. This needs to be done so it does not end up in the new .war file. # I wanted to change the "Company Home" that seems to be everywhere to something that says MBARI. ## Edited ./WEB-INF/classes/alfresco/messages/webclient.properties and changed company_home from 'Company Home' to 'MBARI Test' ## Edited ./WEB-INF/classes/alfresco/messages/webclient_en_US.properties and changed company_home from 'Company Home' to 'MBARI Test' ## I edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces.properties and changed the first two lines to read {noformat} spaces.company_home.name=MBARI Test spaces.company_home.description=The root of MBARIs Test Alfresco Server {noformat} ## Edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces_en_US.properties and made the same changes as the previous step {tip} This took a bit to find all these, and to be honest, I am not sure which one actually made the change on the GUI, but I suspect it was the _en_US ones. {tip} # When users are imported via LDAP, user spaces get created automatically. In order to put them where I wanted them to go (instead of right in the Company Home), I edited the ./WEB-INF/classes/alfresco/authentication-services-context.xml file. In the file there is a bean with an name of personalHomeFolderProvider. There is a property name 'path' and I added {noformat} /${spaces.user_homes.childname} {noformat} to the end to try to get them to create the user spaces there instead of in the Company Home. The final bean XML looks like: {noformat} /${spaces.company_home.childname}/${spaces.user_homes.childname} ${spaces.store} false All All {noformat} # I wanted to change the logo that is used. I attached the replacement [Alfresco Logo|CLT:Installation Notes^AlfrescoLogo32.png]. Copy this to ./images/logo and overwrite the one that is there. {warning} Note that I did NOT setup SSL for this installation so if I will need to come back and do that if I want truly parallel systems {warning} # Now in order to change the default behavior so that all content is versioned from the start, I edited the .\WEB-INF\classes\alfresco\model\contentModel.xml and searched for the content type definition block. {noformat} Content cm:cmobject true d:content false true false true {noformat} and added the following block right before the ending tag: {noformat} cm:versionable {noformat} so the final block looks like: {noformat} Content cm:cmobject true d:content false true false true cm:versionable {noformat} # That takes care of all the changes to the WAR file. We can now put it back into .war form. # While you are in the directory you expanded the war file in, run ## jar cvfm alfresco.war META-INF\MANIFEST.MF . # You should now have an alfresco.war file in the directory. Move that back to the alfresco install and overwrite the existing one. # Most users like the details view, so I set the default to that by editing c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions\web-client-config-custom.xml and added: {noformat} details 20
20
20 {noformat} right before the closing tag. # Now in order to use MBARI accounts, NTLM authentication was turned on and then chained with the native Alfresco accounts so that we could have non-MBARI accounts on the Alfresco server. ## For simplicity sake, I have attached the files and you can simply download and install them in the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions directory. {note} Before doing these next steps, rename the file-servers-custom.xml file to file-servers-custom.xml.orig so you will have a backup of the original {note} ### First install the [NTLM Configuration XML File|^ntlm-authentication-context.xml] ### Next install the [Authentication Chaining Configuration File|^chaining-authentication-context.xml] ### Next install the [CIFS configuration|^file-servers-custom.xml] file and over-write the existing one. {warning} In the CIFS configuration file, make sure you change the tag to reflect a unique name on the network. {warning} ### Next install the [customized authority configuration|^custom-authority-services-context.xml] file (this gives administrative privs to certain accounts). {warning} Note that I did NOT change the server to take over port 80 traffic as the SQL Server install seemed to want IIS which is currently using port 80 {warning} # Now in order for the alfresco web application to be the default, I edit the c:\bin\alfresco\tomcat\conf\server.xml file and added: {noformat} {noformat} as the last line of the tag section (right before the closing tag). {note} You will also notice the Valve tag that I had to add to turn off proxy cache disabling so that IE clients would work correctly over SSL. Gotta love M$. {note} # Just to keep things clean, I edited the c:\bin\alfresco\alfresco.bat file and put 'rem' in front of the second JAVA_OPTS set as I am using Java 6. # You are now actually ready to start alfresco for the first time! Open a command window and cd over the to c:\bin\alfresco directory and then type: {noformat} alf_start.bat {noformat} # After a long time (took several minutes on a regular PC), look at the alfresco.log file in the c:\bin\alfresco directory and see if it looks like everything started OK, you can also check the database to see if the tables have been created in the alfresco-test database. You should also be able to go to http://alfresco-test.shore.mbari.org:8080 and see the alfresco web application. # Now after you run it for the first time and the database structure gets created, you can't restart it because you get: {noformat} java.sql.SQLException: Column names in each table must be unique. Column name 'ID_' in table 'JBPM_ACTION' is specified more than once. {noformat} Sigh, so in order to keep Alfresco from hurting itself, I had to turn off the schema updates. This is done by editing the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions\custom-repository.properties and adding the following: {noformat} db.schema.update=false {noformat} and then restarting alfresco.]]> 3114048 3179533 'Downloads'>'2.1 Releases'>'2.1.1' # I changed to the 'Details View', made 40 items visible, and then downloaded 'alfresco-enterprise-tomcat-2.1.1.zip' file. # I then unzipped the downloaded file to c:\bin which created an alfresco-enterprise-tomcat-2.1.1 folder in c:\bin. # I renamed the alfresco-enterprise-tomcat-2.1.1 folder to simply alfresco. # I then went back to the web browser and went to 'Company Home'>'Downloads'>'2.1 Releases'>'2.1.1'>'License Files' # I am not sure if I can do this with our agreement, but I downloaded the 'enterprise-network-customer-unlimited.lic' file. {note} I did get approval from Joe Van De Graaff at Alfresco to use the license for a test installation to get us through this issue. {note} # I logged out of the Alfresco customer web site. # I Googled on jTDS to find the jTDS JDBC driver and downloaded the jtds-1.2.2-dist.zip file from the website. # Using Windows Explorer, I could just open the jTDS zip file and copy the jtds-1.2.2.jar file. # I then pasted it in the directory c:\bin\alfresco\tomcat\common\lib directory. # I created a c:\data\alf_data directory where the alfresco data will be stored. This is different from the production installation in that the content is stored on a network appliance (\\tornado.shore.mbari.org\alfresco). # I installed a copy of SQL Server 2005 locally to use for the database to back the Alfresco test install. {note} In order to do this without warnings, I had to go back and install IIS through the Add/Remove Programs Control Panel. {note} ## I used the Local System account to run services and only used Windows Authentication logins ## I installed all the service packs and the SQL Server Management Studio product to admin DBs. # In SQL Server, I added the SHORE\DB_Collaboration accounts to the logins. # I created a new database named alfresco-test and made SHORE\DB_Collaboration the owner. # I then went to the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions directory for the customization of the server. ## I edited the custom-repository.properties file ### Changed the dir.root and dir.indexes to look like: {noformat} dir.root=c:/data/alf_data dir.indexes=c:/data/alf_data/lucene-indexes {noformat} ### Commented out the db.* lines for the HSQL Connection (db.driver and db.url) ### Uncommented the db.* lines for MSSQL and changed to use the jTDS driver. They should look like (except the password should be the right one): {noformat} db.driver=net.sourceforge.jtds.jdbc.Driver db.url=jdbc:jtds:sqlserver://localhost/alfresco-test;domain=SHORE;user=DB_Collaboration;password=XXXXXXXXX {noformat} ### I also added the following section to override the mail server settings {noformat} # Mail server configuration mail.host=mail.mbari.org mail.port=25 mail.username= mail.password= {noformat} ## Edited the custom-hibernate-dialect.properties file ### Commented out the HSQL Dialect ### Uncommented the MSSQL Dialect # Now this is not necessarily fun, but in order to really get it configured the way we want it, you need to pull the original .war file out, edit some stuff inside and re-create the .war. {note} This should all be done before starting Alfresco for the first time. {note} # Copy the c:\bin\alfresco\tomcat\webapps\alfresco.war file to your home directory. # Make a second copy so that you will always the original (I copied to alfresco.war.orig and moved it somewhere else. It is important to move it and have only the alfresco.war file in the directory because when you un-jar it, all the files go right where alfresco.war is.) # From a command line, un-jar the war file using: {noformat} jar -xvf alfresco.war {noformat} # This unpacks a lot of files and after it completes, move (or delete) the alfresco.war file from the directory. This needs to be done so it does not end up in the new .war file. # I wanted to change the "Company Home" that seems to be everywhere to something that says MBARI. ## Edited ./WEB-INF/classes/alfresco/messages/webclient.properties and changed company_home from 'Company Home' to 'MBARI Test' ## Edited ./WEB-INF/classes/alfresco/messages/webclient_en_US.properties and changed company_home from 'Company Home' to 'MBARI Test' ## I edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces.properties and changed the first two lines to read {noformat} spaces.company_home.name=MBARI Test spaces.company_home.description=The root of MBARIs Test Alfresco Server {noformat} ## Edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces_en_US.properties and made the same changes as the previous step {tip} This took a bit to find all these, and to be honest, I am not sure which one actually made the change on the GUI, but I suspect it was the _en_US ones. {tip} # When users are imported via LDAP, user spaces get created automatically. In order to put them where I wanted them to go (instead of right in the Company Home), I edited the ./WEB-INF/classes/alfresco/authentication-services-context.xml file. In the file there is a bean with an name of personalHomeFolderProvider. There is a property name 'path' and I added {noformat} /${spaces.user_homes.childname} {noformat} to the end to try to get them to create the user spaces there instead of in the Company Home. The final bean XML looks like: {noformat} /${spaces.company_home.childname}/${spaces.user_homes.childname} ${spaces.store} false All All {noformat} # I wanted to change the logo that is used. I attached the replacement [Alfresco Logo|CLT:Installation Notes^AlfrescoLogo32.png]. Copy this to ./images/logo and overwrite the one that is there. {warning} Note that I did NOT setup SSL for this installation so if I will need to come back and do that if I want truly parallel systems {warning} # Now in order to change the default behavior so that all content is versioned from the start, I edited the .\WEB-INF\classes\alfresco\model\contentModel.xml and searched for the content type definition block. {noformat} Content cm:cmobject true d:content false true false true {noformat} and added the following block right before the ending tag: {noformat} cm:versionable {noformat} so the final block looks like: {noformat} Content cm:cmobject true d:content false true false true cm:versionable {noformat} # That takes care of all the changes to the WAR file. We can now put it back into .war form. # While you are in the directory you expanded the war file in, run ## jar cvfm alfresco.war META-INF\MANIFEST.MF . # You should now have an alfresco.war file in the directory. Move that back to the alfresco install and overwrite the existing one. # Most users like the details view, so I set the default to that by editing c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions\web-client-config-custom.xml and added: {noformat} details 20
20
20 {noformat} right before the closing tag. # Now in order to use MBARI accounts, NTLM authentication was turned on and then chained with the native Alfresco accounts so that we could have non-MBARI accounts on the Alfresco server. ## For simplicity sake, I have attached the files and you can simply download and install them in the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions directory. {note} Before doing these next steps, rename the file-servers-custom.xml file to file-servers-custom.xml.orig so you will have a backup of the original {note} ### First install the [NTLM Configuration XML File|^ntlm-authentication-context.xml] ### Next install the [Authentication Chaining Configuration File|^chaining-authentication-context.xml] ### Next install the [CIFS configuration|^file-servers-custom.xml] file and over-write the existing one. {warning} In the CIFS configuration file, make sure you change the tag to reflect a unique name on the network. {warning} ### Next install the [customized authority configuration|^custom-authority-services-context.xml] file (this gives administrative privs to certain accounts). {warning} Note that I did NOT change the server to take over port 80 traffic as the SQL Server install seemed to want IIS which is currently using port 80 {warning} # Now in order for the alfresco web application to be the default, I edit the c:\bin\alfresco\tomcat\conf\server.xml file and added: {noformat} {noformat} as the last line of the tag section (right before the closing tag). {note} You will also notice the Valve tag that I had to add to turn off proxy cache disabling so that IE clients would work correctly over SSL. Gotta love M$. {note} # Just to keep things clean, I edited the c:\bin\alfresco\alfresco.bat file and put 'rem' in front of the second JAVA_OPTS set as I am using Java 6. # You are now actually ready to start alfresco for the first time! Open a command window and cd over the to c:\bin\alfresco directory and then type: {noformat} alf_start.bat {noformat} # After a long time (took several minutes on a regular PC), look at the alfresco.log file in the c:\bin\alfresco directory and see if it looks like everything started OK, you can also check the database to see if the tables have been created in the alfresco-test database. You should also be able to go to http://alfresco-test.shore.mbari.org:8080 and see the alfresco web application. # Now from the command window where you ran alf_start.bat, run alf_stop.bat to shut the server down. Check the alfresco.log file to see if anything weird happened. If not, try restarting it with alf_start.bat again and look at the alfresco.log file. # Now after you run it for the first time and the database structure gets created, you can't restart it because you get: {noformat} java.sql.SQLException: Column names in each table must be unique. Column name 'ID_' in table 'JBPM_ACTION' is specified more than once. {noformat} Sigh, so in order to keep Alfresco from hurting itself, I had to turn off the schema updates. This is done by editing the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions\custom-repository.properties and adding the following: {noformat} db.schema.update=false {noformat} and then restarting alfresco.]]> 3114050 3179527 'Downloads'>'2.1 Releases'>'2.1.1' # I changed to the 'Details View', made 40 items visible, and then downloaded 'alfresco-enterprise-tomcat-2.1.1.zip' file. # I then unzipped the downloaded file to c:\bin which created an alfresco-enterprise-tomcat-2.1.1 folder in c:\bin. # I renamed the alfresco-enterprise-tomcat-2.1.1 folder to simply alfresco. # I then went back to the web browser and went to 'Company Home'>'Downloads'>'2.1 Releases'>'2.1.1'>'License Files' # I am not sure if I can do this with our agreement, but I downloaded the 'enterprise-network-customer-unlimited.lic' file. {note} I did get approval from Joe Van De Graaff at Alfresco to use the license for a test installation to get us through this issue. {note} # I logged out of the Alfresco customer web site. # I Googled on jTDS to find the jTDS JDBC driver and downloaded the jtds-1.2.2-dist.zip file from the website. # Using Windows Explorer, I could just open the jTDS zip file and copy the jtds-1.2.2.jar file. # I then pasted it in the directory c:\bin\alfresco\tomcat\common\lib directory. # I created a c:\data\alf_data directory where the alfresco data will be stored. This is different from the production installation in that the content is stored on a network appliance (\\tornado.shore.mbari.org\alfresco). # I installed a copy of SQL Server 2005 locally to use for the database to back the Alfresco test install. {note} In order to do this without warnings, I had to go back and install IIS through the Add/Remove Programs Control Panel. {note} ## I used the Local System account to run services and only used Windows Authentication logins ## I installed all the service packs and the SQL Server Management Studio product to admin DBs. # In SQL Server, I added the SHORE\DB_Collaboration accounts to the logins. # I created a new database named alfresco-test and made SHORE\DB_Collaboration the owner. # I then went to the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions directory for the customization of the server. ## I edited the custom-repository.properties file ### Changed the dir.root and dir.indexes to look like: {noformat} dir.root=c:/data/alf_data dir.indexes=c:/data/alf_data/lucene-indexes {noformat} ### Commented out the db.* lines for the HSQL Connection (db.driver and db.url) ### Uncommented the db.* lines for MSSQL and changed to use the jTDS driver. They should look like (except the password should be the right one): {noformat} db.driver=net.sourceforge.jtds.jdbc.Driver db.url=jdbc:jtds:sqlserver://localhost/alfresco-test;domain=SHORE;user=DB_Collaboration;password=XXXXXXXXX {noformat} ### I also added the following section to override the mail server settings {noformat} # Mail server configuration mail.host=mail.mbari.org mail.port=25 mail.username= mail.password= {noformat} ## Edited the custom-hibernate-dialect.properties file ### Commented out the HSQL Dialect ### Uncommented the MSSQL Dialect # Now this is not necessarily fun, but in order to really get it configured the way we want it, you need to pull the original .war file out, edit some stuff inside and re-create the .war. {note} This should all be done before starting Alfresco for the first time. {note} # Copy the c:\bin\alfresco\tomcat\webapps\alfresco.war file to your home directory. # Make a second copy so that you will always the original (I copied to alfresco.war.orig and moved it somewhere else. It is important to move it and have only the alfresco.war file in the directory because when you un-jar it, all the files go right where alfresco.war is.) # From a command line, un-jar the war file using: {noformat} jar -xvf alfresco.war {noformat} # This unpacks a lot of files and after it completes, move (or delete) the alfresco.war file from the directory. This needs to be done so it does not end up in the new .war file. # I wanted to change the "Company Home" that seems to be everywhere to something that says MBARI. ## Edited ./WEB-INF/classes/alfresco/messages/webclient.properties and changed company_home from 'Company Home' to 'MBARI Test' ## Edited ./WEB-INF/classes/alfresco/messages/webclient_en_US.properties and changed company_home from 'Company Home' to 'MBARI Test' ## I edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces.properties and changed the first two lines to read {noformat} spaces.company_home.name=MBARI Test spaces.company_home.description=The root of MBARIs Test Alfresco Server {noformat} ## Edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces_en_US.properties and made the same changes as the previous step {tip} This took a bit to find all these, and to be honest, I am not sure which one actually made the change on the GUI, but I suspect it was the _en_US ones. {tip} # When users are imported via LDAP, user spaces get created automatically. In order to put them where I wanted them to go (instead of right in the Company Home), I edited the ./WEB-INF/classes/alfresco/authentication-services-context.xml file. In the file there is a bean with an name of personalHomeFolderProvider. There is a property name 'path' and I added {noformat} /${spaces.user_homes.childname} {noformat} to the end to try to get them to create the user spaces there instead of in the Company Home. The final bean XML looks like: {noformat} /${spaces.company_home.childname}/${spaces.user_homes.childname} ${spaces.store} false All All {noformat} # I wanted to change the logo that is used. I attached the replacement [Alfresco Logo|CLT:Installation Notes^AlfrescoLogo32.png]. Copy this to ./images/logo and overwrite the one that is there. {warning} Note that I did NOT setup SSL for this installation so if I will need to come back and do that if I want truly parallel systems {warning} # Now in order to change the default behavior so that all content is versioned from the start, I edited the .\WEB-INF\classes\alfresco\model\contentModel.xml and searched for the content type definition block. {noformat} Content cm:cmobject true d:content false true false true {noformat} and added the following block right before the ending tag: {noformat} cm:versionable {noformat} so the final block looks like: {noformat} Content cm:cmobject true d:content false true false true cm:versionable {noformat} # That takes care of all the changes to the WAR file. We can now put it back into .war form. # While you are in the directory you expanded the war file in, run ## jar cvfm alfresco.war META-INF\MANIFEST.MF . # You should now have an alfresco.war file in the directory. Move that back to the alfresco install and overwrite the existing one. # Most users like the details view, so I set the default to that by editing c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions\web-client-config-custom.xml and added: {noformat} details 20
20
20 {noformat} right before the closing tag. # Now in order to use MBARI accounts, NTLM authentication was turned on and then chained with the native Alfresco accounts so that we could have non-MBARI accounts on the Alfresco server. ## For simplicity sake, I have attached the files and you can simply download and install them in the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions directory. {note} Before doing these next steps, rename the file-servers-custom.xml file to file-servers-custom.xml.orig so you will have a backup of the original {note} ### First install the [NTLM Configuration XML File|^ntlm-authentication-context.xml] ### Next install the [Authentication Chaining Configuration File|^chaining-authentication-context.xml] ### Next install the [CIFS configuration|^file-servers-custom.xml] file and over-write the existing one. {warning} In the CIFS configuration file, make sure you change the tag to reflect a unique name on the network. {warning} ### Next install the [customized authority configuration|^custom-authority-services-context.xml] file (this gives administrative privs to certain accounts). {warning} Note that I did NOT change the server to take over port 80 traffic as the SQL Server install seemed to want IIS which is currently using port 80 {warning} # Now in order for the alfresco web application to be the default, I edit the c:\bin\alfresco\tomcat\conf\server.xml file and added: {noformat} {noformat} as the last line of the tag section (right before the closing tag). {note} You will also notice the Valve tag that I had to add to turn off proxy cache disabling so that IE clients would work correctly over SSL. Gotta love M$. {note}]]> 3114044 19071251 19038485 3179529 'Downloads'>'2.1 Releases'>'2.1.1' # I changed to the 'Details View', made 40 items visible, and then downloaded 'alfresco-enterprise-tomcat-2.1.1.zip' file. # I then unzipped the downloaded file to c:\bin which created an alfresco-enterprise-tomcat-2.1.1 folder in c:\bin. # I renamed the alfresco-enterprise-tomcat-2.1.1 folder to simply alfresco. # I then went back to the web browser and went to 'Company Home'>'Downloads'>'2.1 Releases'>'2.1.1'>'License Files' # I am not sure if I can do this with our agreement, but I downloaded the 'enterprise-network-customer-unlimited.lic' file. {note} I did get approval from Joe Van De Graaff at Alfresco to use the license for a test installation to get us through this issue. {note} # I logged out of the Alfresco customer web site. # I Googled on jTDS to find the jTDS JDBC driver and downloaded the jtds-1.2.2-dist.zip file from the website. # Using Windows Explorer, I could just open the jTDS zip file and copy the jtds-1.2.2.jar file. # I then pasted it in the directory c:\bin\alfresco\tomcat\common\lib directory. # I created a c:\data\alf_data directory where the alfresco data will be stored. This is different from the production installation in that the content is stored on a network appliance (\\tornado.shore.mbari.org\alfresco). # I installed a copy of SQL Server 2005 locally to use for the database to back the Alfresco test install. {note} In order to do this without warnings, I had to go back and install IIS through the Add/Remove Programs Control Panel. {note} ## I used the Local System account to run services and only used Windows Authentication logins ## I installed all the service packs and the SQL Server Management Studio product to admin DBs. # In SQL Server, I added the SHORE\DB_Collaboration accounts to the logins. # I created a new database named alfresco-test and made SHORE\DB_Collaboration the owner. # I then went to the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions directory for the customization of the server. ## I edited the custom-repository.properties file ### Changed the dir.root and dir.indexes to look like: {noformat} dir.root=c:/data/alf_data dir.indexes=c:/data/alf_data/lucene-indexes {noformat} ### Commented out the db.* lines for the HSQL Connection (db.driver and db.url) ### Uncommented the db.* lines for MSSQL and changed to use the jTDS driver. They should look like (except the password should be the right one): {noformat} db.driver=net.sourceforge.jtds.jdbc.Driver db.url=jdbc:jtds:sqlserver://localhost/alfresco-test;domain=SHORE;user=DB_Collaboration;password=XXXXXXXXX {noformat} ### I also added the following section to override the mail server settings {noformat} # Mail server configuration mail.host=mail.mbari.org mail.port=25 mail.username= mail.password= {noformat} ## Edited the custom-hibernate-dialect.properties file ### Commented out the HSQL Dialect ### Uncommented the MSSQL Dialect # Now this is not necessarily fun, but in order to really get it configured the way we want it, you need to pull the original .war file out, edit some stuff inside and re-create the .war. {note} This should all be done before starting Alfresco for the first time. {note} # Copy the c:\bin\alfresco\tomcat\webapps\alfresco.war file to your home directory. # Make a second copy so that you will always the original (I copied to alfresco.war.orig and moved it somewhere else. It is important to move it and have only the alfresco.war file in the directory because when you un-jar it, all the files go right where alfresco.war is.) # From a command line, un-jar the war file using: {noformat} jar -xvf alfresco.war {noformat} # This unpacks a lot of files and after it completes, move (or delete) the alfresco.war file from the directory. This needs to be done so it does not end up in the new .war file. # I wanted to change the "Company Home" that seems to be everywhere to something that says MBARI. ## Edited ./WEB-INF/classes/alfresco/messages/webclient.properties and changed company_home from 'Company Home' to 'MBARI Test' ## Edited ./WEB-INF/classes/alfresco/messages/webclient_en_US.properties and changed company_home from 'Company Home' to 'MBARI Test' ## I edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces.properties and changed the first two lines to read {noformat} spaces.company_home.name=MBARI Test spaces.company_home.description=The root of MBARIs Test Alfresco Server {noformat} ## Edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces_en_US.properties and made the same changes as the previous step {tip} This took a bit to find all these, and to be honest, I am not sure which one actually made the change on the GUI, but I suspect it was the _en_US ones. {tip} # When users are imported via LDAP, user spaces get created automatically. In order to put them where I wanted them to go (instead of right in the Company Home), I edited the ./WEB-INF/classes/alfresco/authentication-services-context.xml file. In the file there is a bean with an name of personalHomeFolderProvider. There is a property name 'path' and I added {noformat} /${spaces.user_homes.childname} {noformat} to the end to try to get them to create the user spaces there instead of in the Company Home. The final bean XML looks like: {noformat} /${spaces.company_home.childname}/${spaces.user_homes.childname} ${spaces.store} false All All {noformat} # I wanted to change the logo that is used. I attached the replacement [Alfresco Logo|CLT:Installation Notes^AlfrescoLogo32.png]. Copy this to ./images/logo and overwrite the one that is there. {warning} Note that I did NOT setup SSL for this installation so if I will need to come back and do that if I want truly parallel systems {warning} # Now in order to change the default behavior so that all content is versioned from the start, I edited the .\WEB-INF\classes\alfresco\model\contentModel.xml and searched for the content type definition block. {noformat} Content cm:cmobject true d:content false true false true {noformat} and added the following block right before the ending tag: {noformat} cm:versionable {noformat} so the final block looks like: {noformat} Content cm:cmobject true d:content false true false true cm:versionable {noformat} # That takes care of all the changes to the WAR file. We can now put it back into .war form. # While you are in the directory you expanded the war file in, run ## jar cvfm alfresco.war META-INF\MANIFEST.MF . # You should now have an alfresco.war file in the directory. Move that back to the alfresco install and overwrite the existing one. # Most users like the details view, so I set the default to that by editing c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions\web-client-config-custom.xml and added: {noformat} details 20
20
20 {noformat} right before the closing tag. # Now in order to use MBARI accounts, NTLM authentication was turned on and then chained with the native Alfresco accounts so that we could have non-MBARI accounts on the Alfresco server. ## For simplicity sake, I have attached the files and you can simply download and install them in the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions directory. {note} Before doing these next steps, rename the file-servers-custom.xml file to file-servers-custom.xml.orig so you will have a backup of the original {note} ### First install the [NTLM Configuration XML File|^ntlm-authentication-context.xml] ### Next install the [Authentication Chaining Configuration File|^chaining-authentication-context.xml] ### Next install the [CIFS configuration|^file-servers-custom.xml] file and over-write the existing one. {warning} In the CIFS configuration file, make sure you change the tag to reflect a unique name on the network. {warning} ### Next install the [customized authority configuration|^custom-authority-services-context.xml] file (this gives administrative privs to certain accounts). {warning} Note that I did NOT change the server to take over port 80 traffic as the SQL Server install seemed to want IIS which is currently using port 80 {warning} # Now in order for the alfresco web application to be the default, I edit the c:\bin\alfresco\tomcat\conf\server.xml file and added: {noformat} {noformat} as the last line of the tag section (right before the closing tag). {note} You will also notice the Valve tag that I had to add to turn off proxy cache disabling so that IE clients would work correctly over SSL. Gotta love M$. {note} # Just to keep things clean, I edited the c:\bin\alfresco\alfresco.bat file and put 'rem' in front of the second JAVA_OPTS set as I am using Java 6. # You are now actually ready to start alfresco for the first time! Open a command window and cd over the to c:\bin\alfresco directory and then type: {noformat} alf_start.bat {noformat} # After a bit, look at the alfresco.log file in the c:\bin\alfresco directory and see if it looks like everything started OK, you can also check the database to see if the tables have been created in the alfresco-test database. # Now after you run it for the first time and the database structure gets created, you can't restart it because you get: {noformat} java.sql.SQLException: Column names in each table must be unique. Column name 'ID_' in table 'JBPM_ACTION' is specified more than once. {noformat} Sigh, so in order to keep Alfresco from hurting itself, I had to turn off the schema updates. This is done by editing the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions\custom-repository.properties and adding the following: {noformat} db.schema.update=false {noformat} and then restarting alfresco.]]> 3114046 3179523 'Downloads'>'2.1 Releases'>'2.1.1' # I changed to the 'Details View', made 40 items visible, and then downloaded 'alfresco-enterprise-tomcat-2.1.1.zip' file. # I then unzipped the downloaded file to c:\bin which created an alfresco-enterprise-tomcat-2.1.1 folder in c:\bin. # I renamed the alfresco-enterprise-tomcat-2.1.1 folder to simply alfresco. # I then went back to the web browser and went to 'Company Home'>'Downloads'>'2.1 Releases'>'2.1.1'>'License Files' # I am not sure if I can do this with our agreement, but I downloaded the 'enterprise-network-customer-unlimited.lic' file. {note} I did get approval from Joe Van De Graaff at Alfresco to use the license for a test installation to get us through this issue. {note} # I logged out of the Alfresco customer web site. # I Googled on jTDS to find the jTDS JDBC driver and downloaded the jtds-1.2.2-dist.zip file from the website. # Using Windows Explorer, I could just open the jTDS zip file and copy the jtds-1.2.2.jar file. # I then pasted it in the directory c:\bin\alfresco\tomcat\common\lib directory. # I created a c:\data\alf_data directory where the alfresco data will be stored. This is different from the production installation in that the content is stored on a network appliance (\\tornado.shore.mbari.org\alfresco). # I installed a copy of SQL Server 2005 locally to use for the database to back the Alfresco test install. {note} In order to do this without warnings, I had to go back and install IIS through the Add/Remove Programs Control Panel. {note} ## I used the Local System account to run services and only used Windows Authentication logins ## I installed all the service packs and the SQL Server Management Studio product to admin DBs. # In SQL Server, I added the SHORE\DB_Collaboration accounts to the logins. # I created a new database named alfresco-test and made SHORE\DB_Collaboration the owner. # I then went to the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions directory for the customization of the server. ## I edited the custom-repository.properties file ### Changed the dir.root and dir.indexes to look like: {noformat} dir.root=c:/data/alf_data dir.indexes=c:/data/alf_data/lucene-indexes {noformat} ### Commented out the db.* lines for the HSQL Connection (db.driver and db.url) ### Uncommented the db.* lines for MSSQL and changed to use the jTDS driver. They should look like (except the password should be the right one): {noformat} db.driver=net.sourceforge.jtds.jdbc.Driver db.url=jdbc:jtds:sqlserver://localhost/alfresco-test;domain=SHORE;user=DB_Collaboration;password=XXXXXXXXX {noformat} ### I also added the following section to override the mail server settings {noformat} # Mail server configuration mail.host=mail.mbari.org mail.port=25 mail.username= mail.password= {noformat} ## Edited the custom-hibernate-dialect.properties file ### Commented out the HSQL Dialect ### Uncommented the MSSQL Dialect # Now this is not necessarily fun, but in order to really get it configured the way we want it, you need to pull the original .war file out, edit some stuff inside and re-create the .war. {note} This should all be done before starting Alfresco for the first time. {note} # Copy the c:\bin\alfresco\tomcat\webapps\alfresco.war file to your home directory. # Make a second copy so that you will always the original (I copied to alfresco.war.orig and moved it somewhere else. It is important to move it and have only the alfresco.war file in the directory because when you un-jar it, all the files go right where alfresco.war is.) # From a command line, un-jar the war file using: {noformat} jar -xvf alfresco.war {noformat} # This unpacks a lot of files and after it completes, move (or delete) the alfresco.war file from the directory. This needs to be done so it does not end up in the new .war file. # I wanted to change the "Company Home" that seems to be everywhere to something that says MBARI. ## Edited ./WEB-INF/classes/alfresco/messages/webclient.properties and changed company_home from 'Company Home' to 'MBARI Test' ## Edited ./WEB-INF/classes/alfresco/messages/webclient_en_US.properties and changed company_home from 'Company Home' to 'MBARI Test' ## I edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces.properties and changed the first two lines to read {noformat} spaces.company_home.name=MBARI Test spaces.company_home.description=The root of MBARIs Test Alfresco Server {noformat} ## Edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces_en_US.properties and made the same changes as the previous step {tip} This took a bit to find all these, and to be honest, I am not sure which one actually made the change on the GUI, but I suspect it was the _en_US ones. {tip} # When users are imported via LDAP, user spaces get created automatically. In order to put them where I wanted them to go (instead of right in the Company Home), I edited the ./WEB-INF/classes/alfresco/authentication-services-context.xml file. In the file there is a bean with an name of personalHomeFolderProvider. There is a property name 'path' and I added {noformat} /${spaces.user_homes.childname} {noformat} to the end to try to get them to create the user spaces there instead of in the Company Home. The final bean XML looks like: {noformat} /${spaces.company_home.childname}/${spaces.user_homes.childname} ${spaces.store} false All All {noformat} # I wanted to change the logo that is used. I attached the replacement [Alfresco Logo|CLT:Installation Notes^AlfrescoLogo32.png]. Copy this to ./images/logo and overwrite the one that is there. {warning} Note that I did NOT setup SSL for this installation so if I will need to come back and do that if I want truly parallel systems {warning} # Now in order to change the default behavior so that all content is versioned from the start, I edited the .\WEB-INF\classes\alfresco\model\contentModel.xml and searched for the content type definition block. {noformat} Content cm:cmobject true d:content false true false true {noformat} and added the following block right before the ending tag: {noformat} cm:versionable {noformat} so the final block looks like: {noformat} Content cm:cmobject true d:content false true false true cm:versionable {noformat} # That takes care of all the changes to the WAR file. We can now put it back into .war form. # While you are in the directory you expanded the war file in, run ## jar cvfm alfresco.war META-INF\MANIFEST.MF . # You should now have an alfresco.war file in the directory. Move that back to the alfresco install and overwrite the existing one. # Most users like the details view, so I set the default to that by editing c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions\web-client-config-custom.xml and added: {noformat} details 20
20
20 {noformat} right before the closing tag. # Now in order to use MBARI accounts, NTLM authentication was turned on and then chained with the native Alfresco accounts so that we could have non-MBARI accounts on the Alfresco server. ## For simplicity sake, I have attached the files and you can simply download and install them in the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions directory. {note} Before doing these next steps, rename the file-servers-custom.xml file to file-servers-custom.xml.orig so you will have a backup of the original {note} ### First install the [NTLM Configuration XML File|^ntlm-authentication-context.xml] ### Next install the [Authentication Chaining Configuration File|^chaining-authentication-context.xml] ### Next install the [CIFS configuration|^file-servers-custom.xml] file and over-write the existing one. {warning} In the CIFS configuration file, make sure you change the tag to reflect a unique name on the network. {warning} ### Next install the [customized authority configuration|^custom-authority-services-context.xml] file (this gives administrative privs to certain accounts). # In order for Alfresco to handle all port 80 traffic, I changed Tomcat so that it takes port 80 and SSL goes over port 443. So I edited the c:\Alfresco\tomcat\conf\server.xml file and changed the 8080 port to 80 and the 8443 port to 443 (the 443 change is done in two places).]]> 3114040 3179525 'Downloads'>'2.1 Releases'>'2.1.1' # I changed to the 'Details View', made 40 items visible, and then downloaded 'alfresco-enterprise-tomcat-2.1.1.zip' file. # I then unzipped the downloaded file to c:\bin which created an alfresco-enterprise-tomcat-2.1.1 folder in c:\bin. # I renamed the alfresco-enterprise-tomcat-2.1.1 folder to simply alfresco. # I then went back to the web browser and went to 'Company Home'>'Downloads'>'2.1 Releases'>'2.1.1'>'License Files' # I am not sure if I can do this with our agreement, but I downloaded the 'enterprise-network-customer-unlimited.lic' file. {note} I did get approval from Joe Van De Graaff at Alfresco to use the license for a test installation to get us through this issue. {note} # I logged out of the Alfresco customer web site. # I Googled on jTDS to find the jTDS JDBC driver and downloaded the jtds-1.2.2-dist.zip file from the website. # Using Windows Explorer, I could just open the jTDS zip file and copy the jtds-1.2.2.jar file. # I then pasted it in the directory c:\bin\alfresco\tomcat\common\lib directory. # I created a c:\data\alf_data directory where the alfresco data will be stored. This is different from the production installation in that the content is stored on a network appliance (\\tornado.shore.mbari.org\alfresco). # I installed a copy of SQL Server 2005 locally to use for the database to back the Alfresco test install. {note} In order to do this without warnings, I had to go back and install IIS through the Add/Remove Programs Control Panel. {note} ## I used the Local System account to run services and only used Windows Authentication logins ## I installed all the service packs and the SQL Server Management Studio product to admin DBs. # In SQL Server, I added the SHORE\DB_Collaboration accounts to the logins. # I created a new database named alfresco-test and made SHORE\DB_Collaboration the owner. # I then went to the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions directory for the customization of the server. ## I edited the custom-repository.properties file ### Changed the dir.root and dir.indexes to look like: {noformat} dir.root=c:/data/alf_data dir.indexes=c:/data/alf_data/lucene-indexes {noformat} ### Commented out the db.* lines for the HSQL Connection (db.driver and db.url) ### Uncommented the db.* lines for MSSQL and changed to use the jTDS driver. They should look like (except the password should be the right one): {noformat} db.driver=net.sourceforge.jtds.jdbc.Driver db.url=jdbc:jtds:sqlserver://localhost/alfresco-test;domain=SHORE;user=DB_Collaboration;password=XXXXXXXXX {noformat} ### I also added the following section to override the mail server settings {noformat} # Mail server configuration mail.host=mail.mbari.org mail.port=25 mail.username= mail.password= {noformat} ## Edited the custom-hibernate-dialect.properties file ### Commented out the HSQL Dialect ### Uncommented the MSSQL Dialect # Now this is not necessarily fun, but in order to really get it configured the way we want it, you need to pull the original .war file out, edit some stuff inside and re-create the .war. {note} This should all be done before starting Alfresco for the first time. {note} # Copy the c:\bin\alfresco\tomcat\webapps\alfresco.war file to your home directory. # Make a second copy so that you will always the original (I copied to alfresco.war.orig and moved it somewhere else. It is important to move it and have only the alfresco.war file in the directory because when you un-jar it, all the files go right where alfresco.war is.) # From a command line, un-jar the war file using: {noformat} jar -xvf alfresco.war {noformat} # This unpacks a lot of files and after it completes, move (or delete) the alfresco.war file from the directory. This needs to be done so it does not end up in the new .war file. # I wanted to change the "Company Home" that seems to be everywhere to something that says MBARI. ## Edited ./WEB-INF/classes/alfresco/messages/webclient.properties and changed company_home from 'Company Home' to 'MBARI Test' ## Edited ./WEB-INF/classes/alfresco/messages/webclient_en_US.properties and changed company_home from 'Company Home' to 'MBARI Test' ## I edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces.properties and changed the first two lines to read {noformat} spaces.company_home.name=MBARI Test spaces.company_home.description=The root of MBARIs Test Alfresco Server {noformat} ## Edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces_en_US.properties and made the same changes as the previous step {tip} This took a bit to find all these, and to be honest, I am not sure which one actually made the change on the GUI, but I suspect it was the _en_US ones. {tip} # When users are imported via LDAP, user spaces get created automatically. In order to put them where I wanted them to go (instead of right in the Company Home), I edited the ./WEB-INF/classes/alfresco/authentication-services-context.xml file. In the file there is a bean with an name of personalHomeFolderProvider. There is a property name 'path' and I added {noformat} /${spaces.user_homes.childname} {noformat} to the end to try to get them to create the user spaces there instead of in the Company Home. The final bean XML looks like: {noformat} /${spaces.company_home.childname}/${spaces.user_homes.childname} ${spaces.store} false All All {noformat} # I wanted to change the logo that is used. I attached the replacement [Alfresco Logo|CLT:Installation Notes^AlfrescoLogo32.png]. Copy this to ./images/logo and overwrite the one that is there. {warning} Note that I did NOT setup SSL for this installation so if I will need to come back and do that if I want truly parallel systems {warning} # Now in order to change the default behavior so that all content is versioned from the start, I edited the .\WEB-INF\classes\alfresco\model\contentModel.xml and searched for the content type definition block. {noformat} Content cm:cmobject true d:content false true false true {noformat} and added the following block right before the ending tag: {noformat} cm:versionable {noformat} so the final block looks like: {noformat} Content cm:cmobject true d:content false true false true cm:versionable {noformat} # That takes care of all the changes to the WAR file. We can now put it back into .war form. # While you are in the directory you expanded the war file in, run ## jar cvfm alfresco.war META-INF\MANIFEST.MF . # You should now have an alfresco.war file in the directory. Move that back to the alfresco install and overwrite the existing one. # Most users like the details view, so I set the default to that by editing c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions\web-client-config-custom.xml and added: {noformat} details 20
20
20 {noformat} right before the closing tag. # Now in order to use MBARI accounts, NTLM authentication was turned on and then chained with the native Alfresco accounts so that we could have non-MBARI accounts on the Alfresco server. ## For simplicity sake, I have attached the files and you can simply download and install them in the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions directory. {note} Before doing these next steps, rename the file-servers-custom.xml file to file-servers-custom.xml.orig so you will have a backup of the original {note} ### First install the [NTLM Configuration XML File|^ntlm-authentication-context.xml] ### Next install the [Authentication Chaining Configuration File|^chaining-authentication-context.xml] ### Next install the [CIFS configuration|^file-servers-custom.xml] file and over-write the existing one. {warning} In the CIFS configuration file, make sure you change the tag to reflect a unique name on the network. {warning} ### Next install the [customized authority configuration|^custom-authority-services-context.xml] file (this gives administrative privs to certain accounts). {warning} Note that I did NOT change the server to take over port 80 traffic as the SQL Server install seemed to want IIS which is currently using port 80 {warning}]]> 3114042 10944873 10912113 6619142 6586374 6619139 6586371 10944784 10912022 10944781 10912019 10944780 10912018 10944778 10912016 10944776 10912014 10944774 10912012 10944772 10912010 10944811 10912052 10944808 10912049 10944810 10912051 10944707 10911944 10944709 10911946 10944712 10911949 10944715 10911952 10944717 $5000 Unit Cost | $ | $ | | 5020-000 | Books/Subscriptions | $ | $ | | 5060-000 | Dues, Membership, Licenses | $ | $ | | 5130-000 | Outside Srvc - General | $ | $ | | 5150-000 | Outside Srvc - Maint Contracts | $ | $ | | 5300-000 | Supplies - Computer (Hardware) | $ | $ | | 5310-000 | Supplies - Computer (Software) | $ | $ | | 5320-000 | Supplies - Engineering Lab | $ | $ | | 5330-000 | Supplies - Non-Capitalized Equipment | $ | $ | {panel} h5. Kevin || Requested Item || Cost || Approved? || Account To Charge || Purchase Status || | Books | $300 | (/) | 5020-000 | | | Subscriptions | $200 | (/) | 5060-000 | | | PDA-Tablet | $1000 | (x) | | | | Snow Leopard Upgrade (2) | $100 | (/) | 5310-000 | | | Training | $2500 | (x) | | | | Conference | $2500 | (x) | | | | Hard drive and memory upgrade for laptop | $500 | (/) | 5300-000 | | | UML Tool Evaluation and Purchase | $2000 | (x) | | | h5. Craig || Requested Item || Cost || Approved? || Account To Charge || Purchase Status || | Software Maintenance | $2500 | (/) | 5150-000 | | | Backup Hard Disk | $250 | (/) | 5300-000 | | | Books | $200 | (/) | 5020-000 | | | Subscriptions | $200 | (/) | 5060-000 | | | NAB 2010 Conference | $2000 | (x) | | | | IWCE 2010 Conference | $1800 | (x) | | | h5. Thom || Requested Item || Cost || Approved? || Account To Charge || Purchase Status || | Software/Tools/Maintenance * Frontline $500 * RealBasic $200 | $700 | (/) | 5310-000 | | | IAR for MSP430 | $3400 | (/) | 5310-000 | | | Books | $350 | (/) | 5020-000 | | | Training/Tuition | $1500 | (x) | | | | Membership Dues | $200 | (/) | 5060-000 | | | New monitor/computer upgrade | $450 | (/) | 5300-000 | | | General Supplies (parts organizer) | $350 | (/) | 5320-000 | | | Dev Kit Evals | $1500 | (/) | 5300-000 | | h5. Rich || Requested Item || Cost || Approved? || Account To Charge || Purchase Status || | Books | $500 | (/) | 5020-000 | | | Computer Hardware | $500 | (/) | 5300-000 | | | Subscriptions | $500 | (/) | 5060-000 | | | Real Basic Developers Conference | $2500 | (x) | | | | Digi TS-4 line Serial PortServer | $575 | (/) | 5300-000 | | | Real Basic Software License | $640 | (/) | 5310-000 | | | Frontline Serial protocol analyzer software package | $510 | (/) | 5310-000 | | | OS-X/VMWare Upgrade | $220 | (/) | 5310-000 | | | Labview Developers Suite (maint) | $3300 | (/) | 5310-000 | | | SQL Server 2008 | $60 | (/) | 5310-000 | | h5. Mike || Requested Item || Cost || Approved? || Account To Charge || Purchase Status || | Web3D Consortium Membership | $3500 | (/) | 5060-000 | | | OGC Membership | $1100 | (/) | 5060-000 | | | Books | $200 | (/) | 5020-000 | | | Misc software | $500 | (/) | 5310-000 | | | Training | $3000 | (x) | | | | Conference | $2500 | (x) | | | | Misc hardware | $500 | (/) | 5300-000 | | h5. Karen || Requested Item || Cost || Approved? || Account To Charge || Purchase Status || | Books | $300 | (/) | 5020-000 | | | Membership | $20 | (/) | 5060-000 | | | AGU Conference | $1500 | (x) | | | h5. Support Lab || Requested Item || Cost || Approved? || Account To Charge || Purchase Status || | Misc consumables | $5000 | (/) | 5320-000 | | | Pace Desoldering Station | $1500 | (/) | 5320-000 | | | Lista Parts Cabinet | $2300 | (/) | 5320-000 | | | Calibration and Maintenance | $1000 | (/) | 5130-000 | | | Refurbished OScope | $3000 | (x) | | | | Lab Supplies * I2C/SPI TP320121 Protocol Analyzer * Handtools * DC-1Mhz 75W Power Amplifier (this will not be ordered) | $2400 | (/) | 5320-000 | | h5. Software Lab || Requested Item || Cost || Approved? || Account To Charge || Purchase Status || | Subversion Server | $3800 | (x) | | | | SSDS Ingest Server Upgrade | $3800 | (/) | 5300-000 | | | Server for JIRA | $3800 | (/) | 5300-000 | | | Server for Bamboo | $3800 | (x) | | | | Server for Clover | $3800 | (x) | | | | Server for Crowd | $3800 | (x) | | | | Server for Fisheye | $3800 | (x) | | | | Server for Crucible | $3800 | (x) | | | | Additional RAM, DVD Burners, etc for Computers | $2800 | (/) | 5320-000 | | | Mathworks licenses | $17000 | (/) | 5150-000 | | | Aldec | $2400 | (/) | 5150-000 | | | RaveHD | $2500 | (/) | 5150-000 | | | Borland | $4000 | (x) | | | | MathCAD | $650 | (/) | 5150-000 | | | Wago Modules | $1000 | (/) | 5320-000 | | | Miscellaneous Lab Supplies (DVDs, CDs, cartridges, cables, etc. | $2500 | (/) | 5320-000 | | | Miscellaneous Software Development Tools | $750 | (/) | 5300-000 | | h5. Microwave and Wireless || Requested Item || Cost || Approved? || Account To Charge || Purchase Status || | License Fees | $3,000.00 | (/) | 5330-000 | | | Rack and Hardware | $1,500.00 | (/) | 5330-000 | | | Subcarrier modem maintenance | $1,800.00 | (/) | 5330-000 | | | HD Decoder (used demo deal) | $3,000.00 | (/) | 5330-000 | | | HD-SDI Cards for WF | $2,300.00 | (/) | 5330-000 | | | Misc | $1,500.00 | (/) | 5330-000 | | | Spare Microwave Transceiver | $25,000.00 | (/) | 1500-000 | | | Fix Toro WF SeaTel azimuth axis | $5,000.00 | (/) | 1500-000 | | h5. New Toro Site Development || Requested Item || Cost || Approved? || Account To Charge || Purchase Status || | Initial permits and design | $4,500.00 | (/) | 5130-000 | | | Fencing | $2,000.00 | (/) | 5130-000 | | | Generator with ATS, site grounding and building feed (Day Elec) | $21,000.00 | (x) | | | | 500 gal Propane tank | $\- | (x) | | | | PGE tie in | $2,000.00 | (x) | | | | Shelter, 8X12X9, shipping and instalation total (Shelter One) | $29,000.00 | (x) | | | | Site Prep, grading etc. | $4,000.00 | (x) | | | | 40' tower, Ice bridge and foundation TBD | $20,000.00 | (x) | | | | FCC Fees | $6,000.00 | (x) | | | | margin for error | $10,000.00 | (x) | | | h5. Pressure Test Facility || Requested Item || Cost || Approved? || Account To Charge || Purchase Status || | Discrete components for electrical and pneumatic controls | $7,500.00 | (x) | | | | Digiquartz transducer Model 9000, 20000 PSI | $6,500.00 | (x) | | | | Heise CM 12" 0 to 20,000 PSI gauge | $2,500.00 | (x) | | | | Digiquartz display and serial interface | $800.00 | (x) | | | | Panel Computer, touch screen interface | $2,500.00 | (x) | | | | Sheet Metal work, Hoffman panel and front panel | $250.00 | (x) | | | | High Pressure fittings, HIP and Autoclave Engineers | $1,400.00 | (x) | | | | Misc parts | $500.00 | (x) | | |]]> 10911954 10944719 $5000 Unit Cost | $ | $ | | 5020-000 | Books/Subscriptions | $ | $ | | 5060-000 | Dues, Membership, Licenses | $ | $ | | 5130-000 | Outside Srvc - General | $ | $ | | 5150-000 | Outside Srvc - Maint Contracts | $ | $ | | 5300-000 | Supplies - Computer (Hardware) | $ | $ | | 5310-000 | Supplies - Computer (Software) | $ | $ | | 5320-000 | Supplies - Engineering Lab | $ | $ | | 5330-000 | Supplies - Non-Capitalized Equipment | $ | $ | {panel} {column} {section} ]]> 10911956 10944721 $5000 Unit Cost | $30,000 | $ | | 5020-000 | Books/Subscriptions | $ | $ | | 5060-000 | Dues, Membership, Licenses | $ | $ | | 5130-000 | Outside Srvc - General | $ | $ | | 5150-000 | Outside Srvc - Maint Contracts | $ | $ | | 5300-000 | Supplies - Computer (Hardware) | $ | $ | | 5310-000 | Supplies - Computer (Software) | $ | $ | | 5320-000 | Supplies - Engineering Lab | $ | $ | | 5330-000 | Supplies - Non-Capitalized Equipment | $ | $ | | *Total* | | $123,125 | $ | {panel} {column} {section} ]]> 10911958 10944723 $5000 Unit Cost | $30,000 | $ | | 5020-000 | Books/Subscriptions | $1,850 | $ | | 5060-000 | Dues, Membership, Licenses | $5720 | $ | | 5130-000 | Outside Srvc - General | $7500 | $ | | 5150-000 | Outside Srvc - Maint Contracts | $25,050 | $ | | 5300-000 | Supplies - Computer (Hardware) | $10,375 | $ | | 5310-000 | Supplies - Computer (Software) | $ | $ | | 5320-000 | Supplies - Engineering Lab | $ | $ | | 5330-000 | Supplies - Non-Capitalized Equipment | $ | $ | | *Total* | | $123,125 | $ | {panel} {column} {section} ]]> 10911960 10944724 $5000 Unit Cost | $30,000 | $ | | 5020-000 | Books/Subscriptions | $1,850 | $ | | 5060-000 | Dues, Membership, Licenses | $5720 | $ | | 5130-000 | Outside Srvc - General | $7500 | $ | | 5150-000 | Outside Srvc - Maint Contracts | $25,050 | $ | | 5300-000 | Supplies - Computer (Hardware) | $11,875 | $ | | 5310-000 | Supplies - Computer (Software) | $10,180 | $ | | 5320-000 | Supplies - Engineering Lab | $17,850 | $ | | 5330-000 | Supplies - Non-Capitalized Equipment | $43,100 | $ | | *Total* | | $123,125 | $ | {panel} {column} {section} ]]> 10911961 10944726 $5000 Unit Cost | $30,000 | $ | | 5020-000 | Books/Subscriptions | $1,850 | $ | | 5060-000 | Dues, Membership, Licenses | $5720 | $ | | 5130-000 | Outside Srvc - General | $7500 | $ | | 5150-000 | Outside Srvc - Maint Contracts | $25,050 | $ | | 5300-000 | Supplies - Computer (Hardware) | $11,875 | $ | | 5310-000 | Supplies - Computer (Software) | $10,180 | $ | | 5320-000 | Supplies - Engineering Lab | $17,850 | $ | | 5330-000 | Supplies - Non-Capitalized Equipment | $13,100 | $ | | *Total* | | $123,125 | $ | {panel} {column} {section} ]]> 10911963 19071110 "Downloads">"2.1 Releases">"2.1.1" # I then clicked on alfresco-enterprise-tomcat-2.1.1.zip to download the zip file. # Went to [http://customers.alfresco.com] (I was still logged in) # Went to "Company Home">"Downloads">"2.1 Releases">"2.1.1">"License Files" # I went ahead and downloaded all the "*.lic" files, but I think I only need enterprise-network-customer-unlimited.lic" # Logged out of Alfresco. # Since I suspect I will need a JDBC driver for SQLServer, I downloaded the jTDS-1.2.2 driver from the jtds web site (just Google jtds and go to the download section of the top google return). # I closed the Firefox browser. # I extracted the jtds-1.2.2.jar file from the jtds download # I downloaded and installed the JRockit 6 R27.4 JDK Microsoft Windows (x86 - 32 bit) from BEA's web site {note} After installing JRockit, make sure you set the JAVA_HOME environment variable to point to the installation of JRockit. For example, I went to the desktop, right clicked on the computer, did Properties, then clicked on the Advanced tab, then click on the environment variables button and then created a new system variable named JAVA_HOME and set to c:\bin\Java\jrockit-R27.4.0-jdk1.6.0_02 {note} # I ran the installer, changed the "Program Files" to "bin" in the installation directory for both the JDK and the JRE. I also chose to install the JRE as public. # Using Firefox, I downloaded the PHP 5.2.5 Windows Installer from php.net and installed it. Although I installed it, I did not integrate it with a web server as I want Alfresco to take port 80. I probably did not need to install PHP, but I thought I would anyway. (again, I changed install path from "Program Files" to "bin" # I also downloaded and installed OpenOffice and ran it once so I could get through the initial startup # I setup a Alfresco database on the server Solstice and granted the LAGOON\DB_Collaboration account to be the db_owner of the Alfresco database. # I unzipped the alfresco tomcat zip file to an alfresco directory in c:\bin # I then went to the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions directory for the customization of the server. ## I edited the custom-repository.properties file ### Changed the dir.root and dir.indexes to look like: {noformat} dir.root=//tornado.shore.mbari.org/Alfresco/alf_data dir.indexes=d:/alf_data/lucene-indexes {noformat} ### Commented out the db.* lines for the HSQL Connection (db.driver and db.url) ### Uncommented the db.* lines for MSSQL and changed to use the jTDS driver. They should look like: {noformat} db.driver=net.sourceforge.jtds.jdbc.Driver db.url=jdbc:jtds:sqlserver://solstice.shore.mbari.org/Alfresco;domain=SHORE;user=DB_Collaboration;password=XXXXXXXXX {noformat} ### I also added the following section to override the mail server settings {noformat} # Mail server configuration mail.host=mail.mbari.org mail.port=25 mail.username= mail.password= {noformat} ## Edited the custom-hibernate-dialect.properties file ### Commented out the HSQL Dialect ### Uncommented the MSSQL Dialect # I then installed the jtds-1.2.2.jar in the c:\bin\alfresco\tomcat\common\lib so that it will be on the classpath when Alfresco is started # Now this is not necessarily fun, but in order to really get it configured the way we want it, you need to pull the original .war file out, edit some stuff inside and re-create the .war. {note} This should all be done before starting Alfresco for the first time. {note} # Copy the c:\Alfresco\tomcat\webapps\alfresco.war file to your home directory. # Make a second copy so that you will always the original (I copied to alfresco.war.orig and moved it somewhere else. It is important to move it and have only the alfresco.war file in the directory because when you un-jar it, all the files go right where alfresco.war is.) # From a command line, un-jar the war file using: {noformat} jar -xvf alfresco.war {noformat} # This unpacks a lot of files and after it completes, move (or delete) the alfresco.war file from the directory. This needs to be done so it does not end up in the new .war file. # I wanted to change the "Company Home" that seems to be everywhere to something that says MBARI. ## Edited ./WEB-INF/classes/alfresco/messages/webclient.properties and changed company_home from 'Company Home' to 'MBARI' ## Edited ./WEB-INF/classes/alfresco/messages/webclient_en_US.properties and changed company_home from 'Company Home' to 'MBARI' ## I edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces.properties and changed the first two lines to read {noformat} spaces.company_home.name=MBARI spaces.company_home.description=The root space for MBARI {noformat} ## Edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces_en_US.properties and made the same changes as the previous step {tip} This took a bit to find all these, and to be honest, I am not sure which one actually made the change on the GUI, but I suspect it was the _en_US ones. {tip} # When users are imported via LDAP, user spaces get created automatically. In order to put them where I wanted them to go (instead of right in the Company Home), I edited the ./WEB-INF/classes/alfresco/authentication-services-context.xml file. In the file there is a bean with an name of personalHomeFolderProvider. There is a property name 'path' and I added {noformat} /${spaces.user_homes.childname} {noformat} to the end to try to get them to create the user spaces there instead of in the Company Home. The final bean XML looks like: {noformat} /${spaces.company_home.childname}/${spaces.user_homes.childname} ${spaces.store} false All All {noformat} # I wanted to change the logo that is used. I attached the replacement logo [CLT:here|^AlfrescoLogo32.png]. Copy this to ./images/logo and overwrite the one that is there. # In order to setup SSL for the application (will do that later), edit ./WEB-INF/web.xml and add the following {noformat} Login Pages /* CONFIDENTIAL {noformat} right before the ending tag at the bottom of the file. # Now in order to change the default behavior so that all content is versioned from the start, I edited the .\WEB-INF\classes\alfresco\model\contentModel.xml and searched for the content type definition block. {noformat} Content cm:cmobject true d:content false true false true {noformat} and added the following block right before the ending tag: {noformat} cm:versionable {noformat} so the final block looks like: {noformat} Content cm:cmobject true d:content false true false true cm:versionable {noformat} # Lastly, I wanted to redirect the log files to a separate disk. This is done because in the Windows hardening process, most of the disk space ends up on drive D: where alfresco does not live. The log files quickly fill up the small C: drive. To to this, I edited the .\WEB-INF\classes\log4j.properties and changed the log file appender location to point to a directory that was created on the D: drive called D:/alf_logs. # That takes care of all the changes to the WAR file. We can now put it back into .war form. # While you are in the directory you expanded the war file in, run ## jar cvfm alfresco.war META-INF\MANIFEST.MF . # You should now have an alfresco.war file in the directory. Move that back to the alfresco install and overwrite the existing one. # Most users like the details view, so I set the default to that by editing c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions\web-client-config-custom.xml and added: {noformat} details 20
20
20 {noformat} right before the closing tag. # Now in order to use MBARI accounts, NTLM authentication was turned on and then chained with the native Alfresco accounts so that we could have non-MBARI accounts on the Alfresco server. ## In order to enable NTLM and native Alfresco authentication, I had to edit two files. For simplicity I have just attached them here and they can be downloaded and installed in the extensions directory. ### The first file is the [CLT:ntlm-authentication-context.xml|^ntlm-authentication-context.xml] file. This configures and enables NTLM authentication. ### The next file was the [CLT:chaining-authentication-context.xml|^chaining-authentication-context.xml] file which enabled Alfresco authentication and chained it together with the NTLM authentication from the previous file. # Then in order to setup CIFS on the server, I edited the file-servers-custom.xml file to look like the attached [CLT:file-servers-custom.xml|^file-servers-custom.xml] file. # In order to grant certain accounts admin privs, I created a new custom-authority-services-context.xml in the same directory as the ldap-authentication-context.xml file and added {noformat} kgomes admin administrator {noformat} # In order for Alfresco to handle all port 80 traffic, I changed Tomcat so that it takes port 80 and SSL goes over port 443. So I edited the c:\Alfresco\tomcat\conf\server.xml file and changed the 8080 port to 80 and the 8443 port to 443 (the 443 change is done in two places). # Now I needed to setup the SSL for the web traffic. Cathy Sewell was instrumental in getting this working. She ordered a new certificate specifically for alfresco and put it in the c:\local\cert folder. Here are the instructions for what she did to get the certficate installed. {noformat} SSL certificate for server Alfresco - 1/2/08 C:\bin\Java\jrockit-R27.1.0-jre1.6.0_02\bin>keytool -genkey -alias tomcat -keyalg RSA -keystore tomcat.keystore What is your first and last name? [alfresco.mbari.org]: What is the name of your organizational unit? [IS]: What is the name of your organization? [MBARI]: What is the name of your City or Locality? [Moss Landing]: What is the name of your State or Province? [CD]: CA What is the two-letter country code for this unit? [US]: Is CN=alfresco.mbari.org, OU=IS, O=MBARI, L=Moss Landing, ST=CA, C=US correct? [no]: y Enter key password for (RETURN if same as keystore password): C:\bin\Java\jrockit-R27.4.0-jre1.6.0_02\bin>keytool -certreq -keyalg RSA -alias tomcat -file certreq.csr -keystore tomcat.keystore Enter keystore password: Generated certificate request file, certreq.csr, was submitted to SSL provider. Certificate provider sent certificate file (alfresco.mbari.org.crt), along with gd_bundle.crt, gd_cross_intermediate.crt, and gd_intermediate.crt. Additionally, I downloaded valicert_class2_root.cer from their website. These files were stored in c:\local\cert. The following commands were used to add them to the tomcat keystore: C:\bin\Java\jrockit-R27.4.0-jre1.6.0_02\bin>keytool -import -alias root -keystore tomcat.keystore -trustcacerts -file c:\local\cert\valicert_class2_root.cer Enter keystore password: Certificate already exists in system-wide CA keystore under alias Do you still want to add it to your own keystore? [no]: y Certificate was added to keystore C:\bin\Java\jrockit-R27.4.0-jre1.6.0_02\bin>keytool -import -alias cross -keystore tomcat.keystore -trustcacerts -file c:\local\cert\gd_cross_intermediate.crt Enter keystore password: Certificate was added to keystore C:\bin\Java\jrockit-R27.4.0-jre1.6.0_02\bin>keytool -import -alias intermed -keystore tomcat.keystore -trustcacerts -file c:\local\cert\gd_intermediate.crt Enter keystore password: Certificate was added to keystore C:\bin\Java\jrockit-R27.4.0-jre1.6.0_02\bin>keytool -import -alias tomcat -keystore tomcat.keystore -trustcacerts -file c:\local\cert\alfresco.mbari.org.crt Enter keystore password: Certificate reply was installed in keystore {noformat} # I edited the c:\bin\alfresco\tomcat\conf\server.xml file and uncommented the SSL section and edited to look like that shown below. {noformat} {noformat} # Since I was in the server.xml file, I went ahead and changed it so that the default webapp was alfresco so that you would get alfresco anytime you went to the base URL. I did this by adding: {noformat} {noformat} as the last line of the tag section (right before the closing tag). {note} You will also notice the Valve tag that I had to add to turn off proxy cache disabling so that IE clients would work correctly over SSL. Gotta love M$. {note} # I copied the enterprise-network-unlimited.lic file into the c:\Alfresco\tomcat\shared\classes\alfresco\extensions\license directory # Just to keep things clean, I edited the c:\bin\alfresco\alfresco.bat file and put 'rem' in front of the second JAVA_OPTS set as I am using Java 6. # Now after you run it for the first time and the database structure gets created, you can't restart it because you get: {noformat} java.sql.SQLException: Column names in each table must be unique. Column name 'ID_' in table 'JBPM_ACTION' is specified more than once. {noformat} Sigh, so in order to keep Alfresco from hurting itself, I had to turn off the schema updates. This is done by editing the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions\custom-repository.properties and adding the following: {noformat} db.schema.update=false {noformat} and then restarting alfresco. # To install Alfresco as a Windows Service use a command prompt and enter the following: {noformat} cd c:\bin\alfresco\tomcat\bin service.bat install alfresco tomcat5.exe //US//alfresco --DisplayName "Alfresco Server" tomcat5.exe //US//alfresco --JvmMs=512 --JvmMx=1024 --JvmSs=64 tomcat5.exe //US//alfresco --JavaHome=c:/bin/Java/jrockit-R27.4.0-jdk1.6.0_02 tomcat5.exe //US//alfresco --Environment ALF_HOME=c:/bin/alfresco/ tomcat5.exe //US//alfresco --Environment PATH=c:/bin/alfresco/bin;%PATH% tomcat5.exe //US//alfresco --StartPath c:/bin/alfresco --Startup auto {noformat} # To uninstall the service, at a later time, do the following: {noformat} cd c:\bin\alfresco\tomcat\bin service.bat uninstall alfresco {noformat} # To edit your service settings at any time: {noformat} cd c:\alfresco\tomcat\bin tomcat5w.exe //ES//alfresco {noformat} {warning} These next couple of steps had to be taken to install a patch from Alfresco for an issue with bulk uploads I was having. Essentially when file and path structures get really long and nasty, Alfresco was throwing an error and bailing out. This patch (two Java classes) fixed that issue. {warning} # Next, I downloaded the attached [CLT:JAR|^act2139.jar] file and copied it to the c:\bin\alfresco\tomcat\webapps\alfresco\WEB-INF\classes directory. # I shutdown Alfresco and then unjarred the file to install the new classes. They are: ## org/alfresco/filesys/smb/server/SMBSrvPacket.class ## org/alfresco/filesys/util/DataBuffer.class # I would assume since they do not overwrite anything, that this location is further up in the class loader and so it will load these new classes first. # I deleted the act2139.jar file and the META-INF directory that the unjarring process created. # In order to install certain modules (like the email listener), I had to get the Alfresco Module Manager from the customers.alfresco.com download site. I downloaded the alfresco-mmt-2.1.1.jar file locally so I could use it to install modules. # I then downloaded the email listener module from [http://forge.alfresco.com/projects/email-listener/]. It came as a zip file, so I unzipped it and it created a folder with the appropriate emailListener.amp in it. # Make another backup copy of the alfresco.war file and put somewhere in case you want to roll this back. # Open a command prompt windows and cd to the location where the Alfresco Module Manager jar is. # Run the following: {noformat} java -jar alfresco-mmt-2.1.1.jar path_to_emailListener.amp path_to_alfresco.war {noformat} So for me this looked like: {noformat} java -jar alfresco-mmt-2.1.1.jar .\email-listener_2.1RC2\emailListener.amp c:\bin\alfresco\tomcat\webapps\alfresco.war {noformat} # You should be able to verify the install by running: {noformat} java -jar alfresco-mmt-2.1.1.jar list c:\bin\alfresco\tomcat\webapps\alfresco.war {noformat} and you should see something like: {noformat} Module 'emailListener' installed in 'c:\bin\alfresco\tomcat\webapps\alfresco.war' - Title: EmailListener - Version: 2.1 - Install Date: Fri Dec 07 08:43:10 PST 2007 - Desription: EmailListener Module {noformat} # Finally, to start the service, just go into your Windows Service control panel and locate the service that is now named 'Alfresco Server'. You can start and stop Alfresco from this control panel. {note:title=Database Migrations} For the alfresco.mbari.org installation, we moved the back end database a couple of times for performance and management reasons. The first move was to backup the database from solstice.shore.mbari.org to the SQL 2005 server called capricorn. We did this because 2005 was the officially supported DB and we were experiencing some strange issues. It ran fine on capricorn for a long while, but for licensing reasons, we wanted to consolidate the DB onto a newer SQL Server 2008 machine called equinox.shore.mbari.org. In order to point Alfresco at a different database, I edited the custom-repository.properties file located in the {noformat}c:\bin\alfresco\tomcat\shared\classes\alfresco\extension{noformat} directory. Here is what the final result looked like with the previous two configurations commented out. {noformat} # # SQLServer connection (requires jtds-1.2.jar or equivalent - http://jtds.sourceforge.net/) # db.driver=net.sourceforge.jtds.jdbc.Driver # DB on Solstice #db.url=jdbc:jtds:sqlserver://solstice.shore.mbari.org/Alfresco;domain=SHORE;user=DB_Collaboration;password=T00l%W#Use # DB on capricorn #db.url=jdbc:jtds:sqlserver://capricorn.shore.mbari.org/Alfresco;domain=SHORE;user=DB_Collaboration;password=T00l%W#Use # DB on equinox db.url=jdbc:jtds:sqlserver://equinox.shore.mbari.org/Alfresco;domain=SHORE;user=DB_Collaboration;password=T00l%W#Use {noformat} I also downloaded the most recent jtds driver (1.2.5) and installed it in the c:\bin\alfresco\tomcat\common\lib directory and removed the old version. {note} h1. Content Migration Now, in order to migrate content from old alfresco and normal file structures, I did the following: h3. For content already in alfresco: # Navigate to the space whose contents you want to migrate. For example, let's say I want to migrate the stuff from my personal space. I would navigate (using the WebUI) to the /MBARI/User Homes/kgomes space. You should see the contents of the kgomes folder from this view. # Click on 'More actions->View Details'. # On the right hand side, click on 'Export'. # For package name, I usually enter the space name followed by '_export', but it doesn't really matter. # Click on the link that says 'Click here to select the destination' and select somewhere that you will be able to download the .acp file from. # Select 'Current Space'. # Select 'Include Children'. # Uncheck 'Include this space' unless you have content (documents) in this specific folder (anything other than folders) that you want to migrate. This is a bit tricky, but there are two ways to do this. If you want to have the top level folder created, use the 'Include this space' and that will create the top level folder. Otherwise, if will expand into the folder in which you import the .acp file into. This is important in cases where the folder has already been created for you (like with user homes) and you have to migrate content into that folder. If you have the option to create the top level directory, by all means do so. # Uncheck 'Export in background' so you can force it to happen and you know when it is complete.]]> 19038344 10944727 $5000 Unit Cost | $30,000 | $ | | 5020-000 | Books/Subscriptions | $1,850 | $ | | 5060-000 | Dues, Membership, Licenses | $5,720 | $ | | 5130-000 | Outside Srvc - General | $7,500 | $ | | 5150-000 | Outside Srvc - Maint Contracts | $25,050 | $ | | 5300-000 | Supplies - Computer (Hardware) | $11,875 | $ | | 5310-000 | Supplies - Computer (Software) | $10,180 | $ | | 5320-000 | Supplies - Engineering Lab | $17,850 | $ | | 5330-000 | Supplies - Non-Capitalized Equipment | $13,100 | $ | | *Total* | | $123,125 | $ | {panel} {column} {section} ]]> 10911964 10944729 $5000 Unit Cost | $30,000 | $ | | 5020-000 | Books/Subscriptions | $1,850 | $ | | 5060-000 | Dues, Membership, Licenses | $5,720 | $ | | 5130-000 | Outside Srvc - General | $7,500 | $ | | 5150-000 | Outside Srvc - Maint Contracts | $25,050 | $ | | 5300-000 | Supplies - Computer (Hardware) | $11,875 | $ | | 5310-000 | Supplies - Computer (Software) | $10,180 | $ | | 5320-000 | Supplies - Engineering Lab | $17,850 | $ | | 5330-000 | Supplies - Non-Capitalized Equipment | $13,100 | $ | | *Total* | | $123,125 | $ | {panel} {column} {section} ]]> 10911966 10944731 $5000 Unit Cost | $30,000 | $ | | 5020-000 | Books/Subscriptions | $1,850 | $ | | 5060-000 | Dues, Membership, Licenses | $5,720 | $ | | 5130-000 | Outside Srvc - General | $7,500 | $ | | 5150-000 | Outside Srvc - Maint Contracts | $25,050 | $ | | 5300-000 | Supplies - Computer (Hardware) | $11,875 | $ | | 5310-000 | Supplies - Computer (Software) | $10,180 | $ | | 5320-000 | Supplies - Engineering Lab | $17,850 | $ | | 5330-000 | Supplies - Non-Capitalized Equipment | $13,100 | $ | | *Total* | | $123,125 | $ | {panel} {column} {section} ]]> 10911968 10944733 $5000 Unit Cost | $30,000 | $ | | 5020-000 | Books/Subscriptions | $1,850 | $ | | 5060-000 | Dues, Membership, Licenses | $5,720 | $ | | 5130-000 | Outside Srvc - General | $7,500 | $ | | 5150-000 | Outside Srvc - Maint Contracts | $25,050 | $ | | 5300-000 | Supplies - Computer (Hardware) | $11,875 | $ | | 5310-000 | Supplies - Computer (Software) | $10,180 | $ | | 5320-000 | Supplies - Engineering Lab | $17,850 | $ | | 5330-000 | Supplies - Non-Capitalized Equipment | $13,100 | $ | | *Total* | | $123,125 | $ | {panel} {column} {section} ]]> 10911970 10944734 10911971 10944736 10911973 10944737 10911974 10944742 10911979 10944740 10911977 10944739 10911976 10944746 10911983 10944750 10911988 10944749 10911987 10944753 10911991 10944752 10911990 10944757 10911995 16023620 15990853 10944755 10911993 16023622 15990855 10944761 10911999 16023624 15990857 10944759 10911997 16023626 127.0.0.1 8443 8443 {noformat} {note} # I restarted Bamboo to verify that the SSL connection works. # I then shutdown the Bamboo installation and followed the instructions [here|http://confluence.atlassian.com/display/CROWD/Integrating+Crowd+with+Atlassian+Bamboo] to integrate it with Crowd. Below are the specific things I had to do for our installation ## In order to keep the default groups of bamboo-admin and bamboo-users out of our LDAP, I created those two groups in the MBARI Crowd directory and then created a bambooadmin account that belongs to both. That meets the requirements of Bamboo and does not force our I.S. group to have to have bamboo-admin and bamboo-user groups in our LDAP.]]> 15990859 10944766 10912004 16023628 127.0.0.1 8443 8443 {noformat} {note} # I restarted Bamboo to verify that the SSL connection works. # I then shutdown the Bamboo installation and followed the instructions [here|http://confluence.atlassian.com/display/CROWD/Integrating+Crowd+with+Atlassian+Bamboo] to integrate it with Crowd. Below are the specific things I had to do for our installation ## In order to keep the default groups of bamboo-admin and bamboo-users out of our LDAP, I created those two groups in the MBARI Crowd directory and then created a bambooadmin account that belongs to both. That meets the requirements of Bamboo and does not force our I.S. group to have to have bamboo-admin and bamboo-user groups in our LDAP. ## The rest of the configuration was pretty straightforward except for the fact that Crowd is now using SSL and the connection between build-server and crowd was over SSL. This caused much grief as the connection was not trusted so I finally found some instructions on how to get around that [here|http://blogs.sun.com/andreas/entry/no_more_unable_to_find]. After I ran the program attached and installed the keystore in the java jre/lib/security directory, all was well and I could authenticate into Bamboo using MBARI's LDAP and MBARI Crowd directory.]]> 15990861 10944763 10912001 10944764 10912002 16023630 127.0.0.1 8443 8443 {noformat} {note} # I restarted Bamboo to verify that the SSL connection works. # I then shutdown the Bamboo installation and followed the instructions [here|http://confluence.atlassian.com/display/CROWD/Integrating+Crowd+with+Atlassian+Bamboo] to integrate it with Crowd. Below are the specific things I had to do for our installation ## In order to keep the default groups of bamboo-admin and bamboo-users out of our LDAP, I created those two groups in the MBARI Crowd directory and then created a bambooadmin account that belongs to both. That meets the requirements of Bamboo and does not force our I.S. group to have to have bamboo-admin and bamboo-user groups in our LDAP. ## The rest of the configuration was pretty straightforward except for the fact that Crowd is now using SSL and the connection between build-server and crowd was over SSL. This caused much grief as the connection was not trusted so I finally found some instructions on how to get around that [here|http://blogs.sun.com/andreas/entry/no_more_unable_to_find]. After I ran the program attached and installed the keystore in the java jre/lib/security directory, all was well and I could authenticate into Bamboo using MBARI's LDAP and MBARI Crowd directory. # The last step was to get all this running as a different user. ## I shutdown bamboo. ## I then did a 'chown -R root:root /opt/Bamboo' to make sure that the default ownership of all the files was root ## I did a 'chown -R DB_Collaboration:DB_Collaboration /data/Bamboo' to make sure the DB_Collaboration account owned all the bamboo data. ## I then went in to the /opt/Bamboo directory and gave ownership of the following files and directories to DB_Collaboration. ### atlassian-bamboo.log ### logs ## I then created the /etc/init.d/bamboo script: {noformat} #!/bin/sh # Startup script for bamboo # # chkconfig: 2345 99 01 # description: Atlassian Bamboo # pidfile: /var/run/bamboo.pid . /etc/rc.d/init.d/functions BAMBOO_HOME=/data/Bamboo BAMBOO_INSTALL=/opt/Bamboo BAMBOO_USER=DB_Collaboration export BAMBOO_HOME NAME=bamboo BPID=${BAMBOO_INSTALL}/bamboo.pid PID=/var/run/${NAME}.pid cd ${BAMBOO_INSTALL} if [ _$1 = _condrestart ]; then su - ${BAMBOO_USER} -c " cd ${BAMBOO_INSTALL} && ${BAMBOO_INSTALL}/bamboo.sh stop && ${BAMBOO_INSTALL}/bamboo.sh start " else su - ${BAMBOO_USER} -c " cd ${BAMBOO_INSTALL} && ${BAMBOO_INSTALL}/bamboo.sh $@ " fi RC=$? if [ -f $BPID ]; then cp -- $BPID $PID touch /var/lock/subsys/${NAME} else rm -- $PID /var/lock/subsys/${NAME} 2>/dev/null fi exit $RC {noformat} # I made it executable by all and changed the ownership to root:root # I then ran the following to configure it to start: {noformat} service --add bamboo chkconfig bamboo on service bamboo start {noformat}]]> 15990863 10944770 10912008 10944768 10912006 16023618 tag on port 8085 so that the straight http port was closed.]]> 15990851 10944658 10911895 16023614 15990847 19071195 tag on port 8085 so that the straight http port was closed. # I.S. then opened up port 8443 to the world and ]]> 19038429 19071197 tag on port 8085 so that the straight http port was closed. # I.S. then opened up port 8443 to the world h5. OpenID # I enabled CrowdID on this server as well. # Mike Godin found some redirects were not happening correctly: {noformat} I'm wondering if maybe it's a hostname issue. The redirections I see are: #1 from login page, GET https://crowd.mbari.org:8443/openidserver/server.openid?openid.assoc_handle= #2 redirected GET to https://crowd.mbari.org:8443/openidserver/secure/interaction/allowauthentication!default.action #3 redirected GET to https://localhost:8443/openidserver !!!! It should have redirected to https://crowd.mbari.org:8443/openidserver Weird thing is that the redirection in step 2 is correct. But for some reason crowd.mbari.org forgets it's host name in step 3. I guess this is why things work when a user is already logged into crowd, because only steps #1 and #2 need to occur. {noformat} On the web I found this: {noformat} I found out the solution ! In crowd-openidserver-webapp\WEB-INF\classes\crowd.properties the following values are set: application.login.url http://localhost:8095/openidserver crowd.server.url http://localhost:8095/crowd/services/ After changing "localhost" to the the correct hostname/ip-address, the redirect is working as expected. {noformat} I also made this change and I am waiting to hear from Mike G. ]]> 19038431 10944664 10911901 16023594 15990827 15664406 15631667 16023592 15990825 10944659 10911896 16023590 15990823 10944661 10911898 10944662 10911899 16023588 15990821 10944671 10911908 10944672 10911909 10944673 10911910 16023599 15990832 16023597 15990830 10944669 10911906 16023595 15990828 10944670 10911907 10944682 10911919 16023576 15990809 15664422 15631683 10944680 10911917 16023578 15990811 10944679 10911916 15664420 15631681 16023572 15990805 10944677 10911914 10944675 10911912 10944690 10911927 10944688 10911925 16023586 15990819 10944686 10911923 10944684 10911921 10944698 10911935 10944695 10911932 10944696 10911933 10944693 10911930 16023556 15990788 10944691 10911928 16023558 15990790 10944705 10911942 10944706 10911943 10944703 10911940 16023570 15990803 9830553 9797784 10944702 10911939 10944700 10911937 9830552 9797783 10944527 10911760 11108363 11141122 2009-11-04 17:23:10.217 2009-11-04 17:23:10.217 11108362 11141122 2009-11-04 17:23:10.213 2009-11-04 17:23:10.213 10944529 10911762 24085049 24052289 11108365 11141122 2009-11-04 17:23:10.230 2009-11-04 17:23:10.230 11108364 11141122 2009-11-04 17:23:10.223 2009-11-04 17:23:10.223 19071067 19038300 11108367 11141122 2009-11-04 17:23:10.240 2009-11-04 17:23:10.240 11108366 11141122 2009-11-04 17:23:10.233 2009-11-04 17:23:10.233 19071069 19038302 11108369 11141122 2009-11-04 17:23:10.250 2009-11-04 17:23:10.250 11108368 11141122 2009-11-04 17:23:10.243 2009-11-04 17:23:10.243 11108371 11141121 2009-11-05 08:52:57.610 2009-11-05 08:52:57.610 11108370 11141122 2009-11-05 08:31:34.793 2009-11-05 08:31:34.793 19071065 19038298 24085052 24052292 24085053 24052293 18285341 18252590 18285340 18252589 11108353 11141121 2009-11-04 16:14:11.307 2009-11-04 16:14:11.307 11108354 11141121 2009-11-04 16:14:11.363 2009-11-04 16:14:11.363 11108355 11141121 2009-11-04 16:14:11.367 2009-11-04 16:14:11.367 11108356 11141121 2009-11-04 16:14:11.373 2009-11-04 16:14:11.373 11108357 11141121 2009-11-04 16:14:11.377 2009-11-04 16:14:11.377 11108358 11141121 2009-11-04 16:14:11.383 2009-11-04 16:14:11.383 19071043 19038275 11108359 11141121 2009-11-04 16:14:11.387 2009-11-04 16:14:11.387 11108360 11141121 2009-11-04 16:14:11.390 2009-11-04 16:14:11.390 11108361 11141122 2009-11-04 17:23:10.183 2009-11-04 17:23:10.183 24085018 ** response ** 0 * Channel 1 Power Control = 0 (Off) ** $1PC0 ** Response: ** 0 * Channel 1 Power Control = 1 (On) ** $1PC1 ** Response: ** 1 * Channel 1 Power Read ** $1PR ** Response: ** 1 ]]> 24052258 24085026 ** response ** 0 * Channel 1 Power Control = 0 (Off) ** $1PC0 ** Response: ** 0 * Channel 1 Power Control = 1 (On) ** $1PC1 ** Response: ** 1 * Channel 1 Power Read ** $1PR ** Response: ** 1 * Read Block ** $1RB read temperature sensor block (4 channels) ** $5RB read pH sensor block (Seabird 18s) ** Response: ** \*+02712.00 ** \*+00200.00 ** \*+00125.76 ** \*+00347.95 * Read Data ** $1RD read tDGH channel 1 (temperature ch 1) ** $2RD read tDGH channel 2 (temperature ch 2) ** $3RD read tDGH channel 3 (temperature ch 3) ** $4RD read tDGH channel 4 (temperature ch 4) ** $5RD read tDGH channel 5 (pH sensor ch 1) ** $6RD read tDGH channel 6 (pH sensor ch 2) ** $7RD read tDGH channel 7 (pH sensor ch 3) ** $8RD read tDGH channel 8 (pH sensor ch 4) ** $9RD read tDGH channel 9 (pH sensor ch 5)]]> 24052266 24085024 ** response ** 0 * Channel 1 Power Control = 0 (Off) ** $1PC0 ** Response: ** 0 * Channel 1 Power Control = 1 (On) ** $1PC1 ** Response: ** 1 * Channel 1 Power Read ** $1PR ** Response: ** 1 * Read Block ** $1RB read temperature sensor block (4 channels) ** $5RB read pH sensor block (Seabird 18s) ** Response: ** \*+02712.00 ** \*+00200.00 ** \*+00125.76 ** \*+00347.95 * Read Data ** $1RD read tDGH channel 1 (temperature ch 1) ** $2RD read tDGH channel 2 (temperature ch 2) ** $3RD read tDGH channel 3 (temperature ch 3) ** $4RD read tDGH channel 4 (temperature ch 4) ** $5RD read tDGH channel 5 (pH sensor ch 1) ** $6RD read tDGH channel 6 (pH sensor ch 2) ** $7RD read tDGH channel 7 (pH sensor ch 3) ** $8RD read tDGH channel 8 (pH sensor ch 4) ** $9RD read tDGH channel 9 (pH sensor ch 5)]]> 24052264 24085021 ** response ** 0 * Channel 1 Power Control = 0 (Off) ** $1PC0 ** Response: ** 0 * Channel 1 Power Control = 1 (On) ** $1PC1 ** Response: ** 1 * Channel 1 Power Read ** $1PR ** Response: ** 1 * Read Block ** $1RB read temperature sensor block (4 channels) ** $5RB read pH sensor block (Seabird 18s) ** Response: ** *+27123.00 ** *+00200.00 ** *+00125.76 ** *+00347.95 * Read Data ** $1RD read tDGH channel 1 (temperature ch 1) ** $2RD read tDGH channel 2 (temperature ch 2) ** $3RD read tDGH channel 3 (temperature ch 3) ** $4RD read tDGH channel 4 (temperature ch 4) ** $5RD read tDGH channel 5 (pH sensor ch 1) ** $6RD read tDGH channel 6 (pH sensor ch 2) ** $7RD read tDGH channel 7 (pH sensor ch 3) ** $8RD read tDGH channel 8 (pH sensor ch 4) ** $9RD read tDGH channel 9 (pH sensor ch 5)]]> 24052261 24085022 ** response ** 0 * Channel 1 Power Control = 0 (Off) ** $1PC0 ** Response: ** 0 * Channel 1 Power Control = 1 (On) ** $1PC1 ** Response: ** 1 * Channel 1 Power Read ** $1PR ** Response: ** 1 * Read Block ** $1RB read temperature sensor block (4 channels) ** $5RB read pH sensor block (Seabird 18s) ** Response: ** \*+02712.00 ** \*+00200.00 ** \*+00125.76 ** \*+00347.95 * Read Data ** $1RD read tDGH channel 1 (temperature ch 1) ** $2RD read tDGH channel 2 (temperature ch 2) ** $3RD read tDGH channel 3 (temperature ch 3) ** $4RD read tDGH channel 4 (temperature ch 4) ** $5RD read tDGH channel 5 (pH sensor ch 1) ** $6RD read tDGH channel 6 (pH sensor ch 2) ** $7RD read tDGH channel 7 (pH sensor ch 3) ** $8RD read tDGH channel 8 (pH sensor ch 4) ** $9RD read tDGH channel 9 (pH sensor ch 5)]]> 24052262 24085020 ** response ** 0 * Channel 1 Power Control = 0 (Off) ** $1PC0 ** Response: ** 0 * Channel 1 Power Control = 1 (On) ** $1PC1 ** Response: ** 1 * Channel 1 Power Read ** $1PR ** Response: ** 1 * Read Block ** $1RB read temperature sensor block (4 channels) ** $5RB read pH sensor block (Seabird 18s) * Read Data ** $1RD read tDGH channel 1 (temperature ch 1) ** $2RD read tDGH channel 2 (temperature ch 2) ** $3RD read tDGH channel 3 (temperature ch 3) ** $4RD read tDGH channel 4 (temperature ch 4) ** $5RD read tDGH channel 5 (pH sensor ch 1) ** $6RD read tDGH channel 6 (pH sensor ch 2) ** $7RD read tDGH channel 7 (pH sensor ch 3) ** $8RD read tDGH channel 8 (pH sensor ch 4) ** $9RD read tDGH channel 9 (pH sensor ch 5) ]]> 24052260 27590779 4.4: [https://confluence.atlassian.com/display/JIRA044/Migrating+JIRA+to+Another+Server] ## The JIRA configuration tool: [https://confluence.atlassian.com/display/JIRA044/Using+the+JIRA+Configuration+Tool] h5. Steps # (/) Create new VM named bugs.mbari.org in the DMZ # (/) Have Neil create database Jira_Temp on solstice2.shore.mbari.org # (/) Have Neil create database Jira on solstice2.shore.mbari.org # (/) Have Pat install Java 7 on bugs.shore.mbari.org # (/) Have Pete plumb holes through firewall so processes on bugs.mbari.org can get to Solstice2 # (/) Have Pat create DB_Collaboration account on bugs so it can run JIRA under that account and it can connect to solstice2 using that NT Domain account. # (/) Upgrade license on Atlassian site # (/) Log into bugs.shore.mbari.org # (/) Download 3.13.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 4.4.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 5.2.11 standalone Linux 64 bit tar.gz (not sure this version is necessary, but at least I have it) # (/) Unzip and untar the file to /opt # (/) Download latest JIRA (6.4.7 as of this writing). # (/) Unzip and untar it to /opt # Performed Test Upgrade ## (/) In order to export the current stuff in JIRA, I had to shut off access so people could not change the data while I was backing it up. ## (/) I ssh'd to oceana.mbari.org as root and edited the /opt/jira/conf/server.xml file and commented out the Connector section that had the port of 8010 to shut it off from the normal serving route. ## (/) I uncommented the 8082 port connector and the 8443 port connector so that I could still get to the server. ## (/) I stopped and started the JIRA server and in the log file I got a "keystore was tampered with..." which is not surprising. ## (/) I could then browser over to http://oceana.mbari.org:8082/jira ## (/) Then through the Administration console, I did an XML backup ## (/) I then created a tar of all the attachments in the /data/jira_3_12/attachments directory ## (/) I moved both the XML and tar files to the /root/jira-upgrade directory ## (/) I then reversed the changes to the server.xml file and shut down JIRA ## (/) I left it down during the next steps in case it went so well, I could just point people to the new server (yeah, right). ## (/) I then browsed to the crowd server on oceana and add a new application using: ### URL: http://bugs.mbari.org/jira3135 ### IP: 134.89.2.29 ### Name: JIRA3135 ### Password: (ask Kevin) :) ## (/) On bugs, I made a copy of the JIRA 3.13.5 download in the /opt directory and unzipped and untarred it. ## (/) In order to configure the crowd connection I did the following: ### (/) I scp'd the /opt/crowd/client/crowd-integration-client-1.6.jar file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I removed the existing 1.6.1 crowd client jar from the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I scp'd the /opt/crowd/client/conf/crowd.properties file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I scp'd the /opt/crowd/client/conf/crowd-ehcache.xml file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I edited the crowd.properties file on bugs to look like: {noformat} application.name JIRA3135 application.password (ask Kevin) application.login.url http://oceana.mbari.org:8095/crowd/console/ crowd.server.url http://oceana.mbari.org:8095/crowd/services/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 0 session.lastvalidation session.lastvalidation {noformat} ### (/) I edited the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/osuser.xml file to comment out the current authentication mechanism and then uncomment the crowd one. ## (/) I then edited the /opt/atlassian-jira-standalone-3.13.5/conf/server/xml file and configured the database connection to the Jira_Temp database on Solstice2. I looked like this: {noformat} {noformat} ## (/) Edit the /opt/atlassian/jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/entityengine.xml and changed it from 'hsql' to 'mssql' and delete the line with "PUBLIC" in it per the instructions in the comments in that file. ## (/) I edited the /etc/httpd/conf/httpd.conf file and created a proxy pass at the bottom of the file to point a normal URL to the default port 8080 for JIRA: {noformat} # Proxy Pass for JIRA ProxyPass http://bugs.mbari.org:8080 ProxyPassReverse http://bugs.mbari.org:8080 {noformat} ## (/) I restarted Apache ## (/) I scp'd the jtds driver from oceana to the /opt/atlassian-jira-standalone-3.13.5/common/lib directory (you could down from the internet) ## (/) I then went to the /opt/atlassian-jira-standalone-3.13.5/ directory and ran './bin/startup.sh'. From the log file, I could tell things were hanging. After some troubleshooting I am wondering if the local firewall is preventing the application to get access to the database on solstice2. I can telnet to port 1433, but I can't browse to the base http://bugs.mbari.org from anywhere but the local web browser. I have submitted a ticket. ## (/) I restarted the old JIRA with my hopes dashed :(. ## (/) Pat disabled the firewall on bugs.mbari.org but it still hung trying to connect to solstice2.shore.mbari.org. That is really, really perplexing. Neil mentioned that solstice2 is using Kerberos and solstice is not. Checking with the JTDS docs, version 1.3.1 of the driver added kerberos support, so I downloaded that driver and added the 'userKerberos=true' property to the URL in the server.xml file and restarted. Got an error about no credentials, so added user and password properties to the URL. Nope, no luck. Never did figure this one out, but I had Pat pull the VM inside the firewall and after some thrash it worked. Well, it sort of worked ... sigh. It turns out I had downloaded the standard version instead of the enterprise version. I need to redo this work ... grrr. ## (/) I deleted all the tables in the Jira_Temp database and removed the /data/jira3135/indexes directory (and recreated). ## (/) I downloaded the enterprise version of the 3.13.5 server. I made a copy in the /opt directory and unzipped and untarred the file. ## (/) I went back to crowd and edited the application to change the properties to: ### URL: http://bugs.shore.mbari.org:8080 ### IP: 134.89.12.31 ### Name: jira3135 ### Password: (ask Kevin) :) ## (/) I then repeated the steps above to get the server up and running with the following differences: ### The server name is now bugs.shore.mbari.org ### The paths given above are a little different in that they no longer say "standard" but say "enterprise" ### I deleted the proxy pass as it seemed to have issues before and this is only temporary anyway. ## (/) I then browsed to http://bugs.shore.mbari.org:8080 ## (/) It took me to the start up page and at the top was the option to 'import your existing data'. Seemed too good not to try. I clicked on the link. It asked me for the backup file location and the location where the indexes would be stored. ## (/) I copied the XML zip file and the attachments tar file to the /data/original directory. ## (/) I created the /data/jira3135/indexes and used those directories ... it fired off the import and I waited. ## (/) I tailed the log file to watch the import. Holy crap, it worked!!! I could log in and everything! I copied the results from the log file here for posterity sake: {noformat} 2015-07-22 20:55:45,156 http-8080-Processor22 INFO [jira.action.admin.DataImport] Running data import 2015-07-22 20:55:45,179 http-8080-Processor22 INFO [jira.action.admin.DataImport] Importing data.. 2015-07-22 20:55:45,186 http-8080-Processor22 INFO [jira.action.admin.DataImport] Start parsing XML with SAX Parser 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] XML successfully parsed 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] Removing all entries from the database. 2015-07-22 20:56:24,593 http-8080-Processor22 INFO [jira.action.admin.DataImport] All entries removed. 2015-07-22 20:56:24,594 http-8080-Processor22 INFO [jira.action.admin.DataImport] Started storing 410414 Generic Values 2015-07-22 21:01:51,967 http-8080-Processor22 INFO [jira.action.admin.DataImport] Finished storing Generic Values 2015-07-22 21:01:52,329 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:52,361 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:54,683 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLink' to module 'jira.user.format:profile-link-user-format'. 2015-07-22 21:01:54,724 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullName' to module 'jira.user.format:full-name-user-format'. 2015-07-22 21:01:54,773 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkSearcher' to module 'jira.user.format:profile-link-searcher-user-format'. 2015-07-22 21:01:54,784 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkExternal' to module 'jira.user.format:profile-link-external-user-format'. 2015-07-22 21:01:54,795 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkActionHeader' to module 'jira.user.format:profile-link-action-header-user-format'. 2015-07-22 21:01:54,807 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullProfile' to module 'jira.user.format:full-profile-user-format'. 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/comments 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/issues 2015-07-22 21:01:55,641 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/plugins 2015-07-22 21:01:55,867 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:01:55,871 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/issues does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:55,873 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/comments does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,033 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,257 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,889 http-8080-Processor22 ERROR [atlassian.jira.upgrade.ConsistencyCheckImpl] Attachments are turned on, but attachment path [/data/jira_3_12/attachments] invalid - disabling attachments 2015-07-22 21:02:13,904 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Detected that an upgrade is needed; existing data at build 299 2015-07-22 21:02:13,907 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Doing Upgrade... 2015-07-22 21:02:13,915 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value' succeeded 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 317 2015-07-22 21:02:13,944 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite filters - make each filter a favourite of its owner. 2015-07-22 21:02:17,822 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build319] Could not find author 'fpy' for filter with id '10040' 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite filters - make each filter a favourite of its owner.' succeeded 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 319 2015-07-22 21:02:17,995 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise Share Permissions. Move old shares to new shares. 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise Share Permissions. Move old shares to new shares.' succeeded 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 321 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Migrating the old JIRA UI colors to the new JIRA 3.13 colors 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build322] Custom color detected for jira.lf.menu.bgcolour : #336699 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Migrating the old JIRA UI colors to the new JIRA 3.13 colors' succeeded 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 322 2015-07-22 21:02:18,025 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite dashboards - make each dashboard a favourite of its owner. 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'cmcgann' for dashboard with id '10030' 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'fpy' for dashboard with id '10060' 2015-07-22 21:02:18,423 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'kanna' for dashboard with id '10040' 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite dashboards - make each dashboard a favourite of its owner.' succeeded 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 325 2015-07-22 21:02:18,625 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Reindexing all data in JIRA to include Favourites. 2015-07-22 21:02:18,648 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All starting... 2015-07-22 21:02:18,650 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 0% complete. Current index: Issue 2015-07-22 21:02:18,654 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:02:18,809 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 1% complete. Current index: Issue 2015-07-22 21:02:18,855 indexerPool-2-thread-10 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 2% complete. Current index: Issue 2015-07-22 21:02:18,899 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 3% complete. Current index: Issue 2015-07-22 21:02:18,945 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 4% complete. Current index: Issue 2015-07-22 21:02:19,012 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 5% complete. Current index: Issue . . . 2015-07-22 21:02:26,164 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 95% complete. Current index: Issue 2015-07-22 21:02:26,232 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 96% complete. Current index: Issue 2015-07-22 21:02:26,316 indexerPool-2-thread-9 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 97% complete. Current index: Issue 2015-07-22 21:02:26,771 indexerPool-2-thread-3 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: Issue 2015-07-22 21:02:27,261 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 8607ms. Indexer: DefaultIndexManager: paths: [/data/jira3135/indexes/issues, /data/jira3135/indexes/comments] 2015-07-22 21:02:27,263 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: SearchRequest 2015-07-22 21:02:27,268 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,293 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: SearchRequest 2015-07-22 21:02:27,308 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: PortalPage 2015-07-22 21:02:27,312 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,377 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: PortalPage 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 115ms. Indexer: SharedEntityIndexManager: paths: [/data/jira3135/indexes/entities/portalpage, /data/jira3135/indexes/entities/searchrequest] 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All complete. Total time: 8722ms. 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Reindexing all data in JIRA to include Favourites.' succeeded 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 326 2015-07-22 21:02:27,397 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade succeeded! Setting data build number to 360 2015-07-22 21:02:27,469 JiraQuartzScheduler_Worker-0 WARN [service.services.export.ExportService] Backup directory /data/jira_3_12/backup does not exist {noformat} {warning:title=Paths} It appears that the upgraded JIRA will still look for the attachments and the backup locations in the original places. So I created /data/jira_3_12/backup and untarred the original attachments to /data/jira_3_12 and then everything worked (including attachements) in the new JIRA. {warning} ## (/) I then used the upgraded JIRA to generate a new XML backup and stored it in /data/original/3.13.5 along with another tar of the files in /data/jira_3_12/attachments. ## (/) I then shutdown the JIRA server. *I should be ready to move on to version 4 upgrade WHEW* # Schedule upgrade date and send all hands several days in advance. # When the day arrives, send all hands announcing JIRA outage. # From the Administrator's page in our existing JIRA, perform a 'Backup Data to XML'. # Login to oceana.mbari.org as root. # Shutdown JIRA # Create a tar.gz of the /opt/atlassian-jira-enterprise-3.12.1-standalone directory # Clean up the /data/jira_3_12/backups directory by deleting all but maybe the last 5 backups. # Create a tar.gz of the JIRA home directory on ocean.mbari.org which is located at /data/jira_3_12 # scp both tar.gz files to bugs.mbari.org # login to bugs.mbari.org # Unpack the home directory tar to /data/jira # Run the installer as root (this might need IS help or sudo privs). Note that we usually install the application to /opt # Run the JIRA Configuration tool to set the jira.home to the /data/jira location # Connect to JIRA_Temp database on Solstice2 (.... more to do here, see Atlassian docs) # Migrate existing configuration over to new JIRA (I need to add more here as we added Crowd). # Start JIRA # Import backed up XML # Perform post upgrades checks and tests *Need to document steps for 4.4.5->6.X*]]> 27558013 27590762 4.4: [https://confluence.atlassian.com/display/JIRA044/Migrating+JIRA+to+Another+Server] ## The JIRA configuration tool: [https://confluence.atlassian.com/display/JIRA044/Using+the+JIRA+Configuration+Tool] h5. Steps # (/) Create new VM named bugs.mbari.org in the DMZ # (/) Have Neil create database Jira_Temp on solstice2.shore.mbari.org # (/) Have Neil create database Jira on solstice2.shore.mbari.org # (/) Have Pat install Java 7 on bugs.shore.mbari.org # (/) Have Pete plumb holes through firewall so processes on bugs.mbari.org can get to Solstice2 # (/) Have Pat create DB_Collaboration account on bugs so it can run JIRA under that account and it can connect to solstice2 using that NT Domain account. # (/) Upgrade license on Atlassian site # (/) Log into bugs.shore.mbari.org # (/) Download 3.13.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 4.4.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 5.2.11 standalone Linux 64 bit tar.gz (not sure this version is necessary, but at least I have it) # (/) Unzip and untar the file to /opt # (/) Download latest JIRA (6.4.7 as of this writing). # (/) Unzip and untar it to /opt # Performed Test Upgrade ## (/) In order to export the current stuff in JIRA, I had to shut off access so people could not change the data while I was backing it up. ## (/) I ssh'd to oceana.mbari.org as root and edited the /opt/jira/conf/server.xml file and commented out the Connector section that had the port of 8010 to shut it off from the normal serving route. ## (/) I uncommented the 8082 port connector and the 8443 port connector so that I could still get to the server. ## (/) I stopped and started the JIRA server and in the log file I got a "keystore was tampered with..." which is not surprising. ## (/) I could then browser over to http://oceana.mbari.org:8082/jira ## (/) Then through the Administration console, I did an XML backup ## (/) I then created a tar of all the attachments in the /data/jira_3_12/attachments directory ## (/) I moved both the XML and tar files to the /root/jira-upgrade directory ## (/) I then reversed the changes to the server.xml file and shut down JIRA ## (/) I left it down during the next steps in case it went so well, I could just point people to the new server (yeah, right). ## (/) I then browsed to the crowd server on oceana and add a new application using: ### URL: http://bugs.mbari.org/jira3135 ### IP: 134.89.2.29 ### Name: JIRA3135 ### Password: (ask Kevin) :) ## (/) On bugs, I made a copy of the JIRA 3.13.5 download in the /opt directory and unzipped and untarred it. ## (/) In order to configure the crowd connection I did the following: ### (/) I scp'd the /opt/crowd/client/crowd-integration-client-1.6.jar file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I removed the existing 1.6.1 crowd client jar from the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I scp'd the /opt/crowd/client/conf/crowd.properties file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I scp'd the /opt/crowd/client/conf/crowd-ehcache.xml file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I edited the crowd.properties file on bugs to look like: {noformat} application.name JIRA3135 application.password (ask Kevin) application.login.url http://oceana.mbari.org:8095/crowd/console/ crowd.server.url http://oceana.mbari.org:8095/crowd/services/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 0 session.lastvalidation session.lastvalidation {noformat} ### (/) I edited the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/osuser.xml file to comment out the current authentication mechanism and then uncomment the crowd one. ## (/) I then edited the /opt/atlassian-jira-standalone-3.13.5/conf/server/xml file and configured the database connection to the Jira_Temp database on Solstice2. I looked like this: {noformat} {noformat} ## (/) Edit the /opt/atlassian/jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/entityengine.xml and changed it from 'hsql' to 'mssql' and delete the line with "PUBLIC" in it per the instructions in the comments in that file. ## (/) I edited the /etc/httpd/conf/httpd.conf file and created a proxy pass at the bottom of the file to point a normal URL to the default port 8080 for JIRA: {noformat} # Proxy Pass for JIRA ProxyPass http://bugs.mbari.org:8080 ProxyPassReverse http://bugs.mbari.org:8080 {noformat} ## (/) I restarted Apache ## (/) I scp'd the jtds driver from oceana to the /opt/atlassian-jira-standalone-3.13.5/common/lib directory (you could down from the internet) ## (/) I then went to the /opt/atlassian-jira-standalone-3.13.5/ directory and ran './bin/startup.sh'. From the log file, I could tell things were hanging. After some troubleshooting I am wondering if the local firewall is preventing the application to get access to the database on solstice2. I can telnet to port 1433, but I can't browse to the base http://bugs.mbari.org from anywhere but the local web browser. I have submitted a ticket. ## (/) I restarted the old JIRA with my hopes dashed :(. ## (/) Pat disabled the firewall on bugs.mbari.org but it still hung trying to connect to solstice2.shore.mbari.org. That is really, really perplexing. Neil mentioned that solstice2 is using Kerberos and solstice is not. Checking with the JTDS docs, version 1.3.1 of the driver added kerberos support, so I downloaded that driver and added the 'userKerberos=true' property to the URL in the server.xml file and restarted. Got an error about no credentials, so added user and password properties to the URL. Nope, no luck. Never did figure this one out, but I had Pat pull the VM inside the firewall and after some thrash it worked. Well, it sort of worked ... sigh. It turns out I had downloaded the standard version instead of the enterprise version. I need to redo this work ... grrr. ## (/) I deleted all the tables in the Jira_Temp database and removed the /data/jira3135/indexes directory (and recreated). ## (/) I downloaded the enterprise version of the 3.13.5 server. I made a copy in the /opt directory and unzipped and untarred the file. ## (/) I went back to crowd and edited the application to change the properties to: ### URL: http://bugs.shore.mbari.org:8080 ### IP: 134.89.12.31 ### Name: jira3135 ### Password: (ask Kevin) :) ## (/) I then repeated the steps above to get the server up and running with the following differences: ### The server name is now bugs.shore.mbari.org ### The paths given above are a little different in that they no longer say "standard" but say "enterprise" ### I deleted the proxy pass as it seemed to have issues before and this is only temporary anyway. ## (/) I then browsed to http://bugs.shore.mbari.org:8080 ## (/) It took me to the start up page and at the top was the option to 'import your existing data'. Seemed too good not to try. I clicked on the link. It asked me for the backup file location and the location where the indexes would be stored. ## (/) I copied the XML zip file and the attachments tar file to the /data/original directory. ## (/) I created the /data/jira3135/indexes and used those directories ... it fired off the import and I waited. ## (/) I tailed the log file to watch the import. Holy crap, it worked!!! I could log in and everything! I copied the results from the log file here for posterity sake: {noformat} 2015-07-22 20:55:45,156 http-8080-Processor22 INFO [jira.action.admin.DataImport] Running data import 2015-07-22 20:55:45,179 http-8080-Processor22 INFO [jira.action.admin.DataImport] Importing data.. 2015-07-22 20:55:45,186 http-8080-Processor22 INFO [jira.action.admin.DataImport] Start parsing XML with SAX Parser 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] XML successfully parsed 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] Removing all entries from the database. 2015-07-22 20:56:24,593 http-8080-Processor22 INFO [jira.action.admin.DataImport] All entries removed. 2015-07-22 20:56:24,594 http-8080-Processor22 INFO [jira.action.admin.DataImport] Started storing 410414 Generic Values 2015-07-22 21:01:51,967 http-8080-Processor22 INFO [jira.action.admin.DataImport] Finished storing Generic Values 2015-07-22 21:01:52,329 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:52,361 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:54,683 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLink' to module 'jira.user.format:profile-link-user-format'. 2015-07-22 21:01:54,724 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullName' to module 'jira.user.format:full-name-user-format'. 2015-07-22 21:01:54,773 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkSearcher' to module 'jira.user.format:profile-link-searcher-user-format'. 2015-07-22 21:01:54,784 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkExternal' to module 'jira.user.format:profile-link-external-user-format'. 2015-07-22 21:01:54,795 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkActionHeader' to module 'jira.user.format:profile-link-action-header-user-format'. 2015-07-22 21:01:54,807 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullProfile' to module 'jira.user.format:full-profile-user-format'. 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/comments 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/issues 2015-07-22 21:01:55,641 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/plugins 2015-07-22 21:01:55,867 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:01:55,871 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/issues does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:55,873 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/comments does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,033 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,257 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,889 http-8080-Processor22 ERROR [atlassian.jira.upgrade.ConsistencyCheckImpl] Attachments are turned on, but attachment path [/data/jira_3_12/attachments] invalid - disabling attachments 2015-07-22 21:02:13,904 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Detected that an upgrade is needed; existing data at build 299 2015-07-22 21:02:13,907 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Doing Upgrade... 2015-07-22 21:02:13,915 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value' succeeded 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 317 2015-07-22 21:02:13,944 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite filters - make each filter a favourite of its owner. 2015-07-22 21:02:17,822 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build319] Could not find author 'fpy' for filter with id '10040' 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite filters - make each filter a favourite of its owner.' succeeded 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 319 2015-07-22 21:02:17,995 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise Share Permissions. Move old shares to new shares. 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise Share Permissions. Move old shares to new shares.' succeeded 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 321 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Migrating the old JIRA UI colors to the new JIRA 3.13 colors 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build322] Custom color detected for jira.lf.menu.bgcolour : #336699 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Migrating the old JIRA UI colors to the new JIRA 3.13 colors' succeeded 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 322 2015-07-22 21:02:18,025 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite dashboards - make each dashboard a favourite of its owner. 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'cmcgann' for dashboard with id '10030' 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'fpy' for dashboard with id '10060' 2015-07-22 21:02:18,423 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'kanna' for dashboard with id '10040' 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite dashboards - make each dashboard a favourite of its owner.' succeeded 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 325 2015-07-22 21:02:18,625 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Reindexing all data in JIRA to include Favourites. 2015-07-22 21:02:18,648 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All starting... 2015-07-22 21:02:18,650 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 0% complete. Current index: Issue 2015-07-22 21:02:18,654 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:02:18,809 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 1% complete. Current index: Issue 2015-07-22 21:02:18,855 indexerPool-2-thread-10 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 2% complete. Current index: Issue 2015-07-22 21:02:18,899 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 3% complete. Current index: Issue 2015-07-22 21:02:18,945 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 4% complete. Current index: Issue 2015-07-22 21:02:19,012 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 5% complete. Current index: Issue . . . 2015-07-22 21:02:26,164 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 95% complete. Current index: Issue 2015-07-22 21:02:26,232 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 96% complete. Current index: Issue 2015-07-22 21:02:26,316 indexerPool-2-thread-9 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 97% complete. Current index: Issue 2015-07-22 21:02:26,771 indexerPool-2-thread-3 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: Issue 2015-07-22 21:02:27,261 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 8607ms. Indexer: DefaultIndexManager: paths: [/data/jira3135/indexes/issues, /data/jira3135/indexes/comments] 2015-07-22 21:02:27,263 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: SearchRequest 2015-07-22 21:02:27,268 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,293 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: SearchRequest 2015-07-22 21:02:27,308 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: PortalPage 2015-07-22 21:02:27,312 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,377 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: PortalPage 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 115ms. Indexer: SharedEntityIndexManager: paths: [/data/jira3135/indexes/entities/portalpage, /data/jira3135/indexes/entities/searchrequest] 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All complete. Total time: 8722ms. 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Reindexing all data in JIRA to include Favourites.' succeeded 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 326 2015-07-22 21:02:27,397 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade succeeded! Setting data build number to 360 2015-07-22 21:02:27,469 JiraQuartzScheduler_Worker-0 WARN [service.services.export.ExportService] Backup directory /data/jira_3_12/backup does not exist{noformat} # Schedule upgrade date and send all hands several days in advance. # When the day arrives, send all hands announcing JIRA outage. # From the Administrator's page in our existing JIRA, perform a 'Backup Data to XML'. # Login to oceana.mbari.org as root. # Shutdown JIRA # Create a tar.gz of the /opt/atlassian-jira-enterprise-3.12.1-standalone directory # Clean up the /data/jira_3_12/backups directory by deleting all but maybe the last 5 backups. # Create a tar.gz of the JIRA home directory on ocean.mbari.org which is located at /data/jira_3_12 # scp both tar.gz files to bugs.mbari.org # login to bugs.mbari.org # Unpack the home directory tar to /data/jira # Run the installer as root (this might need IS help or sudo privs). Note that we usually install the application to /opt # Run the JIRA Configuration tool to set the jira.home to the /data/jira location # Connect to JIRA_Temp database on Solstice2 (.... more to do here, see Atlassian docs) # Migrate existing configuration over to new JIRA (I need to add more here as we added Crowd). # Start JIRA # Import backed up XML # Perform post upgrades checks and tests *Need to document steps for 4.4.5->6.X* ]]> 27557996 27590760 4.4: [https://confluence.atlassian.com/display/JIRA044/Migrating+JIRA+to+Another+Server] ## The JIRA configuration tool: [https://confluence.atlassian.com/display/JIRA044/Using+the+JIRA+Configuration+Tool] h5. Steps # (/) Create new VM named bugs.mbari.org in the DMZ # (/) Have Neil create database Jira_Temp on solstice2.shore.mbari.org # (/) Have Neil create database Jira on solstice2.shore.mbari.org # (/) Have Pat install Java 7 on bugs.shore.mbari.org # (/) Have Pete plumb holes through firewall so processes on bugs.mbari.org can get to Solstice2 # (/) Have Pat create DB_Collaboration account on bugs so it can run JIRA under that account and it can connect to solstice2 using that NT Domain account. # (/) Upgrade license on Atlassian site # (/) Log into bugs.shore.mbari.org # (/) Download 3.13.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 4.4.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 5.2.11 standalone Linux 64 bit tar.gz (not sure this version is necessary, but at least I have it) # (/) Unzip and untar the file to /opt # (/) Download latest JIRA (6.4.7 as of this writing). # (/) Unzip and untar it to /opt # Performed Test Upgrade ## (/) In order to export the current stuff in JIRA, I had to shut off access so people could not change the data while I was backing it up. ## (/) I ssh'd to oceana.mbari.org as root and edited the /opt/jira/conf/server.xml file and commented out the Connector section that had the port of 8010 to shut it off from the normal serving route. ## (/) I uncommented the 8082 port connector and the 8443 port connector so that I could still get to the server. ## (/) I stopped and started the JIRA server and in the log file I got a "keystore was tampered with..." which is not surprising. ## (/) I could then browser over to http://oceana.mbari.org:8082/jira ## (/) Then through the Administration console, I did an XML backup ## (/) I then created a tar of all the attachments in the /data/jira_3_12/attachments directory ## (/) I moved both the XML and tar files to the /root/jira-upgrade directory ## (/) I then reversed the changes to the server.xml file and shut down JIRA ## (/) I left it down during the next steps in case it went so well, I could just point people to the new server (yeah, right). ## (/) I then browsed to the crowd server on oceana and add a new application using: ### URL: http://bugs.mbari.org/jira3135 ### IP: 134.89.2.29 ### Name: JIRA3135 ### Password: (ask Kevin) :) ## (/) On bugs, I made a copy of the JIRA 3.13.5 download in the /opt directory and unzipped and untarred it. ## (/) In order to configure the crowd connection I did the following: ### (/) I scp'd the /opt/crowd/client/crowd-integration-client-1.6.jar file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I removed the existing 1.6.1 crowd client jar from the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I scp'd the /opt/crowd/client/conf/crowd.properties file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I scp'd the /opt/crowd/client/conf/crowd-ehcache.xml file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I edited the crowd.properties file on bugs to look like: {noformat} application.name JIRA3135 application.password (ask Kevin) application.login.url http://oceana.mbari.org:8095/crowd/console/ crowd.server.url http://oceana.mbari.org:8095/crowd/services/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 0 session.lastvalidation session.lastvalidation {noformat} ### (/) I edited the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/osuser.xml file to comment out the current authentication mechanism and then uncomment the crowd one. ## (/) I then edited the /opt/atlassian-jira-standalone-3.13.5/conf/server/xml file and configured the database connection to the Jira_Temp database on Solstice2. I looked like this: {noformat} {noformat} ## (/) Edit the /opt/atlassian/jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/entityengine.xml and changed it from 'hsql' to 'mssql' and delete the line with "PUBLIC" in it per the instructions in the comments in that file. ## (/) I edited the /etc/httpd/conf/httpd.conf file and created a proxy pass at the bottom of the file to point a normal URL to the default port 8080 for JIRA: {noformat} # Proxy Pass for JIRA ProxyPass http://bugs.mbari.org:8080 ProxyPassReverse http://bugs.mbari.org:8080 {noformat} ## (/) I restarted Apache ## (/) I scp'd the jtds driver from oceana to the /opt/atlassian-jira-standalone-3.13.5/common/lib directory (you could down from the internet) ## (/) I then went to the /opt/atlassian-jira-standalone-3.13.5/ directory and ran './bin/startup.sh'. From the log file, I could tell things were hanging. After some troubleshooting I am wondering if the local firewall is preventing the application to get access to the database on solstice2. I can telnet to port 1433, but I can't browse to the base http://bugs.mbari.org from anywhere but the local web browser. I have submitted a ticket. ## (/) I restarted the old JIRA with my hopes dashed :(. ## (/) Pat disabled the firewall on bugs.mbari.org but it still hung trying to connect to solstice2.shore.mbari.org. That is really, really perplexing. Neil mentioned that solstice2 is using Kerberos and solstice is not. Checking with the JTDS docs, version 1.3.1 of the driver added kerberos support, so I downloaded that driver and added the 'userKerberos=true' property to the URL in the server.xml file and restarted. Got an error about no credentials, so added user and password properties to the URL. Nope, no luck. Never did figure this one out, but I had Pat pull the VM inside the firewall and after some thrash it worked. Well, it sort of worked ... sigh. It turns out I had downloaded the standard version instead of the enterprise version. I need to redo this work ... grrr. ## (/) I deleted all the tables in the Jira_Temp database and removed the /data/jira3135/indexes directory (and recreated). ## (/) I downloaded the enterprise version of the 3.13.5 server. I made a copy in the /opt directory and unzipped and untarred the file. ## (/) I went back to crowd and edited the application to change the properties to: ### URL: http://bugs.shore.mbari.org:8080 ### IP: 134.89.12.31 ### Name: jira3135 ### Password: (ask Kevin) :) ## (/) I then repeated the steps above to get the server up and running with the following differences: ### The server name is now bugs.shore.mbari.org ### The paths given above are a little different in that they no longer say "standard" but say "enterprise" ### I deleted the proxy pass as it seemed to have issues before and this is only temporary anyway. ## (/) I then browsed to http://bugs.shore.mbari.org:8080 ## (/) It took me to the start up page and at the top was the option to 'import your existing data'. Seemed too good not to try. I clicked on the link. It asked me for the backup file location and the location where the indexes would be stored. ## (/) I copied the XML zip file and the attachments tar file to the /data/original directory. ## (/) I created the /data/jira3135/indexes and used those directories ... it fired off the import and I waited. ## (/) I tailed the log file to watch the import. Holy crap, it worked!!! I could log in and everything! I copied the results from the log file here for posterity sake: {noformat} 2015-07-22 20:55:45,156 http-8080-Processor22 INFO [jira.action.admin.DataImport] Running data import 2015-07-22 20:55:45,179 http-8080-Processor22 INFO [jira.action.admin.DataImport] Importing data.. 2015-07-22 20:55:45,186 http-8080-Processor22 INFO [jira.action.admin.DataImport] Start parsing XML with SAX Parser 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] XML successfully parsed 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] Removing all entries from the database. 2015-07-22 20:56:24,593 http-8080-Processor22 INFO [jira.action.admin.DataImport] All entries removed. 2015-07-22 20:56:24,594 http-8080-Processor22 INFO [jira.action.admin.DataImport] Started storing 410414 Generic Values 2015-07-22 21:01:51,967 http-8080-Processor22 INFO [jira.action.admin.DataImport] Finished storing Generic Values 2015-07-22 21:01:52,329 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:52,361 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:54,683 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLink' to module 'jira.user.format:profile-link-user-format'. 2015-07-22 21:01:54,724 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullName' to module 'jira.user.format:full-name-user-format'. 2015-07-22 21:01:54,773 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkSearcher' to module 'jira.user.format:profile-link-searcher-user-format'. 2015-07-22 21:01:54,784 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkExternal' to module 'jira.user.format:profile-link-external-user-format'. 2015-07-22 21:01:54,795 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkActionHeader' to module 'jira.user.format:profile-link-action-header-user-format'. 2015-07-22 21:01:54,807 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullProfile' to module 'jira.user.format:full-profile-user-format'. 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/comments 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/issues 2015-07-22 21:01:55,641 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/plugins 2015-07-22 21:01:55,867 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:01:55,871 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/issues does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:55,873 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/comments does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,033 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,257 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,889 http-8080-Processor22 ERROR [atlassian.jira.upgrade.ConsistencyCheckImpl] Attachments are turned on, but attachment path [/data/jira_3_12/attachments] invalid - disabling attachments 2015-07-22 21:02:13,904 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Detected that an upgrade is needed; existing data at build 299 2015-07-22 21:02:13,907 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Doing Upgrade... 2015-07-22 21:02:13,915 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value' succeeded 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 317 2015-07-22 21:02:13,944 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite filters - make each filter a favourite of its owner. 2015-07-22 21:02:17,822 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build319] Could not find author 'fpy' for filter with id '10040' 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite filters - make each filter a favourite of its owner.' succeeded 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 319 2015-07-22 21:02:17,995 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise Share Permissions. Move old shares to new shares. 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise Share Permissions. Move old shares to new shares.' succeeded 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 321 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Migrating the old JIRA UI colors to the new JIRA 3.13 colors 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build322] Custom color detected for jira.lf.menu.bgcolour : #336699 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Migrating the old JIRA UI colors to the new JIRA 3.13 colors' succeeded 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 322 2015-07-22 21:02:18,025 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite dashboards - make each dashboard a favourite of its owner. 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'cmcgann' for dashboard with id '10030' 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'fpy' for dashboard with id '10060' 2015-07-22 21:02:18,423 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'kanna' for dashboard with id '10040' 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite dashboards - make each dashboard a favourite of its owner.' succeeded 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 325 2015-07-22 21:02:18,625 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Reindexing all data in JIRA to include Favourites. 2015-07-22 21:02:18,648 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All starting... 2015-07-22 21:02:18,650 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 0% complete. Current index: Issue 2015-07-22 21:02:18,654 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:02:18,809 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 1% complete. Current index: Issue 2015-07-22 21:02:18,855 indexerPool-2-thread-10 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 2% complete. Current index: Issue 2015-07-22 21:02:18,899 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 3% complete. Current index: Issue 2015-07-22 21:02:18,945 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 4% complete. Current index: Issue 2015-07-22 21:02:19,012 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 5% complete. Current index: Issue 2015-07-22 21:02:19,321 indexerPool-2-thread-6 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 6% complete. Current index: Issue 2015-07-22 21:02:19,390 indexerPool-2-thread-3 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 7% complete. Current index: Issue 2015-07-22 21:02:19,439 indexerPool-2-thread-6 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 8% complete. Current index: Issue 2015-07-22 21:02:19,498 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 9% complete. Current index: Issue 2015-07-22 21:02:19,690 indexerPool-2-thread-9 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 10% complete. Current index: Issue 2015-07-22 21:02:19,741 indexerPool-2-thread-9 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 11% complete. Current index: Issue 2015-07-22 21:02:19,793 indexerPool-2-thread-1 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 12% complete. Current index: Issue 2015-07-22 21:02:19,884 indexerPool-2-thread-3 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 13% complete. Current index: Issue 2015-07-22 21:02:20,143 indexerPool-2-thread-10 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 14% complete. Current index: Issue 2015-07-22 21:02:20,199 indexerPool-2-thread-1 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 15% complete. Current index: Issue 2015-07-22 21:02:20,339 indexerPool-2-thread-8 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 16% complete. Current index: Issue 2015-07-22 21:02:20,431 indexerPool-2-thread-10 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 17% complete. Current index: Issue 2015-07-22 21:02:20,491 indexerPool-2-thread-2 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 18% complete. Current index: Issue 2015-07-22 21:02:20,575 indexerPool-2-thread-1 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 19% complete. Current index: Issue 2015-07-22 21:02:20,620 indexerPool-2-thread-10 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 20% complete. Current index: Issue 2015-07-22 21:02:20,661 indexerPool-2-thread-10 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 21% complete. Current index: Issue 2015-07-22 21:02:20,705 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 22% complete. Current index: Issue 2015-07-22 21:02:20,766 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 23% complete. Current index: Issue 2015-07-22 21:02:21,046 indexerPool-2-thread-4 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 24% complete. Current index: Issue 2015-07-22 21:02:21,091 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 25% complete. Current index: Issue 2015-07-22 21:02:21,136 indexerPool-2-thread-6 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 26% complete. Current index: Issue 2015-07-22 21:02:21,209 indexerPool-2-thread-8 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 27% complete. Current index: Issue 2015-07-22 21:02:21,426 indexerPool-2-thread-3 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 28% complete. Current index: Issue 2015-07-22 21:02:21,478 indexerPool-2-thread-3 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 29% complete. Current index: Issue 2015-07-22 21:02:21,523 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 30% complete. Current index: Issue 2015-07-22 21:02:21,583 indexerPool-2-thread-4 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 31% complete. Current index: Issue 2015-07-22 21:02:21,706 indexerPool-2-thread-3 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 32% complete. Current index: Issue 2015-07-22 21:02:21,755 indexerPool-2-thread-9 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 33% complete. Current index: Issue 2015-07-22 21:02:21,830 indexerPool-2-thread-4 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 34% complete. Current index: Issue 2015-07-22 21:02:21,910 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 35% complete. Current index: Issue 2015-07-22 21:02:22,033 indexerPool-2-thread-1 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 36% complete. Current index: Issue 2015-07-22 21:02:22,118 indexerPool-2-thread-4 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 37% complete. Current index: Issue 2015-07-22 21:02:22,186 indexerPool-2-thread-2 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 38% complete. Current index: Issue 2015-07-22 21:02:22,236 indexerPool-2-thread-9 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 39% complete. Current index: Issue 2015-07-22 21:02:22,369 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 40% complete. Current index: Issue 2015-07-22 21:02:22,412 indexerPool-2-thread-4 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 41% complete. Current index: Issue 2015-07-22 21:02:22,555 indexerPool-2-thread-6 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 42% complete. Current index: Issue 2015-07-22 21:02:22,613 indexerPool-2-thread-3 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 43% complete. Current index: Issue 2015-07-22 21:02:22,660 indexerPool-2-thread-3 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 44% complete. Current index: Issue 2015-07-22 21:02:22,716 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 45% complete. Current index: Issue 2015-07-22 21:02:22,789 indexerPool-2-thread-3 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 46% complete. Current index: Issue 2015-07-22 21:02:22,897 indexerPool-2-thread-6 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 47% complete. Current index: Issue 2015-07-22 21:02:22,933 indexerPool-2-thread-9 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 48% complete. Current index: Issue 2015-07-22 21:02:22,967 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 49% complete. Current index: Issue 2015-07-22 21:02:23,009 indexerPool-2-thread-6 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 50% complete. Current index: Issue 2015-07-22 21:02:23,315 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 51% complete. Current index: Issue 2015-07-22 21:02:23,351 indexerPool-2-thread-4 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 52% complete. Current index: Issue 2015-07-22 21:02:23,394 indexerPool-2-thread-3 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 53% complete. Current index: Issue 2015-07-22 21:02:23,433 indexerPool-2-thread-3 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 54% complete. Current index: Issue 2015-07-22 21:02:23,471 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 55% complete. Current index: Issue 2015-07-22 21:02:23,548 indexerPool-2-thread-4 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 56% complete. Current index: Issue 2015-07-22 21:02:23,590 indexerPool-2-thread-3 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 57% complete. Current index: Issue 2015-07-22 21:02:23,638 indexerPool-2-thread-1 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 58% complete. Current index: Issue 2015-07-22 21:02:23,740 indexerPool-2-thread-10 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 59% complete. Current index: Issue 2015-07-22 21:02:23,784 indexerPool-2-thread-4 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 60% complete. Current index: Issue 2015-07-22 21:02:23,834 indexerPool-2-thread-3 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 61% complete. Current index: Issue 2015-07-22 21:02:23,889 indexerPool-2-thread-9 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 62% complete. Current index: Issue 2015-07-22 21:02:23,944 indexerPool-2-thread-3 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 63% complete. Current index: Issue 2015-07-22 21:02:23,989 indexerPool-2-thread-8 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 64% complete. Current index: Issue 2015-07-22 21:02:24,024 indexerPool-2-thread-9 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 65% complete. Current index: Issue 2015-07-22 21:02:24,065 indexerPool-2-thread-3 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 66% complete. Current index: Issue 2015-07-22 21:02:24,239 indexerPool-2-thread-10 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 67% complete. Current index: Issue 2015-07-22 21:02:24,289 indexerPool-2-thread-1 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 68% complete. Current index: Issue 2015-07-22 21:02:24,331 indexerPool-2-thread-8 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 69% complete. Current index: Issue 2015-07-22 21:02:24,500 indexerPool-2-thread-6 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 70% complete. Current index: Issue 2015-07-22 21:02:24,545 indexerPool-2-thread-8 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 71% complete. Current index: Issue 2015-07-22 21:02:24,583 indexerPool-2-thread-9 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 72% complete. Current index: Issue 2015-07-22 21:02:24,627 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 73% complete. Current index: Issue 2015-07-22 21:02:24,674 indexerPool-2-thread-1 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 74% complete. Current index: Issue 2015-07-22 21:02:24,788 indexerPool-2-thread-2 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 75% complete. Current index: Issue 2015-07-22 21:02:24,861 indexerPool-2-thread-3 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 76% complete. Current index: Issue 2015-07-22 21:02:24,904 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 77% complete. Current index: Issue 2015-07-22 21:02:24,959 indexerPool-2-thread-10 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 78% complete. Current index: Issue 2015-07-22 21:02:24,999 indexerPool-2-thread-4 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 79% complete. Current index: Issue 2015-07-22 21:02:25,040 indexerPool-2-thread-4 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 80% complete. Current index: Issue 2015-07-22 21:02:25,083 indexerPool-2-thread-8 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 81% complete. Current index: Issue 2015-07-22 21:02:25,132 indexerPool-2-thread-4 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 82% complete. Current index: Issue 2015-07-22 21:02:25,226 indexerPool-2-thread-4 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 83% complete. Current index: Issue 2015-07-22 21:02:25,394 indexerPool-2-thread-1 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 84% complete. Current index: Issue 2015-07-22 21:02:25,433 indexerPool-2-thread-8 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 85% complete. Current index: Issue 2015-07-22 21:02:25,496 indexerPool-2-thread-6 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 86% complete. Current index: Issue 2015-07-22 21:02:25,550 indexerPool-2-thread-6 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 87% complete. Current index: Issue 2015-07-22 21:02:25,649 indexerPool-2-thread-4 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 88% complete. Current index: Issue 2015-07-22 21:02:25,693 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 89% complete. Current index: Issue 2015-07-22 21:02:25,735 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 90% complete. Current index: Issue 2015-07-22 21:02:25,808 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 91% complete. Current index: Issue 2015-07-22 21:02:25,859 indexerPool-2-thread-10 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 92% complete. Current index: Issue 2015-07-22 21:02:25,934 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 93% complete. Current index: Issue 2015-07-22 21:02:26,047 indexerPool-2-thread-3 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 94% complete. Current index: Issue 2015-07-22 21:02:26,164 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 95% complete. Current index: Issue 2015-07-22 21:02:26,232 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 96% complete. Current index: Issue 2015-07-22 21:02:26,316 indexerPool-2-thread-9 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 97% complete. Current index: Issue 2015-07-22 21:02:26,771 indexerPool-2-thread-3 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: Issue 2015-07-22 21:02:27,261 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 8607ms. Indexer: DefaultIndexManager: paths: [/data/jira3135/indexes/issues, /data/jira3135/indexes/comments] 2015-07-22 21:02:27,263 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: SearchRequest 2015-07-22 21:02:27,268 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,293 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: SearchRequest 2015-07-22 21:02:27,308 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: PortalPage 2015-07-22 21:02:27,312 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,377 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: PortalPage 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 115ms. Indexer: SharedEntityIndexManager: paths: [/data/jira3135/indexes/entities/portalpage, /data/jira3135/indexes/entities/searchrequest] 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All complete. Total time: 8722ms. 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Reindexing all data in JIRA to include Favourites.' succeeded 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 326 2015-07-22 21:02:27,397 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade succeeded! Setting data build number to 360 2015-07-22 21:02:27,469 JiraQuartzScheduler_Worker-0 WARN [service.services.export.ExportService] Backup directory /data/jira_3_12/backup does not exist{noformat} # Schedule upgrade date and send all hands several days in advance. # When the day arrives, send all hands announcing JIRA outage. # From the Administrator's page in our existing JIRA, perform a 'Backup Data to XML'. # Login to oceana.mbari.org as root. # Shutdown JIRA # Create a tar.gz of the /opt/atlassian-jira-enterprise-3.12.1-standalone directory # Clean up the /data/jira_3_12/backups directory by deleting all but maybe the last 5 backups. # Create a tar.gz of the JIRA home directory on ocean.mbari.org which is located at /data/jira_3_12 # scp both tar.gz files to bugs.mbari.org # login to bugs.mbari.org # Unpack the home directory tar to /data/jira # Run the installer as root (this might need IS help or sudo privs). Note that we usually install the application to /opt # Run the JIRA Configuration tool to set the jira.home to the /data/jira location # Connect to JIRA_Temp database on Solstice2 (.... more to do here, see Atlassian docs) # Migrate existing configuration over to new JIRA (I need to add more here as we added Crowd). # Start JIRA # Import backed up XML # Perform post upgrades checks and tests *Need to document steps for 4.4.5->6.X* ]]> 27557994 27590758 4.4: [https://confluence.atlassian.com/display/JIRA044/Migrating+JIRA+to+Another+Server] ## The JIRA configuration tool: [https://confluence.atlassian.com/display/JIRA044/Using+the+JIRA+Configuration+Tool] h5. Steps # (/) Create new VM named bugs.mbari.org in the DMZ # (/) Have Neil create database Jira_Temp on solstice2.shore.mbari.org # (/) Have Neil create database Jira on solstice2.shore.mbari.org # (/) Have Pat install Java 7 on bugs.shore.mbari.org # (/) Have Pete plumb holes through firewall so processes on bugs.mbari.org can get to Solstice2 # (/) Have Pat create DB_Collaboration account on bugs so it can run JIRA under that account and it can connect to solstice2 using that NT Domain account. # (/) Upgrade license on Atlassian site # (/) Log into bugs.shore.mbari.org # (/) Download 3.13.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 4.4.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 5.2.11 standalone Linux 64 bit tar.gz (not sure this version is necessary, but at least I have it) # (/) Unzip and untar the file to /opt # (/) Download latest JIRA (6.4.7 as of this writing). # (/) Unzip and untar it to /opt # Performed Test Upgrade ## (/) In order to export the current stuff in JIRA, I had to shut off access so people could not change the data while I was backing it up. ## (/) I ssh'd to oceana.mbari.org as root and edited the /opt/jira/conf/server.xml file and commented out the Connector section that had the port of 8010 to shut it off from the normal serving route. ## (/) I uncommented the 8082 port connector and the 8443 port connector so that I could still get to the server. ## (/) I stopped and started the JIRA server and in the log file I got a "keystore was tampered with..." which is not surprising. ## (/) I could then browser over to http://oceana.mbari.org:8082/jira ## (/) Then through the Administration console, I did an XML backup ## (/) I then created a tar of all the attachments in the /data/jira_3_12/attachments directory ## (/) I moved both the XML and tar files to the /root/jira-upgrade directory ## (/) I then reversed the changes to the server.xml file and shut down JIRA ## (/) I left it down during the next steps in case it went so well, I could just point people to the new server (yeah, right). ## (/) I then browsed to the crowd server on oceana and add a new application using: ### URL: http://bugs.mbari.org/jira3135 ### IP: 134.89.2.29 ### Name: JIRA3135 ### Password: (ask Kevin) :) ## (/) On bugs, I made a copy of the JIRA 3.13.5 download in the /opt directory and unzipped and untarred it. ## (/) In order to configure the crowd connection I did the following: ### (/) I scp'd the /opt/crowd/client/crowd-integration-client-1.6.jar file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I removed the existing 1.6.1 crowd client jar from the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I scp'd the /opt/crowd/client/conf/crowd.properties file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I scp'd the /opt/crowd/client/conf/crowd-ehcache.xml file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I edited the crowd.properties file on bugs to look like: {noformat} application.name JIRA3135 application.password (ask Kevin) application.login.url http://oceana.mbari.org:8095/crowd/console/ crowd.server.url http://oceana.mbari.org:8095/crowd/services/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 0 session.lastvalidation session.lastvalidation {noformat} ### (/) I edited the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/osuser.xml file to comment out the current authentication mechanism and then uncomment the crowd one. ## (/) I then edited the /opt/atlassian-jira-standalone-3.13.5/conf/server/xml file and configured the database connection to the Jira_Temp database on Solstice2. I looked like this: {noformat} {noformat} ## (/) Edit the /opt/atlassian/jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/entityengine.xml and changed it from 'hsql' to 'mssql' and delete the line with "PUBLIC" in it per the instructions in the comments in that file. ## (/) I edited the /etc/httpd/conf/httpd.conf file and created a proxy pass at the bottom of the file to point a normal URL to the default port 8080 for JIRA: {noformat} # Proxy Pass for JIRA ProxyPass http://bugs.mbari.org:8080 ProxyPassReverse http://bugs.mbari.org:8080 {noformat} ## (/) I restarted Apache ## (/) I scp'd the jtds driver from oceana to the /opt/atlassian-jira-standalone-3.13.5/common/lib directory (you could down from the internet) ## (/) I then went to the /opt/atlassian-jira-standalone-3.13.5/ directory and ran './bin/startup.sh'. From the log file, I could tell things were hanging. After some troubleshooting I am wondering if the local firewall is preventing the application to get access to the database on solstice2. I can telnet to port 1433, but I can't browse to the base http://bugs.mbari.org from anywhere but the local web browser. I have submitted a ticket. ## (/) I restarted the old JIRA with my hopes dashed :(. ## (/) Pat disabled the firewall on bugs.mbari.org but it still hung trying to connect to solstice2.shore.mbari.org. That is really, really perplexing. Neil mentioned that solstice2 is using Kerberos and solstice is not. Checking with the JTDS docs, version 1.3.1 of the driver added kerberos support, so I downloaded that driver and added the 'userKerberos=true' property to the URL in the server.xml file and restarted. Got an error about no credentials, so added user and password properties to the URL. Nope, no luck. Never did figure this one out, but I had Pat pull the VM inside the firewall and after some thrash it worked. Well, it sort of worked ... sigh. It turns out I had downloaded the standard version instead of the enterprise version. I need to redo this work ... grrr. ## (/) I deleted all the tables in the Jira_Temp database and removed the /data/jira3135/indexes directory (and recreated). ## (/) I downloaded the enterprise version of the 3.13.5 server. I made a copy in the /opt directory and unzipped and untarred the file. ## (/) I went back to crowd and edited the application to change the properties to: ### URL: http://bugs.shore.mbari.org:8080 ### IP: 134.89.12.31 ### Name: jira3135 ### Password: (ask Kevin) :) ## (/) I then repeated the steps above to get the server up and running with the following differences: ### The server name is now bugs.shore.mbari.org ### The paths given above are a little different in that they no longer say "standard" but say "enterprise" ### I deleted the proxy pass as it seemed to have issues before and this is only temporary anyway. ## (/) I then browsed to http://bugs.shore.mbari.org:8080 ## (/) It took me to the start up page and at the top was the option to 'import your existing data'. Seemed too good not to try. I clicked on the link. It asked me for the backup file location and the location where the indexes would be stored. ## (/) I copied the XML zip file and the attachments tar file to the /data/original directory. ## (/) I created the /data/jira3135/indexes and used those directories ... it fired off the import and I waited. # Schedule upgrade date and send all hands several days in advance. # When the day arrives, send all hands announcing JIRA outage. # From the Administrator's page in our existing JIRA, perform a 'Backup Data to XML'. # Login to oceana.mbari.org as root. # Shutdown JIRA # Create a tar.gz of the /opt/atlassian-jira-enterprise-3.12.1-standalone directory # Clean up the /data/jira_3_12/backups directory by deleting all but maybe the last 5 backups. # Create a tar.gz of the JIRA home directory on ocean.mbari.org which is located at /data/jira_3_12 # scp both tar.gz files to bugs.mbari.org # login to bugs.mbari.org # Unpack the home directory tar to /data/jira # Run the installer as root (this might need IS help or sudo privs). Note that we usually install the application to /opt # Run the JIRA Configuration tool to set the jira.home to the /data/jira location # Connect to JIRA_Temp database on Solstice2 (.... more to do here, see Atlassian docs) # Migrate existing configuration over to new JIRA (I need to add more here as we added Crowd). # Start JIRA # Import backed up XML # Perform post upgrades checks and tests *Need to document steps for 4.4.5->6.X* ]]> 27557992 27590756 4.4: [https://confluence.atlassian.com/display/JIRA044/Migrating+JIRA+to+Another+Server] ## The JIRA configuration tool: [https://confluence.atlassian.com/display/JIRA044/Using+the+JIRA+Configuration+Tool] h5. Steps # (/) Create new VM named bugs.mbari.org in the DMZ # (/) Have Neil create database Jira_Temp on solstice2.shore.mbari.org # (/) Have Neil create database Jira on solstice2.shore.mbari.org # (/) Have Pat install Java 7 on bugs.shore.mbari.org # (/) Have Pete plumb holes through firewall so processes on bugs.mbari.org can get to Solstice2 # (/) Have Pat create DB_Collaboration account on bugs so it can run JIRA under that account and it can connect to solstice2 using that NT Domain account. # (/) Upgrade license on Atlassian site # (/) Log into bugs.shore.mbari.org # (/) Download 3.13.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 4.4.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 5.2.11 standalone Linux 64 bit tar.gz (not sure this version is necessary, but at least I have it) # (/) Unzip and untar the file to /opt # (/) Download latest JIRA (6.4.7 as of this writing). # (/) Unzip and untar it to /opt # Performed Test Upgrade ## (/) In order to export the current stuff in JIRA, I had to shut off access so people could not change the data while I was backing it up. ## (/) I ssh'd to oceana.mbari.org as root and edited the /opt/jira/conf/server.xml file and commented out the Connector section that had the port of 8010 to shut it off from the normal serving route. ## (/) I uncommented the 8082 port connector and the 8443 port connector so that I could still get to the server. ## (/) I stopped and started the JIRA server and in the log file I got a "keystore was tampered with..." which is not surprising. ## (/) I could then browser over to http://oceana.mbari.org:8082/jira ## (/) Then through the Administration console, I did an XML backup ## (/) I then created a tar of all the attachments in the /data/jira_3_12/attachments directory ## (/) I moved both the XML and tar files to the /root/jira-upgrade directory ## (/) I then reversed the changes to the server.xml file and shut down JIRA ## (/) I left it down during the next steps in case it went so well, I could just point people to the new server (yeah, right). ## (/) I then browsed to the crowd server on oceana and add a new application using: ### URL: http://bugs.mbari.org/jira3135 ### IP: 134.89.2.29 ### Name: JIRA3135 ### Password: (ask Kevin) :) ## (/) On bugs, I made a copy of the JIRA 3.13.5 download in the /opt directory and unzipped and untarred it. ## (/) In order to configure the crowd connection I did the following: ### (/) I scp'd the /opt/crowd/client/crowd-integration-client-1.6.jar file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I removed the existing 1.6.1 crowd client jar from the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I scp'd the /opt/crowd/client/conf/crowd.properties file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I scp'd the /opt/crowd/client/conf/crowd-ehcache.xml file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I edited the crowd.properties file on bugs to look like: {noformat} application.name JIRA3135 application.password (ask Kevin) application.login.url http://oceana.mbari.org:8095/crowd/console/ crowd.server.url http://oceana.mbari.org:8095/crowd/services/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 0 session.lastvalidation session.lastvalidation {noformat} ### (/) I edited the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/osuser.xml file to comment out the current authentication mechanism and then uncomment the crowd one. ## (/) I then edited the /opt/atlassian-jira-standalone-3.13.5/conf/server/xml file and configured the database connection to the Jira_Temp database on Solstice2. I looked like this: {noformat} {noformat} ## (/) Edit the /opt/atlassian/jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/entityengine.xml and changed it from 'hsql' to 'mssql' and delete the line with "PUBLIC" in it per the instructions in the comments in that file. ## (/) I edited the /etc/httpd/conf/httpd.conf file and created a proxy pass at the bottom of the file to point a normal URL to the default port 8080 for JIRA: {noformat} # Proxy Pass for JIRA ProxyPass http://bugs.mbari.org:8080 ProxyPassReverse http://bugs.mbari.org:8080 {noformat} ## (/) I restarted Apache ## (/) I scp'd the jtds driver from oceana to the /opt/atlassian-jira-standalone-3.13.5/common/lib directory (you could down from the internet) ## (/) I then went to the /opt/atlassian-jira-standalone-3.13.5/ directory and ran './bin/startup.sh'. From the log file, I could tell things were hanging. After some troubleshooting I am wondering if the local firewall is preventing the application to get access to the database on solstice2. I can telnet to port 1433, but I can't browse to the base http://bugs.mbari.org from anywhere but the local web browser. I have submitted a ticket. ## (/) I restarted the old JIRA with my hopes dashed :(. ## (/) Pat disabled the firewall on bugs.mbari.org but it still hung trying to connect to solstice2.shore.mbari.org. That is really, really perplexing. Neil mentioned that solstice2 is using Kerberos and solstice is not. Checking with the JTDS docs, version 1.3.1 of the driver added kerberos support, so I downloaded that driver and added the 'userKerberos=true' property to the URL in the server.xml file and restarted. Got an error about no credentials, so added user and password properties to the URL. Nope, no luck. Never did figure this one out, but I had Pat pull the VM inside the firewall and after some thrash it worked. Well, it sort of worked ... sigh. It turns out I had downloaded the standard version instead of the enterprise version. I need to redo this work ... grrr. ## (/) I deleted all the tables in the Jira_Temp database and removed the /data/jira3135/indexes directory (and recreated). ## (/) I downloaded the enterprise version of the 3.13.5 server. I made a copy in the /opt directory and unzipped and untarred the file. ## (/) I went back to crowd and edited the application to change the properties to: ### URL: http://bugs.shore.mbari.org:8080 ### IP: 134.89.12.31 ### Name: jira3135 ### Password: (ask Kevin) :) ## (/) I then repeated the steps above to get the server up and running with the following differences: ### The server name is now bugs.shore.mbari.org ### The paths given above are a little different in that they no longer say "standard" but say "enterprise" ### I deleted the proxy pass as it seemed to have issues before and this is only temporary anyway. # Schedule upgrade date and send all hands several days in advance. # When the day arrives, send all hands announcing JIRA outage. # From the Administrator's page in our existing JIRA, perform a 'Backup Data to XML'. # Login to oceana.mbari.org as root. # Shutdown JIRA # Create a tar.gz of the /opt/atlassian-jira-enterprise-3.12.1-standalone directory # Clean up the /data/jira_3_12/backups directory by deleting all but maybe the last 5 backups. # Create a tar.gz of the JIRA home directory on ocean.mbari.org which is located at /data/jira_3_12 # scp both tar.gz files to bugs.mbari.org # login to bugs.mbari.org # Unpack the home directory tar to /data/jira # Run the installer as root (this might need IS help or sudo privs). Note that we usually install the application to /opt # Run the JIRA Configuration tool to set the jira.home to the /data/jira location # Connect to JIRA_Temp database on Solstice2 (.... more to do here, see Atlassian docs) # Migrate existing configuration over to new JIRA (I need to add more here as we added Crowd). # Start JIRA # Import backed up XML # Perform post upgrades checks and tests *Need to document steps for 4.4.5->6.X* ]]> 27557990 27590765 4.4: [https://confluence.atlassian.com/display/JIRA044/Migrating+JIRA+to+Another+Server] ## The JIRA configuration tool: [https://confluence.atlassian.com/display/JIRA044/Using+the+JIRA+Configuration+Tool] h5. Steps # (/) Create new VM named bugs.mbari.org in the DMZ # (/) Have Neil create database Jira_Temp on solstice2.shore.mbari.org # (/) Have Neil create database Jira on solstice2.shore.mbari.org # (/) Have Pat install Java 7 on bugs.shore.mbari.org # (/) Have Pete plumb holes through firewall so processes on bugs.mbari.org can get to Solstice2 # (/) Have Pat create DB_Collaboration account on bugs so it can run JIRA under that account and it can connect to solstice2 using that NT Domain account. # (/) Upgrade license on Atlassian site # (/) Log into bugs.shore.mbari.org # (/) Download 3.13.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 4.4.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 5.2.11 standalone Linux 64 bit tar.gz (not sure this version is necessary, but at least I have it) # (/) Unzip and untar the file to /opt # (/) Download latest JIRA (6.4.7 as of this writing). # (/) Unzip and untar it to /opt # Performed Test Upgrade ## (/) In order to export the current stuff in JIRA, I had to shut off access so people could not change the data while I was backing it up. ## (/) I ssh'd to oceana.mbari.org as root and edited the /opt/jira/conf/server.xml file and commented out the Connector section that had the port of 8010 to shut it off from the normal serving route. ## (/) I uncommented the 8082 port connector and the 8443 port connector so that I could still get to the server. ## (/) I stopped and started the JIRA server and in the log file I got a "keystore was tampered with..." which is not surprising. ## (/) I could then browser over to http://oceana.mbari.org:8082/jira ## (/) Then through the Administration console, I did an XML backup ## (/) I then created a tar of all the attachments in the /data/jira_3_12/attachments directory ## (/) I moved both the XML and tar files to the /root/jira-upgrade directory ## (/) I then reversed the changes to the server.xml file and shut down JIRA ## (/) I left it down during the next steps in case it went so well, I could just point people to the new server (yeah, right). ## (/) I then browsed to the crowd server on oceana and add a new application using: ### URL: http://bugs.mbari.org/jira3135 ### IP: 134.89.2.29 ### Name: JIRA3135 ### Password: (ask Kevin) :) ## (/) On bugs, I made a copy of the JIRA 3.13.5 download in the /opt directory and unzipped and untarred it. ## (/) In order to configure the crowd connection I did the following: ### (/) I scp'd the /opt/crowd/client/crowd-integration-client-1.6.jar file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I removed the existing 1.6.1 crowd client jar from the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I scp'd the /opt/crowd/client/conf/crowd.properties file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I scp'd the /opt/crowd/client/conf/crowd-ehcache.xml file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I edited the crowd.properties file on bugs to look like: {noformat} application.name JIRA3135 application.password (ask Kevin) application.login.url http://oceana.mbari.org:8095/crowd/console/ crowd.server.url http://oceana.mbari.org:8095/crowd/services/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 0 session.lastvalidation session.lastvalidation {noformat} ### (/) I edited the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/osuser.xml file to comment out the current authentication mechanism and then uncomment the crowd one. ## (/) I then edited the /opt/atlassian-jira-standalone-3.13.5/conf/server/xml file and configured the database connection to the Jira_Temp database on Solstice2. I looked like this: {noformat} {noformat} ## (/) Edit the /opt/atlassian/jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/entityengine.xml and changed it from 'hsql' to 'mssql' and delete the line with "PUBLIC" in it per the instructions in the comments in that file. ## (/) I edited the /etc/httpd/conf/httpd.conf file and created a proxy pass at the bottom of the file to point a normal URL to the default port 8080 for JIRA: {noformat} # Proxy Pass for JIRA ProxyPass http://bugs.mbari.org:8080 ProxyPassReverse http://bugs.mbari.org:8080 {noformat} ## (/) I restarted Apache ## (/) I scp'd the jtds driver from oceana to the /opt/atlassian-jira-standalone-3.13.5/common/lib directory (you could down from the internet) ## (/) I then went to the /opt/atlassian-jira-standalone-3.13.5/ directory and ran './bin/startup.sh'. From the log file, I could tell things were hanging. After some troubleshooting I am wondering if the local firewall is preventing the application to get access to the database on solstice2. I can telnet to port 1433, but I can't browse to the base http://bugs.mbari.org from anywhere but the local web browser. I have submitted a ticket. ## (/) I restarted the old JIRA with my hopes dashed :(. ## (/) Pat disabled the firewall on bugs.mbari.org but it still hung trying to connect to solstice2.shore.mbari.org. That is really, really perplexing. Neil mentioned that solstice2 is using Kerberos and solstice is not. Checking with the JTDS docs, version 1.3.1 of the driver added kerberos support, so I downloaded that driver and added the 'userKerberos=true' property to the URL in the server.xml file and restarted. Got an error about no credentials, so added user and password properties to the URL. Nope, no luck. Never did figure this one out, but I had Pat pull the VM inside the firewall and after some thrash it worked. Well, it sort of worked ... sigh. It turns out I had downloaded the standard version instead of the enterprise version. I need to redo this work ... grrr. ## (/) I deleted all the tables in the Jira_Temp database and removed the /data/jira3135/indexes directory (and recreated). ## (/) I downloaded the enterprise version of the 3.13.5 server. I made a copy in the /opt directory and unzipped and untarred the file. ## (/) I went back to crowd and edited the application to change the properties to: ### URL: http://bugs.shore.mbari.org:8080 ### IP: 134.89.12.31 ### Name: jira3135 ### Password: (ask Kevin) :) ## (/) I then repeated the steps above to get the server up and running with the following differences: ### The server name is now bugs.shore.mbari.org ### The paths given above are a little different in that they no longer say "standard" but say "enterprise" ### I deleted the proxy pass as it seemed to have issues before and this is only temporary anyway. ## (/) I then browsed to http://bugs.shore.mbari.org:8080 ## (/) It took me to the start up page and at the top was the option to 'import your existing data'. Seemed too good not to try. I clicked on the link. It asked me for the backup file location and the location where the indexes would be stored. ## (/) I copied the XML zip file and the attachments tar file to the /data/original directory. ## (/) I created the /data/jira3135/indexes and used those directories ... it fired off the import and I waited. ## (/) I tailed the log file to watch the import. Holy crap, it worked!!! I could log in and everything! I copied the results from the log file here for posterity sake: {noformat} 2015-07-22 20:55:45,156 http-8080-Processor22 INFO [jira.action.admin.DataImport] Running data import 2015-07-22 20:55:45,179 http-8080-Processor22 INFO [jira.action.admin.DataImport] Importing data.. 2015-07-22 20:55:45,186 http-8080-Processor22 INFO [jira.action.admin.DataImport] Start parsing XML with SAX Parser 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] XML successfully parsed 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] Removing all entries from the database. 2015-07-22 20:56:24,593 http-8080-Processor22 INFO [jira.action.admin.DataImport] All entries removed. 2015-07-22 20:56:24,594 http-8080-Processor22 INFO [jira.action.admin.DataImport] Started storing 410414 Generic Values 2015-07-22 21:01:51,967 http-8080-Processor22 INFO [jira.action.admin.DataImport] Finished storing Generic Values 2015-07-22 21:01:52,329 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:52,361 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:54,683 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLink' to module 'jira.user.format:profile-link-user-format'. 2015-07-22 21:01:54,724 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullName' to module 'jira.user.format:full-name-user-format'. 2015-07-22 21:01:54,773 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkSearcher' to module 'jira.user.format:profile-link-searcher-user-format'. 2015-07-22 21:01:54,784 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkExternal' to module 'jira.user.format:profile-link-external-user-format'. 2015-07-22 21:01:54,795 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkActionHeader' to module 'jira.user.format:profile-link-action-header-user-format'. 2015-07-22 21:01:54,807 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullProfile' to module 'jira.user.format:full-profile-user-format'. 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/comments 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/issues 2015-07-22 21:01:55,641 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/plugins 2015-07-22 21:01:55,867 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:01:55,871 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/issues does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:55,873 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/comments does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,033 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,257 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,889 http-8080-Processor22 ERROR [atlassian.jira.upgrade.ConsistencyCheckImpl] Attachments are turned on, but attachment path [/data/jira_3_12/attachments] invalid - disabling attachments 2015-07-22 21:02:13,904 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Detected that an upgrade is needed; existing data at build 299 2015-07-22 21:02:13,907 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Doing Upgrade... 2015-07-22 21:02:13,915 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value' succeeded 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 317 2015-07-22 21:02:13,944 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite filters - make each filter a favourite of its owner. 2015-07-22 21:02:17,822 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build319] Could not find author 'fpy' for filter with id '10040' 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite filters - make each filter a favourite of its owner.' succeeded 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 319 2015-07-22 21:02:17,995 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise Share Permissions. Move old shares to new shares. 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise Share Permissions. Move old shares to new shares.' succeeded 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 321 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Migrating the old JIRA UI colors to the new JIRA 3.13 colors 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build322] Custom color detected for jira.lf.menu.bgcolour : #336699 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Migrating the old JIRA UI colors to the new JIRA 3.13 colors' succeeded 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 322 2015-07-22 21:02:18,025 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite dashboards - make each dashboard a favourite of its owner. 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'cmcgann' for dashboard with id '10030' 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'fpy' for dashboard with id '10060' 2015-07-22 21:02:18,423 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'kanna' for dashboard with id '10040' 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite dashboards - make each dashboard a favourite of its owner.' succeeded 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 325 2015-07-22 21:02:18,625 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Reindexing all data in JIRA to include Favourites. 2015-07-22 21:02:18,648 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All starting... 2015-07-22 21:02:18,650 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 0% complete. Current index: Issue 2015-07-22 21:02:18,654 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:02:18,809 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 1% complete. Current index: Issue 2015-07-22 21:02:18,855 indexerPool-2-thread-10 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 2% complete. Current index: Issue 2015-07-22 21:02:18,899 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 3% complete. Current index: Issue 2015-07-22 21:02:18,945 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 4% complete. Current index: Issue 2015-07-22 21:02:19,012 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 5% complete. Current index: Issue . . . 2015-07-22 21:02:26,164 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 95% complete. Current index: Issue 2015-07-22 21:02:26,232 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 96% complete. Current index: Issue 2015-07-22 21:02:26,316 indexerPool-2-thread-9 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 97% complete. Current index: Issue 2015-07-22 21:02:26,771 indexerPool-2-thread-3 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: Issue 2015-07-22 21:02:27,261 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 8607ms. Indexer: DefaultIndexManager: paths: [/data/jira3135/indexes/issues, /data/jira3135/indexes/comments] 2015-07-22 21:02:27,263 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: SearchRequest 2015-07-22 21:02:27,268 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,293 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: SearchRequest 2015-07-22 21:02:27,308 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: PortalPage 2015-07-22 21:02:27,312 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,377 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: PortalPage 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 115ms. Indexer: SharedEntityIndexManager: paths: [/data/jira3135/indexes/entities/portalpage, /data/jira3135/indexes/entities/searchrequest] 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All complete. Total time: 8722ms. 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Reindexing all data in JIRA to include Favourites.' succeeded 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 326 2015-07-22 21:02:27,397 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade succeeded! Setting data build number to 360 2015-07-22 21:02:27,469 JiraQuartzScheduler_Worker-0 WARN [service.services.export.ExportService] Backup directory /data/jira_3_12/backup does not exist {noformat} {warning:title=Paths} It appears that the upgraded JIRA will still look for the attachments and the backup locations in the original places. So I created /data/jira_3_12/backup and untarred the original attachments to /data/jira_3_12 and then everything worked (including attachements) in the new JIRA. {warning} ## (/) I then used the upgraded JIRA to generate a new XML backup and stored it in /data/original/3.13.5 along with another tar of the files in /data/jira_3_12/attachments. *I should be ready to move on to version 4 upgrade WHEW* # Schedule upgrade date and send all hands several days in advance. # When the day arrives, send all hands announcing JIRA outage. # From the Administrator's page in our existing JIRA, perform a 'Backup Data to XML'. # Login to oceana.mbari.org as root. # Shutdown JIRA # Create a tar.gz of the /opt/atlassian-jira-enterprise-3.12.1-standalone directory # Clean up the /data/jira_3_12/backups directory by deleting all but maybe the last 5 backups. # Create a tar.gz of the JIRA home directory on ocean.mbari.org which is located at /data/jira_3_12 # scp both tar.gz files to bugs.mbari.org # login to bugs.mbari.org # Unpack the home directory tar to /data/jira # Run the installer as root (this might need IS help or sudo privs). Note that we usually install the application to /opt # Run the JIRA Configuration tool to set the jira.home to the /data/jira location # Connect to JIRA_Temp database on Solstice2 (.... more to do here, see Atlassian docs) # Migrate existing configuration over to new JIRA (I need to add more here as we added Crowd). # Start JIRA # Import backed up XML # Perform post upgrades checks and tests *Need to document steps for 4.4.5->6.X*]]> 27557999 27590764 4.4: [https://confluence.atlassian.com/display/JIRA044/Migrating+JIRA+to+Another+Server] ## The JIRA configuration tool: [https://confluence.atlassian.com/display/JIRA044/Using+the+JIRA+Configuration+Tool] h5. Steps # (/) Create new VM named bugs.mbari.org in the DMZ # (/) Have Neil create database Jira_Temp on solstice2.shore.mbari.org # (/) Have Neil create database Jira on solstice2.shore.mbari.org # (/) Have Pat install Java 7 on bugs.shore.mbari.org # (/) Have Pete plumb holes through firewall so processes on bugs.mbari.org can get to Solstice2 # (/) Have Pat create DB_Collaboration account on bugs so it can run JIRA under that account and it can connect to solstice2 using that NT Domain account. # (/) Upgrade license on Atlassian site # (/) Log into bugs.shore.mbari.org # (/) Download 3.13.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 4.4.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 5.2.11 standalone Linux 64 bit tar.gz (not sure this version is necessary, but at least I have it) # (/) Unzip and untar the file to /opt # (/) Download latest JIRA (6.4.7 as of this writing). # (/) Unzip and untar it to /opt # Performed Test Upgrade ## (/) In order to export the current stuff in JIRA, I had to shut off access so people could not change the data while I was backing it up. ## (/) I ssh'd to oceana.mbari.org as root and edited the /opt/jira/conf/server.xml file and commented out the Connector section that had the port of 8010 to shut it off from the normal serving route. ## (/) I uncommented the 8082 port connector and the 8443 port connector so that I could still get to the server. ## (/) I stopped and started the JIRA server and in the log file I got a "keystore was tampered with..." which is not surprising. ## (/) I could then browser over to http://oceana.mbari.org:8082/jira ## (/) Then through the Administration console, I did an XML backup ## (/) I then created a tar of all the attachments in the /data/jira_3_12/attachments directory ## (/) I moved both the XML and tar files to the /root/jira-upgrade directory ## (/) I then reversed the changes to the server.xml file and shut down JIRA ## (/) I left it down during the next steps in case it went so well, I could just point people to the new server (yeah, right). ## (/) I then browsed to the crowd server on oceana and add a new application using: ### URL: http://bugs.mbari.org/jira3135 ### IP: 134.89.2.29 ### Name: JIRA3135 ### Password: (ask Kevin) :) ## (/) On bugs, I made a copy of the JIRA 3.13.5 download in the /opt directory and unzipped and untarred it. ## (/) In order to configure the crowd connection I did the following: ### (/) I scp'd the /opt/crowd/client/crowd-integration-client-1.6.jar file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I removed the existing 1.6.1 crowd client jar from the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I scp'd the /opt/crowd/client/conf/crowd.properties file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I scp'd the /opt/crowd/client/conf/crowd-ehcache.xml file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I edited the crowd.properties file on bugs to look like: {noformat} application.name JIRA3135 application.password (ask Kevin) application.login.url http://oceana.mbari.org:8095/crowd/console/ crowd.server.url http://oceana.mbari.org:8095/crowd/services/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 0 session.lastvalidation session.lastvalidation {noformat} ### (/) I edited the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/osuser.xml file to comment out the current authentication mechanism and then uncomment the crowd one. ## (/) I then edited the /opt/atlassian-jira-standalone-3.13.5/conf/server/xml file and configured the database connection to the Jira_Temp database on Solstice2. I looked like this: {noformat} {noformat} ## (/) Edit the /opt/atlassian/jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/entityengine.xml and changed it from 'hsql' to 'mssql' and delete the line with "PUBLIC" in it per the instructions in the comments in that file. ## (/) I edited the /etc/httpd/conf/httpd.conf file and created a proxy pass at the bottom of the file to point a normal URL to the default port 8080 for JIRA: {noformat} # Proxy Pass for JIRA ProxyPass http://bugs.mbari.org:8080 ProxyPassReverse http://bugs.mbari.org:8080 {noformat} ## (/) I restarted Apache ## (/) I scp'd the jtds driver from oceana to the /opt/atlassian-jira-standalone-3.13.5/common/lib directory (you could down from the internet) ## (/) I then went to the /opt/atlassian-jira-standalone-3.13.5/ directory and ran './bin/startup.sh'. From the log file, I could tell things were hanging. After some troubleshooting I am wondering if the local firewall is preventing the application to get access to the database on solstice2. I can telnet to port 1433, but I can't browse to the base http://bugs.mbari.org from anywhere but the local web browser. I have submitted a ticket. ## (/) I restarted the old JIRA with my hopes dashed :(. ## (/) Pat disabled the firewall on bugs.mbari.org but it still hung trying to connect to solstice2.shore.mbari.org. That is really, really perplexing. Neil mentioned that solstice2 is using Kerberos and solstice is not. Checking with the JTDS docs, version 1.3.1 of the driver added kerberos support, so I downloaded that driver and added the 'userKerberos=true' property to the URL in the server.xml file and restarted. Got an error about no credentials, so added user and password properties to the URL. Nope, no luck. Never did figure this one out, but I had Pat pull the VM inside the firewall and after some thrash it worked. Well, it sort of worked ... sigh. It turns out I had downloaded the standard version instead of the enterprise version. I need to redo this work ... grrr. ## (/) I deleted all the tables in the Jira_Temp database and removed the /data/jira3135/indexes directory (and recreated). ## (/) I downloaded the enterprise version of the 3.13.5 server. I made a copy in the /opt directory and unzipped and untarred the file. ## (/) I went back to crowd and edited the application to change the properties to: ### URL: http://bugs.shore.mbari.org:8080 ### IP: 134.89.12.31 ### Name: jira3135 ### Password: (ask Kevin) :) ## (/) I then repeated the steps above to get the server up and running with the following differences: ### The server name is now bugs.shore.mbari.org ### The paths given above are a little different in that they no longer say "standard" but say "enterprise" ### I deleted the proxy pass as it seemed to have issues before and this is only temporary anyway. ## (/) I then browsed to http://bugs.shore.mbari.org:8080 ## (/) It took me to the start up page and at the top was the option to 'import your existing data'. Seemed too good not to try. I clicked on the link. It asked me for the backup file location and the location where the indexes would be stored. ## (/) I copied the XML zip file and the attachments tar file to the /data/original directory. ## (/) I created the /data/jira3135/indexes and used those directories ... it fired off the import and I waited. ## (/) I tailed the log file to watch the import. Holy crap, it worked!!! I could log in and everything! I copied the results from the log file here for posterity sake: {noformat} 2015-07-22 20:55:45,156 http-8080-Processor22 INFO [jira.action.admin.DataImport] Running data import 2015-07-22 20:55:45,179 http-8080-Processor22 INFO [jira.action.admin.DataImport] Importing data.. 2015-07-22 20:55:45,186 http-8080-Processor22 INFO [jira.action.admin.DataImport] Start parsing XML with SAX Parser 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] XML successfully parsed 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] Removing all entries from the database. 2015-07-22 20:56:24,593 http-8080-Processor22 INFO [jira.action.admin.DataImport] All entries removed. 2015-07-22 20:56:24,594 http-8080-Processor22 INFO [jira.action.admin.DataImport] Started storing 410414 Generic Values 2015-07-22 21:01:51,967 http-8080-Processor22 INFO [jira.action.admin.DataImport] Finished storing Generic Values 2015-07-22 21:01:52,329 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:52,361 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:54,683 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLink' to module 'jira.user.format:profile-link-user-format'. 2015-07-22 21:01:54,724 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullName' to module 'jira.user.format:full-name-user-format'. 2015-07-22 21:01:54,773 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkSearcher' to module 'jira.user.format:profile-link-searcher-user-format'. 2015-07-22 21:01:54,784 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkExternal' to module 'jira.user.format:profile-link-external-user-format'. 2015-07-22 21:01:54,795 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkActionHeader' to module 'jira.user.format:profile-link-action-header-user-format'. 2015-07-22 21:01:54,807 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullProfile' to module 'jira.user.format:full-profile-user-format'. 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/comments 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/issues 2015-07-22 21:01:55,641 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/plugins 2015-07-22 21:01:55,867 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:01:55,871 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/issues does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:55,873 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/comments does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,033 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,257 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,889 http-8080-Processor22 ERROR [atlassian.jira.upgrade.ConsistencyCheckImpl] Attachments are turned on, but attachment path [/data/jira_3_12/attachments] invalid - disabling attachments 2015-07-22 21:02:13,904 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Detected that an upgrade is needed; existing data at build 299 2015-07-22 21:02:13,907 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Doing Upgrade... 2015-07-22 21:02:13,915 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value' succeeded 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 317 2015-07-22 21:02:13,944 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite filters - make each filter a favourite of its owner. 2015-07-22 21:02:17,822 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build319] Could not find author 'fpy' for filter with id '10040' 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite filters - make each filter a favourite of its owner.' succeeded 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 319 2015-07-22 21:02:17,995 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise Share Permissions. Move old shares to new shares. 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise Share Permissions. Move old shares to new shares.' succeeded 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 321 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Migrating the old JIRA UI colors to the new JIRA 3.13 colors 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build322] Custom color detected for jira.lf.menu.bgcolour : #336699 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Migrating the old JIRA UI colors to the new JIRA 3.13 colors' succeeded 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 322 2015-07-22 21:02:18,025 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite dashboards - make each dashboard a favourite of its owner. 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'cmcgann' for dashboard with id '10030' 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'fpy' for dashboard with id '10060' 2015-07-22 21:02:18,423 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'kanna' for dashboard with id '10040' 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite dashboards - make each dashboard a favourite of its owner.' succeeded 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 325 2015-07-22 21:02:18,625 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Reindexing all data in JIRA to include Favourites. 2015-07-22 21:02:18,648 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All starting... 2015-07-22 21:02:18,650 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 0% complete. Current index: Issue 2015-07-22 21:02:18,654 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:02:18,809 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 1% complete. Current index: Issue 2015-07-22 21:02:18,855 indexerPool-2-thread-10 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 2% complete. Current index: Issue 2015-07-22 21:02:18,899 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 3% complete. Current index: Issue 2015-07-22 21:02:18,945 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 4% complete. Current index: Issue 2015-07-22 21:02:19,012 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 5% complete. Current index: Issue . . . 2015-07-22 21:02:26,164 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 95% complete. Current index: Issue 2015-07-22 21:02:26,232 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 96% complete. Current index: Issue 2015-07-22 21:02:26,316 indexerPool-2-thread-9 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 97% complete. Current index: Issue 2015-07-22 21:02:26,771 indexerPool-2-thread-3 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: Issue 2015-07-22 21:02:27,261 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 8607ms. Indexer: DefaultIndexManager: paths: [/data/jira3135/indexes/issues, /data/jira3135/indexes/comments] 2015-07-22 21:02:27,263 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: SearchRequest 2015-07-22 21:02:27,268 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,293 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: SearchRequest 2015-07-22 21:02:27,308 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: PortalPage 2015-07-22 21:02:27,312 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,377 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: PortalPage 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 115ms. Indexer: SharedEntityIndexManager: paths: [/data/jira3135/indexes/entities/portalpage, /data/jira3135/indexes/entities/searchrequest] 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All complete. Total time: 8722ms. 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Reindexing all data in JIRA to include Favourites.' succeeded 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 326 2015-07-22 21:02:27,397 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade succeeded! Setting data build number to 360 2015-07-22 21:02:27,469 JiraQuartzScheduler_Worker-0 WARN [service.services.export.ExportService] Backup directory /data/jira_3_12/backup does not exist {noformat} {warning:title=Paths} It appears that the upgraded JIRA will still look for the attachments and the backup locations in the original places. So I created /data/jira_3_12/backup and untarred the original attachments to /data/jira_3_12 and then everything worked (including attachements) in the new JIRA. {warning} # Schedule upgrade date and send all hands several days in advance. # When the day arrives, send all hands announcing JIRA outage. # From the Administrator's page in our existing JIRA, perform a 'Backup Data to XML'. # Login to oceana.mbari.org as root. # Shutdown JIRA # Create a tar.gz of the /opt/atlassian-jira-enterprise-3.12.1-standalone directory # Clean up the /data/jira_3_12/backups directory by deleting all but maybe the last 5 backups. # Create a tar.gz of the JIRA home directory on ocean.mbari.org which is located at /data/jira_3_12 # scp both tar.gz files to bugs.mbari.org # login to bugs.mbari.org # Unpack the home directory tar to /data/jira # Run the installer as root (this might need IS help or sudo privs). Note that we usually install the application to /opt # Run the JIRA Configuration tool to set the jira.home to the /data/jira location # Connect to JIRA_Temp database on Solstice2 (.... more to do here, see Atlassian docs) # Migrate existing configuration over to new JIRA (I need to add more here as we added Crowd). # Start JIRA # Import backed up XML # Perform post upgrades checks and tests *Need to document steps for 4.4.5->6.X*]]> 27557998 27590744 4.4: [https://confluence.atlassian.com/display/JIRA044/Migrating+JIRA+to+Another+Server] ## The JIRA configuration tool: [https://confluence.atlassian.com/display/JIRA044/Using+the+JIRA+Configuration+Tool] h5. Steps # (/) Create new VM named bugs.mbari.org in the DMZ # (/) Have Neil create database Jira_Temp on solstice2.shore.mbari.org # (/) Have Neil create database Jira on solstice2.shore.mbari.org # (/) Have Pat install Java 7 on bugs.shore.mbari.org # (/) Have Pete plumb holes through firewall so processes on bugs.mbari.org can get to Solstice2 # (/) Have Pat create DB_Collaboration account on bugs so it can run JIRA under that account and it can connect to solstice2 using that NT Domain account. # (/) Upgrade license on Atlassian site # (/) Log into bugs.shore.mbari.org # (/) Download 3.13.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 4.4.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 5.2.11 standalone Linux 64 bit tar.gz (not sure this version is necessary, but at least I have it) # (/) Unzip and untar the file to /opt # (/) Download latest JIRA (6.4.7 as of this writing). # (/) Unzip and untar it to /opt # Performed Test Upgrade ## (/) In order to export the current stuff in JIRA, I had to shut off access so people could not change the data while I was backing it up. ## (/) I ssh'd to oceana.mbari.org as root and edited the /opt/jira/conf/server.xml file and commented out the Connector section that had the port of 8010 to shut it off from the normal serving route. ## (/) I uncommented the 8082 port connector and the 8443 port connector so that I could still get to the server. ## (/) I stopped and started the JIRA server and in the log file I got a "keystore was tampered with..." which is not surprising. ## (/) I could then browser over to http://oceana.mbari.org:8082/jira ## (/) Then through the Administration console, I did an XML backup ## (/) I then created a tar of all the attachments in the /data/jira_3_12/attachments directory ## (/) I moved both the XML and tar files to the /root/jira-upgrade directory ## (/) I then reversed the changes to the server.xml file and shut down JIRA ## (/) I left it down during the next steps in case it went so well, I could just point people to the new server (yeah, right). ## (/) I then browsed to the crowd server on oceana and add a new application using: ### URL: http://bugs.mbari.org/jira3135 ### IP: 134.89.2.29 ### Name: JIRA3135 ### Password: (ask Kevin) :) ## (/) On bugs, I made a copy of the JIRA 3.13.5 download in the /opt directory and unzipped and untarred it. ## (/) In order to configure the crowd connection I did the following: ### (/) I scp'd the /opt/crowd/client/crowd-integration-client-1.6.jar file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I removed the existing 1.6.1 crowd client jar from the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I scp'd the /opt/crowd/client/conf/crowd.properties file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I scp'd the /opt/crowd/client/conf/crowd-ehcache.xml file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I edited the crowd.properties file on bugs to look like: {noformat} application.name JIRA3135 application.password (ask Kevin) application.login.url http://oceana.mbari.org:8095/crowd/console/ crowd.server.url http://oceana.mbari.org:8095/crowd/services/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 0 session.lastvalidation session.lastvalidation {noformat} ### (/) I edited the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/osuser.xml file to comment out the current authentication mechanism and then uncomment the crowd one. ## (/) I then edited the /opt/atlassian-jira-standalone-3.13.5/conf/server/xml file and configured the database connection to the Jira_Temp database on Solstice2. I looked like this: {noformat} {noformat} # Schedule upgrade date and send all hands several days in advance. # When the day arrives, send all hands announcing JIRA outage. # From the Administrator's page in our existing JIRA, perform a 'Backup Data to XML'. # Login to oceana.mbari.org as root. # Shutdown JIRA # Create a tar.gz of the /opt/atlassian-jira-enterprise-3.12.1-standalone directory # Clean up the /data/jira_3_12/backups directory by deleting all but maybe the last 5 backups. # Create a tar.gz of the JIRA home directory on ocean.mbari.org which is located at /data/jira_3_12 # scp both tar.gz files to bugs.mbari.org # login to bugs.mbari.org # Unpack the home directory tar to /data/jira # Run the installer as root (this might need IS help or sudo privs). Note that we usually install the application to /opt # Run the JIRA Configuration tool to set the jira.home to the /data/jira location # Connect to JIRA_Temp database on Solstice2 (.... more to do here, see Atlassian docs) # Migrate existing configuration over to new JIRA (I need to add more here as we added Crowd). # Start JIRA # Import backed up XML # Perform post upgrades checks and tests *Need to document steps for 4.4.5->6.X* ]]> 27557978 27590746 4.4: [https://confluence.atlassian.com/display/JIRA044/Migrating+JIRA+to+Another+Server] ## The JIRA configuration tool: [https://confluence.atlassian.com/display/JIRA044/Using+the+JIRA+Configuration+Tool] h5. Steps # (/) Create new VM named bugs.mbari.org in the DMZ # (/) Have Neil create database Jira_Temp on solstice2.shore.mbari.org # (/) Have Neil create database Jira on solstice2.shore.mbari.org # (/) Have Pat install Java 7 on bugs.shore.mbari.org # (/) Have Pete plumb holes through firewall so processes on bugs.mbari.org can get to Solstice2 # (/) Have Pat create DB_Collaboration account on bugs so it can run JIRA under that account and it can connect to solstice2 using that NT Domain account. # (/) Upgrade license on Atlassian site # (/) Log into bugs.shore.mbari.org # (/) Download 3.13.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 4.4.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 5.2.11 standalone Linux 64 bit tar.gz (not sure this version is necessary, but at least I have it) # (/) Unzip and untar the file to /opt # (/) Download latest JIRA (6.4.7 as of this writing). # (/) Unzip and untar it to /opt # Performed Test Upgrade ## (/) In order to export the current stuff in JIRA, I had to shut off access so people could not change the data while I was backing it up. ## (/) I ssh'd to oceana.mbari.org as root and edited the /opt/jira/conf/server.xml file and commented out the Connector section that had the port of 8010 to shut it off from the normal serving route. ## (/) I uncommented the 8082 port connector and the 8443 port connector so that I could still get to the server. ## (/) I stopped and started the JIRA server and in the log file I got a "keystore was tampered with..." which is not surprising. ## (/) I could then browser over to http://oceana.mbari.org:8082/jira ## (/) Then through the Administration console, I did an XML backup ## (/) I then created a tar of all the attachments in the /data/jira_3_12/attachments directory ## (/) I moved both the XML and tar files to the /root/jira-upgrade directory ## (/) I then reversed the changes to the server.xml file and shut down JIRA ## (/) I left it down during the next steps in case it went so well, I could just point people to the new server (yeah, right). ## (/) I then browsed to the crowd server on oceana and add a new application using: ### URL: http://bugs.mbari.org/jira3135 ### IP: 134.89.2.29 ### Name: JIRA3135 ### Password: (ask Kevin) :) ## (/) On bugs, I made a copy of the JIRA 3.13.5 download in the /opt directory and unzipped and untarred it. ## (/) In order to configure the crowd connection I did the following: ### (/) I scp'd the /opt/crowd/client/crowd-integration-client-1.6.jar file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I removed the existing 1.6.1 crowd client jar from the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I scp'd the /opt/crowd/client/conf/crowd.properties file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I scp'd the /opt/crowd/client/conf/crowd-ehcache.xml file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I edited the crowd.properties file on bugs to look like: {noformat} application.name JIRA3135 application.password (ask Kevin) application.login.url http://oceana.mbari.org:8095/crowd/console/ crowd.server.url http://oceana.mbari.org:8095/crowd/services/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 0 session.lastvalidation session.lastvalidation {noformat} ### (/) I edited the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/osuser.xml file to comment out the current authentication mechanism and then uncomment the crowd one. ## (/) I then edited the /opt/atlassian-jira-standalone-3.13.5/conf/server/xml file and configured the database connection to the Jira_Temp database on Solstice2. I looked like this: {noformat} {noformat} ## (/) I edited the /etc/httpd/conf/httpd.conf file and created a proxy pass at the bottom of the file to point a normal URL to the default port 8080 for JIRA: {noformat} # Proxy Pass for JIRA ProxyPass http://bugs.mbari.org:8080 ProxyPassReverse http://bugs.mbari.org:8080 {noformat} ## (/) I restarted Apache ## (/) I scp'd the jtds driver from oceana to the /opt/atlassian-jira-standalone-3.13.5/common/lib directory (you could down from the internet) ## (/) I then went to the /opt/atlassian-jira-standalone-3.13.5/ directory and ran './bin/startup.sh'. From the log file, I could tell things were hanging. After some troubleshooting I am wondering if the local firewall is preventing the application to get access to the database on solstice2. I can telnet to port 1433, but I can't browse to the base http://bugs.mbari.org from anywhere but the local web browser. I have submitted a ticket. ## (/) I restarted the old JIRA with my hopes dashed :(. # Schedule upgrade date and send all hands several days in advance. # When the day arrives, send all hands announcing JIRA outage. # From the Administrator's page in our existing JIRA, perform a 'Backup Data to XML'. # Login to oceana.mbari.org as root. # Shutdown JIRA # Create a tar.gz of the /opt/atlassian-jira-enterprise-3.12.1-standalone directory # Clean up the /data/jira_3_12/backups directory by deleting all but maybe the last 5 backups. # Create a tar.gz of the JIRA home directory on ocean.mbari.org which is located at /data/jira_3_12 # scp both tar.gz files to bugs.mbari.org # login to bugs.mbari.org # Unpack the home directory tar to /data/jira # Run the installer as root (this might need IS help or sudo privs). Note that we usually install the application to /opt # Run the JIRA Configuration tool to set the jira.home to the /data/jira location # Connect to JIRA_Temp database on Solstice2 (.... more to do here, see Atlassian docs) # Migrate existing configuration over to new JIRA (I need to add more here as we added Crowd). # Start JIRA # Import backed up XML # Perform post upgrades checks and tests *Need to document steps for 4.4.5->6.X* ]]> 27557980 27590740 4.4: [https://confluence.atlassian.com/display/JIRA044/Migrating+JIRA+to+Another+Server] ## The JIRA configuration tool: [https://confluence.atlassian.com/display/JIRA044/Using+the+JIRA+Configuration+Tool] h5. Steps # (/) Create new VM named bugs.mbari.org in the DMZ # (/) Have Neil create database Jira_Temp on solstice2.shore.mbari.org # (/) Have Neil create database Jira on solstice2.shore.mbari.org # (/) Have Pat install Java 7 on bugs.shore.mbari.org # (/) Have Pete plumb holes through firewall so processes on bugs.mbari.org can get to Solstice2 # (/) Have Pat create DB_Collaboration account on bugs so it can run JIRA under that account and it can connect to solstice2 using that NT Domain account. # (/) Upgrade license on Atlassian site # (/) Log into bugs.shore.mbari.org # (/) Download 4.4.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 5.2.11 standalone Linux 64 bit tar.gz (not sure this version is necessary, but at least I have it) # (/) Unzip and untar the file to /opt # (/) Download latest JIRA (6.4.7 as of this writing). # (/) Unzip and untar it to /opt # Perform test upgrade ## # Schedule upgrade date and send all hands several days in advance. # When the day arrives, send all hands announcing JIRA outage. # From the Administrator's page in our existing JIRA, perform a 'Backup Data to XML'. # Login to oceana.mbari.org as root. # Shutdown JIRA # Create a tar.gz of the /opt/atlassian-jira-enterprise-3.12.1-standalone directory # Clean up the /data/jira_3_12/backups directory by deleting all but maybe the last 5 backups. # Create a tar.gz of the JIRA home directory on ocean.mbari.org which is located at /data/jira_3_12 # scp both tar.gz files to bugs.mbari.org # login to bugs.mbari.org # Unpack the home directory tar to /data/jira # Run the installer as root (this might need IS help or sudo privs). Note that we usually install the application to /opt # Run the JIRA Configuration tool to set the jira.home to the /data/jira location # Connect to JIRA_Temp database on Solstice2 (.... more to do here, see Atlassian docs) # Migrate existing configuration over to new JIRA (I need to add more here as we added Crowd). # Start JIRA # Import backed up XML # Perform post upgrades checks and tests *Need to document steps for 4.4.5->6.X* ]]> 27557974 27590742 4.4: [https://confluence.atlassian.com/display/JIRA044/Migrating+JIRA+to+Another+Server] ## The JIRA configuration tool: [https://confluence.atlassian.com/display/JIRA044/Using+the+JIRA+Configuration+Tool] h5. Steps # (/) Create new VM named bugs.mbari.org in the DMZ # (/) Have Neil create database Jira_Temp on solstice2.shore.mbari.org # (/) Have Neil create database Jira on solstice2.shore.mbari.org # (/) Have Pat install Java 7 on bugs.shore.mbari.org # (/) Have Pete plumb holes through firewall so processes on bugs.mbari.org can get to Solstice2 # (/) Have Pat create DB_Collaboration account on bugs so it can run JIRA under that account and it can connect to solstice2 using that NT Domain account. # (/) Upgrade license on Atlassian site # (/) Log into bugs.shore.mbari.org # (/) Download 3.13.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 4.4.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 5.2.11 standalone Linux 64 bit tar.gz (not sure this version is necessary, but at least I have it) # (/) Unzip and untar the file to /opt # (/) Download latest JIRA (6.4.7 as of this writing). # (/) Unzip and untar it to /opt # Performed Test Upgrade ## (/) In order to export the current stuff in JIRA, I had to shut off access so people could not change the data while I was backing it up. ## (/) I ssh'd to oceana.mbari.org as root and edited the /opt/jira/conf/server.xml file and commented out the Connector section that had the port of 8010 to shut it off from the normal serving route. ## (/) I uncommented the 8082 port connector and the 8443 port connector so that I could still get to the server. ## (/) I stopped and started the JIRA server and in the log file I got a "keystore was tampered with..." which is not surprising. ## (/) I could then browser over to http://oceana.mbari.org:8082/jira ## (/) Then through the Administration console, I did an XML backup ## (/) I then created a tar of all the attachments in the /data/jira_3_12/attachments directory ## (/) I moved both the XML and tar files to the /root/jira-upgrade directory ## (/) I then reversed the changes to the server.xml file and shut down JIRA ## (/) I left it down during the next steps in case it went so well, I could just point people to the new server (yeah, right). ## (/) I then browsed to the crowd server on oceana and add a new application using: ### URL: http://bugs.mbari.org/jira3135 ### IP: 134.89.2.29 ### Name: JIRA3135 ### Password: (ask Kevin) :) ## (/) On bugs, I made a copy of the JIRA 3.13.5 download in the /opt directory and unzipped and untarred it. ## (/) In order to configure the crowd connection I did the following: ### (/) I scp'd the /opt/crowd/client/crowd-integration-client-1.6.jar file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I removed the existing 1.6.1 crowd client jar from the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I scp'd the /opt/crowd/client/conf/crowd.properties file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I scp'd the /opt/crowd/client/conf/crowd-ehcache.xml file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I edited the crowd.properties file on bugs to look like: {noformat} application.name JIRA3135 application.password (ask Kevin) application.login.url http://oceana.mbari.org:8095/crowd/console/ crowd.server.url http://oceana.mbari.org:8095/crowd/services/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 0 session.lastvalidation session.lastvalidation {noformat} # Schedule upgrade date and send all hands several days in advance. # When the day arrives, send all hands announcing JIRA outage. # From the Administrator's page in our existing JIRA, perform a 'Backup Data to XML'. # Login to oceana.mbari.org as root. # Shutdown JIRA # Create a tar.gz of the /opt/atlassian-jira-enterprise-3.12.1-standalone directory # Clean up the /data/jira_3_12/backups directory by deleting all but maybe the last 5 backups. # Create a tar.gz of the JIRA home directory on ocean.mbari.org which is located at /data/jira_3_12 # scp both tar.gz files to bugs.mbari.org # login to bugs.mbari.org # Unpack the home directory tar to /data/jira # Run the installer as root (this might need IS help or sudo privs). Note that we usually install the application to /opt # Run the JIRA Configuration tool to set the jira.home to the /data/jira location # Connect to JIRA_Temp database on Solstice2 (.... more to do here, see Atlassian docs) # Migrate existing configuration over to new JIRA (I need to add more here as we added Crowd). # Start JIRA # Import backed up XML # Perform post upgrades checks and tests *Need to document steps for 4.4.5->6.X* ]]> 27557976 27590752 4.4: [https://confluence.atlassian.com/display/JIRA044/Migrating+JIRA+to+Another+Server] ## The JIRA configuration tool: [https://confluence.atlassian.com/display/JIRA044/Using+the+JIRA+Configuration+Tool] h5. Steps # (/) Create new VM named bugs.mbari.org in the DMZ # (/) Have Neil create database Jira_Temp on solstice2.shore.mbari.org # (/) Have Neil create database Jira on solstice2.shore.mbari.org # (/) Have Pat install Java 7 on bugs.shore.mbari.org # (/) Have Pete plumb holes through firewall so processes on bugs.mbari.org can get to Solstice2 # (/) Have Pat create DB_Collaboration account on bugs so it can run JIRA under that account and it can connect to solstice2 using that NT Domain account. # (/) Upgrade license on Atlassian site # (/) Log into bugs.shore.mbari.org # (/) Download 3.13.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 4.4.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 5.2.11 standalone Linux 64 bit tar.gz (not sure this version is necessary, but at least I have it) # (/) Unzip and untar the file to /opt # (/) Download latest JIRA (6.4.7 as of this writing). # (/) Unzip and untar it to /opt # Performed Test Upgrade ## (/) In order to export the current stuff in JIRA, I had to shut off access so people could not change the data while I was backing it up. ## (/) I ssh'd to oceana.mbari.org as root and edited the /opt/jira/conf/server.xml file and commented out the Connector section that had the port of 8010 to shut it off from the normal serving route. ## (/) I uncommented the 8082 port connector and the 8443 port connector so that I could still get to the server. ## (/) I stopped and started the JIRA server and in the log file I got a "keystore was tampered with..." which is not surprising. ## (/) I could then browser over to http://oceana.mbari.org:8082/jira ## (/) Then through the Administration console, I did an XML backup ## (/) I then created a tar of all the attachments in the /data/jira_3_12/attachments directory ## (/) I moved both the XML and tar files to the /root/jira-upgrade directory ## (/) I then reversed the changes to the server.xml file and shut down JIRA ## (/) I left it down during the next steps in case it went so well, I could just point people to the new server (yeah, right). ## (/) I then browsed to the crowd server on oceana and add a new application using: ### URL: http://bugs.mbari.org/jira3135 ### IP: 134.89.2.29 ### Name: JIRA3135 ### Password: (ask Kevin) :) ## (/) On bugs, I made a copy of the JIRA 3.13.5 download in the /opt directory and unzipped and untarred it. ## (/) In order to configure the crowd connection I did the following: ### (/) I scp'd the /opt/crowd/client/crowd-integration-client-1.6.jar file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I removed the existing 1.6.1 crowd client jar from the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I scp'd the /opt/crowd/client/conf/crowd.properties file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I scp'd the /opt/crowd/client/conf/crowd-ehcache.xml file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I edited the crowd.properties file on bugs to look like: {noformat} application.name JIRA3135 application.password (ask Kevin) application.login.url http://oceana.mbari.org:8095/crowd/console/ crowd.server.url http://oceana.mbari.org:8095/crowd/services/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 0 session.lastvalidation session.lastvalidation {noformat} ### (/) I edited the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/osuser.xml file to comment out the current authentication mechanism and then uncomment the crowd one. ## (/) I then edited the /opt/atlassian-jira-standalone-3.13.5/conf/server/xml file and configured the database connection to the Jira_Temp database on Solstice2. I looked like this: {noformat} {noformat} ## (/) Edit the /opt/atlassian/jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/entityengine.xml and changed it from HSQL to MSSQL. ## (/) I edited the /etc/httpd/conf/httpd.conf file and created a proxy pass at the bottom of the file to point a normal URL to the default port 8080 for JIRA: {noformat} # Proxy Pass for JIRA ProxyPass http://bugs.mbari.org:8080 ProxyPassReverse http://bugs.mbari.org:8080 {noformat} ## (/) I restarted Apache ## (/) I scp'd the jtds driver from oceana to the /opt/atlassian-jira-standalone-3.13.5/common/lib directory (you could down from the internet) ## (/) I then went to the /opt/atlassian-jira-standalone-3.13.5/ directory and ran './bin/startup.sh'. From the log file, I could tell things were hanging. After some troubleshooting I am wondering if the local firewall is preventing the application to get access to the database on solstice2. I can telnet to port 1433, but I can't browse to the base http://bugs.mbari.org from anywhere but the local web browser. I have submitted a ticket. ## (/) I restarted the old JIRA with my hopes dashed :(. ## (/) Pat disabled the firewall on bugs.mbari.org but it still hung trying to connect to solstice2.shore.mbari.org. That is really, really perplexing. Neil mentioned that solstice2 is using Kerberos and solstice is not. Checking with the JTDS docs, version 1.3.1 of the driver added kerberos support, so I downloaded that driver and added the 'userKerberos=true' property to the URL in the server.xml file and restarted. Got an error about no credentials, so added user and password properties to the URL. Nope, no luck. Never did figure this one out, but I had Pat pull the VM inside the firewall and after some thrash it worked. # Schedule upgrade date and send all hands several days in advance. # When the day arrives, send all hands announcing JIRA outage. # From the Administrator's page in our existing JIRA, perform a 'Backup Data to XML'. # Login to oceana.mbari.org as root. # Shutdown JIRA # Create a tar.gz of the /opt/atlassian-jira-enterprise-3.12.1-standalone directory # Clean up the /data/jira_3_12/backups directory by deleting all but maybe the last 5 backups. # Create a tar.gz of the JIRA home directory on ocean.mbari.org which is located at /data/jira_3_12 # scp both tar.gz files to bugs.mbari.org # login to bugs.mbari.org # Unpack the home directory tar to /data/jira # Run the installer as root (this might need IS help or sudo privs). Note that we usually install the application to /opt # Run the JIRA Configuration tool to set the jira.home to the /data/jira location # Connect to JIRA_Temp database on Solstice2 (.... more to do here, see Atlassian docs) # Migrate existing configuration over to new JIRA (I need to add more here as we added Crowd). # Start JIRA # Import backed up XML # Perform post upgrades checks and tests *Need to document steps for 4.4.5->6.X* ]]> 27557986 27590754 4.4: [https://confluence.atlassian.com/display/JIRA044/Migrating+JIRA+to+Another+Server] ## The JIRA configuration tool: [https://confluence.atlassian.com/display/JIRA044/Using+the+JIRA+Configuration+Tool] h5. Steps # (/) Create new VM named bugs.mbari.org in the DMZ # (/) Have Neil create database Jira_Temp on solstice2.shore.mbari.org # (/) Have Neil create database Jira on solstice2.shore.mbari.org # (/) Have Pat install Java 7 on bugs.shore.mbari.org # (/) Have Pete plumb holes through firewall so processes on bugs.mbari.org can get to Solstice2 # (/) Have Pat create DB_Collaboration account on bugs so it can run JIRA under that account and it can connect to solstice2 using that NT Domain account. # (/) Upgrade license on Atlassian site # (/) Log into bugs.shore.mbari.org # (/) Download 3.13.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 4.4.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 5.2.11 standalone Linux 64 bit tar.gz (not sure this version is necessary, but at least I have it) # (/) Unzip and untar the file to /opt # (/) Download latest JIRA (6.4.7 as of this writing). # (/) Unzip and untar it to /opt # Performed Test Upgrade ## (/) In order to export the current stuff in JIRA, I had to shut off access so people could not change the data while I was backing it up. ## (/) I ssh'd to oceana.mbari.org as root and edited the /opt/jira/conf/server.xml file and commented out the Connector section that had the port of 8010 to shut it off from the normal serving route. ## (/) I uncommented the 8082 port connector and the 8443 port connector so that I could still get to the server. ## (/) I stopped and started the JIRA server and in the log file I got a "keystore was tampered with..." which is not surprising. ## (/) I could then browser over to http://oceana.mbari.org:8082/jira ## (/) Then through the Administration console, I did an XML backup ## (/) I then created a tar of all the attachments in the /data/jira_3_12/attachments directory ## (/) I moved both the XML and tar files to the /root/jira-upgrade directory ## (/) I then reversed the changes to the server.xml file and shut down JIRA ## (/) I left it down during the next steps in case it went so well, I could just point people to the new server (yeah, right). ## (/) I then browsed to the crowd server on oceana and add a new application using: ### URL: http://bugs.mbari.org/jira3135 ### IP: 134.89.2.29 ### Name: JIRA3135 ### Password: (ask Kevin) :) ## (/) On bugs, I made a copy of the JIRA 3.13.5 download in the /opt directory and unzipped and untarred it. ## (/) In order to configure the crowd connection I did the following: ### (/) I scp'd the /opt/crowd/client/crowd-integration-client-1.6.jar file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I removed the existing 1.6.1 crowd client jar from the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I scp'd the /opt/crowd/client/conf/crowd.properties file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I scp'd the /opt/crowd/client/conf/crowd-ehcache.xml file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I edited the crowd.properties file on bugs to look like: {noformat} application.name JIRA3135 application.password (ask Kevin) application.login.url http://oceana.mbari.org:8095/crowd/console/ crowd.server.url http://oceana.mbari.org:8095/crowd/services/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 0 session.lastvalidation session.lastvalidation {noformat} ### (/) I edited the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/osuser.xml file to comment out the current authentication mechanism and then uncomment the crowd one. ## (/) I then edited the /opt/atlassian-jira-standalone-3.13.5/conf/server/xml file and configured the database connection to the Jira_Temp database on Solstice2. I looked like this: {noformat} {noformat} ## (/) Edit the /opt/atlassian/jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/entityengine.xml and changed it from HSQL to MSSQL. ## (/) I edited the /etc/httpd/conf/httpd.conf file and created a proxy pass at the bottom of the file to point a normal URL to the default port 8080 for JIRA: {noformat} # Proxy Pass for JIRA ProxyPass http://bugs.mbari.org:8080 ProxyPassReverse http://bugs.mbari.org:8080 {noformat} ## (/) I restarted Apache ## (/) I scp'd the jtds driver from oceana to the /opt/atlassian-jira-standalone-3.13.5/common/lib directory (you could down from the internet) ## (/) I then went to the /opt/atlassian-jira-standalone-3.13.5/ directory and ran './bin/startup.sh'. From the log file, I could tell things were hanging. After some troubleshooting I am wondering if the local firewall is preventing the application to get access to the database on solstice2. I can telnet to port 1433, but I can't browse to the base http://bugs.mbari.org from anywhere but the local web browser. I have submitted a ticket. ## (/) I restarted the old JIRA with my hopes dashed :(. ## (/) Pat disabled the firewall on bugs.mbari.org but it still hung trying to connect to solstice2.shore.mbari.org. That is really, really perplexing. Neil mentioned that solstice2 is using Kerberos and solstice is not. Checking with the JTDS docs, version 1.3.1 of the driver added kerberos support, so I downloaded that driver and added the 'userKerberos=true' property to the URL in the server.xml file and restarted. Got an error about no credentials, so added user and password properties to the URL. Nope, no luck. Never did figure this one out, but I had Pat pull the VM inside the firewall and after some thrash it worked. Well, it sort of worked ... sigh. It turns out I had downloaded the standard version instead of the enterprise version. I need to redo this work ... grrr. ## (/) I deleted all the tables in the Jira_Temp database and removed the /data/jira3135/indexes directory (and recreated). ## (/) I downloaded the enterprise version of the 3.13.5 server. I made a copy in the /opt directory and unzipped and untarred the file. ## (/) I went back to crowd and edited the application to change the properties to: ### URL: http://bugs.shore.mbari.org:8080 ### IP: 134.89.12.31 ### Name: jira3135 ### Password: (ask Kevin) :) ## (/) I then repeated the steps above to get the server up and running # Schedule upgrade date and send all hands several days in advance. # When the day arrives, send all hands announcing JIRA outage. # From the Administrator's page in our existing JIRA, perform a 'Backup Data to XML'. # Login to oceana.mbari.org as root. # Shutdown JIRA # Create a tar.gz of the /opt/atlassian-jira-enterprise-3.12.1-standalone directory # Clean up the /data/jira_3_12/backups directory by deleting all but maybe the last 5 backups. # Create a tar.gz of the JIRA home directory on ocean.mbari.org which is located at /data/jira_3_12 # scp both tar.gz files to bugs.mbari.org # login to bugs.mbari.org # Unpack the home directory tar to /data/jira # Run the installer as root (this might need IS help or sudo privs). Note that we usually install the application to /opt # Run the JIRA Configuration tool to set the jira.home to the /data/jira location # Connect to JIRA_Temp database on Solstice2 (.... more to do here, see Atlassian docs) # Migrate existing configuration over to new JIRA (I need to add more here as we added Crowd). # Start JIRA # Import backed up XML # Perform post upgrades checks and tests *Need to document steps for 4.4.5->6.X* ]]> 27557988 26673156 ** response ** 0 * Channel 1 Power Control = 0 (Off) ** $1PC0 ** Response: ** 0 * Channel 1 Power Control = 1 (On) ** $1PC1 ** Response: ** 1 * Channel 1 Power Read ** $1PR ** Response: ** 1 * Read Block ** $1RB read temperature sensor block (4 channels) ** $5RB read pH sensor block (Seabird 18s) ** Response: ** \*+02712.00 ** \*+00200.00 ** \*+00125.76 ** \*+00347.95 * Read Data ** $1RD read tDGH channel 1 (temperature ch 1) ** $2RD read tDGH channel 2 (temperature ch 2) ** $3RD read tDGH channel 3 (temperature ch 3) ** $4RD read tDGH channel 4 (temperature ch 4) ** $5RD read tDGH channel 5 (pH sensor ch 1) ** $6RD read tDGH channel 6 (pH sensor ch 2) ** $7RD read tDGH channel 7 (pH sensor ch 3) ** $8RD read tDGH channel 8 (pH sensor ch 4) ** $9RD read tDGH channel 9 (pH sensor ch 5)]]> 26640388 27590748 4.4: [https://confluence.atlassian.com/display/JIRA044/Migrating+JIRA+to+Another+Server] ## The JIRA configuration tool: [https://confluence.atlassian.com/display/JIRA044/Using+the+JIRA+Configuration+Tool] h5. Steps # (/) Create new VM named bugs.mbari.org in the DMZ # (/) Have Neil create database Jira_Temp on solstice2.shore.mbari.org # (/) Have Neil create database Jira on solstice2.shore.mbari.org # (/) Have Pat install Java 7 on bugs.shore.mbari.org # (/) Have Pete plumb holes through firewall so processes on bugs.mbari.org can get to Solstice2 # (/) Have Pat create DB_Collaboration account on bugs so it can run JIRA under that account and it can connect to solstice2 using that NT Domain account. # (/) Upgrade license on Atlassian site # (/) Log into bugs.shore.mbari.org # (/) Download 3.13.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 4.4.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 5.2.11 standalone Linux 64 bit tar.gz (not sure this version is necessary, but at least I have it) # (/) Unzip and untar the file to /opt # (/) Download latest JIRA (6.4.7 as of this writing). # (/) Unzip and untar it to /opt # Performed Test Upgrade ## (/) In order to export the current stuff in JIRA, I had to shut off access so people could not change the data while I was backing it up. ## (/) I ssh'd to oceana.mbari.org as root and edited the /opt/jira/conf/server.xml file and commented out the Connector section that had the port of 8010 to shut it off from the normal serving route. ## (/) I uncommented the 8082 port connector and the 8443 port connector so that I could still get to the server. ## (/) I stopped and started the JIRA server and in the log file I got a "keystore was tampered with..." which is not surprising. ## (/) I could then browser over to http://oceana.mbari.org:8082/jira ## (/) Then through the Administration console, I did an XML backup ## (/) I then created a tar of all the attachments in the /data/jira_3_12/attachments directory ## (/) I moved both the XML and tar files to the /root/jira-upgrade directory ## (/) I then reversed the changes to the server.xml file and shut down JIRA ## (/) I left it down during the next steps in case it went so well, I could just point people to the new server (yeah, right). ## (/) I then browsed to the crowd server on oceana and add a new application using: ### URL: http://bugs.mbari.org/jira3135 ### IP: 134.89.2.29 ### Name: JIRA3135 ### Password: (ask Kevin) :) ## (/) On bugs, I made a copy of the JIRA 3.13.5 download in the /opt directory and unzipped and untarred it. ## (/) In order to configure the crowd connection I did the following: ### (/) I scp'd the /opt/crowd/client/crowd-integration-client-1.6.jar file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I removed the existing 1.6.1 crowd client jar from the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I scp'd the /opt/crowd/client/conf/crowd.properties file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I scp'd the /opt/crowd/client/conf/crowd-ehcache.xml file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I edited the crowd.properties file on bugs to look like: {noformat} application.name JIRA3135 application.password (ask Kevin) application.login.url http://oceana.mbari.org:8095/crowd/console/ crowd.server.url http://oceana.mbari.org:8095/crowd/services/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 0 session.lastvalidation session.lastvalidation {noformat} ### (/) I edited the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/osuser.xml file to comment out the current authentication mechanism and then uncomment the crowd one. ## (/) I then edited the /opt/atlassian-jira-standalone-3.13.5/conf/server/xml file and configured the database connection to the Jira_Temp database on Solstice2. I looked like this: {noformat} {noformat} ## (/) I edited the /etc/httpd/conf/httpd.conf file and created a proxy pass at the bottom of the file to point a normal URL to the default port 8080 for JIRA: {noformat} # Proxy Pass for JIRA ProxyPass http://bugs.mbari.org:8080 ProxyPassReverse http://bugs.mbari.org:8080 {noformat} ## (/) I restarted Apache ## (/) I scp'd the jtds driver from oceana to the /opt/atlassian-jira-standalone-3.13.5/common/lib directory (you could down from the internet) ## (/) I then went to the /opt/atlassian-jira-standalone-3.13.5/ directory and ran './bin/startup.sh'. From the log file, I could tell things were hanging. After some troubleshooting I am wondering if the local firewall is preventing the application to get access to the database on solstice2. I can telnet to port 1433, but I can't browse to the base http://bugs.mbari.org from anywhere but the local web browser. I have submitted a ticket. ## (/) I restarted the old JIRA with my hopes dashed :(. ## (/) Pat disabled the firewall on bugs.mbari.org but it still hung trying to connect to solstice2.shore.mbari.org. That is really, really perplexing. # Schedule upgrade date and send all hands several days in advance. # When the day arrives, send all hands announcing JIRA outage. # From the Administrator's page in our existing JIRA, perform a 'Backup Data to XML'. # Login to oceana.mbari.org as root. # Shutdown JIRA # Create a tar.gz of the /opt/atlassian-jira-enterprise-3.12.1-standalone directory # Clean up the /data/jira_3_12/backups directory by deleting all but maybe the last 5 backups. # Create a tar.gz of the JIRA home directory on ocean.mbari.org which is located at /data/jira_3_12 # scp both tar.gz files to bugs.mbari.org # login to bugs.mbari.org # Unpack the home directory tar to /data/jira # Run the installer as root (this might need IS help or sudo privs). Note that we usually install the application to /opt # Run the JIRA Configuration tool to set the jira.home to the /data/jira location # Connect to JIRA_Temp database on Solstice2 (.... more to do here, see Atlassian docs) # Migrate existing configuration over to new JIRA (I need to add more here as we added Crowd). # Start JIRA # Import backed up XML # Perform post upgrades checks and tests *Need to document steps for 4.4.5->6.X* ]]> 27557982 27590750 4.4: [https://confluence.atlassian.com/display/JIRA044/Migrating+JIRA+to+Another+Server] ## The JIRA configuration tool: [https://confluence.atlassian.com/display/JIRA044/Using+the+JIRA+Configuration+Tool] h5. Steps # (/) Create new VM named bugs.mbari.org in the DMZ # (/) Have Neil create database Jira_Temp on solstice2.shore.mbari.org # (/) Have Neil create database Jira on solstice2.shore.mbari.org # (/) Have Pat install Java 7 on bugs.shore.mbari.org # (/) Have Pete plumb holes through firewall so processes on bugs.mbari.org can get to Solstice2 # (/) Have Pat create DB_Collaboration account on bugs so it can run JIRA under that account and it can connect to solstice2 using that NT Domain account. # (/) Upgrade license on Atlassian site # (/) Log into bugs.shore.mbari.org # (/) Download 3.13.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 4.4.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 5.2.11 standalone Linux 64 bit tar.gz (not sure this version is necessary, but at least I have it) # (/) Unzip and untar the file to /opt # (/) Download latest JIRA (6.4.7 as of this writing). # (/) Unzip and untar it to /opt # Performed Test Upgrade ## (/) In order to export the current stuff in JIRA, I had to shut off access so people could not change the data while I was backing it up. ## (/) I ssh'd to oceana.mbari.org as root and edited the /opt/jira/conf/server.xml file and commented out the Connector section that had the port of 8010 to shut it off from the normal serving route. ## (/) I uncommented the 8082 port connector and the 8443 port connector so that I could still get to the server. ## (/) I stopped and started the JIRA server and in the log file I got a "keystore was tampered with..." which is not surprising. ## (/) I could then browser over to http://oceana.mbari.org:8082/jira ## (/) Then through the Administration console, I did an XML backup ## (/) I then created a tar of all the attachments in the /data/jira_3_12/attachments directory ## (/) I moved both the XML and tar files to the /root/jira-upgrade directory ## (/) I then reversed the changes to the server.xml file and shut down JIRA ## (/) I left it down during the next steps in case it went so well, I could just point people to the new server (yeah, right). ## (/) I then browsed to the crowd server on oceana and add a new application using: ### URL: http://bugs.mbari.org/jira3135 ### IP: 134.89.2.29 ### Name: JIRA3135 ### Password: (ask Kevin) :) ## (/) On bugs, I made a copy of the JIRA 3.13.5 download in the /opt directory and unzipped and untarred it. ## (/) In order to configure the crowd connection I did the following: ### (/) I scp'd the /opt/crowd/client/crowd-integration-client-1.6.jar file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I removed the existing 1.6.1 crowd client jar from the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I scp'd the /opt/crowd/client/conf/crowd.properties file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I scp'd the /opt/crowd/client/conf/crowd-ehcache.xml file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I edited the crowd.properties file on bugs to look like: {noformat} application.name JIRA3135 application.password (ask Kevin) application.login.url http://oceana.mbari.org:8095/crowd/console/ crowd.server.url http://oceana.mbari.org:8095/crowd/services/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 0 session.lastvalidation session.lastvalidation {noformat} ### (/) I edited the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/osuser.xml file to comment out the current authentication mechanism and then uncomment the crowd one. ## (/) I then edited the /opt/atlassian-jira-standalone-3.13.5/conf/server/xml file and configured the database connection to the Jira_Temp database on Solstice2. I looked like this: {noformat} {noformat} ## (/) I edited the /etc/httpd/conf/httpd.conf file and created a proxy pass at the bottom of the file to point a normal URL to the default port 8080 for JIRA: {noformat} # Proxy Pass for JIRA ProxyPass http://bugs.mbari.org:8080 ProxyPassReverse http://bugs.mbari.org:8080 {noformat} ## (/) I restarted Apache ## (/) I scp'd the jtds driver from oceana to the /opt/atlassian-jira-standalone-3.13.5/common/lib directory (you could down from the internet) ## (/) I then went to the /opt/atlassian-jira-standalone-3.13.5/ directory and ran './bin/startup.sh'. From the log file, I could tell things were hanging. After some troubleshooting I am wondering if the local firewall is preventing the application to get access to the database on solstice2. I can telnet to port 1433, but I can't browse to the base http://bugs.mbari.org from anywhere but the local web browser. I have submitted a ticket. ## (/) I restarted the old JIRA with my hopes dashed :(. ## (/) Pat disabled the firewall on bugs.mbari.org but it still hung trying to connect to solstice2.shore.mbari.org. That is really, really perplexing. Neil mentioned that solstice2 is using Kerberos and solstice is not. Checking with the JTDS docs, version 1.3.1 of the driver added kerberos support, so I downloaded that driver and added the 'userKerberos=true' property to the URL in the server.xml file and restarted. Got an error about no credentials, so added user and password properties to the URL. Nope, no luck. # Schedule upgrade date and send all hands several days in advance. # When the day arrives, send all hands announcing JIRA outage. # From the Administrator's page in our existing JIRA, perform a 'Backup Data to XML'. # Login to oceana.mbari.org as root. # Shutdown JIRA # Create a tar.gz of the /opt/atlassian-jira-enterprise-3.12.1-standalone directory # Clean up the /data/jira_3_12/backups directory by deleting all but maybe the last 5 backups. # Create a tar.gz of the JIRA home directory on ocean.mbari.org which is located at /data/jira_3_12 # scp both tar.gz files to bugs.mbari.org # login to bugs.mbari.org # Unpack the home directory tar to /data/jira # Run the installer as root (this might need IS help or sudo privs). Note that we usually install the application to /opt # Run the JIRA Configuration tool to set the jira.home to the /data/jira location # Connect to JIRA_Temp database on Solstice2 (.... more to do here, see Atlassian docs) # Migrate existing configuration over to new JIRA (I need to add more here as we added Crowd). # Start JIRA # Import backed up XML # Perform post upgrades checks and tests *Need to document steps for 4.4.5->6.X* ]]> 27557984 27590736 4.4: [https://confluence.atlassian.com/display/JIRA044/Migrating+JIRA+to+Another+Server] ## The JIRA configuration tool: [https://confluence.atlassian.com/display/JIRA044/Using+the+JIRA+Configuration+Tool] h5. Steps # (/) Create new VM named bugs.mbari.org in the DMZ # (/) Have Neil create database JIRA_Temp on solstice2.shore.mbari.org # (/) Have Neil create database JIRA on solstice2.shore.mbari.org # (/) Have Pat install Java 7 on bugs.shore.mbari.org # (/) Have Pete plumb holes through firewall so processes on bugs.mbari.org can get to Solstice2 # (/) Have Pat create DB_Collaboration account on bugs so it can run JIRA under that account and it can connect to solstice2 using that NT Domain account. # (/) Upgrade license on Atlassian site # (/) Log into bugs.shore.mbari.org # (/) Download 4.4.5 standalone Linux 64 bit installer (bin) # (/) chmod a+x on the installer # Schedule upgrade date and send all hands several days in advance. # When the day arrives, send all hands announcing JIRA outage. # From the Administrator's page in our existing JIRA, perform a 'Backup Data to XML'. # Login to oceana.mbari.org as root. # Shutdown JIRA # Create a tar.gz of the /opt/atlassian-jira-enterprise-3.12.1-standalone directory # Clean up the /data/jira_3_12/backups directory by deleting all but maybe the last 5 backups. # Create a tar.gz of the JIRA home directory on ocean.mbari.org which is located at /data/jira_3_12 # scp both tar.gz files to bugs.mbari.org # login to bugs.mbari.org # Unpack the home directory tar to /data/jira # Run the installer as root (this might need IS help or sudo privs). Note that we usually install the application to /opt # Run the JIRA Configuration tool to set the jira.home to the /data/jira location # Connect to JIRA_Temp database on Solstice2 (.... more to do here, see Atlassian docs) # Migrate existing configuration over to new JIRA (I need to add more here as we added Crowd). # Start JIRA # Import backed up XML # Perform post upgrades checks and tests *Need to document steps for 4.4.5->6.X* ]]> 27557970 27590738 4.4: [https://confluence.atlassian.com/display/JIRA044/Migrating+JIRA+to+Another+Server] ## The JIRA configuration tool: [https://confluence.atlassian.com/display/JIRA044/Using+the+JIRA+Configuration+Tool] h5. Steps # (/) Create new VM named bugs.mbari.org in the DMZ # (/) Have Neil create database Jira_Temp on solstice2.shore.mbari.org # (/) Have Neil create database Jira on solstice2.shore.mbari.org # (/) Have Pat install Java 7 on bugs.shore.mbari.org # (/) Have Pete plumb holes through firewall so processes on bugs.mbari.org can get to Solstice2 # (/) Have Pat create DB_Collaboration account on bugs so it can run JIRA under that account and it can connect to solstice2 using that NT Domain account. # (/) Upgrade license on Atlassian site # (/) Log into bugs.shore.mbari.org # (/) Download 4.4.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download latest JIRA (6.1.7 as of this writing). # (/) Unzip and untar it to /opt # Perform test upgrade ## # Schedule upgrade date and send all hands several days in advance. # When the day arrives, send all hands announcing JIRA outage. # From the Administrator's page in our existing JIRA, perform a 'Backup Data to XML'. # Login to oceana.mbari.org as root. # Shutdown JIRA # Create a tar.gz of the /opt/atlassian-jira-enterprise-3.12.1-standalone directory # Clean up the /data/jira_3_12/backups directory by deleting all but maybe the last 5 backups. # Create a tar.gz of the JIRA home directory on ocean.mbari.org which is located at /data/jira_3_12 # scp both tar.gz files to bugs.mbari.org # login to bugs.mbari.org # Unpack the home directory tar to /data/jira # Run the installer as root (this might need IS help or sudo privs). Note that we usually install the application to /opt # Run the JIRA Configuration tool to set the jira.home to the /data/jira location # Connect to JIRA_Temp database on Solstice2 (.... more to do here, see Atlassian docs) # Migrate existing configuration over to new JIRA (I need to add more here as we added Crowd). # Start JIRA # Import backed up XML # Perform post upgrades checks and tests *Need to document steps for 4.4.5->6.X* ]]> 27557972 19073665 19040973 19073664 19040972 13959254 13926490 13959252 13926488 27100029 27067275 27100027 27067273 27100031 27067277 13959246 13926482 27100021 27067267 27100020 27067266 13959250 13926486 13959248 13926484 27100023 27067269 8093710 BOOT PICO CF2> BOOT APP for deployment RMC message for A or V (Tracking or DR - tells wether GPS is tracking) \\ First Tasks 1) Add to Prompt GPS OK, RGPS Age OK, AGC OK, Platform Track OK (ask once every 4sec to avoid swamping the Seatel) 2) Create NMEA style string on Spare2 hooked to 24 port terminal server for continuous stream of updates to be displayed by a GUI \\ \\ \\ \\ Seatel SEA TEL MODEl TAC-92 USER INTERFACE DESCRIPTI0N VERSION 1.61 1.0 COMMAND SUMMARY | CONTROL CODES: | FUNCTION | | | 6 | Azimuth CW one step (system step reselution) | | 4 | Azimuth CCW one step | | 8 | Elevation up one step | | 2 | Elevation DOWN one step | | Aaaaa{} | Move AZ to aaa.a deg , true or magnetic | | Baaaa{} | Set ships heading to aaa.a degrees | | C | Step Track ON | | D | Step Track and Tracking OFF | | cnnnn{} | Set MHz/CHA tuning to nnnn MHz | | dnnnn{} | Set KHz/CHB tuning to nnnn KHz | | Eeeee{} | Move EL to ee.e or eee.e degrees | | F | Toggle auto unwrap ON/OFF | | gnnn {} | Set polang position to nnn | | Jrrrr{} | Move azimuth to ship relative position | | Nnnn{ } | Set number of signal strength updates (1-255) | | Onnn{ } | Output data to EME equipment | | R | start spiral search fot satellite | | S | Advance AGC input selectien (Ext, ChA, ChB, IF) | | Taaaa{} | Move to satellite at aaa.a degrees | | U | Force cable unwrap | | W | Write parameters to NV RAM | | Xnnn{} | Set azimuth step track size to nnn steps (1-255) | | Ynnn{} | Set elevation step track size to nnn steps (0-255) | | Z | Toggle C/Ku step size selection | | esc | Cancel pending numeric command | | $mmmmm{} | NMEA Latitude / Longitude input (GPGLL format) | | MONITOR CODES | FUNCTION | TAC RESPONSE | | H | Relative Az,Ship Heading | RrrrrHaaaa,CR,LF,> | | M | Tracking Parameters | Xnnn Ynnn Nnnn cc,CR,LF,> | | P | Az/EL Position | EeeeeAaaaa,CR,LF,> | | s | TaC Status | Snn,CR,LF1> | | V | Software Version | TAC-92 VER N,NN,CR,LF, > | | q | Tuning >Frequencies , Input | Qnnnn nnnn s,CR,LF,> | | u | Polang position | Gnnn ,CR,LF,> | | % | Signal Strength | Lnnnn,CR,LF,> | | & | Error Status | &nnn ,CR,LF,> | | ABBREVIATIONS: | | eeee = | Elevation angle oooo to 0900 nominal 0000 to 3599 range | | aaaa = | True/Magnetic Azimuth 0000 to 3599 range | | rrrr = | Relative azimuth 0950 to 6250 1ange | | nnnn = | A5CII decimal number 0000-9999 | | nnn = | ASCII decima\[ number 0 to 255 | | nn = | System Status twO bitmaped ASCII characters | | cc = | C /Ku tracking parameter bank selection | | s = | AGC receiver selection 0,l,2,3 | | {} = | Carriage return | April 30, 1996 Doc No. 112862-D \\ \\]]> 8060942 8093708 8060940 13959330 13926568 27590911 4.4: [https://confluence.atlassian.com/display/JIRA044/Migrating+JIRA+to+Another+Server] ## The JIRA configuration tool: [https://confluence.atlassian.com/display/JIRA044/Using+the+JIRA+Configuration+Tool] h5. Steps # (/) Create new VM named bugs.mbari.org in the DMZ # (/) Have Neil create database Jira_Temp on solstice2.shore.mbari.org # (/) Have Neil create database Jira on solstice2.shore.mbari.org # (/) Have Pat install Java 7 on bugs.shore.mbari.org # (/) Have Pete plumb holes through firewall so processes on bugs.mbari.org can get to Solstice2 # (/) Have Pat create DB_Collaboration account on bugs so it can run JIRA under that account and it can connect to solstice2 using that NT Domain account. # (/) Upgrade license on Atlassian site # (/) Log into bugs.shore.mbari.org # (/) Download 3.13.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 4.4.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 5.2.11 standalone Linux 64 bit tar.gz (not sure this version is necessary, but at least I have it) # (/) Unzip and untar the file to /opt # (/) Download latest JIRA (6.4.7 as of this writing). # (/) Unzip and untar it to /opt # Performed Test Upgrade ## (/) In order to export the current stuff in JIRA, I had to shut off access so people could not change the data while I was backing it up. ## (/) I ssh'd to oceana.mbari.org as root and edited the /opt/jira/conf/server.xml file and commented out the Connector section that had the port of 8010 to shut it off from the normal serving route. ## (/) I uncommented the 8082 port connector and the 8443 port connector so that I could still get to the server. ## (/) I stopped and started the JIRA server and in the log file I got a "keystore was tampered with..." which is not surprising. ## (/) I could then browser over to http://oceana.mbari.org:8082/jira ## (/) Then through the Administration console, I did an XML backup ## (/) I then created a tar of all the attachments in the /data/jira_3_12/attachments directory ## (/) I moved both the XML and tar files to the /root/jira-upgrade directory ## (/) I then reversed the changes to the server.xml file and shut down JIRA ## (/) I left it down during the next steps in case it went so well, I could just point people to the new server (yeah, right). ## (/) I then browsed to the crowd server on oceana and add a new application using: ### URL: http://bugs.mbari.org/jira3135 ### IP: 134.89.2.29 ### Name: JIRA3135 ### Password: (ask Kevin) :) ## (/) On bugs, I made a copy of the JIRA 3.13.5 download in the /opt directory and unzipped and untarred it. ## (/) In order to configure the crowd connection I did the following: ### (/) I scp'd the /opt/crowd/client/crowd-integration-client-1.6.jar file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I removed the existing 1.6.1 crowd client jar from the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I scp'd the /opt/crowd/client/conf/crowd.properties file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I scp'd the /opt/crowd/client/conf/crowd-ehcache.xml file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I edited the crowd.properties file on bugs to look like: {noformat} application.name JIRA3135 application.password (ask Kevin) application.login.url http://oceana.mbari.org:8095/crowd/console/ crowd.server.url http://oceana.mbari.org:8095/crowd/services/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 0 session.lastvalidation session.lastvalidation {noformat} ### (/) I edited the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/osuser.xml file to comment out the current authentication mechanism and then uncomment the crowd one. ## (/) I then edited the /opt/atlassian-jira-standalone-3.13.5/conf/server/xml file and configured the database connection to the Jira_Temp database on Solstice2. I looked like this: {noformat} {noformat} ## (/) Edit the /opt/atlassian/jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/entityengine.xml and changed it from 'hsql' to 'mssql' and delete the line with "PUBLIC" in it per the instructions in the comments in that file. ## (/) I edited the /etc/httpd/conf/httpd.conf file and created a proxy pass at the bottom of the file to point a normal URL to the default port 8080 for JIRA: {noformat} # Proxy Pass for JIRA ProxyPass http://bugs.mbari.org:8080 ProxyPassReverse http://bugs.mbari.org:8080 {noformat} ## (/) I restarted Apache ## (/) I scp'd the jtds driver from oceana to the /opt/atlassian-jira-standalone-3.13.5/common/lib directory (you could down from the internet) ## (/) I then went to the /opt/atlassian-jira-standalone-3.13.5/ directory and ran './bin/startup.sh'. From the log file, I could tell things were hanging. After some troubleshooting I am wondering if the local firewall is preventing the application to get access to the database on solstice2. I can telnet to port 1433, but I can't browse to the base http://bugs.mbari.org from anywhere but the local web browser. I have submitted a ticket. ## (/) I restarted the old JIRA with my hopes dashed :(. ## (/) Pat disabled the firewall on bugs.mbari.org but it still hung trying to connect to solstice2.shore.mbari.org. That is really, really perplexing. Neil mentioned that solstice2 is using Kerberos and solstice is not. Checking with the JTDS docs, version 1.3.1 of the driver added kerberos support, so I downloaded that driver and added the 'userKerberos=true' property to the URL in the server.xml file and restarted. Got an error about no credentials, so added user and password properties to the URL. Nope, no luck. Never did figure this one out, but I had Pat pull the VM inside the firewall and after some thrash it worked. Well, it sort of worked ... sigh. It turns out I had downloaded the standard version instead of the enterprise version. I need to redo this work ... grrr. ## (/) I deleted all the tables in the Jira_Temp database and removed the /data/jira3135/indexes directory (and recreated). ## (/) I downloaded the enterprise version of the 3.13.5 server. I made a copy in the /opt directory and unzipped and untarred the file. ## (/) I went back to crowd and edited the application to change the properties to: ### URL: http://bugs.shore.mbari.org:8080 ### IP: 134.89.12.31 ### Name: jira3135 ### Password: (ask Kevin) :) ## (/) I then repeated the steps above to get the server up and running with the following differences: ### The server name is now bugs.shore.mbari.org ### The paths given above are a little different in that they no longer say "standard" but say "enterprise" ### I deleted the proxy pass as it seemed to have issues before and this is only temporary anyway. ## (/) I then browsed to http://bugs.shore.mbari.org:8080 ## (/) It took me to the start up page and at the top was the option to 'import your existing data'. Seemed too good not to try. I clicked on the link. It asked me for the backup file location and the location where the indexes would be stored. ## (/) I copied the XML zip file and the attachments tar file to the /data/original directory. ## (/) I created the /data/jira3135/indexes and used those directories ... it fired off the import and I waited. ## (/) I tailed the log file to watch the import. Holy crap, it worked!!! I could log in and everything! I copied the results from the log file here for posterity sake: {noformat} 2015-07-22 20:55:45,156 http-8080-Processor22 INFO [jira.action.admin.DataImport] Running data import 2015-07-22 20:55:45,179 http-8080-Processor22 INFO [jira.action.admin.DataImport] Importing data.. 2015-07-22 20:55:45,186 http-8080-Processor22 INFO [jira.action.admin.DataImport] Start parsing XML with SAX Parser 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] XML successfully parsed 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] Removing all entries from the database. 2015-07-22 20:56:24,593 http-8080-Processor22 INFO [jira.action.admin.DataImport] All entries removed. 2015-07-22 20:56:24,594 http-8080-Processor22 INFO [jira.action.admin.DataImport] Started storing 410414 Generic Values 2015-07-22 21:01:51,967 http-8080-Processor22 INFO [jira.action.admin.DataImport] Finished storing Generic Values 2015-07-22 21:01:52,329 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:52,361 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:54,683 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLink' to module 'jira.user.format:profile-link-user-format'. 2015-07-22 21:01:54,724 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullName' to module 'jira.user.format:full-name-user-format'. 2015-07-22 21:01:54,773 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkSearcher' to module 'jira.user.format:profile-link-searcher-user-format'. 2015-07-22 21:01:54,784 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkExternal' to module 'jira.user.format:profile-link-external-user-format'. 2015-07-22 21:01:54,795 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkActionHeader' to module 'jira.user.format:profile-link-action-header-user-format'. 2015-07-22 21:01:54,807 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullProfile' to module 'jira.user.format:full-profile-user-format'. 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/comments 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/issues 2015-07-22 21:01:55,641 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/plugins 2015-07-22 21:01:55,867 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:01:55,871 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/issues does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:55,873 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/comments does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,033 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,257 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,889 http-8080-Processor22 ERROR [atlassian.jira.upgrade.ConsistencyCheckImpl] Attachments are turned on, but attachment path [/data/jira_3_12/attachments] invalid - disabling attachments 2015-07-22 21:02:13,904 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Detected that an upgrade is needed; existing data at build 299 2015-07-22 21:02:13,907 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Doing Upgrade... 2015-07-22 21:02:13,915 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value' succeeded 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 317 2015-07-22 21:02:13,944 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite filters - make each filter a favourite of its owner. 2015-07-22 21:02:17,822 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build319] Could not find author 'fpy' for filter with id '10040' 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite filters - make each filter a favourite of its owner.' succeeded 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 319 2015-07-22 21:02:17,995 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise Share Permissions. Move old shares to new shares. 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise Share Permissions. Move old shares to new shares.' succeeded 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 321 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Migrating the old JIRA UI colors to the new JIRA 3.13 colors 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build322] Custom color detected for jira.lf.menu.bgcolour : #336699 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Migrating the old JIRA UI colors to the new JIRA 3.13 colors' succeeded 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 322 2015-07-22 21:02:18,025 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite dashboards - make each dashboard a favourite of its owner. 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'cmcgann' for dashboard with id '10030' 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'fpy' for dashboard with id '10060' 2015-07-22 21:02:18,423 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'kanna' for dashboard with id '10040' 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite dashboards - make each dashboard a favourite of its owner.' succeeded 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 325 2015-07-22 21:02:18,625 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Reindexing all data in JIRA to include Favourites. 2015-07-22 21:02:18,648 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All starting... 2015-07-22 21:02:18,650 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 0% complete. Current index: Issue 2015-07-22 21:02:18,654 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:02:18,809 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 1% complete. Current index: Issue 2015-07-22 21:02:18,855 indexerPool-2-thread-10 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 2% complete. Current index: Issue 2015-07-22 21:02:18,899 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 3% complete. Current index: Issue 2015-07-22 21:02:18,945 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 4% complete. Current index: Issue 2015-07-22 21:02:19,012 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 5% complete. Current index: Issue . . . 2015-07-22 21:02:26,164 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 95% complete. Current index: Issue 2015-07-22 21:02:26,232 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 96% complete. Current index: Issue 2015-07-22 21:02:26,316 indexerPool-2-thread-9 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 97% complete. Current index: Issue 2015-07-22 21:02:26,771 indexerPool-2-thread-3 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: Issue 2015-07-22 21:02:27,261 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 8607ms. Indexer: DefaultIndexManager: paths: [/data/jira3135/indexes/issues, /data/jira3135/indexes/comments] 2015-07-22 21:02:27,263 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: SearchRequest 2015-07-22 21:02:27,268 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,293 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: SearchRequest 2015-07-22 21:02:27,308 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: PortalPage 2015-07-22 21:02:27,312 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,377 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: PortalPage 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 115ms. Indexer: SharedEntityIndexManager: paths: [/data/jira3135/indexes/entities/portalpage, /data/jira3135/indexes/entities/searchrequest] 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All complete. Total time: 8722ms. 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Reindexing all data in JIRA to include Favourites.' succeeded 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 326 2015-07-22 21:02:27,397 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade succeeded! Setting data build number to 360 2015-07-22 21:02:27,469 JiraQuartzScheduler_Worker-0 WARN [service.services.export.ExportService] Backup directory /data/jira_3_12/backup does not exist {noformat} {warning:title=Paths} It appears that the upgraded JIRA will still look for the attachments and the backup locations in the original places. So I created /data/jira_3_12/backup and untarred the original attachments to /data/jira_3_12 and then everything worked (including attachements) in the new JIRA. {warning} ## (/) I then used the upgraded JIRA to generate a new XML backup and stored it in /data/original/3.13.5 along with another tar of the files in /data/jira_3_12/attachments. ## (/) I then shutdown the JIRA server. *I should be ready to move on to version 4 upgrade WHEW* ## So, before moving on, I decided that it would be a really good idea to spin up a new Crowd instance to get rid of the :8443 in the URL and to move off of RedHat per IS requests. I have a ticket in for a new VM and a new database to try to get this going. I am waiting on that before moving on. ## (/) Pat created the VM and Neil created the database. ## (/) I logged into auth.mbari.org (name of the VM) and downloaded crowd which I unzipped to the /opt directory ## (/) I then created a /data/crowd directory and gave my account permissions on it and then edited the /opt/atlassian..../crowd-webapp/WEB-INF/classes/crowd-init.properties file to set that as the crowd home directory. ## (/) The instructions say to download the JDBC driver, but they already have JTDS 1.2.7 in the download so I did not do anything. ## (/) You have to manually connect up CrowdID to a database as they setup wizard does not currently do this. ### (/) They say to download the driver, but again 1.2.7 was there so I did nothing. ### (/) I edited the /opt/atlassian.../apache-tomcat/conf/Catalina/localhost/openidserver.xml to look like: {noformat} {noformat} ### (/) I edited the /opt/atlassian.../build.properties files to look like: {noformat} # Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See https://confluence.atlassian.com/display/CROWD/Connecting+Crowd+to+a+Database hibernate.dialect=org.hibernate.dialect.SQLServerDialect # The Hibernate transaction factory to use. See https://confluence.atlassian.com/display/CROWD/Configuring+Crowd hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory # The http port you wish to run crowd from, ie: http://localhost:8095/crowd crowd.tomcat.connector.port=8095 # Tomcat requires a unique port for shutdown crowd.tomcat.shutdown.port=8020 # Crowd context root crowd.url=http://localhost:8095/crowd # Demo context root demo.url=http://localhost:8095/demo # OpenID server context root openidserver.url=http://localhost:8095/openidserver {noformat} ### (/) I then ran the build.sh script in the root of /opt/atlassian... ## (/) I fired up crowd using the /opt/atlassian.../start_crowd.sh script ## (/) I then went to http://auth.mbari.org:8095/crowd to kick off the start up wizard ## (/) I grabbed a new eval license from my account on atlassian and pasted into the license page. ## (/) I selected "New install" on the next page. ## (/) I configured the JDBC connection using this connection URL with user DB_Collaboration {noformat} jdbc:jtds:sqlserver://dione.mbari.org:51001/Crowd;domain=SHORE;useNTLMv2=TRUE {noformat} ## (/) I left the "Options" as they came up {warning:title=Paths} Not sure if this is a problem, but because I started the set up using auth.mbari.org, it set the Base URL to http://auth.mbari.org:8095/crowd instead of localhost. Hope that is not a problem. We will see. {warning} ## (/) I configured the email connection using the settings from [here|https://wind.shore.mbari.org/is/howto/email/mbarimail/imap] and I used my network login (probably shouldn't be doing that ... not sure where it stores my password, but I am assuming in the DB). ## (/) For the local admin account, I created a user named 'crowdadm' so it would not clash with my LDAP account. See Kevin Gomes for password information. ## (/) I checked the OpenID server as an integrated application ## (/) It then took me to the login page and I logged in using the newly minted admin account. Seemed all is well so far. ## (/) I visited the openidserver URL as well and that seemed OK. ## (/) I decided to wait on configuring the MBARI LDAP directory until I got everything with SSL working. ## (/) Now the next step was to follow the directions to configure Crowd to run over SSL found [here|https://confluence.atlassian.com/display/CROWD/Configuring+Crowd+to+Work+with+SSL] ## (/) I shutdown crowd. Note that the stop script does not shutdown things correctly and I noticed the crowd app running as root. That should not be if I started as kgomes. Not sure what is up with that. ## (/) Now Joe had already configured SSL once, so I used his connector configuration in the server.xml file and so the final file looked like: {noformat} {noformat} ## (/) I then edited the /data/crowd/crowd.properties to look like: {noformat} #Sat Aug 01 09:05:15 PDT 2015 session.lastvalidation=session.lastvalidation session.tokenkey=session.tokenkey crowd.server.url=https\://localhost\:8443/crowd/services/ application.name=crowd http.timeout=30000 session.isauthenticated=session.isauthenticated application.login.url=https\://localhost\:8443/crowd/console/ session.validationinterval=0 application.password=Y1Xp3OorCmsOP4eruL1dmH {noformat} One thing to note here is that based on a comment from the SSL configuration page at atlassian (Steve's comment), you are supposed to leave all the host names the same. For example, if the file says localhost, leave it localhost. So this created a bit of a problem based on the fact that I had left the base URL pointing to auth.mbari.org in the wizard steps above. That step wrote auth.mbari.org to the /data/crowd/crowd.properties. All the other files reference localhost, so to be consistent, I changed auth.mbari.org to localhost in the /data/crowd/crowd.properties file. We will see if this works. ## (/) Per the instructions on the atlassian page (referenced above), I also edited the build.properties file and the /client/conf/crowd.properties files before I restarted and used the SSL URLs ## build.properties: {noformat} # Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See https://confluence.atlassian.com/display/CROWD/Connecting+Crowd+to+a+Database hibernate.dialect=org.hibernate.dialect.SQLServerDialect # The Hibernate transaction factory to use. See https://confluence.atlassian.com/display/CROWD/Configuring+Crowd hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory # The http port you wish to run crowd from, ie: http://localhost:8095/crowd crowd.tomcat.connector.port=8095 # Tomcat requires a unique port for shutdown crowd.tomcat.shutdown.port=8020 # Crowd context root crowd.url=https://localhost:8443/crowd # Demo context root demo.url=https://localhost:8443/demo # OpenID server context root openidserver.url=https://localhost:8443/openidserver {noformat} ## crowd.properties (client) {noformat} application.name crowd application.password password application.login.url https://localhost:8443/crowd/console/ crowd.server.url https://localhost:8443/crowd/services/ crowd.base.url https://localhost:8443/crowd/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 2 session.lastvalidation session.lastvalidation {noformat} ## (/) Although not stated, I am assuming you would need to run the build.sh script to push the build.properties changes to their proper places, so I did that. Note that before doing that, I know that it will clobber the server.xml changes I made, so I made a copy of that file and diff'd them after and then rolled the previous changes to the new server.xml file. Actually, amazingly enough, it seems to have done the connector entry correctly so I left it after running the build.sh script. ## (/) Crossed my fingers and then restarted crowd. I tailed the catalina.out file and did not see any stack traces so that is a good sign! ## (/) I visited https://auth.mbari.org:8443/crowd first. It could not find that page, but I suspect that is because I am browsing from the outside, so I tried just https://auth.mbari.org/crowd and got a service unavailable. I am suspecting that this is a combination of firewall and proxy pass and I will send this info to Joe. From what I can see on the crowd side, it seems like the server started cleanly, we just can't get to it. I tried to reach it from a browser on the machine itself too (through VNC) with the same service not available. ## (/) Here are the notes from Joe after he fixed it! Wooohooo! {noformat} Hey Kevin, Thanks for starting clean! I had to make a few adjustments. 1-I modified the server.xml file in /opt/atlassian-crowd-2.8.3/apache-tomcat/conf/server.xml so there are two connectors per the instructions on the Atlassian site. I have backed up this good server.xml file in /etc/temp/ if you want to browse it to see what I did. Of note is that I removed all the jargon referencing the types of ciphers available to simplify things for now. 2-I modified /data/crowd/crowd.properties to have crowd.server.url=https\://localhost\:8443/crowd/services/ application.login.url=https\://localhost\:8443/crowd/console/ But that would cause my login to error with an error saying it was unable to reach the authentication server. I scratched my head for a bit. When I revert the values to just using non-SSL and try to log in, I just get an "invalid login" (I don't know the crowdadm password). So I worked under the assumption that if I can configure SSL to get an "invalid login" when logging in then it would work when provided real credentials. So, I then changed /data/crowd/crowd.proprties to: crowd.server.url=https\://auth.mbari.org\:8443/crowd/services/ application.login.url=https\://auth.mbari.org\:8443/crowd/console/ And now when I try to log in with SSL it says "invalid login". Strange because all the other values I can find only show "localhost" .. in any case... Can you try to log in now? {noformat} ## (/) Next I moved on to configuring the connection to MBARI's LDAP server to enable our logins through Crowd and CrowdID ## (/) I clicked on "Add Directory" in crowd. ## (/) I selected "Connector" then clicked Next ## (/) I put ldap.shore.mbari.org as the name of the server ## (/) I selected "Use memberOf for group memberships" ## (/) I used "OU=AllUsers,DC=shore,DC=mbari,DC=org" for the Base DN ## (/) I used "CN=LDAPbind,OU=Special,OU=AllUsers,DC=shore,DC=mbari,DC=org" for the Username (talk to Pat Allen for password) ## (/) I tested the connection (button click) and it passed. ## (/) I de-selected all the capabilities of the connector as it is a ready only connector and then saved it. It synchronized correctly! ## (/) At first, I could not login using my MBARI credentials, but after going to the "crowd" application in crowd (logged in as the local admin), I had to add the LDAP directory and configure it to "Allow all to authenticate", then I was able to login. After this, the last step was to get this to run as a different user and lock down various directories. ]]> 27558146 27590909 4.4: [https://confluence.atlassian.com/display/JIRA044/Migrating+JIRA+to+Another+Server] ## The JIRA configuration tool: [https://confluence.atlassian.com/display/JIRA044/Using+the+JIRA+Configuration+Tool] h5. Steps # (/) Create new VM named bugs.mbari.org in the DMZ # (/) Have Neil create database Jira_Temp on solstice2.shore.mbari.org # (/) Have Neil create database Jira on solstice2.shore.mbari.org # (/) Have Pat install Java 7 on bugs.shore.mbari.org # (/) Have Pete plumb holes through firewall so processes on bugs.mbari.org can get to Solstice2 # (/) Have Pat create DB_Collaboration account on bugs so it can run JIRA under that account and it can connect to solstice2 using that NT Domain account. # (/) Upgrade license on Atlassian site # (/) Log into bugs.shore.mbari.org # (/) Download 3.13.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 4.4.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 5.2.11 standalone Linux 64 bit tar.gz (not sure this version is necessary, but at least I have it) # (/) Unzip and untar the file to /opt # (/) Download latest JIRA (6.4.7 as of this writing). # (/) Unzip and untar it to /opt # Performed Test Upgrade ## (/) In order to export the current stuff in JIRA, I had to shut off access so people could not change the data while I was backing it up. ## (/) I ssh'd to oceana.mbari.org as root and edited the /opt/jira/conf/server.xml file and commented out the Connector section that had the port of 8010 to shut it off from the normal serving route. ## (/) I uncommented the 8082 port connector and the 8443 port connector so that I could still get to the server. ## (/) I stopped and started the JIRA server and in the log file I got a "keystore was tampered with..." which is not surprising. ## (/) I could then browser over to http://oceana.mbari.org:8082/jira ## (/) Then through the Administration console, I did an XML backup ## (/) I then created a tar of all the attachments in the /data/jira_3_12/attachments directory ## (/) I moved both the XML and tar files to the /root/jira-upgrade directory ## (/) I then reversed the changes to the server.xml file and shut down JIRA ## (/) I left it down during the next steps in case it went so well, I could just point people to the new server (yeah, right). ## (/) I then browsed to the crowd server on oceana and add a new application using: ### URL: http://bugs.mbari.org/jira3135 ### IP: 134.89.2.29 ### Name: JIRA3135 ### Password: (ask Kevin) :) ## (/) On bugs, I made a copy of the JIRA 3.13.5 download in the /opt directory and unzipped and untarred it. ## (/) In order to configure the crowd connection I did the following: ### (/) I scp'd the /opt/crowd/client/crowd-integration-client-1.6.jar file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I removed the existing 1.6.1 crowd client jar from the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I scp'd the /opt/crowd/client/conf/crowd.properties file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I scp'd the /opt/crowd/client/conf/crowd-ehcache.xml file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I edited the crowd.properties file on bugs to look like: {noformat} application.name JIRA3135 application.password (ask Kevin) application.login.url http://oceana.mbari.org:8095/crowd/console/ crowd.server.url http://oceana.mbari.org:8095/crowd/services/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 0 session.lastvalidation session.lastvalidation {noformat} ### (/) I edited the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/osuser.xml file to comment out the current authentication mechanism and then uncomment the crowd one. ## (/) I then edited the /opt/atlassian-jira-standalone-3.13.5/conf/server/xml file and configured the database connection to the Jira_Temp database on Solstice2. I looked like this: {noformat} {noformat} ## (/) Edit the /opt/atlassian/jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/entityengine.xml and changed it from 'hsql' to 'mssql' and delete the line with "PUBLIC" in it per the instructions in the comments in that file. ## (/) I edited the /etc/httpd/conf/httpd.conf file and created a proxy pass at the bottom of the file to point a normal URL to the default port 8080 for JIRA: {noformat} # Proxy Pass for JIRA ProxyPass http://bugs.mbari.org:8080 ProxyPassReverse http://bugs.mbari.org:8080 {noformat} ## (/) I restarted Apache ## (/) I scp'd the jtds driver from oceana to the /opt/atlassian-jira-standalone-3.13.5/common/lib directory (you could down from the internet) ## (/) I then went to the /opt/atlassian-jira-standalone-3.13.5/ directory and ran './bin/startup.sh'. From the log file, I could tell things were hanging. After some troubleshooting I am wondering if the local firewall is preventing the application to get access to the database on solstice2. I can telnet to port 1433, but I can't browse to the base http://bugs.mbari.org from anywhere but the local web browser. I have submitted a ticket. ## (/) I restarted the old JIRA with my hopes dashed :(. ## (/) Pat disabled the firewall on bugs.mbari.org but it still hung trying to connect to solstice2.shore.mbari.org. That is really, really perplexing. Neil mentioned that solstice2 is using Kerberos and solstice is not. Checking with the JTDS docs, version 1.3.1 of the driver added kerberos support, so I downloaded that driver and added the 'userKerberos=true' property to the URL in the server.xml file and restarted. Got an error about no credentials, so added user and password properties to the URL. Nope, no luck. Never did figure this one out, but I had Pat pull the VM inside the firewall and after some thrash it worked. Well, it sort of worked ... sigh. It turns out I had downloaded the standard version instead of the enterprise version. I need to redo this work ... grrr. ## (/) I deleted all the tables in the Jira_Temp database and removed the /data/jira3135/indexes directory (and recreated). ## (/) I downloaded the enterprise version of the 3.13.5 server. I made a copy in the /opt directory and unzipped and untarred the file. ## (/) I went back to crowd and edited the application to change the properties to: ### URL: http://bugs.shore.mbari.org:8080 ### IP: 134.89.12.31 ### Name: jira3135 ### Password: (ask Kevin) :) ## (/) I then repeated the steps above to get the server up and running with the following differences: ### The server name is now bugs.shore.mbari.org ### The paths given above are a little different in that they no longer say "standard" but say "enterprise" ### I deleted the proxy pass as it seemed to have issues before and this is only temporary anyway. ## (/) I then browsed to http://bugs.shore.mbari.org:8080 ## (/) It took me to the start up page and at the top was the option to 'import your existing data'. Seemed too good not to try. I clicked on the link. It asked me for the backup file location and the location where the indexes would be stored. ## (/) I copied the XML zip file and the attachments tar file to the /data/original directory. ## (/) I created the /data/jira3135/indexes and used those directories ... it fired off the import and I waited. ## (/) I tailed the log file to watch the import. Holy crap, it worked!!! I could log in and everything! I copied the results from the log file here for posterity sake: {noformat} 2015-07-22 20:55:45,156 http-8080-Processor22 INFO [jira.action.admin.DataImport] Running data import 2015-07-22 20:55:45,179 http-8080-Processor22 INFO [jira.action.admin.DataImport] Importing data.. 2015-07-22 20:55:45,186 http-8080-Processor22 INFO [jira.action.admin.DataImport] Start parsing XML with SAX Parser 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] XML successfully parsed 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] Removing all entries from the database. 2015-07-22 20:56:24,593 http-8080-Processor22 INFO [jira.action.admin.DataImport] All entries removed. 2015-07-22 20:56:24,594 http-8080-Processor22 INFO [jira.action.admin.DataImport] Started storing 410414 Generic Values 2015-07-22 21:01:51,967 http-8080-Processor22 INFO [jira.action.admin.DataImport] Finished storing Generic Values 2015-07-22 21:01:52,329 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:52,361 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:54,683 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLink' to module 'jira.user.format:profile-link-user-format'. 2015-07-22 21:01:54,724 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullName' to module 'jira.user.format:full-name-user-format'. 2015-07-22 21:01:54,773 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkSearcher' to module 'jira.user.format:profile-link-searcher-user-format'. 2015-07-22 21:01:54,784 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkExternal' to module 'jira.user.format:profile-link-external-user-format'. 2015-07-22 21:01:54,795 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkActionHeader' to module 'jira.user.format:profile-link-action-header-user-format'. 2015-07-22 21:01:54,807 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullProfile' to module 'jira.user.format:full-profile-user-format'. 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/comments 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/issues 2015-07-22 21:01:55,641 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/plugins 2015-07-22 21:01:55,867 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:01:55,871 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/issues does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:55,873 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/comments does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,033 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,257 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,889 http-8080-Processor22 ERROR [atlassian.jira.upgrade.ConsistencyCheckImpl] Attachments are turned on, but attachment path [/data/jira_3_12/attachments] invalid - disabling attachments 2015-07-22 21:02:13,904 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Detected that an upgrade is needed; existing data at build 299 2015-07-22 21:02:13,907 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Doing Upgrade... 2015-07-22 21:02:13,915 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value' succeeded 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 317 2015-07-22 21:02:13,944 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite filters - make each filter a favourite of its owner. 2015-07-22 21:02:17,822 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build319] Could not find author 'fpy' for filter with id '10040' 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite filters - make each filter a favourite of its owner.' succeeded 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 319 2015-07-22 21:02:17,995 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise Share Permissions. Move old shares to new shares. 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise Share Permissions. Move old shares to new shares.' succeeded 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 321 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Migrating the old JIRA UI colors to the new JIRA 3.13 colors 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build322] Custom color detected for jira.lf.menu.bgcolour : #336699 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Migrating the old JIRA UI colors to the new JIRA 3.13 colors' succeeded 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 322 2015-07-22 21:02:18,025 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite dashboards - make each dashboard a favourite of its owner. 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'cmcgann' for dashboard with id '10030' 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'fpy' for dashboard with id '10060' 2015-07-22 21:02:18,423 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'kanna' for dashboard with id '10040' 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite dashboards - make each dashboard a favourite of its owner.' succeeded 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 325 2015-07-22 21:02:18,625 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Reindexing all data in JIRA to include Favourites. 2015-07-22 21:02:18,648 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All starting... 2015-07-22 21:02:18,650 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 0% complete. Current index: Issue 2015-07-22 21:02:18,654 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:02:18,809 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 1% complete. Current index: Issue 2015-07-22 21:02:18,855 indexerPool-2-thread-10 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 2% complete. Current index: Issue 2015-07-22 21:02:18,899 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 3% complete. Current index: Issue 2015-07-22 21:02:18,945 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 4% complete. Current index: Issue 2015-07-22 21:02:19,012 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 5% complete. Current index: Issue . . . 2015-07-22 21:02:26,164 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 95% complete. Current index: Issue 2015-07-22 21:02:26,232 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 96% complete. Current index: Issue 2015-07-22 21:02:26,316 indexerPool-2-thread-9 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 97% complete. Current index: Issue 2015-07-22 21:02:26,771 indexerPool-2-thread-3 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: Issue 2015-07-22 21:02:27,261 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 8607ms. Indexer: DefaultIndexManager: paths: [/data/jira3135/indexes/issues, /data/jira3135/indexes/comments] 2015-07-22 21:02:27,263 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: SearchRequest 2015-07-22 21:02:27,268 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,293 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: SearchRequest 2015-07-22 21:02:27,308 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: PortalPage 2015-07-22 21:02:27,312 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,377 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: PortalPage 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 115ms. Indexer: SharedEntityIndexManager: paths: [/data/jira3135/indexes/entities/portalpage, /data/jira3135/indexes/entities/searchrequest] 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All complete. Total time: 8722ms. 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Reindexing all data in JIRA to include Favourites.' succeeded 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 326 2015-07-22 21:02:27,397 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade succeeded! Setting data build number to 360 2015-07-22 21:02:27,469 JiraQuartzScheduler_Worker-0 WARN [service.services.export.ExportService] Backup directory /data/jira_3_12/backup does not exist {noformat} {warning:title=Paths} It appears that the upgraded JIRA will still look for the attachments and the backup locations in the original places. So I created /data/jira_3_12/backup and untarred the original attachments to /data/jira_3_12 and then everything worked (including attachements) in the new JIRA. {warning} ## (/) I then used the upgraded JIRA to generate a new XML backup and stored it in /data/original/3.13.5 along with another tar of the files in /data/jira_3_12/attachments. ## (/) I then shutdown the JIRA server. *I should be ready to move on to version 4 upgrade WHEW* ## So, before moving on, I decided that it would be a really good idea to spin up a new Crowd instance to get rid of the :8443 in the URL and to move off of RedHat per IS requests. I have a ticket in for a new VM and a new database to try to get this going. I am waiting on that before moving on. ## (/) Pat created the VM and Neil created the database. ## (/) I logged into auth.mbari.org (name of the VM) and downloaded crowd which I unzipped to the /opt directory ## (/) I then created a /data/crowd directory and gave my account permissions on it and then edited the /opt/atlassian..../crowd-webapp/WEB-INF/classes/crowd-init.properties file to set that as the crowd home directory. ## (/) The instructions say to download the JDBC driver, but they already have JTDS 1.2.7 in the download so I did not do anything. ## (/) You have to manually connect up CrowdID to a database as they setup wizard does not currently do this. ### (/) They say to download the driver, but again 1.2.7 was there so I did nothing. ### (/) I edited the /opt/atlassian.../apache-tomcat/conf/Catalina/localhost/openidserver.xml to look like: {noformat} {noformat} ### (/) I edited the /opt/atlassian.../build.properties files to look like: {noformat} # Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See https://confluence.atlassian.com/display/CROWD/Connecting+Crowd+to+a+Database hibernate.dialect=org.hibernate.dialect.SQLServerDialect # The Hibernate transaction factory to use. See https://confluence.atlassian.com/display/CROWD/Configuring+Crowd hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory # The http port you wish to run crowd from, ie: http://localhost:8095/crowd crowd.tomcat.connector.port=8095 # Tomcat requires a unique port for shutdown crowd.tomcat.shutdown.port=8020 # Crowd context root crowd.url=http://localhost:8095/crowd # Demo context root demo.url=http://localhost:8095/demo # OpenID server context root openidserver.url=http://localhost:8095/openidserver {noformat} ### (/) I then ran the build.sh script in the root of /opt/atlassian... ## (/) I fired up crowd using the /opt/atlassian.../start_crowd.sh script ## (/) I then went to http://auth.mbari.org:8095/crowd to kick off the start up wizard ## (/) I grabbed a new eval license from my account on atlassian and pasted into the license page. ## (/) I selected "New install" on the next page. ## (/) I configured the JDBC connection using this connection URL with user DB_Collaboration {noformat} jdbc:jtds:sqlserver://dione.mbari.org:51001/Crowd;domain=SHORE;useNTLMv2=TRUE {noformat} ## (/) I left the "Options" as they came up {warning:title=Paths} Not sure if this is a problem, but because I started the set up using auth.mbari.org, it set the Base URL to http://auth.mbari.org:8095/crowd instead of localhost. Hope that is not a problem. We will see. {warning} ## (/) I configured the email connection using the settings from [here|https://wind.shore.mbari.org/is/howto/email/mbarimail/imap] and I used my network login (probably shouldn't be doing that ... not sure where it stores my password, but I am assuming in the DB). ## (/) For the local admin account, I created a user named 'crowdadm' so it would not clash with my LDAP account. See Kevin Gomes for password information. ## (/) I checked the OpenID server as an integrated application ## (/) It then took me to the login page and I logged in using the newly minted admin account. Seemed all is well so far. ## (/) I visited the openidserver URL as well and that seemed OK. ## (/) I decided to wait on configuring the MBARI LDAP directory until I got everything with SSL working. ## (/) Now the next step was to follow the directions to configure Crowd to run over SSL found [here|https://confluence.atlassian.com/display/CROWD/Configuring+Crowd+to+Work+with+SSL] ## (/) I shutdown crowd. Note that the stop script does not shutdown things correctly and I noticed the crowd app running as root. That should not be if I started as kgomes. Not sure what is up with that. ## (/) Now Joe had already configured SSL once, so I used his connector configuration in the server.xml file and so the final file looked like: {noformat} {noformat} ## (/) I then edited the /data/crowd/crowd.properties to look like: {noformat} #Sat Aug 01 09:05:15 PDT 2015 session.lastvalidation=session.lastvalidation session.tokenkey=session.tokenkey crowd.server.url=https\://localhost\:8443/crowd/services/ application.name=crowd http.timeout=30000 session.isauthenticated=session.isauthenticated application.login.url=https\://localhost\:8443/crowd/console/ session.validationinterval=0 application.password=Y1Xp3OorCmsOP4eruL1dmH {noformat} One thing to note here is that based on a comment from the SSL configuration page at atlassian (Steve's comment), you are supposed to leave all the host names the same. For example, if the file says localhost, leave it localhost. So this created a bit of a problem based on the fact that I had left the base URL pointing to auth.mbari.org in the wizard steps above. That step wrote auth.mbari.org to the /data/crowd/crowd.properties. All the other files reference localhost, so to be consistent, I changed auth.mbari.org to localhost in the /data/crowd/crowd.properties file. We will see if this works. ## (/) Per the instructions on the atlassian page (referenced above), I also edited the build.properties file and the /client/conf/crowd.properties files before I restarted and used the SSL URLs ## build.properties: {noformat} # Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See https://confluence.atlassian.com/display/CROWD/Connecting+Crowd+to+a+Database hibernate.dialect=org.hibernate.dialect.SQLServerDialect # The Hibernate transaction factory to use. See https://confluence.atlassian.com/display/CROWD/Configuring+Crowd hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory # The http port you wish to run crowd from, ie: http://localhost:8095/crowd crowd.tomcat.connector.port=8095 # Tomcat requires a unique port for shutdown crowd.tomcat.shutdown.port=8020 # Crowd context root crowd.url=https://localhost:8443/crowd # Demo context root demo.url=https://localhost:8443/demo # OpenID server context root openidserver.url=https://localhost:8443/openidserver {noformat} ## crowd.properties (client) {noformat} application.name crowd application.password password application.login.url https://localhost:8443/crowd/console/ crowd.server.url https://localhost:8443/crowd/services/ crowd.base.url https://localhost:8443/crowd/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 2 session.lastvalidation session.lastvalidation {noformat} ## (/) Although not stated, I am assuming you would need to run the build.sh script to push the build.properties changes to their proper places, so I did that. Note that before doing that, I know that it will clobber the server.xml changes I made, so I made a copy of that file and diff'd them after and then rolled the previous changes to the new server.xml file. Actually, amazingly enough, it seems to have done the connector entry correctly so I left it after running the build.sh script. ## (/) Crossed my fingers and then restarted crowd. I tailed the catalina.out file and did not see any stack traces so that is a good sign! ## (/) I visited https://auth.mbari.org:8443/crowd first. It could not find that page, but I suspect that is because I am browsing from the outside, so I tried just https://auth.mbari.org/crowd and got a service unavailable. I am suspecting that this is a combination of firewall and proxy pass and I will send this info to Joe. From what I can see on the crowd side, it seems like the server started cleanly, we just can't get to it. I tried to reach it from a browser on the machine itself too (through VNC) with the same service not available. ## (/) Here are the notes from Joe after he fixed it! Wooohooo! {noformat} Hey Kevin, Thanks for starting clean! I had to make a few adjustments. 1-I modified the server.xml file in /opt/atlassian-crowd-2.8.3/apache-tomcat/conf/server.xml so there are two connectors per the instructions on the Atlassian site. I have backed up this good server.xml file in /etc/temp/ if you want to browse it to see what I did. Of note is that I removed all the jargon referencing the types of ciphers available to simplify things for now. 2-I modified /data/crowd/crowd.properties to have crowd.server.url=https\://localhost\:8443/crowd/services/ application.login.url=https\://localhost\:8443/crowd/console/ But that would cause my login to error with an error saying it was unable to reach the authentication server. I scratched my head for a bit. When I revert the values to just using non-SSL and try to log in, I just get an "invalid login" (I don't know the crowdadm password). So I worked under the assumption that if I can configure SSL to get an "invalid login" when logging in then it would work when provided real credentials. So, I then changed /data/crowd/crowd.proprties to: crowd.server.url=https\://auth.mbari.org\:8443/crowd/services/ application.login.url=https\://auth.mbari.org\:8443/crowd/console/ And now when I try to log in with SSL it says "invalid login". Strange because all the other values I can find only show "localhost" .. in any case... Can you try to log in now? {noformat} ## (/) Next I moved on to configuring the connection to MBARI's LDAP server to enable our logins through Crowd and CrowdID ## (/) I clicked on "Add Directory" in crowd. ## (/) I selected "Connector" then clicked Next ## (/) I put ldap.shore.mbari.org as the name of the server ## (/) I selected "Use memberOf for group memberships" ## (/) I used "OU=AllUsers,DC=shore,DC=mbari,DC=org" for the Base DN ## (/) I used "CN=LDAPbind,OU=Special,OU=AllUsers,DC=shore,DC=mbari,DC=org" for the Username (talk to Pat Allen for password) ## (/) I tested the connection (button click) and it passed. ## (/) I de-selected all the capabilities of the connector as it is a ready only connector and then saved it. It synchronized correctly! ## (/) At first, I could not login using my MBARI credentials, but after going to the "crowd" application in crowd (logged in as the local admin), I had to add the LDAP directory and configure it to "Allow all to authenticate", then I was able to login.]]> 27558144 27590907 4.4: [https://confluence.atlassian.com/display/JIRA044/Migrating+JIRA+to+Another+Server] ## The JIRA configuration tool: [https://confluence.atlassian.com/display/JIRA044/Using+the+JIRA+Configuration+Tool] h5. Steps # (/) Create new VM named bugs.mbari.org in the DMZ # (/) Have Neil create database Jira_Temp on solstice2.shore.mbari.org # (/) Have Neil create database Jira on solstice2.shore.mbari.org # (/) Have Pat install Java 7 on bugs.shore.mbari.org # (/) Have Pete plumb holes through firewall so processes on bugs.mbari.org can get to Solstice2 # (/) Have Pat create DB_Collaboration account on bugs so it can run JIRA under that account and it can connect to solstice2 using that NT Domain account. # (/) Upgrade license on Atlassian site # (/) Log into bugs.shore.mbari.org # (/) Download 3.13.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 4.4.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 5.2.11 standalone Linux 64 bit tar.gz (not sure this version is necessary, but at least I have it) # (/) Unzip and untar the file to /opt # (/) Download latest JIRA (6.4.7 as of this writing). # (/) Unzip and untar it to /opt # Performed Test Upgrade ## (/) In order to export the current stuff in JIRA, I had to shut off access so people could not change the data while I was backing it up. ## (/) I ssh'd to oceana.mbari.org as root and edited the /opt/jira/conf/server.xml file and commented out the Connector section that had the port of 8010 to shut it off from the normal serving route. ## (/) I uncommented the 8082 port connector and the 8443 port connector so that I could still get to the server. ## (/) I stopped and started the JIRA server and in the log file I got a "keystore was tampered with..." which is not surprising. ## (/) I could then browser over to http://oceana.mbari.org:8082/jira ## (/) Then through the Administration console, I did an XML backup ## (/) I then created a tar of all the attachments in the /data/jira_3_12/attachments directory ## (/) I moved both the XML and tar files to the /root/jira-upgrade directory ## (/) I then reversed the changes to the server.xml file and shut down JIRA ## (/) I left it down during the next steps in case it went so well, I could just point people to the new server (yeah, right). ## (/) I then browsed to the crowd server on oceana and add a new application using: ### URL: http://bugs.mbari.org/jira3135 ### IP: 134.89.2.29 ### Name: JIRA3135 ### Password: (ask Kevin) :) ## (/) On bugs, I made a copy of the JIRA 3.13.5 download in the /opt directory and unzipped and untarred it. ## (/) In order to configure the crowd connection I did the following: ### (/) I scp'd the /opt/crowd/client/crowd-integration-client-1.6.jar file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I removed the existing 1.6.1 crowd client jar from the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I scp'd the /opt/crowd/client/conf/crowd.properties file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I scp'd the /opt/crowd/client/conf/crowd-ehcache.xml file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I edited the crowd.properties file on bugs to look like: {noformat} application.name JIRA3135 application.password (ask Kevin) application.login.url http://oceana.mbari.org:8095/crowd/console/ crowd.server.url http://oceana.mbari.org:8095/crowd/services/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 0 session.lastvalidation session.lastvalidation {noformat} ### (/) I edited the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/osuser.xml file to comment out the current authentication mechanism and then uncomment the crowd one. ## (/) I then edited the /opt/atlassian-jira-standalone-3.13.5/conf/server/xml file and configured the database connection to the Jira_Temp database on Solstice2. I looked like this: {noformat} {noformat} ## (/) Edit the /opt/atlassian/jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/entityengine.xml and changed it from 'hsql' to 'mssql' and delete the line with "PUBLIC" in it per the instructions in the comments in that file. ## (/) I edited the /etc/httpd/conf/httpd.conf file and created a proxy pass at the bottom of the file to point a normal URL to the default port 8080 for JIRA: {noformat} # Proxy Pass for JIRA ProxyPass http://bugs.mbari.org:8080 ProxyPassReverse http://bugs.mbari.org:8080 {noformat} ## (/) I restarted Apache ## (/) I scp'd the jtds driver from oceana to the /opt/atlassian-jira-standalone-3.13.5/common/lib directory (you could down from the internet) ## (/) I then went to the /opt/atlassian-jira-standalone-3.13.5/ directory and ran './bin/startup.sh'. From the log file, I could tell things were hanging. After some troubleshooting I am wondering if the local firewall is preventing the application to get access to the database on solstice2. I can telnet to port 1433, but I can't browse to the base http://bugs.mbari.org from anywhere but the local web browser. I have submitted a ticket. ## (/) I restarted the old JIRA with my hopes dashed :(. ## (/) Pat disabled the firewall on bugs.mbari.org but it still hung trying to connect to solstice2.shore.mbari.org. That is really, really perplexing. Neil mentioned that solstice2 is using Kerberos and solstice is not. Checking with the JTDS docs, version 1.3.1 of the driver added kerberos support, so I downloaded that driver and added the 'userKerberos=true' property to the URL in the server.xml file and restarted. Got an error about no credentials, so added user and password properties to the URL. Nope, no luck. Never did figure this one out, but I had Pat pull the VM inside the firewall and after some thrash it worked. Well, it sort of worked ... sigh. It turns out I had downloaded the standard version instead of the enterprise version. I need to redo this work ... grrr. ## (/) I deleted all the tables in the Jira_Temp database and removed the /data/jira3135/indexes directory (and recreated). ## (/) I downloaded the enterprise version of the 3.13.5 server. I made a copy in the /opt directory and unzipped and untarred the file. ## (/) I went back to crowd and edited the application to change the properties to: ### URL: http://bugs.shore.mbari.org:8080 ### IP: 134.89.12.31 ### Name: jira3135 ### Password: (ask Kevin) :) ## (/) I then repeated the steps above to get the server up and running with the following differences: ### The server name is now bugs.shore.mbari.org ### The paths given above are a little different in that they no longer say "standard" but say "enterprise" ### I deleted the proxy pass as it seemed to have issues before and this is only temporary anyway. ## (/) I then browsed to http://bugs.shore.mbari.org:8080 ## (/) It took me to the start up page and at the top was the option to 'import your existing data'. Seemed too good not to try. I clicked on the link. It asked me for the backup file location and the location where the indexes would be stored. ## (/) I copied the XML zip file and the attachments tar file to the /data/original directory. ## (/) I created the /data/jira3135/indexes and used those directories ... it fired off the import and I waited. ## (/) I tailed the log file to watch the import. Holy crap, it worked!!! I could log in and everything! I copied the results from the log file here for posterity sake: {noformat} 2015-07-22 20:55:45,156 http-8080-Processor22 INFO [jira.action.admin.DataImport] Running data import 2015-07-22 20:55:45,179 http-8080-Processor22 INFO [jira.action.admin.DataImport] Importing data.. 2015-07-22 20:55:45,186 http-8080-Processor22 INFO [jira.action.admin.DataImport] Start parsing XML with SAX Parser 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] XML successfully parsed 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] Removing all entries from the database. 2015-07-22 20:56:24,593 http-8080-Processor22 INFO [jira.action.admin.DataImport] All entries removed. 2015-07-22 20:56:24,594 http-8080-Processor22 INFO [jira.action.admin.DataImport] Started storing 410414 Generic Values 2015-07-22 21:01:51,967 http-8080-Processor22 INFO [jira.action.admin.DataImport] Finished storing Generic Values 2015-07-22 21:01:52,329 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:52,361 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:54,683 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLink' to module 'jira.user.format:profile-link-user-format'. 2015-07-22 21:01:54,724 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullName' to module 'jira.user.format:full-name-user-format'. 2015-07-22 21:01:54,773 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkSearcher' to module 'jira.user.format:profile-link-searcher-user-format'. 2015-07-22 21:01:54,784 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkExternal' to module 'jira.user.format:profile-link-external-user-format'. 2015-07-22 21:01:54,795 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkActionHeader' to module 'jira.user.format:profile-link-action-header-user-format'. 2015-07-22 21:01:54,807 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullProfile' to module 'jira.user.format:full-profile-user-format'. 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/comments 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/issues 2015-07-22 21:01:55,641 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/plugins 2015-07-22 21:01:55,867 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:01:55,871 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/issues does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:55,873 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/comments does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,033 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,257 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,889 http-8080-Processor22 ERROR [atlassian.jira.upgrade.ConsistencyCheckImpl] Attachments are turned on, but attachment path [/data/jira_3_12/attachments] invalid - disabling attachments 2015-07-22 21:02:13,904 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Detected that an upgrade is needed; existing data at build 299 2015-07-22 21:02:13,907 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Doing Upgrade... 2015-07-22 21:02:13,915 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value' succeeded 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 317 2015-07-22 21:02:13,944 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite filters - make each filter a favourite of its owner. 2015-07-22 21:02:17,822 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build319] Could not find author 'fpy' for filter with id '10040' 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite filters - make each filter a favourite of its owner.' succeeded 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 319 2015-07-22 21:02:17,995 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise Share Permissions. Move old shares to new shares. 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise Share Permissions. Move old shares to new shares.' succeeded 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 321 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Migrating the old JIRA UI colors to the new JIRA 3.13 colors 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build322] Custom color detected for jira.lf.menu.bgcolour : #336699 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Migrating the old JIRA UI colors to the new JIRA 3.13 colors' succeeded 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 322 2015-07-22 21:02:18,025 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite dashboards - make each dashboard a favourite of its owner. 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'cmcgann' for dashboard with id '10030' 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'fpy' for dashboard with id '10060' 2015-07-22 21:02:18,423 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'kanna' for dashboard with id '10040' 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite dashboards - make each dashboard a favourite of its owner.' succeeded 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 325 2015-07-22 21:02:18,625 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Reindexing all data in JIRA to include Favourites. 2015-07-22 21:02:18,648 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All starting... 2015-07-22 21:02:18,650 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 0% complete. Current index: Issue 2015-07-22 21:02:18,654 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:02:18,809 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 1% complete. Current index: Issue 2015-07-22 21:02:18,855 indexerPool-2-thread-10 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 2% complete. Current index: Issue 2015-07-22 21:02:18,899 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 3% complete. Current index: Issue 2015-07-22 21:02:18,945 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 4% complete. Current index: Issue 2015-07-22 21:02:19,012 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 5% complete. Current index: Issue . . . 2015-07-22 21:02:26,164 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 95% complete. Current index: Issue 2015-07-22 21:02:26,232 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 96% complete. Current index: Issue 2015-07-22 21:02:26,316 indexerPool-2-thread-9 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 97% complete. Current index: Issue 2015-07-22 21:02:26,771 indexerPool-2-thread-3 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: Issue 2015-07-22 21:02:27,261 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 8607ms. Indexer: DefaultIndexManager: paths: [/data/jira3135/indexes/issues, /data/jira3135/indexes/comments] 2015-07-22 21:02:27,263 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: SearchRequest 2015-07-22 21:02:27,268 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,293 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: SearchRequest 2015-07-22 21:02:27,308 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: PortalPage 2015-07-22 21:02:27,312 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,377 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: PortalPage 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 115ms. Indexer: SharedEntityIndexManager: paths: [/data/jira3135/indexes/entities/portalpage, /data/jira3135/indexes/entities/searchrequest] 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All complete. Total time: 8722ms. 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Reindexing all data in JIRA to include Favourites.' succeeded 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 326 2015-07-22 21:02:27,397 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade succeeded! Setting data build number to 360 2015-07-22 21:02:27,469 JiraQuartzScheduler_Worker-0 WARN [service.services.export.ExportService] Backup directory /data/jira_3_12/backup does not exist {noformat} {warning:title=Paths} It appears that the upgraded JIRA will still look for the attachments and the backup locations in the original places. So I created /data/jira_3_12/backup and untarred the original attachments to /data/jira_3_12 and then everything worked (including attachements) in the new JIRA. {warning} ## (/) I then used the upgraded JIRA to generate a new XML backup and stored it in /data/original/3.13.5 along with another tar of the files in /data/jira_3_12/attachments. ## (/) I then shutdown the JIRA server. *I should be ready to move on to version 4 upgrade WHEW* ## So, before moving on, I decided that it would be a really good idea to spin up a new Crowd instance to get rid of the :8443 in the URL and to move off of RedHat per IS requests. I have a ticket in for a new VM and a new database to try to get this going. I am waiting on that before moving on. ## (/) Pat created the VM and Neil created the database. ## (/) I logged into auth.mbari.org (name of the VM) and downloaded crowd which I unzipped to the /opt directory ## (/) I then created a /data/crowd directory and gave my account permissions on it and then edited the /opt/atlassian..../crowd-webapp/WEB-INF/classes/crowd-init.properties file to set that as the crowd home directory. ## (/) The instructions say to download the JDBC driver, but they already have JTDS 1.2.7 in the download so I did not do anything. ## (/) You have to manually connect up CrowdID to a database as they setup wizard does not currently do this. ### (/) They say to download the driver, but again 1.2.7 was there so I did nothing. ### (/) I edited the /opt/atlassian.../apache-tomcat/conf/Catalina/localhost/openidserver.xml to look like: {noformat} {noformat} ### (/) I edited the /opt/atlassian.../build.properties files to look like: {noformat} # Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See https://confluence.atlassian.com/display/CROWD/Connecting+Crowd+to+a+Database hibernate.dialect=org.hibernate.dialect.SQLServerDialect # The Hibernate transaction factory to use. See https://confluence.atlassian.com/display/CROWD/Configuring+Crowd hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory # The http port you wish to run crowd from, ie: http://localhost:8095/crowd crowd.tomcat.connector.port=8095 # Tomcat requires a unique port for shutdown crowd.tomcat.shutdown.port=8020 # Crowd context root crowd.url=http://localhost:8095/crowd # Demo context root demo.url=http://localhost:8095/demo # OpenID server context root openidserver.url=http://localhost:8095/openidserver {noformat} ### (/) I then ran the build.sh script in the root of /opt/atlassian... ## (/) I fired up crowd using the /opt/atlassian.../start_crowd.sh script ## (/) I then went to http://auth.mbari.org:8095/crowd to kick off the start up wizard ## (/) I grabbed a new eval license from my account on atlassian and pasted into the license page. ## (/) I selected "New install" on the next page. ## (/) I configured the JDBC connection using this connection URL with user DB_Collaboration {noformat} jdbc:jtds:sqlserver://dione.mbari.org:51001/Crowd;domain=SHORE;useNTLMv2=TRUE {noformat} ## (/) I left the "Options" as they came up {warning:title=Paths} Not sure if this is a problem, but because I started the set up using auth.mbari.org, it set the Base URL to http://auth.mbari.org:8095/crowd instead of localhost. Hope that is not a problem. We will see. {warning} ## (/) I configured the email connection using the settings from [here|https://wind.shore.mbari.org/is/howto/email/mbarimail/imap] and I used my network login (probably shouldn't be doing that ... not sure where it stores my password, but I am assuming in the DB). ## (/) For the local admin account, I created a user named 'crowdadm' so it would not clash with my LDAP account. See Kevin Gomes for password information. ## (/) I checked the OpenID server as an integrated application ## (/) It then took me to the login page and I logged in using the newly minted admin account. Seemed all is well so far. ## (/) I visited the openidserver URL as well and that seemed OK. ## (/) I decided to wait on configuring the MBARI LDAP directory until I got everything with SSL working. ## (/) Now the next step was to follow the directions to configure Crowd to run over SSL found [here|https://confluence.atlassian.com/display/CROWD/Configuring+Crowd+to+Work+with+SSL] ## (/) I shutdown crowd. Note that the stop script does not shutdown things correctly and I noticed the crowd app running as root. That should not be if I started as kgomes. Not sure what is up with that. ## (/) Now Joe had already configured SSL once, so I used his connector configuration in the server.xml file and so the final file looked like: {noformat} {noformat} ## (/) I then edited the /data/crowd/crowd.properties to look like: {noformat} #Sat Aug 01 09:05:15 PDT 2015 session.lastvalidation=session.lastvalidation session.tokenkey=session.tokenkey crowd.server.url=https\://localhost\:8443/crowd/services/ application.name=crowd http.timeout=30000 session.isauthenticated=session.isauthenticated application.login.url=https\://localhost\:8443/crowd/console/ session.validationinterval=0 application.password=Y1Xp3OorCmsOP4eruL1dmH {noformat} One thing to note here is that based on a comment from the SSL configuration page at atlassian (Steve's comment), you are supposed to leave all the host names the same. For example, if the file says localhost, leave it localhost. So this created a bit of a problem based on the fact that I had left the base URL pointing to auth.mbari.org in the wizard steps above. That step wrote auth.mbari.org to the /data/crowd/crowd.properties. All the other files reference localhost, so to be consistent, I changed auth.mbari.org to localhost in the /data/crowd/crowd.properties file. We will see if this works. ## (/) Per the instructions on the atlassian page (referenced above), I also edited the build.properties file and the /client/conf/crowd.properties files before I restarted and used the SSL URLs ## build.properties: {noformat} # Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See https://confluence.atlassian.com/display/CROWD/Connecting+Crowd+to+a+Database hibernate.dialect=org.hibernate.dialect.SQLServerDialect # The Hibernate transaction factory to use. See https://confluence.atlassian.com/display/CROWD/Configuring+Crowd hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory # The http port you wish to run crowd from, ie: http://localhost:8095/crowd crowd.tomcat.connector.port=8095 # Tomcat requires a unique port for shutdown crowd.tomcat.shutdown.port=8020 # Crowd context root crowd.url=https://localhost:8443/crowd # Demo context root demo.url=https://localhost:8443/demo # OpenID server context root openidserver.url=https://localhost:8443/openidserver {noformat} ## crowd.properties (client) {noformat} application.name crowd application.password password application.login.url https://localhost:8443/crowd/console/ crowd.server.url https://localhost:8443/crowd/services/ crowd.base.url https://localhost:8443/crowd/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 2 session.lastvalidation session.lastvalidation {noformat} ## (/) Although not stated, I am assuming you would need to run the build.sh script to push the build.properties changes to their proper places, so I did that. Note that before doing that, I know that it will clobber the server.xml changes I made, so I made a copy of that file and diff'd them after and then rolled the previous changes to the new server.xml file. Actually, amazingly enough, it seems to have done the connector entry correctly so I left it after running the build.sh script. ## (/) Crossed my fingers and then restarted crowd. I tailed the catalina.out file and did not see any stack traces so that is a good sign! ## (/) I visited https://auth.mbari.org:8443/crowd first. It could not find that page, but I suspect that is because I am browsing from the outside, so I tried just https://auth.mbari.org/crowd and got a service unavailable. I am suspecting that this is a combination of firewall and proxy pass and I will send this info to Joe. From what I can see on the crowd side, it seems like the server started cleanly, we just can't get to it. I tried to reach it from a browser on the machine itself too (through VNC) with the same service not available. ## (/) Here are the notes from Joe after he fixed it! Wooohooo! {noformat} Hey Kevin, Thanks for starting clean! I had to make a few adjustments. 1-I modified the server.xml file in /opt/atlassian-crowd-2.8.3/apache-tomcat/conf/server.xml so there are two connectors per the instructions on the Atlassian site. I have backed up this good server.xml file in /etc/temp/ if you want to browse it to see what I did. Of note is that I removed all the jargon referencing the types of ciphers available to simplify things for now. 2-I modified /data/crowd/crowd.properties to have crowd.server.url=https\://localhost\:8443/crowd/services/ application.login.url=https\://localhost\:8443/crowd/console/ But that would cause my login to error with an error saying it was unable to reach the authentication server. I scratched my head for a bit. When I revert the values to just using non-SSL and try to log in, I just get an "invalid login" (I don't know the crowdadm password). So I worked under the assumption that if I can configure SSL to get an "invalid login" when logging in then it would work when provided real credentials. So, I then changed /data/crowd/crowd.proprties to: crowd.server.url=https\://auth.mbari.org\:8443/crowd/services/ application.login.url=https\://auth.mbari.org\:8443/crowd/console/ And now when I try to log in with SSL it says "invalid login". Strange because all the other values I can find only show "localhost" .. in any case... Can you try to log in now? {noformat} ## (/) Next I moved on to configuring the connection to MBARI's LDAP server to enable our logins through Crowd and CrowdID ## (/) I clicked on "Add Directory" in crowd. ## (/) I selected "Connector" then clicked Next ## (/) I put ldap.shore.mbari.org as the name of the server ## (/) I selected "Use memberOf for group memberships" ## (/) I used "OU=AllUsers,DC=shore,DC=mbari,DC=org" for the Base DN ## (/) I used "CN=LDAPbind,OU=Special,OU=AllUsers,DC=shore,DC=mbari,DC=org" for the Username (talk to Pat Allen for password) ## (/) I tested the connection (button click) and it passed. ## (/) I de-selected all the capabilities of the connector as it is a ready only connector and then saved it. It synchronized correctly! ]]> 27558142 27590905 4.4: [https://confluence.atlassian.com/display/JIRA044/Migrating+JIRA+to+Another+Server] ## The JIRA configuration tool: [https://confluence.atlassian.com/display/JIRA044/Using+the+JIRA+Configuration+Tool] h5. Steps # (/) Create new VM named bugs.mbari.org in the DMZ # (/) Have Neil create database Jira_Temp on solstice2.shore.mbari.org # (/) Have Neil create database Jira on solstice2.shore.mbari.org # (/) Have Pat install Java 7 on bugs.shore.mbari.org # (/) Have Pete plumb holes through firewall so processes on bugs.mbari.org can get to Solstice2 # (/) Have Pat create DB_Collaboration account on bugs so it can run JIRA under that account and it can connect to solstice2 using that NT Domain account. # (/) Upgrade license on Atlassian site # (/) Log into bugs.shore.mbari.org # (/) Download 3.13.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 4.4.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 5.2.11 standalone Linux 64 bit tar.gz (not sure this version is necessary, but at least I have it) # (/) Unzip and untar the file to /opt # (/) Download latest JIRA (6.4.7 as of this writing). # (/) Unzip and untar it to /opt # Performed Test Upgrade ## (/) In order to export the current stuff in JIRA, I had to shut off access so people could not change the data while I was backing it up. ## (/) I ssh'd to oceana.mbari.org as root and edited the /opt/jira/conf/server.xml file and commented out the Connector section that had the port of 8010 to shut it off from the normal serving route. ## (/) I uncommented the 8082 port connector and the 8443 port connector so that I could still get to the server. ## (/) I stopped and started the JIRA server and in the log file I got a "keystore was tampered with..." which is not surprising. ## (/) I could then browser over to http://oceana.mbari.org:8082/jira ## (/) Then through the Administration console, I did an XML backup ## (/) I then created a tar of all the attachments in the /data/jira_3_12/attachments directory ## (/) I moved both the XML and tar files to the /root/jira-upgrade directory ## (/) I then reversed the changes to the server.xml file and shut down JIRA ## (/) I left it down during the next steps in case it went so well, I could just point people to the new server (yeah, right). ## (/) I then browsed to the crowd server on oceana and add a new application using: ### URL: http://bugs.mbari.org/jira3135 ### IP: 134.89.2.29 ### Name: JIRA3135 ### Password: (ask Kevin) :) ## (/) On bugs, I made a copy of the JIRA 3.13.5 download in the /opt directory and unzipped and untarred it. ## (/) In order to configure the crowd connection I did the following: ### (/) I scp'd the /opt/crowd/client/crowd-integration-client-1.6.jar file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I removed the existing 1.6.1 crowd client jar from the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I scp'd the /opt/crowd/client/conf/crowd.properties file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I scp'd the /opt/crowd/client/conf/crowd-ehcache.xml file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I edited the crowd.properties file on bugs to look like: {noformat} application.name JIRA3135 application.password (ask Kevin) application.login.url http://oceana.mbari.org:8095/crowd/console/ crowd.server.url http://oceana.mbari.org:8095/crowd/services/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 0 session.lastvalidation session.lastvalidation {noformat} ### (/) I edited the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/osuser.xml file to comment out the current authentication mechanism and then uncomment the crowd one. ## (/) I then edited the /opt/atlassian-jira-standalone-3.13.5/conf/server/xml file and configured the database connection to the Jira_Temp database on Solstice2. I looked like this: {noformat} {noformat} ## (/) Edit the /opt/atlassian/jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/entityengine.xml and changed it from 'hsql' to 'mssql' and delete the line with "PUBLIC" in it per the instructions in the comments in that file. ## (/) I edited the /etc/httpd/conf/httpd.conf file and created a proxy pass at the bottom of the file to point a normal URL to the default port 8080 for JIRA: {noformat} # Proxy Pass for JIRA ProxyPass http://bugs.mbari.org:8080 ProxyPassReverse http://bugs.mbari.org:8080 {noformat} ## (/) I restarted Apache ## (/) I scp'd the jtds driver from oceana to the /opt/atlassian-jira-standalone-3.13.5/common/lib directory (you could down from the internet) ## (/) I then went to the /opt/atlassian-jira-standalone-3.13.5/ directory and ran './bin/startup.sh'. From the log file, I could tell things were hanging. After some troubleshooting I am wondering if the local firewall is preventing the application to get access to the database on solstice2. I can telnet to port 1433, but I can't browse to the base http://bugs.mbari.org from anywhere but the local web browser. I have submitted a ticket. ## (/) I restarted the old JIRA with my hopes dashed :(. ## (/) Pat disabled the firewall on bugs.mbari.org but it still hung trying to connect to solstice2.shore.mbari.org. That is really, really perplexing. Neil mentioned that solstice2 is using Kerberos and solstice is not. Checking with the JTDS docs, version 1.3.1 of the driver added kerberos support, so I downloaded that driver and added the 'userKerberos=true' property to the URL in the server.xml file and restarted. Got an error about no credentials, so added user and password properties to the URL. Nope, no luck. Never did figure this one out, but I had Pat pull the VM inside the firewall and after some thrash it worked. Well, it sort of worked ... sigh. It turns out I had downloaded the standard version instead of the enterprise version. I need to redo this work ... grrr. ## (/) I deleted all the tables in the Jira_Temp database and removed the /data/jira3135/indexes directory (and recreated). ## (/) I downloaded the enterprise version of the 3.13.5 server. I made a copy in the /opt directory and unzipped and untarred the file. ## (/) I went back to crowd and edited the application to change the properties to: ### URL: http://bugs.shore.mbari.org:8080 ### IP: 134.89.12.31 ### Name: jira3135 ### Password: (ask Kevin) :) ## (/) I then repeated the steps above to get the server up and running with the following differences: ### The server name is now bugs.shore.mbari.org ### The paths given above are a little different in that they no longer say "standard" but say "enterprise" ### I deleted the proxy pass as it seemed to have issues before and this is only temporary anyway. ## (/) I then browsed to http://bugs.shore.mbari.org:8080 ## (/) It took me to the start up page and at the top was the option to 'import your existing data'. Seemed too good not to try. I clicked on the link. It asked me for the backup file location and the location where the indexes would be stored. ## (/) I copied the XML zip file and the attachments tar file to the /data/original directory. ## (/) I created the /data/jira3135/indexes and used those directories ... it fired off the import and I waited. ## (/) I tailed the log file to watch the import. Holy crap, it worked!!! I could log in and everything! I copied the results from the log file here for posterity sake: {noformat} 2015-07-22 20:55:45,156 http-8080-Processor22 INFO [jira.action.admin.DataImport] Running data import 2015-07-22 20:55:45,179 http-8080-Processor22 INFO [jira.action.admin.DataImport] Importing data.. 2015-07-22 20:55:45,186 http-8080-Processor22 INFO [jira.action.admin.DataImport] Start parsing XML with SAX Parser 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] XML successfully parsed 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] Removing all entries from the database. 2015-07-22 20:56:24,593 http-8080-Processor22 INFO [jira.action.admin.DataImport] All entries removed. 2015-07-22 20:56:24,594 http-8080-Processor22 INFO [jira.action.admin.DataImport] Started storing 410414 Generic Values 2015-07-22 21:01:51,967 http-8080-Processor22 INFO [jira.action.admin.DataImport] Finished storing Generic Values 2015-07-22 21:01:52,329 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:52,361 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:54,683 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLink' to module 'jira.user.format:profile-link-user-format'. 2015-07-22 21:01:54,724 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullName' to module 'jira.user.format:full-name-user-format'. 2015-07-22 21:01:54,773 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkSearcher' to module 'jira.user.format:profile-link-searcher-user-format'. 2015-07-22 21:01:54,784 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkExternal' to module 'jira.user.format:profile-link-external-user-format'. 2015-07-22 21:01:54,795 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkActionHeader' to module 'jira.user.format:profile-link-action-header-user-format'. 2015-07-22 21:01:54,807 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullProfile' to module 'jira.user.format:full-profile-user-format'. 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/comments 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/issues 2015-07-22 21:01:55,641 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/plugins 2015-07-22 21:01:55,867 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:01:55,871 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/issues does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:55,873 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/comments does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,033 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,257 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,889 http-8080-Processor22 ERROR [atlassian.jira.upgrade.ConsistencyCheckImpl] Attachments are turned on, but attachment path [/data/jira_3_12/attachments] invalid - disabling attachments 2015-07-22 21:02:13,904 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Detected that an upgrade is needed; existing data at build 299 2015-07-22 21:02:13,907 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Doing Upgrade... 2015-07-22 21:02:13,915 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value' succeeded 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 317 2015-07-22 21:02:13,944 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite filters - make each filter a favourite of its owner. 2015-07-22 21:02:17,822 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build319] Could not find author 'fpy' for filter with id '10040' 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite filters - make each filter a favourite of its owner.' succeeded 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 319 2015-07-22 21:02:17,995 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise Share Permissions. Move old shares to new shares. 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise Share Permissions. Move old shares to new shares.' succeeded 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 321 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Migrating the old JIRA UI colors to the new JIRA 3.13 colors 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build322] Custom color detected for jira.lf.menu.bgcolour : #336699 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Migrating the old JIRA UI colors to the new JIRA 3.13 colors' succeeded 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 322 2015-07-22 21:02:18,025 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite dashboards - make each dashboard a favourite of its owner. 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'cmcgann' for dashboard with id '10030' 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'fpy' for dashboard with id '10060' 2015-07-22 21:02:18,423 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'kanna' for dashboard with id '10040' 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite dashboards - make each dashboard a favourite of its owner.' succeeded 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 325 2015-07-22 21:02:18,625 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Reindexing all data in JIRA to include Favourites. 2015-07-22 21:02:18,648 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All starting... 2015-07-22 21:02:18,650 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 0% complete. Current index: Issue 2015-07-22 21:02:18,654 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:02:18,809 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 1% complete. Current index: Issue 2015-07-22 21:02:18,855 indexerPool-2-thread-10 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 2% complete. Current index: Issue 2015-07-22 21:02:18,899 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 3% complete. Current index: Issue 2015-07-22 21:02:18,945 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 4% complete. Current index: Issue 2015-07-22 21:02:19,012 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 5% complete. Current index: Issue . . . 2015-07-22 21:02:26,164 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 95% complete. Current index: Issue 2015-07-22 21:02:26,232 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 96% complete. Current index: Issue 2015-07-22 21:02:26,316 indexerPool-2-thread-9 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 97% complete. Current index: Issue 2015-07-22 21:02:26,771 indexerPool-2-thread-3 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: Issue 2015-07-22 21:02:27,261 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 8607ms. Indexer: DefaultIndexManager: paths: [/data/jira3135/indexes/issues, /data/jira3135/indexes/comments] 2015-07-22 21:02:27,263 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: SearchRequest 2015-07-22 21:02:27,268 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,293 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: SearchRequest 2015-07-22 21:02:27,308 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: PortalPage 2015-07-22 21:02:27,312 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,377 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: PortalPage 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 115ms. Indexer: SharedEntityIndexManager: paths: [/data/jira3135/indexes/entities/portalpage, /data/jira3135/indexes/entities/searchrequest] 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All complete. Total time: 8722ms. 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Reindexing all data in JIRA to include Favourites.' succeeded 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 326 2015-07-22 21:02:27,397 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade succeeded! Setting data build number to 360 2015-07-22 21:02:27,469 JiraQuartzScheduler_Worker-0 WARN [service.services.export.ExportService] Backup directory /data/jira_3_12/backup does not exist {noformat} {warning:title=Paths} It appears that the upgraded JIRA will still look for the attachments and the backup locations in the original places. So I created /data/jira_3_12/backup and untarred the original attachments to /data/jira_3_12 and then everything worked (including attachements) in the new JIRA. {warning} ## (/) I then used the upgraded JIRA to generate a new XML backup and stored it in /data/original/3.13.5 along with another tar of the files in /data/jira_3_12/attachments. ## (/) I then shutdown the JIRA server. *I should be ready to move on to version 4 upgrade WHEW* ## So, before moving on, I decided that it would be a really good idea to spin up a new Crowd instance to get rid of the :8443 in the URL and to move off of RedHat per IS requests. I have a ticket in for a new VM and a new database to try to get this going. I am waiting on that before moving on. ## (/) Pat created the VM and Neil created the database. ## (/) I logged into auth.mbari.org (name of the VM) and downloaded crowd which I unzipped to the /opt directory ## (/) I then created a /data/crowd directory and gave my account permissions on it and then edited the /opt/atlassian..../crowd-webapp/WEB-INF/classes/crowd-init.properties file to set that as the crowd home directory. ## (/) The instructions say to download the JDBC driver, but they already have JTDS 1.2.7 in the download so I did not do anything. ## (/) You have to manually connect up CrowdID to a database as they setup wizard does not currently do this. ### (/) They say to download the driver, but again 1.2.7 was there so I did nothing. ### (/) I edited the /opt/atlassian.../apache-tomcat/conf/Catalina/localhost/openidserver.xml to look like: {noformat} {noformat} ### (/) I edited the /opt/atlassian.../build.properties files to look like: {noformat} # Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See https://confluence.atlassian.com/display/CROWD/Connecting+Crowd+to+a+Database hibernate.dialect=org.hibernate.dialect.SQLServerDialect # The Hibernate transaction factory to use. See https://confluence.atlassian.com/display/CROWD/Configuring+Crowd hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory # The http port you wish to run crowd from, ie: http://localhost:8095/crowd crowd.tomcat.connector.port=8095 # Tomcat requires a unique port for shutdown crowd.tomcat.shutdown.port=8020 # Crowd context root crowd.url=http://localhost:8095/crowd # Demo context root demo.url=http://localhost:8095/demo # OpenID server context root openidserver.url=http://localhost:8095/openidserver {noformat} ### (/) I then ran the build.sh script in the root of /opt/atlassian... ## (/) I fired up crowd using the /opt/atlassian.../start_crowd.sh script ## (/) I then went to http://auth.mbari.org:8095/crowd to kick off the start up wizard ## (/) I grabbed a new eval license from my account on atlassian and pasted into the license page. ## (/) I selected "New install" on the next page. ## (/) I configured the JDBC connection using this connection URL with user DB_Collaboration {noformat} jdbc:jtds:sqlserver://dione.mbari.org:51001/Crowd;domain=SHORE;useNTLMv2=TRUE {noformat} ## (/) I left the "Options" as they came up {warning:title=Paths} Not sure if this is a problem, but because I started the set up using auth.mbari.org, it set the Base URL to http://auth.mbari.org:8095/crowd instead of localhost. Hope that is not a problem. We will see. {warning} ## (/) I configured the email connection using the settings from [here|https://wind.shore.mbari.org/is/howto/email/mbarimail/imap] and I used my network login (probably shouldn't be doing that ... not sure where it stores my password, but I am assuming in the DB). ## (/) For the local admin account, I created a user named 'crowdadm' so it would not clash with my LDAP account. See Kevin Gomes for password information. ## (/) I checked the OpenID server as an integrated application ## (/) It then took me to the login page and I logged in using the newly minted admin account. Seemed all is well so far. ## (/) I visited the openidserver URL as well and that seemed OK. ## (/) I decided to wait on configuring the MBARI LDAP directory until I got everything with SSL working. ## (/) Now the next step was to follow the directions to configure Crowd to run over SSL found [here|https://confluence.atlassian.com/display/CROWD/Configuring+Crowd+to+Work+with+SSL] ## (/) I shutdown crowd. Note that the stop script does not shutdown things correctly and I noticed the crowd app running as root. That should not be if I started as kgomes. Not sure what is up with that. ## (/) Now Joe had already configured SSL once, so I used his connector configuration in the server.xml file and so the final file looked like: {noformat} {noformat} ## (/) I then edited the /data/crowd/crowd.properties to look like: {noformat} #Sat Aug 01 09:05:15 PDT 2015 session.lastvalidation=session.lastvalidation session.tokenkey=session.tokenkey crowd.server.url=https\://localhost\:8443/crowd/services/ application.name=crowd http.timeout=30000 session.isauthenticated=session.isauthenticated application.login.url=https\://localhost\:8443/crowd/console/ session.validationinterval=0 application.password=Y1Xp3OorCmsOP4eruL1dmH {noformat} One thing to note here is that based on a comment from the SSL configuration page at atlassian (Steve's comment), you are supposed to leave all the host names the same. For example, if the file says localhost, leave it localhost. So this created a bit of a problem based on the fact that I had left the base URL pointing to auth.mbari.org in the wizard steps above. That step wrote auth.mbari.org to the /data/crowd/crowd.properties. All the other files reference localhost, so to be consistent, I changed auth.mbari.org to localhost in the /data/crowd/crowd.properties file. We will see if this works. ## (/) Per the instructions on the atlassian page (referenced above), I also edited the build.properties file and the /client/conf/crowd.properties files before I restarted and used the SSL URLs ## build.properties: {noformat} # Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See https://confluence.atlassian.com/display/CROWD/Connecting+Crowd+to+a+Database hibernate.dialect=org.hibernate.dialect.SQLServerDialect # The Hibernate transaction factory to use. See https://confluence.atlassian.com/display/CROWD/Configuring+Crowd hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory # The http port you wish to run crowd from, ie: http://localhost:8095/crowd crowd.tomcat.connector.port=8095 # Tomcat requires a unique port for shutdown crowd.tomcat.shutdown.port=8020 # Crowd context root crowd.url=https://localhost:8443/crowd # Demo context root demo.url=https://localhost:8443/demo # OpenID server context root openidserver.url=https://localhost:8443/openidserver {noformat} ## crowd.properties (client) {noformat} application.name crowd application.password password application.login.url https://localhost:8443/crowd/console/ crowd.server.url https://localhost:8443/crowd/services/ crowd.base.url https://localhost:8443/crowd/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 2 session.lastvalidation session.lastvalidation {noformat} ## (/) Although not stated, I am assuming you would need to run the build.sh script to push the build.properties changes to their proper places, so I did that. Note that before doing that, I know that it will clobber the server.xml changes I made, so I made a copy of that file and diff'd them after and then rolled the previous changes to the new server.xml file. Actually, amazingly enough, it seems to have done the connector entry correctly so I left it after running the build.sh script. ## (/) Crossed my fingers and then restarted crowd. I tailed the catalina.out file and did not see any stack traces so that is a good sign! ## (/) I visited https://auth.mbari.org:8443/crowd first. It could not find that page, but I suspect that is because I am browsing from the outside, so I tried just https://auth.mbari.org/crowd and got a service unavailable. I am suspecting that this is a combination of firewall and proxy pass and I will send this info to Joe. From what I can see on the crowd side, it seems like the server started cleanly, we just can't get to it. I tried to reach it from a browser on the machine itself too (through VNC) with the same service not available. ## (/) Here are the notes from Joe after he fixed it! Wooohooo! {noformat} Hey Kevin, Thanks for starting clean! I had to make a few adjustments. 1-I modified the server.xml file in /opt/atlassian-crowd-2.8.3/apache-tomcat/conf/server.xml so there are two connectors per the instructions on the Atlassian site. I have backed up this good server.xml file in /etc/temp/ if you want to browse it to see what I did. Of note is that I removed all the jargon referencing the types of ciphers available to simplify things for now. 2-I modified /data/crowd/crowd.properties to have crowd.server.url=https\://localhost\:8443/crowd/services/ application.login.url=https\://localhost\:8443/crowd/console/ But that would cause my login to error with an error saying it was unable to reach the authentication server. I scratched my head for a bit. When I revert the values to just using non-SSL and try to log in, I just get an "invalid login" (I don't know the crowdadm password). So I worked under the assumption that if I can configure SSL to get an "invalid login" when logging in then it would work when provided real credentials. So, I then changed /data/crowd/crowd.proprties to: crowd.server.url=https\://auth.mbari.org\:8443/crowd/services/ application.login.url=https\://auth.mbari.org\:8443/crowd/console/ And now when I try to log in with SSL it says "invalid login". Strange because all the other values I can find only show "localhost" .. in any case... Can you try to log in now? {noformat}]]> 27558140 27590903 4.4: [https://confluence.atlassian.com/display/JIRA044/Migrating+JIRA+to+Another+Server] ## The JIRA configuration tool: [https://confluence.atlassian.com/display/JIRA044/Using+the+JIRA+Configuration+Tool] h5. Steps # (/) Create new VM named bugs.mbari.org in the DMZ # (/) Have Neil create database Jira_Temp on solstice2.shore.mbari.org # (/) Have Neil create database Jira on solstice2.shore.mbari.org # (/) Have Pat install Java 7 on bugs.shore.mbari.org # (/) Have Pete plumb holes through firewall so processes on bugs.mbari.org can get to Solstice2 # (/) Have Pat create DB_Collaboration account on bugs so it can run JIRA under that account and it can connect to solstice2 using that NT Domain account. # (/) Upgrade license on Atlassian site # (/) Log into bugs.shore.mbari.org # (/) Download 3.13.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 4.4.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 5.2.11 standalone Linux 64 bit tar.gz (not sure this version is necessary, but at least I have it) # (/) Unzip and untar the file to /opt # (/) Download latest JIRA (6.4.7 as of this writing). # (/) Unzip and untar it to /opt # Performed Test Upgrade ## (/) In order to export the current stuff in JIRA, I had to shut off access so people could not change the data while I was backing it up. ## (/) I ssh'd to oceana.mbari.org as root and edited the /opt/jira/conf/server.xml file and commented out the Connector section that had the port of 8010 to shut it off from the normal serving route. ## (/) I uncommented the 8082 port connector and the 8443 port connector so that I could still get to the server. ## (/) I stopped and started the JIRA server and in the log file I got a "keystore was tampered with..." which is not surprising. ## (/) I could then browser over to http://oceana.mbari.org:8082/jira ## (/) Then through the Administration console, I did an XML backup ## (/) I then created a tar of all the attachments in the /data/jira_3_12/attachments directory ## (/) I moved both the XML and tar files to the /root/jira-upgrade directory ## (/) I then reversed the changes to the server.xml file and shut down JIRA ## (/) I left it down during the next steps in case it went so well, I could just point people to the new server (yeah, right). ## (/) I then browsed to the crowd server on oceana and add a new application using: ### URL: http://bugs.mbari.org/jira3135 ### IP: 134.89.2.29 ### Name: JIRA3135 ### Password: (ask Kevin) :) ## (/) On bugs, I made a copy of the JIRA 3.13.5 download in the /opt directory and unzipped and untarred it. ## (/) In order to configure the crowd connection I did the following: ### (/) I scp'd the /opt/crowd/client/crowd-integration-client-1.6.jar file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I removed the existing 1.6.1 crowd client jar from the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I scp'd the /opt/crowd/client/conf/crowd.properties file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I scp'd the /opt/crowd/client/conf/crowd-ehcache.xml file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I edited the crowd.properties file on bugs to look like: {noformat} application.name JIRA3135 application.password (ask Kevin) application.login.url http://oceana.mbari.org:8095/crowd/console/ crowd.server.url http://oceana.mbari.org:8095/crowd/services/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 0 session.lastvalidation session.lastvalidation {noformat} ### (/) I edited the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/osuser.xml file to comment out the current authentication mechanism and then uncomment the crowd one. ## (/) I then edited the /opt/atlassian-jira-standalone-3.13.5/conf/server/xml file and configured the database connection to the Jira_Temp database on Solstice2. I looked like this: {noformat} {noformat} ## (/) Edit the /opt/atlassian/jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/entityengine.xml and changed it from 'hsql' to 'mssql' and delete the line with "PUBLIC" in it per the instructions in the comments in that file. ## (/) I edited the /etc/httpd/conf/httpd.conf file and created a proxy pass at the bottom of the file to point a normal URL to the default port 8080 for JIRA: {noformat} # Proxy Pass for JIRA ProxyPass http://bugs.mbari.org:8080 ProxyPassReverse http://bugs.mbari.org:8080 {noformat} ## (/) I restarted Apache ## (/) I scp'd the jtds driver from oceana to the /opt/atlassian-jira-standalone-3.13.5/common/lib directory (you could down from the internet) ## (/) I then went to the /opt/atlassian-jira-standalone-3.13.5/ directory and ran './bin/startup.sh'. From the log file, I could tell things were hanging. After some troubleshooting I am wondering if the local firewall is preventing the application to get access to the database on solstice2. I can telnet to port 1433, but I can't browse to the base http://bugs.mbari.org from anywhere but the local web browser. I have submitted a ticket. ## (/) I restarted the old JIRA with my hopes dashed :(. ## (/) Pat disabled the firewall on bugs.mbari.org but it still hung trying to connect to solstice2.shore.mbari.org. That is really, really perplexing. Neil mentioned that solstice2 is using Kerberos and solstice is not. Checking with the JTDS docs, version 1.3.1 of the driver added kerberos support, so I downloaded that driver and added the 'userKerberos=true' property to the URL in the server.xml file and restarted. Got an error about no credentials, so added user and password properties to the URL. Nope, no luck. Never did figure this one out, but I had Pat pull the VM inside the firewall and after some thrash it worked. Well, it sort of worked ... sigh. It turns out I had downloaded the standard version instead of the enterprise version. I need to redo this work ... grrr. ## (/) I deleted all the tables in the Jira_Temp database and removed the /data/jira3135/indexes directory (and recreated). ## (/) I downloaded the enterprise version of the 3.13.5 server. I made a copy in the /opt directory and unzipped and untarred the file. ## (/) I went back to crowd and edited the application to change the properties to: ### URL: http://bugs.shore.mbari.org:8080 ### IP: 134.89.12.31 ### Name: jira3135 ### Password: (ask Kevin) :) ## (/) I then repeated the steps above to get the server up and running with the following differences: ### The server name is now bugs.shore.mbari.org ### The paths given above are a little different in that they no longer say "standard" but say "enterprise" ### I deleted the proxy pass as it seemed to have issues before and this is only temporary anyway. ## (/) I then browsed to http://bugs.shore.mbari.org:8080 ## (/) It took me to the start up page and at the top was the option to 'import your existing data'. Seemed too good not to try. I clicked on the link. It asked me for the backup file location and the location where the indexes would be stored. ## (/) I copied the XML zip file and the attachments tar file to the /data/original directory. ## (/) I created the /data/jira3135/indexes and used those directories ... it fired off the import and I waited. ## (/) I tailed the log file to watch the import. Holy crap, it worked!!! I could log in and everything! I copied the results from the log file here for posterity sake: {noformat} 2015-07-22 20:55:45,156 http-8080-Processor22 INFO [jira.action.admin.DataImport] Running data import 2015-07-22 20:55:45,179 http-8080-Processor22 INFO [jira.action.admin.DataImport] Importing data.. 2015-07-22 20:55:45,186 http-8080-Processor22 INFO [jira.action.admin.DataImport] Start parsing XML with SAX Parser 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] XML successfully parsed 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] Removing all entries from the database. 2015-07-22 20:56:24,593 http-8080-Processor22 INFO [jira.action.admin.DataImport] All entries removed. 2015-07-22 20:56:24,594 http-8080-Processor22 INFO [jira.action.admin.DataImport] Started storing 410414 Generic Values 2015-07-22 21:01:51,967 http-8080-Processor22 INFO [jira.action.admin.DataImport] Finished storing Generic Values 2015-07-22 21:01:52,329 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:52,361 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:54,683 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLink' to module 'jira.user.format:profile-link-user-format'. 2015-07-22 21:01:54,724 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullName' to module 'jira.user.format:full-name-user-format'. 2015-07-22 21:01:54,773 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkSearcher' to module 'jira.user.format:profile-link-searcher-user-format'. 2015-07-22 21:01:54,784 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkExternal' to module 'jira.user.format:profile-link-external-user-format'. 2015-07-22 21:01:54,795 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkActionHeader' to module 'jira.user.format:profile-link-action-header-user-format'. 2015-07-22 21:01:54,807 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullProfile' to module 'jira.user.format:full-profile-user-format'. 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/comments 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/issues 2015-07-22 21:01:55,641 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/plugins 2015-07-22 21:01:55,867 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:01:55,871 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/issues does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:55,873 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/comments does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,033 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,257 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,889 http-8080-Processor22 ERROR [atlassian.jira.upgrade.ConsistencyCheckImpl] Attachments are turned on, but attachment path [/data/jira_3_12/attachments] invalid - disabling attachments 2015-07-22 21:02:13,904 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Detected that an upgrade is needed; existing data at build 299 2015-07-22 21:02:13,907 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Doing Upgrade... 2015-07-22 21:02:13,915 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value' succeeded 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 317 2015-07-22 21:02:13,944 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite filters - make each filter a favourite of its owner. 2015-07-22 21:02:17,822 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build319] Could not find author 'fpy' for filter with id '10040' 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite filters - make each filter a favourite of its owner.' succeeded 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 319 2015-07-22 21:02:17,995 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise Share Permissions. Move old shares to new shares. 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise Share Permissions. Move old shares to new shares.' succeeded 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 321 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Migrating the old JIRA UI colors to the new JIRA 3.13 colors 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build322] Custom color detected for jira.lf.menu.bgcolour : #336699 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Migrating the old JIRA UI colors to the new JIRA 3.13 colors' succeeded 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 322 2015-07-22 21:02:18,025 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite dashboards - make each dashboard a favourite of its owner. 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'cmcgann' for dashboard with id '10030' 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'fpy' for dashboard with id '10060' 2015-07-22 21:02:18,423 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'kanna' for dashboard with id '10040' 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite dashboards - make each dashboard a favourite of its owner.' succeeded 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 325 2015-07-22 21:02:18,625 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Reindexing all data in JIRA to include Favourites. 2015-07-22 21:02:18,648 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All starting... 2015-07-22 21:02:18,650 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 0% complete. Current index: Issue 2015-07-22 21:02:18,654 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:02:18,809 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 1% complete. Current index: Issue 2015-07-22 21:02:18,855 indexerPool-2-thread-10 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 2% complete. Current index: Issue 2015-07-22 21:02:18,899 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 3% complete. Current index: Issue 2015-07-22 21:02:18,945 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 4% complete. Current index: Issue 2015-07-22 21:02:19,012 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 5% complete. Current index: Issue . . . 2015-07-22 21:02:26,164 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 95% complete. Current index: Issue 2015-07-22 21:02:26,232 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 96% complete. Current index: Issue 2015-07-22 21:02:26,316 indexerPool-2-thread-9 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 97% complete. Current index: Issue 2015-07-22 21:02:26,771 indexerPool-2-thread-3 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: Issue 2015-07-22 21:02:27,261 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 8607ms. Indexer: DefaultIndexManager: paths: [/data/jira3135/indexes/issues, /data/jira3135/indexes/comments] 2015-07-22 21:02:27,263 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: SearchRequest 2015-07-22 21:02:27,268 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,293 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: SearchRequest 2015-07-22 21:02:27,308 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: PortalPage 2015-07-22 21:02:27,312 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,377 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: PortalPage 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 115ms. Indexer: SharedEntityIndexManager: paths: [/data/jira3135/indexes/entities/portalpage, /data/jira3135/indexes/entities/searchrequest] 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All complete. Total time: 8722ms. 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Reindexing all data in JIRA to include Favourites.' succeeded 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 326 2015-07-22 21:02:27,397 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade succeeded! Setting data build number to 360 2015-07-22 21:02:27,469 JiraQuartzScheduler_Worker-0 WARN [service.services.export.ExportService] Backup directory /data/jira_3_12/backup does not exist {noformat} {warning:title=Paths} It appears that the upgraded JIRA will still look for the attachments and the backup locations in the original places. So I created /data/jira_3_12/backup and untarred the original attachments to /data/jira_3_12 and then everything worked (including attachements) in the new JIRA. {warning} ## (/) I then used the upgraded JIRA to generate a new XML backup and stored it in /data/original/3.13.5 along with another tar of the files in /data/jira_3_12/attachments. ## (/) I then shutdown the JIRA server. *I should be ready to move on to version 4 upgrade WHEW* ## So, before moving on, I decided that it would be a really good idea to spin up a new Crowd instance to get rid of the :8443 in the URL and to move off of RedHat per IS requests. I have a ticket in for a new VM and a new database to try to get this going. I am waiting on that before moving on. ## (/) Pat created the VM and Neil created the database. ## (/) I logged into auth.mbari.org (name of the VM) and downloaded crowd which I unzipped to the /opt directory ## (/) I then created a /data/crowd directory and gave my account permissions on it and then edited the /opt/atlassian..../crowd-webapp/WEB-INF/classes/crowd-init.properties file to set that as the crowd home directory. ## (/) The instructions say to download the JDBC driver, but they already have JTDS 1.2.7 in the download so I did not do anything. ## (/) You have to manually connect up CrowdID to a database as they setup wizard does not currently do this. ### (/) They say to download the driver, but again 1.2.7 was there so I did nothing. ### (/) I edited the /opt/atlassian.../apache-tomcat/conf/Catalina/localhost/openidserver.xml to look like: {noformat} {noformat} ### (/) I edited the /opt/atlassian.../build.properties files to look like: {noformat} # Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See https://confluence.atlassian.com/display/CROWD/Connecting+Crowd+to+a+Database hibernate.dialect=org.hibernate.dialect.SQLServerDialect # The Hibernate transaction factory to use. See https://confluence.atlassian.com/display/CROWD/Configuring+Crowd hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory # The http port you wish to run crowd from, ie: http://localhost:8095/crowd crowd.tomcat.connector.port=8095 # Tomcat requires a unique port for shutdown crowd.tomcat.shutdown.port=8020 # Crowd context root crowd.url=http://localhost:8095/crowd # Demo context root demo.url=http://localhost:8095/demo # OpenID server context root openidserver.url=http://localhost:8095/openidserver {noformat} ### (/) I then ran the build.sh script in the root of /opt/atlassian... ## (/) I fired up crowd using the /opt/atlassian.../start_crowd.sh script ## (/) I then went to http://auth.mbari.org:8095/crowd to kick off the start up wizard ## (/) I grabbed a new eval license from my account on atlassian and pasted into the license page. ## (/) I selected "New install" on the next page. ## (/) I configured the JDBC connection using this connection URL with user DB_Collaboration {noformat} jdbc:jtds:sqlserver://dione.mbari.org:51001/Crowd;domain=SHORE;useNTLMv2=TRUE {noformat} ## (/) I left the "Options" as they came up {warning:title=Paths} Not sure if this is a problem, but because I started the set up using auth.mbari.org, it set the Base URL to http://auth.mbari.org:8095/crowd instead of localhost. Hope that is not a problem. We will see. {warning} ## (/) I configured the email connection using the settings from [here|https://wind.shore.mbari.org/is/howto/email/mbarimail/imap] and I used my network login (probably shouldn't be doing that ... not sure where it stores my password, but I am assuming in the DB). ## (/) For the local admin account, I created a user named 'crowdadm' so it would not clash with my LDAP account. See Kevin Gomes for password information. ## (/) I checked the OpenID server as an integrated application ## (/) It then took me to the login page and I logged in using the newly minted admin account. Seemed all is well so far. ## (/) I visited the openidserver URL as well and that seemed OK. ## (/) I decided to wait on configuring the MBARI LDAP directory until I got everything with SSL working. ## (/) Now the next step was to follow the directions to configure Crowd to run over SSL found [here|https://confluence.atlassian.com/display/CROWD/Configuring+Crowd+to+Work+with+SSL] ## (/) I shutdown crowd. Note that the stop script does not shutdown things correctly and I noticed the crowd app running as root. That should not be if I started as kgomes. Not sure what is up with that. ## (/) Now Joe had already configured SSL once, so I used his connector configuration in the server.xml file and so the final file looked like: {noformat} {noformat} ## (/) I then edited the /data/crowd/crowd.properties to look like: {noformat} #Sat Aug 01 09:05:15 PDT 2015 session.lastvalidation=session.lastvalidation session.tokenkey=session.tokenkey crowd.server.url=https\://localhost\:8443/crowd/services/ application.name=crowd http.timeout=30000 session.isauthenticated=session.isauthenticated application.login.url=https\://localhost\:8443/crowd/console/ session.validationinterval=0 application.password=Y1Xp3OorCmsOP4eruL1dmH {noformat} One thing to note here is that based on a comment from the SSL configuration page at atlassian (Steve's comment), you are supposed to leave all the host names the same. For example, if the file says localhost, leave it localhost. So this created a bit of a problem based on the fact that I had left the base URL pointing to auth.mbari.org in the wizard steps above. That step wrote auth.mbari.org to the /data/crowd/crowd.properties. All the other files reference localhost, so to be consistent, I changed auth.mbari.org to localhost in the /data/crowd/crowd.properties file. We will see if this works. ## (/) Per the instructions on the atlassian page (referenced above), I also edited the build.properties file and the /client/conf/crowd.properties files before I restarted and used the SSL URLs ## build.properties: {noformat} # Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See https://confluence.atlassian.com/display/CROWD/Connecting+Crowd+to+a+Database hibernate.dialect=org.hibernate.dialect.SQLServerDialect # The Hibernate transaction factory to use. See https://confluence.atlassian.com/display/CROWD/Configuring+Crowd hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory # The http port you wish to run crowd from, ie: http://localhost:8095/crowd crowd.tomcat.connector.port=8095 # Tomcat requires a unique port for shutdown crowd.tomcat.shutdown.port=8020 # Crowd context root crowd.url=https://localhost:8443/crowd # Demo context root demo.url=https://localhost:8443/demo # OpenID server context root openidserver.url=https://localhost:8443/openidserver {noformat} ## crowd.properties (client) {noformat} application.name crowd application.password password application.login.url https://localhost:8443/crowd/console/ crowd.server.url https://localhost:8443/crowd/services/ crowd.base.url https://localhost:8443/crowd/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 2 session.lastvalidation session.lastvalidation {noformat} ## (/) Although not stated, I am assuming you would need to run the build.sh script to push the build.properties changes to their proper places, so I did that. Note that before doing that, I know that it will clobber the server.xml changes I made, so I made a copy of that file and diff'd them after and then rolled the previous changes to the new server.xml file. Actually, amazingly enough, it seems to have done the connector entry correctly so I left it after running the build.sh script. ## (/) Crossed my fingers and then restarted crowd. I tailed the catalina.out file and did not see any stack traces so that is a good sign! ## (/) I visited https://auth.mbari.org:8443/crowd first. It could not find that page, but I suspect that is because I am browsing from the outside, so I tried just https://auth.mbari.org/crowd and got a service unavailable. I am suspecting that this is a combination of firewall and proxy pass and I will send this info to Joe. From what I can see on the crowd side, it seems like the server started cleanly, we just can't get to it. I tried to reach it from a browser on the machine itself too (through VNC) with the same service not available. ]]> 27558138 27590895 4.4: [https://confluence.atlassian.com/display/JIRA044/Migrating+JIRA+to+Another+Server] ## The JIRA configuration tool: [https://confluence.atlassian.com/display/JIRA044/Using+the+JIRA+Configuration+Tool] h5. Steps # (/) Create new VM named bugs.mbari.org in the DMZ # (/) Have Neil create database Jira_Temp on solstice2.shore.mbari.org # (/) Have Neil create database Jira on solstice2.shore.mbari.org # (/) Have Pat install Java 7 on bugs.shore.mbari.org # (/) Have Pete plumb holes through firewall so processes on bugs.mbari.org can get to Solstice2 # (/) Have Pat create DB_Collaboration account on bugs so it can run JIRA under that account and it can connect to solstice2 using that NT Domain account. # (/) Upgrade license on Atlassian site # (/) Log into bugs.shore.mbari.org # (/) Download 3.13.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 4.4.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 5.2.11 standalone Linux 64 bit tar.gz (not sure this version is necessary, but at least I have it) # (/) Unzip and untar the file to /opt # (/) Download latest JIRA (6.4.7 as of this writing). # (/) Unzip and untar it to /opt # Performed Test Upgrade ## (/) In order to export the current stuff in JIRA, I had to shut off access so people could not change the data while I was backing it up. ## (/) I ssh'd to oceana.mbari.org as root and edited the /opt/jira/conf/server.xml file and commented out the Connector section that had the port of 8010 to shut it off from the normal serving route. ## (/) I uncommented the 8082 port connector and the 8443 port connector so that I could still get to the server. ## (/) I stopped and started the JIRA server and in the log file I got a "keystore was tampered with..." which is not surprising. ## (/) I could then browser over to http://oceana.mbari.org:8082/jira ## (/) Then through the Administration console, I did an XML backup ## (/) I then created a tar of all the attachments in the /data/jira_3_12/attachments directory ## (/) I moved both the XML and tar files to the /root/jira-upgrade directory ## (/) I then reversed the changes to the server.xml file and shut down JIRA ## (/) I left it down during the next steps in case it went so well, I could just point people to the new server (yeah, right). ## (/) I then browsed to the crowd server on oceana and add a new application using: ### URL: http://bugs.mbari.org/jira3135 ### IP: 134.89.2.29 ### Name: JIRA3135 ### Password: (ask Kevin) :) ## (/) On bugs, I made a copy of the JIRA 3.13.5 download in the /opt directory and unzipped and untarred it. ## (/) In order to configure the crowd connection I did the following: ### (/) I scp'd the /opt/crowd/client/crowd-integration-client-1.6.jar file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I removed the existing 1.6.1 crowd client jar from the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I scp'd the /opt/crowd/client/conf/crowd.properties file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I scp'd the /opt/crowd/client/conf/crowd-ehcache.xml file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I edited the crowd.properties file on bugs to look like: {noformat} application.name JIRA3135 application.password (ask Kevin) application.login.url http://oceana.mbari.org:8095/crowd/console/ crowd.server.url http://oceana.mbari.org:8095/crowd/services/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 0 session.lastvalidation session.lastvalidation {noformat} ### (/) I edited the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/osuser.xml file to comment out the current authentication mechanism and then uncomment the crowd one. ## (/) I then edited the /opt/atlassian-jira-standalone-3.13.5/conf/server/xml file and configured the database connection to the Jira_Temp database on Solstice2. I looked like this: {noformat} {noformat} ## (/) Edit the /opt/atlassian/jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/entityengine.xml and changed it from 'hsql' to 'mssql' and delete the line with "PUBLIC" in it per the instructions in the comments in that file. ## (/) I edited the /etc/httpd/conf/httpd.conf file and created a proxy pass at the bottom of the file to point a normal URL to the default port 8080 for JIRA: {noformat} # Proxy Pass for JIRA ProxyPass http://bugs.mbari.org:8080 ProxyPassReverse http://bugs.mbari.org:8080 {noformat} ## (/) I restarted Apache ## (/) I scp'd the jtds driver from oceana to the /opt/atlassian-jira-standalone-3.13.5/common/lib directory (you could down from the internet) ## (/) I then went to the /opt/atlassian-jira-standalone-3.13.5/ directory and ran './bin/startup.sh'. From the log file, I could tell things were hanging. After some troubleshooting I am wondering if the local firewall is preventing the application to get access to the database on solstice2. I can telnet to port 1433, but I can't browse to the base http://bugs.mbari.org from anywhere but the local web browser. I have submitted a ticket. ## (/) I restarted the old JIRA with my hopes dashed :(. ## (/) Pat disabled the firewall on bugs.mbari.org but it still hung trying to connect to solstice2.shore.mbari.org. That is really, really perplexing. Neil mentioned that solstice2 is using Kerberos and solstice is not. Checking with the JTDS docs, version 1.3.1 of the driver added kerberos support, so I downloaded that driver and added the 'userKerberos=true' property to the URL in the server.xml file and restarted. Got an error about no credentials, so added user and password properties to the URL. Nope, no luck. Never did figure this one out, but I had Pat pull the VM inside the firewall and after some thrash it worked. Well, it sort of worked ... sigh. It turns out I had downloaded the standard version instead of the enterprise version. I need to redo this work ... grrr. ## (/) I deleted all the tables in the Jira_Temp database and removed the /data/jira3135/indexes directory (and recreated). ## (/) I downloaded the enterprise version of the 3.13.5 server. I made a copy in the /opt directory and unzipped and untarred the file. ## (/) I went back to crowd and edited the application to change the properties to: ### URL: http://bugs.shore.mbari.org:8080 ### IP: 134.89.12.31 ### Name: jira3135 ### Password: (ask Kevin) :) ## (/) I then repeated the steps above to get the server up and running with the following differences: ### The server name is now bugs.shore.mbari.org ### The paths given above are a little different in that they no longer say "standard" but say "enterprise" ### I deleted the proxy pass as it seemed to have issues before and this is only temporary anyway. ## (/) I then browsed to http://bugs.shore.mbari.org:8080 ## (/) It took me to the start up page and at the top was the option to 'import your existing data'. Seemed too good not to try. I clicked on the link. It asked me for the backup file location and the location where the indexes would be stored. ## (/) I copied the XML zip file and the attachments tar file to the /data/original directory. ## (/) I created the /data/jira3135/indexes and used those directories ... it fired off the import and I waited. ## (/) I tailed the log file to watch the import. Holy crap, it worked!!! I could log in and everything! I copied the results from the log file here for posterity sake: {noformat} 2015-07-22 20:55:45,156 http-8080-Processor22 INFO [jira.action.admin.DataImport] Running data import 2015-07-22 20:55:45,179 http-8080-Processor22 INFO [jira.action.admin.DataImport] Importing data.. 2015-07-22 20:55:45,186 http-8080-Processor22 INFO [jira.action.admin.DataImport] Start parsing XML with SAX Parser 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] XML successfully parsed 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] Removing all entries from the database. 2015-07-22 20:56:24,593 http-8080-Processor22 INFO [jira.action.admin.DataImport] All entries removed. 2015-07-22 20:56:24,594 http-8080-Processor22 INFO [jira.action.admin.DataImport] Started storing 410414 Generic Values 2015-07-22 21:01:51,967 http-8080-Processor22 INFO [jira.action.admin.DataImport] Finished storing Generic Values 2015-07-22 21:01:52,329 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:52,361 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:54,683 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLink' to module 'jira.user.format:profile-link-user-format'. 2015-07-22 21:01:54,724 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullName' to module 'jira.user.format:full-name-user-format'. 2015-07-22 21:01:54,773 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkSearcher' to module 'jira.user.format:profile-link-searcher-user-format'. 2015-07-22 21:01:54,784 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkExternal' to module 'jira.user.format:profile-link-external-user-format'. 2015-07-22 21:01:54,795 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkActionHeader' to module 'jira.user.format:profile-link-action-header-user-format'. 2015-07-22 21:01:54,807 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullProfile' to module 'jira.user.format:full-profile-user-format'. 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/comments 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/issues 2015-07-22 21:01:55,641 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/plugins 2015-07-22 21:01:55,867 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:01:55,871 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/issues does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:55,873 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/comments does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,033 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,257 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,889 http-8080-Processor22 ERROR [atlassian.jira.upgrade.ConsistencyCheckImpl] Attachments are turned on, but attachment path [/data/jira_3_12/attachments] invalid - disabling attachments 2015-07-22 21:02:13,904 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Detected that an upgrade is needed; existing data at build 299 2015-07-22 21:02:13,907 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Doing Upgrade... 2015-07-22 21:02:13,915 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value' succeeded 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 317 2015-07-22 21:02:13,944 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite filters - make each filter a favourite of its owner. 2015-07-22 21:02:17,822 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build319] Could not find author 'fpy' for filter with id '10040' 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite filters - make each filter a favourite of its owner.' succeeded 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 319 2015-07-22 21:02:17,995 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise Share Permissions. Move old shares to new shares. 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise Share Permissions. Move old shares to new shares.' succeeded 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 321 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Migrating the old JIRA UI colors to the new JIRA 3.13 colors 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build322] Custom color detected for jira.lf.menu.bgcolour : #336699 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Migrating the old JIRA UI colors to the new JIRA 3.13 colors' succeeded 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 322 2015-07-22 21:02:18,025 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite dashboards - make each dashboard a favourite of its owner. 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'cmcgann' for dashboard with id '10030' 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'fpy' for dashboard with id '10060' 2015-07-22 21:02:18,423 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'kanna' for dashboard with id '10040' 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite dashboards - make each dashboard a favourite of its owner.' succeeded 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 325 2015-07-22 21:02:18,625 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Reindexing all data in JIRA to include Favourites. 2015-07-22 21:02:18,648 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All starting... 2015-07-22 21:02:18,650 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 0% complete. Current index: Issue 2015-07-22 21:02:18,654 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:02:18,809 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 1% complete. Current index: Issue 2015-07-22 21:02:18,855 indexerPool-2-thread-10 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 2% complete. Current index: Issue 2015-07-22 21:02:18,899 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 3% complete. Current index: Issue 2015-07-22 21:02:18,945 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 4% complete. Current index: Issue 2015-07-22 21:02:19,012 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 5% complete. Current index: Issue . . . 2015-07-22 21:02:26,164 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 95% complete. Current index: Issue 2015-07-22 21:02:26,232 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 96% complete. Current index: Issue 2015-07-22 21:02:26,316 indexerPool-2-thread-9 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 97% complete. Current index: Issue 2015-07-22 21:02:26,771 indexerPool-2-thread-3 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: Issue 2015-07-22 21:02:27,261 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 8607ms. Indexer: DefaultIndexManager: paths: [/data/jira3135/indexes/issues, /data/jira3135/indexes/comments] 2015-07-22 21:02:27,263 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: SearchRequest 2015-07-22 21:02:27,268 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,293 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: SearchRequest 2015-07-22 21:02:27,308 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: PortalPage 2015-07-22 21:02:27,312 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,377 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: PortalPage 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 115ms. Indexer: SharedEntityIndexManager: paths: [/data/jira3135/indexes/entities/portalpage, /data/jira3135/indexes/entities/searchrequest] 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All complete. Total time: 8722ms. 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Reindexing all data in JIRA to include Favourites.' succeeded 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 326 2015-07-22 21:02:27,397 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade succeeded! Setting data build number to 360 2015-07-22 21:02:27,469 JiraQuartzScheduler_Worker-0 WARN [service.services.export.ExportService] Backup directory /data/jira_3_12/backup does not exist {noformat} {warning:title=Paths} It appears that the upgraded JIRA will still look for the attachments and the backup locations in the original places. So I created /data/jira_3_12/backup and untarred the original attachments to /data/jira_3_12 and then everything worked (including attachements) in the new JIRA. {warning} ## (/) I then used the upgraded JIRA to generate a new XML backup and stored it in /data/original/3.13.5 along with another tar of the files in /data/jira_3_12/attachments. ## (/) I then shutdown the JIRA server. *I should be ready to move on to version 4 upgrade WHEW* ## So, before moving on, I decided that it would be a really good idea to spin up a new Crowd instance to get rid of the :8443 in the URL and to move off of RedHat per IS requests. I have a ticket in for a new VM and a new database to try to get this going. I am waiting on that before moving on. ## (/) Pat created the VM and Neil created the database. ## (/) I logged into auth.mbari.org (name of the VM) and downloaded crowd which I unzipped to the /opt directory ## (/) I then created a /data/crowd directory and gave my account permissions on it and then edited the /opt/atlassian..../crowd-webapp/WEB-INF/classes/crowd-init.properties file to set that as the crowd home directory. ## (/) The instructions say to download the JDBC driver, but they already have JTDS 1.2.7 in the download so I did not do anything. ## (/) You have to manually connect up CrowdID to a database as they setup wizard does not currently do this. ### (/) They say to download the driver, but again 1.2.7 was there so I did nothing. ### (/) I edited the /opt/atlassian.../apache-tomcat/conf/Catalina/localhost/openidserver.xml to look like: {noformat} {noformat} ### (/) I edited the /opt/atlassian.../build.properties files to look like: {noformat} # Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See https://confluence.atlassian.com/display/CROWD/Connecting+Crowd+to+a+Database hibernate.dialect=org.hibernate.dialect.SQLServerDialect # The Hibernate transaction factory to use. See https://confluence.atlassian.com/display/CROWD/Configuring+Crowd hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory # The http port you wish to run crowd from, ie: http://localhost:8095/crowd crowd.tomcat.connector.port=8095 # Tomcat requires a unique port for shutdown crowd.tomcat.shutdown.port=8020 # Crowd context root crowd.url=http://localhost:8095/crowd # Demo context root demo.url=http://localhost:8095/demo # OpenID server context root openidserver.url=http://localhost:8095/openidserver {noformat} ### (/) I then ran the build.sh script in the root of /opt/atlassian... ## (/) I fired up crowd using the /opt/atlassian.../start_crowd.sh script ## (/) I then went to http://auth.mbari.org:8095/crowd to kick off the start up wizard ## (/) I grabbed a new eval license from my account on atlassian and pasted into the license page. ## (/) I selected "New install" on the next page. ## (/) I configured the JDBC connection using this connection URL with user DB_Collaboration {noformat} jdbc:jtds:sqlserver://dione.mbari.org:51001/Crowd;domain=SHORE;useNTLMv2=TRUE {noformat} ## (/) I left the "Options" as they came up {warning:title=Paths} Not sure if this is a problem, but because I started the set up using auth.mbari.org, it set the Base URL to http://auth.mbari.org:8095/crowd instead of localhost. Hope that is not a problem. We will see. {warning} ## (/) I configured the email connection using the settings from [here|https://wind.shore.mbari.org/is/howto/email/mbarimail/imap] and I used my network login (probably shouldn't be doing that ... not sure where it stores my password, but I am assuming in the DB). ## (/) For the local admin account, I created a user named 'crowdadm' so it would not clash with my LDAP account. See Kevin Gomes for password information. ## (/) I checked the OpenID server as an integrated application ## (/) It then took me to the login page and I logged in using the newly minted admin account. Seemed all is well so far. ## (/) I visited the openidserver URL as well and that seemed OK. ## (/) I decided to wait on configuring the MBARI LDAP directory until I got everything with SSL working. ## (/) Now the next step was to follow the directions to configure Crowd to run over SSL found [here|https://confluence.atlassian.com/display/CROWD/Configuring+Crowd+to+Work+with+SSL] ## (/) I shutdown crowd. Note that the stop script does not shutdown things correctly and I noticed the crowd app running as root. That should not be if I started as kgomes. Not sure what is up with that. ## (/) Now Joe had already configured SSL once, so I used his connector configuration in the server.xml file and so the final file looked like: {noformat} {noformat} ## (/) I then edited the /data/crowd/crowd.properties to look like: {noformat} #Sat Aug 01 09:05:15 PDT 2015 session.lastvalidation=session.lastvalidation session.tokenkey=session.tokenkey crowd.server.url=https\://localhost\:8443/crowd/services/ application.name=crowd http.timeout=30000 session.isauthenticated=session.isauthenticated application.login.url=https\://localhost\:8443/crowd/console/ session.validationinterval=0 application.password=Y1Xp3OorCmsOP4eruL1dmH {noformat} One thing to note here is that based on a comment from the SSL configuration page at atlassian (Steve's comment), you are supposed to leave all the host names the same. For example, if the file says localhost, leave it localhost. So this created a bit of a problem based on the fact that I had left the base URL pointing to auth.mbari.org in the wizard steps above. That step wrote auth.mbari.org to the /data/crowd/crowd.properties. All the other files reference localhost, so to be consistent, I changed auth.mbari.org to localhost in the /data/crowd/crowd.properties file. We will see if this works. ## (/) Per the instructions on the atlassian page (referenced above), I also edited the build.properties file and the /client/conf/crowd.properties files before I restarted and used the SSL URLs ## build.properties: {noformat} # Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See https://confluence.atlassian.com/display/CROWD/Connecting+Crowd+to+a+Database hibernate.dialect=org.hibernate.dialect.SQLServerDialect # The Hibernate transaction factory to use. See https://confluence.atlassian.com/display/CROWD/Configuring+Crowd hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory # The http port you wish to run crowd from, ie: http://localhost:8095/crowd crowd.tomcat.connector.port=8095 # Tomcat requires a unique port for shutdown crowd.tomcat.shutdown.port=8020 # Crowd context root crowd.url=https://localhost:8443/crowd # Demo context root demo.url=https://localhost:8443/demo # OpenID server context root openidserver.url=https://localhost:8443/openidserver {noformat} ## crowd.properties (client) {noformat} application.name crowd application.password password application.login.url https://localhost:8443/crowd/console/ crowd.server.url https://localhost:8443/crowd/services/ crowd.base.url https://localhost:8443/crowd/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 2 session.lastvalidation session.lastvalidation {noformat} ## (/) Although not stated, I am assuming you would need to run the build.sh script to push the build.properties changes to their proper places, so I did that. Note that before doing that, I know that it will clobber the server.xml changes I made, so I made a copy of that file and diff'd them after and then rolled the previous changes to the new server.xml file. Actually, amazingly enough, it seems to have done the connector entry correctly so I left it after running the build.sh script. ## (/) Crossed my fingers and then restarted crowd. I tailed the catalina.out file and did not see any stack traces so that is a good sign! ## (/) I visited https://auth.mbari.org:8443/crowd first. It could not find that page, but I suspect that is because I am browsing from the outside, so I tried just https://auth.mbari.org/crowd and got a service unavailable. I am suspecting that this is a combination of firewall and proxy pass and I will update the trouble ticket and have Joe take a look. From what I can see on the crowd side, it seems like the server started cleanly, we just can't get to it. I tried to reach it from a browser on the machine itself too (through VNC) with the same service not available. ]]> 27558130 27590894 4.4: [https://confluence.atlassian.com/display/JIRA044/Migrating+JIRA+to+Another+Server] ## The JIRA configuration tool: [https://confluence.atlassian.com/display/JIRA044/Using+the+JIRA+Configuration+Tool] h5. Steps # (/) Create new VM named bugs.mbari.org in the DMZ # (/) Have Neil create database Jira_Temp on solstice2.shore.mbari.org # (/) Have Neil create database Jira on solstice2.shore.mbari.org # (/) Have Pat install Java 7 on bugs.shore.mbari.org # (/) Have Pete plumb holes through firewall so processes on bugs.mbari.org can get to Solstice2 # (/) Have Pat create DB_Collaboration account on bugs so it can run JIRA under that account and it can connect to solstice2 using that NT Domain account. # (/) Upgrade license on Atlassian site # (/) Log into bugs.shore.mbari.org # (/) Download 3.13.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 4.4.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 5.2.11 standalone Linux 64 bit tar.gz (not sure this version is necessary, but at least I have it) # (/) Unzip and untar the file to /opt # (/) Download latest JIRA (6.4.7 as of this writing). # (/) Unzip and untar it to /opt # Performed Test Upgrade ## (/) In order to export the current stuff in JIRA, I had to shut off access so people could not change the data while I was backing it up. ## (/) I ssh'd to oceana.mbari.org as root and edited the /opt/jira/conf/server.xml file and commented out the Connector section that had the port of 8010 to shut it off from the normal serving route. ## (/) I uncommented the 8082 port connector and the 8443 port connector so that I could still get to the server. ## (/) I stopped and started the JIRA server and in the log file I got a "keystore was tampered with..." which is not surprising. ## (/) I could then browser over to http://oceana.mbari.org:8082/jira ## (/) Then through the Administration console, I did an XML backup ## (/) I then created a tar of all the attachments in the /data/jira_3_12/attachments directory ## (/) I moved both the XML and tar files to the /root/jira-upgrade directory ## (/) I then reversed the changes to the server.xml file and shut down JIRA ## (/) I left it down during the next steps in case it went so well, I could just point people to the new server (yeah, right). ## (/) I then browsed to the crowd server on oceana and add a new application using: ### URL: http://bugs.mbari.org/jira3135 ### IP: 134.89.2.29 ### Name: JIRA3135 ### Password: (ask Kevin) :) ## (/) On bugs, I made a copy of the JIRA 3.13.5 download in the /opt directory and unzipped and untarred it. ## (/) In order to configure the crowd connection I did the following: ### (/) I scp'd the /opt/crowd/client/crowd-integration-client-1.6.jar file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I removed the existing 1.6.1 crowd client jar from the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I scp'd the /opt/crowd/client/conf/crowd.properties file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I scp'd the /opt/crowd/client/conf/crowd-ehcache.xml file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I edited the crowd.properties file on bugs to look like: {noformat} application.name JIRA3135 application.password (ask Kevin) application.login.url http://oceana.mbari.org:8095/crowd/console/ crowd.server.url http://oceana.mbari.org:8095/crowd/services/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 0 session.lastvalidation session.lastvalidation {noformat} ### (/) I edited the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/osuser.xml file to comment out the current authentication mechanism and then uncomment the crowd one. ## (/) I then edited the /opt/atlassian-jira-standalone-3.13.5/conf/server/xml file and configured the database connection to the Jira_Temp database on Solstice2. I looked like this: {noformat} {noformat} ## (/) Edit the /opt/atlassian/jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/entityengine.xml and changed it from 'hsql' to 'mssql' and delete the line with "PUBLIC" in it per the instructions in the comments in that file. ## (/) I edited the /etc/httpd/conf/httpd.conf file and created a proxy pass at the bottom of the file to point a normal URL to the default port 8080 for JIRA: {noformat} # Proxy Pass for JIRA ProxyPass http://bugs.mbari.org:8080 ProxyPassReverse http://bugs.mbari.org:8080 {noformat} ## (/) I restarted Apache ## (/) I scp'd the jtds driver from oceana to the /opt/atlassian-jira-standalone-3.13.5/common/lib directory (you could down from the internet) ## (/) I then went to the /opt/atlassian-jira-standalone-3.13.5/ directory and ran './bin/startup.sh'. From the log file, I could tell things were hanging. After some troubleshooting I am wondering if the local firewall is preventing the application to get access to the database on solstice2. I can telnet to port 1433, but I can't browse to the base http://bugs.mbari.org from anywhere but the local web browser. I have submitted a ticket. ## (/) I restarted the old JIRA with my hopes dashed :(. ## (/) Pat disabled the firewall on bugs.mbari.org but it still hung trying to connect to solstice2.shore.mbari.org. That is really, really perplexing. Neil mentioned that solstice2 is using Kerberos and solstice is not. Checking with the JTDS docs, version 1.3.1 of the driver added kerberos support, so I downloaded that driver and added the 'userKerberos=true' property to the URL in the server.xml file and restarted. Got an error about no credentials, so added user and password properties to the URL. Nope, no luck. Never did figure this one out, but I had Pat pull the VM inside the firewall and after some thrash it worked. Well, it sort of worked ... sigh. It turns out I had downloaded the standard version instead of the enterprise version. I need to redo this work ... grrr. ## (/) I deleted all the tables in the Jira_Temp database and removed the /data/jira3135/indexes directory (and recreated). ## (/) I downloaded the enterprise version of the 3.13.5 server. I made a copy in the /opt directory and unzipped and untarred the file. ## (/) I went back to crowd and edited the application to change the properties to: ### URL: http://bugs.shore.mbari.org:8080 ### IP: 134.89.12.31 ### Name: jira3135 ### Password: (ask Kevin) :) ## (/) I then repeated the steps above to get the server up and running with the following differences: ### The server name is now bugs.shore.mbari.org ### The paths given above are a little different in that they no longer say "standard" but say "enterprise" ### I deleted the proxy pass as it seemed to have issues before and this is only temporary anyway. ## (/) I then browsed to http://bugs.shore.mbari.org:8080 ## (/) It took me to the start up page and at the top was the option to 'import your existing data'. Seemed too good not to try. I clicked on the link. It asked me for the backup file location and the location where the indexes would be stored. ## (/) I copied the XML zip file and the attachments tar file to the /data/original directory. ## (/) I created the /data/jira3135/indexes and used those directories ... it fired off the import and I waited. ## (/) I tailed the log file to watch the import. Holy crap, it worked!!! I could log in and everything! I copied the results from the log file here for posterity sake: {noformat} 2015-07-22 20:55:45,156 http-8080-Processor22 INFO [jira.action.admin.DataImport] Running data import 2015-07-22 20:55:45,179 http-8080-Processor22 INFO [jira.action.admin.DataImport] Importing data.. 2015-07-22 20:55:45,186 http-8080-Processor22 INFO [jira.action.admin.DataImport] Start parsing XML with SAX Parser 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] XML successfully parsed 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] Removing all entries from the database. 2015-07-22 20:56:24,593 http-8080-Processor22 INFO [jira.action.admin.DataImport] All entries removed. 2015-07-22 20:56:24,594 http-8080-Processor22 INFO [jira.action.admin.DataImport] Started storing 410414 Generic Values 2015-07-22 21:01:51,967 http-8080-Processor22 INFO [jira.action.admin.DataImport] Finished storing Generic Values 2015-07-22 21:01:52,329 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:52,361 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:54,683 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLink' to module 'jira.user.format:profile-link-user-format'. 2015-07-22 21:01:54,724 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullName' to module 'jira.user.format:full-name-user-format'. 2015-07-22 21:01:54,773 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkSearcher' to module 'jira.user.format:profile-link-searcher-user-format'. 2015-07-22 21:01:54,784 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkExternal' to module 'jira.user.format:profile-link-external-user-format'. 2015-07-22 21:01:54,795 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkActionHeader' to module 'jira.user.format:profile-link-action-header-user-format'. 2015-07-22 21:01:54,807 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullProfile' to module 'jira.user.format:full-profile-user-format'. 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/comments 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/issues 2015-07-22 21:01:55,641 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/plugins 2015-07-22 21:01:55,867 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:01:55,871 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/issues does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:55,873 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/comments does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,033 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,257 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,889 http-8080-Processor22 ERROR [atlassian.jira.upgrade.ConsistencyCheckImpl] Attachments are turned on, but attachment path [/data/jira_3_12/attachments] invalid - disabling attachments 2015-07-22 21:02:13,904 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Detected that an upgrade is needed; existing data at build 299 2015-07-22 21:02:13,907 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Doing Upgrade... 2015-07-22 21:02:13,915 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value' succeeded 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 317 2015-07-22 21:02:13,944 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite filters - make each filter a favourite of its owner. 2015-07-22 21:02:17,822 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build319] Could not find author 'fpy' for filter with id '10040' 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite filters - make each filter a favourite of its owner.' succeeded 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 319 2015-07-22 21:02:17,995 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise Share Permissions. Move old shares to new shares. 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise Share Permissions. Move old shares to new shares.' succeeded 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 321 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Migrating the old JIRA UI colors to the new JIRA 3.13 colors 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build322] Custom color detected for jira.lf.menu.bgcolour : #336699 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Migrating the old JIRA UI colors to the new JIRA 3.13 colors' succeeded 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 322 2015-07-22 21:02:18,025 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite dashboards - make each dashboard a favourite of its owner. 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'cmcgann' for dashboard with id '10030' 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'fpy' for dashboard with id '10060' 2015-07-22 21:02:18,423 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'kanna' for dashboard with id '10040' 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite dashboards - make each dashboard a favourite of its owner.' succeeded 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 325 2015-07-22 21:02:18,625 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Reindexing all data in JIRA to include Favourites. 2015-07-22 21:02:18,648 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All starting... 2015-07-22 21:02:18,650 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 0% complete. Current index: Issue 2015-07-22 21:02:18,654 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:02:18,809 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 1% complete. Current index: Issue 2015-07-22 21:02:18,855 indexerPool-2-thread-10 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 2% complete. Current index: Issue 2015-07-22 21:02:18,899 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 3% complete. Current index: Issue 2015-07-22 21:02:18,945 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 4% complete. Current index: Issue 2015-07-22 21:02:19,012 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 5% complete. Current index: Issue . . . 2015-07-22 21:02:26,164 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 95% complete. Current index: Issue 2015-07-22 21:02:26,232 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 96% complete. Current index: Issue 2015-07-22 21:02:26,316 indexerPool-2-thread-9 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 97% complete. Current index: Issue 2015-07-22 21:02:26,771 indexerPool-2-thread-3 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: Issue 2015-07-22 21:02:27,261 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 8607ms. Indexer: DefaultIndexManager: paths: [/data/jira3135/indexes/issues, /data/jira3135/indexes/comments] 2015-07-22 21:02:27,263 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: SearchRequest 2015-07-22 21:02:27,268 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,293 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: SearchRequest 2015-07-22 21:02:27,308 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: PortalPage 2015-07-22 21:02:27,312 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,377 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: PortalPage 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 115ms. Indexer: SharedEntityIndexManager: paths: [/data/jira3135/indexes/entities/portalpage, /data/jira3135/indexes/entities/searchrequest] 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All complete. Total time: 8722ms. 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Reindexing all data in JIRA to include Favourites.' succeeded 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 326 2015-07-22 21:02:27,397 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade succeeded! Setting data build number to 360 2015-07-22 21:02:27,469 JiraQuartzScheduler_Worker-0 WARN [service.services.export.ExportService] Backup directory /data/jira_3_12/backup does not exist {noformat} {warning:title=Paths} It appears that the upgraded JIRA will still look for the attachments and the backup locations in the original places. So I created /data/jira_3_12/backup and untarred the original attachments to /data/jira_3_12 and then everything worked (including attachements) in the new JIRA. {warning} ## (/) I then used the upgraded JIRA to generate a new XML backup and stored it in /data/original/3.13.5 along with another tar of the files in /data/jira_3_12/attachments. ## (/) I then shutdown the JIRA server. *I should be ready to move on to version 4 upgrade WHEW* ## So, before moving on, I decided that it would be a really good idea to spin up a new Crowd instance to get rid of the :8443 in the URL and to move off of RedHat per IS requests. I have a ticket in for a new VM and a new database to try to get this going. I am waiting on that before moving on. ## (/) Pat created the VM and Neil created the database. ## (/) I logged into auth.mbari.org (name of the VM) and downloaded crowd which I unzipped to the /opt directory ## (/) I then created a /data/crowd directory and gave my account permissions on it and then edited the /opt/atlassian..../crowd-webapp/WEB-INF/classes/crowd-init.properties file to set that as the crowd home directory. ## (/) The instructions say to download the JDBC driver, but they already have JTDS 1.2.7 in the download so I did not do anything. ## (/) You have to manually connect up CrowdID to a database as they setup wizard does not currently do this. ### (/) They say to download the driver, but again 1.2.7 was there so I did nothing. ### (/) I edited the /opt/atlassian.../apache-tomcat/conf/Catalina/localhost/openidserver.xml to look like: {noformat} {noformat} ### (/) I edited the /opt/atlassian.../build.properties files to look like: {noformat} # Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See https://confluence.atlassian.com/display/CROWD/Connecting+Crowd+to+a+Database hibernate.dialect=org.hibernate.dialect.SQLServerDialect # The Hibernate transaction factory to use. See https://confluence.atlassian.com/display/CROWD/Configuring+Crowd hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory # The http port you wish to run crowd from, ie: http://localhost:8095/crowd crowd.tomcat.connector.port=8095 # Tomcat requires a unique port for shutdown crowd.tomcat.shutdown.port=8020 # Crowd context root crowd.url=http://localhost:8095/crowd # Demo context root demo.url=http://localhost:8095/demo # OpenID server context root openidserver.url=http://localhost:8095/openidserver {noformat} ### (/) I then ran the build.sh script in the root of /opt/atlassian... ## (/) I fired up crowd using the /opt/atlassian.../start_crowd.sh script ## (/) I then went to http://auth.mbari.org:8095/crowd to kick off the start up wizard ## (/) I grabbed a new eval license from my account on atlassian and pasted into the license page. ## (/) I selected "New install" on the next page. ## (/) I configured the JDBC connection using this connection URL with user DB_Collaboration {noformat} jdbc:jtds:sqlserver://dione.mbari.org:51001/Crowd;domain=SHORE;useNTLMv2=TRUE {noformat} ## (/) I left the "Options" as they came up {warning:title=Paths} Not sure if this is a problem, but because I started the set up using auth.mbari.org, it set the Base URL to http://auth.mbari.org:8095/crowd instead of localhost. Hope that is not a problem. We will see. {warning} ## (/) I configured the email connection using the settings from [here|https://wind.shore.mbari.org/is/howto/email/mbarimail/imap] and I used my network login (probably shouldn't be doing that ... not sure where it stores my password, but I am assuming in the DB). ## (/) For the local admin account, I created a user named 'crowdadm' so it would not clash with my LDAP account. See Kevin Gomes for password information. ## (/) I checked the OpenID server as an integrated application ## (/) It then took me to the login page and I logged in using the newly minted admin account. Seemed all is well so far. ## (/) I visited the openidserver URL as well and that seemed OK. ## (/) I decided to wait on configuring the MBARI LDAP directory until I got everything with SSL working. ## (/) Now the next step was to follow the directions to configure Crowd to run over SSL found [here|https://confluence.atlassian.com/display/CROWD/Configuring+Crowd+to+Work+with+SSL] ## (/) I shutdown crowd. Note that the stop script does not shutdown things correctly and I noticed the crowd app running as root. That should not be if I started as kgomes. Not sure what is up with that. ## (/) Now Joe had already configured SSL once, so I used his connector configuration in the server.xml file and so the final file looked like: {noformat} {noformat} ## (/) I then edited the /data/crowd/crowd.properties to look like: {noformat} #Sat Aug 01 09:05:15 PDT 2015 session.lastvalidation=session.lastvalidation session.tokenkey=session.tokenkey crowd.server.url=https\://auth.mbari.org\:8443/crowd/services/ application.name=crowd http.timeout=30000 session.isauthenticated=session.isauthenticated application.login.url=https\://auth.mbari.org\:8443/crowd/console/ session.validationinterval=0 application.password=Y1Xp3OorCmsOP4eruL1dmH {noformat} ## (/) Per the instructions on the atlassian page (referenced above), I also edited the build.properties file and the /client/conf/crowd.properties files before I restarted and used the SSL URLs ## build.properties: {noformat} # Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See https://confluence.atlassian.com/display/CROWD/Connecting+Crowd+to+a+Database hibernate.dialect=org.hibernate.dialect.SQLServerDialect # The Hibernate transaction factory to use. See https://confluence.atlassian.com/display/CROWD/Configuring+Crowd hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory # The http port you wish to run crowd from, ie: http://localhost:8095/crowd crowd.tomcat.connector.port=8095 # Tomcat requires a unique port for shutdown crowd.tomcat.shutdown.port=8020 # Crowd context root crowd.url=https://auth.mbari.org:8443/crowd # Demo context root demo.url=https://auth.mbari.org:8443/demo # OpenID server context root openidserver.url=https://auth.mbari.org:8443/openidserver {noformat} ## crowd.properties (client) {noformat} application.name crowd application.password password application.login.url https://auth.mbari.org:8443/crowd/console/ crowd.server.url https://auth.mbari.org:8443/crowd/services/ crowd.base.url https://auth.mbari.org:8443/crowd/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 2 session.lastvalidation session.lastvalidation {noformat} ## (/) Although not stated, I am assuming you would need to run the build.sh script to push the build.properties changes to their proper places, so I did that. Note that before doing that, I know that it will clobber the server.xml changes I made, so I made a copy of that file and diff'd them after and then rolled the previous changes to the new server.xml file. Actually, amazingly enough, it seems to have done the connector entry correctly so I left it after running the build.sh script. ## (/) Crossed my fingers and then restarted crowd. I tailed the catalina.out file and did not see any stack traces so that is a good sign! ## (/) I visited https://auth.mbari.org:8443/crowd first. It could not find that page, but I suspect that is because I am browsing from the outside, so I tried just https://auth.mbari.org/crowd and got a service unavailable. I am suspecting that this is a combination of firewall and proxy pass and I will update the trouble ticket and have Joe take a look. From what I can see on the crowd side, it seems like the server started cleanly, we just can't get to it. I tried to reach it from a browser on the machine itself too (through VNC) with the same service not available. ]]> 27558129 27590892 4.4: [https://confluence.atlassian.com/display/JIRA044/Migrating+JIRA+to+Another+Server] ## The JIRA configuration tool: [https://confluence.atlassian.com/display/JIRA044/Using+the+JIRA+Configuration+Tool] h5. Steps # (/) Create new VM named bugs.mbari.org in the DMZ # (/) Have Neil create database Jira_Temp on solstice2.shore.mbari.org # (/) Have Neil create database Jira on solstice2.shore.mbari.org # (/) Have Pat install Java 7 on bugs.shore.mbari.org # (/) Have Pete plumb holes through firewall so processes on bugs.mbari.org can get to Solstice2 # (/) Have Pat create DB_Collaboration account on bugs so it can run JIRA under that account and it can connect to solstice2 using that NT Domain account. # (/) Upgrade license on Atlassian site # (/) Log into bugs.shore.mbari.org # (/) Download 3.13.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 4.4.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 5.2.11 standalone Linux 64 bit tar.gz (not sure this version is necessary, but at least I have it) # (/) Unzip and untar the file to /opt # (/) Download latest JIRA (6.4.7 as of this writing). # (/) Unzip and untar it to /opt # Performed Test Upgrade ## (/) In order to export the current stuff in JIRA, I had to shut off access so people could not change the data while I was backing it up. ## (/) I ssh'd to oceana.mbari.org as root and edited the /opt/jira/conf/server.xml file and commented out the Connector section that had the port of 8010 to shut it off from the normal serving route. ## (/) I uncommented the 8082 port connector and the 8443 port connector so that I could still get to the server. ## (/) I stopped and started the JIRA server and in the log file I got a "keystore was tampered with..." which is not surprising. ## (/) I could then browser over to http://oceana.mbari.org:8082/jira ## (/) Then through the Administration console, I did an XML backup ## (/) I then created a tar of all the attachments in the /data/jira_3_12/attachments directory ## (/) I moved both the XML and tar files to the /root/jira-upgrade directory ## (/) I then reversed the changes to the server.xml file and shut down JIRA ## (/) I left it down during the next steps in case it went so well, I could just point people to the new server (yeah, right). ## (/) I then browsed to the crowd server on oceana and add a new application using: ### URL: http://bugs.mbari.org/jira3135 ### IP: 134.89.2.29 ### Name: JIRA3135 ### Password: (ask Kevin) :) ## (/) On bugs, I made a copy of the JIRA 3.13.5 download in the /opt directory and unzipped and untarred it. ## (/) In order to configure the crowd connection I did the following: ### (/) I scp'd the /opt/crowd/client/crowd-integration-client-1.6.jar file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I removed the existing 1.6.1 crowd client jar from the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I scp'd the /opt/crowd/client/conf/crowd.properties file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I scp'd the /opt/crowd/client/conf/crowd-ehcache.xml file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I edited the crowd.properties file on bugs to look like: {noformat} application.name JIRA3135 application.password (ask Kevin) application.login.url http://oceana.mbari.org:8095/crowd/console/ crowd.server.url http://oceana.mbari.org:8095/crowd/services/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 0 session.lastvalidation session.lastvalidation {noformat} ### (/) I edited the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/osuser.xml file to comment out the current authentication mechanism and then uncomment the crowd one. ## (/) I then edited the /opt/atlassian-jira-standalone-3.13.5/conf/server/xml file and configured the database connection to the Jira_Temp database on Solstice2. I looked like this: {noformat} {noformat} ## (/) Edit the /opt/atlassian/jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/entityengine.xml and changed it from 'hsql' to 'mssql' and delete the line with "PUBLIC" in it per the instructions in the comments in that file. ## (/) I edited the /etc/httpd/conf/httpd.conf file and created a proxy pass at the bottom of the file to point a normal URL to the default port 8080 for JIRA: {noformat} # Proxy Pass for JIRA ProxyPass http://bugs.mbari.org:8080 ProxyPassReverse http://bugs.mbari.org:8080 {noformat} ## (/) I restarted Apache ## (/) I scp'd the jtds driver from oceana to the /opt/atlassian-jira-standalone-3.13.5/common/lib directory (you could down from the internet) ## (/) I then went to the /opt/atlassian-jira-standalone-3.13.5/ directory and ran './bin/startup.sh'. From the log file, I could tell things were hanging. After some troubleshooting I am wondering if the local firewall is preventing the application to get access to the database on solstice2. I can telnet to port 1433, but I can't browse to the base http://bugs.mbari.org from anywhere but the local web browser. I have submitted a ticket. ## (/) I restarted the old JIRA with my hopes dashed :(. ## (/) Pat disabled the firewall on bugs.mbari.org but it still hung trying to connect to solstice2.shore.mbari.org. That is really, really perplexing. Neil mentioned that solstice2 is using Kerberos and solstice is not. Checking with the JTDS docs, version 1.3.1 of the driver added kerberos support, so I downloaded that driver and added the 'userKerberos=true' property to the URL in the server.xml file and restarted. Got an error about no credentials, so added user and password properties to the URL. Nope, no luck. Never did figure this one out, but I had Pat pull the VM inside the firewall and after some thrash it worked. Well, it sort of worked ... sigh. It turns out I had downloaded the standard version instead of the enterprise version. I need to redo this work ... grrr. ## (/) I deleted all the tables in the Jira_Temp database and removed the /data/jira3135/indexes directory (and recreated). ## (/) I downloaded the enterprise version of the 3.13.5 server. I made a copy in the /opt directory and unzipped and untarred the file. ## (/) I went back to crowd and edited the application to change the properties to: ### URL: http://bugs.shore.mbari.org:8080 ### IP: 134.89.12.31 ### Name: jira3135 ### Password: (ask Kevin) :) ## (/) I then repeated the steps above to get the server up and running with the following differences: ### The server name is now bugs.shore.mbari.org ### The paths given above are a little different in that they no longer say "standard" but say "enterprise" ### I deleted the proxy pass as it seemed to have issues before and this is only temporary anyway. ## (/) I then browsed to http://bugs.shore.mbari.org:8080 ## (/) It took me to the start up page and at the top was the option to 'import your existing data'. Seemed too good not to try. I clicked on the link. It asked me for the backup file location and the location where the indexes would be stored. ## (/) I copied the XML zip file and the attachments tar file to the /data/original directory. ## (/) I created the /data/jira3135/indexes and used those directories ... it fired off the import and I waited. ## (/) I tailed the log file to watch the import. Holy crap, it worked!!! I could log in and everything! I copied the results from the log file here for posterity sake: {noformat} 2015-07-22 20:55:45,156 http-8080-Processor22 INFO [jira.action.admin.DataImport] Running data import 2015-07-22 20:55:45,179 http-8080-Processor22 INFO [jira.action.admin.DataImport] Importing data.. 2015-07-22 20:55:45,186 http-8080-Processor22 INFO [jira.action.admin.DataImport] Start parsing XML with SAX Parser 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] XML successfully parsed 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] Removing all entries from the database. 2015-07-22 20:56:24,593 http-8080-Processor22 INFO [jira.action.admin.DataImport] All entries removed. 2015-07-22 20:56:24,594 http-8080-Processor22 INFO [jira.action.admin.DataImport] Started storing 410414 Generic Values 2015-07-22 21:01:51,967 http-8080-Processor22 INFO [jira.action.admin.DataImport] Finished storing Generic Values 2015-07-22 21:01:52,329 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:52,361 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:54,683 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLink' to module 'jira.user.format:profile-link-user-format'. 2015-07-22 21:01:54,724 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullName' to module 'jira.user.format:full-name-user-format'. 2015-07-22 21:01:54,773 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkSearcher' to module 'jira.user.format:profile-link-searcher-user-format'. 2015-07-22 21:01:54,784 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkExternal' to module 'jira.user.format:profile-link-external-user-format'. 2015-07-22 21:01:54,795 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkActionHeader' to module 'jira.user.format:profile-link-action-header-user-format'. 2015-07-22 21:01:54,807 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullProfile' to module 'jira.user.format:full-profile-user-format'. 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/comments 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/issues 2015-07-22 21:01:55,641 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/plugins 2015-07-22 21:01:55,867 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:01:55,871 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/issues does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:55,873 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/comments does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,033 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,257 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,889 http-8080-Processor22 ERROR [atlassian.jira.upgrade.ConsistencyCheckImpl] Attachments are turned on, but attachment path [/data/jira_3_12/attachments] invalid - disabling attachments 2015-07-22 21:02:13,904 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Detected that an upgrade is needed; existing data at build 299 2015-07-22 21:02:13,907 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Doing Upgrade... 2015-07-22 21:02:13,915 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value' succeeded 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 317 2015-07-22 21:02:13,944 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite filters - make each filter a favourite of its owner. 2015-07-22 21:02:17,822 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build319] Could not find author 'fpy' for filter with id '10040' 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite filters - make each filter a favourite of its owner.' succeeded 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 319 2015-07-22 21:02:17,995 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise Share Permissions. Move old shares to new shares. 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise Share Permissions. Move old shares to new shares.' succeeded 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 321 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Migrating the old JIRA UI colors to the new JIRA 3.13 colors 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build322] Custom color detected for jira.lf.menu.bgcolour : #336699 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Migrating the old JIRA UI colors to the new JIRA 3.13 colors' succeeded 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 322 2015-07-22 21:02:18,025 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite dashboards - make each dashboard a favourite of its owner. 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'cmcgann' for dashboard with id '10030' 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'fpy' for dashboard with id '10060' 2015-07-22 21:02:18,423 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'kanna' for dashboard with id '10040' 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite dashboards - make each dashboard a favourite of its owner.' succeeded 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 325 2015-07-22 21:02:18,625 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Reindexing all data in JIRA to include Favourites. 2015-07-22 21:02:18,648 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All starting... 2015-07-22 21:02:18,650 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 0% complete. Current index: Issue 2015-07-22 21:02:18,654 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:02:18,809 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 1% complete. Current index: Issue 2015-07-22 21:02:18,855 indexerPool-2-thread-10 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 2% complete. Current index: Issue 2015-07-22 21:02:18,899 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 3% complete. Current index: Issue 2015-07-22 21:02:18,945 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 4% complete. Current index: Issue 2015-07-22 21:02:19,012 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 5% complete. Current index: Issue . . . 2015-07-22 21:02:26,164 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 95% complete. Current index: Issue 2015-07-22 21:02:26,232 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 96% complete. Current index: Issue 2015-07-22 21:02:26,316 indexerPool-2-thread-9 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 97% complete. Current index: Issue 2015-07-22 21:02:26,771 indexerPool-2-thread-3 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: Issue 2015-07-22 21:02:27,261 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 8607ms. Indexer: DefaultIndexManager: paths: [/data/jira3135/indexes/issues, /data/jira3135/indexes/comments] 2015-07-22 21:02:27,263 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: SearchRequest 2015-07-22 21:02:27,268 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,293 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: SearchRequest 2015-07-22 21:02:27,308 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: PortalPage 2015-07-22 21:02:27,312 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,377 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: PortalPage 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 115ms. Indexer: SharedEntityIndexManager: paths: [/data/jira3135/indexes/entities/portalpage, /data/jira3135/indexes/entities/searchrequest] 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All complete. Total time: 8722ms. 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Reindexing all data in JIRA to include Favourites.' succeeded 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 326 2015-07-22 21:02:27,397 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade succeeded! Setting data build number to 360 2015-07-22 21:02:27,469 JiraQuartzScheduler_Worker-0 WARN [service.services.export.ExportService] Backup directory /data/jira_3_12/backup does not exist {noformat} {warning:title=Paths} It appears that the upgraded JIRA will still look for the attachments and the backup locations in the original places. So I created /data/jira_3_12/backup and untarred the original attachments to /data/jira_3_12 and then everything worked (including attachements) in the new JIRA. {warning} ## (/) I then used the upgraded JIRA to generate a new XML backup and stored it in /data/original/3.13.5 along with another tar of the files in /data/jira_3_12/attachments. ## (/) I then shutdown the JIRA server. *I should be ready to move on to version 4 upgrade WHEW* ## So, before moving on, I decided that it would be a really good idea to spin up a new Crowd instance to get rid of the :8443 in the URL and to move off of RedHat per IS requests. I have a ticket in for a new VM and a new database to try to get this going. I am waiting on that before moving on. ## (/) Pat created the VM and Neil created the database. ## (/) I logged into auth.mbari.org (name of the VM) and downloaded crowd which I unzipped to the /opt directory ## (/) I then created a /data/crowd directory and gave my account permissions on it and then edited the /opt/atlassian..../crowd-webapp/WEB-INF/classes/crowd-init.properties file to set that as the crowd home directory. ## (/) The instructions say to download the JDBC driver, but they already have JTDS 1.2.7 in the download so I did not do anything. ## (/) You have to manually connect up CrowdID to a database as they setup wizard does not currently do this. ### (/) They say to download the driver, but again 1.2.7 was there so I did nothing. ### (/) I edited the /opt/atlassian.../apache-tomcat/conf/Catalina/localhost/openidserver.xml to look like: {noformat} {noformat} ### (/) I edited the /opt/atlassian.../build.properties files to look like: {noformat} # Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See https://confluence.atlassian.com/display/CROWD/Connecting+Crowd+to+a+Database hibernate.dialect=org.hibernate.dialect.SQLServerDialect # The Hibernate transaction factory to use. See https://confluence.atlassian.com/display/CROWD/Configuring+Crowd hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory # The http port you wish to run crowd from, ie: http://localhost:8095/crowd crowd.tomcat.connector.port=8095 # Tomcat requires a unique port for shutdown crowd.tomcat.shutdown.port=8020 # Crowd context root crowd.url=http://localhost:8095/crowd # Demo context root demo.url=http://localhost:8095/demo # OpenID server context root openidserver.url=http://localhost:8095/openidserver {noformat} ### (/) I then ran the build.sh script in the root of /opt/atlassian... ## (/) I fired up crowd using the /opt/atlassian.../start_crowd.sh script ## (/) I then went to http://auth.mbari.org:8095/crowd to kick off the start up wizard ## (/) I grabbed a new eval license from my account on atlassian and pasted into the license page. ## (/) I selected "New install" on the next page. ## (/) I configured the JDBC connection using this connection URL with user DB_Collaboration {noformat} jdbc:jtds:sqlserver://dione.mbari.org:51001/Crowd;domain=SHORE;useNTLMv2=TRUE {noformat} ## (/) I left the "Options" as they came up {warning:title=Paths} Not sure if this is a problem, but because I started the set up using auth.mbari.org, it set the Base URL to http://auth.mbari.org:8095/crowd instead of localhost. Hope that is not a problem. We will see. {warning} ## (/) I configured the email connection using the settings from [here|https://wind.shore.mbari.org/is/howto/email/mbarimail/imap] and I used my network login (probably shouldn't be doing that ... not sure where it stores my password, but I am assuming in the DB). ## (/) For the local admin account, I created a user named 'crowdadm' so it would not clash with my LDAP account. See Kevin Gomes for password information. ## (/) I checked the OpenID server as an integrated application ## (/) It then took me to the login page and I logged in using the newly minted admin account. Seemed all is well so far. ## (/) I visited the openidserver URL as well and that seemed OK. ## (/) I decided to wait on configuring the MBARI LDAP directory until I got everything with SSL working. ## (/) Now the next step was to follow the directions to configure Crowd to run over SSL found [here|https://confluence.atlassian.com/display/CROWD/Configuring+Crowd+to+Work+with+SSL] ## (/) I shutdown crowd. Note that the stop script does not shutdown things correctly and I noticed the crowd app running as root. That should not be if I started as kgomes. Not sure what is up with that. ## (/) Now Joe had already configured SSL once, so I used his connector configuration in the server.xml file and so the final file looked like: {noformat} {noformat} ## (/) I then edited the /data/crowd/crowd.properties to look like: {noformat} #Sat Aug 01 09:05:15 PDT 2015 session.lastvalidation=session.lastvalidation session.tokenkey=session.tokenkey crowd.server.url=https\://auth.mbari.org\:8443/crowd/services/ application.name=crowd http.timeout=30000 session.isauthenticated=session.isauthenticated application.login.url=https\://auth.mbari.org\:8443/crowd/console/ session.validationinterval=0 application.password=Y1Xp3OorCmsOP4eruL1dmH {noformat} ## (/) Per the instructions on the atlassian page (referenced above), I also edited the build.properties file and the /client/conf/crowd.properties files before I restarted and used the SSL URLs ## build.properties: {noformat} # Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See https://confluence.atlassian.com/display/CROWD/Connecting+Crowd+to+a+Database hibernate.dialect=org.hibernate.dialect.SQLServerDialect # The Hibernate transaction factory to use. See https://confluence.atlassian.com/display/CROWD/Configuring+Crowd hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory # The http port you wish to run crowd from, ie: http://localhost:8095/crowd crowd.tomcat.connector.port=8095 # Tomcat requires a unique port for shutdown crowd.tomcat.shutdown.port=8020 # Crowd context root crowd.url=https://auth.mbari.org:8443/crowd # Demo context root demo.url=https://auth.mbari.org:8443/demo # OpenID server context root openidserver.url=https://auth.mbari.org:8443/openidserver {noformat} ## crowd.properties (client) {noformat} application.name crowd application.password password application.login.url https://auth.mbari.org:8443/crowd/console/ crowd.server.url https://auth.mbari.org:8443/crowd/services/ crowd.base.url https://auth.mbari.org:8443/crowd/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 2 session.lastvalidation session.lastvalidation {noformat} ## (/) Although not stated, I am assuming you would need to run the build.sh script to push the build.properties changes to their proper places, so I did that. Note that before doing that, I know that it will clobber the server.xml changes I made, so I made a copy of that file and diff'd them after and then rolled the previous changes to the new server.xml file. Actually, amazingly enough, it seems to have done the connector entry correctly so I left it after running the build.sh script. ## (/) Crossed my fingers and then restarted crowd. # Schedule upgrade date and send all hands several days in advance. # When the day arrives, send all hands announcing JIRA outage. # From the Administrator's page in our existing JIRA, perform a 'Backup Data to XML'. # Login to oceana.mbari.org as root. # Shutdown JIRA # Create a tar.gz of the /opt/atlassian-jira-enterprise-3.12.1-standalone directory # Clean up the /data/jira_3_12/backups directory by deleting all but maybe the last 5 backups. # Create a tar.gz of the JIRA home directory on ocean.mbari.org which is located at /data/jira_3_12 # scp both tar.gz files to bugs.mbari.org # login to bugs.mbari.org # Unpack the home directory tar to /data/jira # Run the installer as root (this might need IS help or sudo privs). Note that we usually install the application to /opt # Run the JIRA Configuration tool to set the jira.home to the /data/jira location # Connect to JIRA_Temp database on Solstice2 (.... more to do here, see Atlassian docs) # Migrate existing configuration over to new JIRA (I need to add more here as we added Crowd). # Start JIRA # Import backed up XML # Perform post upgrades checks and tests *Need to document steps for 4.4.5->6.X*]]> 27558127 27590890 4.4: [https://confluence.atlassian.com/display/JIRA044/Migrating+JIRA+to+Another+Server] ## The JIRA configuration tool: [https://confluence.atlassian.com/display/JIRA044/Using+the+JIRA+Configuration+Tool] h5. Steps # (/) Create new VM named bugs.mbari.org in the DMZ # (/) Have Neil create database Jira_Temp on solstice2.shore.mbari.org # (/) Have Neil create database Jira on solstice2.shore.mbari.org # (/) Have Pat install Java 7 on bugs.shore.mbari.org # (/) Have Pete plumb holes through firewall so processes on bugs.mbari.org can get to Solstice2 # (/) Have Pat create DB_Collaboration account on bugs so it can run JIRA under that account and it can connect to solstice2 using that NT Domain account. # (/) Upgrade license on Atlassian site # (/) Log into bugs.shore.mbari.org # (/) Download 3.13.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 4.4.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 5.2.11 standalone Linux 64 bit tar.gz (not sure this version is necessary, but at least I have it) # (/) Unzip and untar the file to /opt # (/) Download latest JIRA (6.4.7 as of this writing). # (/) Unzip and untar it to /opt # Performed Test Upgrade ## (/) In order to export the current stuff in JIRA, I had to shut off access so people could not change the data while I was backing it up. ## (/) I ssh'd to oceana.mbari.org as root and edited the /opt/jira/conf/server.xml file and commented out the Connector section that had the port of 8010 to shut it off from the normal serving route. ## (/) I uncommented the 8082 port connector and the 8443 port connector so that I could still get to the server. ## (/) I stopped and started the JIRA server and in the log file I got a "keystore was tampered with..." which is not surprising. ## (/) I could then browser over to http://oceana.mbari.org:8082/jira ## (/) Then through the Administration console, I did an XML backup ## (/) I then created a tar of all the attachments in the /data/jira_3_12/attachments directory ## (/) I moved both the XML and tar files to the /root/jira-upgrade directory ## (/) I then reversed the changes to the server.xml file and shut down JIRA ## (/) I left it down during the next steps in case it went so well, I could just point people to the new server (yeah, right). ## (/) I then browsed to the crowd server on oceana and add a new application using: ### URL: http://bugs.mbari.org/jira3135 ### IP: 134.89.2.29 ### Name: JIRA3135 ### Password: (ask Kevin) :) ## (/) On bugs, I made a copy of the JIRA 3.13.5 download in the /opt directory and unzipped and untarred it. ## (/) In order to configure the crowd connection I did the following: ### (/) I scp'd the /opt/crowd/client/crowd-integration-client-1.6.jar file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I removed the existing 1.6.1 crowd client jar from the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I scp'd the /opt/crowd/client/conf/crowd.properties file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I scp'd the /opt/crowd/client/conf/crowd-ehcache.xml file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I edited the crowd.properties file on bugs to look like: {noformat} application.name JIRA3135 application.password (ask Kevin) application.login.url http://oceana.mbari.org:8095/crowd/console/ crowd.server.url http://oceana.mbari.org:8095/crowd/services/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 0 session.lastvalidation session.lastvalidation {noformat} ### (/) I edited the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/osuser.xml file to comment out the current authentication mechanism and then uncomment the crowd one. ## (/) I then edited the /opt/atlassian-jira-standalone-3.13.5/conf/server/xml file and configured the database connection to the Jira_Temp database on Solstice2. I looked like this: {noformat} {noformat} ## (/) Edit the /opt/atlassian/jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/entityengine.xml and changed it from 'hsql' to 'mssql' and delete the line with "PUBLIC" in it per the instructions in the comments in that file. ## (/) I edited the /etc/httpd/conf/httpd.conf file and created a proxy pass at the bottom of the file to point a normal URL to the default port 8080 for JIRA: {noformat} # Proxy Pass for JIRA ProxyPass http://bugs.mbari.org:8080 ProxyPassReverse http://bugs.mbari.org:8080 {noformat} ## (/) I restarted Apache ## (/) I scp'd the jtds driver from oceana to the /opt/atlassian-jira-standalone-3.13.5/common/lib directory (you could down from the internet) ## (/) I then went to the /opt/atlassian-jira-standalone-3.13.5/ directory and ran './bin/startup.sh'. From the log file, I could tell things were hanging. After some troubleshooting I am wondering if the local firewall is preventing the application to get access to the database on solstice2. I can telnet to port 1433, but I can't browse to the base http://bugs.mbari.org from anywhere but the local web browser. I have submitted a ticket. ## (/) I restarted the old JIRA with my hopes dashed :(. ## (/) Pat disabled the firewall on bugs.mbari.org but it still hung trying to connect to solstice2.shore.mbari.org. That is really, really perplexing. Neil mentioned that solstice2 is using Kerberos and solstice is not. Checking with the JTDS docs, version 1.3.1 of the driver added kerberos support, so I downloaded that driver and added the 'userKerberos=true' property to the URL in the server.xml file and restarted. Got an error about no credentials, so added user and password properties to the URL. Nope, no luck. Never did figure this one out, but I had Pat pull the VM inside the firewall and after some thrash it worked. Well, it sort of worked ... sigh. It turns out I had downloaded the standard version instead of the enterprise version. I need to redo this work ... grrr. ## (/) I deleted all the tables in the Jira_Temp database and removed the /data/jira3135/indexes directory (and recreated). ## (/) I downloaded the enterprise version of the 3.13.5 server. I made a copy in the /opt directory and unzipped and untarred the file. ## (/) I went back to crowd and edited the application to change the properties to: ### URL: http://bugs.shore.mbari.org:8080 ### IP: 134.89.12.31 ### Name: jira3135 ### Password: (ask Kevin) :) ## (/) I then repeated the steps above to get the server up and running with the following differences: ### The server name is now bugs.shore.mbari.org ### The paths given above are a little different in that they no longer say "standard" but say "enterprise" ### I deleted the proxy pass as it seemed to have issues before and this is only temporary anyway. ## (/) I then browsed to http://bugs.shore.mbari.org:8080 ## (/) It took me to the start up page and at the top was the option to 'import your existing data'. Seemed too good not to try. I clicked on the link. It asked me for the backup file location and the location where the indexes would be stored. ## (/) I copied the XML zip file and the attachments tar file to the /data/original directory. ## (/) I created the /data/jira3135/indexes and used those directories ... it fired off the import and I waited. ## (/) I tailed the log file to watch the import. Holy crap, it worked!!! I could log in and everything! I copied the results from the log file here for posterity sake: {noformat} 2015-07-22 20:55:45,156 http-8080-Processor22 INFO [jira.action.admin.DataImport] Running data import 2015-07-22 20:55:45,179 http-8080-Processor22 INFO [jira.action.admin.DataImport] Importing data.. 2015-07-22 20:55:45,186 http-8080-Processor22 INFO [jira.action.admin.DataImport] Start parsing XML with SAX Parser 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] XML successfully parsed 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] Removing all entries from the database. 2015-07-22 20:56:24,593 http-8080-Processor22 INFO [jira.action.admin.DataImport] All entries removed. 2015-07-22 20:56:24,594 http-8080-Processor22 INFO [jira.action.admin.DataImport] Started storing 410414 Generic Values 2015-07-22 21:01:51,967 http-8080-Processor22 INFO [jira.action.admin.DataImport] Finished storing Generic Values 2015-07-22 21:01:52,329 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:52,361 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:54,683 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLink' to module 'jira.user.format:profile-link-user-format'. 2015-07-22 21:01:54,724 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullName' to module 'jira.user.format:full-name-user-format'. 2015-07-22 21:01:54,773 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkSearcher' to module 'jira.user.format:profile-link-searcher-user-format'. 2015-07-22 21:01:54,784 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkExternal' to module 'jira.user.format:profile-link-external-user-format'. 2015-07-22 21:01:54,795 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkActionHeader' to module 'jira.user.format:profile-link-action-header-user-format'. 2015-07-22 21:01:54,807 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullProfile' to module 'jira.user.format:full-profile-user-format'. 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/comments 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/issues 2015-07-22 21:01:55,641 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/plugins 2015-07-22 21:01:55,867 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:01:55,871 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/issues does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:55,873 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/comments does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,033 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,257 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,889 http-8080-Processor22 ERROR [atlassian.jira.upgrade.ConsistencyCheckImpl] Attachments are turned on, but attachment path [/data/jira_3_12/attachments] invalid - disabling attachments 2015-07-22 21:02:13,904 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Detected that an upgrade is needed; existing data at build 299 2015-07-22 21:02:13,907 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Doing Upgrade... 2015-07-22 21:02:13,915 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value' succeeded 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 317 2015-07-22 21:02:13,944 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite filters - make each filter a favourite of its owner. 2015-07-22 21:02:17,822 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build319] Could not find author 'fpy' for filter with id '10040' 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite filters - make each filter a favourite of its owner.' succeeded 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 319 2015-07-22 21:02:17,995 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise Share Permissions. Move old shares to new shares. 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise Share Permissions. Move old shares to new shares.' succeeded 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 321 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Migrating the old JIRA UI colors to the new JIRA 3.13 colors 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build322] Custom color detected for jira.lf.menu.bgcolour : #336699 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Migrating the old JIRA UI colors to the new JIRA 3.13 colors' succeeded 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 322 2015-07-22 21:02:18,025 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite dashboards - make each dashboard a favourite of its owner. 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'cmcgann' for dashboard with id '10030' 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'fpy' for dashboard with id '10060' 2015-07-22 21:02:18,423 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'kanna' for dashboard with id '10040' 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite dashboards - make each dashboard a favourite of its owner.' succeeded 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 325 2015-07-22 21:02:18,625 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Reindexing all data in JIRA to include Favourites. 2015-07-22 21:02:18,648 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All starting... 2015-07-22 21:02:18,650 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 0% complete. Current index: Issue 2015-07-22 21:02:18,654 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:02:18,809 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 1% complete. Current index: Issue 2015-07-22 21:02:18,855 indexerPool-2-thread-10 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 2% complete. Current index: Issue 2015-07-22 21:02:18,899 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 3% complete. Current index: Issue 2015-07-22 21:02:18,945 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 4% complete. Current index: Issue 2015-07-22 21:02:19,012 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 5% complete. Current index: Issue . . . 2015-07-22 21:02:26,164 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 95% complete. Current index: Issue 2015-07-22 21:02:26,232 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 96% complete. Current index: Issue 2015-07-22 21:02:26,316 indexerPool-2-thread-9 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 97% complete. Current index: Issue 2015-07-22 21:02:26,771 indexerPool-2-thread-3 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: Issue 2015-07-22 21:02:27,261 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 8607ms. Indexer: DefaultIndexManager: paths: [/data/jira3135/indexes/issues, /data/jira3135/indexes/comments] 2015-07-22 21:02:27,263 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: SearchRequest 2015-07-22 21:02:27,268 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,293 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: SearchRequest 2015-07-22 21:02:27,308 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: PortalPage 2015-07-22 21:02:27,312 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,377 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: PortalPage 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 115ms. Indexer: SharedEntityIndexManager: paths: [/data/jira3135/indexes/entities/portalpage, /data/jira3135/indexes/entities/searchrequest] 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All complete. Total time: 8722ms. 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Reindexing all data in JIRA to include Favourites.' succeeded 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 326 2015-07-22 21:02:27,397 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade succeeded! Setting data build number to 360 2015-07-22 21:02:27,469 JiraQuartzScheduler_Worker-0 WARN [service.services.export.ExportService] Backup directory /data/jira_3_12/backup does not exist {noformat} {warning:title=Paths} It appears that the upgraded JIRA will still look for the attachments and the backup locations in the original places. So I created /data/jira_3_12/backup and untarred the original attachments to /data/jira_3_12 and then everything worked (including attachements) in the new JIRA. {warning} ## (/) I then used the upgraded JIRA to generate a new XML backup and stored it in /data/original/3.13.5 along with another tar of the files in /data/jira_3_12/attachments. ## (/) I then shutdown the JIRA server. *I should be ready to move on to version 4 upgrade WHEW* ## So, before moving on, I decided that it would be a really good idea to spin up a new Crowd instance to get rid of the :8443 in the URL and to move off of RedHat per IS requests. I have a ticket in for a new VM and a new database to try to get this going. I am waiting on that before moving on. ## (/) Pat created the VM and Neil created the database. ## (/) I logged into auth.mbari.org (name of the VM) and downloaded crowd which I unzipped to the /opt directory ## (/) I then created a /data/crowd directory and gave my account permissions on it and then edited the /opt/atlassian..../crowd-webapp/WEB-INF/classes/crowd-init.properties file to set that as the crowd home directory. ## (/) The instructions say to download the JDBC driver, but they already have JTDS 1.2.7 in the download so I did not do anything. ## (/) You have to manually connect up CrowdID to a database as they setup wizard does not currently do this. ### (/) They say to download the driver, but again 1.2.7 was there so I did nothing. ### (/) I edited the /opt/atlassian.../apache-tomcat/conf/Catalina/localhost/openidserver.xml to look like: {noformat} {noformat} ### (/) I edited the /opt/atlassian.../build.properties files to look like: {noformat} # Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See https://confluence.atlassian.com/display/CROWD/Connecting+Crowd+to+a+Database hibernate.dialect=org.hibernate.dialect.SQLServerDialect # The Hibernate transaction factory to use. See https://confluence.atlassian.com/display/CROWD/Configuring+Crowd hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory # The http port you wish to run crowd from, ie: http://localhost:8095/crowd crowd.tomcat.connector.port=8095 # Tomcat requires a unique port for shutdown crowd.tomcat.shutdown.port=8020 # Crowd context root crowd.url=http://localhost:8095/crowd # Demo context root demo.url=http://localhost:8095/demo # OpenID server context root openidserver.url=http://localhost:8095/openidserver {noformat} ### (/) I then ran the build.sh script in the root of /opt/atlassian... ## (/) I fired up crowd using the /opt/atlassian.../start_crowd.sh script ## (/) I then went to http://auth.mbari.org:8095/crowd to kick off the start up wizard ## (/) I grabbed a new eval license from my account on atlassian and pasted into the license page. ## (/) I selected "New install" on the next page. ## (/) I configured the JDBC connection using this connection URL with user DB_Collaboration {noformat} jdbc:jtds:sqlserver://dione.mbari.org:51001/Crowd;domain=SHORE;useNTLMv2=TRUE {noformat} ## (/) I left the "Options" as they came up {warning:title=Paths} Not sure if this is a problem, but because I started the set up using auth.mbari.org, it set the Base URL to http://auth.mbari.org:8095/crowd instead of localhost. Hope that is not a problem. We will see. {warning} ## (/) I configured the email connection using the settings from [here|https://wind.shore.mbari.org/is/howto/email/mbarimail/imap] and I used my network login (probably shouldn't be doing that ... not sure where it stores my password, but I am assuming in the DB). ## (/) For the local admin account, I created a user named 'crowdadm' so it would not clash with my LDAP account. See Kevin Gomes for password information. ## (/) I checked the OpenID server as an integrated application ## (/) It then took me to the login page and I logged in using the newly minted admin account. Seemed all is well so far. ## (/) I visited the openidserver URL as well and that seemed OK. ## (/) I decided to wait on configuring the MBARI LDAP directory until I got everything with SSL working. ## (/) Now the next step was to follow the directions to configure Crowd to run over SSL found [here|https://confluence.atlassian.com/display/CROWD/Configuring+Crowd+to+Work+with+SSL] ## (/) I shutdown crowd. Note that the stop script does not shutdown things correctly and I noticed the crowd app running as root. That should not be if I started as kgomes. Not sure what is up with that. ## (/) Now Joe had already configured SSL once, so I used his connector configuration in the server.xml file and so the final file looked like: {noformat} {noformat} ## (/) I then edited the /data/crowd/crowd.properties to look like: {noformat} #Sat Aug 01 09:05:15 PDT 2015 session.lastvalidation=session.lastvalidation session.tokenkey=session.tokenkey crowd.server.url=https\://auth.mbari.org\:8443/crowd/services/ application.name=crowd http.timeout=30000 session.isauthenticated=session.isauthenticated application.login.url=https\://auth.mbari.org\:8443/crowd/console/ session.validationinterval=0 application.password=Y1Xp3OorCmsOP4eruL1dmH {noformat} ## (/) Per the instructions on the atlassian page (referenced above), I also edited the build.properties file and the /client/conf/crowd.properties files before I restarted and used the SSL URLs ## build.properties: {noformat} # Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See https://confluence.atlassian.com/display/CROWD/Connecting+Crowd+to+a+Database hibernate.dialect=org.hibernate.dialect.SQLServerDialect # The Hibernate transaction factory to use. See https://confluence.atlassian.com/display/CROWD/Configuring+Crowd hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory # The http port you wish to run crowd from, ie: http://localhost:8095/crowd crowd.tomcat.connector.port=8095 # Tomcat requires a unique port for shutdown crowd.tomcat.shutdown.port=8020 # Crowd context root crowd.url=https://auth.mbari.org:8443/crowd # Demo context root demo.url=https://auth.mbari.org:8443/demo # OpenID server context root openidserver.url=https://auth.mbari.org:8443/openidserver {noformat} ## crowd.properties (client) {noformat} application.name crowd application.password password application.login.url https://auth.mbari.org:8443/crowd/console/ crowd.server.url https://auth.mbari.org:8443/crowd/services/ crowd.base.url https://auth.mbari.org:8443/crowd/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 2 session.lastvalidation session.lastvalidation {noformat} ## (/) Although not stated, I am assuming you would need to run the build.sh script to push the build.properties changes to their proper places, so I did that. Note that before doing that, I know that it will clobber the server.xml changes I made, so I made a copy of that file and diff'd them after and then rolled the previous changes to the new server.xml file. # Schedule upgrade date and send all hands several days in advance. # When the day arrives, send all hands announcing JIRA outage. # From the Administrator's page in our existing JIRA, perform a 'Backup Data to XML'. # Login to oceana.mbari.org as root. # Shutdown JIRA # Create a tar.gz of the /opt/atlassian-jira-enterprise-3.12.1-standalone directory # Clean up the /data/jira_3_12/backups directory by deleting all but maybe the last 5 backups. # Create a tar.gz of the JIRA home directory on ocean.mbari.org which is located at /data/jira_3_12 # scp both tar.gz files to bugs.mbari.org # login to bugs.mbari.org # Unpack the home directory tar to /data/jira # Run the installer as root (this might need IS help or sudo privs). Note that we usually install the application to /opt # Run the JIRA Configuration tool to set the jira.home to the /data/jira location # Connect to JIRA_Temp database on Solstice2 (.... more to do here, see Atlassian docs) # Migrate existing configuration over to new JIRA (I need to add more here as we added Crowd). # Start JIRA # Import backed up XML # Perform post upgrades checks and tests *Need to document steps for 4.4.5->6.X*]]> 27558125 27590888 4.4: [https://confluence.atlassian.com/display/JIRA044/Migrating+JIRA+to+Another+Server] ## The JIRA configuration tool: [https://confluence.atlassian.com/display/JIRA044/Using+the+JIRA+Configuration+Tool] h5. Steps # (/) Create new VM named bugs.mbari.org in the DMZ # (/) Have Neil create database Jira_Temp on solstice2.shore.mbari.org # (/) Have Neil create database Jira on solstice2.shore.mbari.org # (/) Have Pat install Java 7 on bugs.shore.mbari.org # (/) Have Pete plumb holes through firewall so processes on bugs.mbari.org can get to Solstice2 # (/) Have Pat create DB_Collaboration account on bugs so it can run JIRA under that account and it can connect to solstice2 using that NT Domain account. # (/) Upgrade license on Atlassian site # (/) Log into bugs.shore.mbari.org # (/) Download 3.13.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 4.4.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 5.2.11 standalone Linux 64 bit tar.gz (not sure this version is necessary, but at least I have it) # (/) Unzip and untar the file to /opt # (/) Download latest JIRA (6.4.7 as of this writing). # (/) Unzip and untar it to /opt # Performed Test Upgrade ## (/) In order to export the current stuff in JIRA, I had to shut off access so people could not change the data while I was backing it up. ## (/) I ssh'd to oceana.mbari.org as root and edited the /opt/jira/conf/server.xml file and commented out the Connector section that had the port of 8010 to shut it off from the normal serving route. ## (/) I uncommented the 8082 port connector and the 8443 port connector so that I could still get to the server. ## (/) I stopped and started the JIRA server and in the log file I got a "keystore was tampered with..." which is not surprising. ## (/) I could then browser over to http://oceana.mbari.org:8082/jira ## (/) Then through the Administration console, I did an XML backup ## (/) I then created a tar of all the attachments in the /data/jira_3_12/attachments directory ## (/) I moved both the XML and tar files to the /root/jira-upgrade directory ## (/) I then reversed the changes to the server.xml file and shut down JIRA ## (/) I left it down during the next steps in case it went so well, I could just point people to the new server (yeah, right). ## (/) I then browsed to the crowd server on oceana and add a new application using: ### URL: http://bugs.mbari.org/jira3135 ### IP: 134.89.2.29 ### Name: JIRA3135 ### Password: (ask Kevin) :) ## (/) On bugs, I made a copy of the JIRA 3.13.5 download in the /opt directory and unzipped and untarred it. ## (/) In order to configure the crowd connection I did the following: ### (/) I scp'd the /opt/crowd/client/crowd-integration-client-1.6.jar file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I removed the existing 1.6.1 crowd client jar from the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I scp'd the /opt/crowd/client/conf/crowd.properties file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I scp'd the /opt/crowd/client/conf/crowd-ehcache.xml file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I edited the crowd.properties file on bugs to look like: {noformat} application.name JIRA3135 application.password (ask Kevin) application.login.url http://oceana.mbari.org:8095/crowd/console/ crowd.server.url http://oceana.mbari.org:8095/crowd/services/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 0 session.lastvalidation session.lastvalidation {noformat} ### (/) I edited the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/osuser.xml file to comment out the current authentication mechanism and then uncomment the crowd one. ## (/) I then edited the /opt/atlassian-jira-standalone-3.13.5/conf/server/xml file and configured the database connection to the Jira_Temp database on Solstice2. I looked like this: {noformat} {noformat} ## (/) Edit the /opt/atlassian/jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/entityengine.xml and changed it from 'hsql' to 'mssql' and delete the line with "PUBLIC" in it per the instructions in the comments in that file. ## (/) I edited the /etc/httpd/conf/httpd.conf file and created a proxy pass at the bottom of the file to point a normal URL to the default port 8080 for JIRA: {noformat} # Proxy Pass for JIRA ProxyPass http://bugs.mbari.org:8080 ProxyPassReverse http://bugs.mbari.org:8080 {noformat} ## (/) I restarted Apache ## (/) I scp'd the jtds driver from oceana to the /opt/atlassian-jira-standalone-3.13.5/common/lib directory (you could down from the internet) ## (/) I then went to the /opt/atlassian-jira-standalone-3.13.5/ directory and ran './bin/startup.sh'. From the log file, I could tell things were hanging. After some troubleshooting I am wondering if the local firewall is preventing the application to get access to the database on solstice2. I can telnet to port 1433, but I can't browse to the base http://bugs.mbari.org from anywhere but the local web browser. I have submitted a ticket. ## (/) I restarted the old JIRA with my hopes dashed :(. ## (/) Pat disabled the firewall on bugs.mbari.org but it still hung trying to connect to solstice2.shore.mbari.org. That is really, really perplexing. Neil mentioned that solstice2 is using Kerberos and solstice is not. Checking with the JTDS docs, version 1.3.1 of the driver added kerberos support, so I downloaded that driver and added the 'userKerberos=true' property to the URL in the server.xml file and restarted. Got an error about no credentials, so added user and password properties to the URL. Nope, no luck. Never did figure this one out, but I had Pat pull the VM inside the firewall and after some thrash it worked. Well, it sort of worked ... sigh. It turns out I had downloaded the standard version instead of the enterprise version. I need to redo this work ... grrr. ## (/) I deleted all the tables in the Jira_Temp database and removed the /data/jira3135/indexes directory (and recreated). ## (/) I downloaded the enterprise version of the 3.13.5 server. I made a copy in the /opt directory and unzipped and untarred the file. ## (/) I went back to crowd and edited the application to change the properties to: ### URL: http://bugs.shore.mbari.org:8080 ### IP: 134.89.12.31 ### Name: jira3135 ### Password: (ask Kevin) :) ## (/) I then repeated the steps above to get the server up and running with the following differences: ### The server name is now bugs.shore.mbari.org ### The paths given above are a little different in that they no longer say "standard" but say "enterprise" ### I deleted the proxy pass as it seemed to have issues before and this is only temporary anyway. ## (/) I then browsed to http://bugs.shore.mbari.org:8080 ## (/) It took me to the start up page and at the top was the option to 'import your existing data'. Seemed too good not to try. I clicked on the link. It asked me for the backup file location and the location where the indexes would be stored. ## (/) I copied the XML zip file and the attachments tar file to the /data/original directory. ## (/) I created the /data/jira3135/indexes and used those directories ... it fired off the import and I waited. ## (/) I tailed the log file to watch the import. Holy crap, it worked!!! I could log in and everything! I copied the results from the log file here for posterity sake: {noformat} 2015-07-22 20:55:45,156 http-8080-Processor22 INFO [jira.action.admin.DataImport] Running data import 2015-07-22 20:55:45,179 http-8080-Processor22 INFO [jira.action.admin.DataImport] Importing data.. 2015-07-22 20:55:45,186 http-8080-Processor22 INFO [jira.action.admin.DataImport] Start parsing XML with SAX Parser 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] XML successfully parsed 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] Removing all entries from the database. 2015-07-22 20:56:24,593 http-8080-Processor22 INFO [jira.action.admin.DataImport] All entries removed. 2015-07-22 20:56:24,594 http-8080-Processor22 INFO [jira.action.admin.DataImport] Started storing 410414 Generic Values 2015-07-22 21:01:51,967 http-8080-Processor22 INFO [jira.action.admin.DataImport] Finished storing Generic Values 2015-07-22 21:01:52,329 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:52,361 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:54,683 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLink' to module 'jira.user.format:profile-link-user-format'. 2015-07-22 21:01:54,724 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullName' to module 'jira.user.format:full-name-user-format'. 2015-07-22 21:01:54,773 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkSearcher' to module 'jira.user.format:profile-link-searcher-user-format'. 2015-07-22 21:01:54,784 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkExternal' to module 'jira.user.format:profile-link-external-user-format'. 2015-07-22 21:01:54,795 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkActionHeader' to module 'jira.user.format:profile-link-action-header-user-format'. 2015-07-22 21:01:54,807 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullProfile' to module 'jira.user.format:full-profile-user-format'. 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/comments 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/issues 2015-07-22 21:01:55,641 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/plugins 2015-07-22 21:01:55,867 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:01:55,871 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/issues does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:55,873 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/comments does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,033 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,257 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,889 http-8080-Processor22 ERROR [atlassian.jira.upgrade.ConsistencyCheckImpl] Attachments are turned on, but attachment path [/data/jira_3_12/attachments] invalid - disabling attachments 2015-07-22 21:02:13,904 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Detected that an upgrade is needed; existing data at build 299 2015-07-22 21:02:13,907 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Doing Upgrade... 2015-07-22 21:02:13,915 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value' succeeded 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 317 2015-07-22 21:02:13,944 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite filters - make each filter a favourite of its owner. 2015-07-22 21:02:17,822 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build319] Could not find author 'fpy' for filter with id '10040' 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite filters - make each filter a favourite of its owner.' succeeded 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 319 2015-07-22 21:02:17,995 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise Share Permissions. Move old shares to new shares. 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise Share Permissions. Move old shares to new shares.' succeeded 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 321 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Migrating the old JIRA UI colors to the new JIRA 3.13 colors 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build322] Custom color detected for jira.lf.menu.bgcolour : #336699 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Migrating the old JIRA UI colors to the new JIRA 3.13 colors' succeeded 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 322 2015-07-22 21:02:18,025 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite dashboards - make each dashboard a favourite of its owner. 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'cmcgann' for dashboard with id '10030' 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'fpy' for dashboard with id '10060' 2015-07-22 21:02:18,423 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'kanna' for dashboard with id '10040' 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite dashboards - make each dashboard a favourite of its owner.' succeeded 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 325 2015-07-22 21:02:18,625 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Reindexing all data in JIRA to include Favourites. 2015-07-22 21:02:18,648 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All starting... 2015-07-22 21:02:18,650 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 0% complete. Current index: Issue 2015-07-22 21:02:18,654 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:02:18,809 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 1% complete. Current index: Issue 2015-07-22 21:02:18,855 indexerPool-2-thread-10 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 2% complete. Current index: Issue 2015-07-22 21:02:18,899 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 3% complete. Current index: Issue 2015-07-22 21:02:18,945 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 4% complete. Current index: Issue 2015-07-22 21:02:19,012 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 5% complete. Current index: Issue . . . 2015-07-22 21:02:26,164 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 95% complete. Current index: Issue 2015-07-22 21:02:26,232 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 96% complete. Current index: Issue 2015-07-22 21:02:26,316 indexerPool-2-thread-9 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 97% complete. Current index: Issue 2015-07-22 21:02:26,771 indexerPool-2-thread-3 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: Issue 2015-07-22 21:02:27,261 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 8607ms. Indexer: DefaultIndexManager: paths: [/data/jira3135/indexes/issues, /data/jira3135/indexes/comments] 2015-07-22 21:02:27,263 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: SearchRequest 2015-07-22 21:02:27,268 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,293 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: SearchRequest 2015-07-22 21:02:27,308 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: PortalPage 2015-07-22 21:02:27,312 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,377 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: PortalPage 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 115ms. Indexer: SharedEntityIndexManager: paths: [/data/jira3135/indexes/entities/portalpage, /data/jira3135/indexes/entities/searchrequest] 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All complete. Total time: 8722ms. 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Reindexing all data in JIRA to include Favourites.' succeeded 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 326 2015-07-22 21:02:27,397 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade succeeded! Setting data build number to 360 2015-07-22 21:02:27,469 JiraQuartzScheduler_Worker-0 WARN [service.services.export.ExportService] Backup directory /data/jira_3_12/backup does not exist {noformat} {warning:title=Paths} It appears that the upgraded JIRA will still look for the attachments and the backup locations in the original places. So I created /data/jira_3_12/backup and untarred the original attachments to /data/jira_3_12 and then everything worked (including attachements) in the new JIRA. {warning} ## (/) I then used the upgraded JIRA to generate a new XML backup and stored it in /data/original/3.13.5 along with another tar of the files in /data/jira_3_12/attachments. ## (/) I then shutdown the JIRA server. *I should be ready to move on to version 4 upgrade WHEW* ## So, before moving on, I decided that it would be a really good idea to spin up a new Crowd instance to get rid of the :8443 in the URL and to move off of RedHat per IS requests. I have a ticket in for a new VM and a new database to try to get this going. I am waiting on that before moving on. ## (/) Pat created the VM and Neil created the database. ## (/) I logged into auth.mbari.org (name of the VM) and downloaded crowd which I unzipped to the /opt directory ## (/) I then created a /data/crowd directory and gave my account permissions on it and then edited the /opt/atlassian..../crowd-webapp/WEB-INF/classes/crowd-init.properties file to set that as the crowd home directory. ## (/) The instructions say to download the JDBC driver, but they already have JTDS 1.2.7 in the download so I did not do anything. ## (/) You have to manually connect up CrowdID to a database as they setup wizard does not currently do this. ### (/) They say to download the driver, but again 1.2.7 was there so I did nothing. ### (/) I edited the /opt/atlassian.../apache-tomcat/conf/Catalina/localhost/openidserver.xml to look like: {noformat} {noformat} ### (/) I edited the /opt/atlassian.../build.properties files to look like: {noformat} # Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See https://confluence.atlassian.com/display/CROWD/Connecting+Crowd+to+a+Database hibernate.dialect=org.hibernate.dialect.SQLServerDialect # The Hibernate transaction factory to use. See https://confluence.atlassian.com/display/CROWD/Configuring+Crowd hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory # The http port you wish to run crowd from, ie: http://localhost:8095/crowd crowd.tomcat.connector.port=8095 # Tomcat requires a unique port for shutdown crowd.tomcat.shutdown.port=8020 # Crowd context root crowd.url=http://localhost:8095/crowd # Demo context root demo.url=http://localhost:8095/demo # OpenID server context root openidserver.url=http://localhost:8095/openidserver {noformat} ### (/) I then ran the build.sh script in the root of /opt/atlassian... ## (/) I fired up crowd using the /opt/atlassian.../start_crowd.sh script ## (/) I then went to http://auth.mbari.org:8095/crowd to kick off the start up wizard ## (/) I grabbed a new eval license from my account on atlassian and pasted into the license page. ## (/) I selected "New install" on the next page. ## (/) I configured the JDBC connection using this connection URL with user DB_Collaboration {noformat} jdbc:jtds:sqlserver://dione.mbari.org:51001/Crowd;domain=SHORE;useNTLMv2=TRUE {noformat} ## (/) I left the "Options" as they came up {warning:title=Paths} Not sure if this is a problem, but because I started the set up using auth.mbari.org, it set the Base URL to http://auth.mbari.org:8095/crowd instead of localhost. Hope that is not a problem. We will see. {warning} ## (/) I configured the email connection using the settings from [here|https://wind.shore.mbari.org/is/howto/email/mbarimail/imap] and I used my network login (probably shouldn't be doing that ... not sure where it stores my password, but I am assuming in the DB). ## (/) For the local admin account, I created a user named 'crowdadm' so it would not clash with my LDAP account. See Kevin Gomes for password information. ## (/) I checked the OpenID server as an integrated application ## (/) It then took me to the login page and I logged in using the newly minted admin account. Seemed all is well so far. ## (/) I visited the openidserver URL as well and that seemed OK. ## (/) I decided to wait on configuring the MBARI LDAP directory until I got everything with SSL working. ## (/) Now the next step was to follow the directions to configure Crowd to run over SSL found [here|https://confluence.atlassian.com/display/CROWD/Configuring+Crowd+to+Work+with+SSL] ## (/) I shutdown crowd. Note that the stop script does not shutdown things correctly and I noticed the crowd app running as root. That should not be if I started as kgomes. Not sure what is up with that. ## (/) Now Joe had already configured SSL once, so I used his connector configuration in the server.xml file and so the final file looked like: {noformat} {noformat} ## (/) I then edited the /data/crowd/crowd.properties to look like: {noformat} #Sat Aug 01 09:05:15 PDT 2015 session.lastvalidation=session.lastvalidation session.tokenkey=session.tokenkey crowd.server.url=https\://auth.mbari.org\:8443/crowd/services/ application.name=crowd http.timeout=30000 session.isauthenticated=session.isauthenticated application.login.url=https\://auth.mbari.org\:8443/crowd/console/ session.validationinterval=0 application.password=Y1Xp3OorCmsOP4eruL1dmH {noformat} ## (/) Per the instructions on the atlassian page (referenced above), I also edited the build.properties file and the /client/conf/crowd.properties files before I restarted and used the SSL URLs ## build.properties: {noformat} # Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See https://confluence.atlassian.com/display/CROWD/Connecting+Crowd+to+a+Database hibernate.dialect=org.hibernate.dialect.SQLServerDialect # The Hibernate transaction factory to use. See https://confluence.atlassian.com/display/CROWD/Configuring+Crowd hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory # The http port you wish to run crowd from, ie: http://localhost:8095/crowd crowd.tomcat.connector.port=8095 # Tomcat requires a unique port for shutdown crowd.tomcat.shutdown.port=8020 # Crowd context root crowd.url=https://auth.mbari.org:8443/crowd # Demo context root demo.url=https://auth.mbari.org:8443/demo # OpenID server context root openidserver.url=https://auth.mbari.org:8443/openidserver {noformat} ## crowd.properties (client) {noformat} {noformat} # Schedule upgrade date and send all hands several days in advance. # When the day arrives, send all hands announcing JIRA outage. # From the Administrator's page in our existing JIRA, perform a 'Backup Data to XML'. # Login to oceana.mbari.org as root. # Shutdown JIRA # Create a tar.gz of the /opt/atlassian-jira-enterprise-3.12.1-standalone directory # Clean up the /data/jira_3_12/backups directory by deleting all but maybe the last 5 backups. # Create a tar.gz of the JIRA home directory on ocean.mbari.org which is located at /data/jira_3_12 # scp both tar.gz files to bugs.mbari.org # login to bugs.mbari.org # Unpack the home directory tar to /data/jira # Run the installer as root (this might need IS help or sudo privs). Note that we usually install the application to /opt # Run the JIRA Configuration tool to set the jira.home to the /data/jira location # Connect to JIRA_Temp database on Solstice2 (.... more to do here, see Atlassian docs) # Migrate existing configuration over to new JIRA (I need to add more here as we added Crowd). # Start JIRA # Import backed up XML # Perform post upgrades checks and tests *Need to document steps for 4.4.5->6.X*]]> 27558123 27590886 4.4: [https://confluence.atlassian.com/display/JIRA044/Migrating+JIRA+to+Another+Server] ## The JIRA configuration tool: [https://confluence.atlassian.com/display/JIRA044/Using+the+JIRA+Configuration+Tool] h5. Steps # (/) Create new VM named bugs.mbari.org in the DMZ # (/) Have Neil create database Jira_Temp on solstice2.shore.mbari.org # (/) Have Neil create database Jira on solstice2.shore.mbari.org # (/) Have Pat install Java 7 on bugs.shore.mbari.org # (/) Have Pete plumb holes through firewall so processes on bugs.mbari.org can get to Solstice2 # (/) Have Pat create DB_Collaboration account on bugs so it can run JIRA under that account and it can connect to solstice2 using that NT Domain account. # (/) Upgrade license on Atlassian site # (/) Log into bugs.shore.mbari.org # (/) Download 3.13.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 4.4.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 5.2.11 standalone Linux 64 bit tar.gz (not sure this version is necessary, but at least I have it) # (/) Unzip and untar the file to /opt # (/) Download latest JIRA (6.4.7 as of this writing). # (/) Unzip and untar it to /opt # Performed Test Upgrade ## (/) In order to export the current stuff in JIRA, I had to shut off access so people could not change the data while I was backing it up. ## (/) I ssh'd to oceana.mbari.org as root and edited the /opt/jira/conf/server.xml file and commented out the Connector section that had the port of 8010 to shut it off from the normal serving route. ## (/) I uncommented the 8082 port connector and the 8443 port connector so that I could still get to the server. ## (/) I stopped and started the JIRA server and in the log file I got a "keystore was tampered with..." which is not surprising. ## (/) I could then browser over to http://oceana.mbari.org:8082/jira ## (/) Then through the Administration console, I did an XML backup ## (/) I then created a tar of all the attachments in the /data/jira_3_12/attachments directory ## (/) I moved both the XML and tar files to the /root/jira-upgrade directory ## (/) I then reversed the changes to the server.xml file and shut down JIRA ## (/) I left it down during the next steps in case it went so well, I could just point people to the new server (yeah, right). ## (/) I then browsed to the crowd server on oceana and add a new application using: ### URL: http://bugs.mbari.org/jira3135 ### IP: 134.89.2.29 ### Name: JIRA3135 ### Password: (ask Kevin) :) ## (/) On bugs, I made a copy of the JIRA 3.13.5 download in the /opt directory and unzipped and untarred it. ## (/) In order to configure the crowd connection I did the following: ### (/) I scp'd the /opt/crowd/client/crowd-integration-client-1.6.jar file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I removed the existing 1.6.1 crowd client jar from the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I scp'd the /opt/crowd/client/conf/crowd.properties file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I scp'd the /opt/crowd/client/conf/crowd-ehcache.xml file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I edited the crowd.properties file on bugs to look like: {noformat} application.name JIRA3135 application.password (ask Kevin) application.login.url http://oceana.mbari.org:8095/crowd/console/ crowd.server.url http://oceana.mbari.org:8095/crowd/services/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 0 session.lastvalidation session.lastvalidation {noformat} ### (/) I edited the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/osuser.xml file to comment out the current authentication mechanism and then uncomment the crowd one. ## (/) I then edited the /opt/atlassian-jira-standalone-3.13.5/conf/server/xml file and configured the database connection to the Jira_Temp database on Solstice2. I looked like this: {noformat} {noformat} ## (/) Edit the /opt/atlassian/jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/entityengine.xml and changed it from 'hsql' to 'mssql' and delete the line with "PUBLIC" in it per the instructions in the comments in that file. ## (/) I edited the /etc/httpd/conf/httpd.conf file and created a proxy pass at the bottom of the file to point a normal URL to the default port 8080 for JIRA: {noformat} # Proxy Pass for JIRA ProxyPass http://bugs.mbari.org:8080 ProxyPassReverse http://bugs.mbari.org:8080 {noformat} ## (/) I restarted Apache ## (/) I scp'd the jtds driver from oceana to the /opt/atlassian-jira-standalone-3.13.5/common/lib directory (you could down from the internet) ## (/) I then went to the /opt/atlassian-jira-standalone-3.13.5/ directory and ran './bin/startup.sh'. From the log file, I could tell things were hanging. After some troubleshooting I am wondering if the local firewall is preventing the application to get access to the database on solstice2. I can telnet to port 1433, but I can't browse to the base http://bugs.mbari.org from anywhere but the local web browser. I have submitted a ticket. ## (/) I restarted the old JIRA with my hopes dashed :(. ## (/) Pat disabled the firewall on bugs.mbari.org but it still hung trying to connect to solstice2.shore.mbari.org. That is really, really perplexing. Neil mentioned that solstice2 is using Kerberos and solstice is not. Checking with the JTDS docs, version 1.3.1 of the driver added kerberos support, so I downloaded that driver and added the 'userKerberos=true' property to the URL in the server.xml file and restarted. Got an error about no credentials, so added user and password properties to the URL. Nope, no luck. Never did figure this one out, but I had Pat pull the VM inside the firewall and after some thrash it worked. Well, it sort of worked ... sigh. It turns out I had downloaded the standard version instead of the enterprise version. I need to redo this work ... grrr. ## (/) I deleted all the tables in the Jira_Temp database and removed the /data/jira3135/indexes directory (and recreated). ## (/) I downloaded the enterprise version of the 3.13.5 server. I made a copy in the /opt directory and unzipped and untarred the file. ## (/) I went back to crowd and edited the application to change the properties to: ### URL: http://bugs.shore.mbari.org:8080 ### IP: 134.89.12.31 ### Name: jira3135 ### Password: (ask Kevin) :) ## (/) I then repeated the steps above to get the server up and running with the following differences: ### The server name is now bugs.shore.mbari.org ### The paths given above are a little different in that they no longer say "standard" but say "enterprise" ### I deleted the proxy pass as it seemed to have issues before and this is only temporary anyway. ## (/) I then browsed to http://bugs.shore.mbari.org:8080 ## (/) It took me to the start up page and at the top was the option to 'import your existing data'. Seemed too good not to try. I clicked on the link. It asked me for the backup file location and the location where the indexes would be stored. ## (/) I copied the XML zip file and the attachments tar file to the /data/original directory. ## (/) I created the /data/jira3135/indexes and used those directories ... it fired off the import and I waited. ## (/) I tailed the log file to watch the import. Holy crap, it worked!!! I could log in and everything! I copied the results from the log file here for posterity sake: {noformat} 2015-07-22 20:55:45,156 http-8080-Processor22 INFO [jira.action.admin.DataImport] Running data import 2015-07-22 20:55:45,179 http-8080-Processor22 INFO [jira.action.admin.DataImport] Importing data.. 2015-07-22 20:55:45,186 http-8080-Processor22 INFO [jira.action.admin.DataImport] Start parsing XML with SAX Parser 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] XML successfully parsed 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] Removing all entries from the database. 2015-07-22 20:56:24,593 http-8080-Processor22 INFO [jira.action.admin.DataImport] All entries removed. 2015-07-22 20:56:24,594 http-8080-Processor22 INFO [jira.action.admin.DataImport] Started storing 410414 Generic Values 2015-07-22 21:01:51,967 http-8080-Processor22 INFO [jira.action.admin.DataImport] Finished storing Generic Values 2015-07-22 21:01:52,329 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:52,361 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:54,683 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLink' to module 'jira.user.format:profile-link-user-format'. 2015-07-22 21:01:54,724 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullName' to module 'jira.user.format:full-name-user-format'. 2015-07-22 21:01:54,773 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkSearcher' to module 'jira.user.format:profile-link-searcher-user-format'. 2015-07-22 21:01:54,784 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkExternal' to module 'jira.user.format:profile-link-external-user-format'. 2015-07-22 21:01:54,795 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkActionHeader' to module 'jira.user.format:profile-link-action-header-user-format'. 2015-07-22 21:01:54,807 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullProfile' to module 'jira.user.format:full-profile-user-format'. 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/comments 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/issues 2015-07-22 21:01:55,641 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/plugins 2015-07-22 21:01:55,867 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:01:55,871 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/issues does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:55,873 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/comments does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,033 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,257 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,889 http-8080-Processor22 ERROR [atlassian.jira.upgrade.ConsistencyCheckImpl] Attachments are turned on, but attachment path [/data/jira_3_12/attachments] invalid - disabling attachments 2015-07-22 21:02:13,904 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Detected that an upgrade is needed; existing data at build 299 2015-07-22 21:02:13,907 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Doing Upgrade... 2015-07-22 21:02:13,915 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value' succeeded 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 317 2015-07-22 21:02:13,944 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite filters - make each filter a favourite of its owner. 2015-07-22 21:02:17,822 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build319] Could not find author 'fpy' for filter with id '10040' 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite filters - make each filter a favourite of its owner.' succeeded 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 319 2015-07-22 21:02:17,995 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise Share Permissions. Move old shares to new shares. 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise Share Permissions. Move old shares to new shares.' succeeded 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 321 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Migrating the old JIRA UI colors to the new JIRA 3.13 colors 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build322] Custom color detected for jira.lf.menu.bgcolour : #336699 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Migrating the old JIRA UI colors to the new JIRA 3.13 colors' succeeded 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 322 2015-07-22 21:02:18,025 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite dashboards - make each dashboard a favourite of its owner. 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'cmcgann' for dashboard with id '10030' 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'fpy' for dashboard with id '10060' 2015-07-22 21:02:18,423 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'kanna' for dashboard with id '10040' 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite dashboards - make each dashboard a favourite of its owner.' succeeded 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 325 2015-07-22 21:02:18,625 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Reindexing all data in JIRA to include Favourites. 2015-07-22 21:02:18,648 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All starting... 2015-07-22 21:02:18,650 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 0% complete. Current index: Issue 2015-07-22 21:02:18,654 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:02:18,809 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 1% complete. Current index: Issue 2015-07-22 21:02:18,855 indexerPool-2-thread-10 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 2% complete. Current index: Issue 2015-07-22 21:02:18,899 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 3% complete. Current index: Issue 2015-07-22 21:02:18,945 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 4% complete. Current index: Issue 2015-07-22 21:02:19,012 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 5% complete. Current index: Issue . . . 2015-07-22 21:02:26,164 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 95% complete. Current index: Issue 2015-07-22 21:02:26,232 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 96% complete. Current index: Issue 2015-07-22 21:02:26,316 indexerPool-2-thread-9 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 97% complete. Current index: Issue 2015-07-22 21:02:26,771 indexerPool-2-thread-3 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: Issue 2015-07-22 21:02:27,261 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 8607ms. Indexer: DefaultIndexManager: paths: [/data/jira3135/indexes/issues, /data/jira3135/indexes/comments] 2015-07-22 21:02:27,263 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: SearchRequest 2015-07-22 21:02:27,268 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,293 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: SearchRequest 2015-07-22 21:02:27,308 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: PortalPage 2015-07-22 21:02:27,312 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,377 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: PortalPage 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 115ms. Indexer: SharedEntityIndexManager: paths: [/data/jira3135/indexes/entities/portalpage, /data/jira3135/indexes/entities/searchrequest] 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All complete. Total time: 8722ms. 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Reindexing all data in JIRA to include Favourites.' succeeded 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 326 2015-07-22 21:02:27,397 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade succeeded! Setting data build number to 360 2015-07-22 21:02:27,469 JiraQuartzScheduler_Worker-0 WARN [service.services.export.ExportService] Backup directory /data/jira_3_12/backup does not exist {noformat} {warning:title=Paths} It appears that the upgraded JIRA will still look for the attachments and the backup locations in the original places. So I created /data/jira_3_12/backup and untarred the original attachments to /data/jira_3_12 and then everything worked (including attachements) in the new JIRA. {warning} ## (/) I then used the upgraded JIRA to generate a new XML backup and stored it in /data/original/3.13.5 along with another tar of the files in /data/jira_3_12/attachments. ## (/) I then shutdown the JIRA server. *I should be ready to move on to version 4 upgrade WHEW* ## So, before moving on, I decided that it would be a really good idea to spin up a new Crowd instance to get rid of the :8443 in the URL and to move off of RedHat per IS requests. I have a ticket in for a new VM and a new database to try to get this going. I am waiting on that before moving on. ## (/) Pat created the VM and Neil created the database. ## (/) I logged into auth.mbari.org (name of the VM) and downloaded crowd which I unzipped to the /opt directory ## (/) I then created a /data/crowd directory and gave my account permissions on it and then edited the /opt/atlassian..../crowd-webapp/WEB-INF/classes/crowd-init.properties file to set that as the crowd home directory. ## (/) The instructions say to download the JDBC driver, but they already have JTDS 1.2.7 in the download so I did not do anything. ## (/) You have to manually connect up CrowdID to a database as they setup wizard does not currently do this. ### (/) They say to download the driver, but again 1.2.7 was there so I did nothing. ### (/) I edited the /opt/atlassian.../apache-tomcat/conf/Catalina/localhost/openidserver.xml to look like: {noformat} {noformat} ### (/) I edited the /opt/atlassian.../build.properties files to look like: {noformat} # Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See https://confluence.atlassian.com/display/CROWD/Connecting+Crowd+to+a+Database hibernate.dialect=org.hibernate.dialect.SQLServerDialect # The Hibernate transaction factory to use. See https://confluence.atlassian.com/display/CROWD/Configuring+Crowd hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory # The http port you wish to run crowd from, ie: http://localhost:8095/crowd crowd.tomcat.connector.port=8095 # Tomcat requires a unique port for shutdown crowd.tomcat.shutdown.port=8020 # Crowd context root crowd.url=http://localhost:8095/crowd # Demo context root demo.url=http://localhost:8095/demo # OpenID server context root openidserver.url=http://localhost:8095/openidserver {noformat} ### (/) I then ran the build.sh script in the root of /opt/atlassian... ## (/) I fired up crowd using the /opt/atlassian.../start_crowd.sh script ## (/) I then went to http://auth.mbari.org:8095/crowd to kick off the start up wizard ## (/) I grabbed a new eval license from my account on atlassian and pasted into the license page. ## (/) I selected "New install" on the next page. ## (/) I configured the JDBC connection using this connection URL with user DB_Collaboration {noformat} jdbc:jtds:sqlserver://dione.mbari.org:51001/Crowd;domain=SHORE;useNTLMv2=TRUE {noformat} ## (/) I left the "Options" as they came up {warning:title=Paths} Not sure if this is a problem, but because I started the set up using auth.mbari.org, it set the Base URL to http://auth.mbari.org:8095/crowd instead of localhost. Hope that is not a problem. We will see. {warning} ## (/) I configured the email connection using the settings from [here|https://wind.shore.mbari.org/is/howto/email/mbarimail/imap] and I used my network login (probably shouldn't be doing that ... not sure where it stores my password, but I am assuming in the DB). ## (/) For the local admin account, I created a user named 'crowdadm' so it would not clash with my LDAP account. See Kevin Gomes for password information. ## (/) I checked the OpenID server as an integrated application ## (/) It then took me to the login page and I logged in using the newly minted admin account. Seemed all is well so far. ## (/) I visited the openidserver URL as well and that seemed OK. ## (/) I decided to wait on configuring the MBARI LDAP directory until I got everything with SSL working. ## (/) Now the next step was to follow the directions to configure Crowd to run over SSL found [here|https://confluence.atlassian.com/display/CROWD/Configuring+Crowd+to+Work+with+SSL] ## (/) I shutdown crowd. Note that the stop script does not shutdown things correctly and I noticed the crowd app running as root. That should not be if I started as kgomes. Not sure what is up with that. ## (/) Now Joe had already configured SSL once, so I used his connector configuration in the server.xml file and so the final file looked like: {noformat} {noformat} ## (/) I then edited the /data/crowd/crowd.properties to look like: {noformat} #Sat Aug 01 09:05:15 PDT 2015 session.lastvalidation=session.lastvalidation session.tokenkey=session.tokenkey crowd.server.url=https\://auth.mbari.org\:8443/crowd/services/ application.name=crowd http.timeout=30000 session.isauthenticated=session.isauthenticated application.login.url=https\://auth.mbari.org\:8443/crowd/console/ session.validationinterval=0 application.password=Y1Xp3OorCmsOP4eruL1dmH {noformat} ## (/) Per the instructions on the atlassian page (referenced above), I also edited the build.properties file and the /client/conf/crowd.properties files before I restarted and used the SSL URLs # Schedule upgrade date and send all hands several days in advance. # When the day arrives, send all hands announcing JIRA outage. # From the Administrator's page in our existing JIRA, perform a 'Backup Data to XML'. # Login to oceana.mbari.org as root. # Shutdown JIRA # Create a tar.gz of the /opt/atlassian-jira-enterprise-3.12.1-standalone directory # Clean up the /data/jira_3_12/backups directory by deleting all but maybe the last 5 backups. # Create a tar.gz of the JIRA home directory on ocean.mbari.org which is located at /data/jira_3_12 # scp both tar.gz files to bugs.mbari.org # login to bugs.mbari.org # Unpack the home directory tar to /data/jira # Run the installer as root (this might need IS help or sudo privs). Note that we usually install the application to /opt # Run the JIRA Configuration tool to set the jira.home to the /data/jira location # Connect to JIRA_Temp database on Solstice2 (.... more to do here, see Atlassian docs) # Migrate existing configuration over to new JIRA (I need to add more here as we added Crowd). # Start JIRA # Import backed up XML # Perform post upgrades checks and tests *Need to document steps for 4.4.5->6.X*]]> 27558121 27590884 4.4: [https://confluence.atlassian.com/display/JIRA044/Migrating+JIRA+to+Another+Server] ## The JIRA configuration tool: [https://confluence.atlassian.com/display/JIRA044/Using+the+JIRA+Configuration+Tool] h5. Steps # (/) Create new VM named bugs.mbari.org in the DMZ # (/) Have Neil create database Jira_Temp on solstice2.shore.mbari.org # (/) Have Neil create database Jira on solstice2.shore.mbari.org # (/) Have Pat install Java 7 on bugs.shore.mbari.org # (/) Have Pete plumb holes through firewall so processes on bugs.mbari.org can get to Solstice2 # (/) Have Pat create DB_Collaboration account on bugs so it can run JIRA under that account and it can connect to solstice2 using that NT Domain account. # (/) Upgrade license on Atlassian site # (/) Log into bugs.shore.mbari.org # (/) Download 3.13.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 4.4.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 5.2.11 standalone Linux 64 bit tar.gz (not sure this version is necessary, but at least I have it) # (/) Unzip and untar the file to /opt # (/) Download latest JIRA (6.4.7 as of this writing). # (/) Unzip and untar it to /opt # Performed Test Upgrade ## (/) In order to export the current stuff in JIRA, I had to shut off access so people could not change the data while I was backing it up. ## (/) I ssh'd to oceana.mbari.org as root and edited the /opt/jira/conf/server.xml file and commented out the Connector section that had the port of 8010 to shut it off from the normal serving route. ## (/) I uncommented the 8082 port connector and the 8443 port connector so that I could still get to the server. ## (/) I stopped and started the JIRA server and in the log file I got a "keystore was tampered with..." which is not surprising. ## (/) I could then browser over to http://oceana.mbari.org:8082/jira ## (/) Then through the Administration console, I did an XML backup ## (/) I then created a tar of all the attachments in the /data/jira_3_12/attachments directory ## (/) I moved both the XML and tar files to the /root/jira-upgrade directory ## (/) I then reversed the changes to the server.xml file and shut down JIRA ## (/) I left it down during the next steps in case it went so well, I could just point people to the new server (yeah, right). ## (/) I then browsed to the crowd server on oceana and add a new application using: ### URL: http://bugs.mbari.org/jira3135 ### IP: 134.89.2.29 ### Name: JIRA3135 ### Password: (ask Kevin) :) ## (/) On bugs, I made a copy of the JIRA 3.13.5 download in the /opt directory and unzipped and untarred it. ## (/) In order to configure the crowd connection I did the following: ### (/) I scp'd the /opt/crowd/client/crowd-integration-client-1.6.jar file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I removed the existing 1.6.1 crowd client jar from the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I scp'd the /opt/crowd/client/conf/crowd.properties file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I scp'd the /opt/crowd/client/conf/crowd-ehcache.xml file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I edited the crowd.properties file on bugs to look like: {noformat} application.name JIRA3135 application.password (ask Kevin) application.login.url http://oceana.mbari.org:8095/crowd/console/ crowd.server.url http://oceana.mbari.org:8095/crowd/services/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 0 session.lastvalidation session.lastvalidation {noformat} ### (/) I edited the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/osuser.xml file to comment out the current authentication mechanism and then uncomment the crowd one. ## (/) I then edited the /opt/atlassian-jira-standalone-3.13.5/conf/server/xml file and configured the database connection to the Jira_Temp database on Solstice2. I looked like this: {noformat} {noformat} ## (/) Edit the /opt/atlassian/jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/entityengine.xml and changed it from 'hsql' to 'mssql' and delete the line with "PUBLIC" in it per the instructions in the comments in that file. ## (/) I edited the /etc/httpd/conf/httpd.conf file and created a proxy pass at the bottom of the file to point a normal URL to the default port 8080 for JIRA: {noformat} # Proxy Pass for JIRA ProxyPass http://bugs.mbari.org:8080 ProxyPassReverse http://bugs.mbari.org:8080 {noformat} ## (/) I restarted Apache ## (/) I scp'd the jtds driver from oceana to the /opt/atlassian-jira-standalone-3.13.5/common/lib directory (you could down from the internet) ## (/) I then went to the /opt/atlassian-jira-standalone-3.13.5/ directory and ran './bin/startup.sh'. From the log file, I could tell things were hanging. After some troubleshooting I am wondering if the local firewall is preventing the application to get access to the database on solstice2. I can telnet to port 1433, but I can't browse to the base http://bugs.mbari.org from anywhere but the local web browser. I have submitted a ticket. ## (/) I restarted the old JIRA with my hopes dashed :(. ## (/) Pat disabled the firewall on bugs.mbari.org but it still hung trying to connect to solstice2.shore.mbari.org. That is really, really perplexing. Neil mentioned that solstice2 is using Kerberos and solstice is not. Checking with the JTDS docs, version 1.3.1 of the driver added kerberos support, so I downloaded that driver and added the 'userKerberos=true' property to the URL in the server.xml file and restarted. Got an error about no credentials, so added user and password properties to the URL. Nope, no luck. Never did figure this one out, but I had Pat pull the VM inside the firewall and after some thrash it worked. Well, it sort of worked ... sigh. It turns out I had downloaded the standard version instead of the enterprise version. I need to redo this work ... grrr. ## (/) I deleted all the tables in the Jira_Temp database and removed the /data/jira3135/indexes directory (and recreated). ## (/) I downloaded the enterprise version of the 3.13.5 server. I made a copy in the /opt directory and unzipped and untarred the file. ## (/) I went back to crowd and edited the application to change the properties to: ### URL: http://bugs.shore.mbari.org:8080 ### IP: 134.89.12.31 ### Name: jira3135 ### Password: (ask Kevin) :) ## (/) I then repeated the steps above to get the server up and running with the following differences: ### The server name is now bugs.shore.mbari.org ### The paths given above are a little different in that they no longer say "standard" but say "enterprise" ### I deleted the proxy pass as it seemed to have issues before and this is only temporary anyway. ## (/) I then browsed to http://bugs.shore.mbari.org:8080 ## (/) It took me to the start up page and at the top was the option to 'import your existing data'. Seemed too good not to try. I clicked on the link. It asked me for the backup file location and the location where the indexes would be stored. ## (/) I copied the XML zip file and the attachments tar file to the /data/original directory. ## (/) I created the /data/jira3135/indexes and used those directories ... it fired off the import and I waited. ## (/) I tailed the log file to watch the import. Holy crap, it worked!!! I could log in and everything! I copied the results from the log file here for posterity sake: {noformat} 2015-07-22 20:55:45,156 http-8080-Processor22 INFO [jira.action.admin.DataImport] Running data import 2015-07-22 20:55:45,179 http-8080-Processor22 INFO [jira.action.admin.DataImport] Importing data.. 2015-07-22 20:55:45,186 http-8080-Processor22 INFO [jira.action.admin.DataImport] Start parsing XML with SAX Parser 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] XML successfully parsed 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] Removing all entries from the database. 2015-07-22 20:56:24,593 http-8080-Processor22 INFO [jira.action.admin.DataImport] All entries removed. 2015-07-22 20:56:24,594 http-8080-Processor22 INFO [jira.action.admin.DataImport] Started storing 410414 Generic Values 2015-07-22 21:01:51,967 http-8080-Processor22 INFO [jira.action.admin.DataImport] Finished storing Generic Values 2015-07-22 21:01:52,329 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:52,361 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:54,683 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLink' to module 'jira.user.format:profile-link-user-format'. 2015-07-22 21:01:54,724 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullName' to module 'jira.user.format:full-name-user-format'. 2015-07-22 21:01:54,773 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkSearcher' to module 'jira.user.format:profile-link-searcher-user-format'. 2015-07-22 21:01:54,784 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkExternal' to module 'jira.user.format:profile-link-external-user-format'. 2015-07-22 21:01:54,795 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkActionHeader' to module 'jira.user.format:profile-link-action-header-user-format'. 2015-07-22 21:01:54,807 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullProfile' to module 'jira.user.format:full-profile-user-format'. 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/comments 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/issues 2015-07-22 21:01:55,641 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/plugins 2015-07-22 21:01:55,867 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:01:55,871 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/issues does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:55,873 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/comments does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,033 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,257 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,889 http-8080-Processor22 ERROR [atlassian.jira.upgrade.ConsistencyCheckImpl] Attachments are turned on, but attachment path [/data/jira_3_12/attachments] invalid - disabling attachments 2015-07-22 21:02:13,904 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Detected that an upgrade is needed; existing data at build 299 2015-07-22 21:02:13,907 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Doing Upgrade... 2015-07-22 21:02:13,915 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value' succeeded 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 317 2015-07-22 21:02:13,944 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite filters - make each filter a favourite of its owner. 2015-07-22 21:02:17,822 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build319] Could not find author 'fpy' for filter with id '10040' 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite filters - make each filter a favourite of its owner.' succeeded 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 319 2015-07-22 21:02:17,995 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise Share Permissions. Move old shares to new shares. 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise Share Permissions. Move old shares to new shares.' succeeded 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 321 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Migrating the old JIRA UI colors to the new JIRA 3.13 colors 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build322] Custom color detected for jira.lf.menu.bgcolour : #336699 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Migrating the old JIRA UI colors to the new JIRA 3.13 colors' succeeded 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 322 2015-07-22 21:02:18,025 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite dashboards - make each dashboard a favourite of its owner. 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'cmcgann' for dashboard with id '10030' 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'fpy' for dashboard with id '10060' 2015-07-22 21:02:18,423 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'kanna' for dashboard with id '10040' 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite dashboards - make each dashboard a favourite of its owner.' succeeded 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 325 2015-07-22 21:02:18,625 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Reindexing all data in JIRA to include Favourites. 2015-07-22 21:02:18,648 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All starting... 2015-07-22 21:02:18,650 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 0% complete. Current index: Issue 2015-07-22 21:02:18,654 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:02:18,809 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 1% complete. Current index: Issue 2015-07-22 21:02:18,855 indexerPool-2-thread-10 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 2% complete. Current index: Issue 2015-07-22 21:02:18,899 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 3% complete. Current index: Issue 2015-07-22 21:02:18,945 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 4% complete. Current index: Issue 2015-07-22 21:02:19,012 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 5% complete. Current index: Issue . . . 2015-07-22 21:02:26,164 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 95% complete. Current index: Issue 2015-07-22 21:02:26,232 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 96% complete. Current index: Issue 2015-07-22 21:02:26,316 indexerPool-2-thread-9 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 97% complete. Current index: Issue 2015-07-22 21:02:26,771 indexerPool-2-thread-3 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: Issue 2015-07-22 21:02:27,261 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 8607ms. Indexer: DefaultIndexManager: paths: [/data/jira3135/indexes/issues, /data/jira3135/indexes/comments] 2015-07-22 21:02:27,263 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: SearchRequest 2015-07-22 21:02:27,268 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,293 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: SearchRequest 2015-07-22 21:02:27,308 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: PortalPage 2015-07-22 21:02:27,312 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,377 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: PortalPage 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 115ms. Indexer: SharedEntityIndexManager: paths: [/data/jira3135/indexes/entities/portalpage, /data/jira3135/indexes/entities/searchrequest] 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All complete. Total time: 8722ms. 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Reindexing all data in JIRA to include Favourites.' succeeded 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 326 2015-07-22 21:02:27,397 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade succeeded! Setting data build number to 360 2015-07-22 21:02:27,469 JiraQuartzScheduler_Worker-0 WARN [service.services.export.ExportService] Backup directory /data/jira_3_12/backup does not exist {noformat} {warning:title=Paths} It appears that the upgraded JIRA will still look for the attachments and the backup locations in the original places. So I created /data/jira_3_12/backup and untarred the original attachments to /data/jira_3_12 and then everything worked (including attachements) in the new JIRA. {warning} ## (/) I then used the upgraded JIRA to generate a new XML backup and stored it in /data/original/3.13.5 along with another tar of the files in /data/jira_3_12/attachments. ## (/) I then shutdown the JIRA server. *I should be ready to move on to version 4 upgrade WHEW* ## So, before moving on, I decided that it would be a really good idea to spin up a new Crowd instance to get rid of the :8443 in the URL and to move off of RedHat per IS requests. I have a ticket in for a new VM and a new database to try to get this going. I am waiting on that before moving on. ## (/) Pat created the VM and Neil created the database. ## (/) I logged into auth.mbari.org (name of the VM) and downloaded crowd which I unzipped to the /opt directory ## (/) I then created a /data/crowd directory and gave my account permissions on it and then edited the /opt/atlassian..../crowd-webapp/WEB-INF/classes/crowd-init.properties file to set that as the crowd home directory. ## (/) The instructions say to download the JDBC driver, but they already have JTDS 1.2.7 in the download so I did not do anything. ## (/) You have to manually connect up CrowdID to a database as they setup wizard does not currently do this. ### (/) They say to download the driver, but again 1.2.7 was there so I did nothing. ### (/) I edited the /opt/atlassian.../apache-tomcat/conf/Catalina/localhost/openidserver.xml to look like: {noformat} {noformat} ### (/) I edited the /opt/atlassian.../build.properties files to look like: {noformat} # Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See https://confluence.atlassian.com/display/CROWD/Connecting+Crowd+to+a+Database hibernate.dialect=org.hibernate.dialect.SQLServerDialect # The Hibernate transaction factory to use. See https://confluence.atlassian.com/display/CROWD/Configuring+Crowd hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory # The http port you wish to run crowd from, ie: http://localhost:8095/crowd crowd.tomcat.connector.port=8095 # Tomcat requires a unique port for shutdown crowd.tomcat.shutdown.port=8020 # Crowd context root crowd.url=http://localhost:8095/crowd # Demo context root demo.url=http://localhost:8095/demo # OpenID server context root openidserver.url=http://localhost:8095/openidserver {noformat} ### (/) I then ran the build.sh script in the root of /opt/atlassian... ## (/) I fired up crowd using the /opt/atlassian.../start_crowd.sh script ## (/) I then went to http://auth.mbari.org:8095/crowd to kick off the start up wizard ## (/) I grabbed a new eval license from my account on atlassian and pasted into the license page. ## (/) I selected "New install" on the next page. ## (/) I configured the JDBC connection using this connection URL with user DB_Collaboration {noformat} jdbc:jtds:sqlserver://dione.mbari.org:51001/Crowd;domain=SHORE;useNTLMv2=TRUE {noformat} ## (/) I left the "Options" as they came up {warning:title=Paths} Not sure if this is a problem, but because I started the set up using auth.mbari.org, it set the Base URL to http://auth.mbari.org:8095/crowd instead of localhost. Hope that is not a problem. We will see. {warning} ## (/) I configured the email connection using the settings from [here|https://wind.shore.mbari.org/is/howto/email/mbarimail/imap] and I used my network login (probably shouldn't be doing that ... not sure where it stores my password, but I am assuming in the DB). ## (/) For the local admin account, I created a user named 'crowdadm' so it would not clash with my LDAP account. See Kevin Gomes for password information. ## (/) I checked the OpenID server as an integrated application ## (/) It then took me to the login page and I logged in using the newly minted admin account. Seemed all is well so far. ## (/) I visited the openidserver URL as well and that seemed OK. ## (/) I decided to wait on configuring the MBARI LDAP directory until I got everything with SSL working. ## (/) Now the next step was to follow the directions to configure Crowd to run over SSL found [here|https://confluence.atlassian.com/display/CROWD/Configuring+Crowd+to+Work+with+SSL] ## (/) I shutdown crowd. Note that the stop script does not shutdown things correctly and I noticed the crowd app running as root. That should not be if I started as kgomes. Not sure what is up with that. ## (/) Now Joe had already configured SSL once, so I used his connector configuration in the server.xml file and so the final file looked like: {noformat} {noformat} # Schedule upgrade date and send all hands several days in advance. # When the day arrives, send all hands announcing JIRA outage. # From the Administrator's page in our existing JIRA, perform a 'Backup Data to XML'. # Login to oceana.mbari.org as root. # Shutdown JIRA # Create a tar.gz of the /opt/atlassian-jira-enterprise-3.12.1-standalone directory # Clean up the /data/jira_3_12/backups directory by deleting all but maybe the last 5 backups. # Create a tar.gz of the JIRA home directory on ocean.mbari.org which is located at /data/jira_3_12 # scp both tar.gz files to bugs.mbari.org # login to bugs.mbari.org # Unpack the home directory tar to /data/jira # Run the installer as root (this might need IS help or sudo privs). Note that we usually install the application to /opt # Run the JIRA Configuration tool to set the jira.home to the /data/jira location # Connect to JIRA_Temp database on Solstice2 (.... more to do here, see Atlassian docs) # Migrate existing configuration over to new JIRA (I need to add more here as we added Crowd). # Start JIRA # Import backed up XML # Perform post upgrades checks and tests *Need to document steps for 4.4.5->6.X*]]> 27558119 27590880 4.4: [https://confluence.atlassian.com/display/JIRA044/Migrating+JIRA+to+Another+Server] ## The JIRA configuration tool: [https://confluence.atlassian.com/display/JIRA044/Using+the+JIRA+Configuration+Tool] h5. Steps # (/) Create new VM named bugs.mbari.org in the DMZ # (/) Have Neil create database Jira_Temp on solstice2.shore.mbari.org # (/) Have Neil create database Jira on solstice2.shore.mbari.org # (/) Have Pat install Java 7 on bugs.shore.mbari.org # (/) Have Pete plumb holes through firewall so processes on bugs.mbari.org can get to Solstice2 # (/) Have Pat create DB_Collaboration account on bugs so it can run JIRA under that account and it can connect to solstice2 using that NT Domain account. # (/) Upgrade license on Atlassian site # (/) Log into bugs.shore.mbari.org # (/) Download 3.13.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 4.4.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 5.2.11 standalone Linux 64 bit tar.gz (not sure this version is necessary, but at least I have it) # (/) Unzip and untar the file to /opt # (/) Download latest JIRA (6.4.7 as of this writing). # (/) Unzip and untar it to /opt # Performed Test Upgrade ## (/) In order to export the current stuff in JIRA, I had to shut off access so people could not change the data while I was backing it up. ## (/) I ssh'd to oceana.mbari.org as root and edited the /opt/jira/conf/server.xml file and commented out the Connector section that had the port of 8010 to shut it off from the normal serving route. ## (/) I uncommented the 8082 port connector and the 8443 port connector so that I could still get to the server. ## (/) I stopped and started the JIRA server and in the log file I got a "keystore was tampered with..." which is not surprising. ## (/) I could then browser over to http://oceana.mbari.org:8082/jira ## (/) Then through the Administration console, I did an XML backup ## (/) I then created a tar of all the attachments in the /data/jira_3_12/attachments directory ## (/) I moved both the XML and tar files to the /root/jira-upgrade directory ## (/) I then reversed the changes to the server.xml file and shut down JIRA ## (/) I left it down during the next steps in case it went so well, I could just point people to the new server (yeah, right). ## (/) I then browsed to the crowd server on oceana and add a new application using: ### URL: http://bugs.mbari.org/jira3135 ### IP: 134.89.2.29 ### Name: JIRA3135 ### Password: (ask Kevin) :) ## (/) On bugs, I made a copy of the JIRA 3.13.5 download in the /opt directory and unzipped and untarred it. ## (/) In order to configure the crowd connection I did the following: ### (/) I scp'd the /opt/crowd/client/crowd-integration-client-1.6.jar file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I removed the existing 1.6.1 crowd client jar from the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I scp'd the /opt/crowd/client/conf/crowd.properties file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I scp'd the /opt/crowd/client/conf/crowd-ehcache.xml file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I edited the crowd.properties file on bugs to look like: {noformat} application.name JIRA3135 application.password (ask Kevin) application.login.url http://oceana.mbari.org:8095/crowd/console/ crowd.server.url http://oceana.mbari.org:8095/crowd/services/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 0 session.lastvalidation session.lastvalidation {noformat} ### (/) I edited the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/osuser.xml file to comment out the current authentication mechanism and then uncomment the crowd one. ## (/) I then edited the /opt/atlassian-jira-standalone-3.13.5/conf/server/xml file and configured the database connection to the Jira_Temp database on Solstice2. I looked like this: {noformat} {noformat} ## (/) Edit the /opt/atlassian/jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/entityengine.xml and changed it from 'hsql' to 'mssql' and delete the line with "PUBLIC" in it per the instructions in the comments in that file. ## (/) I edited the /etc/httpd/conf/httpd.conf file and created a proxy pass at the bottom of the file to point a normal URL to the default port 8080 for JIRA: {noformat} # Proxy Pass for JIRA ProxyPass http://bugs.mbari.org:8080 ProxyPassReverse http://bugs.mbari.org:8080 {noformat} ## (/) I restarted Apache ## (/) I scp'd the jtds driver from oceana to the /opt/atlassian-jira-standalone-3.13.5/common/lib directory (you could down from the internet) ## (/) I then went to the /opt/atlassian-jira-standalone-3.13.5/ directory and ran './bin/startup.sh'. From the log file, I could tell things were hanging. After some troubleshooting I am wondering if the local firewall is preventing the application to get access to the database on solstice2. I can telnet to port 1433, but I can't browse to the base http://bugs.mbari.org from anywhere but the local web browser. I have submitted a ticket. ## (/) I restarted the old JIRA with my hopes dashed :(. ## (/) Pat disabled the firewall on bugs.mbari.org but it still hung trying to connect to solstice2.shore.mbari.org. That is really, really perplexing. Neil mentioned that solstice2 is using Kerberos and solstice is not. Checking with the JTDS docs, version 1.3.1 of the driver added kerberos support, so I downloaded that driver and added the 'userKerberos=true' property to the URL in the server.xml file and restarted. Got an error about no credentials, so added user and password properties to the URL. Nope, no luck. Never did figure this one out, but I had Pat pull the VM inside the firewall and after some thrash it worked. Well, it sort of worked ... sigh. It turns out I had downloaded the standard version instead of the enterprise version. I need to redo this work ... grrr. ## (/) I deleted all the tables in the Jira_Temp database and removed the /data/jira3135/indexes directory (and recreated). ## (/) I downloaded the enterprise version of the 3.13.5 server. I made a copy in the /opt directory and unzipped and untarred the file. ## (/) I went back to crowd and edited the application to change the properties to: ### URL: http://bugs.shore.mbari.org:8080 ### IP: 134.89.12.31 ### Name: jira3135 ### Password: (ask Kevin) :) ## (/) I then repeated the steps above to get the server up and running with the following differences: ### The server name is now bugs.shore.mbari.org ### The paths given above are a little different in that they no longer say "standard" but say "enterprise" ### I deleted the proxy pass as it seemed to have issues before and this is only temporary anyway. ## (/) I then browsed to http://bugs.shore.mbari.org:8080 ## (/) It took me to the start up page and at the top was the option to 'import your existing data'. Seemed too good not to try. I clicked on the link. It asked me for the backup file location and the location where the indexes would be stored. ## (/) I copied the XML zip file and the attachments tar file to the /data/original directory. ## (/) I created the /data/jira3135/indexes and used those directories ... it fired off the import and I waited. ## (/) I tailed the log file to watch the import. Holy crap, it worked!!! I could log in and everything! I copied the results from the log file here for posterity sake: {noformat} 2015-07-22 20:55:45,156 http-8080-Processor22 INFO [jira.action.admin.DataImport] Running data import 2015-07-22 20:55:45,179 http-8080-Processor22 INFO [jira.action.admin.DataImport] Importing data.. 2015-07-22 20:55:45,186 http-8080-Processor22 INFO [jira.action.admin.DataImport] Start parsing XML with SAX Parser 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] XML successfully parsed 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] Removing all entries from the database. 2015-07-22 20:56:24,593 http-8080-Processor22 INFO [jira.action.admin.DataImport] All entries removed. 2015-07-22 20:56:24,594 http-8080-Processor22 INFO [jira.action.admin.DataImport] Started storing 410414 Generic Values 2015-07-22 21:01:51,967 http-8080-Processor22 INFO [jira.action.admin.DataImport] Finished storing Generic Values 2015-07-22 21:01:52,329 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:52,361 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:54,683 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLink' to module 'jira.user.format:profile-link-user-format'. 2015-07-22 21:01:54,724 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullName' to module 'jira.user.format:full-name-user-format'. 2015-07-22 21:01:54,773 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkSearcher' to module 'jira.user.format:profile-link-searcher-user-format'. 2015-07-22 21:01:54,784 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkExternal' to module 'jira.user.format:profile-link-external-user-format'. 2015-07-22 21:01:54,795 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkActionHeader' to module 'jira.user.format:profile-link-action-header-user-format'. 2015-07-22 21:01:54,807 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullProfile' to module 'jira.user.format:full-profile-user-format'. 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/comments 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/issues 2015-07-22 21:01:55,641 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/plugins 2015-07-22 21:01:55,867 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:01:55,871 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/issues does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:55,873 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/comments does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,033 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,257 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,889 http-8080-Processor22 ERROR [atlassian.jira.upgrade.ConsistencyCheckImpl] Attachments are turned on, but attachment path [/data/jira_3_12/attachments] invalid - disabling attachments 2015-07-22 21:02:13,904 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Detected that an upgrade is needed; existing data at build 299 2015-07-22 21:02:13,907 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Doing Upgrade... 2015-07-22 21:02:13,915 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value' succeeded 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 317 2015-07-22 21:02:13,944 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite filters - make each filter a favourite of its owner. 2015-07-22 21:02:17,822 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build319] Could not find author 'fpy' for filter with id '10040' 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite filters - make each filter a favourite of its owner.' succeeded 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 319 2015-07-22 21:02:17,995 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise Share Permissions. Move old shares to new shares. 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise Share Permissions. Move old shares to new shares.' succeeded 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 321 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Migrating the old JIRA UI colors to the new JIRA 3.13 colors 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build322] Custom color detected for jira.lf.menu.bgcolour : #336699 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Migrating the old JIRA UI colors to the new JIRA 3.13 colors' succeeded 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 322 2015-07-22 21:02:18,025 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite dashboards - make each dashboard a favourite of its owner. 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'cmcgann' for dashboard with id '10030' 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'fpy' for dashboard with id '10060' 2015-07-22 21:02:18,423 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'kanna' for dashboard with id '10040' 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite dashboards - make each dashboard a favourite of its owner.' succeeded 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 325 2015-07-22 21:02:18,625 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Reindexing all data in JIRA to include Favourites. 2015-07-22 21:02:18,648 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All starting... 2015-07-22 21:02:18,650 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 0% complete. Current index: Issue 2015-07-22 21:02:18,654 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:02:18,809 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 1% complete. Current index: Issue 2015-07-22 21:02:18,855 indexerPool-2-thread-10 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 2% complete. Current index: Issue 2015-07-22 21:02:18,899 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 3% complete. Current index: Issue 2015-07-22 21:02:18,945 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 4% complete. Current index: Issue 2015-07-22 21:02:19,012 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 5% complete. Current index: Issue . . . 2015-07-22 21:02:26,164 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 95% complete. Current index: Issue 2015-07-22 21:02:26,232 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 96% complete. Current index: Issue 2015-07-22 21:02:26,316 indexerPool-2-thread-9 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 97% complete. Current index: Issue 2015-07-22 21:02:26,771 indexerPool-2-thread-3 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: Issue 2015-07-22 21:02:27,261 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 8607ms. Indexer: DefaultIndexManager: paths: [/data/jira3135/indexes/issues, /data/jira3135/indexes/comments] 2015-07-22 21:02:27,263 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: SearchRequest 2015-07-22 21:02:27,268 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,293 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: SearchRequest 2015-07-22 21:02:27,308 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: PortalPage 2015-07-22 21:02:27,312 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,377 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: PortalPage 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 115ms. Indexer: SharedEntityIndexManager: paths: [/data/jira3135/indexes/entities/portalpage, /data/jira3135/indexes/entities/searchrequest] 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All complete. Total time: 8722ms. 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Reindexing all data in JIRA to include Favourites.' succeeded 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 326 2015-07-22 21:02:27,397 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade succeeded! Setting data build number to 360 2015-07-22 21:02:27,469 JiraQuartzScheduler_Worker-0 WARN [service.services.export.ExportService] Backup directory /data/jira_3_12/backup does not exist {noformat} {warning:title=Paths} It appears that the upgraded JIRA will still look for the attachments and the backup locations in the original places. So I created /data/jira_3_12/backup and untarred the original attachments to /data/jira_3_12 and then everything worked (including attachements) in the new JIRA. {warning} ## (/) I then used the upgraded JIRA to generate a new XML backup and stored it in /data/original/3.13.5 along with another tar of the files in /data/jira_3_12/attachments. ## (/) I then shutdown the JIRA server. *I should be ready to move on to version 4 upgrade WHEW* ## So, before moving on, I decided that it would be a really good idea to spin up a new Crowd instance to get rid of the :8443 in the URL and to move off of RedHat per IS requests. I have a ticket in for a new VM and a new database to try to get this going. I am waiting on that before moving on. ## (/) Pat created the VM and Neil created the database. ## (/) I logged into auth.mbari.org (name of the VM) and downloaded crowd which I unzipped to the /opt directory ## (/) I then created a /data/crowd directory and gave my account permissions on it and then edited the /opt/atlassian..../crowd-webapp/WEB-INF/classes/crowd-init.properties file to set that as the crowd home directory. ## (/) The instructions say to download the JDBC driver, but they already have JTDS 1.2.7 in the download so I did not do anything. ## (/) You have to manually connect up CrowdID to a database as they setup wizard does not currently do this. ### (/) They say to download the driver, but again 1.2.7 was there so I did nothing. ### (/) I edited the /opt/atlassian.../apache-tomcat/conf/Catalina/localhost/openidserver.xml to look like: {noformat} {noformat} ### (/) I edited the /opt/atlassian.../build.properties files to look like: {noformat} # Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See https://confluence.atlassian.com/display/CROWD/Connecting+Crowd+to+a+Database hibernate.dialect=org.hibernate.dialect.SQLServerDialect # The Hibernate transaction factory to use. See https://confluence.atlassian.com/display/CROWD/Configuring+Crowd hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory # The http port you wish to run crowd from, ie: http://localhost:8095/crowd crowd.tomcat.connector.port=8095 # Tomcat requires a unique port for shutdown crowd.tomcat.shutdown.port=8020 # Crowd context root crowd.url=http://localhost:8095/crowd # Demo context root demo.url=http://localhost:8095/demo # OpenID server context root openidserver.url=http://localhost:8095/openidserver {noformat} ### (/) I then ran the build.sh script in the root of /opt/atlassian... ## (/) I fired up crowd using the /opt/atlassian.../start_crowd.sh script ## (/) I then went to http://auth.mbari.org:8095/crowd to kick off the start up wizard ## (/) I grabbed a new eval license from my account on atlassian and pasted into the license page. ## (/) I selected "New install" on the next page. ## (/) I configured the JDBC connection using this connection URL with user DB_Collaboration {noformat} jdbc:jtds:sqlserver://dione.mbari.org:51001/Crowd;domain=SHORE;useNTLMv2=TRUE {noformat} ## (/) I left the "Options" as they came up {warning:title=Paths} Not sure if this is a problem, but because I started the set up using auth.mbari.org, it set the Base URL to http://auth.mbari.org:8095/crowd instead of localhost. Hope that is not a problem. We will see. {warning} ## (/) I configured the email connection using the settings from [here|https://wind.shore.mbari.org/is/howto/email/mbarimail/imap] and I used my network login (probably shouldn't be doing that ... not sure where it stores my password, but I am assuming in the DB). ## (/) For the local admin account, I created a user named 'crowdadm' so it would not clash with my LDAP account. See Kevin Gomes for password information. ## (/) I checked the OpenID server as an integrated application ## (/) It then took me to the login page and I logged in using the newly minted admin account. Seemed all is well so far. ## (/) Now the next step was to follow the directions to configure Crowd to run over SSL found [here|https://confluence.atlassian.com/display/CROWD/Configuring+Crowd+to+Work+with+SSL] # Schedule upgrade date and send all hands several days in advance. # When the day arrives, send all hands announcing JIRA outage. # From the Administrator's page in our existing JIRA, perform a 'Backup Data to XML'. # Login to oceana.mbari.org as root. # Shutdown JIRA # Create a tar.gz of the /opt/atlassian-jira-enterprise-3.12.1-standalone directory # Clean up the /data/jira_3_12/backups directory by deleting all but maybe the last 5 backups. # Create a tar.gz of the JIRA home directory on ocean.mbari.org which is located at /data/jira_3_12 # scp both tar.gz files to bugs.mbari.org # login to bugs.mbari.org # Unpack the home directory tar to /data/jira # Run the installer as root (this might need IS help or sudo privs). Note that we usually install the application to /opt # Run the JIRA Configuration tool to set the jira.home to the /data/jira location # Connect to JIRA_Temp database on Solstice2 (.... more to do here, see Atlassian docs) # Migrate existing configuration over to new JIRA (I need to add more here as we added Crowd). # Start JIRA # Import backed up XML # Perform post upgrades checks and tests *Need to document steps for 4.4.5->6.X*]]> 27558115 27590882 4.4: [https://confluence.atlassian.com/display/JIRA044/Migrating+JIRA+to+Another+Server] ## The JIRA configuration tool: [https://confluence.atlassian.com/display/JIRA044/Using+the+JIRA+Configuration+Tool] h5. Steps # (/) Create new VM named bugs.mbari.org in the DMZ # (/) Have Neil create database Jira_Temp on solstice2.shore.mbari.org # (/) Have Neil create database Jira on solstice2.shore.mbari.org # (/) Have Pat install Java 7 on bugs.shore.mbari.org # (/) Have Pete plumb holes through firewall so processes on bugs.mbari.org can get to Solstice2 # (/) Have Pat create DB_Collaboration account on bugs so it can run JIRA under that account and it can connect to solstice2 using that NT Domain account. # (/) Upgrade license on Atlassian site # (/) Log into bugs.shore.mbari.org # (/) Download 3.13.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 4.4.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 5.2.11 standalone Linux 64 bit tar.gz (not sure this version is necessary, but at least I have it) # (/) Unzip and untar the file to /opt # (/) Download latest JIRA (6.4.7 as of this writing). # (/) Unzip and untar it to /opt # Performed Test Upgrade ## (/) In order to export the current stuff in JIRA, I had to shut off access so people could not change the data while I was backing it up. ## (/) I ssh'd to oceana.mbari.org as root and edited the /opt/jira/conf/server.xml file and commented out the Connector section that had the port of 8010 to shut it off from the normal serving route. ## (/) I uncommented the 8082 port connector and the 8443 port connector so that I could still get to the server. ## (/) I stopped and started the JIRA server and in the log file I got a "keystore was tampered with..." which is not surprising. ## (/) I could then browser over to http://oceana.mbari.org:8082/jira ## (/) Then through the Administration console, I did an XML backup ## (/) I then created a tar of all the attachments in the /data/jira_3_12/attachments directory ## (/) I moved both the XML and tar files to the /root/jira-upgrade directory ## (/) I then reversed the changes to the server.xml file and shut down JIRA ## (/) I left it down during the next steps in case it went so well, I could just point people to the new server (yeah, right). ## (/) I then browsed to the crowd server on oceana and add a new application using: ### URL: http://bugs.mbari.org/jira3135 ### IP: 134.89.2.29 ### Name: JIRA3135 ### Password: (ask Kevin) :) ## (/) On bugs, I made a copy of the JIRA 3.13.5 download in the /opt directory and unzipped and untarred it. ## (/) In order to configure the crowd connection I did the following: ### (/) I scp'd the /opt/crowd/client/crowd-integration-client-1.6.jar file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I removed the existing 1.6.1 crowd client jar from the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I scp'd the /opt/crowd/client/conf/crowd.properties file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I scp'd the /opt/crowd/client/conf/crowd-ehcache.xml file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I edited the crowd.properties file on bugs to look like: {noformat} application.name JIRA3135 application.password (ask Kevin) application.login.url http://oceana.mbari.org:8095/crowd/console/ crowd.server.url http://oceana.mbari.org:8095/crowd/services/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 0 session.lastvalidation session.lastvalidation {noformat} ### (/) I edited the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/osuser.xml file to comment out the current authentication mechanism and then uncomment the crowd one. ## (/) I then edited the /opt/atlassian-jira-standalone-3.13.5/conf/server/xml file and configured the database connection to the Jira_Temp database on Solstice2. I looked like this: {noformat} {noformat} ## (/) Edit the /opt/atlassian/jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/entityengine.xml and changed it from 'hsql' to 'mssql' and delete the line with "PUBLIC" in it per the instructions in the comments in that file. ## (/) I edited the /etc/httpd/conf/httpd.conf file and created a proxy pass at the bottom of the file to point a normal URL to the default port 8080 for JIRA: {noformat} # Proxy Pass for JIRA ProxyPass http://bugs.mbari.org:8080 ProxyPassReverse http://bugs.mbari.org:8080 {noformat} ## (/) I restarted Apache ## (/) I scp'd the jtds driver from oceana to the /opt/atlassian-jira-standalone-3.13.5/common/lib directory (you could down from the internet) ## (/) I then went to the /opt/atlassian-jira-standalone-3.13.5/ directory and ran './bin/startup.sh'. From the log file, I could tell things were hanging. After some troubleshooting I am wondering if the local firewall is preventing the application to get access to the database on solstice2. I can telnet to port 1433, but I can't browse to the base http://bugs.mbari.org from anywhere but the local web browser. I have submitted a ticket. ## (/) I restarted the old JIRA with my hopes dashed :(. ## (/) Pat disabled the firewall on bugs.mbari.org but it still hung trying to connect to solstice2.shore.mbari.org. That is really, really perplexing. Neil mentioned that solstice2 is using Kerberos and solstice is not. Checking with the JTDS docs, version 1.3.1 of the driver added kerberos support, so I downloaded that driver and added the 'userKerberos=true' property to the URL in the server.xml file and restarted. Got an error about no credentials, so added user and password properties to the URL. Nope, no luck. Never did figure this one out, but I had Pat pull the VM inside the firewall and after some thrash it worked. Well, it sort of worked ... sigh. It turns out I had downloaded the standard version instead of the enterprise version. I need to redo this work ... grrr. ## (/) I deleted all the tables in the Jira_Temp database and removed the /data/jira3135/indexes directory (and recreated). ## (/) I downloaded the enterprise version of the 3.13.5 server. I made a copy in the /opt directory and unzipped and untarred the file. ## (/) I went back to crowd and edited the application to change the properties to: ### URL: http://bugs.shore.mbari.org:8080 ### IP: 134.89.12.31 ### Name: jira3135 ### Password: (ask Kevin) :) ## (/) I then repeated the steps above to get the server up and running with the following differences: ### The server name is now bugs.shore.mbari.org ### The paths given above are a little different in that they no longer say "standard" but say "enterprise" ### I deleted the proxy pass as it seemed to have issues before and this is only temporary anyway. ## (/) I then browsed to http://bugs.shore.mbari.org:8080 ## (/) It took me to the start up page and at the top was the option to 'import your existing data'. Seemed too good not to try. I clicked on the link. It asked me for the backup file location and the location where the indexes would be stored. ## (/) I copied the XML zip file and the attachments tar file to the /data/original directory. ## (/) I created the /data/jira3135/indexes and used those directories ... it fired off the import and I waited. ## (/) I tailed the log file to watch the import. Holy crap, it worked!!! I could log in and everything! I copied the results from the log file here for posterity sake: {noformat} 2015-07-22 20:55:45,156 http-8080-Processor22 INFO [jira.action.admin.DataImport] Running data import 2015-07-22 20:55:45,179 http-8080-Processor22 INFO [jira.action.admin.DataImport] Importing data.. 2015-07-22 20:55:45,186 http-8080-Processor22 INFO [jira.action.admin.DataImport] Start parsing XML with SAX Parser 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] XML successfully parsed 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] Removing all entries from the database. 2015-07-22 20:56:24,593 http-8080-Processor22 INFO [jira.action.admin.DataImport] All entries removed. 2015-07-22 20:56:24,594 http-8080-Processor22 INFO [jira.action.admin.DataImport] Started storing 410414 Generic Values 2015-07-22 21:01:51,967 http-8080-Processor22 INFO [jira.action.admin.DataImport] Finished storing Generic Values 2015-07-22 21:01:52,329 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:52,361 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:54,683 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLink' to module 'jira.user.format:profile-link-user-format'. 2015-07-22 21:01:54,724 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullName' to module 'jira.user.format:full-name-user-format'. 2015-07-22 21:01:54,773 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkSearcher' to module 'jira.user.format:profile-link-searcher-user-format'. 2015-07-22 21:01:54,784 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkExternal' to module 'jira.user.format:profile-link-external-user-format'. 2015-07-22 21:01:54,795 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkActionHeader' to module 'jira.user.format:profile-link-action-header-user-format'. 2015-07-22 21:01:54,807 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullProfile' to module 'jira.user.format:full-profile-user-format'. 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/comments 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/issues 2015-07-22 21:01:55,641 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/plugins 2015-07-22 21:01:55,867 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:01:55,871 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/issues does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:55,873 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/comments does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,033 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,257 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,889 http-8080-Processor22 ERROR [atlassian.jira.upgrade.ConsistencyCheckImpl] Attachments are turned on, but attachment path [/data/jira_3_12/attachments] invalid - disabling attachments 2015-07-22 21:02:13,904 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Detected that an upgrade is needed; existing data at build 299 2015-07-22 21:02:13,907 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Doing Upgrade... 2015-07-22 21:02:13,915 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value' succeeded 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 317 2015-07-22 21:02:13,944 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite filters - make each filter a favourite of its owner. 2015-07-22 21:02:17,822 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build319] Could not find author 'fpy' for filter with id '10040' 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite filters - make each filter a favourite of its owner.' succeeded 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 319 2015-07-22 21:02:17,995 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise Share Permissions. Move old shares to new shares. 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise Share Permissions. Move old shares to new shares.' succeeded 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 321 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Migrating the old JIRA UI colors to the new JIRA 3.13 colors 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build322] Custom color detected for jira.lf.menu.bgcolour : #336699 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Migrating the old JIRA UI colors to the new JIRA 3.13 colors' succeeded 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 322 2015-07-22 21:02:18,025 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite dashboards - make each dashboard a favourite of its owner. 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'cmcgann' for dashboard with id '10030' 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'fpy' for dashboard with id '10060' 2015-07-22 21:02:18,423 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'kanna' for dashboard with id '10040' 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite dashboards - make each dashboard a favourite of its owner.' succeeded 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 325 2015-07-22 21:02:18,625 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Reindexing all data in JIRA to include Favourites. 2015-07-22 21:02:18,648 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All starting... 2015-07-22 21:02:18,650 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 0% complete. Current index: Issue 2015-07-22 21:02:18,654 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:02:18,809 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 1% complete. Current index: Issue 2015-07-22 21:02:18,855 indexerPool-2-thread-10 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 2% complete. Current index: Issue 2015-07-22 21:02:18,899 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 3% complete. Current index: Issue 2015-07-22 21:02:18,945 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 4% complete. Current index: Issue 2015-07-22 21:02:19,012 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 5% complete. Current index: Issue . . . 2015-07-22 21:02:26,164 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 95% complete. Current index: Issue 2015-07-22 21:02:26,232 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 96% complete. Current index: Issue 2015-07-22 21:02:26,316 indexerPool-2-thread-9 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 97% complete. Current index: Issue 2015-07-22 21:02:26,771 indexerPool-2-thread-3 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: Issue 2015-07-22 21:02:27,261 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 8607ms. Indexer: DefaultIndexManager: paths: [/data/jira3135/indexes/issues, /data/jira3135/indexes/comments] 2015-07-22 21:02:27,263 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: SearchRequest 2015-07-22 21:02:27,268 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,293 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: SearchRequest 2015-07-22 21:02:27,308 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: PortalPage 2015-07-22 21:02:27,312 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,377 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: PortalPage 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 115ms. Indexer: SharedEntityIndexManager: paths: [/data/jira3135/indexes/entities/portalpage, /data/jira3135/indexes/entities/searchrequest] 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All complete. Total time: 8722ms. 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Reindexing all data in JIRA to include Favourites.' succeeded 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 326 2015-07-22 21:02:27,397 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade succeeded! Setting data build number to 360 2015-07-22 21:02:27,469 JiraQuartzScheduler_Worker-0 WARN [service.services.export.ExportService] Backup directory /data/jira_3_12/backup does not exist {noformat} {warning:title=Paths} It appears that the upgraded JIRA will still look for the attachments and the backup locations in the original places. So I created /data/jira_3_12/backup and untarred the original attachments to /data/jira_3_12 and then everything worked (including attachements) in the new JIRA. {warning} ## (/) I then used the upgraded JIRA to generate a new XML backup and stored it in /data/original/3.13.5 along with another tar of the files in /data/jira_3_12/attachments. ## (/) I then shutdown the JIRA server. *I should be ready to move on to version 4 upgrade WHEW* ## So, before moving on, I decided that it would be a really good idea to spin up a new Crowd instance to get rid of the :8443 in the URL and to move off of RedHat per IS requests. I have a ticket in for a new VM and a new database to try to get this going. I am waiting on that before moving on. ## (/) Pat created the VM and Neil created the database. ## (/) I logged into auth.mbari.org (name of the VM) and downloaded crowd which I unzipped to the /opt directory ## (/) I then created a /data/crowd directory and gave my account permissions on it and then edited the /opt/atlassian..../crowd-webapp/WEB-INF/classes/crowd-init.properties file to set that as the crowd home directory. ## (/) The instructions say to download the JDBC driver, but they already have JTDS 1.2.7 in the download so I did not do anything. ## (/) You have to manually connect up CrowdID to a database as they setup wizard does not currently do this. ### (/) They say to download the driver, but again 1.2.7 was there so I did nothing. ### (/) I edited the /opt/atlassian.../apache-tomcat/conf/Catalina/localhost/openidserver.xml to look like: {noformat} {noformat} ### (/) I edited the /opt/atlassian.../build.properties files to look like: {noformat} # Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See https://confluence.atlassian.com/display/CROWD/Connecting+Crowd+to+a+Database hibernate.dialect=org.hibernate.dialect.SQLServerDialect # The Hibernate transaction factory to use. See https://confluence.atlassian.com/display/CROWD/Configuring+Crowd hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory # The http port you wish to run crowd from, ie: http://localhost:8095/crowd crowd.tomcat.connector.port=8095 # Tomcat requires a unique port for shutdown crowd.tomcat.shutdown.port=8020 # Crowd context root crowd.url=http://localhost:8095/crowd # Demo context root demo.url=http://localhost:8095/demo # OpenID server context root openidserver.url=http://localhost:8095/openidserver {noformat} ### (/) I then ran the build.sh script in the root of /opt/atlassian... ## (/) I fired up crowd using the /opt/atlassian.../start_crowd.sh script ## (/) I then went to http://auth.mbari.org:8095/crowd to kick off the start up wizard ## (/) I grabbed a new eval license from my account on atlassian and pasted into the license page. ## (/) I selected "New install" on the next page. ## (/) I configured the JDBC connection using this connection URL with user DB_Collaboration {noformat} jdbc:jtds:sqlserver://dione.mbari.org:51001/Crowd;domain=SHORE;useNTLMv2=TRUE {noformat} ## (/) I left the "Options" as they came up {warning:title=Paths} Not sure if this is a problem, but because I started the set up using auth.mbari.org, it set the Base URL to http://auth.mbari.org:8095/crowd instead of localhost. Hope that is not a problem. We will see. {warning} ## (/) I configured the email connection using the settings from [here|https://wind.shore.mbari.org/is/howto/email/mbarimail/imap] and I used my network login (probably shouldn't be doing that ... not sure where it stores my password, but I am assuming in the DB). ## (/) For the local admin account, I created a user named 'crowdadm' so it would not clash with my LDAP account. See Kevin Gomes for password information. ## (/) I checked the OpenID server as an integrated application ## (/) It then took me to the login page and I logged in using the newly minted admin account. Seemed all is well so far. ## (/) I visited the openidserver URL as well and that seemed OK. ## (/) I decided to wait on configuring the MBARI LDAP directory until I got everything with SSL working. ## (/) Now the next step was to follow the directions to configure Crowd to run over SSL found [here|https://confluence.atlassian.com/display/CROWD/Configuring+Crowd+to+Work+with+SSL] ## (/) I shutdown crowd. Note that the stop script does not shutdown things correctly and I noticed the crowd app running as root. That should not be if I started as kgomes. Not sure what is up with that. # Schedule upgrade date and send all hands several days in advance. # When the day arrives, send all hands announcing JIRA outage. # From the Administrator's page in our existing JIRA, perform a 'Backup Data to XML'. # Login to oceana.mbari.org as root. # Shutdown JIRA # Create a tar.gz of the /opt/atlassian-jira-enterprise-3.12.1-standalone directory # Clean up the /data/jira_3_12/backups directory by deleting all but maybe the last 5 backups. # Create a tar.gz of the JIRA home directory on ocean.mbari.org which is located at /data/jira_3_12 # scp both tar.gz files to bugs.mbari.org # login to bugs.mbari.org # Unpack the home directory tar to /data/jira # Run the installer as root (this might need IS help or sudo privs). Note that we usually install the application to /opt # Run the JIRA Configuration tool to set the jira.home to the /data/jira location # Connect to JIRA_Temp database on Solstice2 (.... more to do here, see Atlassian docs) # Migrate existing configuration over to new JIRA (I need to add more here as we added Crowd). # Start JIRA # Import backed up XML # Perform post upgrades checks and tests *Need to document steps for 4.4.5->6.X*]]> 27558117 27590875 4.4: [https://confluence.atlassian.com/display/JIRA044/Migrating+JIRA+to+Another+Server] ## The JIRA configuration tool: [https://confluence.atlassian.com/display/JIRA044/Using+the+JIRA+Configuration+Tool] h5. Steps # (/) Create new VM named bugs.mbari.org in the DMZ # (/) Have Neil create database Jira_Temp on solstice2.shore.mbari.org # (/) Have Neil create database Jira on solstice2.shore.mbari.org # (/) Have Pat install Java 7 on bugs.shore.mbari.org # (/) Have Pete plumb holes through firewall so processes on bugs.mbari.org can get to Solstice2 # (/) Have Pat create DB_Collaboration account on bugs so it can run JIRA under that account and it can connect to solstice2 using that NT Domain account. # (/) Upgrade license on Atlassian site # (/) Log into bugs.shore.mbari.org # (/) Download 3.13.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 4.4.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 5.2.11 standalone Linux 64 bit tar.gz (not sure this version is necessary, but at least I have it) # (/) Unzip and untar the file to /opt # (/) Download latest JIRA (6.4.7 as of this writing). # (/) Unzip and untar it to /opt # Performed Test Upgrade ## (/) In order to export the current stuff in JIRA, I had to shut off access so people could not change the data while I was backing it up. ## (/) I ssh'd to oceana.mbari.org as root and edited the /opt/jira/conf/server.xml file and commented out the Connector section that had the port of 8010 to shut it off from the normal serving route. ## (/) I uncommented the 8082 port connector and the 8443 port connector so that I could still get to the server. ## (/) I stopped and started the JIRA server and in the log file I got a "keystore was tampered with..." which is not surprising. ## (/) I could then browser over to http://oceana.mbari.org:8082/jira ## (/) Then through the Administration console, I did an XML backup ## (/) I then created a tar of all the attachments in the /data/jira_3_12/attachments directory ## (/) I moved both the XML and tar files to the /root/jira-upgrade directory ## (/) I then reversed the changes to the server.xml file and shut down JIRA ## (/) I left it down during the next steps in case it went so well, I could just point people to the new server (yeah, right). ## (/) I then browsed to the crowd server on oceana and add a new application using: ### URL: http://bugs.mbari.org/jira3135 ### IP: 134.89.2.29 ### Name: JIRA3135 ### Password: (ask Kevin) :) ## (/) On bugs, I made a copy of the JIRA 3.13.5 download in the /opt directory and unzipped and untarred it. ## (/) In order to configure the crowd connection I did the following: ### (/) I scp'd the /opt/crowd/client/crowd-integration-client-1.6.jar file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I removed the existing 1.6.1 crowd client jar from the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I scp'd the /opt/crowd/client/conf/crowd.properties file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I scp'd the /opt/crowd/client/conf/crowd-ehcache.xml file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I edited the crowd.properties file on bugs to look like: {noformat} application.name JIRA3135 application.password (ask Kevin) application.login.url http://oceana.mbari.org:8095/crowd/console/ crowd.server.url http://oceana.mbari.org:8095/crowd/services/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 0 session.lastvalidation session.lastvalidation {noformat} ### (/) I edited the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/osuser.xml file to comment out the current authentication mechanism and then uncomment the crowd one. ## (/) I then edited the /opt/atlassian-jira-standalone-3.13.5/conf/server/xml file and configured the database connection to the Jira_Temp database on Solstice2. I looked like this: {noformat} {noformat} ## (/) Edit the /opt/atlassian/jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/entityengine.xml and changed it from 'hsql' to 'mssql' and delete the line with "PUBLIC" in it per the instructions in the comments in that file. ## (/) I edited the /etc/httpd/conf/httpd.conf file and created a proxy pass at the bottom of the file to point a normal URL to the default port 8080 for JIRA: {noformat} # Proxy Pass for JIRA ProxyPass http://bugs.mbari.org:8080 ProxyPassReverse http://bugs.mbari.org:8080 {noformat} ## (/) I restarted Apache ## (/) I scp'd the jtds driver from oceana to the /opt/atlassian-jira-standalone-3.13.5/common/lib directory (you could down from the internet) ## (/) I then went to the /opt/atlassian-jira-standalone-3.13.5/ directory and ran './bin/startup.sh'. From the log file, I could tell things were hanging. After some troubleshooting I am wondering if the local firewall is preventing the application to get access to the database on solstice2. I can telnet to port 1433, but I can't browse to the base http://bugs.mbari.org from anywhere but the local web browser. I have submitted a ticket. ## (/) I restarted the old JIRA with my hopes dashed :(. ## (/) Pat disabled the firewall on bugs.mbari.org but it still hung trying to connect to solstice2.shore.mbari.org. That is really, really perplexing. Neil mentioned that solstice2 is using Kerberos and solstice is not. Checking with the JTDS docs, version 1.3.1 of the driver added kerberos support, so I downloaded that driver and added the 'userKerberos=true' property to the URL in the server.xml file and restarted. Got an error about no credentials, so added user and password properties to the URL. Nope, no luck. Never did figure this one out, but I had Pat pull the VM inside the firewall and after some thrash it worked. Well, it sort of worked ... sigh. It turns out I had downloaded the standard version instead of the enterprise version. I need to redo this work ... grrr. ## (/) I deleted all the tables in the Jira_Temp database and removed the /data/jira3135/indexes directory (and recreated). ## (/) I downloaded the enterprise version of the 3.13.5 server. I made a copy in the /opt directory and unzipped and untarred the file. ## (/) I went back to crowd and edited the application to change the properties to: ### URL: http://bugs.shore.mbari.org:8080 ### IP: 134.89.12.31 ### Name: jira3135 ### Password: (ask Kevin) :) ## (/) I then repeated the steps above to get the server up and running with the following differences: ### The server name is now bugs.shore.mbari.org ### The paths given above are a little different in that they no longer say "standard" but say "enterprise" ### I deleted the proxy pass as it seemed to have issues before and this is only temporary anyway. ## (/) I then browsed to http://bugs.shore.mbari.org:8080 ## (/) It took me to the start up page and at the top was the option to 'import your existing data'. Seemed too good not to try. I clicked on the link. It asked me for the backup file location and the location where the indexes would be stored. ## (/) I copied the XML zip file and the attachments tar file to the /data/original directory. ## (/) I created the /data/jira3135/indexes and used those directories ... it fired off the import and I waited. ## (/) I tailed the log file to watch the import. Holy crap, it worked!!! I could log in and everything! I copied the results from the log file here for posterity sake: {noformat} 2015-07-22 20:55:45,156 http-8080-Processor22 INFO [jira.action.admin.DataImport] Running data import 2015-07-22 20:55:45,179 http-8080-Processor22 INFO [jira.action.admin.DataImport] Importing data.. 2015-07-22 20:55:45,186 http-8080-Processor22 INFO [jira.action.admin.DataImport] Start parsing XML with SAX Parser 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] XML successfully parsed 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] Removing all entries from the database. 2015-07-22 20:56:24,593 http-8080-Processor22 INFO [jira.action.admin.DataImport] All entries removed. 2015-07-22 20:56:24,594 http-8080-Processor22 INFO [jira.action.admin.DataImport] Started storing 410414 Generic Values 2015-07-22 21:01:51,967 http-8080-Processor22 INFO [jira.action.admin.DataImport] Finished storing Generic Values 2015-07-22 21:01:52,329 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:52,361 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:54,683 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLink' to module 'jira.user.format:profile-link-user-format'. 2015-07-22 21:01:54,724 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullName' to module 'jira.user.format:full-name-user-format'. 2015-07-22 21:01:54,773 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkSearcher' to module 'jira.user.format:profile-link-searcher-user-format'. 2015-07-22 21:01:54,784 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkExternal' to module 'jira.user.format:profile-link-external-user-format'. 2015-07-22 21:01:54,795 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkActionHeader' to module 'jira.user.format:profile-link-action-header-user-format'. 2015-07-22 21:01:54,807 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullProfile' to module 'jira.user.format:full-profile-user-format'. 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/comments 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/issues 2015-07-22 21:01:55,641 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/plugins 2015-07-22 21:01:55,867 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:01:55,871 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/issues does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:55,873 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/comments does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,033 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,257 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,889 http-8080-Processor22 ERROR [atlassian.jira.upgrade.ConsistencyCheckImpl] Attachments are turned on, but attachment path [/data/jira_3_12/attachments] invalid - disabling attachments 2015-07-22 21:02:13,904 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Detected that an upgrade is needed; existing data at build 299 2015-07-22 21:02:13,907 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Doing Upgrade... 2015-07-22 21:02:13,915 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value' succeeded 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 317 2015-07-22 21:02:13,944 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite filters - make each filter a favourite of its owner. 2015-07-22 21:02:17,822 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build319] Could not find author 'fpy' for filter with id '10040' 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite filters - make each filter a favourite of its owner.' succeeded 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 319 2015-07-22 21:02:17,995 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise Share Permissions. Move old shares to new shares. 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise Share Permissions. Move old shares to new shares.' succeeded 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 321 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Migrating the old JIRA UI colors to the new JIRA 3.13 colors 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build322] Custom color detected for jira.lf.menu.bgcolour : #336699 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Migrating the old JIRA UI colors to the new JIRA 3.13 colors' succeeded 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 322 2015-07-22 21:02:18,025 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite dashboards - make each dashboard a favourite of its owner. 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'cmcgann' for dashboard with id '10030' 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'fpy' for dashboard with id '10060' 2015-07-22 21:02:18,423 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'kanna' for dashboard with id '10040' 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite dashboards - make each dashboard a favourite of its owner.' succeeded 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 325 2015-07-22 21:02:18,625 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Reindexing all data in JIRA to include Favourites. 2015-07-22 21:02:18,648 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All starting... 2015-07-22 21:02:18,650 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 0% complete. Current index: Issue 2015-07-22 21:02:18,654 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:02:18,809 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 1% complete. Current index: Issue 2015-07-22 21:02:18,855 indexerPool-2-thread-10 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 2% complete. Current index: Issue 2015-07-22 21:02:18,899 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 3% complete. Current index: Issue 2015-07-22 21:02:18,945 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 4% complete. Current index: Issue 2015-07-22 21:02:19,012 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 5% complete. Current index: Issue . . . 2015-07-22 21:02:26,164 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 95% complete. Current index: Issue 2015-07-22 21:02:26,232 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 96% complete. Current index: Issue 2015-07-22 21:02:26,316 indexerPool-2-thread-9 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 97% complete. Current index: Issue 2015-07-22 21:02:26,771 indexerPool-2-thread-3 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: Issue 2015-07-22 21:02:27,261 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 8607ms. Indexer: DefaultIndexManager: paths: [/data/jira3135/indexes/issues, /data/jira3135/indexes/comments] 2015-07-22 21:02:27,263 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: SearchRequest 2015-07-22 21:02:27,268 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,293 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: SearchRequest 2015-07-22 21:02:27,308 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: PortalPage 2015-07-22 21:02:27,312 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,377 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: PortalPage 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 115ms. Indexer: SharedEntityIndexManager: paths: [/data/jira3135/indexes/entities/portalpage, /data/jira3135/indexes/entities/searchrequest] 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All complete. Total time: 8722ms. 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Reindexing all data in JIRA to include Favourites.' succeeded 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 326 2015-07-22 21:02:27,397 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade succeeded! Setting data build number to 360 2015-07-22 21:02:27,469 JiraQuartzScheduler_Worker-0 WARN [service.services.export.ExportService] Backup directory /data/jira_3_12/backup does not exist {noformat} {warning:title=Paths} It appears that the upgraded JIRA will still look for the attachments and the backup locations in the original places. So I created /data/jira_3_12/backup and untarred the original attachments to /data/jira_3_12 and then everything worked (including attachements) in the new JIRA. {warning} ## (/) I then used the upgraded JIRA to generate a new XML backup and stored it in /data/original/3.13.5 along with another tar of the files in /data/jira_3_12/attachments. ## (/) I then shutdown the JIRA server. *I should be ready to move on to version 4 upgrade WHEW* ## So, before moving on, I decided that it would be a really good idea to spin up a new Crowd instance to get rid of the :8443 in the URL and to move off of RedHat per IS requests. I have a ticket in for a new VM and a new database to try to get this going. I am waiting on that before moving on. ## (/) Pat created the VM and Neil created the database. ## (/) I logged into auth.mbari.org (name of the VM) and downloaded crowd which I unzipped to the /opt directory ## (/) I then created a /data/crowd directory and gave my account permissions on it and then edited the /opt/atlassian..../crowd-webapp/WEB-INF/classes/crowd-init.properties file to set that as the crowd home directory. ## (/) The instructions say to download the JDBC driver, but they already have JTDS 1.2.7 in the download so I did not do anything. ## (/) You have to manually connect up CrowdID to a database as they setup wizard does not currently do this. ### (/) They say to download the driver, but again 1.2.7 was there so I did nothing. ### (/) I edited the /opt/atlassian.../apache-tomcat/conf/Catalina/localhost/openidserver.xml to look like: {noformat} {noformat} ### (/) I edited the /opt/atlassian.../build.properties files to look like: {noformat} # Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See https://confluence.atlassian.com/display/CROWD/Connecting+Crowd+to+a+Database hibernate.dialect=org.hibernate.dialect.SQLServerDialect # The Hibernate transaction factory to use. See https://confluence.atlassian.com/display/CROWD/Configuring+Crowd hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory # The http port you wish to run crowd from, ie: http://localhost:8095/crowd crowd.tomcat.connector.port=8095 # Tomcat requires a unique port for shutdown crowd.tomcat.shutdown.port=8020 # Crowd context root crowd.url=http://localhost:8095/crowd # Demo context root demo.url=http://localhost:8095/demo # OpenID server context root openidserver.url=http://localhost:8095/openidserver {noformat} ### (/) I then ran the build.sh script in the root of /opt/atlassian... ## (/) I fired up crowd using the /opt/atlassian.../start_crowd.sh script ## (/) I then went to http://auth.mbari.org:8095/crowd to kick off the start up wizard ## (/) I grabbed a new eval license from my account on atlassian and pasted into the license page. ## (/) I selected "New install" on the next page. ## (/) I configured the JDBC connection using this connection URL with user DB_Collaboration {noformat} jdbc:jtds:sqlserver://dione.mbari.org:51001/Crowd;domain=SHORE;useNTLMv2=TRUE {noformat} ## (/) I left the "Options" as they came up {warning:title=Paths} Not sure if this is a problem, but because I started the set up using auth.mbari.org, it set the Base URL to http://auth.mbari.org:8095/crowd instead of localhost. Hope that is not a problem. We will see. {warning} ## (/) I configured the email connection using the settings from [here|https://wind.shore.mbari.org/is/howto/email/mbarimail/imap] and I used my network login (probably shouldn't be doing that ... not sure where it stores my password, but I am assuming in the DB). ## (/) For the local admin account, I created a user named 'crowdadm' so it would not clash with my LDAP account. See Kevin Gomes for password information. ## (/) I checked the OpenID server as an integrated application ## (/) I fired up crowd and then went to the http://localhost:8095 URL to start the configuration. I input the DB connection parameters and it created the DB and took off just fine. I really wanted to run the application on port 80 and 443 as normal applications do so I first tried to change the port numbers that the application ran on. That did not work as those are privileged ports and cannot be controller unless you are root. I did not want to do that, so I will have to do a proxy pass. I had to start up the httpd services (I will need to configure as a service) and then created a new file in /etc/httpd/conf.d called crowd.conf that contained the following: {noformat} # This is the configuration for the proxy pass for the crowd server ProxyRequests Off ProxyPreserveHost On Require all granted ProxyPass /crowd http://auth.mbari.org:8095/crowd ProxyPassReverse /crowd http://auth.mbari.org:8095/crowd Require all granted ProxyPass /openidserver http://auth.mbari.org:8095/openidserver ProxyPassReverse /openidserver http://auth.mbari.org:8095/openidserver Require all granted {noformat} ## (/) This worked for the basic HTTP so I will have to get it working with SSL. ## (/) Something with the openidserver is not working correctly and I suspect I have not done the openidserver install completely or correctly. I read the directions on configuring crowdid and it's connection to the database and restarted the crowd server. That worked, not I have both working of straight HTTP, now I need to get SSL going. ## (/) I originally started to configure SSL for the Tomcat server for Crowd, but then realized, since I am putting the Apache proxy in front of Tomcat, I should be able to just set up SSL on Apache HTTP and leave Tomcat alone (i.e. traffic between Apache HTTP and Tomcat does not need to be encrypted). # Schedule upgrade date and send all hands several days in advance. # When the day arrives, send all hands announcing JIRA outage. # From the Administrator's page in our existing JIRA, perform a 'Backup Data to XML'. # Login to oceana.mbari.org as root. # Shutdown JIRA # Create a tar.gz of the /opt/atlassian-jira-enterprise-3.12.1-standalone directory # Clean up the /data/jira_3_12/backups directory by deleting all but maybe the last 5 backups. # Create a tar.gz of the JIRA home directory on ocean.mbari.org which is located at /data/jira_3_12 # scp both tar.gz files to bugs.mbari.org # login to bugs.mbari.org # Unpack the home directory tar to /data/jira # Run the installer as root (this might need IS help or sudo privs). Note that we usually install the application to /opt # Run the JIRA Configuration tool to set the jira.home to the /data/jira location # Connect to JIRA_Temp database on Solstice2 (.... more to do here, see Atlassian docs) # Migrate existing configuration over to new JIRA (I need to add more here as we added Crowd). # Start JIRA # Import backed up XML # Perform post upgrades checks and tests *Need to document steps for 4.4.5->6.X*]]> 27558110 27100038 27067284 27590877 4.4: [https://confluence.atlassian.com/display/JIRA044/Migrating+JIRA+to+Another+Server] ## The JIRA configuration tool: [https://confluence.atlassian.com/display/JIRA044/Using+the+JIRA+Configuration+Tool] h5. Steps # (/) Create new VM named bugs.mbari.org in the DMZ # (/) Have Neil create database Jira_Temp on solstice2.shore.mbari.org # (/) Have Neil create database Jira on solstice2.shore.mbari.org # (/) Have Pat install Java 7 on bugs.shore.mbari.org # (/) Have Pete plumb holes through firewall so processes on bugs.mbari.org can get to Solstice2 # (/) Have Pat create DB_Collaboration account on bugs so it can run JIRA under that account and it can connect to solstice2 using that NT Domain account. # (/) Upgrade license on Atlassian site # (/) Log into bugs.shore.mbari.org # (/) Download 3.13.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 4.4.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 5.2.11 standalone Linux 64 bit tar.gz (not sure this version is necessary, but at least I have it) # (/) Unzip and untar the file to /opt # (/) Download latest JIRA (6.4.7 as of this writing). # (/) Unzip and untar it to /opt # Performed Test Upgrade ## (/) In order to export the current stuff in JIRA, I had to shut off access so people could not change the data while I was backing it up. ## (/) I ssh'd to oceana.mbari.org as root and edited the /opt/jira/conf/server.xml file and commented out the Connector section that had the port of 8010 to shut it off from the normal serving route. ## (/) I uncommented the 8082 port connector and the 8443 port connector so that I could still get to the server. ## (/) I stopped and started the JIRA server and in the log file I got a "keystore was tampered with..." which is not surprising. ## (/) I could then browser over to http://oceana.mbari.org:8082/jira ## (/) Then through the Administration console, I did an XML backup ## (/) I then created a tar of all the attachments in the /data/jira_3_12/attachments directory ## (/) I moved both the XML and tar files to the /root/jira-upgrade directory ## (/) I then reversed the changes to the server.xml file and shut down JIRA ## (/) I left it down during the next steps in case it went so well, I could just point people to the new server (yeah, right). ## (/) I then browsed to the crowd server on oceana and add a new application using: ### URL: http://bugs.mbari.org/jira3135 ### IP: 134.89.2.29 ### Name: JIRA3135 ### Password: (ask Kevin) :) ## (/) On bugs, I made a copy of the JIRA 3.13.5 download in the /opt directory and unzipped and untarred it. ## (/) In order to configure the crowd connection I did the following: ### (/) I scp'd the /opt/crowd/client/crowd-integration-client-1.6.jar file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I removed the existing 1.6.1 crowd client jar from the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I scp'd the /opt/crowd/client/conf/crowd.properties file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I scp'd the /opt/crowd/client/conf/crowd-ehcache.xml file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I edited the crowd.properties file on bugs to look like: {noformat} application.name JIRA3135 application.password (ask Kevin) application.login.url http://oceana.mbari.org:8095/crowd/console/ crowd.server.url http://oceana.mbari.org:8095/crowd/services/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 0 session.lastvalidation session.lastvalidation {noformat} ### (/) I edited the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/osuser.xml file to comment out the current authentication mechanism and then uncomment the crowd one. ## (/) I then edited the /opt/atlassian-jira-standalone-3.13.5/conf/server/xml file and configured the database connection to the Jira_Temp database on Solstice2. I looked like this: {noformat} {noformat} ## (/) Edit the /opt/atlassian/jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/entityengine.xml and changed it from 'hsql' to 'mssql' and delete the line with "PUBLIC" in it per the instructions in the comments in that file. ## (/) I edited the /etc/httpd/conf/httpd.conf file and created a proxy pass at the bottom of the file to point a normal URL to the default port 8080 for JIRA: {noformat} # Proxy Pass for JIRA ProxyPass http://bugs.mbari.org:8080 ProxyPassReverse http://bugs.mbari.org:8080 {noformat} ## (/) I restarted Apache ## (/) I scp'd the jtds driver from oceana to the /opt/atlassian-jira-standalone-3.13.5/common/lib directory (you could down from the internet) ## (/) I then went to the /opt/atlassian-jira-standalone-3.13.5/ directory and ran './bin/startup.sh'. From the log file, I could tell things were hanging. After some troubleshooting I am wondering if the local firewall is preventing the application to get access to the database on solstice2. I can telnet to port 1433, but I can't browse to the base http://bugs.mbari.org from anywhere but the local web browser. I have submitted a ticket. ## (/) I restarted the old JIRA with my hopes dashed :(. ## (/) Pat disabled the firewall on bugs.mbari.org but it still hung trying to connect to solstice2.shore.mbari.org. That is really, really perplexing. Neil mentioned that solstice2 is using Kerberos and solstice is not. Checking with the JTDS docs, version 1.3.1 of the driver added kerberos support, so I downloaded that driver and added the 'userKerberos=true' property to the URL in the server.xml file and restarted. Got an error about no credentials, so added user and password properties to the URL. Nope, no luck. Never did figure this one out, but I had Pat pull the VM inside the firewall and after some thrash it worked. Well, it sort of worked ... sigh. It turns out I had downloaded the standard version instead of the enterprise version. I need to redo this work ... grrr. ## (/) I deleted all the tables in the Jira_Temp database and removed the /data/jira3135/indexes directory (and recreated). ## (/) I downloaded the enterprise version of the 3.13.5 server. I made a copy in the /opt directory and unzipped and untarred the file. ## (/) I went back to crowd and edited the application to change the properties to: ### URL: http://bugs.shore.mbari.org:8080 ### IP: 134.89.12.31 ### Name: jira3135 ### Password: (ask Kevin) :) ## (/) I then repeated the steps above to get the server up and running with the following differences: ### The server name is now bugs.shore.mbari.org ### The paths given above are a little different in that they no longer say "standard" but say "enterprise" ### I deleted the proxy pass as it seemed to have issues before and this is only temporary anyway. ## (/) I then browsed to http://bugs.shore.mbari.org:8080 ## (/) It took me to the start up page and at the top was the option to 'import your existing data'. Seemed too good not to try. I clicked on the link. It asked me for the backup file location and the location where the indexes would be stored. ## (/) I copied the XML zip file and the attachments tar file to the /data/original directory. ## (/) I created the /data/jira3135/indexes and used those directories ... it fired off the import and I waited. ## (/) I tailed the log file to watch the import. Holy crap, it worked!!! I could log in and everything! I copied the results from the log file here for posterity sake: {noformat} 2015-07-22 20:55:45,156 http-8080-Processor22 INFO [jira.action.admin.DataImport] Running data import 2015-07-22 20:55:45,179 http-8080-Processor22 INFO [jira.action.admin.DataImport] Importing data.. 2015-07-22 20:55:45,186 http-8080-Processor22 INFO [jira.action.admin.DataImport] Start parsing XML with SAX Parser 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] XML successfully parsed 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] Removing all entries from the database. 2015-07-22 20:56:24,593 http-8080-Processor22 INFO [jira.action.admin.DataImport] All entries removed. 2015-07-22 20:56:24,594 http-8080-Processor22 INFO [jira.action.admin.DataImport] Started storing 410414 Generic Values 2015-07-22 21:01:51,967 http-8080-Processor22 INFO [jira.action.admin.DataImport] Finished storing Generic Values 2015-07-22 21:01:52,329 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:52,361 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:54,683 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLink' to module 'jira.user.format:profile-link-user-format'. 2015-07-22 21:01:54,724 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullName' to module 'jira.user.format:full-name-user-format'. 2015-07-22 21:01:54,773 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkSearcher' to module 'jira.user.format:profile-link-searcher-user-format'. 2015-07-22 21:01:54,784 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkExternal' to module 'jira.user.format:profile-link-external-user-format'. 2015-07-22 21:01:54,795 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkActionHeader' to module 'jira.user.format:profile-link-action-header-user-format'. 2015-07-22 21:01:54,807 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullProfile' to module 'jira.user.format:full-profile-user-format'. 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/comments 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/issues 2015-07-22 21:01:55,641 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/plugins 2015-07-22 21:01:55,867 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:01:55,871 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/issues does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:55,873 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/comments does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,033 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,257 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,889 http-8080-Processor22 ERROR [atlassian.jira.upgrade.ConsistencyCheckImpl] Attachments are turned on, but attachment path [/data/jira_3_12/attachments] invalid - disabling attachments 2015-07-22 21:02:13,904 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Detected that an upgrade is needed; existing data at build 299 2015-07-22 21:02:13,907 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Doing Upgrade... 2015-07-22 21:02:13,915 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value' succeeded 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 317 2015-07-22 21:02:13,944 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite filters - make each filter a favourite of its owner. 2015-07-22 21:02:17,822 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build319] Could not find author 'fpy' for filter with id '10040' 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite filters - make each filter a favourite of its owner.' succeeded 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 319 2015-07-22 21:02:17,995 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise Share Permissions. Move old shares to new shares. 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise Share Permissions. Move old shares to new shares.' succeeded 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 321 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Migrating the old JIRA UI colors to the new JIRA 3.13 colors 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build322] Custom color detected for jira.lf.menu.bgcolour : #336699 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Migrating the old JIRA UI colors to the new JIRA 3.13 colors' succeeded 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 322 2015-07-22 21:02:18,025 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite dashboards - make each dashboard a favourite of its owner. 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'cmcgann' for dashboard with id '10030' 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'fpy' for dashboard with id '10060' 2015-07-22 21:02:18,423 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'kanna' for dashboard with id '10040' 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite dashboards - make each dashboard a favourite of its owner.' succeeded 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 325 2015-07-22 21:02:18,625 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Reindexing all data in JIRA to include Favourites. 2015-07-22 21:02:18,648 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All starting... 2015-07-22 21:02:18,650 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 0% complete. Current index: Issue 2015-07-22 21:02:18,654 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:02:18,809 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 1% complete. Current index: Issue 2015-07-22 21:02:18,855 indexerPool-2-thread-10 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 2% complete. Current index: Issue 2015-07-22 21:02:18,899 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 3% complete. Current index: Issue 2015-07-22 21:02:18,945 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 4% complete. Current index: Issue 2015-07-22 21:02:19,012 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 5% complete. Current index: Issue . . . 2015-07-22 21:02:26,164 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 95% complete. Current index: Issue 2015-07-22 21:02:26,232 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 96% complete. Current index: Issue 2015-07-22 21:02:26,316 indexerPool-2-thread-9 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 97% complete. Current index: Issue 2015-07-22 21:02:26,771 indexerPool-2-thread-3 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: Issue 2015-07-22 21:02:27,261 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 8607ms. Indexer: DefaultIndexManager: paths: [/data/jira3135/indexes/issues, /data/jira3135/indexes/comments] 2015-07-22 21:02:27,263 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: SearchRequest 2015-07-22 21:02:27,268 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,293 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: SearchRequest 2015-07-22 21:02:27,308 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: PortalPage 2015-07-22 21:02:27,312 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,377 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: PortalPage 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 115ms. Indexer: SharedEntityIndexManager: paths: [/data/jira3135/indexes/entities/portalpage, /data/jira3135/indexes/entities/searchrequest] 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All complete. Total time: 8722ms. 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Reindexing all data in JIRA to include Favourites.' succeeded 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 326 2015-07-22 21:02:27,397 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade succeeded! Setting data build number to 360 2015-07-22 21:02:27,469 JiraQuartzScheduler_Worker-0 WARN [service.services.export.ExportService] Backup directory /data/jira_3_12/backup does not exist {noformat} {warning:title=Paths} It appears that the upgraded JIRA will still look for the attachments and the backup locations in the original places. So I created /data/jira_3_12/backup and untarred the original attachments to /data/jira_3_12 and then everything worked (including attachements) in the new JIRA. {warning} ## (/) I then used the upgraded JIRA to generate a new XML backup and stored it in /data/original/3.13.5 along with another tar of the files in /data/jira_3_12/attachments. ## (/) I then shutdown the JIRA server. *I should be ready to move on to version 4 upgrade WHEW* ## So, before moving on, I decided that it would be a really good idea to spin up a new Crowd instance to get rid of the :8443 in the URL and to move off of RedHat per IS requests. I have a ticket in for a new VM and a new database to try to get this going. I am waiting on that before moving on. ## (/) Pat created the VM and Neil created the database. ## (/) I logged into auth.mbari.org (name of the VM) and downloaded crowd which I unzipped to the /opt directory ## (/) I then created a /data/crowd directory and gave my account permissions on it and then edited the /opt/atlassian..../crowd-webapp/WEB-INF/classes/crowd-init.properties file to set that as the crowd home directory. ## (/) The instructions say to download the JDBC driver, but they already have JTDS 1.2.7 in the download so I did not do anything. ## (/) You have to manually connect up CrowdID to a database as they setup wizard does not currently do this. ### (/) They say to download the driver, but again 1.2.7 was there so I did nothing. ### (/) I edited the /opt/atlassian.../apache-tomcat/conf/Catalina/localhost/openidserver.xml to look like: {noformat} {noformat} ### (/) I edited the /opt/atlassian.../build.properties files to look like: {noformat} # Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See https://confluence.atlassian.com/display/CROWD/Connecting+Crowd+to+a+Database hibernate.dialect=org.hibernate.dialect.SQLServerDialect # The Hibernate transaction factory to use. See https://confluence.atlassian.com/display/CROWD/Configuring+Crowd hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory # The http port you wish to run crowd from, ie: http://localhost:8095/crowd crowd.tomcat.connector.port=8095 # Tomcat requires a unique port for shutdown crowd.tomcat.shutdown.port=8020 # Crowd context root crowd.url=http://localhost:8095/crowd # Demo context root demo.url=http://localhost:8095/demo # OpenID server context root openidserver.url=http://localhost:8095/openidserver {noformat} ### (/) I then ran the build.sh script in the root of /opt/atlassian... ## (/) I fired up crowd using the /opt/atlassian.../start_crowd.sh script ## (/) I then went to http://auth.mbari.org:8095/crowd to kick off the start up wizard ## (/) I grabbed a new eval license from my account on atlassian and pasted into the license page. ## (/) I selected "New install" on the next page. ## (/) I configured the JDBC connection using this connection URL with user DB_Collaboration {noformat} jdbc:jtds:sqlserver://dione.mbari.org:51001/Crowd;domain=SHORE;useNTLMv2=TRUE {noformat} ## (/) I left the "Options" as they came up {warning:title=Paths} Not sure if this is a problem, but because I started the set up using auth.mbari.org, it set the Base URL to http://auth.mbari.org:8095/crowd instead of localhost. Hope that is not a problem. We will see. {warning} ## (/) I configured the email connection using the settings from [here|https://wind.shore.mbari.org/is/howto/email/mbarimail/imap] and I used my network login (probably shouldn't be doing that ... not sure where it stores my password, but I am assuming in the DB). ## (/) For the local admin account, I created a user named 'crowdadm' so it would not clash with my LDAP account. See Kevin Gomes for password information. ## (/) I checked the OpenID server as an integrated application ## (/) It then took me to the login page and I logged in using the newly minted admin account. Seemed all is well so far. ## (/) I fired up crowd and then went to the http://localhost:8095 URL to start the configuration. I input the DB connection parameters and it created the DB and took off just fine. I really wanted to run the application on port 80 and 443 as normal applications do so I first tried to change the port numbers that the application ran on. That did not work as those are privileged ports and cannot be controller unless you are root. I did not want to do that, so I will have to do a proxy pass. I had to start up the httpd services (I will need to configure as a service) and then created a new file in /etc/httpd/conf.d called crowd.conf that contained the following: {noformat} # This is the configuration for the proxy pass for the crowd server ProxyRequests Off ProxyPreserveHost On Require all granted ProxyPass /crowd http://auth.mbari.org:8095/crowd ProxyPassReverse /crowd http://auth.mbari.org:8095/crowd Require all granted ProxyPass /openidserver http://auth.mbari.org:8095/openidserver ProxyPassReverse /openidserver http://auth.mbari.org:8095/openidserver Require all granted {noformat} ## (/) This worked for the basic HTTP so I will have to get it working with SSL. ## (/) Something with the openidserver is not working correctly and I suspect I have not done the openidserver install completely or correctly. I read the directions on configuring crowdid and it's connection to the database and restarted the crowd server. That worked, not I have both working of straight HTTP, now I need to get SSL going. ## (/) I originally started to configure SSL for the Tomcat server for Crowd, but then realized, since I am putting the Apache proxy in front of Tomcat, I should be able to just set up SSL on Apache HTTP and leave Tomcat alone (i.e. traffic between Apache HTTP and Tomcat does not need to be encrypted). # Schedule upgrade date and send all hands several days in advance. # When the day arrives, send all hands announcing JIRA outage. # From the Administrator's page in our existing JIRA, perform a 'Backup Data to XML'. # Login to oceana.mbari.org as root. # Shutdown JIRA # Create a tar.gz of the /opt/atlassian-jira-enterprise-3.12.1-standalone directory # Clean up the /data/jira_3_12/backups directory by deleting all but maybe the last 5 backups. # Create a tar.gz of the JIRA home directory on ocean.mbari.org which is located at /data/jira_3_12 # scp both tar.gz files to bugs.mbari.org # login to bugs.mbari.org # Unpack the home directory tar to /data/jira # Run the installer as root (this might need IS help or sudo privs). Note that we usually install the application to /opt # Run the JIRA Configuration tool to set the jira.home to the /data/jira location # Connect to JIRA_Temp database on Solstice2 (.... more to do here, see Atlassian docs) # Migrate existing configuration over to new JIRA (I need to add more here as we added Crowd). # Start JIRA # Import backed up XML # Perform post upgrades checks and tests *Need to document steps for 4.4.5->6.X*]]> 27558112 13959352 {noformat} Lastly, I edited the /opt/jboss/server/default/deploy/jbossweb-tomcat55.sar/META-INF/jboss-service.xml and changed the following line: {noformat} false {noformat} to: {noformat} true {noformat} Then I restarted JBoss.]]> 13926590 27590872 4.4: [https://confluence.atlassian.com/display/JIRA044/Migrating+JIRA+to+Another+Server] ## The JIRA configuration tool: [https://confluence.atlassian.com/display/JIRA044/Using+the+JIRA+Configuration+Tool] h5. Steps # (/) Create new VM named bugs.mbari.org in the DMZ # (/) Have Neil create database Jira_Temp on solstice2.shore.mbari.org # (/) Have Neil create database Jira on solstice2.shore.mbari.org # (/) Have Pat install Java 7 on bugs.shore.mbari.org # (/) Have Pete plumb holes through firewall so processes on bugs.mbari.org can get to Solstice2 # (/) Have Pat create DB_Collaboration account on bugs so it can run JIRA under that account and it can connect to solstice2 using that NT Domain account. # (/) Upgrade license on Atlassian site # (/) Log into bugs.shore.mbari.org # (/) Download 3.13.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 4.4.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 5.2.11 standalone Linux 64 bit tar.gz (not sure this version is necessary, but at least I have it) # (/) Unzip and untar the file to /opt # (/) Download latest JIRA (6.4.7 as of this writing). # (/) Unzip and untar it to /opt # Performed Test Upgrade ## (/) In order to export the current stuff in JIRA, I had to shut off access so people could not change the data while I was backing it up. ## (/) I ssh'd to oceana.mbari.org as root and edited the /opt/jira/conf/server.xml file and commented out the Connector section that had the port of 8010 to shut it off from the normal serving route. ## (/) I uncommented the 8082 port connector and the 8443 port connector so that I could still get to the server. ## (/) I stopped and started the JIRA server and in the log file I got a "keystore was tampered with..." which is not surprising. ## (/) I could then browser over to http://oceana.mbari.org:8082/jira ## (/) Then through the Administration console, I did an XML backup ## (/) I then created a tar of all the attachments in the /data/jira_3_12/attachments directory ## (/) I moved both the XML and tar files to the /root/jira-upgrade directory ## (/) I then reversed the changes to the server.xml file and shut down JIRA ## (/) I left it down during the next steps in case it went so well, I could just point people to the new server (yeah, right). ## (/) I then browsed to the crowd server on oceana and add a new application using: ### URL: http://bugs.mbari.org/jira3135 ### IP: 134.89.2.29 ### Name: JIRA3135 ### Password: (ask Kevin) :) ## (/) On bugs, I made a copy of the JIRA 3.13.5 download in the /opt directory and unzipped and untarred it. ## (/) In order to configure the crowd connection I did the following: ### (/) I scp'd the /opt/crowd/client/crowd-integration-client-1.6.jar file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I removed the existing 1.6.1 crowd client jar from the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I scp'd the /opt/crowd/client/conf/crowd.properties file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I scp'd the /opt/crowd/client/conf/crowd-ehcache.xml file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I edited the crowd.properties file on bugs to look like: {noformat} application.name JIRA3135 application.password (ask Kevin) application.login.url http://oceana.mbari.org:8095/crowd/console/ crowd.server.url http://oceana.mbari.org:8095/crowd/services/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 0 session.lastvalidation session.lastvalidation {noformat} ### (/) I edited the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/osuser.xml file to comment out the current authentication mechanism and then uncomment the crowd one. ## (/) I then edited the /opt/atlassian-jira-standalone-3.13.5/conf/server/xml file and configured the database connection to the Jira_Temp database on Solstice2. I looked like this: {noformat} {noformat} ## (/) Edit the /opt/atlassian/jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/entityengine.xml and changed it from 'hsql' to 'mssql' and delete the line with "PUBLIC" in it per the instructions in the comments in that file. ## (/) I edited the /etc/httpd/conf/httpd.conf file and created a proxy pass at the bottom of the file to point a normal URL to the default port 8080 for JIRA: {noformat} # Proxy Pass for JIRA ProxyPass http://bugs.mbari.org:8080 ProxyPassReverse http://bugs.mbari.org:8080 {noformat} ## (/) I restarted Apache ## (/) I scp'd the jtds driver from oceana to the /opt/atlassian-jira-standalone-3.13.5/common/lib directory (you could down from the internet) ## (/) I then went to the /opt/atlassian-jira-standalone-3.13.5/ directory and ran './bin/startup.sh'. From the log file, I could tell things were hanging. After some troubleshooting I am wondering if the local firewall is preventing the application to get access to the database on solstice2. I can telnet to port 1433, but I can't browse to the base http://bugs.mbari.org from anywhere but the local web browser. I have submitted a ticket. ## (/) I restarted the old JIRA with my hopes dashed :(. ## (/) Pat disabled the firewall on bugs.mbari.org but it still hung trying to connect to solstice2.shore.mbari.org. That is really, really perplexing. Neil mentioned that solstice2 is using Kerberos and solstice is not. Checking with the JTDS docs, version 1.3.1 of the driver added kerberos support, so I downloaded that driver and added the 'userKerberos=true' property to the URL in the server.xml file and restarted. Got an error about no credentials, so added user and password properties to the URL. Nope, no luck. Never did figure this one out, but I had Pat pull the VM inside the firewall and after some thrash it worked. Well, it sort of worked ... sigh. It turns out I had downloaded the standard version instead of the enterprise version. I need to redo this work ... grrr. ## (/) I deleted all the tables in the Jira_Temp database and removed the /data/jira3135/indexes directory (and recreated). ## (/) I downloaded the enterprise version of the 3.13.5 server. I made a copy in the /opt directory and unzipped and untarred the file. ## (/) I went back to crowd and edited the application to change the properties to: ### URL: http://bugs.shore.mbari.org:8080 ### IP: 134.89.12.31 ### Name: jira3135 ### Password: (ask Kevin) :) ## (/) I then repeated the steps above to get the server up and running with the following differences: ### The server name is now bugs.shore.mbari.org ### The paths given above are a little different in that they no longer say "standard" but say "enterprise" ### I deleted the proxy pass as it seemed to have issues before and this is only temporary anyway. ## (/) I then browsed to http://bugs.shore.mbari.org:8080 ## (/) It took me to the start up page and at the top was the option to 'import your existing data'. Seemed too good not to try. I clicked on the link. It asked me for the backup file location and the location where the indexes would be stored. ## (/) I copied the XML zip file and the attachments tar file to the /data/original directory. ## (/) I created the /data/jira3135/indexes and used those directories ... it fired off the import and I waited. ## (/) I tailed the log file to watch the import. Holy crap, it worked!!! I could log in and everything! I copied the results from the log file here for posterity sake: {noformat} 2015-07-22 20:55:45,156 http-8080-Processor22 INFO [jira.action.admin.DataImport] Running data import 2015-07-22 20:55:45,179 http-8080-Processor22 INFO [jira.action.admin.DataImport] Importing data.. 2015-07-22 20:55:45,186 http-8080-Processor22 INFO [jira.action.admin.DataImport] Start parsing XML with SAX Parser 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] XML successfully parsed 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] Removing all entries from the database. 2015-07-22 20:56:24,593 http-8080-Processor22 INFO [jira.action.admin.DataImport] All entries removed. 2015-07-22 20:56:24,594 http-8080-Processor22 INFO [jira.action.admin.DataImport] Started storing 410414 Generic Values 2015-07-22 21:01:51,967 http-8080-Processor22 INFO [jira.action.admin.DataImport] Finished storing Generic Values 2015-07-22 21:01:52,329 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:52,361 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:54,683 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLink' to module 'jira.user.format:profile-link-user-format'. 2015-07-22 21:01:54,724 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullName' to module 'jira.user.format:full-name-user-format'. 2015-07-22 21:01:54,773 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkSearcher' to module 'jira.user.format:profile-link-searcher-user-format'. 2015-07-22 21:01:54,784 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkExternal' to module 'jira.user.format:profile-link-external-user-format'. 2015-07-22 21:01:54,795 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkActionHeader' to module 'jira.user.format:profile-link-action-header-user-format'. 2015-07-22 21:01:54,807 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullProfile' to module 'jira.user.format:full-profile-user-format'. 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/comments 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/issues 2015-07-22 21:01:55,641 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/plugins 2015-07-22 21:01:55,867 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:01:55,871 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/issues does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:55,873 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/comments does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,033 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,257 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,889 http-8080-Processor22 ERROR [atlassian.jira.upgrade.ConsistencyCheckImpl] Attachments are turned on, but attachment path [/data/jira_3_12/attachments] invalid - disabling attachments 2015-07-22 21:02:13,904 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Detected that an upgrade is needed; existing data at build 299 2015-07-22 21:02:13,907 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Doing Upgrade... 2015-07-22 21:02:13,915 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value' succeeded 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 317 2015-07-22 21:02:13,944 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite filters - make each filter a favourite of its owner. 2015-07-22 21:02:17,822 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build319] Could not find author 'fpy' for filter with id '10040' 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite filters - make each filter a favourite of its owner.' succeeded 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 319 2015-07-22 21:02:17,995 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise Share Permissions. Move old shares to new shares. 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise Share Permissions. Move old shares to new shares.' succeeded 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 321 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Migrating the old JIRA UI colors to the new JIRA 3.13 colors 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build322] Custom color detected for jira.lf.menu.bgcolour : #336699 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Migrating the old JIRA UI colors to the new JIRA 3.13 colors' succeeded 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 322 2015-07-22 21:02:18,025 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite dashboards - make each dashboard a favourite of its owner. 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'cmcgann' for dashboard with id '10030' 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'fpy' for dashboard with id '10060' 2015-07-22 21:02:18,423 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'kanna' for dashboard with id '10040' 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite dashboards - make each dashboard a favourite of its owner.' succeeded 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 325 2015-07-22 21:02:18,625 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Reindexing all data in JIRA to include Favourites. 2015-07-22 21:02:18,648 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All starting... 2015-07-22 21:02:18,650 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 0% complete. Current index: Issue 2015-07-22 21:02:18,654 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:02:18,809 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 1% complete. Current index: Issue 2015-07-22 21:02:18,855 indexerPool-2-thread-10 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 2% complete. Current index: Issue 2015-07-22 21:02:18,899 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 3% complete. Current index: Issue 2015-07-22 21:02:18,945 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 4% complete. Current index: Issue 2015-07-22 21:02:19,012 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 5% complete. Current index: Issue . . . 2015-07-22 21:02:26,164 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 95% complete. Current index: Issue 2015-07-22 21:02:26,232 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 96% complete. Current index: Issue 2015-07-22 21:02:26,316 indexerPool-2-thread-9 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 97% complete. Current index: Issue 2015-07-22 21:02:26,771 indexerPool-2-thread-3 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: Issue 2015-07-22 21:02:27,261 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 8607ms. Indexer: DefaultIndexManager: paths: [/data/jira3135/indexes/issues, /data/jira3135/indexes/comments] 2015-07-22 21:02:27,263 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: SearchRequest 2015-07-22 21:02:27,268 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,293 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: SearchRequest 2015-07-22 21:02:27,308 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: PortalPage 2015-07-22 21:02:27,312 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,377 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: PortalPage 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 115ms. Indexer: SharedEntityIndexManager: paths: [/data/jira3135/indexes/entities/portalpage, /data/jira3135/indexes/entities/searchrequest] 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All complete. Total time: 8722ms. 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Reindexing all data in JIRA to include Favourites.' succeeded 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 326 2015-07-22 21:02:27,397 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade succeeded! Setting data build number to 360 2015-07-22 21:02:27,469 JiraQuartzScheduler_Worker-0 WARN [service.services.export.ExportService] Backup directory /data/jira_3_12/backup does not exist {noformat} {warning:title=Paths} It appears that the upgraded JIRA will still look for the attachments and the backup locations in the original places. So I created /data/jira_3_12/backup and untarred the original attachments to /data/jira_3_12 and then everything worked (including attachements) in the new JIRA. {warning} ## (/) I then used the upgraded JIRA to generate a new XML backup and stored it in /data/original/3.13.5 along with another tar of the files in /data/jira_3_12/attachments. ## (/) I then shutdown the JIRA server. *I should be ready to move on to version 4 upgrade WHEW* ## So, before moving on, I decided that it would be a really good idea to spin up a new Crowd instance to get rid of the :8443 in the URL and to move off of RedHat per IS requests. I have a ticket in for a new VM and a new database to try to get this going. I am waiting on that before moving on. ## (/) Pat created the VM and Neil created the database. ## (/) I logged into auth.mbari.org (name of the VM) and downloaded crowd which I unzipped to the /opt directory ## (/) I then created a /data/crowd directory and gave my account permissions on it and then edited the /opt/atlassian..../crowd-webapp/WEB-INF/classes/crowd-init.properties file to set that as the crowd home directory. ## (/) The instructions say to download the JDBC driver, but they already have JTDS 1.2.7 in the download so I did not do anything. ## (/) You have to manually connect up CrowdID to a database as they setup wizard does not currently do this. ### (/) They say to download the driver, but again 1.2.7 was there so I did nothing. ### (/) I edited the /opt/atlassian.../apache-tomcat/conf/Catalina/localhost/openidserver.xml to look like: {noformat} {noformat} ### (/) I edited the /opt/atlassian.../build.properties files to look like: {noformat} # Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See https://confluence.atlassian.com/display/CROWD/Connecting+Crowd+to+a+Database hibernate.dialect=org.hibernate.dialect.SQLServerDialect # The Hibernate transaction factory to use. See https://confluence.atlassian.com/display/CROWD/Configuring+Crowd hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory # The http port you wish to run crowd from, ie: http://localhost:8095/crowd crowd.tomcat.connector.port=8095 # Tomcat requires a unique port for shutdown crowd.tomcat.shutdown.port=8020 # Crowd context root crowd.url=http://localhost:8095/crowd # Demo context root demo.url=http://localhost:8095/demo # OpenID server context root openidserver.url=http://localhost:8095/openidserver {noformat} ### (/) I then ran the build.sh script in the root of /opt/atlassian... ## (/) I fired up crowd using the /opt/atlassian.../start_crowd.sh script ## (/) I then went to http://auth.mbari.org:8095/crowd to kick off the start up wizard ## (/) I grabbed a new eval license from my account on atlassian and pasted into the license page. ## (/) I selected "New install" on the next page. ## (/) I configured the JDBC connection using this connection URL with user DB_Collaboration {noformat} jdbc:jtds:sqlserver://dione.mbari.org:51001/Crowd;domain=SHORE;useNTLMv2=TRUE {noformat} ## (/) I left the "Options" as they came up {warning:title=Paths} Not sure if this is a problem, but because I started the set up using auth.mbari.org, it set the Base URL to http://auth.mbari.org:8095/crowd instead of localhost. Hope that is not a problem. We will see. {warning} ## (/) I configured the email connection using the settings from [here|https://wind.shore.mbari.org/is/howto/email/mbarimail/imap] and I used my network login (probably shouldn't be doing that ... not sure where it stores my password, but I am assuming in the DB). ## (/) I fired up crowd and then went to the http://localhost:8095 URL to start the configuration. I input the DB connection parameters and it created the DB and took off just fine. I really wanted to run the application on port 80 and 443 as normal applications do so I first tried to change the port numbers that the application ran on. That did not work as those are privileged ports and cannot be controller unless you are root. I did not want to do that, so I will have to do a proxy pass. I had to start up the httpd services (I will need to configure as a service) and then created a new file in /etc/httpd/conf.d called crowd.conf that contained the following: {noformat} # This is the configuration for the proxy pass for the crowd server ProxyRequests Off ProxyPreserveHost On Require all granted ProxyPass /crowd http://auth.mbari.org:8095/crowd ProxyPassReverse /crowd http://auth.mbari.org:8095/crowd Require all granted ProxyPass /openidserver http://auth.mbari.org:8095/openidserver ProxyPassReverse /openidserver http://auth.mbari.org:8095/openidserver Require all granted {noformat} ## (/) This worked for the basic HTTP so I will have to get it working with SSL. ## (/) Something with the openidserver is not working correctly and I suspect I have not done the openidserver install completely or correctly. I read the directions on configuring crowdid and it's connection to the database and restarted the crowd server. That worked, not I have both working of straight HTTP, now I need to get SSL going. ## (/) I originally started to configure SSL for the Tomcat server for Crowd, but then realized, since I am putting the Apache proxy in front of Tomcat, I should be able to just set up SSL on Apache HTTP and leave Tomcat alone (i.e. traffic between Apache HTTP and Tomcat does not need to be encrypted). # Schedule upgrade date and send all hands several days in advance. # When the day arrives, send all hands announcing JIRA outage. # From the Administrator's page in our existing JIRA, perform a 'Backup Data to XML'. # Login to oceana.mbari.org as root. # Shutdown JIRA # Create a tar.gz of the /opt/atlassian-jira-enterprise-3.12.1-standalone directory # Clean up the /data/jira_3_12/backups directory by deleting all but maybe the last 5 backups. # Create a tar.gz of the JIRA home directory on ocean.mbari.org which is located at /data/jira_3_12 # scp both tar.gz files to bugs.mbari.org # login to bugs.mbari.org # Unpack the home directory tar to /data/jira # Run the installer as root (this might need IS help or sudo privs). Note that we usually install the application to /opt # Run the JIRA Configuration tool to set the jira.home to the /data/jira location # Connect to JIRA_Temp database on Solstice2 (.... more to do here, see Atlassian docs) # Migrate existing configuration over to new JIRA (I need to add more here as we added Crowd). # Start JIRA # Import backed up XML # Perform post upgrades checks and tests *Need to document steps for 4.4.5->6.X*]]> 27558107 27590873 4.4: [https://confluence.atlassian.com/display/JIRA044/Migrating+JIRA+to+Another+Server] ## The JIRA configuration tool: [https://confluence.atlassian.com/display/JIRA044/Using+the+JIRA+Configuration+Tool] h5. Steps # (/) Create new VM named bugs.mbari.org in the DMZ # (/) Have Neil create database Jira_Temp on solstice2.shore.mbari.org # (/) Have Neil create database Jira on solstice2.shore.mbari.org # (/) Have Pat install Java 7 on bugs.shore.mbari.org # (/) Have Pete plumb holes through firewall so processes on bugs.mbari.org can get to Solstice2 # (/) Have Pat create DB_Collaboration account on bugs so it can run JIRA under that account and it can connect to solstice2 using that NT Domain account. # (/) Upgrade license on Atlassian site # (/) Log into bugs.shore.mbari.org # (/) Download 3.13.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 4.4.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 5.2.11 standalone Linux 64 bit tar.gz (not sure this version is necessary, but at least I have it) # (/) Unzip and untar the file to /opt # (/) Download latest JIRA (6.4.7 as of this writing). # (/) Unzip and untar it to /opt # Performed Test Upgrade ## (/) In order to export the current stuff in JIRA, I had to shut off access so people could not change the data while I was backing it up. ## (/) I ssh'd to oceana.mbari.org as root and edited the /opt/jira/conf/server.xml file and commented out the Connector section that had the port of 8010 to shut it off from the normal serving route. ## (/) I uncommented the 8082 port connector and the 8443 port connector so that I could still get to the server. ## (/) I stopped and started the JIRA server and in the log file I got a "keystore was tampered with..." which is not surprising. ## (/) I could then browser over to http://oceana.mbari.org:8082/jira ## (/) Then through the Administration console, I did an XML backup ## (/) I then created a tar of all the attachments in the /data/jira_3_12/attachments directory ## (/) I moved both the XML and tar files to the /root/jira-upgrade directory ## (/) I then reversed the changes to the server.xml file and shut down JIRA ## (/) I left it down during the next steps in case it went so well, I could just point people to the new server (yeah, right). ## (/) I then browsed to the crowd server on oceana and add a new application using: ### URL: http://bugs.mbari.org/jira3135 ### IP: 134.89.2.29 ### Name: JIRA3135 ### Password: (ask Kevin) :) ## (/) On bugs, I made a copy of the JIRA 3.13.5 download in the /opt directory and unzipped and untarred it. ## (/) In order to configure the crowd connection I did the following: ### (/) I scp'd the /opt/crowd/client/crowd-integration-client-1.6.jar file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I removed the existing 1.6.1 crowd client jar from the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I scp'd the /opt/crowd/client/conf/crowd.properties file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I scp'd the /opt/crowd/client/conf/crowd-ehcache.xml file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I edited the crowd.properties file on bugs to look like: {noformat} application.name JIRA3135 application.password (ask Kevin) application.login.url http://oceana.mbari.org:8095/crowd/console/ crowd.server.url http://oceana.mbari.org:8095/crowd/services/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 0 session.lastvalidation session.lastvalidation {noformat} ### (/) I edited the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/osuser.xml file to comment out the current authentication mechanism and then uncomment the crowd one. ## (/) I then edited the /opt/atlassian-jira-standalone-3.13.5/conf/server/xml file and configured the database connection to the Jira_Temp database on Solstice2. I looked like this: {noformat} {noformat} ## (/) Edit the /opt/atlassian/jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/entityengine.xml and changed it from 'hsql' to 'mssql' and delete the line with "PUBLIC" in it per the instructions in the comments in that file. ## (/) I edited the /etc/httpd/conf/httpd.conf file and created a proxy pass at the bottom of the file to point a normal URL to the default port 8080 for JIRA: {noformat} # Proxy Pass for JIRA ProxyPass http://bugs.mbari.org:8080 ProxyPassReverse http://bugs.mbari.org:8080 {noformat} ## (/) I restarted Apache ## (/) I scp'd the jtds driver from oceana to the /opt/atlassian-jira-standalone-3.13.5/common/lib directory (you could down from the internet) ## (/) I then went to the /opt/atlassian-jira-standalone-3.13.5/ directory and ran './bin/startup.sh'. From the log file, I could tell things were hanging. After some troubleshooting I am wondering if the local firewall is preventing the application to get access to the database on solstice2. I can telnet to port 1433, but I can't browse to the base http://bugs.mbari.org from anywhere but the local web browser. I have submitted a ticket. ## (/) I restarted the old JIRA with my hopes dashed :(. ## (/) Pat disabled the firewall on bugs.mbari.org but it still hung trying to connect to solstice2.shore.mbari.org. That is really, really perplexing. Neil mentioned that solstice2 is using Kerberos and solstice is not. Checking with the JTDS docs, version 1.3.1 of the driver added kerberos support, so I downloaded that driver and added the 'userKerberos=true' property to the URL in the server.xml file and restarted. Got an error about no credentials, so added user and password properties to the URL. Nope, no luck. Never did figure this one out, but I had Pat pull the VM inside the firewall and after some thrash it worked. Well, it sort of worked ... sigh. It turns out I had downloaded the standard version instead of the enterprise version. I need to redo this work ... grrr. ## (/) I deleted all the tables in the Jira_Temp database and removed the /data/jira3135/indexes directory (and recreated). ## (/) I downloaded the enterprise version of the 3.13.5 server. I made a copy in the /opt directory and unzipped and untarred the file. ## (/) I went back to crowd and edited the application to change the properties to: ### URL: http://bugs.shore.mbari.org:8080 ### IP: 134.89.12.31 ### Name: jira3135 ### Password: (ask Kevin) :) ## (/) I then repeated the steps above to get the server up and running with the following differences: ### The server name is now bugs.shore.mbari.org ### The paths given above are a little different in that they no longer say "standard" but say "enterprise" ### I deleted the proxy pass as it seemed to have issues before and this is only temporary anyway. ## (/) I then browsed to http://bugs.shore.mbari.org:8080 ## (/) It took me to the start up page and at the top was the option to 'import your existing data'. Seemed too good not to try. I clicked on the link. It asked me for the backup file location and the location where the indexes would be stored. ## (/) I copied the XML zip file and the attachments tar file to the /data/original directory. ## (/) I created the /data/jira3135/indexes and used those directories ... it fired off the import and I waited. ## (/) I tailed the log file to watch the import. Holy crap, it worked!!! I could log in and everything! I copied the results from the log file here for posterity sake: {noformat} 2015-07-22 20:55:45,156 http-8080-Processor22 INFO [jira.action.admin.DataImport] Running data import 2015-07-22 20:55:45,179 http-8080-Processor22 INFO [jira.action.admin.DataImport] Importing data.. 2015-07-22 20:55:45,186 http-8080-Processor22 INFO [jira.action.admin.DataImport] Start parsing XML with SAX Parser 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] XML successfully parsed 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] Removing all entries from the database. 2015-07-22 20:56:24,593 http-8080-Processor22 INFO [jira.action.admin.DataImport] All entries removed. 2015-07-22 20:56:24,594 http-8080-Processor22 INFO [jira.action.admin.DataImport] Started storing 410414 Generic Values 2015-07-22 21:01:51,967 http-8080-Processor22 INFO [jira.action.admin.DataImport] Finished storing Generic Values 2015-07-22 21:01:52,329 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:52,361 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:54,683 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLink' to module 'jira.user.format:profile-link-user-format'. 2015-07-22 21:01:54,724 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullName' to module 'jira.user.format:full-name-user-format'. 2015-07-22 21:01:54,773 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkSearcher' to module 'jira.user.format:profile-link-searcher-user-format'. 2015-07-22 21:01:54,784 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkExternal' to module 'jira.user.format:profile-link-external-user-format'. 2015-07-22 21:01:54,795 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkActionHeader' to module 'jira.user.format:profile-link-action-header-user-format'. 2015-07-22 21:01:54,807 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullProfile' to module 'jira.user.format:full-profile-user-format'. 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/comments 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/issues 2015-07-22 21:01:55,641 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/plugins 2015-07-22 21:01:55,867 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:01:55,871 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/issues does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:55,873 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/comments does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,033 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,257 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,889 http-8080-Processor22 ERROR [atlassian.jira.upgrade.ConsistencyCheckImpl] Attachments are turned on, but attachment path [/data/jira_3_12/attachments] invalid - disabling attachments 2015-07-22 21:02:13,904 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Detected that an upgrade is needed; existing data at build 299 2015-07-22 21:02:13,907 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Doing Upgrade... 2015-07-22 21:02:13,915 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value' succeeded 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 317 2015-07-22 21:02:13,944 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite filters - make each filter a favourite of its owner. 2015-07-22 21:02:17,822 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build319] Could not find author 'fpy' for filter with id '10040' 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite filters - make each filter a favourite of its owner.' succeeded 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 319 2015-07-22 21:02:17,995 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise Share Permissions. Move old shares to new shares. 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise Share Permissions. Move old shares to new shares.' succeeded 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 321 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Migrating the old JIRA UI colors to the new JIRA 3.13 colors 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build322] Custom color detected for jira.lf.menu.bgcolour : #336699 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Migrating the old JIRA UI colors to the new JIRA 3.13 colors' succeeded 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 322 2015-07-22 21:02:18,025 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite dashboards - make each dashboard a favourite of its owner. 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'cmcgann' for dashboard with id '10030' 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'fpy' for dashboard with id '10060' 2015-07-22 21:02:18,423 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'kanna' for dashboard with id '10040' 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite dashboards - make each dashboard a favourite of its owner.' succeeded 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 325 2015-07-22 21:02:18,625 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Reindexing all data in JIRA to include Favourites. 2015-07-22 21:02:18,648 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All starting... 2015-07-22 21:02:18,650 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 0% complete. Current index: Issue 2015-07-22 21:02:18,654 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:02:18,809 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 1% complete. Current index: Issue 2015-07-22 21:02:18,855 indexerPool-2-thread-10 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 2% complete. Current index: Issue 2015-07-22 21:02:18,899 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 3% complete. Current index: Issue 2015-07-22 21:02:18,945 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 4% complete. Current index: Issue 2015-07-22 21:02:19,012 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 5% complete. Current index: Issue . . . 2015-07-22 21:02:26,164 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 95% complete. Current index: Issue 2015-07-22 21:02:26,232 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 96% complete. Current index: Issue 2015-07-22 21:02:26,316 indexerPool-2-thread-9 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 97% complete. Current index: Issue 2015-07-22 21:02:26,771 indexerPool-2-thread-3 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: Issue 2015-07-22 21:02:27,261 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 8607ms. Indexer: DefaultIndexManager: paths: [/data/jira3135/indexes/issues, /data/jira3135/indexes/comments] 2015-07-22 21:02:27,263 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: SearchRequest 2015-07-22 21:02:27,268 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,293 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: SearchRequest 2015-07-22 21:02:27,308 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: PortalPage 2015-07-22 21:02:27,312 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,377 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: PortalPage 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 115ms. Indexer: SharedEntityIndexManager: paths: [/data/jira3135/indexes/entities/portalpage, /data/jira3135/indexes/entities/searchrequest] 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All complete. Total time: 8722ms. 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Reindexing all data in JIRA to include Favourites.' succeeded 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 326 2015-07-22 21:02:27,397 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade succeeded! Setting data build number to 360 2015-07-22 21:02:27,469 JiraQuartzScheduler_Worker-0 WARN [service.services.export.ExportService] Backup directory /data/jira_3_12/backup does not exist {noformat} {warning:title=Paths} It appears that the upgraded JIRA will still look for the attachments and the backup locations in the original places. So I created /data/jira_3_12/backup and untarred the original attachments to /data/jira_3_12 and then everything worked (including attachements) in the new JIRA. {warning} ## (/) I then used the upgraded JIRA to generate a new XML backup and stored it in /data/original/3.13.5 along with another tar of the files in /data/jira_3_12/attachments. ## (/) I then shutdown the JIRA server. *I should be ready to move on to version 4 upgrade WHEW* ## So, before moving on, I decided that it would be a really good idea to spin up a new Crowd instance to get rid of the :8443 in the URL and to move off of RedHat per IS requests. I have a ticket in for a new VM and a new database to try to get this going. I am waiting on that before moving on. ## (/) Pat created the VM and Neil created the database. ## (/) I logged into auth.mbari.org (name of the VM) and downloaded crowd which I unzipped to the /opt directory ## (/) I then created a /data/crowd directory and gave my account permissions on it and then edited the /opt/atlassian..../crowd-webapp/WEB-INF/classes/crowd-init.properties file to set that as the crowd home directory. ## (/) The instructions say to download the JDBC driver, but they already have JTDS 1.2.7 in the download so I did not do anything. ## (/) You have to manually connect up CrowdID to a database as they setup wizard does not currently do this. ### (/) They say to download the driver, but again 1.2.7 was there so I did nothing. ### (/) I edited the /opt/atlassian.../apache-tomcat/conf/Catalina/localhost/openidserver.xml to look like: {noformat} {noformat} ### (/) I edited the /opt/atlassian.../build.properties files to look like: {noformat} # Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See https://confluence.atlassian.com/display/CROWD/Connecting+Crowd+to+a+Database hibernate.dialect=org.hibernate.dialect.SQLServerDialect # The Hibernate transaction factory to use. See https://confluence.atlassian.com/display/CROWD/Configuring+Crowd hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory # The http port you wish to run crowd from, ie: http://localhost:8095/crowd crowd.tomcat.connector.port=8095 # Tomcat requires a unique port for shutdown crowd.tomcat.shutdown.port=8020 # Crowd context root crowd.url=http://localhost:8095/crowd # Demo context root demo.url=http://localhost:8095/demo # OpenID server context root openidserver.url=http://localhost:8095/openidserver {noformat} ### (/) I then ran the build.sh script in the root of /opt/atlassian... ## (/) I fired up crowd using the /opt/atlassian.../start_crowd.sh script ## (/) I then went to http://auth.mbari.org:8095/crowd to kick off the start up wizard ## (/) I grabbed a new eval license from my account on atlassian and pasted into the license page. ## (/) I selected "New install" on the next page. ## (/) I configured the JDBC connection using this connection URL with user DB_Collaboration {noformat} jdbc:jtds:sqlserver://dione.mbari.org:51001/Crowd;domain=SHORE;useNTLMv2=TRUE {noformat} ## (/) I left the "Options" as they came up {warning:title=Paths} Not sure if this is a problem, but because I started the set up using auth.mbari.org, it set the Base URL to http://auth.mbari.org:8095/crowd instead of localhost. Hope that is not a problem. We will see. {warning} ## (/) I configured the email connection using the settings from [here|https://wind.shore.mbari.org/is/howto/email/mbarimail/imap] and I used my network login (probably shouldn't be doing that ... not sure where it stores my password, but I am assuming in the DB). ## (/) For the local admin account, I created a user named 'crowdadm' so it would not clash with my LDAP account. See Kevin Gomes for password information. ## (/) I fired up crowd and then went to the http://localhost:8095 URL to start the configuration. I input the DB connection parameters and it created the DB and took off just fine. I really wanted to run the application on port 80 and 443 as normal applications do so I first tried to change the port numbers that the application ran on. That did not work as those are privileged ports and cannot be controller unless you are root. I did not want to do that, so I will have to do a proxy pass. I had to start up the httpd services (I will need to configure as a service) and then created a new file in /etc/httpd/conf.d called crowd.conf that contained the following: {noformat} # This is the configuration for the proxy pass for the crowd server ProxyRequests Off ProxyPreserveHost On Require all granted ProxyPass /crowd http://auth.mbari.org:8095/crowd ProxyPassReverse /crowd http://auth.mbari.org:8095/crowd Require all granted ProxyPass /openidserver http://auth.mbari.org:8095/openidserver ProxyPassReverse /openidserver http://auth.mbari.org:8095/openidserver Require all granted {noformat} ## (/) This worked for the basic HTTP so I will have to get it working with SSL. ## (/) Something with the openidserver is not working correctly and I suspect I have not done the openidserver install completely or correctly. I read the directions on configuring crowdid and it's connection to the database and restarted the crowd server. That worked, not I have both working of straight HTTP, now I need to get SSL going. ## (/) I originally started to configure SSL for the Tomcat server for Crowd, but then realized, since I am putting the Apache proxy in front of Tomcat, I should be able to just set up SSL on Apache HTTP and leave Tomcat alone (i.e. traffic between Apache HTTP and Tomcat does not need to be encrypted). # Schedule upgrade date and send all hands several days in advance. # When the day arrives, send all hands announcing JIRA outage. # From the Administrator's page in our existing JIRA, perform a 'Backup Data to XML'. # Login to oceana.mbari.org as root. # Shutdown JIRA # Create a tar.gz of the /opt/atlassian-jira-enterprise-3.12.1-standalone directory # Clean up the /data/jira_3_12/backups directory by deleting all but maybe the last 5 backups. # Create a tar.gz of the JIRA home directory on ocean.mbari.org which is located at /data/jira_3_12 # scp both tar.gz files to bugs.mbari.org # login to bugs.mbari.org # Unpack the home directory tar to /data/jira # Run the installer as root (this might need IS help or sudo privs). Note that we usually install the application to /opt # Run the JIRA Configuration tool to set the jira.home to the /data/jira location # Connect to JIRA_Temp database on Solstice2 (.... more to do here, see Atlassian docs) # Migrate existing configuration over to new JIRA (I need to add more here as we added Crowd). # Start JIRA # Import backed up XML # Perform post upgrades checks and tests *Need to document steps for 4.4.5->6.X*]]> 27558108 27590868 4.4: [https://confluence.atlassian.com/display/JIRA044/Migrating+JIRA+to+Another+Server] ## The JIRA configuration tool: [https://confluence.atlassian.com/display/JIRA044/Using+the+JIRA+Configuration+Tool] h5. Steps # (/) Create new VM named bugs.mbari.org in the DMZ # (/) Have Neil create database Jira_Temp on solstice2.shore.mbari.org # (/) Have Neil create database Jira on solstice2.shore.mbari.org # (/) Have Pat install Java 7 on bugs.shore.mbari.org # (/) Have Pete plumb holes through firewall so processes on bugs.mbari.org can get to Solstice2 # (/) Have Pat create DB_Collaboration account on bugs so it can run JIRA under that account and it can connect to solstice2 using that NT Domain account. # (/) Upgrade license on Atlassian site # (/) Log into bugs.shore.mbari.org # (/) Download 3.13.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 4.4.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 5.2.11 standalone Linux 64 bit tar.gz (not sure this version is necessary, but at least I have it) # (/) Unzip and untar the file to /opt # (/) Download latest JIRA (6.4.7 as of this writing). # (/) Unzip and untar it to /opt # Performed Test Upgrade ## (/) In order to export the current stuff in JIRA, I had to shut off access so people could not change the data while I was backing it up. ## (/) I ssh'd to oceana.mbari.org as root and edited the /opt/jira/conf/server.xml file and commented out the Connector section that had the port of 8010 to shut it off from the normal serving route. ## (/) I uncommented the 8082 port connector and the 8443 port connector so that I could still get to the server. ## (/) I stopped and started the JIRA server and in the log file I got a "keystore was tampered with..." which is not surprising. ## (/) I could then browser over to http://oceana.mbari.org:8082/jira ## (/) Then through the Administration console, I did an XML backup ## (/) I then created a tar of all the attachments in the /data/jira_3_12/attachments directory ## (/) I moved both the XML and tar files to the /root/jira-upgrade directory ## (/) I then reversed the changes to the server.xml file and shut down JIRA ## (/) I left it down during the next steps in case it went so well, I could just point people to the new server (yeah, right). ## (/) I then browsed to the crowd server on oceana and add a new application using: ### URL: http://bugs.mbari.org/jira3135 ### IP: 134.89.2.29 ### Name: JIRA3135 ### Password: (ask Kevin) :) ## (/) On bugs, I made a copy of the JIRA 3.13.5 download in the /opt directory and unzipped and untarred it. ## (/) In order to configure the crowd connection I did the following: ### (/) I scp'd the /opt/crowd/client/crowd-integration-client-1.6.jar file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I removed the existing 1.6.1 crowd client jar from the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I scp'd the /opt/crowd/client/conf/crowd.properties file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I scp'd the /opt/crowd/client/conf/crowd-ehcache.xml file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I edited the crowd.properties file on bugs to look like: {noformat} application.name JIRA3135 application.password (ask Kevin) application.login.url http://oceana.mbari.org:8095/crowd/console/ crowd.server.url http://oceana.mbari.org:8095/crowd/services/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 0 session.lastvalidation session.lastvalidation {noformat} ### (/) I edited the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/osuser.xml file to comment out the current authentication mechanism and then uncomment the crowd one. ## (/) I then edited the /opt/atlassian-jira-standalone-3.13.5/conf/server/xml file and configured the database connection to the Jira_Temp database on Solstice2. I looked like this: {noformat} {noformat} ## (/) Edit the /opt/atlassian/jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/entityengine.xml and changed it from 'hsql' to 'mssql' and delete the line with "PUBLIC" in it per the instructions in the comments in that file. ## (/) I edited the /etc/httpd/conf/httpd.conf file and created a proxy pass at the bottom of the file to point a normal URL to the default port 8080 for JIRA: {noformat} # Proxy Pass for JIRA ProxyPass http://bugs.mbari.org:8080 ProxyPassReverse http://bugs.mbari.org:8080 {noformat} ## (/) I restarted Apache ## (/) I scp'd the jtds driver from oceana to the /opt/atlassian-jira-standalone-3.13.5/common/lib directory (you could down from the internet) ## (/) I then went to the /opt/atlassian-jira-standalone-3.13.5/ directory and ran './bin/startup.sh'. From the log file, I could tell things were hanging. After some troubleshooting I am wondering if the local firewall is preventing the application to get access to the database on solstice2. I can telnet to port 1433, but I can't browse to the base http://bugs.mbari.org from anywhere but the local web browser. I have submitted a ticket. ## (/) I restarted the old JIRA with my hopes dashed :(. ## (/) Pat disabled the firewall on bugs.mbari.org but it still hung trying to connect to solstice2.shore.mbari.org. That is really, really perplexing. Neil mentioned that solstice2 is using Kerberos and solstice is not. Checking with the JTDS docs, version 1.3.1 of the driver added kerberos support, so I downloaded that driver and added the 'userKerberos=true' property to the URL in the server.xml file and restarted. Got an error about no credentials, so added user and password properties to the URL. Nope, no luck. Never did figure this one out, but I had Pat pull the VM inside the firewall and after some thrash it worked. Well, it sort of worked ... sigh. It turns out I had downloaded the standard version instead of the enterprise version. I need to redo this work ... grrr. ## (/) I deleted all the tables in the Jira_Temp database and removed the /data/jira3135/indexes directory (and recreated). ## (/) I downloaded the enterprise version of the 3.13.5 server. I made a copy in the /opt directory and unzipped and untarred the file. ## (/) I went back to crowd and edited the application to change the properties to: ### URL: http://bugs.shore.mbari.org:8080 ### IP: 134.89.12.31 ### Name: jira3135 ### Password: (ask Kevin) :) ## (/) I then repeated the steps above to get the server up and running with the following differences: ### The server name is now bugs.shore.mbari.org ### The paths given above are a little different in that they no longer say "standard" but say "enterprise" ### I deleted the proxy pass as it seemed to have issues before and this is only temporary anyway. ## (/) I then browsed to http://bugs.shore.mbari.org:8080 ## (/) It took me to the start up page and at the top was the option to 'import your existing data'. Seemed too good not to try. I clicked on the link. It asked me for the backup file location and the location where the indexes would be stored. ## (/) I copied the XML zip file and the attachments tar file to the /data/original directory. ## (/) I created the /data/jira3135/indexes and used those directories ... it fired off the import and I waited. ## (/) I tailed the log file to watch the import. Holy crap, it worked!!! I could log in and everything! I copied the results from the log file here for posterity sake: {noformat} 2015-07-22 20:55:45,156 http-8080-Processor22 INFO [jira.action.admin.DataImport] Running data import 2015-07-22 20:55:45,179 http-8080-Processor22 INFO [jira.action.admin.DataImport] Importing data.. 2015-07-22 20:55:45,186 http-8080-Processor22 INFO [jira.action.admin.DataImport] Start parsing XML with SAX Parser 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] XML successfully parsed 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] Removing all entries from the database. 2015-07-22 20:56:24,593 http-8080-Processor22 INFO [jira.action.admin.DataImport] All entries removed. 2015-07-22 20:56:24,594 http-8080-Processor22 INFO [jira.action.admin.DataImport] Started storing 410414 Generic Values 2015-07-22 21:01:51,967 http-8080-Processor22 INFO [jira.action.admin.DataImport] Finished storing Generic Values 2015-07-22 21:01:52,329 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:52,361 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:54,683 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLink' to module 'jira.user.format:profile-link-user-format'. 2015-07-22 21:01:54,724 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullName' to module 'jira.user.format:full-name-user-format'. 2015-07-22 21:01:54,773 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkSearcher' to module 'jira.user.format:profile-link-searcher-user-format'. 2015-07-22 21:01:54,784 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkExternal' to module 'jira.user.format:profile-link-external-user-format'. 2015-07-22 21:01:54,795 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkActionHeader' to module 'jira.user.format:profile-link-action-header-user-format'. 2015-07-22 21:01:54,807 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullProfile' to module 'jira.user.format:full-profile-user-format'. 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/comments 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/issues 2015-07-22 21:01:55,641 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/plugins 2015-07-22 21:01:55,867 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:01:55,871 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/issues does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:55,873 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/comments does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,033 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,257 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,889 http-8080-Processor22 ERROR [atlassian.jira.upgrade.ConsistencyCheckImpl] Attachments are turned on, but attachment path [/data/jira_3_12/attachments] invalid - disabling attachments 2015-07-22 21:02:13,904 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Detected that an upgrade is needed; existing data at build 299 2015-07-22 21:02:13,907 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Doing Upgrade... 2015-07-22 21:02:13,915 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value' succeeded 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 317 2015-07-22 21:02:13,944 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite filters - make each filter a favourite of its owner. 2015-07-22 21:02:17,822 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build319] Could not find author 'fpy' for filter with id '10040' 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite filters - make each filter a favourite of its owner.' succeeded 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 319 2015-07-22 21:02:17,995 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise Share Permissions. Move old shares to new shares. 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise Share Permissions. Move old shares to new shares.' succeeded 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 321 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Migrating the old JIRA UI colors to the new JIRA 3.13 colors 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build322] Custom color detected for jira.lf.menu.bgcolour : #336699 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Migrating the old JIRA UI colors to the new JIRA 3.13 colors' succeeded 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 322 2015-07-22 21:02:18,025 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite dashboards - make each dashboard a favourite of its owner. 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'cmcgann' for dashboard with id '10030' 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'fpy' for dashboard with id '10060' 2015-07-22 21:02:18,423 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'kanna' for dashboard with id '10040' 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite dashboards - make each dashboard a favourite of its owner.' succeeded 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 325 2015-07-22 21:02:18,625 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Reindexing all data in JIRA to include Favourites. 2015-07-22 21:02:18,648 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All starting... 2015-07-22 21:02:18,650 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 0% complete. Current index: Issue 2015-07-22 21:02:18,654 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:02:18,809 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 1% complete. Current index: Issue 2015-07-22 21:02:18,855 indexerPool-2-thread-10 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 2% complete. Current index: Issue 2015-07-22 21:02:18,899 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 3% complete. Current index: Issue 2015-07-22 21:02:18,945 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 4% complete. Current index: Issue 2015-07-22 21:02:19,012 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 5% complete. Current index: Issue . . . 2015-07-22 21:02:26,164 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 95% complete. Current index: Issue 2015-07-22 21:02:26,232 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 96% complete. Current index: Issue 2015-07-22 21:02:26,316 indexerPool-2-thread-9 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 97% complete. Current index: Issue 2015-07-22 21:02:26,771 indexerPool-2-thread-3 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: Issue 2015-07-22 21:02:27,261 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 8607ms. Indexer: DefaultIndexManager: paths: [/data/jira3135/indexes/issues, /data/jira3135/indexes/comments] 2015-07-22 21:02:27,263 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: SearchRequest 2015-07-22 21:02:27,268 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,293 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: SearchRequest 2015-07-22 21:02:27,308 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: PortalPage 2015-07-22 21:02:27,312 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,377 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: PortalPage 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 115ms. Indexer: SharedEntityIndexManager: paths: [/data/jira3135/indexes/entities/portalpage, /data/jira3135/indexes/entities/searchrequest] 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All complete. Total time: 8722ms. 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Reindexing all data in JIRA to include Favourites.' succeeded 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 326 2015-07-22 21:02:27,397 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade succeeded! Setting data build number to 360 2015-07-22 21:02:27,469 JiraQuartzScheduler_Worker-0 WARN [service.services.export.ExportService] Backup directory /data/jira_3_12/backup does not exist {noformat} {warning:title=Paths} It appears that the upgraded JIRA will still look for the attachments and the backup locations in the original places. So I created /data/jira_3_12/backup and untarred the original attachments to /data/jira_3_12 and then everything worked (including attachements) in the new JIRA. {warning} ## (/) I then used the upgraded JIRA to generate a new XML backup and stored it in /data/original/3.13.5 along with another tar of the files in /data/jira_3_12/attachments. ## (/) I then shutdown the JIRA server. *I should be ready to move on to version 4 upgrade WHEW* ## So, before moving on, I decided that it would be a really good idea to spin up a new Crowd instance to get rid of the :8443 in the URL and to move off of RedHat per IS requests. I have a ticket in for a new VM and a new database to try to get this going. I am waiting on that before moving on. ## (/) Pat created the VM and Neil created the database. ## (/) I logged into auth.mbari.org (name of the VM) and downloaded crowd which I unzipped to the /opt directory ## (/) I then created a /data/crowd directory and gave my account permissions on it and then edited the /opt/atlassian..../crowd-webapp/WEB-INF/classes/crowd-init.properties file to set that as the crowd home directory. ## (/) The instructions say to download the JDBC driver, but they already have JTDS 1.2.7 in the download so I did not do anything. ## (/) You have to manually connect up CrowdID to a database as they setup wizard does not currently do this. ### (/) They say to download the driver, but again 1.2.7 was there so I did nothing. ### (/) I edited the /opt/atlassian.../apache-tomcat/conf/Catalina/localhost/openidserver.xml to look like: {noformat} {noformat} ### (/) I edited the /opt/atlassian.../build.properties files to look like: {noformat} # Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See https://confluence.atlassian.com/display/CROWD/Connecting+Crowd+to+a+Database hibernate.dialect=org.hibernate.dialect.SQLServerDialect # The Hibernate transaction factory to use. See https://confluence.atlassian.com/display/CROWD/Configuring+Crowd hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory # The http port you wish to run crowd from, ie: http://localhost:8095/crowd crowd.tomcat.connector.port=8095 # Tomcat requires a unique port for shutdown crowd.tomcat.shutdown.port=8020 # Crowd context root crowd.url=http://localhost:8095/crowd # Demo context root demo.url=http://localhost:8095/demo # OpenID server context root openidserver.url=http://localhost:8095/openidserver {noformat} ### (/) I then ran the build.sh script in the root of /opt/atlassian... ## (/) I fired up crowd using the /opt/atlassian.../start_crowd.sh script ## (/) I then went to http://auth.mbari.org:8095/crowd to kick off the start up wizard ## (/) I grabbed a new eval license from my account on atlassian and pasted into the license page. ## (/) I selected "New install" on the next page. ## (/) I configured the JDBC connection using this connection URL with user DB_Collaboration {noformat} jdbc:jtds:sqlserver://dione.mbari.org:51001/Crowd;domain=SHORE;useNTLMv2=TRUE {noformat} ## (/) I fired up crowd and then went to the http://localhost:8095 URL to start the configuration. I input the DB connection parameters and it created the DB and took off just fine. I really wanted to run the application on port 80 and 443 as normal applications do so I first tried to change the port numbers that the application ran on. That did not work as those are privileged ports and cannot be controller unless you are root. I did not want to do that, so I will have to do a proxy pass. I had to start up the httpd services (I will need to configure as a service) and then created a new file in /etc/httpd/conf.d called crowd.conf that contained the following: {noformat} # This is the configuration for the proxy pass for the crowd server ProxyRequests Off ProxyPreserveHost On Require all granted ProxyPass /crowd http://auth.mbari.org:8095/crowd ProxyPassReverse /crowd http://auth.mbari.org:8095/crowd Require all granted ProxyPass /openidserver http://auth.mbari.org:8095/openidserver ProxyPassReverse /openidserver http://auth.mbari.org:8095/openidserver Require all granted {noformat} ## (/) This worked for the basic HTTP so I will have to get it working with SSL. ## (/) Something with the openidserver is not working correctly and I suspect I have not done the openidserver install completely or correctly. I read the directions on configuring crowdid and it's connection to the database and restarted the crowd server. That worked, not I have both working of straight HTTP, now I need to get SSL going. ## (/) I originally started to configure SSL for the Tomcat server for Crowd, but then realized, since I am putting the Apache proxy in front of Tomcat, I should be able to just set up SSL on Apache HTTP and leave Tomcat alone (i.e. traffic between Apache HTTP and Tomcat does not need to be encrypted). # Schedule upgrade date and send all hands several days in advance. # When the day arrives, send all hands announcing JIRA outage. # From the Administrator's page in our existing JIRA, perform a 'Backup Data to XML'. # Login to oceana.mbari.org as root. # Shutdown JIRA # Create a tar.gz of the /opt/atlassian-jira-enterprise-3.12.1-standalone directory # Clean up the /data/jira_3_12/backups directory by deleting all but maybe the last 5 backups. # Create a tar.gz of the JIRA home directory on ocean.mbari.org which is located at /data/jira_3_12 # scp both tar.gz files to bugs.mbari.org # login to bugs.mbari.org # Unpack the home directory tar to /data/jira # Run the installer as root (this might need IS help or sudo privs). Note that we usually install the application to /opt # Run the JIRA Configuration tool to set the jira.home to the /data/jira location # Connect to JIRA_Temp database on Solstice2 (.... more to do here, see Atlassian docs) # Migrate existing configuration over to new JIRA (I need to add more here as we added Crowd). # Start JIRA # Import backed up XML # Perform post upgrades checks and tests *Need to document steps for 4.4.5->6.X*]]> 27558103 27590870 4.4: [https://confluence.atlassian.com/display/JIRA044/Migrating+JIRA+to+Another+Server] ## The JIRA configuration tool: [https://confluence.atlassian.com/display/JIRA044/Using+the+JIRA+Configuration+Tool] h5. Steps # (/) Create new VM named bugs.mbari.org in the DMZ # (/) Have Neil create database Jira_Temp on solstice2.shore.mbari.org # (/) Have Neil create database Jira on solstice2.shore.mbari.org # (/) Have Pat install Java 7 on bugs.shore.mbari.org # (/) Have Pete plumb holes through firewall so processes on bugs.mbari.org can get to Solstice2 # (/) Have Pat create DB_Collaboration account on bugs so it can run JIRA under that account and it can connect to solstice2 using that NT Domain account. # (/) Upgrade license on Atlassian site # (/) Log into bugs.shore.mbari.org # (/) Download 3.13.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 4.4.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 5.2.11 standalone Linux 64 bit tar.gz (not sure this version is necessary, but at least I have it) # (/) Unzip and untar the file to /opt # (/) Download latest JIRA (6.4.7 as of this writing). # (/) Unzip and untar it to /opt # Performed Test Upgrade ## (/) In order to export the current stuff in JIRA, I had to shut off access so people could not change the data while I was backing it up. ## (/) I ssh'd to oceana.mbari.org as root and edited the /opt/jira/conf/server.xml file and commented out the Connector section that had the port of 8010 to shut it off from the normal serving route. ## (/) I uncommented the 8082 port connector and the 8443 port connector so that I could still get to the server. ## (/) I stopped and started the JIRA server and in the log file I got a "keystore was tampered with..." which is not surprising. ## (/) I could then browser over to http://oceana.mbari.org:8082/jira ## (/) Then through the Administration console, I did an XML backup ## (/) I then created a tar of all the attachments in the /data/jira_3_12/attachments directory ## (/) I moved both the XML and tar files to the /root/jira-upgrade directory ## (/) I then reversed the changes to the server.xml file and shut down JIRA ## (/) I left it down during the next steps in case it went so well, I could just point people to the new server (yeah, right). ## (/) I then browsed to the crowd server on oceana and add a new application using: ### URL: http://bugs.mbari.org/jira3135 ### IP: 134.89.2.29 ### Name: JIRA3135 ### Password: (ask Kevin) :) ## (/) On bugs, I made a copy of the JIRA 3.13.5 download in the /opt directory and unzipped and untarred it. ## (/) In order to configure the crowd connection I did the following: ### (/) I scp'd the /opt/crowd/client/crowd-integration-client-1.6.jar file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I removed the existing 1.6.1 crowd client jar from the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I scp'd the /opt/crowd/client/conf/crowd.properties file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I scp'd the /opt/crowd/client/conf/crowd-ehcache.xml file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I edited the crowd.properties file on bugs to look like: {noformat} application.name JIRA3135 application.password (ask Kevin) application.login.url http://oceana.mbari.org:8095/crowd/console/ crowd.server.url http://oceana.mbari.org:8095/crowd/services/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 0 session.lastvalidation session.lastvalidation {noformat} ### (/) I edited the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/osuser.xml file to comment out the current authentication mechanism and then uncomment the crowd one. ## (/) I then edited the /opt/atlassian-jira-standalone-3.13.5/conf/server/xml file and configured the database connection to the Jira_Temp database on Solstice2. I looked like this: {noformat} {noformat} ## (/) Edit the /opt/atlassian/jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/entityengine.xml and changed it from 'hsql' to 'mssql' and delete the line with "PUBLIC" in it per the instructions in the comments in that file. ## (/) I edited the /etc/httpd/conf/httpd.conf file and created a proxy pass at the bottom of the file to point a normal URL to the default port 8080 for JIRA: {noformat} # Proxy Pass for JIRA ProxyPass http://bugs.mbari.org:8080 ProxyPassReverse http://bugs.mbari.org:8080 {noformat} ## (/) I restarted Apache ## (/) I scp'd the jtds driver from oceana to the /opt/atlassian-jira-standalone-3.13.5/common/lib directory (you could down from the internet) ## (/) I then went to the /opt/atlassian-jira-standalone-3.13.5/ directory and ran './bin/startup.sh'. From the log file, I could tell things were hanging. After some troubleshooting I am wondering if the local firewall is preventing the application to get access to the database on solstice2. I can telnet to port 1433, but I can't browse to the base http://bugs.mbari.org from anywhere but the local web browser. I have submitted a ticket. ## (/) I restarted the old JIRA with my hopes dashed :(. ## (/) Pat disabled the firewall on bugs.mbari.org but it still hung trying to connect to solstice2.shore.mbari.org. That is really, really perplexing. Neil mentioned that solstice2 is using Kerberos and solstice is not. Checking with the JTDS docs, version 1.3.1 of the driver added kerberos support, so I downloaded that driver and added the 'userKerberos=true' property to the URL in the server.xml file and restarted. Got an error about no credentials, so added user and password properties to the URL. Nope, no luck. Never did figure this one out, but I had Pat pull the VM inside the firewall and after some thrash it worked. Well, it sort of worked ... sigh. It turns out I had downloaded the standard version instead of the enterprise version. I need to redo this work ... grrr. ## (/) I deleted all the tables in the Jira_Temp database and removed the /data/jira3135/indexes directory (and recreated). ## (/) I downloaded the enterprise version of the 3.13.5 server. I made a copy in the /opt directory and unzipped and untarred the file. ## (/) I went back to crowd and edited the application to change the properties to: ### URL: http://bugs.shore.mbari.org:8080 ### IP: 134.89.12.31 ### Name: jira3135 ### Password: (ask Kevin) :) ## (/) I then repeated the steps above to get the server up and running with the following differences: ### The server name is now bugs.shore.mbari.org ### The paths given above are a little different in that they no longer say "standard" but say "enterprise" ### I deleted the proxy pass as it seemed to have issues before and this is only temporary anyway. ## (/) I then browsed to http://bugs.shore.mbari.org:8080 ## (/) It took me to the start up page and at the top was the option to 'import your existing data'. Seemed too good not to try. I clicked on the link. It asked me for the backup file location and the location where the indexes would be stored. ## (/) I copied the XML zip file and the attachments tar file to the /data/original directory. ## (/) I created the /data/jira3135/indexes and used those directories ... it fired off the import and I waited. ## (/) I tailed the log file to watch the import. Holy crap, it worked!!! I could log in and everything! I copied the results from the log file here for posterity sake: {noformat} 2015-07-22 20:55:45,156 http-8080-Processor22 INFO [jira.action.admin.DataImport] Running data import 2015-07-22 20:55:45,179 http-8080-Processor22 INFO [jira.action.admin.DataImport] Importing data.. 2015-07-22 20:55:45,186 http-8080-Processor22 INFO [jira.action.admin.DataImport] Start parsing XML with SAX Parser 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] XML successfully parsed 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] Removing all entries from the database. 2015-07-22 20:56:24,593 http-8080-Processor22 INFO [jira.action.admin.DataImport] All entries removed. 2015-07-22 20:56:24,594 http-8080-Processor22 INFO [jira.action.admin.DataImport] Started storing 410414 Generic Values 2015-07-22 21:01:51,967 http-8080-Processor22 INFO [jira.action.admin.DataImport] Finished storing Generic Values 2015-07-22 21:01:52,329 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:52,361 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:54,683 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLink' to module 'jira.user.format:profile-link-user-format'. 2015-07-22 21:01:54,724 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullName' to module 'jira.user.format:full-name-user-format'. 2015-07-22 21:01:54,773 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkSearcher' to module 'jira.user.format:profile-link-searcher-user-format'. 2015-07-22 21:01:54,784 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkExternal' to module 'jira.user.format:profile-link-external-user-format'. 2015-07-22 21:01:54,795 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkActionHeader' to module 'jira.user.format:profile-link-action-header-user-format'. 2015-07-22 21:01:54,807 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullProfile' to module 'jira.user.format:full-profile-user-format'. 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/comments 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/issues 2015-07-22 21:01:55,641 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/plugins 2015-07-22 21:01:55,867 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:01:55,871 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/issues does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:55,873 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/comments does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,033 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,257 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,889 http-8080-Processor22 ERROR [atlassian.jira.upgrade.ConsistencyCheckImpl] Attachments are turned on, but attachment path [/data/jira_3_12/attachments] invalid - disabling attachments 2015-07-22 21:02:13,904 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Detected that an upgrade is needed; existing data at build 299 2015-07-22 21:02:13,907 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Doing Upgrade... 2015-07-22 21:02:13,915 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value' succeeded 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 317 2015-07-22 21:02:13,944 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite filters - make each filter a favourite of its owner. 2015-07-22 21:02:17,822 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build319] Could not find author 'fpy' for filter with id '10040' 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite filters - make each filter a favourite of its owner.' succeeded 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 319 2015-07-22 21:02:17,995 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise Share Permissions. Move old shares to new shares. 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise Share Permissions. Move old shares to new shares.' succeeded 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 321 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Migrating the old JIRA UI colors to the new JIRA 3.13 colors 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build322] Custom color detected for jira.lf.menu.bgcolour : #336699 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Migrating the old JIRA UI colors to the new JIRA 3.13 colors' succeeded 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 322 2015-07-22 21:02:18,025 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite dashboards - make each dashboard a favourite of its owner. 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'cmcgann' for dashboard with id '10030' 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'fpy' for dashboard with id '10060' 2015-07-22 21:02:18,423 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'kanna' for dashboard with id '10040' 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite dashboards - make each dashboard a favourite of its owner.' succeeded 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 325 2015-07-22 21:02:18,625 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Reindexing all data in JIRA to include Favourites. 2015-07-22 21:02:18,648 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All starting... 2015-07-22 21:02:18,650 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 0% complete. Current index: Issue 2015-07-22 21:02:18,654 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:02:18,809 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 1% complete. Current index: Issue 2015-07-22 21:02:18,855 indexerPool-2-thread-10 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 2% complete. Current index: Issue 2015-07-22 21:02:18,899 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 3% complete. Current index: Issue 2015-07-22 21:02:18,945 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 4% complete. Current index: Issue 2015-07-22 21:02:19,012 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 5% complete. Current index: Issue . . . 2015-07-22 21:02:26,164 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 95% complete. Current index: Issue 2015-07-22 21:02:26,232 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 96% complete. Current index: Issue 2015-07-22 21:02:26,316 indexerPool-2-thread-9 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 97% complete. Current index: Issue 2015-07-22 21:02:26,771 indexerPool-2-thread-3 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: Issue 2015-07-22 21:02:27,261 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 8607ms. Indexer: DefaultIndexManager: paths: [/data/jira3135/indexes/issues, /data/jira3135/indexes/comments] 2015-07-22 21:02:27,263 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: SearchRequest 2015-07-22 21:02:27,268 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,293 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: SearchRequest 2015-07-22 21:02:27,308 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: PortalPage 2015-07-22 21:02:27,312 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,377 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: PortalPage 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 115ms. Indexer: SharedEntityIndexManager: paths: [/data/jira3135/indexes/entities/portalpage, /data/jira3135/indexes/entities/searchrequest] 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All complete. Total time: 8722ms. 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Reindexing all data in JIRA to include Favourites.' succeeded 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 326 2015-07-22 21:02:27,397 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade succeeded! Setting data build number to 360 2015-07-22 21:02:27,469 JiraQuartzScheduler_Worker-0 WARN [service.services.export.ExportService] Backup directory /data/jira_3_12/backup does not exist {noformat} {warning:title=Paths} It appears that the upgraded JIRA will still look for the attachments and the backup locations in the original places. So I created /data/jira_3_12/backup and untarred the original attachments to /data/jira_3_12 and then everything worked (including attachements) in the new JIRA. {warning} ## (/) I then used the upgraded JIRA to generate a new XML backup and stored it in /data/original/3.13.5 along with another tar of the files in /data/jira_3_12/attachments. ## (/) I then shutdown the JIRA server. *I should be ready to move on to version 4 upgrade WHEW* ## So, before moving on, I decided that it would be a really good idea to spin up a new Crowd instance to get rid of the :8443 in the URL and to move off of RedHat per IS requests. I have a ticket in for a new VM and a new database to try to get this going. I am waiting on that before moving on. ## (/) Pat created the VM and Neil created the database. ## (/) I logged into auth.mbari.org (name of the VM) and downloaded crowd which I unzipped to the /opt directory ## (/) I then created a /data/crowd directory and gave my account permissions on it and then edited the /opt/atlassian..../crowd-webapp/WEB-INF/classes/crowd-init.properties file to set that as the crowd home directory. ## (/) The instructions say to download the JDBC driver, but they already have JTDS 1.2.7 in the download so I did not do anything. ## (/) You have to manually connect up CrowdID to a database as they setup wizard does not currently do this. ### (/) They say to download the driver, but again 1.2.7 was there so I did nothing. ### (/) I edited the /opt/atlassian.../apache-tomcat/conf/Catalina/localhost/openidserver.xml to look like: {noformat} {noformat} ### (/) I edited the /opt/atlassian.../build.properties files to look like: {noformat} # Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See https://confluence.atlassian.com/display/CROWD/Connecting+Crowd+to+a+Database hibernate.dialect=org.hibernate.dialect.SQLServerDialect # The Hibernate transaction factory to use. See https://confluence.atlassian.com/display/CROWD/Configuring+Crowd hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory # The http port you wish to run crowd from, ie: http://localhost:8095/crowd crowd.tomcat.connector.port=8095 # Tomcat requires a unique port for shutdown crowd.tomcat.shutdown.port=8020 # Crowd context root crowd.url=http://localhost:8095/crowd # Demo context root demo.url=http://localhost:8095/demo # OpenID server context root openidserver.url=http://localhost:8095/openidserver {noformat} ### (/) I then ran the build.sh script in the root of /opt/atlassian... ## (/) I fired up crowd using the /opt/atlassian.../start_crowd.sh script ## (/) I then went to http://auth.mbari.org:8095/crowd to kick off the start up wizard ## (/) I grabbed a new eval license from my account on atlassian and pasted into the license page. ## (/) I selected "New install" on the next page. ## (/) I configured the JDBC connection using this connection URL with user DB_Collaboration {noformat} jdbc:jtds:sqlserver://dione.mbari.org:51001/Crowd;domain=SHORE;useNTLMv2=TRUE {noformat} ## (/) I left the "Options" as they came up {warning:title=Paths} Not sure if this is a problem, but because I started the set up using auth.mbari.org, it set the Base URL to http://auth.mbari.org:8095/crowd instead of localhost. Hope that is not a problem. We will see. {warning} ## (/) I fired up crowd and then went to the http://localhost:8095 URL to start the configuration. I input the DB connection parameters and it created the DB and took off just fine. I really wanted to run the application on port 80 and 443 as normal applications do so I first tried to change the port numbers that the application ran on. That did not work as those are privileged ports and cannot be controller unless you are root. I did not want to do that, so I will have to do a proxy pass. I had to start up the httpd services (I will need to configure as a service) and then created a new file in /etc/httpd/conf.d called crowd.conf that contained the following: {noformat} # This is the configuration for the proxy pass for the crowd server ProxyRequests Off ProxyPreserveHost On Require all granted ProxyPass /crowd http://auth.mbari.org:8095/crowd ProxyPassReverse /crowd http://auth.mbari.org:8095/crowd Require all granted ProxyPass /openidserver http://auth.mbari.org:8095/openidserver ProxyPassReverse /openidserver http://auth.mbari.org:8095/openidserver Require all granted {noformat} ## (/) This worked for the basic HTTP so I will have to get it working with SSL. ## (/) Something with the openidserver is not working correctly and I suspect I have not done the openidserver install completely or correctly. I read the directions on configuring crowdid and it's connection to the database and restarted the crowd server. That worked, not I have both working of straight HTTP, now I need to get SSL going. ## (/) I originally started to configure SSL for the Tomcat server for Crowd, but then realized, since I am putting the Apache proxy in front of Tomcat, I should be able to just set up SSL on Apache HTTP and leave Tomcat alone (i.e. traffic between Apache HTTP and Tomcat does not need to be encrypted). # Schedule upgrade date and send all hands several days in advance. # When the day arrives, send all hands announcing JIRA outage. # From the Administrator's page in our existing JIRA, perform a 'Backup Data to XML'. # Login to oceana.mbari.org as root. # Shutdown JIRA # Create a tar.gz of the /opt/atlassian-jira-enterprise-3.12.1-standalone directory # Clean up the /data/jira_3_12/backups directory by deleting all but maybe the last 5 backups. # Create a tar.gz of the JIRA home directory on ocean.mbari.org which is located at /data/jira_3_12 # scp both tar.gz files to bugs.mbari.org # login to bugs.mbari.org # Unpack the home directory tar to /data/jira # Run the installer as root (this might need IS help or sudo privs). Note that we usually install the application to /opt # Run the JIRA Configuration tool to set the jira.home to the /data/jira location # Connect to JIRA_Temp database on Solstice2 (.... more to do here, see Atlassian docs) # Migrate existing configuration over to new JIRA (I need to add more here as we added Crowd). # Start JIRA # Import backed up XML # Perform post upgrades checks and tests *Need to document steps for 4.4.5->6.X*]]> 27558105 19073789 19041098 27590864 4.4: [https://confluence.atlassian.com/display/JIRA044/Migrating+JIRA+to+Another+Server] ## The JIRA configuration tool: [https://confluence.atlassian.com/display/JIRA044/Using+the+JIRA+Configuration+Tool] h5. Steps # (/) Create new VM named bugs.mbari.org in the DMZ # (/) Have Neil create database Jira_Temp on solstice2.shore.mbari.org # (/) Have Neil create database Jira on solstice2.shore.mbari.org # (/) Have Pat install Java 7 on bugs.shore.mbari.org # (/) Have Pete plumb holes through firewall so processes on bugs.mbari.org can get to Solstice2 # (/) Have Pat create DB_Collaboration account on bugs so it can run JIRA under that account and it can connect to solstice2 using that NT Domain account. # (/) Upgrade license on Atlassian site # (/) Log into bugs.shore.mbari.org # (/) Download 3.13.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 4.4.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 5.2.11 standalone Linux 64 bit tar.gz (not sure this version is necessary, but at least I have it) # (/) Unzip and untar the file to /opt # (/) Download latest JIRA (6.4.7 as of this writing). # (/) Unzip and untar it to /opt # Performed Test Upgrade ## (/) In order to export the current stuff in JIRA, I had to shut off access so people could not change the data while I was backing it up. ## (/) I ssh'd to oceana.mbari.org as root and edited the /opt/jira/conf/server.xml file and commented out the Connector section that had the port of 8010 to shut it off from the normal serving route. ## (/) I uncommented the 8082 port connector and the 8443 port connector so that I could still get to the server. ## (/) I stopped and started the JIRA server and in the log file I got a "keystore was tampered with..." which is not surprising. ## (/) I could then browser over to http://oceana.mbari.org:8082/jira ## (/) Then through the Administration console, I did an XML backup ## (/) I then created a tar of all the attachments in the /data/jira_3_12/attachments directory ## (/) I moved both the XML and tar files to the /root/jira-upgrade directory ## (/) I then reversed the changes to the server.xml file and shut down JIRA ## (/) I left it down during the next steps in case it went so well, I could just point people to the new server (yeah, right). ## (/) I then browsed to the crowd server on oceana and add a new application using: ### URL: http://bugs.mbari.org/jira3135 ### IP: 134.89.2.29 ### Name: JIRA3135 ### Password: (ask Kevin) :) ## (/) On bugs, I made a copy of the JIRA 3.13.5 download in the /opt directory and unzipped and untarred it. ## (/) In order to configure the crowd connection I did the following: ### (/) I scp'd the /opt/crowd/client/crowd-integration-client-1.6.jar file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I removed the existing 1.6.1 crowd client jar from the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I scp'd the /opt/crowd/client/conf/crowd.properties file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I scp'd the /opt/crowd/client/conf/crowd-ehcache.xml file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I edited the crowd.properties file on bugs to look like: {noformat} application.name JIRA3135 application.password (ask Kevin) application.login.url http://oceana.mbari.org:8095/crowd/console/ crowd.server.url http://oceana.mbari.org:8095/crowd/services/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 0 session.lastvalidation session.lastvalidation {noformat} ### (/) I edited the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/osuser.xml file to comment out the current authentication mechanism and then uncomment the crowd one. ## (/) I then edited the /opt/atlassian-jira-standalone-3.13.5/conf/server/xml file and configured the database connection to the Jira_Temp database on Solstice2. I looked like this: {noformat} {noformat} ## (/) Edit the /opt/atlassian/jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/entityengine.xml and changed it from 'hsql' to 'mssql' and delete the line with "PUBLIC" in it per the instructions in the comments in that file. ## (/) I edited the /etc/httpd/conf/httpd.conf file and created a proxy pass at the bottom of the file to point a normal URL to the default port 8080 for JIRA: {noformat} # Proxy Pass for JIRA ProxyPass http://bugs.mbari.org:8080 ProxyPassReverse http://bugs.mbari.org:8080 {noformat} ## (/) I restarted Apache ## (/) I scp'd the jtds driver from oceana to the /opt/atlassian-jira-standalone-3.13.5/common/lib directory (you could down from the internet) ## (/) I then went to the /opt/atlassian-jira-standalone-3.13.5/ directory and ran './bin/startup.sh'. From the log file, I could tell things were hanging. After some troubleshooting I am wondering if the local firewall is preventing the application to get access to the database on solstice2. I can telnet to port 1433, but I can't browse to the base http://bugs.mbari.org from anywhere but the local web browser. I have submitted a ticket. ## (/) I restarted the old JIRA with my hopes dashed :(. ## (/) Pat disabled the firewall on bugs.mbari.org but it still hung trying to connect to solstice2.shore.mbari.org. That is really, really perplexing. Neil mentioned that solstice2 is using Kerberos and solstice is not. Checking with the JTDS docs, version 1.3.1 of the driver added kerberos support, so I downloaded that driver and added the 'userKerberos=true' property to the URL in the server.xml file and restarted. Got an error about no credentials, so added user and password properties to the URL. Nope, no luck. Never did figure this one out, but I had Pat pull the VM inside the firewall and after some thrash it worked. Well, it sort of worked ... sigh. It turns out I had downloaded the standard version instead of the enterprise version. I need to redo this work ... grrr. ## (/) I deleted all the tables in the Jira_Temp database and removed the /data/jira3135/indexes directory (and recreated). ## (/) I downloaded the enterprise version of the 3.13.5 server. I made a copy in the /opt directory and unzipped and untarred the file. ## (/) I went back to crowd and edited the application to change the properties to: ### URL: http://bugs.shore.mbari.org:8080 ### IP: 134.89.12.31 ### Name: jira3135 ### Password: (ask Kevin) :) ## (/) I then repeated the steps above to get the server up and running with the following differences: ### The server name is now bugs.shore.mbari.org ### The paths given above are a little different in that they no longer say "standard" but say "enterprise" ### I deleted the proxy pass as it seemed to have issues before and this is only temporary anyway. ## (/) I then browsed to http://bugs.shore.mbari.org:8080 ## (/) It took me to the start up page and at the top was the option to 'import your existing data'. Seemed too good not to try. I clicked on the link. It asked me for the backup file location and the location where the indexes would be stored. ## (/) I copied the XML zip file and the attachments tar file to the /data/original directory. ## (/) I created the /data/jira3135/indexes and used those directories ... it fired off the import and I waited. ## (/) I tailed the log file to watch the import. Holy crap, it worked!!! I could log in and everything! I copied the results from the log file here for posterity sake: {noformat} 2015-07-22 20:55:45,156 http-8080-Processor22 INFO [jira.action.admin.DataImport] Running data import 2015-07-22 20:55:45,179 http-8080-Processor22 INFO [jira.action.admin.DataImport] Importing data.. 2015-07-22 20:55:45,186 http-8080-Processor22 INFO [jira.action.admin.DataImport] Start parsing XML with SAX Parser 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] XML successfully parsed 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] Removing all entries from the database. 2015-07-22 20:56:24,593 http-8080-Processor22 INFO [jira.action.admin.DataImport] All entries removed. 2015-07-22 20:56:24,594 http-8080-Processor22 INFO [jira.action.admin.DataImport] Started storing 410414 Generic Values 2015-07-22 21:01:51,967 http-8080-Processor22 INFO [jira.action.admin.DataImport] Finished storing Generic Values 2015-07-22 21:01:52,329 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:52,361 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:54,683 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLink' to module 'jira.user.format:profile-link-user-format'. 2015-07-22 21:01:54,724 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullName' to module 'jira.user.format:full-name-user-format'. 2015-07-22 21:01:54,773 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkSearcher' to module 'jira.user.format:profile-link-searcher-user-format'. 2015-07-22 21:01:54,784 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkExternal' to module 'jira.user.format:profile-link-external-user-format'. 2015-07-22 21:01:54,795 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkActionHeader' to module 'jira.user.format:profile-link-action-header-user-format'. 2015-07-22 21:01:54,807 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullProfile' to module 'jira.user.format:full-profile-user-format'. 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/comments 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/issues 2015-07-22 21:01:55,641 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/plugins 2015-07-22 21:01:55,867 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:01:55,871 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/issues does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:55,873 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/comments does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,033 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,257 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,889 http-8080-Processor22 ERROR [atlassian.jira.upgrade.ConsistencyCheckImpl] Attachments are turned on, but attachment path [/data/jira_3_12/attachments] invalid - disabling attachments 2015-07-22 21:02:13,904 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Detected that an upgrade is needed; existing data at build 299 2015-07-22 21:02:13,907 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Doing Upgrade... 2015-07-22 21:02:13,915 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value' succeeded 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 317 2015-07-22 21:02:13,944 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite filters - make each filter a favourite of its owner. 2015-07-22 21:02:17,822 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build319] Could not find author 'fpy' for filter with id '10040' 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite filters - make each filter a favourite of its owner.' succeeded 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 319 2015-07-22 21:02:17,995 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise Share Permissions. Move old shares to new shares. 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise Share Permissions. Move old shares to new shares.' succeeded 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 321 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Migrating the old JIRA UI colors to the new JIRA 3.13 colors 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build322] Custom color detected for jira.lf.menu.bgcolour : #336699 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Migrating the old JIRA UI colors to the new JIRA 3.13 colors' succeeded 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 322 2015-07-22 21:02:18,025 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite dashboards - make each dashboard a favourite of its owner. 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'cmcgann' for dashboard with id '10030' 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'fpy' for dashboard with id '10060' 2015-07-22 21:02:18,423 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'kanna' for dashboard with id '10040' 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite dashboards - make each dashboard a favourite of its owner.' succeeded 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 325 2015-07-22 21:02:18,625 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Reindexing all data in JIRA to include Favourites. 2015-07-22 21:02:18,648 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All starting... 2015-07-22 21:02:18,650 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 0% complete. Current index: Issue 2015-07-22 21:02:18,654 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:02:18,809 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 1% complete. Current index: Issue 2015-07-22 21:02:18,855 indexerPool-2-thread-10 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 2% complete. Current index: Issue 2015-07-22 21:02:18,899 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 3% complete. Current index: Issue 2015-07-22 21:02:18,945 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 4% complete. Current index: Issue 2015-07-22 21:02:19,012 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 5% complete. Current index: Issue . . . 2015-07-22 21:02:26,164 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 95% complete. Current index: Issue 2015-07-22 21:02:26,232 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 96% complete. Current index: Issue 2015-07-22 21:02:26,316 indexerPool-2-thread-9 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 97% complete. Current index: Issue 2015-07-22 21:02:26,771 indexerPool-2-thread-3 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: Issue 2015-07-22 21:02:27,261 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 8607ms. Indexer: DefaultIndexManager: paths: [/data/jira3135/indexes/issues, /data/jira3135/indexes/comments] 2015-07-22 21:02:27,263 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: SearchRequest 2015-07-22 21:02:27,268 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,293 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: SearchRequest 2015-07-22 21:02:27,308 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: PortalPage 2015-07-22 21:02:27,312 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,377 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: PortalPage 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 115ms. Indexer: SharedEntityIndexManager: paths: [/data/jira3135/indexes/entities/portalpage, /data/jira3135/indexes/entities/searchrequest] 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All complete. Total time: 8722ms. 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Reindexing all data in JIRA to include Favourites.' succeeded 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 326 2015-07-22 21:02:27,397 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade succeeded! Setting data build number to 360 2015-07-22 21:02:27,469 JiraQuartzScheduler_Worker-0 WARN [service.services.export.ExportService] Backup directory /data/jira_3_12/backup does not exist {noformat} {warning:title=Paths} It appears that the upgraded JIRA will still look for the attachments and the backup locations in the original places. So I created /data/jira_3_12/backup and untarred the original attachments to /data/jira_3_12 and then everything worked (including attachements) in the new JIRA. {warning} ## (/) I then used the upgraded JIRA to generate a new XML backup and stored it in /data/original/3.13.5 along with another tar of the files in /data/jira_3_12/attachments. ## (/) I then shutdown the JIRA server. *I should be ready to move on to version 4 upgrade WHEW* ## So, before moving on, I decided that it would be a really good idea to spin up a new Crowd instance to get rid of the :8443 in the URL and to move off of RedHat per IS requests. I have a ticket in for a new VM and a new database to try to get this going. I am waiting on that before moving on. ## (/) Pat created the VM and Neil created the database. ## (/) I logged into auth.mbari.org (name of the VM) and downloaded crowd which I unzipped to the /opt directory ## (/) I then created a /data/crowd directory and gave my account permissions on it and then edited the /opt/atlassian..../crowd-webapp/WEB-INF/classes/crowd-init.properties file to set that as the crowd home directory. ## (/) The instructions say to download the JDBC driver, but they already have JTDS 1.2.7 in the download so I did not do anything. ## (/) You have to manually connect up CrowdID to a database as they setup wizard does not currently do this. ### (/) They say to download the driver, but again 1.2.7 was there so I did nothing. ### (/) I edited the /opt/atlassian.../apache-tomcat/conf/Catalina/localhost/openidserver.xml to look like: {noformat} {noformat} ### (/) I edited the /opt/atlassian.../build.properties files to look like: {noformat} # Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See https://confluence.atlassian.com/display/CROWD/Connecting+Crowd+to+a+Database hibernate.dialect=org.hibernate.dialect.SQLServerDialect # The Hibernate transaction factory to use. See https://confluence.atlassian.com/display/CROWD/Configuring+Crowd hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory # The http port you wish to run crowd from, ie: http://localhost:8095/crowd crowd.tomcat.connector.port=8095 # Tomcat requires a unique port for shutdown crowd.tomcat.shutdown.port=8020 # Crowd context root crowd.url=http://localhost:8095/crowd # Demo context root demo.url=http://localhost:8095/demo # OpenID server context root openidserver.url=http://localhost:8095/openidserver {noformat} ### (/) I then ran the build.sh script in the root of /opt/atlassian... ## (/) I fired up crowd using the /opt/atlassian.../start_crowd.sh script ## (/) I then went to http://auth.mbari.org:8095/crowd to kick off the start up wizard ## (/) I grabbed a new eval license from my account on atlassian and pasted into the license page. ## (/) I selected "New install" on the next page. ## (/) I fired up crowd and then went to the http://localhost:8095 URL to start the configuration. I input the DB connection parameters and it created the DB and took off just fine. I really wanted to run the application on port 80 and 443 as normal applications do so I first tried to change the port numbers that the application ran on. That did not work as those are privileged ports and cannot be controller unless you are root. I did not want to do that, so I will have to do a proxy pass. I had to start up the httpd services (I will need to configure as a service) and then created a new file in /etc/httpd/conf.d called crowd.conf that contained the following: {noformat} # This is the configuration for the proxy pass for the crowd server ProxyRequests Off ProxyPreserveHost On Require all granted ProxyPass /crowd http://auth.mbari.org:8095/crowd ProxyPassReverse /crowd http://auth.mbari.org:8095/crowd Require all granted ProxyPass /openidserver http://auth.mbari.org:8095/openidserver ProxyPassReverse /openidserver http://auth.mbari.org:8095/openidserver Require all granted {noformat} ## (/) This worked for the basic HTTP so I will have to get it working with SSL. ## (/) Something with the openidserver is not working correctly and I suspect I have not done the openidserver install completely or correctly. I read the directions on configuring crowdid and it's connection to the database and restarted the crowd server. That worked, not I have both working of straight HTTP, now I need to get SSL going. ## (/) I originally started to configure SSL for the Tomcat server for Crowd, but then realized, since I am putting the Apache proxy in front of Tomcat, I should be able to just set up SSL on Apache HTTP and leave Tomcat alone (i.e. traffic between Apache HTTP and Tomcat does not need to be encrypted). # Schedule upgrade date and send all hands several days in advance. # When the day arrives, send all hands announcing JIRA outage. # From the Administrator's page in our existing JIRA, perform a 'Backup Data to XML'. # Login to oceana.mbari.org as root. # Shutdown JIRA # Create a tar.gz of the /opt/atlassian-jira-enterprise-3.12.1-standalone directory # Clean up the /data/jira_3_12/backups directory by deleting all but maybe the last 5 backups. # Create a tar.gz of the JIRA home directory on ocean.mbari.org which is located at /data/jira_3_12 # scp both tar.gz files to bugs.mbari.org # login to bugs.mbari.org # Unpack the home directory tar to /data/jira # Run the installer as root (this might need IS help or sudo privs). Note that we usually install the application to /opt # Run the JIRA Configuration tool to set the jira.home to the /data/jira location # Connect to JIRA_Temp database on Solstice2 (.... more to do here, see Atlassian docs) # Migrate existing configuration over to new JIRA (I need to add more here as we added Crowd). # Start JIRA # Import backed up XML # Perform post upgrades checks and tests *Need to document steps for 4.4.5->6.X*]]> 27558099 27590866 4.4: [https://confluence.atlassian.com/display/JIRA044/Migrating+JIRA+to+Another+Server] ## The JIRA configuration tool: [https://confluence.atlassian.com/display/JIRA044/Using+the+JIRA+Configuration+Tool] h5. Steps # (/) Create new VM named bugs.mbari.org in the DMZ # (/) Have Neil create database Jira_Temp on solstice2.shore.mbari.org # (/) Have Neil create database Jira on solstice2.shore.mbari.org # (/) Have Pat install Java 7 on bugs.shore.mbari.org # (/) Have Pete plumb holes through firewall so processes on bugs.mbari.org can get to Solstice2 # (/) Have Pat create DB_Collaboration account on bugs so it can run JIRA under that account and it can connect to solstice2 using that NT Domain account. # (/) Upgrade license on Atlassian site # (/) Log into bugs.shore.mbari.org # (/) Download 3.13.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 4.4.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 5.2.11 standalone Linux 64 bit tar.gz (not sure this version is necessary, but at least I have it) # (/) Unzip and untar the file to /opt # (/) Download latest JIRA (6.4.7 as of this writing). # (/) Unzip and untar it to /opt # Performed Test Upgrade ## (/) In order to export the current stuff in JIRA, I had to shut off access so people could not change the data while I was backing it up. ## (/) I ssh'd to oceana.mbari.org as root and edited the /opt/jira/conf/server.xml file and commented out the Connector section that had the port of 8010 to shut it off from the normal serving route. ## (/) I uncommented the 8082 port connector and the 8443 port connector so that I could still get to the server. ## (/) I stopped and started the JIRA server and in the log file I got a "keystore was tampered with..." which is not surprising. ## (/) I could then browser over to http://oceana.mbari.org:8082/jira ## (/) Then through the Administration console, I did an XML backup ## (/) I then created a tar of all the attachments in the /data/jira_3_12/attachments directory ## (/) I moved both the XML and tar files to the /root/jira-upgrade directory ## (/) I then reversed the changes to the server.xml file and shut down JIRA ## (/) I left it down during the next steps in case it went so well, I could just point people to the new server (yeah, right). ## (/) I then browsed to the crowd server on oceana and add a new application using: ### URL: http://bugs.mbari.org/jira3135 ### IP: 134.89.2.29 ### Name: JIRA3135 ### Password: (ask Kevin) :) ## (/) On bugs, I made a copy of the JIRA 3.13.5 download in the /opt directory and unzipped and untarred it. ## (/) In order to configure the crowd connection I did the following: ### (/) I scp'd the /opt/crowd/client/crowd-integration-client-1.6.jar file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I removed the existing 1.6.1 crowd client jar from the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I scp'd the /opt/crowd/client/conf/crowd.properties file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I scp'd the /opt/crowd/client/conf/crowd-ehcache.xml file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I edited the crowd.properties file on bugs to look like: {noformat} application.name JIRA3135 application.password (ask Kevin) application.login.url http://oceana.mbari.org:8095/crowd/console/ crowd.server.url http://oceana.mbari.org:8095/crowd/services/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 0 session.lastvalidation session.lastvalidation {noformat} ### (/) I edited the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/osuser.xml file to comment out the current authentication mechanism and then uncomment the crowd one. ## (/) I then edited the /opt/atlassian-jira-standalone-3.13.5/conf/server/xml file and configured the database connection to the Jira_Temp database on Solstice2. I looked like this: {noformat} {noformat} ## (/) Edit the /opt/atlassian/jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/entityengine.xml and changed it from 'hsql' to 'mssql' and delete the line with "PUBLIC" in it per the instructions in the comments in that file. ## (/) I edited the /etc/httpd/conf/httpd.conf file and created a proxy pass at the bottom of the file to point a normal URL to the default port 8080 for JIRA: {noformat} # Proxy Pass for JIRA ProxyPass http://bugs.mbari.org:8080 ProxyPassReverse http://bugs.mbari.org:8080 {noformat} ## (/) I restarted Apache ## (/) I scp'd the jtds driver from oceana to the /opt/atlassian-jira-standalone-3.13.5/common/lib directory (you could down from the internet) ## (/) I then went to the /opt/atlassian-jira-standalone-3.13.5/ directory and ran './bin/startup.sh'. From the log file, I could tell things were hanging. After some troubleshooting I am wondering if the local firewall is preventing the application to get access to the database on solstice2. I can telnet to port 1433, but I can't browse to the base http://bugs.mbari.org from anywhere but the local web browser. I have submitted a ticket. ## (/) I restarted the old JIRA with my hopes dashed :(. ## (/) Pat disabled the firewall on bugs.mbari.org but it still hung trying to connect to solstice2.shore.mbari.org. That is really, really perplexing. Neil mentioned that solstice2 is using Kerberos and solstice is not. Checking with the JTDS docs, version 1.3.1 of the driver added kerberos support, so I downloaded that driver and added the 'userKerberos=true' property to the URL in the server.xml file and restarted. Got an error about no credentials, so added user and password properties to the URL. Nope, no luck. Never did figure this one out, but I had Pat pull the VM inside the firewall and after some thrash it worked. Well, it sort of worked ... sigh. It turns out I had downloaded the standard version instead of the enterprise version. I need to redo this work ... grrr. ## (/) I deleted all the tables in the Jira_Temp database and removed the /data/jira3135/indexes directory (and recreated). ## (/) I downloaded the enterprise version of the 3.13.5 server. I made a copy in the /opt directory and unzipped and untarred the file. ## (/) I went back to crowd and edited the application to change the properties to: ### URL: http://bugs.shore.mbari.org:8080 ### IP: 134.89.12.31 ### Name: jira3135 ### Password: (ask Kevin) :) ## (/) I then repeated the steps above to get the server up and running with the following differences: ### The server name is now bugs.shore.mbari.org ### The paths given above are a little different in that they no longer say "standard" but say "enterprise" ### I deleted the proxy pass as it seemed to have issues before and this is only temporary anyway. ## (/) I then browsed to http://bugs.shore.mbari.org:8080 ## (/) It took me to the start up page and at the top was the option to 'import your existing data'. Seemed too good not to try. I clicked on the link. It asked me for the backup file location and the location where the indexes would be stored. ## (/) I copied the XML zip file and the attachments tar file to the /data/original directory. ## (/) I created the /data/jira3135/indexes and used those directories ... it fired off the import and I waited. ## (/) I tailed the log file to watch the import. Holy crap, it worked!!! I could log in and everything! I copied the results from the log file here for posterity sake: {noformat} 2015-07-22 20:55:45,156 http-8080-Processor22 INFO [jira.action.admin.DataImport] Running data import 2015-07-22 20:55:45,179 http-8080-Processor22 INFO [jira.action.admin.DataImport] Importing data.. 2015-07-22 20:55:45,186 http-8080-Processor22 INFO [jira.action.admin.DataImport] Start parsing XML with SAX Parser 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] XML successfully parsed 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] Removing all entries from the database. 2015-07-22 20:56:24,593 http-8080-Processor22 INFO [jira.action.admin.DataImport] All entries removed. 2015-07-22 20:56:24,594 http-8080-Processor22 INFO [jira.action.admin.DataImport] Started storing 410414 Generic Values 2015-07-22 21:01:51,967 http-8080-Processor22 INFO [jira.action.admin.DataImport] Finished storing Generic Values 2015-07-22 21:01:52,329 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:52,361 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:54,683 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLink' to module 'jira.user.format:profile-link-user-format'. 2015-07-22 21:01:54,724 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullName' to module 'jira.user.format:full-name-user-format'. 2015-07-22 21:01:54,773 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkSearcher' to module 'jira.user.format:profile-link-searcher-user-format'. 2015-07-22 21:01:54,784 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkExternal' to module 'jira.user.format:profile-link-external-user-format'. 2015-07-22 21:01:54,795 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkActionHeader' to module 'jira.user.format:profile-link-action-header-user-format'. 2015-07-22 21:01:54,807 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullProfile' to module 'jira.user.format:full-profile-user-format'. 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/comments 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/issues 2015-07-22 21:01:55,641 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/plugins 2015-07-22 21:01:55,867 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:01:55,871 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/issues does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:55,873 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/comments does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,033 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,257 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,889 http-8080-Processor22 ERROR [atlassian.jira.upgrade.ConsistencyCheckImpl] Attachments are turned on, but attachment path [/data/jira_3_12/attachments] invalid - disabling attachments 2015-07-22 21:02:13,904 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Detected that an upgrade is needed; existing data at build 299 2015-07-22 21:02:13,907 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Doing Upgrade... 2015-07-22 21:02:13,915 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value' succeeded 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 317 2015-07-22 21:02:13,944 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite filters - make each filter a favourite of its owner. 2015-07-22 21:02:17,822 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build319] Could not find author 'fpy' for filter with id '10040' 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite filters - make each filter a favourite of its owner.' succeeded 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 319 2015-07-22 21:02:17,995 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise Share Permissions. Move old shares to new shares. 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise Share Permissions. Move old shares to new shares.' succeeded 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 321 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Migrating the old JIRA UI colors to the new JIRA 3.13 colors 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build322] Custom color detected for jira.lf.menu.bgcolour : #336699 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Migrating the old JIRA UI colors to the new JIRA 3.13 colors' succeeded 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 322 2015-07-22 21:02:18,025 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite dashboards - make each dashboard a favourite of its owner. 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'cmcgann' for dashboard with id '10030' 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'fpy' for dashboard with id '10060' 2015-07-22 21:02:18,423 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'kanna' for dashboard with id '10040' 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite dashboards - make each dashboard a favourite of its owner.' succeeded 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 325 2015-07-22 21:02:18,625 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Reindexing all data in JIRA to include Favourites. 2015-07-22 21:02:18,648 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All starting... 2015-07-22 21:02:18,650 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 0% complete. Current index: Issue 2015-07-22 21:02:18,654 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:02:18,809 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 1% complete. Current index: Issue 2015-07-22 21:02:18,855 indexerPool-2-thread-10 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 2% complete. Current index: Issue 2015-07-22 21:02:18,899 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 3% complete. Current index: Issue 2015-07-22 21:02:18,945 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 4% complete. Current index: Issue 2015-07-22 21:02:19,012 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 5% complete. Current index: Issue . . . 2015-07-22 21:02:26,164 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 95% complete. Current index: Issue 2015-07-22 21:02:26,232 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 96% complete. Current index: Issue 2015-07-22 21:02:26,316 indexerPool-2-thread-9 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 97% complete. Current index: Issue 2015-07-22 21:02:26,771 indexerPool-2-thread-3 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: Issue 2015-07-22 21:02:27,261 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 8607ms. Indexer: DefaultIndexManager: paths: [/data/jira3135/indexes/issues, /data/jira3135/indexes/comments] 2015-07-22 21:02:27,263 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: SearchRequest 2015-07-22 21:02:27,268 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,293 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: SearchRequest 2015-07-22 21:02:27,308 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: PortalPage 2015-07-22 21:02:27,312 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,377 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: PortalPage 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 115ms. Indexer: SharedEntityIndexManager: paths: [/data/jira3135/indexes/entities/portalpage, /data/jira3135/indexes/entities/searchrequest] 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All complete. Total time: 8722ms. 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Reindexing all data in JIRA to include Favourites.' succeeded 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 326 2015-07-22 21:02:27,397 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade succeeded! Setting data build number to 360 2015-07-22 21:02:27,469 JiraQuartzScheduler_Worker-0 WARN [service.services.export.ExportService] Backup directory /data/jira_3_12/backup does not exist {noformat} {warning:title=Paths} It appears that the upgraded JIRA will still look for the attachments and the backup locations in the original places. So I created /data/jira_3_12/backup and untarred the original attachments to /data/jira_3_12 and then everything worked (including attachements) in the new JIRA. {warning} ## (/) I then used the upgraded JIRA to generate a new XML backup and stored it in /data/original/3.13.5 along with another tar of the files in /data/jira_3_12/attachments. ## (/) I then shutdown the JIRA server. *I should be ready to move on to version 4 upgrade WHEW* ## So, before moving on, I decided that it would be a really good idea to spin up a new Crowd instance to get rid of the :8443 in the URL and to move off of RedHat per IS requests. I have a ticket in for a new VM and a new database to try to get this going. I am waiting on that before moving on. ## (/) Pat created the VM and Neil created the database. ## (/) I logged into auth.mbari.org (name of the VM) and downloaded crowd which I unzipped to the /opt directory ## (/) I then created a /data/crowd directory and gave my account permissions on it and then edited the /opt/atlassian..../crowd-webapp/WEB-INF/classes/crowd-init.properties file to set that as the crowd home directory. ## (/) The instructions say to download the JDBC driver, but they already have JTDS 1.2.7 in the download so I did not do anything. ## (/) You have to manually connect up CrowdID to a database as they setup wizard does not currently do this. ### (/) They say to download the driver, but again 1.2.7 was there so I did nothing. ### (/) I edited the /opt/atlassian.../apache-tomcat/conf/Catalina/localhost/openidserver.xml to look like: {noformat} {noformat} ### (/) I edited the /opt/atlassian.../build.properties files to look like: {noformat} # Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See https://confluence.atlassian.com/display/CROWD/Connecting+Crowd+to+a+Database hibernate.dialect=org.hibernate.dialect.SQLServerDialect # The Hibernate transaction factory to use. See https://confluence.atlassian.com/display/CROWD/Configuring+Crowd hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory # The http port you wish to run crowd from, ie: http://localhost:8095/crowd crowd.tomcat.connector.port=8095 # Tomcat requires a unique port for shutdown crowd.tomcat.shutdown.port=8020 # Crowd context root crowd.url=http://localhost:8095/crowd # Demo context root demo.url=http://localhost:8095/demo # OpenID server context root openidserver.url=http://localhost:8095/openidserver {noformat} ### (/) I then ran the build.sh script in the root of /opt/atlassian... ## (/) I fired up crowd using the /opt/atlassian.../start_crowd.sh script ## (/) I then went to http://auth.mbari.org:8095/crowd to kick off the start up wizard ## (/) I grabbed a new eval license from my account on atlassian and pasted into the license page. ## (/) I selected "New install" on the next page. ## (/) I configured the JDBC connection using this connection URL with user DB_Collaboration {noformat} jdbc:jtds:sqlserver://dione.mbari.org:51001:Crowd;domain=SHORE;useNTLMv2=TRUE {noformat} ## (/) I fired up crowd and then went to the http://localhost:8095 URL to start the configuration. I input the DB connection parameters and it created the DB and took off just fine. I really wanted to run the application on port 80 and 443 as normal applications do so I first tried to change the port numbers that the application ran on. That did not work as those are privileged ports and cannot be controller unless you are root. I did not want to do that, so I will have to do a proxy pass. I had to start up the httpd services (I will need to configure as a service) and then created a new file in /etc/httpd/conf.d called crowd.conf that contained the following: {noformat} # This is the configuration for the proxy pass for the crowd server ProxyRequests Off ProxyPreserveHost On Require all granted ProxyPass /crowd http://auth.mbari.org:8095/crowd ProxyPassReverse /crowd http://auth.mbari.org:8095/crowd Require all granted ProxyPass /openidserver http://auth.mbari.org:8095/openidserver ProxyPassReverse /openidserver http://auth.mbari.org:8095/openidserver Require all granted {noformat} ## (/) This worked for the basic HTTP so I will have to get it working with SSL. ## (/) Something with the openidserver is not working correctly and I suspect I have not done the openidserver install completely or correctly. I read the directions on configuring crowdid and it's connection to the database and restarted the crowd server. That worked, not I have both working of straight HTTP, now I need to get SSL going. ## (/) I originally started to configure SSL for the Tomcat server for Crowd, but then realized, since I am putting the Apache proxy in front of Tomcat, I should be able to just set up SSL on Apache HTTP and leave Tomcat alone (i.e. traffic between Apache HTTP and Tomcat does not need to be encrypted). # Schedule upgrade date and send all hands several days in advance. # When the day arrives, send all hands announcing JIRA outage. # From the Administrator's page in our existing JIRA, perform a 'Backup Data to XML'. # Login to oceana.mbari.org as root. # Shutdown JIRA # Create a tar.gz of the /opt/atlassian-jira-enterprise-3.12.1-standalone directory # Clean up the /data/jira_3_12/backups directory by deleting all but maybe the last 5 backups. # Create a tar.gz of the JIRA home directory on ocean.mbari.org which is located at /data/jira_3_12 # scp both tar.gz files to bugs.mbari.org # login to bugs.mbari.org # Unpack the home directory tar to /data/jira # Run the installer as root (this might need IS help or sudo privs). Note that we usually install the application to /opt # Run the JIRA Configuration tool to set the jira.home to the /data/jira location # Connect to JIRA_Temp database on Solstice2 (.... more to do here, see Atlassian docs) # Migrate existing configuration over to new JIRA (I need to add more here as we added Crowd). # Start JIRA # Import backed up XML # Perform post upgrades checks and tests *Need to document steps for 4.4.5->6.X*]]> 27558101 27590865 4.4: [https://confluence.atlassian.com/display/JIRA044/Migrating+JIRA+to+Another+Server] ## The JIRA configuration tool: [https://confluence.atlassian.com/display/JIRA044/Using+the+JIRA+Configuration+Tool] h5. Steps # (/) Create new VM named bugs.mbari.org in the DMZ # (/) Have Neil create database Jira_Temp on solstice2.shore.mbari.org # (/) Have Neil create database Jira on solstice2.shore.mbari.org # (/) Have Pat install Java 7 on bugs.shore.mbari.org # (/) Have Pete plumb holes through firewall so processes on bugs.mbari.org can get to Solstice2 # (/) Have Pat create DB_Collaboration account on bugs so it can run JIRA under that account and it can connect to solstice2 using that NT Domain account. # (/) Upgrade license on Atlassian site # (/) Log into bugs.shore.mbari.org # (/) Download 3.13.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 4.4.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 5.2.11 standalone Linux 64 bit tar.gz (not sure this version is necessary, but at least I have it) # (/) Unzip and untar the file to /opt # (/) Download latest JIRA (6.4.7 as of this writing). # (/) Unzip and untar it to /opt # Performed Test Upgrade ## (/) In order to export the current stuff in JIRA, I had to shut off access so people could not change the data while I was backing it up. ## (/) I ssh'd to oceana.mbari.org as root and edited the /opt/jira/conf/server.xml file and commented out the Connector section that had the port of 8010 to shut it off from the normal serving route. ## (/) I uncommented the 8082 port connector and the 8443 port connector so that I could still get to the server. ## (/) I stopped and started the JIRA server and in the log file I got a "keystore was tampered with..." which is not surprising. ## (/) I could then browser over to http://oceana.mbari.org:8082/jira ## (/) Then through the Administration console, I did an XML backup ## (/) I then created a tar of all the attachments in the /data/jira_3_12/attachments directory ## (/) I moved both the XML and tar files to the /root/jira-upgrade directory ## (/) I then reversed the changes to the server.xml file and shut down JIRA ## (/) I left it down during the next steps in case it went so well, I could just point people to the new server (yeah, right). ## (/) I then browsed to the crowd server on oceana and add a new application using: ### URL: http://bugs.mbari.org/jira3135 ### IP: 134.89.2.29 ### Name: JIRA3135 ### Password: (ask Kevin) :) ## (/) On bugs, I made a copy of the JIRA 3.13.5 download in the /opt directory and unzipped and untarred it. ## (/) In order to configure the crowd connection I did the following: ### (/) I scp'd the /opt/crowd/client/crowd-integration-client-1.6.jar file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I removed the existing 1.6.1 crowd client jar from the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I scp'd the /opt/crowd/client/conf/crowd.properties file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I scp'd the /opt/crowd/client/conf/crowd-ehcache.xml file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I edited the crowd.properties file on bugs to look like: {noformat} application.name JIRA3135 application.password (ask Kevin) application.login.url http://oceana.mbari.org:8095/crowd/console/ crowd.server.url http://oceana.mbari.org:8095/crowd/services/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 0 session.lastvalidation session.lastvalidation {noformat} ### (/) I edited the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/osuser.xml file to comment out the current authentication mechanism and then uncomment the crowd one. ## (/) I then edited the /opt/atlassian-jira-standalone-3.13.5/conf/server/xml file and configured the database connection to the Jira_Temp database on Solstice2. I looked like this: {noformat} {noformat} ## (/) Edit the /opt/atlassian/jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/entityengine.xml and changed it from 'hsql' to 'mssql' and delete the line with "PUBLIC" in it per the instructions in the comments in that file. ## (/) I edited the /etc/httpd/conf/httpd.conf file and created a proxy pass at the bottom of the file to point a normal URL to the default port 8080 for JIRA: {noformat} # Proxy Pass for JIRA ProxyPass http://bugs.mbari.org:8080 ProxyPassReverse http://bugs.mbari.org:8080 {noformat} ## (/) I restarted Apache ## (/) I scp'd the jtds driver from oceana to the /opt/atlassian-jira-standalone-3.13.5/common/lib directory (you could down from the internet) ## (/) I then went to the /opt/atlassian-jira-standalone-3.13.5/ directory and ran './bin/startup.sh'. From the log file, I could tell things were hanging. After some troubleshooting I am wondering if the local firewall is preventing the application to get access to the database on solstice2. I can telnet to port 1433, but I can't browse to the base http://bugs.mbari.org from anywhere but the local web browser. I have submitted a ticket. ## (/) I restarted the old JIRA with my hopes dashed :(. ## (/) Pat disabled the firewall on bugs.mbari.org but it still hung trying to connect to solstice2.shore.mbari.org. That is really, really perplexing. Neil mentioned that solstice2 is using Kerberos and solstice is not. Checking with the JTDS docs, version 1.3.1 of the driver added kerberos support, so I downloaded that driver and added the 'userKerberos=true' property to the URL in the server.xml file and restarted. Got an error about no credentials, so added user and password properties to the URL. Nope, no luck. Never did figure this one out, but I had Pat pull the VM inside the firewall and after some thrash it worked. Well, it sort of worked ... sigh. It turns out I had downloaded the standard version instead of the enterprise version. I need to redo this work ... grrr. ## (/) I deleted all the tables in the Jira_Temp database and removed the /data/jira3135/indexes directory (and recreated). ## (/) I downloaded the enterprise version of the 3.13.5 server. I made a copy in the /opt directory and unzipped and untarred the file. ## (/) I went back to crowd and edited the application to change the properties to: ### URL: http://bugs.shore.mbari.org:8080 ### IP: 134.89.12.31 ### Name: jira3135 ### Password: (ask Kevin) :) ## (/) I then repeated the steps above to get the server up and running with the following differences: ### The server name is now bugs.shore.mbari.org ### The paths given above are a little different in that they no longer say "standard" but say "enterprise" ### I deleted the proxy pass as it seemed to have issues before and this is only temporary anyway. ## (/) I then browsed to http://bugs.shore.mbari.org:8080 ## (/) It took me to the start up page and at the top was the option to 'import your existing data'. Seemed too good not to try. I clicked on the link. It asked me for the backup file location and the location where the indexes would be stored. ## (/) I copied the XML zip file and the attachments tar file to the /data/original directory. ## (/) I created the /data/jira3135/indexes and used those directories ... it fired off the import and I waited. ## (/) I tailed the log file to watch the import. Holy crap, it worked!!! I could log in and everything! I copied the results from the log file here for posterity sake: {noformat} 2015-07-22 20:55:45,156 http-8080-Processor22 INFO [jira.action.admin.DataImport] Running data import 2015-07-22 20:55:45,179 http-8080-Processor22 INFO [jira.action.admin.DataImport] Importing data.. 2015-07-22 20:55:45,186 http-8080-Processor22 INFO [jira.action.admin.DataImport] Start parsing XML with SAX Parser 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] XML successfully parsed 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] Removing all entries from the database. 2015-07-22 20:56:24,593 http-8080-Processor22 INFO [jira.action.admin.DataImport] All entries removed. 2015-07-22 20:56:24,594 http-8080-Processor22 INFO [jira.action.admin.DataImport] Started storing 410414 Generic Values 2015-07-22 21:01:51,967 http-8080-Processor22 INFO [jira.action.admin.DataImport] Finished storing Generic Values 2015-07-22 21:01:52,329 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:52,361 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:54,683 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLink' to module 'jira.user.format:profile-link-user-format'. 2015-07-22 21:01:54,724 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullName' to module 'jira.user.format:full-name-user-format'. 2015-07-22 21:01:54,773 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkSearcher' to module 'jira.user.format:profile-link-searcher-user-format'. 2015-07-22 21:01:54,784 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkExternal' to module 'jira.user.format:profile-link-external-user-format'. 2015-07-22 21:01:54,795 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkActionHeader' to module 'jira.user.format:profile-link-action-header-user-format'. 2015-07-22 21:01:54,807 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullProfile' to module 'jira.user.format:full-profile-user-format'. 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/comments 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/issues 2015-07-22 21:01:55,641 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/plugins 2015-07-22 21:01:55,867 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:01:55,871 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/issues does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:55,873 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/comments does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,033 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,257 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,889 http-8080-Processor22 ERROR [atlassian.jira.upgrade.ConsistencyCheckImpl] Attachments are turned on, but attachment path [/data/jira_3_12/attachments] invalid - disabling attachments 2015-07-22 21:02:13,904 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Detected that an upgrade is needed; existing data at build 299 2015-07-22 21:02:13,907 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Doing Upgrade... 2015-07-22 21:02:13,915 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value' succeeded 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 317 2015-07-22 21:02:13,944 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite filters - make each filter a favourite of its owner. 2015-07-22 21:02:17,822 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build319] Could not find author 'fpy' for filter with id '10040' 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite filters - make each filter a favourite of its owner.' succeeded 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 319 2015-07-22 21:02:17,995 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise Share Permissions. Move old shares to new shares. 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise Share Permissions. Move old shares to new shares.' succeeded 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 321 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Migrating the old JIRA UI colors to the new JIRA 3.13 colors 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build322] Custom color detected for jira.lf.menu.bgcolour : #336699 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Migrating the old JIRA UI colors to the new JIRA 3.13 colors' succeeded 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 322 2015-07-22 21:02:18,025 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite dashboards - make each dashboard a favourite of its owner. 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'cmcgann' for dashboard with id '10030' 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'fpy' for dashboard with id '10060' 2015-07-22 21:02:18,423 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'kanna' for dashboard with id '10040' 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite dashboards - make each dashboard a favourite of its owner.' succeeded 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 325 2015-07-22 21:02:18,625 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Reindexing all data in JIRA to include Favourites. 2015-07-22 21:02:18,648 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All starting... 2015-07-22 21:02:18,650 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 0% complete. Current index: Issue 2015-07-22 21:02:18,654 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:02:18,809 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 1% complete. Current index: Issue 2015-07-22 21:02:18,855 indexerPool-2-thread-10 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 2% complete. Current index: Issue 2015-07-22 21:02:18,899 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 3% complete. Current index: Issue 2015-07-22 21:02:18,945 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 4% complete. Current index: Issue 2015-07-22 21:02:19,012 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 5% complete. Current index: Issue . . . 2015-07-22 21:02:26,164 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 95% complete. Current index: Issue 2015-07-22 21:02:26,232 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 96% complete. Current index: Issue 2015-07-22 21:02:26,316 indexerPool-2-thread-9 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 97% complete. Current index: Issue 2015-07-22 21:02:26,771 indexerPool-2-thread-3 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: Issue 2015-07-22 21:02:27,261 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 8607ms. Indexer: DefaultIndexManager: paths: [/data/jira3135/indexes/issues, /data/jira3135/indexes/comments] 2015-07-22 21:02:27,263 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: SearchRequest 2015-07-22 21:02:27,268 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,293 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: SearchRequest 2015-07-22 21:02:27,308 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: PortalPage 2015-07-22 21:02:27,312 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,377 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: PortalPage 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 115ms. Indexer: SharedEntityIndexManager: paths: [/data/jira3135/indexes/entities/portalpage, /data/jira3135/indexes/entities/searchrequest] 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All complete. Total time: 8722ms. 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Reindexing all data in JIRA to include Favourites.' succeeded 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 326 2015-07-22 21:02:27,397 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade succeeded! Setting data build number to 360 2015-07-22 21:02:27,469 JiraQuartzScheduler_Worker-0 WARN [service.services.export.ExportService] Backup directory /data/jira_3_12/backup does not exist {noformat} {warning:title=Paths} It appears that the upgraded JIRA will still look for the attachments and the backup locations in the original places. So I created /data/jira_3_12/backup and untarred the original attachments to /data/jira_3_12 and then everything worked (including attachements) in the new JIRA. {warning} ## (/) I then used the upgraded JIRA to generate a new XML backup and stored it in /data/original/3.13.5 along with another tar of the files in /data/jira_3_12/attachments. ## (/) I then shutdown the JIRA server. *I should be ready to move on to version 4 upgrade WHEW* ## So, before moving on, I decided that it would be a really good idea to spin up a new Crowd instance to get rid of the :8443 in the URL and to move off of RedHat per IS requests. I have a ticket in for a new VM and a new database to try to get this going. I am waiting on that before moving on. ## (/) Pat created the VM and Neil created the database. ## (/) I logged into auth.mbari.org (name of the VM) and downloaded crowd which I unzipped to the /opt directory ## (/) I then created a /data/crowd directory and gave my account permissions on it and then edited the /opt/atlassian..../crowd-webapp/WEB-INF/classes/crowd-init.properties file to set that as the crowd home directory. ## (/) The instructions say to download the JDBC driver, but they already have JTDS 1.2.7 in the download so I did not do anything. ## (/) You have to manually connect up CrowdID to a database as they setup wizard does not currently do this. ### (/) They say to download the driver, but again 1.2.7 was there so I did nothing. ### (/) I edited the /opt/atlassian.../apache-tomcat/conf/Catalina/localhost/openidserver.xml to look like: {noformat} {noformat} ### (/) I edited the /opt/atlassian.../build.properties files to look like: {noformat} # Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See https://confluence.atlassian.com/display/CROWD/Connecting+Crowd+to+a+Database hibernate.dialect=org.hibernate.dialect.SQLServerDialect # The Hibernate transaction factory to use. See https://confluence.atlassian.com/display/CROWD/Configuring+Crowd hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory # The http port you wish to run crowd from, ie: http://localhost:8095/crowd crowd.tomcat.connector.port=8095 # Tomcat requires a unique port for shutdown crowd.tomcat.shutdown.port=8020 # Crowd context root crowd.url=http://localhost:8095/crowd # Demo context root demo.url=http://localhost:8095/demo # OpenID server context root openidserver.url=http://localhost:8095/openidserver {noformat} ### (/) I then ran the build.sh script in the root of /opt/atlassian... ## (/) I fired up crowd using the /opt/atlassian.../start_crowd.sh script ## (/) I then went to http://auth.mbari.org:8095/crowd to kick off the start up wizard ## (/) I grabbed a new eval license from my account on atlassian and pasted into the license page. ## (/) I selected "New install" on the next page. ## (/) I configured the JDBC connection using this connection URL {noformat} jdbc:jtds:sqlserver://dione.mbari.org:51001:Crowd;domain=SHORE;useNTLMv2=TRUE {noformat} ## (/) I fired up crowd and then went to the http://localhost:8095 URL to start the configuration. I input the DB connection parameters and it created the DB and took off just fine. I really wanted to run the application on port 80 and 443 as normal applications do so I first tried to change the port numbers that the application ran on. That did not work as those are privileged ports and cannot be controller unless you are root. I did not want to do that, so I will have to do a proxy pass. I had to start up the httpd services (I will need to configure as a service) and then created a new file in /etc/httpd/conf.d called crowd.conf that contained the following: {noformat} # This is the configuration for the proxy pass for the crowd server ProxyRequests Off ProxyPreserveHost On Require all granted ProxyPass /crowd http://auth.mbari.org:8095/crowd ProxyPassReverse /crowd http://auth.mbari.org:8095/crowd Require all granted ProxyPass /openidserver http://auth.mbari.org:8095/openidserver ProxyPassReverse /openidserver http://auth.mbari.org:8095/openidserver Require all granted {noformat} ## (/) This worked for the basic HTTP so I will have to get it working with SSL. ## (/) Something with the openidserver is not working correctly and I suspect I have not done the openidserver install completely or correctly. I read the directions on configuring crowdid and it's connection to the database and restarted the crowd server. That worked, not I have both working of straight HTTP, now I need to get SSL going. ## (/) I originally started to configure SSL for the Tomcat server for Crowd, but then realized, since I am putting the Apache proxy in front of Tomcat, I should be able to just set up SSL on Apache HTTP and leave Tomcat alone (i.e. traffic between Apache HTTP and Tomcat does not need to be encrypted). # Schedule upgrade date and send all hands several days in advance. # When the day arrives, send all hands announcing JIRA outage. # From the Administrator's page in our existing JIRA, perform a 'Backup Data to XML'. # Login to oceana.mbari.org as root. # Shutdown JIRA # Create a tar.gz of the /opt/atlassian-jira-enterprise-3.12.1-standalone directory # Clean up the /data/jira_3_12/backups directory by deleting all but maybe the last 5 backups. # Create a tar.gz of the JIRA home directory on ocean.mbari.org which is located at /data/jira_3_12 # scp both tar.gz files to bugs.mbari.org # login to bugs.mbari.org # Unpack the home directory tar to /data/jira # Run the installer as root (this might need IS help or sudo privs). Note that we usually install the application to /opt # Run the JIRA Configuration tool to set the jira.home to the /data/jira location # Connect to JIRA_Temp database on Solstice2 (.... more to do here, see Atlassian docs) # Migrate existing configuration over to new JIRA (I need to add more here as we added Crowd). # Start JIRA # Import backed up XML # Perform post upgrades checks and tests *Need to document steps for 4.4.5->6.X*]]> 27558100 13959339 13926577 27590859 4.4: [https://confluence.atlassian.com/display/JIRA044/Migrating+JIRA+to+Another+Server] ## The JIRA configuration tool: [https://confluence.atlassian.com/display/JIRA044/Using+the+JIRA+Configuration+Tool] h5. Steps # (/) Create new VM named bugs.mbari.org in the DMZ # (/) Have Neil create database Jira_Temp on solstice2.shore.mbari.org # (/) Have Neil create database Jira on solstice2.shore.mbari.org # (/) Have Pat install Java 7 on bugs.shore.mbari.org # (/) Have Pete plumb holes through firewall so processes on bugs.mbari.org can get to Solstice2 # (/) Have Pat create DB_Collaboration account on bugs so it can run JIRA under that account and it can connect to solstice2 using that NT Domain account. # (/) Upgrade license on Atlassian site # (/) Log into bugs.shore.mbari.org # (/) Download 3.13.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 4.4.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 5.2.11 standalone Linux 64 bit tar.gz (not sure this version is necessary, but at least I have it) # (/) Unzip and untar the file to /opt # (/) Download latest JIRA (6.4.7 as of this writing). # (/) Unzip and untar it to /opt # Performed Test Upgrade ## (/) In order to export the current stuff in JIRA, I had to shut off access so people could not change the data while I was backing it up. ## (/) I ssh'd to oceana.mbari.org as root and edited the /opt/jira/conf/server.xml file and commented out the Connector section that had the port of 8010 to shut it off from the normal serving route. ## (/) I uncommented the 8082 port connector and the 8443 port connector so that I could still get to the server. ## (/) I stopped and started the JIRA server and in the log file I got a "keystore was tampered with..." which is not surprising. ## (/) I could then browser over to http://oceana.mbari.org:8082/jira ## (/) Then through the Administration console, I did an XML backup ## (/) I then created a tar of all the attachments in the /data/jira_3_12/attachments directory ## (/) I moved both the XML and tar files to the /root/jira-upgrade directory ## (/) I then reversed the changes to the server.xml file and shut down JIRA ## (/) I left it down during the next steps in case it went so well, I could just point people to the new server (yeah, right). ## (/) I then browsed to the crowd server on oceana and add a new application using: ### URL: http://bugs.mbari.org/jira3135 ### IP: 134.89.2.29 ### Name: JIRA3135 ### Password: (ask Kevin) :) ## (/) On bugs, I made a copy of the JIRA 3.13.5 download in the /opt directory and unzipped and untarred it. ## (/) In order to configure the crowd connection I did the following: ### (/) I scp'd the /opt/crowd/client/crowd-integration-client-1.6.jar file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I removed the existing 1.6.1 crowd client jar from the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I scp'd the /opt/crowd/client/conf/crowd.properties file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I scp'd the /opt/crowd/client/conf/crowd-ehcache.xml file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I edited the crowd.properties file on bugs to look like: {noformat} application.name JIRA3135 application.password (ask Kevin) application.login.url http://oceana.mbari.org:8095/crowd/console/ crowd.server.url http://oceana.mbari.org:8095/crowd/services/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 0 session.lastvalidation session.lastvalidation {noformat} ### (/) I edited the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/osuser.xml file to comment out the current authentication mechanism and then uncomment the crowd one. ## (/) I then edited the /opt/atlassian-jira-standalone-3.13.5/conf/server/xml file and configured the database connection to the Jira_Temp database on Solstice2. I looked like this: {noformat} {noformat} ## (/) Edit the /opt/atlassian/jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/entityengine.xml and changed it from 'hsql' to 'mssql' and delete the line with "PUBLIC" in it per the instructions in the comments in that file. ## (/) I edited the /etc/httpd/conf/httpd.conf file and created a proxy pass at the bottom of the file to point a normal URL to the default port 8080 for JIRA: {noformat} # Proxy Pass for JIRA ProxyPass http://bugs.mbari.org:8080 ProxyPassReverse http://bugs.mbari.org:8080 {noformat} ## (/) I restarted Apache ## (/) I scp'd the jtds driver from oceana to the /opt/atlassian-jira-standalone-3.13.5/common/lib directory (you could down from the internet) ## (/) I then went to the /opt/atlassian-jira-standalone-3.13.5/ directory and ran './bin/startup.sh'. From the log file, I could tell things were hanging. After some troubleshooting I am wondering if the local firewall is preventing the application to get access to the database on solstice2. I can telnet to port 1433, but I can't browse to the base http://bugs.mbari.org from anywhere but the local web browser. I have submitted a ticket. ## (/) I restarted the old JIRA with my hopes dashed :(. ## (/) Pat disabled the firewall on bugs.mbari.org but it still hung trying to connect to solstice2.shore.mbari.org. That is really, really perplexing. Neil mentioned that solstice2 is using Kerberos and solstice is not. Checking with the JTDS docs, version 1.3.1 of the driver added kerberos support, so I downloaded that driver and added the 'userKerberos=true' property to the URL in the server.xml file and restarted. Got an error about no credentials, so added user and password properties to the URL. Nope, no luck. Never did figure this one out, but I had Pat pull the VM inside the firewall and after some thrash it worked. Well, it sort of worked ... sigh. It turns out I had downloaded the standard version instead of the enterprise version. I need to redo this work ... grrr. ## (/) I deleted all the tables in the Jira_Temp database and removed the /data/jira3135/indexes directory (and recreated). ## (/) I downloaded the enterprise version of the 3.13.5 server. I made a copy in the /opt directory and unzipped and untarred the file. ## (/) I went back to crowd and edited the application to change the properties to: ### URL: http://bugs.shore.mbari.org:8080 ### IP: 134.89.12.31 ### Name: jira3135 ### Password: (ask Kevin) :) ## (/) I then repeated the steps above to get the server up and running with the following differences: ### The server name is now bugs.shore.mbari.org ### The paths given above are a little different in that they no longer say "standard" but say "enterprise" ### I deleted the proxy pass as it seemed to have issues before and this is only temporary anyway. ## (/) I then browsed to http://bugs.shore.mbari.org:8080 ## (/) It took me to the start up page and at the top was the option to 'import your existing data'. Seemed too good not to try. I clicked on the link. It asked me for the backup file location and the location where the indexes would be stored. ## (/) I copied the XML zip file and the attachments tar file to the /data/original directory. ## (/) I created the /data/jira3135/indexes and used those directories ... it fired off the import and I waited. ## (/) I tailed the log file to watch the import. Holy crap, it worked!!! I could log in and everything! I copied the results from the log file here for posterity sake: {noformat} 2015-07-22 20:55:45,156 http-8080-Processor22 INFO [jira.action.admin.DataImport] Running data import 2015-07-22 20:55:45,179 http-8080-Processor22 INFO [jira.action.admin.DataImport] Importing data.. 2015-07-22 20:55:45,186 http-8080-Processor22 INFO [jira.action.admin.DataImport] Start parsing XML with SAX Parser 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] XML successfully parsed 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] Removing all entries from the database. 2015-07-22 20:56:24,593 http-8080-Processor22 INFO [jira.action.admin.DataImport] All entries removed. 2015-07-22 20:56:24,594 http-8080-Processor22 INFO [jira.action.admin.DataImport] Started storing 410414 Generic Values 2015-07-22 21:01:51,967 http-8080-Processor22 INFO [jira.action.admin.DataImport] Finished storing Generic Values 2015-07-22 21:01:52,329 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:52,361 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:54,683 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLink' to module 'jira.user.format:profile-link-user-format'. 2015-07-22 21:01:54,724 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullName' to module 'jira.user.format:full-name-user-format'. 2015-07-22 21:01:54,773 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkSearcher' to module 'jira.user.format:profile-link-searcher-user-format'. 2015-07-22 21:01:54,784 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkExternal' to module 'jira.user.format:profile-link-external-user-format'. 2015-07-22 21:01:54,795 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkActionHeader' to module 'jira.user.format:profile-link-action-header-user-format'. 2015-07-22 21:01:54,807 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullProfile' to module 'jira.user.format:full-profile-user-format'. 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/comments 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/issues 2015-07-22 21:01:55,641 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/plugins 2015-07-22 21:01:55,867 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:01:55,871 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/issues does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:55,873 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/comments does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,033 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,257 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,889 http-8080-Processor22 ERROR [atlassian.jira.upgrade.ConsistencyCheckImpl] Attachments are turned on, but attachment path [/data/jira_3_12/attachments] invalid - disabling attachments 2015-07-22 21:02:13,904 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Detected that an upgrade is needed; existing data at build 299 2015-07-22 21:02:13,907 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Doing Upgrade... 2015-07-22 21:02:13,915 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value' succeeded 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 317 2015-07-22 21:02:13,944 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite filters - make each filter a favourite of its owner. 2015-07-22 21:02:17,822 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build319] Could not find author 'fpy' for filter with id '10040' 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite filters - make each filter a favourite of its owner.' succeeded 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 319 2015-07-22 21:02:17,995 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise Share Permissions. Move old shares to new shares. 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise Share Permissions. Move old shares to new shares.' succeeded 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 321 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Migrating the old JIRA UI colors to the new JIRA 3.13 colors 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build322] Custom color detected for jira.lf.menu.bgcolour : #336699 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Migrating the old JIRA UI colors to the new JIRA 3.13 colors' succeeded 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 322 2015-07-22 21:02:18,025 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite dashboards - make each dashboard a favourite of its owner. 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'cmcgann' for dashboard with id '10030' 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'fpy' for dashboard with id '10060' 2015-07-22 21:02:18,423 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'kanna' for dashboard with id '10040' 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite dashboards - make each dashboard a favourite of its owner.' succeeded 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 325 2015-07-22 21:02:18,625 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Reindexing all data in JIRA to include Favourites. 2015-07-22 21:02:18,648 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All starting... 2015-07-22 21:02:18,650 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 0% complete. Current index: Issue 2015-07-22 21:02:18,654 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:02:18,809 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 1% complete. Current index: Issue 2015-07-22 21:02:18,855 indexerPool-2-thread-10 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 2% complete. Current index: Issue 2015-07-22 21:02:18,899 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 3% complete. Current index: Issue 2015-07-22 21:02:18,945 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 4% complete. Current index: Issue 2015-07-22 21:02:19,012 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 5% complete. Current index: Issue . . . 2015-07-22 21:02:26,164 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 95% complete. Current index: Issue 2015-07-22 21:02:26,232 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 96% complete. Current index: Issue 2015-07-22 21:02:26,316 indexerPool-2-thread-9 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 97% complete. Current index: Issue 2015-07-22 21:02:26,771 indexerPool-2-thread-3 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: Issue 2015-07-22 21:02:27,261 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 8607ms. Indexer: DefaultIndexManager: paths: [/data/jira3135/indexes/issues, /data/jira3135/indexes/comments] 2015-07-22 21:02:27,263 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: SearchRequest 2015-07-22 21:02:27,268 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,293 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: SearchRequest 2015-07-22 21:02:27,308 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: PortalPage 2015-07-22 21:02:27,312 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,377 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: PortalPage 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 115ms. Indexer: SharedEntityIndexManager: paths: [/data/jira3135/indexes/entities/portalpage, /data/jira3135/indexes/entities/searchrequest] 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All complete. Total time: 8722ms. 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Reindexing all data in JIRA to include Favourites.' succeeded 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 326 2015-07-22 21:02:27,397 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade succeeded! Setting data build number to 360 2015-07-22 21:02:27,469 JiraQuartzScheduler_Worker-0 WARN [service.services.export.ExportService] Backup directory /data/jira_3_12/backup does not exist {noformat} {warning:title=Paths} It appears that the upgraded JIRA will still look for the attachments and the backup locations in the original places. So I created /data/jira_3_12/backup and untarred the original attachments to /data/jira_3_12 and then everything worked (including attachements) in the new JIRA. {warning} ## (/) I then used the upgraded JIRA to generate a new XML backup and stored it in /data/original/3.13.5 along with another tar of the files in /data/jira_3_12/attachments. ## (/) I then shutdown the JIRA server. *I should be ready to move on to version 4 upgrade WHEW* ## So, before moving on, I decided that it would be a really good idea to spin up a new Crowd instance to get rid of the :8443 in the URL and to move off of RedHat per IS requests. I have a ticket in for a new VM and a new database to try to get this going. I am waiting on that before moving on. ## (/) Pat created the VM and Neil created the database. ## (/) I logged into auth.mbari.org (name of the VM) and downloaded crowd which I unzipped to the /opt directory ## (/) I then created a /data/crowd directory and gave my account permissions on it and then edited the /opt/atlassian..../crowd-webapp/WEB-INF/classes/crowd-init.properties file to set that as the crowd home directory. ## (/) The instructions say to download the JDBC driver, but they already have JTDS 1.2.7 in the download so I did not do anything. ## (/) You have to manually connect up CrowdID to a database as they setup wizard does not currently do this. ### (/) They say to download the driver, but again 1.2.7 was there so I did nothing. ### (/) I edited the /opt/atlassian.../apache-tomcat/conf/Catalina/localhost/openidserver.xml to look like: {noformat} {noformat} ## (/) I fired up crowd and then went to the http://localhost:8095 URL to start the configuration. I input the DB connection parameters and it created the DB and took off just fine. I really wanted to run the application on port 80 and 443 as normal applications do so I first tried to change the port numbers that the application ran on. That did not work as those are privileged ports and cannot be controller unless you are root. I did not want to do that, so I will have to do a proxy pass. I had to start up the httpd services (I will need to configure as a service) and then created a new file in /etc/httpd/conf.d called crowd.conf that contained the following: {noformat} # This is the configuration for the proxy pass for the crowd server ProxyRequests Off ProxyPreserveHost On Require all granted ProxyPass /crowd http://auth.mbari.org:8095/crowd ProxyPassReverse /crowd http://auth.mbari.org:8095/crowd Require all granted ProxyPass /openidserver http://auth.mbari.org:8095/openidserver ProxyPassReverse /openidserver http://auth.mbari.org:8095/openidserver Require all granted {noformat} ## (/) This worked for the basic HTTP so I will have to get it working with SSL. ## (/) Something with the openidserver is not working correctly and I suspect I have not done the openidserver install completely or correctly. I read the directions on configuring crowdid and it's connection to the database and restarted the crowd server. That worked, not I have both working of straight HTTP, now I need to get SSL going. ## (/) I originally started to configure SSL for the Tomcat server for Crowd, but then realized, since I am putting the Apache proxy in front of Tomcat, I should be able to just set up SSL on Apache HTTP and leave Tomcat alone (i.e. traffic between Apache HTTP and Tomcat does not need to be encrypted). # Schedule upgrade date and send all hands several days in advance. # When the day arrives, send all hands announcing JIRA outage. # From the Administrator's page in our existing JIRA, perform a 'Backup Data to XML'. # Login to oceana.mbari.org as root. # Shutdown JIRA # Create a tar.gz of the /opt/atlassian-jira-enterprise-3.12.1-standalone directory # Clean up the /data/jira_3_12/backups directory by deleting all but maybe the last 5 backups. # Create a tar.gz of the JIRA home directory on ocean.mbari.org which is located at /data/jira_3_12 # scp both tar.gz files to bugs.mbari.org # login to bugs.mbari.org # Unpack the home directory tar to /data/jira # Run the installer as root (this might need IS help or sudo privs). Note that we usually install the application to /opt # Run the JIRA Configuration tool to set the jira.home to the /data/jira location # Connect to JIRA_Temp database on Solstice2 (.... more to do here, see Atlassian docs) # Migrate existing configuration over to new JIRA (I need to add more here as we added Crowd). # Start JIRA # Import backed up XML # Perform post upgrades checks and tests *Need to document steps for 4.4.5->6.X*]]> 27558094 19073791 19041100 13959342 13926580 27590862 4.4: [https://confluence.atlassian.com/display/JIRA044/Migrating+JIRA+to+Another+Server] ## The JIRA configuration tool: [https://confluence.atlassian.com/display/JIRA044/Using+the+JIRA+Configuration+Tool] h5. Steps # (/) Create new VM named bugs.mbari.org in the DMZ # (/) Have Neil create database Jira_Temp on solstice2.shore.mbari.org # (/) Have Neil create database Jira on solstice2.shore.mbari.org # (/) Have Pat install Java 7 on bugs.shore.mbari.org # (/) Have Pete plumb holes through firewall so processes on bugs.mbari.org can get to Solstice2 # (/) Have Pat create DB_Collaboration account on bugs so it can run JIRA under that account and it can connect to solstice2 using that NT Domain account. # (/) Upgrade license on Atlassian site # (/) Log into bugs.shore.mbari.org # (/) Download 3.13.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 4.4.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 5.2.11 standalone Linux 64 bit tar.gz (not sure this version is necessary, but at least I have it) # (/) Unzip and untar the file to /opt # (/) Download latest JIRA (6.4.7 as of this writing). # (/) Unzip and untar it to /opt # Performed Test Upgrade ## (/) In order to export the current stuff in JIRA, I had to shut off access so people could not change the data while I was backing it up. ## (/) I ssh'd to oceana.mbari.org as root and edited the /opt/jira/conf/server.xml file and commented out the Connector section that had the port of 8010 to shut it off from the normal serving route. ## (/) I uncommented the 8082 port connector and the 8443 port connector so that I could still get to the server. ## (/) I stopped and started the JIRA server and in the log file I got a "keystore was tampered with..." which is not surprising. ## (/) I could then browser over to http://oceana.mbari.org:8082/jira ## (/) Then through the Administration console, I did an XML backup ## (/) I then created a tar of all the attachments in the /data/jira_3_12/attachments directory ## (/) I moved both the XML and tar files to the /root/jira-upgrade directory ## (/) I then reversed the changes to the server.xml file and shut down JIRA ## (/) I left it down during the next steps in case it went so well, I could just point people to the new server (yeah, right). ## (/) I then browsed to the crowd server on oceana and add a new application using: ### URL: http://bugs.mbari.org/jira3135 ### IP: 134.89.2.29 ### Name: JIRA3135 ### Password: (ask Kevin) :) ## (/) On bugs, I made a copy of the JIRA 3.13.5 download in the /opt directory and unzipped and untarred it. ## (/) In order to configure the crowd connection I did the following: ### (/) I scp'd the /opt/crowd/client/crowd-integration-client-1.6.jar file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I removed the existing 1.6.1 crowd client jar from the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I scp'd the /opt/crowd/client/conf/crowd.properties file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I scp'd the /opt/crowd/client/conf/crowd-ehcache.xml file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I edited the crowd.properties file on bugs to look like: {noformat} application.name JIRA3135 application.password (ask Kevin) application.login.url http://oceana.mbari.org:8095/crowd/console/ crowd.server.url http://oceana.mbari.org:8095/crowd/services/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 0 session.lastvalidation session.lastvalidation {noformat} ### (/) I edited the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/osuser.xml file to comment out the current authentication mechanism and then uncomment the crowd one. ## (/) I then edited the /opt/atlassian-jira-standalone-3.13.5/conf/server/xml file and configured the database connection to the Jira_Temp database on Solstice2. I looked like this: {noformat} {noformat} ## (/) Edit the /opt/atlassian/jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/entityengine.xml and changed it from 'hsql' to 'mssql' and delete the line with "PUBLIC" in it per the instructions in the comments in that file. ## (/) I edited the /etc/httpd/conf/httpd.conf file and created a proxy pass at the bottom of the file to point a normal URL to the default port 8080 for JIRA: {noformat} # Proxy Pass for JIRA ProxyPass http://bugs.mbari.org:8080 ProxyPassReverse http://bugs.mbari.org:8080 {noformat} ## (/) I restarted Apache ## (/) I scp'd the jtds driver from oceana to the /opt/atlassian-jira-standalone-3.13.5/common/lib directory (you could down from the internet) ## (/) I then went to the /opt/atlassian-jira-standalone-3.13.5/ directory and ran './bin/startup.sh'. From the log file, I could tell things were hanging. After some troubleshooting I am wondering if the local firewall is preventing the application to get access to the database on solstice2. I can telnet to port 1433, but I can't browse to the base http://bugs.mbari.org from anywhere but the local web browser. I have submitted a ticket. ## (/) I restarted the old JIRA with my hopes dashed :(. ## (/) Pat disabled the firewall on bugs.mbari.org but it still hung trying to connect to solstice2.shore.mbari.org. That is really, really perplexing. Neil mentioned that solstice2 is using Kerberos and solstice is not. Checking with the JTDS docs, version 1.3.1 of the driver added kerberos support, so I downloaded that driver and added the 'userKerberos=true' property to the URL in the server.xml file and restarted. Got an error about no credentials, so added user and password properties to the URL. Nope, no luck. Never did figure this one out, but I had Pat pull the VM inside the firewall and after some thrash it worked. Well, it sort of worked ... sigh. It turns out I had downloaded the standard version instead of the enterprise version. I need to redo this work ... grrr. ## (/) I deleted all the tables in the Jira_Temp database and removed the /data/jira3135/indexes directory (and recreated). ## (/) I downloaded the enterprise version of the 3.13.5 server. I made a copy in the /opt directory and unzipped and untarred the file. ## (/) I went back to crowd and edited the application to change the properties to: ### URL: http://bugs.shore.mbari.org:8080 ### IP: 134.89.12.31 ### Name: jira3135 ### Password: (ask Kevin) :) ## (/) I then repeated the steps above to get the server up and running with the following differences: ### The server name is now bugs.shore.mbari.org ### The paths given above are a little different in that they no longer say "standard" but say "enterprise" ### I deleted the proxy pass as it seemed to have issues before and this is only temporary anyway. ## (/) I then browsed to http://bugs.shore.mbari.org:8080 ## (/) It took me to the start up page and at the top was the option to 'import your existing data'. Seemed too good not to try. I clicked on the link. It asked me for the backup file location and the location where the indexes would be stored. ## (/) I copied the XML zip file and the attachments tar file to the /data/original directory. ## (/) I created the /data/jira3135/indexes and used those directories ... it fired off the import and I waited. ## (/) I tailed the log file to watch the import. Holy crap, it worked!!! I could log in and everything! I copied the results from the log file here for posterity sake: {noformat} 2015-07-22 20:55:45,156 http-8080-Processor22 INFO [jira.action.admin.DataImport] Running data import 2015-07-22 20:55:45,179 http-8080-Processor22 INFO [jira.action.admin.DataImport] Importing data.. 2015-07-22 20:55:45,186 http-8080-Processor22 INFO [jira.action.admin.DataImport] Start parsing XML with SAX Parser 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] XML successfully parsed 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] Removing all entries from the database. 2015-07-22 20:56:24,593 http-8080-Processor22 INFO [jira.action.admin.DataImport] All entries removed. 2015-07-22 20:56:24,594 http-8080-Processor22 INFO [jira.action.admin.DataImport] Started storing 410414 Generic Values 2015-07-22 21:01:51,967 http-8080-Processor22 INFO [jira.action.admin.DataImport] Finished storing Generic Values 2015-07-22 21:01:52,329 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:52,361 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:54,683 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLink' to module 'jira.user.format:profile-link-user-format'. 2015-07-22 21:01:54,724 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullName' to module 'jira.user.format:full-name-user-format'. 2015-07-22 21:01:54,773 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkSearcher' to module 'jira.user.format:profile-link-searcher-user-format'. 2015-07-22 21:01:54,784 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkExternal' to module 'jira.user.format:profile-link-external-user-format'. 2015-07-22 21:01:54,795 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkActionHeader' to module 'jira.user.format:profile-link-action-header-user-format'. 2015-07-22 21:01:54,807 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullProfile' to module 'jira.user.format:full-profile-user-format'. 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/comments 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/issues 2015-07-22 21:01:55,641 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/plugins 2015-07-22 21:01:55,867 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:01:55,871 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/issues does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:55,873 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/comments does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,033 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,257 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,889 http-8080-Processor22 ERROR [atlassian.jira.upgrade.ConsistencyCheckImpl] Attachments are turned on, but attachment path [/data/jira_3_12/attachments] invalid - disabling attachments 2015-07-22 21:02:13,904 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Detected that an upgrade is needed; existing data at build 299 2015-07-22 21:02:13,907 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Doing Upgrade... 2015-07-22 21:02:13,915 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value' succeeded 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 317 2015-07-22 21:02:13,944 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite filters - make each filter a favourite of its owner. 2015-07-22 21:02:17,822 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build319] Could not find author 'fpy' for filter with id '10040' 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite filters - make each filter a favourite of its owner.' succeeded 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 319 2015-07-22 21:02:17,995 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise Share Permissions. Move old shares to new shares. 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise Share Permissions. Move old shares to new shares.' succeeded 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 321 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Migrating the old JIRA UI colors to the new JIRA 3.13 colors 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build322] Custom color detected for jira.lf.menu.bgcolour : #336699 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Migrating the old JIRA UI colors to the new JIRA 3.13 colors' succeeded 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 322 2015-07-22 21:02:18,025 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite dashboards - make each dashboard a favourite of its owner. 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'cmcgann' for dashboard with id '10030' 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'fpy' for dashboard with id '10060' 2015-07-22 21:02:18,423 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'kanna' for dashboard with id '10040' 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite dashboards - make each dashboard a favourite of its owner.' succeeded 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 325 2015-07-22 21:02:18,625 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Reindexing all data in JIRA to include Favourites. 2015-07-22 21:02:18,648 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All starting... 2015-07-22 21:02:18,650 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 0% complete. Current index: Issue 2015-07-22 21:02:18,654 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:02:18,809 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 1% complete. Current index: Issue 2015-07-22 21:02:18,855 indexerPool-2-thread-10 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 2% complete. Current index: Issue 2015-07-22 21:02:18,899 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 3% complete. Current index: Issue 2015-07-22 21:02:18,945 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 4% complete. Current index: Issue 2015-07-22 21:02:19,012 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 5% complete. Current index: Issue . . . 2015-07-22 21:02:26,164 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 95% complete. Current index: Issue 2015-07-22 21:02:26,232 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 96% complete. Current index: Issue 2015-07-22 21:02:26,316 indexerPool-2-thread-9 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 97% complete. Current index: Issue 2015-07-22 21:02:26,771 indexerPool-2-thread-3 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: Issue 2015-07-22 21:02:27,261 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 8607ms. Indexer: DefaultIndexManager: paths: [/data/jira3135/indexes/issues, /data/jira3135/indexes/comments] 2015-07-22 21:02:27,263 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: SearchRequest 2015-07-22 21:02:27,268 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,293 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: SearchRequest 2015-07-22 21:02:27,308 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: PortalPage 2015-07-22 21:02:27,312 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,377 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: PortalPage 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 115ms. Indexer: SharedEntityIndexManager: paths: [/data/jira3135/indexes/entities/portalpage, /data/jira3135/indexes/entities/searchrequest] 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All complete. Total time: 8722ms. 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Reindexing all data in JIRA to include Favourites.' succeeded 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 326 2015-07-22 21:02:27,397 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade succeeded! Setting data build number to 360 2015-07-22 21:02:27,469 JiraQuartzScheduler_Worker-0 WARN [service.services.export.ExportService] Backup directory /data/jira_3_12/backup does not exist {noformat} {warning:title=Paths} It appears that the upgraded JIRA will still look for the attachments and the backup locations in the original places. So I created /data/jira_3_12/backup and untarred the original attachments to /data/jira_3_12 and then everything worked (including attachements) in the new JIRA. {warning} ## (/) I then used the upgraded JIRA to generate a new XML backup and stored it in /data/original/3.13.5 along with another tar of the files in /data/jira_3_12/attachments. ## (/) I then shutdown the JIRA server. *I should be ready to move on to version 4 upgrade WHEW* ## So, before moving on, I decided that it would be a really good idea to spin up a new Crowd instance to get rid of the :8443 in the URL and to move off of RedHat per IS requests. I have a ticket in for a new VM and a new database to try to get this going. I am waiting on that before moving on. ## (/) Pat created the VM and Neil created the database. ## (/) I logged into auth.mbari.org (name of the VM) and downloaded crowd which I unzipped to the /opt directory ## (/) I then created a /data/crowd directory and gave my account permissions on it and then edited the /opt/atlassian..../crowd-webapp/WEB-INF/classes/crowd-init.properties file to set that as the crowd home directory. ## (/) The instructions say to download the JDBC driver, but they already have JTDS 1.2.7 in the download so I did not do anything. ## (/) You have to manually connect up CrowdID to a database as they setup wizard does not currently do this. ### (/) They say to download the driver, but again 1.2.7 was there so I did nothing. ### (/) I edited the /opt/atlassian.../apache-tomcat/conf/Catalina/localhost/openidserver.xml to look like: {noformat} {noformat} ### (/) I edited the /opt/atlassian.../build.properties files to look like: {noformat} # Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See https://confluence.atlassian.com/display/CROWD/Connecting+Crowd+to+a+Database hibernate.dialect=org.hibernate.dialect.SQLServerDialect # The Hibernate transaction factory to use. See https://confluence.atlassian.com/display/CROWD/Configuring+Crowd hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory # The http port you wish to run crowd from, ie: http://localhost:8095/crowd crowd.tomcat.connector.port=8095 # Tomcat requires a unique port for shutdown crowd.tomcat.shutdown.port=8020 # Crowd context root crowd.url=http://localhost:8095/crowd # Demo context root demo.url=http://localhost:8095/demo # OpenID server context root openidserver.url=http://localhost:8095/openidserver {noformat} ### (/) I then ran the build.sh script in the root of /opt/atlassian... ## (/) I fired up crowd and then went to the http://localhost:8095 URL to start the configuration. I input the DB connection parameters and it created the DB and took off just fine. I really wanted to run the application on port 80 and 443 as normal applications do so I first tried to change the port numbers that the application ran on. That did not work as those are privileged ports and cannot be controller unless you are root. I did not want to do that, so I will have to do a proxy pass. I had to start up the httpd services (I will need to configure as a service) and then created a new file in /etc/httpd/conf.d called crowd.conf that contained the following: {noformat} # This is the configuration for the proxy pass for the crowd server ProxyRequests Off ProxyPreserveHost On Require all granted ProxyPass /crowd http://auth.mbari.org:8095/crowd ProxyPassReverse /crowd http://auth.mbari.org:8095/crowd Require all granted ProxyPass /openidserver http://auth.mbari.org:8095/openidserver ProxyPassReverse /openidserver http://auth.mbari.org:8095/openidserver Require all granted {noformat} ## (/) This worked for the basic HTTP so I will have to get it working with SSL. ## (/) Something with the openidserver is not working correctly and I suspect I have not done the openidserver install completely or correctly. I read the directions on configuring crowdid and it's connection to the database and restarted the crowd server. That worked, not I have both working of straight HTTP, now I need to get SSL going. ## (/) I originally started to configure SSL for the Tomcat server for Crowd, but then realized, since I am putting the Apache proxy in front of Tomcat, I should be able to just set up SSL on Apache HTTP and leave Tomcat alone (i.e. traffic between Apache HTTP and Tomcat does not need to be encrypted). # Schedule upgrade date and send all hands several days in advance. # When the day arrives, send all hands announcing JIRA outage. # From the Administrator's page in our existing JIRA, perform a 'Backup Data to XML'. # Login to oceana.mbari.org as root. # Shutdown JIRA # Create a tar.gz of the /opt/atlassian-jira-enterprise-3.12.1-standalone directory # Clean up the /data/jira_3_12/backups directory by deleting all but maybe the last 5 backups. # Create a tar.gz of the JIRA home directory on ocean.mbari.org which is located at /data/jira_3_12 # scp both tar.gz files to bugs.mbari.org # login to bugs.mbari.org # Unpack the home directory tar to /data/jira # Run the installer as root (this might need IS help or sudo privs). Note that we usually install the application to /opt # Run the JIRA Configuration tool to set the jira.home to the /data/jira location # Connect to JIRA_Temp database on Solstice2 (.... more to do here, see Atlassian docs) # Migrate existing configuration over to new JIRA (I need to add more here as we added Crowd). # Start JIRA # Import backed up XML # Perform post upgrades checks and tests *Need to document steps for 4.4.5->6.X*]]> 27558097 13959341 13926579 13959336 13926574 27590856 4.4: [https://confluence.atlassian.com/display/JIRA044/Migrating+JIRA+to+Another+Server] ## The JIRA configuration tool: [https://confluence.atlassian.com/display/JIRA044/Using+the+JIRA+Configuration+Tool] h5. Steps # (/) Create new VM named bugs.mbari.org in the DMZ # (/) Have Neil create database Jira_Temp on solstice2.shore.mbari.org # (/) Have Neil create database Jira on solstice2.shore.mbari.org # (/) Have Pat install Java 7 on bugs.shore.mbari.org # (/) Have Pete plumb holes through firewall so processes on bugs.mbari.org can get to Solstice2 # (/) Have Pat create DB_Collaboration account on bugs so it can run JIRA under that account and it can connect to solstice2 using that NT Domain account. # (/) Upgrade license on Atlassian site # (/) Log into bugs.shore.mbari.org # (/) Download 3.13.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 4.4.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 5.2.11 standalone Linux 64 bit tar.gz (not sure this version is necessary, but at least I have it) # (/) Unzip and untar the file to /opt # (/) Download latest JIRA (6.4.7 as of this writing). # (/) Unzip and untar it to /opt # Performed Test Upgrade ## (/) In order to export the current stuff in JIRA, I had to shut off access so people could not change the data while I was backing it up. ## (/) I ssh'd to oceana.mbari.org as root and edited the /opt/jira/conf/server.xml file and commented out the Connector section that had the port of 8010 to shut it off from the normal serving route. ## (/) I uncommented the 8082 port connector and the 8443 port connector so that I could still get to the server. ## (/) I stopped and started the JIRA server and in the log file I got a "keystore was tampered with..." which is not surprising. ## (/) I could then browser over to http://oceana.mbari.org:8082/jira ## (/) Then through the Administration console, I did an XML backup ## (/) I then created a tar of all the attachments in the /data/jira_3_12/attachments directory ## (/) I moved both the XML and tar files to the /root/jira-upgrade directory ## (/) I then reversed the changes to the server.xml file and shut down JIRA ## (/) I left it down during the next steps in case it went so well, I could just point people to the new server (yeah, right). ## (/) I then browsed to the crowd server on oceana and add a new application using: ### URL: http://bugs.mbari.org/jira3135 ### IP: 134.89.2.29 ### Name: JIRA3135 ### Password: (ask Kevin) :) ## (/) On bugs, I made a copy of the JIRA 3.13.5 download in the /opt directory and unzipped and untarred it. ## (/) In order to configure the crowd connection I did the following: ### (/) I scp'd the /opt/crowd/client/crowd-integration-client-1.6.jar file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I removed the existing 1.6.1 crowd client jar from the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I scp'd the /opt/crowd/client/conf/crowd.properties file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I scp'd the /opt/crowd/client/conf/crowd-ehcache.xml file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I edited the crowd.properties file on bugs to look like: {noformat} application.name JIRA3135 application.password (ask Kevin) application.login.url http://oceana.mbari.org:8095/crowd/console/ crowd.server.url http://oceana.mbari.org:8095/crowd/services/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 0 session.lastvalidation session.lastvalidation {noformat} ### (/) I edited the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/osuser.xml file to comment out the current authentication mechanism and then uncomment the crowd one. ## (/) I then edited the /opt/atlassian-jira-standalone-3.13.5/conf/server/xml file and configured the database connection to the Jira_Temp database on Solstice2. I looked like this: {noformat} {noformat} ## (/) Edit the /opt/atlassian/jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/entityengine.xml and changed it from 'hsql' to 'mssql' and delete the line with "PUBLIC" in it per the instructions in the comments in that file. ## (/) I edited the /etc/httpd/conf/httpd.conf file and created a proxy pass at the bottom of the file to point a normal URL to the default port 8080 for JIRA: {noformat} # Proxy Pass for JIRA ProxyPass http://bugs.mbari.org:8080 ProxyPassReverse http://bugs.mbari.org:8080 {noformat} ## (/) I restarted Apache ## (/) I scp'd the jtds driver from oceana to the /opt/atlassian-jira-standalone-3.13.5/common/lib directory (you could down from the internet) ## (/) I then went to the /opt/atlassian-jira-standalone-3.13.5/ directory and ran './bin/startup.sh'. From the log file, I could tell things were hanging. After some troubleshooting I am wondering if the local firewall is preventing the application to get access to the database on solstice2. I can telnet to port 1433, but I can't browse to the base http://bugs.mbari.org from anywhere but the local web browser. I have submitted a ticket. ## (/) I restarted the old JIRA with my hopes dashed :(. ## (/) Pat disabled the firewall on bugs.mbari.org but it still hung trying to connect to solstice2.shore.mbari.org. That is really, really perplexing. Neil mentioned that solstice2 is using Kerberos and solstice is not. Checking with the JTDS docs, version 1.3.1 of the driver added kerberos support, so I downloaded that driver and added the 'userKerberos=true' property to the URL in the server.xml file and restarted. Got an error about no credentials, so added user and password properties to the URL. Nope, no luck. Never did figure this one out, but I had Pat pull the VM inside the firewall and after some thrash it worked. Well, it sort of worked ... sigh. It turns out I had downloaded the standard version instead of the enterprise version. I need to redo this work ... grrr. ## (/) I deleted all the tables in the Jira_Temp database and removed the /data/jira3135/indexes directory (and recreated). ## (/) I downloaded the enterprise version of the 3.13.5 server. I made a copy in the /opt directory and unzipped and untarred the file. ## (/) I went back to crowd and edited the application to change the properties to: ### URL: http://bugs.shore.mbari.org:8080 ### IP: 134.89.12.31 ### Name: jira3135 ### Password: (ask Kevin) :) ## (/) I then repeated the steps above to get the server up and running with the following differences: ### The server name is now bugs.shore.mbari.org ### The paths given above are a little different in that they no longer say "standard" but say "enterprise" ### I deleted the proxy pass as it seemed to have issues before and this is only temporary anyway. ## (/) I then browsed to http://bugs.shore.mbari.org:8080 ## (/) It took me to the start up page and at the top was the option to 'import your existing data'. Seemed too good not to try. I clicked on the link. It asked me for the backup file location and the location where the indexes would be stored. ## (/) I copied the XML zip file and the attachments tar file to the /data/original directory. ## (/) I created the /data/jira3135/indexes and used those directories ... it fired off the import and I waited. ## (/) I tailed the log file to watch the import. Holy crap, it worked!!! I could log in and everything! I copied the results from the log file here for posterity sake: {noformat} 2015-07-22 20:55:45,156 http-8080-Processor22 INFO [jira.action.admin.DataImport] Running data import 2015-07-22 20:55:45,179 http-8080-Processor22 INFO [jira.action.admin.DataImport] Importing data.. 2015-07-22 20:55:45,186 http-8080-Processor22 INFO [jira.action.admin.DataImport] Start parsing XML with SAX Parser 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] XML successfully parsed 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] Removing all entries from the database. 2015-07-22 20:56:24,593 http-8080-Processor22 INFO [jira.action.admin.DataImport] All entries removed. 2015-07-22 20:56:24,594 http-8080-Processor22 INFO [jira.action.admin.DataImport] Started storing 410414 Generic Values 2015-07-22 21:01:51,967 http-8080-Processor22 INFO [jira.action.admin.DataImport] Finished storing Generic Values 2015-07-22 21:01:52,329 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:52,361 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:54,683 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLink' to module 'jira.user.format:profile-link-user-format'. 2015-07-22 21:01:54,724 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullName' to module 'jira.user.format:full-name-user-format'. 2015-07-22 21:01:54,773 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkSearcher' to module 'jira.user.format:profile-link-searcher-user-format'. 2015-07-22 21:01:54,784 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkExternal' to module 'jira.user.format:profile-link-external-user-format'. 2015-07-22 21:01:54,795 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkActionHeader' to module 'jira.user.format:profile-link-action-header-user-format'. 2015-07-22 21:01:54,807 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullProfile' to module 'jira.user.format:full-profile-user-format'. 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/comments 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/issues 2015-07-22 21:01:55,641 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/plugins 2015-07-22 21:01:55,867 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:01:55,871 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/issues does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:55,873 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/comments does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,033 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,257 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,889 http-8080-Processor22 ERROR [atlassian.jira.upgrade.ConsistencyCheckImpl] Attachments are turned on, but attachment path [/data/jira_3_12/attachments] invalid - disabling attachments 2015-07-22 21:02:13,904 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Detected that an upgrade is needed; existing data at build 299 2015-07-22 21:02:13,907 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Doing Upgrade... 2015-07-22 21:02:13,915 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value' succeeded 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 317 2015-07-22 21:02:13,944 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite filters - make each filter a favourite of its owner. 2015-07-22 21:02:17,822 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build319] Could not find author 'fpy' for filter with id '10040' 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite filters - make each filter a favourite of its owner.' succeeded 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 319 2015-07-22 21:02:17,995 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise Share Permissions. Move old shares to new shares. 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise Share Permissions. Move old shares to new shares.' succeeded 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 321 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Migrating the old JIRA UI colors to the new JIRA 3.13 colors 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build322] Custom color detected for jira.lf.menu.bgcolour : #336699 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Migrating the old JIRA UI colors to the new JIRA 3.13 colors' succeeded 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 322 2015-07-22 21:02:18,025 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite dashboards - make each dashboard a favourite of its owner. 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'cmcgann' for dashboard with id '10030' 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'fpy' for dashboard with id '10060' 2015-07-22 21:02:18,423 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'kanna' for dashboard with id '10040' 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite dashboards - make each dashboard a favourite of its owner.' succeeded 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 325 2015-07-22 21:02:18,625 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Reindexing all data in JIRA to include Favourites. 2015-07-22 21:02:18,648 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All starting... 2015-07-22 21:02:18,650 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 0% complete. Current index: Issue 2015-07-22 21:02:18,654 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:02:18,809 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 1% complete. Current index: Issue 2015-07-22 21:02:18,855 indexerPool-2-thread-10 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 2% complete. Current index: Issue 2015-07-22 21:02:18,899 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 3% complete. Current index: Issue 2015-07-22 21:02:18,945 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 4% complete. Current index: Issue 2015-07-22 21:02:19,012 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 5% complete. Current index: Issue . . . 2015-07-22 21:02:26,164 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 95% complete. Current index: Issue 2015-07-22 21:02:26,232 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 96% complete. Current index: Issue 2015-07-22 21:02:26,316 indexerPool-2-thread-9 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 97% complete. Current index: Issue 2015-07-22 21:02:26,771 indexerPool-2-thread-3 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: Issue 2015-07-22 21:02:27,261 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 8607ms. Indexer: DefaultIndexManager: paths: [/data/jira3135/indexes/issues, /data/jira3135/indexes/comments] 2015-07-22 21:02:27,263 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: SearchRequest 2015-07-22 21:02:27,268 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,293 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: SearchRequest 2015-07-22 21:02:27,308 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: PortalPage 2015-07-22 21:02:27,312 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,377 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: PortalPage 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 115ms. Indexer: SharedEntityIndexManager: paths: [/data/jira3135/indexes/entities/portalpage, /data/jira3135/indexes/entities/searchrequest] 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All complete. Total time: 8722ms. 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Reindexing all data in JIRA to include Favourites.' succeeded 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 326 2015-07-22 21:02:27,397 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade succeeded! Setting data build number to 360 2015-07-22 21:02:27,469 JiraQuartzScheduler_Worker-0 WARN [service.services.export.ExportService] Backup directory /data/jira_3_12/backup does not exist {noformat} {warning:title=Paths} It appears that the upgraded JIRA will still look for the attachments and the backup locations in the original places. So I created /data/jira_3_12/backup and untarred the original attachments to /data/jira_3_12 and then everything worked (including attachements) in the new JIRA. {warning} ## (/) I then used the upgraded JIRA to generate a new XML backup and stored it in /data/original/3.13.5 along with another tar of the files in /data/jira_3_12/attachments. ## (/) I then shutdown the JIRA server. *I should be ready to move on to version 4 upgrade WHEW* ## So, before moving on, I decided that it would be a really good idea to spin up a new Crowd instance to get rid of the :8443 in the URL and to move off of RedHat per IS requests. I have a ticket in for a new VM and a new database to try to get this going. I am waiting on that before moving on. ## (/) Pat created the VM and Neil created the database. ## (/) I logged into auth.mbari.org (name of the VM) and downloaded crowd which I unzipped to the /opt directory ## (/) I then created a /data/crowd directory and gave my account permissions on it and then edited the /opt/atlassian..../crowd-webapp/WEB-INF/classes/crowd-init.properties file to set that as the crowd home directory. ## (/) The instructions say to download the JDBC driver, but they already have JTDS 1.2.7 in the download so I did not do anything. ## (/) I fired up crowd and then went to the http://localhost:8095 URL to start the configuration. I input the DB connection parameters and it created the DB and took off just fine. I really wanted to run the application on port 80 and 443 as normal applications do so I first tried to change the port numbers that the application ran on. That did not work as those are privileged ports and cannot be controller unless you are root. I did not want to do that, so I will have to do a proxy pass. I had to start up the httpd services (I will need to configure as a service) and then created a new file in /etc/httpd/conf.d called crowd.conf that contained the following: {noformat} # This is the configuration for the proxy pass for the crowd server ProxyRequests Off ProxyPreserveHost On Require all granted ProxyPass /crowd http://auth.mbari.org:8095/crowd ProxyPassReverse /crowd http://auth.mbari.org:8095/crowd Require all granted ProxyPass /openidserver http://auth.mbari.org:8095/openidserver ProxyPassReverse /openidserver http://auth.mbari.org:8095/openidserver Require all granted {noformat} ## (/) This worked for the basic HTTP so I will have to get it working with SSL. ## (/) Something with the openidserver is not working correctly and I suspect I have not done the openidserver install completely or correctly. I read the directions on configuring crowdid and it's connection to the database and restarted the crowd server. That worked, not I have both working of straight HTTP, now I need to get SSL going. ## (/) I originally started to configure SSL for the Tomcat server for Crowd, but then realized, since I am putting the Apache proxy in front of Tomcat, I should be able to just set up SSL on Apache HTTP and leave Tomcat alone (i.e. traffic between Apache HTTP and Tomcat does not need to be encrypted). # Schedule upgrade date and send all hands several days in advance. # When the day arrives, send all hands announcing JIRA outage. # From the Administrator's page in our existing JIRA, perform a 'Backup Data to XML'. # Login to oceana.mbari.org as root. # Shutdown JIRA # Create a tar.gz of the /opt/atlassian-jira-enterprise-3.12.1-standalone directory # Clean up the /data/jira_3_12/backups directory by deleting all but maybe the last 5 backups. # Create a tar.gz of the JIRA home directory on ocean.mbari.org which is located at /data/jira_3_12 # scp both tar.gz files to bugs.mbari.org # login to bugs.mbari.org # Unpack the home directory tar to /data/jira # Run the installer as root (this might need IS help or sudo privs). Note that we usually install the application to /opt # Run the JIRA Configuration tool to set the jira.home to the /data/jira location # Connect to JIRA_Temp database on Solstice2 (.... more to do here, see Atlassian docs) # Migrate existing configuration over to new JIRA (I need to add more here as we added Crowd). # Start JIRA # Import backed up XML # Perform post upgrades checks and tests *Need to document steps for 4.4.5->6.X*]]> 27558091 13959335 13926573 13959338 13926576 27590857 4.4: [https://confluence.atlassian.com/display/JIRA044/Migrating+JIRA+to+Another+Server] ## The JIRA configuration tool: [https://confluence.atlassian.com/display/JIRA044/Using+the+JIRA+Configuration+Tool] h5. Steps # (/) Create new VM named bugs.mbari.org in the DMZ # (/) Have Neil create database Jira_Temp on solstice2.shore.mbari.org # (/) Have Neil create database Jira on solstice2.shore.mbari.org # (/) Have Pat install Java 7 on bugs.shore.mbari.org # (/) Have Pete plumb holes through firewall so processes on bugs.mbari.org can get to Solstice2 # (/) Have Pat create DB_Collaboration account on bugs so it can run JIRA under that account and it can connect to solstice2 using that NT Domain account. # (/) Upgrade license on Atlassian site # (/) Log into bugs.shore.mbari.org # (/) Download 3.13.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 4.4.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 5.2.11 standalone Linux 64 bit tar.gz (not sure this version is necessary, but at least I have it) # (/) Unzip and untar the file to /opt # (/) Download latest JIRA (6.4.7 as of this writing). # (/) Unzip and untar it to /opt # Performed Test Upgrade ## (/) In order to export the current stuff in JIRA, I had to shut off access so people could not change the data while I was backing it up. ## (/) I ssh'd to oceana.mbari.org as root and edited the /opt/jira/conf/server.xml file and commented out the Connector section that had the port of 8010 to shut it off from the normal serving route. ## (/) I uncommented the 8082 port connector and the 8443 port connector so that I could still get to the server. ## (/) I stopped and started the JIRA server and in the log file I got a "keystore was tampered with..." which is not surprising. ## (/) I could then browser over to http://oceana.mbari.org:8082/jira ## (/) Then through the Administration console, I did an XML backup ## (/) I then created a tar of all the attachments in the /data/jira_3_12/attachments directory ## (/) I moved both the XML and tar files to the /root/jira-upgrade directory ## (/) I then reversed the changes to the server.xml file and shut down JIRA ## (/) I left it down during the next steps in case it went so well, I could just point people to the new server (yeah, right). ## (/) I then browsed to the crowd server on oceana and add a new application using: ### URL: http://bugs.mbari.org/jira3135 ### IP: 134.89.2.29 ### Name: JIRA3135 ### Password: (ask Kevin) :) ## (/) On bugs, I made a copy of the JIRA 3.13.5 download in the /opt directory and unzipped and untarred it. ## (/) In order to configure the crowd connection I did the following: ### (/) I scp'd the /opt/crowd/client/crowd-integration-client-1.6.jar file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I removed the existing 1.6.1 crowd client jar from the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I scp'd the /opt/crowd/client/conf/crowd.properties file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I scp'd the /opt/crowd/client/conf/crowd-ehcache.xml file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I edited the crowd.properties file on bugs to look like: {noformat} application.name JIRA3135 application.password (ask Kevin) application.login.url http://oceana.mbari.org:8095/crowd/console/ crowd.server.url http://oceana.mbari.org:8095/crowd/services/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 0 session.lastvalidation session.lastvalidation {noformat} ### (/) I edited the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/osuser.xml file to comment out the current authentication mechanism and then uncomment the crowd one. ## (/) I then edited the /opt/atlassian-jira-standalone-3.13.5/conf/server/xml file and configured the database connection to the Jira_Temp database on Solstice2. I looked like this: {noformat} {noformat} ## (/) Edit the /opt/atlassian/jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/entityengine.xml and changed it from 'hsql' to 'mssql' and delete the line with "PUBLIC" in it per the instructions in the comments in that file. ## (/) I edited the /etc/httpd/conf/httpd.conf file and created a proxy pass at the bottom of the file to point a normal URL to the default port 8080 for JIRA: {noformat} # Proxy Pass for JIRA ProxyPass http://bugs.mbari.org:8080 ProxyPassReverse http://bugs.mbari.org:8080 {noformat} ## (/) I restarted Apache ## (/) I scp'd the jtds driver from oceana to the /opt/atlassian-jira-standalone-3.13.5/common/lib directory (you could down from the internet) ## (/) I then went to the /opt/atlassian-jira-standalone-3.13.5/ directory and ran './bin/startup.sh'. From the log file, I could tell things were hanging. After some troubleshooting I am wondering if the local firewall is preventing the application to get access to the database on solstice2. I can telnet to port 1433, but I can't browse to the base http://bugs.mbari.org from anywhere but the local web browser. I have submitted a ticket. ## (/) I restarted the old JIRA with my hopes dashed :(. ## (/) Pat disabled the firewall on bugs.mbari.org but it still hung trying to connect to solstice2.shore.mbari.org. That is really, really perplexing. Neil mentioned that solstice2 is using Kerberos and solstice is not. Checking with the JTDS docs, version 1.3.1 of the driver added kerberos support, so I downloaded that driver and added the 'userKerberos=true' property to the URL in the server.xml file and restarted. Got an error about no credentials, so added user and password properties to the URL. Nope, no luck. Never did figure this one out, but I had Pat pull the VM inside the firewall and after some thrash it worked. Well, it sort of worked ... sigh. It turns out I had downloaded the standard version instead of the enterprise version. I need to redo this work ... grrr. ## (/) I deleted all the tables in the Jira_Temp database and removed the /data/jira3135/indexes directory (and recreated). ## (/) I downloaded the enterprise version of the 3.13.5 server. I made a copy in the /opt directory and unzipped and untarred the file. ## (/) I went back to crowd and edited the application to change the properties to: ### URL: http://bugs.shore.mbari.org:8080 ### IP: 134.89.12.31 ### Name: jira3135 ### Password: (ask Kevin) :) ## (/) I then repeated the steps above to get the server up and running with the following differences: ### The server name is now bugs.shore.mbari.org ### The paths given above are a little different in that they no longer say "standard" but say "enterprise" ### I deleted the proxy pass as it seemed to have issues before and this is only temporary anyway. ## (/) I then browsed to http://bugs.shore.mbari.org:8080 ## (/) It took me to the start up page and at the top was the option to 'import your existing data'. Seemed too good not to try. I clicked on the link. It asked me for the backup file location and the location where the indexes would be stored. ## (/) I copied the XML zip file and the attachments tar file to the /data/original directory. ## (/) I created the /data/jira3135/indexes and used those directories ... it fired off the import and I waited. ## (/) I tailed the log file to watch the import. Holy crap, it worked!!! I could log in and everything! I copied the results from the log file here for posterity sake: {noformat} 2015-07-22 20:55:45,156 http-8080-Processor22 INFO [jira.action.admin.DataImport] Running data import 2015-07-22 20:55:45,179 http-8080-Processor22 INFO [jira.action.admin.DataImport] Importing data.. 2015-07-22 20:55:45,186 http-8080-Processor22 INFO [jira.action.admin.DataImport] Start parsing XML with SAX Parser 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] XML successfully parsed 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] Removing all entries from the database. 2015-07-22 20:56:24,593 http-8080-Processor22 INFO [jira.action.admin.DataImport] All entries removed. 2015-07-22 20:56:24,594 http-8080-Processor22 INFO [jira.action.admin.DataImport] Started storing 410414 Generic Values 2015-07-22 21:01:51,967 http-8080-Processor22 INFO [jira.action.admin.DataImport] Finished storing Generic Values 2015-07-22 21:01:52,329 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:52,361 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:54,683 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLink' to module 'jira.user.format:profile-link-user-format'. 2015-07-22 21:01:54,724 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullName' to module 'jira.user.format:full-name-user-format'. 2015-07-22 21:01:54,773 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkSearcher' to module 'jira.user.format:profile-link-searcher-user-format'. 2015-07-22 21:01:54,784 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkExternal' to module 'jira.user.format:profile-link-external-user-format'. 2015-07-22 21:01:54,795 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkActionHeader' to module 'jira.user.format:profile-link-action-header-user-format'. 2015-07-22 21:01:54,807 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullProfile' to module 'jira.user.format:full-profile-user-format'. 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/comments 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/issues 2015-07-22 21:01:55,641 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/plugins 2015-07-22 21:01:55,867 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:01:55,871 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/issues does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:55,873 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/comments does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,033 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,257 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,889 http-8080-Processor22 ERROR [atlassian.jira.upgrade.ConsistencyCheckImpl] Attachments are turned on, but attachment path [/data/jira_3_12/attachments] invalid - disabling attachments 2015-07-22 21:02:13,904 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Detected that an upgrade is needed; existing data at build 299 2015-07-22 21:02:13,907 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Doing Upgrade... 2015-07-22 21:02:13,915 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value' succeeded 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 317 2015-07-22 21:02:13,944 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite filters - make each filter a favourite of its owner. 2015-07-22 21:02:17,822 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build319] Could not find author 'fpy' for filter with id '10040' 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite filters - make each filter a favourite of its owner.' succeeded 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 319 2015-07-22 21:02:17,995 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise Share Permissions. Move old shares to new shares. 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise Share Permissions. Move old shares to new shares.' succeeded 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 321 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Migrating the old JIRA UI colors to the new JIRA 3.13 colors 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build322] Custom color detected for jira.lf.menu.bgcolour : #336699 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Migrating the old JIRA UI colors to the new JIRA 3.13 colors' succeeded 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 322 2015-07-22 21:02:18,025 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite dashboards - make each dashboard a favourite of its owner. 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'cmcgann' for dashboard with id '10030' 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'fpy' for dashboard with id '10060' 2015-07-22 21:02:18,423 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'kanna' for dashboard with id '10040' 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite dashboards - make each dashboard a favourite of its owner.' succeeded 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 325 2015-07-22 21:02:18,625 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Reindexing all data in JIRA to include Favourites. 2015-07-22 21:02:18,648 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All starting... 2015-07-22 21:02:18,650 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 0% complete. Current index: Issue 2015-07-22 21:02:18,654 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:02:18,809 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 1% complete. Current index: Issue 2015-07-22 21:02:18,855 indexerPool-2-thread-10 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 2% complete. Current index: Issue 2015-07-22 21:02:18,899 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 3% complete. Current index: Issue 2015-07-22 21:02:18,945 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 4% complete. Current index: Issue 2015-07-22 21:02:19,012 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 5% complete. Current index: Issue . . . 2015-07-22 21:02:26,164 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 95% complete. Current index: Issue 2015-07-22 21:02:26,232 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 96% complete. Current index: Issue 2015-07-22 21:02:26,316 indexerPool-2-thread-9 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 97% complete. Current index: Issue 2015-07-22 21:02:26,771 indexerPool-2-thread-3 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: Issue 2015-07-22 21:02:27,261 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 8607ms. Indexer: DefaultIndexManager: paths: [/data/jira3135/indexes/issues, /data/jira3135/indexes/comments] 2015-07-22 21:02:27,263 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: SearchRequest 2015-07-22 21:02:27,268 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,293 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: SearchRequest 2015-07-22 21:02:27,308 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: PortalPage 2015-07-22 21:02:27,312 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,377 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: PortalPage 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 115ms. Indexer: SharedEntityIndexManager: paths: [/data/jira3135/indexes/entities/portalpage, /data/jira3135/indexes/entities/searchrequest] 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All complete. Total time: 8722ms. 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Reindexing all data in JIRA to include Favourites.' succeeded 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 326 2015-07-22 21:02:27,397 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade succeeded! Setting data build number to 360 2015-07-22 21:02:27,469 JiraQuartzScheduler_Worker-0 WARN [service.services.export.ExportService] Backup directory /data/jira_3_12/backup does not exist {noformat} {warning:title=Paths} It appears that the upgraded JIRA will still look for the attachments and the backup locations in the original places. So I created /data/jira_3_12/backup and untarred the original attachments to /data/jira_3_12 and then everything worked (including attachements) in the new JIRA. {warning} ## (/) I then used the upgraded JIRA to generate a new XML backup and stored it in /data/original/3.13.5 along with another tar of the files in /data/jira_3_12/attachments. ## (/) I then shutdown the JIRA server. *I should be ready to move on to version 4 upgrade WHEW* ## So, before moving on, I decided that it would be a really good idea to spin up a new Crowd instance to get rid of the :8443 in the URL and to move off of RedHat per IS requests. I have a ticket in for a new VM and a new database to try to get this going. I am waiting on that before moving on. ## (/) Pat created the VM and Neil created the database. ## (/) I logged into auth.mbari.org (name of the VM) and downloaded crowd which I unzipped to the /opt directory ## (/) I then created a /data/crowd directory and gave my account permissions on it and then edited the /opt/atlassian..../crowd-webapp/WEB-INF/classes/crowd-init.properties file to set that as the crowd home directory. ## (/) The instructions say to download the JDBC driver, but they already have JTDS 1.2.7 in the download so I did not do anything. ## (/) You have to manually connect up CrowdID to a database as they setup wizard does not currently do this. ### (/) They say to download the driver, but again 1.2.7 was there so I did nothing. ### (/) I edited the /opt/atlassian.../apache-tomcat/conf/Catalina/localhost/openidserver.xml to look like: {noformat} {noformat} ## (/) I fired up crowd and then went to the http://localhost:8095 URL to start the configuration. I input the DB connection parameters and it created the DB and took off just fine. I really wanted to run the application on port 80 and 443 as normal applications do so I first tried to change the port numbers that the application ran on. That did not work as those are privileged ports and cannot be controller unless you are root. I did not want to do that, so I will have to do a proxy pass. I had to start up the httpd services (I will need to configure as a service) and then created a new file in /etc/httpd/conf.d called crowd.conf that contained the following: {noformat} # This is the configuration for the proxy pass for the crowd server ProxyRequests Off ProxyPreserveHost On Require all granted ProxyPass /crowd http://auth.mbari.org:8095/crowd ProxyPassReverse /crowd http://auth.mbari.org:8095/crowd Require all granted ProxyPass /openidserver http://auth.mbari.org:8095/openidserver ProxyPassReverse /openidserver http://auth.mbari.org:8095/openidserver Require all granted {noformat} ## (/) This worked for the basic HTTP so I will have to get it working with SSL. ## (/) Something with the openidserver is not working correctly and I suspect I have not done the openidserver install completely or correctly. I read the directions on configuring crowdid and it's connection to the database and restarted the crowd server. That worked, not I have both working of straight HTTP, now I need to get SSL going. ## (/) I originally started to configure SSL for the Tomcat server for Crowd, but then realized, since I am putting the Apache proxy in front of Tomcat, I should be able to just set up SSL on Apache HTTP and leave Tomcat alone (i.e. traffic between Apache HTTP and Tomcat does not need to be encrypted). # Schedule upgrade date and send all hands several days in advance. # When the day arrives, send all hands announcing JIRA outage. # From the Administrator's page in our existing JIRA, perform a 'Backup Data to XML'. # Login to oceana.mbari.org as root. # Shutdown JIRA # Create a tar.gz of the /opt/atlassian-jira-enterprise-3.12.1-standalone directory # Clean up the /data/jira_3_12/backups directory by deleting all but maybe the last 5 backups. # Create a tar.gz of the JIRA home directory on ocean.mbari.org which is located at /data/jira_3_12 # scp both tar.gz files to bugs.mbari.org # login to bugs.mbari.org # Unpack the home directory tar to /data/jira # Run the installer as root (this might need IS help or sudo privs). Note that we usually install the application to /opt # Run the JIRA Configuration tool to set the jira.home to the /data/jira location # Connect to JIRA_Temp database on Solstice2 (.... more to do here, see Atlassian docs) # Migrate existing configuration over to new JIRA (I need to add more here as we added Crowd). # Start JIRA # Import backed up XML # Perform post upgrades checks and tests *Need to document steps for 4.4.5->6.X*]]> 27558092 13959332 13926570 13959334 13926572 27590854 4.4: [https://confluence.atlassian.com/display/JIRA044/Migrating+JIRA+to+Another+Server] ## The JIRA configuration tool: [https://confluence.atlassian.com/display/JIRA044/Using+the+JIRA+Configuration+Tool] h5. Steps # (/) Create new VM named bugs.mbari.org in the DMZ # (/) Have Neil create database Jira_Temp on solstice2.shore.mbari.org # (/) Have Neil create database Jira on solstice2.shore.mbari.org # (/) Have Pat install Java 7 on bugs.shore.mbari.org # (/) Have Pete plumb holes through firewall so processes on bugs.mbari.org can get to Solstice2 # (/) Have Pat create DB_Collaboration account on bugs so it can run JIRA under that account and it can connect to solstice2 using that NT Domain account. # (/) Upgrade license on Atlassian site # (/) Log into bugs.shore.mbari.org # (/) Download 3.13.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 4.4.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 5.2.11 standalone Linux 64 bit tar.gz (not sure this version is necessary, but at least I have it) # (/) Unzip and untar the file to /opt # (/) Download latest JIRA (6.4.7 as of this writing). # (/) Unzip and untar it to /opt # Performed Test Upgrade ## (/) In order to export the current stuff in JIRA, I had to shut off access so people could not change the data while I was backing it up. ## (/) I ssh'd to oceana.mbari.org as root and edited the /opt/jira/conf/server.xml file and commented out the Connector section that had the port of 8010 to shut it off from the normal serving route. ## (/) I uncommented the 8082 port connector and the 8443 port connector so that I could still get to the server. ## (/) I stopped and started the JIRA server and in the log file I got a "keystore was tampered with..." which is not surprising. ## (/) I could then browser over to http://oceana.mbari.org:8082/jira ## (/) Then through the Administration console, I did an XML backup ## (/) I then created a tar of all the attachments in the /data/jira_3_12/attachments directory ## (/) I moved both the XML and tar files to the /root/jira-upgrade directory ## (/) I then reversed the changes to the server.xml file and shut down JIRA ## (/) I left it down during the next steps in case it went so well, I could just point people to the new server (yeah, right). ## (/) I then browsed to the crowd server on oceana and add a new application using: ### URL: http://bugs.mbari.org/jira3135 ### IP: 134.89.2.29 ### Name: JIRA3135 ### Password: (ask Kevin) :) ## (/) On bugs, I made a copy of the JIRA 3.13.5 download in the /opt directory and unzipped and untarred it. ## (/) In order to configure the crowd connection I did the following: ### (/) I scp'd the /opt/crowd/client/crowd-integration-client-1.6.jar file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I removed the existing 1.6.1 crowd client jar from the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I scp'd the /opt/crowd/client/conf/crowd.properties file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I scp'd the /opt/crowd/client/conf/crowd-ehcache.xml file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I edited the crowd.properties file on bugs to look like: {noformat} application.name JIRA3135 application.password (ask Kevin) application.login.url http://oceana.mbari.org:8095/crowd/console/ crowd.server.url http://oceana.mbari.org:8095/crowd/services/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 0 session.lastvalidation session.lastvalidation {noformat} ### (/) I edited the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/osuser.xml file to comment out the current authentication mechanism and then uncomment the crowd one. ## (/) I then edited the /opt/atlassian-jira-standalone-3.13.5/conf/server/xml file and configured the database connection to the Jira_Temp database on Solstice2. I looked like this: {noformat} {noformat} ## (/) Edit the /opt/atlassian/jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/entityengine.xml and changed it from 'hsql' to 'mssql' and delete the line with "PUBLIC" in it per the instructions in the comments in that file. ## (/) I edited the /etc/httpd/conf/httpd.conf file and created a proxy pass at the bottom of the file to point a normal URL to the default port 8080 for JIRA: {noformat} # Proxy Pass for JIRA ProxyPass http://bugs.mbari.org:8080 ProxyPassReverse http://bugs.mbari.org:8080 {noformat} ## (/) I restarted Apache ## (/) I scp'd the jtds driver from oceana to the /opt/atlassian-jira-standalone-3.13.5/common/lib directory (you could down from the internet) ## (/) I then went to the /opt/atlassian-jira-standalone-3.13.5/ directory and ran './bin/startup.sh'. From the log file, I could tell things were hanging. After some troubleshooting I am wondering if the local firewall is preventing the application to get access to the database on solstice2. I can telnet to port 1433, but I can't browse to the base http://bugs.mbari.org from anywhere but the local web browser. I have submitted a ticket. ## (/) I restarted the old JIRA with my hopes dashed :(. ## (/) Pat disabled the firewall on bugs.mbari.org but it still hung trying to connect to solstice2.shore.mbari.org. That is really, really perplexing. Neil mentioned that solstice2 is using Kerberos and solstice is not. Checking with the JTDS docs, version 1.3.1 of the driver added kerberos support, so I downloaded that driver and added the 'userKerberos=true' property to the URL in the server.xml file and restarted. Got an error about no credentials, so added user and password properties to the URL. Nope, no luck. Never did figure this one out, but I had Pat pull the VM inside the firewall and after some thrash it worked. Well, it sort of worked ... sigh. It turns out I had downloaded the standard version instead of the enterprise version. I need to redo this work ... grrr. ## (/) I deleted all the tables in the Jira_Temp database and removed the /data/jira3135/indexes directory (and recreated). ## (/) I downloaded the enterprise version of the 3.13.5 server. I made a copy in the /opt directory and unzipped and untarred the file. ## (/) I went back to crowd and edited the application to change the properties to: ### URL: http://bugs.shore.mbari.org:8080 ### IP: 134.89.12.31 ### Name: jira3135 ### Password: (ask Kevin) :) ## (/) I then repeated the steps above to get the server up and running with the following differences: ### The server name is now bugs.shore.mbari.org ### The paths given above are a little different in that they no longer say "standard" but say "enterprise" ### I deleted the proxy pass as it seemed to have issues before and this is only temporary anyway. ## (/) I then browsed to http://bugs.shore.mbari.org:8080 ## (/) It took me to the start up page and at the top was the option to 'import your existing data'. Seemed too good not to try. I clicked on the link. It asked me for the backup file location and the location where the indexes would be stored. ## (/) I copied the XML zip file and the attachments tar file to the /data/original directory. ## (/) I created the /data/jira3135/indexes and used those directories ... it fired off the import and I waited. ## (/) I tailed the log file to watch the import. Holy crap, it worked!!! I could log in and everything! I copied the results from the log file here for posterity sake: {noformat} 2015-07-22 20:55:45,156 http-8080-Processor22 INFO [jira.action.admin.DataImport] Running data import 2015-07-22 20:55:45,179 http-8080-Processor22 INFO [jira.action.admin.DataImport] Importing data.. 2015-07-22 20:55:45,186 http-8080-Processor22 INFO [jira.action.admin.DataImport] Start parsing XML with SAX Parser 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] XML successfully parsed 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] Removing all entries from the database. 2015-07-22 20:56:24,593 http-8080-Processor22 INFO [jira.action.admin.DataImport] All entries removed. 2015-07-22 20:56:24,594 http-8080-Processor22 INFO [jira.action.admin.DataImport] Started storing 410414 Generic Values 2015-07-22 21:01:51,967 http-8080-Processor22 INFO [jira.action.admin.DataImport] Finished storing Generic Values 2015-07-22 21:01:52,329 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:52,361 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:54,683 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLink' to module 'jira.user.format:profile-link-user-format'. 2015-07-22 21:01:54,724 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullName' to module 'jira.user.format:full-name-user-format'. 2015-07-22 21:01:54,773 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkSearcher' to module 'jira.user.format:profile-link-searcher-user-format'. 2015-07-22 21:01:54,784 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkExternal' to module 'jira.user.format:profile-link-external-user-format'. 2015-07-22 21:01:54,795 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkActionHeader' to module 'jira.user.format:profile-link-action-header-user-format'. 2015-07-22 21:01:54,807 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullProfile' to module 'jira.user.format:full-profile-user-format'. 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/comments 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/issues 2015-07-22 21:01:55,641 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/plugins 2015-07-22 21:01:55,867 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:01:55,871 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/issues does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:55,873 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/comments does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,033 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,257 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,889 http-8080-Processor22 ERROR [atlassian.jira.upgrade.ConsistencyCheckImpl] Attachments are turned on, but attachment path [/data/jira_3_12/attachments] invalid - disabling attachments 2015-07-22 21:02:13,904 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Detected that an upgrade is needed; existing data at build 299 2015-07-22 21:02:13,907 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Doing Upgrade... 2015-07-22 21:02:13,915 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value' succeeded 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 317 2015-07-22 21:02:13,944 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite filters - make each filter a favourite of its owner. 2015-07-22 21:02:17,822 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build319] Could not find author 'fpy' for filter with id '10040' 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite filters - make each filter a favourite of its owner.' succeeded 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 319 2015-07-22 21:02:17,995 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise Share Permissions. Move old shares to new shares. 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise Share Permissions. Move old shares to new shares.' succeeded 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 321 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Migrating the old JIRA UI colors to the new JIRA 3.13 colors 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build322] Custom color detected for jira.lf.menu.bgcolour : #336699 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Migrating the old JIRA UI colors to the new JIRA 3.13 colors' succeeded 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 322 2015-07-22 21:02:18,025 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite dashboards - make each dashboard a favourite of its owner. 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'cmcgann' for dashboard with id '10030' 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'fpy' for dashboard with id '10060' 2015-07-22 21:02:18,423 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'kanna' for dashboard with id '10040' 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite dashboards - make each dashboard a favourite of its owner.' succeeded 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 325 2015-07-22 21:02:18,625 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Reindexing all data in JIRA to include Favourites. 2015-07-22 21:02:18,648 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All starting... 2015-07-22 21:02:18,650 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 0% complete. Current index: Issue 2015-07-22 21:02:18,654 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:02:18,809 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 1% complete. Current index: Issue 2015-07-22 21:02:18,855 indexerPool-2-thread-10 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 2% complete. Current index: Issue 2015-07-22 21:02:18,899 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 3% complete. Current index: Issue 2015-07-22 21:02:18,945 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 4% complete. Current index: Issue 2015-07-22 21:02:19,012 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 5% complete. Current index: Issue . . . 2015-07-22 21:02:26,164 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 95% complete. Current index: Issue 2015-07-22 21:02:26,232 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 96% complete. Current index: Issue 2015-07-22 21:02:26,316 indexerPool-2-thread-9 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 97% complete. Current index: Issue 2015-07-22 21:02:26,771 indexerPool-2-thread-3 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: Issue 2015-07-22 21:02:27,261 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 8607ms. Indexer: DefaultIndexManager: paths: [/data/jira3135/indexes/issues, /data/jira3135/indexes/comments] 2015-07-22 21:02:27,263 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: SearchRequest 2015-07-22 21:02:27,268 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,293 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: SearchRequest 2015-07-22 21:02:27,308 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: PortalPage 2015-07-22 21:02:27,312 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,377 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: PortalPage 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 115ms. Indexer: SharedEntityIndexManager: paths: [/data/jira3135/indexes/entities/portalpage, /data/jira3135/indexes/entities/searchrequest] 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All complete. Total time: 8722ms. 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Reindexing all data in JIRA to include Favourites.' succeeded 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 326 2015-07-22 21:02:27,397 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade succeeded! Setting data build number to 360 2015-07-22 21:02:27,469 JiraQuartzScheduler_Worker-0 WARN [service.services.export.ExportService] Backup directory /data/jira_3_12/backup does not exist {noformat} {warning:title=Paths} It appears that the upgraded JIRA will still look for the attachments and the backup locations in the original places. So I created /data/jira_3_12/backup and untarred the original attachments to /data/jira_3_12 and then everything worked (including attachements) in the new JIRA. {warning} ## (/) I then used the upgraded JIRA to generate a new XML backup and stored it in /data/original/3.13.5 along with another tar of the files in /data/jira_3_12/attachments. ## (/) I then shutdown the JIRA server. *I should be ready to move on to version 4 upgrade WHEW* ## So, before moving on, I decided that it would be a really good idea to spin up a new Crowd instance to get rid of the :8443 in the URL and to move off of RedHat per IS requests. I have a ticket in for a new VM and a new database to try to get this going. I am waiting on that before moving on. ## (/) Pat created the VM and Neil created the database. ## (/) I logged into auth.mbari.org (name of the VM) and downloaded crowd which I unzipped to the /opt directory ## (/) I then created a /data/crowd directory and gave my account permissions on it and then edited the /opt/atlassian..../crowd-webapp/WEB-INF/classes/crowd-init.properties file to set that as the crowd home directory. ## (/) I fired up crowd and then went to the http://localhost:8095 URL to start the configuration. I input the DB connection parameters and it created the DB and took off just fine. I really wanted to run the application on port 80 and 443 as normal applications do so I first tried to change the port numbers that the application ran on. That did not work as those are privileged ports and cannot be controller unless you are root. I did not want to do that, so I will have to do a proxy pass. I had to start up the httpd services (I will need to configure as a service) and then created a new file in /etc/httpd/conf.d called crowd.conf that contained the following: {noformat} # This is the configuration for the proxy pass for the crowd server ProxyRequests Off ProxyPreserveHost On Require all granted ProxyPass /crowd http://auth.mbari.org:8095/crowd ProxyPassReverse /crowd http://auth.mbari.org:8095/crowd Require all granted ProxyPass /openidserver http://auth.mbari.org:8095/openidserver ProxyPassReverse /openidserver http://auth.mbari.org:8095/openidserver Require all granted {noformat} ## (/) This worked for the basic HTTP so I will have to get it working with SSL. ## (/) Something with the openidserver is not working correctly and I suspect I have not done the openidserver install completely or correctly. I read the directions on configuring crowdid and it's connection to the database and restarted the crowd server. That worked, not I have both working of straight HTTP, now I need to get SSL going. ## (/) I originally started to configure SSL for the Tomcat server for Crowd, but then realized, since I am putting the Apache proxy in front of Tomcat, I should be able to just set up SSL on Apache HTTP and leave Tomcat alone (i.e. traffic between Apache HTTP and Tomcat does not need to be encrypted). # Schedule upgrade date and send all hands several days in advance. # When the day arrives, send all hands announcing JIRA outage. # From the Administrator's page in our existing JIRA, perform a 'Backup Data to XML'. # Login to oceana.mbari.org as root. # Shutdown JIRA # Create a tar.gz of the /opt/atlassian-jira-enterprise-3.12.1-standalone directory # Clean up the /data/jira_3_12/backups directory by deleting all but maybe the last 5 backups. # Create a tar.gz of the JIRA home directory on ocean.mbari.org which is located at /data/jira_3_12 # scp both tar.gz files to bugs.mbari.org # login to bugs.mbari.org # Unpack the home directory tar to /data/jira # Run the installer as root (this might need IS help or sudo privs). Note that we usually install the application to /opt # Run the JIRA Configuration tool to set the jira.home to the /data/jira location # Connect to JIRA_Temp database on Solstice2 (.... more to do here, see Atlassian docs) # Migrate existing configuration over to new JIRA (I need to add more here as we added Crowd). # Start JIRA # Import backed up XML # Perform post upgrades checks and tests *Need to document steps for 4.4.5->6.X*]]> 27558089 13959333 13926571 13959390 13926628 13959394 13926632 13959392 13926630 13959381 13926619 19073671 19040979 13959382 13926620 13959379 13926617 19073673 19040981 13959385 13926623 19073667 19040975 13959383 13926621 19073669 19040977 13959374 13926612 13959371 13926609 13959377 13926615 19073693 19041001 13959376 13926614 19073694 19041002 19073688 19040996 13959365 13926603 19073689 19040997 19073684 19040992 13959369 13926607 19073685 19040993 19073686 19040994 13959367 13926605 13959411 13926649 13959412 13926650 13959413 13926651 27590805 4.4: [https://confluence.atlassian.com/display/JIRA044/Migrating+JIRA+to+Another+Server] ## The JIRA configuration tool: [https://confluence.atlassian.com/display/JIRA044/Using+the+JIRA+Configuration+Tool] h5. Steps # (/) Create new VM named bugs.mbari.org in the DMZ # (/) Have Neil create database Jira_Temp on solstice2.shore.mbari.org # (/) Have Neil create database Jira on solstice2.shore.mbari.org # (/) Have Pat install Java 7 on bugs.shore.mbari.org # (/) Have Pete plumb holes through firewall so processes on bugs.mbari.org can get to Solstice2 # (/) Have Pat create DB_Collaboration account on bugs so it can run JIRA under that account and it can connect to solstice2 using that NT Domain account. # (/) Upgrade license on Atlassian site # (/) Log into bugs.shore.mbari.org # (/) Download 3.13.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 4.4.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 5.2.11 standalone Linux 64 bit tar.gz (not sure this version is necessary, but at least I have it) # (/) Unzip and untar the file to /opt # (/) Download latest JIRA (6.4.7 as of this writing). # (/) Unzip and untar it to /opt # Performed Test Upgrade ## (/) In order to export the current stuff in JIRA, I had to shut off access so people could not change the data while I was backing it up. ## (/) I ssh'd to oceana.mbari.org as root and edited the /opt/jira/conf/server.xml file and commented out the Connector section that had the port of 8010 to shut it off from the normal serving route. ## (/) I uncommented the 8082 port connector and the 8443 port connector so that I could still get to the server. ## (/) I stopped and started the JIRA server and in the log file I got a "keystore was tampered with..." which is not surprising. ## (/) I could then browser over to http://oceana.mbari.org:8082/jira ## (/) Then through the Administration console, I did an XML backup ## (/) I then created a tar of all the attachments in the /data/jira_3_12/attachments directory ## (/) I moved both the XML and tar files to the /root/jira-upgrade directory ## (/) I then reversed the changes to the server.xml file and shut down JIRA ## (/) I left it down during the next steps in case it went so well, I could just point people to the new server (yeah, right). ## (/) I then browsed to the crowd server on oceana and add a new application using: ### URL: http://bugs.mbari.org/jira3135 ### IP: 134.89.2.29 ### Name: JIRA3135 ### Password: (ask Kevin) :) ## (/) On bugs, I made a copy of the JIRA 3.13.5 download in the /opt directory and unzipped and untarred it. ## (/) In order to configure the crowd connection I did the following: ### (/) I scp'd the /opt/crowd/client/crowd-integration-client-1.6.jar file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I removed the existing 1.6.1 crowd client jar from the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I scp'd the /opt/crowd/client/conf/crowd.properties file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I scp'd the /opt/crowd/client/conf/crowd-ehcache.xml file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I edited the crowd.properties file on bugs to look like: {noformat} application.name JIRA3135 application.password (ask Kevin) application.login.url http://oceana.mbari.org:8095/crowd/console/ crowd.server.url http://oceana.mbari.org:8095/crowd/services/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 0 session.lastvalidation session.lastvalidation {noformat} ### (/) I edited the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/osuser.xml file to comment out the current authentication mechanism and then uncomment the crowd one. ## (/) I then edited the /opt/atlassian-jira-standalone-3.13.5/conf/server/xml file and configured the database connection to the Jira_Temp database on Solstice2. I looked like this: {noformat} {noformat} ## (/) Edit the /opt/atlassian/jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/entityengine.xml and changed it from 'hsql' to 'mssql' and delete the line with "PUBLIC" in it per the instructions in the comments in that file. ## (/) I edited the /etc/httpd/conf/httpd.conf file and created a proxy pass at the bottom of the file to point a normal URL to the default port 8080 for JIRA: {noformat} # Proxy Pass for JIRA ProxyPass http://bugs.mbari.org:8080 ProxyPassReverse http://bugs.mbari.org:8080 {noformat} ## (/) I restarted Apache ## (/) I scp'd the jtds driver from oceana to the /opt/atlassian-jira-standalone-3.13.5/common/lib directory (you could down from the internet) ## (/) I then went to the /opt/atlassian-jira-standalone-3.13.5/ directory and ran './bin/startup.sh'. From the log file, I could tell things were hanging. After some troubleshooting I am wondering if the local firewall is preventing the application to get access to the database on solstice2. I can telnet to port 1433, but I can't browse to the base http://bugs.mbari.org from anywhere but the local web browser. I have submitted a ticket. ## (/) I restarted the old JIRA with my hopes dashed :(. ## (/) Pat disabled the firewall on bugs.mbari.org but it still hung trying to connect to solstice2.shore.mbari.org. That is really, really perplexing. Neil mentioned that solstice2 is using Kerberos and solstice is not. Checking with the JTDS docs, version 1.3.1 of the driver added kerberos support, so I downloaded that driver and added the 'userKerberos=true' property to the URL in the server.xml file and restarted. Got an error about no credentials, so added user and password properties to the URL. Nope, no luck. Never did figure this one out, but I had Pat pull the VM inside the firewall and after some thrash it worked. Well, it sort of worked ... sigh. It turns out I had downloaded the standard version instead of the enterprise version. I need to redo this work ... grrr. ## (/) I deleted all the tables in the Jira_Temp database and removed the /data/jira3135/indexes directory (and recreated). ## (/) I downloaded the enterprise version of the 3.13.5 server. I made a copy in the /opt directory and unzipped and untarred the file. ## (/) I went back to crowd and edited the application to change the properties to: ### URL: http://bugs.shore.mbari.org:8080 ### IP: 134.89.12.31 ### Name: jira3135 ### Password: (ask Kevin) :) ## (/) I then repeated the steps above to get the server up and running with the following differences: ### The server name is now bugs.shore.mbari.org ### The paths given above are a little different in that they no longer say "standard" but say "enterprise" ### I deleted the proxy pass as it seemed to have issues before and this is only temporary anyway. ## (/) I then browsed to http://bugs.shore.mbari.org:8080 ## (/) It took me to the start up page and at the top was the option to 'import your existing data'. Seemed too good not to try. I clicked on the link. It asked me for the backup file location and the location where the indexes would be stored. ## (/) I copied the XML zip file and the attachments tar file to the /data/original directory. ## (/) I created the /data/jira3135/indexes and used those directories ... it fired off the import and I waited. ## (/) I tailed the log file to watch the import. Holy crap, it worked!!! I could log in and everything! I copied the results from the log file here for posterity sake: {noformat} 2015-07-22 20:55:45,156 http-8080-Processor22 INFO [jira.action.admin.DataImport] Running data import 2015-07-22 20:55:45,179 http-8080-Processor22 INFO [jira.action.admin.DataImport] Importing data.. 2015-07-22 20:55:45,186 http-8080-Processor22 INFO [jira.action.admin.DataImport] Start parsing XML with SAX Parser 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] XML successfully parsed 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] Removing all entries from the database. 2015-07-22 20:56:24,593 http-8080-Processor22 INFO [jira.action.admin.DataImport] All entries removed. 2015-07-22 20:56:24,594 http-8080-Processor22 INFO [jira.action.admin.DataImport] Started storing 410414 Generic Values 2015-07-22 21:01:51,967 http-8080-Processor22 INFO [jira.action.admin.DataImport] Finished storing Generic Values 2015-07-22 21:01:52,329 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:52,361 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:54,683 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLink' to module 'jira.user.format:profile-link-user-format'. 2015-07-22 21:01:54,724 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullName' to module 'jira.user.format:full-name-user-format'. 2015-07-22 21:01:54,773 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkSearcher' to module 'jira.user.format:profile-link-searcher-user-format'. 2015-07-22 21:01:54,784 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkExternal' to module 'jira.user.format:profile-link-external-user-format'. 2015-07-22 21:01:54,795 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkActionHeader' to module 'jira.user.format:profile-link-action-header-user-format'. 2015-07-22 21:01:54,807 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullProfile' to module 'jira.user.format:full-profile-user-format'. 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/comments 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/issues 2015-07-22 21:01:55,641 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/plugins 2015-07-22 21:01:55,867 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:01:55,871 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/issues does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:55,873 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/comments does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,033 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,257 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,889 http-8080-Processor22 ERROR [atlassian.jira.upgrade.ConsistencyCheckImpl] Attachments are turned on, but attachment path [/data/jira_3_12/attachments] invalid - disabling attachments 2015-07-22 21:02:13,904 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Detected that an upgrade is needed; existing data at build 299 2015-07-22 21:02:13,907 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Doing Upgrade... 2015-07-22 21:02:13,915 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value' succeeded 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 317 2015-07-22 21:02:13,944 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite filters - make each filter a favourite of its owner. 2015-07-22 21:02:17,822 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build319] Could not find author 'fpy' for filter with id '10040' 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite filters - make each filter a favourite of its owner.' succeeded 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 319 2015-07-22 21:02:17,995 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise Share Permissions. Move old shares to new shares. 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise Share Permissions. Move old shares to new shares.' succeeded 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 321 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Migrating the old JIRA UI colors to the new JIRA 3.13 colors 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build322] Custom color detected for jira.lf.menu.bgcolour : #336699 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Migrating the old JIRA UI colors to the new JIRA 3.13 colors' succeeded 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 322 2015-07-22 21:02:18,025 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite dashboards - make each dashboard a favourite of its owner. 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'cmcgann' for dashboard with id '10030' 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'fpy' for dashboard with id '10060' 2015-07-22 21:02:18,423 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'kanna' for dashboard with id '10040' 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite dashboards - make each dashboard a favourite of its owner.' succeeded 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 325 2015-07-22 21:02:18,625 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Reindexing all data in JIRA to include Favourites. 2015-07-22 21:02:18,648 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All starting... 2015-07-22 21:02:18,650 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 0% complete. Current index: Issue 2015-07-22 21:02:18,654 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:02:18,809 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 1% complete. Current index: Issue 2015-07-22 21:02:18,855 indexerPool-2-thread-10 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 2% complete. Current index: Issue 2015-07-22 21:02:18,899 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 3% complete. Current index: Issue 2015-07-22 21:02:18,945 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 4% complete. Current index: Issue 2015-07-22 21:02:19,012 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 5% complete. Current index: Issue . . . 2015-07-22 21:02:26,164 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 95% complete. Current index: Issue 2015-07-22 21:02:26,232 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 96% complete. Current index: Issue 2015-07-22 21:02:26,316 indexerPool-2-thread-9 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 97% complete. Current index: Issue 2015-07-22 21:02:26,771 indexerPool-2-thread-3 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: Issue 2015-07-22 21:02:27,261 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 8607ms. Indexer: DefaultIndexManager: paths: [/data/jira3135/indexes/issues, /data/jira3135/indexes/comments] 2015-07-22 21:02:27,263 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: SearchRequest 2015-07-22 21:02:27,268 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,293 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: SearchRequest 2015-07-22 21:02:27,308 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: PortalPage 2015-07-22 21:02:27,312 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,377 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: PortalPage 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 115ms. Indexer: SharedEntityIndexManager: paths: [/data/jira3135/indexes/entities/portalpage, /data/jira3135/indexes/entities/searchrequest] 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All complete. Total time: 8722ms. 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Reindexing all data in JIRA to include Favourites.' succeeded 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 326 2015-07-22 21:02:27,397 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade succeeded! Setting data build number to 360 2015-07-22 21:02:27,469 JiraQuartzScheduler_Worker-0 WARN [service.services.export.ExportService] Backup directory /data/jira_3_12/backup does not exist {noformat} {warning:title=Paths} It appears that the upgraded JIRA will still look for the attachments and the backup locations in the original places. So I created /data/jira_3_12/backup and untarred the original attachments to /data/jira_3_12 and then everything worked (including attachements) in the new JIRA. {warning} ## (/) I then used the upgraded JIRA to generate a new XML backup and stored it in /data/original/3.13.5 along with another tar of the files in /data/jira_3_12/attachments. ## (/) I then shutdown the JIRA server. *I should be ready to move on to version 4 upgrade WHEW* ## So, before moving on, I decided that it would be a really good idea to spin up a new Crowd instance to get rid of the :8443 in the URL and to move off of RedHat per IS requests. I have a ticket in for a new VM and a new database to try to get this going. I am waiting on that before moving on. ## (/) Pat created the VM and Neil created the database. ## (/) I logged into auth.mbari.org (name of the VM) and downloaded crowd which I unzipped to the /opt directory ## (/) I then created a /data/crowd directory and gave my account permissions on it and then edited the /opt/atlassian..../crowd-webapp/WEB-INF/classes/crowd-init.properties file to set that as the crowd home directory. ## (/) I fired up crowd and then went to the http://localhost:8095 URL to start the configuration. I input the DB connection parameters and it created the DB and took off just fine. I really wanted to run the application on port 80 and 443 as normal applications do so I first tried to change the port numbers that the application ran on. That did not work as those are privileged ports and cannot be controller unless you are root. I did not want to do that, so I will have to do a proxy pass. I had to start up the httpd services (I will need to configure as a service) and then created a new file in /etc/httpd/conf.d called crowd.conf that contained the following: {noformat} # This is the configuration for the proxy pass for the crowd server ProxyRequests Off ProxyPreserveHost On Require all granted ProxyPass /crowd http://auth.mbari.org:8095/crowd ProxyPassReverse /crowd http://auth.mbari.org:8095/crowd Require all granted ProxyPass /openidserver http://auth.mbari.org:8095/openidserver ProxyPassReverse /openidserver http://auth.mbari.org:8095/openidserver Require all granted {noformat} ## (/) This worked for the basic HTTP so I will have to get it working with SSL. ## (/) Something with the openidserver is not working correctly and I suspect I have not done the openidserver install completely or correctly. I read the directions on configuring crowdid and it's connection to the database and restarted the crowd server. That worked, not I have both working of straight HTTP, now I need to get SSL going. # Schedule upgrade date and send all hands several days in advance. # When the day arrives, send all hands announcing JIRA outage. # From the Administrator's page in our existing JIRA, perform a 'Backup Data to XML'. # Login to oceana.mbari.org as root. # Shutdown JIRA # Create a tar.gz of the /opt/atlassian-jira-enterprise-3.12.1-standalone directory # Clean up the /data/jira_3_12/backups directory by deleting all but maybe the last 5 backups. # Create a tar.gz of the JIRA home directory on ocean.mbari.org which is located at /data/jira_3_12 # scp both tar.gz files to bugs.mbari.org # login to bugs.mbari.org # Unpack the home directory tar to /data/jira # Run the installer as root (this might need IS help or sudo privs). Note that we usually install the application to /opt # Run the JIRA Configuration tool to set the jira.home to the /data/jira location # Connect to JIRA_Temp database on Solstice2 (.... more to do here, see Atlassian docs) # Migrate existing configuration over to new JIRA (I need to add more here as we added Crowd). # Start JIRA # Import backed up XML # Perform post upgrades checks and tests *Need to document steps for 4.4.5->6.X*]]> 27558040 13959414 13926652 27590807 4.4: [https://confluence.atlassian.com/display/JIRA044/Migrating+JIRA+to+Another+Server] ## The JIRA configuration tool: [https://confluence.atlassian.com/display/JIRA044/Using+the+JIRA+Configuration+Tool] h5. Steps # (/) Create new VM named bugs.mbari.org in the DMZ # (/) Have Neil create database Jira_Temp on solstice2.shore.mbari.org # (/) Have Neil create database Jira on solstice2.shore.mbari.org # (/) Have Pat install Java 7 on bugs.shore.mbari.org # (/) Have Pete plumb holes through firewall so processes on bugs.mbari.org can get to Solstice2 # (/) Have Pat create DB_Collaboration account on bugs so it can run JIRA under that account and it can connect to solstice2 using that NT Domain account. # (/) Upgrade license on Atlassian site # (/) Log into bugs.shore.mbari.org # (/) Download 3.13.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 4.4.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 5.2.11 standalone Linux 64 bit tar.gz (not sure this version is necessary, but at least I have it) # (/) Unzip and untar the file to /opt # (/) Download latest JIRA (6.4.7 as of this writing). # (/) Unzip and untar it to /opt # Performed Test Upgrade ## (/) In order to export the current stuff in JIRA, I had to shut off access so people could not change the data while I was backing it up. ## (/) I ssh'd to oceana.mbari.org as root and edited the /opt/jira/conf/server.xml file and commented out the Connector section that had the port of 8010 to shut it off from the normal serving route. ## (/) I uncommented the 8082 port connector and the 8443 port connector so that I could still get to the server. ## (/) I stopped and started the JIRA server and in the log file I got a "keystore was tampered with..." which is not surprising. ## (/) I could then browser over to http://oceana.mbari.org:8082/jira ## (/) Then through the Administration console, I did an XML backup ## (/) I then created a tar of all the attachments in the /data/jira_3_12/attachments directory ## (/) I moved both the XML and tar files to the /root/jira-upgrade directory ## (/) I then reversed the changes to the server.xml file and shut down JIRA ## (/) I left it down during the next steps in case it went so well, I could just point people to the new server (yeah, right). ## (/) I then browsed to the crowd server on oceana and add a new application using: ### URL: http://bugs.mbari.org/jira3135 ### IP: 134.89.2.29 ### Name: JIRA3135 ### Password: (ask Kevin) :) ## (/) On bugs, I made a copy of the JIRA 3.13.5 download in the /opt directory and unzipped and untarred it. ## (/) In order to configure the crowd connection I did the following: ### (/) I scp'd the /opt/crowd/client/crowd-integration-client-1.6.jar file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I removed the existing 1.6.1 crowd client jar from the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I scp'd the /opt/crowd/client/conf/crowd.properties file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I scp'd the /opt/crowd/client/conf/crowd-ehcache.xml file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I edited the crowd.properties file on bugs to look like: {noformat} application.name JIRA3135 application.password (ask Kevin) application.login.url http://oceana.mbari.org:8095/crowd/console/ crowd.server.url http://oceana.mbari.org:8095/crowd/services/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 0 session.lastvalidation session.lastvalidation {noformat} ### (/) I edited the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/osuser.xml file to comment out the current authentication mechanism and then uncomment the crowd one. ## (/) I then edited the /opt/atlassian-jira-standalone-3.13.5/conf/server/xml file and configured the database connection to the Jira_Temp database on Solstice2. I looked like this: {noformat} {noformat} ## (/) Edit the /opt/atlassian/jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/entityengine.xml and changed it from 'hsql' to 'mssql' and delete the line with "PUBLIC" in it per the instructions in the comments in that file. ## (/) I edited the /etc/httpd/conf/httpd.conf file and created a proxy pass at the bottom of the file to point a normal URL to the default port 8080 for JIRA: {noformat} # Proxy Pass for JIRA ProxyPass http://bugs.mbari.org:8080 ProxyPassReverse http://bugs.mbari.org:8080 {noformat} ## (/) I restarted Apache ## (/) I scp'd the jtds driver from oceana to the /opt/atlassian-jira-standalone-3.13.5/common/lib directory (you could down from the internet) ## (/) I then went to the /opt/atlassian-jira-standalone-3.13.5/ directory and ran './bin/startup.sh'. From the log file, I could tell things were hanging. After some troubleshooting I am wondering if the local firewall is preventing the application to get access to the database on solstice2. I can telnet to port 1433, but I can't browse to the base http://bugs.mbari.org from anywhere but the local web browser. I have submitted a ticket. ## (/) I restarted the old JIRA with my hopes dashed :(. ## (/) Pat disabled the firewall on bugs.mbari.org but it still hung trying to connect to solstice2.shore.mbari.org. That is really, really perplexing. Neil mentioned that solstice2 is using Kerberos and solstice is not. Checking with the JTDS docs, version 1.3.1 of the driver added kerberos support, so I downloaded that driver and added the 'userKerberos=true' property to the URL in the server.xml file and restarted. Got an error about no credentials, so added user and password properties to the URL. Nope, no luck. Never did figure this one out, but I had Pat pull the VM inside the firewall and after some thrash it worked. Well, it sort of worked ... sigh. It turns out I had downloaded the standard version instead of the enterprise version. I need to redo this work ... grrr. ## (/) I deleted all the tables in the Jira_Temp database and removed the /data/jira3135/indexes directory (and recreated). ## (/) I downloaded the enterprise version of the 3.13.5 server. I made a copy in the /opt directory and unzipped and untarred the file. ## (/) I went back to crowd and edited the application to change the properties to: ### URL: http://bugs.shore.mbari.org:8080 ### IP: 134.89.12.31 ### Name: jira3135 ### Password: (ask Kevin) :) ## (/) I then repeated the steps above to get the server up and running with the following differences: ### The server name is now bugs.shore.mbari.org ### The paths given above are a little different in that they no longer say "standard" but say "enterprise" ### I deleted the proxy pass as it seemed to have issues before and this is only temporary anyway. ## (/) I then browsed to http://bugs.shore.mbari.org:8080 ## (/) It took me to the start up page and at the top was the option to 'import your existing data'. Seemed too good not to try. I clicked on the link. It asked me for the backup file location and the location where the indexes would be stored. ## (/) I copied the XML zip file and the attachments tar file to the /data/original directory. ## (/) I created the /data/jira3135/indexes and used those directories ... it fired off the import and I waited. ## (/) I tailed the log file to watch the import. Holy crap, it worked!!! I could log in and everything! I copied the results from the log file here for posterity sake: {noformat} 2015-07-22 20:55:45,156 http-8080-Processor22 INFO [jira.action.admin.DataImport] Running data import 2015-07-22 20:55:45,179 http-8080-Processor22 INFO [jira.action.admin.DataImport] Importing data.. 2015-07-22 20:55:45,186 http-8080-Processor22 INFO [jira.action.admin.DataImport] Start parsing XML with SAX Parser 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] XML successfully parsed 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] Removing all entries from the database. 2015-07-22 20:56:24,593 http-8080-Processor22 INFO [jira.action.admin.DataImport] All entries removed. 2015-07-22 20:56:24,594 http-8080-Processor22 INFO [jira.action.admin.DataImport] Started storing 410414 Generic Values 2015-07-22 21:01:51,967 http-8080-Processor22 INFO [jira.action.admin.DataImport] Finished storing Generic Values 2015-07-22 21:01:52,329 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:52,361 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:54,683 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLink' to module 'jira.user.format:profile-link-user-format'. 2015-07-22 21:01:54,724 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullName' to module 'jira.user.format:full-name-user-format'. 2015-07-22 21:01:54,773 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkSearcher' to module 'jira.user.format:profile-link-searcher-user-format'. 2015-07-22 21:01:54,784 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkExternal' to module 'jira.user.format:profile-link-external-user-format'. 2015-07-22 21:01:54,795 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkActionHeader' to module 'jira.user.format:profile-link-action-header-user-format'. 2015-07-22 21:01:54,807 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullProfile' to module 'jira.user.format:full-profile-user-format'. 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/comments 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/issues 2015-07-22 21:01:55,641 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/plugins 2015-07-22 21:01:55,867 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:01:55,871 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/issues does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:55,873 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/comments does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,033 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,257 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,889 http-8080-Processor22 ERROR [atlassian.jira.upgrade.ConsistencyCheckImpl] Attachments are turned on, but attachment path [/data/jira_3_12/attachments] invalid - disabling attachments 2015-07-22 21:02:13,904 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Detected that an upgrade is needed; existing data at build 299 2015-07-22 21:02:13,907 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Doing Upgrade... 2015-07-22 21:02:13,915 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value' succeeded 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 317 2015-07-22 21:02:13,944 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite filters - make each filter a favourite of its owner. 2015-07-22 21:02:17,822 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build319] Could not find author 'fpy' for filter with id '10040' 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite filters - make each filter a favourite of its owner.' succeeded 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 319 2015-07-22 21:02:17,995 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise Share Permissions. Move old shares to new shares. 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise Share Permissions. Move old shares to new shares.' succeeded 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 321 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Migrating the old JIRA UI colors to the new JIRA 3.13 colors 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build322] Custom color detected for jira.lf.menu.bgcolour : #336699 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Migrating the old JIRA UI colors to the new JIRA 3.13 colors' succeeded 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 322 2015-07-22 21:02:18,025 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite dashboards - make each dashboard a favourite of its owner. 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'cmcgann' for dashboard with id '10030' 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'fpy' for dashboard with id '10060' 2015-07-22 21:02:18,423 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'kanna' for dashboard with id '10040' 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite dashboards - make each dashboard a favourite of its owner.' succeeded 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 325 2015-07-22 21:02:18,625 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Reindexing all data in JIRA to include Favourites. 2015-07-22 21:02:18,648 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All starting... 2015-07-22 21:02:18,650 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 0% complete. Current index: Issue 2015-07-22 21:02:18,654 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:02:18,809 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 1% complete. Current index: Issue 2015-07-22 21:02:18,855 indexerPool-2-thread-10 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 2% complete. Current index: Issue 2015-07-22 21:02:18,899 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 3% complete. Current index: Issue 2015-07-22 21:02:18,945 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 4% complete. Current index: Issue 2015-07-22 21:02:19,012 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 5% complete. Current index: Issue . . . 2015-07-22 21:02:26,164 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 95% complete. Current index: Issue 2015-07-22 21:02:26,232 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 96% complete. Current index: Issue 2015-07-22 21:02:26,316 indexerPool-2-thread-9 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 97% complete. Current index: Issue 2015-07-22 21:02:26,771 indexerPool-2-thread-3 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: Issue 2015-07-22 21:02:27,261 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 8607ms. Indexer: DefaultIndexManager: paths: [/data/jira3135/indexes/issues, /data/jira3135/indexes/comments] 2015-07-22 21:02:27,263 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: SearchRequest 2015-07-22 21:02:27,268 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,293 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: SearchRequest 2015-07-22 21:02:27,308 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: PortalPage 2015-07-22 21:02:27,312 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,377 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: PortalPage 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 115ms. Indexer: SharedEntityIndexManager: paths: [/data/jira3135/indexes/entities/portalpage, /data/jira3135/indexes/entities/searchrequest] 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All complete. Total time: 8722ms. 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Reindexing all data in JIRA to include Favourites.' succeeded 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 326 2015-07-22 21:02:27,397 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade succeeded! Setting data build number to 360 2015-07-22 21:02:27,469 JiraQuartzScheduler_Worker-0 WARN [service.services.export.ExportService] Backup directory /data/jira_3_12/backup does not exist {noformat} {warning:title=Paths} It appears that the upgraded JIRA will still look for the attachments and the backup locations in the original places. So I created /data/jira_3_12/backup and untarred the original attachments to /data/jira_3_12 and then everything worked (including attachements) in the new JIRA. {warning} ## (/) I then used the upgraded JIRA to generate a new XML backup and stored it in /data/original/3.13.5 along with another tar of the files in /data/jira_3_12/attachments. ## (/) I then shutdown the JIRA server. *I should be ready to move on to version 4 upgrade WHEW* ## So, before moving on, I decided that it would be a really good idea to spin up a new Crowd instance to get rid of the :8443 in the URL and to move off of RedHat per IS requests. I have a ticket in for a new VM and a new database to try to get this going. I am waiting on that before moving on. ## (/) Pat created the VM and Neil created the database. ## (/) I logged into auth.mbari.org (name of the VM) and downloaded crowd which I unzipped to the /opt directory ## (/) I then created a /data/crowd directory and gave my account permissions on it and then edited the /opt/atlassian..../crowd-webapp/WEB-INF/classes/crowd-init.properties file to set that as the crowd home directory. ## (/) I fired up crowd and then went to the http://localhost:8095 URL to start the configuration. I input the DB connection parameters and it created the DB and took off just fine. I really wanted to run the application on port 80 and 443 as normal applications do so I first tried to change the port numbers that the application ran on. That did not work as those are privileged ports and cannot be controller unless you are root. I did not want to do that, so I will have to do a proxy pass. I had to start up the httpd services (I will need to configure as a service) and then created a new file in /etc/httpd/conf.d called crowd.conf that contained the following: {noformat} # This is the configuration for the proxy pass for the crowd server ProxyRequests Off ProxyPreserveHost On Require all granted ProxyPass /crowd http://auth.mbari.org:8095/crowd ProxyPassReverse /crowd http://auth.mbari.org:8095/crowd Require all granted ProxyPass /openidserver http://auth.mbari.org:8095/openidserver ProxyPassReverse /openidserver http://auth.mbari.org:8095/openidserver Require all granted {noformat} ## (/) This worked for the basic HTTP so I will have to get it working with SSL. ## (/) Something with the openidserver is not working correctly and I suspect I have not done the openidserver install completely or correctly. I read the directions on configuring crowdid and it's connection to the database and restarted the crowd server. That worked, not I have both working of straight HTTP, now I need to get SSL going. ## (/) The first step was to actually enable the 8443 port on tomcat. That consisted of editing the server.xml file per the instructions at Atlassian on Configuring Crowd to Work with SSL # Schedule upgrade date and send all hands several days in advance. # When the day arrives, send all hands announcing JIRA outage. # From the Administrator's page in our existing JIRA, perform a 'Backup Data to XML'. # Login to oceana.mbari.org as root. # Shutdown JIRA # Create a tar.gz of the /opt/atlassian-jira-enterprise-3.12.1-standalone directory # Clean up the /data/jira_3_12/backups directory by deleting all but maybe the last 5 backups. # Create a tar.gz of the JIRA home directory on ocean.mbari.org which is located at /data/jira_3_12 # scp both tar.gz files to bugs.mbari.org # login to bugs.mbari.org # Unpack the home directory tar to /data/jira # Run the installer as root (this might need IS help or sudo privs). Note that we usually install the application to /opt # Run the JIRA Configuration tool to set the jira.home to the /data/jira location # Connect to JIRA_Temp database on Solstice2 (.... more to do here, see Atlassian docs) # Migrate existing configuration over to new JIRA (I need to add more here as we added Crowd). # Start JIRA # Import backed up XML # Perform post upgrades checks and tests *Need to document steps for 4.4.5->6.X*]]> 27558042 13959416 13926654 27590809 4.4: [https://confluence.atlassian.com/display/JIRA044/Migrating+JIRA+to+Another+Server] ## The JIRA configuration tool: [https://confluence.atlassian.com/display/JIRA044/Using+the+JIRA+Configuration+Tool] h5. Steps # (/) Create new VM named bugs.mbari.org in the DMZ # (/) Have Neil create database Jira_Temp on solstice2.shore.mbari.org # (/) Have Neil create database Jira on solstice2.shore.mbari.org # (/) Have Pat install Java 7 on bugs.shore.mbari.org # (/) Have Pete plumb holes through firewall so processes on bugs.mbari.org can get to Solstice2 # (/) Have Pat create DB_Collaboration account on bugs so it can run JIRA under that account and it can connect to solstice2 using that NT Domain account. # (/) Upgrade license on Atlassian site # (/) Log into bugs.shore.mbari.org # (/) Download 3.13.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 4.4.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 5.2.11 standalone Linux 64 bit tar.gz (not sure this version is necessary, but at least I have it) # (/) Unzip and untar the file to /opt # (/) Download latest JIRA (6.4.7 as of this writing). # (/) Unzip and untar it to /opt # Performed Test Upgrade ## (/) In order to export the current stuff in JIRA, I had to shut off access so people could not change the data while I was backing it up. ## (/) I ssh'd to oceana.mbari.org as root and edited the /opt/jira/conf/server.xml file and commented out the Connector section that had the port of 8010 to shut it off from the normal serving route. ## (/) I uncommented the 8082 port connector and the 8443 port connector so that I could still get to the server. ## (/) I stopped and started the JIRA server and in the log file I got a "keystore was tampered with..." which is not surprising. ## (/) I could then browser over to http://oceana.mbari.org:8082/jira ## (/) Then through the Administration console, I did an XML backup ## (/) I then created a tar of all the attachments in the /data/jira_3_12/attachments directory ## (/) I moved both the XML and tar files to the /root/jira-upgrade directory ## (/) I then reversed the changes to the server.xml file and shut down JIRA ## (/) I left it down during the next steps in case it went so well, I could just point people to the new server (yeah, right). ## (/) I then browsed to the crowd server on oceana and add a new application using: ### URL: http://bugs.mbari.org/jira3135 ### IP: 134.89.2.29 ### Name: JIRA3135 ### Password: (ask Kevin) :) ## (/) On bugs, I made a copy of the JIRA 3.13.5 download in the /opt directory and unzipped and untarred it. ## (/) In order to configure the crowd connection I did the following: ### (/) I scp'd the /opt/crowd/client/crowd-integration-client-1.6.jar file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I removed the existing 1.6.1 crowd client jar from the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I scp'd the /opt/crowd/client/conf/crowd.properties file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I scp'd the /opt/crowd/client/conf/crowd-ehcache.xml file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I edited the crowd.properties file on bugs to look like: {noformat} application.name JIRA3135 application.password (ask Kevin) application.login.url http://oceana.mbari.org:8095/crowd/console/ crowd.server.url http://oceana.mbari.org:8095/crowd/services/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 0 session.lastvalidation session.lastvalidation {noformat} ### (/) I edited the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/osuser.xml file to comment out the current authentication mechanism and then uncomment the crowd one. ## (/) I then edited the /opt/atlassian-jira-standalone-3.13.5/conf/server/xml file and configured the database connection to the Jira_Temp database on Solstice2. I looked like this: {noformat} {noformat} ## (/) Edit the /opt/atlassian/jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/entityengine.xml and changed it from 'hsql' to 'mssql' and delete the line with "PUBLIC" in it per the instructions in the comments in that file. ## (/) I edited the /etc/httpd/conf/httpd.conf file and created a proxy pass at the bottom of the file to point a normal URL to the default port 8080 for JIRA: {noformat} # Proxy Pass for JIRA ProxyPass http://bugs.mbari.org:8080 ProxyPassReverse http://bugs.mbari.org:8080 {noformat} ## (/) I restarted Apache ## (/) I scp'd the jtds driver from oceana to the /opt/atlassian-jira-standalone-3.13.5/common/lib directory (you could down from the internet) ## (/) I then went to the /opt/atlassian-jira-standalone-3.13.5/ directory and ran './bin/startup.sh'. From the log file, I could tell things were hanging. After some troubleshooting I am wondering if the local firewall is preventing the application to get access to the database on solstice2. I can telnet to port 1433, but I can't browse to the base http://bugs.mbari.org from anywhere but the local web browser. I have submitted a ticket. ## (/) I restarted the old JIRA with my hopes dashed :(. ## (/) Pat disabled the firewall on bugs.mbari.org but it still hung trying to connect to solstice2.shore.mbari.org. That is really, really perplexing. Neil mentioned that solstice2 is using Kerberos and solstice is not. Checking with the JTDS docs, version 1.3.1 of the driver added kerberos support, so I downloaded that driver and added the 'userKerberos=true' property to the URL in the server.xml file and restarted. Got an error about no credentials, so added user and password properties to the URL. Nope, no luck. Never did figure this one out, but I had Pat pull the VM inside the firewall and after some thrash it worked. Well, it sort of worked ... sigh. It turns out I had downloaded the standard version instead of the enterprise version. I need to redo this work ... grrr. ## (/) I deleted all the tables in the Jira_Temp database and removed the /data/jira3135/indexes directory (and recreated). ## (/) I downloaded the enterprise version of the 3.13.5 server. I made a copy in the /opt directory and unzipped and untarred the file. ## (/) I went back to crowd and edited the application to change the properties to: ### URL: http://bugs.shore.mbari.org:8080 ### IP: 134.89.12.31 ### Name: jira3135 ### Password: (ask Kevin) :) ## (/) I then repeated the steps above to get the server up and running with the following differences: ### The server name is now bugs.shore.mbari.org ### The paths given above are a little different in that they no longer say "standard" but say "enterprise" ### I deleted the proxy pass as it seemed to have issues before and this is only temporary anyway. ## (/) I then browsed to http://bugs.shore.mbari.org:8080 ## (/) It took me to the start up page and at the top was the option to 'import your existing data'. Seemed too good not to try. I clicked on the link. It asked me for the backup file location and the location where the indexes would be stored. ## (/) I copied the XML zip file and the attachments tar file to the /data/original directory. ## (/) I created the /data/jira3135/indexes and used those directories ... it fired off the import and I waited. ## (/) I tailed the log file to watch the import. Holy crap, it worked!!! I could log in and everything! I copied the results from the log file here for posterity sake: {noformat} 2015-07-22 20:55:45,156 http-8080-Processor22 INFO [jira.action.admin.DataImport] Running data import 2015-07-22 20:55:45,179 http-8080-Processor22 INFO [jira.action.admin.DataImport] Importing data.. 2015-07-22 20:55:45,186 http-8080-Processor22 INFO [jira.action.admin.DataImport] Start parsing XML with SAX Parser 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] XML successfully parsed 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] Removing all entries from the database. 2015-07-22 20:56:24,593 http-8080-Processor22 INFO [jira.action.admin.DataImport] All entries removed. 2015-07-22 20:56:24,594 http-8080-Processor22 INFO [jira.action.admin.DataImport] Started storing 410414 Generic Values 2015-07-22 21:01:51,967 http-8080-Processor22 INFO [jira.action.admin.DataImport] Finished storing Generic Values 2015-07-22 21:01:52,329 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:52,361 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:54,683 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLink' to module 'jira.user.format:profile-link-user-format'. 2015-07-22 21:01:54,724 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullName' to module 'jira.user.format:full-name-user-format'. 2015-07-22 21:01:54,773 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkSearcher' to module 'jira.user.format:profile-link-searcher-user-format'. 2015-07-22 21:01:54,784 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkExternal' to module 'jira.user.format:profile-link-external-user-format'. 2015-07-22 21:01:54,795 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkActionHeader' to module 'jira.user.format:profile-link-action-header-user-format'. 2015-07-22 21:01:54,807 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullProfile' to module 'jira.user.format:full-profile-user-format'. 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/comments 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/issues 2015-07-22 21:01:55,641 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/plugins 2015-07-22 21:01:55,867 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:01:55,871 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/issues does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:55,873 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/comments does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,033 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,257 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,889 http-8080-Processor22 ERROR [atlassian.jira.upgrade.ConsistencyCheckImpl] Attachments are turned on, but attachment path [/data/jira_3_12/attachments] invalid - disabling attachments 2015-07-22 21:02:13,904 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Detected that an upgrade is needed; existing data at build 299 2015-07-22 21:02:13,907 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Doing Upgrade... 2015-07-22 21:02:13,915 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value' succeeded 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 317 2015-07-22 21:02:13,944 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite filters - make each filter a favourite of its owner. 2015-07-22 21:02:17,822 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build319] Could not find author 'fpy' for filter with id '10040' 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite filters - make each filter a favourite of its owner.' succeeded 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 319 2015-07-22 21:02:17,995 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise Share Permissions. Move old shares to new shares. 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise Share Permissions. Move old shares to new shares.' succeeded 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 321 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Migrating the old JIRA UI colors to the new JIRA 3.13 colors 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build322] Custom color detected for jira.lf.menu.bgcolour : #336699 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Migrating the old JIRA UI colors to the new JIRA 3.13 colors' succeeded 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 322 2015-07-22 21:02:18,025 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite dashboards - make each dashboard a favourite of its owner. 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'cmcgann' for dashboard with id '10030' 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'fpy' for dashboard with id '10060' 2015-07-22 21:02:18,423 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'kanna' for dashboard with id '10040' 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite dashboards - make each dashboard a favourite of its owner.' succeeded 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 325 2015-07-22 21:02:18,625 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Reindexing all data in JIRA to include Favourites. 2015-07-22 21:02:18,648 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All starting... 2015-07-22 21:02:18,650 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 0% complete. Current index: Issue 2015-07-22 21:02:18,654 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:02:18,809 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 1% complete. Current index: Issue 2015-07-22 21:02:18,855 indexerPool-2-thread-10 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 2% complete. Current index: Issue 2015-07-22 21:02:18,899 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 3% complete. Current index: Issue 2015-07-22 21:02:18,945 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 4% complete. Current index: Issue 2015-07-22 21:02:19,012 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 5% complete. Current index: Issue . . . 2015-07-22 21:02:26,164 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 95% complete. Current index: Issue 2015-07-22 21:02:26,232 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 96% complete. Current index: Issue 2015-07-22 21:02:26,316 indexerPool-2-thread-9 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 97% complete. Current index: Issue 2015-07-22 21:02:26,771 indexerPool-2-thread-3 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: Issue 2015-07-22 21:02:27,261 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 8607ms. Indexer: DefaultIndexManager: paths: [/data/jira3135/indexes/issues, /data/jira3135/indexes/comments] 2015-07-22 21:02:27,263 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: SearchRequest 2015-07-22 21:02:27,268 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,293 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: SearchRequest 2015-07-22 21:02:27,308 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: PortalPage 2015-07-22 21:02:27,312 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,377 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: PortalPage 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 115ms. Indexer: SharedEntityIndexManager: paths: [/data/jira3135/indexes/entities/portalpage, /data/jira3135/indexes/entities/searchrequest] 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All complete. Total time: 8722ms. 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Reindexing all data in JIRA to include Favourites.' succeeded 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 326 2015-07-22 21:02:27,397 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade succeeded! Setting data build number to 360 2015-07-22 21:02:27,469 JiraQuartzScheduler_Worker-0 WARN [service.services.export.ExportService] Backup directory /data/jira_3_12/backup does not exist {noformat} {warning:title=Paths} It appears that the upgraded JIRA will still look for the attachments and the backup locations in the original places. So I created /data/jira_3_12/backup and untarred the original attachments to /data/jira_3_12 and then everything worked (including attachements) in the new JIRA. {warning} ## (/) I then used the upgraded JIRA to generate a new XML backup and stored it in /data/original/3.13.5 along with another tar of the files in /data/jira_3_12/attachments. ## (/) I then shutdown the JIRA server. *I should be ready to move on to version 4 upgrade WHEW* ## So, before moving on, I decided that it would be a really good idea to spin up a new Crowd instance to get rid of the :8443 in the URL and to move off of RedHat per IS requests. I have a ticket in for a new VM and a new database to try to get this going. I am waiting on that before moving on. ## (/) Pat created the VM and Neil created the database. ## (/) I logged into auth.mbari.org (name of the VM) and downloaded crowd which I unzipped to the /opt directory ## (/) I then created a /data/crowd directory and gave my account permissions on it and then edited the /opt/atlassian..../crowd-webapp/WEB-INF/classes/crowd-init.properties file to set that as the crowd home directory. ## (/) I fired up crowd and then went to the http://localhost:8095 URL to start the configuration. I input the DB connection parameters and it created the DB and took off just fine. I really wanted to run the application on port 80 and 443 as normal applications do so I first tried to change the port numbers that the application ran on. That did not work as those are privileged ports and cannot be controller unless you are root. I did not want to do that, so I will have to do a proxy pass. I had to start up the httpd services (I will need to configure as a service) and then created a new file in /etc/httpd/conf.d called crowd.conf that contained the following: {noformat} # This is the configuration for the proxy pass for the crowd server ProxyRequests Off ProxyPreserveHost On Require all granted ProxyPass /crowd http://auth.mbari.org:8095/crowd ProxyPassReverse /crowd http://auth.mbari.org:8095/crowd Require all granted ProxyPass /openidserver http://auth.mbari.org:8095/openidserver ProxyPassReverse /openidserver http://auth.mbari.org:8095/openidserver Require all granted {noformat} ## (/) This worked for the basic HTTP so I will have to get it working with SSL. ## (/) Something with the openidserver is not working correctly and I suspect I have not done the openidserver install completely or correctly. I read the directions on configuring crowdid and it's connection to the database and restarted the crowd server. That worked, not I have both working of straight HTTP, now I need to get SSL going. ## (/) The first step was to actually enable the 8443 port on tomcat. That consisted of editing the server.xml file per the instructions at Atlassian on Configuring Crowd to Work with SSL. I wasn't able to fill out the correct values until I did the next step ## (/) To get started, I had to create a self signed certificate while waiting for a real cert. I first created a self-signed key using the password 'sec4auth': {noformat} [kgomes@auth ~]$ /usr/java/jdk1.8.0_51/bin/keytool -genkey -alias tomcat -keyalg RSA Enter keystore password: Re-enter new password: What is your first and last name? [Unknown]: localhost What is the name of your organizational unit? [Unknown]: ENG What is the name of your organization? [Unknown]: MBARI What is the name of your City or Locality? [Unknown]: Moss Landing What is the name of your State or Province? [Unknown]: CA What is the two-letter country code for this unit? [Unknown]: US Is CN=localhost, OU=ENG, O=MBARI, L=Moss Landing, ST=CA, C=US correct? [no]: yes Enter key password for (RETURN if same as keystore password): {noformat} ## (/) I then exported the key to a file: {noformat} /usr/java/jdk1.8.0_51/bin/keytool -export -alias tomcat -file tomcat.cert {noformat} ## (/) Next, I had to import the key into the JRE keystore, so I first changed ownership on the file: {noformat} /usr/java/jdk1.8.0_51/jre/lib/security/cacerts {noformat} ## (/) Then I ran {noformat} /usr/java/jdk1.8.0_51/bin/keytool -import -alias tomcat -file tomcat.cert -keystore /usr/java/jdk1.8.0_51/jre/lib/security/cacerts {noformat} # Schedule upgrade date and send all hands several days in advance. # When the day arrives, send all hands announcing JIRA outage. # From the Administrator's page in our existing JIRA, perform a 'Backup Data to XML'. # Login to oceana.mbari.org as root. # Shutdown JIRA # Create a tar.gz of the /opt/atlassian-jira-enterprise-3.12.1-standalone directory # Clean up the /data/jira_3_12/backups directory by deleting all but maybe the last 5 backups. # Create a tar.gz of the JIRA home directory on ocean.mbari.org which is located at /data/jira_3_12 # scp both tar.gz files to bugs.mbari.org # login to bugs.mbari.org # Unpack the home directory tar to /data/jira # Run the installer as root (this might need IS help or sudo privs). Note that we usually install the application to /opt # Run the JIRA Configuration tool to set the jira.home to the /data/jira location # Connect to JIRA_Temp database on Solstice2 (.... more to do here, see Atlassian docs) # Migrate existing configuration over to new JIRA (I need to add more here as we added Crowd). # Start JIRA # Import backed up XML # Perform post upgrades checks and tests *Need to document steps for 4.4.5->6.X*]]> 27558044 13959403 13926641 13959406 13926644 13959405 13926643 27590797 4.4: [https://confluence.atlassian.com/display/JIRA044/Migrating+JIRA+to+Another+Server] ## The JIRA configuration tool: [https://confluence.atlassian.com/display/JIRA044/Using+the+JIRA+Configuration+Tool] h5. Steps # (/) Create new VM named bugs.mbari.org in the DMZ # (/) Have Neil create database Jira_Temp on solstice2.shore.mbari.org # (/) Have Neil create database Jira on solstice2.shore.mbari.org # (/) Have Pat install Java 7 on bugs.shore.mbari.org # (/) Have Pete plumb holes through firewall so processes on bugs.mbari.org can get to Solstice2 # (/) Have Pat create DB_Collaboration account on bugs so it can run JIRA under that account and it can connect to solstice2 using that NT Domain account. # (/) Upgrade license on Atlassian site # (/) Log into bugs.shore.mbari.org # (/) Download 3.13.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 4.4.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 5.2.11 standalone Linux 64 bit tar.gz (not sure this version is necessary, but at least I have it) # (/) Unzip and untar the file to /opt # (/) Download latest JIRA (6.4.7 as of this writing). # (/) Unzip and untar it to /opt # Performed Test Upgrade ## (/) In order to export the current stuff in JIRA, I had to shut off access so people could not change the data while I was backing it up. ## (/) I ssh'd to oceana.mbari.org as root and edited the /opt/jira/conf/server.xml file and commented out the Connector section that had the port of 8010 to shut it off from the normal serving route. ## (/) I uncommented the 8082 port connector and the 8443 port connector so that I could still get to the server. ## (/) I stopped and started the JIRA server and in the log file I got a "keystore was tampered with..." which is not surprising. ## (/) I could then browser over to http://oceana.mbari.org:8082/jira ## (/) Then through the Administration console, I did an XML backup ## (/) I then created a tar of all the attachments in the /data/jira_3_12/attachments directory ## (/) I moved both the XML and tar files to the /root/jira-upgrade directory ## (/) I then reversed the changes to the server.xml file and shut down JIRA ## (/) I left it down during the next steps in case it went so well, I could just point people to the new server (yeah, right). ## (/) I then browsed to the crowd server on oceana and add a new application using: ### URL: http://bugs.mbari.org/jira3135 ### IP: 134.89.2.29 ### Name: JIRA3135 ### Password: (ask Kevin) :) ## (/) On bugs, I made a copy of the JIRA 3.13.5 download in the /opt directory and unzipped and untarred it. ## (/) In order to configure the crowd connection I did the following: ### (/) I scp'd the /opt/crowd/client/crowd-integration-client-1.6.jar file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I removed the existing 1.6.1 crowd client jar from the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I scp'd the /opt/crowd/client/conf/crowd.properties file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I scp'd the /opt/crowd/client/conf/crowd-ehcache.xml file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I edited the crowd.properties file on bugs to look like: {noformat} application.name JIRA3135 application.password (ask Kevin) application.login.url http://oceana.mbari.org:8095/crowd/console/ crowd.server.url http://oceana.mbari.org:8095/crowd/services/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 0 session.lastvalidation session.lastvalidation {noformat} ### (/) I edited the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/osuser.xml file to comment out the current authentication mechanism and then uncomment the crowd one. ## (/) I then edited the /opt/atlassian-jira-standalone-3.13.5/conf/server/xml file and configured the database connection to the Jira_Temp database on Solstice2. I looked like this: {noformat} {noformat} ## (/) Edit the /opt/atlassian/jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/entityengine.xml and changed it from 'hsql' to 'mssql' and delete the line with "PUBLIC" in it per the instructions in the comments in that file. ## (/) I edited the /etc/httpd/conf/httpd.conf file and created a proxy pass at the bottom of the file to point a normal URL to the default port 8080 for JIRA: {noformat} # Proxy Pass for JIRA ProxyPass http://bugs.mbari.org:8080 ProxyPassReverse http://bugs.mbari.org:8080 {noformat} ## (/) I restarted Apache ## (/) I scp'd the jtds driver from oceana to the /opt/atlassian-jira-standalone-3.13.5/common/lib directory (you could down from the internet) ## (/) I then went to the /opt/atlassian-jira-standalone-3.13.5/ directory and ran './bin/startup.sh'. From the log file, I could tell things were hanging. After some troubleshooting I am wondering if the local firewall is preventing the application to get access to the database on solstice2. I can telnet to port 1433, but I can't browse to the base http://bugs.mbari.org from anywhere but the local web browser. I have submitted a ticket. ## (/) I restarted the old JIRA with my hopes dashed :(. ## (/) Pat disabled the firewall on bugs.mbari.org but it still hung trying to connect to solstice2.shore.mbari.org. That is really, really perplexing. Neil mentioned that solstice2 is using Kerberos and solstice is not. Checking with the JTDS docs, version 1.3.1 of the driver added kerberos support, so I downloaded that driver and added the 'userKerberos=true' property to the URL in the server.xml file and restarted. Got an error about no credentials, so added user and password properties to the URL. Nope, no luck. Never did figure this one out, but I had Pat pull the VM inside the firewall and after some thrash it worked. Well, it sort of worked ... sigh. It turns out I had downloaded the standard version instead of the enterprise version. I need to redo this work ... grrr. ## (/) I deleted all the tables in the Jira_Temp database and removed the /data/jira3135/indexes directory (and recreated). ## (/) I downloaded the enterprise version of the 3.13.5 server. I made a copy in the /opt directory and unzipped and untarred the file. ## (/) I went back to crowd and edited the application to change the properties to: ### URL: http://bugs.shore.mbari.org:8080 ### IP: 134.89.12.31 ### Name: jira3135 ### Password: (ask Kevin) :) ## (/) I then repeated the steps above to get the server up and running with the following differences: ### The server name is now bugs.shore.mbari.org ### The paths given above are a little different in that they no longer say "standard" but say "enterprise" ### I deleted the proxy pass as it seemed to have issues before and this is only temporary anyway. ## (/) I then browsed to http://bugs.shore.mbari.org:8080 ## (/) It took me to the start up page and at the top was the option to 'import your existing data'. Seemed too good not to try. I clicked on the link. It asked me for the backup file location and the location where the indexes would be stored. ## (/) I copied the XML zip file and the attachments tar file to the /data/original directory. ## (/) I created the /data/jira3135/indexes and used those directories ... it fired off the import and I waited. ## (/) I tailed the log file to watch the import. Holy crap, it worked!!! I could log in and everything! I copied the results from the log file here for posterity sake: {noformat} 2015-07-22 20:55:45,156 http-8080-Processor22 INFO [jira.action.admin.DataImport] Running data import 2015-07-22 20:55:45,179 http-8080-Processor22 INFO [jira.action.admin.DataImport] Importing data.. 2015-07-22 20:55:45,186 http-8080-Processor22 INFO [jira.action.admin.DataImport] Start parsing XML with SAX Parser 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] XML successfully parsed 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] Removing all entries from the database. 2015-07-22 20:56:24,593 http-8080-Processor22 INFO [jira.action.admin.DataImport] All entries removed. 2015-07-22 20:56:24,594 http-8080-Processor22 INFO [jira.action.admin.DataImport] Started storing 410414 Generic Values 2015-07-22 21:01:51,967 http-8080-Processor22 INFO [jira.action.admin.DataImport] Finished storing Generic Values 2015-07-22 21:01:52,329 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:52,361 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:54,683 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLink' to module 'jira.user.format:profile-link-user-format'. 2015-07-22 21:01:54,724 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullName' to module 'jira.user.format:full-name-user-format'. 2015-07-22 21:01:54,773 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkSearcher' to module 'jira.user.format:profile-link-searcher-user-format'. 2015-07-22 21:01:54,784 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkExternal' to module 'jira.user.format:profile-link-external-user-format'. 2015-07-22 21:01:54,795 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkActionHeader' to module 'jira.user.format:profile-link-action-header-user-format'. 2015-07-22 21:01:54,807 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullProfile' to module 'jira.user.format:full-profile-user-format'. 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/comments 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/issues 2015-07-22 21:01:55,641 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/plugins 2015-07-22 21:01:55,867 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:01:55,871 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/issues does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:55,873 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/comments does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,033 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,257 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,889 http-8080-Processor22 ERROR [atlassian.jira.upgrade.ConsistencyCheckImpl] Attachments are turned on, but attachment path [/data/jira_3_12/attachments] invalid - disabling attachments 2015-07-22 21:02:13,904 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Detected that an upgrade is needed; existing data at build 299 2015-07-22 21:02:13,907 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Doing Upgrade... 2015-07-22 21:02:13,915 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value' succeeded 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 317 2015-07-22 21:02:13,944 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite filters - make each filter a favourite of its owner. 2015-07-22 21:02:17,822 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build319] Could not find author 'fpy' for filter with id '10040' 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite filters - make each filter a favourite of its owner.' succeeded 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 319 2015-07-22 21:02:17,995 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise Share Permissions. Move old shares to new shares. 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise Share Permissions. Move old shares to new shares.' succeeded 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 321 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Migrating the old JIRA UI colors to the new JIRA 3.13 colors 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build322] Custom color detected for jira.lf.menu.bgcolour : #336699 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Migrating the old JIRA UI colors to the new JIRA 3.13 colors' succeeded 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 322 2015-07-22 21:02:18,025 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite dashboards - make each dashboard a favourite of its owner. 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'cmcgann' for dashboard with id '10030' 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'fpy' for dashboard with id '10060' 2015-07-22 21:02:18,423 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'kanna' for dashboard with id '10040' 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite dashboards - make each dashboard a favourite of its owner.' succeeded 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 325 2015-07-22 21:02:18,625 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Reindexing all data in JIRA to include Favourites. 2015-07-22 21:02:18,648 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All starting... 2015-07-22 21:02:18,650 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 0% complete. Current index: Issue 2015-07-22 21:02:18,654 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:02:18,809 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 1% complete. Current index: Issue 2015-07-22 21:02:18,855 indexerPool-2-thread-10 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 2% complete. Current index: Issue 2015-07-22 21:02:18,899 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 3% complete. Current index: Issue 2015-07-22 21:02:18,945 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 4% complete. Current index: Issue 2015-07-22 21:02:19,012 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 5% complete. Current index: Issue . . . 2015-07-22 21:02:26,164 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 95% complete. Current index: Issue 2015-07-22 21:02:26,232 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 96% complete. Current index: Issue 2015-07-22 21:02:26,316 indexerPool-2-thread-9 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 97% complete. Current index: Issue 2015-07-22 21:02:26,771 indexerPool-2-thread-3 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: Issue 2015-07-22 21:02:27,261 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 8607ms. Indexer: DefaultIndexManager: paths: [/data/jira3135/indexes/issues, /data/jira3135/indexes/comments] 2015-07-22 21:02:27,263 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: SearchRequest 2015-07-22 21:02:27,268 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,293 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: SearchRequest 2015-07-22 21:02:27,308 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: PortalPage 2015-07-22 21:02:27,312 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,377 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: PortalPage 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 115ms. Indexer: SharedEntityIndexManager: paths: [/data/jira3135/indexes/entities/portalpage, /data/jira3135/indexes/entities/searchrequest] 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All complete. Total time: 8722ms. 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Reindexing all data in JIRA to include Favourites.' succeeded 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 326 2015-07-22 21:02:27,397 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade succeeded! Setting data build number to 360 2015-07-22 21:02:27,469 JiraQuartzScheduler_Worker-0 WARN [service.services.export.ExportService] Backup directory /data/jira_3_12/backup does not exist {noformat} {warning:title=Paths} It appears that the upgraded JIRA will still look for the attachments and the backup locations in the original places. So I created /data/jira_3_12/backup and untarred the original attachments to /data/jira_3_12 and then everything worked (including attachements) in the new JIRA. {warning} ## (/) I then used the upgraded JIRA to generate a new XML backup and stored it in /data/original/3.13.5 along with another tar of the files in /data/jira_3_12/attachments. ## (/) I then shutdown the JIRA server. *I should be ready to move on to version 4 upgrade WHEW* ## So, before moving on, I decided that it would be a really good idea to spin up a new Crowd instance to get rid of the :8443 in the URL and to move off of RedHat per IS requests. I have a ticket in for a new VM and a new database to try to get this going. I am waiting on that before moving on. # Schedule upgrade date and send all hands several days in advance. # When the day arrives, send all hands announcing JIRA outage. # From the Administrator's page in our existing JIRA, perform a 'Backup Data to XML'. # Login to oceana.mbari.org as root. # Shutdown JIRA # Create a tar.gz of the /opt/atlassian-jira-enterprise-3.12.1-standalone directory # Clean up the /data/jira_3_12/backups directory by deleting all but maybe the last 5 backups. # Create a tar.gz of the JIRA home directory on ocean.mbari.org which is located at /data/jira_3_12 # scp both tar.gz files to bugs.mbari.org # login to bugs.mbari.org # Unpack the home directory tar to /data/jira # Run the installer as root (this might need IS help or sudo privs). Note that we usually install the application to /opt # Run the JIRA Configuration tool to set the jira.home to the /data/jira location # Connect to JIRA_Temp database on Solstice2 (.... more to do here, see Atlassian docs) # Migrate existing configuration over to new JIRA (I need to add more here as we added Crowd). # Start JIRA # Import backed up XML # Perform post upgrades checks and tests *Need to document steps for 4.4.5->6.X*]]> 27558032 13959408 13926646 27590800 4.4: [https://confluence.atlassian.com/display/JIRA044/Migrating+JIRA+to+Another+Server] ## The JIRA configuration tool: [https://confluence.atlassian.com/display/JIRA044/Using+the+JIRA+Configuration+Tool] h5. Steps # (/) Create new VM named bugs.mbari.org in the DMZ # (/) Have Neil create database Jira_Temp on solstice2.shore.mbari.org # (/) Have Neil create database Jira on solstice2.shore.mbari.org # (/) Have Pat install Java 7 on bugs.shore.mbari.org # (/) Have Pete plumb holes through firewall so processes on bugs.mbari.org can get to Solstice2 # (/) Have Pat create DB_Collaboration account on bugs so it can run JIRA under that account and it can connect to solstice2 using that NT Domain account. # (/) Upgrade license on Atlassian site # (/) Log into bugs.shore.mbari.org # (/) Download 3.13.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 4.4.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 5.2.11 standalone Linux 64 bit tar.gz (not sure this version is necessary, but at least I have it) # (/) Unzip and untar the file to /opt # (/) Download latest JIRA (6.4.7 as of this writing). # (/) Unzip and untar it to /opt # Performed Test Upgrade ## (/) In order to export the current stuff in JIRA, I had to shut off access so people could not change the data while I was backing it up. ## (/) I ssh'd to oceana.mbari.org as root and edited the /opt/jira/conf/server.xml file and commented out the Connector section that had the port of 8010 to shut it off from the normal serving route. ## (/) I uncommented the 8082 port connector and the 8443 port connector so that I could still get to the server. ## (/) I stopped and started the JIRA server and in the log file I got a "keystore was tampered with..." which is not surprising. ## (/) I could then browser over to http://oceana.mbari.org:8082/jira ## (/) Then through the Administration console, I did an XML backup ## (/) I then created a tar of all the attachments in the /data/jira_3_12/attachments directory ## (/) I moved both the XML and tar files to the /root/jira-upgrade directory ## (/) I then reversed the changes to the server.xml file and shut down JIRA ## (/) I left it down during the next steps in case it went so well, I could just point people to the new server (yeah, right). ## (/) I then browsed to the crowd server on oceana and add a new application using: ### URL: http://bugs.mbari.org/jira3135 ### IP: 134.89.2.29 ### Name: JIRA3135 ### Password: (ask Kevin) :) ## (/) On bugs, I made a copy of the JIRA 3.13.5 download in the /opt directory and unzipped and untarred it. ## (/) In order to configure the crowd connection I did the following: ### (/) I scp'd the /opt/crowd/client/crowd-integration-client-1.6.jar file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I removed the existing 1.6.1 crowd client jar from the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I scp'd the /opt/crowd/client/conf/crowd.properties file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I scp'd the /opt/crowd/client/conf/crowd-ehcache.xml file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I edited the crowd.properties file on bugs to look like: {noformat} application.name JIRA3135 application.password (ask Kevin) application.login.url http://oceana.mbari.org:8095/crowd/console/ crowd.server.url http://oceana.mbari.org:8095/crowd/services/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 0 session.lastvalidation session.lastvalidation {noformat} ### (/) I edited the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/osuser.xml file to comment out the current authentication mechanism and then uncomment the crowd one. ## (/) I then edited the /opt/atlassian-jira-standalone-3.13.5/conf/server/xml file and configured the database connection to the Jira_Temp database on Solstice2. I looked like this: {noformat} {noformat} ## (/) Edit the /opt/atlassian/jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/entityengine.xml and changed it from 'hsql' to 'mssql' and delete the line with "PUBLIC" in it per the instructions in the comments in that file. ## (/) I edited the /etc/httpd/conf/httpd.conf file and created a proxy pass at the bottom of the file to point a normal URL to the default port 8080 for JIRA: {noformat} # Proxy Pass for JIRA ProxyPass http://bugs.mbari.org:8080 ProxyPassReverse http://bugs.mbari.org:8080 {noformat} ## (/) I restarted Apache ## (/) I scp'd the jtds driver from oceana to the /opt/atlassian-jira-standalone-3.13.5/common/lib directory (you could down from the internet) ## (/) I then went to the /opt/atlassian-jira-standalone-3.13.5/ directory and ran './bin/startup.sh'. From the log file, I could tell things were hanging. After some troubleshooting I am wondering if the local firewall is preventing the application to get access to the database on solstice2. I can telnet to port 1433, but I can't browse to the base http://bugs.mbari.org from anywhere but the local web browser. I have submitted a ticket. ## (/) I restarted the old JIRA with my hopes dashed :(. ## (/) Pat disabled the firewall on bugs.mbari.org but it still hung trying to connect to solstice2.shore.mbari.org. That is really, really perplexing. Neil mentioned that solstice2 is using Kerberos and solstice is not. Checking with the JTDS docs, version 1.3.1 of the driver added kerberos support, so I downloaded that driver and added the 'userKerberos=true' property to the URL in the server.xml file and restarted. Got an error about no credentials, so added user and password properties to the URL. Nope, no luck. Never did figure this one out, but I had Pat pull the VM inside the firewall and after some thrash it worked. Well, it sort of worked ... sigh. It turns out I had downloaded the standard version instead of the enterprise version. I need to redo this work ... grrr. ## (/) I deleted all the tables in the Jira_Temp database and removed the /data/jira3135/indexes directory (and recreated). ## (/) I downloaded the enterprise version of the 3.13.5 server. I made a copy in the /opt directory and unzipped and untarred the file. ## (/) I went back to crowd and edited the application to change the properties to: ### URL: http://bugs.shore.mbari.org:8080 ### IP: 134.89.12.31 ### Name: jira3135 ### Password: (ask Kevin) :) ## (/) I then repeated the steps above to get the server up and running with the following differences: ### The server name is now bugs.shore.mbari.org ### The paths given above are a little different in that they no longer say "standard" but say "enterprise" ### I deleted the proxy pass as it seemed to have issues before and this is only temporary anyway. ## (/) I then browsed to http://bugs.shore.mbari.org:8080 ## (/) It took me to the start up page and at the top was the option to 'import your existing data'. Seemed too good not to try. I clicked on the link. It asked me for the backup file location and the location where the indexes would be stored. ## (/) I copied the XML zip file and the attachments tar file to the /data/original directory. ## (/) I created the /data/jira3135/indexes and used those directories ... it fired off the import and I waited. ## (/) I tailed the log file to watch the import. Holy crap, it worked!!! I could log in and everything! I copied the results from the log file here for posterity sake: {noformat} 2015-07-22 20:55:45,156 http-8080-Processor22 INFO [jira.action.admin.DataImport] Running data import 2015-07-22 20:55:45,179 http-8080-Processor22 INFO [jira.action.admin.DataImport] Importing data.. 2015-07-22 20:55:45,186 http-8080-Processor22 INFO [jira.action.admin.DataImport] Start parsing XML with SAX Parser 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] XML successfully parsed 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] Removing all entries from the database. 2015-07-22 20:56:24,593 http-8080-Processor22 INFO [jira.action.admin.DataImport] All entries removed. 2015-07-22 20:56:24,594 http-8080-Processor22 INFO [jira.action.admin.DataImport] Started storing 410414 Generic Values 2015-07-22 21:01:51,967 http-8080-Processor22 INFO [jira.action.admin.DataImport] Finished storing Generic Values 2015-07-22 21:01:52,329 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:52,361 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:54,683 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLink' to module 'jira.user.format:profile-link-user-format'. 2015-07-22 21:01:54,724 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullName' to module 'jira.user.format:full-name-user-format'. 2015-07-22 21:01:54,773 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkSearcher' to module 'jira.user.format:profile-link-searcher-user-format'. 2015-07-22 21:01:54,784 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkExternal' to module 'jira.user.format:profile-link-external-user-format'. 2015-07-22 21:01:54,795 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkActionHeader' to module 'jira.user.format:profile-link-action-header-user-format'. 2015-07-22 21:01:54,807 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullProfile' to module 'jira.user.format:full-profile-user-format'. 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/comments 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/issues 2015-07-22 21:01:55,641 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/plugins 2015-07-22 21:01:55,867 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:01:55,871 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/issues does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:55,873 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/comments does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,033 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,257 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,889 http-8080-Processor22 ERROR [atlassian.jira.upgrade.ConsistencyCheckImpl] Attachments are turned on, but attachment path [/data/jira_3_12/attachments] invalid - disabling attachments 2015-07-22 21:02:13,904 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Detected that an upgrade is needed; existing data at build 299 2015-07-22 21:02:13,907 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Doing Upgrade... 2015-07-22 21:02:13,915 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value' succeeded 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 317 2015-07-22 21:02:13,944 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite filters - make each filter a favourite of its owner. 2015-07-22 21:02:17,822 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build319] Could not find author 'fpy' for filter with id '10040' 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite filters - make each filter a favourite of its owner.' succeeded 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 319 2015-07-22 21:02:17,995 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise Share Permissions. Move old shares to new shares. 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise Share Permissions. Move old shares to new shares.' succeeded 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 321 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Migrating the old JIRA UI colors to the new JIRA 3.13 colors 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build322] Custom color detected for jira.lf.menu.bgcolour : #336699 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Migrating the old JIRA UI colors to the new JIRA 3.13 colors' succeeded 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 322 2015-07-22 21:02:18,025 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite dashboards - make each dashboard a favourite of its owner. 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'cmcgann' for dashboard with id '10030' 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'fpy' for dashboard with id '10060' 2015-07-22 21:02:18,423 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'kanna' for dashboard with id '10040' 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite dashboards - make each dashboard a favourite of its owner.' succeeded 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 325 2015-07-22 21:02:18,625 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Reindexing all data in JIRA to include Favourites. 2015-07-22 21:02:18,648 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All starting... 2015-07-22 21:02:18,650 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 0% complete. Current index: Issue 2015-07-22 21:02:18,654 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:02:18,809 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 1% complete. Current index: Issue 2015-07-22 21:02:18,855 indexerPool-2-thread-10 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 2% complete. Current index: Issue 2015-07-22 21:02:18,899 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 3% complete. Current index: Issue 2015-07-22 21:02:18,945 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 4% complete. Current index: Issue 2015-07-22 21:02:19,012 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 5% complete. Current index: Issue . . . 2015-07-22 21:02:26,164 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 95% complete. Current index: Issue 2015-07-22 21:02:26,232 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 96% complete. Current index: Issue 2015-07-22 21:02:26,316 indexerPool-2-thread-9 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 97% complete. Current index: Issue 2015-07-22 21:02:26,771 indexerPool-2-thread-3 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: Issue 2015-07-22 21:02:27,261 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 8607ms. Indexer: DefaultIndexManager: paths: [/data/jira3135/indexes/issues, /data/jira3135/indexes/comments] 2015-07-22 21:02:27,263 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: SearchRequest 2015-07-22 21:02:27,268 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,293 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: SearchRequest 2015-07-22 21:02:27,308 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: PortalPage 2015-07-22 21:02:27,312 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,377 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: PortalPage 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 115ms. Indexer: SharedEntityIndexManager: paths: [/data/jira3135/indexes/entities/portalpage, /data/jira3135/indexes/entities/searchrequest] 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All complete. Total time: 8722ms. 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Reindexing all data in JIRA to include Favourites.' succeeded 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 326 2015-07-22 21:02:27,397 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade succeeded! Setting data build number to 360 2015-07-22 21:02:27,469 JiraQuartzScheduler_Worker-0 WARN [service.services.export.ExportService] Backup directory /data/jira_3_12/backup does not exist {noformat} {warning:title=Paths} It appears that the upgraded JIRA will still look for the attachments and the backup locations in the original places. So I created /data/jira_3_12/backup and untarred the original attachments to /data/jira_3_12 and then everything worked (including attachements) in the new JIRA. {warning} ## (/) I then used the upgraded JIRA to generate a new XML backup and stored it in /data/original/3.13.5 along with another tar of the files in /data/jira_3_12/attachments. ## (/) I then shutdown the JIRA server. *I should be ready to move on to version 4 upgrade WHEW* ## So, before moving on, I decided that it would be a really good idea to spin up a new Crowd instance to get rid of the :8443 in the URL and to move off of RedHat per IS requests. I have a ticket in for a new VM and a new database to try to get this going. I am waiting on that before moving on. ## (/) Pat created the VM and Neil created the database. ## (/) I logged into auth.mbari.org (name of the VM) and downloaded crowd which I unzipped to the /opt directory ## (/) I then created a /data/crowd directory and gave my account permissions on it and then edited the /opt/atlassian..../crowd-webapp/WEB-INF/classes/crowd-init.properties file to set that as the crowd home directory. ## (/) I fired up crowd and then went to the http://localhost:8095 URL to start the configuration. I input the DB connection parameters and it created the DB and took off just fine. I really wanted to run the application on port 80 and 443 as normal applications do so I first tried to change the port numbers that the application ran on. That did not work as those are privileged ports and cannot be controller unless you are root. I did not want to do that, so I will have to do a proxy pass. I had to start up the httpd services (I will need to configure as a service) and then created a new file in /etc/httpd/conf.d called crowd.conf that contained the following: {noformat} # This is the configuration for the proxy pass for the crowd server ProxyRequests Off ProxyPreserveHost On Require all granted ProxyPass /crowd http://auth.mbari.org:8095/crowd ProxyPassReverse /crowd http://auth.mbari.org:8095/crowd Require all granted ProxyPass /openidserver http://auth.mbari.org:8095/openidserver ProxyPassReverse /openidserver http://auth.mbari.org:8095/openidserver Require all granted {noformat} ## This worked for the basic HTTP so I will have to get it working with SSL. ## Something with the openidserver is not working correctly and I suspect I have not done the openidserver install completely or correctly # Schedule upgrade date and send all hands several days in advance. # When the day arrives, send all hands announcing JIRA outage. # From the Administrator's page in our existing JIRA, perform a 'Backup Data to XML'. # Login to oceana.mbari.org as root. # Shutdown JIRA # Create a tar.gz of the /opt/atlassian-jira-enterprise-3.12.1-standalone directory # Clean up the /data/jira_3_12/backups directory by deleting all but maybe the last 5 backups. # Create a tar.gz of the JIRA home directory on ocean.mbari.org which is located at /data/jira_3_12 # scp both tar.gz files to bugs.mbari.org # login to bugs.mbari.org # Unpack the home directory tar to /data/jira # Run the installer as root (this might need IS help or sudo privs). Note that we usually install the application to /opt # Run the JIRA Configuration tool to set the jira.home to the /data/jira location # Connect to JIRA_Temp database on Solstice2 (.... more to do here, see Atlassian docs) # Migrate existing configuration over to new JIRA (I need to add more here as we added Crowd). # Start JIRA # Import backed up XML # Perform post upgrades checks and tests *Need to document steps for 4.4.5->6.X*]]> 27558035 13959410 13926648 27590802 4.4: [https://confluence.atlassian.com/display/JIRA044/Migrating+JIRA+to+Another+Server] ## The JIRA configuration tool: [https://confluence.atlassian.com/display/JIRA044/Using+the+JIRA+Configuration+Tool] h5. Steps # (/) Create new VM named bugs.mbari.org in the DMZ # (/) Have Neil create database Jira_Temp on solstice2.shore.mbari.org # (/) Have Neil create database Jira on solstice2.shore.mbari.org # (/) Have Pat install Java 7 on bugs.shore.mbari.org # (/) Have Pete plumb holes through firewall so processes on bugs.mbari.org can get to Solstice2 # (/) Have Pat create DB_Collaboration account on bugs so it can run JIRA under that account and it can connect to solstice2 using that NT Domain account. # (/) Upgrade license on Atlassian site # (/) Log into bugs.shore.mbari.org # (/) Download 3.13.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 4.4.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 5.2.11 standalone Linux 64 bit tar.gz (not sure this version is necessary, but at least I have it) # (/) Unzip and untar the file to /opt # (/) Download latest JIRA (6.4.7 as of this writing). # (/) Unzip and untar it to /opt # Performed Test Upgrade ## (/) In order to export the current stuff in JIRA, I had to shut off access so people could not change the data while I was backing it up. ## (/) I ssh'd to oceana.mbari.org as root and edited the /opt/jira/conf/server.xml file and commented out the Connector section that had the port of 8010 to shut it off from the normal serving route. ## (/) I uncommented the 8082 port connector and the 8443 port connector so that I could still get to the server. ## (/) I stopped and started the JIRA server and in the log file I got a "keystore was tampered with..." which is not surprising. ## (/) I could then browser over to http://oceana.mbari.org:8082/jira ## (/) Then through the Administration console, I did an XML backup ## (/) I then created a tar of all the attachments in the /data/jira_3_12/attachments directory ## (/) I moved both the XML and tar files to the /root/jira-upgrade directory ## (/) I then reversed the changes to the server.xml file and shut down JIRA ## (/) I left it down during the next steps in case it went so well, I could just point people to the new server (yeah, right). ## (/) I then browsed to the crowd server on oceana and add a new application using: ### URL: http://bugs.mbari.org/jira3135 ### IP: 134.89.2.29 ### Name: JIRA3135 ### Password: (ask Kevin) :) ## (/) On bugs, I made a copy of the JIRA 3.13.5 download in the /opt directory and unzipped and untarred it. ## (/) In order to configure the crowd connection I did the following: ### (/) I scp'd the /opt/crowd/client/crowd-integration-client-1.6.jar file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I removed the existing 1.6.1 crowd client jar from the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I scp'd the /opt/crowd/client/conf/crowd.properties file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I scp'd the /opt/crowd/client/conf/crowd-ehcache.xml file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I edited the crowd.properties file on bugs to look like: {noformat} application.name JIRA3135 application.password (ask Kevin) application.login.url http://oceana.mbari.org:8095/crowd/console/ crowd.server.url http://oceana.mbari.org:8095/crowd/services/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 0 session.lastvalidation session.lastvalidation {noformat} ### (/) I edited the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/osuser.xml file to comment out the current authentication mechanism and then uncomment the crowd one. ## (/) I then edited the /opt/atlassian-jira-standalone-3.13.5/conf/server/xml file and configured the database connection to the Jira_Temp database on Solstice2. I looked like this: {noformat} {noformat} ## (/) Edit the /opt/atlassian/jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/entityengine.xml and changed it from 'hsql' to 'mssql' and delete the line with "PUBLIC" in it per the instructions in the comments in that file. ## (/) I edited the /etc/httpd/conf/httpd.conf file and created a proxy pass at the bottom of the file to point a normal URL to the default port 8080 for JIRA: {noformat} # Proxy Pass for JIRA ProxyPass http://bugs.mbari.org:8080 ProxyPassReverse http://bugs.mbari.org:8080 {noformat} ## (/) I restarted Apache ## (/) I scp'd the jtds driver from oceana to the /opt/atlassian-jira-standalone-3.13.5/common/lib directory (you could down from the internet) ## (/) I then went to the /opt/atlassian-jira-standalone-3.13.5/ directory and ran './bin/startup.sh'. From the log file, I could tell things were hanging. After some troubleshooting I am wondering if the local firewall is preventing the application to get access to the database on solstice2. I can telnet to port 1433, but I can't browse to the base http://bugs.mbari.org from anywhere but the local web browser. I have submitted a ticket. ## (/) I restarted the old JIRA with my hopes dashed :(. ## (/) Pat disabled the firewall on bugs.mbari.org but it still hung trying to connect to solstice2.shore.mbari.org. That is really, really perplexing. Neil mentioned that solstice2 is using Kerberos and solstice is not. Checking with the JTDS docs, version 1.3.1 of the driver added kerberos support, so I downloaded that driver and added the 'userKerberos=true' property to the URL in the server.xml file and restarted. Got an error about no credentials, so added user and password properties to the URL. Nope, no luck. Never did figure this one out, but I had Pat pull the VM inside the firewall and after some thrash it worked. Well, it sort of worked ... sigh. It turns out I had downloaded the standard version instead of the enterprise version. I need to redo this work ... grrr. ## (/) I deleted all the tables in the Jira_Temp database and removed the /data/jira3135/indexes directory (and recreated). ## (/) I downloaded the enterprise version of the 3.13.5 server. I made a copy in the /opt directory and unzipped and untarred the file. ## (/) I went back to crowd and edited the application to change the properties to: ### URL: http://bugs.shore.mbari.org:8080 ### IP: 134.89.12.31 ### Name: jira3135 ### Password: (ask Kevin) :) ## (/) I then repeated the steps above to get the server up and running with the following differences: ### The server name is now bugs.shore.mbari.org ### The paths given above are a little different in that they no longer say "standard" but say "enterprise" ### I deleted the proxy pass as it seemed to have issues before and this is only temporary anyway. ## (/) I then browsed to http://bugs.shore.mbari.org:8080 ## (/) It took me to the start up page and at the top was the option to 'import your existing data'. Seemed too good not to try. I clicked on the link. It asked me for the backup file location and the location where the indexes would be stored. ## (/) I copied the XML zip file and the attachments tar file to the /data/original directory. ## (/) I created the /data/jira3135/indexes and used those directories ... it fired off the import and I waited. ## (/) I tailed the log file to watch the import. Holy crap, it worked!!! I could log in and everything! I copied the results from the log file here for posterity sake: {noformat} 2015-07-22 20:55:45,156 http-8080-Processor22 INFO [jira.action.admin.DataImport] Running data import 2015-07-22 20:55:45,179 http-8080-Processor22 INFO [jira.action.admin.DataImport] Importing data.. 2015-07-22 20:55:45,186 http-8080-Processor22 INFO [jira.action.admin.DataImport] Start parsing XML with SAX Parser 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] XML successfully parsed 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] Removing all entries from the database. 2015-07-22 20:56:24,593 http-8080-Processor22 INFO [jira.action.admin.DataImport] All entries removed. 2015-07-22 20:56:24,594 http-8080-Processor22 INFO [jira.action.admin.DataImport] Started storing 410414 Generic Values 2015-07-22 21:01:51,967 http-8080-Processor22 INFO [jira.action.admin.DataImport] Finished storing Generic Values 2015-07-22 21:01:52,329 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:52,361 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:54,683 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLink' to module 'jira.user.format:profile-link-user-format'. 2015-07-22 21:01:54,724 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullName' to module 'jira.user.format:full-name-user-format'. 2015-07-22 21:01:54,773 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkSearcher' to module 'jira.user.format:profile-link-searcher-user-format'. 2015-07-22 21:01:54,784 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkExternal' to module 'jira.user.format:profile-link-external-user-format'. 2015-07-22 21:01:54,795 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkActionHeader' to module 'jira.user.format:profile-link-action-header-user-format'. 2015-07-22 21:01:54,807 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullProfile' to module 'jira.user.format:full-profile-user-format'. 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/comments 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/issues 2015-07-22 21:01:55,641 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/plugins 2015-07-22 21:01:55,867 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:01:55,871 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/issues does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:55,873 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/comments does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,033 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,257 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,889 http-8080-Processor22 ERROR [atlassian.jira.upgrade.ConsistencyCheckImpl] Attachments are turned on, but attachment path [/data/jira_3_12/attachments] invalid - disabling attachments 2015-07-22 21:02:13,904 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Detected that an upgrade is needed; existing data at build 299 2015-07-22 21:02:13,907 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Doing Upgrade... 2015-07-22 21:02:13,915 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value' succeeded 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 317 2015-07-22 21:02:13,944 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite filters - make each filter a favourite of its owner. 2015-07-22 21:02:17,822 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build319] Could not find author 'fpy' for filter with id '10040' 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite filters - make each filter a favourite of its owner.' succeeded 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 319 2015-07-22 21:02:17,995 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise Share Permissions. Move old shares to new shares. 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise Share Permissions. Move old shares to new shares.' succeeded 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 321 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Migrating the old JIRA UI colors to the new JIRA 3.13 colors 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build322] Custom color detected for jira.lf.menu.bgcolour : #336699 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Migrating the old JIRA UI colors to the new JIRA 3.13 colors' succeeded 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 322 2015-07-22 21:02:18,025 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite dashboards - make each dashboard a favourite of its owner. 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'cmcgann' for dashboard with id '10030' 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'fpy' for dashboard with id '10060' 2015-07-22 21:02:18,423 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'kanna' for dashboard with id '10040' 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite dashboards - make each dashboard a favourite of its owner.' succeeded 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 325 2015-07-22 21:02:18,625 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Reindexing all data in JIRA to include Favourites. 2015-07-22 21:02:18,648 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All starting... 2015-07-22 21:02:18,650 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 0% complete. Current index: Issue 2015-07-22 21:02:18,654 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:02:18,809 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 1% complete. Current index: Issue 2015-07-22 21:02:18,855 indexerPool-2-thread-10 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 2% complete. Current index: Issue 2015-07-22 21:02:18,899 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 3% complete. Current index: Issue 2015-07-22 21:02:18,945 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 4% complete. Current index: Issue 2015-07-22 21:02:19,012 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 5% complete. Current index: Issue . . . 2015-07-22 21:02:26,164 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 95% complete. Current index: Issue 2015-07-22 21:02:26,232 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 96% complete. Current index: Issue 2015-07-22 21:02:26,316 indexerPool-2-thread-9 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 97% complete. Current index: Issue 2015-07-22 21:02:26,771 indexerPool-2-thread-3 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: Issue 2015-07-22 21:02:27,261 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 8607ms. Indexer: DefaultIndexManager: paths: [/data/jira3135/indexes/issues, /data/jira3135/indexes/comments] 2015-07-22 21:02:27,263 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: SearchRequest 2015-07-22 21:02:27,268 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,293 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: SearchRequest 2015-07-22 21:02:27,308 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: PortalPage 2015-07-22 21:02:27,312 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,377 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: PortalPage 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 115ms. Indexer: SharedEntityIndexManager: paths: [/data/jira3135/indexes/entities/portalpage, /data/jira3135/indexes/entities/searchrequest] 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All complete. Total time: 8722ms. 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Reindexing all data in JIRA to include Favourites.' succeeded 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 326 2015-07-22 21:02:27,397 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade succeeded! Setting data build number to 360 2015-07-22 21:02:27,469 JiraQuartzScheduler_Worker-0 WARN [service.services.export.ExportService] Backup directory /data/jira_3_12/backup does not exist {noformat} {warning:title=Paths} It appears that the upgraded JIRA will still look for the attachments and the backup locations in the original places. So I created /data/jira_3_12/backup and untarred the original attachments to /data/jira_3_12 and then everything worked (including attachements) in the new JIRA. {warning} ## (/) I then used the upgraded JIRA to generate a new XML backup and stored it in /data/original/3.13.5 along with another tar of the files in /data/jira_3_12/attachments. ## (/) I then shutdown the JIRA server. *I should be ready to move on to version 4 upgrade WHEW* ## So, before moving on, I decided that it would be a really good idea to spin up a new Crowd instance to get rid of the :8443 in the URL and to move off of RedHat per IS requests. I have a ticket in for a new VM and a new database to try to get this going. I am waiting on that before moving on. ## (/) Pat created the VM and Neil created the database. ## (/) I logged into auth.mbari.org (name of the VM) and downloaded crowd which I unzipped to the /opt directory ## (/) I then created a /data/crowd directory and gave my account permissions on it and then edited the /opt/atlassian..../crowd-webapp/WEB-INF/classes/crowd-init.properties file to set that as the crowd home directory. ## (/) I fired up crowd and then went to the http://localhost:8095 URL to start the configuration. I input the DB connection parameters and it created the DB and took off just fine. I really wanted to run the application on port 80 and 443 as normal applications do so I first tried to change the port numbers that the application ran on. That did not work as those are privileged ports and cannot be controller unless you are root. I did not want to do that, so I will have to do a proxy pass. I had to start up the httpd services (I will need to configure as a service) and then created a new file in /etc/httpd/conf.d called crowd.conf that contained the following: {noformat} # This is the configuration for the proxy pass for the crowd server ProxyRequests Off ProxyPreserveHost On Require all granted ProxyPass /crowd http://auth.mbari.org:8095/crowd ProxyPassReverse /crowd http://auth.mbari.org:8095/crowd Require all granted ProxyPass /openidserver http://auth.mbari.org:8095/openidserver ProxyPassReverse /openidserver http://auth.mbari.org:8095/openidserver Require all granted {noformat} ## (/) This worked for the basic HTTP so I will have to get it working with SSL. ## (/) Something with the openidserver is not working correctly and I suspect I have not done the openidserver install completely or correctly. I read the directions on configuring crowdid and it's connection to the database and restarted the crowd server. # Schedule upgrade date and send all hands several days in advance. # When the day arrives, send all hands announcing JIRA outage. # From the Administrator's page in our existing JIRA, perform a 'Backup Data to XML'. # Login to oceana.mbari.org as root. # Shutdown JIRA # Create a tar.gz of the /opt/atlassian-jira-enterprise-3.12.1-standalone directory # Clean up the /data/jira_3_12/backups directory by deleting all but maybe the last 5 backups. # Create a tar.gz of the JIRA home directory on ocean.mbari.org which is located at /data/jira_3_12 # scp both tar.gz files to bugs.mbari.org # login to bugs.mbari.org # Unpack the home directory tar to /data/jira # Run the installer as root (this might need IS help or sudo privs). Note that we usually install the application to /opt # Run the JIRA Configuration tool to set the jira.home to the /data/jira location # Connect to JIRA_Temp database on Solstice2 (.... more to do here, see Atlassian docs) # Migrate existing configuration over to new JIRA (I need to add more here as we added Crowd). # Start JIRA # Import backed up XML # Perform post upgrades checks and tests *Need to document steps for 4.4.5->6.X*]]> 27558037 19073878 19041187 13959431 13926669 10388276 10355548 19073876 19041185 13959433 13926671 10388279 10355551 19073881 19041190 19073880 19041189 10388283 10355555 19073885 19041194 13959440 13926678 10388285 @kahuna.shore.mbari.org/svn/repos/MBARItracking/trunk MBARItracking {noformat} Where is your account name on kahuna. This package has be checked out to the following accounts on pismo.shore.mbari.org into the \~/dev directory (the password is the same for all these accounts - ask Mike McCann or Pat Allen for it): * m1track * m2track * shiptrack * aistrack * auvtrack  Please refer to the README files in the package for further details on the implementation.  For easy reference here is the current version of the README in the scripts directory: {noformat}  scripts folder of the MBARItracking project =========================================== $Id: README 5246 2009-07-08 18:14:29Z mccann $ The scripts here populate the MBARItracking database with position data. The various scripts are implemented in various ways from various accounts as indicated below: Script Account Implementation ------ ------- -------------- grabShipPosition.py shiptrack Connect to socket, parse $GPRMC, insert to DB, write to log file shipWatchdog.py shiptrack Check log file like: 0,10,20,30,40,50 * * * * /shipWatchdog.py grabAISposition.py aistrack Connect to socket, parse AIS, insert to DB, write to log file aisWatchdog.py aistrack Check log file like: 0,10,20,30,40,50 * * * * /aisWatchdog.py grabOasisTrackers.pl m1track Symlinked by grabM{1,2}tracker.pl, in .forward file, parse MIME m2track messages from email sent from Iridium modems, insert to DB. {noformat}]]> 10355557 19073883 19041192 10388287 @kahuna.shore.mbari.org/svn/repos/MBARItracking/trunk MBARItracking {noformat} Where is your account name on kahuna. This package has be checked out to the following accounts on pismo.shore.mbari.org into the \~/dev directory (the password is the same for all these accounts - ask Mike McCann or Pat Allen for it): * m1track * m2track * shiptrack * aistrack * auvtrack  Please refer to the README files in the package for further details on the implementation.  For easy reference here is the current version of the README in the scripts directory: {noformat}  scripts folder of the MBARItracking project =========================================== $Id: README 5246 2009-07-08 18:14:29Z mccann $ The scripts here populate the MBARItracking database with position data. The various scripts are implemented in various ways from various accounts as indicated below: Script Account Implementation ------ ------- -------------- grabShipPosition.py shiptrack Connect to socket, parse $GPRMC, insert to DB, write to log file shipWatchdog.py shiptrack Check log file like: 0,10,20,30,40,50 * * * * /shipWatchdog.py grabAISposition.py aistrack Connect to socket, parse AIS, insert to DB, write to log file aisWatchdog.py aistrack Check log file like: 0,10,20,30,40,50 * * * * /aisWatchdog.py grabOasisTrackers.pl m1track Symlinked by grabM{1,2}tracker.pl, in .forward file, parse MIME m2track messages from email sent from Iridium modems, insert to DB. {noformat} To monitor the successful operation of this system open this link in Google Earth: [http://elvis.shore.mbari.org/tracking/viewTracking.kml|Should launch GoogleEarth on your system] (This link is on our public web site on the "Today in the Bay" web page: [http://www.mbari.org/cruises/all/plot/all700.html|http://www.mbari.org/cruises/all/plot/all700.html ]). If you can see data for the last hour then the realtime feeds and database are operating. \-\- Mike McCann 23 July 2009]]> 10355559 13959435 13926673 19073889 19041198 13959436 13926674 19073887 19041196 13959438 13926676 19073861 19041170 19073860 19041169 19073865 19041174 19073866 19041175 19073863 19041172 19073869 19041178 19073870 19041179 19073868 19041177 19073873 19041182 19073874 19041183 19073871 19041180 19073872 19041181 27590983 4.4: [https://confluence.atlassian.com/display/JIRA044/Migrating+JIRA+to+Another+Server] ## The JIRA configuration tool: [https://confluence.atlassian.com/display/JIRA044/Using+the+JIRA+Configuration+Tool] h5. Steps # (/) Create new VM named bugs.mbari.org in the DMZ # (/) Have Neil create database Jira_Temp on solstice2.shore.mbari.org # (/) Have Neil create database Jira on solstice2.shore.mbari.org # (/) Have Pat install Java 7 on bugs.shore.mbari.org # (/) Have Pete plumb holes through firewall so processes on bugs.mbari.org can get to Solstice2 # (/) Have Pat create DB_Collaboration account on bugs so it can run JIRA under that account and it can connect to solstice2 using that NT Domain account. # (/) Upgrade license on Atlassian site # (/) Log into bugs.shore.mbari.org # (/) Download 3.13.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 4.4.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 5.2.11 standalone Linux 64 bit tar.gz (not sure this version is necessary, but at least I have it) # (/) Unzip and untar the file to /opt # (/) Download latest JIRA (6.4.7 as of this writing). # (/) Unzip and untar it to /opt # Performed Test Upgrade ## (/) In order to export the current stuff in JIRA, I had to shut off access so people could not change the data while I was backing it up. ## (/) I ssh'd to oceana.mbari.org as root and edited the /opt/jira/conf/server.xml file and commented out the Connector section that had the port of 8010 to shut it off from the normal serving route. ## (/) I uncommented the 8082 port connector and the 8443 port connector so that I could still get to the server. ## (/) I stopped and started the JIRA server and in the log file I got a "keystore was tampered with..." which is not surprising. ## (/) I could then browser over to http://oceana.mbari.org:8082/jira ## (/) Then through the Administration console, I did an XML backup ## (/) I then created a tar of all the attachments in the /data/jira_3_12/attachments directory ## (/) I moved both the XML and tar files to the /root/jira-upgrade directory ## (/) I then reversed the changes to the server.xml file and shut down JIRA ## (/) I left it down during the next steps in case it went so well, I could just point people to the new server (yeah, right). ## (/) I then browsed to the crowd server on oceana and add a new application using: ### URL: http://bugs.mbari.org/jira3135 ### IP: 134.89.2.29 ### Name: JIRA3135 ### Password: (ask Kevin) :) ## (/) On bugs, I made a copy of the JIRA 3.13.5 download in the /opt directory and unzipped and untarred it. ## (/) In order to configure the crowd connection I did the following: ### (/) I scp'd the /opt/crowd/client/crowd-integration-client-1.6.jar file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I removed the existing 1.6.1 crowd client jar from the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I scp'd the /opt/crowd/client/conf/crowd.properties file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I scp'd the /opt/crowd/client/conf/crowd-ehcache.xml file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I edited the crowd.properties file on bugs to look like: {noformat} application.name JIRA3135 application.password (ask Kevin) application.login.url http://oceana.mbari.org:8095/crowd/console/ crowd.server.url http://oceana.mbari.org:8095/crowd/services/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 0 session.lastvalidation session.lastvalidation {noformat} ### (/) I edited the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/osuser.xml file to comment out the current authentication mechanism and then uncomment the crowd one. ## (/) I then edited the /opt/atlassian-jira-standalone-3.13.5/conf/server/xml file and configured the database connection to the Jira_Temp database on Solstice2. I looked like this: {noformat} {noformat} ## (/) Edit the /opt/atlassian/jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/entityengine.xml and changed it from 'hsql' to 'mssql' and delete the line with "PUBLIC" in it per the instructions in the comments in that file. ## (/) I edited the /etc/httpd/conf/httpd.conf file and created a proxy pass at the bottom of the file to point a normal URL to the default port 8080 for JIRA: {noformat} # Proxy Pass for JIRA ProxyPass http://bugs.mbari.org:8080 ProxyPassReverse http://bugs.mbari.org:8080 {noformat} ## (/) I restarted Apache ## (/) I scp'd the jtds driver from oceana to the /opt/atlassian-jira-standalone-3.13.5/common/lib directory (you could down from the internet) ## (/) I then went to the /opt/atlassian-jira-standalone-3.13.5/ directory and ran './bin/startup.sh'. From the log file, I could tell things were hanging. After some troubleshooting I am wondering if the local firewall is preventing the application to get access to the database on solstice2. I can telnet to port 1433, but I can't browse to the base http://bugs.mbari.org from anywhere but the local web browser. I have submitted a ticket. ## (/) I restarted the old JIRA with my hopes dashed :(. ## (/) Pat disabled the firewall on bugs.mbari.org but it still hung trying to connect to solstice2.shore.mbari.org. That is really, really perplexing. Neil mentioned that solstice2 is using Kerberos and solstice is not. Checking with the JTDS docs, version 1.3.1 of the driver added kerberos support, so I downloaded that driver and added the 'userKerberos=true' property to the URL in the server.xml file and restarted. Got an error about no credentials, so added user and password properties to the URL. Nope, no luck. Never did figure this one out, but I had Pat pull the VM inside the firewall and after some thrash it worked. Well, it sort of worked ... sigh. It turns out I had downloaded the standard version instead of the enterprise version. I need to redo this work ... grrr. ## (/) I deleted all the tables in the Jira_Temp database and removed the /data/jira3135/indexes directory (and recreated). ## (/) I downloaded the enterprise version of the 3.13.5 server. I made a copy in the /opt directory and unzipped and untarred the file. ## (/) I went back to crowd and edited the application to change the properties to: ### URL: http://bugs.shore.mbari.org:8080 ### IP: 134.89.12.31 ### Name: jira3135 ### Password: (ask Kevin) :) ## (/) I then repeated the steps above to get the server up and running with the following differences: ### The server name is now bugs.shore.mbari.org ### The paths given above are a little different in that they no longer say "standard" but say "enterprise" ### I deleted the proxy pass as it seemed to have issues before and this is only temporary anyway. ## (/) I then browsed to http://bugs.shore.mbari.org:8080 ## (/) It took me to the start up page and at the top was the option to 'import your existing data'. Seemed too good not to try. I clicked on the link. It asked me for the backup file location and the location where the indexes would be stored. ## (/) I copied the XML zip file and the attachments tar file to the /data/original directory. ## (/) I created the /data/jira3135/indexes and used those directories ... it fired off the import and I waited. ## (/) I tailed the log file to watch the import. Holy crap, it worked!!! I could log in and everything! I copied the results from the log file here for posterity sake: {noformat} 2015-07-22 20:55:45,156 http-8080-Processor22 INFO [jira.action.admin.DataImport] Running data import 2015-07-22 20:55:45,179 http-8080-Processor22 INFO [jira.action.admin.DataImport] Importing data.. 2015-07-22 20:55:45,186 http-8080-Processor22 INFO [jira.action.admin.DataImport] Start parsing XML with SAX Parser 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] XML successfully parsed 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] Removing all entries from the database. 2015-07-22 20:56:24,593 http-8080-Processor22 INFO [jira.action.admin.DataImport] All entries removed. 2015-07-22 20:56:24,594 http-8080-Processor22 INFO [jira.action.admin.DataImport] Started storing 410414 Generic Values 2015-07-22 21:01:51,967 http-8080-Processor22 INFO [jira.action.admin.DataImport] Finished storing Generic Values 2015-07-22 21:01:52,329 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:52,361 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:54,683 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLink' to module 'jira.user.format:profile-link-user-format'. 2015-07-22 21:01:54,724 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullName' to module 'jira.user.format:full-name-user-format'. 2015-07-22 21:01:54,773 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkSearcher' to module 'jira.user.format:profile-link-searcher-user-format'. 2015-07-22 21:01:54,784 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkExternal' to module 'jira.user.format:profile-link-external-user-format'. 2015-07-22 21:01:54,795 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkActionHeader' to module 'jira.user.format:profile-link-action-header-user-format'. 2015-07-22 21:01:54,807 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullProfile' to module 'jira.user.format:full-profile-user-format'. 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/comments 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/issues 2015-07-22 21:01:55,641 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/plugins 2015-07-22 21:01:55,867 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:01:55,871 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/issues does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:55,873 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/comments does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,033 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,257 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,889 http-8080-Processor22 ERROR [atlassian.jira.upgrade.ConsistencyCheckImpl] Attachments are turned on, but attachment path [/data/jira_3_12/attachments] invalid - disabling attachments 2015-07-22 21:02:13,904 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Detected that an upgrade is needed; existing data at build 299 2015-07-22 21:02:13,907 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Doing Upgrade... 2015-07-22 21:02:13,915 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value' succeeded 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 317 2015-07-22 21:02:13,944 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite filters - make each filter a favourite of its owner. 2015-07-22 21:02:17,822 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build319] Could not find author 'fpy' for filter with id '10040' 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite filters - make each filter a favourite of its owner.' succeeded 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 319 2015-07-22 21:02:17,995 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise Share Permissions. Move old shares to new shares. 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise Share Permissions. Move old shares to new shares.' succeeded 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 321 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Migrating the old JIRA UI colors to the new JIRA 3.13 colors 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build322] Custom color detected for jira.lf.menu.bgcolour : #336699 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Migrating the old JIRA UI colors to the new JIRA 3.13 colors' succeeded 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 322 2015-07-22 21:02:18,025 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite dashboards - make each dashboard a favourite of its owner. 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'cmcgann' for dashboard with id '10030' 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'fpy' for dashboard with id '10060' 2015-07-22 21:02:18,423 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'kanna' for dashboard with id '10040' 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite dashboards - make each dashboard a favourite of its owner.' succeeded 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 325 2015-07-22 21:02:18,625 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Reindexing all data in JIRA to include Favourites. 2015-07-22 21:02:18,648 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All starting... 2015-07-22 21:02:18,650 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 0% complete. Current index: Issue 2015-07-22 21:02:18,654 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:02:18,809 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 1% complete. Current index: Issue 2015-07-22 21:02:18,855 indexerPool-2-thread-10 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 2% complete. Current index: Issue 2015-07-22 21:02:18,899 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 3% complete. Current index: Issue 2015-07-22 21:02:18,945 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 4% complete. Current index: Issue 2015-07-22 21:02:19,012 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 5% complete. Current index: Issue . . . 2015-07-22 21:02:26,164 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 95% complete. Current index: Issue 2015-07-22 21:02:26,232 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 96% complete. Current index: Issue 2015-07-22 21:02:26,316 indexerPool-2-thread-9 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 97% complete. Current index: Issue 2015-07-22 21:02:26,771 indexerPool-2-thread-3 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: Issue 2015-07-22 21:02:27,261 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 8607ms. Indexer: DefaultIndexManager: paths: [/data/jira3135/indexes/issues, /data/jira3135/indexes/comments] 2015-07-22 21:02:27,263 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: SearchRequest 2015-07-22 21:02:27,268 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,293 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: SearchRequest 2015-07-22 21:02:27,308 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: PortalPage 2015-07-22 21:02:27,312 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,377 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: PortalPage 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 115ms. Indexer: SharedEntityIndexManager: paths: [/data/jira3135/indexes/entities/portalpage, /data/jira3135/indexes/entities/searchrequest] 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All complete. Total time: 8722ms. 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Reindexing all data in JIRA to include Favourites.' succeeded 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 326 2015-07-22 21:02:27,397 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade succeeded! Setting data build number to 360 2015-07-22 21:02:27,469 JiraQuartzScheduler_Worker-0 WARN [service.services.export.ExportService] Backup directory /data/jira_3_12/backup does not exist {noformat} {warning:title=Paths} It appears that the upgraded JIRA will still look for the attachments and the backup locations in the original places. So I created /data/jira_3_12/backup and untarred the original attachments to /data/jira_3_12 and then everything worked (including attachements) in the new JIRA. {warning} ## (/) I then used the upgraded JIRA to generate a new XML backup and stored it in /data/original/3.13.5 along with another tar of the files in /data/jira_3_12/attachments. ## (/) I then shutdown the JIRA server. *I should be ready to move on to version 4 upgrade WHEW* ## So, before moving on, I decided that it would be a really good idea to spin up a new Crowd instance to get rid of the :8443 in the URL and to move off of RedHat per IS requests. I have a ticket in for a new VM and a new database to try to get this going. I am waiting on that before moving on. ## (/) Pat created the VM and Neil created the database. ## (/) I logged into auth.mbari.org (name of the VM) and downloaded crowd which I unzipped to the /opt directory ## (/) I then created a /data/crowd directory and gave my account permissions on it and then edited the /opt/atlassian..../crowd-webapp/WEB-INF/classes/crowd-init.properties file to set that as the crowd home directory. ## (/) The instructions say to download the JDBC driver, but they already have JTDS 1.2.7 in the download so I did not do anything. ## (/) You have to manually connect up CrowdID to a database as they setup wizard does not currently do this. ### (/) They say to download the driver, but again 1.2.7 was there so I did nothing. ### (/) I edited the /opt/atlassian.../apache-tomcat/conf/Catalina/localhost/openidserver.xml to look like: {noformat} {noformat} ### (/) I edited the /opt/atlassian.../build.properties files to look like: {noformat} # Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See https://confluence.atlassian.com/display/CROWD/Connecting+Crowd+to+a+Database hibernate.dialect=org.hibernate.dialect.SQLServerDialect # The Hibernate transaction factory to use. See https://confluence.atlassian.com/display/CROWD/Configuring+Crowd hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory # The http port you wish to run crowd from, ie: http://localhost:8095/crowd crowd.tomcat.connector.port=8095 # Tomcat requires a unique port for shutdown crowd.tomcat.shutdown.port=8020 # Crowd context root crowd.url=http://localhost:8095/crowd # Demo context root demo.url=http://localhost:8095/demo # OpenID server context root openidserver.url=http://localhost:8095/openidserver {noformat} ### (/) I then ran the build.sh script in the root of /opt/atlassian... ## (/) I fired up crowd using the /opt/atlassian.../start_crowd.sh script ## (/) I then went to http://auth.mbari.org:8095/crowd to kick off the start up wizard ## (/) I grabbed a new eval license from my account on atlassian and pasted into the license page. ## (/) I selected "New install" on the next page. ## (/) I configured the JDBC connection using this connection URL with user DB_Collaboration {noformat} jdbc:jtds:sqlserver://dione.mbari.org:51001/Crowd;domain=SHORE;useNTLMv2=TRUE {noformat} ## (/) I left the "Options" as they came up {warning:title=Paths} Not sure if this is a problem, but because I started the set up using auth.mbari.org, it set the Base URL to http://auth.mbari.org:8095/crowd instead of localhost. Hope that is not a problem. We will see. {warning} ## (/) I configured the email connection using the settings from [here|https://wind.shore.mbari.org/is/howto/email/mbarimail/imap] and I used my network login (probably shouldn't be doing that ... not sure where it stores my password, but I am assuming in the DB). ## (/) For the local admin account, I created a user named 'crowdadm' so it would not clash with my LDAP account. See Kevin Gomes for password information. ## (/) I checked the OpenID server as an integrated application ## (/) It then took me to the login page and I logged in using the newly minted admin account. Seemed all is well so far. ## (/) I visited the openidserver URL as well and that seemed OK. ## (/) I decided to wait on configuring the MBARI LDAP directory until I got everything with SSL working. ## (/) Now the next step was to follow the directions to configure Crowd to run over SSL found [here|https://confluence.atlassian.com/display/CROWD/Configuring+Crowd+to+Work+with+SSL] ## (/) I shutdown crowd. Note that the stop script does not shutdown things correctly and I noticed the crowd app running as root. That should not be if I started as kgomes. Not sure what is up with that. ## (/) Now Joe had already configured SSL once, so I used his connector configuration in the server.xml file and so the final file looked like: {noformat} {noformat} ## (/) I then edited the /data/crowd/crowd.properties to look like: {noformat} #Sat Aug 01 09:05:15 PDT 2015 session.lastvalidation=session.lastvalidation session.tokenkey=session.tokenkey crowd.server.url=https\://localhost\:8443/crowd/services/ application.name=crowd http.timeout=30000 session.isauthenticated=session.isauthenticated application.login.url=https\://localhost\:8443/crowd/console/ session.validationinterval=0 application.password=Y1Xp3OorCmsOP4eruL1dmH {noformat} One thing to note here is that based on a comment from the SSL configuration page at atlassian (Steve's comment), you are supposed to leave all the host names the same. For example, if the file says localhost, leave it localhost. So this created a bit of a problem based on the fact that I had left the base URL pointing to auth.mbari.org in the wizard steps above. That step wrote auth.mbari.org to the /data/crowd/crowd.properties. All the other files reference localhost, so to be consistent, I changed auth.mbari.org to localhost in the /data/crowd/crowd.properties file. We will see if this works. ## (/) Per the instructions on the atlassian page (referenced above), I also edited the build.properties file and the /client/conf/crowd.properties files before I restarted and used the SSL URLs ## build.properties: {noformat} # Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See https://confluence.atlassian.com/display/CROWD/Connecting+Crowd+to+a+Database hibernate.dialect=org.hibernate.dialect.SQLServerDialect # The Hibernate transaction factory to use. See https://confluence.atlassian.com/display/CROWD/Configuring+Crowd hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory # The http port you wish to run crowd from, ie: http://localhost:8095/crowd crowd.tomcat.connector.port=8095 # Tomcat requires a unique port for shutdown crowd.tomcat.shutdown.port=8020 # Crowd context root crowd.url=https://localhost:8443/crowd # Demo context root demo.url=https://localhost:8443/demo # OpenID server context root openidserver.url=https://localhost:8443/openidserver {noformat} ## crowd.properties (client) {noformat} application.name crowd application.password password application.login.url https://localhost:8443/crowd/console/ crowd.server.url https://localhost:8443/crowd/services/ crowd.base.url https://localhost:8443/crowd/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 2 session.lastvalidation session.lastvalidation {noformat} ## (/) Although not stated, I am assuming you would need to run the build.sh script to push the build.properties changes to their proper places, so I did that. Note that before doing that, I know that it will clobber the server.xml changes I made, so I made a copy of that file and diff'd them after and then rolled the previous changes to the new server.xml file. Actually, amazingly enough, it seems to have done the connector entry correctly so I left it after running the build.sh script. ## (/) Crossed my fingers and then restarted crowd. I tailed the catalina.out file and did not see any stack traces so that is a good sign! ## (/) I visited https://auth.mbari.org:8443/crowd first. It could not find that page, but I suspect that is because I am browsing from the outside, so I tried just https://auth.mbari.org/crowd and got a service unavailable. I am suspecting that this is a combination of firewall and proxy pass and I will send this info to Joe. From what I can see on the crowd side, it seems like the server started cleanly, we just can't get to it. I tried to reach it from a browser on the machine itself too (through VNC) with the same service not available. ## (/) Here are the notes from Joe after he fixed it! Wooohooo! {noformat} Hey Kevin, Thanks for starting clean! I had to make a few adjustments. 1-I modified the server.xml file in /opt/atlassian-crowd-2.8.3/apache-tomcat/conf/server.xml so there are two connectors per the instructions on the Atlassian site. I have backed up this good server.xml file in /etc/temp/ if you want to browse it to see what I did. Of note is that I removed all the jargon referencing the types of ciphers available to simplify things for now. 2-I modified /data/crowd/crowd.properties to have crowd.server.url=https\://localhost\:8443/crowd/services/ application.login.url=https\://localhost\:8443/crowd/console/ But that would cause my login to error with an error saying it was unable to reach the authentication server. I scratched my head for a bit. When I revert the values to just using non-SSL and try to log in, I just get an "invalid login" (I don't know the crowdadm password). So I worked under the assumption that if I can configure SSL to get an "invalid login" when logging in then it would work when provided real credentials. So, I then changed /data/crowd/crowd.proprties to: crowd.server.url=https\://auth.mbari.org\:8443/crowd/services/ application.login.url=https\://auth.mbari.org\:8443/crowd/console/ And now when I try to log in with SSL it says "invalid login". Strange because all the other values I can find only show "localhost" .. in any case... Can you try to log in now? {noformat} ## (/) Next I moved on to configuring the connection to MBARI's LDAP server to enable our logins through Crowd and CrowdID ## (/) I clicked on "Add Directory" in crowd. ## (/) I selected "Connector" then clicked Next ## (/) I put ldap.shore.mbari.org as the name of the server ## (/) I selected "Use memberOf for group memberships" ## (/) I used "OU=AllUsers,DC=shore,DC=mbari,DC=org" for the Base DN ## (/) I used "CN=LDAPbind,OU=Special,OU=AllUsers,DC=shore,DC=mbari,DC=org" for the Username (talk to Pat Allen for password) ## (/) I tested the connection (button click) and it passed. ## (/) I de-selected all the capabilities of the connector as it is a ready only connector and then saved it. It synchronized correctly! ## (/) At first, I could not login using my MBARI credentials, but after going to the "crowd" application in crowd (logged in as the local admin), I had to add the LDAP directory and configure it to "Allow all to authenticate", then I was able to login. After this, the last step was to get this to run as a different user and lock down various directories. I went through the entire directory structure /opt/atlassian... and set up so that root owned all read-only locations and DB_Collaboration (account set up by IS) owned the other stuff. I also gave full ownership to the /data/crowd directory to DB_Collaboration so it could write there. Pat set up a script to start on boot and after a little tweaking, it now starts on boot. {warning:title=CrowdID log file} One thing that came up here was that when the crowdID application ran, it tried to write a log file to the location where the process was launched from (which is /opt/atlassian...). This is a bad thing and I figured out that I could change that location by changing the file /opt/atlassian-crowd-2.8.3/crowd-openidserver-webapp/WEB-INF/classes/log4j.properties and hardcoding the /data/crowd/logs/atlassian-crowd-openid-server.log and then restarted the application. {warning} ## (/) Another note is the when an application tried to use the OpenID application, it would get redirected to localhost. I changed the /opt/atlassian.../crowd-openidserver-webapp/WEB-INF/classes/crowd.properties file to look like: {noformat} #Sat Aug 01 10:03:18 PDT 2015 session.lastvalidation=session.lastvalidation session.tokenkey=session.tokenkey crowd.server.url=http\://localhost\:8095/crowd/services/ application.name=crowd-openid-server #application.login.url.template=http\://localhost\:8095/openidserver?returnToUrl\=${RETURN_TO_URL} application.login.url.template=https\://auth.mbari.org/openidserver?returnToUrl\=${RETURN_TO_URL} session.isauthenticated=session.isauthenticated #application.base.url=http\://localhost\:8095/openidserver application.base.url=https\://auth.mbari.org/openidserver #application.login.url=http\://localhost\:8095/openidserver application.login.url=https\://auth.mbari.org/openidserver session.validationinterval=0 application.password=password {noformat} and that seems to have fixed it. # (/) It is finally time to move on to the version 4 upgrade ... holy crap. I first went to the *new* crowd install (auth.mbari.org) and logged in as the crowdadm. # (/) I clicked on Applications, then on Add Application # (/) I selected JIRA from the Application type drop-down # (/) I entered jira445 as the username. Ask Kevin about the password. # (/) I used http://bugs.shore.mbari.org:8081 as the URL # (/) I used 134.89.12.31 as the IP address. # (/) I selected only the MBARI LDAP directory. # (/) Then I selected "Allow all users to authenticate" # (/) Then I clicked on "Add Application" # (/) I VNC'd into bugs.mbari.org. As it turns out, for Linux, there is an installer program to download. I downloaded the .bin for 64 bit Linux installer and moved it to the jira-upgrade directory. # (/) I chmod'd the file to make it executable and ran it. It gave me a warning about not being root, but I went ahead with it. # (/) It asked for the JIRA home and data directory, which I specified as /opt/jira4 and /data/jira445. # (/) For the ports, I specified 8180 and 8105 (HTTP and control respectively). It then extracted all the files and launched JIRA. It said if finished, so I opened a local browser to http://localhost:8180 which kicked off the start up wizard. # (/) I specified the external database using: ## solstice2.shore.mbari.org (server) ## 1433 (port) ## jira4 (database) ## DB_Collaboration (username) ## (password ask Kevin) ## dbo (schema) # But all this failed as it seems to just want to try and use the SQL server authentication instead of domain. I will have to do it manually. # (/) I stopped the server using the bin/stop-jira.sh script. # (/) I created and edited /data/jira445/dbconfig.xml and made it look like the following: {noformat} ?xml version="1.0" encoding="UTF-8"?> defaultDS default mssql jiraschema jdbc:jtds:sqlserver://solstice2.shore.mbari.org:1433/Jira4;domain=SHORE;useNTLMv2=true net.sourceforge.jtds.jdbc.Driver DB_Collaboration (ask Kevin) 15 {noformat} # (/) I then started it again using bin/start-jira.sh and tailed the catalina.out file. Got a bunch of errors related to the schema 'jiraschema', I edited the file and changed the schema to 'dbo' and restarted. That seemed to do it. There was one stack trace for some iCal plugin, but looks OK other than that. # I browsed back to localhost:8180 and the wizard moved to step 2. There was an option to import existing data bit without the crowd connection, I thought I should set it up manually, connect to crowd, then import. I generated an evaluation license, called the app "MBARI JIRA4" and change the server in the url to bugs.shore.mbari.org # For the admin, I created an account called 'jiraadm' (ask Kevin for password). # Since this is a temporary system, I left the email system disabled. # I logged in as jiraadm, went to Administration, then Users, then clicked on Add Directory and chose Atlassian Crowd. Note that I had to set the server URL to http://auth.mbari.org:8095/crowd or I would have had to configure all this SSL crap that I did not want to do for this temporary install. # It tested successfully, I clicked Save and it went through a 13 second sync, whew! # I then went to System->Import and Export->Restore System # I copied the jira-upgrade-3.13.5.zip file from the previous version export into /data/jira445/import and then entered that file name along with the new evaluation license again. # I worked through progress bar after I clicked on Restore (it took a really long time). # I then stopped, restarted and tailed the log file. # I am thinking now I should have put the attachments in the import attachments directory, but I am hoping I can just copy them to the data/attachments directory. # UG! I got some error during the import. The exception read: "JIRA is unable to migrat the User Directory configuration because external users exist but the osuser.xml file is not available". It then gave me a link to a doc that talked about making the old user files available before the upgrade ... crap. So I needed to copy the osuser.xml and crowd.properties file from atlassian-jira/WEB-INF/classes directory on the old install to the same directory on the new install ... sigh. This means I am going to blow away everything and start over. # I shutdown jira4 # I dropped all things in the database and deleted all content in the /data/jira445 directory (except for the dbconfig.xml file). # I also removed the temp, logs (actually you have to leave the directory, just clear the files) and the work/Catalina/localhost directories from the jira installation. # I then copied the osuser.xml and the crowd.properties files from the 3.13.5 install to the 4 install. # I edited the crowd.properties file in hopes that I could point it to the new crowd install on auth.mbari.org and it would work, but we will see. # I then started jira and tailed the log file. # All looked OK (other than iCal plugin stack trace again), so I went to localhost:8180 and got step 2 of the wizard. I used the same info as before. # I logged in as the local admin account and it looks like the system picked up the crowd connection, but lets see what server it used! Hey it used the one I edited into the file! Sweet ... now let's see if the import works. # I copied the 3.13.5 zip file to the import directory again and this time, I untarred the attachments into the import/attachments directory. # I kicked off the restore as before and it worked through it fine. # Shutdown and restarted system, tailing the log file and then went to localhost:8180 # I can see issues (before logging in) and it all looks good!! The attachments did not move over from the import directory, so I copied the tar file from /data/jira445/import to /data/jira445/data and then untarred it there, then removed the tar file and the import zip file from the import directory. # Now I will try to login using my MBARI account and OMG it actually worked!!! (it even gave my kgomes account Admin privs) # I then performed an export and copied those file to the /data/backups/4.4.5 directory (also created a TAR of the attachments and put there too). # Now on to version 5! # OK, so something strange is happening. After the imports, the server ID goes back to the one that is on our current production server, which must mean it is using our current license key (which does not match the server ID, BTW). Oh well, I will press on! # I created a /data/jira5211 directory as well as a /opt/jira5 directory. Knowing what I know now and reading through the install instructions, it appears that I need to create a dbconfig.xml file manually, so I did that using: {noformat} defaultDS default mssql dbo jdbc:jtds:sqlserver://solstice2.shore.mbari.org:1433/Jira5;domain=SHORE;useNTLMv2=true net.sourceforge.jtds.jdbc.Driver DB_Collaboration (ask Kevin) 20 20 30000 20 true 300 select 1 60000 300000 true false {noformat} # I then changed the mode to executable on the installer download and ran that. # I had to choose a "custom install" this time through, but the properties were similar after that (ports I used were 8280 and 8205) # I then browsed to localhost:8280 # I dropped me to a wizard where I define the title as "MBARI JIRA5", and changed host to bugs.shore.mbari.org (from localhost) # This license was a little different in that is just asked for my Atlassian username and password and fetched a new license for me. # For the admin account, I used the same 'jiraadm' account # Left email notification disabled. # I created a new application in crowd for JIRA 5 and used same account info as for 4. # In JIRA, I went to Administration->Users->User Directories and then added a directory as I had done before. # All went well and the sync happened. # I then went to Administration->System->Import and Export->Restore System # I copied the backup of 4.4.5 to the /data/jira5211/import directory and then specified that file name. I did not specify a license as it seems to use the old one and it said so in the text below the box. # Clicked on restore and while it was restoring, I untarred the attachments to the /data/jira5211/data directory # After the restore, I shutdown and restarted JIRA tailing the log file. # Browsed to localhost:8280 and ... success! I see issues before logging in and ... my MBARI login worked, I was admin and all is good!!!! # As with previous version, I ran a backup of the DB and attachments and placed in /data/backups/5.2.11 # I poked around a little and there seems to be an issue in the comments that they are still referencing oceana??? I will have to look into this. # I then re-did the process once again for version 6.4.9. I will only put notes about things that are dramatically different below: ## It looks like the dbconfig.xml file is the same as it is for version 5, so I just copied and edited to point to Jira6 DB. ## I used ports 8380 and 8305 {warning:title=Collation} The DB needs to be using a specific collation that it's not, I will have to correct that on the production run {warning} ## It gave me a choice on "how I wanted to use JIRA" and I chose the default (top) one which was just JIRA. ## Something did not go well on the restore (got to 90%) from backup up and the server seems to have crashed, but it looks like it tried to restart? ## I forced a stop and start and tailed the log file. Could it be related to the collation issue? Upon restart it re-ran the indexing. Looks like it worked OK, let me login with my MBARI account. ## Interesting, the comments pointing to oceana seems to have fixed itself in the step of the upgrade. ## Another interesting note, when I went to the Admin->System->General configuration, it had the base URL as oceana, that would explain it. So I edited that to bugs.shore.mbari.org (it also made me change the Mode to private, which makes sense since authentication is external). ## I went back to the 3, 4, and 5 install and changed the base URL there too. That fixed that issue. # I then sent an email to all hands giving the URLs for folks to look at.]]> 27558219 19073916 19041226 19073915 19041225 13959474 13926712 19073918 19041228 13959472 13926710 27590992 4.4: [https://confluence.atlassian.com/display/JIRA044/Migrating+JIRA+to+Another+Server] ## The JIRA configuration tool: [https://confluence.atlassian.com/display/JIRA044/Using+the+JIRA+Configuration+Tool] h5. Steps # (/) Create new VM named bugs.mbari.org in the DMZ # (/) Have Neil create database Jira_Temp on solstice2.shore.mbari.org # (/) Have Neil create database Jira on solstice2.shore.mbari.org # (/) Have Pat install Java 7 on bugs.shore.mbari.org # (/) Have Pete plumb holes through firewall so processes on bugs.mbari.org can get to Solstice2 # (/) Have Pat create DB_Collaboration account on bugs so it can run JIRA under that account and it can connect to solstice2 using that NT Domain account. # (/) Upgrade license on Atlassian site # (/) Log into bugs.shore.mbari.org # (/) Download 3.13.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 4.4.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 5.2.11 standalone Linux 64 bit tar.gz (not sure this version is necessary, but at least I have it) # (/) Unzip and untar the file to /opt # (/) Download latest JIRA (6.4.7 as of this writing). # (/) Unzip and untar it to /opt # Performed Test Upgrade ## (/) In order to export the current stuff in JIRA, I had to shut off access so people could not change the data while I was backing it up. ## (/) I ssh'd to oceana.mbari.org as root and edited the /opt/jira/conf/server.xml file and commented out the Connector section that had the port of 8010 to shut it off from the normal serving route. ## (/) I uncommented the 8082 port connector and the 8443 port connector so that I could still get to the server. ## (/) I stopped and started the JIRA server and in the log file I got a "keystore was tampered with..." which is not surprising. ## (/) I could then browser over to http://oceana.mbari.org:8082/jira ## (/) Then through the Administration console, I did an XML backup ## (/) I then created a tar of all the attachments in the /data/jira_3_12/attachments directory ## (/) I moved both the XML and tar files to the /root/jira-upgrade directory ## (/) I then reversed the changes to the server.xml file and shut down JIRA ## (/) I left it down during the next steps in case it went so well, I could just point people to the new server (yeah, right). ## (/) I then browsed to the crowd server on oceana and add a new application using: ### URL: http://bugs.mbari.org/jira3135 ### IP: 134.89.2.29 ### Name: JIRA3135 ### Password: (ask Kevin) :) ## (/) On bugs, I made a copy of the JIRA 3.13.5 download in the /opt directory and unzipped and untarred it. ## (/) In order to configure the crowd connection I did the following: ### (/) I scp'd the /opt/crowd/client/crowd-integration-client-1.6.jar file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I removed the existing 1.6.1 crowd client jar from the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I scp'd the /opt/crowd/client/conf/crowd.properties file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I scp'd the /opt/crowd/client/conf/crowd-ehcache.xml file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I edited the crowd.properties file on bugs to look like: {noformat} application.name JIRA3135 application.password (ask Kevin) application.login.url http://oceana.mbari.org:8095/crowd/console/ crowd.server.url http://oceana.mbari.org:8095/crowd/services/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 0 session.lastvalidation session.lastvalidation {noformat} ### (/) I edited the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/osuser.xml file to comment out the current authentication mechanism and then uncomment the crowd one. ## (/) I then edited the /opt/atlassian-jira-standalone-3.13.5/conf/server/xml file and configured the database connection to the Jira_Temp database on Solstice2. I looked like this: {noformat} {noformat} ## (/) Edit the /opt/atlassian/jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/entityengine.xml and changed it from 'hsql' to 'mssql' and delete the line with "PUBLIC" in it per the instructions in the comments in that file. ## (/) I edited the /etc/httpd/conf/httpd.conf file and created a proxy pass at the bottom of the file to point a normal URL to the default port 8080 for JIRA: {noformat} # Proxy Pass for JIRA ProxyPass http://bugs.mbari.org:8080 ProxyPassReverse http://bugs.mbari.org:8080 {noformat} ## (/) I restarted Apache ## (/) I scp'd the jtds driver from oceana to the /opt/atlassian-jira-standalone-3.13.5/common/lib directory (you could down from the internet) ## (/) I then went to the /opt/atlassian-jira-standalone-3.13.5/ directory and ran './bin/startup.sh'. From the log file, I could tell things were hanging. After some troubleshooting I am wondering if the local firewall is preventing the application to get access to the database on solstice2. I can telnet to port 1433, but I can't browse to the base http://bugs.mbari.org from anywhere but the local web browser. I have submitted a ticket. ## (/) I restarted the old JIRA with my hopes dashed :(. ## (/) Pat disabled the firewall on bugs.mbari.org but it still hung trying to connect to solstice2.shore.mbari.org. That is really, really perplexing. Neil mentioned that solstice2 is using Kerberos and solstice is not. Checking with the JTDS docs, version 1.3.1 of the driver added kerberos support, so I downloaded that driver and added the 'userKerberos=true' property to the URL in the server.xml file and restarted. Got an error about no credentials, so added user and password properties to the URL. Nope, no luck. Never did figure this one out, but I had Pat pull the VM inside the firewall and after some thrash it worked. Well, it sort of worked ... sigh. It turns out I had downloaded the standard version instead of the enterprise version. I need to redo this work ... grrr. ## (/) I deleted all the tables in the Jira_Temp database and removed the /data/jira3135/indexes directory (and recreated). ## (/) I downloaded the enterprise version of the 3.13.5 server. I made a copy in the /opt directory and unzipped and untarred the file. ## (/) I went back to crowd and edited the application to change the properties to: ### URL: http://bugs.shore.mbari.org:8080 ### IP: 134.89.12.31 ### Name: jira3135 ### Password: (ask Kevin) :) ## (/) I then repeated the steps above to get the server up and running with the following differences: ### The server name is now bugs.shore.mbari.org ### The paths given above are a little different in that they no longer say "standard" but say "enterprise" ### I deleted the proxy pass as it seemed to have issues before and this is only temporary anyway. ## (/) I then browsed to http://bugs.shore.mbari.org:8080 ## (/) It took me to the start up page and at the top was the option to 'import your existing data'. Seemed too good not to try. I clicked on the link. It asked me for the backup file location and the location where the indexes would be stored. ## (/) I copied the XML zip file and the attachments tar file to the /data/original directory. ## (/) I created the /data/jira3135/indexes and used those directories ... it fired off the import and I waited. ## (/) I tailed the log file to watch the import. Holy crap, it worked!!! I could log in and everything! I copied the results from the log file here for posterity sake: {noformat} 2015-07-22 20:55:45,156 http-8080-Processor22 INFO [jira.action.admin.DataImport] Running data import 2015-07-22 20:55:45,179 http-8080-Processor22 INFO [jira.action.admin.DataImport] Importing data.. 2015-07-22 20:55:45,186 http-8080-Processor22 INFO [jira.action.admin.DataImport] Start parsing XML with SAX Parser 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] XML successfully parsed 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] Removing all entries from the database. 2015-07-22 20:56:24,593 http-8080-Processor22 INFO [jira.action.admin.DataImport] All entries removed. 2015-07-22 20:56:24,594 http-8080-Processor22 INFO [jira.action.admin.DataImport] Started storing 410414 Generic Values 2015-07-22 21:01:51,967 http-8080-Processor22 INFO [jira.action.admin.DataImport] Finished storing Generic Values 2015-07-22 21:01:52,329 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:52,361 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:54,683 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLink' to module 'jira.user.format:profile-link-user-format'. 2015-07-22 21:01:54,724 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullName' to module 'jira.user.format:full-name-user-format'. 2015-07-22 21:01:54,773 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkSearcher' to module 'jira.user.format:profile-link-searcher-user-format'. 2015-07-22 21:01:54,784 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkExternal' to module 'jira.user.format:profile-link-external-user-format'. 2015-07-22 21:01:54,795 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkActionHeader' to module 'jira.user.format:profile-link-action-header-user-format'. 2015-07-22 21:01:54,807 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullProfile' to module 'jira.user.format:full-profile-user-format'. 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/comments 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/issues 2015-07-22 21:01:55,641 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/plugins 2015-07-22 21:01:55,867 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:01:55,871 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/issues does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:55,873 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/comments does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,033 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,257 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,889 http-8080-Processor22 ERROR [atlassian.jira.upgrade.ConsistencyCheckImpl] Attachments are turned on, but attachment path [/data/jira_3_12/attachments] invalid - disabling attachments 2015-07-22 21:02:13,904 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Detected that an upgrade is needed; existing data at build 299 2015-07-22 21:02:13,907 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Doing Upgrade... 2015-07-22 21:02:13,915 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value' succeeded 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 317 2015-07-22 21:02:13,944 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite filters - make each filter a favourite of its owner. 2015-07-22 21:02:17,822 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build319] Could not find author 'fpy' for filter with id '10040' 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite filters - make each filter a favourite of its owner.' succeeded 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 319 2015-07-22 21:02:17,995 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise Share Permissions. Move old shares to new shares. 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise Share Permissions. Move old shares to new shares.' succeeded 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 321 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Migrating the old JIRA UI colors to the new JIRA 3.13 colors 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build322] Custom color detected for jira.lf.menu.bgcolour : #336699 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Migrating the old JIRA UI colors to the new JIRA 3.13 colors' succeeded 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 322 2015-07-22 21:02:18,025 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite dashboards - make each dashboard a favourite of its owner. 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'cmcgann' for dashboard with id '10030' 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'fpy' for dashboard with id '10060' 2015-07-22 21:02:18,423 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'kanna' for dashboard with id '10040' 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite dashboards - make each dashboard a favourite of its owner.' succeeded 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 325 2015-07-22 21:02:18,625 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Reindexing all data in JIRA to include Favourites. 2015-07-22 21:02:18,648 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All starting... 2015-07-22 21:02:18,650 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 0% complete. Current index: Issue 2015-07-22 21:02:18,654 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:02:18,809 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 1% complete. Current index: Issue 2015-07-22 21:02:18,855 indexerPool-2-thread-10 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 2% complete. Current index: Issue 2015-07-22 21:02:18,899 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 3% complete. Current index: Issue 2015-07-22 21:02:18,945 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 4% complete. Current index: Issue 2015-07-22 21:02:19,012 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 5% complete. Current index: Issue . . . 2015-07-22 21:02:26,164 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 95% complete. Current index: Issue 2015-07-22 21:02:26,232 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 96% complete. Current index: Issue 2015-07-22 21:02:26,316 indexerPool-2-thread-9 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 97% complete. Current index: Issue 2015-07-22 21:02:26,771 indexerPool-2-thread-3 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: Issue 2015-07-22 21:02:27,261 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 8607ms. Indexer: DefaultIndexManager: paths: [/data/jira3135/indexes/issues, /data/jira3135/indexes/comments] 2015-07-22 21:02:27,263 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: SearchRequest 2015-07-22 21:02:27,268 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,293 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: SearchRequest 2015-07-22 21:02:27,308 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: PortalPage 2015-07-22 21:02:27,312 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,377 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: PortalPage 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 115ms. Indexer: SharedEntityIndexManager: paths: [/data/jira3135/indexes/entities/portalpage, /data/jira3135/indexes/entities/searchrequest] 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All complete. Total time: 8722ms. 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Reindexing all data in JIRA to include Favourites.' succeeded 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 326 2015-07-22 21:02:27,397 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade succeeded! Setting data build number to 360 2015-07-22 21:02:27,469 JiraQuartzScheduler_Worker-0 WARN [service.services.export.ExportService] Backup directory /data/jira_3_12/backup does not exist {noformat} {warning:title=Paths} It appears that the upgraded JIRA will still look for the attachments and the backup locations in the original places. So I created /data/jira_3_12/backup and untarred the original attachments to /data/jira_3_12 and then everything worked (including attachements) in the new JIRA. {warning} ## (/) I then used the upgraded JIRA to generate a new XML backup and stored it in /data/original/3.13.5 along with another tar of the files in /data/jira_3_12/attachments. ## (/) I then shutdown the JIRA server. *I should be ready to move on to version 4 upgrade WHEW* ## So, before moving on, I decided that it would be a really good idea to spin up a new Crowd instance to get rid of the :8443 in the URL and to move off of RedHat per IS requests. I have a ticket in for a new VM and a new database to try to get this going. I am waiting on that before moving on. ## (/) Pat created the VM and Neil created the database. ## (/) I logged into auth.mbari.org (name of the VM) and downloaded crowd which I unzipped to the /opt directory ## (/) I then created a /data/crowd directory and gave my account permissions on it and then edited the /opt/atlassian..../crowd-webapp/WEB-INF/classes/crowd-init.properties file to set that as the crowd home directory. ## (/) The instructions say to download the JDBC driver, but they already have JTDS 1.2.7 in the download so I did not do anything. ## (/) You have to manually connect up CrowdID to a database as they setup wizard does not currently do this. ### (/) They say to download the driver, but again 1.2.7 was there so I did nothing. ### (/) I edited the /opt/atlassian.../apache-tomcat/conf/Catalina/localhost/openidserver.xml to look like: {noformat} {noformat} ### (/) I edited the /opt/atlassian.../build.properties files to look like: {noformat} # Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See https://confluence.atlassian.com/display/CROWD/Connecting+Crowd+to+a+Database hibernate.dialect=org.hibernate.dialect.SQLServerDialect # The Hibernate transaction factory to use. See https://confluence.atlassian.com/display/CROWD/Configuring+Crowd hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory # The http port you wish to run crowd from, ie: http://localhost:8095/crowd crowd.tomcat.connector.port=8095 # Tomcat requires a unique port for shutdown crowd.tomcat.shutdown.port=8020 # Crowd context root crowd.url=http://localhost:8095/crowd # Demo context root demo.url=http://localhost:8095/demo # OpenID server context root openidserver.url=http://localhost:8095/openidserver {noformat} ### (/) I then ran the build.sh script in the root of /opt/atlassian... ## (/) I fired up crowd using the /opt/atlassian.../start_crowd.sh script ## (/) I then went to http://auth.mbari.org:8095/crowd to kick off the start up wizard ## (/) I grabbed a new eval license from my account on atlassian and pasted into the license page. ## (/) I selected "New install" on the next page. ## (/) I configured the JDBC connection using this connection URL with user DB_Collaboration {noformat} jdbc:jtds:sqlserver://dione.mbari.org:51001/Crowd;domain=SHORE;useNTLMv2=TRUE {noformat} ## (/) I left the "Options" as they came up {warning:title=Paths} Not sure if this is a problem, but because I started the set up using auth.mbari.org, it set the Base URL to http://auth.mbari.org:8095/crowd instead of localhost. Hope that is not a problem. We will see. {warning} ## (/) I configured the email connection using the settings from [here|https://wind.shore.mbari.org/is/howto/email/mbarimail/imap] and I used my network login (probably shouldn't be doing that ... not sure where it stores my password, but I am assuming in the DB). ## (/) For the local admin account, I created a user named 'crowdadm' so it would not clash with my LDAP account. See Kevin Gomes for password information. ## (/) I checked the OpenID server as an integrated application ## (/) It then took me to the login page and I logged in using the newly minted admin account. Seemed all is well so far. ## (/) I visited the openidserver URL as well and that seemed OK. ## (/) I decided to wait on configuring the MBARI LDAP directory until I got everything with SSL working. ## (/) Now the next step was to follow the directions to configure Crowd to run over SSL found [here|https://confluence.atlassian.com/display/CROWD/Configuring+Crowd+to+Work+with+SSL] ## (/) I shutdown crowd. Note that the stop script does not shutdown things correctly and I noticed the crowd app running as root. That should not be if I started as kgomes. Not sure what is up with that. ## (/) Now Joe had already configured SSL once, so I used his connector configuration in the server.xml file and so the final file looked like: {noformat} {noformat} ## (/) I then edited the /data/crowd/crowd.properties to look like: {noformat} #Sat Aug 01 09:05:15 PDT 2015 session.lastvalidation=session.lastvalidation session.tokenkey=session.tokenkey crowd.server.url=https\://localhost\:8443/crowd/services/ application.name=crowd http.timeout=30000 session.isauthenticated=session.isauthenticated application.login.url=https\://localhost\:8443/crowd/console/ session.validationinterval=0 application.password=Y1Xp3OorCmsOP4eruL1dmH {noformat} One thing to note here is that based on a comment from the SSL configuration page at atlassian (Steve's comment), you are supposed to leave all the host names the same. For example, if the file says localhost, leave it localhost. So this created a bit of a problem based on the fact that I had left the base URL pointing to auth.mbari.org in the wizard steps above. That step wrote auth.mbari.org to the /data/crowd/crowd.properties. All the other files reference localhost, so to be consistent, I changed auth.mbari.org to localhost in the /data/crowd/crowd.properties file. We will see if this works. ## (/) Per the instructions on the atlassian page (referenced above), I also edited the build.properties file and the /client/conf/crowd.properties files before I restarted and used the SSL URLs ## build.properties: {noformat} # Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See https://confluence.atlassian.com/display/CROWD/Connecting+Crowd+to+a+Database hibernate.dialect=org.hibernate.dialect.SQLServerDialect # The Hibernate transaction factory to use. See https://confluence.atlassian.com/display/CROWD/Configuring+Crowd hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory # The http port you wish to run crowd from, ie: http://localhost:8095/crowd crowd.tomcat.connector.port=8095 # Tomcat requires a unique port for shutdown crowd.tomcat.shutdown.port=8020 # Crowd context root crowd.url=https://localhost:8443/crowd # Demo context root demo.url=https://localhost:8443/demo # OpenID server context root openidserver.url=https://localhost:8443/openidserver {noformat} ## crowd.properties (client) {noformat} application.name crowd application.password password application.login.url https://localhost:8443/crowd/console/ crowd.server.url https://localhost:8443/crowd/services/ crowd.base.url https://localhost:8443/crowd/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 2 session.lastvalidation session.lastvalidation {noformat} ## (/) Although not stated, I am assuming you would need to run the build.sh script to push the build.properties changes to their proper places, so I did that. Note that before doing that, I know that it will clobber the server.xml changes I made, so I made a copy of that file and diff'd them after and then rolled the previous changes to the new server.xml file. Actually, amazingly enough, it seems to have done the connector entry correctly so I left it after running the build.sh script. ## (/) Crossed my fingers and then restarted crowd. I tailed the catalina.out file and did not see any stack traces so that is a good sign! ## (/) I visited https://auth.mbari.org:8443/crowd first. It could not find that page, but I suspect that is because I am browsing from the outside, so I tried just https://auth.mbari.org/crowd and got a service unavailable. I am suspecting that this is a combination of firewall and proxy pass and I will send this info to Joe. From what I can see on the crowd side, it seems like the server started cleanly, we just can't get to it. I tried to reach it from a browser on the machine itself too (through VNC) with the same service not available. ## (/) Here are the notes from Joe after he fixed it! Wooohooo! {noformat} Hey Kevin, Thanks for starting clean! I had to make a few adjustments. 1-I modified the server.xml file in /opt/atlassian-crowd-2.8.3/apache-tomcat/conf/server.xml so there are two connectors per the instructions on the Atlassian site. I have backed up this good server.xml file in /etc/temp/ if you want to browse it to see what I did. Of note is that I removed all the jargon referencing the types of ciphers available to simplify things for now. 2-I modified /data/crowd/crowd.properties to have crowd.server.url=https\://localhost\:8443/crowd/services/ application.login.url=https\://localhost\:8443/crowd/console/ But that would cause my login to error with an error saying it was unable to reach the authentication server. I scratched my head for a bit. When I revert the values to just using non-SSL and try to log in, I just get an "invalid login" (I don't know the crowdadm password). So I worked under the assumption that if I can configure SSL to get an "invalid login" when logging in then it would work when provided real credentials. So, I then changed /data/crowd/crowd.proprties to: crowd.server.url=https\://auth.mbari.org\:8443/crowd/services/ application.login.url=https\://auth.mbari.org\:8443/crowd/console/ And now when I try to log in with SSL it says "invalid login". Strange because all the other values I can find only show "localhost" .. in any case... Can you try to log in now? {noformat} ## (/) Next I moved on to configuring the connection to MBARI's LDAP server to enable our logins through Crowd and CrowdID ## (/) I clicked on "Add Directory" in crowd. ## (/) I selected "Connector" then clicked Next ## (/) I put ldap.shore.mbari.org as the name of the server ## (/) I selected "Use memberOf for group memberships" ## (/) I used "OU=AllUsers,DC=shore,DC=mbari,DC=org" for the Base DN ## (/) I used "CN=LDAPbind,OU=Special,OU=AllUsers,DC=shore,DC=mbari,DC=org" for the Username (talk to Pat Allen for password) ## (/) I tested the connection (button click) and it passed. ## (/) I de-selected all the capabilities of the connector as it is a ready only connector and then saved it. It synchronized correctly! ## (/) At first, I could not login using my MBARI credentials, but after going to the "crowd" application in crowd (logged in as the local admin), I had to add the LDAP directory and configure it to "Allow all to authenticate", then I was able to login. After this, the last step was to get this to run as a different user and lock down various directories. I went through the entire directory structure /opt/atlassian... and set up so that root owned all read-only locations and DB_Collaboration (account set up by IS) owned the other stuff. I also gave full ownership to the /data/crowd directory to DB_Collaboration so it could write there. Pat set up a script to start on boot and after a little tweaking, it now starts on boot. {warning:title=CrowdID log file} One thing that came up here was that when the crowdID application ran, it tried to write a log file to the location where the process was launched from (which is /opt/atlassian...). This is a bad thing and I figured out that I could change that location by changing the file /opt/atlassian-crowd-2.8.3/crowd-openidserver-webapp/WEB-INF/classes/log4j.properties and hardcoding the /data/crowd/logs/atlassian-crowd-openid-server.log and then restarted the application. {warning} ## (/) Another note is the when an application tried to use the OpenID application, it would get redirected to localhost. I changed the /opt/atlassian.../crowd-openidserver-webapp/WEB-INF/classes/crowd.properties file to look like: {noformat} #Sat Aug 01 10:03:18 PDT 2015 session.lastvalidation=session.lastvalidation session.tokenkey=session.tokenkey crowd.server.url=http\://localhost\:8095/crowd/services/ application.name=crowd-openid-server #application.login.url.template=http\://localhost\:8095/openidserver?returnToUrl\=${RETURN_TO_URL} application.login.url.template=https\://auth.mbari.org/openidserver?returnToUrl\=${RETURN_TO_URL} session.isauthenticated=session.isauthenticated #application.base.url=http\://localhost\:8095/openidserver application.base.url=https\://auth.mbari.org/openidserver #application.login.url=http\://localhost\:8095/openidserver application.login.url=https\://auth.mbari.org/openidserver session.validationinterval=0 application.password=password {noformat} and that seems to have fixed it. # (/) It is finally time to move on to the version 4 upgrade ... holy crap. I first went to the *new* crowd install (auth.mbari.org) and logged in as the crowdadm. # (/) I clicked on Applications, then on Add Application # (/) I selected JIRA from the Application type drop-down # (/) I entered jira445 as the username. Ask Kevin about the password. # (/) I used http://bugs.shore.mbari.org:8081 as the URL # (/) I used 134.89.12.31 as the IP address. # (/) I selected only the MBARI LDAP directory. # (/) Then I selected "Allow all users to authenticate" # (/) Then I clicked on "Add Application" # (/) I VNC'd into bugs.mbari.org. As it turns out, for Linux, there is an installer program to download. I downloaded the .bin for 64 bit Linux installer and moved it to the jira-upgrade directory. # (/) I chmod'd the file to make it executable and ran it. It gave me a warning about not being root, but I went ahead with it. # (/) It asked for the JIRA home and data directory, which I specified as /opt/jira4 and /data/jira445. # (/) For the ports, I specified 8180 and 8105 (HTTP and control respectively). It then extracted all the files and launched JIRA. It said if finished, so I opened a local browser to http://localhost:8180 which kicked off the start up wizard. # (/) I specified the external database using: ## solstice2.shore.mbari.org (server) ## 1433 (port) ## jira4 (database) ## DB_Collaboration (username) ## (password ask Kevin) ## dbo (schema) # But all this failed as it seems to just want to try and use the SQL server authentication instead of domain. I will have to do it manually. # (/) I stopped the server using the bin/stop-jira.sh script. # (/) I created and edited /data/jira445/dbconfig.xml and made it look like the following: {noformat} ?xml version="1.0" encoding="UTF-8"?> defaultDS default mssql jiraschema jdbc:jtds:sqlserver://solstice2.shore.mbari.org:1433/Jira4;domain=SHORE;useNTLMv2=true net.sourceforge.jtds.jdbc.Driver DB_Collaboration (ask Kevin) 15 {noformat} # (/) I then started it again using bin/start-jira.sh and tailed the catalina.out file. Got a bunch of errors related to the schema 'jiraschema', I edited the file and changed the schema to 'dbo' and restarted. That seemed to do it. There was one stack trace for some iCal plugin, but looks OK other than that. # I browsed back to localhost:8180 and the wizard moved to step 2. There was an option to import existing data bit without the crowd connection, I thought I should set it up manually, connect to crowd, then import. I generated an evaluation license, called the app "MBARI JIRA4" and change the server in the url to bugs.shore.mbari.org # For the admin, I created an account called 'jiraadm' (ask Kevin for password). # Since this is a temporary system, I left the email system disabled. # I logged in as jiraadm, went to Administration, then Users, then clicked on Add Directory and chose Atlassian Crowd. Note that I had to set the server URL to http://auth.mbari.org:8095/crowd or I would have had to configure all this SSL crap that I did not want to do for this temporary install. # It tested successfully, I clicked Save and it went through a 13 second sync, whew! # I then went to System->Import and Export->Restore System # I copied the jira-upgrade-3.13.5.zip file from the previous version export into /data/jira445/import and then entered that file name along with the new evaluation license again. # I worked through progress bar after I clicked on Restore (it took a really long time). # I then stopped, restarted and tailed the log file. # I am thinking now I should have put the attachments in the import attachments directory, but I am hoping I can just copy them to the data/attachments directory. # UG! I got some error during the import. The exception read: "JIRA is unable to migrat the User Directory configuration because external users exist but the osuser.xml file is not available". It then gave me a link to a doc that talked about making the old user files available before the upgrade ... crap. So I needed to copy the osuser.xml and crowd.properties file from atlassian-jira/WEB-INF/classes directory on the old install to the same directory on the new install ... sigh. This means I am going to blow away everything and start over. # I shutdown jira4 # I dropped all things in the database and deleted all content in the /data/jira445 directory (except for the dbconfig.xml file). # I also removed the temp, logs (actually you have to leave the directory, just clear the files) and the work/Catalina/localhost directories from the jira installation. # I then copied the osuser.xml and the crowd.properties files from the 3.13.5 install to the 4 install. # I edited the crowd.properties file in hopes that I could point it to the new crowd install on auth.mbari.org and it would work, but we will see. # I then started jira and tailed the log file. # All looked OK (other than iCal plugin stack trace again), so I went to localhost:8180 and got step 2 of the wizard. I used the same info as before. # I logged in as the local admin account and it looks like the system picked up the crowd connection, but lets see what server it used! Hey it used the one I edited into the file! Sweet ... now let's see if the import works. # I copied the 3.13.5 zip file to the import directory again and this time, I untarred the attachments into the import/attachments directory. # I kicked off the restore as before and it worked through it fine. # Shutdown and restarted system, tailing the log file and then went to localhost:8180 # I can see issues (before logging in) and it all looks good!! The attachments did not move over from the import directory, so I copied the tar file from /data/jira445/import to /data/jira445/data and then untarred it there, then removed the tar file and the import zip file from the import directory. # Now I will try to login using my MBARI account and OMG it actually worked!!! (it even gave my kgomes account Admin privs) # I then performed an export and copied those file to the /data/backups/4.4.5 directory (also created a TAR of the attachments and put there too). # Now on to version 5! # OK, so something strange is happening. After the imports, the server ID goes back to the one that is on our current production server, which must mean it is using our current license key (which does not match the server ID, BTW). Oh well, I will press on! # I created a /data/jira5211 directory as well as a /opt/jira5 directory. Knowing what I know now and reading through the install instructions, it appears that I need to create a dbconfig.xml file manually, so I did that using: {noformat} defaultDS default mssql dbo jdbc:jtds:sqlserver://solstice2.shore.mbari.org:1433/Jira5;domain=SHORE;useNTLMv2=true net.sourceforge.jtds.jdbc.Driver DB_Collaboration (ask Kevin) 20 20 30000 20 true 300 select 1 60000 300000 true false {noformat} # I then changed the mode to executable on the installer download and ran that. # I had to choose a "custom install" this time through, but the properties were similar after that (ports I used were 8280 and 8205) # I then browsed to localhost:8280 # I dropped me to a wizard where I define the title as "MBARI JIRA5", and changed host to bugs.shore.mbari.org (from localhost) # This license was a little different in that is just asked for my Atlassian username and password and fetched a new license for me. # For the admin account, I used the same 'jiraadm' account # Left email notification disabled. # I created a new application in crowd for JIRA 5 and used same account info as for 4. # In JIRA, I went to Administration->Users->User Directories and then added a directory as I had done before. # All went well and the sync happened. # I then went to Administration->System->Import and Export->Restore System # I copied the backup of 4.4.5 to the /data/jira5211/import directory and then specified that file name. I did not specify a license as it seems to use the old one and it said so in the text below the box. # Clicked on restore and while it was restoring, I untarred the attachments to the /data/jira5211/data directory # After the restore, I shutdown and restarted JIRA tailing the log file. # Browsed to localhost:8280 and ... success! I see issues before logging in and ... my MBARI login worked, I was admin and all is good!!!! # As with previous version, I ran a backup of the DB and attachments and placed in /data/backups/5.2.11 # I poked around a little and there seems to be an issue in the comments that they are still referencing oceana??? I will have to look into this. # I then re-did the process once again for version 6.4.9. I will only put notes about things that are dramatically different below: ## It looks like the dbconfig.xml file is the same as it is for version 5, so I just copied and edited to point to Jira6 DB. ## I used ports 8380 and 8305 {warning:title=Collation} The DB needs to be using a specific collation that it's not, I will have to correct that on the production run {warning} ## It gave me a choice on "how I wanted to use JIRA" and I chose the default (top) one which was just JIRA. ## Something did not go well on the restore (got to 90%) from backup up and the server seems to have crashed, but it looks like it tried to restart? ## I forced a stop and start and tailed the log file. Could it be related to the collation issue? Upon restart it re-ran the indexing. Looks like it worked OK, let me login with my MBARI account. ## Interesting, the comments pointing to oceana seems to have fixed itself in the step of the upgrade. ## Another interesting note, when I went to the Admin->System->General configuration, it had the base URL as oceana, that would explain it. So I edited that to bugs.shore.mbari.org (it also made me change the Mode to private, which makes sense since authentication is external). ## I went back to the 3, 4, and 5 install and changed the base URL there too. That fixed that issue. # I then sent an email to all hands giving the URLs for folks to look at. # While folks were looking over the upgrade instances, I went ahead and created the cloud instance at Atlassian so I could test upload the JIRA backup from 6.4.9 {warning:title=Disable Remote Crowd Directory} As a part of the test import, I discovered that you have to disable the remote crowd directory through User Management->User Directories *before* you do the backup/export. {warning}]]> 27558229 4489350 4456591 19073891 19041200 13959482 13926720 19073892 19041201 13959481 13926719 19073893 19041202 13959480 13926718 19073895 19041204 19073897 19041206 13959476 13926714 19073899 19041208 19073900 19041209 13959484 13926722 27590948 4.4: [https://confluence.atlassian.com/display/JIRA044/Migrating+JIRA+to+Another+Server] ## The JIRA configuration tool: [https://confluence.atlassian.com/display/JIRA044/Using+the+JIRA+Configuration+Tool] h5. Steps # (/) Create new VM named bugs.mbari.org in the DMZ # (/) Have Neil create database Jira_Temp on solstice2.shore.mbari.org # (/) Have Neil create database Jira on solstice2.shore.mbari.org # (/) Have Pat install Java 7 on bugs.shore.mbari.org # (/) Have Pete plumb holes through firewall so processes on bugs.mbari.org can get to Solstice2 # (/) Have Pat create DB_Collaboration account on bugs so it can run JIRA under that account and it can connect to solstice2 using that NT Domain account. # (/) Upgrade license on Atlassian site # (/) Log into bugs.shore.mbari.org # (/) Download 3.13.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 4.4.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 5.2.11 standalone Linux 64 bit tar.gz (not sure this version is necessary, but at least I have it) # (/) Unzip and untar the file to /opt # (/) Download latest JIRA (6.4.7 as of this writing). # (/) Unzip and untar it to /opt # Performed Test Upgrade ## (/) In order to export the current stuff in JIRA, I had to shut off access so people could not change the data while I was backing it up. ## (/) I ssh'd to oceana.mbari.org as root and edited the /opt/jira/conf/server.xml file and commented out the Connector section that had the port of 8010 to shut it off from the normal serving route. ## (/) I uncommented the 8082 port connector and the 8443 port connector so that I could still get to the server. ## (/) I stopped and started the JIRA server and in the log file I got a "keystore was tampered with..." which is not surprising. ## (/) I could then browser over to http://oceana.mbari.org:8082/jira ## (/) Then through the Administration console, I did an XML backup ## (/) I then created a tar of all the attachments in the /data/jira_3_12/attachments directory ## (/) I moved both the XML and tar files to the /root/jira-upgrade directory ## (/) I then reversed the changes to the server.xml file and shut down JIRA ## (/) I left it down during the next steps in case it went so well, I could just point people to the new server (yeah, right). ## (/) I then browsed to the crowd server on oceana and add a new application using: ### URL: http://bugs.mbari.org/jira3135 ### IP: 134.89.2.29 ### Name: JIRA3135 ### Password: (ask Kevin) :) ## (/) On bugs, I made a copy of the JIRA 3.13.5 download in the /opt directory and unzipped and untarred it. ## (/) In order to configure the crowd connection I did the following: ### (/) I scp'd the /opt/crowd/client/crowd-integration-client-1.6.jar file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I removed the existing 1.6.1 crowd client jar from the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I scp'd the /opt/crowd/client/conf/crowd.properties file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I scp'd the /opt/crowd/client/conf/crowd-ehcache.xml file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I edited the crowd.properties file on bugs to look like: {noformat} application.name JIRA3135 application.password (ask Kevin) application.login.url http://oceana.mbari.org:8095/crowd/console/ crowd.server.url http://oceana.mbari.org:8095/crowd/services/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 0 session.lastvalidation session.lastvalidation {noformat} ### (/) I edited the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/osuser.xml file to comment out the current authentication mechanism and then uncomment the crowd one. ## (/) I then edited the /opt/atlassian-jira-standalone-3.13.5/conf/server/xml file and configured the database connection to the Jira_Temp database on Solstice2. I looked like this: {noformat} {noformat} ## (/) Edit the /opt/atlassian/jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/entityengine.xml and changed it from 'hsql' to 'mssql' and delete the line with "PUBLIC" in it per the instructions in the comments in that file. ## (/) I edited the /etc/httpd/conf/httpd.conf file and created a proxy pass at the bottom of the file to point a normal URL to the default port 8080 for JIRA: {noformat} # Proxy Pass for JIRA ProxyPass http://bugs.mbari.org:8080 ProxyPassReverse http://bugs.mbari.org:8080 {noformat} ## (/) I restarted Apache ## (/) I scp'd the jtds driver from oceana to the /opt/atlassian-jira-standalone-3.13.5/common/lib directory (you could down from the internet) ## (/) I then went to the /opt/atlassian-jira-standalone-3.13.5/ directory and ran './bin/startup.sh'. From the log file, I could tell things were hanging. After some troubleshooting I am wondering if the local firewall is preventing the application to get access to the database on solstice2. I can telnet to port 1433, but I can't browse to the base http://bugs.mbari.org from anywhere but the local web browser. I have submitted a ticket. ## (/) I restarted the old JIRA with my hopes dashed :(. ## (/) Pat disabled the firewall on bugs.mbari.org but it still hung trying to connect to solstice2.shore.mbari.org. That is really, really perplexing. Neil mentioned that solstice2 is using Kerberos and solstice is not. Checking with the JTDS docs, version 1.3.1 of the driver added kerberos support, so I downloaded that driver and added the 'userKerberos=true' property to the URL in the server.xml file and restarted. Got an error about no credentials, so added user and password properties to the URL. Nope, no luck. Never did figure this one out, but I had Pat pull the VM inside the firewall and after some thrash it worked. Well, it sort of worked ... sigh. It turns out I had downloaded the standard version instead of the enterprise version. I need to redo this work ... grrr. ## (/) I deleted all the tables in the Jira_Temp database and removed the /data/jira3135/indexes directory (and recreated). ## (/) I downloaded the enterprise version of the 3.13.5 server. I made a copy in the /opt directory and unzipped and untarred the file. ## (/) I went back to crowd and edited the application to change the properties to: ### URL: http://bugs.shore.mbari.org:8080 ### IP: 134.89.12.31 ### Name: jira3135 ### Password: (ask Kevin) :) ## (/) I then repeated the steps above to get the server up and running with the following differences: ### The server name is now bugs.shore.mbari.org ### The paths given above are a little different in that they no longer say "standard" but say "enterprise" ### I deleted the proxy pass as it seemed to have issues before and this is only temporary anyway. ## (/) I then browsed to http://bugs.shore.mbari.org:8080 ## (/) It took me to the start up page and at the top was the option to 'import your existing data'. Seemed too good not to try. I clicked on the link. It asked me for the backup file location and the location where the indexes would be stored. ## (/) I copied the XML zip file and the attachments tar file to the /data/original directory. ## (/) I created the /data/jira3135/indexes and used those directories ... it fired off the import and I waited. ## (/) I tailed the log file to watch the import. Holy crap, it worked!!! I could log in and everything! I copied the results from the log file here for posterity sake: {noformat} 2015-07-22 20:55:45,156 http-8080-Processor22 INFO [jira.action.admin.DataImport] Running data import 2015-07-22 20:55:45,179 http-8080-Processor22 INFO [jira.action.admin.DataImport] Importing data.. 2015-07-22 20:55:45,186 http-8080-Processor22 INFO [jira.action.admin.DataImport] Start parsing XML with SAX Parser 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] XML successfully parsed 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] Removing all entries from the database. 2015-07-22 20:56:24,593 http-8080-Processor22 INFO [jira.action.admin.DataImport] All entries removed. 2015-07-22 20:56:24,594 http-8080-Processor22 INFO [jira.action.admin.DataImport] Started storing 410414 Generic Values 2015-07-22 21:01:51,967 http-8080-Processor22 INFO [jira.action.admin.DataImport] Finished storing Generic Values 2015-07-22 21:01:52,329 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:52,361 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:54,683 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLink' to module 'jira.user.format:profile-link-user-format'. 2015-07-22 21:01:54,724 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullName' to module 'jira.user.format:full-name-user-format'. 2015-07-22 21:01:54,773 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkSearcher' to module 'jira.user.format:profile-link-searcher-user-format'. 2015-07-22 21:01:54,784 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkExternal' to module 'jira.user.format:profile-link-external-user-format'. 2015-07-22 21:01:54,795 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkActionHeader' to module 'jira.user.format:profile-link-action-header-user-format'. 2015-07-22 21:01:54,807 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullProfile' to module 'jira.user.format:full-profile-user-format'. 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/comments 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/issues 2015-07-22 21:01:55,641 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/plugins 2015-07-22 21:01:55,867 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:01:55,871 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/issues does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:55,873 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/comments does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,033 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,257 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,889 http-8080-Processor22 ERROR [atlassian.jira.upgrade.ConsistencyCheckImpl] Attachments are turned on, but attachment path [/data/jira_3_12/attachments] invalid - disabling attachments 2015-07-22 21:02:13,904 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Detected that an upgrade is needed; existing data at build 299 2015-07-22 21:02:13,907 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Doing Upgrade... 2015-07-22 21:02:13,915 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value' succeeded 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 317 2015-07-22 21:02:13,944 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite filters - make each filter a favourite of its owner. 2015-07-22 21:02:17,822 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build319] Could not find author 'fpy' for filter with id '10040' 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite filters - make each filter a favourite of its owner.' succeeded 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 319 2015-07-22 21:02:17,995 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise Share Permissions. Move old shares to new shares. 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise Share Permissions. Move old shares to new shares.' succeeded 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 321 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Migrating the old JIRA UI colors to the new JIRA 3.13 colors 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build322] Custom color detected for jira.lf.menu.bgcolour : #336699 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Migrating the old JIRA UI colors to the new JIRA 3.13 colors' succeeded 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 322 2015-07-22 21:02:18,025 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite dashboards - make each dashboard a favourite of its owner. 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'cmcgann' for dashboard with id '10030' 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'fpy' for dashboard with id '10060' 2015-07-22 21:02:18,423 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'kanna' for dashboard with id '10040' 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite dashboards - make each dashboard a favourite of its owner.' succeeded 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 325 2015-07-22 21:02:18,625 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Reindexing all data in JIRA to include Favourites. 2015-07-22 21:02:18,648 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All starting... 2015-07-22 21:02:18,650 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 0% complete. Current index: Issue 2015-07-22 21:02:18,654 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:02:18,809 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 1% complete. Current index: Issue 2015-07-22 21:02:18,855 indexerPool-2-thread-10 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 2% complete. Current index: Issue 2015-07-22 21:02:18,899 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 3% complete. Current index: Issue 2015-07-22 21:02:18,945 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 4% complete. Current index: Issue 2015-07-22 21:02:19,012 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 5% complete. Current index: Issue . . . 2015-07-22 21:02:26,164 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 95% complete. Current index: Issue 2015-07-22 21:02:26,232 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 96% complete. Current index: Issue 2015-07-22 21:02:26,316 indexerPool-2-thread-9 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 97% complete. Current index: Issue 2015-07-22 21:02:26,771 indexerPool-2-thread-3 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: Issue 2015-07-22 21:02:27,261 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 8607ms. Indexer: DefaultIndexManager: paths: [/data/jira3135/indexes/issues, /data/jira3135/indexes/comments] 2015-07-22 21:02:27,263 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: SearchRequest 2015-07-22 21:02:27,268 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,293 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: SearchRequest 2015-07-22 21:02:27,308 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: PortalPage 2015-07-22 21:02:27,312 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,377 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: PortalPage 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 115ms. Indexer: SharedEntityIndexManager: paths: [/data/jira3135/indexes/entities/portalpage, /data/jira3135/indexes/entities/searchrequest] 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All complete. Total time: 8722ms. 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Reindexing all data in JIRA to include Favourites.' succeeded 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 326 2015-07-22 21:02:27,397 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade succeeded! Setting data build number to 360 2015-07-22 21:02:27,469 JiraQuartzScheduler_Worker-0 WARN [service.services.export.ExportService] Backup directory /data/jira_3_12/backup does not exist {noformat} {warning:title=Paths} It appears that the upgraded JIRA will still look for the attachments and the backup locations in the original places. So I created /data/jira_3_12/backup and untarred the original attachments to /data/jira_3_12 and then everything worked (including attachements) in the new JIRA. {warning} ## (/) I then used the upgraded JIRA to generate a new XML backup and stored it in /data/original/3.13.5 along with another tar of the files in /data/jira_3_12/attachments. ## (/) I then shutdown the JIRA server. *I should be ready to move on to version 4 upgrade WHEW* ## So, before moving on, I decided that it would be a really good idea to spin up a new Crowd instance to get rid of the :8443 in the URL and to move off of RedHat per IS requests. I have a ticket in for a new VM and a new database to try to get this going. I am waiting on that before moving on. ## (/) Pat created the VM and Neil created the database. ## (/) I logged into auth.mbari.org (name of the VM) and downloaded crowd which I unzipped to the /opt directory ## (/) I then created a /data/crowd directory and gave my account permissions on it and then edited the /opt/atlassian..../crowd-webapp/WEB-INF/classes/crowd-init.properties file to set that as the crowd home directory. ## (/) The instructions say to download the JDBC driver, but they already have JTDS 1.2.7 in the download so I did not do anything. ## (/) You have to manually connect up CrowdID to a database as they setup wizard does not currently do this. ### (/) They say to download the driver, but again 1.2.7 was there so I did nothing. ### (/) I edited the /opt/atlassian.../apache-tomcat/conf/Catalina/localhost/openidserver.xml to look like: {noformat} {noformat} ### (/) I edited the /opt/atlassian.../build.properties files to look like: {noformat} # Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See https://confluence.atlassian.com/display/CROWD/Connecting+Crowd+to+a+Database hibernate.dialect=org.hibernate.dialect.SQLServerDialect # The Hibernate transaction factory to use. See https://confluence.atlassian.com/display/CROWD/Configuring+Crowd hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory # The http port you wish to run crowd from, ie: http://localhost:8095/crowd crowd.tomcat.connector.port=8095 # Tomcat requires a unique port for shutdown crowd.tomcat.shutdown.port=8020 # Crowd context root crowd.url=http://localhost:8095/crowd # Demo context root demo.url=http://localhost:8095/demo # OpenID server context root openidserver.url=http://localhost:8095/openidserver {noformat} ### (/) I then ran the build.sh script in the root of /opt/atlassian... ## (/) I fired up crowd using the /opt/atlassian.../start_crowd.sh script ## (/) I then went to http://auth.mbari.org:8095/crowd to kick off the start up wizard ## (/) I grabbed a new eval license from my account on atlassian and pasted into the license page. ## (/) I selected "New install" on the next page. ## (/) I configured the JDBC connection using this connection URL with user DB_Collaboration {noformat} jdbc:jtds:sqlserver://dione.mbari.org:51001/Crowd;domain=SHORE;useNTLMv2=TRUE {noformat} ## (/) I left the "Options" as they came up {warning:title=Paths} Not sure if this is a problem, but because I started the set up using auth.mbari.org, it set the Base URL to http://auth.mbari.org:8095/crowd instead of localhost. Hope that is not a problem. We will see. {warning} ## (/) I configured the email connection using the settings from [here|https://wind.shore.mbari.org/is/howto/email/mbarimail/imap] and I used my network login (probably shouldn't be doing that ... not sure where it stores my password, but I am assuming in the DB). ## (/) For the local admin account, I created a user named 'crowdadm' so it would not clash with my LDAP account. See Kevin Gomes for password information. ## (/) I checked the OpenID server as an integrated application ## (/) It then took me to the login page and I logged in using the newly minted admin account. Seemed all is well so far. ## (/) I visited the openidserver URL as well and that seemed OK. ## (/) I decided to wait on configuring the MBARI LDAP directory until I got everything with SSL working. ## (/) Now the next step was to follow the directions to configure Crowd to run over SSL found [here|https://confluence.atlassian.com/display/CROWD/Configuring+Crowd+to+Work+with+SSL] ## (/) I shutdown crowd. Note that the stop script does not shutdown things correctly and I noticed the crowd app running as root. That should not be if I started as kgomes. Not sure what is up with that. ## (/) Now Joe had already configured SSL once, so I used his connector configuration in the server.xml file and so the final file looked like: {noformat} {noformat} ## (/) I then edited the /data/crowd/crowd.properties to look like: {noformat} #Sat Aug 01 09:05:15 PDT 2015 session.lastvalidation=session.lastvalidation session.tokenkey=session.tokenkey crowd.server.url=https\://localhost\:8443/crowd/services/ application.name=crowd http.timeout=30000 session.isauthenticated=session.isauthenticated application.login.url=https\://localhost\:8443/crowd/console/ session.validationinterval=0 application.password=Y1Xp3OorCmsOP4eruL1dmH {noformat} One thing to note here is that based on a comment from the SSL configuration page at atlassian (Steve's comment), you are supposed to leave all the host names the same. For example, if the file says localhost, leave it localhost. So this created a bit of a problem based on the fact that I had left the base URL pointing to auth.mbari.org in the wizard steps above. That step wrote auth.mbari.org to the /data/crowd/crowd.properties. All the other files reference localhost, so to be consistent, I changed auth.mbari.org to localhost in the /data/crowd/crowd.properties file. We will see if this works. ## (/) Per the instructions on the atlassian page (referenced above), I also edited the build.properties file and the /client/conf/crowd.properties files before I restarted and used the SSL URLs ## build.properties: {noformat} # Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See https://confluence.atlassian.com/display/CROWD/Connecting+Crowd+to+a+Database hibernate.dialect=org.hibernate.dialect.SQLServerDialect # The Hibernate transaction factory to use. See https://confluence.atlassian.com/display/CROWD/Configuring+Crowd hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory # The http port you wish to run crowd from, ie: http://localhost:8095/crowd crowd.tomcat.connector.port=8095 # Tomcat requires a unique port for shutdown crowd.tomcat.shutdown.port=8020 # Crowd context root crowd.url=https://localhost:8443/crowd # Demo context root demo.url=https://localhost:8443/demo # OpenID server context root openidserver.url=https://localhost:8443/openidserver {noformat} ## crowd.properties (client) {noformat} application.name crowd application.password password application.login.url https://localhost:8443/crowd/console/ crowd.server.url https://localhost:8443/crowd/services/ crowd.base.url https://localhost:8443/crowd/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 2 session.lastvalidation session.lastvalidation {noformat} ## (/) Although not stated, I am assuming you would need to run the build.sh script to push the build.properties changes to their proper places, so I did that. Note that before doing that, I know that it will clobber the server.xml changes I made, so I made a copy of that file and diff'd them after and then rolled the previous changes to the new server.xml file. Actually, amazingly enough, it seems to have done the connector entry correctly so I left it after running the build.sh script. ## (/) Crossed my fingers and then restarted crowd. I tailed the catalina.out file and did not see any stack traces so that is a good sign! ## (/) I visited https://auth.mbari.org:8443/crowd first. It could not find that page, but I suspect that is because I am browsing from the outside, so I tried just https://auth.mbari.org/crowd and got a service unavailable. I am suspecting that this is a combination of firewall and proxy pass and I will send this info to Joe. From what I can see on the crowd side, it seems like the server started cleanly, we just can't get to it. I tried to reach it from a browser on the machine itself too (through VNC) with the same service not available. ## (/) Here are the notes from Joe after he fixed it! Wooohooo! {noformat} Hey Kevin, Thanks for starting clean! I had to make a few adjustments. 1-I modified the server.xml file in /opt/atlassian-crowd-2.8.3/apache-tomcat/conf/server.xml so there are two connectors per the instructions on the Atlassian site. I have backed up this good server.xml file in /etc/temp/ if you want to browse it to see what I did. Of note is that I removed all the jargon referencing the types of ciphers available to simplify things for now. 2-I modified /data/crowd/crowd.properties to have crowd.server.url=https\://localhost\:8443/crowd/services/ application.login.url=https\://localhost\:8443/crowd/console/ But that would cause my login to error with an error saying it was unable to reach the authentication server. I scratched my head for a bit. When I revert the values to just using non-SSL and try to log in, I just get an "invalid login" (I don't know the crowdadm password). So I worked under the assumption that if I can configure SSL to get an "invalid login" when logging in then it would work when provided real credentials. So, I then changed /data/crowd/crowd.proprties to: crowd.server.url=https\://auth.mbari.org\:8443/crowd/services/ application.login.url=https\://auth.mbari.org\:8443/crowd/console/ And now when I try to log in with SSL it says "invalid login". Strange because all the other values I can find only show "localhost" .. in any case... Can you try to log in now? {noformat} ## (/) Next I moved on to configuring the connection to MBARI's LDAP server to enable our logins through Crowd and CrowdID ## (/) I clicked on "Add Directory" in crowd. ## (/) I selected "Connector" then clicked Next ## (/) I put ldap.shore.mbari.org as the name of the server ## (/) I selected "Use memberOf for group memberships" ## (/) I used "OU=AllUsers,DC=shore,DC=mbari,DC=org" for the Base DN ## (/) I used "CN=LDAPbind,OU=Special,OU=AllUsers,DC=shore,DC=mbari,DC=org" for the Username (talk to Pat Allen for password) ## (/) I tested the connection (button click) and it passed. ## (/) I de-selected all the capabilities of the connector as it is a ready only connector and then saved it. It synchronized correctly! ## (/) At first, I could not login using my MBARI credentials, but after going to the "crowd" application in crowd (logged in as the local admin), I had to add the LDAP directory and configure it to "Allow all to authenticate", then I was able to login. After this, the last step was to get this to run as a different user and lock down various directories. I went through the entire directory structure /opt/atlassian... and set up so that root owned all read-only locations and DB_Collaboration (account set up by IS) owned the other stuff. I also gave full ownership to the /data/crowd directory to DB_Collaboration so it could write there. Pat set up a script to start on boot and after a little tweaking, it now starts on boot. {warning:title=CrowdID log file} One thing that came up here was that when the crowdID application ran, it tried to write a log file to the location where the process was launched from (which is /opt/atlassian...). This is a bad thing and I figured out that I could change that location by changing the file /opt/atlassian-crowd-2.8.3/crowd-openidserver-webapp/WEB-INF/classes/log4j.properties and hardcoding the /data/crowd/logs/atlassian-crowd-openid-server.log and then restarted the application. {warning} ## (/) Another note is the when an application tried to use the OpenID application, it would get redirected to localhost. I changed the /opt/atlassian.../crowd-openidserver-webapp/WEB-INF/classes/crowd.properties file to look like: {noformat} #Sat Aug 01 10:03:18 PDT 2015 session.lastvalidation=session.lastvalidation session.tokenkey=session.tokenkey crowd.server.url=http\://localhost\:8095/crowd/services/ application.name=crowd-openid-server #application.login.url.template=http\://localhost\:8095/openidserver?returnToUrl\=${RETURN_TO_URL} application.login.url.template=https\://auth.mbari.org/openidserver?returnToUrl\=${RETURN_TO_URL} session.isauthenticated=session.isauthenticated #application.base.url=http\://localhost\:8095/openidserver application.base.url=https\://auth.mbari.org/openidserver #application.login.url=http\://localhost\:8095/openidserver application.login.url=https\://auth.mbari.org/openidserver session.validationinterval=0 application.password=password {noformat} and that seems to have fixed it. # (/) It is finally time to move on to the version 4 upgrade ... holy crap. I first went to the *new* crowd install (auth.mbari.org) and logged in as the crowdadm. # (/) I clicked on Applications, then on Add Application # (/) I selected JIRA from the Application type drop-down # (/) I entered jira445 as the username. Ask Kevin about the password. # (/) I used http://bugs.shore.mbari.org:8081 as the URL # (/) I used 134.89.12.31 as the IP address. # (/) I selected only the MBARI LDAP directory. # (/) Then I selected "Allow all users to authenticate" # (/) Then I clicked on "Add Application" # (/) I VNC'd into bugs.mbari.org. As it turns out, for Linux, there is an installer program to download. I downloaded the .bin for 64 bit Linux installer and moved it to the jira-upgrade directory. # (/) I chmod'd the file to make it executable and ran it. It gave me a warning about not being root, but I went ahead with it. # (/) It asked for the JIRA home and data directory, which I specified as /opt/jira4 and /data/jira445. # (/) For the ports, I specified 8180 and 8105 (HTTP and control respectively). It then extracted all the files and launched JIRA. It said if finished, so I opened a local browser to http://localhost:8180 which kicked off the start up wizard. # (/) I specified the external database using: ## solstice2.shore.mbari.org (server) ## 1433 (port) ## jira4 (database) ## DB_Collaboration (username) ## (password ask Kevin) ## dbo (schema) # But all this failed as it seems to just want to try and use the SQL server authentication instead of domain. I will have to do it manually. # (/) I stopped the server using the bin/stop-jira.sh script. # (/) I created and edited /data/jira445/dbconfig.xml and made it look like the following: {noformat} ?xml version="1.0" encoding="UTF-8"?> defaultDS default mssql jiraschema jdbc:jtds:sqlserver://solstice2.shore.mbari.org:1433/Jira4;domain=SHORE;useNTLMv2=true net.sourceforge.jtds.jdbc.Driver DB_Collaboration (ask Kevin) 15 {noformat} # (/) I then started it again using bin/start-jira.sh and tailed the catalina.out file. Got a bunch of errors related to the schema 'jiraschema', I edited the file and changed the schema to 'dbo' and restarted. That seemed to do it. There was one stack trace for some iCal plugin, but looks OK other than that. # I browsed back to localhost:8180 and the wizard moved to step 2. There was an option to import existing data bit without the crowd connection, I thought I should set it up manually, connect to crowd, then import. I generated an evaluation license, called the app "MBARI JIRA4" and change the server in the url to bugs.shore.mbari.org # For the admin, I created an account called 'jiraadm' (ask Kevin for password). # Since this is a temporary system, I left the email system disabled. # I logged in as jiraadm, went to Administration, then Users, then clicked on Add Directory and chose Atlassian Crowd. Note that I had to set the server URL to http://auth.mbari.org:8095/crowd or I would have had to configure all this SSL crap that I did not want to do for this temporary install. # It tested successfully, I clicked Save and it went through a 13 second sync, whew! # I then went to System->Import and Export->Restore System # I copied the jira-upgrade-3.13.5.zip file from the previous version export into /data/jira445/import and then entered that file name along with the new evaluation license again. # I worked through progress bar after I clicked on Restore (it took a really long time). # I then stopped, restarted and tailed the log file. # I am thinking now I should have put the attachments in the import attachments directory, but I am hoping I can just copy them to the data/attachments directory. # UG! I got some error during the import. The exception read: "JIRA is unable to migrat the User Directory configuration because external users exist but the osuser.xml file is not available". It then gave me a link to a doc that talked about making the old user files available before the upgrade ... crap. So I needed to copy the osuser.xml and crowd.properties file from atlassian-jira/WEB-INF/classes directory on the old install to the same directory on the new install ... sigh. This means I am going to blow away everything and start over. # I shutdown jira4 # I dropped all things in the database and deleted all content in the /data/jira445 directory (except for the dbconfig.xml file). # I also removed the temp, logs (actually you have to leave the directory, just clear the files) and the work/Catalina/localhost directories from the jira installation. # I then copied the osuser.xml and the crowd.properties files from the 3.13.5 install to the 4 install. # I edited the crowd.properties file in hopes that I could point it to the new crowd install on auth.mbari.org and it would work, but we will see. # I then started jira and tailed the log file. # All looked OK (other than iCal plugin stack trace again), so I went to localhost:8180 and got step 2 of the wizard. I used the same info as before. # I logged in as the local admin account and it looks like the system picked up the crowd connection, but lets see what server it used! Hey it used the one I edited into the file! Sweet ... now let's see if the import works. # I copied the 3.13.5 zip file to the import directory again and this time, I untarred the attachments into the import/attachments directory. ]]> 27558184 27590950 4.4: [https://confluence.atlassian.com/display/JIRA044/Migrating+JIRA+to+Another+Server] ## The JIRA configuration tool: [https://confluence.atlassian.com/display/JIRA044/Using+the+JIRA+Configuration+Tool] h5. Steps # (/) Create new VM named bugs.mbari.org in the DMZ # (/) Have Neil create database Jira_Temp on solstice2.shore.mbari.org # (/) Have Neil create database Jira on solstice2.shore.mbari.org # (/) Have Pat install Java 7 on bugs.shore.mbari.org # (/) Have Pete plumb holes through firewall so processes on bugs.mbari.org can get to Solstice2 # (/) Have Pat create DB_Collaboration account on bugs so it can run JIRA under that account and it can connect to solstice2 using that NT Domain account. # (/) Upgrade license on Atlassian site # (/) Log into bugs.shore.mbari.org # (/) Download 3.13.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 4.4.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 5.2.11 standalone Linux 64 bit tar.gz (not sure this version is necessary, but at least I have it) # (/) Unzip and untar the file to /opt # (/) Download latest JIRA (6.4.7 as of this writing). # (/) Unzip and untar it to /opt # Performed Test Upgrade ## (/) In order to export the current stuff in JIRA, I had to shut off access so people could not change the data while I was backing it up. ## (/) I ssh'd to oceana.mbari.org as root and edited the /opt/jira/conf/server.xml file and commented out the Connector section that had the port of 8010 to shut it off from the normal serving route. ## (/) I uncommented the 8082 port connector and the 8443 port connector so that I could still get to the server. ## (/) I stopped and started the JIRA server and in the log file I got a "keystore was tampered with..." which is not surprising. ## (/) I could then browser over to http://oceana.mbari.org:8082/jira ## (/) Then through the Administration console, I did an XML backup ## (/) I then created a tar of all the attachments in the /data/jira_3_12/attachments directory ## (/) I moved both the XML and tar files to the /root/jira-upgrade directory ## (/) I then reversed the changes to the server.xml file and shut down JIRA ## (/) I left it down during the next steps in case it went so well, I could just point people to the new server (yeah, right). ## (/) I then browsed to the crowd server on oceana and add a new application using: ### URL: http://bugs.mbari.org/jira3135 ### IP: 134.89.2.29 ### Name: JIRA3135 ### Password: (ask Kevin) :) ## (/) On bugs, I made a copy of the JIRA 3.13.5 download in the /opt directory and unzipped and untarred it. ## (/) In order to configure the crowd connection I did the following: ### (/) I scp'd the /opt/crowd/client/crowd-integration-client-1.6.jar file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I removed the existing 1.6.1 crowd client jar from the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I scp'd the /opt/crowd/client/conf/crowd.properties file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I scp'd the /opt/crowd/client/conf/crowd-ehcache.xml file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I edited the crowd.properties file on bugs to look like: {noformat} application.name JIRA3135 application.password (ask Kevin) application.login.url http://oceana.mbari.org:8095/crowd/console/ crowd.server.url http://oceana.mbari.org:8095/crowd/services/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 0 session.lastvalidation session.lastvalidation {noformat} ### (/) I edited the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/osuser.xml file to comment out the current authentication mechanism and then uncomment the crowd one. ## (/) I then edited the /opt/atlassian-jira-standalone-3.13.5/conf/server/xml file and configured the database connection to the Jira_Temp database on Solstice2. I looked like this: {noformat} {noformat} ## (/) Edit the /opt/atlassian/jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/entityengine.xml and changed it from 'hsql' to 'mssql' and delete the line with "PUBLIC" in it per the instructions in the comments in that file. ## (/) I edited the /etc/httpd/conf/httpd.conf file and created a proxy pass at the bottom of the file to point a normal URL to the default port 8080 for JIRA: {noformat} # Proxy Pass for JIRA ProxyPass http://bugs.mbari.org:8080 ProxyPassReverse http://bugs.mbari.org:8080 {noformat} ## (/) I restarted Apache ## (/) I scp'd the jtds driver from oceana to the /opt/atlassian-jira-standalone-3.13.5/common/lib directory (you could down from the internet) ## (/) I then went to the /opt/atlassian-jira-standalone-3.13.5/ directory and ran './bin/startup.sh'. From the log file, I could tell things were hanging. After some troubleshooting I am wondering if the local firewall is preventing the application to get access to the database on solstice2. I can telnet to port 1433, but I can't browse to the base http://bugs.mbari.org from anywhere but the local web browser. I have submitted a ticket. ## (/) I restarted the old JIRA with my hopes dashed :(. ## (/) Pat disabled the firewall on bugs.mbari.org but it still hung trying to connect to solstice2.shore.mbari.org. That is really, really perplexing. Neil mentioned that solstice2 is using Kerberos and solstice is not. Checking with the JTDS docs, version 1.3.1 of the driver added kerberos support, so I downloaded that driver and added the 'userKerberos=true' property to the URL in the server.xml file and restarted. Got an error about no credentials, so added user and password properties to the URL. Nope, no luck. Never did figure this one out, but I had Pat pull the VM inside the firewall and after some thrash it worked. Well, it sort of worked ... sigh. It turns out I had downloaded the standard version instead of the enterprise version. I need to redo this work ... grrr. ## (/) I deleted all the tables in the Jira_Temp database and removed the /data/jira3135/indexes directory (and recreated). ## (/) I downloaded the enterprise version of the 3.13.5 server. I made a copy in the /opt directory and unzipped and untarred the file. ## (/) I went back to crowd and edited the application to change the properties to: ### URL: http://bugs.shore.mbari.org:8080 ### IP: 134.89.12.31 ### Name: jira3135 ### Password: (ask Kevin) :) ## (/) I then repeated the steps above to get the server up and running with the following differences: ### The server name is now bugs.shore.mbari.org ### The paths given above are a little different in that they no longer say "standard" but say "enterprise" ### I deleted the proxy pass as it seemed to have issues before and this is only temporary anyway. ## (/) I then browsed to http://bugs.shore.mbari.org:8080 ## (/) It took me to the start up page and at the top was the option to 'import your existing data'. Seemed too good not to try. I clicked on the link. It asked me for the backup file location and the location where the indexes would be stored. ## (/) I copied the XML zip file and the attachments tar file to the /data/original directory. ## (/) I created the /data/jira3135/indexes and used those directories ... it fired off the import and I waited. ## (/) I tailed the log file to watch the import. Holy crap, it worked!!! I could log in and everything! I copied the results from the log file here for posterity sake: {noformat} 2015-07-22 20:55:45,156 http-8080-Processor22 INFO [jira.action.admin.DataImport] Running data import 2015-07-22 20:55:45,179 http-8080-Processor22 INFO [jira.action.admin.DataImport] Importing data.. 2015-07-22 20:55:45,186 http-8080-Processor22 INFO [jira.action.admin.DataImport] Start parsing XML with SAX Parser 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] XML successfully parsed 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] Removing all entries from the database. 2015-07-22 20:56:24,593 http-8080-Processor22 INFO [jira.action.admin.DataImport] All entries removed. 2015-07-22 20:56:24,594 http-8080-Processor22 INFO [jira.action.admin.DataImport] Started storing 410414 Generic Values 2015-07-22 21:01:51,967 http-8080-Processor22 INFO [jira.action.admin.DataImport] Finished storing Generic Values 2015-07-22 21:01:52,329 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:52,361 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:54,683 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLink' to module 'jira.user.format:profile-link-user-format'. 2015-07-22 21:01:54,724 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullName' to module 'jira.user.format:full-name-user-format'. 2015-07-22 21:01:54,773 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkSearcher' to module 'jira.user.format:profile-link-searcher-user-format'. 2015-07-22 21:01:54,784 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkExternal' to module 'jira.user.format:profile-link-external-user-format'. 2015-07-22 21:01:54,795 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkActionHeader' to module 'jira.user.format:profile-link-action-header-user-format'. 2015-07-22 21:01:54,807 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullProfile' to module 'jira.user.format:full-profile-user-format'. 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/comments 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/issues 2015-07-22 21:01:55,641 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/plugins 2015-07-22 21:01:55,867 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:01:55,871 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/issues does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:55,873 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/comments does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,033 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,257 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,889 http-8080-Processor22 ERROR [atlassian.jira.upgrade.ConsistencyCheckImpl] Attachments are turned on, but attachment path [/data/jira_3_12/attachments] invalid - disabling attachments 2015-07-22 21:02:13,904 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Detected that an upgrade is needed; existing data at build 299 2015-07-22 21:02:13,907 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Doing Upgrade... 2015-07-22 21:02:13,915 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value' succeeded 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 317 2015-07-22 21:02:13,944 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite filters - make each filter a favourite of its owner. 2015-07-22 21:02:17,822 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build319] Could not find author 'fpy' for filter with id '10040' 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite filters - make each filter a favourite of its owner.' succeeded 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 319 2015-07-22 21:02:17,995 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise Share Permissions. Move old shares to new shares. 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise Share Permissions. Move old shares to new shares.' succeeded 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 321 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Migrating the old JIRA UI colors to the new JIRA 3.13 colors 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build322] Custom color detected for jira.lf.menu.bgcolour : #336699 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Migrating the old JIRA UI colors to the new JIRA 3.13 colors' succeeded 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 322 2015-07-22 21:02:18,025 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite dashboards - make each dashboard a favourite of its owner. 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'cmcgann' for dashboard with id '10030' 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'fpy' for dashboard with id '10060' 2015-07-22 21:02:18,423 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'kanna' for dashboard with id '10040' 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite dashboards - make each dashboard a favourite of its owner.' succeeded 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 325 2015-07-22 21:02:18,625 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Reindexing all data in JIRA to include Favourites. 2015-07-22 21:02:18,648 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All starting... 2015-07-22 21:02:18,650 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 0% complete. Current index: Issue 2015-07-22 21:02:18,654 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:02:18,809 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 1% complete. Current index: Issue 2015-07-22 21:02:18,855 indexerPool-2-thread-10 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 2% complete. Current index: Issue 2015-07-22 21:02:18,899 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 3% complete. Current index: Issue 2015-07-22 21:02:18,945 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 4% complete. Current index: Issue 2015-07-22 21:02:19,012 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 5% complete. Current index: Issue . . . 2015-07-22 21:02:26,164 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 95% complete. Current index: Issue 2015-07-22 21:02:26,232 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 96% complete. Current index: Issue 2015-07-22 21:02:26,316 indexerPool-2-thread-9 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 97% complete. Current index: Issue 2015-07-22 21:02:26,771 indexerPool-2-thread-3 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: Issue 2015-07-22 21:02:27,261 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 8607ms. Indexer: DefaultIndexManager: paths: [/data/jira3135/indexes/issues, /data/jira3135/indexes/comments] 2015-07-22 21:02:27,263 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: SearchRequest 2015-07-22 21:02:27,268 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,293 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: SearchRequest 2015-07-22 21:02:27,308 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: PortalPage 2015-07-22 21:02:27,312 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,377 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: PortalPage 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 115ms. Indexer: SharedEntityIndexManager: paths: [/data/jira3135/indexes/entities/portalpage, /data/jira3135/indexes/entities/searchrequest] 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All complete. Total time: 8722ms. 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Reindexing all data in JIRA to include Favourites.' succeeded 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 326 2015-07-22 21:02:27,397 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade succeeded! Setting data build number to 360 2015-07-22 21:02:27,469 JiraQuartzScheduler_Worker-0 WARN [service.services.export.ExportService] Backup directory /data/jira_3_12/backup does not exist {noformat} {warning:title=Paths} It appears that the upgraded JIRA will still look for the attachments and the backup locations in the original places. So I created /data/jira_3_12/backup and untarred the original attachments to /data/jira_3_12 and then everything worked (including attachements) in the new JIRA. {warning} ## (/) I then used the upgraded JIRA to generate a new XML backup and stored it in /data/original/3.13.5 along with another tar of the files in /data/jira_3_12/attachments. ## (/) I then shutdown the JIRA server. *I should be ready to move on to version 4 upgrade WHEW* ## So, before moving on, I decided that it would be a really good idea to spin up a new Crowd instance to get rid of the :8443 in the URL and to move off of RedHat per IS requests. I have a ticket in for a new VM and a new database to try to get this going. I am waiting on that before moving on. ## (/) Pat created the VM and Neil created the database. ## (/) I logged into auth.mbari.org (name of the VM) and downloaded crowd which I unzipped to the /opt directory ## (/) I then created a /data/crowd directory and gave my account permissions on it and then edited the /opt/atlassian..../crowd-webapp/WEB-INF/classes/crowd-init.properties file to set that as the crowd home directory. ## (/) The instructions say to download the JDBC driver, but they already have JTDS 1.2.7 in the download so I did not do anything. ## (/) You have to manually connect up CrowdID to a database as they setup wizard does not currently do this. ### (/) They say to download the driver, but again 1.2.7 was there so I did nothing. ### (/) I edited the /opt/atlassian.../apache-tomcat/conf/Catalina/localhost/openidserver.xml to look like: {noformat} {noformat} ### (/) I edited the /opt/atlassian.../build.properties files to look like: {noformat} # Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See https://confluence.atlassian.com/display/CROWD/Connecting+Crowd+to+a+Database hibernate.dialect=org.hibernate.dialect.SQLServerDialect # The Hibernate transaction factory to use. See https://confluence.atlassian.com/display/CROWD/Configuring+Crowd hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory # The http port you wish to run crowd from, ie: http://localhost:8095/crowd crowd.tomcat.connector.port=8095 # Tomcat requires a unique port for shutdown crowd.tomcat.shutdown.port=8020 # Crowd context root crowd.url=http://localhost:8095/crowd # Demo context root demo.url=http://localhost:8095/demo # OpenID server context root openidserver.url=http://localhost:8095/openidserver {noformat} ### (/) I then ran the build.sh script in the root of /opt/atlassian... ## (/) I fired up crowd using the /opt/atlassian.../start_crowd.sh script ## (/) I then went to http://auth.mbari.org:8095/crowd to kick off the start up wizard ## (/) I grabbed a new eval license from my account on atlassian and pasted into the license page. ## (/) I selected "New install" on the next page. ## (/) I configured the JDBC connection using this connection URL with user DB_Collaboration {noformat} jdbc:jtds:sqlserver://dione.mbari.org:51001/Crowd;domain=SHORE;useNTLMv2=TRUE {noformat} ## (/) I left the "Options" as they came up {warning:title=Paths} Not sure if this is a problem, but because I started the set up using auth.mbari.org, it set the Base URL to http://auth.mbari.org:8095/crowd instead of localhost. Hope that is not a problem. We will see. {warning} ## (/) I configured the email connection using the settings from [here|https://wind.shore.mbari.org/is/howto/email/mbarimail/imap] and I used my network login (probably shouldn't be doing that ... not sure where it stores my password, but I am assuming in the DB). ## (/) For the local admin account, I created a user named 'crowdadm' so it would not clash with my LDAP account. See Kevin Gomes for password information. ## (/) I checked the OpenID server as an integrated application ## (/) It then took me to the login page and I logged in using the newly minted admin account. Seemed all is well so far. ## (/) I visited the openidserver URL as well and that seemed OK. ## (/) I decided to wait on configuring the MBARI LDAP directory until I got everything with SSL working. ## (/) Now the next step was to follow the directions to configure Crowd to run over SSL found [here|https://confluence.atlassian.com/display/CROWD/Configuring+Crowd+to+Work+with+SSL] ## (/) I shutdown crowd. Note that the stop script does not shutdown things correctly and I noticed the crowd app running as root. That should not be if I started as kgomes. Not sure what is up with that. ## (/) Now Joe had already configured SSL once, so I used his connector configuration in the server.xml file and so the final file looked like: {noformat} {noformat} ## (/) I then edited the /data/crowd/crowd.properties to look like: {noformat} #Sat Aug 01 09:05:15 PDT 2015 session.lastvalidation=session.lastvalidation session.tokenkey=session.tokenkey crowd.server.url=https\://localhost\:8443/crowd/services/ application.name=crowd http.timeout=30000 session.isauthenticated=session.isauthenticated application.login.url=https\://localhost\:8443/crowd/console/ session.validationinterval=0 application.password=Y1Xp3OorCmsOP4eruL1dmH {noformat} One thing to note here is that based on a comment from the SSL configuration page at atlassian (Steve's comment), you are supposed to leave all the host names the same. For example, if the file says localhost, leave it localhost. So this created a bit of a problem based on the fact that I had left the base URL pointing to auth.mbari.org in the wizard steps above. That step wrote auth.mbari.org to the /data/crowd/crowd.properties. All the other files reference localhost, so to be consistent, I changed auth.mbari.org to localhost in the /data/crowd/crowd.properties file. We will see if this works. ## (/) Per the instructions on the atlassian page (referenced above), I also edited the build.properties file and the /client/conf/crowd.properties files before I restarted and used the SSL URLs ## build.properties: {noformat} # Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See https://confluence.atlassian.com/display/CROWD/Connecting+Crowd+to+a+Database hibernate.dialect=org.hibernate.dialect.SQLServerDialect # The Hibernate transaction factory to use. See https://confluence.atlassian.com/display/CROWD/Configuring+Crowd hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory # The http port you wish to run crowd from, ie: http://localhost:8095/crowd crowd.tomcat.connector.port=8095 # Tomcat requires a unique port for shutdown crowd.tomcat.shutdown.port=8020 # Crowd context root crowd.url=https://localhost:8443/crowd # Demo context root demo.url=https://localhost:8443/demo # OpenID server context root openidserver.url=https://localhost:8443/openidserver {noformat} ## crowd.properties (client) {noformat} application.name crowd application.password password application.login.url https://localhost:8443/crowd/console/ crowd.server.url https://localhost:8443/crowd/services/ crowd.base.url https://localhost:8443/crowd/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 2 session.lastvalidation session.lastvalidation {noformat} ## (/) Although not stated, I am assuming you would need to run the build.sh script to push the build.properties changes to their proper places, so I did that. Note that before doing that, I know that it will clobber the server.xml changes I made, so I made a copy of that file and diff'd them after and then rolled the previous changes to the new server.xml file. Actually, amazingly enough, it seems to have done the connector entry correctly so I left it after running the build.sh script. ## (/) Crossed my fingers and then restarted crowd. I tailed the catalina.out file and did not see any stack traces so that is a good sign! ## (/) I visited https://auth.mbari.org:8443/crowd first. It could not find that page, but I suspect that is because I am browsing from the outside, so I tried just https://auth.mbari.org/crowd and got a service unavailable. I am suspecting that this is a combination of firewall and proxy pass and I will send this info to Joe. From what I can see on the crowd side, it seems like the server started cleanly, we just can't get to it. I tried to reach it from a browser on the machine itself too (through VNC) with the same service not available. ## (/) Here are the notes from Joe after he fixed it! Wooohooo! {noformat} Hey Kevin, Thanks for starting clean! I had to make a few adjustments. 1-I modified the server.xml file in /opt/atlassian-crowd-2.8.3/apache-tomcat/conf/server.xml so there are two connectors per the instructions on the Atlassian site. I have backed up this good server.xml file in /etc/temp/ if you want to browse it to see what I did. Of note is that I removed all the jargon referencing the types of ciphers available to simplify things for now. 2-I modified /data/crowd/crowd.properties to have crowd.server.url=https\://localhost\:8443/crowd/services/ application.login.url=https\://localhost\:8443/crowd/console/ But that would cause my login to error with an error saying it was unable to reach the authentication server. I scratched my head for a bit. When I revert the values to just using non-SSL and try to log in, I just get an "invalid login" (I don't know the crowdadm password). So I worked under the assumption that if I can configure SSL to get an "invalid login" when logging in then it would work when provided real credentials. So, I then changed /data/crowd/crowd.proprties to: crowd.server.url=https\://auth.mbari.org\:8443/crowd/services/ application.login.url=https\://auth.mbari.org\:8443/crowd/console/ And now when I try to log in with SSL it says "invalid login". Strange because all the other values I can find only show "localhost" .. in any case... Can you try to log in now? {noformat} ## (/) Next I moved on to configuring the connection to MBARI's LDAP server to enable our logins through Crowd and CrowdID ## (/) I clicked on "Add Directory" in crowd. ## (/) I selected "Connector" then clicked Next ## (/) I put ldap.shore.mbari.org as the name of the server ## (/) I selected "Use memberOf for group memberships" ## (/) I used "OU=AllUsers,DC=shore,DC=mbari,DC=org" for the Base DN ## (/) I used "CN=LDAPbind,OU=Special,OU=AllUsers,DC=shore,DC=mbari,DC=org" for the Username (talk to Pat Allen for password) ## (/) I tested the connection (button click) and it passed. ## (/) I de-selected all the capabilities of the connector as it is a ready only connector and then saved it. It synchronized correctly! ## (/) At first, I could not login using my MBARI credentials, but after going to the "crowd" application in crowd (logged in as the local admin), I had to add the LDAP directory and configure it to "Allow all to authenticate", then I was able to login. After this, the last step was to get this to run as a different user and lock down various directories. I went through the entire directory structure /opt/atlassian... and set up so that root owned all read-only locations and DB_Collaboration (account set up by IS) owned the other stuff. I also gave full ownership to the /data/crowd directory to DB_Collaboration so it could write there. Pat set up a script to start on boot and after a little tweaking, it now starts on boot. {warning:title=CrowdID log file} One thing that came up here was that when the crowdID application ran, it tried to write a log file to the location where the process was launched from (which is /opt/atlassian...). This is a bad thing and I figured out that I could change that location by changing the file /opt/atlassian-crowd-2.8.3/crowd-openidserver-webapp/WEB-INF/classes/log4j.properties and hardcoding the /data/crowd/logs/atlassian-crowd-openid-server.log and then restarted the application. {warning} ## (/) Another note is the when an application tried to use the OpenID application, it would get redirected to localhost. I changed the /opt/atlassian.../crowd-openidserver-webapp/WEB-INF/classes/crowd.properties file to look like: {noformat} #Sat Aug 01 10:03:18 PDT 2015 session.lastvalidation=session.lastvalidation session.tokenkey=session.tokenkey crowd.server.url=http\://localhost\:8095/crowd/services/ application.name=crowd-openid-server #application.login.url.template=http\://localhost\:8095/openidserver?returnToUrl\=${RETURN_TO_URL} application.login.url.template=https\://auth.mbari.org/openidserver?returnToUrl\=${RETURN_TO_URL} session.isauthenticated=session.isauthenticated #application.base.url=http\://localhost\:8095/openidserver application.base.url=https\://auth.mbari.org/openidserver #application.login.url=http\://localhost\:8095/openidserver application.login.url=https\://auth.mbari.org/openidserver session.validationinterval=0 application.password=password {noformat} and that seems to have fixed it. # (/) It is finally time to move on to the version 4 upgrade ... holy crap. I first went to the *new* crowd install (auth.mbari.org) and logged in as the crowdadm. # (/) I clicked on Applications, then on Add Application # (/) I selected JIRA from the Application type drop-down # (/) I entered jira445 as the username. Ask Kevin about the password. # (/) I used http://bugs.shore.mbari.org:8081 as the URL # (/) I used 134.89.12.31 as the IP address. # (/) I selected only the MBARI LDAP directory. # (/) Then I selected "Allow all users to authenticate" # (/) Then I clicked on "Add Application" # (/) I VNC'd into bugs.mbari.org. As it turns out, for Linux, there is an installer program to download. I downloaded the .bin for 64 bit Linux installer and moved it to the jira-upgrade directory. # (/) I chmod'd the file to make it executable and ran it. It gave me a warning about not being root, but I went ahead with it. # (/) It asked for the JIRA home and data directory, which I specified as /opt/jira4 and /data/jira445. # (/) For the ports, I specified 8180 and 8105 (HTTP and control respectively). It then extracted all the files and launched JIRA. It said if finished, so I opened a local browser to http://localhost:8180 which kicked off the start up wizard. # (/) I specified the external database using: ## solstice2.shore.mbari.org (server) ## 1433 (port) ## jira4 (database) ## DB_Collaboration (username) ## (password ask Kevin) ## dbo (schema) # But all this failed as it seems to just want to try and use the SQL server authentication instead of domain. I will have to do it manually. # (/) I stopped the server using the bin/stop-jira.sh script. # (/) I created and edited /data/jira445/dbconfig.xml and made it look like the following: {noformat} ?xml version="1.0" encoding="UTF-8"?> defaultDS default mssql jiraschema jdbc:jtds:sqlserver://solstice2.shore.mbari.org:1433/Jira4;domain=SHORE;useNTLMv2=true net.sourceforge.jtds.jdbc.Driver DB_Collaboration (ask Kevin) 15 {noformat} # (/) I then started it again using bin/start-jira.sh and tailed the catalina.out file. Got a bunch of errors related to the schema 'jiraschema', I edited the file and changed the schema to 'dbo' and restarted. That seemed to do it. There was one stack trace for some iCal plugin, but looks OK other than that. # I browsed back to localhost:8180 and the wizard moved to step 2. There was an option to import existing data bit without the crowd connection, I thought I should set it up manually, connect to crowd, then import. I generated an evaluation license, called the app "MBARI JIRA4" and change the server in the url to bugs.shore.mbari.org # For the admin, I created an account called 'jiraadm' (ask Kevin for password). # Since this is a temporary system, I left the email system disabled. # I logged in as jiraadm, went to Administration, then Users, then clicked on Add Directory and chose Atlassian Crowd. Note that I had to set the server URL to http://auth.mbari.org:8095/crowd or I would have had to configure all this SSL crap that I did not want to do for this temporary install. # It tested successfully, I clicked Save and it went through a 13 second sync, whew! # I then went to System->Import and Export->Restore System # I copied the jira-upgrade-3.13.5.zip file from the previous version export into /data/jira445/import and then entered that file name along with the new evaluation license again. # I worked through progress bar after I clicked on Restore (it took a really long time). # I then stopped, restarted and tailed the log file. # I am thinking now I should have put the attachments in the import attachments directory, but I am hoping I can just copy them to the data/attachments directory. # UG! I got some error during the import. The exception read: "JIRA is unable to migrat the User Directory configuration because external users exist but the osuser.xml file is not available". It then gave me a link to a doc that talked about making the old user files available before the upgrade ... crap. So I needed to copy the osuser.xml and crowd.properties file from atlassian-jira/WEB-INF/classes directory on the old install to the same directory on the new install ... sigh. This means I am going to blow away everything and start over. # I shutdown jira4 # I dropped all things in the database and deleted all content in the /data/jira445 directory (except for the dbconfig.xml file). # I also removed the temp, logs (actually you have to leave the directory, just clear the files) and the work/Catalina/localhost directories from the jira installation. # I then copied the osuser.xml and the crowd.properties files from the 3.13.5 install to the 4 install. # I edited the crowd.properties file in hopes that I could point it to the new crowd install on auth.mbari.org and it would work, but we will see. # I then started jira and tailed the log file. # All looked OK (other than iCal plugin stack trace again), so I went to localhost:8180 and got step 2 of the wizard. I used the same info as before. # I logged in as the local admin account and it looks like the system picked up the crowd connection, but lets see what server it used! Hey it used the one I edited into the file! Sweet ... now let's see if the import works. # I copied the 3.13.5 zip file to the import directory again and this time, I untarred the attachments into the import/attachments directory. # I kicked off the restore as before and it worked through it fine. # Shutdown and restarted system, tailing the log file and then went to localhost:8180 ]]> 27558186 27590952 4.4: [https://confluence.atlassian.com/display/JIRA044/Migrating+JIRA+to+Another+Server] ## The JIRA configuration tool: [https://confluence.atlassian.com/display/JIRA044/Using+the+JIRA+Configuration+Tool] h5. Steps # (/) Create new VM named bugs.mbari.org in the DMZ # (/) Have Neil create database Jira_Temp on solstice2.shore.mbari.org # (/) Have Neil create database Jira on solstice2.shore.mbari.org # (/) Have Pat install Java 7 on bugs.shore.mbari.org # (/) Have Pete plumb holes through firewall so processes on bugs.mbari.org can get to Solstice2 # (/) Have Pat create DB_Collaboration account on bugs so it can run JIRA under that account and it can connect to solstice2 using that NT Domain account. # (/) Upgrade license on Atlassian site # (/) Log into bugs.shore.mbari.org # (/) Download 3.13.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 4.4.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 5.2.11 standalone Linux 64 bit tar.gz (not sure this version is necessary, but at least I have it) # (/) Unzip and untar the file to /opt # (/) Download latest JIRA (6.4.7 as of this writing). # (/) Unzip and untar it to /opt # Performed Test Upgrade ## (/) In order to export the current stuff in JIRA, I had to shut off access so people could not change the data while I was backing it up. ## (/) I ssh'd to oceana.mbari.org as root and edited the /opt/jira/conf/server.xml file and commented out the Connector section that had the port of 8010 to shut it off from the normal serving route. ## (/) I uncommented the 8082 port connector and the 8443 port connector so that I could still get to the server. ## (/) I stopped and started the JIRA server and in the log file I got a "keystore was tampered with..." which is not surprising. ## (/) I could then browser over to http://oceana.mbari.org:8082/jira ## (/) Then through the Administration console, I did an XML backup ## (/) I then created a tar of all the attachments in the /data/jira_3_12/attachments directory ## (/) I moved both the XML and tar files to the /root/jira-upgrade directory ## (/) I then reversed the changes to the server.xml file and shut down JIRA ## (/) I left it down during the next steps in case it went so well, I could just point people to the new server (yeah, right). ## (/) I then browsed to the crowd server on oceana and add a new application using: ### URL: http://bugs.mbari.org/jira3135 ### IP: 134.89.2.29 ### Name: JIRA3135 ### Password: (ask Kevin) :) ## (/) On bugs, I made a copy of the JIRA 3.13.5 download in the /opt directory and unzipped and untarred it. ## (/) In order to configure the crowd connection I did the following: ### (/) I scp'd the /opt/crowd/client/crowd-integration-client-1.6.jar file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I removed the existing 1.6.1 crowd client jar from the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I scp'd the /opt/crowd/client/conf/crowd.properties file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I scp'd the /opt/crowd/client/conf/crowd-ehcache.xml file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I edited the crowd.properties file on bugs to look like: {noformat} application.name JIRA3135 application.password (ask Kevin) application.login.url http://oceana.mbari.org:8095/crowd/console/ crowd.server.url http://oceana.mbari.org:8095/crowd/services/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 0 session.lastvalidation session.lastvalidation {noformat} ### (/) I edited the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/osuser.xml file to comment out the current authentication mechanism and then uncomment the crowd one. ## (/) I then edited the /opt/atlassian-jira-standalone-3.13.5/conf/server/xml file and configured the database connection to the Jira_Temp database on Solstice2. I looked like this: {noformat} {noformat} ## (/) Edit the /opt/atlassian/jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/entityengine.xml and changed it from 'hsql' to 'mssql' and delete the line with "PUBLIC" in it per the instructions in the comments in that file. ## (/) I edited the /etc/httpd/conf/httpd.conf file and created a proxy pass at the bottom of the file to point a normal URL to the default port 8080 for JIRA: {noformat} # Proxy Pass for JIRA ProxyPass http://bugs.mbari.org:8080 ProxyPassReverse http://bugs.mbari.org:8080 {noformat} ## (/) I restarted Apache ## (/) I scp'd the jtds driver from oceana to the /opt/atlassian-jira-standalone-3.13.5/common/lib directory (you could down from the internet) ## (/) I then went to the /opt/atlassian-jira-standalone-3.13.5/ directory and ran './bin/startup.sh'. From the log file, I could tell things were hanging. After some troubleshooting I am wondering if the local firewall is preventing the application to get access to the database on solstice2. I can telnet to port 1433, but I can't browse to the base http://bugs.mbari.org from anywhere but the local web browser. I have submitted a ticket. ## (/) I restarted the old JIRA with my hopes dashed :(. ## (/) Pat disabled the firewall on bugs.mbari.org but it still hung trying to connect to solstice2.shore.mbari.org. That is really, really perplexing. Neil mentioned that solstice2 is using Kerberos and solstice is not. Checking with the JTDS docs, version 1.3.1 of the driver added kerberos support, so I downloaded that driver and added the 'userKerberos=true' property to the URL in the server.xml file and restarted. Got an error about no credentials, so added user and password properties to the URL. Nope, no luck. Never did figure this one out, but I had Pat pull the VM inside the firewall and after some thrash it worked. Well, it sort of worked ... sigh. It turns out I had downloaded the standard version instead of the enterprise version. I need to redo this work ... grrr. ## (/) I deleted all the tables in the Jira_Temp database and removed the /data/jira3135/indexes directory (and recreated). ## (/) I downloaded the enterprise version of the 3.13.5 server. I made a copy in the /opt directory and unzipped and untarred the file. ## (/) I went back to crowd and edited the application to change the properties to: ### URL: http://bugs.shore.mbari.org:8080 ### IP: 134.89.12.31 ### Name: jira3135 ### Password: (ask Kevin) :) ## (/) I then repeated the steps above to get the server up and running with the following differences: ### The server name is now bugs.shore.mbari.org ### The paths given above are a little different in that they no longer say "standard" but say "enterprise" ### I deleted the proxy pass as it seemed to have issues before and this is only temporary anyway. ## (/) I then browsed to http://bugs.shore.mbari.org:8080 ## (/) It took me to the start up page and at the top was the option to 'import your existing data'. Seemed too good not to try. I clicked on the link. It asked me for the backup file location and the location where the indexes would be stored. ## (/) I copied the XML zip file and the attachments tar file to the /data/original directory. ## (/) I created the /data/jira3135/indexes and used those directories ... it fired off the import and I waited. ## (/) I tailed the log file to watch the import. Holy crap, it worked!!! I could log in and everything! I copied the results from the log file here for posterity sake: {noformat} 2015-07-22 20:55:45,156 http-8080-Processor22 INFO [jira.action.admin.DataImport] Running data import 2015-07-22 20:55:45,179 http-8080-Processor22 INFO [jira.action.admin.DataImport] Importing data.. 2015-07-22 20:55:45,186 http-8080-Processor22 INFO [jira.action.admin.DataImport] Start parsing XML with SAX Parser 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] XML successfully parsed 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] Removing all entries from the database. 2015-07-22 20:56:24,593 http-8080-Processor22 INFO [jira.action.admin.DataImport] All entries removed. 2015-07-22 20:56:24,594 http-8080-Processor22 INFO [jira.action.admin.DataImport] Started storing 410414 Generic Values 2015-07-22 21:01:51,967 http-8080-Processor22 INFO [jira.action.admin.DataImport] Finished storing Generic Values 2015-07-22 21:01:52,329 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:52,361 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:54,683 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLink' to module 'jira.user.format:profile-link-user-format'. 2015-07-22 21:01:54,724 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullName' to module 'jira.user.format:full-name-user-format'. 2015-07-22 21:01:54,773 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkSearcher' to module 'jira.user.format:profile-link-searcher-user-format'. 2015-07-22 21:01:54,784 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkExternal' to module 'jira.user.format:profile-link-external-user-format'. 2015-07-22 21:01:54,795 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkActionHeader' to module 'jira.user.format:profile-link-action-header-user-format'. 2015-07-22 21:01:54,807 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullProfile' to module 'jira.user.format:full-profile-user-format'. 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/comments 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/issues 2015-07-22 21:01:55,641 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/plugins 2015-07-22 21:01:55,867 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:01:55,871 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/issues does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:55,873 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/comments does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,033 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,257 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,889 http-8080-Processor22 ERROR [atlassian.jira.upgrade.ConsistencyCheckImpl] Attachments are turned on, but attachment path [/data/jira_3_12/attachments] invalid - disabling attachments 2015-07-22 21:02:13,904 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Detected that an upgrade is needed; existing data at build 299 2015-07-22 21:02:13,907 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Doing Upgrade... 2015-07-22 21:02:13,915 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value' succeeded 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 317 2015-07-22 21:02:13,944 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite filters - make each filter a favourite of its owner. 2015-07-22 21:02:17,822 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build319] Could not find author 'fpy' for filter with id '10040' 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite filters - make each filter a favourite of its owner.' succeeded 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 319 2015-07-22 21:02:17,995 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise Share Permissions. Move old shares to new shares. 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise Share Permissions. Move old shares to new shares.' succeeded 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 321 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Migrating the old JIRA UI colors to the new JIRA 3.13 colors 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build322] Custom color detected for jira.lf.menu.bgcolour : #336699 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Migrating the old JIRA UI colors to the new JIRA 3.13 colors' succeeded 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 322 2015-07-22 21:02:18,025 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite dashboards - make each dashboard a favourite of its owner. 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'cmcgann' for dashboard with id '10030' 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'fpy' for dashboard with id '10060' 2015-07-22 21:02:18,423 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'kanna' for dashboard with id '10040' 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite dashboards - make each dashboard a favourite of its owner.' succeeded 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 325 2015-07-22 21:02:18,625 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Reindexing all data in JIRA to include Favourites. 2015-07-22 21:02:18,648 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All starting... 2015-07-22 21:02:18,650 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 0% complete. Current index: Issue 2015-07-22 21:02:18,654 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:02:18,809 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 1% complete. Current index: Issue 2015-07-22 21:02:18,855 indexerPool-2-thread-10 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 2% complete. Current index: Issue 2015-07-22 21:02:18,899 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 3% complete. Current index: Issue 2015-07-22 21:02:18,945 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 4% complete. Current index: Issue 2015-07-22 21:02:19,012 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 5% complete. Current index: Issue . . . 2015-07-22 21:02:26,164 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 95% complete. Current index: Issue 2015-07-22 21:02:26,232 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 96% complete. Current index: Issue 2015-07-22 21:02:26,316 indexerPool-2-thread-9 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 97% complete. Current index: Issue 2015-07-22 21:02:26,771 indexerPool-2-thread-3 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: Issue 2015-07-22 21:02:27,261 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 8607ms. Indexer: DefaultIndexManager: paths: [/data/jira3135/indexes/issues, /data/jira3135/indexes/comments] 2015-07-22 21:02:27,263 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: SearchRequest 2015-07-22 21:02:27,268 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,293 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: SearchRequest 2015-07-22 21:02:27,308 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: PortalPage 2015-07-22 21:02:27,312 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,377 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: PortalPage 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 115ms. Indexer: SharedEntityIndexManager: paths: [/data/jira3135/indexes/entities/portalpage, /data/jira3135/indexes/entities/searchrequest] 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All complete. Total time: 8722ms. 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Reindexing all data in JIRA to include Favourites.' succeeded 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 326 2015-07-22 21:02:27,397 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade succeeded! Setting data build number to 360 2015-07-22 21:02:27,469 JiraQuartzScheduler_Worker-0 WARN [service.services.export.ExportService] Backup directory /data/jira_3_12/backup does not exist {noformat} {warning:title=Paths} It appears that the upgraded JIRA will still look for the attachments and the backup locations in the original places. So I created /data/jira_3_12/backup and untarred the original attachments to /data/jira_3_12 and then everything worked (including attachements) in the new JIRA. {warning} ## (/) I then used the upgraded JIRA to generate a new XML backup and stored it in /data/original/3.13.5 along with another tar of the files in /data/jira_3_12/attachments. ## (/) I then shutdown the JIRA server. *I should be ready to move on to version 4 upgrade WHEW* ## So, before moving on, I decided that it would be a really good idea to spin up a new Crowd instance to get rid of the :8443 in the URL and to move off of RedHat per IS requests. I have a ticket in for a new VM and a new database to try to get this going. I am waiting on that before moving on. ## (/) Pat created the VM and Neil created the database. ## (/) I logged into auth.mbari.org (name of the VM) and downloaded crowd which I unzipped to the /opt directory ## (/) I then created a /data/crowd directory and gave my account permissions on it and then edited the /opt/atlassian..../crowd-webapp/WEB-INF/classes/crowd-init.properties file to set that as the crowd home directory. ## (/) The instructions say to download the JDBC driver, but they already have JTDS 1.2.7 in the download so I did not do anything. ## (/) You have to manually connect up CrowdID to a database as they setup wizard does not currently do this. ### (/) They say to download the driver, but again 1.2.7 was there so I did nothing. ### (/) I edited the /opt/atlassian.../apache-tomcat/conf/Catalina/localhost/openidserver.xml to look like: {noformat} {noformat} ### (/) I edited the /opt/atlassian.../build.properties files to look like: {noformat} # Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See https://confluence.atlassian.com/display/CROWD/Connecting+Crowd+to+a+Database hibernate.dialect=org.hibernate.dialect.SQLServerDialect # The Hibernate transaction factory to use. See https://confluence.atlassian.com/display/CROWD/Configuring+Crowd hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory # The http port you wish to run crowd from, ie: http://localhost:8095/crowd crowd.tomcat.connector.port=8095 # Tomcat requires a unique port for shutdown crowd.tomcat.shutdown.port=8020 # Crowd context root crowd.url=http://localhost:8095/crowd # Demo context root demo.url=http://localhost:8095/demo # OpenID server context root openidserver.url=http://localhost:8095/openidserver {noformat} ### (/) I then ran the build.sh script in the root of /opt/atlassian... ## (/) I fired up crowd using the /opt/atlassian.../start_crowd.sh script ## (/) I then went to http://auth.mbari.org:8095/crowd to kick off the start up wizard ## (/) I grabbed a new eval license from my account on atlassian and pasted into the license page. ## (/) I selected "New install" on the next page. ## (/) I configured the JDBC connection using this connection URL with user DB_Collaboration {noformat} jdbc:jtds:sqlserver://dione.mbari.org:51001/Crowd;domain=SHORE;useNTLMv2=TRUE {noformat} ## (/) I left the "Options" as they came up {warning:title=Paths} Not sure if this is a problem, but because I started the set up using auth.mbari.org, it set the Base URL to http://auth.mbari.org:8095/crowd instead of localhost. Hope that is not a problem. We will see. {warning} ## (/) I configured the email connection using the settings from [here|https://wind.shore.mbari.org/is/howto/email/mbarimail/imap] and I used my network login (probably shouldn't be doing that ... not sure where it stores my password, but I am assuming in the DB). ## (/) For the local admin account, I created a user named 'crowdadm' so it would not clash with my LDAP account. See Kevin Gomes for password information. ## (/) I checked the OpenID server as an integrated application ## (/) It then took me to the login page and I logged in using the newly minted admin account. Seemed all is well so far. ## (/) I visited the openidserver URL as well and that seemed OK. ## (/) I decided to wait on configuring the MBARI LDAP directory until I got everything with SSL working. ## (/) Now the next step was to follow the directions to configure Crowd to run over SSL found [here|https://confluence.atlassian.com/display/CROWD/Configuring+Crowd+to+Work+with+SSL] ## (/) I shutdown crowd. Note that the stop script does not shutdown things correctly and I noticed the crowd app running as root. That should not be if I started as kgomes. Not sure what is up with that. ## (/) Now Joe had already configured SSL once, so I used his connector configuration in the server.xml file and so the final file looked like: {noformat} {noformat} ## (/) I then edited the /data/crowd/crowd.properties to look like: {noformat} #Sat Aug 01 09:05:15 PDT 2015 session.lastvalidation=session.lastvalidation session.tokenkey=session.tokenkey crowd.server.url=https\://localhost\:8443/crowd/services/ application.name=crowd http.timeout=30000 session.isauthenticated=session.isauthenticated application.login.url=https\://localhost\:8443/crowd/console/ session.validationinterval=0 application.password=Y1Xp3OorCmsOP4eruL1dmH {noformat} One thing to note here is that based on a comment from the SSL configuration page at atlassian (Steve's comment), you are supposed to leave all the host names the same. For example, if the file says localhost, leave it localhost. So this created a bit of a problem based on the fact that I had left the base URL pointing to auth.mbari.org in the wizard steps above. That step wrote auth.mbari.org to the /data/crowd/crowd.properties. All the other files reference localhost, so to be consistent, I changed auth.mbari.org to localhost in the /data/crowd/crowd.properties file. We will see if this works. ## (/) Per the instructions on the atlassian page (referenced above), I also edited the build.properties file and the /client/conf/crowd.properties files before I restarted and used the SSL URLs ## build.properties: {noformat} # Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See https://confluence.atlassian.com/display/CROWD/Connecting+Crowd+to+a+Database hibernate.dialect=org.hibernate.dialect.SQLServerDialect # The Hibernate transaction factory to use. See https://confluence.atlassian.com/display/CROWD/Configuring+Crowd hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory # The http port you wish to run crowd from, ie: http://localhost:8095/crowd crowd.tomcat.connector.port=8095 # Tomcat requires a unique port for shutdown crowd.tomcat.shutdown.port=8020 # Crowd context root crowd.url=https://localhost:8443/crowd # Demo context root demo.url=https://localhost:8443/demo # OpenID server context root openidserver.url=https://localhost:8443/openidserver {noformat} ## crowd.properties (client) {noformat} application.name crowd application.password password application.login.url https://localhost:8443/crowd/console/ crowd.server.url https://localhost:8443/crowd/services/ crowd.base.url https://localhost:8443/crowd/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 2 session.lastvalidation session.lastvalidation {noformat} ## (/) Although not stated, I am assuming you would need to run the build.sh script to push the build.properties changes to their proper places, so I did that. Note that before doing that, I know that it will clobber the server.xml changes I made, so I made a copy of that file and diff'd them after and then rolled the previous changes to the new server.xml file. Actually, amazingly enough, it seems to have done the connector entry correctly so I left it after running the build.sh script. ## (/) Crossed my fingers and then restarted crowd. I tailed the catalina.out file and did not see any stack traces so that is a good sign! ## (/) I visited https://auth.mbari.org:8443/crowd first. It could not find that page, but I suspect that is because I am browsing from the outside, so I tried just https://auth.mbari.org/crowd and got a service unavailable. I am suspecting that this is a combination of firewall and proxy pass and I will send this info to Joe. From what I can see on the crowd side, it seems like the server started cleanly, we just can't get to it. I tried to reach it from a browser on the machine itself too (through VNC) with the same service not available. ## (/) Here are the notes from Joe after he fixed it! Wooohooo! {noformat} Hey Kevin, Thanks for starting clean! I had to make a few adjustments. 1-I modified the server.xml file in /opt/atlassian-crowd-2.8.3/apache-tomcat/conf/server.xml so there are two connectors per the instructions on the Atlassian site. I have backed up this good server.xml file in /etc/temp/ if you want to browse it to see what I did. Of note is that I removed all the jargon referencing the types of ciphers available to simplify things for now. 2-I modified /data/crowd/crowd.properties to have crowd.server.url=https\://localhost\:8443/crowd/services/ application.login.url=https\://localhost\:8443/crowd/console/ But that would cause my login to error with an error saying it was unable to reach the authentication server. I scratched my head for a bit. When I revert the values to just using non-SSL and try to log in, I just get an "invalid login" (I don't know the crowdadm password). So I worked under the assumption that if I can configure SSL to get an "invalid login" when logging in then it would work when provided real credentials. So, I then changed /data/crowd/crowd.proprties to: crowd.server.url=https\://auth.mbari.org\:8443/crowd/services/ application.login.url=https\://auth.mbari.org\:8443/crowd/console/ And now when I try to log in with SSL it says "invalid login". Strange because all the other values I can find only show "localhost" .. in any case... Can you try to log in now? {noformat} ## (/) Next I moved on to configuring the connection to MBARI's LDAP server to enable our logins through Crowd and CrowdID ## (/) I clicked on "Add Directory" in crowd. ## (/) I selected "Connector" then clicked Next ## (/) I put ldap.shore.mbari.org as the name of the server ## (/) I selected "Use memberOf for group memberships" ## (/) I used "OU=AllUsers,DC=shore,DC=mbari,DC=org" for the Base DN ## (/) I used "CN=LDAPbind,OU=Special,OU=AllUsers,DC=shore,DC=mbari,DC=org" for the Username (talk to Pat Allen for password) ## (/) I tested the connection (button click) and it passed. ## (/) I de-selected all the capabilities of the connector as it is a ready only connector and then saved it. It synchronized correctly! ## (/) At first, I could not login using my MBARI credentials, but after going to the "crowd" application in crowd (logged in as the local admin), I had to add the LDAP directory and configure it to "Allow all to authenticate", then I was able to login. After this, the last step was to get this to run as a different user and lock down various directories. I went through the entire directory structure /opt/atlassian... and set up so that root owned all read-only locations and DB_Collaboration (account set up by IS) owned the other stuff. I also gave full ownership to the /data/crowd directory to DB_Collaboration so it could write there. Pat set up a script to start on boot and after a little tweaking, it now starts on boot. {warning:title=CrowdID log file} One thing that came up here was that when the crowdID application ran, it tried to write a log file to the location where the process was launched from (which is /opt/atlassian...). This is a bad thing and I figured out that I could change that location by changing the file /opt/atlassian-crowd-2.8.3/crowd-openidserver-webapp/WEB-INF/classes/log4j.properties and hardcoding the /data/crowd/logs/atlassian-crowd-openid-server.log and then restarted the application. {warning} ## (/) Another note is the when an application tried to use the OpenID application, it would get redirected to localhost. I changed the /opt/atlassian.../crowd-openidserver-webapp/WEB-INF/classes/crowd.properties file to look like: {noformat} #Sat Aug 01 10:03:18 PDT 2015 session.lastvalidation=session.lastvalidation session.tokenkey=session.tokenkey crowd.server.url=http\://localhost\:8095/crowd/services/ application.name=crowd-openid-server #application.login.url.template=http\://localhost\:8095/openidserver?returnToUrl\=${RETURN_TO_URL} application.login.url.template=https\://auth.mbari.org/openidserver?returnToUrl\=${RETURN_TO_URL} session.isauthenticated=session.isauthenticated #application.base.url=http\://localhost\:8095/openidserver application.base.url=https\://auth.mbari.org/openidserver #application.login.url=http\://localhost\:8095/openidserver application.login.url=https\://auth.mbari.org/openidserver session.validationinterval=0 application.password=password {noformat} and that seems to have fixed it. # (/) It is finally time to move on to the version 4 upgrade ... holy crap. I first went to the *new* crowd install (auth.mbari.org) and logged in as the crowdadm. # (/) I clicked on Applications, then on Add Application # (/) I selected JIRA from the Application type drop-down # (/) I entered jira445 as the username. Ask Kevin about the password. # (/) I used http://bugs.shore.mbari.org:8081 as the URL # (/) I used 134.89.12.31 as the IP address. # (/) I selected only the MBARI LDAP directory. # (/) Then I selected "Allow all users to authenticate" # (/) Then I clicked on "Add Application" # (/) I VNC'd into bugs.mbari.org. As it turns out, for Linux, there is an installer program to download. I downloaded the .bin for 64 bit Linux installer and moved it to the jira-upgrade directory. # (/) I chmod'd the file to make it executable and ran it. It gave me a warning about not being root, but I went ahead with it. # (/) It asked for the JIRA home and data directory, which I specified as /opt/jira4 and /data/jira445. # (/) For the ports, I specified 8180 and 8105 (HTTP and control respectively). It then extracted all the files and launched JIRA. It said if finished, so I opened a local browser to http://localhost:8180 which kicked off the start up wizard. # (/) I specified the external database using: ## solstice2.shore.mbari.org (server) ## 1433 (port) ## jira4 (database) ## DB_Collaboration (username) ## (password ask Kevin) ## dbo (schema) # But all this failed as it seems to just want to try and use the SQL server authentication instead of domain. I will have to do it manually. # (/) I stopped the server using the bin/stop-jira.sh script. # (/) I created and edited /data/jira445/dbconfig.xml and made it look like the following: {noformat} ?xml version="1.0" encoding="UTF-8"?> defaultDS default mssql jiraschema jdbc:jtds:sqlserver://solstice2.shore.mbari.org:1433/Jira4;domain=SHORE;useNTLMv2=true net.sourceforge.jtds.jdbc.Driver DB_Collaboration (ask Kevin) 15 {noformat} # (/) I then started it again using bin/start-jira.sh and tailed the catalina.out file. Got a bunch of errors related to the schema 'jiraschema', I edited the file and changed the schema to 'dbo' and restarted. That seemed to do it. There was one stack trace for some iCal plugin, but looks OK other than that. # I browsed back to localhost:8180 and the wizard moved to step 2. There was an option to import existing data bit without the crowd connection, I thought I should set it up manually, connect to crowd, then import. I generated an evaluation license, called the app "MBARI JIRA4" and change the server in the url to bugs.shore.mbari.org # For the admin, I created an account called 'jiraadm' (ask Kevin for password). # Since this is a temporary system, I left the email system disabled. # I logged in as jiraadm, went to Administration, then Users, then clicked on Add Directory and chose Atlassian Crowd. Note that I had to set the server URL to http://auth.mbari.org:8095/crowd or I would have had to configure all this SSL crap that I did not want to do for this temporary install. # It tested successfully, I clicked Save and it went through a 13 second sync, whew! # I then went to System->Import and Export->Restore System # I copied the jira-upgrade-3.13.5.zip file from the previous version export into /data/jira445/import and then entered that file name along with the new evaluation license again. # I worked through progress bar after I clicked on Restore (it took a really long time). # I then stopped, restarted and tailed the log file. # I am thinking now I should have put the attachments in the import attachments directory, but I am hoping I can just copy them to the data/attachments directory. # UG! I got some error during the import. The exception read: "JIRA is unable to migrat the User Directory configuration because external users exist but the osuser.xml file is not available". It then gave me a link to a doc that talked about making the old user files available before the upgrade ... crap. So I needed to copy the osuser.xml and crowd.properties file from atlassian-jira/WEB-INF/classes directory on the old install to the same directory on the new install ... sigh. This means I am going to blow away everything and start over. # I shutdown jira4 # I dropped all things in the database and deleted all content in the /data/jira445 directory (except for the dbconfig.xml file). # I also removed the temp, logs (actually you have to leave the directory, just clear the files) and the work/Catalina/localhost directories from the jira installation. # I then copied the osuser.xml and the crowd.properties files from the 3.13.5 install to the 4 install. # I edited the crowd.properties file in hopes that I could point it to the new crowd install on auth.mbari.org and it would work, but we will see. # I then started jira and tailed the log file. # All looked OK (other than iCal plugin stack trace again), so I went to localhost:8180 and got step 2 of the wizard. I used the same info as before. # I logged in as the local admin account and it looks like the system picked up the crowd connection, but lets see what server it used! Hey it used the one I edited into the file! Sweet ... now let's see if the import works. # I copied the 3.13.5 zip file to the import directory again and this time, I untarred the attachments into the import/attachments directory. # I kicked off the restore as before and it worked through it fine. # Shutdown and restarted system, tailing the log file and then went to localhost:8180 # I can see issues (before logging in) and it all looks good!! The attachments did not move over from the import directory, so I copied the tar file from /data/jira445/import to /data/jira445/data and then untarred it there, then removed the tar file and the import zip file from the import directory. # Now I will try to login using my MBARI account.]]> 27558188 27590954 4.4: [https://confluence.atlassian.com/display/JIRA044/Migrating+JIRA+to+Another+Server] ## The JIRA configuration tool: [https://confluence.atlassian.com/display/JIRA044/Using+the+JIRA+Configuration+Tool] h5. Steps # (/) Create new VM named bugs.mbari.org in the DMZ # (/) Have Neil create database Jira_Temp on solstice2.shore.mbari.org # (/) Have Neil create database Jira on solstice2.shore.mbari.org # (/) Have Pat install Java 7 on bugs.shore.mbari.org # (/) Have Pete plumb holes through firewall so processes on bugs.mbari.org can get to Solstice2 # (/) Have Pat create DB_Collaboration account on bugs so it can run JIRA under that account and it can connect to solstice2 using that NT Domain account. # (/) Upgrade license on Atlassian site # (/) Log into bugs.shore.mbari.org # (/) Download 3.13.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 4.4.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 5.2.11 standalone Linux 64 bit tar.gz (not sure this version is necessary, but at least I have it) # (/) Unzip and untar the file to /opt # (/) Download latest JIRA (6.4.7 as of this writing). # (/) Unzip and untar it to /opt # Performed Test Upgrade ## (/) In order to export the current stuff in JIRA, I had to shut off access so people could not change the data while I was backing it up. ## (/) I ssh'd to oceana.mbari.org as root and edited the /opt/jira/conf/server.xml file and commented out the Connector section that had the port of 8010 to shut it off from the normal serving route. ## (/) I uncommented the 8082 port connector and the 8443 port connector so that I could still get to the server. ## (/) I stopped and started the JIRA server and in the log file I got a "keystore was tampered with..." which is not surprising. ## (/) I could then browser over to http://oceana.mbari.org:8082/jira ## (/) Then through the Administration console, I did an XML backup ## (/) I then created a tar of all the attachments in the /data/jira_3_12/attachments directory ## (/) I moved both the XML and tar files to the /root/jira-upgrade directory ## (/) I then reversed the changes to the server.xml file and shut down JIRA ## (/) I left it down during the next steps in case it went so well, I could just point people to the new server (yeah, right). ## (/) I then browsed to the crowd server on oceana and add a new application using: ### URL: http://bugs.mbari.org/jira3135 ### IP: 134.89.2.29 ### Name: JIRA3135 ### Password: (ask Kevin) :) ## (/) On bugs, I made a copy of the JIRA 3.13.5 download in the /opt directory and unzipped and untarred it. ## (/) In order to configure the crowd connection I did the following: ### (/) I scp'd the /opt/crowd/client/crowd-integration-client-1.6.jar file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I removed the existing 1.6.1 crowd client jar from the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I scp'd the /opt/crowd/client/conf/crowd.properties file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I scp'd the /opt/crowd/client/conf/crowd-ehcache.xml file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I edited the crowd.properties file on bugs to look like: {noformat} application.name JIRA3135 application.password (ask Kevin) application.login.url http://oceana.mbari.org:8095/crowd/console/ crowd.server.url http://oceana.mbari.org:8095/crowd/services/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 0 session.lastvalidation session.lastvalidation {noformat} ### (/) I edited the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/osuser.xml file to comment out the current authentication mechanism and then uncomment the crowd one. ## (/) I then edited the /opt/atlassian-jira-standalone-3.13.5/conf/server/xml file and configured the database connection to the Jira_Temp database on Solstice2. I looked like this: {noformat} {noformat} ## (/) Edit the /opt/atlassian/jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/entityengine.xml and changed it from 'hsql' to 'mssql' and delete the line with "PUBLIC" in it per the instructions in the comments in that file. ## (/) I edited the /etc/httpd/conf/httpd.conf file and created a proxy pass at the bottom of the file to point a normal URL to the default port 8080 for JIRA: {noformat} # Proxy Pass for JIRA ProxyPass http://bugs.mbari.org:8080 ProxyPassReverse http://bugs.mbari.org:8080 {noformat} ## (/) I restarted Apache ## (/) I scp'd the jtds driver from oceana to the /opt/atlassian-jira-standalone-3.13.5/common/lib directory (you could down from the internet) ## (/) I then went to the /opt/atlassian-jira-standalone-3.13.5/ directory and ran './bin/startup.sh'. From the log file, I could tell things were hanging. After some troubleshooting I am wondering if the local firewall is preventing the application to get access to the database on solstice2. I can telnet to port 1433, but I can't browse to the base http://bugs.mbari.org from anywhere but the local web browser. I have submitted a ticket. ## (/) I restarted the old JIRA with my hopes dashed :(. ## (/) Pat disabled the firewall on bugs.mbari.org but it still hung trying to connect to solstice2.shore.mbari.org. That is really, really perplexing. Neil mentioned that solstice2 is using Kerberos and solstice is not. Checking with the JTDS docs, version 1.3.1 of the driver added kerberos support, so I downloaded that driver and added the 'userKerberos=true' property to the URL in the server.xml file and restarted. Got an error about no credentials, so added user and password properties to the URL. Nope, no luck. Never did figure this one out, but I had Pat pull the VM inside the firewall and after some thrash it worked. Well, it sort of worked ... sigh. It turns out I had downloaded the standard version instead of the enterprise version. I need to redo this work ... grrr. ## (/) I deleted all the tables in the Jira_Temp database and removed the /data/jira3135/indexes directory (and recreated). ## (/) I downloaded the enterprise version of the 3.13.5 server. I made a copy in the /opt directory and unzipped and untarred the file. ## (/) I went back to crowd and edited the application to change the properties to: ### URL: http://bugs.shore.mbari.org:8080 ### IP: 134.89.12.31 ### Name: jira3135 ### Password: (ask Kevin) :) ## (/) I then repeated the steps above to get the server up and running with the following differences: ### The server name is now bugs.shore.mbari.org ### The paths given above are a little different in that they no longer say "standard" but say "enterprise" ### I deleted the proxy pass as it seemed to have issues before and this is only temporary anyway. ## (/) I then browsed to http://bugs.shore.mbari.org:8080 ## (/) It took me to the start up page and at the top was the option to 'import your existing data'. Seemed too good not to try. I clicked on the link. It asked me for the backup file location and the location where the indexes would be stored. ## (/) I copied the XML zip file and the attachments tar file to the /data/original directory. ## (/) I created the /data/jira3135/indexes and used those directories ... it fired off the import and I waited. ## (/) I tailed the log file to watch the import. Holy crap, it worked!!! I could log in and everything! I copied the results from the log file here for posterity sake: {noformat} 2015-07-22 20:55:45,156 http-8080-Processor22 INFO [jira.action.admin.DataImport] Running data import 2015-07-22 20:55:45,179 http-8080-Processor22 INFO [jira.action.admin.DataImport] Importing data.. 2015-07-22 20:55:45,186 http-8080-Processor22 INFO [jira.action.admin.DataImport] Start parsing XML with SAX Parser 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] XML successfully parsed 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] Removing all entries from the database. 2015-07-22 20:56:24,593 http-8080-Processor22 INFO [jira.action.admin.DataImport] All entries removed. 2015-07-22 20:56:24,594 http-8080-Processor22 INFO [jira.action.admin.DataImport] Started storing 410414 Generic Values 2015-07-22 21:01:51,967 http-8080-Processor22 INFO [jira.action.admin.DataImport] Finished storing Generic Values 2015-07-22 21:01:52,329 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:52,361 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:54,683 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLink' to module 'jira.user.format:profile-link-user-format'. 2015-07-22 21:01:54,724 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullName' to module 'jira.user.format:full-name-user-format'. 2015-07-22 21:01:54,773 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkSearcher' to module 'jira.user.format:profile-link-searcher-user-format'. 2015-07-22 21:01:54,784 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkExternal' to module 'jira.user.format:profile-link-external-user-format'. 2015-07-22 21:01:54,795 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkActionHeader' to module 'jira.user.format:profile-link-action-header-user-format'. 2015-07-22 21:01:54,807 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullProfile' to module 'jira.user.format:full-profile-user-format'. 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/comments 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/issues 2015-07-22 21:01:55,641 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/plugins 2015-07-22 21:01:55,867 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:01:55,871 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/issues does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:55,873 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/comments does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,033 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,257 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,889 http-8080-Processor22 ERROR [atlassian.jira.upgrade.ConsistencyCheckImpl] Attachments are turned on, but attachment path [/data/jira_3_12/attachments] invalid - disabling attachments 2015-07-22 21:02:13,904 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Detected that an upgrade is needed; existing data at build 299 2015-07-22 21:02:13,907 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Doing Upgrade... 2015-07-22 21:02:13,915 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value' succeeded 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 317 2015-07-22 21:02:13,944 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite filters - make each filter a favourite of its owner. 2015-07-22 21:02:17,822 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build319] Could not find author 'fpy' for filter with id '10040' 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite filters - make each filter a favourite of its owner.' succeeded 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 319 2015-07-22 21:02:17,995 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise Share Permissions. Move old shares to new shares. 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise Share Permissions. Move old shares to new shares.' succeeded 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 321 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Migrating the old JIRA UI colors to the new JIRA 3.13 colors 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build322] Custom color detected for jira.lf.menu.bgcolour : #336699 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Migrating the old JIRA UI colors to the new JIRA 3.13 colors' succeeded 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 322 2015-07-22 21:02:18,025 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite dashboards - make each dashboard a favourite of its owner. 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'cmcgann' for dashboard with id '10030' 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'fpy' for dashboard with id '10060' 2015-07-22 21:02:18,423 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'kanna' for dashboard with id '10040' 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite dashboards - make each dashboard a favourite of its owner.' succeeded 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 325 2015-07-22 21:02:18,625 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Reindexing all data in JIRA to include Favourites. 2015-07-22 21:02:18,648 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All starting... 2015-07-22 21:02:18,650 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 0% complete. Current index: Issue 2015-07-22 21:02:18,654 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:02:18,809 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 1% complete. Current index: Issue 2015-07-22 21:02:18,855 indexerPool-2-thread-10 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 2% complete. Current index: Issue 2015-07-22 21:02:18,899 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 3% complete. Current index: Issue 2015-07-22 21:02:18,945 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 4% complete. Current index: Issue 2015-07-22 21:02:19,012 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 5% complete. Current index: Issue . . . 2015-07-22 21:02:26,164 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 95% complete. Current index: Issue 2015-07-22 21:02:26,232 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 96% complete. Current index: Issue 2015-07-22 21:02:26,316 indexerPool-2-thread-9 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 97% complete. Current index: Issue 2015-07-22 21:02:26,771 indexerPool-2-thread-3 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: Issue 2015-07-22 21:02:27,261 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 8607ms. Indexer: DefaultIndexManager: paths: [/data/jira3135/indexes/issues, /data/jira3135/indexes/comments] 2015-07-22 21:02:27,263 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: SearchRequest 2015-07-22 21:02:27,268 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,293 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: SearchRequest 2015-07-22 21:02:27,308 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: PortalPage 2015-07-22 21:02:27,312 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,377 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: PortalPage 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 115ms. Indexer: SharedEntityIndexManager: paths: [/data/jira3135/indexes/entities/portalpage, /data/jira3135/indexes/entities/searchrequest] 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All complete. Total time: 8722ms. 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Reindexing all data in JIRA to include Favourites.' succeeded 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 326 2015-07-22 21:02:27,397 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade succeeded! Setting data build number to 360 2015-07-22 21:02:27,469 JiraQuartzScheduler_Worker-0 WARN [service.services.export.ExportService] Backup directory /data/jira_3_12/backup does not exist {noformat} {warning:title=Paths} It appears that the upgraded JIRA will still look for the attachments and the backup locations in the original places. So I created /data/jira_3_12/backup and untarred the original attachments to /data/jira_3_12 and then everything worked (including attachements) in the new JIRA. {warning} ## (/) I then used the upgraded JIRA to generate a new XML backup and stored it in /data/original/3.13.5 along with another tar of the files in /data/jira_3_12/attachments. ## (/) I then shutdown the JIRA server. *I should be ready to move on to version 4 upgrade WHEW* ## So, before moving on, I decided that it would be a really good idea to spin up a new Crowd instance to get rid of the :8443 in the URL and to move off of RedHat per IS requests. I have a ticket in for a new VM and a new database to try to get this going. I am waiting on that before moving on. ## (/) Pat created the VM and Neil created the database. ## (/) I logged into auth.mbari.org (name of the VM) and downloaded crowd which I unzipped to the /opt directory ## (/) I then created a /data/crowd directory and gave my account permissions on it and then edited the /opt/atlassian..../crowd-webapp/WEB-INF/classes/crowd-init.properties file to set that as the crowd home directory. ## (/) The instructions say to download the JDBC driver, but they already have JTDS 1.2.7 in the download so I did not do anything. ## (/) You have to manually connect up CrowdID to a database as they setup wizard does not currently do this. ### (/) They say to download the driver, but again 1.2.7 was there so I did nothing. ### (/) I edited the /opt/atlassian.../apache-tomcat/conf/Catalina/localhost/openidserver.xml to look like: {noformat} {noformat} ### (/) I edited the /opt/atlassian.../build.properties files to look like: {noformat} # Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See https://confluence.atlassian.com/display/CROWD/Connecting+Crowd+to+a+Database hibernate.dialect=org.hibernate.dialect.SQLServerDialect # The Hibernate transaction factory to use. See https://confluence.atlassian.com/display/CROWD/Configuring+Crowd hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory # The http port you wish to run crowd from, ie: http://localhost:8095/crowd crowd.tomcat.connector.port=8095 # Tomcat requires a unique port for shutdown crowd.tomcat.shutdown.port=8020 # Crowd context root crowd.url=http://localhost:8095/crowd # Demo context root demo.url=http://localhost:8095/demo # OpenID server context root openidserver.url=http://localhost:8095/openidserver {noformat} ### (/) I then ran the build.sh script in the root of /opt/atlassian... ## (/) I fired up crowd using the /opt/atlassian.../start_crowd.sh script ## (/) I then went to http://auth.mbari.org:8095/crowd to kick off the start up wizard ## (/) I grabbed a new eval license from my account on atlassian and pasted into the license page. ## (/) I selected "New install" on the next page. ## (/) I configured the JDBC connection using this connection URL with user DB_Collaboration {noformat} jdbc:jtds:sqlserver://dione.mbari.org:51001/Crowd;domain=SHORE;useNTLMv2=TRUE {noformat} ## (/) I left the "Options" as they came up {warning:title=Paths} Not sure if this is a problem, but because I started the set up using auth.mbari.org, it set the Base URL to http://auth.mbari.org:8095/crowd instead of localhost. Hope that is not a problem. We will see. {warning} ## (/) I configured the email connection using the settings from [here|https://wind.shore.mbari.org/is/howto/email/mbarimail/imap] and I used my network login (probably shouldn't be doing that ... not sure where it stores my password, but I am assuming in the DB). ## (/) For the local admin account, I created a user named 'crowdadm' so it would not clash with my LDAP account. See Kevin Gomes for password information. ## (/) I checked the OpenID server as an integrated application ## (/) It then took me to the login page and I logged in using the newly minted admin account. Seemed all is well so far. ## (/) I visited the openidserver URL as well and that seemed OK. ## (/) I decided to wait on configuring the MBARI LDAP directory until I got everything with SSL working. ## (/) Now the next step was to follow the directions to configure Crowd to run over SSL found [here|https://confluence.atlassian.com/display/CROWD/Configuring+Crowd+to+Work+with+SSL] ## (/) I shutdown crowd. Note that the stop script does not shutdown things correctly and I noticed the crowd app running as root. That should not be if I started as kgomes. Not sure what is up with that. ## (/) Now Joe had already configured SSL once, so I used his connector configuration in the server.xml file and so the final file looked like: {noformat} {noformat} ## (/) I then edited the /data/crowd/crowd.properties to look like: {noformat} #Sat Aug 01 09:05:15 PDT 2015 session.lastvalidation=session.lastvalidation session.tokenkey=session.tokenkey crowd.server.url=https\://localhost\:8443/crowd/services/ application.name=crowd http.timeout=30000 session.isauthenticated=session.isauthenticated application.login.url=https\://localhost\:8443/crowd/console/ session.validationinterval=0 application.password=Y1Xp3OorCmsOP4eruL1dmH {noformat} One thing to note here is that based on a comment from the SSL configuration page at atlassian (Steve's comment), you are supposed to leave all the host names the same. For example, if the file says localhost, leave it localhost. So this created a bit of a problem based on the fact that I had left the base URL pointing to auth.mbari.org in the wizard steps above. That step wrote auth.mbari.org to the /data/crowd/crowd.properties. All the other files reference localhost, so to be consistent, I changed auth.mbari.org to localhost in the /data/crowd/crowd.properties file. We will see if this works. ## (/) Per the instructions on the atlassian page (referenced above), I also edited the build.properties file and the /client/conf/crowd.properties files before I restarted and used the SSL URLs ## build.properties: {noformat} # Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See https://confluence.atlassian.com/display/CROWD/Connecting+Crowd+to+a+Database hibernate.dialect=org.hibernate.dialect.SQLServerDialect # The Hibernate transaction factory to use. See https://confluence.atlassian.com/display/CROWD/Configuring+Crowd hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory # The http port you wish to run crowd from, ie: http://localhost:8095/crowd crowd.tomcat.connector.port=8095 # Tomcat requires a unique port for shutdown crowd.tomcat.shutdown.port=8020 # Crowd context root crowd.url=https://localhost:8443/crowd # Demo context root demo.url=https://localhost:8443/demo # OpenID server context root openidserver.url=https://localhost:8443/openidserver {noformat} ## crowd.properties (client) {noformat} application.name crowd application.password password application.login.url https://localhost:8443/crowd/console/ crowd.server.url https://localhost:8443/crowd/services/ crowd.base.url https://localhost:8443/crowd/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 2 session.lastvalidation session.lastvalidation {noformat} ## (/) Although not stated, I am assuming you would need to run the build.sh script to push the build.properties changes to their proper places, so I did that. Note that before doing that, I know that it will clobber the server.xml changes I made, so I made a copy of that file and diff'd them after and then rolled the previous changes to the new server.xml file. Actually, amazingly enough, it seems to have done the connector entry correctly so I left it after running the build.sh script. ## (/) Crossed my fingers and then restarted crowd. I tailed the catalina.out file and did not see any stack traces so that is a good sign! ## (/) I visited https://auth.mbari.org:8443/crowd first. It could not find that page, but I suspect that is because I am browsing from the outside, so I tried just https://auth.mbari.org/crowd and got a service unavailable. I am suspecting that this is a combination of firewall and proxy pass and I will send this info to Joe. From what I can see on the crowd side, it seems like the server started cleanly, we just can't get to it. I tried to reach it from a browser on the machine itself too (through VNC) with the same service not available. ## (/) Here are the notes from Joe after he fixed it! Wooohooo! {noformat} Hey Kevin, Thanks for starting clean! I had to make a few adjustments. 1-I modified the server.xml file in /opt/atlassian-crowd-2.8.3/apache-tomcat/conf/server.xml so there are two connectors per the instructions on the Atlassian site. I have backed up this good server.xml file in /etc/temp/ if you want to browse it to see what I did. Of note is that I removed all the jargon referencing the types of ciphers available to simplify things for now. 2-I modified /data/crowd/crowd.properties to have crowd.server.url=https\://localhost\:8443/crowd/services/ application.login.url=https\://localhost\:8443/crowd/console/ But that would cause my login to error with an error saying it was unable to reach the authentication server. I scratched my head for a bit. When I revert the values to just using non-SSL and try to log in, I just get an "invalid login" (I don't know the crowdadm password). So I worked under the assumption that if I can configure SSL to get an "invalid login" when logging in then it would work when provided real credentials. So, I then changed /data/crowd/crowd.proprties to: crowd.server.url=https\://auth.mbari.org\:8443/crowd/services/ application.login.url=https\://auth.mbari.org\:8443/crowd/console/ And now when I try to log in with SSL it says "invalid login". Strange because all the other values I can find only show "localhost" .. in any case... Can you try to log in now? {noformat} ## (/) Next I moved on to configuring the connection to MBARI's LDAP server to enable our logins through Crowd and CrowdID ## (/) I clicked on "Add Directory" in crowd. ## (/) I selected "Connector" then clicked Next ## (/) I put ldap.shore.mbari.org as the name of the server ## (/) I selected "Use memberOf for group memberships" ## (/) I used "OU=AllUsers,DC=shore,DC=mbari,DC=org" for the Base DN ## (/) I used "CN=LDAPbind,OU=Special,OU=AllUsers,DC=shore,DC=mbari,DC=org" for the Username (talk to Pat Allen for password) ## (/) I tested the connection (button click) and it passed. ## (/) I de-selected all the capabilities of the connector as it is a ready only connector and then saved it. It synchronized correctly! ## (/) At first, I could not login using my MBARI credentials, but after going to the "crowd" application in crowd (logged in as the local admin), I had to add the LDAP directory and configure it to "Allow all to authenticate", then I was able to login. After this, the last step was to get this to run as a different user and lock down various directories. I went through the entire directory structure /opt/atlassian... and set up so that root owned all read-only locations and DB_Collaboration (account set up by IS) owned the other stuff. I also gave full ownership to the /data/crowd directory to DB_Collaboration so it could write there. Pat set up a script to start on boot and after a little tweaking, it now starts on boot. {warning:title=CrowdID log file} One thing that came up here was that when the crowdID application ran, it tried to write a log file to the location where the process was launched from (which is /opt/atlassian...). This is a bad thing and I figured out that I could change that location by changing the file /opt/atlassian-crowd-2.8.3/crowd-openidserver-webapp/WEB-INF/classes/log4j.properties and hardcoding the /data/crowd/logs/atlassian-crowd-openid-server.log and then restarted the application. {warning} ## (/) Another note is the when an application tried to use the OpenID application, it would get redirected to localhost. I changed the /opt/atlassian.../crowd-openidserver-webapp/WEB-INF/classes/crowd.properties file to look like: {noformat} #Sat Aug 01 10:03:18 PDT 2015 session.lastvalidation=session.lastvalidation session.tokenkey=session.tokenkey crowd.server.url=http\://localhost\:8095/crowd/services/ application.name=crowd-openid-server #application.login.url.template=http\://localhost\:8095/openidserver?returnToUrl\=${RETURN_TO_URL} application.login.url.template=https\://auth.mbari.org/openidserver?returnToUrl\=${RETURN_TO_URL} session.isauthenticated=session.isauthenticated #application.base.url=http\://localhost\:8095/openidserver application.base.url=https\://auth.mbari.org/openidserver #application.login.url=http\://localhost\:8095/openidserver application.login.url=https\://auth.mbari.org/openidserver session.validationinterval=0 application.password=password {noformat} and that seems to have fixed it. # (/) It is finally time to move on to the version 4 upgrade ... holy crap. I first went to the *new* crowd install (auth.mbari.org) and logged in as the crowdadm. # (/) I clicked on Applications, then on Add Application # (/) I selected JIRA from the Application type drop-down # (/) I entered jira445 as the username. Ask Kevin about the password. # (/) I used http://bugs.shore.mbari.org:8081 as the URL # (/) I used 134.89.12.31 as the IP address. # (/) I selected only the MBARI LDAP directory. # (/) Then I selected "Allow all users to authenticate" # (/) Then I clicked on "Add Application" # (/) I VNC'd into bugs.mbari.org. As it turns out, for Linux, there is an installer program to download. I downloaded the .bin for 64 bit Linux installer and moved it to the jira-upgrade directory. # (/) I chmod'd the file to make it executable and ran it. It gave me a warning about not being root, but I went ahead with it. # (/) It asked for the JIRA home and data directory, which I specified as /opt/jira4 and /data/jira445. # (/) For the ports, I specified 8180 and 8105 (HTTP and control respectively). It then extracted all the files and launched JIRA. It said if finished, so I opened a local browser to http://localhost:8180 which kicked off the start up wizard. # (/) I specified the external database using: ## solstice2.shore.mbari.org (server) ## 1433 (port) ## jira4 (database) ## DB_Collaboration (username) ## (password ask Kevin) ## dbo (schema) # But all this failed as it seems to just want to try and use the SQL server authentication instead of domain. I will have to do it manually. # (/) I stopped the server using the bin/stop-jira.sh script. # (/) I created and edited /data/jira445/dbconfig.xml and made it look like the following: {noformat} ?xml version="1.0" encoding="UTF-8"?> defaultDS default mssql jiraschema jdbc:jtds:sqlserver://solstice2.shore.mbari.org:1433/Jira4;domain=SHORE;useNTLMv2=true net.sourceforge.jtds.jdbc.Driver DB_Collaboration (ask Kevin) 15 {noformat} # (/) I then started it again using bin/start-jira.sh and tailed the catalina.out file. Got a bunch of errors related to the schema 'jiraschema', I edited the file and changed the schema to 'dbo' and restarted. That seemed to do it. There was one stack trace for some iCal plugin, but looks OK other than that. # I browsed back to localhost:8180 and the wizard moved to step 2. There was an option to import existing data bit without the crowd connection, I thought I should set it up manually, connect to crowd, then import. I generated an evaluation license, called the app "MBARI JIRA4" and change the server in the url to bugs.shore.mbari.org # For the admin, I created an account called 'jiraadm' (ask Kevin for password). # Since this is a temporary system, I left the email system disabled. # I logged in as jiraadm, went to Administration, then Users, then clicked on Add Directory and chose Atlassian Crowd. Note that I had to set the server URL to http://auth.mbari.org:8095/crowd or I would have had to configure all this SSL crap that I did not want to do for this temporary install. # It tested successfully, I clicked Save and it went through a 13 second sync, whew! # I then went to System->Import and Export->Restore System # I copied the jira-upgrade-3.13.5.zip file from the previous version export into /data/jira445/import and then entered that file name along with the new evaluation license again. # I worked through progress bar after I clicked on Restore (it took a really long time). # I then stopped, restarted and tailed the log file. # I am thinking now I should have put the attachments in the import attachments directory, but I am hoping I can just copy them to the data/attachments directory. # UG! I got some error during the import. The exception read: "JIRA is unable to migrat the User Directory configuration because external users exist but the osuser.xml file is not available". It then gave me a link to a doc that talked about making the old user files available before the upgrade ... crap. So I needed to copy the osuser.xml and crowd.properties file from atlassian-jira/WEB-INF/classes directory on the old install to the same directory on the new install ... sigh. This means I am going to blow away everything and start over. # I shutdown jira4 # I dropped all things in the database and deleted all content in the /data/jira445 directory (except for the dbconfig.xml file). # I also removed the temp, logs (actually you have to leave the directory, just clear the files) and the work/Catalina/localhost directories from the jira installation. # I then copied the osuser.xml and the crowd.properties files from the 3.13.5 install to the 4 install. # I edited the crowd.properties file in hopes that I could point it to the new crowd install on auth.mbari.org and it would work, but we will see. # I then started jira and tailed the log file. # All looked OK (other than iCal plugin stack trace again), so I went to localhost:8180 and got step 2 of the wizard. I used the same info as before. # I logged in as the local admin account and it looks like the system picked up the crowd connection, but lets see what server it used! Hey it used the one I edited into the file! Sweet ... now let's see if the import works. # I copied the 3.13.5 zip file to the import directory again and this time, I untarred the attachments into the import/attachments directory. # I kicked off the restore as before and it worked through it fine. # Shutdown and restarted system, tailing the log file and then went to localhost:8180 # I can see issues (before logging in) and it all looks good!! The attachments did not move over from the import directory, so I copied the tar file from /data/jira445/import to /data/jira445/data and then untarred it there, then removed the tar file and the import zip file from the import directory. # Now I will try to login using my MBARI account and OMG it actually worked!!! # I then performed an export and copied those file to the /data/backups/4.4.5 directory ]]> 27558190 27590956 4.4: [https://confluence.atlassian.com/display/JIRA044/Migrating+JIRA+to+Another+Server] ## The JIRA configuration tool: [https://confluence.atlassian.com/display/JIRA044/Using+the+JIRA+Configuration+Tool] h5. Steps # (/) Create new VM named bugs.mbari.org in the DMZ # (/) Have Neil create database Jira_Temp on solstice2.shore.mbari.org # (/) Have Neil create database Jira on solstice2.shore.mbari.org # (/) Have Pat install Java 7 on bugs.shore.mbari.org # (/) Have Pete plumb holes through firewall so processes on bugs.mbari.org can get to Solstice2 # (/) Have Pat create DB_Collaboration account on bugs so it can run JIRA under that account and it can connect to solstice2 using that NT Domain account. # (/) Upgrade license on Atlassian site # (/) Log into bugs.shore.mbari.org # (/) Download 3.13.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 4.4.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 5.2.11 standalone Linux 64 bit tar.gz (not sure this version is necessary, but at least I have it) # (/) Unzip and untar the file to /opt # (/) Download latest JIRA (6.4.7 as of this writing). # (/) Unzip and untar it to /opt # Performed Test Upgrade ## (/) In order to export the current stuff in JIRA, I had to shut off access so people could not change the data while I was backing it up. ## (/) I ssh'd to oceana.mbari.org as root and edited the /opt/jira/conf/server.xml file and commented out the Connector section that had the port of 8010 to shut it off from the normal serving route. ## (/) I uncommented the 8082 port connector and the 8443 port connector so that I could still get to the server. ## (/) I stopped and started the JIRA server and in the log file I got a "keystore was tampered with..." which is not surprising. ## (/) I could then browser over to http://oceana.mbari.org:8082/jira ## (/) Then through the Administration console, I did an XML backup ## (/) I then created a tar of all the attachments in the /data/jira_3_12/attachments directory ## (/) I moved both the XML and tar files to the /root/jira-upgrade directory ## (/) I then reversed the changes to the server.xml file and shut down JIRA ## (/) I left it down during the next steps in case it went so well, I could just point people to the new server (yeah, right). ## (/) I then browsed to the crowd server on oceana and add a new application using: ### URL: http://bugs.mbari.org/jira3135 ### IP: 134.89.2.29 ### Name: JIRA3135 ### Password: (ask Kevin) :) ## (/) On bugs, I made a copy of the JIRA 3.13.5 download in the /opt directory and unzipped and untarred it. ## (/) In order to configure the crowd connection I did the following: ### (/) I scp'd the /opt/crowd/client/crowd-integration-client-1.6.jar file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I removed the existing 1.6.1 crowd client jar from the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I scp'd the /opt/crowd/client/conf/crowd.properties file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I scp'd the /opt/crowd/client/conf/crowd-ehcache.xml file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I edited the crowd.properties file on bugs to look like: {noformat} application.name JIRA3135 application.password (ask Kevin) application.login.url http://oceana.mbari.org:8095/crowd/console/ crowd.server.url http://oceana.mbari.org:8095/crowd/services/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 0 session.lastvalidation session.lastvalidation {noformat} ### (/) I edited the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/osuser.xml file to comment out the current authentication mechanism and then uncomment the crowd one. ## (/) I then edited the /opt/atlassian-jira-standalone-3.13.5/conf/server/xml file and configured the database connection to the Jira_Temp database on Solstice2. I looked like this: {noformat} {noformat} ## (/) Edit the /opt/atlassian/jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/entityengine.xml and changed it from 'hsql' to 'mssql' and delete the line with "PUBLIC" in it per the instructions in the comments in that file. ## (/) I edited the /etc/httpd/conf/httpd.conf file and created a proxy pass at the bottom of the file to point a normal URL to the default port 8080 for JIRA: {noformat} # Proxy Pass for JIRA ProxyPass http://bugs.mbari.org:8080 ProxyPassReverse http://bugs.mbari.org:8080 {noformat} ## (/) I restarted Apache ## (/) I scp'd the jtds driver from oceana to the /opt/atlassian-jira-standalone-3.13.5/common/lib directory (you could down from the internet) ## (/) I then went to the /opt/atlassian-jira-standalone-3.13.5/ directory and ran './bin/startup.sh'. From the log file, I could tell things were hanging. After some troubleshooting I am wondering if the local firewall is preventing the application to get access to the database on solstice2. I can telnet to port 1433, but I can't browse to the base http://bugs.mbari.org from anywhere but the local web browser. I have submitted a ticket. ## (/) I restarted the old JIRA with my hopes dashed :(. ## (/) Pat disabled the firewall on bugs.mbari.org but it still hung trying to connect to solstice2.shore.mbari.org. That is really, really perplexing. Neil mentioned that solstice2 is using Kerberos and solstice is not. Checking with the JTDS docs, version 1.3.1 of the driver added kerberos support, so I downloaded that driver and added the 'userKerberos=true' property to the URL in the server.xml file and restarted. Got an error about no credentials, so added user and password properties to the URL. Nope, no luck. Never did figure this one out, but I had Pat pull the VM inside the firewall and after some thrash it worked. Well, it sort of worked ... sigh. It turns out I had downloaded the standard version instead of the enterprise version. I need to redo this work ... grrr. ## (/) I deleted all the tables in the Jira_Temp database and removed the /data/jira3135/indexes directory (and recreated). ## (/) I downloaded the enterprise version of the 3.13.5 server. I made a copy in the /opt directory and unzipped and untarred the file. ## (/) I went back to crowd and edited the application to change the properties to: ### URL: http://bugs.shore.mbari.org:8080 ### IP: 134.89.12.31 ### Name: jira3135 ### Password: (ask Kevin) :) ## (/) I then repeated the steps above to get the server up and running with the following differences: ### The server name is now bugs.shore.mbari.org ### The paths given above are a little different in that they no longer say "standard" but say "enterprise" ### I deleted the proxy pass as it seemed to have issues before and this is only temporary anyway. ## (/) I then browsed to http://bugs.shore.mbari.org:8080 ## (/) It took me to the start up page and at the top was the option to 'import your existing data'. Seemed too good not to try. I clicked on the link. It asked me for the backup file location and the location where the indexes would be stored. ## (/) I copied the XML zip file and the attachments tar file to the /data/original directory. ## (/) I created the /data/jira3135/indexes and used those directories ... it fired off the import and I waited. ## (/) I tailed the log file to watch the import. Holy crap, it worked!!! I could log in and everything! I copied the results from the log file here for posterity sake: {noformat} 2015-07-22 20:55:45,156 http-8080-Processor22 INFO [jira.action.admin.DataImport] Running data import 2015-07-22 20:55:45,179 http-8080-Processor22 INFO [jira.action.admin.DataImport] Importing data.. 2015-07-22 20:55:45,186 http-8080-Processor22 INFO [jira.action.admin.DataImport] Start parsing XML with SAX Parser 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] XML successfully parsed 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] Removing all entries from the database. 2015-07-22 20:56:24,593 http-8080-Processor22 INFO [jira.action.admin.DataImport] All entries removed. 2015-07-22 20:56:24,594 http-8080-Processor22 INFO [jira.action.admin.DataImport] Started storing 410414 Generic Values 2015-07-22 21:01:51,967 http-8080-Processor22 INFO [jira.action.admin.DataImport] Finished storing Generic Values 2015-07-22 21:01:52,329 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:52,361 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:54,683 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLink' to module 'jira.user.format:profile-link-user-format'. 2015-07-22 21:01:54,724 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullName' to module 'jira.user.format:full-name-user-format'. 2015-07-22 21:01:54,773 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkSearcher' to module 'jira.user.format:profile-link-searcher-user-format'. 2015-07-22 21:01:54,784 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkExternal' to module 'jira.user.format:profile-link-external-user-format'. 2015-07-22 21:01:54,795 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkActionHeader' to module 'jira.user.format:profile-link-action-header-user-format'. 2015-07-22 21:01:54,807 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullProfile' to module 'jira.user.format:full-profile-user-format'. 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/comments 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/issues 2015-07-22 21:01:55,641 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/plugins 2015-07-22 21:01:55,867 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:01:55,871 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/issues does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:55,873 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/comments does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,033 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,257 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,889 http-8080-Processor22 ERROR [atlassian.jira.upgrade.ConsistencyCheckImpl] Attachments are turned on, but attachment path [/data/jira_3_12/attachments] invalid - disabling attachments 2015-07-22 21:02:13,904 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Detected that an upgrade is needed; existing data at build 299 2015-07-22 21:02:13,907 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Doing Upgrade... 2015-07-22 21:02:13,915 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value' succeeded 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 317 2015-07-22 21:02:13,944 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite filters - make each filter a favourite of its owner. 2015-07-22 21:02:17,822 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build319] Could not find author 'fpy' for filter with id '10040' 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite filters - make each filter a favourite of its owner.' succeeded 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 319 2015-07-22 21:02:17,995 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise Share Permissions. Move old shares to new shares. 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise Share Permissions. Move old shares to new shares.' succeeded 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 321 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Migrating the old JIRA UI colors to the new JIRA 3.13 colors 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build322] Custom color detected for jira.lf.menu.bgcolour : #336699 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Migrating the old JIRA UI colors to the new JIRA 3.13 colors' succeeded 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 322 2015-07-22 21:02:18,025 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite dashboards - make each dashboard a favourite of its owner. 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'cmcgann' for dashboard with id '10030' 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'fpy' for dashboard with id '10060' 2015-07-22 21:02:18,423 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'kanna' for dashboard with id '10040' 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite dashboards - make each dashboard a favourite of its owner.' succeeded 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 325 2015-07-22 21:02:18,625 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Reindexing all data in JIRA to include Favourites. 2015-07-22 21:02:18,648 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All starting... 2015-07-22 21:02:18,650 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 0% complete. Current index: Issue 2015-07-22 21:02:18,654 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:02:18,809 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 1% complete. Current index: Issue 2015-07-22 21:02:18,855 indexerPool-2-thread-10 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 2% complete. Current index: Issue 2015-07-22 21:02:18,899 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 3% complete. Current index: Issue 2015-07-22 21:02:18,945 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 4% complete. Current index: Issue 2015-07-22 21:02:19,012 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 5% complete. Current index: Issue . . . 2015-07-22 21:02:26,164 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 95% complete. Current index: Issue 2015-07-22 21:02:26,232 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 96% complete. Current index: Issue 2015-07-22 21:02:26,316 indexerPool-2-thread-9 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 97% complete. Current index: Issue 2015-07-22 21:02:26,771 indexerPool-2-thread-3 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: Issue 2015-07-22 21:02:27,261 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 8607ms. Indexer: DefaultIndexManager: paths: [/data/jira3135/indexes/issues, /data/jira3135/indexes/comments] 2015-07-22 21:02:27,263 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: SearchRequest 2015-07-22 21:02:27,268 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,293 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: SearchRequest 2015-07-22 21:02:27,308 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: PortalPage 2015-07-22 21:02:27,312 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,377 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: PortalPage 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 115ms. Indexer: SharedEntityIndexManager: paths: [/data/jira3135/indexes/entities/portalpage, /data/jira3135/indexes/entities/searchrequest] 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All complete. Total time: 8722ms. 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Reindexing all data in JIRA to include Favourites.' succeeded 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 326 2015-07-22 21:02:27,397 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade succeeded! Setting data build number to 360 2015-07-22 21:02:27,469 JiraQuartzScheduler_Worker-0 WARN [service.services.export.ExportService] Backup directory /data/jira_3_12/backup does not exist {noformat} {warning:title=Paths} It appears that the upgraded JIRA will still look for the attachments and the backup locations in the original places. So I created /data/jira_3_12/backup and untarred the original attachments to /data/jira_3_12 and then everything worked (including attachements) in the new JIRA. {warning} ## (/) I then used the upgraded JIRA to generate a new XML backup and stored it in /data/original/3.13.5 along with another tar of the files in /data/jira_3_12/attachments. ## (/) I then shutdown the JIRA server. *I should be ready to move on to version 4 upgrade WHEW* ## So, before moving on, I decided that it would be a really good idea to spin up a new Crowd instance to get rid of the :8443 in the URL and to move off of RedHat per IS requests. I have a ticket in for a new VM and a new database to try to get this going. I am waiting on that before moving on. ## (/) Pat created the VM and Neil created the database. ## (/) I logged into auth.mbari.org (name of the VM) and downloaded crowd which I unzipped to the /opt directory ## (/) I then created a /data/crowd directory and gave my account permissions on it and then edited the /opt/atlassian..../crowd-webapp/WEB-INF/classes/crowd-init.properties file to set that as the crowd home directory. ## (/) The instructions say to download the JDBC driver, but they already have JTDS 1.2.7 in the download so I did not do anything. ## (/) You have to manually connect up CrowdID to a database as they setup wizard does not currently do this. ### (/) They say to download the driver, but again 1.2.7 was there so I did nothing. ### (/) I edited the /opt/atlassian.../apache-tomcat/conf/Catalina/localhost/openidserver.xml to look like: {noformat} {noformat} ### (/) I edited the /opt/atlassian.../build.properties files to look like: {noformat} # Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See https://confluence.atlassian.com/display/CROWD/Connecting+Crowd+to+a+Database hibernate.dialect=org.hibernate.dialect.SQLServerDialect # The Hibernate transaction factory to use. See https://confluence.atlassian.com/display/CROWD/Configuring+Crowd hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory # The http port you wish to run crowd from, ie: http://localhost:8095/crowd crowd.tomcat.connector.port=8095 # Tomcat requires a unique port for shutdown crowd.tomcat.shutdown.port=8020 # Crowd context root crowd.url=http://localhost:8095/crowd # Demo context root demo.url=http://localhost:8095/demo # OpenID server context root openidserver.url=http://localhost:8095/openidserver {noformat} ### (/) I then ran the build.sh script in the root of /opt/atlassian... ## (/) I fired up crowd using the /opt/atlassian.../start_crowd.sh script ## (/) I then went to http://auth.mbari.org:8095/crowd to kick off the start up wizard ## (/) I grabbed a new eval license from my account on atlassian and pasted into the license page. ## (/) I selected "New install" on the next page. ## (/) I configured the JDBC connection using this connection URL with user DB_Collaboration {noformat} jdbc:jtds:sqlserver://dione.mbari.org:51001/Crowd;domain=SHORE;useNTLMv2=TRUE {noformat} ## (/) I left the "Options" as they came up {warning:title=Paths} Not sure if this is a problem, but because I started the set up using auth.mbari.org, it set the Base URL to http://auth.mbari.org:8095/crowd instead of localhost. Hope that is not a problem. We will see. {warning} ## (/) I configured the email connection using the settings from [here|https://wind.shore.mbari.org/is/howto/email/mbarimail/imap] and I used my network login (probably shouldn't be doing that ... not sure where it stores my password, but I am assuming in the DB). ## (/) For the local admin account, I created a user named 'crowdadm' so it would not clash with my LDAP account. See Kevin Gomes for password information. ## (/) I checked the OpenID server as an integrated application ## (/) It then took me to the login page and I logged in using the newly minted admin account. Seemed all is well so far. ## (/) I visited the openidserver URL as well and that seemed OK. ## (/) I decided to wait on configuring the MBARI LDAP directory until I got everything with SSL working. ## (/) Now the next step was to follow the directions to configure Crowd to run over SSL found [here|https://confluence.atlassian.com/display/CROWD/Configuring+Crowd+to+Work+with+SSL] ## (/) I shutdown crowd. Note that the stop script does not shutdown things correctly and I noticed the crowd app running as root. That should not be if I started as kgomes. Not sure what is up with that. ## (/) Now Joe had already configured SSL once, so I used his connector configuration in the server.xml file and so the final file looked like: {noformat} {noformat} ## (/) I then edited the /data/crowd/crowd.properties to look like: {noformat} #Sat Aug 01 09:05:15 PDT 2015 session.lastvalidation=session.lastvalidation session.tokenkey=session.tokenkey crowd.server.url=https\://localhost\:8443/crowd/services/ application.name=crowd http.timeout=30000 session.isauthenticated=session.isauthenticated application.login.url=https\://localhost\:8443/crowd/console/ session.validationinterval=0 application.password=Y1Xp3OorCmsOP4eruL1dmH {noformat} One thing to note here is that based on a comment from the SSL configuration page at atlassian (Steve's comment), you are supposed to leave all the host names the same. For example, if the file says localhost, leave it localhost. So this created a bit of a problem based on the fact that I had left the base URL pointing to auth.mbari.org in the wizard steps above. That step wrote auth.mbari.org to the /data/crowd/crowd.properties. All the other files reference localhost, so to be consistent, I changed auth.mbari.org to localhost in the /data/crowd/crowd.properties file. We will see if this works. ## (/) Per the instructions on the atlassian page (referenced above), I also edited the build.properties file and the /client/conf/crowd.properties files before I restarted and used the SSL URLs ## build.properties: {noformat} # Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See https://confluence.atlassian.com/display/CROWD/Connecting+Crowd+to+a+Database hibernate.dialect=org.hibernate.dialect.SQLServerDialect # The Hibernate transaction factory to use. See https://confluence.atlassian.com/display/CROWD/Configuring+Crowd hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory # The http port you wish to run crowd from, ie: http://localhost:8095/crowd crowd.tomcat.connector.port=8095 # Tomcat requires a unique port for shutdown crowd.tomcat.shutdown.port=8020 # Crowd context root crowd.url=https://localhost:8443/crowd # Demo context root demo.url=https://localhost:8443/demo # OpenID server context root openidserver.url=https://localhost:8443/openidserver {noformat} ## crowd.properties (client) {noformat} application.name crowd application.password password application.login.url https://localhost:8443/crowd/console/ crowd.server.url https://localhost:8443/crowd/services/ crowd.base.url https://localhost:8443/crowd/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 2 session.lastvalidation session.lastvalidation {noformat} ## (/) Although not stated, I am assuming you would need to run the build.sh script to push the build.properties changes to their proper places, so I did that. Note that before doing that, I know that it will clobber the server.xml changes I made, so I made a copy of that file and diff'd them after and then rolled the previous changes to the new server.xml file. Actually, amazingly enough, it seems to have done the connector entry correctly so I left it after running the build.sh script. ## (/) Crossed my fingers and then restarted crowd. I tailed the catalina.out file and did not see any stack traces so that is a good sign! ## (/) I visited https://auth.mbari.org:8443/crowd first. It could not find that page, but I suspect that is because I am browsing from the outside, so I tried just https://auth.mbari.org/crowd and got a service unavailable. I am suspecting that this is a combination of firewall and proxy pass and I will send this info to Joe. From what I can see on the crowd side, it seems like the server started cleanly, we just can't get to it. I tried to reach it from a browser on the machine itself too (through VNC) with the same service not available. ## (/) Here are the notes from Joe after he fixed it! Wooohooo! {noformat} Hey Kevin, Thanks for starting clean! I had to make a few adjustments. 1-I modified the server.xml file in /opt/atlassian-crowd-2.8.3/apache-tomcat/conf/server.xml so there are two connectors per the instructions on the Atlassian site. I have backed up this good server.xml file in /etc/temp/ if you want to browse it to see what I did. Of note is that I removed all the jargon referencing the types of ciphers available to simplify things for now. 2-I modified /data/crowd/crowd.properties to have crowd.server.url=https\://localhost\:8443/crowd/services/ application.login.url=https\://localhost\:8443/crowd/console/ But that would cause my login to error with an error saying it was unable to reach the authentication server. I scratched my head for a bit. When I revert the values to just using non-SSL and try to log in, I just get an "invalid login" (I don't know the crowdadm password). So I worked under the assumption that if I can configure SSL to get an "invalid login" when logging in then it would work when provided real credentials. So, I then changed /data/crowd/crowd.proprties to: crowd.server.url=https\://auth.mbari.org\:8443/crowd/services/ application.login.url=https\://auth.mbari.org\:8443/crowd/console/ And now when I try to log in with SSL it says "invalid login". Strange because all the other values I can find only show "localhost" .. in any case... Can you try to log in now? {noformat} ## (/) Next I moved on to configuring the connection to MBARI's LDAP server to enable our logins through Crowd and CrowdID ## (/) I clicked on "Add Directory" in crowd. ## (/) I selected "Connector" then clicked Next ## (/) I put ldap.shore.mbari.org as the name of the server ## (/) I selected "Use memberOf for group memberships" ## (/) I used "OU=AllUsers,DC=shore,DC=mbari,DC=org" for the Base DN ## (/) I used "CN=LDAPbind,OU=Special,OU=AllUsers,DC=shore,DC=mbari,DC=org" for the Username (talk to Pat Allen for password) ## (/) I tested the connection (button click) and it passed. ## (/) I de-selected all the capabilities of the connector as it is a ready only connector and then saved it. It synchronized correctly! ## (/) At first, I could not login using my MBARI credentials, but after going to the "crowd" application in crowd (logged in as the local admin), I had to add the LDAP directory and configure it to "Allow all to authenticate", then I was able to login. After this, the last step was to get this to run as a different user and lock down various directories. I went through the entire directory structure /opt/atlassian... and set up so that root owned all read-only locations and DB_Collaboration (account set up by IS) owned the other stuff. I also gave full ownership to the /data/crowd directory to DB_Collaboration so it could write there. Pat set up a script to start on boot and after a little tweaking, it now starts on boot. {warning:title=CrowdID log file} One thing that came up here was that when the crowdID application ran, it tried to write a log file to the location where the process was launched from (which is /opt/atlassian...). This is a bad thing and I figured out that I could change that location by changing the file /opt/atlassian-crowd-2.8.3/crowd-openidserver-webapp/WEB-INF/classes/log4j.properties and hardcoding the /data/crowd/logs/atlassian-crowd-openid-server.log and then restarted the application. {warning} ## (/) Another note is the when an application tried to use the OpenID application, it would get redirected to localhost. I changed the /opt/atlassian.../crowd-openidserver-webapp/WEB-INF/classes/crowd.properties file to look like: {noformat} #Sat Aug 01 10:03:18 PDT 2015 session.lastvalidation=session.lastvalidation session.tokenkey=session.tokenkey crowd.server.url=http\://localhost\:8095/crowd/services/ application.name=crowd-openid-server #application.login.url.template=http\://localhost\:8095/openidserver?returnToUrl\=${RETURN_TO_URL} application.login.url.template=https\://auth.mbari.org/openidserver?returnToUrl\=${RETURN_TO_URL} session.isauthenticated=session.isauthenticated #application.base.url=http\://localhost\:8095/openidserver application.base.url=https\://auth.mbari.org/openidserver #application.login.url=http\://localhost\:8095/openidserver application.login.url=https\://auth.mbari.org/openidserver session.validationinterval=0 application.password=password {noformat} and that seems to have fixed it. # (/) It is finally time to move on to the version 4 upgrade ... holy crap. I first went to the *new* crowd install (auth.mbari.org) and logged in as the crowdadm. # (/) I clicked on Applications, then on Add Application # (/) I selected JIRA from the Application type drop-down # (/) I entered jira445 as the username. Ask Kevin about the password. # (/) I used http://bugs.shore.mbari.org:8081 as the URL # (/) I used 134.89.12.31 as the IP address. # (/) I selected only the MBARI LDAP directory. # (/) Then I selected "Allow all users to authenticate" # (/) Then I clicked on "Add Application" # (/) I VNC'd into bugs.mbari.org. As it turns out, for Linux, there is an installer program to download. I downloaded the .bin for 64 bit Linux installer and moved it to the jira-upgrade directory. # (/) I chmod'd the file to make it executable and ran it. It gave me a warning about not being root, but I went ahead with it. # (/) It asked for the JIRA home and data directory, which I specified as /opt/jira4 and /data/jira445. # (/) For the ports, I specified 8180 and 8105 (HTTP and control respectively). It then extracted all the files and launched JIRA. It said if finished, so I opened a local browser to http://localhost:8180 which kicked off the start up wizard. # (/) I specified the external database using: ## solstice2.shore.mbari.org (server) ## 1433 (port) ## jira4 (database) ## DB_Collaboration (username) ## (password ask Kevin) ## dbo (schema) # But all this failed as it seems to just want to try and use the SQL server authentication instead of domain. I will have to do it manually. # (/) I stopped the server using the bin/stop-jira.sh script. # (/) I created and edited /data/jira445/dbconfig.xml and made it look like the following: {noformat} ?xml version="1.0" encoding="UTF-8"?> defaultDS default mssql jiraschema jdbc:jtds:sqlserver://solstice2.shore.mbari.org:1433/Jira4;domain=SHORE;useNTLMv2=true net.sourceforge.jtds.jdbc.Driver DB_Collaboration (ask Kevin) 15 {noformat} # (/) I then started it again using bin/start-jira.sh and tailed the catalina.out file. Got a bunch of errors related to the schema 'jiraschema', I edited the file and changed the schema to 'dbo' and restarted. That seemed to do it. There was one stack trace for some iCal plugin, but looks OK other than that. # I browsed back to localhost:8180 and the wizard moved to step 2. There was an option to import existing data bit without the crowd connection, I thought I should set it up manually, connect to crowd, then import. I generated an evaluation license, called the app "MBARI JIRA4" and change the server in the url to bugs.shore.mbari.org # For the admin, I created an account called 'jiraadm' (ask Kevin for password). # Since this is a temporary system, I left the email system disabled. # I logged in as jiraadm, went to Administration, then Users, then clicked on Add Directory and chose Atlassian Crowd. Note that I had to set the server URL to http://auth.mbari.org:8095/crowd or I would have had to configure all this SSL crap that I did not want to do for this temporary install. # It tested successfully, I clicked Save and it went through a 13 second sync, whew! # I then went to System->Import and Export->Restore System # I copied the jira-upgrade-3.13.5.zip file from the previous version export into /data/jira445/import and then entered that file name along with the new evaluation license again. # I worked through progress bar after I clicked on Restore (it took a really long time). # I then stopped, restarted and tailed the log file. # I am thinking now I should have put the attachments in the import attachments directory, but I am hoping I can just copy them to the data/attachments directory. # UG! I got some error during the import. The exception read: "JIRA is unable to migrat the User Directory configuration because external users exist but the osuser.xml file is not available". It then gave me a link to a doc that talked about making the old user files available before the upgrade ... crap. So I needed to copy the osuser.xml and crowd.properties file from atlassian-jira/WEB-INF/classes directory on the old install to the same directory on the new install ... sigh. This means I am going to blow away everything and start over. # I shutdown jira4 # I dropped all things in the database and deleted all content in the /data/jira445 directory (except for the dbconfig.xml file). # I also removed the temp, logs (actually you have to leave the directory, just clear the files) and the work/Catalina/localhost directories from the jira installation. # I then copied the osuser.xml and the crowd.properties files from the 3.13.5 install to the 4 install. # I edited the crowd.properties file in hopes that I could point it to the new crowd install on auth.mbari.org and it would work, but we will see. # I then started jira and tailed the log file. # All looked OK (other than iCal plugin stack trace again), so I went to localhost:8180 and got step 2 of the wizard. I used the same info as before. # I logged in as the local admin account and it looks like the system picked up the crowd connection, but lets see what server it used! Hey it used the one I edited into the file! Sweet ... now let's see if the import works. # I copied the 3.13.5 zip file to the import directory again and this time, I untarred the attachments into the import/attachments directory. # I kicked off the restore as before and it worked through it fine. # Shutdown and restarted system, tailing the log file and then went to localhost:8180 # I can see issues (before logging in) and it all looks good!! The attachments did not move over from the import directory, so I copied the tar file from /data/jira445/import to /data/jira445/data and then untarred it there, then removed the tar file and the import zip file from the import directory. # Now I will try to login using my MBARI account and OMG it actually worked!!! (it even gave my kgomes account Admin privs) # I then performed an export and copied those file to the /data/backups/4.4.5 directory (also created a TAR of the attachments and put there too). # Now on to version 5! ]]> 27558192 27590958 4.4: [https://confluence.atlassian.com/display/JIRA044/Migrating+JIRA+to+Another+Server] ## The JIRA configuration tool: [https://confluence.atlassian.com/display/JIRA044/Using+the+JIRA+Configuration+Tool] h5. Steps # (/) Create new VM named bugs.mbari.org in the DMZ # (/) Have Neil create database Jira_Temp on solstice2.shore.mbari.org # (/) Have Neil create database Jira on solstice2.shore.mbari.org # (/) Have Pat install Java 7 on bugs.shore.mbari.org # (/) Have Pete plumb holes through firewall so processes on bugs.mbari.org can get to Solstice2 # (/) Have Pat create DB_Collaboration account on bugs so it can run JIRA under that account and it can connect to solstice2 using that NT Domain account. # (/) Upgrade license on Atlassian site # (/) Log into bugs.shore.mbari.org # (/) Download 3.13.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 4.4.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 5.2.11 standalone Linux 64 bit tar.gz (not sure this version is necessary, but at least I have it) # (/) Unzip and untar the file to /opt # (/) Download latest JIRA (6.4.7 as of this writing). # (/) Unzip and untar it to /opt # Performed Test Upgrade ## (/) In order to export the current stuff in JIRA, I had to shut off access so people could not change the data while I was backing it up. ## (/) I ssh'd to oceana.mbari.org as root and edited the /opt/jira/conf/server.xml file and commented out the Connector section that had the port of 8010 to shut it off from the normal serving route. ## (/) I uncommented the 8082 port connector and the 8443 port connector so that I could still get to the server. ## (/) I stopped and started the JIRA server and in the log file I got a "keystore was tampered with..." which is not surprising. ## (/) I could then browser over to http://oceana.mbari.org:8082/jira ## (/) Then through the Administration console, I did an XML backup ## (/) I then created a tar of all the attachments in the /data/jira_3_12/attachments directory ## (/) I moved both the XML and tar files to the /root/jira-upgrade directory ## (/) I then reversed the changes to the server.xml file and shut down JIRA ## (/) I left it down during the next steps in case it went so well, I could just point people to the new server (yeah, right). ## (/) I then browsed to the crowd server on oceana and add a new application using: ### URL: http://bugs.mbari.org/jira3135 ### IP: 134.89.2.29 ### Name: JIRA3135 ### Password: (ask Kevin) :) ## (/) On bugs, I made a copy of the JIRA 3.13.5 download in the /opt directory and unzipped and untarred it. ## (/) In order to configure the crowd connection I did the following: ### (/) I scp'd the /opt/crowd/client/crowd-integration-client-1.6.jar file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I removed the existing 1.6.1 crowd client jar from the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I scp'd the /opt/crowd/client/conf/crowd.properties file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I scp'd the /opt/crowd/client/conf/crowd-ehcache.xml file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I edited the crowd.properties file on bugs to look like: {noformat} application.name JIRA3135 application.password (ask Kevin) application.login.url http://oceana.mbari.org:8095/crowd/console/ crowd.server.url http://oceana.mbari.org:8095/crowd/services/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 0 session.lastvalidation session.lastvalidation {noformat} ### (/) I edited the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/osuser.xml file to comment out the current authentication mechanism and then uncomment the crowd one. ## (/) I then edited the /opt/atlassian-jira-standalone-3.13.5/conf/server/xml file and configured the database connection to the Jira_Temp database on Solstice2. I looked like this: {noformat} {noformat} ## (/) Edit the /opt/atlassian/jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/entityengine.xml and changed it from 'hsql' to 'mssql' and delete the line with "PUBLIC" in it per the instructions in the comments in that file. ## (/) I edited the /etc/httpd/conf/httpd.conf file and created a proxy pass at the bottom of the file to point a normal URL to the default port 8080 for JIRA: {noformat} # Proxy Pass for JIRA ProxyPass http://bugs.mbari.org:8080 ProxyPassReverse http://bugs.mbari.org:8080 {noformat} ## (/) I restarted Apache ## (/) I scp'd the jtds driver from oceana to the /opt/atlassian-jira-standalone-3.13.5/common/lib directory (you could down from the internet) ## (/) I then went to the /opt/atlassian-jira-standalone-3.13.5/ directory and ran './bin/startup.sh'. From the log file, I could tell things were hanging. After some troubleshooting I am wondering if the local firewall is preventing the application to get access to the database on solstice2. I can telnet to port 1433, but I can't browse to the base http://bugs.mbari.org from anywhere but the local web browser. I have submitted a ticket. ## (/) I restarted the old JIRA with my hopes dashed :(. ## (/) Pat disabled the firewall on bugs.mbari.org but it still hung trying to connect to solstice2.shore.mbari.org. That is really, really perplexing. Neil mentioned that solstice2 is using Kerberos and solstice is not. Checking with the JTDS docs, version 1.3.1 of the driver added kerberos support, so I downloaded that driver and added the 'userKerberos=true' property to the URL in the server.xml file and restarted. Got an error about no credentials, so added user and password properties to the URL. Nope, no luck. Never did figure this one out, but I had Pat pull the VM inside the firewall and after some thrash it worked. Well, it sort of worked ... sigh. It turns out I had downloaded the standard version instead of the enterprise version. I need to redo this work ... grrr. ## (/) I deleted all the tables in the Jira_Temp database and removed the /data/jira3135/indexes directory (and recreated). ## (/) I downloaded the enterprise version of the 3.13.5 server. I made a copy in the /opt directory and unzipped and untarred the file. ## (/) I went back to crowd and edited the application to change the properties to: ### URL: http://bugs.shore.mbari.org:8080 ### IP: 134.89.12.31 ### Name: jira3135 ### Password: (ask Kevin) :) ## (/) I then repeated the steps above to get the server up and running with the following differences: ### The server name is now bugs.shore.mbari.org ### The paths given above are a little different in that they no longer say "standard" but say "enterprise" ### I deleted the proxy pass as it seemed to have issues before and this is only temporary anyway. ## (/) I then browsed to http://bugs.shore.mbari.org:8080 ## (/) It took me to the start up page and at the top was the option to 'import your existing data'. Seemed too good not to try. I clicked on the link. It asked me for the backup file location and the location where the indexes would be stored. ## (/) I copied the XML zip file and the attachments tar file to the /data/original directory. ## (/) I created the /data/jira3135/indexes and used those directories ... it fired off the import and I waited. ## (/) I tailed the log file to watch the import. Holy crap, it worked!!! I could log in and everything! I copied the results from the log file here for posterity sake: {noformat} 2015-07-22 20:55:45,156 http-8080-Processor22 INFO [jira.action.admin.DataImport] Running data import 2015-07-22 20:55:45,179 http-8080-Processor22 INFO [jira.action.admin.DataImport] Importing data.. 2015-07-22 20:55:45,186 http-8080-Processor22 INFO [jira.action.admin.DataImport] Start parsing XML with SAX Parser 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] XML successfully parsed 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] Removing all entries from the database. 2015-07-22 20:56:24,593 http-8080-Processor22 INFO [jira.action.admin.DataImport] All entries removed. 2015-07-22 20:56:24,594 http-8080-Processor22 INFO [jira.action.admin.DataImport] Started storing 410414 Generic Values 2015-07-22 21:01:51,967 http-8080-Processor22 INFO [jira.action.admin.DataImport] Finished storing Generic Values 2015-07-22 21:01:52,329 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:52,361 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:54,683 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLink' to module 'jira.user.format:profile-link-user-format'. 2015-07-22 21:01:54,724 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullName' to module 'jira.user.format:full-name-user-format'. 2015-07-22 21:01:54,773 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkSearcher' to module 'jira.user.format:profile-link-searcher-user-format'. 2015-07-22 21:01:54,784 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkExternal' to module 'jira.user.format:profile-link-external-user-format'. 2015-07-22 21:01:54,795 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkActionHeader' to module 'jira.user.format:profile-link-action-header-user-format'. 2015-07-22 21:01:54,807 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullProfile' to module 'jira.user.format:full-profile-user-format'. 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/comments 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/issues 2015-07-22 21:01:55,641 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/plugins 2015-07-22 21:01:55,867 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:01:55,871 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/issues does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:55,873 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/comments does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,033 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,257 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,889 http-8080-Processor22 ERROR [atlassian.jira.upgrade.ConsistencyCheckImpl] Attachments are turned on, but attachment path [/data/jira_3_12/attachments] invalid - disabling attachments 2015-07-22 21:02:13,904 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Detected that an upgrade is needed; existing data at build 299 2015-07-22 21:02:13,907 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Doing Upgrade... 2015-07-22 21:02:13,915 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value' succeeded 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 317 2015-07-22 21:02:13,944 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite filters - make each filter a favourite of its owner. 2015-07-22 21:02:17,822 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build319] Could not find author 'fpy' for filter with id '10040' 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite filters - make each filter a favourite of its owner.' succeeded 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 319 2015-07-22 21:02:17,995 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise Share Permissions. Move old shares to new shares. 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise Share Permissions. Move old shares to new shares.' succeeded 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 321 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Migrating the old JIRA UI colors to the new JIRA 3.13 colors 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build322] Custom color detected for jira.lf.menu.bgcolour : #336699 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Migrating the old JIRA UI colors to the new JIRA 3.13 colors' succeeded 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 322 2015-07-22 21:02:18,025 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite dashboards - make each dashboard a favourite of its owner. 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'cmcgann' for dashboard with id '10030' 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'fpy' for dashboard with id '10060' 2015-07-22 21:02:18,423 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'kanna' for dashboard with id '10040' 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite dashboards - make each dashboard a favourite of its owner.' succeeded 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 325 2015-07-22 21:02:18,625 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Reindexing all data in JIRA to include Favourites. 2015-07-22 21:02:18,648 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All starting... 2015-07-22 21:02:18,650 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 0% complete. Current index: Issue 2015-07-22 21:02:18,654 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:02:18,809 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 1% complete. Current index: Issue 2015-07-22 21:02:18,855 indexerPool-2-thread-10 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 2% complete. Current index: Issue 2015-07-22 21:02:18,899 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 3% complete. Current index: Issue 2015-07-22 21:02:18,945 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 4% complete. Current index: Issue 2015-07-22 21:02:19,012 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 5% complete. Current index: Issue . . . 2015-07-22 21:02:26,164 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 95% complete. Current index: Issue 2015-07-22 21:02:26,232 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 96% complete. Current index: Issue 2015-07-22 21:02:26,316 indexerPool-2-thread-9 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 97% complete. Current index: Issue 2015-07-22 21:02:26,771 indexerPool-2-thread-3 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: Issue 2015-07-22 21:02:27,261 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 8607ms. Indexer: DefaultIndexManager: paths: [/data/jira3135/indexes/issues, /data/jira3135/indexes/comments] 2015-07-22 21:02:27,263 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: SearchRequest 2015-07-22 21:02:27,268 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,293 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: SearchRequest 2015-07-22 21:02:27,308 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: PortalPage 2015-07-22 21:02:27,312 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,377 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: PortalPage 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 115ms. Indexer: SharedEntityIndexManager: paths: [/data/jira3135/indexes/entities/portalpage, /data/jira3135/indexes/entities/searchrequest] 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All complete. Total time: 8722ms. 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Reindexing all data in JIRA to include Favourites.' succeeded 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 326 2015-07-22 21:02:27,397 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade succeeded! Setting data build number to 360 2015-07-22 21:02:27,469 JiraQuartzScheduler_Worker-0 WARN [service.services.export.ExportService] Backup directory /data/jira_3_12/backup does not exist {noformat} {warning:title=Paths} It appears that the upgraded JIRA will still look for the attachments and the backup locations in the original places. So I created /data/jira_3_12/backup and untarred the original attachments to /data/jira_3_12 and then everything worked (including attachements) in the new JIRA. {warning} ## (/) I then used the upgraded JIRA to generate a new XML backup and stored it in /data/original/3.13.5 along with another tar of the files in /data/jira_3_12/attachments. ## (/) I then shutdown the JIRA server. *I should be ready to move on to version 4 upgrade WHEW* ## So, before moving on, I decided that it would be a really good idea to spin up a new Crowd instance to get rid of the :8443 in the URL and to move off of RedHat per IS requests. I have a ticket in for a new VM and a new database to try to get this going. I am waiting on that before moving on. ## (/) Pat created the VM and Neil created the database. ## (/) I logged into auth.mbari.org (name of the VM) and downloaded crowd which I unzipped to the /opt directory ## (/) I then created a /data/crowd directory and gave my account permissions on it and then edited the /opt/atlassian..../crowd-webapp/WEB-INF/classes/crowd-init.properties file to set that as the crowd home directory. ## (/) The instructions say to download the JDBC driver, but they already have JTDS 1.2.7 in the download so I did not do anything. ## (/) You have to manually connect up CrowdID to a database as they setup wizard does not currently do this. ### (/) They say to download the driver, but again 1.2.7 was there so I did nothing. ### (/) I edited the /opt/atlassian.../apache-tomcat/conf/Catalina/localhost/openidserver.xml to look like: {noformat} {noformat} ### (/) I edited the /opt/atlassian.../build.properties files to look like: {noformat} # Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See https://confluence.atlassian.com/display/CROWD/Connecting+Crowd+to+a+Database hibernate.dialect=org.hibernate.dialect.SQLServerDialect # The Hibernate transaction factory to use. See https://confluence.atlassian.com/display/CROWD/Configuring+Crowd hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory # The http port you wish to run crowd from, ie: http://localhost:8095/crowd crowd.tomcat.connector.port=8095 # Tomcat requires a unique port for shutdown crowd.tomcat.shutdown.port=8020 # Crowd context root crowd.url=http://localhost:8095/crowd # Demo context root demo.url=http://localhost:8095/demo # OpenID server context root openidserver.url=http://localhost:8095/openidserver {noformat} ### (/) I then ran the build.sh script in the root of /opt/atlassian... ## (/) I fired up crowd using the /opt/atlassian.../start_crowd.sh script ## (/) I then went to http://auth.mbari.org:8095/crowd to kick off the start up wizard ## (/) I grabbed a new eval license from my account on atlassian and pasted into the license page. ## (/) I selected "New install" on the next page. ## (/) I configured the JDBC connection using this connection URL with user DB_Collaboration {noformat} jdbc:jtds:sqlserver://dione.mbari.org:51001/Crowd;domain=SHORE;useNTLMv2=TRUE {noformat} ## (/) I left the "Options" as they came up {warning:title=Paths} Not sure if this is a problem, but because I started the set up using auth.mbari.org, it set the Base URL to http://auth.mbari.org:8095/crowd instead of localhost. Hope that is not a problem. We will see. {warning} ## (/) I configured the email connection using the settings from [here|https://wind.shore.mbari.org/is/howto/email/mbarimail/imap] and I used my network login (probably shouldn't be doing that ... not sure where it stores my password, but I am assuming in the DB). ## (/) For the local admin account, I created a user named 'crowdadm' so it would not clash with my LDAP account. See Kevin Gomes for password information. ## (/) I checked the OpenID server as an integrated application ## (/) It then took me to the login page and I logged in using the newly minted admin account. Seemed all is well so far. ## (/) I visited the openidserver URL as well and that seemed OK. ## (/) I decided to wait on configuring the MBARI LDAP directory until I got everything with SSL working. ## (/) Now the next step was to follow the directions to configure Crowd to run over SSL found [here|https://confluence.atlassian.com/display/CROWD/Configuring+Crowd+to+Work+with+SSL] ## (/) I shutdown crowd. Note that the stop script does not shutdown things correctly and I noticed the crowd app running as root. That should not be if I started as kgomes. Not sure what is up with that. ## (/) Now Joe had already configured SSL once, so I used his connector configuration in the server.xml file and so the final file looked like: {noformat} {noformat} ## (/) I then edited the /data/crowd/crowd.properties to look like: {noformat} #Sat Aug 01 09:05:15 PDT 2015 session.lastvalidation=session.lastvalidation session.tokenkey=session.tokenkey crowd.server.url=https\://localhost\:8443/crowd/services/ application.name=crowd http.timeout=30000 session.isauthenticated=session.isauthenticated application.login.url=https\://localhost\:8443/crowd/console/ session.validationinterval=0 application.password=Y1Xp3OorCmsOP4eruL1dmH {noformat} One thing to note here is that based on a comment from the SSL configuration page at atlassian (Steve's comment), you are supposed to leave all the host names the same. For example, if the file says localhost, leave it localhost. So this created a bit of a problem based on the fact that I had left the base URL pointing to auth.mbari.org in the wizard steps above. That step wrote auth.mbari.org to the /data/crowd/crowd.properties. All the other files reference localhost, so to be consistent, I changed auth.mbari.org to localhost in the /data/crowd/crowd.properties file. We will see if this works. ## (/) Per the instructions on the atlassian page (referenced above), I also edited the build.properties file and the /client/conf/crowd.properties files before I restarted and used the SSL URLs ## build.properties: {noformat} # Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See https://confluence.atlassian.com/display/CROWD/Connecting+Crowd+to+a+Database hibernate.dialect=org.hibernate.dialect.SQLServerDialect # The Hibernate transaction factory to use. See https://confluence.atlassian.com/display/CROWD/Configuring+Crowd hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory # The http port you wish to run crowd from, ie: http://localhost:8095/crowd crowd.tomcat.connector.port=8095 # Tomcat requires a unique port for shutdown crowd.tomcat.shutdown.port=8020 # Crowd context root crowd.url=https://localhost:8443/crowd # Demo context root demo.url=https://localhost:8443/demo # OpenID server context root openidserver.url=https://localhost:8443/openidserver {noformat} ## crowd.properties (client) {noformat} application.name crowd application.password password application.login.url https://localhost:8443/crowd/console/ crowd.server.url https://localhost:8443/crowd/services/ crowd.base.url https://localhost:8443/crowd/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 2 session.lastvalidation session.lastvalidation {noformat} ## (/) Although not stated, I am assuming you would need to run the build.sh script to push the build.properties changes to their proper places, so I did that. Note that before doing that, I know that it will clobber the server.xml changes I made, so I made a copy of that file and diff'd them after and then rolled the previous changes to the new server.xml file. Actually, amazingly enough, it seems to have done the connector entry correctly so I left it after running the build.sh script. ## (/) Crossed my fingers and then restarted crowd. I tailed the catalina.out file and did not see any stack traces so that is a good sign! ## (/) I visited https://auth.mbari.org:8443/crowd first. It could not find that page, but I suspect that is because I am browsing from the outside, so I tried just https://auth.mbari.org/crowd and got a service unavailable. I am suspecting that this is a combination of firewall and proxy pass and I will send this info to Joe. From what I can see on the crowd side, it seems like the server started cleanly, we just can't get to it. I tried to reach it from a browser on the machine itself too (through VNC) with the same service not available. ## (/) Here are the notes from Joe after he fixed it! Wooohooo! {noformat} Hey Kevin, Thanks for starting clean! I had to make a few adjustments. 1-I modified the server.xml file in /opt/atlassian-crowd-2.8.3/apache-tomcat/conf/server.xml so there are two connectors per the instructions on the Atlassian site. I have backed up this good server.xml file in /etc/temp/ if you want to browse it to see what I did. Of note is that I removed all the jargon referencing the types of ciphers available to simplify things for now. 2-I modified /data/crowd/crowd.properties to have crowd.server.url=https\://localhost\:8443/crowd/services/ application.login.url=https\://localhost\:8443/crowd/console/ But that would cause my login to error with an error saying it was unable to reach the authentication server. I scratched my head for a bit. When I revert the values to just using non-SSL and try to log in, I just get an "invalid login" (I don't know the crowdadm password). So I worked under the assumption that if I can configure SSL to get an "invalid login" when logging in then it would work when provided real credentials. So, I then changed /data/crowd/crowd.proprties to: crowd.server.url=https\://auth.mbari.org\:8443/crowd/services/ application.login.url=https\://auth.mbari.org\:8443/crowd/console/ And now when I try to log in with SSL it says "invalid login". Strange because all the other values I can find only show "localhost" .. in any case... Can you try to log in now? {noformat} ## (/) Next I moved on to configuring the connection to MBARI's LDAP server to enable our logins through Crowd and CrowdID ## (/) I clicked on "Add Directory" in crowd. ## (/) I selected "Connector" then clicked Next ## (/) I put ldap.shore.mbari.org as the name of the server ## (/) I selected "Use memberOf for group memberships" ## (/) I used "OU=AllUsers,DC=shore,DC=mbari,DC=org" for the Base DN ## (/) I used "CN=LDAPbind,OU=Special,OU=AllUsers,DC=shore,DC=mbari,DC=org" for the Username (talk to Pat Allen for password) ## (/) I tested the connection (button click) and it passed. ## (/) I de-selected all the capabilities of the connector as it is a ready only connector and then saved it. It synchronized correctly! ## (/) At first, I could not login using my MBARI credentials, but after going to the "crowd" application in crowd (logged in as the local admin), I had to add the LDAP directory and configure it to "Allow all to authenticate", then I was able to login. After this, the last step was to get this to run as a different user and lock down various directories. I went through the entire directory structure /opt/atlassian... and set up so that root owned all read-only locations and DB_Collaboration (account set up by IS) owned the other stuff. I also gave full ownership to the /data/crowd directory to DB_Collaboration so it could write there. Pat set up a script to start on boot and after a little tweaking, it now starts on boot. {warning:title=CrowdID log file} One thing that came up here was that when the crowdID application ran, it tried to write a log file to the location where the process was launched from (which is /opt/atlassian...). This is a bad thing and I figured out that I could change that location by changing the file /opt/atlassian-crowd-2.8.3/crowd-openidserver-webapp/WEB-INF/classes/log4j.properties and hardcoding the /data/crowd/logs/atlassian-crowd-openid-server.log and then restarted the application. {warning} ## (/) Another note is the when an application tried to use the OpenID application, it would get redirected to localhost. I changed the /opt/atlassian.../crowd-openidserver-webapp/WEB-INF/classes/crowd.properties file to look like: {noformat} #Sat Aug 01 10:03:18 PDT 2015 session.lastvalidation=session.lastvalidation session.tokenkey=session.tokenkey crowd.server.url=http\://localhost\:8095/crowd/services/ application.name=crowd-openid-server #application.login.url.template=http\://localhost\:8095/openidserver?returnToUrl\=${RETURN_TO_URL} application.login.url.template=https\://auth.mbari.org/openidserver?returnToUrl\=${RETURN_TO_URL} session.isauthenticated=session.isauthenticated #application.base.url=http\://localhost\:8095/openidserver application.base.url=https\://auth.mbari.org/openidserver #application.login.url=http\://localhost\:8095/openidserver application.login.url=https\://auth.mbari.org/openidserver session.validationinterval=0 application.password=password {noformat} and that seems to have fixed it. # (/) It is finally time to move on to the version 4 upgrade ... holy crap. I first went to the *new* crowd install (auth.mbari.org) and logged in as the crowdadm. # (/) I clicked on Applications, then on Add Application # (/) I selected JIRA from the Application type drop-down # (/) I entered jira445 as the username. Ask Kevin about the password. # (/) I used http://bugs.shore.mbari.org:8081 as the URL # (/) I used 134.89.12.31 as the IP address. # (/) I selected only the MBARI LDAP directory. # (/) Then I selected "Allow all users to authenticate" # (/) Then I clicked on "Add Application" # (/) I VNC'd into bugs.mbari.org. As it turns out, for Linux, there is an installer program to download. I downloaded the .bin for 64 bit Linux installer and moved it to the jira-upgrade directory. # (/) I chmod'd the file to make it executable and ran it. It gave me a warning about not being root, but I went ahead with it. # (/) It asked for the JIRA home and data directory, which I specified as /opt/jira4 and /data/jira445. # (/) For the ports, I specified 8180 and 8105 (HTTP and control respectively). It then extracted all the files and launched JIRA. It said if finished, so I opened a local browser to http://localhost:8180 which kicked off the start up wizard. # (/) I specified the external database using: ## solstice2.shore.mbari.org (server) ## 1433 (port) ## jira4 (database) ## DB_Collaboration (username) ## (password ask Kevin) ## dbo (schema) # But all this failed as it seems to just want to try and use the SQL server authentication instead of domain. I will have to do it manually. # (/) I stopped the server using the bin/stop-jira.sh script. # (/) I created and edited /data/jira445/dbconfig.xml and made it look like the following: {noformat} ?xml version="1.0" encoding="UTF-8"?> defaultDS default mssql jiraschema jdbc:jtds:sqlserver://solstice2.shore.mbari.org:1433/Jira4;domain=SHORE;useNTLMv2=true net.sourceforge.jtds.jdbc.Driver DB_Collaboration (ask Kevin) 15 {noformat} # (/) I then started it again using bin/start-jira.sh and tailed the catalina.out file. Got a bunch of errors related to the schema 'jiraschema', I edited the file and changed the schema to 'dbo' and restarted. That seemed to do it. There was one stack trace for some iCal plugin, but looks OK other than that. # I browsed back to localhost:8180 and the wizard moved to step 2. There was an option to import existing data bit without the crowd connection, I thought I should set it up manually, connect to crowd, then import. I generated an evaluation license, called the app "MBARI JIRA4" and change the server in the url to bugs.shore.mbari.org # For the admin, I created an account called 'jiraadm' (ask Kevin for password). # Since this is a temporary system, I left the email system disabled. # I logged in as jiraadm, went to Administration, then Users, then clicked on Add Directory and chose Atlassian Crowd. Note that I had to set the server URL to http://auth.mbari.org:8095/crowd or I would have had to configure all this SSL crap that I did not want to do for this temporary install. # It tested successfully, I clicked Save and it went through a 13 second sync, whew! # I then went to System->Import and Export->Restore System # I copied the jira-upgrade-3.13.5.zip file from the previous version export into /data/jira445/import and then entered that file name along with the new evaluation license again. # I worked through progress bar after I clicked on Restore (it took a really long time). # I then stopped, restarted and tailed the log file. # I am thinking now I should have put the attachments in the import attachments directory, but I am hoping I can just copy them to the data/attachments directory. # UG! I got some error during the import. The exception read: "JIRA is unable to migrat the User Directory configuration because external users exist but the osuser.xml file is not available". It then gave me a link to a doc that talked about making the old user files available before the upgrade ... crap. So I needed to copy the osuser.xml and crowd.properties file from atlassian-jira/WEB-INF/classes directory on the old install to the same directory on the new install ... sigh. This means I am going to blow away everything and start over. # I shutdown jira4 # I dropped all things in the database and deleted all content in the /data/jira445 directory (except for the dbconfig.xml file). # I also removed the temp, logs (actually you have to leave the directory, just clear the files) and the work/Catalina/localhost directories from the jira installation. # I then copied the osuser.xml and the crowd.properties files from the 3.13.5 install to the 4 install. # I edited the crowd.properties file in hopes that I could point it to the new crowd install on auth.mbari.org and it would work, but we will see. # I then started jira and tailed the log file. # All looked OK (other than iCal plugin stack trace again), so I went to localhost:8180 and got step 2 of the wizard. I used the same info as before. # I logged in as the local admin account and it looks like the system picked up the crowd connection, but lets see what server it used! Hey it used the one I edited into the file! Sweet ... now let's see if the import works. # I copied the 3.13.5 zip file to the import directory again and this time, I untarred the attachments into the import/attachments directory. # I kicked off the restore as before and it worked through it fine. # Shutdown and restarted system, tailing the log file and then went to localhost:8180 # I can see issues (before logging in) and it all looks good!! The attachments did not move over from the import directory, so I copied the tar file from /data/jira445/import to /data/jira445/data and then untarred it there, then removed the tar file and the import zip file from the import directory. # Now I will try to login using my MBARI account and OMG it actually worked!!! (it even gave my kgomes account Admin privs) # I then performed an export and copied those file to the /data/backups/4.4.5 directory (also created a TAR of the attachments and put there too). # Now on to version 5! # OK, so something strange is happening. After the imports, the server ID goes back to the one that is on our current production server, which must mean it is using our current license key (which does not match the server ID, BTW). Oh well, I will press on! # I created a /data/jira5211 directory as well as a /opt/jira5 directory. Knowing what I know now and reading through the install instructions, it appears that I need to create a dbconfig.xml file manually, so I did that using: {noformat} defaultDS default mssql dbo jdbc:jtds:sqlserver://solstice2.shore.mbari.org:1433/Jira5;domain=SHORE;useNTLMv2=true net.sourceforge.jtds.jdbc.Driver DB_Collaboration (ask Kevin) 20 20 30000 20 true 300 select 1 60000 300000 true false {noformat} ]]> 27558194 27590960 4.4: [https://confluence.atlassian.com/display/JIRA044/Migrating+JIRA+to+Another+Server] ## The JIRA configuration tool: [https://confluence.atlassian.com/display/JIRA044/Using+the+JIRA+Configuration+Tool] h5. Steps # (/) Create new VM named bugs.mbari.org in the DMZ # (/) Have Neil create database Jira_Temp on solstice2.shore.mbari.org # (/) Have Neil create database Jira on solstice2.shore.mbari.org # (/) Have Pat install Java 7 on bugs.shore.mbari.org # (/) Have Pete plumb holes through firewall so processes on bugs.mbari.org can get to Solstice2 # (/) Have Pat create DB_Collaboration account on bugs so it can run JIRA under that account and it can connect to solstice2 using that NT Domain account. # (/) Upgrade license on Atlassian site # (/) Log into bugs.shore.mbari.org # (/) Download 3.13.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 4.4.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 5.2.11 standalone Linux 64 bit tar.gz (not sure this version is necessary, but at least I have it) # (/) Unzip and untar the file to /opt # (/) Download latest JIRA (6.4.7 as of this writing). # (/) Unzip and untar it to /opt # Performed Test Upgrade ## (/) In order to export the current stuff in JIRA, I had to shut off access so people could not change the data while I was backing it up. ## (/) I ssh'd to oceana.mbari.org as root and edited the /opt/jira/conf/server.xml file and commented out the Connector section that had the port of 8010 to shut it off from the normal serving route. ## (/) I uncommented the 8082 port connector and the 8443 port connector so that I could still get to the server. ## (/) I stopped and started the JIRA server and in the log file I got a "keystore was tampered with..." which is not surprising. ## (/) I could then browser over to http://oceana.mbari.org:8082/jira ## (/) Then through the Administration console, I did an XML backup ## (/) I then created a tar of all the attachments in the /data/jira_3_12/attachments directory ## (/) I moved both the XML and tar files to the /root/jira-upgrade directory ## (/) I then reversed the changes to the server.xml file and shut down JIRA ## (/) I left it down during the next steps in case it went so well, I could just point people to the new server (yeah, right). ## (/) I then browsed to the crowd server on oceana and add a new application using: ### URL: http://bugs.mbari.org/jira3135 ### IP: 134.89.2.29 ### Name: JIRA3135 ### Password: (ask Kevin) :) ## (/) On bugs, I made a copy of the JIRA 3.13.5 download in the /opt directory and unzipped and untarred it. ## (/) In order to configure the crowd connection I did the following: ### (/) I scp'd the /opt/crowd/client/crowd-integration-client-1.6.jar file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I removed the existing 1.6.1 crowd client jar from the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I scp'd the /opt/crowd/client/conf/crowd.properties file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I scp'd the /opt/crowd/client/conf/crowd-ehcache.xml file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I edited the crowd.properties file on bugs to look like: {noformat} application.name JIRA3135 application.password (ask Kevin) application.login.url http://oceana.mbari.org:8095/crowd/console/ crowd.server.url http://oceana.mbari.org:8095/crowd/services/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 0 session.lastvalidation session.lastvalidation {noformat} ### (/) I edited the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/osuser.xml file to comment out the current authentication mechanism and then uncomment the crowd one. ## (/) I then edited the /opt/atlassian-jira-standalone-3.13.5/conf/server/xml file and configured the database connection to the Jira_Temp database on Solstice2. I looked like this: {noformat} {noformat} ## (/) Edit the /opt/atlassian/jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/entityengine.xml and changed it from 'hsql' to 'mssql' and delete the line with "PUBLIC" in it per the instructions in the comments in that file. ## (/) I edited the /etc/httpd/conf/httpd.conf file and created a proxy pass at the bottom of the file to point a normal URL to the default port 8080 for JIRA: {noformat} # Proxy Pass for JIRA ProxyPass http://bugs.mbari.org:8080 ProxyPassReverse http://bugs.mbari.org:8080 {noformat} ## (/) I restarted Apache ## (/) I scp'd the jtds driver from oceana to the /opt/atlassian-jira-standalone-3.13.5/common/lib directory (you could down from the internet) ## (/) I then went to the /opt/atlassian-jira-standalone-3.13.5/ directory and ran './bin/startup.sh'. From the log file, I could tell things were hanging. After some troubleshooting I am wondering if the local firewall is preventing the application to get access to the database on solstice2. I can telnet to port 1433, but I can't browse to the base http://bugs.mbari.org from anywhere but the local web browser. I have submitted a ticket. ## (/) I restarted the old JIRA with my hopes dashed :(. ## (/) Pat disabled the firewall on bugs.mbari.org but it still hung trying to connect to solstice2.shore.mbari.org. That is really, really perplexing. Neil mentioned that solstice2 is using Kerberos and solstice is not. Checking with the JTDS docs, version 1.3.1 of the driver added kerberos support, so I downloaded that driver and added the 'userKerberos=true' property to the URL in the server.xml file and restarted. Got an error about no credentials, so added user and password properties to the URL. Nope, no luck. Never did figure this one out, but I had Pat pull the VM inside the firewall and after some thrash it worked. Well, it sort of worked ... sigh. It turns out I had downloaded the standard version instead of the enterprise version. I need to redo this work ... grrr. ## (/) I deleted all the tables in the Jira_Temp database and removed the /data/jira3135/indexes directory (and recreated). ## (/) I downloaded the enterprise version of the 3.13.5 server. I made a copy in the /opt directory and unzipped and untarred the file. ## (/) I went back to crowd and edited the application to change the properties to: ### URL: http://bugs.shore.mbari.org:8080 ### IP: 134.89.12.31 ### Name: jira3135 ### Password: (ask Kevin) :) ## (/) I then repeated the steps above to get the server up and running with the following differences: ### The server name is now bugs.shore.mbari.org ### The paths given above are a little different in that they no longer say "standard" but say "enterprise" ### I deleted the proxy pass as it seemed to have issues before and this is only temporary anyway. ## (/) I then browsed to http://bugs.shore.mbari.org:8080 ## (/) It took me to the start up page and at the top was the option to 'import your existing data'. Seemed too good not to try. I clicked on the link. It asked me for the backup file location and the location where the indexes would be stored. ## (/) I copied the XML zip file and the attachments tar file to the /data/original directory. ## (/) I created the /data/jira3135/indexes and used those directories ... it fired off the import and I waited. ## (/) I tailed the log file to watch the import. Holy crap, it worked!!! I could log in and everything! I copied the results from the log file here for posterity sake: {noformat} 2015-07-22 20:55:45,156 http-8080-Processor22 INFO [jira.action.admin.DataImport] Running data import 2015-07-22 20:55:45,179 http-8080-Processor22 INFO [jira.action.admin.DataImport] Importing data.. 2015-07-22 20:55:45,186 http-8080-Processor22 INFO [jira.action.admin.DataImport] Start parsing XML with SAX Parser 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] XML successfully parsed 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] Removing all entries from the database. 2015-07-22 20:56:24,593 http-8080-Processor22 INFO [jira.action.admin.DataImport] All entries removed. 2015-07-22 20:56:24,594 http-8080-Processor22 INFO [jira.action.admin.DataImport] Started storing 410414 Generic Values 2015-07-22 21:01:51,967 http-8080-Processor22 INFO [jira.action.admin.DataImport] Finished storing Generic Values 2015-07-22 21:01:52,329 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:52,361 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:54,683 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLink' to module 'jira.user.format:profile-link-user-format'. 2015-07-22 21:01:54,724 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullName' to module 'jira.user.format:full-name-user-format'. 2015-07-22 21:01:54,773 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkSearcher' to module 'jira.user.format:profile-link-searcher-user-format'. 2015-07-22 21:01:54,784 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkExternal' to module 'jira.user.format:profile-link-external-user-format'. 2015-07-22 21:01:54,795 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkActionHeader' to module 'jira.user.format:profile-link-action-header-user-format'. 2015-07-22 21:01:54,807 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullProfile' to module 'jira.user.format:full-profile-user-format'. 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/comments 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/issues 2015-07-22 21:01:55,641 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/plugins 2015-07-22 21:01:55,867 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:01:55,871 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/issues does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:55,873 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/comments does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,033 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,257 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,889 http-8080-Processor22 ERROR [atlassian.jira.upgrade.ConsistencyCheckImpl] Attachments are turned on, but attachment path [/data/jira_3_12/attachments] invalid - disabling attachments 2015-07-22 21:02:13,904 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Detected that an upgrade is needed; existing data at build 299 2015-07-22 21:02:13,907 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Doing Upgrade... 2015-07-22 21:02:13,915 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value' succeeded 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 317 2015-07-22 21:02:13,944 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite filters - make each filter a favourite of its owner. 2015-07-22 21:02:17,822 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build319] Could not find author 'fpy' for filter with id '10040' 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite filters - make each filter a favourite of its owner.' succeeded 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 319 2015-07-22 21:02:17,995 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise Share Permissions. Move old shares to new shares. 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise Share Permissions. Move old shares to new shares.' succeeded 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 321 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Migrating the old JIRA UI colors to the new JIRA 3.13 colors 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build322] Custom color detected for jira.lf.menu.bgcolour : #336699 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Migrating the old JIRA UI colors to the new JIRA 3.13 colors' succeeded 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 322 2015-07-22 21:02:18,025 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite dashboards - make each dashboard a favourite of its owner. 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'cmcgann' for dashboard with id '10030' 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'fpy' for dashboard with id '10060' 2015-07-22 21:02:18,423 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'kanna' for dashboard with id '10040' 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite dashboards - make each dashboard a favourite of its owner.' succeeded 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 325 2015-07-22 21:02:18,625 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Reindexing all data in JIRA to include Favourites. 2015-07-22 21:02:18,648 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All starting... 2015-07-22 21:02:18,650 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 0% complete. Current index: Issue 2015-07-22 21:02:18,654 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:02:18,809 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 1% complete. Current index: Issue 2015-07-22 21:02:18,855 indexerPool-2-thread-10 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 2% complete. Current index: Issue 2015-07-22 21:02:18,899 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 3% complete. Current index: Issue 2015-07-22 21:02:18,945 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 4% complete. Current index: Issue 2015-07-22 21:02:19,012 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 5% complete. Current index: Issue . . . 2015-07-22 21:02:26,164 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 95% complete. Current index: Issue 2015-07-22 21:02:26,232 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 96% complete. Current index: Issue 2015-07-22 21:02:26,316 indexerPool-2-thread-9 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 97% complete. Current index: Issue 2015-07-22 21:02:26,771 indexerPool-2-thread-3 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: Issue 2015-07-22 21:02:27,261 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 8607ms. Indexer: DefaultIndexManager: paths: [/data/jira3135/indexes/issues, /data/jira3135/indexes/comments] 2015-07-22 21:02:27,263 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: SearchRequest 2015-07-22 21:02:27,268 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,293 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: SearchRequest 2015-07-22 21:02:27,308 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: PortalPage 2015-07-22 21:02:27,312 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,377 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: PortalPage 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 115ms. Indexer: SharedEntityIndexManager: paths: [/data/jira3135/indexes/entities/portalpage, /data/jira3135/indexes/entities/searchrequest] 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All complete. Total time: 8722ms. 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Reindexing all data in JIRA to include Favourites.' succeeded 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 326 2015-07-22 21:02:27,397 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade succeeded! Setting data build number to 360 2015-07-22 21:02:27,469 JiraQuartzScheduler_Worker-0 WARN [service.services.export.ExportService] Backup directory /data/jira_3_12/backup does not exist {noformat} {warning:title=Paths} It appears that the upgraded JIRA will still look for the attachments and the backup locations in the original places. So I created /data/jira_3_12/backup and untarred the original attachments to /data/jira_3_12 and then everything worked (including attachements) in the new JIRA. {warning} ## (/) I then used the upgraded JIRA to generate a new XML backup and stored it in /data/original/3.13.5 along with another tar of the files in /data/jira_3_12/attachments. ## (/) I then shutdown the JIRA server. *I should be ready to move on to version 4 upgrade WHEW* ## So, before moving on, I decided that it would be a really good idea to spin up a new Crowd instance to get rid of the :8443 in the URL and to move off of RedHat per IS requests. I have a ticket in for a new VM and a new database to try to get this going. I am waiting on that before moving on. ## (/) Pat created the VM and Neil created the database. ## (/) I logged into auth.mbari.org (name of the VM) and downloaded crowd which I unzipped to the /opt directory ## (/) I then created a /data/crowd directory and gave my account permissions on it and then edited the /opt/atlassian..../crowd-webapp/WEB-INF/classes/crowd-init.properties file to set that as the crowd home directory. ## (/) The instructions say to download the JDBC driver, but they already have JTDS 1.2.7 in the download so I did not do anything. ## (/) You have to manually connect up CrowdID to a database as they setup wizard does not currently do this. ### (/) They say to download the driver, but again 1.2.7 was there so I did nothing. ### (/) I edited the /opt/atlassian.../apache-tomcat/conf/Catalina/localhost/openidserver.xml to look like: {noformat} {noformat} ### (/) I edited the /opt/atlassian.../build.properties files to look like: {noformat} # Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See https://confluence.atlassian.com/display/CROWD/Connecting+Crowd+to+a+Database hibernate.dialect=org.hibernate.dialect.SQLServerDialect # The Hibernate transaction factory to use. See https://confluence.atlassian.com/display/CROWD/Configuring+Crowd hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory # The http port you wish to run crowd from, ie: http://localhost:8095/crowd crowd.tomcat.connector.port=8095 # Tomcat requires a unique port for shutdown crowd.tomcat.shutdown.port=8020 # Crowd context root crowd.url=http://localhost:8095/crowd # Demo context root demo.url=http://localhost:8095/demo # OpenID server context root openidserver.url=http://localhost:8095/openidserver {noformat} ### (/) I then ran the build.sh script in the root of /opt/atlassian... ## (/) I fired up crowd using the /opt/atlassian.../start_crowd.sh script ## (/) I then went to http://auth.mbari.org:8095/crowd to kick off the start up wizard ## (/) I grabbed a new eval license from my account on atlassian and pasted into the license page. ## (/) I selected "New install" on the next page. ## (/) I configured the JDBC connection using this connection URL with user DB_Collaboration {noformat} jdbc:jtds:sqlserver://dione.mbari.org:51001/Crowd;domain=SHORE;useNTLMv2=TRUE {noformat} ## (/) I left the "Options" as they came up {warning:title=Paths} Not sure if this is a problem, but because I started the set up using auth.mbari.org, it set the Base URL to http://auth.mbari.org:8095/crowd instead of localhost. Hope that is not a problem. We will see. {warning} ## (/) I configured the email connection using the settings from [here|https://wind.shore.mbari.org/is/howto/email/mbarimail/imap] and I used my network login (probably shouldn't be doing that ... not sure where it stores my password, but I am assuming in the DB). ## (/) For the local admin account, I created a user named 'crowdadm' so it would not clash with my LDAP account. See Kevin Gomes for password information. ## (/) I checked the OpenID server as an integrated application ## (/) It then took me to the login page and I logged in using the newly minted admin account. Seemed all is well so far. ## (/) I visited the openidserver URL as well and that seemed OK. ## (/) I decided to wait on configuring the MBARI LDAP directory until I got everything with SSL working. ## (/) Now the next step was to follow the directions to configure Crowd to run over SSL found [here|https://confluence.atlassian.com/display/CROWD/Configuring+Crowd+to+Work+with+SSL] ## (/) I shutdown crowd. Note that the stop script does not shutdown things correctly and I noticed the crowd app running as root. That should not be if I started as kgomes. Not sure what is up with that. ## (/) Now Joe had already configured SSL once, so I used his connector configuration in the server.xml file and so the final file looked like: {noformat} {noformat} ## (/) I then edited the /data/crowd/crowd.properties to look like: {noformat} #Sat Aug 01 09:05:15 PDT 2015 session.lastvalidation=session.lastvalidation session.tokenkey=session.tokenkey crowd.server.url=https\://localhost\:8443/crowd/services/ application.name=crowd http.timeout=30000 session.isauthenticated=session.isauthenticated application.login.url=https\://localhost\:8443/crowd/console/ session.validationinterval=0 application.password=Y1Xp3OorCmsOP4eruL1dmH {noformat} One thing to note here is that based on a comment from the SSL configuration page at atlassian (Steve's comment), you are supposed to leave all the host names the same. For example, if the file says localhost, leave it localhost. So this created a bit of a problem based on the fact that I had left the base URL pointing to auth.mbari.org in the wizard steps above. That step wrote auth.mbari.org to the /data/crowd/crowd.properties. All the other files reference localhost, so to be consistent, I changed auth.mbari.org to localhost in the /data/crowd/crowd.properties file. We will see if this works. ## (/) Per the instructions on the atlassian page (referenced above), I also edited the build.properties file and the /client/conf/crowd.properties files before I restarted and used the SSL URLs ## build.properties: {noformat} # Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See https://confluence.atlassian.com/display/CROWD/Connecting+Crowd+to+a+Database hibernate.dialect=org.hibernate.dialect.SQLServerDialect # The Hibernate transaction factory to use. See https://confluence.atlassian.com/display/CROWD/Configuring+Crowd hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory # The http port you wish to run crowd from, ie: http://localhost:8095/crowd crowd.tomcat.connector.port=8095 # Tomcat requires a unique port for shutdown crowd.tomcat.shutdown.port=8020 # Crowd context root crowd.url=https://localhost:8443/crowd # Demo context root demo.url=https://localhost:8443/demo # OpenID server context root openidserver.url=https://localhost:8443/openidserver {noformat} ## crowd.properties (client) {noformat} application.name crowd application.password password application.login.url https://localhost:8443/crowd/console/ crowd.server.url https://localhost:8443/crowd/services/ crowd.base.url https://localhost:8443/crowd/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 2 session.lastvalidation session.lastvalidation {noformat} ## (/) Although not stated, I am assuming you would need to run the build.sh script to push the build.properties changes to their proper places, so I did that. Note that before doing that, I know that it will clobber the server.xml changes I made, so I made a copy of that file and diff'd them after and then rolled the previous changes to the new server.xml file. Actually, amazingly enough, it seems to have done the connector entry correctly so I left it after running the build.sh script. ## (/) Crossed my fingers and then restarted crowd. I tailed the catalina.out file and did not see any stack traces so that is a good sign! ## (/) I visited https://auth.mbari.org:8443/crowd first. It could not find that page, but I suspect that is because I am browsing from the outside, so I tried just https://auth.mbari.org/crowd and got a service unavailable. I am suspecting that this is a combination of firewall and proxy pass and I will send this info to Joe. From what I can see on the crowd side, it seems like the server started cleanly, we just can't get to it. I tried to reach it from a browser on the machine itself too (through VNC) with the same service not available. ## (/) Here are the notes from Joe after he fixed it! Wooohooo! {noformat} Hey Kevin, Thanks for starting clean! I had to make a few adjustments. 1-I modified the server.xml file in /opt/atlassian-crowd-2.8.3/apache-tomcat/conf/server.xml so there are two connectors per the instructions on the Atlassian site. I have backed up this good server.xml file in /etc/temp/ if you want to browse it to see what I did. Of note is that I removed all the jargon referencing the types of ciphers available to simplify things for now. 2-I modified /data/crowd/crowd.properties to have crowd.server.url=https\://localhost\:8443/crowd/services/ application.login.url=https\://localhost\:8443/crowd/console/ But that would cause my login to error with an error saying it was unable to reach the authentication server. I scratched my head for a bit. When I revert the values to just using non-SSL and try to log in, I just get an "invalid login" (I don't know the crowdadm password). So I worked under the assumption that if I can configure SSL to get an "invalid login" when logging in then it would work when provided real credentials. So, I then changed /data/crowd/crowd.proprties to: crowd.server.url=https\://auth.mbari.org\:8443/crowd/services/ application.login.url=https\://auth.mbari.org\:8443/crowd/console/ And now when I try to log in with SSL it says "invalid login". Strange because all the other values I can find only show "localhost" .. in any case... Can you try to log in now? {noformat} ## (/) Next I moved on to configuring the connection to MBARI's LDAP server to enable our logins through Crowd and CrowdID ## (/) I clicked on "Add Directory" in crowd. ## (/) I selected "Connector" then clicked Next ## (/) I put ldap.shore.mbari.org as the name of the server ## (/) I selected "Use memberOf for group memberships" ## (/) I used "OU=AllUsers,DC=shore,DC=mbari,DC=org" for the Base DN ## (/) I used "CN=LDAPbind,OU=Special,OU=AllUsers,DC=shore,DC=mbari,DC=org" for the Username (talk to Pat Allen for password) ## (/) I tested the connection (button click) and it passed. ## (/) I de-selected all the capabilities of the connector as it is a ready only connector and then saved it. It synchronized correctly! ## (/) At first, I could not login using my MBARI credentials, but after going to the "crowd" application in crowd (logged in as the local admin), I had to add the LDAP directory and configure it to "Allow all to authenticate", then I was able to login. After this, the last step was to get this to run as a different user and lock down various directories. I went through the entire directory structure /opt/atlassian... and set up so that root owned all read-only locations and DB_Collaboration (account set up by IS) owned the other stuff. I also gave full ownership to the /data/crowd directory to DB_Collaboration so it could write there. Pat set up a script to start on boot and after a little tweaking, it now starts on boot. {warning:title=CrowdID log file} One thing that came up here was that when the crowdID application ran, it tried to write a log file to the location where the process was launched from (which is /opt/atlassian...). This is a bad thing and I figured out that I could change that location by changing the file /opt/atlassian-crowd-2.8.3/crowd-openidserver-webapp/WEB-INF/classes/log4j.properties and hardcoding the /data/crowd/logs/atlassian-crowd-openid-server.log and then restarted the application. {warning} ## (/) Another note is the when an application tried to use the OpenID application, it would get redirected to localhost. I changed the /opt/atlassian.../crowd-openidserver-webapp/WEB-INF/classes/crowd.properties file to look like: {noformat} #Sat Aug 01 10:03:18 PDT 2015 session.lastvalidation=session.lastvalidation session.tokenkey=session.tokenkey crowd.server.url=http\://localhost\:8095/crowd/services/ application.name=crowd-openid-server #application.login.url.template=http\://localhost\:8095/openidserver?returnToUrl\=${RETURN_TO_URL} application.login.url.template=https\://auth.mbari.org/openidserver?returnToUrl\=${RETURN_TO_URL} session.isauthenticated=session.isauthenticated #application.base.url=http\://localhost\:8095/openidserver application.base.url=https\://auth.mbari.org/openidserver #application.login.url=http\://localhost\:8095/openidserver application.login.url=https\://auth.mbari.org/openidserver session.validationinterval=0 application.password=password {noformat} and that seems to have fixed it. # (/) It is finally time to move on to the version 4 upgrade ... holy crap. I first went to the *new* crowd install (auth.mbari.org) and logged in as the crowdadm. # (/) I clicked on Applications, then on Add Application # (/) I selected JIRA from the Application type drop-down # (/) I entered jira445 as the username. Ask Kevin about the password. # (/) I used http://bugs.shore.mbari.org:8081 as the URL # (/) I used 134.89.12.31 as the IP address. # (/) I selected only the MBARI LDAP directory. # (/) Then I selected "Allow all users to authenticate" # (/) Then I clicked on "Add Application" # (/) I VNC'd into bugs.mbari.org. As it turns out, for Linux, there is an installer program to download. I downloaded the .bin for 64 bit Linux installer and moved it to the jira-upgrade directory. # (/) I chmod'd the file to make it executable and ran it. It gave me a warning about not being root, but I went ahead with it. # (/) It asked for the JIRA home and data directory, which I specified as /opt/jira4 and /data/jira445. # (/) For the ports, I specified 8180 and 8105 (HTTP and control respectively). It then extracted all the files and launched JIRA. It said if finished, so I opened a local browser to http://localhost:8180 which kicked off the start up wizard. # (/) I specified the external database using: ## solstice2.shore.mbari.org (server) ## 1433 (port) ## jira4 (database) ## DB_Collaboration (username) ## (password ask Kevin) ## dbo (schema) # But all this failed as it seems to just want to try and use the SQL server authentication instead of domain. I will have to do it manually. # (/) I stopped the server using the bin/stop-jira.sh script. # (/) I created and edited /data/jira445/dbconfig.xml and made it look like the following: {noformat} ?xml version="1.0" encoding="UTF-8"?> defaultDS default mssql jiraschema jdbc:jtds:sqlserver://solstice2.shore.mbari.org:1433/Jira4;domain=SHORE;useNTLMv2=true net.sourceforge.jtds.jdbc.Driver DB_Collaboration (ask Kevin) 15 {noformat} # (/) I then started it again using bin/start-jira.sh and tailed the catalina.out file. Got a bunch of errors related to the schema 'jiraschema', I edited the file and changed the schema to 'dbo' and restarted. That seemed to do it. There was one stack trace for some iCal plugin, but looks OK other than that. # I browsed back to localhost:8180 and the wizard moved to step 2. There was an option to import existing data bit without the crowd connection, I thought I should set it up manually, connect to crowd, then import. I generated an evaluation license, called the app "MBARI JIRA4" and change the server in the url to bugs.shore.mbari.org # For the admin, I created an account called 'jiraadm' (ask Kevin for password). # Since this is a temporary system, I left the email system disabled. # I logged in as jiraadm, went to Administration, then Users, then clicked on Add Directory and chose Atlassian Crowd. Note that I had to set the server URL to http://auth.mbari.org:8095/crowd or I would have had to configure all this SSL crap that I did not want to do for this temporary install. # It tested successfully, I clicked Save and it went through a 13 second sync, whew! # I then went to System->Import and Export->Restore System # I copied the jira-upgrade-3.13.5.zip file from the previous version export into /data/jira445/import and then entered that file name along with the new evaluation license again. # I worked through progress bar after I clicked on Restore (it took a really long time). # I then stopped, restarted and tailed the log file. # I am thinking now I should have put the attachments in the import attachments directory, but I am hoping I can just copy them to the data/attachments directory. # UG! I got some error during the import. The exception read: "JIRA is unable to migrat the User Directory configuration because external users exist but the osuser.xml file is not available". It then gave me a link to a doc that talked about making the old user files available before the upgrade ... crap. So I needed to copy the osuser.xml and crowd.properties file from atlassian-jira/WEB-INF/classes directory on the old install to the same directory on the new install ... sigh. This means I am going to blow away everything and start over. # I shutdown jira4 # I dropped all things in the database and deleted all content in the /data/jira445 directory (except for the dbconfig.xml file). # I also removed the temp, logs (actually you have to leave the directory, just clear the files) and the work/Catalina/localhost directories from the jira installation. # I then copied the osuser.xml and the crowd.properties files from the 3.13.5 install to the 4 install. # I edited the crowd.properties file in hopes that I could point it to the new crowd install on auth.mbari.org and it would work, but we will see. # I then started jira and tailed the log file. # All looked OK (other than iCal plugin stack trace again), so I went to localhost:8180 and got step 2 of the wizard. I used the same info as before. # I logged in as the local admin account and it looks like the system picked up the crowd connection, but lets see what server it used! Hey it used the one I edited into the file! Sweet ... now let's see if the import works. # I copied the 3.13.5 zip file to the import directory again and this time, I untarred the attachments into the import/attachments directory. # I kicked off the restore as before and it worked through it fine. # Shutdown and restarted system, tailing the log file and then went to localhost:8180 # I can see issues (before logging in) and it all looks good!! The attachments did not move over from the import directory, so I copied the tar file from /data/jira445/import to /data/jira445/data and then untarred it there, then removed the tar file and the import zip file from the import directory. # Now I will try to login using my MBARI account and OMG it actually worked!!! (it even gave my kgomes account Admin privs) # I then performed an export and copied those file to the /data/backups/4.4.5 directory (also created a TAR of the attachments and put there too). # Now on to version 5! # OK, so something strange is happening. After the imports, the server ID goes back to the one that is on our current production server, which must mean it is using our current license key (which does not match the server ID, BTW). Oh well, I will press on! # I created a /data/jira5211 directory as well as a /opt/jira5 directory. Knowing what I know now and reading through the install instructions, it appears that I need to create a dbconfig.xml file manually, so I did that using: {noformat} defaultDS default mssql dbo jdbc:jtds:sqlserver://solstice2.shore.mbari.org:1433/Jira5;domain=SHORE;useNTLMv2=true net.sourceforge.jtds.jdbc.Driver DB_Collaboration (ask Kevin) 20 20 30000 20 true 300 select 1 60000 300000 true false {noformat} # I then changed the mode to executable on the installer download and ran that. # I had to choose a "custom install" this time through, but the properties were similar after that (ports I used were 8280 and 8205) # I then browsed to localhost:8280 # I dropped me to a wizard where I define the title as "MBARI JIRA5", and changed host to bugs.shore.mbari.org (from localhost) # This license was a little different in that is just asked for my Atlassian username and password and fetched a new license for me. # For the admin account, I used the same 'jiraadm' account # Left email notification disabled. # I created a new application in crowd for JIRA 5 and used same account info as for 4. # In JIRA, I went to Administration->Users->User Directories and then added a directory as I had done before. # All went well and the sync happened. # I then went to Administration->System->Import and Export->Restore System # I copied the backup of 4.4.5 to the /data/jira5211/import directory and then specified that file name. I did not specify a license as it seems to use the old one and it said so in the text below the box. ]]> 27558196 27590962 4.4: [https://confluence.atlassian.com/display/JIRA044/Migrating+JIRA+to+Another+Server] ## The JIRA configuration tool: [https://confluence.atlassian.com/display/JIRA044/Using+the+JIRA+Configuration+Tool] h5. Steps # (/) Create new VM named bugs.mbari.org in the DMZ # (/) Have Neil create database Jira_Temp on solstice2.shore.mbari.org # (/) Have Neil create database Jira on solstice2.shore.mbari.org # (/) Have Pat install Java 7 on bugs.shore.mbari.org # (/) Have Pete plumb holes through firewall so processes on bugs.mbari.org can get to Solstice2 # (/) Have Pat create DB_Collaboration account on bugs so it can run JIRA under that account and it can connect to solstice2 using that NT Domain account. # (/) Upgrade license on Atlassian site # (/) Log into bugs.shore.mbari.org # (/) Download 3.13.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 4.4.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 5.2.11 standalone Linux 64 bit tar.gz (not sure this version is necessary, but at least I have it) # (/) Unzip and untar the file to /opt # (/) Download latest JIRA (6.4.7 as of this writing). # (/) Unzip and untar it to /opt # Performed Test Upgrade ## (/) In order to export the current stuff in JIRA, I had to shut off access so people could not change the data while I was backing it up. ## (/) I ssh'd to oceana.mbari.org as root and edited the /opt/jira/conf/server.xml file and commented out the Connector section that had the port of 8010 to shut it off from the normal serving route. ## (/) I uncommented the 8082 port connector and the 8443 port connector so that I could still get to the server. ## (/) I stopped and started the JIRA server and in the log file I got a "keystore was tampered with..." which is not surprising. ## (/) I could then browser over to http://oceana.mbari.org:8082/jira ## (/) Then through the Administration console, I did an XML backup ## (/) I then created a tar of all the attachments in the /data/jira_3_12/attachments directory ## (/) I moved both the XML and tar files to the /root/jira-upgrade directory ## (/) I then reversed the changes to the server.xml file and shut down JIRA ## (/) I left it down during the next steps in case it went so well, I could just point people to the new server (yeah, right). ## (/) I then browsed to the crowd server on oceana and add a new application using: ### URL: http://bugs.mbari.org/jira3135 ### IP: 134.89.2.29 ### Name: JIRA3135 ### Password: (ask Kevin) :) ## (/) On bugs, I made a copy of the JIRA 3.13.5 download in the /opt directory and unzipped and untarred it. ## (/) In order to configure the crowd connection I did the following: ### (/) I scp'd the /opt/crowd/client/crowd-integration-client-1.6.jar file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I removed the existing 1.6.1 crowd client jar from the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I scp'd the /opt/crowd/client/conf/crowd.properties file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I scp'd the /opt/crowd/client/conf/crowd-ehcache.xml file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I edited the crowd.properties file on bugs to look like: {noformat} application.name JIRA3135 application.password (ask Kevin) application.login.url http://oceana.mbari.org:8095/crowd/console/ crowd.server.url http://oceana.mbari.org:8095/crowd/services/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 0 session.lastvalidation session.lastvalidation {noformat} ### (/) I edited the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/osuser.xml file to comment out the current authentication mechanism and then uncomment the crowd one. ## (/) I then edited the /opt/atlassian-jira-standalone-3.13.5/conf/server/xml file and configured the database connection to the Jira_Temp database on Solstice2. I looked like this: {noformat} {noformat} ## (/) Edit the /opt/atlassian/jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/entityengine.xml and changed it from 'hsql' to 'mssql' and delete the line with "PUBLIC" in it per the instructions in the comments in that file. ## (/) I edited the /etc/httpd/conf/httpd.conf file and created a proxy pass at the bottom of the file to point a normal URL to the default port 8080 for JIRA: {noformat} # Proxy Pass for JIRA ProxyPass http://bugs.mbari.org:8080 ProxyPassReverse http://bugs.mbari.org:8080 {noformat} ## (/) I restarted Apache ## (/) I scp'd the jtds driver from oceana to the /opt/atlassian-jira-standalone-3.13.5/common/lib directory (you could down from the internet) ## (/) I then went to the /opt/atlassian-jira-standalone-3.13.5/ directory and ran './bin/startup.sh'. From the log file, I could tell things were hanging. After some troubleshooting I am wondering if the local firewall is preventing the application to get access to the database on solstice2. I can telnet to port 1433, but I can't browse to the base http://bugs.mbari.org from anywhere but the local web browser. I have submitted a ticket. ## (/) I restarted the old JIRA with my hopes dashed :(. ## (/) Pat disabled the firewall on bugs.mbari.org but it still hung trying to connect to solstice2.shore.mbari.org. That is really, really perplexing. Neil mentioned that solstice2 is using Kerberos and solstice is not. Checking with the JTDS docs, version 1.3.1 of the driver added kerberos support, so I downloaded that driver and added the 'userKerberos=true' property to the URL in the server.xml file and restarted. Got an error about no credentials, so added user and password properties to the URL. Nope, no luck. Never did figure this one out, but I had Pat pull the VM inside the firewall and after some thrash it worked. Well, it sort of worked ... sigh. It turns out I had downloaded the standard version instead of the enterprise version. I need to redo this work ... grrr. ## (/) I deleted all the tables in the Jira_Temp database and removed the /data/jira3135/indexes directory (and recreated). ## (/) I downloaded the enterprise version of the 3.13.5 server. I made a copy in the /opt directory and unzipped and untarred the file. ## (/) I went back to crowd and edited the application to change the properties to: ### URL: http://bugs.shore.mbari.org:8080 ### IP: 134.89.12.31 ### Name: jira3135 ### Password: (ask Kevin) :) ## (/) I then repeated the steps above to get the server up and running with the following differences: ### The server name is now bugs.shore.mbari.org ### The paths given above are a little different in that they no longer say "standard" but say "enterprise" ### I deleted the proxy pass as it seemed to have issues before and this is only temporary anyway. ## (/) I then browsed to http://bugs.shore.mbari.org:8080 ## (/) It took me to the start up page and at the top was the option to 'import your existing data'. Seemed too good not to try. I clicked on the link. It asked me for the backup file location and the location where the indexes would be stored. ## (/) I copied the XML zip file and the attachments tar file to the /data/original directory. ## (/) I created the /data/jira3135/indexes and used those directories ... it fired off the import and I waited. ## (/) I tailed the log file to watch the import. Holy crap, it worked!!! I could log in and everything! I copied the results from the log file here for posterity sake: {noformat} 2015-07-22 20:55:45,156 http-8080-Processor22 INFO [jira.action.admin.DataImport] Running data import 2015-07-22 20:55:45,179 http-8080-Processor22 INFO [jira.action.admin.DataImport] Importing data.. 2015-07-22 20:55:45,186 http-8080-Processor22 INFO [jira.action.admin.DataImport] Start parsing XML with SAX Parser 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] XML successfully parsed 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] Removing all entries from the database. 2015-07-22 20:56:24,593 http-8080-Processor22 INFO [jira.action.admin.DataImport] All entries removed. 2015-07-22 20:56:24,594 http-8080-Processor22 INFO [jira.action.admin.DataImport] Started storing 410414 Generic Values 2015-07-22 21:01:51,967 http-8080-Processor22 INFO [jira.action.admin.DataImport] Finished storing Generic Values 2015-07-22 21:01:52,329 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:52,361 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:54,683 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLink' to module 'jira.user.format:profile-link-user-format'. 2015-07-22 21:01:54,724 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullName' to module 'jira.user.format:full-name-user-format'. 2015-07-22 21:01:54,773 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkSearcher' to module 'jira.user.format:profile-link-searcher-user-format'. 2015-07-22 21:01:54,784 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkExternal' to module 'jira.user.format:profile-link-external-user-format'. 2015-07-22 21:01:54,795 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkActionHeader' to module 'jira.user.format:profile-link-action-header-user-format'. 2015-07-22 21:01:54,807 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullProfile' to module 'jira.user.format:full-profile-user-format'. 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/comments 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/issues 2015-07-22 21:01:55,641 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/plugins 2015-07-22 21:01:55,867 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:01:55,871 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/issues does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:55,873 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/comments does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,033 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,257 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,889 http-8080-Processor22 ERROR [atlassian.jira.upgrade.ConsistencyCheckImpl] Attachments are turned on, but attachment path [/data/jira_3_12/attachments] invalid - disabling attachments 2015-07-22 21:02:13,904 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Detected that an upgrade is needed; existing data at build 299 2015-07-22 21:02:13,907 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Doing Upgrade... 2015-07-22 21:02:13,915 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value' succeeded 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 317 2015-07-22 21:02:13,944 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite filters - make each filter a favourite of its owner. 2015-07-22 21:02:17,822 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build319] Could not find author 'fpy' for filter with id '10040' 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite filters - make each filter a favourite of its owner.' succeeded 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 319 2015-07-22 21:02:17,995 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise Share Permissions. Move old shares to new shares. 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise Share Permissions. Move old shares to new shares.' succeeded 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 321 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Migrating the old JIRA UI colors to the new JIRA 3.13 colors 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build322] Custom color detected for jira.lf.menu.bgcolour : #336699 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Migrating the old JIRA UI colors to the new JIRA 3.13 colors' succeeded 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 322 2015-07-22 21:02:18,025 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite dashboards - make each dashboard a favourite of its owner. 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'cmcgann' for dashboard with id '10030' 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'fpy' for dashboard with id '10060' 2015-07-22 21:02:18,423 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'kanna' for dashboard with id '10040' 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite dashboards - make each dashboard a favourite of its owner.' succeeded 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 325 2015-07-22 21:02:18,625 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Reindexing all data in JIRA to include Favourites. 2015-07-22 21:02:18,648 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All starting... 2015-07-22 21:02:18,650 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 0% complete. Current index: Issue 2015-07-22 21:02:18,654 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:02:18,809 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 1% complete. Current index: Issue 2015-07-22 21:02:18,855 indexerPool-2-thread-10 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 2% complete. Current index: Issue 2015-07-22 21:02:18,899 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 3% complete. Current index: Issue 2015-07-22 21:02:18,945 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 4% complete. Current index: Issue 2015-07-22 21:02:19,012 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 5% complete. Current index: Issue . . . 2015-07-22 21:02:26,164 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 95% complete. Current index: Issue 2015-07-22 21:02:26,232 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 96% complete. Current index: Issue 2015-07-22 21:02:26,316 indexerPool-2-thread-9 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 97% complete. Current index: Issue 2015-07-22 21:02:26,771 indexerPool-2-thread-3 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: Issue 2015-07-22 21:02:27,261 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 8607ms. Indexer: DefaultIndexManager: paths: [/data/jira3135/indexes/issues, /data/jira3135/indexes/comments] 2015-07-22 21:02:27,263 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: SearchRequest 2015-07-22 21:02:27,268 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,293 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: SearchRequest 2015-07-22 21:02:27,308 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: PortalPage 2015-07-22 21:02:27,312 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,377 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: PortalPage 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 115ms. Indexer: SharedEntityIndexManager: paths: [/data/jira3135/indexes/entities/portalpage, /data/jira3135/indexes/entities/searchrequest] 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All complete. Total time: 8722ms. 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Reindexing all data in JIRA to include Favourites.' succeeded 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 326 2015-07-22 21:02:27,397 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade succeeded! Setting data build number to 360 2015-07-22 21:02:27,469 JiraQuartzScheduler_Worker-0 WARN [service.services.export.ExportService] Backup directory /data/jira_3_12/backup does not exist {noformat} {warning:title=Paths} It appears that the upgraded JIRA will still look for the attachments and the backup locations in the original places. So I created /data/jira_3_12/backup and untarred the original attachments to /data/jira_3_12 and then everything worked (including attachements) in the new JIRA. {warning} ## (/) I then used the upgraded JIRA to generate a new XML backup and stored it in /data/original/3.13.5 along with another tar of the files in /data/jira_3_12/attachments. ## (/) I then shutdown the JIRA server. *I should be ready to move on to version 4 upgrade WHEW* ## So, before moving on, I decided that it would be a really good idea to spin up a new Crowd instance to get rid of the :8443 in the URL and to move off of RedHat per IS requests. I have a ticket in for a new VM and a new database to try to get this going. I am waiting on that before moving on. ## (/) Pat created the VM and Neil created the database. ## (/) I logged into auth.mbari.org (name of the VM) and downloaded crowd which I unzipped to the /opt directory ## (/) I then created a /data/crowd directory and gave my account permissions on it and then edited the /opt/atlassian..../crowd-webapp/WEB-INF/classes/crowd-init.properties file to set that as the crowd home directory. ## (/) The instructions say to download the JDBC driver, but they already have JTDS 1.2.7 in the download so I did not do anything. ## (/) You have to manually connect up CrowdID to a database as they setup wizard does not currently do this. ### (/) They say to download the driver, but again 1.2.7 was there so I did nothing. ### (/) I edited the /opt/atlassian.../apache-tomcat/conf/Catalina/localhost/openidserver.xml to look like: {noformat} {noformat} ### (/) I edited the /opt/atlassian.../build.properties files to look like: {noformat} # Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See https://confluence.atlassian.com/display/CROWD/Connecting+Crowd+to+a+Database hibernate.dialect=org.hibernate.dialect.SQLServerDialect # The Hibernate transaction factory to use. See https://confluence.atlassian.com/display/CROWD/Configuring+Crowd hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory # The http port you wish to run crowd from, ie: http://localhost:8095/crowd crowd.tomcat.connector.port=8095 # Tomcat requires a unique port for shutdown crowd.tomcat.shutdown.port=8020 # Crowd context root crowd.url=http://localhost:8095/crowd # Demo context root demo.url=http://localhost:8095/demo # OpenID server context root openidserver.url=http://localhost:8095/openidserver {noformat} ### (/) I then ran the build.sh script in the root of /opt/atlassian... ## (/) I fired up crowd using the /opt/atlassian.../start_crowd.sh script ## (/) I then went to http://auth.mbari.org:8095/crowd to kick off the start up wizard ## (/) I grabbed a new eval license from my account on atlassian and pasted into the license page. ## (/) I selected "New install" on the next page. ## (/) I configured the JDBC connection using this connection URL with user DB_Collaboration {noformat} jdbc:jtds:sqlserver://dione.mbari.org:51001/Crowd;domain=SHORE;useNTLMv2=TRUE {noformat} ## (/) I left the "Options" as they came up {warning:title=Paths} Not sure if this is a problem, but because I started the set up using auth.mbari.org, it set the Base URL to http://auth.mbari.org:8095/crowd instead of localhost. Hope that is not a problem. We will see. {warning} ## (/) I configured the email connection using the settings from [here|https://wind.shore.mbari.org/is/howto/email/mbarimail/imap] and I used my network login (probably shouldn't be doing that ... not sure where it stores my password, but I am assuming in the DB). ## (/) For the local admin account, I created a user named 'crowdadm' so it would not clash with my LDAP account. See Kevin Gomes for password information. ## (/) I checked the OpenID server as an integrated application ## (/) It then took me to the login page and I logged in using the newly minted admin account. Seemed all is well so far. ## (/) I visited the openidserver URL as well and that seemed OK. ## (/) I decided to wait on configuring the MBARI LDAP directory until I got everything with SSL working. ## (/) Now the next step was to follow the directions to configure Crowd to run over SSL found [here|https://confluence.atlassian.com/display/CROWD/Configuring+Crowd+to+Work+with+SSL] ## (/) I shutdown crowd. Note that the stop script does not shutdown things correctly and I noticed the crowd app running as root. That should not be if I started as kgomes. Not sure what is up with that. ## (/) Now Joe had already configured SSL once, so I used his connector configuration in the server.xml file and so the final file looked like: {noformat} {noformat} ## (/) I then edited the /data/crowd/crowd.properties to look like: {noformat} #Sat Aug 01 09:05:15 PDT 2015 session.lastvalidation=session.lastvalidation session.tokenkey=session.tokenkey crowd.server.url=https\://localhost\:8443/crowd/services/ application.name=crowd http.timeout=30000 session.isauthenticated=session.isauthenticated application.login.url=https\://localhost\:8443/crowd/console/ session.validationinterval=0 application.password=Y1Xp3OorCmsOP4eruL1dmH {noformat} One thing to note here is that based on a comment from the SSL configuration page at atlassian (Steve's comment), you are supposed to leave all the host names the same. For example, if the file says localhost, leave it localhost. So this created a bit of a problem based on the fact that I had left the base URL pointing to auth.mbari.org in the wizard steps above. That step wrote auth.mbari.org to the /data/crowd/crowd.properties. All the other files reference localhost, so to be consistent, I changed auth.mbari.org to localhost in the /data/crowd/crowd.properties file. We will see if this works. ## (/) Per the instructions on the atlassian page (referenced above), I also edited the build.properties file and the /client/conf/crowd.properties files before I restarted and used the SSL URLs ## build.properties: {noformat} # Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See https://confluence.atlassian.com/display/CROWD/Connecting+Crowd+to+a+Database hibernate.dialect=org.hibernate.dialect.SQLServerDialect # The Hibernate transaction factory to use. See https://confluence.atlassian.com/display/CROWD/Configuring+Crowd hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory # The http port you wish to run crowd from, ie: http://localhost:8095/crowd crowd.tomcat.connector.port=8095 # Tomcat requires a unique port for shutdown crowd.tomcat.shutdown.port=8020 # Crowd context root crowd.url=https://localhost:8443/crowd # Demo context root demo.url=https://localhost:8443/demo # OpenID server context root openidserver.url=https://localhost:8443/openidserver {noformat} ## crowd.properties (client) {noformat} application.name crowd application.password password application.login.url https://localhost:8443/crowd/console/ crowd.server.url https://localhost:8443/crowd/services/ crowd.base.url https://localhost:8443/crowd/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 2 session.lastvalidation session.lastvalidation {noformat} ## (/) Although not stated, I am assuming you would need to run the build.sh script to push the build.properties changes to their proper places, so I did that. Note that before doing that, I know that it will clobber the server.xml changes I made, so I made a copy of that file and diff'd them after and then rolled the previous changes to the new server.xml file. Actually, amazingly enough, it seems to have done the connector entry correctly so I left it after running the build.sh script. ## (/) Crossed my fingers and then restarted crowd. I tailed the catalina.out file and did not see any stack traces so that is a good sign! ## (/) I visited https://auth.mbari.org:8443/crowd first. It could not find that page, but I suspect that is because I am browsing from the outside, so I tried just https://auth.mbari.org/crowd and got a service unavailable. I am suspecting that this is a combination of firewall and proxy pass and I will send this info to Joe. From what I can see on the crowd side, it seems like the server started cleanly, we just can't get to it. I tried to reach it from a browser on the machine itself too (through VNC) with the same service not available. ## (/) Here are the notes from Joe after he fixed it! Wooohooo! {noformat} Hey Kevin, Thanks for starting clean! I had to make a few adjustments. 1-I modified the server.xml file in /opt/atlassian-crowd-2.8.3/apache-tomcat/conf/server.xml so there are two connectors per the instructions on the Atlassian site. I have backed up this good server.xml file in /etc/temp/ if you want to browse it to see what I did. Of note is that I removed all the jargon referencing the types of ciphers available to simplify things for now. 2-I modified /data/crowd/crowd.properties to have crowd.server.url=https\://localhost\:8443/crowd/services/ application.login.url=https\://localhost\:8443/crowd/console/ But that would cause my login to error with an error saying it was unable to reach the authentication server. I scratched my head for a bit. When I revert the values to just using non-SSL and try to log in, I just get an "invalid login" (I don't know the crowdadm password). So I worked under the assumption that if I can configure SSL to get an "invalid login" when logging in then it would work when provided real credentials. So, I then changed /data/crowd/crowd.proprties to: crowd.server.url=https\://auth.mbari.org\:8443/crowd/services/ application.login.url=https\://auth.mbari.org\:8443/crowd/console/ And now when I try to log in with SSL it says "invalid login". Strange because all the other values I can find only show "localhost" .. in any case... Can you try to log in now? {noformat} ## (/) Next I moved on to configuring the connection to MBARI's LDAP server to enable our logins through Crowd and CrowdID ## (/) I clicked on "Add Directory" in crowd. ## (/) I selected "Connector" then clicked Next ## (/) I put ldap.shore.mbari.org as the name of the server ## (/) I selected "Use memberOf for group memberships" ## (/) I used "OU=AllUsers,DC=shore,DC=mbari,DC=org" for the Base DN ## (/) I used "CN=LDAPbind,OU=Special,OU=AllUsers,DC=shore,DC=mbari,DC=org" for the Username (talk to Pat Allen for password) ## (/) I tested the connection (button click) and it passed. ## (/) I de-selected all the capabilities of the connector as it is a ready only connector and then saved it. It synchronized correctly! ## (/) At first, I could not login using my MBARI credentials, but after going to the "crowd" application in crowd (logged in as the local admin), I had to add the LDAP directory and configure it to "Allow all to authenticate", then I was able to login. After this, the last step was to get this to run as a different user and lock down various directories. I went through the entire directory structure /opt/atlassian... and set up so that root owned all read-only locations and DB_Collaboration (account set up by IS) owned the other stuff. I also gave full ownership to the /data/crowd directory to DB_Collaboration so it could write there. Pat set up a script to start on boot and after a little tweaking, it now starts on boot. {warning:title=CrowdID log file} One thing that came up here was that when the crowdID application ran, it tried to write a log file to the location where the process was launched from (which is /opt/atlassian...). This is a bad thing and I figured out that I could change that location by changing the file /opt/atlassian-crowd-2.8.3/crowd-openidserver-webapp/WEB-INF/classes/log4j.properties and hardcoding the /data/crowd/logs/atlassian-crowd-openid-server.log and then restarted the application. {warning} ## (/) Another note is the when an application tried to use the OpenID application, it would get redirected to localhost. I changed the /opt/atlassian.../crowd-openidserver-webapp/WEB-INF/classes/crowd.properties file to look like: {noformat} #Sat Aug 01 10:03:18 PDT 2015 session.lastvalidation=session.lastvalidation session.tokenkey=session.tokenkey crowd.server.url=http\://localhost\:8095/crowd/services/ application.name=crowd-openid-server #application.login.url.template=http\://localhost\:8095/openidserver?returnToUrl\=${RETURN_TO_URL} application.login.url.template=https\://auth.mbari.org/openidserver?returnToUrl\=${RETURN_TO_URL} session.isauthenticated=session.isauthenticated #application.base.url=http\://localhost\:8095/openidserver application.base.url=https\://auth.mbari.org/openidserver #application.login.url=http\://localhost\:8095/openidserver application.login.url=https\://auth.mbari.org/openidserver session.validationinterval=0 application.password=password {noformat} and that seems to have fixed it. # (/) It is finally time to move on to the version 4 upgrade ... holy crap. I first went to the *new* crowd install (auth.mbari.org) and logged in as the crowdadm. # (/) I clicked on Applications, then on Add Application # (/) I selected JIRA from the Application type drop-down # (/) I entered jira445 as the username. Ask Kevin about the password. # (/) I used http://bugs.shore.mbari.org:8081 as the URL # (/) I used 134.89.12.31 as the IP address. # (/) I selected only the MBARI LDAP directory. # (/) Then I selected "Allow all users to authenticate" # (/) Then I clicked on "Add Application" # (/) I VNC'd into bugs.mbari.org. As it turns out, for Linux, there is an installer program to download. I downloaded the .bin for 64 bit Linux installer and moved it to the jira-upgrade directory. # (/) I chmod'd the file to make it executable and ran it. It gave me a warning about not being root, but I went ahead with it. # (/) It asked for the JIRA home and data directory, which I specified as /opt/jira4 and /data/jira445. # (/) For the ports, I specified 8180 and 8105 (HTTP and control respectively). It then extracted all the files and launched JIRA. It said if finished, so I opened a local browser to http://localhost:8180 which kicked off the start up wizard. # (/) I specified the external database using: ## solstice2.shore.mbari.org (server) ## 1433 (port) ## jira4 (database) ## DB_Collaboration (username) ## (password ask Kevin) ## dbo (schema) # But all this failed as it seems to just want to try and use the SQL server authentication instead of domain. I will have to do it manually. # (/) I stopped the server using the bin/stop-jira.sh script. # (/) I created and edited /data/jira445/dbconfig.xml and made it look like the following: {noformat} ?xml version="1.0" encoding="UTF-8"?> defaultDS default mssql jiraschema jdbc:jtds:sqlserver://solstice2.shore.mbari.org:1433/Jira4;domain=SHORE;useNTLMv2=true net.sourceforge.jtds.jdbc.Driver DB_Collaboration (ask Kevin) 15 {noformat} # (/) I then started it again using bin/start-jira.sh and tailed the catalina.out file. Got a bunch of errors related to the schema 'jiraschema', I edited the file and changed the schema to 'dbo' and restarted. That seemed to do it. There was one stack trace for some iCal plugin, but looks OK other than that. # I browsed back to localhost:8180 and the wizard moved to step 2. There was an option to import existing data bit without the crowd connection, I thought I should set it up manually, connect to crowd, then import. I generated an evaluation license, called the app "MBARI JIRA4" and change the server in the url to bugs.shore.mbari.org # For the admin, I created an account called 'jiraadm' (ask Kevin for password). # Since this is a temporary system, I left the email system disabled. # I logged in as jiraadm, went to Administration, then Users, then clicked on Add Directory and chose Atlassian Crowd. Note that I had to set the server URL to http://auth.mbari.org:8095/crowd or I would have had to configure all this SSL crap that I did not want to do for this temporary install. # It tested successfully, I clicked Save and it went through a 13 second sync, whew! # I then went to System->Import and Export->Restore System # I copied the jira-upgrade-3.13.5.zip file from the previous version export into /data/jira445/import and then entered that file name along with the new evaluation license again. # I worked through progress bar after I clicked on Restore (it took a really long time). # I then stopped, restarted and tailed the log file. # I am thinking now I should have put the attachments in the import attachments directory, but I am hoping I can just copy them to the data/attachments directory. # UG! I got some error during the import. The exception read: "JIRA is unable to migrat the User Directory configuration because external users exist but the osuser.xml file is not available". It then gave me a link to a doc that talked about making the old user files available before the upgrade ... crap. So I needed to copy the osuser.xml and crowd.properties file from atlassian-jira/WEB-INF/classes directory on the old install to the same directory on the new install ... sigh. This means I am going to blow away everything and start over. # I shutdown jira4 # I dropped all things in the database and deleted all content in the /data/jira445 directory (except for the dbconfig.xml file). # I also removed the temp, logs (actually you have to leave the directory, just clear the files) and the work/Catalina/localhost directories from the jira installation. # I then copied the osuser.xml and the crowd.properties files from the 3.13.5 install to the 4 install. # I edited the crowd.properties file in hopes that I could point it to the new crowd install on auth.mbari.org and it would work, but we will see. # I then started jira and tailed the log file. # All looked OK (other than iCal plugin stack trace again), so I went to localhost:8180 and got step 2 of the wizard. I used the same info as before. # I logged in as the local admin account and it looks like the system picked up the crowd connection, but lets see what server it used! Hey it used the one I edited into the file! Sweet ... now let's see if the import works. # I copied the 3.13.5 zip file to the import directory again and this time, I untarred the attachments into the import/attachments directory. # I kicked off the restore as before and it worked through it fine. # Shutdown and restarted system, tailing the log file and then went to localhost:8180 # I can see issues (before logging in) and it all looks good!! The attachments did not move over from the import directory, so I copied the tar file from /data/jira445/import to /data/jira445/data and then untarred it there, then removed the tar file and the import zip file from the import directory. # Now I will try to login using my MBARI account and OMG it actually worked!!! (it even gave my kgomes account Admin privs) # I then performed an export and copied those file to the /data/backups/4.4.5 directory (also created a TAR of the attachments and put there too). # Now on to version 5! # OK, so something strange is happening. After the imports, the server ID goes back to the one that is on our current production server, which must mean it is using our current license key (which does not match the server ID, BTW). Oh well, I will press on! # I created a /data/jira5211 directory as well as a /opt/jira5 directory. Knowing what I know now and reading through the install instructions, it appears that I need to create a dbconfig.xml file manually, so I did that using: {noformat} defaultDS default mssql dbo jdbc:jtds:sqlserver://solstice2.shore.mbari.org:1433/Jira5;domain=SHORE;useNTLMv2=true net.sourceforge.jtds.jdbc.Driver DB_Collaboration (ask Kevin) 20 20 30000 20 true 300 select 1 60000 300000 true false {noformat} # I then changed the mode to executable on the installer download and ran that. # I had to choose a "custom install" this time through, but the properties were similar after that (ports I used were 8280 and 8205) # I then browsed to localhost:8280 # I dropped me to a wizard where I define the title as "MBARI JIRA5", and changed host to bugs.shore.mbari.org (from localhost) # This license was a little different in that is just asked for my Atlassian username and password and fetched a new license for me. # For the admin account, I used the same 'jiraadm' account # Left email notification disabled. # I created a new application in crowd for JIRA 5 and used same account info as for 4. # In JIRA, I went to Administration->Users->User Directories and then added a directory as I had done before. # All went well and the sync happened. # I then went to Administration->System->Import and Export->Restore System # I copied the backup of 4.4.5 to the /data/jira5211/import directory and then specified that file name. I did not specify a license as it seems to use the old one and it said so in the text below the box. # Clicked on restore and while it was restoring, I untarred the attachments to the /data/jira5211/data directory ]]> 27558198 8388610 8355842 27590964 4.4: [https://confluence.atlassian.com/display/JIRA044/Migrating+JIRA+to+Another+Server] ## The JIRA configuration tool: [https://confluence.atlassian.com/display/JIRA044/Using+the+JIRA+Configuration+Tool] h5. Steps # (/) Create new VM named bugs.mbari.org in the DMZ # (/) Have Neil create database Jira_Temp on solstice2.shore.mbari.org # (/) Have Neil create database Jira on solstice2.shore.mbari.org # (/) Have Pat install Java 7 on bugs.shore.mbari.org # (/) Have Pete plumb holes through firewall so processes on bugs.mbari.org can get to Solstice2 # (/) Have Pat create DB_Collaboration account on bugs so it can run JIRA under that account and it can connect to solstice2 using that NT Domain account. # (/) Upgrade license on Atlassian site # (/) Log into bugs.shore.mbari.org # (/) Download 3.13.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 4.4.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 5.2.11 standalone Linux 64 bit tar.gz (not sure this version is necessary, but at least I have it) # (/) Unzip and untar the file to /opt # (/) Download latest JIRA (6.4.7 as of this writing). # (/) Unzip and untar it to /opt # Performed Test Upgrade ## (/) In order to export the current stuff in JIRA, I had to shut off access so people could not change the data while I was backing it up. ## (/) I ssh'd to oceana.mbari.org as root and edited the /opt/jira/conf/server.xml file and commented out the Connector section that had the port of 8010 to shut it off from the normal serving route. ## (/) I uncommented the 8082 port connector and the 8443 port connector so that I could still get to the server. ## (/) I stopped and started the JIRA server and in the log file I got a "keystore was tampered with..." which is not surprising. ## (/) I could then browser over to http://oceana.mbari.org:8082/jira ## (/) Then through the Administration console, I did an XML backup ## (/) I then created a tar of all the attachments in the /data/jira_3_12/attachments directory ## (/) I moved both the XML and tar files to the /root/jira-upgrade directory ## (/) I then reversed the changes to the server.xml file and shut down JIRA ## (/) I left it down during the next steps in case it went so well, I could just point people to the new server (yeah, right). ## (/) I then browsed to the crowd server on oceana and add a new application using: ### URL: http://bugs.mbari.org/jira3135 ### IP: 134.89.2.29 ### Name: JIRA3135 ### Password: (ask Kevin) :) ## (/) On bugs, I made a copy of the JIRA 3.13.5 download in the /opt directory and unzipped and untarred it. ## (/) In order to configure the crowd connection I did the following: ### (/) I scp'd the /opt/crowd/client/crowd-integration-client-1.6.jar file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I removed the existing 1.6.1 crowd client jar from the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I scp'd the /opt/crowd/client/conf/crowd.properties file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I scp'd the /opt/crowd/client/conf/crowd-ehcache.xml file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I edited the crowd.properties file on bugs to look like: {noformat} application.name JIRA3135 application.password (ask Kevin) application.login.url http://oceana.mbari.org:8095/crowd/console/ crowd.server.url http://oceana.mbari.org:8095/crowd/services/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 0 session.lastvalidation session.lastvalidation {noformat} ### (/) I edited the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/osuser.xml file to comment out the current authentication mechanism and then uncomment the crowd one. ## (/) I then edited the /opt/atlassian-jira-standalone-3.13.5/conf/server/xml file and configured the database connection to the Jira_Temp database on Solstice2. I looked like this: {noformat} {noformat} ## (/) Edit the /opt/atlassian/jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/entityengine.xml and changed it from 'hsql' to 'mssql' and delete the line with "PUBLIC" in it per the instructions in the comments in that file. ## (/) I edited the /etc/httpd/conf/httpd.conf file and created a proxy pass at the bottom of the file to point a normal URL to the default port 8080 for JIRA: {noformat} # Proxy Pass for JIRA ProxyPass http://bugs.mbari.org:8080 ProxyPassReverse http://bugs.mbari.org:8080 {noformat} ## (/) I restarted Apache ## (/) I scp'd the jtds driver from oceana to the /opt/atlassian-jira-standalone-3.13.5/common/lib directory (you could down from the internet) ## (/) I then went to the /opt/atlassian-jira-standalone-3.13.5/ directory and ran './bin/startup.sh'. From the log file, I could tell things were hanging. After some troubleshooting I am wondering if the local firewall is preventing the application to get access to the database on solstice2. I can telnet to port 1433, but I can't browse to the base http://bugs.mbari.org from anywhere but the local web browser. I have submitted a ticket. ## (/) I restarted the old JIRA with my hopes dashed :(. ## (/) Pat disabled the firewall on bugs.mbari.org but it still hung trying to connect to solstice2.shore.mbari.org. That is really, really perplexing. Neil mentioned that solstice2 is using Kerberos and solstice is not. Checking with the JTDS docs, version 1.3.1 of the driver added kerberos support, so I downloaded that driver and added the 'userKerberos=true' property to the URL in the server.xml file and restarted. Got an error about no credentials, so added user and password properties to the URL. Nope, no luck. Never did figure this one out, but I had Pat pull the VM inside the firewall and after some thrash it worked. Well, it sort of worked ... sigh. It turns out I had downloaded the standard version instead of the enterprise version. I need to redo this work ... grrr. ## (/) I deleted all the tables in the Jira_Temp database and removed the /data/jira3135/indexes directory (and recreated). ## (/) I downloaded the enterprise version of the 3.13.5 server. I made a copy in the /opt directory and unzipped and untarred the file. ## (/) I went back to crowd and edited the application to change the properties to: ### URL: http://bugs.shore.mbari.org:8080 ### IP: 134.89.12.31 ### Name: jira3135 ### Password: (ask Kevin) :) ## (/) I then repeated the steps above to get the server up and running with the following differences: ### The server name is now bugs.shore.mbari.org ### The paths given above are a little different in that they no longer say "standard" but say "enterprise" ### I deleted the proxy pass as it seemed to have issues before and this is only temporary anyway. ## (/) I then browsed to http://bugs.shore.mbari.org:8080 ## (/) It took me to the start up page and at the top was the option to 'import your existing data'. Seemed too good not to try. I clicked on the link. It asked me for the backup file location and the location where the indexes would be stored. ## (/) I copied the XML zip file and the attachments tar file to the /data/original directory. ## (/) I created the /data/jira3135/indexes and used those directories ... it fired off the import and I waited. ## (/) I tailed the log file to watch the import. Holy crap, it worked!!! I could log in and everything! I copied the results from the log file here for posterity sake: {noformat} 2015-07-22 20:55:45,156 http-8080-Processor22 INFO [jira.action.admin.DataImport] Running data import 2015-07-22 20:55:45,179 http-8080-Processor22 INFO [jira.action.admin.DataImport] Importing data.. 2015-07-22 20:55:45,186 http-8080-Processor22 INFO [jira.action.admin.DataImport] Start parsing XML with SAX Parser 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] XML successfully parsed 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] Removing all entries from the database. 2015-07-22 20:56:24,593 http-8080-Processor22 INFO [jira.action.admin.DataImport] All entries removed. 2015-07-22 20:56:24,594 http-8080-Processor22 INFO [jira.action.admin.DataImport] Started storing 410414 Generic Values 2015-07-22 21:01:51,967 http-8080-Processor22 INFO [jira.action.admin.DataImport] Finished storing Generic Values 2015-07-22 21:01:52,329 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:52,361 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:54,683 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLink' to module 'jira.user.format:profile-link-user-format'. 2015-07-22 21:01:54,724 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullName' to module 'jira.user.format:full-name-user-format'. 2015-07-22 21:01:54,773 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkSearcher' to module 'jira.user.format:profile-link-searcher-user-format'. 2015-07-22 21:01:54,784 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkExternal' to module 'jira.user.format:profile-link-external-user-format'. 2015-07-22 21:01:54,795 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkActionHeader' to module 'jira.user.format:profile-link-action-header-user-format'. 2015-07-22 21:01:54,807 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullProfile' to module 'jira.user.format:full-profile-user-format'. 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/comments 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/issues 2015-07-22 21:01:55,641 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/plugins 2015-07-22 21:01:55,867 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:01:55,871 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/issues does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:55,873 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/comments does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,033 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,257 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,889 http-8080-Processor22 ERROR [atlassian.jira.upgrade.ConsistencyCheckImpl] Attachments are turned on, but attachment path [/data/jira_3_12/attachments] invalid - disabling attachments 2015-07-22 21:02:13,904 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Detected that an upgrade is needed; existing data at build 299 2015-07-22 21:02:13,907 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Doing Upgrade... 2015-07-22 21:02:13,915 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value' succeeded 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 317 2015-07-22 21:02:13,944 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite filters - make each filter a favourite of its owner. 2015-07-22 21:02:17,822 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build319] Could not find author 'fpy' for filter with id '10040' 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite filters - make each filter a favourite of its owner.' succeeded 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 319 2015-07-22 21:02:17,995 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise Share Permissions. Move old shares to new shares. 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise Share Permissions. Move old shares to new shares.' succeeded 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 321 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Migrating the old JIRA UI colors to the new JIRA 3.13 colors 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build322] Custom color detected for jira.lf.menu.bgcolour : #336699 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Migrating the old JIRA UI colors to the new JIRA 3.13 colors' succeeded 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 322 2015-07-22 21:02:18,025 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite dashboards - make each dashboard a favourite of its owner. 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'cmcgann' for dashboard with id '10030' 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'fpy' for dashboard with id '10060' 2015-07-22 21:02:18,423 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'kanna' for dashboard with id '10040' 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite dashboards - make each dashboard a favourite of its owner.' succeeded 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 325 2015-07-22 21:02:18,625 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Reindexing all data in JIRA to include Favourites. 2015-07-22 21:02:18,648 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All starting... 2015-07-22 21:02:18,650 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 0% complete. Current index: Issue 2015-07-22 21:02:18,654 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:02:18,809 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 1% complete. Current index: Issue 2015-07-22 21:02:18,855 indexerPool-2-thread-10 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 2% complete. Current index: Issue 2015-07-22 21:02:18,899 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 3% complete. Current index: Issue 2015-07-22 21:02:18,945 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 4% complete. Current index: Issue 2015-07-22 21:02:19,012 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 5% complete. Current index: Issue . . . 2015-07-22 21:02:26,164 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 95% complete. Current index: Issue 2015-07-22 21:02:26,232 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 96% complete. Current index: Issue 2015-07-22 21:02:26,316 indexerPool-2-thread-9 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 97% complete. Current index: Issue 2015-07-22 21:02:26,771 indexerPool-2-thread-3 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: Issue 2015-07-22 21:02:27,261 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 8607ms. Indexer: DefaultIndexManager: paths: [/data/jira3135/indexes/issues, /data/jira3135/indexes/comments] 2015-07-22 21:02:27,263 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: SearchRequest 2015-07-22 21:02:27,268 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,293 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: SearchRequest 2015-07-22 21:02:27,308 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: PortalPage 2015-07-22 21:02:27,312 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,377 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: PortalPage 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 115ms. Indexer: SharedEntityIndexManager: paths: [/data/jira3135/indexes/entities/portalpage, /data/jira3135/indexes/entities/searchrequest] 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All complete. Total time: 8722ms. 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Reindexing all data in JIRA to include Favourites.' succeeded 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 326 2015-07-22 21:02:27,397 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade succeeded! Setting data build number to 360 2015-07-22 21:02:27,469 JiraQuartzScheduler_Worker-0 WARN [service.services.export.ExportService] Backup directory /data/jira_3_12/backup does not exist {noformat} {warning:title=Paths} It appears that the upgraded JIRA will still look for the attachments and the backup locations in the original places. So I created /data/jira_3_12/backup and untarred the original attachments to /data/jira_3_12 and then everything worked (including attachements) in the new JIRA. {warning} ## (/) I then used the upgraded JIRA to generate a new XML backup and stored it in /data/original/3.13.5 along with another tar of the files in /data/jira_3_12/attachments. ## (/) I then shutdown the JIRA server. *I should be ready to move on to version 4 upgrade WHEW* ## So, before moving on, I decided that it would be a really good idea to spin up a new Crowd instance to get rid of the :8443 in the URL and to move off of RedHat per IS requests. I have a ticket in for a new VM and a new database to try to get this going. I am waiting on that before moving on. ## (/) Pat created the VM and Neil created the database. ## (/) I logged into auth.mbari.org (name of the VM) and downloaded crowd which I unzipped to the /opt directory ## (/) I then created a /data/crowd directory and gave my account permissions on it and then edited the /opt/atlassian..../crowd-webapp/WEB-INF/classes/crowd-init.properties file to set that as the crowd home directory. ## (/) The instructions say to download the JDBC driver, but they already have JTDS 1.2.7 in the download so I did not do anything. ## (/) You have to manually connect up CrowdID to a database as they setup wizard does not currently do this. ### (/) They say to download the driver, but again 1.2.7 was there so I did nothing. ### (/) I edited the /opt/atlassian.../apache-tomcat/conf/Catalina/localhost/openidserver.xml to look like: {noformat} {noformat} ### (/) I edited the /opt/atlassian.../build.properties files to look like: {noformat} # Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See https://confluence.atlassian.com/display/CROWD/Connecting+Crowd+to+a+Database hibernate.dialect=org.hibernate.dialect.SQLServerDialect # The Hibernate transaction factory to use. See https://confluence.atlassian.com/display/CROWD/Configuring+Crowd hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory # The http port you wish to run crowd from, ie: http://localhost:8095/crowd crowd.tomcat.connector.port=8095 # Tomcat requires a unique port for shutdown crowd.tomcat.shutdown.port=8020 # Crowd context root crowd.url=http://localhost:8095/crowd # Demo context root demo.url=http://localhost:8095/demo # OpenID server context root openidserver.url=http://localhost:8095/openidserver {noformat} ### (/) I then ran the build.sh script in the root of /opt/atlassian... ## (/) I fired up crowd using the /opt/atlassian.../start_crowd.sh script ## (/) I then went to http://auth.mbari.org:8095/crowd to kick off the start up wizard ## (/) I grabbed a new eval license from my account on atlassian and pasted into the license page. ## (/) I selected "New install" on the next page. ## (/) I configured the JDBC connection using this connection URL with user DB_Collaboration {noformat} jdbc:jtds:sqlserver://dione.mbari.org:51001/Crowd;domain=SHORE;useNTLMv2=TRUE {noformat} ## (/) I left the "Options" as they came up {warning:title=Paths} Not sure if this is a problem, but because I started the set up using auth.mbari.org, it set the Base URL to http://auth.mbari.org:8095/crowd instead of localhost. Hope that is not a problem. We will see. {warning} ## (/) I configured the email connection using the settings from [here|https://wind.shore.mbari.org/is/howto/email/mbarimail/imap] and I used my network login (probably shouldn't be doing that ... not sure where it stores my password, but I am assuming in the DB). ## (/) For the local admin account, I created a user named 'crowdadm' so it would not clash with my LDAP account. See Kevin Gomes for password information. ## (/) I checked the OpenID server as an integrated application ## (/) It then took me to the login page and I logged in using the newly minted admin account. Seemed all is well so far. ## (/) I visited the openidserver URL as well and that seemed OK. ## (/) I decided to wait on configuring the MBARI LDAP directory until I got everything with SSL working. ## (/) Now the next step was to follow the directions to configure Crowd to run over SSL found [here|https://confluence.atlassian.com/display/CROWD/Configuring+Crowd+to+Work+with+SSL] ## (/) I shutdown crowd. Note that the stop script does not shutdown things correctly and I noticed the crowd app running as root. That should not be if I started as kgomes. Not sure what is up with that. ## (/) Now Joe had already configured SSL once, so I used his connector configuration in the server.xml file and so the final file looked like: {noformat} {noformat} ## (/) I then edited the /data/crowd/crowd.properties to look like: {noformat} #Sat Aug 01 09:05:15 PDT 2015 session.lastvalidation=session.lastvalidation session.tokenkey=session.tokenkey crowd.server.url=https\://localhost\:8443/crowd/services/ application.name=crowd http.timeout=30000 session.isauthenticated=session.isauthenticated application.login.url=https\://localhost\:8443/crowd/console/ session.validationinterval=0 application.password=Y1Xp3OorCmsOP4eruL1dmH {noformat} One thing to note here is that based on a comment from the SSL configuration page at atlassian (Steve's comment), you are supposed to leave all the host names the same. For example, if the file says localhost, leave it localhost. So this created a bit of a problem based on the fact that I had left the base URL pointing to auth.mbari.org in the wizard steps above. That step wrote auth.mbari.org to the /data/crowd/crowd.properties. All the other files reference localhost, so to be consistent, I changed auth.mbari.org to localhost in the /data/crowd/crowd.properties file. We will see if this works. ## (/) Per the instructions on the atlassian page (referenced above), I also edited the build.properties file and the /client/conf/crowd.properties files before I restarted and used the SSL URLs ## build.properties: {noformat} # Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See https://confluence.atlassian.com/display/CROWD/Connecting+Crowd+to+a+Database hibernate.dialect=org.hibernate.dialect.SQLServerDialect # The Hibernate transaction factory to use. See https://confluence.atlassian.com/display/CROWD/Configuring+Crowd hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory # The http port you wish to run crowd from, ie: http://localhost:8095/crowd crowd.tomcat.connector.port=8095 # Tomcat requires a unique port for shutdown crowd.tomcat.shutdown.port=8020 # Crowd context root crowd.url=https://localhost:8443/crowd # Demo context root demo.url=https://localhost:8443/demo # OpenID server context root openidserver.url=https://localhost:8443/openidserver {noformat} ## crowd.properties (client) {noformat} application.name crowd application.password password application.login.url https://localhost:8443/crowd/console/ crowd.server.url https://localhost:8443/crowd/services/ crowd.base.url https://localhost:8443/crowd/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 2 session.lastvalidation session.lastvalidation {noformat} ## (/) Although not stated, I am assuming you would need to run the build.sh script to push the build.properties changes to their proper places, so I did that. Note that before doing that, I know that it will clobber the server.xml changes I made, so I made a copy of that file and diff'd them after and then rolled the previous changes to the new server.xml file. Actually, amazingly enough, it seems to have done the connector entry correctly so I left it after running the build.sh script. ## (/) Crossed my fingers and then restarted crowd. I tailed the catalina.out file and did not see any stack traces so that is a good sign! ## (/) I visited https://auth.mbari.org:8443/crowd first. It could not find that page, but I suspect that is because I am browsing from the outside, so I tried just https://auth.mbari.org/crowd and got a service unavailable. I am suspecting that this is a combination of firewall and proxy pass and I will send this info to Joe. From what I can see on the crowd side, it seems like the server started cleanly, we just can't get to it. I tried to reach it from a browser on the machine itself too (through VNC) with the same service not available. ## (/) Here are the notes from Joe after he fixed it! Wooohooo! {noformat} Hey Kevin, Thanks for starting clean! I had to make a few adjustments. 1-I modified the server.xml file in /opt/atlassian-crowd-2.8.3/apache-tomcat/conf/server.xml so there are two connectors per the instructions on the Atlassian site. I have backed up this good server.xml file in /etc/temp/ if you want to browse it to see what I did. Of note is that I removed all the jargon referencing the types of ciphers available to simplify things for now. 2-I modified /data/crowd/crowd.properties to have crowd.server.url=https\://localhost\:8443/crowd/services/ application.login.url=https\://localhost\:8443/crowd/console/ But that would cause my login to error with an error saying it was unable to reach the authentication server. I scratched my head for a bit. When I revert the values to just using non-SSL and try to log in, I just get an "invalid login" (I don't know the crowdadm password). So I worked under the assumption that if I can configure SSL to get an "invalid login" when logging in then it would work when provided real credentials. So, I then changed /data/crowd/crowd.proprties to: crowd.server.url=https\://auth.mbari.org\:8443/crowd/services/ application.login.url=https\://auth.mbari.org\:8443/crowd/console/ And now when I try to log in with SSL it says "invalid login". Strange because all the other values I can find only show "localhost" .. in any case... Can you try to log in now? {noformat} ## (/) Next I moved on to configuring the connection to MBARI's LDAP server to enable our logins through Crowd and CrowdID ## (/) I clicked on "Add Directory" in crowd. ## (/) I selected "Connector" then clicked Next ## (/) I put ldap.shore.mbari.org as the name of the server ## (/) I selected "Use memberOf for group memberships" ## (/) I used "OU=AllUsers,DC=shore,DC=mbari,DC=org" for the Base DN ## (/) I used "CN=LDAPbind,OU=Special,OU=AllUsers,DC=shore,DC=mbari,DC=org" for the Username (talk to Pat Allen for password) ## (/) I tested the connection (button click) and it passed. ## (/) I de-selected all the capabilities of the connector as it is a ready only connector and then saved it. It synchronized correctly! ## (/) At first, I could not login using my MBARI credentials, but after going to the "crowd" application in crowd (logged in as the local admin), I had to add the LDAP directory and configure it to "Allow all to authenticate", then I was able to login. After this, the last step was to get this to run as a different user and lock down various directories. I went through the entire directory structure /opt/atlassian... and set up so that root owned all read-only locations and DB_Collaboration (account set up by IS) owned the other stuff. I also gave full ownership to the /data/crowd directory to DB_Collaboration so it could write there. Pat set up a script to start on boot and after a little tweaking, it now starts on boot. {warning:title=CrowdID log file} One thing that came up here was that when the crowdID application ran, it tried to write a log file to the location where the process was launched from (which is /opt/atlassian...). This is a bad thing and I figured out that I could change that location by changing the file /opt/atlassian-crowd-2.8.3/crowd-openidserver-webapp/WEB-INF/classes/log4j.properties and hardcoding the /data/crowd/logs/atlassian-crowd-openid-server.log and then restarted the application. {warning} ## (/) Another note is the when an application tried to use the OpenID application, it would get redirected to localhost. I changed the /opt/atlassian.../crowd-openidserver-webapp/WEB-INF/classes/crowd.properties file to look like: {noformat} #Sat Aug 01 10:03:18 PDT 2015 session.lastvalidation=session.lastvalidation session.tokenkey=session.tokenkey crowd.server.url=http\://localhost\:8095/crowd/services/ application.name=crowd-openid-server #application.login.url.template=http\://localhost\:8095/openidserver?returnToUrl\=${RETURN_TO_URL} application.login.url.template=https\://auth.mbari.org/openidserver?returnToUrl\=${RETURN_TO_URL} session.isauthenticated=session.isauthenticated #application.base.url=http\://localhost\:8095/openidserver application.base.url=https\://auth.mbari.org/openidserver #application.login.url=http\://localhost\:8095/openidserver application.login.url=https\://auth.mbari.org/openidserver session.validationinterval=0 application.password=password {noformat} and that seems to have fixed it. # (/) It is finally time to move on to the version 4 upgrade ... holy crap. I first went to the *new* crowd install (auth.mbari.org) and logged in as the crowdadm. # (/) I clicked on Applications, then on Add Application # (/) I selected JIRA from the Application type drop-down # (/) I entered jira445 as the username. Ask Kevin about the password. # (/) I used http://bugs.shore.mbari.org:8081 as the URL # (/) I used 134.89.12.31 as the IP address. # (/) I selected only the MBARI LDAP directory. # (/) Then I selected "Allow all users to authenticate" # (/) Then I clicked on "Add Application" # (/) I VNC'd into bugs.mbari.org. As it turns out, for Linux, there is an installer program to download. I downloaded the .bin for 64 bit Linux installer and moved it to the jira-upgrade directory. # (/) I chmod'd the file to make it executable and ran it. It gave me a warning about not being root, but I went ahead with it. # (/) It asked for the JIRA home and data directory, which I specified as /opt/jira4 and /data/jira445. # (/) For the ports, I specified 8180 and 8105 (HTTP and control respectively). It then extracted all the files and launched JIRA. It said if finished, so I opened a local browser to http://localhost:8180 which kicked off the start up wizard. # (/) I specified the external database using: ## solstice2.shore.mbari.org (server) ## 1433 (port) ## jira4 (database) ## DB_Collaboration (username) ## (password ask Kevin) ## dbo (schema) # But all this failed as it seems to just want to try and use the SQL server authentication instead of domain. I will have to do it manually. # (/) I stopped the server using the bin/stop-jira.sh script. # (/) I created and edited /data/jira445/dbconfig.xml and made it look like the following: {noformat} ?xml version="1.0" encoding="UTF-8"?> defaultDS default mssql jiraschema jdbc:jtds:sqlserver://solstice2.shore.mbari.org:1433/Jira4;domain=SHORE;useNTLMv2=true net.sourceforge.jtds.jdbc.Driver DB_Collaboration (ask Kevin) 15 {noformat} # (/) I then started it again using bin/start-jira.sh and tailed the catalina.out file. Got a bunch of errors related to the schema 'jiraschema', I edited the file and changed the schema to 'dbo' and restarted. That seemed to do it. There was one stack trace for some iCal plugin, but looks OK other than that. # I browsed back to localhost:8180 and the wizard moved to step 2. There was an option to import existing data bit without the crowd connection, I thought I should set it up manually, connect to crowd, then import. I generated an evaluation license, called the app "MBARI JIRA4" and change the server in the url to bugs.shore.mbari.org # For the admin, I created an account called 'jiraadm' (ask Kevin for password). # Since this is a temporary system, I left the email system disabled. # I logged in as jiraadm, went to Administration, then Users, then clicked on Add Directory and chose Atlassian Crowd. Note that I had to set the server URL to http://auth.mbari.org:8095/crowd or I would have had to configure all this SSL crap that I did not want to do for this temporary install. # It tested successfully, I clicked Save and it went through a 13 second sync, whew! # I then went to System->Import and Export->Restore System # I copied the jira-upgrade-3.13.5.zip file from the previous version export into /data/jira445/import and then entered that file name along with the new evaluation license again. # I worked through progress bar after I clicked on Restore (it took a really long time). # I then stopped, restarted and tailed the log file. # I am thinking now I should have put the attachments in the import attachments directory, but I am hoping I can just copy them to the data/attachments directory. # UG! I got some error during the import. The exception read: "JIRA is unable to migrat the User Directory configuration because external users exist but the osuser.xml file is not available". It then gave me a link to a doc that talked about making the old user files available before the upgrade ... crap. So I needed to copy the osuser.xml and crowd.properties file from atlassian-jira/WEB-INF/classes directory on the old install to the same directory on the new install ... sigh. This means I am going to blow away everything and start over. # I shutdown jira4 # I dropped all things in the database and deleted all content in the /data/jira445 directory (except for the dbconfig.xml file). # I also removed the temp, logs (actually you have to leave the directory, just clear the files) and the work/Catalina/localhost directories from the jira installation. # I then copied the osuser.xml and the crowd.properties files from the 3.13.5 install to the 4 install. # I edited the crowd.properties file in hopes that I could point it to the new crowd install on auth.mbari.org and it would work, but we will see. # I then started jira and tailed the log file. # All looked OK (other than iCal plugin stack trace again), so I went to localhost:8180 and got step 2 of the wizard. I used the same info as before. # I logged in as the local admin account and it looks like the system picked up the crowd connection, but lets see what server it used! Hey it used the one I edited into the file! Sweet ... now let's see if the import works. # I copied the 3.13.5 zip file to the import directory again and this time, I untarred the attachments into the import/attachments directory. # I kicked off the restore as before and it worked through it fine. # Shutdown and restarted system, tailing the log file and then went to localhost:8180 # I can see issues (before logging in) and it all looks good!! The attachments did not move over from the import directory, so I copied the tar file from /data/jira445/import to /data/jira445/data and then untarred it there, then removed the tar file and the import zip file from the import directory. # Now I will try to login using my MBARI account and OMG it actually worked!!! (it even gave my kgomes account Admin privs) # I then performed an export and copied those file to the /data/backups/4.4.5 directory (also created a TAR of the attachments and put there too). # Now on to version 5! # OK, so something strange is happening. After the imports, the server ID goes back to the one that is on our current production server, which must mean it is using our current license key (which does not match the server ID, BTW). Oh well, I will press on! # I created a /data/jira5211 directory as well as a /opt/jira5 directory. Knowing what I know now and reading through the install instructions, it appears that I need to create a dbconfig.xml file manually, so I did that using: {noformat} defaultDS default mssql dbo jdbc:jtds:sqlserver://solstice2.shore.mbari.org:1433/Jira5;domain=SHORE;useNTLMv2=true net.sourceforge.jtds.jdbc.Driver DB_Collaboration (ask Kevin) 20 20 30000 20 true 300 select 1 60000 300000 true false {noformat} # I then changed the mode to executable on the installer download and ran that. # I had to choose a "custom install" this time through, but the properties were similar after that (ports I used were 8280 and 8205) # I then browsed to localhost:8280 # I dropped me to a wizard where I define the title as "MBARI JIRA5", and changed host to bugs.shore.mbari.org (from localhost) # This license was a little different in that is just asked for my Atlassian username and password and fetched a new license for me. # For the admin account, I used the same 'jiraadm' account # Left email notification disabled. # I created a new application in crowd for JIRA 5 and used same account info as for 4. # In JIRA, I went to Administration->Users->User Directories and then added a directory as I had done before. # All went well and the sync happened. # I then went to Administration->System->Import and Export->Restore System # I copied the backup of 4.4.5 to the /data/jira5211/import directory and then specified that file name. I did not specify a license as it seems to use the old one and it said so in the text below the box. # Clicked on restore and while it was restoring, I untarred the attachments to the /data/jira5211/data directory # After the restore, I shutdown and restarted JIRA tailing the log file. # Browsed to localhost:8280 and ... success! I see issues before logging in and ... my MBARI login worked, I was admin and all is good!!!!]]> 27558200 27590966 4.4: [https://confluence.atlassian.com/display/JIRA044/Migrating+JIRA+to+Another+Server] ## The JIRA configuration tool: [https://confluence.atlassian.com/display/JIRA044/Using+the+JIRA+Configuration+Tool] h5. Steps # (/) Create new VM named bugs.mbari.org in the DMZ # (/) Have Neil create database Jira_Temp on solstice2.shore.mbari.org # (/) Have Neil create database Jira on solstice2.shore.mbari.org # (/) Have Pat install Java 7 on bugs.shore.mbari.org # (/) Have Pete plumb holes through firewall so processes on bugs.mbari.org can get to Solstice2 # (/) Have Pat create DB_Collaboration account on bugs so it can run JIRA under that account and it can connect to solstice2 using that NT Domain account. # (/) Upgrade license on Atlassian site # (/) Log into bugs.shore.mbari.org # (/) Download 3.13.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 4.4.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 5.2.11 standalone Linux 64 bit tar.gz (not sure this version is necessary, but at least I have it) # (/) Unzip and untar the file to /opt # (/) Download latest JIRA (6.4.7 as of this writing). # (/) Unzip and untar it to /opt # Performed Test Upgrade ## (/) In order to export the current stuff in JIRA, I had to shut off access so people could not change the data while I was backing it up. ## (/) I ssh'd to oceana.mbari.org as root and edited the /opt/jira/conf/server.xml file and commented out the Connector section that had the port of 8010 to shut it off from the normal serving route. ## (/) I uncommented the 8082 port connector and the 8443 port connector so that I could still get to the server. ## (/) I stopped and started the JIRA server and in the log file I got a "keystore was tampered with..." which is not surprising. ## (/) I could then browser over to http://oceana.mbari.org:8082/jira ## (/) Then through the Administration console, I did an XML backup ## (/) I then created a tar of all the attachments in the /data/jira_3_12/attachments directory ## (/) I moved both the XML and tar files to the /root/jira-upgrade directory ## (/) I then reversed the changes to the server.xml file and shut down JIRA ## (/) I left it down during the next steps in case it went so well, I could just point people to the new server (yeah, right). ## (/) I then browsed to the crowd server on oceana and add a new application using: ### URL: http://bugs.mbari.org/jira3135 ### IP: 134.89.2.29 ### Name: JIRA3135 ### Password: (ask Kevin) :) ## (/) On bugs, I made a copy of the JIRA 3.13.5 download in the /opt directory and unzipped and untarred it. ## (/) In order to configure the crowd connection I did the following: ### (/) I scp'd the /opt/crowd/client/crowd-integration-client-1.6.jar file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I removed the existing 1.6.1 crowd client jar from the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I scp'd the /opt/crowd/client/conf/crowd.properties file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I scp'd the /opt/crowd/client/conf/crowd-ehcache.xml file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I edited the crowd.properties file on bugs to look like: {noformat} application.name JIRA3135 application.password (ask Kevin) application.login.url http://oceana.mbari.org:8095/crowd/console/ crowd.server.url http://oceana.mbari.org:8095/crowd/services/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 0 session.lastvalidation session.lastvalidation {noformat} ### (/) I edited the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/osuser.xml file to comment out the current authentication mechanism and then uncomment the crowd one. ## (/) I then edited the /opt/atlassian-jira-standalone-3.13.5/conf/server/xml file and configured the database connection to the Jira_Temp database on Solstice2. I looked like this: {noformat} {noformat} ## (/) Edit the /opt/atlassian/jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/entityengine.xml and changed it from 'hsql' to 'mssql' and delete the line with "PUBLIC" in it per the instructions in the comments in that file. ## (/) I edited the /etc/httpd/conf/httpd.conf file and created a proxy pass at the bottom of the file to point a normal URL to the default port 8080 for JIRA: {noformat} # Proxy Pass for JIRA ProxyPass http://bugs.mbari.org:8080 ProxyPassReverse http://bugs.mbari.org:8080 {noformat} ## (/) I restarted Apache ## (/) I scp'd the jtds driver from oceana to the /opt/atlassian-jira-standalone-3.13.5/common/lib directory (you could down from the internet) ## (/) I then went to the /opt/atlassian-jira-standalone-3.13.5/ directory and ran './bin/startup.sh'. From the log file, I could tell things were hanging. After some troubleshooting I am wondering if the local firewall is preventing the application to get access to the database on solstice2. I can telnet to port 1433, but I can't browse to the base http://bugs.mbari.org from anywhere but the local web browser. I have submitted a ticket. ## (/) I restarted the old JIRA with my hopes dashed :(. ## (/) Pat disabled the firewall on bugs.mbari.org but it still hung trying to connect to solstice2.shore.mbari.org. That is really, really perplexing. Neil mentioned that solstice2 is using Kerberos and solstice is not. Checking with the JTDS docs, version 1.3.1 of the driver added kerberos support, so I downloaded that driver and added the 'userKerberos=true' property to the URL in the server.xml file and restarted. Got an error about no credentials, so added user and password properties to the URL. Nope, no luck. Never did figure this one out, but I had Pat pull the VM inside the firewall and after some thrash it worked. Well, it sort of worked ... sigh. It turns out I had downloaded the standard version instead of the enterprise version. I need to redo this work ... grrr. ## (/) I deleted all the tables in the Jira_Temp database and removed the /data/jira3135/indexes directory (and recreated). ## (/) I downloaded the enterprise version of the 3.13.5 server. I made a copy in the /opt directory and unzipped and untarred the file. ## (/) I went back to crowd and edited the application to change the properties to: ### URL: http://bugs.shore.mbari.org:8080 ### IP: 134.89.12.31 ### Name: jira3135 ### Password: (ask Kevin) :) ## (/) I then repeated the steps above to get the server up and running with the following differences: ### The server name is now bugs.shore.mbari.org ### The paths given above are a little different in that they no longer say "standard" but say "enterprise" ### I deleted the proxy pass as it seemed to have issues before and this is only temporary anyway. ## (/) I then browsed to http://bugs.shore.mbari.org:8080 ## (/) It took me to the start up page and at the top was the option to 'import your existing data'. Seemed too good not to try. I clicked on the link. It asked me for the backup file location and the location where the indexes would be stored. ## (/) I copied the XML zip file and the attachments tar file to the /data/original directory. ## (/) I created the /data/jira3135/indexes and used those directories ... it fired off the import and I waited. ## (/) I tailed the log file to watch the import. Holy crap, it worked!!! I could log in and everything! I copied the results from the log file here for posterity sake: {noformat} 2015-07-22 20:55:45,156 http-8080-Processor22 INFO [jira.action.admin.DataImport] Running data import 2015-07-22 20:55:45,179 http-8080-Processor22 INFO [jira.action.admin.DataImport] Importing data.. 2015-07-22 20:55:45,186 http-8080-Processor22 INFO [jira.action.admin.DataImport] Start parsing XML with SAX Parser 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] XML successfully parsed 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] Removing all entries from the database. 2015-07-22 20:56:24,593 http-8080-Processor22 INFO [jira.action.admin.DataImport] All entries removed. 2015-07-22 20:56:24,594 http-8080-Processor22 INFO [jira.action.admin.DataImport] Started storing 410414 Generic Values 2015-07-22 21:01:51,967 http-8080-Processor22 INFO [jira.action.admin.DataImport] Finished storing Generic Values 2015-07-22 21:01:52,329 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:52,361 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:54,683 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLink' to module 'jira.user.format:profile-link-user-format'. 2015-07-22 21:01:54,724 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullName' to module 'jira.user.format:full-name-user-format'. 2015-07-22 21:01:54,773 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkSearcher' to module 'jira.user.format:profile-link-searcher-user-format'. 2015-07-22 21:01:54,784 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkExternal' to module 'jira.user.format:profile-link-external-user-format'. 2015-07-22 21:01:54,795 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkActionHeader' to module 'jira.user.format:profile-link-action-header-user-format'. 2015-07-22 21:01:54,807 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullProfile' to module 'jira.user.format:full-profile-user-format'. 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/comments 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/issues 2015-07-22 21:01:55,641 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/plugins 2015-07-22 21:01:55,867 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:01:55,871 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/issues does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:55,873 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/comments does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,033 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,257 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,889 http-8080-Processor22 ERROR [atlassian.jira.upgrade.ConsistencyCheckImpl] Attachments are turned on, but attachment path [/data/jira_3_12/attachments] invalid - disabling attachments 2015-07-22 21:02:13,904 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Detected that an upgrade is needed; existing data at build 299 2015-07-22 21:02:13,907 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Doing Upgrade... 2015-07-22 21:02:13,915 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value' succeeded 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 317 2015-07-22 21:02:13,944 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite filters - make each filter a favourite of its owner. 2015-07-22 21:02:17,822 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build319] Could not find author 'fpy' for filter with id '10040' 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite filters - make each filter a favourite of its owner.' succeeded 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 319 2015-07-22 21:02:17,995 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise Share Permissions. Move old shares to new shares. 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise Share Permissions. Move old shares to new shares.' succeeded 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 321 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Migrating the old JIRA UI colors to the new JIRA 3.13 colors 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build322] Custom color detected for jira.lf.menu.bgcolour : #336699 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Migrating the old JIRA UI colors to the new JIRA 3.13 colors' succeeded 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 322 2015-07-22 21:02:18,025 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite dashboards - make each dashboard a favourite of its owner. 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'cmcgann' for dashboard with id '10030' 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'fpy' for dashboard with id '10060' 2015-07-22 21:02:18,423 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'kanna' for dashboard with id '10040' 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite dashboards - make each dashboard a favourite of its owner.' succeeded 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 325 2015-07-22 21:02:18,625 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Reindexing all data in JIRA to include Favourites. 2015-07-22 21:02:18,648 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All starting... 2015-07-22 21:02:18,650 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 0% complete. Current index: Issue 2015-07-22 21:02:18,654 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:02:18,809 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 1% complete. Current index: Issue 2015-07-22 21:02:18,855 indexerPool-2-thread-10 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 2% complete. Current index: Issue 2015-07-22 21:02:18,899 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 3% complete. Current index: Issue 2015-07-22 21:02:18,945 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 4% complete. Current index: Issue 2015-07-22 21:02:19,012 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 5% complete. Current index: Issue . . . 2015-07-22 21:02:26,164 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 95% complete. Current index: Issue 2015-07-22 21:02:26,232 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 96% complete. Current index: Issue 2015-07-22 21:02:26,316 indexerPool-2-thread-9 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 97% complete. Current index: Issue 2015-07-22 21:02:26,771 indexerPool-2-thread-3 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: Issue 2015-07-22 21:02:27,261 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 8607ms. Indexer: DefaultIndexManager: paths: [/data/jira3135/indexes/issues, /data/jira3135/indexes/comments] 2015-07-22 21:02:27,263 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: SearchRequest 2015-07-22 21:02:27,268 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,293 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: SearchRequest 2015-07-22 21:02:27,308 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: PortalPage 2015-07-22 21:02:27,312 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,377 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: PortalPage 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 115ms. Indexer: SharedEntityIndexManager: paths: [/data/jira3135/indexes/entities/portalpage, /data/jira3135/indexes/entities/searchrequest] 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All complete. Total time: 8722ms. 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Reindexing all data in JIRA to include Favourites.' succeeded 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 326 2015-07-22 21:02:27,397 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade succeeded! Setting data build number to 360 2015-07-22 21:02:27,469 JiraQuartzScheduler_Worker-0 WARN [service.services.export.ExportService] Backup directory /data/jira_3_12/backup does not exist {noformat} {warning:title=Paths} It appears that the upgraded JIRA will still look for the attachments and the backup locations in the original places. So I created /data/jira_3_12/backup and untarred the original attachments to /data/jira_3_12 and then everything worked (including attachements) in the new JIRA. {warning} ## (/) I then used the upgraded JIRA to generate a new XML backup and stored it in /data/original/3.13.5 along with another tar of the files in /data/jira_3_12/attachments. ## (/) I then shutdown the JIRA server. *I should be ready to move on to version 4 upgrade WHEW* ## So, before moving on, I decided that it would be a really good idea to spin up a new Crowd instance to get rid of the :8443 in the URL and to move off of RedHat per IS requests. I have a ticket in for a new VM and a new database to try to get this going. I am waiting on that before moving on. ## (/) Pat created the VM and Neil created the database. ## (/) I logged into auth.mbari.org (name of the VM) and downloaded crowd which I unzipped to the /opt directory ## (/) I then created a /data/crowd directory and gave my account permissions on it and then edited the /opt/atlassian..../crowd-webapp/WEB-INF/classes/crowd-init.properties file to set that as the crowd home directory. ## (/) The instructions say to download the JDBC driver, but they already have JTDS 1.2.7 in the download so I did not do anything. ## (/) You have to manually connect up CrowdID to a database as they setup wizard does not currently do this. ### (/) They say to download the driver, but again 1.2.7 was there so I did nothing. ### (/) I edited the /opt/atlassian.../apache-tomcat/conf/Catalina/localhost/openidserver.xml to look like: {noformat} {noformat} ### (/) I edited the /opt/atlassian.../build.properties files to look like: {noformat} # Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See https://confluence.atlassian.com/display/CROWD/Connecting+Crowd+to+a+Database hibernate.dialect=org.hibernate.dialect.SQLServerDialect # The Hibernate transaction factory to use. See https://confluence.atlassian.com/display/CROWD/Configuring+Crowd hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory # The http port you wish to run crowd from, ie: http://localhost:8095/crowd crowd.tomcat.connector.port=8095 # Tomcat requires a unique port for shutdown crowd.tomcat.shutdown.port=8020 # Crowd context root crowd.url=http://localhost:8095/crowd # Demo context root demo.url=http://localhost:8095/demo # OpenID server context root openidserver.url=http://localhost:8095/openidserver {noformat} ### (/) I then ran the build.sh script in the root of /opt/atlassian... ## (/) I fired up crowd using the /opt/atlassian.../start_crowd.sh script ## (/) I then went to http://auth.mbari.org:8095/crowd to kick off the start up wizard ## (/) I grabbed a new eval license from my account on atlassian and pasted into the license page. ## (/) I selected "New install" on the next page. ## (/) I configured the JDBC connection using this connection URL with user DB_Collaboration {noformat} jdbc:jtds:sqlserver://dione.mbari.org:51001/Crowd;domain=SHORE;useNTLMv2=TRUE {noformat} ## (/) I left the "Options" as they came up {warning:title=Paths} Not sure if this is a problem, but because I started the set up using auth.mbari.org, it set the Base URL to http://auth.mbari.org:8095/crowd instead of localhost. Hope that is not a problem. We will see. {warning} ## (/) I configured the email connection using the settings from [here|https://wind.shore.mbari.org/is/howto/email/mbarimail/imap] and I used my network login (probably shouldn't be doing that ... not sure where it stores my password, but I am assuming in the DB). ## (/) For the local admin account, I created a user named 'crowdadm' so it would not clash with my LDAP account. See Kevin Gomes for password information. ## (/) I checked the OpenID server as an integrated application ## (/) It then took me to the login page and I logged in using the newly minted admin account. Seemed all is well so far. ## (/) I visited the openidserver URL as well and that seemed OK. ## (/) I decided to wait on configuring the MBARI LDAP directory until I got everything with SSL working. ## (/) Now the next step was to follow the directions to configure Crowd to run over SSL found [here|https://confluence.atlassian.com/display/CROWD/Configuring+Crowd+to+Work+with+SSL] ## (/) I shutdown crowd. Note that the stop script does not shutdown things correctly and I noticed the crowd app running as root. That should not be if I started as kgomes. Not sure what is up with that. ## (/) Now Joe had already configured SSL once, so I used his connector configuration in the server.xml file and so the final file looked like: {noformat} {noformat} ## (/) I then edited the /data/crowd/crowd.properties to look like: {noformat} #Sat Aug 01 09:05:15 PDT 2015 session.lastvalidation=session.lastvalidation session.tokenkey=session.tokenkey crowd.server.url=https\://localhost\:8443/crowd/services/ application.name=crowd http.timeout=30000 session.isauthenticated=session.isauthenticated application.login.url=https\://localhost\:8443/crowd/console/ session.validationinterval=0 application.password=Y1Xp3OorCmsOP4eruL1dmH {noformat} One thing to note here is that based on a comment from the SSL configuration page at atlassian (Steve's comment), you are supposed to leave all the host names the same. For example, if the file says localhost, leave it localhost. So this created a bit of a problem based on the fact that I had left the base URL pointing to auth.mbari.org in the wizard steps above. That step wrote auth.mbari.org to the /data/crowd/crowd.properties. All the other files reference localhost, so to be consistent, I changed auth.mbari.org to localhost in the /data/crowd/crowd.properties file. We will see if this works. ## (/) Per the instructions on the atlassian page (referenced above), I also edited the build.properties file and the /client/conf/crowd.properties files before I restarted and used the SSL URLs ## build.properties: {noformat} # Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See https://confluence.atlassian.com/display/CROWD/Connecting+Crowd+to+a+Database hibernate.dialect=org.hibernate.dialect.SQLServerDialect # The Hibernate transaction factory to use. See https://confluence.atlassian.com/display/CROWD/Configuring+Crowd hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory # The http port you wish to run crowd from, ie: http://localhost:8095/crowd crowd.tomcat.connector.port=8095 # Tomcat requires a unique port for shutdown crowd.tomcat.shutdown.port=8020 # Crowd context root crowd.url=https://localhost:8443/crowd # Demo context root demo.url=https://localhost:8443/demo # OpenID server context root openidserver.url=https://localhost:8443/openidserver {noformat} ## crowd.properties (client) {noformat} application.name crowd application.password password application.login.url https://localhost:8443/crowd/console/ crowd.server.url https://localhost:8443/crowd/services/ crowd.base.url https://localhost:8443/crowd/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 2 session.lastvalidation session.lastvalidation {noformat} ## (/) Although not stated, I am assuming you would need to run the build.sh script to push the build.properties changes to their proper places, so I did that. Note that before doing that, I know that it will clobber the server.xml changes I made, so I made a copy of that file and diff'd them after and then rolled the previous changes to the new server.xml file. Actually, amazingly enough, it seems to have done the connector entry correctly so I left it after running the build.sh script. ## (/) Crossed my fingers and then restarted crowd. I tailed the catalina.out file and did not see any stack traces so that is a good sign! ## (/) I visited https://auth.mbari.org:8443/crowd first. It could not find that page, but I suspect that is because I am browsing from the outside, so I tried just https://auth.mbari.org/crowd and got a service unavailable. I am suspecting that this is a combination of firewall and proxy pass and I will send this info to Joe. From what I can see on the crowd side, it seems like the server started cleanly, we just can't get to it. I tried to reach it from a browser on the machine itself too (through VNC) with the same service not available. ## (/) Here are the notes from Joe after he fixed it! Wooohooo! {noformat} Hey Kevin, Thanks for starting clean! I had to make a few adjustments. 1-I modified the server.xml file in /opt/atlassian-crowd-2.8.3/apache-tomcat/conf/server.xml so there are two connectors per the instructions on the Atlassian site. I have backed up this good server.xml file in /etc/temp/ if you want to browse it to see what I did. Of note is that I removed all the jargon referencing the types of ciphers available to simplify things for now. 2-I modified /data/crowd/crowd.properties to have crowd.server.url=https\://localhost\:8443/crowd/services/ application.login.url=https\://localhost\:8443/crowd/console/ But that would cause my login to error with an error saying it was unable to reach the authentication server. I scratched my head for a bit. When I revert the values to just using non-SSL and try to log in, I just get an "invalid login" (I don't know the crowdadm password). So I worked under the assumption that if I can configure SSL to get an "invalid login" when logging in then it would work when provided real credentials. So, I then changed /data/crowd/crowd.proprties to: crowd.server.url=https\://auth.mbari.org\:8443/crowd/services/ application.login.url=https\://auth.mbari.org\:8443/crowd/console/ And now when I try to log in with SSL it says "invalid login". Strange because all the other values I can find only show "localhost" .. in any case... Can you try to log in now? {noformat} ## (/) Next I moved on to configuring the connection to MBARI's LDAP server to enable our logins through Crowd and CrowdID ## (/) I clicked on "Add Directory" in crowd. ## (/) I selected "Connector" then clicked Next ## (/) I put ldap.shore.mbari.org as the name of the server ## (/) I selected "Use memberOf for group memberships" ## (/) I used "OU=AllUsers,DC=shore,DC=mbari,DC=org" for the Base DN ## (/) I used "CN=LDAPbind,OU=Special,OU=AllUsers,DC=shore,DC=mbari,DC=org" for the Username (talk to Pat Allen for password) ## (/) I tested the connection (button click) and it passed. ## (/) I de-selected all the capabilities of the connector as it is a ready only connector and then saved it. It synchronized correctly! ## (/) At first, I could not login using my MBARI credentials, but after going to the "crowd" application in crowd (logged in as the local admin), I had to add the LDAP directory and configure it to "Allow all to authenticate", then I was able to login. After this, the last step was to get this to run as a different user and lock down various directories. I went through the entire directory structure /opt/atlassian... and set up so that root owned all read-only locations and DB_Collaboration (account set up by IS) owned the other stuff. I also gave full ownership to the /data/crowd directory to DB_Collaboration so it could write there. Pat set up a script to start on boot and after a little tweaking, it now starts on boot. {warning:title=CrowdID log file} One thing that came up here was that when the crowdID application ran, it tried to write a log file to the location where the process was launched from (which is /opt/atlassian...). This is a bad thing and I figured out that I could change that location by changing the file /opt/atlassian-crowd-2.8.3/crowd-openidserver-webapp/WEB-INF/classes/log4j.properties and hardcoding the /data/crowd/logs/atlassian-crowd-openid-server.log and then restarted the application. {warning} ## (/) Another note is the when an application tried to use the OpenID application, it would get redirected to localhost. I changed the /opt/atlassian.../crowd-openidserver-webapp/WEB-INF/classes/crowd.properties file to look like: {noformat} #Sat Aug 01 10:03:18 PDT 2015 session.lastvalidation=session.lastvalidation session.tokenkey=session.tokenkey crowd.server.url=http\://localhost\:8095/crowd/services/ application.name=crowd-openid-server #application.login.url.template=http\://localhost\:8095/openidserver?returnToUrl\=${RETURN_TO_URL} application.login.url.template=https\://auth.mbari.org/openidserver?returnToUrl\=${RETURN_TO_URL} session.isauthenticated=session.isauthenticated #application.base.url=http\://localhost\:8095/openidserver application.base.url=https\://auth.mbari.org/openidserver #application.login.url=http\://localhost\:8095/openidserver application.login.url=https\://auth.mbari.org/openidserver session.validationinterval=0 application.password=password {noformat} and that seems to have fixed it. # (/) It is finally time to move on to the version 4 upgrade ... holy crap. I first went to the *new* crowd install (auth.mbari.org) and logged in as the crowdadm. # (/) I clicked on Applications, then on Add Application # (/) I selected JIRA from the Application type drop-down # (/) I entered jira445 as the username. Ask Kevin about the password. # (/) I used http://bugs.shore.mbari.org:8081 as the URL # (/) I used 134.89.12.31 as the IP address. # (/) I selected only the MBARI LDAP directory. # (/) Then I selected "Allow all users to authenticate" # (/) Then I clicked on "Add Application" # (/) I VNC'd into bugs.mbari.org. As it turns out, for Linux, there is an installer program to download. I downloaded the .bin for 64 bit Linux installer and moved it to the jira-upgrade directory. # (/) I chmod'd the file to make it executable and ran it. It gave me a warning about not being root, but I went ahead with it. # (/) It asked for the JIRA home and data directory, which I specified as /opt/jira4 and /data/jira445. # (/) For the ports, I specified 8180 and 8105 (HTTP and control respectively). It then extracted all the files and launched JIRA. It said if finished, so I opened a local browser to http://localhost:8180 which kicked off the start up wizard. # (/) I specified the external database using: ## solstice2.shore.mbari.org (server) ## 1433 (port) ## jira4 (database) ## DB_Collaboration (username) ## (password ask Kevin) ## dbo (schema) # But all this failed as it seems to just want to try and use the SQL server authentication instead of domain. I will have to do it manually. # (/) I stopped the server using the bin/stop-jira.sh script. # (/) I created and edited /data/jira445/dbconfig.xml and made it look like the following: {noformat} ?xml version="1.0" encoding="UTF-8"?> defaultDS default mssql jiraschema jdbc:jtds:sqlserver://solstice2.shore.mbari.org:1433/Jira4;domain=SHORE;useNTLMv2=true net.sourceforge.jtds.jdbc.Driver DB_Collaboration (ask Kevin) 15 {noformat} # (/) I then started it again using bin/start-jira.sh and tailed the catalina.out file. Got a bunch of errors related to the schema 'jiraschema', I edited the file and changed the schema to 'dbo' and restarted. That seemed to do it. There was one stack trace for some iCal plugin, but looks OK other than that. # I browsed back to localhost:8180 and the wizard moved to step 2. There was an option to import existing data bit without the crowd connection, I thought I should set it up manually, connect to crowd, then import. I generated an evaluation license, called the app "MBARI JIRA4" and change the server in the url to bugs.shore.mbari.org # For the admin, I created an account called 'jiraadm' (ask Kevin for password). # Since this is a temporary system, I left the email system disabled. # I logged in as jiraadm, went to Administration, then Users, then clicked on Add Directory and chose Atlassian Crowd. Note that I had to set the server URL to http://auth.mbari.org:8095/crowd or I would have had to configure all this SSL crap that I did not want to do for this temporary install. # It tested successfully, I clicked Save and it went through a 13 second sync, whew! # I then went to System->Import and Export->Restore System # I copied the jira-upgrade-3.13.5.zip file from the previous version export into /data/jira445/import and then entered that file name along with the new evaluation license again. # I worked through progress bar after I clicked on Restore (it took a really long time). # I then stopped, restarted and tailed the log file. # I am thinking now I should have put the attachments in the import attachments directory, but I am hoping I can just copy them to the data/attachments directory. # UG! I got some error during the import. The exception read: "JIRA is unable to migrat the User Directory configuration because external users exist but the osuser.xml file is not available". It then gave me a link to a doc that talked about making the old user files available before the upgrade ... crap. So I needed to copy the osuser.xml and crowd.properties file from atlassian-jira/WEB-INF/classes directory on the old install to the same directory on the new install ... sigh. This means I am going to blow away everything and start over. # I shutdown jira4 # I dropped all things in the database and deleted all content in the /data/jira445 directory (except for the dbconfig.xml file). # I also removed the temp, logs (actually you have to leave the directory, just clear the files) and the work/Catalina/localhost directories from the jira installation. # I then copied the osuser.xml and the crowd.properties files from the 3.13.5 install to the 4 install. # I edited the crowd.properties file in hopes that I could point it to the new crowd install on auth.mbari.org and it would work, but we will see. # I then started jira and tailed the log file. # All looked OK (other than iCal plugin stack trace again), so I went to localhost:8180 and got step 2 of the wizard. I used the same info as before. # I logged in as the local admin account and it looks like the system picked up the crowd connection, but lets see what server it used! Hey it used the one I edited into the file! Sweet ... now let's see if the import works. # I copied the 3.13.5 zip file to the import directory again and this time, I untarred the attachments into the import/attachments directory. # I kicked off the restore as before and it worked through it fine. # Shutdown and restarted system, tailing the log file and then went to localhost:8180 # I can see issues (before logging in) and it all looks good!! The attachments did not move over from the import directory, so I copied the tar file from /data/jira445/import to /data/jira445/data and then untarred it there, then removed the tar file and the import zip file from the import directory. # Now I will try to login using my MBARI account and OMG it actually worked!!! (it even gave my kgomes account Admin privs) # I then performed an export and copied those file to the /data/backups/4.4.5 directory (also created a TAR of the attachments and put there too). # Now on to version 5! # OK, so something strange is happening. After the imports, the server ID goes back to the one that is on our current production server, which must mean it is using our current license key (which does not match the server ID, BTW). Oh well, I will press on! # I created a /data/jira5211 directory as well as a /opt/jira5 directory. Knowing what I know now and reading through the install instructions, it appears that I need to create a dbconfig.xml file manually, so I did that using: {noformat} defaultDS default mssql dbo jdbc:jtds:sqlserver://solstice2.shore.mbari.org:1433/Jira5;domain=SHORE;useNTLMv2=true net.sourceforge.jtds.jdbc.Driver DB_Collaboration (ask Kevin) 20 20 30000 20 true 300 select 1 60000 300000 true false {noformat} # I then changed the mode to executable on the installer download and ran that. # I had to choose a "custom install" this time through, but the properties were similar after that (ports I used were 8280 and 8205) # I then browsed to localhost:8280 # I dropped me to a wizard where I define the title as "MBARI JIRA5", and changed host to bugs.shore.mbari.org (from localhost) # This license was a little different in that is just asked for my Atlassian username and password and fetched a new license for me. # For the admin account, I used the same 'jiraadm' account # Left email notification disabled. # I created a new application in crowd for JIRA 5 and used same account info as for 4. # In JIRA, I went to Administration->Users->User Directories and then added a directory as I had done before. # All went well and the sync happened. # I then went to Administration->System->Import and Export->Restore System # I copied the backup of 4.4.5 to the /data/jira5211/import directory and then specified that file name. I did not specify a license as it seems to use the old one and it said so in the text below the box. # Clicked on restore and while it was restoring, I untarred the attachments to the /data/jira5211/data directory # After the restore, I shutdown and restarted JIRA tailing the log file. # Browsed to localhost:8280 and ... success! I see issues before logging in and ... my MBARI login worked, I was admin and all is good!!!! # As with previous version, I ran a backup of the DB and attachments and placed in /data/backups/5.2.11 # I poked around a little and there seems to be an issue in the comments that they are still referencing oceana??? I will have to look into this. # I then re-did the process once again for version 6.4.9. I will only put notes about things that are dramatically different below: ## It looks like the dbconfig.xml file is the same as it is for version 5, so I just copied and edited to point to Jira6 DB. ## I used ports 8380 and 8305 {warning:title=Collation} The DB needs to be using a specific collation that it's not, I will have to correct that on the production run {warning}]]> 27558202 27590968 4.4: [https://confluence.atlassian.com/display/JIRA044/Migrating+JIRA+to+Another+Server] ## The JIRA configuration tool: [https://confluence.atlassian.com/display/JIRA044/Using+the+JIRA+Configuration+Tool] h5. Steps # (/) Create new VM named bugs.mbari.org in the DMZ # (/) Have Neil create database Jira_Temp on solstice2.shore.mbari.org # (/) Have Neil create database Jira on solstice2.shore.mbari.org # (/) Have Pat install Java 7 on bugs.shore.mbari.org # (/) Have Pete plumb holes through firewall so processes on bugs.mbari.org can get to Solstice2 # (/) Have Pat create DB_Collaboration account on bugs so it can run JIRA under that account and it can connect to solstice2 using that NT Domain account. # (/) Upgrade license on Atlassian site # (/) Log into bugs.shore.mbari.org # (/) Download 3.13.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 4.4.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 5.2.11 standalone Linux 64 bit tar.gz (not sure this version is necessary, but at least I have it) # (/) Unzip and untar the file to /opt # (/) Download latest JIRA (6.4.7 as of this writing). # (/) Unzip and untar it to /opt # Performed Test Upgrade ## (/) In order to export the current stuff in JIRA, I had to shut off access so people could not change the data while I was backing it up. ## (/) I ssh'd to oceana.mbari.org as root and edited the /opt/jira/conf/server.xml file and commented out the Connector section that had the port of 8010 to shut it off from the normal serving route. ## (/) I uncommented the 8082 port connector and the 8443 port connector so that I could still get to the server. ## (/) I stopped and started the JIRA server and in the log file I got a "keystore was tampered with..." which is not surprising. ## (/) I could then browser over to http://oceana.mbari.org:8082/jira ## (/) Then through the Administration console, I did an XML backup ## (/) I then created a tar of all the attachments in the /data/jira_3_12/attachments directory ## (/) I moved both the XML and tar files to the /root/jira-upgrade directory ## (/) I then reversed the changes to the server.xml file and shut down JIRA ## (/) I left it down during the next steps in case it went so well, I could just point people to the new server (yeah, right). ## (/) I then browsed to the crowd server on oceana and add a new application using: ### URL: http://bugs.mbari.org/jira3135 ### IP: 134.89.2.29 ### Name: JIRA3135 ### Password: (ask Kevin) :) ## (/) On bugs, I made a copy of the JIRA 3.13.5 download in the /opt directory and unzipped and untarred it. ## (/) In order to configure the crowd connection I did the following: ### (/) I scp'd the /opt/crowd/client/crowd-integration-client-1.6.jar file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I removed the existing 1.6.1 crowd client jar from the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I scp'd the /opt/crowd/client/conf/crowd.properties file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I scp'd the /opt/crowd/client/conf/crowd-ehcache.xml file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I edited the crowd.properties file on bugs to look like: {noformat} application.name JIRA3135 application.password (ask Kevin) application.login.url http://oceana.mbari.org:8095/crowd/console/ crowd.server.url http://oceana.mbari.org:8095/crowd/services/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 0 session.lastvalidation session.lastvalidation {noformat} ### (/) I edited the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/osuser.xml file to comment out the current authentication mechanism and then uncomment the crowd one. ## (/) I then edited the /opt/atlassian-jira-standalone-3.13.5/conf/server/xml file and configured the database connection to the Jira_Temp database on Solstice2. I looked like this: {noformat} {noformat} ## (/) Edit the /opt/atlassian/jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/entityengine.xml and changed it from 'hsql' to 'mssql' and delete the line with "PUBLIC" in it per the instructions in the comments in that file. ## (/) I edited the /etc/httpd/conf/httpd.conf file and created a proxy pass at the bottom of the file to point a normal URL to the default port 8080 for JIRA: {noformat} # Proxy Pass for JIRA ProxyPass http://bugs.mbari.org:8080 ProxyPassReverse http://bugs.mbari.org:8080 {noformat} ## (/) I restarted Apache ## (/) I scp'd the jtds driver from oceana to the /opt/atlassian-jira-standalone-3.13.5/common/lib directory (you could down from the internet) ## (/) I then went to the /opt/atlassian-jira-standalone-3.13.5/ directory and ran './bin/startup.sh'. From the log file, I could tell things were hanging. After some troubleshooting I am wondering if the local firewall is preventing the application to get access to the database on solstice2. I can telnet to port 1433, but I can't browse to the base http://bugs.mbari.org from anywhere but the local web browser. I have submitted a ticket. ## (/) I restarted the old JIRA with my hopes dashed :(. ## (/) Pat disabled the firewall on bugs.mbari.org but it still hung trying to connect to solstice2.shore.mbari.org. That is really, really perplexing. Neil mentioned that solstice2 is using Kerberos and solstice is not. Checking with the JTDS docs, version 1.3.1 of the driver added kerberos support, so I downloaded that driver and added the 'userKerberos=true' property to the URL in the server.xml file and restarted. Got an error about no credentials, so added user and password properties to the URL. Nope, no luck. Never did figure this one out, but I had Pat pull the VM inside the firewall and after some thrash it worked. Well, it sort of worked ... sigh. It turns out I had downloaded the standard version instead of the enterprise version. I need to redo this work ... grrr. ## (/) I deleted all the tables in the Jira_Temp database and removed the /data/jira3135/indexes directory (and recreated). ## (/) I downloaded the enterprise version of the 3.13.5 server. I made a copy in the /opt directory and unzipped and untarred the file. ## (/) I went back to crowd and edited the application to change the properties to: ### URL: http://bugs.shore.mbari.org:8080 ### IP: 134.89.12.31 ### Name: jira3135 ### Password: (ask Kevin) :) ## (/) I then repeated the steps above to get the server up and running with the following differences: ### The server name is now bugs.shore.mbari.org ### The paths given above are a little different in that they no longer say "standard" but say "enterprise" ### I deleted the proxy pass as it seemed to have issues before and this is only temporary anyway. ## (/) I then browsed to http://bugs.shore.mbari.org:8080 ## (/) It took me to the start up page and at the top was the option to 'import your existing data'. Seemed too good not to try. I clicked on the link. It asked me for the backup file location and the location where the indexes would be stored. ## (/) I copied the XML zip file and the attachments tar file to the /data/original directory. ## (/) I created the /data/jira3135/indexes and used those directories ... it fired off the import and I waited. ## (/) I tailed the log file to watch the import. Holy crap, it worked!!! I could log in and everything! I copied the results from the log file here for posterity sake: {noformat} 2015-07-22 20:55:45,156 http-8080-Processor22 INFO [jira.action.admin.DataImport] Running data import 2015-07-22 20:55:45,179 http-8080-Processor22 INFO [jira.action.admin.DataImport] Importing data.. 2015-07-22 20:55:45,186 http-8080-Processor22 INFO [jira.action.admin.DataImport] Start parsing XML with SAX Parser 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] XML successfully parsed 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] Removing all entries from the database. 2015-07-22 20:56:24,593 http-8080-Processor22 INFO [jira.action.admin.DataImport] All entries removed. 2015-07-22 20:56:24,594 http-8080-Processor22 INFO [jira.action.admin.DataImport] Started storing 410414 Generic Values 2015-07-22 21:01:51,967 http-8080-Processor22 INFO [jira.action.admin.DataImport] Finished storing Generic Values 2015-07-22 21:01:52,329 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:52,361 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:54,683 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLink' to module 'jira.user.format:profile-link-user-format'. 2015-07-22 21:01:54,724 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullName' to module 'jira.user.format:full-name-user-format'. 2015-07-22 21:01:54,773 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkSearcher' to module 'jira.user.format:profile-link-searcher-user-format'. 2015-07-22 21:01:54,784 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkExternal' to module 'jira.user.format:profile-link-external-user-format'. 2015-07-22 21:01:54,795 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkActionHeader' to module 'jira.user.format:profile-link-action-header-user-format'. 2015-07-22 21:01:54,807 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullProfile' to module 'jira.user.format:full-profile-user-format'. 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/comments 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/issues 2015-07-22 21:01:55,641 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/plugins 2015-07-22 21:01:55,867 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:01:55,871 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/issues does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:55,873 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/comments does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,033 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,257 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,889 http-8080-Processor22 ERROR [atlassian.jira.upgrade.ConsistencyCheckImpl] Attachments are turned on, but attachment path [/data/jira_3_12/attachments] invalid - disabling attachments 2015-07-22 21:02:13,904 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Detected that an upgrade is needed; existing data at build 299 2015-07-22 21:02:13,907 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Doing Upgrade... 2015-07-22 21:02:13,915 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value' succeeded 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 317 2015-07-22 21:02:13,944 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite filters - make each filter a favourite of its owner. 2015-07-22 21:02:17,822 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build319] Could not find author 'fpy' for filter with id '10040' 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite filters - make each filter a favourite of its owner.' succeeded 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 319 2015-07-22 21:02:17,995 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise Share Permissions. Move old shares to new shares. 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise Share Permissions. Move old shares to new shares.' succeeded 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 321 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Migrating the old JIRA UI colors to the new JIRA 3.13 colors 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build322] Custom color detected for jira.lf.menu.bgcolour : #336699 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Migrating the old JIRA UI colors to the new JIRA 3.13 colors' succeeded 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 322 2015-07-22 21:02:18,025 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite dashboards - make each dashboard a favourite of its owner. 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'cmcgann' for dashboard with id '10030' 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'fpy' for dashboard with id '10060' 2015-07-22 21:02:18,423 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'kanna' for dashboard with id '10040' 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite dashboards - make each dashboard a favourite of its owner.' succeeded 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 325 2015-07-22 21:02:18,625 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Reindexing all data in JIRA to include Favourites. 2015-07-22 21:02:18,648 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All starting... 2015-07-22 21:02:18,650 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 0% complete. Current index: Issue 2015-07-22 21:02:18,654 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:02:18,809 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 1% complete. Current index: Issue 2015-07-22 21:02:18,855 indexerPool-2-thread-10 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 2% complete. Current index: Issue 2015-07-22 21:02:18,899 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 3% complete. Current index: Issue 2015-07-22 21:02:18,945 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 4% complete. Current index: Issue 2015-07-22 21:02:19,012 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 5% complete. Current index: Issue . . . 2015-07-22 21:02:26,164 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 95% complete. Current index: Issue 2015-07-22 21:02:26,232 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 96% complete. Current index: Issue 2015-07-22 21:02:26,316 indexerPool-2-thread-9 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 97% complete. Current index: Issue 2015-07-22 21:02:26,771 indexerPool-2-thread-3 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: Issue 2015-07-22 21:02:27,261 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 8607ms. Indexer: DefaultIndexManager: paths: [/data/jira3135/indexes/issues, /data/jira3135/indexes/comments] 2015-07-22 21:02:27,263 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: SearchRequest 2015-07-22 21:02:27,268 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,293 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: SearchRequest 2015-07-22 21:02:27,308 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: PortalPage 2015-07-22 21:02:27,312 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,377 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: PortalPage 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 115ms. Indexer: SharedEntityIndexManager: paths: [/data/jira3135/indexes/entities/portalpage, /data/jira3135/indexes/entities/searchrequest] 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All complete. Total time: 8722ms. 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Reindexing all data in JIRA to include Favourites.' succeeded 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 326 2015-07-22 21:02:27,397 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade succeeded! Setting data build number to 360 2015-07-22 21:02:27,469 JiraQuartzScheduler_Worker-0 WARN [service.services.export.ExportService] Backup directory /data/jira_3_12/backup does not exist {noformat} {warning:title=Paths} It appears that the upgraded JIRA will still look for the attachments and the backup locations in the original places. So I created /data/jira_3_12/backup and untarred the original attachments to /data/jira_3_12 and then everything worked (including attachements) in the new JIRA. {warning} ## (/) I then used the upgraded JIRA to generate a new XML backup and stored it in /data/original/3.13.5 along with another tar of the files in /data/jira_3_12/attachments. ## (/) I then shutdown the JIRA server. *I should be ready to move on to version 4 upgrade WHEW* ## So, before moving on, I decided that it would be a really good idea to spin up a new Crowd instance to get rid of the :8443 in the URL and to move off of RedHat per IS requests. I have a ticket in for a new VM and a new database to try to get this going. I am waiting on that before moving on. ## (/) Pat created the VM and Neil created the database. ## (/) I logged into auth.mbari.org (name of the VM) and downloaded crowd which I unzipped to the /opt directory ## (/) I then created a /data/crowd directory and gave my account permissions on it and then edited the /opt/atlassian..../crowd-webapp/WEB-INF/classes/crowd-init.properties file to set that as the crowd home directory. ## (/) The instructions say to download the JDBC driver, but they already have JTDS 1.2.7 in the download so I did not do anything. ## (/) You have to manually connect up CrowdID to a database as they setup wizard does not currently do this. ### (/) They say to download the driver, but again 1.2.7 was there so I did nothing. ### (/) I edited the /opt/atlassian.../apache-tomcat/conf/Catalina/localhost/openidserver.xml to look like: {noformat} {noformat} ### (/) I edited the /opt/atlassian.../build.properties files to look like: {noformat} # Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See https://confluence.atlassian.com/display/CROWD/Connecting+Crowd+to+a+Database hibernate.dialect=org.hibernate.dialect.SQLServerDialect # The Hibernate transaction factory to use. See https://confluence.atlassian.com/display/CROWD/Configuring+Crowd hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory # The http port you wish to run crowd from, ie: http://localhost:8095/crowd crowd.tomcat.connector.port=8095 # Tomcat requires a unique port for shutdown crowd.tomcat.shutdown.port=8020 # Crowd context root crowd.url=http://localhost:8095/crowd # Demo context root demo.url=http://localhost:8095/demo # OpenID server context root openidserver.url=http://localhost:8095/openidserver {noformat} ### (/) I then ran the build.sh script in the root of /opt/atlassian... ## (/) I fired up crowd using the /opt/atlassian.../start_crowd.sh script ## (/) I then went to http://auth.mbari.org:8095/crowd to kick off the start up wizard ## (/) I grabbed a new eval license from my account on atlassian and pasted into the license page. ## (/) I selected "New install" on the next page. ## (/) I configured the JDBC connection using this connection URL with user DB_Collaboration {noformat} jdbc:jtds:sqlserver://dione.mbari.org:51001/Crowd;domain=SHORE;useNTLMv2=TRUE {noformat} ## (/) I left the "Options" as they came up {warning:title=Paths} Not sure if this is a problem, but because I started the set up using auth.mbari.org, it set the Base URL to http://auth.mbari.org:8095/crowd instead of localhost. Hope that is not a problem. We will see. {warning} ## (/) I configured the email connection using the settings from [here|https://wind.shore.mbari.org/is/howto/email/mbarimail/imap] and I used my network login (probably shouldn't be doing that ... not sure where it stores my password, but I am assuming in the DB). ## (/) For the local admin account, I created a user named 'crowdadm' so it would not clash with my LDAP account. See Kevin Gomes for password information. ## (/) I checked the OpenID server as an integrated application ## (/) It then took me to the login page and I logged in using the newly minted admin account. Seemed all is well so far. ## (/) I visited the openidserver URL as well and that seemed OK. ## (/) I decided to wait on configuring the MBARI LDAP directory until I got everything with SSL working. ## (/) Now the next step was to follow the directions to configure Crowd to run over SSL found [here|https://confluence.atlassian.com/display/CROWD/Configuring+Crowd+to+Work+with+SSL] ## (/) I shutdown crowd. Note that the stop script does not shutdown things correctly and I noticed the crowd app running as root. That should not be if I started as kgomes. Not sure what is up with that. ## (/) Now Joe had already configured SSL once, so I used his connector configuration in the server.xml file and so the final file looked like: {noformat} {noformat} ## (/) I then edited the /data/crowd/crowd.properties to look like: {noformat} #Sat Aug 01 09:05:15 PDT 2015 session.lastvalidation=session.lastvalidation session.tokenkey=session.tokenkey crowd.server.url=https\://localhost\:8443/crowd/services/ application.name=crowd http.timeout=30000 session.isauthenticated=session.isauthenticated application.login.url=https\://localhost\:8443/crowd/console/ session.validationinterval=0 application.password=Y1Xp3OorCmsOP4eruL1dmH {noformat} One thing to note here is that based on a comment from the SSL configuration page at atlassian (Steve's comment), you are supposed to leave all the host names the same. For example, if the file says localhost, leave it localhost. So this created a bit of a problem based on the fact that I had left the base URL pointing to auth.mbari.org in the wizard steps above. That step wrote auth.mbari.org to the /data/crowd/crowd.properties. All the other files reference localhost, so to be consistent, I changed auth.mbari.org to localhost in the /data/crowd/crowd.properties file. We will see if this works. ## (/) Per the instructions on the atlassian page (referenced above), I also edited the build.properties file and the /client/conf/crowd.properties files before I restarted and used the SSL URLs ## build.properties: {noformat} # Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See https://confluence.atlassian.com/display/CROWD/Connecting+Crowd+to+a+Database hibernate.dialect=org.hibernate.dialect.SQLServerDialect # The Hibernate transaction factory to use. See https://confluence.atlassian.com/display/CROWD/Configuring+Crowd hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory # The http port you wish to run crowd from, ie: http://localhost:8095/crowd crowd.tomcat.connector.port=8095 # Tomcat requires a unique port for shutdown crowd.tomcat.shutdown.port=8020 # Crowd context root crowd.url=https://localhost:8443/crowd # Demo context root demo.url=https://localhost:8443/demo # OpenID server context root openidserver.url=https://localhost:8443/openidserver {noformat} ## crowd.properties (client) {noformat} application.name crowd application.password password application.login.url https://localhost:8443/crowd/console/ crowd.server.url https://localhost:8443/crowd/services/ crowd.base.url https://localhost:8443/crowd/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 2 session.lastvalidation session.lastvalidation {noformat} ## (/) Although not stated, I am assuming you would need to run the build.sh script to push the build.properties changes to their proper places, so I did that. Note that before doing that, I know that it will clobber the server.xml changes I made, so I made a copy of that file and diff'd them after and then rolled the previous changes to the new server.xml file. Actually, amazingly enough, it seems to have done the connector entry correctly so I left it after running the build.sh script. ## (/) Crossed my fingers and then restarted crowd. I tailed the catalina.out file and did not see any stack traces so that is a good sign! ## (/) I visited https://auth.mbari.org:8443/crowd first. It could not find that page, but I suspect that is because I am browsing from the outside, so I tried just https://auth.mbari.org/crowd and got a service unavailable. I am suspecting that this is a combination of firewall and proxy pass and I will send this info to Joe. From what I can see on the crowd side, it seems like the server started cleanly, we just can't get to it. I tried to reach it from a browser on the machine itself too (through VNC) with the same service not available. ## (/) Here are the notes from Joe after he fixed it! Wooohooo! {noformat} Hey Kevin, Thanks for starting clean! I had to make a few adjustments. 1-I modified the server.xml file in /opt/atlassian-crowd-2.8.3/apache-tomcat/conf/server.xml so there are two connectors per the instructions on the Atlassian site. I have backed up this good server.xml file in /etc/temp/ if you want to browse it to see what I did. Of note is that I removed all the jargon referencing the types of ciphers available to simplify things for now. 2-I modified /data/crowd/crowd.properties to have crowd.server.url=https\://localhost\:8443/crowd/services/ application.login.url=https\://localhost\:8443/crowd/console/ But that would cause my login to error with an error saying it was unable to reach the authentication server. I scratched my head for a bit. When I revert the values to just using non-SSL and try to log in, I just get an "invalid login" (I don't know the crowdadm password). So I worked under the assumption that if I can configure SSL to get an "invalid login" when logging in then it would work when provided real credentials. So, I then changed /data/crowd/crowd.proprties to: crowd.server.url=https\://auth.mbari.org\:8443/crowd/services/ application.login.url=https\://auth.mbari.org\:8443/crowd/console/ And now when I try to log in with SSL it says "invalid login". Strange because all the other values I can find only show "localhost" .. in any case... Can you try to log in now? {noformat} ## (/) Next I moved on to configuring the connection to MBARI's LDAP server to enable our logins through Crowd and CrowdID ## (/) I clicked on "Add Directory" in crowd. ## (/) I selected "Connector" then clicked Next ## (/) I put ldap.shore.mbari.org as the name of the server ## (/) I selected "Use memberOf for group memberships" ## (/) I used "OU=AllUsers,DC=shore,DC=mbari,DC=org" for the Base DN ## (/) I used "CN=LDAPbind,OU=Special,OU=AllUsers,DC=shore,DC=mbari,DC=org" for the Username (talk to Pat Allen for password) ## (/) I tested the connection (button click) and it passed. ## (/) I de-selected all the capabilities of the connector as it is a ready only connector and then saved it. It synchronized correctly! ## (/) At first, I could not login using my MBARI credentials, but after going to the "crowd" application in crowd (logged in as the local admin), I had to add the LDAP directory and configure it to "Allow all to authenticate", then I was able to login. After this, the last step was to get this to run as a different user and lock down various directories. I went through the entire directory structure /opt/atlassian... and set up so that root owned all read-only locations and DB_Collaboration (account set up by IS) owned the other stuff. I also gave full ownership to the /data/crowd directory to DB_Collaboration so it could write there. Pat set up a script to start on boot and after a little tweaking, it now starts on boot. {warning:title=CrowdID log file} One thing that came up here was that when the crowdID application ran, it tried to write a log file to the location where the process was launched from (which is /opt/atlassian...). This is a bad thing and I figured out that I could change that location by changing the file /opt/atlassian-crowd-2.8.3/crowd-openidserver-webapp/WEB-INF/classes/log4j.properties and hardcoding the /data/crowd/logs/atlassian-crowd-openid-server.log and then restarted the application. {warning} ## (/) Another note is the when an application tried to use the OpenID application, it would get redirected to localhost. I changed the /opt/atlassian.../crowd-openidserver-webapp/WEB-INF/classes/crowd.properties file to look like: {noformat} #Sat Aug 01 10:03:18 PDT 2015 session.lastvalidation=session.lastvalidation session.tokenkey=session.tokenkey crowd.server.url=http\://localhost\:8095/crowd/services/ application.name=crowd-openid-server #application.login.url.template=http\://localhost\:8095/openidserver?returnToUrl\=${RETURN_TO_URL} application.login.url.template=https\://auth.mbari.org/openidserver?returnToUrl\=${RETURN_TO_URL} session.isauthenticated=session.isauthenticated #application.base.url=http\://localhost\:8095/openidserver application.base.url=https\://auth.mbari.org/openidserver #application.login.url=http\://localhost\:8095/openidserver application.login.url=https\://auth.mbari.org/openidserver session.validationinterval=0 application.password=password {noformat} and that seems to have fixed it. # (/) It is finally time to move on to the version 4 upgrade ... holy crap. I first went to the *new* crowd install (auth.mbari.org) and logged in as the crowdadm. # (/) I clicked on Applications, then on Add Application # (/) I selected JIRA from the Application type drop-down # (/) I entered jira445 as the username. Ask Kevin about the password. # (/) I used http://bugs.shore.mbari.org:8081 as the URL # (/) I used 134.89.12.31 as the IP address. # (/) I selected only the MBARI LDAP directory. # (/) Then I selected "Allow all users to authenticate" # (/) Then I clicked on "Add Application" # (/) I VNC'd into bugs.mbari.org. As it turns out, for Linux, there is an installer program to download. I downloaded the .bin for 64 bit Linux installer and moved it to the jira-upgrade directory. # (/) I chmod'd the file to make it executable and ran it. It gave me a warning about not being root, but I went ahead with it. # (/) It asked for the JIRA home and data directory, which I specified as /opt/jira4 and /data/jira445. # (/) For the ports, I specified 8180 and 8105 (HTTP and control respectively). It then extracted all the files and launched JIRA. It said if finished, so I opened a local browser to http://localhost:8180 which kicked off the start up wizard. # (/) I specified the external database using: ## solstice2.shore.mbari.org (server) ## 1433 (port) ## jira4 (database) ## DB_Collaboration (username) ## (password ask Kevin) ## dbo (schema) # But all this failed as it seems to just want to try and use the SQL server authentication instead of domain. I will have to do it manually. # (/) I stopped the server using the bin/stop-jira.sh script. # (/) I created and edited /data/jira445/dbconfig.xml and made it look like the following: {noformat} ?xml version="1.0" encoding="UTF-8"?> defaultDS default mssql jiraschema jdbc:jtds:sqlserver://solstice2.shore.mbari.org:1433/Jira4;domain=SHORE;useNTLMv2=true net.sourceforge.jtds.jdbc.Driver DB_Collaboration (ask Kevin) 15 {noformat} # (/) I then started it again using bin/start-jira.sh and tailed the catalina.out file. Got a bunch of errors related to the schema 'jiraschema', I edited the file and changed the schema to 'dbo' and restarted. That seemed to do it. There was one stack trace for some iCal plugin, but looks OK other than that. # I browsed back to localhost:8180 and the wizard moved to step 2. There was an option to import existing data bit without the crowd connection, I thought I should set it up manually, connect to crowd, then import. I generated an evaluation license, called the app "MBARI JIRA4" and change the server in the url to bugs.shore.mbari.org # For the admin, I created an account called 'jiraadm' (ask Kevin for password). # Since this is a temporary system, I left the email system disabled. # I logged in as jiraadm, went to Administration, then Users, then clicked on Add Directory and chose Atlassian Crowd. Note that I had to set the server URL to http://auth.mbari.org:8095/crowd or I would have had to configure all this SSL crap that I did not want to do for this temporary install. # It tested successfully, I clicked Save and it went through a 13 second sync, whew! # I then went to System->Import and Export->Restore System # I copied the jira-upgrade-3.13.5.zip file from the previous version export into /data/jira445/import and then entered that file name along with the new evaluation license again. # I worked through progress bar after I clicked on Restore (it took a really long time). # I then stopped, restarted and tailed the log file. # I am thinking now I should have put the attachments in the import attachments directory, but I am hoping I can just copy them to the data/attachments directory. # UG! I got some error during the import. The exception read: "JIRA is unable to migrat the User Directory configuration because external users exist but the osuser.xml file is not available". It then gave me a link to a doc that talked about making the old user files available before the upgrade ... crap. So I needed to copy the osuser.xml and crowd.properties file from atlassian-jira/WEB-INF/classes directory on the old install to the same directory on the new install ... sigh. This means I am going to blow away everything and start over. # I shutdown jira4 # I dropped all things in the database and deleted all content in the /data/jira445 directory (except for the dbconfig.xml file). # I also removed the temp, logs (actually you have to leave the directory, just clear the files) and the work/Catalina/localhost directories from the jira installation. # I then copied the osuser.xml and the crowd.properties files from the 3.13.5 install to the 4 install. # I edited the crowd.properties file in hopes that I could point it to the new crowd install on auth.mbari.org and it would work, but we will see. # I then started jira and tailed the log file. # All looked OK (other than iCal plugin stack trace again), so I went to localhost:8180 and got step 2 of the wizard. I used the same info as before. # I logged in as the local admin account and it looks like the system picked up the crowd connection, but lets see what server it used! Hey it used the one I edited into the file! Sweet ... now let's see if the import works. # I copied the 3.13.5 zip file to the import directory again and this time, I untarred the attachments into the import/attachments directory. # I kicked off the restore as before and it worked through it fine. # Shutdown and restarted system, tailing the log file and then went to localhost:8180 # I can see issues (before logging in) and it all looks good!! The attachments did not move over from the import directory, so I copied the tar file from /data/jira445/import to /data/jira445/data and then untarred it there, then removed the tar file and the import zip file from the import directory. # Now I will try to login using my MBARI account and OMG it actually worked!!! (it even gave my kgomes account Admin privs) # I then performed an export and copied those file to the /data/backups/4.4.5 directory (also created a TAR of the attachments and put there too). # Now on to version 5! # OK, so something strange is happening. After the imports, the server ID goes back to the one that is on our current production server, which must mean it is using our current license key (which does not match the server ID, BTW). Oh well, I will press on! # I created a /data/jira5211 directory as well as a /opt/jira5 directory. Knowing what I know now and reading through the install instructions, it appears that I need to create a dbconfig.xml file manually, so I did that using: {noformat} defaultDS default mssql dbo jdbc:jtds:sqlserver://solstice2.shore.mbari.org:1433/Jira5;domain=SHORE;useNTLMv2=true net.sourceforge.jtds.jdbc.Driver DB_Collaboration (ask Kevin) 20 20 30000 20 true 300 select 1 60000 300000 true false {noformat} # I then changed the mode to executable on the installer download and ran that. # I had to choose a "custom install" this time through, but the properties were similar after that (ports I used were 8280 and 8205) # I then browsed to localhost:8280 # I dropped me to a wizard where I define the title as "MBARI JIRA5", and changed host to bugs.shore.mbari.org (from localhost) # This license was a little different in that is just asked for my Atlassian username and password and fetched a new license for me. # For the admin account, I used the same 'jiraadm' account # Left email notification disabled. # I created a new application in crowd for JIRA 5 and used same account info as for 4. # In JIRA, I went to Administration->Users->User Directories and then added a directory as I had done before. # All went well and the sync happened. # I then went to Administration->System->Import and Export->Restore System # I copied the backup of 4.4.5 to the /data/jira5211/import directory and then specified that file name. I did not specify a license as it seems to use the old one and it said so in the text below the box. # Clicked on restore and while it was restoring, I untarred the attachments to the /data/jira5211/data directory # After the restore, I shutdown and restarted JIRA tailing the log file. # Browsed to localhost:8280 and ... success! I see issues before logging in and ... my MBARI login worked, I was admin and all is good!!!! # As with previous version, I ran a backup of the DB and attachments and placed in /data/backups/5.2.11 # I poked around a little and there seems to be an issue in the comments that they are still referencing oceana??? I will have to look into this. # I then re-did the process once again for version 6.4.9. I will only put notes about things that are dramatically different below: ## It looks like the dbconfig.xml file is the same as it is for version 5, so I just copied and edited to point to Jira6 DB. ## I used ports 8380 and 8305 {warning:title=Collation} The DB needs to be using a specific collation that it's not, I will have to correct that on the production run {warning} ## It gave me a choice on "how I wanted to use JIRA" and I chose the default (top) one which was just JIRA. ]]> 27558204 27590970 4.4: [https://confluence.atlassian.com/display/JIRA044/Migrating+JIRA+to+Another+Server] ## The JIRA configuration tool: [https://confluence.atlassian.com/display/JIRA044/Using+the+JIRA+Configuration+Tool] h5. Steps # (/) Create new VM named bugs.mbari.org in the DMZ # (/) Have Neil create database Jira_Temp on solstice2.shore.mbari.org # (/) Have Neil create database Jira on solstice2.shore.mbari.org # (/) Have Pat install Java 7 on bugs.shore.mbari.org # (/) Have Pete plumb holes through firewall so processes on bugs.mbari.org can get to Solstice2 # (/) Have Pat create DB_Collaboration account on bugs so it can run JIRA under that account and it can connect to solstice2 using that NT Domain account. # (/) Upgrade license on Atlassian site # (/) Log into bugs.shore.mbari.org # (/) Download 3.13.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 4.4.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 5.2.11 standalone Linux 64 bit tar.gz (not sure this version is necessary, but at least I have it) # (/) Unzip and untar the file to /opt # (/) Download latest JIRA (6.4.7 as of this writing). # (/) Unzip and untar it to /opt # Performed Test Upgrade ## (/) In order to export the current stuff in JIRA, I had to shut off access so people could not change the data while I was backing it up. ## (/) I ssh'd to oceana.mbari.org as root and edited the /opt/jira/conf/server.xml file and commented out the Connector section that had the port of 8010 to shut it off from the normal serving route. ## (/) I uncommented the 8082 port connector and the 8443 port connector so that I could still get to the server. ## (/) I stopped and started the JIRA server and in the log file I got a "keystore was tampered with..." which is not surprising. ## (/) I could then browser over to http://oceana.mbari.org:8082/jira ## (/) Then through the Administration console, I did an XML backup ## (/) I then created a tar of all the attachments in the /data/jira_3_12/attachments directory ## (/) I moved both the XML and tar files to the /root/jira-upgrade directory ## (/) I then reversed the changes to the server.xml file and shut down JIRA ## (/) I left it down during the next steps in case it went so well, I could just point people to the new server (yeah, right). ## (/) I then browsed to the crowd server on oceana and add a new application using: ### URL: http://bugs.mbari.org/jira3135 ### IP: 134.89.2.29 ### Name: JIRA3135 ### Password: (ask Kevin) :) ## (/) On bugs, I made a copy of the JIRA 3.13.5 download in the /opt directory and unzipped and untarred it. ## (/) In order to configure the crowd connection I did the following: ### (/) I scp'd the /opt/crowd/client/crowd-integration-client-1.6.jar file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I removed the existing 1.6.1 crowd client jar from the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I scp'd the /opt/crowd/client/conf/crowd.properties file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I scp'd the /opt/crowd/client/conf/crowd-ehcache.xml file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I edited the crowd.properties file on bugs to look like: {noformat} application.name JIRA3135 application.password (ask Kevin) application.login.url http://oceana.mbari.org:8095/crowd/console/ crowd.server.url http://oceana.mbari.org:8095/crowd/services/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 0 session.lastvalidation session.lastvalidation {noformat} ### (/) I edited the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/osuser.xml file to comment out the current authentication mechanism and then uncomment the crowd one. ## (/) I then edited the /opt/atlassian-jira-standalone-3.13.5/conf/server/xml file and configured the database connection to the Jira_Temp database on Solstice2. I looked like this: {noformat} {noformat} ## (/) Edit the /opt/atlassian/jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/entityengine.xml and changed it from 'hsql' to 'mssql' and delete the line with "PUBLIC" in it per the instructions in the comments in that file. ## (/) I edited the /etc/httpd/conf/httpd.conf file and created a proxy pass at the bottom of the file to point a normal URL to the default port 8080 for JIRA: {noformat} # Proxy Pass for JIRA ProxyPass http://bugs.mbari.org:8080 ProxyPassReverse http://bugs.mbari.org:8080 {noformat} ## (/) I restarted Apache ## (/) I scp'd the jtds driver from oceana to the /opt/atlassian-jira-standalone-3.13.5/common/lib directory (you could down from the internet) ## (/) I then went to the /opt/atlassian-jira-standalone-3.13.5/ directory and ran './bin/startup.sh'. From the log file, I could tell things were hanging. After some troubleshooting I am wondering if the local firewall is preventing the application to get access to the database on solstice2. I can telnet to port 1433, but I can't browse to the base http://bugs.mbari.org from anywhere but the local web browser. I have submitted a ticket. ## (/) I restarted the old JIRA with my hopes dashed :(. ## (/) Pat disabled the firewall on bugs.mbari.org but it still hung trying to connect to solstice2.shore.mbari.org. That is really, really perplexing. Neil mentioned that solstice2 is using Kerberos and solstice is not. Checking with the JTDS docs, version 1.3.1 of the driver added kerberos support, so I downloaded that driver and added the 'userKerberos=true' property to the URL in the server.xml file and restarted. Got an error about no credentials, so added user and password properties to the URL. Nope, no luck. Never did figure this one out, but I had Pat pull the VM inside the firewall and after some thrash it worked. Well, it sort of worked ... sigh. It turns out I had downloaded the standard version instead of the enterprise version. I need to redo this work ... grrr. ## (/) I deleted all the tables in the Jira_Temp database and removed the /data/jira3135/indexes directory (and recreated). ## (/) I downloaded the enterprise version of the 3.13.5 server. I made a copy in the /opt directory and unzipped and untarred the file. ## (/) I went back to crowd and edited the application to change the properties to: ### URL: http://bugs.shore.mbari.org:8080 ### IP: 134.89.12.31 ### Name: jira3135 ### Password: (ask Kevin) :) ## (/) I then repeated the steps above to get the server up and running with the following differences: ### The server name is now bugs.shore.mbari.org ### The paths given above are a little different in that they no longer say "standard" but say "enterprise" ### I deleted the proxy pass as it seemed to have issues before and this is only temporary anyway. ## (/) I then browsed to http://bugs.shore.mbari.org:8080 ## (/) It took me to the start up page and at the top was the option to 'import your existing data'. Seemed too good not to try. I clicked on the link. It asked me for the backup file location and the location where the indexes would be stored. ## (/) I copied the XML zip file and the attachments tar file to the /data/original directory. ## (/) I created the /data/jira3135/indexes and used those directories ... it fired off the import and I waited. ## (/) I tailed the log file to watch the import. Holy crap, it worked!!! I could log in and everything! I copied the results from the log file here for posterity sake: {noformat} 2015-07-22 20:55:45,156 http-8080-Processor22 INFO [jira.action.admin.DataImport] Running data import 2015-07-22 20:55:45,179 http-8080-Processor22 INFO [jira.action.admin.DataImport] Importing data.. 2015-07-22 20:55:45,186 http-8080-Processor22 INFO [jira.action.admin.DataImport] Start parsing XML with SAX Parser 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] XML successfully parsed 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] Removing all entries from the database. 2015-07-22 20:56:24,593 http-8080-Processor22 INFO [jira.action.admin.DataImport] All entries removed. 2015-07-22 20:56:24,594 http-8080-Processor22 INFO [jira.action.admin.DataImport] Started storing 410414 Generic Values 2015-07-22 21:01:51,967 http-8080-Processor22 INFO [jira.action.admin.DataImport] Finished storing Generic Values 2015-07-22 21:01:52,329 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:52,361 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:54,683 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLink' to module 'jira.user.format:profile-link-user-format'. 2015-07-22 21:01:54,724 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullName' to module 'jira.user.format:full-name-user-format'. 2015-07-22 21:01:54,773 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkSearcher' to module 'jira.user.format:profile-link-searcher-user-format'. 2015-07-22 21:01:54,784 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkExternal' to module 'jira.user.format:profile-link-external-user-format'. 2015-07-22 21:01:54,795 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkActionHeader' to module 'jira.user.format:profile-link-action-header-user-format'. 2015-07-22 21:01:54,807 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullProfile' to module 'jira.user.format:full-profile-user-format'. 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/comments 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/issues 2015-07-22 21:01:55,641 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/plugins 2015-07-22 21:01:55,867 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:01:55,871 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/issues does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:55,873 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/comments does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,033 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,257 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,889 http-8080-Processor22 ERROR [atlassian.jira.upgrade.ConsistencyCheckImpl] Attachments are turned on, but attachment path [/data/jira_3_12/attachments] invalid - disabling attachments 2015-07-22 21:02:13,904 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Detected that an upgrade is needed; existing data at build 299 2015-07-22 21:02:13,907 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Doing Upgrade... 2015-07-22 21:02:13,915 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value' succeeded 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 317 2015-07-22 21:02:13,944 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite filters - make each filter a favourite of its owner. 2015-07-22 21:02:17,822 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build319] Could not find author 'fpy' for filter with id '10040' 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite filters - make each filter a favourite of its owner.' succeeded 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 319 2015-07-22 21:02:17,995 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise Share Permissions. Move old shares to new shares. 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise Share Permissions. Move old shares to new shares.' succeeded 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 321 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Migrating the old JIRA UI colors to the new JIRA 3.13 colors 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build322] Custom color detected for jira.lf.menu.bgcolour : #336699 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Migrating the old JIRA UI colors to the new JIRA 3.13 colors' succeeded 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 322 2015-07-22 21:02:18,025 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite dashboards - make each dashboard a favourite of its owner. 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'cmcgann' for dashboard with id '10030' 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'fpy' for dashboard with id '10060' 2015-07-22 21:02:18,423 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'kanna' for dashboard with id '10040' 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite dashboards - make each dashboard a favourite of its owner.' succeeded 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 325 2015-07-22 21:02:18,625 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Reindexing all data in JIRA to include Favourites. 2015-07-22 21:02:18,648 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All starting... 2015-07-22 21:02:18,650 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 0% complete. Current index: Issue 2015-07-22 21:02:18,654 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:02:18,809 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 1% complete. Current index: Issue 2015-07-22 21:02:18,855 indexerPool-2-thread-10 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 2% complete. Current index: Issue 2015-07-22 21:02:18,899 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 3% complete. Current index: Issue 2015-07-22 21:02:18,945 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 4% complete. Current index: Issue 2015-07-22 21:02:19,012 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 5% complete. Current index: Issue . . . 2015-07-22 21:02:26,164 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 95% complete. Current index: Issue 2015-07-22 21:02:26,232 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 96% complete. Current index: Issue 2015-07-22 21:02:26,316 indexerPool-2-thread-9 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 97% complete. Current index: Issue 2015-07-22 21:02:26,771 indexerPool-2-thread-3 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: Issue 2015-07-22 21:02:27,261 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 8607ms. Indexer: DefaultIndexManager: paths: [/data/jira3135/indexes/issues, /data/jira3135/indexes/comments] 2015-07-22 21:02:27,263 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: SearchRequest 2015-07-22 21:02:27,268 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,293 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: SearchRequest 2015-07-22 21:02:27,308 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: PortalPage 2015-07-22 21:02:27,312 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,377 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: PortalPage 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 115ms. Indexer: SharedEntityIndexManager: paths: [/data/jira3135/indexes/entities/portalpage, /data/jira3135/indexes/entities/searchrequest] 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All complete. Total time: 8722ms. 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Reindexing all data in JIRA to include Favourites.' succeeded 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 326 2015-07-22 21:02:27,397 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade succeeded! Setting data build number to 360 2015-07-22 21:02:27,469 JiraQuartzScheduler_Worker-0 WARN [service.services.export.ExportService] Backup directory /data/jira_3_12/backup does not exist {noformat} {warning:title=Paths} It appears that the upgraded JIRA will still look for the attachments and the backup locations in the original places. So I created /data/jira_3_12/backup and untarred the original attachments to /data/jira_3_12 and then everything worked (including attachements) in the new JIRA. {warning} ## (/) I then used the upgraded JIRA to generate a new XML backup and stored it in /data/original/3.13.5 along with another tar of the files in /data/jira_3_12/attachments. ## (/) I then shutdown the JIRA server. *I should be ready to move on to version 4 upgrade WHEW* ## So, before moving on, I decided that it would be a really good idea to spin up a new Crowd instance to get rid of the :8443 in the URL and to move off of RedHat per IS requests. I have a ticket in for a new VM and a new database to try to get this going. I am waiting on that before moving on. ## (/) Pat created the VM and Neil created the database. ## (/) I logged into auth.mbari.org (name of the VM) and downloaded crowd which I unzipped to the /opt directory ## (/) I then created a /data/crowd directory and gave my account permissions on it and then edited the /opt/atlassian..../crowd-webapp/WEB-INF/classes/crowd-init.properties file to set that as the crowd home directory. ## (/) The instructions say to download the JDBC driver, but they already have JTDS 1.2.7 in the download so I did not do anything. ## (/) You have to manually connect up CrowdID to a database as they setup wizard does not currently do this. ### (/) They say to download the driver, but again 1.2.7 was there so I did nothing. ### (/) I edited the /opt/atlassian.../apache-tomcat/conf/Catalina/localhost/openidserver.xml to look like: {noformat} {noformat} ### (/) I edited the /opt/atlassian.../build.properties files to look like: {noformat} # Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See https://confluence.atlassian.com/display/CROWD/Connecting+Crowd+to+a+Database hibernate.dialect=org.hibernate.dialect.SQLServerDialect # The Hibernate transaction factory to use. See https://confluence.atlassian.com/display/CROWD/Configuring+Crowd hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory # The http port you wish to run crowd from, ie: http://localhost:8095/crowd crowd.tomcat.connector.port=8095 # Tomcat requires a unique port for shutdown crowd.tomcat.shutdown.port=8020 # Crowd context root crowd.url=http://localhost:8095/crowd # Demo context root demo.url=http://localhost:8095/demo # OpenID server context root openidserver.url=http://localhost:8095/openidserver {noformat} ### (/) I then ran the build.sh script in the root of /opt/atlassian... ## (/) I fired up crowd using the /opt/atlassian.../start_crowd.sh script ## (/) I then went to http://auth.mbari.org:8095/crowd to kick off the start up wizard ## (/) I grabbed a new eval license from my account on atlassian and pasted into the license page. ## (/) I selected "New install" on the next page. ## (/) I configured the JDBC connection using this connection URL with user DB_Collaboration {noformat} jdbc:jtds:sqlserver://dione.mbari.org:51001/Crowd;domain=SHORE;useNTLMv2=TRUE {noformat} ## (/) I left the "Options" as they came up {warning:title=Paths} Not sure if this is a problem, but because I started the set up using auth.mbari.org, it set the Base URL to http://auth.mbari.org:8095/crowd instead of localhost. Hope that is not a problem. We will see. {warning} ## (/) I configured the email connection using the settings from [here|https://wind.shore.mbari.org/is/howto/email/mbarimail/imap] and I used my network login (probably shouldn't be doing that ... not sure where it stores my password, but I am assuming in the DB). ## (/) For the local admin account, I created a user named 'crowdadm' so it would not clash with my LDAP account. See Kevin Gomes for password information. ## (/) I checked the OpenID server as an integrated application ## (/) It then took me to the login page and I logged in using the newly minted admin account. Seemed all is well so far. ## (/) I visited the openidserver URL as well and that seemed OK. ## (/) I decided to wait on configuring the MBARI LDAP directory until I got everything with SSL working. ## (/) Now the next step was to follow the directions to configure Crowd to run over SSL found [here|https://confluence.atlassian.com/display/CROWD/Configuring+Crowd+to+Work+with+SSL] ## (/) I shutdown crowd. Note that the stop script does not shutdown things correctly and I noticed the crowd app running as root. That should not be if I started as kgomes. Not sure what is up with that. ## (/) Now Joe had already configured SSL once, so I used his connector configuration in the server.xml file and so the final file looked like: {noformat} {noformat} ## (/) I then edited the /data/crowd/crowd.properties to look like: {noformat} #Sat Aug 01 09:05:15 PDT 2015 session.lastvalidation=session.lastvalidation session.tokenkey=session.tokenkey crowd.server.url=https\://localhost\:8443/crowd/services/ application.name=crowd http.timeout=30000 session.isauthenticated=session.isauthenticated application.login.url=https\://localhost\:8443/crowd/console/ session.validationinterval=0 application.password=Y1Xp3OorCmsOP4eruL1dmH {noformat} One thing to note here is that based on a comment from the SSL configuration page at atlassian (Steve's comment), you are supposed to leave all the host names the same. For example, if the file says localhost, leave it localhost. So this created a bit of a problem based on the fact that I had left the base URL pointing to auth.mbari.org in the wizard steps above. That step wrote auth.mbari.org to the /data/crowd/crowd.properties. All the other files reference localhost, so to be consistent, I changed auth.mbari.org to localhost in the /data/crowd/crowd.properties file. We will see if this works. ## (/) Per the instructions on the atlassian page (referenced above), I also edited the build.properties file and the /client/conf/crowd.properties files before I restarted and used the SSL URLs ## build.properties: {noformat} # Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See https://confluence.atlassian.com/display/CROWD/Connecting+Crowd+to+a+Database hibernate.dialect=org.hibernate.dialect.SQLServerDialect # The Hibernate transaction factory to use. See https://confluence.atlassian.com/display/CROWD/Configuring+Crowd hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory # The http port you wish to run crowd from, ie: http://localhost:8095/crowd crowd.tomcat.connector.port=8095 # Tomcat requires a unique port for shutdown crowd.tomcat.shutdown.port=8020 # Crowd context root crowd.url=https://localhost:8443/crowd # Demo context root demo.url=https://localhost:8443/demo # OpenID server context root openidserver.url=https://localhost:8443/openidserver {noformat} ## crowd.properties (client) {noformat} application.name crowd application.password password application.login.url https://localhost:8443/crowd/console/ crowd.server.url https://localhost:8443/crowd/services/ crowd.base.url https://localhost:8443/crowd/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 2 session.lastvalidation session.lastvalidation {noformat} ## (/) Although not stated, I am assuming you would need to run the build.sh script to push the build.properties changes to their proper places, so I did that. Note that before doing that, I know that it will clobber the server.xml changes I made, so I made a copy of that file and diff'd them after and then rolled the previous changes to the new server.xml file. Actually, amazingly enough, it seems to have done the connector entry correctly so I left it after running the build.sh script. ## (/) Crossed my fingers and then restarted crowd. I tailed the catalina.out file and did not see any stack traces so that is a good sign! ## (/) I visited https://auth.mbari.org:8443/crowd first. It could not find that page, but I suspect that is because I am browsing from the outside, so I tried just https://auth.mbari.org/crowd and got a service unavailable. I am suspecting that this is a combination of firewall and proxy pass and I will send this info to Joe. From what I can see on the crowd side, it seems like the server started cleanly, we just can't get to it. I tried to reach it from a browser on the machine itself too (through VNC) with the same service not available. ## (/) Here are the notes from Joe after he fixed it! Wooohooo! {noformat} Hey Kevin, Thanks for starting clean! I had to make a few adjustments. 1-I modified the server.xml file in /opt/atlassian-crowd-2.8.3/apache-tomcat/conf/server.xml so there are two connectors per the instructions on the Atlassian site. I have backed up this good server.xml file in /etc/temp/ if you want to browse it to see what I did. Of note is that I removed all the jargon referencing the types of ciphers available to simplify things for now. 2-I modified /data/crowd/crowd.properties to have crowd.server.url=https\://localhost\:8443/crowd/services/ application.login.url=https\://localhost\:8443/crowd/console/ But that would cause my login to error with an error saying it was unable to reach the authentication server. I scratched my head for a bit. When I revert the values to just using non-SSL and try to log in, I just get an "invalid login" (I don't know the crowdadm password). So I worked under the assumption that if I can configure SSL to get an "invalid login" when logging in then it would work when provided real credentials. So, I then changed /data/crowd/crowd.proprties to: crowd.server.url=https\://auth.mbari.org\:8443/crowd/services/ application.login.url=https\://auth.mbari.org\:8443/crowd/console/ And now when I try to log in with SSL it says "invalid login". Strange because all the other values I can find only show "localhost" .. in any case... Can you try to log in now? {noformat} ## (/) Next I moved on to configuring the connection to MBARI's LDAP server to enable our logins through Crowd and CrowdID ## (/) I clicked on "Add Directory" in crowd. ## (/) I selected "Connector" then clicked Next ## (/) I put ldap.shore.mbari.org as the name of the server ## (/) I selected "Use memberOf for group memberships" ## (/) I used "OU=AllUsers,DC=shore,DC=mbari,DC=org" for the Base DN ## (/) I used "CN=LDAPbind,OU=Special,OU=AllUsers,DC=shore,DC=mbari,DC=org" for the Username (talk to Pat Allen for password) ## (/) I tested the connection (button click) and it passed. ## (/) I de-selected all the capabilities of the connector as it is a ready only connector and then saved it. It synchronized correctly! ## (/) At first, I could not login using my MBARI credentials, but after going to the "crowd" application in crowd (logged in as the local admin), I had to add the LDAP directory and configure it to "Allow all to authenticate", then I was able to login. After this, the last step was to get this to run as a different user and lock down various directories. I went through the entire directory structure /opt/atlassian... and set up so that root owned all read-only locations and DB_Collaboration (account set up by IS) owned the other stuff. I also gave full ownership to the /data/crowd directory to DB_Collaboration so it could write there. Pat set up a script to start on boot and after a little tweaking, it now starts on boot. {warning:title=CrowdID log file} One thing that came up here was that when the crowdID application ran, it tried to write a log file to the location where the process was launched from (which is /opt/atlassian...). This is a bad thing and I figured out that I could change that location by changing the file /opt/atlassian-crowd-2.8.3/crowd-openidserver-webapp/WEB-INF/classes/log4j.properties and hardcoding the /data/crowd/logs/atlassian-crowd-openid-server.log and then restarted the application. {warning} ## (/) Another note is the when an application tried to use the OpenID application, it would get redirected to localhost. I changed the /opt/atlassian.../crowd-openidserver-webapp/WEB-INF/classes/crowd.properties file to look like: {noformat} #Sat Aug 01 10:03:18 PDT 2015 session.lastvalidation=session.lastvalidation session.tokenkey=session.tokenkey crowd.server.url=http\://localhost\:8095/crowd/services/ application.name=crowd-openid-server #application.login.url.template=http\://localhost\:8095/openidserver?returnToUrl\=${RETURN_TO_URL} application.login.url.template=https\://auth.mbari.org/openidserver?returnToUrl\=${RETURN_TO_URL} session.isauthenticated=session.isauthenticated #application.base.url=http\://localhost\:8095/openidserver application.base.url=https\://auth.mbari.org/openidserver #application.login.url=http\://localhost\:8095/openidserver application.login.url=https\://auth.mbari.org/openidserver session.validationinterval=0 application.password=password {noformat} and that seems to have fixed it. # (/) It is finally time to move on to the version 4 upgrade ... holy crap. I first went to the *new* crowd install (auth.mbari.org) and logged in as the crowdadm. # (/) I clicked on Applications, then on Add Application # (/) I selected JIRA from the Application type drop-down # (/) I entered jira445 as the username. Ask Kevin about the password. # (/) I used http://bugs.shore.mbari.org:8081 as the URL # (/) I used 134.89.12.31 as the IP address. # (/) I selected only the MBARI LDAP directory. # (/) Then I selected "Allow all users to authenticate" # (/) Then I clicked on "Add Application" # (/) I VNC'd into bugs.mbari.org. As it turns out, for Linux, there is an installer program to download. I downloaded the .bin for 64 bit Linux installer and moved it to the jira-upgrade directory. # (/) I chmod'd the file to make it executable and ran it. It gave me a warning about not being root, but I went ahead with it. # (/) It asked for the JIRA home and data directory, which I specified as /opt/jira4 and /data/jira445. # (/) For the ports, I specified 8180 and 8105 (HTTP and control respectively). It then extracted all the files and launched JIRA. It said if finished, so I opened a local browser to http://localhost:8180 which kicked off the start up wizard. # (/) I specified the external database using: ## solstice2.shore.mbari.org (server) ## 1433 (port) ## jira4 (database) ## DB_Collaboration (username) ## (password ask Kevin) ## dbo (schema) # But all this failed as it seems to just want to try and use the SQL server authentication instead of domain. I will have to do it manually. # (/) I stopped the server using the bin/stop-jira.sh script. # (/) I created and edited /data/jira445/dbconfig.xml and made it look like the following: {noformat} ?xml version="1.0" encoding="UTF-8"?> defaultDS default mssql jiraschema jdbc:jtds:sqlserver://solstice2.shore.mbari.org:1433/Jira4;domain=SHORE;useNTLMv2=true net.sourceforge.jtds.jdbc.Driver DB_Collaboration (ask Kevin) 15 {noformat} # (/) I then started it again using bin/start-jira.sh and tailed the catalina.out file. Got a bunch of errors related to the schema 'jiraschema', I edited the file and changed the schema to 'dbo' and restarted. That seemed to do it. There was one stack trace for some iCal plugin, but looks OK other than that. # I browsed back to localhost:8180 and the wizard moved to step 2. There was an option to import existing data bit without the crowd connection, I thought I should set it up manually, connect to crowd, then import. I generated an evaluation license, called the app "MBARI JIRA4" and change the server in the url to bugs.shore.mbari.org # For the admin, I created an account called 'jiraadm' (ask Kevin for password). # Since this is a temporary system, I left the email system disabled. # I logged in as jiraadm, went to Administration, then Users, then clicked on Add Directory and chose Atlassian Crowd. Note that I had to set the server URL to http://auth.mbari.org:8095/crowd or I would have had to configure all this SSL crap that I did not want to do for this temporary install. # It tested successfully, I clicked Save and it went through a 13 second sync, whew! # I then went to System->Import and Export->Restore System # I copied the jira-upgrade-3.13.5.zip file from the previous version export into /data/jira445/import and then entered that file name along with the new evaluation license again. # I worked through progress bar after I clicked on Restore (it took a really long time). # I then stopped, restarted and tailed the log file. # I am thinking now I should have put the attachments in the import attachments directory, but I am hoping I can just copy them to the data/attachments directory. # UG! I got some error during the import. The exception read: "JIRA is unable to migrat the User Directory configuration because external users exist but the osuser.xml file is not available". It then gave me a link to a doc that talked about making the old user files available before the upgrade ... crap. So I needed to copy the osuser.xml and crowd.properties file from atlassian-jira/WEB-INF/classes directory on the old install to the same directory on the new install ... sigh. This means I am going to blow away everything and start over. # I shutdown jira4 # I dropped all things in the database and deleted all content in the /data/jira445 directory (except for the dbconfig.xml file). # I also removed the temp, logs (actually you have to leave the directory, just clear the files) and the work/Catalina/localhost directories from the jira installation. # I then copied the osuser.xml and the crowd.properties files from the 3.13.5 install to the 4 install. # I edited the crowd.properties file in hopes that I could point it to the new crowd install on auth.mbari.org and it would work, but we will see. # I then started jira and tailed the log file. # All looked OK (other than iCal plugin stack trace again), so I went to localhost:8180 and got step 2 of the wizard. I used the same info as before. # I logged in as the local admin account and it looks like the system picked up the crowd connection, but lets see what server it used! Hey it used the one I edited into the file! Sweet ... now let's see if the import works. # I copied the 3.13.5 zip file to the import directory again and this time, I untarred the attachments into the import/attachments directory. # I kicked off the restore as before and it worked through it fine. # Shutdown and restarted system, tailing the log file and then went to localhost:8180 # I can see issues (before logging in) and it all looks good!! The attachments did not move over from the import directory, so I copied the tar file from /data/jira445/import to /data/jira445/data and then untarred it there, then removed the tar file and the import zip file from the import directory. # Now I will try to login using my MBARI account and OMG it actually worked!!! (it even gave my kgomes account Admin privs) # I then performed an export and copied those file to the /data/backups/4.4.5 directory (also created a TAR of the attachments and put there too). # Now on to version 5! # OK, so something strange is happening. After the imports, the server ID goes back to the one that is on our current production server, which must mean it is using our current license key (which does not match the server ID, BTW). Oh well, I will press on! # I created a /data/jira5211 directory as well as a /opt/jira5 directory. Knowing what I know now and reading through the install instructions, it appears that I need to create a dbconfig.xml file manually, so I did that using: {noformat} defaultDS default mssql dbo jdbc:jtds:sqlserver://solstice2.shore.mbari.org:1433/Jira5;domain=SHORE;useNTLMv2=true net.sourceforge.jtds.jdbc.Driver DB_Collaboration (ask Kevin) 20 20 30000 20 true 300 select 1 60000 300000 true false {noformat} # I then changed the mode to executable on the installer download and ran that. # I had to choose a "custom install" this time through, but the properties were similar after that (ports I used were 8280 and 8205) # I then browsed to localhost:8280 # I dropped me to a wizard where I define the title as "MBARI JIRA5", and changed host to bugs.shore.mbari.org (from localhost) # This license was a little different in that is just asked for my Atlassian username and password and fetched a new license for me. # For the admin account, I used the same 'jiraadm' account # Left email notification disabled. # I created a new application in crowd for JIRA 5 and used same account info as for 4. # In JIRA, I went to Administration->Users->User Directories and then added a directory as I had done before. # All went well and the sync happened. # I then went to Administration->System->Import and Export->Restore System # I copied the backup of 4.4.5 to the /data/jira5211/import directory and then specified that file name. I did not specify a license as it seems to use the old one and it said so in the text below the box. # Clicked on restore and while it was restoring, I untarred the attachments to the /data/jira5211/data directory # After the restore, I shutdown and restarted JIRA tailing the log file. # Browsed to localhost:8280 and ... success! I see issues before logging in and ... my MBARI login worked, I was admin and all is good!!!! # As with previous version, I ran a backup of the DB and attachments and placed in /data/backups/5.2.11 # I poked around a little and there seems to be an issue in the comments that they are still referencing oceana??? I will have to look into this. # I then re-did the process once again for version 6.4.9. I will only put notes about things that are dramatically different below: ## It looks like the dbconfig.xml file is the same as it is for version 5, so I just copied and edited to point to Jira6 DB. ## I used ports 8380 and 8305 {warning:title=Collation} The DB needs to be using a specific collation that it's not, I will have to correct that on the production run {warning} ## It gave me a choice on "how I wanted to use JIRA" and I chose the default (top) one which was just JIRA. ## Something did not go well on the restore (got to 90%) from backup up and the server seems to have crashed, but it looks like it tried to restart? ## I forced a stop and start and tailed the log file. Could it be related to the collation issue? Upon restart it re-ran the indexing. Looks like it worked OK, let me login with my MBARI account. ## Interesting, the comments pointing to oceana seems to have fixed itself in the step of the upgrade. ]]> 27558206 27590972 4.4: [https://confluence.atlassian.com/display/JIRA044/Migrating+JIRA+to+Another+Server] ## The JIRA configuration tool: [https://confluence.atlassian.com/display/JIRA044/Using+the+JIRA+Configuration+Tool] h5. Steps # (/) Create new VM named bugs.mbari.org in the DMZ # (/) Have Neil create database Jira_Temp on solstice2.shore.mbari.org # (/) Have Neil create database Jira on solstice2.shore.mbari.org # (/) Have Pat install Java 7 on bugs.shore.mbari.org # (/) Have Pete plumb holes through firewall so processes on bugs.mbari.org can get to Solstice2 # (/) Have Pat create DB_Collaboration account on bugs so it can run JIRA under that account and it can connect to solstice2 using that NT Domain account. # (/) Upgrade license on Atlassian site # (/) Log into bugs.shore.mbari.org # (/) Download 3.13.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 4.4.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 5.2.11 standalone Linux 64 bit tar.gz (not sure this version is necessary, but at least I have it) # (/) Unzip and untar the file to /opt # (/) Download latest JIRA (6.4.7 as of this writing). # (/) Unzip and untar it to /opt # Performed Test Upgrade ## (/) In order to export the current stuff in JIRA, I had to shut off access so people could not change the data while I was backing it up. ## (/) I ssh'd to oceana.mbari.org as root and edited the /opt/jira/conf/server.xml file and commented out the Connector section that had the port of 8010 to shut it off from the normal serving route. ## (/) I uncommented the 8082 port connector and the 8443 port connector so that I could still get to the server. ## (/) I stopped and started the JIRA server and in the log file I got a "keystore was tampered with..." which is not surprising. ## (/) I could then browser over to http://oceana.mbari.org:8082/jira ## (/) Then through the Administration console, I did an XML backup ## (/) I then created a tar of all the attachments in the /data/jira_3_12/attachments directory ## (/) I moved both the XML and tar files to the /root/jira-upgrade directory ## (/) I then reversed the changes to the server.xml file and shut down JIRA ## (/) I left it down during the next steps in case it went so well, I could just point people to the new server (yeah, right). ## (/) I then browsed to the crowd server on oceana and add a new application using: ### URL: http://bugs.mbari.org/jira3135 ### IP: 134.89.2.29 ### Name: JIRA3135 ### Password: (ask Kevin) :) ## (/) On bugs, I made a copy of the JIRA 3.13.5 download in the /opt directory and unzipped and untarred it. ## (/) In order to configure the crowd connection I did the following: ### (/) I scp'd the /opt/crowd/client/crowd-integration-client-1.6.jar file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I removed the existing 1.6.1 crowd client jar from the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I scp'd the /opt/crowd/client/conf/crowd.properties file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I scp'd the /opt/crowd/client/conf/crowd-ehcache.xml file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I edited the crowd.properties file on bugs to look like: {noformat} application.name JIRA3135 application.password (ask Kevin) application.login.url http://oceana.mbari.org:8095/crowd/console/ crowd.server.url http://oceana.mbari.org:8095/crowd/services/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 0 session.lastvalidation session.lastvalidation {noformat} ### (/) I edited the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/osuser.xml file to comment out the current authentication mechanism and then uncomment the crowd one. ## (/) I then edited the /opt/atlassian-jira-standalone-3.13.5/conf/server/xml file and configured the database connection to the Jira_Temp database on Solstice2. I looked like this: {noformat} {noformat} ## (/) Edit the /opt/atlassian/jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/entityengine.xml and changed it from 'hsql' to 'mssql' and delete the line with "PUBLIC" in it per the instructions in the comments in that file. ## (/) I edited the /etc/httpd/conf/httpd.conf file and created a proxy pass at the bottom of the file to point a normal URL to the default port 8080 for JIRA: {noformat} # Proxy Pass for JIRA ProxyPass http://bugs.mbari.org:8080 ProxyPassReverse http://bugs.mbari.org:8080 {noformat} ## (/) I restarted Apache ## (/) I scp'd the jtds driver from oceana to the /opt/atlassian-jira-standalone-3.13.5/common/lib directory (you could down from the internet) ## (/) I then went to the /opt/atlassian-jira-standalone-3.13.5/ directory and ran './bin/startup.sh'. From the log file, I could tell things were hanging. After some troubleshooting I am wondering if the local firewall is preventing the application to get access to the database on solstice2. I can telnet to port 1433, but I can't browse to the base http://bugs.mbari.org from anywhere but the local web browser. I have submitted a ticket. ## (/) I restarted the old JIRA with my hopes dashed :(. ## (/) Pat disabled the firewall on bugs.mbari.org but it still hung trying to connect to solstice2.shore.mbari.org. That is really, really perplexing. Neil mentioned that solstice2 is using Kerberos and solstice is not. Checking with the JTDS docs, version 1.3.1 of the driver added kerberos support, so I downloaded that driver and added the 'userKerberos=true' property to the URL in the server.xml file and restarted. Got an error about no credentials, so added user and password properties to the URL. Nope, no luck. Never did figure this one out, but I had Pat pull the VM inside the firewall and after some thrash it worked. Well, it sort of worked ... sigh. It turns out I had downloaded the standard version instead of the enterprise version. I need to redo this work ... grrr. ## (/) I deleted all the tables in the Jira_Temp database and removed the /data/jira3135/indexes directory (and recreated). ## (/) I downloaded the enterprise version of the 3.13.5 server. I made a copy in the /opt directory and unzipped and untarred the file. ## (/) I went back to crowd and edited the application to change the properties to: ### URL: http://bugs.shore.mbari.org:8080 ### IP: 134.89.12.31 ### Name: jira3135 ### Password: (ask Kevin) :) ## (/) I then repeated the steps above to get the server up and running with the following differences: ### The server name is now bugs.shore.mbari.org ### The paths given above are a little different in that they no longer say "standard" but say "enterprise" ### I deleted the proxy pass as it seemed to have issues before and this is only temporary anyway. ## (/) I then browsed to http://bugs.shore.mbari.org:8080 ## (/) It took me to the start up page and at the top was the option to 'import your existing data'. Seemed too good not to try. I clicked on the link. It asked me for the backup file location and the location where the indexes would be stored. ## (/) I copied the XML zip file and the attachments tar file to the /data/original directory. ## (/) I created the /data/jira3135/indexes and used those directories ... it fired off the import and I waited. ## (/) I tailed the log file to watch the import. Holy crap, it worked!!! I could log in and everything! I copied the results from the log file here for posterity sake: {noformat} 2015-07-22 20:55:45,156 http-8080-Processor22 INFO [jira.action.admin.DataImport] Running data import 2015-07-22 20:55:45,179 http-8080-Processor22 INFO [jira.action.admin.DataImport] Importing data.. 2015-07-22 20:55:45,186 http-8080-Processor22 INFO [jira.action.admin.DataImport] Start parsing XML with SAX Parser 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] XML successfully parsed 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] Removing all entries from the database. 2015-07-22 20:56:24,593 http-8080-Processor22 INFO [jira.action.admin.DataImport] All entries removed. 2015-07-22 20:56:24,594 http-8080-Processor22 INFO [jira.action.admin.DataImport] Started storing 410414 Generic Values 2015-07-22 21:01:51,967 http-8080-Processor22 INFO [jira.action.admin.DataImport] Finished storing Generic Values 2015-07-22 21:01:52,329 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:52,361 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:54,683 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLink' to module 'jira.user.format:profile-link-user-format'. 2015-07-22 21:01:54,724 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullName' to module 'jira.user.format:full-name-user-format'. 2015-07-22 21:01:54,773 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkSearcher' to module 'jira.user.format:profile-link-searcher-user-format'. 2015-07-22 21:01:54,784 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkExternal' to module 'jira.user.format:profile-link-external-user-format'. 2015-07-22 21:01:54,795 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkActionHeader' to module 'jira.user.format:profile-link-action-header-user-format'. 2015-07-22 21:01:54,807 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullProfile' to module 'jira.user.format:full-profile-user-format'. 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/comments 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/issues 2015-07-22 21:01:55,641 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/plugins 2015-07-22 21:01:55,867 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:01:55,871 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/issues does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:55,873 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/comments does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,033 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,257 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,889 http-8080-Processor22 ERROR [atlassian.jira.upgrade.ConsistencyCheckImpl] Attachments are turned on, but attachment path [/data/jira_3_12/attachments] invalid - disabling attachments 2015-07-22 21:02:13,904 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Detected that an upgrade is needed; existing data at build 299 2015-07-22 21:02:13,907 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Doing Upgrade... 2015-07-22 21:02:13,915 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value' succeeded 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 317 2015-07-22 21:02:13,944 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite filters - make each filter a favourite of its owner. 2015-07-22 21:02:17,822 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build319] Could not find author 'fpy' for filter with id '10040' 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite filters - make each filter a favourite of its owner.' succeeded 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 319 2015-07-22 21:02:17,995 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise Share Permissions. Move old shares to new shares. 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise Share Permissions. Move old shares to new shares.' succeeded 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 321 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Migrating the old JIRA UI colors to the new JIRA 3.13 colors 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build322] Custom color detected for jira.lf.menu.bgcolour : #336699 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Migrating the old JIRA UI colors to the new JIRA 3.13 colors' succeeded 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 322 2015-07-22 21:02:18,025 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite dashboards - make each dashboard a favourite of its owner. 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'cmcgann' for dashboard with id '10030' 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'fpy' for dashboard with id '10060' 2015-07-22 21:02:18,423 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'kanna' for dashboard with id '10040' 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite dashboards - make each dashboard a favourite of its owner.' succeeded 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 325 2015-07-22 21:02:18,625 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Reindexing all data in JIRA to include Favourites. 2015-07-22 21:02:18,648 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All starting... 2015-07-22 21:02:18,650 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 0% complete. Current index: Issue 2015-07-22 21:02:18,654 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:02:18,809 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 1% complete. Current index: Issue 2015-07-22 21:02:18,855 indexerPool-2-thread-10 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 2% complete. Current index: Issue 2015-07-22 21:02:18,899 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 3% complete. Current index: Issue 2015-07-22 21:02:18,945 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 4% complete. Current index: Issue 2015-07-22 21:02:19,012 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 5% complete. Current index: Issue . . . 2015-07-22 21:02:26,164 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 95% complete. Current index: Issue 2015-07-22 21:02:26,232 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 96% complete. Current index: Issue 2015-07-22 21:02:26,316 indexerPool-2-thread-9 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 97% complete. Current index: Issue 2015-07-22 21:02:26,771 indexerPool-2-thread-3 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: Issue 2015-07-22 21:02:27,261 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 8607ms. Indexer: DefaultIndexManager: paths: [/data/jira3135/indexes/issues, /data/jira3135/indexes/comments] 2015-07-22 21:02:27,263 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: SearchRequest 2015-07-22 21:02:27,268 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,293 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: SearchRequest 2015-07-22 21:02:27,308 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: PortalPage 2015-07-22 21:02:27,312 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,377 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: PortalPage 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 115ms. Indexer: SharedEntityIndexManager: paths: [/data/jira3135/indexes/entities/portalpage, /data/jira3135/indexes/entities/searchrequest] 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All complete. Total time: 8722ms. 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Reindexing all data in JIRA to include Favourites.' succeeded 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 326 2015-07-22 21:02:27,397 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade succeeded! Setting data build number to 360 2015-07-22 21:02:27,469 JiraQuartzScheduler_Worker-0 WARN [service.services.export.ExportService] Backup directory /data/jira_3_12/backup does not exist {noformat} {warning:title=Paths} It appears that the upgraded JIRA will still look for the attachments and the backup locations in the original places. So I created /data/jira_3_12/backup and untarred the original attachments to /data/jira_3_12 and then everything worked (including attachements) in the new JIRA. {warning} ## (/) I then used the upgraded JIRA to generate a new XML backup and stored it in /data/original/3.13.5 along with another tar of the files in /data/jira_3_12/attachments. ## (/) I then shutdown the JIRA server. *I should be ready to move on to version 4 upgrade WHEW* ## So, before moving on, I decided that it would be a really good idea to spin up a new Crowd instance to get rid of the :8443 in the URL and to move off of RedHat per IS requests. I have a ticket in for a new VM and a new database to try to get this going. I am waiting on that before moving on. ## (/) Pat created the VM and Neil created the database. ## (/) I logged into auth.mbari.org (name of the VM) and downloaded crowd which I unzipped to the /opt directory ## (/) I then created a /data/crowd directory and gave my account permissions on it and then edited the /opt/atlassian..../crowd-webapp/WEB-INF/classes/crowd-init.properties file to set that as the crowd home directory. ## (/) The instructions say to download the JDBC driver, but they already have JTDS 1.2.7 in the download so I did not do anything. ## (/) You have to manually connect up CrowdID to a database as they setup wizard does not currently do this. ### (/) They say to download the driver, but again 1.2.7 was there so I did nothing. ### (/) I edited the /opt/atlassian.../apache-tomcat/conf/Catalina/localhost/openidserver.xml to look like: {noformat} {noformat} ### (/) I edited the /opt/atlassian.../build.properties files to look like: {noformat} # Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See https://confluence.atlassian.com/display/CROWD/Connecting+Crowd+to+a+Database hibernate.dialect=org.hibernate.dialect.SQLServerDialect # The Hibernate transaction factory to use. See https://confluence.atlassian.com/display/CROWD/Configuring+Crowd hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory # The http port you wish to run crowd from, ie: http://localhost:8095/crowd crowd.tomcat.connector.port=8095 # Tomcat requires a unique port for shutdown crowd.tomcat.shutdown.port=8020 # Crowd context root crowd.url=http://localhost:8095/crowd # Demo context root demo.url=http://localhost:8095/demo # OpenID server context root openidserver.url=http://localhost:8095/openidserver {noformat} ### (/) I then ran the build.sh script in the root of /opt/atlassian... ## (/) I fired up crowd using the /opt/atlassian.../start_crowd.sh script ## (/) I then went to http://auth.mbari.org:8095/crowd to kick off the start up wizard ## (/) I grabbed a new eval license from my account on atlassian and pasted into the license page. ## (/) I selected "New install" on the next page. ## (/) I configured the JDBC connection using this connection URL with user DB_Collaboration {noformat} jdbc:jtds:sqlserver://dione.mbari.org:51001/Crowd;domain=SHORE;useNTLMv2=TRUE {noformat} ## (/) I left the "Options" as they came up {warning:title=Paths} Not sure if this is a problem, but because I started the set up using auth.mbari.org, it set the Base URL to http://auth.mbari.org:8095/crowd instead of localhost. Hope that is not a problem. We will see. {warning} ## (/) I configured the email connection using the settings from [here|https://wind.shore.mbari.org/is/howto/email/mbarimail/imap] and I used my network login (probably shouldn't be doing that ... not sure where it stores my password, but I am assuming in the DB). ## (/) For the local admin account, I created a user named 'crowdadm' so it would not clash with my LDAP account. See Kevin Gomes for password information. ## (/) I checked the OpenID server as an integrated application ## (/) It then took me to the login page and I logged in using the newly minted admin account. Seemed all is well so far. ## (/) I visited the openidserver URL as well and that seemed OK. ## (/) I decided to wait on configuring the MBARI LDAP directory until I got everything with SSL working. ## (/) Now the next step was to follow the directions to configure Crowd to run over SSL found [here|https://confluence.atlassian.com/display/CROWD/Configuring+Crowd+to+Work+with+SSL] ## (/) I shutdown crowd. Note that the stop script does not shutdown things correctly and I noticed the crowd app running as root. That should not be if I started as kgomes. Not sure what is up with that. ## (/) Now Joe had already configured SSL once, so I used his connector configuration in the server.xml file and so the final file looked like: {noformat} {noformat} ## (/) I then edited the /data/crowd/crowd.properties to look like: {noformat} #Sat Aug 01 09:05:15 PDT 2015 session.lastvalidation=session.lastvalidation session.tokenkey=session.tokenkey crowd.server.url=https\://localhost\:8443/crowd/services/ application.name=crowd http.timeout=30000 session.isauthenticated=session.isauthenticated application.login.url=https\://localhost\:8443/crowd/console/ session.validationinterval=0 application.password=Y1Xp3OorCmsOP4eruL1dmH {noformat} One thing to note here is that based on a comment from the SSL configuration page at atlassian (Steve's comment), you are supposed to leave all the host names the same. For example, if the file says localhost, leave it localhost. So this created a bit of a problem based on the fact that I had left the base URL pointing to auth.mbari.org in the wizard steps above. That step wrote auth.mbari.org to the /data/crowd/crowd.properties. All the other files reference localhost, so to be consistent, I changed auth.mbari.org to localhost in the /data/crowd/crowd.properties file. We will see if this works. ## (/) Per the instructions on the atlassian page (referenced above), I also edited the build.properties file and the /client/conf/crowd.properties files before I restarted and used the SSL URLs ## build.properties: {noformat} # Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See https://confluence.atlassian.com/display/CROWD/Connecting+Crowd+to+a+Database hibernate.dialect=org.hibernate.dialect.SQLServerDialect # The Hibernate transaction factory to use. See https://confluence.atlassian.com/display/CROWD/Configuring+Crowd hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory # The http port you wish to run crowd from, ie: http://localhost:8095/crowd crowd.tomcat.connector.port=8095 # Tomcat requires a unique port for shutdown crowd.tomcat.shutdown.port=8020 # Crowd context root crowd.url=https://localhost:8443/crowd # Demo context root demo.url=https://localhost:8443/demo # OpenID server context root openidserver.url=https://localhost:8443/openidserver {noformat} ## crowd.properties (client) {noformat} application.name crowd application.password password application.login.url https://localhost:8443/crowd/console/ crowd.server.url https://localhost:8443/crowd/services/ crowd.base.url https://localhost:8443/crowd/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 2 session.lastvalidation session.lastvalidation {noformat} ## (/) Although not stated, I am assuming you would need to run the build.sh script to push the build.properties changes to their proper places, so I did that. Note that before doing that, I know that it will clobber the server.xml changes I made, so I made a copy of that file and diff'd them after and then rolled the previous changes to the new server.xml file. Actually, amazingly enough, it seems to have done the connector entry correctly so I left it after running the build.sh script. ## (/) Crossed my fingers and then restarted crowd. I tailed the catalina.out file and did not see any stack traces so that is a good sign! ## (/) I visited https://auth.mbari.org:8443/crowd first. It could not find that page, but I suspect that is because I am browsing from the outside, so I tried just https://auth.mbari.org/crowd and got a service unavailable. I am suspecting that this is a combination of firewall and proxy pass and I will send this info to Joe. From what I can see on the crowd side, it seems like the server started cleanly, we just can't get to it. I tried to reach it from a browser on the machine itself too (through VNC) with the same service not available. ## (/) Here are the notes from Joe after he fixed it! Wooohooo! {noformat} Hey Kevin, Thanks for starting clean! I had to make a few adjustments. 1-I modified the server.xml file in /opt/atlassian-crowd-2.8.3/apache-tomcat/conf/server.xml so there are two connectors per the instructions on the Atlassian site. I have backed up this good server.xml file in /etc/temp/ if you want to browse it to see what I did. Of note is that I removed all the jargon referencing the types of ciphers available to simplify things for now. 2-I modified /data/crowd/crowd.properties to have crowd.server.url=https\://localhost\:8443/crowd/services/ application.login.url=https\://localhost\:8443/crowd/console/ But that would cause my login to error with an error saying it was unable to reach the authentication server. I scratched my head for a bit. When I revert the values to just using non-SSL and try to log in, I just get an "invalid login" (I don't know the crowdadm password). So I worked under the assumption that if I can configure SSL to get an "invalid login" when logging in then it would work when provided real credentials. So, I then changed /data/crowd/crowd.proprties to: crowd.server.url=https\://auth.mbari.org\:8443/crowd/services/ application.login.url=https\://auth.mbari.org\:8443/crowd/console/ And now when I try to log in with SSL it says "invalid login". Strange because all the other values I can find only show "localhost" .. in any case... Can you try to log in now? {noformat} ## (/) Next I moved on to configuring the connection to MBARI's LDAP server to enable our logins through Crowd and CrowdID ## (/) I clicked on "Add Directory" in crowd. ## (/) I selected "Connector" then clicked Next ## (/) I put ldap.shore.mbari.org as the name of the server ## (/) I selected "Use memberOf for group memberships" ## (/) I used "OU=AllUsers,DC=shore,DC=mbari,DC=org" for the Base DN ## (/) I used "CN=LDAPbind,OU=Special,OU=AllUsers,DC=shore,DC=mbari,DC=org" for the Username (talk to Pat Allen for password) ## (/) I tested the connection (button click) and it passed. ## (/) I de-selected all the capabilities of the connector as it is a ready only connector and then saved it. It synchronized correctly! ## (/) At first, I could not login using my MBARI credentials, but after going to the "crowd" application in crowd (logged in as the local admin), I had to add the LDAP directory and configure it to "Allow all to authenticate", then I was able to login. After this, the last step was to get this to run as a different user and lock down various directories. I went through the entire directory structure /opt/atlassian... and set up so that root owned all read-only locations and DB_Collaboration (account set up by IS) owned the other stuff. I also gave full ownership to the /data/crowd directory to DB_Collaboration so it could write there. Pat set up a script to start on boot and after a little tweaking, it now starts on boot. {warning:title=CrowdID log file} One thing that came up here was that when the crowdID application ran, it tried to write a log file to the location where the process was launched from (which is /opt/atlassian...). This is a bad thing and I figured out that I could change that location by changing the file /opt/atlassian-crowd-2.8.3/crowd-openidserver-webapp/WEB-INF/classes/log4j.properties and hardcoding the /data/crowd/logs/atlassian-crowd-openid-server.log and then restarted the application. {warning} ## (/) Another note is the when an application tried to use the OpenID application, it would get redirected to localhost. I changed the /opt/atlassian.../crowd-openidserver-webapp/WEB-INF/classes/crowd.properties file to look like: {noformat} #Sat Aug 01 10:03:18 PDT 2015 session.lastvalidation=session.lastvalidation session.tokenkey=session.tokenkey crowd.server.url=http\://localhost\:8095/crowd/services/ application.name=crowd-openid-server #application.login.url.template=http\://localhost\:8095/openidserver?returnToUrl\=${RETURN_TO_URL} application.login.url.template=https\://auth.mbari.org/openidserver?returnToUrl\=${RETURN_TO_URL} session.isauthenticated=session.isauthenticated #application.base.url=http\://localhost\:8095/openidserver application.base.url=https\://auth.mbari.org/openidserver #application.login.url=http\://localhost\:8095/openidserver application.login.url=https\://auth.mbari.org/openidserver session.validationinterval=0 application.password=password {noformat} and that seems to have fixed it. # (/) It is finally time to move on to the version 4 upgrade ... holy crap. I first went to the *new* crowd install (auth.mbari.org) and logged in as the crowdadm. # (/) I clicked on Applications, then on Add Application # (/) I selected JIRA from the Application type drop-down # (/) I entered jira445 as the username. Ask Kevin about the password. # (/) I used http://bugs.shore.mbari.org:8081 as the URL # (/) I used 134.89.12.31 as the IP address. # (/) I selected only the MBARI LDAP directory. # (/) Then I selected "Allow all users to authenticate" # (/) Then I clicked on "Add Application" # (/) I VNC'd into bugs.mbari.org. As it turns out, for Linux, there is an installer program to download. I downloaded the .bin for 64 bit Linux installer and moved it to the jira-upgrade directory. # (/) I chmod'd the file to make it executable and ran it. It gave me a warning about not being root, but I went ahead with it. # (/) It asked for the JIRA home and data directory, which I specified as /opt/jira4 and /data/jira445. # (/) For the ports, I specified 8180 and 8105 (HTTP and control respectively). It then extracted all the files and launched JIRA. It said if finished, so I opened a local browser to http://localhost:8180 which kicked off the start up wizard. # (/) I specified the external database using: ## solstice2.shore.mbari.org (server) ## 1433 (port) ## jira4 (database) ## DB_Collaboration (username) ## (password ask Kevin) ## dbo (schema) # But all this failed as it seems to just want to try and use the SQL server authentication instead of domain. I will have to do it manually. # (/) I stopped the server using the bin/stop-jira.sh script. # (/) I created and edited /data/jira445/dbconfig.xml and made it look like the following: {noformat} ?xml version="1.0" encoding="UTF-8"?> defaultDS default mssql jiraschema jdbc:jtds:sqlserver://solstice2.shore.mbari.org:1433/Jira4;domain=SHORE;useNTLMv2=true net.sourceforge.jtds.jdbc.Driver DB_Collaboration (ask Kevin) 15 {noformat} # (/) I then started it again using bin/start-jira.sh and tailed the catalina.out file. Got a bunch of errors related to the schema 'jiraschema', I edited the file and changed the schema to 'dbo' and restarted. That seemed to do it. There was one stack trace for some iCal plugin, but looks OK other than that. # I browsed back to localhost:8180 and the wizard moved to step 2. There was an option to import existing data bit without the crowd connection, I thought I should set it up manually, connect to crowd, then import. I generated an evaluation license, called the app "MBARI JIRA4" and change the server in the url to bugs.shore.mbari.org # For the admin, I created an account called 'jiraadm' (ask Kevin for password). # Since this is a temporary system, I left the email system disabled. # I logged in as jiraadm, went to Administration, then Users, then clicked on Add Directory and chose Atlassian Crowd. Note that I had to set the server URL to http://auth.mbari.org:8095/crowd or I would have had to configure all this SSL crap that I did not want to do for this temporary install. # It tested successfully, I clicked Save and it went through a 13 second sync, whew! # I then went to System->Import and Export->Restore System # I copied the jira-upgrade-3.13.5.zip file from the previous version export into /data/jira445/import and then entered that file name along with the new evaluation license again. # I worked through progress bar after I clicked on Restore (it took a really long time). # I then stopped, restarted and tailed the log file. # I am thinking now I should have put the attachments in the import attachments directory, but I am hoping I can just copy them to the data/attachments directory. # UG! I got some error during the import. The exception read: "JIRA is unable to migrat the User Directory configuration because external users exist but the osuser.xml file is not available". It then gave me a link to a doc that talked about making the old user files available before the upgrade ... crap. So I needed to copy the osuser.xml and crowd.properties file from atlassian-jira/WEB-INF/classes directory on the old install to the same directory on the new install ... sigh. This means I am going to blow away everything and start over. # I shutdown jira4 # I dropped all things in the database and deleted all content in the /data/jira445 directory (except for the dbconfig.xml file). # I also removed the temp, logs (actually you have to leave the directory, just clear the files) and the work/Catalina/localhost directories from the jira installation. # I then copied the osuser.xml and the crowd.properties files from the 3.13.5 install to the 4 install. # I edited the crowd.properties file in hopes that I could point it to the new crowd install on auth.mbari.org and it would work, but we will see. # I then started jira and tailed the log file. # All looked OK (other than iCal plugin stack trace again), so I went to localhost:8180 and got step 2 of the wizard. I used the same info as before. # I logged in as the local admin account and it looks like the system picked up the crowd connection, but lets see what server it used! Hey it used the one I edited into the file! Sweet ... now let's see if the import works. # I copied the 3.13.5 zip file to the import directory again and this time, I untarred the attachments into the import/attachments directory. # I kicked off the restore as before and it worked through it fine. # Shutdown and restarted system, tailing the log file and then went to localhost:8180 # I can see issues (before logging in) and it all looks good!! The attachments did not move over from the import directory, so I copied the tar file from /data/jira445/import to /data/jira445/data and then untarred it there, then removed the tar file and the import zip file from the import directory. # Now I will try to login using my MBARI account and OMG it actually worked!!! (it even gave my kgomes account Admin privs) # I then performed an export and copied those file to the /data/backups/4.4.5 directory (also created a TAR of the attachments and put there too). # Now on to version 5! # OK, so something strange is happening. After the imports, the server ID goes back to the one that is on our current production server, which must mean it is using our current license key (which does not match the server ID, BTW). Oh well, I will press on! # I created a /data/jira5211 directory as well as a /opt/jira5 directory. Knowing what I know now and reading through the install instructions, it appears that I need to create a dbconfig.xml file manually, so I did that using: {noformat} defaultDS default mssql dbo jdbc:jtds:sqlserver://solstice2.shore.mbari.org:1433/Jira5;domain=SHORE;useNTLMv2=true net.sourceforge.jtds.jdbc.Driver DB_Collaboration (ask Kevin) 20 20 30000 20 true 300 select 1 60000 300000 true false {noformat} # I then changed the mode to executable on the installer download and ran that. # I had to choose a "custom install" this time through, but the properties were similar after that (ports I used were 8280 and 8205) # I then browsed to localhost:8280 # I dropped me to a wizard where I define the title as "MBARI JIRA5", and changed host to bugs.shore.mbari.org (from localhost) # This license was a little different in that is just asked for my Atlassian username and password and fetched a new license for me. # For the admin account, I used the same 'jiraadm' account # Left email notification disabled. # I created a new application in crowd for JIRA 5 and used same account info as for 4. # In JIRA, I went to Administration->Users->User Directories and then added a directory as I had done before. # All went well and the sync happened. # I then went to Administration->System->Import and Export->Restore System # I copied the backup of 4.4.5 to the /data/jira5211/import directory and then specified that file name. I did not specify a license as it seems to use the old one and it said so in the text below the box. # Clicked on restore and while it was restoring, I untarred the attachments to the /data/jira5211/data directory # After the restore, I shutdown and restarted JIRA tailing the log file. # Browsed to localhost:8280 and ... success! I see issues before logging in and ... my MBARI login worked, I was admin and all is good!!!! # As with previous version, I ran a backup of the DB and attachments and placed in /data/backups/5.2.11 # I poked around a little and there seems to be an issue in the comments that they are still referencing oceana??? I will have to look into this. # I then re-did the process once again for version 6.4.9. I will only put notes about things that are dramatically different below: ## It looks like the dbconfig.xml file is the same as it is for version 5, so I just copied and edited to point to Jira6 DB. ## I used ports 8380 and 8305 {warning:title=Collation} The DB needs to be using a specific collation that it's not, I will have to correct that on the production run {warning} ## It gave me a choice on "how I wanted to use JIRA" and I chose the default (top) one which was just JIRA. ## Something did not go well on the restore (got to 90%) from backup up and the server seems to have crashed, but it looks like it tried to restart? ## I forced a stop and start and tailed the log file. Could it be related to the collation issue? Upon restart it re-ran the indexing. Looks like it worked OK, let me login with my MBARI account. ## Interesting, the comments pointing to oceana seems to have fixed itself in the step of the upgrade. ## Another interesting note, when I went to the Admin->System->General configuration, it had the base URL as oceana, that would explain it. So I edited that to bugs.shore.mbari.org (it also made me change the Mode to private, which makes sense since authentication is external).]]> 27558208 3180065 3114598 19073848 3.4.10 (or latest) on alfresco-test.shore.mbari.org ## Tribloom to verify all is working properly ## MBARI to upgrade database on ?.shore.mbari.org from 2005 compatibility mode to 2008. ## Tribloom to verify all is working properly ## Tribloom to install/upgrade alfresco-test-rhel.shore.mbari.org from alfreso-test.shore.mbari.org ## Tribloom to verify all is working properly ## Tribloom to upgrade from 3.4.10 to 4.1.1 on alfresco-test-rhel.shore.mbari.org ## Tribloom to verify all is working properly ## Assuming all is well, proceed to production system ## Shutdown alfresco.mbari.org ## Backup database on equinox.shore.mbari.org ## Backup //atlas.shore.mbari.org/Alfresco/alf_data]]> 19041157 19073850 3.4.10 (or latest) on alfresco-test.shore.mbari.org ## Tribloom to verify all is working properly ## MBARI to upgrade database on ?.shore.mbari.org from 2005 compatibility mode to 2008. ## Tribloom to verify all is working properly ## Tribloom to install/upgrade alfresco-test-rhel.shore.mbari.org from alfreso-test.shore.mbari.org ## Tribloom to verify all is working properly ## Tribloom to upgrade from 3.4.10 to 4.1.1 on alfresco-test-rhel.shore.mbari.org ## Tribloom to verify all is working properly ## Assuming all is well, proceed to production system ## Shutdown alfresco.mbari.org ## Backup database on equinox.shore.mbari.org ## Backup //atlas.shore.mbari.org/Alfresco/alf_data ## Backup d:\alf_data\lucene-indexes on alfresco.mbari.org ## Tribloom to upgrade 2.1.1 -> 3.4.10 (or latest) on alfresco.mbari.org ## Tribloom to verify all is working properly. ## MBARI to upgrade database on equinox.shore.mbari.org from 2005 compatibility mode to 2008. ## Tribloom to verify all is working properly. ## Tribloom to install/upgrade alfresco-rhel.mbari.org from alfresco.mbari.org ## Tribloom to verify all is working properly. ## Tribloom to upgrade from 3.4.10 to 4.1.1 on alfresco-rhel.mbari.org ## Tribloom to verify all is working properly.]]> 19041159 19073844 19041153 19073846 19041155 19073856 19041165 27099734 ** response ** 0 * Channel 1 Power Control = 0 (Off) ** $1PC0 ** Response: ** 0 * Channel 1 Power Control = 1 (On) ** $1PC1 ** Response: ** 1 * Channel 1 Power Read ** $1PR ** Response: ** 1 * Read Block ** $1RB read temperature sensor block (4 channels) ** $5RB read pH sensor block (Seabird 18s) ** Response: ** \*+02712.00 ** \*+00200.00 ** \*+00125.76 ** \*+00347.95 * Read Data ** $1RD read tDGH channel 1 (temperature ch 1) ** $2RD read tDGH channel 2 (temperature ch 2) ** $3RD read tDGH channel 3 (temperature ch 3) ** $4RD read tDGH channel 4 (temperature ch 4) ** $5RD read tDGH channel 5 (pH sensor ch 1) ** $6RD read tDGH channel 6 (pH sensor ch 2) ** $7RD read tDGH channel 7 (pH sensor ch 3) ** $8RD read tDGH channel 8 (pH sensor ch 4) ** $9RD read tDGH channel 9 (pH sensor ch 5)]]> 27066973 27590925 4.4: [https://confluence.atlassian.com/display/JIRA044/Migrating+JIRA+to+Another+Server] ## The JIRA configuration tool: [https://confluence.atlassian.com/display/JIRA044/Using+the+JIRA+Configuration+Tool] h5. Steps # (/) Create new VM named bugs.mbari.org in the DMZ # (/) Have Neil create database Jira_Temp on solstice2.shore.mbari.org # (/) Have Neil create database Jira on solstice2.shore.mbari.org # (/) Have Pat install Java 7 on bugs.shore.mbari.org # (/) Have Pete plumb holes through firewall so processes on bugs.mbari.org can get to Solstice2 # (/) Have Pat create DB_Collaboration account on bugs so it can run JIRA under that account and it can connect to solstice2 using that NT Domain account. # (/) Upgrade license on Atlassian site # (/) Log into bugs.shore.mbari.org # (/) Download 3.13.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 4.4.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 5.2.11 standalone Linux 64 bit tar.gz (not sure this version is necessary, but at least I have it) # (/) Unzip and untar the file to /opt # (/) Download latest JIRA (6.4.7 as of this writing). # (/) Unzip and untar it to /opt # Performed Test Upgrade ## (/) In order to export the current stuff in JIRA, I had to shut off access so people could not change the data while I was backing it up. ## (/) I ssh'd to oceana.mbari.org as root and edited the /opt/jira/conf/server.xml file and commented out the Connector section that had the port of 8010 to shut it off from the normal serving route. ## (/) I uncommented the 8082 port connector and the 8443 port connector so that I could still get to the server. ## (/) I stopped and started the JIRA server and in the log file I got a "keystore was tampered with..." which is not surprising. ## (/) I could then browser over to http://oceana.mbari.org:8082/jira ## (/) Then through the Administration console, I did an XML backup ## (/) I then created a tar of all the attachments in the /data/jira_3_12/attachments directory ## (/) I moved both the XML and tar files to the /root/jira-upgrade directory ## (/) I then reversed the changes to the server.xml file and shut down JIRA ## (/) I left it down during the next steps in case it went so well, I could just point people to the new server (yeah, right). ## (/) I then browsed to the crowd server on oceana and add a new application using: ### URL: http://bugs.mbari.org/jira3135 ### IP: 134.89.2.29 ### Name: JIRA3135 ### Password: (ask Kevin) :) ## (/) On bugs, I made a copy of the JIRA 3.13.5 download in the /opt directory and unzipped and untarred it. ## (/) In order to configure the crowd connection I did the following: ### (/) I scp'd the /opt/crowd/client/crowd-integration-client-1.6.jar file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I removed the existing 1.6.1 crowd client jar from the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I scp'd the /opt/crowd/client/conf/crowd.properties file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I scp'd the /opt/crowd/client/conf/crowd-ehcache.xml file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I edited the crowd.properties file on bugs to look like: {noformat} application.name JIRA3135 application.password (ask Kevin) application.login.url http://oceana.mbari.org:8095/crowd/console/ crowd.server.url http://oceana.mbari.org:8095/crowd/services/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 0 session.lastvalidation session.lastvalidation {noformat} ### (/) I edited the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/osuser.xml file to comment out the current authentication mechanism and then uncomment the crowd one. ## (/) I then edited the /opt/atlassian-jira-standalone-3.13.5/conf/server/xml file and configured the database connection to the Jira_Temp database on Solstice2. I looked like this: {noformat} {noformat} ## (/) Edit the /opt/atlassian/jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/entityengine.xml and changed it from 'hsql' to 'mssql' and delete the line with "PUBLIC" in it per the instructions in the comments in that file. ## (/) I edited the /etc/httpd/conf/httpd.conf file and created a proxy pass at the bottom of the file to point a normal URL to the default port 8080 for JIRA: {noformat} # Proxy Pass for JIRA ProxyPass http://bugs.mbari.org:8080 ProxyPassReverse http://bugs.mbari.org:8080 {noformat} ## (/) I restarted Apache ## (/) I scp'd the jtds driver from oceana to the /opt/atlassian-jira-standalone-3.13.5/common/lib directory (you could down from the internet) ## (/) I then went to the /opt/atlassian-jira-standalone-3.13.5/ directory and ran './bin/startup.sh'. From the log file, I could tell things were hanging. After some troubleshooting I am wondering if the local firewall is preventing the application to get access to the database on solstice2. I can telnet to port 1433, but I can't browse to the base http://bugs.mbari.org from anywhere but the local web browser. I have submitted a ticket. ## (/) I restarted the old JIRA with my hopes dashed :(. ## (/) Pat disabled the firewall on bugs.mbari.org but it still hung trying to connect to solstice2.shore.mbari.org. That is really, really perplexing. Neil mentioned that solstice2 is using Kerberos and solstice is not. Checking with the JTDS docs, version 1.3.1 of the driver added kerberos support, so I downloaded that driver and added the 'userKerberos=true' property to the URL in the server.xml file and restarted. Got an error about no credentials, so added user and password properties to the URL. Nope, no luck. Never did figure this one out, but I had Pat pull the VM inside the firewall and after some thrash it worked. Well, it sort of worked ... sigh. It turns out I had downloaded the standard version instead of the enterprise version. I need to redo this work ... grrr. ## (/) I deleted all the tables in the Jira_Temp database and removed the /data/jira3135/indexes directory (and recreated). ## (/) I downloaded the enterprise version of the 3.13.5 server. I made a copy in the /opt directory and unzipped and untarred the file. ## (/) I went back to crowd and edited the application to change the properties to: ### URL: http://bugs.shore.mbari.org:8080 ### IP: 134.89.12.31 ### Name: jira3135 ### Password: (ask Kevin) :) ## (/) I then repeated the steps above to get the server up and running with the following differences: ### The server name is now bugs.shore.mbari.org ### The paths given above are a little different in that they no longer say "standard" but say "enterprise" ### I deleted the proxy pass as it seemed to have issues before and this is only temporary anyway. ## (/) I then browsed to http://bugs.shore.mbari.org:8080 ## (/) It took me to the start up page and at the top was the option to 'import your existing data'. Seemed too good not to try. I clicked on the link. It asked me for the backup file location and the location where the indexes would be stored. ## (/) I copied the XML zip file and the attachments tar file to the /data/original directory. ## (/) I created the /data/jira3135/indexes and used those directories ... it fired off the import and I waited. ## (/) I tailed the log file to watch the import. Holy crap, it worked!!! I could log in and everything! I copied the results from the log file here for posterity sake: {noformat} 2015-07-22 20:55:45,156 http-8080-Processor22 INFO [jira.action.admin.DataImport] Running data import 2015-07-22 20:55:45,179 http-8080-Processor22 INFO [jira.action.admin.DataImport] Importing data.. 2015-07-22 20:55:45,186 http-8080-Processor22 INFO [jira.action.admin.DataImport] Start parsing XML with SAX Parser 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] XML successfully parsed 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] Removing all entries from the database. 2015-07-22 20:56:24,593 http-8080-Processor22 INFO [jira.action.admin.DataImport] All entries removed. 2015-07-22 20:56:24,594 http-8080-Processor22 INFO [jira.action.admin.DataImport] Started storing 410414 Generic Values 2015-07-22 21:01:51,967 http-8080-Processor22 INFO [jira.action.admin.DataImport] Finished storing Generic Values 2015-07-22 21:01:52,329 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:52,361 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:54,683 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLink' to module 'jira.user.format:profile-link-user-format'. 2015-07-22 21:01:54,724 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullName' to module 'jira.user.format:full-name-user-format'. 2015-07-22 21:01:54,773 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkSearcher' to module 'jira.user.format:profile-link-searcher-user-format'. 2015-07-22 21:01:54,784 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkExternal' to module 'jira.user.format:profile-link-external-user-format'. 2015-07-22 21:01:54,795 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkActionHeader' to module 'jira.user.format:profile-link-action-header-user-format'. 2015-07-22 21:01:54,807 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullProfile' to module 'jira.user.format:full-profile-user-format'. 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/comments 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/issues 2015-07-22 21:01:55,641 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/plugins 2015-07-22 21:01:55,867 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:01:55,871 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/issues does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:55,873 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/comments does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,033 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,257 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,889 http-8080-Processor22 ERROR [atlassian.jira.upgrade.ConsistencyCheckImpl] Attachments are turned on, but attachment path [/data/jira_3_12/attachments] invalid - disabling attachments 2015-07-22 21:02:13,904 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Detected that an upgrade is needed; existing data at build 299 2015-07-22 21:02:13,907 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Doing Upgrade... 2015-07-22 21:02:13,915 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value' succeeded 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 317 2015-07-22 21:02:13,944 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite filters - make each filter a favourite of its owner. 2015-07-22 21:02:17,822 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build319] Could not find author 'fpy' for filter with id '10040' 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite filters - make each filter a favourite of its owner.' succeeded 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 319 2015-07-22 21:02:17,995 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise Share Permissions. Move old shares to new shares. 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise Share Permissions. Move old shares to new shares.' succeeded 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 321 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Migrating the old JIRA UI colors to the new JIRA 3.13 colors 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build322] Custom color detected for jira.lf.menu.bgcolour : #336699 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Migrating the old JIRA UI colors to the new JIRA 3.13 colors' succeeded 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 322 2015-07-22 21:02:18,025 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite dashboards - make each dashboard a favourite of its owner. 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'cmcgann' for dashboard with id '10030' 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'fpy' for dashboard with id '10060' 2015-07-22 21:02:18,423 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'kanna' for dashboard with id '10040' 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite dashboards - make each dashboard a favourite of its owner.' succeeded 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 325 2015-07-22 21:02:18,625 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Reindexing all data in JIRA to include Favourites. 2015-07-22 21:02:18,648 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All starting... 2015-07-22 21:02:18,650 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 0% complete. Current index: Issue 2015-07-22 21:02:18,654 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:02:18,809 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 1% complete. Current index: Issue 2015-07-22 21:02:18,855 indexerPool-2-thread-10 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 2% complete. Current index: Issue 2015-07-22 21:02:18,899 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 3% complete. Current index: Issue 2015-07-22 21:02:18,945 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 4% complete. Current index: Issue 2015-07-22 21:02:19,012 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 5% complete. Current index: Issue . . . 2015-07-22 21:02:26,164 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 95% complete. Current index: Issue 2015-07-22 21:02:26,232 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 96% complete. Current index: Issue 2015-07-22 21:02:26,316 indexerPool-2-thread-9 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 97% complete. Current index: Issue 2015-07-22 21:02:26,771 indexerPool-2-thread-3 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: Issue 2015-07-22 21:02:27,261 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 8607ms. Indexer: DefaultIndexManager: paths: [/data/jira3135/indexes/issues, /data/jira3135/indexes/comments] 2015-07-22 21:02:27,263 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: SearchRequest 2015-07-22 21:02:27,268 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,293 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: SearchRequest 2015-07-22 21:02:27,308 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: PortalPage 2015-07-22 21:02:27,312 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,377 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: PortalPage 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 115ms. Indexer: SharedEntityIndexManager: paths: [/data/jira3135/indexes/entities/portalpage, /data/jira3135/indexes/entities/searchrequest] 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All complete. Total time: 8722ms. 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Reindexing all data in JIRA to include Favourites.' succeeded 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 326 2015-07-22 21:02:27,397 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade succeeded! Setting data build number to 360 2015-07-22 21:02:27,469 JiraQuartzScheduler_Worker-0 WARN [service.services.export.ExportService] Backup directory /data/jira_3_12/backup does not exist {noformat} {warning:title=Paths} It appears that the upgraded JIRA will still look for the attachments and the backup locations in the original places. So I created /data/jira_3_12/backup and untarred the original attachments to /data/jira_3_12 and then everything worked (including attachements) in the new JIRA. {warning} ## (/) I then used the upgraded JIRA to generate a new XML backup and stored it in /data/original/3.13.5 along with another tar of the files in /data/jira_3_12/attachments. ## (/) I then shutdown the JIRA server. *I should be ready to move on to version 4 upgrade WHEW* ## So, before moving on, I decided that it would be a really good idea to spin up a new Crowd instance to get rid of the :8443 in the URL and to move off of RedHat per IS requests. I have a ticket in for a new VM and a new database to try to get this going. I am waiting on that before moving on. ## (/) Pat created the VM and Neil created the database. ## (/) I logged into auth.mbari.org (name of the VM) and downloaded crowd which I unzipped to the /opt directory ## (/) I then created a /data/crowd directory and gave my account permissions on it and then edited the /opt/atlassian..../crowd-webapp/WEB-INF/classes/crowd-init.properties file to set that as the crowd home directory. ## (/) The instructions say to download the JDBC driver, but they already have JTDS 1.2.7 in the download so I did not do anything. ## (/) You have to manually connect up CrowdID to a database as they setup wizard does not currently do this. ### (/) They say to download the driver, but again 1.2.7 was there so I did nothing. ### (/) I edited the /opt/atlassian.../apache-tomcat/conf/Catalina/localhost/openidserver.xml to look like: {noformat} {noformat} ### (/) I edited the /opt/atlassian.../build.properties files to look like: {noformat} # Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See https://confluence.atlassian.com/display/CROWD/Connecting+Crowd+to+a+Database hibernate.dialect=org.hibernate.dialect.SQLServerDialect # The Hibernate transaction factory to use. See https://confluence.atlassian.com/display/CROWD/Configuring+Crowd hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory # The http port you wish to run crowd from, ie: http://localhost:8095/crowd crowd.tomcat.connector.port=8095 # Tomcat requires a unique port for shutdown crowd.tomcat.shutdown.port=8020 # Crowd context root crowd.url=http://localhost:8095/crowd # Demo context root demo.url=http://localhost:8095/demo # OpenID server context root openidserver.url=http://localhost:8095/openidserver {noformat} ### (/) I then ran the build.sh script in the root of /opt/atlassian... ## (/) I fired up crowd using the /opt/atlassian.../start_crowd.sh script ## (/) I then went to http://auth.mbari.org:8095/crowd to kick off the start up wizard ## (/) I grabbed a new eval license from my account on atlassian and pasted into the license page. ## (/) I selected "New install" on the next page. ## (/) I configured the JDBC connection using this connection URL with user DB_Collaboration {noformat} jdbc:jtds:sqlserver://dione.mbari.org:51001/Crowd;domain=SHORE;useNTLMv2=TRUE {noformat} ## (/) I left the "Options" as they came up {warning:title=Paths} Not sure if this is a problem, but because I started the set up using auth.mbari.org, it set the Base URL to http://auth.mbari.org:8095/crowd instead of localhost. Hope that is not a problem. We will see. {warning} ## (/) I configured the email connection using the settings from [here|https://wind.shore.mbari.org/is/howto/email/mbarimail/imap] and I used my network login (probably shouldn't be doing that ... not sure where it stores my password, but I am assuming in the DB). ## (/) For the local admin account, I created a user named 'crowdadm' so it would not clash with my LDAP account. See Kevin Gomes for password information. ## (/) I checked the OpenID server as an integrated application ## (/) It then took me to the login page and I logged in using the newly minted admin account. Seemed all is well so far. ## (/) I visited the openidserver URL as well and that seemed OK. ## (/) I decided to wait on configuring the MBARI LDAP directory until I got everything with SSL working. ## (/) Now the next step was to follow the directions to configure Crowd to run over SSL found [here|https://confluence.atlassian.com/display/CROWD/Configuring+Crowd+to+Work+with+SSL] ## (/) I shutdown crowd. Note that the stop script does not shutdown things correctly and I noticed the crowd app running as root. That should not be if I started as kgomes. Not sure what is up with that. ## (/) Now Joe had already configured SSL once, so I used his connector configuration in the server.xml file and so the final file looked like: {noformat} {noformat} ## (/) I then edited the /data/crowd/crowd.properties to look like: {noformat} #Sat Aug 01 09:05:15 PDT 2015 session.lastvalidation=session.lastvalidation session.tokenkey=session.tokenkey crowd.server.url=https\://localhost\:8443/crowd/services/ application.name=crowd http.timeout=30000 session.isauthenticated=session.isauthenticated application.login.url=https\://localhost\:8443/crowd/console/ session.validationinterval=0 application.password=Y1Xp3OorCmsOP4eruL1dmH {noformat} One thing to note here is that based on a comment from the SSL configuration page at atlassian (Steve's comment), you are supposed to leave all the host names the same. For example, if the file says localhost, leave it localhost. So this created a bit of a problem based on the fact that I had left the base URL pointing to auth.mbari.org in the wizard steps above. That step wrote auth.mbari.org to the /data/crowd/crowd.properties. All the other files reference localhost, so to be consistent, I changed auth.mbari.org to localhost in the /data/crowd/crowd.properties file. We will see if this works. ## (/) Per the instructions on the atlassian page (referenced above), I also edited the build.properties file and the /client/conf/crowd.properties files before I restarted and used the SSL URLs ## build.properties: {noformat} # Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See https://confluence.atlassian.com/display/CROWD/Connecting+Crowd+to+a+Database hibernate.dialect=org.hibernate.dialect.SQLServerDialect # The Hibernate transaction factory to use. See https://confluence.atlassian.com/display/CROWD/Configuring+Crowd hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory # The http port you wish to run crowd from, ie: http://localhost:8095/crowd crowd.tomcat.connector.port=8095 # Tomcat requires a unique port for shutdown crowd.tomcat.shutdown.port=8020 # Crowd context root crowd.url=https://localhost:8443/crowd # Demo context root demo.url=https://localhost:8443/demo # OpenID server context root openidserver.url=https://localhost:8443/openidserver {noformat} ## crowd.properties (client) {noformat} application.name crowd application.password password application.login.url https://localhost:8443/crowd/console/ crowd.server.url https://localhost:8443/crowd/services/ crowd.base.url https://localhost:8443/crowd/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 2 session.lastvalidation session.lastvalidation {noformat} ## (/) Although not stated, I am assuming you would need to run the build.sh script to push the build.properties changes to their proper places, so I did that. Note that before doing that, I know that it will clobber the server.xml changes I made, so I made a copy of that file and diff'd them after and then rolled the previous changes to the new server.xml file. Actually, amazingly enough, it seems to have done the connector entry correctly so I left it after running the build.sh script. ## (/) Crossed my fingers and then restarted crowd. I tailed the catalina.out file and did not see any stack traces so that is a good sign! ## (/) I visited https://auth.mbari.org:8443/crowd first. It could not find that page, but I suspect that is because I am browsing from the outside, so I tried just https://auth.mbari.org/crowd and got a service unavailable. I am suspecting that this is a combination of firewall and proxy pass and I will send this info to Joe. From what I can see on the crowd side, it seems like the server started cleanly, we just can't get to it. I tried to reach it from a browser on the machine itself too (through VNC) with the same service not available. ## (/) Here are the notes from Joe after he fixed it! Wooohooo! {noformat} Hey Kevin, Thanks for starting clean! I had to make a few adjustments. 1-I modified the server.xml file in /opt/atlassian-crowd-2.8.3/apache-tomcat/conf/server.xml so there are two connectors per the instructions on the Atlassian site. I have backed up this good server.xml file in /etc/temp/ if you want to browse it to see what I did. Of note is that I removed all the jargon referencing the types of ciphers available to simplify things for now. 2-I modified /data/crowd/crowd.properties to have crowd.server.url=https\://localhost\:8443/crowd/services/ application.login.url=https\://localhost\:8443/crowd/console/ But that would cause my login to error with an error saying it was unable to reach the authentication server. I scratched my head for a bit. When I revert the values to just using non-SSL and try to log in, I just get an "invalid login" (I don't know the crowdadm password). So I worked under the assumption that if I can configure SSL to get an "invalid login" when logging in then it would work when provided real credentials. So, I then changed /data/crowd/crowd.proprties to: crowd.server.url=https\://auth.mbari.org\:8443/crowd/services/ application.login.url=https\://auth.mbari.org\:8443/crowd/console/ And now when I try to log in with SSL it says "invalid login". Strange because all the other values I can find only show "localhost" .. in any case... Can you try to log in now? {noformat} ## (/) Next I moved on to configuring the connection to MBARI's LDAP server to enable our logins through Crowd and CrowdID ## (/) I clicked on "Add Directory" in crowd. ## (/) I selected "Connector" then clicked Next ## (/) I put ldap.shore.mbari.org as the name of the server ## (/) I selected "Use memberOf for group memberships" ## (/) I used "OU=AllUsers,DC=shore,DC=mbari,DC=org" for the Base DN ## (/) I used "CN=LDAPbind,OU=Special,OU=AllUsers,DC=shore,DC=mbari,DC=org" for the Username (talk to Pat Allen for password) ## (/) I tested the connection (button click) and it passed. ## (/) I de-selected all the capabilities of the connector as it is a ready only connector and then saved it. It synchronized correctly! ## (/) At first, I could not login using my MBARI credentials, but after going to the "crowd" application in crowd (logged in as the local admin), I had to add the LDAP directory and configure it to "Allow all to authenticate", then I was able to login. After this, the last step was to get this to run as a different user and lock down various directories. I went through the entire directory structure /opt/atlassian... and set up so that root owned all read-only locations and DB_Collaboration (account set up by IS) owned the other stuff. I also gave full ownership to the /data/crowd directory to DB_Collaboration so it could write there. Pat set up a script to start on boot and after a little tweaking, it now starts on boot. {warning:title=CrowdID log file} One thing that came up here was that when the crowdID application ran, it tried to write a log file to the location where the process was launched from (which is /opt/atlassian...). This is a bad thing and I figured out that I could change that location by changing the file /opt/atlassian-crowd-2.8.3/crowd-openidserver-webapp/WEB-INF/classes/log4j.properties and hardcoding the /data/crowd/logs/atlassian-crowd-openid-server.log and then restarted the application. {warning}]]> 27558161 19073855 19041164 27099733 27066972 19073858 19041167 27099732 ** response ** 0 * Channel 1 Power Control = 0 (Off) ** $1PC0 ** Response: ** 0 * Channel 1 Power Control = 1 (On) ** $1PC1 ** Response: ** 1 * Channel 1 Power Read ** $1PR ** Response: ** 1 * Read Block ** $1RB read temperature sensor block (4 channels) ** $5RB read pH sensor block (Seabird 18s) ** Response: ** \*+02712.00 ** \*+00200.00 ** \*+00125.76 ** \*+00347.95 * Read Data ** $1RD read tDGH channel 1 (temperature ch 1) ** $2RD read tDGH channel 2 (temperature ch 2) ** $3RD read tDGH channel 3 (temperature ch 3) ** $4RD read tDGH channel 4 (temperature ch 4) ** $5RD read tDGH channel 5 (pH sensor ch 1) ** $6RD read tDGH channel 6 (pH sensor ch 2) ** $7RD read tDGH channel 7 (pH sensor ch 3) ** $8RD read tDGH channel 8 (pH sensor ch 4) ** $9RD read tDGH channel 9 (pH sensor ch 5) \\ \\ \\ \\ \\ \- \\ \- \\ \- \\ \- \\ \- \\ \- \\ \- \\ \- *   *   *   *   *   *   *   *   *   *   *   *   *   *   *   *   *   *   *   *   *   *   *   *   *   *   *   *   *   *   *   *   *   *   *   *   *   *   *   *   ---- \\ \\ \\ \\ \\ \\ \\ \\ \\ DGH Can upgrade project was prioritized up by the Engineering Director in Sep. 2013 in order to remove the project from the 2014 project list and make good on an unrealized project from 2012.  The original scope of work was to fit MBARI HRpH instruments to the DGH can.   RS485 feature of MBARI HRpH was planned.   In 2013, the requirement was added to use the new Seabird 18s digital pH instrument since this instrument was the result of a tech transfer by Thom Maughan to Seabird of the MBARI HRpH instrument and the Seabird 18s is now available as of 4Q2013 (though it is not advertised yet on the Seabird website).   The Seabird 18s does not have an RS485 interface option which motivated a different engineering approach (use of custom microprocessor to aggregate the RS232 instruments and present as a single DGH module to keep the PC software simple). h2. DGH Can Upgrade (tDGH) Requirements: * requirements defined, then reviewed with Ed Peltzer and Dale Graves Sep 2013 h3. Hardware h4. Sensor Interface * 4 channel analog for platinum sensor resistors (RTDs from Omega, same as existing DGH can) * 4 channel digital for RS232 Seabird 18s sensors (4 pin, 12v, RS232). Ability to electrically isolate in case of pH instrument failure. h4. ROV Interface * RS232 * Single power supply \+24v, GND (+24v is more readily available on ROV per DG) h3. Mechanical * The existing DGH housing is corroded, a new housing is desired with 4 connectors for temperature and 4 connectors for pH and 1 connector for ROV h3. Software h4. DGH Can * Must support maximum 1 Hz sample rate (once per second); logging at 1 Hz as well. Typically logging is at 0.5 Hz. Would like 0.2, 0.1 Hz options as well. h4. PC * Installer or standalone executable, must not 'clobber' shared dll's used by another program.  ** virtual machine will be created of Ed's laptop to 'test' the lab view installer.   We will do this early to gate the approach on software. * Same functional and graphical features as existing software.  GUI similar to what we now have in layout with graphical display of pH and "sliders" (horizontal bar graphs) for temperature. GUI should also allow for: ** a. Selection of any temp sensor to go with any pH sensor. ** b. Separate calibration constants (slope & offset) for each pH sensor. ** c. Separate temperature offsets for each temp sensor. h3. Time and Division of Labor: * Ed is the customer and supplies the requirements.   Ed's laptop will need to have a virtual machine constructed to prevent the newer LabView Dll's from affecting an older program.   From time to time Ed will need to log into this virtual machine so that Thom/Dale can test. * Several attempts at making a VM wire tried, Ed's directory replication setup causes VMWare failure * Thom to provide Dale the software def for serial comms so he can work on the Labview GUI ahead of hardware availabilty (Complete) * Thom will be responsible for the project and perform the electronics design and write software/firmware for microprocessor. ** Thom will define serial communications protocol. (In Progress, working over Thxgiving) * Jose will do the PCB layout (Complete) * Indtec will do the assembly (some parts are BGA) * Dale will do the PC Software / GUI (Labview to be used) * Dale will update the instrument housing and spec out the external connectors h3. tDGH controller bringup / hardware design verification * Partial stuff, MSP430F5438A + MAX3222 + MUX + Power Converter + LEDs ** isolating converter consumes \~87mA with 10mA load on 3.3v ** JTAG connection, 14pin connector orients to edge of board, works well ** LEDs work ** UART connection to MAX3222 works ** GPIO connections to INST PWR Enable works * Full stuff controller board received from Indtec on Dec. 4, Tom Marion built up interface board on Dec. 4 ** Had Jose cut/jmp to fix MAX3222, Mux lines, pull ups on Mux Dec 5. **   * PCB Issues ** MUX lines not connected to processor, fixed with blue wires, fixed in rev2. FIXED v2 28 Dec 2013 ** no TX output on MAX3222, C1/C2 cross wired, Fixed with circuit mod. FIXED v2 ** Should have pullups not pull downs on serial lines for MUX - FIXED v2 ** Isolating RS232 not working FIXED v2 * Firmware ** Clock subsystem, 16.777 MHz operation for SMCLK, MCLK, ACLK, Tektronix TDS2024B measures 16.89 MHz (100ns grid). 0.7% error. *** 115200 measures a bit over 8.67 usec per bit time, closer to 8.8 usec. Normally high signal. ** LEDs ** UART0 to 3 sending data, confirmed 115200 ** INST1 PWR Enable tested and working * ToDo ** UART to Instrument connection (fix MAX3222). C1/C2 caps wired incorrectly (fixed in rev 2) DONE ** UART to ROV isolated connection, need to figure out why it's not working. DONE ** Finish hardware bringup and spin rev2 of the controller board. DONE ** UART ISR *** Test serial mux, latency, glitch, etc DONE ** Write test program for exercising relays on interface board DONE ** Write DGH module interface for temperature readings DONE ** Write Seabird 18s interface and driver DONE ** Wire up the DGH housing connectors and mount the board set and DGH module ** Integration test with 5 pH and max sample rate (1Hz) in test tank h3. Seabird 18s setup * setoutputformat= 0 ** 0 \*±vvvvv.vv\r\n pH probe voltage in mV, MBARI style output ** 1 ±vvvv.vv\r\n pH probe voltage in mV ** 2 v.vvvv\r\n pH probe voltage in SBE 18 volts * cal for fast response (request, response immediate, othewise a couple seconds) * setautorun=0 no autorun ** enter interactive mode on powerup, 1 enters tsc on powerup. If tsc is stopped via ESC the instrument re-enters tsc on power cycle. * setexecuted=0 suppress tags ** 1 do not suppress * setecho=0 suppress echoed characters ** 1 do not suppress * setprompt=0 suppress 'S>' ** 1 do not suppress * setbaud=115200 ** 9600, 38400, 115200 * setsampleperiod=1 ** n seconds between scans when running continuously. Each sample is comprised of an average of 8 scans. * Operational commands ** ts returns a measurement in one of the above formats. ** tsc continuously samples and returns the measurement in one of the above formats. The update rate is 1Hz which is an average of 16 samples. Return to interactive mode via the ESC key. ** gethd ** getcd ** getec ** getsd ** getcc * Electrical ** Voltage input 11VDC - 18VDC ** Current consumption 82mA at 12VDC h3. DGH D5451 Module setup * Setup the D5451 to 115200 baud, procedure: ** Wire the default pin on the D5451 to Ground, set terminal to 300 baud (8N1) with serial port connected and 12v supplied (47mA) ** $1WE (echo \*) ** $1SU3108E1C2 (echo \*) ** change terminal settings to 115200, then disconnect the Default pin from ground (leave floating) ** $1RS should return \*3108E1C2 ** $1RD will take a sample, returns \*-99999.99 with input floating (no thermistor) h3. Serial Protocol * Power All (0=off, 1=on) ** $1PA0 ** response ** 0 * Channel 1 Power Control = 0 (Off) ** $1PC0 ** Response: ** 0 * Channel 1 Power Control = 1 (On) ** $1PC1 ** Response: ** 1 * Channel 1 Power Read ** $1PR ** Response: ** 1 * Read Block ** $1RB read temperature sensor block (4 channels) ** $5RB read pH sensor block (Seabird 18s) ** Response: ** \*+02712.00 ** \*+00200.00 ** \*+00125.76 ** \*+00347.95 * Read Data ** $1RD read tDGH channel 1 (temperature ch 1) ** $2RD read tDGH channel 2 (temperature ch 2) ** $3RD read tDGH channel 3 (temperature ch 3) ** $4RD read tDGH channel 4 (temperature ch 4) ** $5RD read tDGH channel 5 (pH sensor ch 1) ** $6RD read tDGH channel 6 (pH sensor ch 2) ** $7RD read tDGH channel 7 (pH sensor ch 3) ** $8RD read tDGH channel 8 (pH sensor ch 4) ** $9RD read tDGH channel 9 (pH sensor ch 5)]]> 27066971 19073857 19041166 19073852 19041161 27590929 4.4: [https://confluence.atlassian.com/display/JIRA044/Migrating+JIRA+to+Another+Server] ## The JIRA configuration tool: [https://confluence.atlassian.com/display/JIRA044/Using+the+JIRA+Configuration+Tool] h5. Steps # (/) Create new VM named bugs.mbari.org in the DMZ # (/) Have Neil create database Jira_Temp on solstice2.shore.mbari.org # (/) Have Neil create database Jira on solstice2.shore.mbari.org # (/) Have Pat install Java 7 on bugs.shore.mbari.org # (/) Have Pete plumb holes through firewall so processes on bugs.mbari.org can get to Solstice2 # (/) Have Pat create DB_Collaboration account on bugs so it can run JIRA under that account and it can connect to solstice2 using that NT Domain account. # (/) Upgrade license on Atlassian site # (/) Log into bugs.shore.mbari.org # (/) Download 3.13.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 4.4.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 5.2.11 standalone Linux 64 bit tar.gz (not sure this version is necessary, but at least I have it) # (/) Unzip and untar the file to /opt # (/) Download latest JIRA (6.4.7 as of this writing). # (/) Unzip and untar it to /opt # Performed Test Upgrade ## (/) In order to export the current stuff in JIRA, I had to shut off access so people could not change the data while I was backing it up. ## (/) I ssh'd to oceana.mbari.org as root and edited the /opt/jira/conf/server.xml file and commented out the Connector section that had the port of 8010 to shut it off from the normal serving route. ## (/) I uncommented the 8082 port connector and the 8443 port connector so that I could still get to the server. ## (/) I stopped and started the JIRA server and in the log file I got a "keystore was tampered with..." which is not surprising. ## (/) I could then browser over to http://oceana.mbari.org:8082/jira ## (/) Then through the Administration console, I did an XML backup ## (/) I then created a tar of all the attachments in the /data/jira_3_12/attachments directory ## (/) I moved both the XML and tar files to the /root/jira-upgrade directory ## (/) I then reversed the changes to the server.xml file and shut down JIRA ## (/) I left it down during the next steps in case it went so well, I could just point people to the new server (yeah, right). ## (/) I then browsed to the crowd server on oceana and add a new application using: ### URL: http://bugs.mbari.org/jira3135 ### IP: 134.89.2.29 ### Name: JIRA3135 ### Password: (ask Kevin) :) ## (/) On bugs, I made a copy of the JIRA 3.13.5 download in the /opt directory and unzipped and untarred it. ## (/) In order to configure the crowd connection I did the following: ### (/) I scp'd the /opt/crowd/client/crowd-integration-client-1.6.jar file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I removed the existing 1.6.1 crowd client jar from the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I scp'd the /opt/crowd/client/conf/crowd.properties file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I scp'd the /opt/crowd/client/conf/crowd-ehcache.xml file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I edited the crowd.properties file on bugs to look like: {noformat} application.name JIRA3135 application.password (ask Kevin) application.login.url http://oceana.mbari.org:8095/crowd/console/ crowd.server.url http://oceana.mbari.org:8095/crowd/services/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 0 session.lastvalidation session.lastvalidation {noformat} ### (/) I edited the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/osuser.xml file to comment out the current authentication mechanism and then uncomment the crowd one. ## (/) I then edited the /opt/atlassian-jira-standalone-3.13.5/conf/server/xml file and configured the database connection to the Jira_Temp database on Solstice2. I looked like this: {noformat} {noformat} ## (/) Edit the /opt/atlassian/jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/entityengine.xml and changed it from 'hsql' to 'mssql' and delete the line with "PUBLIC" in it per the instructions in the comments in that file. ## (/) I edited the /etc/httpd/conf/httpd.conf file and created a proxy pass at the bottom of the file to point a normal URL to the default port 8080 for JIRA: {noformat} # Proxy Pass for JIRA ProxyPass http://bugs.mbari.org:8080 ProxyPassReverse http://bugs.mbari.org:8080 {noformat} ## (/) I restarted Apache ## (/) I scp'd the jtds driver from oceana to the /opt/atlassian-jira-standalone-3.13.5/common/lib directory (you could down from the internet) ## (/) I then went to the /opt/atlassian-jira-standalone-3.13.5/ directory and ran './bin/startup.sh'. From the log file, I could tell things were hanging. After some troubleshooting I am wondering if the local firewall is preventing the application to get access to the database on solstice2. I can telnet to port 1433, but I can't browse to the base http://bugs.mbari.org from anywhere but the local web browser. I have submitted a ticket. ## (/) I restarted the old JIRA with my hopes dashed :(. ## (/) Pat disabled the firewall on bugs.mbari.org but it still hung trying to connect to solstice2.shore.mbari.org. That is really, really perplexing. Neil mentioned that solstice2 is using Kerberos and solstice is not. Checking with the JTDS docs, version 1.3.1 of the driver added kerberos support, so I downloaded that driver and added the 'userKerberos=true' property to the URL in the server.xml file and restarted. Got an error about no credentials, so added user and password properties to the URL. Nope, no luck. Never did figure this one out, but I had Pat pull the VM inside the firewall and after some thrash it worked. Well, it sort of worked ... sigh. It turns out I had downloaded the standard version instead of the enterprise version. I need to redo this work ... grrr. ## (/) I deleted all the tables in the Jira_Temp database and removed the /data/jira3135/indexes directory (and recreated). ## (/) I downloaded the enterprise version of the 3.13.5 server. I made a copy in the /opt directory and unzipped and untarred the file. ## (/) I went back to crowd and edited the application to change the properties to: ### URL: http://bugs.shore.mbari.org:8080 ### IP: 134.89.12.31 ### Name: jira3135 ### Password: (ask Kevin) :) ## (/) I then repeated the steps above to get the server up and running with the following differences: ### The server name is now bugs.shore.mbari.org ### The paths given above are a little different in that they no longer say "standard" but say "enterprise" ### I deleted the proxy pass as it seemed to have issues before and this is only temporary anyway. ## (/) I then browsed to http://bugs.shore.mbari.org:8080 ## (/) It took me to the start up page and at the top was the option to 'import your existing data'. Seemed too good not to try. I clicked on the link. It asked me for the backup file location and the location where the indexes would be stored. ## (/) I copied the XML zip file and the attachments tar file to the /data/original directory. ## (/) I created the /data/jira3135/indexes and used those directories ... it fired off the import and I waited. ## (/) I tailed the log file to watch the import. Holy crap, it worked!!! I could log in and everything! I copied the results from the log file here for posterity sake: {noformat} 2015-07-22 20:55:45,156 http-8080-Processor22 INFO [jira.action.admin.DataImport] Running data import 2015-07-22 20:55:45,179 http-8080-Processor22 INFO [jira.action.admin.DataImport] Importing data.. 2015-07-22 20:55:45,186 http-8080-Processor22 INFO [jira.action.admin.DataImport] Start parsing XML with SAX Parser 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] XML successfully parsed 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] Removing all entries from the database. 2015-07-22 20:56:24,593 http-8080-Processor22 INFO [jira.action.admin.DataImport] All entries removed. 2015-07-22 20:56:24,594 http-8080-Processor22 INFO [jira.action.admin.DataImport] Started storing 410414 Generic Values 2015-07-22 21:01:51,967 http-8080-Processor22 INFO [jira.action.admin.DataImport] Finished storing Generic Values 2015-07-22 21:01:52,329 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:52,361 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:54,683 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLink' to module 'jira.user.format:profile-link-user-format'. 2015-07-22 21:01:54,724 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullName' to module 'jira.user.format:full-name-user-format'. 2015-07-22 21:01:54,773 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkSearcher' to module 'jira.user.format:profile-link-searcher-user-format'. 2015-07-22 21:01:54,784 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkExternal' to module 'jira.user.format:profile-link-external-user-format'. 2015-07-22 21:01:54,795 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkActionHeader' to module 'jira.user.format:profile-link-action-header-user-format'. 2015-07-22 21:01:54,807 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullProfile' to module 'jira.user.format:full-profile-user-format'. 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/comments 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/issues 2015-07-22 21:01:55,641 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/plugins 2015-07-22 21:01:55,867 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:01:55,871 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/issues does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:55,873 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/comments does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,033 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,257 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,889 http-8080-Processor22 ERROR [atlassian.jira.upgrade.ConsistencyCheckImpl] Attachments are turned on, but attachment path [/data/jira_3_12/attachments] invalid - disabling attachments 2015-07-22 21:02:13,904 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Detected that an upgrade is needed; existing data at build 299 2015-07-22 21:02:13,907 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Doing Upgrade... 2015-07-22 21:02:13,915 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value' succeeded 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 317 2015-07-22 21:02:13,944 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite filters - make each filter a favourite of its owner. 2015-07-22 21:02:17,822 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build319] Could not find author 'fpy' for filter with id '10040' 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite filters - make each filter a favourite of its owner.' succeeded 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 319 2015-07-22 21:02:17,995 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise Share Permissions. Move old shares to new shares. 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise Share Permissions. Move old shares to new shares.' succeeded 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 321 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Migrating the old JIRA UI colors to the new JIRA 3.13 colors 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build322] Custom color detected for jira.lf.menu.bgcolour : #336699 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Migrating the old JIRA UI colors to the new JIRA 3.13 colors' succeeded 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 322 2015-07-22 21:02:18,025 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite dashboards - make each dashboard a favourite of its owner. 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'cmcgann' for dashboard with id '10030' 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'fpy' for dashboard with id '10060' 2015-07-22 21:02:18,423 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'kanna' for dashboard with id '10040' 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite dashboards - make each dashboard a favourite of its owner.' succeeded 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 325 2015-07-22 21:02:18,625 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Reindexing all data in JIRA to include Favourites. 2015-07-22 21:02:18,648 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All starting... 2015-07-22 21:02:18,650 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 0% complete. Current index: Issue 2015-07-22 21:02:18,654 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:02:18,809 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 1% complete. Current index: Issue 2015-07-22 21:02:18,855 indexerPool-2-thread-10 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 2% complete. Current index: Issue 2015-07-22 21:02:18,899 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 3% complete. Current index: Issue 2015-07-22 21:02:18,945 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 4% complete. Current index: Issue 2015-07-22 21:02:19,012 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 5% complete. Current index: Issue . . . 2015-07-22 21:02:26,164 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 95% complete. Current index: Issue 2015-07-22 21:02:26,232 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 96% complete. Current index: Issue 2015-07-22 21:02:26,316 indexerPool-2-thread-9 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 97% complete. Current index: Issue 2015-07-22 21:02:26,771 indexerPool-2-thread-3 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: Issue 2015-07-22 21:02:27,261 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 8607ms. Indexer: DefaultIndexManager: paths: [/data/jira3135/indexes/issues, /data/jira3135/indexes/comments] 2015-07-22 21:02:27,263 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: SearchRequest 2015-07-22 21:02:27,268 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,293 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: SearchRequest 2015-07-22 21:02:27,308 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: PortalPage 2015-07-22 21:02:27,312 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,377 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: PortalPage 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 115ms. Indexer: SharedEntityIndexManager: paths: [/data/jira3135/indexes/entities/portalpage, /data/jira3135/indexes/entities/searchrequest] 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All complete. Total time: 8722ms. 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Reindexing all data in JIRA to include Favourites.' succeeded 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 326 2015-07-22 21:02:27,397 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade succeeded! Setting data build number to 360 2015-07-22 21:02:27,469 JiraQuartzScheduler_Worker-0 WARN [service.services.export.ExportService] Backup directory /data/jira_3_12/backup does not exist {noformat} {warning:title=Paths} It appears that the upgraded JIRA will still look for the attachments and the backup locations in the original places. So I created /data/jira_3_12/backup and untarred the original attachments to /data/jira_3_12 and then everything worked (including attachements) in the new JIRA. {warning} ## (/) I then used the upgraded JIRA to generate a new XML backup and stored it in /data/original/3.13.5 along with another tar of the files in /data/jira_3_12/attachments. ## (/) I then shutdown the JIRA server. *I should be ready to move on to version 4 upgrade WHEW* ## So, before moving on, I decided that it would be a really good idea to spin up a new Crowd instance to get rid of the :8443 in the URL and to move off of RedHat per IS requests. I have a ticket in for a new VM and a new database to try to get this going. I am waiting on that before moving on. ## (/) Pat created the VM and Neil created the database. ## (/) I logged into auth.mbari.org (name of the VM) and downloaded crowd which I unzipped to the /opt directory ## (/) I then created a /data/crowd directory and gave my account permissions on it and then edited the /opt/atlassian..../crowd-webapp/WEB-INF/classes/crowd-init.properties file to set that as the crowd home directory. ## (/) The instructions say to download the JDBC driver, but they already have JTDS 1.2.7 in the download so I did not do anything. ## (/) You have to manually connect up CrowdID to a database as they setup wizard does not currently do this. ### (/) They say to download the driver, but again 1.2.7 was there so I did nothing. ### (/) I edited the /opt/atlassian.../apache-tomcat/conf/Catalina/localhost/openidserver.xml to look like: {noformat} {noformat} ### (/) I edited the /opt/atlassian.../build.properties files to look like: {noformat} # Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See https://confluence.atlassian.com/display/CROWD/Connecting+Crowd+to+a+Database hibernate.dialect=org.hibernate.dialect.SQLServerDialect # The Hibernate transaction factory to use. See https://confluence.atlassian.com/display/CROWD/Configuring+Crowd hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory # The http port you wish to run crowd from, ie: http://localhost:8095/crowd crowd.tomcat.connector.port=8095 # Tomcat requires a unique port for shutdown crowd.tomcat.shutdown.port=8020 # Crowd context root crowd.url=http://localhost:8095/crowd # Demo context root demo.url=http://localhost:8095/demo # OpenID server context root openidserver.url=http://localhost:8095/openidserver {noformat} ### (/) I then ran the build.sh script in the root of /opt/atlassian... ## (/) I fired up crowd using the /opt/atlassian.../start_crowd.sh script ## (/) I then went to http://auth.mbari.org:8095/crowd to kick off the start up wizard ## (/) I grabbed a new eval license from my account on atlassian and pasted into the license page. ## (/) I selected "New install" on the next page. ## (/) I configured the JDBC connection using this connection URL with user DB_Collaboration {noformat} jdbc:jtds:sqlserver://dione.mbari.org:51001/Crowd;domain=SHORE;useNTLMv2=TRUE {noformat} ## (/) I left the "Options" as they came up {warning:title=Paths} Not sure if this is a problem, but because I started the set up using auth.mbari.org, it set the Base URL to http://auth.mbari.org:8095/crowd instead of localhost. Hope that is not a problem. We will see. {warning} ## (/) I configured the email connection using the settings from [here|https://wind.shore.mbari.org/is/howto/email/mbarimail/imap] and I used my network login (probably shouldn't be doing that ... not sure where it stores my password, but I am assuming in the DB). ## (/) For the local admin account, I created a user named 'crowdadm' so it would not clash with my LDAP account. See Kevin Gomes for password information. ## (/) I checked the OpenID server as an integrated application ## (/) It then took me to the login page and I logged in using the newly minted admin account. Seemed all is well so far. ## (/) I visited the openidserver URL as well and that seemed OK. ## (/) I decided to wait on configuring the MBARI LDAP directory until I got everything with SSL working. ## (/) Now the next step was to follow the directions to configure Crowd to run over SSL found [here|https://confluence.atlassian.com/display/CROWD/Configuring+Crowd+to+Work+with+SSL] ## (/) I shutdown crowd. Note that the stop script does not shutdown things correctly and I noticed the crowd app running as root. That should not be if I started as kgomes. Not sure what is up with that. ## (/) Now Joe had already configured SSL once, so I used his connector configuration in the server.xml file and so the final file looked like: {noformat} {noformat} ## (/) I then edited the /data/crowd/crowd.properties to look like: {noformat} #Sat Aug 01 09:05:15 PDT 2015 session.lastvalidation=session.lastvalidation session.tokenkey=session.tokenkey crowd.server.url=https\://localhost\:8443/crowd/services/ application.name=crowd http.timeout=30000 session.isauthenticated=session.isauthenticated application.login.url=https\://localhost\:8443/crowd/console/ session.validationinterval=0 application.password=Y1Xp3OorCmsOP4eruL1dmH {noformat} One thing to note here is that based on a comment from the SSL configuration page at atlassian (Steve's comment), you are supposed to leave all the host names the same. For example, if the file says localhost, leave it localhost. So this created a bit of a problem based on the fact that I had left the base URL pointing to auth.mbari.org in the wizard steps above. That step wrote auth.mbari.org to the /data/crowd/crowd.properties. All the other files reference localhost, so to be consistent, I changed auth.mbari.org to localhost in the /data/crowd/crowd.properties file. We will see if this works. ## (/) Per the instructions on the atlassian page (referenced above), I also edited the build.properties file and the /client/conf/crowd.properties files before I restarted and used the SSL URLs ## build.properties: {noformat} # Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See https://confluence.atlassian.com/display/CROWD/Connecting+Crowd+to+a+Database hibernate.dialect=org.hibernate.dialect.SQLServerDialect # The Hibernate transaction factory to use. See https://confluence.atlassian.com/display/CROWD/Configuring+Crowd hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory # The http port you wish to run crowd from, ie: http://localhost:8095/crowd crowd.tomcat.connector.port=8095 # Tomcat requires a unique port for shutdown crowd.tomcat.shutdown.port=8020 # Crowd context root crowd.url=https://localhost:8443/crowd # Demo context root demo.url=https://localhost:8443/demo # OpenID server context root openidserver.url=https://localhost:8443/openidserver {noformat} ## crowd.properties (client) {noformat} application.name crowd application.password password application.login.url https://localhost:8443/crowd/console/ crowd.server.url https://localhost:8443/crowd/services/ crowd.base.url https://localhost:8443/crowd/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 2 session.lastvalidation session.lastvalidation {noformat} ## (/) Although not stated, I am assuming you would need to run the build.sh script to push the build.properties changes to their proper places, so I did that. Note that before doing that, I know that it will clobber the server.xml changes I made, so I made a copy of that file and diff'd them after and then rolled the previous changes to the new server.xml file. Actually, amazingly enough, it seems to have done the connector entry correctly so I left it after running the build.sh script. ## (/) Crossed my fingers and then restarted crowd. I tailed the catalina.out file and did not see any stack traces so that is a good sign! ## (/) I visited https://auth.mbari.org:8443/crowd first. It could not find that page, but I suspect that is because I am browsing from the outside, so I tried just https://auth.mbari.org/crowd and got a service unavailable. I am suspecting that this is a combination of firewall and proxy pass and I will send this info to Joe. From what I can see on the crowd side, it seems like the server started cleanly, we just can't get to it. I tried to reach it from a browser on the machine itself too (through VNC) with the same service not available. ## (/) Here are the notes from Joe after he fixed it! Wooohooo! {noformat} Hey Kevin, Thanks for starting clean! I had to make a few adjustments. 1-I modified the server.xml file in /opt/atlassian-crowd-2.8.3/apache-tomcat/conf/server.xml so there are two connectors per the instructions on the Atlassian site. I have backed up this good server.xml file in /etc/temp/ if you want to browse it to see what I did. Of note is that I removed all the jargon referencing the types of ciphers available to simplify things for now. 2-I modified /data/crowd/crowd.properties to have crowd.server.url=https\://localhost\:8443/crowd/services/ application.login.url=https\://localhost\:8443/crowd/console/ But that would cause my login to error with an error saying it was unable to reach the authentication server. I scratched my head for a bit. When I revert the values to just using non-SSL and try to log in, I just get an "invalid login" (I don't know the crowdadm password). So I worked under the assumption that if I can configure SSL to get an "invalid login" when logging in then it would work when provided real credentials. So, I then changed /data/crowd/crowd.proprties to: crowd.server.url=https\://auth.mbari.org\:8443/crowd/services/ application.login.url=https\://auth.mbari.org\:8443/crowd/console/ And now when I try to log in with SSL it says "invalid login". Strange because all the other values I can find only show "localhost" .. in any case... Can you try to log in now? {noformat} ## (/) Next I moved on to configuring the connection to MBARI's LDAP server to enable our logins through Crowd and CrowdID ## (/) I clicked on "Add Directory" in crowd. ## (/) I selected "Connector" then clicked Next ## (/) I put ldap.shore.mbari.org as the name of the server ## (/) I selected "Use memberOf for group memberships" ## (/) I used "OU=AllUsers,DC=shore,DC=mbari,DC=org" for the Base DN ## (/) I used "CN=LDAPbind,OU=Special,OU=AllUsers,DC=shore,DC=mbari,DC=org" for the Username (talk to Pat Allen for password) ## (/) I tested the connection (button click) and it passed. ## (/) I de-selected all the capabilities of the connector as it is a ready only connector and then saved it. It synchronized correctly! ## (/) At first, I could not login using my MBARI credentials, but after going to the "crowd" application in crowd (logged in as the local admin), I had to add the LDAP directory and configure it to "Allow all to authenticate", then I was able to login. After this, the last step was to get this to run as a different user and lock down various directories. I went through the entire directory structure /opt/atlassian... and set up so that root owned all read-only locations and DB_Collaboration (account set up by IS) owned the other stuff. I also gave full ownership to the /data/crowd directory to DB_Collaboration so it could write there. Pat set up a script to start on boot and after a little tweaking, it now starts on boot. {warning:title=CrowdID log file} One thing that came up here was that when the crowdID application ran, it tried to write a log file to the location where the process was launched from (which is /opt/atlassian...). This is a bad thing and I figured out that I could change that location by changing the file /opt/atlassian-crowd-2.8.3/crowd-openidserver-webapp/WEB-INF/classes/log4j.properties and hardcoding the /data/crowd/logs/atlassian-crowd-openid-server.log and then restarted the application. {warning} # (/) It is finally time to move on to the version 4 upgrade ... holy crap. I first went to the *new* crowd install (auth.mbari.org) and logged in as the crowdadm. # (/) I clicked on Applications, then on Add Application # (/) I selected JIRA from the Application type drop-down # (/) I entered jira445 as the username. Ask Kevin about the password. # (/) I used http://bugs.shore.mbari.org:8081 as the URL # (/) I used 134.89.12.31 as the IP address. # (/) I selected only the MBARI LDAP directory. # (/) Then I selected "Allow all users to authenticate" # (/) Then I clicked on "Add Application" # (/) I VNC'd into bugs.mbari.org. As it turns out, for Linux, there is an installer program to download. I downloaded the .bin for 64 bit Linux installer and moved it to the jira-upgrade directory. # (/) I chmod'd the file to make it executable and ran it. It gave me a warning about not being root, but I went ahead with it. ]]> 27558165 27590927 4.4: [https://confluence.atlassian.com/display/JIRA044/Migrating+JIRA+to+Another+Server] ## The JIRA configuration tool: [https://confluence.atlassian.com/display/JIRA044/Using+the+JIRA+Configuration+Tool] h5. Steps # (/) Create new VM named bugs.mbari.org in the DMZ # (/) Have Neil create database Jira_Temp on solstice2.shore.mbari.org # (/) Have Neil create database Jira on solstice2.shore.mbari.org # (/) Have Pat install Java 7 on bugs.shore.mbari.org # (/) Have Pete plumb holes through firewall so processes on bugs.mbari.org can get to Solstice2 # (/) Have Pat create DB_Collaboration account on bugs so it can run JIRA under that account and it can connect to solstice2 using that NT Domain account. # (/) Upgrade license on Atlassian site # (/) Log into bugs.shore.mbari.org # (/) Download 3.13.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 4.4.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 5.2.11 standalone Linux 64 bit tar.gz (not sure this version is necessary, but at least I have it) # (/) Unzip and untar the file to /opt # (/) Download latest JIRA (6.4.7 as of this writing). # (/) Unzip and untar it to /opt # Performed Test Upgrade ## (/) In order to export the current stuff in JIRA, I had to shut off access so people could not change the data while I was backing it up. ## (/) I ssh'd to oceana.mbari.org as root and edited the /opt/jira/conf/server.xml file and commented out the Connector section that had the port of 8010 to shut it off from the normal serving route. ## (/) I uncommented the 8082 port connector and the 8443 port connector so that I could still get to the server. ## (/) I stopped and started the JIRA server and in the log file I got a "keystore was tampered with..." which is not surprising. ## (/) I could then browser over to http://oceana.mbari.org:8082/jira ## (/) Then through the Administration console, I did an XML backup ## (/) I then created a tar of all the attachments in the /data/jira_3_12/attachments directory ## (/) I moved both the XML and tar files to the /root/jira-upgrade directory ## (/) I then reversed the changes to the server.xml file and shut down JIRA ## (/) I left it down during the next steps in case it went so well, I could just point people to the new server (yeah, right). ## (/) I then browsed to the crowd server on oceana and add a new application using: ### URL: http://bugs.mbari.org/jira3135 ### IP: 134.89.2.29 ### Name: JIRA3135 ### Password: (ask Kevin) :) ## (/) On bugs, I made a copy of the JIRA 3.13.5 download in the /opt directory and unzipped and untarred it. ## (/) In order to configure the crowd connection I did the following: ### (/) I scp'd the /opt/crowd/client/crowd-integration-client-1.6.jar file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I removed the existing 1.6.1 crowd client jar from the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I scp'd the /opt/crowd/client/conf/crowd.properties file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I scp'd the /opt/crowd/client/conf/crowd-ehcache.xml file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I edited the crowd.properties file on bugs to look like: {noformat} application.name JIRA3135 application.password (ask Kevin) application.login.url http://oceana.mbari.org:8095/crowd/console/ crowd.server.url http://oceana.mbari.org:8095/crowd/services/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 0 session.lastvalidation session.lastvalidation {noformat} ### (/) I edited the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/osuser.xml file to comment out the current authentication mechanism and then uncomment the crowd one. ## (/) I then edited the /opt/atlassian-jira-standalone-3.13.5/conf/server/xml file and configured the database connection to the Jira_Temp database on Solstice2. I looked like this: {noformat} {noformat} ## (/) Edit the /opt/atlassian/jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/entityengine.xml and changed it from 'hsql' to 'mssql' and delete the line with "PUBLIC" in it per the instructions in the comments in that file. ## (/) I edited the /etc/httpd/conf/httpd.conf file and created a proxy pass at the bottom of the file to point a normal URL to the default port 8080 for JIRA: {noformat} # Proxy Pass for JIRA ProxyPass http://bugs.mbari.org:8080 ProxyPassReverse http://bugs.mbari.org:8080 {noformat} ## (/) I restarted Apache ## (/) I scp'd the jtds driver from oceana to the /opt/atlassian-jira-standalone-3.13.5/common/lib directory (you could down from the internet) ## (/) I then went to the /opt/atlassian-jira-standalone-3.13.5/ directory and ran './bin/startup.sh'. From the log file, I could tell things were hanging. After some troubleshooting I am wondering if the local firewall is preventing the application to get access to the database on solstice2. I can telnet to port 1433, but I can't browse to the base http://bugs.mbari.org from anywhere but the local web browser. I have submitted a ticket. ## (/) I restarted the old JIRA with my hopes dashed :(. ## (/) Pat disabled the firewall on bugs.mbari.org but it still hung trying to connect to solstice2.shore.mbari.org. That is really, really perplexing. Neil mentioned that solstice2 is using Kerberos and solstice is not. Checking with the JTDS docs, version 1.3.1 of the driver added kerberos support, so I downloaded that driver and added the 'userKerberos=true' property to the URL in the server.xml file and restarted. Got an error about no credentials, so added user and password properties to the URL. Nope, no luck. Never did figure this one out, but I had Pat pull the VM inside the firewall and after some thrash it worked. Well, it sort of worked ... sigh. It turns out I had downloaded the standard version instead of the enterprise version. I need to redo this work ... grrr. ## (/) I deleted all the tables in the Jira_Temp database and removed the /data/jira3135/indexes directory (and recreated). ## (/) I downloaded the enterprise version of the 3.13.5 server. I made a copy in the /opt directory and unzipped and untarred the file. ## (/) I went back to crowd and edited the application to change the properties to: ### URL: http://bugs.shore.mbari.org:8080 ### IP: 134.89.12.31 ### Name: jira3135 ### Password: (ask Kevin) :) ## (/) I then repeated the steps above to get the server up and running with the following differences: ### The server name is now bugs.shore.mbari.org ### The paths given above are a little different in that they no longer say "standard" but say "enterprise" ### I deleted the proxy pass as it seemed to have issues before and this is only temporary anyway. ## (/) I then browsed to http://bugs.shore.mbari.org:8080 ## (/) It took me to the start up page and at the top was the option to 'import your existing data'. Seemed too good not to try. I clicked on the link. It asked me for the backup file location and the location where the indexes would be stored. ## (/) I copied the XML zip file and the attachments tar file to the /data/original directory. ## (/) I created the /data/jira3135/indexes and used those directories ... it fired off the import and I waited. ## (/) I tailed the log file to watch the import. Holy crap, it worked!!! I could log in and everything! I copied the results from the log file here for posterity sake: {noformat} 2015-07-22 20:55:45,156 http-8080-Processor22 INFO [jira.action.admin.DataImport] Running data import 2015-07-22 20:55:45,179 http-8080-Processor22 INFO [jira.action.admin.DataImport] Importing data.. 2015-07-22 20:55:45,186 http-8080-Processor22 INFO [jira.action.admin.DataImport] Start parsing XML with SAX Parser 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] XML successfully parsed 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] Removing all entries from the database. 2015-07-22 20:56:24,593 http-8080-Processor22 INFO [jira.action.admin.DataImport] All entries removed. 2015-07-22 20:56:24,594 http-8080-Processor22 INFO [jira.action.admin.DataImport] Started storing 410414 Generic Values 2015-07-22 21:01:51,967 http-8080-Processor22 INFO [jira.action.admin.DataImport] Finished storing Generic Values 2015-07-22 21:01:52,329 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:52,361 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:54,683 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLink' to module 'jira.user.format:profile-link-user-format'. 2015-07-22 21:01:54,724 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullName' to module 'jira.user.format:full-name-user-format'. 2015-07-22 21:01:54,773 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkSearcher' to module 'jira.user.format:profile-link-searcher-user-format'. 2015-07-22 21:01:54,784 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkExternal' to module 'jira.user.format:profile-link-external-user-format'. 2015-07-22 21:01:54,795 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkActionHeader' to module 'jira.user.format:profile-link-action-header-user-format'. 2015-07-22 21:01:54,807 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullProfile' to module 'jira.user.format:full-profile-user-format'. 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/comments 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/issues 2015-07-22 21:01:55,641 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/plugins 2015-07-22 21:01:55,867 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:01:55,871 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/issues does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:55,873 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/comments does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,033 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,257 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,889 http-8080-Processor22 ERROR [atlassian.jira.upgrade.ConsistencyCheckImpl] Attachments are turned on, but attachment path [/data/jira_3_12/attachments] invalid - disabling attachments 2015-07-22 21:02:13,904 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Detected that an upgrade is needed; existing data at build 299 2015-07-22 21:02:13,907 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Doing Upgrade... 2015-07-22 21:02:13,915 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value' succeeded 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 317 2015-07-22 21:02:13,944 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite filters - make each filter a favourite of its owner. 2015-07-22 21:02:17,822 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build319] Could not find author 'fpy' for filter with id '10040' 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite filters - make each filter a favourite of its owner.' succeeded 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 319 2015-07-22 21:02:17,995 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise Share Permissions. Move old shares to new shares. 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise Share Permissions. Move old shares to new shares.' succeeded 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 321 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Migrating the old JIRA UI colors to the new JIRA 3.13 colors 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build322] Custom color detected for jira.lf.menu.bgcolour : #336699 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Migrating the old JIRA UI colors to the new JIRA 3.13 colors' succeeded 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 322 2015-07-22 21:02:18,025 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite dashboards - make each dashboard a favourite of its owner. 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'cmcgann' for dashboard with id '10030' 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'fpy' for dashboard with id '10060' 2015-07-22 21:02:18,423 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'kanna' for dashboard with id '10040' 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite dashboards - make each dashboard a favourite of its owner.' succeeded 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 325 2015-07-22 21:02:18,625 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Reindexing all data in JIRA to include Favourites. 2015-07-22 21:02:18,648 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All starting... 2015-07-22 21:02:18,650 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 0% complete. Current index: Issue 2015-07-22 21:02:18,654 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:02:18,809 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 1% complete. Current index: Issue 2015-07-22 21:02:18,855 indexerPool-2-thread-10 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 2% complete. Current index: Issue 2015-07-22 21:02:18,899 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 3% complete. Current index: Issue 2015-07-22 21:02:18,945 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 4% complete. Current index: Issue 2015-07-22 21:02:19,012 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 5% complete. Current index: Issue . . . 2015-07-22 21:02:26,164 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 95% complete. Current index: Issue 2015-07-22 21:02:26,232 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 96% complete. Current index: Issue 2015-07-22 21:02:26,316 indexerPool-2-thread-9 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 97% complete. Current index: Issue 2015-07-22 21:02:26,771 indexerPool-2-thread-3 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: Issue 2015-07-22 21:02:27,261 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 8607ms. Indexer: DefaultIndexManager: paths: [/data/jira3135/indexes/issues, /data/jira3135/indexes/comments] 2015-07-22 21:02:27,263 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: SearchRequest 2015-07-22 21:02:27,268 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,293 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: SearchRequest 2015-07-22 21:02:27,308 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: PortalPage 2015-07-22 21:02:27,312 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,377 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: PortalPage 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 115ms. Indexer: SharedEntityIndexManager: paths: [/data/jira3135/indexes/entities/portalpage, /data/jira3135/indexes/entities/searchrequest] 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All complete. Total time: 8722ms. 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Reindexing all data in JIRA to include Favourites.' succeeded 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 326 2015-07-22 21:02:27,397 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade succeeded! Setting data build number to 360 2015-07-22 21:02:27,469 JiraQuartzScheduler_Worker-0 WARN [service.services.export.ExportService] Backup directory /data/jira_3_12/backup does not exist {noformat} {warning:title=Paths} It appears that the upgraded JIRA will still look for the attachments and the backup locations in the original places. So I created /data/jira_3_12/backup and untarred the original attachments to /data/jira_3_12 and then everything worked (including attachements) in the new JIRA. {warning} ## (/) I then used the upgraded JIRA to generate a new XML backup and stored it in /data/original/3.13.5 along with another tar of the files in /data/jira_3_12/attachments. ## (/) I then shutdown the JIRA server. *I should be ready to move on to version 4 upgrade WHEW* ## So, before moving on, I decided that it would be a really good idea to spin up a new Crowd instance to get rid of the :8443 in the URL and to move off of RedHat per IS requests. I have a ticket in for a new VM and a new database to try to get this going. I am waiting on that before moving on. ## (/) Pat created the VM and Neil created the database. ## (/) I logged into auth.mbari.org (name of the VM) and downloaded crowd which I unzipped to the /opt directory ## (/) I then created a /data/crowd directory and gave my account permissions on it and then edited the /opt/atlassian..../crowd-webapp/WEB-INF/classes/crowd-init.properties file to set that as the crowd home directory. ## (/) The instructions say to download the JDBC driver, but they already have JTDS 1.2.7 in the download so I did not do anything. ## (/) You have to manually connect up CrowdID to a database as they setup wizard does not currently do this. ### (/) They say to download the driver, but again 1.2.7 was there so I did nothing. ### (/) I edited the /opt/atlassian.../apache-tomcat/conf/Catalina/localhost/openidserver.xml to look like: {noformat} {noformat} ### (/) I edited the /opt/atlassian.../build.properties files to look like: {noformat} # Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See https://confluence.atlassian.com/display/CROWD/Connecting+Crowd+to+a+Database hibernate.dialect=org.hibernate.dialect.SQLServerDialect # The Hibernate transaction factory to use. See https://confluence.atlassian.com/display/CROWD/Configuring+Crowd hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory # The http port you wish to run crowd from, ie: http://localhost:8095/crowd crowd.tomcat.connector.port=8095 # Tomcat requires a unique port for shutdown crowd.tomcat.shutdown.port=8020 # Crowd context root crowd.url=http://localhost:8095/crowd # Demo context root demo.url=http://localhost:8095/demo # OpenID server context root openidserver.url=http://localhost:8095/openidserver {noformat} ### (/) I then ran the build.sh script in the root of /opt/atlassian... ## (/) I fired up crowd using the /opt/atlassian.../start_crowd.sh script ## (/) I then went to http://auth.mbari.org:8095/crowd to kick off the start up wizard ## (/) I grabbed a new eval license from my account on atlassian and pasted into the license page. ## (/) I selected "New install" on the next page. ## (/) I configured the JDBC connection using this connection URL with user DB_Collaboration {noformat} jdbc:jtds:sqlserver://dione.mbari.org:51001/Crowd;domain=SHORE;useNTLMv2=TRUE {noformat} ## (/) I left the "Options" as they came up {warning:title=Paths} Not sure if this is a problem, but because I started the set up using auth.mbari.org, it set the Base URL to http://auth.mbari.org:8095/crowd instead of localhost. Hope that is not a problem. We will see. {warning} ## (/) I configured the email connection using the settings from [here|https://wind.shore.mbari.org/is/howto/email/mbarimail/imap] and I used my network login (probably shouldn't be doing that ... not sure where it stores my password, but I am assuming in the DB). ## (/) For the local admin account, I created a user named 'crowdadm' so it would not clash with my LDAP account. See Kevin Gomes for password information. ## (/) I checked the OpenID server as an integrated application ## (/) It then took me to the login page and I logged in using the newly minted admin account. Seemed all is well so far. ## (/) I visited the openidserver URL as well and that seemed OK. ## (/) I decided to wait on configuring the MBARI LDAP directory until I got everything with SSL working. ## (/) Now the next step was to follow the directions to configure Crowd to run over SSL found [here|https://confluence.atlassian.com/display/CROWD/Configuring+Crowd+to+Work+with+SSL] ## (/) I shutdown crowd. Note that the stop script does not shutdown things correctly and I noticed the crowd app running as root. That should not be if I started as kgomes. Not sure what is up with that. ## (/) Now Joe had already configured SSL once, so I used his connector configuration in the server.xml file and so the final file looked like: {noformat} {noformat} ## (/) I then edited the /data/crowd/crowd.properties to look like: {noformat} #Sat Aug 01 09:05:15 PDT 2015 session.lastvalidation=session.lastvalidation session.tokenkey=session.tokenkey crowd.server.url=https\://localhost\:8443/crowd/services/ application.name=crowd http.timeout=30000 session.isauthenticated=session.isauthenticated application.login.url=https\://localhost\:8443/crowd/console/ session.validationinterval=0 application.password=Y1Xp3OorCmsOP4eruL1dmH {noformat} One thing to note here is that based on a comment from the SSL configuration page at atlassian (Steve's comment), you are supposed to leave all the host names the same. For example, if the file says localhost, leave it localhost. So this created a bit of a problem based on the fact that I had left the base URL pointing to auth.mbari.org in the wizard steps above. That step wrote auth.mbari.org to the /data/crowd/crowd.properties. All the other files reference localhost, so to be consistent, I changed auth.mbari.org to localhost in the /data/crowd/crowd.properties file. We will see if this works. ## (/) Per the instructions on the atlassian page (referenced above), I also edited the build.properties file and the /client/conf/crowd.properties files before I restarted and used the SSL URLs ## build.properties: {noformat} # Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See https://confluence.atlassian.com/display/CROWD/Connecting+Crowd+to+a+Database hibernate.dialect=org.hibernate.dialect.SQLServerDialect # The Hibernate transaction factory to use. See https://confluence.atlassian.com/display/CROWD/Configuring+Crowd hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory # The http port you wish to run crowd from, ie: http://localhost:8095/crowd crowd.tomcat.connector.port=8095 # Tomcat requires a unique port for shutdown crowd.tomcat.shutdown.port=8020 # Crowd context root crowd.url=https://localhost:8443/crowd # Demo context root demo.url=https://localhost:8443/demo # OpenID server context root openidserver.url=https://localhost:8443/openidserver {noformat} ## crowd.properties (client) {noformat} application.name crowd application.password password application.login.url https://localhost:8443/crowd/console/ crowd.server.url https://localhost:8443/crowd/services/ crowd.base.url https://localhost:8443/crowd/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 2 session.lastvalidation session.lastvalidation {noformat} ## (/) Although not stated, I am assuming you would need to run the build.sh script to push the build.properties changes to their proper places, so I did that. Note that before doing that, I know that it will clobber the server.xml changes I made, so I made a copy of that file and diff'd them after and then rolled the previous changes to the new server.xml file. Actually, amazingly enough, it seems to have done the connector entry correctly so I left it after running the build.sh script. ## (/) Crossed my fingers and then restarted crowd. I tailed the catalina.out file and did not see any stack traces so that is a good sign! ## (/) I visited https://auth.mbari.org:8443/crowd first. It could not find that page, but I suspect that is because I am browsing from the outside, so I tried just https://auth.mbari.org/crowd and got a service unavailable. I am suspecting that this is a combination of firewall and proxy pass and I will send this info to Joe. From what I can see on the crowd side, it seems like the server started cleanly, we just can't get to it. I tried to reach it from a browser on the machine itself too (through VNC) with the same service not available. ## (/) Here are the notes from Joe after he fixed it! Wooohooo! {noformat} Hey Kevin, Thanks for starting clean! I had to make a few adjustments. 1-I modified the server.xml file in /opt/atlassian-crowd-2.8.3/apache-tomcat/conf/server.xml so there are two connectors per the instructions on the Atlassian site. I have backed up this good server.xml file in /etc/temp/ if you want to browse it to see what I did. Of note is that I removed all the jargon referencing the types of ciphers available to simplify things for now. 2-I modified /data/crowd/crowd.properties to have crowd.server.url=https\://localhost\:8443/crowd/services/ application.login.url=https\://localhost\:8443/crowd/console/ But that would cause my login to error with an error saying it was unable to reach the authentication server. I scratched my head for a bit. When I revert the values to just using non-SSL and try to log in, I just get an "invalid login" (I don't know the crowdadm password). So I worked under the assumption that if I can configure SSL to get an "invalid login" when logging in then it would work when provided real credentials. So, I then changed /data/crowd/crowd.proprties to: crowd.server.url=https\://auth.mbari.org\:8443/crowd/services/ application.login.url=https\://auth.mbari.org\:8443/crowd/console/ And now when I try to log in with SSL it says "invalid login". Strange because all the other values I can find only show "localhost" .. in any case... Can you try to log in now? {noformat} ## (/) Next I moved on to configuring the connection to MBARI's LDAP server to enable our logins through Crowd and CrowdID ## (/) I clicked on "Add Directory" in crowd. ## (/) I selected "Connector" then clicked Next ## (/) I put ldap.shore.mbari.org as the name of the server ## (/) I selected "Use memberOf for group memberships" ## (/) I used "OU=AllUsers,DC=shore,DC=mbari,DC=org" for the Base DN ## (/) I used "CN=LDAPbind,OU=Special,OU=AllUsers,DC=shore,DC=mbari,DC=org" for the Username (talk to Pat Allen for password) ## (/) I tested the connection (button click) and it passed. ## (/) I de-selected all the capabilities of the connector as it is a ready only connector and then saved it. It synchronized correctly! ## (/) At first, I could not login using my MBARI credentials, but after going to the "crowd" application in crowd (logged in as the local admin), I had to add the LDAP directory and configure it to "Allow all to authenticate", then I was able to login. After this, the last step was to get this to run as a different user and lock down various directories. I went through the entire directory structure /opt/atlassian... and set up so that root owned all read-only locations and DB_Collaboration (account set up by IS) owned the other stuff. I also gave full ownership to the /data/crowd directory to DB_Collaboration so it could write there. Pat set up a script to start on boot and after a little tweaking, it now starts on boot. {warning:title=CrowdID log file} One thing that came up here was that when the crowdID application ran, it tried to write a log file to the location where the process was launched from (which is /opt/atlassian...). This is a bad thing and I figured out that I could change that location by changing the file /opt/atlassian-crowd-2.8.3/crowd-openidserver-webapp/WEB-INF/classes/log4j.properties and hardcoding the /data/crowd/logs/atlassian-crowd-openid-server.log and then restarted the application. {warning} # (/) It is finally time to move on to the version 4 upgrade ... holy crap. I first went to the *new* crowd install (auth.mbari.org) and logged in as the crowdadm. # (/) I clicked on Applications, then on Add Application # (/) I selected JIRA from the Application type drop-down # (/) I entered jira445 as the username. Ask Kevin about the password. # (/) I used http://bugs.shore.mbari.org:8081 as the URL # (/) I used 134.89.12.31 as the IP address.]]> 27558163 19073853 19041162 27099725 ** response ** 0 * Channel 1 Power Control = 0 (Off) ** $1PC0 ** Response: ** 0 * Channel 1 Power Control = 1 (On) ** $1PC1 ** Response: ** 1 * Channel 1 Power Read ** $1PR ** Response: ** 1 * Read Block ** $1RB read temperature sensor block (4 channels) ** $5RB read pH sensor block (Seabird 18s) ** Response: ** \*+02712.00 ** \*+00200.00 ** \*+00125.76 ** \*+00347.95 * Read Data ** $1RD read tDGH channel 1 (temperature ch 1) ** $2RD read tDGH channel 2 (temperature ch 2) ** $3RD read tDGH channel 3 (temperature ch 3) ** $4RD read tDGH channel 4 (temperature ch 4) ** $5RD read tDGH channel 5 (pH sensor ch 1) ** $6RD read tDGH channel 6 (pH sensor ch 2) ** $7RD read tDGH channel 7 (pH sensor ch 3) ** $8RD read tDGH channel 8 (pH sensor ch 4) ** $9RD read tDGH channel 9 (pH sensor ch 5) ----   \\ DGH Can upgrade project was prioritized up by the Engineering Director in Sep. 2013 in order to remove the project from the 2014 project list and make good on an unrealized project from 2012.  The original scope of work was to fit MBARI HRpH instruments to the DGH can.   RS485 feature of MBARI HRpH was planned.   In 2013, the requirement was added to use the new Seabird 18s digital pH instrument since this instrument was the result of a tech transfer by Thom Maughan to Seabird of the MBARI HRpH instrument and the Seabird 18s is now available as of 4Q2013 (though it is not advertised yet on the Seabird website).   The Seabird 18s does not have an RS485 interface option which motivated a different engineering approach (use of custom microprocessor to aggregate the RS232 instruments and present as a single DGH module to keep the PC software simple). h2. DGH Can Upgrade (tDGH) Requirements: * requirements defined, then reviewed with Ed Peltzer and Dale Graves Sep 2013 h3. Hardware h4. Sensor Interface * 4 channel analog for platinum sensor resistors (RTDs from Omega, same as existing DGH can) * 4 channel digital for RS232 Seabird 18s sensors (4 pin, 12v, RS232). Ability to electrically isolate in case of pH instrument failure. h4. ROV Interface * RS232 * Single power supply \+24v, GND (+24v is more readily available on ROV per DG) h3. Mechanical * The existing DGH housing is corroded, a new housing is desired with 4 connectors for temperature and 4 connectors for pH and 1 connector for ROV h3. Software h4. DGH Can * Must support maximum 1 Hz sample rate (once per second); logging at 1 Hz as well. Typically logging is at 0.5 Hz. Would like 0.2, 0.1 Hz options as well. h4. PC * Installer or standalone executable, must not 'clobber' shared dll's used by another program.  ** virtual machine will be created of Ed's laptop to 'test' the lab view installer.   We will do this early to gate the approach on software. * Same functional and graphical features as existing software.  GUI similar to what we now have in layout with graphical display of pH and "sliders" (horizontal bar graphs) for temperature. GUI should also allow for: ** a. Selection of any temp sensor to go with any pH sensor. ** b. Separate calibration constants (slope & offset) for each pH sensor. ** c. Separate temperature offsets for each temp sensor. h3. Time and Division of Labor: * Ed is the customer and supplies the requirements.   Ed's laptop will need to have a virtual machine constructed to prevent the newer LabView Dll's from affecting an older program.   From time to time Ed will need to log into this virtual machine so that Thom/Dale can test. * Several attempts at making a VM wire tried, Ed's directory replication setup causes VMWare failure * Thom to provide Dale the software def for serial comms so he can work on the Labview GUI ahead of hardware availabilty (Complete) * Thom will be responsible for the project and perform the electronics design and write software/firmware for microprocessor. ** Thom will define serial communications protocol. (In Progress, working over Thxgiving) * Jose will do the PCB layout (Complete) * Indtec will do the assembly (some parts are BGA) * Dale will do the PC Software / GUI (Labview to be used) * Dale will update the instrument housing and spec out the external connectors h3. tDGH controller bringup / hardware design verification * Partial stuff, MSP430F5438A + MAX3222 + MUX + Power Converter + LEDs ** isolating converter consumes \~87mA with 10mA load on 3.3v ** JTAG connection, 14pin connector orients to edge of board, works well ** LEDs work ** UART connection to MAX3222 works ** GPIO connections to INST PWR Enable works * Full stuff controller board received from Indtec on Dec. 4, Tom Marion built up interface board on Dec. 4 ** Had Jose cut/jmp to fix MAX3222, Mux lines, pull ups on Mux Dec 5. **   * PCB Issues ** MUX lines not connected to processor, fixed with blue wires, fixed in rev2. FIXED v2 28 Dec 2013 ** no TX output on MAX3222, C1/C2 cross wired, Fixed with circuit mod. FIXED v2 ** Should have pullups not pull downs on serial lines for MUX - FIXED v2 ** Isolating RS232 not working FIXED v2 * Firmware ** Clock subsystem, 16.777 MHz operation for SMCLK, MCLK, ACLK, Tektronix TDS2024B measures 16.89 MHz (100ns grid). 0.7% error. *** 115200 measures a bit over 8.67 usec per bit time, closer to 8.8 usec. Normally high signal. ** LEDs ** UART0 to 3 sending data, confirmed 115200 ** INST1 PWR Enable tested and working * ToDo ** UART to Instrument connection (fix MAX3222). C1/C2 caps wired incorrectly (fixed in rev 2) DONE ** UART to ROV isolated connection, need to figure out why it's not working. DONE ** Finish hardware bringup and spin rev2 of the controller board. DONE ** UART ISR *** Test serial mux, latency, glitch, etc DONE ** Write test program for exercising relays on interface board DONE ** Write DGH module interface for temperature readings DONE ** Write Seabird 18s interface and driver DONE ** Wire up the DGH housing connectors and mount the board set and DGH module ** Integration test with 5 pH and max sample rate (1Hz) in test tank h3. Seabird 18s setup * setoutputformat= 0 ** 0 \*±vvvvv.vv\r\n pH probe voltage in mV, MBARI style output ** 1 ±vvvv.vv\r\n pH probe voltage in mV ** 2 v.vvvv\r\n pH probe voltage in SBE 18 volts * cal for fast response (request, response immediate, othewise a couple seconds) * setautorun=0 no autorun ** enter interactive mode on powerup, 1 enters tsc on powerup. If tsc is stopped via ESC the instrument re-enters tsc on power cycle. * setexecuted=0 suppress tags ** 1 do not suppress * setecho=0 suppress echoed characters ** 1 do not suppress * setprompt=0 suppress 'S>' ** 1 do not suppress * setbaud=115200 ** 9600, 38400, 115200 * setsampleperiod=1 ** n seconds between scans when running continuously. Each sample is comprised of an average of 8 scans. * Operational commands ** ts returns a measurement in one of the above formats. ** tsc continuously samples and returns the measurement in one of the above formats. The update rate is 1Hz which is an average of 16 samples. Return to interactive mode via the ESC key. ** gethd ** getcd ** getec ** getsd ** getcc * Electrical ** Voltage input 11VDC - 18VDC ** Current consumption 82mA at 12VDC h3. DGH D5451 Module setup * Setup the D5451 to 115200 baud, procedure: ** Wire the default pin on the D5451 to Ground, set terminal to 300 baud (8N1) with serial port connected and 12v supplied (47mA) ** $1WE (echo \*) ** $1SU3108E1C2 (echo \*) ** change terminal settings to 115200, then disconnect the Default pin from ground (leave floating) ** $1RS should return \*3108E1C2 ** $1RD will take a sample, returns \*-99999.99 with input floating (no thermistor) h3. Serial Protocol * Power All (0=off, 1=on) ** $1PA0 ** response ** 0 * Channel 1 Power Control = 0 (Off) ** $1PC0 ** Response: ** 0 * Channel 1 Power Control = 1 (On) ** $1PC1 ** Response: ** 1 * Channel 1 Power Read ** $1PR ** Response: ** 1 * Read Block ** $1RB read temperature sensor block (4 channels) ** $5RB read pH sensor block (Seabird 18s) ** Response: ** \*+02712.00 ** \*+00200.00 ** \*+00125.76 ** \*+00347.95 * Read Data ** $1RD read tDGH channel 1 (temperature ch 1) ** $2RD read tDGH channel 2 (temperature ch 2) ** $3RD read tDGH channel 3 (temperature ch 3) ** $4RD read tDGH channel 4 (temperature ch 4) ** $5RD read tDGH channel 5 (pH sensor ch 1) ** $6RD read tDGH channel 6 (pH sensor ch 2) ** $7RD read tDGH channel 7 (pH sensor ch 3) ** $8RD read tDGH channel 8 (pH sensor ch 4) ** $9RD read tDGH channel 9 (pH sensor ch 5)]]> 27066963 27099726 ** response ** 0 * Channel 1 Power Control = 0 (Off) ** $1PC0 ** Response: ** 0 * Channel 1 Power Control = 1 (On) ** $1PC1 ** Response: ** 1 * Channel 1 Power Read ** $1PR ** Response: ** 1 * Read Block ** $1RB read temperature sensor block (4 channels) ** $5RB read pH sensor block (Seabird 18s) ** Response: ** \*+02712.00 ** \*+00200.00 ** \*+00125.76 ** \*+00347.95 * Read Data ** $1RD read tDGH channel 1 (temperature ch 1) ** $2RD read tDGH channel 2 (temperature ch 2) ** $3RD read tDGH channel 3 (temperature ch 3) ** $4RD read tDGH channel 4 (temperature ch 4) ** $5RD read tDGH channel 5 (pH sensor ch 1) ** $6RD read tDGH channel 6 (pH sensor ch 2) ** $7RD read tDGH channel 7 (pH sensor ch 3) ** $8RD read tDGH channel 8 (pH sensor ch 4) ** $9RD read tDGH channel 9 (pH sensor ch 5) \\ \\ \\ \\ \\ \\ \\ \\ \\ ----\\ \\ \\ \\ \\ \\ \\ \\ \\ DGH Can upgrade project was prioritized up by the Engineering Director in Sep. 2013 in order to remove the project from the 2014 project list and make good on an unrealized project from 2012.  The original scope of work was to fit MBARI HRpH instruments to the DGH can.   RS485 feature of MBARI HRpH was planned.   In 2013, the requirement was added to use the new Seabird 18s digital pH instrument since this instrument was the result of a tech transfer by Thom Maughan to Seabird of the MBARI HRpH instrument and the Seabird 18s is now available as of 4Q2013 (though it is not advertised yet on the Seabird website).   The Seabird 18s does not have an RS485 interface option which motivated a different engineering approach (use of custom microprocessor to aggregate the RS232 instruments and present as a single DGH module to keep the PC software simple). h2. DGH Can Upgrade (tDGH) Requirements: * requirements defined, then reviewed with Ed Peltzer and Dale Graves Sep 2013 h3. Hardware h4. Sensor Interface * 4 channel analog for platinum sensor resistors (RTDs from Omega, same as existing DGH can) * 4 channel digital for RS232 Seabird 18s sensors (4 pin, 12v, RS232). Ability to electrically isolate in case of pH instrument failure. h4. ROV Interface * RS232 * Single power supply \+24v, GND (+24v is more readily available on ROV per DG) h3. Mechanical * The existing DGH housing is corroded, a new housing is desired with 4 connectors for temperature and 4 connectors for pH and 1 connector for ROV h3. Software h4. DGH Can * Must support maximum 1 Hz sample rate (once per second); logging at 1 Hz as well. Typically logging is at 0.5 Hz. Would like 0.2, 0.1 Hz options as well. h4. PC * Installer or standalone executable, must not 'clobber' shared dll's used by another program.  ** virtual machine will be created of Ed's laptop to 'test' the lab view installer.   We will do this early to gate the approach on software. * Same functional and graphical features as existing software.  GUI similar to what we now have in layout with graphical display of pH and "sliders" (horizontal bar graphs) for temperature. GUI should also allow for: ** a. Selection of any temp sensor to go with any pH sensor. ** b. Separate calibration constants (slope & offset) for each pH sensor. ** c. Separate temperature offsets for each temp sensor. h3. Time and Division of Labor: * Ed is the customer and supplies the requirements.   Ed's laptop will need to have a virtual machine constructed to prevent the newer LabView Dll's from affecting an older program.   From time to time Ed will need to log into this virtual machine so that Thom/Dale can test. * Several attempts at making a VM wire tried, Ed's directory replication setup causes VMWare failure * Thom to provide Dale the software def for serial comms so he can work on the Labview GUI ahead of hardware availabilty (Complete) * Thom will be responsible for the project and perform the electronics design and write software/firmware for microprocessor. ** Thom will define serial communications protocol. (In Progress, working over Thxgiving) * Jose will do the PCB layout (Complete) * Indtec will do the assembly (some parts are BGA) * Dale will do the PC Software / GUI (Labview to be used) * Dale will update the instrument housing and spec out the external connectors h3. tDGH controller bringup / hardware design verification * Partial stuff, MSP430F5438A + MAX3222 + MUX + Power Converter + LEDs ** isolating converter consumes \~87mA with 10mA load on 3.3v ** JTAG connection, 14pin connector orients to edge of board, works well ** LEDs work ** UART connection to MAX3222 works ** GPIO connections to INST PWR Enable works * Full stuff controller board received from Indtec on Dec. 4, Tom Marion built up interface board on Dec. 4 ** Had Jose cut/jmp to fix MAX3222, Mux lines, pull ups on Mux Dec 5. **   * PCB Issues ** MUX lines not connected to processor, fixed with blue wires, fixed in rev2. FIXED v2 28 Dec 2013 ** no TX output on MAX3222, C1/C2 cross wired, Fixed with circuit mod. FIXED v2 ** Should have pullups not pull downs on serial lines for MUX - FIXED v2 ** Isolating RS232 not working FIXED v2 * Firmware ** Clock subsystem, 16.777 MHz operation for SMCLK, MCLK, ACLK, Tektronix TDS2024B measures 16.89 MHz (100ns grid). 0.7% error. *** 115200 measures a bit over 8.67 usec per bit time, closer to 8.8 usec. Normally high signal. ** LEDs ** UART0 to 3 sending data, confirmed 115200 ** INST1 PWR Enable tested and working * ToDo ** UART to Instrument connection (fix MAX3222). C1/C2 caps wired incorrectly (fixed in rev 2) DONE ** UART to ROV isolated connection, need to figure out why it's not working. DONE ** Finish hardware bringup and spin rev2 of the controller board. DONE ** UART ISR *** Test serial mux, latency, glitch, etc DONE ** Write test program for exercising relays on interface board DONE ** Write DGH module interface for temperature readings DONE ** Write Seabird 18s interface and driver DONE ** Wire up the DGH housing connectors and mount the board set and DGH module ** Integration test with 5 pH and max sample rate (1Hz) in test tank h3. Seabird 18s setup * setoutputformat= 0 ** 0 \*±vvvvv.vv\r\n pH probe voltage in mV, MBARI style output ** 1 ±vvvv.vv\r\n pH probe voltage in mV ** 2 v.vvvv\r\n pH probe voltage in SBE 18 volts * cal for fast response (request, response immediate, othewise a couple seconds) * setautorun=0 no autorun ** enter interactive mode on powerup, 1 enters tsc on powerup. If tsc is stopped via ESC the instrument re-enters tsc on power cycle. * setexecuted=0 suppress tags ** 1 do not suppress * setecho=0 suppress echoed characters ** 1 do not suppress * setprompt=0 suppress 'S>' ** 1 do not suppress * setbaud=115200 ** 9600, 38400, 115200 * setsampleperiod=1 ** n seconds between scans when running continuously. Each sample is comprised of an average of 8 scans. * Operational commands ** ts returns a measurement in one of the above formats. ** tsc continuously samples and returns the measurement in one of the above formats. The update rate is 1Hz which is an average of 16 samples. Return to interactive mode via the ESC key. ** gethd ** getcd ** getec ** getsd ** getcc * Electrical ** Voltage input 11VDC - 18VDC ** Current consumption 82mA at 12VDC h3. DGH D5451 Module setup * Setup the D5451 to 115200 baud, procedure: ** Wire the default pin on the D5451 to Ground, set terminal to 300 baud (8N1) with serial port connected and 12v supplied (47mA) ** $1WE (echo \*) ** $1SU3108E1C2 (echo \*) ** change terminal settings to 115200, then disconnect the Default pin from ground (leave floating) ** $1RS should return \*3108E1C2 ** $1RD will take a sample, returns \*-99999.99 with input floating (no thermistor) h3. Serial Protocol * Power All (0=off, 1=on) ** $1PA0 ** response ** 0 * Channel 1 Power Control = 0 (Off) ** $1PC0 ** Response: ** 0 * Channel 1 Power Control = 1 (On) ** $1PC1 ** Response: ** 1 * Channel 1 Power Read ** $1PR ** Response: ** 1 * Read Block ** $1RB read temperature sensor block (4 channels) ** $5RB read pH sensor block (Seabird 18s) ** Response: ** \*+02712.00 ** \*+00200.00 ** \*+00125.76 ** \*+00347.95 * Read Data ** $1RD read tDGH channel 1 (temperature ch 1) ** $2RD read tDGH channel 2 (temperature ch 2) ** $3RD read tDGH channel 3 (temperature ch 3) ** $4RD read tDGH channel 4 (temperature ch 4) ** $5RD read tDGH channel 5 (pH sensor ch 1) ** $6RD read tDGH channel 6 (pH sensor ch 2) ** $7RD read tDGH channel 7 (pH sensor ch 3) ** $8RD read tDGH channel 8 (pH sensor ch 4) ** $9RD read tDGH channel 9 (pH sensor ch 5)]]> 27066964 27590933 4.4: [https://confluence.atlassian.com/display/JIRA044/Migrating+JIRA+to+Another+Server] ## The JIRA configuration tool: [https://confluence.atlassian.com/display/JIRA044/Using+the+JIRA+Configuration+Tool] h5. Steps # (/) Create new VM named bugs.mbari.org in the DMZ # (/) Have Neil create database Jira_Temp on solstice2.shore.mbari.org # (/) Have Neil create database Jira on solstice2.shore.mbari.org # (/) Have Pat install Java 7 on bugs.shore.mbari.org # (/) Have Pete plumb holes through firewall so processes on bugs.mbari.org can get to Solstice2 # (/) Have Pat create DB_Collaboration account on bugs so it can run JIRA under that account and it can connect to solstice2 using that NT Domain account. # (/) Upgrade license on Atlassian site # (/) Log into bugs.shore.mbari.org # (/) Download 3.13.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 4.4.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 5.2.11 standalone Linux 64 bit tar.gz (not sure this version is necessary, but at least I have it) # (/) Unzip and untar the file to /opt # (/) Download latest JIRA (6.4.7 as of this writing). # (/) Unzip and untar it to /opt # Performed Test Upgrade ## (/) In order to export the current stuff in JIRA, I had to shut off access so people could not change the data while I was backing it up. ## (/) I ssh'd to oceana.mbari.org as root and edited the /opt/jira/conf/server.xml file and commented out the Connector section that had the port of 8010 to shut it off from the normal serving route. ## (/) I uncommented the 8082 port connector and the 8443 port connector so that I could still get to the server. ## (/) I stopped and started the JIRA server and in the log file I got a "keystore was tampered with..." which is not surprising. ## (/) I could then browser over to http://oceana.mbari.org:8082/jira ## (/) Then through the Administration console, I did an XML backup ## (/) I then created a tar of all the attachments in the /data/jira_3_12/attachments directory ## (/) I moved both the XML and tar files to the /root/jira-upgrade directory ## (/) I then reversed the changes to the server.xml file and shut down JIRA ## (/) I left it down during the next steps in case it went so well, I could just point people to the new server (yeah, right). ## (/) I then browsed to the crowd server on oceana and add a new application using: ### URL: http://bugs.mbari.org/jira3135 ### IP: 134.89.2.29 ### Name: JIRA3135 ### Password: (ask Kevin) :) ## (/) On bugs, I made a copy of the JIRA 3.13.5 download in the /opt directory and unzipped and untarred it. ## (/) In order to configure the crowd connection I did the following: ### (/) I scp'd the /opt/crowd/client/crowd-integration-client-1.6.jar file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I removed the existing 1.6.1 crowd client jar from the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I scp'd the /opt/crowd/client/conf/crowd.properties file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I scp'd the /opt/crowd/client/conf/crowd-ehcache.xml file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I edited the crowd.properties file on bugs to look like: {noformat} application.name JIRA3135 application.password (ask Kevin) application.login.url http://oceana.mbari.org:8095/crowd/console/ crowd.server.url http://oceana.mbari.org:8095/crowd/services/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 0 session.lastvalidation session.lastvalidation {noformat} ### (/) I edited the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/osuser.xml file to comment out the current authentication mechanism and then uncomment the crowd one. ## (/) I then edited the /opt/atlassian-jira-standalone-3.13.5/conf/server/xml file and configured the database connection to the Jira_Temp database on Solstice2. I looked like this: {noformat} {noformat} ## (/) Edit the /opt/atlassian/jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/entityengine.xml and changed it from 'hsql' to 'mssql' and delete the line with "PUBLIC" in it per the instructions in the comments in that file. ## (/) I edited the /etc/httpd/conf/httpd.conf file and created a proxy pass at the bottom of the file to point a normal URL to the default port 8080 for JIRA: {noformat} # Proxy Pass for JIRA ProxyPass http://bugs.mbari.org:8080 ProxyPassReverse http://bugs.mbari.org:8080 {noformat} ## (/) I restarted Apache ## (/) I scp'd the jtds driver from oceana to the /opt/atlassian-jira-standalone-3.13.5/common/lib directory (you could down from the internet) ## (/) I then went to the /opt/atlassian-jira-standalone-3.13.5/ directory and ran './bin/startup.sh'. From the log file, I could tell things were hanging. After some troubleshooting I am wondering if the local firewall is preventing the application to get access to the database on solstice2. I can telnet to port 1433, but I can't browse to the base http://bugs.mbari.org from anywhere but the local web browser. I have submitted a ticket. ## (/) I restarted the old JIRA with my hopes dashed :(. ## (/) Pat disabled the firewall on bugs.mbari.org but it still hung trying to connect to solstice2.shore.mbari.org. That is really, really perplexing. Neil mentioned that solstice2 is using Kerberos and solstice is not. Checking with the JTDS docs, version 1.3.1 of the driver added kerberos support, so I downloaded that driver and added the 'userKerberos=true' property to the URL in the server.xml file and restarted. Got an error about no credentials, so added user and password properties to the URL. Nope, no luck. Never did figure this one out, but I had Pat pull the VM inside the firewall and after some thrash it worked. Well, it sort of worked ... sigh. It turns out I had downloaded the standard version instead of the enterprise version. I need to redo this work ... grrr. ## (/) I deleted all the tables in the Jira_Temp database and removed the /data/jira3135/indexes directory (and recreated). ## (/) I downloaded the enterprise version of the 3.13.5 server. I made a copy in the /opt directory and unzipped and untarred the file. ## (/) I went back to crowd and edited the application to change the properties to: ### URL: http://bugs.shore.mbari.org:8080 ### IP: 134.89.12.31 ### Name: jira3135 ### Password: (ask Kevin) :) ## (/) I then repeated the steps above to get the server up and running with the following differences: ### The server name is now bugs.shore.mbari.org ### The paths given above are a little different in that they no longer say "standard" but say "enterprise" ### I deleted the proxy pass as it seemed to have issues before and this is only temporary anyway. ## (/) I then browsed to http://bugs.shore.mbari.org:8080 ## (/) It took me to the start up page and at the top was the option to 'import your existing data'. Seemed too good not to try. I clicked on the link. It asked me for the backup file location and the location where the indexes would be stored. ## (/) I copied the XML zip file and the attachments tar file to the /data/original directory. ## (/) I created the /data/jira3135/indexes and used those directories ... it fired off the import and I waited. ## (/) I tailed the log file to watch the import. Holy crap, it worked!!! I could log in and everything! I copied the results from the log file here for posterity sake: {noformat} 2015-07-22 20:55:45,156 http-8080-Processor22 INFO [jira.action.admin.DataImport] Running data import 2015-07-22 20:55:45,179 http-8080-Processor22 INFO [jira.action.admin.DataImport] Importing data.. 2015-07-22 20:55:45,186 http-8080-Processor22 INFO [jira.action.admin.DataImport] Start parsing XML with SAX Parser 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] XML successfully parsed 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] Removing all entries from the database. 2015-07-22 20:56:24,593 http-8080-Processor22 INFO [jira.action.admin.DataImport] All entries removed. 2015-07-22 20:56:24,594 http-8080-Processor22 INFO [jira.action.admin.DataImport] Started storing 410414 Generic Values 2015-07-22 21:01:51,967 http-8080-Processor22 INFO [jira.action.admin.DataImport] Finished storing Generic Values 2015-07-22 21:01:52,329 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:52,361 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:54,683 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLink' to module 'jira.user.format:profile-link-user-format'. 2015-07-22 21:01:54,724 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullName' to module 'jira.user.format:full-name-user-format'. 2015-07-22 21:01:54,773 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkSearcher' to module 'jira.user.format:profile-link-searcher-user-format'. 2015-07-22 21:01:54,784 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkExternal' to module 'jira.user.format:profile-link-external-user-format'. 2015-07-22 21:01:54,795 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkActionHeader' to module 'jira.user.format:profile-link-action-header-user-format'. 2015-07-22 21:01:54,807 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullProfile' to module 'jira.user.format:full-profile-user-format'. 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/comments 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/issues 2015-07-22 21:01:55,641 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/plugins 2015-07-22 21:01:55,867 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:01:55,871 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/issues does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:55,873 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/comments does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,033 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,257 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,889 http-8080-Processor22 ERROR [atlassian.jira.upgrade.ConsistencyCheckImpl] Attachments are turned on, but attachment path [/data/jira_3_12/attachments] invalid - disabling attachments 2015-07-22 21:02:13,904 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Detected that an upgrade is needed; existing data at build 299 2015-07-22 21:02:13,907 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Doing Upgrade... 2015-07-22 21:02:13,915 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value' succeeded 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 317 2015-07-22 21:02:13,944 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite filters - make each filter a favourite of its owner. 2015-07-22 21:02:17,822 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build319] Could not find author 'fpy' for filter with id '10040' 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite filters - make each filter a favourite of its owner.' succeeded 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 319 2015-07-22 21:02:17,995 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise Share Permissions. Move old shares to new shares. 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise Share Permissions. Move old shares to new shares.' succeeded 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 321 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Migrating the old JIRA UI colors to the new JIRA 3.13 colors 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build322] Custom color detected for jira.lf.menu.bgcolour : #336699 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Migrating the old JIRA UI colors to the new JIRA 3.13 colors' succeeded 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 322 2015-07-22 21:02:18,025 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite dashboards - make each dashboard a favourite of its owner. 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'cmcgann' for dashboard with id '10030' 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'fpy' for dashboard with id '10060' 2015-07-22 21:02:18,423 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'kanna' for dashboard with id '10040' 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite dashboards - make each dashboard a favourite of its owner.' succeeded 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 325 2015-07-22 21:02:18,625 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Reindexing all data in JIRA to include Favourites. 2015-07-22 21:02:18,648 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All starting... 2015-07-22 21:02:18,650 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 0% complete. Current index: Issue 2015-07-22 21:02:18,654 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:02:18,809 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 1% complete. Current index: Issue 2015-07-22 21:02:18,855 indexerPool-2-thread-10 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 2% complete. Current index: Issue 2015-07-22 21:02:18,899 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 3% complete. Current index: Issue 2015-07-22 21:02:18,945 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 4% complete. Current index: Issue 2015-07-22 21:02:19,012 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 5% complete. Current index: Issue . . . 2015-07-22 21:02:26,164 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 95% complete. Current index: Issue 2015-07-22 21:02:26,232 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 96% complete. Current index: Issue 2015-07-22 21:02:26,316 indexerPool-2-thread-9 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 97% complete. Current index: Issue 2015-07-22 21:02:26,771 indexerPool-2-thread-3 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: Issue 2015-07-22 21:02:27,261 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 8607ms. Indexer: DefaultIndexManager: paths: [/data/jira3135/indexes/issues, /data/jira3135/indexes/comments] 2015-07-22 21:02:27,263 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: SearchRequest 2015-07-22 21:02:27,268 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,293 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: SearchRequest 2015-07-22 21:02:27,308 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: PortalPage 2015-07-22 21:02:27,312 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,377 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: PortalPage 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 115ms. Indexer: SharedEntityIndexManager: paths: [/data/jira3135/indexes/entities/portalpage, /data/jira3135/indexes/entities/searchrequest] 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All complete. Total time: 8722ms. 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Reindexing all data in JIRA to include Favourites.' succeeded 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 326 2015-07-22 21:02:27,397 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade succeeded! Setting data build number to 360 2015-07-22 21:02:27,469 JiraQuartzScheduler_Worker-0 WARN [service.services.export.ExportService] Backup directory /data/jira_3_12/backup does not exist {noformat} {warning:title=Paths} It appears that the upgraded JIRA will still look for the attachments and the backup locations in the original places. So I created /data/jira_3_12/backup and untarred the original attachments to /data/jira_3_12 and then everything worked (including attachements) in the new JIRA. {warning} ## (/) I then used the upgraded JIRA to generate a new XML backup and stored it in /data/original/3.13.5 along with another tar of the files in /data/jira_3_12/attachments. ## (/) I then shutdown the JIRA server. *I should be ready to move on to version 4 upgrade WHEW* ## So, before moving on, I decided that it would be a really good idea to spin up a new Crowd instance to get rid of the :8443 in the URL and to move off of RedHat per IS requests. I have a ticket in for a new VM and a new database to try to get this going. I am waiting on that before moving on. ## (/) Pat created the VM and Neil created the database. ## (/) I logged into auth.mbari.org (name of the VM) and downloaded crowd which I unzipped to the /opt directory ## (/) I then created a /data/crowd directory and gave my account permissions on it and then edited the /opt/atlassian..../crowd-webapp/WEB-INF/classes/crowd-init.properties file to set that as the crowd home directory. ## (/) The instructions say to download the JDBC driver, but they already have JTDS 1.2.7 in the download so I did not do anything. ## (/) You have to manually connect up CrowdID to a database as they setup wizard does not currently do this. ### (/) They say to download the driver, but again 1.2.7 was there so I did nothing. ### (/) I edited the /opt/atlassian.../apache-tomcat/conf/Catalina/localhost/openidserver.xml to look like: {noformat} {noformat} ### (/) I edited the /opt/atlassian.../build.properties files to look like: {noformat} # Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See https://confluence.atlassian.com/display/CROWD/Connecting+Crowd+to+a+Database hibernate.dialect=org.hibernate.dialect.SQLServerDialect # The Hibernate transaction factory to use. See https://confluence.atlassian.com/display/CROWD/Configuring+Crowd hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory # The http port you wish to run crowd from, ie: http://localhost:8095/crowd crowd.tomcat.connector.port=8095 # Tomcat requires a unique port for shutdown crowd.tomcat.shutdown.port=8020 # Crowd context root crowd.url=http://localhost:8095/crowd # Demo context root demo.url=http://localhost:8095/demo # OpenID server context root openidserver.url=http://localhost:8095/openidserver {noformat} ### (/) I then ran the build.sh script in the root of /opt/atlassian... ## (/) I fired up crowd using the /opt/atlassian.../start_crowd.sh script ## (/) I then went to http://auth.mbari.org:8095/crowd to kick off the start up wizard ## (/) I grabbed a new eval license from my account on atlassian and pasted into the license page. ## (/) I selected "New install" on the next page. ## (/) I configured the JDBC connection using this connection URL with user DB_Collaboration {noformat} jdbc:jtds:sqlserver://dione.mbari.org:51001/Crowd;domain=SHORE;useNTLMv2=TRUE {noformat} ## (/) I left the "Options" as they came up {warning:title=Paths} Not sure if this is a problem, but because I started the set up using auth.mbari.org, it set the Base URL to http://auth.mbari.org:8095/crowd instead of localhost. Hope that is not a problem. We will see. {warning} ## (/) I configured the email connection using the settings from [here|https://wind.shore.mbari.org/is/howto/email/mbarimail/imap] and I used my network login (probably shouldn't be doing that ... not sure where it stores my password, but I am assuming in the DB). ## (/) For the local admin account, I created a user named 'crowdadm' so it would not clash with my LDAP account. See Kevin Gomes for password information. ## (/) I checked the OpenID server as an integrated application ## (/) It then took me to the login page and I logged in using the newly minted admin account. Seemed all is well so far. ## (/) I visited the openidserver URL as well and that seemed OK. ## (/) I decided to wait on configuring the MBARI LDAP directory until I got everything with SSL working. ## (/) Now the next step was to follow the directions to configure Crowd to run over SSL found [here|https://confluence.atlassian.com/display/CROWD/Configuring+Crowd+to+Work+with+SSL] ## (/) I shutdown crowd. Note that the stop script does not shutdown things correctly and I noticed the crowd app running as root. That should not be if I started as kgomes. Not sure what is up with that. ## (/) Now Joe had already configured SSL once, so I used his connector configuration in the server.xml file and so the final file looked like: {noformat} {noformat} ## (/) I then edited the /data/crowd/crowd.properties to look like: {noformat} #Sat Aug 01 09:05:15 PDT 2015 session.lastvalidation=session.lastvalidation session.tokenkey=session.tokenkey crowd.server.url=https\://localhost\:8443/crowd/services/ application.name=crowd http.timeout=30000 session.isauthenticated=session.isauthenticated application.login.url=https\://localhost\:8443/crowd/console/ session.validationinterval=0 application.password=Y1Xp3OorCmsOP4eruL1dmH {noformat} One thing to note here is that based on a comment from the SSL configuration page at atlassian (Steve's comment), you are supposed to leave all the host names the same. For example, if the file says localhost, leave it localhost. So this created a bit of a problem based on the fact that I had left the base URL pointing to auth.mbari.org in the wizard steps above. That step wrote auth.mbari.org to the /data/crowd/crowd.properties. All the other files reference localhost, so to be consistent, I changed auth.mbari.org to localhost in the /data/crowd/crowd.properties file. We will see if this works. ## (/) Per the instructions on the atlassian page (referenced above), I also edited the build.properties file and the /client/conf/crowd.properties files before I restarted and used the SSL URLs ## build.properties: {noformat} # Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See https://confluence.atlassian.com/display/CROWD/Connecting+Crowd+to+a+Database hibernate.dialect=org.hibernate.dialect.SQLServerDialect # The Hibernate transaction factory to use. See https://confluence.atlassian.com/display/CROWD/Configuring+Crowd hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory # The http port you wish to run crowd from, ie: http://localhost:8095/crowd crowd.tomcat.connector.port=8095 # Tomcat requires a unique port for shutdown crowd.tomcat.shutdown.port=8020 # Crowd context root crowd.url=https://localhost:8443/crowd # Demo context root demo.url=https://localhost:8443/demo # OpenID server context root openidserver.url=https://localhost:8443/openidserver {noformat} ## crowd.properties (client) {noformat} application.name crowd application.password password application.login.url https://localhost:8443/crowd/console/ crowd.server.url https://localhost:8443/crowd/services/ crowd.base.url https://localhost:8443/crowd/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 2 session.lastvalidation session.lastvalidation {noformat} ## (/) Although not stated, I am assuming you would need to run the build.sh script to push the build.properties changes to their proper places, so I did that. Note that before doing that, I know that it will clobber the server.xml changes I made, so I made a copy of that file and diff'd them after and then rolled the previous changes to the new server.xml file. Actually, amazingly enough, it seems to have done the connector entry correctly so I left it after running the build.sh script. ## (/) Crossed my fingers and then restarted crowd. I tailed the catalina.out file and did not see any stack traces so that is a good sign! ## (/) I visited https://auth.mbari.org:8443/crowd first. It could not find that page, but I suspect that is because I am browsing from the outside, so I tried just https://auth.mbari.org/crowd and got a service unavailable. I am suspecting that this is a combination of firewall and proxy pass and I will send this info to Joe. From what I can see on the crowd side, it seems like the server started cleanly, we just can't get to it. I tried to reach it from a browser on the machine itself too (through VNC) with the same service not available. ## (/) Here are the notes from Joe after he fixed it! Wooohooo! {noformat} Hey Kevin, Thanks for starting clean! I had to make a few adjustments. 1-I modified the server.xml file in /opt/atlassian-crowd-2.8.3/apache-tomcat/conf/server.xml so there are two connectors per the instructions on the Atlassian site. I have backed up this good server.xml file in /etc/temp/ if you want to browse it to see what I did. Of note is that I removed all the jargon referencing the types of ciphers available to simplify things for now. 2-I modified /data/crowd/crowd.properties to have crowd.server.url=https\://localhost\:8443/crowd/services/ application.login.url=https\://localhost\:8443/crowd/console/ But that would cause my login to error with an error saying it was unable to reach the authentication server. I scratched my head for a bit. When I revert the values to just using non-SSL and try to log in, I just get an "invalid login" (I don't know the crowdadm password). So I worked under the assumption that if I can configure SSL to get an "invalid login" when logging in then it would work when provided real credentials. So, I then changed /data/crowd/crowd.proprties to: crowd.server.url=https\://auth.mbari.org\:8443/crowd/services/ application.login.url=https\://auth.mbari.org\:8443/crowd/console/ And now when I try to log in with SSL it says "invalid login". Strange because all the other values I can find only show "localhost" .. in any case... Can you try to log in now? {noformat} ## (/) Next I moved on to configuring the connection to MBARI's LDAP server to enable our logins through Crowd and CrowdID ## (/) I clicked on "Add Directory" in crowd. ## (/) I selected "Connector" then clicked Next ## (/) I put ldap.shore.mbari.org as the name of the server ## (/) I selected "Use memberOf for group memberships" ## (/) I used "OU=AllUsers,DC=shore,DC=mbari,DC=org" for the Base DN ## (/) I used "CN=LDAPbind,OU=Special,OU=AllUsers,DC=shore,DC=mbari,DC=org" for the Username (talk to Pat Allen for password) ## (/) I tested the connection (button click) and it passed. ## (/) I de-selected all the capabilities of the connector as it is a ready only connector and then saved it. It synchronized correctly! ## (/) At first, I could not login using my MBARI credentials, but after going to the "crowd" application in crowd (logged in as the local admin), I had to add the LDAP directory and configure it to "Allow all to authenticate", then I was able to login. After this, the last step was to get this to run as a different user and lock down various directories. I went through the entire directory structure /opt/atlassian... and set up so that root owned all read-only locations and DB_Collaboration (account set up by IS) owned the other stuff. I also gave full ownership to the /data/crowd directory to DB_Collaboration so it could write there. Pat set up a script to start on boot and after a little tweaking, it now starts on boot. {warning:title=CrowdID log file} One thing that came up here was that when the crowdID application ran, it tried to write a log file to the location where the process was launched from (which is /opt/atlassian...). This is a bad thing and I figured out that I could change that location by changing the file /opt/atlassian-crowd-2.8.3/crowd-openidserver-webapp/WEB-INF/classes/log4j.properties and hardcoding the /data/crowd/logs/atlassian-crowd-openid-server.log and then restarted the application. {warning} ## (/) Another note is the when an application tried to use the OpenID application, it would get redirected to localhost. I changed the /opt/atlassian.../crowd-openidserver-webapp/WEB-INF/classes/crowd.properties file to look like: {noformat} #Sat Aug 01 10:03:18 PDT 2015 session.lastvalidation=session.lastvalidation session.tokenkey=session.tokenkey crowd.server.url=http\://localhost\:8095/crowd/services/ application.name=crowd-openid-server #application.login.url.template=http\://localhost\:8095/openidserver?returnToUrl\=${RETURN_TO_URL} application.login.url.template=https\://auth.mbari.org/openidserver?returnToUrl\=${RETURN_TO_URL} session.isauthenticated=session.isauthenticated #application.base.url=http\://localhost\:8095/openidserver application.base.url=https\://auth.mbari.org/openidserver #application.login.url=http\://localhost\:8095/openidserver application.login.url=https\://auth.mbari.org/openidserver session.validationinterval=0 application.password=password {noformat} and that seems to have fixed it. # (/) It is finally time to move on to the version 4 upgrade ... holy crap. I first went to the *new* crowd install (auth.mbari.org) and logged in as the crowdadm. # (/) I clicked on Applications, then on Add Application # (/) I selected JIRA from the Application type drop-down # (/) I entered jira445 as the username. Ask Kevin about the password. # (/) I used http://bugs.shore.mbari.org:8081 as the URL # (/) I used 134.89.12.31 as the IP address. # (/) I selected only the MBARI LDAP directory. # (/) Then I selected "Allow all users to authenticate" # (/) Then I clicked on "Add Application" # (/) I VNC'd into bugs.mbari.org. As it turns out, for Linux, there is an installer program to download. I downloaded the .bin for 64 bit Linux installer and moved it to the jira-upgrade directory. # (/) I chmod'd the file to make it executable and ran it. It gave me a warning about not being root, but I went ahead with it. ]]> 27558169 27099723 tags ** 1 do not suppress * setecho=0 suppress echoed characters ** 1 do not suppress * setprompt=0 suppress 'S>' ** 1 do not suppress * setbaud=115200 ** 9600, 38400, 115200 * setsampleperiod=1 ** n seconds between scans when running continuously. Each sample is comprised of an average of 8 scans. * Operational commands ** ts returns a measurement in one of the above formats. ** tsc continuously samples and returns the measurement in one of the above formats. The update rate is 1Hz which is an average of 16 samples. Return to interactive mode via the ESC key. ** gethd ** getcd ** getec ** getsd ** getcc * Electrical ** Voltage input 11VDC - 18VDC ** Current consumption 82mA at 12VDC h3. DGH D5451 Module setup * Setup the D5451 to 115200 baud, procedure: ** Wire the default pin on the D5451 to Ground, set terminal to 300 baud (8N1) with serial port connected and 12v supplied (47mA) ** $1WE (echo \*) ** $1SU3108E1C2 (echo \*) ** change terminal settings to 115200, then disconnect the Default pin from ground (leave floating) ** $1RS should return \*3108E1C2 ** $1RD will take a sample, returns \*-99999.99 with input floating (no thermistor) h3. Serial Protocol * Power All (0=off, 1=on) ** $1PA0 ** response ** 0 * Channel 1 Power Control = 0 (Off) ** $1PC0 ** Response: ** 0 * Channel 1 Power Control = 1 (On) ** $1PC1 ** Response: ** 1 * Channel 1 Power Read ** $1PR ** Response: ** 1 * Read Block ** $1RB read temperature sensor block (4 channels) ** $5RB read pH sensor block (Seabird 18s) ** Response: ** \*+02712.00 ** \*+00200.00 ** \*+00125.76 ** \*+00347.95 * Read Data ** $1RD read tDGH channel 1 (temperature ch 1) ** $2RD read tDGH channel 2 (temperature ch 2) ** $3RD read tDGH channel 3 (temperature ch 3) ** $4RD read tDGH channel 4 (temperature ch 4) ** $5RD read tDGH channel 5 (pH sensor ch 1) ** $6RD read tDGH channel 6 (pH sensor ch 2) ** $7RD read tDGH channel 7 (pH sensor ch 3) ** $8RD read tDGH channel 8 (pH sensor ch 4) ** $9RD read tDGH channel 9 (pH sensor ch 5)]]> 27066961 27099729 ** response ** 0 * Channel 1 Power Control = 0 (Off) ** $1PC0 ** Response: ** 0 * Channel 1 Power Control = 1 (On) ** $1PC1 ** Response: ** 1 * Channel 1 Power Read ** $1PR ** Response: ** 1 * Read Block ** $1RB read temperature sensor block (4 channels) ** $5RB read pH sensor block (Seabird 18s) ** Response: ** \*+02712.00 ** \*+00200.00 ** \*+00125.76 ** \*+00347.95 * Read Data ** $1RD read tDGH channel 1 (temperature ch 1) ** $2RD read tDGH channel 2 (temperature ch 2) ** $3RD read tDGH channel 3 (temperature ch 3) ** $4RD read tDGH channel 4 (temperature ch 4) ** $5RD read tDGH channel 5 (pH sensor ch 1) ** $6RD read tDGH channel 6 (pH sensor ch 2) ** $7RD read tDGH channel 7 (pH sensor ch 3) ** $8RD read tDGH channel 8 (pH sensor ch 4) ** $9RD read tDGH channel 9 (pH sensor ch 5) \\ \\ \\ \\ \\ \- \\ \- \\ \- \\ \- \\ \- \\ \- \\ \- \\ \- *   *   *   *   *   *   *   *   *   *   *   *   *   *   *   *   *   *   *   *   *   *   *   *   *   *   *   *   *   *   *   *   *   *   *   *   *   *   *   *   ---- \\ \\ \\ \\ \\ \\ \\ \\ \\ DGH Can upgrade project was prioritized up by the Engineering Director in Sep. 2013 in order to remove the project from the 2014 project list and make good on an unrealized project from 2012.  The original scope of work was to fit MBARI HRpH instruments to the DGH can.   RS485 feature of MBARI HRpH was planned.   In 2013, the requirement was added to use the new Seabird 18s digital pH instrument since this instrument was the result of a tech transfer by Thom Maughan to Seabird of the MBARI HRpH instrument and the Seabird 18s is now available as of 4Q2013 (though it is not advertised yet on the Seabird website).   The Seabird 18s does not have an RS485 interface option which motivated a different engineering approach (use of custom microprocessor to aggregate the RS232 instruments and present as a single DGH module to keep the PC software simple). h2. DGH Can Upgrade (tDGH) Requirements: * requirements defined, then reviewed with Ed Peltzer and Dale Graves Sep 2013 h3. Hardware h4. Sensor Interface * 4 channel analog for platinum sensor resistors (RTDs from Omega, same as existing DGH can) * 4 channel digital for RS232 Seabird 18s sensors (4 pin, 12v, RS232). Ability to electrically isolate in case of pH instrument failure. h4. ROV Interface * RS232 * Single power supply \+24v, GND (+24v is more readily available on ROV per DG) h3. Mechanical * The existing DGH housing is corroded, a new housing is desired with 4 connectors for temperature and 4 connectors for pH and 1 connector for ROV h3. Software h4. DGH Can * Must support maximum 1 Hz sample rate (once per second); logging at 1 Hz as well. Typically logging is at 0.5 Hz. Would like 0.2, 0.1 Hz options as well. h4. PC * Installer or standalone executable, must not 'clobber' shared dll's used by another program.  ** virtual machine will be created of Ed's laptop to 'test' the lab view installer.   We will do this early to gate the approach on software. * Same functional and graphical features as existing software.  GUI similar to what we now have in layout with graphical display of pH and "sliders" (horizontal bar graphs) for temperature. GUI should also allow for: ** a. Selection of any temp sensor to go with any pH sensor. ** b. Separate calibration constants (slope & offset) for each pH sensor. ** c. Separate temperature offsets for each temp sensor. h3. Time and Division of Labor: * Ed is the customer and supplies the requirements.   Ed's laptop will need to have a virtual machine constructed to prevent the newer LabView Dll's from affecting an older program.   From time to time Ed will need to log into this virtual machine so that Thom/Dale can test. * Several attempts at making a VM wire tried, Ed's directory replication setup causes VMWare failure * Thom to provide Dale the software def for serial comms so he can work on the Labview GUI ahead of hardware availabilty (Complete) * Thom will be responsible for the project and perform the electronics design and write software/firmware for microprocessor. ** Thom will define serial communications protocol. (In Progress, working over Thxgiving) * Jose will do the PCB layout (Complete) * Indtec will do the assembly (some parts are BGA) * Dale will do the PC Software / GUI (Labview to be used) * Dale will update the instrument housing and spec out the external connectors h3. tDGH controller bringup / hardware design verification * Partial stuff, MSP430F5438A + MAX3222 + MUX + Power Converter + LEDs ** isolating converter consumes \~87mA with 10mA load on 3.3v ** JTAG connection, 14pin connector orients to edge of board, works well ** LEDs work ** UART connection to MAX3222 works ** GPIO connections to INST PWR Enable works * Full stuff controller board received from Indtec on Dec. 4, Tom Marion built up interface board on Dec. 4 ** Had Jose cut/jmp to fix MAX3222, Mux lines, pull ups on Mux Dec 5. **   * PCB Issues ** MUX lines not connected to processor, fixed with blue wires, fixed in rev2. FIXED v2 28 Dec 2013 ** no TX output on MAX3222, C1/C2 cross wired, Fixed with circuit mod. FIXED v2 ** Should have pullups not pull downs on serial lines for MUX - FIXED v2 ** Isolating RS232 not working FIXED v2 * Firmware ** Clock subsystem, 16.777 MHz operation for SMCLK, MCLK, ACLK, Tektronix TDS2024B measures 16.89 MHz (100ns grid). 0.7% error. *** 115200 measures a bit over 8.67 usec per bit time, closer to 8.8 usec. Normally high signal. ** LEDs ** UART0 to 3 sending data, confirmed 115200 ** INST1 PWR Enable tested and working * ToDo ** UART to Instrument connection (fix MAX3222). C1/C2 caps wired incorrectly (fixed in rev 2) DONE ** UART to ROV isolated connection, need to figure out why it's not working. DONE ** Finish hardware bringup and spin rev2 of the controller board. DONE ** UART ISR *** Test serial mux, latency, glitch, etc DONE ** Write test program for exercising relays on interface board DONE ** Write DGH module interface for temperature readings DONE ** Write Seabird 18s interface and driver DONE ** Wire up the DGH housing connectors and mount the board set and DGH module ** Integration test with 5 pH and max sample rate (1Hz) in test tank h3. Seabird 18s setup * setoutputformat= 0 ** 0 \*±vvvvv.vv\r\n pH probe voltage in mV, MBARI style output ** 1 ±vvvv.vv\r\n pH probe voltage in mV ** 2 v.vvvv\r\n pH probe voltage in SBE 18 volts * cal for fast response (request, response immediate, othewise a couple seconds) * setautorun=0 no autorun ** enter interactive mode on powerup, 1 enters tsc on powerup. If tsc is stopped via ESC the instrument re-enters tsc on power cycle. * setexecuted=0 suppress tags ** 1 do not suppress * setecho=0 suppress echoed characters ** 1 do not suppress * setprompt=0 suppress 'S>' ** 1 do not suppress * setbaud=115200 ** 9600, 38400, 115200 * setsampleperiod=1 ** n seconds between scans when running continuously. Each sample is comprised of an average of 8 scans. * Operational commands ** ts returns a measurement in one of the above formats. ** tsc continuously samples and returns the measurement in one of the above formats. The update rate is 1Hz which is an average of 16 samples. Return to interactive mode via the ESC key. ** gethd ** getcd ** getec ** getsd ** getcc * Electrical ** Voltage input 11VDC - 18VDC ** Current consumption 82mA at 12VDC h3. DGH D5451 Module setup * Setup the D5451 to 115200 baud, procedure: ** Wire the default pin on the D5451 to Ground, set terminal to 300 baud (8N1) with serial port connected and 12v supplied (47mA) ** $1WE (echo \*) ** $1SU3108E1C2 (echo \*) ** change terminal settings to 115200, then disconnect the Default pin from ground (leave floating) ** $1RS should return \*3108E1C2 ** $1RD will take a sample, returns \*-99999.99 with input floating (no thermistor) h3. Serial Protocol * Power All (0=off, 1=on) ** $1PA0 ** response ** 0 * Channel 1 Power Control = 0 (Off) ** $1PC0 ** Response: ** 0 * Channel 1 Power Control = 1 (On) ** $1PC1 ** Response: ** 1 * Channel 1 Power Read ** $1PR ** Response: ** 1 * Read Block ** $1RB read temperature sensor block (4 channels) ** $5RB read pH sensor block (Seabird 18s) ** Response: ** \*+02712.00 ** \*+00200.00 ** \*+00125.76 ** \*+00347.95 * Read Data ** $1RD read tDGH channel 1 (temperature ch 1) ** $2RD read tDGH channel 2 (temperature ch 2) ** $3RD read tDGH channel 3 (temperature ch 3) ** $4RD read tDGH channel 4 (temperature ch 4) ** $5RD read tDGH channel 5 (pH sensor ch 1) ** $6RD read tDGH channel 6 (pH sensor ch 2) ** $7RD read tDGH channel 7 (pH sensor ch 3) ** $8RD read tDGH channel 8 (pH sensor ch 4) ** $9RD read tDGH channel 9 (pH sensor ch 5)]]> 27066967 27099730 ** response ** 0 * Channel 1 Power Control = 0 (Off) ** $1PC0 ** Response: ** 0 * Channel 1 Power Control = 1 (On) ** $1PC1 ** Response: ** 1 * Channel 1 Power Read ** $1PR ** Response: ** 1 * Read Block ** $1RB read temperature sensor block (4 channels) ** $5RB read pH sensor block (Seabird 18s) ** Response: ** \*+02712.00 ** \*+00200.00 ** \*+00125.76 ** \*+00347.95 * Read Data ** $1RD read tDGH channel 1 (temperature ch 1) ** $2RD read tDGH channel 2 (temperature ch 2) ** $3RD read tDGH channel 3 (temperature ch 3) ** $4RD read tDGH channel 4 (temperature ch 4) ** $5RD read tDGH channel 5 (pH sensor ch 1) ** $6RD read tDGH channel 6 (pH sensor ch 2) ** $7RD read tDGH channel 7 (pH sensor ch 3) ** $8RD read tDGH channel 8 (pH sensor ch 4) ** $9RD read tDGH channel 9 (pH sensor ch 5) \\ \\ \\ \\ \\ \- \\ \- \\ \- \\ \- \\ \- \\ \- \\ \- \\ \- *   *   *   *   *   *   *   *   *   *   *   *   *   *   *   *   *   *   *   *   *   *   *   *   *   *   *   *   *   *   *   *   *   *   *   *   *   *   *   *   ---- \\ \\ \\ \\ \\ \\ \\ \\ \\ DGH Can upgrade project was prioritized up by the Engineering Director in Sep. 2013 in order to remove the project from the 2014 project list and make good on an unrealized project from 2012.  The original scope of work was to fit MBARI HRpH instruments to the DGH can.   RS485 feature of MBARI HRpH was planned.   In 2013, the requirement was added to use the new Seabird 18s digital pH instrument since this instrument was the result of a tech transfer by Thom Maughan to Seabird of the MBARI HRpH instrument and the Seabird 18s is now available as of 4Q2013 (though it is not advertised yet on the Seabird website).   The Seabird 18s does not have an RS485 interface option which motivated a different engineering approach (use of custom microprocessor to aggregate the RS232 instruments and present as a single DGH module to keep the PC software simple). h2. DGH Can Upgrade (tDGH) Requirements: * requirements defined, then reviewed with Ed Peltzer and Dale Graves Sep 2013 h3. Hardware h4. Sensor Interface * 4 channel analog for platinum sensor resistors (RTDs from Omega, same as existing DGH can) * 4 channel digital for RS232 Seabird 18s sensors (4 pin, 12v, RS232). Ability to electrically isolate in case of pH instrument failure. h4. ROV Interface * RS232 * Single power supply \+24v, GND (+24v is more readily available on ROV per DG) h3. Mechanical * The existing DGH housing is corroded, a new housing is desired with 4 connectors for temperature and 4 connectors for pH and 1 connector for ROV h3. Software h4. DGH Can * Must support maximum 1 Hz sample rate (once per second); logging at 1 Hz as well. Typically logging is at 0.5 Hz. Would like 0.2, 0.1 Hz options as well. h4. PC * Installer or standalone executable, must not 'clobber' shared dll's used by another program.  ** virtual machine will be created of Ed's laptop to 'test' the lab view installer.   We will do this early to gate the approach on software. * Same functional and graphical features as existing software.  GUI similar to what we now have in layout with graphical display of pH and "sliders" (horizontal bar graphs) for temperature. GUI should also allow for: ** a. Selection of any temp sensor to go with any pH sensor. ** b. Separate calibration constants (slope & offset) for each pH sensor. ** c. Separate temperature offsets for each temp sensor. h3. Time and Division of Labor: * Ed is the customer and supplies the requirements.   Ed's laptop will need to have a virtual machine constructed to prevent the newer LabView Dll's from affecting an older program.   From time to time Ed will need to log into this virtual machine so that Thom/Dale can test. * Several attempts at making a VM wire tried, Ed's directory replication setup causes VMWare failure * Thom to provide Dale the software def for serial comms so he can work on the Labview GUI ahead of hardware availabilty (Complete) * Thom will be responsible for the project and perform the electronics design and write software/firmware for microprocessor. ** Thom will define serial communications protocol. (In Progress, working over Thxgiving) * Jose will do the PCB layout (Complete) * Indtec will do the assembly (some parts are BGA) * Dale will do the PC Software / GUI (Labview to be used) * Dale will update the instrument housing and spec out the external connectors h3. tDGH controller bringup / hardware design verification * Partial stuff, MSP430F5438A + MAX3222 + MUX + Power Converter + LEDs ** isolating converter consumes \~87mA with 10mA load on 3.3v ** JTAG connection, 14pin connector orients to edge of board, works well ** LEDs work ** UART connection to MAX3222 works ** GPIO connections to INST PWR Enable works * Full stuff controller board received from Indtec on Dec. 4, Tom Marion built up interface board on Dec. 4 ** Had Jose cut/jmp to fix MAX3222, Mux lines, pull ups on Mux Dec 5. **   * PCB Issues ** MUX lines not connected to processor, fixed with blue wires, fixed in rev2. FIXED v2 28 Dec 2013 ** no TX output on MAX3222, C1/C2 cross wired, Fixed with circuit mod. FIXED v2 ** Should have pullups not pull downs on serial lines for MUX - FIXED v2 ** Isolating RS232 not working FIXED v2 * Firmware ** Clock subsystem, 16.777 MHz operation for SMCLK, MCLK, ACLK, Tektronix TDS2024B measures 16.89 MHz (100ns grid). 0.7% error. *** 115200 measures a bit over 8.67 usec per bit time, closer to 8.8 usec. Normally high signal. ** LEDs ** UART0 to 3 sending data, confirmed 115200 ** INST1 PWR Enable tested and working * ToDo ** UART to Instrument connection (fix MAX3222). C1/C2 caps wired incorrectly (fixed in rev 2) DONE ** UART to ROV isolated connection, need to figure out why it's not working. DONE ** Finish hardware bringup and spin rev2 of the controller board. DONE ** UART ISR *** Test serial mux, latency, glitch, etc DONE ** Write test program for exercising relays on interface board DONE ** Write DGH module interface for temperature readings DONE ** Write Seabird 18s interface and driver DONE ** Wire up the DGH housing connectors and mount the board set and DGH module ** Integration test with 5 pH and max sample rate (1Hz) in test tank h3. Seabird 18s setup * setoutputformat= 0 ** 0 \*±vvvvv.vv\r\n pH probe voltage in mV, MBARI style output ** 1 ±vvvv.vv\r\n pH probe voltage in mV ** 2 v.vvvv\r\n pH probe voltage in SBE 18 volts * cal for fast response (request, response immediate, othewise a couple seconds) * setautorun=0 no autorun ** enter interactive mode on powerup, 1 enters tsc on powerup. If tsc is stopped via ESC the instrument re-enters tsc on power cycle. * setexecuted=0 suppress tags ** 1 do not suppress * setecho=0 suppress echoed characters ** 1 do not suppress * setprompt=0 suppress 'S>' ** 1 do not suppress * setbaud=115200 ** 9600, 38400, 115200 * setsampleperiod=1 ** n seconds between scans when running continuously. Each sample is comprised of an average of 8 scans. * Operational commands ** ts returns a measurement in one of the above formats. ** tsc continuously samples and returns the measurement in one of the above formats. The update rate is 1Hz which is an average of 16 samples. Return to interactive mode via the ESC key. ** gethd ** getcd ** getec ** getsd ** getcc * Electrical ** Voltage input 11VDC - 18VDC ** Current consumption 82mA at 12VDC h3. DGH D5451 Module setup * Setup the D5451 to 115200 baud, procedure: ** Wire the default pin on the D5451 to Ground, set terminal to 300 baud (8N1) with serial port connected and 12v supplied (47mA) ** $1WE (echo \*) ** $1SU3108E1C2 (echo \*) ** change terminal settings to 115200, then disconnect the Default pin from ground (leave floating) ** $1RS should return \*3108E1C2 ** $1RD will take a sample, returns \*-99999.99 with input floating (no thermistor) h3. Serial Protocol * Power All (0=off, 1=on) ** $1PA0 ** response ** 0 * Channel 1 Power Control = 0 (Off) ** $1PC0 ** Response: ** 0 * Channel 1 Power Control = 1 (On) ** $1PC1 ** Response: ** 1 * Channel 1 Power Read ** $1PR ** Response: ** 1 * Read Block ** $1RB read temperature sensor block (4 channels) ** $5RB read pH sensor block (Seabird 18s) ** Response: ** \*+02712.00 ** \*+00200.00 ** \*+00125.76 ** \*+00347.95 * Read Data ** $1RD read tDGH channel 1 (temperature ch 1) ** $2RD read tDGH channel 2 (temperature ch 2) ** $3RD read tDGH channel 3 (temperature ch 3) ** $4RD read tDGH channel 4 (temperature ch 4) ** $5RD read tDGH channel 5 (pH sensor ch 1) ** $6RD read tDGH channel 6 (pH sensor ch 2) ** $7RD read tDGH channel 7 (pH sensor ch 3) ** $8RD read tDGH channel 8 (pH sensor ch 4) ** $9RD read tDGH channel 9 (pH sensor ch 5)]]> 27066968 27590937 4.4: [https://confluence.atlassian.com/display/JIRA044/Migrating+JIRA+to+Another+Server] ## The JIRA configuration tool: [https://confluence.atlassian.com/display/JIRA044/Using+the+JIRA+Configuration+Tool] h5. Steps # (/) Create new VM named bugs.mbari.org in the DMZ # (/) Have Neil create database Jira_Temp on solstice2.shore.mbari.org # (/) Have Neil create database Jira on solstice2.shore.mbari.org # (/) Have Pat install Java 7 on bugs.shore.mbari.org # (/) Have Pete plumb holes through firewall so processes on bugs.mbari.org can get to Solstice2 # (/) Have Pat create DB_Collaboration account on bugs so it can run JIRA under that account and it can connect to solstice2 using that NT Domain account. # (/) Upgrade license on Atlassian site # (/) Log into bugs.shore.mbari.org # (/) Download 3.13.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 4.4.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 5.2.11 standalone Linux 64 bit tar.gz (not sure this version is necessary, but at least I have it) # (/) Unzip and untar the file to /opt # (/) Download latest JIRA (6.4.7 as of this writing). # (/) Unzip and untar it to /opt # Performed Test Upgrade ## (/) In order to export the current stuff in JIRA, I had to shut off access so people could not change the data while I was backing it up. ## (/) I ssh'd to oceana.mbari.org as root and edited the /opt/jira/conf/server.xml file and commented out the Connector section that had the port of 8010 to shut it off from the normal serving route. ## (/) I uncommented the 8082 port connector and the 8443 port connector so that I could still get to the server. ## (/) I stopped and started the JIRA server and in the log file I got a "keystore was tampered with..." which is not surprising. ## (/) I could then browser over to http://oceana.mbari.org:8082/jira ## (/) Then through the Administration console, I did an XML backup ## (/) I then created a tar of all the attachments in the /data/jira_3_12/attachments directory ## (/) I moved both the XML and tar files to the /root/jira-upgrade directory ## (/) I then reversed the changes to the server.xml file and shut down JIRA ## (/) I left it down during the next steps in case it went so well, I could just point people to the new server (yeah, right). ## (/) I then browsed to the crowd server on oceana and add a new application using: ### URL: http://bugs.mbari.org/jira3135 ### IP: 134.89.2.29 ### Name: JIRA3135 ### Password: (ask Kevin) :) ## (/) On bugs, I made a copy of the JIRA 3.13.5 download in the /opt directory and unzipped and untarred it. ## (/) In order to configure the crowd connection I did the following: ### (/) I scp'd the /opt/crowd/client/crowd-integration-client-1.6.jar file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I removed the existing 1.6.1 crowd client jar from the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I scp'd the /opt/crowd/client/conf/crowd.properties file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I scp'd the /opt/crowd/client/conf/crowd-ehcache.xml file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I edited the crowd.properties file on bugs to look like: {noformat} application.name JIRA3135 application.password (ask Kevin) application.login.url http://oceana.mbari.org:8095/crowd/console/ crowd.server.url http://oceana.mbari.org:8095/crowd/services/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 0 session.lastvalidation session.lastvalidation {noformat} ### (/) I edited the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/osuser.xml file to comment out the current authentication mechanism and then uncomment the crowd one. ## (/) I then edited the /opt/atlassian-jira-standalone-3.13.5/conf/server/xml file and configured the database connection to the Jira_Temp database on Solstice2. I looked like this: {noformat} {noformat} ## (/) Edit the /opt/atlassian/jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/entityengine.xml and changed it from 'hsql' to 'mssql' and delete the line with "PUBLIC" in it per the instructions in the comments in that file. ## (/) I edited the /etc/httpd/conf/httpd.conf file and created a proxy pass at the bottom of the file to point a normal URL to the default port 8080 for JIRA: {noformat} # Proxy Pass for JIRA ProxyPass http://bugs.mbari.org:8080 ProxyPassReverse http://bugs.mbari.org:8080 {noformat} ## (/) I restarted Apache ## (/) I scp'd the jtds driver from oceana to the /opt/atlassian-jira-standalone-3.13.5/common/lib directory (you could down from the internet) ## (/) I then went to the /opt/atlassian-jira-standalone-3.13.5/ directory and ran './bin/startup.sh'. From the log file, I could tell things were hanging. After some troubleshooting I am wondering if the local firewall is preventing the application to get access to the database on solstice2. I can telnet to port 1433, but I can't browse to the base http://bugs.mbari.org from anywhere but the local web browser. I have submitted a ticket. ## (/) I restarted the old JIRA with my hopes dashed :(. ## (/) Pat disabled the firewall on bugs.mbari.org but it still hung trying to connect to solstice2.shore.mbari.org. That is really, really perplexing. Neil mentioned that solstice2 is using Kerberos and solstice is not. Checking with the JTDS docs, version 1.3.1 of the driver added kerberos support, so I downloaded that driver and added the 'userKerberos=true' property to the URL in the server.xml file and restarted. Got an error about no credentials, so added user and password properties to the URL. Nope, no luck. Never did figure this one out, but I had Pat pull the VM inside the firewall and after some thrash it worked. Well, it sort of worked ... sigh. It turns out I had downloaded the standard version instead of the enterprise version. I need to redo this work ... grrr. ## (/) I deleted all the tables in the Jira_Temp database and removed the /data/jira3135/indexes directory (and recreated). ## (/) I downloaded the enterprise version of the 3.13.5 server. I made a copy in the /opt directory and unzipped and untarred the file. ## (/) I went back to crowd and edited the application to change the properties to: ### URL: http://bugs.shore.mbari.org:8080 ### IP: 134.89.12.31 ### Name: jira3135 ### Password: (ask Kevin) :) ## (/) I then repeated the steps above to get the server up and running with the following differences: ### The server name is now bugs.shore.mbari.org ### The paths given above are a little different in that they no longer say "standard" but say "enterprise" ### I deleted the proxy pass as it seemed to have issues before and this is only temporary anyway. ## (/) I then browsed to http://bugs.shore.mbari.org:8080 ## (/) It took me to the start up page and at the top was the option to 'import your existing data'. Seemed too good not to try. I clicked on the link. It asked me for the backup file location and the location where the indexes would be stored. ## (/) I copied the XML zip file and the attachments tar file to the /data/original directory. ## (/) I created the /data/jira3135/indexes and used those directories ... it fired off the import and I waited. ## (/) I tailed the log file to watch the import. Holy crap, it worked!!! I could log in and everything! I copied the results from the log file here for posterity sake: {noformat} 2015-07-22 20:55:45,156 http-8080-Processor22 INFO [jira.action.admin.DataImport] Running data import 2015-07-22 20:55:45,179 http-8080-Processor22 INFO [jira.action.admin.DataImport] Importing data.. 2015-07-22 20:55:45,186 http-8080-Processor22 INFO [jira.action.admin.DataImport] Start parsing XML with SAX Parser 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] XML successfully parsed 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] Removing all entries from the database. 2015-07-22 20:56:24,593 http-8080-Processor22 INFO [jira.action.admin.DataImport] All entries removed. 2015-07-22 20:56:24,594 http-8080-Processor22 INFO [jira.action.admin.DataImport] Started storing 410414 Generic Values 2015-07-22 21:01:51,967 http-8080-Processor22 INFO [jira.action.admin.DataImport] Finished storing Generic Values 2015-07-22 21:01:52,329 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:52,361 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:54,683 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLink' to module 'jira.user.format:profile-link-user-format'. 2015-07-22 21:01:54,724 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullName' to module 'jira.user.format:full-name-user-format'. 2015-07-22 21:01:54,773 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkSearcher' to module 'jira.user.format:profile-link-searcher-user-format'. 2015-07-22 21:01:54,784 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkExternal' to module 'jira.user.format:profile-link-external-user-format'. 2015-07-22 21:01:54,795 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkActionHeader' to module 'jira.user.format:profile-link-action-header-user-format'. 2015-07-22 21:01:54,807 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullProfile' to module 'jira.user.format:full-profile-user-format'. 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/comments 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/issues 2015-07-22 21:01:55,641 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/plugins 2015-07-22 21:01:55,867 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:01:55,871 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/issues does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:55,873 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/comments does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,033 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,257 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,889 http-8080-Processor22 ERROR [atlassian.jira.upgrade.ConsistencyCheckImpl] Attachments are turned on, but attachment path [/data/jira_3_12/attachments] invalid - disabling attachments 2015-07-22 21:02:13,904 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Detected that an upgrade is needed; existing data at build 299 2015-07-22 21:02:13,907 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Doing Upgrade... 2015-07-22 21:02:13,915 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value' succeeded 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 317 2015-07-22 21:02:13,944 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite filters - make each filter a favourite of its owner. 2015-07-22 21:02:17,822 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build319] Could not find author 'fpy' for filter with id '10040' 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite filters - make each filter a favourite of its owner.' succeeded 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 319 2015-07-22 21:02:17,995 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise Share Permissions. Move old shares to new shares. 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise Share Permissions. Move old shares to new shares.' succeeded 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 321 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Migrating the old JIRA UI colors to the new JIRA 3.13 colors 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build322] Custom color detected for jira.lf.menu.bgcolour : #336699 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Migrating the old JIRA UI colors to the new JIRA 3.13 colors' succeeded 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 322 2015-07-22 21:02:18,025 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite dashboards - make each dashboard a favourite of its owner. 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'cmcgann' for dashboard with id '10030' 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'fpy' for dashboard with id '10060' 2015-07-22 21:02:18,423 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'kanna' for dashboard with id '10040' 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite dashboards - make each dashboard a favourite of its owner.' succeeded 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 325 2015-07-22 21:02:18,625 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Reindexing all data in JIRA to include Favourites. 2015-07-22 21:02:18,648 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All starting... 2015-07-22 21:02:18,650 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 0% complete. Current index: Issue 2015-07-22 21:02:18,654 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:02:18,809 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 1% complete. Current index: Issue 2015-07-22 21:02:18,855 indexerPool-2-thread-10 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 2% complete. Current index: Issue 2015-07-22 21:02:18,899 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 3% complete. Current index: Issue 2015-07-22 21:02:18,945 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 4% complete. Current index: Issue 2015-07-22 21:02:19,012 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 5% complete. Current index: Issue . . . 2015-07-22 21:02:26,164 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 95% complete. Current index: Issue 2015-07-22 21:02:26,232 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 96% complete. Current index: Issue 2015-07-22 21:02:26,316 indexerPool-2-thread-9 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 97% complete. Current index: Issue 2015-07-22 21:02:26,771 indexerPool-2-thread-3 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: Issue 2015-07-22 21:02:27,261 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 8607ms. Indexer: DefaultIndexManager: paths: [/data/jira3135/indexes/issues, /data/jira3135/indexes/comments] 2015-07-22 21:02:27,263 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: SearchRequest 2015-07-22 21:02:27,268 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,293 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: SearchRequest 2015-07-22 21:02:27,308 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: PortalPage 2015-07-22 21:02:27,312 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,377 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: PortalPage 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 115ms. Indexer: SharedEntityIndexManager: paths: [/data/jira3135/indexes/entities/portalpage, /data/jira3135/indexes/entities/searchrequest] 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All complete. Total time: 8722ms. 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Reindexing all data in JIRA to include Favourites.' succeeded 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 326 2015-07-22 21:02:27,397 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade succeeded! Setting data build number to 360 2015-07-22 21:02:27,469 JiraQuartzScheduler_Worker-0 WARN [service.services.export.ExportService] Backup directory /data/jira_3_12/backup does not exist {noformat} {warning:title=Paths} It appears that the upgraded JIRA will still look for the attachments and the backup locations in the original places. So I created /data/jira_3_12/backup and untarred the original attachments to /data/jira_3_12 and then everything worked (including attachements) in the new JIRA. {warning} ## (/) I then used the upgraded JIRA to generate a new XML backup and stored it in /data/original/3.13.5 along with another tar of the files in /data/jira_3_12/attachments. ## (/) I then shutdown the JIRA server. *I should be ready to move on to version 4 upgrade WHEW* ## So, before moving on, I decided that it would be a really good idea to spin up a new Crowd instance to get rid of the :8443 in the URL and to move off of RedHat per IS requests. I have a ticket in for a new VM and a new database to try to get this going. I am waiting on that before moving on. ## (/) Pat created the VM and Neil created the database. ## (/) I logged into auth.mbari.org (name of the VM) and downloaded crowd which I unzipped to the /opt directory ## (/) I then created a /data/crowd directory and gave my account permissions on it and then edited the /opt/atlassian..../crowd-webapp/WEB-INF/classes/crowd-init.properties file to set that as the crowd home directory. ## (/) The instructions say to download the JDBC driver, but they already have JTDS 1.2.7 in the download so I did not do anything. ## (/) You have to manually connect up CrowdID to a database as they setup wizard does not currently do this. ### (/) They say to download the driver, but again 1.2.7 was there so I did nothing. ### (/) I edited the /opt/atlassian.../apache-tomcat/conf/Catalina/localhost/openidserver.xml to look like: {noformat} {noformat} ### (/) I edited the /opt/atlassian.../build.properties files to look like: {noformat} # Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See https://confluence.atlassian.com/display/CROWD/Connecting+Crowd+to+a+Database hibernate.dialect=org.hibernate.dialect.SQLServerDialect # The Hibernate transaction factory to use. See https://confluence.atlassian.com/display/CROWD/Configuring+Crowd hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory # The http port you wish to run crowd from, ie: http://localhost:8095/crowd crowd.tomcat.connector.port=8095 # Tomcat requires a unique port for shutdown crowd.tomcat.shutdown.port=8020 # Crowd context root crowd.url=http://localhost:8095/crowd # Demo context root demo.url=http://localhost:8095/demo # OpenID server context root openidserver.url=http://localhost:8095/openidserver {noformat} ### (/) I then ran the build.sh script in the root of /opt/atlassian... ## (/) I fired up crowd using the /opt/atlassian.../start_crowd.sh script ## (/) I then went to http://auth.mbari.org:8095/crowd to kick off the start up wizard ## (/) I grabbed a new eval license from my account on atlassian and pasted into the license page. ## (/) I selected "New install" on the next page. ## (/) I configured the JDBC connection using this connection URL with user DB_Collaboration {noformat} jdbc:jtds:sqlserver://dione.mbari.org:51001/Crowd;domain=SHORE;useNTLMv2=TRUE {noformat} ## (/) I left the "Options" as they came up {warning:title=Paths} Not sure if this is a problem, but because I started the set up using auth.mbari.org, it set the Base URL to http://auth.mbari.org:8095/crowd instead of localhost. Hope that is not a problem. We will see. {warning} ## (/) I configured the email connection using the settings from [here|https://wind.shore.mbari.org/is/howto/email/mbarimail/imap] and I used my network login (probably shouldn't be doing that ... not sure where it stores my password, but I am assuming in the DB). ## (/) For the local admin account, I created a user named 'crowdadm' so it would not clash with my LDAP account. See Kevin Gomes for password information. ## (/) I checked the OpenID server as an integrated application ## (/) It then took me to the login page and I logged in using the newly minted admin account. Seemed all is well so far. ## (/) I visited the openidserver URL as well and that seemed OK. ## (/) I decided to wait on configuring the MBARI LDAP directory until I got everything with SSL working. ## (/) Now the next step was to follow the directions to configure Crowd to run over SSL found [here|https://confluence.atlassian.com/display/CROWD/Configuring+Crowd+to+Work+with+SSL] ## (/) I shutdown crowd. Note that the stop script does not shutdown things correctly and I noticed the crowd app running as root. That should not be if I started as kgomes. Not sure what is up with that. ## (/) Now Joe had already configured SSL once, so I used his connector configuration in the server.xml file and so the final file looked like: {noformat} {noformat} ## (/) I then edited the /data/crowd/crowd.properties to look like: {noformat} #Sat Aug 01 09:05:15 PDT 2015 session.lastvalidation=session.lastvalidation session.tokenkey=session.tokenkey crowd.server.url=https\://localhost\:8443/crowd/services/ application.name=crowd http.timeout=30000 session.isauthenticated=session.isauthenticated application.login.url=https\://localhost\:8443/crowd/console/ session.validationinterval=0 application.password=Y1Xp3OorCmsOP4eruL1dmH {noformat} One thing to note here is that based on a comment from the SSL configuration page at atlassian (Steve's comment), you are supposed to leave all the host names the same. For example, if the file says localhost, leave it localhost. So this created a bit of a problem based on the fact that I had left the base URL pointing to auth.mbari.org in the wizard steps above. That step wrote auth.mbari.org to the /data/crowd/crowd.properties. All the other files reference localhost, so to be consistent, I changed auth.mbari.org to localhost in the /data/crowd/crowd.properties file. We will see if this works. ## (/) Per the instructions on the atlassian page (referenced above), I also edited the build.properties file and the /client/conf/crowd.properties files before I restarted and used the SSL URLs ## build.properties: {noformat} # Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See https://confluence.atlassian.com/display/CROWD/Connecting+Crowd+to+a+Database hibernate.dialect=org.hibernate.dialect.SQLServerDialect # The Hibernate transaction factory to use. See https://confluence.atlassian.com/display/CROWD/Configuring+Crowd hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory # The http port you wish to run crowd from, ie: http://localhost:8095/crowd crowd.tomcat.connector.port=8095 # Tomcat requires a unique port for shutdown crowd.tomcat.shutdown.port=8020 # Crowd context root crowd.url=https://localhost:8443/crowd # Demo context root demo.url=https://localhost:8443/demo # OpenID server context root openidserver.url=https://localhost:8443/openidserver {noformat} ## crowd.properties (client) {noformat} application.name crowd application.password password application.login.url https://localhost:8443/crowd/console/ crowd.server.url https://localhost:8443/crowd/services/ crowd.base.url https://localhost:8443/crowd/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 2 session.lastvalidation session.lastvalidation {noformat} ## (/) Although not stated, I am assuming you would need to run the build.sh script to push the build.properties changes to their proper places, so I did that. Note that before doing that, I know that it will clobber the server.xml changes I made, so I made a copy of that file and diff'd them after and then rolled the previous changes to the new server.xml file. Actually, amazingly enough, it seems to have done the connector entry correctly so I left it after running the build.sh script. ## (/) Crossed my fingers and then restarted crowd. I tailed the catalina.out file and did not see any stack traces so that is a good sign! ## (/) I visited https://auth.mbari.org:8443/crowd first. It could not find that page, but I suspect that is because I am browsing from the outside, so I tried just https://auth.mbari.org/crowd and got a service unavailable. I am suspecting that this is a combination of firewall and proxy pass and I will send this info to Joe. From what I can see on the crowd side, it seems like the server started cleanly, we just can't get to it. I tried to reach it from a browser on the machine itself too (through VNC) with the same service not available. ## (/) Here are the notes from Joe after he fixed it! Wooohooo! {noformat} Hey Kevin, Thanks for starting clean! I had to make a few adjustments. 1-I modified the server.xml file in /opt/atlassian-crowd-2.8.3/apache-tomcat/conf/server.xml so there are two connectors per the instructions on the Atlassian site. I have backed up this good server.xml file in /etc/temp/ if you want to browse it to see what I did. Of note is that I removed all the jargon referencing the types of ciphers available to simplify things for now. 2-I modified /data/crowd/crowd.properties to have crowd.server.url=https\://localhost\:8443/crowd/services/ application.login.url=https\://localhost\:8443/crowd/console/ But that would cause my login to error with an error saying it was unable to reach the authentication server. I scratched my head for a bit. When I revert the values to just using non-SSL and try to log in, I just get an "invalid login" (I don't know the crowdadm password). So I worked under the assumption that if I can configure SSL to get an "invalid login" when logging in then it would work when provided real credentials. So, I then changed /data/crowd/crowd.proprties to: crowd.server.url=https\://auth.mbari.org\:8443/crowd/services/ application.login.url=https\://auth.mbari.org\:8443/crowd/console/ And now when I try to log in with SSL it says "invalid login". Strange because all the other values I can find only show "localhost" .. in any case... Can you try to log in now? {noformat} ## (/) Next I moved on to configuring the connection to MBARI's LDAP server to enable our logins through Crowd and CrowdID ## (/) I clicked on "Add Directory" in crowd. ## (/) I selected "Connector" then clicked Next ## (/) I put ldap.shore.mbari.org as the name of the server ## (/) I selected "Use memberOf for group memberships" ## (/) I used "OU=AllUsers,DC=shore,DC=mbari,DC=org" for the Base DN ## (/) I used "CN=LDAPbind,OU=Special,OU=AllUsers,DC=shore,DC=mbari,DC=org" for the Username (talk to Pat Allen for password) ## (/) I tested the connection (button click) and it passed. ## (/) I de-selected all the capabilities of the connector as it is a ready only connector and then saved it. It synchronized correctly! ## (/) At first, I could not login using my MBARI credentials, but after going to the "crowd" application in crowd (logged in as the local admin), I had to add the LDAP directory and configure it to "Allow all to authenticate", then I was able to login. After this, the last step was to get this to run as a different user and lock down various directories. I went through the entire directory structure /opt/atlassian... and set up so that root owned all read-only locations and DB_Collaboration (account set up by IS) owned the other stuff. I also gave full ownership to the /data/crowd directory to DB_Collaboration so it could write there. Pat set up a script to start on boot and after a little tweaking, it now starts on boot. {warning:title=CrowdID log file} One thing that came up here was that when the crowdID application ran, it tried to write a log file to the location where the process was launched from (which is /opt/atlassian...). This is a bad thing and I figured out that I could change that location by changing the file /opt/atlassian-crowd-2.8.3/crowd-openidserver-webapp/WEB-INF/classes/log4j.properties and hardcoding the /data/crowd/logs/atlassian-crowd-openid-server.log and then restarted the application. {warning} ## (/) Another note is the when an application tried to use the OpenID application, it would get redirected to localhost. I changed the /opt/atlassian.../crowd-openidserver-webapp/WEB-INF/classes/crowd.properties file to look like: {noformat} #Sat Aug 01 10:03:18 PDT 2015 session.lastvalidation=session.lastvalidation session.tokenkey=session.tokenkey crowd.server.url=http\://localhost\:8095/crowd/services/ application.name=crowd-openid-server #application.login.url.template=http\://localhost\:8095/openidserver?returnToUrl\=${RETURN_TO_URL} application.login.url.template=https\://auth.mbari.org/openidserver?returnToUrl\=${RETURN_TO_URL} session.isauthenticated=session.isauthenticated #application.base.url=http\://localhost\:8095/openidserver application.base.url=https\://auth.mbari.org/openidserver #application.login.url=http\://localhost\:8095/openidserver application.login.url=https\://auth.mbari.org/openidserver session.validationinterval=0 application.password=password {noformat} and that seems to have fixed it. # (/) It is finally time to move on to the version 4 upgrade ... holy crap. I first went to the *new* crowd install (auth.mbari.org) and logged in as the crowdadm. # (/) I clicked on Applications, then on Add Application # (/) I selected JIRA from the Application type drop-down # (/) I entered jira445 as the username. Ask Kevin about the password. # (/) I used http://bugs.shore.mbari.org:8081 as the URL # (/) I used 134.89.12.31 as the IP address. # (/) I selected only the MBARI LDAP directory. # (/) Then I selected "Allow all users to authenticate" # (/) Then I clicked on "Add Application" # (/) I VNC'd into bugs.mbari.org. As it turns out, for Linux, there is an installer program to download. I downloaded the .bin for 64 bit Linux installer and moved it to the jira-upgrade directory. # (/) I chmod'd the file to make it executable and ran it. It gave me a warning about not being root, but I went ahead with it. # (/) It asked for the JIRA home and data directory, which I specified as /opt/jira4 and /data/jira445. # (/) For the ports, I specified 8180 and 8105 (HTTP and control respectively). It then extracted all the files and launched JIRA. It said if finished, so I opened a local browser to http://localhost:8180 which kicked off the start up wizard. # (/) I specified the external database using: ## solstice2.shore.mbari.org (server) ## 1433 (port) ## jira4 (database) ## DB_Collaboration (username) ## (password ask Kevin) ## dbo (schema) # But all this failed as it seems to just want to try and use the SQL server authentication instead of domain. I will have to do it manually. # (/) I stopped the server using the bin/stop-jira.sh script. # (/) I created and edited /data/jira445/dbconfig.xml and made it look like the following: {noformat} ?xml version="1.0" encoding="UTF-8"?> defaultDS default mssql jiraschema jdbc:jtds:sqlserver://solstice2.shore.mbari.org:1433/Jira4;domain=SHORE;useNTLMv2=true net.sourceforge.jtds.jdbc.Driver DB_Collaboration (ask Kevin) 15 {noformat}]]> 27558173 27099727 ** response ** 0 * Channel 1 Power Control = 0 (Off) ** $1PC0 ** Response: ** 0 * Channel 1 Power Control = 1 (On) ** $1PC1 ** Response: ** 1 * Channel 1 Power Read ** $1PR ** Response: ** 1 * Read Block ** $1RB read temperature sensor block (4 channels) ** $5RB read pH sensor block (Seabird 18s) ** Response: ** \*+02712.00 ** \*+00200.00 ** \*+00125.76 ** \*+00347.95 * Read Data ** $1RD read tDGH channel 1 (temperature ch 1) ** $2RD read tDGH channel 2 (temperature ch 2) ** $3RD read tDGH channel 3 (temperature ch 3) ** $4RD read tDGH channel 4 (temperature ch 4) ** $5RD read tDGH channel 5 (pH sensor ch 1) ** $6RD read tDGH channel 6 (pH sensor ch 2) ** $7RD read tDGH channel 7 (pH sensor ch 3) ** $8RD read tDGH channel 8 (pH sensor ch 4) ** $9RD read tDGH channel 9 (pH sensor ch 5)\\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ ---- \\ \\ \\ \\ \\ \\ \\ \\ \\ DGH Can upgrade project was prioritized up by the Engineering Director in Sep. 2013 in order to remove the project from the 2014 project list and make good on an unrealized project from 2012.  The original scope of work was to fit MBARI HRpH instruments to the DGH can.   RS485 feature of MBARI HRpH was planned.   In 2013, the requirement was added to use the new Seabird 18s digital pH instrument since this instrument was the result of a tech transfer by Thom Maughan to Seabird of the MBARI HRpH instrument and the Seabird 18s is now available as of 4Q2013 (though it is not advertised yet on the Seabird website).   The Seabird 18s does not have an RS485 interface option which motivated a different engineering approach (use of custom microprocessor to aggregate the RS232 instruments and present as a single DGH module to keep the PC software simple). h2. DGH Can Upgrade (tDGH) Requirements: * requirements defined, then reviewed with Ed Peltzer and Dale Graves Sep 2013 h3. Hardware h4. Sensor Interface * 4 channel analog for platinum sensor resistors (RTDs from Omega, same as existing DGH can) * 4 channel digital for RS232 Seabird 18s sensors (4 pin, 12v, RS232). Ability to electrically isolate in case of pH instrument failure. h4. ROV Interface * RS232 * Single power supply \+24v, GND (+24v is more readily available on ROV per DG) h3. Mechanical * The existing DGH housing is corroded, a new housing is desired with 4 connectors for temperature and 4 connectors for pH and 1 connector for ROV h3. Software h4. DGH Can * Must support maximum 1 Hz sample rate (once per second); logging at 1 Hz as well. Typically logging is at 0.5 Hz. Would like 0.2, 0.1 Hz options as well. h4. PC * Installer or standalone executable, must not 'clobber' shared dll's used by another program.  ** virtual machine will be created of Ed's laptop to 'test' the lab view installer.   We will do this early to gate the approach on software. * Same functional and graphical features as existing software.  GUI similar to what we now have in layout with graphical display of pH and "sliders" (horizontal bar graphs) for temperature. GUI should also allow for: ** a. Selection of any temp sensor to go with any pH sensor. ** b. Separate calibration constants (slope & offset) for each pH sensor. ** c. Separate temperature offsets for each temp sensor. h3. Time and Division of Labor: * Ed is the customer and supplies the requirements.   Ed's laptop will need to have a virtual machine constructed to prevent the newer LabView Dll's from affecting an older program.   From time to time Ed will need to log into this virtual machine so that Thom/Dale can test. * Several attempts at making a VM wire tried, Ed's directory replication setup causes VMWare failure * Thom to provide Dale the software def for serial comms so he can work on the Labview GUI ahead of hardware availabilty (Complete) * Thom will be responsible for the project and perform the electronics design and write software/firmware for microprocessor. ** Thom will define serial communications protocol. (In Progress, working over Thxgiving) * Jose will do the PCB layout (Complete) * Indtec will do the assembly (some parts are BGA) * Dale will do the PC Software / GUI (Labview to be used) * Dale will update the instrument housing and spec out the external connectors h3. tDGH controller bringup / hardware design verification * Partial stuff, MSP430F5438A + MAX3222 + MUX + Power Converter + LEDs ** isolating converter consumes \~87mA with 10mA load on 3.3v ** JTAG connection, 14pin connector orients to edge of board, works well ** LEDs work ** UART connection to MAX3222 works ** GPIO connections to INST PWR Enable works * Full stuff controller board received from Indtec on Dec. 4, Tom Marion built up interface board on Dec. 4 ** Had Jose cut/jmp to fix MAX3222, Mux lines, pull ups on Mux Dec 5. **   * PCB Issues ** MUX lines not connected to processor, fixed with blue wires, fixed in rev2. FIXED v2 28 Dec 2013 ** no TX output on MAX3222, C1/C2 cross wired, Fixed with circuit mod. FIXED v2 ** Should have pullups not pull downs on serial lines for MUX - FIXED v2 ** Isolating RS232 not working FIXED v2 * Firmware ** Clock subsystem, 16.777 MHz operation for SMCLK, MCLK, ACLK, Tektronix TDS2024B measures 16.89 MHz (100ns grid). 0.7% error. *** 115200 measures a bit over 8.67 usec per bit time, closer to 8.8 usec. Normally high signal. ** LEDs ** UART0 to 3 sending data, confirmed 115200 ** INST1 PWR Enable tested and working * ToDo ** UART to Instrument connection (fix MAX3222). C1/C2 caps wired incorrectly (fixed in rev 2) DONE ** UART to ROV isolated connection, need to figure out why it's not working. DONE ** Finish hardware bringup and spin rev2 of the controller board. DONE ** UART ISR *** Test serial mux, latency, glitch, etc DONE ** Write test program for exercising relays on interface board DONE ** Write DGH module interface for temperature readings DONE ** Write Seabird 18s interface and driver DONE ** Wire up the DGH housing connectors and mount the board set and DGH module ** Integration test with 5 pH and max sample rate (1Hz) in test tank h3. Seabird 18s setup * setoutputformat= 0 ** 0 \*±vvvvv.vv\r\n pH probe voltage in mV, MBARI style output ** 1 ±vvvv.vv\r\n pH probe voltage in mV ** 2 v.vvvv\r\n pH probe voltage in SBE 18 volts * cal for fast response (request, response immediate, othewise a couple seconds) * setautorun=0 no autorun ** enter interactive mode on powerup, 1 enters tsc on powerup. If tsc is stopped via ESC the instrument re-enters tsc on power cycle. * setexecuted=0 suppress tags ** 1 do not suppress * setecho=0 suppress echoed characters ** 1 do not suppress * setprompt=0 suppress 'S>' ** 1 do not suppress * setbaud=115200 ** 9600, 38400, 115200 * setsampleperiod=1 ** n seconds between scans when running continuously. Each sample is comprised of an average of 8 scans. * Operational commands ** ts returns a measurement in one of the above formats. ** tsc continuously samples and returns the measurement in one of the above formats. The update rate is 1Hz which is an average of 16 samples. Return to interactive mode via the ESC key. ** gethd ** getcd ** getec ** getsd ** getcc * Electrical ** Voltage input 11VDC - 18VDC ** Current consumption 82mA at 12VDC h3. DGH D5451 Module setup * Setup the D5451 to 115200 baud, procedure: ** Wire the default pin on the D5451 to Ground, set terminal to 300 baud (8N1) with serial port connected and 12v supplied (47mA) ** $1WE (echo \*) ** $1SU3108E1C2 (echo \*) ** change terminal settings to 115200, then disconnect the Default pin from ground (leave floating) ** $1RS should return \*3108E1C2 ** $1RD will take a sample, returns \*-99999.99 with input floating (no thermistor) h3. Serial Protocol * Power All (0=off, 1=on) ** $1PA0 ** response ** 0 * Channel 1 Power Control = 0 (Off) ** $1PC0 ** Response: ** 0 * Channel 1 Power Control = 1 (On) ** $1PC1 ** Response: ** 1 * Channel 1 Power Read ** $1PR ** Response: ** 1 * Read Block ** $1RB read temperature sensor block (4 channels) ** $5RB read pH sensor block (Seabird 18s) ** Response: ** \*+02712.00 ** \*+00200.00 ** \*+00125.76 ** \*+00347.95 * Read Data ** $1RD read tDGH channel 1 (temperature ch 1) ** $2RD read tDGH channel 2 (temperature ch 2) ** $3RD read tDGH channel 3 (temperature ch 3) ** $4RD read tDGH channel 4 (temperature ch 4) ** $5RD read tDGH channel 5 (pH sensor ch 1) ** $6RD read tDGH channel 6 (pH sensor ch 2) ** $7RD read tDGH channel 7 (pH sensor ch 3) ** $8RD read tDGH channel 8 (pH sensor ch 4) ** $9RD read tDGH channel 9 (pH sensor ch 5)]]> 27066965 27590935 4.4: [https://confluence.atlassian.com/display/JIRA044/Migrating+JIRA+to+Another+Server] ## The JIRA configuration tool: [https://confluence.atlassian.com/display/JIRA044/Using+the+JIRA+Configuration+Tool] h5. Steps # (/) Create new VM named bugs.mbari.org in the DMZ # (/) Have Neil create database Jira_Temp on solstice2.shore.mbari.org # (/) Have Neil create database Jira on solstice2.shore.mbari.org # (/) Have Pat install Java 7 on bugs.shore.mbari.org # (/) Have Pete plumb holes through firewall so processes on bugs.mbari.org can get to Solstice2 # (/) Have Pat create DB_Collaboration account on bugs so it can run JIRA under that account and it can connect to solstice2 using that NT Domain account. # (/) Upgrade license on Atlassian site # (/) Log into bugs.shore.mbari.org # (/) Download 3.13.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 4.4.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 5.2.11 standalone Linux 64 bit tar.gz (not sure this version is necessary, but at least I have it) # (/) Unzip and untar the file to /opt # (/) Download latest JIRA (6.4.7 as of this writing). # (/) Unzip and untar it to /opt # Performed Test Upgrade ## (/) In order to export the current stuff in JIRA, I had to shut off access so people could not change the data while I was backing it up. ## (/) I ssh'd to oceana.mbari.org as root and edited the /opt/jira/conf/server.xml file and commented out the Connector section that had the port of 8010 to shut it off from the normal serving route. ## (/) I uncommented the 8082 port connector and the 8443 port connector so that I could still get to the server. ## (/) I stopped and started the JIRA server and in the log file I got a "keystore was tampered with..." which is not surprising. ## (/) I could then browser over to http://oceana.mbari.org:8082/jira ## (/) Then through the Administration console, I did an XML backup ## (/) I then created a tar of all the attachments in the /data/jira_3_12/attachments directory ## (/) I moved both the XML and tar files to the /root/jira-upgrade directory ## (/) I then reversed the changes to the server.xml file and shut down JIRA ## (/) I left it down during the next steps in case it went so well, I could just point people to the new server (yeah, right). ## (/) I then browsed to the crowd server on oceana and add a new application using: ### URL: http://bugs.mbari.org/jira3135 ### IP: 134.89.2.29 ### Name: JIRA3135 ### Password: (ask Kevin) :) ## (/) On bugs, I made a copy of the JIRA 3.13.5 download in the /opt directory and unzipped and untarred it. ## (/) In order to configure the crowd connection I did the following: ### (/) I scp'd the /opt/crowd/client/crowd-integration-client-1.6.jar file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I removed the existing 1.6.1 crowd client jar from the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I scp'd the /opt/crowd/client/conf/crowd.properties file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I scp'd the /opt/crowd/client/conf/crowd-ehcache.xml file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I edited the crowd.properties file on bugs to look like: {noformat} application.name JIRA3135 application.password (ask Kevin) application.login.url http://oceana.mbari.org:8095/crowd/console/ crowd.server.url http://oceana.mbari.org:8095/crowd/services/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 0 session.lastvalidation session.lastvalidation {noformat} ### (/) I edited the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/osuser.xml file to comment out the current authentication mechanism and then uncomment the crowd one. ## (/) I then edited the /opt/atlassian-jira-standalone-3.13.5/conf/server/xml file and configured the database connection to the Jira_Temp database on Solstice2. I looked like this: {noformat} {noformat} ## (/) Edit the /opt/atlassian/jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/entityengine.xml and changed it from 'hsql' to 'mssql' and delete the line with "PUBLIC" in it per the instructions in the comments in that file. ## (/) I edited the /etc/httpd/conf/httpd.conf file and created a proxy pass at the bottom of the file to point a normal URL to the default port 8080 for JIRA: {noformat} # Proxy Pass for JIRA ProxyPass http://bugs.mbari.org:8080 ProxyPassReverse http://bugs.mbari.org:8080 {noformat} ## (/) I restarted Apache ## (/) I scp'd the jtds driver from oceana to the /opt/atlassian-jira-standalone-3.13.5/common/lib directory (you could down from the internet) ## (/) I then went to the /opt/atlassian-jira-standalone-3.13.5/ directory and ran './bin/startup.sh'. From the log file, I could tell things were hanging. After some troubleshooting I am wondering if the local firewall is preventing the application to get access to the database on solstice2. I can telnet to port 1433, but I can't browse to the base http://bugs.mbari.org from anywhere but the local web browser. I have submitted a ticket. ## (/) I restarted the old JIRA with my hopes dashed :(. ## (/) Pat disabled the firewall on bugs.mbari.org but it still hung trying to connect to solstice2.shore.mbari.org. That is really, really perplexing. Neil mentioned that solstice2 is using Kerberos and solstice is not. Checking with the JTDS docs, version 1.3.1 of the driver added kerberos support, so I downloaded that driver and added the 'userKerberos=true' property to the URL in the server.xml file and restarted. Got an error about no credentials, so added user and password properties to the URL. Nope, no luck. Never did figure this one out, but I had Pat pull the VM inside the firewall and after some thrash it worked. Well, it sort of worked ... sigh. It turns out I had downloaded the standard version instead of the enterprise version. I need to redo this work ... grrr. ## (/) I deleted all the tables in the Jira_Temp database and removed the /data/jira3135/indexes directory (and recreated). ## (/) I downloaded the enterprise version of the 3.13.5 server. I made a copy in the /opt directory and unzipped and untarred the file. ## (/) I went back to crowd and edited the application to change the properties to: ### URL: http://bugs.shore.mbari.org:8080 ### IP: 134.89.12.31 ### Name: jira3135 ### Password: (ask Kevin) :) ## (/) I then repeated the steps above to get the server up and running with the following differences: ### The server name is now bugs.shore.mbari.org ### The paths given above are a little different in that they no longer say "standard" but say "enterprise" ### I deleted the proxy pass as it seemed to have issues before and this is only temporary anyway. ## (/) I then browsed to http://bugs.shore.mbari.org:8080 ## (/) It took me to the start up page and at the top was the option to 'import your existing data'. Seemed too good not to try. I clicked on the link. It asked me for the backup file location and the location where the indexes would be stored. ## (/) I copied the XML zip file and the attachments tar file to the /data/original directory. ## (/) I created the /data/jira3135/indexes and used those directories ... it fired off the import and I waited. ## (/) I tailed the log file to watch the import. Holy crap, it worked!!! I could log in and everything! I copied the results from the log file here for posterity sake: {noformat} 2015-07-22 20:55:45,156 http-8080-Processor22 INFO [jira.action.admin.DataImport] Running data import 2015-07-22 20:55:45,179 http-8080-Processor22 INFO [jira.action.admin.DataImport] Importing data.. 2015-07-22 20:55:45,186 http-8080-Processor22 INFO [jira.action.admin.DataImport] Start parsing XML with SAX Parser 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] XML successfully parsed 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] Removing all entries from the database. 2015-07-22 20:56:24,593 http-8080-Processor22 INFO [jira.action.admin.DataImport] All entries removed. 2015-07-22 20:56:24,594 http-8080-Processor22 INFO [jira.action.admin.DataImport] Started storing 410414 Generic Values 2015-07-22 21:01:51,967 http-8080-Processor22 INFO [jira.action.admin.DataImport] Finished storing Generic Values 2015-07-22 21:01:52,329 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:52,361 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:54,683 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLink' to module 'jira.user.format:profile-link-user-format'. 2015-07-22 21:01:54,724 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullName' to module 'jira.user.format:full-name-user-format'. 2015-07-22 21:01:54,773 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkSearcher' to module 'jira.user.format:profile-link-searcher-user-format'. 2015-07-22 21:01:54,784 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkExternal' to module 'jira.user.format:profile-link-external-user-format'. 2015-07-22 21:01:54,795 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkActionHeader' to module 'jira.user.format:profile-link-action-header-user-format'. 2015-07-22 21:01:54,807 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullProfile' to module 'jira.user.format:full-profile-user-format'. 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/comments 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/issues 2015-07-22 21:01:55,641 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/plugins 2015-07-22 21:01:55,867 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:01:55,871 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/issues does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:55,873 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/comments does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,033 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,257 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,889 http-8080-Processor22 ERROR [atlassian.jira.upgrade.ConsistencyCheckImpl] Attachments are turned on, but attachment path [/data/jira_3_12/attachments] invalid - disabling attachments 2015-07-22 21:02:13,904 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Detected that an upgrade is needed; existing data at build 299 2015-07-22 21:02:13,907 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Doing Upgrade... 2015-07-22 21:02:13,915 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value' succeeded 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 317 2015-07-22 21:02:13,944 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite filters - make each filter a favourite of its owner. 2015-07-22 21:02:17,822 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build319] Could not find author 'fpy' for filter with id '10040' 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite filters - make each filter a favourite of its owner.' succeeded 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 319 2015-07-22 21:02:17,995 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise Share Permissions. Move old shares to new shares. 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise Share Permissions. Move old shares to new shares.' succeeded 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 321 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Migrating the old JIRA UI colors to the new JIRA 3.13 colors 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build322] Custom color detected for jira.lf.menu.bgcolour : #336699 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Migrating the old JIRA UI colors to the new JIRA 3.13 colors' succeeded 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 322 2015-07-22 21:02:18,025 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite dashboards - make each dashboard a favourite of its owner. 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'cmcgann' for dashboard with id '10030' 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'fpy' for dashboard with id '10060' 2015-07-22 21:02:18,423 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'kanna' for dashboard with id '10040' 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite dashboards - make each dashboard a favourite of its owner.' succeeded 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 325 2015-07-22 21:02:18,625 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Reindexing all data in JIRA to include Favourites. 2015-07-22 21:02:18,648 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All starting... 2015-07-22 21:02:18,650 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 0% complete. Current index: Issue 2015-07-22 21:02:18,654 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:02:18,809 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 1% complete. Current index: Issue 2015-07-22 21:02:18,855 indexerPool-2-thread-10 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 2% complete. Current index: Issue 2015-07-22 21:02:18,899 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 3% complete. Current index: Issue 2015-07-22 21:02:18,945 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 4% complete. Current index: Issue 2015-07-22 21:02:19,012 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 5% complete. Current index: Issue . . . 2015-07-22 21:02:26,164 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 95% complete. Current index: Issue 2015-07-22 21:02:26,232 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 96% complete. Current index: Issue 2015-07-22 21:02:26,316 indexerPool-2-thread-9 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 97% complete. Current index: Issue 2015-07-22 21:02:26,771 indexerPool-2-thread-3 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: Issue 2015-07-22 21:02:27,261 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 8607ms. Indexer: DefaultIndexManager: paths: [/data/jira3135/indexes/issues, /data/jira3135/indexes/comments] 2015-07-22 21:02:27,263 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: SearchRequest 2015-07-22 21:02:27,268 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,293 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: SearchRequest 2015-07-22 21:02:27,308 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: PortalPage 2015-07-22 21:02:27,312 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,377 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: PortalPage 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 115ms. Indexer: SharedEntityIndexManager: paths: [/data/jira3135/indexes/entities/portalpage, /data/jira3135/indexes/entities/searchrequest] 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All complete. Total time: 8722ms. 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Reindexing all data in JIRA to include Favourites.' succeeded 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 326 2015-07-22 21:02:27,397 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade succeeded! Setting data build number to 360 2015-07-22 21:02:27,469 JiraQuartzScheduler_Worker-0 WARN [service.services.export.ExportService] Backup directory /data/jira_3_12/backup does not exist {noformat} {warning:title=Paths} It appears that the upgraded JIRA will still look for the attachments and the backup locations in the original places. So I created /data/jira_3_12/backup and untarred the original attachments to /data/jira_3_12 and then everything worked (including attachements) in the new JIRA. {warning} ## (/) I then used the upgraded JIRA to generate a new XML backup and stored it in /data/original/3.13.5 along with another tar of the files in /data/jira_3_12/attachments. ## (/) I then shutdown the JIRA server. *I should be ready to move on to version 4 upgrade WHEW* ## So, before moving on, I decided that it would be a really good idea to spin up a new Crowd instance to get rid of the :8443 in the URL and to move off of RedHat per IS requests. I have a ticket in for a new VM and a new database to try to get this going. I am waiting on that before moving on. ## (/) Pat created the VM and Neil created the database. ## (/) I logged into auth.mbari.org (name of the VM) and downloaded crowd which I unzipped to the /opt directory ## (/) I then created a /data/crowd directory and gave my account permissions on it and then edited the /opt/atlassian..../crowd-webapp/WEB-INF/classes/crowd-init.properties file to set that as the crowd home directory. ## (/) The instructions say to download the JDBC driver, but they already have JTDS 1.2.7 in the download so I did not do anything. ## (/) You have to manually connect up CrowdID to a database as they setup wizard does not currently do this. ### (/) They say to download the driver, but again 1.2.7 was there so I did nothing. ### (/) I edited the /opt/atlassian.../apache-tomcat/conf/Catalina/localhost/openidserver.xml to look like: {noformat} {noformat} ### (/) I edited the /opt/atlassian.../build.properties files to look like: {noformat} # Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See https://confluence.atlassian.com/display/CROWD/Connecting+Crowd+to+a+Database hibernate.dialect=org.hibernate.dialect.SQLServerDialect # The Hibernate transaction factory to use. See https://confluence.atlassian.com/display/CROWD/Configuring+Crowd hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory # The http port you wish to run crowd from, ie: http://localhost:8095/crowd crowd.tomcat.connector.port=8095 # Tomcat requires a unique port for shutdown crowd.tomcat.shutdown.port=8020 # Crowd context root crowd.url=http://localhost:8095/crowd # Demo context root demo.url=http://localhost:8095/demo # OpenID server context root openidserver.url=http://localhost:8095/openidserver {noformat} ### (/) I then ran the build.sh script in the root of /opt/atlassian... ## (/) I fired up crowd using the /opt/atlassian.../start_crowd.sh script ## (/) I then went to http://auth.mbari.org:8095/crowd to kick off the start up wizard ## (/) I grabbed a new eval license from my account on atlassian and pasted into the license page. ## (/) I selected "New install" on the next page. ## (/) I configured the JDBC connection using this connection URL with user DB_Collaboration {noformat} jdbc:jtds:sqlserver://dione.mbari.org:51001/Crowd;domain=SHORE;useNTLMv2=TRUE {noformat} ## (/) I left the "Options" as they came up {warning:title=Paths} Not sure if this is a problem, but because I started the set up using auth.mbari.org, it set the Base URL to http://auth.mbari.org:8095/crowd instead of localhost. Hope that is not a problem. We will see. {warning} ## (/) I configured the email connection using the settings from [here|https://wind.shore.mbari.org/is/howto/email/mbarimail/imap] and I used my network login (probably shouldn't be doing that ... not sure where it stores my password, but I am assuming in the DB). ## (/) For the local admin account, I created a user named 'crowdadm' so it would not clash with my LDAP account. See Kevin Gomes for password information. ## (/) I checked the OpenID server as an integrated application ## (/) It then took me to the login page and I logged in using the newly minted admin account. Seemed all is well so far. ## (/) I visited the openidserver URL as well and that seemed OK. ## (/) I decided to wait on configuring the MBARI LDAP directory until I got everything with SSL working. ## (/) Now the next step was to follow the directions to configure Crowd to run over SSL found [here|https://confluence.atlassian.com/display/CROWD/Configuring+Crowd+to+Work+with+SSL] ## (/) I shutdown crowd. Note that the stop script does not shutdown things correctly and I noticed the crowd app running as root. That should not be if I started as kgomes. Not sure what is up with that. ## (/) Now Joe had already configured SSL once, so I used his connector configuration in the server.xml file and so the final file looked like: {noformat} {noformat} ## (/) I then edited the /data/crowd/crowd.properties to look like: {noformat} #Sat Aug 01 09:05:15 PDT 2015 session.lastvalidation=session.lastvalidation session.tokenkey=session.tokenkey crowd.server.url=https\://localhost\:8443/crowd/services/ application.name=crowd http.timeout=30000 session.isauthenticated=session.isauthenticated application.login.url=https\://localhost\:8443/crowd/console/ session.validationinterval=0 application.password=Y1Xp3OorCmsOP4eruL1dmH {noformat} One thing to note here is that based on a comment from the SSL configuration page at atlassian (Steve's comment), you are supposed to leave all the host names the same. For example, if the file says localhost, leave it localhost. So this created a bit of a problem based on the fact that I had left the base URL pointing to auth.mbari.org in the wizard steps above. That step wrote auth.mbari.org to the /data/crowd/crowd.properties. All the other files reference localhost, so to be consistent, I changed auth.mbari.org to localhost in the /data/crowd/crowd.properties file. We will see if this works. ## (/) Per the instructions on the atlassian page (referenced above), I also edited the build.properties file and the /client/conf/crowd.properties files before I restarted and used the SSL URLs ## build.properties: {noformat} # Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See https://confluence.atlassian.com/display/CROWD/Connecting+Crowd+to+a+Database hibernate.dialect=org.hibernate.dialect.SQLServerDialect # The Hibernate transaction factory to use. See https://confluence.atlassian.com/display/CROWD/Configuring+Crowd hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory # The http port you wish to run crowd from, ie: http://localhost:8095/crowd crowd.tomcat.connector.port=8095 # Tomcat requires a unique port for shutdown crowd.tomcat.shutdown.port=8020 # Crowd context root crowd.url=https://localhost:8443/crowd # Demo context root demo.url=https://localhost:8443/demo # OpenID server context root openidserver.url=https://localhost:8443/openidserver {noformat} ## crowd.properties (client) {noformat} application.name crowd application.password password application.login.url https://localhost:8443/crowd/console/ crowd.server.url https://localhost:8443/crowd/services/ crowd.base.url https://localhost:8443/crowd/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 2 session.lastvalidation session.lastvalidation {noformat} ## (/) Although not stated, I am assuming you would need to run the build.sh script to push the build.properties changes to their proper places, so I did that. Note that before doing that, I know that it will clobber the server.xml changes I made, so I made a copy of that file and diff'd them after and then rolled the previous changes to the new server.xml file. Actually, amazingly enough, it seems to have done the connector entry correctly so I left it after running the build.sh script. ## (/) Crossed my fingers and then restarted crowd. I tailed the catalina.out file and did not see any stack traces so that is a good sign! ## (/) I visited https://auth.mbari.org:8443/crowd first. It could not find that page, but I suspect that is because I am browsing from the outside, so I tried just https://auth.mbari.org/crowd and got a service unavailable. I am suspecting that this is a combination of firewall and proxy pass and I will send this info to Joe. From what I can see on the crowd side, it seems like the server started cleanly, we just can't get to it. I tried to reach it from a browser on the machine itself too (through VNC) with the same service not available. ## (/) Here are the notes from Joe after he fixed it! Wooohooo! {noformat} Hey Kevin, Thanks for starting clean! I had to make a few adjustments. 1-I modified the server.xml file in /opt/atlassian-crowd-2.8.3/apache-tomcat/conf/server.xml so there are two connectors per the instructions on the Atlassian site. I have backed up this good server.xml file in /etc/temp/ if you want to browse it to see what I did. Of note is that I removed all the jargon referencing the types of ciphers available to simplify things for now. 2-I modified /data/crowd/crowd.properties to have crowd.server.url=https\://localhost\:8443/crowd/services/ application.login.url=https\://localhost\:8443/crowd/console/ But that would cause my login to error with an error saying it was unable to reach the authentication server. I scratched my head for a bit. When I revert the values to just using non-SSL and try to log in, I just get an "invalid login" (I don't know the crowdadm password). So I worked under the assumption that if I can configure SSL to get an "invalid login" when logging in then it would work when provided real credentials. So, I then changed /data/crowd/crowd.proprties to: crowd.server.url=https\://auth.mbari.org\:8443/crowd/services/ application.login.url=https\://auth.mbari.org\:8443/crowd/console/ And now when I try to log in with SSL it says "invalid login". Strange because all the other values I can find only show "localhost" .. in any case... Can you try to log in now? {noformat} ## (/) Next I moved on to configuring the connection to MBARI's LDAP server to enable our logins through Crowd and CrowdID ## (/) I clicked on "Add Directory" in crowd. ## (/) I selected "Connector" then clicked Next ## (/) I put ldap.shore.mbari.org as the name of the server ## (/) I selected "Use memberOf for group memberships" ## (/) I used "OU=AllUsers,DC=shore,DC=mbari,DC=org" for the Base DN ## (/) I used "CN=LDAPbind,OU=Special,OU=AllUsers,DC=shore,DC=mbari,DC=org" for the Username (talk to Pat Allen for password) ## (/) I tested the connection (button click) and it passed. ## (/) I de-selected all the capabilities of the connector as it is a ready only connector and then saved it. It synchronized correctly! ## (/) At first, I could not login using my MBARI credentials, but after going to the "crowd" application in crowd (logged in as the local admin), I had to add the LDAP directory and configure it to "Allow all to authenticate", then I was able to login. After this, the last step was to get this to run as a different user and lock down various directories. I went through the entire directory structure /opt/atlassian... and set up so that root owned all read-only locations and DB_Collaboration (account set up by IS) owned the other stuff. I also gave full ownership to the /data/crowd directory to DB_Collaboration so it could write there. Pat set up a script to start on boot and after a little tweaking, it now starts on boot. {warning:title=CrowdID log file} One thing that came up here was that when the crowdID application ran, it tried to write a log file to the location where the process was launched from (which is /opt/atlassian...). This is a bad thing and I figured out that I could change that location by changing the file /opt/atlassian-crowd-2.8.3/crowd-openidserver-webapp/WEB-INF/classes/log4j.properties and hardcoding the /data/crowd/logs/atlassian-crowd-openid-server.log and then restarted the application. {warning} ## (/) Another note is the when an application tried to use the OpenID application, it would get redirected to localhost. I changed the /opt/atlassian.../crowd-openidserver-webapp/WEB-INF/classes/crowd.properties file to look like: {noformat} #Sat Aug 01 10:03:18 PDT 2015 session.lastvalidation=session.lastvalidation session.tokenkey=session.tokenkey crowd.server.url=http\://localhost\:8095/crowd/services/ application.name=crowd-openid-server #application.login.url.template=http\://localhost\:8095/openidserver?returnToUrl\=${RETURN_TO_URL} application.login.url.template=https\://auth.mbari.org/openidserver?returnToUrl\=${RETURN_TO_URL} session.isauthenticated=session.isauthenticated #application.base.url=http\://localhost\:8095/openidserver application.base.url=https\://auth.mbari.org/openidserver #application.login.url=http\://localhost\:8095/openidserver application.login.url=https\://auth.mbari.org/openidserver session.validationinterval=0 application.password=password {noformat} and that seems to have fixed it. # (/) It is finally time to move on to the version 4 upgrade ... holy crap. I first went to the *new* crowd install (auth.mbari.org) and logged in as the crowdadm. # (/) I clicked on Applications, then on Add Application # (/) I selected JIRA from the Application type drop-down # (/) I entered jira445 as the username. Ask Kevin about the password. # (/) I used http://bugs.shore.mbari.org:8081 as the URL # (/) I used 134.89.12.31 as the IP address. # (/) I selected only the MBARI LDAP directory. # (/) Then I selected "Allow all users to authenticate" # (/) Then I clicked on "Add Application" # (/) I VNC'd into bugs.mbari.org. As it turns out, for Linux, there is an installer program to download. I downloaded the .bin for 64 bit Linux installer and moved it to the jira-upgrade directory. # (/) I chmod'd the file to make it executable and ran it. It gave me a warning about not being root, but I went ahead with it. # (/) It asked for the JIRA home and data directory, which I specified as /opt/jira4 and /data/jira445. # (/) For the ports, I specified 8180 and 8105 (HTTP and control respectively). It then extracted all the files and launched JIRA. It said if finished, so I opened a local browser to http://localhost:8180 which kicked off the start up wizard. # (/) I specified the external database using: ## solstice2.shore.mbari.org (server) ## 1433 (port) ## jira4 (database) ## DB_Collaboration (username) ## (password ask Kevin) ## dbo (schema) # But all this failed as it seems to just want to try and use the SQL server authentication instead of domain. I will have to do it manually.]]> 27558171 27590942 4.4: [https://confluence.atlassian.com/display/JIRA044/Migrating+JIRA+to+Another+Server] ## The JIRA configuration tool: [https://confluence.atlassian.com/display/JIRA044/Using+the+JIRA+Configuration+Tool] h5. Steps # (/) Create new VM named bugs.mbari.org in the DMZ # (/) Have Neil create database Jira_Temp on solstice2.shore.mbari.org # (/) Have Neil create database Jira on solstice2.shore.mbari.org # (/) Have Pat install Java 7 on bugs.shore.mbari.org # (/) Have Pete plumb holes through firewall so processes on bugs.mbari.org can get to Solstice2 # (/) Have Pat create DB_Collaboration account on bugs so it can run JIRA under that account and it can connect to solstice2 using that NT Domain account. # (/) Upgrade license on Atlassian site # (/) Log into bugs.shore.mbari.org # (/) Download 3.13.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 4.4.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 5.2.11 standalone Linux 64 bit tar.gz (not sure this version is necessary, but at least I have it) # (/) Unzip and untar the file to /opt # (/) Download latest JIRA (6.4.7 as of this writing). # (/) Unzip and untar it to /opt # Performed Test Upgrade ## (/) In order to export the current stuff in JIRA, I had to shut off access so people could not change the data while I was backing it up. ## (/) I ssh'd to oceana.mbari.org as root and edited the /opt/jira/conf/server.xml file and commented out the Connector section that had the port of 8010 to shut it off from the normal serving route. ## (/) I uncommented the 8082 port connector and the 8443 port connector so that I could still get to the server. ## (/) I stopped and started the JIRA server and in the log file I got a "keystore was tampered with..." which is not surprising. ## (/) I could then browser over to http://oceana.mbari.org:8082/jira ## (/) Then through the Administration console, I did an XML backup ## (/) I then created a tar of all the attachments in the /data/jira_3_12/attachments directory ## (/) I moved both the XML and tar files to the /root/jira-upgrade directory ## (/) I then reversed the changes to the server.xml file and shut down JIRA ## (/) I left it down during the next steps in case it went so well, I could just point people to the new server (yeah, right). ## (/) I then browsed to the crowd server on oceana and add a new application using: ### URL: http://bugs.mbari.org/jira3135 ### IP: 134.89.2.29 ### Name: JIRA3135 ### Password: (ask Kevin) :) ## (/) On bugs, I made a copy of the JIRA 3.13.5 download in the /opt directory and unzipped and untarred it. ## (/) In order to configure the crowd connection I did the following: ### (/) I scp'd the /opt/crowd/client/crowd-integration-client-1.6.jar file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I removed the existing 1.6.1 crowd client jar from the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I scp'd the /opt/crowd/client/conf/crowd.properties file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I scp'd the /opt/crowd/client/conf/crowd-ehcache.xml file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I edited the crowd.properties file on bugs to look like: {noformat} application.name JIRA3135 application.password (ask Kevin) application.login.url http://oceana.mbari.org:8095/crowd/console/ crowd.server.url http://oceana.mbari.org:8095/crowd/services/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 0 session.lastvalidation session.lastvalidation {noformat} ### (/) I edited the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/osuser.xml file to comment out the current authentication mechanism and then uncomment the crowd one. ## (/) I then edited the /opt/atlassian-jira-standalone-3.13.5/conf/server/xml file and configured the database connection to the Jira_Temp database on Solstice2. I looked like this: {noformat} {noformat} ## (/) Edit the /opt/atlassian/jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/entityengine.xml and changed it from 'hsql' to 'mssql' and delete the line with "PUBLIC" in it per the instructions in the comments in that file. ## (/) I edited the /etc/httpd/conf/httpd.conf file and created a proxy pass at the bottom of the file to point a normal URL to the default port 8080 for JIRA: {noformat} # Proxy Pass for JIRA ProxyPass http://bugs.mbari.org:8080 ProxyPassReverse http://bugs.mbari.org:8080 {noformat} ## (/) I restarted Apache ## (/) I scp'd the jtds driver from oceana to the /opt/atlassian-jira-standalone-3.13.5/common/lib directory (you could down from the internet) ## (/) I then went to the /opt/atlassian-jira-standalone-3.13.5/ directory and ran './bin/startup.sh'. From the log file, I could tell things were hanging. After some troubleshooting I am wondering if the local firewall is preventing the application to get access to the database on solstice2. I can telnet to port 1433, but I can't browse to the base http://bugs.mbari.org from anywhere but the local web browser. I have submitted a ticket. ## (/) I restarted the old JIRA with my hopes dashed :(. ## (/) Pat disabled the firewall on bugs.mbari.org but it still hung trying to connect to solstice2.shore.mbari.org. That is really, really perplexing. Neil mentioned that solstice2 is using Kerberos and solstice is not. Checking with the JTDS docs, version 1.3.1 of the driver added kerberos support, so I downloaded that driver and added the 'userKerberos=true' property to the URL in the server.xml file and restarted. Got an error about no credentials, so added user and password properties to the URL. Nope, no luck. Never did figure this one out, but I had Pat pull the VM inside the firewall and after some thrash it worked. Well, it sort of worked ... sigh. It turns out I had downloaded the standard version instead of the enterprise version. I need to redo this work ... grrr. ## (/) I deleted all the tables in the Jira_Temp database and removed the /data/jira3135/indexes directory (and recreated). ## (/) I downloaded the enterprise version of the 3.13.5 server. I made a copy in the /opt directory and unzipped and untarred the file. ## (/) I went back to crowd and edited the application to change the properties to: ### URL: http://bugs.shore.mbari.org:8080 ### IP: 134.89.12.31 ### Name: jira3135 ### Password: (ask Kevin) :) ## (/) I then repeated the steps above to get the server up and running with the following differences: ### The server name is now bugs.shore.mbari.org ### The paths given above are a little different in that they no longer say "standard" but say "enterprise" ### I deleted the proxy pass as it seemed to have issues before and this is only temporary anyway. ## (/) I then browsed to http://bugs.shore.mbari.org:8080 ## (/) It took me to the start up page and at the top was the option to 'import your existing data'. Seemed too good not to try. I clicked on the link. It asked me for the backup file location and the location where the indexes would be stored. ## (/) I copied the XML zip file and the attachments tar file to the /data/original directory. ## (/) I created the /data/jira3135/indexes and used those directories ... it fired off the import and I waited. ## (/) I tailed the log file to watch the import. Holy crap, it worked!!! I could log in and everything! I copied the results from the log file here for posterity sake: {noformat} 2015-07-22 20:55:45,156 http-8080-Processor22 INFO [jira.action.admin.DataImport] Running data import 2015-07-22 20:55:45,179 http-8080-Processor22 INFO [jira.action.admin.DataImport] Importing data.. 2015-07-22 20:55:45,186 http-8080-Processor22 INFO [jira.action.admin.DataImport] Start parsing XML with SAX Parser 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] XML successfully parsed 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] Removing all entries from the database. 2015-07-22 20:56:24,593 http-8080-Processor22 INFO [jira.action.admin.DataImport] All entries removed. 2015-07-22 20:56:24,594 http-8080-Processor22 INFO [jira.action.admin.DataImport] Started storing 410414 Generic Values 2015-07-22 21:01:51,967 http-8080-Processor22 INFO [jira.action.admin.DataImport] Finished storing Generic Values 2015-07-22 21:01:52,329 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:52,361 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:54,683 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLink' to module 'jira.user.format:profile-link-user-format'. 2015-07-22 21:01:54,724 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullName' to module 'jira.user.format:full-name-user-format'. 2015-07-22 21:01:54,773 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkSearcher' to module 'jira.user.format:profile-link-searcher-user-format'. 2015-07-22 21:01:54,784 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkExternal' to module 'jira.user.format:profile-link-external-user-format'. 2015-07-22 21:01:54,795 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkActionHeader' to module 'jira.user.format:profile-link-action-header-user-format'. 2015-07-22 21:01:54,807 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullProfile' to module 'jira.user.format:full-profile-user-format'. 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/comments 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/issues 2015-07-22 21:01:55,641 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/plugins 2015-07-22 21:01:55,867 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:01:55,871 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/issues does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:55,873 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/comments does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,033 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,257 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,889 http-8080-Processor22 ERROR [atlassian.jira.upgrade.ConsistencyCheckImpl] Attachments are turned on, but attachment path [/data/jira_3_12/attachments] invalid - disabling attachments 2015-07-22 21:02:13,904 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Detected that an upgrade is needed; existing data at build 299 2015-07-22 21:02:13,907 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Doing Upgrade... 2015-07-22 21:02:13,915 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value' succeeded 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 317 2015-07-22 21:02:13,944 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite filters - make each filter a favourite of its owner. 2015-07-22 21:02:17,822 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build319] Could not find author 'fpy' for filter with id '10040' 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite filters - make each filter a favourite of its owner.' succeeded 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 319 2015-07-22 21:02:17,995 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise Share Permissions. Move old shares to new shares. 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise Share Permissions. Move old shares to new shares.' succeeded 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 321 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Migrating the old JIRA UI colors to the new JIRA 3.13 colors 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build322] Custom color detected for jira.lf.menu.bgcolour : #336699 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Migrating the old JIRA UI colors to the new JIRA 3.13 colors' succeeded 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 322 2015-07-22 21:02:18,025 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite dashboards - make each dashboard a favourite of its owner. 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'cmcgann' for dashboard with id '10030' 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'fpy' for dashboard with id '10060' 2015-07-22 21:02:18,423 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'kanna' for dashboard with id '10040' 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite dashboards - make each dashboard a favourite of its owner.' succeeded 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 325 2015-07-22 21:02:18,625 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Reindexing all data in JIRA to include Favourites. 2015-07-22 21:02:18,648 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All starting... 2015-07-22 21:02:18,650 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 0% complete. Current index: Issue 2015-07-22 21:02:18,654 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:02:18,809 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 1% complete. Current index: Issue 2015-07-22 21:02:18,855 indexerPool-2-thread-10 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 2% complete. Current index: Issue 2015-07-22 21:02:18,899 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 3% complete. Current index: Issue 2015-07-22 21:02:18,945 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 4% complete. Current index: Issue 2015-07-22 21:02:19,012 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 5% complete. Current index: Issue . . . 2015-07-22 21:02:26,164 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 95% complete. Current index: Issue 2015-07-22 21:02:26,232 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 96% complete. Current index: Issue 2015-07-22 21:02:26,316 indexerPool-2-thread-9 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 97% complete. Current index: Issue 2015-07-22 21:02:26,771 indexerPool-2-thread-3 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: Issue 2015-07-22 21:02:27,261 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 8607ms. Indexer: DefaultIndexManager: paths: [/data/jira3135/indexes/issues, /data/jira3135/indexes/comments] 2015-07-22 21:02:27,263 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: SearchRequest 2015-07-22 21:02:27,268 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,293 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: SearchRequest 2015-07-22 21:02:27,308 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: PortalPage 2015-07-22 21:02:27,312 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,377 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: PortalPage 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 115ms. Indexer: SharedEntityIndexManager: paths: [/data/jira3135/indexes/entities/portalpage, /data/jira3135/indexes/entities/searchrequest] 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All complete. Total time: 8722ms. 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Reindexing all data in JIRA to include Favourites.' succeeded 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 326 2015-07-22 21:02:27,397 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade succeeded! Setting data build number to 360 2015-07-22 21:02:27,469 JiraQuartzScheduler_Worker-0 WARN [service.services.export.ExportService] Backup directory /data/jira_3_12/backup does not exist {noformat} {warning:title=Paths} It appears that the upgraded JIRA will still look for the attachments and the backup locations in the original places. So I created /data/jira_3_12/backup and untarred the original attachments to /data/jira_3_12 and then everything worked (including attachements) in the new JIRA. {warning} ## (/) I then used the upgraded JIRA to generate a new XML backup and stored it in /data/original/3.13.5 along with another tar of the files in /data/jira_3_12/attachments. ## (/) I then shutdown the JIRA server. *I should be ready to move on to version 4 upgrade WHEW* ## So, before moving on, I decided that it would be a really good idea to spin up a new Crowd instance to get rid of the :8443 in the URL and to move off of RedHat per IS requests. I have a ticket in for a new VM and a new database to try to get this going. I am waiting on that before moving on. ## (/) Pat created the VM and Neil created the database. ## (/) I logged into auth.mbari.org (name of the VM) and downloaded crowd which I unzipped to the /opt directory ## (/) I then created a /data/crowd directory and gave my account permissions on it and then edited the /opt/atlassian..../crowd-webapp/WEB-INF/classes/crowd-init.properties file to set that as the crowd home directory. ## (/) The instructions say to download the JDBC driver, but they already have JTDS 1.2.7 in the download so I did not do anything. ## (/) You have to manually connect up CrowdID to a database as they setup wizard does not currently do this. ### (/) They say to download the driver, but again 1.2.7 was there so I did nothing. ### (/) I edited the /opt/atlassian.../apache-tomcat/conf/Catalina/localhost/openidserver.xml to look like: {noformat} {noformat} ### (/) I edited the /opt/atlassian.../build.properties files to look like: {noformat} # Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See https://confluence.atlassian.com/display/CROWD/Connecting+Crowd+to+a+Database hibernate.dialect=org.hibernate.dialect.SQLServerDialect # The Hibernate transaction factory to use. See https://confluence.atlassian.com/display/CROWD/Configuring+Crowd hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory # The http port you wish to run crowd from, ie: http://localhost:8095/crowd crowd.tomcat.connector.port=8095 # Tomcat requires a unique port for shutdown crowd.tomcat.shutdown.port=8020 # Crowd context root crowd.url=http://localhost:8095/crowd # Demo context root demo.url=http://localhost:8095/demo # OpenID server context root openidserver.url=http://localhost:8095/openidserver {noformat} ### (/) I then ran the build.sh script in the root of /opt/atlassian... ## (/) I fired up crowd using the /opt/atlassian.../start_crowd.sh script ## (/) I then went to http://auth.mbari.org:8095/crowd to kick off the start up wizard ## (/) I grabbed a new eval license from my account on atlassian and pasted into the license page. ## (/) I selected "New install" on the next page. ## (/) I configured the JDBC connection using this connection URL with user DB_Collaboration {noformat} jdbc:jtds:sqlserver://dione.mbari.org:51001/Crowd;domain=SHORE;useNTLMv2=TRUE {noformat} ## (/) I left the "Options" as they came up {warning:title=Paths} Not sure if this is a problem, but because I started the set up using auth.mbari.org, it set the Base URL to http://auth.mbari.org:8095/crowd instead of localhost. Hope that is not a problem. We will see. {warning} ## (/) I configured the email connection using the settings from [here|https://wind.shore.mbari.org/is/howto/email/mbarimail/imap] and I used my network login (probably shouldn't be doing that ... not sure where it stores my password, but I am assuming in the DB). ## (/) For the local admin account, I created a user named 'crowdadm' so it would not clash with my LDAP account. See Kevin Gomes for password information. ## (/) I checked the OpenID server as an integrated application ## (/) It then took me to the login page and I logged in using the newly minted admin account. Seemed all is well so far. ## (/) I visited the openidserver URL as well and that seemed OK. ## (/) I decided to wait on configuring the MBARI LDAP directory until I got everything with SSL working. ## (/) Now the next step was to follow the directions to configure Crowd to run over SSL found [here|https://confluence.atlassian.com/display/CROWD/Configuring+Crowd+to+Work+with+SSL] ## (/) I shutdown crowd. Note that the stop script does not shutdown things correctly and I noticed the crowd app running as root. That should not be if I started as kgomes. Not sure what is up with that. ## (/) Now Joe had already configured SSL once, so I used his connector configuration in the server.xml file and so the final file looked like: {noformat} {noformat} ## (/) I then edited the /data/crowd/crowd.properties to look like: {noformat} #Sat Aug 01 09:05:15 PDT 2015 session.lastvalidation=session.lastvalidation session.tokenkey=session.tokenkey crowd.server.url=https\://localhost\:8443/crowd/services/ application.name=crowd http.timeout=30000 session.isauthenticated=session.isauthenticated application.login.url=https\://localhost\:8443/crowd/console/ session.validationinterval=0 application.password=Y1Xp3OorCmsOP4eruL1dmH {noformat} One thing to note here is that based on a comment from the SSL configuration page at atlassian (Steve's comment), you are supposed to leave all the host names the same. For example, if the file says localhost, leave it localhost. So this created a bit of a problem based on the fact that I had left the base URL pointing to auth.mbari.org in the wizard steps above. That step wrote auth.mbari.org to the /data/crowd/crowd.properties. All the other files reference localhost, so to be consistent, I changed auth.mbari.org to localhost in the /data/crowd/crowd.properties file. We will see if this works. ## (/) Per the instructions on the atlassian page (referenced above), I also edited the build.properties file and the /client/conf/crowd.properties files before I restarted and used the SSL URLs ## build.properties: {noformat} # Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See https://confluence.atlassian.com/display/CROWD/Connecting+Crowd+to+a+Database hibernate.dialect=org.hibernate.dialect.SQLServerDialect # The Hibernate transaction factory to use. See https://confluence.atlassian.com/display/CROWD/Configuring+Crowd hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory # The http port you wish to run crowd from, ie: http://localhost:8095/crowd crowd.tomcat.connector.port=8095 # Tomcat requires a unique port for shutdown crowd.tomcat.shutdown.port=8020 # Crowd context root crowd.url=https://localhost:8443/crowd # Demo context root demo.url=https://localhost:8443/demo # OpenID server context root openidserver.url=https://localhost:8443/openidserver {noformat} ## crowd.properties (client) {noformat} application.name crowd application.password password application.login.url https://localhost:8443/crowd/console/ crowd.server.url https://localhost:8443/crowd/services/ crowd.base.url https://localhost:8443/crowd/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 2 session.lastvalidation session.lastvalidation {noformat} ## (/) Although not stated, I am assuming you would need to run the build.sh script to push the build.properties changes to their proper places, so I did that. Note that before doing that, I know that it will clobber the server.xml changes I made, so I made a copy of that file and diff'd them after and then rolled the previous changes to the new server.xml file. Actually, amazingly enough, it seems to have done the connector entry correctly so I left it after running the build.sh script. ## (/) Crossed my fingers and then restarted crowd. I tailed the catalina.out file and did not see any stack traces so that is a good sign! ## (/) I visited https://auth.mbari.org:8443/crowd first. It could not find that page, but I suspect that is because I am browsing from the outside, so I tried just https://auth.mbari.org/crowd and got a service unavailable. I am suspecting that this is a combination of firewall and proxy pass and I will send this info to Joe. From what I can see on the crowd side, it seems like the server started cleanly, we just can't get to it. I tried to reach it from a browser on the machine itself too (through VNC) with the same service not available. ## (/) Here are the notes from Joe after he fixed it! Wooohooo! {noformat} Hey Kevin, Thanks for starting clean! I had to make a few adjustments. 1-I modified the server.xml file in /opt/atlassian-crowd-2.8.3/apache-tomcat/conf/server.xml so there are two connectors per the instructions on the Atlassian site. I have backed up this good server.xml file in /etc/temp/ if you want to browse it to see what I did. Of note is that I removed all the jargon referencing the types of ciphers available to simplify things for now. 2-I modified /data/crowd/crowd.properties to have crowd.server.url=https\://localhost\:8443/crowd/services/ application.login.url=https\://localhost\:8443/crowd/console/ But that would cause my login to error with an error saying it was unable to reach the authentication server. I scratched my head for a bit. When I revert the values to just using non-SSL and try to log in, I just get an "invalid login" (I don't know the crowdadm password). So I worked under the assumption that if I can configure SSL to get an "invalid login" when logging in then it would work when provided real credentials. So, I then changed /data/crowd/crowd.proprties to: crowd.server.url=https\://auth.mbari.org\:8443/crowd/services/ application.login.url=https\://auth.mbari.org\:8443/crowd/console/ And now when I try to log in with SSL it says "invalid login". Strange because all the other values I can find only show "localhost" .. in any case... Can you try to log in now? {noformat} ## (/) Next I moved on to configuring the connection to MBARI's LDAP server to enable our logins through Crowd and CrowdID ## (/) I clicked on "Add Directory" in crowd. ## (/) I selected "Connector" then clicked Next ## (/) I put ldap.shore.mbari.org as the name of the server ## (/) I selected "Use memberOf for group memberships" ## (/) I used "OU=AllUsers,DC=shore,DC=mbari,DC=org" for the Base DN ## (/) I used "CN=LDAPbind,OU=Special,OU=AllUsers,DC=shore,DC=mbari,DC=org" for the Username (talk to Pat Allen for password) ## (/) I tested the connection (button click) and it passed. ## (/) I de-selected all the capabilities of the connector as it is a ready only connector and then saved it. It synchronized correctly! ## (/) At first, I could not login using my MBARI credentials, but after going to the "crowd" application in crowd (logged in as the local admin), I had to add the LDAP directory and configure it to "Allow all to authenticate", then I was able to login. After this, the last step was to get this to run as a different user and lock down various directories. I went through the entire directory structure /opt/atlassian... and set up so that root owned all read-only locations and DB_Collaboration (account set up by IS) owned the other stuff. I also gave full ownership to the /data/crowd directory to DB_Collaboration so it could write there. Pat set up a script to start on boot and after a little tweaking, it now starts on boot. {warning:title=CrowdID log file} One thing that came up here was that when the crowdID application ran, it tried to write a log file to the location where the process was launched from (which is /opt/atlassian...). This is a bad thing and I figured out that I could change that location by changing the file /opt/atlassian-crowd-2.8.3/crowd-openidserver-webapp/WEB-INF/classes/log4j.properties and hardcoding the /data/crowd/logs/atlassian-crowd-openid-server.log and then restarted the application. {warning} ## (/) Another note is the when an application tried to use the OpenID application, it would get redirected to localhost. I changed the /opt/atlassian.../crowd-openidserver-webapp/WEB-INF/classes/crowd.properties file to look like: {noformat} #Sat Aug 01 10:03:18 PDT 2015 session.lastvalidation=session.lastvalidation session.tokenkey=session.tokenkey crowd.server.url=http\://localhost\:8095/crowd/services/ application.name=crowd-openid-server #application.login.url.template=http\://localhost\:8095/openidserver?returnToUrl\=${RETURN_TO_URL} application.login.url.template=https\://auth.mbari.org/openidserver?returnToUrl\=${RETURN_TO_URL} session.isauthenticated=session.isauthenticated #application.base.url=http\://localhost\:8095/openidserver application.base.url=https\://auth.mbari.org/openidserver #application.login.url=http\://localhost\:8095/openidserver application.login.url=https\://auth.mbari.org/openidserver session.validationinterval=0 application.password=password {noformat} and that seems to have fixed it. # (/) It is finally time to move on to the version 4 upgrade ... holy crap. I first went to the *new* crowd install (auth.mbari.org) and logged in as the crowdadm. # (/) I clicked on Applications, then on Add Application # (/) I selected JIRA from the Application type drop-down # (/) I entered jira445 as the username. Ask Kevin about the password. # (/) I used http://bugs.shore.mbari.org:8081 as the URL # (/) I used 134.89.12.31 as the IP address. # (/) I selected only the MBARI LDAP directory. # (/) Then I selected "Allow all users to authenticate" # (/) Then I clicked on "Add Application" # (/) I VNC'd into bugs.mbari.org. As it turns out, for Linux, there is an installer program to download. I downloaded the .bin for 64 bit Linux installer and moved it to the jira-upgrade directory. # (/) I chmod'd the file to make it executable and ran it. It gave me a warning about not being root, but I went ahead with it. # (/) It asked for the JIRA home and data directory, which I specified as /opt/jira4 and /data/jira445. # (/) For the ports, I specified 8180 and 8105 (HTTP and control respectively). It then extracted all the files and launched JIRA. It said if finished, so I opened a local browser to http://localhost:8180 which kicked off the start up wizard. # (/) I specified the external database using: ## solstice2.shore.mbari.org (server) ## 1433 (port) ## jira4 (database) ## DB_Collaboration (username) ## (password ask Kevin) ## dbo (schema) # But all this failed as it seems to just want to try and use the SQL server authentication instead of domain. I will have to do it manually. # (/) I stopped the server using the bin/stop-jira.sh script. # (/) I created and edited /data/jira445/dbconfig.xml and made it look like the following: {noformat} ?xml version="1.0" encoding="UTF-8"?> defaultDS default mssql jiraschema jdbc:jtds:sqlserver://solstice2.shore.mbari.org:1433/Jira4;domain=SHORE;useNTLMv2=true net.sourceforge.jtds.jdbc.Driver DB_Collaboration (ask Kevin) 15 {noformat} # (/) I then started it again using bin/start-jira.sh and tailed the catalina.out file. Got a bunch of errors related to the schema 'jiraschema', I edited the file and changed the schema to 'dbo' and restarted. That seemed to do it. There was one stack trace for some iCal plugin, but looks OK other than that. # I browsed back to localhost:8180 and the wizard moved to step 2. There was an option to import existing data bit without the crowd connection, I thought I should set it up manually, connect to crowd, then import. I generated an evaluation license, called the app "MBARI JIRA4" and change the server in the url to bugs.shore.mbari.org # For the admin, I created an account called 'jiraadm' (ask Kevin for password). # Since this is a temporary system, I left the email system disabled. # I logged in as jiraadm, went to Administration, then Users, then clicked on Add Directory and chose Atlassian Crowd. Note that I had to set the server URL to http://auth.mbari.org:8095/crowd or I would have had to configure all this SSL crap that I did not want to do for this temporary install. # It tested successfully, I clicked Save and it went through a 13 second sync, whew! # I then went to System->Import and Export->Restore System # I copied the jira-upgrade-3.13.5.zip file from the previous version export into /data/jira445/import and then entered that file name along with the new evaluation license again. # I worked through progress bar after I clicked on Restore. ]]> 27558178 19073840 19041149 27590940 4.4: [https://confluence.atlassian.com/display/JIRA044/Migrating+JIRA+to+Another+Server] ## The JIRA configuration tool: [https://confluence.atlassian.com/display/JIRA044/Using+the+JIRA+Configuration+Tool] h5. Steps # (/) Create new VM named bugs.mbari.org in the DMZ # (/) Have Neil create database Jira_Temp on solstice2.shore.mbari.org # (/) Have Neil create database Jira on solstice2.shore.mbari.org # (/) Have Pat install Java 7 on bugs.shore.mbari.org # (/) Have Pete plumb holes through firewall so processes on bugs.mbari.org can get to Solstice2 # (/) Have Pat create DB_Collaboration account on bugs so it can run JIRA under that account and it can connect to solstice2 using that NT Domain account. # (/) Upgrade license on Atlassian site # (/) Log into bugs.shore.mbari.org # (/) Download 3.13.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 4.4.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 5.2.11 standalone Linux 64 bit tar.gz (not sure this version is necessary, but at least I have it) # (/) Unzip and untar the file to /opt # (/) Download latest JIRA (6.4.7 as of this writing). # (/) Unzip and untar it to /opt # Performed Test Upgrade ## (/) In order to export the current stuff in JIRA, I had to shut off access so people could not change the data while I was backing it up. ## (/) I ssh'd to oceana.mbari.org as root and edited the /opt/jira/conf/server.xml file and commented out the Connector section that had the port of 8010 to shut it off from the normal serving route. ## (/) I uncommented the 8082 port connector and the 8443 port connector so that I could still get to the server. ## (/) I stopped and started the JIRA server and in the log file I got a "keystore was tampered with..." which is not surprising. ## (/) I could then browser over to http://oceana.mbari.org:8082/jira ## (/) Then through the Administration console, I did an XML backup ## (/) I then created a tar of all the attachments in the /data/jira_3_12/attachments directory ## (/) I moved both the XML and tar files to the /root/jira-upgrade directory ## (/) I then reversed the changes to the server.xml file and shut down JIRA ## (/) I left it down during the next steps in case it went so well, I could just point people to the new server (yeah, right). ## (/) I then browsed to the crowd server on oceana and add a new application using: ### URL: http://bugs.mbari.org/jira3135 ### IP: 134.89.2.29 ### Name: JIRA3135 ### Password: (ask Kevin) :) ## (/) On bugs, I made a copy of the JIRA 3.13.5 download in the /opt directory and unzipped and untarred it. ## (/) In order to configure the crowd connection I did the following: ### (/) I scp'd the /opt/crowd/client/crowd-integration-client-1.6.jar file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I removed the existing 1.6.1 crowd client jar from the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I scp'd the /opt/crowd/client/conf/crowd.properties file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I scp'd the /opt/crowd/client/conf/crowd-ehcache.xml file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I edited the crowd.properties file on bugs to look like: {noformat} application.name JIRA3135 application.password (ask Kevin) application.login.url http://oceana.mbari.org:8095/crowd/console/ crowd.server.url http://oceana.mbari.org:8095/crowd/services/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 0 session.lastvalidation session.lastvalidation {noformat} ### (/) I edited the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/osuser.xml file to comment out the current authentication mechanism and then uncomment the crowd one. ## (/) I then edited the /opt/atlassian-jira-standalone-3.13.5/conf/server/xml file and configured the database connection to the Jira_Temp database on Solstice2. I looked like this: {noformat} {noformat} ## (/) Edit the /opt/atlassian/jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/entityengine.xml and changed it from 'hsql' to 'mssql' and delete the line with "PUBLIC" in it per the instructions in the comments in that file. ## (/) I edited the /etc/httpd/conf/httpd.conf file and created a proxy pass at the bottom of the file to point a normal URL to the default port 8080 for JIRA: {noformat} # Proxy Pass for JIRA ProxyPass http://bugs.mbari.org:8080 ProxyPassReverse http://bugs.mbari.org:8080 {noformat} ## (/) I restarted Apache ## (/) I scp'd the jtds driver from oceana to the /opt/atlassian-jira-standalone-3.13.5/common/lib directory (you could down from the internet) ## (/) I then went to the /opt/atlassian-jira-standalone-3.13.5/ directory and ran './bin/startup.sh'. From the log file, I could tell things were hanging. After some troubleshooting I am wondering if the local firewall is preventing the application to get access to the database on solstice2. I can telnet to port 1433, but I can't browse to the base http://bugs.mbari.org from anywhere but the local web browser. I have submitted a ticket. ## (/) I restarted the old JIRA with my hopes dashed :(. ## (/) Pat disabled the firewall on bugs.mbari.org but it still hung trying to connect to solstice2.shore.mbari.org. That is really, really perplexing. Neil mentioned that solstice2 is using Kerberos and solstice is not. Checking with the JTDS docs, version 1.3.1 of the driver added kerberos support, so I downloaded that driver and added the 'userKerberos=true' property to the URL in the server.xml file and restarted. Got an error about no credentials, so added user and password properties to the URL. Nope, no luck. Never did figure this one out, but I had Pat pull the VM inside the firewall and after some thrash it worked. Well, it sort of worked ... sigh. It turns out I had downloaded the standard version instead of the enterprise version. I need to redo this work ... grrr. ## (/) I deleted all the tables in the Jira_Temp database and removed the /data/jira3135/indexes directory (and recreated). ## (/) I downloaded the enterprise version of the 3.13.5 server. I made a copy in the /opt directory and unzipped and untarred the file. ## (/) I went back to crowd and edited the application to change the properties to: ### URL: http://bugs.shore.mbari.org:8080 ### IP: 134.89.12.31 ### Name: jira3135 ### Password: (ask Kevin) :) ## (/) I then repeated the steps above to get the server up and running with the following differences: ### The server name is now bugs.shore.mbari.org ### The paths given above are a little different in that they no longer say "standard" but say "enterprise" ### I deleted the proxy pass as it seemed to have issues before and this is only temporary anyway. ## (/) I then browsed to http://bugs.shore.mbari.org:8080 ## (/) It took me to the start up page and at the top was the option to 'import your existing data'. Seemed too good not to try. I clicked on the link. It asked me for the backup file location and the location where the indexes would be stored. ## (/) I copied the XML zip file and the attachments tar file to the /data/original directory. ## (/) I created the /data/jira3135/indexes and used those directories ... it fired off the import and I waited. ## (/) I tailed the log file to watch the import. Holy crap, it worked!!! I could log in and everything! I copied the results from the log file here for posterity sake: {noformat} 2015-07-22 20:55:45,156 http-8080-Processor22 INFO [jira.action.admin.DataImport] Running data import 2015-07-22 20:55:45,179 http-8080-Processor22 INFO [jira.action.admin.DataImport] Importing data.. 2015-07-22 20:55:45,186 http-8080-Processor22 INFO [jira.action.admin.DataImport] Start parsing XML with SAX Parser 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] XML successfully parsed 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] Removing all entries from the database. 2015-07-22 20:56:24,593 http-8080-Processor22 INFO [jira.action.admin.DataImport] All entries removed. 2015-07-22 20:56:24,594 http-8080-Processor22 INFO [jira.action.admin.DataImport] Started storing 410414 Generic Values 2015-07-22 21:01:51,967 http-8080-Processor22 INFO [jira.action.admin.DataImport] Finished storing Generic Values 2015-07-22 21:01:52,329 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:52,361 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:54,683 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLink' to module 'jira.user.format:profile-link-user-format'. 2015-07-22 21:01:54,724 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullName' to module 'jira.user.format:full-name-user-format'. 2015-07-22 21:01:54,773 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkSearcher' to module 'jira.user.format:profile-link-searcher-user-format'. 2015-07-22 21:01:54,784 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkExternal' to module 'jira.user.format:profile-link-external-user-format'. 2015-07-22 21:01:54,795 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkActionHeader' to module 'jira.user.format:profile-link-action-header-user-format'. 2015-07-22 21:01:54,807 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullProfile' to module 'jira.user.format:full-profile-user-format'. 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/comments 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/issues 2015-07-22 21:01:55,641 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/plugins 2015-07-22 21:01:55,867 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:01:55,871 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/issues does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:55,873 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/comments does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,033 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,257 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,889 http-8080-Processor22 ERROR [atlassian.jira.upgrade.ConsistencyCheckImpl] Attachments are turned on, but attachment path [/data/jira_3_12/attachments] invalid - disabling attachments 2015-07-22 21:02:13,904 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Detected that an upgrade is needed; existing data at build 299 2015-07-22 21:02:13,907 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Doing Upgrade... 2015-07-22 21:02:13,915 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value' succeeded 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 317 2015-07-22 21:02:13,944 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite filters - make each filter a favourite of its owner. 2015-07-22 21:02:17,822 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build319] Could not find author 'fpy' for filter with id '10040' 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite filters - make each filter a favourite of its owner.' succeeded 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 319 2015-07-22 21:02:17,995 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise Share Permissions. Move old shares to new shares. 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise Share Permissions. Move old shares to new shares.' succeeded 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 321 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Migrating the old JIRA UI colors to the new JIRA 3.13 colors 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build322] Custom color detected for jira.lf.menu.bgcolour : #336699 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Migrating the old JIRA UI colors to the new JIRA 3.13 colors' succeeded 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 322 2015-07-22 21:02:18,025 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite dashboards - make each dashboard a favourite of its owner. 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'cmcgann' for dashboard with id '10030' 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'fpy' for dashboard with id '10060' 2015-07-22 21:02:18,423 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'kanna' for dashboard with id '10040' 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite dashboards - make each dashboard a favourite of its owner.' succeeded 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 325 2015-07-22 21:02:18,625 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Reindexing all data in JIRA to include Favourites. 2015-07-22 21:02:18,648 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All starting... 2015-07-22 21:02:18,650 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 0% complete. Current index: Issue 2015-07-22 21:02:18,654 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:02:18,809 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 1% complete. Current index: Issue 2015-07-22 21:02:18,855 indexerPool-2-thread-10 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 2% complete. Current index: Issue 2015-07-22 21:02:18,899 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 3% complete. Current index: Issue 2015-07-22 21:02:18,945 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 4% complete. Current index: Issue 2015-07-22 21:02:19,012 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 5% complete. Current index: Issue . . . 2015-07-22 21:02:26,164 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 95% complete. Current index: Issue 2015-07-22 21:02:26,232 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 96% complete. Current index: Issue 2015-07-22 21:02:26,316 indexerPool-2-thread-9 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 97% complete. Current index: Issue 2015-07-22 21:02:26,771 indexerPool-2-thread-3 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: Issue 2015-07-22 21:02:27,261 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 8607ms. Indexer: DefaultIndexManager: paths: [/data/jira3135/indexes/issues, /data/jira3135/indexes/comments] 2015-07-22 21:02:27,263 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: SearchRequest 2015-07-22 21:02:27,268 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,293 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: SearchRequest 2015-07-22 21:02:27,308 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: PortalPage 2015-07-22 21:02:27,312 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,377 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: PortalPage 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 115ms. Indexer: SharedEntityIndexManager: paths: [/data/jira3135/indexes/entities/portalpage, /data/jira3135/indexes/entities/searchrequest] 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All complete. Total time: 8722ms. 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Reindexing all data in JIRA to include Favourites.' succeeded 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 326 2015-07-22 21:02:27,397 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade succeeded! Setting data build number to 360 2015-07-22 21:02:27,469 JiraQuartzScheduler_Worker-0 WARN [service.services.export.ExportService] Backup directory /data/jira_3_12/backup does not exist {noformat} {warning:title=Paths} It appears that the upgraded JIRA will still look for the attachments and the backup locations in the original places. So I created /data/jira_3_12/backup and untarred the original attachments to /data/jira_3_12 and then everything worked (including attachements) in the new JIRA. {warning} ## (/) I then used the upgraded JIRA to generate a new XML backup and stored it in /data/original/3.13.5 along with another tar of the files in /data/jira_3_12/attachments. ## (/) I then shutdown the JIRA server. *I should be ready to move on to version 4 upgrade WHEW* ## So, before moving on, I decided that it would be a really good idea to spin up a new Crowd instance to get rid of the :8443 in the URL and to move off of RedHat per IS requests. I have a ticket in for a new VM and a new database to try to get this going. I am waiting on that before moving on. ## (/) Pat created the VM and Neil created the database. ## (/) I logged into auth.mbari.org (name of the VM) and downloaded crowd which I unzipped to the /opt directory ## (/) I then created a /data/crowd directory and gave my account permissions on it and then edited the /opt/atlassian..../crowd-webapp/WEB-INF/classes/crowd-init.properties file to set that as the crowd home directory. ## (/) The instructions say to download the JDBC driver, but they already have JTDS 1.2.7 in the download so I did not do anything. ## (/) You have to manually connect up CrowdID to a database as they setup wizard does not currently do this. ### (/) They say to download the driver, but again 1.2.7 was there so I did nothing. ### (/) I edited the /opt/atlassian.../apache-tomcat/conf/Catalina/localhost/openidserver.xml to look like: {noformat} {noformat} ### (/) I edited the /opt/atlassian.../build.properties files to look like: {noformat} # Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See https://confluence.atlassian.com/display/CROWD/Connecting+Crowd+to+a+Database hibernate.dialect=org.hibernate.dialect.SQLServerDialect # The Hibernate transaction factory to use. See https://confluence.atlassian.com/display/CROWD/Configuring+Crowd hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory # The http port you wish to run crowd from, ie: http://localhost:8095/crowd crowd.tomcat.connector.port=8095 # Tomcat requires a unique port for shutdown crowd.tomcat.shutdown.port=8020 # Crowd context root crowd.url=http://localhost:8095/crowd # Demo context root demo.url=http://localhost:8095/demo # OpenID server context root openidserver.url=http://localhost:8095/openidserver {noformat} ### (/) I then ran the build.sh script in the root of /opt/atlassian... ## (/) I fired up crowd using the /opt/atlassian.../start_crowd.sh script ## (/) I then went to http://auth.mbari.org:8095/crowd to kick off the start up wizard ## (/) I grabbed a new eval license from my account on atlassian and pasted into the license page. ## (/) I selected "New install" on the next page. ## (/) I configured the JDBC connection using this connection URL with user DB_Collaboration {noformat} jdbc:jtds:sqlserver://dione.mbari.org:51001/Crowd;domain=SHORE;useNTLMv2=TRUE {noformat} ## (/) I left the "Options" as they came up {warning:title=Paths} Not sure if this is a problem, but because I started the set up using auth.mbari.org, it set the Base URL to http://auth.mbari.org:8095/crowd instead of localhost. Hope that is not a problem. We will see. {warning} ## (/) I configured the email connection using the settings from [here|https://wind.shore.mbari.org/is/howto/email/mbarimail/imap] and I used my network login (probably shouldn't be doing that ... not sure where it stores my password, but I am assuming in the DB). ## (/) For the local admin account, I created a user named 'crowdadm' so it would not clash with my LDAP account. See Kevin Gomes for password information. ## (/) I checked the OpenID server as an integrated application ## (/) It then took me to the login page and I logged in using the newly minted admin account. Seemed all is well so far. ## (/) I visited the openidserver URL as well and that seemed OK. ## (/) I decided to wait on configuring the MBARI LDAP directory until I got everything with SSL working. ## (/) Now the next step was to follow the directions to configure Crowd to run over SSL found [here|https://confluence.atlassian.com/display/CROWD/Configuring+Crowd+to+Work+with+SSL] ## (/) I shutdown crowd. Note that the stop script does not shutdown things correctly and I noticed the crowd app running as root. That should not be if I started as kgomes. Not sure what is up with that. ## (/) Now Joe had already configured SSL once, so I used his connector configuration in the server.xml file and so the final file looked like: {noformat} {noformat} ## (/) I then edited the /data/crowd/crowd.properties to look like: {noformat} #Sat Aug 01 09:05:15 PDT 2015 session.lastvalidation=session.lastvalidation session.tokenkey=session.tokenkey crowd.server.url=https\://localhost\:8443/crowd/services/ application.name=crowd http.timeout=30000 session.isauthenticated=session.isauthenticated application.login.url=https\://localhost\:8443/crowd/console/ session.validationinterval=0 application.password=Y1Xp3OorCmsOP4eruL1dmH {noformat} One thing to note here is that based on a comment from the SSL configuration page at atlassian (Steve's comment), you are supposed to leave all the host names the same. For example, if the file says localhost, leave it localhost. So this created a bit of a problem based on the fact that I had left the base URL pointing to auth.mbari.org in the wizard steps above. That step wrote auth.mbari.org to the /data/crowd/crowd.properties. All the other files reference localhost, so to be consistent, I changed auth.mbari.org to localhost in the /data/crowd/crowd.properties file. We will see if this works. ## (/) Per the instructions on the atlassian page (referenced above), I also edited the build.properties file and the /client/conf/crowd.properties files before I restarted and used the SSL URLs ## build.properties: {noformat} # Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See https://confluence.atlassian.com/display/CROWD/Connecting+Crowd+to+a+Database hibernate.dialect=org.hibernate.dialect.SQLServerDialect # The Hibernate transaction factory to use. See https://confluence.atlassian.com/display/CROWD/Configuring+Crowd hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory # The http port you wish to run crowd from, ie: http://localhost:8095/crowd crowd.tomcat.connector.port=8095 # Tomcat requires a unique port for shutdown crowd.tomcat.shutdown.port=8020 # Crowd context root crowd.url=https://localhost:8443/crowd # Demo context root demo.url=https://localhost:8443/demo # OpenID server context root openidserver.url=https://localhost:8443/openidserver {noformat} ## crowd.properties (client) {noformat} application.name crowd application.password password application.login.url https://localhost:8443/crowd/console/ crowd.server.url https://localhost:8443/crowd/services/ crowd.base.url https://localhost:8443/crowd/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 2 session.lastvalidation session.lastvalidation {noformat} ## (/) Although not stated, I am assuming you would need to run the build.sh script to push the build.properties changes to their proper places, so I did that. Note that before doing that, I know that it will clobber the server.xml changes I made, so I made a copy of that file and diff'd them after and then rolled the previous changes to the new server.xml file. Actually, amazingly enough, it seems to have done the connector entry correctly so I left it after running the build.sh script. ## (/) Crossed my fingers and then restarted crowd. I tailed the catalina.out file and did not see any stack traces so that is a good sign! ## (/) I visited https://auth.mbari.org:8443/crowd first. It could not find that page, but I suspect that is because I am browsing from the outside, so I tried just https://auth.mbari.org/crowd and got a service unavailable. I am suspecting that this is a combination of firewall and proxy pass and I will send this info to Joe. From what I can see on the crowd side, it seems like the server started cleanly, we just can't get to it. I tried to reach it from a browser on the machine itself too (through VNC) with the same service not available. ## (/) Here are the notes from Joe after he fixed it! Wooohooo! {noformat} Hey Kevin, Thanks for starting clean! I had to make a few adjustments. 1-I modified the server.xml file in /opt/atlassian-crowd-2.8.3/apache-tomcat/conf/server.xml so there are two connectors per the instructions on the Atlassian site. I have backed up this good server.xml file in /etc/temp/ if you want to browse it to see what I did. Of note is that I removed all the jargon referencing the types of ciphers available to simplify things for now. 2-I modified /data/crowd/crowd.properties to have crowd.server.url=https\://localhost\:8443/crowd/services/ application.login.url=https\://localhost\:8443/crowd/console/ But that would cause my login to error with an error saying it was unable to reach the authentication server. I scratched my head for a bit. When I revert the values to just using non-SSL and try to log in, I just get an "invalid login" (I don't know the crowdadm password). So I worked under the assumption that if I can configure SSL to get an "invalid login" when logging in then it would work when provided real credentials. So, I then changed /data/crowd/crowd.proprties to: crowd.server.url=https\://auth.mbari.org\:8443/crowd/services/ application.login.url=https\://auth.mbari.org\:8443/crowd/console/ And now when I try to log in with SSL it says "invalid login". Strange because all the other values I can find only show "localhost" .. in any case... Can you try to log in now? {noformat} ## (/) Next I moved on to configuring the connection to MBARI's LDAP server to enable our logins through Crowd and CrowdID ## (/) I clicked on "Add Directory" in crowd. ## (/) I selected "Connector" then clicked Next ## (/) I put ldap.shore.mbari.org as the name of the server ## (/) I selected "Use memberOf for group memberships" ## (/) I used "OU=AllUsers,DC=shore,DC=mbari,DC=org" for the Base DN ## (/) I used "CN=LDAPbind,OU=Special,OU=AllUsers,DC=shore,DC=mbari,DC=org" for the Username (talk to Pat Allen for password) ## (/) I tested the connection (button click) and it passed. ## (/) I de-selected all the capabilities of the connector as it is a ready only connector and then saved it. It synchronized correctly! ## (/) At first, I could not login using my MBARI credentials, but after going to the "crowd" application in crowd (logged in as the local admin), I had to add the LDAP directory and configure it to "Allow all to authenticate", then I was able to login. After this, the last step was to get this to run as a different user and lock down various directories. I went through the entire directory structure /opt/atlassian... and set up so that root owned all read-only locations and DB_Collaboration (account set up by IS) owned the other stuff. I also gave full ownership to the /data/crowd directory to DB_Collaboration so it could write there. Pat set up a script to start on boot and after a little tweaking, it now starts on boot. {warning:title=CrowdID log file} One thing that came up here was that when the crowdID application ran, it tried to write a log file to the location where the process was launched from (which is /opt/atlassian...). This is a bad thing and I figured out that I could change that location by changing the file /opt/atlassian-crowd-2.8.3/crowd-openidserver-webapp/WEB-INF/classes/log4j.properties and hardcoding the /data/crowd/logs/atlassian-crowd-openid-server.log and then restarted the application. {warning} ## (/) Another note is the when an application tried to use the OpenID application, it would get redirected to localhost. I changed the /opt/atlassian.../crowd-openidserver-webapp/WEB-INF/classes/crowd.properties file to look like: {noformat} #Sat Aug 01 10:03:18 PDT 2015 session.lastvalidation=session.lastvalidation session.tokenkey=session.tokenkey crowd.server.url=http\://localhost\:8095/crowd/services/ application.name=crowd-openid-server #application.login.url.template=http\://localhost\:8095/openidserver?returnToUrl\=${RETURN_TO_URL} application.login.url.template=https\://auth.mbari.org/openidserver?returnToUrl\=${RETURN_TO_URL} session.isauthenticated=session.isauthenticated #application.base.url=http\://localhost\:8095/openidserver application.base.url=https\://auth.mbari.org/openidserver #application.login.url=http\://localhost\:8095/openidserver application.login.url=https\://auth.mbari.org/openidserver session.validationinterval=0 application.password=password {noformat} and that seems to have fixed it. # (/) It is finally time to move on to the version 4 upgrade ... holy crap. I first went to the *new* crowd install (auth.mbari.org) and logged in as the crowdadm. # (/) I clicked on Applications, then on Add Application # (/) I selected JIRA from the Application type drop-down # (/) I entered jira445 as the username. Ask Kevin about the password. # (/) I used http://bugs.shore.mbari.org:8081 as the URL # (/) I used 134.89.12.31 as the IP address. # (/) I selected only the MBARI LDAP directory. # (/) Then I selected "Allow all users to authenticate" # (/) Then I clicked on "Add Application" # (/) I VNC'd into bugs.mbari.org. As it turns out, for Linux, there is an installer program to download. I downloaded the .bin for 64 bit Linux installer and moved it to the jira-upgrade directory. # (/) I chmod'd the file to make it executable and ran it. It gave me a warning about not being root, but I went ahead with it. # (/) It asked for the JIRA home and data directory, which I specified as /opt/jira4 and /data/jira445. # (/) For the ports, I specified 8180 and 8105 (HTTP and control respectively). It then extracted all the files and launched JIRA. It said if finished, so I opened a local browser to http://localhost:8180 which kicked off the start up wizard. # (/) I specified the external database using: ## solstice2.shore.mbari.org (server) ## 1433 (port) ## jira4 (database) ## DB_Collaboration (username) ## (password ask Kevin) ## dbo (schema) # But all this failed as it seems to just want to try and use the SQL server authentication instead of domain. I will have to do it manually. # (/) I stopped the server using the bin/stop-jira.sh script. # (/) I created and edited /data/jira445/dbconfig.xml and made it look like the following: {noformat} ?xml version="1.0" encoding="UTF-8"?> defaultDS default mssql jiraschema jdbc:jtds:sqlserver://solstice2.shore.mbari.org:1433/Jira4;domain=SHORE;useNTLMv2=true net.sourceforge.jtds.jdbc.Driver DB_Collaboration (ask Kevin) 15 {noformat} # (/) I then started it again using bin/start-jira.sh and tailed the catalina.out file. Got a bunch of errors related to the schema 'jiraschema', I edited the file and changed the schema to 'dbo' and restarted. That seemed to do it. There was one stack trace for some iCal plugin, but looks OK other than that. # I browsed back to localhost:8180 and the wizard moved to step 2. There was an option to import existing data bit without the crowd connection, I thought I should set it up manually, connect to crowd, then import. I generated an evaluation license, called the app "MBARI JIRA4" and change the server in the url to bugs.shore.mbari.org # For the admin, I created an account called 'jiraadm' (ask Kevin for password). # Since this is a temporary system, I left the email system disabled. # I logged in as jiraadm, went to Administration, then Users, then clicked on Add Directory and chose Atlassian Crowd. Note that I had to set the server URL to http://auth.mbari.org:8095/crowd or I would have had to configure all this SSL crap that I did not want to do for this temporary install. # It tested successfully, I clicked Save and it went through a 13 second sync, whew! # I then went to System->Import and Export->Restore System # I copied the jira-upgrade-3.13.5.zip file from the previous version export into /data/jira445/import and then entered that file name along with the new evaluation license again.]]> 27558176 19073842 19041151 27590939 4.4: [https://confluence.atlassian.com/display/JIRA044/Migrating+JIRA+to+Another+Server] ## The JIRA configuration tool: [https://confluence.atlassian.com/display/JIRA044/Using+the+JIRA+Configuration+Tool] h5. Steps # (/) Create new VM named bugs.mbari.org in the DMZ # (/) Have Neil create database Jira_Temp on solstice2.shore.mbari.org # (/) Have Neil create database Jira on solstice2.shore.mbari.org # (/) Have Pat install Java 7 on bugs.shore.mbari.org # (/) Have Pete plumb holes through firewall so processes on bugs.mbari.org can get to Solstice2 # (/) Have Pat create DB_Collaboration account on bugs so it can run JIRA under that account and it can connect to solstice2 using that NT Domain account. # (/) Upgrade license on Atlassian site # (/) Log into bugs.shore.mbari.org # (/) Download 3.13.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 4.4.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 5.2.11 standalone Linux 64 bit tar.gz (not sure this version is necessary, but at least I have it) # (/) Unzip and untar the file to /opt # (/) Download latest JIRA (6.4.7 as of this writing). # (/) Unzip and untar it to /opt # Performed Test Upgrade ## (/) In order to export the current stuff in JIRA, I had to shut off access so people could not change the data while I was backing it up. ## (/) I ssh'd to oceana.mbari.org as root and edited the /opt/jira/conf/server.xml file and commented out the Connector section that had the port of 8010 to shut it off from the normal serving route. ## (/) I uncommented the 8082 port connector and the 8443 port connector so that I could still get to the server. ## (/) I stopped and started the JIRA server and in the log file I got a "keystore was tampered with..." which is not surprising. ## (/) I could then browser over to http://oceana.mbari.org:8082/jira ## (/) Then through the Administration console, I did an XML backup ## (/) I then created a tar of all the attachments in the /data/jira_3_12/attachments directory ## (/) I moved both the XML and tar files to the /root/jira-upgrade directory ## (/) I then reversed the changes to the server.xml file and shut down JIRA ## (/) I left it down during the next steps in case it went so well, I could just point people to the new server (yeah, right). ## (/) I then browsed to the crowd server on oceana and add a new application using: ### URL: http://bugs.mbari.org/jira3135 ### IP: 134.89.2.29 ### Name: JIRA3135 ### Password: (ask Kevin) :) ## (/) On bugs, I made a copy of the JIRA 3.13.5 download in the /opt directory and unzipped and untarred it. ## (/) In order to configure the crowd connection I did the following: ### (/) I scp'd the /opt/crowd/client/crowd-integration-client-1.6.jar file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I removed the existing 1.6.1 crowd client jar from the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I scp'd the /opt/crowd/client/conf/crowd.properties file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I scp'd the /opt/crowd/client/conf/crowd-ehcache.xml file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I edited the crowd.properties file on bugs to look like: {noformat} application.name JIRA3135 application.password (ask Kevin) application.login.url http://oceana.mbari.org:8095/crowd/console/ crowd.server.url http://oceana.mbari.org:8095/crowd/services/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 0 session.lastvalidation session.lastvalidation {noformat} ### (/) I edited the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/osuser.xml file to comment out the current authentication mechanism and then uncomment the crowd one. ## (/) I then edited the /opt/atlassian-jira-standalone-3.13.5/conf/server/xml file and configured the database connection to the Jira_Temp database on Solstice2. I looked like this: {noformat} {noformat} ## (/) Edit the /opt/atlassian/jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/entityengine.xml and changed it from 'hsql' to 'mssql' and delete the line with "PUBLIC" in it per the instructions in the comments in that file. ## (/) I edited the /etc/httpd/conf/httpd.conf file and created a proxy pass at the bottom of the file to point a normal URL to the default port 8080 for JIRA: {noformat} # Proxy Pass for JIRA ProxyPass http://bugs.mbari.org:8080 ProxyPassReverse http://bugs.mbari.org:8080 {noformat} ## (/) I restarted Apache ## (/) I scp'd the jtds driver from oceana to the /opt/atlassian-jira-standalone-3.13.5/common/lib directory (you could down from the internet) ## (/) I then went to the /opt/atlassian-jira-standalone-3.13.5/ directory and ran './bin/startup.sh'. From the log file, I could tell things were hanging. After some troubleshooting I am wondering if the local firewall is preventing the application to get access to the database on solstice2. I can telnet to port 1433, but I can't browse to the base http://bugs.mbari.org from anywhere but the local web browser. I have submitted a ticket. ## (/) I restarted the old JIRA with my hopes dashed :(. ## (/) Pat disabled the firewall on bugs.mbari.org but it still hung trying to connect to solstice2.shore.mbari.org. That is really, really perplexing. Neil mentioned that solstice2 is using Kerberos and solstice is not. Checking with the JTDS docs, version 1.3.1 of the driver added kerberos support, so I downloaded that driver and added the 'userKerberos=true' property to the URL in the server.xml file and restarted. Got an error about no credentials, so added user and password properties to the URL. Nope, no luck. Never did figure this one out, but I had Pat pull the VM inside the firewall and after some thrash it worked. Well, it sort of worked ... sigh. It turns out I had downloaded the standard version instead of the enterprise version. I need to redo this work ... grrr. ## (/) I deleted all the tables in the Jira_Temp database and removed the /data/jira3135/indexes directory (and recreated). ## (/) I downloaded the enterprise version of the 3.13.5 server. I made a copy in the /opt directory and unzipped and untarred the file. ## (/) I went back to crowd and edited the application to change the properties to: ### URL: http://bugs.shore.mbari.org:8080 ### IP: 134.89.12.31 ### Name: jira3135 ### Password: (ask Kevin) :) ## (/) I then repeated the steps above to get the server up and running with the following differences: ### The server name is now bugs.shore.mbari.org ### The paths given above are a little different in that they no longer say "standard" but say "enterprise" ### I deleted the proxy pass as it seemed to have issues before and this is only temporary anyway. ## (/) I then browsed to http://bugs.shore.mbari.org:8080 ## (/) It took me to the start up page and at the top was the option to 'import your existing data'. Seemed too good not to try. I clicked on the link. It asked me for the backup file location and the location where the indexes would be stored. ## (/) I copied the XML zip file and the attachments tar file to the /data/original directory. ## (/) I created the /data/jira3135/indexes and used those directories ... it fired off the import and I waited. ## (/) I tailed the log file to watch the import. Holy crap, it worked!!! I could log in and everything! I copied the results from the log file here for posterity sake: {noformat} 2015-07-22 20:55:45,156 http-8080-Processor22 INFO [jira.action.admin.DataImport] Running data import 2015-07-22 20:55:45,179 http-8080-Processor22 INFO [jira.action.admin.DataImport] Importing data.. 2015-07-22 20:55:45,186 http-8080-Processor22 INFO [jira.action.admin.DataImport] Start parsing XML with SAX Parser 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] XML successfully parsed 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] Removing all entries from the database. 2015-07-22 20:56:24,593 http-8080-Processor22 INFO [jira.action.admin.DataImport] All entries removed. 2015-07-22 20:56:24,594 http-8080-Processor22 INFO [jira.action.admin.DataImport] Started storing 410414 Generic Values 2015-07-22 21:01:51,967 http-8080-Processor22 INFO [jira.action.admin.DataImport] Finished storing Generic Values 2015-07-22 21:01:52,329 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:52,361 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:54,683 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLink' to module 'jira.user.format:profile-link-user-format'. 2015-07-22 21:01:54,724 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullName' to module 'jira.user.format:full-name-user-format'. 2015-07-22 21:01:54,773 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkSearcher' to module 'jira.user.format:profile-link-searcher-user-format'. 2015-07-22 21:01:54,784 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkExternal' to module 'jira.user.format:profile-link-external-user-format'. 2015-07-22 21:01:54,795 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkActionHeader' to module 'jira.user.format:profile-link-action-header-user-format'. 2015-07-22 21:01:54,807 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullProfile' to module 'jira.user.format:full-profile-user-format'. 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/comments 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/issues 2015-07-22 21:01:55,641 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/plugins 2015-07-22 21:01:55,867 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:01:55,871 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/issues does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:55,873 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/comments does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,033 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,257 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,889 http-8080-Processor22 ERROR [atlassian.jira.upgrade.ConsistencyCheckImpl] Attachments are turned on, but attachment path [/data/jira_3_12/attachments] invalid - disabling attachments 2015-07-22 21:02:13,904 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Detected that an upgrade is needed; existing data at build 299 2015-07-22 21:02:13,907 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Doing Upgrade... 2015-07-22 21:02:13,915 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value' succeeded 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 317 2015-07-22 21:02:13,944 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite filters - make each filter a favourite of its owner. 2015-07-22 21:02:17,822 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build319] Could not find author 'fpy' for filter with id '10040' 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite filters - make each filter a favourite of its owner.' succeeded 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 319 2015-07-22 21:02:17,995 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise Share Permissions. Move old shares to new shares. 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise Share Permissions. Move old shares to new shares.' succeeded 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 321 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Migrating the old JIRA UI colors to the new JIRA 3.13 colors 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build322] Custom color detected for jira.lf.menu.bgcolour : #336699 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Migrating the old JIRA UI colors to the new JIRA 3.13 colors' succeeded 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 322 2015-07-22 21:02:18,025 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite dashboards - make each dashboard a favourite of its owner. 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'cmcgann' for dashboard with id '10030' 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'fpy' for dashboard with id '10060' 2015-07-22 21:02:18,423 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'kanna' for dashboard with id '10040' 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite dashboards - make each dashboard a favourite of its owner.' succeeded 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 325 2015-07-22 21:02:18,625 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Reindexing all data in JIRA to include Favourites. 2015-07-22 21:02:18,648 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All starting... 2015-07-22 21:02:18,650 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 0% complete. Current index: Issue 2015-07-22 21:02:18,654 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:02:18,809 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 1% complete. Current index: Issue 2015-07-22 21:02:18,855 indexerPool-2-thread-10 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 2% complete. Current index: Issue 2015-07-22 21:02:18,899 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 3% complete. Current index: Issue 2015-07-22 21:02:18,945 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 4% complete. Current index: Issue 2015-07-22 21:02:19,012 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 5% complete. Current index: Issue . . . 2015-07-22 21:02:26,164 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 95% complete. Current index: Issue 2015-07-22 21:02:26,232 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 96% complete. Current index: Issue 2015-07-22 21:02:26,316 indexerPool-2-thread-9 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 97% complete. Current index: Issue 2015-07-22 21:02:26,771 indexerPool-2-thread-3 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: Issue 2015-07-22 21:02:27,261 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 8607ms. Indexer: DefaultIndexManager: paths: [/data/jira3135/indexes/issues, /data/jira3135/indexes/comments] 2015-07-22 21:02:27,263 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: SearchRequest 2015-07-22 21:02:27,268 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,293 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: SearchRequest 2015-07-22 21:02:27,308 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: PortalPage 2015-07-22 21:02:27,312 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,377 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: PortalPage 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 115ms. Indexer: SharedEntityIndexManager: paths: [/data/jira3135/indexes/entities/portalpage, /data/jira3135/indexes/entities/searchrequest] 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All complete. Total time: 8722ms. 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Reindexing all data in JIRA to include Favourites.' succeeded 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 326 2015-07-22 21:02:27,397 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade succeeded! Setting data build number to 360 2015-07-22 21:02:27,469 JiraQuartzScheduler_Worker-0 WARN [service.services.export.ExportService] Backup directory /data/jira_3_12/backup does not exist {noformat} {warning:title=Paths} It appears that the upgraded JIRA will still look for the attachments and the backup locations in the original places. So I created /data/jira_3_12/backup and untarred the original attachments to /data/jira_3_12 and then everything worked (including attachements) in the new JIRA. {warning} ## (/) I then used the upgraded JIRA to generate a new XML backup and stored it in /data/original/3.13.5 along with another tar of the files in /data/jira_3_12/attachments. ## (/) I then shutdown the JIRA server. *I should be ready to move on to version 4 upgrade WHEW* ## So, before moving on, I decided that it would be a really good idea to spin up a new Crowd instance to get rid of the :8443 in the URL and to move off of RedHat per IS requests. I have a ticket in for a new VM and a new database to try to get this going. I am waiting on that before moving on. ## (/) Pat created the VM and Neil created the database. ## (/) I logged into auth.mbari.org (name of the VM) and downloaded crowd which I unzipped to the /opt directory ## (/) I then created a /data/crowd directory and gave my account permissions on it and then edited the /opt/atlassian..../crowd-webapp/WEB-INF/classes/crowd-init.properties file to set that as the crowd home directory. ## (/) The instructions say to download the JDBC driver, but they already have JTDS 1.2.7 in the download so I did not do anything. ## (/) You have to manually connect up CrowdID to a database as they setup wizard does not currently do this. ### (/) They say to download the driver, but again 1.2.7 was there so I did nothing. ### (/) I edited the /opt/atlassian.../apache-tomcat/conf/Catalina/localhost/openidserver.xml to look like: {noformat} {noformat} ### (/) I edited the /opt/atlassian.../build.properties files to look like: {noformat} # Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See https://confluence.atlassian.com/display/CROWD/Connecting+Crowd+to+a+Database hibernate.dialect=org.hibernate.dialect.SQLServerDialect # The Hibernate transaction factory to use. See https://confluence.atlassian.com/display/CROWD/Configuring+Crowd hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory # The http port you wish to run crowd from, ie: http://localhost:8095/crowd crowd.tomcat.connector.port=8095 # Tomcat requires a unique port for shutdown crowd.tomcat.shutdown.port=8020 # Crowd context root crowd.url=http://localhost:8095/crowd # Demo context root demo.url=http://localhost:8095/demo # OpenID server context root openidserver.url=http://localhost:8095/openidserver {noformat} ### (/) I then ran the build.sh script in the root of /opt/atlassian... ## (/) I fired up crowd using the /opt/atlassian.../start_crowd.sh script ## (/) I then went to http://auth.mbari.org:8095/crowd to kick off the start up wizard ## (/) I grabbed a new eval license from my account on atlassian and pasted into the license page. ## (/) I selected "New install" on the next page. ## (/) I configured the JDBC connection using this connection URL with user DB_Collaboration {noformat} jdbc:jtds:sqlserver://dione.mbari.org:51001/Crowd;domain=SHORE;useNTLMv2=TRUE {noformat} ## (/) I left the "Options" as they came up {warning:title=Paths} Not sure if this is a problem, but because I started the set up using auth.mbari.org, it set the Base URL to http://auth.mbari.org:8095/crowd instead of localhost. Hope that is not a problem. We will see. {warning} ## (/) I configured the email connection using the settings from [here|https://wind.shore.mbari.org/is/howto/email/mbarimail/imap] and I used my network login (probably shouldn't be doing that ... not sure where it stores my password, but I am assuming in the DB). ## (/) For the local admin account, I created a user named 'crowdadm' so it would not clash with my LDAP account. See Kevin Gomes for password information. ## (/) I checked the OpenID server as an integrated application ## (/) It then took me to the login page and I logged in using the newly minted admin account. Seemed all is well so far. ## (/) I visited the openidserver URL as well and that seemed OK. ## (/) I decided to wait on configuring the MBARI LDAP directory until I got everything with SSL working. ## (/) Now the next step was to follow the directions to configure Crowd to run over SSL found [here|https://confluence.atlassian.com/display/CROWD/Configuring+Crowd+to+Work+with+SSL] ## (/) I shutdown crowd. Note that the stop script does not shutdown things correctly and I noticed the crowd app running as root. That should not be if I started as kgomes. Not sure what is up with that. ## (/) Now Joe had already configured SSL once, so I used his connector configuration in the server.xml file and so the final file looked like: {noformat} {noformat} ## (/) I then edited the /data/crowd/crowd.properties to look like: {noformat} #Sat Aug 01 09:05:15 PDT 2015 session.lastvalidation=session.lastvalidation session.tokenkey=session.tokenkey crowd.server.url=https\://localhost\:8443/crowd/services/ application.name=crowd http.timeout=30000 session.isauthenticated=session.isauthenticated application.login.url=https\://localhost\:8443/crowd/console/ session.validationinterval=0 application.password=Y1Xp3OorCmsOP4eruL1dmH {noformat} One thing to note here is that based on a comment from the SSL configuration page at atlassian (Steve's comment), you are supposed to leave all the host names the same. For example, if the file says localhost, leave it localhost. So this created a bit of a problem based on the fact that I had left the base URL pointing to auth.mbari.org in the wizard steps above. That step wrote auth.mbari.org to the /data/crowd/crowd.properties. All the other files reference localhost, so to be consistent, I changed auth.mbari.org to localhost in the /data/crowd/crowd.properties file. We will see if this works. ## (/) Per the instructions on the atlassian page (referenced above), I also edited the build.properties file and the /client/conf/crowd.properties files before I restarted and used the SSL URLs ## build.properties: {noformat} # Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See https://confluence.atlassian.com/display/CROWD/Connecting+Crowd+to+a+Database hibernate.dialect=org.hibernate.dialect.SQLServerDialect # The Hibernate transaction factory to use. See https://confluence.atlassian.com/display/CROWD/Configuring+Crowd hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory # The http port you wish to run crowd from, ie: http://localhost:8095/crowd crowd.tomcat.connector.port=8095 # Tomcat requires a unique port for shutdown crowd.tomcat.shutdown.port=8020 # Crowd context root crowd.url=https://localhost:8443/crowd # Demo context root demo.url=https://localhost:8443/demo # OpenID server context root openidserver.url=https://localhost:8443/openidserver {noformat} ## crowd.properties (client) {noformat} application.name crowd application.password password application.login.url https://localhost:8443/crowd/console/ crowd.server.url https://localhost:8443/crowd/services/ crowd.base.url https://localhost:8443/crowd/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 2 session.lastvalidation session.lastvalidation {noformat} ## (/) Although not stated, I am assuming you would need to run the build.sh script to push the build.properties changes to their proper places, so I did that. Note that before doing that, I know that it will clobber the server.xml changes I made, so I made a copy of that file and diff'd them after and then rolled the previous changes to the new server.xml file. Actually, amazingly enough, it seems to have done the connector entry correctly so I left it after running the build.sh script. ## (/) Crossed my fingers and then restarted crowd. I tailed the catalina.out file and did not see any stack traces so that is a good sign! ## (/) I visited https://auth.mbari.org:8443/crowd first. It could not find that page, but I suspect that is because I am browsing from the outside, so I tried just https://auth.mbari.org/crowd and got a service unavailable. I am suspecting that this is a combination of firewall and proxy pass and I will send this info to Joe. From what I can see on the crowd side, it seems like the server started cleanly, we just can't get to it. I tried to reach it from a browser on the machine itself too (through VNC) with the same service not available. ## (/) Here are the notes from Joe after he fixed it! Wooohooo! {noformat} Hey Kevin, Thanks for starting clean! I had to make a few adjustments. 1-I modified the server.xml file in /opt/atlassian-crowd-2.8.3/apache-tomcat/conf/server.xml so there are two connectors per the instructions on the Atlassian site. I have backed up this good server.xml file in /etc/temp/ if you want to browse it to see what I did. Of note is that I removed all the jargon referencing the types of ciphers available to simplify things for now. 2-I modified /data/crowd/crowd.properties to have crowd.server.url=https\://localhost\:8443/crowd/services/ application.login.url=https\://localhost\:8443/crowd/console/ But that would cause my login to error with an error saying it was unable to reach the authentication server. I scratched my head for a bit. When I revert the values to just using non-SSL and try to log in, I just get an "invalid login" (I don't know the crowdadm password). So I worked under the assumption that if I can configure SSL to get an "invalid login" when logging in then it would work when provided real credentials. So, I then changed /data/crowd/crowd.proprties to: crowd.server.url=https\://auth.mbari.org\:8443/crowd/services/ application.login.url=https\://auth.mbari.org\:8443/crowd/console/ And now when I try to log in with SSL it says "invalid login". Strange because all the other values I can find only show "localhost" .. in any case... Can you try to log in now? {noformat} ## (/) Next I moved on to configuring the connection to MBARI's LDAP server to enable our logins through Crowd and CrowdID ## (/) I clicked on "Add Directory" in crowd. ## (/) I selected "Connector" then clicked Next ## (/) I put ldap.shore.mbari.org as the name of the server ## (/) I selected "Use memberOf for group memberships" ## (/) I used "OU=AllUsers,DC=shore,DC=mbari,DC=org" for the Base DN ## (/) I used "CN=LDAPbind,OU=Special,OU=AllUsers,DC=shore,DC=mbari,DC=org" for the Username (talk to Pat Allen for password) ## (/) I tested the connection (button click) and it passed. ## (/) I de-selected all the capabilities of the connector as it is a ready only connector and then saved it. It synchronized correctly! ## (/) At first, I could not login using my MBARI credentials, but after going to the "crowd" application in crowd (logged in as the local admin), I had to add the LDAP directory and configure it to "Allow all to authenticate", then I was able to login. After this, the last step was to get this to run as a different user and lock down various directories. I went through the entire directory structure /opt/atlassian... and set up so that root owned all read-only locations and DB_Collaboration (account set up by IS) owned the other stuff. I also gave full ownership to the /data/crowd directory to DB_Collaboration so it could write there. Pat set up a script to start on boot and after a little tweaking, it now starts on boot. {warning:title=CrowdID log file} One thing that came up here was that when the crowdID application ran, it tried to write a log file to the location where the process was launched from (which is /opt/atlassian...). This is a bad thing and I figured out that I could change that location by changing the file /opt/atlassian-crowd-2.8.3/crowd-openidserver-webapp/WEB-INF/classes/log4j.properties and hardcoding the /data/crowd/logs/atlassian-crowd-openid-server.log and then restarted the application. {warning} ## (/) Another note is the when an application tried to use the OpenID application, it would get redirected to localhost. I changed the /opt/atlassian.../crowd-openidserver-webapp/WEB-INF/classes/crowd.properties file to look like: {noformat} #Sat Aug 01 10:03:18 PDT 2015 session.lastvalidation=session.lastvalidation session.tokenkey=session.tokenkey crowd.server.url=http\://localhost\:8095/crowd/services/ application.name=crowd-openid-server #application.login.url.template=http\://localhost\:8095/openidserver?returnToUrl\=${RETURN_TO_URL} application.login.url.template=https\://auth.mbari.org/openidserver?returnToUrl\=${RETURN_TO_URL} session.isauthenticated=session.isauthenticated #application.base.url=http\://localhost\:8095/openidserver application.base.url=https\://auth.mbari.org/openidserver #application.login.url=http\://localhost\:8095/openidserver application.login.url=https\://auth.mbari.org/openidserver session.validationinterval=0 application.password=password {noformat} and that seems to have fixed it. # (/) It is finally time to move on to the version 4 upgrade ... holy crap. I first went to the *new* crowd install (auth.mbari.org) and logged in as the crowdadm. # (/) I clicked on Applications, then on Add Application # (/) I selected JIRA from the Application type drop-down # (/) I entered jira445 as the username. Ask Kevin about the password. # (/) I used http://bugs.shore.mbari.org:8081 as the URL # (/) I used 134.89.12.31 as the IP address. # (/) I selected only the MBARI LDAP directory. # (/) Then I selected "Allow all users to authenticate" # (/) Then I clicked on "Add Application" # (/) I VNC'd into bugs.mbari.org. As it turns out, for Linux, there is an installer program to download. I downloaded the .bin for 64 bit Linux installer and moved it to the jira-upgrade directory. # (/) I chmod'd the file to make it executable and ran it. It gave me a warning about not being root, but I went ahead with it. # (/) It asked for the JIRA home and data directory, which I specified as /opt/jira4 and /data/jira445. # (/) For the ports, I specified 8180 and 8105 (HTTP and control respectively). It then extracted all the files and launched JIRA. It said if finished, so I opened a local browser to http://localhost:8180 which kicked off the start up wizard. # (/) I specified the external database using: ## solstice2.shore.mbari.org (server) ## 1433 (port) ## jira4 (database) ## DB_Collaboration (username) ## (password ask Kevin) ## dbo (schema) # But all this failed as it seems to just want to try and use the SQL server authentication instead of domain. I will have to do it manually. # (/) I stopped the server using the bin/stop-jira.sh script. # (/) I created and edited /data/jira445/dbconfig.xml and made it look like the following: {noformat} ?xml version="1.0" encoding="UTF-8"?> defaultDS default mssql jiraschema jdbc:jtds:sqlserver://solstice2.shore.mbari.org:1433/Jira4;domain=SHORE;useNTLMv2=true net.sourceforge.jtds.jdbc.Driver DB_Collaboration (ask Kevin) 15 {noformat} # (/) I then started it again using bin/start-jira.sh and tailed the catalina.out file. Got a bunch of errors related to the schema 'jiraschema', I edited the file and changed the schema to 'dbo' and restarted. That seemed to do it. There was one stack trace for some iCal plugin, but looks OK other than that. # I browsed back to localhost:8180 and the wizard moved to step 2. There was an option to import existing data bit without the crowd connection, I thought I should set it up manually, connect to crowd, then import. I generated an evaluation license, called the app "MBARI JIRA4" and change the server in the url to bugs.shore.mbari.org # For the admin, I created an account called 'jiraadm' (ask Kevin for password). # Since this is a temporary system, I left the email system disabled. # I logged in as jiraadm, went to Administration, then Users, then clicked on Add Directory and chose Atlassian Crowd. Note that I had to set the server URL to http://auth.mbari.org:8095/crowd or I would have had to configure all this SSL crap that I did not want to do for this temporary install. # It tested successfully, I clicked Save and it went through a 13 second sync, whew! ]]> 27558175 27590946 4.4: [https://confluence.atlassian.com/display/JIRA044/Migrating+JIRA+to+Another+Server] ## The JIRA configuration tool: [https://confluence.atlassian.com/display/JIRA044/Using+the+JIRA+Configuration+Tool] h5. Steps # (/) Create new VM named bugs.mbari.org in the DMZ # (/) Have Neil create database Jira_Temp on solstice2.shore.mbari.org # (/) Have Neil create database Jira on solstice2.shore.mbari.org # (/) Have Pat install Java 7 on bugs.shore.mbari.org # (/) Have Pete plumb holes through firewall so processes on bugs.mbari.org can get to Solstice2 # (/) Have Pat create DB_Collaboration account on bugs so it can run JIRA under that account and it can connect to solstice2 using that NT Domain account. # (/) Upgrade license on Atlassian site # (/) Log into bugs.shore.mbari.org # (/) Download 3.13.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 4.4.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 5.2.11 standalone Linux 64 bit tar.gz (not sure this version is necessary, but at least I have it) # (/) Unzip and untar the file to /opt # (/) Download latest JIRA (6.4.7 as of this writing). # (/) Unzip and untar it to /opt # Performed Test Upgrade ## (/) In order to export the current stuff in JIRA, I had to shut off access so people could not change the data while I was backing it up. ## (/) I ssh'd to oceana.mbari.org as root and edited the /opt/jira/conf/server.xml file and commented out the Connector section that had the port of 8010 to shut it off from the normal serving route. ## (/) I uncommented the 8082 port connector and the 8443 port connector so that I could still get to the server. ## (/) I stopped and started the JIRA server and in the log file I got a "keystore was tampered with..." which is not surprising. ## (/) I could then browser over to http://oceana.mbari.org:8082/jira ## (/) Then through the Administration console, I did an XML backup ## (/) I then created a tar of all the attachments in the /data/jira_3_12/attachments directory ## (/) I moved both the XML and tar files to the /root/jira-upgrade directory ## (/) I then reversed the changes to the server.xml file and shut down JIRA ## (/) I left it down during the next steps in case it went so well, I could just point people to the new server (yeah, right). ## (/) I then browsed to the crowd server on oceana and add a new application using: ### URL: http://bugs.mbari.org/jira3135 ### IP: 134.89.2.29 ### Name: JIRA3135 ### Password: (ask Kevin) :) ## (/) On bugs, I made a copy of the JIRA 3.13.5 download in the /opt directory and unzipped and untarred it. ## (/) In order to configure the crowd connection I did the following: ### (/) I scp'd the /opt/crowd/client/crowd-integration-client-1.6.jar file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I removed the existing 1.6.1 crowd client jar from the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I scp'd the /opt/crowd/client/conf/crowd.properties file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I scp'd the /opt/crowd/client/conf/crowd-ehcache.xml file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I edited the crowd.properties file on bugs to look like: {noformat} application.name JIRA3135 application.password (ask Kevin) application.login.url http://oceana.mbari.org:8095/crowd/console/ crowd.server.url http://oceana.mbari.org:8095/crowd/services/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 0 session.lastvalidation session.lastvalidation {noformat} ### (/) I edited the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/osuser.xml file to comment out the current authentication mechanism and then uncomment the crowd one. ## (/) I then edited the /opt/atlassian-jira-standalone-3.13.5/conf/server/xml file and configured the database connection to the Jira_Temp database on Solstice2. I looked like this: {noformat} {noformat} ## (/) Edit the /opt/atlassian/jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/entityengine.xml and changed it from 'hsql' to 'mssql' and delete the line with "PUBLIC" in it per the instructions in the comments in that file. ## (/) I edited the /etc/httpd/conf/httpd.conf file and created a proxy pass at the bottom of the file to point a normal URL to the default port 8080 for JIRA: {noformat} # Proxy Pass for JIRA ProxyPass http://bugs.mbari.org:8080 ProxyPassReverse http://bugs.mbari.org:8080 {noformat} ## (/) I restarted Apache ## (/) I scp'd the jtds driver from oceana to the /opt/atlassian-jira-standalone-3.13.5/common/lib directory (you could down from the internet) ## (/) I then went to the /opt/atlassian-jira-standalone-3.13.5/ directory and ran './bin/startup.sh'. From the log file, I could tell things were hanging. After some troubleshooting I am wondering if the local firewall is preventing the application to get access to the database on solstice2. I can telnet to port 1433, but I can't browse to the base http://bugs.mbari.org from anywhere but the local web browser. I have submitted a ticket. ## (/) I restarted the old JIRA with my hopes dashed :(. ## (/) Pat disabled the firewall on bugs.mbari.org but it still hung trying to connect to solstice2.shore.mbari.org. That is really, really perplexing. Neil mentioned that solstice2 is using Kerberos and solstice is not. Checking with the JTDS docs, version 1.3.1 of the driver added kerberos support, so I downloaded that driver and added the 'userKerberos=true' property to the URL in the server.xml file and restarted. Got an error about no credentials, so added user and password properties to the URL. Nope, no luck. Never did figure this one out, but I had Pat pull the VM inside the firewall and after some thrash it worked. Well, it sort of worked ... sigh. It turns out I had downloaded the standard version instead of the enterprise version. I need to redo this work ... grrr. ## (/) I deleted all the tables in the Jira_Temp database and removed the /data/jira3135/indexes directory (and recreated). ## (/) I downloaded the enterprise version of the 3.13.5 server. I made a copy in the /opt directory and unzipped and untarred the file. ## (/) I went back to crowd and edited the application to change the properties to: ### URL: http://bugs.shore.mbari.org:8080 ### IP: 134.89.12.31 ### Name: jira3135 ### Password: (ask Kevin) :) ## (/) I then repeated the steps above to get the server up and running with the following differences: ### The server name is now bugs.shore.mbari.org ### The paths given above are a little different in that they no longer say "standard" but say "enterprise" ### I deleted the proxy pass as it seemed to have issues before and this is only temporary anyway. ## (/) I then browsed to http://bugs.shore.mbari.org:8080 ## (/) It took me to the start up page and at the top was the option to 'import your existing data'. Seemed too good not to try. I clicked on the link. It asked me for the backup file location and the location where the indexes would be stored. ## (/) I copied the XML zip file and the attachments tar file to the /data/original directory. ## (/) I created the /data/jira3135/indexes and used those directories ... it fired off the import and I waited. ## (/) I tailed the log file to watch the import. Holy crap, it worked!!! I could log in and everything! I copied the results from the log file here for posterity sake: {noformat} 2015-07-22 20:55:45,156 http-8080-Processor22 INFO [jira.action.admin.DataImport] Running data import 2015-07-22 20:55:45,179 http-8080-Processor22 INFO [jira.action.admin.DataImport] Importing data.. 2015-07-22 20:55:45,186 http-8080-Processor22 INFO [jira.action.admin.DataImport] Start parsing XML with SAX Parser 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] XML successfully parsed 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] Removing all entries from the database. 2015-07-22 20:56:24,593 http-8080-Processor22 INFO [jira.action.admin.DataImport] All entries removed. 2015-07-22 20:56:24,594 http-8080-Processor22 INFO [jira.action.admin.DataImport] Started storing 410414 Generic Values 2015-07-22 21:01:51,967 http-8080-Processor22 INFO [jira.action.admin.DataImport] Finished storing Generic Values 2015-07-22 21:01:52,329 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:52,361 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:54,683 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLink' to module 'jira.user.format:profile-link-user-format'. 2015-07-22 21:01:54,724 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullName' to module 'jira.user.format:full-name-user-format'. 2015-07-22 21:01:54,773 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkSearcher' to module 'jira.user.format:profile-link-searcher-user-format'. 2015-07-22 21:01:54,784 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkExternal' to module 'jira.user.format:profile-link-external-user-format'. 2015-07-22 21:01:54,795 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkActionHeader' to module 'jira.user.format:profile-link-action-header-user-format'. 2015-07-22 21:01:54,807 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullProfile' to module 'jira.user.format:full-profile-user-format'. 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/comments 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/issues 2015-07-22 21:01:55,641 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/plugins 2015-07-22 21:01:55,867 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:01:55,871 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/issues does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:55,873 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/comments does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,033 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,257 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,889 http-8080-Processor22 ERROR [atlassian.jira.upgrade.ConsistencyCheckImpl] Attachments are turned on, but attachment path [/data/jira_3_12/attachments] invalid - disabling attachments 2015-07-22 21:02:13,904 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Detected that an upgrade is needed; existing data at build 299 2015-07-22 21:02:13,907 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Doing Upgrade... 2015-07-22 21:02:13,915 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value' succeeded 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 317 2015-07-22 21:02:13,944 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite filters - make each filter a favourite of its owner. 2015-07-22 21:02:17,822 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build319] Could not find author 'fpy' for filter with id '10040' 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite filters - make each filter a favourite of its owner.' succeeded 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 319 2015-07-22 21:02:17,995 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise Share Permissions. Move old shares to new shares. 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise Share Permissions. Move old shares to new shares.' succeeded 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 321 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Migrating the old JIRA UI colors to the new JIRA 3.13 colors 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build322] Custom color detected for jira.lf.menu.bgcolour : #336699 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Migrating the old JIRA UI colors to the new JIRA 3.13 colors' succeeded 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 322 2015-07-22 21:02:18,025 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite dashboards - make each dashboard a favourite of its owner. 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'cmcgann' for dashboard with id '10030' 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'fpy' for dashboard with id '10060' 2015-07-22 21:02:18,423 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'kanna' for dashboard with id '10040' 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite dashboards - make each dashboard a favourite of its owner.' succeeded 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 325 2015-07-22 21:02:18,625 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Reindexing all data in JIRA to include Favourites. 2015-07-22 21:02:18,648 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All starting... 2015-07-22 21:02:18,650 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 0% complete. Current index: Issue 2015-07-22 21:02:18,654 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:02:18,809 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 1% complete. Current index: Issue 2015-07-22 21:02:18,855 indexerPool-2-thread-10 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 2% complete. Current index: Issue 2015-07-22 21:02:18,899 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 3% complete. Current index: Issue 2015-07-22 21:02:18,945 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 4% complete. Current index: Issue 2015-07-22 21:02:19,012 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 5% complete. Current index: Issue . . . 2015-07-22 21:02:26,164 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 95% complete. Current index: Issue 2015-07-22 21:02:26,232 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 96% complete. Current index: Issue 2015-07-22 21:02:26,316 indexerPool-2-thread-9 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 97% complete. Current index: Issue 2015-07-22 21:02:26,771 indexerPool-2-thread-3 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: Issue 2015-07-22 21:02:27,261 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 8607ms. Indexer: DefaultIndexManager: paths: [/data/jira3135/indexes/issues, /data/jira3135/indexes/comments] 2015-07-22 21:02:27,263 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: SearchRequest 2015-07-22 21:02:27,268 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,293 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: SearchRequest 2015-07-22 21:02:27,308 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: PortalPage 2015-07-22 21:02:27,312 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,377 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: PortalPage 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 115ms. Indexer: SharedEntityIndexManager: paths: [/data/jira3135/indexes/entities/portalpage, /data/jira3135/indexes/entities/searchrequest] 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All complete. Total time: 8722ms. 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Reindexing all data in JIRA to include Favourites.' succeeded 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 326 2015-07-22 21:02:27,397 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade succeeded! Setting data build number to 360 2015-07-22 21:02:27,469 JiraQuartzScheduler_Worker-0 WARN [service.services.export.ExportService] Backup directory /data/jira_3_12/backup does not exist {noformat} {warning:title=Paths} It appears that the upgraded JIRA will still look for the attachments and the backup locations in the original places. So I created /data/jira_3_12/backup and untarred the original attachments to /data/jira_3_12 and then everything worked (including attachements) in the new JIRA. {warning} ## (/) I then used the upgraded JIRA to generate a new XML backup and stored it in /data/original/3.13.5 along with another tar of the files in /data/jira_3_12/attachments. ## (/) I then shutdown the JIRA server. *I should be ready to move on to version 4 upgrade WHEW* ## So, before moving on, I decided that it would be a really good idea to spin up a new Crowd instance to get rid of the :8443 in the URL and to move off of RedHat per IS requests. I have a ticket in for a new VM and a new database to try to get this going. I am waiting on that before moving on. ## (/) Pat created the VM and Neil created the database. ## (/) I logged into auth.mbari.org (name of the VM) and downloaded crowd which I unzipped to the /opt directory ## (/) I then created a /data/crowd directory and gave my account permissions on it and then edited the /opt/atlassian..../crowd-webapp/WEB-INF/classes/crowd-init.properties file to set that as the crowd home directory. ## (/) The instructions say to download the JDBC driver, but they already have JTDS 1.2.7 in the download so I did not do anything. ## (/) You have to manually connect up CrowdID to a database as they setup wizard does not currently do this. ### (/) They say to download the driver, but again 1.2.7 was there so I did nothing. ### (/) I edited the /opt/atlassian.../apache-tomcat/conf/Catalina/localhost/openidserver.xml to look like: {noformat} {noformat} ### (/) I edited the /opt/atlassian.../build.properties files to look like: {noformat} # Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See https://confluence.atlassian.com/display/CROWD/Connecting+Crowd+to+a+Database hibernate.dialect=org.hibernate.dialect.SQLServerDialect # The Hibernate transaction factory to use. See https://confluence.atlassian.com/display/CROWD/Configuring+Crowd hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory # The http port you wish to run crowd from, ie: http://localhost:8095/crowd crowd.tomcat.connector.port=8095 # Tomcat requires a unique port for shutdown crowd.tomcat.shutdown.port=8020 # Crowd context root crowd.url=http://localhost:8095/crowd # Demo context root demo.url=http://localhost:8095/demo # OpenID server context root openidserver.url=http://localhost:8095/openidserver {noformat} ### (/) I then ran the build.sh script in the root of /opt/atlassian... ## (/) I fired up crowd using the /opt/atlassian.../start_crowd.sh script ## (/) I then went to http://auth.mbari.org:8095/crowd to kick off the start up wizard ## (/) I grabbed a new eval license from my account on atlassian and pasted into the license page. ## (/) I selected "New install" on the next page. ## (/) I configured the JDBC connection using this connection URL with user DB_Collaboration {noformat} jdbc:jtds:sqlserver://dione.mbari.org:51001/Crowd;domain=SHORE;useNTLMv2=TRUE {noformat} ## (/) I left the "Options" as they came up {warning:title=Paths} Not sure if this is a problem, but because I started the set up using auth.mbari.org, it set the Base URL to http://auth.mbari.org:8095/crowd instead of localhost. Hope that is not a problem. We will see. {warning} ## (/) I configured the email connection using the settings from [here|https://wind.shore.mbari.org/is/howto/email/mbarimail/imap] and I used my network login (probably shouldn't be doing that ... not sure where it stores my password, but I am assuming in the DB). ## (/) For the local admin account, I created a user named 'crowdadm' so it would not clash with my LDAP account. See Kevin Gomes for password information. ## (/) I checked the OpenID server as an integrated application ## (/) It then took me to the login page and I logged in using the newly minted admin account. Seemed all is well so far. ## (/) I visited the openidserver URL as well and that seemed OK. ## (/) I decided to wait on configuring the MBARI LDAP directory until I got everything with SSL working. ## (/) Now the next step was to follow the directions to configure Crowd to run over SSL found [here|https://confluence.atlassian.com/display/CROWD/Configuring+Crowd+to+Work+with+SSL] ## (/) I shutdown crowd. Note that the stop script does not shutdown things correctly and I noticed the crowd app running as root. That should not be if I started as kgomes. Not sure what is up with that. ## (/) Now Joe had already configured SSL once, so I used his connector configuration in the server.xml file and so the final file looked like: {noformat} {noformat} ## (/) I then edited the /data/crowd/crowd.properties to look like: {noformat} #Sat Aug 01 09:05:15 PDT 2015 session.lastvalidation=session.lastvalidation session.tokenkey=session.tokenkey crowd.server.url=https\://localhost\:8443/crowd/services/ application.name=crowd http.timeout=30000 session.isauthenticated=session.isauthenticated application.login.url=https\://localhost\:8443/crowd/console/ session.validationinterval=0 application.password=Y1Xp3OorCmsOP4eruL1dmH {noformat} One thing to note here is that based on a comment from the SSL configuration page at atlassian (Steve's comment), you are supposed to leave all the host names the same. For example, if the file says localhost, leave it localhost. So this created a bit of a problem based on the fact that I had left the base URL pointing to auth.mbari.org in the wizard steps above. That step wrote auth.mbari.org to the /data/crowd/crowd.properties. All the other files reference localhost, so to be consistent, I changed auth.mbari.org to localhost in the /data/crowd/crowd.properties file. We will see if this works. ## (/) Per the instructions on the atlassian page (referenced above), I also edited the build.properties file and the /client/conf/crowd.properties files before I restarted and used the SSL URLs ## build.properties: {noformat} # Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See https://confluence.atlassian.com/display/CROWD/Connecting+Crowd+to+a+Database hibernate.dialect=org.hibernate.dialect.SQLServerDialect # The Hibernate transaction factory to use. See https://confluence.atlassian.com/display/CROWD/Configuring+Crowd hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory # The http port you wish to run crowd from, ie: http://localhost:8095/crowd crowd.tomcat.connector.port=8095 # Tomcat requires a unique port for shutdown crowd.tomcat.shutdown.port=8020 # Crowd context root crowd.url=https://localhost:8443/crowd # Demo context root demo.url=https://localhost:8443/demo # OpenID server context root openidserver.url=https://localhost:8443/openidserver {noformat} ## crowd.properties (client) {noformat} application.name crowd application.password password application.login.url https://localhost:8443/crowd/console/ crowd.server.url https://localhost:8443/crowd/services/ crowd.base.url https://localhost:8443/crowd/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 2 session.lastvalidation session.lastvalidation {noformat} ## (/) Although not stated, I am assuming you would need to run the build.sh script to push the build.properties changes to their proper places, so I did that. Note that before doing that, I know that it will clobber the server.xml changes I made, so I made a copy of that file and diff'd them after and then rolled the previous changes to the new server.xml file. Actually, amazingly enough, it seems to have done the connector entry correctly so I left it after running the build.sh script. ## (/) Crossed my fingers and then restarted crowd. I tailed the catalina.out file and did not see any stack traces so that is a good sign! ## (/) I visited https://auth.mbari.org:8443/crowd first. It could not find that page, but I suspect that is because I am browsing from the outside, so I tried just https://auth.mbari.org/crowd and got a service unavailable. I am suspecting that this is a combination of firewall and proxy pass and I will send this info to Joe. From what I can see on the crowd side, it seems like the server started cleanly, we just can't get to it. I tried to reach it from a browser on the machine itself too (through VNC) with the same service not available. ## (/) Here are the notes from Joe after he fixed it! Wooohooo! {noformat} Hey Kevin, Thanks for starting clean! I had to make a few adjustments. 1-I modified the server.xml file in /opt/atlassian-crowd-2.8.3/apache-tomcat/conf/server.xml so there are two connectors per the instructions on the Atlassian site. I have backed up this good server.xml file in /etc/temp/ if you want to browse it to see what I did. Of note is that I removed all the jargon referencing the types of ciphers available to simplify things for now. 2-I modified /data/crowd/crowd.properties to have crowd.server.url=https\://localhost\:8443/crowd/services/ application.login.url=https\://localhost\:8443/crowd/console/ But that would cause my login to error with an error saying it was unable to reach the authentication server. I scratched my head for a bit. When I revert the values to just using non-SSL and try to log in, I just get an "invalid login" (I don't know the crowdadm password). So I worked under the assumption that if I can configure SSL to get an "invalid login" when logging in then it would work when provided real credentials. So, I then changed /data/crowd/crowd.proprties to: crowd.server.url=https\://auth.mbari.org\:8443/crowd/services/ application.login.url=https\://auth.mbari.org\:8443/crowd/console/ And now when I try to log in with SSL it says "invalid login". Strange because all the other values I can find only show "localhost" .. in any case... Can you try to log in now? {noformat} ## (/) Next I moved on to configuring the connection to MBARI's LDAP server to enable our logins through Crowd and CrowdID ## (/) I clicked on "Add Directory" in crowd. ## (/) I selected "Connector" then clicked Next ## (/) I put ldap.shore.mbari.org as the name of the server ## (/) I selected "Use memberOf for group memberships" ## (/) I used "OU=AllUsers,DC=shore,DC=mbari,DC=org" for the Base DN ## (/) I used "CN=LDAPbind,OU=Special,OU=AllUsers,DC=shore,DC=mbari,DC=org" for the Username (talk to Pat Allen for password) ## (/) I tested the connection (button click) and it passed. ## (/) I de-selected all the capabilities of the connector as it is a ready only connector and then saved it. It synchronized correctly! ## (/) At first, I could not login using my MBARI credentials, but after going to the "crowd" application in crowd (logged in as the local admin), I had to add the LDAP directory and configure it to "Allow all to authenticate", then I was able to login. After this, the last step was to get this to run as a different user and lock down various directories. I went through the entire directory structure /opt/atlassian... and set up so that root owned all read-only locations and DB_Collaboration (account set up by IS) owned the other stuff. I also gave full ownership to the /data/crowd directory to DB_Collaboration so it could write there. Pat set up a script to start on boot and after a little tweaking, it now starts on boot. {warning:title=CrowdID log file} One thing that came up here was that when the crowdID application ran, it tried to write a log file to the location where the process was launched from (which is /opt/atlassian...). This is a bad thing and I figured out that I could change that location by changing the file /opt/atlassian-crowd-2.8.3/crowd-openidserver-webapp/WEB-INF/classes/log4j.properties and hardcoding the /data/crowd/logs/atlassian-crowd-openid-server.log and then restarted the application. {warning} ## (/) Another note is the when an application tried to use the OpenID application, it would get redirected to localhost. I changed the /opt/atlassian.../crowd-openidserver-webapp/WEB-INF/classes/crowd.properties file to look like: {noformat} #Sat Aug 01 10:03:18 PDT 2015 session.lastvalidation=session.lastvalidation session.tokenkey=session.tokenkey crowd.server.url=http\://localhost\:8095/crowd/services/ application.name=crowd-openid-server #application.login.url.template=http\://localhost\:8095/openidserver?returnToUrl\=${RETURN_TO_URL} application.login.url.template=https\://auth.mbari.org/openidserver?returnToUrl\=${RETURN_TO_URL} session.isauthenticated=session.isauthenticated #application.base.url=http\://localhost\:8095/openidserver application.base.url=https\://auth.mbari.org/openidserver #application.login.url=http\://localhost\:8095/openidserver application.login.url=https\://auth.mbari.org/openidserver session.validationinterval=0 application.password=password {noformat} and that seems to have fixed it. # (/) It is finally time to move on to the version 4 upgrade ... holy crap. I first went to the *new* crowd install (auth.mbari.org) and logged in as the crowdadm. # (/) I clicked on Applications, then on Add Application # (/) I selected JIRA from the Application type drop-down # (/) I entered jira445 as the username. Ask Kevin about the password. # (/) I used http://bugs.shore.mbari.org:8081 as the URL # (/) I used 134.89.12.31 as the IP address. # (/) I selected only the MBARI LDAP directory. # (/) Then I selected "Allow all users to authenticate" # (/) Then I clicked on "Add Application" # (/) I VNC'd into bugs.mbari.org. As it turns out, for Linux, there is an installer program to download. I downloaded the .bin for 64 bit Linux installer and moved it to the jira-upgrade directory. # (/) I chmod'd the file to make it executable and ran it. It gave me a warning about not being root, but I went ahead with it. # (/) It asked for the JIRA home and data directory, which I specified as /opt/jira4 and /data/jira445. # (/) For the ports, I specified 8180 and 8105 (HTTP and control respectively). It then extracted all the files and launched JIRA. It said if finished, so I opened a local browser to http://localhost:8180 which kicked off the start up wizard. # (/) I specified the external database using: ## solstice2.shore.mbari.org (server) ## 1433 (port) ## jira4 (database) ## DB_Collaboration (username) ## (password ask Kevin) ## dbo (schema) # But all this failed as it seems to just want to try and use the SQL server authentication instead of domain. I will have to do it manually. # (/) I stopped the server using the bin/stop-jira.sh script. # (/) I created and edited /data/jira445/dbconfig.xml and made it look like the following: {noformat} ?xml version="1.0" encoding="UTF-8"?> defaultDS default mssql jiraschema jdbc:jtds:sqlserver://solstice2.shore.mbari.org:1433/Jira4;domain=SHORE;useNTLMv2=true net.sourceforge.jtds.jdbc.Driver DB_Collaboration (ask Kevin) 15 {noformat} # (/) I then started it again using bin/start-jira.sh and tailed the catalina.out file. Got a bunch of errors related to the schema 'jiraschema', I edited the file and changed the schema to 'dbo' and restarted. That seemed to do it. There was one stack trace for some iCal plugin, but looks OK other than that. # I browsed back to localhost:8180 and the wizard moved to step 2. There was an option to import existing data bit without the crowd connection, I thought I should set it up manually, connect to crowd, then import. I generated an evaluation license, called the app "MBARI JIRA4" and change the server in the url to bugs.shore.mbari.org # For the admin, I created an account called 'jiraadm' (ask Kevin for password). # Since this is a temporary system, I left the email system disabled. # I logged in as jiraadm, went to Administration, then Users, then clicked on Add Directory and chose Atlassian Crowd. Note that I had to set the server URL to http://auth.mbari.org:8095/crowd or I would have had to configure all this SSL crap that I did not want to do for this temporary install. # It tested successfully, I clicked Save and it went through a 13 second sync, whew! # I then went to System->Import and Export->Restore System # I copied the jira-upgrade-3.13.5.zip file from the previous version export into /data/jira445/import and then entered that file name along with the new evaluation license again. # I worked through progress bar after I clicked on Restore (it took a really long time). # I then stopped, restarted and tailed the log file. # I am thinking now I should have put the attachments in the import attachments directory, but I am hoping I can just copy them to the data/attachments directory. # UG! I got some error during the import. The exception read: "JIRA is unable to migrat the User Directory configuration because external users exist but the osuser.xml file is not available". It then gave me a link to a doc that talked about making the old user files available before the upgrade ... crap. So I needed to copy the osuser.xml and crowd.properties file from atlassian-jira/WEB-INF/classes directory on the old install to the same directory on the new install ... sigh. This means I am going to blow away everything and start over. # I shutdown jira4 # I dropped all things in the database and deleted all content in the /data/jira445 directory (except for the dbconfig.xml file). # I also removed the temp, logs (actually you have to leave the directory, just clear the files) and the work/Catalina/localhost directories from the jira installation. # I then copied the osuser.xml and the crowd.properties files from the 3.13.5 install to the 4 install. # I edited the crowd.properties file in hopes that I could point it to the new crowd install on auth.mbari.org and it would work, but we will see. # I then started jira and tailed the log file. ]]> 27558182 19073837 19041146 27590944 4.4: [https://confluence.atlassian.com/display/JIRA044/Migrating+JIRA+to+Another+Server] ## The JIRA configuration tool: [https://confluence.atlassian.com/display/JIRA044/Using+the+JIRA+Configuration+Tool] h5. Steps # (/) Create new VM named bugs.mbari.org in the DMZ # (/) Have Neil create database Jira_Temp on solstice2.shore.mbari.org # (/) Have Neil create database Jira on solstice2.shore.mbari.org # (/) Have Pat install Java 7 on bugs.shore.mbari.org # (/) Have Pete plumb holes through firewall so processes on bugs.mbari.org can get to Solstice2 # (/) Have Pat create DB_Collaboration account on bugs so it can run JIRA under that account and it can connect to solstice2 using that NT Domain account. # (/) Upgrade license on Atlassian site # (/) Log into bugs.shore.mbari.org # (/) Download 3.13.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 4.4.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 5.2.11 standalone Linux 64 bit tar.gz (not sure this version is necessary, but at least I have it) # (/) Unzip and untar the file to /opt # (/) Download latest JIRA (6.4.7 as of this writing). # (/) Unzip and untar it to /opt # Performed Test Upgrade ## (/) In order to export the current stuff in JIRA, I had to shut off access so people could not change the data while I was backing it up. ## (/) I ssh'd to oceana.mbari.org as root and edited the /opt/jira/conf/server.xml file and commented out the Connector section that had the port of 8010 to shut it off from the normal serving route. ## (/) I uncommented the 8082 port connector and the 8443 port connector so that I could still get to the server. ## (/) I stopped and started the JIRA server and in the log file I got a "keystore was tampered with..." which is not surprising. ## (/) I could then browser over to http://oceana.mbari.org:8082/jira ## (/) Then through the Administration console, I did an XML backup ## (/) I then created a tar of all the attachments in the /data/jira_3_12/attachments directory ## (/) I moved both the XML and tar files to the /root/jira-upgrade directory ## (/) I then reversed the changes to the server.xml file and shut down JIRA ## (/) I left it down during the next steps in case it went so well, I could just point people to the new server (yeah, right). ## (/) I then browsed to the crowd server on oceana and add a new application using: ### URL: http://bugs.mbari.org/jira3135 ### IP: 134.89.2.29 ### Name: JIRA3135 ### Password: (ask Kevin) :) ## (/) On bugs, I made a copy of the JIRA 3.13.5 download in the /opt directory and unzipped and untarred it. ## (/) In order to configure the crowd connection I did the following: ### (/) I scp'd the /opt/crowd/client/crowd-integration-client-1.6.jar file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I removed the existing 1.6.1 crowd client jar from the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I scp'd the /opt/crowd/client/conf/crowd.properties file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I scp'd the /opt/crowd/client/conf/crowd-ehcache.xml file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I edited the crowd.properties file on bugs to look like: {noformat} application.name JIRA3135 application.password (ask Kevin) application.login.url http://oceana.mbari.org:8095/crowd/console/ crowd.server.url http://oceana.mbari.org:8095/crowd/services/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 0 session.lastvalidation session.lastvalidation {noformat} ### (/) I edited the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/osuser.xml file to comment out the current authentication mechanism and then uncomment the crowd one. ## (/) I then edited the /opt/atlassian-jira-standalone-3.13.5/conf/server/xml file and configured the database connection to the Jira_Temp database on Solstice2. I looked like this: {noformat} {noformat} ## (/) Edit the /opt/atlassian/jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/entityengine.xml and changed it from 'hsql' to 'mssql' and delete the line with "PUBLIC" in it per the instructions in the comments in that file. ## (/) I edited the /etc/httpd/conf/httpd.conf file and created a proxy pass at the bottom of the file to point a normal URL to the default port 8080 for JIRA: {noformat} # Proxy Pass for JIRA ProxyPass http://bugs.mbari.org:8080 ProxyPassReverse http://bugs.mbari.org:8080 {noformat} ## (/) I restarted Apache ## (/) I scp'd the jtds driver from oceana to the /opt/atlassian-jira-standalone-3.13.5/common/lib directory (you could down from the internet) ## (/) I then went to the /opt/atlassian-jira-standalone-3.13.5/ directory and ran './bin/startup.sh'. From the log file, I could tell things were hanging. After some troubleshooting I am wondering if the local firewall is preventing the application to get access to the database on solstice2. I can telnet to port 1433, but I can't browse to the base http://bugs.mbari.org from anywhere but the local web browser. I have submitted a ticket. ## (/) I restarted the old JIRA with my hopes dashed :(. ## (/) Pat disabled the firewall on bugs.mbari.org but it still hung trying to connect to solstice2.shore.mbari.org. That is really, really perplexing. Neil mentioned that solstice2 is using Kerberos and solstice is not. Checking with the JTDS docs, version 1.3.1 of the driver added kerberos support, so I downloaded that driver and added the 'userKerberos=true' property to the URL in the server.xml file and restarted. Got an error about no credentials, so added user and password properties to the URL. Nope, no luck. Never did figure this one out, but I had Pat pull the VM inside the firewall and after some thrash it worked. Well, it sort of worked ... sigh. It turns out I had downloaded the standard version instead of the enterprise version. I need to redo this work ... grrr. ## (/) I deleted all the tables in the Jira_Temp database and removed the /data/jira3135/indexes directory (and recreated). ## (/) I downloaded the enterprise version of the 3.13.5 server. I made a copy in the /opt directory and unzipped and untarred the file. ## (/) I went back to crowd and edited the application to change the properties to: ### URL: http://bugs.shore.mbari.org:8080 ### IP: 134.89.12.31 ### Name: jira3135 ### Password: (ask Kevin) :) ## (/) I then repeated the steps above to get the server up and running with the following differences: ### The server name is now bugs.shore.mbari.org ### The paths given above are a little different in that they no longer say "standard" but say "enterprise" ### I deleted the proxy pass as it seemed to have issues before and this is only temporary anyway. ## (/) I then browsed to http://bugs.shore.mbari.org:8080 ## (/) It took me to the start up page and at the top was the option to 'import your existing data'. Seemed too good not to try. I clicked on the link. It asked me for the backup file location and the location where the indexes would be stored. ## (/) I copied the XML zip file and the attachments tar file to the /data/original directory. ## (/) I created the /data/jira3135/indexes and used those directories ... it fired off the import and I waited. ## (/) I tailed the log file to watch the import. Holy crap, it worked!!! I could log in and everything! I copied the results from the log file here for posterity sake: {noformat} 2015-07-22 20:55:45,156 http-8080-Processor22 INFO [jira.action.admin.DataImport] Running data import 2015-07-22 20:55:45,179 http-8080-Processor22 INFO [jira.action.admin.DataImport] Importing data.. 2015-07-22 20:55:45,186 http-8080-Processor22 INFO [jira.action.admin.DataImport] Start parsing XML with SAX Parser 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] XML successfully parsed 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] Removing all entries from the database. 2015-07-22 20:56:24,593 http-8080-Processor22 INFO [jira.action.admin.DataImport] All entries removed. 2015-07-22 20:56:24,594 http-8080-Processor22 INFO [jira.action.admin.DataImport] Started storing 410414 Generic Values 2015-07-22 21:01:51,967 http-8080-Processor22 INFO [jira.action.admin.DataImport] Finished storing Generic Values 2015-07-22 21:01:52,329 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:52,361 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:54,683 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLink' to module 'jira.user.format:profile-link-user-format'. 2015-07-22 21:01:54,724 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullName' to module 'jira.user.format:full-name-user-format'. 2015-07-22 21:01:54,773 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkSearcher' to module 'jira.user.format:profile-link-searcher-user-format'. 2015-07-22 21:01:54,784 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkExternal' to module 'jira.user.format:profile-link-external-user-format'. 2015-07-22 21:01:54,795 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkActionHeader' to module 'jira.user.format:profile-link-action-header-user-format'. 2015-07-22 21:01:54,807 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullProfile' to module 'jira.user.format:full-profile-user-format'. 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/comments 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/issues 2015-07-22 21:01:55,641 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/plugins 2015-07-22 21:01:55,867 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:01:55,871 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/issues does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:55,873 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/comments does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,033 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,257 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,889 http-8080-Processor22 ERROR [atlassian.jira.upgrade.ConsistencyCheckImpl] Attachments are turned on, but attachment path [/data/jira_3_12/attachments] invalid - disabling attachments 2015-07-22 21:02:13,904 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Detected that an upgrade is needed; existing data at build 299 2015-07-22 21:02:13,907 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Doing Upgrade... 2015-07-22 21:02:13,915 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value' succeeded 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 317 2015-07-22 21:02:13,944 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite filters - make each filter a favourite of its owner. 2015-07-22 21:02:17,822 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build319] Could not find author 'fpy' for filter with id '10040' 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite filters - make each filter a favourite of its owner.' succeeded 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 319 2015-07-22 21:02:17,995 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise Share Permissions. Move old shares to new shares. 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise Share Permissions. Move old shares to new shares.' succeeded 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 321 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Migrating the old JIRA UI colors to the new JIRA 3.13 colors 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build322] Custom color detected for jira.lf.menu.bgcolour : #336699 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Migrating the old JIRA UI colors to the new JIRA 3.13 colors' succeeded 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 322 2015-07-22 21:02:18,025 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite dashboards - make each dashboard a favourite of its owner. 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'cmcgann' for dashboard with id '10030' 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'fpy' for dashboard with id '10060' 2015-07-22 21:02:18,423 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'kanna' for dashboard with id '10040' 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite dashboards - make each dashboard a favourite of its owner.' succeeded 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 325 2015-07-22 21:02:18,625 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Reindexing all data in JIRA to include Favourites. 2015-07-22 21:02:18,648 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All starting... 2015-07-22 21:02:18,650 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 0% complete. Current index: Issue 2015-07-22 21:02:18,654 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:02:18,809 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 1% complete. Current index: Issue 2015-07-22 21:02:18,855 indexerPool-2-thread-10 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 2% complete. Current index: Issue 2015-07-22 21:02:18,899 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 3% complete. Current index: Issue 2015-07-22 21:02:18,945 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 4% complete. Current index: Issue 2015-07-22 21:02:19,012 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 5% complete. Current index: Issue . . . 2015-07-22 21:02:26,164 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 95% complete. Current index: Issue 2015-07-22 21:02:26,232 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 96% complete. Current index: Issue 2015-07-22 21:02:26,316 indexerPool-2-thread-9 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 97% complete. Current index: Issue 2015-07-22 21:02:26,771 indexerPool-2-thread-3 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: Issue 2015-07-22 21:02:27,261 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 8607ms. Indexer: DefaultIndexManager: paths: [/data/jira3135/indexes/issues, /data/jira3135/indexes/comments] 2015-07-22 21:02:27,263 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: SearchRequest 2015-07-22 21:02:27,268 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,293 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: SearchRequest 2015-07-22 21:02:27,308 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: PortalPage 2015-07-22 21:02:27,312 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,377 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: PortalPage 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 115ms. Indexer: SharedEntityIndexManager: paths: [/data/jira3135/indexes/entities/portalpage, /data/jira3135/indexes/entities/searchrequest] 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All complete. Total time: 8722ms. 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Reindexing all data in JIRA to include Favourites.' succeeded 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 326 2015-07-22 21:02:27,397 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade succeeded! Setting data build number to 360 2015-07-22 21:02:27,469 JiraQuartzScheduler_Worker-0 WARN [service.services.export.ExportService] Backup directory /data/jira_3_12/backup does not exist {noformat} {warning:title=Paths} It appears that the upgraded JIRA will still look for the attachments and the backup locations in the original places. So I created /data/jira_3_12/backup and untarred the original attachments to /data/jira_3_12 and then everything worked (including attachements) in the new JIRA. {warning} ## (/) I then used the upgraded JIRA to generate a new XML backup and stored it in /data/original/3.13.5 along with another tar of the files in /data/jira_3_12/attachments. ## (/) I then shutdown the JIRA server. *I should be ready to move on to version 4 upgrade WHEW* ## So, before moving on, I decided that it would be a really good idea to spin up a new Crowd instance to get rid of the :8443 in the URL and to move off of RedHat per IS requests. I have a ticket in for a new VM and a new database to try to get this going. I am waiting on that before moving on. ## (/) Pat created the VM and Neil created the database. ## (/) I logged into auth.mbari.org (name of the VM) and downloaded crowd which I unzipped to the /opt directory ## (/) I then created a /data/crowd directory and gave my account permissions on it and then edited the /opt/atlassian..../crowd-webapp/WEB-INF/classes/crowd-init.properties file to set that as the crowd home directory. ## (/) The instructions say to download the JDBC driver, but they already have JTDS 1.2.7 in the download so I did not do anything. ## (/) You have to manually connect up CrowdID to a database as they setup wizard does not currently do this. ### (/) They say to download the driver, but again 1.2.7 was there so I did nothing. ### (/) I edited the /opt/atlassian.../apache-tomcat/conf/Catalina/localhost/openidserver.xml to look like: {noformat} {noformat} ### (/) I edited the /opt/atlassian.../build.properties files to look like: {noformat} # Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See https://confluence.atlassian.com/display/CROWD/Connecting+Crowd+to+a+Database hibernate.dialect=org.hibernate.dialect.SQLServerDialect # The Hibernate transaction factory to use. See https://confluence.atlassian.com/display/CROWD/Configuring+Crowd hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory # The http port you wish to run crowd from, ie: http://localhost:8095/crowd crowd.tomcat.connector.port=8095 # Tomcat requires a unique port for shutdown crowd.tomcat.shutdown.port=8020 # Crowd context root crowd.url=http://localhost:8095/crowd # Demo context root demo.url=http://localhost:8095/demo # OpenID server context root openidserver.url=http://localhost:8095/openidserver {noformat} ### (/) I then ran the build.sh script in the root of /opt/atlassian... ## (/) I fired up crowd using the /opt/atlassian.../start_crowd.sh script ## (/) I then went to http://auth.mbari.org:8095/crowd to kick off the start up wizard ## (/) I grabbed a new eval license from my account on atlassian and pasted into the license page. ## (/) I selected "New install" on the next page. ## (/) I configured the JDBC connection using this connection URL with user DB_Collaboration {noformat} jdbc:jtds:sqlserver://dione.mbari.org:51001/Crowd;domain=SHORE;useNTLMv2=TRUE {noformat} ## (/) I left the "Options" as they came up {warning:title=Paths} Not sure if this is a problem, but because I started the set up using auth.mbari.org, it set the Base URL to http://auth.mbari.org:8095/crowd instead of localhost. Hope that is not a problem. We will see. {warning} ## (/) I configured the email connection using the settings from [here|https://wind.shore.mbari.org/is/howto/email/mbarimail/imap] and I used my network login (probably shouldn't be doing that ... not sure where it stores my password, but I am assuming in the DB). ## (/) For the local admin account, I created a user named 'crowdadm' so it would not clash with my LDAP account. See Kevin Gomes for password information. ## (/) I checked the OpenID server as an integrated application ## (/) It then took me to the login page and I logged in using the newly minted admin account. Seemed all is well so far. ## (/) I visited the openidserver URL as well and that seemed OK. ## (/) I decided to wait on configuring the MBARI LDAP directory until I got everything with SSL working. ## (/) Now the next step was to follow the directions to configure Crowd to run over SSL found [here|https://confluence.atlassian.com/display/CROWD/Configuring+Crowd+to+Work+with+SSL] ## (/) I shutdown crowd. Note that the stop script does not shutdown things correctly and I noticed the crowd app running as root. That should not be if I started as kgomes. Not sure what is up with that. ## (/) Now Joe had already configured SSL once, so I used his connector configuration in the server.xml file and so the final file looked like: {noformat} {noformat} ## (/) I then edited the /data/crowd/crowd.properties to look like: {noformat} #Sat Aug 01 09:05:15 PDT 2015 session.lastvalidation=session.lastvalidation session.tokenkey=session.tokenkey crowd.server.url=https\://localhost\:8443/crowd/services/ application.name=crowd http.timeout=30000 session.isauthenticated=session.isauthenticated application.login.url=https\://localhost\:8443/crowd/console/ session.validationinterval=0 application.password=Y1Xp3OorCmsOP4eruL1dmH {noformat} One thing to note here is that based on a comment from the SSL configuration page at atlassian (Steve's comment), you are supposed to leave all the host names the same. For example, if the file says localhost, leave it localhost. So this created a bit of a problem based on the fact that I had left the base URL pointing to auth.mbari.org in the wizard steps above. That step wrote auth.mbari.org to the /data/crowd/crowd.properties. All the other files reference localhost, so to be consistent, I changed auth.mbari.org to localhost in the /data/crowd/crowd.properties file. We will see if this works. ## (/) Per the instructions on the atlassian page (referenced above), I also edited the build.properties file and the /client/conf/crowd.properties files before I restarted and used the SSL URLs ## build.properties: {noformat} # Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See https://confluence.atlassian.com/display/CROWD/Connecting+Crowd+to+a+Database hibernate.dialect=org.hibernate.dialect.SQLServerDialect # The Hibernate transaction factory to use. See https://confluence.atlassian.com/display/CROWD/Configuring+Crowd hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory # The http port you wish to run crowd from, ie: http://localhost:8095/crowd crowd.tomcat.connector.port=8095 # Tomcat requires a unique port for shutdown crowd.tomcat.shutdown.port=8020 # Crowd context root crowd.url=https://localhost:8443/crowd # Demo context root demo.url=https://localhost:8443/demo # OpenID server context root openidserver.url=https://localhost:8443/openidserver {noformat} ## crowd.properties (client) {noformat} application.name crowd application.password password application.login.url https://localhost:8443/crowd/console/ crowd.server.url https://localhost:8443/crowd/services/ crowd.base.url https://localhost:8443/crowd/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 2 session.lastvalidation session.lastvalidation {noformat} ## (/) Although not stated, I am assuming you would need to run the build.sh script to push the build.properties changes to their proper places, so I did that. Note that before doing that, I know that it will clobber the server.xml changes I made, so I made a copy of that file and diff'd them after and then rolled the previous changes to the new server.xml file. Actually, amazingly enough, it seems to have done the connector entry correctly so I left it after running the build.sh script. ## (/) Crossed my fingers and then restarted crowd. I tailed the catalina.out file and did not see any stack traces so that is a good sign! ## (/) I visited https://auth.mbari.org:8443/crowd first. It could not find that page, but I suspect that is because I am browsing from the outside, so I tried just https://auth.mbari.org/crowd and got a service unavailable. I am suspecting that this is a combination of firewall and proxy pass and I will send this info to Joe. From what I can see on the crowd side, it seems like the server started cleanly, we just can't get to it. I tried to reach it from a browser on the machine itself too (through VNC) with the same service not available. ## (/) Here are the notes from Joe after he fixed it! Wooohooo! {noformat} Hey Kevin, Thanks for starting clean! I had to make a few adjustments. 1-I modified the server.xml file in /opt/atlassian-crowd-2.8.3/apache-tomcat/conf/server.xml so there are two connectors per the instructions on the Atlassian site. I have backed up this good server.xml file in /etc/temp/ if you want to browse it to see what I did. Of note is that I removed all the jargon referencing the types of ciphers available to simplify things for now. 2-I modified /data/crowd/crowd.properties to have crowd.server.url=https\://localhost\:8443/crowd/services/ application.login.url=https\://localhost\:8443/crowd/console/ But that would cause my login to error with an error saying it was unable to reach the authentication server. I scratched my head for a bit. When I revert the values to just using non-SSL and try to log in, I just get an "invalid login" (I don't know the crowdadm password). So I worked under the assumption that if I can configure SSL to get an "invalid login" when logging in then it would work when provided real credentials. So, I then changed /data/crowd/crowd.proprties to: crowd.server.url=https\://auth.mbari.org\:8443/crowd/services/ application.login.url=https\://auth.mbari.org\:8443/crowd/console/ And now when I try to log in with SSL it says "invalid login". Strange because all the other values I can find only show "localhost" .. in any case... Can you try to log in now? {noformat} ## (/) Next I moved on to configuring the connection to MBARI's LDAP server to enable our logins through Crowd and CrowdID ## (/) I clicked on "Add Directory" in crowd. ## (/) I selected "Connector" then clicked Next ## (/) I put ldap.shore.mbari.org as the name of the server ## (/) I selected "Use memberOf for group memberships" ## (/) I used "OU=AllUsers,DC=shore,DC=mbari,DC=org" for the Base DN ## (/) I used "CN=LDAPbind,OU=Special,OU=AllUsers,DC=shore,DC=mbari,DC=org" for the Username (talk to Pat Allen for password) ## (/) I tested the connection (button click) and it passed. ## (/) I de-selected all the capabilities of the connector as it is a ready only connector and then saved it. It synchronized correctly! ## (/) At first, I could not login using my MBARI credentials, but after going to the "crowd" application in crowd (logged in as the local admin), I had to add the LDAP directory and configure it to "Allow all to authenticate", then I was able to login. After this, the last step was to get this to run as a different user and lock down various directories. I went through the entire directory structure /opt/atlassian... and set up so that root owned all read-only locations and DB_Collaboration (account set up by IS) owned the other stuff. I also gave full ownership to the /data/crowd directory to DB_Collaboration so it could write there. Pat set up a script to start on boot and after a little tweaking, it now starts on boot. {warning:title=CrowdID log file} One thing that came up here was that when the crowdID application ran, it tried to write a log file to the location where the process was launched from (which is /opt/atlassian...). This is a bad thing and I figured out that I could change that location by changing the file /opt/atlassian-crowd-2.8.3/crowd-openidserver-webapp/WEB-INF/classes/log4j.properties and hardcoding the /data/crowd/logs/atlassian-crowd-openid-server.log and then restarted the application. {warning} ## (/) Another note is the when an application tried to use the OpenID application, it would get redirected to localhost. I changed the /opt/atlassian.../crowd-openidserver-webapp/WEB-INF/classes/crowd.properties file to look like: {noformat} #Sat Aug 01 10:03:18 PDT 2015 session.lastvalidation=session.lastvalidation session.tokenkey=session.tokenkey crowd.server.url=http\://localhost\:8095/crowd/services/ application.name=crowd-openid-server #application.login.url.template=http\://localhost\:8095/openidserver?returnToUrl\=${RETURN_TO_URL} application.login.url.template=https\://auth.mbari.org/openidserver?returnToUrl\=${RETURN_TO_URL} session.isauthenticated=session.isauthenticated #application.base.url=http\://localhost\:8095/openidserver application.base.url=https\://auth.mbari.org/openidserver #application.login.url=http\://localhost\:8095/openidserver application.login.url=https\://auth.mbari.org/openidserver session.validationinterval=0 application.password=password {noformat} and that seems to have fixed it. # (/) It is finally time to move on to the version 4 upgrade ... holy crap. I first went to the *new* crowd install (auth.mbari.org) and logged in as the crowdadm. # (/) I clicked on Applications, then on Add Application # (/) I selected JIRA from the Application type drop-down # (/) I entered jira445 as the username. Ask Kevin about the password. # (/) I used http://bugs.shore.mbari.org:8081 as the URL # (/) I used 134.89.12.31 as the IP address. # (/) I selected only the MBARI LDAP directory. # (/) Then I selected "Allow all users to authenticate" # (/) Then I clicked on "Add Application" # (/) I VNC'd into bugs.mbari.org. As it turns out, for Linux, there is an installer program to download. I downloaded the .bin for 64 bit Linux installer and moved it to the jira-upgrade directory. # (/) I chmod'd the file to make it executable and ran it. It gave me a warning about not being root, but I went ahead with it. # (/) It asked for the JIRA home and data directory, which I specified as /opt/jira4 and /data/jira445. # (/) For the ports, I specified 8180 and 8105 (HTTP and control respectively). It then extracted all the files and launched JIRA. It said if finished, so I opened a local browser to http://localhost:8180 which kicked off the start up wizard. # (/) I specified the external database using: ## solstice2.shore.mbari.org (server) ## 1433 (port) ## jira4 (database) ## DB_Collaboration (username) ## (password ask Kevin) ## dbo (schema) # But all this failed as it seems to just want to try and use the SQL server authentication instead of domain. I will have to do it manually. # (/) I stopped the server using the bin/stop-jira.sh script. # (/) I created and edited /data/jira445/dbconfig.xml and made it look like the following: {noformat} ?xml version="1.0" encoding="UTF-8"?> defaultDS default mssql jiraschema jdbc:jtds:sqlserver://solstice2.shore.mbari.org:1433/Jira4;domain=SHORE;useNTLMv2=true net.sourceforge.jtds.jdbc.Driver DB_Collaboration (ask Kevin) 15 {noformat} # (/) I then started it again using bin/start-jira.sh and tailed the catalina.out file. Got a bunch of errors related to the schema 'jiraschema', I edited the file and changed the schema to 'dbo' and restarted. That seemed to do it. There was one stack trace for some iCal plugin, but looks OK other than that. # I browsed back to localhost:8180 and the wizard moved to step 2. There was an option to import existing data bit without the crowd connection, I thought I should set it up manually, connect to crowd, then import. I generated an evaluation license, called the app "MBARI JIRA4" and change the server in the url to bugs.shore.mbari.org # For the admin, I created an account called 'jiraadm' (ask Kevin for password). # Since this is a temporary system, I left the email system disabled. # I logged in as jiraadm, went to Administration, then Users, then clicked on Add Directory and chose Atlassian Crowd. Note that I had to set the server URL to http://auth.mbari.org:8095/crowd or I would have had to configure all this SSL crap that I did not want to do for this temporary install. # It tested successfully, I clicked Save and it went through a 13 second sync, whew! # I then went to System->Import and Export->Restore System # I copied the jira-upgrade-3.13.5.zip file from the previous version export into /data/jira445/import and then entered that file name along with the new evaluation license again. # I worked through progress bar after I clicked on Restore (it took a really long time). # I then stopped, restarted and tailed the log file. # I am thinking now I should have put the attachments in the import attachments directory, but I am hoping I can just copy them to the data/attachments directory. ]]> 27558180 19073838 19041147 4489220 "Downloads">"2.1 Releases">"2.1.1" # I then clicked on alfresco-enterprise-tomcat-2.1.1.zip to download the zip file. # Went to [http://customers.alfresco.com] (I was still logged in) # Went to "Company Home">"Downloads">"2.1 Releases">"2.1.1">"License Files" # I went ahead and downloaded all the "*.lic" files, but I think I only need enterprise-network-customer-unlimited.lic" # Logged out of Alfresco. # Since I suspect I will need a JDBC driver for SQLServer, I downloaded the jTDS-1.2.2 driver from the jtds web site (just Google jtds and go to the download section of the top google return). # I closed the Firefox browser. # I extracted the jtds-1.2.2.jar file from the jtds download # I downloaded and installed the JRockit 6 R27.4 JDK Microsoft Windows (x86 - 32 bit) from BEA's web site {note} After installing JRockit, make sure you set the JAVA_HOME environment variable to point to the installation of JRockit. For example, I went to the desktop, right clicked on the computer, did Properties, then clicked on the Advanced tab, then click on the environment variables button and then created a new system variable named JAVA_HOME and set to c:\bin\Java\jrockit-R27.4.0-jdk1.6.0_02 {note} # I ran the installer, changed the "Program Files" to "bin" in the installation directory for both the JDK and the JRE. I also chose to install the JRE as public. # Using Firefox, I downloaded the PHP 5.2.5 Windows Installer from php.net and installed it. Although I installed it, I did not integrate it with a web server as I want Alfresco to take port 80. I probably did not need to install PHP, but I thought I would anyway. (again, I changed install path from "Program Files" to "bin" # I also downloaded and installed OpenOffice and ran it once so I could get through the initial startup # I setup a Alfresco database on the server Solstice and granted the LAGOON\DB_Collaboration account to be the db_owner of the Alfresco database. # I unzipped the alfresco tomcat zip file to an alfresco directory in c:\bin # I then went to the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions directory for the customization of the server. ## I edited the custom-repository.properties file ### Changed the dir.root and dir.indexes to look like: {noformat} dir.root=//tornado.shore.mbari.org/Alfresco/alf_data dir.indexes=d:/alf_data/lucene-indexes {noformat} ### Commented out the db.* lines for the HSQL Connection (db.driver and db.url) ### Uncommented the db.* lines for MSSQL and changed to use the jTDS driver. They should look like: {noformat} db.driver=net.sourceforge.jtds.jdbc.Driver db.url=jdbc:jtds:sqlserver://solstice.shore.mbari.org/Alfresco;domain=SHORE;user=DB_Collaboration;password=XXXXXXXXX {noformat} ### I also added the following section to override the mail server settings {noformat} # Mail server configuration mail.host=mail.mbari.org mail.port=25 mail.username= mail.password= {noformat} ## Edited the custom-hibernate-dialect.properties file ### Commented out the HSQL Dialect ### Uncommented the MSSQL Dialect # I then installed the jtds-1.2.2.jar in the c:\bin\alfresco\tomcat\common\lib so that it will be on the classpath when Alfresco is started # Now this is not necessarily fun, but in order to really get it configured the way we want it, you need to pull the original .war file out, edit some stuff inside and re-create the .war. {note} This should all be done before starting Alfresco for the first time. {note} # Copy the c:\Alfresco\tomcat\webapps\alfresco.war file to your home directory. # Make a second copy so that you will always the original (I copied to alfresco.war.orig and moved it somewhere else. It is important to move it and have only the alfresco.war file in the directory because when you un-jar it, all the files go right where alfresco.war is.) # From a command line, un-jar the war file using: {noformat} jar -xvf alfresco.war {noformat} # This unpacks a lot of files and after it completes, move (or delete) the alfresco.war file from the directory. This needs to be done so it does not end up in the new .war file. # I wanted to change the "Company Home" that seems to be everywhere to something that says MBARI. ## Edited ./WEB-INF/classes/alfresco/messages/webclient.properties and changed company_home from 'Company Home' to 'MBARI' ## Edited ./WEB-INF/classes/alfresco/messages/webclient_en_US.properties and changed company_home from 'Company Home' to 'MBARI' ## I edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces.properties and changed the first two lines to read {noformat} spaces.company_home.name=MBARI spaces.company_home.description=The root space for MBARI {noformat} ## Edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces_en_US.properties and made the same changes as the previous step {tip} This took a bit to find all these, and to be honest, I am not sure which one actually made the change on the GUI, but I suspect it was the _en_US ones. {tip} # When users are imported via LDAP, user spaces get created automatically. In order to put them where I wanted them to go (instead of right in the Company Home), I edited the ./WEB-INF/classes/alfresco/authentication-services-context.xml file. In the file there is a bean with an name of personalHomeFolderProvider. There is a property name 'path' and I added {noformat} /${spaces.user_homes.childname} {noformat} to the end to try to get them to create the user spaces there instead of in the Company Home. The final bean XML looks like: {noformat} /${spaces.company_home.childname}/${spaces.user_homes.childname} ${spaces.store} false All All {noformat} # I wanted to change the logo that is used. I attached the replacement logo [here|^AlfrescoLogo32.png]. Copy this to ./images/logo and overwrite the one that is there. # In order to setup SSL for the application (will do that later), edit ./WEB-INF/web.xml and add the following {noformat} Login Pages /* CONFIDENTIAL {noformat} right before the ending tag at the bottom of the file. # Now in order to change the default behavior so that all content is versioned from the start, I edited the .\WEB-INF\classes\alfresco\model\contentModel.xml and searched for the content type definition block. {noformat} Content cm:cmobject true d:content false true false true {noformat} and added the following block right before the ending tag: {noformat} cm:versionable {noformat} so the final block looks like: {noformat} Content cm:cmobject true d:content false true false true cm:versionable {noformat} # That takes care of all the changes to the WAR file. We can now put it back into .war form. # While you are in the directory you expanded the war file in, run ## jar cvfm alfresco.war META-INF\MANIFEST.MF . # You should now have an alfresco.war file in the directory. Move that back to the alfresco install and overwrite the existing one. # Most users like the details view, so I set the default to that by editing c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions\web-client-config-custom.xml and added: {noformat} details 20
20
20 {noformat} right before the closing tag. # Now in order to use MBARI accounts, NTLM authentication was turned on and then chained with the native Alfresco accounts so that we could have non-MBARI accounts on the Alfresco server. ## In order to enable NTLM and native Alfresco authentication, I had to edit two files. For simplicity I have just attached them here and they can be downloaded and installed in the extensions directory. ### The first file is the [ntlm-authentication-context.xml|^ntlm-authentication-context.xml] file. This configures and enables NTLM authentication. ### The next file was the [chaining-authentication-context.xml|^chaining-authentication-context.xml] file which enabled Alfresco authentication and chained it together with the NTLM authentication from the previous file. # Then in order to setup CIFS on the server, I edited the file-servers-custom.xml file to look like the attached [file-servers-custom.xml|^file-servers-custom.xml] file. # In order to grant certain accounts admin privs, I created a new custom-authority-services-context.xml in the same directory as the ldap-authentication-context.xml file and added {noformat} kgomes admin administrator {noformat} # In order for Alfresco to handle all port 80 traffic, I changed Tomcat so that it takes port 80 and SSL goes over port 443. So I edited the c:\Alfresco\tomcat\conf\server.xml file and changed the 8080 port to 80 and the 8443 port to 443 (the 443 change is done in two places). # Now I needed to setup the SSL for the web traffic. Cathy Sewell was instrumental in getting this working. She ordered a new certificate specifically for alfresco and put it in the c:\local\cert folder. Here are the instructions for what she did to get the certficate installed. {noformat} SSL certificate for server Alfresco - 1/2/08 C:\bin\Java\jrockit-R27.1.0-jre1.6.0_02\bin>keytool -genkey -alias tomcat -keyalg RSA -keystore tomcat.keystore What is your first and last name? [alfresco.mbari.org]: What is the name of your organizational unit? [IS]: What is the name of your organization? [MBARI]: What is the name of your City or Locality? [Moss Landing]: What is the name of your State or Province? [CD]: CA What is the two-letter country code for this unit? [US]: Is CN=alfresco.mbari.org, OU=IS, O=MBARI, L=Moss Landing, ST=CA, C=US correct? [no]: y Enter key password for (RETURN if same as keystore password): C:\bin\Java\jrockit-R27.4.0-jre1.6.0_02\bin>keytool -certreq -keyalg RSA -alias tomcat -file certreq.csr -keystore tomcat.keystore Enter keystore password: Generated certificate request file, certreq.csr, was submitted to SSL provider. Certificate provider sent certificate file (alfresco.mbari.org.crt), along with gd_bundle.crt, gd_cross_intermediate.crt, and gd_intermediate.crt. Additionally, I downloaded valicert_class2_root.cer from their website. These files were stored in c:\local\cert. The following commands were used to add them to the tomcat keystore: C:\bin\Java\jrockit-R27.4.0-jre1.6.0_02\bin>keytool -import -alias root -keystore tomcat.keystore -trustcacerts -file c:\local\cert\valicert_class2_root.cer Enter keystore password: Certificate already exists in system-wide CA keystore under alias Do you still want to add it to your own keystore? [no]: y Certificate was added to keystore C:\bin\Java\jrockit-R27.4.0-jre1.6.0_02\bin>keytool -import -alias cross -keystore tomcat.keystore -trustcacerts -file c:\local\cert\gd_cross_intermediate.crt Enter keystore password: Certificate was added to keystore C:\bin\Java\jrockit-R27.4.0-jre1.6.0_02\bin>keytool -import -alias intermed -keystore tomcat.keystore -trustcacerts -file c:\local\cert\gd_intermediate.crt Enter keystore password: Certificate was added to keystore C:\bin\Java\jrockit-R27.4.0-jre1.6.0_02\bin>keytool -import -alias tomcat -keystore tomcat.keystore -trustcacerts -file c:\local\cert\alfresco.mbari.org.crt Enter keystore password: Certificate reply was installed in keystore {noformat} # I edited the c:\bin\alfresco\tomcat\conf\server.xml file and uncommented the SSL section and edited to look like that shown below. {noformat} {noformat} # Since I was in the server.xml file, I went ahead and changed it so that the default webapp was alfresco so that you would get alfresco anytime you went to the base URL. I did this by adding: {noformat} {noformat} as the last line of the tag section (right before the closing tag). {note} You will also notice the Valve tag that I had to add to turn off proxy cache disabling so that IE clients would work correctly over SSL. Gotta love M$. {note} # I copied the enterprise-network-unlimited.lic file into the c:\Alfresco\tomcat\shared\classes\alfresco\extensions\license directory # Just to keep things clean, I edited the c:\bin\alfresco\alfresco.bat file and put 'rem' in front of the second JAVA_OPTS set as I am using Java 6. # Now after you run it for the first time and the database structure gets created, you can't restart it because you get: {noformat} java.sql.SQLException: Column names in each table must be unique. Column name 'ID_' in table 'JBPM_ACTION' is specified more than once. {noformat} Sigh, so in order to keep Alfresco from hurting itself, I had to turn off the schema updates. This is done by editing the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions\custom-repository.properties and adding the following: {noformat} db.schema.update=false {noformat} and then restarting alfresco. # To install Alfresco as a Windows Service use a command prompt and enter the following: {noformat} cd c:\bin\alfresco\tomcat\bin service.bat install alfresco tomcat5.exe //US//alfresco --DisplayName "Alfresco Server" tomcat5.exe //US//alfresco --JvmMs=512 --JvmMx=1024 --JvmSs=64 tomcat5.exe //US//alfresco --JavaHome=c:/bin/Java/jrockit-R27.4.0-jdk1.6.0_02 tomcat5.exe //US//alfresco --Environment ALF_HOME=c:/bin/alfresco/ tomcat5.exe //US//alfresco --Environment PATH=c:/bin/alfresco/bin;%PATH% tomcat5.exe //US//alfresco --StartPath c:/bin/alfresco --Startup auto {noformat} # To uninstall the service, at a later time, do the following: {noformat} cd c:\bin\alfresco\tomcat\bin service.bat uninstall alfresco {noformat} # To edit your service settings at any time: {noformat} cd c:\alfresco\tomcat\bin tomcat5w.exe //ES//alfresco {noformat} {warning} These next couple of steps had to be taken to install a patch from Alfresco for an issue with bulk uploads I was having. Essentially when file and path structures get really long and nasty, Alfresco was throwing an error and bailing out. This patch (two Java classes) fixed that issue. {warning} # Next, I downloaded the attached [JAR|^act2139.jar] file and copied it to the c:\bin\alfresco\tomcat\webapps\alfresco\WEB-INF\classes directory. # I shutdown Alfresco and then unjarred the file to install the new classes. They are: ## org/alfresco/filesys/smb/server/SMBSrvPacket.class ## org/alfresco/filesys/util/DataBuffer.class # I would assume since they do not overwrite anything, that this location is further up in the class loader and so it will load these new classes first. # I deleted the act2139.jar file and the META-INF directory that the unjarring process created. # In order to install certain modules (like the email listener), I had to get the Alfresco Module Manager from the customers.alfresco.com download site. I downloaded the alfresco-mmt-2.1.1.jar file locally so I could use it to install modules. # I then downloaded the email listener module from [http://forge.alfresco.com/projects/email-listener/]. It came as a zip file, so I unzipped it and it created a folder with the appropriate emailListener.amp in it. # Make another backup copy of the alfresco.war file and put somewhere in case you want to roll this back. # Open a command prompt windows and cd to the location where the Alfresco Module Manager jar is. # Run the following: {noformat} java -jar alfresco-mmt-2.1.1.jar path_to_emailListener.amp path_to_alfresco.war {noformat} So for me this looked like: {noformat} java -jar alfresco-mmt-2.1.1.jar .\email-listener_2.1RC2\emailListener.amp c:\bin\alfresco\tomcat\webapps\alfresco.war {noformat} # You should be able to verify the install by running: {noformat} java -jar alfresco-mmt-2.1.1.jar list c:\bin\alfresco\tomcat\webapps\alfresco.war {noformat} and you should see something like: {noformat} Module 'emailListener' installed in 'c:\bin\alfresco\tomcat\webapps\alfresco.war' - Title: EmailListener - Version: 2.1 - Install Date: Fri Dec 07 08:43:10 PST 2007 - Desription: EmailListener Module {noformat} # Finally, to start the service, just go into your Windows Service control panel and locate the service that is now named 'Alfresco Server'. You can start and stop Alfresco from this control panel. h1. Content Migration Now, in order to migrate content from old alfresco and normal file structures, I did the following: h3. For content already in alfresco: # Navigate to the space whose contents you want to migrate. For example, let's say I want to migrate the stuff from my personal space. I would navigate (using the WebUI) to the /MBARI/User Homes/kgomes space. You should see the contents of the kgomes folder from this view. # Click on 'More actions->View Details'. # On the right hand side, click on 'Export'. # For package name, I usually enter the space name followed by '_export', but it doesn't really matter. # Click on the link that says 'Click here to select the destination' and select somewhere that you will be able to download the .acp file from. # Select 'Current Space'. # Select 'Include Children'. # Uncheck 'Include this space' unless you have content (documents) in this specific folder (anything other than folders) that you want to migrate. This is a bit tricky, but there are two ways to do this. If you want to have the top level folder created, use the 'Include this space' and that will create the top level folder. Otherwise, if will expand into the folder in which you import the .acp file into. This is important in cases where the folder has already been created for you (like with user homes) and you have to migrate content into that folder. If you have the option to create the top level directory, by all means do so. # Uncheck 'Export in background' so you can force it to happen and you know when it is complete.]]> 4456452 19074049 19041363 4489222 "Downloads">"2.1 Releases">"2.1.1" # I then clicked on alfresco-enterprise-tomcat-2.1.1.zip to download the zip file. # Went to [http://customers.alfresco.com] (I was still logged in) # Went to "Company Home">"Downloads">"2.1 Releases">"2.1.1">"License Files" # I went ahead and downloaded all the "*.lic" files, but I think I only need enterprise-network-customer-unlimited.lic" # Logged out of Alfresco. # Since I suspect I will need a JDBC driver for SQLServer, I downloaded the jTDS-1.2.2 driver from the jtds web site (just Google jtds and go to the download section of the top google return). # I closed the Firefox browser. # I extracted the jtds-1.2.2.jar file from the jtds download # I downloaded and installed the JRockit 6 R27.4 JDK Microsoft Windows (x86 - 32 bit) from BEA's web site {note} After installing JRockit, make sure you set the JAVA_HOME environment variable to point to the installation of JRockit. For example, I went to the desktop, right clicked on the computer, did Properties, then clicked on the Advanced tab, then click on the environment variables button and then created a new system variable named JAVA_HOME and set to c:\bin\Java\jrockit-R27.4.0-jdk1.6.0_02 {note} # I ran the installer, changed the "Program Files" to "bin" in the installation directory for both the JDK and the JRE. I also chose to install the JRE as public. # Using Firefox, I downloaded the PHP 5.2.5 Windows Installer from php.net and installed it. Although I installed it, I did not integrate it with a web server as I want Alfresco to take port 80. I probably did not need to install PHP, but I thought I would anyway. (again, I changed install path from "Program Files" to "bin" # I also downloaded and installed OpenOffice and ran it once so I could get through the initial startup # I setup a Alfresco database on the server Solstice and granted the LAGOON\DB_Collaboration account to be the db_owner of the Alfresco database. # I unzipped the alfresco tomcat zip file to an alfresco directory in c:\bin # I then went to the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions directory for the customization of the server. ## I edited the custom-repository.properties file ### Changed the dir.root and dir.indexes to look like: {noformat} dir.root=//tornado.shore.mbari.org/Alfresco/alf_data dir.indexes=d:/alf_data/lucene-indexes {noformat} ### Commented out the db.* lines for the HSQL Connection (db.driver and db.url) ### Uncommented the db.* lines for MSSQL and changed to use the jTDS driver. They should look like: {noformat} db.driver=net.sourceforge.jtds.jdbc.Driver db.url=jdbc:jtds:sqlserver://solstice.shore.mbari.org/Alfresco;domain=SHORE;user=DB_Collaboration;password=XXXXXXXXX {noformat} ### I also added the following section to override the mail server settings {noformat} # Mail server configuration mail.host=mail.mbari.org mail.port=25 mail.username= mail.password= {noformat} ## Edited the custom-hibernate-dialect.properties file ### Commented out the HSQL Dialect ### Uncommented the MSSQL Dialect # I then installed the jtds-1.2.2.jar in the c:\bin\alfresco\tomcat\common\lib so that it will be on the classpath when Alfresco is started # Now this is not necessarily fun, but in order to really get it configured the way we want it, you need to pull the original .war file out, edit some stuff inside and re-create the .war. {note} This should all be done before starting Alfresco for the first time. {note} # Copy the c:\Alfresco\tomcat\webapps\alfresco.war file to your home directory. # Make a second copy so that you will always the original (I copied to alfresco.war.orig and moved it somewhere else. It is important to move it and have only the alfresco.war file in the directory because when you un-jar it, all the files go right where alfresco.war is.) # From a command line, un-jar the war file using: {noformat} jar -xvf alfresco.war {noformat} # This unpacks a lot of files and after it completes, move (or delete) the alfresco.war file from the directory. This needs to be done so it does not end up in the new .war file. # I wanted to change the "Company Home" that seems to be everywhere to something that says MBARI. ## Edited ./WEB-INF/classes/alfresco/messages/webclient.properties and changed company_home from 'Company Home' to 'MBARI' ## Edited ./WEB-INF/classes/alfresco/messages/webclient_en_US.properties and changed company_home from 'Company Home' to 'MBARI' ## I edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces.properties and changed the first two lines to read {noformat} spaces.company_home.name=MBARI spaces.company_home.description=The root space for MBARI {noformat} ## Edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces_en_US.properties and made the same changes as the previous step {tip} This took a bit to find all these, and to be honest, I am not sure which one actually made the change on the GUI, but I suspect it was the _en_US ones. {tip} # When users are imported via LDAP, user spaces get created automatically. In order to put them where I wanted them to go (instead of right in the Company Home), I edited the ./WEB-INF/classes/alfresco/authentication-services-context.xml file. In the file there is a bean with an name of personalHomeFolderProvider. There is a property name 'path' and I added {noformat} /${spaces.user_homes.childname} {noformat} to the end to try to get them to create the user spaces there instead of in the Company Home. The final bean XML looks like: {noformat} /${spaces.company_home.childname}/${spaces.user_homes.childname} ${spaces.store} false All All {noformat} # I wanted to change the logo that is used. I attached the replacement logo [here|^AlfrescoLogo32.png]. Copy this to ./images/logo and overwrite the one that is there. # In order to setup SSL for the application (will do that later), edit ./WEB-INF/web.xml and add the following {noformat} Login Pages /* CONFIDENTIAL {noformat} right before the ending tag at the bottom of the file. # Now in order to change the default behavior so that all content is versioned from the start, I edited the .\WEB-INF\classes\alfresco\model\contentModel.xml and searched for the content type definition block. {noformat} Content cm:cmobject true d:content false true false true {noformat} and added the following block right before the ending tag: {noformat} cm:versionable {noformat} so the final block looks like: {noformat} Content cm:cmobject true d:content false true false true cm:versionable {noformat} # That takes care of all the changes to the WAR file. We can now put it back into .war form. # While you are in the directory you expanded the war file in, run ## jar cvfm alfresco.war META-INF\MANIFEST.MF . # You should now have an alfresco.war file in the directory. Move that back to the alfresco install and overwrite the existing one. # Most users like the details view, so I set the default to that by editing c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions\web-client-config-custom.xml and added: {noformat} details 20
20
20 {noformat} right before the closing tag. # Now in order to use MBARI accounts, NTLM authentication was turned on and then chained with the native Alfresco accounts so that we could have non-MBARI accounts on the Alfresco server. ## In order to enable NTLM and native Alfresco authentication, I had to edit two files. For simplicity I have just attached them here and they can be downloaded and installed in the extensions directory. ### The first file is the [ntlm-authentication-context.xml|^ntlm-authentication-context.xml] file. This configures and enables NTLM authentication. ### The next file was the [chaining-authentication-context.xml|^chaining-authentication-context.xml] file which enabled Alfresco authentication and chained it together with the NTLM authentication from the previous file. # Then in order to setup CIFS on the server, I edited the file-servers-custom.xml file to look like the attached [file-servers-custom.xml|^file-servers-custom.xml] file. # In order to grant certain accounts admin privs, I created a new custom-authority-services-context.xml in the same directory as the ldap-authentication-context.xml file and added {noformat} kgomes admin administrator {noformat} # In order for Alfresco to handle all port 80 traffic, I changed Tomcat so that it takes port 80 and SSL goes over port 443. So I edited the c:\Alfresco\tomcat\conf\server.xml file and changed the 8080 port to 80 and the 8443 port to 443 (the 443 change is done in two places). # Now I needed to setup the SSL for the web traffic. Cathy Sewell was instrumental in getting this working. She ordered a new certificate specifically for alfresco and put it in the c:\local\cert folder. Here are the instructions for what she did to get the certficate installed. {noformat} SSL certificate for server Alfresco - 1/2/08 C:\bin\Java\jrockit-R27.1.0-jre1.6.0_02\bin>keytool -genkey -alias tomcat -keyalg RSA -keystore tomcat.keystore What is your first and last name? [alfresco.mbari.org]: What is the name of your organizational unit? [IS]: What is the name of your organization? [MBARI]: What is the name of your City or Locality? [Moss Landing]: What is the name of your State or Province? [CD]: CA What is the two-letter country code for this unit? [US]: Is CN=alfresco.mbari.org, OU=IS, O=MBARI, L=Moss Landing, ST=CA, C=US correct? [no]: y Enter key password for (RETURN if same as keystore password): C:\bin\Java\jrockit-R27.4.0-jre1.6.0_02\bin>keytool -certreq -keyalg RSA -alias tomcat -file certreq.csr -keystore tomcat.keystore Enter keystore password: Generated certificate request file, certreq.csr, was submitted to SSL provider. Certificate provider sent certificate file (alfresco.mbari.org.crt), along with gd_bundle.crt, gd_cross_intermediate.crt, and gd_intermediate.crt. Additionally, I downloaded valicert_class2_root.cer from their website. These files were stored in c:\local\cert. The following commands were used to add them to the tomcat keystore: C:\bin\Java\jrockit-R27.4.0-jre1.6.0_02\bin>keytool -import -alias root -keystore tomcat.keystore -trustcacerts -file c:\local\cert\valicert_class2_root.cer Enter keystore password: Certificate already exists in system-wide CA keystore under alias Do you still want to add it to your own keystore? [no]: y Certificate was added to keystore C:\bin\Java\jrockit-R27.4.0-jre1.6.0_02\bin>keytool -import -alias cross -keystore tomcat.keystore -trustcacerts -file c:\local\cert\gd_cross_intermediate.crt Enter keystore password: Certificate was added to keystore C:\bin\Java\jrockit-R27.4.0-jre1.6.0_02\bin>keytool -import -alias intermed -keystore tomcat.keystore -trustcacerts -file c:\local\cert\gd_intermediate.crt Enter keystore password: Certificate was added to keystore C:\bin\Java\jrockit-R27.4.0-jre1.6.0_02\bin>keytool -import -alias tomcat -keystore tomcat.keystore -trustcacerts -file c:\local\cert\alfresco.mbari.org.crt Enter keystore password: Certificate reply was installed in keystore {noformat} # I edited the c:\bin\alfresco\tomcat\conf\server.xml file and uncommented the SSL section and edited to look like that shown below. {noformat} {noformat} # Since I was in the server.xml file, I went ahead and changed it so that the default webapp was alfresco so that you would get alfresco anytime you went to the base URL. I did this by adding: {noformat} {noformat} as the last line of the tag section (right before the closing tag). {note} You will also notice the Valve tag that I had to add to turn off proxy cache disabling so that IE clients would work correctly over SSL. Gotta love M$. {note} # I copied the enterprise-network-unlimited.lic file into the c:\Alfresco\tomcat\shared\classes\alfresco\extensions\license directory # Just to keep things clean, I edited the c:\bin\alfresco\alfresco.bat file and put 'rem' in front of the second JAVA_OPTS set as I am using Java 6. # Now after you run it for the first time and the database structure gets created, you can't restart it because you get: {noformat} java.sql.SQLException: Column names in each table must be unique. Column name 'ID_' in table 'JBPM_ACTION' is specified more than once. {noformat} Sigh, so in order to keep Alfresco from hurting itself, I had to turn off the schema updates. This is done by editing the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions\custom-repository.properties and adding the following: {noformat} db.schema.update=false {noformat} and then restarting alfresco. # To install Alfresco as a Windows Service use a command prompt and enter the following: {noformat} cd c:\bin\alfresco\tomcat\bin service.bat install alfresco tomcat5.exe //US//alfresco --DisplayName "Alfresco Server" tomcat5.exe //US//alfresco --JvmMs=512 --JvmMx=1024 --JvmSs=64 tomcat5.exe //US//alfresco --JavaHome=c:/bin/Java/jrockit-R27.4.0-jdk1.6.0_02 tomcat5.exe //US//alfresco --Environment ALF_HOME=c:/bin/alfresco/ tomcat5.exe //US//alfresco --Environment PATH=c:/bin/alfresco/bin;%PATH% tomcat5.exe //US//alfresco --StartPath c:/bin/alfresco --Startup auto {noformat} # To uninstall the service, at a later time, do the following: {noformat} cd c:\bin\alfresco\tomcat\bin service.bat uninstall alfresco {noformat} # To edit your service settings at any time: {noformat} cd c:\alfresco\tomcat\bin tomcat5w.exe //ES//alfresco {noformat} {warning} These next couple of steps had to be taken to install a patch from Alfresco for an issue with bulk uploads I was having. Essentially when file and path structures get really long and nasty, Alfresco was throwing an error and bailing out. This patch (two Java classes) fixed that issue. {warning} # Next, I downloaded the attached JAR file and copied it to the c:\bin\alfresco\tomcat\webapps\alfresco\WEB-INF\classes directory. # I shutdown Alfresco and then unjarred the file to install the new classes. They are: ## org/alfresco/filesys/smb/server/SMBSrvPacket.class ## org/alfresco/filesys/util/DataBuffer.class # I would assume since they do not overwrite anything, that this location is further up in the class loader and so it will load these new classes first. # I deleted the act2139.jar file and the META-INF directory that the unjarring process created. # In order to install certain modules (like the email listener), I had to get the Alfresco Module Manager from the customers.alfresco.com download site. I downloaded the alfresco-mmt-2.1.1.jar file locally so I could use it to install modules. # I then downloaded the email listener module from [http://forge.alfresco.com/projects/email-listener/]. It came as a zip file, so I unzipped it and it created a folder with the appropriate emailListener.amp in it. # Make another backup copy of the alfresco.war file and put somewhere in case you want to roll this back. # Open a command prompt windows and cd to the location where the Alfresco Module Manager jar is. # Run the following: {noformat} java -jar alfresco-mmt-2.1.1.jar path_to_emailListener.amp path_to_alfresco.war {noformat} So for me this looked like: {noformat} java -jar alfresco-mmt-2.1.1.jar .\email-listener_2.1RC2\emailListener.amp c:\bin\alfresco\tomcat\webapps\alfresco.war {noformat} # You should be able to verify the install by running: {noformat} java -jar alfresco-mmt-2.1.1.jar list c:\bin\alfresco\tomcat\webapps\alfresco.war {noformat} and you should see something like: {noformat} Module 'emailListener' installed in 'c:\bin\alfresco\tomcat\webapps\alfresco.war' - Title: EmailListener - Version: 2.1 - Install Date: Fri Dec 07 08:43:10 PST 2007 - Desription: EmailListener Module {noformat} # Finally, to start the service, just go into your Windows Service control panel and locate the service that is now named 'Alfresco Server'. You can start and stop Alfresco from this control panel. h1. Content Migration Now, in order to migrate content from old alfresco and normal file structures, I did the following: h3. For content already in alfresco: # Navigate to the space whose contents you want to migrate. For example, let's say I want to migrate the stuff from my personal space. I would navigate (using the WebUI) to the /MBARI/User Homes/kgomes space. You should see the contents of the kgomes folder from this view. # Click on 'More actions->View Details'. # On the right hand side, click on 'Export'. # For package name, I usually enter the space name followed by '_export', but it doesn't really matter. # Click on the link that says 'Click here to select the destination' and select somewhere that you will be able to download the .acp file from. # Select 'Current Space'. # Select 'Include Children'. # Uncheck 'Include this space' unless you have content (documents) in this specific folder (anything other than folders) that you want to migrate. This is a bit tricky, but there are two ways to do this. If you want to have the top level folder created, use the 'Include this space' and that will create the top level folder. Otherwise, if will expand into the folder in which you import the .acp file into. This is important in cases where the folder has already been created for you (like with user homes) and you have to migrate content into that folder. If you have the option to create the top level directory, by all means do so. # Uncheck 'Export in background' so you can force it to happen and you know when it is complete.]]> 4456454 19074033 19041347 10223625 10256387 10223624 10256387 10223623 10256387 10223622 10256387 10223621 10256387 10223620 10256387 10223619 10256387 10223630 10256388 2009-05-11 10:03:20.500 2009-05-11 10:03:20.500 10223628 10256388 2009-05-11 10:03:20.483 2009-05-11 10:03:20.483 10223629 10256388 2009-05-11 10:03:20.497 2009-05-11 10:03:20.497 10223626 10256387 10223627 10256387 17498117 17465349 5308445 Open" and select the elf-file (e.g. "test.elf") you want to debug. Now click on "Run->Connect to target" and enter the following settings: Target: "Remote/TCP" Hostname: "localhost" Port: "2000" Set breakpoint at 'main': yes Set breakpoint at 'exit': yes Attach to target: yes Download Program: yes Command after attaching: "monitor erase all" Run Method: Continue from last Stop When you click on "Ok" Insight should tell you that the connection was successful, and gdbproxy should say "notice: msp430-gdbproxy: connected". To start the debugging click on "Run" or simply press "r". If everything worked correctly you should now see the sourcecode of your program with the first line of main() marked green. The red point is the breakpoint that has been set by Insight automatically. You can set or remove breakpoints by clicking on the '-' in front of the line. Now you can 'c'ontinue the execution to the next breakpoint, 's'tep through the code, or step a single assembler instruction... but be careful with "finish": Insight sometimes seems to lock up with this command. So if you want to finish a function, I recommend setting a breakpoint to the end of the function and using "continue". ]]> 5275677 17498115 17465347 17498121 17465353 4489288 Open" and select the elf-file (e.g. "test.elf") you want to debug. Now click on "Run->Connect to target" and enter the following settings: Target: "Remote/TCP" Hostname: "localhost" Port: "2000" Set breakpoint at 'main': yes Set breakpoint at 'exit': yes Attach to target: yes Download Program: yes Command after attaching: "monitor erase all" Run Method: Continue from last Stop When you click on "Ok" Insight should tell you that the connection was successful, and gdbproxy should say "notice: msp430-gdbproxy: connected". To start the debugging click on "Run" or simply press "r". If everything worked correctly you should now see the sourcecode of your program with the first line of main() marked green. The red point is the breakpoint that has been set by Insight automatically. You can set or remove breakpoints by clicking on the '-' in front of the line. Now you can 'c'ontinue the execution to the next breakpoint, 's'tep through the code, or step a single assembler instruction... but be careful with "finish": Insight sometimes seems to lock up with this command. So if you want to finish a function, I recommend setting a breakpoint to the end of the function and using "continue". ]]> 4456525 4489289 Open" and select the elf-file (e.g. "test.elf") you want to debug. Now click on "Run->Connect to target" and enter the following settings: Target: "Remote/TCP" Hostname: "localhost" Port: "2000" Set breakpoint at 'main': yes Set breakpoint at 'exit': yes Attach to target: yes Download Program: yes Command after attaching: "monitor erase all" Run Method: Continue from last Stop When you click on "Ok" Insight should tell you that the connection was successful, and gdbproxy should say "notice: msp430-gdbproxy: connected". To start the debugging click on "Run" or simply press "r". If everything worked correctly you should now see the sourcecode of your program with the first line of main() marked green. The red point is the breakpoint that has been set by Insight automatically. You can set or remove breakpoints by clicking on the '-' in front of the line. Now you can 'c'ontinue the execution to the next breakpoint, 's'tep through the code, or step a single assembler instruction... but be careful with "finish": Insight sometimes seems to lock up with this command. So if you want to finish a function, I recommend setting a breakpoint to the end of the function and using "continue". ]]> 4456526 17498125 17465357 17498123 17465355 10388432 10355704 28409857 2.7.4 -> 3.5.17 -> 5.0.3 -> latest (5.8 at time of writing this) h5. Steps # I.S. created a new VM named pompeii.shore.mbari.org that I will use to do all the stepwise upgrades # Java 1.6.0_36 was installed, so I asked for an update to the latest 1.8 version # I.S. created four databases for the upgrade path. # Per the installation instructions, for each of these databases, I performed the following using Aqua Data Studio {noformat} ALTER DATABASE COLLATE SQL_Latin1_General_CP1_CS_AS {noformat} # Per the installation instructions, for each database, I ran: {noformat} ALTER DATABASE SET READ_COMMITTED_SNAPSHOT ON WITH ROLLBACK IMMEDIATE; {noformat} # I VNC'd into pompeii.shore.mbari.org and fired up Firefox. # I downloaded the .tar.gz versions of the standalone for all the versions listed above. # I went to the Confluence Administration panel and went to Backup and Restore # I selected both the Backup check boxes and clicked "Backup"]]> 28377089 3670818 3638073 3964951 3932184 3964939 3932172 5407466 5374736 3964941 3932174 3964943 3932176 5407462 5374732 3964945 3932178 5407460 D0 52.08 52.08 \+0 \+0.00 D0->D1 104.17 104.17 \+0 \+0.00 D1->D2 156.25 156.25 \+0 \+0.00 D2->D3 208.33 208.33 \+0 \+0.00 D3->D4 260.42 260.42 \+0 \+0.00 D4->D5 312.50 312.50 \+0 \+0.00 D5->D6 364.58 364.58 \+0 \+0.00 D6->D7 416.67 416.67 \+0 \+0.00 D7->stopbit 468.75 468.75 \+0 \+0.00 end of stopb 520.83 520.83 \+0 \+0.00 \*/ UBR00=0xC0; UBR10=0x00; UMCTL0=0x00; /\* uart0 3686400Hz 19200bps \*/ UBR01=0xC0; UBR11=0x00; UMCTL1=0x00; /\* uart1 3686400Hz 19200bps \*/ h4. The simplest way to use the USART in UART mode is this: interrupt is not enabled, the software checks if it can output the next byte (UTXIFG = 1), and if a new character has been received (URXIFG = 1). \\ h4. Modbus Register Map * REG_INPUT_START         512         // input registers start at 512 * REG_INPUT_NREGS         8           // 8x16 bit registers * REG_SOLENOIDS_A        0            // Holding registers start at 0 (16 coils for each A and B) * REG_SOLENOIDS_B        1   * REG_HOLDING_START    0           // to match WAGO * REG_HOLDING_NREGS   40         // 40 is more than actual (2) * REG_COILS_START         0           // read individual coils (was 1000) * REG_COILS_SIZE           32          // 32 coils * REG_DISC_START          0           // discrete (was 1000) * REG_DISC_SIZE             32          // 32 coils \\ h3. ---- MODBUS * Commands ** Read Input Register (0x04) ** Read Holding Registers (0x03) ** Write Single Register (0x06) ** Write Multiple Registers (0x10) ** Read/Write Multiple Registers (0x17) ** Read Coils (0x01) ** Write Single Coil (0x05) ** Write Multiple Coils (0x0F) ** Read Discrete Inputs (0x02) ** Report Slave ID (0x11)   * Address * Slave ID  * Berlios ModBus Stack ** The modbus stack is config'd in {color:#0000ff}mbconfig.h{color} which is located in vpc\modbus\include \\ \\ ---- h3. Debugging MSP430 h4. Starting gdbproxy The next step is starting gdbproxy, which is responsible for the communication between GDB and the FET: msp430-gdbproxy \--port=2000 msp430 If your FET is properly connected to the parallel port, you should see a message like the following: info: msp430: Target device is a 'MSP430F12x' (type 11) notice: msp430-gdbproxy: waiting on TCP port 2000 h4. Using Insight (Windows) After you have started Insight (c:\msp430\bin\msp430-gdb.exe), click on "File->Open" and select the elf-file (e.g. "test.elf") you want to debug. Now click on "Run->Connect to target" and enter the following settings: Target: "Remote/TCP" Hostname: "localhost" Port: "2000" Set breakpoint at 'main': yes Set breakpoint at 'exit': yes Attach to target: yes Download Program: yes Command after attaching: "monitor erase all" Run Method: Continue from last Stop When you click on "Ok" Insight should tell you that the connection was successful, and gdbproxy should say "notice: msp430-gdbproxy: connected". To start the debugging click on "Run" or simply press "r". If everything worked correctly you should now see the sourcecode of your program with the first line of main() marked green. The red point is the breakpoint that has been set by Insight automatically. You can set or remove breakpoints by clicking on the '-' in front of the line. Now you can 'c'ontinue the execution to the next breakpoint, 's'tep through the code, or step a single assembler instruction... but be careful with "finish": Insight sometimes seems to lock up with this command. So if you want to finish a function, I recommend setting a breakpoint to the end of the function and using "continue". \\ h2. Installing the Compiler Tool Chain To obtain and install the compiler: # Go to the MSPGCC download page and obtain the latest MSPGCC installation. I used the 'mspgcc-20040723.exe' download which installed everything I needed for a Win32 setup. \\ # This step need only be performed if you wish to use the graphical version of GDB. The latest MSPGCC download only includes the command line GDB debugger. I prefer to use the graphical version called Insight. A slightly older prebuilt version of Insight can be used. Install this older version of insight into a different directory to that chosen for the latest MSPGCC installation as you don't want to overwrite the files obtained in step 1. \\ You should now have two installations. The latest version of MSPGCC installed during step 1, and a slightly older version of Insight from step 2. Both versions of the GDB debugger are called msp430-gdb.exe so one needs to be renamed. Locate the older version msp430-gdb.exe from the files installed during this step and rename it msp430-insight.exe. \\ # Ensure the BIN directory from the files installed during step 1 and the BIN directory from the files installed during step 2 are included in your PATH environment variable. \\ \\ # The MSPGCC download includes a program called msp430-gdbproxy.exe. This intercepts the GDB TCP commands and redirects them to the parallel port. Start msp430-gdbproxy (a shortcut to this will have been placed on the start menu when MSPGCC was installed). By default msp430-gdbproxy uses port 3333 - do not change this. \\ # Program the flash as per the instruction in the section above. The flash can be programmed from within GDB but it is much faster to do it separately and beforehand. \\ # Start the debugger using the command ... msp430-insight a.out... the commands in the gdb.ini file will do the rest. If you prefer to use the command line debugger simply replace msp430-insight with msp430-gdb. \\ # Insight will start at and the program will stop at the breakpoint in main() as shown below. \\ MSP430 Clocking \\ MSP430 Basic Clock Module * Clock Signals: ** *ACLK*: Auxiliary clock. The signal is sourced from LFXT1CLK with a divider of 1, 2, 4, or 8. (The calibration program for the serial link sets the divider to 4, but after the calibration it can be changed to any other values.) ACLK can be used as the clock signal for Timer A and Timer B. ** *MCLK*: Master clock. The signal can be sourced from LFXT1CLK, XT2CLK (if available), or DCOCLK with a divider of 1, 2, 4, or 8. MCLK is used by the CPU and system. ** *SMCLK*: Sub-main clock. The signal is sourced from either XT2CLK (if available), or DCOCLK with a divider of 1, 2, 4, or 8. SMCLK can be used as the clock signal for Timer A and Timer B. * MSP430 Clocking pictorial: *   * \\ !MSP430_clocking2.JPG!                  !MSP430_BCSCTL1.JPG! !MSP430_BCSCTL2.JPG!\\ \\]]> 5374730 16449734 16416974 16449732 16416972 16449738 16416978 16449736 16416976 5407447 D0 52.08 52.08 \+0 \+0.00 D0->D1 104.17 104.17 \+0 \+0.00 D1->D2 156.25 156.25 \+0 \+0.00 D2->D3 208.33 208.33 \+0 \+0.00 D3->D4 260.42 260.42 \+0 \+0.00 D4->D5 312.50 312.50 \+0 \+0.00 D5->D6 364.58 364.58 \+0 \+0.00 D6->D7 416.67 416.67 \+0 \+0.00 D7->stopbit 468.75 468.75 \+0 \+0.00 end of stopb 520.83 520.83 \+0 \+0.00 \*/ UBR00=0xC0; UBR10=0x00; UMCTL0=0x00; /\* uart0 3686400Hz 19200bps \*/ UBR01=0xC0; UBR11=0x00; UMCTL1=0x00; /\* uart1 3686400Hz 19200bps \*/ h4. The simplest way to use the USART in UART mode is this: interrupt is not enabled, the software checks if it can output the next byte (UTXIFG = 1), and if a new character has been received (URXIFG = 1). \\ h4. Modbus Register Map * REG_INPUT_START         512         // input registers start at 512 * REG_INPUT_NREGS         8           // 8x16 bit registers * REG_SOLENOIDS_A        0            // Holding registers start at 0 (16 coils for each A and B) * REG_SOLENOIDS_B        1   * REG_HOLDING_START    0           // to match WAGO * REG_HOLDING_NREGS   40         // 40 is more than actual (2) * REG_COILS_START         0           // read individual coils (was 1000) * REG_COILS_SIZE           32          // 32 coils * REG_DISC_START          0           // discrete (was 1000) * REG_DISC_SIZE             32          // 32 coils \\ h3. ---- MODBUS * Commands ** Read Input Register (0x04) ** Read Holding Registers (0x03) ** Write Single Register (0x06) ** Write Multiple Registers (0x10) ** Read/Write Multiple Registers (0x17) ** Read Coils (0x01) ** Write Single Coil (0x05) ** Write Multiple Coils (0x0F) ** Read Discrete Inputs (0x02) ** Report Slave ID (0x11)   * Address * Slave ID  * Berlios ModBus Stack ** The modbus stack is config'd in {color:#0000ff}mbconfig.h{color} which is located in vpc\modbus\include \\ \\ ---- h3. Debugging MSP430 h4. Starting gdbproxy The next step is starting gdbproxy, which is responsible for the communication between GDB and the FET: msp430-gdbproxy \--port=2000 msp430 If your FET is properly connected to the parallel port, you should see a message like the following: info: msp430: Target device is a 'MSP430F12x' (type 11) notice: msp430-gdbproxy: waiting on TCP port 2000 h4. Using Insight (Windows) After you have started Insight (c:\msp430\bin\msp430-gdb.exe), click on "File->Open" and select the elf-file (e.g. "test.elf") you want to debug. Now click on "Run->Connect to target" and enter the following settings: Target: "Remote/TCP" Hostname: "localhost" Port: "2000" Set breakpoint at 'main': yes Set breakpoint at 'exit': yes Attach to target: yes Download Program: yes Command after attaching: "monitor erase all" Run Method: Continue from last Stop When you click on "Ok" Insight should tell you that the connection was successful, and gdbproxy should say "notice: msp430-gdbproxy: connected". To start the debugging click on "Run" or simply press "r". If everything worked correctly you should now see the sourcecode of your program with the first line of main() marked green. The red point is the breakpoint that has been set by Insight automatically. You can set or remove breakpoints by clicking on the '-' in front of the line. Now you can 'c'ontinue the execution to the next breakpoint, 's'tep through the code, or step a single assembler instruction... but be careful with "finish": Insight sometimes seems to lock up with this command. So if you want to finish a function, I recommend setting a breakpoint to the end of the function and using "continue". \\ h2. Installing the Compiler Tool Chain To obtain and install the compiler: # Go to the MSPGCC download page and obtain the latest MSPGCC installation. I used the 'mspgcc-20040723.exe' download which installed everything I needed for a Win32 setup. \\ # This step need only be performed if you wish to use the graphical version of GDB. The latest MSPGCC download only includes the command line GDB debugger. I prefer to use the graphical version called Insight. A slightly older prebuilt version of Insight can be used. Install this older version of insight into a different directory to that chosen for the latest MSPGCC installation as you don't want to overwrite the files obtained in step 1. \\ You should now have two installations. The latest version of MSPGCC installed during step 1, and a slightly older version of Insight from step 2. Both versions of the GDB debugger are called msp430-gdb.exe so one needs to be renamed. Locate the older version msp430-gdb.exe from the files installed during this step and rename it msp430-insight.exe. \\ # Ensure the BIN directory from the files installed during step 1 and the BIN directory from the files installed during step 2 are included in your PATH environment variable. \\ \\ # The MSPGCC download includes a program called msp430-gdbproxy.exe. This intercepts the GDB TCP commands and redirects them to the parallel port. Start msp430-gdbproxy (a shortcut to this will have been placed on the start menu when MSPGCC was installed). By default msp430-gdbproxy uses port 3333 - do not change this. \\ # Program the flash as per the instruction in the section above. The flash can be programmed from within GDB but it is much faster to do it separately and beforehand. \\ # Start the debugger using the command ... msp430-insight a.out... the commands in the gdb.ini file will do the rest. If you prefer to use the command line debugger simply replace msp430-insight with msp430-gdb. \\ # Insight will start at and the program will stop at the breakpoint in main() as shown below. \\ MSP430 Clocking \\ MSP430 Basic Clock Module * Clock Signals: ** *ACLK*: Auxiliary clock. The signal is sourced from LFXT1CLK with a divider of 1, 2, 4, or 8. (The calibration program for the serial link sets the divider to 4, but after the calibration it can be changed to any other values.) ACLK can be used as the clock signal for Timer A and Timer B. ** *MCLK*: Master clock. The signal can be sourced from LFXT1CLK, XT2CLK (if available), or DCOCLK with a divider of 1, 2, 4, or 8. MCLK is used by the CPU and system. ** *SMCLK*: Sub-main clock. The signal is sourced from either XT2CLK (if available), or DCOCLK with a divider of 1, 2, 4, or 8. SMCLK can be used as the clock signal for Timer A and Timer B. * MSP430 Clocking pictorial: *   * \\ !MSP430_clocking2.JPG!                  !MSP430_BCSCTL1.JPG! !MSP430_BCSCTL2.JPG!\\ \\]]> 5374716 8388796 8356035 3964994 3932227 8388795 8356034 19074116 Backup ...' # \[kgomes\] Accepted the defaults # \[kgomes\] Under options, I selected 'Verify after backup' # \[kgomes\] Under General, I selected 'Disk' as the destination, then clicked on 'Add...' # \[kgomes\] I added the file name '2012_12_12_2.1.1' to the default path as the file name to save it to # \[kgomes\] I then took about 15 minutes and stated it was completed successfully. # \[kgomes\] I then mapped the equinox 'backup' folder on foghorn and could then see the backup of the SQL database. # \[kgomes\] I copied the backup to the backup file to the D:\MSSQL 10.MSSQL\MSSQL\BACKUP directory so I could use it to restore the database on foghorn # \[kgomes\] # \[kgomes\] # \[kgomes\] # \[kgomes\] {panel} {column} {section}]]> 19041430 3670850 3638111 8388798 8356037 5407445 D0 52.08 52.08 \+0 \+0.00 D0->D1 104.17 104.17 \+0 \+0.00 D1->D2 156.25 156.25 \+0 \+0.00 D2->D3 208.33 208.33 \+0 \+0.00 D3->D4 260.42 260.42 \+0 \+0.00 D4->D5 312.50 312.50 \+0 \+0.00 D5->D6 364.58 364.58 \+0 \+0.00 D6->D7 416.67 416.67 \+0 \+0.00 D7->stopbit 468.75 468.75 \+0 \+0.00 end of stopb 520.83 520.83 \+0 \+0.00 \*/ UBR00=0xC0; UBR10=0x00; UMCTL0=0x00; /\* uart0 3686400Hz 19200bps \*/ UBR01=0xC0; UBR11=0x00; UMCTL1=0x00; /\* uart1 3686400Hz 19200bps \*/ h4. The simplest way to use the USART in UART mode is this: interrupt is not enabled, the software checks if it can output the next byte (UTXIFG = 1), and if a new character has been received (URXIFG = 1). \\ h4. Modbus Register Map * REG_INPUT_START         512         // input registers start at 512 * REG_INPUT_NREGS         8           // 8x16 bit registers * REG_SOLENOIDS_A        0            // Holding registers start at 0 (16 coils for each A and B) * REG_SOLENOIDS_B        1   * REG_HOLDING_START    0           // to match WAGO * REG_HOLDING_NREGS   40         // 40 is more than actual (2) * REG_COILS_START         0           // read individual coils (was 1000) * REG_COILS_SIZE           32          // 32 coils * REG_DISC_START          0           // discrete (was 1000) * REG_DISC_SIZE             32          // 32 coils \\ h3. ---- MODBUS * Commands ** Read Input Register (0x04) ** Read Holding Registers (0x03) ** Write Single Register (0x06) ** Write Multiple Registers (0x10) ** Read/Write Multiple Registers (0x17) ** Read Coils (0x01) ** Write Single Coil (0x05) ** Write Multiple Coils (0x0F) ** Read Discrete Inputs (0x02) ** Report Slave ID (0x11)   * Address * Slave ID  * Berlios ModBus Stack ** The modbus stack is config'd in {color:#0000ff}mbconfig.h{color} which is located in vpc\modbus\include \\ \\ ---- h3. Debugging MSP430 h4. Starting gdbproxy The next step is starting gdbproxy, which is responsible for the communication between GDB and the FET: msp430-gdbproxy \--port=2000 msp430 If your FET is properly connected to the parallel port, you should see a message like the following: info: msp430: Target device is a 'MSP430F12x' (type 11) notice: msp430-gdbproxy: waiting on TCP port 2000 h4. Using Insight (Windows) After you have started Insight (c:\msp430\bin\msp430-gdb.exe), click on "File->Open" and select the elf-file (e.g. "test.elf") you want to debug. Now click on "Run->Connect to target" and enter the following settings: Target: "Remote/TCP" Hostname: "localhost" Port: "2000" Set breakpoint at 'main': yes Set breakpoint at 'exit': yes Attach to target: yes Download Program: yes Command after attaching: "monitor erase all" Run Method: Continue from last Stop When you click on "Ok" Insight should tell you that the connection was successful, and gdbproxy should say "notice: msp430-gdbproxy: connected". To start the debugging click on "Run" or simply press "r". If everything worked correctly you should now see the sourcecode of your program with the first line of main() marked green. The red point is the breakpoint that has been set by Insight automatically. You can set or remove breakpoints by clicking on the '-' in front of the line. Now you can 'c'ontinue the execution to the next breakpoint, 's'tep through the code, or step a single assembler instruction... but be careful with "finish": Insight sometimes seems to lock up with this command. So if you want to finish a function, I recommend setting a breakpoint to the end of the function and using "continue". \\ h2. Installing the Compiler Tool Chain To obtain and install the compiler: # Go to the MSPGCC download page and obtain the latest MSPGCC installation. I used the 'mspgcc-20040723.exe' download which installed everything I needed for a Win32 setup. \\ # This step need only be performed if you wish to use the graphical version of GDB. The latest MSPGCC download only includes the command line GDB debugger. I prefer to use the graphical version called Insight. A slightly older prebuilt version of Insight can be used. Install this older version of insight into a different directory to that chosen for the latest MSPGCC installation as you don't want to overwrite the files obtained in step 1. \\ You should now have two installations. The latest version of MSPGCC installed during step 1, and a slightly older version of Insight from step 2. Both versions of the GDB debugger are called msp430-gdb.exe so one needs to be renamed. Locate the older version msp430-gdb.exe from the files installed during this step and rename it msp430-insight.exe. \\ # Ensure the BIN directory from the files installed during step 1 and the BIN directory from the files installed during step 2 are included in your PATH environment variable. \\ \\ # The MSPGCC download includes a program called msp430-gdbproxy.exe. This intercepts the GDB TCP commands and redirects them to the parallel port. Start msp430-gdbproxy (a shortcut to this will have been placed on the start menu when MSPGCC was installed). By default msp430-gdbproxy uses port 3333 - do not change this. \\ # Program the flash as per the instruction in the section above. The flash can be programmed from within GDB but it is much faster to do it separately and beforehand. \\ # Start the debugger using the command ... msp430-insight a.out... the commands in the gdb.ini file will do the rest. If you prefer to use the command line debugger simply replace msp430-insight with msp430-gdb. \\ # Insight will start at and the program will stop at the breakpoint in main() as shown below. \\ MSP430 Clocking \\ MSP430 Basic Clock Module * Clock Signals: ** *ACLK*: Auxiliary clock. The signal is sourced from LFXT1CLK with a divider of 1, 2, 4, or 8. (The calibration program for the serial link sets the divider to 4, but after the calibration it can be changed to any other values.) ACLK can be used as the clock signal for Timer A and Timer B. ** *MCLK*: Master clock. The signal can be sourced from LFXT1CLK, XT2CLK (if available), or DCOCLK with a divider of 1, 2, 4, or 8. MCLK is used by the CPU and system. ** *SMCLK*: Sub-main clock. The signal is sourced from either XT2CLK (if available), or DCOCLK with a divider of 1, 2, 4, or 8. SMCLK can be used as the clock signal for Timer A and Timer B. * MSP430 Clocking pictorial: *   * \\ !MSP430_clocking2.JPG!                  !MSP430_BCSCTL1.JPG! !MSP430_BCSCTL2.JPG!\\ \\]]> 5374714 8388797 8356036 19074118 Backup ...' # \[kgomes\] Accepted the defaults # \[kgomes\] Under options, I selected 'Verify after backup' # \[kgomes\] Under General, I selected 'Disk' as the destination, then clicked on 'Add...' # \[kgomes\] I added the file name '2012_12_12_2.1.1' to the default path as the file name to save it to # \[kgomes\] I then took about 15 minutes and stated it was completed successfully. # \[kgomes\] I then mapped the equinox 'backup' folder on foghorn and could then see the backup of the SQL database. # \[kgomes\] I copied the backup to the backup file to the D:\MSSQL 10.MSSQL\MSSQL\BACKUP directory so I could use it to restore the database on foghorn # \[kgomes\] On foghorn I started up SQL Server Management Studio again # \[kgomes\] # \[kgomes\] # \[kgomes\] {panel} {column} {section}]]> 19041432 8388791 8356030 19074128 Backup ...' # \[kgomes\] Accepted the defaults # \[kgomes\] Under options, I selected 'Verify after backup' # \[kgomes\] Under General, I selected 'Disk' as the destination, then clicked on 'Add...' # \[kgomes\] I added the file name '2012_12_12_2.1.1' to the default path as the file name to save it to # \[kgomes\] I then took about 15 minutes and stated it was completed successfully. # \[kgomes\] I then mapped the equinox 'backup' folder on foghorn and could then see the backup of the SQL database. # \[kgomes\] I copied the backup to the backup file to the D:\MSSQL 10.MSSQL\MSSQL\BACKUP directory so I could use it to restore the database on foghorn # \[kgomes\] On foghorn I started up SQL Server Management Studio again # \[kgomes\] # \[kgomes\] # \[kgomes\] I downloaded version 2.1.7.1, 3.4.10, 3.4.11 and 4.1.1.3 and put them in the /tmp directory on alfresco5-test.mbari.org and on alfresco5.mbari.org # \[kgomes\] # \[kgomes\] # \[kgomes\] # \[kgomes\] # \[kgomes\] # \[kgomes\] # \[kgomes\] # \[kgomes\] {panel} {column} {section}]]> 19041442 8388793 8356032 19074130 Backup ...' # \[kgomes\] Accepted the defaults # \[kgomes\] Under options, I selected 'Verify after backup' # \[kgomes\] Under General, I selected 'Disk' as the destination, then clicked on 'Add...' # \[kgomes\] I added the file name '2012_12_12_2.1.1' to the default path as the file name to save it to # \[kgomes\] I then took about 15 minutes and stated it was completed successfully. # \[kgomes\] I then mapped the equinox 'backup' folder on foghorn and could then see the backup of the SQL database. # \[kgomes\] I copied the backup to the backup file to the D:\MSSQL 10.MSSQL\MSSQL\BACKUP directory so I could use it to restore the database on foghorn # \[kgomes\] On foghorn I started up SQL Server Management Studio again # \[kgomes\] I right-clicked on the "Databases" icon and select "Restore Database..." # \[kgomes\] I entered 'Alfresco' as the "To database" name to restore to # \[kgomes\] I selected 'From Device', then clicked on the "..." button. # \[kgomes\] I left the default media of "file" and then clicked "Add..." # \[kgomes\] Then I had to select "All Files" from the "Files of Type" because I forgot to add the .bak extension when I backed it up. # \[kgomes\] Then selected OK, then OK again. # \[kgomes\] I put a check mark next to the new device entry. # \[kgomes\] I looked under "Options" and selected "Overwrite the existing database" even though I don't think it is needed in this case. # \[kgomes\] Then I clicked OK to fire it off. # \[kgomes\] # \[kgomes\] # \[kgomes\] # \[kgomes\] # \[kgomes\] I downloaded version 2.1.7.1, 3.4.10, 3.4.11 and 4.1.1.3 and put them in the /tmp directory on alfresco5-test.mbari.org and on alfresco5.mbari.org # \[kgomes\] # \[kgomes\] # \[kgomes\] # \[kgomes\] # \[kgomes\] # \[kgomes\] # \[kgomes\] # \[kgomes\] {panel} {column} {section}]]> 19041444 5407452 D0 52.08 52.08 \+0 \+0.00 D0->D1 104.17 104.17 \+0 \+0.00 D1->D2 156.25 156.25 \+0 \+0.00 D2->D3 208.33 208.33 \+0 \+0.00 D3->D4 260.42 260.42 \+0 \+0.00 D4->D5 312.50 312.50 \+0 \+0.00 D5->D6 364.58 364.58 \+0 \+0.00 D6->D7 416.67 416.67 \+0 \+0.00 D7->stopbit 468.75 468.75 \+0 \+0.00 end of stopb 520.83 520.83 \+0 \+0.00 \*/ UBR00=0xC0; UBR10=0x00; UMCTL0=0x00; /\* uart0 3686400Hz 19200bps \*/ UBR01=0xC0; UBR11=0x00; UMCTL1=0x00; /\* uart1 3686400Hz 19200bps \*/ h4. The simplest way to use the USART in UART mode is this: interrupt is not enabled, the software checks if it can output the next byte (UTXIFG = 1), and if a new character has been received (URXIFG = 1). \\ h4. Modbus Register Map * REG_INPUT_START         512         // input registers start at 512 * REG_INPUT_NREGS         8           // 8x16 bit registers * REG_SOLENOIDS_A        0            // Holding registers start at 0 (16 coils for each A and B) * REG_SOLENOIDS_B        1   * REG_HOLDING_START    0           // to match WAGO * REG_HOLDING_NREGS   40         // 40 is more than actual (2) * REG_COILS_START         0           // read individual coils (was 1000) * REG_COILS_SIZE           32          // 32 coils * REG_DISC_START          0           // discrete (was 1000) * REG_DISC_SIZE             32          // 32 coils \\ h3. ---- MODBUS * Commands ** Read Input Register (0x04) ** Read Holding Registers (0x03) ** Write Single Register (0x06) ** Write Multiple Registers (0x10) ** Read/Write Multiple Registers (0x17) ** Read Coils (0x01) ** Write Single Coil (0x05) ** Write Multiple Coils (0x0F) ** Read Discrete Inputs (0x02) ** Report Slave ID (0x11)   * Address * Slave ID  * Berlios ModBus Stack ** The modbus stack is config'd in {color:#0000ff}mbconfig.h{color} which is located in vpc\modbus\include \\ \\ ---- h3. Debugging MSP430 h4. Starting gdbproxy The next step is starting gdbproxy, which is responsible for the communication between GDB and the FET: msp430-gdbproxy \--port=2000 msp430 If your FET is properly connected to the parallel port, you should see a message like the following: info: msp430: Target device is a 'MSP430F12x' (type 11) notice: msp430-gdbproxy: waiting on TCP port 2000 h4. Using Insight (Windows) After you have started Insight (c:\msp430\bin\msp430-gdb.exe), click on "File->Open" and select the elf-file (e.g. "test.elf") you want to debug. Now click on "Run->Connect to target" and enter the following settings: Target: "Remote/TCP" Hostname: "localhost" Port: "2000" Set breakpoint at 'main': yes Set breakpoint at 'exit': yes Attach to target: yes Download Program: yes Command after attaching: "monitor erase all" Run Method: Continue from last Stop When you click on "Ok" Insight should tell you that the connection was successful, and gdbproxy should say "notice: msp430-gdbproxy: connected". To start the debugging click on "Run" or simply press "r". If everything worked correctly you should now see the sourcecode of your program with the first line of main() marked green. The red point is the breakpoint that has been set by Insight automatically. You can set or remove breakpoints by clicking on the '-' in front of the line. Now you can 'c'ontinue the execution to the next breakpoint, 's'tep through the code, or step a single assembler instruction... but be careful with "finish": Insight sometimes seems to lock up with this command. So if you want to finish a function, I recommend setting a breakpoint to the end of the function and using "continue". \\ h2. Installing the Compiler Tool Chain To obtain and install the compiler: # Go to the MSPGCC download page and obtain the latest MSPGCC installation. I used the 'mspgcc-20040723.exe' download which installed everything I needed for a Win32 setup. \\ # This step need only be performed if you wish to use the graphical version of GDB. The latest MSPGCC download only includes the command line GDB debugger. I prefer to use the graphical version called Insight. A slightly older prebuilt version of Insight can be used. Install this older version of insight into a different directory to that chosen for the latest MSPGCC installation as you don't want to overwrite the files obtained in step 1. \\ You should now have two installations. The latest version of MSPGCC installed during step 1, and a slightly older version of Insight from step 2. Both versions of the GDB debugger are called msp430-gdb.exe so one needs to be renamed. Locate the older version msp430-gdb.exe from the files installed during this step and rename it msp430-insight.exe. \\ # Ensure the BIN directory from the files installed during step 1 and the BIN directory from the files installed during step 2 are included in your PATH environment variable. \\ \\ # The MSPGCC download includes a program called msp430-gdbproxy.exe. This intercepts the GDB TCP commands and redirects them to the parallel port. Start msp430-gdbproxy (a shortcut to this will have been placed on the start menu when MSPGCC was installed). By default msp430-gdbproxy uses port 3333 - do not change this. \\ # Program the flash as per the instruction in the section above. The flash can be programmed from within GDB but it is much faster to do it separately and beforehand. \\ # Start the debugger using the command ... msp430-insight a.out... the commands in the gdb.ini file will do the rest. If you prefer to use the command line debugger simply replace msp430-insight with msp430-gdb. \\ # Insight will start at and the program will stop at the breakpoint in main() as shown below. \\ MSP430 Clocking \\ MSP430 Basic Clock Module * Clock Signals: ** *ACLK*: Auxiliary clock. The signal is sourced from LFXT1CLK with a divider of 1, 2, 4, or 8. (The calibration program for the serial link sets the divider to 4, but after the calibration it can be changed to any other values.) ACLK can be used as the clock signal for Timer A and Timer B. ** *MCLK*: Master clock. The signal can be sourced from LFXT1CLK, XT2CLK (if available), or DCOCLK with a divider of 1, 2, 4, or 8. MCLK is used by the CPU and system. ** *SMCLK*: Sub-main clock. The signal is sourced from either XT2CLK (if available), or DCOCLK with a divider of 1, 2, 4, or 8. SMCLK can be used as the clock signal for Timer A and Timer B. * MSP430 Clocking pictorial: *   * \\ !MSP430_clocking2.JPG!                  !MSP430_BCSCTL1.JPG! !MSP430_BCSCTL2.JPG!\\ \\]]> 5374721 8388788 8356027 3964986 3932219 5407454 D0 52.08 52.08 \+0 \+0.00 D0->D1 104.17 104.17 \+0 \+0.00 D1->D2 156.25 156.25 \+0 \+0.00 D2->D3 208.33 208.33 \+0 \+0.00 D3->D4 260.42 260.42 \+0 \+0.00 D4->D5 312.50 312.50 \+0 \+0.00 D5->D6 364.58 364.58 \+0 \+0.00 D6->D7 416.67 416.67 \+0 \+0.00 D7->stopbit 468.75 468.75 \+0 \+0.00 end of stopb 520.83 520.83 \+0 \+0.00 \*/ UBR00=0xC0; UBR10=0x00; UMCTL0=0x00; /\* uart0 3686400Hz 19200bps \*/ UBR01=0xC0; UBR11=0x00; UMCTL1=0x00; /\* uart1 3686400Hz 19200bps \*/ h4. The simplest way to use the USART in UART mode is this: interrupt is not enabled, the software checks if it can output the next byte (UTXIFG = 1), and if a new character has been received (URXIFG = 1). \\ h4. Modbus Register Map * REG_INPUT_START         512         // input registers start at 512 * REG_INPUT_NREGS         8           // 8x16 bit registers * REG_SOLENOIDS_A        0            // Holding registers start at 0 (16 coils for each A and B) * REG_SOLENOIDS_B        1   * REG_HOLDING_START    0           // to match WAGO * REG_HOLDING_NREGS   40         // 40 is more than actual (2) * REG_COILS_START         0           // read individual coils (was 1000) * REG_COILS_SIZE           32          // 32 coils * REG_DISC_START          0           // discrete (was 1000) * REG_DISC_SIZE             32          // 32 coils \\ h3. ---- MODBUS * Commands ** Read Input Register (0x04) ** Read Holding Registers (0x03) ** Write Single Register (0x06) ** Write Multiple Registers (0x10) ** Read/Write Multiple Registers (0x17) ** Read Coils (0x01) ** Write Single Coil (0x05) ** Write Multiple Coils (0x0F) ** Read Discrete Inputs (0x02) ** Report Slave ID (0x11)   * Address * Slave ID  * Berlios ModBus Stack ** The modbus stack is config'd in {color:#0000ff}mbconfig.h{color} which is located in vpc\modbus\include \\ \\ ---- h3. Debugging MSP430 h4. Starting gdbproxy The next step is starting gdbproxy, which is responsible for the communication between GDB and the FET: msp430-gdbproxy \--port=2000 msp430 If your FET is properly connected to the parallel port, you should see a message like the following: info: msp430: Target device is a 'MSP430F12x' (type 11) notice: msp430-gdbproxy: waiting on TCP port 2000 h4. Using Insight (Windows) After you have started Insight (c:\msp430\bin\msp430-gdb.exe), click on "File->Open" and select the elf-file (e.g. "test.elf") you want to debug. Now click on "Run->Connect to target" and enter the following settings: Target: "Remote/TCP" Hostname: "localhost" Port: "2000" Set breakpoint at 'main': yes Set breakpoint at 'exit': yes Attach to target: yes Download Program: yes Command after attaching: "monitor erase all" Run Method: Continue from last Stop When you click on "Ok" Insight should tell you that the connection was successful, and gdbproxy should say "notice: msp430-gdbproxy: connected". To start the debugging click on "Run" or simply press "r". If everything worked correctly you should now see the sourcecode of your program with the first line of main() marked green. The red point is the breakpoint that has been set by Insight automatically. You can set or remove breakpoints by clicking on the '-' in front of the line. Now you can 'c'ontinue the execution to the next breakpoint, 's'tep through the code, or step a single assembler instruction... but be careful with "finish": Insight sometimes seems to lock up with this command. So if you want to finish a function, I recommend setting a breakpoint to the end of the function and using "continue". \\ h2. Installing the Compiler Tool Chain To obtain and install the compiler: # Go to the MSPGCC download page and obtain the latest MSPGCC installation. I used the 'mspgcc-20040723.exe' download which installed everything I needed for a Win32 setup. \\ # This step need only be performed if you wish to use the graphical version of GDB. The latest MSPGCC download only includes the command line GDB debugger. I prefer to use the graphical version called Insight. A slightly older prebuilt version of Insight can be used. Install this older version of insight into a different directory to that chosen for the latest MSPGCC installation as you don't want to overwrite the files obtained in step 1. \\ You should now have two installations. The latest version of MSPGCC installed during step 1, and a slightly older version of Insight from step 2. Both versions of the GDB debugger are called msp430-gdb.exe so one needs to be renamed. Locate the older version msp430-gdb.exe from the files installed during this step and rename it msp430-insight.exe. \\ # Ensure the BIN directory from the files installed during step 1 and the BIN directory from the files installed during step 2 are included in your PATH environment variable. \\ \\ # The MSPGCC download includes a program called msp430-gdbproxy.exe. This intercepts the GDB TCP commands and redirects them to the parallel port. Start msp430-gdbproxy (a shortcut to this will have been placed on the start menu when MSPGCC was installed). By default msp430-gdbproxy uses port 3333 - do not change this. \\ # Program the flash as per the instruction in the section above. The flash can be programmed from within GDB but it is much faster to do it separately and beforehand. \\ # Start the debugger using the command ... msp430-insight a.out... the commands in the gdb.ini file will do the rest. If you prefer to use the command line debugger simply replace msp430-insight with msp430-gdb. \\ # Insight will start at and the program will stop at the breakpoint in main() as shown below. \\ MSP430 Clocking \\ MSP430 Basic Clock Module * Clock Signals: ** *ACLK*: Auxiliary clock. The signal is sourced from LFXT1CLK with a divider of 1, 2, 4, or 8. (The calibration program for the serial link sets the divider to 4, but after the calibration it can be changed to any other values.) ACLK can be used as the clock signal for Timer A and Timer B. ** *MCLK*: Master clock. The signal can be sourced from LFXT1CLK, XT2CLK (if available), or DCOCLK with a divider of 1, 2, 4, or 8. MCLK is used by the CPU and system. ** *SMCLK*: Sub-main clock. The signal is sourced from either XT2CLK (if available), or DCOCLK with a divider of 1, 2, 4, or 8. SMCLK can be used as the clock signal for Timer A and Timer B. * MSP430 Clocking pictorial: *   * \\ !MSP430_clocking2.JPG!                  !MSP430_BCSCTL1.JPG! !MSP430_BCSCTL2.JPG!\\ \\]]> 5374723 8388789 8356028 8388783 8356022 8388785 8356024 8388786 8356025 5407427 ... mbari MBARI Repository http://oceana.shore.mbari.org/maven2 ... ... {code} h3. Including a Dependency from the Repository Once the MBARI repository is included in you build, you can browse the repository to see what projects are available (just go to [http://oceana.shore.mbari.org/maven2]). If you find a dependency you need you can reference it in your _pom.xml_. Here's an example... {code:xml} ... ... qt4j qt4j 0.5 ... ... {code} h3. Putting a Dependency into the Repository The easiest way to put a dependency into the repository is to setup a Maven build file (i.e. _pom.xml_). In _pom.xml_ add the following _distributionManagement_ information: {code:xml} 4.0.0 qt4j qt4j jar 1.0-SNAPSHOT QT4J ... mbari-repository MBARI Repository scp://oceana.shore.mbari.org/var/www/html/maven2 {code} Executing _mvn deploy_ will put your build jar at http://oceana.shore.mbari.org/maven2////-.jar. In the example here it would put it into [http://oceana.shore.mbari.org/maven2/qt4j/qt4j/1.0-SNAPSHOT/] h3. Publishing Maven generated web sites Maven can generate a web site for a default web site for you. You can view samples of the currently published projects at [http://oceana.shore.mbari.org/projects]. It's not very interesting, however, it is a very simple way to publish the javadoc, sources and auto-generated reports. To do so modify your _pom.xml_: {code:xml} ... org.apache.maven.plugins maven-jxr-plugin org.apache.maven.plugins maven-pmd-plugin 1.5 org.apache.maven.plugins maven-checkstyle-plugin ... oceana.shore.mbari.org scp://oceana.shore.mbari.org/var/www/html/projects/${project.name} {code} Then run _mvn javadoc:javadoc site:site site:deploy_. This will build the javadocs, create a site with some useful reports, then publish the site (using scp) to oceana in the correct location. h3. Project Specific Maven Repositories Some projects may need to be configured differently for different deployment locations. For example, [VARS|VARS:Home] is configured differently for each ship and shore. These specific configurations are stored in Maven repositories in [http://oceana.shore.mbari.org/maven2-prj]. Each directory listed there is a different repository. Here's an example of how to include the projects configured for [Eye-in-the-sea|EITS:Home]. {code:xml} mbari-eits MBARI-EITS Repository http://oceana.shore.mbari.org/maven2-prj/eits {code} h2. {anchor:M3} +Using the external MBARI repository from an [Ant|http://ant.apache.org] project using Maven+ Maven repositories can be used from Ant build scripts using [Maven's antlib|http://maven.apache.org/ant-tasks.html]. To do this you must have both Maven and Ant installed. h3. Bootstrapping antlib To bootstrap antlib into your projects (so users can build without having to install antlib) modify your _build.xml_ file like so: {code:xml} ... Finding dependencies of ${pom.artifactId}-${version} ... {code} h2. {anchor:M4} +Using the external MBARI repository from an [Ant|http://ant.apache.org] project using Ivy+ Maven repositories can be used from Ant build scripts using [Ivy|http://incubator.apache.org/ivy/]. h3. Referencing the repository In the directory containing the ant build file, _build.xml_, create a file called _ivyconf.xml_. _ivyconf.xml_ tells Ivy where to look for dependencies. The contents of the file will look something like: {code:xml} {code} h3. Including a Dependency from the Repository In the directory containing _build.xml_, create a file called _ivy.xml_. _ivy.xml_ tells Ivy what dependencies to include in your build. Here's an example of it's contents: {code:xml} {code} h3. Using Ivy from Ant The code below will fetch Ivy for you. SO you do not need install any additional software in order to get you build to work. In your ant build file include the following: {code:xml} ... {code} Calling _ant ivy.install_ will fetch all the dependencies from the web and put them into the _lib_ directory of your project. ]]> 5374696 19074132 Backup ...' # \[kgomes\] Accepted the defaults # \[kgomes\] Under options, I selected 'Verify after backup' # \[kgomes\] Under General, I selected 'Disk' as the destination, then clicked on 'Add...' # \[kgomes\] I added the file name '2012_12_12_2.1.1' to the default path as the file name to save it to # \[kgomes\] I then took about 15 minutes and stated it was completed successfully. # \[kgomes\] I then mapped the equinox 'backup' folder on foghorn and could then see the backup of the SQL database. # \[kgomes\] I copied the backup to the backup file to the D:\MSSQL 10.MSSQL\MSSQL\BACKUP directory so I could use it to restore the database on foghorn # \[kgomes\] On foghorn I started up SQL Server Management Studio again # \[kgomes\] I right-clicked on the "Databases" icon and select "Restore Database..." # \[kgomes\] I entered 'Alfresco' as the "To database" name to restore to # \[kgomes\] I selected 'From Device', then clicked on the "..." button. # \[kgomes\] I left the default media of "file" and then clicked "Add..." # \[kgomes\] Then I had to select "All Files" from the "Files of Type" because I forgot to add the .bak extension when I backed it up. # \[kgomes\] Then selected OK, then OK again. # \[kgomes\] I put a check mark next to the new device entry. # \[kgomes\] I looked under "Options" and selected "Overwrite the existing database" even though I don't think it is needed in this case. # \[kgomes\] Then I clicked OK to fire it off. # \[kgomes\] After this, Neil and I noticed that the schema being used on the tables was 'LAGOON\DB_Collaboration'. Neil wanted to change that to 'dbo'. He made the change and we may have to edit the JTDS driver URL to use that schema specifically (if it works at all). # \[kgomes\] I then logged into alfresco.mbari.org and copied the 'lucence-indexes' directory on the D:\alf_data to the 2012_12_12_2.1.1 directory on atlas\Alfresco so that we had a backup of the indexes. # \[kgomes\] I copied the database backup from equinox to the same share so we had all three: content store, database backup and lucene-indexes all in one spot. # \[kgomes\] I downloaded version 2.1.7.1, 3.4.10, 3.4.11 and 4.1.1.3 and put them in the /tmp directory on alfresco5-test.mbari.org and on alfresco5.mbari.org # \[kgomes\] I put a README.txt file in this same directory to explain all this. {panel} {column} {section}]]> 19041446 5407429 ... mbari MBARI Repository http://oceana.shore.mbari.org/maven2 ... ... {code} h2. {anchor:M2} +Using the external MBARI repository from a [Maven 2|http://maven.apache.org/] project+ h3. Referencing the Repository To include the MBARI repository in your Maven build, edit your _pom.xml_ to include the MBARI repository location: {code:xml} ... mbari MBARI Repository http://oceana.shore.mbari.org/maven2 ... ... {code} h3. Including a Dependency from the Repository Once the MBARI repository is included in you build, you can browse the repository to see what projects are available (just go to [http://oceana.shore.mbari.org/maven2]). If you find a dependency you need you can reference it in your _pom.xml_. Here's an example... {code:xml} ... ... qt4j qt4j 0.5 ... ... {code} h3. Putting a Dependency into the Repository The easiest way to put a dependency into the repository is to setup a Maven build file (i.e. _pom.xml_). In _pom.xml_ add the following _distributionManagement_ information: {code:xml} 4.0.0 qt4j qt4j jar 1.0-SNAPSHOT QT4J ... mbari-repository MBARI Repository scp://oceana.shore.mbari.org/var/www/html/maven2 {code} Executing _mvn deploy_ will put your build jar at http://oceana.shore.mbari.org/maven2////-.jar. In the example here it would put it into [http://oceana.shore.mbari.org/maven2/qt4j/qt4j/1.0-SNAPSHOT/] h3. Publishing Maven generated web sites Maven can generate a web site for a default web site for you. You can view samples of the currently published projects at [http://oceana.shore.mbari.org/projects]. It's not very interesting, however, it is a very simple way to publish the javadoc, sources and auto-generated reports. To do so modify your _pom.xml_: {code:xml} ... org.apache.maven.plugins maven-jxr-plugin org.apache.maven.plugins maven-pmd-plugin 1.5 org.apache.maven.plugins maven-checkstyle-plugin ... oceana.shore.mbari.org scp://oceana.shore.mbari.org/var/www/html/projects/${project.name} {code} Then run _mvn javadoc:javadoc site:site site:deploy_. This will build the javadocs, create a site with some useful reports, then publish the site (using scp) to oceana in the correct location. h3. Project Specific Maven Repositories Some projects may need to be configured differently for different deployment locations. For example, [VARS|VARS:Home] is configured differently for each ship and shore. These specific configurations are stored in Maven repositories in [http://oceana.shore.mbari.org/maven2-prj]. Each directory listed there is a different repository. Here's an example of how to include the projects configured for [Eye-in-the-sea|EITS:Home]. {code:xml} mbari-eits MBARI-EITS Repository http://oceana.shore.mbari.org/maven2-prj/eits {code} h2. {anchor:M3} +Using the external MBARI repository from an [Ant|http://ant.apache.org] project using Maven+ Maven repositories can be used from Ant build scripts using [Maven's antlib|http://maven.apache.org/ant-tasks.html]. To do this you must have both Maven and Ant installed. h3. Bootstrapping antlib To bootstrap antlib into your projects (so users can build without having to install antlib) modify your _build.xml_ file like so: {code:xml} ... Finding dependencies of ${pom.artifactId}-${version} ... {code} h2. {anchor:M4} +Using the external MBARI repository from an [Ant|http://ant.apache.org] project using Ivy+ Maven repositories can be used from Ant build scripts using [Ivy|http://incubator.apache.org/ivy/]. h3. Referencing the repository In the directory containing the ant build file, _build.xml_, create a file called _ivyconf.xml_. _ivyconf.xml_ tells Ivy where to look for dependencies. The contents of the file will look something like: {code:xml} {code} h3. Including a Dependency from the Repository In the directory containing _build.xml_, create a file called _ivy.xml_. _ivy.xml_ tells Ivy what dependencies to include in your build. Here's an example of it's contents: {code:xml} {code} h3. Using Ivy from Ant The code below will fetch Ivy for you. SO you do not need install any additional software in order to get you build to work. In your ant build file include the following: {code:xml} ... {code} Calling _ant ivy.install_ will fetch all the dependencies from the web and put them into the _lib_ directory of your project. ]]> 5374698 5407440 D0 52.08 52.08 \+0 \+0.00 D0->D1 104.17 104.17 \+0 \+0.00 D1->D2 156.25 156.25 \+0 \+0.00 D2->D3 208.33 208.33 \+0 \+0.00 D3->D4 260.42 260.42 \+0 \+0.00 D4->D5 312.50 312.50 \+0 \+0.00 D5->D6 364.58 364.58 \+0 \+0.00 D6->D7 416.67 416.67 \+0 \+0.00 D7->stopbit 468.75 468.75 \+0 \+0.00 end of stopb 520.83 520.83 \+0 \+0.00 \*/ UBR00=0xC0; UBR10=0x00; UMCTL0=0x00; /\* uart0 3686400Hz 19200bps \*/ UBR01=0xC0; UBR11=0x00; UMCTL1=0x00; /\* uart1 3686400Hz 19200bps \*/ h4. The simplest way to use the USART in UART mode is this: interrupt is not enabled, the software checks if it can output the next byte (UTXIFG = 1), and if a new character has been received (URXIFG = 1). \\ h4. Modbus Register Map * REG_INPUT_START         512         // input registers start at 512 * REG_INPUT_NREGS         8           // 8x16 bit registers * REG_SOLENOIDS_A        0            // Holding registers start at 0 (16 coils for each A and B) * REG_SOLENOIDS_B        1   * REG_HOLDING_START    0           // to match WAGO * REG_HOLDING_NREGS   40         // 40 is more than actual (2) * REG_COILS_START         0           // read individual coils (was 1000) * REG_COILS_SIZE           32          // 32 coils * REG_DISC_START          0           // discrete (was 1000) * REG_DISC_SIZE             32          // 32 coils \\ h3. ---- MODBUS * Commands ** Read Input Register (0x04) ** Read Holding Registers (0x03) ** Write Single Register (0x06) ** Write Multiple Registers (0x10) ** Read/Write Multiple Registers (0x17) ** Read Coils (0x01) ** Write Single Coil (0x05) ** Write Multiple Coils (0x0F) ** Read Discrete Inputs (0x02) ** Report Slave ID (0x11)   * Address * Slave ID  * Berlios ModBus Stack ** The modbus stack is config'd in {color:#0000ff}mbconfig.h{color} which is located in vpc\modbus\include \\ \\ ---- h3. Debugging MSP430 h4. Starting gdbproxy The next step is starting gdbproxy, which is responsible for the communication between GDB and the FET: msp430-gdbproxy \--port=2000 msp430 If your FET is properly connected to the parallel port, you should see a message like the following: info: msp430: Target device is a 'MSP430F12x' (type 11) notice: msp430-gdbproxy: waiting on TCP port 2000 h4. Using Insight (Windows) After you have started Insight (c:\msp430\bin\msp430-gdb.exe), click on "File->Open" and select the elf-file (e.g. "test.elf") you want to debug. Now click on "Run->Connect to target" and enter the following settings: Target: "Remote/TCP" Hostname: "localhost" Port: "2000" Set breakpoint at 'main': yes Set breakpoint at 'exit': yes Attach to target: yes Download Program: yes Command after attaching: "monitor erase all" Run Method: Continue from last Stop When you click on "Ok" Insight should tell you that the connection was successful, and gdbproxy should say "notice: msp430-gdbproxy: connected". To start the debugging click on "Run" or simply press "r". If everything worked correctly you should now see the sourcecode of your program with the first line of main() marked green. The red point is the breakpoint that has been set by Insight automatically. You can set or remove breakpoints by clicking on the '-' in front of the line. Now you can 'c'ontinue the execution to the next breakpoint, 's'tep through the code, or step a single assembler instruction... but be careful with "finish": Insight sometimes seems to lock up with this command. So if you want to finish a function, I recommend setting a breakpoint to the end of the function and using "continue". \\ h2. Installing the Compiler Tool Chain To obtain and install the compiler: # Go to the MSPGCC download page and obtain the latest MSPGCC installation. I used the 'mspgcc-20040723.exe' download which installed everything I needed for a Win32 setup. \\ # This step need only be performed if you wish to use the graphical version of GDB. The latest MSPGCC download only includes the command line GDB debugger. I prefer to use the graphical version called Insight. A slightly older prebuilt version of Insight can be used. Install this older version of insight into a different directory to that chosen for the latest MSPGCC installation as you don't want to overwrite the files obtained in step 1. \\ You should now have two installations. The latest version of MSPGCC installed during step 1, and a slightly older version of Insight from step 2. Both versions of the GDB debugger are called msp430-gdb.exe so one needs to be renamed. Locate the older version msp430-gdb.exe from the files installed during this step and rename it msp430-insight.exe. \\ # Ensure the BIN directory from the files installed during step 1 and the BIN directory from the files installed during step 2 are included in your PATH environment variable. \\ \\ # The MSPGCC download includes a program called msp430-gdbproxy.exe. This intercepts the GDB TCP commands and redirects them to the parallel port. Start msp430-gdbproxy (a shortcut to this will have been placed on the start menu when MSPGCC was installed). By default msp430-gdbproxy uses port 3333 - do not change this. \\ # Program the flash as per the instruction in the section above. The flash can be programmed from within GDB but it is much faster to do it separately and beforehand. \\ # Start the debugger using the command ... msp430-insight a.out... the commands in the gdb.ini file will do the rest. If you prefer to use the command line debugger simply replace msp430-insight with msp430-gdb. \\ # Insight will start at and the program will stop at the breakpoint in main() as shown below. \\ MSP430 Clocking \\ MSP430 Basic Clock Module * Clock Signals: ** *ACLK*: Auxiliary clock. The signal is sourced from LFXT1CLK with a divider of 1, 2, 4, or 8. (The calibration program for the serial link sets the divider to 4, but after the calibration it can be changed to any other values.) ACLK can be used as the clock signal for Timer A and Timer B. ** *MCLK*: Master clock. The signal can be sourced from LFXT1CLK, XT2CLK (if available), or DCOCLK with a divider of 1, 2, 4, or 8. MCLK is used by the CPU and system. ** *SMCLK*: Sub-main clock. The signal is sourced from either XT2CLK (if available), or DCOCLK with a divider of 1, 2, 4, or 8. SMCLK can be used as the clock signal for Timer A and Timer B. * MSP430 Clocking pictorial: *   * \\ !MSP430_clocking2.JPG!                  !MSP430_BCSCTL1.JPG! !MSP430_BCSCTL2.JPG!\\ \\]]> 5374709 3670819 3638074 28409859 2.7.4 -> 3.5.17 -> 5.0.3 -> latest (5.8 at time of writing this) h5. Steps # I.S. created a new VM named pompeii.shore.mbari.org that I will use to do all the stepwise upgrades # Java 1.6.0_36 was installed, so I asked for an update to the latest 1.8 version # I.S. created four databases for the upgrade path. # Per the installation instructions, for each of these databases, I performed the following using Aqua Data Studio {noformat} ALTER DATABASE COLLATE SQL_Latin1_General_CP1_CS_AS {noformat} # Per the installation instructions, for each database, I ran: {noformat} ALTER DATABASE SET READ_COMMITTED_SNAPSHOT ON WITH ROLLBACK IMMEDIATE; {noformat} # I VNC'd into pompeii.shore.mbari.org and fired up Firefox. # I downloaded the .tar.gz versions of the standalone for all the versions listed above. # I went to the Confluence Administration panel and went to Backup and Restore # I selected both the Backup check boxes and clicked "Backup" # The backup completed and I downloaded the 1.3 GB file.]]> 28377091 11273135 Accessories  --> Communications  --> Hyperterm  --> McStar USBser 115200 ** 115200, 8n1, no flow, COM5 * Step 4 - remove magnet from McSTAR 'white spot' ** If no activity, hit ENTER a couple of times and put magnet on white spot and remove. ** Should see a boot screen, do not hit a key to stop autoboot \\ h4. McSTAR Functional Test    •Step 1 - in Hyperterm, after McSTAR has booted, login with by entering 'root' \-JFFS2 message is harmless, but if login not seen due to JFFS2 message, hit ENTER a couple of times. •Step 2 - cd /media/sda1 (USB harddisk connected to McStar) \-List (ls) should show app dir •Step 3 - 'cd /media/sda1/app/scripts' •Step 4 - type 'date', then type 'date \-s "Tue Mar 09 10:54:30 PST 2010"' •Step 4 - start the McSTAR app './run_mcstar.sh' \-Allow it to run until the first recording message comes out.   Say stuff, whistle, whisper, etc. every 10 seconds or so (data blocks vary from 2 to 20 minutes; typically 5 minutes). \-After the first recording data message, hit Ctrl-c (terminate McSTAR data collection). \-"Writing a new audio file D000000..."  h4. Verification •Step 1 - after terminating run_mcstar.sh   In Hyperterm, change directories to the data directory. \-cd /media/sda1/data \-Cd to the latest directory, then cd to R00000 •Find the file and transfer \-In Hyperterm, Transfer  \--> Receive File, use Zmodem (no crash recovery). Close \-In hyperterm, tell McSTAR to transfer the file you recorded • sz D00000 •On the HP Netbook, start Audacity On Windows •Project  \--> Import Raw Data \-Accept the defaults, and change 44100 to 48000 On a Mac •File  \--> Import  \--> Raw Data... •select file •open file and accept default settings except Sample Rate - change from default value of 44100 Hz to 48000 Hz (sampling rate of McSTAR). \\]]> 11240397 11273136 Accessories  \--> Communications  \--> Hyperterm  \--> McStar USBser 115200 ** 115200, 8n1, no flow, COM5 * Step 4 - remove magnet from McSTAR 'white spot' ** If no activity, hit ENTER a couple of times and put magnet on white spot and remove. ** Should see a boot screen, do not hit a key to stop autoboot \\ h4. McSTAR Functional Test    •Step 1 - in Hyperterm, after McSTAR has booted, login with by entering 'root' \-JFFS2 message is harmless, but if login not seen due to JFFS2 message, hit ENTER a couple of times. •Step 2 - cd /media/sda1 (USB harddisk connected to McStar) \-List (ls) should show app dir •Step 3 - 'cd /media/sda1/app/scripts' •Step 4 - type 'date', then type 'date \-s "Tue Mar 09 10:54:30 PST 2010"' •Step 4 - start the McSTAR app './run_mcstar.sh' \-Allow it to run until the first recording message comes out.   Say stuff, whistle, whisper, etc. every 10 seconds or so (data blocks vary from 2 to 20 minutes; typically 5 minutes). \-After the first recording data message, hit Ctrl-c (terminate McSTAR data collection). \-"Writing a new audio file D000000..."  h4. Verification •Step 1 - after terminating run_mcstar.sh   In Hyperterm, change directories to the data directory. \-cd /media/sda1/data \-Cd to the latest directory, then cd to R00000 •Find the file and transfer \-In Hyperterm, Transfer  \--> Receive File, use Zmodem (no crash recovery). Close \-In hyperterm, tell McSTAR to transfer the file you recorded • sz D00000 •On the HP Netbook, start Audacity On Windows •Project  \--> Import Raw Data \-Accept the defaults, and change 44100 to 48000 On a Mac •File  --> Import  --> Raw Data... •select file •open file and accept default settings except Sample Rate - change from default value of 44100 Hz to 48000 Hz (sampling rate of McSTAR). \\]]> 11240398 5407413 D0 52.08 52.08 \+0 \+0.00 D0->D1 104.17 104.17 \+0 \+0.00 D1->D2 156.25 156.25 \+0 \+0.00 D2->D3 208.33 208.33 \+0 \+0.00 D3->D4 260.42 260.42 \+0 \+0.00 D4->D5 312.50 312.50 \+0 \+0.00 D5->D6 364.58 364.58 \+0 \+0.00 D6->D7 416.67 416.67 \+0 \+0.00 D7->stopbit 468.75 468.75 \+0 \+0.00 end of stopb 520.83 520.83 \+0 \+0.00 \*/ UBR00=0xC0; UBR10=0x00; UMCTL0=0x00; /\* uart0 3686400Hz 19200bps \*/ UBR01=0xC0; UBR11=0x00; UMCTL1=0x00; /\* uart1 3686400Hz 19200bps \*/ h4. The simplest way to use the USART in UART mode is this: interrupt is not enabled, the software checks if it can output the next byte (UTXIFG = 1), and if a new character has been received (URXIFG = 1). \\ h4. Modbus Register Map * REG_INPUT_START         512         // input registers start at 512 * REG_INPUT_NREGS         8           // 8x16 bit registers * REG_SOLENOIDS_A        0            // Holding registers start at 0 (16 coils for each A and B) * REG_SOLENOIDS_B        1   * REG_HOLDING_START    0           // to match WAGO * REG_HOLDING_NREGS   40         // 40 is more than actual (2) * REG_COILS_START         0           // read individual coils (was 1000) * REG_COILS_SIZE           32          // 32 coils * REG_DISC_START          0           // discrete (was 1000) * REG_DISC_SIZE             32          // 32 coils \\ h3. ---- MODBUS * Commands ** Read Input Register (0x04) ** Read Holding Registers (0x03) ** Write Single Register (0x06) ** Write Multiple Registers (0x10) ** Read/Write Multiple Registers (0x17) ** Read Coils (0x01) ** Write Single Coil (0x05) ** Write Multiple Coils (0x0F) ** Read Discrete Inputs (0x02) ** Report Slave ID (0x11)   * Address * Slave ID  * Berlios ModBus Stack ** The modbus stack is config'd in {color:#0000ff}mbconfig.h{color} which is located in vpc\modbus\include \\ \\ ---- h3. Debugging MSP430 h4. Starting gdbproxy The next step is starting gdbproxy, which is responsible for the communication between GDB and the FET: msp430-gdbproxy \--port=2000 msp430 If your FET is properly connected to the parallel port, you should see a message like the following: info: msp430: Target device is a 'MSP430F12x' (type 11) notice: msp430-gdbproxy: waiting on TCP port 2000 h4. Using Insight (Windows) After you have started Insight (c:\msp430\bin\msp430-gdb.exe), click on "File->Open" and select the elf-file (e.g. "test.elf") you want to debug. Now click on "Run->Connect to target" and enter the following settings: Target: "Remote/TCP" Hostname: "localhost" Port: "2000" Set breakpoint at 'main': yes Set breakpoint at 'exit': yes Attach to target: yes Download Program: yes Command after attaching: "monitor erase all" Run Method: Continue from last Stop When you click on "Ok" Insight should tell you that the connection was successful, and gdbproxy should say "notice: msp430-gdbproxy: connected". To start the debugging click on "Run" or simply press "r". If everything worked correctly you should now see the sourcecode of your program with the first line of main() marked green. The red point is the breakpoint that has been set by Insight automatically. You can set or remove breakpoints by clicking on the '-' in front of the line. Now you can 'c'ontinue the execution to the next breakpoint, 's'tep through the code, or step a single assembler instruction... but be careful with "finish": Insight sometimes seems to lock up with this command. So if you want to finish a function, I recommend setting a breakpoint to the end of the function and using "continue". \\ h2. Installing the Compiler Tool Chain To obtain and install the compiler: # Go to the MSPGCC download page and obtain the latest MSPGCC installation. I used the 'mspgcc-20040723.exe' download which installed everything I needed for a Win32 setup. \\ # This step need only be performed if you wish to use the graphical version of GDB. The latest MSPGCC download only includes the command line GDB debugger. I prefer to use the graphical version called Insight. A slightly older prebuilt version of Insight can be used. Install this older version of insight into a different directory to that chosen for the latest MSPGCC installation as you don't want to overwrite the files obtained in step 1. \\ You should now have two installations. The latest version of MSPGCC installed during step 1, and a slightly older version of Insight from step 2. Both versions of the GDB debugger are called msp430-gdb.exe so one needs to be renamed. Locate the older version msp430-gdb.exe from the files installed during this step and rename it msp430-insight.exe. \\ # Ensure the BIN directory from the files installed during step 1 and the BIN directory from the files installed during step 2 are included in your PATH environment variable. \\ \\ # The MSPGCC download includes a program called msp430-gdbproxy.exe. This intercepts the GDB TCP commands and redirects them to the parallel port. Start msp430-gdbproxy (a shortcut to this will have been placed on the start menu when MSPGCC was installed). By default msp430-gdbproxy uses port 3333 - do not change this. \\ # Program the flash as per the instruction in the section above. The flash can be programmed from within GDB but it is much faster to do it separately and beforehand. \\ # Start the debugger using the command ... msp430-insight a.out... the commands in the gdb.ini file will do the rest. If you prefer to use the command line debugger simply replace msp430-insight with msp430-gdb. \\ # Insight will start at and the program will stop at the breakpoint in main() as shown below. \\ MSP430 Clocking \\ MSP430 Basic Clock Module * Clock Signals: ** *ACLK*: Auxiliary clock. The signal is sourced from LFXT1CLK with a divider of 1, 2, 4, or 8. (The calibration program for the serial link sets the divider to 4, but after the calibration it can be changed to any other values.) ACLK can be used as the clock signal for Timer A and Timer B. ** *MCLK*: Master clock. The signal can be sourced from LFXT1CLK, XT2CLK (if available), or DCOCLK with a divider of 1, 2, 4, or 8. MCLK is used by the CPU and system. ** *SMCLK*: Sub-main clock. The signal is sourced from either XT2CLK (if available), or DCOCLK with a divider of 1, 2, 4, or 8. SMCLK can be used as the clock signal for Timer A and Timer B. * MSP430 Clocking pictorial: *   * \\ !MSP430_clocking2.JPG!                  !MSP430_BCSCTL1.JPG! !MSP430_BCSCTL2.JPG!\\ \\]]> 5374682 11273137 Accessories  \--> Communications  \--> Hyperterm  \--> McStar USBser 115200 ** 115200, 8n1, no flow, COM5 * Step 4 - remove magnet from McSTAR 'white spot' ** If no activity, hit ENTER a couple of times and put magnet on white spot and remove. ** Should see a boot screen, do not hit a key to stop autoboot \\ h4. McSTAR Functional Test    •Step 1 - in Hyperterm, after McSTAR has booted, login with by entering 'root' \-JFFS2 message is harmless, but if login not seen due to JFFS2 message, hit ENTER a couple of times. •Step 2 - cd /media/sda1 (USB harddisk connected to McStar) \-List (ls) should show app dir •Step 3 - 'cd /media/sda1/app/scripts' •Step 4 - type 'date', then type 'date \-s "Tue Mar 09 10:54:30 PST 2010"' •Step 4 - start the McSTAR app './run_mcstar.sh' \-Allow it to run until the first recording message comes out.   Say stuff, whistle, whisper, etc. every 10 seconds or so (data blocks vary from 2 to 20 minutes; typically 5 minutes). \-After the first recording data message, hit Ctrl-c (terminate McSTAR data collection). \-"Writing a new audio file D000000..."  h4. Verification •Step 1 - after terminating run_mcstar.sh   In Hyperterm, change directories to the data directory. \-cd /media/sda1/data \-Cd to the latest directory, then cd to R00000 •Find the file and transfer \-In Hyperterm, Transfer  \--> Receive File, use Zmodem (no crash recovery). Close \-In hyperterm, tell McSTAR to transfer the file you recorded • sz D00000 •On the HP Netbook, start Audacity On Windows •Project  \--> Import Raw Data \-Accept the defaults, and change 44100 to 48000 On a Mac •File  \--> Import  \--> Raw Data... •select file •open file and accept default settings except Sample Rate - change from default value of 44100 Hz to 48000 Hz (sampling rate of McSTAR). \\]]> 11240399 5407411 D0 52.08 52.08 \+0 \+0.00 D0->D1 104.17 104.17 \+0 \+0.00 D1->D2 156.25 156.25 \+0 \+0.00 D2->D3 208.33 208.33 \+0 \+0.00 D3->D4 260.42 260.42 \+0 \+0.00 D4->D5 312.50 312.50 \+0 \+0.00 D5->D6 364.58 364.58 \+0 \+0.00 D6->D7 416.67 416.67 \+0 \+0.00 D7->stopbit 468.75 468.75 \+0 \+0.00 end of stopb 520.83 520.83 \+0 \+0.00 \*/ UBR00=0xC0; UBR10=0x00; UMCTL0=0x00; /\* uart0 3686400Hz 19200bps \*/ UBR01=0xC0; UBR11=0x00; UMCTL1=0x00; /\* uart1 3686400Hz 19200bps \*/ h4. The simplest way to use the USART in UART mode is this: interrupt is not enabled, the software checks if it can output the next byte (UTXIFG = 1), and if a new character has been received (URXIFG = 1). \\ h4. Modbus Register Map * REG_INPUT_START         512         // input registers start at 512 * REG_INPUT_NREGS         8           // 8x16 bit registers * REG_SOLENOIDS_A        0            // Holding registers start at 0 (16 coils for each A and B) * REG_SOLENOIDS_B        1   * REG_HOLDING_START    0           // to match WAGO * REG_HOLDING_NREGS   40         // 40 is more than actual (2) * REG_COILS_START         0           // read individual coils (was 1000) * REG_COILS_SIZE           32          // 32 coils * REG_DISC_START          0           // discrete (was 1000) * REG_DISC_SIZE             32          // 32 coils \\ h3. ---- MODBUS * Commands ** Read Input Register (0x04) ** Read Holding Registers (0x03) ** Write Single Register (0x06) ** Write Multiple Registers (0x10) ** Read/Write Multiple Registers (0x17) ** Read Coils (0x01) ** Write Single Coil (0x05) ** Write Multiple Coils (0x0F) ** Read Discrete Inputs (0x02) ** Report Slave ID (0x11)   * Address * Slave ID  * Berlios ModBus Stack ** The modbus stack is config'd in {color:#0000ff}mbconfig.h{color} which is located in vpc\modbus\include \\ \\ ---- h3. Debugging MSP430 h4. Starting gdbproxy The next step is starting gdbproxy, which is responsible for the communication between GDB and the FET: msp430-gdbproxy \--port=2000 msp430 If your FET is properly connected to the parallel port, you should see a message like the following: info: msp430: Target device is a 'MSP430F12x' (type 11) notice: msp430-gdbproxy: waiting on TCP port 2000 h4. Using Insight (Windows) After you have started Insight (c:\msp430\bin\msp430-gdb.exe), click on "File->Open" and select the elf-file (e.g. "test.elf") you want to debug. Now click on "Run->Connect to target" and enter the following settings: Target: "Remote/TCP" Hostname: "localhost" Port: "2000" Set breakpoint at 'main': yes Set breakpoint at 'exit': yes Attach to target: yes Download Program: yes Command after attaching: "monitor erase all" Run Method: Continue from last Stop When you click on "Ok" Insight should tell you that the connection was successful, and gdbproxy should say "notice: msp430-gdbproxy: connected". To start the debugging click on "Run" or simply press "r". If everything worked correctly you should now see the sourcecode of your program with the first line of main() marked green. The red point is the breakpoint that has been set by Insight automatically. You can set or remove breakpoints by clicking on the '-' in front of the line. Now you can 'c'ontinue the execution to the next breakpoint, 's'tep through the code, or step a single assembler instruction... but be careful with "finish": Insight sometimes seems to lock up with this command. So if you want to finish a function, I recommend setting a breakpoint to the end of the function and using "continue". \\ h2. Installing the Compiler Tool Chain To obtain and install the compiler: # Go to the MSPGCC download page and obtain the latest MSPGCC installation. I used the 'mspgcc-20040723.exe' download which installed everything I needed for a Win32 setup. \\ # This step need only be performed if you wish to use the graphical version of GDB. The latest MSPGCC download only includes the command line GDB debugger. I prefer to use the graphical version called Insight. A slightly older prebuilt version of Insight can be used. Install this older version of insight into a different directory to that chosen for the latest MSPGCC installation as you don't want to overwrite the files obtained in step 1. \\ You should now have two installations. The latest version of MSPGCC installed during step 1, and a slightly older version of Insight from step 2. Both versions of the GDB debugger are called msp430-gdb.exe so one needs to be renamed. Locate the older version msp430-gdb.exe from the files installed during this step and rename it msp430-insight.exe. \\ # Ensure the BIN directory from the files installed during step 1 and the BIN directory from the files installed during step 2 are included in your PATH environment variable. \\ \\ # The MSPGCC download includes a program called msp430-gdbproxy.exe. This intercepts the GDB TCP commands and redirects them to the parallel port. Start msp430-gdbproxy (a shortcut to this will have been placed on the start menu when MSPGCC was installed). By default msp430-gdbproxy uses port 3333 - do not change this. \\ # Program the flash as per the instruction in the section above. The flash can be programmed from within GDB but it is much faster to do it separately and beforehand. \\ # Start the debugger using the command ... msp430-insight a.out... the commands in the gdb.ini file will do the rest. If you prefer to use the command line debugger simply replace msp430-insight with msp430-gdb. \\ # Insight will start at and the program will stop at the breakpoint in main() as shown below. \\ MSP430 Clocking \\ MSP430 Basic Clock Module * Clock Signals: ** *ACLK*: Auxiliary clock. The signal is sourced from LFXT1CLK with a divider of 1, 2, 4, or 8. (The calibration program for the serial link sets the divider to 4, but after the calibration it can be changed to any other values.) ACLK can be used as the clock signal for Timer A and Timer B. ** *MCLK*: Master clock. The signal can be sourced from LFXT1CLK, XT2CLK (if available), or DCOCLK with a divider of 1, 2, 4, or 8. MCLK is used by the CPU and system. ** *SMCLK*: Sub-main clock. The signal is sourced from either XT2CLK (if available), or DCOCLK with a divider of 1, 2, 4, or 8. SMCLK can be used as the clock signal for Timer A and Timer B. * MSP430 Clocking pictorial: *   * \\ !MSP430_clocking2.JPG!                  !MSP430_BCSCTL1.JPG! !MSP430_BCSCTL2.JPG!\\ \\]]> 5374680 11273131 Accessories  \--> Communications  \--> Hyperterm  \--> McStar USBser 115200 ** 115200, 8n1, no flow, COM5 * Step 4 - remove magnet from McSTAR 'white spot' ** If no activity, hit ENTER a couple of times and put magnet on white spot and remove. ** Should see a boot screen, do not hit a key to stop autoboot \\ h4. McSTAR Functional Test    •Step 1 - in Hyperterm, after McSTAR has booted, login with by entering 'root' \-JFFS2 message is harmless, but if login not seen due to JFFS2 message, hit ENTER a couple of times. •Step 2 - cd /media/sda1 (USB harddisk connected to McStar) \-List (ls) should show app dir •Step 3 - 'cd /media/sda1/app/scripts' •Step 4 - type 'date', then type 'date \-s "Tue Mar 09 10:54:30 PST 2010"' •Step 4 - start the McSTAR app './run_mcstar.sh' \-Allow it to run until the first recording message comes out.   Say stuff, whistle, whisper, etc. every 10 seconds or so (data blocks vary from 2 to 20 minutes; typically 5 minutes). \-After the first recording data message, hit Ctrl-c (terminate McSTAR data collection). \-"Writing a new audio file D000000..."  h4. Verification •Step 1 - after terminating run_mcstar.sh   In Hyperterm, change directories to the data directory. \-cd /media/sda1/data \-Cd to the latest directory, then cd to R00000 •Find the file and transfer \-In Hyperterm, Transfer  \--> Receive File, use Zmodem (no crash recovery). Close \-In hyperterm, tell McSTAR to transfer the file you recorded • sz D00000 •On the HP Netbook, start Audacity On Windows •Project  \--> Import Raw Data \-Accept the defaults, and change 44100 to 48000 On a Mac •File  \--> Import  \--> Raw Data... •select file •open file and accept default settings except Sample Rate - change from default value of 44100 Hz to 48000 Hz (sampling rate of McSTAR). \\]]> 11240393 11273132 Accessories  --> Communications  --> Hyperterm  --> McStar USBser 115200 ** 115200, 8n1, no flow, COM5 * Step 4 - remove magnet from McSTAR 'white spot' ** If no activity, hit ENTER a couple of times and put magnet on white spot and remove. ** Should see a boot screen, do not hit a key to stop autoboot \\ h4. McSTAR Functional Test    •Step 1 - in Hyperterm, after McSTAR has booted, login with by entering 'root' \-JFFS2 message is harmless, but if login not seen due to JFFS2 message, hit ENTER a couple of times. •Step 2 - cd /media/sda1 (USB harddisk connected to McStar) \-List (ls) should show app dir •Step 3 - 'cd /media/sda1/app/scripts' •Step 4 - type 'date', then type 'date \-s "Tue Mar 09 10:54:30 PST 2010"' •Step 4 - start the McSTAR app './run_mcstar.sh' \-Allow it to run until the first recording message comes out.   Say stuff, whistle, whisper, etc. every 10 seconds or so (data blocks vary from 2 to 20 minutes; typically 5 minutes). \-After the first recording data message, hit Ctrl-c (terminate McSTAR data collection). \-"Writing a new audio file D000000..."  h4. Verification •Step 1 - after terminating run_mcstar.sh   In Hyperterm, change directories to the data directory. \-cd /media/sda1/data \-Cd to the latest directory, then cd to R00000 •Find the file and transfer \-In Hyperterm, Transfer  \--> Receive File, use Zmodem (no crash recovery). Close \-In hyperterm, tell McSTAR to transfer the file you recorded • sz D00000 •On the HP Netbook, start Audacity On Windows •Project  \--> Import Raw Data \-Accept the defaults, and change 44100 to 48000 On a Mac •File  --> Import  --> Raw Data... •select file •open file and accept default settings except Sample Rate - change from default value of 44100 Hz to 48000 Hz (sampling rate of McSTAR). \\]]> 11240394 11273133 Accessories  \--> Communications  \--> Hyperterm  \--> McStar USBser 115200 ** 115200, 8n1, no flow, COM5 * Step 4 - remove magnet from McSTAR 'white spot' ** If no activity, hit ENTER a couple of times and put magnet on white spot and remove. ** Should see a boot screen, do not hit a key to stop autoboot \\ h4. McSTAR Functional Test    •Step 1 - in Hyperterm, after McSTAR has booted, login with by entering 'root' \-JFFS2 message is harmless, but if login not seen due to JFFS2 message, hit ENTER a couple of times. •Step 2 - cd /media/sda1 (USB harddisk connected to McStar) \-List (ls) should show app dir •Step 3 - 'cd /media/sda1/app/scripts' •Step 4 - type 'date', then type 'date \-s "Tue Mar 09 10:54:30 PST 2010"' •Step 4 - start the McSTAR app './run_mcstar.sh' \-Allow it to run until the first recording message comes out.   Say stuff, whistle, whisper, etc. every 10 seconds or so (data blocks vary from 2 to 20 minutes; typically 5 minutes). \-After the first recording data message, hit Ctrl-c (terminate McSTAR data collection). \-"Writing a new audio file D000000..."  h4. Verification •Step 1 - after terminating run_mcstar.sh   In Hyperterm, change directories to the data directory. \-cd /media/sda1/data \-Cd to the latest directory, then cd to R00000 •Find the file and transfer \-In Hyperterm, Transfer  \--> Receive File, use Zmodem (no crash recovery). Close \-In hyperterm, tell McSTAR to transfer the file you recorded • sz D00000 •On the HP Netbook, start Audacity On Windows •Project  \--> Import Raw Data \-Accept the defaults, and change 44100 to 48000 On a Mac •File  \--> Import  \--> Raw Data... •select file •open file and accept default settings except Sample Rate - change from default value of 44100 Hz to 48000 Hz (sampling rate of McSTAR). \\]]> 11240395 11273134 Accessories  --> Communications  --> Hyperterm  --> McStar USBser 115200 ** 115200, 8n1, no flow, COM5 * Step 4 - remove magnet from McSTAR 'white spot' ** If no activity, hit ENTER a couple of times and put magnet on white spot and remove. ** Should see a boot screen, do not hit a key to stop autoboot \\ h4. McSTAR Functional Test    •Step 1 - in Hyperterm, after McSTAR has booted, login with by entering 'root' \-JFFS2 message is harmless, but if login not seen due to JFFS2 message, hit ENTER a couple of times. •Step 2 - cd /media/sda1 (USB harddisk connected to McStar) \-List (ls) should show app dir •Step 3 - 'cd /media/sda1/app/scripts' •Step 4 - type 'date', then type 'date \-s "Tue Mar 09 10:54:30 PST 2010"' •Step 4 - start the McSTAR app './run_mcstar.sh' \-Allow it to run until the first recording message comes out.   Say stuff, whistle, whisper, etc. every 10 seconds or so (data blocks vary from 2 to 20 minutes; typically 5 minutes). \-After the first recording data message, hit Ctrl-c (terminate McSTAR data collection). \-"Writing a new audio file D000000..."  h4. Verification •Step 1 - after terminating run_mcstar.sh   In Hyperterm, change directories to the data directory. \-cd /media/sda1/data \-Cd to the latest directory, then cd to R00000 •Find the file and transfer \-In Hyperterm, Transfer  \--> Receive File, use Zmodem (no crash recovery). Close \-In hyperterm, tell McSTAR to transfer the file you recorded • sz D00000 •On the HP Netbook, start Audacity On Windows •Project  \--> Import Raw Data \-Accept the defaults, and change 44100 to 48000 On a Mac •File  --> Import  --> Raw Data... •select file •open file and accept default settings except Sample Rate - change from default value of 44100 Hz to 48000 Hz (sampling rate of McSTAR). \\]]> 11240396 5407415 D0 52.08 52.08 \+0 \+0.00 D0->D1 104.17 104.17 \+0 \+0.00 D1->D2 156.25 156.25 \+0 \+0.00 D2->D3 208.33 208.33 \+0 \+0.00 D3->D4 260.42 260.42 \+0 \+0.00 D4->D5 312.50 312.50 \+0 \+0.00 D5->D6 364.58 364.58 \+0 \+0.00 D6->D7 416.67 416.67 \+0 \+0.00 D7->stopbit 468.75 468.75 \+0 \+0.00 end of stopb 520.83 520.83 \+0 \+0.00 \*/ UBR00=0xC0; UBR10=0x00; UMCTL0=0x00; /\* uart0 3686400Hz 19200bps \*/ UBR01=0xC0; UBR11=0x00; UMCTL1=0x00; /\* uart1 3686400Hz 19200bps \*/ h4. The simplest way to use the USART in UART mode is this: interrupt is not enabled, the software checks if it can output the next byte (UTXIFG = 1), and if a new character has been received (URXIFG = 1). \\ h4. Modbus Register Map * REG_INPUT_START         512         // input registers start at 512 * REG_INPUT_NREGS         8           // 8x16 bit registers * REG_SOLENOIDS_A        0            // Holding registers start at 0 (16 coils for each A and B) * REG_SOLENOIDS_B        1   * REG_HOLDING_START    0           // to match WAGO * REG_HOLDING_NREGS   40         // 40 is more than actual (2) * REG_COILS_START         0           // read individual coils (was 1000) * REG_COILS_SIZE           32          // 32 coils * REG_DISC_START          0           // discrete (was 1000) * REG_DISC_SIZE             32          // 32 coils \\ h3. ---- MODBUS * Commands ** Read Input Register (0x04) ** Read Holding Registers (0x03) ** Write Single Register (0x06) ** Write Multiple Registers (0x10) ** Read/Write Multiple Registers (0x17) ** Read Coils (0x01) ** Write Single Coil (0x05) ** Write Multiple Coils (0x0F) ** Read Discrete Inputs (0x02) ** Report Slave ID (0x11)   * Address * Slave ID  * Berlios ModBus Stack ** The modbus stack is config'd in {color:#0000ff}mbconfig.h{color} which is located in vpc\modbus\include \\ \\ ---- h3. Debugging MSP430 h4. Starting gdbproxy The next step is starting gdbproxy, which is responsible for the communication between GDB and the FET: msp430-gdbproxy \--port=2000 msp430 If your FET is properly connected to the parallel port, you should see a message like the following: info: msp430: Target device is a 'MSP430F12x' (type 11) notice: msp430-gdbproxy: waiting on TCP port 2000 h4. Using Insight (Windows) After you have started Insight (c:\msp430\bin\msp430-gdb.exe), click on "File->Open" and select the elf-file (e.g. "test.elf") you want to debug. Now click on "Run->Connect to target" and enter the following settings: Target: "Remote/TCP" Hostname: "localhost" Port: "2000" Set breakpoint at 'main': yes Set breakpoint at 'exit': yes Attach to target: yes Download Program: yes Command after attaching: "monitor erase all" Run Method: Continue from last Stop When you click on "Ok" Insight should tell you that the connection was successful, and gdbproxy should say "notice: msp430-gdbproxy: connected". To start the debugging click on "Run" or simply press "r". If everything worked correctly you should now see the sourcecode of your program with the first line of main() marked green. The red point is the breakpoint that has been set by Insight automatically. You can set or remove breakpoints by clicking on the '-' in front of the line. Now you can 'c'ontinue the execution to the next breakpoint, 's'tep through the code, or step a single assembler instruction... but be careful with "finish": Insight sometimes seems to lock up with this command. So if you want to finish a function, I recommend setting a breakpoint to the end of the function and using "continue". \\ h2. Installing the Compiler Tool Chain To obtain and install the compiler: # Go to the MSPGCC download page and obtain the latest MSPGCC installation. I used the 'mspgcc-20040723.exe' download which installed everything I needed for a Win32 setup. \\ # This step need only be performed if you wish to use the graphical version of GDB. The latest MSPGCC download only includes the command line GDB debugger. I prefer to use the graphical version called Insight. A slightly older prebuilt version of Insight can be used. Install this older version of insight into a different directory to that chosen for the latest MSPGCC installation as you don't want to overwrite the files obtained in step 1. \\ You should now have two installations. The latest version of MSPGCC installed during step 1, and a slightly older version of Insight from step 2. Both versions of the GDB debugger are called msp430-gdb.exe so one needs to be renamed. Locate the older version msp430-gdb.exe from the files installed during this step and rename it msp430-insight.exe. \\ # Ensure the BIN directory from the files installed during step 1 and the BIN directory from the files installed during step 2 are included in your PATH environment variable. \\ \\ # The MSPGCC download includes a program called msp430-gdbproxy.exe. This intercepts the GDB TCP commands and redirects them to the parallel port. Start msp430-gdbproxy (a shortcut to this will have been placed on the start menu when MSPGCC was installed). By default msp430-gdbproxy uses port 3333 - do not change this. \\ # Program the flash as per the instruction in the section above. The flash can be programmed from within GDB but it is much faster to do it separately and beforehand. \\ # Start the debugger using the command ... msp430-insight a.out... the commands in the gdb.ini file will do the rest. If you prefer to use the command line debugger simply replace msp430-insight with msp430-gdb. \\ # Insight will start at and the program will stop at the breakpoint in main() as shown below. \\ MSP430 Clocking \\ MSP430 Basic Clock Module * Clock Signals: ** *ACLK*: Auxiliary clock. The signal is sourced from LFXT1CLK with a divider of 1, 2, 4, or 8. (The calibration program for the serial link sets the divider to 4, but after the calibration it can be changed to any other values.) ACLK can be used as the clock signal for Timer A and Timer B. ** *MCLK*: Master clock. The signal can be sourced from LFXT1CLK, XT2CLK (if available), or DCOCLK with a divider of 1, 2, 4, or 8. MCLK is used by the CPU and system. ** *SMCLK*: Sub-main clock. The signal is sourced from either XT2CLK (if available), or DCOCLK with a divider of 1, 2, 4, or 8. SMCLK can be used as the clock signal for Timer A and Timer B. * MSP430 Clocking pictorial: *   * \\ !MSP430_clocking2.JPG!                  !MSP430_BCSCTL1.JPG! !MSP430_BCSCTL2.JPG!\\ \\]]> 5374684 11273127 Accessories  \--> Communications  \--> Hyperterm  \--> McStar USBser 115200 \-115200, 8n1, no flow, COM5 •Step 4 - remove magnet from McSTAR 'white spot' \-If no activity, hit ENTER a couple of times and put magnet on white spot and remove. \-Should see a boot screen, do not hit a key to stop autoboot \\ h4. McSTAR Functional Test    •Step 1 - in Hyperterm, after McSTAR has booted, login with by entering 'root' \-JFFS2 message is harmless, but if login not seen due to JFFS2 message, hit ENTER a couple of times. •Step 2 - cd /media/sda1 (USB harddisk connected to McStar) \-List (ls) should show app dir •Step 3 - 'cd /media/sda1/app/scripts' •Step 4 - type 'date', then type 'date \-s "Tue Mar 09 10:54:30 PST 2010"' •Step 4 - start the McSTAR app './run_mcstar.sh' \-Allow it to run until the first recording message comes out.   Say stuff, whistle, whisper, etc. every 10 seconds or so (data blocks vary from 2 to 20 minutes; typically 5 minutes). \-After the first recording data message, hit Ctrl-c (terminate McSTAR data collection). \-"Writing a new audio file D000000..."  h4. Verification •Step 1 - after terminating run_mcstar.sh   In Hyperterm, change directories to the data directory. \-cd /media/sda1/data \-Cd to the latest directory, then cd to R00000 •Find the file and transfer \-In Hyperterm, Transfer  \--> Receive File, use Zmodem (no crash recovery). Close \-In hyperterm, tell McSTAR to transfer the file you recorded • sz D00000 •On the HP Netbook, start Audacity On Windows •Project  \--> Import Raw Data \-Accept the defaults, and change 44100 to 48000 On a Mac •File  \--> Import  \--> Raw Data... •select file •open file and accept default settings except Sample Rate - change from default value of 44100 Hz to 48000 Hz (sampling rate of McSTAR). \\]]> 11240389 11273128 Accessories  --> Communications  --> Hyperterm  --> McStar USBser 115200 ** 115200, 8n1, no flow, COM5 * Step 4 - remove magnet from McSTAR 'white spot' ** If no activity, hit ENTER a couple of times and put magnet on white spot and remove. ** Should see a boot screen, do not hit a key to stop autoboot \\ h4. McSTAR Functional Test    •Step 1 - in Hyperterm, after McSTAR has booted, login with by entering 'root' \-JFFS2 message is harmless, but if login not seen due to JFFS2 message, hit ENTER a couple of times. •Step 2 - cd /media/sda1 (USB harddisk connected to McStar) \-List (ls) should show app dir •Step 3 - 'cd /media/sda1/app/scripts' •Step 4 - type 'date', then type 'date \-s "Tue Mar 09 10:54:30 PST 2010"' •Step 4 - start the McSTAR app './run_mcstar.sh' \-Allow it to run until the first recording message comes out.   Say stuff, whistle, whisper, etc. every 10 seconds or so (data blocks vary from 2 to 20 minutes; typically 5 minutes). \-After the first recording data message, hit Ctrl-c (terminate McSTAR data collection). \-"Writing a new audio file D000000..."  h4. Verification •Step 1 - after terminating run_mcstar.sh   In Hyperterm, change directories to the data directory. \-cd /media/sda1/data \-Cd to the latest directory, then cd to R00000 •Find the file and transfer \-In Hyperterm, Transfer  \--> Receive File, use Zmodem (no crash recovery). Close \-In hyperterm, tell McSTAR to transfer the file you recorded • sz D00000 •On the HP Netbook, start Audacity On Windows •Project  \--> Import Raw Data \-Accept the defaults, and change 44100 to 48000 On a Mac •File  --> Import  --> Raw Data... •select file •open file and accept default settings except Sample Rate - change from default value of 44100 Hz to 48000 Hz (sampling rate of McSTAR). \\]]> 11240390 11273129 Accessories  \--> Communications  \--> Hyperterm  \--> McStar USBser 115200 ** 115200, 8n1, no flow, COM5 * Step 4 - remove magnet from McSTAR 'white spot' ** If no activity, hit ENTER a couple of times and put magnet on white spot and remove. ** Should see a boot screen, do not hit a key to stop autoboot \\ h4. McSTAR Functional Test    •Step 1 - in Hyperterm, after McSTAR has booted, login with by entering 'root' \-JFFS2 message is harmless, but if login not seen due to JFFS2 message, hit ENTER a couple of times. •Step 2 - cd /media/sda1 (USB harddisk connected to McStar) \-List (ls) should show app dir •Step 3 - 'cd /media/sda1/app/scripts' •Step 4 - type 'date', then type 'date \-s "Tue Mar 09 10:54:30 PST 2010"' •Step 4 - start the McSTAR app './run_mcstar.sh' \-Allow it to run until the first recording message comes out.   Say stuff, whistle, whisper, etc. every 10 seconds or so (data blocks vary from 2 to 20 minutes; typically 5 minutes). \-After the first recording data message, hit Ctrl-c (terminate McSTAR data collection). \-"Writing a new audio file D000000..."  h4. Verification •Step 1 - after terminating run_mcstar.sh   In Hyperterm, change directories to the data directory. \-cd /media/sda1/data \-Cd to the latest directory, then cd to R00000 •Find the file and transfer \-In Hyperterm, Transfer  \--> Receive File, use Zmodem (no crash recovery). Close \-In hyperterm, tell McSTAR to transfer the file you recorded • sz D00000 •On the HP Netbook, start Audacity On Windows •Project  \--> Import Raw Data \-Accept the defaults, and change 44100 to 48000 On a Mac •File  \--> Import  \--> Raw Data... •select file •open file and accept default settings except Sample Rate - change from default value of 44100 Hz to 48000 Hz (sampling rate of McSTAR). \\]]> 11240391 11273130 Accessories  --> Communications  --> Hyperterm  --> McStar USBser 115200 ** 115200, 8n1, no flow, COM5 * Step 4 - remove magnet from McSTAR 'white spot' ** If no activity, hit ENTER a couple of times and put magnet on white spot and remove. ** Should see a boot screen, do not hit a key to stop autoboot \\ h4. McSTAR Functional Test    •Step 1 - in Hyperterm, after McSTAR has booted, login with by entering 'root' \-JFFS2 message is harmless, but if login not seen due to JFFS2 message, hit ENTER a couple of times. •Step 2 - cd /media/sda1 (USB harddisk connected to McStar) \-List (ls) should show app dir •Step 3 - 'cd /media/sda1/app/scripts' •Step 4 - type 'date', then type 'date \-s "Tue Mar 09 10:54:30 PST 2010"' •Step 4 - start the McSTAR app './run_mcstar.sh' \-Allow it to run until the first recording message comes out.   Say stuff, whistle, whisper, etc. every 10 seconds or so (data blocks vary from 2 to 20 minutes; typically 5 minutes). \-After the first recording data message, hit Ctrl-c (terminate McSTAR data collection). \-"Writing a new audio file D000000..."  h4. Verification •Step 1 - after terminating run_mcstar.sh   In Hyperterm, change directories to the data directory. \-cd /media/sda1/data \-Cd to the latest directory, then cd to R00000 •Find the file and transfer \-In Hyperterm, Transfer  \--> Receive File, use Zmodem (no crash recovery). Close \-In hyperterm, tell McSTAR to transfer the file you recorded • sz D00000 •On the HP Netbook, start Audacity On Windows •Project  \--> Import Raw Data \-Accept the defaults, and change 44100 to 48000 On a Mac •File  --> Import  --> Raw Data... •select file •open file and accept default settings except Sample Rate - change from default value of 44100 Hz to 48000 Hz (sampling rate of McSTAR). \\]]> 11240392 5407419 D0 52.08 52.08 \+0 \+0.00 D0->D1 104.17 104.17 \+0 \+0.00 D1->D2 156.25 156.25 \+0 \+0.00 D2->D3 208.33 208.33 \+0 \+0.00 D3->D4 260.42 260.42 \+0 \+0.00 D4->D5 312.50 312.50 \+0 \+0.00 D5->D6 364.58 364.58 \+0 \+0.00 D6->D7 416.67 416.67 \+0 \+0.00 D7->stopbit 468.75 468.75 \+0 \+0.00 end of stopb 520.83 520.83 \+0 \+0.00 \*/ UBR00=0xC0; UBR10=0x00; UMCTL0=0x00; /\* uart0 3686400Hz 19200bps \*/ UBR01=0xC0; UBR11=0x00; UMCTL1=0x00; /\* uart1 3686400Hz 19200bps \*/ h4. The simplest way to use the USART in UART mode is this: interrupt is not enabled, the software checks if it can output the next byte (UTXIFG = 1), and if a new character has been received (URXIFG = 1). \\ h4. Modbus Register Map * REG_INPUT_START         512         // input registers start at 512 * REG_INPUT_NREGS         8           // 8x16 bit registers * REG_SOLENOIDS_A        0            // Holding registers start at 0 (16 coils for each A and B) * REG_SOLENOIDS_B        1   * REG_HOLDING_START    0           // to match WAGO * REG_HOLDING_NREGS   40         // 40 is more than actual (2) * REG_COILS_START         0           // read individual coils (was 1000) * REG_COILS_SIZE           32          // 32 coils * REG_DISC_START          0           // discrete (was 1000) * REG_DISC_SIZE             32          // 32 coils \\ h3. ---- MODBUS * Commands ** Read Input Register (0x04) ** Read Holding Registers (0x03) ** Write Single Register (0x06) ** Write Multiple Registers (0x10) ** Read/Write Multiple Registers (0x17) ** Read Coils (0x01) ** Write Single Coil (0x05) ** Write Multiple Coils (0x0F) ** Read Discrete Inputs (0x02) ** Report Slave ID (0x11)   * Address * Slave ID  * Berlios ModBus Stack ** The modbus stack is config'd in {color:#0000ff}mbconfig.h{color} which is located in vpc\modbus\include \\ \\ ---- h3. Debugging MSP430 h4. Starting gdbproxy The next step is starting gdbproxy, which is responsible for the communication between GDB and the FET: msp430-gdbproxy \--port=2000 msp430 If your FET is properly connected to the parallel port, you should see a message like the following: info: msp430: Target device is a 'MSP430F12x' (type 11) notice: msp430-gdbproxy: waiting on TCP port 2000 h4. Using Insight (Windows) After you have started Insight (c:\msp430\bin\msp430-gdb.exe), click on "File->Open" and select the elf-file (e.g. "test.elf") you want to debug. Now click on "Run->Connect to target" and enter the following settings: Target: "Remote/TCP" Hostname: "localhost" Port: "2000" Set breakpoint at 'main': yes Set breakpoint at 'exit': yes Attach to target: yes Download Program: yes Command after attaching: "monitor erase all" Run Method: Continue from last Stop When you click on "Ok" Insight should tell you that the connection was successful, and gdbproxy should say "notice: msp430-gdbproxy: connected". To start the debugging click on "Run" or simply press "r". If everything worked correctly you should now see the sourcecode of your program with the first line of main() marked green. The red point is the breakpoint that has been set by Insight automatically. You can set or remove breakpoints by clicking on the '-' in front of the line. Now you can 'c'ontinue the execution to the next breakpoint, 's'tep through the code, or step a single assembler instruction... but be careful with "finish": Insight sometimes seems to lock up with this command. So if you want to finish a function, I recommend setting a breakpoint to the end of the function and using "continue". \\ h2. Installing the Compiler Tool Chain To obtain and install the compiler: # Go to the MSPGCC download page and obtain the latest MSPGCC installation. I used the 'mspgcc-20040723.exe' download which installed everything I needed for a Win32 setup. \\ # This step need only be performed if you wish to use the graphical version of GDB. The latest MSPGCC download only includes the command line GDB debugger. I prefer to use the graphical version called Insight. A slightly older prebuilt version of Insight can be used. Install this older version of insight into a different directory to that chosen for the latest MSPGCC installation as you don't want to overwrite the files obtained in step 1. \\ You should now have two installations. The latest version of MSPGCC installed during step 1, and a slightly older version of Insight from step 2. Both versions of the GDB debugger are called msp430-gdb.exe so one needs to be renamed. Locate the older version msp430-gdb.exe from the files installed during this step and rename it msp430-insight.exe. \\ # Ensure the BIN directory from the files installed during step 1 and the BIN directory from the files installed during step 2 are included in your PATH environment variable. \\ \\ # The MSPGCC download includes a program called msp430-gdbproxy.exe. This intercepts the GDB TCP commands and redirects them to the parallel port. Start msp430-gdbproxy (a shortcut to this will have been placed on the start menu when MSPGCC was installed). By default msp430-gdbproxy uses port 3333 - do not change this. \\ # Program the flash as per the instruction in the section above. The flash can be programmed from within GDB but it is much faster to do it separately and beforehand. \\ # Start the debugger using the command ... msp430-insight a.out... the commands in the gdb.ini file will do the rest. If you prefer to use the command line debugger simply replace msp430-insight with msp430-gdb. \\ # Insight will start at and the program will stop at the breakpoint in main() as shown below. \\ MSP430 Clocking \\ MSP430 Basic Clock Module * Clock Signals: ** *ACLK*: Auxiliary clock. The signal is sourced from LFXT1CLK with a divider of 1, 2, 4, or 8. (The calibration program for the serial link sets the divider to 4, but after the calibration it can be changed to any other values.) ACLK can be used as the clock signal for Timer A and Timer B. ** *MCLK*: Master clock. The signal can be sourced from LFXT1CLK, XT2CLK (if available), or DCOCLK with a divider of 1, 2, 4, or 8. MCLK is used by the CPU and system. ** *SMCLK*: Sub-main clock. The signal is sourced from either XT2CLK (if available), or DCOCLK with a divider of 1, 2, 4, or 8. SMCLK can be used as the clock signal for Timer A and Timer B. * MSP430 Clocking pictorial: *   * \\ !MSP430_clocking2.JPG!                  !MSP430_BCSCTL1.JPG! !MSP430_BCSCTL2.JPG!\\ \\]]> 5374688 19074097 19041411 11273124 Accessories  \--> Communications  \--> Hyperterm  \--> McStar USBser 115200 \-115200, 8n1, no flow, COM5 •Step 4 - remove magnet from McStar 'white spot' \-If no activity, hit ENTER a couple of times and put magnet on white spot and remove. \-Should see a boot screen, do not hit a key to stop autoboot \\ h4. McStar Functional Test    •Step 1 - in Hyperterm, after Mcstar has booted, login with by entering 'root' \-JFFS2 message is harmless, but if login not seen due to JFFS2 message, hit ENTER a couple of times. •Step 2 - cd /media/sda1 (USB harddisk connected to McStar) \-List (ls) should show app dir •Step 3 - 'cd /media/sda1/app/scripts' •Step 4 - type 'date', then type 'date \-s "Tue Mar 09 10:54:30 PST 2010"' •Step 4 - start the McStar app './run_mcstar.sh' \-Allow it to run until the first recording message comes out.   Say stuff, whistle, whisper, etc. every 10 seconds or so (data blocks vary from 2 to 20 minutes; typically 5 minutes). \-After the first recording data message, hit Ctrl-c (terminate McSTAR data collection). \-"Writing a new audio file D000000..."  h4. Verification •Step 1 - after terminating run_mcstar.sh   In Hyperterm, change directories to the data directory. \-cd /media/sda1/data \-Cd to the latest directory, then cd to R00000 •Find the file and transfer \-In Hyperterm, Transfer  \--> Receive File, use Zmodem (no crash recovery). Close \-In hyperterm, tell Mcstar to transfer the file you recorded • sz D00000 •On the HP Netbook, start Audacity On Windows •Project --> Import Raw Data \-Accept the defaults, and change 44100 to 48000 On a Mac •File  \--> Import  \--> Raw Data... •select file •open file and accept default settings except Sample Rate - change from default value of 44100 Hz to 48000 Hz (sampling rate of McSTAR). \\]]> 11240386 5407425 ... mbari MBARI Repository http://oceana.shore.mbari.org/maven2 ... ... {code} h3. Including a Dependency from the Repository Once the MBARI repository is included in you build, you can browse the repository to see what projects are available (just go to [http://oceana.shore.mbari.org/maven2]). If you find a dependency you need you can reference it in your _pom.xml_. Here's an example... {code:xml} ... ... qt4j qt4j 0.5 ... ... {code} h3. Putting a Dependency into the Repository The easiest way to put a dependency into the repository is to setup a Maven build file (i.e. _pom.xml_). In _pom.xml_ add the following _distributionManagement_ information: {code:xml} 4.0.0 qt4j qt4j jar 1.0-SNAPSHOT QT4J ... mbari-repository MBARI Repository scp://oceana.shore.mbari.org/var/www/html/maven2 {code} Executing _mvn deploy_ will put your build jar at http://oceana.shore.mbari.org/maven2////-.jar. In the example here it would put it into [http://oceana.shore.mbari.org/maven2/qt4j/qt4j/1.0-SNAPSHOT/] h3. Publishing Maven generated web sites Maven can generate a web site for a default web site for you. You can view samples of the currently published projects at [http://oceana.shore.mbari.org/projects]. It's not very interesting, however, it is a very simple way to publish the javadoc, sources and auto-generated reports. To do so modify your _pom.xml_: {code:xml} ... org.apache.maven.plugins maven-jxr-plugin org.apache.maven.plugins maven-pmd-plugin 1.5 org.apache.maven.plugins maven-checkstyle-plugin ... oceana.shore.mbari.org scp://oceana.shore.mbari.org/var/www/html/projects/${project.name} {code} Then run _mvn javadoc:javadoc site:site site:deploy_. This will build the javadocs, create a site with some useful reports, then publish the site (using scp) to oceana in the correct location. h3. Project Specific Maven Repositories Some projects may need to be configured differently for different deployment locations. For example, [VARS|VARS:Home] is configured differently for each ship and shore. These specific configurations are stored in Maven repositories in [http://oceana.shore.mbari.org/maven2-prj]. Each directory listed there is a different repository. Here's an example of how to include the projects configured for [Eye-in-the-sea|EITS:Home]. {code:xml} mbari-eits MBARI-EITS Repository http://oceana.shore.mbari.org/maven2-prj/eits {code} h2. {anchor:M3} +Using the MBARI repository from an [Ant|http://ant.apache.org] project using Maven+ Maven repositories can be used from Ant build scripts using [Maven's antlib|http://maven.apache.org/ant-tasks.html]. To do this you must have both Maven and Ant installed. h3. Bootstrapping antlib To bootstrap antlib into your projects (so users can build without having to install antlib) modify your _build.xml_ file like so: {code:xml} ... Finding dependencies of ${pom.artifactId}-${version} ... {code} h2. {anchor:M4} +Using the MBARI repository from an [Ant|http://ant.apache.org] project using Ivy+ Maven repositories can be used from Ant build scripts using [Ivy|http://incubator.apache.org/ivy/]. h3. Referencing the repository In the directory containing the ant build file, _build.xml_, create a file called _ivyconf.xml_. _ivyconf.xml_ tells Ivy where to look for dependencies. The contents of the file will look something like: {code:xml} {code} h3. Including a Dependency from the Repository In the directory containing _build.xml_, create a file called _ivy.xml_. _ivy.xml_ tells Ivy what dependencies to include in your build. Here's an example of it's contents: {code:xml} {code} h3. Using Ivy from Ant The code below will fetch Ivy for you. SO you do not need install any additional software in order to get you build to work. In your ant build file include the following: {code:xml} ... {code} Calling _ant ivy.install_ will fetch all the dependencies from the web and put them into the _lib_ directory of your project. ]]> 5374694 11273125 Accessories  --> Communications  --> Hyperterm  --> McStar USBser 115200 \-115200, 8n1, no flow, COM5 •Step 4 - remove magnet from McSTAR 'white spot' \-If no activity, hit ENTER a couple of times and put magnet on white spot and remove. \-Should see a boot screen, do not hit a key to stop autoboot \\ h4. McSTAR Functional Test    •Step 1 - in Hyperterm, after McSTAR has booted, login with by entering 'root' \-JFFS2 message is harmless, but if login not seen due to JFFS2 message, hit ENTER a couple of times. •Step 2 - cd /media/sda1 (USB harddisk connected to McStar) \-List (ls) should show app dir •Step 3 - 'cd /media/sda1/app/scripts' •Step 4 - type 'date', then type 'date \-s "Tue Mar 09 10:54:30 PST 2010"' •Step 4 - start the McSTAR app './run_mcstar.sh' \-Allow it to run until the first recording message comes out.   Say stuff, whistle, whisper, etc. every 10 seconds or so (data blocks vary from 2 to 20 minutes; typically 5 minutes). \-After the first recording data message, hit Ctrl-c (terminate McSTAR data collection). \-"Writing a new audio file D000000..."  h4. Verification •Step 1 - after terminating run_mcstar.sh   In Hyperterm, change directories to the data directory. \-cd /media/sda1/data \-Cd to the latest directory, then cd to R00000 •Find the file and transfer \-In Hyperterm, Transfer  --> Receive File, use Zmodem (no crash recovery). Close \-In hyperterm, tell McSTAR to transfer the file you recorded • sz D00000 •On the HP Netbook, start Audacity On Windows •Project  --> Import Raw Data \-Accept the defaults, and change 44100 to 48000 On a Mac •File  --> Import  --> Raw Data... •select file •open file and accept default settings except Sample Rate - change from default value of 44100 Hz to 48000 Hz (sampling rate of McSTAR). \\]]> 11240387 17268963 17236200 17268964 17236201 19074101 19041415 17268966 17236203 19074099 19041413 19074106 19041420 17268968 17236205 3965004 'Downloads'>'2.1 Releases'>'2.1.1' # I changed to the 'Details View', made 40 items visible, and then downloaded 'alfresco-enterprise-tomcat-2.1.1.zip' file. # I then unzipped the downloaded file to c:\bin which created an alfresco-enterprise-tomcat-2.1.1 folder in c:\bin. # I renamed the alfresco-enterprise-tomcat-2.1.1 folder to simply alfresco. # I then went back to the web browser and went to 'Company Home'>'Downloads'>'2.1 Releases'>'2.1.1'>'License Files' # I am not sure if I can do this with our agreement, but I downloaded the 'enterprise-network-customer-unlimited.lic' file. {note} I did get approval from Joe Van De Graaff at Alfresco to use the license for a test installation to get us through this issue. {note} # I logged out of the Alfresco customer web site. # I Googled on jTDS to find the jTDS JDBC driver and downloaded the jtds-1.2.2-dist.zip file from the website. # Using Windows Explorer, I could just open the jTDS zip file and copy the jtds-1.2.2.jar file. # I then pasted it in the directory c:\bin\alfresco\tomcat\common\lib directory. # I created a c:\data\alf_data directory where the alfresco data will be stored. This is different from the production installation in that the content is stored on a network appliance (\\tornado.shore.mbari.org\alfresco). # I installed a copy of SQL Server 2005 locally to use for the database to back the Alfresco test install. {note} In order to do this without warnings, I had to go back and install IIS through the Add/Remove Programs Control Panel. {note} ## I used the Local System account to run services and only used Windows Authentication logins ## I installed all the service packs and the SQL Server Management Studio product to admin DBs. # In SQL Server, I added the SHORE\DB_Collaboration accounts to the logins. # I created a new database named alfresco-test and made SHORE\DB_Collaboration the owner. # I then went to the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions directory for the customization of the server. ## I edited the custom-repository.properties file ### Changed the dir.root and dir.indexes to look like: {noformat} dir.root=c:/data/alf_data dir.indexes=c:/data/alf_data/lucene-indexes {noformat} ### Commented out the db.* lines for the HSQL Connection (db.driver and db.url) ### Uncommented the db.* lines for MSSQL and changed to use the jTDS driver. They should look like (except the password should be the right one): {noformat} db.driver=net.sourceforge.jtds.jdbc.Driver db.url=jdbc:jtds:sqlserver://localhost/alfresco-test;domain=SHORE;user=DB_Collaboration;password=XXXXXXXXX {noformat} ### I also added the following section to override the mail server settings {noformat} # Mail server configuration mail.host=mail.mbari.org mail.port=25 mail.username= mail.password= {noformat} ## Edited the custom-hibernate-dialect.properties file ### Commented out the HSQL Dialect ### Uncommented the MSSQL Dialect # Now this is not necessarily fun, but in order to really get it configured the way we want it, you need to pull the original .war file out, edit some stuff inside and re-create the .war. {note} This should all be done before starting Alfresco for the first time. {note} # Copy the c:\bin\alfresco\tomcat\webapps\alfresco.war file to your home directory. # Make a second copy so that you will always the original (I copied to alfresco.war.orig and moved it somewhere else. It is important to move it and have only the alfresco.war file in the directory because when you un-jar it, all the files go right where alfresco.war is.) # From a command line, un-jar the war file using: {noformat} jar -xvf alfresco.war {noformat} # This unpacks a lot of files and after it completes, move (or delete) the alfresco.war file from the directory. This needs to be done so it does not end up in the new .war file. # I wanted to change the "Company Home" that seems to be everywhere to something that says MBARI. ## Edited ./WEB-INF/classes/alfresco/messages/webclient.properties and changed company_home from 'Company Home' to 'MBARI Test' ## Edited ./WEB-INF/classes/alfresco/messages/webclient_en_US.properties and changed company_home from 'Company Home' to 'MBARI Test' ## I edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces.properties and changed the first two lines to read {noformat} spaces.company_home.name=MBARI Test spaces.company_home.description=The root of MBARIs Test Alfresco Server {noformat} ## Edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces_en_US.properties and made the same changes as the previous step {tip} This took a bit to find all these, and to be honest, I am not sure which one actually made the change on the GUI, but I suspect it was the _en_US ones. {tip} # When users are imported via LDAP, user spaces get created automatically. In order to put them where I wanted them to go (instead of right in the Company Home), I edited the ./WEB-INF/classes/alfresco/authentication-services-context.xml file. In the file there is a bean with an name of personalHomeFolderProvider. There is a property name 'path' and I added {noformat} /${spaces.user_homes.childname} {noformat} to the end to try to get them to create the user spaces there instead of in the Company Home. The final bean XML looks like: {noformat} /${spaces.company_home.childname}/${spaces.user_homes.childname} ${spaces.store} false All All {noformat} # I wanted to change the logo that is used. I attached the replacement [Alfresco Logo|CLT:Installation Notes^AlfrescoLogo32.png]. Copy this to ./images/logo and overwrite the one that is there. {warning} Note that I did NOT setup SSL for this installation so if I will need to come back and do that if I want truly parallel systems {warning} # Now in order to change the default behavior so that all content is versioned from the start, I edited the .\WEB-INF\classes\alfresco\model\contentModel.xml and searched for the content type definition block. {noformat} Content cm:cmobject true d:content false true false true {noformat} and added the following block right before the ending tag: {noformat} cm:versionable {noformat} so the final block looks like: {noformat} Content cm:cmobject true d:content false true false true cm:versionable {noformat} # That takes care of all the changes to the WAR file. We can now put it back into .war form. # While you are in the directory you expanded the war file in, run ## jar cvfm alfresco.war META-INF\MANIFEST.MF . # You should now have an alfresco.war file in the directory. Move that back to the alfresco install and overwrite the existing one. # Most users like the details view, so I set the default to that by editing c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions\web-client-config-custom.xml and added: {noformat} details 20
20
20 {noformat} right before the closing tag. # Now in order to use MBARI accounts, NTLM authentication was turned on and then chained with the native Alfresco accounts so that we could have non-MBARI accounts on the Alfresco server. ## For simplicity sake, I have attached the files and you can simply download and install them in the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions directory. {note} Before doing these next steps, rename the file-servers-custom.xml file to file-servers-custom.xml.orig so you will have a backup of the original {note} ### First install the [NTLM Configuration XML File|^ntlm-authentication-context.xml] ### Next install the [Authentication Chaining Configuration File|^chaining-authentication-context.xml] ### Next install the [CIFS configuration|^file-servers-custom.xml] file and over-write the existing one. ### Now in order to setup a job that imports users and groups once a day, download and install the [LDAP configuration|^ldap-synchronisation-context.xml] file. ### The ldap sych XML file simply contains all the configuration information with properties to hold the actual values for your installation. To define these properties, I installed the following [properties file|^ldap-synchronisation.properties]. If you are setting up your own installation, you will change these properties for your install. {warning} In the CIFS configuration file, make sure you change the tag to reflect a unique name on the network. {warning} ### Next install the [customized authority configuration|^custom-authority-services-context.xml] file (this gives administrative privs to certain accounts). {warning} Note that I did NOT change the server to take over port 80 traffic as the SQL Server install seemed to want IIS which is currently using port 80 {warning} # Now in order for the alfresco web application to be the default, I edit the c:\bin\alfresco\tomcat\conf\server.xml file and added: {noformat} {noformat} as the last line of the tag section (right before the closing tag). {note} You will also notice the Valve tag that I had to add to turn off proxy cache disabling so that IE clients would work correctly over SSL. Gotta love M$. {note} # Just to keep things clean, I edited the c:\bin\alfresco\alfresco.bat file and put 'rem' in front of the second JAVA_OPTS set as I am using Java 6. # You are now actually ready to start alfresco for the first time! Open a command window and cd over the to c:\bin\alfresco directory and then type: {noformat} alf_start.bat {noformat} # After a long time (took several minutes on a regular PC), look at the alfresco.log file in the c:\bin\alfresco directory and see if it looks like everything started OK, you can also check the database to see if the tables have been created in the alfresco-test database. You should also be able to go to http://alfresco-test.shore.mbari.org:8080 and see the alfresco web application. # Now from the command window where you ran alf_start.bat, run alf_stop.bat to shut the server down. Check the alfresco.log file to see if anything weird happened. If not, try restarting it with alf_start.bat again and look at the alfresco.log file. Sometimes, you can't restart it because you get: {noformat} java.sql.SQLException: Column names in each table must be unique. Column name 'ID_' in table 'JBPM_ACTION' is specified more than once. {noformat} Sigh, so in order to keep Alfresco from hurting itself, you might have to turn off the schema updates. This is done by editing the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions\custom-repository.properties and adding the following: {noformat} db.schema.update=false {noformat} and then restarting alfresco. # To install Alfresco as a Windows Service use a command prompt and enter the following: {noformat} cd c:\bin\alfresco\tomcat\bin service.bat install alfresco tomcat5.exe //US//alfresco --DisplayName "Alfresco Server" tomcat5.exe //US//alfresco --JvmMs=512 --JvmMx=1024 --JvmSs=64 tomcat5.exe //US//alfresco --JavaHome=c:/bin/Java/jrockit-R27.4.0-jdk1.6.0_02 tomcat5.exe //US//alfresco --Environment ALF_HOME=c:/bin/alfresco/ tomcat5.exe //US//alfresco --Environment PATH=c:/bin/alfresco/bin;%PATH% tomcat5.exe //US//alfresco --StartPath c:/bin/alfresco --Startup auto {noformat} # To uninstall the service, at a later time, do the following: {noformat} cd c:\bin\alfresco\tomcat\bin service.bat uninstall alfresco {noformat} # To edit your service settings at any time: {noformat} cd c:\alfresco\tomcat\bin tomcat5w.exe //ES//alfresco {noformat} {warning} These next couple of steps had to be taken to install a patch from Alfresco for an issue with bulk uploads I was having. Essentially when file and path structures get really long and nasty, Alfresco was throwing an error and bailing out. This patch (two Java classes) fixed that issue. {warning} # Next, I downloaded the attached [JAR|^act2139.jar] file and copied it to the c:\bin\alfresco\tomcat\webapps\alfresco\WEB-INF\classes directory. # I shutdown Alfresco and then unjarred the file to install the new classes. They are: ## org/alfresco/filesys/smb/server/SMBSrvPacket.class ## org/alfresco/filesys/util/DataBuffer.class # I would assume since they do not overwrite anything, that this location is further up in the class loader and so it will load these new classes first. # I deleted the act2139.jar file and the META-INF directory that the unjarring process created. # To verify this took, I ran alfresco with the {noformat} CATALINA_OPTS="-verbose:class" {noformat} and verifyied that I saw: {noformat} [Loaded org.alfresco.filesys.smb.server.SMBSrvPacket from file:/opt/alfresco211/tomcat/webapps/alfresco/WEB-INF/classes/org/alfresco/filesys/smb/server/SMBSrvPacket.class] {noformat} and NOT: {noformat} Loaded org.alfresco.filesys.smb.server.SMBSrvPacket from file:/opt/alfresco211/tomcat/webapps/alfresco/WEB-INF/lib/alfresco-repository.jar] {noformat} ]]> 3932237 19074104 19041418 19074103 19041417 19074110 Backup ...' {panel} {column} {section}]]> 19041424 3964999 'Downloads'>'2.1 Releases'>'2.1.1' # I changed to the 'Details View', made 40 items visible, and then downloaded 'alfresco-enterprise-tomcat-2.1.1.zip' file. # I then unzipped the downloaded file to c:\bin which created an alfresco-enterprise-tomcat-2.1.1 folder in c:\bin. # I renamed the alfresco-enterprise-tomcat-2.1.1 folder to simply alfresco. # I then went back to the web browser and went to 'Company Home'>'Downloads'>'2.1 Releases'>'2.1.1'>'License Files' # I am not sure if I can do this with our agreement, but I downloaded the 'enterprise-network-customer-unlimited.lic' file. {note} I did get approval from Joe Van De Graaff at Alfresco to use the license for a test installation to get us through this issue. {note} # I logged out of the Alfresco customer web site. # I Googled on jTDS to find the jTDS JDBC driver and downloaded the jtds-1.2.2-dist.zip file from the website. # Using Windows Explorer, I could just open the jTDS zip file and copy the jtds-1.2.2.jar file. # I then pasted it in the directory c:\bin\alfresco\tomcat\common\lib directory. # I created a c:\data\alf_data directory where the alfresco data will be stored. This is different from the production installation in that the content is stored on a network appliance (\\tornado.shore.mbari.org\alfresco). # I installed a copy of SQL Server 2005 locally to use for the database to back the Alfresco test install. {note} In order to do this without warnings, I had to go back and install IIS through the Add/Remove Programs Control Panel. {note} ## I used the Local System account to run services and only used Windows Authentication logins ## I installed all the service packs and the SQL Server Management Studio product to admin DBs. # In SQL Server, I added the SHORE\DB_Collaboration accounts to the logins. # I created a new database named alfresco-test and made SHORE\DB_Collaboration the owner. # I then went to the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions directory for the customization of the server. ## I edited the custom-repository.properties file ### Changed the dir.root and dir.indexes to look like: {noformat} dir.root=c:/data/alf_data dir.indexes=c:/data/alf_data/lucene-indexes {noformat} ### Commented out the db.* lines for the HSQL Connection (db.driver and db.url) ### Uncommented the db.* lines for MSSQL and changed to use the jTDS driver. They should look like (except the password should be the right one): {noformat} db.driver=net.sourceforge.jtds.jdbc.Driver db.url=jdbc:jtds:sqlserver://localhost/alfresco-test;domain=SHORE;user=DB_Collaboration;password=XXXXXXXXX {noformat} ### I also added the following section to override the mail server settings {noformat} # Mail server configuration mail.host=mail.mbari.org mail.port=25 mail.username= mail.password= {noformat} ## Edited the custom-hibernate-dialect.properties file ### Commented out the HSQL Dialect ### Uncommented the MSSQL Dialect # Now this is not necessarily fun, but in order to really get it configured the way we want it, you need to pull the original .war file out, edit some stuff inside and re-create the .war. {note} This should all be done before starting Alfresco for the first time. {note} # Copy the c:\bin\alfresco\tomcat\webapps\alfresco.war file to your home directory. # Make a second copy so that you will always the original (I copied to alfresco.war.orig and moved it somewhere else. It is important to move it and have only the alfresco.war file in the directory because when you un-jar it, all the files go right where alfresco.war is.) # From a command line, un-jar the war file using: {noformat} jar -xvf alfresco.war {noformat} # This unpacks a lot of files and after it completes, move (or delete) the alfresco.war file from the directory. This needs to be done so it does not end up in the new .war file. # I wanted to change the "Company Home" that seems to be everywhere to something that says MBARI. ## Edited ./WEB-INF/classes/alfresco/messages/webclient.properties and changed company_home from 'Company Home' to 'MBARI Test' ## Edited ./WEB-INF/classes/alfresco/messages/webclient_en_US.properties and changed company_home from 'Company Home' to 'MBARI Test' ## I edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces.properties and changed the first two lines to read {noformat} spaces.company_home.name=MBARI Test spaces.company_home.description=The root of MBARIs Test Alfresco Server {noformat} ## Edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces_en_US.properties and made the same changes as the previous step {tip} This took a bit to find all these, and to be honest, I am not sure which one actually made the change on the GUI, but I suspect it was the _en_US ones. {tip} # When users are imported via LDAP, user spaces get created automatically. In order to put them where I wanted them to go (instead of right in the Company Home), I edited the ./WEB-INF/classes/alfresco/authentication-services-context.xml file. In the file there is a bean with an name of personalHomeFolderProvider. There is a property name 'path' and I added {noformat} /${spaces.user_homes.childname} {noformat} to the end to try to get them to create the user spaces there instead of in the Company Home. The final bean XML looks like: {noformat} /${spaces.company_home.childname}/${spaces.user_homes.childname} ${spaces.store} false All All {noformat} # I wanted to change the logo that is used. I attached the replacement [Alfresco Logo|CLT:Installation Notes^AlfrescoLogo32.png]. Copy this to ./images/logo and overwrite the one that is there. {warning} Note that I did NOT setup SSL for this installation so if I will need to come back and do that if I want truly parallel systems {warning} # Now in order to change the default behavior so that all content is versioned from the start, I edited the .\WEB-INF\classes\alfresco\model\contentModel.xml and searched for the content type definition block. {noformat} Content cm:cmobject true d:content false true false true {noformat} and added the following block right before the ending tag: {noformat} cm:versionable {noformat} so the final block looks like: {noformat} Content cm:cmobject true d:content false true false true cm:versionable {noformat} # That takes care of all the changes to the WAR file. We can now put it back into .war form. # While you are in the directory you expanded the war file in, run ## jar cvfm alfresco.war META-INF\MANIFEST.MF . # You should now have an alfresco.war file in the directory. Move that back to the alfresco install and overwrite the existing one. # Most users like the details view, so I set the default to that by editing c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions\web-client-config-custom.xml and added: {noformat} details 20
20
20 {noformat} right before the closing tag. # Now in order to use MBARI accounts, NTLM authentication was turned on and then chained with the native Alfresco accounts so that we could have non-MBARI accounts on the Alfresco server. ## For simplicity sake, I have attached the files and you can simply download and install them in the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions directory. {note} Before doing these next steps, rename the file-servers-custom.xml file to file-servers-custom.xml.orig so you will have a backup of the original {note} ### First install the [NTLM Configuration XML File|^ntlm-authentication-context.xml] ### Next install the [Authentication Chaining Configuration File|^chaining-authentication-context.xml] ### Next install the [CIFS configuration|^file-servers-custom.xml] file and over-write the existing one. ### Now in order to setup a job that imports users and groups once a day, download and install the [LDAP configuration|^ldap-synchronisation-context.xml] file. ### The ldap sych XML file simply contains all the configuration information with properties to hold the actual values for your installation. To define these properties, I installed the following [properties file|^ldap-synchronisation.properties]. If you are setting up your own installation, you will change these properties for your install. {warning} In the CIFS configuration file, make sure you change the tag to reflect a unique name on the network. {warning} ### Next install the [customized authority configuration|^custom-authority-services-context.xml] file (this gives administrative privs to certain accounts). {warning} Note that I did NOT change the server to take over port 80 traffic as the SQL Server install seemed to want IIS which is currently using port 80 {warning} # Now in order for the alfresco web application to be the default, I edit the c:\bin\alfresco\tomcat\conf\server.xml file and added: {noformat} {noformat} as the last line of the tag section (right before the closing tag). {note} You will also notice the Valve tag that I had to add to turn off proxy cache disabling so that IE clients would work correctly over SSL. Gotta love M$. {note} # Just to keep things clean, I edited the c:\bin\alfresco\alfresco.bat file and put 'rem' in front of the second JAVA_OPTS set as I am using Java 6. # You are now actually ready to start alfresco for the first time! Open a command window and cd over the to c:\bin\alfresco directory and then type: {noformat} alf_start.bat {noformat} # After a long time (took several minutes on a regular PC), look at the alfresco.log file in the c:\bin\alfresco directory and see if it looks like everything started OK, you can also check the database to see if the tables have been created in the alfresco-test database. You should also be able to go to http://alfresco-test.shore.mbari.org:8080 and see the alfresco web application. # Now from the command window where you ran alf_start.bat, run alf_stop.bat to shut the server down. Check the alfresco.log file to see if anything weird happened. If not, try restarting it with alf_start.bat again and look at the alfresco.log file. Sometimes, you can't restart it because you get: {noformat} java.sql.SQLException: Column names in each table must be unique. Column name 'ID_' in table 'JBPM_ACTION' is specified more than once. {noformat} Sigh, so in order to keep Alfresco from hurting itself, you might have to turn off the schema updates. This is done by editing the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions\custom-repository.properties and adding the following: {noformat} db.schema.update=false {noformat} and then restarting alfresco. # To install Alfresco as a Windows Service use a command prompt and enter the following: {noformat} cd c:\bin\alfresco\tomcat\bin service.bat install alfresco tomcat5.exe //US//alfresco --DisplayName "Alfresco Server" tomcat5.exe //US//alfresco --JvmMs=512 --JvmMx=1024 --JvmSs=64 tomcat5.exe //US//alfresco --JavaHome=c:/bin/Java/jrockit-R27.4.0-jdk1.6.0_02 tomcat5.exe //US//alfresco --Environment ALF_HOME=c:/bin/alfresco/ tomcat5.exe //US//alfresco --Environment PATH=c:/bin/alfresco/bin;%PATH% tomcat5.exe //US//alfresco --StartPath c:/bin/alfresco --Startup auto {noformat} # To uninstall the service, at a later time, do the following: {noformat} cd c:\bin\alfresco\tomcat\bin service.bat uninstall alfresco {noformat} # To edit your service settings at any time: {noformat} cd c:\alfresco\tomcat\bin tomcat5w.exe //ES//alfresco {noformat}]]> 3932232 19074108 Backup ...' {column} {section}]]> 19041422 3965001 'Downloads'>'2.1 Releases'>'2.1.1' # I changed to the 'Details View', made 40 items visible, and then downloaded 'alfresco-enterprise-tomcat-2.1.1.zip' file. # I then unzipped the downloaded file to c:\bin which created an alfresco-enterprise-tomcat-2.1.1 folder in c:\bin. # I renamed the alfresco-enterprise-tomcat-2.1.1 folder to simply alfresco. # I then went back to the web browser and went to 'Company Home'>'Downloads'>'2.1 Releases'>'2.1.1'>'License Files' # I am not sure if I can do this with our agreement, but I downloaded the 'enterprise-network-customer-unlimited.lic' file. {note} I did get approval from Joe Van De Graaff at Alfresco to use the license for a test installation to get us through this issue. {note} # I logged out of the Alfresco customer web site. # I Googled on jTDS to find the jTDS JDBC driver and downloaded the jtds-1.2.2-dist.zip file from the website. # Using Windows Explorer, I could just open the jTDS zip file and copy the jtds-1.2.2.jar file. # I then pasted it in the directory c:\bin\alfresco\tomcat\common\lib directory. # I created a c:\data\alf_data directory where the alfresco data will be stored. This is different from the production installation in that the content is stored on a network appliance (\\tornado.shore.mbari.org\alfresco). # I installed a copy of SQL Server 2005 locally to use for the database to back the Alfresco test install. {note} In order to do this without warnings, I had to go back and install IIS through the Add/Remove Programs Control Panel. {note} ## I used the Local System account to run services and only used Windows Authentication logins ## I installed all the service packs and the SQL Server Management Studio product to admin DBs. # In SQL Server, I added the SHORE\DB_Collaboration accounts to the logins. # I created a new database named alfresco-test and made SHORE\DB_Collaboration the owner. # I then went to the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions directory for the customization of the server. ## I edited the custom-repository.properties file ### Changed the dir.root and dir.indexes to look like: {noformat} dir.root=c:/data/alf_data dir.indexes=c:/data/alf_data/lucene-indexes {noformat} ### Commented out the db.* lines for the HSQL Connection (db.driver and db.url) ### Uncommented the db.* lines for MSSQL and changed to use the jTDS driver. They should look like (except the password should be the right one): {noformat} db.driver=net.sourceforge.jtds.jdbc.Driver db.url=jdbc:jtds:sqlserver://localhost/alfresco-test;domain=SHORE;user=DB_Collaboration;password=XXXXXXXXX {noformat} ### I also added the following section to override the mail server settings {noformat} # Mail server configuration mail.host=mail.mbari.org mail.port=25 mail.username= mail.password= {noformat} ## Edited the custom-hibernate-dialect.properties file ### Commented out the HSQL Dialect ### Uncommented the MSSQL Dialect # Now this is not necessarily fun, but in order to really get it configured the way we want it, you need to pull the original .war file out, edit some stuff inside and re-create the .war. {note} This should all be done before starting Alfresco for the first time. {note} # Copy the c:\bin\alfresco\tomcat\webapps\alfresco.war file to your home directory. # Make a second copy so that you will always the original (I copied to alfresco.war.orig and moved it somewhere else. It is important to move it and have only the alfresco.war file in the directory because when you un-jar it, all the files go right where alfresco.war is.) # From a command line, un-jar the war file using: {noformat} jar -xvf alfresco.war {noformat} # This unpacks a lot of files and after it completes, move (or delete) the alfresco.war file from the directory. This needs to be done so it does not end up in the new .war file. # I wanted to change the "Company Home" that seems to be everywhere to something that says MBARI. ## Edited ./WEB-INF/classes/alfresco/messages/webclient.properties and changed company_home from 'Company Home' to 'MBARI Test' ## Edited ./WEB-INF/classes/alfresco/messages/webclient_en_US.properties and changed company_home from 'Company Home' to 'MBARI Test' ## I edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces.properties and changed the first two lines to read {noformat} spaces.company_home.name=MBARI Test spaces.company_home.description=The root of MBARIs Test Alfresco Server {noformat} ## Edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces_en_US.properties and made the same changes as the previous step {tip} This took a bit to find all these, and to be honest, I am not sure which one actually made the change on the GUI, but I suspect it was the _en_US ones. {tip} # When users are imported via LDAP, user spaces get created automatically. In order to put them where I wanted them to go (instead of right in the Company Home), I edited the ./WEB-INF/classes/alfresco/authentication-services-context.xml file. In the file there is a bean with an name of personalHomeFolderProvider. There is a property name 'path' and I added {noformat} /${spaces.user_homes.childname} {noformat} to the end to try to get them to create the user spaces there instead of in the Company Home. The final bean XML looks like: {noformat} /${spaces.company_home.childname}/${spaces.user_homes.childname} ${spaces.store} false All All {noformat} # I wanted to change the logo that is used. I attached the replacement [Alfresco Logo|CLT:Installation Notes^AlfrescoLogo32.png]. Copy this to ./images/logo and overwrite the one that is there. {warning} Note that I did NOT setup SSL for this installation so if I will need to come back and do that if I want truly parallel systems {warning} # Now in order to change the default behavior so that all content is versioned from the start, I edited the .\WEB-INF\classes\alfresco\model\contentModel.xml and searched for the content type definition block. {noformat} Content cm:cmobject true d:content false true false true {noformat} and added the following block right before the ending tag: {noformat} cm:versionable {noformat} so the final block looks like: {noformat} Content cm:cmobject true d:content false true false true cm:versionable {noformat} # That takes care of all the changes to the WAR file. We can now put it back into .war form. # While you are in the directory you expanded the war file in, run ## jar cvfm alfresco.war META-INF\MANIFEST.MF . # You should now have an alfresco.war file in the directory. Move that back to the alfresco install and overwrite the existing one. # Most users like the details view, so I set the default to that by editing c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions\web-client-config-custom.xml and added: {noformat} details 20
20
20 {noformat} right before the closing tag. # Now in order to use MBARI accounts, NTLM authentication was turned on and then chained with the native Alfresco accounts so that we could have non-MBARI accounts on the Alfresco server. ## For simplicity sake, I have attached the files and you can simply download and install them in the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions directory. {note} Before doing these next steps, rename the file-servers-custom.xml file to file-servers-custom.xml.orig so you will have a backup of the original {note} ### First install the [NTLM Configuration XML File|^ntlm-authentication-context.xml] ### Next install the [Authentication Chaining Configuration File|^chaining-authentication-context.xml] ### Next install the [CIFS configuration|^file-servers-custom.xml] file and over-write the existing one. ### Now in order to setup a job that imports users and groups once a day, download and install the [LDAP configuration|^ldap-synchronisation-context.xml] file. ### The ldap sych XML file simply contains all the configuration information with properties to hold the actual values for your installation. To define these properties, I installed the following [properties file|^ldap-synchronisation.properties]. If you are setting up your own installation, you will change these properties for your install. {warning} In the CIFS configuration file, make sure you change the tag to reflect a unique name on the network. {warning} ### Next install the [customized authority configuration|^custom-authority-services-context.xml] file (this gives administrative privs to certain accounts). {warning} Note that I did NOT change the server to take over port 80 traffic as the SQL Server install seemed to want IIS which is currently using port 80 {warning} # Now in order for the alfresco web application to be the default, I edit the c:\bin\alfresco\tomcat\conf\server.xml file and added: {noformat} {noformat} as the last line of the tag section (right before the closing tag). {note} You will also notice the Valve tag that I had to add to turn off proxy cache disabling so that IE clients would work correctly over SSL. Gotta love M$. {note} # Just to keep things clean, I edited the c:\bin\alfresco\alfresco.bat file and put 'rem' in front of the second JAVA_OPTS set as I am using Java 6. # You are now actually ready to start alfresco for the first time! Open a command window and cd over the to c:\bin\alfresco directory and then type: {noformat} alf_start.bat {noformat} # After a long time (took several minutes on a regular PC), look at the alfresco.log file in the c:\bin\alfresco directory and see if it looks like everything started OK, you can also check the database to see if the tables have been created in the alfresco-test database. You should also be able to go to http://alfresco-test.shore.mbari.org:8080 and see the alfresco web application. # Now from the command window where you ran alf_start.bat, run alf_stop.bat to shut the server down. Check the alfresco.log file to see if anything weird happened. If not, try restarting it with alf_start.bat again and look at the alfresco.log file. Sometimes, you can't restart it because you get: {noformat} java.sql.SQLException: Column names in each table must be unique. Column name 'ID_' in table 'JBPM_ACTION' is specified more than once. {noformat} Sigh, so in order to keep Alfresco from hurting itself, you might have to turn off the schema updates. This is done by editing the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions\custom-repository.properties and adding the following: {noformat} db.schema.update=false {noformat} and then restarting alfresco. # To install Alfresco as a Windows Service use a command prompt and enter the following: {noformat} cd c:\bin\alfresco\tomcat\bin service.bat install alfresco tomcat5.exe //US//alfresco --DisplayName "Alfresco Server" tomcat5.exe //US//alfresco --JvmMs=512 --JvmMx=1024 --JvmSs=64 tomcat5.exe //US//alfresco --JavaHome=c:/bin/Java/jrockit-R27.4.0-jdk1.6.0_02 tomcat5.exe //US//alfresco --Environment ALF_HOME=c:/bin/alfresco/ tomcat5.exe //US//alfresco --Environment PATH=c:/bin/alfresco/bin;%PATH% tomcat5.exe //US//alfresco --StartPath c:/bin/alfresco --Startup auto {noformat} # To uninstall the service, at a later time, do the following: {noformat} cd c:\bin\alfresco\tomcat\bin service.bat uninstall alfresco {noformat} # To edit your service settings at any time: {noformat} cd c:\alfresco\tomcat\bin tomcat5w.exe //ES//alfresco {noformat} {warning} These next couple of steps had to be taken to install a patch from Alfresco for an issue with bulk uploads I was having. Essentially when file and path structures get really long and nasty, Alfresco was throwing an error and bailing out. This patch (two Java classes) fixed that issue. {warning} # Next, I downloaded the attached [JAR|^act2139.jar] file and copied it to the c:\bin\alfresco\tomcat\webapps\alfresco\WEB-INF\classes directory. # I backed up the existing two files by copying them to a directory on my desktop so make sure I still had them. The are: ## org/alfresco/filesys/smb/server/SMBSrvPacket.class ## org/alfresco/filesys/util/DataBuffer.class # I shutdown Alfresco and then unjarred the file to install the new classes]]> 3932234 3965002 'Downloads'>'2.1 Releases'>'2.1.1' # I changed to the 'Details View', made 40 items visible, and then downloaded 'alfresco-enterprise-tomcat-2.1.1.zip' file. # I then unzipped the downloaded file to c:\bin which created an alfresco-enterprise-tomcat-2.1.1 folder in c:\bin. # I renamed the alfresco-enterprise-tomcat-2.1.1 folder to simply alfresco. # I then went back to the web browser and went to 'Company Home'>'Downloads'>'2.1 Releases'>'2.1.1'>'License Files' # I am not sure if I can do this with our agreement, but I downloaded the 'enterprise-network-customer-unlimited.lic' file. {note} I did get approval from Joe Van De Graaff at Alfresco to use the license for a test installation to get us through this issue. {note} # I logged out of the Alfresco customer web site. # I Googled on jTDS to find the jTDS JDBC driver and downloaded the jtds-1.2.2-dist.zip file from the website. # Using Windows Explorer, I could just open the jTDS zip file and copy the jtds-1.2.2.jar file. # I then pasted it in the directory c:\bin\alfresco\tomcat\common\lib directory. # I created a c:\data\alf_data directory where the alfresco data will be stored. This is different from the production installation in that the content is stored on a network appliance (\\tornado.shore.mbari.org\alfresco). # I installed a copy of SQL Server 2005 locally to use for the database to back the Alfresco test install. {note} In order to do this without warnings, I had to go back and install IIS through the Add/Remove Programs Control Panel. {note} ## I used the Local System account to run services and only used Windows Authentication logins ## I installed all the service packs and the SQL Server Management Studio product to admin DBs. # In SQL Server, I added the SHORE\DB_Collaboration accounts to the logins. # I created a new database named alfresco-test and made SHORE\DB_Collaboration the owner. # I then went to the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions directory for the customization of the server. ## I edited the custom-repository.properties file ### Changed the dir.root and dir.indexes to look like: {noformat} dir.root=c:/data/alf_data dir.indexes=c:/data/alf_data/lucene-indexes {noformat} ### Commented out the db.* lines for the HSQL Connection (db.driver and db.url) ### Uncommented the db.* lines for MSSQL and changed to use the jTDS driver. They should look like (except the password should be the right one): {noformat} db.driver=net.sourceforge.jtds.jdbc.Driver db.url=jdbc:jtds:sqlserver://localhost/alfresco-test;domain=SHORE;user=DB_Collaboration;password=XXXXXXXXX {noformat} ### I also added the following section to override the mail server settings {noformat} # Mail server configuration mail.host=mail.mbari.org mail.port=25 mail.username= mail.password= {noformat} ## Edited the custom-hibernate-dialect.properties file ### Commented out the HSQL Dialect ### Uncommented the MSSQL Dialect # Now this is not necessarily fun, but in order to really get it configured the way we want it, you need to pull the original .war file out, edit some stuff inside and re-create the .war. {note} This should all be done before starting Alfresco for the first time. {note} # Copy the c:\bin\alfresco\tomcat\webapps\alfresco.war file to your home directory. # Make a second copy so that you will always the original (I copied to alfresco.war.orig and moved it somewhere else. It is important to move it and have only the alfresco.war file in the directory because when you un-jar it, all the files go right where alfresco.war is.) # From a command line, un-jar the war file using: {noformat} jar -xvf alfresco.war {noformat} # This unpacks a lot of files and after it completes, move (or delete) the alfresco.war file from the directory. This needs to be done so it does not end up in the new .war file. # I wanted to change the "Company Home" that seems to be everywhere to something that says MBARI. ## Edited ./WEB-INF/classes/alfresco/messages/webclient.properties and changed company_home from 'Company Home' to 'MBARI Test' ## Edited ./WEB-INF/classes/alfresco/messages/webclient_en_US.properties and changed company_home from 'Company Home' to 'MBARI Test' ## I edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces.properties and changed the first two lines to read {noformat} spaces.company_home.name=MBARI Test spaces.company_home.description=The root of MBARIs Test Alfresco Server {noformat} ## Edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces_en_US.properties and made the same changes as the previous step {tip} This took a bit to find all these, and to be honest, I am not sure which one actually made the change on the GUI, but I suspect it was the _en_US ones. {tip} # When users are imported via LDAP, user spaces get created automatically. In order to put them where I wanted them to go (instead of right in the Company Home), I edited the ./WEB-INF/classes/alfresco/authentication-services-context.xml file. In the file there is a bean with an name of personalHomeFolderProvider. There is a property name 'path' and I added {noformat} /${spaces.user_homes.childname} {noformat} to the end to try to get them to create the user spaces there instead of in the Company Home. The final bean XML looks like: {noformat} /${spaces.company_home.childname}/${spaces.user_homes.childname} ${spaces.store} false All All {noformat} # I wanted to change the logo that is used. I attached the replacement [Alfresco Logo|CLT:Installation Notes^AlfrescoLogo32.png]. Copy this to ./images/logo and overwrite the one that is there. {warning} Note that I did NOT setup SSL for this installation so if I will need to come back and do that if I want truly parallel systems {warning} # Now in order to change the default behavior so that all content is versioned from the start, I edited the .\WEB-INF\classes\alfresco\model\contentModel.xml and searched for the content type definition block. {noformat} Content cm:cmobject true d:content false true false true {noformat} and added the following block right before the ending tag: {noformat} cm:versionable {noformat} so the final block looks like: {noformat} Content cm:cmobject true d:content false true false true cm:versionable {noformat} # That takes care of all the changes to the WAR file. We can now put it back into .war form. # While you are in the directory you expanded the war file in, run ## jar cvfm alfresco.war META-INF\MANIFEST.MF . # You should now have an alfresco.war file in the directory. Move that back to the alfresco install and overwrite the existing one. # Most users like the details view, so I set the default to that by editing c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions\web-client-config-custom.xml and added: {noformat} details 20
20
20 {noformat} right before the closing tag. # Now in order to use MBARI accounts, NTLM authentication was turned on and then chained with the native Alfresco accounts so that we could have non-MBARI accounts on the Alfresco server. ## For simplicity sake, I have attached the files and you can simply download and install them in the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions directory. {note} Before doing these next steps, rename the file-servers-custom.xml file to file-servers-custom.xml.orig so you will have a backup of the original {note} ### First install the [NTLM Configuration XML File|^ntlm-authentication-context.xml] ### Next install the [Authentication Chaining Configuration File|^chaining-authentication-context.xml] ### Next install the [CIFS configuration|^file-servers-custom.xml] file and over-write the existing one. ### Now in order to setup a job that imports users and groups once a day, download and install the [LDAP configuration|^ldap-synchronisation-context.xml] file. ### The ldap sych XML file simply contains all the configuration information with properties to hold the actual values for your installation. To define these properties, I installed the following [properties file|^ldap-synchronisation.properties]. If you are setting up your own installation, you will change these properties for your install. {warning} In the CIFS configuration file, make sure you change the tag to reflect a unique name on the network. {warning} ### Next install the [customized authority configuration|^custom-authority-services-context.xml] file (this gives administrative privs to certain accounts). {warning} Note that I did NOT change the server to take over port 80 traffic as the SQL Server install seemed to want IIS which is currently using port 80 {warning} # Now in order for the alfresco web application to be the default, I edit the c:\bin\alfresco\tomcat\conf\server.xml file and added: {noformat} {noformat} as the last line of the tag section (right before the closing tag). {note} You will also notice the Valve tag that I had to add to turn off proxy cache disabling so that IE clients would work correctly over SSL. Gotta love M$. {note} # Just to keep things clean, I edited the c:\bin\alfresco\alfresco.bat file and put 'rem' in front of the second JAVA_OPTS set as I am using Java 6. # You are now actually ready to start alfresco for the first time! Open a command window and cd over the to c:\bin\alfresco directory and then type: {noformat} alf_start.bat {noformat} # After a long time (took several minutes on a regular PC), look at the alfresco.log file in the c:\bin\alfresco directory and see if it looks like everything started OK, you can also check the database to see if the tables have been created in the alfresco-test database. You should also be able to go to http://alfresco-test.shore.mbari.org:8080 and see the alfresco web application. # Now from the command window where you ran alf_start.bat, run alf_stop.bat to shut the server down. Check the alfresco.log file to see if anything weird happened. If not, try restarting it with alf_start.bat again and look at the alfresco.log file. Sometimes, you can't restart it because you get: {noformat} java.sql.SQLException: Column names in each table must be unique. Column name 'ID_' in table 'JBPM_ACTION' is specified more than once. {noformat} Sigh, so in order to keep Alfresco from hurting itself, you might have to turn off the schema updates. This is done by editing the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions\custom-repository.properties and adding the following: {noformat} db.schema.update=false {noformat} and then restarting alfresco. # To install Alfresco as a Windows Service use a command prompt and enter the following: {noformat} cd c:\bin\alfresco\tomcat\bin service.bat install alfresco tomcat5.exe //US//alfresco --DisplayName "Alfresco Server" tomcat5.exe //US//alfresco --JvmMs=512 --JvmMx=1024 --JvmSs=64 tomcat5.exe //US//alfresco --JavaHome=c:/bin/Java/jrockit-R27.4.0-jdk1.6.0_02 tomcat5.exe //US//alfresco --Environment ALF_HOME=c:/bin/alfresco/ tomcat5.exe //US//alfresco --Environment PATH=c:/bin/alfresco/bin;%PATH% tomcat5.exe //US//alfresco --StartPath c:/bin/alfresco --Startup auto {noformat} # To uninstall the service, at a later time, do the following: {noformat} cd c:\bin\alfresco\tomcat\bin service.bat uninstall alfresco {noformat} # To edit your service settings at any time: {noformat} cd c:\alfresco\tomcat\bin tomcat5w.exe //ES//alfresco {noformat} {warning} These next couple of steps had to be taken to install a patch from Alfresco for an issue with bulk uploads I was having. Essentially when file and path structures get really long and nasty, Alfresco was throwing an error and bailing out. This patch (two Java classes) fixed that issue. {warning} # Next, I downloaded the attached [JAR|^act2139.jar] file and copied it to the c:\bin\alfresco\tomcat\webapps\alfresco\WEB-INF\classes directory. # I shutdown Alfresco and then unjarred the file to install the new classes. They are: ## org/alfresco/filesys/smb/server/SMBSrvPacket.class ## org/alfresco/filesys/util/DataBuffer.class # I would assume since they do not overwrite anything, that this location is further up in the class loader and so it will load these new classes first. # I deleted the act2139.jar file and the META-INF directory that the unjarring process created. # To verify this took, I ran alfresco with the {noformat} CATALINA_OPTS="-verbose:class" {noformat} and verifyied that I saw: {noformat} [Loaded org.alfresco.filesys.smb.server.SMBSrvPacket from file:/opt/alfresco211/tomcat/webapps/alfresco/WEB-INF /classes/org/alfresco/filesys/smb/server/SMBSrvPacket.class] {noformat} and NOT: {noformat} Loaded org.alfresco.filesys.smb.server.SMBSrvPacket from file:/opt/alfresco211/tomcat/webapps/alfresco/WEB-INF/lib /alfresco-repository.jar] {noformat} ]]> 3932235 19074114 Backup ...' # \[kgomes\] Accepted the defaults # \[kgomes\] Under options, I selected 'Verify after backup' # \[kgomes\] Under General, I selected 'Disk' as the destination, then clicked on 'Add...' # \[kgomes\] I added the file name '2012_12_12_2.1.1' to the default path as the file name to save it to # \[kgomes\] # \[kgomes\] # \[kgomes\] # \[kgomes\] # \[kgomes\] # \[kgomes\] # \[kgomes\] {panel} {column} {section}]]> 19041428 3964995 Open" and select the elf-file (e.g. "test.elf") you want to debug. Now click on "Run->Connect to target" and enter the following settings: Target: "Remote/TCP" Hostname: "localhost" Port: "2000" Set breakpoint at 'main': yes Set breakpoint at 'exit': yes Attach to target: yes Download Program: yes Command after attaching: "monitor erase all" Run Method: Continue from last Stop When you click on "Ok" Insight should tell you that the connection was successful, and gdbproxy should say "notice: msp430-gdbproxy: connected". To start the debugging click on "Run" or simply press "r". If everything worked correctly you should now see the sourcecode of your program with the first line of main() marked green. The red point is the breakpoint that has been set by Insight automatically. You can set or remove breakpoints by clicking on the '-' in front of the line. Now you can 'c'ontinue the execution to the next breakpoint, 's'tep through the code, or step a single assembler instruction... but be careful with "finish": Insight sometimes seems to lock up with this command. So if you want to finish a function, I recommend setting a breakpoint to the end of the function and using "continue". ]]> 3932228 11273139 Accessories  --> Communications  --> Hyperterm  --> McStar USBser 115200 ** 115200, 8n1, no flow, COM5 * Step 4 - remove magnet from McSTAR 'white spot' ** If no activity, hit ENTER a couple of times and put magnet on white spot and remove. ** Should see a boot screen, do not hit a key to stop autoboot \\ h4. McSTAR Functional Test    •Step 1 - in Hyperterm, after McSTAR has booted, login with by entering 'root' \-JFFS2 message is harmless, but if login not seen due to JFFS2 message, hit ENTER a couple of times. •Step 2 - cd /media/sda1 (USB harddisk connected to McStar) \-List (ls) should show app dir •Step 3 - 'cd /media/sda1/app/scripts' •Step 4 - type 'date', then type 'date \-s "Tue Mar 09 10:54:30 PST 2010"' •Step 4 - start the McSTAR app './run_mcstar.sh' \-Allow it to run until the first recording message comes out.   Say stuff, whistle, whisper, etc. every 10 seconds or so (data blocks vary from 2 to 20 minutes; typically 5 minutes). \-After the first recording data message, hit Ctrl-c (terminate McSTAR data collection). \-"Writing a new audio file D000000..."  h4. Verification •Step 1 - after terminating run_mcstar.sh   In Hyperterm, change directories to the data directory. \-cd /media/sda1/data \-Cd to the latest directory, then cd to R00000 •Find the file and transfer \-In Hyperterm, Transfer  \--> Receive File, use Zmodem (no crash recovery). Close \-In hyperterm, tell McSTAR to transfer the file you recorded • sz D00000 •On the HP Netbook, start Audacity On Windows •Project  \--> Import Raw Data \-Accept the defaults, and change 44100 to 48000 On a Mac •File  --> Import  --> Raw Data... •select file •open file and accept default settings except Sample Rate - change from default value of 44100 Hz to 48000 Hz (sampling rate of McSTAR). \\]]> 11240401 3670851 3638112 11273142 11240404 8388807 8356048 19074112 Backup ...' {panel} {column} {section}]]> 19041426 3964997 'Downloads'>'2.1 Releases'>'2.1.1' # I changed to the 'Details View', made 40 items visible, and then downloaded 'alfresco-enterprise-tomcat-2.1.1.zip' file. # I then unzipped the downloaded file to c:\bin which created an alfresco-enterprise-tomcat-2.1.1 folder in c:\bin. # I renamed the alfresco-enterprise-tomcat-2.1.1 folder to simply alfresco. # I then went back to the web browser and went to 'Company Home'>'Downloads'>'2.1 Releases'>'2.1.1'>'License Files' # I am not sure if I can do this with our agreement, but I downloaded the 'enterprise-network-customer-unlimited.lic' file. {note} I did get approval from Joe Van De Graaff at Alfresco to use the license for a test installation to get us through this issue. {note} # I logged out of the Alfresco customer web site. # I Googled on jTDS to find the jTDS JDBC driver and downloaded the jtds-1.2.2-dist.zip file from the website. # Using Windows Explorer, I could just open the jTDS zip file and copy the jtds-1.2.2.jar file. # I then pasted it in the directory c:\bin\alfresco\tomcat\common\lib directory. # I created a c:\data\alf_data directory where the alfresco data will be stored. This is different from the production installation in that the content is stored on a network appliance (\\tornado.shore.mbari.org\alfresco). # I installed a copy of SQL Server 2005 locally to use for the database to back the Alfresco test install. {note} In order to do this without warnings, I had to go back and install IIS through the Add/Remove Programs Control Panel. {note} ## I used the Local System account to run services and only used Windows Authentication logins ## I installed all the service packs and the SQL Server Management Studio product to admin DBs. # In SQL Server, I added the SHORE\DB_Collaboration accounts to the logins. # I created a new database named alfresco-test and made SHORE\DB_Collaboration the owner. # I then went to the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions directory for the customization of the server. ## I edited the custom-repository.properties file ### Changed the dir.root and dir.indexes to look like: {noformat} dir.root=c:/data/alf_data dir.indexes=c:/data/alf_data/lucene-indexes {noformat} ### Commented out the db.* lines for the HSQL Connection (db.driver and db.url) ### Uncommented the db.* lines for MSSQL and changed to use the jTDS driver. They should look like (except the password should be the right one): {noformat} db.driver=net.sourceforge.jtds.jdbc.Driver db.url=jdbc:jtds:sqlserver://localhost/alfresco-test;domain=SHORE;user=DB_Collaboration;password=XXXXXXXXX {noformat} ### I also added the following section to override the mail server settings {noformat} # Mail server configuration mail.host=mail.mbari.org mail.port=25 mail.username= mail.password= {noformat} ## Edited the custom-hibernate-dialect.properties file ### Commented out the HSQL Dialect ### Uncommented the MSSQL Dialect # Now this is not necessarily fun, but in order to really get it configured the way we want it, you need to pull the original .war file out, edit some stuff inside and re-create the .war. {note} This should all be done before starting Alfresco for the first time. {note} # Copy the c:\bin\alfresco\tomcat\webapps\alfresco.war file to your home directory. # Make a second copy so that you will always the original (I copied to alfresco.war.orig and moved it somewhere else. It is important to move it and have only the alfresco.war file in the directory because when you un-jar it, all the files go right where alfresco.war is.) # From a command line, un-jar the war file using: {noformat} jar -xvf alfresco.war {noformat} # This unpacks a lot of files and after it completes, move (or delete) the alfresco.war file from the directory. This needs to be done so it does not end up in the new .war file. # I wanted to change the "Company Home" that seems to be everywhere to something that says MBARI. ## Edited ./WEB-INF/classes/alfresco/messages/webclient.properties and changed company_home from 'Company Home' to 'MBARI Test' ## Edited ./WEB-INF/classes/alfresco/messages/webclient_en_US.properties and changed company_home from 'Company Home' to 'MBARI Test' ## I edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces.properties and changed the first two lines to read {noformat} spaces.company_home.name=MBARI Test spaces.company_home.description=The root of MBARIs Test Alfresco Server {noformat} ## Edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces_en_US.properties and made the same changes as the previous step {tip} This took a bit to find all these, and to be honest, I am not sure which one actually made the change on the GUI, but I suspect it was the _en_US ones. {tip} # When users are imported via LDAP, user spaces get created automatically. In order to put them where I wanted them to go (instead of right in the Company Home), I edited the ./WEB-INF/classes/alfresco/authentication-services-context.xml file. In the file there is a bean with an name of personalHomeFolderProvider. There is a property name 'path' and I added {noformat} /${spaces.user_homes.childname} {noformat} to the end to try to get them to create the user spaces there instead of in the Company Home. The final bean XML looks like: {noformat} /${spaces.company_home.childname}/${spaces.user_homes.childname} ${spaces.store} false All All {noformat} # I wanted to change the logo that is used. I attached the replacement [Alfresco Logo|CLT:Installation Notes^AlfrescoLogo32.png]. Copy this to ./images/logo and overwrite the one that is there. {warning} Note that I did NOT setup SSL for this installation so if I will need to come back and do that if I want truly parallel systems {warning} # Now in order to change the default behavior so that all content is versioned from the start, I edited the .\WEB-INF\classes\alfresco\model\contentModel.xml and searched for the content type definition block. {noformat} Content cm:cmobject true d:content false true false true {noformat} and added the following block right before the ending tag: {noformat} cm:versionable {noformat} so the final block looks like: {noformat} Content cm:cmobject true d:content false true false true cm:versionable {noformat} # That takes care of all the changes to the WAR file. We can now put it back into .war form. # While you are in the directory you expanded the war file in, run ## jar cvfm alfresco.war META-INF\MANIFEST.MF . # You should now have an alfresco.war file in the directory. Move that back to the alfresco install and overwrite the existing one. # Most users like the details view, so I set the default to that by editing c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions\web-client-config-custom.xml and added: {noformat} details 20
20
20 {noformat} right before the closing tag. # Now in order to use MBARI accounts, NTLM authentication was turned on and then chained with the native Alfresco accounts so that we could have non-MBARI accounts on the Alfresco server. ## For simplicity sake, I have attached the files and you can simply download and install them in the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions directory. {note} Before doing these next steps, rename the file-servers-custom.xml file to file-servers-custom.xml.orig so you will have a backup of the original {note} ### First install the [NTLM Configuration XML File|^ntlm-authentication-context.xml] ### Next install the [Authentication Chaining Configuration File|^chaining-authentication-context.xml] ### Next install the [CIFS configuration|^file-servers-custom.xml] file and over-write the existing one. {warning} In the CIFS configuration file, make sure you change the tag to reflect a unique name on the network. {warning} ### Next install the [customized authority configuration|^custom-authority-services-context.xml] file (this gives administrative privs to certain accounts). {warning} Note that I did NOT change the server to take over port 80 traffic as the SQL Server install seemed to want IIS which is currently using port 80 {warning} # Now in order for the alfresco web application to be the default, I edit the c:\bin\alfresco\tomcat\conf\server.xml file and added: {noformat} {noformat} as the last line of the tag section (right before the closing tag). {note} You will also notice the Valve tag that I had to add to turn off proxy cache disabling so that IE clients would work correctly over SSL. Gotta love M$. {note} # Just to keep things clean, I edited the c:\bin\alfresco\alfresco.bat file and put 'rem' in front of the second JAVA_OPTS set as I am using Java 6. # You are now actually ready to start alfresco for the first time! Open a command window and cd over the to c:\bin\alfresco directory and then type: {noformat} alf_start.bat {noformat} # After a long time (took several minutes on a regular PC), look at the alfresco.log file in the c:\bin\alfresco directory and see if it looks like everything started OK, you can also check the database to see if the tables have been created in the alfresco-test database. You should also be able to go to http://alfresco-test.shore.mbari.org:8080 and see the alfresco web application. # Now from the command window where you ran alf_start.bat, run alf_stop.bat to shut the server down. Check the alfresco.log file to see if anything weird happened. If not, try restarting it with alf_start.bat again and look at the alfresco.log file. Sometimes, you can't restart it because you get: {noformat} java.sql.SQLException: Column names in each table must be unique. Column name 'ID_' in table 'JBPM_ACTION' is specified more than once. {noformat} Sigh, so in order to keep Alfresco from hurting itself, you might have to turn off the schema updates. This is done by editing the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions\custom-repository.properties and adding the following: {noformat} db.schema.update=false {noformat} and then restarting alfresco. # To install Alfresco as a Windows Service use a command prompt and enter the following: {noformat} cd c:\bin\alfresco\tomcat\bin service.bat install alfresco tomcat5.exe //US//alfresco --DisplayName "Alfresco Server" tomcat5.exe //US//alfresco --JvmMs=512 --JvmMx=1024 --JvmSs=64 tomcat5.exe //US//alfresco --JavaHome=c:/bin/Java/jrockit-R27.4.0-jdk1.6.0_02 tomcat5.exe //US//alfresco --Environment ALF_HOME=c:/bin/alfresco/ tomcat5.exe //US//alfresco --Environment PATH=c:/bin/alfresco/bin;%PATH% tomcat5.exe //US//alfresco --StartPath c:/bin/alfresco --Startup auto {noformat} # To uninstall the service, at a later time, do the following: {noformat} cd c:\bin\alfresco\tomcat\bin service.bat uninstall alfresco {noformat} # To edit your service settings at any time: {noformat} cd c:\alfresco\tomcat\bin tomcat5w.exe //ES//alfresco {noformat}]]> 3932230 11273141 Accessories  \--> Communications  \--> Hyperterm  \--> McStar USBser 115200 ** 115200, 8n1, no flow, COM5 * Step 4 - remove magnet from McSTAR 'white spot' ** If no activity, hit ENTER a couple of times and put magnet on white spot and remove. ** Should see a boot screen, do not hit a key to stop autoboot \\ h4. McSTAR Functional Test    * Step 1 - in Hyperterm, after McSTAR has booted, login with by entering 'root' ** JFFS2 message is harmless, but if login not seen due to JFFS2 message, hit ENTER a couple of times. * Step 2 - cd /media/sda1 (USB harddisk connected to McStar) ** List (ls) should show app dir * Step 3 - 'cd /media/sda1/app/scripts' * Step 4 - type 'date', then type 'date \-s "Tue Mar 09 10:54:30 PST 2010"' * Step 4 - start the McSTAR app './run_mcstar.sh' ** Allow it to run until the first recording message comes out.   Say stuff, whistle, whisper, etc. every 10 seconds or so (data blocks vary from 2 to 20 minutes; typically 5 minutes). ** After the first recording data message, hit Ctrl-c (terminate McSTAR data collection). ** "Writing a new audio file D000000..."  h4. Verification •Step 1 - after terminating run_mcstar.sh   In Hyperterm, change directories to the data directory. \-cd /media/sda1/data \-Cd to the latest directory, then cd to R00000 •Find the file and transfer \-In Hyperterm, Transfer  \--> Receive File, use Zmodem (no crash recovery). Close \-In hyperterm, tell McSTAR to transfer the file you recorded • sz D00000 •On the HP Netbook, start Audacity On Windows •Project  \--> Import Raw Data \-Accept the defaults, and change 44100 to 48000 On a Mac •File  \--> Import  \--> Raw Data... •select file •open file and accept default settings except Sample Rate - change from default value of 44100 Hz to 48000 Hz (sampling rate of McSTAR). \\]]> 11240403 8388808 8356049 19074052 19041366 16449729 16416969 4489218 "Downloads">"2.1 Releases">"2.1.1" # I then clicked on alfresco-enterprise-tomcat-2.1.1.zip to download the zip file. # Went to [http://customers.alfresco.com] (I was still logged in) # Went to "Company Home">"Downloads">"2.1 Releases">"2.1.1">"License Files" # I went ahead and downloaded all the "*.lic" files, but I think I only need enterprise-network-customer-unlimited.lic" # Logged out of Alfresco. # Since I suspect I will need a JDBC driver for SQLServer, I downloaded the jTDS-1.2.2 driver from the jtds web site (just Google jtds and go to the download section of the top google return). # I closed the Firefox browser. # I extracted the jtds-1.2.2.jar file from the jtds download # I downloaded and installed the JRockit 6 R27.4 JDK Microsoft Windows (x86 - 32 bit) from BEA's web site {note} After installing JRockit, make sure you set the JAVA_HOME environment variable to point to the installation of JRockit. For example, I went to the desktop, right clicked on the computer, did Properties, then clicked on the Advanced tab, then click on the environment variables button and then created a new system variable named JAVA_HOME and set to c:\bin\Java\jrockit-R27.4.0-jdk1.6.0_02 {note} # I ran the installer, changed the "Program Files" to "bin" in the installation directory for both the JDK and the JRE. I also chose to install the JRE as public. # Using Firefox, I downloaded the PHP 5.2.5 Windows Installer from php.net and installed it. Although I installed it, I did not integrate it with a web server as I want Alfresco to take port 80. I probably did not need to install PHP, but I thought I would anyway. (again, I changed install path from "Program Files" to "bin" # I also downloaded and installed OpenOffice and ran it once so I could get through the initial startup # I setup a Alfresco database on the server Solstice and granted the LAGOON\DB_Collaboration account to be the db_owner of the Alfresco database. # I unzipped the alfresco tomcat zip file to an alfresco directory in c:\bin # I then went to the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions directory for the customization of the server. ## I edited the custom-repository.properties file ### Changed the dir.root and dir.indexes to look like: {noformat} dir.root=//tornado.shore.mbari.org/Alfresco/alf_data dir.indexes=d:/alf_data/lucene-indexes {noformat} ### Commented out the db.* lines for the HSQL Connection (db.driver and db.url) ### Uncommented the db.* lines for MSSQL and changed to use the jTDS driver. They should look like: {noformat} db.driver=net.sourceforge.jtds.jdbc.Driver db.url=jdbc:jtds:sqlserver://solstice.shore.mbari.org/Alfresco;domain=SHORE;user=DB_Collaboration;password=XXXXXXXXX {noformat} ### I also added the following section to override the mail server settings {noformat} # Mail server configuration mail.host=mail.mbari.org mail.port=25 mail.username= mail.password= {noformat} ## Edited the custom-hibernate-dialect.properties file ### Commented out the HSQL Dialect ### Uncommented the MSSQL Dialect # I then installed the jtds-1.2.2.jar in the c:\bin\alfresco\tomcat\common\lib so that it will be on the classpath when Alfresco is started # Now this is not necessarily fun, but in order to really get it configured the way we want it, you need to pull the original .war file out, edit some stuff inside and re-create the .war. {note} This should all be done before starting Alfresco for the first time. {note} # Copy the c:\Alfresco\tomcat\webapps\alfresco.war file to your home directory. # Make a second copy so that you will always the original (I copied to alfresco.war.orig and moved it somewhere else. It is important to move it and have only the alfresco.war file in the directory because when you un-jar it, all the files go right where alfresco.war is.) # From a command line, un-jar the war file using: {noformat} jar -xvf alfresco.war {noformat} # This unpacks a lot of files and after it completes, move (or delete) the alfresco.war file from the directory. This needs to be done so it does not end up in the new .war file. # I wanted to change the "Company Home" that seems to be everywhere to something that says MBARI. ## Edited ./WEB-INF/classes/alfresco/messages/webclient.properties and changed company_home from 'Company Home' to 'MBARI' ## Edited ./WEB-INF/classes/alfresco/messages/webclient_en_US.properties and changed company_home from 'Company Home' to 'MBARI' ## I edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces.properties and changed the first two lines to read {noformat} spaces.company_home.name=MBARI spaces.company_home.description=The root space for MBARI {noformat} ## Edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces_en_US.properties and made the same changes as the previous step {tip} This took a bit to find all these, and to be honest, I am not sure which one actually made the change on the GUI, but I suspect it was the _en_US ones. {tip} # When users are imported via LDAP, user spaces get created automatically. In order to put them where I wanted them to go (instead of right in the Company Home), I edited the ./WEB-INF/classes/alfresco/authentication-services-context.xml file. In the file there is a bean with an name of personalHomeFolderProvider. There is a property name 'path' and I added {noformat} /${spaces.user_homes.childname} {noformat} to the end to try to get them to create the user spaces there instead of in the Company Home. The final bean XML looks like: {noformat} /${spaces.company_home.childname}/${spaces.user_homes.childname} ${spaces.store} false All All {noformat} # I wanted to change the logo that is used. I attached the replacement logo [here|^AlfrescoLogo32.png]. Copy this to ./images/logo and overwrite the one that is there. # In order to setup SSL for the application (will do that later), edit ./WEB-INF/web.xml and add the following {noformat} Login Pages /* CONFIDENTIAL {noformat} right before the ending tag at the bottom of the file. # Now in order to change the default behavior so that all content is versioned from the start, I edited the .\WEB-INF\classes\alfresco\model\contentModel.xml and searched for the content type definition block. {noformat} Content cm:cmobject true d:content false true false true {noformat} and added the following block right before the ending tag: {noformat} cm:versionable {noformat} so the final block looks like: {noformat} Content cm:cmobject true d:content false true false true cm:versionable {noformat} # That takes care of all the changes to the WAR file. We can now put it back into .war form. # While you are in the directory you expanded the war file in, run ## jar cvfm alfresco.war META-INF\MANIFEST.MF . # You should now have an alfresco.war file in the directory. Move that back to the alfresco install and overwrite the existing one. # Most users like the details view, so I set the default to that by editing c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions\web-client-config-custom.xml and added: {noformat} details 20
20
20 {noformat} right before the closing tag. # Now in order to use MBARI accounts, NTLM authentication was turned on and then chained with the native Alfresco accounts so that we could have non-MBARI accounts on the Alfresco server. ## In order to enable NTLM and native Alfresco authentication, I had to edit two files. For simplicity I have just attached them here and they can be downloaded and installed in the extensions directory. ### The first file is the [ntlm-authentication-context.xml|^ntlm-authentication-context.xml] file. This configures and enables NTLM authentication. ### The next file was the [chaining-authentication-context.xml|^chaining-authentication-context.xml] file which enabled Alfresco authentication and chained it together with the NTLM authentication from the previous file. # Then in order to setup CIFS on the server, I edited the file-servers-custom.xml file to look like the attached [file-servers-custom.xml|^file-servers-custom.xml] file. # In order to grant certain accounts admin privs, I created a new custom-authority-services-context.xml in the same directory as the ldap-authentication-context.xml file and added {noformat} kgomes admin administrator {noformat} # In order for Alfresco to handle all port 80 traffic, I changed Tomcat so that it takes port 80 and SSL goes over port 443. So I edited the c:\Alfresco\tomcat\conf\server.xml file and changed the 8080 port to 80 and the 8443 port to 443 (the 443 change is done in two places). # Now I needed to setup the SSL for the web traffic. Cathy Sewell was instrumental in getting this working. She ordered a new certificate specifically for alfresco and put it in the c:\local\cert folder. Here are the instructions for what she did to get the certficate installed. {noformat} SSL certificate for server Alfresco - 1/2/08 C:\bin\Java\jrockit-R27.1.0-jre1.6.0_02\bin>keytool -genkey -alias tomcat -keyalg RSA -keystore tomcat.keystore What is your first and last name? [alfresco.mbari.org]: What is the name of your organizational unit? [IS]: What is the name of your organization? [MBARI]: What is the name of your City or Locality? [Moss Landing]: What is the name of your State or Province? [CD]: CA What is the two-letter country code for this unit? [US]: Is CN=alfresco.mbari.org, OU=IS, O=MBARI, L=Moss Landing, ST=CA, C=US correct? [no]: y Enter key password for (RETURN if same as keystore password): C:\bin\Java\jrockit-R27.4.0-jre1.6.0_02\bin>keytool -certreq -keyalg RSA -alias tomcat -file certreq.csr -keystore tomcat.keystore Enter keystore password: Generated certificate request file, certreq.csr, was submitted to SSL provider. Certificate provider sent certificate file (alfresco.mbari.org.crt), along with gd_bundle.crt, gd_cross_intermediate.crt, and gd_intermediate.crt. Additionally, I downloaded valicert_class2_root.cer from their website. These files were stored in c:\local\cert. The following commands were used to add them to the tomcat keystore: C:\bin\Java\jrockit-R27.4.0-jre1.6.0_02\bin>keytool -import -alias root -keystore tomcat.keystore -trustcacerts -file c:\local\cert\valicert_class2_root.cer Enter keystore password: Certificate already exists in system-wide CA keystore under alias Do you still want to add it to your own keystore? [no]: y Certificate was added to keystore C:\bin\Java\jrockit-R27.4.0-jre1.6.0_02\bin>keytool -import -alias cross -keystore tomcat.keystore -trustcacerts -file c:\local\cert\gd_cross_intermediate.crt Enter keystore password: Certificate was added to keystore C:\bin\Java\jrockit-R27.4.0-jre1.6.0_02\bin>keytool -import -alias intermed -keystore tomcat.keystore -trustcacerts -file c:\local\cert\gd_intermediate.crt Enter keystore password: Certificate was added to keystore C:\bin\Java\jrockit-R27.4.0-jre1.6.0_02\bin>keytool -import -alias tomcat -keystore tomcat.keystore -trustcacerts -file c:\local\cert\alfresco.mbari.org.crt Enter keystore password: Certificate reply was installed in keystore {noformat} # I edited the c:\bin\alfresco\tomcat\conf\server.xml file and uncommented the SSL section and edited to look like that shown below. {noformat} {noformat} # Since I was in the server.xml file, I went ahead and changed it so that the default webapp was alfresco so that you would get alfresco anytime you went to the base URL. I did this by adding: {noformat} {noformat} as the last line of the tag section (right before the closing tag). {note} You will also notice the Valve tag that I had to add to turn off proxy cache disabling so that IE clients would work correctly over SSL. Gotta love M$. {note} # I copied the enterprise-network-unlimited.lic file into the c:\Alfresco\tomcat\shared\classes\alfresco\extensions\license directory # Just to keep things clean, I edited the c:\bin\alfresco\alfresco.bat file and put 'rem' in front of the second JAVA_OPTS set as I am using Java 6. # Now after you run it for the first time and the database structure gets created, you can't restart it because you get: {noformat} java.sql.SQLException: Column names in each table must be unique. Column name 'ID_' in table 'JBPM_ACTION' is specified more than once. {noformat} Sigh, so in order to keep Alfresco from hurting itself, I had to turn off the schema updates. This is done by editing the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions\custom-repository.properties and adding the following: {noformat} db.schema.update=false {noformat} and then restarting alfresco. # To install Alfresco as a Windows Service use a command prompt and enter the following: {noformat} cd c:\bin\alfresco\tomcat\bin service.bat install alfresco tomcat5.exe //US//alfresco --DisplayName "Alfresco Server" tomcat5.exe //US//alfresco --JvmMs=512 --JvmMx=1024 --JvmSs=64 tomcat5.exe //US//alfresco --JavaHome=c:/bin/Java/jrockit-R27.4.0-jdk1.6.0_02 tomcat5.exe //US//alfresco --Environment ALF_HOME=c:/bin/alfresco/ tomcat5.exe //US//alfresco --Environment PATH=c:/bin/alfresco/bin;%PATH% tomcat5.exe //US//alfresco --StartPath c:/bin/alfresco --Startup auto {noformat} # To uninstall the service, at a later time, do the following: {noformat} cd c:\bin\alfresco\tomcat\bin service.bat uninstall alfresco {noformat} # To edit your service settings at any time: {noformat} cd c:\alfresco\tomcat\bin tomcat5w.exe //ES//alfresco {noformat} # In order to install certain modules (like the email listener), I had to get the Alfresco Module Manager from the customers.alfresco.com download site. I downloaded the alfresco-mmt-2.1.1.jar file locally so I could use it to install modules. # I then downloaded the email listener module from [http://forge.alfresco.com/projects/email-listener/]. It came as a zip file, so I unzipped it and it created a folder with the appropriate emailListener.amp in it. # Make another backup copy of the alfresco.war file and put somewhere in case you want to roll this back. # Open a command prompt windows and cd to the location where the Alfresco Module Manager jar is. # Run the following: {noformat} java -jar alfresco-mmt-2.1.1.jar path_to_emailListener.amp path_to_alfresco.war {noformat} So for me this looked like: {noformat} java -jar alfresco-mmt-2.1.1.jar .\email-listener_2.1RC2\emailListener.amp c:\bin\alfresco\tomcat\webapps\alfresco.war {noformat} # You should be able to verify the install by running: {noformat} java -jar alfresco-mmt-2.1.1.jar list c:\bin\alfresco\tomcat\webapps\alfresco.war {noformat} and you should see something like: {noformat} Module 'emailListener' installed in 'c:\bin\alfresco\tomcat\webapps\alfresco.war' - Title: EmailListener - Version: 2.1 - Install Date: Fri Dec 07 08:43:10 PST 2007 - Desription: EmailListener Module {noformat} # Finally, to start the service, just go into your Windows Service control panel and locate the service that is now named 'Alfresco Server'. You can start and stop Alfresco from this control panel. h1. Content Migration Now, in order to migrate content from old alfresco and normal file structures, I did the following: h3. For content already in alfresco: # Navigate to the space whose contents you want to migrate. For example, let's say I want to migrate the stuff from my personal space. I would navigate (using the WebUI) to the /MBARI/User Homes/kgomes space. You should see the contents of the kgomes folder from this view. # Click on 'More actions->View Details'. # On the right hand side, click on 'Export'. # For package name, I usually enter the space name followed by '_export', but it doesn't really matter. # Click on the link that says 'Click here to select the destination' and select somewhere that you will be able to download the .acp file from. # Select 'Current Space'. # Select 'Include Children'. # Uncheck 'Include this space' unless you have content (documents) in this specific folder (anything other than folders) that you want to migrate. This is a bit tricky, but there are two ways to do this. If you want to have the top level folder created, use the 'Include this space' and that will create the top level folder. Otherwise, if will expand into the folder in which you import the .acp file into. This is important in cases where the folder has already been created for you (like with user homes) and you have to migrate content into that folder. If you have the option to create the top level directory, by all means do so. # Uncheck 'Export in background' so you can force it to happen and you know when it is complete.]]> 4456450 19074056 19041370 19074058 19041372 17268957 17236194 11273096 Import Raw Data \-Accept the defaults, and change 44100 to 48000\\ h4. Verification \\ \\ •Step 1 - after terminating run_mcstar.sh   In Hyperterm, change directories to the data directory. \-cd /media/sda1/data \-Cd to the latest directory, then cd to R00000 •Find the file and transfer \-In Hyperterm, TransferàReceive File, use Zmodem (no crash recovery). Close \-In hyperterm, tell Mcstar to transfer the file you recorded • sz D00000 •On the HP Netbook, start Audacity \-Start-->Programs-->Audacity \\]]> 11240358 11273094 11240356 17268961 17236198 11273091 11240353 11273092 11240354 17268959 17236196 11273122 Accessories  --> Communications  --> Hyperterm  --> McStar USBser 115200 \-115200, 8n1, no flow, COM5 •Step 4 - remove magnet from McStar 'white spot' \-If no activity, hit ENTER a couple of times and put magnet on white spot and remove. \-Should see a boot screen, do not hit a key to stop autoboot \\ h4. McStar Functional Test    •Step 1 - in Hyperterm, after Mcstar has booted, login with by entering 'root' \-JFFS2 message is harmless, but if login not seen due to JFFS2 message, hit ENTER a couple of times. •Step 2 - cd /media/sda1 (USB harddisk connected to McStar) \-List (ls) should show app dir •Step 3 - 'cd /media/sda1/app/scripts' •Step 4 - type 'date', then type 'date \-s "Tue Mar 09 10:54:30 PST 2010"' •Step 4 - start the McStar app './run_mcstar.sh' \-Allow it to run until the first recording message comes out.   Say stuff, whistle, whisper, etc. every 10 seconds or so (data blocks vary from 2 to 20 minutes; typically 5 minutes). \-After the first recording data message, hit Ctrl-c (terminate McSTAR data collection). \-"Writing a new audio file D000000..."  h4. Verification •Step 1 - after terminating run_mcstar.sh   In Hyperterm, change directories to the data directory. \-cd /media/sda1/data \-Cd to the latest directory, then cd to R00000 •Find the file and transfer \-In Hyperterm, Transfer  --> Receive File, use Zmodem (no crash recovery). Close \-In hyperterm, tell Mcstar to transfer the file you recorded • sz D00000 •On the HP Netbook, start Audacity On Windows •Project --> Import Raw Data \-Accept the defaults, and change 44100 to 48000 On a Mac File  --> Import  --> Raw Data... select file open file and accept default settings except Sample Rate - change from default value of 44100 Hz to 48000 Hz (sampling rate of McSTAR). \\]]> 11240384 25100290 25067522 16449711 16416950 11273120 Accessories  \-\- Communications  \--> Hyperterm  \-->McStar USBser 115200 \-115200, 8n1, no flow, COM5 •Step 4 - remove magnet from McStar 'white spot' \-If no activity, hit ENTER a couple of times and put magnet on white spot and remove. \-Should see a boot screen, do not hit a key to stop autoboot \\ h4. McStar Functional Test    •Step 1 - in Hyperterm, after Mcstar has booted, login with by entering 'root' \-JFFS2 message is harmless, but if login not seen due to JFFS2 message, hit ENTER a couple of times. •Step 2 - cd /media/sda1 (USB harddisk connected to McStar) \-List (ls) should show app dir •Step 3 - 'cd /media/sda1/app/scripts' •Step 4 - type 'date', then type 'date \-s "Tue Mar 09 10:54:30 PST 2010"' •Step 4 - start the McStar app './run_mcstar.sh' \-Allow it to run until the first recording message comes out.   Say stuff, whistle, whisper, etc. every 10 seconds or so (data blocks vary from 2 to 20 minutes; typically 5 minutes). \-After the first recording data message, hit Ctrl-c (terminate McSTAR data collection). \-"Writing a new audio file D000000..."  h4. Verification •Step 1 - after terminating run_mcstar.sh   In Hyperterm, change directories to the data directory. \-cd /media/sda1/data \-Cd to the latest directory, then cd to R00000 •Find the file and transfer \-In Hyperterm, Transfer  \--> Receive File, use Zmodem (no crash recovery). Close \-In hyperterm, tell Mcstar to transfer the file you recorded • sz D00000 •On the HP Netbook, start Audacity On Windows •Project --> Import Raw Data \-Accept the defaults, and change 44100 to 48000 On a Mac File  \--> Import  \--> Raw Data... select file open file and accept default settings except Sample Rate - change from default value of 44100 Hz to 48000 Hz (sampling rate of McSTAR). \\]]> 11240382 19074069 3.4.10 (or latest) on alfresco-test.shore.mbari.org ## Tribloom to verify all is working properly {note} Don't forget to verify Gliffy diagrams as well at each verification step. {note} ## MBARI to upgrade database on ?.shore.mbari.org from 2005 compatibility mode to 2008. ## Tribloom to verify all is working properly ## Tribloom to install/upgrade alfresco-test-rhel.shore.mbari.org from alfreso-test.shore.mbari.org ## Tribloom to verify all is working properly ## Tribloom to upgrade from 3.4.10 to 4.1.1 on alfresco-test-rhel.shore.mbari.org ## Tribloom to verify all is working properly ## Assuming all is well, proceed to production system ## Shutdown alfresco.mbari.org ## Backup database on equinox.shore.mbari.org ## Backup //atlas.shore.mbari.org/Alfresco/alf_data ## Backup d:\alf_data\lucene-indexes on alfresco.mbari.org ## Tribloom to upgrade 2.1.1 -> 3.4.10 (or latest) on alfresco.mbari.org ## Tribloom to verify all is working properly. ## MBARI to upgrade database on equinox.shore.mbari.org from 2005 compatibility mode to 2008. ## Tribloom to verify all is working properly. ## Tribloom to install/upgrade alfresco-rhel.mbari.org from alfresco.mbari.org ## Tribloom to verify all is working properly. ## Tribloom to upgrade from 3.4.10 to 4.1.1 on alfresco-rhel.mbari.org ## Tribloom to verify all is working properly.]]> 19041383 11273118 Import Raw Data \-Accept the defaults, and change 44100 to 48000 On a Mac File  --> Import  --> Raw Data... select file open file and accept default settings except Sample Rate - change from default value of 44100 Hz to 48000 Hz (sampling rate of McSTAR). \\]]> 11240380 16449707 16416946 19074071 3.4.10 (or latest) on alfresco-test.shore.mbari.org ## Tribloom to verify all is working properly ## MBARI to upgrade database on ?.shore.mbari.org from 2005 compatibility mode to 2008. ## Tribloom to verify all is working properly ## Tribloom to install/upgrade alfresco-test-rhel.shore.mbari.org from alfreso-test.shore.mbari.org ## Tribloom to verify all is working properly ## Tribloom to upgrade from 3.4.10 to 4.1.1 on alfresco-test-rhel.shore.mbari.org ## Tribloom to verify all is working properly ## Assuming all is well, proceed to production system ## Shutdown alfresco.mbari.org ## Backup database on equinox.shore.mbari.org ## Backup //atlas.shore.mbari.org/Alfresco/alf_data ## Backup d:\alf_data\lucene-indexes on alfresco.mbari.org ## Tribloom to upgrade 2.1.1 -> 3.4.10 (or latest) on alfresco.mbari.org ## Tribloom to verify all is working properly. ## MBARI to upgrade database on equinox.shore.mbari.org from 2005 compatibility mode to 2008. ## Tribloom to verify all is working properly. ## Tribloom to install/upgrade alfresco-rhel.mbari.org from alfresco.mbari.org ## Tribloom to verify all is working properly. ## Tribloom to upgrade from 3.4.10 to 4.1.1 on alfresco-rhel.mbari.org ## Tribloom to verify all is working properly.]]> 19041385 11273116 Import Raw Data \-Accept the defaults, and change 44100 to 48000 On a Mac File \--> Import \--> Raw Data... select file open file and accept default settings except Sample Rate - change from default value of 44100 Hz to 48000 Hz (sampling rate of McSTAR). \\]]> 11240378 16449709 16416948 19074073 3.4.10 (or latest) on alfresco-test.shore.mbari.org ## Tribloom to verify all is working properly ## MBARI to upgrade database on ?.shore.mbari.org from 2005 compatibility mode to 2008. ## Tribloom to verify all is working properly ## Tribloom to install/upgrade alfresco-test-rhel.shore.mbari.org from alfreso-test.shore.mbari.org ## Tribloom to verify all is working properly ## Tribloom to upgrade from 3.4.10 to 4.1.1 on alfresco-test-rhel.shore.mbari.org ## Tribloom to verify all is working properly ## Assuming all is well, proceed to production system ## Shutdown alfresco.mbari.org ## Backup database on equinox.shore.mbari.org ## Backup //atlas.shore.mbari.org/Alfresco/alf_data ## Backup d:\alf_data\lucene-indexes on alfresco.mbari.org ## Tribloom to upgrade 2.1.1 -> 3.4.10 (or latest) on alfresco.mbari.org ## Tribloom to verify all is working properly. ## MBARI to upgrade database on equinox.shore.mbari.org from 2005 compatibility mode to 2008. ## Tribloom to verify all is working properly. ## Tribloom to install/upgrade alfresco-rhel.mbari.org from alfresco.mbari.org ## Tribloom to verify all is working properly. ## Tribloom to upgrade from 3.4.10 to 4.1.1 on alfresco-rhel.mbari.org ## Tribloom to verify all is working properly.]]> 19041387 11273113 Import Raw Data \-Accept the defaults, and change 44100 to 48000]]> 11240375 19074075 3.4.10 (or latest) on alfresco-test.shore.mbari.org ## Tribloom to verify all is working properly ## MBARI to upgrade database on ?.shore.mbari.org from 2005 compatibility mode to 2008. ## Tribloom to verify all is working properly ## Tribloom to install/upgrade alfresco-test-rhel.shore.mbari.org from alfreso-test.shore.mbari.org ## Tribloom to verify all is working properly ## Tribloom to upgrade from 3.4.10 to 4.1.1 on alfresco-test-rhel.shore.mbari.org ## Tribloom to verify all is working properly ## Assuming all is well, proceed to production system ## Shutdown alfresco.mbari.org ## Backup database on equinox.shore.mbari.org ## Backup //atlas.shore.mbari.org/Alfresco/alf_data ## Backup d:\alf_data\lucene-indexes on alfresco.mbari.org ## Tribloom to upgrade 2.1.1 -> 3.4.10 (or latest) on alfresco.mbari.org ## Tribloom to verify all is working properly. ## MBARI to upgrade database on equinox.shore.mbari.org from 2005 compatibility mode to 2008. ## Tribloom to verify all is working properly. ## Tribloom to install/upgrade alfresco-rhel.mbari.org from alfresco.mbari.org ## Tribloom to verify all is working properly. ## Tribloom to upgrade from 3.4.10 to 4.1.1 on alfresco-rhel.mbari.org ## Tribloom to verify all is working properly.]]> 19041389 16449705 16416944 19074078 19041392 11273111 Import Raw Data \-Accept the defaults, and change 44100 to 48000 \\]]> 11240373 19074077 3.4.10 (or latest) on alfresco-test.shore.mbari.org ## Tribloom to verify all is working properly ## MBARI to upgrade database on ?.shore.mbari.org from 2005 compatibility mode to 2008. ## Tribloom to verify all is working properly ## Tribloom to install/upgrade alfresco-test-rhel.shore.mbari.org from alfreso-test.shore.mbari.org ## Tribloom to verify all is working properly ## Tribloom to upgrade from 3.4.10 to 4.1.1 on alfresco-test-rhel.shore.mbari.org ## Tribloom to verify all is working properly ## Assuming all is well, proceed to production system ## Shutdown alfresco.mbari.org ## Backup database on equinox.shore.mbari.org ## Backup //atlas.shore.mbari.org/Alfresco/alf_data ## Backup d:\alf_data\lucene-indexes on alfresco.mbari.org ## Tribloom to upgrade 2.1.1 -> 3.4.10 (or latest) on alfresco.mbari.org ## Tribloom to verify all is working properly. ## MBARI to upgrade database on equinox.shore.mbari.org from 2005 compatibility mode to 2008. ## Tribloom to verify all is working properly. ## Tribloom to install/upgrade alfresco-rhel.mbari.org from alfresco.mbari.org ## Tribloom to verify all is working properly. ## Tribloom to upgrade from 3.4.10 to 4.1.1 on alfresco-rhel.mbari.org ## Tribloom to verify all is working properly.]]> 19041391 19074080 19041394 11273109 Import Raw Data \-Accept the defaults, and change 44100 to 48000 \\ h4. Verification \\ \\ •Step 1 - after terminating run_mcstar.sh   In Hyperterm, change directories to the data directory. \-cd /media/sda1/data \-Cd to the latest directory, then cd to R00000 •Find the file and transfer \-In Hyperterm, TransferàReceive File, use Zmodem (no crash recovery). Close \-In hyperterm, tell Mcstar to transfer the file you recorded • sz D00000 •On the HP Netbook, start Audacity \-Start\-->Programs-\->Audacity \\]]> 11240371 16449701 16416940 19074082 19041396 11273059 " ## \# Set the RTC, only if a battery has been installed on the Beagleboard# # set the battery backed RTC, "hwclock \-w" ## \# Build the McStar Natively# # Enter "shutdown now". # Power off Beagleboard # Remove Ethernet Dongle # Attach a (not so) freshly EXT3 formatted USB drive to the host # Enter "cp \-R /media/sda1/McStar/app /media/sda1/." # Remove the USB host from the host and connect it to the Beagleboard # Power up the Beagleboard # Enter "root" at the Linux prompt # Enter "cd /media/sda1/app/src" # Enter "touch Makefile \*.h \*.cpp" # Enter "make clean" # Enter "make" ## \# Test the McStar App for 10 minutes, writing a new file every minute # Enter "mkdir /media/sda/data" # Enter "cd /media/sda/app/scripts" # Enter "./test_mcstar.sh"]]> 11240320 11273062 " ## \# Set the RTC, only if a battery has been installed on the Beagleboard# # set the battery backed RTC, "hwclock \-w" ## \# Build the McStar Natively# # Enter "shutdown now". # Power off Beagleboard # Remove Ethernet Dongle # Attach a (not so) freshly EXT3 formatted USB drive to the host # Enter "cp \-R /media/sda1/McStar/app /media/sda1/." # Remove the USB host from the host and connect it to the Beagleboard # Power up the Beagleboard # Enter "root" at the Linux prompt # Enter "cd /media/sda1/app/src" # Enter "touch Makefile \*.h \*.cpp" # Enter "make clean" # Enter "make" ## \# Test the McStar App for 10 minutes, writing a new file every minute # Enter "mkdir /media/sda1/data" # Enter "cd /media/sda1/app/scripts" # Enter "./test_mcstar.sh"]]> 11240323 11273061 11240322 11273063 " ## \# Set the RTC, only if a battery has been installed on the Beagleboard# # set the battery backed RTC, "hwclock \-w" ## \# Build the McStar Natively# # Enter "shutdown now". # Power off Beagleboard # Remove Ethernet Dongle # Attach a (not so) freshly EXT3 formatted USB drive to the host # Enter "cp \-R /media/sda1/McStar/app /media/sda1/." # Remove the USB host from the host and connect it to the Beagleboard # Power up the Beagleboard # Enter "root" at the Linux prompt # Enter "cd /media/sda1/app/src" # Enter "touch Makefile \*.h \*.cpp" # Enter "make clean" # Enter "make" ## \# Test the McStar App for 10 minutes, writing a new file every minute # Enter "mkdir /media/sda1/data" # Enter "cd /media/sda1/app/scripts" # Enter "./test_mcstar.sh"\\ \\ SD Card Copy h1. Copy Linux filesystem on bootable SD card This tutorial is part of our Tutorials section. It shows how to flash an image onto an SD/SDHC card. This guide assumes that the card is correctly partitioned, as described in the Create a bootable SD/SDHC card in Ubuntu tutorial. h4. Steps in this tutorial # Mount the SD/SDHC card (if not already mounted) # Write bootloader if necessary # Write Linux kernel image # Write Linux root file system # Unmount h1. Quick Solution: Copy an already existing card If you have already one working SD image and an (absolutely similar) formatted second card, you can just copy them. WARNING Please be aware that the filesystem names (/dev/sdb1, etc.) can differ from system to system, make sure to select the right one. Copy one SD card to another: sudo dd if=/dev/sdb of=/dev/sdcThe safer alternative: Copy the SD card to harddisk and then onto another sudo dd if=/dev/sdb of=~/sd-card-copy.binNow back on the second SD card: sudo dd if=~/sd-card-copy.bin of=/dev/sdb h1. Mount SD/SDHC card Check where linux mounted the card. One way is to check this via mount . Call mount to see where the card has been mounted. Two partitions should have been mounted, one named '/media/BOOT' and the other one '/media/LINUX'. Note the device name, e.g. '/dev/sdb'. mountIf the card has not been mounted, you have two choices: h3. Automatic _Just unplug and re-plug the cardreader. It will be detected and mounted automatically._ h3. Manually If the check with mount didn't work out, use dmesg: dmesg | tailWatch out for a line like this: [sdc] Attached SCSI removable diskWhere *sdc* could also be sdc or sdd. If it was sdb, the device name of the memory card is */dev/sdc*. sudo mkdir -p /media/BOOT sudo mount /dev/sdc1 /media/BOOT sudo mkdir -p /media/LINUX sudo mount /dev/sdc2 /media/LINUX h1. Copy files on the BOOT partition (MLO, u-boot.bin and uImage) _Please note that the bootloader files don't have to be rewritten every time. This applies especially when a new custom Linux system is created with_ BitBake and OpenEmbedded_. However if you work close to the hardware, e.g. on drivers, this is different._ h4. Overo Download MLO and uBoot from this link (commands for shell below): * PIXHAWK OpenEmbedded Images Download (OpenCV and libdc1394 ready) *IMPORTANT: Copy MLO FIRST\!*. The commands below download the two files and copy them in the right order on the boot partition. _You may have to adjust the filenames for future revisions._ cd $HOME wget http://pixhawk.ethz.ch/wiki/_media/symlink/images/overo/mlo-overo wget http://pixhawk.ethz.ch/wiki/_media/symlink/images/overo/u-boot.bin-overoAnd now copy the two files onto the boot partition (*MLO first* because of a bug in the X-loader which causes problems if MLO is not the first file written onto the boot partition). cp MLO-overo* /media/BOOT/MLO cp u-boot.bin-overo* /media/BOOT/u-boot.bin The Linux kernel (*uImage*) resides also on the *BOOT* partition of the SD-card. If you compile a new version of the kernel you have to copy the new *uImage* on the BOOT partition. See the instructions below. h4. BeagleBoard Download MLO and uBoot from this link (commands for shell below): * http://www.angstrom-distribution.org/demo/beagleboard/ * Only for PIXHAWK Team (_will be made public in october_) *IMPORTANT: Copy MLO FIRST\!*. The commands below download the two files and copy them in the right order on the boot partition. _You may have to adjust the filenames for future revisions._ cd $HOME wget http://www.angstrom-distribution.org/demo/beagleboard/MLO wget http://www.angstrom-distribution.org/demo/beagleboard/u-boot.binAnd now copy the two files onto the boot partition (*MLO first* because of a bug in the X-loader which causes problems if MLO is not the first file written onto the boot partition). cp MLO /media/BOOT/MLO cp u-boot.bin /media/BOOT/u-boot.bin The Linux kernel (*uImage*) resides also on the *BOOT* partition of the SD-card. If you compile a new version of the kernel you have to copy the new *uImage* on the BOOT partition. See the instructions below. h1. Copy Linux _The next step is to copy the Linux kernel and the Linux root filesystem on the BOOT and LINUX partitions. You can use_ *{_}precompiled binaries{_}* _for both or_ *{_}compile an OpenEmbedded image yourself{_}{*}_. Instructions for both options are provided below._ h2. Copy the precompiled Ã…ngström Image The precompiled Ã…ngström image consists (besided MLO and u-boot.bin from the bootloader section) of two files: The Linux kernel image (uImage) and the root file system. h3. Copy uImage Download and copy the kernel image into the root directory of the boot partition. h4. Gumstix Overo cd $HOME wget http://pixhawk.ethz.ch/wiki/_media/symlink/images/overo/uimage.bin-overo cp uimage.bin-overo* /media/BOOT/uImage h4. BeagleBoard cd $HOME wget http://www.angstrom-distribution.org/demo/beagleboard/uImage cp uImage /media/BOOT/uImage h3. Copy the Linux root file system The file is named *rootfs.tar.bz2 for the Beagle link and omap3-desktop-image-overo-*.tar.bz2 for the Overo link below. Check the main folder for the current name. * Gumstix Overo: PIXHAWK OpenEmbedded Images Download (OpenCV and libdc1394 ready) * BeagleBoard: http://www.angstrom-distribution.org/demo/beagleboard/ Download the files to a temporary directory, e.g. the Desktop or your user folder. The next step is to extract these files into the LINUX partition (NOT the boot partition). This can only be done by using Linux. If you're using Windows or MacOS, read this. h4. Gumstix Overo If you have downloaded the console image: wget http://pixhawk.ethz.ch/wiki/_media/symlink/images/overo/pixhawk-console-image-overo.tar.bz2 sudo tar xjf pixhawk-console-image-overo-*.tar.bz2 -C /media/LINUXOr the desktop image: wget http://pixhawk.ethz.ch/wiki/_media/symlink/images/overo/pixhawk-desktop-image-overo.tar.bz2 sudo tar xjf pixhawk-desktop-image-overo-*.tar.bz2 -C /media/LINUXpossibly, "pixhawk-desktop-image-overo-*.tar.bz2" has to be changed into "pixhawk-console-image-overo.tar.bz2" (just adept file name) h4. BeagleBoard sudo tar xjf *rootfs.tar.bz2 -C /media/LINUX h2. Copy custom OpenEmbedded Linux Image h3. Linux Kernel Image and u-boot bootloader Copy the kernel image and u-boot. h4. Gumstix Overo sudo cp $OE_HOME/tmp/deploy/glibc/images/overo/uImage-overo.bin /media/BOOT/uImage cp $OE_HOME/tmp/deploy/glibc/images/overo/u-boot-overo.bin /media/BOOT/u-boot.bin h4. BeagleBoard sudo cp $OE_HOME/tmp/deploy/glibc/images/beagleboard/uImage-beagleboard.bin /media/BOOT/uImage cp $OE_HOME/tmp/deploy/glibc/images/beagleboard/u-boot-beagleboard.bin /media/BOOT/u-boot.bin h3. Linux root filesystem After the kernel, the root filesystem has to be copied as well. If you are overwriting an existing installation and you don't need a 100% clean system, you can just delete all files. The command below will delete all files in /media/LINUX except the lost+found directory of the EXT3 file system. sudo rm -rf /media/LINUX/* && sudo mkdir /media/LINUX/lost+foundHowever if you want a really clean disk, you should format it, but this will take considerably longer. sudo mkfs.ext3 -L LINUX /dev/sdc2And now copy the new files. h4. Gumstix Overo The console image: sudo tar xjf $OE_HOME/tmp/deploy/glibc/images/overo/omap3-console-image-overo.tar.bz2 -C /media/LINUXThe pixhawk console image: sudo tar xjf $OE_HOME/tmp/deploy/glibc/images/overo/pixhawk-console-image-overo.tar.bz2 -C /media/LINUXOr the desktop image: sudo tar xjf $OE_HOME/tmp/deploy/glibc/images/overo/omap3-desktop-image-overo.tar.bz2 -C /media/LINUX h4. BeagleBoard The console image: sudo tar xjf $OE_HOME/tmp/deploy/glibc/images/beagleboard/omap3-console-image-beagleboard.tar.bz2 -C /media/LINUXOr the desktop image: sudo tar xjf $OE_HOME/tmp/deploy/glibc/images/beagleboard/omap3-desktop-image-overo.beagleboard.bz2 -C /media/LINUX h1. Unmount the SD/SDHC card Now unmount the drive either manually (by clicking the unmount icon on the desktop) or by shell command: sync sudo umount /media/BOOT sudo umount /media/LINUX sudo rm -r /media/BOOT sudo rm -r /media/LINUX h1. Copy bytewise from one SDHC card to another If you have modified your installation and want to clone the content of the SD card, you can do this with dd. Make sure to plug in the source card first, then the destination card. Check the file names with: dmesg | tailAnd unmount the card (with the GUI or with umount /dev/sdb). Then use dd to copy the first gigabyte from one card to the other (including partition table, etc.): sudo dd if=/dev/sdb of=/dev/sdc bs=1073741824]]> 11240324 16449626 16416863 11273065 " ## \# Set the RTC, only if a battery has been installed on the Beagleboard# # set the battery backed RTC, "hwclock \-w" ## \# Build the McStar Natively# # Enter "shutdown now". # Power off Beagleboard # Remove Ethernet Dongle # Attach a (not so) freshly EXT3 formatted USB drive to the host # Enter "cp \-R /media/sda1/McStar/app /media/sda1/." # Remove the USB host from the host and connect it to the Beagleboard # Power up the Beagleboard # Enter "root" at the Linux prompt # Enter "cd /media/sda1/app/src" # Enter "touch Makefile \*.h \*.cpp" # Enter "make clean" # Enter "make" ## \# Test the McStar App for 10 minutes, writing a new file every minute # Enter "mkdir /media/sda1/data" # Enter "cd /media/sda1/app/scripts" # Enter "./test_mcstar.sh" \\ \\ ---- h3. Notes on Beagel Board and SD Card Copy h1. Copy Linux filesystem on bootable SD card This tutorial is part of our Tutorials section. It shows how to flash an image onto an SD/SDHC card. This guide assumes that the card is correctly partitioned, as described in the Create a bootable SD/SDHC card in Ubuntu tutorial. h4. Steps in this tutorial # Mount the SD/SDHC card (if not already mounted) # Write bootloader if necessary # Write Linux kernel image # Write Linux root file system # Unmount h1. Quick Solution: Copy an already existing card If you have already one working SD image and an (absolutely similar) formatted second card, you can just copy them. WARNING Please be aware that the filesystem names (/dev/sdb1, etc.) can differ from system to system, make sure to select the right one. Copy one SD card to another: sudo dd if=/dev/sdb of=/dev/sdcThe safer alternative: Copy the SD card to harddisk and then onto another sudo dd if=/dev/sdb of=~/sd-card-copy.binNow back on the second SD card: sudo dd if=~/sd-card-copy.bin of=/dev/sdb h1. Mount SD/SDHC card Check where linux mounted the card. One way is to check this via mount . Call mount to see where the card has been mounted. Two partitions should have been mounted, one named '/media/BOOT' and the other one '/media/LINUX'. Note the device name, e.g. '/dev/sdb'. mountIf the card has not been mounted, you have two choices: h3. Automatic _Just unplug and re-plug the cardreader. It will be detected and mounted automatically._ h3. Manually If the check with mount didn't work out, use dmesg: dmesg \| tailWatch out for a line like this: [sdc] Attached SCSI removable diskWhere *sdc* could also be sdc or sdd. If it was sdb, the device name of the memory card is */dev/sdc*. sudo mkdir \-p /media/BOOT sudo mount /dev/sdc1 /media/BOOT sudo mkdir \-p /media/LINUX sudo mount /dev/sdc2 /media/LINUX h1. Copy files on the BOOT partition (MLO, u-boot.bin and uImage) _Please note that the bootloader files don't have to be rewritten every time. This applies especially when a new custom Linux system is created with_ BitBake and OpenEmbedded_. However if you work close to the hardware, e.g. on drivers, this is different.\_ h4. Overo Download MLO and uBoot from this link (commands for shell below): * PIXHAWK OpenEmbedded Images Download (OpenCV and libdc1394 ready) *IMPORTANT: Copy MLO FIRST\!*. The commands below download the two files and copy them in the right order on the boot partition. _You may have to adjust the filenames for future revisions._ cd $HOME wget [http://pixhawk.ethz.ch/wiki/_media/symlink/images/overo/mlo-overo] wget [http://pixhawk.ethz.ch/wiki/_media/symlink/images/overo/u-boot.bin-overoAnd] now copy the two files onto the boot partition (*MLO first* because of a bug in the X-loader which causes problems if MLO is not the first file written onto the boot partition). cp MLO-overo\* /media/BOOT/MLO cp u-boot.bin-overo\* /media/BOOT/u-boot.bin The Linux kernel (*uImage*) resides also on the *BOOT* partition of the SD-card. If you compile a new version of the kernel you have to copy the new *uImage* on the BOOT partition. See the instructions below. h4. BeagleBoard Download MLO and uBoot from this link (commands for shell below): * [http://www.angstrom-distribution.org/demo/beagleboard/] * Only for PIXHAWK Team (_will be made public in october_) *IMPORTANT: Copy MLO FIRST\!*. The commands below download the two files and copy them in the right order on the boot partition. _You may have to adjust the filenames for future revisions._ cd $HOME wget [http://www.angstrom-distribution.org/demo/beagleboard/MLO] wget [http://www.angstrom-distribution.org/demo/beagleboard/u-boot.binAnd] now copy the two files onto the boot partition (*MLO first* because of a bug in the X-loader which causes problems if MLO is not the first file written onto the boot partition). cp MLO /media/BOOT/MLO cp u-boot.bin /media/BOOT/u-boot.bin The Linux kernel (*uImage*) resides also on the *BOOT* partition of the SD-card. If you compile a new version of the kernel you have to copy the new *uImage* on the BOOT partition. See the instructions below. h1. Copy Linux _The next step is to copy the Linux kernel and the Linux root filesystem on the BOOT and LINUX partitions. You can use_ *{_}precompiled binaries{_}* _for both or_ *{_}compile an OpenEmbedded image yourself{_}{*}_. Instructions for both options are provided below._ h2. Copy the precompiled Ã…ngström Image The precompiled Ã…ngström image consists (besided MLO and u-boot.bin from the bootloader section) of two files: The Linux kernel image (uImage) and the root file system. h3. Copy uImage Download and copy the kernel image into the root directory of the boot partition. h4. Gumstix Overo cd $HOME wget [http://pixhawk.ethz.ch/wiki/_media/symlink/images/overo/uimage.bin-overo] cp uimage.bin-overo\* /media/BOOT/uImage h4. BeagleBoard cd $HOME wget [http://www.angstrom-distribution.org/demo/beagleboard/uImage] cp uImage /media/BOOT/uImage h3. Copy the Linux root file system The file is named *rootfs.tar.bz2 for the Beagle link and omap3-desktop-image-overo\-*.tar.bz2 for the Overo link below. Check the main folder for the current name. * Gumstix Overo: PIXHAWK OpenEmbedded Images Download (OpenCV and libdc1394 ready) * BeagleBoard: [http://www.angstrom-distribution.org/demo/beagleboard/] Download the files to a temporary directory, e.g. the Desktop or your user folder. The next step is to extract these files into the LINUX partition (NOT the boot partition). This can only be done by using Linux. If you're using Windows or MacOS, read this. h4. Gumstix Overo If you have downloaded the console image: wget [http://pixhawk.ethz.ch/wiki/_media/symlink/images/overo/pixhawk-console-image-overo.tar.bz2] sudo tar xjf pixhawk-console-image-overo-*.tar.bz2 \-C /media/LINUXOr the desktop image: wget [http://pixhawk.ethz.ch/wiki/_media/symlink/images/overo/pixhawk-desktop-image-overo.tar.bz2] sudo tar xjf pixhawk-desktop-image-overo\-*.tar.bz2* *{-}C /media/LINUXpossibly, "pixhawk-desktop-image-overo{-}*.tar.bz2" has to be changed into "pixhawk-console-image-overo.tar.bz2" (just adept file name) h4. BeagleBoard sudo tar xjf \*rootfs.tar.bz2 \-C /media/LINUX h2. Copy custom OpenEmbedded Linux Image h3. Linux Kernel Image and u-boot bootloader Copy the kernel image and u-boot. h4. Gumstix Overo sudo cp $OE_HOME/tmp/deploy/glibc/images/overo/uImage-overo.bin /media/BOOT/uImage cp $OE_HOME/tmp/deploy/glibc/images/overo/u-boot-overo.bin /media/BOOT/u-boot.bin h4. BeagleBoard sudo cp $OE_HOME/tmp/deploy/glibc/images/beagleboard/uImage-beagleboard.bin /media/BOOT/uImage cp $OE_HOME/tmp/deploy/glibc/images/beagleboard/u-boot-beagleboard.bin /media/BOOT/u-boot.bin h3. Linux root filesystem After the kernel, the root filesystem has to be copied as well. If you are overwriting an existing installation and you don't need a 100% clean system, you can just delete all files. The command below will delete all files in /media/LINUX except the lost+found directory of the EXT3 file system. sudo rm \-rf /media/LINUX/\* && sudo mkdir /media/LINUX/lost+foundHowever if you want a really clean disk, you should format it, but this will take considerably longer. sudo mkfs.ext3 \-L LINUX /dev/sdc2And now copy the new files. h4. Gumstix Overo The console image: sudo tar xjf $OE_HOME/tmp/deploy/glibc/images/overo/omap3-console-image-overo.tar.bz2 \-C /media/LINUXThe pixhawk console image: sudo tar xjf $OE_HOME/tmp/deploy/glibc/images/overo/pixhawk-console-image-overo.tar.bz2 \-C /media/LINUXOr the desktop image: sudo tar xjf $OE_HOME/tmp/deploy/glibc/images/overo/omap3-desktop-image-overo.tar.bz2 \-C /media/LINUX h4. BeagleBoard The console image: sudo tar xjf $OE_HOME/tmp/deploy/glibc/images/beagleboard/omap3-console-image-beagleboard.tar.bz2 \-C /media/LINUXOr the desktop image: sudo tar xjf $OE_HOME/tmp/deploy/glibc/images/beagleboard/omap3-desktop-image-overo.beagleboard.bz2 \-C /media/LINUX h1. Unmount the SD/SDHC card Now unmount the drive either manually (by clicking the unmount icon on the desktop) or by shell command: sync sudo umount /media/BOOT sudo umount /media/LINUX sudo rm \-r /media/BOOT sudo rm \-r /media/LINUX h1. Copy bytewise from one SDHC card to another If you have modified your installation and want to clone the content of the SD card, you can do this with dd. Make sure to plug in the source card first, then the destination card. Check the file names with: dmesg \| tailAnd unmount the card (with the GUI or with umount /dev/sdb). Then use dd to copy the first gigabyte from one card to the other (including partition table, etc.): sudo dd if=/dev/sdb of=/dev/sdc bs=1073741824]]> 11240326 11273067 " ## \# Set the RTC, only if a battery has been installed on the Beagleboard# # set the battery backed RTC, "hwclock \-w" ## \# Build the McStar Natively# # Enter "shutdown now". # Power off Beagleboard # Remove Ethernet Dongle # Attach a (not so) freshly EXT3 formatted USB drive to the host # Enter "cp \-R /media/sda1/McStar/app /media/sda1/." # Remove the USB host from the host and connect it to the Beagleboard # Power up the Beagleboard # Enter "root" at the Linux prompt # Enter "cd /media/sda1/app/src" # Enter "touch Makefile \*.h \*.cpp" # Enter "make clean" # Enter "make" ## \# Test the McStar App for 10 minutes, writing a new file every minute # Enter "mkdir /media/sda1/data" # Enter "cd /media/sda1/app/scripts" # Enter "./test_mcstar.sh" \\ \\ ---- h3. Notes on Beagel Board and SD Card Copy h1. Copy Linux filesystem on bootable SD card This tutorial is part of our Tutorials section. It shows how to flash an image onto an SD/SDHC card. This guide assumes that the card is correctly partitioned, as described in the Create a bootable SD/SDHC card in Ubuntu tutorial. h4. Steps in this tutorial # Mount the SD/SDHC card (if not already mounted) # Write bootloader if necessary # Write Linux kernel image # Write Linux root file system # Unmount h1. Quick Solution: Copy an already existing card If you have already one working SD image and an (absolutely similar) formatted second card, you can just copy them. WARNING Please be aware that the filesystem names (/dev/sdb1, etc.) can differ from system to system, make sure to select the right one. Copy one SD card to another: sudo dd if=/dev/sdb of=/dev/sdcThe safer alternative: Copy the SD card to harddisk and then onto another sudo dd if=/dev/sdb of=~/sd-card-copy.binNow back on the second SD card: sudo dd if=~/sd-card-copy.bin of=/dev/sdb h1. Mount SD/SDHC card Check where linux mounted the card. One way is to check this via mount . Call mount to see where the card has been mounted. Two partitions should have been mounted, one named '/media/BOOT' and the other one '/media/LINUX'. Note the device name, e.g. '/dev/sdb'. mountIf the card has not been mounted, you have two choices: h3. Automatic _Just unplug and re-plug the cardreader. It will be detected and mounted automatically._ h3. Manually If the check with mount didn't work out, use dmesg: dmesg \| tailWatch out for a line like this: [sdc] Attached SCSI removable diskWhere *sdc* could also be sdc or sdd. If it was sdb, the device name of the memory card is */dev/sdc*. sudo mkdir \-p /media/BOOT sudo mount /dev/sdc1 /media/BOOT sudo mkdir \-p /media/LINUX sudo mount /dev/sdc2 /media/LINUX h1. Copy files on the BOOT partition (MLO, u-boot.bin and uImage) _Please note that the bootloader files don't have to be rewritten every time. This applies especially when a new custom Linux system is created with_ BitBake and OpenEmbedded_. However if you work close to the hardware, e.g. on drivers, this is different.\_ h4. Overo Download MLO and uBoot from this link (commands for shell below): * PIXHAWK OpenEmbedded Images Download (OpenCV and libdc1394 ready) *IMPORTANT: Copy MLO FIRST\!*. The commands below download the two files and copy them in the right order on the boot partition. _You may have to adjust the filenames for future revisions._ cd $HOME wget [http://pixhawk.ethz.ch/wiki/_media/symlink/images/overo/mlo-overo] wget [http://pixhawk.ethz.ch/wiki/_media/symlink/images/overo/u-boot.bin-overoAnd] now copy the two files onto the boot partition (*MLO first* because of a bug in the X-loader which causes problems if MLO is not the first file written onto the boot partition). cp MLO-overo\* /media/BOOT/MLO cp u-boot.bin-overo\* /media/BOOT/u-boot.bin The Linux kernel (*uImage*) resides also on the *BOOT* partition of the SD-card. If you compile a new version of the kernel you have to copy the new *uImage* on the BOOT partition. See the instructions below. h4. BeagleBoard Download MLO and uBoot from this link (commands for shell below): * [http://www.angstrom-distribution.org/demo/beagleboard/] * Only for PIXHAWK Team (_will be made public in october_) *IMPORTANT: Copy MLO FIRST\!*. The commands below download the two files and copy them in the right order on the boot partition. _You may have to adjust the filenames for future revisions._ cd $HOME wget [http://www.angstrom-distribution.org/demo/beagleboard/MLO] wget [http://www.angstrom-distribution.org/demo/beagleboard/u-boot.binAnd] now copy the two files onto the boot partition (*MLO first* because of a bug in the X-loader which causes problems if MLO is not the first file written onto the boot partition). cp MLO /media/BOOT/MLO cp u-boot.bin /media/BOOT/u-boot.bin The Linux kernel (*uImage*) resides also on the *BOOT* partition of the SD-card. If you compile a new version of the kernel you have to copy the new *uImage* on the BOOT partition. See the instructions below. h1. Copy Linux _The next step is to copy the Linux kernel and the Linux root filesystem on the BOOT and LINUX partitions. You can use_ *{_}precompiled binaries{_}* _for both or_ *{_}compile an OpenEmbedded image yourself{_}{*}_. Instructions for both options are provided below._ h2. Copy the precompiled Ã…ngström Image The precompiled Ã…ngström image consists (besided MLO and u-boot.bin from the bootloader section) of two files: The Linux kernel image (uImage) and the root file system. h3. Copy uImage Download and copy the kernel image into the root directory of the boot partition. h4. Gumstix Overo cd $HOME wget [http://pixhawk.ethz.ch/wiki/_media/symlink/images/overo/uimage.bin-overo] cp uimage.bin-overo\* /media/BOOT/uImage h4. BeagleBoard cd $HOME wget [http://www.angstrom-distribution.org/demo/beagleboard/uImage] cp uImage /media/BOOT/uImage h3. Copy the Linux root file system The file is named *rootfs.tar.bz2 for the Beagle link and omap3-desktop-image-overo\-*.tar.bz2 for the Overo link below. Check the main folder for the current name. * Gumstix Overo: PIXHAWK OpenEmbedded Images Download (OpenCV and libdc1394 ready) * BeagleBoard: [http://www.angstrom-distribution.org/demo/beagleboard/] Download the files to a temporary directory, e.g. the Desktop or your user folder. The next step is to extract these files into the LINUX partition (NOT the boot partition). This can only be done by using Linux. If you're using Windows or MacOS, read this. h4. Gumstix Overo If you have downloaded the console image: wget [http://pixhawk.ethz.ch/wiki/_media/symlink/images/overo/pixhawk-console-image-overo.tar.bz2] sudo tar xjf pixhawk-console-image-overo-*.tar.bz2 \-C /media/LINUXOr the desktop image: wget [http://pixhawk.ethz.ch/wiki/_media/symlink/images/overo/pixhawk-desktop-image-overo.tar.bz2] sudo tar xjf pixhawk-desktop-image-overo\-*.tar.bz2* *{-}C /media/LINUXpossibly, "pixhawk-desktop-image-overo{-}*.tar.bz2" has to be changed into "pixhawk-console-image-overo.tar.bz2" (just adept file name) h4. BeagleBoard sudo tar xjf \*rootfs.tar.bz2 \-C /media/LINUX h2. Copy custom OpenEmbedded Linux Image h3. Linux Kernel Image and u-boot bootloader Copy the kernel image and u-boot. h4. Gumstix Overo sudo cp $OE_HOME/tmp/deploy/glibc/images/overo/uImage-overo.bin /media/BOOT/uImage cp $OE_HOME/tmp/deploy/glibc/images/overo/u-boot-overo.bin /media/BOOT/u-boot.bin h4. BeagleBoard sudo cp $OE_HOME/tmp/deploy/glibc/images/beagleboard/uImage-beagleboard.bin /media/BOOT/uImage cp $OE_HOME/tmp/deploy/glibc/images/beagleboard/u-boot-beagleboard.bin /media/BOOT/u-boot.bin h3. Linux root filesystem After the kernel, the root filesystem has to be copied as well. If you are overwriting an existing installation and you don't need a 100% clean system, you can just delete all files. The command below will delete all files in /media/LINUX except the lost+found directory of the EXT3 file system. sudo rm \-rf /media/LINUX/\* && sudo mkdir /media/LINUX/lost+foundHowever if you want a really clean disk, you should format it, but this will take considerably longer. sudo mkfs.ext3 \-L LINUX /dev/sdc2And now copy the new files. h4. Gumstix Overo The console image: sudo tar xjf $OE_HOME/tmp/deploy/glibc/images/overo/omap3-console-image-overo.tar.bz2 \-C /media/LINUXThe pixhawk console image: sudo tar xjf $OE_HOME/tmp/deploy/glibc/images/overo/pixhawk-console-image-overo.tar.bz2 \-C /media/LINUXOr the desktop image: sudo tar xjf $OE_HOME/tmp/deploy/glibc/images/overo/omap3-desktop-image-overo.tar.bz2 \-C /media/LINUX h4. BeagleBoard The console image: sudo tar xjf $OE_HOME/tmp/deploy/glibc/images/beagleboard/omap3-console-image-beagleboard.tar.bz2 \-C /media/LINUXOr the desktop image: sudo tar xjf $OE_HOME/tmp/deploy/glibc/images/beagleboard/omap3-desktop-image-overo.beagleboard.bz2 \-C /media/LINUX h1. Unmount the SD/SDHC card Now unmount the drive either manually (by clicking the unmount icon on the desktop) or by shell command: sync sudo umount /media/BOOT sudo umount /media/LINUX sudo rm \-r /media/BOOT sudo rm \-r /media/LINUX h1. Copy bytewise from one SDHC card to another If you have modified your installation and want to clone the content of the SD card, you can do this with dd. Make sure to plug in the source card first, then the destination card. Check the file names with: dmesg \| tailAnd unmount the card (with the GUI or with umount /dev/sdb). Then use dd to copy the first gigabyte from one card to the other (including partition table, etc.): sudo dd if=/dev/sdb of=/dev/sdc bs=1073741824]]> 11240328 16449630 16416867 19074281 19041600 11273070 " ## \# Set the RTC, only if a battery has been installed on the Beagleboard# # set the battery backed RTC, "hwclock \-w" ## \# Build the McStar Natively# # Enter "shutdown now". # Power off Beagleboard # Remove Ethernet Dongle from the Beagleboard {warning:title=Copy McStar app from host to harddrive}{warning} # Attach a freshly EXT3 formatted USB drive to the host # Enter "cp \-R \~/McStar/app /media/sda1/." # Unmount USB drive # Remove the USB host from the host and connect it to the Beagleboard # Power up the Beagleboard # Enter "root" at the Linux prompt # Enter "cd /media/sda1/app/src" # Enter "touch Makefile \*.h \*.cpp" # Enter "make clean" # Enter "make" ## \# Test the McStar App for 10 minutes, writing a new file every minute # Enter "mkdir /media/sda1/data" # Enter "cd /media/sda1/app/scripts" # Enter "./test_mcstar.sh" \\ \\ ---- h3. Notes on Beagel Board and SD Card Copy h1. Copy Linux filesystem on bootable SD card This tutorial is part of our Tutorials section. It shows how to flash an image onto an SD/SDHC card. This guide assumes that the card is correctly partitioned, as described in the Create a bootable SD/SDHC card in Ubuntu tutorial. h4. Steps in this tutorial # Mount the SD/SDHC card (if not already mounted) # Write bootloader if necessary # Write Linux kernel image # Write Linux root file system # Unmount h1. Quick Solution: Copy an already existing card If you have already one working SD image and an (absolutely similar) formatted second card, you can just copy them. WARNING Please be aware that the filesystem names (/dev/sdb1, etc.) can differ from system to system, make sure to select the right one. Copy one SD card to another: sudo dd if=/dev/sdb of=/dev/sdcThe safer alternative: Copy the SD card to harddisk and then onto another sudo dd if=/dev/sdb of=~/sd-card-copy.binNow back on the second SD card: sudo dd if=~/sd-card-copy.bin of=/dev/sdb h1. Mount SD/SDHC card Check where linux mounted the card. One way is to check this via mount . Call mount to see where the card has been mounted. Two partitions should have been mounted, one named '/media/BOOT' and the other one '/media/LINUX'. Note the device name, e.g. '/dev/sdb'. mountIf the card has not been mounted, you have two choices: h3. Automatic _Just unplug and re-plug the cardreader. It will be detected and mounted automatically._ h3. Manually If the check with mount didn't work out, use dmesg: dmesg \| tailWatch out for a line like this: [sdc] Attached SCSI removable diskWhere *sdc* could also be sdc or sdd. If it was sdb, the device name of the memory card is */dev/sdc*. sudo mkdir \-p /media/BOOT sudo mount /dev/sdc1 /media/BOOT sudo mkdir \-p /media/LINUX sudo mount /dev/sdc2 /media/LINUX h1. Copy files on the BOOT partition (MLO, u-boot.bin and uImage) _Please note that the bootloader files don't have to be rewritten every time. This applies especially when a new custom Linux system is created with_ BitBake and OpenEmbedded_. However if you work close to the hardware, e.g. on drivers, this is different.\_ h4. Overo Download MLO and uBoot from this link (commands for shell below): * PIXHAWK OpenEmbedded Images Download (OpenCV and libdc1394 ready) *IMPORTANT: Copy MLO FIRST\!*. The commands below download the two files and copy them in the right order on the boot partition. _You may have to adjust the filenames for future revisions._ cd $HOME wget [http://pixhawk.ethz.ch/wiki/_media/symlink/images/overo/mlo-overo] wget [http://pixhawk.ethz.ch/wiki/_media/symlink/images/overo/u-boot.bin-overoAnd] now copy the two files onto the boot partition (*MLO first* because of a bug in the X-loader which causes problems if MLO is not the first file written onto the boot partition). cp MLO-overo\* /media/BOOT/MLO cp u-boot.bin-overo\* /media/BOOT/u-boot.bin The Linux kernel (*uImage*) resides also on the *BOOT* partition of the SD-card. If you compile a new version of the kernel you have to copy the new *uImage* on the BOOT partition. See the instructions below. h4. BeagleBoard Download MLO and uBoot from this link (commands for shell below): * [http://www.angstrom-distribution.org/demo/beagleboard/] * Only for PIXHAWK Team (_will be made public in october_) *IMPORTANT: Copy MLO FIRST\!*. The commands below download the two files and copy them in the right order on the boot partition. _You may have to adjust the filenames for future revisions._ cd $HOME wget [http://www.angstrom-distribution.org/demo/beagleboard/MLO] wget [http://www.angstrom-distribution.org/demo/beagleboard/u-boot.binAnd] now copy the two files onto the boot partition (*MLO first* because of a bug in the X-loader which causes problems if MLO is not the first file written onto the boot partition). cp MLO /media/BOOT/MLO cp u-boot.bin /media/BOOT/u-boot.bin The Linux kernel (*uImage*) resides also on the *BOOT* partition of the SD-card. If you compile a new version of the kernel you have to copy the new *uImage* on the BOOT partition. See the instructions below. h1. Copy Linux _The next step is to copy the Linux kernel and the Linux root filesystem on the BOOT and LINUX partitions. You can use_ *{_}precompiled binaries{_}* _for both or_ *{_}compile an OpenEmbedded image yourself{_}{*}_. Instructions for both options are provided below._ h2. Copy the precompiled Ã…ngström Image The precompiled Ã…ngström image consists (besided MLO and u-boot.bin from the bootloader section) of two files: The Linux kernel image (uImage) and the root file system. h3. Copy uImage Download and copy the kernel image into the root directory of the boot partition. h4. Gumstix Overo cd $HOME wget [http://pixhawk.ethz.ch/wiki/_media/symlink/images/overo/uimage.bin-overo] cp uimage.bin-overo\* /media/BOOT/uImage h4. BeagleBoard cd $HOME wget [http://www.angstrom-distribution.org/demo/beagleboard/uImage] cp uImage /media/BOOT/uImage h3. Copy the Linux root file system The file is named *rootfs.tar.bz2 for the Beagle link and omap3-desktop-image-overo\-*.tar.bz2 for the Overo link below. Check the main folder for the current name. * Gumstix Overo: PIXHAWK OpenEmbedded Images Download (OpenCV and libdc1394 ready) * BeagleBoard: [http://www.angstrom-distribution.org/demo/beagleboard/] Download the files to a temporary directory, e.g. the Desktop or your user folder. The next step is to extract these files into the LINUX partition (NOT the boot partition). This can only be done by using Linux. If you're using Windows or MacOS, read this. h4. Gumstix Overo If you have downloaded the console image: wget [http://pixhawk.ethz.ch/wiki/_media/symlink/images/overo/pixhawk-console-image-overo.tar.bz2] sudo tar xjf pixhawk-console-image-overo-*.tar.bz2 \-C /media/LINUXOr the desktop image: wget [http://pixhawk.ethz.ch/wiki/_media/symlink/images/overo/pixhawk-desktop-image-overo.tar.bz2] sudo tar xjf pixhawk-desktop-image-overo\-*.tar.bz2* *{-}C /media/LINUXpossibly, "pixhawk-desktop-image-overo{-}*.tar.bz2" has to be changed into "pixhawk-console-image-overo.tar.bz2" (just adept file name) h4. BeagleBoard sudo tar xjf \*rootfs.tar.bz2 \-C /media/LINUX h2. Copy custom OpenEmbedded Linux Image h3. Linux Kernel Image and u-boot bootloader Copy the kernel image and u-boot. h4. Gumstix Overo sudo cp $OE_HOME/tmp/deploy/glibc/images/overo/uImage-overo.bin /media/BOOT/uImage cp $OE_HOME/tmp/deploy/glibc/images/overo/u-boot-overo.bin /media/BOOT/u-boot.bin h4. BeagleBoard sudo cp $OE_HOME/tmp/deploy/glibc/images/beagleboard/uImage-beagleboard.bin /media/BOOT/uImage cp $OE_HOME/tmp/deploy/glibc/images/beagleboard/u-boot-beagleboard.bin /media/BOOT/u-boot.bin h3. Linux root filesystem After the kernel, the root filesystem has to be copied as well. If you are overwriting an existing installation and you don't need a 100% clean system, you can just delete all files. The command below will delete all files in /media/LINUX except the lost+found directory of the EXT3 file system. sudo rm \-rf /media/LINUX/\* && sudo mkdir /media/LINUX/lost+foundHowever if you want a really clean disk, you should format it, but this will take considerably longer. sudo mkfs.ext3 \-L LINUX /dev/sdc2And now copy the new files. h4. Gumstix Overo The console image: sudo tar xjf $OE_HOME/tmp/deploy/glibc/images/overo/omap3-console-image-overo.tar.bz2 \-C /media/LINUXThe pixhawk console image: sudo tar xjf $OE_HOME/tmp/deploy/glibc/images/overo/pixhawk-console-image-overo.tar.bz2 \-C /media/LINUXOr the desktop image: sudo tar xjf $OE_HOME/tmp/deploy/glibc/images/overo/omap3-desktop-image-overo.tar.bz2 \-C /media/LINUX h4. BeagleBoard The console image: sudo tar xjf $OE_HOME/tmp/deploy/glibc/images/beagleboard/omap3-console-image-beagleboard.tar.bz2 \-C /media/LINUXOr the desktop image: sudo tar xjf $OE_HOME/tmp/deploy/glibc/images/beagleboard/omap3-desktop-image-overo.beagleboard.bz2 \-C /media/LINUX h1. Unmount the SD/SDHC card Now unmount the drive either manually (by clicking the unmount icon on the desktop) or by shell command: sync sudo umount /media/BOOT sudo umount /media/LINUX sudo rm \-r /media/BOOT sudo rm \-r /media/LINUX h1. Copy bytewise from one SDHC card to another If you have modified your installation and want to clone the content of the SD card, you can do this with dd. Make sure to plug in the source card first, then the destination card. Check the file names with: dmesg \| tailAnd unmount the card (with the GUI or with umount /dev/sdb). Then use dd to copy the first gigabyte from one card to the other (including partition table, etc.): sudo dd if=/dev/sdb of=/dev/sdc bs=1073741824]]> 11240331 11273069 " ## \# Set the RTC, only if a battery has been installed on the Beagleboard# # set the battery backed RTC, "hwclock \-w" ## \# Build the McStar Natively# # Enter "shutdown now". # Power off Beagleboard # Remove Ethernet Dongle # Attach a (not so) freshly EXT3 formatted USB drive to the host # Enter "cp \-R /media/sda1/McStar/app /media/sda1/." # Remove the USB host from the host and connect it to the Beagleboard # Power up the Beagleboard # Enter "root" at the Linux prompt # Enter "cd /media/sda1/app/src" # Enter "touch Makefile \*.h \*.cpp" # Enter "make clean" # Enter "make" ## \# Test the McStar App for 10 minutes, writing a new file every minute # Enter "mkdir /media/sda1/data" # Enter "cd /media/sda1/app/scripts" # Enter "./test_mcstar.sh" \\ \\ ---- h3. Notes on Beagel Board and SD Card Copy h1. Copy Linux filesystem on bootable SD card This tutorial is part of our Tutorials section. It shows how to flash an image onto an SD/SDHC card. This guide assumes that the card is correctly partitioned, as described in the Create a bootable SD/SDHC card in Ubuntu tutorial. h4. Steps in this tutorial # Mount the SD/SDHC card (if not already mounted) # Write bootloader if necessary # Write Linux kernel image # Write Linux root file system # Unmount h1. Quick Solution: Copy an already existing card If you have already one working SD image and an (absolutely similar) formatted second card, you can just copy them. WARNING Please be aware that the filesystem names (/dev/sdb1, etc.) can differ from system to system, make sure to select the right one. Copy one SD card to another: sudo dd if=/dev/sdb of=/dev/sdcThe safer alternative: Copy the SD card to harddisk and then onto another sudo dd if=/dev/sdb of=~/sd-card-copy.binNow back on the second SD card: sudo dd if=~/sd-card-copy.bin of=/dev/sdb h1. Mount SD/SDHC card Check where linux mounted the card. One way is to check this via mount . Call mount to see where the card has been mounted. Two partitions should have been mounted, one named '/media/BOOT' and the other one '/media/LINUX'. Note the device name, e.g. '/dev/sdb'. mountIf the card has not been mounted, you have two choices: h3. Automatic _Just unplug and re-plug the cardreader. It will be detected and mounted automatically._ h3. Manually If the check with mount didn't work out, use dmesg: dmesg \| tailWatch out for a line like this: [sdc] Attached SCSI removable diskWhere *sdc* could also be sdc or sdd. If it was sdb, the device name of the memory card is */dev/sdc*. sudo mkdir \-p /media/BOOT sudo mount /dev/sdc1 /media/BOOT sudo mkdir \-p /media/LINUX sudo mount /dev/sdc2 /media/LINUX h1. Copy files on the BOOT partition (MLO, u-boot.bin and uImage) _Please note that the bootloader files don't have to be rewritten every time. This applies especially when a new custom Linux system is created with_ BitBake and OpenEmbedded_. However if you work close to the hardware, e.g. on drivers, this is different.\_ h4. Overo Download MLO and uBoot from this link (commands for shell below): * PIXHAWK OpenEmbedded Images Download (OpenCV and libdc1394 ready) *IMPORTANT: Copy MLO FIRST\!*. The commands below download the two files and copy them in the right order on the boot partition. _You may have to adjust the filenames for future revisions._ cd $HOME wget [http://pixhawk.ethz.ch/wiki/_media/symlink/images/overo/mlo-overo] wget [http://pixhawk.ethz.ch/wiki/_media/symlink/images/overo/u-boot.bin-overoAnd] now copy the two files onto the boot partition (*MLO first* because of a bug in the X-loader which causes problems if MLO is not the first file written onto the boot partition). cp MLO-overo\* /media/BOOT/MLO cp u-boot.bin-overo\* /media/BOOT/u-boot.bin The Linux kernel (*uImage*) resides also on the *BOOT* partition of the SD-card. If you compile a new version of the kernel you have to copy the new *uImage* on the BOOT partition. See the instructions below. h4. BeagleBoard Download MLO and uBoot from this link (commands for shell below): * [http://www.angstrom-distribution.org/demo/beagleboard/] * Only for PIXHAWK Team (_will be made public in october_) *IMPORTANT: Copy MLO FIRST\!*. The commands below download the two files and copy them in the right order on the boot partition. _You may have to adjust the filenames for future revisions._ cd $HOME wget [http://www.angstrom-distribution.org/demo/beagleboard/MLO] wget [http://www.angstrom-distribution.org/demo/beagleboard/u-boot.binAnd] now copy the two files onto the boot partition (*MLO first* because of a bug in the X-loader which causes problems if MLO is not the first file written onto the boot partition). cp MLO /media/BOOT/MLO cp u-boot.bin /media/BOOT/u-boot.bin The Linux kernel (*uImage*) resides also on the *BOOT* partition of the SD-card. If you compile a new version of the kernel you have to copy the new *uImage* on the BOOT partition. See the instructions below. h1. Copy Linux _The next step is to copy the Linux kernel and the Linux root filesystem on the BOOT and LINUX partitions. You can use_ *{_}precompiled binaries{_}* _for both or_ *{_}compile an OpenEmbedded image yourself{_}{*}_. Instructions for both options are provided below._ h2. Copy the precompiled Ã…ngström Image The precompiled Ã…ngström image consists (besided MLO and u-boot.bin from the bootloader section) of two files: The Linux kernel image (uImage) and the root file system. h3. Copy uImage Download and copy the kernel image into the root directory of the boot partition. h4. Gumstix Overo cd $HOME wget [http://pixhawk.ethz.ch/wiki/_media/symlink/images/overo/uimage.bin-overo] cp uimage.bin-overo\* /media/BOOT/uImage h4. BeagleBoard cd $HOME wget [http://www.angstrom-distribution.org/demo/beagleboard/uImage] cp uImage /media/BOOT/uImage h3. Copy the Linux root file system The file is named *rootfs.tar.bz2 for the Beagle link and omap3-desktop-image-overo\-*.tar.bz2 for the Overo link below. Check the main folder for the current name. * Gumstix Overo: PIXHAWK OpenEmbedded Images Download (OpenCV and libdc1394 ready) * BeagleBoard: [http://www.angstrom-distribution.org/demo/beagleboard/] Download the files to a temporary directory, e.g. the Desktop or your user folder. The next step is to extract these files into the LINUX partition (NOT the boot partition). This can only be done by using Linux. If you're using Windows or MacOS, read this. h4. Gumstix Overo If you have downloaded the console image: wget [http://pixhawk.ethz.ch/wiki/_media/symlink/images/overo/pixhawk-console-image-overo.tar.bz2] sudo tar xjf pixhawk-console-image-overo-*.tar.bz2 \-C /media/LINUXOr the desktop image: wget [http://pixhawk.ethz.ch/wiki/_media/symlink/images/overo/pixhawk-desktop-image-overo.tar.bz2] sudo tar xjf pixhawk-desktop-image-overo\-*.tar.bz2* *{-}C /media/LINUXpossibly, "pixhawk-desktop-image-overo{-}*.tar.bz2" has to be changed into "pixhawk-console-image-overo.tar.bz2" (just adept file name) h4. BeagleBoard sudo tar xjf \*rootfs.tar.bz2 \-C /media/LINUX h2. Copy custom OpenEmbedded Linux Image h3. Linux Kernel Image and u-boot bootloader Copy the kernel image and u-boot. h4. Gumstix Overo sudo cp $OE_HOME/tmp/deploy/glibc/images/overo/uImage-overo.bin /media/BOOT/uImage cp $OE_HOME/tmp/deploy/glibc/images/overo/u-boot-overo.bin /media/BOOT/u-boot.bin h4. BeagleBoard sudo cp $OE_HOME/tmp/deploy/glibc/images/beagleboard/uImage-beagleboard.bin /media/BOOT/uImage cp $OE_HOME/tmp/deploy/glibc/images/beagleboard/u-boot-beagleboard.bin /media/BOOT/u-boot.bin h3. Linux root filesystem After the kernel, the root filesystem has to be copied as well. If you are overwriting an existing installation and you don't need a 100% clean system, you can just delete all files. The command below will delete all files in /media/LINUX except the lost+found directory of the EXT3 file system. sudo rm \-rf /media/LINUX/\* && sudo mkdir /media/LINUX/lost+foundHowever if you want a really clean disk, you should format it, but this will take considerably longer. sudo mkfs.ext3 \-L LINUX /dev/sdc2And now copy the new files. h4. Gumstix Overo The console image: sudo tar xjf $OE_HOME/tmp/deploy/glibc/images/overo/omap3-console-image-overo.tar.bz2 \-C /media/LINUXThe pixhawk console image: sudo tar xjf $OE_HOME/tmp/deploy/glibc/images/overo/pixhawk-console-image-overo.tar.bz2 \-C /media/LINUXOr the desktop image: sudo tar xjf $OE_HOME/tmp/deploy/glibc/images/overo/omap3-desktop-image-overo.tar.bz2 \-C /media/LINUX h4. BeagleBoard The console image: sudo tar xjf $OE_HOME/tmp/deploy/glibc/images/beagleboard/omap3-console-image-beagleboard.tar.bz2 \-C /media/LINUXOr the desktop image: sudo tar xjf $OE_HOME/tmp/deploy/glibc/images/beagleboard/omap3-desktop-image-overo.beagleboard.bz2 \-C /media/LINUX h1. Unmount the SD/SDHC card Now unmount the drive either manually (by clicking the unmount icon on the desktop) or by shell command: sync sudo umount /media/BOOT sudo umount /media/LINUX sudo rm \-r /media/BOOT sudo rm \-r /media/LINUX h1. Copy bytewise from one SDHC card to another If you have modified your installation and want to clone the content of the SD card, you can do this with dd. Make sure to plug in the source card first, then the destination card. Check the file names with: dmesg \| tailAnd unmount the card (with the GUI or with umount /dev/sdb). Then use dd to copy the first gigabyte from one card to the other (including partition table, etc.): sudo dd if=/dev/sdb of=/dev/sdc bs=1073741824]]> 11240330 10388618 10355892 10388614 10355888 11273081 11240342 8388612 Backup Database... ## Select Database-complete ## Click on Add... under Destination ## I typed in a file location of \\tempest\tempbox\kgomes\backups\crowd\db_backup as the file to backup to. ## I then created a new tar.gz file for the /opt/atlassian-crowd-1.5.1 installation and put in the same backup location on tempest. ## I then created a new tar.gz file for the crowd home directory /data/crowd and put in same tempest location # I copied the jtds-1.2.jar from /opt/atlassian-crowd-1.5.1/crowd-webapp/WEB-INF/lib to the same directory in the new installation # I then edited the /opt/atlassian-crowd-1.6/crowd-webapp/WEB-INF/classes/crowd-init.properties and pointed the crowd home directory to /data/crowd # I then copied the updated crowd client jar (/opt/atlassian-crowd-1.6/client/crowd-integrations-client-1.6.jar) to /opt/confluence/confluence/WEB-INF/lib and to /opt/jira/atlassian-jira/WEB-INF/lib (I removed the old ones too IMPORTANT!) # I downloaded the recommended crowd-ehcache.xml file from the instructions listed above and copied to the /opt/confluence/confluence/WEB-INF/classes and /opt/jira/atlassian-jira/WEB-INF/classes directories # Lastly I changed the /opt/crowd symbolic link to point to the new crowd installation, shut down confluence, jira, and crowd and restarted crowd. ]]> 8355844 11273083 " ## \# Set the RTC, only if a battery has been installed on the Beagleboard# # set the battery backed RTC, "hwclock \-w" ## \# Build the McStar Natively# # Enter "shutdown now". # Power off Beagleboard # Remove Ethernet Dongle from the Beagleboard {warning:title=Copy McStar app from host to harddrive}{warning} # Attach a freshly EXT3 formatted USB drive to the host # Enter "cp \-R \~/McStar/app /media/sda1/." # Unmount USB drive # Remove the USB host from the host and connect it to the Beagleboard # Power up the Beagleboard # Enter "root" at the Linux prompt # Enter "cd /media/sda1/app/src" # Enter "touch Makefile \*.h \*.cpp" # Enter "make clean" # Enter "make" ## \# Test the McStar App for 10 minutes, writing a new file every minute # Enter "mkdir /media/sda1/data" # Enter "cd /media/sda1/app/scripts" # Enter "./test_mcstar.sh" \\ \\ ---- h3. Notes on Beagel Board and SD Card Copy h1. Copy Linux filesystem on bootable SD card This tutorial is part of our Tutorials section. It shows how to flash an image onto an SD/SDHC card. This guide assumes that the card is correctly partitioned, as described in the Create a bootable SD/SDHC card in Ubuntu tutorial. h4. Steps in this tutorial # Mount the SD/SDHC card (if not already mounted) # Write bootloader if necessary # Write Linux kernel image # Write Linux root file system # Unmount h1. Quick Solution: Copy an already existing card If you have already one working SD image and an (absolutely similar) formatted second card, you can just copy them. WARNING Please be aware that the filesystem names (/dev/sdb1, etc.) can differ from system to system, make sure to select the right one. Copy one SD card to another: sudo dd if=/dev/sdb of=/dev/sdcThe safer alternative: Copy the SD card to harddisk and then onto another sudo dd if=/dev/sdb of=~/sd-card-copy.binNow back on the second SD card: sudo dd if=~/sd-card-copy.bin of=/dev/sdb h1. Mount SD/SDHC card Check where linux mounted the card. One way is to check this via mount . Call mount to see where the card has been mounted. Two partitions should have been mounted, one named '/media/BOOT' and the other one '/media/LINUX'. Note the device name, e.g. '/dev/sdb'. mountIf the card has not been mounted, you have two choices: h3. Automatic _Just unplug and re-plug the cardreader. It will be detected and mounted automatically._ h3. Manually If the check with mount didn't work out, use dmesg: dmesg \| tailWatch out for a line like this: [sdc] Attached SCSI removable diskWhere *sdc* could also be sdc or sdd. If it was sdb, the device name of the memory card is */dev/sdc*. sudo mkdir \-p /media/BOOT sudo mount /dev/sdc1 /media/BOOT sudo mkdir \-p /media/LINUX sudo mount /dev/sdc2 /media/LINUX h1. Copy files on the BOOT partition (MLO, u-boot.bin and uImage) _Please note that the bootloader files don't have to be rewritten every time. This applies especially when a new custom Linux system is created with_ BitBake and OpenEmbedded_. However if you work close to the hardware, e.g. on drivers, this is different.\_ h4. Overo Download MLO and uBoot from this link (commands for shell below): * PIXHAWK OpenEmbedded Images Download (OpenCV and libdc1394 ready) *IMPORTANT: Copy MLO FIRST\!*. The commands below download the two files and copy them in the right order on the boot partition. _You may have to adjust the filenames for future revisions._ cd $HOME wget [http://pixhawk.ethz.ch/wiki/_media/symlink/images/overo/mlo-overo] wget [http://pixhawk.ethz.ch/wiki/_media/symlink/images/overo/u-boot.bin-overoAnd] now copy the two files onto the boot partition (*MLO first* because of a bug in the X-loader which causes problems if MLO is not the first file written onto the boot partition). cp MLO-overo\* /media/BOOT/MLO cp u-boot.bin-overo\* /media/BOOT/u-boot.bin The Linux kernel (*uImage*) resides also on the *BOOT* partition of the SD-card. If you compile a new version of the kernel you have to copy the new *uImage* on the BOOT partition. See the instructions below. h4. BeagleBoard Download MLO and uBoot from this link (commands for shell below): * [http://www.angstrom-distribution.org/demo/beagleboard/] * Only for PIXHAWK Team (_will be made public in october_) *IMPORTANT: Copy MLO FIRST\!*. The commands below download the two files and copy them in the right order on the boot partition. _You may have to adjust the filenames for future revisions._ cd $HOME wget [http://www.angstrom-distribution.org/demo/beagleboard/MLO] wget [http://www.angstrom-distribution.org/demo/beagleboard/u-boot.binAnd] now copy the two files onto the boot partition (*MLO first* because of a bug in the X-loader which causes problems if MLO is not the first file written onto the boot partition). cp MLO /media/BOOT/MLO cp u-boot.bin /media/BOOT/u-boot.bin The Linux kernel (*uImage*) resides also on the *BOOT* partition of the SD-card. If you compile a new version of the kernel you have to copy the new *uImage* on the BOOT partition. See the instructions below. h1. Copy Linux _The next step is to copy the Linux kernel and the Linux root filesystem on the BOOT and LINUX partitions. You can use_ *{_}precompiled binaries{_}* _for both or_ *{_}compile an OpenEmbedded image yourself{_}{*}_. Instructions for both options are provided below._ h2. Copy the precompiled Ã…ngström Image The precompiled Ã…ngström image consists (besided MLO and u-boot.bin from the bootloader section) of two files: The Linux kernel image (uImage) and the root file system. h3. Copy uImage Download and copy the kernel image into the root directory of the boot partition. h4. Gumstix Overo cd $HOME wget [http://pixhawk.ethz.ch/wiki/_media/symlink/images/overo/uimage.bin-overo] cp uimage.bin-overo\* /media/BOOT/uImage h4. BeagleBoard cd $HOME wget [http://www.angstrom-distribution.org/demo/beagleboard/uImage] cp uImage /media/BOOT/uImage h3. Copy the Linux root file system The file is named *rootfs.tar.bz2 for the Beagle link and omap3-desktop-image-overo\-*.tar.bz2 for the Overo link below. Check the main folder for the current name. * Gumstix Overo: PIXHAWK OpenEmbedded Images Download (OpenCV and libdc1394 ready) * BeagleBoard: [http://www.angstrom-distribution.org/demo/beagleboard/] Download the files to a temporary directory, e.g. the Desktop or your user folder. The next step is to extract these files into the LINUX partition (NOT the boot partition). This can only be done by using Linux. If you're using Windows or MacOS, read this. h4. Gumstix Overo If you have downloaded the console image: wget [http://pixhawk.ethz.ch/wiki/_media/symlink/images/overo/pixhawk-console-image-overo.tar.bz2] sudo tar xjf pixhawk-console-image-overo-*.tar.bz2 \-C /media/LINUXOr the desktop image: wget [http://pixhawk.ethz.ch/wiki/_media/symlink/images/overo/pixhawk-desktop-image-overo.tar.bz2] sudo tar xjf pixhawk-desktop-image-overo\-*.tar.bz2* *{-}C /media/LINUXpossibly, "pixhawk-desktop-image-overo{-}*.tar.bz2" has to be changed into "pixhawk-console-image-overo.tar.bz2" (just adept file name) h4. BeagleBoard sudo tar xjf \*rootfs.tar.bz2 \-C /media/LINUX h2. Copy custom OpenEmbedded Linux Image h3. Linux Kernel Image and u-boot bootloader Copy the kernel image and u-boot. h4. Gumstix Overo sudo cp $OE_HOME/tmp/deploy/glibc/images/overo/uImage-overo.bin /media/BOOT/uImage cp $OE_HOME/tmp/deploy/glibc/images/overo/u-boot-overo.bin /media/BOOT/u-boot.bin h4. BeagleBoard sudo cp $OE_HOME/tmp/deploy/glibc/images/beagleboard/uImage-beagleboard.bin /media/BOOT/uImage cp $OE_HOME/tmp/deploy/glibc/images/beagleboard/u-boot-beagleboard.bin /media/BOOT/u-boot.bin h3. Linux root filesystem After the kernel, the root filesystem has to be copied as well. If you are overwriting an existing installation and you don't need a 100% clean system, you can just delete all files. The command below will delete all files in /media/LINUX except the lost+found directory of the EXT3 file system. sudo rm \-rf /media/LINUX/\* && sudo mkdir /media/LINUX/lost+foundHowever if you want a really clean disk, you should format it, but this will take considerably longer. sudo mkfs.ext3 \-L LINUX /dev/sdc2And now copy the new files. h4. Gumstix Overo The console image: sudo tar xjf $OE_HOME/tmp/deploy/glibc/images/overo/omap3-console-image-overo.tar.bz2 \-C /media/LINUXThe pixhawk console image: sudo tar xjf $OE_HOME/tmp/deploy/glibc/images/overo/pixhawk-console-image-overo.tar.bz2 \-C /media/LINUXOr the desktop image: sudo tar xjf $OE_HOME/tmp/deploy/glibc/images/overo/omap3-desktop-image-overo.tar.bz2 \-C /media/LINUX h4. BeagleBoard The console image: sudo tar xjf $OE_HOME/tmp/deploy/glibc/images/beagleboard/omap3-console-image-beagleboard.tar.bz2 \-C /media/LINUXOr the desktop image: sudo tar xjf $OE_HOME/tmp/deploy/glibc/images/beagleboard/omap3-desktop-image-overo.beagleboard.bz2 \-C /media/LINUX h1. Unmount the SD/SDHC card Now unmount the drive either manually (by clicking the unmount icon on the desktop) or by shell command: sync sudo umount /media/BOOT sudo umount /media/LINUX sudo rm \-r /media/BOOT sudo rm \-r /media/LINUX h1. Copy bytewise from one SDHC card to another If you have modified your installation and want to clone the content of the SD card, you can do this with dd. Make sure to plug in the source card first, then the destination card. Check the file names with: dmesg \| tailAnd unmount the card (with the GUI or with umount /dev/sdb). Then use dd to copy the first gigabyte from one card to the other (including partition table, etc.): sudo dd if=/dev/sdb of=/dev/sdc bs=1073741824]]> 11240344 11273084 " ## \# Set the RTC, only if a battery has been installed on the Beagleboard# # set the battery backed RTC, "hwclock \-w" ## \# Build the McStar Natively# # Enter "shutdown now". # Power off Beagleboard # Remove Ethernet Dongle from the Beagleboard {warning:title=Copy McStar app from host to harddrive}{warning} # Attach a freshly EXT3 formatted USB drive to the host # Enter "cp \-R \~/McStar/app /media/sda1/." # Unmount USB drive # Remove the USB host from the host and connect it to the Beagleboard # Power up the Beagleboard # Enter "root" at the Linux prompt # Enter "cd /media/sda1/app/src" # Enter "touch Makefile \*.h \*.cpp" # Enter "make clean" # Enter "make" ## \# Test the McStar App for 10 minutes, writing a new file every minute # Enter "mkdir /media/sda1/data" # Enter "cd /media/sda1/app/scripts" # Enter "./test_mcstar.sh" \\ \\ ---- h3. Notes on Beagel Board and SD Card Copy h1. Copy Linux filesystem on bootable SD card This tutorial is part of our Tutorials section. It shows how to flash an image onto an SD/SDHC card. This guide assumes that the card is correctly partitioned, as described in the Create a bootable SD/SDHC card in Ubuntu tutorial. h4. Steps in this tutorial # Mount the SD/SDHC card (if not already mounted) # Write bootloader if necessary # Write Linux kernel image # Write Linux root file system # Unmount h1. Quick Solution: Copy an already existing card If you have already one working SD image and an (absolutely similar) formatted second card, you can just copy them. WARNING Please be aware that the filesystem names (/dev/sdb1, etc.) can differ from system to system, make sure to select the right one. Copy one SD card to another: sudo dd if=/dev/sdb of=/dev/sdcThe safer alternative: Copy the SD card to harddisk and then onto another sudo dd if=/dev/sdb of=~/sd-card-copy.binNow back on the second SD card: sudo dd if=~/sd-card-copy.bin of=/dev/sdb h1. Mount SD/SDHC card Check where linux mounted the card. One way is to check this via mount . Call mount to see where the card has been mounted. Two partitions should have been mounted, one named '/media/BOOT' and the other one '/media/LINUX'. Note the device name, e.g. '/dev/sdb'. mountIf the card has not been mounted, you have two choices: h3. Automatic _Just unplug and re-plug the cardreader. It will be detected and mounted automatically._ h3. Manually If the check with mount didn't work out, use dmesg: dmesg \| tailWatch out for a line like this: [sdc] Attached SCSI removable diskWhere *sdc* could also be sdc or sdd. If it was sdb, the device name of the memory card is */dev/sdc*. sudo mkdir \-p /media/BOOT sudo mount /dev/sdc1 /media/BOOT sudo mkdir \-p /media/LINUX sudo mount /dev/sdc2 /media/LINUX h1. Copy files on the BOOT partition (MLO, u-boot.bin and uImage) _Please note that the bootloader files don't have to be rewritten every time. This applies especially when a new custom Linux system is created with_ BitBake and OpenEmbedded_. However if you work close to the hardware, e.g. on drivers, this is different.\_ h4. Overo Download MLO and uBoot from this link (commands for shell below): * PIXHAWK OpenEmbedded Images Download (OpenCV and libdc1394 ready) *IMPORTANT: Copy MLO FIRST\!*. The commands below download the two files and copy them in the right order on the boot partition. _You may have to adjust the filenames for future revisions._ cd $HOME wget [http://pixhawk.ethz.ch/wiki/_media/symlink/images/overo/mlo-overo] wget [http://pixhawk.ethz.ch/wiki/_media/symlink/images/overo/u-boot.bin-overoAnd] now copy the two files onto the boot partition (*MLO first* because of a bug in the X-loader which causes problems if MLO is not the first file written onto the boot partition). cp MLO-overo\* /media/BOOT/MLO cp u-boot.bin-overo\* /media/BOOT/u-boot.bin The Linux kernel (*uImage*) resides also on the *BOOT* partition of the SD-card. If you compile a new version of the kernel you have to copy the new *uImage* on the BOOT partition. See the instructions below. h4. BeagleBoard Download MLO and uBoot from this link (commands for shell below): * [http://www.angstrom-distribution.org/demo/beagleboard/] * Only for PIXHAWK Team (_will be made public in october_) *IMPORTANT: Copy MLO FIRST\!*. The commands below download the two files and copy them in the right order on the boot partition. _You may have to adjust the filenames for future revisions._ cd $HOME wget [http://www.angstrom-distribution.org/demo/beagleboard/MLO] wget [http://www.angstrom-distribution.org/demo/beagleboard/u-boot.binAnd] now copy the two files onto the boot partition (*MLO first* because of a bug in the X-loader which causes problems if MLO is not the first file written onto the boot partition). cp MLO /media/BOOT/MLO cp u-boot.bin /media/BOOT/u-boot.bin The Linux kernel (*uImage*) resides also on the *BOOT* partition of the SD-card. If you compile a new version of the kernel you have to copy the new *uImage* on the BOOT partition. See the instructions below. h1. Copy Linux _The next step is to copy the Linux kernel and the Linux root filesystem on the BOOT and LINUX partitions. You can use_ *{_}precompiled binaries{_}* _for both or_ *{_}compile an OpenEmbedded image yourself{_}{*}_. Instructions for both options are provided below._ h2. Copy the precompiled Ã…ngström Image The precompiled Ã…ngström image consists (besided MLO and u-boot.bin from the bootloader section) of two files: The Linux kernel image (uImage) and the root file system. h3. Copy uImage Download and copy the kernel image into the root directory of the boot partition. h4. Gumstix Overo cd $HOME wget [http://pixhawk.ethz.ch/wiki/_media/symlink/images/overo/uimage.bin-overo] cp uimage.bin-overo\* /media/BOOT/uImage h4. BeagleBoard cd $HOME wget [http://www.angstrom-distribution.org/demo/beagleboard/uImage] cp uImage /media/BOOT/uImage h3. Copy the Linux root file system The file is named *rootfs.tar.bz2 for the Beagle link and omap3-desktop-image-overo\-*.tar.bz2 for the Overo link below. Check the main folder for the current name. * Gumstix Overo: PIXHAWK OpenEmbedded Images Download (OpenCV and libdc1394 ready) * BeagleBoard: [http://www.angstrom-distribution.org/demo/beagleboard/] Download the files to a temporary directory, e.g. the Desktop or your user folder. The next step is to extract these files into the LINUX partition (NOT the boot partition). This can only be done by using Linux. If you're using Windows or MacOS, read this. h4. Gumstix Overo If you have downloaded the console image: wget [http://pixhawk.ethz.ch/wiki/_media/symlink/images/overo/pixhawk-console-image-overo.tar.bz2] sudo tar xjf pixhawk-console-image-overo-*.tar.bz2 \-C /media/LINUXOr the desktop image: wget [http://pixhawk.ethz.ch/wiki/_media/symlink/images/overo/pixhawk-desktop-image-overo.tar.bz2] sudo tar xjf pixhawk-desktop-image-overo\-*.tar.bz2* *{-}C /media/LINUXpossibly, "pixhawk-desktop-image-overo{-}*.tar.bz2" has to be changed into "pixhawk-console-image-overo.tar.bz2" (just adept file name) h4. BeagleBoard sudo tar xjf \*rootfs.tar.bz2 \-C /media/LINUX h2. Copy custom OpenEmbedded Linux Image h3. Linux Kernel Image and u-boot bootloader Copy the kernel image and u-boot. h4. Gumstix Overo sudo cp $OE_HOME/tmp/deploy/glibc/images/overo/uImage-overo.bin /media/BOOT/uImage cp $OE_HOME/tmp/deploy/glibc/images/overo/u-boot-overo.bin /media/BOOT/u-boot.bin h4. BeagleBoard sudo cp $OE_HOME/tmp/deploy/glibc/images/beagleboard/uImage-beagleboard.bin /media/BOOT/uImage cp $OE_HOME/tmp/deploy/glibc/images/beagleboard/u-boot-beagleboard.bin /media/BOOT/u-boot.bin h3. Linux root filesystem After the kernel, the root filesystem has to be copied as well. If you are overwriting an existing installation and you don't need a 100% clean system, you can just delete all files. The command below will delete all files in /media/LINUX except the lost+found directory of the EXT3 file system. sudo rm \-rf /media/LINUX/\* && sudo mkdir /media/LINUX/lost+foundHowever if you want a really clean disk, you should format it, but this will take considerably longer. sudo mkfs.ext3 \-L LINUX /dev/sdc2And now copy the new files. h4. Gumstix Overo The console image: sudo tar xjf $OE_HOME/tmp/deploy/glibc/images/overo/omap3-console-image-overo.tar.bz2 \-C /media/LINUXThe pixhawk console image: sudo tar xjf $OE_HOME/tmp/deploy/glibc/images/overo/pixhawk-console-image-overo.tar.bz2 \-C /media/LINUXOr the desktop image: sudo tar xjf $OE_HOME/tmp/deploy/glibc/images/overo/omap3-desktop-image-overo.tar.bz2 \-C /media/LINUX h4. BeagleBoard The console image: sudo tar xjf $OE_HOME/tmp/deploy/glibc/images/beagleboard/omap3-console-image-beagleboard.tar.bz2 \-C /media/LINUXOr the desktop image: sudo tar xjf $OE_HOME/tmp/deploy/glibc/images/beagleboard/omap3-desktop-image-overo.beagleboard.bz2 \-C /media/LINUX h1. Unmount the SD/SDHC card Now unmount the drive either manually (by clicking the unmount icon on the desktop) or by shell command: sync sudo umount /media/BOOT sudo umount /media/LINUX sudo rm \-r /media/BOOT sudo rm \-r /media/LINUX h1. Copy bytewise from one SDHC card to another If you have modified your installation and want to clone the content of the SD card, you can do this with dd. Make sure to plug in the source card first, then the destination card. Check the file names with: dmesg \| tailAnd unmount the card (with the GUI or with umount /dev/sdb). Then use dd to copy the first gigabyte from one card to the other (including partition table, etc.): sudo dd if=/dev/sdb of=/dev/sdc bs=1073741824]]> 11240345 14549017 14516250 11273085 " ## \# Set the RTC, only if a battery has been installed on the Beagleboard# # set the battery backed RTC, "hwclock \-w" ## \# Build the McStar Natively# # Enter "shutdown now". # Power off Beagleboard # Remove Ethernet Dongle from the Beagleboard {warning:title=Copy McStar app from host to harddrive}{warning} # Attach a freshly EXT3 formatted USB drive to the host # Enter "cp \-R \~/McStar/app /media/sda1/." # Unmount USB drive # Remove the USB host from the host and connect it to the Beagleboard # Power up the Beagleboard # Enter "root" at the Linux prompt # Enter "cd /media/sda1/app/src" # Enter "touch Makefile \*.h \*.cpp" # Enter "make clean" # Enter "make" ## \# Test the McStar App for 10 minutes, writing a new file every minute # Enter "mkdir /media/sda1/data" # Enter "cd /media/sda1/app/scripts" # Enter "./test_mcstar.sh" \\ \\ ---- h3. Notes on Beagel Board and SD Card Copy h1. Copy Linux filesystem on bootable SD card This tutorial is part of our Tutorials section. It shows how to flash an image onto an SD/SDHC card. This guide assumes that the card is correctly partitioned, as described in the Create a bootable SD/SDHC card in Ubuntu tutorial. h4. Steps in this tutorial # Mount the SD/SDHC card (if not already mounted) # Write bootloader if necessary # Write Linux kernel image # Write Linux root file system # Unmount h1. Quick Solution: Copy an already existing card If you have already one working SD image and an (absolutely similar) formatted second card, you can just copy them. WARNING Please be aware that the filesystem names (/dev/sdb1, etc.) can differ from system to system, make sure to select the right one. Copy one SD card to another: sudo dd if=/dev/sdb of=/dev/sdcThe safer alternative: Copy the SD card to harddisk and then onto another sudo dd if=/dev/sdb of=~/sd-card-copy.binNow back on the second SD card: sudo dd if=~/sd-card-copy.bin of=/dev/sdb h1. Mount SD/SDHC card Check where linux mounted the card. One way is to check this via mount . Call mount to see where the card has been mounted. Two partitions should have been mounted, one named '/media/BOOT' and the other one '/media/LINUX'. Note the device name, e.g. '/dev/sdb'. mountIf the card has not been mounted, you have two choices: h3. Automatic _Just unplug and re-plug the cardreader. It will be detected and mounted automatically._ h3. Manually If the check with mount didn't work out, use dmesg: dmesg \| tailWatch out for a line like this: [sdc] Attached SCSI removable diskWhere *sdc* could also be sdc or sdd. If it was sdb, the device name of the memory card is */dev/sdc*. sudo mkdir \-p /media/BOOT sudo mount /dev/sdc1 /media/BOOT sudo mkdir \-p /media/LINUX sudo mount /dev/sdc2 /media/LINUX h1. Copy files on the BOOT partition (MLO, u-boot.bin and uImage) _Please note that the bootloader files don't have to be rewritten every time. This applies especially when a new custom Linux system is created with_ BitBake and OpenEmbedded_. However if you work close to the hardware, e.g. on drivers, this is different.\_ h4. Overo Download MLO and uBoot from this link (commands for shell below): * PIXHAWK OpenEmbedded Images Download (OpenCV and libdc1394 ready) *IMPORTANT: Copy MLO FIRST\!*. The commands below download the two files and copy them in the right order on the boot partition. _You may have to adjust the filenames for future revisions._ cd $HOME wget [http://pixhawk.ethz.ch/wiki/_media/symlink/images/overo/mlo-overo] wget [http://pixhawk.ethz.ch/wiki/_media/symlink/images/overo/u-boot.bin-overoAnd] now copy the two files onto the boot partition (*MLO first* because of a bug in the X-loader which causes problems if MLO is not the first file written onto the boot partition). cp MLO-overo\* /media/BOOT/MLO cp u-boot.bin-overo\* /media/BOOT/u-boot.bin The Linux kernel (*uImage*) resides also on the *BOOT* partition of the SD-card. If you compile a new version of the kernel you have to copy the new *uImage* on the BOOT partition. See the instructions below. h4. BeagleBoard Download MLO and uBoot from this link (commands for shell below): * [http://www.angstrom-distribution.org/demo/beagleboard/] * Only for PIXHAWK Team (_will be made public in october_) *IMPORTANT: Copy MLO FIRST\!*. The commands below download the two files and copy them in the right order on the boot partition. _You may have to adjust the filenames for future revisions._ cd $HOME wget [http://www.angstrom-distribution.org/demo/beagleboard/MLO] wget [http://www.angstrom-distribution.org/demo/beagleboard/u-boot.binAnd] now copy the two files onto the boot partition (*MLO first* because of a bug in the X-loader which causes problems if MLO is not the first file written onto the boot partition). cp MLO /media/BOOT/MLO cp u-boot.bin /media/BOOT/u-boot.bin The Linux kernel (*uImage*) resides also on the *BOOT* partition of the SD-card. If you compile a new version of the kernel you have to copy the new *uImage* on the BOOT partition. See the instructions below. h1. Copy Linux _The next step is to copy the Linux kernel and the Linux root filesystem on the BOOT and LINUX partitions. You can use_ *{_}precompiled binaries{_}* _for both or_ *{_}compile an OpenEmbedded image yourself{_}{*}_. Instructions for both options are provided below._ h2. Copy the precompiled Ã…ngström Image The precompiled Ã…ngström image consists (besided MLO and u-boot.bin from the bootloader section) of two files: The Linux kernel image (uImage) and the root file system. h3. Copy uImage Download and copy the kernel image into the root directory of the boot partition. h4. Gumstix Overo cd $HOME wget [http://pixhawk.ethz.ch/wiki/_media/symlink/images/overo/uimage.bin-overo] cp uimage.bin-overo\* /media/BOOT/uImage h4. BeagleBoard cd $HOME wget [http://www.angstrom-distribution.org/demo/beagleboard/uImage] cp uImage /media/BOOT/uImage h3. Copy the Linux root file system The file is named *rootfs.tar.bz2 for the Beagle link and omap3-desktop-image-overo\-*.tar.bz2 for the Overo link below. Check the main folder for the current name. * Gumstix Overo: PIXHAWK OpenEmbedded Images Download (OpenCV and libdc1394 ready) * BeagleBoard: [http://www.angstrom-distribution.org/demo/beagleboard/] Download the files to a temporary directory, e.g. the Desktop or your user folder. The next step is to extract these files into the LINUX partition (NOT the boot partition). This can only be done by using Linux. If you're using Windows or MacOS, read this. h4. Gumstix Overo If you have downloaded the console image: wget [http://pixhawk.ethz.ch/wiki/_media/symlink/images/overo/pixhawk-console-image-overo.tar.bz2] sudo tar xjf pixhawk-console-image-overo-*.tar.bz2 \-C /media/LINUXOr the desktop image: wget [http://pixhawk.ethz.ch/wiki/_media/symlink/images/overo/pixhawk-desktop-image-overo.tar.bz2] sudo tar xjf pixhawk-desktop-image-overo\-*.tar.bz2* *{-}C /media/LINUXpossibly, "pixhawk-desktop-image-overo{-}*.tar.bz2" has to be changed into "pixhawk-console-image-overo.tar.bz2" (just adept file name) h4. BeagleBoard sudo tar xjf \*rootfs.tar.bz2 \-C /media/LINUX h2. Copy custom OpenEmbedded Linux Image h3. Linux Kernel Image and u-boot bootloader Copy the kernel image and u-boot. h4. Gumstix Overo sudo cp $OE_HOME/tmp/deploy/glibc/images/overo/uImage-overo.bin /media/BOOT/uImage cp $OE_HOME/tmp/deploy/glibc/images/overo/u-boot-overo.bin /media/BOOT/u-boot.bin h4. BeagleBoard sudo cp $OE_HOME/tmp/deploy/glibc/images/beagleboard/uImage-beagleboard.bin /media/BOOT/uImage cp $OE_HOME/tmp/deploy/glibc/images/beagleboard/u-boot-beagleboard.bin /media/BOOT/u-boot.bin h3. Linux root filesystem After the kernel, the root filesystem has to be copied as well. If you are overwriting an existing installation and you don't need a 100% clean system, you can just delete all files. The command below will delete all files in /media/LINUX except the lost+found directory of the EXT3 file system. sudo rm \-rf /media/LINUX/\* && sudo mkdir /media/LINUX/lost+foundHowever if you want a really clean disk, you should format it, but this will take considerably longer. sudo mkfs.ext3 \-L LINUX /dev/sdc2And now copy the new files. h4. Gumstix Overo The console image: sudo tar xjf $OE_HOME/tmp/deploy/glibc/images/overo/omap3-console-image-overo.tar.bz2 \-C /media/LINUXThe pixhawk console image: sudo tar xjf $OE_HOME/tmp/deploy/glibc/images/overo/pixhawk-console-image-overo.tar.bz2 \-C /media/LINUXOr the desktop image: sudo tar xjf $OE_HOME/tmp/deploy/glibc/images/overo/omap3-desktop-image-overo.tar.bz2 \-C /media/LINUX h4. BeagleBoard The console image: sudo tar xjf $OE_HOME/tmp/deploy/glibc/images/beagleboard/omap3-console-image-beagleboard.tar.bz2 \-C /media/LINUXOr the desktop image: sudo tar xjf $OE_HOME/tmp/deploy/glibc/images/beagleboard/omap3-desktop-image-overo.beagleboard.bz2 \-C /media/LINUX h1. Unmount the SD/SDHC card Now unmount the drive either manually (by clicking the unmount icon on the desktop) or by shell command: sync sudo umount /media/BOOT sudo umount /media/LINUX sudo rm \-r /media/BOOT sudo rm \-r /media/LINUX h1. Copy bytewise from one SDHC card to another If you have modified your installation and want to clone the content of the SD card, you can do this with dd. Make sure to plug in the source card first, then the destination card. Check the file names with: dmesg \| tailAnd unmount the card (with the GUI or with umount /dev/sdb). Then use dd to copy the first gigabyte from one card to the other (including partition table, etc.): sudo dd if=/dev/sdb of=/dev/sdc bs=1073741824]]> 11240347 14549016 14516249 11273088 11240350 11273089 11240351 8388620 "Downloads">"2.1 Releases">"2.1.1" # I then clicked on alfresco-enterprise-tomcat-2.1.1.zip to download the zip file. # Went to [http://customers.alfresco.com] (I was still logged in) # Went to "Company Home">"Downloads">"2.1 Releases">"2.1.1">"License Files" # I went ahead and downloaded all the "*.lic" files, but I think I only need enterprise-network-customer-unlimited.lic" # Logged out of Alfresco. # Since I suspect I will need a JDBC driver for SQLServer, I downloaded the jTDS-1.2.2 driver from the jtds web site (just Google jtds and go to the download section of the top google return). # I closed the Firefox browser. # I extracted the jtds-1.2.2.jar file from the jtds download # I downloaded and installed the JRockit 6 R27.4 JDK Microsoft Windows (x86 - 32 bit) from BEA's web site {note} After installing JRockit, make sure you set the JAVA_HOME environment variable to point to the installation of JRockit. For example, I went to the desktop, right clicked on the computer, did Properties, then clicked on the Advanced tab, then click on the environment variables button and then created a new system variable named JAVA_HOME and set to c:\bin\Java\jrockit-R27.4.0-jdk1.6.0_02 {note} # I ran the installer, changed the "Program Files" to "bin" in the installation directory for both the JDK and the JRE. I also chose to install the JRE as public. # Using Firefox, I downloaded the PHP 5.2.5 Windows Installer from php.net and installed it. Although I installed it, I did not integrate it with a web server as I want Alfresco to take port 80. I probably did not need to install PHP, but I thought I would anyway. (again, I changed install path from "Program Files" to "bin" # I also downloaded and installed OpenOffice and ran it once so I could get through the initial startup # I setup a Alfresco database on the server Solstice and granted the LAGOON\DB_Collaboration account to be the db_owner of the Alfresco database. # I unzipped the alfresco tomcat zip file to an alfresco directory in c:\bin # I then went to the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions directory for the customization of the server. ## I edited the custom-repository.properties file ### Changed the dir.root and dir.indexes to look like: {noformat} dir.root=//tornado.shore.mbari.org/Alfresco/alf_data dir.indexes=d:/alf_data/lucene-indexes {noformat} ### Commented out the db.* lines for the HSQL Connection (db.driver and db.url) ### Uncommented the db.* lines for MSSQL and changed to use the jTDS driver. They should look like: {noformat} db.driver=net.sourceforge.jtds.jdbc.Driver db.url=jdbc:jtds:sqlserver://solstice.shore.mbari.org/Alfresco;domain=SHORE;user=DB_Collaboration;password=XXXXXXXXX {noformat} ### I also added the following section to override the mail server settings {noformat} # Mail server configuration mail.host=mail.mbari.org mail.port=25 mail.username= mail.password= {noformat} ## Edited the custom-hibernate-dialect.properties file ### Commented out the HSQL Dialect ### Uncommented the MSSQL Dialect # I then installed the jtds-1.2.2.jar in the c:\bin\alfresco\tomcat\common\lib so that it will be on the classpath when Alfresco is started # Now this is not necessarily fun, but in order to really get it configured the way we want it, you need to pull the original .war file out, edit some stuff inside and re-create the .war. {note} This should all be done before starting Alfresco for the first time. {note} # Copy the c:\Alfresco\tomcat\webapps\alfresco.war file to your home directory. # Make a second copy so that you will always the original (I copied to alfresco.war.orig and moved it somewhere else. It is important to move it and have only the alfresco.war file in the directory because when you un-jar it, all the files go right where alfresco.war is.) # From a command line, un-jar the war file using: {noformat} jar -xvf alfresco.war {noformat} # This unpacks a lot of files and after it completes, move (or delete) the alfresco.war file from the directory. This needs to be done so it does not end up in the new .war file. # I wanted to change the "Company Home" that seems to be everywhere to something that says MBARI. ## Edited ./WEB-INF/classes/alfresco/messages/webclient.properties and changed company_home from 'Company Home' to 'MBARI' ## Edited ./WEB-INF/classes/alfresco/messages/webclient_en_US.properties and changed company_home from 'Company Home' to 'MBARI' ## I edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces.properties and changed the first two lines to read {noformat} spaces.company_home.name=MBARI spaces.company_home.description=The root space for MBARI {noformat} ## Edited ./WEB-INF/classes/alfresco/messages/bootstrap-spaces_en_US.properties and made the same changes as the previous step {tip} This took a bit to find all these, and to be honest, I am not sure which one actually made the change on the GUI, but I suspect it was the _en_US ones. {tip} # When users are imported via LDAP, user spaces get created automatically. In order to put them where I wanted them to go (instead of right in the Company Home), I edited the ./WEB-INF/classes/alfresco/authentication-services-context.xml file. In the file there is a bean with an name of personalHomeFolderProvider. There is a property name 'path' and I added {noformat} /${spaces.user_homes.childname} {noformat} to the end to try to get them to create the user spaces there instead of in the Company Home. The final bean XML looks like: {noformat} /${spaces.company_home.childname}/${spaces.user_homes.childname} ${spaces.store} false All All {noformat} # I wanted to change the logo that is used. I attached the replacement logo [here|^AlfrescoLogo32.png]. Copy this to ./images/logo and overwrite the one that is there. # In order to setup SSL for the application (will do that later), edit ./WEB-INF/web.xml and add the following {noformat} Login Pages /* CONFIDENTIAL {noformat} right before the ending tag at the bottom of the file. # Now in order to change the default behavior so that all content is versioned from the start, I edited the .\WEB-INF\classes\alfresco\model\contentModel.xml and searched for the content type definition block. {noformat} Content cm:cmobject true d:content false true false true {noformat} and added the following block right before the ending tag: {noformat} cm:versionable {noformat} so the final block looks like: {noformat} Content cm:cmobject true d:content false true false true cm:versionable {noformat} # Lastly, I wanted to redirect the log files to a separate disk. This is done because in the Windows hardening process, most of the disk space ends up on drive D: where alfresco does not live. The log files quickly fill up the small C: drive. To to this, I edited the .\WEB-INF\classes\log4j.properties and changed the log file appender location to point to a directory that was created on the D: drive called D:/alf_logs. # That takes care of all the changes to the WAR file. We can now put it back into .war form. # While you are in the directory you expanded the war file in, run ## jar cvfm alfresco.war META-INF\MANIFEST.MF . # You should now have an alfresco.war file in the directory. Move that back to the alfresco install and overwrite the existing one. # Most users like the details view, so I set the default to that by editing c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions\web-client-config-custom.xml and added: {noformat} details 20
20
20 {noformat} right before the closing tag. # Now in order to use MBARI accounts, NTLM authentication was turned on and then chained with the native Alfresco accounts so that we could have non-MBARI accounts on the Alfresco server. ## In order to enable NTLM and native Alfresco authentication, I had to edit two files. For simplicity I have just attached them here and they can be downloaded and installed in the extensions directory. ### The first file is the [ntlm-authentication-context.xml|^ntlm-authentication-context.xml] file. This configures and enables NTLM authentication. ### The next file was the [chaining-authentication-context.xml|^chaining-authentication-context.xml] file which enabled Alfresco authentication and chained it together with the NTLM authentication from the previous file. # Then in order to setup CIFS on the server, I edited the file-servers-custom.xml file to look like the attached [file-servers-custom.xml|^file-servers-custom.xml] file. # In order to grant certain accounts admin privs, I created a new custom-authority-services-context.xml in the same directory as the ldap-authentication-context.xml file and added {noformat} kgomes admin administrator {noformat} # In order for Alfresco to handle all port 80 traffic, I changed Tomcat so that it takes port 80 and SSL goes over port 443. So I edited the c:\Alfresco\tomcat\conf\server.xml file and changed the 8080 port to 80 and the 8443 port to 443 (the 443 change is done in two places). # Now I needed to setup the SSL for the web traffic. Cathy Sewell was instrumental in getting this working. She ordered a new certificate specifically for alfresco and put it in the c:\local\cert folder. Here are the instructions for what she did to get the certficate installed. {noformat} SSL certificate for server Alfresco - 1/2/08 C:\bin\Java\jrockit-R27.1.0-jre1.6.0_02\bin>keytool -genkey -alias tomcat -keyalg RSA -keystore tomcat.keystore What is your first and last name? [alfresco.mbari.org]: What is the name of your organizational unit? [IS]: What is the name of your organization? [MBARI]: What is the name of your City or Locality? [Moss Landing]: What is the name of your State or Province? [CD]: CA What is the two-letter country code for this unit? [US]: Is CN=alfresco.mbari.org, OU=IS, O=MBARI, L=Moss Landing, ST=CA, C=US correct? [no]: y Enter key password for (RETURN if same as keystore password): C:\bin\Java\jrockit-R27.4.0-jre1.6.0_02\bin>keytool -certreq -keyalg RSA -alias tomcat -file certreq.csr -keystore tomcat.keystore Enter keystore password: Generated certificate request file, certreq.csr, was submitted to SSL provider. Certificate provider sent certificate file (alfresco.mbari.org.crt), along with gd_bundle.crt, gd_cross_intermediate.crt, and gd_intermediate.crt. Additionally, I downloaded valicert_class2_root.cer from their website. These files were stored in c:\local\cert. The following commands were used to add them to the tomcat keystore: C:\bin\Java\jrockit-R27.4.0-jre1.6.0_02\bin>keytool -import -alias root -keystore tomcat.keystore -trustcacerts -file c:\local\cert\valicert_class2_root.cer Enter keystore password: Certificate already exists in system-wide CA keystore under alias Do you still want to add it to your own keystore? [no]: y Certificate was added to keystore C:\bin\Java\jrockit-R27.4.0-jre1.6.0_02\bin>keytool -import -alias cross -keystore tomcat.keystore -trustcacerts -file c:\local\cert\gd_cross_intermediate.crt Enter keystore password: Certificate was added to keystore C:\bin\Java\jrockit-R27.4.0-jre1.6.0_02\bin>keytool -import -alias intermed -keystore tomcat.keystore -trustcacerts -file c:\local\cert\gd_intermediate.crt Enter keystore password: Certificate was added to keystore C:\bin\Java\jrockit-R27.4.0-jre1.6.0_02\bin>keytool -import -alias tomcat -keystore tomcat.keystore -trustcacerts -file c:\local\cert\alfresco.mbari.org.crt Enter keystore password: Certificate reply was installed in keystore {noformat} # I edited the c:\bin\alfresco\tomcat\conf\server.xml file and uncommented the SSL section and edited to look like that shown below. {noformat} {noformat} # Since I was in the server.xml file, I went ahead and changed it so that the default webapp was alfresco so that you would get alfresco anytime you went to the base URL. I did this by adding: {noformat} {noformat} as the last line of the tag section (right before the closing tag). {note} You will also notice the Valve tag that I had to add to turn off proxy cache disabling so that IE clients would work correctly over SSL. Gotta love M$. {note} # I copied the enterprise-network-unlimited.lic file into the c:\Alfresco\tomcat\shared\classes\alfresco\extensions\license directory # Just to keep things clean, I edited the c:\bin\alfresco\alfresco.bat file and put 'rem' in front of the second JAVA_OPTS set as I am using Java 6. # Now after you run it for the first time and the database structure gets created, you can't restart it because you get: {noformat} java.sql.SQLException: Column names in each table must be unique. Column name 'ID_' in table 'JBPM_ACTION' is specified more than once. {noformat} Sigh, so in order to keep Alfresco from hurting itself, I had to turn off the schema updates. This is done by editing the c:\bin\alfresco\tomcat\shared\classes\alfresco\extensions\custom-repository.properties and adding the following: {noformat} db.schema.update=false {noformat} and then restarting alfresco. # To install Alfresco as a Windows Service use a command prompt and enter the following: {noformat} cd c:\bin\alfresco\tomcat\bin service.bat install alfresco tomcat5.exe //US//alfresco --DisplayName "Alfresco Server" tomcat5.exe //US//alfresco --JvmMs=512 --JvmMx=1024 --JvmSs=64 tomcat5.exe //US//alfresco --JavaHome=c:/bin/Java/jrockit-R27.4.0-jdk1.6.0_02 tomcat5.exe //US//alfresco --Environment ALF_HOME=c:/bin/alfresco/ tomcat5.exe //US//alfresco --Environment PATH=c:/bin/alfresco/bin;%PATH% tomcat5.exe //US//alfresco --StartPath c:/bin/alfresco --Startup auto {noformat} # To uninstall the service, at a later time, do the following: {noformat} cd c:\bin\alfresco\tomcat\bin service.bat uninstall alfresco {noformat} # To edit your service settings at any time: {noformat} cd c:\alfresco\tomcat\bin tomcat5w.exe //ES//alfresco {noformat} {warning} These next couple of steps had to be taken to install a patch from Alfresco for an issue with bulk uploads I was having. Essentially when file and path structures get really long and nasty, Alfresco was throwing an error and bailing out. This patch (two Java classes) fixed that issue. {warning} # Next, I downloaded the attached [JAR|^act2139.jar] file and copied it to the c:\bin\alfresco\tomcat\webapps\alfresco\WEB-INF\classes directory. # I shutdown Alfresco and then unjarred the file to install the new classes. They are: ## org/alfresco/filesys/smb/server/SMBSrvPacket.class ## org/alfresco/filesys/util/DataBuffer.class # I would assume since they do not overwrite anything, that this location is further up in the class loader and so it will load these new classes first. # I deleted the act2139.jar file and the META-INF directory that the unjarring process created. # In order to install certain modules (like the email listener), I had to get the Alfresco Module Manager from the customers.alfresco.com download site. I downloaded the alfresco-mmt-2.1.1.jar file locally so I could use it to install modules. # I then downloaded the email listener module from [http://forge.alfresco.com/projects/email-listener/]. It came as a zip file, so I unzipped it and it created a folder with the appropriate emailListener.amp in it. # Make another backup copy of the alfresco.war file and put somewhere in case you want to roll this back. # Open a command prompt windows and cd to the location where the Alfresco Module Manager jar is. # Run the following: {noformat} java -jar alfresco-mmt-2.1.1.jar path_to_emailListener.amp path_to_alfresco.war {noformat} So for me this looked like: {noformat} java -jar alfresco-mmt-2.1.1.jar .\email-listener_2.1RC2\emailListener.amp c:\bin\alfresco\tomcat\webapps\alfresco.war {noformat} # You should be able to verify the install by running: {noformat} java -jar alfresco-mmt-2.1.1.jar list c:\bin\alfresco\tomcat\webapps\alfresco.war {noformat} and you should see something like: {noformat} Module 'emailListener' installed in 'c:\bin\alfresco\tomcat\webapps\alfresco.war' - Title: EmailListener - Version: 2.1 - Install Date: Fri Dec 07 08:43:10 PST 2007 - Desription: EmailListener Module {noformat} # Finally, to start the service, just go into your Windows Service control panel and locate the service that is now named 'Alfresco Server'. You can start and stop Alfresco from this control panel. h1. Content Migration Now, in order to migrate content from old alfresco and normal file structures, I did the following: h3. For content already in alfresco: # Navigate to the space whose contents you want to migrate. For example, let's say I want to migrate the stuff from my personal space. I would navigate (using the WebUI) to the /MBARI/User Homes/kgomes space. You should see the contents of the kgomes folder from this view. # Click on 'More actions->View Details'. # On the right hand side, click on 'Export'. # For package name, I usually enter the space name followed by '_export', but it doesn't really matter. # Click on the link that says 'Click here to select the destination' and select somewhere that you will be able to download the .acp file from. # Select 'Current Space'. # Select 'Include Children'. # Uncheck 'Include this space' unless you have content (documents) in this specific folder (anything other than folders) that you want to migrate. This is a bit tricky, but there are two ways to do this. If you want to have the top level folder created, use the 'Include this space' and that will create the top level folder. Otherwise, if will expand into the folder in which you import the .acp file into. This is important in cases where the folder has already been created for you (like with user homes) and you have to migrate content into that folder. If you have the option to create the top level directory, by all means do so. # Uncheck 'Export in background' so you can force it to happen and you know when it is complete.]]> 8355852 8388619 8355851 11273028 11240288 11273034 11240294 11273042 " ## \# Set the RTC, only if a battery has been installed on the Beagleboard# # set the battery backed RTC, "hwclock \-w" ## \# Build the McStar Natively# # Enter "shutdown now". # Power off Beagleboard # Remove Ethernet Dongle # Attach a (not so) freshly EXT3 formatted USB drive to the host # Enter "cp \-R \~/McStar/app /media/sda/." # Remove the USB host from the host and connect it to the Beagleboard # Power up the Beagleboard # Enter "root" at the Linux prompt # Enter "cd /media/sda/app/src" # Enter "touch Makefile \*.h \*.cpp" # Enter "make clean" # Enter "make" ## \# Test the McStar App for 10 minutes, writing a new file every minute # Enter "mkdir /media/sda/data" # Enter "cd /media/sda/app/scripts" # Enter "./test_mcstar.sh"]]> 11240303 11273045 " ## \# Set the RTC, only if a battery has been installed on the Beagleboard# # set the battery backed RTC, "hwclock \-w" ## \# Build the McStar Natively# # Enter "shutdown now". # Power off Beagleboard # Remove Ethernet Dongle # Attach a (not so) freshly EXT3 formatted USB drive to the host # Enter "cp \-R \~/McStar/app /media/sda/." # Remove the USB host from the host and connect it to the Beagleboard # Power up the Beagleboard # Enter "root" at the Linux prompt # Enter "cd /media/sda/app/src" # Enter "touch Makefile \*.h \*.cpp" # Enter "make clean" # Enter "make" ## \# Test the McStar App for 10 minutes, writing a new file every minute # Enter "mkdir /media/sda/data" # Enter "cd /media/sda/app/scripts" # Enter "./test_mcstar.sh"]]> 11240306 19074271 19041589 11273043 " ## \# Set the RTC, only if a battery has been installed on the Beagleboard# # set the battery backed RTC, "hwclock \-w" ## \# Build the McStar Natively# # Enter "shutdown now". # Power off Beagleboard # Remove Ethernet Dongle # Attach a (not so) freshly EXT3 formatted USB drive to the host # Enter "cp \-R \~/McStar/app /media/sda/." # Remove the USB host from the host and connect it to the Beagleboard # Power up the Beagleboard # Enter "root" at the Linux prompt # Enter "cd /media/sda/app/src" # Enter "touch Makefile \*.h \*.cpp" # Enter "make clean" # Enter "make" ## \# Test the McStar App for 10 minutes, writing a new file every minute # Enter "mkdir /media/sda/data" # Enter "cd /media/sda/app/scripts" # Enter "./test_mcstar.sh"]]> 11240304 11273050 " ## \# Set the RTC, only if a battery has been installed on the Beagleboard# # set the battery backed RTC, "hwclock \-w" ## \# Build the McStar Natively# # Enter "shutdown now". # Power off Beagleboard # Remove Ethernet Dongle # Attach a (not so) freshly EXT3 formatted USB drive to the host # Enter "cp \-R \~/McStar/app /media/sda/." # Remove the USB host from the host and connect it to the Beagleboard # Power up the Beagleboard # Enter "root" at the Linux prompt # Enter "cd /media/sda/app/src" # Enter "touch Makefile \*.h \*.cpp" # Enter "make clean" # Enter "make" ## \# Test the McStar App for 10 minutes, writing a new file every minute # Enter "mkdir /media/sda/data" # Enter "cd /media/sda/app/scripts" # Enter "./test_mcstar.sh"]]> 11240311 11273047 " ## \# Set the RTC, only if a battery has been installed on the Beagleboard# # set the battery backed RTC, "hwclock \-w" ## \# Build the McStar Natively# # Enter "shutdown now". # Power off Beagleboard # Remove Ethernet Dongle # Attach a (not so) freshly EXT3 formatted USB drive to the host # Enter "cp \-R \~/McStar/app /media/sda/." # Remove the USB host from the host and connect it to the Beagleboard # Power up the Beagleboard # Enter "root" at the Linux prompt # Enter "cd /media/sda/app/src" # Enter "touch Makefile \*.h \*.cpp" # Enter "make clean" # Enter "make" ## \# Test the McStar App for 10 minutes, writing a new file every minute # Enter "mkdir /media/sda/data" # Enter "cd /media/sda/app/scripts" # Enter "./test_mcstar.sh"]]> 11240308 11273048 " ## \# Set the RTC, only if a battery has been installed on the Beagleboard# # set the battery backed RTC, "hwclock \-w" ## \# Build the McStar Natively# # Enter "shutdown now". # Power off Beagleboard # Remove Ethernet Dongle # Attach a (not so) freshly EXT3 formatted USB drive to the host # Enter "cp \-R \~/McStar/app /media/sda/." # Remove the USB host from the host and connect it to the Beagleboard # Power up the Beagleboard # Enter "root" at the Linux prompt # Enter "cd /media/sda/app/src" # Enter "touch Makefile \*.h \*.cpp" # Enter "make clean" # Enter "make" ## \# Test the McStar App for 10 minutes, writing a new file every minute # Enter "mkdir /media/sda/data" # Enter "cd /media/sda/app/scripts" # Enter "./test_mcstar.sh"]]> 11240309 11273054 " ## \# Set the RTC, only if a battery has been installed on the Beagleboard# # set the battery backed RTC, "hwclock \-w" ## \# Build the McStar Natively# # Enter "shutdown now". # Power off Beagleboard # Remove Ethernet Dongle # Attach a (not so) freshly EXT3 formatted USB drive to the host # Enter "cp \-R \~/McStar/app /media/sda/." # Remove the USB host from the host and connect it to the Beagleboard # Power up the Beagleboard # Enter "root" at the Linux prompt # Enter "cd /media/sda/app/src" # Enter "touch Makefile \*.h \*.cpp" # Enter "make clean" # Enter "make" ## \# Test the McStar App for 10 minutes, writing a new file every minute # Enter "mkdir /media/sda/data" # Enter "cd /media/sda/app/scripts" # Enter "./test_mcstar.sh"]]> 11240315 8388655 8355888 11273052 " ## \# Set the RTC, only if a battery has been installed on the Beagleboard# # set the battery backed RTC, "hwclock \-w" ## \# Build the McStar Natively# # Enter "shutdown now". # Power off Beagleboard # Remove Ethernet Dongle # Attach a (not so) freshly EXT3 formatted USB drive to the host # Enter "cp \-R \~/McStar/app /media/sda/." # Remove the USB host from the host and connect it to the Beagleboard # Power up the Beagleboard # Enter "root" at the Linux prompt # Enter "cd /media/sda/app/src" # Enter "touch Makefile \*.h \*.cpp" # Enter "make clean" # Enter "make" ## \# Test the McStar App for 10 minutes, writing a new file every minute # Enter "mkdir /media/sda/data" # Enter "cd /media/sda/app/scripts" # Enter "./test_mcstar.sh"]]> 11240313 10356262 10388980 1 2008-04-09 12:55:07.140 2008-04-09 12:55:07.140 3114598 11273058 " ## \# Set the RTC, only if a battery has been installed on the Beagleboard# # set the battery backed RTC, "hwclock \-w" ## \# Build the McStar Natively# # Enter "shutdown now". # Power off Beagleboard # Remove Ethernet Dongle # Attach a (not so) freshly EXT3 formatted USB drive to the host # Enter "cp \-R \~/McStar/app /media/sda/." # Remove the USB host from the host and connect it to the Beagleboard # Power up the Beagleboard # Enter "root" at the Linux prompt # Enter "cd /media/sda/app/src" # Enter "touch Makefile \*.h \*.cpp" # Enter "make clean" # Enter "make" ## \# Test the McStar App for 10 minutes, writing a new file every minute # Enter "mkdir /media/sda/data" # Enter "cd /media/sda/app/scripts" # Enter "./test_mcstar.sh"]]> 11240319 11273055 " ## \# Set the RTC, only if a battery has been installed on the Beagleboard# # set the battery backed RTC, "hwclock \-w" ## \# Build the McStar Natively# # Enter "shutdown now". # Power off Beagleboard # Remove Ethernet Dongle # Attach a (not so) freshly EXT3 formatted USB drive to the host # Enter "cp \-R \~/McStar/app /media/sda/." # Remove the USB host from the host and connect it to the Beagleboard # Power up the Beagleboard # Enter "root" at the Linux prompt # Enter "cd /media/sda/app/src" # Enter "touch Makefile \*.h \*.cpp" # Enter "make clean" # Enter "make" ## \# Test the McStar App for 10 minutes, writing a new file every minute # Enter "mkdir /media/sda/data" # Enter "cd /media/sda/app/scripts" # Enter "./test_mcstar.sh"]]> 11240316 8388654 8355887 11273056 " ## \# Set the RTC, only if a battery has been installed on the Beagleboard# # set the battery backed RTC, "hwclock \-w" ## \# Build the McStar Natively# # Enter "shutdown now". # Power off Beagleboard # Remove Ethernet Dongle # Attach a (not so) freshly EXT3 formatted USB drive to the host # Enter "cp \-R \~/McStar/app /media/sda/." # Remove the USB host from the host and connect it to the Beagleboard # Power up the Beagleboard # Enter "root" at the Linux prompt # Enter "cd /media/sda/app/src" # Enter "touch Makefile \*.h \*.cpp" # Enter "make clean" # Enter "make" ## \# Test the McStar App for 10 minutes, writing a new file every minute # Enter "mkdir /media/sda/data" # Enter "cd /media/sda/app/scripts" # Enter "./test_mcstar.sh"]]> 11240317 16449561 16416794 16449560 16416793 19074226 19041543 16449558 16416791 16449555 16416788 16449556 16416789 16449563 16416796 11273016 11240276 19074235 19041552 11273018 11240278 11273024 11240284 19074230 19041547 11273026 11240286 16449551 16416784 19074228 19041545 19074233 19041550 11273020 11240280 19074234 19041551 19074231 19041548 11273022 11240282 5407261 5374526 5407262 5374527 5407255 5374520 19074204 characters. Then control goes into a forever loop, reading those dm items, formatting them for output via serial port, and then sleeping for .9 seconds. Some points to note.... # depth items is produced from pressure and ships lat, using standard algorithms by another navproc task (depthCalcTask()).  # Rov Lat/Lon is likewise produced by  the navproc rovPositionTask() from winfrog serial data. The specific datamanger item names consumed are defined in dvecsIntfc.h.{color:#ff0000}*\**{color}{color:#ff0000}\***NOTE THIS NEEDS TO BE RESOLVED FOR MIGRATION TO Rachel Carson... Vorne did not exist on Pt.Lobos/Ventana and the items names are different \! \*\*{color}{color:#ff0000}*\**{color} # The vorneTask() uses the old VT102 ascii terminal command syntax to position the cursor.  \[1,1H is the string command to move the cursor to row1,column1. Then (0x0B) is used to move relative for text appearing on line, 2,3 and 4. # If any garbage exists/gets written to character cells not normally written to during operation (ie in positions beyond end of line, it will remain there. The vorneTask makes an attempt to clear all character position by writing to all lines/cells on startup, but not after that. # The vorne display has significant lag in the time it takes to render the screen.... the serial write is practically immediate; the internal rendering of all the character positions takes perhaps a half-a-second or more.  \\]]> 19041521 16449578 16416811 19074205 19041522 19074206 19041523 16449572 16416805 16449571 16416804 16449584 16416817 16449585 16416818 16449580 16416813 16449582 16416815 19074202 19041518 6226365 6259147 7798808 JkMount status Order deny,allow Deny from all Allow from 127.0.0.1 {noformat} I then created the file /etc/httpd/conf/workers.properties with the contents: {noformat} # Define list of workers that will be used # for mapping requests # The configuration directives are valid # for the mod_jk version 1.2.18 and later # worker.list=mars # Define mars worker worker.mars.port=8009 worker.mars.host=new-ssds.mbari.org worker.mars.type=ajp13 {noformat} I then created the file /etc/httpd/conf/uiworkermap.properties with the contents: {noformat} # Simple worker configuration file # # Mount the Servlet context to the ajp13 worker /mars=mars /mars/*=mars {noformat} I then restarted the apache server. h5. Configure JBoss/Tomcat bundle I edited the file /opt/jboss/server/default/deploy/jbossweb-tomcat55.sar/server.xml. I made sure the section that turns on the AJP connector was not commented out (it was not) and it looks like: {noformat} {noformat} Lastly, I edited the /opt/jboss/server/default/deploy/jbossweb-tomcat55.sar/META-INF/jboss-service.xml and changed the following line: {noformat} false {noformat} to: {noformat} true {noformat} Then I restarted JBoss.]]> 7766042 7798797 JkMount status Order deny,allow Deny from all Allow from 127.0.0.1 {noformat}]]> 7766031 7798795 7766029 7798799 JkMount status Order deny,allow Deny from all Allow from 127.0.0.1 {noformat} I then created the file /etc/httpd/conf/workers.properties with the contents: {noformat} # Define list of workers that will be used # for mapping requests # The configuration directives are valid # for the mod_jk version 1.2.18 and later # worker.list=mars # Define mars worker worker.mars.port=8009 worker.mars.host=new-ssds.mbari.org worker.mars.type=ajp13 {noformat} I then created the file /etc/httpd/conf/uiworkermap.properties with the contents: {noformat} # Simple worker configuration file # # Mount the Servlet context to the ajp13 worker /mars=mars /mars/*=mars {noformat} I then restarted the apache server.]]> 7766033 7798800 JkMount status Order deny,allow Deny from all Allow from 127.0.0.1 {noformat} I then created the file /etc/httpd/conf/workers.properties with the contents: {noformat} # Define list of workers that will be used # for mapping requests # The configuration directives are valid # for the mod_jk version 1.2.18 and later # worker.list=mars # Define mars worker worker.mars.port=8009 worker.mars.host=new-ssds.mbari.org worker.mars.type=ajp13 {noformat} I then created the file /etc/httpd/conf/uiworkermap.properties with the contents: {noformat} # Simple worker configuration file # # Mount the Servlet context to the ajp13 worker /mars=mars /mars/*=mars {noformat} I then restarted the apache server. h5. Configure JBoss/Tomcat bundle I edited the file /opt/jboss/server/default/deploy/jbossweb-tomcat55.sar/server.xml. I made sure the section that turns on the AJP connector was not commented out (it was not) and it looks like: {noformat} {noformat} Lastly, I edited the /opt/jboss/server/default/deploy/jbossweb-tomcat55.sar/META-INF/jboss-service.xml and changed the following line: {noformat} false {noformat} to: {noformat} true {noformat}]]> 7766034 6226432 6259221 3670607 3637858 3670604 3637855 3670602 3637853 3670601 3637852 3670599 3637850 10388833 10356107 3670598 3637848 3670611 3637861 7798867 7766103 7798865 7766101 10388835 10356109 10388837 10356111 6226229 6259008 6226233 6259012 6226235 6259014 6226216 D0 52.08 52.08 \+0 \+0.00 D0->D1 104.17 104.17 \+0 \+0.00 D1->D2 156.25 156.25 \+0 \+0.00 D2->D3 208.33 208.33 \+0 \+0.00 D3->D4 260.42 260.42 \+0 \+0.00 D4->D5 312.50 312.50 \+0 \+0.00 D5->D6 364.58 364.58 \+0 \+0.00 D6->D7 416.67 416.67 \+0 \+0.00 D7->stopbit 468.75 468.75 \+0 \+0.00 end of stopb 520.83 520.83 \+0 \+0.00 \*/ UBR00=0xC0; UBR10=0x00; UMCTL0=0x00; /\* uart0 3686400Hz 19200bps \*/ UBR01=0xC0; UBR11=0x00; UMCTL1=0x00; /\* uart1 3686400Hz 19200bps \*/ h4. The simplest way to use the USART in UART mode is this: interrupt is not enabled, the software checks if it can output the next byte (UTXIFG = 1), and if a new character has been received (URXIFG = 1). \\ h4. Modbus Register Map * REG_INPUT_START         512         // input registers start at 512 * REG_INPUT_NREGS         8           // 8x16 bit registers * REG_SOLENOIDS_A        0            // Holding registers start at 0 (16 coils for each A and B) * REG_SOLENOIDS_B        1   * REG_HOLDING_START    0           // to match WAGO * REG_HOLDING_NREGS   40         // 40 is more than actual (2) * REG_COILS_START         0           // read individual coils (was 1000) * REG_COILS_SIZE           32          // 32 coils * REG_DISC_START          0           // discrete (was 1000) * REG_DISC_SIZE             32          // 32 coils \\ h3. ---- MODBUS * Commands ** Read Input Register (0x04) ** Read Holding Registers (0x03) ** Write Single Register (0x06) ** Write Multiple Registers (0x10) ** Read/Write Multiple Registers (0x17) ** Read Coils (0x01) ** Write Single Coil (0x05) ** Write Multiple Coils (0x0F) ** Read Discrete Inputs (0x02) ** Report Slave ID (0x11)   * Address * Slave ID  * Berlios ModBus Stack ** The modbus stack is config'd in {color:#0000ff}mbconfig.h{color} which is located in vpc\modbus\include \\ \\ ---- h3. Debugging MSP430 h4. Starting gdbproxy The next step is starting gdbproxy, which is responsible for the communication between GDB and the FET: msp430-gdbproxy \--port=2000 msp430 If your FET is properly connected to the parallel port, you should see a message like the following: info: msp430: Target device is a 'MSP430F12x' (type 11) notice: msp430-gdbproxy: waiting on TCP port 2000 h4. Using Insight (Windows) After you have started Insight (c:\msp430\bin\msp430-gdb.exe), click on "File->Open" and select the elf-file (e.g. "test.elf") you want to debug. Now click on "Run->Connect to target" and enter the following settings: Target: "Remote/TCP" Hostname: "localhost" Port: "2000" Set breakpoint at 'main': yes Set breakpoint at 'exit': yes Attach to target: yes Download Program: yes Command after attaching: "monitor erase all" Run Method: Continue from last Stop When you click on "Ok" Insight should tell you that the connection was successful, and gdbproxy should say "notice: msp430-gdbproxy: connected". To start the debugging click on "Run" or simply press "r". If everything worked correctly you should now see the sourcecode of your program with the first line of main() marked green. The red point is the breakpoint that has been set by Insight automatically. You can set or remove breakpoints by clicking on the '-' in front of the line. Now you can 'c'ontinue the execution to the next breakpoint, 's'tep through the code, or step a single assembler instruction... but be careful with "finish": Insight sometimes seems to lock up with this command. So if you want to finish a function, I recommend setting a breakpoint to the end of the function and using "continue". \\ h2. Installing the Compiler Tool Chain To obtain and install the compiler: # Go to the MSPGCC download page and obtain the latest MSPGCC installation. I used the 'mspgcc-20040723.exe' download which installed everything I needed for a Win32 setup. \\ # This step need only be performed if you wish to use the graphical version of GDB. The latest MSPGCC download only includes the command line GDB debugger. I prefer to use the graphical version called Insight. A slightly older prebuilt version of Insight can be used. Install this older version of insight into a different directory to that chosen for the latest MSPGCC installation as you don't want to overwrite the files obtained in step 1. \\ You should now have two installations. The latest version of MSPGCC installed during step 1, and a slightly older version of Insight from step 2. Both versions of the GDB debugger are called msp430-gdb.exe so one needs to be renamed. Locate the older version msp430-gdb.exe from the files installed during this step and rename it msp430-insight.exe. \\ # Ensure the BIN directory from the files installed during step 1 and the BIN directory from the files installed during step 2 are included in your PATH environment variable. \\ \\ # The MSPGCC download includes a program called msp430-gdbproxy.exe. This intercepts the GDB TCP commands and redirects them to the parallel port. Start msp430-gdbproxy (a shortcut to this will have been placed on the start menu when MSPGCC was installed). By default msp430-gdbproxy uses port 3333 - do not change this. \\ # Program the flash as per the instruction in the section above. The flash can be programmed from within GDB but it is much faster to do it separately and beforehand. \\ # Start the debugger using the command ... msp430-insight a.out... the commands in the gdb.ini file will do the rest. If you prefer to use the command line debugger simply replace msp430-insight with msp430-gdb. \\ # Insight will start at and the program will stop at the breakpoint in main() as shown below. \\ MSP430 Clocking \\ MSP430 Basic Clock Module * Clock Signals: ** *ACLK*: Auxiliary clock. The signal is sourced from LFXT1CLK with a divider of 1, 2, 4, or 8. (The calibration program for the serial link sets the divider to 4, but after the calibration it can be changed to any other values.) ACLK can be used as the clock signal for Timer A and Timer B. ** *MCLK*: Master clock. The signal can be sourced from LFXT1CLK, XT2CLK (if available), or DCOCLK with a divider of 1, 2, 4, or 8. MCLK is used by the CPU and system. ** *SMCLK*: Sub-main clock. The signal is sourced from either XT2CLK (if available), or DCOCLK with a divider of 1, 2, 4, or 8. SMCLK can be used as the clock signal for Timer A and Timer B. * MSP430 Clocking pictorial: *   * \\ !MSP430_clocking2.JPG!                  !MSP430_BCSCTL1.JPG! !MSP430_BCSCTL2.JPG!\\ \\]]> 6258995 6226218 D0 52.08 52.08 \+0 \+0.00 D0->D1 104.17 104.17 \+0 \+0.00 D1->D2 156.25 156.25 \+0 \+0.00 D2->D3 208.33 208.33 \+0 \+0.00 D3->D4 260.42 260.42 \+0 \+0.00 D4->D5 312.50 312.50 \+0 \+0.00 D5->D6 364.58 364.58 \+0 \+0.00 D6->D7 416.67 416.67 \+0 \+0.00 D7->stopbit 468.75 468.75 \+0 \+0.00 end of stopb 520.83 520.83 \+0 \+0.00 \*/ UBR00=0xC0; UBR10=0x00; UMCTL0=0x00; /\* uart0 3686400Hz 19200bps \*/ UBR01=0xC0; UBR11=0x00; UMCTL1=0x00; /\* uart1 3686400Hz 19200bps \*/ h4. The simplest way to use the USART in UART mode is this: interrupt is not enabled, the software checks if it can output the next byte (UTXIFG = 1), and if a new character has been received (URXIFG = 1). \\ h4. Modbus Register Map * REG_INPUT_START         512         // input registers start at 512 * REG_INPUT_NREGS         8           // 8x16 bit registers * REG_SOLENOIDS_A        0            // Holding registers start at 0 (16 coils for each A and B) * REG_SOLENOIDS_B        1   * REG_HOLDING_START    0           // to match WAGO * REG_HOLDING_NREGS   40         // 40 is more than actual (2) * REG_COILS_START         0           // read individual coils (was 1000) * REG_COILS_SIZE           32          // 32 coils * REG_DISC_START          0           // discrete (was 1000) * REG_DISC_SIZE             32          // 32 coils \\ h3. ---- MODBUS * Commands ** Read Input Register (0x04) ** Read Holding Registers (0x03) ** Write Single Register (0x06) ** Write Multiple Registers (0x10) ** Read/Write Multiple Registers (0x17) ** Read Coils (0x01) ** Write Single Coil (0x05) ** Write Multiple Coils (0x0F) ** Read Discrete Inputs (0x02) ** Report Slave ID (0x11)   * Address * Slave ID  * Berlios ModBus Stack ** The modbus stack is config'd in {color:#0000ff}mbconfig.h{color} which is located in vpc\modbus\include \\ \\ ---- h3. Debugging MSP430 h4. Starting gdbproxy The next step is starting gdbproxy, which is responsible for the communication between GDB and the FET: msp430-gdbproxy \--port=2000 msp430 If your FET is properly connected to the parallel port, you should see a message like the following: info: msp430: Target device is a 'MSP430F12x' (type 11) notice: msp430-gdbproxy: waiting on TCP port 2000 h4. Using Insight (Windows) After you have started Insight (c:\msp430\bin\msp430-gdb.exe), click on "File->Open" and select the elf-file (e.g. "test.elf") you want to debug. Now click on "Run->Connect to target" and enter the following settings: Target: "Remote/TCP" Hostname: "localhost" Port: "2000" Set breakpoint at 'main': yes Set breakpoint at 'exit': yes Attach to target: yes Download Program: yes Command after attaching: "monitor erase all" Run Method: Continue from last Stop When you click on "Ok" Insight should tell you that the connection was successful, and gdbproxy should say "notice: msp430-gdbproxy: connected". To start the debugging click on "Run" or simply press "r". If everything worked correctly you should now see the sourcecode of your program with the first line of main() marked green. The red point is the breakpoint that has been set by Insight automatically. You can set or remove breakpoints by clicking on the '-' in front of the line. Now you can 'c'ontinue the execution to the next breakpoint, 's'tep through the code, or step a single assembler instruction... but be careful with "finish": Insight sometimes seems to lock up with this command. So if you want to finish a function, I recommend setting a breakpoint to the end of the function and using "continue". \\ h2. Installing the Compiler Tool Chain To obtain and install the compiler: # Go to the MSPGCC download page and obtain the latest MSPGCC installation. I used the 'mspgcc-20040723.exe' download which installed everything I needed for a Win32 setup. \\ # This step need only be performed if you wish to use the graphical version of GDB. The latest MSPGCC download only includes the command line GDB debugger. I prefer to use the graphical version called Insight. A slightly older prebuilt version of Insight can be used. Install this older version of insight into a different directory to that chosen for the latest MSPGCC installation as you don't want to overwrite the files obtained in step 1. \\ You should now have two installations. The latest version of MSPGCC installed during step 1, and a slightly older version of Insight from step 2. Both versions of the GDB debugger are called msp430-gdb.exe so one needs to be renamed. Locate the older version msp430-gdb.exe from the files installed during this step and rename it msp430-insight.exe. \\ # Ensure the BIN directory from the files installed during step 1 and the BIN directory from the files installed during step 2 are included in your PATH environment variable. \\ \\ # The MSPGCC download includes a program called msp430-gdbproxy.exe. This intercepts the GDB TCP commands and redirects them to the parallel port. Start msp430-gdbproxy (a shortcut to this will have been placed on the start menu when MSPGCC was installed). By default msp430-gdbproxy uses port 3333 - do not change this. \\ # Program the flash as per the instruction in the section above. The flash can be programmed from within GDB but it is much faster to do it separately and beforehand. \\ # Start the debugger using the command ... msp430-insight a.out... the commands in the gdb.ini file will do the rest. If you prefer to use the command line debugger simply replace msp430-insight with msp430-gdb. \\ # Insight will start at and the program will stop at the breakpoint in main() as shown below. \\ MSP430 Clocking \\ MSP430 Basic Clock Module * Clock Signals: ** *ACLK*: Auxiliary clock. The signal is sourced from LFXT1CLK with a divider of 1, 2, 4, or 8. (The calibration program for the serial link sets the divider to 4, but after the calibration it can be changed to any other values.) ACLK can be used as the clock signal for Timer A and Timer B. ** *MCLK*: Master clock. The signal can be sourced from LFXT1CLK, XT2CLK (if available), or DCOCLK with a divider of 1, 2, 4, or 8. MCLK is used by the CPU and system. ** *SMCLK*: Sub-main clock. The signal is sourced from either XT2CLK (if available), or DCOCLK with a divider of 1, 2, 4, or 8. SMCLK can be used as the clock signal for Timer A and Timer B. * MSP430 Clocking pictorial: *   * \\ !MSP430_clocking2.JPG!                  !MSP430_BCSCTL1.JPG! !MSP430_BCSCTL2.JPG!\\ \\]]> 6258997 10388957 10356239 10388959 10356241 10388954 10356235 10388988 10356270 10388990 10356272 10388989 10356271 10388991 @kahuna.shore.mbari.org/svn/repos/MBARItracking/trunk MBARItracking {noformat} where is your account name on kahuna. This package has be checked out to the following accounts on pismo.shore.mbari.org into the \~/dev directory (the password is the same for all these accounts - ask Mike McCann or Pat Allen for it): * m1track * m2track * shiptrack * aistrack * auvtrack  Please refer to the README files in the package for further details on the implementation.  For example here is the current version of the README file in the scripts directory: {noformat} scripts folder of the MBARItracking project =========================================== $Id: README 5246 2009-07-08 18:14:29Z mccann $ The scripts here populate the MBARItracking database with position data. The various scripts are implemented in various ways from various accounts as indicated below: Script Account Implementation ------ ------- -------------- grabShipPosition.py shiptrack Connect to socket, parse $GPRMC, insert to DB, write to log file shipWatchdog.py shiptrack Check log file like: 0,10,20,30,40,50 * * * * /shipWatchdog.py grabAISposition.py aistrack Connect to socket, parse AIS, insert to DB, write to log file aisWatchdog.py aistrack Check log file like: 0,10,20,30,40,50 * * * * /aisWatchdog.py grabOasisTrackers.pl m1track Symlinked by grabM{1,2}tracker.pl, in .forward file, parse MIME m2track messages from email sent from Iridium modems, insert to DB. {noformat} To monitor the successful operation of this system open this link in Google Earth: [http://elvis.shore.mbari.org/tracking/viewTracking.kml|Should launch GoogleEarth on your system] (This link is on our public web site on the "Today in the Bay" web page: [http://www.mbari.org/cruises/all/plot/all700.html|http://www.mbari.org/cruises/all/plot/all700.html ]). If you can see data for the last hour then the real-time feeds and database are operating. \-\- Mike McCann 23 July 2009]]> 10356273 10388993 10356275 10388979 10356261 10388982 10356264 26673154 ** response ** 0 * Channel 1 Power Control = 0 (Off) ** $1PC0 ** Response: ** 0 * Channel 1 Power Control = 1 (On) ** $1PC1 ** Response: ** 1 * Channel 1 Power Read ** $1PR ** Response: ** 1 * Read Block ** $1RB read temperature sensor block (4 channels) ** $5RB read pH sensor block (Seabird 18s) ** Response: ** \*+02712.00 ** \*+00200.00 ** \*+00125.76 ** \*+00347.95 * Read Data ** $1RD read tDGH channel 1 (temperature ch 1) ** $2RD read tDGH channel 2 (temperature ch 2) ** $3RD read tDGH channel 3 (temperature ch 3) ** $4RD read tDGH channel 4 (temperature ch 4) ** $5RD read tDGH channel 5 (pH sensor ch 1) ** $6RD read tDGH channel 6 (pH sensor ch 2) ** $7RD read tDGH channel 7 (pH sensor ch 3) ** $8RD read tDGH channel 8 (pH sensor ch 4) ** $9RD read tDGH channel 9 (pH sensor ch 5)]]> 26640386 10388981 10356263 10388984 10356266 10388986 10356268 3670778 3638031 6226248 6259028 3670773 3638026 3670783 3638036 6226255 6259035 3670781 3638034 6226634 6259432 6226636 6259434 6226638 6259436 6226640 6259438 6226642 6259440 3670400 3637645 6226644 6259442 5406865 Open" and select the elf-file (e.g. "test.elf") you want to debug. Now click on "Run->Connect to target" and enter the following settings: Target: "Remote/TCP" Hostname: "localhost" Port: "2000" Set breakpoint at 'main': yes Set breakpoint at 'exit': yes Attach to target: yes Download Program: yes Command after attaching: "monitor erase all" Run Method: Continue from last Stop When you click on "Ok" Insight should tell you that the connection was successful, and gdbproxy should say "notice: msp430-gdbproxy: connected". To start the debugging click on "Run" or simply press "r". If everything worked correctly you should now see the sourcecode of your program with the first line of main() marked green. The red point is the breakpoint that has been set by Insight automatically. You can set or remove breakpoints by clicking on the '-' in front of the line. Now you can 'c'ontinue the execution to the next breakpoint, 's'tep through the code, or step a single assembler instruction... but be careful with "finish": Insight sometimes seems to lock up with this command. So if you want to finish a function, I recommend setting a breakpoint to the end of the function and using "continue". \\ h2. Installing the Compiler Tool Chain To obtain and install the compiler: # Go to the MSPGCC download page and obtain the latest MSPGCC installation. I used the 'mspgcc-20040723.exe' download which installed everything I needed for a Win32 setup. \\ # This step need only be performed if you wish to use the graphical version of GDB. The latest MSPGCC download only includes the command line GDB debugger. I prefer to use the graphical version called Insight. A slightly older prebuilt version of Insight can be used. Install this older version of insight into a different directory to that chosen for the latest MSPGCC installation as you don't want to overwrite the files obtained in step 1. \\ You should now have two installations. The latest version of MSPGCC installed during step 1, and a slightly older version of Insight from step 2. Both versions of the GDB debugger are called msp430-gdb.exe so one needs to be renamed. Locate the older version msp430-gdb.exe from the files installed during this step and rename it msp430-insight.exe. \\ # Ensure the BIN directory from the files installed during step 1 and the BIN directory from the files installed during step 2 are included in your PATH environment variable. \\ \\ # The MSPGCC download includes a program called msp430-gdbproxy.exe. This intercepts the GDB TCP commands and redirects them to the parallel port. Start msp430-gdbproxy (a shortcut to this will have been placed on the start menu when MSPGCC was installed). By default msp430-gdbproxy uses port 3333 - do not change this. \\ # Program the flash as per the instruction in the section above. The flash can be programmed from within GDB but it is much faster to do it separately and beforehand. \\ # Start the debugger using the command ... msp430-insight a.out... the commands in the gdb.ini file will do the rest. If you prefer to use the command line debugger simply replace msp430-insight with msp430-gdb. \\ # Insight will start at and the program will stop at the breakpoint in main() as shown below. \\ MSP430 Clocking \\ MSP430 Basic Clock Module * Clock Signals: ** *ACLK*: Auxiliary clock. The signal is sourced from LFXT1CLK with a divider of 1, 2, 4, or 8. (The calibration program for the serial link sets the divider to 4, but after the calibration it can be changed to any other values.) ACLK can be used as the clock signal for Timer A and Timer B. ** *MCLK*: Master clock. The signal can be sourced from LFXT1CLK, XT2CLK (if available), or DCOCLK with a divider of 1, 2, 4, or 8. MCLK is used by the CPU and system. ** *SMCLK*: Sub-main clock. The signal is sourced from either XT2CLK (if available), or DCOCLK with a divider of 1, 2, 4, or 8. SMCLK can be used as the clock signal for Timer A and Timer B. * MSP430 Clocking pictorial: *   * \\ !MSP430_clocking2.JPG!                  !MSP430_BCSCTL1.JPG! !MSP430_BCSCTL2.JPG!\\ \\]]> 5374115 6226646 6259444 6226648 6259446 6226650 6259448 6226652 6259450 6226653 6259451 3670355 3637600 3670357 3637602 3670359 3637604 3670360 3637605 3670361 3637606 3670362 3637607 3670364 3637609 3670365 3637610 3670368 3637613 3670339 3637584 3670341 3637586 3670343 3637588 3670346 3637591 3670345 3637590 3670348 3637593 3670347 3637592 3670350 3637595 3670349 3637594 3670352 3637597 3670351 3637596 3670354 3637599 3670353 3637598 3670330 3637575 3670328 3637573 3670326 3637571 3670337 3637582 3670336 3637581 3670334 3637579 3670332 3637577 3670314 3637559 3670309 3637554 3670320 3637565 3670318 3637563 3670316 3637561 3670295 3637540 3670296 3637541 3670298 3637543 3670291 3637536 3670293 3637538 3670303 3637548 3670305 3637550 3670300 3637545 3670302 3637547 6226613 6259412 3670287 3637532 3670285 3637530 8290318 2 3114598 2008-12-26 21:20:30.000 2008-12-26 21:20:30.000 5406724 Open" and select the elf-file (e.g. "test.elf") you want to debug. Now click on "Run->Connect to target" and enter the following settings: Target: "Remote/TCP" Hostname: "localhost" Port: "2000" Set breakpoint at 'main': yes Set breakpoint at 'exit': yes Attach to target: yes Download Program: yes Command after attaching: "monitor erase all" Run Method: Continue from last Stop When you click on "Ok" Insight should tell you that the connection was successful, and gdbproxy should say "notice: msp430-gdbproxy: connected". To start the debugging click on "Run" or simply press "r". If everything worked correctly you should now see the sourcecode of your program with the first line of main() marked green. The red point is the breakpoint that has been set by Insight automatically. You can set or remove breakpoints by clicking on the '-' in front of the line. Now you can 'c'ontinue the execution to the next breakpoint, 's'tep through the code, or step a single assembler instruction... but be careful with "finish": Insight sometimes seems to lock up with this command. So if you want to finish a function, I recommend setting a breakpoint to the end of the function and using "continue". ]]> 5373956 16810134 16777371 3670484 3637731 3670483 3637730 3670486 3637733 3670488 3637735 3670490 3637737 3670489 3637736 5406806 Open" and select the elf-file (e.g. "test.elf") you want to debug. Now click on "Run->Connect to target" and enter the following settings: Target: "Remote/TCP" Hostname: "localhost" Port: "2000" Set breakpoint at 'main': yes Set breakpoint at 'exit': yes Attach to target: yes Download Program: yes Command after attaching: "monitor erase all" Run Method: Continue from last Stop When you click on "Ok" Insight should tell you that the connection was successful, and gdbproxy should say "notice: msp430-gdbproxy: connected". To start the debugging click on "Run" or simply press "r". If everything worked correctly you should now see the sourcecode of your program with the first line of main() marked green. The red point is the breakpoint that has been set by Insight automatically. You can set or remove breakpoints by clicking on the '-' in front of the line. Now you can 'c'ontinue the execution to the next breakpoint, 's'tep through the code, or step a single assembler instruction... but be careful with "finish": Insight sometimes seems to lock up with this command. So if you want to finish a function, I recommend setting a breakpoint to the end of the function and using "continue". ]]> 5374051 5406815 Open" and select the elf-file (e.g. "test.elf") you want to debug. Now click on "Run->Connect to target" and enter the following settings: Target: "Remote/TCP" Hostname: "localhost" Port: "2000" Set breakpoint at 'main': yes Set breakpoint at 'exit': yes Attach to target: yes Download Program: yes Command after attaching: "monitor erase all" Run Method: Continue from last Stop When you click on "Ok" Insight should tell you that the connection was successful, and gdbproxy should say "notice: msp430-gdbproxy: connected". To start the debugging click on "Run" or simply press "r". If everything worked correctly you should now see the sourcecode of your program with the first line of main() marked green. The red point is the breakpoint that has been set by Insight automatically. You can set or remove breakpoints by clicking on the '-' in front of the line. Now you can 'c'ontinue the execution to the next breakpoint, 's'tep through the code, or step a single assembler instruction... but be careful with "finish": Insight sometimes seems to lock up with this command. So if you want to finish a function, I recommend setting a breakpoint to the end of the function and using "continue". \\ h2. Installing the Compiler Tool Chain To obtain and install the compiler: # Go to the MSPGCC download page and obtain the latest MSPGCC installation. I used the 'mspgcc-20040723.exe' download which installed everything I needed for a Win32 setup. \\ # This step need only be performed if you wish to use the graphical version of GDB. The latest MSPGCC download only includes the command line GDB debugger. I prefer to use the graphical version called Insight. A slightly older prebuilt version of Insight can be used. Install this older version of insight into a different directory to that chosen for the latest MSPGCC installation as you don't want to overwrite the files obtained in step 1. \\ You should now have two installations. The latest version of MSPGCC installed during step 1, and a slightly older version of Insight from step 2. Both versions of the GDB debugger are called msp430-gdb.exe so one needs to be renamed. Locate the older version msp430-gdb.exe from the files installed during this step and rename it msp430-insight.exe. \\ # Ensure the BIN directory from the files installed during step 1 and the BIN directory from the files installed during step 2 are included in your PATH environment variable. \\ \\ # The MSPGCC download includes a program called msp430-gdbproxy.exe. This intercepts the GDB TCP commands and redirects them to the parallel port. Start msp430-gdbproxy (a shortcut to this will have been placed on the start menu when MSPGCC was installed). By default msp430-gdbproxy uses port 3333 - do not change this. \\ # Program the flash as per the instruction in the section above. The flash can be programmed from within GDB but it is much faster to do it separately and beforehand. \\ # Start the debugger using the command ... msp430-insight a.out... the commands in the gdb.ini file will do the rest. If you prefer to use the command line debugger simply replace msp430-insight with msp430-gdb. \\ # Insight will start at and the program will stop at the breakpoint in main() as shown below. ]]> 5374060 5406817 Open" and select the elf-file (e.g. "test.elf") you want to debug. Now click on "Run->Connect to target" and enter the following settings: Target: "Remote/TCP" Hostname: "localhost" Port: "2000" Set breakpoint at 'main': yes Set breakpoint at 'exit': yes Attach to target: yes Download Program: yes Command after attaching: "monitor erase all" Run Method: Continue from last Stop When you click on "Ok" Insight should tell you that the connection was successful, and gdbproxy should say "notice: msp430-gdbproxy: connected". To start the debugging click on "Run" or simply press "r". If everything worked correctly you should now see the sourcecode of your program with the first line of main() marked green. The red point is the breakpoint that has been set by Insight automatically. You can set or remove breakpoints by clicking on the '-' in front of the line. Now you can 'c'ontinue the execution to the next breakpoint, 's'tep through the code, or step a single assembler instruction... but be careful with "finish": Insight sometimes seems to lock up with this command. So if you want to finish a function, I recommend setting a breakpoint to the end of the function and using "continue". \\ h2. Installing the Compiler Tool Chain To obtain and install the compiler: # Go to the MSPGCC download page and obtain the latest MSPGCC installation. I used the 'mspgcc-20040723.exe' download which installed everything I needed for a Win32 setup. \\ # This step need only be performed if you wish to use the graphical version of GDB. The latest MSPGCC download only includes the command line GDB debugger. I prefer to use the graphical version called Insight. A slightly older prebuilt version of Insight can be used. Install this older version of insight into a different directory to that chosen for the latest MSPGCC installation as you don't want to overwrite the files obtained in step 1. \\ You should now have two installations. The latest version of MSPGCC installed during step 1, and a slightly older version of Insight from step 2. Both versions of the GDB debugger are called msp430-gdb.exe so one needs to be renamed. Locate the older version msp430-gdb.exe from the files installed during this step and rename it msp430-insight.exe. \\ # Ensure the BIN directory from the files installed during step 1 and the BIN directory from the files installed during step 2 are included in your PATH environment variable. \\ \\ # The MSPGCC download includes a program called msp430-gdbproxy.exe. This intercepts the GDB TCP commands and redirects them to the parallel port. Start msp430-gdbproxy (a shortcut to this will have been placed on the start menu when MSPGCC was installed). By default msp430-gdbproxy uses port 3333 - do not change this. \\ # Program the flash as per the instruction in the section above. The flash can be programmed from within GDB but it is much faster to do it separately and beforehand. \\ # Start the debugger using the command ... msp430-insight a.out... the commands in the gdb.ini file will do the rest. If you prefer to use the command line debugger simply replace msp430-insight with msp430-gdb. \\ # Insight will start at and the program will stop at the breakpoint in main() as shown below.\\ MSP430 Clocking\\ MSP430 Basic Clock Module * Clock Signals: ** *ACLK*: Auxiliary clock. The signal is sourced from LFXT1CLK with a divider of 1, 2, 4, or 8. (The calibration program for the serial link sets the divider to 4, but after the calibration it can be changed to any other values.) ACLK can be used as the clock signal for Timer A and Timer B. ** *MCLK*: Master clock. The signal can be sourced from LFXT1CLK, XT2CLK (if available), or DCOCLK with a divider of 1, 2, 4, or 8. MCLK is used by the CPU and system. ** *SMCLK*: Sub-main clock. The signal is sourced from either XT2CLK (if available), or DCOCLK with a divider of 1, 2, 4, or 8. SMCLK can be used as the clock signal for Timer A and Timer B. * MSP430 Clocking pictorial !MSP430_clocking2.JPG!  \\]]> 5374062 5406788 5374029 16810203 16777442 16810205 16777444 5406789 5374030 16810207 16777446 16810209 16777448 3670442 3637687 16810197 16777436 3670440 3637685 16810199 16777438 16810201 16777440 16810219 16777458 6226478 6259268 16810213 16777452 16810211 16777450 16810217 16777456 16810215 16777454 3670415 3637660 3670416 3637661 3670417 3637662 19072761 19040042 5406825 5374070 5406823 Open" and select the elf-file (e.g. "test.elf") you want to debug. Now click on "Run->Connect to target" and enter the following settings: Target: "Remote/TCP" Hostname: "localhost" Port: "2000" Set breakpoint at 'main': yes Set breakpoint at 'exit': yes Attach to target: yes Download Program: yes Command after attaching: "monitor erase all" Run Method: Continue from last Stop When you click on "Ok" Insight should tell you that the connection was successful, and gdbproxy should say "notice: msp430-gdbproxy: connected". To start the debugging click on "Run" or simply press "r". If everything worked correctly you should now see the sourcecode of your program with the first line of main() marked green. The red point is the breakpoint that has been set by Insight automatically. You can set or remove breakpoints by clicking on the '-' in front of the line. Now you can 'c'ontinue the execution to the next breakpoint, 's'tep through the code, or step a single assembler instruction... but be careful with "finish": Insight sometimes seems to lock up with this command. So if you want to finish a function, I recommend setting a breakpoint to the end of the function and using "continue". \\ h2. Installing the Compiler Tool Chain To obtain and install the compiler: # Go to the MSPGCC download page and obtain the latest MSPGCC installation. I used the 'mspgcc-20040723.exe' download which installed everything I needed for a Win32 setup. \\ # This step need only be performed if you wish to use the graphical version of GDB. The latest MSPGCC download only includes the command line GDB debugger. I prefer to use the graphical version called Insight. A slightly older prebuilt version of Insight can be used. Install this older version of insight into a different directory to that chosen for the latest MSPGCC installation as you don't want to overwrite the files obtained in step 1. \\ You should now have two installations. The latest version of MSPGCC installed during step 1, and a slightly older version of Insight from step 2. Both versions of the GDB debugger are called msp430-gdb.exe so one needs to be renamed. Locate the older version msp430-gdb.exe from the files installed during this step and rename it msp430-insight.exe. \\ # Ensure the BIN directory from the files installed during step 1 and the BIN directory from the files installed during step 2 are included in your PATH environment variable. \\ \\ # The MSPGCC download includes a program called msp430-gdbproxy.exe. This intercepts the GDB TCP commands and redirects them to the parallel port. Start msp430-gdbproxy (a shortcut to this will have been placed on the start menu when MSPGCC was installed). By default msp430-gdbproxy uses port 3333 - do not change this. \\ # Program the flash as per the instruction in the section above. The flash can be programmed from within GDB but it is much faster to do it separately and beforehand. \\ # Start the debugger using the command ... msp430-insight a.out... the commands in the gdb.ini file will do the rest. If you prefer to use the command line debugger simply replace msp430-insight with msp430-gdb. \\ # Insight will start at and the program will stop at the breakpoint in main() as shown below. \\ MSP430 Clocking \\ MSP430 Basic Clock Module * Clock Signals: ** *ACLK*: Auxiliary clock. The signal is sourced from LFXT1CLK with a divider of 1, 2, 4, or 8. (The calibration program for the serial link sets the divider to 4, but after the calibration it can be changed to any other values.) ACLK can be used as the clock signal for Timer A and Timer B. ** *MCLK*: Master clock. The signal can be sourced from LFXT1CLK, XT2CLK (if available), or DCOCLK with a divider of 1, 2, 4, or 8. MCLK is used by the CPU and system. ** *SMCLK*: Sub-main clock. The signal is sourced from either XT2CLK (if available), or DCOCLK with a divider of 1, 2, 4, or 8. SMCLK can be used as the clock signal for Timer A and Timer B. * MSP430 Clocking pictorial: *   *  \\ !MSP430_clocking2.JPG!                  !MSP430_BCSCTL1.JPG! !MSP430_BCSCTL2.JPG!\\   \\]]> 5374068 19072765 19040046 5406829 5374075 5406827 5374073 19072767 19040048 19072802 19040084 19072800 19040082 19072798 19040080 19072796 19040078 19072794 19040076 19072792 19040074 19072790 19040072 19072789 19040071 19072787 19040069 19072785 19040067 19072786 19040068 19072783 19040065 19072781 19040063 19072779 19040061 19072777 19040059 19072778 19040060 19072775 19040057 19072773 19040055 19072771 19040052 3670086 3637323 11272373 11239608 3670083 3637318 11272377 11239612 11272375 11239610 3670094 3637332 11272382 Serial Port->usbserial-A9006R0V. I set the communication settings to 115200, No flow control. Then I opened up a connection by selecting Connection->Open Connection. Nothing seems to happen, but if you then plug the 5V power adapter into the board, you should see the boot sequence start. It takes quite a bit of time for the Angstrom kernel to start up (like several minutes). Eventually, the login prompt will come up and you can login as root (no password).]]> 11239617 11272380 Serial Port->usbserial-A9006R0V. I set the communication settings to 115200, No flow control. Then I opened up a connection by selecting Connection->Open Connection. Nothing seems to happen, but if you then plug the 5V power adapter into the board, you should see the boot sequence start. It takes quite a bit of time for the Angstrom kernel to start up (like several minutes).]]> 11239615 11272379 11239614 3670096 3637335 3670095 3637333 5407168 D0 52.08 52.08 \+0 \+0.00 D0->D1 104.17 104.17 \+0 \+0.00 D1->D2 156.25 156.25 \+0 \+0.00 D2->D3 208.33 208.33 \+0 \+0.00 D3->D4 260.42 260.42 \+0 \+0.00 D4->D5 312.50 312.50 \+0 \+0.00 D5->D6 364.58 364.58 \+0 \+0.00 D6->D7 416.67 416.67 \+0 \+0.00 D7->stopbit 468.75 468.75 \+0 \+0.00 end of stopb 520.83 520.83 \+0 \+0.00 \*/ UBR00=0xC0; UBR10=0x00; UMCTL0=0x00; /\* uart0 3686400Hz 19200bps \*/ UBR01=0xC0; UBR11=0x00; UMCTL1=0x00; /\* uart1 3686400Hz 19200bps \*/ h4. The simplest way to use the USART in UART mode is this: interrupt is not enabled, the software checks if it can output the next byte (UTXIFG = 1), and if a new character has been received (URXIFG = 1). \\ h4. Modbus Register Map * REG_INPUT_START         512         // input registers start at 512 * REG_INPUT_NREGS         8           // 8x16 bit registers * REG_SOLENOIDS_A        0            // Holding registers start at 0 (16 coils for each A and B) * REG_SOLENOIDS_B        1   * REG_HOLDING_START    0           // to match WAGO * REG_HOLDING_NREGS   40         // 40 is more than actual (2) * REG_COILS_START         0           // read individual coils (was 1000) * REG_COILS_SIZE           32          // 32 coils * REG_DISC_START          0           // discrete (was 1000) * REG_DISC_SIZE             32          // 32 coils \\ h3. ---- MODBUS * Commands ** Read Input Register (0x04) ** Read Holding Registers (0x03) ** Write Single Register (0x06) ** Write Multiple Registers (0x10) ** Read/Write Multiple Registers (0x17) ** Read Coils (0x01) ** Write Single Coil (0x05) ** Write Multiple Coils (0x0F) ** Read Discrete Inputs (0x02) ** Report Slave ID (0x11)   * Address * Slave ID  * Berlios ModBus Stack ** The modbus stack is config'd in {color:#0000ff}mbconfig.h{color} which is located in vpc\modbus\include \\ \\ ---- h3. Debugging MSP430 h4. Starting gdbproxy The next step is starting gdbproxy, which is responsible for the communication between GDB and the FET: msp430-gdbproxy \--port=2000 msp430 If your FET is properly connected to the parallel port, you should see a message like the following: info: msp430: Target device is a 'MSP430F12x' (type 11) notice: msp430-gdbproxy: waiting on TCP port 2000 h4. Using Insight (Windows) After you have started Insight (c:\msp430\bin\msp430-gdb.exe), click on "File->Open" and select the elf-file (e.g. "test.elf") you want to debug. Now click on "Run->Connect to target" and enter the following settings: Target: "Remote/TCP" Hostname: "localhost" Port: "2000" Set breakpoint at 'main': yes Set breakpoint at 'exit': yes Attach to target: yes Download Program: yes Command after attaching: "monitor erase all" Run Method: Continue from last Stop When you click on "Ok" Insight should tell you that the connection was successful, and gdbproxy should say "notice: msp430-gdbproxy: connected". To start the debugging click on "Run" or simply press "r". If everything worked correctly you should now see the sourcecode of your program with the first line of main() marked green. The red point is the breakpoint that has been set by Insight automatically. You can set or remove breakpoints by clicking on the '-' in front of the line. Now you can 'c'ontinue the execution to the next breakpoint, 's'tep through the code, or step a single assembler instruction... but be careful with "finish": Insight sometimes seems to lock up with this command. So if you want to finish a function, I recommend setting a breakpoint to the end of the function and using "continue". \\ h2. Installing the Compiler Tool Chain To obtain and install the compiler: # Go to the MSPGCC download page and obtain the latest MSPGCC installation. I used the 'mspgcc-20040723.exe' download which installed everything I needed for a Win32 setup. \\ # This step need only be performed if you wish to use the graphical version of GDB. The latest MSPGCC download only includes the command line GDB debugger. I prefer to use the graphical version called Insight. A slightly older prebuilt version of Insight can be used. Install this older version of insight into a different directory to that chosen for the latest MSPGCC installation as you don't want to overwrite the files obtained in step 1. \\ You should now have two installations. The latest version of MSPGCC installed during step 1, and a slightly older version of Insight from step 2. Both versions of the GDB debugger are called msp430-gdb.exe so one needs to be renamed. Locate the older version msp430-gdb.exe from the files installed during this step and rename it msp430-insight.exe. \\ # Ensure the BIN directory from the files installed during step 1 and the BIN directory from the files installed during step 2 are included in your PATH environment variable. \\ \\ # The MSPGCC download includes a program called msp430-gdbproxy.exe. This intercepts the GDB TCP commands and redirects them to the parallel port. Start msp430-gdbproxy (a shortcut to this will have been placed on the start menu when MSPGCC was installed). By default msp430-gdbproxy uses port 3333 - do not change this. \\ # Program the flash as per the instruction in the section above. The flash can be programmed from within GDB but it is much faster to do it separately and beforehand. \\ # Start the debugger using the command ... msp430-insight a.out... the commands in the gdb.ini file will do the rest. If you prefer to use the command line debugger simply replace msp430-insight with msp430-gdb. \\ # Insight will start at and the program will stop at the breakpoint in main() as shown below. \\ MSP430 Clocking \\ MSP430 Basic Clock Module * Clock Signals: ** *ACLK*: Auxiliary clock. The signal is sourced from LFXT1CLK with a divider of 1, 2, 4, or 8. (The calibration program for the serial link sets the divider to 4, but after the calibration it can be changed to any other values.) ACLK can be used as the clock signal for Timer A and Timer B. ** *MCLK*: Master clock. The signal can be sourced from LFXT1CLK, XT2CLK (if available), or DCOCLK with a divider of 1, 2, 4, or 8. MCLK is used by the CPU and system. ** *SMCLK*: Sub-main clock. The signal is sourced from either XT2CLK (if available), or DCOCLK with a divider of 1, 2, 4, or 8. SMCLK can be used as the clock signal for Timer A and Timer B. * MSP430 Clocking pictorial: *   * \\ !MSP430_clocking2.JPG!                  !MSP430_BCSCTL1.JPG! !MSP430_BCSCTL2.JPG!\\ \\]]> 5374432 5407167 D0 52.08 52.08 \+0 \+0.00 D0->D1 104.17 104.17 \+0 \+0.00 D1->D2 156.25 156.25 \+0 \+0.00 D2->D3 208.33 208.33 \+0 \+0.00 D3->D4 260.42 260.42 \+0 \+0.00 D4->D5 312.50 312.50 \+0 \+0.00 D5->D6 364.58 364.58 \+0 \+0.00 D6->D7 416.67 416.67 \+0 \+0.00 D7->stopbit 468.75 468.75 \+0 \+0.00 end of stopb 520.83 520.83 \+0 \+0.00 \*/ UBR00=0xC0; UBR10=0x00; UMCTL0=0x00; /\* uart0 3686400Hz 19200bps \*/ UBR01=0xC0; UBR11=0x00; UMCTL1=0x00; /\* uart1 3686400Hz 19200bps \*/ h4. The simplest way to use the USART in UART mode is this: interrupt is not enabled, the software checks if it can output the next byte (UTXIFG = 1), and if a new character has been received (URXIFG = 1). \\ h4. Modbus Register Map * REG_INPUT_START         512         // input registers start at 512 * REG_INPUT_NREGS         8           // 8x16 bit registers * REG_SOLENOIDS_A        0            // Holding registers start at 0 (16 coils for each A and B) * REG_SOLENOIDS_B        1   * REG_HOLDING_START    0           // to match WAGO * REG_HOLDING_NREGS   40         // 40 is more than actual (2) * REG_COILS_START         0           // read individual coils (was 1000) * REG_COILS_SIZE           32          // 32 coils * REG_DISC_START          0           // discrete (was 1000) * REG_DISC_SIZE             32          // 32 coils \\ h3. ---- MODBUS * Commands ** Read Input Register (0x04) ** Read Holding Registers (0x03) ** Write Single Register (0x06) ** Write Multiple Registers (0x10) ** Read/Write Multiple Registers (0x17) ** Read Coils (0x01) ** Write Single Coil (0x05) ** Write Multiple Coils (0x0F) ** Read Discrete Inputs (0x02) ** Report Slave ID (0x11)   * Address * Slave ID  * Berlios ModBus Stack ** The modbus stack is config'd in {color:#0000ff}mbconfig.h{color} which is located in vpc\modbus\include \\ \\ ---- h3. Debugging MSP430 h4. Starting gdbproxy The next step is starting gdbproxy, which is responsible for the communication between GDB and the FET: msp430-gdbproxy \--port=2000 msp430 If your FET is properly connected to the parallel port, you should see a message like the following: info: msp430: Target device is a 'MSP430F12x' (type 11) notice: msp430-gdbproxy: waiting on TCP port 2000 h4. Using Insight (Windows) After you have started Insight (c:\msp430\bin\msp430-gdb.exe), click on "File->Open" and select the elf-file (e.g. "test.elf") you want to debug. Now click on "Run->Connect to target" and enter the following settings: Target: "Remote/TCP" Hostname: "localhost" Port: "2000" Set breakpoint at 'main': yes Set breakpoint at 'exit': yes Attach to target: yes Download Program: yes Command after attaching: "monitor erase all" Run Method: Continue from last Stop When you click on "Ok" Insight should tell you that the connection was successful, and gdbproxy should say "notice: msp430-gdbproxy: connected". To start the debugging click on "Run" or simply press "r". If everything worked correctly you should now see the sourcecode of your program with the first line of main() marked green. The red point is the breakpoint that has been set by Insight automatically. You can set or remove breakpoints by clicking on the '-' in front of the line. Now you can 'c'ontinue the execution to the next breakpoint, 's'tep through the code, or step a single assembler instruction... but be careful with "finish": Insight sometimes seems to lock up with this command. So if you want to finish a function, I recommend setting a breakpoint to the end of the function and using "continue". \\ h2. Installing the Compiler Tool Chain To obtain and install the compiler: # Go to the MSPGCC download page and obtain the latest MSPGCC installation. I used the 'mspgcc-20040723.exe' download which installed everything I needed for a Win32 setup. \\ # This step need only be performed if you wish to use the graphical version of GDB. The latest MSPGCC download only includes the command line GDB debugger. I prefer to use the graphical version called Insight. A slightly older prebuilt version of Insight can be used. Install this older version of insight into a different directory to that chosen for the latest MSPGCC installation as you don't want to overwrite the files obtained in step 1. \\ You should now have two installations. The latest version of MSPGCC installed during step 1, and a slightly older version of Insight from step 2. Both versions of the GDB debugger are called msp430-gdb.exe so one needs to be renamed. Locate the older version msp430-gdb.exe from the files installed during this step and rename it msp430-insight.exe. \\ # Ensure the BIN directory from the files installed during step 1 and the BIN directory from the files installed during step 2 are included in your PATH environment variable. \\ \\ # The MSPGCC download includes a program called msp430-gdbproxy.exe. This intercepts the GDB TCP commands and redirects them to the parallel port. Start msp430-gdbproxy (a shortcut to this will have been placed on the start menu when MSPGCC was installed). By default msp430-gdbproxy uses port 3333 - do not change this. \\ # Program the flash as per the instruction in the section above. The flash can be programmed from within GDB but it is much faster to do it separately and beforehand. \\ # Start the debugger using the command ... msp430-insight a.out... the commands in the gdb.ini file will do the rest. If you prefer to use the command line debugger simply replace msp430-insight with msp430-gdb. \\ # Insight will start at and the program will stop at the breakpoint in main() as shown below. \\ MSP430 Clocking \\ MSP430 Basic Clock Module * Clock Signals: ** *ACLK*: Auxiliary clock. The signal is sourced from LFXT1CLK with a divider of 1, 2, 4, or 8. (The calibration program for the serial link sets the divider to 4, but after the calibration it can be changed to any other values.) ACLK can be used as the clock signal for Timer A and Timer B. ** *MCLK*: Master clock. The signal can be sourced from LFXT1CLK, XT2CLK (if available), or DCOCLK with a divider of 1, 2, 4, or 8. MCLK is used by the CPU and system. ** *SMCLK*: Sub-main clock. The signal is sourced from either XT2CLK (if available), or DCOCLK with a divider of 1, 2, 4, or 8. SMCLK can be used as the clock signal for Timer A and Timer B. * MSP430 Clocking pictorial: *   * \\ !MSP430_clocking2.JPG!                  !MSP430_BCSCTL1.JPG! !MSP430_BCSCTL2.JPG!\\ \\]]> 5374431 5407169 D0 52.08 52.08 \+0 \+0.00 D0->D1 104.17 104.17 \+0 \+0.00 D1->D2 156.25 156.25 \+0 \+0.00 D2->D3 208.33 208.33 \+0 \+0.00 D3->D4 260.42 260.42 \+0 \+0.00 D4->D5 312.50 312.50 \+0 \+0.00 D5->D6 364.58 364.58 \+0 \+0.00 D6->D7 416.67 416.67 \+0 \+0.00 D7->stopbit 468.75 468.75 \+0 \+0.00 end of stopb 520.83 520.83 \+0 \+0.00 \*/ UBR00=0xC0; UBR10=0x00; UMCTL0=0x00; /\* uart0 3686400Hz 19200bps \*/ UBR01=0xC0; UBR11=0x00; UMCTL1=0x00; /\* uart1 3686400Hz 19200bps \*/ h4. The simplest way to use the USART in UART mode is this: interrupt is not enabled, the software checks if it can output the next byte (UTXIFG = 1), and if a new character has been received (URXIFG = 1). \\ h4. Modbus Register Map * REG_INPUT_START         512         // input registers start at 512 * REG_INPUT_NREGS         8           // 8x16 bit registers * REG_SOLENOIDS_A        0            // Holding registers start at 0 (16 coils for each A and B) * REG_SOLENOIDS_B        1   * REG_HOLDING_START    0           // to match WAGO * REG_HOLDING_NREGS   40         // 40 is more than actual (2) * REG_COILS_START         0           // read individual coils (was 1000) * REG_COILS_SIZE           32          // 32 coils * REG_DISC_START          0           // discrete (was 1000) * REG_DISC_SIZE             32          // 32 coils \\ h3. ---- MODBUS * Commands ** Read Input Register (0x04) ** Read Holding Registers (0x03) ** Write Single Register (0x06) ** Write Multiple Registers (0x10) ** Read/Write Multiple Registers (0x17) ** Read Coils (0x01) ** Write Single Coil (0x05) ** Write Multiple Coils (0x0F) ** Read Discrete Inputs (0x02) ** Report Slave ID (0x11)   * Address * Slave ID  * Berlios ModBus Stack ** The modbus stack is config'd in {color:#0000ff}mbconfig.h{color} which is located in vpc\modbus\include \\ \\ ---- h3. Debugging MSP430 h4. Starting gdbproxy The next step is starting gdbproxy, which is responsible for the communication between GDB and the FET: msp430-gdbproxy \--port=2000 msp430 If your FET is properly connected to the parallel port, you should see a message like the following: info: msp430: Target device is a 'MSP430F12x' (type 11) notice: msp430-gdbproxy: waiting on TCP port 2000 h4. Using Insight (Windows) After you have started Insight (c:\msp430\bin\msp430-gdb.exe), click on "File->Open" and select the elf-file (e.g. "test.elf") you want to debug. Now click on "Run->Connect to target" and enter the following settings: Target: "Remote/TCP" Hostname: "localhost" Port: "2000" Set breakpoint at 'main': yes Set breakpoint at 'exit': yes Attach to target: yes Download Program: yes Command after attaching: "monitor erase all" Run Method: Continue from last Stop When you click on "Ok" Insight should tell you that the connection was successful, and gdbproxy should say "notice: msp430-gdbproxy: connected". To start the debugging click on "Run" or simply press "r". If everything worked correctly you should now see the sourcecode of your program with the first line of main() marked green. The red point is the breakpoint that has been set by Insight automatically. You can set or remove breakpoints by clicking on the '-' in front of the line. Now you can 'c'ontinue the execution to the next breakpoint, 's'tep through the code, or step a single assembler instruction... but be careful with "finish": Insight sometimes seems to lock up with this command. So if you want to finish a function, I recommend setting a breakpoint to the end of the function and using "continue". \\ h2. Installing the Compiler Tool Chain To obtain and install the compiler: # Go to the MSPGCC download page and obtain the latest MSPGCC installation. I used the 'mspgcc-20040723.exe' download which installed everything I needed for a Win32 setup. \\ # This step need only be performed if you wish to use the graphical version of GDB. The latest MSPGCC download only includes the command line GDB debugger. I prefer to use the graphical version called Insight. A slightly older prebuilt version of Insight can be used. Install this older version of insight into a different directory to that chosen for the latest MSPGCC installation as you don't want to overwrite the files obtained in step 1. \\ You should now have two installations. The latest version of MSPGCC installed during step 1, and a slightly older version of Insight from step 2. Both versions of the GDB debugger are called msp430-gdb.exe so one needs to be renamed. Locate the older version msp430-gdb.exe from the files installed during this step and rename it msp430-insight.exe. \\ # Ensure the BIN directory from the files installed during step 1 and the BIN directory from the files installed during step 2 are included in your PATH environment variable. \\ \\ # The MSPGCC download includes a program called msp430-gdbproxy.exe. This intercepts the GDB TCP commands and redirects them to the parallel port. Start msp430-gdbproxy (a shortcut to this will have been placed on the start menu when MSPGCC was installed). By default msp430-gdbproxy uses port 3333 - do not change this. \\ # Program the flash as per the instruction in the section above. The flash can be programmed from within GDB but it is much faster to do it separately and beforehand. \\ # Start the debugger using the command ... msp430-insight a.out... the commands in the gdb.ini file will do the rest. If you prefer to use the command line debugger simply replace msp430-insight with msp430-gdb. \\ # Insight will start at and the program will stop at the breakpoint in main() as shown below. \\ MSP430 Clocking \\ MSP430 Basic Clock Module * Clock Signals: ** *ACLK*: Auxiliary clock. The signal is sourced from LFXT1CLK with a divider of 1, 2, 4, or 8. (The calibration program for the serial link sets the divider to 4, but after the calibration it can be changed to any other values.) ACLK can be used as the clock signal for Timer A and Timer B. ** *MCLK*: Master clock. The signal can be sourced from LFXT1CLK, XT2CLK (if available), or DCOCLK with a divider of 1, 2, 4, or 8. MCLK is used by the CPU and system. ** *SMCLK*: Sub-main clock. The signal is sourced from either XT2CLK (if available), or DCOCLK with a divider of 1, 2, 4, or 8. SMCLK can be used as the clock signal for Timer A and Timer B. * MSP430 Clocking pictorial: *   * \\ !MSP430_clocking2.JPG!                  !MSP430_BCSCTL1.JPG! !MSP430_BCSCTL2.JPG!\\ \\]]> 5374433 19072811 19040093 19072808 19040090 19072810 19040092 19072803 19040085 11272369 11239604 19072805 19040087 3670056 3637291 3670055 3637290 19072861 19040143 3670058 3637293 3670057 3637292 19072865 19040147 3670054 3637289 3670053 3637288 19072863 19040145 23199976 23167215 3670064 3637299 23199975 23167214 3670063 3637298 23199978 23167217 3670066 3637301 23199977 23167216 3670065 3637300 23199972 23167211 23199971 23167210 3670059 3637294 3670062 3637297 3670061 3637296 3670071 3637306 3670072 3637307 3670073 3637308 3670074 3637309 3670067 3637302 3670069 3637304 3670079 3637314 3670080 3637315 3670082 3637317 3670075 3637310 23199988 23167227 3670076 3637311 23199990 23167229 3670078 3637313 19072884 19040172 19072886 19040174 19072885 19040173 19072888 19040176 19072889 19040177 19072875 19040163 19072877 19040165 23199968 23167207 19072878 19040166 19072879 19040167 19072880 19040168 19072881 19040169 19072882 19040170 19072867 19040149 5406996 D0 52.08 52.08 +0 +0.00 D0->D1 104.17 104.17 +0 +0.00 D1->D2 156.25 156.25 +0 +0.00 D2->D3 208.33 208.33 +0 +0.00 D3->D4 260.42 260.42 +0 +0.00 D4->D5 312.50 312.50 +0 +0.00 D5->D6 364.58 364.58 +0 +0.00 D6->D7 416.67 416.67 +0 +0.00 D7->stopbit 468.75 468.75 +0 +0.00 end of stopb 520.83 520.83 +0 +0.00 */ UBR00=0xC0; UBR10=0x00; UMCTL0=0x00; /* uart0 3686400Hz 19200bps */ UBR01=0xC0; UBR11=0x00; UMCTL1=0x00; /* uart1 3686400Hz 19200bps */ h4.   h4. Modbus Register Map * REG_INPUT_START         512         // input registers start at 512 * REG_INPUT_NREGS         8           // 8x16 bit registers * REG_SOLENOIDS_A        0            // Holding registers start at 0 (16 coils for each A and B) * REG_SOLENOIDS_B        1   * REG_HOLDING_START    0           // to match WAGO * REG_HOLDING_NREGS   40         // 40 is more than actual (2) * REG_COILS_START         0           // read individual coils (was 1000) * REG_COILS_SIZE           32          // 32 coils * REG_DISC_START          0           // discrete (was 1000) * REG_DISC_SIZE             32          // 32 coils \\ h3. ---- MODBUS * Commands ** Read Input Register (0x04) ** Read Holding Registers (0x03) ** Write Single Register (0x06) ** Write Multiple Registers (0x10) ** Read/Write Multiple Registers (0x17) ** Read Coils (0x01) ** Write Single Coil (0x05) ** Write Multiple Coils (0x0F) ** Read Discrete Inputs (0x02) ** Report Slave ID (0x11)   * Address * Slave ID  * Berlios ModBus Stack ** The modbus stack is config'd in {color:#0000ff}mbconfig.h{color} which is located in vpc\modbus\include \\ \\ ---- h3. Debugging MSP430 h4. Starting gdbproxy The next step is starting gdbproxy, which is responsible for the communication between GDB and the FET: msp430-gdbproxy \--port=2000 msp430 If your FET is properly connected to the parallel port, you should see a message like the following: info: msp430: Target device is a 'MSP430F12x' (type 11) notice: msp430-gdbproxy: waiting on TCP port 2000 h4. Using Insight (Windows) After you have started Insight (c:\msp430\bin\msp430-gdb.exe), click on "File->Open" and select the elf-file (e.g. "test.elf") you want to debug. Now click on "Run->Connect to target" and enter the following settings: Target: "Remote/TCP" Hostname: "localhost" Port: "2000" Set breakpoint at 'main': yes Set breakpoint at 'exit': yes Attach to target: yes Download Program: yes Command after attaching: "monitor erase all" Run Method: Continue from last Stop When you click on "Ok" Insight should tell you that the connection was successful, and gdbproxy should say "notice: msp430-gdbproxy: connected". To start the debugging click on "Run" or simply press "r". If everything worked correctly you should now see the sourcecode of your program with the first line of main() marked green. The red point is the breakpoint that has been set by Insight automatically. You can set or remove breakpoints by clicking on the '-' in front of the line. Now you can 'c'ontinue the execution to the next breakpoint, 's'tep through the code, or step a single assembler instruction... but be careful with "finish": Insight sometimes seems to lock up with this command. So if you want to finish a function, I recommend setting a breakpoint to the end of the function and using "continue". \\ h2. Installing the Compiler Tool Chain To obtain and install the compiler: # Go to the MSPGCC download page and obtain the latest MSPGCC installation. I used the 'mspgcc-20040723.exe' download which installed everything I needed for a Win32 setup. \\ # This step need only be performed if you wish to use the graphical version of GDB. The latest MSPGCC download only includes the command line GDB debugger. I prefer to use the graphical version called Insight. A slightly older prebuilt version of Insight can be used. Install this older version of insight into a different directory to that chosen for the latest MSPGCC installation as you don't want to overwrite the files obtained in step 1. \\ You should now have two installations. The latest version of MSPGCC installed during step 1, and a slightly older version of Insight from step 2. Both versions of the GDB debugger are called msp430-gdb.exe so one needs to be renamed. Locate the older version msp430-gdb.exe from the files installed during this step and rename it msp430-insight.exe. \\ # Ensure the BIN directory from the files installed during step 1 and the BIN directory from the files installed during step 2 are included in your PATH environment variable. \\ \\ # The MSPGCC download includes a program called msp430-gdbproxy.exe. This intercepts the GDB TCP commands and redirects them to the parallel port. Start msp430-gdbproxy (a shortcut to this will have been placed on the start menu when MSPGCC was installed). By default msp430-gdbproxy uses port 3333 - do not change this. \\ # Program the flash as per the instruction in the section above. The flash can be programmed from within GDB but it is much faster to do it separately and beforehand. \\ # Start the debugger using the command ... msp430-insight a.out... the commands in the gdb.ini file will do the rest. If you prefer to use the command line debugger simply replace msp430-insight with msp430-gdb. \\ # Insight will start at and the program will stop at the breakpoint in main() as shown below. \\ MSP430 Clocking \\ MSP430 Basic Clock Module * Clock Signals: ** *ACLK*: Auxiliary clock. The signal is sourced from LFXT1CLK with a divider of 1, 2, 4, or 8. (The calibration program for the serial link sets the divider to 4, but after the calibration it can be changed to any other values.) ACLK can be used as the clock signal for Timer A and Timer B. ** *MCLK*: Master clock. The signal can be sourced from LFXT1CLK, XT2CLK (if available), or DCOCLK with a divider of 1, 2, 4, or 8. MCLK is used by the CPU and system. ** *SMCLK*: Sub-main clock. The signal is sourced from either XT2CLK (if available), or DCOCLK with a divider of 1, 2, 4, or 8. SMCLK can be used as the clock signal for Timer A and Timer B. * MSP430 Clocking pictorial: *   * \\ !MSP430_clocking2.JPG!                  !MSP430_BCSCTL1.JPG! !MSP430_BCSCTL2.JPG!\\ \\]]> 5374253 21561411 3407873 3114598 2013-06-13 15:09:52.153 2013-06-13 15:09:52.153 3670229 3637475 3670234 3637479 3670232 3637477 11272288 $5000 Unit Cost | $30,000 | $ | | 5020-000 | Books/Subscriptions | $1,850 | $ | | 5060-000 | Dues, Membership, Licenses | $5,720 | $ | | 5130-000 | Outside Srvc - General | $7,500 | $ | | 5150-000 | Outside Srvc - Maint Contracts | $25,050 | $ | | 5300-000 | Supplies - Computer (Hardware) | $11,875 | $ | | 5310-000 | Supplies - Computer (Software) | $10,180 | $ | | 5320-000 | Supplies - Engineering Lab | $17,850 | $ | | 5330-000 | Supplies - Non-Capitalized Equipment | $13,100 | $ | | *Total* | | $123,125 | $ | {panel}{column}{section}]]> 11239521 11272290 $5000 Unit Cost | $30,000 | $30,000 | | 5020-000 | Books/Subscriptions | $1,850 | $ 1,790.05| | 5060-000 | Dues, Membership, Licenses | $5,720 | $5,720 | | 5130-000 | Outside Srvc - General | $7,500 | $ | | 5150-000 | Outside Srvc - Maint Contracts | $25,050 | $ | | 5300-000 | Supplies - Computer (Hardware) | $11,875 | $ | | 5310-000 | Supplies - Computer (Software) | $10,180 | $ | | 5320-000 | Supplies - Engineering Lab | $17,850 | $ | | 5330-000 | Supplies - Non-Capitalized Equipment | $13,100 | $ | | *Total* | | $123,125 | $ | {panel} Notes: # Early in 2010, there were several purchases that happened in 2009 that did not get resolved until 2010 which kind of threw me for a loop. They are: ## H.264 HD Decoder with IP-100B for $4,330.00 ## IP-100B option for HVD9100 for $1,623.75 ## RedHat Enterprise MRG for $1,399.00. While this was successfully purchased in 2009, it is a contract for service in 2010, so it has to go against 2010 ... ouch. Chalk that one up to lessons learned. ## All the Adobe products: $2002.01 (Lonny got it all ordered in December, but it did not "arrive" until 1/4. OUCH! ## The IBM purchase for JViews licenses were done in december and I recieved the invoice on 12/10. I assumed they also sent an invoice to purchasing ... Ummm, NOT! Fortunately, accounting worked with me and that $7500 should go against 2009. {column}{section}]]> 11239523 5407092 D0 52.08 52.08 \+0 \+0.00 D0->D1 104.17 104.17 \+0 \+0.00 D1->D2 156.25 156.25 \+0 \+0.00 D2->D3 208.33 208.33 \+0 \+0.00 D3->D4 260.42 260.42 \+0 \+0.00 D4->D5 312.50 312.50 \+0 \+0.00 D5->D6 364.58 364.58 \+0 \+0.00 D6->D7 416.67 416.67 \+0 \+0.00 D7->stopbit 468.75 468.75 \+0 \+0.00 end of stopb 520.83 520.83 \+0 \+0.00 \*/ UBR00=0xC0; UBR10=0x00; UMCTL0=0x00; /\* uart0 3686400Hz 19200bps \*/ UBR01=0xC0; UBR11=0x00; UMCTL1=0x00; /\* uart1 3686400Hz 19200bps \*/ h4. The simplest way to use the USART in UART mode is this: interrupt is not enabled, the software checks if it can output the next byte (UTXIFG = 1), and if a new character has been received (URXIFG = 1).\\ h4. Modbus Register Map * REG_INPUT_START         512         // input registers start at 512 * REG_INPUT_NREGS         8           // 8x16 bit registers * REG_SOLENOIDS_A        0            // Holding registers start at 0 (16 coils for each A and B) * REG_SOLENOIDS_B        1   * REG_HOLDING_START    0           // to match WAGO * REG_HOLDING_NREGS   40         // 40 is more than actual (2) * REG_COILS_START         0           // read individual coils (was 1000) * REG_COILS_SIZE           32          // 32 coils * REG_DISC_START          0           // discrete (was 1000) * REG_DISC_SIZE             32          // 32 coils \\ h3. ---- MODBUS * Commands ** Read Input Register (0x04) ** Read Holding Registers (0x03) ** Write Single Register (0x06) ** Write Multiple Registers (0x10) ** Read/Write Multiple Registers (0x17) ** Read Coils (0x01) ** Write Single Coil (0x05) ** Write Multiple Coils (0x0F) ** Read Discrete Inputs (0x02) ** Report Slave ID (0x11)   * Address * Slave ID  * Berlios ModBus Stack ** The modbus stack is config'd in {color:#0000ff}mbconfig.h{color} which is located in vpc\modbus\include \\ \\ ---- h3. Debugging MSP430 h4. Starting gdbproxy The next step is starting gdbproxy, which is responsible for the communication between GDB and the FET: msp430-gdbproxy \--port=2000 msp430 If your FET is properly connected to the parallel port, you should see a message like the following: info: msp430: Target device is a 'MSP430F12x' (type 11) notice: msp430-gdbproxy: waiting on TCP port 2000 h4. Using Insight (Windows) After you have started Insight (c:\msp430\bin\msp430-gdb.exe), click on "File->Open" and select the elf-file (e.g. "test.elf") you want to debug. Now click on "Run->Connect to target" and enter the following settings: Target: "Remote/TCP" Hostname: "localhost" Port: "2000" Set breakpoint at 'main': yes Set breakpoint at 'exit': yes Attach to target: yes Download Program: yes Command after attaching: "monitor erase all" Run Method: Continue from last Stop When you click on "Ok" Insight should tell you that the connection was successful, and gdbproxy should say "notice: msp430-gdbproxy: connected". To start the debugging click on "Run" or simply press "r". If everything worked correctly you should now see the sourcecode of your program with the first line of main() marked green. The red point is the breakpoint that has been set by Insight automatically. You can set or remove breakpoints by clicking on the '-' in front of the line. Now you can 'c'ontinue the execution to the next breakpoint, 's'tep through the code, or step a single assembler instruction... but be careful with "finish": Insight sometimes seems to lock up with this command. So if you want to finish a function, I recommend setting a breakpoint to the end of the function and using "continue". \\ h2. Installing the Compiler Tool Chain To obtain and install the compiler: # Go to the MSPGCC download page and obtain the latest MSPGCC installation. I used the 'mspgcc-20040723.exe' download which installed everything I needed for a Win32 setup. \\ # This step need only be performed if you wish to use the graphical version of GDB. The latest MSPGCC download only includes the command line GDB debugger. I prefer to use the graphical version called Insight. A slightly older prebuilt version of Insight can be used. Install this older version of insight into a different directory to that chosen for the latest MSPGCC installation as you don't want to overwrite the files obtained in step 1. \\ You should now have two installations. The latest version of MSPGCC installed during step 1, and a slightly older version of Insight from step 2. Both versions of the GDB debugger are called msp430-gdb.exe so one needs to be renamed. Locate the older version msp430-gdb.exe from the files installed during this step and rename it msp430-insight.exe. \\ # Ensure the BIN directory from the files installed during step 1 and the BIN directory from the files installed during step 2 are included in your PATH environment variable. \\ \\ # The MSPGCC download includes a program called msp430-gdbproxy.exe. This intercepts the GDB TCP commands and redirects them to the parallel port. Start msp430-gdbproxy (a shortcut to this will have been placed on the start menu when MSPGCC was installed). By default msp430-gdbproxy uses port 3333 - do not change this. \\ # Program the flash as per the instruction in the section above. The flash can be programmed from within GDB but it is much faster to do it separately and beforehand. \\ # Start the debugger using the command ... msp430-insight a.out... the commands in the gdb.ini file will do the rest. If you prefer to use the command line debugger simply replace msp430-insight with msp430-gdb. \\ # Insight will start at and the program will stop at the breakpoint in main() as shown below. \\ MSP430 Clocking \\ MSP430 Basic Clock Module * Clock Signals: ** *ACLK*: Auxiliary clock. The signal is sourced from LFXT1CLK with a divider of 1, 2, 4, or 8. (The calibration program for the serial link sets the divider to 4, but after the calibration it can be changed to any other values.) ACLK can be used as the clock signal for Timer A and Timer B. ** *MCLK*: Master clock. The signal can be sourced from LFXT1CLK, XT2CLK (if available), or DCOCLK with a divider of 1, 2, 4, or 8. MCLK is used by the CPU and system. ** *SMCLK*: Sub-main clock. The signal is sourced from either XT2CLK (if available), or DCOCLK with a divider of 1, 2, 4, or 8. SMCLK can be used as the clock signal for Timer A and Timer B. * MSP430 Clocking pictorial: *   * \\ !MSP430_clocking2.JPG!                  !MSP430_BCSCTL1.JPG! !MSP430_BCSCTL2.JPG!\\ \\]]> 5374354 11272300 11239533 11272298 11239531 11272296 $5000 Unit Cost | $30,000 | $30,000 | | 5020-000 | Books/Subscriptions | $1,850 | $ 1,790.05| | 5060-000 | Dues, Membership, Licenses | $5,720 | $5,720 | | 5130-000 | Outside Srvc - General | $7,500 | $7,400 | | 5150-000 | Outside Srvc - Maint Contracts | $25,050 | $25,774.70 | | 5300-000 | Supplies - Computer (Hardware) | $11,875 | $12,256.26 | | 5310-000 | Supplies - Computer (Software) | $10,180 | $9,819.49 | | 5320-000 | Supplies - Engineering Lab | $17,850 | $12,636.21 | | 5330-000 | Supplies - Non-Capitalized Equipment | $13,100 | $7,146.25 | | *Total* | | $123,125 | $112,542.96 | {panel} Notes: # Early in 2010, there were several purchases that happened in 2009 that did not get resolved until 2010 which kind of threw me for a loop. They are: ## H.264 HD Decoder with IP-100B for $4,330.00 ## IP-100B option for HVD9100 for $1,623.75 ## RedHat Enterprise MRG for $1,399.00. While this was successfully purchased in 2009, it is a contract for service in 2010, so it has to go against 2010 ... ouch. Chalk that one up to lessons learned. ## All the Adobe products: $2002.01 (Lonny got it all ordered in December, but it did not "arrive" until 1/4. OUCH! ## The IBM purchase for JViews licenses were done in december and I recieved the invoice on 12/10. I assumed they also sent an invoice to purchasing ... Ummm, NOT! Fortunately, accounting worked with me and that $7500 should go against 2009. {column}{section}]]> 11239529 11272294 $5000 Unit Cost | $30,000 | $30,000 | | 5020-000 | Books/Subscriptions | $1,850 | $ 1,790.05| | 5060-000 | Dues, Membership, Licenses | $5,720 | $5,720 | | 5130-000 | Outside Srvc - General | $7,500 | $7,400 | | 5150-000 | Outside Srvc - Maint Contracts | $25,050 | $25,774.70 | | 5300-000 | Supplies - Computer (Hardware) | $11,875 | $12,256.26 | | 5310-000 | Supplies - Computer (Software) | $10,180 | $9,819.49 | | 5320-000 | Supplies - Engineering Lab | $17,850 | $12,636.21 | | 5330-000 | Supplies - Non-Capitalized Equipment | $13,100 | $7,146.25 | | *Total* | | $123,125 | $112,542.96 | {panel} Notes: # Early in 2010, there were several purchases that happened in 2009 that did not get resolved until 2010 which kind of threw me for a loop. They are: ## H.264 HD Decoder with IP-100B for $4,330.00 ## IP-100B option for HVD9100 for $1,623.75 ## RedHat Enterprise MRG for $1,399.00. While this was successfully purchased in 2009, it is a contract for service in 2010, so it has to go against 2010 ... ouch. Chalk that one up to lessons learned. ## All the Adobe products: $2002.01 (Lonny got it all ordered in December, but it did not "arrive" until 1/4. OUCH! ## The IBM purchase for JViews licenses were done in december and I recieved the invoice on 12/10. I assumed they also sent an invoice to purchasing ... Ummm, NOT! Fortunately, accounting worked with me and that $7500 should go against 2009. {column}{section}]]> 11239527 11272292 $5000 Unit Cost | $30,000 | $30,000 | | 5020-000 | Books/Subscriptions | $1,850 | $ 1,790.05| | 5060-000 | Dues, Membership, Licenses | $5,720 | $5,720 | | 5130-000 | Outside Srvc - General | $7,500 | $7,400 | | 5150-000 | Outside Srvc - Maint Contracts | $25,050 | $25,774.70 | | 5300-000 | Supplies - Computer (Hardware) | $11,875 | $12,256.26 | | 5310-000 | Supplies - Computer (Software) | $10,180 | $9,819.49 | | 5320-000 | Supplies - Engineering Lab | $17,850 | $12,636.21 | | 5330-000 | Supplies - Non-Capitalized Equipment | $13,100 | $7,146.25 | | *Total* | | $123,125 | $ | {panel} Notes: # Early in 2010, there were several purchases that happened in 2009 that did not get resolved until 2010 which kind of threw me for a loop. They are: ## H.264 HD Decoder with IP-100B for $4,330.00 ## IP-100B option for HVD9100 for $1,623.75 ## RedHat Enterprise MRG for $1,399.00. While this was successfully purchased in 2009, it is a contract for service in 2010, so it has to go against 2010 ... ouch. Chalk that one up to lessons learned. ## All the Adobe products: $2002.01 (Lonny got it all ordered in December, but it did not "arrive" until 1/4. OUCH! ## The IBM purchase for JViews licenses were done in december and I recieved the invoice on 12/10. I assumed they also sent an invoice to purchasing ... Ummm, NOT! Fortunately, accounting worked with me and that $7500 should go against 2009. {column}{section}]]> 11239525 11272291 $5000 Unit Cost | $30,000 | $30,000 | | 5020-000 | Books/Subscriptions | $1,850 | $ 1,790.05| | 5060-000 | Dues, Membership, Licenses | $5,720 | $5,720 | | 5130-000 | Outside Srvc - General | $7,500 | $7,400 | | 5150-000 | Outside Srvc - Maint Contracts | $25,050 | $25,774.70 | | 5300-000 | Supplies - Computer (Hardware) | $11,875 | $12,256.26 | | 5310-000 | Supplies - Computer (Software) | $10,180 | $9,819.49 | | 5320-000 | Supplies - Engineering Lab | $17,850 | $12,636.21 | | 5330-000 | Supplies - Non-Capitalized Equipment | $13,100 | $7,146.25 | | *Total* | | $123,125 | $ | {panel} Notes: # Early in 2010, there were several purchases that happened in 2009 that did not get resolved until 2010 which kind of threw me for a loop. They are: ## H.264 HD Decoder with IP-100B for $4,330.00 ## IP-100B option for HVD9100 for $1,623.75 ## RedHat Enterprise MRG for $1,399.00. While this was successfully purchased in 2009, it is a contract for service in 2010, so it has to go against 2010 ... ouch. Chalk that one up to lessons learned. ## All the Adobe products: $2002.01 (Lonny got it all ordered in December, but it did not "arrive" until 1/4. OUCH! ## The IBM purchase for JViews licenses were done in december and I recieved the invoice on 12/10. I assumed they also sent an invoice to purchasing ... Ummm, NOT! Fortunately, accounting worked with me and that $7500 should go against 2009. {column}{section}]]> 11239524 10387550 10354783 10387551 10354784 10387553 {noformat} Lastly, I edited the /opt/jboss/server/default/deploy/jbossweb-tomcat55.sar/META-INF/jboss-service.xml and changed the following line: {noformat} false {noformat} to: {noformat} true {noformat} Then I restarted JBoss.]]> 10354786 10387565 10354798 10387564 10354797 10387570 10354804 12550237 12484702 10387569 10354803 12550235 12484700 10387567 10354801 12550234 12484699 10387558 10354791 10387556 10354789 10387562 10354795 12550229 12484694 10387560 10354793 12550227 12484692 12550225 12484690 15237269 15204505 10387582 10354816 10387580 10354814 15237273 Add/Remove Software) # Click on the Search tab and enter 'openssl' then hit return. Make sure the openssl and openssl-devel are installed and if not, check the packages and click on 'Apply' (some dependencies may be installed as well). # In order to use the odbc functions for erlang (not necessarily need for us, but whatever), the odbc packages needed to be installed. In the Package Manager, I made sure the following were installed: ## unixODBC (both the i386 and the x86_64) ## unixODBC-devel (both the i386 and the x86_64) # Now for the current production release in the EPEL for rabbitmq (which is 2.1.0), we needed Erlang R13 (not 14 or 12). So this means I needed to build it. I went to erlang.org and downloaded the R13B04 tar.gz file and unpacked on my Desktop. # I opened a command terminal and ran: {noformat} cd ~/Desktop gunzip otp_src_R13B04.tar.gz tar -xvf otp_src_R13B04.tar cd otp_src_R13B04 ./configure --with-ssl --with-odbc make make install {noformat} # Had to get I.S. to give me permissions to install development libraries and tools so I could build erlang. # I had to install a java compiler to enable the jinterface. ## Downloaded the 64bit JDK RPM from java.com to my Desktop ## Ran chmod to enable execution of the downloaded .rpm.bin file. # Created a directory for erlang in /usr/local/erlang using sudo # Downloaded the erlang R14B source distribution from [http://www.erlang.org/download.html] to my Desktop on ssds-ingest and then moved it to the /usr/local/erlang directory. # I then unzipped and untarred the the erlang dist in the /usr/local/erlang and then renamed the directory it created to otp_r14b. # I then cd'd into the opt_r14b directory and ran the ./configure script. # I then ran 'make' and then 'make install' (finally had I.S. do this as I couldn't). ]]> 15204509 12550222 12484686 15237274 Add/Remove Software) # Click on the Search tab and enter 'openssl' then hit return. Make sure the openssl and openssl-devel are installed and if not, check the packages and click on 'Apply' (some dependencies may be installed as well). # In order to use the odbc functions for erlang (not necessarily need for us, but whatever), the odbc packages needed to be installed. In the Package Manager, I made sure the following were installed: ## unixODBC (both the i386 and the x86_64) ## unixODBC-devel (both the i386 and the x86_64) # I also needed to install the ncurses devel libraries with the package manager as well as the wxWidgets library. So using package manager, I installed (for i386 and x86_64): ## ncurses-devel ## wxGTK ## wxGTK-devel ## wxGTK-gl # Now for the current production release in the EPEL for rabbitmq (which is 2.1.0), we needed Erlang R13 (not 14 or 12). So this means I needed to build it. I went to erlang.org and downloaded the R13B04 tar.gz file and unpacked on my Desktop. # I opened a command terminal and ran: {noformat} cd ~/Desktop gunzip otp_src_R13B04.tar.gz tar -xvf otp_src_R13B04.tar cd otp_src_R13B04 ./configure --with-ssl --with-odbc make make install {noformat} # Had to get I.S. to give me permissions to install development libraries and tools so I could build erlang. # I had to install a java compiler to enable the jinterface. ## Downloaded the 64bit JDK RPM from java.com to my Desktop ## Ran chmod to enable execution of the downloaded .rpm.bin file. # Created a directory for erlang in /usr/local/erlang using sudo # Downloaded the erlang R14B source distribution from [http://www.erlang.org/download.html] to my Desktop on ssds-ingest and then moved it to the /usr/local/erlang directory. # I then unzipped and untarred the the erlang dist in the /usr/local/erlang and then renamed the directory it created to otp_r14b. # I then cd'd into the opt_r14b directory and ran the ./configure script. # I then ran 'make' and then 'make install' (finally had I.S. do this as I couldn't). ]]> 15204510 10387586 10354820 15237271 Add/Remove Software) # Click on the Search tab and enter 'openssl' then hit return. Make sure the openssl and openssl-devel are installed and if not, check the packages and click on 'Apply' # Had to get I.S. to give me permissions to install development libraries and tools so I could build erlang. # I had to install a java compiler to enable the jinterface. ## Downloaded the 64bit JDK RPM from java.com to my Desktop ## Ran chmod to enable execution of the downloaded .rpm.bin file. # Created a directory for erlang in /usr/local/erlang using sudo # Downloaded the erlang R14B source distribution from [http://www.erlang.org/download.html] to my Desktop on ssds-ingest and then moved it to the /usr/local/erlang directory. # I then unzipped and untarred the the erlang dist in the /usr/local/erlang and then renamed the directory it created to otp_r14b. # I then cd'd into the opt_r14b directory and ran the ./configure script. # I then ran 'make' and then 'make install' (finally had I.S. do this as I couldn't). ]]> 15204507 10387583 10354817 10387573 10354807 10387574 10354808 10387571 10354805 15237276 Add/Remove Software) # Click on the Search tab and enter 'openssl' then hit return. Make sure the openssl and openssl-devel are installed and if not, check the packages and click on 'Apply' (some dependencies may be installed as well). # In order to use the odbc functions for erlang (not necessarily need for us, but whatever), the odbc packages needed to be installed. In the Package Manager, I made sure the following were installed: ## unixODBC (both the i386 and the x86_64) ## unixODBC-devel (both the i386 and the x86_64) # I also needed to install the ncurses devel libraries with the package manager as well as the wxWidgets library. So using package manager, I installed (for i386 and x86_64 and then a bunch of dependencies were added): ## ncurses-devel ## wxGTK ## wxGTK-devel ## wxGTK-gl # Now for the current production release in the EPEL for rabbitmq (which is 2.1.0), we needed Erlang R13 (not 14 or 12). So this means I needed to build it. I went to erlang.org and downloaded the R13B04 tar.gz file and unpacked on my Desktop. # I opened a command terminal and ran: {noformat} cd ~/Desktop gunzip otp_src_R13B04.tar.gz tar -xvf otp_src_R13B04.tar cd otp_src_R13B04 ./configure --with-ssl --with-odbc make make install {noformat} # Had to get I.S. to give me permissions to install development libraries and tools so I could build erlang. # I had to install a java compiler to enable the jinterface. ## Downloaded the 64bit JDK RPM from java.com to my Desktop ## Ran chmod to enable execution of the downloaded .rpm.bin file. # Created a directory for erlang in /usr/local/erlang using sudo # Downloaded the erlang R14B source distribution from [http://www.erlang.org/download.html] to my Desktop on ssds-ingest and then moved it to the /usr/local/erlang directory. # I then unzipped and untarred the the erlang dist in the /usr/local/erlang and then renamed the directory it created to otp_r14b. # I then cd'd into the opt_r14b directory and ran the ./configure script. # I then ran 'make' and then 'make install' (finally had I.S. do this as I couldn't). ]]> 15204512 10387572 10354806 15237281 Add/Remove Software) # Make sure under the Browse->Development tab/section that the Development Libraries and Development Tools are installed. # Make sure that a real Java SDK is installed (1.5+) before continuing (see java.com) # Click on the Search tab and enter 'openssl' then hit return. Make sure the openssl and openssl-devel are installed and if not, check the packages and click on 'Apply' (some dependencies may be installed as well). # In order to use the odbc functions for erlang (not necessarily need for us, but whatever), the odbc packages needed to be installed. In the Package Manager, I made sure the following were installed: ## unixODBC (both the i386 and the x86_64) ## unixODBC-devel (both the i386 and the x86_64) # I also needed to install the ncurses devel libraries with the package manager as well as the wxWidgets library. So using package manager, I installed (for i386 and x86_64 and then a bunch of dependencies were added): ## ncurses-devel ## wxGTK ## wxGTK-devel ## wxGTK-gl # Now for the current production release in the EPEL for rabbitmq (which is 2.1.0), we needed Erlang R13 (not 14 or 12). So this means I needed to build it. I went to erlang.org and downloaded the R13B04 tar.gz file and unpacked on my Desktop. # I opened a command terminal and ran: {noformat} cd ~/Desktop gunzip otp_src_R13B04.tar.gz tar -xvf otp_src_R13B04.tar cd otp_src_R13B04 ./configure --with-ssl --with-odbc make make install {noformat} ]]> 15204517 10387577 10354811 10387578 10354812 15237279 Add/Remove Software) # Make sure under the Browse->Development tab/section that the Development Libraries and Development Tools are installed. # Make sure that a real Java SDK is installed (1.5+) before continuing (see java.com) # Click on the Search tab and enter 'openssl' then hit return. Make sure the openssl and openssl-devel are installed and if not, check the packages and click on 'Apply' (some dependencies may be installed as well). # In order to use the odbc functions for erlang (not necessarily need for us, but whatever), the odbc packages needed to be installed. In the Package Manager, I made sure the following were installed: ## unixODBC (both the i386 and the x86_64) ## unixODBC-devel (both the i386 and the x86_64) # I also needed to install the ncurses devel libraries with the package manager as well as the wxWidgets library. So using package manager, I installed (for i386 and x86_64 and then a bunch of dependencies were added): ## ncurses-devel ## wxGTK ## wxGTK-devel ## wxGTK-gl # Now for the current production release in the EPEL for rabbitmq (which is 2.1.0), we needed Erlang R13 (not 14 or 12). So this means I needed to build it. I went to erlang.org and downloaded the R13B04 tar.gz file and unpacked on my Desktop. # I opened a command terminal and ran: {noformat} cd ~/Desktop gunzip otp_src_R13B04.tar.gz tar -xvf otp_src_R13B04.tar cd otp_src_R13B04 ./configure --with-ssl --with-odbc make make install {noformat} # Had to get I.S. to give me permissions to install development libraries and tools so I could build erlang. # I had to install a java compiler to enable the jinterface. ## Downloaded the 64bit JDK RPM from java.com to my Desktop ## Ran chmod to enable execution of the downloaded .rpm.bin file. # Created a directory for erlang in /usr/local/erlang using sudo # Downloaded the erlang R14B source distribution from [http://www.erlang.org/download.html] to my Desktop on ssds-ingest and then moved it to the /usr/local/erlang directory. # I then unzipped and untarred the the erlang dist in the /usr/local/erlang and then renamed the directory it created to otp_r14b. # I then cd'd into the opt_r14b directory and ran the ./configure script. # I then ran 'make' and then 'make install' (finally had I.S. do this as I couldn't). ]]> 15204515 10387575 10354809 10387576 10354810 10387463 10354695 10387479 10354711 10387505 10354738 10387651 10354887 10387656 10354892 10387659 10354895 10387660 ... internal dav:http://seaspray.shore.mbari.org:8082/archiva/repository/internal/ snapshots dav:http://seaspray.shore.mbari.org:8082/archiva/repository/snapshots/ internal Archiva Managed Internal Repository http://seaspray.shore.mbari.org:8082/archiva/repository/internal/ true false snapshots Archiva Managed Snapshot Repository http://seaspray.shore.mbari.org:8082/archiva/repository/snapshots/ false true ... {code} h2. {anchor:M2} +Using the external MBARI repository from a [Maven 2|http://maven.apache.org/] project+ h3. Referencing the Repository To include the MBARI repository in your Maven build, edit your _pom.xml_ to include the MBARI repository location: {code:xml} ... mbari MBARI Repository http://oceana.shore.mbari.org/maven2 ... ... {code} h3. Including a Dependency from the Repository Once the MBARI repository is included in you build, you can browse the repository to see what projects are available (just go to [http://oceana.shore.mbari.org/maven2]). If you find a dependency you need you can reference it in your _pom.xml_. Here's an example... {code:xml} ... ... qt4j qt4j 0.5 ... ... {code} h3. Putting a Dependency into the Repository The easiest way to put a dependency into the repository is to setup a Maven build file (i.e. _pom.xml_). In _pom.xml_ add the following _distributionManagement_ information: {code:xml} 4.0.0 qt4j qt4j jar 1.0-SNAPSHOT QT4J ... mbari-repository MBARI Repository scp://oceana.shore.mbari.org/var/www/html/maven2 {code} Executing _mvn deploy_ will put your build jar at http://oceana.shore.mbari.org/maven2////-.jar. In the example here it would put it into [http://oceana.shore.mbari.org/maven2/qt4j/qt4j/1.0-SNAPSHOT/] h3. Publishing Maven generated web sites Maven can generate a web site for a default web site for you. You can view samples of the currently published projects at [http://oceana.shore.mbari.org/projects]. It's not very interesting, however, it is a very simple way to publish the javadoc, sources and auto-generated reports. To do so modify your _pom.xml_: {code:xml} ... org.apache.maven.plugins maven-jxr-plugin org.apache.maven.plugins maven-pmd-plugin 1.5 org.apache.maven.plugins maven-checkstyle-plugin ... oceana.shore.mbari.org scp://oceana.shore.mbari.org/var/www/html/projects/${project.name} {code} Then run _mvn javadoc:javadoc site:site site:deploy_. This will build the javadocs, create a site with some useful reports, then publish the site (using scp) to oceana in the correct location. h3. Project Specific Maven Repositories Some projects may need to be configured differently for different deployment locations. For example, [VARS|VARS:Home] is configured differently for each ship and shore. These specific configurations are stored in Maven repositories in [http://oceana.shore.mbari.org/maven2-prj]. Each directory listed there is a different repository. Here's an example of how to include the projects configured for [Eye-in-the-sea|EITS:Home]. {code:xml} mbari-eits MBARI-EITS Repository http://oceana.shore.mbari.org/maven2-prj/eits {code} h2. {anchor:M3} +Using the external MBARI repository from an [Ant|http://ant.apache.org] project using Maven+ Maven repositories can be used from Ant build scripts using [Maven's antlib|http://maven.apache.org/ant-tasks.html]. To do this you must have both Maven and Ant installed. h3. Bootstrapping antlib To bootstrap antlib into your projects (so users can build without having to install antlib) modify your _build.xml_ file like so: {code:xml} ... Finding dependencies of ${pom.artifactId}-${version} ... {code} h2. {anchor:M4} +Using the external MBARI repository from an [Ant|http://ant.apache.org] project using Ivy+ Maven repositories can be used from Ant build scripts using [Ivy|http://incubator.apache.org/ivy/]. h3. Referencing the repository In the directory containing the ant build file, _build.xml_, create a file called _ivyconf.xml_. _ivyconf.xml_ tells Ivy where to look for dependencies. The contents of the file will look something like: {code:xml} {code} h3. Including a Dependency from the Repository In the directory containing _build.xml_, create a file called _ivy.xml_. _ivy.xml_ tells Ivy what dependencies to include in your build. Here's an example of it's contents: {code:xml} {code} h3. Using Ivy from Ant The code below will fetch Ivy for you. SO you do not need install any additional software in order to get you build to work. In your ant build file include the following: {code:xml} ... {code} Calling _ant ivy.install_ will fetch all the dependencies from the web and put them into the _lib_ directory of your project. ]]> 10354896 10387664 10354900 10387665 ... internal dav:http://seaspray.shore.mbari.org:8082/archiva/repository/internal/ snapshots dav:http://seaspray.shore.mbari.org:8082/archiva/repository/snapshots/ internal Archiva Managed Internal Repository http://seaspray.shore.mbari.org:8082/archiva/repository/internal/ true false snapshots Archiva Managed Snapshot Repository http://seaspray.shore.mbari.org:8082/archiva/repository/snapshots/ false true ... {code} h2. {anchor:M2} +Using the external MBARI repository from a [Maven 2|http://maven.apache.org/] project+ h3. Referencing the Repository To include the MBARI repository in your Maven build, edit your _pom.xml_ to include the MBARI repository location: {code:xml} ... mbari MBARI Repository http://oceana.shore.mbari.org/maven2 ... ... {code} h3. Including a Dependency from the Repository Once the MBARI repository is included in you build, you can browse the repository to see what projects are available (just go to [http://oceana.shore.mbari.org/maven2]). If you find a dependency you need you can reference it in your _pom.xml_. Here's an example... {code:xml} ... ... qt4j qt4j 0.5 ... ... {code} h3. Putting a Dependency into the Repository The easiest way to put a dependency into the repository is to setup a Maven build file (i.e. _pom.xml_). In _pom.xml_ add the following _distributionManagement_ information: {code:xml} 4.0.0 qt4j qt4j jar 1.0-SNAPSHOT QT4J ... mbari-repository MBARI Repository scp://oceana.shore.mbari.org/var/www/html/maven2 {code} Executing _mvn deploy_ will put your build jar at http://oceana.shore.mbari.org/maven2////-.jar. In the example here it would put it into [http://oceana.shore.mbari.org/maven2/qt4j/qt4j/1.0-SNAPSHOT/] h3. Publishing Maven generated web sites Maven can generate a web site for a default web site for you. You can view samples of the currently published projects at [http://oceana.shore.mbari.org/projects]. It's not very interesting, however, it is a very simple way to publish the javadoc, sources and auto-generated reports. To do so modify your _pom.xml_: {code:xml} ... org.apache.maven.plugins maven-jxr-plugin org.apache.maven.plugins maven-pmd-plugin 1.5 org.apache.maven.plugins maven-checkstyle-plugin ... oceana.shore.mbari.org scp://oceana.shore.mbari.org/var/www/html/projects/${project.name} {code} Then run _mvn javadoc:javadoc site:site site:deploy_. This will build the javadocs, create a site with some useful reports, then publish the site (using scp) to oceana in the correct location. h3. Project Specific Maven Repositories Some projects may need to be configured differently for different deployment locations. For example, [VARS|VARS:Home] is configured differently for each ship and shore. These specific configurations are stored in Maven repositories in [http://oceana.shore.mbari.org/maven2-prj]. Each directory listed there is a different repository. Here's an example of how to include the projects configured for [Eye-in-the-sea|EITS:Home]. {code:xml} mbari-eits MBARI-EITS Repository http://oceana.shore.mbari.org/maven2-prj/eits {code} h2. {anchor:M3} +Using the external MBARI repository from an [Ant|http://ant.apache.org] project using Maven+ Maven repositories can be used from Ant build scripts using [Maven's antlib|http://maven.apache.org/ant-tasks.html]. To do this you must have both Maven and Ant installed. h3. Bootstrapping antlib To bootstrap antlib into your projects (so users can build without having to install antlib) modify your _build.xml_ file like so: {code:xml} ... Finding dependencies of ${pom.artifactId}-${version} ... {code} h2. {anchor:M4} +Using the external MBARI repository from an [Ant|http://ant.apache.org] project using Ivy+ Maven repositories can be used from Ant build scripts using [Ivy|http://incubator.apache.org/ivy/]. h3. Referencing the repository In the directory containing the ant build file, _build.xml_, create a file called _ivyconf.xml_. _ivyconf.xml_ tells Ivy where to look for dependencies. The contents of the file will look something like: {code:xml} {code} h3. Including a Dependency from the Repository In the directory containing _build.xml_, create a file called _ivy.xml_. _ivy.xml_ tells Ivy what dependencies to include in your build. Here's an example of it's contents: {code:xml} {code} h3. Using Ivy from Ant The code below will fetch Ivy for you. SO you do not need install any additional software in order to get you build to work. In your ant build file include the following: {code:xml} ... {code} Calling _ant ivy.install_ will fetch all the dependencies from the web and put them into the _lib_ directory of your project. ]]> 10354901 10387666 10354902 10387587 10354821 10387588 10354822 10387590 10354824 10387599 10354833 10387601 10354835 10387595 10354829 10387597 10354831 15237246 15204482 28049429 4.4: [https://confluence.atlassian.com/display/JIRA044/Migrating+JIRA+to+Another+Server] ## The JIRA configuration tool: [https://confluence.atlassian.com/display/JIRA044/Using+the+JIRA+Configuration+Tool] h5. Steps # (/) Create new VM named bugs.mbari.org in the DMZ # (/) Have Neil create database Jira_Temp on solstice2.shore.mbari.org # (/) Have Neil create database Jira on solstice2.shore.mbari.org # (/) Have Pat install Java 7 on bugs.shore.mbari.org # (/) Have Pete plumb holes through firewall so processes on bugs.mbari.org can get to Solstice2 # (/) Have Pat create DB_Collaboration account on bugs so it can run JIRA under that account and it can connect to solstice2 using that NT Domain account. # (/) Upgrade license on Atlassian site # (/) Log into bugs.shore.mbari.org # (/) Download 3.13.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 4.4.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 5.2.11 standalone Linux 64 bit tar.gz (not sure this version is necessary, but at least I have it) # (/) Unzip and untar the file to /opt # (/) Download latest JIRA (6.4.7 as of this writing). # (/) Unzip and untar it to /opt # Performed Test Upgrade ## (/) In order to export the current stuff in JIRA, I had to shut off access so people could not change the data while I was backing it up. ## (/) I ssh'd to oceana.mbari.org as root and edited the /opt/jira/conf/server.xml file and commented out the Connector section that had the port of 8010 to shut it off from the normal serving route. ## (/) I uncommented the 8082 port connector and the 8443 port connector so that I could still get to the server. ## (/) I stopped and started the JIRA server and in the log file I got a "keystore was tampered with..." which is not surprising. ## (/) I could then browser over to http://oceana.mbari.org:8082/jira ## (/) Then through the Administration console, I did an XML backup ## (/) I then created a tar of all the attachments in the /data/jira_3_12/attachments directory ## (/) I moved both the XML and tar files to the /root/jira-upgrade directory ## (/) I then reversed the changes to the server.xml file and shut down JIRA ## (/) I left it down during the next steps in case it went so well, I could just point people to the new server (yeah, right). ## (/) I then browsed to the crowd server on oceana and add a new application using: ### URL: http://bugs.mbari.org/jira3135 ### IP: 134.89.2.29 ### Name: JIRA3135 ### Password: (ask Kevin) :) ## (/) On bugs, I made a copy of the JIRA 3.13.5 download in the /opt directory and unzipped and untarred it. ## (/) In order to configure the crowd connection I did the following: ### (/) I scp'd the /opt/crowd/client/crowd-integration-client-1.6.jar file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I removed the existing 1.6.1 crowd client jar from the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I scp'd the /opt/crowd/client/conf/crowd.properties file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I scp'd the /opt/crowd/client/conf/crowd-ehcache.xml file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I edited the crowd.properties file on bugs to look like: {noformat} application.name JIRA3135 application.password (ask Kevin) application.login.url http://oceana.mbari.org:8095/crowd/console/ crowd.server.url http://oceana.mbari.org:8095/crowd/services/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 0 session.lastvalidation session.lastvalidation {noformat} ### (/) I edited the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/osuser.xml file to comment out the current authentication mechanism and then uncomment the crowd one. ## (/) I then edited the /opt/atlassian-jira-standalone-3.13.5/conf/server/xml file and configured the database connection to the Jira_Temp database on Solstice2. I looked like this: {noformat} {noformat} ## (/) Edit the /opt/atlassian/jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/entityengine.xml and changed it from 'hsql' to 'mssql' and delete the line with "PUBLIC" in it per the instructions in the comments in that file. ## (/) I edited the /etc/httpd/conf/httpd.conf file and created a proxy pass at the bottom of the file to point a normal URL to the default port 8080 for JIRA: {noformat} # Proxy Pass for JIRA ProxyPass http://bugs.mbari.org:8080 ProxyPassReverse http://bugs.mbari.org:8080 {noformat} ## (/) I restarted Apache ## (/) I scp'd the jtds driver from oceana to the /opt/atlassian-jira-standalone-3.13.5/common/lib directory (you could down from the internet) ## (/) I then went to the /opt/atlassian-jira-standalone-3.13.5/ directory and ran './bin/startup.sh'. From the log file, I could tell things were hanging. After some troubleshooting I am wondering if the local firewall is preventing the application to get access to the database on solstice2. I can telnet to port 1433, but I can't browse to the base http://bugs.mbari.org from anywhere but the local web browser. I have submitted a ticket. ## (/) I restarted the old JIRA with my hopes dashed :(. ## (/) Pat disabled the firewall on bugs.mbari.org but it still hung trying to connect to solstice2.shore.mbari.org. That is really, really perplexing. Neil mentioned that solstice2 is using Kerberos and solstice is not. Checking with the JTDS docs, version 1.3.1 of the driver added kerberos support, so I downloaded that driver and added the 'userKerberos=true' property to the URL in the server.xml file and restarted. Got an error about no credentials, so added user and password properties to the URL. Nope, no luck. Never did figure this one out, but I had Pat pull the VM inside the firewall and after some thrash it worked. Well, it sort of worked ... sigh. It turns out I had downloaded the standard version instead of the enterprise version. I need to redo this work ... grrr. ## (/) I deleted all the tables in the Jira_Temp database and removed the /data/jira3135/indexes directory (and recreated). ## (/) I downloaded the enterprise version of the 3.13.5 server. I made a copy in the /opt directory and unzipped and untarred the file. ## (/) I went back to crowd and edited the application to change the properties to: ### URL: http://bugs.shore.mbari.org:8080 ### IP: 134.89.12.31 ### Name: jira3135 ### Password: (ask Kevin) :) ## (/) I then repeated the steps above to get the server up and running with the following differences: ### The server name is now bugs.shore.mbari.org ### The paths given above are a little different in that they no longer say "standard" but say "enterprise" ### I deleted the proxy pass as it seemed to have issues before and this is only temporary anyway. ## (/) I then browsed to http://bugs.shore.mbari.org:8080 ## (/) It took me to the start up page and at the top was the option to 'import your existing data'. Seemed too good not to try. I clicked on the link. It asked me for the backup file location and the location where the indexes would be stored. ## (/) I copied the XML zip file and the attachments tar file to the /data/original directory. ## (/) I created the /data/jira3135/indexes and used those directories ... it fired off the import and I waited. ## (/) I tailed the log file to watch the import. Holy crap, it worked!!! I could log in and everything! I copied the results from the log file here for posterity sake: {noformat} 2015-07-22 20:55:45,156 http-8080-Processor22 INFO [jira.action.admin.DataImport] Running data import 2015-07-22 20:55:45,179 http-8080-Processor22 INFO [jira.action.admin.DataImport] Importing data.. 2015-07-22 20:55:45,186 http-8080-Processor22 INFO [jira.action.admin.DataImport] Start parsing XML with SAX Parser 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] XML successfully parsed 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] Removing all entries from the database. 2015-07-22 20:56:24,593 http-8080-Processor22 INFO [jira.action.admin.DataImport] All entries removed. 2015-07-22 20:56:24,594 http-8080-Processor22 INFO [jira.action.admin.DataImport] Started storing 410414 Generic Values 2015-07-22 21:01:51,967 http-8080-Processor22 INFO [jira.action.admin.DataImport] Finished storing Generic Values 2015-07-22 21:01:52,329 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:52,361 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:54,683 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLink' to module 'jira.user.format:profile-link-user-format'. 2015-07-22 21:01:54,724 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullName' to module 'jira.user.format:full-name-user-format'. 2015-07-22 21:01:54,773 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkSearcher' to module 'jira.user.format:profile-link-searcher-user-format'. 2015-07-22 21:01:54,784 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkExternal' to module 'jira.user.format:profile-link-external-user-format'. 2015-07-22 21:01:54,795 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkActionHeader' to module 'jira.user.format:profile-link-action-header-user-format'. 2015-07-22 21:01:54,807 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullProfile' to module 'jira.user.format:full-profile-user-format'. 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/comments 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/issues 2015-07-22 21:01:55,641 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/plugins 2015-07-22 21:01:55,867 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:01:55,871 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/issues does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:55,873 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/comments does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,033 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,257 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,889 http-8080-Processor22 ERROR [atlassian.jira.upgrade.ConsistencyCheckImpl] Attachments are turned on, but attachment path [/data/jira_3_12/attachments] invalid - disabling attachments 2015-07-22 21:02:13,904 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Detected that an upgrade is needed; existing data at build 299 2015-07-22 21:02:13,907 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Doing Upgrade... 2015-07-22 21:02:13,915 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value' succeeded 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 317 2015-07-22 21:02:13,944 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite filters - make each filter a favourite of its owner. 2015-07-22 21:02:17,822 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build319] Could not find author 'fpy' for filter with id '10040' 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite filters - make each filter a favourite of its owner.' succeeded 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 319 2015-07-22 21:02:17,995 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise Share Permissions. Move old shares to new shares. 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise Share Permissions. Move old shares to new shares.' succeeded 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 321 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Migrating the old JIRA UI colors to the new JIRA 3.13 colors 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build322] Custom color detected for jira.lf.menu.bgcolour : #336699 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Migrating the old JIRA UI colors to the new JIRA 3.13 colors' succeeded 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 322 2015-07-22 21:02:18,025 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite dashboards - make each dashboard a favourite of its owner. 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'cmcgann' for dashboard with id '10030' 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'fpy' for dashboard with id '10060' 2015-07-22 21:02:18,423 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'kanna' for dashboard with id '10040' 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite dashboards - make each dashboard a favourite of its owner.' succeeded 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 325 2015-07-22 21:02:18,625 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Reindexing all data in JIRA to include Favourites. 2015-07-22 21:02:18,648 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All starting... 2015-07-22 21:02:18,650 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 0% complete. Current index: Issue 2015-07-22 21:02:18,654 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:02:18,809 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 1% complete. Current index: Issue 2015-07-22 21:02:18,855 indexerPool-2-thread-10 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 2% complete. Current index: Issue 2015-07-22 21:02:18,899 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 3% complete. Current index: Issue 2015-07-22 21:02:18,945 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 4% complete. Current index: Issue 2015-07-22 21:02:19,012 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 5% complete. Current index: Issue . . . 2015-07-22 21:02:26,164 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 95% complete. Current index: Issue 2015-07-22 21:02:26,232 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 96% complete. Current index: Issue 2015-07-22 21:02:26,316 indexerPool-2-thread-9 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 97% complete. Current index: Issue 2015-07-22 21:02:26,771 indexerPool-2-thread-3 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: Issue 2015-07-22 21:02:27,261 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 8607ms. Indexer: DefaultIndexManager: paths: [/data/jira3135/indexes/issues, /data/jira3135/indexes/comments] 2015-07-22 21:02:27,263 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: SearchRequest 2015-07-22 21:02:27,268 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,293 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: SearchRequest 2015-07-22 21:02:27,308 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: PortalPage 2015-07-22 21:02:27,312 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,377 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: PortalPage 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 115ms. Indexer: SharedEntityIndexManager: paths: [/data/jira3135/indexes/entities/portalpage, /data/jira3135/indexes/entities/searchrequest] 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All complete. Total time: 8722ms. 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Reindexing all data in JIRA to include Favourites.' succeeded 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 326 2015-07-22 21:02:27,397 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade succeeded! Setting data build number to 360 2015-07-22 21:02:27,469 JiraQuartzScheduler_Worker-0 WARN [service.services.export.ExportService] Backup directory /data/jira_3_12/backup does not exist {noformat} {warning:title=Paths} It appears that the upgraded JIRA will still look for the attachments and the backup locations in the original places. So I created /data/jira_3_12/backup and untarred the original attachments to /data/jira_3_12 and then everything worked (including attachements) in the new JIRA. {warning} ## (/) I then used the upgraded JIRA to generate a new XML backup and stored it in /data/original/3.13.5 along with another tar of the files in /data/jira_3_12/attachments. ## (/) I then shutdown the JIRA server. *I should be ready to move on to version 4 upgrade WHEW* ## So, before moving on, I decided that it would be a really good idea to spin up a new Crowd instance to get rid of the :8443 in the URL and to move off of RedHat per IS requests. I have a ticket in for a new VM and a new database to try to get this going. I am waiting on that before moving on. ## (/) Pat created the VM and Neil created the database. ## (/) I logged into auth.mbari.org (name of the VM) and downloaded crowd which I unzipped to the /opt directory ## (/) I then created a /data/crowd directory and gave my account permissions on it and then edited the /opt/atlassian..../crowd-webapp/WEB-INF/classes/crowd-init.properties file to set that as the crowd home directory. ## (/) The instructions say to download the JDBC driver, but they already have JTDS 1.2.7 in the download so I did not do anything. ## (/) You have to manually connect up CrowdID to a database as they setup wizard does not currently do this. ### (/) They say to download the driver, but again 1.2.7 was there so I did nothing. ### (/) I edited the /opt/atlassian.../apache-tomcat/conf/Catalina/localhost/openidserver.xml to look like: {noformat} {noformat} ### (/) I edited the /opt/atlassian.../build.properties files to look like: {noformat} # Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See https://confluence.atlassian.com/display/CROWD/Connecting+Crowd+to+a+Database hibernate.dialect=org.hibernate.dialect.SQLServerDialect # The Hibernate transaction factory to use. See https://confluence.atlassian.com/display/CROWD/Configuring+Crowd hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory # The http port you wish to run crowd from, ie: http://localhost:8095/crowd crowd.tomcat.connector.port=8095 # Tomcat requires a unique port for shutdown crowd.tomcat.shutdown.port=8020 # Crowd context root crowd.url=http://localhost:8095/crowd # Demo context root demo.url=http://localhost:8095/demo # OpenID server context root openidserver.url=http://localhost:8095/openidserver {noformat} ### (/) I then ran the build.sh script in the root of /opt/atlassian... ## (/) I fired up crowd using the /opt/atlassian.../start_crowd.sh script ## (/) I then went to http://auth.mbari.org:8095/crowd to kick off the start up wizard ## (/) I grabbed a new eval license from my account on atlassian and pasted into the license page. ## (/) I selected "New install" on the next page. ## (/) I configured the JDBC connection using this connection URL with user DB_Collaboration {noformat} jdbc:jtds:sqlserver://dione.mbari.org:51001/Crowd;domain=SHORE;useNTLMv2=TRUE {noformat} ## (/) I left the "Options" as they came up {warning:title=Paths} Not sure if this is a problem, but because I started the set up using auth.mbari.org, it set the Base URL to http://auth.mbari.org:8095/crowd instead of localhost. Hope that is not a problem. We will see. {warning} ## (/) I configured the email connection using the settings from [here|https://wind.shore.mbari.org/is/howto/email/mbarimail/imap] and I used my network login (probably shouldn't be doing that ... not sure where it stores my password, but I am assuming in the DB). ## (/) For the local admin account, I created a user named 'crowdadm' so it would not clash with my LDAP account. See Kevin Gomes for password information. ## (/) I checked the OpenID server as an integrated application ## (/) It then took me to the login page and I logged in using the newly minted admin account. Seemed all is well so far. ## (/) I visited the openidserver URL as well and that seemed OK. ## (/) I decided to wait on configuring the MBARI LDAP directory until I got everything with SSL working. ## (/) Now the next step was to follow the directions to configure Crowd to run over SSL found [here|https://confluence.atlassian.com/display/CROWD/Configuring+Crowd+to+Work+with+SSL] ## (/) I shutdown crowd. Note that the stop script does not shutdown things correctly and I noticed the crowd app running as root. That should not be if I started as kgomes. Not sure what is up with that. ## (/) Now Joe had already configured SSL once, so I used his connector configuration in the server.xml file and so the final file looked like: {noformat} {noformat} ## (/) I then edited the /data/crowd/crowd.properties to look like: {noformat} #Sat Aug 01 09:05:15 PDT 2015 session.lastvalidation=session.lastvalidation session.tokenkey=session.tokenkey crowd.server.url=https\://localhost\:8443/crowd/services/ application.name=crowd http.timeout=30000 session.isauthenticated=session.isauthenticated application.login.url=https\://localhost\:8443/crowd/console/ session.validationinterval=0 application.password=Y1Xp3OorCmsOP4eruL1dmH {noformat} One thing to note here is that based on a comment from the SSL configuration page at atlassian (Steve's comment), you are supposed to leave all the host names the same. For example, if the file says localhost, leave it localhost. So this created a bit of a problem based on the fact that I had left the base URL pointing to auth.mbari.org in the wizard steps above. That step wrote auth.mbari.org to the /data/crowd/crowd.properties. All the other files reference localhost, so to be consistent, I changed auth.mbari.org to localhost in the /data/crowd/crowd.properties file. We will see if this works. ## (/) Per the instructions on the atlassian page (referenced above), I also edited the build.properties file and the /client/conf/crowd.properties files before I restarted and used the SSL URLs ## build.properties: {noformat} # Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See https://confluence.atlassian.com/display/CROWD/Connecting+Crowd+to+a+Database hibernate.dialect=org.hibernate.dialect.SQLServerDialect # The Hibernate transaction factory to use. See https://confluence.atlassian.com/display/CROWD/Configuring+Crowd hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory # The http port you wish to run crowd from, ie: http://localhost:8095/crowd crowd.tomcat.connector.port=8095 # Tomcat requires a unique port for shutdown crowd.tomcat.shutdown.port=8020 # Crowd context root crowd.url=https://localhost:8443/crowd # Demo context root demo.url=https://localhost:8443/demo # OpenID server context root openidserver.url=https://localhost:8443/openidserver {noformat} ## crowd.properties (client) {noformat} application.name crowd application.password password application.login.url https://localhost:8443/crowd/console/ crowd.server.url https://localhost:8443/crowd/services/ crowd.base.url https://localhost:8443/crowd/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 2 session.lastvalidation session.lastvalidation {noformat} ## (/) Although not stated, I am assuming you would need to run the build.sh script to push the build.properties changes to their proper places, so I did that. Note that before doing that, I know that it will clobber the server.xml changes I made, so I made a copy of that file and diff'd them after and then rolled the previous changes to the new server.xml file. Actually, amazingly enough, it seems to have done the connector entry correctly so I left it after running the build.sh script. ## (/) Crossed my fingers and then restarted crowd. I tailed the catalina.out file and did not see any stack traces so that is a good sign! ## (/) I visited https://auth.mbari.org:8443/crowd first. It could not find that page, but I suspect that is because I am browsing from the outside, so I tried just https://auth.mbari.org/crowd and got a service unavailable. I am suspecting that this is a combination of firewall and proxy pass and I will send this info to Joe. From what I can see on the crowd side, it seems like the server started cleanly, we just can't get to it. I tried to reach it from a browser on the machine itself too (through VNC) with the same service not available. ## (/) Here are the notes from Joe after he fixed it! Wooohooo! {noformat} Hey Kevin, Thanks for starting clean! I had to make a few adjustments. 1-I modified the server.xml file in /opt/atlassian-crowd-2.8.3/apache-tomcat/conf/server.xml so there are two connectors per the instructions on the Atlassian site. I have backed up this good server.xml file in /etc/temp/ if you want to browse it to see what I did. Of note is that I removed all the jargon referencing the types of ciphers available to simplify things for now. 2-I modified /data/crowd/crowd.properties to have crowd.server.url=https\://localhost\:8443/crowd/services/ application.login.url=https\://localhost\:8443/crowd/console/ But that would cause my login to error with an error saying it was unable to reach the authentication server. I scratched my head for a bit. When I revert the values to just using non-SSL and try to log in, I just get an "invalid login" (I don't know the crowdadm password). So I worked under the assumption that if I can configure SSL to get an "invalid login" when logging in then it would work when provided real credentials. So, I then changed /data/crowd/crowd.proprties to: crowd.server.url=https\://auth.mbari.org\:8443/crowd/services/ application.login.url=https\://auth.mbari.org\:8443/crowd/console/ And now when I try to log in with SSL it says "invalid login". Strange because all the other values I can find only show "localhost" .. in any case... Can you try to log in now? {noformat} ## (/) Next I moved on to configuring the connection to MBARI's LDAP server to enable our logins through Crowd and CrowdID ## (/) I clicked on "Add Directory" in crowd. ## (/) I selected "Connector" then clicked Next ## (/) I put ldap.shore.mbari.org as the name of the server ## (/) I selected "Use memberOf for group memberships" ## (/) I used "OU=AllUsers,DC=shore,DC=mbari,DC=org" for the Base DN ## (/) I used "CN=LDAPbind,OU=Special,OU=AllUsers,DC=shore,DC=mbari,DC=org" for the Username (talk to Pat Allen for password) ## (/) I tested the connection (button click) and it passed. ## (/) I de-selected all the capabilities of the connector as it is a ready only connector and then saved it. It synchronized correctly! ## (/) At first, I could not login using my MBARI credentials, but after going to the "crowd" application in crowd (logged in as the local admin), I had to add the LDAP directory and configure it to "Allow all to authenticate", then I was able to login. After this, the last step was to get this to run as a different user and lock down various directories. I went through the entire directory structure /opt/atlassian... and set up so that root owned all read-only locations and DB_Collaboration (account set up by IS) owned the other stuff. I also gave full ownership to the /data/crowd directory to DB_Collaboration so it could write there. Pat set up a script to start on boot and after a little tweaking, it now starts on boot. {warning:title=CrowdID log file} One thing that came up here was that when the crowdID application ran, it tried to write a log file to the location where the process was launched from (which is /opt/atlassian...). This is a bad thing and I figured out that I could change that location by changing the file /opt/atlassian-crowd-2.8.3/crowd-openidserver-webapp/WEB-INF/classes/log4j.properties and hardcoding the /data/crowd/logs/atlassian-crowd-openid-server.log and then restarted the application. {warning} ## (/) Another note is the when an application tried to use the OpenID application, it would get redirected to localhost. I changed the /opt/atlassian.../crowd-openidserver-webapp/WEB-INF/classes/crowd.properties file to look like: {noformat} #Sat Aug 01 10:03:18 PDT 2015 session.lastvalidation=session.lastvalidation session.tokenkey=session.tokenkey crowd.server.url=http\://localhost\:8095/crowd/services/ application.name=crowd-openid-server #application.login.url.template=http\://localhost\:8095/openidserver?returnToUrl\=${RETURN_TO_URL} application.login.url.template=https\://auth.mbari.org/openidserver?returnToUrl\=${RETURN_TO_URL} session.isauthenticated=session.isauthenticated #application.base.url=http\://localhost\:8095/openidserver application.base.url=https\://auth.mbari.org/openidserver #application.login.url=http\://localhost\:8095/openidserver application.login.url=https\://auth.mbari.org/openidserver session.validationinterval=0 application.password=password {noformat} and that seems to have fixed it. # (/) It is finally time to move on to the version 4 upgrade ... holy crap. I first went to the *new* crowd install (auth.mbari.org) and logged in as the crowdadm. # (/) I clicked on Applications, then on Add Application # (/) I selected JIRA from the Application type drop-down # (/) I entered jira445 as the username. Ask Kevin about the password. # (/) I used http://bugs.shore.mbari.org:8081 as the URL # (/) I used 134.89.12.31 as the IP address. # (/) I selected only the MBARI LDAP directory. # (/) Then I selected "Allow all users to authenticate" # (/) Then I clicked on "Add Application" # (/) I VNC'd into bugs.mbari.org. As it turns out, for Linux, there is an installer program to download. I downloaded the .bin for 64 bit Linux installer and moved it to the jira-upgrade directory. # (/) I chmod'd the file to make it executable and ran it. It gave me a warning about not being root, but I went ahead with it. # (/) It asked for the JIRA home and data directory, which I specified as /opt/jira4 and /data/jira445. # (/) For the ports, I specified 8180 and 8105 (HTTP and control respectively). It then extracted all the files and launched JIRA. It said if finished, so I opened a local browser to http://localhost:8180 which kicked off the start up wizard. # (/) I specified the external database using: ## solstice2.shore.mbari.org (server) ## 1433 (port) ## jira4 (database) ## DB_Collaboration (username) ## (password ask Kevin) ## dbo (schema) # But all this failed as it seems to just want to try and use the SQL server authentication instead of domain. I will have to do it manually. # (/) I stopped the server using the bin/stop-jira.sh script. # (/) I created and edited /data/jira445/dbconfig.xml and made it look like the following: {noformat} ?xml version="1.0" encoding="UTF-8"?> defaultDS default mssql jiraschema jdbc:jtds:sqlserver://solstice2.shore.mbari.org:1433/Jira4;domain=SHORE;useNTLMv2=true net.sourceforge.jtds.jdbc.Driver DB_Collaboration (ask Kevin) 15 {noformat} # (/) I then started it again using bin/start-jira.sh and tailed the catalina.out file. Got a bunch of errors related to the schema 'jiraschema', I edited the file and changed the schema to 'dbo' and restarted. That seemed to do it. There was one stack trace for some iCal plugin, but looks OK other than that. # I browsed back to localhost:8180 and the wizard moved to step 2. There was an option to import existing data bit without the crowd connection, I thought I should set it up manually, connect to crowd, then import. I generated an evaluation license, called the app "MBARI JIRA4" and change the server in the url to bugs.shore.mbari.org # For the admin, I created an account called 'jiraadm' (ask Kevin for password). # Since this is a temporary system, I left the email system disabled. # I logged in as jiraadm, went to Administration, then Users, then clicked on Add Directory and chose Atlassian Crowd. Note that I had to set the server URL to http://auth.mbari.org:8095/crowd or I would have had to configure all this SSL crap that I did not want to do for this temporary install. # It tested successfully, I clicked Save and it went through a 13 second sync, whew! # I then went to System->Import and Export->Restore System # I copied the jira-upgrade-3.13.5.zip file from the previous version export into /data/jira445/import and then entered that file name along with the new evaluation license again. # I worked through progress bar after I clicked on Restore (it took a really long time). # I then stopped, restarted and tailed the log file. # I am thinking now I should have put the attachments in the import attachments directory, but I am hoping I can just copy them to the data/attachments directory. # UG! I got some error during the import. The exception read: "JIRA is unable to migrat the User Directory configuration because external users exist but the osuser.xml file is not available". It then gave me a link to a doc that talked about making the old user files available before the upgrade ... crap. So I needed to copy the osuser.xml and crowd.properties file from atlassian-jira/WEB-INF/classes directory on the old install to the same directory on the new install ... sigh. This means I am going to blow away everything and start over. # I shutdown jira4 # I dropped all things in the database and deleted all content in the /data/jira445 directory (except for the dbconfig.xml file). # I also removed the temp, logs (actually you have to leave the directory, just clear the files) and the work/Catalina/localhost directories from the jira installation. # I then copied the osuser.xml and the crowd.properties files from the 3.13.5 install to the 4 install. # I edited the crowd.properties file in hopes that I could point it to the new crowd install on auth.mbari.org and it would work, but we will see. # I then started jira and tailed the log file. # All looked OK (other than iCal plugin stack trace again), so I went to localhost:8180 and got step 2 of the wizard. I used the same info as before. # I logged in as the local admin account and it looks like the system picked up the crowd connection, but lets see what server it used! Hey it used the one I edited into the file! Sweet ... now let's see if the import works. # I copied the 3.13.5 zip file to the import directory again and this time, I untarred the attachments into the import/attachments directory. # I kicked off the restore as before and it worked through it fine. # Shutdown and restarted system, tailing the log file and then went to localhost:8180 # I can see issues (before logging in) and it all looks good!! The attachments did not move over from the import directory, so I copied the tar file from /data/jira445/import to /data/jira445/data and then untarred it there, then removed the tar file and the import zip file from the import directory. # Now I will try to login using my MBARI account and OMG it actually worked!!! (it even gave my kgomes account Admin privs) # I then performed an export and copied those file to the /data/backups/4.4.5 directory (also created a TAR of the attachments and put there too). # Now on to version 5! # OK, so something strange is happening. After the imports, the server ID goes back to the one that is on our current production server, which must mean it is using our current license key (which does not match the server ID, BTW). Oh well, I will press on! # I created a /data/jira5211 directory as well as a /opt/jira5 directory. Knowing what I know now and reading through the install instructions, it appears that I need to create a dbconfig.xml file manually, so I did that using: {noformat} defaultDS default mssql dbo jdbc:jtds:sqlserver://solstice2.shore.mbari.org:1433/Jira5;domain=SHORE;useNTLMv2=true net.sourceforge.jtds.jdbc.Driver DB_Collaboration (ask Kevin) 20 20 30000 20 true 300 select 1 60000 300000 true false {noformat} # I then changed the mode to executable on the installer download and ran that. # I had to choose a "custom install" this time through, but the properties were similar after that (ports I used were 8280 and 8205) # I then browsed to localhost:8280 # I dropped me to a wizard where I define the title as "MBARI JIRA5", and changed host to bugs.shore.mbari.org (from localhost) # This license was a little different in that is just asked for my Atlassian username and password and fetched a new license for me. # For the admin account, I used the same 'jiraadm' account # Left email notification disabled. # I created a new application in crowd for JIRA 5 and used same account info as for 4. # In JIRA, I went to Administration->Users->User Directories and then added a directory as I had done before. # All went well and the sync happened. # I then went to Administration->System->Import and Export->Restore System # I copied the backup of 4.4.5 to the /data/jira5211/import directory and then specified that file name. I did not specify a license as it seems to use the old one and it said so in the text below the box. # Clicked on restore and while it was restoring, I untarred the attachments to the /data/jira5211/data directory # After the restore, I shutdown and restarted JIRA tailing the log file. # Browsed to localhost:8280 and ... success! I see issues before logging in and ... my MBARI login worked, I was admin and all is good!!!! # As with previous version, I ran a backup of the DB and attachments and placed in /data/backups/5.2.11 # I poked around a little and there seems to be an issue in the comments that they are still referencing oceana??? I will have to look into this. # I then re-did the process once again for version 6.4.9. I will only put notes about things that are dramatically different below: ## It looks like the dbconfig.xml file is the same as it is for version 5, so I just copied and edited to point to Jira6 DB. ## I used ports 8380 and 8305 {warning:title=Collation} The DB needs to be using a specific collation that it's not, I will have to correct that on the production run {warning} ## It gave me a choice on "how I wanted to use JIRA" and I chose the default (top) one which was just JIRA. ## Something did not go well on the restore (got to 90%) from backup up and the server seems to have crashed, but it looks like it tried to restart? ## I forced a stop and start and tailed the log file. Could it be related to the collation issue? Upon restart it re-ran the indexing. Looks like it worked OK, let me login with my MBARI account. ## Interesting, the comments pointing to oceana seems to have fixed itself in the step of the upgrade. ## Another interesting note, when I went to the Admin->System->General configuration, it had the base URL as oceana, that would explain it. So I edited that to bugs.shore.mbari.org (it also made me change the Mode to private, which makes sense since authentication is external). ## I went back to the 3, 4, and 5 install and changed the base URL there too. That fixed that issue. # I then sent an email to all hands giving the URLs for folks to look at. # While folks were looking over the upgrade instances, I went ahead and created the cloud instance at Atlassian so I could test upload the JIRA backup from 6.4.9 {warning:title=Disable Remote Crowd Directory} As a part of the test import, I discovered that you have to disable the remote crowd directory through User Management->User Directories *before* you do the backup/export. {warning} # You basically do a backup of the system, tar up the attachments and then push those files to the cloud instance through WebDAV. Then you choose those files to do a 'JIRA Import'. The attachments did not work and I had to leave those de-selected and then submitted a ticket for that to be done. # It did seem to import all the users from our LDAP system, so I had to go through and 'Deactivate' all the users that I did not think would login. The billing adjusts fine to that, so that seems tractable. I am still working on seeing how users login to their imported accounts and if you can link BitBucket accounts to JIRA. ]]> 28016661 27099545 27066782 28049431 4.4: [https://confluence.atlassian.com/display/JIRA044/Migrating+JIRA+to+Another+Server] ## The JIRA configuration tool: [https://confluence.atlassian.com/display/JIRA044/Using+the+JIRA+Configuration+Tool] h5. Steps # (/) Create new VM named bugs.mbari.org in the DMZ # (/) Have Neil create database Jira_Temp on solstice2.shore.mbari.org # (/) Have Neil create database Jira on solstice2.shore.mbari.org # (/) Have Pat install Java 7 on bugs.shore.mbari.org # (/) Have Pete plumb holes through firewall so processes on bugs.mbari.org can get to Solstice2 # (/) Have Pat create DB_Collaboration account on bugs so it can run JIRA under that account and it can connect to solstice2 using that NT Domain account. # (/) Upgrade license on Atlassian site # (/) Log into bugs.shore.mbari.org # (/) Download 3.13.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 4.4.5 standalone Linux 64 bit tar.gz # (/) Unzip and untar the file to /opt # (/) Download 5.2.11 standalone Linux 64 bit tar.gz (not sure this version is necessary, but at least I have it) # (/) Unzip and untar the file to /opt # (/) Download latest JIRA (6.4.7 as of this writing). # (/) Unzip and untar it to /opt # Performed Test Upgrade ## (/) In order to export the current stuff in JIRA, I had to shut off access so people could not change the data while I was backing it up. ## (/) I ssh'd to oceana.mbari.org as root and edited the /opt/jira/conf/server.xml file and commented out the Connector section that had the port of 8010 to shut it off from the normal serving route. ## (/) I uncommented the 8082 port connector and the 8443 port connector so that I could still get to the server. ## (/) I stopped and started the JIRA server and in the log file I got a "keystore was tampered with..." which is not surprising. ## (/) I could then browser over to http://oceana.mbari.org:8082/jira ## (/) Then through the Administration console, I did an XML backup ## (/) I then created a tar of all the attachments in the /data/jira_3_12/attachments directory ## (/) I moved both the XML and tar files to the /root/jira-upgrade directory ## (/) I then reversed the changes to the server.xml file and shut down JIRA ## (/) I left it down during the next steps in case it went so well, I could just point people to the new server (yeah, right). ## (/) I then browsed to the crowd server on oceana and add a new application using: ### URL: http://bugs.mbari.org/jira3135 ### IP: 134.89.2.29 ### Name: JIRA3135 ### Password: (ask Kevin) :) ## (/) On bugs, I made a copy of the JIRA 3.13.5 download in the /opt directory and unzipped and untarred it. ## (/) In order to configure the crowd connection I did the following: ### (/) I scp'd the /opt/crowd/client/crowd-integration-client-1.6.jar file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I removed the existing 1.6.1 crowd client jar from the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/lib directory ### (/) I scp'd the /opt/crowd/client/conf/crowd.properties file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I scp'd the /opt/crowd/client/conf/crowd-ehcache.xml file from oceana to the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes directory ### (/) I edited the crowd.properties file on bugs to look like: {noformat} application.name JIRA3135 application.password (ask Kevin) application.login.url http://oceana.mbari.org:8095/crowd/console/ crowd.server.url http://oceana.mbari.org:8095/crowd/services/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 0 session.lastvalidation session.lastvalidation {noformat} ### (/) I edited the /opt/atlassian-jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/osuser.xml file to comment out the current authentication mechanism and then uncomment the crowd one. ## (/) I then edited the /opt/atlassian-jira-standalone-3.13.5/conf/server/xml file and configured the database connection to the Jira_Temp database on Solstice2. I looked like this: {noformat} {noformat} ## (/) Edit the /opt/atlassian/jira-standalone-3.13.5/atlassian-jira/WEB-INF/classes/entityengine.xml and changed it from 'hsql' to 'mssql' and delete the line with "PUBLIC" in it per the instructions in the comments in that file. ## (/) I edited the /etc/httpd/conf/httpd.conf file and created a proxy pass at the bottom of the file to point a normal URL to the default port 8080 for JIRA: {noformat} # Proxy Pass for JIRA ProxyPass http://bugs.mbari.org:8080 ProxyPassReverse http://bugs.mbari.org:8080 {noformat} ## (/) I restarted Apache ## (/) I scp'd the jtds driver from oceana to the /opt/atlassian-jira-standalone-3.13.5/common/lib directory (you could down from the internet) ## (/) I then went to the /opt/atlassian-jira-standalone-3.13.5/ directory and ran './bin/startup.sh'. From the log file, I could tell things were hanging. After some troubleshooting I am wondering if the local firewall is preventing the application to get access to the database on solstice2. I can telnet to port 1433, but I can't browse to the base http://bugs.mbari.org from anywhere but the local web browser. I have submitted a ticket. ## (/) I restarted the old JIRA with my hopes dashed :(. ## (/) Pat disabled the firewall on bugs.mbari.org but it still hung trying to connect to solstice2.shore.mbari.org. That is really, really perplexing. Neil mentioned that solstice2 is using Kerberos and solstice is not. Checking with the JTDS docs, version 1.3.1 of the driver added kerberos support, so I downloaded that driver and added the 'userKerberos=true' property to the URL in the server.xml file and restarted. Got an error about no credentials, so added user and password properties to the URL. Nope, no luck. Never did figure this one out, but I had Pat pull the VM inside the firewall and after some thrash it worked. Well, it sort of worked ... sigh. It turns out I had downloaded the standard version instead of the enterprise version. I need to redo this work ... grrr. ## (/) I deleted all the tables in the Jira_Temp database and removed the /data/jira3135/indexes directory (and recreated). ## (/) I downloaded the enterprise version of the 3.13.5 server. I made a copy in the /opt directory and unzipped and untarred the file. ## (/) I went back to crowd and edited the application to change the properties to: ### URL: http://bugs.shore.mbari.org:8080 ### IP: 134.89.12.31 ### Name: jira3135 ### Password: (ask Kevin) :) ## (/) I then repeated the steps above to get the server up and running with the following differences: ### The server name is now bugs.shore.mbari.org ### The paths given above are a little different in that they no longer say "standard" but say "enterprise" ### I deleted the proxy pass as it seemed to have issues before and this is only temporary anyway. ## (/) I then browsed to http://bugs.shore.mbari.org:8080 ## (/) It took me to the start up page and at the top was the option to 'import your existing data'. Seemed too good not to try. I clicked on the link. It asked me for the backup file location and the location where the indexes would be stored. ## (/) I copied the XML zip file and the attachments tar file to the /data/original directory. ## (/) I created the /data/jira3135/indexes and used those directories ... it fired off the import and I waited. ## (/) I tailed the log file to watch the import. Holy crap, it worked!!! I could log in and everything! I copied the results from the log file here for posterity sake: {noformat} 2015-07-22 20:55:45,156 http-8080-Processor22 INFO [jira.action.admin.DataImport] Running data import 2015-07-22 20:55:45,179 http-8080-Processor22 INFO [jira.action.admin.DataImport] Importing data.. 2015-07-22 20:55:45,186 http-8080-Processor22 INFO [jira.action.admin.DataImport] Start parsing XML with SAX Parser 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] XML successfully parsed 2015-07-22 20:56:24,211 http-8080-Processor22 INFO [jira.action.admin.DataImport] Removing all entries from the database. 2015-07-22 20:56:24,593 http-8080-Processor22 INFO [jira.action.admin.DataImport] All entries removed. 2015-07-22 20:56:24,594 http-8080-Processor22 INFO [jira.action.admin.DataImport] Started storing 410414 Generic Values 2015-07-22 21:01:51,967 http-8080-Processor22 INFO [jira.action.admin.DataImport] Finished storing Generic Values 2015-07-22 21:01:52,329 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:52,361 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:54,683 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLink' to module 'jira.user.format:profile-link-user-format'. 2015-07-22 21:01:54,724 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullName' to module 'jira.user.format:full-name-user-format'. 2015-07-22 21:01:54,773 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkSearcher' to module 'jira.user.format:profile-link-searcher-user-format'. 2015-07-22 21:01:54,784 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkExternal' to module 'jira.user.format:profile-link-external-user-format'. 2015-07-22 21:01:54,795 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'profileLinkActionHeader' to module 'jira.user.format:profile-link-action-header-user-format'. 2015-07-22 21:01:54,807 http-8080-Processor22 INFO [jira.plugin.profile.DefaultUserFormatMapper] Mapping type 'fullProfile' to module 'jira.user.format:full-profile-user-format'. 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/comments 2015-07-22 21:01:55,640 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/issues 2015-07-22 21:01:55,641 http-8080-Processor22 ERROR [atlassian.jira.util.FileFactory] Unable to delete directory /data/jira3135/indexes/plugins 2015-07-22 21:01:55,867 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:01:55,871 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/issues does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:01:55,873 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/comments does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,033 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,257 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:13,889 http-8080-Processor22 ERROR [atlassian.jira.upgrade.ConsistencyCheckImpl] Attachments are turned on, but attachment path [/data/jira_3_12/attachments] invalid - disabling attachments 2015-07-22 21:02:13,904 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Detected that an upgrade is needed; existing data at build 299 2015-07-22 21:02:13,907 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Doing Upgrade... 2015-07-22 21:02:13,915 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Set application property 'webwork.multipart.maxSize' to default value if not set or invalid value' succeeded 2015-07-22 21:02:13,936 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 317 2015-07-22 21:02:13,944 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite filters - make each filter a favourite of its owner. 2015-07-22 21:02:17,822 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build319] Could not find author 'fpy' for filter with id '10040' 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite filters - make each filter a favourite of its owner.' succeeded 2015-07-22 21:02:17,990 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 319 2015-07-22 21:02:17,995 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise Share Permissions. Move old shares to new shares. 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise Share Permissions. Move old shares to new shares.' succeeded 2015-07-22 21:02:18,003 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 321 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Migrating the old JIRA UI colors to the new JIRA 3.13 colors 2015-07-22 21:02:18,008 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build322] Custom color detected for jira.lf.menu.bgcolour : #336699 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Migrating the old JIRA UI colors to the new JIRA 3.13 colors' succeeded 2015-07-22 21:02:18,021 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 322 2015-07-22 21:02:18,025 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Initialise favourite dashboards - make each dashboard a favourite of its owner. 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'cmcgann' for dashboard with id '10030' 2015-07-22 21:02:18,272 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'fpy' for dashboard with id '10060' 2015-07-22 21:02:18,423 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build325] Could not find owner 'kanna' for dashboard with id '10040' 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Initialise favourite dashboards - make each dashboard a favourite of its owner.' succeeded 2015-07-22 21:02:18,618 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 325 2015-07-22 21:02:18,625 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Reindexing all data in JIRA to include Favourites. 2015-07-22 21:02:18,648 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All starting... 2015-07-22 21:02:18,650 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 0% complete. Current index: Issue 2015-07-22 21:02:18,654 http-8080-Processor22 INFO [jira.issue.index.DefaultIndexManager] Reindexing all issues 2015-07-22 21:02:18,809 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 1% complete. Current index: Issue 2015-07-22 21:02:18,855 indexerPool-2-thread-10 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 2% complete. Current index: Issue 2015-07-22 21:02:18,899 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 3% complete. Current index: Issue 2015-07-22 21:02:18,945 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 4% complete. Current index: Issue 2015-07-22 21:02:19,012 indexerPool-2-thread-7 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 5% complete. Current index: Issue . . . 2015-07-22 21:02:26,164 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 95% complete. Current index: Issue 2015-07-22 21:02:26,232 indexerPool-2-thread-5 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 96% complete. Current index: Issue 2015-07-22 21:02:26,316 indexerPool-2-thread-9 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 97% complete. Current index: Issue 2015-07-22 21:02:26,771 indexerPool-2-thread-3 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: Issue 2015-07-22 21:02:27,261 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 8607ms. Indexer: DefaultIndexManager: paths: [/data/jira3135/indexes/issues, /data/jira3135/indexes/comments] 2015-07-22 21:02:27,263 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 98% complete. Current index: SearchRequest 2015-07-22 21:02:27,268 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/searchrequest does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,293 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: SearchRequest 2015-07-22 21:02:27,308 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 99% complete. Current index: PortalPage 2015-07-22 21:02:27,312 http-8080-Processor22 WARN [atlassian.jira.util.LuceneUtils] Directory /data/jira3135/indexes/entities/portalpage does not exist - perhaps it was deleted? Creating.. 2015-07-22 21:02:27,377 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: PortalPage 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex took: 115ms. Indexer: SharedEntityIndexManager: paths: [/data/jira3135/indexes/entities/portalpage, /data/jira3135/indexes/entities/searchrequest] 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.upgrade.tasks.UpgradeTask_Build326] Re-indexing is 100% complete. Current index: 2015-07-22 21:02:27,384 http-8080-Processor22 INFO [jira.util.index.IndexLifecycleManager$Composite] Reindex All complete. Total time: 8722ms. 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Reindexing all data in JIRA to include Favourites.' succeeded 2015-07-22 21:02:27,389 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number on to 326 2015-07-22 21:02:27,397 http-8080-Processor22 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade succeeded! Setting data build number to 360 2015-07-22 21:02:27,469 JiraQuartzScheduler_Worker-0 WARN [service.services.export.ExportService] Backup directory /data/jira_3_12/backup does not exist {noformat} {warning:title=Paths} It appears that the upgraded JIRA will still look for the attachments and the backup locations in the original places. So I created /data/jira_3_12/backup and untarred the original attachments to /data/jira_3_12 and then everything worked (including attachements) in the new JIRA. {warning} ## (/) I then used the upgraded JIRA to generate a new XML backup and stored it in /data/original/3.13.5 along with another tar of the files in /data/jira_3_12/attachments. ## (/) I then shutdown the JIRA server. *I should be ready to move on to version 4 upgrade WHEW* ## So, before moving on, I decided that it would be a really good idea to spin up a new Crowd instance to get rid of the :8443 in the URL and to move off of RedHat per IS requests. I have a ticket in for a new VM and a new database to try to get this going. I am waiting on that before moving on. ## (/) Pat created the VM and Neil created the database. ## (/) I logged into auth.mbari.org (name of the VM) and downloaded crowd which I unzipped to the /opt directory ## (/) I then created a /data/crowd directory and gave my account permissions on it and then edited the /opt/atlassian..../crowd-webapp/WEB-INF/classes/crowd-init.properties file to set that as the crowd home directory. ## (/) The instructions say to download the JDBC driver, but they already have JTDS 1.2.7 in the download so I did not do anything. ## (/) You have to manually connect up CrowdID to a database as they setup wizard does not currently do this. ### (/) They say to download the driver, but again 1.2.7 was there so I did nothing. ### (/) I edited the /opt/atlassian.../apache-tomcat/conf/Catalina/localhost/openidserver.xml to look like: {noformat} {noformat} ### (/) I edited the /opt/atlassian.../build.properties files to look like: {noformat} # Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See https://confluence.atlassian.com/display/CROWD/Connecting+Crowd+to+a+Database hibernate.dialect=org.hibernate.dialect.SQLServerDialect # The Hibernate transaction factory to use. See https://confluence.atlassian.com/display/CROWD/Configuring+Crowd hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory # The http port you wish to run crowd from, ie: http://localhost:8095/crowd crowd.tomcat.connector.port=8095 # Tomcat requires a unique port for shutdown crowd.tomcat.shutdown.port=8020 # Crowd context root crowd.url=http://localhost:8095/crowd # Demo context root demo.url=http://localhost:8095/demo # OpenID server context root openidserver.url=http://localhost:8095/openidserver {noformat} ### (/) I then ran the build.sh script in the root of /opt/atlassian... ## (/) I fired up crowd using the /opt/atlassian.../start_crowd.sh script ## (/) I then went to http://auth.mbari.org:8095/crowd to kick off the start up wizard ## (/) I grabbed a new eval license from my account on atlassian and pasted into the license page. ## (/) I selected "New install" on the next page. ## (/) I configured the JDBC connection using this connection URL with user DB_Collaboration {noformat} jdbc:jtds:sqlserver://dione.mbari.org:51001/Crowd;domain=SHORE;useNTLMv2=TRUE {noformat} ## (/) I left the "Options" as they came up {warning:title=Paths} Not sure if this is a problem, but because I started the set up using auth.mbari.org, it set the Base URL to http://auth.mbari.org:8095/crowd instead of localhost. Hope that is not a problem. We will see. {warning} ## (/) I configured the email connection using the settings from [here|https://wind.shore.mbari.org/is/howto/email/mbarimail/imap] and I used my network login (probably shouldn't be doing that ... not sure where it stores my password, but I am assuming in the DB). ## (/) For the local admin account, I created a user named 'crowdadm' so it would not clash with my LDAP account. See Kevin Gomes for password information. ## (/) I checked the OpenID server as an integrated application ## (/) It then took me to the login page and I logged in using the newly minted admin account. Seemed all is well so far. ## (/) I visited the openidserver URL as well and that seemed OK. ## (/) I decided to wait on configuring the MBARI LDAP directory until I got everything with SSL working. ## (/) Now the next step was to follow the directions to configure Crowd to run over SSL found [here|https://confluence.atlassian.com/display/CROWD/Configuring+Crowd+to+Work+with+SSL] ## (/) I shutdown crowd. Note that the stop script does not shutdown things correctly and I noticed the crowd app running as root. That should not be if I started as kgomes. Not sure what is up with that. ## (/) Now Joe had already configured SSL once, so I used his connector configuration in the server.xml file and so the final file looked like: {noformat} {noformat} ## (/) I then edited the /data/crowd/crowd.properties to look like: {noformat} #Sat Aug 01 09:05:15 PDT 2015 session.lastvalidation=session.lastvalidation session.tokenkey=session.tokenkey crowd.server.url=https\://localhost\:8443/crowd/services/ application.name=crowd http.timeout=30000 session.isauthenticated=session.isauthenticated application.login.url=https\://localhost\:8443/crowd/console/ session.validationinterval=0 application.password=Y1Xp3OorCmsOP4eruL1dmH {noformat} One thing to note here is that based on a comment from the SSL configuration page at atlassian (Steve's comment), you are supposed to leave all the host names the same. For example, if the file says localhost, leave it localhost. So this created a bit of a problem based on the fact that I had left the base URL pointing to auth.mbari.org in the wizard steps above. That step wrote auth.mbari.org to the /data/crowd/crowd.properties. All the other files reference localhost, so to be consistent, I changed auth.mbari.org to localhost in the /data/crowd/crowd.properties file. We will see if this works. ## (/) Per the instructions on the atlassian page (referenced above), I also edited the build.properties file and the /client/conf/crowd.properties files before I restarted and used the SSL URLs ## build.properties: {noformat} # Modify the attributes of this file to quickly adjust the deployment values of Crowd. # The Hibernate database dialect to use. See https://confluence.atlassian.com/display/CROWD/Connecting+Crowd+to+a+Database hibernate.dialect=org.hibernate.dialect.SQLServerDialect # The Hibernate transaction factory to use. See https://confluence.atlassian.com/display/CROWD/Configuring+Crowd hibernate.transaction.factory_class=org.hibernate.transaction.JDBCTransactionFactory # The http port you wish to run crowd from, ie: http://localhost:8095/crowd crowd.tomcat.connector.port=8095 # Tomcat requires a unique port for shutdown crowd.tomcat.shutdown.port=8020 # Crowd context root crowd.url=https://localhost:8443/crowd # Demo context root demo.url=https://localhost:8443/demo # OpenID server context root openidserver.url=https://localhost:8443/openidserver {noformat} ## crowd.properties (client) {noformat} application.name crowd application.password password application.login.url https://localhost:8443/crowd/console/ crowd.server.url https://localhost:8443/crowd/services/ crowd.base.url https://localhost:8443/crowd/ session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 2 session.lastvalidation session.lastvalidation {noformat} ## (/) Although not stated, I am assuming you would need to run the build.sh script to push the build.properties changes to their proper places, so I did that. Note that before doing that, I know that it will clobber the server.xml changes I made, so I made a copy of that file and diff'd them after and then rolled the previous changes to the new server.xml file. Actually, amazingly enough, it seems to have done the connector entry correctly so I left it after running the build.sh script. ## (/) Crossed my fingers and then restarted crowd. I tailed the catalina.out file and did not see any stack traces so that is a good sign! ## (/) I visited https://auth.mbari.org:8443/crowd first. It could not find that page, but I suspect that is because I am browsing from the outside, so I tried just https://auth.mbari.org/crowd and got a service unavailable. I am suspecting that this is a combination of firewall and proxy pass and I will send this info to Joe. From what I can see on the crowd side, it seems like the server started cleanly, we just can't get to it. I tried to reach it from a browser on the machine itself too (through VNC) with the same service not available. ## (/) Here are the notes from Joe after he fixed it! Wooohooo! {noformat} Hey Kevin, Thanks for starting clean! I had to make a few adjustments. 1-I modified the server.xml file in /opt/atlassian-crowd-2.8.3/apache-tomcat/conf/server.xml so there are two connectors per the instructions on the Atlassian site. I have backed up this good server.xml file in /etc/temp/ if you want to browse it to see what I did. Of note is that I removed all the jargon referencing the types of ciphers available to simplify things for now. 2-I modified /data/crowd/crowd.properties to have crowd.server.url=https\://localhost\:8443/crowd/services/ application.login.url=https\://localhost\:8443/crowd/console/ But that would cause my login to error with an error saying it was unable to reach the authentication server. I scratched my head for a bit. When I revert the values to just using non-SSL and try to log in, I just get an "invalid login" (I don't know the crowdadm password). So I worked under the assumption that if I can configure SSL to get an "invalid login" when logging in then it would work when provided real credentials. So, I then changed /data/crowd/crowd.proprties to: crowd.server.url=https\://auth.mbari.org\:8443/crowd/services/ application.login.url=https\://auth.mbari.org\:8443/crowd/console/ And now when I try to log in with SSL it says "invalid login". Strange because all the other values I can find only show "localhost" .. in any case... Can you try to log in now? {noformat} ## (/) Next I moved on to configuring the connection to MBARI's LDAP server to enable our logins through Crowd and CrowdID ## (/) I clicked on "Add Directory" in crowd. ## (/) I selected "Connector" then clicked Next ## (/) I put ldap.shore.mbari.org as the name of the server ## (/) I selected "Use memberOf for group memberships" ## (/) I used "OU=AllUsers,DC=shore,DC=mbari,DC=org" for the Base DN ## (/) I used "CN=LDAPbind,OU=Special,OU=AllUsers,DC=shore,DC=mbari,DC=org" for the Username (talk to Pat Allen for password) ## (/) I tested the connection (button click) and it passed. ## (/) I de-selected all the capabilities of the connector as it is a ready only connector and then saved it. It synchronized correctly! ## (/) At first, I could not login using my MBARI credentials, but after going to the "crowd" application in crowd (logged in as the local admin), I had to add the LDAP directory and configure it to "Allow all to authenticate", then I was able to login. After this, the last step was to get this to run as a different user and lock down various directories. I went through the entire directory structure /opt/atlassian... and set up so that root owned all read-only locations and DB_Collaboration (account set up by IS) owned the other stuff. I also gave full ownership to the /data/crowd directory to DB_Collaboration so it could write there. Pat set up a script to start on boot and after a little tweaking, it now starts on boot. {warning:title=CrowdID log file} One thing that came up here was that when the crowdID application ran, it tried to write a log file to the location where the process was launched from (which is /opt/atlassian...). This is a bad thing and I figured out that I could change that location by changing the file /opt/atlassian-crowd-2.8.3/crowd-openidserver-webapp/WEB-INF/classes/log4j.properties and hardcoding the /data/crowd/logs/atlassian-crowd-openid-server.log and then restarted the application. {warning} ## (/) Another note is the when an application tried to use the OpenID application, it would get redirected to localhost. I changed the /opt/atlassian.../crowd-openidserver-webapp/WEB-INF/classes/crowd.properties file to look like: {noformat} #Sat Aug 01 10:03:18 PDT 2015 session.lastvalidation=session.lastvalidation session.tokenkey=session.tokenkey crowd.server.url=http\://localhost\:8095/crowd/services/ application.name=crowd-openid-server #application.login.url.template=http\://localhost\:8095/openidserver?returnToUrl\=${RETURN_TO_URL} application.login.url.template=https\://auth.mbari.org/openidserver?returnToUrl\=${RETURN_TO_URL} session.isauthenticated=session.isauthenticated #application.base.url=http\://localhost\:8095/openidserver application.base.url=https\://auth.mbari.org/openidserver #application.login.url=http\://localhost\:8095/openidserver application.login.url=https\://auth.mbari.org/openidserver session.validationinterval=0 application.password=password {noformat} and that seems to have fixed it. # (/) It is finally time to move on to the version 4 upgrade ... holy crap. I first went to the *new* crowd install (auth.mbari.org) and logged in as the crowdadm. # (/) I clicked on Applications, then on Add Application # (/) I selected JIRA from the Application type drop-down # (/) I entered jira445 as the username. Ask Kevin about the password. # (/) I used http://bugs.shore.mbari.org:8081 as the URL # (/) I used 134.89.12.31 as the IP address. # (/) I selected only the MBARI LDAP directory. # (/) Then I selected "Allow all users to authenticate" # (/) Then I clicked on "Add Application" # (/) I VNC'd into bugs.mbari.org. As it turns out, for Linux, there is an installer program to download. I downloaded the .bin for 64 bit Linux installer and moved it to the jira-upgrade directory. # (/) I chmod'd the file to make it executable and ran it. It gave me a warning about not being root, but I went ahead with it. # (/) It asked for the JIRA home and data directory, which I specified as /opt/jira4 and /data/jira445. # (/) For the ports, I specified 8180 and 8105 (HTTP and control respectively). It then extracted all the files and launched JIRA. It said if finished, so I opened a local browser to http://localhost:8180 which kicked off the start up wizard. # (/) I specified the external database using: ## solstice2.shore.mbari.org (server) ## 1433 (port) ## jira4 (database) ## DB_Collaboration (username) ## (password ask Kevin) ## dbo (schema) # But all this failed as it seems to just want to try and use the SQL server authentication instead of domain. I will have to do it manually. # (/) I stopped the server using the bin/stop-jira.sh script. # (/) I created and edited /data/jira445/dbconfig.xml and made it look like the following: {noformat} ?xml version="1.0" encoding="UTF-8"?> defaultDS default mssql jiraschema jdbc:jtds:sqlserver://solstice2.shore.mbari.org:1433/Jira4;domain=SHORE;useNTLMv2=true net.sourceforge.jtds.jdbc.Driver DB_Collaboration (ask Kevin) 15 {noformat} # (/) I then started it again using bin/start-jira.sh and tailed the catalina.out file. Got a bunch of errors related to the schema 'jiraschema', I edited the file and changed the schema to 'dbo' and restarted. That seemed to do it. There was one stack trace for some iCal plugin, but looks OK other than that. # I browsed back to localhost:8180 and the wizard moved to step 2. There was an option to import existing data bit without the crowd connection, I thought I should set it up manually, connect to crowd, then import. I generated an evaluation license, called the app "MBARI JIRA4" and change the server in the url to bugs.shore.mbari.org # For the admin, I created an account called 'jiraadm' (ask Kevin for password). # Since this is a temporary system, I left the email system disabled. # I logged in as jiraadm, went to Administration, then Users, then clicked on Add Directory and chose Atlassian Crowd. Note that I had to set the server URL to http://auth.mbari.org:8095/crowd or I would have had to configure all this SSL crap that I did not want to do for this temporary install. # It tested successfully, I clicked Save and it went through a 13 second sync, whew! # I then went to System->Import and Export->Restore System # I copied the jira-upgrade-3.13.5.zip file from the previous version export into /data/jira445/import and then entered that file name along with the new evaluation license again. # I worked through progress bar after I clicked on Restore (it took a really long time). # I then stopped, restarted and tailed the log file. # I am thinking now I should have put the attachments in the import attachments directory, but I am hoping I can just copy them to the data/attachments directory. # UG! I got some error during the import. The exception read: "JIRA is unable to migrat the User Directory configuration because external users exist but the osuser.xml file is not available". It then gave me a link to a doc that talked about making the old user files available before the upgrade ... crap. So I needed to copy the osuser.xml and crowd.properties file from atlassian-jira/WEB-INF/classes directory on the old install to the same directory on the new install ... sigh. This means I am going to blow away everything and start over. # I shutdown jira4 # I dropped all things in the database and deleted all content in the /data/jira445 directory (except for the dbconfig.xml file). # I also removed the temp, logs (actually you have to leave the directory, just clear the files) and the work/Catalina/localhost directories from the jira installation. # I then copied the osuser.xml and the crowd.properties files from the 3.13.5 install to the 4 install. # I edited the crowd.properties file in hopes that I could point it to the new crowd install on auth.mbari.org and it would work, but we will see. # I then started jira and tailed the log file. # All looked OK (other than iCal plugin stack trace again), so I went to localhost:8180 and got step 2 of the wizard. I used the same info as before. # I logged in as the local admin account and it looks like the system picked up the crowd connection, but lets see what server it used! Hey it used the one I edited into the file! Sweet ... now let's see if the import works. # I copied the 3.13.5 zip file to the import directory again and this time, I untarred the attachments into the import/attachments directory. # I kicked off the restore as before and it worked through it fine. # Shutdown and restarted system, tailing the log file and then went to localhost:8180 # I can see issues (before logging in) and it all looks good!! The attachments did not move over from the import directory, so I copied the tar file from /data/jira445/import to /data/jira445/data and then untarred it there, then removed the tar file and the import zip file from the import directory. # Now I will try to login using my MBARI account and OMG it actually worked!!! (it even gave my kgomes account Admin privs) # I then performed an export and copied those file to the /data/backups/4.4.5 directory (also created a TAR of the attachments and put there too). # Now on to version 5! # OK, so something strange is happening. After the imports, the server ID goes back to the one that is on our current production server, which must mean it is using our current license key (which does not match the server ID, BTW). Oh well, I will press on! # I created a /data/jira5211 directory as well as a /opt/jira5 directory. Knowing what I know now and reading through the install instructions, it appears that I need to create a dbconfig.xml file manually, so I did that using: {noformat} defaultDS default mssql dbo jdbc:jtds:sqlserver://solstice2.shore.mbari.org:1433/Jira5;domain=SHORE;useNTLMv2=true net.sourceforge.jtds.jdbc.Driver DB_Collaboration (ask Kevin) 20 20 30000 20 true 300 select 1 60000 300000 true false {noformat} # I then changed the mode to executable on the installer download and ran that. # I had to choose a "custom install" this time through, but the properties were similar after that (ports I used were 8280 and 8205) # I then browsed to localhost:8280 # I dropped me to a wizard where I define the title as "MBARI JIRA5", and changed host to bugs.shore.mbari.org (from localhost) # This license was a little different in that is just asked for my Atlassian username and password and fetched a new license for me. # For the admin account, I used the same 'jiraadm' account # Left email notification disabled. # I created a new application in crowd for JIRA 5 and used same account info as for 4. # In JIRA, I went to Administration->Users->User Directories and then added a directory as I had done before. # All went well and the sync happened. # I then went to Administration->System->Import and Export->Restore System # I copied the backup of 4.4.5 to the /data/jira5211/import directory and then specified that file name. I did not specify a license as it seems to use the old one and it said so in the text below the box. # Clicked on restore and while it was restoring, I untarred the attachments to the /data/jira5211/data directory # After the restore, I shutdown and restarted JIRA tailing the log file. # Browsed to localhost:8280 and ... success! I see issues before logging in and ... my MBARI login worked, I was admin and all is good!!!! # As with previous version, I ran a backup of the DB and attachments and placed in /data/backups/5.2.11 # I poked around a little and there seems to be an issue in the comments that they are still referencing oceana??? I will have to look into this. # I then re-did the process once again for version 6.4.9. I will only put notes about things that are dramatically different below: ## It looks like the dbconfig.xml file is the same as it is for version 5, so I just copied and edited to point to Jira6 DB. ## I used ports 8380 and 8305 {warning:title=Collation} The DB needs to be using a specific collation that it's not, I will have to correct that on the production run {warning} ## It gave me a choice on "how I wanted to use JIRA" and I chose the default (top) one which was just JIRA. ## Something did not go well on the restore (got to 90%) from backup up and the server seems to have crashed, but it looks like it tried to restart? ## I forced a stop and start and tailed the log file. Could it be related to the collation issue? Upon restart it re-ran the indexing. Looks like it worked OK, let me login with my MBARI account. ## Interesting, the comments pointing to oceana seems to have fixed itself in the step of the upgrade. ## Another interesting note, when I went to the Admin->System->General configuration, it had the base URL as oceana, that would explain it. So I edited that to bugs.shore.mbari.org (it also made me change the Mode to private, which makes sense since authentication is external). ## I went back to the 3, 4, and 5 install and changed the base URL there too. That fixed that issue. # I then sent an email to all hands giving the URLs for folks to look at. # While folks were looking over the upgrade instances, I went ahead and created the cloud instance at Atlassian so I could test upload the JIRA backup from 6.4.9 {warning:title=Disable Remote Crowd Directory} As a part of the test import, I discovered that you have to disable the remote crowd directory through User Management->User Directories *before* you do the backup/export. {warning} # You basically do a backup of the system, tar up the attachments and then push those files to the cloud instance through WebDAV. Then you choose those files to do a 'JIRA Import'. The attachments did not work and I had to leave those de-selected and then submitted a ticket for that to be done. # It did seem to import all the users from our LDAP system, so I had to go through and 'Deactivate' all the users that I did not think would login. The billing adjusts fine to that, so that seems tractable. I am still working on seeing how users login to their imported accounts and if you can link BitBucket accounts to JIRA. h3. The Production (Final) Migration The day is finally here, the production JIRA migration. Here are the steps I took: # Logged into oceana as root # Edited the /opt/jira/conf/server.xml and commented out the Connector section that had the port of 8010 to shut it off from the normal serving route # I uncommented the 8082 port connector and the 8443 port connector so that I could still get to the server. # I stopped and started the JIRA server and in the log file I got a "keystore was tampered with..." which is not surprising. # I could then browser over to http://oceana.mbari.org:8082/jira # Then through the Administration console, I did an XML backup (file named final-jira-migration-backup-2015-08-21) and selected the zip option ## I had to create a /tmp/jira-backup directory and give DB_Collaboration:coladm ownership for the backup to happen ... sigh # I created the directory /root/jira-upgrade/final-2015-08-21 and moved the backup from /tmp/jira-backup to that location # I then shut down JIRA (hopefully for the LAST time!!!) # I logged out of oceana # I logged into bugs.shore.mbari.org as me # Due to a patch and reboot, all the JIRA servers were down, which was fine. # I cd'd to /opt/atlassian-jira-enterprise-3.13.5-standalone # I wanted to clean things up so I cd'd to logs and removed all the log files # I then wanted to remove the deployed web application so I could start clean so I changed to ../work and deleted the entire Catalina directory # Using Aqua Data Studio, I deleted all the tables in the Jira_Temp database on solstice2 # Back on bugs, I scp'd the backup zip file and the attachments file to the /data/backups/3.12/final-upgrade-2015-08-21 directory # I cd'd to the /data/jira3135 directory and deleted the attachments and indexes directories and then created empty directories for those again. # Since the first import will look for attachments in /data/jira_3_12, I cd'd to that directory and deleted the attachments directory there. # I then copied the attachments tar I scp'd over and untarred it in that location. # I then started up JIRA (version 3.13.5) using /opt/atlassian-jira-enterprise-3.13.5-standalone/bin/startup.sh # I tailed the log file and it looked like a clean startup. # I browsed over to http://bugs.shore.mbari.org:8080 and got the start up page. # I clicked on the "Import existing data" link and specified the /data/backups/3.12/final-upgrade-2015-08-21/final-jira-migration-backup-2015-08-21.zip as the backup file and /data/jira3135/indexes as the index location # I tailed the log file during the import process and everything looked great ... YEEEEEEEEEEESSSSSSSSSSSSSS!!!!!! # OK, so far so good. Attachments were there and everything. # I then went to the administration panel and performed another backup to XML using the file nanme final-jira-migration-3135-backup-2015-08-21 and selected the zip option. # It created the zip file in the JIRA tomcat bin directory! So I moved it to /data/backups/3.13.15/final-upgrade-2015-08-21 # I created a tar of the attachments (which was in the /data/jira_3_12 directory) and moved it to /data/backups/3.13.15/final-upgrade-2015-08-21 also # I then shutdown the 3.13.5 JIRA instance for the LAST (hopefully) time!! # I fired up Aqua Data Studio again and deleted all the stuff in the Jira4 database on solstice 2 # I then cd'd to /opt/jira4/logs and cleaned out any log files # I cd'd to /opt/jira4/work and removed the .pid file and the Catalina directory # I cd'd to the /opt/jira4 directory and removed the temp directory too. # I then cd'd to the /data/jira445 directory and removed everything but the dbconfig.xml file # I then started JIRA 4 and tailed the log file # It created all the tables in the DB as well as all the directories fine. # I copied the /data/backups/3.13.5/final-upgrade-2015-08-21/final-jira-migration-3135-backup-2015-08-21.zip to the /data/jira445/import directory # I copied the /data/backups/3.13.5/final-upgrade-2015-08-21/final-jira-migration-3135-attachments.tar to the /data/jira445/data directory # I untarred it there and it put all the attachments in the attachments directory. # I then removed the tar file. # I then went to the http://bugs.shore.mbari.org:8180 url in my browser # I clicked on the "Import your existing data" link # I entered /data/jira445/import/final-jira-migration-3135-backup-2015-08-21.zip in the File name box and then clicked import. # It bounced back because of eval license was needed, so I clicked on the generate eval license and agreed to the terms, Yes to install license and then clicked import. # I tailed the log file and everything worked!!!! Attachments too!!!! # I logged in and went to the admin panel. # I went to the Import and Export and clicked on Backup System tab on the left. # I entered the file name final-migration-445-2015-08-21 and clicked Backup # This created the backup located here: /data/jira445/export/final-migration-445-2015-08-21.zip # I then shutdown the JIRA4 for the (hopefully) LAST TIME!!!! # I created the /data/backups/4.4.5/final-upgrade-2015-08-21 directory # I then moved the /data/jira445/export/final-migration-445-2015-08-21.zip to the /data/backups/4.4.5/final-upgrade-2015-08-21 directory # I cd'd to the /data/jira445/data directory and tarred up the attachements directory to the final-migration-445-attachments-2015-08-21.tar file # I then moved that file to the /data/backups/4.4.5/final-upgrade-2015-08-21 directory # I cd'd to the /opt/jira5/logs directory and removed all the log files # I cd'd to the /opt/jira5/work directory and removed the Catalina directory and the pid file # I cd'd to the /data/jira5211 directory and I removed all the directories except for the dbconfig.xml file # I used Aqua data studio to delete all the tables in the Jira5 database (this took a couple of rounds of delete due to key constraints) # I then started JIRA 5 using /opt/jira5/bin/start-jira.sh and the DB tables and /data/jira5211 directories were all created OK # I copied the /data/backups/4.4.5/final-upgrade-2015-08-21/final-migration-445-attachments-2015-08-21.tar to the /data/jira5211/data directory # I then untarred the file there which put all the attachments in the attachments folder. # I then copied the /data/backups/4.5.5/final-upgrade-2015-08-21/final-migration-445-2015-08-21.zip to the /data/jira5211/import directory # I tailed the /opt/jira5/log/catalina.out file and opened http://bugs.shore.mbari.org:8280 in my browser # I clicked on the "import data" link # I put /data/jira5211/import/final-migration-445-2015-08-21.zip in the file name field and then clicked on Generate an evaluation key # I filled out everything and it put the license key in and then I clicked on "import" # Everything seemed to go smoothly, so I logged in and then created a backup by going to Administration->System->Import and Export. # I input the file name final-upgrade-5211-2015-08-21 which created the /data/jira5211/export/final-upgrade-5211-2015-08-21.zip file # I shutdown JIRA 5 for (hopefully!) the LAST TIME !!! # I tarred up that /data/jira5211/data/attachments directory and moved it to /data/backups/5.2.11/final-upgrade-5211-2015-08-21/final-upgrade-5211-attachments-2015-08-21.tar # I moved the backup that was in the /data/jira5211/export directory to the /data/backups/5.2.11/final-upgrade-5211-2015-08-21 directory # Using Aqua data studio, I deleted everything in the Jira6 database (took a couple rounds due to keys) # I cd'd to /opt/jira6/logs and removed all the log files # I cd'd to /opt/jira6/work and deleted everything there # I cd'd to /data/jira649 and removed everything but the dbconfig.xml file # I then cd'd to /opt/jira6/bin and started jira using jira-start.sh # I tailed to log file to make sure it all started up OK. # After successful start up, I copied the /data/backups/5.2.11/final-upgrade-5211-2015-08-21/final-upgrade-5211-2015-08-21.zip file to the /data/jira649/import directory # I copied the /data/backups/5.2.11/final-upgrade-5211-2015-08-21/final-upgrade-5211-attachments-2015-08-21.tar to the /data/jira649/data directory and untarred it which put all the attachments in the attachments directory. # I then went to http://bugs.shore.mbari.org:8380 to kick off the set up # I tailed the log file in the terminal to make sure all was OK # I clicked on "import your data" link # I put /data/jira649/import/final-upgrade-5211-2015-08-21.zip in the file name box and clicked on Generate evaluation license, followed the instructions and then clicked on Import # Everything seems to have worked (including attachments)!!! # I went to User Management->User Directories and I moved the JIRA internal directory up in the order of directories and disabled the Remote Crowd Directory # I then did an export using System->Backup System and used the file name final-upgrade-6211-2015-08-21 # I then shutdown the JIRA 6 for (hopefully!!!) the LAST TIME !!!! # I cd'd to the /data/jira629/data directory and created the final-upgrade-629-attachments-2015-08-21.tar file of the attachments directory # I cd'd to the /data/backup/6.4.9/ directory and created the final-upgrade-649-2015-08-21 directory. # I cd'd to that directory and moved the backup file and the attachment tar to that directory. # I then opened a terminal on my local machine and SCP'd those backup files locally. # I then mounted the WebDAV directory on my local machine using finder an connecting using https://mbari1.atlassian.net/webdav/ # I then copied the backup files I scp'd to may local machine to the remote WebDAV directory. # I logged in to our cloud system and went to Administration->System # I clicked on JIRA Import on the left hand side # I only selected the XML backup zip to import as Atlassian has to do the attachments. # I gave me the option of updating URLs that were in issues, I selected the ones point to oceana and continued. # It warned me that everything would be replaced. I left the email enabled and continued. # It looks like it did a purge first, then the import. # It failed and I updated my support ticket to have them look at it # They uploaded and re-indexed and it wiped out all accounts, so I logged in as admin/admin and it put me through a setup routine # I changed that admin password, but it looks like it is a limited 'admin'. I am wondering if the account needs to have site admin because I can't get into any of the user management stuff. ]]> 28016663 10387625 10354861 15237193 15204426 10387627 10354863 15237214 15204449 10387649 10354885 10387644 10354880 23658561 23625794 23658526 23625759 23658524 23625757 23658522 23625755 9899683 9798386 2009-05-10 15:42:33.313 2009-05-10 15:42:33.313 9899682 9798386 2009-05-10 15:42:33.313 2009-05-10 15:42:33.313 4948041 Open" and select the elf-file (e.g. "test.elf") you want to debug. Now click on "Run->Connect to target" and enter the following settings: Target: "Remote/TCP" Hostname: "localhost" Port: "2000" Set breakpoint at 'main': yes Set breakpoint at 'exit': yes Attach to target: yes Download Program: yes Command after attaching: "monitor erase all" Run Method: Continue from last Stop When you click on "Ok" Insight should tell you that the connection was successful, and gdbproxy should say "notice: msp430-gdbproxy: connected". To start the debugging click on "Run" or simply press "r". If everything worked correctly you should now see the sourcecode of your program with the first line of main() marked green. The red point is the breakpoint that has been set by Insight automatically. You can set or remove breakpoints by clicking on the '-' in front of the line. Now you can 'c'ontinue the execution to the next breakpoint, 's'tep through the code, or step a single assembler instruction... but be careful with "finish": Insight sometimes seems to lock up with this command. So if you want to finish a function, I recommend setting a breakpoint to the end of the function and using "continue". ]]> 4915278 7405576 7372808 7405577 7372809 7405625 7372857 622599 ... mbari MBARI Repository http://oceana.shore.mbari.org/maven2 ... ... {code} h3. Including a Dependency from the Repository Once the MBARI repository is included in you build, you can browse the repository to see what projects are available (just go to [http://oceana.shore.mbari.org/maven2]). If you find a dependency you need you can reference it in your _pom.xml_. Here's an example... {code:xml} ... ... qt4j qt4j 0.5 ... ... {code} h3. Putting a Dependency into the Repository The easiest way to put a dependency into the repository is to setup a Maven build file (i.e. _pom.xml_). In _pom.xml_ add the following _distributionManagement_ information: {code:xml} 4.0.0 qt4j qt4j jar 1.0-SNAPSHOT QT4J ... mbari-repository MBARI Repository scp://oceana.shore.mbari.org/var/www/html/maven2 {code} Executing _mvn deploy_ will put your build jar at http://oceana.shore.mbari.org/maven2////-.jar. In the example here it would put it into [http://oceana.shore.mbari.org/maven2/qt4j/qt4j/1.0-SNAPSHOT/] h3. Publishing Maven generated web sites Maven can generate a web site for a default web site for you. You can view samples of the currently published projects at [http://oceana.shore.mbari.org/projects]. It's not very interesting, however, it is a very simple way to publish the javadoc, sources and auto-generated reports. To do so modify your _pom.xml_: {code:xml} ... org.apache.maven.plugins maven-jxr-plugin org.apache.maven.plugins maven-pmd-plugin 1.5 org.apache.maven.plugins maven-checkstyle-plugin ... oceana.shore.mbari.org scp://oceana.shore.mbari.org/var/www/html/projects/${project.name} {code} Then run _mvn javadoc:javadoc site:site site:deploy_. This will build the javadocs, create a site with some useful reports, then publish the site (using scp) to oceana in the correct location. h3. Project Specific Maven Repositories Some projects may need to be configured differently for different deployment locations. For example, [VARS|VARS:Home] is configured differently for each ship and shore. These specific configurations are stored in Maven repositories in [http://oceana.shore.mbari.org/maven2-prj]. Each directory listed there is a different repository. Here's an example of how to include the projects configured for [Eye-in-the-sea|EITS:Home]. {code:xml} mbari-eits MBARI-EITS Repository http://oceana.shore.mbari.org/maven2-prj/eits {code} h2. {anchor:M3}+Using the MBARI repository from an [Ant|http://ant.apache.org] project using Maven+ Maven repositories can be used from Ant build scripts using [Maven's antlib|http://maven.apache.org/ant-tasks.html]. To do this you must have both Maven and Ant installed. h3. Bootstrapping antlib To bootstrap antlib into your projects (so users can build without having to install antlib) modify your _build.xml_ file like so: {code:xml} ... Finding dependencies of ${pom.artifactId}-${version} ... {code} h2. {anchor:M4}+Using the MBARI repository from an [Ant|http://ant.apache.org] project using Ivy+ Maven repositories can be used from Ant build scripts using [Ivy|http://incubator.apache.org/ivy/]. h3. Referencing the repository In the directory containing the ant build file, _build.xml_, create a file called _ivyconf.xml_. _ivyconf.xml_ tells Ivy where to look for dependencies. The contents of the file will look something like: {code:xml} {code} h3. Including a Dependency from the Repository In the directory containing _build.xml_, create a file called _ivy.xml_. _ivy.xml_ tells Ivy what dependencies to include in your build. Here's an example of it's contents: {code:xml} {code} h3. Using Ivy from Ant The code below will fetch Ivy for you. SO you do not need install any additional software in order to get you build to work. In your ant build file include the following: {code:xml} ... {code} Calling _ant ivy.install_ will fetch all the dependencies from the web and put them into the _lib_ directory of your project. ]]> 589831 622600 ... mbari MBARI Repository http://oceana.shore.mbari.org/maven2 ... ... {code} h3. Including a Dependency from the Repository Once the MBARI repository is included in you build, you can browse the repository to see what projects are available (just go to [http://oceana.shore.mbari.org/maven2]). If you find a dependency you need you can reference it in your _pom.xml_. Here's an example... {code:xml} ... ... qt4j qt4j 0.5 ... ... {code} h3. Putting a Dependency into the Repository The easiest way to put a dependency into the repository is to setup a Maven build file (i.e. _pom.xml_). In _pom.xml_ add the following _distributionManagement_ information: {code:xml} 4.0.0 qt4j qt4j jar 1.0-SNAPSHOT QT4J ... mbari-repository MBARI Repository scp://oceana.shore.mbari.org/var/www/html/maven2 {code} Executing _mvn deploy_ will put your build jar at http://oceana.shore.mbari.org/maven2////-.jar. In the example here it would put it into [http://oceana.shore.mbari.org/maven2/qt4j/qt4j/1.0-SNAPSHOT/] h3. Publishing Maven generated web sites Maven can generate a web site for a default web site for you. You can view samples of the currently published projects at [http://oceana.shore.mbari.org/projects]. It's not very interesting, however, it is a very simple way to publish the javadoc, sources and auto-generated reports. To do so modify your _pom.xml_: {code:xml} ... org.apache.maven.plugins maven-jxr-plugin org.apache.maven.plugins maven-pmd-plugin 1.5 org.apache.maven.plugins maven-checkstyle-plugin ... oceana.shore.mbari.org scp://oceana.shore.mbari.org/var/www/html/projects/${project.name} {code} Then run _mvn javadoc:javadoc site:site site:deploy_. This will build the javadocs, create a site with some useful reports, then publish the site (using scp) to oceana in the correct location. h3. Project Specific Maven Repositories Some projects may need to be configured differently for different deployment locations. For example, [VARS|VARS:Home] is configured differently for each ship and shore. These specific configurations are stored in Maven repositories in [http://oceana.shore.mbari.org/maven2-prj]. Each directory listed there is a different repository. Here's an example of how to include the projects configured for [Eye-in-the-sea|EITS:Home]. {code:xml} mbari-eits MBARI-EITS Repository http://oceana.shore.mbari.org/maven2-prj/eits {code} h2. {anchor:M3}+Using the MBARI repository from an [Ant|http://ant.apache.org] project using Maven+ Maven repositories can be used from Ant build scripts using [Maven's antlib|http://maven.apache.org/ant-tasks.html]. To do this you must have both Maven and Ant installed. h3. Bootstrapping antlib To bootstrap antlib into your projects (so users can build without having to install antlib) modify your _build.xml_ file like so: {code:xml} ... Finding dependencies of ${pom.artifactId}-${version} ... {code} h2. {anchor:M4}+Using the MBARI repository from an [Ant|http://ant.apache.org] project using Ivy+ Maven repositories can be used from Ant build scripts using [Ivy|http://incubator.apache.org/ivy/]. h3. Referencing the repository In the directory containing the ant build file, _build.xml_, create a file called _ivyconf.xml_. _ivyconf.xml_ tells Ivy where to look for dependencies. The contents of the file will look something like: {code:xml} {code} h3. Including a Dependency from the Repository In the directory containing _build.xml_, create a file called _ivy.xml_. _ivy.xml_ tells Ivy what dependencies to include in your build. Here's an example of it's contents: {code:xml} {code} h3. Using Ivy from Ant The code below will fetch Ivy for you. SO you do not need install any additional software in order to get you build to work. In your ant build file include the following: {code:xml} ... {code} Calling _ant ivy.install_ will fetch all the dependencies from the web and put them into the _lib_ directory of your project. ]]> 589832 7405630 7372862 622601 ... mbari MBARI Repository http://oceana.shore.mbari.org/maven2 ... ... {code} h3. Including a Dependency from the Repository Once the MBARI repository is included in you build, you can browse the repository to see what projects are available (just go to [http://oceana.shore.mbari.org/maven2]). If you find a dependency you need you can reference it in your _pom.xml_. Here's an example... {code:xml} ... ... qt4j qt4j 0.5 ... ... {code} h3. Putting a Dependency into the Repository The easiest way to put a dependency into the repository is to setup a Maven build file (i.e. _pom.xml_). In _pom.xml_ add the following _distributionManagement_ information: {code:xml} 4.0.0 qt4j qt4j jar 1.0-SNAPSHOT QT4J ... mbari-repository MBARI Repository scp://oceana.shore.mbari.org/var/www/html/maven2 {code} Executing _mvn deploy_ will put your build jar at http://oceana.shore.mbari.org/maven2////-.jar. In the example here it would put it into [http://oceana.shore.mbari.org/maven2/qt4j/qt4j/1.0-SNAPSHOT/] h3. Publishing Maven generated web sites Maven can generate a web site for a default web site for you. You can view samples of the currently published projects at [http://oceana.shore.mbari.org/projects]. It's not very interesting, however, it is a very simple way to publish the javadoc, sources and auto-generated reports. To do so modify your _pom.xml_: {code:xml} ... org.apache.maven.plugins maven-jxr-plugin org.apache.maven.plugins maven-pmd-plugin 1.5 org.apache.maven.plugins maven-checkstyle-plugin ... oceana.shore.mbari.org scp://oceana.shore.mbari.org/var/www/html/projects/${project.name} {code} Then run _mvn javadoc:javadoc site:site site:deploy_. This will build the javadocs, create a site with some useful reports, then publish the site (using scp) to oceana in the correct location. h3. Project Specific Maven Repositories Some projects may need to be configured differently for different deployment locations. For example, [VARS|VARS:Home] is configured differently for each ship and shore. These specific configurations are stored in Maven repositories in [http://oceana.shore.mbari.org/maven2-prj]. Each directory listed there is a different repository. Here's an example of how to include the projects configured for [Eye-in-the-sea|EITS:Home]. {code:xml} mbari-eits MBARI-EITS Repository http://oceana.shore.mbari.org/maven2-prj/eits {code} h2. {anchor:M3} +Using the MBARI repository from an [Ant|http://ant.apache.org] project using Maven+ Maven repositories can be used from Ant build scripts using [Maven's antlib|http://maven.apache.org/ant-tasks.html]. To do this you must have both Maven and Ant installed. h3. Bootstrapping antlib To bootstrap antlib into your projects (so users can build without having to install antlib) modify your _build.xml_ file like so: {code:xml} ... Finding dependencies of ${pom.artifactId}-${version} ... {code} h2. {anchor:M4} +Using the MBARI repository from an [Ant|http://ant.apache.org] project using Ivy+ Maven repositories can be used from Ant build scripts using [Ivy|http://incubator.apache.org/ivy/]. h3. Referencing the repository In the directory containing the ant build file, _build.xml_, create a file called _ivyconf.xml_. _ivyconf.xml_ tells Ivy where to look for dependencies. The contents of the file will look something like: {code:xml} {code} h3. Including a Dependency from the Repository In the directory containing _build.xml_, create a file called _ivy.xml_. _ivy.xml_ tells Ivy what dependencies to include in your build. Here's an example of it's contents: {code:xml} {code} h3. Using Ivy from Ant The code below will fetch Ivy for you. SO you do not need install any additional software in order to get you build to work. In your ant build file include the following: {code:xml} ... {code} Calling _ant ivy.install_ will fetch all the dependencies from the web and put them into the _lib_ directory of your project. ]]> 589833 622602 ... mbari MBARI Repository http://oceana.shore.mbari.org/maven2 ... ... {code} h3. Including a Dependency from the Repository Once the MBARI repository is included in you build, you can browse the repository to see what projects are available (just go to [http://oceana.shore.mbari.org/maven2]). If you find a dependency you need you can reference it in your _pom.xml_. Here's an example... {code:xml} ... ... qt4j qt4j 0.5 ... ... {code} h3. Putting a Dependency into the Repository The easiest way to put a dependency into the repository is to setup a Maven build file (i.e. _pom.xml_). In _pom.xml_ add the following _distributionManagement_ information: {code:xml} 4.0.0 qt4j qt4j jar 1.0-SNAPSHOT QT4J ... mbari-repository MBARI Repository scp://oceana.shore.mbari.org/var/www/html/maven2 {code} Executing _mvn deploy_ will put your build jar at http://oceana.shore.mbari.org/maven2////-.jar. In the example here it would put it into [http://oceana.shore.mbari.org/maven2/qt4j/qt4j/1.0-SNAPSHOT/] h3. Publishing Maven generated web sites Maven can generate a web site for a default web site for you. You can view samples of the currently published projects at [http://oceana.shore.mbari.org/projects]. It's not very interesting, however, it is a very simple way to publish the javadoc, sources and auto-generated reports. To do so modify your _pom.xml_: {code:xml} ... org.apache.maven.plugins maven-jxr-plugin org.apache.maven.plugins maven-pmd-plugin 1.5 org.apache.maven.plugins maven-checkstyle-plugin ... oceana.shore.mbari.org scp://oceana.shore.mbari.org/var/www/html/projects/${project.name} {code} Then run _mvn javadoc:javadoc site:site site:deploy_. This will build the javadocs, create a site with some useful reports, then publish the site (using scp) to oceana in the correct location. h3. Project Specific Maven Repositories Some projects may need to be configured differently for different deployment locations. For example, [VARS|VARS:Home] is configured differently for each ship and shore. These specific configurations are stored in Maven repositories in [http://oceana.shore.mbari.org/maven2-prj]. Each directory listed there is a different repository. Here's an example of how to include the projects configured for [Eye-in-the-sea|EITS:Home]. {code:xml} mbari-eits MBARI-EITS Repository http://oceana.shore.mbari.org/maven2-prj/eits {code} h2. {anchor:M3} +Using the MBARI repository from an [Ant|http://ant.apache.org] project using Maven+ Maven repositories can be used from Ant build scripts using [Maven's antlib|http://maven.apache.org/ant-tasks.html]. To do this you must have both Maven and Ant installed. h3. Bootstrapping antlib To bootstrap antlib into your projects (so users can build without having to install antlib) modify your _build.xml_ file like so: {code:xml} ... Finding dependencies of ${pom.artifactId}-${version} ... {code} h2. {anchor:M4} +Using the MBARI repository from an [Ant|http://ant.apache.org] project using Ivy+ Maven repositories can be used from Ant build scripts using [Ivy|http://incubator.apache.org/ivy/]. h3. Referencing the repository In the directory containing the ant build file, _build.xml_, create a file called _ivyconf.xml_. _ivyconf.xml_ tells Ivy where to look for dependencies. The contents of the file will look something like: {code:xml} {code} h3. Including a Dependency from the Repository In the directory containing _build.xml_, create a file called _ivy.xml_. _ivy.xml_ tells Ivy what dependencies to include in your build. Here's an example of it's contents: {code:xml} {code} h3. Using Ivy from Ant The code below will fetch Ivy for you. SO you do not need install any additional software in order to get you build to work. In your ant build file include the following: {code:xml} ... {code} Calling _ant ivy.install_ will fetch all the dependencies from the web and put them into the _lib_ directory of your project. ]]> 589834 7405633 7372865 622596 ... mbari MBARI Repository http://oceana.shore.mbari.org/maven2 ... ... {code} h3. Including a Dependency from the Repository Once the MBARI repository is included in you build, you can browse the repository to see what projects are available (just go to [http://oceana.shore.mbari.org/maven2]). If you find a dependency you need you can reference it in your _pom.xml_. Here's an example... {code:xml} ... ... qt4j qt4j 0.5 ... ... {code} h3. Putting a Dependency into the Repository The easiest way to put a dependency into the repository is to setup a Maven build file (i.e. _pom.xml_). In _pom.xml_ add the following _distributionManagement_ information: {code:xml} 4.0.0 qt4j qt4j jar 1.0-SNAPSHOT QT4J ... mbari-repository MBARI Repository scp://oceana.shore.mbari.org/var/www/html/maven2 {code} Executing _mvn deploy_ will put your build jar at http://oceana.shore.mbari.org/maven2////-.jar. In the example here it would put it into [http://oceana.shore.mbari.org/maven2/qt4j/qt4j/1.0-SNAPSHOT/] h3. Publishing Maven generated web sites Maven can generate a web site for a default web site for you. You can view samples of the currently published projects at [http://oceana.shore.mbari.org/projects]. It's not very interesting, however, it is a very simple way to publish the javadoc, sources and auto-generated reports. To do so modify your _pom.xml_: {code:xml} ... org.apache.maven.plugins maven-jxr-plugin org.apache.maven.plugins maven-pmd-plugin 1.5 org.apache.maven.plugins maven-checkstyle-plugin ... oceana.shore.mbari.org scp://oceana.shore.mbari.org/var/www/html/projects/${project.name} {code} Then run _mvn javadoc:javadoc site:site site:deploy_. This will build the javadocs, create a site with some useful reports, then publish the site (using scp) to oceana in the correct location. h3. Project Specific Maven Repositories Some projects may need to be configured differently for different deployment locations. For example, [VARS|VARS:Home] is configured differently for each ship and shore. These specific configurations are stored in Maven repositories in [http://oceana.shore.mbari.org/maven2-prj]. Each directory listed there is a different repository. Here's an example of how to include the projects configured for [Eye-in-the-sea|EITS:Home]. {code:xml} mbari-eits MBARI-EITS Repository http://oceana.shore.mbari.org/maven2-prj/eits {code} h2. Using the MBARI repository from an [Ant|http://ant.apache.org] project using Maven Maven repositories can be used from Ant build scripts using [Maven's antlib|http://maven.apache.org/ant-tasks.html]. To do this you must have both Maven and Ant installed. h3. Bootstrapping antlib To bootstrap antlib into your projects (so users can build without having to install antlib) modify your _build.xml_ file like so: {code:xml} ... Finding dependencies of ${pom.artifactId}-${version} ... {code} h2. Using the MBARI repository from an [Ant|http://ant.apache.org] project using Ivy Maven repositories can be used from Ant build scripts using [Ivy|http://incubator.apache.org/ivy/]. h3. Referencing the repository In the directory containing the ant build file, _build.xml_, create a file called _ivyconf.xml_. _ivyconf.xml_ tells Ivy where to look for dependencies. The contents of the file will look something like: {code:xml} {code} h3. Including a Dependency from the Repository In the directory containing _build.xml_, create a file called _ivy.xml_. _ivy.xml_ tells Ivy what dependencies to include in your build. Here's an example of it's contents: {code:xml} {code} h3. Using Ivy from Ant The code below will fetch Ivy for you. SO you do not need install any additional software in order to get you build to work. In your ant build file include the following: {code:xml} ... {code} Calling _ant ivy.install_ will fetch all the dependencies from the web and put them into the _lib_ directory of your project. ]]> 589828 622597 ... mbari MBARI Repository http://oceana.shore.mbari.org/maven2 ... ... {code} h3. Including a Dependency from the Repository Once the MBARI repository is included in you build, you can browse the repository to see what projects are available (just go to [http://oceana.shore.mbari.org/maven2]). If you find a dependency you need you can reference it in your _pom.xml_. Here's an example... {code:xml} ... ... qt4j qt4j 0.5 ... ... {code} h3. Putting a Dependency into the Repository The easiest way to put a dependency into the repository is to setup a Maven build file (i.e. _pom.xml_). In _pom.xml_ add the following _distributionManagement_ information: {code:xml} 4.0.0 qt4j qt4j jar 1.0-SNAPSHOT QT4J ... mbari-repository MBARI Repository scp://oceana.shore.mbari.org/var/www/html/maven2 {code} Executing _mvn deploy_ will put your build jar at http://oceana.shore.mbari.org/maven2////-.jar. In the example here it would put it into [http://oceana.shore.mbari.org/maven2/qt4j/qt4j/1.0-SNAPSHOT/] h3. Publishing Maven generated web sites Maven can generate a web site for a default web site for you. You can view samples of the currently published projects at [http://oceana.shore.mbari.org/projects]. It's not very interesting, however, it is a very simple way to publish the javadoc, sources and auto-generated reports. To do so modify your _pom.xml_: {code:xml} ... org.apache.maven.plugins maven-jxr-plugin org.apache.maven.plugins maven-pmd-plugin 1.5 org.apache.maven.plugins maven-checkstyle-plugin ... oceana.shore.mbari.org scp://oceana.shore.mbari.org/var/www/html/projects/${project.name} {code} Then run _mvn javadoc:javadoc site:site site:deploy_. This will build the javadocs, create a site with some useful reports, then publish the site (using scp) to oceana in the correct location. h3. Project Specific Maven Repositories Some projects may need to be configured differently for different deployment locations. For example, [VARS|VARS:Home] is configured differently for each ship and shore. These specific configurations are stored in Maven repositories in [http://oceana.shore.mbari.org/maven2-prj]. Each directory listed there is a different repository. Here's an example of how to include the projects configured for [Eye-in-the-sea|EITS:Home]. {code:xml} mbari-eits MBARI-EITS Repository http://oceana.shore.mbari.org/maven2-prj/eits {code} h2. +Using the MBARI repository from an [Ant|http://ant.apache.org] project using Maven+ Maven repositories can be used from Ant build scripts using [Maven's antlib|http://maven.apache.org/ant-tasks.html]. To do this you must have both Maven and Ant installed. h3. Bootstrapping antlib To bootstrap antlib into your projects (so users can build without having to install antlib) modify your _build.xml_ file like so: {code:xml} ... Finding dependencies of ${pom.artifactId}-${version} ... {code} h2. +Using the MBARI repository from an [Ant|http://ant.apache.org] project using Ivy+ Maven repositories can be used from Ant build scripts using [Ivy|http://incubator.apache.org/ivy/]. h3. Referencing the repository In the directory containing the ant build file, _build.xml_, create a file called _ivyconf.xml_. _ivyconf.xml_ tells Ivy where to look for dependencies. The contents of the file will look something like: {code:xml} {code} h3. Including a Dependency from the Repository In the directory containing _build.xml_, create a file called _ivy.xml_. _ivy.xml_ tells Ivy what dependencies to include in your build. Here's an example of it's contents: {code:xml} {code} h3. Using Ivy from Ant The code below will fetch Ivy for you. SO you do not need install any additional software in order to get you build to work. In your ant build file include the following: {code:xml} ... {code} Calling _ant ivy.install_ will fetch all the dependencies from the web and put them into the _lib_ directory of your project. ]]> 589829 622598 ... mbari MBARI Repository http://oceana.shore.mbari.org/maven2 ... ... {code} h3. Including a Dependency from the Repository Once the MBARI repository is included in you build, you can browse the repository to see what projects are available (just go to [http://oceana.shore.mbari.org/maven2]). If you find a dependency you need you can reference it in your _pom.xml_. Here's an example... {code:xml} ... ... qt4j qt4j 0.5 ... ... {code} h3. Putting a Dependency into the Repository The easiest way to put a dependency into the repository is to setup a Maven build file (i.e. _pom.xml_). In _pom.xml_ add the following _distributionManagement_ information: {code:xml} 4.0.0 qt4j qt4j jar 1.0-SNAPSHOT QT4J ... mbari-repository MBARI Repository scp://oceana.shore.mbari.org/var/www/html/maven2 {code} Executing _mvn deploy_ will put your build jar at http://oceana.shore.mbari.org/maven2////-.jar. In the example here it would put it into [http://oceana.shore.mbari.org/maven2/qt4j/qt4j/1.0-SNAPSHOT/] h3. Publishing Maven generated web sites Maven can generate a web site for a default web site for you. You can view samples of the currently published projects at [http://oceana.shore.mbari.org/projects]. It's not very interesting, however, it is a very simple way to publish the javadoc, sources and auto-generated reports. To do so modify your _pom.xml_: {code:xml} ... org.apache.maven.plugins maven-jxr-plugin org.apache.maven.plugins maven-pmd-plugin 1.5 org.apache.maven.plugins maven-checkstyle-plugin ... oceana.shore.mbari.org scp://oceana.shore.mbari.org/var/www/html/projects/${project.name} {code} Then run _mvn javadoc:javadoc site:site site:deploy_. This will build the javadocs, create a site with some useful reports, then publish the site (using scp) to oceana in the correct location. h3. Project Specific Maven Repositories Some projects may need to be configured differently for different deployment locations. For example, [VARS|VARS:Home] is configured differently for each ship and shore. These specific configurations are stored in Maven repositories in [http://oceana.shore.mbari.org/maven2-prj]. Each directory listed there is a different repository. Here's an example of how to include the projects configured for [Eye-in-the-sea|EITS:Home]. {code:xml} mbari-eits MBARI-EITS Repository http://oceana.shore.mbari.org/maven2-prj/eits {code} h2. +Using the MBARI repository from an [Ant|http://ant.apache.org] project using Maven+ Maven repositories can be used from Ant build scripts using [Maven's antlib|http://maven.apache.org/ant-tasks.html]. To do this you must have both Maven and Ant installed. h3. Bootstrapping antlib To bootstrap antlib into your projects (so users can build without having to install antlib) modify your _build.xml_ file like so: {code:xml} ... Finding dependencies of ${pom.artifactId}-${version} ... {code} h2. +Using the MBARI repository from an [Ant|http://ant.apache.org] project using Ivy+ Maven repositories can be used from Ant build scripts using [Ivy|http://incubator.apache.org/ivy/]. h3. Referencing the repository In the directory containing the ant build file, _build.xml_, create a file called _ivyconf.xml_. _ivyconf.xml_ tells Ivy where to look for dependencies. The contents of the file will look something like: {code:xml} {code} h3. Including a Dependency from the Repository In the directory containing _build.xml_, create a file called _ivy.xml_. _ivy.xml_ tells Ivy what dependencies to include in your build. Here's an example of it's contents: {code:xml} {code} h3. Using Ivy from Ant The code below will fetch Ivy for you. SO you do not need install any additional software in order to get you build to work. In your ant build file include the following: {code:xml} ... {code} Calling _ant ivy.install_ will fetch all the dependencies from the web and put them into the _lib_ directory of your project. ]]> 589830 7405638 7372870 3407873 2008-01-11 13:10:58.250 2013-06-13 15:09:52.153 10388980 10356262 2 2006-10-17 21:48:40.373 2026-02-03 16:16:06.819 18252222 6 false 0.0 0 0 9798110 5 false 0.0 0 0 814 5 false 0.0 0 0 10356237 5 false 0.0 0 0 7766027 6 false 0.0 0 0 19039049 6 false 0.0 0 0 814 6 false 0.0 0 0 19041368 6 false 0.0 0 0 19039402 5 false 0.0 0 0 19041365 6 false 0.0 0 0 11240274 5 false 0.0 0 0 10911981 5 false 0.0 0 0 11240349 5 false 0.0 0 0 10354800 5 false 0.0 0 0 27066970 6 false 0.0 0 0 13926566 5 false 0.0 0 0 19040044 6 false 0.0 0 0 5832921 5 false 0.0 0 0 9798110 6 false 0.0 0 0 9372328 6 false 0.0 0 0 6259430 6 false 0.0 0 0 10356302 5 false 0.0 0 0 19040089 6 false 0.0 0 0 19041520 5 false 0.0 0 0 15630363 6 false 0.0 0 0 10354882 5 false 0.0 0 0 25919541 5 false 0.0 0 0 10354884 5 false 0.0 0 0 15631441 6 false 0.0 0 0 24051827 5 false 0.0 0 0 19040970 5 false 0.0 0 0 25919541 6 false 0.0 0 0 2162995 5 false 0.0 0 0 15631445 6 false 0.0 0 0 18252222 5 false 0.0 0 0 19039359 5 false 0.0 0 0 2162995 6 false 0.0 0 0 11240296 6 false 0.0 0 0 11240296 5 false 0.0 0 0 7766027 5 false 0.0 0 0 11240274 6 false 0.0 0 0 10355550 6 false 0.0 0 0 19040159 6 false 0.0 0 0 27066777 5 false 0.0 0 0 19040157 6 false 0.0 0 0 11797066 5 false 0.0 0 0 19040155 6 false 0.0 0 0 16220240 5 false 0.0 0 0 19040153 6 false 0.0 0 0 13926566 6 false 0.0 0 0 23167205 5 false 0.0 0 0 12484688 6 false 0.0 0 0 19040161 6 false 0.0 0 0 3113965 6 false 0.0 0 0 23167213 5 false 0.0 0 0 18580035 5 false 0.0 0 0 10355550 5 false 0.0 0 0 11239606 5 false 0.0 0 0 8355849 6 false 0.0 0 0 10912227 6 false 0.0 0 0 19040151 6 false 0.0 0 0 9798447 6 false 0.0 0 0 11797064 5 false 0.0 0 0 11797064 6 false 0.0 0 0 19040991 5 false 0.0 0 0 15631044 5 false 0.0 0 0 15631042 5 false 0.0 0 0 11240349 6 false 0.0 0 0 28213255 5 false 0.0 0 0 8355883 5 false 0.0 0 0 3637859 6 false 0.0 0 0 5832918 5 false 0.0 0 0 8355883 6 false 0.0 0 0 3113965 5 false 0.0 0 0 19041520 6 false 0.0 0 0 8913120 6 false 0.0 0 0 16416786 5 false 0.0 0 0 19040044 5 false 0.0 0 0 15631445 5 false 0.0 0 0 15631441 5 false 0.0 0 0 18251845 5 false 0.0 0 0 16416807 5 false 0.0 0 0 15631044 6 false 0.0 0 0 15631042 6 false 0.0 0 0 15631339 5 false 0.0 0 0 3637286 6 false 0.0 0 0 16416809 5 false 0.0 0 0 8355849 5 false 0.0 0 0 15630488 6 false 0.0 0 0 15630488 5 false 0.0 0 0 8913090 6 false 0.0 0 0 11797066 6 false 0.0 0 0 19040991 6 false 0.0 0 0 5832828 5 false 0.0 0 0 12484688 5 false 0.0 0 0 3637286 5 false 0.0 0 0 9371671 5 false 0.0 0 0 9371671 6 false 0.0 0 0 19040970 6 false 0.0 0 0 9798378 5 false 0.0 0 0 10356476 5 false 0.0 0 0 10912227 5 false 0.0 0 0 16416865 5 false 0.0 0 0 3114599 5 false 0.0 0 0 23167205 6 false 0.0 0 0 3637859 5 false 0.0 0 0 27067271 6 false 0.0 0 0 19040089 5 false 0.0 0 0 19039049 5 false 0.0 0 0 19040151 5 false 0.0 0 0 23167213 6 false 0.0 0 0 16416942 6 false 0.0 0 0 19041365 5 false 0.0 0 0 19041368 5 false 0.0 0 0 21365729 5 false 0.0 0 0 18252474 6 false 0.0 0 0 9798398 5 false 0.0 0 0 10356302 6 false 0.0 0 0 10356471 5 false 0.0 0 0 9372328 5 false 0.0 0 0 15630363 5 false 0.0 0 0 9798447 5 false 0.0 0 0 9798378 6 false 0.0 0 0 18580092 5 false 0.0 0 0 16416942 5 false 0.0 0 0 16416971 6 false 0.0 0 0 5374734 5 false 0.0 0 0 15204448 5 false 0.0 0 0 9798398 6 false 0.0 0 0 19040161 5 false 0.0 0 0 19039359 6 false 0.0 0 0 19040159 5 false 0.0 0 0 19040157 5 false 0.0 0 0 19040155 5 false 0.0 0 0 19040153 5 false 0.0 0 0 17236193 6 false 0.0 0 0 8913120 5 false 0.0 0 0 3114599 6 false 0.0 0 0 7176201 6 false 0.0 0 0 16416971 5 false 0.0 0 0 10356237 6 false 0.0 0 0 18252474 5 false 0.0 0 0 15204478 5 false 0.0 0 0 27067271 5 false 0.0 0 0 5832828 6 false 0.0 0 0 10354800 6 false 0.0 0 0 8913090 5 false 0.0 0 0 19039402 6 false 0.0 0 0 15631339 6 false 0.0 0 0 10356476 6 false 0.0 0 0 16416786 6 false 0.0 0 0 24052291 5 false 0.0 0 0 18251845 6 false 0.0 0 0 16220240 6 false 0.0 0 0 10356471 6 false 0.0 0 0 28213255 6 false 0.0 0 0 6259010 6 false 0.0 0 0 16416807 6 false 0.0 0 0 21365729 6 false 0.0 0 0 15204448 6 false 0.0 0 0 24051827 6 false 0.0 0 0 16416809 6 false 0.0 0 0 9798677 5 false 0.0 0 0 11239606 6 false 0.0 0 0 3638030 5 false 0.0 0 0 18580092 6 false 0.0 0 0 10354884 6 false 0.0 0 0 10354882 6 false 0.0 0 0 5374734 6 false 0.0 0 0 10911981 6 false 0.0 0 0 15204478 6 false 0.0 0 0 6259010 5 false 0.0 0 0 7176201 5 false 0.0 0 0 5832918 6 false 0.0 0 0 17236193 5 false 0.0 0 0 9798677 6 false 0.0 0 0 3637534 6 false 0.0 0 0 27066777 6 false 0.0 0 0 9798684 6 false 0.0 0 0 24052291 6 false 0.0 0 0 3637556 6 false 0.0 NavigationDrivers Setup Development Env tm dvlTaskTest - read dvl file tm dvlTaskTest - post DM data tm dvlTaskTest - dvl tx serial data tm dvlTask.c - dvl rx serial data tm dvlTask.c - read DM angle tm dvlTask.c - process dvl data tm dvlTask.c - publish DVL pos to DM tm dvlReader - read DM dvl pos dvlReader - verify output correctness listen to Mike ]]> 0 0 27066970 5 false 0.0 0 0 9798684 5 false 0.0 0 0 5832921 6 false 0.0 0 0 16416865 6 false 0.0 0 0 18580035 6 false 0.0 0 0 3637556 5 false 0.0 0 0 3637556 6 false 0.0 0 0 3637534 5 false 0.0 0 0 6259430 5 false 0.0 0 0 3638030 6 false 0.0 0 0