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
66 Developing Applications for J2EE Servers
Working in JBuilder
means the archive is exploded into a directory as its contents are deployed
instead.
If you select the EJB service, the service properties include a Datasource
Mapping combo box with options to deploy (auto-deploy) data sources for all EJB
modules in the project. These are the options:
■
Map Project Datasources: Maps data sources for all EJB modules in
config.xml for the domain specified in the server configuration. Datasource
entries are removed when the server shuts down.
■
Map And Persist Project Datasources: Maps data sources for all EJB modules
in
config.xml for the domain specified in the server configuration. Data Source
information is persisted in
config.xml. Datasource entries are removed when
the server shuts down.
■
Do Not Map Project Datasources: Does not map any data sources.
e If you want to make changes to the configuration settings for the server selected
for the service, click the ellipsis (…) button and edit the settings you want on the
General and Custom pages. Click OK.
f Repeat these steps for each service you want access to.
Click OK when you are finished with the dialog box to select your specified server for
your current project.
If you neglect to select one ore more servers for a project, the Server page of the
Project Properties dialog box appears when you start an EJB wizard from the object
gallery. Use this page to select your server. All EJB projects must have one or more
selected servers.
Working in JBuilder
JBuilder supports WebLogic servers in all areas of development. This section
describes some of the WebLogic-specific features available to you.
Using existing code
If you already have existing WebLogic EJB 2.0 deployment descriptors for enterprise
beans you created previously, you can create a new EJB module that contains the
descriptors. You have two options:
■
Use the EJB Module From Descriptors wizard, which creates a new EJB module
that contains the deployment descriptors.
■
Use the Project For Existing Code wizard, which creates a new JBuilder project
containing one or more new EJB modules that contain the deployment descriptors.
See “Creating an EJB module from existing deployment descriptors” in Developing
Applications with Enterprise JavaBeans for complete information.