Posts

Showing posts with the label BizTalk 2006R2

Using the BAM API to write BAM events from orchestrations

One of the easiest ways to update a bam activity from an orchestration is to use the BAM API, Simply add reference to Microsoft.BizTalk.Bam.EventObservartion Microsoft.BizTalk.Bam.XLANGs to your project and you are ready to start. In the basic level you have to start, update and end an activity. Start Activity I reccomend creating variables for activity name and instanceID, To avoid any confutions. The Activity name must match the Activity name created and deployed using bm.exe. (I will create a seperate post for this) The code in start-bam-expression-shape in orchestration PreProcessInvoice will then look something like this: activityName = ("ProcessInvoice"); //this is the activity we are loading data into activityInstance = System.Convert.ToString(System.Guid.NewGuid())+"PreProcessInvoice" ; //if bamming to same activity from different orchestration, we may track where the data is comming from by adding orchestration name. Microsoft.BizTalk.Bam...

The Messaging Engine failed to register an adapter "WCF-BasicHttp". Details: "Registering multiple adapter types within the same process is not a supported configuration. For e.g. HTTP and SOAP receive adapters cannot co-exist in the same process

Image
When deploying a wcf service to biztalk the is a good chance you will run into: The Messaging Engine failed to register an adapter "WCF-BasicHttp". Details: "Registering multiple adapter types within the same process is not a supported configuration. For e.g. HTTP and SOAP receive adapters cannot co-exist in the same process" Solution When installting a SOAPm HTTP or WCF service on the same WebServer then seperate app pools must be created for each adapter. Using seperat app pools will solve the issue. Note the this is only a problem om win servers as desktop version of windows does not have an app pool concept.

Configuration Display Error for SQL-Adapter

Image
I just found an issue in the SQL-Adapter for BizTalk 2006R2. It seems that there are different values for displaying the configuration and for the actual configuration. Here is an image showing how it looks like when you open the SendPort to view the details. Don`t trus this view! Here is the actual configuration for the same SendPort with the actual configuration used runtime. If your bindignfile is not 100% acurate you could end up with different values for displaying the configuration and the actual configuration.  As you can see from the images two different values are in the system, but it is the actual configuration that is used. This may happen if you manually update the bindigfile, but forget to update all the entrys for database/queue information.  I have been told that it is the same for MQ-Adapter and even on the BizTalk 2010, but I have not verifyed this