diff --git a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/INSTRUCTIONS b/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/INSTRUCTIONS deleted file mode 100644 index 6186d02a58..0000000000 --- a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/INSTRUCTIONS +++ /dev/null @@ -1,148 +0,0 @@ -new | dir | /awips/adapt/ifps/help -new | svcbu | banner_exprtbksiteGrdMode.gif -del | svcbu | banner_exprtbksiteGrdMode.jpg -new | svcbu | banner_exprtbksiteGrdToCSMode.gif -del | svcbu | banner_exprtbksiteGrdToCSMode.jpg -new | svcbu | banner_exprtGrdMode.gif -del | svcbu | banner_exprtGrdMode.jpg -new | svcbu | banner_exprtMode.gif -del | svcbu | banner_exprtMode.jpg -new | svcbu | banner_ghgMode.gif -new | svcbu | banner_imprtGrdMode.gif -del | svcbu | banner_imprtGrdMode.jpg -new | svcbu | banner_imprtMode.gif -del | svcbu | banner_imprtMode.jpg -new | svcbu | banner_no_backup.gif -del | svcbu | banner_no_backup.jpg -new | svcbu | banner_svcbuMode.gif -del | svcbu | banner_svcbuMode.jpg -new | svcbu | banner_waitMode.gif -del | svcbu | banner_waitMode.jpg -new | svcbu | choose_domain.jpg -new | svcbu | choose_domain_multi1.jpg -new | svcbu | choose_domain_multi2.jpg -new | svcbu | clean_up.gif -new | svcbu | do_not_cancel.gif -new | svcbu | failed_site.jpg -new | svcbu | gfe_startup.gif -new | svcbu | multi_exprtbksiteGrdMode.gif -del | svcbu | multi_exprtbksiteGrdMode.jpg -new | svcbu | multi_exprtbksiteGrdToCSMode.gif -del | svcbu | multi_exprtbksiteGrdToCSMode.jpg -new | svcbu | multi_exprtGrdMode.gif -del | svcbu | multi_exprtGrdMode.jpg -new | svcbu | multi_exprtMode.gif -del | svcbu | multi_exprtMode.jpg -new | svcbu | multi_ghgMode.gif -new | svcbu | multi_imprtGrdMode.gif -del | svcbu | multi_imprtGrdMode.jpg -new | svcbu | multi_imprtMode.gif -del | svcbu | multi_imprtMode.jpg -new | svcbu | multi_no_backup.gif -del | svcbu | multi_no_backup.jpg -new | svcbu | multi_svcbuMode.gif -del | svcbu | multi_svcbuMode.jpg -new | svcbu | multi_waitMode.gif -del | svcbu | multi_waitMode.jpg -new | svcbu | option_both.jpg -new | svcbu | option_gfe.jpg -new | svcbu | option_import_gfe.jpg -new | svcbu | option_import.jpg -new | svcbu | option_import_no_gfe.jpg -new | svcbu | option_none.jpg -new | svcbu | svcbu_faq.html -new | svcbu | svcbu_help.html -new | svcbu | svcbu_instructions.html -new | svcbu | svcbu_multidom.html -new | svcbu | xmessage_faq_01.jpg -new | svcbu | xmessage_faq_02.jpg -new | svcbu | xmessage_faq_03.jpg -new | svcbu | xmessage_faq_04.jpg -new | svcbu | xmessage_faq_05.jpg -new | svcbu | xmessage_faq_06.jpg -new | svcbu | xmessage_faq_07.jpg -new | svcbu | xmessage_faq_08.jpg -new | svcbu | xmessage_faq_09.jpg -new | svcbu | xmessage_faq_10.jpg -new | svcbu | xmessage_faq_11.jpg -new | svcbu | xmessage_faq_12.jpg -new | svcbu | xmessage_faq_13.jpg -new | svcbu | xmessage_faq_14.jpg -new | svcbu | xmessage_faq_15.jpg -new | svcbu | xmessage_faq_16.jpg -new | svcbu | xmessage_faq_17.jpg -new | svcbu | xmessage_faq_18.jpg -new | svcbu | xmessage_faq_19.jpg -new | svcbu | xmessage_faq_20.jpg -new | svcbu | xmessage_faq_21.jpg -new | svcbu | xmessage_faq_22.jpg -new | svcbu | xmessage_faq_23.jpg -new | svcbu | xmessage_faq_24.jpg -new | svcbu | xmessage_faq_25.jpg -new | svcbu | xmessage_faq_26.jpg -new | svcbu | xmessage_faq_27.jpg -new | svcbu | xmessage_faq_28.jpg -new | svcbu | xmessage_faq_29.jpg -new | svcbu | xmessage_faq_30.jpg -new | svcbu | xmessage_faq_31.jpg -new | svcbu | xmessage_faq_32.jpg -new | svcbu | xmessage_faq_33.jpg -new | svcbu | xmessage_faq_34.jpg -new | svcbu | xmessage_faq_35.jpg -new | svcbu | xmessage_faq_36.jpg -new | svcbu | xmessage_faq_37.jpg -new | svcbu | xmessage_faq_38.jpg -new | svcbu | xmessage_faq_39.jpg -new | svcbu | xmessage_faq_40.jpg -new | svcbu | xmessage_faq_41.jpg -new | svcbu | xmessage_faq_42.jpg -new | svcbu | xmessage_faq_43.jpg -new | svcbu | xmessage_faq_44.jpg -new | svcbu | xmessage_faq_45.jpg -new | svcbu | xmessage_faq_46.jpg -new | svcbu | xmessage_faq_47.jpg -new | svcbu | xmessage_faq_48.jpg -new | svcbu | xmessage_faq_49.jpg -new | svcbu | xmessage_faq_50.jpg -new | svcbu | xmessage_faq_51.jpg -new | svcbu | xmessage_faq_52.jpg -new | svcbu | xmessage_faq_53.jpg -new | svcbu | xmessage_faq_54.jpg -new | svcbu | xmessage_faq_55.jpg -new | svcbu | xmessage_faq_56.jpg -new | svcbu | xmessage_faq_57.jpg -new | svcbu | xmessage_faq_58.jpg -new | svcbu | xmessage_faq_59.jpg -new | svcbu | xmessage_faq_60.jpg -new | svcbu | xmessage_faq_61.jpg -new | svcbu | xmessage_faq_62.jpg -new | svcbu | xmessage_faq_63.jpg -new | svcbu | xmessage_faq_64.jpg -new | svcbu | xmessage_faq_65.jpg -new | svcbu | xmessage_faq_66.jpg -new | svcbu | xmessage_faq_67.jpg -new | svcbu | xmessage_faq_68.jpg -new | svcbu | xmessage_faq_69.gif -new | svcbu | xmessage_faq_70.gif -new | svcbu | xmessage_faq_71.gif -new | svcbu | xmessage_faq_72.gif -new | svcbu | xmessage_faq_73.gif -new | svcbu | xmessage_faq_74.gif -new | svcbu | xmessage_faq_75.gif -new | svcbu | xmessage_faq_76.gif -new | svcbu | xmessage_faq_77.gif -new | svcbu | xmessage_faq_78.gif -new | svcbu | xmessage_faq_79.gif -new | svcbu | xmessage_faq_80.gif -new | svcbu | xmessage_faq_81.gif -new | svcbu | xmessage_faq_82.gif -new | svcbu | xmessage_inst_01.jpg -new | svcbu | xmessage_inst_02.jpg -new | svcbu | xmessage_inst_03.jpg -new | svcbu | xmessage_inst_04.jpg -new | svcbu | xmessage_multidom_01.jpg -new | svcbu | xmessage_multidom_02.jpg -new | svcbu | xmessage_multidom_03.jpg -new | svcbu | xmessage_multidom_04.jpg -new | svcbu | xmessage_multidom_05.jpg -new | svcbu | xmessage_multidom_06.jpg diff --git a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/banner_exprtGrdMode.gif b/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/banner_exprtGrdMode.gif deleted file mode 100644 index 7efc60bbf6..0000000000 Binary files a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/banner_exprtGrdMode.gif and /dev/null differ diff --git a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/banner_exprtMode.gif b/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/banner_exprtMode.gif deleted file mode 100644 index a7d1ba8cc4..0000000000 Binary files a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/banner_exprtMode.gif and /dev/null differ diff --git a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/banner_exprtbksiteGrdMode.gif b/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/banner_exprtbksiteGrdMode.gif deleted file mode 100644 index b3aa5d64cb..0000000000 Binary files a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/banner_exprtbksiteGrdMode.gif and /dev/null differ diff --git a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/banner_exprtbksiteGrdToCSMode.gif b/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/banner_exprtbksiteGrdToCSMode.gif deleted file mode 100644 index 0c34ae6294..0000000000 Binary files a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/banner_exprtbksiteGrdToCSMode.gif and /dev/null differ diff --git a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/banner_ghgMode.gif b/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/banner_ghgMode.gif deleted file mode 100644 index 3e6f18069c..0000000000 Binary files a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/banner_ghgMode.gif and /dev/null differ diff --git a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/banner_imprtGrdMode.gif b/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/banner_imprtGrdMode.gif deleted file mode 100644 index 6d56ea73ea..0000000000 Binary files a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/banner_imprtGrdMode.gif and /dev/null differ diff --git a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/banner_imprtMode.gif b/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/banner_imprtMode.gif deleted file mode 100644 index 74291a4b4a..0000000000 Binary files a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/banner_imprtMode.gif and /dev/null differ diff --git a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/banner_no_backup.gif b/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/banner_no_backup.gif deleted file mode 100644 index a6e6a79155..0000000000 Binary files a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/banner_no_backup.gif and /dev/null differ diff --git a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/banner_svcbuMode.gif b/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/banner_svcbuMode.gif deleted file mode 100644 index 16e83fdf0a..0000000000 Binary files a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/banner_svcbuMode.gif and /dev/null differ diff --git a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/banner_waitMode.gif b/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/banner_waitMode.gif deleted file mode 100644 index fc368f7bb6..0000000000 Binary files a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/banner_waitMode.gif and /dev/null differ diff --git a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/choose_domain.jpg b/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/choose_domain.jpg deleted file mode 100644 index 2356abec86..0000000000 Binary files a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/choose_domain.jpg and /dev/null differ diff --git a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/choose_domain_multi1.jpg b/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/choose_domain_multi1.jpg deleted file mode 100644 index bab7dfda77..0000000000 Binary files a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/choose_domain_multi1.jpg and /dev/null differ diff --git a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/choose_domain_multi2.jpg b/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/choose_domain_multi2.jpg deleted file mode 100644 index e63b4e3405..0000000000 Binary files a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/choose_domain_multi2.jpg and /dev/null differ diff --git a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/clean_up.gif b/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/clean_up.gif deleted file mode 100644 index c91f0ed215..0000000000 Binary files a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/clean_up.gif and /dev/null differ diff --git a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/do_not_cancel.gif b/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/do_not_cancel.gif deleted file mode 100644 index c91f0ed215..0000000000 Binary files a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/do_not_cancel.gif and /dev/null differ diff --git a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/failed_site.jpg b/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/failed_site.jpg deleted file mode 100644 index ec6a0992c3..0000000000 Binary files a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/failed_site.jpg and /dev/null differ diff --git a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/gfe_startup.gif b/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/gfe_startup.gif deleted file mode 100644 index 16866b7bff..0000000000 Binary files a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/gfe_startup.gif and /dev/null differ diff --git a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/images/banner_no_backup.png b/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/images/banner_no_backup.png new file mode 100644 index 0000000000..5c3b1fc8ec Binary files /dev/null and b/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/images/banner_no_backup.png differ diff --git a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/images/banner_svcbuMode.png b/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/images/banner_svcbuMode.png new file mode 100644 index 0000000000..9bc356bf84 Binary files /dev/null and b/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/images/banner_svcbuMode.png differ diff --git a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/images/banner_svcbuMode_2.png b/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/images/banner_svcbuMode_2.png new file mode 100644 index 0000000000..9d38d206df Binary files /dev/null and b/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/images/banner_svcbuMode_2.png differ diff --git a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/images/svcbu_confirm_exit.png b/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/images/svcbu_confirm_exit.png new file mode 100644 index 0000000000..b17ce39fe5 Binary files /dev/null and b/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/images/svcbu_confirm_exit.png differ diff --git a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/images/svcbu_enter.png b/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/images/svcbu_enter.png new file mode 100644 index 0000000000..207fc250e3 Binary files /dev/null and b/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/images/svcbu_enter.png differ diff --git a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/images/svcbu_exit.png b/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/images/svcbu_exit.png new file mode 100644 index 0000000000..65a8297eb6 Binary files /dev/null and b/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/images/svcbu_exit.png differ diff --git a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/images/svcbu_exit_status.png b/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/images/svcbu_exit_status.png new file mode 100644 index 0000000000..cff8df971c Binary files /dev/null and b/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/images/svcbu_exit_status.png differ diff --git a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/images/svcbu_export_config.png b/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/images/svcbu_export_config.png new file mode 100644 index 0000000000..0b53ac9d7d Binary files /dev/null and b/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/images/svcbu_export_config.png differ diff --git a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/images/svcbu_export_config_status.png b/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/images/svcbu_export_config_status.png new file mode 100644 index 0000000000..18153d19f2 Binary files /dev/null and b/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/images/svcbu_export_config_status.png differ diff --git a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/images/svcbu_export_grids.png b/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/images/svcbu_export_grids.png new file mode 100644 index 0000000000..a862f0709f Binary files /dev/null and b/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/images/svcbu_export_grids.png differ diff --git a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/images/svcbu_export_grids_status.png b/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/images/svcbu_export_grids_status.png new file mode 100644 index 0000000000..d28dea9966 Binary files /dev/null and b/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/images/svcbu_export_grids_status.png differ diff --git a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/images/svcbu_export_local_grids_status.png b/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/images/svcbu_export_local_grids_status.png new file mode 100644 index 0000000000..d6298acd53 Binary files /dev/null and b/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/images/svcbu_export_local_grids_status.png differ diff --git a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/images/svcbu_icon_failed.png b/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/images/svcbu_icon_failed.png new file mode 100644 index 0000000000..3aa2f498f2 Binary files /dev/null and b/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/images/svcbu_icon_failed.png differ diff --git a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/images/svcbu_icon_in_progress_animated.gif b/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/images/svcbu_icon_in_progress_animated.gif new file mode 100644 index 0000000000..899eda5c72 Binary files /dev/null and b/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/images/svcbu_icon_in_progress_animated.gif differ diff --git a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/images/svcbu_icon_not_started.png b/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/images/svcbu_icon_not_started.png new file mode 100644 index 0000000000..f5650f92d0 Binary files /dev/null and b/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/images/svcbu_icon_not_started.png differ diff --git a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/images/svcbu_icon_success.png b/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/images/svcbu_icon_success.png new file mode 100644 index 0000000000..ffeb291f7b Binary files /dev/null and b/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/images/svcbu_icon_success.png differ diff --git a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/images/svcbu_import_grids.png b/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/images/svcbu_import_grids.png new file mode 100644 index 0000000000..563185e81e Binary files /dev/null and b/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/images/svcbu_import_grids.png differ diff --git a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/images/svcbu_import_grids_status.png b/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/images/svcbu_import_grids_status.png new file mode 100644 index 0000000000..91f9ba8170 Binary files /dev/null and b/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/images/svcbu_import_grids_status.png differ diff --git a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/images/svcbu_start_gfe.png b/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/images/svcbu_start_gfe.png new file mode 100644 index 0000000000..f4812c5e9b Binary files /dev/null and b/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/images/svcbu_start_gfe.png differ diff --git a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/images/svcbu_start_gfe_status.png b/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/images/svcbu_start_gfe_status.png new file mode 100644 index 0000000000..7ecd9eb427 Binary files /dev/null and b/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/images/svcbu_start_gfe_status.png differ diff --git a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/images/svcbu_startup_status.png b/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/images/svcbu_startup_status.png new file mode 100644 index 0000000000..d374d33818 Binary files /dev/null and b/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/images/svcbu_startup_status.png differ diff --git a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/images/svcbu_startup_status_large.png b/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/images/svcbu_startup_status_large.png new file mode 100644 index 0000000000..f76dbadf46 Binary files /dev/null and b/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/images/svcbu_startup_status_large.png differ diff --git a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/multi_exprtGrdMode.gif b/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/multi_exprtGrdMode.gif deleted file mode 100644 index 19d70ba87e..0000000000 Binary files a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/multi_exprtGrdMode.gif and /dev/null differ diff --git a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/multi_exprtMode.gif b/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/multi_exprtMode.gif deleted file mode 100644 index fc4d78e710..0000000000 Binary files a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/multi_exprtMode.gif and /dev/null differ diff --git a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/multi_exprtbksiteGrdMode.gif b/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/multi_exprtbksiteGrdMode.gif deleted file mode 100644 index ffad843aa8..0000000000 Binary files a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/multi_exprtbksiteGrdMode.gif and /dev/null differ diff --git a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/multi_exprtbksiteGrdToCSMode.gif b/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/multi_exprtbksiteGrdToCSMode.gif deleted file mode 100644 index e6c8ce0344..0000000000 Binary files a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/multi_exprtbksiteGrdToCSMode.gif and /dev/null differ diff --git a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/multi_ghgMode.gif b/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/multi_ghgMode.gif deleted file mode 100644 index d466fc3132..0000000000 Binary files a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/multi_ghgMode.gif and /dev/null differ diff --git a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/multi_imprtGrdMode.gif b/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/multi_imprtGrdMode.gif deleted file mode 100644 index 76b096292e..0000000000 Binary files a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/multi_imprtGrdMode.gif and /dev/null differ diff --git a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/multi_imprtMode.gif b/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/multi_imprtMode.gif deleted file mode 100644 index 0ee82c5594..0000000000 Binary files a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/multi_imprtMode.gif and /dev/null differ diff --git a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/multi_no_backup.gif b/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/multi_no_backup.gif deleted file mode 100644 index a0d7658c4b..0000000000 Binary files a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/multi_no_backup.gif and /dev/null differ diff --git a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/multi_svcbuMode.gif b/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/multi_svcbuMode.gif deleted file mode 100644 index d2127b9844..0000000000 Binary files a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/multi_svcbuMode.gif and /dev/null differ diff --git a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/multi_waitMode.gif b/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/multi_waitMode.gif deleted file mode 100644 index 2275c784e3..0000000000 Binary files a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/multi_waitMode.gif and /dev/null differ diff --git a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/option_both.jpg b/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/option_both.jpg deleted file mode 100644 index 374536885a..0000000000 Binary files a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/option_both.jpg and /dev/null differ diff --git a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/option_gfe.jpg b/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/option_gfe.jpg deleted file mode 100644 index 0f13b5a409..0000000000 Binary files a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/option_gfe.jpg and /dev/null differ diff --git a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/option_import.jpg b/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/option_import.jpg deleted file mode 100644 index 4638824ab7..0000000000 Binary files a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/option_import.jpg and /dev/null differ diff --git a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/option_import_gfe.jpg b/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/option_import_gfe.jpg deleted file mode 100644 index a4be85b0fb..0000000000 Binary files a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/option_import_gfe.jpg and /dev/null differ diff --git a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/option_import_no_gfe.jpg b/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/option_import_no_gfe.jpg deleted file mode 100644 index e3ee18cc59..0000000000 Binary files a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/option_import_no_gfe.jpg and /dev/null differ diff --git a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/option_none.jpg b/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/option_none.jpg deleted file mode 100644 index 89a43f054e..0000000000 Binary files a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/option_none.jpg and /dev/null differ diff --git a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/svcbu_cleanup.html b/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/svcbu_cleanup.html new file mode 100644 index 0000000000..796656276c --- /dev/null +++ b/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/svcbu_cleanup.html @@ -0,0 +1,86 @@ + + +
+ +
+
+
+
+
+
+
+
+
If you have contacted the failed site and confirmed receipt of their forecast grids,
+click Yes to exit service backup.
+If not, click No and contact the failed site.
+
+
- Service -Backup GUI- -FAQ- |
-
-1. WHAT IS THE DIFFERENCE BETWEEN -EXIT SERVICE BACKUP AND CLEAN UP SERVICE BACKUP?
--2. WHY IS THE "EXPORT CCC'S -CONFIGURATION TO THE CENTRAL SERVER" BUTTON GRAYED OUT?
--3. WHY IS THE "EXPORT CCC'S -DIGITAL FORECAST TO THE CENTRAL SERVER" BUTTON GRAYED OUT?
--4. WHEN SHOULD I USE THE REFRESH -BUTTON?
--5. DO I NEED TO EXPORT A FAILED -SITE'S GRIDS TO THE CENTRAL SERVER?
- - SCAN THROUGH ERRORS THAT OCCUR WHEN:
- IMPORTING CONFIGURATION
-
- IMPORTING DIGITAL DATA
-
- STARTING GFE
-
-
-EXPORTING DIGITAL DATA BACK TO A FAILED
-SITE
-
-
-EXPORTING A FAILED SITE'S DIGITAL DATA
-TO THE CENTRAL SERVER
-
-
-EXPORTING CONFIGURATION TO THE CENTRAL
-SERVER
-
-
-EXPORTING YOUR DIGITAL DATA TO THE
-CENTRAL SERVER
-
- EXITING SERVICE BACKUP
-
- CLEANING UP SERVICE BACKUP
-
1. -WHAT IS THE DIFFERENCE BETWEEN "EXIT SERVICE BACKUP" AND "CLEAN UP -SERVICE BACKUP"? -[BACK -TO THE TOP]
-The Exit Service Backup -button is only enabled while you are in Service Backup Mode. -Selecting this button will run the clean up script and will exit the -Service Backup GUI when it is finished. The Clean Up Service -Backup button is enabled even when you are not in Service Backup -Mode. Selecting this button while in Service Backup Mode will run -the clean up script, but will not exit the Service Backup GUI. -Selecting this button while you are not in Service Backup Mode will -bring up a GUI that allows you to enter the 3 letter ID of the site -that you wish to clean up.
--2. -WHY IS THE "EXPORT CCC'S CONFIGURATION TO THE CENTRAL SERVER" BUTTON -GRAYED OUT? -[BACK -TO THE TOP]
-This button is only enabled while you are -not in Service Backup Mode and the Service Backup GUI is started as -user ifps. If the GUI is started by any other user or you are in -Service Backup Mode, this button will be grayed out. To start the -GUI as user ifps:
-1. su
-ifps
-
-2. cd /awips/ifps/primary/bin
-
-3. ./service_backup.bat
-3. -WHY IS THE "EXPORT CCC'S DIGITAL FORECAST TO THE CENTRAL SERVER" BUTTON -GRAYED OUT? [BACK TO THE TOP]
-This button will become disabled when -your are in the process of exporting your grids to the central server -for service backup. At this time, the button will read "Currently -Exporting CCC's Digital Data" and you may not start up another export -until it is finished. If the export was started from the ifps -crontab, then the script will sleep for a random amount of time (up to -30 minutes) between running ifpnetCDF and sending the grids to the -central server. This is done to prevent all WFOs from exporting -their grids at the same time. If you send the grids from the -Service Backup GUI, they will be send immediately after ifpetCDF -runs.
-4. WHEN SHOULD I -USE THE REFRESH BUTTON? -[BACK -TO THE TOP]
-The REFRESH button will update the state -of the Service Backup GUI. It is a good idea to press the REFRESH -button before performing any other actions to ensure that the GUI -reflects your current service backup mode.
--5. -DO I NEED TO EXPORT A FAILED SITE'S GRIDS TO THE CENTRAL SERVER? -[BACK TO THE TOP]
-Starting in IFPS16.1, the Service Backup -GUI contains an option to export the failed site's digital data to the -central server. This is a cautionary step to help prevent the -loss of data when restoring grids to a failed site. If you are -unable to export a failed site's grids back to them, you can export -them to the central server. Then, the failed site can contact the -NCF, who has instructions on how to restore the digital data from the -central server.
-6. ERROR MESSAGES -[BACK -TO THE TOP]
-This section will explain some of the -different error messages that you may see while using the Service -Backup GUI.
-
-
When you start the Service Backup GUI -while in service backup mode, you will be prompted to select a -domain. You will see this message if you attempt to start the -Service Backup GUI as the failed site. The Service Backup GUI -must always be started as your site.
--
-IMPORTING CONFIGURATION [BACK -TO THE TOP]
--
-
Before you import a failed site's -configuration, a script will run to make sure that there are no service -backup databases on your system that will cause any problems. If -any IFPS databases are found, you will see this message. If you -wish to continue, you must select the CLEAN button to clean up that -site's database and configuration. If you do not wish to clean up -this site's database and configuration, select QUIT to return to the -Service Backup GUI. For more information, see -/data/logs/adapt/ifps/<date>/svcbu_check_<time> on dx4f.
--
-
Before you import a failed site's -configuration, a script will run to make sure that there are no service -backup files on your system that will cause any problems. If any -IFPS files are found, you will see this message. If you wish to -continue, you must select the CLEAN button to clean up that site's -configuration. If you do not wish to clean up this site's -configuration, select QUIT to return to the Service Backup GUI. -For more information, see -/data/logs/adapt/ifps/<date>/svcbu_check_<time> on dx4f.
--
-
Before you import a failed site's -configuration, a script will run to make sure that there are no service -backup files on your system that will cause any problems. If any -GFE files are found, you will see this message. If you wish to -continue, you must select the CLEAN button to clean up that site's -configuration. If you do not wish to clean up this site's -configuration, select QUIT to return to the Service Backup GUI. -For more information, see -/data/logs/adapt/ifps/<date>/svcbu_check_<time> on dx4f.
--
-
Before you import a failed site's -configuration, a script will run to make sure that there are no service -backup files on your system that will cause any problems. If any -GFE files are found and the Service Backup GUI is not able to determine -the failed site's ID, you will see this message. Press the -DETAILS button to view the log file to see what files were found. -You must delete these files before you are allowed to continue. -If you do not wish to clean up, select QUIT to return to the Service -Backup GUI. For more information, see -/data/logs/adapt/ifps/<date>/svcbu_check_<time> on dx4f.
--
-
You will see this error message if you -import you own site ID when asked what site's configuration you wish to -import. If your site has multiple domains, you will not be -allowed to import either domain's configuration.
--
-
You will see this error message when you -attempt to import a failed site's configuration while in service backup -mode. If you wish to import this site's configuration again or -another site's configuration, use the Clean Up Service Backup button to -clean up this site's configuration first.
--
-
You will see this error message if a -failed site's configuration fails to reach your site after 30 -minutes. Possible reasons for seeing this message are problems -with msg_send or the failed site's configuration is not present on the -central server. If you would like to continue to wait for the -failed site's configuration, for up to another 30 minutes, press -YES. If you do not wish to wait, select NO. Selecting NO -will clean up the necessary lock files and return you to the Service -Backup GUI.
--
-
You will see this error message when you -attempt to import a failed site's configuration while you are waiting -for a failed site's server to start. If you wish to import a -failed site's configuration, you must first wait until after the server -is started. Be sure to clean up before importing.
--
-
You will see this error message when you -attempt to import a failed site's configuration while you are importing -a failed site's digital data. If you wish to import a failed -site's configuration, you must first wait until after the import of the -digital data is finished. Be sure to clean up before importing.
--
-
You will see this error message when you -attempt to import a failed site's configuration while an import process -is already running. If you wish to import a failed site's -configuration, you must first wait until the first import is -finished. Be sure to clean up before importing.
--
-
You will see this error message when you -attempt to import a failed site's configuration while exporting your -configuration to the central server for service backup. If you -wish to import a failed site's configuration, you must first wait until -the export is finished.
--
-
You will see this error message when you -attempt to import a failed site's configuration while exporting your -grids to the central server for service backup. If you wish to -import a failed site's configuration, you must first wait until the -export is finished.
--
-
You will see this error message when you -attempt to import a failed site's configuration while exporting grids -back to a failed site. If you wish to import another failed -site's configuration, you must wait until the export is finished. -Be sure to clean up the first site's configuration before starting -another import.
--
-
You will see this error message when you -attempt to import a failed site's configuration while exporting a -failed site's grids to the central server. If you wish to import -another failed site's configuration, you must wait until the export is -finished. Be sure to clean up the first site's configuration -before starting another import.
--
-
You will see this error message if there -was a problem importing a failed site's configuration, digital data, -and/or starting their GFE. For more information, see -/data/logs/adapt/ifps/<date>/svcbu_doall_<time> on the -machine that you started the import from.
--
-IMPORTING DIGITAL DATA [BACK -TO THE TOP]
-
-
You will see this message if a failed -site's digital data has not reached your site after 30 minutes. -Possible reasons for seeing this message are problems with msg_send or -the failed site's digital data is not present on the central -server. If you wish to continue to wait for the failed site's -grids, for up to 30 minutes, press YES. If you do not wish to -wait, press NO. Selecting NO will clean up the necessary lock -files and will return you to the Service Backup GUI. You will -still be in service backup mode.
--
-
If you choose to import a site's -configuration and import their digital data and/or start their GFE, the -Service Backup GUI will make 10 attempts at 30 second intervals to -verify that the failed site's server has started on dx4f. If the -failed site's server fails to start or takes more than 6 minutes to -start, you will see this message. For more information, see -/data/logs/adapt/ifps/<date>/SVCBU_import_config_<time> and -/data/logs/adapt/ifps/<date>/svcbu_doall_<time> on the -machine that you started the import from.
--
-
You will see this message if there was a -problem importing a failed site's digital data. For more -information, see -/data/logs/adapt/ifps/<date>/svcbu_reqGrd_<time> on the -machine you ran the import from.
--
-
You will see this error message when you -attempt to import a failed site's digital data while you are not in -Service Backup Mode. Import the failed site's configuration -before importing their digital data.
--
-
You will see this error message when -trying to import a failed site's digital data while importing their -configuration. Wait until the configuration import is complete -before importing a failed site's digital data.
--
-
You will see this error message when -trying to import a failed site's digital data while an import is -already running. Wait until the first set of grids has finished -importing before importing again.
--
-
You will see this error message when -trying to import a failed site's digital data while the failed site's -server is trying to start. Please wait until the failed site's -server is running to import digital data.
--
-
You will see this error message when -trying to import a failed site's digital data while exporting your -configuration to the central server. You must wait until the -export is finished before you can begin to import digital data for a -failed site.
--
-
You will see this error message when -trying to import a failed site's digital data while exporting your -grids to the central server. You must wait until the export is -finished before you can begin to import digital data for a failed site.
--
-
You will see this error message when -trying to import a failed site's digital data while exporting grids -back to the failed site. If you wish to re-import the failed -site's digital data, you must wait until the export has finished.
--
-
You will see this error message when -trying to import a failed site's digital data while exporting a failed -site's grids to the central server. If you wish to re-import the -failed site's digital data, you must wait until the export is finished.
--
-
If the Service Backup GUI is not able to -find the failed site's environment file, it is a likely sign that there -was a problem importing the failed site's configuration. If this -is the case, you will not be able to import the failed site's digital -data. You should clean up the failed site's configuration and -import it again. For more information, see -/data/logs/adapt/ifps/<date>/svcbu_<time>.
--
-
STARTING -GFE -[BACK -TO THE TOP]
--
-
You will see this message if there was a -problem starting GFE for a failed site. For more information, see -/data/logs/adapt/ifps/<date>/svcbuGFE_<time> on the machine -that you tried to start GFE from.
--
-
When trying to start GFE for any domain, -the Service Backup GUI must first source that domain's environment -file. If the Service Backup GUI is not able to find a failed -site's environment file, it will not be able to start GFE for that -site. For more information, see -/data/logs/adapt/ifps/<date>/svcbu_doall_<time>.
--
-
-EXPORTING -DIGITAL DATA BACK TO A FAILED SITE [BACK -TO THE TOP]
--
-
If the Service Backup GUI is not able to -find the failed site's environment file, it is a likely sign that there -was a problem importing the failed site's configuration or you are not -in service backup mode. If this is the case, you will not be able -to export the grids to a failed site. Ensure that you are in -service backup mode and that the failed site's environment file is -present. For more information, see -/data/logs/adapt/ifps/<date>/svcbu_<time>.
--
-
You will see this message if there was an -error exporting the digital data back to a failed site. For more -information, see -/data/logs/adapt/ifps/<date>/svcbu_expbksiteGrd_<time> on -the machine that you ran the export from.
--
-
You will see this error message if you -attempt to export grids back to a failed site while you are not in -Service Backup Mode. You must be in Service Backup Mode to export -digital data back to a failed site.
--
-
You will see this error message when -attempting to export grids back to a failed site while you are -importing their configuration. Wait until the import is finished -before exporting the digital data back to the failed site.
--
-
You will see this error message when -attempting to export grids back to a failed site while their server is -trying to start. Wait until the server is started before -exporting the digital data back to the failed site.
--
-
You will see this error message when -attempting to export grids back to a failed site while you are -importing the site's digital data. Wait until the import is -finished before exporting the digital data back to the failed site.
-
-
You will see this error message when -attempting to export grids back to a failed site while you are -exporting your configuration to the central server for service -backup. You must wait until the export is finished before you can -begin exporting grids back to a failed site.
--
-
You will see this error message when -attempting to export grids back to a failed site while exporting your -grids to the central server. You must wait until the export is -finished before you can begin exporting grids back to a failed site.
--
-
You will see this message when you -attempt to export digital data back to a failed site while one export -of the data is already running. If you wish to re-export the -digital data back to the failed site, you must wait for the first -export to finish.
--
-
You will see this error message when you -attempt to export digital data back to a failed site while exporting -the failed site's grids to the central server. If you wish to -export the failed site's grids back to them, you must wait for the -first export to finish.
--
-EXPORTING -A FAILED SITE'S DIGITAL DATA TO THE CENTRAL SERVER -[BACK -TO THE TOP]
--
-
You will see this message if there was a -problem exporting a failed site's digital data to the central -server. For more information, see -/data/logs/adapt/ifps/<date>/svcbu_exprtbksiteGrdToCS_<time> -on the machine you ran the export from.
--
-
You will see this error message if you -try to export a failed site's digital data to the central server and -the failed site's environment file was not found by the Service Backup -GUI. Make sure that you are in service backup mode and that -/awips/adapt/ifps/localbin/<failed site>/ifps-<failed -site>.env is present.
--
-
You will see this error message if you -try to export a failed site's digital data to the central server while -you are not in service backup mode. If you wish to export a -failed site's grids to the central server, you must first import the -failed site's configuration.
--
-
You will see this error message if you -try to export a failed site's digital data to the central server -while importing their configuration. You must first let the -import finish before you can begin exporting to the central server.
--
-
You will see this error message if you -try to export a failed site's digital data to the central server while -importing their digital data. If you wish to export the failed -site's digital data to the central server, you must let the import -finish first.
--
-
You will see this error message if you -try to export a failed site's digital data to the central server while -waiting for their server to start. Verify that the failed site's -server is running before exporting their grids to the central server.
--
-
You will see this error message if you -try to export a failed site's digital data tot he central server while -exporting your configuration to the central server. You must wait -for the first export to finish before you can export a failed site's -digital data to the central server.
--
-
You will see this error message if you -try to export a failed site's digital data to the central server while -exporting your digital data to the central server. You must wait -for your export to finish before you can export the failed site's grids -to the central server.
--
-
You will see this error message if you -try to export a failed site's digital data to the central server while -exporting the grids back to the failed site. You must first -finish exporting the grids to the failed site before you can send them -to the central server.
--
-
You will see this error message if you -try to export a failed site's digital data to the central server while -one export process is already running. If you wish to re-export -the failed site's digital data, you must let the first export process -finish.
--
-EXPORTING -CONFIGURATION TO THE CENTRAL SERVER [BACK -TO THE TOP]
--
-
You will see this message if there was a -problem exporting your configuration to the central server. For -more information, see -/data/logs/adapt/ifps/<date>/svcbu_<time> on the machine -that you ran the export from.
--
-
You will see this error message if you -try to export your configuration to the central server while you are in -Service Backup Mode. You must exit Service Backup Mode before you -can export your configuration.
--
-
You will see this error message if you -try to export you configuration to the central server while the export -is already running. If you wish to re-export your configuration, you -must wait for the first export to finish.
--
-EXPORTING -YOUR DIGITAL DATA TO THE CENTRAL SERVER [BACK -TO THE TOP]
--
-
You will see this message if there was a -problem exporting your digital data to the central server. For -more information, see -/data/logs/adapt/ifps/<date>/svcbu_expGrd_<time> on the -machine that you ran the export from.
--
-
You will see this message if you try to -export your grids to the central server while an export is already -running. If you wish to re-export your grids to the central -server, you must wait for the first export to finish.
--
-
You will see this error message if you -try to export your digital data to the central server while exporting a -failed site's digital data to the central server. You must wait -for the first export to finish before you can export your grids.
--
-EXITING SERVICE BACKUP -[BACK -TO THE TOP]
--
-
You will see this error message if you -try to exit service backup while you are not in Service Backup -Mode. You must be in Service Backup Mode to use the Exit -button. If you wish to run the cleanup script, use the "CLEAN UP -SERVICE BACKUP" button.
--
-
You will see this error message if you -try to exit service backup while importing a failed site's -configuration. Wait until the import is complete before exiting -service backup.
--
-
You will see this error message if you -try to exit service backup while importing a failed site's digital -data. Wait until the import is complete before exiting service -backup.
--
-
You will see this error message if you -try to exit service backup while waiting for a failed site's server to -start. Wait until the server is started before exiting service -backup.
--
-
You will see this error message when -trying to exit service backup while exporting grids back to a failed -site. You must wait until the export is finished before you can -exit service backup.
--
-CLEANING UP SERVICE BACKUP -[BACK TO THE TOP]
--
-
You will see this message if you attempt -to clean up your own site's configuration files. If your site has -multiple domains, you will not be allowed to clean up either domain's -configuration.
--
-
You will see this message if there was a -problem running the cleanup script. For more information, see -/data/logs/adapt/ifps/<date>/svcbu_cleanup_<time> on dx4f.
--
-
You will see this message if you try to -run the cleanup script while the failed site's server is trying to -start. Wait until the server is started before you run the -cleanup script.
--
-
You will see this message if you try to -run the cleanup script while importing a failed site's -configuration. Wait until the import is complete before you run -the cleanup script.
--
-
You will see this message if you try to -run the clean up script while exporting grids back to a failed -site. You must wait until the export is finished before you can -clean up service backup.
--
-
You will see this error message if you -try to run the clean up script while exporting a failed site's grids to -the central server. You must let the export finish before you can clean -up service backup.
- - diff --git a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/svcbu_help.html b/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/svcbu_help.html deleted file mode 100644 index 168cf069ec..0000000000 --- a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/svcbu_help.html +++ /dev/null @@ -1,464 +0,0 @@ - - - - - - - - - - - -
- Service Backup GUI --HELP |
-
GHG SERVICE BACKUP - -[BACK TO THE TOP] -
- -This button will allow you to start -another site's GFE after downloading their configuration. Before you are allowed -to start the failed site's GFE, check_svcbu.bat will run to check for any -service backup files that may cause problems. If any files are found, you will -be prompted to clean up. If you do not clean up, you will not be allowed to -continue, since serious errors may occur (server not starting, text products not -working, etc.). If no service backup files are found, you will be asked for the -failed site's ID. Once the failed site's configuration is downloaded and the -server is started, the failed site's GFE will start. At this time, you will be -able to create the Hazards grids for the failed site. NOTE: You should not -create any other grids at this time. You must first import the failed site's -grids in order to perform a full service backup.
- -IMPORT CONFIGURATION - DATA - [BACK TO THE TOP] -
- -This button will allow you to - import another site's configuration data. Before you are allowed to import, - check_svcbu.bat will run to check for any service backup files that may -cause problems. If any are found, you will be prompted to clean up. If -you do not clean up, you will not be allowed to continue, for errors may -occur. If no files are found or once the files are cleaned up, you will -be asked if you would like to also import the failed site's digital data -and/or start their GFE after the import is finished. Make your choice and -select OK.
- -This button will be disabled -while you are in the process of importing a site's configuration or digital -data. It will be enabled at all other times.
- -IMPORT FAILED - SITE'S DIGITAL DATA - [BACK TO THE TOP] -
- -This button will also be called - "IMPORT CCC's DIGITAL DATA" when you are in service backup mode. It will - allow you to import the digital data of the site specified in the title -(CCC in this example). You will also be asked if you would like to start -GFE for the failed site once the import is finished. Make your choice and -select OK.
- -This button will only be enabled - after you have successfully imported the failed site's configuration. -It will be disabled while you are importing a failed site's configuration -or digital data or are not in service backup mode.
- -EXPORT GRIDS TO -FAILED SITE - [BACK TO THE TOP] -
- -This button will also be called - "EXPORT GRIDS TO CCC" when you are in service backup mode. It will allow - you to export the digital data back to the failed site (CCC in this example).
- -This button will only be enabled - after you have successfully imported the failed site's configuration. -It will be disabled while you are importing a failed site's configuration -or digital data or you are not in service backup mode.
- -- EXPORT CCC'S CONFIGURATION TO THE CENTRAL SERVER - [BACK TO THE TOP] -
- -This button will allow you to - export your own configuration (CCC's in this example) to the central server - for service backup.
- -This button will only be enabled - when you start the GUI as user ifps and are not in service backup mode. -If you start the Service Backup GUI as any other user, the button label will -read "Must Be User IFPS to Export CCC's Configuration".
- -- EXPORT CCC'S DIGITAL FORECAST TO THE CENTRAL SERVER - [BACK TO THE TOP] -
- -This button will allow you to - export your digital data (CCC's in this example) to the central server -for service backup.
- -This button will be enabled whenever - you are not currently exporting your digital forecast to the central server.
- -- EXPORT A FAILED SITE'S DIGITAL DATA TO THE CENTRAL SERVER - [BACK TO THE TOP] -
- -This button will allow you to - export a failed site's digital data to the central server. (NOTE: - You still need to export the digital data back to the failed site.)
- -This button will be enabled after - you have successfully imported the failed site's configuration. It will - be disabled while you are exporting configuration or digital data or while - you are not in service backup mode.
- -START GFE - [BACK TO THE TOP] -
- -This button will allow you to - start GFE for a specified time. If you are in service backup mode or have - multiple domains at your site, you will be asked what domain you would -like to start service backup for. Otherwise, GFE will start for your site -only.
- -This button will be enabled at - all times.
- -EXIT SERVICE BACKUP - [BACK TO THE TOP] -
- -This button will also be called - "EXIT SERVICE BACKUP FOR CCC" while you are in service backup mode. It -will allow you to clean up the failed site's configuration (CCC in this -example) and will close the Service Backup GUI when finished.
- -This button will only be enabled - while you are in service backup mode.
- -CLEAN UP SERVICE BACKUP - [BACK TO THE TOP] -
- -This button will allow you to - clean up a failed site's configuration. If you are in service backup mode, - it will clean up the configuration of the failed site. If you are not -currently in backup mode, then you will be prompted for the site ID that -you wish to clean up.
- -This button will be disabled -while you are importing a failed site's digital data.
- -OK - [BACK TO THE TOP] -
- -This button perform the selected - action. It will stay depressed until the selected action is finished.
- - - -This button will refresh the banner message - (if necessary) and will enable/disable the necessary buttons. It will -also unselect any button.
- - - -YOU ARE NOT IN BACKUP - MODE - [BACK TO THE TOP] -
- -
-
This banner will appear if you - are not in service backup mode. At this time, only the following buttons - will be enabled:
- -EMERGENCY GFE -(GHG ONLY)
- -IMPORT CONFIGURATION - DATA
- -EXPORT CCC'S CONFIGURATION - TO THE CENTRAL SERVER (if the GUI is started as user ifps)
- -EXPORT CCC'S DIGITAL - FORECAST TO THE CENTRAL SERVER
- -START GFE
- -CLEAN UP SERVICE - BACKUP
- -- YOU ARE CURRENTLY IMPORTING A FAILED SITE'S CONFIGURATION - [BACK TO THE TOP] -
- -
-
This banner will appear while - you are in the process of importing a failed site's configuration from -the central server from another Service Backup GUI. At this time, only -the following buttons will be enabled:
- -EXPORT CCC'S DIGITAL - FORECAST TO THE CENTRAL SERVER
- -START GFE
- -CLEAN UP SERVICE - BACKUP
- -WAITING - FOR A FAILED SITE'S SERVER TO START - [BACK TO THE TOP] -
- -
-
This banner may also read "WAITING - FOR XXX'S SERVER TO START" It will appear while you are waiting for a -failed site's server (xxx's in this example) to start. At this time, only -the following buttons will be enabled:
- -EXPORT CCC'S DIGITAL - FORECAST TO THE CENTRAL SERVER
- -START GFE
- -- YOU ARE CURRENTLY IMPORTING A FAILED SITE'S DIGITAL DATA - [BACK TO THE TOP] -
- -
-
This banner may also read "YOU - ARE CURRENTLY IMPORTING XXX'S DIGITAL DATA." It will appear while you -are importing a failed site's digital data (xxx's in this example). At -this time, only the following buttons will be enabled:
- -EXPORT CCC'S DIGITAL - FORECAST TO THE CENTRAL SERVER
- -START GFE
- -YOU ARE CURRENTLY - BACKING UP XXX - [BACK TO THE TOP] -
- -
-
This message will appear while - you are in service backup mode for a failed site (XXX in this example). - At this time, the following buttons will be enabled:
- -IMPORT CONFIGURATION - DATA
- -IMPORT XXX'S DIGITAL - DATA
- -EXPORT GRIDS TO - XXX
- -EXPORT CCC'S DIGITAL - FORECAST TO THE CENTRAL SERVER
- -START GFE
- -EXIT SERVICE BACKUP -FOR XXX
- -CLEAN UP SERVICE - BACKUP
- -EXPORTING GRIDS -BACK TO XXX - [BACK TO THE TOP] -
- -
-
EXPORT CCC'S - DIGITAL FORECAST TO THE CENTRAL SERVER
- -START GFE
- -- YOU ARE CURRENTLY EXPORTING YOUR CONFIGURATION TO THE CENTRAL SERVER - [BACK TO THE TOP] -
- -
-
EXPORT CCC'S - DIGITAL FORECAST TO THE CENTRAL SERVER
- -START GFE
- -CLEAN UP SERVICE -BACKUP
- -- YOU ARE CURRENTLY EXPORTING YOUR GRIDS TO THE CENTRAL SERVER - [BACK TO THE TOP] -
- -
-
IMPORT CONFIGURATION - DATA
- -START GFE
- -CLEAN UP SERVICE -BACKUP
- -If you are in service backup -mode, the following buttons will be enabled:
- -IMPORT CONFIGURATION - DATA
- -IMPORT CCC'S - DIGITAL DATA
- -EXPORT GRIDS - TO CCC
- -EXPORT CCC'S - DIGITAL DATA TO THE CENTRAL SERVER
- -START GFE
- -EXIT SERVICE - BACKUP FOR CCC
- -CLEAN UP - SERVICE BACKUP
- -- YOU ARE CURRENTLY EXPORTING XXX'S GRIDS TO THE CENTRAL SERVER - [BACK TO THE TOP] -
- -
-
This message will appear while you are exporting a failed - site's grids to the central server. At this time, the following buttons - will be enabled:
- -EXPORT CCC'S DIGITAL -FORECAST TO THE CENTRAL SERVER
- -START GFE
- - - diff --git a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/svcbu_instructions.html b/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/svcbu_instructions.html index b597ee2fbd..c1341cc028 100644 --- a/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/svcbu_instructions.html +++ b/cave/com.raytheon.viz.gfe/help/GfeServiceBackup/svcbu_instructions.html @@ -1,433 +1,11 @@ - -
- Service Backup GUI --INSTRUCTIONS |
-
- -HOW TO START GHG SERVICE BACKUP
- - -HOW TO IMPORT A FAILED SITE'S CONFIGURATION AND DIGITAL DATA AND START -THEIR GFE IN -ONE STEP -- - -HOW TO IMPORT A FAILED SITE'S CONFIGURATION AND DIGITAL DATA IN ONE STEP -
-- - -HOW TO IMPORT A FAILED SITE'S CONFIGURATION AND START THEIR GFE IN -ONE STEP
-- - -HOW TO IMPORT A FAILED SITE'S CONFIGURATION
-- - -HOW TO IMPORT A FAILED SITE'S DIGITAL DATA AND START THEIR GFE IN ONE STEP -
-- - -HOW TO IMPORT A FAILED SITE'S DIGITAL DATA
-- - -HOW TO EXPORT GRIDS BACK TO A FAILED SITE
-- -HOW TO EXPORT A FAILED SITE'S DIGITAL DATA -TO THE CENTRAL SERVER
-- - -HOW TO EXPORT YOUR CONFIGURATION TO THE CENTRAL SERVER
-- - -HOW TO EXPORT YOUR DIGITAL DATA TO THE CENTRAL SERVER
-- - -HOW TO START GFE FROM THE SERVICE BACKUP GUI
- --HOW TO CLEAN UP SERVICE BACKUP
--
HOW TO START GHG -SERVICE BACKUP [BACK -TO THE TOP]
-1, Verify that the banner at the top of the Service Backup -GUI reads "YOU ARE NOT IN BACKUP MODE." If you are already in backup mode -for another site, you will need to run the - -clean up script first.
-
-
2. Select GHG Service Backup and press OK.
-3. The script will first check to see if there are any -service backup files present that may cause a problem. If any are found, -you will be prompted to clean up. If you wish to clean up and continue, -select CLEAN. Otherwise, select QUIT to return to the Service Backup GUI.
-
-
If no files are found, the script will run silently and you will -not be notified.
-4. Another GUI will appear, asking for the ID of the -failed site. Enter the failed site's 3 letter ID and press OK.
-
-
5. After a few minutes, a progress bar will appear with -the status of the failed site's configuration. When it is finished, you -may close the progress bar.
-6. Once the configuration import is complete and the -failed site's server is started, the Service Backup GUI will make up to ten -attempts to connect to the server. If it is not able to connect after ten -attempts, you will be notified and will not be allowed to continue.
-
-
-7. Once the GUI is able to connect to the server, the GFE Startup GUI will -appear. Select a User, Config file, and Mode and press Start. At -this point, you will be able to generate the failed site's warnings. Once -you have done this, you can import the failed site's digital data -and perform a full service backup.
--
--HOW TO IMPORT A FAILED SITE'S CONFIGURATION AND DIGITAL DATA AND START -THEIR GFE IN -ONE STEP -[BACK TO THE TOP]
-1. Verify that the banner at the top of the Service Backup -GUI reads "YOU ARE NOT IN BACKUP MODE." If you are backing up -another site, you will -need to clean up first.
-
-
2. Select Import Configuration Data and press OK.
-3. The script will first check to see if there are any -service backup files present that may cause a problem. If any are found, -you will be prompted to clean up. If you wish to clean up and continue, -select CLEAN. Otherwise, select QUIT to return to the Service Backup GUI.
-
-
If no files are found, the script will run silently and you will -not be notified.
-4. Another GUI will appear asking you "Would you also like -to Import Digital Forecast and/or Start GFE." Verify that both buttons are -selected and press OK.
-
-
5. Another GUI will appear, asking for the ID of the -failed site. Enter the failed site's 3 letter ID and press OK.
-
-
6. After a few minutes, a progress bar will appear with -the status of the failed site's configuration. When it is finished, you -may close the progress bar.
-7. Once the configuration import is complete and the -failed site's server is started, the Service Backup GUI will make up to ten -attempts to connect to the server. If it is not able to connect after ten -attempts, you will be notified and will not be allowed to continue.
-
-
8. If the GUI is able to connect to the failed site's -server, you will see another progress bar appear with the status of the -import of the failed site's digital data. When it is finished, you may -close the progress bar.
-9. If the import of the digital data is successful, the -GFE Startup GUI will appear. Select a User, Config file, and Mode and press Start.
- -- -
-HOW TO IMPORT A FAILED SITE'S CONFIGURATION AND DIGITAL DATA IN -ONE STEP -[BACK TO THE TOP]
-1. Verify that the banner at the top of the Service Backup -GUI reads "YOU ARE NOT IN BACKUP MODE." If you are already in -backup mode, you will -need to clean up first.
-
-
2. Select Import Configuration Data and press OK.
-3. The script will first check to see if there are any -service backup files present that may cause a problem. If any are found, -you will be prompted to clean up. If you wish to clean up and continue, -select CLEAN. Otherwise, select QUIT to return to the Service Backup GUI.
-
-
If no files are found, the script will run silently and you will -not be notified.
-4. Another GUI will appear asking you "Would you also like -to Import Digital Forecast and/or Start GFE." Verify that only the "Import -Digital Data" button is -selected and press OK.
-
-
5. Another GUI will appear, asking for the ID of the -failed site. Enter the failed site's 3 letter ID and press OK.
-
-
6. After a few minutes, a progress bar will appear with -the status of the failed site's configuration. When it is finished, you -may close the progress bar.
-7. Once the configuration import is complete and the -failed site's server is started, the Service Backup GUI will make up to ten -attempts to connect to the server. If it is not able to connect after ten -attempts, you will be notified and will not be allowed to continue.
-
-
8. If the GUI is able to connect to the failed site's -server, you will see another progress bar appear with the status of the -import of the failed site's digital data. When it is finished, you may -close the progress bar.
-- -
-HOW TO IMPORT A FAILED SITE'S CONFIGURATION AND START THEIR GFE IN -ONE STEP -[BACK TO THE TOP]
-1. Verify that the banner at the top of the Service Backup -GUI reads "YOU ARE NOT IN BACKUP MODE." If you are already in -backup mode, you will -need to clean up first.
-
-
2. Select Import Configuration Data and press OK.
-3. The script will first check to see if there are any -service backup files present that may cause a problem. If any are found, -you will be prompted to clean up. If you wish to clean up and continue, -select CLEAN. Otherwise, select QUIT to return to the Service Backup GUI.
-
-
If no files are found, the script will run silently and you will -not be notified.
-4. Another GUI will appear asking you "Would you also like -to Import Digital Forecast and/or Start GFE." Verify that only the "Start -GFE" button is -selected and press OK.
-
-
5. Another GUI will appear, asking for the ID of the -failed site. Enter the failed site's 3 letter ID and press OK.
-
-
6. After a few minutes, a progress bar will appear with -the status of the failed site's configuration. When it is finished, you -may close the progress bar.
-7. Once the configuration import is complete and the -failed site's server is started, the Service Backup GUI will make up to ten -attempts to connect to the server. If it is not able to connect after ten -attempts, you will be notified and will not be allowed to continue.
-
-
8. If the GUI is able to connect to the failed site's -server, the GFE Startup GUI will appear. Select a User, Config file, and -Mode and -press Start.
-- -
HOW TO IMPORT A FAILED SITE'S CONFIGURATION -[BACK TO THE TOP]
-1. Verify that the banner at the top of the Service Backup -GUI reads "YOU ARE NOT IN BACKUP MODE." If you are already in -backup mode, you will -need to clean up first.
-
-
2. Select Import Configuration Data and press OK.
-3. The script will first check to see if there are any -service backup files present that may cause a problem. If any are found, -you will be prompted to clean up. If you wish to clean up and continue, -select CLEAN. Otherwise, select QUIT to return to the Service Backup GUI.
-
-
If no files are found, the script will run silently and you will -not be notified.
-4. Another GUI will appear asking you "Would you also like -to Import Digital Forecast and/or Start GFE." Verify that both buttons are -deselected and press OK.
-
-
5. Another GUI will appear, asking for the ID of the -failed site. Enter the failed site's 3 letter ID and press OK.
-
-
-
-6. After a few minutes, a progress bar will appear with -the status of the failed site's configuration. When it is finished, you -may close the progress bar.
--
-HOW TO IMPORT A FAILED SITE'S DIGITAL DATA AND START THEIR GFE IN ONE STEP -[BACK TO THE TOP]
-1. Verify that the banner at the top of the Service Backup GUI reads -"YOU ARE CURRENTLY BACKING UP XXX" (where XXX is a failed site). If it doesn't, -you must first import -the failed site's configuration
- -
-
2. Select Import XXX's Digital Data and press OK.
- -3. Another GUI will appear asking you "Would you also like to Start -GFE." Verify that "Start GFE" is selected and press OK.
- -
-
4. After a few minutes, a progress bar will appear with the status of -the failed site's digital data. When it is finished, you may close the -progress bar.
- -5. If the import is successful, the GFE Startup GUI will appear. Select a User, Config -file, and Mode and press Start.
- -- -
HOW TO IMPORT A FAILED SITE'S DIGITAL DATA -[BACK TO THE TOP]
- -1. Verify that the banner at the top of the Service Backup GUI reads -"YOU ARE CURRENTLY BACKING UP XXX" (where XXX is a failed site). If it doesn't, -you must first -import the failed site's configuration.
- -
-
2. Select Import XXX's Digital Data and press OK.
- -3. Another GUI will appear asking you "Would you also like to Start -GFE." Verify that "Start GFE" is deselected and press OK.
- -
-
4. After a few minutes, a progress bar will appear with the status of -the failed site's digital data. When it is finished, you may close the -progress bar.
- -- -
HOW TO EXPORT GRIDS BACK TO A FAILED SITE -[BACK TO THE TOP]
-1. Verify that the banner at the top of the Service Backup GUI reads -"YOU ARE CURRENTLY BACKING UP XXX" (where XXX is a failed site). If it -doesn't, you must first -import the failed site's configuration.
-
-
2. Select Export Grids to XXX and press OK.
-3. A message will appear saying "Exporting Digital Data Back to XXX" -(where XXX is the failed site).
-
-
-
-HOW TO EXPORT A FAILED SITE'S DIGITAL DATA TO THE CENTRAL SERVER - -[BACK TO THE TOP]
-1. Verify that the message at the top of the GUI reads "YOU ARE -CURRENTLY BACKING UP XXX" (where XXX is a failed site). If it doesn't, you -must first -import the failed site's configuration.
-
-
2. Select Export XXX's Grids To The Central Server and press OK.
-3. A message will appear saying "Exporting XXX's Digital Data To The -Central Server" (where XXX is the failed site).
-
-
-
HOW TO EXPORT YOUR CONFIGURATION TO THE CENTRAL SERVER -[BACK TO THE TOP]
-1. Start the Service Backup GUI as user ifps. to do this:
- a. su ifps
-
- b. cd /awips/ifps/primary/bin
-
- c. ./service_backup.bat
2. Verify that the message at the top of the GUI reads "YOU ARE NOT IN -BACKUP MODE." If it does not, you will not be able to export your -configuration to the central server.
-
-
3. Select Export CCC's Configuration to the Central Server (where CCC -is your site's 3 letter ID) and press OK.
--
HOW TO EXPORT YOUR DIGITAL DATA TO THE CENTRAL SERVER -[BACK TO THE TOP]
-1. Select Export CCC's Digital Forecast to the Central Server (where -CCC is your site's 3 letter ID) and press OK.
--
HOW TO START GFE FROM THE SERVICE BACKUP GUI -[BACK TO THE TOP]
-1. Select Start GFE from the Service Backup GUI and press OK.
-2. If you are currently in Service Backup Mode or your site has -multiple domains, you will be asked which domain you would like to start GFE -for. Select a domain and press OK.
-
-
If you are not in Service Backup Mode or your site does not have multiple -domains, GFE will start for your site.
-3. The GFE Startup GUI will appear. Select a User, Config file, -and Mode and press Start.
--
HOW TO EXIT SERVICE BACKUP -[BACK TO THE TOP]
-1. Verify that the banner at the top of the Service Backup GUI reads -"YOU ARE CURRENTLY BACKING UP XXX" (where XXX is a failed site). If it -does not, you will not be able to exit service backup.
-
-
2. Select Exit Service Backup for XXX (where XXX is a failed site) and -press OK.
-3. The service backup clean up script will run. If it is -successful, the Service Backup GUI will disappear when it is finished.
--
HOW TO CLEAN UP SERVICE BACKUP -[BACK TO THE TOP]
-1. Select Clean Up Service Backup from the Service Backup GUI and press -OK.
-2. If the Service Backup GUI is able to determine the failed site, you -will see a message saying "Cleaning Up XXX's Configuration"
-
-
3. If the Service Backup GUI cannot determine the failed site's ID, a -GUI will appear asking you for the failed site's ID. Enter the failed -site's 3 letter ID and press OK.
-
-