This Blog is the 3rd case I publish in the context of my support blog – a continuance blog in which I publish Portal support
cases which customer may encounter.


This interesting case demonstrates the importance of navigating in the Portal by using the navigation APIs and not the direct URL to the Portal content.


The customer in this story had an issue with a page that was being triggered from an application (UWL application) and was expected to open in a new headerless page. Instead, it opened in a full L-Shape Portal framework page.

In mobile, on the other hand, when running the same application, it’s working as expected – the new page opened in headerless window when opening a new task. Bear in mind that the mobile application uses a different framework page (mobile framework page).


Why does this happen?

Here are a few more details:

The customer has a custom launcher page with a button that launches the mobile UWL application using a URL such as this*:


(*I anonymized the URL. But you get the idea.)

Can you see what is wrong with this URL?


As I cannot use screen shots from the customer’s system – I simulated this type of scenario on a local computer.

Let’s assume that the page shown below is the launcher.

Both the links are targeting the same iView. The first (“Good Navigation”) does it correctly, and the second (“Bad Navigation”) does it incorrectly.



     Figure 1: The simulated launchpad


In the customer’s system it would open the UWL navigation. In my simulation it opens a very basic iView which contains a link to another iView in a new window (as if the UWL is opening a task in a new window).

Look at the result from the “Bad Navigation” below.


Do you see what’s wrong here?

Hint 1: Look at the screen shot below which shows the navigation result.

Hint 2: It is running on a desktop framework page.



     Figure 2: "Bad Navigation"


So the problem here is that the portal framework has disappeared – note that there is no TLN or DTN – only the application has been triggered.


The link on this page that opened is navigating to another iView in new headerless window.

But surprise! The new iView has opened in a full Portal framework page as shown below:


     Figure 3: "Bad Navigation" result - the content is presented in Portal default framework

Now wait! It gets even more complicated: when running that same URL from the mobile framework page – the page opens correctly in a headerless framework page.


So what is going on here?


As I already mentioned above – the problem is related to the navigation URL. The customer has customized his or her launchpad to navigate directly to the content, instead of navigating to it via the navigation APIs.

So the correct way to navigate to the UWL application in that case would be:

http://myportal:50000/irj/portal?NavigationTarget=ROLES:// aportal_content/Folder1/Folder2/MyWorksets/MyRole/UWL_MOBILE& username_field=auser&password_field=apasswork&login_submit=on&login_do_redirect=1&ganame=MY_TASKS


You can see that the navigation is done by using the NavigationTarget parameter followed by the target content.

So when clicking the “Good Navigation” and navigating correctly by navigating in the Portal – the iView (simulation of the UWL application) opens inside the Portal frame – with the TLN and DTN (and all the other iViews of the frame of course):



     Figure 4: "Good Navigation"


And then opening a new headerless window (in the UWL it is New Task) the Portal understands “headerless window” and opens the new page as expected in a new headerless window.



     Figure 5: "Good Navigation" result - the content is displayed in headerless window as expected

When you navigate directly to the content, not all the JavaScript framework pages  are loaded and subscribed.  So when a new navigation from that content is performed – there is no JavaScript to process it and understand “open me in a headerless page”. The Portal performs this navigation in the default framework page of the Portal – which for desktop is the framework with the L-Shape (TLN and DTN).

Now why does this work correctly in mobile?

In mobile, the default framework is headerless – so the fallback of the Portal when it doesn’t have the JavaScript to “translate” the opening mode – is to open the page in the headerless window. Luckily, in the mobile case it seems to operate correctly, but it is based on an incorrect navigation just like in the desktop framework case.



So to summarize the conclusions from this case:  when you want to navigate in the Portal DON’T navigate to the content directly and DO use the NavigationTarget parameter.


In this blog, I would like to share the new Portal features of SPS 9 of NetWeaver 7.4 (or SPS 14 of 7.31).

There are just two new features in this Support Packages Stack, but nevertheless, they represent important improvements.



1. The most important one in my eyes, is the availability of the Ajax Standards Mode Framework Page.



This new feature solves an old problem with Internet Explorer. So far, the Ajax Framework page did not render properly in standards mode, but only in quirks mode. To get a better understanding of the problem, I highly recommend Maya Amit's blog on IE and Portal - Standards/Quirks Mode Evolution. It explains in a very detailed way what problems exist, when the portal runs in quirks mode, but web dynpro applications start in standards mode or SAP UI5 is written in standards and how you could work around those problems so far.



Now you can just use the new Ajax Standards Mode Framework Page and run SAP UI5 applications in the Portal window. The new Ajax Standards Mode Framework page and the Ajax Standards Mode Portal Desktop can be found at Portal Content > Portal Users > Standards Portal Users > Ajax Standards Mode Framework Content. With fresh installations (no upgrades) as of 7.4 SPS 9, there is an URL alias portal/standards already available that will launch the new Ajax  Standards Mode desktop.





However, there are still some limitations, for example that this Framework Page should not be run in quirks mode (sounds logical :-)) and only supports IE 9 and higher. In addition, it is still true that standard and quirks content cannot be displayed together on the same page, so if you want to render content in quirks mode while using the new Ajax Standards Mode Framework Page, the content must be opened in a new window using the Launch in New Window property. Finally, the new Framework Page does not support administrative scenario, so if you want to use the Content Administration or System Administration for example, you should stick to the old Ajax framework page.


Here is what you have to do to test it after upgrading to SPS9:

