When web.xml is omitted, the operations for the Web applications with the server management commands are limited. The following table describes whether the operations can be executed for the Web applications when web.xml is omitted.

Table 11-12 Operability of the Web applications when web.xml is omitted

Operations				Operability
Commands	Arguments	Operations
cjaddapp	-type filter	Adding a filter		N#1
	-type war	Adding a WAR file		Y
cjcopyres	-type war	Copying a WAR file		Y
cjdeleteapp	-type filter	Deleting a filter		N#2
	-type war	Deleting a WAR file		Y
	None	Deleting an application		Y
cjdeleteres	-type war	Deleting a WAR file		Y
cjexportapp	-raw	Exporting applications (not containing runtime information)		Y#3
	-normal	Exporting applications (containing runtime information)		Y#3
cjgetappprop	-type war	Obtaining the WAR file attributes		Y
	-type all	Obtaining the application attributes		Y
cjgetresprop	-type war	Obtaining the WAR file attributes		Y
cjimportapp		Importing a J2EE application		Y#4
cjimportres	-type war	Importing a WAR file		Y#4
cjlistapp	-type war	Displaying the list of WAR files		Y
cjlistres	-type war	Displaying the list of WAR files		Y
cjreloadapp		Reloading an application		Y
cjreplaceapp	-replaceDD	Replacing an application (DD definition is not inherited)		Y
	None	Replacing an application (DD definition is inherited)		Y
cjsetappprop	-type war	Attribute settings	Information related to the default DD	N#5
			Runtime information	Y
	-type all	Attribute settings	Information related to the default DD	N#5
			Runtime information	Y
cjsetresprop	-type war	Attribute settings	Information related to the default DD	N#5
			Runtime information	Y
cjstartapp		Starting an application		Y
cjstopapp		Stopping an application		Y

Legend:

Y: Operations can be executed

N: Operations cannot be executed

#1: An error occurs during command execution and the message KDJE37606-E is output.

#2: A filter cannot be added in an application in which web.xml is omitted, therefore, the filter can also not be deleted.

#3: An exported file does not include web.xml.

#4: An imported WAR can only use the JSP and static contents.

#5: Handled as a read-only attribute, so the settings are ignored.