Content-based router is a pattern to route messages to different receivers, based on content from message. Example: File R1_AAA.txt have first column with value “R1”, then route this message to receiver BC_R1 File R2_BBB.txt have first column with value “R2”,
This is a scenario to use SOAPUI tool to trigger web service via sender SOAP adapter, then convert to output file via receiver file adapter. Create graphical iFlow view: iFlow = IF_SOAP2FILE_MAPPING Sender system = BC_SOAP_A Receiver system = BC_B
In past post, http://saprainbow.com/sap-pi-adapter/simple-any-file-to-file-scenario-in-id-only-without-esr-objects/ will copy any file to file with dummy interface using integration directory only. In this post, will achieve the thing but in SAP PO AEX, using NWDS, iFlow and ICO. Objective: Create a scenario where file
Integrated Configuration The main different we can see from Integration Directory is, there no longer have those old faithful classic 4 objects (sender agreement, receiver determination, interface determination and receiver agreement). Instead, replaced with Integrated Configuration (also known as ICO).