Anup,

Site-to-site doesn't work by having a port with the same name on both machines. There have been a few people try that, so I guess that's a fairly common misconception. Sorry about that!

On Machine A, you don't want to setup an Output Port. Instead, you want to drag on a Remote Process Group (the 5th icon in the toolbar).

It will ask you for the URL of the instance to send to. This is the URL of the second instance's UI - so for instance localhost:8080/nifi

Then, you can create a connection from GetFile to that RemoteProcessGroup. It will ask which port to send data to.

If you drag the connection and it says that there are no input ports available, you may need to right-click and choose "Refresh flow" and wait a few seconds for it to refresh the remote instance's contents. Then try creating the connection again.

Let us know if you still have problems.

Thanks!
-Mark


------ Original Message ------
From: "anup s" <[email protected]>
To: [email protected]
Sent: 4/28/2015 10:11:30 AM
Subject: configuring site-to-site

Hi,
   I am trying to perform a site to site configuration.

I am trying to do a GetFile at one site and do a PutFile in another.

What I did:
Configured NiFi in machine A and set the socket input port number and set
secure to false in nifi.properties
 - Ran the first NiFi instance in machine A
 - Setup a GetFile with a input dir on machine A
 - Connected it to an output port (named it XYZ)

Configured NiFi in machine B and set the socket input port number to a
different number and set secure to false in nifi.properties
 - Ran the second NiFi instance in machine B
 - Setup a PutFile processor with the local dir of machine B
 - Connected it to an input port (named it same, XYZ )

When I run both the nifi instances I do not see the files getting
transferred. What am i missing?



--
View this message in context: http://apache-nifi-incubating-developer-list.39713.n7.nabble.com/configuring-site-to-site-tp1253.html Sent from the Apache NiFi (incubating) Developer List mailing list archive at Nabble.com.

Reply via email to