Development Component Types

Use

Every development component (DC) has a unique type. This type determines the technology of the DC, the tools available for developing the component, the way in which the component is compiled, and the kind of products a DC creates during compilation.

Example

Component types carry a unique name and a vendor ID. The number of DC types can be increased, if necessary - even by third-party suppliers. Note that inside your SAP NetWeaver Developer Studio, you can find DC types that are not described in this topic. For more information about them, see the corresponding documentation that describes their usage(s).

Development Component Types

Name	Deployable Build Result	Description
Build Infrastructure	No	A DC that provides the necessary library functionality to implement Build Plug-in or Build Infrastructure Extension DCs. DCs of this type shall only be used by Build Plug-in, Build Infrastructure Extension or other Build Infrastructure DCs.
Build Infrastructure Extension	No	A DC that provides certain extensions to the build process. They can be attached to another DC in addition to a Build Plug-in DC to tweak or complement the build process. DCs of this type can be used and referenced like ordinary DCs.
Build Plugin	No	A DC that implements the build process of a certain component type (or a set of related DC types). DC of this type is used from other DCs by declaring a special build plug-in usage dependency. This dependency is an explicit reference to the build plug-in DC in the . DCDEF file of the using DC that is entered when the using DC is created. This special dependency is created by the SAP NetWeaver Developer Studio when you create a new DC.
Composite Application	Yes	Contains all elements required for a Composite Application Services project. These are Dictionary objects, metadata and Java classes.
Content Guided Procedures	No	Guided Procedures (GP) design time is a set of tools that allows you to model arbitrary business processes using a repository of software modules accessed in a uniform manner. These modules come pre-programmed with the GP framework and ready to use. They perform atomic tasks and can be combined into a working process.
Content UME Permissions	No	Extends the possibilities provided by the AS Java security roles. However, they are only supported when using a programmatic approach.
Dictionary	Yes	Defines global data structures that are created in the database on the server, where the DC should be deployed. Since the data structures are created in a central database you should use unique names. To ensure this, the name server allows only certain prefixes for table names.
Enterprise Portal Portal Application Standalone	Yes	The model classes and structures for an Enterprise Portal Application project. These projects are automatically built in deployable archives (SDA).
External Library	No	Enables you to use functions for development inside the component model that are available only as libraries and not as source files. You develop External Library DCs when you use the NWDI for development and want to use a function that is available to you only as a JAR file. To do that you have to: Create a new DC of type External Library. Create a public part of type Compilation and add the JAR file as a public part entity. You can now use the library to build other DCs. Because the DC type External Library itself has no deployable build result, you must deploy this DC together with another DC to make it available on the server. To do this, you need another public part of type Assembly . Create another public part of type Assembly . Add these JAR files as a public part entity. To do that in the context menu of the public part, choose Manage Entities . Put the JAR file into the public part. You can now wrap this public part into another DC type and make it available on the server. Other DCs then refer to the wrapped DC and not to the External Library. After the build, you can use the new DC just like any other DC. You can use it either separately or combine several External Library DCs into a software component.
J2EE EJB Module	No	Contains the model classes (for an Enterprise Application DC ). When you create an EJB Module DC , the Developer Studio automatically creates a public part for assembly that contains the classes for the beans and a public part for compilation that contains the bean interfaces. To add JPA (Java Persistency API) support in the DC, you have to manually add JPA facet to the DC project. More information: Creating JPA Projects in the Developer Studio .
J2EE Enterprise Application	Yes	Combines Web Module DCs and EJB Module DCs into an enterprise application.
J2EE Web Module	No	Contains the files that belong to the view (and view-controller) part of an enterprise application project, such as JSPs, Servlets and Proxy classes for beans defined in an EJB project.
J2EE Server Component Library	n/a	Deprecated. There is limited support on already existing old DC projects of this type. You can import, build and deploy them using the Developer Studio, but you cannot create new J2EE Library DCs. We recommend that you migrate the J2EE Library DCs to Enterprise Application DCs.
Java	No	Contains arbitrary Java code.
Mobile Web Dynpro Offline	No	Web Dynpro provides the infrastructure and necessary rendering classes, with which the Web Dynpro applications can be executed on a mobile device.
Process Modeling	Yes	Allows you to create an end-to-end business process model using a set of elements, defined by the Business Process Modeling Notation (BPMN). Assigning software modules to the business process model's elements makes the model executable.
Product Description DC	No	DC that contains metadata of a product (such as name, vendor, versioning). DC dependencies from the respective Product Description DC to the respective Software Component Description DCs define the product constituent.
Software Component Description SC	No	DC that contains metadata of an SC (such as name, vendor, versioning). DC dependencies from the respective Product Description DC to the respective Software Component Description DCs define the product constituent.
Visual Composer	No	Visual Composer provides a development environment for rapidly creating and adapting model-based transactional and analytical applications. It has been designed to enable business analysts to create enterprise applications using standardized components that meet SAP's standards and quality criteria.
Web Dynpro	Yes	A container for one or more Web Dynpro components.
Web Services Deployable Proxy and Standalone Proxy	Yes	Contains client code that accesses a Web Service.