1. Create a new URL alias for the portal in standards mode in the URL Alias Manager

2. Assign the new alias to the Ajax Standards Mode Portal Desktop in the master rule.

3. You need a portal page with a UI5 iView for testing. Open the UI5 iView's properties and change the value of property Launch in New Window to Display in Portal Content Area.


4. Now logon with your test user using the Portal URL with the alias for standards mode (using IE, or course)

5. Open the page with your iView. The UI5 iView will now be displayed in the portal content area. Opening a new window is not necessary any more.


If you are interested in more details, please read Matan Mizrahi's detailed blog on Ajax Framework Page in Standards Mode.



2. URL Alias for Fiori Launchpad on Portal



Before SPS9, you had to create a URL alias with URL Alias Manager in System Configuration and then create a new display rule to assign the Fiori desktop to the new URL alias. For new installation, there is now a preconfigured alias portal/fiori that is already assigned to the Fiori desktop in the master rule collection:




This feature will save you some time when setting up the new Fiori launchpad desktop, but as mentioned above, it is only available in new installations, as in an upgrade there might be a risk to overwrite existing master rule configurations.





My name is Matan Mizrahi, and I'm a software developer in the SAP Enterprise Portal group.

In the past few months we have worked really hard to adjust the Ajax Framework Page (let's just call it AFP) to run on Internet Explorer in standards mode.

I am happy to announce that it's now available in NW7.31 SP14 and 7.4 SP9 (released on November 24th).


Some details

For those of you who don't know what "standards mode" is, I will try to make it as simple as possible. However, if you want to know more, I strongly recommend reading this blog , written by my colleague Maya Amit.

Let's get started.

Microsoft Internet Explorer (MSIE or just IE) was the dominant web browser (alongside Netscape Navigator) in the early days of the internet as we know it. Web pages were built in such a way that IE could render them in its own way, without following the standards rules for the HTML web language.

Later on, when other standards-rendering browsers (like Google Chrome and Mozilla Firefox) came into the market, Microsoft began to understand the need to support standards mode rendering. Therefore , in March 2009, Microsoft released Internet Explorer 8, which adhered to the rules of the standards rendering, alongside the "old" rendering mode, called quirks.

So far some history and useful information.

Up until now, AFP could only run in quirks rendering  mode. And - as you can see on Maya's blog , SAP introduced UI5 based apps, which cannot run on quirks rendering mode, therefore we had to find a solution for those apps, which was a standalone portal page (AKA navMode 10, or "Display In separate headerless portal window(standards mode) - read more about it here, and more about other navigation modes in note 2054208).

The problem was, that when you wanted to open a SAPUI5 application, you couldn't open it in your portal, which is probably the most convenient way.

Now , after a lot of work, we've managed to fit AFP to render properly in standards mode. Now you can navigate through your portal without having to open new windows,and enjoy all benefits of SAPUI5 applications, integrated in your portal.

AFP in standards mode is supported in IE starting from IE9.

How do I use it?

It's very simple. You now get a new framework page, dedicated to AFP in standards mode:

afp std.PNG

All you need to do is enable this framework page in the Master Rule Collection:

1.First of all, go to System Administration->System Configuration->Portal Display->URL Alias Manager.

There you'll see that we've added a new URL alias, called standards. You can use it for the configuration of the new framework page,and of course you can create one of your own.

std url alias.PNG

2.Go to Desktop & Display Rules->Portal Administrators -> Super Administrators->Master Rule Collection,

and add the rule you like. You can add it to a specific user, alias,group ,role and so on.

Here's one example, but you can read more about the Master Rule Collection here and here

master rule.PNG

You can find it in Portal users->Standard Portal Users-> Ajax Standards Mode Framework Content -> Ajax Standards Mode Portal Desktop.

Then search for "Location" :

afpstd desktop name.PNG

That's it! You're all set and ready to use the AFP in IE standards mode.

Notice that you might see some slight differences between the same themes used in AFP quirks mode and standards mode.

Feel free to ask questions, comment or send any feedback.

Important note

Notice that if you are using this feature, your page will be rendered in standards mode, which means that content that runs in quirks mode(HTMLB for example) won't be able to run in the content area. To resolve this, you can use nav mode 3 (I mentioned earlier a reference to nav modes).

For more information see note 2001910 - AFP Standards mode support.

Run Simple,



today I would like to share with you some insights on Web Dispatcher configuration for a Portal system. I set up a demo system for Fiori launchpad on Portal including various types of content like Fiori apps (different waves), Personas, Mobile documents, and more. Since the new Fiori iView template (for Fiori apps wave 2 and above) only runs correctly, when the system which hosts the Fiori wave 2+ application is set up to use Web Dispatcher, we decided to have all calls going via the Web Dispatcher.


What I will show you in this blog is just an example of how our system was configured. Of course, this cannot be transferred one to one to other systems, so the intention is more to give you some kind of lead.


Let me first give you a short overview of our landscape which is geographically distributed:

We have a portal system running in Germany (in the Web Dispatcher file, I just changed that to domain: dom3), a Personas system in a second country (dom2), and a Fiori ERP system which is located in a third country (dom1) and also hosts the HANA system and the Web Dispatcher.

We configured all systems to support SSL.



This is our web dispatcher configuration file:








_PF = $(DIR_PROFILE)/<file-name-of-profile-file>







# Accesssability of Message Server


rdisp/mshost = fiori.dom1.corp

ms/http_port = 8101


# Configuration for medium scenario


icm/max_conn = 500

icm/max_sockets = 1024

icm/req_queue_len = 500

icm/min_threads = 10

icm/max_threads = 50

mpi/total_size_MB = 80


# SAP Web Dispatcher Ports


icm/server_port_0 = PROT=HTTP,HOST=fiori.dom1.corp,PORT=81$$

icm/server_port_1 = PROT=HTTPS,HOST=fiori.dom1.corp,PORT=4050

icm/server_port_2 = PROT=HTTP,HOST=fiori.dom1.corp,PORT=8101

icm/HTTP/admin_0 = PREFIX=/sap/admin,DOCROOT=$(DIR_DATA)$(DIR_SEP)icmandir,AUTHFILE=$(icm/authfile),PORT=81$$


# Start webdispatcher



Execute_00 = local rm -f $(_WD)

Execute_01 = local ln -s -f $(DIR_EXECUTABLE)/sapwebdisp$(FT_EXE) $(_WD)

Start_Program_00 = local $(_WD) pf=$(_PF)



#Configuration Entries

wdisp/system_conflict_resolution = 1

wdisp/add_clientprotocol_header = 1

wdisp/handle_webdisp_ap_header = 1

wdisp/add_xforwardedfor_header = true


rdisp/TRACE = 1

# Automatic Rendering Info of systems

#wdisp/group_info_protocol = http

#wdisp/ping_protocol = http

#wdisp/url_map_protocol = http

wdisp/ssl_encrypt = 1

ssl/ssl_lib = /usr/sap/<system-name>/SYS/exe/f/g/

ssl/server_pse = /usr/sap/<system-name>/<instance-name>/sec/SAPSSLS.pse

ssl/client_pse = /usr/sap/<system-name>/<instance-name>/sec/SAPSSLS.pse

icm/HTTPS/verify_client = 1

wdisp/ssl_auth = 1

icm/HTTPS/forward_ccert_as_header = true

icm/HTTP/mod_0 =PREFIX=/, FILE=/usr/sap/<system-name>/SYS/profile/rewrite.txt

wdisp/system_0 = SID=<system-ID HANA>, EXTSRV=https://fiori.dom1.corp:4302,SRCSRV=*:4050, SRCURL=/sap/hba/;/sap/hana;/sap/bi;/sap/ui5;/sap/check

wdisp/system_1 = SID=<system-ID HANA>, EXTSRV=http://fiori.dom1.corp:8002,SRCSRV=*:8120, SRCURL=/sap/hba/;/sap/hana;/sap/bi

wdisp/system_2 = SID=<system-ID Personas>, MSHOST=personas.dom2.corp, MSPORT=8100,SRCSRV=*:4050, SRCURL=/sap/bc/personas;/sap/public/icmandir

wdisp/system_3 = SID=<system-ID Fiori>, MSHOST=fiori.dom1.corp, MSPORT=8101,SRCSRV=*:8120;*:4050, SRCURL=/sap/bc/;/sap/public/bc/;/sap/opu/odata;/sap/opu/sodata/;/sap/es,  CLIENT=004

wdisp/system_4 = SID=<system-ID Portal>, EXTSRV=https://portal.dom3.corp:50001, SRCSRV=*:4050, SRCURL=/irj/;/

wdisp/system_5 = SID=<system-ID Portal>, EXTSRV=https://portal.dom3.corp:50001, SRCSRV=*:4050, SRCURL=/mcm/;/



In the section SAP Web Dispatcher Ports, we configured a port for HTTP as 81+system number, being 8120, and the port for HTTPS as 4050. To make communication more secure, we use SSL and now call our portal at https://fiori.dom1.corp:4050/irj/portal (because the Web Dispatcher runs on the fiori.dom1 system). Personas applications are called at https://fiori.dom1.corp:4050/sap/bc/personas/ + some parameters, while the relative path to Fiori applications starts with /sap/bc/ui5_ui5/.


To overcome possible resolution conflicts, we set wdisp/system_conflict_resolution = 1, so the first fitting system entry is selected and put first

wdisp/system_2 = SID=<system-ID Personas>, MSHOST=personas.dom2.corp, MSPORT=8100,SRCSRV=*:4050, SRCURL=/sap/bc/personas

to filter for all personas application calls, and then

wdisp/system_3 = SID=<system-ID Fiori>, MSHOST=fiori.dom1.corp, MSPORT=8101,SRCSRV=*:8120;*:4050, SRCURL=/sap/bc/;/sap/public/bc/;/sap/opu/odata;/sap/opu/

to direct all other calls with a relative URL starting with /sap/bc/ to the Fiori system.


Note that for the message server entries for both the Fiori and the Personas system are defined using parameter MSPORT and the http port, as SSL is only used for the connection to the backend application server, but not to the message server.


In general, there are different manners how web dispatcher can be configured for SSL, but we decided to use SSL re-encryption where the Web Dispatcher decrypts the HTTPS request and then SSL-encrypt the request again before forwarding it to the web application server. This is configured by

1. Setting PROT=HTTPS for the ICM/server_port: icm/server_port_1 = PROT=HTTPS,HOST=fiori.dom1.corp,PORT=4050

(for decrypting the request)

2. Setting wdisp/ssl_encrypt = 1 (for encrypting the request again)

3. Configure the web dispatcher with PSEs, signed certificates, and credentials according to the documentation (

If you are interested in more details and a much more complete guide on Web Dispatcher configuration for SSL, I highly recommend reading How to Configure SAP WebDispatcher for SSL. A great guide!



Hi Portalpeople.


Just want to share the solution of a problem i met today.


In Portal (7.3) Manager, who was about to approve a Travel Trip from UWL, got an error when trying to open attachments in the relevant Trip.


The error was: "Application Blocked by Java Security"

Java error_2014-11-25.png


At first we tried to follow the bullet of the solution in note


But that did not do the trick.


The trick was the Exception Site list in Java Security tab.

Here, enter the backend system server and port used when running http://<server>:<port>/sap/bc/gui/sap/its/webgui/

(Actually we ended up not using the specific path, only http://SERVER:PORT)


Hope this can help other avoid using 4-6 hours on this.


KR Michael

In this blog I will explain about the URL to Help Topic mechanism and how to use it properly.


Considering you are doing your testing on one portal (DEV) and want to move it to QA and later to production, you won’t need to manually edit the settings of every iView and change the URL for the help topic for the new server’s URL, in case that the help topic resides on that server (absolute URL).





The first, and perhaps the easiest solution for this, is to create and deploy an HTML static page resource - a simple Portal Application which does not contain any Portal Components or Services, but only consists of some static web resources which resides under a help folder.


After deploying it, (for example, an application named “MyHelpResources”), set the "URL to Help Topic" property to "/MyHelpResources/help/1.html" and the content of 1.html is added to the markup of the body of the opened help window.



With this approach you can address static content on the current server without using absolute URLs.

You can deploy the static help pages on any of your systems (development test and production) and there is no need to change the configuration of iViews between the systems if you are transporting the content between them.



Assuming you need to address a help page which is more sophisticated than static content, the HTML can redirect you by a script to a relative URL or just open a frame within the markup addressing the wanted relative URL.



The second approach uses the delegator mechanism.

When you set the "Show 'Help' Option" of an iView to true, it enables the help option in the iView tray resulting in launching the iView using the PRT help Mode.

If the component, which the iView is based on, has implemented the doHelp() function in the code, it will be invoked, otherwise, a delegator will be invoked.


What is a delegator?

A delegator is a different component which can be called by one component.

You can read more about it here:


And also, you can read about it in my next blog which will have a link to once it’s published.


When a Portal Component, which is the basis for any iView, is launched in a certain mode, a set of fallbacks is being triggered to decide the rendering code that will actually be invoked.

If the component did not implemented the doHelp function in its code, a delegator component, either specific to the component, or a default delegator will be invoked.

If none of the above exist, then the default mode - doContent implementation of the component will be invoked.

By default there are several mode delegators that are provided with the SAP NetWeaver Portal.

In order to view those delegators, you can use the Portal Registry Browser component that can be launched using the following URL:


Then navigate to "runtime" -> "prt.modes"

The component which is registered as the default delegator for the help mode is and its implementation of the doHelp method is what provides the actual functionality.

In the next blog, I will explain how to write your own default delegator which overrides the “SystemModes” delegator.

In the portal the UI Theme Designer has a CSS tab that doesn't work (yet!). You can add custom css styling in there, but nothing happens. Previously you could download the theme via the Web Repository WRR, manually change the less files and upload it into the portal. Then you need to recompile the theme. Please note: this is undocumented and you don't have any support from SAP.



This is how it works

The CSS tab is available, you can enter everything in it as you want, but during compiling nothing is added. So we need to add the custom.less file, which is created if you enter css information in the CSS tab.


First I will create a new theme, based on goldreflection:


Screenshot - 18-11-2014 , 14_13_57_ver001.png


I will rename my Custom Gold Reflection theme to "PeppiePortals" and open the UR Control Properties.


Screenshot - 18-11-2014 , 14_19_32.png


1. Create the custom.less file


Select the CSS tab now.


After selecting UR Control properties, select the "All/no selection (middle arrow)". At the left hand side all Controls will be displayed. Just select a random UR one.


After selecting you will see at the righthand side UR Technology: Unified Rendering appear. It is time to add some CSS styling.


Be aware of the fact that a lot of elements can be styled with the UI Theme Designer in the Expert tab as well. This feature is only for adding new css properties that do not exist in the current theming.

As an example I have added the css style "urPgHTTxtSmall". For this element the background color will be set to red. Again, this is tricky since the .urPgHTTxtSmall will be used on more places in WebDynpro than in this example. So know what you do


Screenshot - 18-11-2014 , 14_35_36.png


Now save the theme (and publish it, so it is generated in the WRR).



2. Download the theme and edit the less definition


Go to Content Administration > Web Repository


Screenshot - 18-11-2014 , 14_45_41.png


Expand the theming folder and navigate to UR > ls. Now open your custom theme folder. You will see a custom.less file which you created in step 1. You will need to change the base.less file to import the custom.less file.


Right click on the base.less file and download it. Edit the file with your favorite text editor, too bad Edlin is not available anymore, so I am using Notepad++.


Screenshot - 18-11-2014 , 14_49_47.png

Add the statement


@import "custom.less";


And save the file.


Upload the base.less file and replace it with the old version. (select yourfolder > right click > select upload)


Screenshot - 18-11-2014 , 14_52_54.png


Now we need to open the UI Theme Designer again and recompile the theme.

Screenshot - 18-11-2014 , 14_56_45.png

Screenshot - 18-11-2014 , 14_57_58.png


Now check if the css is displayed correctly. If this works, you can change stuff directly in the CSS tab and recompile the theme. This will save you approx 2 minutes per change! In my case... this saves me a LOT of time!


Screenshot - 18-11-2014 , 15_03_26.png



Hope you can use this as well Happy branding again!



Noël Hendrikx - SAP Portal consultant @ Peppie Portals.

Specialized in Corporate branding SAP Portal / Adobe Interactive Forms.


UI Theming blog series

Portal theming - also waited a couple of years?

How to... UI Theme Designer - Installation

How to... UI Theme Designer - Migration

How to... UI Theme Designer - Locating elements

How to... UI Theme Designer - Transportation

How to... UI Theme Designer - Make use of the Custom CSS tab in the Portal!



Other blogs:

Tired of zipping / unzipping portal theme?

Tips for the Portal Content Studio

DSM Terminator and popup blockers (or not)

My best development friend - Autoresponder FTW


As a new member to the SAP Community Network, I wanted to earn points and gain badges and I found the SAP NetWeaver Portal: Movie Challenge an exciting and fun task.  This also gave me the opportunity to write my first blog post on SCN.  For me, learning the navigation and how to develop myself via this medium are key to my progression within the organisation as a support engineer. I am also thrilled to be a part of a company who's strategy is trying to match the moving needs of their customers.


The video that most intrigued me on the SAP Portal YouTube Channel was the Customer Testimonials from P&G (Procter & Gamble).



The reasons I wanted to review this particular video is because;


  • I have an extensive background within the Retail industry.
  • I studied Business (Management) as my primary degree.
  • I wanted to see the Customers opinions on SAP's Systems and how it improved their organisational processes.


Ulf Westhoven, who is the NetWeaver Service Manager at P&G explains, that their purpose 'Is to improve the lives of the worlds consumers, now and for generations to come', using SAP systems simplifies their business processes to try and achieve this goal.  Prior to this, the organisation used many IT Solutions and this confused the users and effected the companies overall purpose. Ulf also explains that the SAP System provided the scalability and functionality for the organisation and that their large scale rollout wouldn't have been possible without SAP.


Ulf then mentions how the NetWeaver Portal has dramatically improved the UI, and that users are delighted that there is no longer multiple systems to login to for different functions.  The accessibility of the information is also another item he brings up, that staff are now able to access the data and information through mobile devices which is of huge importance in modern organisations.


This video gives a great insight into how SAP Systems can benefit and improve business processes within an organisation and simplifying even the most complex of tasks.  It also shows how SAP are moving with changes in the current marketplace with mobile communications being of vital importance. Overall, I thoroughly enjoyed the video as it was very informative on how SAP changed the organisations functions and how it dramatically effected the company globally.  This video can help inspire future customers when seeing the success story of P&G using SAP Products.


Thanks for taking your time to read!


Dave Courtney



With NetWeaver 7.4 SP7, there is a new Fiori framework page available to enable portal users to launch Fiori applications from a Fiori Launchpad like UI. Since the new framework provides lots of benefits to the users beyond just UI harmonization, great usability, and responsiveness (e.g. support of Fiori apps wave 2 and above), it was clear to me that I wanted to take my Mobile Portal demo scenario to the next level and move it to the new design.


In this blog, I will share some insights and experience on what changes between the classical Mobile Portal and Fiori launchpad on EP.



1. Enabling Fiori Launchpad


As of NW 7.31 SP12 / NW 7.4 SP7, there is a new Fiori Desktop and Fiori Framework Page available. You can find both in Portal Content > Portal Users > Standard Portal Users > Fiori Framework Content. Just assign the desktop to a your own URL alias (defined with URL Alias Manager) in a rule collection to make it available.



2. Content


It is important to understand that users can consume any type of content (like Web Dynpro, SAP UI5, SAP Screen Personas) in the new Fiori Launchpad on Portal and not just Fiori apps. You can run all Portal iViews in Fiori Launchpad. With 7.4 SPS 8, there is a new type of iViews, which was not available before, the SAP  Fiori iView for Fiori wave 2 and above applications.


Like for Mobile Portal, the new Fiori launchpad content is assigned to the Portal user in portal roles. In FLP on Portal, the roles contain all iViews to which the user has access via the tile catalog, but the user can select and personalize which of these iViews he wants to see on his Home Page.



3. Personalized Launcher vs. Tile Catalog


My Mobile Portal uses the Personalized Launcher to give users access to applications and to provide a catalog with additional content for personalizing their Mobile Portal Launcher. Concept wise this is not very far away from what the Fiori Launchpad provides. Here as well, you have a catalog which contains all iViews/tiles that you can display in your Fiori launchpad. This tile catalog, like in the Personalized Launcher, is structured by categories. The iView property Mobile App Categories defines in which categories of the tile catalog an iView shows up - just like in the Personalized Launcher. There is just one difference: The location where the available categories are defined changed. You now configure the categories (ID, order, and title for each of them) in very much the same way as in Mobile Portal, just in a different iView: Fiori Launchpad Categories in Portal Content > Portal Users > Standard Portal Users >  iViews > Fiori Launchpad.





4. Filter ID vs. Object ID of Device Group


Mobile Portal uses filtering based on filter IDs to determine the content for each device type. This is not always easy, so I really like the new, simpler way of doing it: device groups. Already for Mobile Portal, you configured device groups to assign them to different portal desktops with specific appearance and behavior. Now, you can just reuse them and define for each iView on which device groups it should be displayed. This is done in the iView property ObjectID of Device Group.




After that short introductory comparison, here is what I did to set up my Mobile Portal scenario with Fiori launchpad on Portal:




1.  Define the Portal URL alias and assign it to Fiori desktop in Master rule collection



2.  Configure the tile categories in the Fiori Launchpad Categories iView




3. Since I wanted to keep my mobile Portal content in place, I just created a copy of the portal role used for Mobile Portal.


4. I removed all the filter IDs, since they are not needed in the FLP scenario, and made sure that all iViews are set to Visible in my role.



5. For all iViews, I adapted the following properties:


    a. Object ID of Device Group: I found the Object IDs in the Device Group Manager in System Administration > System Configuration > Portal Display



and entered those on which the iView should be displayed separated by semicolons into the iView property.


If the property remains empty, the iView will not be displayed on any devices, so this property is really important. And note that you have to enter the ID of the device group, not its name.



    b. Native: Checked it for native apps, so they only appear on mobile devices.


    c. Permanent in Launcher: I checked all iViews that should show up in the user's home page when he first logs in. If you do not set any iViews as Permanent in Launcher, the user will first see an empty page, when he logs in. He can then open the tile catalog and assign tiles to his default group My Home or create other groups and assign the tile to it. Users can still remove iViews marked as Permanent in Launcher from My Home.


    d. Image Type for defining the way the selected image will be displayed (as an icon, full tile).

    e. Mobile App Categories: I entered the IDs of the categories I wanted to assign as a semicolon separated list.



6. To enhance my demo, I added also some Fiori wave 2 apps. The Fiori wave 1 apps run as in Mobile Portal (see my blog about that), but for Fiori wave 2 and above apps, there is a dedicated iView template available. There is a detailed blog by Irena Kull on this topic. Please note that the system that hosts the Fiori wave 2 application needs to be set up to run with web dispatcher.

7. As a second enhancement, I added some Personas apps. Please see this blog for details.


8. I created a new demo user and assigned my new role to him.


9. Then I logged in with the demo user, created some groups (Sales Executive, Employee Services), assigned some tiles from the tile catalog, and moved some of the permanent tiles around. Here you see the result:



Finally, you can also customize the portal theme used in the Fiori desktop with the UI Theme Designer.


Hope that was helpful,


For many customers, the consumption of the SAP Enterprise Portal on mobile devices is a major enhancement for their existing SAP Enterprise Portal implementation and, in some cases, a key component in the corporate mobile strategy.


Since the release of SAP Fiori and the introduction of the Fiori launchpad with a clear strategic direction to (1) apply the Fiori launchpad on multiple platform (ABAP, SAP Enterprise Portal and Cloud) (2) align the User Experience of the different clients (Portal, NWBC) with the Fiori User Experience - the new Fiori framework page is the recommended framework page for consuming the SAP Portal on mobile devices in a launcher/launchpad scenario.


Additional enhancements and new functionalities will be delivered as part of the new Fiori framework page.


While designing and developing the new Fiori framework page (a.k.a FLP@EP) we put special attention to minimizing the transition effort between the previous mobile framework pages and the new Fiori framework page (by using the same configurations and settings), while providing more capabilities with the new one, such as:


  • Rich end user experience for desktop and mobile consumption
  • Responsive design running on both desktop and mobile devices with an aligned User Experience across devices, following the SAP Fiori design
  • Extended PAM support
  • Theme customization with the UI theme designer
  • Developed on top of SAPUI5 libraries





Customer running the existing mobile framework pages (i.e. Personalized Launcher and smartphone/tablet framework pages) are advised to evaluate and plan to implement the new Fiori framework page for mobile (and optionally desktop) consumption.




Customer who are now starting a project to consume the SAP Portal on mobile devices are advised to use the new Fiori framework page.


Finally, the renewal of the portal with the Fiori design is not complete without the integration of the Fiori applications in the portal, and this is also already available for a subset of the Fiori apps. For the veteran portal experts, you can think about the Fiori apps as the new multichannel business content for the portal, across devices.

SAP has developed, a few years ago, a way to push events (messages) from server to client without having the end user click any button or do any action.

The main purpose of this feature was to have a chat application between Portal users.

This method is called RTMF.


RTMF is a j2ee servlet which loads javascript files to the browser which polls the server every interval of time (Usually 3 seconds).

Since RTMF is deprecated and due to performance reasons, there are 2 alternatives for the same type of functionality:

  1. HTML5 websocket which can be read more about here:

  2. SAP WebDynpro “TimedTrigger” element.

In this blog, I’ll explain how to use the 2nd option.

In order to have a push channel in your WebDynpro application, you simply add the TimedTrigger element to your view (don’t worry, the element is not visible when the application is running).


In the properties of the element, set the delay time (polling interval) to a desired time, for example 2 seconds.

The element also has an “enabled” property which can be bind to a Boolean attribute so you can switch on and off the polling to the server.

In the “events” tab of the element, create an event handler for the onAction event.

This handler will be called every 2 seconds and in that method you can implement the logic that you want to perform.


The biggest advantage of the TimedTrigger element is that you can have your heavy and long running logic run in the background while the UI is not stuck waiting for a response about the long running operation.

I’ve created a sample WD application which is an empty view that only has a timedTrigger element set to 2 senconds and recorded the HTTP requests with HTTPWatch and this is the result:


As seen, every 2 seconds, a request is being sent to the server, to the application I have created.

You should know that there is another type of WD element which offers the same functionality called MessageBasedTrigger.

This element is using RTMF as the framework that delivers data from server to client, but since RTMF is deprecated, you should not use it as well.

Hope this blog will help you in your development of WD applications.

Official documentation for TimedTrigger:

Welcome to the September and October edition of the SAP Portal news blog summarizing the highlights of the last two months. This time we have the following topics:


  • SAP TechEd News
  • SAP Fiori Launchpad News
  • SAP HANA Cloud Portal New
  • SAP Enterprise Portal News
  • Partner Test Events
  • Blogs from the Community


SAP TechEd News and Impressions


What is the role of Portals today, in which directions is SAP Portal transforming and which Portal deployment option is the right one in the days of cloud and SAP Fiori? These are question we discussed at SAP TechEd Las Vegas with many customers. For external facing scenarios, we see more and more customers now starting to adopt our solution HANA Cloud Portal to create their business sites. With many customers at SAP TechEd we discussed the question how the concepts of SAP Fiori launchpad and SAP Portal fit together. With the introduction of Fiori launchpad on the HANA Cloud Platform, you will also see Fiori launchpad and Fiori experience included into HANA Cloud Portal. We are in the process of transforming and reinventing portal - on the cloud and based on the SAP Fiori UX paradigm. If you are at SAP TechEd Berlin, join us and we continue the discussion. Check out our SAP TechEd information site built with our solution HANA Cloud Portal.


See here Aviad Rivlin in his packed networking session on SAP Fiori launchpad at SAP TechEd Las Vegas:


...and Yariv Zur explaining the Portal deployment options: On-Premise, Managed, or full cloud:


SAP Fiori Lauchpad News


Get an overview on the latest release of SAP NetWeaver 7.4 Support Package Stack 08 (and the corresponding release NW 7.31 SP13) and the new features in SAP Fiori launchpad running in SAP Enterprise Portal.


Starting with SAP NetWeaver 7.4 SPS8 you can also run Fiori wave 2+ transactional applications in SAP Enterprise Portal. Watch this product demo showing how this integration is configured:



The integration between the SAP Enterprise Portal and the Fiori apps is getting more and more important for many customers. This new white paper will guide you through the common architectures for consuming the Fiori apps via the SAP Portal, and running the SAP Portal (with the Fiori apps) on mobile devices, outside of the corporate network. Read also the blog SAP Portal and SAP Fiori - Common Architecture by Aviad Rivlin.


You are interested in new and changed features of SAP Fiori launchpad in User Interface Add-On SPS10 for SAP NetWeaver? Then check out this blog written by me.


You missed SAP TechEd Las Vegas and you will also not go to Berlin? You can get some details on our SAP Fiori hands-on session in this blog and you can also watch some interesting product demos.



SAP HANA Cloud Portal


At SAP TechEd Las Vegas we announced the availability of the SAP Fiori launchpad running on SAP HANA Cloud Platform as part of the HANA Cloud Portal offering as a full SaaS (Software-as-a-Service) solution. Fiori launchpad on HANA Cloud Platform can run in a hybrid architecture, where the user interface is running on the cloud and the business data is consumed from the on-premise systems in a secured way. Or it can run in a full cloud architecture, where both the user interface and the data, resides in the cloud.


About two years ago Danone’s IT department was requested to develop a Web CRM system (B2E scenario) to be used by customer service operators working at Danone’s call centers located in South Africa.  They started with building a monolithic application, based on SAP UI5, but this solution did not fit all the requirements.  After reviewing some products available on the market, Danone chose SAP HANA Cloud Portal because of its flexibility and easy branding and customization, easy integration with SAP and non-SAP sources, out-of-the-box widgets, mobile consumption and social experience. The original monolithic application was broken down into smaller components that were reassembled into a portal website. You can find more information in this blog Marco Paciucci. At SAP TechEd && d-code in Berlin, November 11-13 2014, Danone will be hosting a session dedicated to this topic.


Developers may wonder, in which case they should use SAP HANA Cloud Portal or when a single “monolithic” application would be sufficient? This white paper aims at giving the developers the guidelines on when they should use Cloud Portal and what is the value proposition it offers to application developers.


SAP Enterprise Portal News


Applying corporate design guidelines to your SAP Enterprise Portal is about to become much easier. You should get familiar with using the UI Theme Designer tool in SAP Enterprise Portal, which is a browser-based tool that enables easy theme building by modifying one of the theme templates provided by SAP. For more information read this blog by Orit Harel - that also contains 3 great product demos (activating the theme designer, migrating thems with the theme designer, examples of theming capabilities).


In this blog post by Tal Haviv, you can find sample code on how to read/save cookies in portal component java code or using javascript.


The newer versions of IE with standards mode can cause many rendering issues, which affect EP rendering. Read this great blog by Maya Amit who analyzed different scenarios and describes how to solve the issues.


Partner Test Events


You can still register for our SAP HANA Cloud Portal partner tests in Palo Alto and Walldorf this year. These complementary 3-day hands-on partner events are aimed at partners who are looking to exploit opportunities in the marketplace by getting direct access to SAP HANA Cloud Portal and its integration with leading SAP cloud solutions such as SuccessFactors extension platform and SAP Cloud for Customer. Read more in this blog in which you also find the information how to register for the event.


Blogs of the Community

We recommend reading the following blogs written by members of the Portal and HANA Cloud Portal communities on SCN:


Embed YouTube Video with Custom Image & Text Overlay in HANA Cloud Portal Site by Ameya Pimpalgaonkar


Extending SuccessFactors by creating an extension site over HANA Cloud Portal (On Trial) by Zohar Yehezkely


SAP NetWeaver Portal Movie Critic: What Is Responsive design? by Mark Whately

Video: The World Today - Intern creates a pretty freakin cool event site

Director: SAP Portal

Published on Dec 10, 2013


This comedy is fresh and energetic, and its pace, acting, and dialog will appeal to people from young techies to seasoned office workers, no matter their line of work.



The movie starts with the introduction of the youthful Event Intern Emma Green, who was "widely applauded in her office of Atomic Publishing for creating a pretty freakin' cool event site." In a reenactment of her amazing accomplishment, Emma is shown adding widgets and images to a webpage. As the voiceover informs us, creating the event site took Ms. Green "about five minutes." While we listen to other employees laud her hard work and understanding of technology, it's clear her colleagues have no idea how quickly and easily Emma created the event site.  As John Kimmel, Head of HR, puts it, "...these tech types--I'll tell you what, I mean, computers, the Internet, yeah… ."  With her ample free time, we see Emma doing all manner of non-work activities: sleeping at her desk, texting, and riding some kind of (totally rad and awesome) 4-wheeled bike through a corridor.



Favorite scene:  We see Emma's manager speaking to the camera in the foreground.  "[The IT department] didn't get it...  Young people, they get it.  Twitter, Facebook, you know?  They can do that stuff all day long.  No brainer.  Hack into things, control satellites?  This is exactly what we need for the office."  As her manager speaks, Emma is shown in the background shopping online, using Facebook, playing Candy Crush on her phone, and painting her nails.


If the movie was made purely for entertainment purposes, I rate it a 10/10.  However, if it was trying to convey information about the capabilities of SAP Portals or Hana Cloud Portal, I think it could be improved by conveying more information about which application Emma used to created the site -- perhaps by taking a little more time to show how she was using the tools, by pausing longer on frames that showed "Powered by Hana Cloud Portal," or by including more SAP branding in the shots.  I also think the movie could benefit from having someone mention "Hana Cloud Portal," "SAP Portal," etc. I think SAP terminology could be used in the movie in a way that still fits with the movie's tongue-in-cheek style.


Bottom Line:  This is a funny movie and worth re-watching, but I recommend making the SAP brand more apparent.


Liked this blog post?  Visit SAP NetWeaver Portal 2014 Movie Challenge for more movie reviews and all the details you need to blog your own movie review.


when preparing a demo system for TechEd, we set up a Fiori Launchpad running on Enterprise Portal (blog to follow). To complete the demo, we planned to add a transaction edited using SAP Screen Personas to the Portal. I found a nice blog by Peter Spielvogel about the integration, but then noticed that this is on SAP Screen Personas 2.0, while our systemwas on 3.0.



Here is a description about how to integrate a transaction edited with SAP Screen Personas 3.0 into the Portal. I first published this blog describing the integration using a URL iView. This worked fine - however, the recommended way is to use an Application Integration iView for UI5 applications.

Therefore, you will find the adapted description below now:



Step 1: Get the flavor ID in the Personas System



Go to SAP Screen Personas Flavor Maintenance (TA code /PERSONAS/FLAVORS) and search for your flavor. I used the transaction for which I had created the flavor to search.



In the results screen, you find the ID of the flavor.









Step 2: Create an SAP system in the Portal


In the Portal system landscape, I created a new SAP system (using dedicated application server) to connect to the SAP Screen Personas system and gave it an alias. Next, I assigned end user permissions for my new system to the Fiori Launchpad user. Then I established trust between the Personas system and the Portal.





Step 3: Create a UI5 iView


In Portal Content Management, I created a new UI5 iView.

Navigate to Portal Applications >  Personas2_PortalApps.png.

Copy the UI5 template, then select a folder under Portal Content and click Paste as PCD Object.


Give your new iView a name.


In the iView properties, I made the following settings:


Relative Path for UI5 Applications:/sap/bc/personas?~transaction=<transaction_to_be_launched>&sap-personas-flavor=<ID of the flavor I created>

System: Alias of myPersonas system

Application Parameters: sap-ie=Edge (UI5 applications need to run in standard mode)

Launch in New Window: Display in separate headerless portal window (standard mode)




To make the iView visible in Fiori Launchpad, I had to set some properties in addition (see Shani's blog on Sample content for Fiori launchpad for Portal or mine on Mobile Portal with Fiori Launchpad) and to assign it to one of my Fiori Launchpad roles.




And here we go:





Hope that was useful.




In this video Aviad Rivlin, product manager for SAP Portal announced he will share information on topics of SAP NetWeaver Portal mobile edition, SAP Fiori and their integration.



Regarding purpose of this video cheerful background music, length of presentation of both platform and final invitation to join and attend this lecture is excellent.


Parts that could be improved:

- Aviad gives impression like he is reading text on the left side of the camera all the time except during invitation at the end of the video.

- at the end of the video  url's to social media pages of SAP Portal are displayed. Those URL's should be real links to those pages - it's widely used functionality.


Since I work with SAP CI and CC for almost 3 years now I came to conclusion that it is time to meet people from SAP I have been working with and what is the better occasion for that than TechEd conferences?

Combined with opportunity to learn something new during interesting lectures like it has been Avid lecture for sure, it will be the best used time.


This Blog is part of the SAP NetWeaver Portal Movie Critic - Challenge. For more information about that and how to participate check out  Announcement of SAP Portal and HANA Cloud Portal Gamification Movie Challenge


Thank you for taking the time to read my review.





Filter Blog

By author:
By date:
By tag: