The Notification Channel framework provides predefined roles as templates for developers, administrators, end users and so-called provider users. You configure the roles based on the provided templates and assign users to the roles.
The role templates specify the authorizations for content that can be accessed by users of the specific consumer application, for example the notification panel in the SAP Fiori launchpad or administrativ transactions within the implementation guide (IMG).
You can find more information abut how to use role templates in Creating and Assigning Roles from Templates.
The following role templates are available in transaction PFGC.
Template Name |
Description |
---|---|
/IWNGW/RT_BEP_ADM |
Role template for Notification Channel backend administrator |
/IWNGW/RT_HUB_ADM |
Role template for Notification Channel hub administrator |
/IWNGW/RT_NP_DEV |
Role template for Notification Channel developer |
/IWNGW/RT_USER_CONSU |
Role template for Notification Channel consumer user |
/IWNGW/RT_USER_PRODU |
Role template for Notification Channel producer user |
The template /IWNGW/RT_BEP_ADM carries authorization proposals for activities that are required by the backend administrator. You can access those activities in the SAP Reference IMG in the Implementation Guide (IMG) in transaction SPRO under .
The activities include the following:
Setting up connectivity between the backend and the hub (frontend server)
Creating and registering RFC destinations
Configuring the queued background RFC destination and scheduler
Registering and activating the notification provider (ABAP class which implements a specific ABAP OO interface )
The template /IWNGW/RT_HUB_ADM carries authorization proposals for activities that are required by the frontend administrator. You can access those activities in the SAP Reference IMG in the Implementation Guide (IMG) in transaction SPRO under .
The activities include the following:
Setting up connectivity between the hub (frontend server) and the notification provider (backend)
Creating and registering RFC destinations
Setting up SAP system alias configuration
Setting up push channels
Websocket connection which is used by the SAP Fiori launchpad
SMP connection which is used to push notifications to mobile devices
Configuring the encrypted notification data store
The template /IWNGW/RT_NP_DEV carries authorization proposals for activities that are required during the development process of a notification provider.
The activities include the following:
Creating implementation of an ABAP OO class
Registration of that particular provider class
Using tools for clearing the metadata cache and notification store
The template /IWNGW/RT_USER_CONSU carries authorization proposals for activities that are required by the frontend user. Usually this is the user who receives notification through a mobile device or through the SAP Fiori launchpad notification panel.
Authorizations inlcuded cover some mandatory requirements for the frontend - backend communication. For example, a notification can have actions like "Approve" or "Reject", those actions are, when triggered, routed through the hub to the backend where they are actually processed through the origination provider.
The template /IWNGW/RT_USER_PRODU carries authorization proposals for activities that are required by the backend user. Usually this the user who triggers a notification creation, most probably implicitly through a leading transaction which itself then triggers the notification creation API.