|
|
|
|
Yes, except in those countries that are subject to U.S. export controls
such as Iran, Iraq, Libya, Syria, Sudan, North Korea, and Cuba.
Another version of Enterprise Ready Server is available, Enterprise Ready Server Version
2.0, that supports Windows 2000 and NT. All other features and specs are
essentially the same as Enterprise Ready Server Version 2.1.
You have the option to install Apache JServ or Jakarta Tomcat when you install
the Enterprise Ready Server. Apache JServ contains the JavaServer Development
Kit and Apache's Java Servlet engine. Jakarta Tomcat includes the Sun Java
2 Standard edition (J2SE). Install either one of these modules and your
Web server is Java ready.
JServ is the Apache Group's initial implementation of a Java servlet engine,
and Tomcat is the second, enhanced version.
| JServ |
Tomcat |
| Servlet API 2.0 |
yes |
|
| Servlet API 2.2 |
|
yes |
| Written in Java for portability |
yes |
yes |
| Operates separate from server for stability |
yes |
yes |
| Integrated load balancing |
yes |
yes |
| Servlets may be separated into different
logical containers to ease administration |
yes |
yes |
| MD5 based connection authentication |
yes |
yes |
| Java server pages |
As ext modules |
1.1 |
| Works with Apache 1.3.x |
yes |
yes |
| Works with Apache 2.x |
|
yes |
If you want to run JavaServer Pages or servlets on your Web site, you need
a servlet engine.
The DAV module implements the standard WebDAV protocol, allowing distributed
Web authoring tools to interact with the Apache Web server. If your company
is an ISP, and you would like to give your customers a way to update the
content on their site without giving them access to your server, DAV is
a structured way to manage content through the Web server, rather than the
standard FTP protocol to upload and download files.
Mod_perl (written by a Covalent employee) is one of the most widely used
languages for CGI scripts. Mod_perl improves the performance of Perl CGIs,
allowing Perl programmers to enhance the Apache Web server by making it
possible for Apache to understand modules written in Perl.
Covalent Enterprise Ready Server provides PHP with MySQL support. Contact Covalent
Support if you require further details.
Transport Layer Security (TLS) is the third incarnation of Secure Socket
Layer (SSL) protocol. Since Covalent SSL supports both SSL and TLS, you
can support a wider variety of secure connections.
Yes, but the module's value is that it provides ease of management, installation,
and support, and is compatible with hardware accelerators from Rainbow and
nCipher.
Yes. The Covalent SSL module supports the use of Global Server IDs (GSID),
which upgrade standard 40-bit browsers to use full 128-bit security. GSID
server certificates are issued to those organizations which meet U.S. government
criteria.
Yes, a Certificate Authority (CA) is a trusted third party that certifies
specific claims about public keys.
No. Well-established companies such as VeriSign, Equifax, Thawte, GTE Cybertrust,
and Entrust are regarded as the most commonly trusted CAs. If your certificate
is signed by a relatively unknown company, such as "Joe's Trucking," your
customers may not trust your Web site's reliability.
Yes, usually. Browsers verify that the server name in the server's digital
certificate matches the server name in the URL being accessed. If they do
not match, it may indicate a security problem, so the browser will warn
the user.
Some Web hosting sites have worked around this by getting one certificate
for the main site, and serving all secure Web pages from that site. In most
cases, this is harmless; however, it may be disconcerting to users who are
expecting a secure transaction with one site, but are presented with a certificate
for a different site.
So if you want to use virtual hosts with Covalent SSL, it's best to have
a certificate for each virtual host serving secure pages. Covalent SSL fully
supports per-virtual-host certificates.
While your digital certificate can be issued by any Certificate Authority
(CA), most Web browsers contain a list of trusted CAs, such as VeriSign
or GTE CyberTrust. For example, if viewers go to a Web site that has a certificate
issued by "Slick Rick's Speedy Certificate Authority," they will be asked
if they wish to accept that CA as valid. Not knowing who Slick Rick is,
they may decline.
Use the Covalent SSL Certificate and Key Management Tool to generate a Certificate
Signing Request (CSR). Submit the CSR to the CA of your choice for signing.
Covalent SSL supports almost all CAs, and has relationships with VeriSign,
Thawte, Entrust, and Equifax.
Yes. Covalent SSL provides 168-bit encryption, and is compatible with both SSL
and TLS (Transport Layer Security, the third incarnation of Secure Socket Layer
(SSL) protocol), in order to support a wider variety of secure connections.
Both. Covalent Enterprise FTP Server supports encryption of user IDs, passwords,
and FTP commands as well as the data that is being transferred.
ERS FTP provides two methods of implementing SSL: Implicit SSL and Explicit
SSL. The decision to use Implicit SSL or Explicit SSL is a policy choice dictated
by the enterprise. ERS FTP provides support for both.
Administrators select Implicit SSL if they require FTP clients to be "SSL
enabled." With Implicit SSL, the socket is setup immediately for secure communication
and no clear text is passed between the client and server. These servers usually
run on port 990. With this mode of operation, only clients that support SSL will
be permitted access. Also no AUTH command is needed when using Implicit SSL, since
all control and data connections are secure.
Administrators implement Explicit SSL when they want to provide access to a mixture
of FTP clients. With Explicit SSL, the user connects like standard FTP (i.e.,
without any security required). When a user requests sensitive data, the server
can then require the client to upgrade to a secure connection. The advantage of
Explicit SSL is that SSL is not required of the client, so older clients will
be able to access the server.
With bandwidth management and data flow control, FTP is the most efficient and
reliable protocol to transfer large files over a TCP/IP network. FTP is simple
to implement, reliable, and commonly available.
Covalent Enterprise FTP Server takes advantage of the filtering capabilities of
Apache 2.0 to enable FTP to be used with SSL. Both FTP and SSL are simply modules
within the Apache 2.0 framework, and the ability of Apache 2.0 to cascade filters
allows FTP to incorporate SSL. This enables IDs and passwords to be encrypted,
as well as encryption of the transmitted data itself. And since SSL supports digital
certificates, so, then, does FTP. Along the same lines, you can enforce client
authorization on a per request basis.
Securing FTP transmissions have typically involved cumbersome workarounds that
increase infrastructure complexity. Because Covalent Enterprise FTP is incorporated
within the same Apache server that is serving HTTP, workarounds and FTP-dedicated
infrastructure elements can be eliminated.
And because Covalent Enterprise FTP is incorporated within the same Apache server
that is serving HTTP, the same configuration syntax can be shared for both FTP
and HTTP, for example the same LDAP directory can be used to authentication users
requesting Web pages and files.
It can take advantage of the performance-tuning capabilities of the underlying
Apache 2.0 structure. You can choose the balance between performance and scalability
by picking the desired Apache processing module (pre-fork, threaded, hybrid).
Requests are handled from a pool of workers instead of starting a process for
each request.
The clients in the following list have been tested by Covalent. Please check back
periodically for updates.
|
|
|
|
Apache Geronimo, now a fully certified J2EE platform, is competitive with other J2EE application servers and should be considered by customers when choosing a J2EE solution...This move by Covalent is comforting and promising. Expert commercial support is extremely important to the future of the Geronimo platform.
Richard Monson-Haefel
Senior Analyst, The Burton Group and co-founder of the Apache Geronimo project
|
|
|
