1 5 6 7 8 9 32 Previous Next

SAP Enterprise Portal

479 Posts

We invite you to participate in the "Topic of the Week" campaign for SAP Fiori launchpad. A topic of the week is a selected topic about which you will get up-to-date information on SCN and our social media channels. You can listen to us and also discuss with us on SCN, Twitter, Facebook and LinkedIn on special days. Moreover we will also inform you about our focus topics for this year's SAP TechEd && d-code and make you aware what you can expect when you attend the event in Las Vegas or Berlin.

From September 17-18 we offer you "SAP Fiori Launchpad" as the topic of the week.

What are the highlights of SAP Fiori launchpad as the topic of the week and what can you expect?

ASUG Webinar on September 17

Participate in our ASUG webinar on SAP Fiori launchpad on September 17, and learn also what we plan for SAP TechEd && d-code this year.


Product Information

We will use our Social Media channels to give you up-to-date information on SAP Fiori launchpad in general and how it runs in SAP Enterprise Portal

You can access the following channels to follow the information flow and join the conversation:

  • Twitter: Get all kinds of information under hashtag #SAPFiori. You can read tweets also without having an own Twitter account.
  • Facebook: Get images, see videos, get some product insight and some technical overview information etc. You can read the content of our public Facebook page also without having an own Facebook account.
  • LinkedIn: Get more technical information.
  • and visit our SAP Enterprise Portal community on SCN where we also cover SAP Fiori launchpad

We also want your feedback: so we encourage you for interaction, discussion, commentary, questions, feedback.

  • Send your questions on Twitter to @Portal_SAP https://twitter.com/PORTAL_SAP and use hashtag #SAPFiori for your tweets
  • or simply add your feedback and questions as comments to this blog.


We are looking forward to meeting you this week at the webinar or on our social media channels.

Applying corporate design guidelines to your SAP Enterprise Portal is about to become much easier.

Are you familiar with the UI Theme Designer tool in SAP Enterprise Portal? If not, I’d like to expose you to an improved theming experience (compared to the Theme Editor you’re probably familiar with).


The UI Theme Designer is a browser-based tool that enables easy theme building by modifying one of the theme templates provided by SAP.



Why Use the UI Theme Designer?


By using the UI Theme Designer in the Portal, you can benefit from the following:

  • Increased theming efficiency (reduced theming effort for customizing portal and integrated applications).
  • Ease of use – simple and intuitive.
  • Reduced theming effort.

We achieve these benefits providing the following capabilities:

  • Graphical web-based WYSIWYG editor for controls as well as applications.
  • Different levels of theming:
    • Quick theming - Used for general theme settings affecting various SAP UI technologies.
    • Expert theming – Used for SAP UI technology-specific theme settings.
    • CSS - Manual theming based on LESS style sheet notations.
  • Built-in preview pages: Application previous and control overview pages.
  • Enabled for SAPUI5 and Unified Rendering.




The UI Theme Designer is available in SAP NetWeaver 7.3 SP10, 7.31 SP9 or 7.4 SP4 onwards.



Migrating Themes for Use with The UI Theme Designer

You can import portal themes for use with the UI Theme Designer. Themes customized using the Theme Editor must be exported before the UI Theme Designer is activated. The exported themes should be imported (migrated) after activating UI Theme Designer. The following video contains all you need to know about Theme Migration in less than a minute.






Activation of UI Theme Designer

Configuration for activating the UI Theme Designer is also fast and easy. The configuration is illustrated in the following video in less than a minute.




Examples of Theming Capabilities


After doing the previous steps (Theme Migration (if required) and UI Theme Designer activation), you can now enjoy creating and editing themes in an easy, simple, and intuitive way. Examples of different levels of theming: Quick, Expert and CSS are provided in the following video.




Ongoing Improvements


Note that UI Theme Designer is in continuous development and therefore additional improvements are also reflected when working with the tool in the Portal. For example, theming based on Fiori Framework Page is supported, starting from SAP NetWeaver 7.31 SP12. Another example is the support of Right-To-Left (RTL), starting from SAP NetWeaver 7.31 SP13.
So you can expect that your experience will continue to improve in the future.



Notes and Known Limitations


  • Note 1890375 - Known Issues of UI Theme Designer for SAP NetWeaver Portal.
  • Note 1927550 - Update UI Theme Designer to version 1.1.4 in the portal.
  • Note 1895989 - UI5 iView stylesheet rendering issues.
  • Note 1959708 - Supporting integration of UI Theme designer and UI5 application in the portal.



Further Information




Enjoy - We'd appreciate your feedback



As a new starter to SAP it is important for me to get comfortable with SAP products and how they can add value you to the customer. I have discovered that there is a strong emphasis on making the world simpler at SAP and this video gives a good understanding of how we at SAP can create a simpler world for our customers.


The video opens with an intro to Sara, a sales manager, who has been working with SAP applications for years. Now she needs mobile applications in order to do her job, now she has an issue where she is using lots of different applications over the different devices she uses to do her job. There is no similarity between the apps.


Peter, the CIO of the company, has a challenging role where he is supporting many different devices, platforms and applications. He is now struggling to control the variety of applications, while at the same time the users are demanding more support and he needs more expertise to maintain the ever growing devices and applications.


SAP's solutions to Sara and Peter's problems are covered by Responsive Design.


Responsive Design aims to let the user of the applications have similar experiences across different devices, desktop, mobile and tablet, with the views for each device adapted for the device in use. There is a high emphasis on ensuring the content is easy to read and navigate.


The video goes on to show how SAP Portal is taking Responsive Design to the next level. On desktop there is full user access, where on tablet there is access to selected information and on tablet only crucial information and options are available. The content is designed to look great and be in a form relevant to the business, user role and user preferences.


Users will have a

    • Coherent experience
    • Optimized for the user's needs
    • Single point to manage the content
    • Ability to preview on a wide range of devices
    • Control for the user experience

Based on the latest technologies

    • HTML5
    • OpenSocial
    • OData protocol

Available on

    • HANA
    • On Cloud
    • On Premise


I found this video good at explain how SAP can make user experiences simpler for users.


What Is Responsive design ?? - YouTube


Check out Announcement of SAP Portal and HANA Cloud Portal Gamification Movie Challenge



The purpose of this blog post is to explain and demonstrate how to integrate an SAP Fiori application into SAP Enterprise Portal.

This blog post is for portal developers and administrators who would like to learn about the tasks required to integrate SAP Fiori applications in Portal. In only a few steps you can easily add a SAP Fiori application to Portal.

This capability is applicable only for a subset of Fiori transactional applications, which are self-contained in nature and do not require contextual services. These are typically e.g. Employee or Manager Self Services. See details in SAP Note #2103156


What’s the Problem?


Actually there are a few problems we need to address:

  • Fiori (Wave II and above) applications are called via a URL location fragment. Therefore, a simple form submission is not sufficient here.
  • Fiori applications are protected against click-jacking attacks; this prevents them from being rendered in an iFrame.
  • Extra parameters need to be forwarded to the application to ensure it runs in standalone mode.

Standard use of the Application Integrator (UI5 iView) is not possible – precisely because of the problems listed above.


The Solution


We have created a new iView template in the portal: SAP Fiori iView. By using this iView, you will be able to call a specific Fiori application running on an ABAP back-end system and run it within the portal framework.




  • Your Enterprise Portal version is:
    • 7.3 EHP 1 SP 13 and above
    • 7.4 SP 8 and above
  • Your back-end server has SAP Fiori Launchpad SP 8 or above
  • You have made sure that both the portal server and the ABAP server can be reached via the same URL (including the server name). This can be achieved by using a SAP Web Dispatcher.


How to configure a web dispatcher (example)

We need to access both servers via the same URL. Therefore, we set up a web dispatcher.


So, we configure it such that:


For the client, it seems as if, both the portal and the Fiori application are on the same server.


So, How to Integrate a Fiori Application into Portal


In this example:


The Fiori app can be accessed directly from: https://abab.sap.com:44336/sap/bc/ui5_ui5/ui2/ushell/shells/abap/FioriLaunchpad.html?sap-client=123#Shell-runStandaloneApp?sap-ushell-SAPUI5.Component=cus.crm.opportunity&sap-ushell-url=/sap/bc/ui5_ui5/sap/crm_opprtnty


Since the web dispatcher is already set up it also can be accessed from: http://dispatcher.sap.com/sap/bc/ui5_ui5/ui2/ushell/





  1. Create a system object and give it an alias, such as 'WEBSIDP'. This system will actually points to on the same URL we are using to access the portal - the web dispatcher.
  2. Enter the following mandatory settings for this system object:
    1. SAP Client: 123
    2. ICM Protocol: http
    3. Web AS Host Name: dispatcher.sap.com
    4. Set the system HTTP Security Session to be on. See SAP KBA #1717945 for details.
    5. You can set other properties too according to your needs.
  3. Create a Fiori iView.
    1. In Content Administration, create a new iView from template and select SAP Fiori iView.
    2. Go through the wizard, choose a name for your iView, and then click Next.
    3. In the next screen, fill in the details as follows (according to the example):
      • System: WEBSIDP (this is the system alias we defined before)
      • Relative Path for SAP Fiori Application: sap/bc/ui5_ui5/ui2/ushell/shells/abap/FioriLaunchpad.html
      • Parameters to Pass on the Location String in the URL: Shell-runStandaloneApp?sap-ushell-SAPUI5.Component=cus.crm.opportunity&sap-ushell-url=/sap/bc/ui5_ui5/sap/crm_opprtnty
        • If you leave this field blank you will simply get the SAP Fiori Launchpad (FLP).
      • SAP Fiori Application Header: You can choose one of the following:
        • No Header - you will not see the FLP header, personalization will be off (disclaimer: supported as of ABAP Add-on SP10)
        • Minimal Header - You will have the FLP header with functions that match embedded mode, personalization will be enabled (supported as of ABAP add-on SP9)
    4. Click Next, then Finish.
    5. Once this is done you can preview the iView. All the properties that you entered with the wizard are still available via the iView property editor under the category 'Content - Fiori'
    6. Unless you have a custom theme maintained in the portal that is suitable for an SAPUI5 application, set the Hand Over Portal Style Sheet property on the iView to false. The Fiori application will be rendered with the default theme of the application, as it is on the back-end system.


That's it. You're done. All you need to do now is add the iView to a Role and assign it to your end users.




  • See SAP Note #2017946 - SAP Fiori application integration with NetWeaver Portal.
  • The official SAP documentations are here.
  • SAP recommends accessing both Portal and ABAP BE via the same URL. If you wish to do otherwise you will have to modify your FioriLaunchpda.html on the BE server. Please refer to SAP Note #2057847 for detailed information.
  • Creating Trust Between Portal and Back-End Systems - see more info here.
  • It is recommended to run Fiori iView in the portal content area only in HTML5 (Standards) supported framework page. If your end-users framework page is not supporting standards document mode rendering, and your end-users are using Internet Explorer, set the Fiori iView to launch in a new headerless portal window that support Standards mode. See SAP note #1737445 for more details.



In some situation you may want to change the title of the portal page. OR you may want to change the link, meta tags, etc..

