Yes, you are absolutely right. You may think of 7.5 stack split system functionality as PI dual stack functionality, but spread across two systems with their own SIDs. This means, principal limitations for Integrated Configuration scenarios which were in place in earlier releases in part of necessity to use Java-only features in them, remain the same in 7.5 stack split system. Which gives two options:
- If you want to reduce migration and re-development efforts, you may still use classic scenarios (sender + receiver agreements, receiver + interface determinations from configuration perspective, dual stack execution from runtime perspective). This may make sense if there is no possibility to use automatic migration tools (like Integration Directory Migration Tool) - and existence of ABAP mapping programs is a good use case for that;
- For new developments and whenever possible, you may migrate to Integrated Configuration scenarios and benefit from Java-only processing for them.
Configuration scenarios can be used not only in conjunction with classic scenarios - Integrated Configuration objects can also be assigned to a configuration scenario.
Regards,
Vadim