November 2005 Entries
The project I am working on will connect a new partner (with new messaging standards) to our existing BizTalk hub. Because the new project and the already existing operations share the same message types (whithin the organization), we decided to give the message types an upgrade. One of the main reasons for this is the problems we had before, connecting BizTalk to a Siebel system. BizTalk uses as a message type identifier the root node name and the namespace of a message (and the port to which it...
Some processes I have been implementing recently are long-running by nature. Between start and completion of the orchestration, several days can pass. This is because user intervention is required in another system. I classified the orchestrations as "long-running". The main scope of those orchestrations, created to catch any exceptions, was also set to "long-running". Because I required orchestration variables in a specific part of the orchestration, I was forced to create a nested (small) scope,...
Suppose you have multiple orchestrations that you want to deploy and start, and you bind the ports dynamically. Then, you might want to bind different receive shapes in the orchestrations to the same receive port. Is this possible? In general: yes. There is no real limitation to multiple orchestrations listening to the same receive port, if only each receive shape on that port listens to a different message type. The message type is the combination of: Root node name Namespace When you attempt to...
At this moment, I am working on a project for realization of integration with an external message hub, using BizTalk 2004 on our side. The external message hub is using EDI-like standards for message content that have been elevated to XML. One of the rules is that the exact message size (in bytes) has to be specified for each message we send to this hub. Note that the message size has to be specified as a tag value in the message itself! This problem challenged me, because the calculation to do this...