Skip to Content

To define and implement a successful UI strategy for a solution/product/service is a complex challenge. Multiple constraints influence the decision process and evolve over time. The list includes

  • customer expectations
  • architecture best practices
  • company strategy
  • ability to execute

When we started to implement our cloud service years ago we acknowledged the customer expectation to offer a browser based environment for integration content discovery, configuration, modeling and monitoring.

However, to maintain a high feature velocity we adopted as intermediate step a dual approach – Web Application (mainly for discovery and configuration) and Eclipse PlugIns (for modeling and monitoring) in parallel. During this phase we invested steadily on the Web Application also for modeling and configuration.

With our progress in the last months we are close to offer a fully enabled Web Application that supports all use cases for Integration Developers. One of the last remaining features is Integration Flow tracing which will be completed in our next monthly deliveries.

Based on the positive customer feedback on our “WebUI only” approach and our implementation progress made we reduce our development investments in Eclipse PlugIns going forward.

This means in detail

  • we discontinue the “Integration Designer” feature for Eclipse by 06-June-2018 in the context of our Eclipse Oxygen adoption (please use the Web Application instead)
  • we restrict the remaining features in Eclipse and encourage Eclipse usage only for the ADK based adapter development use case

You may continue to use your existing Eclipse Neon installations beyond 06-June, but our future development, maintenance & support would be on our Web Application only.

I recommend you to explore the Web Application capabilities if not done yet.

 

Remarks

  1. We currently don’t have plans to move to SAP Web IDE development platform as
    • our development focus is on the Integration Flow modeling environment
    • we plan to extend our offering in Web Application which supports and improves all use cases for an Integration Developer
  2. The ADK based adapter development use case is defined as “create, implement, unit test and deploy your adapter”. No change for these actions in Eclipse. But consumption of the adapter in an Integration Flow will require Web Application usage in future.
To report this post you need to login first.

12 Comments

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

  1. Olegs Veliks

    Have been switched from Eclipse to Web UI 6 month ago. It’s very comfortable once you get use to it. I’m still missing info about which xsd/wsdl mapping refers to. And maybe zoom out/zoom in possibility within mapping Editor.

    (0) 
  2. J. Jansen

    Thank you for the update Andreas. This clarifies the way forward regarding developer tools. I like the updates on Web UI so far as well. Do have some suggestions on priority items for your product backlog though (Hint: something to do with testing graphical mappings and being able to view content of queue context 🙂

     

    Regards,

    Jeroen

    (0) 
  3. Eng Swee Yeoh

    Hi Andreas

     

    Thanks for the update. One question – will the Eclipse plugin update site be also decommissioned post June 2018? I have tonnes of content already developed in Eclipse and it will be useful in the future to still be able to open them up in read-only in Eclipse just for reference.

     

    Regards

    Eng Swee

    (0) 

Leave a Reply