When configuring a new External Processes within the BPMC Data Pipeline, there are 2 types of process that can be defined: IN and OUT. What do these settings mean and how do they affect the behavior of your feed?
IN stands for In-Process. When an External Process is set for In-process, that means it executes as a sub-step of the feed it is embedded into, and the short description is logged as a step in the Data Process Control. If the IN process steps fails, it will fail the feed. In essence, it is an extension of the feed it is embedded into.
OUT stands for Out-of-Process. When an external process is set for Out-of-Process, it spawns a completely different agent job and is NOT logged into the feed logs; you cannot see its success or failure in the Data Process Control logs and runs in an independent memory pool. If an Out- Process fails, it will NOT fail the feed (the current feed has no knowledge of the OUT process other than invoking it).
By in large, the OUT functionality was added to support the daisy chaining of other BPMC feeds. Since the BPM Connect process queue requires feeds to be run in serial fashion (vs parallel), if the BPMC feed is called IN process, than its logging can collide with the current feed, and can break the Data Process Control and feed collision handler.
Rule of thumb, stick with IN except when running BPMC feeds, than use OUT ;)
Click here for more information on External Process tab concepts
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment