xan/awips2
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Merge branch 'omaha_15.1.1' of ssh://awips2omaha.com:29418/AWIPS2_baseline into master_15.1.1

Browse source 
Conflicts:
	edexOsgi/com.raytheon.uf.edex.archive/utility/common_static/base/archiver/purger/RAW_DATA.xml
	edexOsgi/com.raytheon.uf.tools.gfesuite.servicebackup/svcBackup/ServiceBackup/scripts/export_configuration
	edexOsgi/com.raytheon.uf.tools.gfesuite.servicebackup/svcBackup/ServiceBackup/scripts/proc_receive_config

Former-commit-id: 7349df3d27 [formerly 9742125df2b54fe54e1e06dba554de21db52f5a0]
Former-commit-id: b0d72bf798
This commit is contained in:
Fay.Liang 2015-04-08 12:22:27 -04:00
commit 9d752cfc41
391 changed files with 7440 additions and 10079 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
build/deploy.edex.awips2/esb/conf/wrapper.conf
View file

@ -139,7 +139,7 @@ wrapper.java.additional.log.5=-Djava.util.logging.config.file=${EDEX_HOME}/conf/
# errors reported by thrift sometimes when the stream is corrupt/incorrect
wrapper.java.additional.thrift.maxStreamSize=-Dthrift.stream.maxsize=200
wrapper.java.additional.retain.failed=-Dretain.failed.data=${RETAIN_FAILED}
#wrapper.java.additional.retain.failed=-Dretain.failed.data=${RETAIN_FAILED}
# enables yourkit profiling, determined by flag to start.sh
wrapper.java.additional.profile.1=${PROFILER_PARAM_1}

2
cave/build/cave/memorySettings.xml
View file

@ -420,7 +420,7 @@
<site-type>ncep</site-type>
<ini-substitutions>
<max-memory>
<value>2048M</value>
<value>3072M</value>
</max-memory>
<max-perm>

601
cave/build/p2-build.xml
View file

@ -1,134 +1,112 @@
<project default="main" basedir=".">
<!-- TODO: Verify These Properties References An Actual Directory. -->
<property name="eclipse.dir"
value="/opt/uframe-eclipse" />
<property name="build.version"
value="1.0.0" />
<property name="build.os"
value="linux" />
<property name="build.ws"
value="gtk" />
<property name="build.arch"
value="x86" />
<property name="eclipse.dir" value="/opt/uframe-eclipse" />
<property name="build.version" value="1.0.0" />
<property name="build.os" value="linux" />
<property name="build.ws" value="gtk" />
<property name="build.arch" value="x86" />
<property name="workspace.dir" value="${basedir}/../" />
<property name="pde.build.script"
value="org.eclipse.pde.build_3.8.2.v20121114-140810/scripts/build.xml" />
<property name="eclipse.launcher.jar"
value="org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar" />
<property name="pde.build.script" value="org.eclipse.pde.build_3.8.2.v20121114-140810/scripts/build.xml" />
<property name="eclipse.launcher.jar" value="org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar" />
<!-- Verify That We Have Access To A Copy Of Eclipse -->
<target name="verify">
</target>
<!-- Creates The Temporary Directories That We Will Need To Build
The P2 Repositories. -->
<target name="init" depends="verify">
<!-- We Will Use A Temporary p2 Directory And Leave The
cave/tmp Directory For The Original PDE Build. -->
<mkdir dir="${basedir}/cave/p2" />
<!-- Copy The P2 Build build.properties File. -->
<copy tofile="${basedir}/cave/p2/build.properties"
file="${basedir}/build.properties.p2" verbose="true" />
<copy tofile="${basedir}/cave/p2/build.properties" file="${basedir}/build.properties.p2" verbose="true" />
<!-- We Will Copy The Plugins Here Eventually. -->
<mkdir dir="${basedir}/cave/p2/plugins" />
<!-- We Will Copy The Features Here Eventually. -->
<mkdir dir="${basedir}/cave/p2/features" />
<mkdir dir="${basedir}/cave/p2/repository" />
<mkdir dir="${basedir}/cave/p2/dist" />
<!-- BEGIN: Copy The Plugins -->
<echo message="PLUGINS: com.*/**" />
<copy todir="${basedir}/cave/p2/plugins">
<fileset dir="${workspace.dir}"
includes="com.*/**" />
</copy>
<echo message="PLUGINS: ucar.*/**" />
<copy todir="${basedir}/cave/p2/plugins">
<fileset dir="${workspace.dir}"
includes="ucar.*/**" />
</copy>
<echo message="PLUGINS: *.feature*/**" />
<copy todir="${basedir}/cave/p2/plugins">
<fileset dir="${workspace.dir}"
includes="*.feature*/**" />
</copy>
<echo message="PLUGINS: ncsa.*/**" />
<copy todir="${basedir}/cave/p2/plugins">
<fileset dir="${workspace.dir}"
includes="ncsa.*/**" />
</copy>
<echo message="PLUGINS: org.*/**" />
<copy todir="${basedir}/cave/p2/plugins">
<fileset dir="${workspace.dir}"
includes="org.*/**" />
</copy>
<echo message="PLUGINS: net.*/**" />
<copy todir="${basedir}/cave/p2/plugins">
<fileset dir="${workspace.dir}"
includes="net.*/**" />
</copy>
<echo message="PLUGINS: ohd*/**" />
<copy todir="${basedir}/cave/p2/plugins">
<fileset dir="${workspace.dir}"
includes="ohd*/**" />
</copy>
<echo message="PLUGINS: javax.*/**" />
<copy todir="${basedir}/cave/p2/plugins">
<fileset dir="${workspace.dir}"
includes="javax.*/**" />
</copy>
<echo message="PLUGINS: gov.*/**" />
<copy todir="${basedir}/cave/p2/plugins">
<fileset dir="${workspace.dir}"
includes="gov.*/**" />
</copy>
<echo message="PLUGINS: edu.*/**" />
<copy todir="${basedir}/cave/p2/plugins">
<fileset dir="${workspace.dir}"
includes="edu.*/**" />
</copy>
<echo message="PLUGINS: de.*/**" />
<copy todir="${basedir}/cave/p2/plugins">
<fileset dir="${workspace.dir}"
includes="de.*/**" />
</copy>
<echo message="PLUGINS: it.*/**" />
<copy todir="${basedir}/cave/p2/plugins">
<fileset dir="${workspace.dir}"
includes="it.*/**" />
</copy>
<echo message="PLUGINS: v*/**" />
<copy todir="${basedir}/cave/p2/plugins">
<fileset dir="${workspace.dir}"
includes="v*/**" />
<fileset dir="${workspace.dir}" includes="com.*/**" />
</copy>
<echo message="PLUGINS: ch.*/**" />
<copy todir="${basedir}/cave/p2/plugins">
<fileset dir="${workspace.dir}"
includes="ch.*/**" />
</copy>
<echo message="PLUGINS: ucar.*/**" />
<copy todir="${basedir}/cave/p2/plugins">
<fileset dir="${workspace.dir}" includes="ucar.*/**" />
</copy>
<echo message="PLUGINS: *.feature*/**" />
<copy todir="${basedir}/cave/p2/plugins">
<fileset dir="${workspace.dir}" includes="*.feature*/**" />
</copy>
<echo message="PLUGINS: ncsa.*/**" />
<copy todir="${basedir}/cave/p2/plugins">
<fileset dir="${workspace.dir}" includes="ncsa.*/**" />
</copy>
<echo message="PLUGINS: org.*/**" />
<copy todir="${basedir}/cave/p2/plugins">
<fileset dir="${workspace.dir}" includes="org.*/**" />
</copy>
<echo message="PLUGINS: net.*/**" />
<copy todir="${basedir}/cave/p2/plugins">
<fileset dir="${workspace.dir}" includes="net.*/**" />
</copy>
<echo message="PLUGINS: ohd*/**" />
<copy todir="${basedir}/cave/p2/plugins">
<fileset dir="${workspace.dir}" includes="ohd*/**" />
</copy>
<echo message="PLUGINS: javax.*/**" />
<copy todir="${basedir}/cave/p2/plugins">
<fileset dir="${workspace.dir}" includes="javax.*/**" />
</copy>
<echo message="PLUGINS: gov.*/**" />
<copy todir="${basedir}/cave/p2/plugins">
<fileset dir="${workspace.dir}" includes="gov.*/**" />
</copy>
<echo message="PLUGINS: edu.*/**" />
<copy todir="${basedir}/cave/p2/plugins">
<fileset dir="${workspace.dir}" includes="edu.*/**" />
</copy>
<echo message="PLUGINS: de.*/**" />
<copy todir="${basedir}/cave/p2/plugins">
<fileset dir="${workspace.dir}" includes="de.*/**" />
</copy>
<echo message="PLUGINS: it.*/**" />
<copy todir="${basedir}/cave/p2/plugins">
<fileset dir="${workspace.dir}" includes="it.*/**" />
</copy>
<echo message="PLUGINS: v*/**" />
<copy todir="${basedir}/cave/p2/plugins">
<fileset dir="${workspace.dir}" includes="v*/**" />
</copy>
<echo message="PLUGINS: ch.*/**" />
<copy todir="${basedir}/cave/p2/plugins">
<fileset dir="${workspace.dir}" includes="ch.*/**" />
</copy>
<!-- END: Copy The Plugins -->
</target>
<!-- Cleans Up Any Temporary Directories -->
<target name="clean">
<if>
@ -140,296 +118,237 @@
</then>
</if>
</target>
<tstamp>
<format property="build.timestamp"
pattern="yyyyMMddHHmm" />
<format property="build.timestamp" pattern="yyyyMMddHHmm" />
</tstamp>
<target name="p2.build" depends="clean, init">
<target name="p2.build" depends="clean, init">
<!-- We Need To Build The p2 Repos In A Certain Order Due To
Dependencies. -->
<!-- copy the com.raytheon.uf.viz.application.feature feature.
Used by the com.raytheon.viz.feature.awips feature. -->
<copy todir="${basedir}/cave/p2/features" verbose="true">
<fileset dir="${workspace.dir}"
includes="com.raytheon.uf.viz.application.feature/**" />
</copy>
<copy todir="${basedir}/cave/p2/features" verbose="true">
<fileset dir="${workspace.dir}" includes="com.raytheon.uf.viz.application.feature/**" />
</copy>
<antcall target="p2.build.repo">
<param name="feature"
value="com.raytheon.viz.feature.awips" />
<param name="omit"
value="true" />
<param name="feature" value="com.raytheon.viz.feature.awips" />
<param name="omit" value="true" />
</antcall>
<!--
we will still build this for the MSFT Windows CAVE.
-->
<antcall target="p2.build.repo">
<param name="feature"
value="com.raytheon.uf.common.base.feature" />
<param name="feature" value="com.raytheon.uf.common.base.feature" />
</antcall>
<antcall target="p2.build.repo">
<param name="feature"
value="com.raytheon.uf.viz.base.feature" />
<param name="feature" value="com.raytheon.uf.viz.base.feature" />
</antcall>
<antcall target="p2.build.repo">
<param name="feature"
value="com.raytheon.uf.viz.cots.feature" />
<param name="feature" value="com.raytheon.uf.viz.cots.feature" />
</antcall>
<antcall target="p2.build.repo">
<param name="feature"
value="com.raytheon.uf.viz.common.core.feature" />
</antcall>
<antcall target="p2.build.repo">
<param name="feature"
value="com.raytheon.uf.viz.localization.perspective.feature" />
</antcall>
<antcall target="p2.build.repo">
<param name="feature"
value="com.raytheon.uf.viz.core.feature" />
<param name="feature" value="com.raytheon.uf.viz.common.core.feature" />
</antcall>
<antcall target="p2.build.repo">
<param name="feature"
value="com.raytheon.uf.viz.core.maps.feature" />
<param name="feature" value="com.raytheon.uf.viz.localization.perspective.feature" />
</antcall>
<antcall target="p2.build.repo">
<param name="feature"
value="com.raytheon.uf.viz.sounding.feature" />
<param name="feature" value="com.raytheon.uf.viz.core.feature" />
</antcall>
<antcall target="p2.build.repo">
<param name="feature"
value="com.raytheon.uf.viz.dataplugin.obs.feature" />
<param name="feature" value="com.raytheon.uf.viz.core.maps.feature" />
</antcall>
<antcall target="p2.build.repo">
<param name="feature"
value="com.raytheon.uf.viz.dataplugins.feature" />
<param name="feature" value="com.raytheon.uf.viz.sounding.feature" />
</antcall>
<antcall target="p2.build.repo">
<param name="feature"
value="com.raytheon.uf.viz.d2d.core.feature" />
<param name="feature" value="com.raytheon.uf.viz.dataplugin.obs.feature" />
</antcall>
<antcall target="p2.build.repo">
<param name="feature"
value="com.raytheon.viz.radar.feature" />
<param name="feature" value="com.raytheon.uf.viz.dataplugins.feature" />
</antcall>
<antcall target="p2.build.repo">
<param name="feature"
value="com.raytheon.viz.text.feature" />
<param name="feature" value="com.raytheon.uf.viz.d2d.core.feature" />
</antcall>
<antcall target="p2.build.repo">
<param name="feature"
value="com.raytheon.viz.warngen.feature" />
<param name="feature" value="com.raytheon.viz.radar.feature" />
</antcall>
<antcall target="p2.build.repo">
<param name="feature"
value="com.raytheon.viz.grib.feature" />
</antcall>
<antcall target="p2.build.repo">
<param name="feature"
value="com.raytheon.uf.viz.kml.export.feature" />
</antcall>
<antcall target="p2.build.repo">
<param name="feature"
value="com.raytheon.viz.gfe.feature" />
<param name="feature" value="com.raytheon.viz.text.feature" />
</antcall>
<antcall target="p2.build.repo">
<param name="feature"
value="com.raytheon.uf.viz.displays.feature" />
<param name="feature" value="com.raytheon.viz.warngen.feature" />
</antcall>
<antcall target="p2.build.repo">
<param name="feature"
value="com.raytheon.viz.satellite.feature" />
<param name="feature" value="com.raytheon.viz.grib.feature" />
</antcall>
<antcall target="p2.build.repo">
<param name="feature"
value="com.raytheon.uf.viz.ncep.core.feature" />
<param name="feature" value="com.raytheon.uf.viz.kml.export.feature" />
</antcall>
<antcall target="p2.build.repo">
<param name="feature"
value="com.raytheon.uf.viz.aviation.advisory.feature" />
<param name="feature" value="com.raytheon.uf.viz.nwsauth.feature" />
</antcall>
<antcall target="p2.build.repo">
<param name="feature"
value="com.raytheon.uf.viz.ncep.dataplugins.feature" />
<param name="feature" value="com.raytheon.viz.gfe.feature" />
</antcall>
<antcall target="p2.build.repo">
<param name="feature"
value="com.raytheon.viz.hydro.feature" />
<param name="feature" value="com.raytheon.uf.viz.displays.feature" />
</antcall>
<antcall target="p2.build.repo">
<param name="feature"
value="com.raytheon.uf.viz.d2d.xy.feature" />
<param name="feature" value="com.raytheon.viz.satellite.feature" />
</antcall>
<antcall target="p2.build.repo">
<param name="feature"
value="com.raytheon.uf.viz.ncep.displays.feature" />
<param name="feature" value="com.raytheon.uf.viz.ncep.core.feature" />
</antcall>
<antcall target="p2.build.repo">
<param name="feature"
value="com.raytheon.uf.viz.ncep.nsharp.feature" />
<param name="feature" value="com.raytheon.uf.viz.aviation.advisory.feature" />
</antcall>
<antcall target="p2.build.repo">
<param name="feature"
value="com.raytheon.uf.viz.d2d.nsharp.feature" />
<param name="feature" value="com.raytheon.uf.viz.ncep.dataplugins.feature" />
</antcall>
<antcall target="p2.build.repo">
<param name="feature"
value="com.raytheon.uf.viz.archive.feature" />
<param name="feature" value="com.raytheon.viz.hydro.feature" />
</antcall>
<antcall target="p2.build.repo">
<param name="feature"
value="com.raytheon.uf.viz.ncep.perspective.feature" />
</antcall>
<antcall target="p2.build.repo">
<param name="feature"
value="com.raytheon.uf.viz.nwsauth.feature" />
</antcall>
<antcall target="p2.build.repo">
<param name="feature"
value="com.raytheon.uf.viz.thinclient.feature" />
<param name="feature" value="com.raytheon.uf.viz.d2d.xy.feature" />
</antcall>
<antcall target="p2.build.repo">
<param name="feature"
value="com.raytheon.uf.viz.useradmin.feature" />
</antcall>
<antcall target="p2.build.repo">
<param name="feature"
value="com.raytheon.uf.viz.registry.feature" />
</antcall>
<antcall target="p2.build.repo">
<param name="feature"
value="com.raytheon.uf.viz.datadelivery.feature" />
</antcall>
<antcall target="p2.build.repo">
<param name="feature"
value="com.raytheon.uf.viz.npp.feature" />
</antcall>
<antcall target="p2.build.repo">
<param name="feature"
value="com.raytheon.uf.viz.d2d.skewt.feature" />
<param name="feature" value="com.raytheon.uf.viz.ncep.displays.feature" />
</antcall>
<antcall target="p2.build.repo">
<param name="feature"
value="com.raytheon.viz.volumebrowser.feature" />
<param name="feature" value="com.raytheon.uf.viz.ncep.nsharp.feature" />
</antcall>
<antcall target="p2.build.repo">
<param name="feature"
value="com.raytheon.uf.viz.acarssounding.feature" />
</antcall>
<antcall target="p2.build.repo">
<param name="feature"
value="com.raytheon.viz.avnfps.feature" />
</antcall>
<antcall target="p2.build.repo">
<param name="feature"
value="com.raytheon.uf.viz.dat.feature" />
</antcall>
<antcall target="p2.build.repo">
<param name="feature"
value="com.raytheon.uf.viz.d2d.gfe.feature" />
<param name="feature" value="com.raytheon.uf.viz.d2d.nsharp.feature" />
</antcall>
<antcall target="p2.build.repo">
<param name="feature"
value="com.raytheon.uf.viz.collaboration.feature" />
</antcall>
<antcall target="p2.build.repo">
<param name="feature"
value="com.raytheon.uf.viz.gisdatastore.feature" />
</antcall>
<antcall target="p2.build.repo">
<param name="feature"
value="com.raytheon.uf.viz.d2d.ui.awips.feature" />
<param name="feature" value="com.raytheon.uf.viz.archive.feature" />
</antcall>
<antcall target="p2.build.repo">
<param name="feature" value="com.raytheon.uf.viz.ncep.perspective.feature" />
</antcall>
<antcall target="p2.build.repo">
<param name="feature" value="com.raytheon.uf.viz.thinclient.feature" />
</antcall>
<antcall target="p2.build.repo">
<param name="feature" value="com.raytheon.uf.viz.useradmin.feature" />
</antcall>
<antcall target="p2.build.repo">
<param name="feature" value="com.raytheon.uf.viz.registry.feature" />
</antcall>
<antcall target="p2.build.repo">
<param name="feature" value="com.raytheon.uf.viz.datadelivery.feature" />
</antcall>
<antcall target="p2.build.repo">
<param name="feature" value="com.raytheon.uf.viz.npp.feature" />
</antcall>
<antcall target="p2.build.repo">
<param name="feature" value="com.raytheon.uf.viz.d2d.skewt.feature" />
</antcall>
<antcall target="p2.build.repo">
<param name="feature" value="com.raytheon.viz.volumebrowser.feature" />
</antcall>
<antcall target="p2.build.repo">
<param name="feature" value="com.raytheon.uf.viz.acarssounding.feature" />
</antcall>
<antcall target="p2.build.repo">
<param name="feature" value="com.raytheon.viz.avnfps.feature" />
</antcall>
<antcall target="p2.build.repo">
<param name="feature" value="com.raytheon.uf.viz.dat.feature" />
</antcall>
<antcall target="p2.build.repo">
<param name="feature" value="com.raytheon.uf.viz.d2d.gfe.feature" />
</antcall>
<antcall target="p2.build.repo">
<param name="feature" value="com.raytheon.uf.viz.collaboration.feature" />
</antcall>
<antcall target="p2.build.repo">
<param name="feature" value="com.raytheon.uf.viz.gisdatastore.feature" />
</antcall>
<antcall target="p2.build.repo">
<param name="feature" value="com.raytheon.uf.viz.d2d.ui.awips.feature" />
</antcall>
<antcall target="cleanup.features" />
</target>
<target name="wa-build" depends="p2.build" description="Builds work assignment specific features after the main build">
<for param="wa.feature.list.file">
<fileset dir="${basedir}" includes="*-wa-build.properties" />
<sequential>
<var name="wa.features" unset="true" />
<property file="@{wa.feature.list.file}" />
<for list="${wa.features}" param="wa.feature">
<sequential>
<antcall target="p2.build.repo">
<param name="feature" value="@{wa.feature}" />
</antcall>
</sequential>
</for>
</sequential>
</for>
<for param="wa.feature.list.file">
<fileset dir="${basedir}" includes="*-wa-build.properties" />
<sequential>
<var name="wa.features" unset="true" />
<property file="@{wa.feature.list.file}" />
<for list="${wa.features}" param="wa.feature">
<sequential>
<antcall target="p2.build.repo">
<param name="feature" value="@{wa.feature}" />
</antcall>
</sequential>
</for>
</sequential>
</for>
</target>
<target name="wa-cleanup" depends="wa-build" description="Removes references to WA-specific features that should not be built as an RPM.">
<for param="wa.feature.list.file">
<fileset dir="${basedir}" includes="*-wa-build.properties" />
<sequential>
<var name="wa.features.ignore" unset="true" />
<property file="@{wa.feature.list.file}" />
<for list="${wa.features.ignore}" param="wa.feature">
<sequential>
<if>
<available file="${basedir}/cave/p2/features/@{wa.feature}" type="dir" />
<then>
<!-- Remove the feature directory. -->
<delete includeemptydirs="true">
<fileset dir="${basedir}/cave/p2/features/@{wa.feature}" />
</delete>
<!-- Remove references to the feature from features.txt -->
<exec executable="/bin/sed" output="${basedir}/cave/p2/dist/features.txt.tmp">
<arg value="/@{wa.feature}/d" />
<arg value="${basedir}/cave/p2/dist/features.txt" />
</exec>
<move file="${basedir}/cave/p2/dist/features.txt.tmp"
tofile="${basedir}/cave/p2/dist/features.txt" />
</then>
</if>
</sequential>
</for>
</sequential>
</for>
<for param="wa.feature.list.file">
<fileset dir="${basedir}" includes="*-wa-build.properties" />
<sequential>
<var name="wa.features.ignore" unset="true" />
<property file="@{wa.feature.list.file}" />
<for list="${wa.features.ignore}" param="wa.feature">
<sequential>
<if>
<available file="${basedir}/cave/p2/features/@{wa.feature}" type="dir" />
<then>
<!-- Remove the feature directory. -->
<delete includeemptydirs="true">
<fileset dir="${basedir}/cave/p2/features/@{wa.feature}" />
</delete>
<!-- Remove references to the feature from features.txt -->
<exec executable="/bin/sed" output="${basedir}/cave/p2/dist/features.txt.tmp">
<arg value="/@{wa.feature}/d" />
<arg value="${basedir}/cave/p2/dist/features.txt" />
</exec>
<move file="${basedir}/cave/p2/dist/features.txt.tmp" tofile="${basedir}/cave/p2/dist/features.txt" />
</then>
</if>
</sequential>
</for>
</sequential>
</for>
</target>
<target name="main" depends="clean, p2.build, wa-build, wa-cleanup" />
<target name="main" depends="clean, p2.build, wa-build, wa-cleanup" />
<target name="p2.build.repo">
<!-- Copy The Feature -->
<copy todir="${basedir}/cave/p2/features">
<fileset dir="${workspace.dir}"
includes="${feature}/**" />
<fileset dir="${workspace.dir}" includes="${feature}/**" />
</copy>
<!-- Update The Feature -->
<property name="process.feature.tool"
value="${workspace.dir}/build/tools/ProcessFeature.jar" />
<java
jar="${process.feature.tool}"
fork="true"
failonerror="false"
resultproperty="feature.tool.exitcode">
<property name="process.feature.tool" value="${workspace.dir}/build/tools/ProcessFeature.jar" />
<java jar="${process.feature.tool}" fork="true" failonerror="false" resultproperty="feature.tool.exitcode">
<arg value="-u" />
<arg value="${basedir}/cave/p2/features/${feature}" />
<arg value="${build.version}" />
</java>
<if>
<equals arg1="${feature.tool.exitcode}"
arg2="255" />
<equals arg1="${feature.tool.exitcode}" arg2="255" />
<then>
<fail message="${process.feature.tool} FAILED." />
</then>
</if>
<!-- Build The Repository -->
<java
classname="org.eclipse.core.launcher.Main"
fork="true"
failonerror="true">
<java classname="org.eclipse.core.launcher.Main" fork="true" failonerror="true">
<arg value="-application" />
<arg value="org.eclipse.ant.core.antRunner" />
<arg value="-buildfile" />
@ -440,30 +359,25 @@
<arg value="-DtopLevelElementId=${feature}" />
<arg value="-DforceContextQualifier=${build.timestamp}" />
<arg value="-Dconfigs=${build.os},${build.ws},${build.arch}" />
<classpath>
<pathelement
location="${eclipse.dir}/plugins/${eclipse.launcher.jar}" />
<pathelement location="${eclipse.dir}/plugins/${eclipse.launcher.jar}" />
</classpath>
</java>
<!-- Record that the feature has been built (for now) -->
<if>
<not>
<isset property="omit" />
</not>
<then>
<echo message="${feature}${line.separator}"
file="${basedir}/cave/p2/dist/features.txt"
append="true" />
<echo message="${feature}${line.separator}" file="${basedir}/cave/p2/dist/features.txt" append="true" />
</then>
</if>
<!-- Package The Repository -->
<zip
destfile="${basedir}/cave/p2/dist/${feature}-repo-${build.os}.${build.arch}.zip"
basedir="${basedir}/cave/p2/repository" />
<zip destfile="${basedir}/cave/p2/dist/${feature}-repo-${build.os}.${build.arch}.zip" basedir="${basedir}/cave/p2/repository" />
<!-- Cleanup The Current Build -->
<if>
<available file="${basedir}/cave/p2/I.CAVE" type="dir" />
@ -483,77 +397,56 @@
</if>
<mkdir dir="${basedir}/cave/p2/repository" />
</target>
<target name="cleanup.features">
<!-- Remove 'com.raytheon.viz.feature.awips' -->
<if>
<available
file="${basedir}/cave/p2/features/com.raytheon.viz.feature.awips"
type="dir" />
<available file="${basedir}/cave/p2/features/com.raytheon.viz.feature.awips" type="dir" />
<then>
<delete includeemptydirs="true">
<fileset
dir="${basedir}/cave/p2/features/com.raytheon.viz.feature.awips"
/>
<fileset dir="${basedir}/cave/p2/features/com.raytheon.viz.feature.awips" />
</delete>
</then>
</if>
<!-- Remove 'com.raytheon.uf.viz.feature.alertviz' -->
<if>
<available
file="${basedir}/cave/p2/features/com.raytheon.uf.viz.feature.alertviz"
type="dir" />
<available file="${basedir}/cave/p2/features/com.raytheon.uf.viz.feature.alertviz" type="dir" />
<then>
<delete includeemptydirs="true">
<fileset
dir="${basedir}/cave/p2/features/com.raytheon.uf.viz.feature.alertviz"
/>
<fileset dir="${basedir}/cave/p2/features/com.raytheon.uf.viz.feature.alertviz" />
</delete>
</then>
</if>
<!-- Remove 'com.raytheon.viz.feature.awips.developer' -->
<if>
<available
file="${basedir}/cave/p2/features/com.raytheon.viz.feature.awips.developer"
type="dir" />
<available file="${basedir}/cave/p2/features/com.raytheon.viz.feature.awips.developer" type="dir" />
<then>
<delete includeemptydirs="true">
<fileset
dir="${basedir}/cave/p2/features/com.raytheon.viz.feature.awips.developer"
/>
<fileset dir="${basedir}/cave/p2/features/com.raytheon.viz.feature.awips.developer" />
</delete>
</then>
</if>
<!-- Remove 'com.raytheon.uf.common.base.feature' -->
<if>
<available
file="${basedir}/cave/p2/features/com.raytheon.uf.common.base.feature"
type="dir" />
<available file="${basedir}/cave/p2/features/com.raytheon.uf.common.base.feature" type="dir" />
<then>
<delete includeemptydirs="true">
<fileset
dir="${basedir}/cave/p2/features/com.raytheon.uf.common.base.feature"
/>
<fileset dir="${basedir}/cave/p2/features/com.raytheon.uf.common.base.feature" />
</delete>
</then>
</if>
<!-- Remove 'com.raytheon.uf.viz.collaboration.product.feature' -->
<if>
<available file="${basedir}/cave/p2/features/com.raytheon.uf.viz.collaboration.product.feature" type="dir" />
<then>
<delete includeemptydirs="true">
<fileset dir="${basedir}/cave/p2/features/com.raytheon.uf.viz.collaboration.product.feature" />
</delete>
</then>
</if>
<!-- Remove 'com.raytheon.uf.viz.collaboration.product.feature' -->
<if>
<available
file="${basedir}/cave/p2/features/com.raytheon.uf.viz.collaboration.product.feature"
type="dir" />
<then>
<delete includeemptydirs="true">
<fileset
dir="${basedir}/cave/p2/features/com.raytheon.uf.viz.collaboration.product.feature"
/>
</delete>
</then>
</if>
</target>
<taskdef resource="net/sf/antcontrib/antlib.xml"
classpath="${basedir}/lib/ant/ant-contrib-1.0b3.jar" />
</project>
<taskdef resource="net/sf/antcontrib/antlib.xml" classpath="${basedir}/lib/ant/ant-contrib-1.0b3.jar" />
</project>

