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....

Initial settings for the BI folks to run Portal

10 times out of 11, the BI Consultants I have met have cumbersome laptops and insane browser settings. Not to forget ... the missing software and constant bickering that Portal Sucks !!

Here I am, helping them feel easy at work by giving them some tips to follow before you constantly scratch those Portal Dudes !!

Add the Portal and BI systems in your browser
Within Internet Explorer, you should make sure that you add your SAP NetWeaver Portal and BI systems to the list of trusted sites within Internet Explorer. This is available through the Tools -> Internet Options -> Security -> Trusted Sites -> Sites area.

Within Internet Explorer, you should make sure that you add your SAP NetWeaver Portal and BI systems to the list of sites that can always use cookies. This is available through the Tools -> Internet Options -> Privacy -> Sites .

JAVA script settings:
Within Internet Explorer, you should check your advanced tab settings. Also, a requirement is to ensure that JavaScript is enabled for your internet explorer browser. If you disable JavaScript, your page and portal won’t load. See this Microsoft guide on how to enable javascript on your client browser.
On the Tools menu, click Internet Options, and then click the Security tab.
Click the Internet zone.
If you do not have to customize your Internet security settings, click Default Level.
If you have to customize your Internet security settings, follow these steps:a. Click Custom Level.b. In the Security Settings – Internet Zone dialog box, click Enable for Active Scripting in the Scripting section.
Click the Back button to return to the previous page, and then click the Refresh button to run scripts. If it is not, see this Microsoft hotfix page http://support.microsoft.com/kb/871205 for a resolution to this issue.

HTTP Content
If you’re having issues with IE such that it won’t decompress HTTP Content on IE 6 SP2. Ensure that your wininet.dll file is at the following version for IE 6 SP2

Next, add your local domain to your trusted sites in Internet Explorer. If you can’t add the entire domain, add the ABAP and JAVA systems manually. If you’re still having issues with Internet Explorer 6.0 and you’ve followed all these steps, I suggest using HTTP Watch or another http trace program and check your http return codes when loading pages and also use the JavaScript debugger to get a better idea of the types of JavaScript errors you are receiving. Then search Microsoft’s Knowledge Base articles at http://support.microsoft.com/.


MSHTML.dll
In addition, you need the latest version of the mshtml.dll version for Windows XP SP2. This is mentioned and available in this Microsoft hot fix: http://support.microsoft.com/kb/917425.

Setting up Internet Explorer 7.0
Internet Explorer 7.0 is supported for NetWeaver as of SPS10.
Installing Latest Version of .NET 1.1 framework
Download and install the latest version of Microsoft .NET Framework 1.1. Currently, there is a version 2.0 available, but 1.1 is required. See OSS note 877774 for details. Keep in mind this must be installed BEFORE SAPGUI or the BI Addon is installed. http://www.microsoft.com/downloads/details.aspx?FamilyID=262d25e3-f589-4842-8157-034d1e7cf3a3

Install Microsoft Visual J# .NET
This is a new Prerequisite (Note 964495): You need have installed "Microsoft Visual J# .NET Version 1.1 Redistributable Package" http://www.microsoft.com/downloads/details.aspx?FamilyId=E3CF70A9-84CA-4FEA-9E7D-7D674D2C7CA1&displaylang=en

Installing MSXML Parser
The latest version of Microsoft XML Parser should be installed. MSXML parser comes installed on Windows XP machines, but if you’re using a prior operating system, you may need to install it. Also, you should make sure the version you are using is up to date. MSXML Parser is required for Visual Composer designtime. Currently, the latest version is MSXML Parser 6.0 which is located at: http://www.microsoft.com/downloads/details.aspx?FamilyID=993c0bcf-3bcf-4009-be21-27e85e1857b1&DisplayLang=en

Installing Adobe SVG Viewer
Download and run Adobe SVG Viewer 3.0 http://www.adobe.com/support/downloads/product.jsp?product=46&platform=Windows Adobe SVG Viewer is required for all users that will use the Visual Composer Designtime. It is not required for any runtime users or for any other BEx tools (at least it isn’t required yet …)

