aboutsummaryrefslogtreecommitdiffstats
blob: 8c7dc2d52bfededf815c900b4ed473db29f4a7fa (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
<?xml version="1.0"?>
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
    "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
<chapter id="installing.greenpages">
  <title>Installing and exploring @greenpages@</title>
    <titleabbrev>Installing @greenpages@</titleabbrev>
  <section id="installing.greenpages.introduction">
    <title>Introduction</title>
    <para>@greenpages@ is a simple application that allows users to search an online email address directory. Each listing
    in the directory details the relevant email addresses and the name of the owner. @greenpages@ has only three screens:
    the search screen, the results screen and the listing detail screen.</para>
    <para>In the search screen, users can enter search criteria to be matched against the listings in the directory.
    The result screen displays any listings that match the criteria entered by the user. The listing detail screen
    shows all the data known about a given listing.</para>
    <para>Despite its simplicity, @greenpages@ is designed to demonstrate many different @webserv@ features and to
    act as a template from which other modular applications can be built. In particular, @greenpages@ demonstrates: 
    <itemizedlist mark="bullet">
      <listitem><para>module dependencies with <literal>Import-Package</literal>,</para></listitem>
      <listitem><para>load-time weaving with JPA and AspectJ,</para></listitem>
      <listitem><para>bundle classpath scanning, and</para></listitem>
      <listitem><para>service export, lookup and injection.</para></listitem>
    </itemizedlist></para>
    <para>In addition to demonstrating common @webserv@ features, @greenpages@ demonstrates integration with:
    <itemizedlist mark="bullet">
      <listitem><para>Spring Framework 3.0;</para></listitem>
      <listitem><para>FreeMarker 2.3;</para></listitem>
      <listitem><para>EclipseLink 1.0.0;</para></listitem>
      <listitem><para>H2 1.0.71; and</para></listitem>
      <listitem><para>Commons DBCP 1.2.2.</para></listitem>
    </itemizedlist>
    </para>
	<para>The @greenpages@ application is packaged as a PAR file containing four modules.
       <mediaobject>
         <imageobject role="fo">
          <imagedata fileref="images/installing-greenpages/greenpages.png" format="PNG" align="center" width="11cm"/>
        </imageobject>
        <imageobject role="html">
          <imagedata fileref="images/installing-greenpages/greenpages.png" format="PNG" align="center" width="13cm"/>
        </imageobject>
       </mediaobject>
    </para>
    <para>
        The <literal>greenpages.db</literal> module provides access to an external database and publishes a
		<literal>javax.sql.DataSource</literal> service.
    </para>
    <para>
		The <literal>greenpages.app</literal> module exports a <literal>greenpages</literal> package containing
		<literal>Directory</literal> and <literal>Listing</literal> interfaces.
    </para>
    <para>
		The <literal>greenpages.jpa</literal> module imports the <literal>greenpages</literal> package and
		uses the <literal>javax.sql.DataSource</literal> service to
		access the external database and publishes its contents as a <literal>greenpages.Directory</literal> service.
    </para>
    <para>
		The <literal>greenpages.web</literal> module imports the <literal>greenpages</literal> package and uses the
		<literal>greenpages.Directory</literal> service to respond to web requests.
    </para>
  </section>
  
  <section id="installing.greenpages.obtaining">
    <title>Obtaining @greenpages@</title>
    <para>This document provides instructions for building the complete @greenpages@ application and running it in @webserv@ as well as running tests and executing it from the @sts@. 
    In addition, the application is examined in development stages from @sts@, stepping through the development process and comparing this to the solution.
    </para>
<para>To get the completed @greenpages@ application, including tests and explanatory skeleton parts:
    <orderedlist>
      <listitem>
        <para>download the latest ZIP file from <programlisting>@greenpages.download.url@</programlisting></para>
      </listitem>
      <listitem>
        <para>extract all the files from the ZIP file to a convenient directory (preserving the directory structure).</para>
      </listitem>
    </orderedlist>
</para>
<para>To extract the files on Windows:
<programlisting>prompt> mkdir c:\springsource\samples
prompt> cd c:\springsource\samples
prompt> jar xf c:\path\to\@greenpages.zip.file@
prompt> set GREENPAGES_HOME=c:\springsource\samples\@greenpages.expanded.dir@</programlisting>
</para>
<para>To extract the files on Unix systems:
<programlisting>prompt$ mkdir -p /opt/springsource/samples 
prompt$ cd /opt/springsource/samples 
prompt$ unzip /path/to/@greenpages.zip.file@ 
prompt$ export GREENPAGES_HOME=/opt/springsource/samples/@greenpages.expanded.dir@
</programlisting>
</para>
<para>The environment variable <literal>GREENPAGES_HOME</literal> set here is not used by the projects, but is used as a shorthand
    in the instructions that follow.
</para>
<para>The @greenpages@ zip file contains two main directories called <literal>solution</literal> and <literal>start</literal>.
    The <literal>solution</literal> directory contains the completed application which can be built and tested (as described in the next section).
    The <literal>start</literal> directory contains an initial skeleton of the @greenpages@ application which can be used to generate the full application.
    The examination steps refer to this skeleton by way of illustration.
</para>
<para>To follow the examination steps read <xref linkend="web.module"/> <emphasis>after</emphasis> installing the full application in the following section.
</para>
  </section>

  <section id="installing.greenpages.building">
    <title>Building and installing @greenpages@</title>
    <section id="installing.greenpages.building.mvn">
      <title>Building with @maven.full@</title>
<para>@greenpages@ uses @maven.full@ as its primary build system. Each module of the application can be built
    separately and the entire application can built and assembled into a PAR file from a single location.
    To build the application and assemble it into a PAR
    file:
  <orderedlist>
    <listitem>
        <para>Make <code>$GREENPAGES_HOME/solution</code> the current directory.</para>
    </listitem>
    <listitem>
        <para>Run the command
        <code>mvn package</code>. The first time this is run several files will be downloaded
        from @maven@ repositories and @s2@ repositories. Subsequent runs will not need to do this.
        </para>
    </listitem>
    <listitem>
        <para>Verify that the 
        <code>greenpages-@app.version@.par</code> file exists in 
        <code>$GREENPAGES_HOME/solution/greenpages/target</code>.
        </para>
    </listitem>
  </orderedlist>
</para>
</section>

<section id="installing.greenpages.building.par.provided">
      <title>Installing dependencies into @webserv@</title>
      <para>
      Unlike traditional Java EE applications, @greenpages@ does not package all of its dependencies inside its
      deployment unit. Instead, it relies on the mechanisms of OSGi to locate its dependencies at runtime.
      When running an OSGi application on @webserv@, these dependencies can be loaded into memory as needed, but first they
      must be made available to @webserv@.
      </para>
      <para>The Maven build included with @greenpages@ uses the <code>dependency:copy-dependencies</code> plugin to gather 
            all the artifacts that @greenpages@ depends on that are not supplied by the @webserv@ runtime. These dependencies 
            can then be installed into the @webserv@ repository. Dependencies are gathered automatically during the
			<code>package</code> phase. These dependencies can be found in
			<literal>$GREENPAGES_HOME/solution/greenpages/target/par-provided</literal>. To install dependencies
            simply copy all the <code>*.jar</code> files from this directory into <literal>$VWS_HOME/repository/usr</literal>.
      </para>

<para>Installing dependencies on Windows:
<programlisting>prompt> cd %GREENPAGES_HOME%\solution\greenpages 
prompt> copy target\par-provided\* %VWS_HOME%\repository\usr
</programlisting>
</para>

<para>Installing Dependencies on UNIX:
<programlisting>prompt$ cd $GREENPAGES_HOME/solution/greenpages 
prompt$ cp target/par-provided/* $VWS_HOME/repository/usr
</programlisting>
</para>
<para>
  Notice that @webserv@ will not necessarily see these dependencies unless its repository indexes are rebuilt.
  Different repositories behave differently in this respect; some are passive (their indexes are built only once upon startup)
  and some are active (they can detect new files or files being removed dynamically).
  The <literal>usr</literal> repository is active so there is no
  need to restart @webserv@ when copying these files.
  The next time @webserv@ is started the <literal>-clean</literal> option will cause @webserv@ to re-scan the repository directories in any case.
  It is always safe to start @webserv@ with the <literal>-clean</literal> option.
</para>
</section>

<section id="installing.greenpages.building.db">
      <title>Starting and configuring the database</title>
<para>@greenpages@ uses the H2 database to store all its data. Before you can start the application, you must start the database server and populate the database with data.</para>
          <orderedlist>
              <listitem><para>Change to the <code>$GREENPAGES_HOME/db</code> current directory.  On Unix:</para>
		<programlisting>prompt$ cd $GREENPAGES_HOME/db</programlisting>
		<para>On Windows:</para>
		<programlisting>prompt> cd %GREENPAGES_HOME%\db</programlisting>
              </listitem>
              <listitem><para>Run the database startup script appropriate to the operating system.  For Unix, this is <literal>run.sh</literal>, run in the background:</para>
		<programlisting>prompt$ sh run.sh &amp;</programlisting>
		<para>Press Return to continue.</para>
		<para>On Windows, run the <literal>run.bat</literal> command:</para>
		<programlisting>prompt> run</programlisting>
		<para>For both platforms, the command might invoke a browser window offering a connection to the database; close this window.</para>
              </listitem>
              <listitem><para>Run the data population script appropriate to the operating system.  For Unix, this is <literal>data.sh</literal>:</para>
		<programlisting>prompt$ sh data.sh</programlisting>
		<para>On Windows, run the <literal>data.bat</literal> command:</para>
		<programlisting>prompt> data</programlisting>
              </listitem>
          </orderedlist>

<para>
You only to need run these commands once to start a database server for H2; the server will continue to run in the background. 
</para>
</section>

<section id="installing.greenpages.building.par">
      <title>Installing and starting @greenpages@ PAR</title>

<para>To install the @greenpages@ PAR into @webserv@ and start it:
          <orderedlist>
              <listitem><para>Copy the @greenpages@ PAR  to the <code>$VWS_HOME/pickup</code> directory.  On Unix:</para>
		<programlisting>prompt$ cd $VWS_HOME
prompt$ cp $GREENPAGES_HOME/solution/greenpages/target/greenpages-solution-@app.version@.par pickup/</programlisting>
		<para>On Windows:</para>
		<programlisting>prompt> cd %VWS_HOME%
prompt> copy %GREENPAGES_HOME%\solution\greenpages\target\greenpages-solution-@app.version@.par pickup\</programlisting>
              </listitem>
              <listitem><para>Start @webserv@ with the <literal>-clean</literal> option.  On Unix:</para>
              <programlisting>prompt$ $VWS_HOME/bin/startup.sh -clean</programlisting> 
	      <para>On Windows:</para>
              <programlisting>prompt> "%VWS_HOME%"\bin\startup.bat -clean</programlisting> 
              </listitem>
              <listitem>
<para>Verify that @greenpages@ starts correctly by checking in the @webserv@ output for the log message:
<programlisting>&lt;DE0005I&gt; Started par 'greenpages' version '@app.version@'. </programlisting>
</para>
              </listitem>
          </orderedlist>
</para>

</section>

</section>

<section id="installing.greenpages.browsing">
      <title>Browsing the @greenpages@ application</title>
      <para>
          Once installed and started, the @greenpages@ 
          application can be accessed with a web browser using the address 
          <ulink url="http://localhost:8080/greenpages">http://localhost:8080/greenpages</ulink>.
      </para>
<para>
    From the home page, a search query can be entered into the search box:
    <mediaobject>
        <imageobject role="fo">
            <imagedata fileref="images/installing-greenpages/browse-1.png" format="PNG" align="center" width="12cm"/>
        </imageobject>
        <imageobject role="html">
            <imagedata fileref="images/installing-greenpages/browse-1.png" format="PNG" align="center"/>
        </imageobject>
    </mediaobject>
</para>

<para>
    After entering a query into the search box, the results page shows all the matches from the 
    directory:
    <mediaobject>
        <imageobject role="fo">
            <imagedata fileref="images/installing-greenpages/browse-2.png" format="PNG" align="center" width="12cm"/>
        </imageobject>
        <imageobject role="html">
            <imagedata fileref="images/installing-greenpages/browse-2.png" format="PNG" align="center"/>
        </imageobject>
    </mediaobject>
</para>

<para>
    Clicking on <emphasis>view</emphasis> next to an entry in the search listing displays the full details for that 
    listing entry:
    <mediaobject>
        <imageobject role="fo">
            <imagedata fileref="images/installing-greenpages/browse-3.png" format="PNG" align="center" width="12cm"/>
        </imageobject>
        <imageobject role="html">
            <imagedata fileref="images/installing-greenpages/browse-3.png" format="PNG" align="center"/>
        </imageobject>
    </mediaobject>
</para>
</section>

<section id="installing.greenpages.tools">
    <title>Running @greenpages@ from Eclipse</title>
    <para>Using Eclipse and the @webserv@ tools, it is possible to run applications directly from the IDE. 
      As changes are made to the application in the IDE,
      they can be automatically applied to the running application allowing for rapid feedback of changes in function.
    </para>

    <section id="installing.greenpages.tools.importing">
        <title>Importing the @greenpages@ projects into Eclipse</title>
        <para>
            Before you can start the @greenpages@ application from Eclipse, you must import the projects. To import the projects into Eclipse:
            <orderedlist>
                <listitem>
<para>Open the Import Wizard using 
    <menuchoice><guimenu>File</guimenu><guimenuitem>Import</guimenuitem></menuchoice>.
</para>
                  </listitem>
                  <listitem>
<para>From the Import Wizard select 
    <menuchoice><guimenu>General</guimenu><guimenuitem>Existing Projects into Workspace</guimenuitem></menuchoice>
and click <emphasis>Next</emphasis>:
    <mediaobject>
        <imageobject role="fo">
            <imagedata fileref="images/installing-greenpages/import-projects2.png" format="PNG" align="center" width="8cm"/>
        </imageobject>
        <imageobject role="html">
            <imagedata fileref="images/installing-greenpages/import-projects2.png" format="PNG" align="center"/>
        </imageobject>
    </mediaobject>
</para>
</listitem>
                  <listitem>
<para>Click <guibutton>Browse…</guibutton> and select <code>$GREENPAGES_HOME/solution</code> as the root directory.</para>
                  </listitem>
                  <listitem>
<para>In the <emphasis>Import Projects</emphasis> window, select all the projects and click <emphasis>Finish</emphasis>:
    <mediaobject>
        <imageobject role="fo">
            <imagedata fileref="images/installing-greenpages/import-projects3.png" format="PNG" align="center" width="15cm"/>
        </imageobject>
        <imageobject role="html">
            <imagedata fileref="images/installing-greenpages/import-projects3.png" format="PNG" align="center"/>
        </imageobject>
    </mediaobject>
</para>
                  </listitem>
                  <listitem>
<para>Validate that the imported projects appear in Package Explorer:

    <mediaobject>
        <imageobject role="fo">
            <imagedata fileref="images/installing-greenpages/import-projects4.png" format="PNG" align="center" width="5cm"/>
        </imageobject>
        <imageobject role="html">
            <imagedata fileref="images/installing-greenpages/import-projects4.png" format="PNG" align="center"/>
        </imageobject>
    </mediaobject>
    
There may be compilation errors at this stage.
</para>
                  </listitem>
              </orderedlist>
          </para>
      </section>
      
      <section id="installing.greenpages.tools.configuring">
          <title>Configuring @webserv@ target runtime</title>
          <para>
              Projects for @webserv@ are associated with a @virgo@ @webserv@ runtime environment in Eclipse. This is to allow
              launching and testing from within Eclipse, and also to allow classpath construction in Eclipse to
              mirror the dynamic classpath in the @webserv@ runtime.
          </para>
          <para>
            Compilation errors in the previous step will be resolved here.
          </para>
          <para>
              To configure a @webserv@ runtime environment:
          </para>
          <orderedlist>
              <listitem>
                  <para>Open <menuchoice><guimenu>Window</guimenu><guisubmenu>Show View</guisubmenu><guimenuitem>Other…</guimenuitem></menuchoice>.</para>
              </listitem> 
              <listitem>
<para>In the <emphasis>Show View</emphasis> dialog choose 
<menuchoice><guimenu>Server</guimenu><guimenuitem>Servers</guimenuitem></menuchoice> to make the servers view visible:
    <mediaobject>
        <imageobject role="fo">
            <imagedata fileref="images/installing-greenpages/servers.png" format="PNG" align="center" width="6cm"/>
        </imageobject>
        <imageobject role="html">
            <imagedata fileref="images/installing-greenpages/servers.png" format="PNG" align="center"/>
        </imageobject>
    </mediaobject>
</para>
              </listitem>
              <listitem>
<para>Right-click in the <emphasis>Servers</emphasis> (which may not be empty) view and select 
    <menuchoice><guimenu>New</guimenu><guimenuitem>Server</guimenuitem></menuchoice>.
</para>
              </listitem>
              <listitem>
<para>In the <emphasis>New Server</emphasis> dialog, choose 
<menuchoice><guimenu>EclipseRT</guimenu><guimenuitem>Virgo Web Server</guimenuitem></menuchoice> 
    and click <emphasis>Next</emphasis>.
</para>
              </listitem>
              <listitem>
<para>Click <guibutton>Browse</guibutton> and select the <code>$VWS_HOME</code> directory. Ensure that a JRE is selected
supporting Java 1.6 or above.
Click <guibutton>Finish</guibutton> to complete creation of the server:
    <mediaobject>
        <imageobject role="fo">
            <imagedata fileref="images/installing-greenpages/new-server.png" format="PNG" align="center" width="9cm"/>
        </imageobject>
        <imageobject role="html">
            <imagedata fileref="images/installing-greenpages/new-server.png" format="PNG" align="center"/>
        </imageobject>
    </mediaobject>
</para>
              </listitem>
              <listitem>
<para>Select all projects (except <emphasis>Servers</emphasis>) in <emphasis>Package Explorer</emphasis>.
Right-click on the projects and choose <guimenuitem>Close Project</guimenuitem> 
and then <guimenuitem>Open Project</guimenuitem>.
</para>
              </listitem>
          </orderedlist>

<para>
It is possible that there remain spurious build errors from Eclipse (see the <emphasis>Problems</emphasis> view), in which case
a project clean build may clear the problems. Select <menuchoice><guimenu>Project</guimenu><guimenuitem>Clean…</guimenuitem></menuchoice>
from the main menu, and choose to <emphasis>Clean all projects</emphasis>.
It may be necessary to repeat this on a few projects.
(This process is sometimes known as the <quote>Eclipse dance</quote>.)
</para>
<para>
Despite the dance steps outlined, there will remain some <emphasis>Warnings</emphasis> like this:
<mediaobject>
    <imageobject role="fo">
        <imagedata fileref="images/installing-greenpages/problem-warning.png" format="PNG" align="center" width="14cm"/>
    </imageobject>
    <imageobject role="html">
        <imagedata fileref="images/installing-greenpages/problem-warning.png" format="PNG" align="center"/>
    </imageobject>
</mediaobject>
It is safe to ignore these.
</para>

</section>

<section id="installing.greenpages.tools.run">
          <title>Running @greenpages@ from within Eclipse</title>
          <para>
              Now that @greenpages@ is successfully imported into Eclipse, you can run the project directly from within the IDE. </para>
           <para>If you previously deployed the @greenpages@ PAR to @webserv@ by copying the PAR file to the <literal>pickup</literal> directory, be sure you now remove it so that it does not conflict with the deployment of the Eclipse project.  On Unix:</para>
	  <programlisting>prompt$ cd $VWS_HOME/pickup
prompt$ rm greenpages-solution-@app.version@.par</programlisting>
	
	  <para>On Windows:</para>
	  <programlisting>prompt> cd %VWS_HOME%\pickup
prompt> del greenpages-solution-@app.version@.par</programlisting>

	  <para>Also, to prevent conflicts with the server configured in Eclipse, stop a currently-running @webserv@ by typing <literal>Control-C</literal> in the console window from which you started the server.  </para>

          <para>
              To run @greenpages@ from within Eclipse:
              <orderedlist>
                  <listitem>
                      <para>
                      Right click on the @webserv@ instance in the <emphasis>Servers</emphasis> view and select the <menuchoice><guimenu>Add and Remove…</guimenu></menuchoice>
                      menu item.
<!--    <mediaobject>-->
<!--        <imageobject role="fo">-->
<!--            <imagedata fileref="images/installing-greenpages/addandremove.png" format="PNG" align="center" width="5cm"/>-->
<!--        </imageobject>-->
<!--        <imageobject role="html">-->
<!--            <imagedata fileref="images/installing-greenpages/addandremove.png" format="PNG" align="center"/>-->
<!--        </imageobject>-->
<!--    </mediaobject>-->
     <mediaobject>
        <imageobject role="fo">
            <imagedata fileref="images/installing-greenpages/addedtoserver.png" format="PNG" align="center" width="7cm"/>
        </imageobject>
        <imageobject role="html">
            <imagedata fileref="images/installing-greenpages/addedtoserver.png" format="PNG" align="center"/>
        </imageobject>
    </mediaobject>
    </para>
    </listitem>
    <listitem><para>
     Add <emphasis>greenpages-solution</emphasis> (which is the containing project or PAR) to the server and finish.
    </para></listitem>                     
                  <listitem>
                      <para>To start @webserv@ from within Eclipse right-click on the @webserv@ node in the Servers window and choose <guimenuitem>Start</guimenuitem>.
                      The <emphasis>Servers</emphasis> view should now show the server and the added project:
    <mediaobject>
        <imageobject role="fo">
            <imagedata fileref="images/installing-greenpages/installed.png" format="PNG" align="center" width="14cm"/>
        </imageobject>
        <imageobject role="html">
            <imagedata fileref="images/installing-greenpages/installed.png" format="PNG" align="center"/>
        </imageobject>
    </mediaobject>
                      </para>
                  </listitem>
                  <listitem>
                      <para>
                          Verify that @greenpages@ is started correctly by checking for 
                          <code>&lt;DE0005I&gt; Started par 'greenpages' version '@greenpages.version.number@'.</code> in the Console window.
    <mediaobject>
        <imageobject role="fo">
            <imagedata fileref="images/installing-greenpages/success.png" format="PNG" align="center" width="16cm"/>
        </imageobject>
        <imageobject role="html">
            <imagedata fileref="images/installing-greenpages/success.png" format="PNG" align="center"/>
        </imageobject>
    </mediaobject>
                      </para>
                  </listitem>
              </orderedlist>
          </para>
          <para>
          (<emphasis>If errors are shown implying that @greenpages@ failed to be installed, this may be because some dependencies were not
          copied to @webserv@, as described in section <xref linkend="installing.greenpages.building.par.provided"/>. Check this.</emphasis>)
          </para>
          
          <para>Once installed and started @greenpages@ is again available from a web browser at the address 
              <ulink url="http://localhost:8080/greenpages">http://localhost:8080/greenpages</ulink>.
          </para>
      </section>
  </section>

</chapter>