none
Old SAP Adapter with BizTalk 2010 RRS feed

  • Question

  • We are upgrading our system from BTS 2006 R2 to BTS 2010.

    Old applications have dozens SAP ports.

    It look like the unreasonable task to move everything to new WCF-SAP adapter, because it would require the schema regeneration, map modification, port recreation, etc.

    But if regenerated schemas are similar to the old schemas, this task would be straightforward and fast. I don't know.

    What is your experience? 
    Thank!


    Leonid Ganeline [BizTalk MVP] BizTalkien: Advanced Questions

    Thursday, October 11, 2012 10:27 PM

Answers

  • Hi Leonid,

    I am involving someone familiar with this topic to help you. Thanks for your understanding.

    Thanks,


    Alan Yao [MSFT]
    MSDN Community Support | Feedback to us
    Get or Request Code Sample from Microsoft
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

    Monday, October 15, 2012 2:48 AM
    Moderator
  • Hi Leonid,

    1. BizTalk 2010 does not have the legacy SAP adapter any more. See http://www.microsoft.com/biztalk/en/us/whats-new.aspx.
    “mySAP Adapter (legacy) – The SAP Adapter included in the BizTalk Adapter Pack replaces the legacy SAP adapter.”

    2. The schema generation of the SAP Adapter included in the BizTalk Adapter Pack is as easy as that of the legacy adapter.

    Thanks,

    Cathy Miller

    Tuesday, October 16, 2012 5:44 PM
  • Have you tried

    BizTalk Adapter Pack Migration Tool 2.0

    http://www.microsoft.com/en-us/download/details.aspx?id=7840

    Does that meet your requirement?

    Wednesday, October 17, 2012 7:47 AM
  • This is most likely related to SAP dll versions not being present in the proper folder.

    Please have a look at the following discussion and make sure you have appropriate SAP dlls (32 bit / 64 bit) in proper folders.

    <Sorry - it is now allowing me to put the link here>

    Please go to Social dot msdn dot Microsoft dot com

    Select Forums

    Search Forum - Search Thread for 0cc63835-0b6c-49e8-9d66-a6904bd934ea

    Check for Ben Cline1's blog post

    Friday, October 19, 2012 6:50 AM

All replies

  • Hi Leonid,

    I am involving someone familiar with this topic to help you. Thanks for your understanding.

    Thanks,


    Alan Yao [MSFT]
    MSDN Community Support | Feedback to us
    Get or Request Code Sample from Microsoft
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

    Monday, October 15, 2012 2:48 AM
    Moderator
  • Hi Leonid,

    1. BizTalk 2010 does not have the legacy SAP adapter any more. See http://www.microsoft.com/biztalk/en/us/whats-new.aspx.
    “mySAP Adapter (legacy) – The SAP Adapter included in the BizTalk Adapter Pack replaces the legacy SAP adapter.”

    2. The schema generation of the SAP Adapter included in the BizTalk Adapter Pack is as easy as that of the legacy adapter.

    Thanks,

    Cathy Miller

    Tuesday, October 16, 2012 5:44 PM
  • Hi Cathy,

    Thank you for answer!

    I also tried use the old adapter without success.

    The new adapter creates schema that looks like the old schemas.  Unfortunately they are not 100% as old, so I have to manually recreate the related maps. I'm trying to do some automatic map conversion.


    Leonid Ganeline [BizTalk MVP] BizTalkien: Advanced Questions

    Tuesday, October 16, 2012 5:52 PM
  • Hi Leo,

    Two year back i had also came up with similar scenario when i was migrating my solution from BizTalk 2004 to BizTalk 2009 (http://social.msdn.microsoft.com/Forums/is/biztalkgeneral/thread/f0846b7c-eb9c-40b1-bc51-2c081c1c3f10)

    I followed below suggestion and i made BizTalk 2004 SAP schema with BizTalk 2009 WCF. You can try this but as per my experince SAP will not do validation of message.

    Let me know if this solution is still valid.

    Regards

    ------------------------------

     Hi Anand,

      SAP adapter documentation can be found under ProgramFiles\MicrosoftAdapterPack\Documentation which will provide more details how to migrate from prev versions. Anyway all you need to do is configure a WCF send port SAP binding selected configure the endpoint address with your SAP information. Under SOAP action header set the following : http://Microsoft.LobServices.Sap/2007/03/Idoc/SendIdoc

    So the latest adapter provide two operations Send and SendIdoc. We are going to use SendIdoc operation to support the prev version messages.  Then under "Messages" tab select the template and paste the following:

    <SendIdoc xmlns="http://Microsoft.LobServices.Sap/2007/03/Idoc/">
    <idocData><bts-msg-body xmlns="http://www.microsoft.com/schemas/bts2007" encoding="string"/></idocData>
    </SendIdoc>

     It should work now, let me know.

    -SHR

    ------------------------------

    Wednesday, October 17, 2012 3:39 AM
  • Hi Anand,

    Using the old SAP schemas is out of the question. We have to regenerate the schemas for the WCF-SAP adapter. The new schemas are very similar but there aren't now the automatic update of the old schemas to the new schemas. Right now I'm manually recreating the maps which involve the SAP schemas. It is not the fastest way. :(


    Leonid Ganeline [BizTalk MVP] BizTalkien: Advanced Questions

    Wednesday, October 17, 2012 3:59 AM
  • Have you tried

    BizTalk Adapter Pack Migration Tool 2.0

    http://www.microsoft.com/en-us/download/details.aspx?id=7840

    Does that meet your requirement?

    Wednesday, October 17, 2012 7:47 AM
  • Have you tried

    BizTalk Adapter Pack Migration Tool 2.0

    http://www.microsoft.com/en-us/download/details.aspx?id=7840

    Does that meet your requirement?

    sagre1, thanks a lot! I will try it immediately. 

    Leonid Ganeline [BizTalk MVP] BizTalkien: Advanced Questions

    Wednesday, October 17, 2012 3:05 PM
  • Have you tried

    BizTalk Adapter Pack Migration Tool 2.0

    http://www.microsoft.com/en-us/download/details.aspx?id=7840

    Does that meet your requirement?

    I've tried with it unsuccessfully. Got an error:

    I have no idea how to resolve it.


    Leonid Ganeline [BizTalk MVP] BizTalkien: Advanced Questions

    Wednesday, October 17, 2012 4:15 PM
  • Leonid,

    Are you running this on a 64-bit server?  If so try running it as a 32-bit process as follows:

      • Make a copy of BizTalkAdapterPackMigrationTool.exe.  (The following command sets a flag in the executable to run only 32-bit mode)
      • From a command window run: corflags /32BIT+ BizTalkAdapterPackMigrationTool.exe /Force
      • Run BizTalkAdapterPackMigrationTool.exe and see if it works.

    If that doesn't work, try to force it to 64-bit using: corflags /32BIT- /ILONLY- BizTalkAdapterPackMigrationTool.exe

    HTH


    David Downing... If this answers your question, please Mark as the Answer. If this post is helpful, please vote as helpful.




    Wednesday, October 17, 2012 4:51 PM
  • I just noticed one more thing that may or may not help. This utility requires WCF LOB Adapter SDK SP2.

    David Downing... If this answers your question, please Mark as the Answer. If this post is helpful, please vote as helpful.

    Wednesday, October 17, 2012 8:16 PM
  • This is most likely related to SAP dll versions not being present in the proper folder.

    Please have a look at the following discussion and make sure you have appropriate SAP dlls (32 bit / 64 bit) in proper folders.

    <Sorry - it is now allowing me to put the link here>

    Please go to Social dot msdn dot Microsoft dot com

    Select Forums

    Search Forum - Search Thread for 0cc63835-0b6c-49e8-9d66-a6904bd934ea

    Check for Ben Cline1's blog post

    Friday, October 19, 2012 6:50 AM
  • Yeah, Sagre1, you are right. I've managed to start it on another machine with right installation.

    Leonid Ganeline [BizTalk MVP] BizTalkien: Advanced Questions

    Friday, October 19, 2012 6:59 PM