I'm having a problem with the command you showed below. When I run it for my stuff I get the following: PS C:\Dev\aim\nifi-toolkit-1.9.1\bin> .\cli.bat nifi pg-enable-services -pgid aee943fb-48ac-351e-aef7-29db27d33b0f -p .. \conf\cli.properties
ERROR: Error executing command 'pg-enable-services' : One or more services could not be enabled, run command with -verbose to obtain more details The are for components referencing the StandardHttpContextMap, one HandleHttpRequest component and three HandleHttpResponse components. Any suggestion on how to handle this error? -----Original Message----- From: Bryan Bende <bbe...@gmail.com> Sent: Thursday, March 21, 2019 12:27 PM To: users@nifi.apache.org Subject: Re: Automate the Enablement of a StandardHttpContextMap [CAUTION: This email originated from outside of Kodak Alaris. Do not click links or open attachments unless you recognize the sender and know the content is safe.] ________________________________ When a template, or a versioned flow, is instantiated, all the processors are initially stopped and the services are disabled. This is done on purpose since starting and enabling components may cause interactions with external systems, and it may not be clear or desired that just by instantiating the template that all of these interactions are automatically going to take place. So it requires an extra step where the user (or your script) must explicitly enabled and start the components. The NIFI CLI has a command "pg-enable-services" that can be used to enable all the services in a given process group. You could call this from your script like "./bin/cli.sh nifi pg-enable-service -pgid someid". On Thu, Mar 21, 2019 at 11:29 AM William Gosse <william.go...@aifoundry.com> wrote: > > I’m trying to automate the deployment of a template that contains a > HandleHttpRequest processor. > > > > My issue is that this always comes up with an Invalid component marker after > a fresh deployment of the template. > > The cause of this marker is that the StandardHttpContextMap in the > HandleHttpRequest processor needs to be manually enabled in Controller > Services. > > > > Is there any way to avoid this manual enablement? > > > >
