FND – 62 – Create outbound destination for content publisher

The configuration steps to be executed on the HUB system (FND) are detailed at SAP Help.

  1. Maintaining Inbound bgRFC Queue on the Hub System SAP Help
  2. Create outbound destination for content publisher SAP Help

This document explains how to execute step 2.

When a mobile user subscripes for push notification, he/she basically informs SAP Gateway to receive updates on a collection. As Gateway handles subscriptions in a pretty abstract way, the user needs to inform some information during the subscription process. One of these informations is the communication channel. This channel corresponds to a HTTP destination created at the HUB system.
SAP Help

A user subscribing will pass the following channel information to Gateway: urn:sap-com:channel:<CHANNEL_NAME>/<unique_ID_of_device

The first part (urn:sap-com:channel) is used by OData as a keyword to filter and extract the name of the channel. The channel name is a HTTP destination created in SM59. I’ll use SMP_PUSH. This implies that you can have several push destinations for a single SAP Gateway system.

No SPRO activity

All activities are done on the SAP Gateway HUB (FND) system.

  1. Create HTTP Destination
  2. Transaction SM59


  3. New Destination


  • RFC Destination: SMP_PUSH
  • Connection Type: G


  1. Go to tab “Technical Settings”
  • Target host: Host of SMP 3 (smp3.tobias.de)
  • Service No: HTTP Port of SMP 3 (8080, depends on your configuration)
  • Path Prefix: Prefix used by SMP 3 for push notifications (/Notification/)


  1. Go to tab “Logon & Security


  • User: SMP Push user (smppush)
  • Password: password of SMP Push user
  1. Save
  2. Test destination

FND – 42 – Define trust between SAP Gateway and SAP backend

The configuration steps to be executed on the HUB system (FND) are detailed at SAP Help. The steps are for the OData Channel Service for backend system.

  1. Basic configuration activities: SAP Help
    • Set profile parameters to support SSO2 SAP Help
    • Activate ICF Services SAP Help
  2. User & Authorization SAP Help
  3. SAP Gateway to Consumer (FND to SMP3) SAP Help
    1. Creating a bgRFC destination for outbound queues SAP Help
    2. Registering bgRFC destination for the oubound queue SAP Help
    3. Creating bgRFC supervisor destination SAP Help
  4. SAP Gateway to SAP Backend (FND to BEP) SAP Help
    1. Create RFC on SAP Gateway (FND) to SAP backend (BEP) SAP Help
    2. Define trust between SAP Gateway and SAP backend (FND <-> BEP) SAP Help
    3. Configure SAP backend system (BEP) to accept assertion ticket from SAP Gateway SAP Help
    4. Configure SAP Gateway (FND) to accept assertion ticket from SAP backend (BEP) SAP Help
    5. Configure SAP system alias for applications SAP Help
  5. Activate SAP NetWeaver Gateway SAP Help

This document explains how to execute step 4.2.

A trust relationship between IWFND and BEP is needed to allow for SSO.
SAP Help

No SPRO activity.

Transaction SMT1


Trust relationship wizard opens


Inform a RFC destination: ECCCLNT001 (created in previous step)


Click continue. Basic connection checks are done

Continue

Continue

Complete

FND – 41 -Create RFC on SAP Gateway (FND) to SAP backend (BEP)

The configuration steps to be executed on the HUB system (FND) are detailed at SAP Help. The steps are for the OData Channel Service for backend system.

  1. Basic configuration activities: SAP Help
    • Set profile parameters to support SSO2 SAP Help
    • Activate ICF Services SAP Help
  2. User & Authorization SAP Help
  3. SAP Gateway to Consumer (FND to SMP3) SAP Help
    1. Creating a bgRFC destination for outbound queues SAP Help
    2. Registering bgRFC destination for the oubound queue SAP Help
    3. Creating bgRFC supervisor destination SAP Help
  4. SAP Gateway to SAP Backend (FND to BEP) SAP Help
    1. Create RFC on SAP Gateway (FND) to SAP backend (BEP) SAP Help
    2. Define trust between SAP Gateway and SAP backend (FND <-> BEP) SAP Help
    3. Configure SAP backend system (BEP) to accept assertion ticket from SAP Gateway SAP Help
    4. Configure SAP Gateway (FND) to accept assertion ticket from SAP backend (BEP) SAP Help
    5. Configure SAP system alias for applications SAP Help
  5. Activate SAP NetWeaver Gateway SAP Help

This document explains how to execute step 4.1.

