1 5 6 7 8 9 37 Previous Next

SAP Enterprise Portal

553 Posts

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:

  • SAP Web Dispatcher or any other reverse proxy, which is responsible to dispatch the requests between the ABAP Frontend Server (FES) and Java server (EP)

Note: only one FES is supported as of today.

  • 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
  • Administrators need to activate the following OData services in the Customizing activity to enable the Remote Content editor:
    • /UI2/INTEROP
  • An ABAP FES user has to assign catalogs/groups to one of the his roles (from transaction SU01 open the tab Roles, choose a role, open tab Menu, open the rightside dropdown list of Transaction button, choose Catalog or Group, search for the  required catalogs/groups and assign them to the role).


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:
      1. Use the link https://<server>:<port>/nwa and search destination in search window
      2. Define a new destination for the ABAP FES of type "http". 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/
      3. Choose your logon type in Logon Data tab. For the type Basic provide an FES user (and password) to which the catalogs were assigned
      4. Choose Ping Destination button to check the connection.

      • Destination name can contain alphanumeric characters (a-z,  A-Z,  0-9), special characters (underscores (“_”), hyphens (“-”), parentheses, and tildes (“~”))
      • Destination name cannot include spaces
      • FIORI_CATALOGS  service should be activated on FES
      • ABAP FES authorization should be granted for the EP administrative scenario (details).

     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. Make sure that no role/role folder/workset above the chosen one is marked as an entry point as well (like in the example below: the folder ESS_WDJ is marked as an entry point, and the main role FFP_Demo_SP16 is not.)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 or NW 7.40 SP11 and NWBC 5.0 PL5 or higher.

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

Remember my blog about IE and Portal which covered many scenarios that exposed rendering issues when running Portal in IE browsers? Just when we thought we’d covered all the possibilities, we discovered we hadn’t…

This blog covers another rendering issue we found in IE11 when running an iView in standalone mode.

What’s standalone mode?

Standalone mode means opening a Portal iView by navigating directly to the PCD path of the iView without using the Portal APIs, or in other words, without any Portal framework page. This is in contrast to opening a Portal iView by navigating to the content area, where the target is displayed in place.

Here’s an example of what a direct call to an iView looks like:


Navigation can be triggered by either of the following:

  • Calling an “EPCM.doNavigate” JavaScript method to get the target as a parameter (there are other parameters to this method but I won’t discuss them here).
  • Navigating to the Portal and adding the target iView as a parameter:

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&


Navigating to the Portal calls the content area and passes the “NavTarget” (the target iView) as a parameter in the post data. For example:



In the HTTPWatch snapshot below, you see the call to the content area and to the NavTarget (the iView that the Portal needs to navigate to) parameter in the “Post Data” tab:



(By the way – I published a blog in the past which discusses an interesting issue caused by calling content directly and not via the navigation APIs)


When would an iView run in standalone mode?

Sometimes an application (either an SAP application or a custom application) links directly to Portal iViews instead of calling them via the navigation APIs. BI Launcher is an example of this type of application. They trigger “window.open” and send the “open” method the direct link of the iView.


Another case where iViews run directly is when you preview an iView (you can preview an iView when you edit it in content management).


What’s the problem with running iViews directly?

As long as an iView is running within a Portal framework (full portal/ separate window/ separate portal window/ separate portal window standard mode, and so on), the browser automatically opens with correct document mode (standard/quirks).  This occurs because the Portal framework sends a parameter in the response header called “x-ua-compatible” to the browser. For example:

  • Running in Ajax framework page – the value is “IE=5,IE=EmulateIE7” (which means quirks).
  • Running “Ajax Standard Mode Framework” – the value would be “Edge” (which means standard).
  • Running in a separate Portal window standard mode – it would be “Edge”.

In the HTTPWatch snapshot below, we see the property sent in the first call of the Portal (by the way, it will be sent only when running in an IE browser because only IE recognizes the property):




Running an iView directly means that the framework “services” are lost, include sending the parameter for the correct document mode. The new standalone browser window containing the target iView opens in the default document mode of the specific IE version.

Why do most rendering issues arise in IE11?

Recently, a lot of customers upgraded their IE browser to IE11 and this issue emerged for many of them: the iViews opened in a new browser window via direct URL are not rendered well.


When examining the document mode of the browser, we at SAP could see that it was set to “Edge” instead of “IE5 Quirks” or just “Quirks”.

Why did this suddenly arise in IE11 and not in older versions of IE? That’s because up to IE11, new windows open in “quirks” mode by default. However, since IE11, new windows open in “Edge” mode by default. So we need to instruct it explicitly to open in quirks mode.


Of course, there could also be the opposite situation:  an iView requiring standard mode rendering (Edge) and running on an IE older then IE11 opens automatically in quirks mode. But this seems to be an infrequent scenario.


What’s the solution?

The solution for this phenomenon is quite simple: add the “x-ua-compatible” property to the iView header.


A new property has been added to the root iView of AI iViews. This property is called “Default Document Rendering Mode”. This property has 2 possible values: “Quirks” or “Standard”. The default value for the property is “quirks”.


When the value is set to quirks – the header that is added is:

<meta http-equiv="X-UA-Compatible" content="IE=5, IE=EmulateIE7"/>


And when it’s set to standard – the header is:

<meta http-equiv="X-UA-Compatible" content="Edge"/>


In the HTTPWatch snapshot below, you can see that the property is added to the head of the returned HTML:



Note that when the property is returned from the framework – it is set in the response header, and in the iView it is set in the HTML head.

Both methods are valid, but if the value is set to both – the response header overrides the HTML head and its value  affects the browser.

Solution evolution

At first, the solution was implemented only in BI iViews, because these were the first scenarios we dealt with.

The SAP Note with the solution for BI iViews is:

2012705 - BI iView's are not render correctly when using Internet Explorer 10 and above


When we received feedback about other iView types, because the solution for BI iViews had proved a good solution, we extended the solution to all AI iViews. The SAP Note is:

2098706 - iView rendered corruptly when using IE10 and above when executing it directly or from headerless window


And there’s also SAP Note 2163649 which fixes a regression from SAP Note 2098706

2163649 - More scenarios of opening an iView directly (standalone) with IE10 and above causes rendering issues (continuation of note 2098706)

Troubleshooting and workarounds

  • If you deployed the fix from one of the above notes and this still doesn’t fix the issue – it might be that the iView was not updated with the new property.

You can check it by opening the iView properties via the “Content administration” tab and checking if the  “DefaultDocumentMode” property exists. If it doesn’t, perform the following steps:

  1. Navigate to Content Administration -> Portal Content Management.
  2. In Portal Content, expand the Portal Applications folder, and select com.sap.portal.appintegrator.sap.portalApp.PNG
  3. From the right-click menu, choose “Update PCD Objects”.
  4. Go to the iView and check that the “Default Document Rendering Mode” property exists.

  • If you have the version with the fix from SAP Note 2012705 and you don’t want to implement the more advanced note – you can use a workaround of adding the “DefaultDocumentMode” property to other iView types manually via the PCD inspector.

        If you want to implement this workaround – follow the steps mentioned in this document

Background: This connector relates to the Notifications received by UWL from Knowledge Management (KM).


blOG3 UWL ActionInboxConnector Picture.PNG



Overview: The ActionInboxConnector provides KM Recent Notifications into the UWL Notification tab, which include document feedback, subscription items, subscription administration, and document approval notifications; in addition, checked out documents appear under Tracking , and documents for approval under Tasks. By default the Action Inbox Connector for UWL is enabled. For more information, see Action Inbox section in the KM Administration Guide.


Issues & Why: With the ActionInboxConnector errors and exceptions may appear for a wide range of different reasons. 


  1. Are you currently using KM or KMC?
  2. Have you attempted to deactivate (and then reactivate the ActionInbox Connector.)?


Common Exception Issue: ActionInboxConnector: Failure in retrieving from Action Inbox.


Solution: The main point of analysis interest here is to check the following path > System Administration -> System Configuration -> UWL -> UWL Admin



  • Important Point: Computer Monitor Service (Under KM) must be working



Then check the following: when you go to UWL administration and select the system 'ActionInbox' open the tray for 'Universal Worklist Service Configuration' what is the value set for 'Timeout Value for the Connected Systems? If it is 30 seconds you can try and increase its value to 300sec or so.



Important: Also kindly follow the SAP Note 1133821 to ensure destination service configuration to and from the UWL is setup accordingly.



Summary: With issues relating to the ActionInboxConnector you need to determine whether or you are using KM functionality. The reason for this is because with KM and KMC and their surrounding functionality examples of what these notifications are based upon vary and include Notification tabs which include document feedback, subscription items, subscription administration, and document approval notifications; in addition, checked out documents appear under Tracking, and documents for approval under Tasks. If you are not using KM and collaboration the connector (ActionInboxConnector) should be deactivated in the UWL configuration page. (It is activated by default).


The ActionInbox connector uses resources from the KMC so even if you don't use KM on the portal, this connector is co-dependent on the codefrom KMC. This is the same as the AdHocConnector with the portal.

Background: The UWL (Universal Worklist) functions through a baseline concept known as the UWL Destination Service Configuration.





Overview: You can define the connections to systems for Universal Worklist. These systems provide work items via UWL Connectors. The Universal Worklist Systems page is accessible from Portal via navigation to > System Administration > System Configuration > Universal Worklist and
> Universal Worklist Administration.


Common Issues:


  • "Cannot connect to the Provider" when you access tabs e.g. ESS/MSS
  • “Problem occurred while creating JCO client for destination: ABCXYZ”
  • “User is missing credentials for connecting to system alias: ABCXYZ”


Why: The RFC destinations have to be maintained so that the UWL can make functional calls to the backend applications. In most cases the exceptions outlined above appear as the calls to the backend fail due to a discrepancy in the configuration setup of the RFC destinations.


Solution: SAP Note: 1133821 - UWL Destination Service Configuration.


By following the documentation above we can ensure that the RFC destination is missing or is not configured properly.


After the note is implemented and the WebFlowConnector re-created the cache should be cleared and the backend re-registered.


Important: Check that after applying Note 1133821 the destination names and the UWL connector names exactly match, even considering


If your portal system alias (=UWL connector name) is for example XYZCLNT100, then the RFC destination name should be exactly XYZCLNT100$WebFlowConnector. Please correct the RFC destination accordingly.


After you have checked/prepared the RFC destination for the future use please delete that connector in the UWL config UI (Portal->System
Administration->System Configuration->Universal Worklist) with which you would like to use this RFC destination.


After that


  • Restart the portal cluster
  • Recreate and reregister connector


Now retest.  Are you still seeing the issue?



Summary: These steps are important for the connector to work properly.  So in the portal, there needs to be a deletion on the connector, a restart of the portal cluster, then a recreate and re-register so that the new connector interacts with the RFC destination.

More and more customers are adopting the new Fiori Launchpad (FLP) design on SAP Enterprise Portal (EP) to benefit from a modern and easy to use user interface that also runs nicely on mobile devices. Of course, users also want to access their documents and unstructured content in their Portal in a UI that fits into the new FLP design seamlessly both from desktop and mobile.


To achieve this, SAP Mobile Documents is the natural choice. Besides the cool UI, it also allows you to easily integrate content from other sources like Microsoft Sharepoint or the SAP Business Suite. In this blog, I would like to look into the integration from a technical point of view. For more details on business benefits and how you can best leverage SAP Mobile Documents with SAP Enterprise Portal, I recommend reading Annette Fuchs' blog on SAP Mobile Documents and SAP Fiori launchpad on EP integration.



1. Installation of SAP Mobile Documents

For your on-premise server installation you need an SAP NetWeaver AS Java as a platform to install the SAP Mobile Documents Server. So you might decide to install it on your Portal server. There are already quite some blogs out there on SCN describing the installation in detail.

Check out Martina Kirschenmann's SAP Mobile Documents - Implementation and Integration for a comprehensive overview of all necessary and optional configuration steps and links to more detailed blogs.




2. Configuration of SAP Mobile Documents


In Mobile Documents, you usually have 3 areas:

  • My Documents where the user can store personal documents and sync them to all connected clients,
  • Shared documents for securely sharing documents with internal and external users according to various security settings
  • Corporate Repositories where managed content can be provided to the users.


To use My Documents and Shared Documents, you first have to create repositories called mydocuments and shareddocuments in the Knowledge Management of your SAP Enteprise Portal.


Further repositories from SAP Knowledge Management or other sources can be accessed in the Corporate section- see my blog Providing corporate content to end users with SAP Fiori Launchpad on Enterprise Portal for more detail and check out:

- SAP Mobile Documents Setup Guide for all details on configuration

- Setup connection for SAP Mobile Documents to Microsoft Sharepoint for Microsoft Sharepoint integration

- SAP Mobile Documents - Connecting a File Share as Corporate Repository.



3. Setting up SAP Fiori launchpad in the Enterprise Portal

Some time ago, I already published a blog on Building your Mobile Portal using Fiori Launchpad on EP. It touches all steps that are necessary for setting up FLP on EP, but since that one was more addressed to the experienced portal admin, I will now go into more details specifically for Mobile Documents and add some more screenshots.



a. Create a new URL Alias and assign the Fiori desktop to it

In this step, you create a new URL suffix that you can use to call the portal in FLP design directly. Of course, you could also configure your Portal to run with FLP, when calling the standard URL, and use a specific URL alias to access the Ajax Framework page.



In the Portal, navigate to System Administration > System Configuration > Portal Display > URL Alias Manager. Click New to create a new URL Alias with a meaningful name starting with portal/ like portal/fiori or portal/flp.


To assign the URL alias to the Fiori desktop, navigate to System Administration > System Configuration > Portal Display > Desktops & Display Rules.

On this page, navigate to Portal Content > Portal Administrators > Super Administrators and open the Master Rule Collection. Click Add IF Expression.

In the IF part of the new expression, select URL Alias from the dropdown and enter your newly created URL alias into the text field right to it. Click Apply.

Now click the THEN part of the expression. In the Portal Content tree, open Portal Content > Portal Users > Standard Portal Users > Fiori Framework Content. Right click Fiori Desktop and select Add Portal Desktop to Expression. Click Submit again. With Move Down, you can bring your new expression to the right place in the Master Rule.


In most cases, you will change the Fiori Launchpad theme to better reflect your corporate identity, so you would rather use an adapted copy of the Fiori desktop.



b. Defining categories for the Tile Catalog


You can use categories to allow end users to identify relevant content more easily. The categories that are needed in your company, can be configured as properties of the Fiori Launchpad Categories iView. If you do not define categories, all tiles will appear under one category called General.


In the Portal, navigate to Content Administration > Portal Content Management.
Open folder Portal Content > Portal Users > Standard Portal Users > iViews > Fiori Launchpad.
Right click Fiori Framework Categories to open the Properties. Click All to display all properties.
When you scroll down a bit, you can see Category 01 ID, Order, Title to Category 20 ID, Order, Title. Here you can define up to 20 categories for the tiles in your launchpad.



c. Create SAP Mobile Documents iViews


For each tile in your SAP Fiori launchpad that should open Mobile Documents, you need to create a URL iView.


Go to Content Administration and choose create iView from Template. Select the URL iView template. After iView creation, edit the following properties:



  • On the URL iView tab, enter the URL to start Mobile Documents.You can either display the complete Mobile Documents web client or a direct link to a specific folder.

    • Complete web client: Enter URL /mcm/browser. If SAP Mobile Documents runs on the Portal server, it is not necessary to enter a system. Otherwise, create a system for Mobile Documents in System Administration > System Landscape and enter the alias of this system on the URL iView tab.



    • Direct link: Enter URL /mcm/browser/v1/open and if necessary, a system. To find out the object ID of the folder to display, open the Mobile Documents web client and navigate to the folder you want to display in the iView.

Select the folder by clicking the checkbox in front it, then click the i to open the folder information. In the web link and mobile link on the information page, you can find the object ID and the repository ID.




In your URL iView settings, enter two URL parameters:

      • URL parameter rep with value the repository ID as you find it after rep= in the folder's web link, type String
      • URL parameter obj with value the object ID as you find it after obj= in the folder's web link, type String.






  • Now you have to set some more iView properties that are not Mobile Documents specific, but are important for the iView to show up in Fiori launchpad. Go to tab Properties, click All and Modify Properties. Set the following properties:
    • Object ID of Device group: Enter the ID of all device groups on which the iView should show up. You can find these IDs in System Administration > System Configuration > Portal Display > Device Group Manager. You can find the IDs in the rightmost column. Enter the IDs for all relevant device groups separated by semicolons, e.g. com.sap.portal.dg.desktop;com.sap.portal.dg.smartphone;com.sap.portal.dg.tablet.
    • Mobile App Categories: Enter a list of all categories where the iView should show up in the Tile Catalog according to the categories that you created in part 3b.
    • Default App in Home Page (as of Portal 7.4 SPS 10 or Portal 7.31 SPS 15. In earlier releases, this property is called Permanent in Launcher): If this is set to true, the selected iView is displayed by default on the home page. Otherwise, the end user would first have to go to the Tile Catalog and assign the tile to one of his groups.
    • SAP UI5 icon: Define the icon that is displayed on the tile, e.g. sap-icon://documents or sap-icon://document-text. If you set the Image Type to Image instead of Icon, you can also display an image stored in the Web Resource Repository using the property Icon URI.


If you would like to read more details about iView properties, please read Shani Limor's blog on SAP Fiori Launchpad on Portal - Sample Content for Administrators.



d. Assigning the iViews to roles



Create a new freestyle role or edit an existing one. Add the new Mobile Documents iViews to the role and make sure that there is an entry point defined for the iView or one ore more levels higher. Make sure the the iView is set to Visible.

Assign the role to a user or a group. Now all iViews in the role are listed in the Tile catalog for the user. The tiles that were defined as Default App in Home Page / Permanent in Launcher are accessible from the user's home page automatically.



Now the system is set up. Access Fiori launchpad in the Portal with the following URL http://<portalserver>:<portalport>/irj/<your URL alias>. Click the menu icon to access groups and the tile catalog and you can start to play with Mobile Documents in your Portal.

FLP final.png

Definition: The Universal Worklist (UWL) gives users unified and centralized way to access their work and the relevant information in the portal. It collects tasks and notifications from multiple provider systems – SAPBusiness Workflow, Collaboration Task, Alert Framework and Knowledge Management Recent Notifications - in one list for one-stop access.




Performance:  There are many configuration options that affect the performance.





UWL Sizing guide


In the process of creation, the sizing guide determines the hardware requirements.


  • Number of users
  • Total number of items per user
  • Number of connectors


Performance Degradation Factors


  • Sometimes specific connectors (BPMUWL) cannot fulfill the get items request. There is 30 seconds timeout defined for the connectors (configurable)
  • Communication channel between UWL and providers (Network, JCo)


Performance Configuration Recommendations


  • Use Delta Pull mechanism (where applicable)


  • Delta Pull period should be no longer than the time that task is required to be updated in the UWL for all new items from the backend. If the items are created more frequently, the period should be shortened and the opposite. Better results for performance will be with higher values but the items may not be always up to date.The minimal value is 60 seconds and it is default value as well.


  • Cache validity should have a longer period value than the delta pull.If cache validity has expired then a call to backend will be performed regardless of the fact that delta pull has occurred.


  • Page refresh rate, that is accessible from data properties of Personalize Tasks, specifies how often UI will be refreshed with data from the cache. Note that the cache validity period takes precedence.Then the Page refresh rate should have less period value than cache validity. Last comes the Delta Pull period. In short: Cache Validity > Page refresh rate > Delta Pull period.


  • The number of users per channel depends on the number of the tasks and the number of theusers. Default value is 40 users per channel. Increasing this number will decrease the number of the invocation to the backend. Note that the higher the number of users per channel, the higher volume of data per invocation will be transferred.


  • The IView property “Wait duration for UI refresh while waiting for update” can be increased if UI is not responsive. If the value of this property is set to 0 then user interface will be blocked waiting for the call to the backend to complete.  In this case after call is completed and  cache is updated, items are read from cache displayed in the UI. Assigning value to the property allows  the UI to read the last data found in cache and display it immediately, this  way unblocking UI while the call to backend is performed in background. After the time defined in the property passes, presumably cache already updated with the latest items in background, UI is updated again from cache showing the latest items.


  • The number of the custom attributes should be decreased.For every additional attribute an additional call to backend is performed. The setting “Retrieve custom attribute via primary pull” should be switched off.


Commonly Reported Issues


  • CPU spikes – due to high volume of data. Check performance recommendations
  • Long DB processing time – Oracle DB software is not up to date Refresh is excessively used. The connector is not able to fulfill the request
  • Cache is not cleared in applying new XML configuration
  • Configuration issues – the documentation  has to be read carefully
  • RFC destination is not configured according to the note 1133821
  • Task definition and Task visualization change at backend take effects in UWL only after re-registering WebFlow     connector
  • Delta pull for WebFlow connector is working only if the ABAP reports at backend are configured (RSWNUWLSEL or SWN_SELSEN). 3rd party reporting is not supported.
  • Out of memory exception in updating items from the WebFlow – JCo payload (8-10 kB per item) Real Time refresh must be activated in the backend
  • Deployment issues due to incompatible changes in the DB schema (bug fixing)
  • Misunderstanding of the substitution support in UWL On upgrade: SOM connector does not display the items. Wrong connector is displayed to the item.
  • Users deleted at customer systems.


Key UWL Documentation


  • KBA 1577547 UWL Performance Tips and Considerations



In the first part of our „Portal on smartwatch“ blog series my colleague Michael demonstrated the BTEXX mobilePortal prototype for the Pebble smartwatch. Today as the Apple Watch is released in many countries I want to share some information on our Apple Watch prototype with you.



WatchKit Apps


At first I was sceptical about business apps on smartwatches. Who wants to use this tiny screen for more than fitness tracking? After spending a lot of time in the Apple Watch simulator I changed my mind. Don’t think of smartwatches as a replacement for your current tools but as an addition! Your users should be able to choose the right tool for the right time!


With our first WatchKit App "My Tasks" you don't have to take out your phone or even your notebook to approve yet another time correction. Browse through your UWL inbox and open your tasks to access detailed information and approve (or reject ) the tasks directly on our wrist!







Push Notifications on the Apple Watch are pretty similar to the ones you know from your iPhone. You receive a short text and some custom actions. Here's an example of an UWL notification from our prototype:




You get some basic information on the updated UWL task and the available actions. You can approve the request directly on your watch without using your iPhone. Of course sometimes you can’t decide without further information. In this case just open the task on your iPhone with the BTEXX mobilePortal or in the iOS Notification Center.









For our prototype we completely reused our BTEXX mobilePortal 2.0 backend. The app itself is implemented in Swift and uses the Apple WatchKit Library.


WatchKit Apps are basically just extensions to native iPhone apps. Right now the code of third party apps runs on the iPhone while the Apple Watch acts as an external touchscreen. Later this year Apple will provide the possibility to develop fully native Apple Watch Apps. This should bring some improvements regarding features and performance.


At the moment wearables are still a research field for us - we’re trying to figure out what can be done and more importantly what should be done with smartwatches in the business context.


I’m looking forward to your feedback and questions!


Best regards







Based on the connection between user perspective, SAP technology and process know-how, BTEXX implements user-friendly solutions that make companies more efficient and users happy.

In the upcoming ASUG event in Orlando several SAP Portal oriented sessions will be offered, which you can find in the session catalog of the agenda builder of ASUG Annual Conference. In the agenda builder, you find the sessions by choosing "Browse ASUG tracks", then you scroll down and find the track "Portals".


These are the main topic areas:

  • SAP Portal portfolio and roadmap (session PO1310) : learn about the transformation of the SAP Portal portfolio into cloud (mainly for external facing scenarios) and into the SAP Fiori UX paradigm.
  • Fiori Launchpad (sessions PO1343, PO799, PO836) : SAP Fiori launchpad running on SAP Enterprise Portal is a key milestone in aligning the SAP UI Clients (Fiori launchpad, Portal, NWBC) with the Fiori UX design. In this session you learn how to renew your SAP Enterprise Portal with the new multi-channel, personalized framework page following the Fiori design. You will also get the latest news about our planned release for NW 7.4 SPS11/7.31 SPS16 providing new cool features like for example remote catalogs, which allow the integration of catalogs and groups from ABAP backend systems. Or you have locked areas on the homepage which you can use for example for company information, which should not be changed by the end user. Join our Fiori launchpad sessions to get the latest updates on existing and planned features - or contact one of our experts directly. Learn also about Fiori launchpad deployment best practices (ABAP, SAP Portal and HANA Cloud Platform) and common architectures.
  • Cloud Portal (sessions PO801, PO762): Learn how to create business driven sites using SAP HANA Cloud Portal and how to extend business solution using HANA Cloud Portal and Fiori Launchpad on HANA Cloud Platform.
  • Customer Sessions (PO460, PO80, PO1126): Listen to our customers Johnson and Johnson, Roche and the University of Mississippi and learn about their Portal projects.
  • Mobile Documents (session PO358): Learn how to renew and enhance the SAP Portal experience using SAP Mobile Documents


Check out our SAPPHIRE/ASUG page where you can find the latest information on our sessions and our Portal experts, you can meet in Orlando.


Sessions in Details

TopicSession Title and NumberContent
Portal RoadmapPO1310 SAP Portal Roadmap - Innovations for Cloud and On Premise (Lecture)SAP Portal is with over 10,000 productive customers strong and growing. With the introduction of new options in the portfolio such as SAP HANA Cloud Portal or the inclusion of Fiori Launchpad, the options for customers are growing. In this session we will update on the Portal strategy and roadmap, introduce customer testimonials and answer FAQ.
Fiori LaunchpadPO1343 Renewing your SAP Enterprise Portal implementation with SAP Fiori launchpad (Lecture)Join this session to learn how to renew your SAP Enterprise Portal with the new multi-channel, personalized framework page following the Fiori design, new multi-channel SAP Fiori apps running in the portal, and new multi-channel Fiori apps developed with SAP Web IDE and consumed via the SAP Portal.
PO799 SAP Fiori launchpad deployment options recommendations for SAP Portal customers (Lecture)SAP Fiori launchpad provides end users a role-based personalized aggregation point for SAP business applications and analytics. Join this session to learn about Fiori launchpad deployment best practices (ABAP, SAP Portal and HANA Cloud Platform) and common architectures. This session will focus on the use cases for existing SAP Portal customers.
PO836 Exploring ways to make Fiori adoption easier and faster (Panel Discussion)Join this session to hear a panel of experts discussion various strategies and best practices to expedite SAP Fiori adoption - Whether by use exploration tools, custom development or by adopting cloud based components to your Fiori implementation.
Cloud PortalPO801 SAP HANA Cloud Portal - Overview, Innovations, Showcases and Future Directions (Lecture)Join this session to learn how to easily create business driven sites using SAP HANA Cloud Portal. The session highlights the solution market approach, benefits and capabilities as well as key implementation scenarios.
PO762 Extending your business scenarios with SAP HANA Cloud Portal - Scenarios, Use Cases, Best Practices (Lecture)Get an overview on how to extend business solutions using HANA Cloud Portal and Fiori Launchpad on HANA Cloud Platform.
Customer SessionsPO460 Learn How Johnson and Johnson Redesigned its Global SAP Enterprise Portal (Lecture)Join this session to learn how Johnson and Johnson leveraged the SAP Enterprise Portal to create an enjoyable, modern, personalized, and multi-channel aggregation point based on the SAP portal platform.
PO80 Co-Innovation Roche/SAP: Cross Browsers and Device Support, One Portal (Lecture)Roche has created a unique point of access for any SAP application: “One Portal”. After a migration phase the focus was set on usability. The concept is called “Simply One” and it has been implemented with a completely new user experience based on HTML5 with responsive design. This session is focused on sharing the Simply One experience and outcome
PO1126: Success with a responsive, accessible and intuitive to use SAP Enterprise Portal Implementation (Lecture)The University of Mississippi re-designed its SAP Enterprise Portal and implemented it to be very accessible to visually challenged users, responsive to work across mobile devices and desktop computers and intuitive and easy to use. Join this session to learn from experiences of this cost effective successful implementation.
Mobile DocumentsPO358 Enhance Your SAP Portal Experience Using SAP Mobile Documents (Lecture)Join this session to learn how to renew and enhance the SAP Portal experience using SAP Mobile Documents. See how documents from SAP Portal KM, Microsoft Sharepoint, or SAP Business Suite can easily be consumed across different devices – in the cloud or on premise.


Contact our Experts

Feel free to reach out to our experts for on-site discussions on our product portfolio and the latest innovations. You can also contact them before the event for organizing an on-site meeting:


Aviad Rivlin: aviad.rivlin@sap.com Twitter:@aviadrivlin

Inbal Sabag: inbal.sabag@sap.com Twitter: @inbalsab

Guy Bavly: guy.bavly@sap.com Twitter: @GuyBavly

Lev Segev: lev.segev@sap.com Twitter: @segevle

Yariv Zur: yariv.zur@sap.com Twitter: @vlvl


Let's get Social

During and before SAPPHIRE NOW and ASUG you can also keep yourself up-to-date by checking SCN and our Social Media Channels.


SCN Spaces

Watch the following SAP Community Network Spaces:
SCN Space for SAP Portal

SCN Space for Cloud Portal



Follow the official SAP Portal twitter account @Portal_SAP

Portal Hashtags on Twitter:
#SAPPortal – SAP NetWeaver Portal hashtag
#hanacloudportal - Cloud Portal hashtag

#SAPFiori launchpad


LinkedIn and Facebook

Follow the event also on LinkedIn and Facebook.



More information on our SAPPHIRE NOW and ASUG plans will follow in the upcoming weeks, bookmark this blog to be up-to-date.


URL iViews


Mostly all projects in SAP Portal use iViews that retrieve content directly from a Web page.


A URL iView is a collection of Meta attributes, one of which is the URL to the information source. A built-in browser available in the URL iView Wizard and Editor enables you to navigate easily within a Web site in order to retrieve the URL of the source Web page to display in the iView.


There are some scenarios where URL iView’s are directly referring intranet link like a help link to SDN.( www.sdn.sap.com). For these the iView properties do not change on migration to different portal systems in landscape.


However there are scenarios where SAP Portal interacts with many different SAP systems like


  • SAP Business Warehouse
  • SAP Solman,
  • SAP Governance Risk and Compliance solution ( GRC)
  • SAP ECC and so on.

Users may use BW reports or launch other SAP systems using the links from SAP Portal.


For E.g. , URLs for the iView’s may start with


Fin and HR internet

https://<SAP ECC server name>/sap/bc/gui/sap/its/webgui/!

SAP BW Reports

https://<SAB BW server name>/sap/bw/BEx

GRC Reports

https://SAP GRC Server name>/sap/bw/BEx


https://<SAP Solman Server name>/sap/bc/webdynpro/sap/



In above case the server names will change as per landscape and environments. They will be different for Development, Test and Production.


If the links are copied statically then there has to be manual action during migration of these iViews to change the URL for them.


Technical Solution:


To avoid the manual action and as a result any issue with that during migrations we can define URL aliases in Portal for all such backend systems.

Basis need to create http systems for all such backends and these systems should have proper parameters

1) Hostname – URL of the backend system

2) Port number – if any

3) Protocol- HTTPS


Once the httpsystems are configured the URL iViews need to be modified to get the URL from this system.



1.       System Creation

Basis needs to create Http Systems:


1) Go to System Administration- System Landscape and create systems with below parameters

A. Hostname – URL of the backend system

B. Port number – if any

C. Protocol- HTTPS




Once all backend systems are created you can check the httpsystems under System type.





2.  iViews Modification

Once the systems are tested for connection, we need to modify the iView properties :

    1. System- Select the required HTTP system as per backend
    2. Check the box “ Use system in URL”
    3. URL has static content of URL which does not change with system landscape migrations





The URL will be called with the link as https://<SAB BW server name>/sap/bw/BEx at runtime.


3.   Migration :

During migration of iViews, Basis needs to create the systems in respective environments. There will be no manual action for iViews and they will point to corresponding backends as per landscape automatically using URL alias.




Thus we can have URL aliases for URL iViews to ensure no manual action for changing the iView’s during migrations and hence maintenance of iViews becomes easy.

Also in case the server names changes in future we just need to update the System alias for httpSystem and need not change all iViews using that server.


Filter Blog

By author:
By date:
By tag: