SAP AS ABAP Administration · AS ABAP Architecture & Instances

In a (legacy) double-stack system, how were ABAP and Java kept apart yet connected — and why does modern SAP avoid this design?

Answer locked. Get the free KnowCard app to reveal it — plus spaced-repetition review so it actually sticks.

This is one card from the KnowCard library — thousands more across SAP, Linux, Python and more. In the app you get the answer, AI explanations, and cards that come back right before you would forget them. Free to start on iOS, Android or the web.

More in AS ABAP Architecture & Instances

You inherit a server whose instance name starts with 'D', so a teammate insists it only runs dialog work. Why is that assumption wrong?

In a multi-instance SAP system, which single component decides which instance is called the 'central instance', and what are all the others called?

A colleague spins up a full SAP NetWeaver AS with the database, application, and presentation all running on one host. What is the only legitimate use for that layout?

In some CRM scenarios with a mobile frontend, SAP inserts a fourth layer into the classic three-tier stack. Where does it sit, and what is it called?

What single architectural fact turns an ordinary SAP system into what SAP calls a 'distributed system'?

Beyond running work processes, what core services does the primary application server (PAS) instance provide that make it mandatory in every AS ABAP system?

Start learning today

Free to start — download the app or use it in your browser.