The Management Pack automatically discovers instances of the BizTalk service running within the Operations Manager 2007 management group, and deploys the BizTalk monitoring agent to those servers (aka Monitored Systems). Once the agents have been deployed, they automatically begin monitoring BizTalk applications for performance and exception issues.
The agent monitors for problems in the .NET elements of BizTalk applications, as indicated on the diagram by . These elements include adapters, pipelines, maps and orchestrations. With the AVIcode .NET MP also installed, you can monitor .NET Windows Services, Web Services and COM+ components that your BizTalk application communicates with, or any other ASP.NET application hosted under IIS.
Once the Application Management Pack has been installed, it initiates a 2-level discovery process for BizTalk servers and components:
Information about BizTalk adapters, applications, maps, orchestrations and pipelines is stored in the BizTalk database. In order for the discovery script to access this information, it must have access to the database server and the BizTalk database. Because the discovery script normally runs under the local system (action) account, it may not have the appropriate permissions to access the database, but can be granted access by correctly configuring the 'Run As' profile. If discovery does fail, correct the Run As account information, and force discovery to take place (see below for information on how to know when discovery has failed and about forcing discovery to take place).
The members of the .NET Enterprise Agent Deployment Group were selected when the Management Pack was installed. To modify the group membership:
To add Explicit members to the group, select the Explicit Members tab.
To add Dynamic members to the group, select the Excluded Members tab.
To Exclude members from the group, select the Dynamic Members tab.
You can determine whether discovery for adapters, applications, maps, orchestrations and pipelines has failed if:
If discovery fails for any adapters, applications, maps, orchestrations and pipelines, several methods can be used to correct the configuration of the discovery account. There are two methods for ensuring that there are sufficient permissions to complete the discovery process: Configure a run-as account, or add permissions to the local computer (action) account.
Configure a 'Run As' profile
You will need to use an account from either the BizTalk Operators Group or the BizTalk Administrators Group to configure as the 'Run As' profile for BizTalk discovery. You may: 1) select an existing domain account from one of the groups, or 2) create a new domain account and add it to one of the groups.
To configure the 'Run As' profile to use the selected account:
Add permissions to the Action account
To add permissions to the action account, you can either make the action account a member of either the BizTalk Operators Group or the BizTalk Administrators Group, or give the action account permissions for the BizTalk management database.
If the action account is the Local System account, then use the computer account when adding permissions.
If discovery for adapters, applications, maps, orchestrations and pipelines fails, it will normally take 6 hours before a new discovery attempt takes place unless discovery is forced.
Forcing Discovery Method #1
Forcing Discovery Method #2
This method requires changing the discovery interval to 1 minute (for example), waiting for the next discovery, and then changing the discovery interval back to 6 hours. This method is much longer, but no any harmful operation is done during it.
When monitoring is initially enabled for BizTalk applications, the default configuration is as follows:
The agents may be configured via the actions in the Operations Console.
If the actions are not visible, select 'View''Actions' in the Operations Console. Actions may be applied to orchestrations, pipelines, adapters, maps, or applications as a whole.
To select an object to apply an action to:
BizTalk Hosts state view
BizTalk Server state view
Last update: Thursday, December 09, 2010 09:42:11 AM