Custom Pipeline Component: xsl transform

Home Page › Forums › BizTalk 2004 – BizTalk 2010 › Custom Pipeline Component: xsl transform

Viewing 2 reply threads
  • Author
    Posts
    • February 10, 2009 at 8:20 AM #21678
      community-content

        Hello,

        I’m working on a new project that will utilize biztalk’s message transformation features.  I’m looking for the best way to implement a design that the only objective is to tranform a message and send the new message directly back.  I’m hoping to achieve this in a request-response port for security purposes.

        My external schema would be very simple – essentially a uniqueID and a string.  I would write a custom pipeline component to convert the string into an xml doc via xmlstream and apply an xsl based on what the uniqueID is for the document.  Then convert the new xml to string and respond back in the same original schema format.

        Would this be an appropriate method for my objective?  Would you implement this if performance and reliability were the most important?

        <Root>

         

        <uniqueID></uniqueID>

        <xmlMessage></xmlMessage>

        </Root>

         

        I appreciate any advice you can give.

        -Novice Biztalker

      • February 11, 2009 at 9:27 AM #21701
        community-content

          Anyone have a suggestion?

          • February 13, 2009 at 8:33 AM #21731
            community-content

              Is there some other lift you will get from using BizTalk?  Are you looking to have this as part of a larger BizTalk based solution?  if so, I think you can look at the dynamic transform examples that Stephen Thomas has put together. 

              If you are just planning on calling this from an app that is stand alone, I would go down the XSLT inside of your application route. 

          • February 16, 2009 at 1:03 AM #21740
            community-content

              Hi,

               I need some more information about receive loaction how you get the message (xml file) and where you received the file is it at (folder/ ftp folder / in url) ? and where to send….

              if it is (folder / ftp folder)…it is very simple …create two XSD, one for input message one for Out put message the use mapping to align to XSD(u can use external XSLT which you have)..

              if it is (in url)..no need use Biztalk server …user XML serilization using xml parser to fullfill you requirement.

              suman kalyan betal

               

               

              • February 16, 2009 at 8:30 AM #21744
                community-content

                  Thank you for the replies.  I’ll be receiving the message via a biztalk webservice generated by the Biztalk Web Publishing wizard.  Or that’s at least what I had planned.  I was planning to publish an external schema which is essentially 2 nodes.  One for messageType and the other for the actual message parsed as a string.

                  Another thing to note is that we will end up having flat files sent to us.  Which means that we would need to publish the schema so the translation can occur.  Which also means that every time there is a new exchange, we would need to redeploy our biztalk solution.

                  Thanks for the suggestion Suman.  I think I’ll look deeper into that.

            • Author
              Posts
            Viewing 2 reply threads
            • The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.