Install & Configure
Check out the prerequisits
.
1. Run the installer
Download and run the installer on the server you are planning run IPM from.
2. Create or configure an IPM user
IPM needs to run under a user with some special privileges. This is setup by the application pool running the site in IIS. The user of the IPMPool needs to be a member of
- The Administrators group of the local server IPM runs on.
- The IIS_IUSRS group on the local server IPM runs on.
- The BizTalk Server Administrators group used by the BizTalk server IPM should monitor.
Some IPM customer uses the same users that they use to run the BizTalk services under, and some customer setup a separate IPM users and adds that user to the required groups.
3. Configure IIS
To enable IPM Web to run under the user we setup, we need to configure the IPM Application Pool. This is managed under the Identity tab on the Application Pool properties in IIS.
To get IPM 2.0 to work under IIS 6.0 you need to make a small adjustment in the IIS to use the correct ASP.NET version. Follow these simple steps: Open IIS manager, right click on the IPM Web Site, go to ASP.NET tab, then under the dropdown ASP.NET version select the 4.0.xxxxx version. Then Click OK
To get MVC to work under IIS 6.0 you need to make a small adjustment in the IIS to use a wildcard mapping for aspnet_isapi.dll. Follow these simple steps: Open IIS manager, expand the IPM site and right click on the IPM Viritual Directory, go to Properties, then Home Directory tab, then click Configuration. Under Wildcard application maps, click Insert (not Add, which is confusingly just above), then enter C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll for “Executable”, and uncheck Verify that file exists.
4. Configure the IPM Subscription Service
The IPM Subscription service that is responsible for sending out alerts and report also needs to use the same user we just configured. The IPM installer installed the service so all we need is to configure it to use the correct user account.
5. Setting up the database connections
The IPM installer created a “Communicate BizTalk Tools/Integration Platform Monitor” folder on the start menu. In this folder there is a Service connection shortcut and a Web connection shortcut.
Use these to open the configuration document to set the connection string to the “BizTalkMgmt” database.
If the “BizTalkMgmt” database is not on the local machine the data source needs to be set to the server where the BizTalkMgmt can be found.
<connectionStrings>
<add
name=”BizTalkMgmtDbConnectionString”
connectionString=”Data Source=.;Initial Catalog=BizTalkMgmtDb;Integrated Security=True”
providerName=”System.Data.SqlClient” />
</connectionStrings>
Remember to change this setting for both the “Web connection” and the “Service connection”!
If you are using SQL Server 2008 R2, you have to give the “Biztalk Server Administrators” group or the user running the application pool explicit db_datareader rights in the BizTalkMgmtDb database
6. SMTP settings etc
In the start menu there is also a Web settings shortcut and a Service settings shortcut. In the Service settings configuration document one needs to define the SMTP configuration that should be used to send alerts and reports.
In the Web settings one needs to configure the correct path to the BM.exe and the BttDeploy.exe. These are by default configured for the default installation path of BizTalk 2006.
7. Troubleshoot the installation
Start your browser and point it at “http://localhost:19972/IPM” directly on the server you have installed it on. If there are any exceptions these will be displayed directly in the browser (as you are browsing locally).
IPM also logs all exception (both on the Subscription service and the IPM web to the application log). Each of the components also logs to a log file that is located under folders in the installation path chosen in the installer. And as always – do not hesitate to contact our support group if you have any question on the installer or the product in general.
