You give me too much credit, I will probably reach out for help
setting it up ;)  In any case, please "pinch" this list again if you
haven't heard anything in the next few days :)

Cheers,
Matt

On Wed, Mar 15, 2017 at 6:54 PM, Uwe Geercken <[email protected]> wrote:
> Thanks Matt,
>
> there is a little "but" though: The business rules are maintained outside of 
> nifi in a web app. and that's good and the concept behind business rules - to 
> not clutter up the flow and to devide the responsibilities of IT code/process 
> and business logic.
>
> Having said this, you will need to have a mysql/mariadb database, import the 
> schema and also run the rulemaintenance web application in tomcat, to create 
> the business logic.
>
> Hope that is not too much to ask for...
>
> Greetings and thanks again.
>
> Uwe
>
>> Gesendet: Mittwoch, 15. März 2017 um 23:24 Uhr
>> Von: "Matt Burgess" <[email protected]>
>> An: [email protected]
>> Betreff: Re: RuleEngine Processor
>>
>> Uwe,
>>
>> I will do my best to look at this but it will probably be next week. It 
>> seems very interesting and my only excuse is being swamped by other things. 
>> Thank you for sharing this, hopefully others in the community will give it a 
>> go as well.
>>
>> Regards,
>> Matt
>>
>>
>> > On Mar 15, 2017, at 6:12 PM, Uwe Geercken <[email protected]> wrote:
>> >
>> > Hello,
>> >
>> > I have worked quite a bit on my RuleEngine processor and would appreciate, 
>> > if somebody takes some time to try it and to look at the source code and 
>> > give me some feedback.
>> >
>> > You can download it at: https://github.com/uwegeercken/nifi_processors
>> >
>> > It is my first bundle of processors, so I guess there are many 
>> > improvements I could make - but I need your expertise and opinion.
>> >
>> > Also - quite important - I have renamed the processor to 
>> > "ExecuteRuleEngine". I believe that fits better to the general naming 
>> > convention that is used for the processors.
>> >
>> > I still need to work a lot on the documentation, too.
>> >
>> > Greetings,
>> >
>> > Uwe
>>

Reply via email to