hans@900: \section{Management of operational processes}
hans@900: 
hans@900: Availability of the components
hans@900:   1. Database server 
hans@900:   2. Artefact-server
hans@900:   3. Apache Tomcat running the WebClient
hans@900:   4. Apache WebServer
hans@900: 
hans@900: During a server startup the installed components get started
hans@900: automatically.
hans@900: 
hans@900: \subsection{Managing the Artefact Server}
hans@900: 
hans@900: \subsubsection*{Start Stop Restart}
hans@900: 
hans@900: The artefact server can be restarted without stopping the WebClient.
hans@900: During the restart-process client accessing the server get an approriate
hans@900: message. Their session data will not be lost if the artefact database
hans@900: will remain untouched.
hans@900: 
hans@900:   Stopping artefact server
hans@900:   \verb+ /etc/init.d/artefact-server stop+
hans@900: 
hans@900:   Starting artefact server
hans@900:   \verb+ /etc/init.d/artefact-server start+
hans@900: 
hans@900:   Restarting artefact server
hans@900:   \verb+ /etc/init.d/artefact-server restart+
hans@900: 
hans@900: \subsubsection*{Monitoring the System}
hans@900: 
hans@900: C.f. Testing the installation for the levels: operating system,
hans@900: network and service availability
hans@900: 
hans@900: \subsubsection*{Troubleshooting}
hans@900: 
hans@900: Database problems
hans@900: For checking problems for problems with the connection to the database
hans@900: server, check the logfile of the artefact-server (c.f. FIXME
hans@900: installation) look for entries like FIXME.
hans@900: 
hans@900: In most cases, a restart of the artefact-server will help to solve
hans@900: problems in the artefact-server. If you still encounter problems, check
hans@900: for the network connection to the database server and the maturity of
hans@900: the database server.
hans@900: 
hans@900: 
hans@900: Inconsistencies between original data and cached data
hans@900: The artefact-server stores result sets of the database in a cache and
hans@900: provides maps via configuration files for MapServer based on shapefiles.
hans@900: In case of inconsistencies showing up for longer than twice the
hans@900: maximum of the update cycle of internal ETL processes, do the following
hans@900: as user \verb+root+:
hans@900: 
hans@900: \begin{lstlisting}
hans@900:   /etc/init.d/artefact-server stop
hans@900:   rm -ri \$ARTEFACT-SERVER-HOME/cache/*
hans@900:   /etc/init.d/artefact-server start
hans@900: \end{lstlisting}
hans@900: 
hans@900: \subsection{Managing the GNV-Client}
hans@900: \subsubsection*{Start Stop Restart}
hans@900: 
hans@900: The GNV-WebClient can be managed by controlling Apache Tomcat instance:
hans@900: 
hans@900:  Status GNV-WebClient
hans@900:  \verb+ /etc/init.d/tomcat5.5 status+
hans@900: 
hans@900:  Stopping GNV-WebClient
hans@900:  \verb+ /etc/init.d/tomcat5.5 stop+
hans@900: 
hans@900:  Starting GNV-WebClient
hans@900:  \verb+ /etc/init.d/tomcat5.5 start+
hans@900: 
hans@900:  Restarting GNV-WebClient
hans@900:  \verb+ /etc/init.d/tomcat5.5 restart+
hans@900: 
hans@900: \subsubsection*{Monitoring the System}
hans@900: 
hans@900: For different possibilities c.f. Testing the installation
hans@900: 
hans@900: \subsubsection*{Troubleshooting}
hans@900: 
hans@900: The GNV-WebClient can not accessed through the Apache WebServer, do the
hans@900: following:
hans@900: 1. \verb+ /etc/init.d/apache2 restart+
hans@900: 2. Check in your browser at \verb+ http://\$SERVERNAME/gnv+
hans@900: 
hans@900: If you still encounter problems, follow the next these steps:
hans@900: {\bf Caution: The entire application will be down until the WebServer is
hans@900: back up}
hans@900: \begin{lstlisting}
hans@900:   /etc/init.d/apache2 stop
hans@900:   /etc/init.d/tomcat5.5 stop
hans@900:   rm -r /usr/share/tomcat5.5/work/Catalina/localhost/gnv/*
hans@900:   /etc/init.d/tomcat5.5 start # wait until tomcat is up
hans@900:   /etc/init.d/apache2 start
hans@900: \end{lstlisting}
hans@900: 
hans@900: For further information, you look into the Logging during the use of the
hans@900: GNV WebClient
hans@900: \verb+ tail -f -n 50 /usr/share/tomcat5.5/logs/gnv.log+
hans@900: 
hans@900: To get even more logging, do the following:
hans@900: 
hans@900: {\bf Caution: The entire application will be down until the Apache Tomcat
hans@900: has started properly; the higher log-level can affect the
hans@900: runtime-behaviour of the client}
hans@900: \begin{lstlisting}
hans@900:   /etc/init.d/tomcat5.5 stop
hans@900:   Set logging to DEBUG (FIXME)
hans@900:   vim /usr/share/tomcat5.5/webapps/gnv/WEB-INF/classes/log4j.properties
hans@900:   /etc/init.d/tomcat5.5 start # wait until tomcat is up
hans@900:   tail -f -n 50 /usr/share/tomcat5.5/logs/gnv.log
hans@900: \end{lstlisting}
hans@900: 
hans@900: It is recommended to undo the logging configuration, after the relevant
hans@900: part has been found.
hans@900: 
hans@900: \section{Lists of References}
hans@900: FIXME
hans@900: 
hans@900: FIXME: How to adapt the address/port of connection to REST-server.E