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
40 Developing Applications for J2EE Servers
Remote deploying
Note By default, all services associated with a partition are started. This could cause the
partition to take a longer time to start. To reduce startup time, uncheck the services that
you don’t require in the Server run configuration.
Remote deploying
To prepare to remote deploy EJBs, WARs, and EAR modules for the Borland
Enterprise Server AppServer Edition 6.0, follow these steps.
1 Choose Enterprise|Configure Servers.
2 Select Borland Enterprise Server AppServer Edition 6.0 from the left side of the
dialog box.
3 Click the Custom tab and set the Server, Configuration, and Partition names to
match that of the remote server.
4 Click the Advanced Settings button and make sure the Management Port matches
your server configuration.
5 Click OK two times.
6 Choose Enterprise|Enterprise Setup.
7 Select the CORBA node to display the CORBA page, and set the Smart Agent Port
to match that of your server configuration.
8 Click OK.
To prepare to remote deploy EJBs, WARs, and EAR modules for the Borland
Enterprise Server AppServer Edition 5.2.1, follow these steps.
1 Choose Enterprise|Configure Servers.
2 Select Borland Enterprise AppServer Edition 5.2.1 from the left side of the dialog
box.
3 Click the Custom tab and set the Server and Partition names to match that of the
remote server.
4 Click Advanced Settings and make sure the Management Port matches your server
configuration.
5 Click OK two times.
6 Choose Enterprise|Enterprise Setup.
7 Select the CORBA node to display the CORBA page, and set the Smart Agent Port
to match that of your server configuration.
8 Click OK.
Now you are ready to deploy. There are two ways to deploy EJBs, WARs, and EAR
modules using JBuilder:
■
Deploying to the server using the Borland Enterprise Server Deployment Wizard
(Enterprise|Server Deployment). This is a Borland Enterprise Server tool and
requires that the management agent is running. On the first page of the wizard,
select the modules to deploy. The wizard then detects all partitions on the server,
even if they have not been started. Select the appropriate partition from the list and
click Finish to deploy the archive. If the partition has already been started, restart the
partition to access the deployed archive.
■
Deploying to the server using the context menu option on any deployable node.
Right-click the deployable node to see the Deploy commands. Choose Deploy. You
can also select multiple deployable nodes, right-click them, and use the context
menu that appears to deploy more than one module.