Where to store Adapter variables?
From: Mark Shasby (mark_at_shasby.com)
Date: 07/15/04
- Next message: Roman: "BizTalk Document Tracking Mess"
- Previous message: Darren Osborne: "Re: AssemblyName context property was not valid"
- Next in thread: Adrian Hamza[MSFT]: "RE: Where to store Adapter variables?"
- Reply: Adrian Hamza[MSFT]: "RE: Where to store Adapter variables?"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 15 Jul 2004 11:11:13 +0100
Hello,
I have written a custom adapter that interfaces to several business
departments within several companies, potentially well over 50 different
combinations. These companies/departments have differing transport
parameters, such as character encoding, encryption, compression etc.
Where is the best place to keep these parameters?
1: They could be added as different receive locations but that involves
quite a lot of redundancy as most of the parameters in each receive
location will be the same.
2: They could be stored as trading partner agreement addendums in BAS
but I get the impression that is only really meant for for
communications that use Sharepoint HTTP?
3: They could be stored in an SQL table somewhere.
4: Any other suggestions..?
What is the Microsoft-intended way to store these parameters?
- Next message: Roman: "BizTalk Document Tracking Mess"
- Previous message: Darren Osborne: "Re: AssemblyName context property was not valid"
- Next in thread: Adrian Hamza[MSFT]: "RE: Where to store Adapter variables?"
- Reply: Adrian Hamza[MSFT]: "RE: Where to store Adapter variables?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|