Quick Start Guide for HTNG Published Web Services
From HTNG Connectivity Wiki
Table of Contents
Over the last few years many companies have used HTNG specifications to implement Web Services interfaces to connect key systems. These projects have involved the development of specification(s), development of the software, testing of the software and the migration into production.
This Quick Start Guide is designed to give those vendors wishing to develop to these standards some educational material and examples, in enough detail to get them moving in the right direction. The Quick Start Guide provides a step-by-step approach to building a development environment and constructing a complete web-services implementation using the published HTNG "Single Guest Itinerary" (SGI) specifications.
- Setting up the Development Environment
- Using the online WSDL and Schema Documentation
- Creating a Web Service Server using the SGI specification
- Migrating the Web Service to IIS
- Creating a GUI based client and posting a charge using the SGI specification - Part 1
- Creating a GUI based client and posting a charge using the SGI specification - Part 2
- Adding Application Security to our Web Service and Client
- Synchronous versus Asynchronous behavior and considerations
- Appropriate Fault Behavior
- Exchanging Files using the ODX specification - In development
- Developing your own Web Service specification - In development
Developers are encouraged to update this material with additional topics and improve any of the existing sections. HTNG reserves the right to amend or delete any of these changes to protect the integrity of this documentation.
A number of assumptions are made within this current material. These include:
- The organization using this guide has HTNG member access to all of the HTNG libraries. For those that do not, membership information can be found at http://www.htng.org.
- Development is done using Visual Studio 2008 in the C# language
- The developer has some knowledge of the Visual Studio 2008 tools
- The developer has some knowledge of WSDLs, XML and Web Services. Some good education on these topics may be found at http://www.w3schools.com