Installing Adobe Flash Player
Download and Install Adobe Flash Player (v7.0+) - plug in for Internet Explorer 6.0 Adobe Flash Player is required for Visual Composer (both designtime and runtime). This is located at: http://www.adobe.com/shockwave/download/download.cgi?P1_Prod_Version=ShockwaveFlash

Verify SAPGUI Settings for BI
In excel, go to Tools -> Macro -> Security -> Trusted Publishers Verify the SAP AG certificate and make sure “Trust Access to Visual Basic Project” and “Trust all installed addins and templates” are checked. Run C:\Program Files\SAP\FrontEnd\Bw\sapbexc350.xla and ensure there are no red files… Run C:\Program Files\SAP\FrontEnd\Bw\sapbexc700.xla and ensure there are no red files…
Server Side Settings
Step 1 – Ensure that your ABAP and JAVA systems are on the same fully qualified domain name. There are numerous cross-domain issues that could occur. Also, ensure that all communication server side is using the fully qualified domain name. Step 2 – You may be missing style elements which could cause incorrect rendering. If you are still having issues, try switching to an SAP Delivered Theme instead of Custom Theme on the Portal.

Hope this blog helps the BI folks and ofcourse the Portal DUDES !!!

Email Connectivity in SAP Netweaver Portal

Sending Emails from the Portal is a key functionality for Collaboration and certain KM services. Below is a step by step configuration of Email in Portal.

Create the system Object for the Microsoft Exchange Server

Use the SMTP server address

Create the Alias for the system object

Configure the email service

System Administration > System Configuration > Content Management > Global Services > Mailing Services > check for the tick sign in the Active section.

Creating an Email Transport

System Administration > System Configuration > Collaboration > Transports

System Administration > System Configuration > Collaboration > Transports > Mail Transport > Click New > use the SMTP address

Make sure you have the collaboration link activated on the portal to test this functionality.

Check your email for the response..

I hope the above configuration was simple enough....

Flavors of EP

One of the hottest topics on SDN is the versions of EP. In this blog I have focussed on 4 different areas:
Running an Enterprise Portal
Collaboration
Knowledge management
Mobilizing Business Processes
(Click on the image to see a larger version)

URL in SAP Netweaver

Short URL

Easy way:

Step 1:

Click on add to Browser favorites in the page title bar in the right-top corner of the page.

Check the favorites and determine the URL link for the iView.

Hard way:

STEP1: Go to a PCD object in the Portal content directory and determine the path under PCD location properties.

Step 2: Copy the link and go to system administration > navigation > short URL >

Step 3: Type ROLES:// followed by the PCD location and determine your short URL.

Step 4: concatenate the URL (check the below example) For example, the user mapping iView can be displayed with the following URL: http://myServer:50000/irj/portal?NavigationTarget=

ROLES://portal_content/every_user/general/eu_role/

com.sap.portal.portal_personalization/com.sap.portal.persoUserMapping

A short version of the URL might be the following, with the navigation target hashed and shortened: http://myServer:50000/irj/portal?NavigationTarget=navurl:

//b3d6d9ebac16a46574d62757803b05d4

I know it’s goofy to add a hard and easy way to work this but the hard way is for the GEEKS!

And of course the Slackers enjoy the easy one J

URL for Portal Quick Links:

Quick links are shortcuts to iViews and pages. Each quick link is a string that you add to the default portal URL in order to navigate to a specific iView or page. Quick links provide a meaningful name for iViews and pages to which users may want to navigate.

For example, if the base address of the portal is http://myServer:50000/irj/portal and the quick link to the page is email, a URL to the page would be: http://myServer:50000/irj/portal/email

Portal Theme Editor Concept

Prior to 7.0 version of Netweaver the idea of changing the web templates of BI Reports were completely dependent on modifying the contents in the BWReports.css cascading style sheets in the MIME repository via T-code SE80. The various elements in the file were edited using a CSS editor and later imported back with the respective changes. With the changes the reports were generated on a web browser and the template would adapt the cascading style sheet that was modified. These URL’s were later linked to the Portal or sometimes a different application.

