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
34 Developing Applications for J2EE Servers
Making the ORB available to JBuilder
Making the ORB available to JBuilder
You use the CORBA node of the Enterprise Setup dialog box (Enterprise|Enterprise
Setup) to set up the Borland Enterprise Server for use with VisiBroker. For Borland
Enterprise Server AppServer Editions 6.0 and 5.2.1, the server will create its own
VisiBroker configuration called “VisiBroker <server name and version>.” The default
VisiBroker configuration won’t be changed.
You also use this dialog box to set the VisiBroker Smart Agent port to a unique number.
All client/server communication takes through the Smart Agent port. To start the Smart
Agent from the Tools menu, check the Add The VisiBroker Smart Agent Item To The
Tools Menu option. This option is selected by default. The CORBA node of the
Enterprise Setup dialog box looks like this:
To make the ORB available to JBuilder, you must start the VisiBroker Smart Agent with
the Enterprise|VisiBroker Smart Agent command. This handles the initial bootstrap
issues such as how the client locates the naming service and so on.
For Borland Enterprise Server AppServer Edition 5.2.1/6.0: If you choose
Enterprise|Borland Enterprise Server Management Agent, the VisiBroker Smart Agent
is started as part of the process. When you are working with the Borland Enterprise
Server AppServer Edition 5.2.1/6.0, you must start the Borland Enterprise Server
Management Agent instead of the VisiBroker Smart Agent. If you don’t start it, it is
automatically started for you when you start the server within JBuilder. Note that
starting the server automatically might take longer because the server searches for any
running agents. The most efficient way to start the Management Agent is to start it
yourself.
For more information on setting up the ORB for use within JBuilder, see “Setting up
JBuilder for CORBA applications” on page 47.
Configurations, partitions, partition services, and J2EE APIs
The architecture of the Borland Enterprise Server AppServer Edition 6.0 and 5.2.1
varies significantly. The Borland Enterprise Server AppServer Edition 6.0 introduces
the concept of management hubs and configurations. A management hub, also known
as the server control unit, controls, by server (or machine identifier), one or more
configurations. A configuration, in turn, manages one or more running partitions, or
processes. A configuration is based on an XML configuration file that resides in the
configuration’s root directory. This file determines the order of partition startup. A
configuration can have multiple partitions. Because each partition is a separate
process, an application’s functions can be distributed across multiple processes.
In the Borland Enterprise Server AppServer Edition 5.2.1, a server, also a machine
identifier, manages a partition. A server can also have multiple partitions. And, as with