Hotel Technology Next Generation

Conformance Statement Questionnaire

Property Web Services

Version 2010A


Referenced Documents

  1. HTNG Property Web Services Product Specification 2010A
  2. HTNG Property Web Services Specifications 2009B

Part 1:  Web Services Framework Version 2.1.1
Part 2:  Single Guest Itinerary Version 2.2
Part 3:  Digital Signage Version 1.0
Part 4:  Open Data Exchange Version 1.4.2
Part 5:  Back Office Integration Version 2.0
Part 6:  Guest Self Service Version 1.0.3
Part 7:  Food and Beverage Ordering Version 1.0
Part 8:  Guest and Room Status Messaging Version 1.0

  1. HTNG Kiosk Integration Specifications 2010A
  2. WS-I Basic Profile 1.0
  3. WS-Security 1.0 Specification

Instructions to applicants are given in blue text.

Note to submitter: This form contains a series of questions that need to be answered. Please complete ALL the fields in the questionnaire below to produce a conformance statement for your product. Your completed form should be submitted as input to the web certification system. Please ensure that you use the current version of the questionnaire (available on the certification website) for your submission. See the Guide to HTNG Certification for more information. Please note that all information in this conformance statement will appear on the public register of certified products. Revision History showing the changes in this Conformance Statement from prior versions is contained at the end of this document.

Submitter Information

Q

1

Organization Name

Galaxy Hotel Systems LLC

A

1

Q

2

Contact Information

Bill Rosenberg

A

2

Product Information

Note to submitter: The information provided in this section must match the name and version information provided on the registration form when registering this product for certification. Please refer to section 3 of the Guide to HTNG Certification.

Q

3

Product Name

LightSpeed.

A

3

Q

4

Product Version/Identifier

9.4

A

4

Scope of Certification

Q

5

Specifications Implemented

The Product Specification requires conformance to either the Framework 2.1.1, the Back Office 2.0 Specification, or the Kiosk Integration 1.0 Specification. If conforming to anything other than Back Office 2.0 or Kiosk Integration 1.0, conformance to Framework 2.1.1 is mandatory.  Please indicate to which specifications the product conforms; at least one of the lines below must be answered ‘yes.’

A

5

HTNG Web Services Framework Version 2.1.1  (mandatory unless conforming ONLY to Back Office 2.0 or Kiosk Integration 1.0)

YES

HTNG Single Guest Itinerary Version 2.2 (optional)

YES

HTNG Digital Signage Version 1.0 (optional)

NO

HTNG Open Data Exchange Version 1.4.2 (optional)

NO

HTNG Back Office Integration Version 2.0 (optional)

NO

HTNG Guest Self Service Version 1.0.3 (optional)

NO

HTNG Food and Beverage Ordering Version 1.0 (optional)

NO

HTNG Guest and Room Status Messaging Version 1.0 (optional)

YES

HTNG Kiosk Integration Version 1.0 (optional)

NO

Web Services Framework 2.1.1 Conformance (mandatory unless conforming ONLY to Back Office 2.0 or Kiosk Integration 1.0)

Q

6

Identify the Web Services that utilize Web Services Framework 2.1.1

Please identify each Web service supported. The majority correspond to published HTNG Specifications. The last entry allows for proprietary services to be referenced.
Interoperability may be demonstrated by providing one of the following:

  1. The name of other companies with whom you have successfully interoperated.
  2. A test report from internal testing. These can be either a URL on your own website or as inline text in the Supporting Document Table below.
  3. Other evidence of a successful implementation.

At least one web service must be implemented unless conforming ONLY to Back Office 2.0 or Kiosk Integration 1.0.

A

6

Web Services Implemented

Web Service Name

Interoperable Vendors, Test Report URL, or Supporting Document Number (see table below)

HTNG Product Distribution Specifications 2010A - Part 1: Reservations Version 2.3

NO

HTNG Product Distribution Specifications 2010A - Part 2: Availability Version 2.2

Note: Release 2009B is identical and acceptable

NO

 

HTNG Product Distribution Specifications 2010A - Part 3: Statistics Version 2.0

Note: Releases 2009B, 2009A and 2008A are identical and acceptable

NO

 

HTNG Product Distribution Specifications 2010A - Part 4: Groups Version 1.1

Note: Release 2009B is identical and acceptable

NO

 

HTNG Product Distribution Specifications 2010A - Part 5: Rates Version 1.2

NO

 

HTNG Product Distribution Specifications 2010A - Part 6: Inventory Version 1.0

NO

HTNG Product Distribution Specifications 2010A - Part 7: Seamless Shop/Book Version 1.0

NO

HTNG Property Web Services Specifications 2009B - Part 2: Single Guest Itinerary Version 2.2
Note: Releases 2009A and 2008B are identical and acceptable

YES

SDD Systems Inc., TriplePlay Services

HTNG Property Web Services Specifications 2009B - Part 3: Digital Signage Version 1.0
Note: Releases 2009A, 2008B and 2008A are identical and acceptable

NO

HTNG Property Web Services Specifications 2009B - Part 4: Open Data Exchange Version 1.4.2

Note: Release 2009A is identical and acceptable

NO

HTNG Property Web Services Specifications 2009B - Part 6: Guest Self Service Version 1.0.3

Note: Release 2009A is identical and acceptable

NO

HTNG Property Web Services Specifications 2009B - Part 7: Food and Beverage Ordering Version 1.0

Note: Releases 2009A and 2008B are identical and acceptable

NO

 

HTNG Property Web Services Specification 2009B – Part 8: Guest and Room Status Messaging Version 1.0

YES

SDD Systems Inc., TriplePlay Services

HTNG Property Web Services Specifications 2008B - Part 4: Open Data Exchange Version 1.4.1

NO

HTNG Property Web Services Specifications 2008B - Part 6: Guest Self Service Version 1.0.1

NO

HTNG Property Web Services Specifications 2008A - Part 2: Single Guest Itinerary Version 1.0

Note: Release 2007A is identical and acceptable

NO

 

HTNG Property Web Services Specifications 2008A - Part 4: Open Data Exchange Version 1.0

NO

HTNG Property Web Services Specifications 2008A - Part 6: Guest Self Service Version 1.0

NO

HTNG Property/Distribution Specifications 2009B - Part 1: Reservations Version 2.2

NO

 

HTNG Property/Distribution Specifications 2009B - Part 2: Availability Version 2.2

NO

 

HTNG Property/Distribution Specifications 2009B - Part 3: Statistics Version 2.0

Note: Releases 2009A and 2008A are identical and acceptable

NO

 

HTNG Property/Distribution Specifications 2009B - Part 4: Groups Version 1.1

NO

 

HTNG Property/Distribution Specifications 2009B - Part 5: Rates Version 1.2

NO

 

HTNG Property/Distribution Specifications 2009A - Part 1: Reservations Version 2.1

NO

HTNG Property/Distribution Specifications 2009A - Part 2: Availability Version 2.1

NO

HTNG Property/Distribution Specifications 2009A - Part 4: Groups Version 1.0

Note: Release 2008A is identical and acceptable

NO

HTNG Property/Distribution Specifications 2009A - Part 5: Rates Version 1.1

NO

HTNG Property/Distribution Specifications 2008A - Part 1: Reservations Version 2.0

NO

HTNG Property/Distribution Specifications 2008A - Part 2: Availability Version 2.0

NO

HTNG Property/Distribution Specifications 2008A - Part 5: Rates Version 1.0

Note: Release 2007A is identical and acceptable

NO

HTNG Property/Distribution Specifications 2007A - Part 1: Reservations Version 1.0

NO

HTNG Property/Distribution Specifications 2007A - Part 2: Availability Version 1.0

NO

Proprietary System(s)

NO

 

Q

7

Details of Proprietary Systems

Please provide a summary description of any proprietary systems identified in A6.
Add rows to the table as required.

A

7

System Name

Version Number

Summary of System Details

Contact Name

Date of Implementation

Q

8

Supporting Documents

The table below defines six possible supporting documents which provide evidence of conformance. Four of these are mandatory (denoted by shading). The Published API Specification should be used to reference the published HTNG specification that is supported. These documents may be provided either as a URL to an external site or as inline text in the Supporting Document Table below.

Replicate this table for each Web Service supported.

A

8

HTNG Property Web Services Specifications 2009B - Part 2: Single Guest Itinerary Version 2.2

Documentation Provided

Mandatory/
Optional

HTNG Specification Reference, URL, or Supporting Document Number (see table below)

WSDL

Mandatory

HTNG Property Web Services Specifications 2009B - Part 2: Single Guest Itinerary Version 2.2

http://collaboration.htng.org/specs/documents/22377/HTNG_PropertyWebServices_2009B_supporting_files.zip

Schemas externally referenced in WSDL

Mandatory

HTNG Property Web Services Specifications 2009B - Part 2: Single Guest Itinerary Version 2.2

 http://collaboration.htng.org/specs/documents/22377/HTNG_PropertyWebServices_2009B_supporting_files.zip

SOAP Packet Trace

Mandatory

Reservation Lookup – see Supporting Document 1

Fetch Reservation – see Supporting Document 2

Post Payment – see Supporting Document 3

 

Published API Specification

Mandatory for HTNG defined Web Services

