Discuss business intelligence, integration, compliance and a host of other SAP-related topics – implementation, best practices and resources to negotiate the world of SAP better!

« Mobile Business Intelligence - Part 2 | Main | Individual Process Quality aspects in SAP ERP (HCM )- Part 3 »

Architecture Plan for SAP Netweaver based Solution

Architecture for any IT based solution is a most important factor for aligning IT with business expectation. This also facilitates a transparent and manageable roadmap for most adaptable and efficient system landscape. An effective architectural design of a solution helps business to fulfill their target in an open, scalable and easy to handle infrastructure. This blog will focus on approach of an architecture design for SAP Netweaver based solution.

 Before starting an architecture design, first make a decision about the platform on which the solution will be built. As this blog is considering SAP Netweaver based solution as an example, the solution in discussion will be built on SAP Netweaver platform. First step is to consider Basic Architecture of the decided platform for the solution. It means the basic architecture of Netweaver based solution is briefed in a refrigerator-type diagram as shown below:

Ranjeet01.jpgOnce basic architecture is defined, we need to go through the use cases for the solution. Based on the use cases, the decision has to be made on component of Netweaver stack to be used for solution design. For example, use case says develop a User Interface which will be used to display analytical reports based of user's input data. Based on this use case, solution needs at least Portal, Business Intelligence (BI) and J2EE application server. This is the minimum component required to fulfill the use case requirement. So this is the second step for defining architecture for a solution and is called minimum infrastructure based on solution concept.
The third step is to finalizing different components required to implement this solution and is called minimum infrastructure with respect to SAP product. Different phases involved with solution implementation are Blueprint, Build, Execute and lifecycle management. In this step, SAP product has to be outlined for different phases of solution implementation. For example, to build portal based application, we need Netweaver Development Infrastructure to manage coding other than portal application server. Other different products might require are CTS+ for transport, NWA for administration and others.
Once all products decided for solution implementation, the last and final step is detailed solution deployment infrastructure. This step can be achieved by applying different architectural/deployment principles applicable for the selected products and recommended best practices for those products. Based on this step, an architect can revisit the decision made in previous step to give more effective design.

Below content showcases the points discussed above:

  1. Base Architecture(Solution IT platform)
  2. Minimum Infrastructure (Based on use case concept): Influenced by Solution Use Cases
  3. Minimum Infrastructure (Based on SAP product)
  4. Detailed Solution Deployment Infrastructure: Influenced by Architectural Principles, Deployment Principles and Best Practices.

Post a comment

(If you haven't left a comment here before, you may need to be approved by the site owner before your comment will appear. Until then, it won't appear on the entry. Thanks for waiting.)

Please key in the two words you see in the box to validate your identity as an authentic user and reduce spam.

Subscribe to this blog's feed

Follow us on

Blogger Profiles

Infosys on Twitter