What is the benefit of using the Composite Designer?
The Composite Designer impacts directly your development by increasing the speed, hiding the complexity and reducing the total cost of ownership.
You increase the speed of your development, when you directly drag and drop objects from the palette. You can execute this for all technological layers, without the need to switch between the various perspectives.
In a similar case, you quickly browse for external services with the Search Console in resources such as Service Registry and Enterprise Services Repository. Once the service is found, you can directly drag and drop it from the Search Console to the application overview. This facilitates and speeds up your development as you have the advantage of having all these technologies and tools for external services in the Composite Designer.
There is also a possibility to use Predefined Templates to automatically generate parts of applications, which additionally could save effort and time for you.
(We will provide more information about the Search Console and the Predefined Templates in a separate blog.)
Besides using the graphical palette, you can create development objects for various technologies from another central view – the Composite Explorer.
The picture below shows the Composite Explorer view, with most of the context options for development objects for the business layer.
Using these features you increase the speed of your development and you enjoy a comfortable way of developing the “skeleton” of your application. This is achieved by the flexible features of just a single perspective – the Composite Designer.
When talking about hiding the complexity of your development, the Composite Designer represents the incredibly easy way to create relations between the objects. You simply drag the relation pointer from the first object to the second one. Here is the great benefit of the tool which automatically executes the numerous relation creation steps in its background and gives the result right away. In standard development you need to do all the steps by yourself – manually.
Therefore, in the relation creation use case you achieve your goals in an easier and faster manner, which hides the complexity of the standard “multiple perspective” development.
You can see all these manual steps that the Composite Designer does for you, when you actually create a relation. These steps are for example, creating of DC dependencies, exposing elements as public parts to be visible for the second development component (in a standard development done from the NWDI perspective), and so on. Usually, you need to perform all the tasks in separate perspectives.
Here is an example for a relation creation between a CAF application service (AS) and an Enterprise Java Bean (EJB) and the steps, which the tool performs automatically in its background.
As a result, using the Composite Designer you reduce your total cost of ownership (TCO) as most likely you use the saved time for addressing other tasks.