HTNG Property Web Services Specifications 2009B - Part 2: Single Guest Itinerary Version 2.2

 http://collaboration.htng.org/specs/documents/22377/HTNG_PropertyWebServices_Technical_Specification_2009B_Issue2_FINAL.pdf

Write-up on WS Security Implementation

Optional

 Supporting Document 8

Write-up on WS Addressing Implementation

Optional

 Supporting Document 9

A

8

HTNG Property Web Services Specification 2009B – Part 8: Guest and Room Status Messaging Version 1.0

Documentation Provided

Mandatory/
Optional

HTNG Specification Reference, URL, or Supporting Document Number (see table below)

WSDL

Mandatory

HTNG Property Web Services Specification 2009B – Part 8: Guest and Room Status Messaging Version 1.0

 

 http://collaboration.htng.org/specs/documents/22377/HTNG_PropertyWebServices_2009B_supporting_files.zip

Schemas externally referenced in WSDL

Mandatory

HTNG Property Web Services Specification 2009B – Part 8: Guest and Room Status Messaging Version 1.0

 

http://collaboration.htng.org/specs/documents/22377/HTNG_PropertyWebServices_2009B_supporting_files.zip

SOAP Packet Trace

Mandatory

HTNG_CheckInNotification – see Supporting Document 4

HTNG_CheckOutNotification  – see Supporting Document 5

HTNG_RoomMoveNotification  – see Supporting Document 6

HTNG_StayUpdateNotification – see Supporting Document 7

 

Published API Specification

Mandatory for HTNG defined Web Services

HTNG Property Web Services Specification 2009B – Part 8: Guest and Room Status Messaging Version 1.0

 

 http://collaboration.htng.org/specs/documents/22377/HTNG_PropertyWebServices_Technical_Specification_2009B_Issue2_FINAL.pdf

Write-up on WS Security Implementation

Optional

  Supporting Document 8

Write-up on WS Addressing Implementation

Optional

 Supporting Document 9

Q

9

Communication Style

Indicate which communication methods the product supports. At least one communication style must be supported.

A

9

Communication Style

Synchronous

YES

Asynchronous

NO

Single Guest Itinerary Conformance (optional)

Q

10

Roles

 

 

Please check all Single Guest Itinerary Web Service roles for which the product is being certified. At least one role must be supported.

A

10

Role

Activity Reservation System

NO

Accommodation Reservation System

NO

Posting System

YES

Folio System

YES

Customer Profile System

NO

Itinerary Consolidation System

NO

Itinerary Display System

NO

Q

11

Activity Reservation System Role

 

 

If the product performs the role of an Activity Reservation System please indicate which functions and messages are supported. Shaded cells indicate mandatory functionality. Black cells are not applicable.

A

11

Function/Message Description

Function/Message Name

Mandatory/
Optional

Can provide these web service functions

Can initiate these messages

Lookup Activities for matching guests

ActivityLookup

Mandatory

NO

 

Create Activity

CreateActivity

Mandatory

 

NO

Update Activity

UpdateActivity

Mandatory

 

NO

Cancel Activity

CancelActivity

Mandatory

 

NO

List Activities for a specific guest

FetchActivities

Mandatory

NO

 

Lookup Matching Guest Profiles

ProfileLookup

Mandatory

NO

NO

Fetch detailed information for a specific guest profile

FetchProfile

Mandatory

NO

NO

Create new profile

NewProfile

Optional

NO

NO

Modify existing profile

UpdateProfile

Mandatory

NO

NO

Notify when appointment time is outside of stay dates

OutOfScopeNotification

Mandatory

NO

 

Notification of status change

GuestStatusNotification

Mandatory

NO

 

Link new profile ID to another system

Subscription

Mandatory

NO

NO

Lookup matching reservations

ReservationLookup

Optional

 

NO

Fetch specific reservation details

FetchReservation

Optional

 

NO

Notify of guest location

LocationNotification

Optional

 

NO

Send guest message

GuestMessage

Optional

 

NO

Merge guest profile

MergeProfile

Mandatory

NO

NO

Q

12

Accommodation Reservation System Role

 

 

If the product performs the role of an Accommodation Reservation System please indicate which functions and messages are supported. Shaded cells indicate mandatory functionality. Black cells are not applicable.

A

12

Function/Message Description

Function/Message Name

Mandatory/
Optional

Can provide these web service functions

Can initiate these messages

Notify when reservation stay date range with scheduled appointment is moved outside of appointment date

OutOfScopeNotification

Mandatory

 

NO

Notification of status change

GuestStatusNotification

Mandatory

 

NO

Lookup matching reservations

ReservationLookup

Mandatory

NO

 

Fetch specific reservation details

FetchReservation

Mandatory

NO

 

Notify of guest location

LocationNotification

Mandatory

NO

 

Send guest message

GuestMessage

Mandatory

NO

 

Q

13

Posting System Role

 

 

If the product performs the role of a Posting System please indicate which functions and messages are supported. Shaded cells indicate mandatory functionality. Black cells are not applicable.

A

13

Function/Message Description

Function/Message Name

Mandatory/
Optional

Can provide these web service functions

Can initiate these messages

Post charge

PostPayment

Mandatory

 

YES

Retrieve details of a POS check

FetchCheckDetails

Optional

NO

Q

14

Folio System Role

 

 

If the product performs the role of a Folio System please indicate which functions and messages are supported. Shaded cells indicate mandatory functionality. Black cells are not applicable.

A

14

Function/Message Description

Function/Message Name

Mandatory/
Optional

Can provide these web service functions

Can initiate these messages

Post charge for related activity

PostPayment

Mandatory

YES

 

Retrieve details of a POS check

FetchCheckDetails

Optional

NO

Q

15

Customer Profile System Role

 

 

If the product performs the role of a Customer Profile System please indicate which functions and messages are supported. Shaded cells indicate mandatory functionality. Black cells are not applicable.

A

15

Function/Message Description

Function/Message Name

Mandatory/
Optional

Can provide these web service functions

Can initiate these messages

Lookup Matching Guest Profiles

ProfileLookup

Mandatory

NO

NO

Fetch detailed information for a specific guest profile

FetchProfile

Mandatory

NO

NO

Create new profile

NewProfile

Optional

NO

NO

Modify existing profile

UpdateProfile

Mandatory

NO

NO

Link new profile ID to another system

Subscription

Mandatory

NO

NO

Merge guest profile

MergeProfile

Mandatory

NO

NO

Q

16

Itinerary Consolidation System Role

 

 

If the product performs the role of an Itinerary Consolidation System please indicate which functions and messages are supported. Shaded cells indicate mandatory functionality. Black cells are not applicable.

A

16

Function/Message Description

Function/Message Name

Mandatory/
Optional

Can provide these web service functions

Can initiate these messages

Lookup Activities for matching guests

ActivityLookup

Mandatory

NO

NO

Create Activity

CreateActivity

Mandatory

NO

 

Update Activity

UpdateActivity

Mandatory

NO

 

Cancel Activity

CancelActivity

Mandatory

NO

 

List Activities for a specific guest

FetchActivities

Mandatory

NO

NO

Q

17

Itinerary Display System Role

 

 

If the product performs the role of an Itinerary Display System please indicate which functions and messages are supported. Shaded cells indicate mandatory functionality. Black cells are not applicable.

A

17

Function/Message Description

Function/Message Name

Mandatory/
Optional

Can provide these web service functions

Can initiate these messages

List Activities for a specific guest

FetchActivities

Mandatory

 

NO

Lookup matching reservations

ReservationLookup

Mandatory

 

NO

Digital Signage Conformance (optional)

Q

18

Roles

Please check all Digital Signage Web Service roles for which the product is being certified. At least one role must be supported.

A

18

Does the Product function as an Event Information Display Manager?

NO

Does the Product function as an Event and Meeting Space Manager?

NO

 

 

Event Information Display Manager Role

Q

19

If the product performs the role of an Event Information Display Manager please indicate which functions and messages are supported. Shaded cells indicate mandatory functionality. Black cells are not applicable.

A

19

Function/Message Description

Function/Message Name

Mandatory/
Optional

Can provide these web service functions

Can initiate/consume these messages

Request Reserved Meeting Space

MeetingSpaceRequest

Mandatory

 

NO

MeetingSpaceResponse

Mandatory

 

NO

Request Meeting Space Characteristics

MeetingSpaceCharacteristicsRequest

Mandatory

 

NO

MeetingSpaceCharacteristicsResponse

Mandatory

 

NO

Q

20

If the product performs the role of an Event Information Display Manager please indicate which message parameters are supported.

A

20

Request Message / Request Event Information By:

Parameter Name

Mandatory/
Optional

Start Time

startTime

Optional

NO

End Time

endTime

Optional

NO

Event Identifier

eventKey

Optional

NO

Exhibit Flag – Y/N

isExhibit

Optional

NO

Postable Flag – Y/N

isPostable

Optional

NO

Room Grouping

roomGrouping

Optional

NO

 

Parameter Description

Parameter Name

Mandatory/
Optional

Group logo URL or pathname

logoURL

Optional

NO

Meeting Name and related identifier

meetingName

Optional

NO

Meeting “Post As” Name

meetingPostAs

Optional

NO

Host Event Identifier

hostEventKey

Optional

NO

Exhibit Flag – Y/N

isExhibit

Optional

NO

Postable Flag – Y/N

isPostable

Optional

NO

