FAQs
Can the Active Directory Receive Adapter help me build an orchestration that listens for changes to Active Directory?

Yes. The ON CHANGE ONLY option on the Active Directory Receive Adapter provides this feature. A message is submitted to your BizTalk application only when the results of the query you have specified change. This feature provides a great way to trigger orchestrations and keep information in your Enterprise Applications synchronized.

There is also a REAL-TIME mode that gets events from Active Directory asynchronously and submits them to BizTalk  as they happen.

See the entire answer

What is an example of how and why I might use ActiveADAPTER?

Here is an example of one of dozens of high ROI BizTalk applications you can build with ActiveADAPTER.

Suppose Jane is a new hire in your organization.

At the end of the hiring process, HR notify IT operations of Jane's start date. A member of IT Operations (with no Active Directory knowledge) goes to your Service Desk system, raises a new ticket, and completes a simple form about Jane's role in your organisation.

From the information entered, the Service Desk system creates an xml file and submits it to BizTalk. BizTalk uses the information in the message and ActiveADAPTER to:

  • create Jane's Active Directory account
  • synchronize Jane's Active Directory telephone numbers, office location, and Manager's name from the information in HR system entered during the recruitment process
  • set a first-use password for Jane and specify that it must be changed on first logon
  • grant Jane access to the resources she will need by placing her in a number of security groups

On Jane's first day BizTalk uses ActiveADAPTER to enable Jane's account and emails the first-use password to her Manager at 8am.

On arrival, Jane is given her first-use password and logs on with access to everything she needs.

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