ansaurus

Question

Approach to extract inner-schema XML values for mapping to orchestration's inbound schema

Answer 1

A:

Hi, I have some questions, am I correct that the actual xml you are extracting from the DB2 database will be something like:

<DB2Message>   
  <MESSAGE_DATA>   
    <EAIMessage>  
    <Header>  
    <ServiceID>  
    <MessageID>  
    ....  
    <Mode>   
    <Header>   
    <Body>    
    <RawXML>   
    <Body>  
    </EAIMessage>  
  </MESSAGE_DATA>   
  <MESSAGE_DATE>   
  <MESSAGE_ID>   
  <TXN_ID> ....  
<DB2Message>

What is meant to be in the RawXML element?
What does the schema you use to parse this into BizTalk look like - do you use CDATA to escape the contained XML?
Will the XML within the Message_Data element always match a known schema?

David Hall 2008-11-01 07:53:22

The XML inside MESSAGE_DATA is not 100% matching the EAIMessage schema that the orchestration expects. But in general principle is somewhat like what you listed. So there has to be some mapping involving to place the fields correctly into an EAIMessage. RawXML is to take in MESSAGE_DATA as is.

icelava 2008-11-02 04:22:29

So, in the schema that you use to extract data from Oracle, you have as xn:Any element (MESSAGE_DATA) that contains something like the EDIMessage? And Raw XML is just mapped as is?Does the xml fragment in MESSAGE_DATA match any schema, or can it change beyond a schema definition?

David Hall 2008-11-04 02:53:18

Sorry, I found out in the actual project implementation, the DB2Message schema is _attribute_ based, not element based. I am updating my post above.

icelava 2008-11-05 02:21:07

Answer 2

A:

I would suggest looking into envelope schemas to 'unwrap' the interior message from the outer message. I believe the envelope can promote properties from the envelope into the inner message's context as it moves through the receive pipeline. The inner message will then have to map to a schema of its own type. You will then be able to route or make decisions based on the schema type and use XPath to pick out whatever you need. Have not tried all of these things, but I am certain the functionality exists to do do this.

ChrisLoris 2008-12-05 04:15:11

Answer 3

A:

Chris is correct - it seems it's only the inner part of the message you actually care about, the outer part is just an envelope.

As such I would suggest you create a disassembler which, in the receive pipeline, will strip out the envelope (you can keep it in it's entirety as a context property and/or extract some bits from it as individual properties, if you need to act on them), and extract the inner part which would become the message published into the Message Box.

Now the real message is the one get's processed, but the rest of the send port and any subscriber, and whatever information you require from the envelope flows with it through its context.

Now you have full access to the message and it's properties; if applicable you can deploy a schema for this message, which could have distinguished properties which would give you quick access to some (simple type) nodes. alternatively you can use xlang/s xpath to extract the information.

If your embedded message was inside an element in the envelope you could certainly use the built in XmlDisassembler to do all of this (you would just need to deploy your schemas correctly and configure the component accordingly; I'm not sure how well this works with a message contained within an attribute, but it's probably worth a try.

Worst case you are looking at writing a custom disassembler that would strip the envelope and then call the built-in disassembler to process the internal message, but that should not be too much effort as well.

Yossi Dahan 2008-12-06 14:20:55

ansaurus

tags:

views:

answers:

Approach to extract inner-schema XML values for mapping to orchestration's inbound schema

related questions