Designing the Real Time Message NDS Types and Download Profile

For this scenario you must create two NDS types

One NDS type is used for the real time message. Indicate an appropriate notification download condition. This allows the mechanism that creates the NDS to refer to this condition rather than hard-coding the NDS type.
One NDS type is used for the near real time message. This NDS type must reference a special XAI inbound service used to indicate to the download staging sender that the XDS does not need to be created.

Note: Download Condition. The real time message engine receives the NDS type as input. It is the user exit's responsibility to determine the appropriate NDS type based on a notification download condition.

You'll need to create an entry in the service provider's notification download profile for each NDS type. Set the processing method to XAI and indicate the appropriate route type (real time or near real time) created above.