This section describes how to troubleshoot problems associated with the EAServer plug-in for JBuilder. For information about installing the plug-in, see the Sybase white paper, Configuring and Troubleshooting the Sybase EAServer Plug-in for JBuilder X,.
If you are having trouble with the EAServer plug-in for JBuilder, verify the following:
You have the latest easerver-jbsp.jar file.
The working directory matches the EAServer installation location.
The plug-in is set up using the JBuilder Project | Default Project Properties.
The project’s application server is set to EAServer. Verify using the JBuilder Project | Project Properties | Servers menu item.
If you are debugging a JSP, you are using a local EAServer installation.
If the WAR file contains extra files, or if it contains other application servers, such as the BNX Authentication Suite (BAS) 5.0:
Right-click the Web application, and choose the Dependencies tab.
Select EAServer, and select Never Include any Classes or Resources.
Reviewing deployment output and generating verbose logging
Examine the output that was generated during deployment. Pay special attention to the CLASSPATH.
Display extra internal logging information and runtime exceptions by running JBuilder with the -verbose option; for example:
jbuilder\bin\jbuilder -verbose > output.txt
where output.txt is the log file.
Examine the EAServer log files, which are typically found in the EAServer bin or devbin subdirectory.
Deploy the WAR file to EAServer using EAServer Manager or jagtool.
Run the J2SDKEE Sun verifier on the generated EAR, JAR, or WAR file; for example, on Windows:
verifier.bat myWAR.war
