Skip to Content

In my previous posts I already explained The Enterprise Architecture show, The enterprise architecture show – episode 2, And …  Why  We  Need  the Enterprise  Architecture  Framework?. This post is about to explain why SAP so concerned about enterprise architecture.

 

SAP has been pushing Enterprise Service Oriented Architecture (e-SOA) for quite  a long time. E-SOA is based on SOA principles and extends SOA with SAP assets in the business world, our business applications. E-SOA lays  down an architecture that adopts SAP applications to SOA principles (Autonomy, Simple, well-documented interface, Flexibility and Unity). e-SOA enabled enterprises to create more flexible IT infrastructure to support more agile businesses using ASP applications and technologies.

 

To support SAP e-SOA architecture, SAP introduced set of technologies (such as NetWeaver), tools (such as CAF toolset), and services (such as ESA adoption program). As I already mentioned in SOA, It’s not about the IT It’s about the Business., although SOA is pushed by the IT world it can be successfully adopted by enterprises without the acceptances, understanding and supporting of the business side. If we need to compose a list of successful SOA adoption points, the first point will be getting the business people involved in the process. The second point will be a holistic view of the enterprise. Developing a service required knowledge and understanding of all the service consumers (both humans and machines). Such knowledge is required to set currently the interface and implementation of the service. To reach such knowledge and understanding we need to get a holistic view of the enterprise. Furthermore, without knowing what your current architecture is, what should be your future architecture, what are the gaps and how you’re going to close those gaps, you won’t be able to succeed.

 

Another point that should be addressed to gain success with SOA adoption is the right level of services granularity. Ending up with thousands of services or with few services won’t help the service oriented architecture adoption. Enterprises need to find out the right service granularity for them. This granularity should be wider enough to enable flexibility and narrow enough to enable people to use them and communicate between them.

 

If you’ll look today for a methodology that will give you  a  holistic view of the enterprise and will guide you  as to  how to map your existing architecture, map your target architecture, identifying the gaps, set time-lined projects to close the  gaps  and governing the entire process; you’ll find out that enterprise architecture is the methodology you  are  after.

 

SAP is not just  an  application and technology provider; we are also partners of our customers, partners with deep knowledge and experience in 22 industries. As a partner with business oriented attitude we see both SOA and enterprise architecture as concepts, architecture and methodology that will help your business. Pushing enterprise architecture from our  perspective has two objectives 1)  Provides help for  your business  and for you  to get  a  better understanding of current architecture and what needs  to be changed . 2)  Provides help with SOA adoption. Those two objectives support the same goal: making   your business more agile and successful.

 

Natty Gur

To report this post you need to login first.

6 Comments

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

  1. David Halitsky
    “If you’ll look today for a methodology that will give you  a  holistic view of the enterprise and will guide you  as to  how to map your existing architecture, map your target architecture, identifying the gaps, set time-lined projects to close the  gaps  and governing the entire process; you’ll find out that enterprise architecture is the methodology you  are  after.”

    But I think that anything good can always be improved; if not, the consumer economies of the West would have fallen a long time ago because in the long run,  marketing can’t be relied upon to do everything.

    So for that reason, I’ll be posting soon about the BAPI “REPMANCONF1_CANCEL” in relation to the “Post With Correction” toolbar button of transaction MFBF.  This simple example will suffice to shed some light on how close the SAP community is or isn’t to two of the priaseworthy goals you mention:

    being able to successfully map an existing architecture

    being able to successfully map a target architecture

    (0) 
  2. Maxim Efimov
    Great post, Natty! Granularity of service is a good start, but I think even more important is reusability of service for adoption of ESA… By concentrating on granularity along one can introduce artificial standards for web services development. On the other hand, without providing clear guidance one will introduce ambiguity in development process and leave to a chance and individual interpretation of a given developer…
    (0) 
    1. Natty Gur Post author
      Thanks Maxim. I totally agree. It look to trivial to me that I didn’t mention it, but you’re totally right . service reusability is important aspect that can and must be achieved by enterprise architecture work.

      Thanks again!

      (0) 
  3. W. Janssen
    Clear post. One thing I don’t really get though. You mention that soa is IT driven and doesn’t need acceptance from the business side.

    “although SOA is pushed by the IT world it can be successfully adopted by enterprises without the acceptances, understanding and supporting of the business side”

    Seen the impact of adopting soa on the entire enterprise, I thought soa needs acceptance of both sides, IT and business side.

    (0) 
    1. Natty Gur Post author
      apparently I wasn’t clear enough,

      “soa needs acceptance of both sides, IT and business side” thats completely right. the problem is that in most of the enterprises today, SOA accepted by IT but not by the business side.

      (0) 

Leave a Reply