Transport Interface
Páginas: 31 (7522 palabras)
Publicado: 17 de diciembre de 2012
| |
| |
| ||TPS-GTS Interface Specification |
| |
| |
|[pic]|
Table of Contents
1 Document Overview 4
1.1 Purpose of Document 6
1.2 Document Scope 6
2 Methodology 6
2.1 Interface Frequency 7
2.2 Validations 7
2.3 Services 8
3 Request Statuses 84 Grouped Requests 9
4.1 Points to be taken care during grouping 10
4.2 Handling chain request 11
4.3 Need Status 12
5 Message Types and Definitions 13
5.1 Length of each field used in message definition 13
5.2 Add (TPS->GTS) 23
5.3 Update (TPS->GTS) 24
5.4 Confirmation (GTS->TPS) 29
5.5 Cancellation Message 31
5.6 Get Status Response 32
5.7 CancelResponse 34
5.8 Error Message (GTS->TPS) 36
6 Scenarios and corresponding error messages 36
7 Error message types 46
8 Exception Handling and Reconciliation 46
9 Security 48
10 Data Models used in GTS 49
10.1 GTS_Transport_Need 50
10.2 GTS_Passenger 53
10.3 GTS_Transport_Group_Details 55
10.4 EMS_EXTERNAL_FILE_ERROR 57
10.5EMS_EXTERNAL_FILE_ERROR_DETAILS 58
11 XML format 59
11.1 Add Request 59
11.2 Update Request 59
11.3 Response for add/update 59
11.4 Request for Cancellation 59
11.5 Response for cancellation 59
11.6 Request for Status based on id 60
11.7 Response for Status 60
11.8 Request for status of last updated requests 60
12 Connection details/naming of services 60
13 Overview ofEMS environments 60
14 Contact Details 61
Document Overview
Version History
|Date |Ver. |Updated by |Notes |
|17 Sept. 2008 |v0 1 |Jason |Draft v0 1 released for review |
|22 Sept |v02 |Jason |Added details on methodology |
| | | |Separated Add and Update messages |
| | | |Added roles & responsibilities section |
| | ||Added validations section |
| | | |Added services section |
|23 Sept |v0 3 |Jason |Updated per Dave’s feedback |
|30 Oct |V0 4 |Jason |Addedhighlighted sections |
|28 Nov |V0 5 |Jason |Made small changes to the schema spec – i.e. no mobile numbers on |
| | | |the update message. |
|14 Jan 09 |V1 0 |Jason |Removed round trip fields...
| |
| ||TPS-GTS Interface Specification |
| |
| |
|[pic]|
Table of Contents
1 Document Overview 4
1.1 Purpose of Document 6
1.2 Document Scope 6
2 Methodology 6
2.1 Interface Frequency 7
2.2 Validations 7
2.3 Services 8
3 Request Statuses 84 Grouped Requests 9
4.1 Points to be taken care during grouping 10
4.2 Handling chain request 11
4.3 Need Status 12
5 Message Types and Definitions 13
5.1 Length of each field used in message definition 13
5.2 Add (TPS->GTS) 23
5.3 Update (TPS->GTS) 24
5.4 Confirmation (GTS->TPS) 29
5.5 Cancellation Message 31
5.6 Get Status Response 32
5.7 CancelResponse 34
5.8 Error Message (GTS->TPS) 36
6 Scenarios and corresponding error messages 36
7 Error message types 46
8 Exception Handling and Reconciliation 46
9 Security 48
10 Data Models used in GTS 49
10.1 GTS_Transport_Need 50
10.2 GTS_Passenger 53
10.3 GTS_Transport_Group_Details 55
10.4 EMS_EXTERNAL_FILE_ERROR 57
10.5EMS_EXTERNAL_FILE_ERROR_DETAILS 58
11 XML format 59
11.1 Add Request 59
11.2 Update Request 59
11.3 Response for add/update 59
11.4 Request for Cancellation 59
11.5 Response for cancellation 59
11.6 Request for Status based on id 60
11.7 Response for Status 60
11.8 Request for status of last updated requests 60
12 Connection details/naming of services 60
13 Overview ofEMS environments 60
14 Contact Details 61
Document Overview
Version History
|Date |Ver. |Updated by |Notes |
|17 Sept. 2008 |v0 1 |Jason |Draft v0 1 released for review |
|22 Sept |v02 |Jason |Added details on methodology |
| | | |Separated Add and Update messages |
| | | |Added roles & responsibilities section |
| | ||Added validations section |
| | | |Added services section |
|23 Sept |v0 3 |Jason |Updated per Dave’s feedback |
|30 Oct |V0 4 |Jason |Addedhighlighted sections |
|28 Nov |V0 5 |Jason |Made small changes to the schema spec – i.e. no mobile numbers on |
| | | |the update message. |
|14 Jan 09 |V1 0 |Jason |Removed round trip fields...
Leer documento completo
Regístrate para leer el documento completo.