Top Banner
Chapter 12 Interoperability and Integration CA 907 WCF 1 WS-* Interoperability Integration with legacy systems. Contents are from: - Textbook - Pro WCF Practical Microsoft SOA Implementation by Dennis Mulder
24
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: Unit 5

Chapter 12 Interoperability and Integration

CA 907 WCF

1

WS-* Interoperability Integration with legacy systems. Contents are from:

- Textbook- Pro WCF Practical Microsoft SOA Implementation by Dennis Mulder

Page 2: Unit 5

Interoperability

Ability to communicate with other platforms thru standard protocol like SOAP.

SOAP is platform independent. To achieve interoperability WCF team

generatedmany compatibility tests for a subset of different vender specifications.

Microsoft created WCF interoperability Plug-Fest #

Sun is one of the participants.# www.mssoapinterop.org/ilab

CA 907 WCF

2

Page 3: Unit 5

Interoperability

Sun web services team worked with Microsoft WCF team.

They released open source framework – Project Tango1 which focuses on interoperability with WCE.

It has evolved into Web Services Interoperability Technology(WSIT)2

Another major participant in the WCF/.NET interoperability is Axis Project from Apache Software Foundation 3

CA 907 WCF

3

Page 4: Unit 5

Interoperability

1. http://weblogs.java.net/blogharoldcarr/archive/2006/02/an_overview_of_1.html

2. http://java.sun.com/webservices/interop/index.jsp

3. http://ws.apache.org/axis2

One of the earliest efforts is to implement WS-I Basic Profile.

CA 907 WCF

4

Page 5: Unit 5

Interoperability

WS-I Basic Profile Some venders had chosen different versions

of WSDL or SOAP. So getting interoperability among diff. system

is very difficult. The early SOA vendors did not confirm to

open standards, so true interoperability between different vendors is very difficult.

CA 907 WCF

5

Page 6: Unit 5

Interoperability

WS-I Basic Profile Major participants form Web Services

Interoperability (WS-I) organization to develop web services standard in non- proprietary and open manner.

Currently appox. 90 organizations are participating.

CA 907 WCF

6

Page 7: Unit 5

Interoperability

WS-I Basic Profile Core components

- In April 2004 WS-I released version 1.0.- This set of specifications laid the groundwork for vendors and customers to form strong base.

- Many companies and open sources groups recognized that market will no longer allow stand alone proprietary interoperability stack.

CA 907 WCF

7

Page 8: Unit 5

Interoperability

WS-I Basic Profile Core components

- S0AP 1.1 - WSDL 1.1 - UDDI 2.0- XML 1.0 - XML Schema Part1: Structures- XML Schema Part 2: Datatypes- SSL Version 3.0etc….

CA 907 WCF

8

Page 9: Unit 5

Interoperability

WS-I Basic Profile ASP.NET Support for basic profile

- Initially it did not support basic profile 1.0.- With ASP.NET 2.0 support for basic profile 1.1 was available

*http://www.servicetechspecs.com/ws*

CA 907 WCF

9

Page 10: Unit 5

Interoperability

Web Service protocol support by WCF BasicHttpBinding

- Supports WS-Basic Profile 1.1- Allows to create endpoint which can communicate with *.asmx based web services.

WSHttpBinding- Basic + secure+reliable sessions.

CA 907 WCF

10

Page 11: Unit 5

Interoperability

Web Service protocol support by WCF WSDualHttpBinding

- Copy of WSHttpBinding but it supports duplex

WCF Services are compatible with Web Service Enhancement(WSE 3.0)

CA 907 WCF

11

Page 12: Unit 5

Integration

Process of linking together different computing systems and software applications physically or functionally, to act as a unit.

WCF supports COM+ Integration, MSMQ

Difference between Interoperability and Integration

CA 907 WCF

12

Page 13: Unit 5

Chapter 13 Deploying WCF

Installing WCF Services Upgrading existing services Troubleshooting WCF service installations.

CA 907 WCF

13

Page 14: Unit 5

Installing WCF Services Operating System support

- Windows XP SP2- Windows Server 2003 with SP1- Windows Vista (WCF is installed)- Window 7

Required Software- .NET Framework 3.0, 3.5 and …- IIS(Internet Information Services)- MSMQ(MicroSoft Message Queuing)

CA 907 WCF

14

Page 15: Unit 5

Installing WCF Services .NET Framework

- http://www.microsoft.com/en-in/download/details.aspx?id=22

- Needed on machine in which you want to run WCF Service

*http://en.wikipedia.org/wiki/.NET_Framework*

CA 907 WCF

15

Page 16: Unit 5

Installing WCF Services IIS

- Needed on machine in which you want to Host WCF Service

- To install it open control panel add remove programs Add/Remove Windows Components

CA 907 WCF

16

Page 17: Unit 5

Installing WCF Services

CA 907 WCF

17

Page 18: Unit 5

Installing WCF Services MSMQ

- To install it open control panel add remove programs Add/Remove Windows Components

And view previous screen

CA 907 WCF

18

Page 19: Unit 5

Installing WCF Services Hosting on IIS

- Create virtual directory in c:\inetpub\wwwroot directory- Copy of publish .svc and config files (see demo)

Hosting as Windows Service- Create .exe of your host application.- Install it by using installutil.exe- Start service by net start command- Stop service by net stop command

CA 907 WCF

19

Page 20: Unit 5

Upgrading Services Upgrading in IIS is very easy copy or republish

the assembly, config, svc files and you are done.

In Window Service you need to restart service manually after doing changes in your code. So that the changes are available.

CA 907 WCF

20

Page 21: Unit 5

Trouble Shooting WCF installations Client/Server Communications

- It client cannot communicate with service then problem might not be with client only.- Start looking at service first, by using svcutil.exe- On IIS try the address of service in browser.- If both options are ok then problem is on client side.- Review client config file.

CA 907 WCF

21

Page 22: Unit 5

Trouble Shooting WCF installations Unexpected Service behavior

- Reason is unhandled exception.- It can be monitoring by setting IncludeExceptionDetailInFaults=true either in code or config.- After testing you can turn it off.- You can also see Trace viewer, Message logging

More on trouble shootinghttp://msdn.microsoft.com/en-us/aa702636.aspx

CA 907 WCF

22

Page 23: Unit 5

References

Cross Platformhttp://en.wikipedia.org/wiki/Cross_platform

WS-* Specshttp://www.servicetechspecs.com/ws WS-* Specs =

WS-Addressing, WS- Discovery, WS-Federation, WS-Policy, WS-Security, and WS-Trust

http://en.wikipedia.org/wiki/List_of_web_service_specifications CA 907 WCF

23

Page 24: Unit 5

References Miscellaneoushttp://msdn.microsoft.com/en-

us/library/aa480021.aspxhttp://www.oracle.com/us/products/middleware/soa/

overview/index.htmlhttp://www.whatissoa.com/http://www.dotnetobject.com/Thread-WCF-

Interview-Questions-and-Answerhttp://www.questpond.com/dotnet/WCF-Interview-Questions-and-Answers.html

CA 907 WCF

24