Install ESB Portal Database on a Named Instance
On my current project I had a requirement to install the ESB Toolkit exception portal database on a named instance of SQL Server. This particular client was sharing a single physical server among multiple database applications for their development environment. Some of these applications, like BizTalk, make changes to the SQL Server configuration settings that are optimal for normal database operation. To isolate these applications they created a named instance for each application that required special configuration settings.
There are plenty of guides for installing and configuring the ESB exception portal out there already so I will not replicate those instructions here. If you need a guide, I am a fan of Configure BizTalk ESB Toolkit 2.2 Management Portal. Installing the portal on a named instance is not complicated but I have not seen it documented. It was not obvious to me until I read through the batch and PowerShell installation scripts.
When you run the Management_Install.cmd batch script, add an argument to the end that specifies the name of the SQL Server instance you wwould like use for the portal database. So if you have a server named devsql with an instance named bts the command would look like this:
1 | .\Management_Install.cmd devsql\bts |
The user running the script will need to have permission to create new databases in the named instance. Assuming the prerequisites and security have been configured correctly the script should install the portal database to the specified SQL Server instance.
If you would rather run the PowerShell script directly, the SQL instance name is the second argument to the script. The first argument to the PowerShell script is the IIS website ID for the ESB web services. Using the same values as before, the command would look like this:
1 | .\Management_Install.ps1 1 devsql\bts |