by community-syndication | Dec 8, 2006 | BizTalk Community Blogs via Syndication
I’ve finally made a release of BizUnitExtensions. R1 BETA is targeted at Biztalk 2004. It consists of the core BizUnit product (source and tests) as well as the Extensions (source and tests). The core code base has been bug fixed (for all steps we used in our projects). The tests for the core code base have been completely revamped. All XML comments were thoroughly revised (again, this was done only for steps that we used and we fixed warnings in all other files as well).
If you want to run the provided unit tests please remember that the unit tests are provided as a indicative sample of what may be achieved and not guaranteed to run on your machines. This is because unlike NUnit tests which test the assembly in question and can be assisted by mock libraries, the BizUnit assemblies actually control real orchestrations and other Biztalk artifacts which it is impossible to mock and provide.
The core product for v2006 comes with a sample solution but the v2004 does not (we inherited these products and only bug fixed the code where necessary) so dont accuse us of inconsistency!!We have run a couple of the test steps against the SDK samples and the documentation indicates which these are and you should have them deployed first before using the tests.
The main thing is that the product works for all the steps we used (and there were quite a few that we used). But we didnt use ALL of the steps so it is quite possible that there are still some errors in the code base. Do report them and we will try and fix them. Or alternately if you can step through the code (which is very easy to understand) and provide a fix (and possibly a unit test-if it does not depend on your project assemblies) that would be very useful and we will include that in the code base.
As soon as a few people have used this and are happy that the product basically installs and works fine, we will upgrade it to the RTM release and barring bug fixes, we should be concentrating on v2006 after that, but 2004 WILL NOT be abandoned.
The changes to the core prooduct in v2006 would be a bit of a challenge because we have to merge our fixes from 2004 into the stuff that Kevin has written in 2006 and not lose any fixes he might have made.
We have fairly amibitious plans for v2006 including tests against the official MS tutorial scenarios that are more in-depth as well as some good tutorials based on our projects (without any confidential info of course), so please do support this effort. Theres actually a lot more on the cards, but we will reveal that when we make more concrete progress.
Another thing which would be useful for the community is people writing in to let us know how you are using BizUnit in your projects. Even if you cannot contribute code and support tools (for IPR and other reasons) it would be nice to know how its being used out there.
by community-syndication | Dec 8, 2006 | BizTalk Community Blogs via Syndication
At the project I am working on I mainly use the Event Log to write progress statements from my orchestrations. On my develop-machine I ran into the error message ‘Requested registry access is not allowed’.
It appeared that the user account under which the processing host runs, did not have enough authorisations to access the Event Log.
This can be fixed by giving that user account full control to a certain Registry Key.
To achieve this you must start the Registry Editor (regedit.exe) and navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog. Right click on the node and click ‘Permissions…’.
Next add the user account under which the processing host runs and give this user full control.
Close the dialog and the Registry Editor and finally restart the processing host.
You should now be able to write to the Event Log.
by community-syndication | Dec 7, 2006 | BizTalk Community Blogs via Syndication
(This is courtesy of Ross a collegue of where I’m working onsite currently)
What you need is:
(1) a Send Port with the MSMQ Send Adapter
(2) XMLTransmit pipeline
Within the MSMQ Send Port adapter – set the Body Type to a value of 30 (this
translates back to the Win32 API values and you can look them up for the enumeration,
so it’s not a value of 8=BSTR a trap which we may fall into)
Within the XMLTransmit pipeline – click on the ellipse
to set per instance configuration settings for this pipeline.
Set ‘Include XML Declaration’ =false
Set ‘Preserve BOM…’ = false (byte order mark – the 3 chars that
are a bomb, upside-down question mark etc) so the client wont receive it.
Once this is done – all good!
Your clients who expect just ActiveX formatted messages only, are happy to play with
BizTalk.
Thanks Ross!
