Installation guide

HTTP directory browsing
26 EAServer
Undeployment of packages, Web applications, and applications
When deleting a package, Web application, or application, you can choose
whether to delete only the entity’s properties file, or to delete all files that have
been generated by the deployment of the entity, including component stubs and
skeletons and IDL interface and datatype definitions. By default, EAServer
Manager performs a full deletion. In earlier EAServer versions, only properties
files were deleted. When deleting with
jagtool, add the type option to the delete
command to specify whether to use full or simple deletion
This feature is useful for deleting entities that have been imported from a J2EE
archive file. Full deletion makes removing the entity as easily as the original
deployment.
HTTP directory browsing
EAServer 5.0 includes built-in support for HTTP directory browsing. When a
Web client submits a request that ends in a directory name, and the directory
does not contain a Welcome file, EAServer returns a listing for the directory.
You can configure which directories can be browsed. For more information on
this feature, see “HTTP Directory Browsing” in Chapter 3, “Creating and
Configuring Servers,” in the EAServer System Administration Guide.
EAServer Transaction Manager
EAServer 5.0 includes the EAServer Transaction Manager, which supports the
specifications for the Java Transaction API (JTA) 1.0, and complies with the
JTS and the Object Transaction Service (OTS) and X/Open Architecture (XA)
standards. The JTS transaction coordinator integrates the functionality of
shared connections, OTS/XA, and JTS/JTA transaction modes, and uses two-
phase commit to coordinate transactions among multiple databases.
The EAServer Transaction Manager includes:
• Resource recovery and transaction logging
• Transaction interoperability
• Resource manager