Web Services Workshop - Sybase

More documents

Recommendations

Info

Describing the Web Service Why does a Web service need to be described • Web services could be used by anyone, anywhere, using any language on any platform • A description allows a developer to know how to interact with a Web service • PowerBuilder provides tools to read and integrate WSDL Web services are described using Web Services Description Language (WSDL) WSDL is written in XML Usually a developer of a Web Service does not have to manually write WSDL • PowerBuilder 11 will create the ASMX, DISCO and WSDL Sybase Symposium 2007 – November 15 - Brussels 8
PowerBuilder/.NET Web Services PowerBuilder gives you the choice of outputting PowerScript code as an • Assembly • Web Service The only difference PowerBuilder Web Service creation now versus back in Version 9.0 of PowerBuilder is EAServer is no longer a requirement • These Web Services are deployed to your Microsoft IIS Web Server Sybase Symposium 2007 – November 15 - Brussels 9
Page 1 and 2: Web Services Workshop Dave Fish Sen
Page 3 and 4: Proprietary Interfaces & Manual Int
Page 5 and 6: Business With Web Services Salespeo
Page 7: Web Services Components The primary
Page 11 and 12: Web Service Virtual Directory The w
Page 13 and 14: NVOs - Business As Usual Sybase Sym
Page 15 and 16: Web Service Deployment Options Can
Page 17 and 18: Deployment Progress Seen via the ou
Page 19 and 20: WSDL Example Sybase Symposium 2007
Page 21 and 22: IIS Directory: What Is Here Sybase
Page 23 and 24: Global.asax File A source file wher
Page 25 and 26: ASMX Files ASP.NET provides support
Page 27 and 28: Testing The Web Service Sybase Symp
Page 29 and 30: Why Did We Do This Interoperability
Page 31 and 32: Consuming .NET Web Services Sybase
Page 33 and 34: SOAP An XML-based communications pr
Page 35 and 36: Web Service Consumption Invoking We
Page 37 and 38: Web Service Proxy Wizard Sybase Sym
Page 39 and 40: Locate WSDL Sybase Symposium 2007 -
Page 41 and 42: Selecting From UDDI Search Results
Page 43 and 44: Select A Service From WSDL Sybase S
Page 45 and 46: Define Proxy Project Name and Locat
Page 47 and 48: Post Web Service Proxy Wizard Upon
Page 49 and 50: The Web Service Proxy System Tree (
Page 51 and 52: Exported Web Service Proxy Note the
Page 53 and 54: Web Services Runtime Engines EasySo
Page 55 and 56: Importing PowerBuilder Extensions P
Page 57 and 58: Important Notes About These Imports
Page 59 and 60:
Result Of PBX Import Following the
Page 61 and 62:
SoapConnection Methods New methods
Page 63 and 64:
SoapConnection: SetClientCertificat
Page 65 and 66:
SoapConnection: UseIntegratedAuthen
Page 67 and 68:
SoapConnection: SetProxyServer( ) S
Page 69 and 70:
Making The Web Service Call Declare
Page 71 and 72:
SOAP Message With Header The exact
Page 73 and 74:
Web Service Has Reference To Header
Page 75 and 76:
Proxy Created Artifacts Since this
Page 77 and 78:
Result With SOAP Headers Call to th
Page 79 and 80:
Web Service DataWindows Sybase Symp
Page 81 and 82:
Web Service DataWindows Are an exte
Page 83 and 84:
Other Web Service DataWindow Notes
Page 85 and 86:
Selecting A WSDL File First, select
Page 87 and 88:
Select Web Service / Web Service Me
Page 89 and 90:
Finished Web Service DataWindow Aft
Page 91 and 92:
New WSConnection Object Some Web se
Page 93 and 94:
Updates On Web Service DataWindows
Page 95 and 96:
Web Service DataWindow Updates Simi
Page 97 and 98:
Web Service Tracing You can also pe
show all

Web Services Workshop - Sybase

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?