Air Status EDI
From UG
(Difference between revisions)
(→Technical part) |
(→Technical Requirements and Design) |
||
| Line 19: | Line 19: | ||
== Technical Requirements and Design == | == Technical Requirements and Design == | ||
| + | |||
| + | === Intro === | ||
| + | CT2 and Descartes system (GLN) will exchange XML messages. | ||
| + | |||
| + | In a nutshell: | ||
| + | * CT2 sends MAWB (same as FWB) to Descartes(GLN) network/server | ||
| + | * GLN forwards to Airline nework | ||
| + | * when update becomes available info is passed back to CT2 through Descartes | ||
| + | |||
| + | === Outgoing message === | ||
| + | |||
| + | ==== Example ==== | ||
| + | <pre> | ||
| + | <?xml version="1.0" encoding="UTF-8" standalone="yes"?> | ||
| + | <ns3:Envelope xmlns:ns2="http://www.myvan.descartes.com/ebi/2004/r1" [^] xmlns:ns3="http://www.w3.org/2003/05/soap-envelope" [^] xmlns:ns4="http://schemas.xmlsoap.org/ws/2004/03/addressing"> [^] | ||
| + | <ns3:Header> | ||
| + | <ns4:From> | ||
| + | <ns4:Address>urn:duns:657589457</ns4:Address> | ||
| + | </ns4:From> | ||
| + | <!—THIS NEEDS TO BE THE AIRLINE ID.--> | ||
| + | <ns4:To>urn:duns:657589457</ns4:To> | ||
| + | <ns4:Action>urn:myvan:FWB</ns4:Action> | ||
| + | <ns2:Sequence> | ||
| + | <ns2:MessageNumber>351-5648-6541</ns2:MessageNumber> | ||
| + | </ns2:Sequence> | ||
| + | </ns3:Header> | ||
| + | <ns3:Body> | ||
| + | <JaguarFile> | ||
| + | <Shipment> | ||
| + | <FWB> | ||
| + | 351-5648-6541 | ||
| + | </FWB> | ||
| + | </Shipment> | ||
| + | </JaguarFile> | ||
| + | </ns3:Body> | ||
| + | </ns3:Envelope> | ||
| + | </pre> | ||
| + | |||
| + | === Incoming message === | ||
== History == | == History == | ||
Revision as of 18:16, 27 October 2010
Contents |
Parent mantis
0002422: [Air Status EDI] ............. <proj parent>
Business Requirements
Intro
Project: Automated air status update service (EDI with Descartes)
This will allow airfreight shipments booked directly by Jaguar with the airlines, to be fed automatic status updates (departure and arrival dates), removing our need to manually check and then update the status of Airfreigt shipments.
One CT one direct flight Use Case
One CT multistop flight Use Case
Split Use Case
Technical Requirements and Design
Intro
CT2 and Descartes system (GLN) will exchange XML messages.
In a nutshell:
- CT2 sends MAWB (same as FWB) to Descartes(GLN) network/server
- GLN forwards to Airline nework
- when update becomes available info is passed back to CT2 through Descartes
Outgoing message
Example
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<ns3:Envelope xmlns:ns2="http://www.myvan.descartes.com/ebi/2004/r1" [^] xmlns:ns3="http://www.w3.org/2003/05/soap-envelope" [^] xmlns:ns4="http://schemas.xmlsoap.org/ws/2004/03/addressing"> [^]
<ns3:Header>
<ns4:From>
<ns4:Address>urn:duns:657589457</ns4:Address>
</ns4:From>
<!—THIS NEEDS TO BE THE AIRLINE ID.-->
<ns4:To>urn:duns:657589457</ns4:To>
<ns4:Action>urn:myvan:FWB</ns4:Action>
<ns2:Sequence>
<ns2:MessageNumber>351-5648-6541</ns2:MessageNumber>
</ns2:Sequence>
</ns3:Header>
<ns3:Body>
<JaguarFile>
<Shipment>
<FWB>
351-5648-6541
</FWB>
</Shipment>
</JaguarFile>
</ns3:Body>
</ns3:Envelope>
