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 SE
QAD CRM uses database and session triggers to connect and update the databases of both systems, eliminating the need for manual intervention when transferring data between the two systems.
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 deployment servers of the QAD CRM and your QAD Enterprise Applications.
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.
Your QAD CRM databases are running 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.
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, connmgr, AppServer broker, and WebSpeed broker to add 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
Note: If you are using QAD 2008 SE or earlier, specify the srvrStartupProc parameter for the .NET UI as follows:
srvrStartupProc=mfaistrt.p
3
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 mf.p
 
If you are integrating CRM with QAD 2007.1 SE, then you need to replace “-p mf.p” with “-p mfbg.p” in the above file.
Performing Additional Steps For QAD 2007.1 SE
Additional Steps are to be performed for integrating QAD CRM with QAD 2007.1 SE Release. Skip the following steps if you are integrating CRM with QAD 2009 SE or later releases.
1
Back up the following programs from the QADERPInstallDir /xrc directory if available:
 
cmw.t
Write trigger for QAD Enterprise Applications cm_mstr table
ptw.t
Write trigger for QAD Enterprise Applications pt_mstr table
adw.t
Write trigger for QAD Enterprise Applications ad_mstr table
mfwb01a.p
Program for the integration
sopiwitt.i
Best Price routine
sopiwids.i
Best Price routine
sopiwapi.p
Best Price routine
2
Transfer the programs listed in the last step from QADCRMInstallDir \integration\eb21 to QADERPInstallDir /xrc using an FTP or WinSCP program.
3
Compile the programs you copied in the previous step using MFG/UTIL.
Note: If the programs are customized, contact your QAD Enterprise Applications supplier.
4
Copy the compiled files cmw.r, ptw.r, and adw.r from QADERPInstallDir \xrc to the directory QADERPInstallDir /triggers.
5
Copy mfwb01a.r from QADERPInstallDir \xrc to the directory QADERPInstallDir.
6
Copy sopiwapi.r from QADERPInstallDir \xrc to the directory QADERPInstallDir /us/so directory.
Performing Additional Steps For QAD 2008 SE
Additional Steps are to be performed for integrating QAD CRM with QAD 2008 SE Release. Skip the following steps if you are integrating CRM with QAD 2009 SE or later releases.
1
Back up the following programs from the QADERPInstallDir /xrc directory if available:
 
sopiwitt.i
Best Price routine
sopiwids.i
Best Price routine
sopiwapi.p
Best Price routine
2
Transfer the programs listed in Step 1 from QADCRMInstallDir \integration\eb21 to QADERPInstallDir \xrc using an FTP or WinSCP program.
3
Compile the sopiwapi.p program you copied in Step 1 using MFG/UTIL.
Note: If the programs are customized, contact your QAD Enterprise Applications supplier.
4
Copy sopiwapi.r from QADERPInstallDir \xrc to the directory QADERPInstallDir /us/so directory.
AIM Configuration
Do the following if AIM is configured with QAD Enterprise Application (SE):
1
Before configuring AIM, verify that you have met the following prerequisites:
System requirements for AIM in QAD Enterprise Applications integration section. See System Requirements.
2
Back up cpdtrig.p from the AIMInstallDir/xrc directory.
3
Transfer cpdtrig.p from QADCRMInstallDir \integration\eb21 to AIMInstallDir/xrc using an FTP or WinSCP program.
4
Compile cpdtrig.p.
Note: If the above program is customized, contact your QAD Enterprise Applications supplier.
5
Copy the compiled cpdtrig.r to the QAD Enterprise Applications environment, depending upon the AIM configuration.