community-content

Forum Replies Created

Viewing 15 posts - 6,046 through 6,060 (of 9,652 total)
  • Author
    Posts
  • in reply to: Problems with flatfile parsing #17294

    The only thing I can suggest now is to verify that all suspended messages are cleared out before trying each time and list here any BizTalk event messages that get generated.  Otherwise, it sounds like it should work.  Maybe you can list out your configuration, if its simple enough, to see if anyone has seen a problem before or some simple "gatchas".

    in reply to: Need help in BizTalk #17293

    The quick way to log your message is to send it out a static one-way port to a Folder configured in a send port.  I use an "archive" folder, and while building and debugging at particular points in the Orchestration, I write out messages to that folder so as not to confuse them with the normal process.  You just need a send shape and a one-way static port, and configure the message and message type.

    Does this help?

    in reply to: Problems with flatfile parsing #17292
    • yes the custom Pipeline holds the flatfile disassembler which is configured with the proper schema
    • i did it like i learnd it from the microsoft tutorials so yes again
    • the custom Pipeline is selected in the Receive Port configuration
    • i also did that

    for the folder permission: i configured a ver unsecure version for testing where all services etc run under local admin…

    in reply to: Problems with flatfile parsing #17291
    • Have you configured the Flatfile Disassembler in the custom Pipeline with the correct schema?
    • Have you deployed the entire application from the Solution, and not from each Project?
    • Have you Selected the proper Pipeline from the drop down in your Receive Port configuration?
    • Have you restarted the Host Instance for the Application to be sure your changes have taken effect?

    I'd ask about Folder permissions, but apparently that's fine or you wouldn't get an XML file to work.

    in reply to: Integrating with Windows Application #17290

    Probably the easiest method to configure is file drop.  You can use System.IO and the built in file and folder controls to reach them.  Now you either create XML or some flat file type to package your data and drop it to your Receive Location folder.  You can read the response from a send port folder.

    That said, I agree with John D. on the way to get started.  There are also now a few good books on the subject, and a plethora of integration options, including Web Services, HTTP, SQL and Oracle DB.

    Please, tell us more about what you are trying to accomplish.  It sounds like you want to find a quick way to understand BizTalk.  The best way is to find a pattern you like or that makes sense and create your own version.  Look for BizTalk 2006 Recipes: A Problem-Solution Approach

     

    in reply to: Problems with flatfile parsing #17289

    Thanks for the quick answer.

     The test with the native file also succeeded…

     

    The error message reads : The Messaging Engine encountered an error during the processing of one or more inbound messages.

    in reply to: Integrating with Windows Application #17288

    Anon-Again,

    firstly, I *really* recommend that you do the BizTalk tutorial in the kit, if you have not done it yet.

    Secondly, I do not understand what you want to do, so you will need to explain much better.

    John D.

    in reply to: Problems with flatfile parsing #17287

    Anon-Again,

    there is a further validation step you can try. Set the properties of the map to take a native file input and then point it at your flat-file. It will do both the conversion and the mapping in one step.

    You don't say what the error message means. What is the text you see in the event log?

    John D.

    in reply to: Need help in BizTalk #17286

    Sasi,

    probably I didn't explain clearly. There are three options: (1) you do the logging, (2) let BizTalk trace the message, (3) output a message.

    For (1) you are right – it will be in XML form when you get your hands on it in the orchestration.

    For (2), what message format is traced, depends on where you switch tracing on. If it's the receive location, it will be before the pipeline and it will be in native format.

    For (3), you can create a port on the orchestration and output the message. In the orchestration you will have an XML message, but in the send port you could convert it back into a flat-file. You would need to create a flat-file-send-pipeline with the same flat-file schema in it that you use to convert the incoming file.

    John D.

    in reply to: Need help in BizTalk #17284

    John,

    Thanks a lot for your response.

    Still I am in confusion in logging the message into the text file.

    Suppose if I receive an XML file from an external to BizTalk, by using the HAT tool we can check whether that message has been logged in or not. if I am converting that XML file to a Flat File then before sending that flat file to external I want to log the message by creating a text file in some folder. Is it possible to create a text file and write the message by using Orchestration?

    Please clarify.

    in reply to: Construct Message #17282

    AnonAreYouReallyAnon,

    did you try Googling for "BizTalk conditional mapping functoid"? Here's a good like for you:

    http://www.topxml.com/BizTalk-Functoids/re-21366_Mapping–Conditional-Output.aspx

    The second part treats exactly your question.

    John D.

    Jitendra,

    to help you understand subscriptions, and to help your problem in particular, it is a good idea to try setting up a parallel subscription for the same message. Just define a new send port and give it an appropriate filter. For example the one suggested by BizTron. Then change the filter to the one your orchestration is using.

    John D.

    in reply to: Need help in BizTalk #17280

    Sasidhar,

    if you are using BTS 2006, once you turn on message tracing, you can drill down to the message with the admin tool. Nice.

    If 2004, then it's much less transparent, but if you turn on tracing you can eventually get to the message body using the HAT tool. If I remember correctly, you get the option in HAT to save the message, and it saves two files, one of which is the body.

    John D.

    in reply to: Biztalk adapter in axapta #17279

    Thanks a lot,

          if possible can u send an document to me to my mail id on this scenario so that we can work on this adapter….. this is my

     mail id:[email protected] 

    thank u once again,

     

    in reply to: Need help in BizTalk #17278

    John,

    Thanks for your response. For my 2nd query mentioned above, if I want to see the input message which is coming from external to BizTalk, can I check the same in HAT? Does HAT tool displays the total message?

    I suppose it is very difficult to trace the error when it is written into Event viewer for a particular mesasge. So, is there any possibility to create a log file which is a text file and write the message into that?

    Please clarify.

    Sasidhar 

     

     

Viewing 15 posts - 6,046 through 6,060 (of 9,652 total)