This service will support creation of subscriptions only in the context of the new OData library 1.0.
An administrator can subscribe for notifications on behalf of a user or a role (a set of users). In both the cases, the users subscribed by the administrator gets the notifications and not the administrator. The notifications for the subscribed collections are pushed from the SAP backend to the SAP Gateway Hub system when the collections are modified. SAP Gateway then pushes the notifications using HTTP POST to all subscribers based on their delivery address. In case of roles, they are resolved by application specific implementation in the SAP Gateway system and corresponding users are sent notifications.
Following topics are covered:
Operations Supported
Authorization Details
Multiple Origin Composition (MOC) for Subscription Management
Here is the link to access the service document URL for subscription management:
http://<hostname>:<port>/sap/opu/odata/IWBEP/SUBSCRIPTIONMANAGEMENT/?$format=xml
Contact your system administrator for host name and port number.
An administrator can:
Create subscription for any user or role
Update subscription for any user or role
Delete any subscription either created by the administrator or any user
Read and Query any number of subscriptions provided which is in the context of new OData library 1.0
Proceed with the following configuration if you are using the original version (version 1) of SUBSCRIPTIONMANAGEMENT service and you want it to support content based routing. If you are using version 2 of SUBSCRIPTIONMANAGEMENT service, the following configuration is not applicable.
Version 2 of SUBSCRIPTIONMANAGEMENT service will be active if earlier version (version 1) is already available in active state. You only need to activate the version 2 of SUBSCRIPTIONMANAGEMENT service if it is not already in the active state. See Activate and Maintain Services for more information.
In transaction SPRO open the SAP Reference IMG and navigate to: and click on the Activity icon.
Choose the Model Identifier you created while activating the version 1 of SUBSCRIPTIONMANAGEMENT service. For example, ZOM_MGW_ADM_SUB_MODEL_0001_BE.
Change the Class/Interface to /IWFND/CL_MGW_ADP_VIRTUAL_PERS.
Save your settings.
The user requires specific authorization for the services in the system through the object /IWBEP/SUB. This is to limit the access to specific Business areas. The Role Template /IWBEP/RT_SUB_USR is used to create roles with the required authorization. The authorization checks are performed in two steps:
Level |
Authorization Check |
Description |
Field |
Value |
1 |
Authorization check for SUBSCRIPTIONMANAGEMENT service |
This is the first level of check where the authorization to the administrator to create subscriptions on behalf of users or roles is checked. |
/IWBEP/GTN |
/IWBEP/SUBSCRIPTIONMANAGEMENT |
ACTVT |
* (all operations) |
|||
2 |
Authorization check for specific services |
This is the second level check where the authorization to create subscription for a service is checked. For example, If the Administrator wants to create subscriptions on behalf of a user for the service RMTSAMPLEFLIGHT, the administrator needs the authorization mentioned here in level 2 and level 1. |
/IWBEP/GTN |
/IWBEP/RMTSAMPLEFLIGHT |
ACTVT |
* (all operations) |