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
84 Developing Applications for J2EE Servers
Selecting a server
5 Click the Custom tab to view fields unique to the server. Change or fill in these fields:
■
Server Version: Your choices are server version 3.2.5 and 3.0.8. These are the
versions of JBoss JBuilder officially supports.
■
Configuration Name: Specify the configuration you want to begin using. You can
select a configuration from the drop-down list, or type in your own configuration
name. The configuration you specify must exist in the
server directory, which is a
subdirectory of the Home directory.
■
Deployment Path: Specify the path used to deploy your modules. By default, the
deployment path will be in the
deploy subdirectory of the directory you specified
as the Configuration Name.
■
Include System Modules When Listing Deployments: JBuilder can list all your
deployed modules. If you wish to see the system modules such as the web
container or the EJB container and other services that are a core part of the
JBoss server, check this option.
■
Include Disabled Modules When Listing Deployments. JBuilder can list all your
deployed modules. If you wish to see modules which are currently disabled,
check this option. A disabled module is simply one that has been renamed to
<module name>.disabled when you chose to disable it within JBuilder using the
Disable deployment option.
6 Choose OK to close the dialog box and configure JBuilder.
When you configure JBuilder to target a JBoss server, required libraries are created for
you. To see a list of the JBoss libraries, see “The created libraries” on page 23.
Selecting a server
If you are working with more than one version of JBoss Application Server and have
configured JBuilder for all versions, you must select which version you want to use for
your current project. Choose Project|Project Properties and select Server in the tree to
display the Server page. See “Selecting a server” on page 24 for more information.
Creating a JBoss service module
You can use JBoss to create a service module for extending the JBoss server. A
service module contains the definition of a service. Once you compile the service
module, a service archive (SAR) is created, ready to be deployed to JBoss.
To begin creating a JBoss service module within JBuilder, follow these steps:
1 Choose File|New|Enterprise and double-click the JBoss Service Module wizard. The
wizard appears: