There are already several standard and well documented methods for creating a NLB cluster for BAM Portal like here. The problem with all these methods is that they tend to be very complex and long. Usually you would end up missing some steps and it will not work.
What I was able to find is a very simple and short way to configure BAM portal on several servers using Windows NLB.
- Start by configuring BAM Portal on the first server “Server1” using the BizTalk Configuration Tool (normally).
- Open the SQL management studio.
- Open the Database “BamPrimaryImport”.
- You will find a table called ”bam_Metadata_Properties”.
- Remove the row for the value “BAMVRoot”
- Now login to the second server “Server2”.
- Open the BizTalk Configuration Tool and WOW you can use it to configure the Portal on this node also.
- Repeat steps 2-7 for as many nodes you have in your NLB.
- Now you are not done yet please continue. Change the web.config on all nodes so that the management web service and query web service URLs are pointing correctly to the NLB address and not the nodes addresses.
- Now perform the steps below to update the BAM configuration for the location of the cluster.
Use the BAM Management Utility to get the current BAM configuration. To do this, click Start, click Run, and type drive:Program FilesMicrosoft BizTalk Server 2010Trackingbm get-config -FileName:MyConfig.xml.
Replace the local host name with the name of the NLB cluster. To do this, click Start, click Run, and type notepad drive:Program FilesMicrosoft BizTalk Server 2010TrackingMyConfig.xml.
For hardware-based NLB only, verify the configuration file has the following:
Modify the following line to point to the NLB cluster by replacing the computer name (machinename) with the cluster name:
Save the new configuration. To do this, click Start, click Run, and type drive:Program FilesMicrosoft BizTalk Server 2010Trackingbm update-config -FileName:MyConfig.xml.