J2EE n ABAP Stack

[Former Member]

Dear Experts...........

Plz throw some light on J2EE stack and ABAP stack.

Their functinalities and differences...........

Reward points will be given if found helpful..

Thanks

AMD

[Former Member · Accepted solution]

hi Abhishek,

XI opeartion are distributed among two servers one is ABAP and JAVA.

ABAP Stack: Integration Engine, BPE

Java: Adapter Engine, SLD, IR, ID

SAP has come with ABAP and all its operations need to go with ABAP server but keeping in mind about market they went to java stack so that other componenst can be plugged in to SAP EASILY.

SAP has modules like ENTERPRISE PORTAL ,webdynproruns on java stack.

all abap related programs runs on abap.

so by maintiangin 2 servers ABAP AND java SAP is able to come with various modules which are called as SAP netweaver stack.

coming to XI all adapter related components runs on java. and mapping programs runs on abap.

these two server are communicated with FAST JCO RFC.

[Former Member]

Hi,

Java stack comprises of Integration Builder , SLD, Runtime workbench and adapter engine .

Abap stack comprises of Integration engine, Business proces eningeAlso HTTP and Idoc adapter are locateed in Abap stack

Java stack is used to desing and configure the objects and converting data,,

Abap stack is used to execute the pipe line configuration .

Difference : - Abap stack execute the piple line steps where as java stack designs and configures the objects.

thanks

[rodrigoalejandro_pertierr]

hi,

read this

SAP NetWeaver is based on a dual-stack architecture based on ABAP and Java. While ABAP has been with SAP for years and provides a robust and scalable development and runtime environment for any type of business programming, Java is based on open standards and leverages SAP NetWeaver to the broad community of Java developers. In a service-oriented environment, however, the programming languages boundaries disappear, since components written in one language (for example, ABAP) can expose their capabilities as services that are used by components written in another language (for example, Java). The interoperability is achieved through Web service standards that have been implemented for both stacks. Likewise, SAP’s user interface strategy is built on top of the Web Dynpro programming model that is supported seamlessly both in the Java space and in the ABAP space.

The question of which environment you should use when depends on a couple of criteria that have to be weighed up carefully.

ABAP’s strength lies in its proven application server architecture. The language is based on a strong integration of OPEN SQL and manages large data sets known as internal tables. This allows use of ABAP in transaction-oriented environments with good performance. The development environment (ABAP Workbench) is tightly integrated in the application server. Since ABAP is essentially a server-based development infrastructure, working in large development teams is organized by the correction and transport system in a distributed development landscape. ABAP support a variety of data types that are optimized for business processes. Many important engines in SAP NetWeaver, such as the BI OLAP engine or the XI integration engine, are implemented in ABAP.

Java focuses more on the user-interface side although more and more applications make use of the entire Java stack from user interface to business logic and persistence. Many of the ABAP scalability features have been adapted for the Java stack, such as the proven scalability by means of a J2EE dispatcher and J2EE server nodes (that correspond to the ABAP dispatcher and work processes). The NetWeaver Development Infrastructure organizes distributed development in teams by means of central repository, build and transportation services similar in philosophy to ABAP’s change and transport system. However, there are subtle differences that have to be taken into account. Java development is carried out on the client side in the NetWeaver Developer Studio. A local J2EE engine makes it easy for Java developers to work offline and subsequently integrate their work into a central test system. Sources are checked out locally so that you only need to connect to the development infrastructure from time to time. SAP has implemented a lot of SAP NetWeaver components in Java such as the J2EE server itself, the Portal, the Developer Studio to name just a few.

ABAP and Java are code-based environments. Although they offer model-driven and highly graphical tools, such as the Web Dynpro View Designer and the Web Dynpro Data Modeler, you end up in editor and debugger sessions, since most of the developer’s work has to be done here. This excludes other types of roles, such as the business analyst, who typically has a lot of technical insight, but lacks coding skills in most cases. Here, SAP focuses on purely model-driven tools, such as the Visual Composer. The Visual Composer allows you to model the flow of your application or iView, helps to integrate various data sources, and makes deployment to the portal easy. It enables rapid prototyping.

Finally, it is important to note that SAP NetWeaver is in transition from an integration platform to a composition and business process platform.

Composite applications can be developed on top of SAP NetWeaver and are supported by the SAP Composite Application Framework (CAF) and Guided Procedures.

Both technologies accelerate composition on top of SAP NetWeaver, but are integrated in the Developer Studio and leverage existing technologies such as Web Dynpro and Adobe Forms integration.

Thanks

hope helps

Rodrigo

[Former Member]

Hi,

XI consists of ABAP and JAVA Stacks.

Integration Engine and the Integration server sits on ABAP Stack.Integration Server runs on ABAP Stack

The processed XML messages can be monitored in SXMB_MONI which again resides in ABAP Stack.

Adapter Framework,IR, ID, SLD,Runtime work bench are all developed on JAVA Stack.

Hope this will help you.

Best Regards

Sushama

[aashish_sinha]

