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
![](/manual/borland-software/jbuilder-2005/server-user-manual/images/img-69.png)
70 Developing Applications for J2EE Servers
Remote deploying
5 Select the Map Project EJB Modules At Runtime option:
6 Choose OK to close the dialog box.
EJB modules that are included in EARs won’t be mapped at runtime. If you try to
deploy a module (either EJB or web) that has been mapped, JBuilder displays a
warning. If you try to map a module (either EJB or web) that has been already
deployed, the deployment will fail and JBuilder displays a warning. You’ll also get a
warning if you right-click a module, choose Properties, and in the Build options page
select Never from the Build <Module> Directory drop-down list and then attempt to
deploy as an exploded directory or to map an EJB or web module.
Redeploying individual classes
For WebLogic 8.x only, once you have mapped an EJB project module at runtime as
explained in the previous section, you can then redeploy individual classes from the
module directory:
1 Right-click the class you want to redeploy (reload) in the project pane.
2 Choose Redeploy.
WebLogic 8.x Platform Server deployment features
The OpenTool for WebLogic 8.x Platform Server has improved deployment features.
You can now deploy submodules so you can deploy a module that has been newly
added to an EAR or redeploy it.
Use the deploy options on the context menu when you right-click the archive and choose
Properties. You can also access the deployment options when you choose Enterprise|
Server Deployment and choose from the actions on the drop-down Action list.
There are two additional options on the context menu that appears when you right-click
the archive and choose Deploy Options: Deactivate and Activate. Deactivate suspends
deployed components, leaving staged data in place for subsequent reactivation. To
reactivate a deactivated component, choose Activate. To totally remove the application
and any staged data from the server, choose Undeploy.
JBuilder now allows WebLogic Server 7.x and 8.x EAR, WAR, RAR, and EJB modules
to be deployed as an exploded directory. To permit this, follow these steps.
1 Choose Enterprise|Server Deployment to display the WebLogic Deploy Settings
dialog box.
2 Check the Deploy As Exploded Directory option.
3 Choose OK to close the dialog box.