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 5: Using JBuilder with Borland servers 35
Configurations, partitions, partition services, and J2EE APIs
Borland Enterprise Server AppServer Edition 6.0, because each partition is a separate
process, an application’s functions can be distributed across multiple processes. For
either edition, when you use the Configure Servers dialog box to configure the server,
all these pieces are seamlessly set up for use in JBuilder.
For more information on the Borland Enterprise Server architecture, refer to the
documentation, available from the Help menu of the Borland Management Console.
In both editions, partitions provide containers and services for hosting your
applications. Any or all of a partition’s containers and services can be enabled or
disabled. Additionally, a partition can be cloned (copied) on the same configuration or
server or on another enterprise configuration or server located on the same local area
network. Cloning a partition can save significant time in the deployment process
because it not only copies all of the deployed modules, but also copies all the
associated service configurations settings which can require a considerable amount of
time and effort to complete.
Application components are hosted in either the web container or EJB container, or
simply in the partition itself (in the case of connectors). You can deploy application
EARs or smaller archives to partitions. The partitions are “smart” and will place your
application components in the proper containers. Since you may create as many
partitions as you wish, you can also have as many container instances as you wish.
Borland provides up to two different containers per partition instance:
■
Web container (Tomcat 4.x or 5.0): for hosting JSPs and servlets, and
■
EJB container (Borland): for hosting EJB components
Each partition also provides Partition Services and J2EE APIs as Partition Services.
These services and APIs are:
■
Naming Service: In Borland Enterprise Server, the Naming Service is managed by
the VisiBroker ORB.
■
JDataStore: Borland’s all-Java database.
■
JDBC: For getting connections to and modeling data from databases.
■
Java Mail: A Java email service.
■
JTA: The Java transactional API.
■
JAXP: The Java API for XML parsing.
■
JNDI: The Java Naming and Directory interface.
■
RMI-IIOP: Remote method invocation (RMI) carried out via internet inter-ORB
protocol (IIOP).
JBuilder, by default, uses a partition named
jbpartition and a configuration named
jbuilder as a deployment target for Borland Enterprise Server AppServer Edition 6.0.
For Borland Enterprise Server AppServer Edition 5.2.1, the partition name is
jbuilder.
If the configuration or partition doesn’t exist, one will be created for you automatically.
For both editions, the default partition shares the same port number with Tomcat and
JDataStore services. Additionally, in both editions, the server name is the same as the
machine identifier.
You can start multiple partitions using multiple JBuilder run configurations. To create
multiple run configurations, follow these steps:
1 Choose Run|Configurations, then click New.
2 Change the Run Type to Server. The displayed server is the server selected for the
project in Project Properties|Server.
3 In the Category tree, select Server|Command Line.