Skip to Content

I hope you’ve all downloaded the SAP NetWeaver Composition Environment trial version and managed to get a first impression of some of the new features, capabilities and improvements of the next version of Visual Composer, which provides the modeling environment in which to create UI views for composite applications.


You probably noticed that in this version you create components and not iViews. A component can be either a composite view (similar to an iView in Visual Composer 7.0 – 2004s) or a service component (a complex data service). The nice thing about components is that you can easily reuse them in other models.


In Visual Composer for NetWeaver 7.0, a nested iView or other embedded component is an integral part of the model itself and cannot be reused by other models. In Visual Composer for CE, “embedding” a model simply means creating a reference from one component to another component.
As a result, model creation, maintenance, and efficiency are significantly streamlined.


Another important improvement that you probably observed is the new Lifecycle Management capability. In order to use source control with your models, you can integrate Visual Composer with NetWeaver Development Infrastructure and its Design Time Repository, or use the improved shared repository that enables basic source control functionality such as check-in, check-out, and revert.


And what about the actual modeling experience? That we also improved, providing you with a more intuitive way to create wizards and other containers, the ability to define a sequence of actions, a new switch operator, and much more….


In my upcoming blogs, I’ll explore more of the new Visual Composer capabilities and drill-down into the details…
But before then, come on – install the trial version and start previewing Visual Composer for SAP NetWeaver Composition Environment. I’d be very happy to hear your feedback and learn from your experiences!

Hope to see you all in our CE sessions at TechEd:
CE106 – Modeling with SAP NetWeaver Visual Composer – Status and Outlook lecture
CE153 – Modeling in Visual Composer for SAP NetWeaver Composition Environment – nd Hands-on session
CE250 – Advanced Modeling in Visual Composer for SAP NetWeaver Composition Environment – an Hands-on session

To report this post you need to login first.


You must be Logged on to comment or reply to a post.

  1. Former Member
    Thanks for this great blog!

    Regarding Visual Composer, is the modeling (Design Time) the only part that has been enhanced or are there some breakthroughs in the Runtime as well ?  ๐Ÿ™‚

    Best regards,

    1. Hi Guilaume,

      Thanks (-:

      Yes, there was also a breakthrough in the runtime: whereas Visual Composer 7.0 (04s) is mainly a tool for modeling portal iViews, Visual Composer for CE is designed for creation of Web Dynpro-based composite applications. As such, in VC for CE, the Web Dynpro foundation is the runtime UI technology and enables you to render models to both HTML and Flex.

      1. Former Member
        Does this mean that I can use Visual Composer 7.1 to generate a webdynpro that I can then edit as a webdynpro i.e. Business process user can do the basics and pass on to an experienced programmer?
        1. If you are asking about the model to code scenario (starting to model the application in VC and then adding the missing functionality in WD), this will not be possible, mainly because by doing that you’ll lose your connection to the VC model.
          But, in a later phase of this version, we’ll offer the code to model solution… you’ll be able to create your Visual Composer application – and in case you won’t have a secific control, or logic in VC, you could create this missing functionality in WD, and than consume it in Visual Composer.
          You’ll basically add it as a black box, island of technology to your model.
          This way, you’ll not lose your Visual Composer model – but you’ll be able to enhance its functionality using WD.

Leave a Reply