> In NiFi I can use ports, but than I need to connect those ports. You can wrap each operation in a process group and then connect the process groups via ports so your main canvas is substantially less cluttered. You can also nest process groups inside of each other. that works really well for organizing related functionality.
On Mon, Jul 22, 2019 at 10:17 AM ski n <[email protected]> wrote: > I work on migrating a large ESB process to a NiFi flow. This process > contains around 40 events (40 different flowfiles). On the ESB a loosely > coupled pattern was used with the help of JMS queues. In NiFi I can use > ports, but than I need to connect those ports. The canvas soon becomes > messy. > > Is there a way to use something like a ‘topic’ in Nifi? So some kind of > endpoint without connecting items (processors/process groups) or is this > against the dataflow concept and you always need external brokers like > Kafka or ActiveMQ for this? > > Another question is what to do with failure messages. Can you configure a > default ‘endpoint’ for all failures within a certain process.? Now I > connect all processors to failure handling step/port, but this gets soon > messy as well. What is the best practice for errors? Do most use > autotermination? > > > Regards, > > > Raymond >
