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
38 Developing Applications for J2EE Servers
Starting the configuration or server
Starting the configuration or server
Before any server related actions (server startup, deployment, and so on) are
performed, you must start the management agent with Enterprise|Borland Enterprise
Server Management Agent (use the version of this command that matches the version
of the Borland Enterprise Server AppServer Edition your project is targeted for.). For
the Borland Enterprise Server 6.0, this will start the management hub. For Borland
Enterprise Server 5.2.1, this starts the server.
For both editions, after the management agent has started up, you can launch the
partition by right-clicking the EJB or web module in the project pane and selecting Run
Using Defaults. You can also create a Server run configuration and run the project
using that configuration.
Running the partition in JBuilder will
■
Create the partition (and configuration for Borland Enterprise Server 6.0), if not
already present. The partition name (and the configuration name for Borland
Enterprise Server 6.0) used in this step is derived from the run configuration used to
start up the server. If you are starting the configuration or server using the default
configuration, the partition name as configured in the application server properties
will be used.
■
Deploy any resources defined in jndi-definitions.xml (if present) to the root of the
partition directory. For the Borland Enterprise Server AppServer Edition 6.0, this
directory is:
PARTITION_NAME\dars\jbuilder.dar. For Borland Enterprise Server 6.0
only, the
jndi-definitions.xml file is packaged into a .dar file and deployed. For the
Borland Enterprise Server AppServer Edition 5.2.1, it is:
APPSERVER_HOME\var\
servers\SERVER_NAME\partitions\PARTITION_NAME\
.
This file will be created if your project contains an EJB 2.0 module with data
sources/messaging resources defined.
Note This action can be turned off by unchecking the Deploy jndi-definitions.xml option in
the Deployment EJBs Services properties on the Server node of the Project
Properties dialog box.
■
Copy selected libraries to the partition’s lib directory. All archives in this directory
will be added to the partition’s classpath when the partition is started up.
The directory on the server for Borland Enterprise Server AppServer Edition 6.0 is
APPSERVER_HOME\var\domains\base\configurations\CONFIGURATION_NAME\mos\
PARTITION_NAME\lib.
For the Borland Enterprise Server AppServer Edition 5.2.1, the
directory is
APPSERVER_HOME\var\servers\SERVER_NAME\partitions\PARTITION_NAME\lib.