Hi,

java - adapter engine, integration builder

abap - integration server (BPE, IE), Idoc-HTTp adapter

Java stack and Abap stack communicate with each other through JCO call ( Java Connector)

please go through links::

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/media/uuid/4aa47d27-0a01-0010-5db4-bb62dfc8c0...

Regards

Aashish Sinha

PS : reward points if helpful

[Former Member]

Difference between the ABAP Stack and the J2EE stack are:

Integration Engine and the Integration server Idoc-HTTp adapter sit on ABAP Stack . Execution of the IS part will be done on ABAP Stack. we can monitor the processed XML messages also in SXMB_MONI( ABAP Stack)

Adapter Engine sits on JAVA Stack. All the IR, ID, SLD, RWB Application are developed on JAVA Stack, hence we need JAVA Webstart to run these Applications

All the Adapter related Errors can be checked in RWB, Communication channel monitoring( Developed and sits on JAVA stack)

Java Stack functionality:the functionalities of java stack is used to design and configure the objects and converting data,,

ABAP Stack Functionality: the functionalities of ABAP stack are executing the pipe line configuration .

The difference b/w abap and java stack are ....abap stack execute the pipeline steps where are java stack design and configure the objects.

SAP has come with ABAP and all its operations need to go with ABAP server but keeping in mind about market they went to java stack so that other components can be plugged in to SAP EASILY.

SAP has modules like ENTERPRISE PORTAL ,webdynpro which run on java stack.

all abap related programs runs on abap.

so by maintianing 2 servers ABAP AND java SAP is able to come with various modules which are called as SAP netweaver stack.

coming to XI all adapter related components runs on java. and mapping programs runs on abap.

these two server are communicated with each other through JCO RFC.

Please reward points if helpful.Thanking you

[Former Member]

hi Abhishek,

XI opeartion are distributed among two servers one is ABAP and JAVA.

ABAP Stack: Integration Engine, BPE

Java: Adapter Engine, SLD, IR, ID

SAP has come with ABAP and all its operations need to go with ABAP server but keeping in mind about market they went to java stack so that other componenst can be plugged in to SAP EASILY.

SAP has modules like ENTERPRISE PORTAL ,webdynproruns on java stack.

all abap related programs runs on abap.

so by maintiangin 2 servers ABAP AND java SAP is able to come with various modules which are called as SAP netweaver stack.

coming to XI all adapter related components runs on java. and mapping programs runs on abap.

these two server are communicated with FAST JCO RFC.

Thanks & Regards,

Rama Krishna

Edited by: rama krishna talluri on Mar 6, 2008 10:30 AM

Edited by: rama krishna talluri on Mar 6, 2008 10:31 AM

[Former Member]

Hi AMD,

ABAP and Java stacks in NW are so called usage types, which you need in order to implement certain IT scenario. You can find detailed information about those usage types in the service marketplace. There is installation and upgrade documentation and the document is the Master Guide. You may also refer to the technical infrastructure guide which is located at the same place.

There is no differentiation between both stacks, you just need each of them to implement certain IT scenario.

If you have troubles finding the docs in the marketplace let me know and I will give you exact location.

Regards

Azahar

[Former Member]

Hi

J2ee stack----> core on which java based components in XI run

ABAP stack---> core on which ABAP based components in XI run

regards

krishna

[Former Member]

Hi,

XI consist of both abap and java stack

java stack: Integration Builder , SLD runtime workbench..adapter engine .

the functionalities of java stack is used to desing and configure the objects and converting data,,

abap stack: Integration egnine business proces eninge and http and idoc adapter are located in abap stack..

the functionalies of abap stack are executing the pipe line configuration .

The differeance bw abap and java stack are ....abap stack execute the piple line steps where are java stack design and configure the objects.

thanq

krishna

[Former Member]

Hi

Components iof ABAP and Java stack in XI are

java - adapter engine, integration builder

abap - integration server (BPE, IE), Idoc-HTTp adapter

Java components are monitered in RWB and in Integration engine we monitor messages in SXMB_MONI

Integration Broker is located in ABAP stack and in JAVA stack we will design and configure the objects

Adapter engine is J2ee based adapter engine and it home for majority of Xi adapters

Edited by: Ashok Reddy Thatigutla on Mar 6, 2008 10:25 AM

[Former Member]

Hi,

XI consists of both ABAP + JAVA Stacks

Difference between the ABAP Stack and the J2EE stack are

Integration Engine and the Integration server are sits on ABAP Stack. Alll the Execution of the IS part will be done on ABAP Stack. we can monitor the processed XML messages also in SXMB_MONI( ABAP Stack)

Adapter Engine will be there on JAVA Stack. All the IR, ID, SLD, RWB Application are developed on JAVA Stack, so thats why we need JAVA Webstart to run these Applications

All the Adapter related Errors we can see in RWB, Communication channel monitoring( Developed and sits on JAVA stack)

Regards

Seshagiri

Edited by: N V Seshagiri on Mar 6, 2008 10:12 AM