Integrating Integrators – BizTalk, Windows Azure, Windows Workflow, and Beyond
Join
Sign in
Search Options
Search Everything
Search BizTalk 2004
Home
AppFabric
BizTalk Server
Windows Azure
Windows Workflow
Jobs (Hire A Guru)
More ...
Home
»
BizTalk Server
»
BizTalk 2004
»
BizTalk 2004 Forum
»
partners with different transport type and address
partners with different transport type and address
BizTalk 2004
This group is for all content related to BizTalk Server 2004. This includes a forum, samples, videos, labs, whitepapers, and tools. Most of the content here also applies to other versions of BizTalk beyond 2004.
Get this RSS feed
Home
Forum
Files
Sitewide Application Navigation
Home
Blogs
Media
Forums
Wikis
Groups
Details
1
Reply
0
Subscribers
Posted
over 8 years ago
Options
Subscribe via RSS
Share this
BizTalk 2004 Forum
partners with different transport type and address
rated by 0 users
This post has
1 Reply |
0
Followers
Posted by
Anonymous
on
Sun, Oct 9 2005 9:24 AM
partners with different transport type and address
Hi ,
In our company I intend to send order messages to our trading partners,
Partners are recognized by source file name of the incomming message.
We should send messages by email or ftp (depending on our partners limitations) using orchestration.
Would you tell me how and where can I define partner’s communication type (email,ftp) , and how can I direct messages to the right sent port in my orchestration?
Thanks
Arman
Edit tags
Edit
Reply
Posted by
Stephen W. Thomas
on
Mon, Oct 10 2005 7:22 PM
partners with different transport type and address
Hello.
I think you can do with a new different ways.
One way is just to set up a Send Port for each Partner with the correct transport type. The, use direct binding out of the Orchestation and route the messages to the correct trading partner based on SourceFileName. Just make sure you set up the subscriptions right otherwise you will get into an endless loop.
Another way to do it is to use Role Links. This way, you set up one Role for each partner. Then, you define a property to route your message to the Role (in your case SourceFileName). Then, you add the Send Port for the partner into the Role. This way you have a lot less risk in routing errors but you have a little more work to do.
Hope this helps.
Stephen W. Thomas
http://www.BizTalkGurus.com
Reply
Page 1 of 1 (2 items)