After finishing the definition of properties and operations required for J2EE applications, you can execute the J2EE applications.

The following table provides an overview of the execution of J2EE applications:

Table 10-1 Overview of the execution of J2EE applications

Settings	Contents	J2EE application format		Reference
		Archive format	Exploded archive format
Starting and stopping J2EE applications	Start J2EE applications normally or by compiling JSP. Stop J2EE applications normally or by forced termination.	Y	Y	Section 10.2
Referencing the list of J2EE applications	Reference the list of imported applications.	Y	Y	Section 10.3
Deleting J2EE applications	Delete J2EE applications.	Y	R#1	Section 10.4
Switching between J2EE applications	Switch the following J2EE applications on the J2EE server: Applications in the archive format Applications in the exploded archive format	R#2	R#2	Section 10.5
Changing the J2EE application name	Change the name of a J2EE application.	Y	Y	Section 10.6
Acquiring the RMI-IIOP stubs and interfaces	Acquire RMI-IIOP stubs and interfaces of J2EE applications.	Y	Y	Section 10.7
Referencing the list of transactions	Reference a list of transaction information. When a J2EE server is running, transaction information like the operation state and the time elapsed since starting the server is displayed. When a J2EE server is being stopped, the state of an unprocessed transaction pending in the status file is displayed.	Y	Y	Section 10.8

Legend:

Y: Can be executed

R: Restricted execution

#1

You cannot delete a component from the application.

Note that filter addition can be executed because filter addition is a change in the application attributes.

#2

Use the following commands to switch between J2EE applications:

• The cjreplaceapp command for the archive format
• The cjreloadapp command for the exploded archive format