I have two orchestrations each handles different types of messages.
For ex, Employee.odx handles of type Exmployee.xsd and Product.odx
handles of messages type Product.xsd

problem description is,
Need to implement broker style orchestration,
1. that receives a both types of messages,
2. constructs messages based on their type,
3. publish newly constructed message to biztalk

my idea is,
An orchestration can't receive two types of messages, it can receive
only one type, so, what i thought for step 1 is,
create a new schema whose instance looks as follows for employee.

<TypeDefinerSchema>
<Type>Employee</Type>
<TypeXml>
<![CDATA[<EMPLOYEE><NAME></NAME><SSN></SSN></EMPLOYEE>]]
</TypeXml>
</TypeDefinerSchema>

This way my broker orchestration can accept any type of input xml.


Next step is constructing message,

With some xpath or promoted properties, I can fetch type of xml
document and xml, I can't really construct with this info.
But, I can do a LoadXml, but this is not helpful to me, as my ultimate
goal is to pubish to biztalk, so that employee orchestration is
started.

To really construct message of employee, i can write a .NET class
method, that takes these 2 params and use reflection to construct
employee message.

>From here on, I really doesn't know, how to return message from .net
class and publish to biztalk.

If any body can show me way, I would really appreciate.

btw, two types and orchestrations is only for example sake, there are
actually 100+ types and orchestrations, so solution needs to be
generic.

Thanks
MeDhanush

[ Post a follow-up to this message ]

MeDhanush,

I'm a bit confused about why you would want a broker orchestration. If each
of your 100+ orchestrations handles a different schema then the broker orch
is just additional overhead that you don't need.

But, to answer your questions:
1. how to return message from .net class - In the broker orch add a
Construct Message shape to create the message that you want to pass. Inside
the Construct Message add a message assignment shape. In the message
assignment shape assign the message you are constructing with the result of
your .Net call (the .Net function will have to return System.Xml.XmlDocment)
2. and publish to biztalk - Once you have created the message you should use
add a "Call Orchestration" or "Start Orchestration" shape. You can pass the
message you created to another orchestration using one of those 2 functions.

Hope that helps.


"medhanush@yahoo.com" wrote:

>
> I have two orchestrations each handles different types of messages.
> For ex, Employee.odx handles of type Exmployee.xsd and Product.odx
> handles of messages type Product.xsd
>
> problem description is,
> Need to implement broker style orchestration,
> 1. that receives a both types of messages,
> 2. constructs messages based on their type,
> 3. publish newly constructed message to biztalk
>
> my idea is,
> An orchestration can't receive two types of messages, it can receive
> only one type, so, what i thought for step 1 is,
> create a new schema whose instance looks as follows for employee.
>
> <TypeDefinerSchema>
>  <Type>Employee</Type>
>  <TypeXml>
>      <![CDATA[<EMPLOYEE><NAME></NAME><SSN></SSN></EMPLOYEE>]]
> </TypeXml>
> </TypeDefinerSchema>
>
> This way my broker orchestration can accept any type of input xml.
>
>
> Next step is constructing message,
>
> With some xpath or promoted properties, I can fetch type of xml
> document and xml, I can't really construct with this info.
> But, I can do a LoadXml, but this is not helpful to me, as my ultimate
> goal is to pubish to biztalk, so that employee orchestration is
> started.
>
> To really construct message of employee, i can write a .NET class
> method, that takes these 2 params and use reflection to construct
> employee message.
> 
> class and publish to biztalk.
>
> If any body can show me way, I would really appreciate.
>
> btw, two types and orchestrations is only for example sake, there are
> actually 100+ types and orchestrations, so solution needs to be
> generic.
>
> Thanks
> MeDhanush
>
>

[ Post a follow-up to this message ]