1 2 3 32 Previous Next

SAP Enterprise Portal

468 Posts

Background: From my perspective one of the most commonly encountered Enterprise Portal issues seems to be that which involve session management. Now the term "session management" covers a wide range of different angles across a wide spectrum. Session management issues can involve the retention of Portal sessions, a faulty logoff mechanism or inadequate browser cookie handling.

Overview: From a high level perspective any session management issue that we may encounter, follows the underlying concept depicted in the image below.

BLOG7 session.PNG

Some Common Issues (Across Multiple Scenarios):

  1. Session Retention - User A logs out and User B is presented with User A's session upon logging in.
  2. RFC sessions are not terminated in the back-end even after the logoff is called within the Portal.
  3. The browser session does not get terminated when the user clicks "logoff" in the Portal.
  4. The application does not invalid the existing, authenticated session on the server upon user logout.
  5. Cookies may appear to get "cleaned" but when the user returns to the logon page the previous application session is still active.


Important Point To Remember:

When session expires or logoff is invoked or browser is closed, no matter what, the connection is not terminated but returned to the pool and kept open as defined in the Connection Lifetime property. In short, the connection stays open for the predefined amount of time by design and this is not an unexpected behavior. It remains in the pool, it is no longer used by another service e.g. the UWL and it is available for other clients.

How To Analyze a session issue:

Now taking what I have written above into account we know that the connection itself is not terminated but rather returned to the connection pool (The connection lifetime pool can be reset to a different value). So if you encounter a session issue the first thing to check is SM04 (transaction)

  1. When you use transaction SM04 to check sessions what are you seeing? In many cases when the portal is closed (via logoff) a reference is stored. From using the SM04 transaction it may appear that the sessions remain open but infact they will only be references. But you are seeing the transaction field remain filled?
  2. Are you closing the browser after user logoff? When a user logs off from your company Portal by choosing the Log Off button, a logoff action should be triggered on the SAP Portal Side (Portal & Connected back-end systems). Although the SAP Netweaver Portal comes with an out-of-the-box mechanism that terminates a session when the user closes the browser or navigates out of the SAP iFrame the mechanism itself does not handle logoff. Instead your company Portal must raise the terminating event when logging off from the SAP Portal.


Session Release Agent (SRA) & Distributed Session Manager (DSM) Terminator

When executing the ITS services that access a component system (R/3) in the portal, there is the question how to close the sessions in the component system when the user closes the browser (the HTTP protocol is considered to be stateless). When the user closes the browser window or navigates to another position, the browser sends a mass request to a dedicated portal component to end one or more open sessions (by default DSM.Terminator). This component distributes the corresponding termination commands to the component systems. The Termination command then closes the server session.

To close the sessions, a small additional window is generated in the browser outside the visible screen area. This window is automatically closed after two seconds if the Transmission command has been processed. Since ITS-based services cannot be used directly in session management, the Automatic Server Session Termination works with a wrapper technique. A main page consists of:

  • An iFrame that displays the content coming from the ITS
  • A special script called the Distributed Session Manager (DSM) that is responsible for handling the session management on the page

Each content page (page generated by the ITS) includes JavaScript code that is processed in the browser once the browser has loaded the page. This script creates a new JavaScript object called SessInfo with a unique identification of the ITS session and the callback URL to which the SISP command is returned. Once the content page has been loaded into the iFrame, the SessInfo object is transferred from the content page to the main page and is captured there by the Distributed Session Manager (DSM). The DSM stores the SessInfo object in its own storage. When the user leaves the browser, navigates to another page, or uses the Back button, the DSM is activated (by receiving the browser event onunload). The DSM then sends termination commands to all registered callback URLs, resulting in a termination of the ITS session on the server.

Logging On/Off

As stated above your company Portal must raise the terminating event when logging off from the SAP Portal. To setup such a configuration the following appendix can be followed, referenced or used as guidance.

Appendix: JavaScript Code for Session Termination:


Now the appendix outlined above deals with the actual "Logoff" command button option. Here we can find an overview on logging both on/off into Portal sessions and also some information on factors that prevent session termination via the browsers "X" option.

Logging ON/OFF The Portal



Logging ON/OFF The Portal (ii)


In the logoff section outlined in the first link above we see the following "Do not simply close your browser. Closing the browser leaves your portal session still working, until it times out. When working in a browser that supports multiple tabs, such as Internet Explorer 7 or Mozilla Firefox, if you close a tab in which a portal is running, the portal session is saved. If you then open the portal in a new tab, you are already logged on and need to first log off if you wish to log on with different credentials."



In my next blog posting in this series I will outline the full set of relevant solution documentation for session issues & the Enterprise Portal.


Note: This blog posting is part 2/3 in a series involving Portal sessions, Checkout the first part below:




Part 3 coming soon.....



From Internet Explorer 8 onwards, Microsoft gradually shifted its strategy, moving from the old quirks mode concept towards full standards mode rendering. The limitation of this strategy is that you cannot run quirks mode content on the same page as standards mode content. The only way to do so is to render it in a new window.

