Skip to Content

image

The previous blog of this series – Implementing Services in Java (Part 6) – showed you how the previously modeled & defined service interface can be implemented using JEE technology. Having been a successful participant in last year’s initiative on Partner-delivered Enterprise Services (PdES), the SAP Global CO-Innovation Lab Network team invited us to show you in this blog how we implemented our first SAP SOA methodology-compliant service using .NET technology.

 

imageOur goal is to help organizations make strategic decisions about how to better manage their global talent and optimize workforce performance.  We empower organizations with a 360-degree view into their human capital data, giving them the critical insight they need into their talent and organizations to support overall corporate objectives.
In 2008, we successfully participated in the PdES 2008 initiative and modeled our first SAP SOA methodology-compliant service. Have a closer look at our scenario PdES: SAP Talent Visualization by Nakisa, Inc..

So continue on your PdES journey and have a look at the screencam:

 

Screen cam

 

 

The detailed storyboard is outlined in the following:

  • Obtain the WSDL for service.
  • Use Microsoft’s Web Services Description Language Utility (wsdl.exe) to generate server code.

Go to command prompt. And issue following command:

 

wsdl /n:[Namespace] /l:CS /protocol:SOAP /serverInterface [pathToWSDL]

 

Make sure wsdl.exe is in your path. It is normally located in “C:Program FilesMicrosoft Visual Studio 8SDKv2.0Bin”. If you don’t want to modify the path environment variable then used full path to wsdl.exe.

 

For further details about wsdl.exe go to http://msdn.microsoft.com/en-us/library/7h3ystb6(VS.71).aspx

  • Create a new C# Web Project. Create a new blank web service with appropriate name.
  • Import code generated by wsdl.exe.
  • Modify the web service to implement the interface generated by wsdl.exe.
  • Implement the body of the method inherited from generated interface.

 

Ride in the tube of SOA and learn how to deliver your services based on SAP’s modeling and definition methodology. Stay tuned for more information and move on in your PdES journey with the next blog on “Implementing Services in ABAP”.

In the following the links to all other blogs from the PdES Architecture Series:

1.      SAP Co-Innovation Lab Architecture Series: Partner-delivered Enterprise Service – Introduction (Part 1)Screencam
2.      SAP Co-Innovation Lab Architecture Series: Partner-delivered Enterprise Service – Outlining the ‘way to deliver’ services (Part 2)
3.      SAP Co-Innovation Lab Architecture Series: Partner-delivered Enterprise Service – Modeling Services (Part 3)Screencam
4.      SAP Co-Innovation Lab Architecture Series: Partner-delivered Enterprise Services – Defining services (Part 4)  – Screencam
5.      SAP Co-Innovation Lab Architecture Series: Partner-delivered Enterprise Services – Leveraging a wizard to automate Service Creation (Part 5)Screencam + Wizard
6.      SAP Co-Innovation Lab Architecture Series: Partner-delivered Enterprise Services – Implementing Services in Java (Part 6)Screencam
7.      SAP Co-Innovation Lab Architecture Series: Partner-delivered Enterprise Services – Implementing Services in .NET (Part 7 – provided by Nakisa)Screencam (This Blog)
8.      SAP Co-Innovation Lab Architecture Series: Partner-delivered Enterprise Services – Implementing services in ABAP (Part 8)Screencam
9.      SAP Co-Innovation Lab Architecture Series: Custom Development delivered Custom Enterprise Services (Part 9)Screencam
10.    The specified item was not found.Certification

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply