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 6: Using JBuilder’s CORBA tools 47
Setting up JBuilder for CORBA applications
Setting up JBuilder for CORBA applications
This section explains how to set up JBuilder with the VisiBroker ORB or OrbixWeb so
that you can create, run, and deploy CORBA applications. You can also configure
other, third-party ORBs. More information on the VisiBroker ORB is available in the
doc
directory of your Borland Enterprise Server installation. Consult the OrbixWeb
documentation for information on particular features of that ORB.
Configuring VisiBroker when the Borland Enterprise Server
is installed
Follow the steps in this section to set up JBuilder for use with VisiBroker when the
Borland Enterprise Server AppServer Edition 6.0 is already installed, configured and
the target server for your project. Note that the server creates its own VisiBroker
configuration. For information on configuring Borland Enterprise Server, see Chapter 5,
“Using JBuilder with Borland servers.”
To configure VisiBroker when the Borland Enterprise Server is installed,
1 Choose Enterprise|Enterprise Setup to display the Enterprise Setup dialog box.
Select the CORBA page. The parameters in this dialog box allow JBuilder to see the
ORB.
2 Select the VisiBroker (Borland Enterprise Server AppServer Edition 6.0) option from
the Configuration drop-down list.
The Enterprise Setup dialog box will look similar to this:
3 Click OK to close the dialog box. You do not have to complete other configuration
steps; JBuilder is now configured for use with VisiBroker.
4 Click OK to save the configuration.
Important In the runtime configuration for your CORBA application, you need to add the following
parameters to the VM Parameters field in the Edit Runtime Configuration dialog box
(Run|Configurations|Edit):
-Dvbroker.agent.port=14000
-Dborland.enterprise.licenseDir=C:/<BES_install>/var
-Dborland.enterprise.licenseDefaultDir=C:/<BES_install>/license
You’ve now completed setting up your system to use the VisiBroker version installed
with the Borland Enterprise Server AppServer Edition 6.0. Before running your
application, choose Tools|VisiBroker Smart Agent to start the Smart Agent. (Note that it
is also automatically started when you start the Management Agent with the Enterprise|
Borland Enterprise Server Management Agent command.)