BEx Web Applications Java - Analysis of Session Management

You want to analyse if sessions are properly released on the J2EE engine
after executing one or more BEx Web Applications Java.

Logon to the following URL to start the session overview: FQDN/irj/servlet/prt/portal/prtroot/com.sap.ip.bi.web.portal.integration.sessionoverview
Note: The user needs to have administrator authorization.
Start transaction SM04 in the ABAP backend.
The session overview shows:
Current date:
Controllers: <# of controllers>
Applications without page: <# of applications without page>
Applications with page: <# of applications with page>
Portal connection pools: <# of portal connection pools>

SM04 shows the RFC connections opened from J2EE engine to ABAP backend.

Execute the session overview twice:
1) Before executing the BEx Web Applications Java
2) After terminating the BEx Web Applications Java

Note: A BEx Web Application session is terminated, e.g. when:
- navigating to another page
- using the logoff button
- closing the browser window

The numbers for <# of controllers>,

<# of applications without page>,

<# of applications with page>, and <# of portal connection pools>

must be the same before and after executing the BEx Web Applications Java. Otherwise there is a problem in the session management that requires further analysis.

Execute the SM04 after terminating the BEx Web Applications Java.
Note: In transaction SM04 you will see a connection of type RFC for each BEx Web Application Java.
Important: Terminating a BEx Web Application will not release the RFC connection in SM04. This behavior is due to the RFC connection pool of the Enterprise Portal. The RFC connection will be returned to the connection pool and will be reused when doing a re-logon. Therefore the proper release of sessions of BEx Web Applications Java cannot be analysed with SM04. SM04 will only show that the memory consumed on the
ABAP stack will be freed after a successful termination.
1) Start the session overview. See the number of controllers

Start the BEx Web Application

Refresh the session overview. See the number of controllers:

Start SM04. See the memory consumed in the ABAP backend:

Terminate the BEx Web Application (e.g. by closing the browser window):

Refresh the session overview. See the number of controllers

Java for FOOD ! part-1

Java became popular with the Internet as a language of the World Wide Web. Life was added to the static HTML pages using Java script and with the CGI (Common Interface Gateway) simple databases can be performed and the results are displayed in the browser.
However these technologies are limited in the case of simultaneous accesses from very large number of users who can retrieve with quick response time.
SUN provides a solution to these problems in terms of server side architecture for Internet applications with the Java 2 Platform Enterprise Edition .

J2EE is a vendor standard for a set of software components which are basically created in Java programming language. To create cross platform Java programs a JDK or a Java Devlopment Kit is required which includes the software required to create and test Java applications and applets, the packages with the java classes that are a part of the basic configuration. The software can be accessed via the link http://java.sun.com/j2se/1.4.2/download.html
the software includes the java compiler, the Java runtime environment (Java Virtual Machine) for running the applications , the applet viewer for runnning the applets, a java debugger and other utilities.

The use of J2EE in SAP has several advantages such as :
the open integration architecture SAP Netweaver integrates with the openness of J2EE.
It provides the platform independence and web services technology supported directly by java heavily used in SOA.
The J2EE Connector architecture allows standardized integration of external services.

more on part 2....