One way to do is to identify the correct place where you have to change this, and make it work. Say for example, changing the title of SAP EP, will change title in all portal pages. If you don't want to change system wide, and only you want to change it in particular page, you can follow this example.


In my requirement, I had to change my Logo, text's in portal logon page. For that i developed/deployed the custom logon on page from the standard war files.


And used these commands to make it work.


Added these (below mentioned commands) java-script commands in <script></script> section of the logon.jsp / logonmobile.jsp files.

In this case i was not able to locate the <head></head> tag in my page, because it was getting derived from EP framework level.


To change Title of the logon page :


document.title = "My title";


And to Add link element in head section of the html page i used this command.


var l1 = document.createElement("link");

l1.rel = "icon";

l1.sizes = "196x196";

l1.href = "<%=webpath%>layout/android-touch-icon-Mobility-196x196.png";



To Add Meta tag

var m1 = document.createElement("meta");

m1.name = "mobile-web-app-capable";

m1.content = "yes";



To know the details about why you have to add such tag's, you can find it in this links:


For Apple - Mobile WebApp :




For Andriod




Similar way, you can also change the favicon


Refer this page for details about it : stackoverflow.com/questions/260857/changing-website-favicon-dynamically


Other useful links :

5 Tips for Turning Your Website Into an iOS Web... – Chief Creative Mechanic


In this case i was not able to locate the <head></head> tag in my page, because it was getting derived from EP framework level. So i had to use the above mentioned method of adding, link, meta tags to the <head> section of the page.


In some other case, (Say in Fiori home page, launchpad page,) you want to add such details, you can directly add them as per the developer.apple or developer.chrome links given above.


Hope this helps to create custom bookmark of SAP portal logon in Android, iOS and other mobile apps, and web-browser bookmarks with custom pictures.

Thanks for reading.

The newer versions of IE pose many rendering issues/challenges which affect EP rendering. There are so many complications and solutions around this subject that it’s really hard to deal with.


So I decided to learn this subject and make some order in all this mess – so that I’ll know how to handle the variety of issues that come to our door here at support. In this blog I will share some of these issues with you.

I used kind of childish graphics – but I think that they demonstrate my points nicely.

So here’s an historical review of the evolution of the standards/quirks issues:


     1.  In the beginning –old IE versions


The older versions of IE (such as IE6, IE7) ran only in quirks mode. The portal rendered everything in quirks mode with no issues. Applications running in the portal were not strict about standard syntax and they lived happily within IE – which wasn’t strict about syntax either.



Then IE with standards mode arrived and evolved and the portal had to deal with rendering issues…



     2.  IE8 presents standards mode




IE8 and above presented standards mode rendering. For IE8 and IE9 the default mode is quirks, but if the administrator configured all the browsers in an organization to run in standards mode, the portal wouldn’t be rendered well.





Enforce IE to run the portal in quirks mode by changing the document mode.

How? We added an iView to all framework pages. The iView adds parameter to the header and tells IE to render in quirks mode.

This iView has to be added to every non-standard framework page for the portal to be rendered correctly.


More Details

  1. Note: 1458799 - Limited supportability for IE8 and above in the Portal
  2. Note: 1787647 - Browser Document Mode iView hides the portal content area - a fix to a regression from note 1458799
  3. Blog: Browser Document Mode – How to set the IE Compatibility View from server side.


And peace is restored…


     3. SAP presents UI5 applications





In recent years SAP introduced a new UI technology for SAP applications called SAP UI5. UI5 applications are written in standards mode and require standards mode rendering, while the portal runs only in quirks mode. Standards and quirks can’t run together on the same page.





Run standards-mode applications in a separate window which opens in standards mode.

How? Set the “Launch in New Window” property of the iView to “Display in separate headerless portal window (standards mode)”. This navigation mode, as its’ name implies, tells the iView to open in a new window and sets the HTML header to standards.



More Details

  1. Note: 1737445 - Internet Explorer standards mode rendering for EP
  2. SCN: Launching portal applications in Internet Explorer standards mode rendering – This blog presents a detailed “how-to” for configuring the new navigation mode.



And the smile is back...


     4. IE10 and IE11 presents QME mode – quirks mode is not really quirks anymore




From IE10 the values that were previously used for rendering pages in quirks mode (Emulate IE7/Emulate IE8) are now rendered in QME (Quirks Mode Emulation). In this QME mode there are slight differences in some values that the browser returns and the portal again is not rendered well.



Use another value (IE=5, IE=EmulateIE7 ) to enforce the “old” quirks mode.

How? Change the “Browser Mode” property value of the “Browser Document Mode” iView to IE=5


Mode Details



  1. Note: 1458799 - Limited supportability for IE8 and above in the Portal
  2. http://msdn.microsoft.com/en-us/library/ff955275(v=vs.85).aspx – The Microsoft documentation to QME mode






      5. IE11 run in standards mode by default




When a new window is opened by an application in IE11, the new window is opened in standards mode by default (before IE11, the new window was opened according to the parent window’s mode). If the application that is opened in the new window doesn’t support standards mode – it will be rendered incorrectly.




Enforce IE11 to render the newly-opened page in the correct rendering mode.

How? Check the document mode of the parent window before opening the new window, and enforce the parent’s mode on the child.


More Details



Note: 1969004 - Open navigation mode 1 (new window) rendering mode according to the parent window rendering mode


This note has a few side effects which were fixed in the following notes:

And again:



     6. IE11 presents itself as Mozilla






According to Microsoft documentation, the IE11 user agent string was changed to be compatible with modern browsers. It returns the following string: “Mozilla/5.0(Windows NT 6.3; Trident/7.0; rv:11.0) like Gecko.”

This string was not familiar to the portal, and the portal recognized IE11 as if it was Mozilla. Due to that, the X-UA-Compatible string which changes the document mode to quirks was not sent to the browser, causing rendering issues.

Another instance of this problem appears in HTMLB applications.

HTMLB APIs also check for the UserAgent of the browser, and like the Portal – the HTMLB code recognized IE11 as Mozilla, and as a result upload wrong sources to the browser, and the controls don't function as expected.



Familiarize the portal with the new user agent string as an IE11 user agent.

How? Add this new user agent string to the “user agents” dictionary of the portal.


More details

Note: 1972506 - Cannot access portal with Internet Explorer 11

Fix for HTMLB: note 2000759 - HTMLB Support for IE11


And we're smiling again...







     7. Standards mode Web Dynpro applications





Some WD ABAP/JAVA applications started running standards by default (for example – HCM). Because the Portal enforces quirks mode, these applications have rendering issues when they run in the portal. The result is bad rendering of the applications.




Enforce the application to run in quirks mode.



How? Add a parameter (SAP IE parameter) to the application URL which tells the application in which mode it should run. For quirks it would be ie=EmulateIE8” and for standards ie=Edge”.

This works for all ABAP applications except for SAP Transaction iViews (SAP GUI for HTML) which receive the application parameters in another format, so the sap-ie parameter is not aggregated to the URL as expected.

In newer portal SPs all of this happens automatically (see note 1814711) and the portal knows what to send to every destination.

But! Previous to the versions mentioned in the note, you had to set the SAP IE parameter manually for all applications, and for SAP Transaction iViews you had to do a special configuration according to note 1970427.


More Details

Side effect note to 1753544:

And finally:


8. iViews running in standalone mode (with no framework page)




There are scenarios that Portal AI iViews are opened in new window directly, means: some application navigate to the URL of the iView without using the navigation APIs.

Examples for this are: previewing an iView (from the content management), BI launcher – launches BI iViews directly.

Since there is no framework page – there is no direction for the browser in which document mode to be opened, so the browser opens in the default mode. In IE11 the default mode is “Edge”, and hence there are rendering issues for iView that needs “Quirks” rendering.



Add the meta-tag for document mode indication (either standard or quirks) in the head of the iView HTML

How: The correct value will be detected by a new property on the iView, which indicates whether the iView should be running and quirks mode or standard mode.


More Details

I wrote an extensive blog about this topic which explains the issue and the solution for it: Rendering issues when running portal iView with no Portal framework (standalone)

There are few notes for this issue:

  1. 2012705 - BI iView's are not render correctly when using Internet Explorer 10 and above.This note solves the issue for BI iViews only (the property “DefaultDocumentMode” is added only to BI iView template.
  2. 2098706 - iView rendered corruptly when using IE10 and above when executing it directly or from headerless window This note extends the solution for all AI iViews
  3. 2163649 - More scenarios of opening an iView directly (standalone) with IE10 and above causes rendering issues (continuation of note 2098706) This note fixes a regression from note 2098706

These are all of the issues that I’m aware of at the moment. I hope that this blog made some sense in all the confusion around the portal and IE.

I want to end this blog with some good news.

You were probably thinking “why don’t they just adjust the main framework pages in the portal to be compliant with standards mode? This would solve many of the issues mentioned here!”

Well… we are! In the next SPs of 7.31 (SP14) and 7.40 (SP9) the Ajax Framework Page will support standards mode!

You can read the blog that my colleague Matan Mizrahi wrote about the Ajax Standards Framework page: Ajax Framework Page in IE standards mode and the note which describe the framework page is: 2001910 - AFP Standards mode support.





If you develop portal applications, you probably find yourself sometimes searching for best way to pass parameters (configuration or others) from java code(server) into Javascript (client side)  for easy to use later.


In this blog post you can find a code sample of how to pass parameters/properties from Portal Component and then easily read these in Javascript.

This works if you are using the ajax framework page or your custom framework page using the LSAPI mechanism


Java code for the portal component:


import com.sap.portal.navigation.afp.IAFPHelperService;
import com.sapportals.portal.prt.component.*;
import com.sapportals.portal.prt.resource.IResource;
import com.sapportals.portal.prt.runtime.PortalRuntime;
public class Test extends AbstractPortalComponent
  private static String COMP_NAME = "MyTestComponent";
    public void doContent(IPortalComponentRequest request, IPortalComponentResponse response)
       IPortalComponentContext componentContext = request.getComponentContext();
      IPortalComponentProfile profile = componentContext.getProfile();
      String myProfileProperty = profile.getProperty("myProperty");
    IAFPHelperService afpHelperService = (IAFPHelperService) PortalRuntime.getRuntimeResources().getService(IAFPHelperService.KEY);  
    afpHelperService.addClientSideAttribute(COMP_NAME, "myProperty", myProfileProperty);
  IResource myJS = request.getResource(IResource.SCRIPT,"scripts/myAppJS.js");
  response.include(request, myJS);

In this sample I assume the portal component has (in its PortalApp.xml) a property named "myProperty".  (see related blog on how to read/set properties)

  • First we need to retrieve the AFPHelperService (line 19)
  • Then, call the addClientSideAttribute method with your component name or any namespace you would like to use , the property and the property value. (line 20).
  • In next lines I'm just including a javascript resource that I have.

Server side code is done!


For using the AFPHelperService , you would need reference to it in PortalApp.xml. add sharing reference as you see bellow:

  <property name="PrivateSharingReference" value="com.sap.portal.navigation.afp.helperservice"/>

Reading the attributes from client side - Javascript code:


var SERVER_COMP = "MyTestComponent";
var topFrame =  EPCM.getSAPTop();
var propFromServer = topFrame.LSAPI.AFPPlugin.configuration.getClientSideAttributeValue(SERVER_COMP, "myProperty");
alert("myProperty = " + propFromServer);

  • First we need to get the top frame of the framework page where LSAPI is located. EPCM.getSAPTop().
  • Actual work is being done in line 3, retrieve the parameter saved on server side by calling the method LSAPI.AFPPlugin.configuration.getClientSideAttributeValue with the namespace and name of the property
  • Result of this would be an alert with property set from server side - "This is my value!":


Once the attributes were set in server side, you will be able to retrieve them in any javascript (in the same framework page session of course)


Last step is of course creating an iView from this portal component and test it!

01-09-2014 11-56-07.jpg



Related Links:

Ajax Framework Page

L-Shape API




In case you have a portal or JEE application that connects to an SAP backend, knowing if the connection works is important, even more important can be to know WHY it isn`t working. In the following example I was developing a KM application that uses a DMS Repository Manager from SAP connected to a SAP ABAP backend. The code worked when using /documents as the repository, but failed when using the DMSRM entry path.


The log did not help much, as it only showed that the connection failed.


The error message contains some more information, but still isn`t showing why the connection failed.


Caught exception: com.sapportals.connector.connection.ConnectionFailedException: Connection Failed: A nested exception occurred. Could not initialize physical connection. 
 at com.sapportals.connectors.SAPCFConnector.SAPConnectorException.getNewConnectionFailedLocalizedException(SAPConnectorException.java:182)
 at com.sapportals.connectors.SAPCFConnector.connection.SAPCFConnectorManagedConnectionFactory.createManagedConnection(SAPCFConnectorManagedConnectionFactory.java:155)
 at com.sap.engine.services.connector.jca.ConnectionHashSet.match(ConnectionHashSet.java:401)


