Do You Have Any Tips About Load Balancing, Failover and Clustering for ActiveADAPTER?

Active Directory Send Adapter

If you create multiple host instances for the host that acts as the send handler for ActiveADAPTER, BizTalk will generally take care of failover for you with send ports.  BizTalk will distribute messages to the host instances in a round robin fashion, and if one is down it will try the next. See your BizTalk documentation for more information.

Active Directory Receive Adapter

The best way to think about ActiveADAPTER receive locations and failover is to treat them like FTP receive locations. Microsoft has a number of documents dealing with failover and clustering solutions for FTP receive locations and these architectures will typically apply to ActiveADAPTER receive locations. See your BizTalk documentation for more information.

The use of Host load balancing in NOT recommended for receive locations. The queries performed by your ActiveADAPTER receive locations do not lock Active Directory results and if run on different host instances as part of load balancing may result in duplicate messages into your receive ports.


As mentioned above, the best way to think about ActiveADAPTER in terms of clustering architecture is like the FTP adapter. There are a couple of useful resources about adapters and clustering at:

In the second article Kent Weare discusses Active/Passive clustering that can offer redundancy with just the one BizTalk host – “host clustering”.

We are interested in purchasing ActiveADAPTER for use by government or government contractors. What are the export conditions for ActiveADAPTER?

ActiveADAPTER was originally developed by Equate IT, a company registered in Australia. All developers and consultants have Australian or US citizenship. More information can be found in the EULA displayed during installation of ActiveADAPTER.

See the entire answer

Will the ActiveADAPTER Send Adapter return error information back to my orchestration?

Yes. The adapter will return any exceptions back to your application AFTER any retries you have configured have been done.

Within your orchestration you can use Scope shapes to catch exceptions. In your exception handlers you can retrieve the error description to determine which way to branch.

Sample orchestrations that illustrate exception handing are included in the ActiveADAPTER Samples folder.

See the entire answer

What transactional strategy does the ActiveADAPTER Send Adapter use?

The Send Adapter commits changes per message and per object. This means commits cannot span messages. Within a message, changes to an object are all committed together. To ensure changes are all or nothing, therefore, the strategy you need to use is one message per object.

See the entire answer