Doubts....!!!!!

[Former Member]

Hi All,

I just wanted to know the <b>-></b>

1)Difference between Application Server and Presentation Server.

2)Difference between proxy classes and global classes[In CFW View].

3)Difference between Application and System events.

Please Do Help.

Waiting for the response...

Regards,

Simy.

[Former Member]

Difference between Application Server and Presentation Server ?

Presentation server: the system(our front end) with which we connect to SAP is the presentation server.its our local system.

Application server : the system where total requests are received and processed and sends response is the Appl system in SAP.

Regards

srikanth

[anversha_s]

hi

Look at this,

<b>System Events (Default)</b>

The event is passed to the application server, but does not trigger the PAI. If you have registered an event handler method in your ABAP program for the event (using the SET HANDLER statement), this method is executed on the application server.

Within the event handler method, you can use the static method SET_NEW_OK_CODE of the global class CL_GUI_CFW to set a function code and trigger the PAI event yourself. After the PAI has been processed, the PBO event of the next screen is triggered.

The advantage of using this technique is that the event handler method is executed automatically and there are no conflicts with the automatic input checks associated with the screen. The disadvantage is that the contents of the screen fields are not transported to the program, which means that obsolete values could appear on the next screen. You can work around this by using the SET_NEW_OK_CODE method to trigger field transport and the PAI event after the event handler has finished.

<b>Application Events</b>

The event is passed to the application server, and triggers the PAI. The function code that you pass contains an internal identifier. You do not have to evaluate this in your ABAP program. Instead, if you want to handle the event, you must include a method call in a PAI dialog module for the static method DISPATCH of the global class CL_GUI_CFW. If you have defined an event handler method in your ABAP program for the event (using the SET HANDLER statement), the DISPATCH method calls it. After the event handler has been processed, control returns to the PAI event after the DISPATCH statement and PAI processing continues.

The advantage of this is that you can specify yourself the point at which the event is handled, and the contents of the screen fields are transported to the application server beforehand. The disadvantage is that this kind of event handling can lead to conflicts with the automatic input checks on the screen, causing events to be lost.

Hope u understood.

anver

if hlped mark points

[anversha_s]

hi simy,

again..

If you consider the R/3 Architecture of SAP, client workstations is the the <b>presentation layer</b>, <b>applications servers</b> are the application server layer and the actual data storage device is the database layer. WIth the help of application server, you can share the load across different servers and manage a show where the number of users are huge.

Suppose you want to load data from flat file and you want to automate it, you have to put these files in the application server rather the client workstation. So process chain IPs can pick data only from application server.

rgds

anver

if hlped mark points