Technology Blogs by SAP
Learn how to extend and personalize SAP applications. Follow the SAP technology blog for insights into SAP BTP, ABAP, SAP Analytics Cloud, SAP HANA, and more.
cancel
Showing results for 
Search instead for 
Did you mean: 
kenichi_unnai
Advisor
Advisor

This is a part of the implementation details of How To... Implement End-to-End Push Notifications with HCPms and SAP Gateway.


Implementation Plan

Working with SAP Gateway Hub. Major to-do thing here is to configure the bgRFC (Background RFC) to create a queue for push messages. If you don't need ERP backend access, you can implement OData services in the Hub system. The OData service must be implemented as "subscribable".


Steps to Implement


1. Import Root CA Certificate from HCPms to SAP Gateway system

2. Configure HTTP Destination to HCPms

3. Configure bgRFC

1. Import Root CA Certificate from HCPms to SAP Gateway system


As HCPms requires SSL, we need to import the Root Certificate into SAP Gateway Hub system. Open your HCPms URL in the browser (Firefox is recommended to export the Root Certificate).

Click on the lock icon left side of the URL. Click on More Information.

In the popup, select Security tab and click View Certificate.

Select Details and choose your root certificate. Press "Export" and save the cert file on the disk (the format doesn't really matter - choose the default PEM format).

In the Gateway Hub box, run the transaction code STRUST. Select "SSL client SSL Client (Anonymo" as shown.

Find and click the small icon for Import certificate. Select the Root Certificate file just downloaded.

Click on "Add to Certificate List". (If you see the button is not activated, make sure your screen is in edit mode).

Be sure to save the imported Root Certificate file by pressing the Save icon.


2. Configure HTTP Destination to HCPms


Now we're going to configure the HTTP connection between SAP Gateway Hub and HCPms. Run the transaction code SM59. Create a new entry with the Connection Type = G (HTTP connection). Type the Target Host for your HCPms instance server name with the port# 443. Enter the Path Prefix /Notification/ .


In addition to it, supply the http proxy server information so that SAP Gateway Hub can go through the proxy to the HCPms server.

Switch to the tab Logon & Security. Enter your HCPms account credential.

Scroll down - and select SSL = Active, SSL Certificate = ANONYM SSL CLIENT (Anonymous). This ensures the connection will use the Root Certificate you had imported.

After saving the configuration, press the connection test button. It should return "405 Method Not Allowed". This is the expected result.


3. Configure bgRFC


Let's create a bgRFC configuration. We need to do this step to create a push message queue for HCPms.


Run the transaction code SBGRFCCONF. First thing is -


a. Define Supervisor Destination


(Note - formal help document: Configure the bgRFC Supervisor Destination - SAP NetWeaver Gateway - SAP Library)


Click on the Define Supervisor Destination tab. Here you need to define Supervisor Destination, a kind of the system user setting. Click on the Create icon and name your Supervisor Destination = BGRFC_SUPERVISOR.

Enter the Destination Name and select Create User with the User Name = BGRFCSUPER (actually, the name can be anything). As the formal help document states, this user needs a SAP Role "SAP_BC_BGRFC_SUPERVISOR" assigned. No password needs to be set.


Note - the User generation in this window might not work well, depends on the password policy of your system. If you find it doesn't work, create the user BGRFCSUPER via the transaction code SU01. (as a system user of type B)

In the transaction code SM59, now you have a RFC Destination "BGRFC_SUPERVISOR" in Connection Type 3. And the system user for bgRFC is assigned in the Logon & Security tab.


b. Define Inbound Destination


(Note - formal help document: Maintaining Inbound bgRFC Queue on the Hub System - SAP NetWeaver Gateway - SAP Library)


Run the transaction code SM59. Create a new RFC Destination "IWFND_ODATA_PUSH" in Connection Type 3. Supply Target Host = <the local SAP Gateway Hub server name> and its System Number.

Click on the Special Options tab, and scroll down to select Transfer Protocol = Classic with bgRFC. Save the config.

Run the transaction code SBGRFCCONF. Select the Define Inbound Dest. tab. Click on the create icon.

Here you enter the IWFND_ODATA_PUSH value you had created. This is going to be the name of the queue. Make sure to choose Logon/server group value too.

Now you had configured the bgRFC setting to create a push queue.

What's next? Let's try the push test.


#7 How To... Implement End-to-End Push Notifications with HCPms and SAP Gateway

17 Comments