Member since
03-08-2016
23
Posts
8
Kudos Received
1
Solution
My Accepted Solutions
Title | Views | Posted |
---|---|---|
1432 | 03-24-2016 07:54 PM |
03-24-2016
07:54 PM
The root cause of the problem has been remedied. Please consider this matter closed.
... View more
03-18-2016
04:09 PM
@Charles Clifford I notieced you have access to following: 1. Hadoop Administration 1 2. Migration 3. Management and Operations 2.0 So you have full access on Admin track. If you are done with #1 & #3 (which you have already completed), You do not need to do #2.
... View more
03-15-2016
06:25 PM
Thanks. I have decided to switch over to VMWare from VirtualBox.
... View more
07-01-2016
09:24 PM
1 Kudo
First, by default port 9090 for the inbound connection is open for the Azure sandbox (among all the other ports that look like swiss cheese) Set up a SSH tunnel that you will connect to NiFi through. This is assuming your are using the Resource Managed VMs. You need to replace the sandbox URL with your own. By default Azure does not give you the nice DNS name. You have to explicitly set this up as a property of the IP address (very annoying). For a Mac in Terminal use this to set up your tunnel: ssh -L 9090:sandbox.eastus.cloudapp.azure.com:9090 azureuser@sandbox.eastus.cloudapp.azure.com
For Windows: Using Putty, Go to SSH -> Tunnels. Enter 9090 for Source Port and localhost:9090 for Destination Port. Don't forget to save the configuration. Now just go to http://localhost:9090/nifi for any browser and enjoy! If you are using 9090 locally, just change the destination to a unused port. On the nifi side you can change the port in the /conf/nifi.properties file.
... View more