Using biztalk as routing service as in WCF 4.0


hi,

 

im wondering if following in possible in biztalk.

 

wcf 4.0 offers routing service accepts raw message , able forward message based on specific criteria, soapaction being obvious one.

response routed back.

 

so clients can send request 1 endpoint (routing service) , receive expected reply.

this works great lightweight approach.

 

 

is there way through biztalk?

we don’t want have deploy schemas generated datacontracts in service in biztalk, have act router (again based on soap action), using pass-through pipelines.

 

 

has tried approach?

if have how has performance been affected compared wcf router service?

advice sould appreciated.

thanks

mcpd

hi,

using biztalk router less lightweight approach, enhance flexibility can route on multiple protocols , technology (through adapters). routing can done message-based based on properties, but since not want deploy schema's have go content-based routing principle using orchestration , xpath (retrieving soap-action). since want use un-typed messages approach follow. regarding performance less performant it's solution pub/sub (biztalk uses database) compared wcf, routing take place in memory. third option (alternative) can using esb toolkit. in end depends want achieve based on requirements , long-term strategy routing solution.

regards,

steef-jan wiggers
mcts biztalk server
http://soa-thoughts.blogspot.com/
if answers question please mark accordingly

biztalk


BizTalk Server  >  BizTalk Server General



Comments

Post a Comment

Popular posts from this blog

Azure DocumentDB Owner resource does not exist

having same error microsoft.azure.documents.documentclientexception: message: {"errors":["owner resource not exist"]} , scenario. when deployed webapp azure , try document docdb throws error. docdb exists in azure , contains document looking for. weird local machine(running vs) works fine. i'm using same settings in azure , local. have , idea this. thanks Microsoft Azure  >  Azure Cosmos DB
Read more

job syspolicy_purge_history job fail in sqlserver 2008

Image
hello guys, when installed sqlserver,it automatically created 1 job name job syspolicy_purge_history. but failed @ step 1. the reason is: date                11/6/2010 2:00:00 am log                job history (syspolicy_purge_history) step id                1 server                mxosv-otsdb01 job name                syspolicy_purge_history step name                verify automation enabled. duration                00:00:00 sql severity                16 sql message id                34022 operator emailed                operator net sent                operator paged                retries attempted                0 message executed user: nt authority\system. policy automation turned off. [sqlstate 42000] (error 34022).  the step failed. have run statement: select msdb.dbo.fn_syspolicy_is_automation_enabled the returned valus 0. what can resolve it? or can delete job manually.   thanks in advance. if haven't things want,be
Read more

Trying to register with public marketplace error with 'Get-AzureStackStampInformation'

when trying register against public azure adfs azure stack error below. logs can found at: c:\maslogs\azurestack.azureregistration.2017-10-12.01-31-23.log  and  \\azs-ercs01\c$\maslogs error occurred checking stamp information: system.management.automation.remoteexception: term 'get-azurestackstampinformation' not recognized name of cmdlet, function, script file, or operable program. check spelling of name, or if path included, verify path correct , try again. @ c:\azurestack-tools-master\registration\registerwithazure.psm1:1106 char:5 +     throw "logs can found at: $global:azureregistrationlog  and  \ ... +     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     + categoryinfo          : operationstopped: (logs can fou... , try again.:string) [], runtimeexception     + fullyqualifiederrorid : logs can found at: c:\maslogs\azurestack.azureregistration.2017-10-12.01-31-23.log  a    nd  \\azs-ercs01\c$\maslogs error occurred chec
Read more