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 4: Configuring the target server settings 25
Selecting a server
■
To use different servers for different services,
1 Select the Modular Services Provided By Different Servers option.
2 Check the check boxes next to all the services for which you want to specify
an application server in the Services list.
3 Click one of the checked services to select it in the Services list.
4 In the Service Properties For Project group box, use the Server drop-down list
to select the server you want to use for this service.
If server-specific properties are available for the server you selected for the
particular service you are working with, they will appear below the Server
drop-down list. If the Deployment service is selected, a Build Target For
Deploying To Server drop-down list appears on the Service Properties For
Project panel. Select the type of build you want to occur. If the EJB service is
selected, you’ll see read-only information appear that is intended to help you
decide which server is appropriate for your needs.
If you select the JSP/Servlet service, the Default Runtime Host Name and
Default Runtime Port Number fields are available to you. The default values
refer to the global server configuration. If you change these values, they are
used for all server run configurations created after you made the change.
If you expand the Deployment service node, you can select from several
subnodes that have accompanying properties. The properties vary depending
on which is your selected server. All servers have a Build Target For
Deploying To Server field, however. Select your desired build option from the
drop-down list.
For Borland Enterprise Server only
The Deployment jndi-definitions.xml option determines whether the
jndi-
definitions.xml
file is included in any of the deployment actions you select.
Uncheck it if you don’t want it included.
jndi-definitions.xml is an XML
deployment descriptor for EJB 2.0 resources.
For WebLogic 7.x – 8.1
If you expand the WebLogic Deployment service node and select the WARs
node, the service properties include a Map Project Webapps At Runtime
option. When this option is selected (the default value) all web applications in
the project deploy from the web application directory and not as a WAR when
the server starts up.
If you expand the WebLogic Deployment service node and select the EARs
node, the service properties include a Map Project EJB Modules At Runtime
option. When this option is selected (the default value) all EJBs in the project
deploy from the EJB directory and not as a EAR when the server starts up.
All the WebLogic Deployment service nodes have Deploy As Archive and
Deploy As Exploded Directory options. Checking the Deploy As Archive option
enables the archive to be deployed. Checking the Deploy As Exploded
Directory option 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 combo box with
options to deploy data sources for all EJB modules in the project. These are
the options:
■
Map Project Data Sources: 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 Data Sources: Maps data sources for all EJB
modules in
config.xml for the domain specified in the server configuration.