SIG User Manual
m (→Demo System) |
m (→WSDL & XSD. Demo, Test, Prod systems) |
||
| Line 37: | Line 37: | ||
= WSDL & XSD. Demo, Test, Prod systems = | = WSDL & XSD. Demo, Test, Prod systems = | ||
SIG - is SOAP server. | SIG - is SOAP server. | ||
| + | SIG team manages three systems: | ||
| + | * Demo System. [{{SigWsdlURL}} '''SIG WSDL''']. Open to public for evaluation purposes. Currently only SIG_AirShop request is available | ||
| + | * Test System. Allocated to every customer after the contract signature | ||
| + | * Production System. Allocated to every customer when integration completed | ||
| − | + | WSDL contains the only method SIGQuerySoap which wraps the actual XML request in sig:SIGQuery+sig:Request tags. | |
| − | + | The XML requests and replies schemas available at '''[[media:SIG.xsd|SIG.xsd]]''' | |
| − | + | ||
| − | The XML requests and replies | + | |
This is the simple request | This is the simple request | ||
| Line 66: | Line 68: | ||
</soapenv:Envelope> | </soapenv:Envelope> | ||
</syntaxhighlight> | </syntaxhighlight> | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
Revision as of 10:42, 12 September 2012
Preface
SIG is a middleware web service designed to provide IBE/OTA with a unified interface to the following functions of different GDS and local CRS.
- Fixed date shopping
- Flex date shopping
- Flight Availability
- Fare Availability
- Fare Rule Display
- Booking & Pricing
- Ticket Issue
- Different forms of payment: CASH, CC, CASH+CC
- Booking status & Repricing
- Booking Cancellation & Ticket Void
- Ticket status
- Schedule Display
- Fare Display
Currently SIG manages interfaces with the following systems:
- Galileo
- Sirena-Travel & Sirena-2.3
- SITA Gabriel
- Biletix Distribution System (Charter Database)
SIG is an execellent chance to IBE/OTA to avoid integration with many systems because it offers
- Quick new system links. As soon as organization tasks solved
- IBE/OTA developers do not need to know anything about GDS/CRS. All GDS/CRS technology concerns covered by SIG team.
- IBE/OTA developers do not need to speak Russian to deal with Russian systems
- No extra look/book invoices even for heavy loaded B2C projects.
- Comprehensive shopping engine able to find itineraries not offered by connected GDS/CRS shopping tools
- Smart price and availability caching tools
Currently SIG is being used by the following projects: biletix.ru, portbilet.ru, tutu.ru, e-ticket.ru, aviarost.ru, etc.
These integrations work via SIG old API not available for new customers.
Now SIG team develops new SIG API targeted to launch its basic functions at 01.10.2012.
This API described in details in other sections.
WSDL & XSD. Demo, Test, Prod systems
SIG - is SOAP server. SIG team manages three systems:
- Demo System. SIG WSDL. Open to public for evaluation purposes. Currently only SIG_AirShop request is available
- Test System. Allocated to every customer after the contract signature
- Production System. Allocated to every customer when integration completed
WSDL contains the only method SIGQuerySoap which wraps the actual XML request in sig:SIGQuery+sig:Request tags.
The XML requests and replies schemas available at SIG.xsd
This is the simple request
<soapenv:Header/>
<soapenv:Body>
<sig:SIGQuery>
<sig:Request>
<?xml version="1.0" encoding="UTF-8"?>
<SIG_AirShopRQ CustomerID="TestUser">
<Itinerary>
<OriginDestination ODRef="1" To="mow" From="svx" Date="2013-03-10"/>
<OriginDestination ODRef="2" To="svx" From="mow" Date="2013-03-15"/>
</Itinerary>
<PaxTypes>
<PaxType Count="1" AgeCat="ADT" PTRef="adt0"/>
</PaxTypes>
</SIG_AirShopRQ>
</sig:Request>
</sig:SIGQuery>
</soapenv:Body>
</soapenv:Envelope>