This change of approach has caused many issues in SAP Enterprise Portal (and in any other Web applications that were implemented in the quirks mode environment). These issues and the ways to solve them are described in the following SCN blog http://scn.sap.com/community/enterprise-portal/blog/2014/09/03/ie-and-portal-standardsquirks-mode-evolution-or-love-hate-relationships).

Since the strategy of all Web applications is to move towards the standards mode rendering approach, SAP Enterprise Portal implemented new framework pages that fully support standards mode rendering: the Ajax Standard Mode framework page and the Fiori Framework page (FFP). For more information about these framework pages, see SAP Note # 2001910 (Ajax Framework Page standards) and SAP Note #2031108 (FFP). For FFP, you can also refer to the following blog SAP Fiori Launchpad in SAP Enterprise Portal: Overview Information.

The purpose of this document is to provide guidelines for content transitions from a quirks mode environment to a standards mode environment.




Quirks framework page – a framework page that specifies that the browser renders in quirks mode (IE5 quirks in IE10 and higher). For example, Classic Framework Page, Light Framework Page, Ajax Framework Page or any custom framework page based on the afore mentioned framework pages.

Standards framework page - a framework page that specifies that the browser render in standards mode (edge). For example, Ajax Standard Mode Framework Page, Fiori Framework page, or any custom framework page based on the Ajax Standard Mode Framework Page.

How Do I Set Up a Framework Page to Run in Either Quirks or Standards Mode?

