6.5    Supporting Multiple Senders for Your iFlow

Imagine you have multiple sender systems sending the same XML message but using different communication mediums or protocols. One sends it using the file adapter, and the other uses a Simple Object Access Protocol (SOAP) adapter. Before SAP PO 7.5 SP 04, the only way to achieve this was to create two separate iFlows. This situation creates additional implementation/maintenance work and isn’t practical. From SAP PO 7.5 SP 04, it’s now possible to use multiple sender communication channels in the same iFlow. This section shows you how to accomplish this.

With this support of multiple senders in your iFlow, you can configure central message processing by creating one iFlow with a sender wildcard. Follow these high-level steps to create an iFlow with a sender wildcard:

  1. From the SAP NetWeaver Design Studio Designer perspective, you can now use a pattern called Recipient List (Multiple Senders), as shown in Figure 6.47.
  2. The next screen shows the patterns that automatically set a wildcard in the sender Communication Component (see Figure 6.48). Select Finish.
    Recipient List (Multiple Senders)

    Figure 6.47    Recipient List (Multiple Senders)

    Sender System Made Generic with a Wildcard Type

    Figure 6.48    Sender System Made Generic with a Wildcard Type

  3. From the created iFlow, you can add specific Sender Agreement and Communication Channels using the Add button in the Senders tab as shown in Figure 6.49.
    Adding a Sender Agreement in the Senders Tab

    Figure 6.49    Adding a Sender Agreement in the Senders Tab

  4. From the new screen that appears, specify the sender system using the Browse button (see Figure 6.50).
    Creating a Sender Agreement

    Figure 6.50    Creating a Sender Agreement

  5. After selecting a Sender System, select or create a communication channel to associate with it.
  6. Finally, select the Refresh button to see the list of Sender Agreements, as shown in Figure 6.51.
List of All Sender Agreements That Match an iFlow

Figure 6.51    List of All Sender Agreements That Match an iFlow

Notes

A sender agreement consists of the channel assignment and the assigned users. A sender agreement is suitable for a wildcard iFlow if the sender agreement interface definition matches the iFlow sender interface or if the sender agreement uses interface wildcards. It’s also possible to create a sender agreement from scratch by right-clicking on a sender business system or business component and selecting the New Sender Agreement option from the context menu.