BEA WebLogic Server 7 ユーザーズマニュアル

BEA WebLogic Server 7.0 Upgrade Guide

Applications on J2EE-compliant servers such as WebLogic Server 7.0 are created and 
deployed as one of the following four types: Web Applications, Enterprise JavaBeans, 
Enterprise Archives, and client applications. To port your existing components to 
WebLogic Server 7.0, create the appropriate J2EE deployment units. For more 
information on J2EE deployment units, see 

 in Assembling and Configuring Web Applications. Web 

Applications are usually a collection of servlets, JSPs, and HTML files, packaged as 
WAR files. Enterprise JavaBeans (packaged as JAR files) are server-side Java 
components written according to the EJB specification. Enterprise Archives (EAR 
files) contain all of the JAR and WAR component archive files for an application and 
an XML descriptor that describes the bundled components. Client Applications are 
Java classes that connect to WebLogic Server through Remote Method Invocation 
(RMI). Later sections discuss the aforementioned J2EE deployment units in greater 
detail.

In order to convert an application to a Web Application and then port it into a Web 
Application deployed on WebLogic Server 7.0, the application’s files must be placed 
within a directory structure that follows a specific pattern. For development, these files 
can be left in an exploded directory format. However, for production situations, it is 
highly recommended that you bundle your applications into a WAR file as a single 
Web Application. For more information on Web Applications see 

.

The following sections provide information you need to know about porting and 
deploying Web Applications, including a procedure for porting a simple servlet from 
WebLogic Server 5.1 to WebLogic Server 7.0:

„