To force browsers to render in your chosen mode, insert an out-of-the-box Browser Document Mode iView into the framework page and set the Browser Document Mode property of the iView to be "IE=5, IE=EmulateIE7" for quirks mode or "IE=edge" for standards mode (for more information, see SAP Note #1458799).



Standards mode support


UI Technology

Portal Versions

SAP Note


7.02 SP15, 7.30 SP11, 7.31 SP5, 7.40


WD Java

7.30 SP 9, 7.31 SP1, 7.40



7.00, 7.01, 7.30, 7.31, 7.40



Not supported

In process


Not supported

In process

Content migration steps

A quirks framework page can contain three types of content:

  • Quirks mode rendering applications
  • Standards mode rendering applications ("Launch in New Window" property of the iView is set to "Display in separate headerless portal window (standards mode)").
  • Standalone running applications.

Steps needed for Quirks mode rendering applications

If the application has been implemented in an SAP UI technology which supports dual rendering and your portal version is one of the versions mentioned in SAP Note #1814711 then you don’t have to do anything! (Dual rendering means that the application supports both quirks and standards mode rendering. In the "Standards mode support" table above, you can see which technology supports standards mode, and in which versions.)

The portal notifies the backend of the standards mode environment and the application renders in the correct mode.

If the application is based on an SAP UI technology, which does not yet support standards mode, or if you cannot upgrade your backend, then you must set the iView\Page property "Launch in New Window" to "Display in separate headerless portal window". This mode will force the browser to open a new window rendered in quirks mode.




Steps needed for standards mode rendering applications

If the application is rendered in a quirks mode rendering framework page, you have to set the property "Launch in New Window" of these iViews to "Display in separate headerless portal window (standards mode)" than no further action is necessary. The application will continue to function as before.

If you want the application to render in-place, then you can change the property "Launch in New Window" of the iView to "Display in Portal Content Area".


Steps needed for Standalone rendering applications

When we talk about standalone rendering applications, we mean that the iViews are launched directly in a separate browser window.

By directly, we mean that it is done without using the portal navigation API.

One example of direct launch is the following URL:


Another example is when executing the iView in "preview" mode (through iView\Page editor).

In SAP Notes 2098706, 2097861, and 2012705, we explained a new iView/page property, "Default Document Rendering Mode". You can set the value to either "Quirks" or "Standards" to force the required rendering mode in standalone scenarios.



We all know that there is no standard solution provided by SAP to log out an idle user.After a number of futile search attempts in google/SDN for a solution, I set about to find a solution on my own. Find below the steps to create the simple portal component which tracks the user inactivity.

I have already  seen couple of solutions for this but they have minor issues and did not suit my requirements.

1. Portal user idle timeout using dialog windows - Client side solution => this solution does not seem to work for AJAX Framework in recent releases and did not track the user clicks, mouse movement etc. It worked only for Navigation event in portal. Basically, it will consider the user idle if he does not navigate. The user will be timed out

2. http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/309379b6-bb9b-2d10-feb1-91f2a7078574?overridelayout=true => Though this one says that it can track the user clicks, mouse movements etc, the logoff functionality did not work in NW portal 7.4.

My requirement is to track the user events in the content area as well before deciding if the user is idle or not.

The portal component which I have developed is very basic and uses Jquery. It tracks Key press, mouse movements in content area of the portal framework.

1. Go to Development Infrastructure perspective and create a EP DC

Screen Shot 2015-07-27 at 15.48.20.png

Screen Shot 2015-07-27 at 15.50.40.png


Click finish.


2. Create a 'Portal Application Object' in this EP DC.

Screen Shot 2015-07-27 at 15.52.33.png


Click Next. Select the DC created in step 1

Screen Shot 2015-07-27 at 15.52.41.png


Click Next. Choose Portal Component -> JSPDynPage

Screen Shot 2015-07-27 at 15.52.58.png


Click Next.  Enter the JSP class, package and file name.

Screen Shot 2015-07-27 at 15.53.19.png


Click Finish.


3. Open the TimeOut.jsp file under dist/PORTAL-INF/pagelet folder and copy the code below. Make sure that you place the relevant Jquery file under /scripts folder.




<% String mimeUrl = componentRequest.getWebResourcePath(); %>

  <script type="text/javascript" src="<%=mimeUrl%>/scripts/jquery-1.11.2.min.js"></script>

<script type="text/javascript">

var idleTime = 0;

$(document).ready(function () {

    //Increment the idle time counter every minute.

    idleInterval = setInterval(timerIncrement, 120000); // 2 minute


    //Zero the idle timer on mouse movement.

    $('body').mousemove(function (e) {

     idleTime = 0;

     document.querySelector('.content .value').innerHTML = idleTime + "mouse moved";



    $('body').keypress(function (e) {

        idleTime = 0;

        document.querySelector('.content .value').innerHTML =idleTime +  "key press";





    $('body').click(function() {

       idleTime = 0;

       document.querySelector('.content .value').innerHTML = idleTime + "mouse moved";






function timerIncrement() {

    idleTime = idleTime + 1;

    document.querySelector('.content .value').innerHTML = idleTime;

    if (idleTime > 0) {

        if (confirm('Your session is inactive for the last 2 minutes. Press OK to log off. Press cancel to extend the session.') == true) {



        } else {

        idleTime = 0;

        document.querySelector('.content .value').innerHTML = idleTime









<div class="content">Status:  <span class='value'></span></div>





4. Build and Deploy the DC to the server.


5. Create an iview for the deployed application. You can preview and test before embedding it in the portal framework.

  Preview the iview and do not do any action on it. You can see the pop up below after 2 minutes.



Screen Shot 2015-07-27 at 16.04.47.png


6. Now you can place this iview in the framework page under 'Technical Hidden iviews Container'.


Screen Shot 2015-07-27 at 16.04.27.png


7. Save the Framework page. Log off and login to the portal.


As you can see, code is simple and timings and messages can be customised as per your requirements.

I have placed the following HTML element in the code so as to check if the mouse movements and user clicks are tracked or not.


<div class="content">Status:  <span class='value'></span></div>


Since you have placed the iview under hidden iviews, you will not be able to see this HTML element. If you want to debug , please move the iview to one of the other containers and make the component visible on the screen.


Feel free to comment any improvisations on this approach.

Background: As we know when we are using the Enterprise Portal we often encounter issues related to session management and these can occur for a wide range of different reasons. The purpose of this blog is to provide a short and simplistic overview on what type of sessions are involved in terms of association with the Enterprise Portal. In my next blog I will provide an overview on some of the most commonly encountered session issues.


Overview: From an end users perspective utilizing the enterprise Portal is a straightforward process. We simply logon, fulfill our work obligations and logoff. As an end user we are only concerned with the graphical representation of the Portal that we are delivered with through our monitors representation and we are not truly troubled by what underlying functionality is taking place.


What & Why: If you have ever encountered a "User Session" or "Cookie Rentention" issue with the Portal then you are most likely familiar with the transaction of SM04.


SM04:  Essentially SM04 as a transaction provides us with a view on the different connection types. With reference to SM04 the connection type means what kind of user (and their connection) is connecting to the SAP System e.g. the Portal.


Connection Types: Connection types include that of RFC, GUI, Plugin (HTTP/SMTP).


RFC Connections: This particular connection type references users which are connected up to the system (Portal) via an RFC Connection. (See RFC's using the SM04 transaction), a simplistic view on a RFC connection type user is someone who is utilizing the connection using external based RFC clients.


GUI Connections: As the title implies this particular connection types makes referneces to users who utilize access to the Portal via a GUI based connection platform.


Part 2: Common Issues coming soon







This blog post is to suggest one of the solutions to disable the  "Confirm Certificate" pop-up window which arises when the administrator tries to access the roles assigned in portal.


Consider the scenario where in the end-user(/administrator) is accessing roles assigned to their user id and a confirm certificate pop up window arises as shown below:

     Confirm Certificate.jpg         

                                                                            Fig.1.1:Confirm Certificate Pop Up Window


To avoid this pop up,we should set the profile parameter to the correct value in the backend systems.

For example:In case of displaying Universal Worklist in the portal,we create a role named Home.So while accessing the role "Home" ,the end user encounters the above mentioned pop up.On further probing into the issue,a profile parameter(set in the backend) based on which the pop up is shown came into picture .

Profile Parameter.jpg

                                                                                               Fig .1.2:Profile Parameter


In this case ,to disable the confirm certificate popup ,we have set the above mentioned profile parameter to the value , 0 ;i.e





in the backend ECC system ,so that the next time when the user accesses the portal role Home, the Confirm Certificate window does not pop up.

The parameter set would look as follows:


In a similar way , we need to set the above profile parameter for all the backend systems so that the Confirm Certificate window does not pop up.


Hope this helps .:)



This blog post is to suggest one of the solutions to enable theme editor in SAP Enterprise Portal in case the administrators are not able to view the same by default and are able to see a blank page instead.


Consider the scenario where in the administrator needs to view in the theme editor to form a customized theme for the portal but is not able to view the same.In such cases ,the following steps needs to pursued:




  1. Log on to SAP Netweaver Administrator, navigate to: Configuration->Infrastructure->Application Modules.
  2. In the Overview tab, filter the Application List. In the name field, type laf and then press Enter.
  3. Select the laf service from the application list->Click on More Actions->Select View Corresponding to Application
  4. Once redirected to Start and Stop Applications page, click on the Restart button to restart the com.sap.portal.themes.lafservice and refresh to check the status of the service by clicking on Refresh.
  5. Once the service is restarted successfully, logon to SAP Portal->Content Administration->Portal Display->Portal Themes->Theme Editor->Click on Options->Refresh



The theme editor would be visible now.

Hope this solution helps out!

Background:  You would like to disable the UWL cache to support a preferential setup in  your system.


Is it possible: In short the answer is yes. However only to a certain extent.


How to we disable it?


  1. Log into Enterprise Portal.
  2. In the portal, navigate to System Administration -> System Configuration  -> Universal Worklist & Workflow -> Universal Worklist -> Administration.
  3. In the list of systems,  select the connector for which you do not want to use the UWL cache and choose  Edit.
  4. In the list of properties displayed below, you do not see the Use Cache so that to  disable it, as shown below:


Limitation of cache disablement: You can switch off the UWL cache for BPEMUWLConnector and custom UWL connectors in the UWL configuration. This may be used, for example, if the application runs on the same application server as the UWL. In this case the access to the back end can be faster without using the cache database even if all iView related actions require direct back-end calls.


Reported Issue: When you try follow the steps to disable to disable the cache you are essentially unable to "uncheck" the checkbox


Important: In cases where cache disablement is not possible, in the properties to be edited there is no Use  Cache for the selected connector. Switching the cache off is supported for BPEMUWLConnectors and custom connectors only.





Key Points


  1. You can switch off the UWL cache for BPEMUWLConnector and custom  UWL connectors in the UWL configuration.
  2. This is feasible if the application runs on the same application server as the UWL. In this case the access to the back end can be faster without  using the cache database even if all iView related actions require direct back-end calls.

Background: You have upgraded to a newer Enterprise Portal version and the roles and permissions previously maintained are now lost in KM documents folders and rooms however the groups and users which were previously assigned still remain.



Overview: When you assign role permissions to the folder after the upgrades completion all functionality operates accordingly however the older previously assigned roles and permissions are now lost.



Issues & Why: Inside the /root/UME/roles involve custom roles. Such behavior may be caused due to permissions on your resources not being inherited from the collection <i>/documents/documents</i> due to a configuration discrepancy.




blog5 kmpermissions.PNG







Evironment: EP Release Independent SAP NetWeaver



Solution: The permissions should not be effected by an upgrade procedure. Please check if all the permissions on your resources are in fact inherited from the collection <i>/documents/documents </i>. If configurations are maintained correctly the means of the resolution is to correct the role permissions is to reset them once more manually.


Welcome to the Q2 edition the SAP Portal news blog. We have many news for you in the following topic areas:

  • SAP Fiori / SAP Fiori Launchpad on HANA Cloud Platform
  • HANA Cloud Portal News
  • More Cloud Solutions on HANA Cloud Platform and Cloud Portal: Partner Portal
  • Enterprise Portal
  • Developer Challenge 2015
  • Blogs from the Community


SAP Fiori / SAP Fiori Launchpad on HANA Cloud Platform


Experience, Customize and Run SAP Fiori on the Cloud with SAP Fiori, Demo Cloud Edition

SAP Fiori, demo cloud edition provides a new cloud based, simple deployment option for SAP Fiori on the cloud. It runs on SAP HANA Cloud Platform, while consuming the business data from the customers’ on-premise system. The extended SAP Fiori, demo cloud edition offering, which is free of charge for 30 days, provides customers additional capabilities of extending  and branding SAP Fiori apps, and a full role-based, personalized SAP Fiori launchpad experience. Watch this movie:

Watch this demo showing how to get started with SAP Fiori, demo cloud edition:

There are 4 additional demos in which you learn:


SAP Fiori Launchpad Available in SAP HANA Cloud Platform

SAP Fiori launchpad is now available for all SAP HANA Cloud Platform trial users and productive users. The launchpad is available as a site in HANA Cloud Portal, and provides a range of services, including navigation, application configuration, and embedded support.

In order to create and configure content for a launchpad site, you can read this blog and the SAP Fiori launchpad on Cloud documentation.


Blogs from our experts

I recommend to read also these blogs written by our Cloud experience experts:


SAP HANA Cloud Portal


Cloud Portal on SAP Store

HANA Cloud Portal has a page on the new SAP Store.


How to Mark your Cloud Portal Site ready for Smartphone

This blog offers some best practices - based on the ongoing customer implementation projects - and will give you an instruction on how to create a Cloud Portal based site which looks good on smartphones.


More Cloud Solutions on HANA Cloud Platform and Cloud Portal


Improve Partner Engagement with new Partner Portal for SAP Cloud for Customer

The new partner portal for SAP Cloud for Customer supports channel managers to create a web-based site for partners to easily access intuitive self-services. The solution offers out of the box content and services from self-registration as a new partner to managing marketing leads, sales opportunities or customer appointments. Check out the solution details on SCN and in SAP Cloud for Customer documentation.


SAP Enterprise Portal News


SAP Portal features on SAP NetWeaver 7.4 SPS11 and 7.31 SPS16

Learn about the new end user and administration features developed in the latest Enterprise Portal support package for SAP NetWeaver 7.4 SPS11 and 7.31 SPS16. The features support mainly the integration of SAP Fiori launchpad into Enterprise Portal. Read also this blog focusing on the administration features for SAP Fiori launchpad on Enterprise Portal.


Watch this product demo on SAP Fiori launchpad on SAP EP:


And a movie on the administration experience:


There are three additional blogs describing some of the new features:

More Enterprise Portal blogs from our experts

I also recommend the following blogs



HANA Cloud Portal Developer Challenge


We would like to invite you to participate in the Cloud Portal developer challenge 2015 and demonstrate your developer excellence and leverage the capabilities of the trial developer environment of HANA Cloud Platform and Cloud Portal. We ask you to develop SAPUI5 business applications simply and intuitively with HANA Cloud Platform and Cloud Portal and:
• publish them to a Cloud Portal site or
• create a SAP Fiori launchpad site and publish your business applications to the Fiori launchpad

What is in for you? All participants of the challenge will receive a SAP HANA Cloud Portal Developer Award of Excellence. Get familiar with this new challenge and participate, we are looking forward to your contributions!


Blogs from the Community


In the first part of the „Portal on smartwatch“ blog series our partner company BTEXX demonstrated the BTEXX mobilePortal prototype for the Pebble smartwatch. Now as the Apple Watch is released in many countries BTEXX wants to share some information on their Apple Watch prototype.


Check out the first great contribution to the HANA Cloud Portal developer challenge 2015: Tailored Apps for HCM by Marcos Andrade.

The new SAP Fiori launchpad design for SAP Enterprise Portal offers an intuitive modern Fiori UI to portal users. Though it can be used to launch all types of iViews, it still seems especially suited for application portals providing a centralized access to applications from various backend systems. So, how can you best share unstructured corporate content like guidelines, process documents, product information, and others?


I think that the way that best fits the SAP Fiori launchpad look and feel is using SAP Mobile Documents.


I just published a detailed blog on how to setup and configure SAP Mobile Documents for usage with SAP Fiori launchpad running on SAP Enterprise Portal. There is just one step that is somehow missing in this blog: How to connect to KM repositories with Corporate content. So, let's just assume that Mobile Documents and Fiori launchpad (FLP) on EP have been set up, but you now would like to give all users (read) access to some unstructured content, e.g. corporate policies.


In this example, let's assume you would like to store those documents in the Portal Knowledge Management. Of course, you could also use other CMIS-compatible document repositories like a file share or a Microsoft SharePoint server, but since you are running SAP Enterprise Portal, KM might be a natural choice. Now, the first decision is whether you want to create a completely new repository in SAP KM Administration or just store your content in one subfolder of an existing repository.


To create a new repository:

In your portal, go to System Administration > System Configuration > Knowledge Management > Content Management > Repository Managers > CM Repository. Click Create to create a new CM repository. Here is an example how to fill in the form:




Click OK to save and activate the repository. Make sure that the file system folder that you entered for storing already exists on your server, otherwise the repository won't show up in your Knowledge Management area.




To assign the new repository as a Corporate Repository in SAP Mobile Documents, open the admin interface of Mobile Documents.

  • Enter https://<your server>:<your port>/mcm/admin into your browser, preferably Chrome.
  • Navigate to Repositories > Corporate Content.
  • Click Create.
  • In the pop-up window, make the relevant settings for your new repository, e.g.
    •   Connection: Local_KM
    •   Repository: Select a KM repository from the list, e.g the one that you created before or re-use an existing one.
    •   Display Name: Enter the name that should show up in SAP Mobile Documents
    •   Description: If you want, enter a description
    •   Pushed Content: Check if the repository contains pushed content that is automatically downloaded to the users' devices.
    •   Restricted To: Enter a role or semicolon-separated list of roles from SAP HANA Cloud Platform. Only users with one of those roles can see the content of the Corporate Repository.
    •   Root URI: Start folder in the repository (after the repository name), e.g. use /Guidelines for KM folder /documents/Guidelines.
    •   Document Classification: Select a predefined classification for all documents in the repository.
  • Click Save.




Now you can see the new repository in your SAP Mobile Documents tile in SAP Fiori launchpad.

This blog is designed for application developers/administrators who want to run their SAP Cloud applications in the SAP Fiori Launchpad on Portal (FLP on EP), thereby taking advantage of the portal’s role-based content management with the latest SAP cloud technology.

If you’re new to FLP, you can start off by reading this blog which explains what it is and how to run it on Portal.

We’ll start with some prerequisites, then we’ll create a simple application, and lastly, we’ll consume it in Portal using our ABAP back-end server and running it on FLP.


  • You are using Portal version 7.31 SP16 and higher
  • You set the Fiori Framework Page SAPUI5 library to “ABAP”:


  • You have access to SAP HANA Cloud Platform cockpit.
  • You are familiar with developing Fiori applications and/or SAPUI5 applications.
  • In the event that your back-end system is not connected to the internet, you need to install the SAP HANA Cloud connector. This enables your Web IDE to communicate with your back-end system to deploy or import applications you are developing.

For more information, see this short video of a step-by-step process on installing and defining the cloud connector:


Now, let’s begin…

  1. Go to your Web IDE.
  2. Create a Fiori application:
  • Create a new project.



  • Select a Fiori template


  1. Select an ODATA service to be used by the application, for example, the ODATA service below shows catalogs in the GM6 ABAP:


    • Fill in the template customization in the Master section and Detail section


    • Now the application is built, and you can run it from Web IDE.

3.   Deploy application to the back-end system as shown below:


  • Choose Deploy to SAPUI5 ABAP Repository and complete the steps in the wizard.


4.  Open FLP Designer.

5.  Create a catalog and a tile:

    • Choose the “+” icon.


  • Enter a title and an ID.


  • Add a target mapping (this points to the actual application to be launched from the tile):
    • Choose “Target Mapping”.


  • Choose “Create Target Mapping”.     


  • Fill in the following entries:


  • Add the a tile:


  • This is an example of a simple application, so we’ll select a static application launcher


  • Add a title, information, icon, and so on.


  • Fill in the following details; select an icon for the tile, semantic object for navigation (note: this is a target mapping that is mapped to the application we have created) and confirm.


6.  Go to your Portal and log on as an Administrator.

7.  Consume the application in the portal:

  • Under “Content Administration”, locate the Fiori Role and open it for editing.


  • Choose “Add Remote Content”.


  • Select the destination GM6 and the catalog name where the application was deployed in the previous step, select it, and choose “Add”:



  • Choose Finish (or choose “Next” if you want to preview the whole procedure).

8.    Log on to FLP on Portal (as explained in the blog linked in the introduction) to run the application:

  • Choose “Tile Catalog”:


The application you developed should appear under the “EP_DEMO_CATALOG” catalog.

  • Add the application you developed to the user by clicking the “+” icon.



  • Now you see the application in FLP.

Click the tile to run it.



Now you can use the portal even more as a one stop shop for your end users and enrich their user experience while keeping your content management as is, create state-of-the-art applications with a great UI and powerful and familiar back-end systems.

This blog is for portal content administrators who would like to learn about the new features developed in the latest Enterprise Portal support package for Fiori launchpad (FLP) on EP, their added value, and the configuration required.





The following minimum required SP for EP: NW 7.31 SP16, NW 7.40 SP11.


For Remote ABAP content consumption scenario, the pre-requisites are:

  1. SAP Web Dispatcher or any other reverse proxy, which is responsible to dispatch the requests between the ABAP FES and Java server (EP)
  2. Minimum required SP for your ABAP GW server is:
    • for ABAP GW server NW731 you need UI Add On 1.0 for NW 7.03 SP12
    • for ABAP GW server NW7.4 SP11 you need SAP_UI 740 SP12 component
  3. Administrators need to activate the following OData services in the Customizing activity to enable the Remote Content editor:
    • /UI2/INTEROP


For additional information please refer to SAP note 2031108.

1 Remote ABAP Content Consumption

Administrators can consume catalogs and groups from an ABAP Frontend Server (FES), so that end-users can see them in the tile catalog and the home page. Tiles are rendered in a similar manner, regardless of whether they are based on portal content or remote ABAP content.
For this, administrators can use the new remote content editor to add catalogs and groups from ABAP FES to portal roles.
Using the editor, administrators can assign ABAP catalogs to portal categories. This allows tiles from both existing portal categories and ABAP catalogs to appear together under the assigned category in the tile catalog.
The ABAP groups can be consumed together with the corresponding catalogs. These groups can be assigned to portal categories. If a category contains a tile configured to appear in the Home page (so called pre-defined group), the ABAP group will be merged with the pre-defined group and thus appear in the home page.
End users can personalize remote ABAP content in the same way as portal content: they can add tiles, remove tiles, reorder tiles, create groups, delete groups, etc.
To enable Remote ABAP content consumption, follow the steps below:
1. In Framework Page Configuration select Fiori Framework Page in dropdown list and set the property SAPUI5 Library Source to ABAP (please click on the picture for better reading):

     2. Define a destination corresponding to an ABAP FES and establish the connection:
a) Use the link https://<server>:<port>/nwa and search destination in search window
b) Define a new destination for the ABAP FES. In the Destinations window, enter a new URL in the syntax:
          <protocol>://<front-end server host>:<front-end server port>/sap/opu/odata/UI2/FIORI_CATALOGS/

      • FIORI_CATALOGS  service should be activated on FES
      • ABAP FES authorization should be granted for the EP administrative scenario (details) .
         c) Choose Ping Destination button to check the connection.

     3. Go to portal content:
      1. Open a role for edit
      2. Verify that an Entry Point property is set in the role structure
      3. Click on Add Remote Content button
      4. Add remote catalog(s)/group(s)
      5. Save:
4. Launch the Fiori framework page URL alias not with the EPserver URL, but with SAP Web Dispatcher URL (with an end-user who is assigned to the relevant portal role). Go to the Tile Catalog to see new category with the name exactly as maintained in the Fiori Launchpad Designer (FLPD):
5. Optional: Assign an ABAP catalog to an existing EP category using the Assign Categories button. The ABAP catalogs will be merged with existing tiles assigned to the categories or assigned to an “empty” category:
     6. Add an ABAP group and assign it to a locked group on the home page using the Assign Categories button:

2 Locked Group
Administrators can configure a locked group of tiles which cannot be personalized by end-users.
Only one locked group can be configured for a home page. A locked group always appears at the top of the home page.
Any administrator’s changes to a locked group are automatically reflected on the home page, in contrast to predefined groups, which users need to reset to see updates.
In the example above, an ABAP group is added to the locked group called Company Locked Area and the result looks like this:
To support this capability, the following configuration is required:

1. In Framework Page Configuration select Fiori Framework Page in drop down list and select the Enable Locked Group checkbox:
2. Open Portal Content->Portal Users->Standards Portal Users->iViews->Fiori Launchpad->Fiori Launchpad Categories. Search for Locked Group ID and Locked Group Title properties; enter a title and an ID for the locked group:
3. Choose a role/role folder/workset which content is to be displayed in a locked group, and mark it as an Entry Point. Open the role/role folder/workset properties editor and select Lock Group checkbox under Personalized Launcher category. Only iViews or pages which are one level below the relevant container are added to the locked group.


3 Dynamic Tiles

Administrators can configure properties to enable iViews or pages to be rendered as dynamic tiles in FLP on EP. The information displayed on dynamic tiles could be pulled from back-end systems using OData services or component.
To support this capability, the following properties have been added to the Properties editor:
  ● Service URL: specifies a URL configured to a relative path of the service or component (not necessarily portal) that      returns    an OData structure

  ● Interval after the display is refreshed (in seconds)

  ● Unit label to be displayed (optional).


The dynamic tile will send a request to the server for update data according the refresh time interval.  In order to receive valid response from the server the browser should allow server cache. For most browsers this option is
set by default, but for some browsers configuration is needed. For example, for IE 10 the following should be done:
  •   Switch to F12 mode.
  • Open Cache menu and check Always refresh from server
For IE9 and IE11 this property is checked by default.

4 NetWeaver Business Client for Desktop and FLP on EP integration

The SAP Fiori launchpad on Portal is available in SAP NetWeaver Business Client for Desktop (NWBC).
This provides an enhanced user experience to users who work with SAP GUI transactions. Tiles provide access to SAP GUI transactions with a native application look-and-feel. The Quick Launch in the home page can be used to search for and launch the applications. More about NWBC with FLP on EP can be found here.

5 SAP Fiori Client

SAP Fiori Client is a mobile application that can be installed on Android and iOS devices.
This application  acts as an enterprise enhancement to the mobile browser when SAP Fiori applications are running. It provides more reliable asset caching (HTML, CSS, JavaScript files, and more) as well as, on iOS, an enhanced attachment viewing process. Therefore, the application is not affected by browser cache issues.

6 Enhanced Tile Configuration

The following properties have been added to the Properties editor to support the configuration by administrators of both static and dynamic tiles:
● Information
● Subtitle
● Keywords
These properties can be used in tile display as shown below:
Keywords can be used in the search field of the Tile Catalog (filter by a category). You can also search by keyword using the Quick Launch; once you press Enter, the results appear.

7 Enhanced Object ID of Device Group Administration

Administrators can now set the device type at the container level, such as role/role folder/workset. Previously, it was only possible to set the device type at the level of the specific iView or page.

8 Enhanced Action Mode

Action Mode allows end-users to personalize the home page. It can be activated as following:
1.  By clicking an icon in right bottom corner on the home page 
2.   With an action Personalize Home Page from User Action Menu.
Action mode provides the following functions:
  • Remove a tile from a group
  • Move a tile from one group to another
  • Delete a group
  • Reset group content.
After activating Action mode, the following appears:

Now a user can move the tiles from group to group (excluding the locked group) or remove the tile from the home page:
Pre-defined group can be reset to see the changes done by the administrator. A group, which is not a pre-defined group, can be deleted.
9              System Updates
Cached resources are automatically invalidated during system updates, so that users do not need to manually clear the browser cache to see the changes. Please refer to note in Dynamic Tiles for the specific IE10 behavior.

To learn more:


This blog post describes the integration of two working environments, Fiori Launchpad on Enterprise Portal (FLP on EP) and NetWeaver Business Client (NWBC) for desktop, and how to enable it. This feature is available for NW7.31 SP16, NW 7.40 SP11.

The integration objective is to optimize the experience of a heavy GUI user who works in a federated system environment, while minimizing the overhead on the content administrator. This is achieved by a good synergy with Enterprise Portal as a federated content management system and the NWBC as a desktop client optimized for GUI centric work environment.   


Enabling Integration

What do you need to do to make this integration happen?

On the NWBC side, when configuring the portal connection, you need to select the Use Display Rules checkbox in the System Selection screen:




In Portal Display Rule Editor in Master Rule Collection for the URL alias portal/flp there is a rule corresponding to FLP on EP launching (please click on the picture for better reading):


When launching NWBC with the integrated FLP on EP the following shows:NWBCwithFLP.PNG

The SAP GUI transaction opens in a new tab:



Hiding UI Elements


A NWBC administrator can hide UI elements, such as the Quick Launcher and Favorites by configuring properties in a so-called admin configuration file. This file contains NWBC properties which hide particular NWBC UI elements. The file can be found under %programdata%/sap/nwbc/NwbcOptions.xml.template.



    1. Save NwbcOptions.xml.template as NwbcOptions.xml in the NWBC directory on the desktop.
    2. Find the corresponding property and set it to false:



           3. Start NWBC. Quick Launch and Favorites are disabled:



Working with FLP on EP through NWBC

The Quick Launch in the home page can be used to search for and launch the applications.


For customers who are used to working with transaction codes, the codes can be added to the tile titles. You can search for and launch tiles by entering the transaction code in Quick Launch:


A user can search in the tile catalog by entering either the title or the subtitle, and launch selected tiles by clicking them.


A user can access the tile catalog and personalize content in the same way as FLP on EP, that is, add tiles, remove tiles, reorder tiles, create groups, delete groups, etc.


For more information, see NWBC for desktop.

In Enterprise Portal 7.31 SP14 / 7.4 SP9 a new feature was introduced Ajax Framework Page in IE standards mode


This feature allows you to run standards based content e.g HTML5 / UI5 / Fiori applications inside the AFP Shell.


This is the reason why in 7.31 SP16 / 7.4 SP11  we introduce AFP Standards with SAP Blue Crystal theme and Fiori User Experience.


The Blue Crystal theme will only be supported while using AFP in standards mode because it was designed for UI5 and Fiori applications.



29-03-2015 14-56-13.png



New visual design for the pop-up



25-03-2015 11-00-13.png



New visual design for the role entries in the TLN and overflow buttons.


25-03-2015 10-59-22.png



Notice that the Detailed Navigation (DTN) is now without the curves you used to see in bottom and top right side.


25-03-2015 11-01-55.png



New parameters for the background colors of those elements were exposed for the UI Theme Designer allowing you to easily customize the theme.


In the following screenshot you can see a very small example of theming possibilities (as you imagine no designer will pick these colors )





We tried to keep this theme as lean as possible and to adhere to the simple clean look of Fiori User Experience.




Hope you like it.

Overview:  The language that the portal is displayed in depends on the following hierarchy, with the languages at the top of the list taking precedence over those at the bottom:


  1. Component (iview) language (defined in the portalapp.xml)
  2. Portal Mandatory language (defined in the prtDefault.properties)
  3. User language (defined in the user’s profile).
  4. Request language (defined by the browser).
  5. Portal Default language (defined in the prtDefault.properties)
  6. System Default language (default locale defined by the OS).


Example:  for example, if you have your portal user language (as in point 3) set to Czech, but the language of the iView that is the logon page (as in point 1) set to English, that logon page will be displayed in English.



blog4 language.PNG



Property Location:  Regarding the navigation path for the prtDefault.properties kindly refer to the SAP Documentation outlined below which provides a detailed summary and walkthrough regarding the language settings.





Useful Reference Documentation:


  • SAP Note: 1013521 - Configuration of supported languages within the portal
  • SAP Note: 1661391 - Portal 7.3 is not displayed in the configured language
  • SAP Note: 1696439 - Changing the Default or Mandatory Locale for a 730 EP
  • NW Portal 7.3: SAP Documentation and Guides: http://scn.sap.com/docs/DOC-23349


Filter Blog

By author:
By date:
By tag: