Skip to Content

How I use my TOGAF/SOA Skills in Solution Architecting around Netweaver Technologies – Part 2

This blog is not a solution or implementation methodology, I’m blogging on what I have learned and how I’m using the same on my everyday work. Intention is to visualize the scope of service oriented architecture and how we can practice; it’s purely my thoughts from my learning’s. 

Intention of choosing SOA/ESOA in each case that I work on is to implement a concrete infrastructure, using real-world standards such as web services and various networking and programming languages and protocols. Model that we select likely introduce additional elements such as security, management, service composition, and more.. In fact, it is envisioned that architects may use several reference models for a specific architecture including process-oriented models, network models (such as the OSI 7 layerstack) and more.

An architect who places several services in their architecture will need to consider who will be using the services and how they will be able to find and bind to the services. Some of the aspects of this will be handled by the underlying transport; other aspects may be best served by the architect using a service registry as a persistent.

I start working on design by doing the following,

  • Identify entities that can serve as services.
  • Establish visibility between service providers and consumers.
  • Identify/define interaction-mediated if not already available.
  • Define effective usage of services.
  • Have descriptions associated with services.
  • identify the execution context required to support interaction.

The ease with which the above elements can be identified within a given SOA-based system could have significant impact on the scalability, maintainability and ease of use of the system.

Now it’s time to look at best practices, consulting-conceptual-portfolio, elements that we look for and make use of are

     1. Business strategy
     2. Business process Innovation
     3. Modeling
     4. RoadMap
     5. Organization and governance
     6. Value assessment

Once we have all the elements above we can actually jump start on implementation using tools provide by SAP. My next blog is on how I use BPM/BRM in composition. 

Be the first to leave a comment
You must be Logged on to comment or reply to a post.