API:FAQ - Revision history

Admin at 01:25, 16 February 2022

2022-02-16T01:25:26Z

← Older revision		Revision as of 01:25, 16 February 2022
Line 181:		Line 181:

	Debugging: Run a ldd command on mdxxxx.so and libmdxxxxJavaWrapper.so. All dependencies should have a corresponding library mapped. If you are having trouble still, please send the output of these two ldd commands along with a 'uname -a' to tech support.		Debugging: Run a ldd command on mdxxxx.so and libmdxxxxJavaWrapper.so. All dependencies should have a corresponding library mapped. If you are having trouble still, please send the output of these two ldd commands along with a 'uname -a' to tech support.


			==Unable to establish SSL connection when downloading DQ Suite via wget Tool==
			If you encounter an SSL connection error when downloading the DQ Suite file using the wget tool, you can try adding the following options to your command to fix this issue:
			#We're moving away from TLS 1.1 to TLS 1.2 so you need to add the '''–secure-protocol''' option:
			#:<code>--secure-protocol=TLSv1_2</code>
			#If you get a 302 redirect to a different domain, try adding the '''--mirror''' option.
			#:<code>--mirror <nowiki>https://update.melissadata.com</nowiki></code>

Admin at 01:30, 21 January 2022

2022-01-21T01:30:53Z

← Older revision		Revision as of 01:30, 21 January 2022
Line 7:		Line 7:

	==What development environment will the API work with?==		==What development environment will the API work with?==
	The APIs are available for the following platforms: Windows®, Linux®~~, Mac~~, AIX and can be used with any programming language such as C#, Java, Python, C/C++.		The APIs are available for the following platforms: Windows®, Linux®, AIX and can be used with any programming language such as C#, Java, Python, C/C++.

Admin at 19:55, 16 April 2021

2021-04-16T19:55:55Z

← Older revision		Revision as of 19:55, 16 April 2021
Line 7:		Line 7:

	==What development environment will the API work with?==		==What development environment will the API work with?==
	~~This easy to use programmer’s tool is currently provided as a 64-bit DLL~~ for ~~Windows~~ and ~~will work~~ with ~~a variety of~~ programming ~~languages. It is also available for Linux~~, ~~Solaris~~, ~~AIX~~, ~~and HPUX~~.		The APIs are available for the following platforms: Windows®, Linux®, Mac, AIX and can be used with any programming language such as C#, Java, Python, C/C++.

Admin at 20:58, 24 May 2017

2017-05-24T20:58:23Z

← Older revision		Revision as of 20:58, 24 May 2017
Line 152:		Line 152:
	:To work in x64, you must recompile mdxxxxNET.dll and mdxxxxCS.dll into 64bit. Go into the source folder and run CreateDLLs.bat with a x64 Visual Studio command script. Please see the readme.txt and open CreateDLLs.bat in wordpad for more details. Then, grab dll_64bit/mdxxxx.dll. Go to Properties->Build->Target Platform and change to x64.		:To work in x64, you must recompile mdxxxxNET.dll and mdxxxxCS.dll into 64bit. Go into the source folder and run CreateDLLs.bat with a x64 Visual Studio command script. Please see the readme.txt and open CreateDLLs.bat in wordpad for more details. Then, grab dll_64bit/mdxxxx.dll. Go to Properties->Build->Target Platform and change to x64.

	:If you are working with IIS express in Visual Studio, go to Tools > Options > Projects and Solutions > Web Projects > Use the 64 bit version of IIS Express for websites and projects checkbox.”		:If you are working with IIS express in Visual Studio, go to Tools > Options > Projects and Solutions > Web Projects > Use the 64 bit version of IIS Express for websites and projects checkbox.

Admin at 20:58, 24 May 2017

2017-05-24T20:58:01Z

← Older revision		Revision as of 20:58, 24 May 2017
Line 151:		Line 151:
	Working in 64bit on a 64bit machine		Working in 64bit on a 64bit machine
	:To work in x64, you must recompile mdxxxxNET.dll and mdxxxxCS.dll into 64bit. Go into the source folder and run CreateDLLs.bat with a x64 Visual Studio command script. Please see the readme.txt and open CreateDLLs.bat in wordpad for more details. Then, grab dll_64bit/mdxxxx.dll. Go to Properties->Build->Target Platform and change to x64.		:To work in x64, you must recompile mdxxxxNET.dll and mdxxxxCS.dll into 64bit. Go into the source folder and run CreateDLLs.bat with a x64 Visual Studio command script. Please see the readme.txt and open CreateDLLs.bat in wordpad for more details. Then, grab dll_64bit/mdxxxx.dll. Go to Properties->Build->Target Platform and change to x64.

			:If you are working with IIS express in Visual Studio, go to Tools > Options > Projects and Solutions > Web Projects > Use the 64 bit version of IIS Express for websites and projects checkbox.”

Admin at 22:38, 15 December 2016

2016-12-15T22:38:20Z

← Older revision		Revision as of 22:38, 15 December 2016
Line 1:		Line 1:
	__FORCETOC__		__FORCETOC__
	==How To Set Your License ~~String~~?==		==How To Set Your License Key?==
	[[Set Environment Variable\|Set Your Environment Variable For Windows]]		[[Set Environment Variable\|Set Your Environment Variable For Windows]]

Admin at 15:21, 14 October 2016

2016-10-14T15:21:58Z

← Older revision		Revision as of 15:21, 14 October 2016
Line 144:		Line 144:

	;64-bit System		;64-bit System
	Working with the .NET wrapper changes if a use is on a x64 system. On a 64bit machine, they can choose to execute in 32bit mode or 64bit mode, but whatever mode they choose, all components must be have the same architecture.		Working with the .NET wrapper changes if a use is on a x64 system. On a 64bit machine, they can choose to execute in 32bit mode or 64bit mode, but whatever mode they choose, all components must have the same architecture.

	Working in 32bit on a 64bit machine:		Working in 32bit on a 64bit machine:
Line 161:		Line 161:

	;64-bit System		;64-bit System
	Working with the java wrapper changes if a use is on a x64 system. On a 64bit machine, they can choose to execute in 32bit mode or 64bit mode, but whatever mode they choose, all components must be have the same architecture.		Working with the java wrapper changes if a use is on a x64 system. On a 64bit machine, they can choose to execute in 32bit mode or 64bit mode, but whatever mode they choose, all components must have the same architecture.

	Working in 32bit on a 64bit machine:		Working in 32bit on a 64bit machine:
Line 176:		Line 176:

	=="skipping incompatible /th/melissadata/libmdxxxx.so when searching for -lmdxxxx"==		=="skipping incompatible /th/melissadata/libmdxxxx.so when searching for -lmdxxxx"==
	The error is caused when the melissa data unix library is not compatible with your system. There are several configurations that ~~much~~ match for your system to be able to run our libraries on our unix platforms. Please make sure that your glibc version matches or is compatible with the provided library and that you are using the correct width (32 or 64 bit).		The error is caused when the melissa data unix library is not compatible with your system. There are several configurations that must match for your system to be able to run our libraries on our unix platforms. Please make sure that your glibc version matches or is compatible with the provided library and that you are using the correct width (32 or 64 bit).

	Debugging: Run a ldd command on mdxxxx.so and libmdxxxxJavaWrapper.so. All dependencies should have a corresponding library mapped. If you are having trouble still, please send the output of these two ldd commands along with a 'uname -a' to tech support.		Debugging: Run a ldd command on mdxxxx.so and libmdxxxxJavaWrapper.so. All dependencies should have a corresponding library mapped. If you are having trouble still, please send the output of these two ldd commands along with a 'uname -a' to tech support.

Admin at 19:39, 23 June 2016

2016-06-23T19:39:10Z

← Older revision		Revision as of 19:39, 23 June 2016
Line 7:		Line 7:

	==What development environment will the API work with?==		==What development environment will the API work with?==
	This easy to use programmer’s tool is currently provided as a ~~32 or~~ 64-bit DLL ~~or COM object~~ for Windows and will work with a variety of programming languages. It is also available for Linux, Solaris, AIX, and HPUX.		This easy to use programmer’s tool is currently provided as a 64-bit DLL for Windows and will work with a variety of programming languages. It is also available for Linux, Solaris, AIX, and HPUX.

