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

BEA WebLogic Server 7.0 Upgrade Guide

Developing WebLogic Server Applications. Note that if you are using JSPs and 
want them to compile at run time you must have the home and remote interfaces 
of the bean included in the classes directory of your WAR file.

3. Create the Enterprise Archive by executing a jar command like the following in 

the staging directory:

jar cvf myApp.ear *

4. Click on the Install Applications link under the Getting Started heading in the 

home page of the console and place the EAR file in the 

domain\applications

 

directory.  For more information on Enterprise Applications, see 

 in Developing WebLogic Server Applications.

WebLogic Server supports J2EE client applications, packaged in a JAR file with a 
standard XML deployment descriptor. Client applications in this context are clients 
that are not Web browsers. They are Java classes that connect to WebLogic Server 
using Remote Method Invocation (RMI). A Java client can access Enterprise 
JavaBeans, JDBC connections,  messaging, and other services using RMI. Client 
applications range from simple command line utilities that use standard I/O to highly 
interactive GUI applications built using the Java Swing/AWT classes.

To execute a WebLogic Server Java client, the client computer needs the 

weblogic_sp.jar

 file, the 

weblogic.jar

 file, the remote interfaces for any RMI 

classes and Enterprise Beans that are on WebLogic Server, as well as the client 
application classes. To simplify maintenance and deployment, it is a good idea to 
package a client-side application in a JAR file that can be added to the client's classpath 
along with the 

weblogic.jar

 and 

weblogic_sp.jar

 files. The 

weblogic.ClientDeployer

 command line utility is executed on the client computer 

to run a client application packaged to this specification. For more information about 
J2EE client applications, see 

Server Applications.