Sie sind auf Seite 1von 60

Copyright(c) 2018 by Nixon Vunganai.

All rights reserved.

Neither this document nor any part of it may be copied or reproduced in any form or by any
means or translated into another language, without the prior consent of Nixon Vunganai. The
information contained in this document is subject to change without notice.

WHATSAPP +255738656506
INTRODUCTION 5

UI TECHNOLOGIES 6

SAP Fiori 6
Initial Setup 6
Prerequisites 6
Schedule SAPUI5 Application Index Calculation 7
Connection Settings (Front-End Server to ABAP Back-End Server) 7
Define Trust for SAP Business Systems 7
Manage RFC Destinations 8
Activate SAP Gateway 8
Define SAP System Alias 8
Initial Launchpad Configuration 9
Service Maintenance of SAP Gateway 9
Maintain Logon Group 10
Service Maintenance of Internet Communication Framework ( ICF ) 10
Assign Launchpad Authorizations to Users 11
SAP Web Dispatcher 12
Configure SAP Web Dispatcher 12
Define Host Name of SAP Web Dispatcher for Applications 12
Configuring SAP Fiori Search 13
Setup Feedback Service 14
Configuring Launchpad Content 14
Adding Apps to SAP Fiori Launchpad 14
Navigation Concept 14
App-Specific Documentation 14
Configure Target Mappings and Tiles 15
SAP Fiori Launchpad Designer ( Cross-Client ) 15
SAP Fiori Launchpad Designer (Current Client) 15
Edit Legacy Navigation Target Configurations in LPD_CUST 16
Prepare Backend Catalogs for Reuse 16
Establish RFC and HTTP Connection 16
Extract Transactions and Web Dynpro Applications 17
Define Semantic Objects for Navigation 18
Configure Authorization Roles 19
Data Administration 19
Invalidate Caches 19
Create Cleanup Jobs 19
Support Tools 20
SAP Fiori Launchpad Content Check Report 20
SAP Fiori Launchpad Intent Analysis 20
SAP Gateway Application Log 21
SAP Gateway Error Log 21
SAP NetWeaver Business Client 21
Define SAP GUI Tags (Runtime for SAP NetWeaver User Interface 21
Define Parameter Names 22
Assign Parameter Values 22
SAP NetWeaver User Interface Services 22
Define Semantic Objects 22
Register POWL for OData Consumption 23
Register OData Service for UI2 Cache Usage 23
SAP Jam Integration 23
Introduction to SAP Jam Integration and Collaboration 23
Define HTTP Service 25
Maintain Certificate of Service Provider 25
Enable SAML 2 Identity Provider 26
Prepare OAuth SHA1 26
Register Application as OAuth Client 27
Register SAML Trusted Identity Provider at SAP Jam 28
Define Server Settings 28
Define Application Settings 30
Register OData Service 30
Define URL Mapping 32
Configure REST Tunnel 33
Define Service of Provider 35
Notifications 36
Send Notifications 36
Maintain bgRFC Destination 37
Activate OData Service for Notifications 37
Register Event Handler for Change Documents 38
Business Add-Ins ( BAdIs ) 39
BAdI: External ID for Backend User 39
BAdI: Fill Empty Fields of OData Service Registry 39
BAdI: OData Service Mapping 40
BAdI: Authorization Check for Subscription and Notification 40
BAdI: Subscription Filter 41
SAP Visual Business 42
Maintain Application Definitions 42
Overwrite Map Server Default URLs 43
Overwrite Geo-Coding Service Default URLs 43
Define Application Replacements 44
UI Theme Designer 44
Use Custom Themes 44
Activate SICF service for using custom themes 44
Maintain Custom Themes 45
Activate SICF services for UI theme designer 45
ACF: Create Whitelist 45
ACF: Create Certificate 48
Floorplan Manager 49
Activate ICF Services for FPM Applications 49
Context Based Adaptations ( CBAs ) 49
Define Schemas 49
Define Dimensions 49
Message Settings 50
Define FPM Message Mapping 50
WHATSAPP +255738656506
Define FPM Message Categories 50
Set-Up Printing for Web Dynpro ABAP ALV System-Wide 51
Create RFC Destination in AS Java 51
Create RFC Destination in AS ABAP 53
Set-Up Web Service Destination for Adobe Document Services 54
Edit Web Dynpro ABAP-Specific Settings 56
Edit SAP GUI-Specific Settings 57
Manage Generic Crystal Reports 57
INTRODUCTION
Welcome to the fascinating world of SAP. This book helps you crack the tricks of mastering SAP HANA
Customization

WHATSAPP +255738656506
UI Technologies

SAP Fiori

Initial Setup

Prerequisites

Use

Check if this is the front-end server of your SAP Fiori system landscape. Read the documentation about
the system architecture for SAP Fiori apps on SAP Help Portal at
http://help.sap.com/fiori_bs201/helpdata/en/ec/a941524a6b6760e10000000 a42f68/content.htm?fram
eset=/en/29/9a5652d8c725fe10000000a441470 /frameset.htm.

Check the below mentioned settings before you continue to set up SAP Fiori launchpad. This list
does not claim to be exhaustive.

Requirements

Internet Communication Manager


The SAP Fiori launchpad needs a working HTTP(S) connection from the client (browser) to the current
SAP NetWeaver Application Server ABAP. You can check the HTTP(S) settings ( e.g. host name and
port number) in transaction SMICM.

Enter the full domain name into the profile parameter icm/host_name_full. You can check this parameter
in transaction RZ11.

Single-Sign-On
Activate single-sign-on. The front-end server must be able to issue a single sign-on ticket. Therefore, set
the profile parameter login/create_sso2_ticket = 2 and set the profile parameter login/accept_sso2_ticket
= 1. You can check these parameters in transaction RZ11.

SAP NetWeaver Gateway


The SAP NetWeaver Gateway must be installed on the SAP Fiori front-end-server. If it is not
yet installed, you need to install it first. Proceed as described in the installation guide for SAP NetWeaver
Gateway on SAP Help Portal at
http://help.sap.com/saphelp_gateway20sp08/helpdata/en/c/424a2657aa4cf58d
f949578a56ba80/frameset.htm.

SAP NetWeaver Gateway supports two deployment options: The embedded deployment and the central
hub deployment. For more information, see
http://help.sap.com/saphelp_gateway20sp08/helpdata/en/62/91ad98b19 b4a91bca77fbe44227f/content
.htm.

For SAP Fiori, set up SAP NetWeaver Gateway with the deployment option Central Hub
Deployment to separate back-end from front-end components. For more information, see the SAP Fiori
documentation on the SAP Help Portal at
http://help.sap.com/fiori_bs201/helpdata/en/4c/ca4152fc94b610e10000000a44176d/content.htm?fram
eset=/en/29/9a5652d8c725fe10000000a441470 /frameset.htm.
Read the documentation about the system architecture for SAP Fiori apps on SAP Help Portal at
http://help.sap.com/fiori_bs201/helpdata/en/ec/a941524a6b6760e10000000a42f68 /co
ntent.htm?frameset=/en/29/9a5652d8c725fe10000000a441470 /frameset.htm.

Example

Example of a full domain name: icm/host_name_full = server.domain.com

Example of single sign on settings: login/create_sso2_ticket = 2 and login/accept_sso2_ticket = 1

Schedule SAPUI5 Application Index Calculation

Use

The SAPUI5 application index provides an indexing and caching mechanism for information related to
SAPUI5 apps, components, and libraries that are contained in SAPUI5 repositories on the SAP
NetWeaver Application Server for ABAP. The index is used by several different services (such as the
SAP Fiori launchpad and cache buster), which means you have to schedule the index creation as a
background job.

Activities

To update the SAPUI5 application index regularly, in Define Background Job ( transaction
SM6), schedule the execution of the /UI5/APP_INDEX_CALCULATE report as a background job.

For more information, see the report documentation and SAP Library for User Interface Add-On 2 for
SAP NetWeaver on SAP Help Portal at http://help.sap.com/nw-uiaddon. Under Application Help, open
SAP Library and search for SAPUI5 Application Index.

Connection Settings (Front-End Server to ABAP Back-End Server)

Define Trust for SAP Business Systems

Use

The back-end server(s) of SAP Fiori launchpad must trust the front-end server to enable a working single
sign on environment.

Activities

Proceed as described in the configuration guide of SAP Gateway on SAP Help Portal at
http://help.sap.com/saphelp_gateway20sp08/helpdata/en/46/17f252ab9471aa450906fbf62fef7/content.
htm?frameset=/en/4c/a670b0e6c4c01ae2b9a042056f9dc/frameset.htm. Note: This activity has to be
performed on each back-end system.

Example

You have the front-end server FES with client 010 and two SAP Business Suite back-end systems BE1
and BE2.

WHATSAPP +255738656506
On BE1 and BE2 you create the RFC destination FESCLNT010 and use SMT1 to create the trust
relationship.

At runtime the user log in is done on system FES and the single-sign-on ticket is issued here. When
calling either back-end system BE1 or BE2 the single-sign-on ticket is passed with this call.
Now the back-end server checks if it trusts the system that issued the single-sign-on ticket. If yes, then
the trust is set up correctly and the single-sign-on works correctly as well.

Manage RFC Destinations

Use

Define remote function call (RFC) destinations from the front-end server for SAP Fiori to the back-end
system(s).
Additionally define an RFC destination that has the front-end server itself as target for local RFC calls.

Requirements

The back-end servers must already trust the front-end server.

Activities

Proceed as described in the configuration guide of SAP Gateway on SAP Help Portal at
http://help.sap.com/saphelp_gateway20sp08/helpdata/en/0a/a6ff82d7d94b1fa7b87f29ecaa0e01/content.
htm?frameset=/en/4c/a670b0e6c4c01ae2b9a042056f9dc/frameset.htm.

Example

You have the front-end server FES (client 010) and two SAP Business Suite back-end systems BE1
(client 020) and BE2 (client 020).
On FES you create the RFC destinations BE1CLNT020_T, BE2CLNT020_T, and FESCLNT010_T and
activate the trust relationship in all these RFC destinations.

Activate SAP Gateway

Use

Activate SAP Gateway for using SAP Fiori launchpad.

Define SAP System Alias

Use

A SAP system alias is needed as the logical name of a system connection.

Requirements
Remote function call (RFC) destinations must exist from the front-end server for SAP Fiori to all back-
end servers.

Standard settings

Create one SAP system alias pointing to the front-end server and activate the indicator Local Gateway.

Create one SAP system alias for each back-end system and assign the corresponding RFC destination.

Initial Launchpad Configuration

Service Maintenance of SAP Gateway

Use

Several SAP NetWeaver Gateway services are needed for running SAP Fiori launchpad. Here you can
activate and maintain details of these services.

Standard settings

For running SAP Fiori launchpad as an end user, you need the following services as a basis (these are the
external service names):

- /UI2/INTEROP
- /UI2/PAGE_BUILDER_PERS
For running SAP Fiori launchpad designer as an administrator, you need the following services in
addition:

- /UI2/PAGE_BUILDER_CONF
- /UI2/PAGE_BUILDER_CUST
- /UI2/TRANSPORT

Activities

For each above mentioned external service name do the following:

- Add the service to the service catalog (you can restrict the filter by a local system alias).
Specify the technical service name in the customer namespace. Use the
highest available version.

- Activate the Internet Communication Framework (ICF) node ODATA.


- Assign an SAP system alias that uses the local system.
- Choose Call Browser to check the connection and to automatically generate authorization-related
hash values.
For more information, see the documentation for setting up the SAP Fiori launchpad on SAP Help
Portal at http://help.sap.com/saphelp_uiaddon10/helpdata/en/84/ff5551a49c4bb4d
f90c2fcfd96f/content.htm?frameset=/en/a7/fff2179874b4a8a5b995c a55a6/frameset.htm.
WHATSAPP +255738656506
Example

You created the following SAP NetWeaver Gateway services:


Technical Service Name External Service Name
ZINTEROP /UI2/INTEROP
ZPAGE_BUILDER_PERS /UI2/PAGE_BUILDER_PERS
ZPAGE_BUILDER_CUST /UI2/PAGE_BUILDER_CUST
ZPAGE_BUILDER_CONF /UI2/PAGE_BUILDER_CONF
ZTRANSPORT /UI2/TRANSPORT

Maintain Logon Group

Use

This is an optional customizing activity for setting up the SAP Fiori launchpad designer. This activity is
only necessary in multi application server systems.

Use transaction SMLG to configure a logon group that is assigned to only one single application server.

KW documentation:
http://help.sap.com/saphelp_uiaddon10/helpdata/en/b1/600 bceda146cd8b042f2a4248c99a/f rameset.htm

Requirements

Service Maintenance of Internet Communication Framework ( ICF )

Use

The Internet Communication Manager (ICM) and its framework (ICF) are the entry point of HTTP(S)
requests to the SAP NetWeaver Application Server ABAP. It is necessary to activate the services of SAP
Fiori launchpad.

Standard settings

The following nodes need to be activated:

- /default_host/sap/bc/ui2/nwbc
- /default_host/sap/bc/ui2/start_up
- /default_host/sap/bc/ui5_ui5/sap/ar_srvc_launch
- /default_host/sap/bc/ui5_ui5/sap/ar_srvc_news
- /default_host/sap/bc/ui5_ui5/sap/arsrvc_upb_admn
- /default_host/sap/bc/ui5_ui5/ui2 /ushell
- /default_host/sap/public/bc/ui2
- /default_host/sap/public/bc/ui5_ui5

Activities

Proceed as described in the SAP Fiori launchpad documentation on SAP Help Portal at
http://help.sap.com/saphelp_uiaddon10/helpdata/en/b/794d91f25a4bf9a9e42a41896641/content.htm
?frameset=/en/a7/fff2179874b4a8a5b995ca55a6/frameset.htm.

Assign Launchpad Authorizations to Users

Use

Users need authorization roles to run the SAP Fiori launchpad (as an end-user) and the SAP Fiori
launchpad designer (as an administrator). Here you assign the necessary authorization roles and adjust
them according to your needs.

Requirements

You finished the steps of the customizing activity Service Maintenance of SAP Gateway. There you
created technical service names for each relevant SAP Gateway service and successfully called each
of the services.

Standard settings

As template the following authorization roles exit:

- SAP_UI2_USER_700
- SAP_UI2_ADMIN
The user role contains necessary authorization defaults for running the SAP Fiori launchpad.

The admin role contains necessary authorization defaults for running the SAP Fiori launchpad designer.

Activities

1. Copy both template roles into your customer namespace.


2. Add additional authorization default entries in the copied roles for the TADIR services with the
following ID:
a) Program ID: RTR
b) Object Type: IWSG
c) Object Name: <object name>.
Replace <object name> with the technical service names that you used in the customizing
activity Service Maintenance of SAP Gateway.

3. Generate the authorization profiles in each role.


WHATSAPP +255738656506
4. Assign end-users of the SAP Fiori launchpad to the user role and assign administrators of the SAP
Fiori launchpad designer to the admin role.
For more information, see the documentation for setting up the SAP Fiori launchpad on SAP Help
Portal at http://help.sap.com/saphelp_uiaddon10/helpdata/en/85/befff5604fa09a16
68dd97ef4407/content.htm?frameset=/en/a7/fff2179874b4a8a5b995c a55a6/frameset.htm.

Example

You created the following roles as a copy: ZUI2_USER_700 and ZUI2_ADMIN You
assigned the following authorization default entries to the copied roles:

- ZUI2_USER_700
- TADIR service RTR IWSG ZINTEROP_0001
- TADIR service RTR IWSG ZPAGE_BUILDER_PERS_0001
- ZUI2_ADMIN
- TADIR service RTR IWSG ZINTEROP_0001
- TADIR service RTR IWSG ZPAGE_BUILDER_PERS_0001
- TADIR service RTR IWSG ZPAGE_BUILDER_CUST_0001
- TADIR service RTR IWSG ZPAGE_BUILDER_CONF_0001 - TADIR service RTR
IWSG ZTRANSPORT_0001

SAP Web Dispatcher

Configure SAP Web Dispatcher

Use

The SAP Web Dispatcher is needed as reverse proxy in front of the different systems and hosts of SAP
Fiori launchpad to ensure the single domain policy of browsers.

Activities

Proceed as described in the SAP Fiori launchpad documentation on SAP Help Portal at
http://help.sap.com/saphelp_uiaddon10/helpdata/en/a/d29d2a7d9429bb2f1e2f5ae5df5b/content.htm
?frameset=/en/a7/fff2179874b4a8a5b995ca55a6/frameset.htm.

Define Host Name of SAP Web Dispatcher for Applications

Use

The host name of the SAP Web Dispatcher (SAP's reverse proxy) and the port numbers that are used for
HTTP and HTTPS on the SAP Web Dispatcher host must be defined on the SAP NetWeaver Application
Server ABAP to enable the generation of start URLs that point to the reverse proxy instead of the SAP
NetWeaver Application Server ABAP.

Requirements

You installed an SAP Web Dispatcher and configured its profile for usage with SAP Fiori launchpad.

Standard settings

You define entries in this customizing activity for the applications SAP Fiori launchpad and
SAP Fiori launchpad designer as these can be started from within the front-end server for SAP Fiori. As
both have the same segments in the beginning of their path, it will be sufficient to define one entry for
both applications in table HTTPURLLOC:

Activities

Create the following entries in table HTTPURLLOC and adjust them according to your system
landscape.

Sort Key Protocol Application Host Port


0001 tps> HTTPS /sap/bc/ui5_ui5* <webdisp_host> < webdisp_port_ht

0002 HTTP /sap/bc/ui5_ui5* <webdisp_host> < webdisp_port_ht


tp>

Configuring SAP Fiori Search

Use

This is an optional customizing activity for configuring embedded search in the back-end
system.

Requirements

The back-end system must run with an SAP HANA database.

Activities

Configuring embedded search in the back-end system.


You must have set up the Embedded Search technology.

For more information, see SAP Help Portal at http://help.sap.com # SAP NetWeaver # SAP
NetWeaver Platform 7 # Application Help # Function-Oriented View # Search and Operational
Analytics # Embedded Search # Setting Up Embedded Search
(http://help.sap.com/saphelp_nw74/helpdata/en/f1/2e6f2de1424beda628670406e7 fcc/content.htm?fra
meset=/en/6d/ad05874f44592b42abc729eeadd4 c/frameset.htm ).

Note
When search models are transported, for example in the event of a system upgrade, manual
steps can be required. For more information, see SAP Help Portal at http://help.sap.com #
WHATSAPP +255738656506
SAP NetWeaver # SAP NetWeaver Platform 7 # Application Help #
Function-Oriented View # Search and Operational Analytics # Embedded Search #
Managing Search and Operational Analytics # Search-Specific Administration Tasks and
Information # Transporting Search Models
(http://help.sap.com/saphelp_nw74/helpdata/en/cd/6202b708dc46dea7baf7c0649554 d/content.htm?fra
meset=/en/6d/ad05874f44592b42abc729eeadd4c/frameset.htm).

Activating Search in SAP Business Suite Foundation


You must have activated the following business function in Customizing for your SAP Business Suite
application under Activate Business Functions:

- SAP HANA Search for SAP Business Suite ( BSESH_HANA_SEARCH )

Furthermore, the activities under Cross-Application Components # General Application Functions #


HANA-Based Search for SAP Business Suite are relevant in Customizing for your SAP Business
Suite product.

Setup Feedback Service

Use

This is an optional customizing activity for setting up the SAP Feedback Service.
Activities

See also

http://help.sap.com/saphelp_uiaddon10/helpdata/en/b9/4112cf401745729244e2478067d72 a/frameset.ht
m

Configuring Launchpad Content

Adding Apps to SAP Fiori Launchpad

Navigation Concept

Use

For more information about the navigation concept of SAP Fiori, see the documentation for setting up
SAP Fiori launchpad on SAP Help Portal at
http://help.sap.com/saphelp_uiaddon10/helpdata/en/bd/8aed27ab4541bcce8e75c046 fc/content.htm
?frameset=/en/a7/fff2179874b4a8a5b995ca55a6/frameset.htm.

App-Specific Documentation

Use

You want to add an app of the SAP Business Suite to the SAP Fiori launchpad.
Standard settings

For more information, see the documentation on SAP Help Portal at http://help.sap.com/fiori.

Proceed according to the app-specific implementation documentation.

Configure Target Mappings and Tiles

SAP Fiori Launchpad Designer ( Cross-Client )

Use

The SAP Fiori launchpad designer is an administrator tool that runs in the browser. It is used for
configuring app tiles as well as target mappings. Additionally it is used for pre-configuring the end user
home page of the SAP Fiori launchpad.
For more information, see also the documentation for the SAP Fiori launchpad designer on SAP Help
Portal at http://help.sap.com/saphelp_uiaddon10/helpdata/en/cb/0ae6a170754
bb9bcfa66c4c4bdcc7/content.h tm?frameset=/en/a7/fff2179874b4a8a5b995ca55a6/frameset.htm.

Requirements

The initial setup of the SAP Fiori launchpad must be completed first.

Standard settings

This customizing activity starts the SAP Fiori launchpad designer in cross-client scope. You can adapt
these cross-client settings in each client with the customizing activity SAP Fiori Launchpad Designer
(Current Client).

SAP Fiori Launchpad Designer (Current Client)

Use

The SAP Fiori launchpad designer is an administrator tool that runs in the browser. It is used for
configuring app tiles as well as target mappings. Additionally it is used for pre-configuring the end user
home page of the SAP Fiori launchpad.

For more information, see also the documentation for the SAP Fiori launchpad designer on SAP Help
Portal at http://help.sap.com/saphelp_uiaddon10/helpdata/en/cb/0ae6a170754
bb9bcfa66c4c4bdcc7/content.h tm?frameset=/en/a7/fff2179874b4a8a5b995c a55a6/frameset.htm.

Requirements

The initial setup of the SAP Fiori launchpad must be completed first.

Standard settings

This customizing activity starts the SAP Fiori launchpad designer in the client-specific scope.
WHATSAPP +255738656506
Edit Legacy Navigation Target Configurations in LPD_CUST

Use

Define navigation targets with their technical details.

In the SAP Fiori launchpad designer you can reference a navigation target of this customizing activity
within target mappings of catalogs.
Requirements

For more information, see the documentation for setting up the SAP Fiori launchpad on SAP Help
Portal at http://help.sap.com/saphelp_uiaddon10/helpdata/en/b7/999de9e8be4fa584f9
9a108280a2/content.htm?frameset=/en/a7/fff2179874b4a8a5b995ca55a6/frameset.htm.

Prepare Backend Catalogs for Reuse

Establish RFC and HTTP Connection

Use

To integrate Web Dynpro ABAP applications and SAP GUI transactions located on a SAP Fiori back-
end server into SAP Fiori launchpad, the SAP Fiori front-end server needs to connect to this server.

The following connection types are required:

- Via RFC: This connection type is required when setting up the SAP Fiori front-end server. In this
case, the catalogs containing the applications on the back-end server are replicated to the SAP Fiori
front-end server for faster access.
- Via HTTP: This connection type is required when a Web Dynpro application or a SAP GUI
transaction is launched during runtime of the SAP Fiori launchpad.

Activities

1. Call transaction SM0 and display the content of the view /UI2/V_SYSALIAS.
2. Call transaction SM59 in a new window.
3. For each entry of the view /UI2/V_SYSALIAS, create an RFC connection with the name <system
alias>_RFC. Make sure that the connection points to the server with the correct catalogs. The
software component which needs to be installed in a backend server for a specific system alias can
be derived from the documentation of the SAP Business Suite application that you need to install.
Please check the documentation in the Fiori App Library:
https://fioriappslibrary.hana.ondemand.com/sap/fix/externalViewer
4. For each entry of the view /UI2/V_SYSALIAS, create an HTTP(S) connection with the name
<system alias>_HTTP pointing to the same system as the RFC connection in the previous step.

Note that you can reuse system alias configurations by mapping the source system alias of a
Web Dynpro ABAP application or SAP GUI transaction to a target system alias with existing RFC
connections. For more information, see
http://help.sap.com/saphelp_uiaddon20/helpdata/en/c2/4f90116e74a9bb864a001a1466
42 /content.htm
Example

There is an entry in the view /UI2/V_SYSALIAS, named FIORI_BE.

Thus, you need to create an RFC connection in transaction SM59 named FIORI_BE_RFC and an
HTTP(S) connection named FIORI_BE_HTTP.

Extract Transactions and Web Dynpro Applications

WHATSAPP +255738656506
Define Semantic Objects for Navigation

Use

This is an optional customizing activity.

Define new semantic objects that can be used in the SAP Fiori launchpad designer for creating new
navigation intents.

Standard settings

Normally you can reuse the semantic objects that were delivered by SAP (see transaction
/UI2/SEMOBJ_SAP).

If you need new semantic objects, enter them in this customizing activity. This might be necessary for
adding navigation to applications developed by you in the SAP Fiori launchpad.

For more information, see the documentation for setting up the SAP Fiori launchpad on SAP Help
Portal at http://help.sap.com/saphelp_uiaddon10/helpdata/en/60/9c84bbacb04fd8a17b
db5da742815f/content.htm?frameset=/en/a7/fff2179874b4a8a5b995ca55a6/frameset.htm.
Configure Authorization Roles

Use

The assignment of catalogs to users gives the users access to the SAP Fiori apps that are part of the
catalogs.

The assignment of groups to users gives the users a predefined set of SAP Fiori apps on their home page
in the SAP Fiori launchpad.

The assignment of authorization roles to users gives the users the permission to call the SAP Fiori apps.

Activities

Assigning catalogs and groups to roles

For more information, see the SAP Fiori launchpad documentation on SAP Help Portal at
http://help.sap.com/saphelp_uiaddon10/helpdata/en/c9/cdf5ac9617457a9be2a00a0cb5aacb/content.htm
?frameset=/en/a7/fff2179874b4a8a5b995ca55a6/frameset.htm.

Assigning authorization roles to users

For more information, see the SAP Fiori launchpad documentation on SAP Help Portal at
http://help.sap.com/saphelp_uiaddon10/helpdata/en/44/5570c460b24244bbacd962fe7126/content.ht
m?frameset=/en/a7/fff2179874b4 a8a5b995ca55a6/frameset.htm

Data Administration

Invalidate Caches

Use

This activity invalidates all server-side caches in SAP NetWeaver user interface services.

For more information, start this activity and read the documentation.

Example

We recommend to execute this activity after the import of a support package as the cached data might not
match the updated services.

Create Cleanup Jobs

Use

This activity allows you to schedule background jobs for cleaning up obsolete data.

Use report /UI2/PERS_EXPIRED_DELETE to clean up user-dependent data after the validity of this
data has expired.

Use report /UIF/CLEAN_LREP to clean up expired application states. This report is only available for
SAP NetWeaver 71.
WHATSAPP +255738656506
Activities

Create a periodic job.

1. Click on the Create cleanup jobs activity.


2. In the Job name field, enter a name for the cleanup job.
3. Choose Start condition and specify the schedule for this job. Make sure to define a periodic job.
4. Choose Step to define the steps for the job. The Create Step 1 dialog box is displayed.
5. In the ABAP program section, enter /UI2/PERS_EXPIRED_DELETE in the Name field and
choose Save.
The Step List Overview screen is displayed.

6. Choose Create to add another step.


The Create Step 2 dialog box is displayed.

7. In the ABAP program section, enter /UIF/CLEAN_LREP in the Name field and choose Save.
The Step List Overview screen is displayed.

8. Choose Back to return to the main page.


9. Choose Save to save the schedule.
10. In the main page, choose Save to save this new job.
The cleanup process will now run automatically according to the schedule you have defined.

Support Tools

SAP Fiori Launchpad Content Check Report


Use

This report is available to check the consistency of delivered and customized content created for use with
SAP Fiori launchpad.

Activities

See also
http://help.sap.com/saphelp_uiaddon10/helpdata/en/8/777b4fa29f42509186966ab81a05f /content.ht
m?frameset=/en/a7/fff2179874b4a8a5b995ca55a6/frameset.htm.

SAP Fiori Launchpad Intent Analysis

Use

Check the assignment of a given intent (semantic object - action pair) to a user in the context of SAP
Fiori launchpad.

Activities
See also http://help.sap.com/saphelp_uiaddon10/helpdata/en/51/8e6949d2f44
d51ad80f80ef0bc6ce/content.ht m?frameset=/en/a7/fff2179874b4 a8a5b995ca55a6/frameset.htm.

SAP Gateway Application Log

Use

The SAP Gateway application log can help in analyzing various error situations in both the front-end
server for SAP Fiori and the ABAP back-end server(s).

Activities

See also http://help.sap.com/saphelp_gateway20sp08/helpdata/en/64/115fe15


cc42c4ac671f9c05eb0d4/conten t.htm?frameset=/en/2e/89be0ca7454a254569cd4 a1a018/frameset.htm.

SAP Gateway Error Log

Use
The SAP Gateway error log can help in analyzing various error situations in both the front-end server for
SAP Fiori and the ABAP Fiori back-end server(s).

Activities

See also http://help.sap.com/saphelp_gateway20sp08/helpdata/en/64/115fe15


cc42c4ac671f9c05eb0d4/conten t.htm?frameset=/en/2e/89be0ca7454a254569cd4 a1a018/frameset.htm.

SAP NetWeaver Business Client

Define SAP GUI Tags (Runtime for SAP NetWeaver User Interface
Services)

Use

In this Customizing activity you can create and edit SAP GUI tags.

In SAP NetWeaver Business Client (NWBC), SAP GUI for Windows can run as the main application. In
this Customizing activity, if you mark individual fields of the SAP GUI application with tags, NWBC
exports these fields and makes them available in its side panel. The side panel can use this data to display
secondary contents (for example, statistics or notes).

Requirements

You want to program a side panel application and have read the NWBC documentation ( see section
Integrating the Context-Sensitive Side Panel).

You have selected the relevant fields in SAP GUI Property Collector and copied them to the buffer.
WHATSAPP +255738656506
Activities

Insert the properties from the buffer content into the table of this Customizing activity.

For more information, see Integrating the Context-Sensitive Side Panel.

Define Parameter Names

Use

Use this Customizing Activity to define names for configuration parameters.

Configuration parameters delivered by SAP are in maintenance view /UI2/NWBC_CFGNV. You


can look at the contents with transaction SM0 or directly with transaction /UI2/NWBC_CFG_P_SAP.

For more information, see the SAP Library for SAP NetWeaver Business Client 4 on SAP Help Portal at
http://help.sap.com.

Assign Parameter Values

Use

Use this Customizing Activity to assign values to configuration parameters.

The assignments delivered by SAP are in maintenance view /UI2/NWBC_CFGV. You can look at the
contents with transaction SM0 or directly with transaction /UI2/NWBC_CFG_SAP.

For more information, see the SAP Library for SAP NetWeaver Business Client 4 on SAP Help Portal at
http://help.sap.com.

SAP NetWeaver User Interface Services

Define Semantic Objects

Use

You can define your own semantic objects in this Customizing activity. Additionally it is
possible to overwrite the attributes of a semantic object that was delivered by SAP by defining an entry
with the same key.

Standard settings

The semantic objects delivered by SAP are available in the transaction /UI2/SEMOBJ_SAP.

Register POWL for OData Consumption

Use

In this Customizing activity you register a POWL application ID for OData consumption.

Activities

1. Register a POWL application ID.


Specify the application ID of a POWL and map it to the technical model name upon which your
service is based. The model name does not have to exist at this stage.

2. For each application ID, select the POWL queries that you would like to consume via OData.
If you do not enter a query, it is presumed to be inactive. You can also include a query in the list
and uncheck the Active indicator.

3. For each POWL query that is set to active, you have to specify a query key.
OData requires a key for each entity.

Register OData Service for UI2 Cache Usage

Use

In this activity you can register services to use the caching mechanisms provided by SAP NetWeaver
user interface services.

SAP Jam Integration

Introduction to SAP Jam Integration and Collaboration

Use
WHATSAPP +255738656506
The Social Media Integration for ABAP (ABAP SMI) provides an ABAP API that enables you to use
features from external service providers such as SAP Jam.

The API sends HTTP requests to the service provider that address the specific REST or OData services
of the provider.

Requirements

- The Customizing activities are only necessary if an application supports this type of collaboration
and you are using this application.
- To integrate SAP Jam with your SAP system, you must obtain a valid SAP Jam license. Contact
your account executive for further details.
- You must be registered as a company administrator on the SAP Jam server.
- You have maintained a unique email address for the SAP Jam users in the user master record of
your back-end system.

Standard settings

The following Customizing entries have been preconfigured by SAP and delivered as entries of tables
with delivery class S:

- View cluster CLB2VC_PTYPE: Definition of service provider types (Jam, StreamWork), and their
supported endpoints.

- View CLB2V_IC_DISP: Definition of dispatcher classes for processing the HTTP requests.

- View CLB2V_AUTH_CONT: Definition of authentication contexts. - View CLB2V_AUTH_METH:


Definition of authentication methods.

- View cluster CLB2VC_PLATF_DEF: Default servers of the service provider.

- View CLB2V_APPLI: Applications using the collaboration scenario. The default value is
DEFAULT (description: Social Media Integration for ABAP).

Activities

The following steps describe the Customizing settings that are specific for each customer system
and client and thus not preconfigured by SAP. The steps must be carried out in each client of the back-
end system as well as at the SAP Jam server.

The examples focus on connecting to SAP Jam.

Note

- Previous releases of ABAP SMI known as Social Media ABAP Integration Library (SAIL) were
delivered as part of SAP NetWeaver component SAP_BASIS. A previous release may be used in
parallel with the version shipped with the UI Add-On. The Customizing tables are different
therefore you will need to repeat the Customizing steps described in the following nodes even if the
basis settings have been provided.
- If you have an existing connection to SAP Jam established using SAIL, you can now use report
RCLB2_CUST_MIGRATE to migrate your configuration data to ABAP SMI. SAIL and ABAP
SMI belong to different SAP NetWeaver components and the respective configuration data is stored
in different Customizing tables. The report allows you to conveniently migrate your SAIL
configuration data to the relevant ABAP SMI Customizing tables. For more information, see
Migration Report for SAIL Configuration Data.
Define HTTP Service

Use

In this Customizing activity, you determine or define the appropriate HTTP service that can be used in
the communication with the external service provider.

Communication from a company network with the outside world takes places by means of an HTTP
proxy.

Activities

To maintain the appropriate HTTP service for the communication with SAP Jam, proceed as follows:

1. Run transaction SICF.

2. On the Define Services screen, choose Execute (F8) without making further specifications.
3. On the Maintain service screen, choose Client -> Proxy Settings (Ctrl+F2). The Proxy
Configuration for HTTP Client screen appears.
4. On the HTTPS Protocol tab, in the Host Name and Port fields, enter the default values that the
system uses for proxy access.
You need the values for the Host Name and Port fields later in Customizing activity Define Server
Settings.
Note:
If you use global defaults, you can leave the Host Name and Port fields empty.

5. Choose OK.

Maintain Certificate of Service Provider

Use

In this Customizing activity, you register the certificate of the service provider.

Requirements

The certificate must first be retrieved from the Web site of the service provider.

- Go to the SAP Jam web site using the browser of your choice.
- View your SSL certificate and navigate to the self-signed root certificate authority ( CA ).
- To export the certificate to a base64-encoded file, select the Base-64 encoded X09
(.CER) option as the format for the export file

Activities

WHATSAPP +255738656506
1. Choose the entry SSL client (Anonymous) by using transaction STRUST.
2. Import the certificate of the service provider to the Certificate List.

Enable SAML 2 Identity Provider

Use

In this Customizing activity, you can enable the support feature of the Security Assertion Markup
Language 2 (SAML 2).

Requirements

Transaction SAML2 must be present in your system.

Activities

1. Using transaction SAML2, enable SAML 2 support.


The default provider name is <system ID>_<client>.
Change the default by adding a company- specific prefix, for example:
<company>_<system ID>_<client>.
Register the provider name for your organization with the target platform of the external service
provider.

2. The IdP certificate can be found on the Local Provider tab; choose Metadata. In the dialog box,
select Service Provider and choose Download Metadata.
3. Open the XML file.
4. Extract and save the part that is shown in the tag < ds:X509Certificate >.

Example

Provider Name: SAP_YN_000

Prepare OAuth SHA1

Use

In this Customizing activity, you retrieve an RSA-SHA1 certificate. The authentication of calls in an
application context uses OAuth with RSA-SHA1 encryption. For authentication in SAP Jam, you also
need the RSA-SHA1 certificate.

Standard settings
The application CLBOAU has already been delivered for the Secure Store and Forward (transaction
SSFA).

Activities

1. Using transaction STRUST, choose Create in the context menu of entry SSF CLBOAU to create a
certificate in RSA-SHA1 encryption (PSE) if it is not available.
2. Double-click the Subject field of your own certificate. This shows the certificate that you can
export in base64-encoded format.

Note

If required, the standard SSF ID CLBOAU can be changed to another value in transaction
CLB2_PTYPE.

Register Application as OAuth Client

Use

In this Customizing activity, you register your application as an OAuth client in SAP Jam.

Requirements

You have Administrator privileges for your company's SAP Jam installation (for a list of company
administrators, logon to your company's SAP Jam account, click your name at the top of the page, and
select Admin from the dropdown list).

