Hooking Stuff Together
Search ⌘K

BizTalk

SAP .NET Connector(NCo) in BizTalk Server

By Gyanendra Kumar Gautam 1 min read

SAP .NET Connector 3.0 is the current version of SAP’s development environment for communication between the Microsoft .NET platform and SAP systems. SAP has already announced deprecation of its classic RFC SDK and they will stop supporting it after March 2016.

So BizTalk server product group has added support for the SAP .NET Connector in WCF–SAP adapter. And they have released it with cumulative update 2 for BizTalk 2013 R2.

Currently the BizTalk WCF-SAP adapter will support both the RFC SDK and the SAP .NET Connector (NCo) through the ConnectorType property within the WCF-SAP binding.

Connector type value can be ‘ClassicRfc’ and ‘NCo’ as explained in the whitepaper released on the Codit website.

image.png

In order to use the SAP .NET Connector, you must install both

Architecture wise it is the re-engineering of Microsoft BizTalk Adapter for mySAP Business Suite to replace Classic RFC SDK from new NetWeaver RFC Library.

image.png

Conclusion

So in conclusion Microsoft has provided the cumulative update / hotfix for WCF –SAP adapter which can be used to make the transition to the new SAP Connector for .NET as smooth as possible.

Both the WCF-SAP and WCF-Custom adapters are updated with a new property that allows you to choose between the Classic RFC and the new Connector for .NET libraries. Please refer the whitepaper for further details.

Resource:

http://www.codit.eu/blog/2016/01/04/microsoft-adds-support-for-sap-net-connector-in-biztalk-server-2013-r2/?utm_source=twitter&utm_medium=post&utm_campaign=biztalk2013r2cu2

http://www.integrationusergroup.com/hybrid-integration-with-sap/

2 comments on SAP .NET Connector(NCo) in BizTalk Server

  1. Vishnu

    I have installed it on my box and observed below exception at the transform stage inside orchestration. If we just redeploy the assembly, the error is gone.

    System.TypeLoadException: Method ‘get_UseXSLTransform’ in type ‘xxxxxxxxxxxx’ from assembly ‘xxxxxxxxxx’ does not have an implementation.
    at System.RuntimeTypeHandle.GetTypeByName(String name, Boolean throwOnError, Boolean ignoreCase, Boolean reflectionOnly, StackCrawlMarkHandle stackMark, IntPtr pPrivHostBinder, Boolean loadTypeFromPartialName, ObjectHandleOnStack type)
    at System.RuntimeTypeHandle.GetTypeByName(String name, Boolean throwOnError, Boolean ignoreCase, Boolean reflectionOnly, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean loadTypeFromPartialName)
    at System.RuntimeType.GetType(String typeName, Boolean throwOnError, Boolean ignoreCase, Boolean reflectionOnly, StackCrawlMark& stackMark)
    at System.Type.GetType(String typeName)

    Have the update tested in dev before moving it to Prod.

    Wait for the next CU or reach out to MS for private build.

  2. Shruthi

    Hi Gautam,

    I have just downloaded the latest BizTalk 2013 CU5 package and also the latest SAP connector. I have made the changes in the binding for the connectionType to NCo.

    Now the transactions are getting created in SAP because I get a successful response from SAP, but if I go and check in SAP tables the material document does not exist.

    If I change the connection type to ‘ClassicRfc’ it works perfect, I can see the material document

    Is there anything else to be changed/configured in BizTalk or SAP?

    Thanks,
    Shruthi

Leave a comment

Held for moderation. Your address is never published, and the database keeps only a hash of it.
Subscribe

Search 473 posts