1 soap based web booking cio peter havskov christensen, m.sc., b. econ., mcsa...
TRANSCRIPT
June 2007
SOAP based www booking
1
SOAP basedweb booking
CIO Peter Havskov Christensen, M.Sc., B. Econ., MCSA
June 2007
SOAP based www booking
Why SOAP / Web Services
• A platform for new feature rich web booking.– Standard Unicorn were preventing some much wanted
features.
• Allow tour operators (agents) to do electronic packing of ferry tickets, accommodation and other services.– Part of our contract with Danish Government.
Development of SOAP services partly financed by EU through Destination Bornholm.
June 2007
SOAP based www booking
SOAP: an electronic envelope
XML DOCUMENT<booking><nr>23456789></nr><leg><from>R</from><to>Y</to>………
XML DOCUMENT<booking><nr>23456789></nr><leg><from>R</from><to>Y</to>………
TICKETTICKET
XML-document
Traditional scenario
SOAP-envelope Internet (https://)
SALES CHANNEL:AGENTCODE:
AGENTPASSWORD:
June 2007
SOAP based www booking
Simplified SOAP overview
CarResDB
cluster
CarResterminalservers
CarResSOAP
servers
www.bornholmstrafikken.dk
SOAP clientand
WEB server
Customers with WEB clients (IE, Mozilla etc)
HTML
XML
June 2007
SOAP based www booking
Key element: The XML document pairs
• Main Request and response pairs:– Several lists of possible values– CustomerInfo (only needed for customer login)– Timetable– PriceTimetable– Book– ModifyBook– Cancel– CreatePayment
June 2007
SOAP based www booking
June 2007
SOAP based www booking
What we use SOAP for
• New web booking for frequent travelers (customers with customer code in CarRes):– BornholmerBizz (RFID) for cars– BornholmerCard (RFID + biometric fingerprint) for
walking passengers
• New web booking for standard customers (customers without customer code in CarRes)
• Auto updating availability on www• Print of BornholmerCard
June 2007
SOAP based www booking
Why 2 different web bookings
• 2 customer groups– Different level of experience– Different needs– Eye opener from User group 2006
• One group knows harbors, routes, general terms etc. but needs history and future booking overview. This group should not have to choose a pay option.
• Second group does not necessarily know harbors, routes etc and need pay options
June 2007
SOAP based www booking
9
Old booking New standard booking
• Step 1– Products– Single / return– Routes– Date(s)– Time– Passenger type– Vehicle type (if any)
• Step 2– Outbound departure
• Step 3:– Return departure
• Step 4– Lead passenger + names of all
travellers• Step 5:
– Print ticket or pay• Step 6:
– Print ticket after pay
• Step 1:– In car / Walking / Bicycle / MC
• Step 2:– Single / return– Date(s)– Number of passengers
• Step 3:– Routes (graphic)
• Step 4:– Vehicle and/or passenger type
• Step 5:– Departure(s) and product (airline style)
• Step 6:– Lead passenger (+names if needed)
• Step 7:– Payment method
• Step 8:– Email, print and vCal
June 2007
SOAP based www booking
June 2007
SOAP based www booking
June 2007
SOAP based www booking
June 2007
SOAP based www booking
June 2007
SOAP based www booking
June 2007
SOAP based www booking
June 2007
SOAP based www booking
June 2007
SOAP based www booking
June 2007
SOAP based www booking
June 2007
SOAP based www booking
June 2007
SOAP based www booking
June 2007
SOAP based www booking
June 2007
SOAP based www booking
June 2007
SOAP based www booking
New Verisign Extended Validation
June 2007
SOAP based www booking
Summary of standard booking
• 8 simple steps• Product choosen “airline style”• National phone directory integration• Open source calender standard: vCal / iCal (RFC 2445):
– Works with Outlook and many open source calenders– Windows mobile and PDA sync of calender
• PDF– Ticket(s) and receipt on one page incl travel og check in guidance– Contact information (both ways)
• Green bar– Customer trust (nothing wrong with traditional SSL but easier
verification)
June 2007
SOAP based www booking
Frequent travelers
• Login with customer code and password• Needs booking overview (has to pay for no show as part of
agreement) without the need of customers remembering booking numbers and security codes. Booking numbers are not used for check in and now not needed for modify and cancel.
• Designed to be fast for returning users (few steps)• No payment since payment is handled by check in
automats• Possibility to update address and contact information.
June 2007
SOAP based www booking
June 2007
SOAP based www booking
June 2007
SOAP based www booking
June 2007
SOAP based www booking
June 2007
SOAP based www booking
Future
• Translation to English, German and Swedish• Minor adjustments / improvements as get experience• Full self service for frequent travelers (requires additional
parameters to SOAP requests)• Freight booking inspired by Frequent travelers Log in. View and
modification of details for future departures (requires additional parameters to SOAP requests and/or new requests)
• New version of departure control room that uses CustomerInfo, BookRecall and BookingSearch request and lets one person handle more than 12 simultaneous automats.
• Future automat modify might use SOAP.
June 2007
SOAP based www booking
Status
• At CarRes User Group 2006 we could not agree on ”requirements for a good web dialogue”.
• At CarRes User Group 2007 we have building blocks (SOAP) that enables each of us to create feature rich web bookings according to our own opinion on ”requirements for a good web dialogue”.
• With SOAP with also have great possibilities to create Ticket Vending Machines or very simple POS applications for go show situations.