QAS Pro On Demand Access Requirements

Document type: Tech doc  
Associated product(s): Product name: Pro On DemandImplementation: On Demand
Views: 5244  |  Created: 3 years agoLast updated: 4 months ago

<< More documents like this

Experian QAS Pro On Demand
High Availability Service



1. Background

The Experian QAS Pro On Demand products and services are based on Portal Web Sites and Web Services that run over HTTP and HTTPS.

Experian QAS Pro On Demand products and services are hosted in redundant data centres located in the United Kingdom and the United States. Each product has access to a primary and secondary data centre to protect customers against interruptions in service.

In the event of a service interruption in one of our data centres, customer transactions will automatically be failed over to the secondary location to ensure continuous service. Once the issue has been cleared customer transactions will be automatically transferred back to the primary location.


2. Access Requirements

Access to the Experian QAS Pro On Demand products and services is over the internet using industry standard protocols and ports. In order to access the High Availability service you need to ensure that certain URLs are accessible through your IT infrastructure (i.e. firewalls). The following table outlines the access requirements necessary to use the V3 Pro On Demand products and services.

Service Name Port Protocol Description
Pro On Demand Portal 80, 443 HTTP, HTTPS

Account Management Portal

https://ondemand.qas.com

https://uk.ondemand.qas.com (194.60.177.160)

https://us.ondemand.qas.com (167.107.84.3)

EMEA/UK Endpoint 443 HTTPS

Integration endpoint WSDL

https://ws.ondemand.qas.com/ProOnDemand/V3/ProOnDemandService.asmx

https://uk.ws.ondemand.qas.com/ProOnDemand/V3/ProOnDemandService.asmx

(194.60.177.162) 

https://us.ws.ondemand.qas.com/ProOnDemand/V3/ProOnDemandService.asmx

 (167.107.84.4)

US Endpoint 443 HTTPS

Integration endpoint WSDL
https://ws2.ondemand.qas.com/ProOnDemand/V3/ProOnDemandService.asmx

https://us.ws2.ondemand.qas.com/ProOnDemand/V3/ProOnDemandService.asmx

 

(167.107.80.230) https://us2.ws2.ondemand.qas.com/ProOnDemand/V2/ProOnDemandService.asmx 

(66.128.68.203)

APAC Endpoint 443 HTTPS

Integration endpoint WSDL

https://ws3.ondemand.qas.com/ProOnDemand/V3/ProOnDemandService.asmx

https://au.ws3.ondemand.qas.com/ProOnDemand/V3/ProOnDemandService.asmx
(205.174.45.23)

https://us2.ws3.ondemand.qas.com/ProOnDemand/V3/ProOnDemandService.asmx 
(66.128.68.203)


  
The access requirements for customers using V1 of the Pro On Demand WSDL are the same as V2. The V1 WSDL endpoints are:

https://ws.ondemand.qas.com/ProWebIntermediary/OnDemandProWebIntermediary.asmx
https://ws2.ondemand.qas.com/ProWebIntermediary/OnDemandProWebIntermediary.asmx


3. Testing

Each WSDL endpoint has a number of fully functioning URLs. These can be used to test access from your servers to each location where the Pro On Demand products and services are hosted.

 

E.g. A UK customer should ensure their servers have access to the following endpoints and that they can run searches against them.

https://ws.ondemand.qas.com/ProOnDemand/V3/ProOnDemandService.asmx
https://uk.ws.ondemand.qas.com/ProOnDemand/V3/ProOnDemandService.asmx
https://us.ws.ondemand.qas.com/ProOnDemand/V3/ProOnDemandService.asmx

 

E.g. A US customer should ensure their servers have access to the following endpoints and that they can run searches against them


https://ws2.ondemand.qas.com/ProOnDemand/V3/ProOnDemandService.asmx
https://us.ws2.ondemand.qas.com/ProOnDemand/V3/ProOnDemandService.asmx  https://us2.ws2.ondemand.qas.com/ProOnDemand/V2/ProOnDemandService.asmx

E.g. A APAC customer should ensure their servers have access to the following endpoints and that they can run searches against them

https://ws3.ondemand.qas.com/ProOnDemand/V3/ProOnDemandService.asmx 

https://au.ws3.ondemand.qas.com/ProOnDemand/V3/ProOnDemandService.asmx 

https://us2.ws3.ondemand.qas.com/ProOnDemand/V3/ProOnDemandService.asmx

NB: These URLs are all fully functioning versions of the product and can be used by a customer to run address lookups.

 

 

Was this document helpful?

What can we do to improve this information?