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  |   Cloud ERP  |   Home  |

  •     QAD Glossary

  • Release Notes for Version 2.2
    QAD Field Service Scheduler Version: 2.2
    Date: April 2009
    QAD Enterprise Applications Versions: eB2.1 SP4
    Installation Changes
    Setup is required for the .NET UI client. See “.NET Client Setup.”
    Install eB2.1 SP4 per standard MFG/UTIL procedure.
    Install .NET UI 2.5.3 per standard procedure.
    QAD Enterprise Applications
    If also installing MFS 2.2, use the steps in Technical Reference: MFS 2.2 to update the ERP server and then skip to “.NET Client Setup” below.
    Stop all Tomcat Webapps, AppServers, WebSpeed brokers and database servers.
    Copy the contents of \Server\SSM\eb21sp4 from the media into a folder called
    < QAD ERP InstallDir >\ssmpatch.
    Run MFG/UTIL and choose Database|Load Data Definitions.
    Connect to your main production db and load
    < QAD ERP InstallDir >\ssmpatch\db\ssmpatch.df as the data definition file.
    Repeat the schema load for the main empty db.
    Choose Database|Load System Data into Database.
    Connect to your main production db and load < QAD ERP InstallDir >\ssmpatch\data as the input directory, accepting the selected tables.
    Repeat the data load for the administration production db.
    If you have additional languages, repeat the data load into your main production db using
    < QAD ERP InstallDir >\ssmpatch\data\< lang > as the input directory.
    Perform a full system recompile.
    Choose Programs|Compile Procedures.
    Enter < QAD ERP InstallDir >\ssmpatch\ssmcompile.lst for the Compile List File. The Compile Propath should include the < QAD ERP InstallDir >\ssmpatch\xrc directory prior to the < QAD ERP InstallDir >\xrc directory. The destination directory should be
    < QAD ERP InstallDir >\ssmpatch.
    If you have additional languages, repeat the compile process using the appropriate QAD Enterprise Applications language and language-specific compile database set.
    Copy the compile triggers from < QAD ERP InstallDir >\ssmpatch\triggers to
    < QAD ERP InstallDir >\triggers.
    Choose UI|Build UI Configuration in MFG/UTIL and include
    < QAD ERP InstallDir >\ssmpatch\xrc in the Propath prior to < QAD ERP InstallDir >\xrc.
    Edit the Propath in all client scripts so that < QAD ERP InstallDir >\ssmpatch is listed before
    < QAD ERP InstallDir >.
    Edit for the qadui AppServer so that < QAD ERP InstallDir >\ssmpatch is listed before < QAD ERP InstallDir > and < QAD ERP InstallDir >\ssmpatch\ are added to the end.
    Add srvrStartupProc=mfaistrt.p and srvrStartupProcParam=qra to the qadui AppServer.
    Restart all database servers, WebSpeed brokers, AppServers, and Tomcat Webapps.
    Run the program < QAD ERP InstallDir >\ssmpatch\xrc\utssmse.p from a Progress editor that is connected to the main production db.
    Launch QAD Enterprise Applications and select Field Help Load (36.4.19). Enter US as the language and < QAD ERP InstallDir >\ssmpatch\data\fieldhlp.fhd as the Field Help Load File.
    If using .NET UI, run Menu System Maintenance for the .NET UI and click the Refresh button to install the new menu options for SSM.
    .NET Client Setup
    FSS must be installed locally onto each client that will need to run the application from the QAD .NET user interface. To do this, extract \Client\ into the plugins folder of your QAD .NET UI client installation. Your QAD .NET UI client installation is typically found in C:\Program Files\QAD.
    Note: To use the mapping capabilities of FSS, you also must install Microsoft MapPoint 2009 locally on each client PC.
    Application Changes
    FSS 2.2 now integrates with an optional installation of Microsoft MapPoint 2009. Previously, mapping capabilities were only available via MapPoint 2006. With FSS 2.2, mapping capabilities require the installation of MapPoint 2009 on each FSS client.