Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Scribd Logo
Upload

Welcome to Scribd!

  • 161 views

    Abap Vs Java Stack in Sap

    Uploaded by

    aniruddha_2012
    ABAP is SAP's native programming language and architecture, used for its core ERP systems. Java architecture was adopted when SAP acquired portal solutions and is used for web-facing products. Dual stack architecture runs both ABAP and Java on one system but has high operational costs, so SAP now recommends splitting these systems and consolidating features to reduce the need for both stacks.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd

    Abap Vs Java Stack in Sap

    Uploaded by

    aniruddha_2012
    161 views1 page
    ABAP is SAP's native programming language and architecture, used for its core ERP systems. Java architecture was adopted when SAP acquired portal solutions and is used for web-facing products. Dual stack architecture runs both ABAP and Java on one system but has high operational costs, so SAP now recommends splitting these systems and consolidating features to reduce the need for both stacks.

    Original Description:

    Abap vs Java Stack in Sap

    Original Title

    Abap vs Java Stack in Sap

    Copyright

    © © All Rights Reserved

    Available Formats

    DOCX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    ABAP is SAP's native programming language and architecture, used for its core ERP systems. Java architecture was adopted when SAP acquired portal solutions and is used for web-facing products. Dual stack architecture runs both ABAP and Java on one system but has high operational costs, so SAP now recommends splitting these systems and consolidating features to reduce the need for both stacks.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    161 views1 page

    Abap Vs Java Stack in Sap

    Uploaded by

    aniruddha_2012
    ABAP is SAP's native programming language and architecture, used for its core ERP systems. Java architecture was adopted when SAP acquired portal solutions and is used for web-facing products. Dual stack architecture runs both ABAP and Java on one system but has high operational costs, so SAP now recommends splitting these systems and consolidating features to reduce the need for both stacks.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    of 1

    How are JAVA, ABAP and Dual stack architecture differentiated in SAP?

    Can anyone explain all these 3


    architectures in details?

    Answer:

    In short, ABAP stack is what SAP had developed in house, in other words the native offering. ABAP stack
    is the foundation of SAP Business Suite and is also the foundation of the new S/4 HANA suite.

    It is a kind of "virtual machine" if you'd like to call it - providing a compiled language (ABAP)
    environment on various different Hardware platforms and realize 100% compatibility. Majority of the
    traditional SAP inter lecture property are actually built within the ABAP stack.

    In comparison Java stack was adopted when SAP acquired Top Tier portal solutions. It was not the first
    but the most serious and successful SAP entering Internet/web domain. As its name indicated, it uses
    JVM and the programming language in this stack is ... JAVA.

    Various "web-facing" SAP product leveraged JAVA stack extensively, most prominent of course is the
    SAP Enterprise Portal. But also SAP XI, PI, and PO serious solutions. There were SAP HR ESS, MSS, BW
    Java, features that used to use Java stack too (but are moving into ABAP).

    There were a period where "webb-ize" everything drove the product direction to dual-stack Which
    means one SAP system has two stacks: JAVA and ABAP sharing one identity. However as web is
    becoming ubiquitous, the dual-stack operational cost seems stayed relatively high due to the fact that it
    requires interaction of two pretty different product, and mentality.

    So what SAP now recommending is split the dual stack - for example you can still have BW and BI-JAVA,
    but they will be split into two systems and managed separately. The only dual stack system we still
    recommend is Solution Manager which is used to manage all your SAP systems, so understandably, you
    need this system to be both ABAP and JAVA.

    On a larger scale, SAP is also consolidating its features, and reduce the need for "both ABAP and JAVA".
    Many things like CRM ICC, HR ESS are nolonger require to be running in a separate (JAVA) stack. This
    made operating SAP system much less costly.

    You might also like