tag:blogger.com,1999:blog-9057379846514679550.post811615342007457891..comments2023-11-01T13:19:34.469+01:00Comments on Thoughts on aspects within Microsoft 365 based Digital Workplace: Reasoning for Duet Enterprise in addition to SAP NetWeaver GatewayWilliam van Strienhttp://www.blogger.com/profile/02730614987048826403noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-9057379846514679550.post-77876542628000719832012-01-27T22:47:01.617+01:002012-01-27T22:47:01.617+01:00Niels,
Thanks for your response.
Let me make it st...Niels,<br />Thanks for your response.<br />Let me make it straight: Duet Enterprise is in no means limited to only mapping SAP UI onto comparable SharePoint UI. The real potential (see the remark of Kristian, and my reaction on that) is in combining the strengths of SharePoint platform with the structural and stable processing of SAP. For example: work on / around SAP data via the information worker capabilities of SharePoint; enterprise content management, BI dashboarding, composite apps.<br />The approach that The Next View advocates is to start from the User Experience view, by first deriving the User Interaction Design. Next step is to validate with the SAP analysts and architects whether it is feasible to realize that UID via the SAP backend. If not, decide to adapt to UID, or make custom development in SAP. Always, the user and the requested (+ intuitive) user experience is the guiding factor; and IT landscape in combination with (lack of sufficient) business case may be the constraint.<br /><br />I'm familiar with Sitrion, fine tool for certain aspects of SAP / MS interop. Issue is that it is a 3rd party product as add-on to the portfolio of strategic IT suppliers SAP and Microsoft. Enterprise Architecture consolidates the IT landscapes, and reduces the number of foreign tools + technologies.William van Strienhttps://www.blogger.com/profile/02730614987048826403noreply@blogger.comtag:blogger.com,1999:blog-9057379846514679550.post-67062260080035108132012-01-27T21:58:35.150+01:002012-01-27T21:58:35.150+01:00Mapping SAP functionality one-to-one into SharePoi...Mapping SAP functionality one-to-one into SharePoint webparts or lists is of limited value, evil tongues in the industry call this “lipstick on a pig”. <br />It is much more useful to unify the informal and formal aspects of business processes in a way mimic real work better. We see three widely adopted use cases: 1) SAP self-services that hide SAP complexity via a natural Microsoft context in Office, SharePoint, Azure or on Mobile Devices. 2) Office documents as artifacts of SAP processes 3) Formal SAP workflows chained with informal Microsoft workflows.<br />To enable this, some sort of service composition is needed. SAP Gateway (Duet Enterprise) is an excellent choice for SAP centric developers. For .NET developers that want to cover both back-end and front-end composition in heterogeneous environments (SAP and beyond), 3rd party vendors make robust tools available. Sitrion, for example, has taken a software factory approach to .NET development for SAP. No matter what the approach, composition is king.Niels Hvidtfeldthttps://www.blogger.com/profile/16329057932481596366noreply@blogger.comtag:blogger.com,1999:blog-9057379846514679550.post-17535653632678486072012-01-24T20:36:19.026+01:002012-01-24T20:36:19.026+01:00Kristian
Yes, real added value is within combining...Kristian<br />Yes, real added value is within combining the strengths of the 2 platforms, with each a different primary focus. However, in practice more and more the initial or starting motivation appears to replace the SAP user interface by another, more appreciated (due familiarity) ui in the primary enterprise portal. And as we both are aware, this is often SharePoint based.William van Strienhttps://www.blogger.com/profile/02730614987048826403noreply@blogger.comtag:blogger.com,1999:blog-9057379846514679550.post-59513752913794672062012-01-24T17:50:42.946+01:002012-01-24T17:50:42.946+01:00I agree with your comment on SAP/SharePoint intero...I agree with your comment on SAP/SharePoint interoperability often being driven by negativism towards SAP. If that is the driver, then as you say, any UI framework can be utilised to address the problem.<br /><br />The real potential for SAP/SharePoint solutions lies in a new class of composite applications that mash up structured and unstructured content. In reality, this is conceptually disruptive and customers are still waiting for the visionary killer use cases.Kristian Kalsinghttps://www.blogger.com/profile/01681951823483157725noreply@blogger.com