Backup Meeting Room Space Name

backupMeetingRoomName

Optional

NO

Overflow Meeting Room Space Name

overflowMeetingRoomName

Optional

NO

Response Complete – Y/N

isResponseComplete

Optional

NO

 

 

Event and Meeting Space Manager Role

Q

21

If the product performs the role of an Event and Meeting Space Manager please indicate which functions and messages are supported. Shaded cells indicate mandatory functionality. Black cells are not applicable.

A

21

Function/Message Description

Function/Message Name

Mandatory/
Optional

Can provide these web service functions

Can initiate/consume these messages

Request Reserved Meeting Space

MeetingSpaceRequest

Mandatory

NO

 

MeetingSpaceResponse

Mandatory

NO

 

Request Meeting Space Characteristics

MeetingSpaceCharacteristicsRequest

Mandatory

NO

 

MeetingSpaceCharacteristicsResponse

Mandatory

NO

 

Q

22

If the product performs the role of an Event and Meeting Space Manager please indicate which message parameters are supported.

A

22

Parameter Description

Parameter Name

Mandatory/
Optional

Floor Number

floorNumber

Optional

NO

Floor Description

floorDescription

Optional

NO

Room Grouping

roomGrouping

Optional

NO

Directions

directions

Optional

NO

Is Room Divisible – Y/N

isDivisible

Optional

NO

Parent Room Identifier

parentRoomKey

Optional

NO

Map Reference Number

mapReferenceNum

Optional

NO

NO

Response Complete - Y/N

isResponseComplete

Optional

NO

Open Data Exchange (optional)

Q

23

Roles

Please check all Open Data Exchange Web Service roles for which the product is being certified. At least one role must be supported.

A

23

Does the Product function as a Data Receiver?

NO

Does the Product function as a Data Sender

NO

Q

24

Data Receiver

If the product performs the role of a Data Receiver, please indicate which functions and messages are supported. At least one of the two Function/Message Names must be supported.  Black cells are not applicable.

A

24

Function/Message
Description

Function/Message
Name

Can provide these

Can initiate these 

Push Files

PushFile

NO

Pull Files

PullFile

NO

Q

25

Data Sender

If the product performs the role of Data Sender, please indicate which functions and messages are supported. At least one of the Function/Message Names must be supported.

A

25

Function/Message
Description

Function/Message
Name

Can provide these

Can initiate these 

Push Files

PushFile

NO

Oull Files

PullFile

NO

Back Office Integration (optional)

 

Service Implementers

Q

26

In order to post an entry into an Accounting Application, it is typically required that the entry be balanced (debits equal credits), but it is realized that many Service Callers do not have mechanisms in place to perform or ensure such balancing.  As such, we are requiring the Service Implementer to ensure that any balancing requirements are met.

A

26

Please indicate whether your application includes balancing functionality.

Mandatory

NO

Q

27

Data transformations (e.g. Account Code Mapping, Transaction Analysis, Appending…) is not a function of the Specification but is a known requirement to send data to a Back Office Destination. 

A

27

Please indicate whether your application will include transformation functionality.

Optional

NO

Q

28

Understanding that many service callers cannot accommodate destination Attributes, it will be the responsibility of Service Implementer to ensure the proper Attributes required by the Destination system are present.

A

28

Please indicate whether your application includes functionality to accommodate Destination System Attributes.

Optional

NO

Q

29

If there is a desire to ensure that payloads received are not processed multiple times, the service implementer can utilize and track a combination of the SourceID and MessageID elements of the PostGeneralLedgerData element. This will be the responsibility of the destination Service Implementer but it can only be implemented if the source ensures that the SourceID and MessageID elements are used correctly.

A

29

Please indicate whether your application ensures that payloads with unique combinations of SourceID and MessageID are not processed multiple times.

Optional

NO

 

Service Callers

Q

30

There is a desire to ensure that payloads received are not processed multiple times.  The service implementer can utilize and track a combination of the SourceID and MessageID elements of the PostGeneralLedgerData element. The source ensures that the SourceID and MessageID elements are used correctly.

A

30

Will you ensure that MessageID elements will be unique for every service call?

Mandatory

NO

Q

31

Statistical entries such as Hours Worked should be transmitted in the form of GLJournalLine and the statistical value should be stored as the Amount.

A

31

Please indicate whether your application includes statistical values.

Mandatory

NO

Q

32

Accounting Applications have specific Account Types, such as Revenue for which a positive number must be indicated as a Credit, as compared to an Expense for which a positive number is a Debit.  In addition, Accounting Applications require non-statistical entries to balance.

A

32a

Please indicate whether your Debit/Credit indicators will be in line with the GAAP principles.

Optional

NO

A

32b

Please indicate whether you will be providing a balanced file (Debits equal Credits) for non-statistical amounts.

Optional

NO

Q

33

Data transformations (e.g. Account Code Mapping, Transaction Analysis, Appending…) is not a function of the Specification but is an expected requirement to send data to a Back Office Destination. 

A

33

Please indicate whether your payload will provide data using the destination accounting systems scheme (will you provide account code mapping?).

Optional

NO

Q

34

Back Office Specification 2.0 covers only generic General Ledger Transactions, and additional specifications will be provided regarding specific transaction types in the future.  Below, we have proposed Attribute Names by Role.   Service Callers should indicate the attributes they will be providing:

A

34

GLAttribute Name

GLAttribute Value

Parent of GLAttribute

Example

Mandatory/ Optional

Will Provide

RETAIL

 

RevenueCenter

String

GLJournalLine

Specific code, name of outlet

Optional

NO

Shift

String

GLJournalLine

Time Period (am, pm)

Optional

NO

CustomerType

String

GLJournalLine

Resident, Non-Resident

Optional

NO

 

F&B

 

RevenueCenter

String

GLJournalLine

Specific code, name of outlet

Optional

NO

Revenue CenterType

String

GLJournalLine

Bar, Self Service

Optional

NO

MealPeriod

String

GLJournalLine

Breakfast, Lunch, Dinner

Optional

NO

CustomerType

String

GLJournalLine

Resident, Non-Resident

Optional

NO

 

HOTEL PMS

 

Department

String

GLJournalLine

Front Office, Housekeeping

Optional

NO

MarketSegment

String

GLJournalLine

Luxury, Business

Optional

NO

BookingSource

String

GLJournalLine

Email, Phone, Walk-in, Internet

Optional

NO

RoomType

String

GLJournalLine

Single, Double, Suite

Optional

NO

CustomerType

String

GLJournalLine

Resident, Non-Resident

Optional

NO

 

SPA

 

RevenueCenter

String

GLJournalLine

Specific code or name

Optional

NO

ActivityType

String

GLJournalLine

Massage, Peeling

Optional

NO

ProviderType

String

GLJournalLine

Internal, External, Therapist Qualification

Optional

NO

FacilityType

String

GLJournalLine

Pool, Sauna

Optional

NO

Package

String

GLJournalLine

Specific code or name

Optional

NO

 

GOLF

 

GolfClub

String

GLJournalLine

Specific code or name

Optional

NO

GolfCourse

String

GLJournalLine

Specific code or name

Optional

NO

CustomerType

String

GLJournalLine

Resident, Non-Resident

Optional

NO

Package

String

GLJournalLine

Specific code or name

Optional

NO

FeeType

String

GLJournalLine

Green fee, Member fee

Optional

NO

 

LABOR OR PAYROLL

Employee

String

GLJournalLine

Code, Name, Number

Optional

NO

Position

String

GLJournalLine

Front Office Manager, Bartender

Optional

NO

Department

String

GLJournalLine

Marketing, Finance, Front Office

Optional

NO

Increment

String

GLJournalLine

Daily, Weekly, Monthly

Optional

NO

Guest Self Service (optional)

Q

35

Roles

Please check all Guest Self Service Web Service roles for which the product is being certified. At least one role must be supported.

A

35

Role

Self Service Frontend

NO

Services Scheduling System

NO

Q

36

Self Service Frontend

If the product performs the role of a Self Service Frontend please indicate which functions and messages are supported. Shaded cells indicate mandatory functionality. Black cells are not applicable.

A

36

Function/Message Description

Function/Message Name

Mandatory/
Optional

Can provide these web service functions

Can initiate these messages

 

Create new profile

NewProfile

Optional

NO

NO

Modify existing profile

UpdateProfile

Mandatory

NO

NO

Merge guest profile

MergeProfile

Mandatory

NO

NO

 

List template categories

TemplateCategory

Mandatory

 

NO

List templates

TemplateInfo

Mandatory

 

NO

List payment conditions

PaymentCondition

Optional

 

NO

Request availabilities

Availability

Mandatory

 

NO

Create booking

Create

Mandatory

 

NO

Delete booking

Delete

Optional

 

NO

Pay bookings

Sale

Optional

 

NO

List bookings

FetchBooking

Optional

 

NO

Q

37

Services Scheduling System

If the product performs the role of a Services Scheduling System please indicate which functions and messages are supported. Shaded cells indicate mandatory functionality. Black cells are not applicable.

A

37

Function/Message Description

Function/Message Name

Mandatory/
Optional

Can provide these web service functions

Can initiate these messages

 

Create new profile

NewProfile

Optional

NO

NO

Modify existing profile

UpdateProfile

Mandatory

NO

NO

Merge guest profile

MergeProfile

Mandatory

