Using the online WSDL and Schema Documentation

From HTNG Connectivity Wiki

Jump to: navigation, search

Accessing the online Documentation

HTNG provides a set of documentation that can be referenced via the various workgroup namespaces. A quick reminder of the naming convention used for namespaces and/or workgroups can be presented in the following table:-

Workgroup Acronym
Architecture ARC
Distribution Content Management DCM
In-Room Technology IRT
Payments PMT
Property Distribution PDS
Property Web Services PWS

Based on this convention, the following documentation is available for access:-

Workgroup Team Namespace URL Notes
PWS - Single Guest Intinerary (SGI) http://htng.org/PWS/2008A/SingleGuestItinerary/Default.html Will be updated in the 2008B specification
PWS - Digital Signage (DS) http://htng.org/PWSWG/2007/01/DigitalSignage Uses an old naming convention, is schedule for update in 2009
PWS - Open Data Exchange (ODX) http://htng.org/PWS/2008A/ODX/Default.html Will be updated in the 2008B specification

Accessing the namespace for the Single Guest Itinerary workgroup will take you to a page like this one

File:ActivityServiceWebPage.jpg

Right click on the WSDL - Service Description and each of the XSD's to save each of these important documents to your hard drive. Remember to use the "Save Target As..." functionality:

File:ActivityServiceSaveAs.jpg

Once these have been downloaded they need to be placed in a simple directory structure. We recommend that you seperate the Schemas (XSDs) from the WSDL. Here is an example of that approach:

File:ActivityServiceDirectoryStructure.jpg

In order to develop some software to utilize these as web services you need to generate the Environment Utilizing WSE 3.0. Through the WSE 3.0 utilities we can generate the various files to wire up the Web Service. The first step in this process is the construction of the "Interface" file that will be the reference to the various services being offered through the WSDL. Locate the WseWsdl3.exe program. You'll normally find it in C:\Program Files\Microsoft WSE\v3.0\Tools (Note: If you have Vista64 installed it will normally be in C:\Program Files (x86)\Microsoft WSE\v3.0\Tools. This file is directed at the WSDL to generate the appropriate code behind file.

The command sequence is typically something like: wsdl.exe /serverInterface /n:HTNG.SGI /o:ServiceInterfaces.cs Activity.wsdl Activity.xsd Common.xsd Name.xsd PmtPosting.xsd Reservation.xsd

Most organisations utilise a simple batch file to create the appropriate files to access the web service (as a client or a server).

File:ActivityServiceBatchFile.jpg

This batch file is used to generate the web service server and proxy classes that will be used to communicate between systems. You can access a text version of this file via http://www.htng.org/mwiki/images/3/30/ActivityService.txt remember to save it as a .bat file so you can run it on your machine.

Once the wsdl and wsewsdl3 utilities have been run against the WSDL and Schema's you can then use Visual Studio to construct the appropriate web service. In the following chapters we will build the Single Guest Itinerary Server and then extend it to include a client application that can post charges to it.

After running the ActivityService.bat file you should have two files now sitting in you main directory ServiceInterfaces.cs and Proxy.cs

The next section Creating a Web Service Server using the SGI specification provides details on how to use these files. college essays

Personal tools
administrative tools