SAP Fiori – Notification Channel Configuration
- SAP NETWEAVER / 7.5 / 05 / (10/2016) / sap.com SAP NETWEAVER 7.5
- SAP_GWFND / 750 / 0005 / SAPK-75005INSAPGWFND / SAP Gateway Foundation
The Notification Channel is a framework for the applications to deliver end-user notifications across multiple channels. It is part of the SAP_GWFND component of the Front-End Server.
The functionality includes:
Backend provider interface – enable / text templates / handling actions
Backend API – manage notification (create/delete)
Configuration for hub and embedded scenarios (connectivity)
Configuration for push channels (connectivity)
Example use case: SAP Fiori launchpad integration
Develop Notification Provider
The next is the general interface for the notification provider, all notification providers must implement this interface:
Each provider has an automatically assigned ID that is used for all interaction with the notification channel, before any notification is created, the notification provider must be implemented.
Register the notification provider
Transaction: /n/IWNGW/BEP_NPREG – Register Notification Provider
Indicate a Provider ID, a class that has the /IWNGW/IF_NOTIF_PROVIDER interface, and a provider description:
Use the SM30 transaction with the /IWNGW/VB_REG_P view, to activate the previously defined provider:
Configure the Notification Channel
OData V4 Service:
Implement the V4 /IWNGW/NOTIFICATION_SRV service.
All the steps for the configuration of the service are accessed from the SPRO in the route:
- SPRO -> SAP NetWeaver -> Notification Channel
1. Enter the Notification Hub RFC Destination
A RFC connection from the front-end server to the back-end server must exist previously.
- SPRO -> Notification Channel Provider Enablement -> Configuration -> Connection Settings -> Enter the RFC Destination Notification Hub
Select the corresponding RFC Connection and Execute to save the configuration:
2. Enter the Backend System Alias
A System Alias must be pre-configured.
- SPRO -> Notification Channel Provider Enablement -> Configuration -> Connection Settings -> Enter the SAP Backend System Alias
Enter the indicated System Alias and Execute to save the configuration:
3. Create bgRFC Destination
This is an access to transaction SM59
- SPRO -> Notification Channel Provider Enablement -> Configuration -> Connection Settings -> Create bgRFC Destination
- The RFC destination to be created must strictly be called “IWNGW_BGRFC“
- Connection Type: 3 – ABAP Connection
- Enter a characteristic description.
- On the Technical Settings tab, ensure that the Load Balancing option is set to YES. The Target System, Msg.Server, and IP Address fields are completed automatically.
- In the Special Options tab, the Protocol field must be set to Classic with bgRFC.
- Save and verify the connection, authentication and logging to the backend test.
4. Register RFC Destination for Background Processing
The Notification Channel uses output queues to reliably send information to a back-end system, these output queues use bgRFC (Background Remote Function Call) technology.
This activity allows you to register the bgRFC connection.
- SPRO -> Notification Channel Provider Enablement -> Configuration -> Connection Settings -> Register RFC Destination for Background Processing
- Run the activity.
- Go to the Define Inbound Dest. tab, and select Create.
- In the Destination Name field, enter the exact name: IWNGW_BEP_OUT_BGRFC
- Create the following new queue prefix: In the New Prefix section, enter Q and press the New/Add button.
- Save all changes.
5. Create bgRFC Supervisor Destination
The Notification Channel uses output queues to reliably send information to the user, these output queues use bgRFC (Background Remote Function Call) technology.
The bgRFC can only function if a Supervisor Destination has been defined, this activity allows you to create that Supervisor Destination.
- SPRO -> Notification Channel Provider Enablement -> Configuration -> Connection Settings -> Create bgRFC Supervisor Destination
- Run the Create bgRFC Supervisor Destination activity.
- Go to the Define Supervisor Dest. tab, and create the Destination Supervisor if it does not exist.
- The RFC destination name must be exactly: BGRFC_SUPERVISOR, then you must enter a suitable User and Password.
- The user must be a special user created specifically for the bgRFC Supervisor Destination.
- The user must be assigned the authorization role SAP_BC_BGRFC_SUPERVISOR or the copy of the authorization role.
- Save all changes.
6. Register Notification Providers
This activity allows you to register new notification providers that can be used as notification sources within the notification channel. The Notification Provider must be created previously as indicated in the previous points (point 5).
- SPRO -> Notification Channel Provider Enablement -> Administration -> Notification Provider Settings -> Register Notification Providers
- Run the Register Notification Providers activity.
- If it does not exist, create / add the required notification provider.
- The assigned Class Provider must be fill mandatorily with the /IWNGW/IF_NOTIF_PROVIDER Class Interface.
- Save all changes.
7. Manage Notification Providers
This activity allows you to manage the notification providers by enabling/disabling the previously registered notification providers.
- SPRO -> Notification Channel Provider Enablement -> Administration -> Notification Provider Settings -> Manage Notification Providers
- Run the Manage Notification Providers activity.
- Add Notification Providers as needed.
- Check or Un-Check the Activation check as appropriate.
- Save all changes.
With these procedures the Notification Channels are configured and active.
Nice work Geovanny. It's good also to mention how people can test this by registering the demo provider IWNGW_DEMO1 and using the demo transaction /IWNGW/BEP_DEMO.
That's right @Jocelyn, Thank you very much for your cooperation!! 🙂
I completed the configuration and this is not working.
I have a Gateway server and the ECC server. Can you explain what should be the differences on that case.
Thanks for the post! Do you have any information on how to configure the Fiori Launchpad to get the notifications as in the first picture in the post?
It looks like it could be a launchpad plugin?
I got this working on my system. Is there any way to control which actions are shown in the notification center in Fiori for the notification items.I just want to push an information to the user without any actions (Approve and Decline by default). Is this possible in the current version? I assume this is related to the content in DB Table "/iwngw/naction" but I couldn't find any configuration
to add some records to this table.
I am trying to get this working, but it is not really clear for me which steps must be done in the Front-end and which ones are to be done in the Back-end. Could you provide further information about this, please?
Thanks Geovanny. I have few questions and it will great, if you can please address it. I tried implementing Notification center as mentioned in Jocelyn Dart's blog but it neither shows up the Notification icon nor working as expected.
Hi Seeker, have you got an answer on this?
I got no answers. But we didn't implement Notification center due to back-end requirement of OData V4 enabled, whereas we had only V2. If you solve these issues, it will be helpful if you can post the solution here, which might be helpful for others.
Thanks and Regards.
Thanks, actually I am testing this on our Sandbox environment so we are going to upgrade our backend Gateway foundation to 7.51 and try if it works. My understanding is that OData 4.0 should be available from 7.50, correct?
For your info I found following tutorial which shows step by step how to configure this so it might be useful in case you have the option to upgrade:
It seems this functionality is not longer available for 7.50.
I have seen help,sap.com and many blogs which give info related to Triggering of demo notification only.
Apart from Demo Notification Provider ID, how can we trigger other Notification provider Id's and is there any transaction that captures failed Notification (i.e due to failed connections), so we can retrigger them.
Thanks in advance