A RFC connection between SAP Gateway HUB and SAP backend is needed so that the HUB system can communicate with BEP. Without this, the OData services exposed at Gateway won’t work, as they cannot map the services (BAPIs) to a backend.
SAP Help

SPRO: SAP Reference IMG and navigate to:  SAP NetWeaver Gateway OData Channel Configuration Connection Settings SAP NetWeaver Gateway to SAP System Manage RFC Destinations

This open transaction SM59

  • Create

  • Give a name for the RFC destination, like <SID>CLNT<Client>
  • RFC Destination: ECCCLNT001 (example)
  • Connection type: 3
  • Inform a description
  • Go to tab “Technical Settings
    • Load balancing: Yes or No, depending on landscape
    • Target host: host name of SAP backend (BEP) system
    • System number: system number of SAP backend (BEP) system

  • Go to tab “Logon & Security
    • Client: cliente of BEP system
    • Current User: Yes
    • Trust Relationship: Yes


  • Go to tab “Special Options
    • Transfer Protocol: Classic with tRFC


  • Save

FND – 32 – Registering bgRFC destination for the oubound queue

The configuration steps to be executed on the HUB system (FND) are detailed at SAP Help. The steps are for the OData Channel Service for backend system.

  1. Basic configuration activities: SAP Help
    • Set profile parameters to support SSO2 SAP Help
    • Activate ICF Services SAP Help
  2. User & Authorization SAP Help
  3. SAP Gateway to Consumer (FND to SMP3) SAP Help
    1. Creating a bgRFC destination for outbound queues SAP Help
    2. Registering bgRFC destination for the oubound queue SAP Help
    3. Creating bgRFC supervisor destination SAP Help
  4. SAP Gateway to SAP Backend (FND to BEP) SAP Help
    1. Create RFC on SAP Gateway (FND) to SAP backend (BEP) SAP Help
    2. Define trust between SAP Gateway and SAP backend (FND <-> BEP) SAP Help
    3. Configure SAP backend system (BEP) to accept assertion ticket from SAP Gateway SAP Help
    4. Configure SAP Gateway (FND) to accept assertion ticket from SAP backend (BEP) SAP Help
    5. Configure SAP system alias for applications SAP Help
  5. Activate SAP NetWeaver Gateway SAP Help

This document explains how to execute step 3.2.

“Register the bgRFC destination for the outbound queue to handle communications efficiently.” SAP Help

SPRO: SAP Reference IMG and navigate to:  SAP NetWeaver Gateway OData Channel Configuration Connection Settings SAP NetWeaver Gateway to Consumer Register RFC Destination for Outbound Queues

This opens transactoin SBGRCCONF

  1. Select tab “Define Inbound Dest.
  2. Select “Create


     

  • Inb. Dest. Name: IWFND_BGRFC_DEST
  1. Save
  2. Enter a new prefix


  • Prefix: IWFND_CNP 
  • Prefix: IWCNT_WF


  1. Save
  2. Navigate to tab “Schedulor: Destination


  3. Create


  • Type: Inbound


  • Destination: IWFND_BGRFC_DEST 
  1. Save

BEP – 2 – Defining a Remote Function Call to SAP NetWeaver Gateway

The configuration steps to be executed on the backend (BEP) are detailed at SAP Help. The steps are for the OData Channel Service for backend system.

  1. Settings for Idempotent services Blog SAP Help
  2. Defining a remote function call to SAP Gateway SAP Help
  3. Connection settings to SAP Gateway Blog SAP Help
  4. Configure bgRFC supervisor destination Blog SAP Help

This document explains how to execute step 2.

“You create or define a background remote function call (bgRFC) destination, which is used for communications in an outbound queue, and an inbound queue among SAP systems.”
SAP Help

Important: “If you are using push from an SAP Business Suite backend system to an SAP NetWeaver Gateway hub system, it is important not to have a trusted RFC connection.”

SPRO: SAP Reference IMG and navigate to  SAP NetWeaver Gateway Service Enablement Backend OData Channel Connection Settings to SAP NetWeaver Gateway Create RFC Destination for Outbound Queues

This open transaction SM59.

  1. Click Create.


  1. Give a name for the RFC destination, like BEP_BGRFC_DEST
  • Connection type: 3
  • Inform a description
  1. Go to tab “Technical Settings
  • Target host: host name of SAP Gateway system
  • System number: system number of SAP Gateway system


  1. Go to tab “Logon & Security
  • Enter the logon data for the technical user
  • Trust Relationship: No


  1. Go to tab “Special Options
  • Transfer Protocol: Classic with bgRFC


  1. Save
  2. Test the connection.