Skip to Content

Fiorified BI Launchpad in BOE 4.2

 The Fiorified BI Launchpad is a modern version of the classic BI launchpad application introduced from BOE 4.2 SP04. It has a fiorified user experience that makes the user interface (UI) simple and intuitive.

Foirified BI Launchpad URL http://<WebServer>:<Port>/BOE/BILaunchpad

where <WebServer> is the name of the web server for BI platform and <Port> is the port number for the platform.

Before Start:

New BI launchpad has dependency on REST SDK which deployed on:

  1.  WACS(web Application container Server).
  2. Tomcat

More info : https://blogs.sap.com/2017/12/15/bi-platform-rest-sdk-rws-in-boe-4.2/

So WACS or Tomcat must be running to use new Launchpad.

To check REST APIs, simple API

Where <port> is the port number of WACS(Web Application Container Server) or Tomcat.

Above URL Response contains : product version details.

Logon Page:

Administrator configurations for new BI Launchpad (Fiorified) :

Name FioriBI.properties
Location “\BOE\WEB-INF\config\default” (BOE webapp in webserver)

Home Page:

 

BI Launchpad Tool bar:

Tab

Description

My Home

When User first logs in to the BI Launch Pad, this is default user interface, which user can customize for the tasks you perform there.

Schedule

In this tab user can access all schedule instances scheduled by him using calendar widget and perform client actions on those instances

Inbox

(If User doesn’t have rights for both My Alerts and Inbox then this tab will be hidden)

The Inbox lets you view and manage system alerts,notifications and documents as message.

Folders

(If User doesn’t have rights for both My Folders and Public Folders then this tab will be hidden)

User can organize and manage objects using public and personal folders.

Recycle Bin

(Administrator can hide this tab by disabling Recycle Bin)

(Not user specific)

Recycle Bin is an application in the BI Launch Pad. When the user deletes an item from the BOE system, it is moved to the Recycle Bin, where it is temporarily stored until the Recycle Bin is emptied. This gives the user the opportunity to recover accidentally deleted reports/folders and restore them to their original locations.

Note:  Based on the user rights Menu tabs will be rendered and User can configure to any tab as default home tab.

Filters in My Home:

Filter

Description

Show all

This filter lists all the flat list BI objects : documents, reports, categories in the Home page.

My recently viewed

This filter lists all your recently viewed BI  documents in the Home page.

My Documents

This filter lists all documents you created in the Home page.

All Categories

A category is an organizational alternative to a folder. Use categories to label objects. This filter lists all the categories (Corporate and Personal) in the Home page.

My Favorites

(This is new feature available only in new launchpad)

This filter lists all documents or categories that you marked as your favorites in the Home page.

My recently run

This filter lists all your recently run BI documents in the Home page.

 BOE 4.2 SP05 features:

  • Context refresh in all the pages.
  • Uploading and editing the category image:
  • Table widget in all the pages were changed. The new Table widget provides sorting and filtering options.
  • More documents types were supported such as LUMX.
  • Landing Page and Landing filter was introduced. In account preferences, we can change the landing page:
  • GDPR(Global data protection regulation): The product was made GDPR compliant:
  • Back button was introduced in new BILaunchpad:
  • Expired and warning status was introduced in schedule. And ‘Pause’ and ‘Resume’ Caf actions were introduced.
  • The document can be marked as Favorite.
  • Web-Assistant to guide us through the Launchpad (https://blogs.sap.com/2017/12/19/fiorified-bi-launchpad-and-web-assistant-in-boe-4.2/).

License:

The BI platform supports the following types of user licenses:

  • Concurrent user
  • Named user

Note: Number of concurrent logon sessions for a named user is limited to 10. If the named user tries to log into the 11th concurrent logon session, the system displays an approprite error message. You need to release one of the existing sessions to be able to log in.

Session Management:

Lifetime of the web session is defined in the web.xml of web-app (BOE).

The default time-out value for each web-app is 20 minutes.

If User opens Old BI launchpad and fiorified BI launchpad in different tabs of same browser then both the launchpads uses same Enterprise Session.

Web Application Bundle:

New fiorified BI launchpad also part of BOE webapp bundle. There is no need of some extra deployment specifically to new launchpad.

But there is separate .properties file for new launchpad called “FioriBI.properies” .

Name FioriBI.properties
Location “\BOE\WEB-INF\config\default” (BOE webapp in webserver)

Copy *.properties  file to “\BOE\WEB-INF\config\custom” location and change the values as per requirement.

Restart the web server and clear the cache in browser before refresh the BI launchpad.

 

Videos:

Related Links:

https://help.sap.com/viewer/p/SAP_BUSINESSOBJECTS_BUSINESS_INTELLIGENCE_PLATFORM

https://blogs.sap.com/2017/12/19/fiorified-bi-launchpad-and-web-assistant-in-boe-4.2/

https://blogs.sap.com/2017/12/15/bi-platform-rest-sdk-rws-in-boe-4.2/

 

147 Comments
You must be Logged on to comment or reply to a post.
  • Do we have any documentation for Fiori to work with Apache as frontend and Tomcat as backend ?

     

    If we change RestFul URL to Tomcat one everything works, once we change it to Apache URL “Invalid Session” is displayed

    • Nevermind, fixed it by adding JkMount /BOE/*/FioriBI/BOETimeoutPing instead of JkMount /BOE/*/Bing/BOETimeoutPing as per SAP note 2477447

       

      Note needs to be edited for SP06

  • I just updated from BOE4.2 SP05 Patch 500 to SP06 Patch 300 and I cannot open documents. THe error I am getting is

    Error while performing the request; server is unable to find the match for the Request-URI (RWS 00056)

    It looks like it fails on this call

    1. Request URL:
    2. Request Method:
      GET
    3. Status Code:

      404

    In console I have:

    flapjack4ui5.js:1 18:00:23 sap.bi.webi.action.composite.LoadDocument – Error during LoadDocument {action: “openDocument”, status: “error”, error: undefined}
    e.log @ flapjack4ui5.js:1
    i @ flapjack4ui5.js:1
    error @ flapjack4ui5.js:1
    (anonymous) @ LoadDocument.js?eval:1
    Promise.catch (async)
    n.do @ LoadDocument.js?eval:1
    (anonymous) @ flapjack4ui5.js:2
    setTimeout (async)
    a @ flapjack4ui5.js:2
    n.fireAction @ flapjack4ui5.js:2
    (anonymous) @ Document.controller.js?eval:1
    Promise.then (async)
    (anonymous) @ Document.controller.js?eval:1
    Promise.then (async)
    u._handleDocumentRouteMatched @ Document.controller.js?eval:1
    a.fireEvent @ EventProvider-dbg.js:228
    _routeMatched @ VM3190:1309
    (anonymous) @ VM3190:1184
    execute @ VM3190:7472
    dispatch @ VM3190:7475
    dispatch @ VM3190:7474
    parse @ VM3190:7482
    parse @ VM3190:1203
    initialize @ VM3190:1204
    u.init @ Component.js?eval:1
    (anonymous) @ ManagedObject-dbg.js:497
    constructor @ ManagedObject-dbg.js:516
    constructor @ Component-dbg.js:245
    constructor @ VM3190:619
    f @ Metadata-dbg.js:346
    e @ Component-dbg.js:1823
    sap.ui.component @ Component-dbg.js:1882
    u.createComponent @ Core-dbg.js:1831
    (anonymous) @ Interface-dbg.js:44
    (anonymous) @ index.html:50
    (anonymous) @ Core-dbg.js:1176
    u._executeInitListeners @ Core-dbg.js:1175
    u.init @ Core-dbg.js:1056
    (anonymous) @ Core-dbg.js:347
    l @ jquery.sap.global-dbg.js:2600
    S.finishTask @ jquery.sap.global-dbg.js:2595
    (anonymous) @ Core-dbg.js:355
    p @ jquery-dbg.js:3187
    fireWith @ jquery-dbg.js:3317
    ready @ jquery-dbg.js:3536
    V @ jquery-dbg.js:3552

    flapjack4ui5.js:1 18:00:23 sap/bi/webi/controller/Document.controller – {action: “loadDocument”, status: “error”, error: undefined}

    I also opened a ticket with SAP support but they asked me to split deploy all over again, which didn’t fix the issue.

    Any help or feedback is greatly appreciated.

    Thanks,

    Rene