Determining MSIF transfer service and OU for transfer scenarios
How MSIF determines which MSIF transfer service and OU is to be
associated with a transfer scenario depends on the scenario type and
delivery mode:
- RT transfer scenario of type SendMsg, SendFile, ProvideFileForDownload and DownloadFile
- The customer application specifies the OU directly in the request, and puts the request message directly in the service input queue of the MSIF transfer service that is to process the transfer scenario.
- SnF transfer scenario of type SendMsg or SendFile
- The customer application specifies the OU directly in the request, and puts the request message directly in the service input queue of the MSIF transfer service that is to process the transfer scenario.
- RT transfer scenario of type MsgReceived, FileReceived, RespondDownload or NotifReceived
- The received primitive is associated with the OU that is mapped
to the receiving message partner. The message partner determines the
service input queue of the MSIF transfer service that is to process
the transfer scenario (see Figure 1).
Figure 1. Message flow for a real-time MsgReceived, FileReceived, RespondDownload or NotifReceived scenario 
- SnF transfer scenario of type MsgReceived, FileReceived or NotifReceived
- The received primitive is associated with the OU of the SnF queue
session or SnF output channel. The message partner that was used to
open the SnF queue session or SnF output channel determines the service
input queue of the MSIF transfer service that is to process the transfer
scenario (see Figure 2).
Figure 2. Message flow for an SnF MsgReceived, FileReceived or NotifReceived scenario 