start the Application Server:
asadmin start-domain domain1
on Windows, you can choose
Programs→Sun Microsystems→J2EE 1.4 SDK→Start Default Server
stop the Application Server:
asadmin stop-domain domain1
on Windows, choose
Programs→Sun Microsystems→J2EE 1.4 SDK→Stop Default Server
Starting the Admin Console:
http://localhost:4848/asadmin/
Starting the deploytool Utility:
deploytool
Starting and Stopping the Derby Database Server:
asadmin start-database
asadmin stop-database
logs:
<J2EE_HOME>/domains/domain1/logs/server.log
<j2ee.home>/derby/db.log
Admin Console log viewer. To use the log viewer:
1. Select the Application Server node.
2. Select the Logging tab.
3. Click the Open Log Viewer button. The log viewer will open and display
the last 40 entries.
Using a Debugger
The Application Server supports the Java Platform Debugger Architecture
(JPDA). With JPDA, you can configure the Application Server to communicate
debugging information via a socket. In order to debug an application using a
debugger:
1. Enable debugging in the Application Server using the Admin Console as
follows:
a. Select the Application Server node.
b. Select the JVM Settings tab. The default debug options are set to:
-Xdebug -Xrunjdwp:transport=dt_socket,server=y,
suspend=n,address=1044
As you can see, the default debugger socket port is 1044. You can change
it to a port not in use by the Application Server or another service.
c. Check the Enabled box of the Debug field.
d. Click the Save button.
2. Stop the Application Server and then restart it.
3. Compile your Java source with the -g flag.
4. Package and deploy your application.
5. Start a debugger and connect to the debugger socket at the port you set
when you enabled debugging.
asadmin start-domain domain1
on Windows, you can choose
Programs→Sun Microsystems→J2EE 1.4 SDK→Start Default Server
stop the Application Server:
asadmin stop-domain domain1
on Windows, choose
Programs→Sun Microsystems→J2EE 1.4 SDK→Stop Default Server
Starting the Admin Console:
http://localhost:4848/asadmin/
Starting the deploytool Utility:
deploytool
Starting and Stopping the Derby Database Server:
asadmin start-database
asadmin stop-database
logs:
<J2EE_HOME>/domains/domain1/logs/server.log
<j2ee.home>/derby/db.log
Admin Console log viewer. To use the log viewer:
1. Select the Application Server node.
2. Select the Logging tab.
3. Click the Open Log Viewer button. The log viewer will open and display
the last 40 entries.
Using a Debugger
The Application Server supports the Java Platform Debugger Architecture
(JPDA). With JPDA, you can configure the Application Server to communicate
debugging information via a socket. In order to debug an application using a
debugger:
1. Enable debugging in the Application Server using the Admin Console as
follows:
a. Select the Application Server node.
b. Select the JVM Settings tab. The default debug options are set to:
-Xdebug -Xrunjdwp:transport=dt_socket,server=y,
suspend=n,address=1044
As you can see, the default debugger socket port is 1044. You can change
it to a port not in use by the Application Server or another service.
c. Check the Enabled box of the Debug field.
d. Click the Save button.
2. Stop the Application Server and then restart it.
3. Compile your Java source with the -g flag.
4. Package and deploy your application.
5. Start a debugger and connect to the debugger socket at the port you set
when you enabled debugging.