Skip to Content

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


Implementation Plan

/wp-content/uploads/2015/10/12_820397.png

If you need ERP backend access for push content (such as SAP Business Workflow), wire the SAP Gateway Hub and its ERP backend.


Note: as the FLIGHT OData services are installed with SAP Gateway installation, your ERP box might not have the FLIGHT services. In that case please use your OData services (such as the one from SAP Business Workflow) in the configuration example below.


Steps to Implement


Configure the OData so that the service execution goes to ERP backend from SAP Gateway Hub.


On the Gateway Hub, Run the transaction code /IWFND/MAINT_SERVICE. Find the FLIGHT services.

/wp-content/uploads/2015/10/7_1_819171.png

In the Service Catalog for “RMTSAMPLEFLIGHT”, find the System Alias and Add System Alias so that the service execution goes to the remote Backend system by checking in the “Default System” box.

/wp-content/uploads/2015/10/7_2_819242.png

In this way, the OData service access to the Gateway Hub goes to the Backend system.


Let’s configure the bgRFC on the backend box. This queue will go to Gateway Hub.

bgRFC2.png

On the ERP Backend box, Run the transaction code SBGRFCCONF. The steps are pretty much similar with what you had done at the Gateway Hub.


a. Define Supervisor Destination

/wp-content/uploads/2015/10/6_5_819244.png

/wp-content/uploads/2015/10/6_6_819254.png


b. Define Inbound Destination

(Note – formal help document: Maintaining Outbound bgRFC Queue from SAP Backend System to the – SAP NetWeaver Gateway – SAP Library)

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

/wp-content/uploads/2015/10/7_3_819273.png

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

/wp-content/uploads/2015/10/6_8_819256.png

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

/wp-content/uploads/2015/10/6_9_819257.png

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

/wp-content/uploads/2015/10/7_4_819281.png

Click on the Scheduler: Destination tab.

/wp-content/uploads/2015/10/7_5_819326.png

Create the bgRFC Configuration as “Inbound”.

/wp-content/uploads/2015/10/7_6_819327.png

/wp-content/uploads/2015/10/7_7_819328.png

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

bgRFC2.png

Now the landscape should be complete – if you subscribe the service, a new subscription entry will be created in the subscription table /IWBEP/D_MGW_SUB in the Backend system. You can use the same troubleshooting tips learned in the SAP Gateway Hub configuration steps.


The entire landscape is ready for subscribe & notify.

/wp-content/uploads/2015/10/13_820398.png

What’s next? – Let’s learn tips & tricks of Subscribable OData and Notification API in ABAP.


#9 How To… Implement End-to-End Push Notifications with HCPms and SAP Gateway


To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply