in Search

Do you Twitter? Follow us @CodeBetter

Jeff Lynch [MVP]

Everything E-Commerce!

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!

Published Jun 09 2008, 09:53 AM by jlynch

Filed under: BizTalk Server, RosettaNet

Comments

Will Shaver said:

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

# June 9, 2008 12:31 PM

Hemant Bhadane said:

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

# June 9, 2008 11:40 PM

jlynch said:

Will,

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

Jeff

# June 10, 2008 9:11 PM

Staci Butler said:

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!

# June 11, 2008 1:25 PM

jlynch said:

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

# June 12, 2008 9:31 AM

jlynch said:

@ 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!

# June 12, 2008 10:06 AM

Community Blogs said:

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

# June 16, 2008 1:50 AM

Staci Butler said:

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

# June 23, 2008 1:52 PM

jlynch said:

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

# June 24, 2008 3:17 PM

Staci Butler said:

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.

# July 21, 2008 11:42 AM

Name (required)

Your URL (optional)

Comments (required)

Remember Me?