Operating system
The Pro Web installer contains the setup executable for Pro Web. There are four steps to installing Pro Web on Windows:
The Pro Web installer contains the setup executable for Pro Web. There are four steps to installing Pro Web on Windows:
Login
Run the Pro Web setup executable.
Once the installation program starts, follow the on-screen instructions to install Pro Web.
On the license Agreement dialog, the license agreement is displayed. You should read the license agreement, and if you are happy with the terms, select the I accept the terms of the license agreement option.
The Select Components dialog is displayed. You can choose to install one or more of the following sets of sample integration code and pages:
The program files and sample code can be installed on the same machine or on different machines. Select the sample integration code and pages that you want to install.
Select the C interface option to install the C API library, which can be used in a non-web environment.
Choose the destination folder you want to install to.
On the Primary Server Connection Details dialog, enter the primary port number that you want to use for Pro Web to connect to the server. If a previous version of Pro Web exists then this port number must be different. If required, you can add a comment to the Comment box to appear alongside the server port number in the Administrator Console.
If you selected the C#.NET sample code and you do not have the Microsoft .NET Framework installed on your system, the Pro Web Installation will prompt you to install it.
For each sample integration code that you selected, a dialog will be displayed for you to confirm the destination folder in which the files will be installed. When you have specified the locations for all the integration code that you want to install, the Select Program Folder dialog is displayed.
Enter the name of the folder that you want to use for the Pro Web program files. You can select an existing folder from the list, or specify a new folder by typing the name in the Program Folder text box.
On the Start Copying Files dialog, a list of the choices that you have made is displayed. Click Next to start copying the files to the computer. You may be prompted to install Microsoft Visual Studio C++ 2010 Redistributable Package.
Click Yes to install the package. If a maintenance pop-up appears, click Repair and follow the on-screen instructions.
After the product installation is complete, you can choose to install data. Check or uncheck the Install Data box as required, and click Finish to close the dialog.The final installation dialog displays your server name and address as well as the primary server port number. You will need these details if you want to check whether the Pro Web Service is running or to configure additional integration code.
When you have successfully installed Pro Web, the following components are available from the Pro Web program group on the Start menu (or on the Apps screen for later versions of Windows).
Components | Description |
---|---|
Add Service | This shortcut will install the Pro Web service. You will have to start it manually. |
Remove Service | This shortcut will remove the Pro Web service. You can reinstate it using the Add Service shortcut. |
Uninstall | This will completely remove Pro Web from your system. |
Integration Code | The integration code shortcuts will open the folders you chose when installing the sample code. |
Configuration Editor | This will open the Configuration Editor. |
Administrator Console | This will open the Administrator Console. |
Test Harness | This will open the Test Harness. |
Data Checker | The will open the Data Checker. |
Help | A link to the online user assistance. |
The following program files need to be installed on all machines that will host the Pro Web server (typically your web servers). They are installed in C:/Program Files/ Experian/Pro Web by default.
File | Description |
---|---|
qaswvdn.exe or qaswvdk.exe | Pro Web server |
qawserve.ini | Pro Web server configuration file qalcl.dat |
qalcl.dat | Locale information file |
qalicn.ini | Licence information file |
country.ini | Country information file |
Before you begin
<version number>
is highlighted.Newly installed data will not be available for use until you have activated it.
Data Updates
Experian provides periodic updates of datasets as and when updated data is available. Follow the instructions in the installation program to replace your existing datasets.
Datasets expire after a certain period of time, at which point you must install an update.
The Pro Web Service should start automatically after a successful installation. To check that the service is running type http://[server name]:[port]/proweb.wsdl
into a web browser, using the server name and port specified during installation. If the service is running, the Pro Web WSDL document is displayed.
If you cannot see the document, you must activate the Pro Web Service manually. To do this, follow these steps:
<version number>
service.Datasets must be activated using the Administrator Console. Using the Administrator Console, Windows users can update data without shutting down the server. To run the Administrator Console, go to the program group where you installed the server, and click on Administrator Console. To activate newly-installed data you must follow the same procedure as for updating existing data.
Visit the troubleshooting section to troubleshoot your installation.
Operating system
There are three steps to installing Pro Web on Linux:
administrator privileges
You will need to know the IP address of your machine as well as the number of an unused port (first port) for the primary Pro Web Server. If you are using Partner Sourced datasets, you will also require the number of an unused second port for the Partner Sourced Data Server.
To install the Pro Web software, follow these steps:
Extract the appropriate files for your platform (i.e. web.800.bin.tar) to a suitable location, for example /opt/qasProWeb/.
In order to view the man pages supplied with Pro Web, you must first copy them from the man/man7 directory in the pro installer to the man/man7 directory on your computer. This is usually usr/share/man/man7. Once copied, man pages can be invoked using the man command.
Navigate to your chosen location and, using a text editor such as vim, edit the indicated lines in the following files:
ServerAddress=QATCPIP:
IP address:first portServerWSDLUrn=http:
//IP address:first portExternalServers=
description,QATCPIP:
IP address:second portWhere description is an internal label for the Partner Sourced Data Server. If you are not using the Partner Sourced Data Server it is not necessary to edit the ExternalServers line.
ServerAddress=QATCPIP
:IP address:second portUnlockCode=
license keyWhere each license key is the full text of a Partner Sourced dataset license key as it appears on your despatch note. If you are not using the Partner Sourced Data Server it is not necessary to edit acserver.ini.
ServerAddress=QATCPIP:
IP address:first portAdd your Primary Sourced data license key(s) to separate lines at the end of this file, as they appear on your despatch note.
Data files are installed separately from Pro Web but they should be located on the same machine as the Pro Web Server. The files installed vary according to the dataset, additional datasets and DataPlus sets you have purchased. For information about a specific dataset see the Data Guide that shipped with your data.
Before you begin the installation process, you should ensure that you have the despatch note that is supplied with Pro Web. The despatch note contains all of the license keys for each dataset that you have purchased. When you install data for the first time, you are prompted to insert the license key for each dataset that you want to install.
To install new Primary Sourced data, follow these steps:
Copy the data files to an appropriate location on your system, for example /opt/qasData/.
The first time that you install a dataset, you will need to add the InstalledData
and DataMappings
settings to the qawserve.ini file. Navigate to /opt/qasProWeb/ (or wherever you installed the Pro Web Server) and open qawserve.ini in a text editor such as vim.
Under the [QADefault] sections, add an InstalledData line. This setting should contain a list of the datasets you have installed, and their locations:
InstalledData={dataset identifier},{path}
+{dataset identifier},{path}
This setting should point to the data that you just copied. For example, the line might read:
InstalledData=GBR,/opt/qasData/gbr001
If more than one dataset is to be added to this setting, you should use the plus (+) sign at the start of each subseqent line. For example:
InstalledData=GBR,/opt/qasData/gbr001
+USA,/opt/qasData/usa001
Add a new AllInstalledData line beneath this, with the same content:
AllInstalledData=GBR,/opt/qasData/gbr001
+USA,/opt/qasData/usa001
Do not remove any exisiting lines from the AllInstalledData
setting.
InstalledData
In the same section, add a DataMappings
setting. This setting should contain a list of the datasets and groups of additional datasets you want to use:
DataMappings={data mapping identifier},{data mapping name},{dataset list}
+{data mapping identifier},{data mapping name},{dataset list}
In this example, if you had a Names additional dataset, the line might read:
Datamappings=GBR,United Kingdom,GBR
+GBN,United Kingdom With Names,GBR+GBRNAM
To update existing Primary Sourced data, follow these steps:
Copy the data files to an appropriate new location on your system.
Navigate to /opt/qasProWeb/ (or wherever you installed the Pro Web Server), and open qawserve.ini in a text editor such as vim.
Under the [QADefault] section, add or edit the NewInstalledData
setting as required. This setting lists the data you have installed, but have not yet activated to work with any products.
The setting is in the same format as the InstalledData
setting:
NewInstalledData={dataset identifier},{path}
This setting has to point to the data that you just copied. For example, the line might read:
NewInstalledData=GBR,/opt/qasData/gbr001
If more than one dataset is to be added to this setting, you should use the plus (+) sign at the start of each subsequent line. For example:
NewInstalledData=GBR,/opt/qasData/gbr001
+AUS,/opt/qasData/aus001
You should also check that the DataMappings
setting is still correct for the data you are updating.
Finally, activate the new data using the Administrator Console or the Command Line Management Utility.
To install new Partner Sourced data, follow these steps:
Stop the Partner Sourced Data Server (qasproglo) if it is running.
If you already have Partner Sourced datasets installed, you must copy the data files from the data DVD to the same location as the existing data on your system. If this is the first time you are installing Partner Sourced datasets, you can choose an appropriate location, such as /opt/qasData/.
Ensure the data filenames are in upper case and in the correct format, for example: ITA5BI.MD, ITA5FC.MD and ITA5GC.MD. The first three characters of the filename are the ISO code of the country whose data is stored in the file.
Datasets can occupy between one and three files, ending in BI, FC or GC (as above). You should copy all files for each dataset you are licensed to use.
Navigate to /opt/qasProWeb/ (or wherever you installed the Pro Web Server) and open acserver.ini in a text editor such as vim.
Under the [QADefault] section, locate or create the DataDir
line. This setting should contain the path to which you copied the data files, for example:
DataDir=/opt/qasData/
You can also use the InstalledData setting to specify the location of each dataset separately.
In the same section, locate the DataMappings setting. This setting should contain a complete list of the Partner Sourced datasets you want to use, so you need to add a line for each new dataset you are installing:
DataMappings={data mapping identifier},{description},{ISO}
For example, if you had the Austria and Italy datasets the line might read:
Datamappings=AUT,Austria,AUT
+ITA,Italy,ITA
Start or restart the Partner Sourced Data Server.
DataDir
, InstalledData
and DataMappings
settings in the acserver.ini file (located in /opt/qasProWeb/ or wherever you installed the Pro Web Server) are still correct for the data you have updated.If you need to perform a data rollback, follow these steps but copy the data file from your backup location.
You should copy all files. Data files must be in lower case and in the following format: usa.zlx, usa.dts, usagcd.dap.
The first time that you carry out a data update, you will need to add InstalledData
and DataMappings
settings to the qawserve.ini file.
The qawserve.ini file is located in the apps folder. Open the file using a plain text editor such as vi or emacs. Under the [QADefault] section, locate the settings InstalledData
and DataMappings
. These settings contains a list of the datasets you have installed.
Add a line to each setting for each new dataset that you are installing, or update the path for any dataset you are updating.
Data Updates
Experian provides periodic updates of datasets as and when updated data is available. These updates will be sent to you; follow the instructions in the installation program to replace your existing datasets.
Datasets expire after a certain period of time, at which point you must install an update.
Before you start the server you should check the resource limit values.
Depending on whether you want to start the server interactively or via the system's startup scripts, resource limitations may apply. Use the ulimit -a command (or your system's equivalent) to verify that the following requirements are met:
Resource Name | Limitation |
---|---|
time | This needs to be set to unlimited for continuous operation. |
stack(kbytes) | This should be set to a minimum value of 1024KB. |
open files | This should be set to a minimum value of 4 for each concurrent client. If you use DataPlus, the factor can increase up to the number of data files installed for the dataset. For example, if you use all the Australia DataPlus sets then the value should be 8 for each concurrent client. |
The resource names may vary depending on your Web operating system. For example, "open files" is called "nofiles (descriptors)" on AIX.
To start the service, follow these steps:
Operating system
There are three steps to installing Pro Web on Aix:
administrator privileges
You will need to know the IP address of your machine as well as the number of an unused port (first port) for the primary Pro Web Server. If you are using Partner Sourced datasets, you will also require the number of an unused second port for the Partner Sourced Data Server.
To install the Pro Web software, follow these steps:
Extract the appropriate files for your platform (i.e. web.800.bin.tar) to a suitable location, for example /opt/qasProWeb/.
In order to view the man pages supplied with Pro Web, you must first copy them from the man/man7 directory in the pro installer to the man/man7 directory on your computer. This is usually usr/share/man/man7. Once copied, man pages can be invoked using the man command.
Navigate to your chosen location and, using a text editor such as vim, edit the indicated lines in the following files:
ServerAddress=QATCPIP:
IP address:first portServerWSDLUrn=http:
//IP address:first portExternalServers=
description,QATCPIP:
IP address:second portWhere description is an internal label for the Partner Sourced Data Server. If you are not using the Partner Sourced Data Server it is not necessary to edit the ExternalServers line.
ServerAddress=QATCPIP
:IP address:second portUnlockCode=
license keyWhere each license key is the full text of a Partner Sourced dataset license key as it appears on your despatch note. If you are not using the Partner Sourced Data Server it is not necessary to edit acserver.ini.
ServerAddress=QATCPIP:
IP address:first portAdd your Primary Sourced data license key(s) to separate lines at the end of this file, as they appear on your despatch note.
Data files are installed separately from Pro Web but they should be located on the same machine as the Pro Web Server. The files installed vary according to the dataset, additional datasets and DataPlus sets you have purchased. For information about a specific dataset see the Data Guide that shipped with your data.
Before you begin the installation process, you should ensure that you have the despatch note that is supplied with Pro Web. The despatch note contains all of the license keys for each dataset that you have purchased. When you install data for the first time, you are prompted to insert the license key for each dataset that you want to install.
To install new Primary Sourced data, follow these steps:
Copy the data files to an appropriate location on your system, for example /opt/qasData/.
The first time that you install a dataset, you will need to add the InstalledData
and DataMappings
settings to the qawserve.ini file. Navigate to /opt/qasProWeb/ (or wherever you installed the Pro Web Server) and open qawserve.ini in a text editor such as vim.
Under the [QADefault] sections, add an InstalledData line. This setting should contain a list of the datasets you have installed, and their locations:
InstalledData={dataset identifier},{path}
+{dataset identifier},{path}
This setting should point to the data that you just copied. For example, the line might read:
InstalledData=GBR,/opt/qasData/gbr001
If more than one dataset is to be added to this setting, you should use the plus (+) sign at the start of each subseqent line. For example:
InstalledData=GBR,/opt/qasData/gbr001
+USA,/opt/qasData/usa001
Add a new AllInstalledData line beneath this, with the same content:
AllInstalledData=GBR,/opt/qasData/gbr001
+USA,/opt/qasData/usa001
Do not remove any exisiting lines from the AllInstalledData
setting.
InstalledData
In the same section, add a DataMappings
setting. This setting should contain a list of the datasets and groups of additional datasets you want to use:
DataMappings={data mapping identifier},{data mapping name},{dataset list}
+{data mapping identifier},{data mapping name},{dataset list}
In this example, if you had a Names additional dataset, the line might read:
Datamappings=GBR,United Kingdom,GBR
+GBN,United Kingdom With Names,GBR+GBRNAM
To update existing Primary Sourced data, follow these steps:
Copy the data files to an appropriate new location on your system.
Navigate to /opt/qasProWeb/ (or wherever you installed the Pro Web Server), and open qawserve.ini in a text editor such as vim.
Under the [QADefault] section, add or edit the NewInstalledData
setting as required. This setting lists the data you have installed, but have not yet activated to work with any products.
The setting is in the same format as the InstalledData
setting:
NewInstalledData={dataset identifier},{path}
This setting has to point to the data that you just copied. For example, the line might read:
NewInstalledData=GBR,/opt/qasData/gbr001
If more than one dataset is to be added to this setting, you should use the plus (+) sign at the start of each subsequent line. For example:
NewInstalledData=GBR,/opt/qasData/gbr001
+AUS,/opt/qasData/aus001
You should also check that the DataMappings
setting is still correct for the data you are updating.
Finally, activate the new data using the Administrator Console or the Command Line Management Utility.
To install new Partner Sourced data, follow these steps:
Stop the Partner Sourced Data Server (qasproglo) if it is running.
If you already have Partner Sourced datasets installed, you must copy the data files from the data DVD to the same location as the existing data on your system. If this is the first time you are installing Partner Sourced datasets, you can choose an appropriate location, such as /opt/qasData/.
Ensure the data filenames are in upper case and in the correct format, for example: ITA5BI.MD, ITA5FC.MD and ITA5GC.MD. The first three characters of the filename are the ISO code of the country whose data is stored in the file.
Datasets can occupy between one and three files, ending in BI, FC or GC (as above). You should copy all files for each dataset you are licensed to use.
Navigate to /opt/qasProWeb/ (or wherever you installed the Pro Web Server) and open acserver.ini in a text editor such as vim.
Under the [QADefault] section, locate or create the DataDir
line. This setting should contain the path to which you copied the data files, for example:
DataDir=/opt/qasData/
You can also use the InstalledData setting to specify the location of each dataset separately.
In the same section, locate the DataMappings setting. This setting should contain a complete list of the Partner Sourced datasets you want to use, so you need to add a line for each new dataset you are installing:
DataMappings={data mapping identifier},{description},{ISO}
For example, if you had the Austria and Italy datasets the line might read:
Datamappings=AUT,Austria,AUT
+ITA,Italy,ITA
Start or restart the Partner Sourced Data Server.
DataDir
, InstalledData
and DataMappings
settings in the acserver.ini file (located in /opt/qasProWeb/ or wherever you installed the Pro Web Server) are still correct for the data you have updated.If you need to perform a data rollback, follow these steps but copy the data file from your backup location.
You should copy all files. Data files must be in lower case and in the following format: usa.zlx, usa.dts, usagcd.dap.
The first time that you carry out a data update, you will need to add InstalledData
and DataMappings
settings to the qawserve.ini file.
The qawserve.ini file is located in the apps folder. Open the file using a plain text editor such as vi or emacs. Under the [QADefault] section, locate the settings InstalledData
and DataMappings
. These settings contains a list of the datasets you have installed.
Add a line to each setting for each new dataset that you are installing, or update the path for any dataset you are updating.
Data Updates
Experian provides periodic updates of datasets as and when updated data is available. These updates will be sent to you; follow the instructions in the installation program to replace your existing datasets.
Datasets expire after a certain period of time, at which point you must install an update.
Before you start the server you should check the resource limit values.
Depending on whether you want to start the server interactively or via the system's startup scripts, resource limitations may apply. Use the ulimit -a command (or your system's equivalent) to verify that the following requirements are met:
Resource Name | Limitation |
---|---|
time | This needs to be set to unlimited for continuous operation. |
stack(kbytes) | This should be set to a minimum value of 1024KB. |
open files | This should be set to a minimum value of 4 for each concurrent client. If you use DataPlus, the factor can increase up to the number of data files installed for the dataset. For example, if you use all the Australia DataPlus sets then the value should be 8 for each concurrent client. |
The resource names may vary depending on your Web operating system. For example, "open files" is called "nofiles (descriptors)" on AIX.
To start the service, follow these steps:
Operating system
There are three steps to installing Pro Web on Solaris:
administrator privileges
You will need to know the IP address of your machine as well as the number of an unused port (first port) for the primary Pro Web Server. If you are using Partner Sourced datasets, you will also require the number of an unused second port for the Partner Sourced Data Server.
To install the Pro Web software, follow these steps:
Extract the appropriate files for your platform (i.e. web.800.bin.tar) to a suitable location, for example /opt/qasProWeb/.
In order to view the man pages supplied with Pro Web, you must first copy them from the man/man7 directory in the pro installer to the man/man7 directory on your computer. This is usually usr/share/man/man7. Once copied, man pages can be invoked using the man command.
Navigate to your chosen location and, using a text editor such as vim, edit the indicated lines in the following files:
ServerAddress=QATCPIP:
IP address:first portServerWSDLUrn=http:
//IP address:first portExternalServers=
description,QATCPIP:
IP address:second portWhere description is an internal label for the Partner Sourced Data Server. If you are not using the Partner Sourced Data Server it is not necessary to edit the ExternalServers line.
ServerAddress=QATCPIP
:IP address:second portUnlockCode=
license keyWhere each license key is the full text of a Partner Sourced dataset license key as it appears on your despatch note. If you are not using the Partner Sourced Data Server it is not necessary to edit acserver.ini.
ServerAddress=QATCPIP:
IP address:first portAdd your Primary Sourced data license key(s) to separate lines at the end of this file, as they appear on your despatch note.
Data files are installed separately from Pro Web but they should be located on the same machine as the Pro Web Server. The files installed vary according to the dataset, additional datasets and DataPlus sets you have purchased. For information about a specific dataset see the Data Guide that shipped with your data.
Before you begin the installation process, you should ensure that you have the despatch note that is supplied with Pro Web. The despatch note contains all of the license keys for each dataset that you have purchased. When you install data for the first time, you are prompted to insert the license key for each dataset that you want to install.
To install new Primary Sourced data, follow these steps:
Copy the data files to an appropriate location on your system, for example /opt/qasData/.
The first time that you install a dataset, you will need to add the InstalledData
and DataMappings
settings to the qawserve.ini file. Navigate to /opt/qasProWeb/ (or wherever you installed the Pro Web Server) and open qawserve.ini in a text editor such as vim.
Under the [QADefault] sections, add an InstalledData line. This setting should contain a list of the datasets you have installed, and their locations:
InstalledData={dataset identifier},{path}
+{dataset identifier},{path}
This setting should point to the data that you just copied. For example, the line might read:
InstalledData=GBR,/opt/qasData/gbr001
If more than one dataset is to be added to this setting, you should use the plus (+) sign at the start of each subseqent line. For example:
InstalledData=GBR,/opt/qasData/gbr001
+USA,/opt/qasData/usa001
Add a new AllInstalledData line beneath this, with the same content:
AllInstalledData=GBR,/opt/qasData/gbr001
+USA,/opt/qasData/usa001
Do not remove any exisiting lines from the AllInstalledData
setting.
InstalledData
In the same section, add a DataMappings
setting. This setting should contain a list of the datasets and groups of additional datasets you want to use:
DataMappings={data mapping identifier},{data mapping name},{dataset list}
+{data mapping identifier},{data mapping name},{dataset list}
In this example, if you had a Names additional dataset, the line might read:
Datamappings=GBR,United Kingdom,GBR
+GBN,United Kingdom With Names,GBR+GBRNAM
To update existing Primary Sourced data, follow these steps:
Copy the data files to an appropriate new location on your system.
Navigate to /opt/qasProWeb/ (or wherever you installed the Pro Web Server), and open qawserve.ini in a text editor such as vim.
Under the [QADefault] section, add or edit the NewInstalledData
setting as required. This setting lists the data you have installed, but have not yet activated to work with any products.
The setting is in the same format as the InstalledData
setting:
NewInstalledData={dataset identifier},{path}
This setting has to point to the data that you just copied. For example, the line might read:
NewInstalledData=GBR,/opt/qasData/gbr001
If more than one dataset is to be added to this setting, you should use the plus (+) sign at the start of each subsequent line. For example:
NewInstalledData=GBR,/opt/qasData/gbr001
+AUS,/opt/qasData/aus001
You should also check that the DataMappings
setting is still correct for the data you are updating.
Finally, activate the new data using the Administrator Console or the Command Line Management Utility.
To install new Partner Sourced data, follow these steps:
Stop the Partner Sourced Data Server (qasproglo) if it is running.
If you already have Partner Sourced datasets installed, you must copy the data files from the data DVD to the same location as the existing data on your system. If this is the first time you are installing Partner Sourced datasets, you can choose an appropriate location, such as /opt/qasData/.
Ensure the data filenames are in upper case and in the correct format, for example: ITA5BI.MD, ITA5FC.MD and ITA5GC.MD. The first three characters of the filename are the ISO code of the country whose data is stored in the file.
Datasets can occupy between one and three files, ending in BI, FC or GC (as above). You should copy all files for each dataset you are licensed to use.
Navigate to /opt/qasProWeb/ (or wherever you installed the Pro Web Server) and open acserver.ini in a text editor such as vim.
Under the [QADefault] section, locate or create the DataDir
line. This setting should contain the path to which you copied the data files, for example:
DataDir=/opt/qasData/
You can also use the InstalledData setting to specify the location of each dataset separately.
In the same section, locate the DataMappings setting. This setting should contain a complete list of the Partner Sourced datasets you want to use, so you need to add a line for each new dataset you are installing:
DataMappings={data mapping identifier},{description},{ISO}
For example, if you had the Austria and Italy datasets the line might read:
Datamappings=AUT,Austria,AUT
+ITA,Italy,ITA
Start or restart the Partner Sourced Data Server.
DataDir
, InstalledData
and DataMappings
settings in the acserver.ini file (located in /opt/qasProWeb/ or wherever you installed the Pro Web Server) are still correct for the data you have updated.If you need to perform a data rollback, follow these steps but copy the data file from your backup location.
You should copy all files. Data files must be in lower case and in the following format: usa.zlx, usa.dts, usagcd.dap.
The first time that you carry out a data update, you will need to add InstalledData
and DataMappings
settings to the qawserve.ini file.
The qawserve.ini file is located in the apps folder. Open the file using a plain text editor such as vi or emacs. Under the [QADefault] section, locate the settings InstalledData
and DataMappings
. These settings contains a list of the datasets you have installed.
Add a line to each setting for each new dataset that you are installing, or update the path for any dataset you are updating.
Data Updates
Experian provides periodic updates of datasets as and when updated data is available. These updates will be sent to you; follow the instructions in the installation program to replace your existing datasets.
Datasets expire after a certain period of time, at which point you must install an update.
Before you start the server you should check the resource limit values.
Depending on whether you want to start the server interactively or via the system's startup scripts, resource limitations may apply. Use the ulimit -a command (or your system's equivalent) to verify that the following requirements are met:
Resource Name | Limitation |
---|---|
time | This needs to be set to unlimited for continuous operation. |
stack(kbytes) | This should be set to a minimum value of 1024KB. |
open files | This should be set to a minimum value of 4 for each concurrent client. If you use DataPlus, the factor can increase up to the number of data files installed for the dataset. For example, if you use all the Australia DataPlus sets then the value should be 8 for each concurrent client. |
The resource names may vary depending on your Web operating system. For example, "open files" is called "nofiles (descriptors)" on AIX.
To start the service, follow these steps:
Operating system
The Pro Web sample pages provide a good starting point for integrating in to your own system. To begin, make sure that the server path is configured correctly.For Windows users, this will be done during installation (except for the JSP sample which must be configured manually). For UNIX users, or if the server address or port has been changed, you must reconfigure the sample pages as follows:
Integration Code | File | Form |
---|---|---|
JSP | web.xml. Uncompress the war file and extract the web.xml file from the WEB-INF subdirectory. |
<param-value>http://localhost:2021</param-value> |
C#.NET | web.config in the root directory | <add key="com.qas.proweb.serverURL" value="http://localhost:2021/" /> |
PHP | constants.inc in the root directory | define( CONTROL_WSDL_URN, "http://localost:2021/proweb.wsdl"); |
Now that the server path has been configured correctly, the sample pages can be viewed by navigating to the index.htm page for the relevant language. For example, the C# sample pages installed to the default location could be viewed at http://[server address]/ProWebCS/index.htm.