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

  • Installation and Configuration Information
    The following summarizes installation and configuration changes for this version of the QAD .NET UI.
    Cumulative Patch Information
    Important: Before installing the QAD .NET UI, be sure to go to the QAD Store ( ) to check for the most recent version of QAD .NET UI 2.9.6 for QAD Enterprise Applications – Standard Edition 2012 and 2013.
    Release Summary
    QAD .NET UI Version:
    Product Versions: QAD Enterprise Applications 2012 and 2013 – Standard Edition
    Microsoft .NET Framework Version: 3.5 SP1
    Tomcat Versions: 5.5.x and 6.0.x. If you are upgrading and have already installed Tomcat 5.5.x, you do not need to upgrade to Tomcat 6. Tomcat 5.5.x is fully supported for use with this version of the QAD .NET UI.
    Operating System: The QAD .NET UI client runs on Windows XP, Windows 7, and Windows 8. It can run on 64-bit Windows, but only in 32-bit mode.
    Progress Version: OpenEdge 10.2B is required.
    Note: If upgrading from a previous version, be sure to review the release notes for the versions between your current version and this version.
    For information on the QAD .NET UI release history, see the Platform and Product Availability Guide, available from the General Reference section of the QAD support site ( ).
    Progress 10.2B Required
    This version of the QAD NET UI requires Progress OpenEdge 10.2B.
    Supported Languages
    The user interface supports the following languages in this release:
    Chinese (Simplified)
    English (US)
    Portuguese (Brazilian)
    Chinese (Traditional)
    Spanish (Castilian)
    Spanish (Latin American)
    The following languages have some support, but new terms added in this release may appear in English:
    ADMIN Database Update Required for 2012 SE
    Note: This database update is required only if you are installing QAD .NET UI 2.9.6 for the first time on a 2012 SE system. If you previously installed QAD .NET UI 2.9.6 ( on your 2012 SE system, you do not need to do this database update again when installing QAD .NET UI on 2012 SE.
    Before installing the QAD .NET UI for use with 2012 SE, update the ADMIN database as follows:
    Use the files in $CDIMAGE/system/schema to update the database.
    Connect to the ADMIN database via Progress.
    Run the utunfrz.p program (load it into the procedure editor and execute). This unfreezes the schema for the next step.
    Load the definition file ui_adm.df.
    After loading the schema, freeze the schema by running the utfrz.p program.
    After installing the QAD .NET UI, do the following:
    Launch the QAD .NET UI client.
    Load three browse definitions included in $CDIMAGE/system/browse:
    Open Browse Maintenance Import.
    Select the Overwrite Existing check box.
    Load the following three browse definitions:
    Favorites Storage and Automatic Migration
    Previously, when upgrading to a new release of the QAD .NET UI, saved Favorites were not migrated automatically. Starting with QAD .NET UI 2.9.6, Favorites have now been enhanced so that:
    All Favorites are now stored on the home server (in a UserMenu.xml file) rather than locally.
    All Favorites, including menus, commands, browses, and operational metrics, are saved as QAD Shell URL (qadsh://) links.
    Configuration settings can be referenced in qadsh:// parameters.
    All favorites, starting with QAD .NET UI 2.7.1, are automatically migrated to the new format.
    During migration, favorites previously stored locally (in the UserMenu.dat file) are converted to the UserMenu.xml file, which is stored on the home server. For backup, converted files are saved as .bak files.
    Process Maps Installation
    Starting with QAD Enterprise Applications 2012 – Standard Edition, the process maps for Standard Edition have been redesigned to include the following:
    New Color Scheme — The new color scheme has designated colors for all the supply chain processes.
    Enhanced Navigation — The navigation structure was flattened, and the process map footer makes navigation from map to map easier.
    Updated Vertical Maps — The new version features eight updated vertical maps with more granularity than ever before.
    New End-to-End Maps — The high-level end-to-end maps Quote to Cash, Procure-to-Pay, and Plan to Perform were added.
    Improved Supply Chain Process View — The supply chain process view was enhanced with the new categories Design, Enable, and Engage.
    Linkage to the Document Library — Each node allows you to search the QAD Document Library with a click of a button to find relevant user guides, installation guides, or training guides.
    The new, redesigned process maps are not included with the QAD .NET UI release media. Please visit the QAD Store to download the latest package.
    Process Maps and Internet Explorer
    Note the following when editing and viewing process maps in Internet Explorer:
    With Internet Explorer 8 and 9, Print Preview is not supported for process maps and they do not print correctly.
    By default, the Process Viewer uses Silverlight rather than SVG.
    The Process Editor uses SVG.
    Important: Internet Explorer 8 and 9 do not include the Adobe SVG plug-in, which is required for using the QAD .NET UI’s Process Editor. If using Internet Explorer 8 or 9, you must install the SVG plug-in. If you have not installed the SVG plug-in on your local machine, the Process Editor will display an error message when you try to edit a process map.
    QAD includes the SVG plugin with QAD .NET UI in the client directory on the home server (in HomeServerURL /client/SVGView.exe) and includes it with the QAD .NET UI client when the client is installed. For example, you can find it here:
    C:\Program Files (x86)\QAD\QAD Enterprise Applications\SVGView.exe
    After installing SVG, restart the QAD .NET UI and open the Process Editor. After a moment, it will prompt you to verify the use of SVG, and then you can proceed to use the Process Editor.
    Internet Explorer and QAD .NET UI Client Installation
    Warning The 64-bit version of Internet Explorer will not install the QAD .NET UI client, even if you are running Internet Explorer as an administrator. You must use the 32-bit version of Internet Explorer (typically located in C:\Program Files (x86)\Internet Explorer\iexplore.exe) to install the QAD .NET UI client. A situation in which this is likely to occur is when a user inadvertently creates a shortcut to the 64-bit version of Internet Explorer rather than the 32-bit version, and then uses that shortcut to launch Internet Explorer.
    QAD Document Library Access
    The QAD Document Library ( ) offers a complete set of all QAD user guides, training guides, and other materials.
    With all the user guides now available in the QAD Document Library, QAD Assist now includes a link to the QAD Document Library and only includes the program and field help as content.
    QAD Assist Installation
    QAD Assist is a QAD .NET UI application that hosts HTML versions of the QAD Enterprise Applications online help for programs and fields. With QAD Assist, you can search the online help to quickly find more information.
    QAD Assist must be installed manually after the QAD .NET UI has been installed. (Note that if you are updating the QAD .NET UI on your system where the QAD Assist has already been installed, you do not need to install it again.) The installation steps for QAD Enterprise Applications – Standard Edition are as follows.
    File Delivery
    The installation files include:
    Files for installing the QAD Assist application
    Files for installing the QAD Assist content
    The QAD Assist application and content files are included in the QAD Enterprise Applications – Standard Edition Language CD for each supported language.
    The application files are:
    The content files are named as follows:
    where <product> is erp for QAD Enterprise Applications.
    For example, the English file for QAD Enterprise Applications help is:
    Installation Steps
    Use the following steps to install QAD Assist. (Note that the steps are based on using a Linux environment with JDK 1.6.)
    Shut down Tomcat.
    Copy epub.war and search.war into the /webapps directory.
    Start Tomcat. With the application files in place, you next copy and unzip the content files.
    Copy <product>-<language> to the /webapps/epub directory.
    For each .zip you have copied, unzip the content using the unzip command:
    unzip <product>-<language>
    Unzipping creates a directory containing the content under the /epub directory. After you have unzipped the content, set up the search engine index.
    Using a web browser, access the search administration page URL. Open http://<host>:<port>/search, where <host> and <port> are the host and port for the Tomcat instance under which you installed the epub and search Web applications.
    Click the New Index button and in the field enter:
    This creates a new index and directory in the following location:
    Next, you need to add index (links) content to the search engine by copying the links_*.xml files (which contain the default link information for the search engine index) under /epub to /search/WEBINF/indexes/default.
    You can use the following step to copy all the index files (files that match 'links-*.xml') into the directory.
    Using a command line, navigate to the /epub directory and enter:
    cp `find . -name "links-*.xml"` ../search/WEB-INF/indexes/default
    The search engine automatically imports these files and removes them upon completion.
    The search administration page (http://<host>:<port>/search) updates the information about the default index, including the number of documents in the Documents column and the total size under the Size column.
    Note that you can import the same content multiple times without affecting the number of documents loaded into the search engine, although that action will increase the allocated file size. In the Actions column, you can click Optimize to reclaim the excess disk space.
    To load the default index, you must stop and start the search engine for that index:
    In the Actions column for default, click Stop.
    In the Actions column for default, click Start.
    Finally, you need to update the client-session.xml file.
    Edit the client-session.xml file (<HomeServer>/configurations/<SysEnvName>/client-session.xml) so that it includes the following settings:
    QAD Assist is now ready for use. You can access it from the QAD .NET UI by choosing Help|Search or by pressing the F1 key.
    Note: If the search engine does not automatically load the index files, bounce (stop and then start) Tomcat. To do so, go to the /bin directory and enter ./ and then ./
    Reporting Framework Sample Reports
    When upgrading from a version of the QAD .NET UI prior to version 2.9.4, where the Reporting Framework included six sample reports, note that the six reports have been removed in the newer versions. If you keep the previous menu system data, and the AppServer has the upgraded version without the .p programs (proxies) for the sample reports, you get an error when you launch the reports from the menu. If you no longer need these reports, you can delete them from the menu system using Menu System Maintenance. If you would like to continue to use these sample reports, you can copy the six proxy programs from your previous system to the new system and compile them. Alternatively, delete them from the menu system, and then install the six sample reports included on the Reporting Framework Source CD, following the instructions included with the CD.
    QAD Reporting Framework Service Installation
    You should install and configure the QAD Reporting Framework Service on one or more Windows machines. This service continuously monitors a special report batch (QADSVC) for reports to be run immediately on the server. This service is necessary for several uses including report bursting and report integration with some maintenance programs. See the Service Mode section in chapter 6 (Administering Reports) of the Reporting Framework User Guide for more information.