Hi Keerthi,
SAP started writing software on mainframe systems. They eventually
expanded to distributed open systems (i.e. UNIX). They created their
own programming language (ABAP/4) either to have total control over the
software environment or to avoid having to license someone else's (or
both). They used their own ABAP language to create the server software.
Older SAP systems were ABAP-only systems. Older SAP systems were not
web-friendly (and did not support HTTP). SAP built middleware like ITS,
IGS & Business Connector to bridge that gap.
Newer SAP systems will support HTTP and web functionality in ABAP, but I
hear it's not the best development environment (not being a developer
myself). SAP introduced the java stack to extend the functionality of
the ABAP stack (particularly in the web world), and to provide customers
with a more 'standard' development platform. There are many more java
programmers than there are ABAP programmers making it easier to source
talent.
The SAP application instance (for current versions) can be created as a
stand-alone ABAP, stand-alone Java or dual-stack ABAP/JAVA instance
type. Application instance types can be mixed within the same system
instance. The SAP system is uniquely identified by the SID (system ID).
The SAP application instance is uniquely identified by the
SIDhost2-digit-system#
The core business logic (general ledger, A/R, A/P, HR) resides in ABAP,
and not in Java. Java is certainly used to facilitate access to the
core business logic through various channels (ex. SAP Enterprise
Portal).
Regards,
kk
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.