.NET and SAP integration : The Path ahead

Microsoft recently announced a partnership with SAP that gave a way for tighter integration for application development and cloud deployments. This particular announcement has quite a few implications. SAP and Microsoft’s plans to hit on two key areas: one is to help .NET Framework developers more easily build applications that can easily connect to SAP, apart from that it aims to help customers harness the power of the cloud.

This will be a nice partnership for .NET developers as they will be able to consume and extend the software more easily with SAP Process Extension. The overall application development process will be simplified thus giving developers more time and space to try out new and innovative things. The level of access that will be provided to SAP and Microsoft Developers is bound to shorten the development cycles which in turn will result in lowering the cost of application development. Core Applications will be easily accessible to coders and programmers working on .NET or SAP.


The partnership has been touted to define and build the architecture over two phases:

• Developer Experience – The focus for the first phase will lie on providing all .NET developer a unified experience through the .NET and SAP platforms.

• Lifecycle Management – After that, the repositories will be logically unified, in an attempt so that artifacts belonging to one solution can be managed as one throughout the Microsoft and SAP platforms.

This architecture will surely bring value to customers in many ways:

• After implementing this more core processes will be extended with people-centric sub-processes or front-ends, i.e. the SAP data and functionality can be used in several new contexts.

• Development of extensions will become really easy and cheap, as a single developer wil be building the whole extension.

• Total cost of ownership (TCO) of extensions becomes much lower, as the whole extension, both the SAP and Microsoft parts, are managed as one over the entire life cycle.

Knowing what your project requires and what are the features required for making it more attractive and useful for the user, must be considered while opting for any of the two but with this integration things will change drastically and the better of any one can be used in the other and vice versa.


Author writes regularly about Code Protection and .net Obfuscator s. To know more about .net Code Security, .net Code Protection and .net Obfuscators
feel free to contact the author at http://secureteam.terapad.com/





Article Source : http://netobfuscator.wordpress.com/2011/07/01/net-and-sap-integration-the-path-ahead/