Did you reference all used projects and JAR files in the Java build path?

If your project depends on classes available in other projects or JAR files, you need to describe them in the Java Build Path (Properties ® Java Build Path from the context menu over the project).

By default, EJB and Web projects include in the JRE_LIB and J2EE Libraries variables in their build paths (Propertie  ® Java Build Path ® Libraries) the JRE and corresponding J2EE library JARs.

See the corresponding part of the SAP NetWeaver Developer Guide to find out if your project needs other specific libraries for compilation.

Did you describe all manually-added project components in the deployment descriptors?

If you manually added files to the project folder in an external way, you need to describe the corresponding Web or EJB components in the proper deployment descriptors.

For components added from the J2EE Toolset, the description is added automatically.

Are all components referenced in your projects available on the J2EE Engine?

It is possible that certain referenced components linked from the SAP NetWeaver Developer Studio are not available later on the J2EE Engine. In such case, the projects will compile and build, but will not deploy or it is possible to get a java.lang.ClassNotFoundException.

To make sure the situation is avoided, you need to check if the corresponding applications are installed on the J2EE Engine, or if they are available in the default set of libraries in the J2EE Engine.

Did you add as modules all corresponding (Web or EJB) projects?

You need to reference the corresponding projects so their project archives are included in the application EAR file.

If you have not done so, select the Enterprise project in the J2EE Explorer or J2EE DC Explorer, and choose Add Modules from the context menu.

Did you define proper context root for each Web module in the project?

Make sure that the context root of the Web modules are unique. Other wise you get a deployment error.

Did you define the correct settings for the J2EE Engine?

To be able to deploy an application from the SAP NetWeaver Developer Studio, you need to specify the host and port of the J2EE Engine.

This is done from Window ® Preferences ® SAP J2EE Engine.

If you installed the SAP NetWeaver Developer Studio along with the local J2EE Engine, the J2EE Engine settings in the SAP NetWeaver Developer Studio are automatically configured, so you can miss this step.

Did you set breakpoints at the correct places in the source?

If you did not set any breakpoints, the application being debugged will not show different behavior from its ordinary behavior, that is it will not halt at problematic places.

Setting breakpoints is done by clicking the left gutter of the Java editor with the secondary mouse button, and choosing Set Breakpoint.

Is the application version deployed on the J2EE Engine the same as the version in the J2EE projects in the SAP NetWeaver Developer Studio?

Make sure you have packed and deployed the latest version of the application on the J2EE Engine. One way to do this is by checking the icon with which breakpoints are displayed in the source code. If the icon is only a circle, then the current version of the source file is not deployed on the J2EE Engine. In such a case, you need to rebuild and redeploy the application.

If the breakpoint icon is a circle with an OK tick, then the source file is already available on the J2EE Engine.

Is the J2EE Engine properly configured for debugging?

You can view the J2EE Engine status from the J2EE Engine view.

The proper configuration includes enabling the debugging of the desired processes, disabling the load balancing mechanism for those processes, and so on. Some of the operations are done from external tools to the SAP NetWeaver Developer Studio, and require restart of the J2EE Engine.

For more information, see Preparing the Debugging Process.