Home arrow Java arrow Page 4 - Getting Set with J2EE

Getting Set with J2EE

Before you can work with J2EE 1.4 SDK, you need to make sure it is set up correctly. This article, the first of two parts, will help you do that. The second part will take you through writing a simple application. It is excerpted from chapter two of the book Beginning J2EE 1.4 From Novice to Professional, written by James L. Weaver, Kevin Mukhar, and Jim Crume (Apress, 2005; ISBN: 1590593413).

Author Info:
By: Apress Publishing
Rating: 4 stars4 stars4 stars4 stars4 stars / 13
December 08, 2005
  1. · Getting Set with J2EE
  2. · Installing the J2EE 1.4 SDK
  3. · Starting the Database Server
  4. · Starting the J2EE Server

print this article

Getting Set with J2EE - Starting the J2EE Server
(Page 4 of 4 )

The next step to verifying that your installation is working correctly is to start the J2EE server. The server is launched from menus that are automatically created during installation, so choose the following option from the Start menu:

Start | All Programs | Sun Microsystems | J2EE 1.4 SDK | Start Default Domain

A command window should open with messages similar to the following, the last one prompting you to Press any key to continue as shown below:

Starting Domain domain1, please wait.
Log redirected to C:\Sun\AppServer\ domains\domain1\logs\server.log.
Domain domain1 started.
Press any key to continue . . .

At this point the J2EE server is started. Go ahead and press any key as requested, open a browser, and go to the following URL:


The web browser should display the default J2EE web page:

Pat yourself on the back for a job well done. Let's go shred a little code for a final test.

Problems and Solutions

Here is a possible problem you might come up against when running through the previous steps to test your J2EE 1.4 SDK installation:



The web browser reports "Page cannot be displayed" when trying to open the URL http://localhost:8080

Make certain that there weren't any errors reported when starting hte J2EE server.

If you see messages indicating that the server couldn't start because TCP ports were in use by other processes, you may either have another web server using port 8080, or have another instance of the J2EE server running.

Also, make certain that you've specified the port "8080" in the URL (this is the default port used by the J2EE server).


DISCLAIMER: The content provided in this article is not warranted or guaranteed by Developer Shed, Inc. The content provided is intended for entertainment and/or educational purposes in order to introduce to the reader key ideas, concepts, and/or product reviews. As such it is incumbent upon the reader to employ real-world tactics for security and implementation of best practices. We are not liable for any negative consequences that may result from implementing any information covered in our articles or tutorials. If this is a hardware review, it is not recommended to open and/or modify your hardware.

blog comments powered by Disqus

- Java Too Insecure, Says Microsoft Researcher
- Google Beats Oracle in Java Ruling
- Deploying Multiple Java Applets as One
- Deploying Java Applets
- Understanding Deployment Frameworks
- Database Programming in Java Using JDBC
- Extension Interfaces and SAX
- Entities, Handlers and SAX
- Advanced SAX
- Conversions and Java Print Streams
- Formatters and Java Print Streams
- Java Print Streams
- Wildcards, Arrays, and Generics in Java
- Wildcards and Generic Methods in Java
- Finishing the Project: Java Web Development ...

Watch our Tech Videos 
Dev Articles Forums 
 RSS  Articles
 RSS  Forums
 RSS  All Feeds
Write For Us 
Weekly Newsletter
Developer Updates  
Free Website Content 
Contact Us 
Site Map 
Privacy Policy 

Developer Shed Affiliates


© 2003-2019 by Developer Shed. All rights reserved. DS Cluster - Follow our Sitemap
Popular Web Development Topics
All Web Development Tutorials