|
900
|
1 \section{Management of operational processes} |
|
|
2 |
|
|
3 Availability of the components |
|
|
4 1. Database server |
|
|
5 2. Artefact-server |
|
|
6 3. Apache Tomcat running the WebClient |
|
|
7 4. Apache WebServer |
|
|
8 |
|
|
9 During a server startup the installed components get started |
|
|
10 automatically. |
|
|
11 |
|
|
12 \subsection{Managing the Artefact Server} |
|
|
13 |
|
|
14 \subsubsection*{Start Stop Restart} |
|
|
15 |
|
|
16 The artefact server can be restarted without stopping the WebClient. |
|
|
17 During the restart-process client accessing the server get an approriate |
|
|
18 message. Their session data will not be lost if the artefact database |
|
|
19 will remain untouched. |
|
|
20 |
|
|
21 Stopping artefact server |
|
|
22 \verb+ /etc/init.d/artefact-server stop+ |
|
|
23 |
|
|
24 Starting artefact server |
|
|
25 \verb+ /etc/init.d/artefact-server start+ |
|
|
26 |
|
|
27 Restarting artefact server |
|
|
28 \verb+ /etc/init.d/artefact-server restart+ |
|
|
29 |
|
|
30 \subsubsection*{Monitoring the System} |
|
|
31 |
|
|
32 C.f. Testing the installation for the levels: operating system, |
|
|
33 network and service availability |
|
|
34 |
|
|
35 \subsubsection*{Troubleshooting} |
|
|
36 |
|
|
37 Database problems |
|
|
38 For checking problems for problems with the connection to the database |
|
|
39 server, check the logfile of the artefact-server (c.f. FIXME |
|
|
40 installation) look for entries like FIXME. |
|
|
41 |
|
|
42 In most cases, a restart of the artefact-server will help to solve |
|
|
43 problems in the artefact-server. If you still encounter problems, check |
|
|
44 for the network connection to the database server and the maturity of |
|
|
45 the database server. |
|
|
46 |
|
|
47 |
|
|
48 Inconsistencies between original data and cached data |
|
|
49 The artefact-server stores result sets of the database in a cache and |
|
|
50 provides maps via configuration files for MapServer based on shapefiles. |
|
|
51 In case of inconsistencies showing up for longer than twice the |
|
|
52 maximum of the update cycle of internal ETL processes, do the following |
|
|
53 as user \verb+root+: |
|
|
54 |
|
|
55 \begin{lstlisting} |
|
|
56 /etc/init.d/artefact-server stop |
|
|
57 rm -ri \$ARTEFACT-SERVER-HOME/cache/* |
|
|
58 /etc/init.d/artefact-server start |
|
|
59 \end{lstlisting} |
|
|
60 |
|
|
61 \subsection{Managing the GNV-Client} |
|
|
62 \subsubsection*{Start Stop Restart} |
|
|
63 |
|
|
64 The GNV-WebClient can be managed by controlling Apache Tomcat instance: |
|
|
65 |
|
|
66 Status GNV-WebClient |
|
|
67 \verb+ /etc/init.d/tomcat5.5 status+ |
|
|
68 |
|
|
69 Stopping GNV-WebClient |
|
|
70 \verb+ /etc/init.d/tomcat5.5 stop+ |
|
|
71 |
|
|
72 Starting GNV-WebClient |
|
|
73 \verb+ /etc/init.d/tomcat5.5 start+ |
|
|
74 |
|
|
75 Restarting GNV-WebClient |
|
|
76 \verb+ /etc/init.d/tomcat5.5 restart+ |
|
|
77 |
|
|
78 \subsubsection*{Monitoring the System} |
|
|
79 |
|
|
80 For different possibilities c.f. Testing the installation |
|
|
81 |
|
|
82 \subsubsection*{Troubleshooting} |
|
|
83 |
|
|
84 The GNV-WebClient can not accessed through the Apache WebServer, do the |
|
|
85 following: |
|
|
86 1. \verb+ /etc/init.d/apache2 restart+ |
|
|
87 2. Check in your browser at \verb+ http://\$SERVERNAME/gnv+ |
|
|
88 |
|
|
89 If you still encounter problems, follow the next these steps: |
|
|
90 {\bf Caution: The entire application will be down until the WebServer is |
|
|
91 back up} |
|
|
92 \begin{lstlisting} |
|
|
93 /etc/init.d/apache2 stop |
|
|
94 /etc/init.d/tomcat5.5 stop |
|
|
95 rm -r /usr/share/tomcat5.5/work/Catalina/localhost/gnv/* |
|
|
96 /etc/init.d/tomcat5.5 start # wait until tomcat is up |
|
|
97 /etc/init.d/apache2 start |
|
|
98 \end{lstlisting} |
|
|
99 |
|
|
100 For further information, you look into the Logging during the use of the |
|
|
101 GNV WebClient |
|
|
102 \verb+ tail -f -n 50 /usr/share/tomcat5.5/logs/gnv.log+ |
|
|
103 |
|
|
104 To get even more logging, do the following: |
|
|
105 |
|
|
106 {\bf Caution: The entire application will be down until the Apache Tomcat |
|
|
107 has started properly; the higher log-level can affect the |
|
|
108 runtime-behaviour of the client} |
|
|
109 \begin{lstlisting} |
|
|
110 /etc/init.d/tomcat5.5 stop |
|
|
111 Set logging to DEBUG (FIXME) |
|
|
112 vim /usr/share/tomcat5.5/webapps/gnv/WEB-INF/classes/log4j.properties |
|
|
113 /etc/init.d/tomcat5.5 start # wait until tomcat is up |
|
|
114 tail -f -n 50 /usr/share/tomcat5.5/logs/gnv.log |
|
|
115 \end{lstlisting} |
|
|
116 |
|
|
117 It is recommended to undo the logging configuration, after the relevant |
|
|
118 part has been found. |
|
|
119 |
|
|
120 \section{Lists of References} |
|
|
121 FIXME |
|
|
122 |
|
|
123 FIXME: How to adapt the address/port of connection to REST-server.E |
