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