Admin at 23:56, 2 March 2015

2015-03-02T23:56:25Z

Show changes

Admin at 23:55, 2 March 2015

2015-03-02T23:55:41Z

← Older revision		Revision as of 23:55, 2 March 2015
Line 1:		Line 1:
	__FORCETOC__		__FORCETOC__
	==How To Set Your License String?==		==How To Set Your License String?==
	~~;Answer:~~
	:[[Set Environment Variable\|Set Your Environment Variable For Windows]]		:[[Set Environment Variable\|Set Your Environment Variable For Windows]]

Line 8:		Line 7:

	==What development environment will the API work with?==		==What development environment will the API work with?==
	~~;Answer:~~
	:This easy to use programmer’s tool is currently provided as a 32 or 64-bit DLL or COM object for Windows and will work with a variety of programming languages. It is also available for Linux, Solaris, AIX, and HPUX.		:This easy to use programmer’s tool is currently provided as a 32 or 64-bit DLL or COM object for Windows and will work with a variety of programming languages. It is also available for Linux, Solaris, AIX, and HPUX.


	==What type of support do you offer?==		==What type of support do you offer?==
	~~;Answer:~~
	:Technical support is always free, as are the frequent updates, and many online resources found on our website.		:Technical support is always free, as are the frequent updates, and many online resources found on our website.


	==Environment Variables==		==Environment Variables==
	~~;Answer:~~
	:MDADDR_SERVERMODE		:MDADDR_SERVERMODE
	::Currently, MDADDR_SERVERMODE only has one value, “sticky”. Sticky is an option that can be set to change the way Address Object behaves when many instances are created and destroyed. This variable, turned off by default, will enable Address Object to retain some of the data files used for initialization in memory after the last instance of Address Object is de-allocated, but before the application ends. This may be useful for applications that use multiple instances (For example: Web services that use individual threads for each client) and have times where the number of instances drop to 0 while the application is still running. Using this variable should increase the speed of initialization for those qualifying applications. To set the sticky variable, follow these steps:		::Currently, MDADDR_SERVERMODE only has one value, “sticky”. Sticky is an option that can be set to change the way Address Object behaves when many instances are created and destroyed. This variable, turned off by default, will enable Address Object to retain some of the data files used for initialization in memory after the last instance of Address Object is de-allocated, but before the application ends. This may be useful for applications that use multiple instances (For example: Web services that use individual threads for each client) and have times where the number of instances drop to 0 while the application is still running. Using this variable should increase the speed of initialization for those qualifying applications. To set the sticky variable, follow these steps:
