February 2006 Entries
I have noticed that many visitors of this blog have been searching for “multiple receive shapes” or something comparable. Therefore, some of the basics explained below. See also another post here: For each orchestration you design, you will have to make clear how a new instance of the orchestration can be started. This can be done because it is called by another orchestration instance. The most common way of starting a new orchestration instance is by means of an activating receive shape....
Recently, we upgraded the messages exchanged with one of the business partners. The partner used the opportunity to change a few other things on his side as well. We transport the messages back and forth using HTTP. We prefer HTTP (and SOAP) when there is no good reason to choose any other form of transporting the messages. When we tested the changes, some problems arose on the partner's system, receiving the messages over HTTP. It took some testing effort, before we asked the partner to return to...
Custom functoids are very useful for extending the standard mapper toolkit with functionality you always wanted. For the ad hoc problems, there is the scripting functoid which allows you to write an inline script, that will be included in the map's XSLT. The problem here is that the script needs to be repeated for each map link where it is required. Therefore, I decided to write the reusable logic in a custom functoid. There are some excellent blog posts on setting up custom functoids, that I used...
An existing orchestration, that reads Siebel-messages from an MSMQC-queue, maps them, and posts them to a remote http-server had to be upgraded. Together with the upgrade, the performance had to be reconsidered, as the orchestration would be dealing with an increased number of messages. We did some stress tests and found out that it was easy to get the remote http server into trouble. For a test, we dropped ~20 or more message files in a directory on the file system. This directory is read by a test...