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
|
<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
<head>
<!--
Copyright (c) 2010, 2019 Oracle and/or its affiliates. All rights reserved.
This program and the accompanying materials are made available under the
terms of the Eclipse Public License v. 2.0, which is available at
http://www.eclipse.org/legal/epl-2.0.
This Source Code may also be made available under the following Secondary
Licenses when the conditions for such availability set forth in the
Eclipse Public License v. 2.0 are satisfied: GNU General Public License,
version 2 with the GNU Classpath Exception, which is available at
https://www.gnu.org/software/classpath/license.html.
SPDX-License-Identifier: EPL-2.0 OR GPL-2.0 WITH Classpath-exception-2.0
-->
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="Author" content="JavaSoftware">
<meta name="GENERATOR" content="Mozilla/4.61 [en] (WinNT; U) [Netscape]">
<title>ApacheJServ</title>
</head>
<body>
If you don't already have Apache web server and Apache JServ
module installed and running,
<br>you'll need to download them from the <a href="http://www.apache.org">Apache
Software Foundation</a> and install them. We
<br>were able to find binary versions of Apache web server for both the
Solaris and Windows NT
<br>operating systems, and Apache JServ 1.1.2 for Windows NT. However,
for Solaris,
<br>Apache JServ needed to be built from the source.
<p>(on Solaris)
<blockquote>Apache Web Server 1.3.9 (<a href="http://httpd.apache.org/dist/binaries/">binary</a>)
<br>Apache JServ 1.1.2 (built from <a href="http://java.apache.org/">source</a>)</blockquote>
(on NT)
<blockquote>Apache Web Server 1.3.14 (<a href="http://httpd.apache.org/dist/binaries/">binary</a>)
<br>Apache JServ 1.1.2 (<a href="http://java.apache.org/">binary</a>)</blockquote>
To run the JakartaMailServlet, you must add the Jakarta Mail and JavaBeans
Activation Framework
<br>jar files to the web server's system classpath. Apache JServ also requires
that the
<br>Java Servlet Development Kit 2.0 (<a href="http://java.sun.com/products/servlet/archive.html">JSDK2.0</a>)
is installed and also added to the web server's
<br>system classpath. JSDK2.0 is a reference implementation of the Servlet
API Specification Version 2.0.
<p>When running Apache JServ in automatic mode, add wrapper.classpath properties
for each
<br>of these jar files to the servlet engine's propeties file. The default
engine properties file is
<br>jserv.properties and is usually found in Apache JServ's 'conf' directory.
Wrapper properties
<br>are used to automatically start the servlet engine.
<p>(on Solaris)
<blockquote>wrapper.classpath=/files/java/lib/JSDK2.0/lib/jsdk.jar
<br>wrapper.classpath=/files/java/lib/jakartamail/jakarta.mail.jar
<br>wrapper.classpath=/files/java/lib/jaf/jakarta.activation.jar</blockquote>
(on NT)
<blockquote>wrapper.classpath=d:\java\lib\jsdk2.0\lib\jsdk.jar
<br>wrapper.classpath=d:\java\lib\jakartamail\jakarta.mail.jar
<br>wrapper.classpath=d:\java\lib\jaf\jakarta.activation.jar</blockquote>
When running Apache JServ in manual mode, add these jar files to the CLASSPATH
<br>environment variable (this is documented in the Jakarta Mail README file
and additional
<br>Windows NT information is provided <a href="classpath-NT.html">here</a>).
<p>Once this is done, restart the web server.
<br>
<p>Additional Notes
<blockquote>One thing to watch out for is how the web server is referenced
when using the
<br>JakartaMailServlet on this web server. It is important to use the
configured server
<br>name (i.e. the name assigned with the ServerName directive) in the
URL. If the
<br>configured server name includes a domain, it must be referenced including
the
<br>domain, even if the JakartaMail.html page can be accessed without it.
<p>For example, Apache is configured with the ServerName set to 'shadygrove'.
If the Jakarta Mail demo is referenced by:
<p> http://shadygrove.east/example/JakartaMail.html
<p>and the initail reference to the JakartaMailServlet being:
<p> http://shadygrove.east/example/JakartaMailServlet
<p>the user is successfully logged in. However, when an attempt is made
to access the INBOX, the user is instructed to login because there is no
current session. When this occurs, note that the URL referencing the JakartaMailServlet
no longer contains the domain originally used but the configured ServerName.
<p> http://shadygrove/example/JakartaMailServlet
<br>
<p>Also note that Apache JServ does not use a SecurityManager or enforce
any Java
<br>security policy.</blockquote>
</body>
</html>
|
