Machine.config file use
Web Server forum
Back To The Forum Home!Search!Private Messaging System

Web Server Talk Web Server Talk > Web Servers reviews > BizTalk Server > BizTalk Server > Machine.config file use




  Last Thread   Next Thread Next
  Show Printable Version Email this Page Subscribe to this Thread      Post New Thread    Post A Reply      

    Machine.config file use  
jss


View Ip Address Report This Message To A Moderator Edit/Delete Message


 
07-15-04 10:50 PM

We will be receiving many variations of a flat file message document.   As p
art of that process we will need to interpret the first 12 characters of the
 flat file.  Depending on the code, the corresponding schema will be chosen.
   One approarch was to add
settings in the machine.config file.  Something similar to this:

<appSettings>
<add key="        FH32" value="http://TransactionBroker_BG.schCIS_FH32_FF_BG
#FH32" />
<add key="CISUnknownMessageType" value="http://TransactionBroker_BG.schCIS_G
eneric_FF_BG#CISGenericMessage" />
<add key="CISMessageTypeIndicatorLength" value="12" />
</appSettings>

Is this a good design choice or is there a more appropriate place to put thi
s type of code?





[ Post a follow-up to this message ]



    RE: Machine.config file use  
Gilles [MSFT]


View Ip Address Report This Message To A Moderator Edit/Delete Message


 
07-15-04 10:50 PM

Hello,

>We will be receiving many variations of a flat file message document.   As 
part of that process we will need to interpret the first 12 characters of th
e flat
>file.  Depending on the code, the corresponding schema will be chosen.   On
e approarch was to add settings in the machine.config file.  Something
>similar to this:
>
>	<appSettings>
>            <add key="        FH32" value="http://TransactionBroker_BG.schC
IS_FH32_FF_BG#FH32" />
>            <add key="CISUnknownMessageType" value="http://TransactionBroke
r_BG.schCIS_Generic_FF_BG#CISGenericMessage" />
>            <add key="CISMessageTypeIndicatorLength" value="12" />
>    </appSettings>
>
>Is this a good design choice or is there a more appropriate place to put this type 
of code?

I would suggest you write a csutom disassembling pipeline component which ex
poses a collection of name/values pairs as properties.
Your component can then look at the first 12 bytes, emit the right XML and p
romote the right namespace so further processing can be done.

As far as your config values are concerned, you can expose them as propertie
s of your cusotm pipeline (collection of name/value pairs).
They will be stored with the pipeline component properties (in Biztalk confi
g db) and you will be able to change them at runtime, using WMI.

Thanks,
-Gilles.







[ Post a follow-up to this message ]



    Sponsored Links  




 





   All times are GMT. The time now is 10:12 AM.      Post New Thread    Post A Reply      
  Last Thread   Next Thread Next


Most Popular forums 

Forum Jump:
Rate This Thread:

Forum Rules:
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is OFF
vB code is ON
Smilies are ON
[IMG] code is OFF
 
Medical and Health forum | Computer Games Reviews | Graphics design forum

Back To The Top
Home | Usercp | Faq | Register