Ali Raza Zaidi

A practitioner’s musings on Dynamics 365 Finance and Operations

Tips and tricks

How to Send File to MSMQ Using C#

by

During the testing of BizTalk application, which read data from MSMQ. I have to write small C# routine, this routine send data to MSMQ.  If you have no knowledge about MSMQ, Please read My Post on this here.
http://www.biztalkhq.com/what-is-msmq-and-how-to-configure-it-on-windows-7/

 

To Send File on MSMQ you have to include the dll System.Messaging in your C# or Vb.net application. To Simplest code is as follow.

 

public void FileToMSMQ(string FilePath, string MsmqName)

{

//FilePath =@”e:test.xml”;

//MsmqName= @".private$testQue";

System.Messaging.MessageQueue _TheQueue = new System.Messaging.MessageQueue(MsmqName);

System.IO.FileStream _FileStream = new System.IO.FileStream(FilePath, System.IO.FileMode.Open);

Message _Message = new Message();

_Message.BodyStream = _FileStream;

_Message.Label = System.IO.Path.GetFileName(FilePath);

_Message.Priority = MessagePriority.Normal;

_TheQueue.Send(_Message);

}
You can down sample code from here

 

 

 

 

Generic fault message exception handling

by

 

In my current project, there are 50 operations on each port. It is very difficult and time consuming to create fault on every port operation and then add exception handler for every fault message.  This solution is not so comprehensive that if fault message is of different type what you made on each port

For example I selected “BTS.Soap_envelope_1__1.Fault on each operation,

than orchestration goes in suspended mode and process left uncompleted.

After too much search if found following exception type.

Microsoft.XLANGs.BaseTypes.UnexpectedMessageTypeException

 

Its works wonder if any fault message return my orchestration process is not break.

 

Pros: Normal exception caught and Orchestration completes its process.

Con: suspended instance of orchestration still visible at BizTalk admin with message “The instance completed without consuming all of its messages. The instance and its unconsumed messages have been suspended.”

What is BizTalk message Type ?

by

All messages in BizTalk are represents in XML. One important aspect of all XML documents is its namespace. Briefly, a namespace allows you describe the Student (for example) in one way without affecting anyone else’s description, possible student can mean different things to other applications, Second important aspect of all XML document is the name of document root node.

For example namespace of student XML is

urn:schemas-BiztalkHQ-net:Student:mapcontext:1

and Root Node of Schema is

Student .

The combination of message namespace and name of root node are represented as:

 

urn:schemas-citrite-net:licensing:mapcontext:1#Student

The hash symbol (#) separates the namespace from the name of the root node.

What is the difference between a Document Schema and a PropertySchema?

by

A property schema enables you to define promoted properties in a common location and have them referenced by other schemas.
A property schema can have a namespace but not records or attributes.
Elements defined in the property schema have a name and type.

The property schema must get deployed to BizTalk Server like all other schemas because the property schema may need to be referenced by more than one schema, and because the information in the property schema must be available to components at runtime.
After a property schema has been created, elements and attributes with the same type can be promoted as one of the named properties in the property schema.
Schema is the meta-data used to describe the content and structure of a Business Document. Implemented by parsers that validate a Business Document’s conformance to the Schema at runtime.
Schemas for business documents do not contain any BizTags but contains only those tags required to support the business transaction, as designed by the publishing organization.

A document schema is used to define a message. It is a definition on an Xml message with optional extensions for flat files, EDI file, etc that enable the parsers to convert the native format into Xml.
A property schema is used to define message context properties. These can be of type MessageDataPropertyBase (the property value is promoted or demoted from/to the message itself) or MessageContextPropertyBase(property value only exists within the message context and can be set by adapters, pipelines or within orchestrations).
If you wish to promote a field from a message into the message context the you need to define a document schema and property schema. In the document schema you promote the required field using the property schema to define the property type that will be used in the message context.
Message context properties are used for content based routing, correlation, modifying message content within orchestrations, etc.

BizTalk 2010 Study resources

by

By now everybody knows that Microsoft BizTalk 2010 is available. In this blog entry I will give a summary of information to get started with BizTalk 2010. Here are the steps:
Get BizTalk 2010 Developer edition
The developer edition is completely free to use for development, demo and testing.
Get BizTalk Adapters
The BizTalk Adapters are used to easily send and receive message from Oracle eBusiness Suite, SQL Server, Oracle Database, mySAP Business Suite and Siebel eBusiness Applications.
Get BizTalk 2010 Documentation
This is all the documentation that you will need to learn and go deeper into the BizTalk 2010 technology.
Get BizTalk 2010 Training Kit
This is probably one of the most important downloads to get started to learn about the new features in BizTalk 2010.
View BizTalk Server Developer Center
Bookmark this site and keep a close eye on this site for all new information about BizTalk.

This should be more than enough to get you started with BizTalk Server 2010. There is allot more to learn about BizTalk, but this will be a good starting point.

Schema Types in BizTalk Server 2010

by

BizTalk server 2010 allow us to define 4 Types of schemas.

XML  Schema:

the most commonly used schema type in BizTalk. Inbound and outbound messages are type of schema. It is a document used to describe the element of real time business entity.  The structure of XML is defined in XSD i.e.  XML schema definition format.  You can define XSD in BizTalk xml editor or you can regenerate it from given xml files. Because XSD is common standard then XSD can be created any XML Editor ie. Notepad ++, dreamweaver.

Flat file Schema:

The Schema base on Flat files. Most application still used comma separated, space separated or position based flat files.  Flat File schema is right option to generate inbound and outbound messages.  Flat files are beyond to capabilities of XSD. BizTalk Server Flat file schema defines a rich set of specific annotation tags that can be used to store all of the required additional information.

This schema format is used to translate all content and properties of flat file message instance into   equaling XML message Instance and vice versa.  Flat file Schema can also be used in BizTalk Mapper to transform incoming flat file message to different xml schema message or other flat file schema message.

Envelope Schema:

Envelope schema is special type of schema. Messages of Envelope type wraps different xml business document into a single xml document.   Envelope schema is used to define with common XML Schema. After xml schema is defined, many properties need to be set to convert xml schema into envelope schema.   Most important of property is “IsEnveloped” property of XML Schema to Yes.

Property Schema:

Property schema is used to store the promoted properties of  BizTalk message. Property promotion is the process of copying specific values form within an instance messages to message context. Form message context these values easily accessible to BizTalk components. These components use the values to perform message routing. These values easily available in BizTalk orchestration and can be alter with respect to message.  Property schema is simple xml schema that BizTalk used to copy promoted values of xml schema between xml instance messages and the message context.