Location:  United Kingdom  (clear)

Upgrading from Pro V3 API to Pro V6 API

Document type: Tech doc  
Associated product(s): Product name: Pro Version: 1.0 - 3.x Implementation: API (more products)
Product name: Pro Version: 4.0 + Implementation: API

Views: 318  |  Created: Last yearLast updated: Last year
Countries: United Kingdom United Kingdom 

Requirements

You will require the following information or resources to perform this upgrade. If you cannot meet the requirements, you will need to consult your IT department/ IT administrator.

1. The location on your computer of the current data files

2. The current QAS program files location

3. What data you will require for the new product (address data, data plus sets, other countries)

4. Ensure there is a nominated person to perform the quarterly data updates. Failure to perform updates will result in the data expiring and the product not working. If this nominated person changes, you should contact us to get the address or name information updated on your account. 

5. You will need to decide if you would like to create a Primary or User Interface integration (refer to manual).

6. What search engine will your integration use (singleline, typedown – refer to the manual)?

7. You will need to have experience developing software in the language you are integrating in. This would include error handling and also testing.

8. Time – a User Interface integration will probably take 1-3 days for the integration and then some testing time. A Primary integration will probably take 3-6 days. You may also wish to consider some Professional Services time – you should discuss this with your Account Manager.

9. If you would like to take advantage of our Electronic Updates product then please contact your Account Manager.

Steps to be Taken

1. Install and configure the Pro V6 API software, as per the V6 API Guide.

2. Test your installation with the supplied Test Harness, using the latest test address to ensure you have the most recent data.

3. Compared with your existing code, the program flow will be largely the same. However the function calls will be different, for example whereas V3 uses QAPro_UIPopup, V6 uses QAProWV_UIStartup. For more information on the functions, refer to the API Guide, in either the “Primary API Reference” or the “User Interface Reference”.

4. You should now write your V6 based on the functionality of your existing integration, or rework if necessary. We recommend that you refer to the Pro V6 API Guide or the supplied sample code for guidance on how to use the API and integration best practises, even if you have integrated an Experian QAS product before.

Was this document helpful?

What can we do to improve this information?