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 7: Using JBuilder with BEA WebLogic servers 69
Remote deploying
■
Deploying from the project pane:
a Right-click the module you want to deploy in the project pane and choose
Properties.
b Select Deployment in the tree to display the Deployment page.
c Set the Admin URL to Set the Admin URL to the remote server, such as <HOST
NAME>:<port number>
.
d Right-click the module you want to deploy in the project pane and choose Deploy
Options|Deploy.
Deploying J2EE modules as an exploded directory
You can deploy WebLogic 7.x and 8.x J2EE modules as an exploded directory. You
can set this option at the project-wide level, at the module level, or at deployment time.
To set this option at the project level,
1 Choose Project|Project Properties and select the Server page.
2 Open the Deployment node in the tree on the left to see the types of J2EE module
modes.
3 Select the type of module node(s) you want to explode at deployment time.
4 Check the Deploy As Exploded Directory option on the module type page that
appears.
5 When you are done selecting the types of modules you want to explode at
deployment time, choose OK to close the dialog box.
To set this option at the module level,
1 Right-click the module you want to deploy as an exploded directory and choose
Properties.
2 Select the Deployment page.
3 On the WebLogic 8.x page that appears, check the Deploy As Exploded Directory
check box.
4 Choose OK to close the dialog box.
To set this option at deployment time,
1 Choose Enterprise|Server Deployment to display the WebLogic Deploy Settings
dialog box.
2 Check the Deploy As Exploded Directory check box.
3 Choose OK to close the dialog box.
Mapping EJB project modules at runtime
EJB project modules can be mapped at runtime. Mapping EJB modules modifies your
domain config file by adding an application tag to it. The advantage to doing this is that
the module is not deployed as an archive. You would want to use this feature only for
development and not during production. Follow these steps:
1 Choose Project|Project Properties.
2 Select the Server page.
3 Open the Deployment node in the tree on the left to see the types of J2EE module
modes.
4 Check the EJB node in the tree on the Server page and EJB module deployment
properties appear.