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.com




Release Notes for Version 2.1.1
QAD Field Service Scheduler Version: 2.1.1
Date: November 2008
QAD Enterprise Applications Versions: QAD Enterprise Applications 2008.1 - Enterprise Edition (EE)/Standard Edition (SE)
Installation Changes
Setup is required for the .NET UI client. See “.NET Client Setup.”
If you are using QAD 2008.1 EE, you require a license code from QAD Support to unlock and use QAD FSS—no further setup is required.
If you are using QAD 2008.1 SE, complete the setup instructions described in “QAD Enterprise Applications 2008.1 – Standard Edition Setup.”
.NET Client Setup
1
Remove any existing qad.plugin.fss folder under:
< .NET UI HomeServer >/packages/plugins/.
2
This release contains two FSS client packages:
qad.plugin.fss-2.1.1.0-ee.zip for QAD 2008.1 EE
qad.plugin.fss-2.1.1.0-se.zip for QAD 2008.1 SE
Extract the appropriate .zip file into < .NET UI HomeServer >/packages/.
3
Update < .NET UI HomeServer >/packages/plugins/manifest.qpkg and add the following line to the end of the package element:
<package ref="${Repos}/plugins/qad.plugin.fss/manifest.qpkg"/>
The next time that clients connect to the .NET UI HomeServer, they will be prompted to load the new FSS plug-in.
Note: To use the mapping capabilities of FSS, you must install Microsoft MapPoint 2006 locally on each PC.
QAD Enterprise Applications 2008.1 Standard Edition Setup
QAD FSS version 2.1.1 is a bolt-on install to the server side and to the .NET UI plug-in.
1
Stop all AppServers, WebSpeed Brokers, and database servers; for example:
asbman –i qadui_AS –stop
wtbman –i qadui_WS –stop
stopProduction.bat or stop.Production
2
Copy the contents of the Server/2008.1se/ssm folder into a folder called ssmpatch under the < QAD ERP InstallDir > folder.
3
Copy the contents of the Server/2008.1se/fss folder into a folder called fsspatch under the < QAD ERP InstallDir > folder.
4
Run MFG/UTIL and choose Database|Load Data Definitions.
5
Connect to your main production database and enter
< QAD ERP InstallDir >/ssmpatch/db/ssm2008.1se.df as the data definition file.
6
Click OK to load the new schema.
7
Repeat the schema load for the main empty database.
8
Choose Database|Load System Data into Database.
9
Connect to your main production database and enter < QAD ERP InstallDir >/ssmpatch/data as the input directory.
10
Accept the selected tables and click OK to load the data.
11
Repeat the data load for the administration production database.
12
If you have additional languages, repeat the data load into your main production database using
< QAD ERP InstallDir >/ssmpatch/data/<lang> as the input directory.
13
Perform a full system recompile to make use of the new schema changes.
14
Choose Programs|Compile Procedures.
15
In the Compile List File field, enter < QAD ERP InstallDir >/ssmpatch/ssmcompile.lst.
16
Include < QAD ERP InstallDir >/ssmpatch/xrc at the beginning of the compile PROPATH and enter < QAD ERP InstallDir >/ssmpatch as the destination directory.
17
Click Compile to deploy the new programs. Answer Yes to any prompts, and then click Continue on the Summary screen.
18
Repeat Steps 14 through 17 in order to compile the fsspatch, replacing ssmpatch with fsspatch, and ssmcompile.lst with fsscompile.lst.
19
If you have additional languages, repeat the compile process using the appropriate QAD Enterprise Applications language and language-specific compile database set.
20
Copy the compiled triggers from < QAD ERP InstallDir >/ssmpatch/triggers to
< QAD ERP InstallDir >/triggers.
21
Edit the PROPATH in all client scripts so that < QAD ERP InstallDir >/ssmpatch is listed before < QAD ERP InstallDir >; for example:
CharacterclientProduction.bat
Production.ini (two instances)
connmgrProduction.bat
telnetProduction.bat
qadui.chr
22
Edit ubroker.properties for the qadui AppServer as follows:
The PROPATH should have <QAD ERP InstallDir>/ssmpatch listed before <QAD ERP InstallDir> and <QAD ERP InstallDir>/ssmpatch/qra.pl added to the end
Add srvrStartupProc=mfaistrt.p
Add srvrStartupProcParam=qra
23
Restart the database servers, AppServers, and WebSpeed brokers.
startProduction.bat or start.Production
asbman -i qadui_AS -start
wtbman -i qadui_WS -start
24
Run the program < QAD ERP InstallDir >/ssmpatch/xrc/utssmse.p from a Progress editor that is connected to the main production database.
25
Launch QAD Enterprise Applications 2008.1 and select menu 36.4.19 – Field Help Load. Enter US as the language and < QAD ERP InstallDir >/ssmpatch/data/fieldhld.fhd as the Field Help Load File. Accept all other defaults and click Go to load the new help data.
26
Run Menu System Maintenance from the .NET UI and click the Refresh button to install the new menu options for SSM.
Application Changes