Line 43:		Line 39:

	==How do I use checksums to validate the integrity of my files?==		==How do I use checksums to validate the integrity of my files?==
	~~;Answer:~~
	:Checksums are codes generated from files that can be used to check the integrity of a file. If two files have the same checksum, they can be assumed to be the same file. At Melissa Data, we use a md5 checksum utility (http://www.fourmilab.ch/md5/). If our tech support asks for your checksum, you can download the command line utility at the URL above. Then, after unzipping it, navigate to md5.exe from the command line, and type md5 “filename” for the checksum. We will then compare your checksum to ours to see if any corruption has occurred.		:Checksums are codes generated from files that can be used to check the integrity of a file. If two files have the same checksum, they can be assumed to be the same file. At Melissa Data, we use a md5 checksum utility (http://www.fourmilab.ch/md5/). If our tech support asks for your checksum, you can download the command line utility at the URL above. Then, after unzipping it, navigate to md5.exe from the command line, and type md5 “filename” for the checksum. We will then compare your checksum to ours to see if any corruption has occurred.


	==What is in my DQ Suite DVD?==		==What is in my DQ Suite DVD?==
	~~;Answer:~~
	:Here is a general overview of the structure and contents of the DQ Suite DVD:		:Here is a general overview of the structure and contents of the DQ Suite DVD:

Line 82:		Line 76:

	==How do I automate the DQ Suite setup?==		==How do I automate the DQ Suite setup?==
	~~;Answer:~~
	:;For Windows:		:;For Windows:
	::The Windows Setup program for Data Quality Tools accepts optional command line parameters. These can be useful to system administrators and to other programs calling the Setup program wishing to automate the entire process without clicking on the dialogs.		::The Windows Setup program for Data Quality Tools accepts optional command line parameters. These can be useful to system administrators and to other programs calling the Setup program wishing to automate the entire process without clicking on the dialogs.
Line 104:		Line 97:

	==What do I need to do when installing the DQ Suite DVD?==		==What do I need to do when installing the DQ Suite DVD?==
	~~;Answer:~~
	:When you install the DQ Suite DVD, please pay attention to changes.txt on the root of the DVD. It will contain any changes that have been made to any of the objects which may require you to rewrite/recompile your application. Also, when using the wrappers in the Interfaces folder, please read the readmes for each wrapper you are using as they may contain changes to the build process you have to make.		:When you install the DQ Suite DVD, please pay attention to changes.txt on the root of the DVD. It will contain any changes that have been made to any of the objects which may require you to rewrite/recompile your application. Also, when using the wrappers in the Interfaces folder, please read the readmes for each wrapper you are using as they may contain changes to the build process you have to make.


	==What is a wrapper and how do I use it?==		==What is a wrapper and how do I use it?==
	~~;Answer:~~
	:A wrapper is an additional layer of code that acts as an interface from the standard AddressObject dll to the target programming language. Currently, wrappers are available for dotNET, Java, PHP, PERL, Python, Ruby and OWB. In order to use the wrapper, both the underlining code and the wrapper itself must be installed. So, to first install the underlying code, run the install for AddressObject on the root of the DQ Suite DVD. Now, you must install the wrapper itself. Look in the Interfaces folder of the DVD and locate the language and platform of the wrapper you want. Then, follow the readme to install the wrapper. Once installed, again refer to the readme for instructions to setup and run.		:A wrapper is an additional layer of code that acts as an interface from the standard AddressObject dll to the target programming language. Currently, wrappers are available for dotNET, Java, PHP, PERL, Python, Ruby and OWB. In order to use the wrapper, both the underlining code and the wrapper itself must be installed. So, to first install the underlying code, run the install for AddressObject on the root of the DQ Suite DVD. Now, you must install the wrapper itself. Look in the Interfaces folder of the DVD and locate the language and platform of the wrapper you want. Then, follow the readme to install the wrapper. Once installed, again refer to the readme for instructions to setup and run.


	==What is multi-threaded programming, with respect to MelissaDATA’s data quality tools?==		==What is multi-threaded programming, with respect to MelissaDATA’s data quality tools?==
	~~;Answer:~~
	:When working with MelissaDATA API components, you are multi-threading in these situations:		:When working with MelissaDATA API components, you are multi-threading in these situations:
	:*You have several threads, each creating an instance of an object.		:*You have several threads, each creating an instance of an object.
Line 139:		Line 129:

	==Not able to compile PHP interface in PHP Version 5.3.x, any solutions.==		==Not able to compile PHP interface in PHP Version 5.3.x, any solutions.==
	~~;Answer:~~
	:Current SWIG source file mdAddrPHPWrapper.cpp on the disk file is not compatible with Php Version 5.3.x. SWIG wrapper were compiled using PHP 5.2.x. In PPH 5.2.x, SWIG wrappers use zend_error_noreturn() function which is no longer avialable in PHP 5.3.x. To create compatible mdAddrPHPWrapper.dll with Php 5.3.x, you need to make changes in mdAddrPHPWrapper.cpp manually. Open mdAddrPHPWrapper.cpp in text pad and replace “zend_error_noreturn” with “zend_error “. After making changes in mdAddrPHPWrapper.cpp compile wrapper again using CreateDll.bat file.		:Current SWIG source file mdAddrPHPWrapper.cpp on the disk file is not compatible with Php Version 5.3.x. SWIG wrapper were compiled using PHP 5.2.x. In PPH 5.2.x, SWIG wrappers use zend_error_noreturn() function which is no longer avialable in PHP 5.3.x. To create compatible mdAddrPHPWrapper.dll with Php 5.3.x, you need to make changes in mdAddrPHPWrapper.cpp manually. Open mdAddrPHPWrapper.cpp in text pad and replace “zend_error_noreturn” with “zend_error “. After making changes in mdAddrPHPWrapper.cpp compile wrapper again using CreateDll.bat file.


	==xxxxObj.dll was loaded but the call to DllRegisterServer failed with the error code 0x80020009 or 0x80050007==		==xxxxObj.dll was loaded but the call to DllRegisterServer failed with the error code 0x80020009 or 0x80050007==
	~~;Answer:~~
	:The error is caused when the user does not have the administrative rights to register an object. Log into windows as an administrator or command a command prompt as an administrator and try to register again. This security feature was introduced in Windows 7 and Windows Server 2008.		:The error is caused when the user does not have the administrative rights to register an object. Log into windows as an administrator or command a command prompt as an administrator and try to register again. This security feature was introduced in Windows 7 and Windows Server 2008.


	=='MelissaData.mdxxxxCSPINVOKE’ threw an exception==		=='MelissaData.mdxxxxCSPINVOKE’ threw an exception==
	~~;Answer:~~
	:The error is caused when the .NET wrapper cannot find one or more necessary components. Make sure all necessary components are in the correct directories. Melissa Data .NET wrappers are generated using an open source project called SWIG. The chain of dependent libraries are as follows:		:The error is caused when the .NET wrapper cannot find one or more necessary components. Make sure all necessary components are in the correct directories. Melissa Data .NET wrappers are generated using an open source project called SWIG. The chain of dependent libraries are as follows:
	::.NET project ---references--> mdxxxxNET.dll ---uses--> mdxxxxCS.dll ---uses--> mdxxxx.dll.		::.NET project ---references--> mdxxxxNET.dll ---uses--> mdxxxxCS.dll ---uses--> mdxxxx.dll.
Line 167:		Line 154:

	==mdxxxxJavaWrapper.dll: Can't find dependent libraries==		==mdxxxxJavaWrapper.dll: Can't find dependent libraries==
	~~;Answer:~~
	:The error is caused when the Java wrapper cannot find one or more necessary components.Make sure all necessary components are in the correct directories. Melissa Data Java wrappers are generated using an open source project called SWIG. The chain of dependent libraries are as follows:		:The error is caused when the Java wrapper cannot find one or more necessary components.Make sure all necessary components are in the correct directories. Melissa Data Java wrappers are generated using an open source project called SWIG. The chain of dependent libraries are as follows:
	::Java project ---references--> mdxxx.jar and mdxxxxJavaWrapper.dll ---uses--> mdxxxx.dll.		::Java project ---references--> mdxxx.jar and mdxxxxJavaWrapper.dll ---uses--> mdxxxx.dll.
Line 186:		Line 172:
	=="Cannot open shared object file"==		=="Cannot open shared object file"==
	Receiving "Cannot open shared object file: No such file or directory at" error message when trying to use a interface.		Receiving "Cannot open shared object file: No such file or directory at" error message when trying to use a interface.
	~~;Answer:~~
	:Users typically get this error when the generated wrapper .so file cannot find the target .so library. To see this, do a ldd on the wrapper .so file and make sure all the dependency links are satisfied. If the target library dependency link is not satisfied, set your LD_LIBRARY_PATH environment variable to the directory containing the target library and try again. In AIX, the environment variable is called LIBPATH.		:Users typically get this error when the generated wrapper .so file cannot find the target .so library. To see this, do a ldd on the wrapper .so file and make sure all the dependency links are satisfied. If the target library dependency link is not satisfied, set your LD_LIBRARY_PATH environment variable to the directory containing the target library and try again. In AIX, the environment variable is called LIBPATH.


	=="skipping incompatible /th/melissadata/libmdxxxx.so when searching for -lmdxxxx"==		=="skipping incompatible /th/melissadata/libmdxxxx.so when searching for -lmdxxxx"==
	~~;Answer:~~
	:The error is caused when the melissa data unix library is not compatible with your system. There are several configurations that much match for your system to be able to run our libraries on our unix platforms. Please make sure that your glibc version matches or is compatible with the provided library and that you are using the correct width (32 or 64 bit).		:The error is caused when the melissa data unix library is not compatible with your system. There are several configurations that much match for your system to be able to run our libraries on our unix platforms. Please make sure that your glibc version matches or is compatible with the provided library and that you are using the correct width (32 or 64 bit).