SAP EP – Netweaver Portal

Symptom
This is the Central Note for Ajax Framework Page with SAP NetWeaver Portal.
Other terms
AFP, Ajax Framework Page, Navigation, SAP Signature Design
Reason and Prerequisites
This note serves as an entry point for issues that relate to the Ajax Framework Page (and in particular the Navigation). It describes how to enable “SAP Signature Design” theme for SAP NetWeaver Portal and lists the known limitations when working with the Ajax Framework page.
Solution
Introduction
The “SAP Signature Design” is SAPs visual design that offers a harmonized user interface for SAP’s diverse products as well as an advanced interaction theme. It is technically based on a new portal theme (font types and size, color scheme, etc.) and can be integrated into the Ajax-based Framework Page (layout, header, navigation iViews, content area).
The Ajax Framework Page provides an enhanced user experience, functionality, and a new Ajax-based development infrastructure. The underlying Ajax technology ensures that most of the page’s functionality is based on the client side, allowing for a significant improvement in usability of the portal. The Ajax interface uses a new look and feel (the “SAP Signature Design”), and provides an improved user interaction model.
The Ajax Framework Page is implemented using Java Scripts, uses asynchronous data transfers between the server and the client, and uses an enhanced client-side caching (in specific, the navigation hierarchy is cached on the client side). Through this usage, server load is reduced and activities are moved to the client side eliminating the need to update the entire page with every server request, thereby achieving a flicker-free experience. The Ajax Framework Page is fully customizable, allowing for simple branding capabilities and advanced personalization options.
Availability
Ajax Framework Page and the new “SAP Signature Design” for SAP NetWeaver Portal is globally available for SAP NetWeaver customers starting with Enhancement Pack 2 for SAP NetWeaver 7.0 and SAP NetWeaver 7.20.
For prior releases, the Ajax Framework Page / “SAP Signature Design” explicitly targets customers who use the portal in combination with SAP Business Suite 7. These customers can optionally activate and run their new SAP Business Suite 7 applications based on the new design (see activation section for details).
Customers who use the portal for releases prior to SAP Business Suite 7 or who use the portal in non-application scenarios (e.g. Intranet/Extranet) may not use the “SAP Signature Design” at the moment since these scenarios typically require a highly customized Look&Feel that is not yet provided by the current Ajax framework page. For those scenarios, SAP plans to introduce an Ajax-based framework page (incl. customization options) with a later enhancement package of SAP NetWeaver.
Releases
The Ajax Framework Page is supported within the following releases:
SAP NetWeaver 7.0 enhancement package 1 and onwards – For SAP Business Suite 7 customersSAP NetWeaver 7.11 and onwards – For SAP Business By Design customersSAP NetWeaver 7.2 and onwards – Global Availability
Terminology Changes
The following changes in terminology have taken place:
Old: “Standard Framework Page”
New: “Classic Framework Page”
Old: “Default Framework Page”
New: The default framework page term refers to the currently active framework page e.g. for the framework page that loads portal suffix should be stated (as opposed to referring to the Classic Framework page instance itself in the current reference)
Activation
In SAP NetWeaver 7.2 Service Pack 2 and onwards Ajax Framework Page is set as the default framework page for new SAP NetWeaver Portal installations.
When upgrading to SAP Netweaver 7.0 Enhancement Pack 2 or to SAP NetWeaver 7.2, the framework page remains unchanged and a desktop rule should be set manually in order to expose the Ajax framework page to the users (a full description can be found in the SAP Portal documentation).
In other supported releases, the upgraded installation framework page remains unchanged and manual activation steps should be taken (outlined in the following paragraph).
For other Ajax Framework Page supported releases, the standard portal framework for integrating and running Business Suite applications is still regarded as the “classic framework page”. Therefore, to enable the Ajax Framework Page customers of SAP Business Suite 7 have to activate the framework page and add it to the existing set of framework pages. For the activation, these are the needed steps to take:
After logging into the portal, paste the following URL into the address bar and press Enter: http://<host>:<port>/irj/servlet/prt/portal/prtroot/com.sap.portal.navigation.afp.setup.AFPEnabler. This creates a delta link of the Ajax Framework Content folder in pcd:portal_content/com.sap.pct/every_user/general and adds a desktop rule for the alias portal/ajax.To access the portal using the Ajax Framework Page, add the suffix /ajax to the portal URL. For example, http://<host>:<port>/irj/portal/ajaxOptional: To replace the Classic Framework Page with the Ajax Framework Page in the desktop rule, add ?default=true to the URL above. You can also save the Ajax Framework Page as the default page by editing the relevant portal desktop.More information can be found on http://help.sap.com/saphelp_nw70ehp1/helpdata/EN/48/1d5d0a71364269e10000000a421937/frameset.htm
Additional Information & Help
Links to various releases help files:
SAP NetWeaver 7.0 Enhancement Package 1: http://help.sap.com/saphelp_nw70ehp1/helpdata/EN/48/1d5d0a71364269e10000000a421937/frameset.htmSAP NetWeaver 7.0 Enhancement Package 2: TBDSAP NetWeaver 7.2: TBD
Further known issues:
Browser support / deviations
Ajax Framework Page is SAP Product Availability Matrix (PAM) compliant.
Following are known deviations due to browser core differences:
Due to Performance considerations, when a Detailed Navigation string is longer than the Detailed Navigation width it is trimmed without a three points notation (’…’).The entry’s tooltip presents the entire stringThe Detailed Navigation is expandable and can be adjusted to the proper width.
In Microsoft Internet Explorer, the three points notation is enabled as the browser core functionality supports it without impact on the performance.