4
cave/com.raytheon.uf.viz.alertviz.ui/META-INF/MANIFEST.MF
View file

@ -1,8 +1,8 @@
Manifest-Version: 1.0
Bundle-ManifestVersion: 2
Bundle-Name: Ui Plug-in
Bundle-Name: AlertViz UI Plugin
Bundle-SymbolicName: com.raytheon.uf.viz.alertviz.ui
Bundle-Version: 1.14.0.qualifier
Bundle-Version: 1.15.0.qualifier
Bundle-Activator: com.raytheon.uf.viz.alertviz.ui.Activator
Bundle-Vendor: Raytheon
Require-Bundle: org.eclipse.ui,

14
cave/com.raytheon.uf.viz.alertviz.ui/src/com/raytheon/uf/viz/alertviz/ui/dialogs/AlertVisualization.java
View file

@ -19,7 +19,6 @@
package com.raytheon.uf.viz.alertviz.ui.dialogs;
import java.io.File;
import java.io.FileNotFoundException;
import org.eclipse.equinox.app.IApplication;
import org.eclipse.jface.dialogs.MessageDialog;
@ -49,7 +48,6 @@ import com.raytheon.uf.common.localization.LocalizationContext.LocalizationType;
import com.raytheon.uf.common.localization.PathManagerFactory;
import com.raytheon.uf.common.message.StatusMessage;
import com.raytheon.uf.common.status.UFStatus.Priority;
import com.raytheon.uf.viz.alertviz.AlertVizPython;
import com.raytheon.uf.viz.alertviz.AlertvizJob;
import com.raytheon.uf.viz.alertviz.ConfigContext;
import com.raytheon.uf.viz.alertviz.ConfigurationManager;
@ -95,6 +93,7 @@ import com.raytheon.uf.viz.core.VizApp;
* 09 Mar 2015 3856 lvenable Added a check to determine if the timer is running before
* changing the icon on the timer action. If it isn't running
* then set the icon to the default image.
* 18 Mar 2015 4234 njensen Remove reference to non-working python
*
* </pre>
*
@ -628,17 +627,6 @@ public class AlertVisualization implements ITimerAction, IAudioAction,
return;
}
// Run python script (this is done early since this will not block)
if (amd.isPythonEnabled() == true) {
try {
AlertVizPython.enqueue(statMsg, amd.clone(), gConfig);
} catch (FileNotFoundException e) {
Container.logInternal(Priority.ERROR,
"AlertVizualization: exception python script not found: "
+ amd.getPythonScript(), e);
}
}
boolean isGdnAdminMessage = statMsg.getCategory().equals("GDN_ADMIN")
|| statMsg.getSourceKey().equals("GDN_ADMIN");

46
cave/com.raytheon.uf.viz.alertviz.ui/src/com/raytheon/uf/viz/alertviz/ui/dialogs/PriorityControls.java
View file

