Server User Manual
Table Of Contents
- Developing Applications for J2EE™ Servers
- Contents
- Ch 1: Introduction
- Ch 2: Programming for the Java 2 Platform, Enterprise Edition
- Ch 3: Creating applications with J2EE technologies
- Ch 4: Configuring the target server settings
- Ch 5: Using JBuilder with Borland servers
- Configuring Borland servers in JBuilder
- Making the ORB available to JBuilder
- Configurations, partitions, partition services, and J2EE APIs
- Starting the configuration or server
- Remote deploying
- Remote debugging
- Web module workarounds
- Displaying the Borland Management Console in JBuilder
- International issues
- Borland servers and JDataStore 7.0
- Ch 6: Using JBuilder’s CORBA tools
- Ch 7: Using JBuilder with BEA WebLogic servers
- Ch 8: Using JBuilder with IBM WebSphere servers
- Ch 9: Using JBuilder with JBoss servers
- Ch 10: Using JBuilder with Tomcat
- Ch 11: Editing J2EE deployment descriptors
- Ch 12: Integrating with Enterprise Information Systems
- Ch 13: Building J2EE modules
- J2EE modules
- Setting module build properties
- Adding custom file types
- Sample build scenarios
- EJB JAR without any bean classes
- EJB JAR with custom files
- EJB JAR without EJB designer XML descriptors
- WAR with custom descriptor(s) in the WEB-INF directory
- WAR without any classes
- WAR with custom class filters
- WAR with custom file types
- EAR with custom files
- RAR with classes and dependencies
- Application client module with classes and dependencies
- Improving module build performance
- Index
Chapter 4: Configuring the target server settings 23
The created libraries
The created libraries
When you configure the server settings, one or more libraries are created for you
automatically in your JBuilder home directory that contain all the application server files
you will need for enterprise bean development with the application server of your
choice. These are the libraries created for you, listed by application server:
Borland Enterprise Server 6.0.1
■
Borland Enterprise Server 6.0 Client: All JARs needed to run a client.
■
Borland Enterprise Server 6.0 Servlet: Used for web applications.
Borland Enterprise Server 5.2.1
■
Borland Enterprise Server 5.2.1 Client: All JARs needed to run a client.
■
Borland Enterprise Server 5.2.1 Servlet: Used for web applications.
WebLogic 8.1
■
WebLogic 8.1 Client: All JARs needed to run a client.
■
WebLogic 8.1 Deploy: JARs needed to run the WebLogic 8.1 deploy tool.
■
WebLogic 8.1 Servlet: Used for web applications.
WebLogic 7.x
■
WebLogic 7.x Client: All JARs needed to run a client.
■
WebLogic 7.x Deploy: JARs needed to run the WebLogic 7.x deploy tool.
■
WebLogic 7.x Servlet: Used for web applications.
WebSphere 5.x
■
WebSphere 5.x Client: JARs needed to run a client.
■
WebSphere Application Server 5.x Ext Dirs: JARs used during server startup.
■
WebSphere Application Server 5.x EJB Deploy: JARs used to compile enterprise
beans and create stubs.
■
WebSphere Application Server 5.x Servlet: Used for web applications.
WebSphere 4.0 Single Server
■
WebSphere AES 4.0 Client: JARs needed to run a client.
■
WebSphere AES 4.0 Ext Dirs: JARs used during server startup.
■
WebSphere AES 4.0 EjbDeploy: JARs used to compile enterprise beans and
create stubs.
■
WebSphere AES 4.0 SeAppInstaller: JARs used to run the WebSphere 4.0
deploy tool (SeAppInstaller).
■
WebSphere AES 4.0 Servlet: Used for web applications.
WebSphere 4.0 Advanced Edition
■
WebSphere AE 4.0 Client: JARs needed to run a client.
■
WebSphere AE 4.0 Ext Dirs: JARs used during server startup.
■
WebSphere AE 4.0 XmlConfig: JARs used to run the WebSphere 4.0 AE deploy
tool.
■
WebSphere AE 4.0 EjbDeploy: JARs used to compile enterprise beans can
create stubs.
■
WebSphere AE 4.0 Servlet: Used for web applications.