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-48.png)
Chapter 6: Using JBuilder’s CORBA tools 49
Setting up JBuilder for CORBA applications
5 The Library For Projects field defines the library location of the ORB tools. To define
the library location, click the ellipsis (…) button next to the Library For Projects field.
This displays the Select A Different Library dialog box.
The library is necessary for compiling the generated stubs and skeletons and for
executing an application. For VisiBroker, browse to the Borland Enterprise Server
6.0 Client library, then click OK two times.
6 In the Enterprise Setup dialog box, leave the Apply This Configuration To The
Current Project option selected in order to set this ORB configuration for the current
project, as well as the default project.
7 Set the Make This Configuration’s ORB The Default For The Java VM option to use
the selected ORB as the default ORB for the Java VM.
8 Select the Add A VisiBroker Smart Agent Item To The Tools Menu option to enable
the Smart Agent to run as a JBuilder service during development. This option will be
disabled if the Smart Agent is not necessary.
9 Select a port on which to run the Smart Agent. The default port of 14000 will work on
most systems.
Note When running the project, you can use a JBuilder macro in the VM Parameters field
on the Edit Runtime Configuration dialog box for the application. This macro allows
the project to be used on another machine where the Smart Agent is configured for
a different port. The syntax is:
-Dvbroker.agent.port=($SmartAgentPort)
10 Click OK to save the configuration.
You also need to pass options to the IDL compiler.
To pass options to the IDL compiler when configuring VisiBroker stand-alone,
1 Choose Project|Project Properties|Build|IDL to display the IDL Build page, which will
look similar to this: