Setting up Tableau Server is easy. Really easy.
And compared to (ahem) some of Tableau’s competitors, setting up a distributed installation is even more straight-forward.
In my opinion, the “trickiest” thing in terms of making everything work is validating that the well documented list of ports we use to communicate back and forth are open. We actually open these ports in the Windows firewall for you automatically, but if you’re running other stuff that does port filtering, it still might get in the way.
So here’s a quick way to make sure that everything that needs to be accessible is indeed accessible:
Next, you need this custom port list that yours truly created to plug into SuperScan. You’re welcome.
- Install SuperScan
- Drop the port list into the same folder where the tool is installed (generally, C:Program Files (x86)SuperScan).
- Modify the scanner.ini file to include the new port list in the [PortLists] section
At this point, when you launch the tool, you should be able to click Port list setup, then Load the port list in question. Click OK.
Finally, make sure that the Scan Type is set to Every Port in list.
Here’s me scanning my Primary machine (192.168.203.29) from a different box which is about to become a worker:
…and here’s me scanning the worker from the Primary:
Note that I’ve JUST added the worker as a machine I want to setup, and currently only the “Worker Setup Port” is open.
Once the configuration of the worker is done, it’s listening to more ports:
So, to summarize – port scanning Tableau for dummies (not you, me.)
…and a quick note about setting up SuperScan: since it IS so long in the tooth, your modern OS may handle some things it does a little differently. For example:
- You may not be able to edit the port.lst file or the scanner.ini file directly in the program folder. Instead, you may have to temporarily move them elsewhere for editing, them move ’em back.
- Windows may also save “old” copies of the files you edit and move in a different location…and use them instead of the newer ones! If this happens, check out the folder C:Users <your user name> AppDataLocalVirtualStoreProgram Files (x86)SuperScan. It’s likely you’ll find some stuff in there of interest.
Final thing – nah, I’m not going to support you on how to get SuperScan working on your machine: flex those technical muscles of yours and work through it yourself…