Page Comparison

...

The partner will need to provide a web service with which the CRS can communicate responses to availability requests.

The following are the endpoints for the SHR GenHTNG API:

Authentication

Participating partner sites/channels will be obligated to provide appropriate credentials, as defined in the SOAP header, to utilize the CRS web services. Credentials include:

...

• User Name [ID] – a unique login name for authentication

• Password – a secure password corresponding to the user name 

Communication Pattern and SOAP Actions and Headers

The GenHTNG Interface uses a communication pattern called the “HTNG Asynchronous Communication Process”. This process is described in detail in section 4 of the HTNG Property Web Services Specification Release 2009B.

...

<?xml version="'1.0"' encoding="'UTF-8" '?>
<soap<n1:Envelope xmlns:xsin1= "http://www.w3.org/20012003/05/XMLSchemasoap-instanceenvelope" xmlns:xsdn3="http://wwwdocs.w3oasis-open.org/wss/2004/2001/XMLSchema";01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:soapn2="http://schemaswww.xmlsoapw3.org/soap2005/envelope08/addressing";> <soap:Header>
<HTNGHeader xmlnsxmlns:n4="http://htng.org/1.1/Header/";PWSWG/2007/02/AsyncHeaders">
<From> <systemId="145124"> <Credential> <userName="partner">
<password="a1b2c3"/>
</Credential>
</From>
<To>
<systemId="Windsurfer"/>
</To>
<timestamp>date</timestamp>
<echoToken />
<transactionId />
<action />
</HTNGHeader>
</soap:Header>
<soap:Body>
</soap:Body>
</soap:Envelope> <n1:Header>
		<n2:MessageID>{{MessageID}}</n2:MessageID>
		<n4:CorrelationID>2b36432943304e8d81ba5618d5df9e5a</n4:CorrelationID>
		<n2:Action>http://htng.org/PWSWG/2010/12/OTA_HotelResNotifRQ _SubmitRequest</n2:Action>
		<n2:To>https://uat.windsurfercrs.com/pms/genhtngservice.aspx</n2:To>
		<n2:ReplyTo>
			<n2:Address>http://www.w3.org/2005/08/addressing/role/anonymous</n2:Address>
		</n2:ReplyTo>
		<n3:Security mustUnderstand="1">
			<n3:UsernameToken>
				<n3:Username>{{UserName}}</n3:Username>
				<n3:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">{{Password}}</n3:Password>
			</n3:UsernameToken>
		</n3:Security>
		<n4:ReplyTo>
			<n2:Address>https://api-dev.protel.net/services/ProtelApiService.ProtelApiServiceHttpsSoap12Endpoint</n2:Address>
		</n4:ReplyTo>
	</n1:Header>

SOAP Fault Handling [Errors]

...

• Soap 1.2 envelope

• WS-Addressing 1.0

• WS Security (using Username/Password credentials) – WS Security requires use of https transport.

• Asynchronous Or Synchronous communication model

 There is currently no capability to produce a “wsdl” file. Schemas may be obtained from the Open Travel Alliance.

HTNG

...

Communication Process

The pattern is implemented using separate correlated asynchronous OR synchronous web service calls (call) for each HTNG message exchange. HTNG messages are always a request RQ and response (RS) message pair.

The exchange of a message pair starts a 5 stage (if successful) process.

Response to Inbound Requests:

Sync Response : Inbound request from PMS is processed and an immediate response is sent for that request.
Async Response : Inbound request from PMS and send the response to provided URL.
( In this case PMS provides the endpoint URL , on which response will be sent. This URL must be present in the CRS setup.)

Outbound Request from CRS to PMS (Reservations)

For response from PMS to the outbound request from CRS, Sync or Async response can be supported.

Sync Response: PMS needs to send an immediate response to the request.

Async Response: PMS needs to send response to the provided GenHTNG endpoint (which is also used to send inbound requests from PMS)

Reference Documents