How to Implement HTNG Web Services

If you already have experience writing web services, you should be able to visit our Specifications page, download what you need, and do what you are used to doing. However, if you have limited experience in writing web services, or if you run into questions about the specs, you may find these resources to be useful.


These resources require a current HTNG membership and login credentials.  If you work for a company that has a current membership but do not have your own login, you can request one.  Otherwise, join HTNG to get access.


Developer's Quick Start Guide

Implementing Web Services Using HTNG Specifications, A Quick Start Guide for Software Developers serves as a step-by-step reference for HTNG members who need assistance in quickly creating web services based upon published HTNG specifications. This is intended to be a living document and will expand in content based up-on member feedback.

The first release covers implementation using Java (with the Metro stack) in a NetBeans IDE. Future versions will likely cover Microsoft C# and additional Java Frameworks (including Eclipse and Axis).


HTNG Discussion Board

One of the best resources available to you is the Implementers' Discussion area on the HTNG Discussion Board.  Search the board to the answer to your question, or start a new thread. Our membership community has extensive experience in many areas, and people are always willing to help.  HTNG's technical staff also monitor the discussion as well and will help when they can.


Testing System

We have received feedback from our members that they would like access to a testing system. We are working toward this in three phases.

  • In the first phase, we staged and configured a server that is capable of responding to synchronous OTA_PingRQ requests using the HTNG Web Services Framework (including WS-Addressing and WS-Security).  This is deployed in beta test mode; if you would like access, please contact our workgroups mailbox.
  • We are currently working on the second phas,e which will add the ability to handle asynchronous communications, queuing, full message payload logging, and (HTNG) server-initiated messages.
  • The third phase will be to provide a reference implementation (both a client and a server) for each of our specifications. The order in which the specifications will be implemented will largely be based upon a combination of what we are asked to implement and what we can deliver quickly. At this time, Single Guest Itinerary and Guest & Room Status Messaging are the forerunners. The goal is to have a few interfaces implemented and available to our members to test against in the fourth quarter of 2011.