When using NiFi RPG with RAW, do we still use the UI port in the URL connection field?

[#1]

I am going to be using RAW for my NiFi RPG. I have set up 'nifi.remote.input.socket.port' to be port 8022. Now when I am adding the RPG to the canvas, in the URL field do I still put in my NiFI UI port (https://example.com:9091/nifi/) or do I put in the new RAW port (https://example.com:8022)? I tried testing it and it's only working with https://example.com:9091/nifi/ and I wasn't sure if that is how it is meant to work or if I have some configuration wrong.

Thanks,

Chad

[#2 · Accepted solution]

@Chad Woodhead

Whether you use HTTP or RAW, the URL used when creating the RPG will always point at the same URL for the NIFi target instance or instances.

 http(s)://<hostname>:<nifi.web.http(s).port>/nifi   (for example: https://hostname:9091/nifi)

The RPG will always connect to the above target URL to retrieve S2S details. (such as: will connection use RAW or HTTP, how many nodes in target cluster, target node current load, nifi.remote.input.host and nifi.remote.input.socket.port for each target cluster node, etc...)

When it comes to the actual transfer of FlowFiles over the S2S protocol, Those FlowFiles will either be transferred over the same nifi.web.http(s).port or via a dedicated RAW nifi.remote.input.socket.port.

Thank you,

Matt

[#3]

Got it, thanks!