In order to bring you the best possible user experience, this site uses Javascript. If you are seeing this message, it is likely that the Javascript option in your browser is disabled. For optimal viewing of this site, please ensure that Javascript is enabled for your browser.
Login  |   On Demand  |   Home  |   qad.com




Integrating QAD CRM with QAD EE
QAD CRM uses database and session triggers and QXtend to connect and update the databases of both systems for other modules.
For integration, the databases of both systems:
Must always be available
Must run in multi-user mode
Can share the same database server
For integration you must configure the file servers of QAD CRM and your QAD Enterprise Applications.
QAD CRM uses QXtend to transfer data between QAD Enterprise Applications and QAD CRM for the following modules.
Address
Multiple Currency
Users
Prerequisites
Before integrating with QAD Enterprise Applications, verify that you have met the following prerequisites:
System requirements for QAD Enterprise Applications integration. See System Requirements.
QAD CRM databases are in multi-user mode.
Your QAD Enterprise Applications is functioning properly.
Your network is operating.
QAD Enterprise Applications databases are in multi-user mode.
You have access to QAD Enterprise Applications compiled programs (.r) and the xrc folder.
QXtend is installed and functioning properly.
Configuring QAD Enterprise Applications for Integration
1
Modify QAD Enterprise Applications parameter file (.pf) for connecting to the QAD CRM databases.
The following is an example of how you can modify the .pf file.
-db /QADERPInstallDir/db/testdb -ld qaddb -trig triggers
-db /QADERPInstallDir/db/helptest -ld qadhelp -trig triggers
-db /QADERPInstallDir/db/admintest -ld qadadm -trig triggers
-db /qadcrm/db/bisgen -ld bisgen -trig triggers
-db /qadcrm/db/bisgmenu -ld bisgmenu -trig triggers
-db /qadcrm/db/dataexch -ld dataexch -trig triggers
-h 8
-yy 1950
 
Normally, QAD Enterprise Applications uses the same .pf file for telnet, connmgr, AppServer broker, and WebSpeed broker. If this is not the case, you must modify all .pf files.
2
Modify QAD Enterprise Applications configuration settings (.ini) file, telnet, QAD Financials AppServer broker, QAD UI AppServer, WebSpeed broker, and connmgr to append the following directory locations in the PROPATH:
QADERPInstallDir/qadcrm/prod
QADERPInstallDir/qadcrm/prod/system
QADERPInstallDir/qadcrm/prod/dataexch
QADERPInstallDir/qadcrm/prod/progs
QADERPInstallDir/qadcrm/prod/report
QADERPInstallDir/qadcrm/prod/triggers
QADERPInstallDir/qadcrm/prod/integration/mfgpro
3
Modify server.xml under folder <QDT_install_directory> /envs/ <environment name> /configs to include QAD CRM database connection details as follows:
Note: Skip the following steps if you are integrating CRM with QAD 2009.1 EE or later releases.
4
If you are using QAD 2009 EE, back up the following program from the QADERPInstallDir /xrc directory:
 
ptw.t
Write trigger for the QAD Enterprise Applications pt_mstr table
5
Transfer the programs in step 4 from QADCRMInstallDir \integration\eb3 to QADERPInstallDir /xrc using an FTP or WinSCP program.
6
Compile the programs you copied using MFG/UTIL.
Note: If the programs are customized, contact your QAD Enterprise Applications supplier.
7
Copy the compiled file ptw.r from QADERPInstallDir /xrc to the directory QADERPInstallDir /triggers.
8
Modify the script file used by QAD Enterprise Applications Character Client to connect to the bisgen, bisgmenu, and dataexch databases and startup program:
exec $DLC/bin/_progres -rq
$MFGDB -ld qaddb -znotrim -trig triggers
-db $ADMDB -ld qadadm
-db $HLPDB -ld qadhelp
-db $QADSAMDB -ld bisgen -trig triggers
-db $EDATADB -ld dataexch -trig triggers
-db $EBMENUDB -ld bisgmenu -trig triggers
-cpstream iso8859-1 -cpinternal iso8859-1 -cpcoll basic
-Bt 350 -c 30 -D 100 -mmax 3000 -nb 200 -s 63
-E -d dmy -yy 1970 -T /ext1/mfgeB/mfgwork -h 8
-p mfbg.p