Configuring and Troubleshooting the Sybase EAServer Plug-in for JBuilder 2005

This document provides instructions to install, configure, and troubleshoot the Sybase EAServer plug-in for JBuilder 2005.

Install the EAServer Plug-in in JBuilder 2005
Configure the EAServer Plug-in in JBuilder 2005
Set EAServer As Your Default Server
Troubleshooting

Overview of the EAServer Plug-in for JBuilder 2005

The Sybase EAServer plug-in (a.k.a. integration module) for Borland JBuilder 2005 has been tested against EAServer 4.2.2, 4.2.3, 5.0 and 5.1. The plug-in provides the ability to:

• Deploy JAR, EAR and WAR archives from JBuilder to EAServer
• Develop and debug deployed EJBs, Servlets, and JSPs
• Use a GUI editor to set EAServer-specific properties

For most features, you only need a local EAServer client installation (including jagtool), and can utilize a remote EAServer server from JBuilder. However, if you want to debug JSPs, then you will need a local EAServer server installation on the same machine as JBuilder.

Install the EAServer Plug-in in JBuilder 2005

Simply click the checkbox beside the Sybase EAServer Integration Module to install the plugin as shown below.

The plug-in includes two files, extracted to the \lib\servers folder in your JBuilder installation directory.

Plug-in File	Description
easerver-jbsp.jar	The jar contains 96 Java classes and a manifest. This set of Java classes that are responsible for the support of EAServer in the list of supported Application Servers
EAServer_Plug-in_deployment.xml	The ant build script used during deployment. It can be customized to suit your preferences. For example, if you do not want a refresh to occur after a deploy, you can modify the build script accordingly so it does not invoke the refresh task.

Configure the EAServer Plug-in in JBuilder 2005

Follow these steps to configure JBuilder 2005 for use with EAServer.

Note: Although the screenshots show examples of Windows directories, the plug-in can be similarly configured for use with the UNIX versions of JBuilder and EAServer as well.

1. Run JBuilder
2. Choose Enterprise | Configure Servers
   
   

3. Highlight Sybase EAServer. On the General tab for Server Settings:
   • Click Enable server
     
   • Set the Home directory to the location where EAServer is installed
     
   • Set the Native executable launcher to the location of the serverstart.bat file
     
   • Specify the EAServer installation directory (same as the Home directory) as the Working directory

4. Select the Custom tab of the Server Settings, and specify these values:
   • Browse to pick your JDK installation directory
     
   • Specify the jagadmin login, password, server name, and IIOP port.

   Click OK to accept the changes.

Set EAServer As Your Default Server

Follow these steps so all new projects will have their server set to EAServer by default.

1. Choose Project | Default Project Properties

2. Click Server in the left pane, then choose Sybase EAServer as the Single server for all services in project.

   Click OK to save the information.
   
   

Troubleshooting

This section includes some troubleshooting tips for the Sybase EAServer plug-in for JBuilder 2005, and information on how to get additional help.

Troubleshooting Tips

Here are some general ideas to help troubleshoot problems with the EAServer plug-in.

1. Verify Configuration
   • Check that the you have the latest easerver-jbsp.jar file. (At the time of this writing, a November 2003 file date.)
   • Ensure the working directory matches the EAServer installation location (See step 3 under the Configure the EAServer Plug-in in JBuilder section.)
   • Ensure the plug-in is setup via JBuilder menu item Project | Default Project Properties
   • Make sure that the project's application server is set to EAServer from JBuilder menu item Project | Project Properties | Servers
   • If you are trying to debug a JSP, ensure you are using a local EAServer installation
   • Check the WAR file to see if it contains extra files. If so, right click on the Web application and choose the dependencies tab. Select EAServer and choose Never include any classes or resources. Also do this if other application servers such as BAS 5.0 Client are listed.
     

2. Review Deployment and Verbose Output
   • Examine the output generated during a deploy in the output window. Especially examine the classpath
   • Turn on verbose mode to display extra internal logging info and runtime exceptions., by running JBuilder with the -verbose option.
     For example:
     jbuilder2005\bin\jbuilder -verbose > c:\out.txt

   • Examine the EAServer log files, usually found in the %JAGUAR%/bin/ or %JAGUAR%/devbin directory

3. Try External Deployment and Verification
   • Attempt to deploy the archive file to EAServer using EAServer Manager or jagtool
   • Run the Sun verifier found in the J2SDKEE on the generated JAR/WAR/EAR file: verifier.bat myJAR.jar

More Information

For more documentation, samples, and support information, see the Sybase EAServer Plug-in for JBuilder 2005 page

Related Links