Customer Relationship Management 6.7.3 > Install Guide > Upgrade > Upgrading QAD CRM 6.7.2 to CRM 6.7.3 > Normal Installation
  
Normal Installation
Follow the instructions in Configuring the Delivery Server.
Note: Rename the qadcrmwebclient.war file; for example, qadcrmwebclient673.war. In this way, when you copy this .war file to the Tomcat webapps folder, it can be extracted to a different webapps folder other than the one that the existing CRM 6.7.2 system uses.
Splitting UI and Backend Programs on the Deployment Server
Follow the instructions in Splitting and Compiling UI and Backend QAD CRM Programs.
Copying QAD Backend Programs on the Application Server
Follow the instructions in Copying QAD Backend Programs on the Application Server with the following notes:
• Since you already have a CRM 6.7.2 system integrated with QAD EA, make sure that you create a folder under QADERPInstallDir/qadcrm/<New CRM6.7.3 env name> for CRM 6.7.3 program files that need to be stored in the backend Application Server; for example, QADERPInstallDir/qadcrm/qad673test.
• Copy the backend program source files from the Windows Deployment server to the AppServer machine and recompile them against your newly converted CRM 6.7.3 database.
Configuring Application Server
Follow the instructions in Configuring Application Server with the following notes:
• Back up your existing ubroker.properties file before you change it.
• It is recommended that you define a new entry in the ubroker.properties file rather than updating the existing CRM 6.7.2 entry. You can always remove the existing CRM 6.7.2 AppServer later after your CRM 6.7.3 system is confirmed to be working.
• When defining the PROPATH for your AppServer, make sure that you refer to the correct QADERPInstallDir/qadcrm/ folder that you created in an earlier upgrade step in Copying QAD Backend Programs on the Application Server.
Performing Additional Configurations for Integration with QAD EA
Follow the instructions in Performing Additional Configurations for Integration with QAD Enterprise Applications.
Maintaining and Validating QAD CRM AppServer Information
Follow the instructions in Maintaining and Validating QAD CRM AppServer Information. These steps generate the AppServer configuration file needed by the QAD CRM Webclient (*.cab) files that are generated in the next step.
Generating and Copying QAD CRM WebClient Files
Follow the instructions in Generating and Copying QAD CRM WebClient Files.
Integrating with QAD SE
If you need to integrate CRM 6.7.3 with your QAD SE system, implement the steps in the following sections:
• Integrating QAD CRM with QAD SE
• Configuring the Environment for Sales Order Integration
Note:  
• When you define the PROPATH in the configuration files, make sure that you refer to the correct QADERPInstallDir/qadcrm/ folder that you created earlier in Copying QAD Backend Programs on the Application Server.
• Ensure that you update the PROPATH of all configuration files that are used to reference the old CRM 6.7.2 programs. The PROPATH includes the PROPATH setting used by the .NET Connection Manager pool startup script, the PROPATH setting defined in the Progress ubroker.properties file for the QADUI AppServer, and so on. Update of the PROPATH ensures that all elements point to the new CRM 6.7.3 programs that you have installed.
Integrating with QAD EE
To integrate CRM 6.7.3 with your QAD EE system, implement the steps in the following sections:
• Integrating QAD CRM with QAD EE.
• Configuring the Environment for Sales Order Integration.
Go to QXtend Inbound and update the Connection Pool ee-crm.SIAPI to use the CRM 6.7.3 AppServer. It is unnecessary to reimplement all the steps in Configuring QXtend for Integration.
Note:  
• When you define the PROPATH in configuration files, make sure that you refer to the correct QADERPInstallDir/qadcrm/ folder that you created earlier in Copying QAD Backend Programs on the Application Server.
• Ensure that you update the PROPATH of all configuration files that are used to reference the old CRM 6.7.2 programs. The PROPATH includes the PROPATH setting used by the .NET Connection Manager pool startup script, the PROPATH setting defined in the Progress ubroker.properties file for the QADUI AppServer, and so on. Update of the PROPATH ensures that all elements point to the new CRM 6.7.3 programs that you have installed.
Updating the AppServer Name Defined in QAD CRM
The name of the AppServer is referenced in the QAD CRM Application itself to enable CRM and ERP integration. Update the AppServer name to reflect the name of the new AppServer you have set up for the CRM 6.7.3 system.
In QAD CRM, go to Main Menu|Settings|System|AppServer Service Maintenance and define the CRM 6.7.3 AppServer. Follow the instructions in the “AppServer Service Maintenance” section in QAD Customer Relationship Management Administration Guide.
When the AppServer Service record has been created, go to Main Menu|QAD ERP Integration|ERP Management Control to update the QAD CRM Service Name field with the name of the new CRM 6.7.3 AppServer.
If you have set up QAD AdminService in your CRM system, it is necessary to update all references to CRM 6.7.3 AppServer by following the instructions in the “Configuring AppServer Settings” section in QAD Customer Relationship Management Administration Guide.