This traces the error down to the SAP Connector Framework but isn`t helpful when trying to find out what happened exactly. It fails, but where and why exactly is not visible. The system in the portal landscape is configured for SSO using SAPLOGONTICKET and the SSO works perfectly when the connection test is run or the repository is called in the KM. As the error occurs in the CF part, it would be nice to see log messages from there. Obviously only the error messages are shown. But as I already know that an error is occurring, that log message is of little use.


Therefore, it would be nice to increase the log level of CF to see if maybe debug messages are logged. SAP NetWeaver Java comes with a powerful logging and tracing framework that can be accessed and configured using NWA. Changes are reflected immediately, making it even more easy to work with this tool. The question is now: where are the logs stored?


As can be seen in the log message, the package of the CF classes is com.sapportals.connectors.

There is no easy access to the source code to know which class name is used to write the logs into. Using the log configuration in NWA it is possible to search for classes. Searching for connector reveals the following classes.


As a ABAP system is called, the R3 class is a good hunch. Setting the log level to Debug.


Invoking the method of the Java class again shows now more log messages:


There is one error message showing an actual hint on what is not working. Expanding this entry shows what is happening.


Thread Hash: 128521575. Could not create JCO connection. Exception:Parameter containing a user ID is missing: neither user nor user alias nor external ID nor SSO ticket nor X.509 certificate is specified. Trying to connect with the default language instead.

The connection cannot be established because a parameter user ID is missing. While the ABAP system in the SAP Portal landscape is configured to use SSO and is working, the DMSRM repository manager has a problem in using SSO. It looks that as a faultback user ID logon is tried. Of course this is not working as no user / password mapping is configured for the system.


Changing the system in the portal landscape to make use of user id mapping solves the issue. Now the KM application is able to connect.


As the amount of log messages is drastically increased, the log level should be reset to default after solving the issue.

This blog explains how to configure and create out of the box Broadcast messages using SAP sample UI.


The Broadcast messages (BCM) is a new feature that gives portal administrators the ability to broadcast messages to end users in a defined time frame. It also gives the ability to assign a message to certain groups or roles with priority (high/normal).




You have installed SAP Enterprise Portal (EP) 7.31 SP11 or above.


Broadcast Messaging Configuration




1. Copy Sample_BroadcastMessageIview under Portal Content >> Portal Applications >> com.sap.portal.broadcast.message.framework to Portal Content >> <Any Folder> and paste it as pcd object with the same name or choose different name.

In this blog the name is Broadcast Message


2.Open Ajax Framework Page and add Broadcast Message Framework and Broadcast Message iVewes as delta link to the page. Make sure it is under Masthead Container and Visible.





3. Enable Broadcast Messaging service:

  a. Access SAP NetWeaver Administrator >> Configuration >> Infrastructure >> Application Modules >> search for <com.sap.portal.broadcast.message.service>

  b. In Web Module Details click broadcastmessageservice

  c. In Portal Service Details change BCM is Active property to true




4. Assign the user broadcast messaging role

  a. Access User Administration

  b. Add broadcast_messages_role to the users or groups.




Creating Broadcast Messaging


Access the portal >> Broadcast Messages >> Click New




2. Add Broadcast Message Name >> click Next >> You can choose the message Priority <High, Normal>  Write the Broadcast Message in the Message Box and set the time frame and click Next

3. Assign role or group to display the message for certain users or groups then click Next and then click Finish




Now you can check the message status from the Broadcast Message Overview






When the message is active it will show Next to the user name at the Masthead as shown in the below figure


Welcome to the July and August edition of the SAP Portal News Blog in 2014. This is what I have prepared for you:

  • SAP Fiori LaunchPad and SAP UX news
  • HANA Cloud Platform news
  • Enterprise Portal news
  • Events
  • Blogs from the Community

SAP Fiori LaunchPad and SAP UX News


Portal Framework Page Running in SAP Fiori Design

In the last few months we have been working to align the SAP Portal user experience with the SAP Fiori user experience. With SAP Enterprise Portal 7.4 SP7 it is the first time that we are delivering a new portal framework page following the SAP Fiori design. This is a new role based, personalized, responsive and very intuitive portal framework page, running on the SAP Portal infrastructure and following the Fiori design. Running the SAP Fiori launchpad on the Portal enables you to consume any type of content (Web Dynpro, SAP UI5, SAP Screen Personas, SAP Fiori, etc.), you are not limited to SAP Fiori applications only. Watch also this movie:



Pre-Configured Sample Content to Enable the Fiori Launchpad on SAP Enterprise Portal

Read this blog written for portal content administrators, explaining the administration tasks required for enabling SAP Fiori launchpad on Enterprise Portal. It contains links to pre-configured sample content that you can import into your portal. In only a few steps you can easily run the SAP Fiori launchpad experience within the SAP Enterprise Portal environment.


New Version of SAP User Interface Roadmap Available

The lastest version of the SAP user interface roadmap is available.




SAP HANA Cloud Platform News


New Apps in your SuccessFactors Instance

SAP HANA Cloud Platform, extension package for SuccessFactors enables customers, partners and developers to extend their SuccessFactors solutions and build entirely new HR applications to better fit their business needs. With the latest release, you can easily discover and even try new extension applications available in the SAP HANA Marketplace, within your SuccessFactors instance. For more information see the SuccessFactors release blog.


Who is Who in HANA Cloud Platform

You want to get into contact with HANA Cloud Platform experts? Have a look at this SCN page and get to know the team.


Enterprise Portal


New EP Support Blog

Read this new Enterprise Portal support blog in which people from the EP support team share interesting support cases with you and how they can be solved. You can find the first issue in the blog which is "Portal pages not supported by Chrome".




SAP TechEd && d-code 2014

SAP TechEd && d-code is approaching, you can join us from October 20-24 in Las Vegas, and from November 11-13 in Berlin, the registration is still open. This year you will hear from the SAP Portal team on the SAP portal portfolio and its strategic direction as a user experience platform: the latest innovations, benefits, demos, and showcases from SAP Enterprise Portal 7.4, SAP HANA Cloud Portal and cloud extensions, as well as the new SAP Fiori launchpad experience on top of the SAP portal portfolio. More information about our sessions: see the session catalogue. More detailed information on our SAP TechEd && d-code plans will soon be published as an SCN blog. Stay tuned!


SAP HANA Cloud Portal Partner Tests

Following two very successful partner events held earlier this year, we are announcing the next two partner events focused on SAP HANA Cloud Portal. 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.


SAP Portal ASUG Webinar Series

Register for our new ASUG webinar series on HANA Cloud Portal, SAP Fiori launchpad and SAP Portal innovations to prepare for SAP TechEd && d-code. The next session is about SAP Fiori launchpad on September 17, 11:00 US Eastern Time Zone.


SAUG National Summit 2014

Come to the SAP Australien National Summit 2014 September 8-9 in Sydney. Join the "Run Your Business Better" breakout session number 5D on how to use the SAP Fiori launchpad, held by Simon Kemp, SAP Mentor from Plaut IT.


Blogs From the Community


We recommend to read the following blogs written by members of the SAP Portal and HANA Cloud Portal SCN communities:



Last Not Least

Subscribe here to receive the next edition of the quarterly SAP Portal e-mail newsletter which is planned for October 2014. Each issue contains valuable information about SAP Portal's new portfolio, including SAP HANA Cloud Portal, Cloud for Service, SuccessFactors Extension Platform, Mobile Portal, Fiori Launchpad and more.

On one of my recent SRM projects I had a requirement wherein a specific portal role was to be assigned to a portal user based on an action performed on one of the standard SRM webdynpro screen. The assigned role was also to be removed based on another action. Probably there could be some help available on SDN, but I was unable to find it. So thought of sharing this. Hope it helps some.....


SAP has provided a service wrapper interface /sapsrm/if_spml_srvc_wrapper with methods that help carry out operations on a portal user ID. I have shown below how a user can be assigned a specific portal role, y'all can try other methods available to create a portal user, delete one, delete roles and so on...

To assign a portal role we need to get the unique ID of the role which your portal administrator could provide you.




*RFC Destination of portal in SM59

        lc_rfcdest        TYPE rfcdest VALUE 'PORTAL',    

*Portal user ID              

        lc_portal_user TYPE xubname VALUE 'TEST_USER',         

*Unique ID of the portal role

        lc_portal_role TYPE txt255 VALUE 'ROLE.PCD_ROLE_PERSISTENCE.EIuf/fYAf+G39przMn+8lcKhzII='.



       lo_spml_wrpr   TYPE REF TO /sapsrm/if_spml_srvc_wrapper,

       lt_ep_roles    TYPE /sapsrm/t_ep_roles,

       ls_ep_roles    TYPE /sapsrm/s_ep_roles.


lo_spml_wrpr = /sapsrm/cl_spml_wrpr_factory=>get_spml_wrapper( lc_rfcdest ).


ls_ep_roles-uniqueid = lc_portal_role.

APPEND ls_ep_roles TO lt_ep_roles.






         iv_logon_id = lc_portal_user

         it_roles       = lt_ep_roles   ).


   CATCH /sapsrm/cx_spml_connection.

     "Exception handling here


   CATCH /sapsrm/cx_spml_service.

     "Exception handling here



Best regards

Vipin Varghese

Hello everybody,


I have seen videos from this playlist SAP TechEd - YouTube and I was interested in one of them. So I decided to write a short blog as a critic to it.


My SAP carrier started only one year ago, so I am pretty new in the community. But one day I would like to visit SAP TechEd and some similar conferences. I think it is very important to keep in touch with new technologies, trends and innovations given by SAP. And when can you get more information than during a conference where you can meet the most involved people in the world? Well, since I am from Czech Republic I think my first SAP TechEd visit will be in Berlin. Unfortunately it will be probably not sooner than in couple of years...


Here you can look at video which I mentioned: (I am sorry for not inserting the video directly to the blog, but I did not find how to do it...If you can advice me I will edit it)


SAP Portal @ SAP TechEd 2013 - Aviad Rivlin - YouTube


Do you like it? Or not? Place your opinion in a comments below the article.


Since this is a critic I will start with "cons" part.

Did you see that large building in the beginning of the movie? Do you know it? Despite the fact I have never been in Las Vegas (even anywhere in United States unfortunately...), I know that it is hotel Palazzo in Las Vegas. Well, but the movie seems not to be meant as an invitation to SAP TechEd in Las Vegas. As I understood from the speech, it is meant to invite the people on any SAP TechEd in 2013 (as we can see from the title). Only the detail.



What I didm't like more is speaker don't looking to the camera. And not only that, he is looking to one exact place during the whole speech. It looks like he is reading the text from a board or better monitor (something white and rectangular is reflecting at the speaker's glasses) placed left from the camera (from his point of view). It doesn't seem to be very professional. Does he talking to us or somebody else standing on ours right side? Of course he can read the text, but at least it should look like he is not reading it. By the way the speech was short enough to be able to learn it and speak without reading it.



Well, lets pass to the "pros".

I like the music playing inthe background. I like it very much, it is positive and happy. Also the introduction is very good held and it gaves smooth beginning to the movie. The same for the end for the movie.

I aprecciate shortness of the movie. It is invitation, it is not neccessary to tell so much things. And the most important things were clearly said - who is the person, what is he doing, what can he and his team offer at SAP TechEd and, of course, official invite for everybody who is looking at the movie.


I like this video despite the small details. Be sure to visit Announcement of SAP Portal and HANA Cloud Portal Gamification Movie Challenge.


Best regards

This blog is for portal content administrators who would like to learn about the administration tasks required for enabling SAP Fiori Wave1 apps on Portal with already running SAP Fiori Launchpad experience (FLP on EP).


In only a few steps you can easily run the SAP Fiori Wave 1 apps within the SAP NetWeaver portal environment.

  Portal users can control Fiori Wave 1 apps on FLP on EP in the same way as the rest of applications already configured on FLP.





1)  1)   Using NW 7.31 SP12 or higher SP, NW 7.4 SP7 or higher SP

2)   Enable SAP Fiori Launchpad on Portal, for instance like this:



  3)  Fiori Wave1 apps implemented in customer’s landscape.


Required steps:


1)    (Optional) Create a Fiori1 role and a folder for Fiori1 apps in Portal content and add this role to an existing FLP on EP role.
In the example below:

  • FFP_Demo  is an FLP on EP role
  • Fiori1_apps is a role for Fiori1 apps with a folder below (folder should be marked as visible)


2Define a backend system for Fiori1 apps (Fiori gateway system in case of a separate one)





3)  Create an iView and assign it to a relevant role:


           a) Navigate to Portal Applications -> com.sap.portal.appintegrator.sap -> UI5:


   b)   Copy UI5 template and  "Paste as PCD Object" to any location under Portal Content:


  c)    Add the created iView to the relevant role

  d)   Set the following view properties and save:




Property NameProperty Value (example)
Relative Path for SAPUI5 Applicationssap/bc/bsp/sap/ui5_hcm_ts_man/index.html
Mobile App CategoriesFiori1
Object ID of Device Group *)







Launch in New WindowDisplay in separate headerless portal window (standard mode)
SAPUI5 Iconsap-icon://time-entry-request
Hand Over Portal Stylesheet<to uncheck>
NameTime Sheet Entry


*) The value of this property should be one concatenated line.



The result:


Open  FLP on EP and go to Tile Catalog. The Fiori app Time Sheet Entry appears:


  It can be assigned to "My Home" groups and become visible on a user’s home page:



To learn more about  FLP on EP:


Fiori Launchpad on Portal on help.sap.com

Known issue note FLP on EP - SAP Note 2008931

SAP Fiori Integration with SAP Enterprise Portal - SAP Note 2031108

SAP Enterprise Portal 7.4 SP7 SAP Fiori Launchpad on the SAP Portal and more

SAP Fiori Launchpad on Portal – Sample Content for Administrators

How to Integrate Fiori1 Apps with Enterprise Portal (movie)



In this Blog I will try to cover steps based on my experience for configuring Report Launchpad’s from Portal end, delivered with New business packages which uses ABAP launch pads for showing report links (Bex queries, Dashboards etc.) into standard delivered/Custom portal contents for EHSM, SRM, HR Admin,, ESS, MSS, LSO and many more,I  have not gone in details regarding basic technical configurations done in Portal like system object creation and SSO as lot of information is available on SCN for configuration of the same.


While configuring the above business packages on Portal, important aspect is most of the standard reporting contents are delivered through Report Launchpad’s which are configurable in LPD_CUST transaction of backend/ECC ,Most of the Reports utilizes corresponding BI java system for rendering and pulls up the data from the Master BI ABAP system.


Initially I faced lot of issues with running these standard reports from Portal as did not found much information on configuration of those from Portal side like what type of system object is required, does it require BI ABAP system object or BI java system object etc.


Some issues like service not found while running the reports from Portal as reports were supposed to be executed from BI java, but they were getting executed from BI abap as i created the system object of BI abap with the given System Alias in Launchpad but it should have been BI java system object.


I thought putting my experience in this Blog to provide a small help to others who might be facing these issues in configuring the similar type of scenarios.


In this Blog I am only covering Portal Admin related configurations, configurations related with BI ABAP report authorizations, activations, LPD_CUST and ECC authorizations are out of scope for this Blog.


Following are the steps which need to be executed to configure the Report Launchpad’s from Portal end.


1) Prerequisites : In order to run the standard Launchpad reports from Standard or Custom roles from Portal as a prerequisite their BI ABAP configurations should be in place like reports/dashboards should be activated and other BI related configuration should be in place ,User should exist in systems and have proper Authorizations in BI ABAP,ECC and BI java system. Administrator must have knowledge and understanding of ABAP Launchpad concept. For configuring reports to be executed from BI java, system should be present and configured for BI master system.



2) Once prerequisites are fulfilled there is need to identify which type of BI system we have to create in Portal and its system alias name. To identify that first
we have to check in the Report launchpad what type of configuration is done for the standard reports and dashboards.


From Portal role we can identify the Role and instance of the Launchpad being called from the application parameter passed in iView property, once we have the role and instance name of the Launchpad being called, we can go to LPD_CUST and search the Report Launchpad in question. After finding the relevant report Launchpad an analysis is required of its configuration, we can pick up any report or dashboard and check how it’s being configured in the Launchpad, if their specified version is SAP BW 2.x/3.x ,that means they supposed to get rendered from BI abap master system, if in the configuration their version is given like SAP BI Net weaver 7.x that means they supposed to get rendered from BI java system. Once we have identified this we need to create the system object in Portal based on this information, either BI abap system or BI java system or both depending on the requirement. System alias used are also defined in the Launchpad configurations we have to create the system object with these alias only  as given in Launchpad configurations of reports and dashboards in Portal.


3) If reports supposed to be rendered and executed from BI abap system then we have to create a BI abap system object depending on the system landscape either use Load balancer or dedicated application server system template to create the system object and give the system Alias same as configured for the reports in the standard or custom Launchpad’s. User should have proper authorizations to execute the reports in BI abap system also user should exist in ECC system and have relevant authorization for the standard role for the particular module like EHSM,LSO,MSS etc. as these Launchpad’s are shipped in ECCwith the standard EHSM,SRM and HR contents.


4) If reports are supposed to get rendered from BI java system then we have to create system object in Portal for BI java, and provide the same system alias which is given in Launchpad configurations of reports and Dashboards in LPD_CUST transaction,


Initially i was unsure on what type of system object i will be using for creating BI java system in portal as no standard SAP help material i found on SCN on this topic. Did some research on SCN and based on some threads i concluded that i can create a system object of type dedicated server or load balance server and i have to just populate the Web application server properties like WAS host name and Protocol to create a BI java system object in portal, i gave logical name as <SID>CLNT000 in system object properties and populated the BI java server url in WEB as host name and specified the protocol.


Next step was establishing trust between portal and BI java system, after performing it BI java system is ready for executing the Launchpad reports from portal.

Important point to note is User must exist in Portal, Bi java (No additional roles needed on Bi java server) and BI abap server and have proper authorizations in place for this scenario to work properly.


These are the basic steps which need to be taken care of while configuring report Launchpad’s based on ABAP Launchpad from Portal end.I hope this blog will help people like me who are configuring this scenario for the first time.


Happy reading, Comments and suggestions are welcome


Some Reference links:

Portal System Object Properties – Web AS - Portal - SCN Wiki

Working with Launchpads at Design Time - Launchpads - SAP Library


This Blog Describe how to extract the total number of End users & Service users logon counts from each Portal server node using Authentication logs .This information correctly depicts the total number of logon, user has performed unlike the unique login of the user provided in portal activity reports. Analyst /Consultants can merge this information logs with the Backend ECC/HR/SRM/CRM user logs maintained in USR02 tables for further reporting purposes for determining business transactions in more detailed manner.

following are the steps :


1) Go to NWA log viewer of SAP Portal




2) Choose authentication log from view




3) Click everywhere and from advance filter choose date filter and set it for biggining of day time till present time click on apply filter




4) Now download the excel file of logs from log file download content




5) Choose all column and download





6) Save it on the location you like on your machine. Now open excel file and apply filter, Select all login ok and application irj logs and now choose and count the required users




Below example show total number of 120 logons from the selected date on all the nodes of SAP portal for all user types, user type can be selected from user dropdown (Service or end user)




Portal Consultants can merge this information with ECC/ABAP system user logs and device statistics and reports ,they can formulate a Excel template based on their requirement  if they want and feed the data from ABAP system and Portal Authentication logs and generate Graphs out of it.


Main Advantage which I see in this approach is no coding required (Java or ABAP) and all the user logins(End users & Service users) based on the application(irj) can be identified from all server nodes, the approach works well in the Portal scenario where login screen is used by the users for Login to Portal.

I am listing down some use cases where this approach can be used:

-- Getting the last logon date of WAS users or irj Portal users.

-- Generating Portal Usage history reports from this logs using some reporting tool like Excel etc.

-- Can be used for Auditing purpose and to identify security attacks


Its good to take a back up of these logs periodically as depending on portal usage and log size configured ,logs will be overwritten once the log size reaches its maximum value.


Some refrences:





Thanks for reading!


Filter Blog

By author:
By date:
By tag: