Biztalk hands-on Experiment (6) orchestration Development

1 course Introduction

Familiarize yourself with orchestration related development and testing technologies through this course

2. Preparations

1. Familiar with XML, XML schema, XSLT, and other related XML Development Technologies
2. Familiar with. Net Development Technology
3. Create a blank BizTalk Project

3 demo 3.1 Use identifiable fields and branch Processes

1. Open inputpo schema, right-click and select promote

1. Add total to the distinguished Field

1. Create an orchestration> inmsg. The message type points to inputpo.
2. Connect the process structure as shown in. Set the first receive-shaped active attribute of the process to true.

1. Click rule_1 and add a condition judgment expression to the condition expression.

Inmsg. Total & gt; 100

1. Generate and deploy programs
2. Configure orchestration, deploy the logical port to the physical provider port, and select xmlreceive for the pipeline of the receiving port.

1. Start the application and copy two different messages based on the XML message generated by inputpo. The total field of one message is smaller than 100, and the other is greater than 100. Check whether the messages are output to different directories.

3.2 exception Compensation

1. Modify the original orchestration, add the scope shape to the process, and drag the Expession and existing decide shapes into the scope, as shown in

1. Create an int type variable in orchestration View

1. Add the following code to the expression of expression_1 or.

Result = system. Convert. toint32 (1/inmsg. Total );
System. Diagnostics. EventLog. writeentry ("orchestrationdevdemo", "Result:" + result. tostring ());

 

1. Right-click scope_1 and select new exception handling.

1. Drag the expession expression into the exception management shape

1. Click the exclamation point of scope_1 and set the transaction type to long running.

1. Click catchexception_1. In the Properties window, configure the object name and type (mscorlib-> system-> exception)

1. Add the following code to expession_2:

System. Diagnostics. EventLog. writeentry ("orchestrationdevdemo", "exception:" + exp. Message );

 

1. Deploy the application and restart the BizTalk instance
2. Use simulated data for testing. The system log contains the corresponding log information.

3.3 call (start) sub-process

1. Create a sub-flow with only one sending shape and a sending port.
2. In the subprocess, add a Message Parameter of the message type.
3. Add a branch condition and use the call or start orchestration shape. Configure the corresponding sub-process and input message
4. Stop all BizTalk applications and then deploy the applications (because orchestration has dependencies)
5. Test whether new conditions are applied and whether messages are output.

Biztalk hands-on Experiment (6) orchestration Development