Show TOC

Setting up NavigationLocate this document in the navigation structure

You have to perform several configuration steps to add applications as navigation targets to the launchpad.

Prerequisites

To allow Web Dynpro ABAP applications to be started from the launchpad, you need to make sure the server runtime for SAP NetWeaver user interface (UI) services is installed in the back end. This is required when there is a separation between front-end server and back-end system. To install the server runtime for SAP NetWeaver user interface (UI) services, you install product instance Integration Services: Provider and activate ICF node /default_host/sap/bc/ui2/nwbc.

For more information about installing the product instance, see chapter "Software Units" in the Master Guide for User Interface Add-On for SAP NetWeaver. For more information about activating ICF nodes, see Active Services in ICF (UI Services).

If you configure the Web Dynpro ABAP or SAP GUI application to run on a system other than the launchpad front-end server, you need to switch off the login cross-site request forgery (XSRF) protection on the ICF node /sap/bc/ui2/nwbc for NWBC for HTML. Otherwise it might not be possible for end users to log on with a launchpad URL pointing to this Web Dynpro ABAP or SAP GUI application.

For more information, see SAP Note 1617090 Information published on SAP site.

Context

The following application types can be launched from the launchpad:
  • SAPUI5
  • Web Dynpro ABAP
  • SAP GUI for HTML
  • SuccessFactors applications
  • Any web application

Navigation between launchpad applications is based on intents. To set up navigation, perform the following steps:

Procedure

  1. Identify an application that you would like to use as a navigation target.
  2. Identify a semantic object you would like to refer to. You can either choose one of the semantic objects shipped by SAP, or create a new semantic object.
  3. Create a catalog in the launchpad designer or use an existing one.
  4. Create and configure a target mapping. In the launchpad designer, you add a target mapping to the catalog. In the target mapping configuration, you map an intent to a navigation target.
  5. Create and configure an app launcher tile. In the launchpad designer, you add a dynamic or static app launcher tile to the catalog. In the tile configuration, you enter meta data (for example title, description and icon) and define the navigation by specifying semantic object and action.
  6. Assign the catalog that contains the app launcher tile and the target mapping to a role in role maintenance (transaction PFCG).
Related Information