Standard settings

The SAP applications that use Social Media Integration for ABAP are already defined in view
CLB2V_APPLI. You have to repeat the activities for each application that you are using, especially for
the default application DEFAULT, in each SAP system and client that will connect to an external service
provider.

Activities

1. In the navigation bar, choose OAuth Clients.


2. Register each application that you want to use, for each SAP system and client, by choosing the link
Add OAuth Client.
We recommend choosing the name of the OAuth client following the pattern:
<company>_<system>_<client>_< application >
3. Enter the Integration URL, for example, a link to the homepage of your company or an application.
4. Enter the Security Certificate that you downloaded in the Customizing activity Retrieve
Certificate for RSA-SHA1.
Note: Make sure to remove all hard returns from the textbox: If you see a space at the end of the
line, you should remove it.

5. Save the new OAuth client.

WHATSAPP +255738656506
To get the details of the OAuth client that you just created, choose View in SAP Jam. You will receive a
consumer key that you will need in a later step.

Example

OAuth client name = SAP_YN_000_DEFAULT

Register SAML Trusted Identity Provider at SAP Jam

Use

In this Customizing activity, you register the identity provider (IdP) you defined in Customizing activity
Enable SAML 2 Identity Provider.

Requirements

- You are a company administrator.


- You have retrieved the IdP ID through Customizing activity Enable SAML 2 Identity Provider.
- You have retrieved the IdP certificate through Customizing activity Maintain Certificate of Service
Provider.

Activities

1. From the navigation bar, choose SAML Trusted IDPs.


A list of the IdPs registered for your company is displayed.

2. If the IdP ID is not listed, choose Register Your Identity Provider.


3. In the following dialog, enter the following data:
- IdP ID obtained from Customizing activity Enable SAML 2 Identity Provider
- Allowed assertion scope to Users in my company
- Certificate retrieved through Customizing activity Maintain Certificate of Service Provider
4. Choose Register.

Define Server Settings

Use

In this Customizing activity, you can enter the client-specific settings for the communication with the
service provider.
Standard settings SAP delivers

the following definitions: - Service

provider type 'Jam' and the supported

methods on this platform (view cluster

CLB2VC_PTYPE)

- Default URL of the SAP Jam server in view cluster CLB2VC_PLATF_DEF

Activities

- In view cluster CLB2VC_PLATF, choose service provider type Jam.

- For each server to which you want to connect, specify the following settings:
- Service Provider name: For SAP Jam, this must be cubetree.com.
- URL that addresses the SAP Jam data center, as provided by SAP Jam's product support
- Proxy settings (host and port) are only required for older releases, in the event of HTTP errors
(for example, ICM_HTTP_CONNECTION_FAILED).

- SSL client identity is ANONYM, corresponding to the SSL client (Anonymous) of transaction
STRUST.

- Select the Send Notifications option, if you want to distribute notifications to SAP Jam.

- Specifying a bgRFC Destination that deviates from the default IWFND_ODATA_PUSH is


optional. If you leave the field empty, the system assumes that the destination
IWFND_ODATA_PUSH exists in transaction SBGRFCCONF and that the scheduler settings
are made for this destination.
- The valid authentication method for each authentication context, for each relevant server of
SAP Jam:
APPLI (application context) OAUTH_10_SHA1
APPUSR (application context with user authentication) OAUTH_10_SHA_

USER (user context) SAML_20


NONE (no authentication) NONE
Example

For the connection to SAP Jam, the settings are as follows:


Service Provider Type: Jam
Server: Jam productive
Service Provider: cubetree.com
URL target server: Data center URL provided by SAP Jam's product support
Proxy Host: Empty (*)
Proxy Port: Empty (*)
SSL Client Identity: ANONYM
Send Notifications, bgRFC Destination,

WHATSAPP +255738656506
Gateway Destination: Not selected or empty, if you do not use the distribution of
notifications.
(*) to be specified in older releases only, in the event of HTTP errors (for example,
ICM_HTTP_CONNECTION_FAILED).

Define Application Settings

Use

In this Customizing activity, you maintain the server settings for the applications that are used.
If nothing else, you will need to maintain the default value, which is the DEFAULT application.
Although other applications may have been defined and delivered with a specific SAP release.

Standard settings

SAP predefined applications that support the collaboration tool integration in view CLBV_APPLI, and
the possible platforms in view CLB2V_PLATF_DEF.

Activities

1. For each application, assign the collaboration server that is addressed by way of REST
communication.
For example, assign Service Provider Type: Jam, and Server: Jam Productive, for productive
use of SAP Jam.

2. Next, for each assignment, configure the server settings:


- Ext. Application ID: The OAuth client registered by way of Customizing activity
Register Application as OAuth Client

- Consumer Key: The consumer key that you retrieved by way of Customizing activity
Register Application as OAuth Client

- HTTP Timeout: The timeout for HTTP requests sent to the service provider
Number greater than 0 (1,2,,...): Timeout in seconds
0: Use default timeout
-1: No timeout

