1 / 53

WCf OverView

WCf OverView. Wcf is part of SOA Service side story Clientside neednot have to WCF. Client side Story. Client side Story. Could be Client or Server side Could be Integrated with WCF. WCF and SOA.

mareo
Download Presentation

WCf OverView

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. WCf OverView

  2. Wcf is part of SOA Service side story Clientside neednot have to WCF Client side Story Client side Story Could be Client or Server side Could be Integrated with WCF

  3. WCF and SOA

  4. Suppose you have a CRM System, Accounting System and Reporting System in place, you will think of creating a API layer for this Functionality. • WCF is all about exposing the functionality over API layer (Service) defined by a contract. • WCF is Buildup from Ground up level to be a first class SOA citizen.

  5. Lets discuss that in SOA we have Little SOA and Big SOA

  6. Suppose we have a Agency Management System of a Insurance Company which is Busy in day to day activities, like providing certificates, issuing policies, keep track of customer for a particular customer on a particular Policy. • There fore “Agency Management System ” that is small exe but in the backend it has big activities/functionality like Reporting System with a separate database, CRM System with a Separate Table etc.

  7. Lets create a API layer for this Functionality, that’s is exposing the functionality over API layer defined by a contract. By hiding the crucial details. Business Tier Components Cordinates the Functionality at Data Tier Level All the details of access to table and all

  8. Therefore we should have a Service that Isolates this Business Tier and Data Tier that Is a single application system from another. And expose this a s unit over a Service Layer (which defines security, contract, policy of Communication) to Agency management System is Little SOA and to other applications of Business Partners etc. Over the net is Bigger SOA.

  9. Scenarios/ Applications Where I can USE WCF

  10. Here we have Message level Security

  11. WCF- Interoperability and Integration

  12. We are getting into the scenario where I have to look and think less At/on xml form in message more concentrate on features required

  13. Client and Service

  14. Explicit contract are Defined over the Service Contract Client will choose one of the end point based on the Protocol to use Component Host is Living for the Message to be received And the End Points are the entry Points

  15. Practicals

  16. ClassLibrary

  17. Host

  18. Client Manually copy the meta data

  19. There is away to generate the Proxy (Meta Data Information) without hand Coding it, that’s via WSDL

  20. Should be service description Language. For Http Protocol

  21. When we say host.open(), it create/opens the channels for communication and the creates the Service Description , so at runtime information of the Protocols, what all End points are available . So it generates the WSDl document. And client use the same to create the Proxy. The service Model Generates the Service Description file

  22. You can mail this WSDL to Client and Ask client to use svcutil.exe tool, to generate the Proxy

  23. Next

  24. Keep this on therefore will have two endpoints

More Related