What should you do?

You work as a Microsoft BizTalk Server 2006 developer at Domain.com. You have received instruction from the Domain.com network CIO to start an orchestration for unit testing.

During the course of the day you decide to attempting to start your orchestration from within the BizTalk Explorer View but you consistently get error messages popping up regarding enlistment. You are required to choose what the cause of these errors could be.

What should you do?

You work as a Microsoft BizTalk Server 2006 developer at Domain.com. You have received instruction from the Domain.com network CIO to start an orchestration for unit testing.

During the course of the day you decide to attempting to start your orchestration from within the BizTalk Explorer View but you consistently get error messages popping up regarding enlistment. You are required to choose what the cause of these errors could be.

What should you do?

A.
The orchestration has one or more build errors. The Task List should be checked and correct any build errors before attempting to start.

B.
The orchestration has not yet been enlisted. You need to enlist your orchestration before you start it.

C.
A strong name key file reference is lacked by your orchestration. The Project properties should be opened and on the Assembly tab, enter a Strong Key Name file.

D.
Your orchestration has Send Ports or Send Port Groups bound that have not yet been enlisted. All Send Ports and Send Port Groups bound to your orchestration should.

Explanation:
You should remember in the scenario that if you attempt to start an orchestration bound to Send Ports or Send Port Groups that have not yet been enlisted, you are bound to receive errors.

Incorrect Answers:
A: You should remember in the scenario if the orchestration had build errors it would have prevented a successful build.
B: The orchestration should be started without enlisting it in the scenario as this will be done automatically if the Send ports or Send Ports group are bound to it.
C: In the scenario this lack of a strong key file reference would have resulted in a unsuccessful build.



Leave a Reply 0

Your email address will not be published. Required fields are marked *