@ -43,7 +43,6 @@ import org.eclipse.swt.widgets.Label;
import org.eclipse.swt.widgets.Shell;
import com.raytheon.uf.common.status.UFStatus.Priority;
import com.raytheon.uf.viz.alertviz.AlertVizPython;
import com.raytheon.uf.viz.alertviz.INeedsSaveListener;
import com.raytheon.uf.viz.alertviz.config.AlertMetadata;
@ -63,7 +62,8 @@ import com.raytheon.uf.viz.alertviz.config.AlertMetadata;
* 08 Sep 2012 13528 Xiaochuan Run setNewConfig to update priorities
* setting.
* 14 Dec 2012 4827 Xiaochuan Set toolTip on changeActionBtn.
*
* 18 Mar 2015 4234 njensen Remove reference to dead code
*
* </pre>
*
* @author lvenable
@ -74,7 +74,7 @@ public class PriorityControls {
/**
* Parent composite.
*/
private Composite parentComp;
private final Composite parentComp;
/**
* Canvas displaying the priority.
@ -99,7 +99,7 @@ public class PriorityControls {
/**
* Priority number.
*/
private int priority = 0;;
private int priority = 0;
/**
* Text message check box.
@ -144,7 +144,7 @@ public class PriorityControls {
/**
* Control font.
*/
private Font controlFont;
private final Font controlFont;
/**
* Canvas width.
@ -169,11 +169,11 @@ public class PriorityControls {
/**
* Parent shell.
*/
private Shell parentShell;
private final Shell parentShell;
private Button actionChk;
private AlertVisConfigDlg configDialog;
private final AlertVisConfigDlg configDialog;
/**
* Button used to change the audio file.
@ -184,7 +184,7 @@ public class PriorityControls {
private FileSelectDlg audioDlg;
private INeedsSaveListener needsSaveListener;
private final INeedsSaveListener needsSaveListener;
/**
* Constructor.
@ -197,12 +197,13 @@ public class PriorityControls {
* Priority number.
*/
public PriorityControls(Shell parentShell, Composite parentComp,
int priority, INeedsSaveListener needsSaveListener, AlertVisConfigDlg configDialog ) {
int priority, INeedsSaveListener needsSaveListener,
AlertVisConfigDlg configDialog) {
this.parentComp = parentComp;
this.priority = priority;
this.parentShell = parentShell;
this.configDialog = configDialog;
createPriorityColor();
this.controlFont = new Font(parentComp.getDisplay(), "Monospace", 10,
@ -222,12 +223,14 @@ public class PriorityControls {
priorityCanvas.setSize(CANVAS_WIDTH, CANVAS_HEIGHT);
priorityCanvas.setLayoutData(gd);
priorityCanvas.addPaintListener(new PaintListener() {
@Override
public void paintControl(PaintEvent e) {
drawCanvas(e.gc);
}
});
priorityCanvas.addDisposeListener(new DisposeListener() {
@Override
public void widgetDisposed(DisposeEvent e) {
priorityColor.dispose();
controlFont.dispose();
@ -247,6 +250,7 @@ public class PriorityControls {
textChk = new Button(parentComp, SWT.CHECK);
textChk.setLayoutData(gd);
textChk.addSelectionListener(new SelectionAdapter() {
@Override
public void widgetSelected(SelectionEvent event) {
updateBlinkButton();
configDialog.setNewConfig();
@ -266,8 +270,9 @@ public class PriorityControls {
blinkChk.setEnabled(false);
blinkChk.setLayoutData(gd);
blinkChk.addSelectionListener(new SelectionAdapter() {
@Override
public void widgetSelected(SelectionEvent event) {
alertMetadata.setBlink(blinkChk.getSelection());
alertMetadata.setBlink(blinkChk.getSelection());
configDialog.setNewConfig();
needsSaveListener.saveNeeded(true);
}
@ -284,6 +289,7 @@ public class PriorityControls {
popupChk = new Button(parentComp, SWT.CHECK);
popupChk.setLayoutData(gd);
popupChk.addSelectionListener(new SelectionAdapter() {
@Override
public void widgetSelected(SelectionEvent event) {
alertMetadata.setPopup(popupChk.getSelection());
configDialog.setNewConfig();
@ -310,8 +316,9 @@ public class PriorityControls {
audioChk.setLayoutData(gd);
audioChk.setToolTipText("");
audioChk.addSelectionListener(new SelectionAdapter() {
@Override
public void widgetSelected(SelectionEvent event) {
updateAudioChangeButton();
updateAudioChangeButton();
alertMetadata.setAudioEnabled(audioChk.getSelection());
configDialog.setNewConfig();
needsSaveListener.saveNeeded(true);
@ -322,6 +329,7 @@ public class PriorityControls {
changeAudioBtn.setText("...");
changeAudioBtn.setToolTipText("Change audio file");
changeAudioBtn.addSelectionListener(new SelectionAdapter() {
@Override
public void widgetSelected(SelectionEvent event) {
selectAudioFile();
configDialog.setNewConfig();
@ -346,6 +354,7 @@ public class PriorityControls {
actionChk.setLayoutData(gd);
actionChk.setToolTipText("Action File not available...");
actionChk.addSelectionListener(new SelectionAdapter() {
@Override
public void widgetSelected(SelectionEvent event) {
updateActionChangeButton();
alertMetadata.setPythonEnabled(actionChk.getSelection());
@ -358,6 +367,7 @@ public class PriorityControls {
changeActionBtn.setText("...");
changeActionBtn.setToolTipText("Change action file");
changeActionBtn.addSelectionListener(new SelectionAdapter() {
@Override
public void widgetSelected(SelectionEvent event) {
selectActionFile();
configDialog.setNewConfig();
@ -377,6 +387,7 @@ public class PriorityControls {
logChk = new Button(parentComp, SWT.CHECK);
logChk.setLayoutData(gd);
logChk.addSelectionListener(new SelectionAdapter() {
@Override
public void widgetSelected(SelectionEvent event) {
alertMetadata.setLog(logChk.getSelection());
configDialog.setNewConfig();
@ -417,8 +428,9 @@ public class PriorityControls {
changeTextColorBtn.setText("...");
changeTextColorBtn.setToolTipText("Change foreground/background color");
changeTextColorBtn.addSelectionListener(new SelectionAdapter() {
@Override
public void widgetSelected(SelectionEvent event) {
showColorDialog();
showColorDialog();
configDialog.setNewConfig();
}
@ -764,8 +776,8 @@ public class PriorityControls {
filteredExtensions.put(".py~", ".py~");
actionDlg = new FileSelectDlg(parentComp.getShell(),
SWT.APPLICATION_MODAL, AlertVizPython.ALERTVIZ_PYTHON_PATH,
new String[] { ".py", "*", "*.*" }, false, filteredExtensions);
SWT.APPLICATION_MODAL, "alertViz/python", new String[] { ".py",
"*", "*.*" }, false, filteredExtensions);
actionDlg.setSelectedFile(actionFile);
Boolean retVal = (Boolean) actionDlg.open("Action Selection File",
@ -784,7 +796,7 @@ public class PriorityControls {
saveNeeded = !selectedFileName.equals(actionFile);
alertMetadata.setPythonScript(selectedFileName);
changeActionBtn.setToolTipText(selectedFileName);
} else {
alertMetadata.setAudioFile(null);
alertMetadata.setAudioEnabled(false);

10
cave/com.raytheon.uf.viz.alertviz/META-INF/MANIFEST.MF
View file

@ -1,8 +1,8 @@
Manifest-Version: 1.0
Bundle-ManifestVersion: 2
Bundle-Name: Notification Plug-in
Bundle-Name: AlertViz Plugin
Bundle-SymbolicName: com.raytheon.uf.viz.alertviz;singleton:=true
Bundle-Version: 1.14.0.qualifier
Bundle-Version: 1.15.0.qualifier
Bundle-Activator: com.raytheon.uf.viz.alertviz.Activator
Bundle-Vendor: Raytheon
Require-Bundle: org.eclipse.ui,
@ -12,7 +12,6 @@ Require-Bundle: org.eclipse.ui,
com.raytheon.uf.common.serialization;visibility:=reexport,
com.raytheon.uf.viz.core;visibility:=reexport,
com.raytheon.uf.common.status,
org.jep;bundle-version="1.0.0",
com.raytheon.uf.common.message;bundle-version="1.11.11",
com.raytheon.uf.common.alertviz,
javax.jms;bundle-version="1.0.0",
@ -22,10 +21,7 @@ Require-Bundle: org.eclipse.ui,
Export-Package: com.raytheon.uf.viz.alertviz,
com.raytheon.uf.viz.alertviz.config
Bundle-RequiredExecutionEnvironment: JavaSE-1.7
Import-Package: com.raytheon.uf.common.python,
com.raytheon.uf.common.time,
com.raytheon.uf.viz.python.swt,
com.raytheon.uf.viz.python.swt.widgets,
Import-Package: com.raytheon.uf.common.time,
org.apache.log4j
Bundle-ActivationPolicy: lazy
Eclipse-RegisterBuddy: ch.qos.logback

191
cave/com.raytheon.uf.viz.alertviz/src/com/raytheon/uf/viz/alertviz/AlertVizPython.java
View file

@ -1,191 +0,0 @@
/**
* This software was developed and / or modified by Raytheon Company,
* pursuant to Contract DG133W-05-CQ-1067 with the US Government.
*
* U.S. EXPORT CONTROLLED TECHNICAL DATA
* This software product contains export-restricted data whose
* export/transfer/disclosure is restricted by U.S. law. Dissemination
* to non-U.S. persons whether in the United States or abroad requires
* an export license or other authorization.
*
* Contractor Name: Raytheon Company
* Contractor Address: 6825 Pine Street, Suite 340
* Mail Stop B8
* Omaha, NE 68106
* 402.291.0100
*
* See the AWIPS II Master Rights File ("Master Rights File.pdf") for
* further licensing information.
**/
package com.raytheon.uf.viz.alertviz;
import java.io.File;
import java.io.FileNotFoundException;
import java.util.HashMap;
import java.util.concurrent.ConcurrentLinkedQueue;
import jep.JepException;
import org.eclipse.core.runtime.IProgressMonitor;
import org.eclipse.core.runtime.IStatus;
import org.eclipse.core.runtime.Status;
import org.eclipse.core.runtime.jobs.Job;
import com.raytheon.uf.common.localization.IPathManager;
import com.raytheon.uf.common.localization.LocalizationContext;
import com.raytheon.uf.common.localization.LocalizationContext.LocalizationLevel;
import com.raytheon.uf.common.localization.LocalizationContext.LocalizationType;
import com.raytheon.uf.common.localization.PathManagerFactory;
import com.raytheon.uf.common.message.StatusMessage;
import com.raytheon.uf.common.python.PythonScript;
import com.raytheon.uf.common.status.UFStatus.Priority;
import com.raytheon.uf.viz.alertviz.config.AlertMetadata;
import com.raytheon.uf.viz.alertviz.config.TrayConfiguration;
/**
* TODO Add Description
*
* <pre>
*
* SOFTWARE HISTORY
* Date Ticket# Engineer Description
* ------------ ---------- ----------- --------------------------
* Jul 9, 2009 chammack Initial creation
* May 5, 2011 9101 cjeanbap Check Python Script type
*
* </pre>
*
* @author chammack
* @version 1.0
*/
public class AlertVizPython extends Job {
private String alertVizPythonDir;
private static ConcurrentLinkedQueue<ExecObj> execQueue = new ConcurrentLinkedQueue<ExecObj>();
private static ConcurrentLinkedQueue<Runnable> runQueue = new ConcurrentLinkedQueue<Runnable>();
private static AlertVizPython pythonThread;
public static final String ALERTVIZ_PYTHON_PATH = "alertViz/python";
private static class ExecObj {
public StatusMessage statusMessage;
public AlertMetadata alertMetadata;
public TrayConfiguration globalConfiguration;
}
public static void enqueue(StatusMessage statusMessage,
AlertMetadata alertMetadata, TrayConfiguration globalConfiguration)
throws FileNotFoundException {
File file = PathManagerFactory.getPathManager().getStaticFile(
ALERTVIZ_PYTHON_PATH + "/" + alertMetadata.getPythonScript());
if (file == null) {
throw new FileNotFoundException(
"Unable to find file in localization with name: "
+ alertMetadata.getPythonScript());
}
if (!alertMetadata.getPythonScript().endsWith(".py")) {
statusMessage.setDetails(file.getAbsolutePath());
alertMetadata.setPythonScript("PyShellScriptWrapper.py");
}
ExecObj eo = new ExecObj();
eo.statusMessage = statusMessage;
eo.alertMetadata = alertMetadata;
eo.globalConfiguration = globalConfiguration;
execQueue.add(eo);
if (pythonThread == null) {
pythonThread = new AlertVizPython();
pythonThread.setSystem(true);
pythonThread.schedule();
}
}
public static void run(Runnable run) {
runQueue.add(run);
}
private AlertVizPython() {
super("Alertviz Python Executor");
IPathManager pathMgr = PathManagerFactory.getPathManager();
LocalizationContext cx = pathMgr.getContext(
LocalizationType.CAVE_STATIC, LocalizationLevel.BASE);
File file = pathMgr.getFile(cx, ALERTVIZ_PYTHON_PATH);
cx = pathMgr.getContext(LocalizationType.CAVE_STATIC,
LocalizationLevel.SITE);
File file2 = pathMgr.getFile(cx, ALERTVIZ_PYTHON_PATH);
cx = pathMgr.getContext(LocalizationType.CAVE_STATIC,
LocalizationLevel.USER);
File file3 = pathMgr.getFile(cx, ALERTVIZ_PYTHON_PATH);
this.alertVizPythonDir = file.getAbsolutePath() + ":"
+ file2.getAbsolutePath() + ":" + file3.getAbsolutePath();
}
@Override
protected IStatus run(IProgressMonitor monitor) {
final String processorPython = ALERTVIZ_PYTHON_PATH
+ "/MasterProcessor.py";
PythonScript pythonScript = null;
try {
File file = PathManagerFactory.getPathManager().getStaticFile(
processorPython);
if (file == null) {
throw new RuntimeException("Master processor file missing");
}
pythonScript = new PythonScript(file.getAbsolutePath(),
alertVizPythonDir, this.getClass().getClassLoader());
while (!pythonThread.getThread().isInterrupted()) {
while (!runQueue.isEmpty()) {
runQueue.remove().run();
}
while (!execQueue.isEmpty()) {
ExecObj eo = execQueue.remove();
try {
HashMap<String, Object> args = new HashMap<String, Object>();
args.put("statusMessage", eo.statusMessage);
args.put("alertMetadata", eo.alertMetadata);
args.put("globalConfiguration", eo.globalConfiguration);
pythonScript.execute("process", args);
} catch (JepException e) {
Container.logInternal(Priority.ERROR,
"AlertVizPython: JEPP exception executing python script: "
+ processorPython, e);
}
}
try {
Thread.sleep(50);
} catch (InterruptedException e) {
return Status.OK_STATUS;
}
}
} catch (JepException e) {
Container.logInternal(Priority.ERROR,
"AlertVizPython: exception creating JEPP python script: "
+ processorPython, e);
} finally {
if (pythonScript != null) {
pythonScript.dispose();
}
}
return Status.OK_STATUS;
}
}

52
cave/com.raytheon.uf.viz.alertviz/src/com/raytheon/uf/viz/alertviz/AlertVizPythonCallback.java
View file

@ -1,52 +0,0 @@
/**
* This software was developed and / or modified by Raytheon Company,
* pursuant to Contract DG133W-05-CQ-1067 with the US Government.
*
* U.S. EXPORT CONTROLLED TECHNICAL DATA
* This software product contains export-restricted data whose
* export/transfer/disclosure is restricted by U.S. law. Dissemination
* to non-U.S. persons whether in the United States or abroad requires
* an export license or other authorization.
*
* Contractor Name: Raytheon Company
* Contractor Address: 6825 Pine Street, Suite 340
* Mail Stop B8
* Omaha, NE 68106
* 402.291.0100
*
* See the AWIPS II Master Rights File ("Master Rights File.pdf") for
* further licensing information.
**/
package com.raytheon.uf.viz.alertviz;
/**
* Provides a level of indirection to make sure that runnables are called back
* on the original python thread
*
* <pre>
*
* SOFTWARE HISTORY
* Date Ticket# Engineer Description
* ------------ ---------- ----------- --------------------------
* Jul 14, 2009 chammack Initial creation
*
* </pre>
*
* @author chammack
* @version 1.0
*/
public class AlertVizPythonCallback implements Runnable {
private Runnable run;
public AlertVizPythonCallback(Runnable run) {
this.run = run;
}
@Override
public void run() {
AlertVizPython.run(run);
}
}

12
cave/com.raytheon.uf.viz.d2d.ui/src/com/raytheon/uf/viz/d2d/ui/dialogs/procedures/ProcedureDlg.java
View file

@ -108,6 +108,7 @@ import com.raytheon.viz.ui.editor.AbstractEditor;
* Aug 11, 2014 3480 bclement added info logging when procedure is loaded
* Jan 06, 2015 3879 nabowle Disallow copy-in when the view is empty.
* Mar 02, 2015 4204 njensen Copy In uses tab name if applicable
* Mar 12, 2015 4204 njensen Ensure renamed bundle goes into tab name on next load
*
* </pre>
*
@ -577,8 +578,7 @@ public class ProcedureDlg extends CaveSWTDialog {
if (Window.OK == id.open()) {
String newName = id.getValue();
if (newName != null
&& "".equals(newName.trim()) == false) {
if (newName != null && !newName.trim().isEmpty()) {
b.name = newName;
resyncProcedureAndList();
saved = false;
@ -857,12 +857,14 @@ public class ProcedureDlg extends CaveSWTDialog {
}
private void load() {
if (dataList.getSelectionIndex() < 0) {
int index = dataList.getSelectionIndex();
if (index < 0) {
return;
}
try {
Bundle b = Bundle.unmarshalBundle(
bundles.get(dataList.getSelectionIndex()).xml, null);
BundlePair selected = bundles.get(index);
Bundle b = Bundle.unmarshalBundle(selected.xml);
b.setName(selected.name);
if (currentRdo.getSelection()) {
for (IAlterBundleContributor contributor : AlterBundleFactory
.getContributors()) {

8
cave/com.raytheon.uf.viz.d2d.ui/src/com/raytheon/uf/viz/d2d/ui/map/SideView.java
View file

@ -51,7 +51,6 @@ import com.raytheon.uf.viz.core.exception.VizException;
import com.raytheon.uf.viz.core.globals.VizGlobalsManager;
import com.raytheon.uf.viz.core.maps.scales.MapScalesManager;
import com.raytheon.uf.viz.core.procedures.Bundle;
import com.raytheon.uf.viz.core.rsc.AbstractVizResource;
import com.raytheon.uf.viz.core.rsc.IInputHandler;
import com.raytheon.uf.viz.core.rsc.IInputHandler.InputPriority;
import com.raytheon.uf.viz.core.time.TimeMatchingJob;
@ -95,6 +94,7 @@ import com.vividsolutions.jts.geom.Coordinate;
* Jul 15, 2014 2954 njensen Updated init() for MapScalesManager change
* Aug 25, 2014 3467 mapeters Removed changing of editability from swapPanes().
* Mar 02, 2015 4204 njensen Support for swapping part names
* Apr 02, 2015 4204 njensen Fix 4-panel swap of renamed parts
*
* </pre>
*
@ -365,7 +365,6 @@ public class SideView extends ViewPart implements IMultiPaneEditor,
}
IDisplayPane[] editorPanes = theEditor.getDisplayPanes();
AbstractVizResource<?, ?> editableResource = null;
// Set swapping so we don't get disposed, and find an editable
// resource if there is one
for (IDisplayPane dPane : editorPanes) {
@ -477,6 +476,11 @@ public class SideView extends ViewPart implements IMultiPaneEditor,
}
}
}
/*
* have to set part name again here cause addPane() or
* removePane() may mess it up
*/
theEditor.setPartName(viewName);
} else {
int min = Math.min(viewPaneCount, editorPaneCount);
for (int i = 0; i < min; ++i) {

21
cave/com.raytheon.uf.viz.d2d.ui/src/com/raytheon/uf/viz/d2d/ui/map/actions/FourPanelLayoutMenuAction.java
View file

@ -21,11 +21,14 @@ package com.raytheon.uf.viz.d2d.ui.map.actions;
import java.util.List;
import org.eclipse.ui.part.EditorPart;
import com.raytheon.uf.viz.core.IDisplayPane;
import com.raytheon.uf.viz.core.drawables.IRenderableDisplay;
import com.raytheon.uf.viz.d2d.core.ID2DRenderableDisplay;
import com.raytheon.uf.viz.d2d.core.legend.D2DLegendResource;
import com.raytheon.uf.viz.d2d.core.legend.D2DLegendResource.LegendMode;
import com.raytheon.viz.ui.IRenameablePart;
import com.raytheon.viz.ui.cmenu.AbstractRightClickAction;
import com.raytheon.viz.ui.editor.IMultiPaneEditor;
@ -45,6 +48,7 @@ import com.raytheon.viz.ui.editor.IMultiPaneEditor;
* Date Ticket# Engineer Description
* ------------ ---------- ----------- --------------------------
* Aug 19, 2009 bgonzale Initial Creation.
* Apr 07, 2015 4204 njensen Keep part name if renamed
*
* </pre>
*
@ -72,8 +76,16 @@ public class FourPanelLayoutMenuAction extends AbstractRightClickAction {
return;
}
IMultiPaneEditor editor = (IMultiPaneEditor) getContainer();
IRenderableDisplay definiteDisplay = (IRenderableDisplay) getContainer()
.getDisplayPanes()[0].getRenderableDisplay();
IRenderableDisplay definiteDisplay = getContainer().getDisplayPanes()[0]
.getRenderableDisplay();
String partName = null;
if (editor instanceof EditorPart) {
EditorPart part = (EditorPart) editor;
if (!part.getPartName().equals(part.getEditorInput().getName())) {
partName = part.getPartName();
}
}
if (editor.getNumberofPanes() > 1) {
for (IDisplayPane pane : getContainer().getDisplayPanes()) {
@ -85,6 +97,11 @@ public class FourPanelLayoutMenuAction extends AbstractRightClickAction {
}
}
// keep the part name if it was customized
if (partName != null && editor instanceof IRenameablePart) {
((IRenameablePart) editor).setPartName(partName);
}
for (IDisplayPane pane : editor.getDisplayPanes()) {
List<D2DLegendResource> rscs = pane.getDescriptor()
.getResourceList()

20
cave/com.raytheon.uf.viz.feature.alertviz/feature.xml
View file

@ -199,25 +199,12 @@
version="0.0.0"
unpack="false"/>
<plugin
id="com.raytheon.uf.common.python"
download-size="0"
install-size="0"
version="0.0.0"
unpack="false"/>
<plugin
id="org.postgres"
download-size="0"
install-size="0"
version="0.0.0"/>
<plugin
id="org.jep"
download-size="0"
install-size="0"
version="0.0.0"/>
<plugin
id="org.apache.velocity"
download-size="0"
@ -275,13 +262,6 @@
version="0.0.0"
unpack="false"/>
<plugin
id="com.raytheon.uf.viz.python.swt"
download-size="0"
install-size="0"
version="0.0.0"
unpack="false"/>
<plugin
id="com.raytheon.uf.common.serialization.comm"
download-size="0"

3
cave/com.raytheon.viz.gfe/META-INF/MANIFEST.MF
View file

@ -35,7 +35,8 @@ Require-Bundle: org.eclipse.ui,
com.raytheon.uf.viz.image.export;bundle-version="1.14.0",
com.raytheon.uf.viz.kml.export;bundle-version="1.14.1",
com.raytheon.uf.common.numeric;bundle-version="1.14.0",
com.raytheon.uf.common.topo;bundle-version="1.14.0"
com.raytheon.uf.common.topo;bundle-version="1.14.0",
com.raytheon.uf.common.plugin.nwsauth;bundle-version="1.14.0"
Bundle-ActivationPolicy: lazy
Export-Package: com.raytheon.viz.gfe,
com.raytheon.viz.gfe.constants,

148
cave/com.raytheon.viz.gfe/help/GfeServiceBackup/INSTRUCTIONS
View file

@ -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

BIN
cave/com.raytheon.viz.gfe/help/GfeServiceBackup/banner_exprtGrdMode.gif
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 12 KiB

BIN
cave/com.raytheon.viz.gfe/help/GfeServiceBackup/banner_exprtMode.gif
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 13 KiB

BIN
cave/com.raytheon.viz.gfe/help/GfeServiceBackup/banner_exprtbksiteGrdMode.gif
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 11 KiB

BIN
cave/com.raytheon.viz.gfe/help/GfeServiceBackup/banner_exprtbksiteGrdToCSMode.gif
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 12 KiB

BIN
cave/com.raytheon.viz.gfe/help/GfeServiceBackup/banner_ghgMode.gif
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 43 KiB

BIN
cave/com.raytheon.viz.gfe/help/GfeServiceBackup/banner_imprtGrdMode.gif
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 12 KiB

BIN
cave/com.raytheon.viz.gfe/help/GfeServiceBackup/banner_imprtMode.gif
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 12 KiB

BIN
cave/com.raytheon.viz.gfe/help/GfeServiceBackup/banner_no_backup.gif
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 11 KiB

BIN
cave/com.raytheon.viz.gfe/help/GfeServiceBackup/banner_svcbuMode.gif
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 12 KiB

BIN
cave/com.raytheon.viz.gfe/help/GfeServiceBackup/banner_waitMode.gif
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 12 KiB

BIN
cave/com.raytheon.viz.gfe/help/GfeServiceBackup/choose_domain.jpg
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 3.4 KiB

BIN
cave/com.raytheon.viz.gfe/help/GfeServiceBackup/choose_domain_multi1.jpg
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 6.9 KiB

BIN
cave/com.raytheon.viz.gfe/help/GfeServiceBackup/choose_domain_multi2.jpg
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 9.1 KiB

BIN
cave/com.raytheon.viz.gfe/help/GfeServiceBackup/clean_up.gif
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 7.3 KiB

BIN
cave/com.raytheon.viz.gfe/help/GfeServiceBackup/do_not_cancel.gif
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 7.3 KiB

BIN
cave/com.raytheon.viz.gfe/help/GfeServiceBackup/failed_site.jpg
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 15 KiB

BIN
cave/com.raytheon.viz.gfe/help/GfeServiceBackup/gfe_startup.gif
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 68 KiB

BIN
cave/com.raytheon.viz.gfe/help/GfeServiceBackup/images/banner_no_backup.png Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 36 KiB

BIN
cave/com.raytheon.viz.gfe/help/GfeServiceBackup/images/banner_svcbuMode.png Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 37 KiB

BIN
cave/com.raytheon.viz.gfe/help/GfeServiceBackup/images/banner_svcbuMode_2.png Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 37 KiB

BIN
cave/com.raytheon.viz.gfe/help/GfeServiceBackup/images/svcbu_confirm_exit.png Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 15 KiB

BIN
cave/com.raytheon.viz.gfe/help/GfeServiceBackup/images/svcbu_enter.png Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 35 KiB

BIN
cave/com.raytheon.viz.gfe/help/GfeServiceBackup/images/svcbu_exit.png Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 38 KiB

BIN
cave/com.raytheon.viz.gfe/help/GfeServiceBackup/images/svcbu_exit_status.png Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 14 KiB

BIN
cave/com.raytheon.viz.gfe/help/GfeServiceBackup/images/svcbu_export_config.png Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 38 KiB

BIN
cave/com.raytheon.viz.gfe/help/GfeServiceBackup/images/svcbu_export_config_status.png Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 12 KiB

BIN
cave/com.raytheon.viz.gfe/help/GfeServiceBackup/images/svcbu_export_grids.png Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 38 KiB

BIN
cave/com.raytheon.viz.gfe/help/GfeServiceBackup/images/svcbu_export_grids_status.png Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 14 KiB

BIN
cave/com.raytheon.viz.gfe/help/GfeServiceBackup/images/svcbu_export_local_grids_status.png Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 13 KiB

BIN
cave/com.raytheon.viz.gfe/help/GfeServiceBackup/images/svcbu_icon_failed.png Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 447 B

BIN
cave/com.raytheon.viz.gfe/help/GfeServiceBackup/images/svcbu_icon_in_progress_animated.gif Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 1.3 KiB

BIN
cave/com.raytheon.viz.gfe/help/GfeServiceBackup/images/svcbu_icon_not_started.png Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 221 B

BIN
cave/com.raytheon.viz.gfe/help/GfeServiceBackup/images/svcbu_icon_success.png Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 369 B

BIN
cave/com.raytheon.viz.gfe/help/GfeServiceBackup/images/svcbu_import_grids.png Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 38 KiB

BIN
cave/com.raytheon.viz.gfe/help/GfeServiceBackup/images/svcbu_import_grids_status.png Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 14 KiB

BIN
cave/com.raytheon.viz.gfe/help/GfeServiceBackup/images/svcbu_start_gfe.png Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 38 KiB

BIN
cave/com.raytheon.viz.gfe/help/GfeServiceBackup/images/svcbu_start_gfe_status.png Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 13 KiB

BIN
cave/com.raytheon.viz.gfe/help/GfeServiceBackup/images/svcbu_startup_status.png Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 22 KiB

BIN
cave/com.raytheon.viz.gfe/help/GfeServiceBackup/images/svcbu_startup_status_large.png Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 66 KiB

BIN
cave/com.raytheon.viz.gfe/help/GfeServiceBackup/multi_exprtGrdMode.gif
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 13 KiB

BIN
cave/com.raytheon.viz.gfe/help/GfeServiceBackup/multi_exprtMode.gif
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 14 KiB

BIN
cave/com.raytheon.viz.gfe/help/GfeServiceBackup/multi_exprtbksiteGrdMode.gif
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 13 KiB

BIN
cave/com.raytheon.viz.gfe/help/GfeServiceBackup/multi_exprtbksiteGrdToCSMode.gif
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 13 KiB

BIN
cave/com.raytheon.viz.gfe/help/GfeServiceBackup/multi_ghgMode.gif
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 43 KiB

BIN
cave/com.raytheon.viz.gfe/help/GfeServiceBackup/multi_imprtGrdMode.gif
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 13 KiB

BIN
cave/com.raytheon.viz.gfe/help/GfeServiceBackup/multi_imprtMode.gif
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 13 KiB

BIN
cave/com.raytheon.viz.gfe/help/GfeServiceBackup/multi_no_backup.gif
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 11 KiB

BIN
cave/com.raytheon.viz.gfe/help/GfeServiceBackup/multi_svcbuMode.gif
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 12 KiB

BIN
cave/com.raytheon.viz.gfe/help/GfeServiceBackup/multi_waitMode.gif
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 13 KiB

BIN
cave/com.raytheon.viz.gfe/help/GfeServiceBackup/option_both.jpg
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 12 KiB

BIN
cave/com.raytheon.viz.gfe/help/GfeServiceBackup/option_gfe.jpg
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 12 KiB

BIN
cave/com.raytheon.viz.gfe/help/GfeServiceBackup/option_import.jpg
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 12 KiB

BIN
cave/com.raytheon.viz.gfe/help/GfeServiceBackup/option_import_gfe.jpg
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 10 KiB

BIN
cave/com.raytheon.viz.gfe/help/GfeServiceBackup/option_import_no_gfe.jpg
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 10 KiB

BIN
cave/com.raytheon.viz.gfe/help/GfeServiceBackup/option_none.jpg
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 12 KiB

86
cave/com.raytheon.viz.gfe/help/GfeServiceBackup/svcbu_cleanup.html Normal file
View file

@ -0,0 +1,86 @@
<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
<head>
<meta name="Author" content="Ron Anderson">
<title>Service Backup Exit/Cleanup Actions</title>
</head>
<body>
<H3><a name="Export_Failed_Grids">EXPORTING FAILED SITE'S GRIDS</a></H3>
<ol>
<li>Verify that the failed site is listed in the banner at the top of the Service Backup Dialog under
&quot;YOU ARE CURRENTLY BACKING UP&quot;. If it isn't, you must first
<a href="svcbu_startup.html#Entering_Svcbu" style="text-decoration: none">enter service backup for the failed site.</a>
</li>
<p align="center">
<img border="0" src="images/banner_svcbuMode_2.png"></p>
<li>Select the failed site from the drop down next to the "Export Forecast Grids" button.
Only sites you are currently backing up will appear at the top of the list.
</li>
<p align="center">
<img border="0" src="images/svcbu_export_grids.png"></p>
<li>
Click the "Export Forecast Grids" button to start the import.
</li>
<li>A
<a target="main" style="text-decoration: none"
href="svcbu_status_dialog.html#Status_Information">Service Backup Status Dialog</a>
will open showing the status of each step required to export
the failed site's forecast grids.
<p align="center">
<img border="0" src="images/svcbu_export_grids_status.png"</p>
</li>
</ol>
<H3><a name="Exiting_Svcbu">EXITING SERVICE BACKUP</a></H3>
<ol>
<li>Verify that the failed site is listed in the banner at the top of the Service Backup Dialog under
&quot;YOU ARE CURRENTLY BACKING UP&quot;. If it isn't, you must first
<a href="svcbu_startup.html#Entering_Svcbu" style="text-decoration: none">enter service backup for the failed site.</a>
</li>
<p align="center">
<img border="0" src="images/banner_svcbuMode_2.png"></p>
<li>Select the failed site from the drop down next to the "Exit Service Backup" button.
Only sites you are currently backing up will appear at the top of the list.
</li>
<p align="center">
<img border="0" src="images/svcbu_exit.png"></p>
<li>
Click the "Exit Service Backup" button.
</li>
<li>A Confirm Exit Dialog will be displayed asking if you have contacted the failed site to
confirm they have receive their forecast grids. It is imperative that you do this prior to
exiting service backup or the grids may be lost.
</li>
<p align="center">
<img border="0" src="images/svcbu_confirm_exit.png"</p>
<p>If you have contacted the failed site and confirmed receipt of their forecast grids,
click Yes to exit service backup.<BR>
If not, click No and contact the failed site.</p>
<li>A
<a target="main" style="text-decoration: none"
href="svcbu_status_dialog.html#Status_Information">Service Backup Status Dialog</a>
will open showing the status of each step required to exit
service backup.
<p align="center">
<img border="0" src="images/svcbu_exit_status.png"</p>
</li>
</ol>
</body>
</html>

764
cave/com.raytheon.viz.gfe/help/GfeServiceBackup/svcbu_faq.html
View file

@ -1,764 +0,0 @@
<!DOCTYPE html PUBLIC "-//w3c//dtd html 4.0 transitional//en">
<html>
<head>
<meta name="Author" content="John Wagner">
<title>Service Backup FAQ</title>
</head>
<body>
<table border="0" width="100%">
<tbody>
<tr valign="top">
<td align="center" valign="top">
<h1><a name="#[BACK TO THE TOP]"><font color="#0000ff"><i>Service
Backup GUI</i> </font></a></h1>
<a name="#[BACK TO THE TOP]"> </a>
<h2><a name="#[BACK TO THE TOP]"><font color="BLACK"><i>FAQ</i></font></a></h2>
</td>
</tr>
</tbody>
</table>
<br>
<hr noshade="noshade" size="5">
<h3>&nbsp;&nbsp;&nbsp;Contents of this section</h3>
<p align="left">
<a
href="#1.%20%20WHAT%20IS%20THE%20DIFFERENCE%20BETWEEN%20EXIT%20SERVICE%20BACKUP%20AND%20CLEAN%20UP%20SERVICE%20BACKUP"
style="text-decoration: none;">1.&nbsp; WHAT IS THE DIFFERENCE BETWEEN
EXIT SERVICE BACKUP AND CLEAN UP SERVICE BACKUP?</a></p>
<p align="left">
<a
href="#2.%20%20WHY%20IS%20THE%20EXPORT%20CCCS%20CONFIGURATION%20TO%20THE%20CENTRAL%20SERVER%20BUTTON%20GRAYED%20OUT"
style="text-decoration: none;">2.&nbsp; WHY IS THE "EXPORT CCC'S
CONFIGURATION TO THE CENTRAL SERVER" BUTTON GRAYED OUT?</a></p>
<p align="left">
<a
href="#3.__WHY_IS_THE_EXPORT_CCCS_DIGITAL_FORECAST_TO_THE_CENTRAL_SERVER_BUTTON_GRAYED_OUT"
style="text-decoration: none;">3.&nbsp; WHY IS THE "EXPORT CCC'S
DIGITAL FORECAST TO THE CENTRAL SERVER" BUTTON GRAYED OUT?</a></p>
<p align="left">
<a href="#3.%20%20WHEN%20SHOULD%20I%20USE%20THE%20REFRESH%20BUTTON"
style="text-decoration: none;">4</a><a
href="#3.%20%20WHEN%20SHOULD%20I%20USE%20THE%20REFRESH%20BUTTON"
style="text-decoration: none;">.&nbsp; WHEN SHOULD I USE THE REFRESH
BUTTON?</a></p>
<p align="left">
<a
href="#4.__DO_I_NEED_TO_EXPORT_A_FAILED_SITES_GRIDS_TO_THE_CENTRAL_SERVER"
style="text-decoration: none;">5.&nbsp; DO I NEED TO EXPORT A FAILED
SITE'S GRIDS TO THE CENTRAL SERVER?</a></p>
<p align="left"><a href="#3.%20%20ERROR%20MESSAGES"
style="text-decoration: none;">6</a><a href="#3.%20%20ERROR%20MESSAGES"
style="text-decoration: none;">.&nbsp; ERROR MESSAGES</a></p>
<p align="left">&nbsp;&nbsp;&nbsp; SCAN THROUGH ERRORS THAT OCCUR WHEN:<br>
&nbsp;&nbsp;&nbsp; <a href="#IMPORTING_CONFIGURATION"
style="text-decoration: none;">IMPORTING CONFIGURATION</a>
<br>
&nbsp;&nbsp;&nbsp; <a href="#IMPORTING_DIGITAL_DATA"
style="text-decoration: none;">IMPORTING DIGITAL DATA</a>
<br>
&nbsp;&nbsp;&nbsp; <a href="#STARTING_GFE"
style="text-decoration: none;">STARTING GFE</a>
<br>
&nbsp;&nbsp;&nbsp;
<a href="#EXPORTING_DIGITAL_DATA_BACK_TO_A_FAILED_SITE"
style="text-decoration: none;">EXPORTING DIGITAL DATA BACK TO A FAILED
SITE</a>
<br>
&nbsp;&nbsp;&nbsp;
<a href="#EXPORTING_A_FAILED_SITES_DIGITAL_DATA_TO_THE_CENTRAL_SERVER"
style="text-decoration: none;">EXPORTING A FAILED SITE'S DIGITAL DATA
TO THE CENTRAL SERVER</a>
<br>
&nbsp;&nbsp;&nbsp;
<a href="#EXPORTING_CONFIGURATION_TO_THE_CENTRAL_SERVER"
style="text-decoration: none;">EXPORTING CONFIGURATION TO THE CENTRAL
SERVER</a>
<br>
&nbsp;&nbsp;&nbsp;
<a href="#EXPORTING_YOUR_DIGITAL_DATA_TO_THE_CENTRAL_SERVER"
style="text-decoration: none;">EXPORTING YOUR DIGITAL DATA TO THE
CENTRAL SERVER</a>
<br>
&nbsp;&nbsp;&nbsp; <a href="#EXITING_SERVICE_BACKUP"
style="text-decoration: none;">EXITING SERVICE BACKUP</a>
<br>
&nbsp;&nbsp;&nbsp; <a href="#CLEANING_UP_SERVICE_BACKUP"
style="text-decoration: none;">CLEANING UP SERVICE BACKUP</a>
</p>
<hr>
<p align="left"><b><a
name="1. WHAT IS THE DIFFERENCE BETWEEN EXIT SERVICE BACKUP AND CLEAN UP SERVICE BACKUP">1.&nbsp;
WHAT IS THE DIFFERENCE BETWEEN "EXIT SERVICE BACKUP" AND "CLEAN UP
SERVICE BACKUP"?</a>&nbsp; </b>
<a href="#%5BBACK%20TO%20THE%20TOP%5D" style="text-decoration: none;">[BACK
TO THE TOP]</a></p>
<p style="margin-left: 10px;" align="left">The Exit Service Backup
button is only enabled while you are in Service Backup Mode.&nbsp;
Selecting this button will run the clean up script and will exit the
Service Backup GUI when it is finished.&nbsp; The Clean Up Service
Backup button is enabled even when you are not in Service Backup
Mode.&nbsp; Selecting this button while in Service Backup Mode will run
the clean up script, but will not exit the Service Backup GUI.&nbsp;
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.</p>
<p><b>
<a
name="2. WHY IS THE EXPORT CCCS CONFIGURATION TO THE CENTRAL SERVER BUTTON GRAYED OUT">2.&nbsp;
WHY IS THE "EXPORT CCC'S CONFIGURATION TO THE CENTRAL SERVER" BUTTON
GRAYED OUT?</a>&nbsp; </b>
<a href="#%5BBACK%20TO%20THE%20TOP%5D" style="text-decoration: none;">[BACK
TO THE TOP]</a></p>
<p style="margin-left: 10px;">This button is only enabled while you are
not in Service Backup Mode and the Service Backup GUI is started as
user ifps.&nbsp; If the GUI is started by any other user or you are in
Service Backup Mode, this button will be grayed out.&nbsp; To start the
GUI as user ifps:</p>
<p style="margin-left: 10px;"><font face="Lucida Console">1.&nbsp; su
ifps</font>
<br style="margin-left: 10px;">
<font face="Lucida Console">2.&nbsp; cd /awips/ifps/primary/bin</font>
<br style="margin-left: 10px;">
<font face="Lucida Console">3.&nbsp; ./service_backup.bat</font></p>
<p><b>
<a
name="3.__WHY_IS_THE_EXPORT_CCCS_DIGITAL_FORECAST_TO_THE_CENTRAL_SERVER_BUTTON_GRAYED_OUT">3.&nbsp;
WHY IS THE "EXPORT CCC'S DIGITAL FORECAST TO THE CENTRAL SERVER" BUTTON
GRAYED OUT?</a> </b><a href="##%5BBACK%20TO%20THE%20TOP%5D"
style="text-decoration: none;">[BACK TO THE TOP]</a></p>
<p style="margin-left: 10px;">This button will become disabled when
your are in the process of exporting your grids to the central server
for service backup.&nbsp; 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.&nbsp; 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.&nbsp; This is done to prevent all WFOs from exporting
their grids at the same time.&nbsp; If you send the grids from the
Service Backup GUI, they will be send immediately after ifpetCDF
runs.&nbsp; </p>
<p><a name="3. WHEN SHOULD I USE THE REFRESH BUTTON"><b>4</b></a><b><a
name="3. WHEN SHOULD I USE THE REFRESH BUTTON">.&nbsp; WHEN SHOULD I
USE THE REFRESH BUTTON?</a></b>
<a href="#%5BBACK%20TO%20THE%20TOP%5D" style="text-decoration: none;">[BACK
TO THE TOP]</a></p>
<p style="margin-left: 10px;">The REFRESH button will update the state
of the Service Backup GUI.&nbsp; 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.&nbsp; </p>
<p><a
name="4.__DO_I_NEED_TO_EXPORT_A_FAILED_SITES_GRIDS_TO_THE_CENTRAL_SERVER">
<b>5</b></a><b><a
name="4.__DO_I_NEED_TO_EXPORT_A_FAILED_SITES_GRIDS_TO_THE_CENTRAL_SERVER">.&nbsp;
DO I NEED TO EXPORT A FAILED SITE'S GRIDS TO THE CENTRAL SERVER?</a></b>&nbsp;
<a href="#%5BBACK%20TO%20THE%20TOP%5D">[BACK TO THE TOP]</a></p>
<p style="margin-left: 10px;">Starting in IFPS16.1, the Service Backup
GUI contains an option to export the failed site's digital data to the
central server.&nbsp; This is a cautionary step to help prevent the
loss of data when restoring grids to a failed site.&nbsp; If you are
unable to export a failed site's grids back to them, you can export
them to the central server.&nbsp; Then, the failed site can contact the
NCF, who has instructions on how to restore the digital data from the
central server.</p>
<p><a name="3. ERROR MESSAGES"><b>6</b></a><b><a
name="3. ERROR MESSAGES">.&nbsp; ERROR MESSAGES</a>&nbsp; </b>
<a href="#%5BBACK%20TO%20THE%20TOP%5D" style="text-decoration: none;">[BACK
TO THE TOP]</a></p>
<p style="margin-left: 10px;">This section will explain some of the
different error messages that you may see while using the Service
Backup GUI.</p>
<p style="margin-left: 10px;">
<img src="xmessage_faq_01.jpg" border="0" height="96" width="295"></p>
<p style="margin-left: 10px;">When you start the Service Backup GUI
while in service backup mode, you will be prompted to select a
domain.&nbsp; You will see this message if you attempt to start the
Service Backup GUI as the failed site.&nbsp; The Service Backup GUI
must always be started as your site.</p>
<p style="margin-left: 10px;">&nbsp;</p>
<p style="margin-left: 10px;"><font size="4"><b><a
name="IMPORTING_CONFIGURATION">
IMPORTING CONFIGURATION</a>&nbsp; </b><a
href="#%5BBACK%20TO%20THE%20TOP%5D" style="text-decoration: none;">[BACK
TO THE TOP]</a></font></p>
<p style="margin-left: 10px;">&nbsp;</p>
<p style="margin-left: 10px;">
<img src="xmessage_faq_02.jpg" border="0" height="96" width="480"></p>
<p style="margin-left: 10px;">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.&nbsp; If
any IFPS databases are found, you will see this message.&nbsp; If you
wish to continue, you must select the CLEAN button to clean up that
site's database and configuration.&nbsp; If you do not wish to clean up
this site's database and configuration, select QUIT to return to the
Service Backup GUI.&nbsp; For more information, see
/data/logs/adapt/ifps/&lt;date&gt;/svcbu_check_&lt;time&gt; on dx4f.</p>
<p style="margin-left: 10px;">&nbsp;</p>
<p style="margin-left: 10px;">
<img src="xmessage_faq_03.jpg" border="0" height="96" width="579"></p>
<p style="margin-left: 10px;">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.&nbsp; If any
IFPS files are found, you will see this message.&nbsp; If you wish to
continue, you must select the CLEAN button to clean up that site's
configuration.&nbsp; If you do not wish to clean up this site's
configuration, select QUIT to return to the Service Backup GUI.&nbsp;
For more information, see
/data/logs/adapt/ifps/&lt;date&gt;/svcbu_check_&lt;time&gt; on dx4f.</p>
<p style="margin-left: 10px;">&nbsp;</p>
<p style="margin-left: 10px;">
<img src="xmessage_faq_04.jpg" border="0" height="96" width="686"></p>
<p style="margin-left: 10px;">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.&nbsp; If any
GFE files are found, you will see this message.&nbsp; If you wish to
continue, you must select the CLEAN button to clean up that site's
configuration.&nbsp; If you do not wish to clean up this site's
configuration, select QUIT to return to the Service Backup GUI.&nbsp;
For more information, see
/data/logs/adapt/ifps/&lt;date&gt;/svcbu_check_&lt;time&gt; on dx4f.</p>
<p style="margin-left: 10px;">&nbsp;</p>
<p style="margin-left: 10px;">
<img src="xmessage_faq_05.jpg" border="0" height="96" width="587"></p>
<p style="margin-left: 10px;">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.&nbsp; 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.&nbsp; Press the
DETAILS button to view the log file to see what files were found.&nbsp;
You must delete these files before you are allowed to continue.&nbsp;
If you do not wish to clean up, select QUIT to return to the Service
Backup GUI.&nbsp; For more information, see
/data/logs/adapt/ifps/&lt;date&gt;/svcbu_check_&lt;time&gt; on dx4f.</p>
<p style="margin-left: 10px;">&nbsp;</p>
<p style="margin-left: 10px;">
<img src="xmessage_faq_06.jpg" border="0" height="96" width="445"></p>
<p style="margin-left: 10px;">You will see this error message if you
import you own site ID when asked what site's configuration you wish to
import.&nbsp; If your site has multiple domains, you will not be
allowed to import either domain's configuration.</p>
<p style="margin-left: 10px;">&nbsp;</p>
<p style="margin-left: 10px;">
<img src="xmessage_faq_07.jpg" border="0" height="96" width="402"></p>
<p style="margin-left: 10px;">You will see this error message when you
attempt to import a failed site's configuration while in service backup
mode.&nbsp; 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.</p>
<p style="margin-left: 10px;">&nbsp;</p>
<p style="margin-left: 10px;">
<img src="xmessage_faq_67.jpg" border="0" height="96" width="721"></p>
<p style="margin-left: 10px;">You will see this error message if a
failed site's configuration fails to reach your site after 30
minutes.&nbsp; Possible reasons for seeing this message are problems
with msg_send or the failed site's configuration is not present on the
central server.&nbsp; If you would like to continue to wait for the
failed site's configuration, for up to another 30 minutes, press
YES.&nbsp; If you do not wish to wait, select NO.&nbsp; Selecting NO
will clean up the necessary lock files and return you to the Service
Backup GUI.</p>
<p style="margin-left: 10px;">&nbsp;</p>
<p style="margin-left: 10px;">
<img src="xmessage_faq_08.jpg" border="0" height="118" width="385"></p>
<p style="margin-left: 10px;">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.&nbsp; If you wish to import a
failed site's configuration, you must first wait until after the server
is started.&nbsp; Be sure to clean up before importing.</p>
<p style="margin-left: 10px;">&nbsp;</p>
<p style="margin-left: 10px;">
<img src="xmessage_faq_09.jpg" border="0" height="118" width="385"></p>
<p style="margin-left: 10px;">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.&nbsp; If you wish to import a failed
site's configuration, you must first wait until after the import of the
digital data is finished.&nbsp; Be sure to clean up before importing. </p>
<p style="margin-left: 10px;">&nbsp;</p>
<p style="margin-left: 10px;">
<img src="xmessage_faq_10.jpg" border="0" height="118" width="382"></p>
<p style="margin-left: 10px;">You will see this error message when you
attempt to import a failed site's configuration while an import process
is already running.&nbsp; If you wish to import a failed site's
configuration, you must first wait until the first import is
finished.&nbsp; Be sure to clean up before importing.</p>
<p style="margin-left: 10px;">&nbsp;</p>
<p style="margin-left: 10px;">
<img src="xmessage_faq_38.jpg" border="0" height="118" width="429"></p>
<p style="margin-left: 10px;">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.&nbsp; If you
wish to import a failed site's configuration, you must first wait until
the export is finished.</p>
<p style="margin-left: 10px;">&nbsp;</p>
<p style="margin-left: 10px;">
<img src="xmessage_faq_39.jpg" border="0" height="118" width="390"></p>
<p style="margin-left: 10px;">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.&nbsp; If you wish to
import a failed site's configuration, you must first wait until the
export is finished. </p>
<p style="margin-left: 10px;">&nbsp;</p>
<p style="margin-left: 10px;">
<img src="xmessage_faq_40.jpg" border="0" height="118" width="390"></p>
<p style="margin-left: 10px;">You will see this error message when you
attempt to import a failed site's configuration while exporting grids
back to a failed site.&nbsp; If you wish to import another failed
site's configuration, you must wait until the export is finished.&nbsp;
Be sure to clean up the first site's configuration before starting
another import.</p>
<p style="margin-left: 10px;">&nbsp;</p>
<p style="margin-left: 10px;">
<img src="xmessage_faq_50.jpg" border="0" height="118" width="385"></p>
<p style="margin-left: 10px;">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.&nbsp; If you wish to import
another failed site's configuration, you must wait until the export is
finished.&nbsp; Be sure to clean up the first site's configuration
before starting another import.</p>
<p style="margin-left: 10px;">&nbsp;</p>
<p style="margin-left: 10px;">
<img src="xmessage_faq_11.jpg" border="0" height="96" width="401"></p>
<p style="margin-left: 10px;">You will see this error message if there
was a problem importing a failed site's configuration, digital data,
and/or starting their GFE.&nbsp; For more information, see
/data/logs/adapt/ifps/&lt;date&gt;/svcbu_doall_&lt;time&gt; on the
machine that you started the import from.</p>
<p style="margin-left: 10px;">&nbsp;</p>
<p style="margin-left: 10px;"><font size="4"><b><a
name="IMPORTING_DIGITAL_DATA">
IMPORTING DIGITAL DATA</a>&nbsp; </b><a
href="#%5BBACK%20TO%20THE%20TOP%5D" style="text-decoration: none;">[BACK
TO THE TOP]</a></font></p>
<p style="margin-left: 10px;">
<img src="xmessage_faq_68.jpg" border="0" height="96" width="663"></p>
<p style="margin-left: 10px;">You will see this message if a failed
site's digital data has not reached your site after 30 minutes.&nbsp;
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.&nbsp; If you wish to continue to wait for the failed site's
grids, for up to 30 minutes, press YES.&nbsp; If you do not wish to
wait, press NO.&nbsp; Selecting NO will clean up the necessary lock
files and will return you to the Service Backup GUI.&nbsp; You will
still be in service backup mode.</p>
<p style="margin-left: 10px;">&nbsp;</p>
<p style="margin-left: 10px;">
<img src="xmessage_faq_12.jpg" border="0" height="96" width="607"></p>
<p style="margin-left: 10px;">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.&nbsp; If the
failed site's server fails to start or takes more than 6 minutes to
start, you will see this message.&nbsp; For more information, see
/data/logs/adapt/ifps/&lt;date&gt;/SVCBU_import_config_&lt;time&gt; and
/data/logs/adapt/ifps/&lt;date&gt;/svcbu_doall_&lt;time&gt; on the
machine that you started the import from.</p>
<p style="margin-left: 10px;">&nbsp;</p>
<p style="margin-left: 10px;">
<img src="xmessage_faq_13.jpg" border="0" height="96" width="301"></p>
<p style="margin-left: 10px;">You will see this message if there was a
problem importing a failed site's digital data.&nbsp; For more
information, see
/data/logs/adapt/ifps/&lt;date&gt;/svcbu_reqGrd_&lt;time&gt; on the
machine you ran the import from.</p>
<p style="margin-left: 10px;">&nbsp;</p>
<p style="margin-left: 10px;">
<img src="xmessage_faq_14.jpg" border="0" height="118" width="319"></p>
<p style="margin-left: 10px;">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.&nbsp; Import the failed site's configuration
before importing their digital data.</p>
<p style="margin-left: 10px;">&nbsp;</p>
<p style="margin-left: 10px;">
<img src="xmessage_faq_15.jpg" border="0" height="118" width="331"></p>
<p style="margin-left: 10px;">You will see this error message when
trying to import a failed site's digital data while importing their
configuration.&nbsp; Wait until the configuration import is complete
before importing a failed site's digital data.</p>
<p style="margin-left: 10px;">&nbsp;</p>
<p style="margin-left: 10px;">
<img src="xmessage_faq_16.jpg" border="0" height="118" width="322"></p>
<p style="margin-left: 10px;">You will see this error message when
trying to import a failed site's digital data while an import is
already running.&nbsp; Wait until the first set of grids has finished
importing before importing again.</p>
<p style="margin-left: 10px;">&nbsp;</p>
<p style="margin-left: 10px;">
<img src="xmessage_faq_17.jpg" border="0" height="118" width="293"></p>
<p style="margin-left: 10px;">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.&nbsp; Please wait until the failed site's
server is running to import digital data. </p>
<p style="margin-left: 10px;">&nbsp;</p>
<p style="margin-left: 10px;">
<img src="xmessage_faq_41.jpg" border="0" height="118" width="429"></p>
<p style="margin-left: 10px;">You will see this error message when
trying to import a failed site's digital data while exporting your
configuration to the central server.&nbsp; You must wait until the
export is finished before you can begin to import digital data for a
failed site.</p>
<p style="margin-left: 10px;">&nbsp;</p>
<p style="margin-left: 10px;">
<img src="xmessage_faq_42.jpg" border="0" height="118" width="360"></p>
<p style="margin-left: 10px;">You will see this error message when
trying to import a failed site's digital data while exporting your
grids to the central server.&nbsp; You must wait until the export is
finished before you can begin to import digital data for a failed site.</p>
<p style="margin-left: 10px;">&nbsp;</p>
<p style="margin-left: 10px;">
<img src="xmessage_faq_43.jpg" border="0" height="118" width="259"></p>
<p style="margin-left: 10px;">You will see this error message when
trying to import a failed site's digital data while exporting grids
back to the failed site.&nbsp; If you wish to re-import the failed
site's digital data, you must wait until the export has finished. </p>
<p style="margin-left: 10px;">&nbsp;</p>
<p style="margin-left: 10px;">
<img src="xmessage_faq_51.jpg" border="0" height="118" width="374"></p>
<p style="margin-left: 10px;">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.&nbsp; If you wish to re-import the
failed site's digital data, you must wait until the export is finished.</p>
<p style="margin-left: 10px;">&nbsp;</p>
<p style="margin-left: 10px;">
<img src="xmessage_faq_20.jpg" border="0" height="140" width="405"></p>
<p style="margin-left: 10px;">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.&nbsp; If this
is the case, you will not be able to import the failed site's digital
data.&nbsp; You should clean up the failed site's configuration and
import it again.&nbsp; For more information, see
/data/logs/adapt/ifps/&lt;date&gt;/svcbu_&lt;time&gt;.</p>
<p style="margin-left: 10px;">&nbsp;</p>
<p style="margin-left: 10px;">&nbsp;</p>
<p style="margin-left: 10px;"><font size="4"><b><a name="STARTING_GFE">STARTING
GFE</a>&nbsp; </b>
<a href="#%5BBACK%20TO%20THE%20TOP%5D" style="text-decoration: none;">[BACK
TO THE TOP]</a></font></p>
<p style="margin-left: 10px;">&nbsp;</p>
<p style="margin-left: 10px;">
<img src="xmessage_faq_18.jpg" border="0" height="96" width="279"></p>
<p style="margin-left: 10px;">You will see this message if there was a
problem starting GFE for a failed site.&nbsp; For more information, see
/data/logs/adapt/ifps/&lt;date&gt;/svcbuGFE_&lt;time&gt; on the machine
that you tried to start GFE from.</p>
<p style="margin-left: 10px;">&nbsp;</p>
<p style="margin-left: 10px;">
<img src="xmessage_faq_19.jpg" border="0" height="96" width="473"></p>
<p style="margin-left: 10px;">When trying to start GFE for any domain,
the Service Backup GUI must first source that domain's environment
file.&nbsp; 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.&nbsp; For more information, see
/data/logs/adapt/ifps/&lt;date&gt;/svcbu_doall_&lt;time&gt;. </p>
<p style="margin-left: 10px;">&nbsp;</p>
<p style="margin-left: 10px;">&nbsp;</p>
<p style="margin-left: 10px;"><font size="4">
<b><a name="EXPORTING_DIGITAL_DATA_BACK_TO_A_FAILED_SITE">EXPORTING
DIGITAL DATA BACK TO A FAILED SITE</a>&nbsp; </b><a
href="#%5BBACK%20TO%20THE%20TOP%5D" style="text-decoration: none;">[BACK
TO THE TOP]</a></font></p>
<p style="margin-left: 10px;">&nbsp;</p>
<p style="margin-left: 10px;">
<img src="xmessage_faq_21.jpg" border="0" height="140" width="405"></p>
<p style="margin-left: 10px;">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.&nbsp; If this is the case, you will not be able
to export the grids to a failed site.&nbsp; Ensure that you are in
service backup mode and that the failed site's environment file is
present.&nbsp; For more information, see
/data/logs/adapt/ifps/&lt;date&gt;/svcbu_&lt;time&gt;.</p>
<p style="margin-left: 10px;">&nbsp;</p>
<p style="margin-left: 10px;">
<img src="xmessage_faq_22.jpg" border="0" height="96" width="363"></p>
<p style="margin-left: 10px;">You will see this message if there was an
error exporting the digital data back to a failed site.&nbsp; For more
information, see
/data/logs/adapt/ifps/&lt;date&gt;/svcbu_expbksiteGrd_&lt;time&gt; on
the machine that you ran the export from.</p>
<p style="margin-left: 10px;">&nbsp;</p>
<p style="margin-left: 10px;">
<img src="xmessage_faq_23.jpg" border="0" height="118" width="319"></p>
<p style="margin-left: 10px;">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.&nbsp; You must be in Service Backup Mode to export
digital data back to a failed site.</p>
<p style="margin-left: 10px;">&nbsp;</p>
<p style="margin-left: 10px;">
<img src="xmessage_faq_24.jpg" border="0" height="118" width="331"></p>
<p style="margin-left: 10px;">You will see this error message when
attempting to export grids back to a failed site while you are
importing their configuration.&nbsp; Wait until the import is finished
before exporting the digital data back to the failed site.</p>
<p style="margin-left: 10px;">&nbsp;</p>
<p style="margin-left: 10px;">
<img src="xmessage_faq_25.jpg" border="0" height="118" width="293"></p>
<p style="margin-left: 10px;">You will see this error message when
attempting to export grids back to a failed site while their server is
trying to start.&nbsp; Wait until the server is started before
exporting the digital data back to the failed site.</p>
<p style="margin-left: 10px;">&nbsp;</p>
<p style="margin-left: 10px;">
<img src="xmessage_faq_26.jpg" border="0" height="118" width="264"></p>
<p style="margin-left: 10px;">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.&nbsp; Wait until the import is
finished before exporting the digital data back to the failed site.</p>
<p style="margin-left: 10px;">
<img src="xmessage_faq_44.jpg" border="0" height="118" width="429"></p>
<p style="margin-left: 10px;">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.&nbsp; You must wait until the export is finished before you can
begin exporting grids back to a failed site.</p>
<p style="margin-left: 10px;">&nbsp;</p>
<p style="margin-left: 10px;">
<img src="xmessage_faq_45.jpg" border="0" height="118" width="360"></p>
<p style="margin-left: 10px;">You will see this error message when
attempting to export grids back to a failed site while exporting your
grids to the central server.&nbsp; You must wait until the export is
finished before you can begin exporting grids back to a failed site.</p>
<p style="margin-left: 10px;">&nbsp;</p>
<p style="margin-left: 10px;">
<img src="xmessage_faq_46.jpg" border="0" height="118" width="259"></p>
<p style="margin-left: 10px;">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.&nbsp; If you wish to re-export the
digital data back to the failed site, you must wait for the first
export to finish.</p>
<p style="margin-left: 10px;">&nbsp;</p>
<p style="margin-left: 10px;">
<img src="xmessage_faq_52.jpg" border="0" height="118" width="374"></p>
<p style="margin-left: 10px;">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.&nbsp; If you wish to
export the failed site's grids back to them, you must wait for the
first export to finish.</p>
<p style="margin-left: 10px;">&nbsp;</p>
<p style="margin-left: 10px;"><font size="4">
<b><a name="EXPORTING_A_FAILED_SITES_DIGITAL_DATA_TO_THE_CENTRAL_SERVER">EXPORTING
A FAILED SITE'S DIGITAL DATA TO THE CENTRAL SERVER</a>&nbsp; </b>
<a href="#%5BBACK%20TO%20THE%20TOP%5D" style="text-decoration: none;">[BACK
TO THE TOP]</a></font></p>
<p style="margin-left: 10px;">&nbsp;</p>
<p style="margin-left: 10px;">
<img src="xmessage_faq_62.jpg" border="0" height="96" width="511"></p>
<p style="margin-left: 10px;">You will see this message if there was a
problem exporting a failed site's digital data to the central
server.&nbsp; For more information, see
/data/logs/adapt/ifps/&lt;date&gt;/svcbu_exprtbksiteGrdToCS_&lt;time&gt;
on the machine you ran the export from.</p>
<p style="margin-left: 10px;">&nbsp;</p>
<p style="margin-left: 10px;">
<img src="xmessage_faq_63.jpg" border="0" height="140" width="417"></p>
<p style="margin-left: 10px;">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.&nbsp; Make sure that you are in service backup mode and that
/awips/adapt/ifps/localbin/&lt;failed site&gt;/ifps-&lt;failed
site&gt;.env is present.</p>
<p style="margin-left: 10px;">&nbsp;</p>
<p style="margin-left: 10px;">
<img src="xmessage_faq_53.jpg" border="0" height="118" width="405"></p>
<p style="margin-left: 10px;">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.&nbsp; If you wish to export a
failed site's grids to the central server, you must first import the
failed site's configuration.</p>
<p style="margin-left: 10px;">&nbsp;</p>
<p style="margin-left: 10px;">
<img src="xmessage_faq_54.jpg" border="0" height="118" width="405"></p>
<p style="margin-left: 10px;">You will see this error message if you
try to export a failed site's digital data to the central server&nbsp;
while importing their configuration.&nbsp; You must first let the
import finish before you can begin exporting to the central server.</p>
<p style="margin-left: 10px;">&nbsp;</p>
<p style="margin-left: 10px;">
<img src="xmessage_faq_55.jpg" border="0" height="118" width="405"></p>
<p style="margin-left: 10px;">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.&nbsp; If you wish to export the failed
site's digital data to the central server, you must let the import
finish first.</p>
<p style="margin-left: 10px;">&nbsp;</p>
<p style="margin-left: 10px;">
<img src="xmessage_faq_56.jpg" border="0" height="118" width="400"></p>
<p style="margin-left: 10px;">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.&nbsp; Verify that the failed site's
server is running before exporting their grids to the central server.</p>
<p style="margin-left: 10px;">&nbsp;</p>
<p style="margin-left: 10px;">
<img src="xmessage_faq_57.jpg" border="0" height="118" width="429"></p>
<p style="margin-left: 10px;">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.&nbsp; You must wait
for the first export to finish before you can export a failed site's
digital data to the central server.</p>
<p style="margin-left: 10px;">&nbsp;</p>
<p style="margin-left: 10px;">
<img src="xmessage_faq_58.jpg" border="0" height="118" width="400"></p>
<p style="margin-left: 10px;">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.&nbsp; You must wait
for your export to finish before you can export the failed site's grids
to the central server.</p>
<p style="margin-left: 10px;">&nbsp;</p>
<p style="margin-left: 10px;">
<img src="xmessage_faq_59.jpg" border="0" height="118" width="400"></p>
<p style="margin-left: 10px;">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.&nbsp; You must first
finish exporting the grids to the failed site before you can send them
to the central server.</p>
<p style="margin-left: 10px;">&nbsp;</p>
<p style="margin-left: 10px;">
<img src="xmessage_faq_60.jpg" border="0" height="118" width="437"></p>
<p style="margin-left: 10px;">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.&nbsp; If you wish to re-export
the failed site's digital data, you must let the first export process
finish. </p>
<p style="margin-left: 10px;">&nbsp;</p>
<p style="margin-left: 10px;"><font size="4">
<b><a name="EXPORTING_CONFIGURATION_TO_THE_CENTRAL_SERVER">EXPORTING
CONFIGURATION TO THE CENTRAL SERVER</a>&nbsp; </b><a
href="#%5BBACK%20TO%20THE%20TOP%5D" style="text-decoration: none;">[BACK
TO THE TOP]</a></font></p>
<p style="margin-left: 10px;">&nbsp;</p>
<p style="margin-left: 10px;">
<img src="xmessage_faq_27.jpg" border="0" height="96" width="396"></p>
<p style="margin-left: 10px;">You will see this message if there was a
problem exporting your configuration to the central server.&nbsp; For
more information, see
/data/logs/adapt/ifps/&lt;date&gt;/svcbu_&lt;time&gt; on the machine
that you ran the export from.</p>
<p style="margin-left: 10px;">&nbsp;</p>
<p style="margin-left: 10px;">
<img src="xmessage_faq_28.jpg" border="0" height="118" width="418"></p>
<p style="margin-left: 10px;">You will see this error message if you
try to export your configuration to the central server while you are in
Service Backup Mode.&nbsp; You must exit Service Backup Mode before you
can export your configuration.</p>
<p style="margin-left: 10px;">&nbsp;</p>
<p style="margin-left: 10px;">
<img src="xmessage_faq_47.jpg" border="0" height="118" width="554"></p>
<p style="margin-left: 10px;">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.</p>
<p style="margin-left: 10px;">&nbsp;</p>
<p style="margin-left: 10px;"><font size="4">
<b><a name="EXPORTING_YOUR_DIGITAL_DATA_TO_THE_CENTRAL_SERVER">EXPORTING
YOUR DIGITAL DATA TO THE CENTRAL SERVER</a>&nbsp; </b><a
href="#%5BBACK%20TO%20THE%20TOP%5D" style="text-decoration: none;">[BACK
TO THE TOP]</a></font></p>
<p style="margin-left: 10px;">&nbsp;</p>
<p style="margin-left: 10px;">
<img src="xmessage_faq_29.jpg" border="0" height="96" width="308"></p>
<p style="margin-left: 10px;">You will see this message if there was a
problem exporting your digital data to the central server.&nbsp; For
more information, see
/data/logs/adapt/ifps/&lt;date&gt;/svcbu_expGrd_&lt;time&gt; on the
machine that you ran the export from.</p>
<p style="margin-left: 10px;">&nbsp;</p>
<p style="margin-left: 10px;">
<img src="xmessage_faq_66.jpg" border="0" height="140" width="337"></p>
<p style="margin-left: 10px;">You will see this message if you try to
export your grids to the central server while an export is already
running.&nbsp; If you wish to re-export your grids to the central
server, you must wait for the first export to finish.</p>
<p style="margin-left: 10px;">&nbsp;</p>
<p style="margin-left: 10px;">
<img src="xmessage_faq_65.jpg" border="0" height="140" width="351"></p>
<p style="margin-left: 10px;">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.&nbsp; You must wait
for the first export to finish before you can export your grids.</p>
<p style="margin-left: 10px;">&nbsp;</p>
<p style="margin-left: 10px;"><font size="4">
<b><a name="EXITING_SERVICE_BACKUP">EXITING SERVICE BACKUP</a>&nbsp; </b>
<a href="#%5BBACK%20TO%20THE%20TOP%5D" style="text-decoration: none;">[BACK
TO THE TOP]</a></font></p>
<p style="margin-left: 10px;">&nbsp;</p>
<p style="margin-left: 10px;">
<img src="xmessage_faq_30.jpg" border="0" height="96" width="502"></p>
<p style="margin-left: 10px;">You will see this error message if you
try to exit service backup while you are not in Service Backup
Mode.&nbsp; You must be in Service Backup Mode to use the Exit
button.&nbsp; If you wish to run the cleanup script, use the "CLEAN UP
SERVICE BACKUP" button.</p>
<p style="margin-left: 10px;">&nbsp;</p>
<p style="margin-left: 10px;">
<img src="xmessage_faq_31.jpg" border="0" height="118" width="331"></p>
<p style="margin-left: 10px;">You will see this error message if you
try to exit service backup while importing a failed site's
configuration.&nbsp; Wait until the import is complete before exiting
service backup.</p>
<p style="margin-left: 10px;">&nbsp;</p>
<p style="margin-left: 10px;">
<img src="xmessage_faq_32.jpg" border="0" height="118" width="264"></p>
<p style="margin-left: 10px;">You will see this error message if you
try to exit service backup while importing a failed site's digital
data.&nbsp; Wait until the import is complete before exiting service
backup.</p>
<p style="margin-left: 10px;">&nbsp;</p>
<p style="margin-left: 10px;">
<img src="xmessage_faq_33.jpg" border="0" height="118" width="293"></p>
<p style="margin-left: 10px;">You will see this error message if you
try to exit service backup while waiting for a failed site's server to
start.&nbsp; Wait until the server is started before exiting service
backup.</p>
<p style="margin-left: 10px;">&nbsp;</p>
<p style="margin-left: 10px;">
<img src="xmessage_faq_48.jpg" border="0" height="118" width="259"></p>
<p style="margin-left: 10px;">You will see this error message when
trying to exit service backup while exporting grids back to a failed
site.&nbsp; You must wait until the export is finished before you can
exit service backup.</p>
<p style="margin-left: 10px;">&nbsp;</p>
<p style="margin-left: 10px;"><font size="4">
<b><a name="CLEANING_UP_SERVICE_BACKUP">CLEANING UP SERVICE BACKUP</a>&nbsp;
</b><a href="#%5BBACK%20TO%20THE%20TOP%5D"
style="text-decoration: none;">[BACK TO THE TOP]</a></font></p>
<p style="margin-left: 10px;">&nbsp;</p>
<p style="margin-left: 10px;">
<img src="xmessage_faq_34.jpg" border="0" height="96" width="380"></p>
<p style="margin-left: 10px;">You will see this message if you attempt
to clean up your own site's configuration files.&nbsp; If your site has
multiple domains, you will not be allowed to clean up either domain's
configuration.</p>
<p style="margin-left: 10px;">&nbsp;</p>
<p style="margin-left: 10px;">
<img src="xmessage_faq_35.jpg" border="0" height="96" width="279"></p>
<p style="margin-left: 10px;">You will see this message if there was a
problem running the cleanup script.&nbsp; For more information, see
/data/logs/adapt/ifps/&lt;date&gt;/svcbu_cleanup_&lt;time&gt; on dx4f.</p>
<p style="margin-left: 10px;">&nbsp;</p>
<p style="margin-left: 10px;">
<img src="xmessage_faq_36.jpg" border="0" height="118" width="293"></p>
<p style="margin-left: 10px;">You will see this message if you try to
run the cleanup script while the failed site's server is trying to
start.&nbsp; Wait until the server is started before you run the
cleanup script.</p>
<p style="margin-left: 10px;">&nbsp;</p>
<p style="margin-left: 10px;">
<img src="xmessage_faq_37.jpg" border="0" height="118" width="264"></p>
<p style="margin-left: 10px;">You will see this message if you try to
run the cleanup script while importing a failed site's
configuration.&nbsp; Wait until the import is complete before you run
the cleanup script.</p>
<p style="margin-left: 10px;">&nbsp;</p>
<p style="margin-left: 10px;">
<img src="xmessage_faq_49.jpg" border="0" height="118" width="259"></p>
<p style="margin-left: 10px;">You will see this message if you try to
run the clean up script while exporting grids back to a failed
site.&nbsp; You must wait until the export is finished before you can
clean up service backup. </p>
<p style="margin-left: 10px;">&nbsp;</p>
<p style="margin-left: 10px;">
<img src="xmessage_faq_64.jpg" border="0" height="118" width="374"></p>
<p style="margin-left: 10px;">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.</p>
</body>
</html>

464
cave/com.raytheon.viz.gfe/help/GfeServiceBackup/svcbu_help.html
View file

@ -1,464 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Language" content="en-us">
<meta name="GENERATOR" content="Microsoft FrontPage 6.0">
<meta name="ProgId" content="FrontPage.Editor.Document">
<meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
<title>IFPS SERVICE BACKUP GUI</title>
</head>
<body>
<TABLE BORDER="0" WIDTH="100%" id="table1">
<TR VALIGN="TOP">
<TD ALIGN="CENTER" VALIGN="TOP">
<H1><A NAME="#SERVICE BACKUP GUI HELP PAGE"><FONT COLOR="#0000FF"><I>Service Backup GUI</I>
</FONT></H1>
<H2><FONT COLOR="BLACK"><I>HELP</I></FONT></H2></TD>
</TR>
</TABLE><BR>
<HR SIZE=5 NOSHADE>
<table border="0" cellpadding="0" cellspacing="0" style="border-collapse: collapse; " bordercolor="#ffffff" width="100%" id="AutoNumber1" bordercolorlight="#FFFFFF" bordercolordark="#FFFFFF">
<tbody>
<tr>
<td width="50%">
<p align="Left"><a href="#BUTTONS"><font size="4" color="#000000">BUTTONS</font></a>
</p>
<a style="text-decoration: none">GHG SERVICE BACKUP</span></a>
<br>
<a style="text-decoration: none; " href="#IMPORT CONFIGURATION DATA">IMPORT CONFIGURATION DATA</a>
<br>
<a style="text-decoration: none; " href="#IMPORT FAILED SITES DIGITAL DATA">IMPORT FAILED SITES DIGITAL DATA</a>
<br>
<a style="text-decoration: none; " href="#EXPORT GRIDS TO FAILED SITE">EXPORT GRIDS TO FAILED SITE</a>
<br>
<a style="text-decoration: none; " href="#EXPORT CCCS CONFIGURATION TO THE CENTRAL SERVER">EXPORT CCC'S CONFIGURATION TO THE CENTRAL SERVER</a>
<br>
<a style="text-decoration: none; " href="#EXPORT CCCS DIGITAL FORECAST TO THE CENTRAL SERVER">EXPORT CCC'S DIGITAL FORECAST TO THE CENTRAL SERVER</a>
<br>
<a style="text-decoration: none; " href="#EXPORT_A_FAILED_SITES_DIGITAL_DATA_TO_THE_CENTRAL_SERVER">EXPORT A FAILED SITE'S DIGITAL DATA TO THE CENTRAL SERVER</a>
<br>
<a style="text-decoration: none; " href="#START GFE">START
GFE</a>
<br>
<a style="text-decoration: none; " href="#EXIT SERVICE BACKUP">EXIT SERVICE BACKUP</a>
<br>
<a style="text-decoration: none; " href="#CLEAN UP SERVICE BACKUP">CLEAN UP SERVICE BACKUP</a>
<br>
<a style="text-decoration: none; " href="#OK">OK</a>
<br>
<a style="text-decoration: none; " href="#REFRESH">REFRESH</a>
</td>
<td width="50%">
<p align="Left"><a href="#BANNERS"><font size="4" color="#000000">BANNERS</font></a>
</p>
<a style="text-decoration: none; " href="#YOU ARE NOT IN BACKUP MODE">YOU ARE NOT IN BACKUP MODE</a>
<br>
<a style="text-decoration: none; " href="#YOU ARE CURRENTLY IMPORTING A FAILED SITES CONFIGURATION">YOU ARE CURRENTLY IMPORTING A FAILED SITES CONFIGURATION</a>
<br>
<a style="text-decoration: none; " href="#WAITING FOR A FAILED SITES SERVER TO START">WAITING FOR A FAILED SITES SERVER TO START</a>
<br>
<a style="text-decoration: none; " href="#YOU ARE CURRENTLY IMPORTING A FAILED SITES DIGITAL DATA">YOU ARE CURRENTLY IMPORTING A FAILED SITES DIGITAL DATA</a>
<br>
<a style="text-decoration: none; " href="#YOU ARE CURRENTLY BACKING UP XXX">YOU ARE CURRENTLY BACKING UP XXX</a>
<br>
<a style="text-decoration: none; " href="#EXPORTING_GRIDS_BACK_TO_XXX">EXPORTING GRIDS BACK TO XXX</a>
<br>
<a style="text-decoration: none; " href="#YOU_ARE_CURRENTLY_EXPORTING_YOUR_CONFIGURATION_TO_THE_CENTRAL_SERVER">YOU ARE CURRENTLY EXPORTING YOUR CONFIGURATION TO THE CENTRAL SERVER</a>
<br>
<a style="text-decoration: none; " href="#YOU_ARE_CURRENTLY_EXPORTING_YOUR_GRIDS_TO_THE_CENTRAL_SERVER">YOU ARE CURRENTLY EXPORTING YOUR GRIDS TO THE CENTRAL SERVER</a>
<br>
<a style="text-decoration: none; " href="#YOU_ARE_CURRENTLY_EXPORTING_XXXS_GRIDS_TO_THE_CENTRAL_SERVER">YOU ARE CURRENTLY EXPORTING XXX'S GRIDS TO THE CENTRAL SERVER</a>
</td>
</tr>
</tbody>
</table>
<hr>
<p align="Left"><font size="4"><b><u><a name="BUTTONS">BUTTONS</a></u> </b>
<a name="BUTTONS" style="text-decoration: none; " href="##SERVICE BACKUP GUI HELP PAGE">[BACK TO THE TOP]</a>
</font></p>
<p align="Left"><b><a name="EMERGENCY_GFE_(GHG_ONLY)">GHG SERVICE BACKUP</a>
</b><a style="text-decoration: none; " href="##SERVICE BACKUP GUI HELP PAGE">
[BACK TO THE TOP]</a>
</p>
<p align="Left" style="margin-left: 10px; ">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. <b>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.</b></p>
<p align="Left"><b><a name="IMPORT CONFIGURATION DATA">IMPORT CONFIGURATION
DATA</a>
</b><a style="text-decoration: none; " href="##SERVICE BACKUP GUI HELP PAGE">[BACK TO THE TOP]</a>
</p>
<p align="Left" style="margin-left: 10px; ">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. </p>
<p align="Left" style="margin-left: 10px; ">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. </p>
<p align="Left"><b><a name="IMPORT FAILED SITES DIGITAL DATA">IMPORT FAILED
SITE'S DIGITAL DATA</a>
</b><a style="text-decoration: none; " href="##SERVICE BACKUP GUI HELP PAGE">[BACK TO THE TOP]</a>
</p>
<p align="Left" style="margin-left: 10px; ">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.</p>
<p align="Left" style="margin-left: 10px; ">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.</p>
<p align="Left"><b><a name="EXPORT GRIDS TO FAILED SITE">EXPORT GRIDS TO
FAILED SITE</a>
</b><a style="text-decoration: none; " href="##SERVICE BACKUP GUI HELP PAGE">[BACK TO THE TOP]</a>
</p>
<p align="Left" style="margin-left: 10px; ">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).</p>
<p align="Left" style="margin-left: 10px; ">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.</p>
<p align="Left"><b><a name="EXPORT CCCS CONFIGURATION TO THE CENTRAL SERVER">
EXPORT CCC'S CONFIGURATION TO THE CENTRAL SERVER</a>
</b><a style="text-decoration: none; " href="##SERVICE BACKUP GUI HELP PAGE">[BACK TO THE TOP]</a>
</p>
<p align="Left" style="margin-left: 10px; ">This button will allow you to
export your own configuration (CCC's in this example) to the central server
for service backup.</p>
<p align="Left" style="margin-left: 10px; ">This button will only be enabled
when you start the GUI as user ifps and are not in service backup mode.&nbsp;
If you start the Service Backup GUI as any other user, the button label will
read &quot;Must Be User IFPS to Export CCC's Configuration&quot;. </p>
<p align="Left"><b><a name="EXPORT CCCS DIGITAL FORECAST TO THE CENTRAL SERVER">
EXPORT CCC'S DIGITAL FORECAST TO THE CENTRAL SERVER</a>
</b><a style="text-decoration: none; " href="##SERVICE BACKUP GUI HELP PAGE">[BACK TO THE TOP]</a>
</p>
<p align="Left" style="margin-left: 10px; ">This button will allow you to
export your digital data (CCC's in this example) to the central server
for service backup.</p>
<p align="Left" style="margin-left: 10px; ">This button will be enabled whenever
you are not currently exporting your digital forecast to the central server.</p>
<p align="Left" style="margin-left: 0px; "><b><a name="EXPORT_A_FAILED_SITES_DIGITAL_DATA_TO_THE_CENTRAL_SERVER">
EXPORT A FAILED SITE'S DIGITAL DATA TO THE CENTRAL SERVER</a>
</b><a style="text-decoration: none; " href="##SERVICE BACKUP GUI HELP PAGE">[BACK TO THE TOP]</a>
</p>
<p align="Left" style="margin-left: 10px; ">This button will allow you to
export a failed site's digital data to the central server. (<b>NOTE:</b>
You still need to export the digital data back to the failed site.)</p>
<p align="Left" style="margin-left: 10px; ">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.</p>
<p align="Left"><b><a name="START GFE">START GFE</a>
</b><a style="text-decoration: none; " href="##SERVICE BACKUP GUI HELP PAGE">[BACK TO THE TOP]</a>
</p>
<p align="Left" style="margin-left: 10px; ">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.</p>
<p align="Left" style="margin-left: 10px; ">This button will be enabled at
all times.</p>
<p align="Left"><b><a name="EXIT SERVICE BACKUP">EXIT SERVICE BACKUP</a>
</b><a style="text-decoration: none; " href="##SERVICE BACKUP GUI HELP PAGE">[BACK TO THE TOP]</a>
</p>
<p align="Left" style="margin-left: 10px; ">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.</p>
<p align="Left" style="margin-left: 10px; ">This button will only be enabled
while you are in service backup mode. </p>
<p align="Left"><b><a name="CLEAN UP SERVICE BACKUP">CLEAN UP SERVICE BACKUP</a>
</b><a style="text-decoration: none; " href="##SERVICE BACKUP GUI HELP PAGE">[BACK TO THE TOP]</a>
</p>
<p align="Left" style="margin-left: 10px; ">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.</p>
<p align="Left" style="margin-left: 10px; ">This button will be disabled
while you are importing a failed site's digital data.</p>
<p align="Left"><b><a name="OK">OK</a>
</b><a style="text-decoration: none; " href="##SERVICE BACKUP GUI HELP PAGE">[BACK TO THE TOP]</a>
</p>
<p align="Left" style="margin-left: 10px; ">This button perform the selected
action. It will stay depressed until the selected action is finished.</p>
<p><b><a name="REFRESH">REFRESH</a>
</b><a style="text-decoration: none; " href="##SERVICE BACKUP GUI HELP PAGE">[BACK TO THE TOP]</a>
</p>
<p style="margin-left: 10px; ">This button will refresh the banner message
(if necessary) and will enable/disable the necessary buttons. It will
also unselect any button.</p>
<p align="Left"><font size="4"><b><u><a name="BANNERS">BANNERS</a></u> </b>
<a style="text-decoration: none; " href="##SERVICE BACKUP GUI HELP PAGE">[BACK TO THE TOP]</a>
</font></p>
<p align="Left"><b><a name="YOU ARE NOT IN BACKUP MODE">YOU ARE NOT IN BACKUP
MODE</a>
</b><a style="text-decoration: none; " href="##SERVICE BACKUP GUI HELP PAGE">[BACK TO THE TOP]</a>
</p>
<p align="Center"><img border="0" src="banner_no_backup.gif" width="541" height="798">
</p>
<p align="Left" style="margin-left: 10px; ">This banner will appear if you
are not in service backup mode. At this time, only the following buttons
will be enabled:</p>
<p align="Left" style="margin-left: 20px; "><font size="2">EMERGENCY GFE
(GHG ONLY)</font></p>
<p align="Left" style="margin-left: 20px; "><font size="2">IMPORT CONFIGURATION
DATA</font></p>
<p align="Left" style="margin-left: 20px; "><font size="2">EXPORT CCC'S CONFIGURATION
TO THE CENTRAL SERVER (if the GUI is started as user ifps)</font></p>
<p align="Left" style="margin-left: 20px; "><font size="2">EXPORT CCC'S DIGITAL
FORECAST TO THE CENTRAL SERVER</font></p>
<p align="Left" style="margin-left: 20px; "><font size="2">START GFE</font></p>
<p align="Left" style="margin-left: 20px; "><font size="2">CLEAN UP SERVICE
BACKUP</font></p>
<p align="Left"><b><a name="YOU ARE CURRENTLY IMPORTING A FAILED SITES CONFIGURATION">
YOU ARE CURRENTLY IMPORTING A FAILED SITE'S CONFIGURATION</a>
</b><a style="text-decoration: none; " href="##SERVICE BACKUP GUI HELP PAGE">[BACK TO THE TOP]</a>
</p>
<p align="Center"><img border="0" src="banner_imprtMode.gif" width="541" height="834">
</p>
<p align="Left" style="margin-left: 10px; ">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:</p>
<p align="Left" style="margin-left: 20px; "><font size="2">EXPORT CCC'S DIGITAL
FORECAST TO THE CENTRAL SERVER</font></p>
<p align="Left" style="margin-left: 20px; "><font size="2">START GFE</font></p>
<p align="Left" style="margin-left: 20px; "><font size="2">CLEAN UP SERVICE
BACKUP</font></p>
<p align="Left"><b><a name="WAITING FOR A FAILED SITES SERVER TO START">WAITING
FOR A FAILED SITE'S SERVER TO START</a>
</b><a style="text-decoration: none; " href="##SERVICE BACKUP GUI HELP PAGE">[BACK TO THE TOP]</a>
</p>
<p align="Center"><img border="0" src="banner_waitMode.gif" width="541" height="834">
</p>
<p align="Left" style="margin-left: 10px; ">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:</p>
<p align="Left" style="margin-left: 20px; "><font size="2">EXPORT CCC'S DIGITAL
FORECAST TO THE CENTRAL SERVER</font></p>
<p align="Left" style="margin-left: 20px; "><font size="2">START GFE</font></p>
<p align="Left"><b><a name="YOU ARE CURRENTLY IMPORTING A FAILED SITES DIGITAL DATA">
YOU ARE CURRENTLY IMPORTING A FAILED SITE'S DIGITAL DATA</a>
</b><a style="text-decoration: none; " href="##SERVICE BACKUP GUI HELP PAGE">[BACK TO THE TOP]</a>
</p>
<p align="Center"><img border="0" src="banner_imprtGrdMode.gif" width="520" height="834">
</p>
<p align="Left" style="margin-left: 10px; ">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:</p>
<p align="Left" style="margin-left: 20px; "><font size="2">EXPORT CCC'S DIGITAL
FORECAST TO THE CENTRAL SERVER</font></p>
<p align="Left" style="margin-left: 20px; "><font size="2">START GFE</font></p>
<p align="Left"><b><a name="YOU ARE CURRENTLY BACKING UP XXX">YOU ARE CURRENTLY
BACKING UP XXX</a>
</b><a style="text-decoration: none; " href="##SERVICE BACKUP GUI HELP PAGE">[BACK TO THE TOP]</a>
</p>
<p align="Center"><img border="0" src="banner_svcbuMode.gif" width="520" height="834">
</p>
<p align="Left" style="margin-left: 10px; ">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:</p>
<p align="Left" style="margin-left: 20px; "><font size="2">IMPORT CONFIGURATION
DATA</font></p>
<p align="Left" style="margin-left: 20px; "><font size="2">IMPORT XXX'S DIGITAL
DATA</font></p>
<p align="Left" style="margin-left: 20px; "><font size="2">EXPORT GRIDS TO
XXX</font></p>
<p align="Left" style="margin-left: 20px; "><font size="2">EXPORT CCC'S DIGITAL
FORECAST TO THE CENTRAL SERVER</font></p>
<p align="Left" style="margin-left: 20px; "><font size="2"> START GFE</font></p>
<p align="Left" style="margin-left: 20px; "><font size="2">EXIT SERVICE BACKUP
FOR XXX</font></p>
<p align="Left" style="margin-left: 20px; "><font size="2">CLEAN UP SERVICE
BACKUP</font></p>
<p align="Left"><b><a name="EXPORTING_GRIDS_BACK_TO_XXX">EXPORTING GRIDS
BACK TO XXX</a>
</b><a style="text-decoration: none; " href="##SERVICE BACKUP GUI HELP PAGE">[BACK TO THE TOP]</a>
</p>
<p align="Center" style="margin-left: 20px; "><img border="0" src="banner_exprtbksiteGrdMode.gif" width="520" height="806">
</p>
This message will appear while you are exporting a failed site's grids
back to them. At this time, the following buttons will be enabled:
<p align="Left" style="margin-left: 20px; "><font size="2"> EXPORT CCC'S
DIGITAL FORECAST TO THE CENTRAL SERVER</font></p>
<p align="Left" style="margin-left: 20px; "><font size="2"> START GFE</font></p>
<p align="Left"><b><a name="YOU_ARE_CURRENTLY_EXPORTING_YOUR_CONFIGURATION_TO_THE_CENTRAL_SERVER">
YOU ARE CURRENTLY EXPORTING YOUR CONFIGURATION TO THE CENTRAL SERVER</a>
</b><a style="text-decoration: none; " href="##SERVICE BACKUP GUI HELP PAGE">[BACK TO THE TOP]</a>
</p>
<p align="Center" style="margin-left: 20px; "><img border="0" src="banner_exprtMode.gif" width="617" height="834">
</p>
This message will appear when you are exporting your configuration to
the central server for service backup. At this time, the following buttons
will be enabled:
<p align="Left" style="margin-left: 20px; "><font size="2"> EXPORT CCC'S
DIGITAL FORECAST TO THE CENTRAL SERVER</font></p>
<p align="Left" style="margin-left: 20px; "><font size="2"> START GFE</font></p>
<p align="Left" style="margin-left: 20px; "><font size="2">CLEAN UP SERVICE
BACKUP</font></p>
<p align="Left"><b><a name="YOU_ARE_CURRENTLY_EXPORTING_YOUR_GRIDS_TO_THE_CENTRAL_SERVER">
YOU ARE CURRENTLY EXPORTING YOUR GRIDS TO THE CENTRAL SERVER</a>
</b><a style="text-decoration: none; " href="##SERVICE BACKUP GUI HELP PAGE">[BACK TO THE TOP]</a>
</p>
<p align="Center" style="margin-left: 20px; "><img border="0" src="banner_exprtGrdMode.gif" width="576" height="834">
</p>
This message will appear when you are exporting your grids to the central
server for service backup. If you are not in service backup mode, the following
buttons will be enabled:
<p align="Left" style="margin-left: 20px; "><font size="2"> IMPORT CONFIGURATION
DATA</font></p>
<p align="Left" style="margin-left: 20px; "><font size="2"> START GFE</font></p>
<p align="Left" style="margin-left: 20px; "><font size="2">CLEAN UP SERVICE
BACKUP</font></p>
<p align="Left" style="margin-left: 20px; ">If you are in service backup
mode, the following buttons will be enabled:</p>
<p align="Left" style="margin-left: 20px; "><font size="2"> IMPORT CONFIGURATION
DATA</font></p>
<p align="Left" style="margin-left: 20px; "><font size="2"> IMPORT CCC'S
DIGITAL DATA</font></p>
<p align="Left" style="margin-left: 20px; "><font size="2"> EXPORT GRIDS
TO CCC</font></p>
<p align="Left" style="margin-left: 20px; "><font size="2"> EXPORT CCC'S
DIGITAL DATA TO THE CENTRAL SERVER</font></p>
<p align="Left" style="margin-left: 20px; "><font size="2"> START GFE</font></p>
<p align="Left" style="margin-left: 20px; "><font size="2"> EXIT SERVICE
BACKUP FOR CCC</font></p>
<p align="Left" style="margin-left: 20px; "><font size="2"> CLEAN UP
SERVICE BACKUP</font></p>
<p align="Left"><b><a name="YOU_ARE_CURRENTLY_EXPORTING_XXXS_GRIDS_TO_THE_CENTRAL_SERVER">
YOU ARE CURRENTLY EXPORTING XXX'S GRIDS TO THE CENTRAL SERVER</a>
</b><a style="text-decoration: none; " href="##SERVICE BACKUP GUI HELP PAGE">[BACK TO THE TOP]</a>
</p>
<p align="Center"><img border="0" src="banner_exprtbksiteGrdToCSMode.gif" width="582" height="834">
</p>
<p align="Left"> 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:</p>
<p align="Left" style="margin-left: 10px; "><font size="2">EXPORT CCC'S DIGITAL
FORECAST TO THE CENTRAL SERVER</font></p>
<p align="Left" style="margin-left: 10px; "><font size="2">START GFE</font></p>
</body>
</html>

434
cave/com.raytheon.viz.gfe/help/GfeServiceBackup/svcbu_instructions.html
View file

@ -1,433 +1,11 @@
<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
<head>
<meta name="Author" content="John Wagner">
<title>Service Backup Instructions</title>
<meta name="Author" content="Ron Anderson">
<title>GFE Service Backup Instructions</title>
</head>
<body>
<TABLE BORDER="0" WIDTH="100%">
<TR VALIGN="TOP">
<TD ALIGN="CENTER" VALIGN="TOP">
<H1><A NAME="Top"><FONT COLOR="#0000FF"><I>Service Backup GUI</I>
</FONT></H1>
<H2><FONT COLOR="BLACK"><I>INSTRUCTIONS</I></FONT></H2></TD>
</TR>
</TABLE><BR>
<HR SIZE=5 NOSHADE>
<H3>&nbsp;&nbsp;&nbsp;Contents of this section</H3>
<p>
&nbsp;&nbsp;&nbsp;
<a href="#HOW_TO_START_GHG_SERVICE_BACKUP" style="text-decoration: none">HOW TO START GHG SERVICE BACKUP</a></p>
&nbsp;&nbsp;&nbsp;
<a href="#HOW TO IMPORT A FAILED SITES CONFIGURATION AND DIGITAL DATA AND START THEIR GFE IN ONE STEP" style="text-decoration: none">
HOW TO IMPORT A FAILED SITE'S CONFIGURATION AND DIGITAL DATA AND START
THEIR GFE IN
ONE STEP</a>
<p>
&nbsp;&nbsp;&nbsp;
<a href="#HOW TO IMPORT A FAILED SITES CONFIGURATION AND DIGITAL DATA IN ONE STEP" style="text-decoration: none">
HOW TO IMPORT&nbsp; A FAILED SITE'S CONFIGURATION AND DIGITAL DATA IN ONE STEP</a>
</p>
<p>
&nbsp;&nbsp;&nbsp;
<a href="#HOW TO IMPORT A FAILED SITES CONFIGURATION AND START THEIR GFE IN ONE STEP" style="text-decoration: none">
HOW TO IMPORT A FAILED SITE'S CONFIGURATION AND START THEIR GFE IN
ONE STEP</a> </p>
<p>
&nbsp;&nbsp;&nbsp;
<a href="#HOW TO IMPORT A FAILED SITES CONFIGURATION" style="text-decoration: none">
HOW TO IMPORT A FAILED SITE'S CONFIGURATION</a> </p>
<p>
&nbsp;&nbsp;&nbsp;
<a href="#HOW TO IMPORT A FAILED SITES DIGITAL DATA AND START THEIR GFE IN ONE STEP" style="text-decoration: none">
HOW TO IMPORT A FAILED SITE'S DIGITAL DATA AND START THEIR GFE IN ONE STEP</a>
</p>
<p>
&nbsp;&nbsp;&nbsp;
<a href="#HOW TO IMPORT A FAILED SITES DIGITAL DATA" style="text-decoration: none">
HOW TO IMPORT A FAILED SITE'S DIGITAL DATA</a> </p>
<p>
&nbsp;&nbsp;&nbsp;
<a href="#HOW TO EXPORT GRIDS BACK TO A FAILED SITE" style="text-decoration: none">
HOW TO EXPORT GRIDS BACK TO A FAILED SITE</a> </p>
<p>
&nbsp;&nbsp;&nbsp;
<a href="#HOW_TO_EXPORT_A_FAILED_SITES_DIGITAL_DATA_TO_THE_CENTRAL_SERVER" style="text-decoration: none">HOW TO EXPORT A FAILED SITE'S DIGITAL DATA
TO THE CENTRAL SERVER</a></p>
<p>
&nbsp;&nbsp;&nbsp;
<a href="#HOW TO EXPORT YOUR CONFIGURATION TO THE CENTRAL SERVER" style="text-decoration: none">
HOW TO EXPORT YOUR CONFIGURATION TO THE CENTRAL SERVER</a> </p>
<p>
&nbsp;&nbsp;&nbsp;
<a href="#HOW TO EXPORT YOUR DIGITAL DATA TO THE CENTRAL SERVER" style="text-decoration: none">
HOW TO EXPORT YOUR DIGITAL DATA TO THE CENTRAL SERVER</a> </p>
<p>
&nbsp;&nbsp;&nbsp;
<a href="#HOW TO START GFE FROM THE SERVICE BACKUP GUI" style="text-decoration: none">
HOW TO START GFE FROM THE SERVICE BACKUP GUI</a> </p>
<p>&nbsp;&nbsp;&nbsp; <a href="#HOW TO EXIT SERVICE BACKUP" style="text-decoration: none">
HOW TO EXIT SERVICE BACKUP</a> </p>
<p>&nbsp;&nbsp;&nbsp; <a href="#HOW TO CLEAN UP SERVICE BACKUP" style="text-decoration: none">
HOW TO CLEAN UP SERVICE BACKUP</a> </p>
<hr>
<p align="left">&nbsp;</p>
<p align="left"><b><a name="HOW_TO_START_GHG_SERVICE_BACKUP">HOW TO START GHG
SERVICE BACKUP</a> </b><a href="#Top" style="text-decoration: none">[BACK
TO THE TOP]</a></p>
<p align="left">1,&nbsp; Verify that the banner at the top of the Service Backup
GUI reads &quot;YOU ARE NOT IN BACKUP MODE.&quot;&nbsp; If you are already in backup mode
for another site, you will need to run the
<a href="#HOW TO CLEAN UP SERVICE BACKUP" style="text-decoration: none">
clean up</a> script first.</p>
<p align="center">
<img border="0" src="banner_no_backup.gif" width="539" height="796"></p>
<p align="left">2.&nbsp; Select GHG Service Backup and press OK.</p>
<p align="left">3.&nbsp; The script will first check to see if there are any
service backup files present that may cause a problem.&nbsp; If any are found,
you will be prompted to clean up.&nbsp; If you wish to clean up and continue,
select CLEAN.&nbsp; Otherwise, select QUIT to return to the Service Backup GUI.&nbsp; </p>
<p align="center">
<img border="0" src="xmessage_faq_02.jpg" width="480" height="96"></p>
<p align="left">If no files are found, the script will run silently and you will
not be notified.</p>
<p align="left">4.&nbsp; Another GUI will appear, asking for the ID of the
failed site.&nbsp; Enter the failed site's 3 letter ID and press OK.</p>
<p align="center">
<img border="0" src="failed_site.jpg" width="544" height="259"></p>
<p align="left">5.&nbsp; After a few minutes, a progress bar will appear with
the status of the failed site's configuration.&nbsp; When it is finished, you
may close the progress bar.</p>
<p align="left">6.&nbsp; 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.&nbsp; If it is not able to connect after ten
attempts, you will be notified and will not be allowed to continue.</p>
<p align="center">
<img border="0" src="xmessage_inst_01.jpg" width="382" height="64"></p>
<p align="left">
7.&nbsp; Once the GUI is able to connect to the server, the GFE Startup GUI will
appear.&nbsp; Select a User, Config file, and Mode and press Start.&nbsp; At
this point, you will be able to generate the failed site's warnings.&nbsp; Once
you have done this, you can <a href="#HOW TO IMPORT A FAILED SITES DIGITAL DATA" style="text-decoration: none">import the failed site's digital data
</a>and perform a full service backup.</p>
<p align="left">
&nbsp;</p>
<p align="left"><b>
<a name="HOW TO IMPORT A FAILED SITES CONFIGURATION AND DIGITAL DATA AND START THEIR GFE IN ONE STEP">HOW TO IMPORT A FAILED SITE'S CONFIGURATION AND DIGITAL DATA AND START
THEIR GFE IN
ONE STEP</a>&nbsp; </b>
<a style="text-decoration: none" href="#Top">[BACK TO THE TOP]</a></p>
<p align="left">1.&nbsp; Verify that the banner at the top of the Service Backup
GUI reads &quot;YOU ARE NOT IN BACKUP MODE.&quot;&nbsp; If you are backing up
another site, you will
need to <a href="#HOW TO CLEAN UP SERVICE BACKUP"
style="text-decoration: none">clean up </a>first.</p>
<p align="center">
<img border="0" src="banner_no_backup.gif" width="539" height="796"></p>
<p align="left">2.&nbsp; Select Import Configuration Data and press OK.</p>
<p align="left">3.&nbsp; The script will first check to see if there are any
service backup files present that may cause a problem.&nbsp; If any are found,
you will be prompted to clean up.&nbsp; If you wish to clean up and continue,
select CLEAN.&nbsp; Otherwise, select QUIT to return to the Service Backup GUI.&nbsp; </p>
<p align="center">
<img border="0" src="xmessage_faq_02.jpg" width="480" height="96"></p>
<p align="left">If no files are found, the script will run silently and you will
not be notified.</p>
<p align="left">4.&nbsp; Another GUI will appear asking you &quot;Would you also like
to Import Digital Forecast and/or Start GFE.&quot;&nbsp; Verify that both buttons are
selected and press OK.</p>
<p align="center">
<img border="0" src="option_both.jpg" width="307" height="300"></p>
<p align="left">5.&nbsp; Another GUI will appear, asking for the ID of the
failed site.&nbsp; Enter the failed site's 3 letter ID and press OK.</p>
<p align="center">
<img border="0" src="failed_site.jpg" width="544" height="259"></p>
<p align="left">6.&nbsp; After a few minutes, a progress bar will appear with
the status of the failed site's configuration.&nbsp; When it is finished, you
may close the progress bar.</p>
<p align="left">7.&nbsp; 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.&nbsp; If it is not able to connect after ten
attempts, you will be notified and will not be allowed to continue.</p>
<p align="center">
<img border="0" src="xmessage_inst_01.jpg" width="382" height="64"></p>
<p align="left">8.&nbsp; If the GUI is able to connect to the failed site's
server, you will see another progress bar appear with the status of&nbsp; the
import of the failed site's digital data.&nbsp; When it is finished, you may
close the progress bar.</p>
<p align="left">9.&nbsp; If the import of the digital data is successful, the
GFE Startup GUI will appear.&nbsp; Select a User, Config file, and Mode and press Start.</p>
<p align="left">&nbsp;</p>
<p align="left"><b>
<a name="HOW TO IMPORT A FAILED SITES CONFIGURATION AND DIGITAL DATA IN ONE STEP">HOW TO IMPORT&nbsp; A FAILED SITE'S CONFIGURATION AND DIGITAL DATA IN
ONE STEP</a>&nbsp; </b>
<a style="text-decoration: none" href="#Top">[BACK TO THE TOP]</a></p>
<p align="left">1.&nbsp; Verify that the banner at the top of the Service Backup
GUI reads &quot;YOU ARE NOT IN BACKUP MODE.&quot;&nbsp; If you are already in
backup mode, you will
need to <a href="#HOW TO CLEAN UP SERVICE BACKUP"
style="text-decoration: none">clean up</a> first.</p>
<p align="center">
<img border="0" src="banner_no_backup.gif" width="539" height="796"></p>
<p align="left">2.&nbsp; Select Import Configuration Data and press OK.</p>
<p align="left">3.&nbsp; The script will first check to see if there are any
service backup files present that may cause a problem.&nbsp; If any are found,
you will be prompted to clean up.&nbsp; If you wish to clean up and continue,
select CLEAN.&nbsp; Otherwise, select QUIT to return to the Service Backup GUI.&nbsp; </p>
<p align="center">
<img border="0" src="xmessage_faq_02.jpg" width="480" height="96"></p>
<p align="left">If no files are found, the script will run silently and you will
not be notified.</p>
<p align="left">4.&nbsp; Another GUI will appear asking you &quot;Would you also like
to Import Digital Forecast and/or Start GFE.&quot;&nbsp; Verify that only the &quot;Import
Digital Data&quot; button is
selected and press OK.</p>
<p align="center">
<img border="0" src="option_import.jpg" width="307" height="300"></p>
<p align="left">5.&nbsp; Another GUI will appear, asking for the ID of the
failed site.&nbsp; Enter the failed site's 3 letter ID and press OK.</p>
<p align="center">
<img border="0" src="failed_site.jpg" width="544" height="259"></p>
<p align="left">6.&nbsp; After a few minutes, a progress bar will appear with
the status of the failed site's configuration.&nbsp; When it is finished, you
may close the progress bar.</p>
<p align="left">7.&nbsp; 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.&nbsp; If it is not able to connect after ten
attempts, you will be notified and will not be allowed to continue.</p>
<p align="center">
<img border="0" src="xmessage_inst_01.jpg" width="382" height="64"></p>
<p align="left">8.&nbsp; If the GUI is able to connect to the failed site's
server, you will see another progress bar appear with the status of&nbsp; the
import of the failed site's digital data.&nbsp; When it is finished, you may
close the progress bar.</p>
<p align="left">&nbsp;</p>
<p align="left"><b>
<a name="HOW TO IMPORT A FAILED SITES CONFIGURATION AND START THEIR GFE IN ONE STEP">HOW TO IMPORT A FAILED SITE'S CONFIGURATION AND START THEIR GFE IN
ONE STEP</a>&nbsp; </b>
<a style="text-decoration: none" href="#Top">[BACK TO THE TOP]</a></p>
<p align="left">1.&nbsp; Verify that the banner at the top of the Service Backup
GUI reads &quot;YOU ARE NOT IN BACKUP MODE.&quot;&nbsp; If you are already in
backup mode, you will
need to <a href="#HOW TO CLEAN UP SERVICE BACKUP"
style="text-decoration: none">clean up</a> first.</p>
<p align="center">
<img border="0" src="banner_no_backup.gif" width="539" height="796"></p>
<p align="left">2.&nbsp; Select Import Configuration Data and press OK.</p>
<p align="left">3.&nbsp; The script will first check to see if there are any
service backup files present that may cause a problem.&nbsp; If any are found,
you will be prompted to clean up.&nbsp; If you wish to clean up and continue,
select CLEAN.&nbsp; Otherwise, select QUIT to return to the Service Backup GUI.&nbsp; </p>
<p align="center">
<img border="0" src="xmessage_faq_02.jpg" width="480" height="96"></p>
<p align="left">If no files are found, the script will run silently and you will
not be notified.</p>
<p align="left">4.&nbsp; Another GUI will appear asking you &quot;Would you also like
to Import Digital Forecast and/or Start GFE.&quot;&nbsp; Verify that only the &quot;Start
GFE&quot; button is
selected and press OK.</p>
<p align="center">
<img border="0" src="option_gfe.jpg" width="307" height="300"></p>
<p align="left">5.&nbsp; Another GUI will appear, asking for the ID of the
failed site.&nbsp; Enter the failed site's 3 letter ID and press OK.</p>
<p align="center">
<img border="0" src="failed_site.jpg" width="544" height="259"></p>
<p align="left">6.&nbsp; After a few minutes, a progress bar will appear with
the status of the failed site's configuration.&nbsp; When it is finished, you
may close the progress bar.</p>
<p align="left">7.&nbsp; 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.&nbsp; If it is not able to connect after ten
attempts, you will be notified and will not be allowed to continue.</p>
<p align="center">
<img border="0" src="xmessage_inst_01.jpg" width="382" height="64"></p>
<p align="left">8.&nbsp; If the GUI is able to connect to the failed site's
server, the GFE Startup GUI will appear.&nbsp; Select a User, Config file, and
Mode and
press Start.</p>
<p align="left">&nbsp;</p>
<p align="left"><b><a name="HOW TO IMPORT A FAILED SITES CONFIGURATION">HOW TO IMPORT A FAILED SITE'S CONFIGURATION</a>&nbsp; </b>
<a style="text-decoration: none" href="#Top">[BACK TO THE TOP]</a></p>
<p align="left">1.&nbsp; Verify that the banner at the top of the Service Backup
GUI reads &quot;YOU ARE NOT IN BACKUP MODE.&quot;&nbsp; If you are already in
backup mode, you will
need to <a href="#HOW TO CLEAN UP SERVICE BACKUP"
style="text-decoration: none">clean up</a> first.</p>
<p align="center">
<img border="0" src="banner_no_backup.gif" width="539" height="796"></p>
<p align="left">2.&nbsp; Select Import Configuration Data and press OK.</p>
<p align="left">3.&nbsp; The script will first check to see if there are any
service backup files present that may cause a problem.&nbsp; If any are found,
you will be prompted to clean up.&nbsp; If you wish to clean up and continue,
select CLEAN.&nbsp; Otherwise, select QUIT to return to the Service Backup GUI.&nbsp; </p>
<p align="center">
<img border="0" src="xmessage_faq_02.jpg" width="480" height="96"></p>
<p align="left">If no files are found, the script will run silently and you will
not be notified.</p>
<p align="left">4.&nbsp; Another GUI will appear asking you &quot;Would you also like
to Import Digital Forecast and/or Start GFE.&quot;&nbsp; Verify that both buttons are
deselected and press OK.</p>
<p align="center">
<img border="0" src="option_none.jpg" width="307" height="300"></p>
<p align="left">5.&nbsp; Another GUI will appear, asking for the ID of the
failed site.&nbsp; Enter the failed site's 3 letter ID and press OK.</p>
<p align="center">
<img border="0" src="failed_site.jpg" width="544" height="259"></p>
<p align="left">
&nbsp;</p>
<p align="left">6.&nbsp; After a few minutes, a progress bar will appear with
the status of the failed site's configuration.&nbsp; When it is finished, you
may close the progress bar.</p>
<p align="left">&nbsp;</p>
<p><b>
<a name="HOW TO IMPORT A FAILED SITES DIGITAL DATA AND START THEIR GFE IN ONE STEP">HOW TO IMPORT A FAILED SITE'S DIGITAL DATA AND START THEIR GFE IN ONE STEP</a>&nbsp;</b>
<a style="text-decoration: none" href="#Top">[BACK TO THE TOP]</a></p>
<p>1.&nbsp; Verify that the banner at the top of the Service Backup GUI reads
&quot;YOU ARE CURRENTLY BACKING UP XXX&quot; (where XXX is a failed site). If it doesn't,
you must first <a href="#HOW TO IMPORT A FAILED SITES CONFIGURATION AND DIGITAL DATA AND START THEIR GFE IN ONE STEP" style="text-decoration: none">import
the failed site's configuration</a></p>
<p align="center">
<img border="0" src="banner_svcbuMode.gif" width="518" height="828"></p>
<p>2.&nbsp; Select Import XXX's Digital Data and press OK.</p>
<p>3.&nbsp; Another GUI will appear asking you &quot;Would you also like to Start
GFE.&quot;&nbsp; Verify that &quot;Start GFE&quot; is selected and press OK.&nbsp; </p>
<p align="center">
<img border="0" src="option_import_gfe.jpg" width="286" height="250"></p>
<p>4.&nbsp; After a few minutes, a progress bar will appear with the status of
the failed site's digital data.&nbsp; When it is finished, you may close the
progress bar.</p>
<p>5.&nbsp; If the import is successful, the GFE Startup GUI will appear.&nbsp; Select a User, Config
file, and Mode and press Start.</p>
<p>&nbsp;</p>
<p><b><a name="HOW TO IMPORT A FAILED SITES DIGITAL DATA">HOW TO IMPORT A FAILED SITE'S DIGITAL DATA</a>&nbsp; </b>
<a style="text-decoration: none" href="#Top">[BACK TO THE TOP]</a></p>
<p>1.&nbsp; Verify that the banner at the top of the Service Backup GUI reads
&quot;YOU ARE CURRENTLY BACKING UP XXX&quot; (where XXX is a failed site). If it doesn't,
you must first
<a href="#HOW TO IMPORT A FAILED SITES CONFIGURATION AND DIGITAL DATA AND START THEIR GFE IN ONE STEP"
style="text-decoration: none">import the failed site's configuration</a>.</p>
<p align="center">
<img border="0" src="banner_svcbuMode.gif" width="518" height="828"></p>
<p>2.&nbsp; Select Import XXX's Digital Data and press OK.</p>
<p>3.&nbsp; Another GUI will appear asking you &quot;Would you also like to Start
GFE.&quot;&nbsp; Verify that &quot;Start GFE&quot; is deselected and press OK.&nbsp; </p>
<p align="center">
<img border="0" src="option_import_no_gfe.jpg" width="286" height="250"></p>
<p>4.&nbsp; After a few minutes, a progress bar will appear with the status of
the failed site's digital data.&nbsp; When it is finished, you may close the
progress bar.</p>
<p>&nbsp;</p>
<p><b><a name="HOW TO EXPORT GRIDS BACK TO A FAILED SITE">HOW TO EXPORT GRIDS BACK TO A FAILED SITE</a>&nbsp; </b>
<a style="text-decoration: none" href="#Top">[BACK TO THE TOP]</a></p>
<p>1.&nbsp; Verify that the banner at the top of the Service Backup GUI reads
&quot;YOU ARE CURRENTLY BACKING UP XXX&quot; (where XXX is a failed site).&nbsp; If it
doesn't, you must first
<a href="#HOW TO IMPORT A FAILED SITES CONFIGURATION AND DIGITAL DATA AND START THEIR GFE IN ONE STEP"
style="text-decoration: none">import the failed site's configuration</a>.</p>
<p align="center">
<img border="0" src="banner_svcbuMode.gif" width="518" height="828"></p>
<p>2.&nbsp;&nbsp; Select Export Grids to XXX and press OK.</p>
<p>3.&nbsp; A message will appear saying &quot;Exporting Digital Data Back to XXX&quot;
(where XXX is the failed site).</p>
<p align="center">
<img border="0" src="xmessage_inst_02.jpg" width="321" height="96"></p>
<p>&nbsp;</p>
<p><b><a name="HOW_TO_EXPORT_A_FAILED_SITES_DIGITAL_DATA_TO_THE_CENTRAL_SERVER">
HOW TO EXPORT A FAILED SITE'S DIGITAL DATA TO THE CENTRAL SERVER</a>&nbsp; </b>
<a href="#Top" style="text-decoration: none">
[BACK TO THE TOP]</a></p>
<p>1.&nbsp; Verify that the message at the top of the GUI reads &quot;YOU ARE
CURRENTLY BACKING UP XXX&quot; (where XXX is a failed site).&nbsp; If it doesn't, you
must first
<a href="#HOW TO IMPORT A FAILED SITES CONFIGURATION AND DIGITAL DATA AND START THEIR GFE IN ONE STEP"
style="text-decoration: none">import the failed site's configuration</a>.</p>
<p align="center">
<img border="0" src="banner_svcbuMode.gif" width="518" height="828"></p>
<p>2.&nbsp; Select Export XXX's Grids To The Central Server and press OK.</p>
<p>3.&nbsp; A message will appear saying &quot;Exporting XXX's Digital Data To The
Central Server&quot; (where XXX is the failed site).</p>
<p align="center">
<img border="0" src="xmessage_inst_04.jpg" width="447" height="96"></p>
<p>&nbsp;</p>
<p><b><a name="HOW TO EXPORT YOUR CONFIGURATION TO THE CENTRAL SERVER">HOW TO EXPORT YOUR CONFIGURATION TO THE CENTRAL SERVER</a>&nbsp; </b>
<a style="text-decoration: none" href="#Top">[BACK TO THE TOP]</a></p>
<p>1.&nbsp; Start the Service Backup GUI as user ifps.&nbsp; to do this:</p>
<p>&nbsp;&nbsp;&nbsp; a.&nbsp; <font size="-1" face="Lucida Console">su ifps</font>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;b.&nbsp; <font size="-1" face="Lucida Console">cd /awips/ifps/primary/bin</font>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;c.&nbsp; <font size="-1" face="Lucida Console">./service_backup.bat </font></p>
<p>2.&nbsp; Verify that the message at the top of the GUI reads &quot;YOU ARE NOT IN
BACKUP MODE.&quot;&nbsp; If it does not, you will not be able to export your
configuration to the central server.</p>
<p align="center">
<img border="0" src="banner_no_backup.gif" width="539" height="796"></p>
<p>3.&nbsp; Select Export CCC's Configuration to the Central Server (where CCC
is your site's 3 letter ID) and press OK.</p>
<p>&nbsp;</p>
<p><b><a name="HOW TO EXPORT YOUR DIGITAL DATA TO THE CENTRAL SERVER">HOW TO EXPORT YOUR DIGITAL DATA TO THE CENTRAL SERVER</a>&nbsp; </b>
<a style="text-decoration: none" href="#Top">[BACK TO THE TOP]</a></p>
<p>1.&nbsp; Select Export CCC's Digital Forecast to the Central Server (where
CCC is your site's 3 letter ID) and press OK.</p>
<p>&nbsp;</p>
<p><b><a name="HOW TO START GFE FROM THE SERVICE BACKUP GUI">HOW TO START GFE FROM THE SERVICE BACKUP GUI</a>&nbsp; </b>
<a style="text-decoration: none" href="#Top">[BACK TO THE TOP]</a></p>
<p>1.&nbsp; Select Start GFE from the Service Backup GUI and press OK.</p>
<p>2.&nbsp; 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.&nbsp; Select a domain and press OK.&nbsp; </p>
<p align="center">
<img border="0" src="choose_domain.jpg" width="243" height="190"></p>
<p>If you are not in Service Backup Mode or your site does not have multiple
domains, GFE will start for your site.</p>
<p>3.&nbsp; The GFE Startup GUI will appear.&nbsp; Select a User, Config file,
and Mode and press Start.</p>
<p>&nbsp;</p>
<p><b><a name="HOW TO EXIT SERVICE BACKUP">HOW TO EXIT SERVICE BACKUP</a>&nbsp; </b>
<a style="text-decoration: none" href="#Top">[BACK TO THE TOP]</a></p>
<p>1.&nbsp; Verify that the banner at the top of the Service Backup GUI reads
&quot;YOU ARE CURRENTLY BACKING UP XXX&quot; (where XXX is a failed site).&nbsp; If it
does not, you will not be able to exit service backup.</p>
<p align="center">
<img border="0" src="banner_svcbuMode.gif" width="518" height="828"></p>
<p>2.&nbsp; Select Exit Service Backup for XXX (where XXX is a failed site) and
press OK.</p>
<p>3.&nbsp; The service backup clean up script will run.&nbsp; If it is
successful, the Service Backup GUI will disappear when it is finished.</p>
<p>&nbsp;</p>
<p><b><a name="HOW TO CLEAN UP SERVICE BACKUP">HOW TO CLEAN UP SERVICE BACKUP</a>&nbsp; </b>
<a style="text-decoration: none" href="#Top">[BACK TO THE TOP]</a></p>
<p>1.&nbsp; Select Clean Up Service Backup from the Service Backup GUI and press
OK.</p>
<p>2.&nbsp; If the Service Backup GUI is able to determine the failed site, you
will see a message saying &quot;Cleaning Up XXX's Configuration&quot;</p>
<p align="center">
<img border="0" src="xmessage_inst_03.jpg" width="299" height="96"></p>
<p>3.&nbsp; If the Service Backup GUI cannot determine the failed site's ID, a
GUI will appear asking you for the failed site's ID.&nbsp; Enter the failed
site's 3 letter ID and press OK. </p>
<p align="center">
<img border="0" src="failed_site.jpg" width="544" height="259"></p>
</body>
<frameset cols="25%,75%">
<frame name="contents" src="svcbu_instructions_toc.html">
<frame name="main" src="svcbu_startup.html">
</frameset>
</html>

38
cave/com.raytheon.viz.gfe/help/GfeServiceBackup/svcbu_instructions_toc.html Normal file
View file

@ -0,0 +1,38 @@
<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<NTML>
<HEAD>
<META name="Author" content="Ron Anderson">
<TITLE>GFE Service Backup Instructions</TITLE>
</HEAD>
<BODY>
<H2><FONT COLOR="#0000FF"><I>GFE Service Backup</I></FONT></H2>
<H3><FONT COLOR="BLACK"><I>Instructions</I></FONT></H3>
<HR SIZE=5 NOSHADE>
<H4>Startup Actions</H4>
<OL>
<LI><a target="main" href="svcbu_startup.html#Entering_Svcbu">Backing Up a Failed Site</a><BR>
<LI><a target="main" href="svcbu_startup.html#Import_Grids">Importing Failed Site's Grids</a><BR>
<LI><a target="main" href="svcbu_startup.html#Starting_GFE">Starting a GFE Session</a><BR>
</OL>
<BR>
<H4>Exit/Cleanup Actions</H4>
<OL>
<LI><a target="main" href="svcbu_cleanup.html#Export_Failed_Grids">Exporting a Failed Site's Grids</a><BR>
<LI><a target="main" href="svcbu_cleanup.html#Exiting_Svcbu">Exiting Service Backup</a>
</OL>
<BR>
<H4>Local Site Actions</H4>
<OL>
<LI><a target="main" href="svcbu_local.html#Export_Local_Grids">Exporting Local Grids</a>
<LI><a target="main" href="svcbu_local.html#Export_Config">Exporting Local Configuration</a><BR>
</OL>
<BR>
<H4>Status Dialog</H4>
<OL>
<LI><a target="main" href="svcbu_status_dialog.html#Status_Information">Status Explanation</a>
</OL>
</BODY>
</HTML>

75
cave/com.raytheon.viz.gfe/help/GfeServiceBackup/svcbu_local.html Normal file
View file

@ -0,0 +1,75 @@
<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
<head>
<meta name="Author" content="Ron Anderson">
<title>GFE Service Backup Local Site Actions</title>
</head>
<body>
<H1>GFE Service Backup Local Site Actions</H1>
<HR>
<H3><a name="Export_Local_Grids">EXPORTING YOUR FORECAST GRIDS TO THE CENTRAL SERVER</a></H3>
<p>This action would normally be done prior to your local site going down for maintenance/repair/upgrade.
</p>
<ol>
<li>Select a primary site from the drop down next to the "Export Forecast Grids" button in
the "Local Site Actions" section of the Service Backup Dialog.
If you only have a single GFE domain your primary site will already be selected.
</li>
<p align="center">
<img border="0" src="images/svcbu_export_config.png"></p>
<li> Click the "Export Forecast Grids" button in
the "Local Site Actions" section of the Service Backup Dialog.
</li>
<li>A
<a target="main" style="text-decoration: none"
href="svcbu_status_dialog.html#Status_Information">Service Backup Status Dialog</a>
will open showing the status of each step required to export
your forecast grids to the central server.
</li>
<p align="center">
<img border="0" src="images/svcbu_export_local_grids_status.png"</p>
</ol>
<H3><a name="Export_Config">EXPORTING YOUR LOCAL CONFIGURATION TO THE CENTRAL SERVER</a></H3>
<p>This action should be performed by the GFE focal point whenever your local configuration has
been changed to ensure that the backup site will have your latest configuration should you
need to enter service backup.
</p>
<p>NOTE: The "Export Configuration" button will only be displayed if the Service Backup
Dialog is started by a user having the GFE focalPoint permission.
Contact your AWIPS administrator if you need to have this permission assigned to you.
</p>
<ol>
<li>Select a primary site from the drop down next to the "Export Configuration" button.
If you only have a single GFE domain your primary site will already be selected.
</li>
<p align="center">
<img border="0" src="images/svcbu_export_config.png"></p>
<li> Click the "Export Configuration" button.
</li>
<li>A
<a target="main" style="text-decoration: none"
href="svcbu_status_dialog.html#Status_Information">Service Backup Status Dialog</a>
will open showing the status of each step required to export
your configuration to the central server.
</li>
<p align="center">
<img border="0" src="images/svcbu_export_config_status.png"</p>
</ol>
</body>
</html>

249
cave/com.raytheon.viz.gfe/help/GfeServiceBackup/svcbu_multidom.html
View file

@ -1,249 +0,0 @@
<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
<head>
<meta name="Author" content="John Wagner">
<title>Service Backup GUI Help</title>
</head>
<body>
<TABLE BORDER="0" WIDTH="100%">
<TR VALIGN="TOP">
<TD ALIGN="CENTER" VALIGN="TOP">
<H1><A NAME="#MULTIPLE_DOMAIN_HELP_PAGE"><FONT COLOR="#0000FF"><I>Service Backup GUI</I>
</FONT></H1>
<H2><i>Multiple Domains</i></H2></TD>
</TR>
</TABLE><BR>
<HR SIZE=5 NOSHADE>
<p align="left">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </p>
<p class="MsoNormal">If your site currently has two domains, you will notice
that there are several differences between your GUI and related programs and the
GUI and programs that appear in the help pages.&nbsp; These differences include</p>
<p class="MsoNormal">
<br><a href="#Banners" style="text-decoration: none">Banners</a>
<br><a href="#Choose_Domain_GUI" style="text-decoration: none">Choose Domain GUI</a>
<br><a href="#Clean_Up_Script" style="text-decoration: none">Clean Up Script</a>
<br><a href="#Error_Messages" style="text-decoration: none">Error Messages</a>
</p>
<p class="MsoNormal">This page will explain the differences that you may
encounter while using the Service Backup GUI (In all of the examples below, CCC
is the 3 letter ID of the domain that is running the Service Backup GUI, DDD is
the 3 letter ID of the other domain that is not controlled by the Service Backup
GUI, XXX is a failed site being backed up by CCC, and YYY is a failed site that
DDD is performing service backup for.).</p>
<hr>
<p class="MsoNormal"><a name="Banners"><b>Banners</b></a>&nbsp;
<a href="#MULTIPLE_DOMAIN_HELP_PAGE" style="text-decoration: none">[BACK
TO THE TOP]</a></p>
<p class="MsoNormal">If you site has two domains, you will notice that there are
two banners at the top of the GUI.&nbsp; The top banner will reflect the state of the
Service Backup GUI for the domain that you are currently running it as.&nbsp; These
messages that appear in the GUI will not differ from those at single domain
sites that appear in the other Help pages.&nbsp; When you are in service backup mode,
the background of the banner will be orange.</p>
<p class="MsoNormal">The lower banner will reflect the state of the Service
Backup GUI for the domain that you are not running the GUI as.&nbsp; When that domain
is in service backup mode, the background of the banner will be yellow.&nbsp; The
message in this banner will differ from those in the other help pages.&nbsp; You will
see these banners below and how they will effect the&nbsp; state of the Service
Backup GUI.</p>
<p class="MsoNormal">&nbsp;</p>
<p class="MsoNormal" align="center">
<img border="0" src="multi_no_backup.gif" width="539" height="822"></p>
<p class="MsoNormal" align="left">&nbsp;</p>
<p class="MsoNormal" align="left">You will see this first banner when both
domains are not in service backup mode.&nbsp; At this point, you will be able to</p>
<p class="MsoNormal" align="left">&nbsp;&nbsp;&nbsp; -Import a failed site's
configuration</p>
<p class="MsoNormal" align="left">&nbsp;&nbsp;&nbsp; -Export CCC's configuration
to the central server for service backup (this option is only enabled when the
GUI is started as user ifps)</p>
<p class="MsoNormal" align="left">&nbsp;&nbsp;&nbsp; -Export CCC's digital data
to the central server for service backup</p>
<p class="MsoNormal" align="left">&nbsp;&nbsp;&nbsp; -Start GFE</p>
<p class="MsoNormal" align="left">&nbsp;&nbsp;&nbsp; -Run the
<a href="#Clean_Up_Script" style="text-decoration: none">clean up script</a></p>
<p class="MsoNormal" align="left">&nbsp;</p>
<p class="MsoNormal" align="center">
<img border="0" src="multi_imprtMode.gif" width="539" height="854"></p>
<p class="MsoNormal" align="left">&nbsp;</p>
<p class="MsoNormal" align="left">You will see this banner when DDD is importing
a failed site's configuration.&nbsp; Until the import is finished, you will only
be allowed to </p>
<p class="MsoNormal" align="left">&nbsp;&nbsp;&nbsp; -Export CCC's digital data
to the central server for service backup</p>
<p class="MsoNormal" align="left">&nbsp;&nbsp;&nbsp; -Start GFE</p>
<p class="MsoNormal" align="left">&nbsp;&nbsp;&nbsp; -Run the
<a href="#Clean_Up_Script" style="text-decoration: none">clean up script</a></p>
<p class="MsoNormal" align="left">&nbsp;</p>
<p class="MsoNormal" align="center">
<img border="0" src="multi_waitMode.gif" width="539" height="854"></p>
<p class="MsoNormal" align="center">&nbsp;</p>
<p class="MsoNormal" align="left">You will see this banner if DDD has finished
importing YYY's configuration and is waiting for YYY's server to start to begin
importing YYY's digital data.&nbsp; At this point, you will only be able to</p>
<p class="MsoNormal" align="left">&nbsp;&nbsp;&nbsp; -Export CCC's digital data
to the central server for service backup</p>
<p class="MsoNormal" align="left">&nbsp;&nbsp;&nbsp; -Start GFE</p>
<p class="MsoNormal" align="left">&nbsp;&nbsp;&nbsp; -Run the
<a href="#Clean_Up_Script" style="text-decoration: none">clean up script</a></p>
<p class="MsoNormal" align="left">&nbsp;</p>
<p class="MsoNormal" align="center">
<img border="0" src="multi_imprtGrdMode.gif" width="539" height="854"></p>
<p class="MsoNormal" align="center">&nbsp;</p>
<p class="MsoNormal" align="left">You will see this banner while DDD is
importing YYY's digital data.&nbsp; Until the import is finished, you will only
be able to </p>
<p class="MsoNormal" align="left">&nbsp;&nbsp;&nbsp; -Export CCC's digital data
to the central server for service backup</p>
<p class="MsoNormal" align="left">&nbsp;&nbsp;&nbsp; -Start GFE</p>
<p class="MsoNormal" align="left">&nbsp;&nbsp;&nbsp; -Run the
<a href="#Clean_Up_Script" style="text-decoration: none">clean up script</a></p>
<p class="MsoNormal">&nbsp;</p>
<p class="MsoNormal" align="center">
<img border="0" src="multi_svcbuMode.gif" width="539" height="854"></p>
<p class="MsoNormal" align="center">&nbsp;</p>
<p class="MsoNormal" align="left">You will see this message while DDD is backing
up YYY and DDD is not currently importing or exporting any digital data or
configuration files.&nbsp; At this point, you will be able to</p>
<p class="MsoNormal" align="left">&nbsp;&nbsp;&nbsp; -Import a failed site's
configuration</p>
<p class="MsoNormal" align="left">&nbsp;&nbsp;&nbsp; -Export CCC's configuration
to the central server for service backup (this option is only enabled when the
GUI is started as user ifps)</p>
<p class="MsoNormal" align="left">&nbsp;&nbsp;&nbsp; -Export CCC's digital data
to the central server for service backup</p>
<p class="MsoNormal" align="left">&nbsp;&nbsp;&nbsp; -Start GFE</p>
<p class="MsoNormal" align="left">&nbsp;&nbsp;&nbsp; -Run the
<a href="#Clean_Up_Script" style="text-decoration: none">clean up script</a></p>
<p class="MsoNormal" align="left">&nbsp;</p>
<p class="MsoNormal" align="center">
<img border="0" src="multi_exprtbksiteGrdMode.gif" width="539" height="854"></p>
<p class="MsoNormal" align="center">&nbsp;</p>
<p class="MsoNormal" align="left">You will see this message while DDD is
exporting YYY's grids back to them.&nbsp; At this point, you will only be able
to</p>
<p class="MsoNormal" align="left">&nbsp;&nbsp;&nbsp; -Export CCC's digital data
to the central server for service backup</p>
<p class="MsoNormal" align="left">&nbsp;&nbsp;&nbsp; -Start GFE</p>
<p class="MsoNormal" align="left">&nbsp;&nbsp;&nbsp; -Run the
<a href="#Clean_Up_Script" style="text-decoration: none">clean up script</a></p>
<p class="MsoNormal">&nbsp;</p>
<p class="MsoNormal" align="center">
<img border="0" src="multi_exprtbksiteGrdToCSMode.gif" width="539" height="854"></p>
<p class="MsoNormal" align="left">You will see this message while DDD is
exporting YYY's grids to the central server.&nbsp; At this point, you will only be able
to</p>
<p class="MsoNormal" align="left">&nbsp;&nbsp;&nbsp; -Export CCC's digital data
to the central server for service backup</p>
<p class="MsoNormal" align="left">&nbsp;&nbsp;&nbsp; -Start GFE</p>
<p class="MsoNormal" align="left">&nbsp;&nbsp;&nbsp; -Run the
<a href="#Clean_Up_Script" style="text-decoration: none">clean up script</a></p>
<p class="MsoNormal" align="left">&nbsp;</p>
<p class="MsoNormal" align="center">
<img border="0" src="multi_exprtMode.gif" width="539" height="880"></p>
<p class="MsoNormal" align="center">&nbsp;</p>
<p class="MsoNormal" align="left">You will see this message while DDD is
exporting their configuration to the central server for service backup.&nbsp; At
this point, you will only be able to</p>
<p class="MsoNormal" align="left">&nbsp;&nbsp;&nbsp; -Export CCC's digital data
to the central server for service backup</p>
<p class="MsoNormal" align="left">&nbsp;&nbsp;&nbsp; -Start GFE</p>
<p class="MsoNormal" align="left">&nbsp;&nbsp;&nbsp; -Run the
<a href="#Clean_Up_Script" style="text-decoration: none">clean up script</a></p>
<p class="MsoNormal">&nbsp;</p>
<p class="MsoNormal" align="center">
<img border="0" src="multi_exprtGrdMode.gif" width="539" height="880"></p>
<p class="MsoNormal" align="center">&nbsp;</p>
<p class="MsoNormal" align="left">You will see this message while DDD is
exporting their grids to the central server for service backup.&nbsp; At this
point, you will only be able to</p>
<p class="MsoNormal" align="left">&nbsp;&nbsp;&nbsp; -Import Configuration Data</p>
<p class="MsoNormal" align="left">&nbsp;&nbsp;&nbsp; -Export CCC's digital data
to the central server for service backup</p>
<p class="MsoNormal" align="left">&nbsp;&nbsp;&nbsp; -Start GFE</p>
<p class="MsoNormal" align="left">&nbsp;&nbsp;&nbsp; -Run the
<a href="#Clean_Up_Script" style="text-decoration: none">clean up script</a></p>
<p class="MsoNormal">&nbsp;</p>
<p class="MsoNormal"><a name="Choose_Domain_GUI"><b>Choose Domain GUI</b></a>&nbsp;
<a href="#MULTIPLE_DOMAIN_HELP_PAGE" style="text-decoration: none">[BACK
TO THE TOP]</a></p>
<p class="MsoNormal">If your site has multiple domains, the Choose Domain GUI
will allow you to select which domain to start the Service Backup GUI and GFE
as.&nbsp; The GUI also provides you with the location of that domain’s server.&nbsp; This
will hopefully make it easier to perform service backup for two failed sites.</p>
<p class="MsoNormal">&nbsp;</p>
<p class="MsoNormal" align="center">
<img border="0" src="choose_domain_multi1.jpg" width="243" height="190"></p>
<p class="MsoNormal" align="center"><font size="2">While you are not in service
backup mode, the Choose Domain GUI displays both domains and the location of
each domain's server</font></p>
<p class="MsoNormal" align="center">&nbsp;</p>
<p class="MsoNormal" align="center">
<img border="0" src="choose_domain_multi2.jpg" width="243" height="234"></p>
<p class="MsoNormal" align="center"><font size="2">While you are in service
backup mode, the Choose Domain GUI displays both domains and any failed site's
that are currently being backed up.&nbsp; </font></p>
<p class="MsoNormal">&nbsp;</p>
<p class="MsoNormal"><a name="Clean_Up_Script"><b>Clean Up Script</b></a>&nbsp;
<a href="#MULTIPLE_DOMAIN_HELP_PAGE" style="text-decoration: none">[BACK
TO THE TOP]</a></p>
<p class="MsoNormal">The clean up script will only allow you to clean up a
failed site's configuration as the domain that you initiated service backup as.&nbsp;
When backing up two failed sites, be sure to check what domain you are running
as to prevent cleaning up the wrong site.&nbsp;&nbsp; If you try to clean up a
failed site from the wrong domain, you will see the following message:</p>
<p class="MsoNormal">&nbsp;</p>
<p class="MsoNormal" align="center">
<img border="0" src="xmessage_multidom_01.jpg" width="424" height="96"></p>
<p class="MsoNormal" align="center">&nbsp;</p>
<p class="MsoNormal" align="left"><b><a name="Error_Messages">Error Messages</a></b>&nbsp;
<a href="#MULTIPLE_DOMAIN_HELP_PAGE" style="text-decoration: none">[BACK TO THE TOP]</a></p>
<p class="MsoNormal" align="left">There are a few error messages that will only
appear if your site has multiple domains.&nbsp; These messages appear below,
along with a brief explanation of each one.</p>
<p class="MsoNormal" align="left">&nbsp;</p>
<p class="MsoNormal" align="center">
<img border="0" src="xmessage_multidom_02.jpg" width="358" height="140"></p>
<p class="MsoNormal" align="left">This message will appear when you try to
import a failed site's configuration while DDD is in the process of importing or
exporting data.&nbsp; Check the yellow banner at the top of the service backup
GUI to see what they are importing or exporting.&nbsp; Once they are finished,
you will be able to import a failed site's configuration.</p>
<p class="MsoNormal" align="left">&nbsp;</p>
<p class="MsoNormal" align="center">
<img border="0" src="xmessage_multidom_03.jpg" width="340" height="140"></p>
<p class="MsoNormal" align="left">This message will appear when you try to
import a failed site's digital data while DDD is in the process of&nbsp;
importing or exporting data.&nbsp; Check the yellow banner at the top of the
service backup GUI to see what they are importing or exporting.&nbsp; Once they
are finished, you will be able to import the failed site's digital data.</p>
<p class="MsoNormal" align="left">&nbsp;</p>
<p class="MsoNormal" align="center">
<img border="0" src="xmessage_multidom_04.jpg" width="336" height="140"></p>
<p class="MsoNormal" align="left">This message will appear when you try to
export grids back to a failed site while DDD is in the process of&nbsp;
importing or exporting data.&nbsp; Check the yellow banner at the top of the
service backup GUI to see what they are importing or exporting.&nbsp; Once they
are finished, you will be able to export the digital data back to the failed
site.</p>
<p class="MsoNormal" align="left">&nbsp;</p>
<p class="MsoNormal" align="center">
<img border="0" src="xmessage_multidom_05.jpg" width="354" height="140"></p>
<p class="MsoNormal" align="left">This message will appear when you try to
export your configuration to the central server while DDD is in the process of&nbsp;
importing or exporting data.&nbsp; Check the yellow banner at the top of the
service backup GUI to see what they are importing or exporting.&nbsp; Once they
are finished, you will be able to export your configuration to the central
server.</p>
<p class="MsoNormal" align="left">&nbsp;</p>
<p class="MsoNormal" align="center">
<img border="0" src="xmessage_multidom_06.jpg" width="332" height="162"></p>
<p class="MsoNormal" align="left">This message will appear when you try to
export a failed site's digital data to the central server while DDD is in the
process of importing or exporting data.&nbsp; Check the yellow banner at the top
of the service backup GUI to see what they are importing or exporting.&nbsp;
Once they are finished, you will be able to export a failed site's digital data
to the central server.</p>
</body>
</html>

131
cave/com.raytheon.viz.gfe/help/GfeServiceBackup/svcbu_startup.html Normal file
View file

@ -0,0 +1,131 @@
<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
<head>
<meta name="Author" content="Ron Anderson">
<title>GFE Service Backup Startup Actions</title>
</head>
<body>
<H1>GFE Service Backup Startup Actions</H1>
<HR>
<H3><a name="Entering_Svcbu">ENTERING SERVICE BACKUP FOR A FAILED SITE</a></H3>
<ol>
<li>Verify that the banner at the top of the Service Backup
Dialog reads &quot;YOU ARE NOT IN BACKUP MODE&quot;&nbsp; or does not include the failed site
you wish to back up under "YOU ARE BACKING UP".
<br>
If the failed site is listed you may want to
<a href="#HOW_TO_EXIT_SERVICE_BACKUP" style="text-decoration: none">exit</a> and re-enter service backup to ensure you are using the failed site's latest configuration.</li>
<p align="center">
<img border="0" hspace="10" src="images/banner_no_backup.png">
<img border="0" hspace="10" src="images/banner_svcbuMode.png"></p>
<li>Select the failed site from the drop down next to the "Enter Service Backup" button.
The sites you commonly back up will appear at the top of the list.
</li>
<li>Check the boxes next to any desired start up options:</li>
<ol type="a">
<li><b>Import Forecast Grids:</b> Automatically import the failed site's digital forecast grids.
If you are entering service backup to issue an urgent warning product you may wish to skip
this step. You can import the grids after after entering service backup using the
<a href="#Import_Grids" style="text-decoration: none">"Import Forecast Grids"</a> button.
</li>
<li><b>Troubleshooting Mode:</b> You should check this box if you are activating the site
for testing and intending to enter service backup. This will disable ISC and
VTEC Active Table sharing since you are not acting as the failed site.
</li>
<li><b>Automatically Start GFE:</b> Checking this box will automatically start a GFE session
for the failed site as you enter service backup. You can also do this after entering
service backup using the
<a href="#Starting_GFE" style="text-decoration: none">"Start GFE Session"</a> button.
</li>
</ol>
<p align="center">
<img border="0" src="images/svcbu_enter.png">
</p>
<li>After you have selected the desired start up options, click the "Enter Service Backup"
button.
</li>
<li>A
<a target="main" style="text-decoration: none"
href="svcbu_status_dialog.html#Status_Information">Service Backup Status Dialog</a>
will open showing the status of each step required to enter
service backup for the failed site.
</li>
</ol>
<H3><a name="Import_Grids">IMPORTING A FAILED SITE'S FORECAST GRIDS</a></H3>
<ol>
<li>Verify that the failed site is listed in the banner at the top of the Service Backup Dialog under
&quot;YOU ARE CURRENTLY BACKING UP&quot;. If it isn't, you must first
<a href="#Entering_Svcbu" style="text-decoration: none">enter service backup for the failed site.</a>
</li>
<p align="center">
<img border="0" src="images/banner_svcbuMode_2.png"></p>
<li>Select the failed site from the drop down next to the "Import Forecast Grids" button.
Only sites you are currently backing up will appear in the list.
</li>
<p align="center">
<img border="0" src="images/svcbu_import_grids.png"></p>
<li>
Click the "Import Forecast Grids" button to start the import.
</li>
<li>A
<a target="main" style="text-decoration: none"
href="svcbu_status_dialog.html#Status_Information">Service Backup Status Dialog</a>
will open showing the status of each step required to import
the failed site's forecast grids.
<p align="center">
<img border="0" src="images/svcbu_import_grids_status.png"</p>
</li>
</ol>
<H3><a name="Starting_GFE">STARTING A GFE SESSION</a></H3>
<ol>
<li>Verify that the failed site is listed in the banner at the top of the Service Backup Dialog under
&quot;YOU ARE CURRENTLY BACKING UP&quot;. If it isn't, you must first
<a href="#Entering_Svcbu" style="text-decoration: none">enter service backup for the failed site.</a>
</li>
<p align="center">
<img border="0" src="images/banner_svcbuMode_2.png"></p>
<li>Select the failed site from the drop down next to the "Start GFE Session" button.
Only sites you are currently backing up will appear in the list.
</li>
<p align="center">
<img border="0" src="images/svcbu_start_gfe.png"></p>
<li>
Click the "Start GFE Session" button to start the import.
</li>
<li>A
<a target="main" style="text-decoration: none"
href="svcbu_status_dialog.html#Status_Information">Service Backup Status Dialog</a>
will open showing the status of each step required to start a GFE session for the failed site.
<p align="center">
<img border="0" src="images/svcbu_start_gfe_status.png"</p>
</li>
</ol>
</ol>
</body>
</html>

45
cave/com.raytheon.viz.gfe/help/GfeServiceBackup/svcbu_status_dialog.html Normal file
View file

@ -0,0 +1,45 @@
<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
<head>
<meta name="Author" content="Ron Anderson">
<title>GFE Service Backup Status Dialog</title>
</head>
<body>
<H1>GFE Service Backup Status Dialog</H1>
<HR>
<H3><a name="Status_Information">STATUS EXPLANATION</a></H3>
<p>The Service Backup Status Dialog displays status of active Service Backup jobs.
These jobs consist of a list a steps to be accomplished.
Each step is displayed on a separate line with a status icon and a time.
</p>
<p align="center">
<img border="0" src="images/svcbu_startup_status.png"</p>
<p>The status icons are listed below along with their meaning:
<ul style="list-style: none;">
<li><img border="0" align="bottom" src="images/svcbu_icon_not_started.png"> Not started</li>
<li><img border="0" align="bottom" src="images/svcbu_icon_in_progress_animated.gif"> In progress</li>
<li><img border="0" align="bottom" src="images/svcbu_icon_success.png"> Success</li>
<li><img border="0" align="bottom" src="images/svcbu_icon_failed.png"> Failed</li>
</ul>
</p>
<p>
Steps that are in progress will show the elapsed time for the step to the right of the icon.<br>
Completed steps will show the time of day when the step was completed.
</p>
<p>
Clicking the Cancel button will cause the job to terminate.
</p>
<p>
Checking the "Use large font" box will cause the dialog to display using a large font so you
can monitor the progress of the job from another workstation.
</p>
<p align="center">
<img border="0" src="images/svcbu_startup_status_large.png"</p>
</body>
</html>

BIN
cave/com.raytheon.viz.gfe/help/GfeServiceBackup/xmessage_faq_01.jpg
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 7.1 KiB

BIN
cave/com.raytheon.viz.gfe/help/GfeServiceBackup/xmessage_faq_02.jpg
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 12 KiB

BIN
cave/com.raytheon.viz.gfe/help/GfeServiceBackup/xmessage_faq_03.jpg
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 14 KiB

BIN
cave/com.raytheon.viz.gfe/help/GfeServiceBackup/xmessage_faq_04.jpg
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 15 KiB

BIN
cave/com.raytheon.viz.gfe/help/GfeServiceBackup/xmessage_faq_05.jpg
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 14 KiB

BIN
cave/com.raytheon.viz.gfe/help/GfeServiceBackup/xmessage_faq_06.jpg
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 9.8 KiB

BIN
cave/com.raytheon.viz.gfe/help/GfeServiceBackup/xmessage_faq_07.jpg
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 9.2 KiB

BIN
cave/com.raytheon.viz.gfe/help/GfeServiceBackup/xmessage_faq_08.jpg
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 11 KiB

BIN
cave/com.raytheon.viz.gfe/help/GfeServiceBackup/xmessage_faq_09.jpg
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 11 KiB

BIN
cave/com.raytheon.viz.gfe/help/GfeServiceBackup/xmessage_faq_10.jpg
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 12 KiB

BIN
cave/com.raytheon.viz.gfe/help/GfeServiceBackup/xmessage_faq_11.jpg
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 8.8 KiB

BIN
cave/com.raytheon.viz.gfe/help/GfeServiceBackup/xmessage_faq_12.jpg
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 13 KiB

BIN
cave/com.raytheon.viz.gfe/help/GfeServiceBackup/xmessage_faq_13.jpg
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 7.3 KiB

BIN
cave/com.raytheon.viz.gfe/help/GfeServiceBackup/xmessage_faq_14.jpg
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 9.9 KiB

BIN
cave/com.raytheon.viz.gfe/help/GfeServiceBackup/xmessage_faq_15.jpg
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 10 KiB

BIN
cave/com.raytheon.viz.gfe/help/GfeServiceBackup/xmessage_faq_16.jpg
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 10 KiB

BIN
cave/com.raytheon.viz.gfe/help/GfeServiceBackup/xmessage_faq_17.jpg
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 9.5 KiB

BIN
cave/com.raytheon.viz.gfe/help/GfeServiceBackup/xmessage_faq_18.jpg
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 6.8 KiB

BIN
cave/com.raytheon.viz.gfe/help/GfeServiceBackup/xmessage_faq_19.jpg
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 10 KiB

BIN
cave/com.raytheon.viz.gfe/help/GfeServiceBackup/xmessage_faq_20.jpg
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 16 KiB

BIN
cave/com.raytheon.viz.gfe/help/GfeServiceBackup/xmessage_faq_21.jpg
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 16 KiB

Some files were not shown because too many files have changed in this diff Show more