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




Installation and Configuration Information
The following summarizes installation and configuration changes for this version of the QAD .NET UI.
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 ( http://support.qad.com ).
The QAD Document Library ( http://www.qad.com/documentlibrary/ ) offers a complete set of all QAD user guides, training guides, and other materials.
Note: If upgrading from a previous version, be sure to review the release notes for the versions between your current version and this version.
Cumulative Patch Information
Important: Before installing the QAD .NET UI 2013, be sure to go to the QAD Store ( http://store.qad.com ) to check for the latest cumulative patch to QAD .NET UI 2013.1. You must install the patch after installing the QAD .NET UI.
Release Summary
QAD .NET UI Version: 2013.1 EE (3.0.1)
Product Versions: QAD Enterprise Applications 2013.1 – Enterprise Edition
Microsoft .NET Framework Version: 4
Microsoft .NET Framework 4 must be installed on client machines. You can download and install it from the Microsoft Download Center ( http://www.microsoft.com/en-us/download/details.aspx?id=17851 ).
Tomcat Versions: 5.5.x, 6.0.x, and 7.0.x.
Operating System: The QAD .NET UI client runs on Windows XP SP3, Windows Vista, Windows 7, and Windows 8 (Desktop Mode). The QAD .NET UI can run on 64-bit Windows, but only in 32-bit mode.
Microsoft Internet Explorer Version: 9 or higher. If running Windows XP SP3, you can use Internet Explorer 8, but see HTML5 Process Maps and Internet Explorer.
The Connection Manager SSH implementation uses the jSch component by JCraft, Inc., distributed in accordance with the license agreement ( http://www.jcraft.com/jsch/LICENSE.txt ).
Supported Languages
The user interface supports the following languages in this release:
 
Chinese (Simplified)
English (US)
Italian
Portuguese (Brazilian)
Chinese (Traditional)
French
Japanese
Spanish (Castilian)
Dutch
German
Polish
Spanish (Latin American)
The following languages have some support, but new terms added in this release may appear in English:
 
Bulgarian
Greek
Norwegian
Slovenia
Czech
Hungarian
Romanian
Swedish
Danish
Korean
Russian
Turkish
Finnish
Lithuanian
Slovak
Ukrainian
Georgia SoftWorks Windows SSH or Telnet Server Installation
The QAD .NET UI uses an SSH or telnet server for two purposes:
On the database server, it is used to run a pool of sessions that support maintenance programs, reports, and inquiries.
It enables the client terminal interface for programs that only run in terminal mode (see Programs in Terminal Mode Only) as well as any custom programs that do not conform to QAD programming standards.
As of the QAD .NET UI 2013 release, the QAD .NET UI now supports secure shell (SSH) as well as telnet. You can use either SSH or telnet; the default is now to use SSH. Typically, the SSH or telnet server runs on a UNIX (or Linux) machine. If you plan to use a UNIX machine for the SSH server, QAD recommends using the SSH daemon, which comes standard on all UNIX distributions. If you plan to use a UNIX machine for the telnet server, you can use the default telnet service provided with the operating system.
If you want to run the SSH or telnet server on a Windows machine rather than a UNIX (or Linux) machine, use the Georgia SoftWorks (GSW) SSH Server or Telnet Server. This software is not included on the QAD .NET UI installation media: you must download the latest version of the software to obtain the most recent patches and functionality from Georgia SoftWorks:
For the Georgia SoftWorks SSH Server, see:
For the Georgia SoftWorks Telnet Server, see:
Refer to the Georgia SoftWorks documentation for installation information as well as software and system sizing requirements.
The Georgia Softworks Power Features pack provides a session monitor, which is helpful for troubleshooting connection issues.
Registering the Georgia SoftWorks Software
To register the software, you provide a product ID to Georgia SoftWorks so that a serial number can be generated for your product. The serial number identifies server hardware and software components. If these components change or are upgraded, contact Georgia SoftWorks about generating a new product ID and serial number.
Important: If you need to reinstall or are planning to move your installation to a different platform, or if you are a sales agent or a distributor, include that information on the registration.
1
Select the Registration icon from the program group in the Start menu.
2
In the Georgia SoftWorks Product Registration window, enter your customer information. The information that displays in the Product Information section is system-generated.
3
Set Sessions Requested to 100. This is the number QAD automatically supplies with your registration.
4
Choose Save to File to save this information, or choose Print. Then, follow the appropriate step to supply the product ID to Georgia SoftWorks:
a
E-mail the saved registration form file to Georgia SoftWorks at:
registration@georgiasoftworks.com
When your form is received, a serial number is generated for your product and is returned to you by e-mail.
b
FAX the printed registration form to Georgia SoftWorks at 706-265-1020. When your form is received, a serial number is generated for your product and is returned to you by FAX.
When you receive your serial number, return to the Georgia SoftWorks Product Registration window and enter it in the appropriate field in the registration form. Click Register.
Tomcat Configuration
As part of the software prerequisites for installing QAD Enterprise Edition, you must install the Tomcat web server in the $CATALINA_HOME directory as described in the QAD Enterprise Applications – Enterprise Edition Installation Guide.
Note: When you install Tomcat, be sure to update the tomcat-users.xml file in the /conf directory to include user, password, and role settings for the admin and pronav users. For example:
<?xml version='1.0' encoding='utf-8'?>
<tomcat-users>
<user name="tomcat" password="tomcat" roles="tomcat" />
<user name="role1" password="tomcat" roles="role1" />
<user name="both" password="tomcat" roles="tomcat,role1" />
<user name="admin" password="mfgpro" roles="qadadmin,manager,manager-gui,admin,pronav" />
<user name="pronav" password="editor" roles="pronav" />
</tomcat-users>
Process Maps Installation
The process maps are delivered separately from the QAD .NET UI. The process maps for QAD Enterprise Applications 2013.1 – Enterprise Edition are included with the QAD 2013.1 EE release media and are available on the QAD Store (http://store.qad.com ). The QAD Deployment Toolkit (QDT) installs the process map components (including the viewer and editor) along with the process map content as part of the overall installation process for the product. However, you should then get the latest process map content for QAD 2013.1 EE from the QAD Store.
Process Map Configuration Settings
QDT installs the process map viewer, editor, and related components on the home server as a stand-alone web application named pronav (tomcat/webapps/pronav). The following settings in the client session configuration file (client-session.xml) specify the default configuration:
 
<!-- Process map settings -->
<ProcessMapBaseUrl>${DesktopProtocol}://${DesktopHost}:${DesktopPort}/pronav</ProcessMapBaseUrl>
<qad.url.process.editor>${ProcessMapBaseUrl}/ProcessEditor.jsp</qad.url.process.editor>
<qad.url.process.viewer>${ProcessMapBaseUrl}/ProcessViewer.jsp</qad.url.process.viewer>
Previously, the process viewer and editor were in /tomcat/webapps/ <environment> and the process map content was in /tomcat/webapps/ <environment> /WEB-INF/pronav.
Now process maps are included in an environment named pronav (/tomcat/webapps/pronav) by default. A benefit of this approach is that you can now define a single process map installation that can be shared across multiple environments.
Note: The configuration setting for the process map images (QAD_IMG), set in Administration > Process Admin, now requires a fully qualified domain name. The settings now include a QAD_PMAP_ROOT setting to specify the URL to the process map installation (http:// server . domain .com: port /pronav/) and then the QAD_IMG setting is {QAD_PMAP_ROOT}images/.
HTML5 Process Maps and Internet Explorer
The Process Viewer and Process Editor have been updated to support HTML5.
Computers running the QAD .NET UI 2013.1 EE client should be upgraded to use the most recent version of Internet Explorer available for the version of Windows.
For instance, if running Windows 7 or Windows Vista, you should have Internet Explorer 9, which supports HTML5.
If running Windows XP SP3, be sure to upgrade to Internet Explorer 8. (Internet Explorer 9 is not supported on Windows XP.)
Note: With Internet Explorer 8, the Process Editor will not work properly when opened inside the QAD .NET UI because Internet Explorer 8 does not support HTML5.
If you want to edit process maps and are running Windows XP SP3 with Internet Explorer 8, a workaround is to install a different browser that supports HTML5 such as Chrome or Firefox, and then access the Process Editor as a stand-alone web application based on where it is installed.
You can identify the URL for the Process Editor by choosing Help | View Configuration and searching for “process” to find the URLs for both the Process Editor and Process Viewer. The Process Editor URL will typically have the format http:// server.domain.com: port /pronav/ProcessEditor.jsp. Enter this URL in the browser that supports HTML5.
Easy On Boarding and Integrated Customization Toolkit Process Maps
Process maps now include additional maps for Easy On Boarding (EOB) and the Integrated Customization Toolkit (ICT).
Easy On Boarding, available as a QAD Services engagement, simplifies the implementation process by populating most standard data and configuring standard processes. Companies can adjust both data and processes later, but the process streamlines the implementation tasks. For more information about Easy On Boarding, please contact QAD Services.
The Easy On Boarding process maps are organized into industry verticals including Automotive, Life Sciences, Industrial, Electrical, Consumer Products, and Food and Beverage. Nodes on the maps include links to Easy On Boarding training, documentation, and other attachments that are provided during a QAD Services engagement.
You can only access the Easy On Boarding attachments if you have a QAD Services engagement for QAD Easy On Boarding.
Note: The location of the Easy On Boarding attachments is specified by the Attachments setting on the Administration | Process Admin — Process Properties screen. If you do not have a QAD Services engagement and you try to access the attachments from a process map node, you will get a “file not found” error message. However, if you set Attachments to ProcessViewer.jsp?ProcessName=eob_attachments&f=, a process map displays instead that lets you know you can only access the attachments if you have a QAD Services engagement.
Internet Explorer and QAD .NET UI Client Installation
Warning The 64-bit version of Internet Explorer does 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.
Reporting Framework Sample Reports
When upgrading from a version of the QAD .NET UI earlier than 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, which is available for download from the QAD Store (see Reporting Framework Source and Samples on QAD Store).
Configuring Business Intelligence (BI) Portal for Dashboards
This release of the QAD .NET UI includes Dashboards, which bring together browses, web pages, business intelligence, and metrics within panels. If you have QAD Business Intelligence (BI) 3.9, you can include BI panels on dashboards. To have the QAD .NET UI communicate with BI, you need to specify the URL for accessing the BI portal in the client session configuration (client-session.xml) file’s <BI.Dashboard.URL> setting. The BI portal must be accessible to allow BI panels to be available on dashboards. (If the BI portal is not accessible, the BI panel option will not be available on Dashboards | Create Dashboard.) The setting in <TomcatHome> /webapps/qadhome/configurations/ <environment> /client-session.xml is:
 
<BI.Dashboard.URL>http://ip_address_of_BI:port_number/qadbi</BI.Dashboard.URL>
 
In addition, to access the BI portal, the login/password for the QAD .NET UI client must match the login/password for the BI portal.
Operational Metrics for Dashboards
Dashboards can include operational metrics if they are available on your system. QAD provides the Operational Metrics functionality with an active maintenance contract, and a term license key applied to the QAD Enterprise Applications product (see https://support.qad.com/license_keys/activemaintenance ). For more information, contact QAD Support.