I agree ccBPM is the a technical solution for you scenario. But if you are challenged by development of the ccBPM object, or you customer would rather avoid BPM in their landscape; then you can try a creative solution using pure, standard PI functionality.
You could use a database as intermediary repository for the data between you 7 senders and your receives.
This will allow you:
- Simplify the mapping to the Receive, Mail in this case.
- Have control over when the received data is complete and when to send the email using communication channel availability.
I will only be able to give you a guide on what to do, but hopefully it give you some ideas you can sort things out.
You will need:
- A database in any database server you system has access to.
- The correct JDBC drivers for the database deployed in PI
- Design a database schema(table) based on the data you need to create the Receiver Message structure.
- Make sure you have key fields as TimeStamp, Sender, TimeSent, which could help you managing and grouping data.
- Create a Mapping between the database table and the eMail structure you need.
- I will recommend you to use XML-SQL format to easy up the work.
- This is the help on how to use the sender JDBC adapter, Defining XML Documents for Message Protocol XML SQL Format - Configuring the JDBC Adapter in the Integration Directory/P…
- I will recommend you to use XML-SQL format to easy up the work.
- Create the Mapping from the Sender interfaces to the the Database.
- Need reference for using the reciever JDBC adapter: Configuring the Receiver JDBC Adapter - Configuring the JDBC Adapter in the Integration Directory/PCK - SAP Library
- When configuring use the Channel Availability Planning
You can use the database to create different views, to control the interface.
Enjoy, interfaces with the JDBC adapter are very enjoyable to develop and troubleshoot