Yellowfin 8.0.1 requires additional firewall ports for MS SQL Named Instance
We are using the Yellowfin application within BMC's TrueSight Server Automation product for their Live Reporting application. Our environment has some unique security requirements. The Yellowfin web server and database exist outside a secured network. The data source requires access to the TrueSight Server Automation database, which exists inside the secure network. The database is hosted on a MS SQL Server 2012 instance, and the instance is using a specific port, and not the dynamic port option.
When we run the installer for Live Reporting (which is a wrapper around the Yellowfin v8.0.1 installer) the installation fails if we select the named instance option using the specific port for the instance. If we select the default instance, it succeeds. From what we've been able to determine, the installer is trying to reach out to the instance using the default port of 1433 even though we've specified a port for the instance.
Does anyone know and understand why the YF installer is using a port other than the specified port during the installation? And to be up front, I have already engaged BMC on this as well, but they are not coming up with any answers.