ORCHESTRATIONS in Visual C#

Making PDF 417 in Visual C# ORCHESTRATIONS

Name the variable objSample. Add a description, such as Demonstration Object. Specify the variable s .NET type by clicking the drop-down box for the Type property and selecting <.NET Class>. In the Select Artifact Type dialog box, select the SampleClass class, as shown in Figure 5 24.

Figure 5 24. Selecting the artifact type 6. Drop an Expression shape in the orchestration, and enter the following code to invoke the external assembly, as shown in Figure 5 25.

When creating a .NET class variable in BizTalk, an option exists to Use Default Constructor. This property causes an instance of the object to be constructed when the orchestration instantiates. If this property is set to False, the variable will need to be instantiated in an Expression shape through the new keyword (as in step 6 of the solution). Another property that should be noted is on the referenced assembly itself: Copy Local. This property indicates whether the assembly referenced should be copied into the local bin directory when a project is built. Several factors will help decide whether the assembly should be copied locally; if a reference is to a dynamic assembly (such as another BizTalk project that is built at the same time as the project in which it is referenced), you probably will not want to copy the assembly locally. It is important to note that when calling a .NET assembly that is not marked as serializable, it must be called from an atomic scope. When creating an assembly that will be used primarily by BizTalk, it is appropriate to mark all classes as serializable. The following example demonstrates doing this in C#. [Serializable] public class Example { }

You have messages that conform to several different schema types. You wish to create a single orchestration to consume the messages and process them in a generic fashion.

BizTalk orchestrations deal with messages that are strongly typed. A strongly typed message conforms to a selected BizTalk schema or .NET class, and the message inherits its properties from this schema or class. An untyped message is configured to use System.Xml.XmlDocument as the message type and is not tied to a specific schema. For example, a large business may receive purchase orders from several different systems, and each message must follow the same processing steps. Although the messages are similar, they differ in minor details and are strongly typed to different schemas. In order to process the messages from these disparate systems using the same process, you may wish to define a process with an untyped message to receive the different purchase order schemas into the same receive port.

Note It is important that you have a basic understanding of receiving messages prior to implementing untyped

To create an untyped message and use it within an orchestration, take the following steps: 1. In the Orchestration View window, expand the top node of the tree view (this node will have the same type name as the orchestration) so that the Messages folder is visible. Right-click the Messages folder, and select New Message, which creates a message. Click the new message, and give it a descriptive name in the Properties window. In this example, the message is named incomingOrder. Click the Message Type property in the Properties window, and select the .NET type System.Xml.XmlDocument. From the toolbox, drag a Receive shape onto the orchestration directly beneath the green circle at the top of the design surface. With the Receive shape selected, specify the shape s Name, Message, and Activate properties. In our example, we use ReceiveOrder, incomingOrder (created in step 3), and True, respectively.

2. 3. 4. 5. 6.