Note: You can also define additional parameters in the "Extensions" folder. This section needs not to be
filled for connecting to SAP Jam, but is necessary for other target platforms that need to be addressed
via the OAuth 2 protocol.

Register OData Service

Use
The OData Service Registry is a reuse component for any application. The registry allows you to define a
subset of OData services that can be published in a given application context to external or on-demand
platforms.
You define the OData services in the application system.

Standard settings

SAP standard services may have been delivered from view cluster CLB2VC_GW_SRV_S (transaction
SE54). Check these default settings, first.

Activities

If necessary, you can register your own OData services in view cluster CLB2VC_GW_SRV_C
(Customer) as follows:

- The business object type (mandatory) and the application context (optional) determine your
business context.
- The external service name is the external name of an OData Service and includes the service
namespace. The value must correspond to an entry in Customizing (see Customizing for SAP
NetWeaver under Gateway -> OData Channel -> Administration -> General Settings ->
Activate and Maintain Services (or run transaction /IWFND/MAINT_SERVICE)).

- Enter the version of the service in the Service Version field.


- The name of the Collection or entity set within the service that corresponds to the business object
type.
- The Resource URL field contains the static part of the OData service. Adhere to the following
naming convention:
/sap/opu/odata/{NAMESPACE}/{SERVICE}
The internal URL prefix for addressing the Gateway system is added from the information that has
to be maintained (once) in the Customizing activity Server Settings in the form of the RFC
destination of the Gateway server.

- The Annotation URL field must contain the static part of the OData annotation resource that is
assigned to the specific OData service.
The field needs to be maintained only if the business objects can be rendered by the service
provider, for example, through the Thing Inspector component of SAP UI5. If the service provider
is SAP Jam, the resource URL must also be registered in your SAP Jam instance as an external
application. For more information, see the SAP Jam Administration Guide on SAP Help Portal at
http://help.sap.com/sapjam.

- In the dialog structure, under Service Providers, assign all service providers for which the service
registration is to be valid, for example, Jam.
- In the dialog structure, under Related Services, you have the option of defining a service
mapping. That is, all OData resources that are added here will be treated like the OData resource of
the corresponding root entry. The resource information from the root node will be used while
sharing information with the external service provider.
Note: If the collection name or annotation URL cannot be statically defined, you can implement BAdI
Empty Fields in OData Service Registry to determine the right values at runtime.

WHATSAPP +255738656506
Define URL Mapping

Use

To meet a requirement not to expose internal proxy host or port names outside the firewall, you must
define the mapping for the URLs that are sent as part of the notifications.

During the distribution of the notifications an implicit URL rewriting of backward references takes place,
based on table HTTPURLLOC.

Standard settings

No entries are predefined by SAP.

Activities

1. Run transaction SE16 and call up table HTTPURLLOC.

2. Maintain table HTTPURLLOC as follows:

- In the PROTOCOL field, enter the protocol that the external communication uses. For SAP
Jam, this is HTTPS. Use SSL whenever possible.
- In the FOR_DOMAIN field, enter the external representation of the URL, for example,
www.saptest.com.
- In the APPLICATN field, specify the same application ID as used in Customizing activity
Define Application Settings
- In the HOST and PORT fields, enter the internal proxy information, for example, lcfsg2hd
and 8080.
Notes:

- The HTTPURLLOC entries represent an inside to out mapping that corresponds to the outside
to in mapping at your reverse proxy or web dispatcher.
- You can also specify a default entry, with host and port set to *, if it is not possible to specify
all application servers at design time (for example, due to virtualization).
- Only links to OData resources will be converted. The program will not convert UI links, nor
parse the text segment (summary) of the notification.
- The exception handling is controlled by indicator Mapping Exception that is part of the
Define Server Settings: If the indicator is set, an exception is raised when the URL mapping is
not successful. This exception results in erroneous entries in the bgRFC queue.
Example

Specific server:
MANDT 000
SORT KEY 0004
PROTOCOL HTTPS
APPLICATN DEFAULT
FOR DOMAIN WWW.SAPTEST.COM
HOST LYXY245.WDF.SAP.CORP
PORT 8010

Default or fallback entry:


MANDT 000
SORT KEY 0005
PROTOCOL HTTPS
APPLICATN DEFAULT
FOR DOMAIN WWW.SAPTEST.COM
HOST *
PORT *
Configure REST Tunnel

Use

In this Customizing activity, you configure a REST tunnel to place indirect OData or REST calls to the
external service provider. The use of this type of indirect OData or REST call prevents cross-domain
authorization problems that occur when using direct calls.

Note:
This configuration option is currently not supported for external service providers other than SAP Jam.

ABAP SMI provides a general REST tunnel that uses the same trusted connection as the one you have
established in the Customizing steps for Server Settings and Application-Specific Server Settings. From
the application#s perspective, the tunnel is called first before SAP Jam is called - that is, it is called
indirectly.

The REST tunnel can be addressed as an ICF service using the ICF node path
sap/bc/ui2/smi/rest_tunnel/. The REST tunnel splits the URL, and uses the authentication context
specified in transaction CLB2_TUNNEL (view CLB2V_TUNNEL_C) for authentication with the service
provider. It then rebuilds the URL and forwards the OData request to the target resource in SAP Jam.
By default, tunneling is not active.

Activities

1. To check whether the ICF node sap/bc/ui2/smi/rest_tunnel/ is activated, run transaction SICF.

2. Run transaction CLB2_TUNNEL, and choose New Entries. Do one of the following:

- To activate the REST tunnel for the OData endpoint of the service metadata document,
complete the fields as follows:
Field Value
Tunnel Destination Enter Jam.
Service Provider Type Select Jam.
Application ID Select DEFAULT.
Service Root Enter api/v1/OData.
(This entry is case-sensitive.)
Resource Path Enter $metadata.
Authentication Context Select NONE (No authentication).

WHATSAPP +255738656506
- To activate the REST tunnel for the OData endpoint of SAP Jam, complete the fields as
follows:
Field Value
Tunnel Destination Enter Jam.
Service Provider Type Select Jam.
Application ID Select DEFAULT.
Service Root Enter api/v1/OData.
(This entry is case-sensitive.)
Resource Path tunnel), leave the To use the default (that is, the unrestricted REST
field empty.
Authentication Context Select USER (User context).
- To activate the REST tunnel for posting feed entries in SAP Jam, complete the fields as
follows:
Field Value
Tunnel Destination Enter Jam.
Service Provider Type Select Jam.
Application ID Select DEFAULT.
Service Root Enter api/v1/feed/post.
(This entry is case-sensitive.)
Resource Path To use the default (that is, the unrestricted REST
tunnel), leave the field empty.
Authentication Context Select USER (User context).

- To activate the REST tunnel for retrieving the single-use tokens from SAP Jam, complete the
fields as follows:

Field Value
Tunnel Destination Enter Jam.
Service Provider Type Select Jam.
Application ID Select DEFAULT.
Service Root Enter /v1/single_use_tokens.
(This entry is case-sensitive.)
Resource Path tunnel), leave the To use the default (that is, the unrestricted REST
field empty.
Authentication Context Select USER (User context).
Note:
Some services that would expose security tokens through the REST tunnel are blocked by a blacklist.
The blacklist cannot be modified.

3. Save your entries.

Example

Here is an example of a URL:

https://vmw911.wdf.sap.corp:445/sap/bc/ui2/smi/rest_tunnel/Jam/api/v1/OData/Grou
ps('ABC12')
The URL consists of the following elements:
Element Description
vmw911.wdf.sap.corp:445 Back-end host and port
sap/bc/ui2/smi/rest_tunnel ICF node path
Jam Tunnel destination
api/v1/OData Service root
Groups('ABC12') Resource path for the service
Note:
The system uses the most specific entry matching the service root and the resource path to determine the
service provider type, application ID, and authentication context.

The REST tunnel then replaces the first part of the URL (including the tunnel destination) with the
address of the service provider as specified in the server settings of ABAP SMI ( see Customizing
activity Define Server Settings).

Define Service of Provider

Use

With this Customizing activity you can register additional service APIs of the external service providers.
You then access view CLB2V_SERVICE_C.

Requirements

The registration is the prerequisite for using the ABAP OData API, as represented by class
CL_ODL_API or test report R_ODL_TEST.

Standard settings

SAP has delivered standard settings as part of view CLB2V_SERVICE_S, which you can access with
transaction CLB2_PTYPE.

Activities

You can specify any identifier in the field "OData Service".

Specify the root URL of the OData service as the service name.

Example

In view CLB2V_SERVICE_S, SAP has delivered an entry:


OData Service = DEFAULT
Service Name = api/v1/OData
Auth. Context = USER

You only have to make an additional entry in CLB2V_SERVICE_C, if you need to address a different
OData endpoint for Jam or the endpoint of a different service provider.

WHATSAPP +255738656506
Notifications

Send Notifications

Use

The following steps describe the Customizing activities that you can use to activate and send
notifications to the external service provider SAP Jam.

Requirements

You have configured the connection to SAP Jam by performing the Customizing activities under
SAP Jam Integration.
For more information, see the SAP Library for User Interface Add-On for SAP NetWeaver on SAP Help
Portal at http://help.sap.com/nw-uiaddon. Under Application Help, open SAP Library and search for
Connecting SAP Jam with ABAP SMI.

Standard settings

By default, notifications are not forwarded to external service providers, even if you already use a
connection to these platforms to call the ABAP Social Media Integration API.

Activities

To configure the Sending Notifications scenario, proceed as follows:

1. For each target server, activate the Send Notification option in Customizing activity Define Server
Settings.
Optionally, specify a separate background RFC destination to be used instead of the default value
IWFND_ODATA_PUSH.

2. Set the distribution monitor by using the Background RFC monitor in which you also configure an
inbound destination (see Customizing activity Maintain bgRFC Destination).
3. Register relevant callback services for applications, such as SAP CRM, that trigger notifications to
benefit from the OData service registry (see Customizing activity Register OData Service).
For more information, see the application-specific guides.

4. Define a URL Mapping for the OData resource links that are transferred with the notifications.
5. Activate the relevant OData services for your scenario in Customizing activity Activate OData
Service for Notifications.

6. If the notification will be triggered by a change document, in transaction SWEC, enter the event
handler (see Customizing activity Register Event Handler for Change Documents).

Note:
The notification may contain OData resource links that allow SAP Jam to retrieve more information
about the business object using SAP Gateway. For information about how to set up the connection
between SAP Jam and SAP Gateway, see the SAP Jam Developer#s Guide on SAP Help Portal
at http://help.sap.com/sapjam.
Maintain bgRFC Destination

Use

In this Customizing activity, you configure the destination for the background processing of notifications.

Activities

1. In transaction SBGRFCCONF, ensure that the inbound destination IWFND_ODATA_PUSH is


defined.
2. If necessary, create a new destination under a new name.
If you define a new inbound destination, register the new background RFC destination in view
CLB2V_PLATF for each relevant target server (see Customizing activity Define Server
Settings).

3. Enter the scheduler settings for the destination.

Activate OData Service for Notifications

Use

In this Customizing activity, you can activate OData services for which notifications are to be sent to a
collaboration platform that acts as a feed aggregator. You have to specify new entries for each OData
service for which you want to distribute notifications. If no entry exists for a service, no notifications are
sent.

You must define the notification filter. The filter restricts the number of notifications that are sent, that is,
it works as an anti-spam filter. You must explicitly specify the OData services for which notifications are
to be sent to the service provider.

The following Customizing views represent the notification filter:

- CLBV_GW_NOTIFY_S: Entries delivered by SAP

- CLBV_GW_NOTIFY_C: Customer-defined settings.

The logic that decides whether a notification is sent first checks if an entry exists in the C table for your
service provider type and OData service. If so, the S table is not taken into account. This means that
entries in the C table override the SAP default entries.

Requirements

You have activated SAP Jam as a feed aggregator in Customizing view CLB2V_PLATF.

Activities

WHATSAPP +255738656506
To activate notifications for specific OData services, proceed as follows:
1. Specify the target service provider (field Service Provider Type).
2. Enter the OData services by specifying their external and technical service names ( fields External
Service Name and Technical Service Name).
These must be the same names that have been registered on the SAP Gateway Server in
Customizing for SAP NetWeaver under Gateway -> OData Channel -> Administration -> General
Settings -> SAP NetWeaver Gateway to SAP System -> Activate and Maintain Services (transaction
/IWFND/MAINT_SERVICES).

3. In the Send Notification field, select All Notifications.

Example

Field Value
Service Provider Type SAP Jam
External Service Name ACCOUNT_CSCS
Technical Service Name /IWFND/ACCOUNT_CSCS
Send Notifications All Notifications

Register Event Handler for Change Documents

Use

You can register an event handler that is triggered by the change documents function for business
objects. This means that when a business object is changed, the system sends a notification to a target
platform, such as SAP Jam.

Requirements

You have followed the steps outlined in Send Notifications.

Standard settings

The UI add-on for SAP NetWeaver provides an implementation of Business Add-In (BAdI) Send
Gateway Notifications (CLB2_BULK_FEED_SEND)in which SAP Jam is set up as the service provider.

In addition, a default event handler function (CLB2_CD_NOTIFICATION_SEND) is delivered that can


be directly used in transaction SWEC. This function delegates to class
CL_CLB2_CD_NOTIF_PUBLISHER. If the default logic of the class is not sufficient for your
application, you can redefine the methods of this class in a sub-class. In this case, you have to copy the
function to instantiate your own class.
Activities

1. In transaction SWEC, field Event Container, enter the event handler function
CLB2_CD_NOTIFICATION_SEND, or any other function that has been specified by your
application.

2. In transaction SE16, table SWECDOBJ, ensure that the FBTYP field is set to N.
Business Add-Ins ( BAdIs )

BAdI: External ID for Backend User

Use

With this Business Add-In (BAdI), you can define the mapping from the back-end user name to an
external ID for an external service provider.

The external service provider may request an email address as a user name. This email address can be
taken from various sources: - User's data in the system

- Business Partner data


- Remote system

Standard settings

The default implementation uses the BAPI BAPI_USER_GET_DETAIL to read the email address from
the user in the back-end system.

Example

See the fallback implementation of the BAdI in class CL_CLB2_USER_MAPPING_DEFAULT.

BAdI: Fill Empty Fields of OData Service Registry

Use

You use this Business Add-In (BAdI) for a newly introduced application context (filter value) if you are
using the service registry of the ABAP Social Media Integration (ABAP SMI) but it is not possible to
statically define the collection or annotation for the specific OData service.

Requirements

- You are actively using the ABAP SMI service registry (table CLB2C_GW_SRV or
CLB2C_GW_SRV).

- Either the Collection field or the Annotation URL field is left empty for one or more entries in the
table and the application-specific context.

Example

There are two different collections that may be addressed for the service /CRMSWI01/CRMSMI_SRV/
and business object type BUS1006:

- IndividualAccountCollection - CorporateAccountCollection

WHATSAPP +255738656506
This is why the Collection field in the service registry is left empty. An implementation of the BAdI
method DETERMINE_COLLECTION must determine the right collection based on the category of a
specific business partner.

Optionally, you can implement the method DETERMINE_ANNOTATION to dynamically define the
annotations for a specific OData service. The main aspect is to dynamically influence the view of the
business object in a UI, based on criteria such as the user role.

BAdI: OData Service Mapping

Use

With this Business Add-In (BAdI), you can define service-specific methods required for successfully
mapping OData services entered in the ABAP SMI service registry (view cluster CLB2VC_GW_SRV_S
(SAP) or CLB2VC_GW_SRV_C ( Customer )).

Requirements

- You are actively using the ABAP SMI service registry for OData services.
- Note that the service registry is implicitly used by
- the subscription and notification mechanisms of ABAP SMI
- the Share feature of SAP Fiori
- You also use the service mapping function that is represented by the Related Services node of the
view clusters mentioned above.
- If you implement a service mapping, you may also require key mapping as the key property names
are different for the root service and the related service.

Standard settings

For the key mapping between two services, a fallback implementation is available that maps the key 1:1.
This means the result key will be the same as the input key.

Activities

Implement the BAdI for services that are to be mapped and for which the key cannot be passed to the
target service as is.

BAdI: Authorization Check for Subscription and Notification

Use

With this Business Add-In (BAdI), you can add a specific authorization check to the processes of
subscription and notification.

Requirements
You actively use ABAP SMI for sending notifications to an external data provider or for managing the
SAP Gateway subscriptions for these notifications.

Standard settings

The fallback class in the standard system setup does not perform a special authorization check.

Activities

You only need to implement this BAdI if you need to introduce additional checks.

Note

The interface if_clb2_notify_auth provides a constant gc_scenario for distinguishing


subscription and notification scenarios.

BAdI: Subscription Filter

Use

With this Business Add-In (BAdI), you can overwrite the standard behavior for constructing or analyzing
the filter parameter of a subscription. The BAdI provides the following methods:

- CHECK_FILTER: Compares an input filter string (as passed by the application) with the filter
parameter stored with the subscription.
Note:
CHECK_FILTER is called during the subscription as well as the notification processes of
ABAP SMI, but only if the application does not pass the filter string on its own.

- BUILD_FILTER: Builds the filter parameter for a subscription, from a list of name-value pairs
of the key elements of the application. Note:
BUILD_FILTER is only called when using class CL_CLB2_GW_SUBSCRIPTION for the
maintenance of the SAP Gateway subscriptions, and only if the application does not pass the
filter string on its own.
The filter parameter is to be used to comply with the OData.org definition of an OData query
filter (without the leading $filter).

Requirements

You actively use ABAP SMI for sending notifications to an external data provider or for managing the
SAP Gateway subscriptions for these notifications.

In this context, you need to implement or activate a new OData service where the default logic as
delivered by SAP is not sufficient.

Standard settings

Fallback class CL_CLB2_NOTIFY_SRV_DEFAULT is used if no active BAdI implementation can be


found for the specific service and application context (= filter values).

- BUILD_FILTER: Concatenates the name-value pairs of the input list following the pattern
<name[1]> eq '<value[1]>' and <name[2]> eq '<value[2]>' and ...

WHATSAPP +255738656506
- CHECK_FILTER: Assumes the same pattern for both input strings, the application filter, as well as
the subscription filter. It compares the values of all filter parameter key components with the
application filter components and returns abap_true if they are all valid.
Note:
The method is suitable for simple conditions with the eq operator, but not for complex
conditions with other operators. Especially in the case of complex filters, you need to create
your own BAdI implementation.
Activities

You can implement the BAdI in the system where the subscription or notification is triggered, or in a
remote system that can be addressed by an RFC call. The BAdI method calls are embedded into RFC
functions. The RFC destination is determined from the application context by evaluating Customizing
view CLB2V_CONTEXT.

SAP Visual Business

Maintain Application Definitions

Use

In this Customizing activity you define and assign geo-coding services, map products, map layer stacks
and applications for SAP Visual Business. Those settings are mandatory to operate SAP Visual Business.
The settings are client-independent and SAP and customer entries are separated by namespace
reservations.

The lowest level of definitions are geo-coding services and map products. Possible geo-coding services
are address search, route calculation, and reverse geo-coding (address for given geo-location). Supported
are RESTful geo-coding services, which are referred to by service URLs. With the service definition you
also need to specify an ABAP class, implementing interface IF_VBI_GEOCODING_SERVICE, which
is capable of parsing the service response.

A map product is a technical description of a map service, which delivers a map in tiles (images) or as a
single image. Typically a map product provides multiple levels of detail, where each level consists of
multiple tiles. For each map product at least one service URL needs to be given. Multiple URLs can be
provided for distributing the requests among multiple servers. Also the map service is expected to be
RESTful.

The next definition level are map layer stacks. Each stack consists of at least one map product. Multiple
map products can be assigned to one stack in a given order and opacity in order to combine them, for
example, combine a satellite map with a road map as overlay. Note: The projection of all map products
combined in a map layer stack must be the same!

Finally, the multiple map layer stacks can be assigned to an application. One of them needs to be defined
as default stack. Further, the application holds definitions for the behavior and appearance of the
navigation and toolbar control. Further an application might refer to a geo-coding service definition.
Finally the Visual Frame definitions allow you to restrict the application to a certain part of the map.

It is also valid to assign no map layer stack to the application. In this case the application will show a
plain D scene.
Standard settings
The SAP delivered settings can be used for demo purposes only. For a productive use geo-coding
services and map products need to be licensed from a service provider.

Activities

You can define your own SAP Visual Business application. Depending on the use of SAP Visual
Business you can provide them using configuration to the WebDynpro Reuse Component or the FPM
GUIBB for SAP Visual Business. In your own application you provide the application ID to the
application class CL_VBI_APPLICATION.

Overwrite Map Server Default URLs

Use

In this Customizing activity, you can overwrite the map server default URLs assigned to a SAP delivered
map products. The map products are used by the SAP Visual Business browser plug-in.

Requirements

You can only overwrite URLs of existing map products.

Standard settings

For test purposes you can run SAP Visual Business with the SAP delivered URLs.

Activities

The map product URLs contain a token, app ID, or something equivalent, which identifies the service
consumer at the map provider. For a productive use you need to license the map product of your choice.
With the license agreement you get your own token. In order to use this you have to overwrite the default
URLs.

Overwrite Geo-Coding Service Default URLs


Use

In this Customizing activity, you can overwrite the geo-coding service default URLs assigned to a SAP
delivered service. The geo-coding services are used by the SAP Visual Business browser plug-in.

Requirements

You can only overwrite URLs of existing geo-coding services.

Standard settings

For test purposes you can run SAP Visual Business with the SAP delivered URLs.

WHATSAPP +255738656506
Activities

The geo-coding service URLs contain a token, which identifies the service consumer at the service
provider. For a productive use you need to license the geo-coding service, usually together with a map
product, of your choice. With the license agreement you get your own token. In order to use this you
have to overwrite the default URLs.

Define Application Replacements

Use

In this Customizing activity, you can replace the definitions for a Visual Business Application by the
definitions for a different one. This provides an easy possibility to change the definitions made in SAP
delivered Visual Business applications. Just copy the SAP delivered application, change it according to
your needs, and make a replacement entry that the original application should be replace by your copy.

Requirements

You can only use existing applications as replacing and replaced application.

Standard settings

No entries required

Activities

Enter the application you want to replace and the one which should be used instead.
Example

You copied the demo application GEOMAP_DEMO to your own version ZGEOMAP_DEMO and
adapted it to your needs. In order to use your definitions in all places where GEOMAP_DEMO is used
you enter an entry:

Application: GEOMAP_DEMO Replacement: ZGEOMAP_DEMO

UI Theme Designer

Use Custom Themes

Activate SICF service for using custom themes

Use

To use custom themes with SAP application the SICF nodes /sap/public/bc/themes
needs to be activated.
Activities

Launch the activity and enter the term "/UI5/THEMES" and execute.

Maintain Custom Themes

Activate SICF services for UI theme designer

Use
To maintain custom themes the following SICF nodes needs to be activated:

- /sap/public/bc/themes
- /sap/bc/theming

Activities

Launch the activity and enter the term "/UI5/THEME_DESIGNER" and


execute.

ACF: Create Whitelist

Use

As rendered pages are usually displayed in Web Dynpro in a Web browser that is connected to the
Internet, security must be taken into account in active UI elements, such as AcfExecute and
AcfUpDownload:

- The active UI elements communicate only with authorized servers.


- Only authorized executables with specified signatures run on the client PC when using
AcfExecut.

- Data can only be stored in authorized directories.

WHATSAPP +255738656506
- Data can only be read from authorized directories.
The authorized servers and directories are in a white list, that is, an administrator has stored this
information locally (transaction WDR_ACF_WLIST). If requests for access to directories or
communication with servers are sent using HTTP or HTTPS, the control first checks whether this is
allowed at all.

The white list is passed, signed and decoded, automatically in each round-trip.

The administrator creates the public key required for decoding. The SAP GUI installation can distribute
it to the necessary subsequent systems.
The white list can only be maintained in its original system. An administrator must transport it from the
original system into all subsequent systems.

Requirements

Prerequisite for the white list is the installation of SAPCRYPTOLIB.

Activities

1. Execute the activity.


2. Choose Change.
3. Choose New Entries.
4. Enter a name and short description for your new white list.
5. Make the settings for your application:

- For AcfExecute make your settings under Application.


Specify the allowed application, the application path, and any parameters.

- ForAcfUpDownload make your settings under Download (Server -> Directory) or Upload
(Directory -> Server)
Enter the file storage path and type, i.e. server or directory. Specify the HTTP server and port
that you specified in the transaction CSADMIN to specify the directories for the upload and
download.

6. Save your entries.


7. Go back to the initial screen.
8. Select your white list and choose Install Certificate to create the certificate that you need to decode
your white list.
Choose Download Certificate to use a certificate that is already locally on your PC for the
automatic installation.
The system creates a white list with the name SAPFrontendService<original system
name><GUID>.p12.
You can display the XML file with Display .

Paths

For directories:

- If the path points to a file, the file is released.


- If the path points to a directory, the directory and all its subdirectories are released (whether or not
the path ends with a/ ).

Directories and Applications

The following also applies:


- $TEMP points to System.getProperty("java.io.tmpdir"). Example:
$TEMP/foo.txt allows access to C:\Documents and Settings\<user>\Local
Settings\Temp\foo.txt.

- Analogously$HOME points toSystem.getProperty("user.home").


The system allows the user access to C:\Documents and Settings\<user>.
- You can access environment variables between dollar signs.
Example: $windir$/system2: can access all files below C:\WINDOWS\system2.

Note that for reasons of security, abbreviations such as $HOME are not supported during the Microsoft
Project Integration.

Server URLs

You can release entire domains by beginning your settings with *..
Example: *.wdf.sap.corp: releases all servers in the domain wdf.sap.corp.

If no log is specified, HTTP:// is used automatically.

Example

<?xml version="1" encoding="utf-8"?>


<frontendServices version="7">
<execute>
<extension>doc</extension>
<extension>jpeg</extension>
<extension>jpg</extension>
<extension>png</extension>
<extension>txt</extension>
<application path="$windir$/system2/mspaint.exe">
<parameter position="01" type="STRING">
<legalValue>*.txt</legalValue>
</parameter>
</application>
<application path="$windir$/system2/notepad.exe">
<parameter position="01" type="STRING">
<legalValue>*.asc</legalValue>
<legalValue>*.txt</legalValue>
</parameter>
<parameter position="02" type="STRING">
<illegalValue>&amp;*</illegalValue>
</parameter>
</application>
WHATSAPP +255738656506
<application path="$ProgramFiles$/Microsoft
Office/Office12/WINWORD.EXE">
<parameter position="01" type="STRING">
<legalValue>*.txt</legalValue>
</parameter>
</application>
</execute>
<download>
<directory>c:\temp</directory>
<directory>c:\temp\download< /directory >
<server>http://10207:1090</server>
<server>http://pwdf0652.wdf.sap.corp:1090</server>
<server>http://pwdf2625.wdf.sap.corp:1090</server>
<server>http://pwdf2625:1090</server>
</download>
<upload>
<directory>$HOME/SAPWORKDIR< /directory >
<server>*.WDF.SAP.CORP</server>
<directory>C:\temp</directory>
<directory>c:\temp\upload</directory>
<server>http://10207:1090</server>
<server>http://pwdf0652.wdf.sap.corp:1090</server>
<server>http://pwdf2625.wdf.sap.corp:1090</server>
<server>http://pwdf2625:1090</server>
</upload>
< /frontendServices >

Notes

For more information about Web Dynpro, see the SAP Library for SAP NetWeaver on the
SAP Help Portal at http://help.sap.com/nw_platform under UI Technologies in SAP NetWeaver.

ACF: Create Certificate

Use

This transaction is used to create a certificate.

Note on creating a certificate:


If the old certificate has been overwritten, the new certificate must also be distributed to the end users.

For more information, see the detailed documentation about working with whitelists in the SAP Help
Portal.
Floorplan Manager

Activate ICF Services for FPM Applications

Use

Before you execute and use Floorplan Manager (FPM) applications, you must activate the corresponding
ICF services.

With this customizing activity, you can activate the following:

1)ICF services for FPM service applications (FPM Workbench, Application Creation Tool (ACT), CBA
Enabler, Hierarchy Browser, and Message Mapper)
2)ICF services for FPM test applications (FPM Test Suite and all assigned FPM test applications)

