I think I must be having a WordPress day…
Following on from the upgrade to 2.1.2 earlier this morning (and a successful technical interview for a BizTalk job in London!) I’ve also upgraded the my theme to better use the post column for images.
This new theme is based on ‘Origami’ developed by Leevi Graham and Tim […]
Brian Wilson has started a nice series on event handlers in SharePoint 2007, first episode: Everything you need to know about MOSS Event Handlers.
I’m already looking forward to episode 3: Free Add-on : Site Settings – Manage Event Handlers. It sounds like a nice replacement for Patrick’s tool: Event Handler Explorer! 🙂
Microsoft has been doing tons and tons of improvements in their documentation..The latest one , which caught my attention is that they have documented some common tasks occurring in general BizTalk Development. Check them out here:
http://msdn2.microsoft.com/en-us/library/aa548054.aspx
Enjoy.
Check out the cool Code Samples on BTS 2006 at MSDN:
http://msdn2.microsoft.com/en-us/biztalk/aa937647.aspx
Featured Samples
BizTalk Server 2006 Code Samples Collection
This file contains all of the BizTalk Server 2006 samples for easy download. It is updated as new samples are published.
Integrating BizTalk Server 2006 and Windows Workflow Foundation (BizTalk Server Sample)
This sample demonstrates how to integrate Microsoft BizTalk Server […]
As reported on Slashdot and on the WordPress.org blog, the 2.1.1 release of the WordPress blogging system was hacked sometime towards the end of February/beginning of March.
The hacker gained user-level access to one of the servers that powers wordpress.org, and modified two files to include code that would allow for remote PHP execution. Although details […]
I’ve received a number of questions regarding a sample I posted a while ago: Arbitrary
Binary Attachments to Multi-Part Messages; mostly related to issues when sending
the resulting messages through the SMTP adapter and not all attachments (or no attachments
at all) getting to the destination account.
I’ve found that usually, this is the result of setting the SMTP.MessagePartsAttachments
property to the wrong value. In the sample I posted alongside the article, I was setting
the property to 2. I didn’t give any explanation about it at the time, but
contrary to what it may intuitively appear, you don’t set this property to the number
of attachments (parts) you want to send alongside the message.If you attach 4 different
parts to the message, you don’t set the property to the value 4.
Instead, the value 2 means “Send all parts as attachments”, which is exactly the behavior
you want. For completeness sake, here’s what each possible value for this property
means (taken from the BizTalk
documentation):
So I’ve built a “BizTalk For Business Analysts” class that I’m delivering next week to 20 or so of my new co-workers. We’re covering the basics of BizTalk, and I’ve built three lab exercises that deal with the Orchestration Designer for Business Analysts, using SharePoint/InfoPath with BizTalk, and building and consuming BAM models. […]
This week’s post is brought to us by Suraj Guarav, our EDI/AS2 development lead for R2:
A new feature coming up in Beta 2 (also in Feb CTP but with limited test coverage) is the ability to dynamically modify the list of allowed values in envelope ID fields.
A typical customer scenario could be that there is a unique sender and receiver qualifier that two trading partners use which is outside the set of values defined by the X12 standards body. In such a case, the allowable values that appear in the drop-down lists in the EDI Properties in the Partner Agreement Manager (PAM) for ISA05 and ISA07 need to be extended to incorporate the additional acceptable values.
Customization Using Extended Service Schema
The EDI system pulls the list of allowed values from static service schemas in the Microsoft.BizTalk.Edi.BaseArtifacts dll that ships with R2. There is one schema each for X12 and Edifact. To extend the base set of values, a service schema extension needs to be developed and deployed. Service schema extension templates for X12 and Edifact ship with the product and are located at Microsoft BizTalk Server 2006\XSD_Schema\EDI. They are called X12_ServiceSchemaExtension.xsd and Edifact_ServiceSchemaExtension.xsd respectively.
To extend ISA01 field, create a Biztalk project and add the X12 Service schema to it. In case a service schema has been deployed previously, it should be used as it may contain extensions to other envelope fields.
Add values to the ISA01 collection. Similarly, other fields in the schema can be modified as well. Once the changes are done, deploy the schema in the current BizTalk group. It should have the same namespace and root node name as the original extension schema that came with the product. After the schema is deployed, new values would be recognized throughout the system. They would show up in Partner Agreement Manager and runtime processing would also employ these values during validation. In addition, XML tools (e.g. validate instance) would also make use of these values for validation.
Only the list of fields that can be customized are present in the extension schemas. Addition of any new field in the schemas would not have any impact on system’s behavior, they would simply be ignored. Additionally, it is not possible to delete a value from the base service schemas. Customizing envelopes is additive only!
Thanks Suraj!
Cheers,
Tony