Now things have changed a bit. The concept of Portal Theme Editor has taken precedence over the use of the MIME objects in the backend BI system. Developers can now use this editor as a central editing location for all the web applications that are executed in the Portal browser. Just for clarifications or for some naïve learners, Web Templates are created in the Web Application Designer (BEx Tool), these web templates when executed on a browser is called BEx Web Application and this Bex Web Application when executed on a Portal Browser is called a BEx Web Application iView.

So getting back to the point after taking the beginners detour, these web applications can be assigned a specific Portal theme by using certain components in the Theme Editor. Some of them are Global Formats Content Area, Complex Elements, Basic Elements, and Component-Specific Formats.

Lets feed the baby using a spoon and follow the below steps to achieve the invincible: Execute the BEx Web application in the Web browser and Decide what needs to be changed. Open the same as a template in your WAD and identify which web item needs to be changed and use the theme editor to make the necessary changes. (System admin > portal display)

Now let’s get graphical. Consider the below screen print. It is an example of a standard web application as seen on a BEx web analyzer.

(Click on image to see a larger version)

To change or modify certain parts of the template consider the below screen prints:

BI-Portal

Configuration of BI and Portal

You can summarize the configuration in three main topics:

1. Communication

2. Single Sign-On (SSO)

3. User Management

You have to setup both directions for communication:

1. Java to ABAP communication

2. ABAP to Java communication

For communication, the RFC/JCo protocol and HTTP(S) web protocol are used. Communication is used to create and display BI content in the Portal. Communication is used to display Portal content in BI (e.g. BEx Information Broadcasting shows Knowledge Management folder). See note 888687 for technical details.

For Single Sign-On (SSO), you have to ensure that Java and ABAP trust each other:

1. Java is trusting ABAP

2. ABAP is trusting Java

Single Sign-On (SSO) is working with SAP Logon Tickets. SAP Logon Tickets are created with the help of certificates and could be validated with certificates. Therefore, certificates must be exchanged between Java and ABAP.
Certificates consist of a public key and optionally of a private key. The private key of certificate is required for creating and signing SAP Logon Tickets. The public key of certificate is used for validating SAP Logon Tickets.
SAP Logon Tickets are digitally signed with the private key of the issuing system's certificate. They contain the user ID, authentication scheme, validity period, issuing system and digital signature but they do not contain any passwords. SAP Logon Tickets are validated with the public key of the issuing system's certificate (the public key is located in System PSE or TicketKeystore). They are only accepted if the issuing system is part of Single Sign-On Access Control List (ACL) or EvaluateTicketLoginModule in the validating system. Reports to Run:

1. RSPOR_SETUP

1. Execute the report RSPOR_SETUP with transaction SE38 (or SA38; or you can execute the report from the SAP Reference IMG, see Documentation below)

2. Use value help of entry field Program ID (or RFC Destination) to choose __ as RFC Destination (this destination is created by the Template Installer)

3. Enter Portal SID (required to check step 10)

4. Press button Execute

2. RS_TEMPLATE_MAINTAIN_70

Run Report RS_TEMPLATE_MAINTAIN_70 and Enter Template ID 0ANALYSIS_PATTERN > Choose Program / Execute
Choose Analyse / Validate , Choose Analyse / Execute in Debug Mode ,A Web Browser is opened and you have to logon to the Portal. Finally, an empty Analysis Pattern (without data) should appear. After these tests you can continue your testing by creating and using your own Queries (with BEx Query Designer), Web Templates (BEx Web Application Designer) and Reports (BEx Report Designer).

SSO2 Wizard

SAP released a Note 1083421 . There is a wizard called SSO2Wizard_700.ZIP which you can download from the Note. This note is valid since 23.12.2007 , so I have to conclude this is fairly new. The wizard when downloaded can be accessed via the Portal URL followed by /SSO2

OK...so this can help SSO logon ticket issues from the ABAP side and it automatically checks for inconsistencies. Its like the template Installer or the Support Tool we have for BI.

Netweaver BI and how does it support SOA?