ONLY ANSWER IF YOU\'RE WILLING TO ELABORATE! In your answer include \"WHAT PROGR
ID: 3799308 • Letter: O
Question
ONLY ANSWER IF YOU'RE WILLING TO ELABORATE! In your answer include "WHAT PROGRAMS" were used and "HOW" you did it. I will need to learn this and I will need to make edit and must know which application were used. Briefly explain your answer so I may understand. I will complain and I will cancel my membership if only an answer is provided. Thanks! **IMPORTANT: Provide a 2 part answer so that I can TELL THE DIFFERENCE! I AM NEW TO THIS AND WANT TO LEARN.
Part1A: Define a schema for a flight availability request application that requests flight availability for a city pair on a specific date for a specific number and type of passengers. Also include: time or time window, connecting cities, client preferences, e.g., airlines, flight types, etc. the request can be narrowed to request availability for a specific airline, specific flight, or specific booking class on a specific flight. LET ME KNOW WHAT YOU USED TO DO THIS? EG. Notepad++ AND HOW YOU DID THIS?
Part1B: Write a simple SOAP program that returns information about commercial flights from the XML Schema of Exercise 3.4 (practical part of Problem Set 1). You are expected to use an Integrated Development Environment (IDE) to code, debug, compile, and test your programs for both the client and the server side of the application. The application can be tested on a single host, or two remote hosts on the Internet. You submission should include the following components. 1) Source code of the application; 2) Executables and instructions how to run the application; 3) A brief report that discusses your design, your implementation (e.g., platform of development, programming language, etc), and test cases. LET ME KNOW LANGUAGE USED IF APPLICABLE AND HOW YOU DID THIS.
Explanation / Answer
The Low Fare Search Request message requests priced itinerary options for flights between specific city pairs on specific dates for specific numbers and types of passengers. Optional request information can include: - Time / Time Window - Connecting cities. - Client Preferences (airlines, cabin, flight types etc.) The Low Fare Search request contains similar information to a Low Fare Search entry on an airline CRS or GDS. Point of sale object. A collection of information that specifies how the message processing should occur or how the data should be returned. Origin and Destination location, and time information for the Air Low Fare Search request. ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... The Low Fare Search Response message contains a number of 'Priced Itinerary' options. Each includes: - A set of available flights matching the client's request. - Pricing information including taxes and full fare breakdown for each passenger type - Ticketing information - Fare Basis Codes and the information necessary to make a rules entry. This message contains similar information to a standard airline CRS or GDS Low Fare Search Response message. Success Standard way to indicate successful processing of an OTA message. Returning an empty element of this type indicates success. Standard way to indicate successful processing of an OTA message, but one in which warnings are generated. Successfull Low Fare priced itineraries in response to a Low Fare Search request. A collection of errors that occurred during the processing of a message. The OTA_PayloadStdAttributes defines the standard attributes that appear on the root element for all OTA payloads.Related Questions
Navigate
Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.