(I wrote this article a while back before I had my own tent in the blog-o-sphere. I am copying it here since I now have my own, and the content is still relevant)

 

If you see none of the artifacts discovered under the BizTalk 2010 Management Pack's views, check the Operations Manager event log on the first server in the BizTalk group. The MP discovery performs discovery of artifacts by default ONLY on the first machine added to the BizTalk group. Check the event for errors in BizTalk discovery, after a re-start of the System Center Management Service.

   

If you see:

   

Event ID: 21406

Source: Health Service Modules

Log Name: Operations Manager

Level: Warning

   

The process started at hh:MM:ss PM failed to create System.Discovery.Data. Errors found in output:

   

C:\Program Files\System Center Operations Manager 2007\Health Service State\Monitoring Host Temporary Files 1\496\Microsoft.BizTalk.Server.2010.BizTalkRoleDiscovery.vbs(87, 5) (null): 0x80131904

   

Command executed:     "C:\Windows\system32\cscript.exe" /nologo "Microsoft.BizTalk.Server.2010.BizTalkRoleDiscovery.vbs" {DFE02236-093D-1771-7E8E-56887C699C80} {9DBABE54-0EC0-D877-AD6F-9B43EF77738D} SERVERNAME.Enterprise. SERVERNAME 2

Working Directory:          C:\Program Files\System Center Operations Manager 2007\Health Service State\Monitoring Host Temporary Files 1\496\

   

One or more workflows were affected by this. 

   

Workflow name: Microsoft.BizTalk.Server.2010.RuleEngineRole.Discovery

Instance name: SERVERNAME.Enterprise.DOMAINNAME.Global

Instance ID: {9DBABE54-0EC0-D877-AD6F-9B43EF77738D}

Management group: DOMAINNAMESCOM

   

   

This means discovery is failing to execute. In most environments the default action account of SYSTEM will not have sufficient privileges to perform BizTalk discovery. The BizTalk Management Pack configures two Profiles: BizTalk Server Discovery Account, and BizTalk Server Monitoring Account. Much like the configuration for the SQL MP, you must provide accounts for both of these Profiles, with sufficient privileges to discover and monitor BizTalk. The privileges at least need to be member of BizTalk Operators Group, but for some tasks members of BizTalk Administrators Group. Refer to the BizTalk 2010 MP guide for details on security privileges.