Jeff Lynch [MVP]

Sponsors

The Lounge

Wicked Cool Jobs

Advertisement

Images in this post missing? We recently lost them in a site migration. We're working to restore these as you read this. Should you need an image in an emergency, please contact us at imagehelp@codebetter.com
BizTalk Server 2006 R2: To Boldly Go Where No Man Has Gone Before!

This week I’m going to embark on a dark and mysterious journey, fraught with great danger, both real and imagined. I’m about to begin development of a BizTalk Accelerator for RosettaNet (BTARN 3.5) project with the assistance of Microsoft Consulting Services. For those of you experienced in BizTalk development, you’ll understand my trepidation. For those of you familiar with RosettaNet (RNIF), you’ll understand my sheer terror!

If I survive this ordeal, I promise to post about my experiences, so that future generations of BizTalk developers don’t make the same mistakes, don’t fall into the same traps and don’t lose what little is left of their rapidly graying hair!

Stay tuned!


Posted Mon, Jun 9 2008 9:53 AM by Jeff Lynch

[Advertisement]

Comments

Will Shaver wrote re: BizTalk Server 2006 R2: To Boldly Go Where No Man Has Gone Before!
on Mon, Jun 9 2008 12:31 PM

At least your hair is graying... I'd take that over the full on retreat that my hair is doing.

Hemant Bhadane wrote re: BizTalk Server 2006 R2: To Boldly Go Where No Man Has Gone Before!
on Mon, Jun 9 2008 11:40 PM

Hey Jeff,

I can completely understand your "sheer terror"

Incase I can help you any way (delegate some work) let me know,I will be more than glad to help.

I have written few Custom Adapters previously, but not as complex as RosettaNet though...

All the Best Buddy.

-Hemant Bhadane

MCTS BTS 04 & 06

luckybiztalker.weebly.com

Jeff Lynch wrote re: BizTalk Server 2006 R2: To Boldly Go Where No Man Has Gone Before!
on Tue, Jun 10 2008 9:11 PM

Will,

Sorry about that man! Don't fret. My kids tell me the "Steve Jobs" look is in!

Jeff

Staci Butler wrote re: BizTalk Server 2006 R2: To Boldly Go Where No Man Has Gone Before!
on Wed, Jun 11 2008 1:25 PM

The level of difficulty will be based on your trading partner and what system they are using to read your RNIF headers and payload.  It's really not that hard on the Biztalk side.  If you are using the 3.5 accelerator make sure you get the hotfix that fixes the attachement boundary issue.  Biztalk leaves the "< >" symbols off of the attachment identifier in the MIME message and some partners may not be able to find it.  GOOD LUCK!

Jeff Lynch wrote re: BizTalk Server 2006 R2: To Boldly Go Where No Man Has Gone Before!
on Thu, Jun 12 2008 9:31 AM

@ Hement - Thanks for the offer. I'll let you know if I get stuck.

Jeff Lynch wrote re: BizTalk Server 2006 R2: To Boldly Go Where No Man Has Gone Before!
on Thu, Jun 12 2008 10:06 AM

@ Staci - Thank you very much for the hotfix tip. Our implementation is async, double-action, signed but not encrypted over https. The payload is a non-RosettaNet document (PIDX P21 PIP) with a binary (PDF) attachment.

Loads of fun!

Community Blogs wrote RosettaNet: Who Invents This Stuff?
on Mon, Jun 16 2008 1:50 AM

Captain Picard - “Admiral, we’ve engaged the Borg” Day 2 in my RosettaNet development project and all

Staci Butler wrote re: BizTalk Server 2006 R2: To Boldly Go Where No Man Has Gone Before!
on Mon, Jun 23 2008 1:52 PM

I am all too familiar with the PIDX invoice.  I'm surprised you are signing the message.  All of my trading parnters that use PIDX via RNIF do not.   Hope the project is going well.

Staci

Jeff Lynch wrote re: BizTalk Server 2006 R2: To Boldly Go Where No Man Has Gone Before!
on Tue, Jun 24 2008 3:17 PM

@ Staci - How do you guarantee non-repudiation if the message isn't signed?

Staci Butler wrote re: BizTalk Server 2006 R2: To Boldly Go Where No Man Has Gone Before!
on Mon, Jul 21 2008 11:42 AM

Hi Jeff - Unfortunately you cannot.  The messasge will only go into the non-repudiation database if it is signed because that is how Biztalk knows who it is from.  I'm guessing non-repudiation is not a big deal for my trading partners.  Most of my trading parnters who use RNIF also use Client Authentication on the HTTPS request to perform trading partner validation.  

Devlicio.us