Hierarchy
⤷ OPU-GW-COR (Application Component) Gateway Framework
⤷ /IWFND/MGW_PUSH (Package) GW Framework - Odata Channel - Notification
IMG Activity
ID | /IWFND/MGW_NOTF_CNTP | OData Channel: Notification Content Publisher |
Transaction Code | /IWFND/59000012 | (empty) |
Created on | 20111104 | |
Customizing Attributes | /IWFND/MGW_NOTF_CNTP | OData Channel: Notification Content Publisher |
Customizing Activity | /IWFND/MGW_NOTF_CNTP | OData Channel: BAdI for Notification Content Publisher |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | /IWFND/GW_BADI_PUBLISHER |
Use
Each application can publish the Notification content from the SAP NetWeaver Gateway system. To publish the notifications implement the BAdI /IWFND/BD_MGW_NOTIF_SENDER. The BAdI is called by the Notification Receiver in Gateway after it formats the Notification Content and serializes the Notification Content to ODATA Atom Format.
Requirements
Standard settings
There is a default implementation delivered by SAP for the BAdI definition. SAP provides a default way to publish the Notification Content.
The BAdI is a filter based single use BAdI.
Activities
DELIVERY_CHANNEL - Delivery channel name is the mandatory filter paramater. The Delivery Channel filter parameter can be:
A pattern from the delivery address specified in the format as "urn:sap:channel:<channel name>/<request URI>" while subscribing an entity.
OR
An RFC connection name of type "G" maintained in transaction SM59 for the delivery address while subscribing an entity.
Note: The filter parameter DELIVERY_CHANNEL is derived out of delivery address. If delivery address is not specified while subscribing for an entity then BAdI will never be called. This is applicable even for pull based subscriptions where delivery address is optional. For pull based notifications if formatting is required then provide a dummy delivery address while subscribing and maintain the same as filter parameter for the DELIVERY_CHANNEL.
Example
You can implement this BAdI while publishing notification contents using different authentication mechanisms.
Business Attributes
ASAP Roadmap ID | 105 | Define functions and processes |
Mandatory / Optional | 3 | Nonrequired activity |
Critical / Non-Critical | 2 | Non-critical |
Country-Dependency | A | Valid for all countries |
Maintenance Objects
Maintenance object type | E | Business Add-In - Definition |
History
Last changed by/on | SAP | 20111108 |
SAP Release Created in | 250 |