The General Splitter is configured with XPath //z and with Grouping set to 2.In the second branch the message is sent to a Local Process, where it is split, and each split message is sent out using SFTP by a Send step.In the first branch the message is sent out as it is using SFTP.Parallel Multicast is used to route the message to two receivers to show the difference in runtime processing.The message is created using a Content Modifier, which sets the body to a simple sample XML:.In the main process, a message is triggered by a Timer step.To showcase the runtime behavior, we build an easy sample: In this scenario, we use the Send step together with General Splitter in a local process. Sample Scenario 1: Splitter with Send Step in Local ProcessĪs stated above, you can use the Iterating or General Splitter in a local processes together with a child element. Combinations with different flow steps in the local process need extra testing, because they may behave differently than in the main process.If Splitter is used in local process in combination with any other steps except Gather (for example Send, Request-Reply ) the message returned into main process is the message before splitter.If splitter is used in local process in combination with Gather, the message returned to main process is the message at the end of local process.There is always one message going into the local process and one message returning from the local process to the main process.Some steps that would be useful are Send, Request-Reply and Gather. You can use any flow step for this, but most do not make sense in the context of the scenario. Splitters in local processes need a child element. ![]() This will raise an error during deployment You cannot use a splitter without a child element in a local process.Splitter -> Gather -> Splitter -> Gather…. ![]()
0 Comments
Leave a Reply. |