Yet another

When compiling an orchestration I get an error saying .

Error 1 illegal use of identifier '' in an expression wher the '' have some value. 

This is actually me setting an initial value for a a string variable. You need to put the initial value in "initialValue" quotemarks



I had forgotten this, so i spent some time rememering/trying different stuff and document it here so you dont have to,





Comments

Post a Comment

Popular posts from this blog

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.



Read more

Fully Qualifyed Name

Image
From time to time one need to use the fully qualifyed name for an assembly in Biztalk. This is valid for all versions of BizTalk.

The correct syntax in this case is : "+ ,"

An example for this would be if you need to validate the xml upon the receival, and you need to use the XMLReceive pipeline that ships with BizTalk.

You then need to add teh Fully Qualifyed name to The DocumentSpecNames in the configuration shown below. Remember that if you use the RootNode name this is capital sensitive.


If you dont do this you will get the famous : No Disassemble stage components can recognize the data. error


There was a failure executing the receive pipeline: "Microsoft.BizTalk.DefaultPipelines.XMLReceive, Microsoft.BizTalk.DefaultPipelines, Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" Source: "XML disassembler" Receive Port: "" URI: "" Reason: No Disassemble stage components can recognize the data. 

Read more

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.EventObservartionMicrosoft.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.EventObservation.Orchest…
Read more