Show TOC

Integrating Web Dynpro and SAP GUI Applications Using Mass MaintenanceLocate this document in the navigation structure

If you want to integrate a whole set of Web Dynpro and SAP GUI applications in the launchpad, you create technical catalogs with application descriptors in the backend and replicate these catalogs to the frontend server.

Prerequisites

You are assigned to the following roles:

  • Backend role: SAP_UI2_ADMIN_750

  • Frontend server role: SAP_UI2_ADMIN_731

These roles are included in the composite role SAP_UI2_ADMIN. See Configuring Roles with Launchpad Start Authorizations.

Context

There are two types of integration scenarios:

  • With SAP S/4HANA, a set of Web Dynpro ABAP applications and SAP GUI transactions is available as standard content in predefined technical catalogs. You can consume this SAP S/4HANA content in the launchpad and adapt it to your needs.

    For a detailed description of the required configuration steps, refer to the SAP S/4HANA documentation at http://help.sap.com/s4hana, select a release and choose Start of the navigation path Product Documentation Next navigation step UI Technology Guide End of the navigation path.
  • You can use the Mass Maintenance Tool to create application descriptors for all the Web Dynpro ABAP applications and SAP GUI transactions that you want to integrate in the launchpad. This allows you to create application descriptors for all applications in a component efficiently and in one place.
For both scenarios, you need to replicate the technical catalogs from the backend to the front-end server using an extraction report. After the replication, you can create business catalogs based on the technical catalogs.
The following graphic shows the major entities involved in these scenarios:
Entities in the back-end system:

  • Technical catalog

    Technical catalogs contain applications that are grouped by technical aspects (e.g. application component).
Entities on the frontend server:

  • Replicated technical catalog

    The replicated catalog cannot be edited or assigned to a PFCG role.

  • Business catalog

    Business catalogs contain applications grouped according to a specific business role. The content of the business catalog is a subset of the content of the technical catalog. This subset reflects the authorization requirements of a certain business user.

The following graphic provides a high-level overview of the configuration steps that are required to set up the integration of custom backend catalogs:

NoteThe following image contains links to more information.
SAP GUI, Web Dynpro ABAP and Floorplan Manager (FPM) applications require an application descriptor if they are to be called from the SAP Fiori launchpad. You can use the Mass Maintenance Tool (MMT) to create all the necessary application descriptors efficiently and in one place. To allow the launchpad to consume catalogs containing Web Dynpro ABAP and SAP GUI applications from a specific back-end system, you need to establish connections between frontend server and back-end systems. To ensure that catalogs are only replicated for specific system aliases, you assign the relevant system alias to the catalog. To make the backend catalogs visible in the launchpad and in the launchpad designer, you need to replicate them to the frontend server. This section provides information about catalogs. Authorizations to run launchpad and launchpad designer and to access launchpad content are assigned to users based on roles.

Procedure

Perform the following steps in the backend system:

  1. Create an application descriptor for each application you want to integrate in the launchpad.

    • Add your application descriptors to an existing catalog.

    • If there is no catalog that fulfils your requirements, you can create your own catalogs and add your application descriptors to them.

    See Create Application Descriptors Using the Mass Maintenance Tool.

Perform the following steps on the frontend server:

  1. Establish connections to backend systems.

    If you add your application descriptors to an existing catalog, you can skip this step.

    See Establish Connections between Frontend Server and Back-End Systems.

  2. Assign system aliases to the technical catalog.

    If you add your application descriptors to an existing catalog, you can skip this step.

    See Assign System Alias to Catalog.

  3. Use the extraction report to replicate the catalog into the frontend system.

    See Extract Transactions and Web Dynpro ABAP Applications.

  4. Create business catalogs based on the technical catalog.

    The business catalog should reference the app launcher tiles and target mappings in the technical catalog.

    In the launchpad designer, use features such as Copy Tile, Copy Target Mapping and Copy Catalog.

    See Setting Up Content With the Launchpad Designer.

  5. Configure authorization roles.