The configuration of Evolvi involves both Micros|Travel and Evolvi, this documentation goes so far as to describe the Micros|Travel involvement.
The whole download process can be described best in a step by step fashion,
1) User logs into Evolvi system
2) User creates booking in Evolvi and creates a Handoff file, this handoff file is initially created and exists only on Evolvi's systems.
3) Evolvi then transfer this file shortly after creation to a folder on the Users network, this procedure is handled by Evolvi and up to and including this point is Evolvi's responsibility.
4) Micros|Travel run a background process on a machine in the Users network, this application will read these handoff's from the folder which Evolvi drop them off at. From this point onward the booking is handled by Micros|Travel Software.
5) The application will transfer the Handoff from Evolvi into the CRS Tables, the same place standard GDS bookings are located.
6) The User checks their download list shortly after the download is done to see if it has arrived, if so they continue to download in the same fashion as any other GDS download.
+ Points 1 to 3 inclusive are entirely reliant on Evolvi if any of those points can not be passed then they should be able to resolve those issues.
+ Points 4 to 6 inclusive are reliant on Micros|Travel, as such if any of these points can not be passed then we should be contacted.
+ Points 3 to 5 inclusive are automatic and invisible to the end user, but still require time to complete. The time taken to get from point 4 to 5 is definable by Micros|Travel. The time taken from 3 to 4 is dependant on Evolvi's systems and quite possibly your Internet Service Provider (ISP).
+ Any data inconsistencies discovered on GDS & Evolvi downloads would normally run directly through to the Micros|Travel Support team, however, the root cause of such data problems may lie with the source of the data, in this case, the user entering the booking or Evolvi. Micros|Travel will normally investigate these scenarios to the best of their ability given the information given. If such an enquiry arises it is advised that a booking reference, or some identifiable aspect of the Evolvi download is included when e-mailing support. If possible, it would be ideal for the XML file in question to be forwarded to Micros|Travel. This could significantly speed up the response times.
For Traveller to even begin picking up the Evolvi data, it must first be arriving on the users network, procedure we would recommend to be handled by Evolvi who have a number of options. It is advised that they are contacted for a full overview of these options. Micros|Travel can advise on the best option for Traveller if required.
Setting up Traveller for Evolvi would normally be carried out by a Micros|Travel Engineer, for exact information contact support or your account manager. A basic overview of the system setup is described below:
+ A program, named evxfer.exe is installed on a single machine on the Users network, this machine will have access to both Traveller and the folder in which the evolvi handoff's are located.
+ An evolvi.ini configuration file which contains the following information will contain the changeable settings for the evxfer.exe program.
- Pseudo
City : The Pseudo city code for downloads, this is set by Evolvi.
- Path : The path in which the *.XML files will appear from
Evolvi.
- Operator : The Operator for all Evolvi Downloads, this often
differs from branch to branch, as such is a changeable setting.
- TTYP : the Transaction Type, this is normally "RAIL"
but can in some circumstances be otherwise.
- Department : the department in which Evolvi downloads are
processed by default.
There are 6 flexible and 4 static custom fields
The 6 flexible fields are reserved by Micros|Travel for items which can change code/value on a download-by-download basis.
The 4 static custom fields are reserved for elements which rarely change
For more information on how to use these entries, click here.
