Next Previous Contents

1. Introduction

1.1 Background

This document was started January, 1999 by Gary Meyer ( [email protected]) after several weeks of installing various open source and proprietary Enterprise Java products for Linux. "Enterprise Java" is defined as using the Java Enterprise APIs.

1.2 Audience

This HOWTO is intended to benefit software professionals who are interested in evaluating, developing, or deploying Enterprise Java on Linux. Limited knowledge or experience in either Linux or Java is assumed.

1.3 New Versions

The newest version of this document can be found at the author's website at http://24.8.19.113/ej4linux.html.

1.4 Copyrights and License

Copyright (c) 1999 Gary Meyer.

This document may be distributed only subject to the terms and conditions set forth in the LDP License at http://www.linuxdoc.org/COPYRIGHT.html. This document must not be distributed in modified form without the author's consent.

1.5 Disclaimers

The suggestions in this document are provided to help you get a Enterprise Java environment on Linux up and running as quickly as possible. The suggestions are not product recommendations or endorsements. As you become familiar with the options available, you can do you own product evaluations and determine what options are best for your particular purpose.

For the purpose of this HOWTO, "Enterprise Java" is defined as using the Java Enterprise APIs. This HOWTO does not address scalability, availability, manageability, and other such aspects of software that are often associated with the word "enterprise."

1.6 Potential Future Sections

This HOW has focused on the most popular aspects of Enterprise Java. The following sections may be added to this HOWTO.

Interested in authoring a section?

Please contact the author, Gary Meyer, at ( [email protected]).

1.7 Other Resources

The App-Serv Center website at http://www.app-serv.com/.

Java Enterprise in a Nutshell by David Flanagan et al at http://www.oreilly.com/catalog/jentnut/.

1.8 Feedback

Please submit all additions and corrections to the author, Gary Meyer, at ( [email protected]).


Next Previous Contents