Requirements

Ensure that you have activated the ICF services of all relevant WD ABAP applications, see SAP Note
#1088717.

Activities

Execute this customizing activity to ensure that the relevant ICF services are active. You can then run the
above-mentioned FPM applications.

Context Based Adaptations ( CBAs )

Define Schemas

Use

With context-based adaptations (CBA), an FPM application can be adapted dependent on specific
runtime parameters. A particular adaptation is applied when the application is called within a specified
context (a context being, for example, the role of the person who launches the application).

Before you start to work with CBAs, you need to create or use an existing schema.

A schema is a list of characteristics (or dimensions) that can be used for adaptations, for example a role
or country. Adaptation schemas relate to a whole application area; it is not necessary to create a separate
schema for each application
Activities

Start this customizing activity to create a new schema or check which schemas already exist.

Define Dimensions

Use

WHATSAPP +255738656506
With context-based adaptations (CBA), an FPM application can be adapted dependent on specific
runtime parameters. A particular adaptation is applied when the application is called within a specified
context (a context being, for example, the role of the person who launches the application).

A dimension represents an individual characteristic within an adaptation schema. It is maintained in


transaction SM0 view FPM_V_ADAPT_DIM. Examples of adaptation dimensions include role and
country. A dimension is defined by the following attributes:

# Name: For identification purposes.

# Index: Used to determine the dominating adaptation dimension in case there is a collision.

# Data element: Used only at design time, allowing the provision of field helps and F4 helps.

The adaptation dimensions that are used in an adaptable application are found on the Parameters page of
the application in transaction SE80.

Requirements

To create dimensions, you should create a schema beforehand.

Activities

Start this customizing activity to create new dimensions for a schema.

Message Settings

Define FPM Message Mapping

Use

Messages that are displayed by the system often contain technical terms which might not be understood
by everyone working with the system.

Message Mapper is used to map messages (error messages, warning messages, and information/success
messages) currently displayed by the system to a more understandable, user-friendly form.

Define FPM Message Categories

Use

Within this maintenance view, you can define new message categories for FPM applications. You can
group messages into categories.

Customers cannot delete categories created by SAP applications but they can add new entries based on
their own requirements.

You can use categories to specify, for example, the following items: roles such as Administrator,
Manager, and Employee; technical groups such as an No Authorization group; functional groups such as
an SRM Shopping Cart Customizing group.
Set-Up Printing for Web Dynpro ABAP ALV System-Wide

Create RFC Destination in AS Java

Use

The Web Dynpro ABAP ALV creates a PDF version of the table, optimized for printing. To be able to
create a print version from the WD ABAP ALV, the print service must be made available werden on a
Java application server, with Usage Type Installation.

NOTE: For more information, see SAP Note 14198.

If you have no AS Java, you can deactivate print version display, centrally. See: Maintain Web Dynpro
ABAP-Specific Settings.

Activities

To generate the PDF version, you need a connection between the AS ABAP on which your Web-Dynpro
applications run, and the AS Java. Maintain the destinations in both systems:

1. Create RFC destination in AS Java


To be able to use the RFC connection to AS Java, in the ABAP system, the destination
must exist in the AS Java. Proceed as follows, depending on the AS Java release:

- Up to SAP NetWeaver 70, 71 or 72 (including SPs):