NO

NO

 

List template categories

TemplateCategory

Mandatory

NO

 

List templates

TemplateInfo

Mandatory

NO

 

List payment conditions

PaymentCondition

Optional

NO

 

Request availabilities

Availability

Mandatory

NO

 

Create booking

Create

Mandatory

NO

 

Delete booking

Delete

Optional

NO

 

Pay bookings

Sale

Optional

NO

 

List bookings

FetchBooking

Optional

NO

 

Food and Beverage Ordering (optional)

Q

38

Roles

Please check all Food and Beverage Ordering Web Service roles for which the product is being certified. At least one role must be supported.

A

38

Role

Device (Kiosk, Touch Screen, In-Room TV, IP Phone, etc)

NO

Food and Beverage POS System

NO

Q

39

Device Role

If the product performs the Device Role please indicate which functions and messages are supported. Shaded cells indicate mandatory functionality. Black cells are not applicable.

A

39

Function/Message Description

Function/Message Name

Mandatory/
Optional

Can provide these web service functions

Can initiate these messages

Gets configuration information

GetConfigurationInfo

Mandatory

NO

Calculates transaction totals

CalculateTotals

Mandatory

NO

Gets a transaction

GetTransaction

Mandatory

NO

Gets a transaction delivery status

GetTransactionDeliveryStatus

Mandatory

NO

Post new transaction

PostNewTransaction

Mandatory

NO

Spit a transaction into multiple transactions

SplitTransaction

Mandatory

NO

Q

40

Food and Beverage POS System

If the product performs the role of a Food and Beverage POS System please indicate which functions and messages are supported. Shaded cells indicate mandatory functionality. Black cells are not applicable.

A

40

Function/Message Description

Function/Message Name

Mandatory/
Optional

Can provide these web service functions

Can initiate these messages

Gets configuration information

GetConfigurationInfo

Mandatory

NO

Calculates transaction totals

CalculateTotals

Mandatory

NO

Gets a transaction

GetTransaction

Mandatory

NO

Gets a transaction delivery status

GetTransactionDeliveryStatus

Mandatory

NO

Post new transaction

PostNewTransaction

Mandatory

NO

Spit a transaction into multiple transactions

SplitTransaction

Mandatory

NO

Guest and Room Status Messaging (optional)

Q

41

Roles

 

Please check all roles for which the product is being certified.  If you are certifying to the Guest and Room Status Messaging Specification, you must select at least one of the following roles.

A

41

Role

Room Stay Information Provider

YES

Room Stay Information Consumer

NO

Q

42

Room Stay Information Provider

 

If the product performs the role of a Room Stay Information Provider, please indicate which functions and messages are supported. Shaded cells indicate mandatory functionality. Black cells are not applicable.

A

42

Message Description

Message Name

Mandatory/
Optional

Can provide these web service functions

Can initiate these messages

Send Guest Check-In Notification Message

HTNG_CheckInNotification

Mandatory

YES

Send Guest Check-Out Notification Message

HTNG_CheckOutNotification

Mandatory

YES

Send Guest Room-Move Notification Message

HTNG_RoomMoveNotification

Mandatory

YES

Send Stay Update Notification Message

HTNG_StayUpdateNotification

Mandatory

YES

Q

43

Room Stay Information Consumer

 

If the product performs the role of a Room Stay Information Consumer, please indicate which functions and messages are supported. Shaded cells indicate mandatory functionality. Black cells are not applicable.

A

43

Message Description

Message Name

Mandatory/
Optional

Can provide these web service functions

Can initiate these messages

Receive Guest Check-In Notification Message

HTNG_CheckInNotification

Mandatory

NO

NO

Receive Guest Check-Out Notification Message

HTNG_CheckOutNotification

Mandatory

NO

NO

Receive Guest Room-Move Notification Message

HTNG_RoomMoveNotification

Mandatory

NO

NO

Receive Stay Update Notification Message

HTNG_StayUpdateNotification

Mandatory

NO

NO

Kiosk Integration (optional)

Q

44

Roles

 

 

Please check all roles for which the product is being certified. At least one role must be supported.

A

44

Role

Kiosk Application

NO

PMS Application

NO

Q

45

Kiosk Application

 

 

If the product performs the role of a Kiosk Application, please indicate which functions and messages are supported. Shaded cells indicate mandatory functionality. Black cells are not applicable.

A

45

Function/Message Description

Function/Message Name

Mandatory/
Optional

Can provide these web service functions

Can initiate these messages

Find Booking

OTA_ReadRQ

Mandatory

NO

Modify Booking

OTA_HotelResNotifRQ

Optional

 

NO

Authorize Card

HTNG_ PaymentCardProcessingRQ

Optional

NO

Check-In

OTA_HotelResNotifRQ

Mandatory

NO

Cut Key Request

HTNG_HotelKeyEncodeRQ

Optional

NO

Retrieve Folio

HTNG_HotelFolioRQ

Mandatory

NO

Charge Card

HTNG_ PaymentCardProcessingRQ

Optional

NO

Check Out

OTA_HotelResNotifRQ

Mandatory

NO

Q

46

PMS Application

 

 

If the product performs the role of a PMS Application, please indicate which functions and messages are supported. Shaded cells indicate mandatory functionality. Black cells are not applicable.

A

46

Function/Message Description

Function/Message Name

Mandatory/
Optional

Can provide these web service functions

Can initiate these messages

Find Booking

OTA_ReadRQ

Mandatory

NO

Modify Booking

OTA_HotelResNotifRQ

Optional

NO

Authorize Card

HTNG_PaymentCardProcessingRQ

Optional

NO

Check-In

OTA_HotelResNotifRQ

Mandatory

NO

Cut Key Request

HTNG_ HotelKeyEncodeRQ

Optional

NO

Retrieve Folio

HTNG_ HotelFolioRQ

Mandatory

NO

Charge Card

HTNG_ PaymentCardProcessingRQ

Optional

NO

Check Out

OTA_HotelResNotifRQ

Mandatory

NO

Certification Summary

 

 

The Trademark License Agreement allows for a Product Specification to require display of a Certification Summary along with the Trademark. For this Product Specification, no summary is required.

Supporting Document Table

 

 

The following table is provided for supporting documents identified in Q6 and Q8. If the document cannot be referenced as a URL, please insert the contents of the document into a row of the table below, adding an appropriate title and referencing it in A6 or A8 above. Insert additional table entries as required.

 

 

 

Supporting Document 1

1

 Request:

 

POST /LightSpeedXmlWeb/services/ReservationProviderPortType HTTP/1.0

Content-Type: text/xml; charset=utf-8

Accept: application/soap+xml, application/dime, multipart/related, text/*

User-Agent: Axis/1.4

Host: 127.0.0.1:8091

Cache-Control: no-cache

Pragma: no-cache

SOAPAction: "http://htng.org/PWS/2008A/SingleGuestItinerary#FetchReservation"

Content-Length: 1558

 

 

 

<?xml version="1.0" encoding="UTF-8"?>

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

   <soapenv:Header>

      <wsse:Security soapenv:mustUnderstand="1" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">

         <wsse:UsernameToken wsu:Id="UsernameToken-1" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">

            <wsse:Username>HTUSER</wsse:Username>

            <wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">htPassword</wsse:Password>

         </wsse:UsernameToken>

      </wsse:Security>

      <wsa:MessageID soapenv:mustUnderstand="0">uuid:bc98f870-6522-11e0-9aba-960ce609374e</wsa:MessageID>

      <wsa:To soapenv:mustUnderstand="0">http://localhost:8090/LightSpeedXmlWeb/services/ReservationProviderPortType</wsa:To>

      <wsa:Action soapenv:mustUnderstand="0">http://htng.org/PWS/2008A/SingleGuestItinerary#ReservationLookup</wsa:Action>

      <From soapenv:mustUnderstand="0" xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing">

         <Address>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</Address>

      </From>

   </soapenv:Header>

   <soapenv:Body>

      <ReservationLookupRequest xmlns="http://htng.org/PWS/2008A/SingleGuestItinerary/Reservation/Types">

         <ReservationLookupData reservationStatus="CHECKED_IN">

            <ProfileInfo>

               <ns1:LastName xmlns:ns1="http://htng.org/PWS/2008A/SingleGuestItinerary/Common/Types">Adams</ns1:LastName>

            </ProfileInfo>

            <ResortId>5608</ResortId>

         </ReservationLookupData>

      </ReservationLookupRequest>

   </soapenv:Body>

</soapenv:Envelope>

 

 

Response:

 

 

HTTP/1.1 200 OK

Server: Apache-Coyote/1.1

X-Powered-By: Servlet 2.4; Tomcat-5.0.28/JBoss-4.0.1sp1 (build: CVSTag=JBoss_4_0_1_SP1 date=200502160314)

Set-Cookie: JSESSIONID=861148184CE4F64306DCF8B7EF30B215; Path=/

Content-Type: text/xml;charset=utf-8

Date: Mon, 13 Jun 2011 16:29:45 GMT

Connection: close

 

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing">

   <soapenv:Header>

      <wsa:MessageID soapenv:mustUnderstand="0">uuid:a665ffb0-95d5-11e0-be39-d30c18650bf1</wsa:MessageID>

      <wsa:To soapenv:mustUnderstand="0">http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</wsa:To>

      <wsa:Action soapenv:mustUnderstand="0">http://htng.org/PWS/2008A/SingleGuestItinerary#ReservationLookupResponse</wsa:Action>

      <wsa:From soapenv:mustUnderstand="0" xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing">

         <wsa:Address>http://localhost:8090/LightSpeedXmlWeb/services/ReservationProviderPortType</wsa:Address>

      </wsa:From>

      <wsa:RelatesTo RelationshipType="wsa:Reply" soapenv:mustUnderstand="0">uuid:bc98f870-6522-11e0-9aba-960ce609374e</wsa:RelatesTo>

   </soapenv:Header>

   <soapenv:Body>

      <ReservationLookupResponse xmlns="http://htng.org/PWS/2008A/SingleGuestItinerary/Reservation/Types">

         <Result resultStatusFlag="SUCCESS"/>

         <ReservationLookups>

            <ReservationLookup reservationStatus="CHECKED_IN">

               <ReservationID>92350</ReservationID>

               <RoomNumber>851</RoomNumber>

               <DateRange>

                  <ns1:Start xmlns:ns1="http://htng.org/PWS/2008A/SingleGuestItinerary/Activity/Types">2010-11-09T07:00:00.000Z</ns1:Start>

                  <ns2:End xmlns:ns2="http://htng.org/PWS/2008A/SingleGuestItinerary/Activity/Types">2010-11-14T07:00:00.000Z</ns2:End>

               </DateRange>

               <ProfileInfo familiarName="Adams, a">

                  <ns3:FirstName xmlns:ns3="http://htng.org/PWS/2008A/SingleGuestItinerary/Common/Types">a</ns3:FirstName>

                  <ns4:LastName xmlns:ns4="http://htng.org/PWS/2008A/SingleGuestItinerary/Common/Types">Adams</ns4:LastName>

               </ProfileInfo>

               <ReservationAddress>

                  <ns5:AddressLine xmlns:ns5="http://htng.org/PWS/2008A/SingleGuestItinerary/Common/Types">12345 Main Street</ns5:AddressLine>

                  <ns6:CityName xmlns:ns6="http://htng.org/PWS/2008A/SingleGuestItinerary/Common/Types">Herculaneum</ns6:CityName>

                  <ns7:StateProv xmlns:ns7="http://htng.org/PWS/2008A/SingleGuestItinerary/Common/Types">MO</ns7:StateProv>

                  <ns8:CountryCode xmlns:ns8="http://htng.org/PWS/2008A/SingleGuestItinerary/Common/Types">USA</ns8:CountryCode>

                  <ns9:PostalCode xmlns:ns9="http://htng.org/PWS/2008A/SingleGuestItinerary/Common/Types">63048-1539</ns9:PostalCode>

               </ReservationAddress>

               <ConfirmationNo>92350</ConfirmationNo>

               <ResortId>5608</ResortId>

            </ReservationLookup>

            <ReservationLookup reservationStatus="CHECKED_IN">

               <ReservationID>137056</ReservationID>

               <RoomNumber>662</RoomNumber>

               <DateRange>

                  <ns10:Start xmlns:ns10="http://htng.org/PWS/2008A/SingleGuestItinerary/Activity/Types">2010-11-13T07:00:00.000Z</ns10:Start>

                  <ns11:End xmlns:ns11="http://htng.org/PWS/2008A/SingleGuestItinerary/Activity/Types">2010-11-20T07:00:00.000Z</ns11:End>

               </DateRange>

               <ProfileInfo familiarName="Adams, Larry">

                  <ns12:FirstName xmlns:ns12="http://htng.org/PWS/2008A/SingleGuestItinerary/Common/Types">Larry</ns12:FirstName>

                  <ns13:LastName xmlns:ns13="http://htng.org/PWS/2008A/SingleGuestItinerary/Common/Types">Adams</ns13:LastName>

               </ProfileInfo>

               <ReservationAddress>

                  <ns14:AddressLine xmlns:ns14="http://htng.org/PWS/2008A/SingleGuestItinerary/Common/Types">12345 Main Street</ns14:AddressLine>

                  <ns15:CityName xmlns:ns15="http://htng.org/PWS/2008A/SingleGuestItinerary/Common/Types">Bethel Heights</ns15:CityName>

                  <ns16:StateProv xmlns:ns16="http://htng.org/PWS/2008A/SingleGuestItinerary/Common/Types">AR</ns16:StateProv>

                  <ns17:CountryCode xmlns:ns17="http://htng.org/PWS/2008A/SingleGuestItinerary/Common/Types">USA</ns17:CountryCode>

                  <ns18:PostalCode xmlns:ns18="http://htng.org/PWS/2008A/SingleGuestItinerary/Common/Types">72764</ns18:PostalCode>

               </ReservationAddress>

               <ConfirmationNo>137056</ConfirmationNo>

               <ResortId>5608</ResortId>

            </ReservationLookup>

         </ReservationLookups>

      </ReservationLookupResponse>

   </soapenv:Body>

</soapenv:Envelope>

 

Supporting Document 2

2

 Request:

 

 

 POST /LightSpeedXmlWeb/services/ReservationProviderPortType HTTP/1.0

Content-Type: text/xml; charset=utf-8

Accept: application/soap+xml, application/dime, multipart/related, text/*

User-Agent: Axis/1.4

Host: 127.0.0.1:8091

Cache-Control: no-cache

Pragma: no-cache

SOAPAction: "http://htng.org/PWS/2008A/SingleGuestItinerary#FetchReservation"

Content-Length: 1558

 

<?xml version="1.0" encoding="UTF-8"?>

   <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing">

      <soapenv:Header>

         <wsse:Security soapenv:mustUnderstand="1" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">

            <wsse:UsernameToken wsu:Id="UsernameToken-6" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">

               <wsse:Username>1234</wsse:Username>

               <wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">htPassword</wsse:Password>

            </wsse:UsernameToken>

         </wsse:Security>

         <wsa:MessageID soapenv:mustUnderstand="0">uuid:07ed8290-95da-11e0-be39-d30c18650bf1</wsa:MessageID>

         <wsa:To soapenv:mustUnderstand="0">http://localhost:8091/LightSpeedXmlWeb/services/ReservationProviderPortType</wsa:To>

         <wsa:Action soapenv:mustUnderstand="0">http://htng.org/PWS/2008A/SingleGuestItinerary#FetchReservation</wsa:Action>

         <wsa:From xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing" soapenv:mustUnderstand="0">

            <wsa:Address>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</wsa:Address>

         </wsa:From>

      </soapenv:Header>

      <soapenv:Body>

         <FetchReservationRequest xmlns="http://htng.org/PWS/2008A/SingleGuestItinerary/Reservation/Types">

            <ReservationID>137056</ReservationID>

            <ResortId>5608</ResortId>

         </FetchReservationRequest>

      </soapenv:Body>

   </soapenv:Envelope>

 

 

Response:

 

HTTP/1.1 200 OK

Server: Apache-Coyote/1.1

X-Powered-By: Servlet 2.4; Tomcat-5.0.28/JBoss-4.0.1sp1 (build: CVSTag=JBoss_4_0_1_SP1 date=200502160314)

Set-Cookie: JSESSIONID=861148184CE4F64306DCF8B7EF30B215; Path=/

Content-Type: text/xml;charset=utf-8

Date: Mon, 13 Jun 2011 16:29:45 GMT

Connection: close

 

<?xml version="1.0" encoding="UTF-8"?>

   <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing">

      <soapenv:Header>

         <wsa:MessageID soapenv:mustUnderstand="0">uuid:59882a60-95da-11e0-be39-d30c18650bf1</wsa:MessageID>

         <wsa:To soapenv:mustUnderstand="0">http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</wsa:To>

         <wsa:Action soapenv:mustUnderstand="0">http://htng.org/PWS/2008A/SingleGuestItinerary#FetchReservationResponse</wsa:Action>

         <wsa:From xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing" soapenv:mustUnderstand="0">

            <wsa:Address>http://localhost:8091/LightSpeedXmlWeb/services/ReservationProviderPortType</wsa:Address>

         </wsa:From>

         <wsa:RelatesTo RelationshipType="wsa:Reply" soapenv:mustUnderstand="0">uuid:57b4f100-95da-11e0-be39-d30c18650bf1</wsa:RelatesTo>

      </soapenv:Header>

      <soapenv:Body>

         <FetchReservationResponse xmlns="http://htng.org/PWS/2008A/SingleGuestItinerary/Reservation/Types">

            <Result resultStatusFlag="SUCCESS"/>

            <ReservationData reservationStatus="CHECKED_IN">

               <ReservationID>137056</ReservationID>

               <ConfirmationNO>137056</ConfirmationNO>

               <ProfileInfo familiarName="Adams, Larry">

                  <ns1:FirstName xmlns:ns1="http://htng.org/PWS/2008A/SingleGuestItinerary/Common/Types"> Larry</ns1:FirstName>

                  <ns2:LastName xmlns:ns2="http://htng.org/PWS/2008A/SingleGuestItinerary/Common/Types">Adams</ns2:LastName>

               </ProfileInfo>

               <ArrivalDate>2010-11-13T07:00:00.000Z</ArrivalDate>

               <DepartureDate>2010-11-20T07:00:00.000Z</DepartureDate>

               <ShortRateCode>OWNFIX</ShortRateCode>

               <ShortRoomType>P2B</ShortRoomType>

               <RoomNumber>662</RoomNumber>

               <ResortId>5608</ResortId>

               <MarketSegment>OWN</MarketSegment>

               <SourceCode>SVO</SourceCode>

               <NoPostFlag>false</NoPostFlag>

               <UserDefinedValues>

                  <ns3:UserDefinedValue valueName="SPECSERV" xmlns:ns3="http://htng.org/PWS/2008A/SingleGuestItinerary/Common/Types">

                     <ns3:CharacterValue>DMND</ns3:CharacterValue>

                     <ns3:NumericValue>0.0</ns3:NumericValue>

                  </ns3:UserDefinedValue>

                  <ns4:UserDefinedValue valueName="SPECSERV" xmlns:ns4="http://htng.org/PWS/2008A/SingleGuestItinerary/Common/Types">

                     <ns4:CharacterValue>XX</ns4:CharacterValue>

                     <ns4:NumericValue>0.0</ns4:NumericValue>

                  </ns4:UserDefinedValue>

                  <ns5:UserDefinedValue valueName="SPECSERV" xmlns:ns5="http://htng.org/PWS/2008A/SingleGuestItinerary/Common/Types">

                     <ns5:CharacterValue>L8C</ns5:CharacterValue>

                     <ns5:NumericValue>0.0</ns5:NumericValue>

                  </ns5:UserDefinedValue>

                  <ns6:UserDefinedValue valueName="SPECSERV" xmlns:ns6="http://htng.org/PWS/2008A/SingleGuestItinerary/Common/Types">

                     <ns6:CharacterValue>SVR</ns6:CharacterValue>

                     <ns6:NumericValue>0.0</ns6:NumericValue>

                  </ns6:UserDefinedValue>

                  <ns7:UserDefinedValue valueName="VIPCODE" xmlns:ns7="http://htng.org/PWS/2008A/SingleGuestItinerary/Common/Types">

                     <ns7:CharacterValue>1</ns7:CharacterValue>

                     <ns7:NumericValue>0.0</ns7:NumericValue>

                  </ns7:UserDefinedValue>

                  <ns8:UserDefinedValue valueName="PTICK" xmlns:ns8="http://htng.org/PWS/2008A/SingleGuestItinerary/Common/Types">

                     <ns8:CharacterValue></ns8:CharacterValue>

                     <ns8:NumericValue>0.0</ns8:NumericValue>

                  </ns8:UserDefinedValue>

                  <ns9:UserDefinedValue valueName="EMAIL" xmlns:ns9="http://htng.org/PWS/2008A/SingleGuestItinerary/Common/Types">

                     <ns9:CharacterValue>myemailaddr@yahoo.com</ns9:CharacterValue>

                     <ns9:NumericValue>0.0</ns9:NumericValue>

                  </ns9:UserDefinedValue>

               </UserDefinedValues>

            </ReservationData>

         </FetchReservationResponse>

      </soapenv:Body>

   </soapenv:Envelope>

 

Supporting Document 3

3

 Request:

 

 

POST /LightSpeedXmlWeb/services/ReservationProviderPortType HTTP/1.0

Content-Type: text/xml; charset=utf-8

Accept: application/soap+xml, application/dime, multipart/related, text/*

User-Agent: Axis/1.4

Host: 127.0.0.1:8091

Cache-Control: no-cache

Pragma: no-cache

SOAPAction: "http://htng.org/PWS/2008A/SingleGuestItinerary#PostPayment"

Content-Length: 2618

 

<?xml version="1.0" encoding="UTF-8"?>

   <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing">

      <soapenv:Header>

         <wsse:Security soapenv:mustUnderstand="1" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">

            <wsse:UsernameToken wsu:Id="UsernameToken-10" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">

               <wsse:Username>5678</wsse:Username>

               <wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">htPassword</wsse:Password>

            </wsse:UsernameToken>

         </wsse:Security>

         <wsa:MessageID soapenv:mustUnderstand="0">uuid:074f9f70-95db-11e0-be39-d30c18650bf1</wsa:MessageID>

         <wsa:To soapenv:mustUnderstand="0">http://localhost:8091/LightSpeedXmlWeb/services/ReservationProviderPortType</wsa:To>

         <wsa:Action soapenv:mustUnderstand="0">http://htng.org/PWS/2008A/SingleGuestItinerary#PostPayment</wsa:Action>

         <wsa:From xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing" soapenv:mustUnderstand="0">

            <wsa:Address>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</wsa:Address>

         </wsa:From>

      </soapenv:Header>

      <soapenv:Body>

         <pmtpostingupdate xmlns="http://htng.org/PWS/2008A/SingleGuestItinerary/PaymentPosting/Types">

            <Number type="resno">236865</Number>

            <ClientId>HTNG POSTING</ClientId>

            <PostingGUID>12345</PostingGUID>

            <ZoomInKey/>

            <AccountDetail>

               <Account/>

               <Unit>1</Unit>

            </AccountDetail>

            <VoidFlag>false</VoidFlag>

            <PostPropertyId>5608</PostPropertyId>

            <RegisterId>0</RegisterId>

            <CashierEmpId>0</CashierEmpId>

            <ServerEmpId>12</ServerEmpId>

            <RevenueCenterId>46</RevenueCenterId>

            <CheckNumber>0</CheckNumber>

            <Covers>1</Covers>

            <MealPeriod>2</MealPeriod>

            <PaymentId>12345</PaymentId>

            <TipAmount>0</TipAmount>

            <PaymentAmount>496</PaymentAmount>

            <CheckAmount>0</CheckAmount>

            <ResortId>5608</ResortId>

            <Itemizers>

               <Itemizer class="tax" id="46" name="46">4960</Itemizer>

               <Itemizer class="tax" id="46" name="46">4960</Itemizer>

               <Itemizer class="tax" id="46" name="46">4960</Itemizer>

               <Itemizer class="tax" id="46" name="46">4960</Itemizer>

               <Itemizer class="tax" id="46" name="46">4960</Itemizer>

               <Itemizer class="tax" id="46" name="46">4960</Itemizer>

               <Itemizer class="tax" id="46" name="46">4960</Itemizer>

               <Itemizer class="tax" id="46" name="46">4960</Itemizer>

               <Itemizer class="tax" id="46" name="46">4960</Itemizer>

               <Itemizer class="tax" id="46" name="46">4960</Itemizer>

            </Itemizers>

         </pmtpostingupdate>

      </soapenv:Body>

   </soapenv:Envelope>

 

 

Response:

 

 

HTTP/1.1 200 OK

Server: Apache-Coyote/1.1

X-Powered-By: Servlet 2.4; Tomcat-5.0.28/JBoss-4.0.1sp1 (build: CVSTag=JBoss_4_0_1_SP1 date=200502160314)

Set-Cookie: JSESSIONID=D07921E21624AC7B1FEB04DC5F4BFE40; Path=/

Content-Type: text/xml;charset=utf-8

Date: Mon, 13 Jun 2011 16:34:40 GMT

Connection: close

 

<?xml version="1.0" encoding="UTF-8"?>

   <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing">

      <soapenv:Header>

         <wsa:MessageID soapenv:mustUnderstand="0">uuid:08db4880-95db-11e0-be39-d30c18650bf1</wsa:MessageID>

         <wsa:To soapenv:mustUnderstand="0">http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</wsa:To>

         <wsa:Action soapenv:mustUnderstand="0">http://htng.org/PWS/2008A/SingleGuestItinerary#PostPaymentResponse</wsa:Action>

         <wsa:From xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing" soapenv:mustUnderstand="0">

            <wsa:Address>http://localhost:8091/LightSpeedXmlWeb/services/ReservationProviderPortType</wsa:Address>

         </wsa:From>

         <wsa:RelatesTo RelationshipType="wsa:Reply" soapenv:mustUnderstand="0">uuid:074f9f70-95db-11e0-be39-d30c18650bf1</wsa:RelatesTo>

      </soapenv:Header>

      <soapenv:Body>

         <pmtpostingresults xmlns="http://htng.org/PWS/2008A/SingleGuestItinerary/PaymentPosting/Types">

            <Status code="SUCCESS" resultStatusFlag="SUCCESS">

               <ns1:Text xmlns:ns1="http://htng.org/PWS/2008A/SingleGuestItinerary/Common/Types">

                  <ns1:TextElement>SUCCESS</ns1:TextElement>

               </ns1:Text>

            </Status>

            <PostingGUID>12345</PostingGUID>

            <PaymentAmount>4</PaymentAmount>

            <Unit>1</Unit>

            <Account></Account>

            <Occupant></Occupant>

         </pmtpostingresults>

      </soapenv:Body>

   </soapenv:Envelope>

 

Supporting Document 4

4

 <soapenv:Envelope

  xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"

  xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing"

  xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

  <soapenv:Header>

    <wsse:Security soapenv:mustUnderstand="1" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">

      <wsse:UsernameToken wsu:Id="UsernameToken-13" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">

        <wsse:Username>1200</wsse:Username>

        <wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">friday</wsse:Password>

      </wsse:UsernameToken>

    </wsse:Security>

    <wsa:MessageID soapenv:mustUnderstand="0">uuid:c14dd750-95dd-11e0-be39-d30c18650bf1</wsa:MessageID>

    <wsa:To soapenv:mustUnderstand="0">http://10.20.249.158:8090/lightspeedtest/services/RoomStayEventConsumer</wsa:To>

    <wsa:Action soapenv:mustUnderstand="0">http://htng.org/2009B/CheckedIn</wsa:Action>

    <From soapenv:mustUnderstand="0" xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing">

      <Address>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</Address>

    </From>

  </soapenv:Header>

  <soapenv:Body>

    <HTNG_CheckInNotification xmlns="http://htng.org/2009B">

      <AffectedGuests>

        <ns1:AffectedGuest GuestID="123456" ReservationID="theResId" xmlns:ns1="http://htng.org/Common"/>

      </AffectedGuests>

      <RoomSharingInfo>

        <ns2:Room RoomID="1234" xmlns:ns2="http://htng.org/Common">

          <ns2:RoomType InvBlockCode="" IsRoom="true" RoomTypeCode="AccomCode">

            <ns2:RoomDescription Formatted="false" TextFormat="PlainText">AccomDesc</ns2:RoomDescription>

          </ns2:RoomType>

        </ns2:Room>

        <ns3:PrimaryShareDetails ArrivalTime="17:54:08.422Z"

          DepartureTime="17:54:08.422Z" xmlns:ns3="http://htng.org/Common">

          <ns3:Reservation CreateDateTime="2011-06-13T16:54:08.422Z"

            CreatorID="creatorID" ResStatus="resStatus">

            <ns3:HotelReservationIDs>

              <ns3:HotelReservationID

                ResID_Date="2011-06-13T16:54:08.422Z"

                ResID_Source="source"

                ResID_SourceContext="sourceContext"

                ResID_Type="resID_Type" ResID_Value="resID_Value"/>

            </ns3:HotelReservationIDs>

            <ns3:RoomTypes>

              <ns3:RoomType InvBlockCode="invBlockCode" IsRoom="true">

                <ns3:RoomDescription Formatted="false">_value</ns3:RoomDescription>

              </ns3:RoomType>

            </ns3:RoomTypes>

            <ns3:RatePlans>

              <ns3:RatePlan RatePlanCode="ratePlanCode" RatePlanName="ratePlanName"/>

            </ns3:RatePlans>

            <ns3:GuestCounts>

              <ns3:GuestCount AgeQualifyingCode="ageQualifyingCode" Count="1"/>

            </ns3:GuestCounts>

            <ns3:TimeSpan End="2011-06-13T16:54:08.422Z" Start="2011-06-13T16:54:08.422Z"/>

          </ns3:Reservation>

          <ns3:Guest GroupEventCode="groupEventCode">

            <ns3:Profiles>

              <ns3:ProfileInfo>

                <ns3:Profile>

                  <ns3:Customer CurrencyCode="currencyCode">

                    <ns3:PersonName>

                      <ns3:Surname>surname</ns3:Surname>

                    </ns3:PersonName>

                  </ns3:Customer>

                  <ns3:Preferences>

                    <ns3:Preference>

                      <ns3:Preference Description="Chg For Cot"

                        UnitOfMeasure="CODE" Value="COT"/>

                      <ns3:Preference Description="Charge"

                        UnitOfMeasure="USD" Value="30.00"/>

                    </ns3:Preference>

                  </ns3:Preferences>

                </ns3:Profile>

              </ns3:ProfileInfo>

            </ns3:Profiles>

          </ns3:Guest>

        </ns3:PrimaryShareDetails>

      </RoomSharingInfo>

    </HTNG_CheckInNotification>

  </soapenv:Body>

</soapenv:Envelope>

 

Supporting Document 5

5

 <soapenv:Envelope

  xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"

  xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing"

  xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

  <soapenv:Header>

    <wsse:Security soapenv:mustUnderstand="1" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">

      <wsse:UsernameToken wsu:Id="UsernameToken-14" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">

        <wsse:Username>1200</wsse:Username>

        <wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">friday</wsse:Password>

      </wsse:UsernameToken>

    </wsse:Security>

    <wsa:MessageID soapenv:mustUnderstand="0">uuid:fb396ab0-95dd-11e0-be39-d30c18650bf1</wsa:MessageID>

    <wsa:To soapenv:mustUnderstand="0">http://10.20.249.158:8090/lightspeedtest/services/RoomStayEventConsumer</wsa:To>

    <wsa:Action soapenv:mustUnderstand="0">http://htng.org/2009B/CheckedOut</wsa:Action>

    <From soapenv:mustUnderstand="0" xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing">

      <Address>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</Address>

    </From>

  </soapenv:Header>

  <soapenv:Body>

    <HTNG_CheckOutNotification xmlns="http://htng.org/2009B">

      <AffectedGuests>

        <ns1:AffectedGuest GuestID="123456" ReservationID="theResId" xmlns:ns1="http://htng.org/Common"/>

      </AffectedGuests>

      <RoomSharingInfo>

        <ns2:Room RoomID="1234" xmlns:ns2="http://htng.org/Common">

          <ns2:RoomType InvBlockCode="" IsRoom="true" RoomTypeCode="AccomCode">

            <ns2:RoomDescription Formatted="false" TextFormat="PlainText">AccomDesc</ns2:RoomDescription>

          </ns2:RoomType>

        </ns2:Room>

        <ns3:PrimaryShareDetails ArrivalTime="17:55:45.611Z"

          DepartureTime="17:55:45.611Z" xmlns:ns3="http://htng.org/Common">

          <ns3:Reservation CreateDateTime="2011-06-13T16:55:45.611Z"

            CreatorID="creatorID" ResStatus="resStatus">

            <ns3:HotelReservationIDs>

              <ns3:HotelReservationID

                ResID_Date="2011-06-13T16:55:45.611Z"

                ResID_Source="source"

                ResID_SourceContext="sourceContext"

                ResID_Type="resID_Type" ResID_Value="resID_Value"/>

            </ns3:HotelReservationIDs>

            <ns3:RoomTypes>

              <ns3:RoomType InvBlockCode="invBlockCode" IsRoom="true">

                <ns3:RoomDescription Formatted="false">_value</ns3:RoomDescription>

              </ns3:RoomType>

            </ns3:RoomTypes>

            <ns3:RatePlans>

              <ns3:RatePlan RatePlanCode="ratePlanCode" RatePlanName="ratePlanName"/>

            </ns3:RatePlans>

            <ns3:GuestCounts>

              <ns3:GuestCount AgeQualifyingCode="ageQualifyingCode" Count="1"/>

            </ns3:GuestCounts>

            <ns3:TimeSpan End="2011-06-13T16:55:45.611Z" Start="2011-06-13T16:55:45.611Z"/>

          </ns3:Reservation>

          <ns3:Guest GroupEventCode="groupEventCode">

            <ns3:Profiles>

              <ns3:ProfileInfo>

                <ns3:Profile>

                  <ns3:Customer CurrencyCode="currencyCode">

                    <ns3:PersonName>

                      <ns3:Surname>surname</ns3:Surname>

                    </ns3:PersonName>

                  </ns3:Customer>

                  <ns3:Preferences>

                    <ns3:Preference>

                      <ns3:Preference Description="Chg For Cot"

                        UnitOfMeasure="CODE" Value="COT"/>

                      <ns3:Preference Description="Charge"

                        UnitOfMeasure="USD" Value="30.00"/>

                    </ns3:Preference>

                  </ns3:Preferences>

                </ns3:Profile>

              </ns3:ProfileInfo>

            </ns3:Profiles>

          </ns3:Guest>

        </ns3:PrimaryShareDetails>

      </RoomSharingInfo>

    </HTNG_CheckOutNotification>

  </soapenv:Body>

</soapenv:Envelope>

 

Supporting Document 6

6

 <soapenv:Envelope

  xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"

  xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing"

  xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

  <soapenv:Header>

    <wsse:Security soapenv:mustUnderstand="1" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">

      <wsse:UsernameToken wsu:Id="UsernameToken-16" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">

        <wsse:Username>1200</wsse:Username>

        <wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">friday</wsse:Password>

      </wsse:UsernameToken>

    </wsse:Security>

    <wsa:MessageID soapenv:mustUnderstand="0">uuid:14873b00-95de-11e0-be39-d30c18650bf1</wsa:MessageID>

    <wsa:To soapenv:mustUnderstand="0">http://10.20.249.158:8090/lightspeedtest/services/RoomStayEventConsumer</wsa:To>

    <wsa:Action soapenv:mustUnderstand="0">http://htng.org/2009B/RoomMoved</wsa:Action>

    <From soapenv:mustUnderstand="0" xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing">

      <Address>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</Address>

    </From>

  </soapenv:Header>

  <soapenv:Body>

    <HTNG_RoomMoveNotification xmlns="http://htng.org/2009B">

      <AffectedGuests>

        <ns1:AffectedGuest GuestID="123456" ReservationID="theResId" xmlns:ns1="http://htng.org/Common"/>

      </AffectedGuests>

      <SourceRoomInformation>

        <RoomSharingInfo>

          <ns2:Room RoomID="1234" xmlns:ns2="http://htng.org/Common">

            <ns2:RoomType InvBlockCode="" IsRoom="true" RoomTypeCode="AccomCode">

              <ns2:RoomDescription Formatted="false" TextFormat="PlainText">AccomDesc</ns2:RoomDescription>

            </ns2:RoomType>

          </ns2:Room>

          <ns3:PrimaryShareDetails ArrivalTime="17:56:28.049Z"

            DepartureTime="17:56:28.049Z" xmlns:ns3="http://htng.org/Common">

            <ns3:Reservation CreateDateTime="2011-06-13T16:56:28.049Z"

              CreatorID="creatorID" ResStatus="resStatus">

              <ns3:HotelReservationIDs>

                <ns3:HotelReservationID

                  ResID_Date="2011-06-13T16:56:28.049Z"

                  ResID_Source="source"

                  ResID_SourceContext="sourceContext"

                  ResID_Type="resID_Type" ResID_Value="resID_Value"/>

              </ns3:HotelReservationIDs>

              <ns3:RoomTypes>

                <ns3:RoomType InvBlockCode="invBlockCode" IsRoom="true">

                  <ns3:RoomDescription Formatted="false">_value</ns3:RoomDescription>

                </ns3:RoomType>

              </ns3:RoomTypes>

              <ns3:RatePlans>

                <ns3:RatePlan RatePlanCode="ratePlanCode" RatePlanName="ratePlanName"/>

              </ns3:RatePlans>

              <ns3:GuestCounts>

                <ns3:GuestCount AgeQualifyingCode="ageQualifyingCode" Count="1"/>

              </ns3:GuestCounts>

              <ns3:TimeSpan End="2011-06-13T16:56:28.049Z" Start="2011-06-13T16:56:28.049Z"/>

            </ns3:Reservation>

            <ns3:Guest GroupEventCode="groupEventCode">

              <ns3:Profiles>

                <ns3:ProfileInfo>

                  <ns3:Profile>

                    <ns3:Customer CurrencyCode="currencyCode">

                      <ns3:PersonName>

                        <ns3:Surname>surname</ns3:Surname>

                      </ns3:PersonName>

                    </ns3:Customer>

                  </ns3:Profile>

                </ns3:ProfileInfo>

              </ns3:Profiles>

            </ns3:Guest>

          </ns3:PrimaryShareDetails>

        </RoomSharingInfo>

      </SourceRoomInformation>

      <DestinationRoomInformation>

        <RoomSharingInfo>

          <ns4:Room RoomID="1234" xmlns:ns4="http://htng.org/Common">

            <ns4:RoomType InvBlockCode="" IsRoom="true" RoomTypeCode="AccomCode">

              <ns4:RoomDescription Formatted="false" TextFormat="PlainText">AccomDesc</ns4:RoomDescription>

            </ns4:RoomType>

          </ns4:Room>

          <ns5:PrimaryShareDetails ArrivalTime="17:56:28.049Z"

            DepartureTime="17:56:28.049Z" xmlns:ns5="http://htng.org/Common">

            <ns5:Reservation CreateDateTime="2011-06-13T16:56:28.049Z"

              CreatorID="creatorID" ResStatus="resStatus">

              <ns5:HotelReservationIDs>

                <ns5:HotelReservationID

                  ResID_Date="2011-06-13T16:56:28.049Z"

                  ResID_Source="source"

                  ResID_SourceContext="sourceContext"

                  ResID_Type="resID_Type" ResID_Value="resID_Value"/>

              </ns5:HotelReservationIDs>

              <ns5:RoomTypes>

                <ns5:RoomType InvBlockCode="invBlockCode" IsRoom="true">

                  <ns5:RoomDescription Formatted="false">_value</ns5:RoomDescription>

                </ns5:RoomType>

              </ns5:RoomTypes>

              <ns5:RatePlans>

                <ns5:RatePlan RatePlanCode="ratePlanCode" RatePlanName="ratePlanName"/>

              </ns5:RatePlans>

              <ns5:GuestCounts>

                <ns5:GuestCount AgeQualifyingCode="ageQualifyingCode" Count="1"/>

              </ns5:GuestCounts>

              <ns5:TimeSpan End="2011-06-13T16:56:28.049Z" Start="2011-06-13T16:56:28.049Z"/>

            </ns5:Reservation>

            <ns5:Guest GroupEventCode="groupEventCode">

              <ns5:Profiles>

                <ns5:ProfileInfo>

                  <ns5:Profile>

                    <ns5:Customer CurrencyCode="currencyCode">

                      <ns5:PersonName>

                        <ns5:Surname>surname</ns5:Surname>

                      </ns5:PersonName>

                    </ns5:Customer>

                  </ns5:Profile>

                </ns5:ProfileInfo>

              </ns5:Profiles>

            </ns5:Guest>

          </ns5:PrimaryShareDetails>

        </RoomSharingInfo>

      </DestinationRoomInformation>

    </HTNG_RoomMoveNotification>

  </soapenv:Body>

</soapenv:Envelope>

 

Supporting Document 7

7

 <soapenv:Envelope

  xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"

  xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing"

  xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

  <soapenv:Header>

    <wsse:Security soapenv:mustUnderstand="1" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">

      <wsse:UsernameToken wsu:Id="UsernameToken-18" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">

        <wsse:Username>1200</wsse:Username>

        <wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">friday</wsse:Password>

      </wsse:UsernameToken>

    </wsse:Security>

    <wsa:MessageID soapenv:mustUnderstand="0">uuid:3858fff0-95de-11e0-be39-d30c18650bf1</wsa:MessageID>

    <wsa:To soapenv:mustUnderstand="0">http://10.20.249.158:8090/lightspeedtest/services/RoomStayEventConsumer</wsa:To>

    <wsa:Action soapenv:mustUnderstand="0">http://htng.org/2009B/StayUpdated</wsa:Action>

    <From soapenv:mustUnderstand="0" xmlns="http://schemas.xmlsoap.org/ws/2004/08/addressing">

      <Address>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</Address>

    </From>

  </soapenv:Header>

  <soapenv:Body>

    <HTNG_StayUpdateNotification xmlns="http://htng.org/2009B">

      <RoomSharingInfo>

        <ns1:Room RoomID="1234" xmlns:ns1="http://htng.org/Common">

          <ns1:RoomType InvBlockCode="" IsRoom="true" RoomTypeCode="AccomCode">

            <ns1:RoomDescription Formatted="false" TextFormat="PlainText">AccomDesc</ns1:RoomDescription>

          </ns1:RoomType>

        </ns1:Room>

        <ns2:PrimaryShareDetails ArrivalTime="17:57:28.160Z"

          DepartureTime="17:57:28.160Z" xmlns:ns2="http://htng.org/Common">

          <ns2:Reservation CreateDateTime="2011-06-13T16:57:28.160Z"

            CreatorID="creatorID" ResStatus="resStatus">

            <ns2:HotelReservationIDs>

              <ns2:HotelReservationID

                ResID_Date="2011-06-13T16:57:28.160Z"

                ResID_Source="source"

                ResID_SourceContext="sourceContext"

                ResID_Type="resID_Type" ResID_Value="resID_Value"/>

            </ns2:HotelReservationIDs>

            <ns2:RoomTypes>

              <ns2:RoomType InvBlockCode="invBlockCode" IsRoom="true">

                <ns2:RoomDescription Formatted="false">_value</ns2:RoomDescription>

              </ns2:RoomType>

            </ns2:RoomTypes>

            <ns2:RatePlans>

              <ns2:RatePlan RatePlanCode="ratePlanCode" RatePlanName="ratePlanName"/>

            </ns2:RatePlans>

            <ns2:GuestCounts>

              <ns2:GuestCount AgeQualifyingCode="ageQualifyingCode" Count="1"/>

            </ns2:GuestCounts>

            <ns2:TimeSpan End="2011-06-13T16:57:28.160Z" Start="2011-06-13T16:57:28.160Z"/>

          </ns2:Reservation>

          <ns2:Guest GroupEventCode="groupEventCode">

            <ns2:Profiles>

              <ns2:ProfileInfo>

                <ns2:Profile>

                  <ns2:Customer CurrencyCode="currencyCode">

                    <ns2:PersonName>

                      <ns2:Surname>surname</ns2:Surname>

                    </ns2:PersonName>

                  </ns2:Customer>

                </ns2:Profile>

              </ns2:ProfileInfo>

            </ns2:Profiles>

          </ns2:Guest>

        </ns2:PrimaryShareDetails>

      </RoomSharingInfo>

    </HTNG_StayUpdateNotification>

  </soapenv:Body>

</soapenv:Envelope>

 

Supporting Document 8

8

 LightSpeed’s implementation of WS-SECURITY uses the credentials passed in each SOAP packet to authorize and authenticate the user. It authenticates the user using the username and password and if this passes, the user is then authorized using internal mechanisms to validate the user has the specific role to execute the web service. LightSpeed follows the WS-SECURITY framework at http://ws.apache.org/wss4j/package.html)

 

Supporting Document 9

8

 LightSpeed needs the WS-ADDRESSING headers to be included in each message for future implementations of LightSpeed. The addressing headers are not executed at this time.


Revision History

Issue 1.0 November 24, 2008, First Release
Issue 2.0 April 10, 2009, First Release (Updated Open Data Exchange, added Back Office)
Issue 3.0 September 24, 2009, First Release (added Guest and Room Status Messaging)
Issue 4.0 April 23, 2010, First Release (added Kiosk Integration)


Copyright © 2009 HTNG, All Rights Reserved