Working with J2EE Engine Libraries 

Purpose

If you want to use in your applications Java classes that will not be included in the application EAR, you can implement this by using J2EE Engine libraries (or simply libraries). For example, this may be necessary if the corresponding functions or modules will be reused by multiple J2EE applications, so it is more convenient to have them in a single library instead of having them packaged in each application.

In the SAP NetWeaver Developer Studio, you can create new libraries or reference libraries in Web and EJB projects for compilation.

Process Flow

You can create libraries in Library projects. A Library project can contain one or more JARs or references to existing server components (libraries, interfaces, services). A library project defines exactly one library, which is made available in the J2EE Engine under a logical name. For more information, see Defining Libraries.

You can also define a library as a development component (DC). This is particularly useful if your application projects are based on the SAP component model and therefore make use of the SAP development infrastructure. In such cases, you create Library DC projects instead of ordinary Library projects. For more information, see Defining Library DCs.

From the SAP NetWeaver Developer Studio you can build the library archive (SDA) and deploy it directly on the J2EE Engine. See Creating a Library Archive and Deploying a Library Archive.

If you want to use libraries in Web or EJB projects, you need to add the libraries to the Java build path of the projects. See Referencing Libraries in Applications.