See the section below: Create RFC destination in AS Java (in Visual Administrator)
- From 7 (including SPs)
See the section below: Create RFC destination in AS Java (in SAP NetWeaver
Administrator)
2. Create RFC Destination in AS ABAP (transaction SM59)
You have instantiated an RFC server in the AS Java, in which you can now register as RFC client
in AS ABAP, in step 1. Do this by creating an RFC connection.

3. Set up Web service destination for the Adobe Document Services


Adobe Document Services (ADS) requires an additional connection between the AS Java and the
AS JAVA on which ADS runs.

Create RFC destination in AS Java (in Visual Administrator)


To create an RFC destination in the in AS Java:

1. Open the Visual Administrator. Choose:


- under Windows, the directory <drive>:\usr\sap\<SID>\JC<INSTANCE>\ j2ee\admin
- under Unix the directory /usr/sap/<SID>/JC<INSTANCE>/j2ee/admin. Double-click on the
file go.bat.
2. In the Visual Administrator logon screen, choose a connection, and choose Connect.

WHATSAPP +255738656506
3. Enter the password for the connection. You are now connected to the Visual Administrator.
4. In the directory, choose <SID>/server<#>/services/Jco RFC provider.
5. Update an RFC destination:
- Program ID: <JAVA_HOSTNAME>_ALV_<ABAP_SID>
Enter a unique program ID. The program ID should contain the name of the ABAP and Java
servers, and be used only to create the print version.

- Gateway host: < GATEWAY_HOST >


Enter the AS ABAP gateway on which your Web-Dynpro applications run.

- Gateway service: sapgw< SYSTEM_NUMBER >


- Number of processes (1): 20
- Application server host: AS ABAP
- System number: < SYSTEM_NUMBER >
- Client: < CLIENT >
- Language: EN
- User: < USER >
(user in application system with authorization S_RFC)
- Password: < PASSWORD >
6. Copy the RFC destination to the available RFC destinations with Set.
7. Start the RFC Server using Start.

Create RFC destination in AS Java (in SAP NetWeaver Administrator)


To create an JCo RFC destination in the in AS Java:

1. Call the SAP NetWeaver Administrator with http://<Server>:<Port>/nwa. <Server> is the AS


Java in which the SAP NetWeaver Administrator is installed, and <Port> is the HTTP port of AS
Java.
2. Choose Configuration Management -> Infrastructure -> JCo RFC Provider. You go to the
JCo RFC destination maintenance.
3. Choose Create.
4. Enter the server configuration data in step 1:
- Program ID: <JAVA_HOSTNAME>_ALV_<ABAP_SID>
Enter a unique program ID. The program ID should contain the name of the ABAP and Java
servers, and be used only to create the print version.

- Gateway host: < GATEWAY_HOST >


Enter the AS ABAP gateway on which your Web-Dynpro applications run.

- Gateway service: sapgw< SYSTEM_NUMBER >


- Number of servers (1): 20
5. Enter the repository configuration data in step 2:
- Application server host: AS ABAP
- System number: < SYSTEM_NUMBER >
- Client: < CLIENT >
- User: <USER> (user in application system with authorization S_RFC)
- Password: < PASSWORD >
- Language: EN
6. Enter the security setting data in step .
You can use Secure Network Connection (SNC), and enter its data.

7. Enter other options in step 4.


You can specify the instance for the servers, and whether RFC traces are to be recorded.

8. Choose Complete, to confirm your entries.


The destination now appears in the initial screen in the table, with the status Running.

Create RFC Destination in AS ABAP

Use

The Web Dynpro ABAP ALV creates a PDF version of the table, optimized for printing. To be able to
create a print version from the WD ABAP ALV, the print service must be made available werden on a
Java application server, with Usage Type Installation.

If you have no AS Java, you can deactivate print version display, centrally. See:Maintain Web Dynpro
ABAP-Specific Settings.

Requirements

To generate the PDF version, you need a connection between the AS ABAP on which your Web-Dynpro
applications run, and the AS Java. Maintain the destinations in both systems. To be able to use the RFC
connection to AS Java, in the ABAP system, the destination must exist in the AS Java.

- Create RFC destination in AS Java

Standard settings

Activities

To create an RFC connection from the AS ABAP to the AS Java, perform the following steps:

1. Start the transaction Configure RFC Connections (transaction code SM59).


2. Choose Create.
3. Maintain the RFC destination:
- RFC destination: SALV_WD_EXPORT_PDF
- Connection Type: T
(for TCP/IP connection)

- Description: < DESCRIPTION >


Entries in tab Technical Settings:
- Activation Type: Registered server program
WHATSAPP +255738656506
- Screen: <JAVA_HOSTNAME>_ALV_<ABAP_SID>
Specify the same program ID as used in the AS Java.

- Gateway host: < GATEWAY_HOST >


Specify the AS ABAP gateway.
Important: This must be the same as in the JCo RFC provider in AS Java.

- Gateway service: sapgw< SYSTEM_NUMBER >


4. Click on the connection test to check your data.
5. To check that the connection is to the correct system, choose: Extras -> System Information ->
Target System, and check the field System ID.

Set-Up Web Service Destination for Adobe Document Services

Use

If you use Adobe Document Services (ADS) to create the PDF document for the print version, maintain
an additional web service destination.

Requirements

- ADS must be installed and configured


- The AS ABAP on which the WebDynpro applications runs, must be connected to an AS Java with a
print service:
- Create RFC destination in AS Java
- Create RFC destination in AS ABAP
- The ADS user for secure communication with the AS Java in which the Adobe Document Services
are installed, has been created.

Activities

Proceed as follows, depending on the AS Java release:

- Up to SAP NetWeaver 70, 71 or 72 (including SPs):


See the section below: Set up Web service destination for the Adobe Document Services
(in Visual Administrator)
- From 7 (including SPs)
See the section below: Set up Web service destination for the Adobe Document Services
(in SAP NetWeaver Administrator)

Set up Web service destination for the Adobe Document Services (in Visual
Administrator)
To set-up the web service destination for communication with the Adobe Document Services:

1. Open the Visual Administrator. Choose:


- under Windows, the directory
<drive>:\usr\sap\<SID>\JC<INSTANCE>\j2ee\admin
- under Unix the directory /usr/sap/<SID>/JC<INSTANCE>/j2ee/admin. Double-click on the
file go.bat.
2. In the Visual Administrator logon screen, choose a connection, and choose Connect.
3. Enter the password for the connection. You are now connected to the Visual Administrator.
4. Go to the directory Server -> Services -> Web Services Security -> Web Service
Clients -> sap.com -> tc~wd~pdfobject ->
com.sap.tc.webdynpro.adsproxy.AdsProxy*ConfigPort_Document.
5. To change the default URL
http://localhost:50000/AdobeDocumentServices/Config?style=document, choose Custom in the
drop-down box next to the text URL, for the destination URL.
6. Replace the string localhost:50000 with the host name and port number < host name>:<port
number> of the Adobe Document Services.
7. Specify the user name and password. It must be a technical Adobe user which you created when
configuring ADS.
8. Save your entries.
9. To pass the changed data to AS Java, go to Services -> Deploy.
10. Choose Application.
11. Choose sap.com/tc~wd~pdfobject.
12. To stop the application, choose Stop Application.
13. Then, choose Start Application.

Set up Web service destination for the Adobe Document Services (in SAP
NetWeaver Administrator)
To set up the web service destination for communication with the Adobe Document Services:

1. Call the SAP NetWeaver Administrator with http://<server>:<port>/nwa. <Server> is the AS Java
in which the SAP NetWeaver Administrator is installed, and <port> is the HTTP port of AS Java.
2. Choose SOA Management -> Technical Configuration -> Destination Template Management.
3. Choose Create Destination.
4. Choose Destination Type WSIL.
5. Enter ConfigPort_Document as Destination Name. The name is case-sensitive.
6. Enter URL http://<server>:<port>/inspection.wsil .
<server> is the AS Java in which the Adobe Document Services are installed, and <port> is the
HTTP port of the AS Java.

7. In the Security tab, in the Authentification group, choose HTTP Authentication, and select User
ID/Password (Basic).
8. Choose Details, and enter User ID ADSUser. Enter the password that you created when
configuring Adobe Document Services for the ADSUser, and confirm.
9. Save your entries.
The destination now appears in the initial screen of the destination Template Management.
WHATSAPP +255738656506
Edit Web Dynpro ABAP-Specific Settings

Use

This activity makes various client-specific settings for the Web Dynpro ABAP ALV. You can make
settings for:

Allow export function BEx Analyzer


This entry activates and deactivates the BEx Analyzer function in the Web Dynpro ABAP ALV toolbar
export function selection list. Only deactivate this function if you have an SAP NetWeaver application
server with Usage Type BI Java.

Whether the export functionBEx Analyzer can be set depends on the application. If it can, it is hidden by
default.

Allow Crystal Reports


This entry controls centrally whether Crystal reporting is to be possible. If so, the end user can display
the data in ALV as a Crystal Report.

Note:
This requires a special viewer in the frontend. This setting is only meaningful if this viewer has been
installed. See SAP Note 15044 (https://service.sap.com/sap/support/notes/15044)

Java Server available


With this entry, you can deactivate Java-dependent functions in the ALV abschalten. This is useful if you
have no Java server. If you have no Java server, certain functions are not available:

- Print and print settings


- Business graphic display
- In information broadcasting: distribution in the Portal, print, send in pdf format If you specify that
there is no Java server, these functions are hidden.
Service to generate the print version
This entry selects the service to generate the PDF. You have two options:

- ADS ( default )
Generation with Adobe Document Services.

- SAP
Generation with SAP BI Export Library. This is in Usage Type BI Java from 72, and in Usage
Type PDF Export from 70.

If the application is in barrier-free mode, the setting SAP is selected automatically, because it provides
the data which the screen reader requires.
You must perform further configuration steps to create the print version in your system, see: Set Up
Printing for Web Dynpro ABAP ALV.

Standard export format


Specify the default data export format.
Edit SAP GUI-Specific Settings

Use

This activity makes client-specific settings for the SAP List Viewer for SAP GUI.

Allow Crystal Reports


This entry controls whether Crystal Reports are to be active. If so, the end user can display the data in
ALV as a Crystal Report.

Note:
This requires a special viewer in the frontend. This setting is only meaningful if this viewer has been
installed. See SAP Note 15044 (https://service.sap.com/sap/support/notes/15044).

Allow user to select spreadsheet format


This flag allows the user to select the spreadsheet format. You can specify a default format.

Default spreadsheet format


Default spreadsheet format.

Manage Generic Crystal Reports

Use

This application uploads user generic crystal report layouts, downloads or deletes existing layouts, and
specifies the system-wide default layout.

WHATSAPP +255738656506