How to use an alternate SQL Port for self-hosted Enterprise Insights for Jira Align
Summary
By default, SQL Server runs on port 1433 and hence while installing the self-hosted (on-premise) version of Enterprise Insights (EI) it expects to communicate with the SQL server on the default port.
This article discusses how to setup a SQL server on an alternate port and configure EI to communicate on a different port from the default port.
Environment
Jira Align self-hosted
Solution
There is no documentation to confirm if such a configuration is officially supported.
An alternate port can be used for the ETL (SSIS), Data Warehouse or the Jira Align database servers.
When running Install.ps1 specify the port using a comma after the server name or IP address.
Examples (assuming the alternate port is configured to be 1435)
Please provide your data warehouse server name: mysqlsvr,1435
Jira Align Server Name: 10.1.0.5,1435
ETL Server Name: ssissvr,1435Q & A:
Question: Is there an impact of changing the port on EI in both, daily runs and during the installation of an upgrade?
Answer: There is no impact on Enterprise Insights. During upgrading you will need to remember to specify the port when prompted for the server (see examples above).
Question: If changed, aside from the TCP port change on the SQL server, is there any other configuration change that has to be made?
Answer: Run Install.ps1 to re-create the SQL Agent Job with the correct port numbers.
Was this helpful?