Component Modeler

The Component Modeler is a graphical tool for the definition of Development Components (DCs) for business applications based on Java Web Dynpro technology. This tool enables you to:

Create a Component
Define a Component Interface
Define an Application
Create a Connection
Create/Import a Data Source

You start the Component Modeler on the Web Dynpro project you have created by double-clicking the project name in the Web Dynpro Explorer. In the right-hand screen area, the modeler tool is opened with a background made of grid lines. Inititally, the editor is empty and open for your definitions. As next step, you would click once on one of the palette entries.

Component
- Lets you create a new component - either a local component or a development component - for the Web Dynpro project.
Component Interface
- The component interface you define here is a standalone component interface.
Application
- A Web Dynpro application is the startup unit. You can define more than one application, at design time you decide which one you need at runtime.
Connection
- Using this option, you either create or implement a usage relation.
Data Sources
- Using this option, you can create/import a Web Dynpro model for backend access.
  Note
  We recommend that you generally make your definitions from the graphical tools.

After you have chosen the needed application unit from the palette, click once again in the editor area, and the corresponding unit wizard is started. Finalize the wizard for each desired application unit. The table below provides some detail information for the different wizards.

Unit type	Creation procedure	Result
Component	The wizard provides support for specification of window properties and view embedding.	The component is displayed with an incoming and an outgoing port from where you can make dataflow definitions lateron.
Component Interface		The component interface is displayed with an incoming port since this unit is used from others.
Application	For the application, explicitely a package name is needed.	With the definition of the application unit, you also have made decisions on the assigned component as well as on authentication. An arrow shows the assigned component.

Unit type

Creation procedure

Result

Component

The wizard provides support for specification of window properties and view embedding.

The component is displayed with an incoming and an outgoing port from where you can make dataflow definitions lateron.

Component Interface

The component interface is displayed with an incoming port since this unit is used from others.

Application

For the application, explicitely a package name is needed.

With the definition of the application unit, you also have made decisions on the assigned component as well as on authentication. An arrow shows the assigned component.

To edit a unit, double-click on it in the graphical tool (it is not explicitely marked as selected when you click once on it) to open the corresponding editor or tool.

Automatic Layouting

When using the editor, you don't have to manually arrange the units since automatic layouting is supported. Choose context menu entry Layout in the editor area to arrange the entity types in the editor screen. Additionally, you can zoom in and zoom out the editor display size, select the corresponding context menu entry.

Component Usages

Also for the definition of component usages which are reference relationships you get graphical support from the tool.

is used by reference

is implemented by reference