community-content

Forum Replies Created

Viewing 15 posts - 3,661 through 3,675 (of 9,648 total)
  • Author
    Posts
  • in reply to: XML debatching (long) #20945

    You’re exactly right in your last edit Bart: the envelope schema (your customerSchema) will debatch at the entry level, creating multiple document schemas (your customerSchema without the root node); you then need to map your document schema to a final schema which includes the root node, but one which only allows one entry element (your outSchema).

    If you are using an orchestration, you will need to accept the debatched document schema (your customerSchema without the root node) in the Receive Shape and map from this schema to your final schema (your outSchema). The when debatching, XmlDisassembler component in your pipeline will locate your envelope schema with details on how to debatch the message, but the actual output from the component will be several individual (debatched) messages.

    Hope this all makes sense, and congrats for getting the final solution – I think I’ll have a whiskey tonight to celebrate too!

    Cheers, Nick.

    ps. If you could make this question as answered (if it is), that would be appreciated.

    in reply to: Problems with flatfile parsing #20943

    Hi,

    I am a newbie learning Biztalk. 

    My application goes as follows:

    I have an input csv file with 4 rows. I put it in a input folder.  I need to split the message into 4 individual csv files (each row in a separate file) and the result should come in output folder.. I use receive and sent pipelines only. I also promoted all the fields using Property fields. i tried everything suggested above (except that i dont have an orchestration for my project as it is not needed in this case). 

    The input message is being picked but I dont get output. The error is “The Messaging Engine encountered an error during the processing of one or more inbound messages. “

    Can anyone help please?

    in reply to: XML debatching (long) #20942

    NO!!! I spoke too soon!

    I have the 3 files now, but they are void of any data.  Looks like i’m switching from beer to whiskey.

    Edit: I’m hypothesizing that the reason there is no data is because i’m using the customerSchema as the envelope.  When it hits that Body XPath, it’s stripping all the data off.  So now I think I understand your original post about making your own envelope.  I’ll do some experimenting here.

    Edit:  I think that hypothesis is wrong.  Because the envelope schema and the customerSchema have the same root node name, i was forced to change the target namespace.  I’m now thinking that the loss of data comes from the messages having a different target namespace.

    Edit:  FINALLY KILLED IT! problem was in the orchestration.  Now only using 3 schemas:  customerSchema(which is now the envelope), documentSchema (customerSchema without the root node), and ourSchema.  All in the same namespace.  Final product is exactly what i needed.  <entry> node separated into it’s own file and able to be processed by the map.  I had to change the map in the orchestration to use the incoming schema: documentSchema rather than what it used to be: customerSchema.  Not sure if any of that makes sense.  It’s getting late here and i’m getting a little delirious.  But thought i would write it out in case anyone could find it useful.  Thanks again for the guidance!

    in reply to: XML debatching (long) #20941

    GOT IT!!!

    Thank you very much Nick, I really appreciate your help.  It feels damn good when it works!

    My problem after getting the messages to debatch was my receive port.  It was expecting the customerSchema type, not the debatched message type (customerDocument).  So I changed my receive port to expect the customerDocument type and then I used a construct message shape to map the customerDocument message type to the customerSchema (basically the same except a different root node).

    Well, again, i really appreciate the guidance.  I think it’s time for a beer now!

    in reply to: XML debatching (long) #20940

    Nick,

    Thank you very much for posting such a detailed suggestion.  I think we’re almost there.

    So what i did is take the customerSchema file and mark it as an envelope and mark the root node as the body xpath.  Then i created a new schema that holds the body.  Build works great, but i see the message is suspended with the following error:

    The Messaging engine failed to process a message submitted by
    adapter:FILE Source URL:C:\Mapping\In\*.xml. Details:The published
    message could not be routed because no subscribers were found. This error occurs
    if the subscribing orchestration or send port has not been enlisted, or if some
    of the message properties necessary for subscription evaluation have not been
    promoted. Please use the Biztalk Administration console to troubleshoot this
    failure. 

    So I right clicked on the suspended message and clicked on message flow.  I found 4 parts to the message:

    Unparsed Interchange

    entry

    entry

    entry

    It so happens that my test document had just 3 peices so it looks like it is splitting the message! 

    I looked over your post a few more times to see if i was missing anything.  I see that you have suggested to create 2 entirely new schemas.  At that point i would have 4 total schemas (customer, customerEnvelope, customerDocument, and ourSchema) and the envelope schema and the customer schema would have the same root name (an error i ran into when trying that way).  I can get away from the error by changing the namespace on the envelope and document schema, but then the message just totally skips the debatching.

    Thanks again.  I can’t help but think we’re very close to having a working solution.

    Bart

    It definately is a Distributed Transaction Coordinator (MSDTC) error – I blogged about this several months ago at http://www.modhul.com/2008/01/22/further-biztalk-msdtc-issues/

    If you’re still not having any luck, please post any error messages you receive on the SQL Server / BizTalk Side.

    Rgds, Nick.

    in reply to: XML debatching (long) #20938

    Hello Anon,

    I think you’re almost there with option A – which I would recommend as the best approach: its much better to do your debatching in the pipeline than start an orchestration to do the debatching with the additional overhead that incurs!

    You need to create two schemas, an envelope and a document/body schema; the envelope schema will define the message you will receive from your customer and the document schema the single <entry> schema.

    1. Create a new (ordinary) schema as your envelope schema as follows:

    Envelope Schema

    2. Click on the Schema node (at the top of your schema tree) and set the schema property Envelope to Yes

    3. Click on your Root node and click the elipsis button on the Body XPath property (note, this will be greyed out until you sent the Envelope property to Yes), navigate to your root node, not the entry node, and click Ok. This will update the Body XPath property.

    4. Create a separate schema that represents your single entry message so that once the message is debatched, the XmlDisassembler will recognise the individual messages.

    Deploy and test – there is no need to configure an XmlDisassembler,just use the standard XmlReceive pipeline and BizTalk will work its magic and figure out the necessary schemas. Be aware that the validate schema test in Visual Studio won’t work with the envelope schema,but it will work with the document message.

    It can be a bit fiddly getting these things to work – I’ve just spent today doing just that and it took me a few attempts – but when it works, it is beautiful. If you get any errors, post them here and we will help get this sorted. it would also be helpful if you could post an example of the actual message you are receiving.

    Cheers, Nick.

    in reply to: Document type does not match any of the given schemas #20937

    You haven’t described where you are mapping from your pathology_in message to the schema.clinic message – it sounds like the mapping isn’t working somewhere and the message that is passed to your send port is still the pathology_in message.

    I’m also thinking that your problem may be coming from the receive side rather than the send side, let me explain: if the error was on the send side, BizTalk will have already found a schema to associate with the message, so if its found a message in the MgmtDb on the way in (the receive port), it shouldn’t then have problems on the send side! I’m therefore thinking that your error is actually on the receive side….

    Either way, if you could advise on how you projects are structured and how they are
    deployed in BizTalk Applications; it would also be good to get a copy
    of the full error you are receiving from the Event Log.

    Cheers, Nick.

     

    in reply to: XML debatching (long) #20936

    Hello Sidhu,

    Thanks for the quick reply.

    I tried changing all the schemas (4 in all)* to have nothing in target namespace.  When i try to change the namespace on the on the envelopeSchema, it has an error that says:  “Namespace attribute of an import must not match the real value of the enclosing targetNamespace of the <schema>.”

    The four schemas, in case that would help:

    customerSchema

    ourSchema (we must eventually map to this)

    documentSchema (this schema i created from the customer schema without the root node)

    envelopeSchema (has essentially the header of the customerSchema)

    Thank you,

    in reply to: XML debatching (long) #20935

    When you create a schema in Visual studio, it will automatically assign a namespace but if your incoming xml doesn’t have a namespace associated with <entry> node, you have to update the namespace of <entry> node to empty.

    in reply to: WCF Adapter and SSO #20934

    Thanks for your reply Russel. That method will definitely speed up promotion.

    That said for a couple of reasons, not limited to my own curiosity, I would still like to know how to use SSO properly. First in the (very likely) event that I have to link to several Oracle databases in a single application the method you mentioned above would be fairly inconvenient as I would have to replace each password one by one. Also I may be a bit paranoid but is it a good idea to have production passwords easily visible in plain text?

     

    Any suggestions?

     

    Thanks

     

    Stuart

     Additionally, Biztalk and SQL Server are on seperate machines.

    in reply to: WCF Adapter and SSO #20931

    Are you flowing the original user credentials through BizTalk and into Oracle?  That is the problem that SSO is designed to solve.  You just mentioned that you have to re-enter the password every time you promote the application, and there is a simpler solution than SSO for that problem.  To keep from re-entering the password every time you promote the app, just open the binding file in a text editor and do a find and replace of “Password=**********” with “Password=<real password>”.

    in reply to: Communication with web service java #20925

     Hi ruselw!

    Of course chunked is correct but perhaps not needed, for this reason I’m triying that the WS supplier check if they can change the chunked option.

    During last evening I reach the same conclusion than you using a custom pipeline, but now I go to check the option using the WCF-BasicHttp adapter. I will keep you informed.

    Thanks a lot

    There is some other service (orchestration or 2 way send port) in your BizTalk environment that has the same subscription as the orchestration you published.  Are there any other orchestrations that are sharing the receive port that was generated when you published the orchestration?  Are there any services using the same message type?  You could debug this by running a query for all subscriptions in the group hub page.

Viewing 15 posts - 3,661 through 3,675 (of 9,648 total)