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




Configuring Application Server
You must prepare the AppServer environment which is required for the QAD CRM 6.5.1 product.
To prepare the AppServer environment:
1
Define QAD CRM AppServer broker in the ubroker.properties file. Use the Progress $DLC /bin/genuuid utility to generate a new unique UUID for the new Progress AppServer definition.
2
Create the AppServer broker .pf file using the QADCRMInstalldir /qadcrmparam_as.pf as a template to connect to the QAD CRM databases.
Note: Do not remove any predefined parameters in your . pf file. If Progress database server and AppServer are installed on same machine, do not connect the databases using the client-server mode (-H -S parameters) in your pf file and start the databases as self-service clients.
3
Specify following startup parameters for the AppServer broker:
a
Specify the srvrStartupParam parameter:
srvrStartupParam=-pf <AppServer broker .pf file with full path>
Note: If you are using a Unicode database, make sure that the Appserver Broker pf file contains the following Unicode parameters:
-cpinternal UTF-8
-cpstream UTF-8
-cpcoll ICU-UCA
-cpcase Basic
b
Specify the srvrStartupProc parameter:
srvrStartupProc=QADERPInstallDir /qadcrm/prod/progs/pappsistart.p
4
Modify the PROPATH parameters of the AppServer brokers. Put QAD CRM directories in the PROPATH; for example, put the following folders in the PROPATH:
qadcrm\prod\system
qadcrm\prod\integration\mfgpro
qadcrm\prod\dataexch
qadcrm\prod\progs
qadcrm\prod\report
qadcrm\prod\triggers
5
Start the AppServer broker using the following command:
ProgressInstallDir/bin/asbman -name <broker name> -start
6
To start the AppServer automatically, modify the QAD-supplied startup batch files.
Performing Additional Configurations for Integration with QAD Enterprise Applications
In case QAD CRM is integrated with QAD Enterprise Applications (SE or EE), you must perform additional configurations for the application server.
QAD CRM Integrated with QAD SE
1
Modify the AppServer broker .pf file to connect to the QAD SE databases and qxevents databases instead of the QAD CRM databases. The qaddb should be the first database in the .pf file.
2
Use the trigger option and specify the trigger location for QAD Enterprise Applications databases and qxevents database:
-trig triggers
3
Modify the PROPATH to add QAD SE directories before QAD CRM directories.
QAD CRM Integrated with QAD EE
1
Modify the AppServer broker .pf file to connect to the QAD SE databases and qxevents databases instead of the QAD CRM databases. The qaddb should be the first database in the .pf file.
2
Use the trigger option and specify the trigger location for QAD Enterprise Applications databases and qxevents database:
-trig triggers
3
Modify the PROPATH of the AppServer brokers:
Add QADERPInstallDir /prod/integration/mfgpro as the first line
Add QAD EE directories before QAD CRM directories
For example, the modified PROPATH looks something like this:
QADERPInstallDir/qadcrm/prod/integration/mfgpro
SSMPatchInstallDir/
QXtendInstallDir/
QXOInstallDir/
QADERPDesktopInstallDir/com/mfgpro
QADERPDesktopInstallDir/
QADERPInstallDir/
QADERPInstallDir/us/bbi
QADERPInstallDir/us
QADERPInstallDir/us/sq
QADERPInstallDir/us/tx
QADERPInstallDir/config
QADERPInstallDir/qra/qra.pl
QADERPInstallDir/fin/proxy.pl
QADERPInstallDir/fin/proxy
QADERPInstallDir/qadcrm/prod
QADERPInstallDir/qadcrm/prod/dataexch
QADERPInstallDir/qadcrm/prod/progs
QADERPInstallDir/qadcrm/prod/system
QADERPInstallDir/qadcrm/prod/triggers
QADERPInstallDir/qadcrm/prod/report
Note: Include SSMPatchInstallDir if SSM patch is installed.
4
Start the AppServer broker using the following command:
ProgressInstallDir/bin/asbman -name <broker name> -start
Maintaining and Validating QAD CRM AppServer Information
Perform the following steps on the CRM Deployment Server:
1
From QAD CRM Deployment Utility screen, click the Maintain QAD CRM AppServer Information button.
2
In the Service Parameter Maintenance window, configure appropriate parameter values.
Host (-H)
Enter the host name or IP address of the NameServer that provides the AppServer connection.
Service (-S)
Enter the service name or port number of the NameServer that provides the AppServer connection.
Application Service
Enter the name of a valid AppServer application service supported by the NameServer. The NameServer chooses an AppServer that supports this application service for the partition connection.
AppServer URL
Specify the URL for connecting to AppServer; for example, coli45 is the name of the host and 41580 is the broker port number through which to connect to the AppServer.
Note: It is advisable that you use the DirectConnect method to connect to the AppServer through a URL similar to the AppServer URL as shown in the screenshot.
Configuration
Choose Remote to connect to an AppServer using the connection information specified for this partition.
3
Save your changes and exit the Progress session completely.
4
Run the QAD CRM Deployment Utility and click the Validate QAD CRM AppServer Information button.
5
In the AppServer Session Information window, click the Get Info button and make sure that the AppServer connection information such as PROPATH and databases information is correct as per your CRM environment configuration.
If the connection is successful, you will see a connection string in the connection Id fill-in beginning with the Host IP address that hosts the appserver.
6
Once again, execute all the steps under the section “Splitting UI and Backend Programs on the Deployment Server” in order to generate the correct content for the file appsrvtt.d, which is used by the front end programs to connect to the QAD Progress Application Server.
Generating and Copying QAD CRM WebClient Files
After you install QAD CRM, you can find the QAD CRM WebClient project file qadcrm.wcp in QADCRMInstallDir \webclient\frontend. You can tailor some settings in this file based on your system configuration.
1
Run the QAD CRM Deployment Utility and click the Generate QAD CRM Webclient Files button.
2
From the File menu, select Open to locate and open the file qadcrm.wcp in the QADCRMInstallDir \webclient\frontend directory.
3
In the WebClient project file window, enter values in the fields based on your deployment configurations.
Configuration File URL
Enter the configuration file URL according to your CRM setup on the (Tomcat) delivery server.
Application Root Dir
Enter QADCRMInstallDir \webclient\frontend.
Acceptable Version(s)
Click the Versions button and in the window that appears, clear the Acceptable to run option for the current version; then select 6.5b13 and click the Remove button. Click OK to return to the General tab. The Acceptable Version(s) field should now be blank.
4
Under the Component tab, click the Locator button and modify the URL of your codebase as per your configuration. Click OK to Save your changes.
5
Under the WebClient tab, modify the WebClient Install URL as per your configuration.
6
Click the Save button on the toolbar to save the project.
7
From the Deployment menu, select Generate.
8
In the Generate QADCRM window, click the Security button and select the digital signature files; then click OK. Relevant files for a particular environment are available in QADCRMInstallDir \bin.
9
Select Deploytment|Generate from the menu and make sure all the settings in the Generate QADCRM window are configured correctly.
New Version
You must select this option.
Version Name
Current version name is set to 6.5b13.
Output Directory
Specify the output directory based on your CRM installation directory.
Version Directory
This field is automatically populated once you specify the output directory.
10
Click OK to generate the cab files.
In the process of cab files generation, the system prompts you to enter a password for each component cab file to be created. In the password prompt, enter qadcrm and click OK.
In case of errors, the cab files generation process is aborted and errors are recorded in the log file. Refer to the log file for error details, if any; then rectify any problems and generate the files again.
11
When cab files generation is complete, WebClient files are created in the QADCRMInstallDir \webclient\frontend\ CRMVersion directory.
12
You need to copy the .cab files generated for QAD CRM earlier during the step: splitting of user interface and backend programs on Deployment Server. Refer to QADCRMInstallDir \webclient\frontend\6.5b13\qadcrm.log for the files that needs to be copied from the CRM Deployment Server to Delivery Server (where Tomcat is installed). For example, you will copy files such as the following:
QADCRMInstallDir\webclient\frontend\6.5b13qadcrm.prowcapc to TomcatInstallDir/webapps /qadcrmwebclient/qadcrm
QADCRMInstallDir\webclient\frontend\6.5b13qadcrm.cab to TomcatInstallDir/webapps /qadcrmwebclient/qadcrm/6.5b13