Functionality and UI behavior deviations / limitations
The Real Time Collaboration (cRooms) feature is supported starting with SAP enhancement package 2 for SAP NetWeaver 7.0 and SAP NetWeaver 7.2 releases.
Prior Ajax Framework Page releases do not support this feature.
The new implementation of the BestFit functionality doesn’t rely on the “Folder as a leaf” functionality and allows easier and simpler ways of configuration. “Folder as a leaf” categorization is deprecated in Ajax Framework Page as it is not longer in use.The presentation of the Traditional Dynamic iView was updated as part of the Signature Design to a pop-up window presentation (as opposed to inline presentation as can be found on the Classic Framework page design)Changes in navigation hierarchy require invalidation of the client cache in order to be reflected in the user’s browser. This is done centrally by using the “Navigation Cache Management” (System Administration -> Navigation -> Navigation Cache), or locally by clearing the browser’s cache.In NetWeaver 7.0 Enhancement Package 1, the preview image of the Ajax Framework Top Level navigation and the Navigation Panel within the Theme editor, is not shown when selected.
This issue is solved in NetWeaver Enhancement Package 2 and on.
Due to the browser’s resource racing in Microsoft’s Internet Explorer, overlapping entries are seldom rendered in the Top Level Navigation bar in SAP NetWeaver 7.0 release. To address the situation, refresh the browser. The permanent fix, , was issued in SAP NetWeaver 7.0 Enhancement Pack 1 Service pack 2 and onwards.In a BestFit role, when clicking a “Related Service” link, the title of the opened window is its opener Work Center’s name (instead of the clicked link’s title). Fix was applied to the following Enhancement package / Service Packs (and onward): NetWeaver 7.0 Enhancement Package 1 Service Pack 3, NetWeaver 7.0 Enhancement Package 2 Service Pack 2, NetWeaver 7.2.Second navigation (POST) within a headerless window to the same application (target URL) with different parameters, will navigate to the previous/original target without considering the new parameters.
Workaround: reopen the headerless window
Fix was applied to the following Enhancement package / Service Packs (and onward): NetWeaver 7.0 Enhancement Package 1 Service Pack 5, NetWeaver 7.0 Enhancement Package 2 Service Pack 2, NetWeaver 7.2.Within a headerless window, the History and Back/Forward buttons are not displayed. Those items were added in the following releases (and onward): NetWeaver 7.0 Enhancement Package 1 Service Pack 5, NetWeaver 7.0 Enhancement Package 2 Service Pack 2.
Deployment & Configuration:
Deployment of a J2EE application(EAR file) with references from a portal application using Software Deployment Manager(SDM) in SAP NetWeaver 7.0, causes broken references from the portal application to the J2EE application, which lead to an Ajax Framework Page (AFP) failure.
Temporary solution: refresh the portal application using the Administration Console (log in with Administrator user, navigate to System Administration->Support->Portal Runtime under Tools choose Administration Console -> Archive Deployment Checker, look for your portal application and click “Show”, then click on refresh) this will automatically update the broken references.
A permanent solution will be provided by Portal Runtime (PRT) in upcoming Service packs.
Standards deviation
Accessibility and Globalization (BiDi) standards are supported starting with SAP NetWeaver 7.0 Enhancement Package 2 and SAP NetWeaver 7.2.
Prior Ajax Framework Page releases do not support these standards.
Tab reordering (Drag & Drop keyboard accessibility) is not available in SAP Enhancement Package 2 for SAP NetWeaver 7.0 and SAP NetWeaver 7.2. This feature will be enabled as part of the Personalization Dialog in coming releases. All navigation capabilities are valid and available.
The Classic Framework Page provides an offering that addresses the standards requirements.