Skip to Content

As part of the consultation process of moving towards SNC providing a

     . NetWeaver Architecture (Sub) Space

we need to define what is NetWeaver Architecture.

This document serves as the placeholder and container for that discussion.

This might sound funny, but we need to start from somewhere, so I will begin with

a description of NetWeaver Architect which I received in a job description.

We can then, fine tune this list, we can remove items, more narrowly specify certain

items and add items, all where necessary.

So here goes:

     Design and Architecture of complex SAP solutions

     SAP Technical Design issues

     SAP to SAP and SAP to Non-SAP

     SAP Architecture design across all SAP Components – any architecture question for any component

     SAP System Landscape, Platform, Technology design and strategy

     Future proofing SAP strategies

     Continuous Improvement Strategies

     Upgrade and Migration Strategy and Implementation and Design

     Across all integrations of SAP with other products

     Across operating system and through databases

     Across network and server architecture and topology

     Disaster Planning and Contingency

     High Availability and DR design

     Value and return on investment

     Data Center from the SAP perspective

As part of this process let’s now discuss in the comments to this document what

exactly the SAP Architecture Space should contain.

Everybody is welcome, this is a safe place so don’t be shy.

My personal goal in this discussion is for me to be less vocal and let everybody else

have a good debate.

(please do _not_ click LIKE for this Document, the purpose of this is not for collecting

points)

To report this post you need to login first.

5 Comments

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

  1. Shehryar Humayun

    Hi,

    Thanks for the initiative. This is going to get political…but in any case, even before listing what is included in NetWeaver Architecture, shouldn’t we first agree on which definition of the term “architecture” we wish to use as a reference?

    The second point is: should we aim to align NetWeaver Architecture with an overall architecture framework like SAP EAF or TOGAF?

    Regards.

    (0) 
    1. Andy Silvey Post author

      Hi Shehryar,

      thank you and welcome.

      The SCN NetWeaver Architecture Category is brand new, and has existed for only a month, and can be found here.

      This means we are right at the beginning which is an opportunity for everybody who is interested to get involved and influence and shape what I believe will become a very interesting sub community in the SCN.

      So please, feel welcomed to get involved here and reply to this discussion with your definition of the term architecture which could be an influence in the founding principles of this area of SCN.

      I absolutely agree with you that SAP EAF and TOGAF should be given respectable attention in the SCN NetWeaver Architecture Category and the community should be aligned with SAP EAF and TOGAF which as we know are aligned themselves.

      This is the perfect opportunity for a blog or series of blogs totally befitting to the community introducing SAP EAF and TOGAF, and explaing what they are, how they are used, how they are aligned, where to find information on them and training and how they are applied. Why don’t you blog that ?

      All the best, and welcome.

      Andy.

      (0) 
  2. José M. Prieto

    Hello,

    Thanks Andy for the initiative.

    So let me contribute to the definition of the term Architecture. In general for me, and from a very simplistic perspective, this term is the process that includes the planning, design and build of SOMETHING to meet a given set of REQUIREMENTS. So moving to “SAP NetWeaver Architecture” will bring particular meanings to the words SOMETHING and REQUIREMENTS. On one hand SOMETHING will become “NetWeaver as platform for running SAP solutions” and on the other REQUIREMENTS will become “business requirements”. Additionally NetWeaver as a platform is very technology-wise so the space should then be oriented to the technology architecture arena. Finally TOGAF or SAP EAF are nothing else than tools (or frameworks) that help us to orderly apply that process in more or less the same way.

    Other than this, I see pretty difficult to put boundaries to the space meaning these topics should be covered and those others should not. There will never ever be a general agreement for sure. I suggest any topic involving SAP NetWeaver as a technology platform as a mean to give an answer to business requirements and the procedures to get to that end may have a mentioned either as blog, document or discussion in this space.

    Cheers,

    José M. Prieto

    (0) 
    1. Andy Silvey Post author

      Hi Jose,

      I agree with you about the scope of Architecture, but also, I would like to see the Architects community on the SCN promoting and supporting SAP EAF and TOGAF because these help achieve precisely what you said, help us orderly apply the process.

      Orderly application of the process leads to common standards of design and coherance in design decisions.

      One of the worsts things which often happens is people put their finger in the air and design this, then someone else puts their finger in the air and designs that.

      Especially large organisations need standards to maintain consistency over time and SAP EAF and TOGAF will help achieve this hence I would like us all to lead the SCN Architecture Community in accordance with such an approach and encourage architects to use templates and frameworks for architecture decisions to keep landscape designs consistent across components where possible.

      All the best and thank you for joining in this discussion.

      Andy.

      (0) 

Leave a Reply