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 4: Configuring the target server settings 27
Updating projects with the latest server settings
5 Click OK to close the file browser. This displays the new library at the bottom of the
library list and selects it.
6 Click OK. JBuilder creates a new .library file in the JBuilder /lib directory with the
name you specified (for example,
InterClient.library). It also returns you to the
Database Drivers page which displays the name of the corresponding .config file in
the list which will be derived from the library file (for example,
InterClient.config).
7 Select the new .config file in the database driver list and click OK. This places the
.config file in the JBuilder
/lib/ext directory.
8 Close and restart JBuilder so the changes to the database drivers will take effect,
and the new driver will be put on the JBuilder classpath.
Important If you make changes to the .library file after the .config file has been derived, you must
re-generate the .config file using Enterprise Setup, then restart JBuilder.
Now that JBuilder can see the database driver, you must add the database driver
library to the Required Libraries list in Project|Properties, or Project|Default Properties.
Adding the JDBC driver to projects
Projects run from within JBuilder use only the classpath defined for that project.
Therefore, to make sure the JDBC driver is available for all new projects that will need
it, define the library and add it to your default list of required libraries. This is done from
within JBuilder using the following steps:
1 Start JBuilder and close any open projects.
2 Choose Project|Default Project Properties.
3 Select the Required Libraries tab on the Paths page, then click the Add button.
4 Select the new JDBC driver from the library list and click OK.
5 Click OK to close the Default Project Properties dialog box.
Note You can also add the JDBC driver to an existing project. Just open the project, then
choose Project|Properties and use the same process as above.
Updating projects with the latest server settings
If a server configuration has been modified since a project was last opened, JBuilder
updates it with the latest server settings for the project’s selected server(s). So, for
example, if you have modified server settings for one project and you have others that
aren’t open that use the same server configuration, the next time you open those other
projects, your modified server settings will be in force automatically. If you want to use
a similar but unique server configuration for a particular project, create a duplicate
configuration using the Copy button, and use the Copy Servers wizard to edit it to your
needs.
Be aware that this automatic updating of projects with the latest server settings can
occur only with server configurations modified in JBuilder 9 or higher. If you attempt to
transfer server libraries from a previous JBuilder version, your projects won’t be
updated with them. You can still tell JBuilder to update the project manually:
1 Right-click the project node of the project you want to update in the project pane and
choose Properties.
2 Select the Servers page.
3 Click the ellipsis (…) button next to your selected single server or the separate
service servers and make your changes.
4 Click OK to close the dialog box.